Database Info

[DEV] Porting kernel 3.10.x to d2 for Lollipop

As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!

Does your kernel compile and boot on cm11? If it does, there shouldn't be much problems in getting it working on L.

Any news? Does it compile?

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y

Ivan_Meler said:
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y
Click to expand...
Click to collapse
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
ztotherad said:
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]
Click to expand...
Click to collapse
I know samsung does things like that (i have few other devices from them) but hey thats samsung and they are lazy so they dont want to update kernel version after device is relesed so they do this not to feel outdated on softwere side

Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works

frap129 said:
Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works
Click to expand...
Click to collapse
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
I was planning on working on that as well over the weekend.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays

Ivan_Meler said:
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays
Click to expand...
Click to collapse
I'm very new to the AOSP build process and didn't have much luck last night getting the CM device sources to play nicely with AOSP. I'm finding it difficult to find any relevant guides on porting over the CM device trees to pure AOSP. If you or anyone else can help by explaining the process or pointing to a guide that I may have missed, I'd be grateful. Plus the more people we have collaborating on his, the better our chances of getting Lollipop on our devices.

I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy

Restl3ss said:
I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy
Click to expand...
Click to collapse
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?

polarEskimo said:
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?
Click to expand...
Click to collapse
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)

Restl3ss said:
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)
Click to expand...
Click to collapse
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.

polarEskimo said:
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.
Click to expand...
Click to collapse
I'll push what I've got to github after this experiment

Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much

Ivan_Meler said:
Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much
Click to expand...
Click to collapse
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS

Managed to work past my problem with SElinux for now, the build has now moved on to... another set of errors!
Build currently hangs at this:
Code:
host C++: libutils_32 <= system/core/libutils/StopWatch.cpp
host C++: libutils_32 <= system/core/libutils/String8.cpp
host C++: libutils_32 <= system/core/libutils/String16.cpp
host C++: libutils_32 <= system/core/libutils/SystemClock.cpp
host C++: libutils_32 <= system/core/libutils/Threads.cpp
host C++: libutils_32 <= system/core/libutils/Timers.cpp
system/core/libutils/Timers.cpp: In function 'nsecs_t systemTime(int)':
system/core/libutils/Timers.cpp:43:13: error: 'CLOCK_BOOTTIME' was not declared in this scope
build/core/binary.mk:618: recipe for target 'out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o' failed
make: *** [out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o] Error 1
#### make failed to build some targets (01:19 (mm:ss)) ####
Going to bed, will get back at it in the morning. Source should be up on github by tomorrow night

Restl3ss said:
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS
Click to expand...
Click to collapse
I'm with you on that, I'd rather have pure AOSP than buggy CM nightlies. Also interesting choice of ROM name lol. Thanks for your hard work and I'm looking forward to pulling down your repos so I can take a stab at these compile-time issues.

Kernel Developer available for any project

Hello all Samsung Galaxy Young users,
As you can see my name on this forum is PsychoGame.
I'm not a full-time software developer, but rather a Linux enthusiast which is familiar with Linux and it's kernel for over 10+ years.
When using Linux (Fedora in my case) I'm always interested in optimizing the hell out of it so I know I get maximum performance out of my hardware.
This of course requires using custom *self* build kernels which are optimally patched and configured for my specific hardware.
Conclusion is that I have real good knowledge of what's going on in the kernel and can be a valuable addition to a developers team.
In the past I worked on other projects kernel and android (CyanogenMod) for example (Samsung Galaxy Y (S5630)) where with my kernel knowledge I've been able to help other developers move forward very much.
Already I've downloaded the (Samsung Galaxy Young (GT-S6310) Update 1) kernel source to my PC, and found out on which CAF branch this kernel was based on.
Now I'm ready to get involved in development for at least the kernel of this device.
Are there any requests of things people would want me to do?
I've looked into what Shinkamaru kernel currently features and think I can make some more improvements on this as well.
Not only am I making myself available for development but also want to try to form a "Development Team" for this device.
Next to my android/linux enthusiasm I have a personal life as well so it would be virtually impossible to do all development on my own.
If you are interested in joining this "Development Team" and you have some past experience with kernel building with linux (or android preferred).
Or maybe you have some knowledge in ROM development leave a comment in here.
Greetings PsychoGame

Thank you for your availability and desire to help us!
I have a Galaxy Young Duos TV (S6313T) and this device doesn't have any custom kernel
Can you create a simple one for us?
A kernel that support CM11 would be helpful too
This is my stock kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=3523152
Thaaaanks! :good:

Hello OsniNO,
Thank you for you're message.
It's midnight over here in Holland, so I will take a look into the sourcecode you provided in your post.
What I'll do first is compare the sourcecode for your specific device with the available sourcecode of the other Galaxy Young devices.
When sourcecode is mostly the same between most devices I'll try to create a overall kernel which may be usable in all Galaxy Young released devices.
Features to improve the device performance and responsiveness which will be included by me are as follow:
- KSM will be enabled cause the Galaxy Young is a low ram device in my opinion so this should improve performance and responsiveness.
- ZRAM should and will be enabled by default to improve the devices RAM availability which also should improve performance and responsiveness.
- Interactive scheduler should be enabled by default with no-op (maybe) as default.
Greetings PsychoGame

PsychoGame said:
Hello OsniNO,
Thank you for you're message.
It's midnight over here in Holland, so I will take a look into the sourcecode you provided in your post.
What I'll do first is compare the sourcecode for your specific device with the available sourcecode of the other Galaxy Young devices.
When sourcecode is mostly the same between most devices I'll try to create a overall kernel which may be usable in all Galaxy Young released devices.
Features to improve the device performance and responsiveness which will be included by me are as follow:
- KSM will be enabled cause the Galaxy Young is a low ram device in my opinion so this should improve performance and responsiveness.
- ZRAM should and will be enabled by default to improve the devices RAM availability which also should improve performance and responsiveness.
- Interactive scheduler should be enabled by default with no-op (maybe) as default.
Greetings PsychoGame
Click to expand...
Click to collapse
Thank you veeeery much!!
Just can't wait

Hello from germany,
since i got the NFC Version 6310N,which is technically the same, i would like to request cifs kernel support to Mount smb shares (dont get me wrong es file manager works eine,but i want the share to show up as a folder )
Thanks in advance

I too have the Galaxy Young GT-S6310N and would be more than happy to help out with testing and such
Don't have any real experience with kernel-building and the like, but I do have loads of spare time and would really like to see a working cm11 for 6310N this year :fingers-crossed:

thank you very much for working on the young gt-s6310
hi.
requests...
being able to swap ram using the sd card (class 10), being able to really and completly move apps to sd card, and being able to swap internal sd with external sd (saw there is a tutorial already - haven't tried it because...):crying:
and some personal help with my gt-s6310T. after factory, cash and delvik cash wipe, the cm11 (cm11_s6310_by_DevSwift1_V4) and the gapps for cm11. (my cwm was never able to access my ext sd card in clockworkmod but everything else worked with my ext sd card) since then my phone/usb connect/clockworkmod/twrp/phone settings-storage couldn't locate my ext sd card at all. only grey mound sd in the storage area. and the cm11 messed up my phone so badly that i had to reflash a stockrom only using odin cause nothing else worked. no internal sd in cwm, no access to my computer using the usb cable. after that everything was ok but still stuck with no ext sd card. what should i do to fix this?

Thanks for your help in advance.
As I have mentioned in another post i want to make CM13 for S6312(I'll start doing it next year [I'm busy with my scientific research(not as high level as it sounds)]), but I don't have the experience to do that yet so I would be greatfull if you could help with Kernel and hopefully other stuff.

xlen said:
Thanks for your help in advance.
As I have mentioned in another post i want to make CM13 for S6312(I'll start doing it next year [I'm busy with my scientific research(not as high level as it sounds)]), but I don't have the experience to do that yet so I would be greatfull if you could help with Kernel and hopefully other stuff.
Click to expand...
Click to collapse
I wish you good luck but without a good understanding of how linux works or even how to code it's going to be impossible for you to make CM13. Also let's first just finish CM11 before we go any higher.

sorry guys
lesleyxxx15 said:
I wish you good luck but without a good understanding of how linux works or even how to code it's going to be impossible for you to make CM13. Also let's first just finish CM11 before we go any higher.
Click to expand...
Click to collapse
Thanks luck is one of many things I need!
sorry guys but I will start only february as I have to finish my scientific research...

