Database Users

slow

Hello
Does anyone have any idea why the device takes 4 seconds to come on ??????
the artix rooted

Mine takes less than a second. There have been a few times when it took a little longer, but that's pretty rare.
I'm rooted, but I stuck with Blur.

gamliel said:
Hello
Does anyone have any idea why the device takes 4 seconds to come on ??????
the artix rooted
Click to expand...
Click to collapse
Are you underclocking? I have SetCPU set to lower mhz's when the screen is off, which I noticed did cause it to take longer to come on, once the profile was set.

underclockink ??? what is this ???

gamliel said:
underclockink ??? what is this ???
Click to expand...
Click to collapse
Its when you set it so the CPU can't go above a certain mhz to save power. Opposite of that is over clocking which makes the CPU go faster.
Sent from my MB860 using Tapatalk

Wow mine easily takes 15 to boot
Completely stock

If you installed live wallpapers from market don't use them, I had same problems with some, sometimes took some time to wake up. However the stock ones are fine.
Sent from my MB860 using XDA App

Techcruncher said:
Wow mine easily takes 15 to boot
Completely stock
Click to expand...
Click to collapse
I think what he means is when the phone is already on, to wake the screen.

You right.
I try all the think that the guys said .....
but it is not help to me.
it take sometime. More then 4 second.
why????????
The device is clean. Only Rooted no apps and no wallpaper

I've been having issues with this too. I definetly hope this gets resolved at some point. My captivate was on as soon as I hit the button.

Deadly Issue ;( !! (UPDATE: occurs with the stock kernel)

Hello everyone...
I have 2 issues with my Transformer
the first one is that whenever i leave my Transformer for couple hours it shuts down !! doesn't occur when charging but it does when it's not.. even when the battery is around 80% !! i had this problem with ALL kernels except the stock kernel which i don't wanna use !! also had this problem for around 2 months...
the second one happened today when i left my Transformer "Charged" at 100%.. and after couple of hours i found it shut down but when i powered it on again i found the battery 27% !!
i went to the battery stats and found that battery was decreasing slowly and there was a gap (which means that it turned off) and after the gap it shows the battery low !! it happened within 6 hours !!
Please help me if you can... !! I'm using Revolver ROM 3.9.5 and "Blades Kernel 3" that comes in the Revolver Parts...
UPDATE : The problem occurs with the stock kernel !!

This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?

The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.

Cernunnoz said:
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
Click to expand...
Click to collapse
I never heard of this app... Just like i said it doesn't happen with the stock kernel !!
But the reason I'm using other kernels is because i wanna Overclock !!

a.mcdear said:
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Click to expand...
Click to collapse
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !

sounds like a silly question but i have seen it alot. Are you charging through a computer(USB) or wall?

It could be related to setCPU and the according profiles. Just recently I saw that my profiles were messed up after updating ROM and kernel. Might be worth a shot.

Reinstall stock kernel Issue #1 fixed.
Issue 2 sounds like charger shut off and left TF on not charging.

You've pretty much explained to yourself why the thing is shutting down.. It works fine on the stock kernel but not one that is letting you overclock.. Sounds to me like you are either overclocking more than it can handle or undervolting to much or both.
I can almost bet that its not shutting down completely and its just going into a state that the screen is off but the OS is hung up, so its not responding to you turning the screen on.. This would explain why the battery seems to be dieing when its sitting idle.
Not sure about it dieing while its plugged in other than maybe a fluke.

I don't wanna use the stock kernel.. it's really slow !!
and i over clock to 1.4 ghz only since i can't overclock more than that because it restarts itself endlessly if i overclocked more than 1.4 ghz !! i undervolted about -25 or -50.. not much !!
Yes i charge it on a wall or anything but NOT on my computer...
How can i change profiles in setcpu ??

xMini said:
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
Click to expand...
Click to collapse
No no you misunderstood! DONT let the battery hit 0.

First, you need to use more exclamation points !!!!
sounds like you are suffering from deep sleep issues. What rom are you running? also, have you tried running a custom kernel and not overclock it? You have several variables that can be influencing your issues, start isolating what may be causing your problems. the kernel seems the must likely of culprits, I would clear the overclock and install setcpu and run it for a but and see if you can replicate your issue.
Sent from my GT-I9000 using XDA App

Just try the non stock kernel, oc it but dont uv it, not all devices can handle uv, even if it is only a little bit. Even take it back too 1000mhz and try to increase the uv and oc by little bits at a time to see exactly what your transformer can handle. I think its the uv thats causing the problems. Experiment a bit and youll find the sweet spot.

I'm using Revolver ROM and i mentioned that...
I've never undervolted till yestersay.. maybe it caused the second problem
I set the clock speed at 1ghz and i'm waiting to see if anything changes..

Yeah... the problem still occurs even after setting the clock speed at 1ghz and default voltage !! using clemsyn kernel ver 22...

Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk

colonel187 said:
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I'm guessing my device is bad and it's Asus' problem ! i tried setting the clock speed at normal 1Ghz but the problem still occurs !! the reason i overclock is that because with the stock kernel i get slower web browsing and slower flash playback and slower overall performance!! however I'm back on the stock kernel to check out if the problem is gone or not...
I doubted my device couple months ago... because I've seen everyone overclock their devices at 1.6 GHz Without any issues !! but when i try to overclock a little bit more than 1.4 GHz it restarts itself endlessly !!

Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App

ropaisoft said:
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you exactly mean by "for now" ??
and how can i even send it to ASUS ??! i don't live in the USA

xMini said:
I'm guessing my device is bad and it's Asus' problem !!!
Click to expand...
Click to collapse
You stated in an earlier post that the problem does not show up in the stock ASUS setup, but only with a custom ROM and Kernel. How does that make it ASUS' problem. If you buy a car that says it runs on 87 octane fuel and you put 100% nitro methane in the tank and it blows up it is not the manufacturers fault.

note on steriods???

i just noticed this morning after unplugging my note that even though my note is going into deep sleep the battery drain is still way too much as compared to the previous day...
i checked cpuspy and at first didn't register anything odd except that it goes into deep sleep.. after a second glance only then i realized that instead of running at 200mhz my note was running at 1000mhz during charge..
has anyone here experienced this before?? although i noticed that it seems to be a lot snappier now
i just can't help but worry what lasting damage it may be doing to the processor... and the fact that even though it goes into deep sleep i'm losing about 5% of juice for every 15-20 mins.
see screenshots below. the first was when i unplugged it from the charger and the second... after going to deep sleep

see screenshots
sorry forgot to attach screenshots

scarlet_sg said:
i just noticed this morning after unplugging my note that even though my note is going into deep sleep the battery drain is still way too much as compared to the previous day...
i checked cpuspy and at first didn't register anything odd except that it goes into deep sleep.. after a second glance only then i realized that instead of running at 200mhz my note was running at 1000mhz during charge..
has anyone here experienced this before?? although i noticed that it seems to be a lot snappier now
i just can't help but worry what lasting damage it may be doing to the processor... and the fact that even though it goes into deep sleep i'm losing about 5% of juice for every 15-20 mins.
see screenshots below. the first was when i unplugged it from the charger and the second... after going to deep sleep
Click to expand...
Click to collapse
Try restarting and see it is softens up
Sent from my GT-N7000 using xda premium

tried it... even did a hard reset by pulling battery out... still the same...
now clueless on what next...

See what processes are running. And kill some unneccessary ones?
Sent from my GT-N7000 using XDA

scarlet_sg said:
tried it... even did a hard reset by pulling battery out... still the same...
now clueless on what next...
Click to expand...
Click to collapse
ANy new apps that u installed recently ?
Normally , rogue process is going to call an abnormal battery drain ,,,download some sort of process,app moniter and see which process is running and taking most of the CPU time......My guess is that it has to be one of the apps that you have installed or started which is causing this

That was what I thought initially but I don't remember installing anything these past few days as I just froze a few bloatware and was monitoring the device for any issues.
The last thing I remember changing was some setting under the development concerning background process.
Hmmmn. Maybe I'll put it back and see.
Really appreciate the help guys. I'll keep you updated.
Sent from my GT-N7000 using XDA

Kernel and rom version pleeez
Sent from my GT-N7000 using Tapatalk 2

scarlet_sg said:
The last thing I remember changing was some setting under the development concerning background process.
Hmmmn. Maybe I'll put it back and see.
Click to expand...
Click to collapse
this may be the reason - afair this setting kills each process after you leave it, so in readily you might have ended with a constant loop of processes being closed and then restarted by system
Sent from my GT-N7000 using xda premium

i unchecked the limiting of background process but still the same... cpu is still running at 1000mhz most of the time
i did a hard reset by turning off and pulling the battery for a few minutes... still the same although the note still goes into deep sleep but hardly uses other cpu speeds except for 1000mhz...
i tried freezing some of my apps and games, those which i suspect might have required 1000mhz to run but still the same...
i guess i'll just have to wait and see for a little while if this changes...
i'm now thinking of reverting back to GB... since the battery drain for ICS is such a let down and with this problem... i'll give it a couple more days

what ROM are you running?
anyway something in the governor seems to have changed ,your case seems to be a performance governor.
try installing set cpu and set minimum to 200 ,max to 1400 ,and the governor to "on demand"
should fix things for you

IM on stock Ics lp9. I haven't root yet after I upgraded ota.
Set CPU requires root ain't it?
Sent from my GT-N7000 using XDA

scarlet_sg said:
IM on stock Ics lp9. I haven't root yet after I upgraded ota.
Set CPU requires root ain't it?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
yes it does ,but if you're not rooted then the governor couldn't possibly have changed by you !!
could it be a bug in lp9? I heard that ICS have some battery issues
how long were you running LP9 before noticing this issue?

Well, havent heard it from that rom. Bring it back
Sent from my GT-N7000 using Tapatalk 2

it might be the fault of some rogue app running in background, did you check with betterbatterystats?
Sent from my GT-N7000 using xda premium

I was using lp9 for about 2 Weeks after I started noticing the CPU usage
Couldn't find a fix so I reverted back to rooted lc2 GB
With all the issues with Ics - battery drain, fc's and mmc bug and now this CPU overclocking felt it wasn't worth it.
Now the note is sleeping like a baby. Battery is back to its efficient self. I'm getting 3 days on one full charge.
Will just wait for an update on official Ics.
Appreciate all the help guys.
Sent from my GT-N7000 using XDA

[Q] Paranoidandroid & trinity kernel - how to log freezes

Hi,
I have paranoid android (2.1.1) and morfics Trinity kernel (111) running on my n7.
Sometimes when I come home from work and pick up my nexus it is warm and I have to press the power button for 10 seconds to reboot device as it won't wake up. After powering on, the battery level is much lower than it should be and battery usage tells me that the android os used up a lot.
I wondered if there is a way to track these freezes or whatever they are to find out what is causing them.
Could anybody give me some advice on that?
Thanks,
Nimdastas

nobody?
Nobody can help me on this?

try raising your voltages slightly. the tsvz series of trinity kernels are undervolted, it might be too much undervolting for your device. try upping your voltages slightly until you find a stable place for your device. or try a ts trinity kernel, they arent undervolted. a96 is one of my favorite.

Nimdastas said:
Hi,
I have paranoid android (2.1.1) and morfics Trinity kernel (111) running on my n7.
Sometimes when I come home from work and pick up my nexus it is warm and I have to press the power button for 10 seconds to reboot device as it won't wake up. After powering on, the battery level is much lower than it should be and battery usage tells me that the android os used up a lot.
I wondered if there is a way to track these freezes or whatever they are to find out what is causing them.
Could anybody give me some advice on that?
Thanks,
Nimdastas
Click to expand...
Click to collapse
I use BetterBatteryStats from the play store to track exactly what keeps my N7 from deep sleep mode.
Sent from my Paranoid Nexus 7

RockNrolling said:
I use BetterBatteryStats from the play store to track exactly what keeps my N7 from deep sleep mode.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
he's experiencing sod, not a problem with deep sleep.

simms22 said:
he's experiencing sod, not a problem with deep sleep.
Click to expand...
Click to collapse
Thanks for clarifying. But what do you mean by sod? Is that an abbreviation? I would think BetterBatteryStats could help diagnose whatever is draining his battery, regardless of what it's called.
Sent from my Paranoid Nexus 7

RockNrolling said:
Thanks for clarifying. But what do you mean by sod? Is that an abbreviation? I would think BetterBatteryStats could help diagnose whatever is draining his battery, regardless of what it's called.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
sod is an abbreviation, sleep if death. its when you turn your screen off then it won't turn back on when you try to turn it on. mostly its a symptom of too much undervolting for the device.

simms22 said:
sod is an abbreviation, sleep if death. its when you turn your screen off then it won't turn back on when you try to turn it on. mostly its a symptom of too much undervolting for the device.
Click to expand...
Click to collapse
Thanks for explaining! I understand now. I find it odd that different Nexus 7s would respond in very different ways to Trinity TSVZ a111. I'm running that kernel on my N7 with absolutely no issues.
Sent from my Paranoid Nexus 7

RockNrolling said:
Thanks for explaining! I understand now. I find it odd that different Nexus 7s would respond in very different ways to Trinity TSVZ a111. I'm running that kernel on my N7 with absolutely no issues.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
actually, every device differs. some can overclock or undervolt more than others. I had issues when with some games on a110 because it was slightly too undervolted for me, while others had no problems, and some had sod. a111 runs perfect for me now, since the core voltages were slightly raised, but some still have sod. bumping the voltages up slightly helps most.

simms22 said:
actually, every device differs. some can overclock or undervolt more than others. I had issues when with some games on a110 because it was slightly too undervolted for me, while others had no problems, and some had sod. a111 runs perfect for me now, since the core voltages were slightly raised, but some still have sod. bumping the voltages up slightly helps most.
Click to expand...
Click to collapse
Well, I definitely learned something new today. Thanks for sharing your expertise!
Sent from my Paranoid Nexus 7

thanks
Thanks for the explanation, finally I know what sod in the main thread means
And concerning the logging, even if I don't need it anymore, the battery stats app should help me? I suspect that it won't be able to log much when it comes to such deep issues.
Thanks,
Nimda

Nimdastas said:
Hi,
I have paranoid android (2.1.1) and morfics Trinity kernel (111) running on my n7.
Sometimes when I come home from work and pick up my nexus it is warm and I have to press the power button for 10 seconds to reboot device as it won't wake up. After powering on, the battery level is much lower than it should be and battery usage tells me that the android os used up a lot.
I wondered if there is a way to track these freezes or whatever they are to find out what is causing them.
Could anybody give me some advice on that?
Thanks,
Nimdastas
Click to expand...
Click to collapse
Answering the question, yes, there is a way to track/log the freezes. There is decent summary here : http://code.google.com/p/tegraowners-ics-rom/wiki/How_to_get_logs
You could also download an app like bootleg uptime to grab logs for you.

Thanks all for your help, and thanks irishrally for the tip!

[Q] Why is Android System consuming so much batter nowadays?

It didn't used to be like this. But now I get a pretty bad drain from Android System. It would be the second highest battery consumer, and would be using the CPU for quite a lot.
I'll post my battery screens and BBS stats soon. But for now, anyone else getting this issue? I'm on CM10.1 M1, tried different nightlies but still getting this f*cking problem. It's driving me crazy.

starscream92 said:
It didn't used to be like this. But now I get a pretty bad drain from Android System. It would be the second highest battery consumer, and would be using the CPU for quite a lot.
I'll post my battery screens and BBS stats soon. But for now, anyone else getting this issue? I'm on CM10.1 M1, tried different nightlies but still getting this f*cking problem. It's driving me crazy.
Click to expand...
Click to collapse
try a different rom besides for cm, or try a different kernel. no such issue here with the rasbean jelly rom/trinity kernel. android system stays between 2-6% here.

simms22 said:
try a different rom besides for cm, or try a different kernel. no such issue here with the rasbean jelly rom/trinity kernel. android system stays between 2-6% here.
Click to expand...
Click to collapse
Alright, I'll give Rasbean Jelly ROM a try.

If you look at my attached screenshot, you'll see what apps are included in Android System. Maybe you use one of those apps a lot? What % is your Android System at by the way?
Sent from my Nexus 4 using xda premium

android88 said:
If you look at my attached screenshot, you'll see what apps are included in Android System. Maybe you use one of those apps a lot? What % is your Android System at by the way?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I have the exact same list of packages for Android System. Right now my phone's been on for an hour and it's at 21%, with a CPU total of 15 mins and it kept my phone awake for 4 minutes.
I dunno why it's like this all of a sudden. A week ago it was completely fine.
The thing is, I did clean re-flashes already and it still does that. I even wiped system. How do I properly reset my phone to get a clean slate? Should I RMA my phone if this issue doesn't go away?
Edit:
Just flashed MiNCO v6, and the drain seems to subside a little bit, but I need more time with my phone to judge better. Sigh, I'm missing CM's quick reply feature already!

starscream92 said:
I have the exact same list of packages for Android System. Right now my phone's been on for an hour and it's at 21%, with a CPU total of 15 mins and it kept my phone awake for 4 minutes.
I dunno why it's like this all of a sudden. A week ago it was completely fine.
The thing is, I did clean re-flashes already and it still does that. I even wiped system. How do I properly reset my phone to get a clean slate? Should I RMA my phone if this issue doesn't go away?
Edit:
Just flashed MiNCO v6, and the drain seems to subside a little bit, but I need more time with my phone to judge better. Sigh, I'm missing CM's quick reply feature already!
Click to expand...
Click to collapse
It's not a hardware issue. The longer the phone is on, the lower % the Android System will be at (obviously lol) because the other stuff is averaging it out. You can also ry changing your kernel.
About the messaging quick reply, just replace MiNCO's mms.apk with CM's.
Sent from my Nexus 4 using xda premium

android88 said:
It's not a hardware issue. The longer the phone is on, the lower % the Android System will be at (obviously lol) because the other stuff is averaging it out. You can also ry changing your kernel.
About the messaging quick reply, just replace MiNCO's mms.apk with CM's.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for all your suggestions!