Database Develop

Fast reboot in 7 seconds

Hello,
I just got my third really fast reboot if I can even call it a reboot.
The fastreboots (I'll call it FRB from now on.) always happened when the CPU was really busy
The phone were getting laggy and didn't respond anymore and the screen shut off but the 4 softbuttons still lit up.
The bootanimation was starting and stopped like 7 seconds later and the display showed the lockmenu.
the first time this happened I just thought "wow, what was a freaking fast reboot"
the second time I just said wtf and accidentally checked the uptime.. 2 days! the phone just rebooted but is still showing 2 days?
and now the 3rd FRB, checked the uptime -> almost 4 days
What the hell? Is someone else experiencing this?
All active apps are stopped and everything is just like a normal reboot
ROM: CyanogenMod 6 08172010 Nightly
Kernel: 2.6.35-925mV-1113MHz-BFS-SVS-AIX-720p-Monks-081610 (max clock: 1036; min: 245; interactive)
And I think I also noticed a FRB before using this kernel and a previous CM6 nightly

I've had this happen too. The only thing I noticed is it happened after my phone had been idle for a long period of times. Its happened roughly 3-5 times for me. As a windows user I admit it didn't concern me much lol

It's not a reboot, it's Android restarting. The back-end Linux stuff stays up. Pretty obvious when it's the boot animation you see, not the solid X.. And as you say, it's pretty fast.
And yes I suspect there's a watchdog.. If the whole system is stalled for > N seconds, restart it. Waze does this to me once or twice a week.

Yeah, this has been happening to me a lot more lately, especially when I start installing apps from the market after a wipe and restore, it messes up the market. It also messes up on Titanium backup. Getting very annoying.
Has happened on Enoms, and LeoFroyo ROMs.

khaytsus said:
Pretty obvious when it's the boot animation you see, not the solid X..
And yes I suspect there's a watchdog.. If the whole system is stalled for > N seconds, restart it.
Click to expand...
Click to collapse
Yes, makes sense

I've been calling it a random/soft reboot and it has been happening with eclair as well.

Happens for me too, got this stuff twice, both at car's dock with GPS and navigation on.
Isn't this kind of reboot a documented thing? How comes?
EDIT: not OC/UV, enom's 2.11.3.

because it seems its only mainly happening on custom roms lol

I don't think it's the custom rom. At least not enom's one, because of his conservative kernel policy. Looks more like something with overheating (both times it happened for me I've used a car dock with 3g,bt,gps on and charging)...

disgustip8ted said:
because it seems its only mainly happening on custom roms lol
Click to expand...
Click to collapse
Nope, I see this 1-2 times a week since I got my N1 2 months ago and only switched to a custom this last weekend.

tltester said:
I don't think it's the custom rom. At least not enom's one, because of his conservative kernel policy. Looks more like something with overheating (both times it happened for me I've used a car dock with 3g,bt,gps on and charging)...
Click to expand...
Click to collapse
Not overheating for me.. It's anything that bogs the system, as previously explained. But of course there could be many paths to this issue.

It's not the roms....I'm totally stock running FRF91 with absolutely no root access enabled and this happened to me yesterday. It caught me off guard too because like others said my phone went into a state of sluggish responsiveness and then all of a sudden it jumped right to my boot animation, no big X. about 5-8 seconds later I was back at the homescreen watching my Widgets load up like they do when the phone first boots up.

Is it possible to create an app that forces this kind of reboot? I think not

xPatriicK said:
Is it possible to create an app that forces this kind of reboot? I think not
Click to expand...
Click to collapse
I think so.
Try from adb:
Code:
adb shell stop
adb shell start
Is the observed behaviour the same?

djmcnz said:
Is the observed behaviour the same?
Click to expand...
Click to collapse
Yes
/10chars.

ptrrrrrck said:
Is it possible to create an app that forces this kind of reboot? I think not
Click to expand...
Click to collapse
djmcnz said:
I think so.
Try from adb:
Code:
adb shell stop
adb shell start
Click to expand...
Click to collapse
Quite an old thread here, never the less: any chance of reproducing this without ADB acces but on the device itself? Quite handy when playing around with the new T-Mobile Theme Changer and instead of a lenghty reboot reloading the shell would suffice. Eh...?

