Maybe you could be so kind and help me.
Short strory: After i installed the CM10 V0.8.1 i was messing around with the CPU frequences.
As we all know the highest is 1000Mhz.
So it was working fine as i switched the options of the lowest frequence from 200/300 to just 450Mhz.
But after i tried to speed up my tablet by turning the lowest frequence to 1000Mhz it never started again after rebooting.
(So that way it could not run slower than 1000Mhz, as i thought.)
Just the usual "Lenovo" symbol at the start is shown ever since, that's all.
I already tried to reinstall the system. It didn't work. The same procedure didn't work after i deleted the cache, dalvik cache, etc..... I can still get into CWM!
Now, how can i get my tablet to work again?
Can anyone help me, please???
Tell me what more information you need! Model is the 16GB WE version with 3G Ericsson Card..
I have no backup, in case that would help.....
Thanks.
Any progress?
Sent from my Galaxy Nexus using Tapatalk 2
Related
Hi there, I'm on FreeX10 Beta4 with the latest camera hotfix, after patching the hotfix there were twice where I encounter my phone seemed to be stucked at 998mhz full load.
Realized that when my phone heats up all of the sudden. Checked through system panel found nothing was using up the processor but it's at full load on SetCPU its set to scale on-demand. Gotta reboot the phone then it's gone. Anyone had any idea whats going on? It was all fine before I applied the hotfix for the camera. Thanks in advance!
Sorry I've realized I've posted in the wrong section, can any mods move it over to the Q&A, Thanks!
Update: Used google goggles, and my proc is on full load again
Wondering also if anyone had similar problem to that, I can't post a reply on FreeX10's thread regarding this problem due to post count
Since the kernal is still the SE one, setcpu would not work.
aR_ChRiS said:
Since the kernal is still the SE one, setcpu would not work.
Click to expand...
Click to collapse
Hmmm that is just to check the scaling, but weird thing is that my processor goes up to max when I try to use google goggles, any idea what would be the problem? It just gets stucked at max clockspeed till I reboot my phone
I had this as well, there was some internal process using up most of the CPU all the time (something like xftwd-daemon).
I read that you can fix it by rebooting your phone, and it worked.
Apparently this happens on the first boot after wiping the cache or dalvik cache or something.
Happened a few times even after reboot. Wiped my battery stats and trying out now to see if it's still happening So far so good
I got my wife a Nook Color a while back, and installed CM 7.0 n it. It ran fine, and I had it OC'ed at 1100. Since then, I've installed 7.0.3, which gave me a wifi error. I decided to run Phiremod 6.3 (running great), but I have a strange issue.
When i go into performance settings to overclock, it freezes immediately after choosing any speed. I can't even change the governor from on demand to interactive without it freezing. It locks up so that I have to turn it off and back on again. No luck in changing the CPU speed. I never had issues before running at 1000 on previous dalingrin kernels, not sure why its acting up. I did do a complete wipe of system before installing.
Can i try using SetCPU or something similar instead, or should I be looking at something else?
Try setcpu like you said. If u have the time tho, why not wipe the whole thing and try installing phirrmod again?
Tried it again, with the same result. Not sure what's going on there, but I'll try SetCPU and report back. Thanks for the reply.
RampageRR said:
Tried it again, with the same result. Not sure what's going on there, but I'll try SetCPU and report back. Thanks for the reply.
Click to expand...
Click to collapse
So how did Setcpu work out for you?
RampageRR said:
I got my wife a Nook Color a while back, and installed CM 7.0 n it. It ran fine, and I had it OC'ed at 1100. Since then, I've installed 7.0.3, which gave me a wifi error. I decided to run Phiremod 6.3 (running great), but I have a strange issue.
When i go into performance settings to overclock, it freezes immediately after choosing any speed. I can't even change the governor from on demand to interactive without it freezing. It locks up so that I have to turn it off and back on again. No luck in changing the CPU speed. I never had issues before running at 1000 on previous dalingrin kernels, not sure why its acting up. I did do a complete wipe of system before installing.
Can i try using SetCPU or something similar instead, or should I be looking at something else?
Click to expand...
Click to collapse
I had to do a complete wipe of all data...Phiremod is running awesomely
Here's an issue I just noticed late last night. My CPU seems to be stuck at max. I've tried different governors, wiped cache/dalvik and reflashed kernel and rom. I also killed all running apps to see if an app was causing it, to no avail.
Here's what really stumps me, my battery life seems fantastic. Not what I'd expect if my CPU is running at 100%. Could there be an issue with detecting CPU speed? As I mentioned before, trying different governors doesn't help with scaling but I notice when I select "powersave" my CPU jumps from max to the minimum value and stays there, still not scaling.
Before someone mentions I did search before posting. Went through the threads, tried the suggestions within and still have the problem. Hence why I'm posting here now.
Am I overlooking something? Any help will be appreciated, thanks!
Edit: My current rom and kernel are in my sig.
so are you monitoring this via setcpu on Decks?
alaman68 said:
so are you monitoring this via setcpu on Decks?
Click to expand...
Click to collapse
Yes I am, is there a known issue?
My understanding is that having both setcpu and the native CPU performance running will result in some conflict. that is probably the problem, but I don't know how to monitor the scaling with the native performance. so i see what you are trying to do.
I never run setcpu on CM7 or Decks because it is built in, but if the battery life is alright, it would appear the built in takes precedence.
Is there a good way to monitor the CPU without setCPU? Thanks
cesjr02 said:
Is there a good way to monitor the CPU without setCPU? Thanks
Click to expand...
Click to collapse
check out "system panel"
edit: or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency.
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
My CPU doesn't scale correctly either. Its either running at MAX, Deep Sleep, or 245mhz. Never does it use the in between frequencies no matter what govenor I use(I have tried them all). I use CPU Spy to check scaling and No Frills CPU to change the governor both are from the market.
cesjr02 said:
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
Click to expand...
Click to collapse
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
alaman68 said:
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
Click to expand...
Click to collapse
Thanks, says the time spent at 499 MHz is 92.51%. I don't think underclocking is the issue. If I overclock to 1113MHz it will peg there as well. Seems to only go 100% when screen is on however according to the system panel app. I'll try your suggestion in (#2) and report back.
Tried reflashing the rom without wiping. Still have the same issue. So odd. I'll try a different kernel just to see if that helps, but I'd hate to part with my 3.3.7 LEE kernel.
Last thing I can think of is doing a full wipe, but I'd like to avoid that if I can.
Definitely experiencing the problem with other kernels. I'm out of ideas.
Did you try tiamat 4.1.0? I'm using it now and the battery life is right there with 3.3.7.
Sent from my PC36100 using XDA App
Did you restore any apps with titanium backup by chance?
Sent from my PC36100 using XDA App
By the way, I appreciate all your help alaman68.
Tiamat 4.1.0 was the other kernel I tried. No luck. Also I've never used titanium backup to restore apps. I'm stumped as to why my CPU won't scale anymore. The Android System seems to be using as much as I allow it.
Trying, you could try a sense rom for a day and check the scaling for a benchmark.
Is there anything else you are running? Undervolting, v6... Anything else?
Not undervolting as my phone never liked it. Nor running V6 or any other scripts either. I'll try flashing a sense rom, see if I have the same problem there. Or else, think doing a full wipe and reflash everything would help?
if all else fails, a clean flash won't hurt. Even get a new download. Gotta ask, did everything properly? you using amon_ra recovery? did you download any new apps when that started happening?
I may just have to. I suppose there's always a chance I made a mistake somewhere, but I've been at this rooting/flashing thing for a long while. Thing is, everything was fine up until I noticed it last night.
I'll do a clean install. I can always nand restore if it doesn't work. (Save me the time to set up everything.)
I'll report back
Did a clean install and guess what, my CPU is scaling again! There must have been a conflict somewhere. Thanks again alaman68 for all your help and suggestions. Sometimes these phones get gremlins I tell ya.
For the past few days I seemed to be getting a lot of random force close errors on my legend, with no discernible pattern. This continued up to the point where all of a sudden pretty much every app crashed and wouldnt remain open more than a few seconds. I then tried to reboot, and since then the phone just gets stuck in a bootloop at the rom loading screen. I've tried four or five different roms, all with the same error.
I would assume this was a memory/processor malfunction, however the fact that I can still flash roms and make backups with clockwordmod suggests to me the hardware could be ok? Does anybody know of some sort of diagnostic rom I could run to check this?
Thanks guys
Matt
Here's some stuffs to check out, don't over clock, Max 600mhz, not every phone can be oc'd, maybe even try less processor speed say 480 MHz. Have u been ocing your phone on extream speed for long time, like 806+ mhz, that will kill a processor for sure.
Have you done a fix permissions with clockwork mod? This can help heaps with fc's.
If using an ext partition which type are you using 2 3 or 4, apparantly if your using ext4 and your phone is crashing it can cause even more issues.
Using lots if widgets on your screens?
Have you tried a different/new SD card?
My understanding is your rom space can eventually fail if your flashing lots n lots of roms, but you said you can flash successfully, so that sounds good.
There is a few to start you off.
Sent from my Legend using XDA
Amazingly I have managed to completely fix the problem. In a last moment of desperation before buying a new phone I decided to try wiping the battery stats, simply because I had never tried it before (didnt see the need to). Miraculously this did the trick, and I managed to boot into cyanogen 6!
I then restored a backup I made when the phone first died, and confirmed it was still broken as I expected. I then wiped the battery stats , and viola it worked!
I have no idea what is stored in the battery stats, but I am very surprised this made a difference. Thanks for your help anyway ranger.
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Ethan_Kok said:
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Click to expand...
Click to collapse
I upgraded to the latest stable CM10.1.2 release and have started getting random sleep of deaths (SD install). I've had them while plugged in, not plugged in, with screensaver on, with screensaver off (thought maybe keeping it active would help prevent)... I can't seem to find a pattern. I've tried every nightly since and am still seeing it. I tried rolling back to the first stable release, still there. I'm going to try rolling back from 1100 MHz to 1000, then 800, to see if that helps at all.
I'm a total newb to debugging this thing, but I'm happy to try and pull any logs to post if someone can point me in the right direction (I've looked around before on how to do this but get confused easily). Also, I'd be willing to try a clean install, but don't want to go through the hassle of reinstalling everything again. If there is a quick way to backup programs, I'm all ears.
The good news is, it runs great when it's up. Quite smooth. Pretty awesome stuff.
I believe Titanium Backup should back everything up.....
I have downgraded to CyanogenMod 7.2 as I am very exasperated with this issue, the short battery life and lagginess that the upgrade has brought.