Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU installer
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash Superuser zip
Reboot
Thank you for choosing codefireXperiment,
Yippee! First AOSP build with fully functional IR Blaster! I use the HTC implementation so any IR control app must use the HTC IR api. I tested with this app.
http://forum.xda-developers.com/showthread.php?t=2271113
Blaster mode and Learn mode are fully functional and stable. This is the first non-Nexus device I've done AOSP on so bear with me for a bit. The build is rock solid stable and I dare any build to try and out-benchmark me ;D
one more for good measure
This is truly a wonderful suprise!!
This is truly a wonderful suprise!!
Welcome bigrush!
This sounds cool! Thanks for the hard work. Im gonna give this a shot tomorrow.
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Are the APN for ATT in this ROM or do I have to put them in myself
Sent from my HTC One using Tapatalk 2
Does cfx have the same janky animation and sluggishness of other AOSP roms for the One when compared against a Sense or GE ROM?
If anyone could fix aosp/optimize for device specific hw on non-nexus devices its you.
Sieze said:
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Click to expand...
Click to collapse
I'm getting this same error too. Anybody know what's up yet? Probably something simple lol
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
bigrushdog said:
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
Click to expand...
Click to collapse
im using CW touch 6.0.3.3
running a backup atm but once finished il flash TWRP and see if it works.
Ok. So it fails to flash on cw then?
bigrushdog said:
Ok. So it fails to flash on cw then?
Click to expand...
Click to collapse
yup. it flashed with out a hitch on TWRP...
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
bigrushdog said:
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
Click to expand...
Click to collapse
well initial response to laying my finger and moving it on the screen. amazing. i didnt think id feel or tell much a difference in response. but holy S#!7 so smooth and stuff happens when its supposed to aka as soon as i touch the icon its open...
(ノ^_^)ノ also the boot animation is pretty frickin sweet.
also the benchmark has me drooling.
Quadrant Standard: 6749
also im really frickin liking this ROM
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
bigrushdog said:
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
Click to expand...
Click to collapse
well hey credits due where its earned right? but yea im still crappin my pants at how there is absolutely no lag at my finger tip.
Hands down the best android experience ive ever had. i can trully feel the power of my device in my hand in all its glory.
Grab that IR app and program your TV man. Dude dropped source for the app so maybe I'll do some IR toggles or something
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
mikexmayhem said:
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
Click to expand...
Click to collapse
Flashed with twrp. Still gave error but said successful. After reboot everything looks just fine. Great ROM!
Related
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
danial.aw said:
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
Click to expand...
Click to collapse
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Ya I did message him... Unfortunately I believe he is busy
[r.]GimP said:
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Click to expand...
Click to collapse
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
SnowLeopardJB said:
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
Click to expand...
Click to collapse
Stuff like this keeps schooling me every day, brain starting to hurt
That being said, I setup an Ubuntu environment earlier today, from one of the guides in chef central, using 12.04 64bit, got all the packages, but i'm terrified to sync a potential 10 gigs of stuff, what exactly should i be syncing to on github for our device, and say for illusion rom to try building from source?
and as I side project today, I nearly got a zte x500 to take a custom rom and recovery from the stock recovery, after noticing ZTE signed their packages with the test keys, just needed to figure out the mmcblk for recovery for the cricket score <edit> I know the syntax that particular updater script needs now, but dont have access to the phone til monday. the person is getting a new phone anyway but it's my pet project to flash a custom rom and recovery from the stock recovery and good practice doing updater-scripts from scratch </edit>
Been a fun day.
danial.aw said:
Ya I did message him... Unfortunately I believe he is busy
Click to expand...
Click to collapse
I am not "busy" haha, just on vacation without my computer out of country
Ahh well hope you have fun and get back to your computer soon times lol
Hey Morris any chance you are back and kicking?
morrislee said:
I am not "busy" haha, just on vacation without my computer out of country
Click to expand...
Click to collapse
Just checking, would it be possible for you to make an inversion patch for your hybrid modem?
So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Darian_A said:
So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
Click to expand...
Click to collapse
Only if HTC, Qualcomm, and Texas Instruments provide the corresponding updated sources for development. Otherwise what few developers that are left here will still be banging their heads against the wall to port it.
Darin_Ram said:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Click to expand...
Click to collapse
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
KT-82166 said:
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
Click to expand...
Click to collapse
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Roms
Darin_Ram said:
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Click to expand...
Click to collapse
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Sense Jellybean...
Once we have sense Jellybean, the next working will be KitKat.
We are very close to having the very first Sense jellybean rom
4.3 roms
The evervolv rom is currently the best "4.3" rom for the Amaze. Found here: evervolv.com/devices/ruby.
Although, the mobile data is very choppy. It will connect but it's seems to when it wants. Not sure about the intricacies of that. But, a bit of a dealbreaker for me at this point. The good news is evervolv has been updating this rom with
tweaks and bug fixes everyday. So, it looks very promising. Also note, I have found an "unofficial" cm10.2
build by sportsstar89 but the sound does not work. If you search 'ruby' on goo.im you will find it. I would post a link
but the site seems to be down atm. I am currently running cm10/1006-nightly, what i've found to be the best jelly bean
rom at this point. There is also an unofficial cm10.1 build that is pretty good as well. It can be found here: droidfirmwares.com/cm10-1-android-4-2-2-jelly-bean-custom-firmware-for-htc-amaze-4g.html/2. I ran it for quite a while w/o any noticeable
trouble. I just prefer official cm builds i guess.
Fadiayad said:
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Click to expand...
Click to collapse
I don't think you can get the keyboard on CM10 unless there's an app or someone made a port or something.
The snapshot feature works differently with Cyanogenmod cause they use the long press power button then selecting screenshot, though you'll have to enable the feature in the system settings.
Flip to silent the phone? Must be a feature I don't use lol
Idk, I liked the ICS stock tmobile (I de-bloated it myself using root uninstaller. Got rid of anything pertaining to t-mobile and it runs like a dream.)
Nenamark2 benchmark averages at 47 fps.
Antutu results are a little over 9000 (Let the Dragon Ball Z jokes start now lmao)
Overclocking is something that I would have loved to do on this stock rom, but I'll just run V6 Supercharger script instead.
Though pushing min. clock to about 1.2ghz gives a slight difference in benchmarks.
Hmmmmmm.......
It would take a lot of developer skills to get it on this device. CM said if they didn't officially support the device before, they won't start now regardless of ram specs. The s4 has it, but even better there is a dev for the international s4 that has made a 4.3.1 ROM which is made up of 85% straight Google source with 15% cm commits to get it to work on our device. And IMO, aosp is better and more stable than cm10.2 and has way less lag.
Sent from my GT-I9505 using Tapatalk
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
from what i have seen and heard kit kat will be better on amaze
Darian_A said:
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
Click to expand...
Click to collapse
Unfortunatelly jeepers007 bricked his device
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
chevycowboyusa said:
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Odysseus1962 said:
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Click to expand...
Click to collapse
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for you comments, now I fully understand your dilemma. The issue isn't just getting a working JB ROM, it's getting a working JB/sense ROM. You see I'm sense agnostic. My HD2 had sense with windows, but all of the best android ROMs for it were aosp or cm based, so I got used to not having it. Now I've got it again with the nrg ROM so I use it. When I ran Tytung's cm ROMs I always customize anyway. To me cm or aosp is like having a blank canvas to paint on. You have the basic features, but It's infinitely customizable to taste. Sense gives a different platform. You can still customize, but It's not as flexible to customize as aosp or cm. In a way it's factory customized. Either way I'd just love to see a fully functioning JB on our devices. Please keep up the good work!
Ciao
I've asked somthing in above post..
Can anyone reply please... I want to start my work though....
Sent from my Amaze 4G using xda app-developers app
shubham211995 said:
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
I'm not the most experienced but from my knowleged you should be ok as long as you watch what partitions you format.
Sent from my HTC_Amaze_4G using xda app-developers app
Hello this thread is intended for development purpouses only. Do not post thank you posts, request posts or anything not related to the main purpose. You have a thanks button if you are thankful.
Well warching at what lg did with kitkat using bad jb blobs for gpu that resulted in abnormal cpu usage for rendering and in slowness and glitchness I decided to set up Team Neutron. This team will build a working cm10 that is smooth which is possible.
Well now anyone with abilities can join after i talk to them. Not here on topic but after they pm me.
Atm i would want to know if the following people will join me withoit egos secrets or drama. I will split iobs and watch over the project. I will work on it myself.
Kernel
@airidosas252
Rom dev from source
@weritos
Please confirm or infirm my invitation. This could be my last project for this device since it has almost no support. It will be a good one though.
I understand correctly
Going to collect СM10 ??
We are gonna get a super stable cm 10 if you want to work with me
Sent from my LG-P710 using XDA Free mobile app
christi9503 said:
We are gonna get a super stable cm 10 if you want to work with me
Sent from my LG-P710 using XDA Free mobile app
Click to expand...
Click to collapse
This is certainly good
But for the models 715 to gather a working network will be problematic, СM10 not support two SIM cards
That is right but we are never going to get a stable cm11 because of the gpu. We can make 1 sim work i think
Sent from my LG-P710 using XDA Free mobile app
Edit: @weritos
The best we can get is a JB based rom like CM10.2 at most. After we get the single sim working we can patch somehow for the P715 to use one sim (some ramdisk tweaking).
What I am thinking off:
let's pull the blobs only from our phone. See if we can get it running. We analyze the log and see what are we missing then add them 1 by 1 (this will give us maximum stability that can be attained).
let's remake that device tree with only the 100% necessary things and we can always add up on top of that. Let's not take TeamHackLG base. Of course we will use the 7x27a settings (SoC's are almost the same). Well, the best thing is to make some display things for our own 8225 socket. It will take a while but all we need is in our kernel. We can focus on this later to improve the stability even more.
Well. Our first goal is to make it boot using ONLY the blobs from our device + the GPU drivers I managed to obtain (they are optimized for JB). After we get that working we should worry about other things. Kernel should be modified just to boot (in the first stage). After we get a fully working device (RIL, WIFI etc) we can work on a better kernel, optimization, overclock, deep-sleep and everything we want. I also watched in the LG Ramdisk (from stock). It's a bunch of garbage half of it could be deleted. Well I am pulling the blobs tonight, download cm10.2 source and let's get to work my friend. Imo we should focuse on the boot first. Ofc if you have any opinion I am always to open it and if your idea turns to be a better one (since none is perfect) we will go for that.
EDIT2: There is a fetch error in cm10.2 let's try with branch jellybean.
christi9503 said:
That is right but we are never going to get a stable cm11 because of the gpu. We can make 1 sim work i think
Sent from my LG-P710 using XDA Free mobile app
Edit: @weritos
The best we can get is a JB based rom like CM10.2 at most. After we get the single sim working we can patch somehow for the P715 to use one sim (some ramdisk tweaking).
What I am thinking off:
let's pull the blobs only from our phone. See if we can get it running. We analyze the log and see what are we missing then add them 1 by 1 (this will give us maximum stability that can be attained).
let's remake that device tree with only the 100% necessary things and we can always add up on top of that. Let's not take TeamHackLG base. Of course we will use the 7x27a settings (SoC's are almost the same). Well, the best thing is to make some display things for our own 8225 socket. It will take a while but all we need is in our kernel. We can focus on this later to improve the stability even more.
Well. Our first goal is to make it boot using ONLY the blobs from our device + the GPU drivers I managed to obtain (they are optimized for JB). After we get that working we should worry about other things. Kernel should be modified just to boot (in the first stage). After we get a fully working device (RIL, WIFI etc) we can work on a better kernel, optimization, overclock, deep-sleep and everything we want. I also watched in the LG Ramdisk (from stock). It's a bunch of garbage half of it could be deleted. Well I am pulling the blobs tonight, download cm10.2 source and let's get to work my friend. Imo we should focuse on the boot first. Ofc if you have any opinion I am always to open it and if your idea turns to be a better one (since none is perfect) we will go for that.
EDIT2: There is a fetch error in cm10.2 let's try with branch jellybean.
Click to expand...
Click to collapse
That's a great idea, but first you should try CM10, 10.2 will be very slow on this device, since it is using hardware much more, and it is slower compared to CM10. But that's just my opinion.
True. @shiftyHungary: well after researching it seems cm10.2 is more optimized and from what I am seeing the most stable version of cm for 7x27 is cm10.2 we should work with that imo. There is a sync error because there was some fights over some source. will be fixed easy by replacing in repo with the path that it's used for cm11 or jsut delete that repo. Don't know which one yet. Researching.
Sent from my LG-P710 using XDA Free mobile app
Wow, it's a good new!! Thank you Chri.,
Sent from my Xperia M2 LTE using XDA Free mobile app
christi9503 said:
True. @shiftyHungary: well after researching it seems cm10.2 is more optimized and from what I am seeing the most stable version of cm for 7x27 is cm10.2 we should work with that imo. There is a sync error because there was some fights over some source. will be fixed easy by replacing in repo with the path that it's used for cm11 or jsut delete that repo. Don't know which one yet. Researching.
Sent from my LG-P710 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, you know that better than me, I just shared my experience with my previous devices. Pm me if any help needed.
Well yeah. I really want CM also. I made my own version of CM11 it's smoother than the one we have but still mile away from what it should be even with hard-core optimization because CPU is too high because of the CPU. @weritos ->much respect to this guy, though I disliked some of the things were handled, I give props to him and I am thinking it's a good opportunity to work together and share idea with him (none has nothing to lose). Yeah cm11 will not be our deal and all the graphic glitches in games and stuff it's not because weritos CM11 it's because of LG being LG... With Cm 10.2 we have a way better chance (this came to my mind when actually trying to fix AOKP Ril problem which was based on CM10). I could feel the full powa!!!. Cm copiled GOOD from source will be butter (not in games and stuff ofc it's and Adreno 203 after all) smooth at least in UI and current day-by-day operations.
CM10.2 from the source code
christi9503, As soon as I pass all my exams
I redid the device tree under CM10.2, alter and drop provider (use LG)
But I tell immediately there will be problems with WiFi, Network
Well we can solve problems if we work rogether mosr likely. Best of luck with your exams. I am finishing blobs tonight and i made like half of the device tree. Tonight or tomorrow i will look in the ramdisk and will delete all that is useless
Sent from my LG-P710 using XDA Free mobile app
Well @weritos. Blobs are done (didn't pull the GPU ones since I will be using the ones I have found). Device tree is not fully done but it will be. I am building right now the first build. Using display CAF so it will take a while to get caf to work.
Edit: I will learn to use github and push repos there. Easier to work.
Cristi,
For now, use stock Kitkat kernel sources (just compile them using GCC 4.6 and you're good to go)
Because, once we modified stock kernel for certain things to work, like Wi-Fi, I can duplicate those and merge with my own customized kernel.
I'll work my ass off at my own kernel tonight, since I discovered certain problems.
Anyway, CM10.2 is a way better choice than CM11.
If Google didn't change whole lot of things in Kitkat, things would never have got that messy as it is now.
airidosas252 said:
Cristi,
For now, use stock Kitkat kernel sources (just compile them using GCC 4.6 and you're good to go)
Because, once we modified stock kernel for certain things to work, like Wi-Fi, I can duplicate those and merge with my own customized kernel.
I'll work my ass off at my own kernel tonight, since I discovered certain problems.
Anyway, CM10.2 is a way better choice than CM11.
If Google didn't change whole lot of things in Kitkat, things would never have got that messy as it is now.
Click to expand...
Click to collapse
Looking at the actual ramdisk kernel doesn't need modification for wi-fi to work. Same for RIL. Seeing as how it is handled we might be missing some bins or libs it'll be hard but it's possible to get ril with only our device files. This company called LG is just ****ing with us. Working on ramdisk for over 1 hours. There are A **** LOAD of duplicated files, obsoled, not used files. Working on it.
christi9503 said:
Looking at the actual ramdisk kernel doesn't need modification for wi-fi to work. Same for RIL. Seeing as how it is handled we might be missing some bins or libs it'll be hard but it's possible to get ril with only our device files. This company called LG is just ****ing with us. Working on ramdisk for over 1 hours. There are A **** LOAD of duplicated files, obsoled, not used files. Working on it.
Click to expand...
Click to collapse
And for those reasons I started to mistrust them as a company.
Good thing there are other devices, which really do the helping out.
Anyway, CM10.2 will be easier to get working on our device than CM11.
airidosas252 said:
And for those reasons I started to mistrust them as a company.
Good thing there are other devices, which really do the helping out.
Anyway, CM10.2 will be easier to get working on our device than CM11.
Click to expand...
Click to collapse
The mess they made. They just dirty patched mostly anything. My last LG device for sure.
Sometimes I am really thinking what big companies think. Another update. Sometime there is echo on what you are talking and stuff (like you hear your voice if you talk in the mic). It is because LG doubled some uevents or even tripled them. So they get inited like 3 times. This might solve the mic problem forever also.
airidosas252 said:
And for those reasons I started to mistrust them as a company.
Good thing there are other devices, which really do the helping out.
Anyway, CM10.2 will be easier to get working on our device than CM11.
Click to expand...
Click to collapse
WiFi will not work immediately
Rild will not work
weritos said:
WiFi will not work immediately
Rild will not work
Click to expand...
Click to collapse
We will work that out my friend. Better if it takes 1 week or so to fix just 1 problem than making a messy fix and having instability and stuff. Quality over quantity. In the end that is the best combo.
Amyway, how everything is moving?
Wi-fi isn't a big deal breaker. We'll fix it, as well as RIL.
And we should avoid using modules.
Sent from my LG-P710 using XDA Free mobile app
[KERNEL] Starship-Kernel The Next Generation Stock/AOSP & CM-13 04/25/16 (Linaro 4.9)
Welcome to Starship Kernel The Next Generation (TNG) for the Nexus 6 Shamu. Not much else to say other than more than ever the Kernel is by design light wait, power efficient and moves at Warp Speed. There are no special features to play around with but instead designed to just be installed and just work. If looking for things to play around with may as well just move on as this is probably not the kernel for you.
Have shed some light on a few names below but really need to thank all the Nexus 6 Kernel Developers as could not have done much of anything without them. Before this project I had limited Kernel knowledge. Have been developing since I guess my first Rom had been CM6 based but never had much Kernel dealings. Have always worked joining up with a team to get CM or other AOSP like Roms up and running on TouchWiz,. Sense and other devices far from the Stock Android Experience. In working in groups and teams have for the most part always been the Device File & Vendor Blob guy. Everything I have learned about Kernels has honestly come from sifting through other Kernels and researching the hell out of out of commits until being able to stand on my own 2 feet and think so far have done a dam good job putting together a hell of a Kernel for the Nexus 6 that is extremely stable and performs well beyond expectation besides the big ol Jinx I just through out there.
This is now the new and improved Next Generation moving from say warp 6 to warp 9. Would say 10 but some funky stuff goes down at ten and if you dont know lets just say its not a place you wana go.
Definitely need to throw up thanks to Flair2, Imoseyon and Neoboddy89 as have used a decent amount of their commits in particular..
Features Worth Noting
Have placed features into either groups or single commits that make rather large improvements but are welcome to sift through the Kernels Commit History below as there are many individual changes to numerous to mention in a single post or even page . As mentioned most come from just sifting over and reading commits from every Kernel I could find. Most from Shamu but also some carefully selected from other devices with similar hardware
Kernel Version 3.10.101
Fast USB Charging
LZ4 Compression
Sio & Bfq i/o Schedulers - "bfq" used as default scheduler
ExFAT Support
Power Efficient Workqueues
KGSL Optimixations
Audio Codec Optimizations
Video Firmware Optimizations
CPU Idle Optimizations
GPU Power saving Optimizations
Adreno_Idler
Color Temperature Interface Using PCC
Frandom Support
LED Support (Rom must also Support)
MSM Vidc: Optimizations
Net: Wireless Bcmdhd, Various Optimizations
PM Enhancements.
F2FS 3.10
Starship Kernel, Nough Said!!
Source / Commit History aka change log
https://github.com/Chairshot215/starship_kernel_moto_shamu/commits/mm-mr1?page=1
Download Starship-Kernel_Class_SMTNG7_(Linaro-4.9) (04.16.2016)
Marshmallow 6.0.1 Stock/AOSP
https://www.androidfilehost.com/?fid=24499762636007231
CM-13.0
https://www.androidfilehost.com/?fid=24499762636007230
Again I am not responsible for any negative effects using any of the files on this thread or any post that has been linked in this thread so using is all at your own risk.
seems like nexus 6 development just blew up with new ROMs and kernels, thank you pal
Sent from my Nexus 6 using Tapatalk
Yup!
Does this kernel bypass force encryption?
Team Octos -Nexus 6
force encryption is disabled in the r_2 boot.img but so far is still showing that my N6 is Encrypted. With that said have not performed the recommended factory reset when going from a force encrypted boot.img to one that is not.
System UI Crash
Perhaps I've misinterpreted the OP, but I seem to have a major issue. Assuming this kernel is meant for 5.1.1 AOSP builds, upon flashing the kernel and wiping caches I get System UI crashes that do not allow me to actually start Android... am I at fault here?
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
chairshot215 said:
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
Click to expand...
Click to collapse
An issue like this is usually directed at the ramdisk. You may want to look into moving to an any kernel installer instead.
Sent from my Nexus 6 using Tapatalk
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
ps000000 said:
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
Click to expand...
Click to collapse
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Took me for a loop when Google started using the Teal coloring I was using for a few versions.
calaeb08 said:
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
chairshot215 said:
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Through me for a loop when Google started using the Teal coloring I was using for a few versions.
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
Click to expand...
Click to collapse
I myself know nothing about developing roms or kernels, that's why I'm here to ride on the bus with the smart kids lol. I do know that you can just leave it the way it is, but you gotta let people know it's forced encryption so they don't have to start all over. They can flash that zip that disables it before booting up.
What's the point of a sig anyways?
Well Definitely it for Lollipop, Probably. One thing that bothered me moving from the N5 to N6 is my BT Headset sounded like a warped and scratched record. I had lucked out with that pair in that had been reasonable priced and sounded amazing previously. Have added a few choice commits, well almost 2 pages but the things work like a charm. Decided for that and a few other reasons for one last post until 6.0.
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
NolenUmar said:
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I actually am still receiving emails about the Victory. Not that I could ever return to either the screen size or Touchwiz but wish I still had the device. Still feel like that SOB defeated me. Had been I think the 3rd device I worked on developing from the CM source and was so dead set on doing everything crazy proper so it could be an officially supported device. Wish I still had the device as do not like the feeling of spending countless hours on something and then leave unfinished. Think in the end all but GPS, Camera and that dang reboot when switching from Wifi to LTE. Think I used the Apexq as a template for getting everything else going. Otherwise wish the community luck. The phone was nice for the Price just a shame it has been years and everyone is still stuck on Stock with last I checked a bunch of out dated Kernels. Anyhow thats my Victory, rather defeated Rant. Remember at one point had got so frustrated used some command I don't remember off the top of my head and a lib decompiler and made the below list of all the files and their dependencies when trying to put together a vendor blob list.
http://pastebin.com/SFyJ14kv
Whats crazy about just pulling up this list is that I see the creation date was todays date but in 2013. Just had to mention that SOB device. Now I’m all worked up, lol.
Updated the M Kernel to r1.2 as works fine with SuperSU 5.1
This is an Encrypted Kernel. Will probably change with next update but for now it is Encrypted.
Now 2.0 with a few optimizations. Forgot about encryption but again looking for next update,lol.
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
calaeb08 said:
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
chairshot215 said:
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
Click to expand...
Click to collapse
You'd probably be better off using hellsgods anykernel scripts. Though, I'm not sure why yours isn't working to disable it. Theres also a fed patcher that should fix it. It kinda defeats the purpose of anykernel if your replacing files in the ramdisk instead of editing them.
Sent from my Nexus 6 using Tapatalk
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
You'll need to mess with:
/sys/devices/system/cpu/cpu0/core_ctl/min_cpus
/sys/devices/system/cpu/cpu0/core_ctl/max_cpus
/sys/devices/system/cpu/cpu4/core_ctl/min_cpus
/sys/devices/system/cpu/cpu4/core_ctl/max_cpus
It takes integer value ranging from 0-4. 0-4 meaning how many cores you want online per cluster.
The only issue is that I don't have /core_ctl directory that you've specified, I don't recall ever having it on this ROM, though I could be wrong. I'm using the krexus ROM in case I hadn't specified before.
I know, reading the stock ROM forums I got very excited to see the before mentioned information that was posted only to see that said (/core_ctl) directory was missing from any AOSP ROM I had used. This is the one thing that is holding me up from giving up my Windows phone as my business phone (the lag as a result of only being able to use 4 cores is intolerable in my line of work) even giving a link to what all these directory files mean would be very helpful. Thanks.
You could google what those directory means and that would give you that answer.
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
tboned82 said:
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
Click to expand...
Click to collapse
You may be needing a custom kernel to achieve this successfully.
Sent from my honor 5X using XDA Labs
adriansticoid said:
You may be needing a custom kernel to achieve this successfully
Click to expand...
Click to collapse
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from achieving the CPU control I'm after, but not sure if it's the only thing at play when it comes to this issue.
tboned82 said:
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from doing this, but not sure if it's the only thing at play when it comes to this issue.
Click to expand...
Click to collapse
Have you joined the beta channel of Blaze in Telegram?
adriansticoid said:
Have you joined the beta channel of Blaze in Telegram?
Click to expand...
Click to collapse
I have not, but would be very interested, what is Telegram?
tboned82 said:
I have not, but would be very interested, what is Telegram?
Click to expand...
Click to collapse
It's a messaging app. Just like Whatsapp, but with some diferences. You can check it in the Play Store. Telegram group link is in the Blaze kernel thread.
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
tboned82 said:
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
Click to expand...
Click to collapse
You didn't have screens of death?
Sent from my honor 5X using XDA Labs
tboned82 said:
didn't have pleasing results
Click to expand...
Click to collapse
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
Yeah the developer have not seen action the past few weeks.
adriansticoid said:
You didn't have screens of death?
Click to expand...
Click to collapse
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
adriansticoid said:
Yeah the developer have not seen action the past few weeks.
Click to expand...
Click to collapse
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
tboned82 said:
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
Click to expand...
Click to collapse
It's been that story for many developers man. A great project paused because life hit hard again. I believe he'll come back to it soon.
tboned82 said:
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
Drains battery like hell. Lol.
Sent from my Galaxy Tab 3 using XDA Labs
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
I had thought of doing this, though I don't see any cm 12.1 links in the Honor 5x thread, just 13, (though I'm at work at the moment and have to be stealthy about my research...errgghh Damn kids and their Snapchat) and I have to admit I've kind of fallen in love with the Krexus ROM and am apprehensive to flash another. Just need that hotplug support (and OTA updates would be nice as well