Sense ROMs have the feature ("Hot restart"), so it's reproducible.

schaggo said:
Quite an old thread here, never the less: any chance of reproducing this without ADB acces but on the device itself? Quite handy when playing around with the new T-Mobile Theme Changer and instead of a lenghty reboot reloading the shell would suffice. Eh...?
Click to expand...
Click to collapse
Well, you can stop the shell via terminal on the phone but then you'd have no way to start it again...

A week ago I used a CM Nightly and noticed the 'Suspend' mode in the powerbutton menu (when you hold the powerbutton). I pressed it and it kinda rebooted like this. Not sure if it's what I meant in post 1 .. and it's not in the nightlies anymore

schaggo said:
Quite an old thread here, never the less: any chance of reproducing this without ADB acces but on the device itself? Quite handy when playing around with the new T-Mobile Theme Changer and instead of a lenghty reboot reloading the shell would suffice. Eh...?
Click to expand...
Click to collapse
There are a few apps on the market that can do this, it's called hot booting (Search for hot boot). The only one I can see that is free is root toolbox but I couldn't get it to work on my S2. Quickboot plus has the option and it works just fine.

Blitzkrieg trouble

FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!

At least you got it installed, I couldn't even get that!
Sent from my Gingervolt-ed VS910 4G using xda premium

Mark Once Again said:
FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!
Click to expand...
Click to collapse
Was it still unstable if you turned it down to 1GHz instead of keeping it at 1.5GHz?

I never could get that far. As soon as the phone was almost up it would restart. I tried about 5 or six times. I am happy with the phone without Blitzkrieg. Just thought I would pass along the info.
Thanks to all!

Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...

vortmax said:
Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...
Click to expand...
Click to collapse
I wonder why of all things, that would make a difference. You must've figured that out by chance? Haha
Sent from my Supercharged, Blitzed LG Revolution using xda premium.

I tried plugged into the usb on my pc, plugged into the charger and not plugged in at all. Same result each time. No complaint, just thought it might help having the info out there.
Thanks again!

You might try first installing a CPU utility like setcpu, and setting it to do no more than 1ghz on boot, and then flash it
Sent from my VS910 4G

Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.

brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
Turn up the min. That fixed it for me

brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
You can turn off the haptic feedback to minimize that vibration reboot but it won't solve the issue tho
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p

For those who use blitzkrieg kernel I recommend using cpu tuner instead of setcpu
I've been testing both app extensively for the past 2 weeks and notice cpu tuner is much more stable than set cpu and both have the same features
I use the free set cpu verison that you can download on the xda site that's the same as the paid version you get on the market
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p

Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?

I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.

keynith said:
I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.
Click to expand...
Click to collapse
keynith, try to set the min cpu speed to 768 in setcpu.
So far after changing the min cpu speed i haven't had any issues again.

Did that yesterday and no problems since seemed to work
Sent from my VS910 4G using XDA App

brad08stanggt said:
Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?
Click to expand...
Click to collapse
Best thing I can say to do is to Restore to default and install things one or two at a time. It's likely an App causing the issue. I have had that happen a few times on my Droid 2 Global. Every time I would run the Goggle Nav App, my phone would randomly reboot. Don't have it installed, would be perfectly fine, until I installed Pandora app. Some buggy apps can cause such issue, and also bad settings. So, I would suggest going the 'long way' and starting from scratch and installing only necessary apps one or two at a time. If things work good, move on to next apps. When things go bad, recall the apps you just installed where the problem occurred. Restore your phone, install only those apps and see if you have reboot issues. If so, you are closing in to finding the real problem. I doubt, even by the post you wrote, that it's the phone or hardware. You need a factory fresh restore, including wiping ALL data, including settings for your apps.
-Cybie

