Database Info

[Q] boot up takes up to 7 minutes :(

hi guys.
I got a xoom 3G/wifi with rom tiamat "moray" band kernel tiamat 2.2.2 but it takes 7 minutes TO boot up the os
Anyone san help me?
Thanks in advance!

Everyone has that problem. Try out the rogue 1.4.3 rana kernel. That might improve your boot times.
Sent from my MB860 using xda premium

Originally Posted by bigrushdog
NOTE: to make boot times even faster, remove the following init.d scripts:
/system/etc/init.d/08zipalign /system/etc/init.d/09sqlvacuum /system/etc/init.d/10dalvikcleaner
You really don't need these on every boot. Maybe once a month, drop them back in the init.d folder, run them on boot, then take them out again.

Really? They have the SQL vacuum and dalvik cleaner on every boot? That is so pointless. Going to have to remember that once theam EOS puts out their official ICS ROM.
Sent from my MB860 using xda premium

oh i see i tought that was only for me :S
thank you all.
Hope that with ICS rom things will go smoother...

kiranshi said:
oh i see i tought that was only for me :S
thank you all.
Hope that with ICS rom things will go smoother...
Click to expand...
Click to collapse
Boot on ICS seems much faster.
Sent from my Xoom using xda premium

liftman- said:
Originally Posted by bigrushdog
NOTE: to make boot times even faster, remove the following init.d scripts:
/system/etc/init.d/08zipalign /system/etc/init.d/09sqlvacuum /system/etc/init.d/10dalvikcleaner
You really don't need these on every boot. Maybe once a month, drop them back in the init.d folder, run them on boot, then take them out again.
Click to expand...
Click to collapse
Dang.. tried this as I have INSANE slow boot times.. but it didn't seem to help. Though I didn't seem to have the SQL one.
Boot time just now.. was 17 minutes!!! Counting from the moment the boot animation starts, till the launcher home screen shows up. So actually longer.. going from off to usable. It seems to get longer every time. Last time I timed it, months back. It was about 6 minutes.
Is there something else I can check on??

you try the rogue kernel?

liftman- said:
you try the rogue kernel?
Click to expand...
Click to collapse
Just tried it... 9 minutes. Better... still quite long though.

i've the same time for reboot.
Try Rogue Kernel "Rana" it will be faster

what's your boot time on a factory rom and kernel?

liftman- said:
what's your boot time on a factory rom and kernel?
Click to expand...
Click to collapse
It was so long ago that I had stock anything on my Xoom that I never timed it. Haha It booted faster than the SGS Captivate I used at that time, I specifically remember commenting on that when I first got it.

How much space do you have left on system storage and your sd card. Whats the transfer rate?

CWM Recovery feature "Fix Permissions"

Not sure if many of you know this but there is a feature in CWMR called fix permissions. This is a handy feature to use if you're getting FC's that can't be cleared by going to /settings/applications/manage applications/name of app/clear data.
For examply, I just did a restore of RebelROM and the first time I went to open ICS Camera I got a FC. Cleared data, restarted the app, FC. So I booted into CWMR and fixed permissions and upon reboot the camera now works fine. Just a heads up for those who aren't familiar with this feature.

916x10 said:
Not sure if many of you know this but there is a feature in CWMR called fix permissions. This is a handy feature to use if you're getting FC's that can't be cleared by going to /settings/applications/manage applications/name of app/clear data.
For examply, I just did a restore of RebelROM and the first time I went to open ICS Camera I got a FC. Cleared data, restarted the app, FC. So I booted into CWMR and fixed permissions and upon reboot the camera now works fine. Just a heads up for those who aren't familiar with this feature.
Click to expand...
Click to collapse
What's an "FC"?
I tried the "Fix Permissions" feature just to see how it worked. It completed after a few minutes and everything seems to be working just as well as it did before.

daihard said:
What's an "FC"?
Click to expand...
Click to collapse
Force close
Sent from my MB865 using XDA

bigTINY779 said:
Force close
Click to expand...
Click to collapse
Ah, got it. Thanks!

daihard said:
I tried the "Fix Permissions" feature just to see how it worked. It completed after a few minutes and everything seems to be working just as well as it did before.
Click to expand...
Click to collapse
If you had no problems before fixing permissions, you won't see anything different. This is only for those having fc issues or other app related issues that arent fixed by more standard means. It's not a guarantee this will fix it either, just another thing to try along the way.
via Atrix 2/VictoryROM/XDA app

running counter
Hi there there is a counter running after the 'done!' message, any idea what is this?

Thanks man! fixed my problem
Gadgetz said:
Not sure if many of you know this but there is a feature in CWMR called fix permissions. This is a handy feature to use if you're getting FC's that can't be cleared by going to /settings/applications/manage applications/name of app/clear data.
For examply, I just did a restore of RebelROM and the first time I went to open ICS Camera I got a FC. Cleared data, restarted the app, FC. So I booted into CWMR and fixed permissions and upon reboot the camera now works fine. Just a heads up for those who aren't familiar with this feature.
Click to expand...
Click to collapse

gibbe2001 said:
Thanks man! fixed my problem
Click to expand...
Click to collapse
You got it!
Sent from my MB865 using XDA App

Just how long does it actually take? because mine has been at it since the past 5 minutes. :S

ryandigweed said:
Just how long does it actually take? because mine has been at it since the past 5 minutes. :S
Click to expand...
Click to collapse
It's taking long?
Mine just got through within like 10 seconds.
LIFE! IT'S WHAT YOU MAKE OUT OF IT!

Lifehacker7 said:
It's taking long?
Mine just got through within like 10 seconds.
LIFE! IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
Mine was not 10 seconds but it did get done with 3 or 4 minutes (Galaxy S3 CWM v5.5.0.4). I realized after posting that this was not a thread for my phone, but I thought I'd let you know that it was not instantaneous even on my device (also you can thank Google for sending me to this thread instead of my normal lurking grounds (S3 / Nexus 10)).

Can't find stable Android 4.x ROM/ Kernel

Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.

Unrelashade said:
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Click to expand...
Click to collapse
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2

mattlowry said:
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own

demkantor said:
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
Click to expand...
Click to collapse
Thanks guys! Fastboot says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
Click to expand...
Click to collapse
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha

Unrelashade said:
Thanks guys! Fastboot says:
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Click to expand...
Click to collapse
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2

Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium

You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?

mattlowry said:
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
demkantor said:
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
WeekendsR2Short said:
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
Click to expand...
Click to collapse
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.44.1107
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
Jun 27 2011, 14:08:29
Click to expand...
Click to collapse
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha

If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Sent from my HTC MyTouch 4G Slide using xda premium

Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2

A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Sent from my myTouch_4G_Slide using xda app-developers app

Unrelashade said:
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
Click to expand...
Click to collapse
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.

WeekendsR2Short said:
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
Click to expand...
Click to collapse
Thanks for the info.
demkantor said:
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Click to expand...
Click to collapse
Ok, right now I'll not try flashing bootloader since everything seems to be normal.
What I did to get last_kmsg:
Code:
Open terminal app
Enter "su" to get root privileges
Enter "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" to save current log.
Close terminal app.
I attached the last_kmsg.txt. What do I do with it now? I don't have knowledge to understand it.
mattlowry said:
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
I can't remember using a ROM that never crashed, but I'll try a stock ROM if nothing else works. However an old kernel of scverhagens CM 9.1 seems to work flawlessly if battery is not about < 15%. The newest r10 kernel on the other hand always immediately crashes when the phone is not charging. When charging I haven't experienced a crash yet. That's strange and makes me suspect my battery is the problem.
mojoffdawal said:
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Click to expand...
Click to collapse
Thanks! I guess I'll try an Anker since I have seen so much users here using it.

virtuous rom works great! when i had mine, i was running 4.0.3 overclocked to 1.5ghz. super stable too! daily driver for sure.
Sent from my SGH-T999 using xda app-developers app

Thanks, but the problem is I'm pretty sure that something's wrong with my phone...
I'll try virtuous ROM and a new battery though.

hope it works
Sent from my SGH-T999 using Tapatalk 2

So, I'm reviving this thread, because I stopped writing only because my phone was broken. Now it's back and I'm facing this problem again.
I've tried a lot of the 4.x ROMs here from the forums, but all of them rebooted or shut down after 5 - 10 minutes after flashing. I also tried some without flashing gapps even, but still the same symptoms. Also tested it with my new battery, nothing changed. Even the scverhagen CM 9.1 ROM rebootet shortly after flashing that worked longer previously (guess that was just by chance)
Now I've tried the original image and it works! Ugh. So what can be wrong, any ideas?

I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app

bit1 said:
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
It happened with both stock and new battery (Anker).
Thanks, update to latest TWRP had been my next try, if it didn't work now. But it does! Yeaaah so happy Thanks to everyone again. Almost three hours uptime and not a single issue so far!
To conclude: What I did:
Revert completely back to stock with BlueIX6's stock image (except that phone was still s-off and sdcard not wiped).
Then followed instructions to unlock bootloader, flash CWM recovery and finally flashed ROM (see sticky thread). Works like a charm!
In hindsight maybe radio made my phone unstable... I think it's the only thing that's different from now.

Android is upgrading. Every boot. ART only

Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?

stanc74 said:
Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?
Click to expand...
Click to collapse
Thats how it is every boot it has to pre compile the code for apps

Hmm...but in pre root form, this only happened the first time after selecting runtime. Now its happening every reboot! Is this supposed to be normal for a rooted phone?

stanc74 said:
Hmm...but in pre root form, this only happened the first time after selecting runtime. Now its happening every reboot! Is this supposed to be normal for a rooted phone?
Click to expand...
Click to collapse
I don't see that issue on my s2 skyrocket running 4.4 art. I'm not running art on my n5. I'm guessing it's an issue with the franko kernel, but that's just a guess

This happens to my N5 as well. Omni 12/01 nightly + Franco r14
Sent from my Nexus 5 using XDA Premium 4 mobile app

chill out guys, this is normal behavior when using ART.

This is not normal behavior at all on stock ROM. When you switch to ART, it only does the upgrade/compile thing on the first boot. Having it redo it after every reboot is probably a compatibility issue with the ROM you are running.

mdandashly said:
When you switch to ART, it only does the upgrade/compile thing on the first boot.
Click to expand...
Click to collapse
That's my recollection as well. It still is on stock ROM. But it looks like other people who have rooted are facing issues that might have arose from kernel or app issues.
I have already wiped cache and rebuilt dalvik fwiw. Also uninstalled titanium backup while no weird odex files are noted. Only Franco kernel left as last data point but I wanted to see if others faced this problem before taking the plunge to reinstall stock kernel

dorkythegreat said:
This happens to my N5 as well. Omni 12/01 nightly + Franco r14
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It does not happen on stock rooted for me either. I would suggest returning to stock rooted to use ART. According to Omni threads they are in nightlies so stuff is expected to be wrong.

Fwiw. I've flashed stock kernel, reflashed the patched libart.so (ie. Whatsapp compatibility fix) , reinstalled whatsapp. Still no joy.

Ah... from According to:
[url]https://code.google.com/p/android/issues/detail?id=61916
The problem is identified as an extra unbalance check between MonitorEnter / MonitorExit JVM instructions, which ART does and Dalvik doesn't. Some apps (such as Whatsapp) fail to have those balanced.
The fix will be probably fixed in AOSP sooner than later...
Sooo ... everybody relax and have a cup of tea (me included) :good:[/QUOTE]

stanc74 said:
Ah... from [URL="http://forum.xda-developers.com/showthread.php?p=47473296”]this thread about ART[/URL], this upgrading on every boot seems a known ART bug related to partially incompatible apps like whatsapp
Click to expand...
Click to collapse
Hmmm... sorry for the bad news but the problem discussed in that thread is unrelated with yours. We were discussing the (initial) whatsapp incompatibility.
BTW: Using ART here (Nexus 4), absolutely no problems now

it will depend on your apps. this is normal behavior. my n7 doesnt go through it, but my n4 does. they have different apps installed. my n5 goes yhrough it as well(but only 3 apps upgrading on a reboot). its fine if you want to freak out over it, but in reality it is normal.

I have 80 apps upgrading on reboot..and these are pretty standard apps.... This is quite a mysterious situation.
Good to know its happening. Perhaps next ota will address this...

stanc74 said:
I have 80 apps upgrading on reboot..and these are pretty standard apps.... This is quite a mysterious situation.
Good to know its happening. Perhaps next ota will address this...
Click to expand...
Click to collapse
my nexus 4 has 92 apps that upgrade after every reboot while on ART. 92 apps, out of 183 apps.

I’m using ART. Running Purity ROM with ElementalX. No long boot issue. I did have a long boot with apps optimization when I switched to ART the first time, but since then it boots normally and quickly.

Updated to 4.4.1. Had to flash stock boot and system IMG along the way. Updated, rooted and now it seems fine. Fast reboot with no data loss!

simms22 said:
chill out guys, this is normal behavior when using ART.
Click to expand...
Click to collapse
markdapimp said:
Thats how it is every boot it has to pre compile the code for apps
Click to expand...
Click to collapse
stanc74 said:
Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?
Click to expand...
Click to collapse
i am running stock 4.4.2 on N5 with bootloader unlocked and after each reboot i face the same cache rebuilt thing (android is upgrading) for all the user applications i have. Is it normal for stock rom too? have you seen any one on stock who is having otherwise?

I have this problem on my sony xperia sp running cm11, but it is happening since 5 days. Maybe it is the new version of a custom kernel, or link2sd.

Nope it's not normal. What else have you installed or flashed?
Sent from my Nexus 5 using Tapatalk

way to soft boot Android 5.1 or other way to clear system ram?

Hey all,
As you all know, in android 5.1 there's a new memory leak. The only work around is to reboot your device every once in a while. But, isn't there a working app or something to soft reboot your device or something ? This would be a lot faster then rebooting my phone twice a day.
Greets,
Swa100

keep the discussions contained.. there is already a thread for 5.1 discussion and one for memory leak..
and i dont think 30 seconds is too much . for reboot ofcourse .. and twice a day ? thats really strange ..

'Fast Reboot' work's and free at playstore...

CM memory cleaner cleans ram without a reboot. It's not a task killer though it can stop things booting

zerosum0 said:
CM memory cleaner cleans ram without a reboot. It's not a task killer though it can stop things booting
Click to expand...
Click to collapse
Which app is that exactly? And does that also cleans ram used up by "system"?

galaxys said:
'Fast Reboot' work's and free at playstore...
Click to expand...
Click to collapse
Does that one works with android 5.1? Because I've tried some others and those weren't working (reboot took forever, same effect as clearing the dalvik cache)

galaxys said:
'Fast Reboot' work's and free at playstore...
Click to expand...
Click to collapse
I've just tried this one. It causes the system to use even more ram. So it makes the leak worse

Xposed installer can do a soft reboot (Xposed framework doesn't work on 5.1 but the apk can still be used for this function).

swa100 said:
Hey all,
As you all know, in android 5.1 there's a new memory leak. The only work around is to reboot your device every once in a while. But, isn't there a working app or something to soft reboot your device or something ? This would be a lot faster then rebooting my phone twice a day.
Greets,
Swa100
Click to expand...
Click to collapse
Wakamatsu said:
Xposed installer can do a soft reboot (Xposed framework doesn't work on 5.1 but the apk can still be used for this function).
Click to expand...
Click to collapse
Yes, but its not recommended, because it causing battery drain.

zagorteney said:
Yes, but its not recommended, because it causing battery drain.
Click to expand...
Click to collapse
Rebooting uses a bit of battery but it doesn't cause drain.

Wakamatsu said:
Rebooting uses a bit of battery but it doesn't cause drain.
Click to expand...
Click to collapse
Wasn't talking about full reboot, but about soft reboot. There are some statements of few recognized developers (don't exactly remember if on GravityBox or Battery Drain thread), but they clearly explained that soft reboot doesn't allow all aplications to close properly and because of that system left to run some noended process in background.
So this is causing battery drain and not the act of rebooting itself.

swa100 said:
I've just tried this one. It causes the system to use even more ram. So it makes the leak worse
Click to expand...
Click to collapse
How so? All it does is free ram and yes I use it with 5.1.

Get cm cleaner. It has clear ram widget. Plus you can choose which apps run at boot
Sent from my Nexus 5

Yes, this is what developers have said. Please avoid soft reboots wherever possible.

USE THE APP I TOLD YOU ABOUT. TRY IT!not ? just it works
Sent from my Nexus 5