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
Related
UPDATE
Due to unforeseen issues with this build and a plethora of people incapable of reading even simple notes, this release is being pulled while we work out some issues with our own internal testers.
Thank you.
Kernels. The final pain in the arse. These are the voyages of the dev team Ninphetamine. Our continuing mission, to break strange new code. To seek out new bugs and strange implementations. To boldly go where no phone has gone...before.
*cue musical score*
It's been some time since I last graced the Android community. Draped in the success of FroydVillain 1.5, empowered from my victories over Froyo's poor (and non existent) AOSP implementation for the HTC Hero, onward I charged into the task of dragging the ancient kernel of the Hero into the 21st century. However, after seeing how HTC are as likely to stick to recommended kernel practices as I am likely to win a Miss Universe contest, (This is highly unlikely and the least significant reason is that I am not female.) I buckled like a jet fighter made from tin foil and surrendered faster than an agoraphobic Frenchman. There has been some advances into more modern kernels for the Hero but as I predicted they're still plagued with issues, all of which can be blamed squarely on HTC.
It took some major rehabilitation to get me back into the Android development scene, a key factor in that rehab being the ownership of a Samsung Galaxy S. A delightful phone, still in my opinion the best single core Android phone that money can buy. Beautiful screen, fast, elegant and excellent on battery. It nursed me through those dark days of waking up in cold sweats with github commits circling through my head, kernel debug symbols blinking in the dark of the night like Vietnam flashbacks, breaking down into incoherent rants on IRC development channels ending eventually with "YOU WEREN'T THERE MAN, YOU JUST DON'T UNDERSTAND, HTC WILL COME AND GET YOU EVENTUALLY, THEN YOU'LL KNOW". Oh how I longed to find a high up HTC developer in a bathroom to blow them away before ending my own bitter misery. Alas, it was not to be.
After a successful tour of duty as a regular non developing user on the Samsung Galaxy S, I treated myself to a brand new and shiny Samsung Galaxy S II. As soon as I used the device and checked out the available source code for it, I knew I was ready, I knew I was fully recovered to be able to break free from the oppression of HTC, I knew that I was capable to step once more unto the breach and step back into Android development. The stage set, the orchestra struck...all that remained was to see if the Samsung Galaxy II could dance.
And dance it can. Accompanied by my trusty partner in crime netarchy (because this time if I go down in a gibbering wreck I'm damn sure taking someone with me) there is at last another phone with the magic, capabilities and horsepower to endure the test of time and upgrades, that like the Hero has carved out a niche of not only being the good of its generation but being the very best of its generation. Such hardware deserves only the best development efforts and here we are.
The best kernel for a phone that any human hand is capable of producing at this very moment in time. This will of course be rendered moot with the next release BUT RIGHT NOW, this is it boys and girls. Download it, flash it, use it with whatever ROM you wish (VillainROM of course for those with an IQ north of my shoe size) and enjoy the liberated freedom, speed and stability that those whoever owned a HTC Hero became accustomed to.
After much arguing with Samsung's inane practices, lack of logic, bizarre design decisions and enough harrassment via their support interface that I confidently expect a restraining order any day now, I bring you...
Ninphetamine version 1.0, the beginning.
Features:
Overclocking up to 1.6GHz. The phone is blisteringly fast at stock 1.2GHz so be happy you can push it to 1.6GHz. We will not provide higher, if you want higher then make your own.
Full voltage control interface. Via SetCPU you can set voltage as low as 800mV or as high as 1500mV for each speed in the database. If you're possessed with the intelligence of a baboon and destroy your phone as a result, do not come crying to us. All you'll get is a quote in this thread with much mocking from myself and your peers.
Patches and bug fixes up to and including 2.6.35.11. We're working on going up to 2.6.35.13 however the important fixes are in already. As well as some that never made it to 2.6.35.y -at all-.
Fully tested performance optimisations. This kernel comes with BFQv2-r1 IO scheduler enabled as default along with some tweaked parameters for this scheduler. These were painstakingly tested over many many many many many MANY different benchmark tests. These are the best. Anyone who claims otherwise or says that noop or deadline or CFQ is better, they're wrong. Why? Because I say so and I'm right.
A customised and trimmed down initramfs, including Clockworkmod. Many thanks to ogdobber for this who kindly gave me the template including ClockWorkMod that I took and further improved upon. All storage mounts are optimised for performance and data throughput, busybox is included as well as a much improved shell that by default provides tab completion even via adb shell. Please note that by default, adb is insecure, this means that adb shell, adb remount etc all work and give root access immediately.
So there you have it. Please download, flash, test and report any issues/bugs in this thread. I'll then either completely ignore the dumb posts or take on board constructive ones and use those reports/suggestions, incorporate them into the next version and then take all the credit.
Thanks to:
This release would not have been possible without the awesome and tireless work of netarchy, of Nexus S and Asus Transformer fame. Thanks also to ogdobber and supercurio for their assistance. Also thanks to mattgirv, Lenny, Rawat, Obihoernchen, geko95gek and Ante0 for being my guinea pigs for the many many test builds that were made before this final release, no doubt without them there would be a lot more bugs in this release than there already are. Also not forgetting of course, the everlasting patience of my wonderful wife, without which I never would have bothered picking Android up again at all.
Bugs/Issues:
Please of course report them in this thread, however before doing so, please:
Wipe dalvik.
Ensure you have no other OC software installed such as Tegrak. The only OC software supported by this kernel is SetCPU (or setting manually via command line of course).
Are you using a custom ROM? See if you still get issues with stock Samsung firmware or VillainROM. I cannot test with every single custom ROM out there, so I test with stock Samsung (naturally) and my ROM of choice.
If you're still having issues such as random hangs/crashes/reboots and if these issues still occur at stock speeds/voltages then please do the following:
Install the Android SDK if you have not already done so.
In a command window, do the following:
Code:
adb logcat > USERNAME-logcat.log
Then in another window:
Code:
adb shell cat /proc/kmsg > USERNAME-kmsg.log
Naturally replacing USERNAME with your name and make these logs available either via attachment or pastebin or whatever. Please do not paste them directly into posts as these logs can become quite large quite quickly.
Known Issues:
adb install <package> currently does not work.
Version 1.1
Changelog:
Some minor edits to the initramfs to fix adb install <application>.apk and a few other path issues. Loses the nice adb shell with tab completion, but fixes some issues. Download links updated.
Version 1.2
Changelog:
More initramfs changes to fix an issue with nandroid backups.
Making nandroid backups work again may have broken the "adb install" package install method, but I figure working nandroid and needing to push the apk to the phone to then install with Application Manager beats broken nandroids. I'll look further into the adb install issue later today.
Version 1.4
Changelog:
Some configuration changes to try and track down the random hangs/reboots people are experiencing.
Support for startup scripts in /system/etc/init.d added should ROM makers wish to use them.
Added debugging code, which prevents deep sleep in version 1.4, but makes crashes easier to diagnose.
FAQ/General Points
I hate Odin. It is a giant buggy piece of ****. Things can inexplicably go wrong for no other reason than Odin is a big heap of proprietary fail. Before reporting issues with the kernel, please either flash it with CWM or Heimdall. I highly recommend Heimdall, it will flash a jpeg to your kernel filesystem if you tell it to and somehow it'll boot anyway. I do all my testing with Heimdall so it's safe to assume that if I'm posting it, Heimdall will flash it. Heimdall also has the advantage of being open source and completely cross platform. Please take the time to download it and get used to using it, it will save you a lot of pain in the future.
This kernel has been tested with 2.3.3 KF2 and 2.3.4 KG1. There is no reason it shouldn't work with any ROM revision.
Somewhat amazing that I need to point this out, but you MUST FLASH THE KERNEL FOR THE VOLTAGE TAB TO APPEAR IN SETCPU.
Don't use tegrak with this kernel. DO. NOT. USE. TEGRAK. WITH. THIS. KERNEL.
The voltage that's adjusted is the CPU core voltage.
Major_Sarcasm said:
Just a FYI for those people that can't make logical connections; if you have Tegrak OC installed when you flash this kernel, you might end up with a boot loop. Go back to default settings in the app, then uninstall it before flashing.
Click to expand...
Click to collapse
More will be added to this post as the need arises.
pulled for now
SUPER !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Thank you !!!
netarchy said:
Use the voltage interface in SetCPU.
Click to expand...
Click to collapse
OOOO who is here!!! famous netarchy
Hacre said:
Reserved
Click to expand...
Click to collapse
Welcome. Will give it a try.
2.3.3, 2.3.4 ... all ok w this universal kernel?
EDIT: Great... I see you edited Post #2, and the answer is yes.
Thanks for the kernel. Does this have the multi-touch fix included?
jlevy73 said:
Thanks for the kernel. Does this have the multi-touch fix included?
Click to expand...
Click to collapse
I've not noticed an issue with multi-touch, of what do you speak?
*subscribes to thread*
netarchy said:
Use the voltage interface in SetCPU.
Click to expand...
Click to collapse
Okay maybe this is a dumb question, how do you undervolt using setcpu? I know I use it to underclock, and AFAIK it's different from undervolting. I've check the interface of setcpu just now trying to find undervolting options
mach0boi said:
Okay maybe this is a dumb question, how do you undervolt using setcpu? I know I use it to underclock, and AFAIK it's different from undervolting. I've check the interface of setcpu just now trying to find undervolting options
Click to expand...
Click to collapse
Make sure you're using the latest version, and use the voltages tab.
mach0boi said:
Nice! So how will you do the undervolting here?
Click to expand...
Click to collapse
Ummm...
Hacre said:
Full voltage control interface. Via SetCPU you can set voltage as low as 800mV
Click to expand...
Click to collapse
If only I'd mentioned it in the OP...
netarchy said:
Make sure you're using the latest version, and use the voltages tab.
Click to expand...
Click to collapse
Ooh okay i didn't knew there was such feature! thank you!
Hacre said:
Ummm...
If only I'd mentioned it in the OP...
Click to expand...
Click to collapse
I'm sorry maybe I'm just using an outdated version and never knew you could actually do that. Forgive my ignorance
sorry i am new to android so i do not know about undervolt or overclock, can anyone please tell me best combination of voltages on 1.6ghz that does not effect battery life?
ravian29 said:
sorry i am new to android so i do not know about undervolt or overclock, can anyone please tell me best combination of voltages on 1.6ghz that does not effect battery life?
Click to expand...
Click to collapse
The stock max voltage of the CPU is 1275-1300mV. Anything under this improves battery life, anything over this harms battery life from the standard "stock" expectations. Just like with a PC, not all processors are created equal. There is no setting for 1.6GHz that will not affect battery life as at best you'll need to increase voltage from the standard max setting. If you're not sure, use our defaults, these have been tested on two different handsets. There isn't even a guarantee that 1.6GHz will even work on your handset.
If you're not sure or are not confident, don't touch it. Any settings you set past 1.2GHz/1300mV are at your own risk, may damage your handset or even rip a hole in the space-time continuum, then you'll not only look an idiot with a broken handset but Stephen Hawking will be really pissed and you really don't want him trying to crush your toes in that tank he calls a wheelchair.
Best case scenario, try our defaults and only increase voltage in 25mV steps. If you find yourself a 1450mV and your phone still isn't stable then 1.6GHz isn't going to work for you. If battery life is your concern, then consider undervolting in 25mV increments at 1.2GHz or even 1GHz or 800KHz.
mach0boi said:
Ooh okay i didn't knew there was such feature! thank you!
Click to expand...
Click to collapse
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
@hacre cheers mate
umair9001 said:
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
Click to expand...
Click to collapse
In Settings -> About Phone what does the Kernel version show?
umair9001 said:
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
Click to expand...
Click to collapse
Yeah also checked it and I'm also using the latest version. Was about to ask this. Another question, is that voltage tab option kernel related? I'm using cfroot kernel and cannot find that damn voltage tab I'm using tegrak to undervolt. If I knew there's a feature like this in SetCPU, I should've not bought tegrak
Q&A for [ROM][5.0.2] OMNI - i777 [UNOFFICIAL] beta
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.2] OMNI - i777 [UNOFFICIAL] beta. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cyril279 said:
@coolerboyj, I just tried it. I turned off the wifi, then rebooted, and the device booted into android as expected.
I have not tried shift with Omni 5.0, but it should work well.
Click to expand...
Click to collapse
This rom does have random reboots when opening games, like Clash of Clans (works like 20% of the time)
I was wondering if there was a fix.
Thanks in advance
coolerboyj said:
This rom does have random reboots when opening games, like Clash of Clans (works like 20% of the time)[...]
Click to expand...
Click to collapse
MONSTERELLEVEN said:
i have had some random reboots and the call bug as you mentioned but other than that all is good.[...]
Click to expand...
Click to collapse
Regarding the random reboots, are you using the stock kernel?
cyril279 said:
Regarding the random reboots, are you using the stock kernel?
Click to expand...
Click to collapse
yes am using the stock kernel, didnt mess with anything at all
Good to know. I haven't experienced any of the random reboots yet, but I am not a heavy-user beyond a few utility apps, text, email, and calling.
I do know that there seem to be a considerable number of apps that work fine on 4.4 that exhibit undesirable behavior on 5.0. It isn't obvious whether the issues are app compatibility, or that our device tree isn't yet up to par, or that android 5 isn't yet up to par (or even all of the above).
MONSTERELLEVEN said:
yes am using the stock kernel, didnt mess with anything at all
Click to expand...
Click to collapse
cyril279 said:
Good to know. I haven't experienced any of the random reboots yet, but I am not a heavy-user beyond a few utility apps, text, email, and calling.
I do know that there seem to be a considerable number of apps that work fine on 4.4 that exhibit undesirable behavior on 5.0. It isn't obvious whether the issues are app compatibility, or that our device tree isn't yet up to par, or that android 5 isn't yet up to par (or even all of the above).
Click to expand...
Click to collapse
am not a heavy user myself but i think you are right about andoid 5 isnt ready yet, actually it reminds me exactly of mircrosoft and the transformation from windows 7 to windows 8
cyril279 said:
Regarding the random reboots, are you using the stock kernel?
Click to expand...
Click to collapse
Yes, the one thats provided with the ROM.
This ROM only claims to have the video recording bug.
I haven't tested it, but thought id give you the link.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-12-t2955551
DELETE
coolerboyj said:
This ROM only claims to have the video recording bug.
I haven't tested it, but thought id give you the link.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-12-t2955551
Click to expand...
Click to collapse
I think i9100 lollipop rom by @Lysergic Acid also doesn't have "No Sound issue on outgoing calls"
Can I flash omni using CWM recovery. I'm using shift kernel and cyanidel from @rogersb11.
pg1980 said:
Can I flash omni using CWM recovery. I'm using shift kernel and cyanidel from @rogersb11.
Click to expand...
Click to collapse
If you are using my kernel and the philz recovery that comes with it you can flash anything lol
My phone burns and reboot when I try to open some apps.
I need some help for this, I'm using OmniRom 5.0.2 lollipop unofficial and when I use the music player of the rom, my phone gets so hot and battery drains to fast, also reboot when try to use other apps from the play store like, youtube, etc... everything else works fine. I want to know if you are going to fix the other bugs like the outgoing calls, etc..??
BTW, thank you so much for your effort on this rom, i really like OmniRom and I hope you can make it better and keep GS2 alive
I have found that there are specific apps that cause the device to immediately reboot. I believe this to be mainly a result of the current memory issues regarding this device and Lollipop.
I haven't experienced any heating issues beyond the initial firmware settling (scanning the device) .
I hope to be able to find a solution to all bugs, but I cannot promise that it will happen.
JCPALACIOSG said:
I need some help for this, I'm using OmniRom 5.0.2 lollipop unofficial and when I use the music player of the rom, my phone gets so hot and battery drains to fast, also reboot when try to use other apps from the play store like, youtube, etc... everything else works fine. I want to know if you are going to fix the other bugs like the outgoing calls, etc..??
BTW, thank you so much for your effort on this rom, i really like OmniRom and I hope you can make it better and keep GS2 alive
Click to expand...
Click to collapse
@rogersb11,
I don't see anything onvious here at all. The call goes through, so it isn't even obvious which errors are relevant if any. Maybe you've already looked through one of these:
http://pastebin.com/z039Bktb
-Cyril
cyril279 said:
@rogersb11,
I don't see anything onvious here at all. The call goes through, so it isn't even obvious which errors are relevant if any. Maybe you've already looked through one of these:
http://pastebin.com/z039Bktb
-Cyril
Click to expand...
Click to collapse
Just seeing this, sorry. I'll pull it now, this call bug log?
Edit: I see that it is, hard to scan it well on my phone, I'll look once I'm at my computer. I updated audio stuff before my last build but no luck. I think using a prebuilt hwcomposer from kk would solve many many issues with video etc. That's what we did for n2 and we don't have official cm12 either. I need to pull a kk zip to get the hwcomposer and see how that works. Also I may need to build an i777 almost stock kernel with my n2 source because only my kernel on n2 will allow working everything hardware. My i777 kernel is based on cm but my n2 is Samsung kernel source 3.0.31 that has been routinely merged with aosp. Quick glance looks like audio isn't routing properly but I could be wrong. It's such a strange bug since it works just fine after flipping on and off. Again sorry for the delay, I seriously only get about 15% of the notifications I should
Yeah, this is the call log, and without something flagrantly crashing (and leaving a better calling card) I have nothing specific to look into.
No worries about the notification, I've been working on slim with warrior1208. ... Although until slim is back online, that project is almost stalled.
We'll have a proper daily driver if we can get this. I can't help but wonder if some of the "under the hood fixes" of 5.1 may help. Prolly just wishful thinking.
rogersb11 said:
Just seeing this, sorry. I'll pull it now, this call bug log?
Edit: [...] Quick glance looks like audio isn't routing properly but I could be wrong. It's such a strange bug since it works just fine after flipping on and off. Again sorry for the delay, I seriously only get about 15% of the notifications I should
Click to expand...
Click to collapse
cyril279 said:
Yeah, this is the call log, and without something flagrantly crashing (and leaving a better calling card) I have nothing specific to look into.
No worries about the notification, I've been working on slim with warrior1208. ... Although until slim is back online, that project is almost stalled.
We'll have a proper daily driver if we can get this. I can't help but wonder if some of the "under the hood fixes" of 5.1 may help. Prolly just wishful thinking.
Click to expand...
Click to collapse
Right now I currently despise 5.1 LOL. Not that it's bad but I have to start over if I want it. Hey, I remember you cooking your mobo awhile back, used to do it all the time but can't remember. What temperature and for how long did you do it? I wanna give it a go on MTT jtagged Xbox. It finally fried so figure might as well give it a shot, heat gun isn't working and my reball machine crapped out least year so I sold it to someone willing to fix it at the time
rogersb11 said:
Right now I currently despise 5.1 LOL. Not that it's bad but I have to start over if I want it. Hey, I remember you cooking your mobo awhile back, used to do it all the time but can't remember. What temperature and for how long did you do it? I wanna give it a go on MTT jtagged Xbox. It finally fried so figure might as well give it a shot, heat gun isn't working and my reball machine crapped out least year so I sold it to someone willing to fix it at the time
Click to expand...
Click to collapse
I used this procedure once to cook the mobo and it worked out for me. I was skeptical but it works:
http://forum.notebookreview.com/thr...-bake-your-gpu-for-fun-and-for-profit.437683/
Saved in the bookmarks
rogersb11 said:
Right now I currently despise 5.1 LOL. Not that it's bad but I have to start over if I want it. Hey, I remember you cooking your mobo awhile back, used to do it all the time but can't remember. What temperature and for how long did you do it? I wanna give it a go on MTT jtagged Xbox. It finally fried so figure might as well give it a shot, heat gun isn't working and my reball machine crapped out least year so I sold it to someone willing to fix it at the time
Click to expand...
Click to collapse
385 for ten minutes brought me success. For two different devices.
I noticed that 5.1 seemed to temporarily push asimovi's progress backward a bit, which is a part of why I haven't published a 5.1 Omni. I lost internal storage again, and haven't found the culprit. I keep forgetting to look into system_vold.
5.0 should have been a test release.
[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
Hi, I would ask if there is a very vanilla ROM (not CM), similar to stock, but without Google Apps
OpenAndroidUser said:
Hi, I would ask if there is a very vanilla ROM (not CM), similar to stock, but without Google Apps
Click to expand...
Click to collapse
I'm pretty sure you could flash AOSP itself. It's stock, but theres no Google apps.
Sent from my Nexus 6P using Tapatalk
http://forum.xda-developers.com/moto-e-2015/orig-development/caf-6-0-surnia-t3250165 this was the first pure AOSP Marshmallow ROM available, been using it for almost a year now & its 100% stable.
cmason37 said:
http://forum.xda-developers.com/moto-e-2015/orig-development/caf-6-0-surnia-t3250165 this was the first pure AOSP Marshmallow ROM available, been using it for almost a year now & its 100% stable.
Click to expand...
Click to collapse
Hey @cmason37, thanks for posting this as I'm always searching for those elusive MM 'Stable' Roms I would like to try that rom, however, the above link has been disabled. If you could repost the link that would be excellent.
In the meantime I'll scrub the world wide web for this file, thanks
Bm6
Sent from my XT1527 using XDA-Developers mobile app
BillyMumphry said:
Hey @cmason37, thanks for posting this as I'm always searching for those elusive MM 'Stable' Roms I would like to try that rom, however, the above link has been disabled. If you could repost the link that would be excellent.
In the meantime I'll scrub the world wide web for this file, thanks
Bm6
Click to expand...
Click to collapse
It works just fine for me. Are you visiting the link on your phone, or PC?
I'm on my phone right now. Thanks I'll go sit at the PC and try.
Sent from my XT1527 using XDA-Developers mobile app
BillyMumphry said:
I'm on my phone right now. Thanks I'll go sit at the PC and try.
Sent from my XT1527 using XDA-Developers mobile app
Click to expand...
Click to collapse
btw I wouldn't recommend it, I was trying it and it's preatty buggy and outdated. It doesn't have fm radio and it's using only bottom microphone for video recording (stock 6.0 uses both mics so there is stereo effect). It also doesn't support any new custom kernels because it wasn't updated for ages. The worst thing is that it slows down a lot after few days and you need to reboot. On stock 6.0 with squid kernel the performance drop wasn't that big, I was using it for 30 days without reboot and it was still pretty good.
iks8 said:
btw I wouldn't recommend it, I was trying it and it's preatty buggy and outdated. It doesn't have fm radio and it's using only bottom microphone for video recording (stock 6.0 uses both mics so there is stereo effect). It also doesn't support any new custom kernels because it wasn't updated for ages. The worst thing is that it slows down a lot after few days and you need to reboot. On stock 6.0 with squid kernel the performance drop wasn't that big, I was using it for 30 days without reboot and it was still pretty good.
Click to expand...
Click to collapse
I don't have any of those problems, except for msybe fm radio but I don't give a crap about that. But, I can flash squid kernel & I don't get performance drops often. So it's literally bug free for me. Maybe you should try flashing it again. After all, bad flashes happen.
cmason37 said:
I don't have any of those problems, except for msybe fm radio but I don't give a crap about that. But, I can flash squid kernel & I don't get performance drops often. So it's literally bug free for me. Maybe you should try flashing it again. After all, bad flashes happen.
Click to expand...
Click to collapse
I tried it for three times always with the same resoult ;/ btw I don't own this phone anymore.
iks8 said:
I tried it for three times always with the same resoult ;/ btw I don't own this phone anymore.
Click to expand...
Click to collapse
My apologies you guys for not getting back earlier. I've been fumigating for bugs.
Those issues you were describing are the exact issues I'm dealing with today on my current ROM a popular CM based true to form option-heavy, stability-light ROM. This is a shame as its been fairly reliable platform for me. The occasional issue that was easily remedied with a reboot, a restore or a reflash. The past few months have been bug after bug for me. Mostly a pesky incompatibility issue with my ROM and OpenGapps.
Its seems all I've been doing lately is testing alternative gapp pkg sources, kernels and mods.
What makes this issue the real tops though is that the ROM I use was just listed as "Official" and "Stable" last month. There may be a weekly update waiting in the basket for me but the basket build server is down.
So....?
Not sure where to go from here. I'll tell you this much though. When I decided to try and root this device 8 months ago I had no idea it involved so much. I can almost write my own svripts, I'm understanding the bugreports I generate and read and i haven't spent this much time in a ToyBox since I was 9.
Lol. I'm not complaining though... I love to learn.
Oh and I still haven't tried the ROM you recommended as of yet. PC seems buggy now too.
iks8 said:
I tried it for three times always with the same resoult ;/ btw I don't own this phone anymore.
Click to expand...
Click to collapse
Sent from my XT1527 using XDA-Developers mobile app
Its been a while I didn't saw any new post or discussion in various rom posts like pixel havoc and other. No one is trying out those roms. Is that mean no one is using this device. If you are still using this rom comment down below your experience now.. Thanks in advance.
wasim814 said:
Its been a while I didn't saw any new post or discussion in various rom posts like pixel havoc and other. No one is trying out those roms. Is that mean no one is using this device. If you are still using this rom comment down below your experience now.. Thanks in advance.
Click to expand...
Click to collapse
Land still my daily driver
Still using and on pie ROM by nichcreme
I'm just sticking with Oreo
Google messed up the UI and UX on Pie
And as there's no more updates to Oreo ROMs I'm sticking with liquid remix by difr
wasim814 said:
Its been a while I didn't saw any new post or discussion in various rom posts like pixel havoc and other. No one is trying out those roms. Is that mean no one is using this device. If you are still using this rom comment down below your experience now.. Thanks in advance.
Click to expand...
Click to collapse
Land is still my daily driver.
Excuse my "noobiness", but I wonder why Xiaomi updates MIUI and doesn't security patches. Stock ROM for Land is now 10.2 but its security patch is from 2017.04.01!!![emoji33][emoji33]
Viceant01 said:
Excuse my "noobiness", but I wonder why Xiaomi updates MIUI and doesn't security patches. Stock ROM for Land is now 10.2 but its security patch is from 2017.04.01!!![emoji33][emoji33]
Click to expand...
Click to collapse
No security updates for older phones :silly:
AfterAnonimatum said:
I'm just sticking with Oreo
Google messed up the UI and UX on Pie
And as there's no more updates to Oreo ROMs I'm sticking with liquid remix by difr
Click to expand...
Click to collapse
How is your experience so far with that rom??
Development for the land is dying but i never expected this much xda support when i bought it.
wasim814 said:
How is your experience so far with that rom??
Click to expand...
Click to collapse
Been using it for a long time and even though I'm within the 1% of people with a "defective" device (means that I get random black and green screens with Difr's kernels) I have to say that this ROMs is awesome, no lag, excellent ram management, perfect battery backup up to 8-10h of intensive use
I don't remember facing any critical bug (apart from the random reboots that as I mentioned earlier less than 1% of devices suffer)
Edit: forgot to mention that it has little to absolutely no performance drop over time
Haven't wiped the device in around 3 months (and I'm the type of person that usually swaps roms at least once a month)
AfterAnonimatum said:
Been using it for a long time and even though I'm within the 1% of people with a "defective" device (means that I get random black and green screens with Difr's kernels) I have to say that this ROMs is awesome, no lag, excellent ram management, perfect battery backup up to 8-10h of intensive use
I don't remember facing any critical bug (apart from the random reboots that as I mentioned earlier less than 1% of devices suffer)
Edit: forgot to mention that it has little to absolutely no performance drop over time
Haven't wiped the device in around 3 months (and I'm the type of person that usually swaps roms at least once a month)
Click to expand...
Click to collapse
Sometimes I even swap roms multiple times in a week.. Lol ?
wasim814 said:
Sometimes I even swap roms multiple times in a week.. Lol ?
Click to expand...
Click to collapse
I guess I will give a try this one cause a never used that rom before
wasim814 said:
I guess I will give a try this one cause a never used that rom before
Click to expand...
Click to collapse
I always return to this one
Have tried a lot of Oreo ROMs but most of them have either poor features or huge performance drops over time or critical bugs
AfterAnonimatum said:
I always return to this one
Have tried a lot of Oreo ROMs but most of them have either poor features or huge performance drops over time or critical bugs
Click to expand...
Click to collapse
Can you send me link to that rom
Official builds are no longer happening - https://download.lineageos.org/land ?
enjoy10 said:
Official builds are no longer happening - https://download.lineageos.org/land ?
Click to expand...
Click to collapse
It's sad