I've searched high and low for this issue, and I've found hits, but nothing that seems to help me or fully answer my questions.
I flashed CM10 nightlies straight away when I got my new Galaxy Tab 2 10.1 last week. Whilst it's a great ROM like with all official CM's, the tab sporadically doesn't wake up after a sleep.
Now the known issues from http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-P5100:Nightly:Known_issues says:
Code:
The screen many a times does not respond to touches for unlocking, needed to reboot the tablet.
Which seems to be what I'm experiencing. All I would like to know if I'm the only one experiencing this issue and if not, do people know if the issue is being actively worked on and is there a workaround in the mean time?
Thanks in advance.
Are you overclocking?
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Are you overclocking?
Click to expand...
Click to collapse
Thanks for the response. I'm not overclocking running at the default 300MHz to 1008MHz from the stock CM kernel settings on the interactive govenor.
I did however install the kernel from the AOKP thread. Ran that over the weekend and never saw the screen wake problem again. As soon as I installed the latest CM nightly the screen wouldn't wake from sleep again so I re-installed the AOKP kernel and everything was working again.
(I also noticed that the AOKP kernel came with CPU settings of 300MHz to 1200MHz on the interactive govenor - I put that back to 300MHz to 1008MHz for safety but didn't see the screen wake problem during my testing with the higher clock speeds).
Has anyone got any info on this screen wake issue?
The amount of times I was having to reset the tablet when I was using the stock CM kernel meant it wasn't usable as a daily device until I installed the AOKP kernel. How can I get in touch with the CM guys to see if I can help with this screen wake issue?
You'll need to find a proxy to post for you in the dev forums in Codeworkxx's thread. You'll need a logcat of the issue.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
You'll need to find a proxy to post for you in the dev forums in Codeworkxx's thread.
Click to expand...
Click to collapse
Or you could just go to their irc channel #teamhacksung-support @freenode
ok thanks, will try to get a logcat and post is in the DEV forum
Related
I know this isn't where i should post this but my Post Count is to low to post in the development forum. I installed RC 0.4 of CM 7 with a full wipe from .3 and up until last night everything was working fine (except the 4g/3g hand-off). Last night out of the blue it started random rebooting/boot looping. I plugged it in and went to bed. When i woke up it was on and some of my launcher settings were reset but other than that it was ok. Then today I have been experiencing more random reboots. Anyone else with this issue?
Can't post in the dev area yet either
I've had CM7 RC4 on for 3 days now and I haven't experienced any reboots yet but I'm not in a 4G area. Did you mess with the overclocking settings? Try to drop it down to 1GHz and see if that helps. Are you on the stock radio? I have mine on stock radio and it seems to work well.
I didn't overclock it any. I did use setcpu to check to make sure that that it was limiting itself to 1Gh thought, but i didn't touch anything else. My radio is the stock MR1 radio 1.16.00.0402w_1. I switched kernels to KangBang's most recent version for now, the random reboots became to much to handle.
You need go back older radio 223r, I have no problem with CM7 RC0.4 and none reboots. The CM7 author stated says use 223r radio.
slayher said:
I highly recommend The stock radio images. All the testing up to this point is based on 1.16.00.0223r Baseband
Click to expand...
Click to collapse
JBass said:
I didn't overclock it any. I did use setcpu to check to make sure that that it was limiting itself to 1Gh thought, but i didn't touch anything else. My radio is the stock MR1 radio 1.16.00.0402w_1. I switched kernels to KangBang's most recent version for now, the random reboots became to much to handle.
Click to expand...
Click to collapse
I read in the forum that you need to be 402w or before.
here: http://forum.xda-developers.com/showpost.php?p=14692504&postcount=5024
Keep in mind that the stock setting for the new release is 1.8GHz in the performance settings. I heard this stock setting was causing some problems for some.
JBass, you gave me link is not CM7 author.
You need read again - http://forum.xda-developers.com/showpost.php?p=13179476&postcount=1
I know that it wasn't from the dev but I guess I'm naive for believing the internet
Now its supported,
cant post link but on rootzwiki the post has been updated.
I am on AOKP B31 without fast charge enabled but seem to have a problem with the phone charging when off. If I plug it into a USB or wall charger, both samsung, the initial battery screen will come on but after the screen turns off it will not turn back on. I left it there for 30 min turned it on and it showed 50% more battery. We all know with a samsung that is not possible. Just want to see if others are having this issue, or a fix.
Thanks in advance.
I am sporadically having this issue as well- Samsung charger, AOKP b31. I will play with it over the weekend and see if I can figure anything out. For the moment I am not seeing this behavior, but initially after flashing I did...
I have not had this issue on any other THS or AOKP build and I have used a lot of them. The last one I was on was milestone 4 and it was fine.
Sent from my AOKP ICS captivate using XDA
Hmm, still doing it. Setting the Min CPU to 200MHz has not helped, as I have seen posted elsewhere. Charging screen turned off at some point, and when I booted up it was at 64% (from 7%). I'm not super worried about it though, seeing as how I flash like crazy and will not be on Build 31 for any length of time. If I get this on other builds or other Roms I will update again.
Edit: Build 32 is out, so I am going to flash and see if that resolves the issue. I am wondering is this is a kernel issue, as the Glitch for Build 31 was the first time I had switched from Glitch version 14 beta 6. Maybe I'll try the Semaphore kernel if the issue remains.
I flashed 32 and it still is the same issue. Also tried the min CPU increase but nothing. Hopefully it will be fixed soon. My concern is that it will continue to charge after 100%.
Sent from my SGH-I897 using XDA
read the first post of AOKP. report bugs where it tells you to. they will not look here, or will they care if they do look here, if you do not follow their instructions for reporting bugs.
look to see if the bug exists, and if it is there, click the STAR to vote for the issue as that page says to do.
I have read the OP but I did not want to flood the bug tracker if it was a problem already found or known. I did not have the 10 posts needed to post in the development section, so I figured start this to see if anyone had an issue. I know how much everyone hates the development thread being diluted with dumb question after question. I did report it on the bug reporter site.
P.S. - Thanks for your essentials mod, makes everything much easier.
Just wonder - will disable fast charge help?
I have not enabled fast charge. I thought that only effects charging when on USB? I could be wrong though.
Sent from my SGH-I897 using XDA
I have been testing with both i897 and i9000 bootloaders. This may be a Glitch kernel issue, as I have flashed Semaphore ICS kernel 1.0.0 and have not seen this. Looks like there is already a bug reported in the AOKP page. Not a huge concern though, I think, because the phone seems to charge nevertheless.
Hi everyone,
I'm new to Samsungs tablets, I have HTC HD2 so i have a little knowledge about firmwares, kernels, roms, flashing and etc. and now i have problem with galaxy tab 2 p5100.
The facts that i know correct me if i am wrong:
1-custom kernels for overclocking doesn't work on stock firmware (ICS,JB)
2-you need to have either AOKP 4.1.1 or CM(CyanogenMod) 9,10,10.1 for overclocking
after flashing CM 10 on my TAB, i tried to flash AOKP_p51xx_1-52GHz_v2-2.zip using CWR but phone stuck on "Samsung Galaxy Tab 2 10.1" logo then i flashed CMOC10-Kernel the same way and it worked so the questions are:
1-why AOKP kernel didnt work i saw posts indicating that it is working, is there anyhing that i have to do before or after flashing this kernel?
2-i have succeeded to flash CMOC10-Kernel, i went to the settings - performance and i change my max frequency to 1380 and set it on boot, so is it enough? or i have to use special program to overclock GPU?
3-what governor is the best for this tablet?
and final question, it is about auto brightness setting, it seems CM 10 can't detect room's light level correctly is there anyway to solve this or change sensitivity of light sensor?
1. The aokp kernel did work, because if it didn't your phone would have never booted!
2. That's enough, but a word of advice, over clocking reduces batter life and increases heat.
3. The governor you want to use totally depends on you and your usage!
4. Try a different auto brightness app like lux auto brightness
prince147 said:
1. The aokp kernel did work, because if it didn't your phone would have never booted!
2. That's enough, but a word of advice, over clocking reduces batter life and increases heat.
3. The governor you want to use totally depends on you and your usage!
4. Try a different auto brightness app like lux auto brightness
Click to expand...
Click to collapse
1. Phone(tablet) didn't boot after flashing aokp kernel! it stuck on Samsung logo (not cyanogenmod logo) as i mentioned in my post the kernel that worked is CMOC10-Kernel produced by johnsel ... wonder why aokp kernel didnt work!
2. i know the consequences of overclocking, reducing battery life(sometimes hardware life) more heat it is predictable, i was just asking is there any program apart from default cyanogenmod settings to see GPU clock also because all programs that i tried they just show me cpu clock not gpu! of course it is not so important ... just interesting!
3.i am using smartass v2 on my htc hd2 it is recommended governor for my htc, but i don't see that option in cm10 is there any place (some website) that i can get information about governors?
4.thanks for your suggestion i will try that :good:
Finally thank you so much for helping me, i appreciate that :good::good::good:
1.I'm not so sure about your problem, report it to the dev for it to be solved
2.this post contains info about how to on gpu over clocking http://forum.xda-developers.com/showthread.php?p=31683246
3.these two articles explain clearly about governors http://www.xda-developers.com/android/your-guide-to-governors/
http://androidforums.com/xperia-mini-all-things-root/513426-android-cpu-governors-explained.html
Sent from my GT-P3100 using Tapatalk 2
I tried to post this in the CM10.1 thread but apparently I need 10 post elsewhere first.
There seems to be a problem with setting the Maximum CPU Frequency option in cm-10.1-20130210-NIGHTLY-skyrocket. It will reset to default, or probably never sets, as soon as you leave the screen. The minimum frequency seems to work fine.
Unsure if the developers are aware of this but it would be cool if it could get looked at in the next release. I never game on my phone so I really have minimal reason to keep it above 1GHz.
Thanks.
Well it IS just about a week old..... Try using a different 4.2 kernel. I think there are 2 of them out there somewhere.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
this is a nightly non stable build. there is a bug report option somewhere on the cm site, i just forget where exactly. check the bug reports, and if its not there help the team by reporting it.
I have this same issue with with CM 10 Stable, the latest CM 10 nightlies, and CM 10.1 nightly. I am thinking its an issue that all of them have.
installed newest
(date 27.1.2014 with GAPPS modular mini from: http://forum.xda-developers.com/showthread.php?t=2530073)
did full wipe (factory reset, system, cache) as in info
have some major problems with stability, looks like system degrades quickly after leaving screen off mode
After restart I can set up everything fine, can use network, launch apps, change system settings etc
but after first turning off and turning on lock screen starts to show first problems, dots (I'm using pattern unlock) sometimes start to activate on their own, not always but sometimes this happens, but I'm still able to logon...
after second 'screen off' and 'screen on' I'm having big problems trying to unlock screen - sometime dot's don't react to touches, sometimes they do not end connecting after taking away finger from screen...
after third off/on I'm unable to pass unlock screen - it becomes unresponsive, dots start to connect randomly, sometime even 'emergency calls' gets activated...
what can cause this? full phone restart appears to fix problems for short time, but after few off/on have problems agains...
this did not happen in builds from few months ago
tried to set higher min cpu frequency to 384MHz but that doesn't help
other things that I chaged are:
- cpu governor -> badass
- i/o -> noop
- active 'allow purging of assets'
anyone got ideas what could cause this? and how to fix
phone:
htc sensation xe, unlocked
hboot 1.29, radio 11.24a.3504.31_m
can provide other info if needed
It's easy to be fixed, install stock rom.
nlooooo said:
It's easy to be fixed, install stock rom.
Click to expand...
Click to collapse
thank you, very helpful
What firmware are you on? Did you experience any of these problems on any other rom?
You say the dots connect themselves. As if the touchscreen is used? Sounds somehow like a broken digitizer.
zodi79 said:
thank you, very helpful
Click to expand...
Click to collapse
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
nlooooo said:
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
Click to expand...
Click to collapse
I must have missed all of these threads. There were some threads about cm11 but they had other issues.
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Sent from my Nexus 5 using xda app-developers app
Sultanxda said:
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Click to expand...
Click to collapse
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
zodi79 said:
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
Click to expand...
Click to collapse
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
first of all - sorry for misinformation but I found cause of my problems with interface... looks like minimal amount of water must have got under the cover when I few days ago applied new screen protection, yesterday I got this idea of what could cause this sudden problems... few hours phone stayed on the room heater (not too hot ofc) and touch screen problems are gone! yeah, tbh I love this phone and was very angry thinking I'd have to replace it, now I don't have to
back to rom - atm back to your (sultan) rom based on CM 11 with update from 29.1.2014, it has some small problems but I like to test new features
problems I've found so far:
- less responsive and smooth
- launcher3 doesn't allow to create new home screens on the left, had to create new to the right then make some rearangments before I got things right
- some widget resize problems under launcher3
- other small problems all I can live with
but I like more available memory and better battery life, going to test ART soon
and it is good that messanging is back, hangouts is just... not for me
Why cant i find my phone contacts on SIM ??? Its say no contacts found? When i import some numbers from vCard from SD why cant i move them to SIM???
cm10.2 - cm11
Sultanxda said:
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
Click to expand...
Click to collapse
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
romadd said:
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
Click to expand...
Click to collapse
I tested it for 3 hours and it was working well
Sultanxda said:
I tested it for 3 hours and it was working well
Click to expand...
Click to collapse
I had fresh install, but configured cpu clock speed 1674 mhz (maybe the problem ?)
And i had the same symptom describe by Firehawk989 http://forum.xda-developers.com/showpost.php?p=49938883&postcount=3341
Any way i run already with your CM11 and it seem more stable for me except a little problem
http://forum.xda-developers.com/showpost.php?p=49353701&postcount=1
This is another story