Well?
I don't know if you guys fixed your problems yet, but I kinda had some of the same issues and I do not use CPU Tuner or Set CPU! Also I know that when you install Blitz 1.3 It defaults to normal CPU speeds that are already in phone settings as checked by CPU Spy after flashing Blitz. I have been using Antutu CPU Master Pro to set speeds and profiles works great for the price I use it on my Viewsonic G-tablet as well! Anyway what my first issue is the screen locks I had them all the time and the only way I kept them from happening was to set my min at the 245.76 MHz and my all the time max at 1200MHz. I also set the screen off at 122.88MHz - 245.76MHz On demand scaling profile to keep it not wakening from sleep quick enough. Antutu has all kinds of settings in the Pro version and If you want a overclock I think its the best to use.
The only Issue I have not figured out is you guys get a 10 sec vibrate then a reboot I get a Vibrate forever until I reboot I got woke up this morning at 4:00 A.M. by my phone vibrating next to my bed only happens at night and only when I start receiving emails early in the morning. I tried several screen off settings and not having vibration on at all and still happens figure that one out and I will gladly try anything you come up with!!! The only time it doesn't do it is if it is plugged in and charging!

Softkey lights
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
EDIT: charging to 100% fixed this.
Thanks for the quick reply and all your other posts too mt, they are very informative.

anangelablaze said:
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
Click to expand...
Click to collapse
Charge it to 100% and it will stop

Reboot when TouchPad goes to sleep in Homescreen

This is a common problem since the very beginning. The only way to stop it from occuring is if I leave it on Browser and put it to sleep.
I just installed the latest CM9 and the problem still occurs.
Is there anyway to fix it?

Sepharite said:
This is a common problem since the very beginning. The only way to stop it from occuring is if I leave it on Browser and put it to sleep.
I just installed the latest CM9 and the problem still occurs.
Is there anyway to fix it?
Click to expand...
Click to collapse
After the first time you get it to sleep without rebooting, you can turn off the screen at any point without a problem, right?

Try raising up the minimum clock speed to 384 and see what happens.

Minimum cpu was already raised. I changed the schedule to deadline,let's see if this works.
Sent from my GT-I9100 using Tapatalk 2

Caches were cleaed upon installing the latest nightly? Used to have that problem with some of the very first nightlies, TP would reboot upon turning off the screen, clearing caches fixed that.

I have the same, or similar problem
allstar319 said:
Caches were cleaed upon installing the latest nightly? Used to have that problem with some of the very first nightlies, TP would reboot upon turning off the screen, clearing caches fixed that.
Click to expand...
Click to collapse
I have the same, or similar problem but unfortunately have not found a fix after trying every possible remedy from clearing the cache and upping the min frequency to a complete uninstall with acmeuninstaller . Clearing the cache may fix it for a small amount of time but it always seems to come back. I tried upgrading with both goo and with CWM thinking one may be missing something but both have the same results.
I managed to trace the problem to wifi turning off when sleeping for me. If i set wifi to stay on during sleep it does not happen, if I use a widget to go into airplane mode on sleep it does not happen but if i set wifi to turn off during sleep it happens. It may take a day or two to manifest but it always seems to come back.
I finally ended up using the 7/7 nightly because it doesn't do it and i dont feel like finding the exact nightly that the bug manifested in. I know it was after 7/7 and prior to 8/9. It is a pain as the 7/7 has some lag not found in the later nightly but if the choice is lag or greater battery drain, I choose lag.
Anyway..... Sorry to jack your thread. I feel for you, the reboot on sleep make the TP unusable. If you do manage to find a fix because i still search the forums hoping to see something i haven't tried yet.

Making the cpu scheduler to Deadline fixed the problem so far.
Sent from my GT-I9100 using Tapatalk 2

same problem
hello guys,
I have the same reboot-problem. I tried almost anything...
@Sepharite
Is it still fixed with cpu scheduler to Deadline?
If yes, how did you do that?
I just installed the app "No-frills CPU Control" und turned the cpu scheduler to Deadline, but it still reboots.
I have only no reboots, when I'm using the touchpad after booting for a while.
Anyone has an idea?

esemudeo said:
hello guys,
I have the same reboot-problem. I tried almost anything...
@Sepharite
Is it still fixed with cpu scheduler to Deadline?
If yes, how did you do that?
I just installed the app "No-frills CPU Control" und turned the cpu scheduler to Deadline, but it still reboots.
I have only no reboots, when I'm using the touchpad after booting for a while.
Anyone has an idea?
Click to expand...
Click to collapse
I've had the same problem for months. At this point, we may have to live with it. I find that if you let the device time out of its own, about 80% of the time it won't reboot again. It definitely serves as a reminder that we aren't in stable build territory yet (though, some people apparently don't experience this).
Sent from my SCH-I535 using Tapatalk 2

