![]() ![]() ![]() ![]() I'm not asking a "big work".Download QuickMemoryTestOK 4 full version program free setup for Windows. Maybe you think it's easy to support those "clones" because kernel work on both phones (for example : wiko cink 5 and MMX A116) but there is kernel changes which are impossible to check without source (for example : best support of different sensors at same time for mtk drivers - see oppo R819 kernel source).įor others phones (with manufacturer source) : I'm surprised to see people coming, sending requests and no one trying to send patches, reviews, docs about diff (see post #2). So if you ask to support MMX A116, Xolo Q800 or others which have no kernel source from manufacturer itself (not another manufacturer), it won't be my priority and I will maybe never support those phones (I'm working on Omnirom for MT6589 phones too so I have a lot of work scheduled). I'm not going to support "clones" or "rebranded" phones if manufacturer is not releasing the kernel source (this is GPL rules). Guys, you are "spamming" my thread with requests actually ! This should be a dev discussion.įor requests you can MP me (I'm replying to most of them - or replying in concerned thread). Ok this is for hal but it's still interesting to check changes and this is actually my focus. The focus of doc would be to show if the changes would be interesting for system part (better app for photos for example)Įxample of new var introduced by recent mtk source (MAIN_SENSOR_ROTATE_DEGREE_X see config files) : The other idea would be to create documents, to document a specific change between another mtk source like those changes : So for merging I'm replacing VENDOR_EDIT by OPPO_R819 so when kernel is compiling it should be able to keep Oppo changes only for Oppo R819 (thank you preprocessor for your hard work). Create a build script with a var for TARGET_PRODUCT which would be able to check env, build kernel and modules to out/ (my build.sh is a example for e960 - Faea F2S)Īctually, I'm merging Oppo R819 sources and I saw there was differences on mediatek drivers (some things were added by Oppo). ![]() Adapt configuration files (Remove drivers not added or not working, add missing var).Check changes between your original stock source of your device.Do pull requests to add devices or drivers.Check if you can compile actually suported devices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |