Database Users

Latest Tiamat ROM & Kernel Have Me Worried

I have never run the OC'd GPU kernel for fear of damaging my device. I have been running Tiamat kernels since about day 3, though. Today I installed the latest ROM release that includes the Tachi kernel. Whenever I reboot it causes odd display errors at the Motorola logo. The first time this happened the screen would freak out for about ten seconds before the Xoom would reboot. I restored a nandroid to 3.1 and had no problems, so I upgraded from that to the latest Tiamat again. I checked stock rooted 3.2 while upgrading and had no display errors. It seems to be linked to the ROM / kernel. I didn't test just the kernel on the stock ROM, but what would cause this other than the kernel? Just looking for some ideas. The Xoom runs fine after booting.
Here is a short video showing what it does now. This is MUCH better than what it was doing.
https://www.youtube.com/watch?v=s1Uae_Q25pQ&feature=youtube_gdata_player

dude..put that thing down, and walk away...my friend lost his arm when his Xoom blew up after one of those glitches!!!!!!
i'm just kidding. that glitch comes with the Tachi kernel, not the Tiamat rom. and according to the notes the developers provided, it's perfectly normal and it stems from updates for the Tegra platform released by nVidia that they integrated into the kernel. so no worries.

zehkaiser said:
I have never run the OC'd GPU kernel for fear of damaging my device. I have been running Tiamat kernels since about day 3, though. Today I installed the latest ROM release that includes the Tachi kernel. Whenever I reboot it causes odd display errors at the Motorola logo. The first time this happened the screen would freak out for about ten seconds before the Xoom would reboot. I restored a nandroid to 3.1 and had no problems, so I upgraded from that to the latest Tiamat again. I checked stock rooted 3.2 while upgrading and had no display errors. It seems to be linked to the ROM / kernel. I didn't test just the kernel on the stock ROM, but what would cause this other than the kernel? Just looking for some ideas. The Xoom runs fine after booting.
Here is a short video showing what it does now. This is MUCH better than what it was doing.
https://www.youtube.com/watch?v=s1Uae_Q25pQ&feature=youtube_gdata_player
Click to expand...
Click to collapse
My friend you have options just load up the other kernel Launchpad.... try that before you lose it....Troubleshoot till the very end is how I do it before I getting too worried..

LOLOLOLOLOL
you're freaking out about nothing, its supposed to be like that and it wont do any harm to your xoom

Kippui said:
LOLOLOLOLOL
you're freaking out about nothing, its supposed to be like that and it wont do any harm to your xoom
Click to expand...
Click to collapse
What he said. Just chill. It's all good man. Just a few minor graphical glitches. It won't hurt it in the least bit.
That's the best answer we can give you because it's the correct answer, and the only answer as well. The posts before me covered it like a boss.

The graphics glitch, as many have said, is perfectly normal and anticipated by team tiamat.
Now, if during the glitch a strange voice tells you that everyone is against you and they all have to die....call tech support.
Sent from my GT-I9000 using XDA Premium App

I wasnt supposed to listen to the voices?but I already bought the guns and explosives...what am I supposed to do with all this stuff now?they were expensive...

lmfao i tought they put those graphical glitches there as part of the bootanimation i think it looks sick

I feel a little better now. Just wasn't sure what was going on. I'm glad I'm not the only one with the problem. When it explodes I'll call ya. ;-)

truthkillszz said:
lmfao i tought they put those graphical glitches there as part of the bootanimation i think it looks sick
Click to expand...
Click to collapse
I was thinking the same thing. Now who wants to make this into a boot animation?

brijahn said:
I was thinking the same thing. Now who wants to make this into a boot animation?
Click to expand...
Click to collapse
Haha, way ahead of you

If you read the post it was mentioned in it. I think we skip reading and just dl it. I do it
Sent from my DROIDX using XDA Premium App

Moded ROM's - are they really better?

Hi folks!
I don't mean to harm any developer, which in my opinion are real heroes by their attempts in perfecting the GT10.1 ROM, given the circumstances when Google didn't release the source code of Honeycomb.
I want to share my personal experience with those ROM's. I tried all of the available ROM's in this forum. Used each of them for at least a couple of days. Played with Kernel and OC, odexed and de-odexed, optimized and themed - every bit of available MOD I tried. I was in my search of the best and fine-tuned ROM.
But what I found were mostly stability problems, some strange bugs and FC's that anoyed me a lot. And, to be honest, I could not feel real performance gain and smoothness, even when using the OC Kernel.
So I gave up and restored my GT10.1 with stock TW ROM (un-rooted). And, voila! The GT is mostly stable, the FC's are very rare and the OS interface is smooth like silk!
Is there anyone else in this forum with the same personal experience?

Same situation here. I tried them all and stock TW ROM is the most stable and smoothest. I am a heavy user of my tablet. I think Ive gotten a force close only once with the stock ROM after 2 months of use while I got force closes at least twice a week with any of the ROMs here. Not only that but you are risking damaging your battery by flashing ROMs and Kernels other than stock like shown in this thread. http://forum.xda-developers.com/showthread.php?t=1215182
You didnt see a performance increasing over the stock TW ROM because there is no performance increase and this is a fact. Stock ROM with TouchWiz already has hardware accelerated GUI, which is why its so silky smooth similar to ipad. Some of the ROMs you see here dont even have hardware accelerated GUI.
Some of the devs here IMO are going too far for their capability and are unaware what they are changing inadvertently causes issues in other areas. All the force closes, bugs, stability issues, and likelihood of damaging your battery is evidence of this.

ArtificialSweetener said:
Same situation here. I tried them all and stock TW ROM is the most stable and smoothest. I am a heavy user of my tablet. I think Ive gotten a force close only once with the stock ROM after 2 months of use while I got force closes at least twice a week with any of the ROMs here. Not only that but you are risking damaging your battery by flashing ROMs and Kernels other than stock like shown in this thread. http://forum.xda-developers.com/showthread.php?t=1215182
You didnt see a performance increasing over the stock TW ROM because there is no performance increase and this is a fact. Stock ROM with TouchWiz already has hardware accelerated GUI, which is why its so silky smooth similar to ipad. Some of the ROMs you see here dont even have hardware accelerated GUI.
Some of the devs here IMO are going too far for their capability and are unaware what they are changing inadvertently causes issues in other areas. All the force closes, bugs, stability issues, and likelihood of damaging your battery is evidence of this.
Click to expand...
Click to collapse
Is this 5th Element on his third screen name? You also say you'll go blind if you buy the 8.9
Sent from xda premium app

I also think stock tw rom is best for this tablet so far.

I'm using task650's rom and it is a definite improvement over stock. The main difference is in smoothness, especially moving between screens. Also using pershoots kernel.
I don't have any bugs to speak of, no force closes and no issues with the battery.

ewans said:
I'm using task650's rom and it is a definite improvement over stock. The main difference is in smoothness, especially moving between screens. Also using pershoots kernel.
I don't have any bugs to speak of, no force closes and no issues with the battery.
Click to expand...
Click to collapse
+ 1 for tasks rom, much better than stock, no issues here. Using pershoots kernel too.
Sent from my GT-P7510 using xda premium

is there any custom rom that comes with polaris office?

ArtificialSweetener said:
Same situation here. I tried them all and stock TW ROM is the most stable and smoothest. I am a heavy user of my tablet. I think Ive gotten a force close only once with the stock ROM after 2 months of use while I got force closes at least twice a week with any of the ROMs here. Not only that but you are risking damaging your battery by flashing ROMs and Kernels other than stock like shown in this thread. http://forum.xda-developers.com/showthread.php?t=1215182
You didnt see a performance increasing over the stock TW ROM because there is no performance increase and this is a fact. Stock ROM with TouchWiz already has hardware accelerated GUI, which is why its so silky smooth similar to ipad. Some of the ROMs you see here dont even have hardware accelerated GUI.
Some of the devs here IMO are going too far for their capability and are unaware what they are changing inadvertently causes issues in other areas. All the force closes, bugs, stability issues, and likelihood of damaging your battery is evidence of this.
Click to expand...
Click to collapse
LOL DAMAGE THE BATTERY!
Or you could just recalibrate it after you load a new rom.
Sent from my microwave

xinhang said:
is there any custom rom that comes with polaris office?
Click to expand...
Click to collapse
With tasks rom you can reflash any of the removed apps. They are in the OP.
Sent from my microwave

seh6183 said:
LOL DAMAGE THE BATTERY!
Or you could just recalibrate it after you load a new rom.
Sent from my microwave
Click to expand...
Click to collapse
Yes damage the battery. Many people are unable to return their battery to its normal state. Not only that but recalibration does not return the battery to its full capacity. Its a very serious issue and its all caused by flashing ROMs other than stock touchwiz.

ArtificialSweetener said:
Yes damage the battery. Many people are unable to return their battery to its normal state. Not only that but recalibration does not return the battery to its full capacity. Its a very serious issue and its all caused by flashing ROMs other than stock touchwiz.
Click to expand...
Click to collapse
Not true whatsoever.
Sent from my SPH-D710 using XDA App

PhantomHacker said:
Not true whatsoever.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Not true? You did not do any research on this. I did. There are multiple threads about this issue and it has been confirmed by everyone that 3rd party ROMs/Kernels are causing the problem. There is no questioning this.
http://forum.xda-developers.com/showthread.php?t=1276567
http://forum.xda-developers.com/showthread.php?t=1215182

ArtificialSweetener said:
Not true? You did not do any research on this. I did. There are multiple threads about this issue and it has been confirmed by everyone that 3rd party ROMs/Kernels are causing the problem. There is no questioning this.
http://forum.xda-developers.com/showthread.php?t=1276567
http://forum.xda-developers.com/showthread.php?t=1215182
Click to expand...
Click to collapse
This is your first android device isnt it?

ArtificialSweetener said:
Not true? You did not do any research on this. I did. There are multiple threads about this issue and it has been confirmed by everyone that 3rd party ROMs/Kernels are causing the problem. There is no questioning this.
http://forum.xda-developers.com/showthread.php?t=1276567
http://forum.xda-developers.com/showthread.php?t=1215182
Click to expand...
Click to collapse
This is an issue even with stock not rooted, it has more to do with some of the chips that are used to track the battery and not the actual rom. This has been an issue for other android devices as well, and what happens is that the software does not seem to know exactly what the actual state of the battery is. Instead it tries to base this information off of past data.
I had the battey drainage issue, but after recalbrating it I have not had this issue ever again, and my battey life is great. Thats why Samsung recommends plugging in your tab to charge it to full, and then run it dead the first time.
What I noticed was that the software reported that the battey was dead, when in fact it was still fully charged. So I searched XDA and found some good information.
Most of the FCs I have ever gotten where from loading apps that conflict with each other. Like that version of the market that someone posted. Went back to the stock market app and all my problems went away.

novasam said:
This is an issue even with stock not rooted, it has more to do with some of the chips that are used to track the battery and not the actual rom. This has been an issue for other android devices as well, and what happens is that the software does not seem to know exactly what the actual state of the battery is. Instead it tries to base this information off of past data.
I had the battey drainage issue, but after recalbrating it I have not had this issue ever again, and my battey life is great. Thats why Samsung recommends plugging in your tab to charge it to full, and then run it dead the first time.
What I noticed was that the software reported that the battey was dead, when in fact it was still fully charged. So I searched XDA and found some good information.
Most of the FCs I have ever gotten where from loading apps that conflict with each other. Like that version of the market that someone posted. Went back to the stock market app and all my problems went away.
Click to expand...
Click to collapse
and by flashing 3rd party ROM/Kernel you are just asking for this issue to arise on your unit. Statistics do not lie. Everyone who is having this issue has gotten it just after they flashed 3rd party ROM/Kernel. Read the threads if you dont believe me. I have not seen even one person who has gotten this issue from the stock ROM.

ArtificialSweetener said:
Same situation here. I tried them all and stock TW ROM is the most stable and smoothest. I am a heavy user of my tablet. I think Ive gotten a force close only once with the stock ROM after 2 months of use while I got force closes at least twice a week with any of the ROMs here. Not only that but you are risking damaging your battery by flashing ROMs and Kernels other than stock like shown in this thread. http://forum.xda-developers.com/showthread.php?t=1215182
You didnt see a performance increasing over the stock TW ROM because there is no performance increase and this is a fact. Stock ROM with TouchWiz already has hardware accelerated GUI, which is why its so silky smooth similar to ipad. Some of the ROMs you see here dont even have hardware accelerated GUI.
Some of the devs here IMO are going too far for their capability and are unaware what they are changing inadvertently causes issues in other areas. All the force closes, bugs, stability issues, and likelihood of damaging your battery is evidence of this.
Click to expand...
Click to collapse
You obviously haven't done your research bro. Tw do NOT have its GUI hardware accelarated. If you would be a knowledgeable as you say with all your input you would have already dug into the file yourself to see that. They didn't even activate the launcher!! ! No damage to battery either bro. That would be like saying do not turn off or on your tablet because it will cause battery damage. Or don't run too many apps or Widgets because it will damage your battery. This thread is ridiculous.
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
oh yeah. Thanks to the guys who supported my rom in this thread. You guys are the reason I do this.
---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------
ArtificialSweetener said:
and by flashing 3rd party ROM/Kernel you are just asking for this issue to arise on your unit. Statistics do not lie. Everyone who is having this issue has gotten it just after they flashed 3rd party ROM/Kernel. Read the threads if you dont believe me. I have not seen even one person who has gotten this issue from the stock ROM.
Click to expand...
Click to collapse
Most of the issues that arise are USER related anyways, force closes, bad flashes ect... directions are made for a reason, to be followed and some like to be lazy and to other routes. So that's on them.
---------- Post added at 05:03 PM ---------- Previous post was at 05:02 PM ----------
PhantomHacker said:
Not true whatsoever.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
High five to you bro!

ArtificialSweetener said:
Not true? You did not do any research on this. I did. There are multiple threads about this issue and it has been confirmed by everyone that 3rd party ROMs/Kernels are causing the problem. There is no questioning this.
http://forum.xda-developers.com/showthread.php?t=1276567
http://forum.xda-developers.com/showthread.php?t=1215182
Click to expand...
Click to collapse
you didn't do enough research.
http://forum.xda-developers.com/showthread.php?t=1138772
count the number of users there with battery issues, who are on the stock rom.
samsung even pulled the TW update for a time, due to sluggish performance, and ... battery issues.

ArtificialSweetener said:
and by flashing 3rd party ROM/Kernel you are just asking for this issue to arise on your unit. Statistics do not lie. Everyone who is having this issue has gotten it just after they flashed 3rd party ROM/Kernel. Read the threads if you dont believe me. I have not seen even one person who has gotten this issue from the stock ROM.
Click to expand...
Click to collapse
Welcome back, 5thelement! Your writing style (and nonsensical trolling BS) were not missed!

Battery?
I suppose you have a Stock TouchW rom, right??

pershoot said:
you didn't do enough research.
http://forum.xda-developers.com/showthread.php?t=1138772
count the number of users there with battery issues, who are on the stock rom.
samsung even pulled the TW update for a time, due to sluggish performance, and ... battery issues.
Click to expand...
Click to collapse
Been running custom everything from the beginning and never had an issue. With pershoots kernel overclocking enabled i still get much better battery life and performance, not to mention task's rom, which blows stock out of the water.

Force reboots on all ICS ROMs

Currently using Kang Milestone 5. Tried CM9, Nightlies, CM9 HumberOS etc. and my tab still randomly reboots. Even rebooted while it was asking me for account info.
This is after fresh restocks from Overcome instructions too.
On Gingerbread I had absolutely no problems.
Seems to happen at least every two hours. Is it as bad for anyone else?

R Forrester said:
Currently using Kang Milestone 5. Tried CM9, Nightlies, CM9 HumberOS etc. and my tab still randomly reboots. Even rebooted while it was asking me for account info.
This is after fresh restocks from Overcome instructions too.
On Gingerbread I had absolutely no problems.
Seems to happen at least every two hours. Is it as bad for anyone else?
Click to expand...
Click to collapse
No, havnt had any reboots like that myself. CM9 runs brilliantly on my Tab, Just shows what Sammy could have done if they gave a sh1t about updating their previous devices.

Been happening a lot less lately. Might be partially due to the fact that I've stuck with milestone 5 as well as kept the 160 dpi instead of using 120 like I normally do.
Still, it happened on a fresh install while I was entering in details.
Seems entirely random.

So to bump this thread I have found that undervolting the CPU by 50-75 mV seems to have solved these issues, at least in the latest CM10 version in case anyone is curious.

R Forrester said:
Currently using Kang Milestone 5. Tried CM9, Nightlies, CM9 HumberOS etc. and my tab still randomly reboots. Even rebooted while it was asking me for account info.
This is after fresh restocks from Overcome instructions too.
On Gingerbread I had absolutely no problems.
Seems to happen at least every two hours. Is it as bad for anyone else?
Click to expand...
Click to collapse
My tab is GT-P1000N. My tab rebooted after every second. I was dieing to solve my problem. I searched everywhere but couldn't find any solution. Then I asked alroger how to solve this problem and thanks to him he said that the best thing to do is to stop overclocking the tab i.e to keep it max 998 MHZ. That's how my problem got solved. And also do a fresh install. Yor problem will be solved.
With best regards,
Adnan
And sorry for bad english. Because I am a Bangladeshi.

