I am running bruce nightly cm10 build/08-12.. when my screen times out most times I cant get it to come back on....I have to bull the battery to restart... does anyone know how to fix this?? Thank you
handman29 said:
I am running bruce nightly cm10 build/08-12.. when my screen times out most times I cant get it to come back on....I have to bull the battery to restart... does anyone know how to fix this?? Thank you
Click to expand...
Click to collapse
Format your SD Card (Save all the data on your computer first)
If that doesn't work, just wait until a more stable build of CM10 comes out. It's a beta. These things happen in a beta.
Does the capacitive buttons stay lit while it does this? I had the same issue over the last 2 updates. Did a wipe all except SD card from 4ext recovery and did a clean install. No problems yet.
Or try manually clock your minimum CPU frequency to 384mhz as according to Bruce himself by:
After first boot go to settings>performance>processor and set the minimum CPU frquency to 384mhz then tick 'set on boot'.
Then on every boot after that go to settings>developer options and tick 'disable hw overlays'
Click to expand...
Click to collapse
I also had that problem but fixed by following this
Minimum frequency
Hi,
Set the minimum frequency worked for me.
Thanks
Sent from my SGH-T999 using xda app-developers app
Related
I am currently running Peter's ICS 12/6 nightly with Matrix kernel 16.0. Every now and then my screen won't automatically sleep. I have settings under display to sleep after 15 secs, yet my screen will stay on until I manually shut it off. Is this a bug, or a setting in NStools that I have to adjust? Is anyone else experiencing this?
thanks
hi.
I had that same prob. I just flashed the v.16.5 and, somehow, everything get back to normal, u can try the same or just set all the option in the NStools to default and see if this solves it.
Cheers
if i helped u somehow, hit thanks button pls.
kalitza said:
hi.
I had that same prob. I just flashed the v.16.5 and, somehow, everything get back to normal, u can try the same or just set all the option in the NStools to default and see if this solves it.
Cheers
if i helped u somehow, hit thanks button pls.
Click to expand...
Click to collapse
I didn't even realize that V 16.5 was out lol. I will try that and see what happens, thanks
unomedmen1 said:
I didn't even realize that V 16.5 was out lol. I will try that and see what happens, thanks
Click to expand...
Click to collapse
anytime
I recently flashed the cm10 alpha 2 build it worked great I loved it, still do love it. I made 810 MHz the max cpu speed and 192 the min (to try and save battery). I was playing fish live (gay I know, but how can you resist a virtual fish tank?) all of the sudden cm10 boot screen came up never booted, so I held down the power to restart and when I did everything worked great excepet it said messaging has stoped. Every time I click to open my texts nothing happens any ideas?
benj23673 said:
I recently flashed the cm10 alpha 2 build it worked great I loved it, still do love it. I made 810 MHz the max cpu speed and 192 the min (to try and save battery). I was playing fish live (gay I know, but how can you resist a virtual fish tank?) all of the sudden cm10 boot screen came up never booted, so I held down the power to restart and when I did everything worked great excepet it said messaging has stoped. Every time I click to open my texts nothing happens any ideas?
Click to expand...
Click to collapse
try reflashing cm10 alpha 2 and random reboots shuold be expected since this rom is in alpha stage
chinthekng said:
try reflashing cm10 alpha 2 and random reboots shuold be expected since this rom is in alpha stage
Click to expand...
Click to collapse
By reflashing you mean, wipe factory data bla bla bla reflash?
I would try clear data/cache for the messaging app. I believe there is also a "framework" process you can clear cache/data to fix that problem....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
benj23673 said:
By reflashing you mean, wipe factory data bla bla bla reflash?
Click to expand...
Click to collapse
Try going through the installation process for cm10 without wiping data first and if that doesn't work then reflash with wiping
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
My CPU stays maxed out at 1400 and it doesn't sleep for some reason I tried changing kernels and rom and full wipe but nothing has helped. This has just started occurring the past week or two and I didn't install anything new. Can someone help?
Sent from my GT-N8000 using xda premium
caaznkid said:
My CPU stays maxed out at 1400 and it doesn't sleep for some reason I tried changing kernels and rom and full wipe but nothing has helped. This has just started occurring the past week or two and I didn't install anything new. Can someone help?
Sent from my GT-N8000 using xda premium
Click to expand...
Click to collapse
When you switched roms did you do a dirty install? Or did you do a factory reset then install then wipe dalvik and cache? If you did it dirty possible the problem app followed you
I did a fresh install. The only reason I wiped it in the first place is because thus problem came out of nowhere. Better battery stats shows me it's due to media scanner service that my tablet is doing this.
Sent from my GT-N8000 using xda premium
Question
Dear android experts
I'd like to ask, I have Galaxy Note 10.1 GT-N8000 and having problem in starting app ASPHALT 7 1.0.6, this app always stopped.
My question were:
1. What if my VGA card ( MALI ) is damaged??? does GT-N8000 device still could be started or couldn't be started????
2. what happened to my GT-N8000? because I just changing Jelly Bean version every month, and never got problem, and now I really got a problem, this time from XXCMD1 Multi-CSC Deodexed to XXCME2 Multi-CSC Deodexed downloaded from the XDA forum. from XXCMD1 asphalt 7 1.0.6 played smoothly then I install XXCME2 and asphalt 7 1.0.6 run smoothly, the last time when I feel that XXCME2 wasn't too good and I do the
1. 2x Wipe data / Factory Reset.
2. 2x Wipe Cache
3. 2x Wipe Dalvik Cache
4. 2x in each, Format SDCard, Format Preload, Format Data, Format System, Format Cache
5. Before install XXCMD1 Multi-CSC deodexed.zip I did a Wipe data / Factory Reset again. Then install
All of this were done using CWM 6.0.3.1
After install XXCMD1 my asphalt 7 1.0.6 could not run anymore, and always said app has stopped. only this app could not be started. all other games still could be started. Now I reinstall XXCME2 Multi-CSC deodexed and asphalt 7 1.0.6 still could not be started too.
What happened to my GT-N8000. Does device always changing OS could damage GT-N8000 hardware???
Thank you so much. :crying:
lmao, thanks for hijacking my thread....I think your problem lies more with the asphalt game. If your GPU was damaged then you'd see a lot of artifacts and a lot of other games would crash too.
Also, I fixed my wakelock maxed CPU frequency problem.
Downloaded an app called SGS toolbox and used to to delete corrupt images on SD which fixed the media scanner problem. Now my tablet can sleep in peace. :good:
thank you so much for the answer. Glad to hear your problem solved.
caaznkid said:
My CPU stays maxed out at 1400 and it doesn't sleep for some reason I tried changing kernels and rom and full wipe but nothing has helped. This has just started occurring the past week or two and I didn't install anything new. Can someone help?
Halo, I'd like to know how to detect CPU stays maxed??? because I never install any tools apps, only a root explorer.
Thanks
Click to expand...
Click to collapse
pikwan80 said:
caaznkid said:
My CPU stays maxed out at 1400 and it doesn't sleep for some reason I tried changing kernels and rom and full wipe but nothing has helped. This has just started occurring the past week or two and I didn't install anything new. Can someone help?
Halo, I'd like to know how to detect CPU stays maxed??? because I never install any tools apps, only a root explorer.
Thanks
Click to expand...
Click to collapse
mine came with A application called system and you can look at the speed there.
Click to expand...
Click to collapse
What are the best settings for the TF101 in the Performance menu on KatKiss 4.3?
Like CPU settings, I/O settings and ZRAM enabled or disabled?
I have mine set to:
Interactive
312 MHz
1504 MHz
SIO
ZRAM OFF
Putting your min to 216 may cause SOD and RR. It will still go down to deep sleep if idle. It is stable at 1600 on and 1640 for mine (have not tried 1704) but it gets quite warm.
I used to use SmartassV2 on 4.2, but on this kernel it sticks at max CPU and never slows down.
I tried ZRAM ON and did not notice any difference so I turned it off.
Try the OC values and see what works for yours. Some tablets are more stable than others at different clock values so try some and see what happens. I would recommend flashing the FSYNC_ON.zip from the thread just incase you bet a RR or SOD that you do not risk corrupting the /data/ partition.
frederuco said:
I have mine set to:
Interactive
312 MHz
1504 MHz
SIO
ZRAM OFF
Putting your min to 216 may cause SOD and RR. It will still go down to deep sleep if idle. It is stable at 1600 on and 1640 for mine (have not tried 1704) but it gets quite warm.
I used to use SmartassV2 on 4.2, but on this kernel it sticks at max CPU and never slows down.
I tried ZRAM ON and did not notice any difference so I turned it off.
Try the OC values and see what works for yours. Some tablets are more stable than others at different clock values so try some and see what happens. I would recommend flashing the FSYNC_ON.zip from the thread just incase you bet a RR or SOD that you do not risk corrupting the /data/ partition.
Click to expand...
Click to collapse
What settings if I don't want to flash FSYNC_ON.zip because it will make the I/O run slower?
Or will I not notice any difference if I flash it?
allard1997 said:
What settings if I don't want to flash FSYNC_ON.zip because it will make the I/O run slower?
Or will I not notice any difference if I flash it?
Click to expand...
Click to collapse
The risk of not flashing fsync_on is that the data partition may become corrupted if there is a SOD or RR. It may not.
When testing different performance settings, it may cause instabilities in the system and cause SOD or RR.
I run with fsync off, but I have a good TWRP backup about every week. Not all tablets will run stable at all settings.
frederuco said:
The risk of not flashing fsync_on is that the data partition may become corrupted if there is a SOD or RR. It may not.
When testing different performance settings, it may cause instabilities in the system and cause SOD or RR.
I run with fsync off, but I have a good TWRP backup about every week. Not all tablets will run stable at all settings.
Click to expand...
Click to collapse
Okay but if I flash it will I notice it in performance?
And what is SOD and RR exactly? (I'm a noob)
allard1997 said:
Okay but if I flash it will I notice it in performance?
And what is SOD and RR exactly? (I'm a noob)
Click to expand...
Click to collapse
Some users say that there are times when they notice it slow down, but it is rare and worth the security on their data partition.
SOD = Sleep Of Death (wont wake up unless you hold POWER for about 12 seconds)
RR = Random Reboot (Just randomly reboots, sometimes when sleeping or maybe when it is in use)
frederuco said:
I have mine set to:
Interactive
312 MHz
1504 MHz
SIO
ZRAM OFF
.
Click to expand...
Click to collapse
I flashed this ROM a week ago, but in settings>performance> there isn't ZRAM option. Why?
wylyka said:
I flashed this ROM a week ago, but in settings>performance> there isn't ZRAM option. Why?
Click to expand...
Click to collapse
Did you wipe system and data before flashing?
Which build are you running?
frederuco said:
Did you wipe system and data before flashing?
Which build are you running?
Click to expand...
Click to collapse
Hi frederuco, I wiped everything and format/system then i flashed Katkiss 4.3 on my TF101g (then another wipe cache) and there was no ZRAM option, so I flashed the modded rom by Shev_t but the same.
There are about 25 builds of KatKiss 4.3, the latest is build 027.
frederuco said:
There are about 25 builds of KatKiss 4.3, the latest is build 027.
Click to expand...
Click to collapse
Sorry, build 027.
I'm not sure why it isn't there. I would head to the Dev thread and ask there
frederuco said:
I'm not sure why it isn't there. I would head to the Dev thread and ask there
Click to expand...
Click to collapse
How I check if it's enable? And is there a way to manage it by file explore?
Works Great
frederuco said:
I have mine set to:
Interactive
312 MHz
1504 MHz
SIO
ZRAM OFF
Putting your min to 216 may cause SOD and RR. It will still go down to deep sleep if idle. It is stable at 1600 on and 1640 for mine (have not tried 1704) but it gets quite warm.
I used to use SmartassV2 on 4.2, but on this kernel it sticks at max CPU and never slows down.
I tried ZRAM ON and did not notice any difference so I turned it off.
Try the OC values and see what works for yours. Some tablets are more stable than others at different clock values so try some and see what happens. I would recommend flashing the FSYNC_ON.zip from the thread just incase you bet a RR or SOD that you do not risk corrupting the /data/ partition.
Click to expand...
Click to collapse
Settings work great. Thanks
frederuco said:
Some users say that there are times when they notice it slow down, but it is rare and worth the security on their data partition.
Click to expand...
Click to collapse
Do you have to flash the fsync_on.zip every time you update the rom and gapps?
Thanks in advance
Hey guys,
ive tried different roms (stock cm11s, mahdi, droidkang) with different kernels (stock, franco, ak).
I have completely wiped my device and set up everything new.
Still im getting reboots every now and then.
Mostly it happens to me while im surfing with chrome, but it also happened in the gallery, while watching movies and so on. Never had a problem while gaming.
Last_ksmg always says "kernel panic", followed by "failed to stop secondary cpus".
Please see the linked last_ksmg files.
https://dl.dropboxusercontent.com/u/16054199/last_kmsg6
https://dl.dropboxusercontent.com/u/16054199/last_kmsg7
Any help is highly appriciated, im getting really frustrated...
Are you using any kernel apps? What other apps are you using? Are you running Xposed?
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
Try reflashing everything through fastboot. Each individual partition, just to make sure everything is clear and wiped.
soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
I was having reboot issues will using both DPI changer and textdroider from the playstore. I would suggest getting rid of textdroider DPI and instead manually change it. Go into your file manger then system/build prop and look for LCD.density. It fixed my rebooting issues running Jedi Open Source rom.
Sent from my Oneplus one using XDA Free mobile app
Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?
soulcrash said:
Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?
Click to expand...
Click to collapse
Reboots are usually on the software level, but 38R actually had reboot problems. Best if you installed a custom kernel and tweaked it yourself, say AK.
Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...
soulcrash said:
Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...
Click to expand...
Click to collapse
Yes, but I and a couple of friends get those reboots too. It's a common problem, not easily diagnosed. If your last_kmsg gets written to, it's saying that a configuration has crashed and the software itself is requesting a forced reboot.
If the last_kmsg has nothing inside then it's obviously a hardware issue.
Sent from my OnePlus One using Tapatalk VIP
Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?
soulcrash said:
Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?
Click to expand...
Click to collapse
After you install ak, install UKM (flashable zip in recovery) and then install Synapse from the Play Store. Then go into Synapse and swipe the drawers to see these options.
CPU:
Set a safe non overclocking frequency
Governor: slim
Hotplug: CPU Boost by CyanogenMod
GPU Governor: msm-adreno-tz
Memory: Drop Caches Enabled
USB Fast Charge Disabled
Log Creation disabled.
Thanks for your help man, i still get reboots, im back at my nexus5 and wait if someone from the opo support answers me ... Frustrating.
have you the problem on all ROms after updating to R38? Some ppl are reporting that after R38 Update even other ROm Versions does the Random Reboot Bug....