Infinite Jest said:
I've had the same problem for months. At this point, we may have to live with it. I find that if you let the device time out of its own, about 80% of the time it won't reboot again. It definitely serves as a reminder that we aren't in stable build territory yet (though, some people apparently don't experience this).
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer. I have to ask, you don`t have this problem anymore?

esemudeo said:
Thanks for the answer. I have to ask, you don`t have this problem anymore?
Click to expand...
Click to collapse
No, I still have this issue. I just live with it and try to minimize rebooting (which in have to do every couple of days anyway, thanks to match some point all of my apps crashing a couple of times when I try to open them unless I reboot.)

hey guys, good news.
User Sohip wrote in another thread, he also had reboots, but after he disabled the lock screen it stopped rebooting.
So I disabled the lock screen, and it seems to work. You should try it.
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
oh, now I get reboots again
---------- Post added at 11:00 AM ---------- Previous post was at 10:27 AM ----------
By the way, just in case, somenone tries ot fix this reboot-problem.
When the touchpad goes to sleep, it makes a „click“-sound, and then it reboots.
At least my touchpad makes a „click“-sound.

I haven't had a lock screen for months and the problem has persisted.

[Still bugged, need help] Clock freezes while in deep sleep.

I´m having quite a frustrating problem. Tried to search the net for hours, only finding a handful of people with the same issue but no solution. So, I wondered if anyone can help me out here? The problem is that my clock is not updating while screen is off. Naturally, this affects all alarms and notifications as well.
20:15 -> I adjust alarm to 20:30 and put the screen off. I press power right after the screen has gone off, and see the lockscreen.
Lockscreen informs it´s 20:15 and the alarm is set at 20:30.
20:30 -> Nothing happens.
20:45 -> I press power. Clock says 20:15 for a second. After one second, it shows 20:45, and the alarm starts ringing.
So the problem is quite easy to identify- the clock doesn´t get updated when screen is off. The moment I switch it on -seeing the lockscreen- it gets updated and acts accordingly if any alarms or notifications were to ring at the period it was not updating. However, it´s much less easy to find out what´s behind it. Could anyone spare me a hint here?
I´m running a rooted P7300 with CM10, 30/10 build. Using Tasker to underclock while the screen is off in order to preserve battery life. I thought that caused the problem, but while leaving the CPU untouched....
01:00 -> Switching tablet off, putting alarm at 9:00
09:10 -> Wife wakes me up instead of the alarm. I press power.
Clock says 8:48 for a second. After that second, it gets updated, shows 9:10, and the alarm starts ringing.
I´m getting a little clueless here, so any help would be appreciated.
Running rooted P7300 with CM10 (30/10 build).
Cheers, Henu.
EDIT: Ok, I´ve come to the conclusion that this freezing happens when entering Deep Sleep. If that could give anyone any clues?

Works on CM10 version 11-11
Hi,
I can confirm that it works correctly in CM10 from 11-11.
I only have one weird problem left: the device drains more power when turned of than in standby.

I have been running the 11_11 build since it was released and had not had clock issues until today. I am not overly technical and have no clue why it is happening again. But for as smooth as this rom is I will live with it.
When mine gets confused on time it will not reset itself once i wake the tablet up, it stays messed up until I manually fix it.
Sent from my GT-P7310 using Tapatalk 2

Launcher ?
Do you use the stock launcer? Mine did strange things when using the apex launcher. No problems with stock launcher from cm10.

I am using the stock launcher but have installed nova and thinking about giving it a try
Sent from my GT-P7310 using Tapatalk 2

You could try the clock sync app from the play store. It worked on my phone when it had clock sync issues with a rom. Unfortunately, i'm new to xda, so I can't post the link, but just go to the play store and search for clock sync. It's by Sergey Barinov.

Thanks, but unfortunately none of this methods helped- I´m still having the same issue even with the 11/11- build, running Clock Sync as well. Anyone could shed any light here? I wish I wouldn´t have to go back to some (yuck) stock version.

