Ok I have this one issue when running AOKP and I have back Burton set to kill tasks for no apparent reason tasks well be killed without back button any ideas
Sent from my SCH-I500 using XDA App
It's the phantom button issue. Just another form of it because you gave the phantom more power
Sent from my SCH-I500 using xda premium
Any fix for this been found......I guess it can join my phantom ring
Sent from my SCH-I500 using XDA App
The problem is mainly cause by hardware interference, but it can be bandaged a little bit. If you search the old glitch thread you could read a fair amount about phantom press issue. Glitch 13.1 (for gingerbread) has "fixes" for the issue in place that drastically reduced the amount of phantom presses I experienced. Those weren't added to v14 though, because for others it apparently didn't work or actually exacerbated the issue. I asked tk-glitch about it and I think he said he's at least looking at implementing it into v14 though.
You can also turn off the long-press back to kill feature too, I've kept it off because I had issues with it closing apps by itself when it was enabled.
k_nivesout said:
The problem is mainly cause by hardware interference, but it can be bandaged a little bit. If you search the old glitch thread you could read a fair amount about phantom press issue. Glitch 13.1 (for gingerbread) has "fixes" for the issue in place that drastically reduced the amount of phantom presses I experienced. Those weren't added to v14 though, because for others it apparently didn't work or actually exacerbated the issue. I asked tk-glitch about it and I think he said he's at least looking at implementing it into v14 though.
You can also turn off the long-press back to kill feature too, I've kept it off because I had issues with it closing apps by itself when it was enabled.
Click to expand...
Click to collapse
Hey I tried to search that thread just now and I couldn't find anything on it. what would you suggest I search for to find the posts?
tacofox said:
Hey I tried to search that thread just now and I couldn't find anything on it. what would you suggest I search for to find the posts?
Click to expand...
Click to collapse
go to the dev section and look up the glitch v13 thread...read thru the last 20-30pages.
There's no real "fix". I've coded a band-aid to make it happen far less often. Here's the thread: https://github.com/Efpophis/Glitch/issues/9
I'm running kgb kernel with the "fix". I think Bill was going to code it into glitch...
update 16 Mar 2012:
there is a real fix but it involves taking your phone apart and modifying it. See this thread:
http://forum.xda-developers.com/showthread.php?t=1328670
electric bill said:
There's no real "fix". I've coded a band-aid to make it happen far less often. Here's the thread: https://github.com/Efpophis/Glitch/issues/9
I'm running kgb kernel with the "fix". I think Bill was going to code it into glitch...
Click to expand...
Click to collapse
thanks for taking your phone apart. That "bandaid" has made a world of difference.
Sent from my SCH-I500 using xda premium
Related
OK, I have written an app to attempt and stop call wonkyness on CM7 builds. Specifically the phone locking up when making and receiving calls.
It's my observation that it's the mic that causes the phone to lock up and so this app opens and closes the mic every minute to keep it "fresh". It's a long shot, but I can't seem to duplicate wonkyness with it enabled so I'm posting it for other to try.
Now after a few positive comments to help boost my confidence in the app, I've made it's own thread to make it easy to track comments.
Just install and run (or just reboot as it auto-start on boot). To disable, uninstall it.
Please post your results!
Change Log:
Version 1.4
Made service more persistent by adding notification bar. Turns out, Android was killing off the service when memory was running low causing wonk to surface.
Version 1.3
Can only be installed on internal memory. Needed to make sure the service can started up on boot. (Thanks to mjukis for pointing this out)
Version 1.2
Only dewonkificates when screen is off to avoid conflicts with any apps you may be using.
Removed debug logging
[Post edited because the wonkyness is still there and this .apk works fine to fix it]
Dude.... As best as I can tell in 20 minutes' time, this damn thing seems to actually work! Gotta tell ya how skeptical I was....but I'm pretty flippin' pleased right now!
Good looking out!!
Much appreciated for this app.
While it's still too early to say it's 100% working, so far so good.
I have had the wonk since build 3 to 23 (except for 16).
I will keep testing and report back often.
That's great news and I'm happy that it looks like it's working for people. I was on the edge of rolling back and this was a desperate attempt to fix it.
Agree with the op. Can't say for sure its the miracle I've been waiting for... but 4 calls in (admittedly 2 from myself, ) no wonks. When I'd expect all to be wonky
If this 'wonklessisity' continues you will surely become supreme ruler of xda!
Will report back soon.
Sent from my Nexus One using XDA App
TheMasterBaron said:
That's great news and I'm happy that it looks like it's working for people. I was on the edge of rolling back and this was a desperate attempt to fix it.
Click to expand...
Click to collapse
What are your thoughts and battery impact?....and would some timeframe greater or less than 1 min. factor in??
Does this fix it?
http://review.cyanogenmod.com/#change,2642
shaggy-h said:
Does this fix it?
http://review.cyanogenmod.com/#change,2642
Click to expand...
Click to collapse
No, that's a different problem.
Sent from my Nexus One using Tapatalk
makelegs said:
What are your thoughts and battery impact?....and would some timeframe greater or less than 1 min. factor in??
Click to expand...
Click to collapse
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
I also believe it have something to do with the mic, since all apps that use it have the same freeze, and it seems to work for me. Thanks
TheMasterBaron said:
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
Click to expand...
Click to collapse
Seems reasonable enough, to me.
TheMasterBaron said:
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
Click to expand...
Click to collapse
Maybe watchdog would be a better app for checking. Would give us a better idea of CPU use. Also juice plotter may help see prior and after install battery consumption
I've tested it,and havent got any wongkiness for today. I think its working...
Sent from my Nexus One using XDA App
Got source?
fitsnugly said:
Got source?
Click to expand...
Click to collapse
Added to the OP
TheMasterBaron said:
Added to the OP
Click to expand...
Click to collapse
gracias!
You deserve an E-Cookie for coming up with such an awesome name
Wonky just visited me when my wife called. Installed your dewonky app for testing.
Thanks.
This bug is the reason I got off CM7 nightlies, so damn annoying. Maybe this is a Gingerbread thing rather than a Nexus S problem cause the Nexus S is supposed to be rebooting itself while in calls as I'm sure everyone knows.
Since we have Q&A stickies in the Inspire and Captivate forums (as well as a few other fora around here), I thought we need a general CM7 Q&A here for the Atrix.
BEFORE ASKING QUESTIONS IN THE FORUMS, ASK YOURSELF:
Has this question probably come up so often that there is an FAQ that includes it?
OFFICIAL CM7 FAQ FROM THE ATRIX-DEV TEAM​
Phalanx7621 said:
I know how much people LOVE to post questions in here as if it's the CM7 ROM and get all pissy about how things dont' work, but keep in mind that if that were true and a bunch of stuff didn't work it would NOT have been made part of the nightly CM7 releases. Also, it wouldn't have been released if that were the case. The devs work very hard to make sure most major problems are taken care of before every release, but if yer flashing A NIGHTLY, keep in mind it comes with NO promises of functionality and it is STATED in the OP that it shouldn't be used as a daily driver. So if you have a stable version, such as the lastest stable version found on the development page OP, then post a question or comment here after searching for the answer with search feature here and google. Otherwise, there's a Nightly post section as well in the Development side if you wanna look there and that's what yer using. Most of the time if there is a major issue and you can't find it on the bug tracker than it's yer phone, or something you have installed that is messing with the functionality of the ROM. Lastly remember folks, it's the developers job to make their product work with the ROM, not the other way around. Have fun, happy flashing!
Click to expand...
Click to collapse
You know what ? Its a damned good idea. Too many people are cluttering the development thread. Now since no one else has posted a question related to CM7, I have one:
Can someone help me figure out what is eating my battery on standby ?? I don't have that power hungry facebook app and I did some tweaks found ( via SetCPU ) that I found in the development thread, but it made very little difference. The thing is, I just have no idea how to monitor what is using all the power. How did they figure out that facebook was causing a big drain ?
Do you use google latitude?
A very good thing is use BetterBatteryStats to really understand where the CPU is being keept awake. The embed battery stats for example only showed me Android OS as a culprit, but gave me no further details..
my 2 cents
i have heard CPU Spy is great for figuring out whats using up your resources. dont know as i tend to get pretty good battery life (16+ hours with exchange push enabled)
Thanks for the tips. Yes, I do/have used latitude. I'll put an end to that and give those apps a try. Will report back!
Any idea tips & tricks for CyanogenMod Setting?
raunamaxtor said:
Any idea tips & tricks for CyanogenMod Setting?
Click to expand...
Click to collapse
this isnt all inclusive, but it might give you a start
http://wiki.cyanogenmod.com/wiki/CyanogenMod_Settings
Had anyone else had trouble getting the hbogo app to work on CM7? I can login and try to play a video but get audio with no video. The hbogo splash screen plays perfectly when playing a video for the first time.
Edit: Just found a bug report for this exact issue. (issue 163, sorry, I can't post links.)
Sent from my MB860 using XDA App
When I receive a call, my phone goes to a lock screen, I have to swipe the lock screen to answer. On stock, when I got a call, the screen woke up in the dialer app and all I had to do was press the answer button. For the life of me I can't seem to find a setting to change this, any input appreciated.
mobileweasel said:
You know what ? Its a damned good idea. Too many people are cluttering the development thread. Now since no one else has posted a question related to CM7, I have one:
Can someone help me figure out what is eating my battery on standby ?? I don't have that power hungry facebook app and I did some tweaks found ( via SetCPU ) that I found in the development thread, but it made very little difference. The thing is, I just have no idea how to monitor what is using all the power. How did they figure out that facebook was causing a big drain ?
Click to expand...
Click to collapse
Do you by chance have Tango installed? I had it for all of 2 days and noticed my battery died about twice as fast as it normally would. I usually get a good 16+ hours easy with moderate use but was only getting about 9 with the same usage. Did a quick google search and verified tango was the culprit. Uninstalled and back to normal. I don't know if this applies to any other video call apps but might be worth looking into.
emmc
Think I already read something about it, but cannot find right now... What's the deal with /mnt/emmc and /sdcard in cm7 ? Is it possible to get it back like the stock rom ?
I am having problems using Titanium and taking screenshots, think it is something related...
Thanks in advance!
Wifi connectivity drives me nuts on cm7. Had to turn it off and on in order to connect. Someone mentioned to edit propbuild. Idk what that means.
Sent from my MB860 using XDA App
eklam said:
Think I already read something about it, but cannot find right now... What's the deal with /mnt/emmc and /sdcard in cm7 ? Is it possible to get it back like the stock rom ?
I am having problems using Titanium and taking screenshots, think it is something related...
Thanks in advance!
Click to expand...
Click to collapse
You need to go into Setting/CyanogenMod settings/Application, check "Use internal storage" then reboot your phone and it should be back to how it was before.
Betterbatterystats seems to have found some interesting things. Phone on for 1hr and ten minutes.
Under partial wakelocks:
Lightflow: 1hr10m3s
AlarmManager: 58m13s
JuiceDefender:55m44s
There is more ( I can provide screenshot if required ), but those are the top three.
I do find this a little odd. Juice defender was just installed the other day and I can't see how it would cause any problems. Battery was a bit crappy before and didn't get any better/worse. I froze lightflow the other day and battery drain was about the same.
filthyfnj24: Nope no Tango.
I can provide a list of apps if would help as well.
I got watchdog and Im able to detect what cause battery drain while on standby. Its the "suspend" service running on the background with 90% cpu usage ... as soon as I heard the warning from watchdog, I wake my phone and that "suspend" stop immidately. Happen to me since I got this rom cm7. It didn't happen before on alien...
Sent from my MB860 using XDA App
I as well am having problems with Suspend and abnormally high sensor usage.
I got watchdog and Im able to detect what cause battery drain while on standby. Its the "suspend" service running on the background with 90% cpu usage ... as soon as I heard the warning from watchdog, I wake my phone and that "suspend" stop immidately. Happen to me since I got this rom cm7. It didn't happen before on alien...
Click to expand...
Click to collapse
EDIT: upon further investigation I have narrowed down AlarmManager as causing a lot of partial wake locks, but I dont have any alarms set and have not synced my calendar and have the Calendar alerts turned off. However Suspend is showing as a problem as well.
I'm using BetterBatteryStats, SpareParts, and the stock battery manager to try and track this down.
Well, after eliminating Lightflow and turning off Beautiful Widgets small weather, things are improving. Instead of losing 5% per hour on standby, it is now down to about 3%. Juice defender and Alarm manager are still at the top of the list, In 2hrs and 18min I have:
Alarm manager 33m12s
Juice defender 27m56s
So, Juice Defender is next on the list. The funny part is I know that CM7 is causing this. Battery used to last near forever on standby.
Great idea... Stickied. You may also want to check out the atrix-dev-team FAQ and consider suggesting Q/A posts from this thread or links to other posts in other threads, for updates to that FAQ.
Ever since I upgraded from pre-beta 4 to Beta, my phone has had two horizontal deadzone lines on the touchscreen. This persists from ROM to ROM, and is getting to be annoying. I have no warranty, as I bought the phone from a guy who won it in a contest, unlocked it and brought it to another carrier.
Is there any chance that this is a software issue, and can be repaired?
I got it !!!!
Alarm Manager is no longer a problem. Phone now sleeping correctly. I disabled background date, topped off the battery and verified via Betterbatterystats. Now if we could disable background data while it sleeps and re-enable it when you wake it up then we'd be set.
I'm aware that turning of screen/touch sounds will help remedy the problem of AudioOut_1 being a battery-sucking vampire, but are there any actual fixes yet (turning off the sounds seems like more of a workaround than a fix, I think)?
Most posts I've found regarding AudioOut_1 are not very recent, so I'm not sure if that means the problem is solved or if everyone has simply turned off touch sounds and screen lock sounds. In my experience, the issue persists (at least in the most recent versions of AOKP/CM9 that I've used, which are I think one version behind the latest). It may be stupid, but I enjoy the CM9/AOKP touch sounds and would like to hear them without my battery suffering quite so much in the process.
For what it's worth, searching "audioout" on either the CM9 thread or the AOKP thread turn up zero results. Surely I'm not the only one still getting this wakelock, am I?
Also, regarding this wakelock: is it kernel-related? I'm really quite unfamiliar with how this sort of thing works, but I'd like to know a little more if only to satisfy my curiosity.
Turn off lockscreen sounds. Should help
Sent from my SGH-I777 using xda premium
jthatch12 said:
Turn off lockscreen sounds. Should help
Click to expand...
Click to collapse
I don't have any sounds enabled and I still have a problem with this wakelock.
Sent from my SGH-I777 using xda premium
I am also struggling with this wakelock and seeking additional help (using BBS too). I'm running AOKP build 37 on the Epic 4g Touch (also SGS2). I hope we find something out.
I don't really have any battery drain from this but still looking for an answer! Taskkkkkkk where are youuuuuuu???????????????
Download latest version. Do a full wipe. (Full wipes are not just cache. Its everything) and see if issue persists. If a full wipe isn't done before posting about an issue it shouldn't be posted.
Sent from my SGH-I777 using Tapatalk 2
I haven't had this wakelock for a while now, with my sounds on. I fully wipe each time I update, and that includes formatting system along with a factory reset and wiping caches
Sent from my SGH-I777 using XDA
Hi guys, I'm running the latest version of Slim Bean with stock modem XXLE8 and whatever kernel comes with Slim. I've noticed that there is a 1.5-2 second delay upon hitting the power or home button to the screen turning on and being ready to use. It's pretty annoying as you can imagine, I've actually figured out what the problem is, my phone is going to deep sleep too early and is taking up to 2 seconds to wake up, I wouldn't mind this if the phone has been left alone for 2 hours or so, but if I leave my phone for 5 minutes I shouldn't have to wait 2 seconds to unlock it. I came to this conclusion by using the app softlocker from the market, which disables sleep, and the lockscreen is perfectly fine with no lag, so should I try a new modem or a new kernel or is there something else I have to try to solve this issue?
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
DeadVirus said:
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
Click to expand...
Click to collapse
I've read both but neither seem to provide much of a solution. It is pretty ridiculous a phone like the S3 with such powerful hardware suffers from unlock lag. My HTC Desire Z used to unlock instantly... Kinda disappointing.
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
theslashy said:
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
Click to expand...
Click to collapse
I've been looking but can't seem to find one. The delay is about 1.5-2 seconds on Siyah, was about the same with YANK kernel.
jj92942000 said:
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmmmmm I might flash a stock rom and check it out because I don't remember it happening when I was running stock, tho that was for a grand total of 3 days lol.
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
0semaj0 said:
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
Click to expand...
Click to collapse
sure, but i own quite a view other android phones and none behaves like the s3, not even the superlow-budget htc one v
i installed the omega 4.2 AOKP rom today, but the lag is there, too....i got back to arhd for now...
theres a app called softlocker, but with that the cpu never gets to deepsleep, my s3 gets warm and the battery drains badly
I'm stock locked and latest ota. Just don't really get it is this normal?
Sent from my HTC6435LVW using xda premium
Guess this is normal
Sent from my HTC6435LVW using xda premium
ickedmel said:
Guess this is normal
Click to expand...
Click to collapse
Unfortunately, it probably is. At the top of the app usage screen, there's a drop from which you can view the kernel wakelocks. I would expect a large hsic wakelock time.
Is so, that's only fixable by a custom kernel.
crpalmer said:
Unfortunately, it probably is. At the top of the app usage screen, there's a drop from which you can view the kernel wakelocks. I would expect a large hsic wakelock time.
Is so, that's only fixable by a custom kernel.
Click to expand...
Click to collapse
I'm having the exact same issue. And it just started in the last few days. Before then I was able to easily get through a day or more and now I'm having to plug in during the day. I don't know what started it. I have tried tinkering with the settings and uninstalling any apps I downloaded in the last few days. The only other thing I did was that for the first time I configured and setup wireless tether but I haven't used it at all in several days.
You are correct that it shows, in my case, a large hsic wakelock time. So I'll be finally moving to a custom rom and kernel.
But I'm curious, what could cause that to start so suddenly?
n8mack33 said:
I'm having the exact same issue. And it just started in the last few days. Before then I was able to easily get through a day or more and now I'm having to plug in during the day. I don't know what started it. I have tried tinkering with the settings and uninstalling any apps I downloaded in the last few days. The only other thing I did was that for the first time I configured and setup wireless tether but I haven't used it at all in several days.
You are correct that it shows, in my case, a large hsic wakelock time. So I'll be finally moving to a custom rom and kernel.
But I'm curious, what could cause that to start so suddenly?
Click to expand...
Click to collapse
It basically involves the kernel having trouble shutting down the communication with the radio. I think you can get temporary relief by rebooting.
FYI, you can always try a new kernel without going to a custom Rom.
Thank you! I'm trying out your kernel now. So far so good. This is why I love xda.
crpalmer said:
Unfortunately, it probably is. At the top of the app usage screen, there's a drop from which you can view the kernel wakelocks. I would expect a large hsic wakelock time.
Is so, that's only fixable by a custom kernel.
Click to expand...
Click to collapse
Thank you guys for the responses and crpalmer you're right huge.. since I'm stuck on OTA nothing I can do nut maybe restart for maybe a temporary fix.
Sent from my HTC6435LVW using xda premium
As a PS, a large hsic wakelock would be one much larger than your screen on time. If you are actually using mobile data, a big wakelock is likely normal.
HSIC wakelock is bad. There should've already been fixes in the kernel to deal with unnecessary HSIC wakelock.
Barring that, the fix requires root. Basically you have to run a Wireshark capture while idling with the screen off, open the dumpfile on a PC, and look for the largest source of traffic. Once you know what's causing it, you have to change the settings or delete the application.
I had this same issue and it seems to have gone away after uninstalling some Facebook updates. I went back to 1.9.something, an apk I found kicking around XDA somewhere. YMMV.