In the interest of keeping this topic easy to follow, lets keep the posts developer/development related. Off topic posts and questions will likely be reported. Warning From A Moderator: http://forum.xda-developers.com/showthread.php?p=64117749
Hello everyone,
This thread is for discussing, and furthering the development of aosp/cm for our devices. I and most others believe it is in the best interest of getting the port done if we all collaborate on it. I will try to update this op and post relevant information as it becomes available.
Cheers!
CM13 Working Repo
https://github.com/7420dev
Current Goals: Listed In Order Of Priority
1.) Fixing The Various Drivers(camera,etc.)
2.) Misc. Bug Fixing
Current Status:
Open Source Gralloc in testing. Appears to be working properly.(Screen Works)
List Of Working Drivers:
-WiFi
-GPS
-AP Hotspot
-Basic 2D Graphics
-GPS
-LED
-MTP
-Sound
-BT
-Texting(SMS/MMS)
-Mobile Data
-Telephony
Here's a video from @arter97 booting cm using @tdcfpp gralloc:
https://youtu.be/fv0I45HtgtQ
Donating:
If you wish to donate, please donate to the people putting the most effort into this project! To make it easier these are the top two currently.
@tdcfpp and @sktjdgns1189 and you can donate to him here: https://t.co/sf7R69JYqx tdcfpp is working extremely hard on porting gralloc, and making excellent progress. Sktjdgns1189 is working on hard on fixing various driver issues. So far he's fixed telephony, sound and WiFi to name a few. I will try to update this as more people contribute!
Do not ask for etas or test builds!
It will happen eventually, but it will be laggy, and buggy. There is no point, if people wanted AOSP or CM, they shouldn't get a Samsung/Exynos device.
Is posible to port meizu pro 5 rom wich have same soc aas galaxy s6.
Rekan_ said:
It will happen eventually, but it will be laggy, and buggy. There is no point, if people wanted AOSP or CM, they shouldn't get a Samsung/Exynos device.
Click to expand...
Click to collapse
I would be surprised if it was laggy. Buggy, most likely, but laggy I don't think so. I've used aosp on other Samsung devices and it was always faster than TW. I didn't buy my s6 with the expectation of aosp, but if it is possible, I would definitely like to try it. The exynos 7420 is an absolute beast, and if the 810 can run the nexus like butter, imagine what the 7420 could do.
kiko3 said:
Is posible to port meizu pro 5 rom wich have same soc aas galaxy s6.
Click to expand...
Click to collapse
It could be possible. It will be interesting to see when the source comes out.
Sent from my SM-G925K using XDA Free mobile app
Xileforce said:
I would be surprised if it was laggy. Buggy, most likely, but laggy I don't think so. I've used aosp on other Samsung devices and it was always faster than TW. I didn't buy my s6 with the expectation of aosp, but if it is possible, I would definitely like to try it. The exynos 7420 is an absolute beast, and if the 810 can run the nexus like butter, imagine what the 7420 could do.
Click to expand...
Click to collapse
Probably the older Samsung devices had their sources released and this phones sources haven't been.
And yeah, I had a smooth experience with my S4 and S3 with AOSP
Pure Android 6.0 on galaxy tab S is not laggy at all! it's so smooth compared to touchwizz. On S6 it will literally flying
I don't know anything about how to achieve this.
But I found the Meizu MX Pro 5 firmware (Which have the same chip as s6)
download.meizu.com/Firmware/Flyme/PRO_5/4.5.4.1/cn/20151022054017/9e3d5077/update.zip
Hope it helps
I know the end goal is to be able to compile Android for the Galaxy S6 from scratch, but I was wondering if it would be technically possible to create some sort of hybrid version. Although a complete AOSP version would be amazing, I believe a lot of users would be happy if someone could take the current kernel based on Samsung sources, so everything around boot and driver/hardware initialization should work, and put some version of the AOSP interface on top of that. Similar to how the Google Play Editions used to work. Is that in any way feasible?
woeds said:
I know the end goal is to be able to compile Android for the Galaxy S6 from scratch, but I was wondering if it would be technically possible to create some sort of hybrid version. Although a complete AOSP version would be amazing, I believe a lot of users would be happy if someone could take the current kernel based on Samsung sources, so everything around boot and driver/hardware initialization should work, and put some version of the AOSP interface on top of that. Similar to how the Google Play Editions used to work. Is that in any way feasible?
Click to expand...
Click to collapse
One of the things I have done is to take a hal library and substitute it on stock with an open source one. That have worked on the i9300 with gralloc.
---------- Post added at 08:29 AM ---------- Previous post was at 08:27 AM ----------
One thing I would need from our kernel devs is a dual boot kernel. Would it be possible @arter97?
tdcfpp said:
One of the things I have done is to take a hal library and substitute it on stock with an open source one. That have worked on the i9300 with gralloc.
---------- Post added at 08:29 AM ---------- Previous post was at 08:27 AM ----------
One thing I would need from our kernel devs is a dual boot kernel. Would it be possible @arter97?
Click to expand...
Click to collapse
Haha
I've been dualbooting my S6 since my kernel's debut.
This is a bit hacky, but it's working since S3 days.
This will give you a bit of an idea how it works :
https://bitbucket.org/arter97/andro...unt.sh?at=g920fi&fileviewer=file-view-default
First time I spun a CM build from bmc08gt sources, I dualbooted it with Touchwiz intact.
Obviously, ramdisk is not compatible. So to boot different ROMs, different boot.img would be needed but it's not a big deal (at least for me).
Even using the recovery as the handy multiboot solution is quite nice since I'd say the actual recovery won't be much needed during development.
BOOT = Touchwiz, RECOVERY = CM.
arter97 said:
Haha
I've been dualbooting my S6 since my kernel's debut.
This is a bit hacky, but it's working since S3 days.
This will give you a bit of an idea how it works :
https://bitbucket.org/arter97/andro...unt.sh?at=g920fi&fileviewer=file-view-default
First time I spun a CM build from bmc08gt sources, I dualbooted it with Touchwiz intact.
Obviously, ramdisk is not compatible. So to boot different ROMs, different boot.img would be needed but it's not a big deal (at least for me).
Even using the recovery as the handy multiboot solution is quite nice since I'd say the actual recovery won't be much needed during development.
BOOT = Touchwiz, RECOVERY = CM.
Click to expand...
Click to collapse
Well, I don't want to re-invent the wheel. Is it possible to dual boot with your s6 kernel?
tdcfpp said:
Well, I don't want to re-invent the wheel. Is it possible to dual boot with your s6 kernel?
Click to expand...
Click to collapse
By flashing the kernel each time, yes.
(Or using RECOVERY as a second kernel)
arter97 said:
Haha
I've been dualbooting my S6 since my kernel's debut.
This is a bit hacky, but it's working since S3 days.
This will give you a bit of an idea how it works :
https://bitbucket.org/arter97/andro...unt.sh?at=g920fi&fileviewer=file-view-default
First time I spun a CM build from bmc08gt sources, I dualbooted it with Touchwiz intact.
Obviously, ramdisk is not compatible. So to boot different ROMs, different boot.img would be needed but it's not a big deal (at least for me).
Even using the recovery as the handy multiboot solution is quite nice since I'd say the actual recovery won't be much needed during development.
BOOT = Touchwiz, RECOVERY = CM.
Click to expand...
Click to collapse
Couldn't we use an implementation of anykernel to allow ramdisk compatibility with cm and tw at the same time?
Xileforce said:
Couldn't we use an implementation of anykernel to allow ramdisk compatibility with cm and tw at the same time?
Click to expand...
Click to collapse
Multibooting with a single kernel requires multiple ramdisk to be in a single boot.img
Anykernel method is not suitable with this.
arter97 said:
Multibooting with a single kernel requires multiple ramdisk to be in a single boot.img
Anykernel method is not suitable with this.
Click to expand...
Click to collapse
Oh okay I see what you are referring to. I meant in terms of not multibooting. As in if we wanted to develop a kernel that would work on both tw and cm, probably the only way to do that would be anykernel correct?
Xileforce said:
Oh okay I see what you are referring to. I meant in terms of not multibooting. As in if we wanted to develop a kernel that would work on both tw and cm, probably the only way to do that would be anykernel correct?
Click to expand...
Click to collapse
Yes and it still requires some source changes to accommodate both CM and Touchwiz(MTP, etc) but still I don't like Anykernel method.
I will release 2 separate kernels if CM happens.
arter97 said:
Yes and it still requires some source changes to accommodate both CM and Touchwiz(MTP, etc) but still I don't like Anykernel method.
I will release 2 separate kernels if CM happens.
Click to expand...
Click to collapse
You got time ahead then.
arter97 said:
Yes and it still requires some source changes to accommodate both CM and Touchwiz(MTP, etc) but still I don't like Anykernel method.
I will release 2 separate kernels if CM happens.
Click to expand...
Click to collapse
Got it. I feared there may be some source changes. I've never been a fan of anykernel either.
Found out that this app is compatible with the s6. I'm wondering if the tool would be able to patch your kernel @arter97
http://forum.xda-developers.com/showthread.php?t=2447534
Related
CYANOGENMOD 10.2 [UNOFFICIAL BUILDS]
Code:
BUGS:
no 1080p recording
cant use UMS (if you want to transfer something to your mobile connect with PTP and manually move it on your phone)
probably more
Code:
DOWNLOADS:
ROM
[URL="http://www.androidfilehost.com/?fid=23212708291682444"]DOWNLOAD ROM[/URL]
GAPPS
[URL="http://www.androidfilehost.com/?fid=23212708291681346"]gapps-jb-20130813-signed[/URL]
Code:
INSTALLATION INSTRUCTION:
Full wipe
manual format /system
Flash ROM
Flash Gapps
Reboot
Code:
BIG THANKS TO:
the CyanogenMod team
[URL="http://forum.xda-developers.com/member.php?u=3430186"]Mateo1111[/URL]: cause i really like your roms
[URL="http://forum.xda-developers.com/member.php?u=360947"]AntonX[/URL]: got some tweaks from him
change log
Code:
[CENTER]
CHANGELOG:
28/11
cm source
build is up and running
25/11
Updated cm source
Fixed settings for l9 - it works now
Fixed emulated storage - its disabled now
got some problems with connecting phone with UMS
though could be the school computer.
Going to test later today @ home
[/CENTER]
sweet nice to see new developer out there for p760 - wish you all the best and good luck in development
ulaon said:
sweet nice to see new developer out there for p760 - wish you all the best and good luck in development
Click to expand...
Click to collapse
Thanks ill do my best to learn
i stop developing this rom since mateo has a fully functional cm10.2 and its unuseful to have same roms this does not mean i stop developing this was more an experiment for myself
Fl3kzZ said:
i stop developing this rom since mateo has a fully functional cm10.2 and its unuseful to have same roms this does not mean i stop developing this was more an experiment for myself
Click to expand...
Click to collapse
"Nice, long career" ...but thank you! :good:
i wont stop but what i mean is there is already a stable 10.2 rom with frequent updates so whats the point to create another one?
JulianJenner said:
"Nice, long career" ...but thank you! :good:
Click to expand...
Click to collapse
Fl3kzZ said:
i wont stop but what i mean is there is already a stable 10.2 rom with frequent updates so whats the point to create another one?
Click to expand...
Click to collapse
He just quite developing it. You should keep it updated, as long as cm10.2 code still changes. Also you can probably still tweak the kernel some more, or add some cool cuatom features
And I dont know, how much you know about kernel development, but there is a thread about a "booting 3.4 kernel" in the galaxy nexus forum. This one also contains a lot of degfconfig settings, which might also work on our board (4430 and 4460 chipsets AFAIK). If you could check which enhancements we can use, so we can use them for 4.4 in the future. They might solve those graphical glitches.
Sent from my SM-T210 using xda app-developers app
N00BY0815 said:
He just quite developing it. You should keep it updated, as long as cm10.2 code still changes. Also you can probably still tweak the kernel some more, or add some cool cuatom features
And I dont know, how much you know about kernel development, but there is a thread about a "booting 3.4 kernel" in the galaxy nexus forum. This one also contains a lot of degfconfig settings, which might also work on our board (4430 and 4460 chipsets AFAIK). If you could check which enhancements we can use, so we can use them for 4.4 in the future. They might solve those graphical glitches.
Sent from my SM-T210 using xda app-developers app
Click to expand...
Click to collapse
alright i will get back to it but i had some probs with pc :/ my hdd crashed so i had to reinstall everything and for some reason i couldnt dual boot ubuntu and win 7 but got a working backtrack 5 distro so after weekend ill set things up
Sent from my LG-P760
got some trouble with dual booting ubuntu and windows but maybe found a way
so expect some builds soon
Google has recently released the 3.10 linux kernel for Android. and CodeAurora has also got it. I was wondering if it's realistic to port in this phase. I tried to but I failed hard lol. Main reason to port the 3.10 series is that it should have a great battery life. I'm not sure whether it will run on KitKat since it's supposed to be for Android 5.0.
Links:
Google Kernel: https://android.googlesource.com/kernel/common.git/+/experimental/android-3.10
CodeAurora Kernel: https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10
Anyone else attempted? If anyone could give me some more info about this I would be very happy!
Thread cleaned
How many times do we have to say it?
Keep this damn soap opera drama OFF XDA and stick to your Google +
How rude to bring all this crap in here to the OP's discussion
Next talk of secret kernels or banned members will be...trouble.
If you have no respect for XDA, then leave XDA...please!
Thank you for your cooperation
Friendly Neighborhood Senior Moderator
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
sorg said:
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
Click to expand...
Click to collapse
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
broodplank1337, what happens if you build a recovery and fastboot boot that?
xboxfanj said:
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
Click to expand...
Click to collapse
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
sorg said:
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
Click to expand...
Click to collapse
Yeah, there's a bunch of proprietary files specific to the SOC.
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
LLStarks said:
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
Click to expand...
Click to collapse
True. Caf does have some 3.10 device branches but none for 8960/8064, since those are not supported. Not sure why since they do support weaker chips such as 8226 and 8610. They do have some ramdisk changes for 3.10, but even with all that, I have no adb and no ramconsole on the optimus g (nexus 4).
Sent from my Optimus G using xda app-developers app
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
LLStarks said:
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
Click to expand...
Click to collapse
my s3 3.4-drm kernels supports it - patches came from here ==>
(s4 kernel is a WIP)
https://github.com/freedreno/kernel-msm/
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
LLStarks said:
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
Click to expand...
Click to collapse
We have offloaded all audio processing and mp3 decoding to the DSP. Thus allowing all 4 primary cores to sleep while playing audio. Media player app itself may use CPU cycles for UI updates when the screen is on. Working on WMA decoding...
Sent from my GT-I9505G using XDA Premium 4 mobile app
please make this kernel work with miui rom!
ALL WORK HAS MOVED TO THE 3.4 BRINGUP. YES, THAT MEANS 3.4 IS BOOTING AND WIP AND THIS KERNEL IS NOW DEPRECATED! CLICK HERE TO VIEW 3.4 PROGRESS
Check latest posts for updates
As you may be aware, we've been trying unsuccessfully to boot Nvidia's 3.4 kernel for tegra 3 on grouper.
Progress has pretty much halted, as this project needs to be finished before we have any hope of 3.4 ever working.
SAUCES
-
WE ALSO HAVE A GITHUB ORGANIZATION
What is this?
An attempt to get Google's ludicrously outdated grouper 3.1 kernel up-to-date with Nvidia's 3.1 kernel.
Why?
1) It'll be, put simply, "better" than Google's out-of-date kernel (...potentially)
2) This *must* be completed before work on 3.4 goes ahead
3) Hopefully other kernels, such as franco's, could be merged with this
How?
I did a "git rev-list" of Nvidia's branch, then Google's branch, all the way back to the point where Google added grouper support (Around March 2012), then diffed the result. I've attached the files in this post: The commits in the diff which have a + next to them are Nvidia's commits, as these are not present in Google's log. I simply need to cherry-pick all 1,699 of these, and make sure to manually update the grouper board files exactly as Nvidia's dev. boards are updated (because of course grouper itself is not updated at all in Nvidia's source). Then I need to fix all the compilation errors. If I get through around 50 - 80 commits a day, and fix the compilation errors the next day, I should be finished in 2 months max. Then serious 3.4 work can begin.
Should I use it?
From a user's perspective, in all honesty, no. This is a) a WIP and b) a means to another end (3.4). Other offerings such as franco's kernel are so far more improved than Google's anyway that this will not be necessarily "better" than those simply due to a load of updates from Nvidia. What *will* make this useful is if the final product is merged, as I said, into existing kernels, thus improving those. That said, I'll never upload a new version before having tested it myself, so you can be in the very least assured that it'll boot and run.
HOWEVER it would be extremely useful if you could run this simply for testing purposes. All my trust is placed in Nvidia's commits and my own ability to fix conflicts and compilation errors. Things may go wrong and your help would be massively appreciated.
Shutupandletmeflash!!!
I'll post updates regularly as possible here. I've used agnostic as it's fantastic. The naming scheme is: Alpha whilst I'm still cherry-picking, Beta once that's done and we're testing to fix bugs, then RC once its in a stable, releasable state (there'll probably only be 1 RC, then no more work); The numbering is x.y where x indicates major release (0 is Alpha, 1 will be Beta) and y will be increment by 1 on every single release.
Credits
@sgt. meow
Nvidia
Google
Asus
@legolas93 for F2FS
@frantisek.nesveda for agnostic-kernel
Anyone else I've forgotten (sorry, it's a while since I opened the 3.4 discussion thread)
XDA:DevDB Information
linux-tegra-nv-3.1-grouper, Kernel for the Nexus 7
Contributors
HTCDreamOn, Ziyan, n1kolaa, sgt. meow
Source Code: https://github.com/Ziyann/android_kernel_asus_grouper
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2015-06-07
FAQ
Q: Why is TricksterMod/ CPUSpy/etc. Not showing 1300MHz?
A: read this post.
GREAT! :good:
Its great to see people giving attention to an old device.
I will look forward to it.
What you forgot me
You know moral support!!
Lol J/K
Good thing you put it in original development
That will help.
So keep up the... Hmm dont know how to express it....
Your doing an beyond awesome job!
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I'm sure we will get Android 5 one way or another
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/10/15/being-the-will-of-our-lord-duarte-the-nexus-7-2012-will-receive-the-holy-blessing-of-android-5-0-official/
frantisek.nesveda said:
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/1...ve-the-holy-blessing-of-android-5-0-official/
Click to expand...
Click to collapse
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I expect the kernel will be updated as it was for 4.4 from 4.3. I'm still carrying on with this, however, as of course the new kernel will still be 3.1.10. Then I can apply those updates on top of this.
P.S Did some more cherry-picking today. Mostly smooth, very few conflicts so far.
HTCDreamOn said:
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
Click to expand...
Click to collapse
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
Same here
the kernel should work with CM
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now Android browser is a pain with attachments, 0.1 will be tomorrow.
HTCDreamOn said:
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now.
Click to expand...
Click to collapse
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
USBhost said:
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
Click to expand...
Click to collapse
0.1 uploaded. Glad it works.
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Interactive has never ran good on my tablet no matter what kernal.
Sent from my Nexus 7 using Tapatalk 2
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Thanks for pointing this out, I hadn't noticed this before but it's happening to me as well. I seem to remember a commit affecting cpufreq scaling somewhere so this could be it, but it should be easy to fix. I might stock up these smaller problems and fix them right at the end to reduce conflicts, but if its simple enough I'll fix it soonish.
In other news, Alpha 0.2 has been uploaded (first post as usual) mostly just more commits picked, but we're starting to get to the good stuff: changes to tegra3 drivers etc. And some things I can use to update grouper board files :good:
Alpha 0.2 works well here.
Snappy for a stock kernel.
Only things to report:
Max freq is 1200 with all governors.
To turn the tablet on after sleep I have to press the button a lot.
Keep up the good work!!!
Agreed with alpha 2 running smooth same as above with frequency at 1200 keep up the good work looking forward to future updates
I just installed Alpha 2 on LiquidSmooth 3.2. After the first boot, I got multiple force closes on "com.android.acore" but after a reboot everything seems to work just fine. I will use it for the next days and report any bugs I encounter.
I just tried the alpha 2 on my tilapia running a clean install of CyanogenMod 2014-10-23. On the first boot everything is fine, but after a reboot I get SystemUI FC's everytime I unlock the device and it relocks again.
When I install M-kernel a69 or alpha 1 of this kernel, everything seems to be fine. I am using Data-F2FS, if it matters somehow.
I can post a logcat or kmesg tomorrow, right now I screwed up my hackintosh bad and it doesn't even boot, so I don't have a way to access adb.
The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918
This work is not mine but @elginsk8r. I do not know why it is not in the Samsung Galaxy Tab A Series section. But here you go guys who own Samsung Galaxy Tab A 8.0"
elginsk8r said:
For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
If you would like to contribute to Evervolv, please visit our Gerrit Code Review.
Current version: Based off 6.0.1 Marshmallow)
Features:
Extended PowerMenu
Battery %,
Volume button music control.
Trackball Wake (Available on devices with a trackball/pad)
CM Theme manager
ability to turn all customization off with one switch in the toolbox, giving you 100% aosp look and feel.
eng builds (instead of userdebug like everyone else) providing more open experience (ie adb root by default)
full complement of commandline tools (busybox, vim, ssh, curl/wet with ssl support!)
custom updater written from scratch by Preludedrew and Texasice, featuring automatic update checks,
support for downloading gapps, and advanced automatic install (TWRP and CWM supported but TWRP preferred)
Bug Reporting:
Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use EVPaste to post your logs.
Downloads:
Testing Build <-- Working Audio
Source:
Evervolv Github
Branch: mm-6.0
Changelog:
Nightly changelogs are available on download page (EVUpdater too!)
or you can view them at the Evervolv Gerrit
Donations:
If you wish to donate please do so here (Paypal)
Click to expand...
Click to collapse
These donations are not for me but for @elginsk8r
I do not maintain these roms so ask him if you need help!
I am currently working on a Cyanogenmod 14 for this device and it will be done by almost the end of the year or longer. Depends so hitting the Thanks button will encourage me to finish the Cyanogenmod rom faster and more accurately with dedication.
ParadoXGodzillA said:
This work is not mine but @elginsk8r. I do not know why it is not in the Samsung Galaxy Tab A Series section. But here you go guys who own Samsung Galaxy Tab A 8.0"
These donations are not for me but for @elginsk8r
I do not maintain these roms so ask him if you need help!
I am currently working on a Cyanogenmod 14 for this device and it will be done by almost the end of the year or longer. Depends so hitting the Thanks button will encourage me to finish the Cyanogenmod rom faster and more accurately with dedication.
Click to expand...
Click to collapse
Did you ask permission to post this?
There could be reasons why devs don't post their work for general public release in device forums.
Also if we are going to credit the rom then the original author @deadman96385 should be recognized.
ashyx said:
Did you ask permission to post this?
There could be reasons why devs don't post their work for general public release in device forums.
Also if we are going to credit the rom then the original author @deadman96385 should be recognized.
Click to expand...
Click to collapse
@deadman96385 didn't make this rom, he made a rom for SM-T550. @elginsk8r made SM-T350. Also, the rom was posted before there was a Samsung Galaxy Tab A Series forum.
ParadoXGodzillA said:
@deadman96385 didn't make this rom, he made a rom for SM-T550. @elginsk8r made SM-T350. Also, the rom was posted before there was a Samsung Galaxy Tab A Series forum.
Click to expand...
Click to collapse
I think you'll find the original sources are from @deadman96385 repo.
Irrespective of that it's still prudent to ask the current developer for permission.
ashyx said:
I think you'll find the original sources are from @deadman96385 repo.
Irrespective of that it's still prudent to ask the current developer for permission.
Click to expand...
Click to collapse
No, the original author is me, deadman and i ported both devices at the same time using evervolv sources.
But this kid did not ask for permission, so could the mod close this thread?
elginsk8r said:
No, the original author is me, deadman and i ported both devices at the same time using evervolv sources.
But this kid did not ask for permission, so could the mod close this thread?
Click to expand...
Click to collapse
Sorry for posting this thread without permission. But anyways I am not a "kid". That is very rude if you think of it in my perspective.
ParadoXGodzillA said:
Sorry for posting this thread without permission. But anyways I am not a "kid". That is very rude if you think of it in my perspective.
Click to expand...
Click to collapse
I wouldn't take it personally. It's just a term to describe someone, I don't think elginsk8r actually meant you were a kid. [emoji6]
ashyx said:
I wouldn't take it personally. It's just a term to describe someone, I don't think elginsk8r actually meant you were a kid. [emoji6]
Click to expand...
Click to collapse
Ok. Thanks for the clarification.
Would have been awesome...
Sent from my SM-T350 using XDA Premium HD app
Well I went ahead and tried this build anyways and it boots fine. Video and audio is working. It's a bit sluggish at times but I think that could be solved with A little work on the kernel. As long as I didn't over do it with the apps installed it ran very nicely though. I really hope that the original dev (who is a genius in my mind) keeps working on this port. I would be more than willing to do the testing and am used to logcats. Just let me know. And thank you for sharing.
i tried this the other day and i like it. but there are a couple of bugs that i found. when installing Gapps Google Music stops working on boot which i removed because i don't use it anyway. And no cameras work on it at all. all apps fail to load camera. other than that i like it. i hope someone works on this more or makes newer roms for this device.
itz me ry4n said:
i tried this the other day and i like it. but there are a couple of bugs that i found. when installing Gapps Google Music stops working on boot which i removed because i don't use it anyway. And no cameras work on it at all. all apps fail to load camera. other than that i like it. i hope someone works on this more or makes newer roms for this device.
Click to expand...
Click to collapse
I will be keeping my fingers crossed too. This is a good tablet. I picked up the Tab 3 t110 last year around Christmas and it too has almost no development. At least this tab has a ported CM based rom to tinker with. A good stock rooted rom would be nice too. I will be watching this thread to see if it goes anywhere.
Sent from my SM-T350 using XDA Premium HD app
glockman4519 said:
I will be keeping my fingers crossed too. This is a good tablet. I picked up the Tab 3 t110 last year around Christmas and it too has almost no development. At least this tab has a ported CM based rom to tinker with. A good stock rooted rom would be nice too. I will be watching this thread to see if it goes anywhere.
Click to expand...
Click to collapse
Yea it would be nice for development on this. I have a stock rooted ROM that I rooted my self, I debloated it installed Xposed frameworks and Magiskv9. And it runs great.
itz me ry4n said:
Yea it would be nice for development on this. I have a stock rooted ROM that I rooted my self, I debloated it installed Xposed frameworks and Magiskv9. And it runs great.
Click to expand...
Click to collapse
Can you upload your debloated rom?
itz me ry4n said:
Yea it would be nice for development on this. I have a stock rooted ROM that I rooted my self, I debloated it installed Xposed frameworks and Magiskv9. And it runs great.
Click to expand...
Click to collapse
That is what I am looking for too a zip of the stock rooted firmware. I can debloat it myself but its the zip that I wish I knew how to get or make.
Currently running Evervolv on my t350. Over joyed to have found a Rom and development on this device, I had lost hope for it. Thanks to everyone especially the dev.
I finally got this ROM to run very smoothly and everything is working as it should. Camera, videos, audio and Bluetooth all working. About the only thing that isn't that great is battery consumption but I think as the rom settles in it may get better. I hope that the original dev decides to officially support the t350 with his build of Evervolve. So far so good. Even the theme engine worked flawlessly.
glockman4519 said:
I finally got this ROM to run very smoothly and everything is working as it should. Camera, videos, audio and Bluetooth all working. About the only thing that isn't that great is battery consumption but I think as the rom settles in it may get better. I hope that the original dev decides to officially support the t350 with his build of Evervolve. So far so good. Even the theme engine worked flawlessly.
Click to expand...
Click to collapse
the cameras and everything work on this out of the box, or did you need to do something to get them to work?
ratchetrizzo said:
the cameras and everything work on this out of the box, or did you need to do something to get them to work?
Click to expand...
Click to collapse
They worked without moding anything. But it wasn't an easy install... Lol.. I would add an app or two and let it go for a while. Doing it that way it worked great. The only issue was the battery usage. It wasn't good at all but if we had a kernel that would allow for tweaking, I think it could be tamed. Its a good start to having a ROM other than TouchWiz. : )
Please help me
I installed this custom rom and there is no google play services or nothing. just audio fx, calculator, chromium, clock. contacts, documents, downloads, email, gallery, music, settings and themes. No google anything. Please link me or tell me how to find the google play services version that i need, will be much appreciated thanks in advance