adnan.rakib said:
My tab is GT-P1000N. My tab rebooted after every second. I was dieing to solve my problem. I searched everywhere but couldn't find any solution. Then I asked alroger how to solve this problem and thanks to him he said that the best thing to do is to stop overclocking the tab i.e to keep it max 998 MHZ. That's how my problem got solved. And also do a fresh install. Yor problem will be solved.
With best regards,
Adnan
And sorry for bad english. Because I am a Bangladeshi.
Click to expand...
Click to collapse
I was using kanged gummy kernel with CM9.1 before upgrading to CM10 and running at 1.2ghz NEVER rebooted. Now that I'm using CM10 I can't go past 1ghz without reboots however it seems faster than CM9.1/kanged gummy/1.2ghz.
Would be great If I could get 1.2ghz though, speeds things up a lot.

Using gt-p1000 I get random reboots too, using cm9 & 9.1, never had prob with gb. Now using latest cm9 nightly -so far so good.
Sent from my GT-P1000 using xda app-developers app

R Forrester said:
I was using kanged gummy kernel with CM9.1 before upgrading to CM10 and running at 1.2ghz NEVER rebooted. Now that I'm using CM10 I can't go past 1ghz without reboots however it seems faster than CM9.1/kanged gummy/1.2ghz.
Would be great If I could get 1.2ghz though, speeds things up a lot.
Click to expand...
Click to collapse
You should be able to OC to 1.4 now.
See:
http://forum.xda-developers.com/showpost.php?p=34290097&postcount=514

[Q] Random Boots When On a Call

I'm getting Random Bootloops when on calls, or that's when I see it most often. Obviously it's a pain to drop calls in this manner then tell the caller I have the new GS4 I'm currently running ForceRom 2.3 which comes with KT Kernel. The problem seemed to start about 1 week ago while I have been running ForceRom without issues since it was released. I have tried installing Stock Kernel but problem persisted. I even DataWiped and restored a backup but problem is still there. I'm going to try to run fully stock un-rooted next, but wanted to know of any other suggestion.

Kingmdm said:
I'm getting Random Bootloops when on calls, or that's when I see it most often. Obviously it's a pain to drop calls in this manner then tell the caller I have the new GS4 I'm currently running ForceRom 2.3 which comes with KT Kernel. The problem seemed to start about 1 week ago while I have been running ForceRom without issues since it was released. I have tried installing Stock Kernel but problem persisted. I even DataWiped and restored a backup but problem is still there. I'm going to try to run fully stock un-rooted next, but wanted to know of any other suggestion.
Click to expand...
Click to collapse
I have the same problem :/

Joe0113 said:
I have the same problem :/
Click to expand...
Click to collapse
I guess that's good to hear. I have seen many other posts around the Web including here about reboots when using camera, but not my issue. I went ahead and restored everything back to TW MDL stock and left un-rooted for now (I doubt root is the problem though). So far no reboots when on calls, but will need more heavy usage over the next few days. Since I haven't installed any apps and still only using fully stock apps maybe issue could be with a downloaded app. 1 Cool side affect is I have tried Samsung's WatchOn while on stock and I must admit it's truly cool to control all my TVs now, it will be a keeper Are you using a custom ROM, which one?

Are you guys undetvolting your cpu or overvolting or messing with kernel settings at all?
Sent from my SPH-L720 using xda premium

Im glad you asked since that was my concern. I have been using default settings on KT kernel which comes with ForceRom. It seemed problem mostly occurred when screen times-out and on Bluetooth. I thought when screen is off KT UC cpu but problem persisted when using stock kernel.
Sent from my SPH-L720 using Tapatalk 2

Something defiantly hung back from the kernel, if the problem doesn't persist since your on stock MDL now I wouldn't worry about it. My guess was undervolting on kernel BC I had the same problem but it went away after I loaded stock kernel settings
Sent from my SPH-L720 using xda premium

Kernels?

I've been searching all day and haven't found a lollipop kernel that isn't more than a slightly modified stock kernel. Am I just blind or are there pretty much only pre-lollipop kernels?

EddyTeddy01 said:
I've been searching all day and haven't found a lollipop kernel that isn't more than a slightly modified stock kernel. Am I just blind or are there pretty much only pre-lollipop kernels?
Click to expand...
Click to collapse
I've been looking too and I don't think there are any, bar Khaon's. I'm not sure if this is f2fs only, not read into too much. However, I'm using rastapop rom and its working great, pretty much stock but with a few select features, which happened to be just what I was looking for.
Sent from my Nexus 10 using XDA Free mobile app

Hayth said:
I've been looking too and I don't think there are any, bar Khaon's. I'm not sure if this is f2fs only, not read into too much. However, I'm using rastapop rom and its working great, pretty much stock but with a few select features, which happened to be just what I was looking for.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
What about wifi? Mine is fubar under cm12 and stock lollipop. Haven't found a kernel either.

Khaon's kernel isn't just for f2fs, I'm using it right now on Dirty Unicorns ROM. It has a few governors, schedulers, OC/UV. It has been working great for me so far.

omgi0wn said:
Khaon's kernel isn't just for f2fs, I'm using it right now on Dirty Unicorns ROM. It has a few governors, schedulers, OC/UV. It has been working great for me so far.
Click to expand...
Click to collapse
I just installed Purity ROM on my N10. Was using Franco Kernel before (planned to stay on KitKat) but it was buggy as hell and I tried to reach out to him multiple times, via here and G+ but he never cared to reply back. So glad I paid for it.
I'm using the stock kernel installed with Purity. You think the above Kernel would have any issues with the ROM?
I looked at his Gdrive folder here and he has two different ones. Using the tablet because I'm traveling I can't see the whole filename.
Which one should I choose?
Thanks.

usafle said:
I just installed Purity ROM on my N10. Was using Franco Kernel before (planned to stay on KitKat) but it was buggy as hell and I tried to reach out to him multiple times, via here and G+ but he never cared to reply back. So glad I paid for it.
I'm using the stock kernel installed with Purity. You think the above Kernel would have any issues with the ROM?
I looked at his Gdrive folder here and he has two different ones. Using the tablet because I'm traveling I can't see the whole filename.
Which one should I choose?
Thanks.
Click to expand...
Click to collapse
I am on the 2/17 kernel right now, I'm not entirely sure what the differences between the two kernels he has up there are. I think once might allow sabermod which I think was recently included in his ROM, not entirely sure though.
Sent from my Nexus 10 using Tapatalk

omgi0wn said:
I am on the 2?17 kernel right now, I'm not entirely sure what the differences between the two kernels he has up there are. I think once might allow sabermod which I think was recently included in his ROM, not entirely sure though.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Thanks. Wanted to make sure since I'm traveling and if I throw a boot loop, I won't have any way to recovery from it.
Are you using some 3rd party app for the O/C - kernel settings etc or does he have a specific app for kernel management?

usafle said:
Thanks. Wanted to make sure since I'm traveling and if I throw a boot loop, I won't have any way to recovery from it.
Are you using some 3rd party app for the O/C - kernel settings etc or does he have a specific app for kernel management?
Click to expand...
Click to collapse
He doesn't have any personal kernel management software but Aero Kernel, SetCPU or something along those lines should do the job.

omgi0wn said:
He doesn't have any personal kernel management software but Aero Kernel, SetCPU or something along those lines should do the job.
Click to expand...
Click to collapse
I am using now kernel audiutor. It is very good !! Everything is supported should give a try.

If the man himself recommends a certain kernel management program, chances are I'm going to try that one out.
Thanks, just flashed your Kernel on my N10 running Purity ROM. So far, no boot-loop. Looking forward to it.
Do you have any recommended settings for the N10 + your Kernel?
Khaon said:
I am using now kernel audiutor. It is very good !! Everything is supported should give a try.
Click to expand...
Click to collapse

EddyTeddy01 said:
I've been searching all day and haven't found a lollipop kernel that isn't more than a slightly modified stock kernel. Am I just blind or are there pretty much only pre-lollipop kernels?
Click to expand...
Click to collapse
There maybe hope for a Lollipop 5.1.0 Franco kernel for the Nexus 10, see this post from the Nexus 5 forum where Franco mentions his kernel/devices priorities.
http://forum.xda-developers.com/showthread.php?p=59405055
Sent from my Nexus 10 using XDA Premium HD app

