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.
Related
UnityROM-2 v.3.0.1
HTC Evo 4G LTE ( jewel )
Basic Overview
Source built Cyanogenmod 11.0 with a bucket of butter poured on top .
Compiled and Built with SaberMod GCC 4.8 Toolchains with a lot of optimization flags set.
BUILDTYPE = SNAPSHOT ONLY
(Not meaning only once a month or so like CM Inc.)
Aroma Installation.
Requirements:
S-Off, HBOOT 2.10+ & 4.13.651.4 Firmware Update to function correctly.
TWRP 2.7.1.0b , 2.8.0.x or 2.7.1.2 recoveries recommended.
NPL recovery though. That's the only catch here.
Purpose
Just trying to make a cleaner, faster, and generally more optimized build basically, without changing the ROM itself (apps & such). With some extra nice things thrown in even if there's is no visible difference in the ROM
Credits
@IAmTheOneTheyCallNeo for all of his help getting GCC 4.8 up and running finally. I owe you big man.
@Captain_Throwback for his original commits and help with the original thread & in this one as well.
@gruesomewolf for all of his help learning how to build a custom kernel.
Cyanogenmod Inc. & Google Inc. of course. For everything they do, way too much to try listing here.
LiquidSmooth for some additional build flags.
And please, if you like my work or the work others have contributed to this project, hit the thanks button. Thanks.
Features & Links
*** Global O3 & Strict-Aliasing=3 Optimizations & lots more ***
Full-Modular Aroma ROM & Gapps WITHIN the main package, yet still in separate directories.
Clean or Dirty ROM Flashing Options in Aroma.
Multiple LCD Density Options in Aroma.
System App Remover in Aroma.
Works with or without Gapps Installed
***UnityKernel-3.0.1 Features***
Optimized same as the UnityROM-2 only with GCC 4.9.
I/O Schedulers: SIO & FIOPS.
Governors: Intellidemand & Intelliactive.
LZ4 Compression/Decompression.
Current Release:
https://www.androidfilehost.com/?fid=95784891001602846
UnityKernel-3.0.0 Updater (includes previous 2.7.0 Kernel)
Current Release (UnityKernel Only):
http://d-h.st/KFr
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
**Sources current as of version 2.5.8**
**10/12/2014**
Direct link to UnityROM-2 Build Guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all, this guide is for you.
Downloading now. I just hope data worx
solcam said:
Downloading now. I just hope data worx
Click to expand...
Click to collapse
It does. Just don't mess with ART lol.
Fixing to give this a try... Wish me luck, lol!
Eager to try this.. waiting to reach home so that I can d/l it.
Also, bit curious, what happened to your other thread (I think.. Unity ROM1.0)?
I'm up and running. It's so smooth and haven't run into one problem yet. Loved the "easier" installation process and ability to customize installed apps.
[email protected] said:
Eager to try this.. waiting to reach home so that I can d/l it.
Also, bit curious, what happened to your other thread (I think.. Unity ROM1.0)?
Click to expand...
Click to collapse
It had a few names actually. Couldn't find a good one lol. It was just Project Unity by the end. What happened was I needed help doing something to make my ROM different from CM Official in some positive meaningful way and after banging my head against a wall basically trying everything I could think of to do this and after getting nowhere for too long I had the ROM taken down till there was a change like this.
But was noted as one of the most reliable AOSP/CM ROMs available for Evo LTE which is why I had to bring it back up with GCC 4.8 & O3 optimizations once I noticed the difference during my initial tests.
Wow. Thanks LiquidSmoke. This is by far the most stable 4.4.4 Rom that I have used so far. Data is working perfectly. I s on Dirty Unicorns 7.9 but, data was retarded, lol. They should take some notes from you. Again thanks for the BEST Kit Kat Rom available for our aging but still dope devices.
solcam said:
Wow. Thanks LiquidSmoke. This is by far the most stable 4.4.4 Rom that I have used so far. Data is working perfectly. I s on Dirty Unicorns 7.9 but, data was retarded, lol. They should take some notes from you. Again thanks for the BEST Kit Kat Rom available for our aging but still dope devices.
Click to expand...
Click to collapse
Well it's only getting better too. I'm adding in some more build optimization flags now. And once those are done I'm going to try of add the -fstrict-aliasing flag but that one is a real pain but worth the effort to get in there.
Could I update the nightly CM 11 builds on top of this ROM?
Indianvixen9 said:
Could I update the nightly CM 11 builds on top of this ROM?
Click to expand...
Click to collapse
I don't know why you would want to flash over this ROM with the official but I guess... Sounds dumb to me lol
I can't get "Ok Google" voice command to work on this ROM even though it is enabled from the Google Now settings. What can I do? I am almost certain that this has nothing to do with this ROM... but I thought I would give it a shot!
+1
not a hickup so far, data handoff excellent
Sent from my EVO using xda premium
Anyway possible u could make this exact same Rom for Sprint Galaxy S3 or show me how? This Rom is the sh*t and I could care less about ART working. As long as 3g works, I'm good. Thanks again LiquidSmoke.
Aloupha said:
I can't get "Ok Google" voice command to work on this ROM even though it is enabled from the Google Now settings. What can I do? I am almost certain that this has nothing to do with this ROM... but I thought I would give it a shot!
Click to expand...
Click to collapse
I managed to get it to work. I followed these steps:
1- I uninstalled Google Search using Titanium Backup
2- I reinstalled Google Search from the Play Store. At this point, saying Ok Google only works on the Google Now screen.
3- I downloaded and installed Google Now Launcher.
Voila! It works from the home screen and all the usual places where it should.
solcam said:
Anyway possible u could make this exact same Rom for Sprint Galaxy S3 or show me how? This Rom is the sh*t and I could care less about ART working. As long as 3g works, I'm good. Thanks again LiquidSmoke.
Click to expand...
Click to collapse
I could make a gs3 variant pretty easily. I think. I'd need you to be my tester if I do
I wish there was a way to get blinkfeed to work on aosp roms
Sent from my EVO using XDA Premium 4 mobile app
Welcome back. I thought the thread disappeared forever.
cirehawk said:
Welcome back. I thought the thread disappeared forever.
Click to expand...
Click to collapse
Nope. Was hoping you'd notice I got Project Unity 2.0 up. Was looking forward to your help if you're still down.
I got guides, build environment setup & build scripts now you name it. Just need a partner still. But that's nothing unusual lol.
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please Note:I do not have a Verizon Fascinate!!!! The closest thing I have is a Telus Fascinate 4G, which is essentially a Galaxy S 4G. However, this ROM has been built for (and tested on) a Verizon Fascinate.
Installation Instructions - Thanks Ophidian_DarkCore!
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?pli=1
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
1. Read "Things to take note of" below
2. Wipe system, data, and cache paritions (just in case)
3. Install zip
4. If you want root (SuperSU) or Gapps, install them now (or later, if you so desire)
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
The RIL (aka data, SMS, calls, etc) is NON-FUNCTIONAL.
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
Selinux is currently in permissive mode. I'm not sure whether or not it can be switched to enforcing without breaking things
The USB connection is MTP and not mass storage as Omni has removed mass storage. Unfortunately, it sometimes is super-duper slow. In recovery there is still an option to mount as mass storage device.
Live wallpapers are not present as this definitely qualifies as a low-ram device...
Tv-out support is not present. It was removed upstream and I don't want to bother adding it back in.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps slow down the i9000 and Galaxy S 4G significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
It boots!
Wi-Fi
Seriously, I'm not exactly sure what else works. I suspect that most other functions including Bluetooth and auto-brightness work but I'm not sure
What doesn't
RIL, cause I removed it...
Some of the soft keys (possibly fixed in latest build)
You tell me...
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Samsung Fascinate, ROM for the Samsung Fascinate
Contributors
xc-racer99, Ophidian_DarkCore, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: MTD Rom
Based On: OmniRom
Version Information
Status: Testing
Created 2015-08-01
Last Updated 2015-08-01
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to Ophidian_DarkCore for being the primary tester and prompting me to work on this project.
Thanks to hhp_211 for doing some testing and offering to send me a Fascinate.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P (my phone) and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch fascinatemtd"
Changelog
Changelog for 2015/08/01 Build
Untested!!!!!
TWRP fix (I think)
Totally removed RIL, prior builds have RIL there but its non-functional
Changelog for 2015/08/13 Build
Untested!
Encryption should now work
Keymapping (ie soft keys Home and Back) may be fixed
Changelog for 2015/08/31
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
SoD should be fixed...
Untested by me
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Gapps
Gapps can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
Thanks, I wasn't sure how you installed it. Will update OP.
xc-racer99 said:
Thanks, I wasn't sure how you installed it. Will update OP.
Click to expand...
Click to collapse
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Click to expand...
Click to collapse
OK, Only worked from the odin cwm.
I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.
1st impressions are wow!!
looks good and kernel has OC
and a few nice features.
Good work on all involved!
Installed beta SuperSU-2.49
Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*
Stable so far.
I'll test changing vm heapsize and LMK values
Also trying omni switch, but probably go back to asop recents as its using a lot of mem
oh and I'll check Big Mem settings too.
So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !
Later:
Gapps : I went very minimal install package,
Yes performance still takes a hit and I've also noticed some random reboots too.
I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.
As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.
I always disable that stuff even on my other/main phones.
.
i juse disableservice and autostarts for that stuff.
my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?
i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).
EDIT: "interactive(tweaked)" hispeed_freq?
edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added.
will new releases ?
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Godlovskiy said:
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Click to expand...
Click to collapse
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
it is noteworthy that in build from 30/07 this is not observed
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
OC didn't actually work in that build I think.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
xc-racer99 said:
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Click to expand...
Click to collapse
On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.
xc-racer99 said:
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
Click to expand...
Click to collapse
I can help you with bug reports,you just shoud tell me what I have to do
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://forum.xda-developers.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.
To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.
Collect logs during listview scrolling.
Let me know if the play store can install apps.
Ophidian_DarkCore said:
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
Click to expand...
Click to collapse
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
quickgiant said:
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
Click to expand...
Click to collapse
I also would be thankful if you would add 24 bit audio.
Thanks
xda_bg said:
I also would be thankful if you would add 24 bit audio.
Thanks
Click to expand...
Click to collapse
the frame size of 10 million exabytes is larger than my patience^2
http://i.imgur.com/eljXmhJ.png
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
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
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