I don't know if this will help but I just resolved this issue for myself. I did a factory reset. And also wiped all caches and system before flash. Then immediately after flash before rebooting system I wiped everything again except system. And then I started up and there was no issue with the clock. I'm running cm 10. I hope this helps.
Sent from my HTC One X using xda app-developers app

Sounds like voodoo but I´m all in for trying even that. I will post the results tomorrow.
To confirm:
1) Basic superwipe procedure (factory reset/ system, cache, dalvik)
2) flash OS -> don´t boot yet up to OS like normally
3) wipe cache & dalvik
4) THEN reboot -> to OS?

Voodoo, baby.
It worked. Seriously, what the hell. My wild guess is that some file(s) might be corrupted in the actual package- and when the system notices they are missing at the first boot, it will replace them with working ones. Then again, I´m no Android/ Linux expert.
With a clean install, I ran alarm after 8 hours. Worked. Then I added Apex Launcher, waited 2 hours. Alarm went on. Installed everything again with Titanium Backup, put alarm after an hour. Still worked. So I can confirm that it´s not app- dependant but OS- dependant. However, it worked, so thanks a goddamn zillion!!!

Congratulations. Just happy to help.
Sent from my HTC One X using xda app-developers app

I´m going to snap this piece of junk into half soon.
The problems came back, no reason why. I´m now trying one more thing, which is completely disabling Tasker, as it´s basically the only thing running while the screen is off. If that doesn´t help, i´m clueless.
EDIT: What a surprise, it didn´t help. So, it´s either non- functioning CM10 or stock ICS. I could had settled with CM9 easily, but that gave me the battery bug after two weeks. Seriously, this whole me- buying- a- tablet- and- getting- it- to- work has been a living joke. I just would love to have a stripped down OS with a Kernel supporting "all sorts of stuff" like processor speed, running app restriction, tweakable backlight etc.

Ok, so I wiped cache and dalvik and it worked for a couple of hours. Then last night the clock froze again. And this was quite interesting..
Alarm set at 10:30
I wake up 11:15 (hey, it was New Year´s Eve )
I press power and the clock says 11:15 and next alarm is set "tuesday 10:30".
Two seconds later the alarm hops into "wednesday 10:30".
Two hours later I press power, and the clock is 11:15 for a second and jumps to real time. So it´s definitely broken again.
I was just wondering- maybe I could try replacing the clock with another kernel´s version, would that be possible? Any help would be much appreciated.
EDIT: I also tried -once again- without automatic time& date (as my connectivity is set to cut off while the screen is off) and it still didn´t alarm me until I manually pressed the screen on.
EDIT2: Ran A1 kernel, no effect, still bugged.
EDIT3: Ran Tracid´s official ICS. Worked for a day, then bugged. Same thing with A1 kernel. I also had some serious issues with MTP connection and bootloader, so I restored stock and brought it back to the store where I got it for warranty repair. They think it´s a faulty MoBo.

I´m shamelessly bumping this. I ran the stock firmware with Odin and took it to the repair, as I wrote earlier.
Got the tab from warranty repair, seems that the only thing they had performed was "software update" . Very useful for someone who is constantly switching ROMs etc... like I hadn´t tried that before.
After returning to stock and all, I installed CM10 again. And "surprisingly", the problems started again. With or without apps, launchers, cachewipes, younameit. I´m now giving this a test with the stock ROM for a couple of days. I actually hope it doesn´t work, because that would be the only reasonable thing now. If it works with the stock ROM, I´m getting clueless. Does that mean I have some sort of issue which happens only in flashed ROMs instead of the stock one? That would be just....awkward.

[Q] Small lags here and there

Hello guys, how are you?
I would like to ask if you also have the same "problem" with your nexus 6. First of all, I come from an OnePlus One which was very smooth . I used to run CM + Franco Kernel but even stock CM (11 or 12) run nicely on it.
Now I'm using a Nexus 6 with the stock rom and the latest version of franco kernel (r26) but, for example, when I swipe the multitasking windows, I can see clearly a lag especially with the last one. Scrolling up and down is also laggy sometimes. Are you experiencing the same? I am running without the encryption and I already tried to disable Fsync; the launcher is the Google one.
Do you have any other sugestions?
Regards,
Rafael

I had this issue on Franco kernel. I went back to stock and the lags went away and battery life almost doubled