usafle said:
If the man himself recommends a certain kernel management program, chances are I'm going to try that one out.
Thanks, just flashed your Kernel on my N10 running Purity ROM. So far, no boot-loop. Looking forward to it.
Do you have any recommended settings for the N10 + your Kernel?
Click to expand...
Click to collapse
Hello,
basically, stock kernel performs also well, but I don't like the default "tunnables".
Governor : you can stick with interactive and default values I made : I changed touch boost to be kernel side and the touchboost duration is 200 ms, however, you can decrease it to 100ms(that's i am using).(default value is 500ms)
io scheduler: you can switch from BFQ to fiops or ZEN. The io scheduler handles who is reading or writing to the disk. If you mainly multitasking(torrents,music,beo<insg, etc at the same time) bfq is good, otherwise you can switch to fiops or zen
Ofc undervolting: our device is set up with high voltage, basicaly I can reduce 100~150mV but this DOES NOT APPLY to everyone, you have to test yourself your own chip to figure out which voltage is required to have it stable.

Khaon said:
Hello,
basically, stock kernel performs also well, but I don't like the default "tunnables".
<SNIP>
Click to expand...
Click to collapse
I don't know if its just MY device or some other issue. I'm running Purity ROM and after flashing your kernel I can actually watch my battery drain.
Its been 47 minutes and I'm already down to 89%. At this rate it will be dead in 3 hours +/-. Only using Wifi and screen is set to lowest brightness setting. No gaming, just using Boat Browser and sending Hangout messages.
I'm using Greenify to kill any apps in the background and I've used SDMaid to stop any unnecessary apps from running on startup.
Not sure what the issue is or if you even want to be bothered trying to diagnose? Not meant as a slight to you or your work at all just don't know if this is just a issue with mine or others are having the same problems?
I've already let the device die and recharge a few times thinking it was the battery stats being reported incorrectly but it doesn't seem to be the case.
Any suggestions? Ideas?
Thanks.

usafle said:
I don't know if its just MY device or some other issue. I'm running Purity ROM and after flashing your kernel I can actually watch my battery drain.
Its been 47 minutes and I'm already down to 89%. At this rate it will be dead in 3 hours +/-. Only using Wifi and screen is set to lowest brightness setting. No gaming, just using Boat Browser and sending Hangout messages.
I'm using Greenify to kill any apps in the background and I've used SDMaid to stop any unnecessary apps from running on startup.
Not sure what the issue is or if you even want to be bothered trying to diagnose? Not meant as a slight to you or your work at all just don't know if this is just a issue with mine or others are having the same problems?
I've already let the device die and recharge a few times thinking it was the battery stats being reported incorrectly but it doesn't seem to be the case.
Any suggestions? Ideas?
Thanks.
Click to expand...
Click to collapse
Hm there are out there many apps to check battery drains and what process consumes energy.
I dont know much of that, but I use betterbatterystats, I know- from screen I saw- there are more complete software, yes I would bother trying to fix anything broken as long as I am given at least the minimum information

usafle said:
I don't know if its just MY device or some other issue. I'm running Purity ROM and after flashing your kernel I can actually watch my battery drain.
Its been 47 minutes and I'm already down to 89%. At this rate it will be dead in 3 hours +/-. Only using Wifi and screen is set to lowest brightness setting. No gaming, just using Boat Browser and sending Hangout messages.
I'm using Greenify to kill any apps in the background and I've used SDMaid to stop any unnecessary apps from running on startup.
Not sure what the issue is or if you even want to be bothered trying to diagnose? Not meant as a slight to you or your work at all just don't know if this is just a issue with mine or others are having the same problems?
I've already let the device die and recharge a few times thinking it was the battery stats being reported incorrectly but it doesn't seem to be the case.
Any suggestions? Ideas?
Thanks.
Click to expand...
Click to collapse
Hi there!
Check of your device is actually going into deep sleep. There is an issue with the latest google play services. It prevents the device from going to sleep. I am using CM12 nightly and i suffer from this issue as well.
Nexus 10 and Oneplus one.

Beaster said:
Hi there!
Check of your device is actually going into deep sleep. There is an issue with the latest google play services. It prevents the device from going to sleep. I am using CM12 nightly and i suffer from this issue as well.
Nexus 10 and Oneplus one.
Click to expand...
Click to collapse
What should be the newest version of Google Play Services? Mine is showing 7.0.97 (1791429_ 436)
Thanks.

usafle said:
What should be the newest version of Google Play Services? Mine is showing 7.0.97 (1791429_ 436)
Thanks.
Click to expand...
Click to collapse
Yeap same here. The next cm12 nightly willnhave the necessary commits to solve the issue