PsychoGame said:
Hello all Samsung Galaxy Young users,
As you can see my name on this forum is PsychoGame.
I'm not a full-time software developer, but rather a Linux enthusiast which is familiar with Linux and it's kernel for over 10+ years.
When using Linux (Fedora in my case) I'm always interested in optimizing the hell out of it so I know I get maximum performance out of my hardware.
This of course requires using custom *self* build kernels which are optimally patched and configured for my specific hardware.
Conclusion is that I have real good knowledge of what's going on in the kernel and can be a valuable addition to a developers team.
In the past I worked on other projects kernel and android (CyanogenMod) for example (Samsung Galaxy Y (S5630)) where with my kernel knowledge I've been able to help other developers move forward very much.
Already I've downloaded the (Samsung Galaxy Young (GT-S6310) Update 1) kernel source to my PC, and found out on which CAF branch this kernel was based on.
Now I'm ready to get involved in development for at least the kernel of this device.
Are there any requests of things people would want me to do?
I've looked into what Shinkamaru kernel currently features and think I can make some more improvements on this as well.
Not only am I making myself available for development but also want to try to form a "Development Team" for this device.
Next to my android/linux enthusiasm I have a personal life as well so it would be virtually impossible to do all development on my own.
If you are interested in joining this "Development Team" and you have some past experience with kernel building with linux (or android preferred).
Or maybe you have some knowledge in ROM development leave a comment in here.
Greetings PsychoGame
Click to expand...
Click to collapse
Hello bro..
It's rare to find devs who work for other type of phones..
I want to ask if you can help in getting a custom recovery or kernel for the Galaxy Core Prime VE (G361H)? We don't have any devs or any development, we only have a pre-rooted ROM..
We want a custom recovery or a kernel with SeAndroid permissive and we won't say no for any added features... so can you please help us?
Thanks in advance..
Sent from my SM-G361H using Tapatalk

New linux kernel 4.9 for Snapdragon 625 and kernel and HAL source code

Great news fron Weibo, thanks for Mokee's developer XiNGRZ's share.
New linux kernel 4.9 for Qualcomm Snapdragon 625 and kernel and HAL source code of Android 9
http://caf.mokeedev.com/?version=9
https://wx1.sinaimg.cn/large/4b263fe4gy1futf5hw8wmj21hs0a2gt0.jpg
https://m.weibo.cn/status/4279258651583321
I don't know how to upload the picture, so only can give you the website's hyperlink

Yes! Looking in the CAF sources page (https://wiki.codeaurora.org/xwiki/bin/QAEP/release) you can see that kernel 4.9 for msm8953 and msm8953pro exists since Oreo ( LA.UM.6.6.2.r1-04200-89xx.0 is yet based on kernel 4.9 and CAF released it in 19/07/2018) and it was based on Linux 4.9.82, now with Android 9 it's based on Linux 4.9.112.
So, long life to all these devices that has this SoC!
But, for Pie there are 2 tags and one is still based on kernel 3.18 (to be more precise, 3.18.115, LA.UM.7.6.r1-02000-89xx.0 ) and the other one is at kernel 4.9 (4.9.112, LA.UM.7.6.2.r1-03000-89xx.0 ). I think we can see some ROMs with kernel 4.9 in the next months, but for now we stay on 3.18 while waiting they make perfectly working 4.9.

matteo0026 said:
Yes! Looking in the CAF sources page (https://wiki.codeaurora.org/xwiki/bin/QAEP/release) you can see that kernel 4.9 for msm8953 and msm8953pro exists since Oreo ( LA.UM.6.6.2.r1-04200-89xx.0 is yet based on kernel 4.9 and CAF released it in 19/07/2018) and it was based on Linux 4.9.82, now with Android 9 it's based on Linux 4.9.112.
So, long life to all these devices that has this SoC!
But, for Pie there are 2 tags and one is still based on kernel 3.18 (to be more precise, 3.18.115, LA.UM.7.6.r1-02000-89xx.0 ) and the other one is at kernel 4.9 (4.9.112, LA.UM.7.6.2.r1-03000-89xx.0 ). I think we can see some ROMs with kernel 4.9 in the next months, but for now we stay on 3.18 while waiting they make perfectly working 4.9.
Click to expand...
Click to collapse
Nice ! I love my sd625 device, good to know it's not left behind with an old Kernel.
Do you think this Kernel could improve performance and battery life ? Maybe make this chip even more efficient

Redmi4power said:
Nice ! I love my sd625 device, good to know it's not left behind with an old Kernel.
Do you think this Kernel could improve performance and battery life ? Maybe make this chip even more efficient
Click to expand...
Click to collapse
No, I think it just improves security. But it's yet a big step for sd625

matteo0026 said:
No, I think it just improves security. But it's yet a big step for sd625
Click to expand...
Click to collapse
It does improve performance and battery life. Main thing, amongst other things like improved security and way newer drivers, is the EAS.
Our devs are already working on 4.9 kernel for Mi A1, already testing it and recently released experimental builds and even now it's no comparison to 3.18 in it's current state, it's not even fair to compare.

airidosas252 said:
It does improve performance and battery life. Main thing, amongst other things like improved security and way newer drivers, is the EAS.
Our devs are already working on 4.9 kernel for Mi A1, already testing it and recently released experimental builds and even now it's no comparison to 3.18 in it's current state, it's not even fair to compare.
Click to expand...
Click to collapse
I saw that thread on Mi A1, devs are doing a good work. And do you think that EAS could be usable on our SoC too? If yes, I know that improves much the battery life

matteo0026 said:
I saw that thread on Mi A1, devs are doing a good work. And do you think that EAS could be usable on our SoC too? If yes, I know that improves much the battery life
Click to expand...
Click to collapse
Of course, EAS is impremented by Qcom itself on 4.9, so it is properly optimized and calibrated. Even now I don't need to adjust anything, just left it as it is.
What's more interesting is what OEM is going to do - be with 3.18 or move on to 4.9. Knowing Xiaomi, I'm guessing they'll stay on 3.18.

airidosas252 said:
Of course, EAS is impremented by Qcom itself on 4.9, so it is properly optimized and calibrated. Even now I don't need to adjust anything, just left it as it is.
What's more interesting is what OEM is going to do - be with 3.18 or move on to 4.9. Knowing Xiaomi, I'm guessing they'll stay on 3.18.
Click to expand...
Click to collapse
Ehm, yes I they stay on 3.18 because there are 3.18 tags based on Pie for msm8953_64. I'm thinking to do 4.9 for p2, but... I don't know what I have to do... I haven't knowledges, but I want to give a try.

matteo0026 said:
Ehm, yes I they stay on 3.18 because there are 3.18 tags based on Pie for msm8953_64. I'm thinking to do 4.9 for p2, but... I don't know what I have to do... I haven't knowledges, but I want to give a try.
Click to expand...
Click to collapse
Some crucial stuff might need backporting for sure, you should ask around other people. They might help you out. I'm out of development game, too busy doing other things in my life, so can't comment on this much more.

matteo0026 said:
Ehm, yes I they stay on 3.18 because there are 3.18 tags based on Pie for msm8953_64. I'm thinking to do 4.9 for p2, but... I don't know what I have to do... I haven't knowledges, but I want to give a try.
Click to expand...
Click to collapse
p2 community is with you. we can help you with testing. go ahead ???

Any update?

There will be advantage ?
Is it easy to port ?

Can not download source code for msm8953_64

Ask in tissot forum may be they'll know something

when its coming?
so excited:fingers-crossed:

ZJ_CN said:
Great news fron Weibo, thanks for Mokee's developer XiNGRZ's share.
New linux kernel 4.9 for Qualcomm Snapdragon 625 and kernel and HAL source code of Android 9
http://caf.mokeedev.com/?version=9
https://wx1.sinaimg.cn/large/4b263fe4gy1futf5hw8wmj21hs0a2gt0.jpg
https://m.weibo.cn/status/4279258651583321
I don't know how to upload the picture, so only can give you the website's hyperlink
Click to expand...
Click to collapse
any update ?
SD625 kernel 4.9

Hello, please help me find the kernel sources CAF for msm8953_64 3.18.71-74, thanks in advance
---------- Post added at 02:28 PM ---------- Previous post was at 02:21 PM ----------
Hello, please help me find the kernel sources CAF for msm8953_64 3.18.71-74, i have compile kernel for device billion capture +, thanks in advance

Would like to breath new life into my Lenovo P2, but I guess 4.9 will remain a dream?

[ROM] [UNOFFICIAL] LineageOS 14 for Meizu M5C [MT6737m]

LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c

Assim que possível, irei testar!

Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?

thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better

XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM

thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest

XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...

thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources

XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.

thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working

XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?

thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone

XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.

Great work!

Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?

pls compile

publish a release

Is it possible to use a recent Kernel in tab2?

I was wondering if is it possible to use a recent kernel in tab2.
There is a Linux system (Maemo Leste, based on Devuan (Debian without systemd)) that runs in a Motorola Droid 4, that uses a recent version of the Linux Kernel (5.11) and has the same CPU and GPU. https://leste.maemo.org/Motorola_Droid_4
Would it work in tab2?
(sorry for my english).

gu_1_ said:
I was wondering if is it possible to use a recent kernel in tab2.
There is a Linux system (Maemo Leste, based on Devuan (Debian without systemd)) that runs in a Motorola Droid 4, that uses a recent version of the Linux Kernel (5.11) and has the same CPU and GPU. https://leste.maemo.org/Motorola_Droid_4
Would it work in tab2?
(sorry for my english).
Click to expand...
Click to collapse
This rom here uses a 3.4 kernel which is currently the latest one used on Tab 2
[ROM][AOSP][8.1 Oreo] Unlegacy Android (Unofficial)
Warranties: THIS GUIDE COMES WITH NO WARRANTY. I AM NOT RESPONSIBLE OF BREAKING YOUR PRECIOUS TABLET. PLEASE BACKUP YOUR DATA BEFORE CONTINUING, AS THIS GUIDE WILL WIPE YOUR DATA. Also, this guide assumes you have the following requirements...
forum.xda-developers.com
Why don't you try building a rom with 5.11 one ?? As you can see in the thread above, camera doesn't work due to 3.4 kernel and also wifi was an issue earlier but it is fixed now. Something or the other might not work but maybe the rom would boot up atleast !

gu_1_ said:
I was wondering if is it possible to use a recent kernel in tab2.
There is a Linux system (Maemo Leste, based on Devuan (Debian without systemd)) that runs in a Motorola Droid 4, that uses a recent version of the Linux Kernel (5.11) and has the same CPU and GPU. https://leste.maemo.org/Motorola_Droid_4
Would it work in tab2?
(sorry for my english).
Click to expand...
Click to collapse
Actually yes, we can use the 5.12 kernel i worked on but not with android, with Alpine Linux, please check https://forum.xda-developers.com/t/...linux-on-samsung-galaxy-tab-2-unified.4171483 (5.12 kernel only for 7 inch tablets, the 10 inch ones have different display panel, if you have a 10 inch one want to help with making it usable with 5.12 kernel, I'll try)

Mighty said:
Actually yes, we can use the 5.12 kernel i worked on but not with android, with Alpine Linux, please check https://forum.xda-developers.com/t/...linux-on-samsung-galaxy-tab-2-unified.4171483 (5.12 kernel only for 7 inch tablets, the 10 inch ones have different display panel, if you have a 10 inch one want to help with making it usable with 5.12 kernel, I'll try)
Click to expand...
Click to collapse
Update its 5.15 now https://gitlab.com/postmarketOS/pmaports/-/merge_requests/2526

TheDoctor46 said:
This rom here uses a 3.4 kernel which is currently the latest one used on Tab 2
[ROM][AOSP][8.1 Oreo] Unlegacy Android (Unofficial)
Warranties: THIS GUIDE COMES WITH NO WARRANTY. I AM NOT RESPONSIBLE OF BREAKING YOUR PRECIOUS TABLET. PLEASE BACKUP YOUR DATA BEFORE CONTINUING, AS THIS GUIDE WILL WIPE YOUR DATA. Also, this guide assumes you have the following requirements...
forum.xda-developers.com
Why don't you try building a rom with 5.11 one ?? As you can see in the thread above, camera doesn't work due to 3.4 kernel and also wifi was an issue earlier but it is fixed now. Something or the other might not work but maybe the rom would boot up atleast !
Click to expand...
Click to collapse
Well as far as Android is concerned, in the future, we might get Android 11 with the 5.4 android common kernel. That won't be a easy job to make though.
To port to mainline (5.15 kernel or newer) is kinda possible but it requires even harder work, indicated by the fact that there is only a finger-countable few of those get to this stage, and even if you get it, some features won't work.

LR7875 said:
Well as far as Android is concerned, in the future, we might get Android 11 with the 5.4 android common kernel. That won't be a easy job to make though.
To port to mainline (5.15 kernel or newer) is kinda possible but it requires even harder work, indicated by the fact that there is only a finger-countable few of those get to this stage, and even if you get it, some features won't work.
Click to expand...
Click to collapse
Making android work with mainline is going to be a task! For now we are running mainline 5.15 with PostMarketOS

Mighty said:
Making android work with mainline is going to be a task! For now we are running mainline 5.15 with PostMarketOS
Click to expand...
Click to collapse
Well that is good news, hope you reach success!
If that come true it will be a legend!