I have small lags here and there (sometimes seconds long freezes) but that's mostly due to me messing with kernel settings, trying out custom kernels and nightly ROM builds.

where you able to find out what was causing the lag and how to fx it? im having the same issue.

angourakis said:
Hello guys, how are you?
I would like to ask if you also have the same "problem" with your nexus 6. First of all, I come from an OnePlus One which was very smooth . I used to run CM + Franco Kernel but even stock CM (11 or 12) run nicely on it.
Now I'm using a Nexus 6 with the stock rom and the latest version of franco kernel (r26) but, for example, when I swipe the multitasking windows, I can see clearly a lag especially with the last one. Scrolling up and down is also laggy sometimes. Are you experiencing the same? I am running without the encryption and I already tried to disable Fsync; the launcher is the Google one.
Do you have any other sugestions?
Regards,
Rafael
Click to expand...
Click to collapse
phyba said:
I had this issue on Franco kernel. I went back to stock and the lags went away and battery life almost doubled
Click to expand...
Click to collapse
brando56894 said:
I have small lags here and there (sometimes seconds long freezes) but that's mostly due to me messing with kernel settings, trying out custom kernels and nightly ROM builds.
Click to expand...
Click to collapse
aniel300 said:
where you able to find out what was causing the lag and how to fx it? im having the same issue.
Click to expand...
Click to collapse
@ ALL who have this problem:
i had it too, and i was thinking that i have been the only one..went crazy because i didnt find the reason for this.
Solution:
1) You need the paid version of FKU
2) Open FKU, go into "CPU Manager"
3) Go into Governor Control
4) click on "input_boost_duration"
5) Change the value to: 1000000
6) Turn the button on for set on boot (so this value will be saved and applys again after a reboot)
7) then reboot the device, and voila
explanation:
on the stock kernel there is following setting:
if you touch the display, the Cpu will stay at 1497 Mhz for 3 Seconds and thats the reason why stock is smooth!
Franco changed this value for saving battery. his standard value is 0.04 Seconds on 1497 MHz, then it goes down to 300 if the cpu dont has to handle something.
So for example: if you scroll in the settings, and the CPU frequency goes so quickly down (after the 0.04 secs) there will be stutters
and with the 7 steps i mentioned above, you change the boost duration to 1 second. This means the device will not lag, because the CPU stays for 1 sec on 1497 Mhz and the battery impact isnt that big!
Please try this out and respond to me if it helped

aniel300 said:
where you able to find out what was causing the lag and how to fx it? im having the same issue.
Click to expand...
Click to collapse
Turns out, most of my problems were caused by the "Deep Darkness" CM theme. Builds of BlissPop and BenzoROM would be fine for a little while and then start to screw up, getting pissed off I would boot into CleanROM which didn't have any themes applied (I use MultiROM) and everything would work as expected for hours, no lags at all! I decided to switch to another theme in BlissPop to test my theory and voila no more lag!

GregNexus said:
@ ALL who have this problem:
i had it too, and i was thinking that i have been the only one..went crazy because i didnt find the reason for this.
Solution:
1) You need the paid version of FKU
2) Open FKU, go into "CPU Manager"
3) Go into Governor Control
4) click on "input_boost_duration"
5) Change the value to: 1000000
6) Turn the button on for set on boot (so this value will be saved and applys again after a reboot)
7) then reboot the device, and voila
explanation:
on the stock kernel there is following setting:
if you touch the display, the Cpu will stay at 1497 Mhz for 3 Seconds and thats the reason why stock is smooth!
Franco changed this value for saving battery. his standard value is 0.04 Seconds on 1497 MHz, then it goes down to 300 if the cpu dont has to handle something.
So for example: if you scroll in the settings, and the CPU frequency goes so quickly down (after the 0.04 secs) there will be stutters
and with the 7 steps i mentioned above, you change the boost duration to 1 second. This means the device will not lag, because the CPU stays for 1 sec on 1497 Mhz and the battery impact isnt that big!
Please try this out and respond to me if it helped
Click to expand...
Click to collapse
BEEN SEARCHING FOR A SOLUTION TO THIS FOR DAYS NOW AND THIS WORKED! THANKS! :good: