Database Info

[Q] Package installer won't work... can't press button

I just upgraded to cm7 and now sometimes when I try to install an app from an apk file it wont let me hit the install button.
If I am using Amazon appstore it works, the same type of screen comes up and I can install stuff. But when installing from a downloaded apk (like from here) the button just doesn't work... it isn't greyed out or anything but is simply unresponsive.
Sent from my CM7 SCH-i500

Hey I have this same problem, did you ever figure out this issue? Thanks!

Please let me know if anyone knows how to fix this issue, I'm having the same problem

Bump this
Problem persists on my phone as well. Brand new Droid X2 stock ROM rooted with zergrush kit including busybox, superuser, and recently installed: nobloat free, droidwall, SD Booster, blade buddy, spare parts+, and setcpu (which is pretty much useless without a custom ROM that has the kernel to support it)
Edit: make sure unknown sources is checked under app settings =]
Edit again: NOPE still a problem =[
Edit again: FIGURED IT OUT!!!! Simply turn off your screen filter! =D (I don't know why, but that WAS my problem 100%)

Hi all, I'm facing the same problem, but I don't have screen filter installed. What else have you tried?
Here's my main post about this.

I've also heard that Juice Defender can cause this problem. Sadly, like you, I still can't fix it on my phone!
Anyone?

AHA! I found mine! TEAM Battery Bar. It's a spectacular app; if you've not gotten it yet, I highly recommend it. I just turned it off within the app itself, (I checked running apps to give me a clue,) and the installer button worked.
After hearing about several display-related apps causing the problem, I looked for those on my phone. TEAM Battery Bar does indeed run a constant display item, so I think that's the key. I'll notify the dev. He's pretty responsive.

I can confirm: disabling TEAM Battery Bar solve the problem! thanks

Arcangel Loki said:
Problem persists on my phone as well. Brand new Droid X2 stock ROM rooted with zergrush kit including busybox, superuser, and recently installed: nobloat free, droidwall, SD Booster, blade buddy, spare parts+, and setcpu (which is pretty much useless without a custom ROM that has the kernel to support it)
Edit: make sure unknown sources is checked under app settings =]
Edit again: NOPE still a problem =[
Edit again: FIGURED IT OUT!!!! Simply turn off your screen filter! =D (I don't know why, but that WAS my problem 100%)
Click to expand...
Click to collapse
Thanks, that fixed my problem on my Galaxy S2 with LPQ ICS rom. Probably should report it to the dev for fixing...

in my case Juice Defender was a problem, since I don't have any screen filters installed
uninstalling Juice Defender fixed my phone
EDIT Friend of mine has the same phone (SGS2) with the same ROM installed, JD never caused any problems with his phone
The only difference between my JD settings and his - I got brightness control enabled, so maybe that was a problem, not JD itself

Arcangel Loki said:
Problem persists on my phone as well. Brand new Droid X2 stock ROM rooted with zergrush kit including busybox, superuser, and recently installed: nobloat free, droidwall, SD Booster, blade buddy, spare parts+, and setcpu (which is pretty much useless without a custom ROM that has the kernel to support it)
Edit: make sure unknown sources is checked under app settings =]
Edit again: NOPE still a problem =[
Edit again: FIGURED IT OUT!!!! Simply turn off your screen filter! =D (I don't know why, but that WAS my problem 100%)
Click to expand...
Click to collapse
I'm currently on SGS2 rooted stock LPQ and just figured it out myself that Screen Filter is actually doing something so that the install button cant be pressed. Has anyone informed the dev?
Edit: just mailed the dev of Screen Filter hoping for confirmation and fix

'Lux Auto Brightness' is causing the same issue, so seems that all the applications trying to adjust screen brightness will cause the issue.
By the moment I disable it, I am able again to install apks... really weird
Also, not clear why only the install button is effectively disabled, as cancel bitton works and the 'show all perms' drop down , also works

kjdiehl said:
AHA! I found mine! TEAM Battery Bar. It's a spectacular app; if you've not gotten it yet, I highly recommend it. I just turned it off within the app itself, (I checked running apps to give me a clue,) and the installer button worked.
After hearing about several display-related apps causing the problem, I looked for those on my phone. TEAM Battery Bar does indeed run a constant display item, so I think that's the key. I'll notify the dev. He's pretty responsive.
Click to expand...
Click to collapse
Good call! That was the exact app that was causing me problems as well. Here's hoping to a quick fix!

sageDieu said:
I just upgraded to cm7 and now sometimes when I try to install an app from an apk file it wont let me hit the install button.
If I am using Amazon appstore it works, the same type of screen comes up and I can install stuff. But when installing from a downloaded apk (like from here) the button just doesn't work... it isn't greyed out or anything but is simply unresponsive.
Sent from my CM7 SCH-i500
Click to expand...
Click to collapse
"Upgraded"
Sent from my XT912 using xda app-developers app

Thank you
kjdiehl said:
AHA! I found mine! TEAM Battery Bar. It's a spectacular app; if you've not gotten it yet, I highly recommend it. I just turned it off within the app itself, (I checked running apps to give me a clue,) and the installer button worked.
After hearing about several display-related apps causing the problem, I looked for those on my phone. TEAM Battery Bar does indeed run a constant display item, so I think that's the key. I'll notify the dev. He's pretty responsive.[/QUOTE
i encountered the same issue and after reading your post and searching hard on my n7000, i finally found what causes it...on my n7000 it was glove box. After uninstalling my phone is back to normal again
Click to expand...
Click to collapse

Thanks for all the infos, guys. For me, it was both Lux Auto Brightness and Twilight. I disabled them using task manager and everything went smoothly from that. Explains why no matter how much I reboot, it doesn't fix things. I also have avast Mobile Antivirus installed and it has a constant display notification but it doesn't cause any issues. I am guessing it has something to do with code wired to the phone's hardware? As all the apps causing problems had to do with overlapping device setting control over screen brightness or hue.

[ROM][BETA 4.0.3][Evervolv-ICS-2.1.0-01MAR-HeroC]

This is now considered a beta version of Ice Cream Sandwich for the HeroC. Please keep all comments/communication about this ROM in this thread, and keep the Development thread clean for people actively working on the ROM.
No guarantees that anything will work, or that your phone will not be turned into a brick or a toaster. Please backup if you value what is currently on your phone.
You can use this with or without gapps. If you load them both on the initial setup, be sure to select "Setup Wizard" when the system first comes up.
In its current state this ROM with GAPPS needs around 155M in /system. I am currently running firerats at 160/20 just to be safe for testing purposes. I would recommend at least 155 for system.
There are some obvious places where we can reduce the size, but that will come as we continue to refine and move forward. Performance in not great, but overall it is fairly functional. Gapps are just some a minimal version to get Market working.
THIS ROM TAKES A LONG TIME TO BOOT (ESPECIALLY FIRST BOOT).
Boot animation has been added in 26NOV version. Please be patient.
This is a work in progress and there remain many Opportunities for Improvement (the gentle euphemism for Defects).
Working (at least for me):
Touchscreen
Trackball
Phone
Data
WiFi
MMS
Audio
Bluetooth
SD Card
Market
GPS
Gallery
Boot Animation
LatinIME Keyboard
Prediction/Dictionary
Network Stats (Data Usage)
Headsets (Audio Jack & HTC 11 Pin)
Not Working:
Camera
Gallery2
Graphics Acceleration
TBD (Lots of other stuff)
25-NOV-2011 Initial Alpha release
TeamICS-4.0.1-25NOV-HeroC.zip
26-NOV-2011 Update with working GPS. Disabled broken qcom egl so that Google Maps works (slowly). FIXED LINK
TeamICS-4.0.1-26NOV-GPS-HeroC.zip
28-NOV-2011 Updated kernel for better alignment with ICS. Lots of additional updates. Updated to fix wifi issue (wlan.ko replacement)
TeamICS-4.0.1-28NOV-NEWKERN.zip
01-DEC-2011 Updated kernel to support network stats (Data usage). Modified LatinIME to show entire keyboard. Synced with CM/AOSP repos.
TeamICS-4.0.1-01DEC-HeroC.zip
06-DEC-2011 Updated with test fix for random app crashes (phone, exchange, popups, etc.)
TeamICS-4.0.1-01DEC-HeroC.zip
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Fixed trackball. Replaced Gallery2 with older Gallery for the time being. This has major changes to the source base and limited testing, so backup is recommended.
TeamICS-4.0.3-18DEC-HeroC.zip - Currently offline while resolving some issues
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Update from earlier post to add audio driver fixes, and su updates that restore Superuser functionality.
TeamICS-4.0.3-18DEC-HeroC-AUDIOFIX.zip - Currently offline while resolving some issues
20-DEC-2011 Back to 4.0.1 for the time being, until 4.0.3 issues can be resolved. This version has all of the standard fixes including radio/data, trackball, and audio. Also includes Gallery instead of Gallery2.
TeamICS-4.0.1-20DEC-HeroC.zip
22-DEC-2011 Minor update to include fixes for Headset (Audio Jack) and Dictionary/Prediction.
TeamICS-4.0.1-22DEC-HeroC.zip
25-DEC-2011 Add basic Bluetooth functionality. Additional testing in progress. Classification changed to Beta, as all major functionality is working except for Camera and Hardware Acceleration.
TeamICS-4.0.1-25DEC-HeroC.zip
01-MAR-2012 Integrating development with Evervolv team. Brings alignment with ICS 4.0.3 development.
Evervolv-ICS-2.1.0-01MAR-HeroC.zip
GAPPS
You can use the latest ICS Gapps from here. Or other Gapps of your choice.

FAQ / Fixes
DATA ISSUES
If you are having issues with Data try the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
If you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
KEYBOARD ISSUE
Attached below is a replacement keyboard that doesn't have the bottom row off-screen. This is just a quick hack to get a functional keyboard. After some clean up and testing, I will include it in the releases going forward. Just replace the existing /system/app/LatinIME.apk with this one for the time being.

Reserved 2
This is also reserved for later use.

Nice.
Sent from my HERO200 using XDA App

I've got work in an hour........ so here we go, I'll let you know what happens.

whoa man, already? YOU GUYS ARE AWESOME!!
p.s- happy thanksgiving btw!!
edit:btw downloading it right now,, going to give it a go
---------- Post added at 10:45 AM ---------- Previous post was at 10:03 AM ----------
hmmm after the HTC screen, i get a black screen showing nothing. Plugged the charger and shows charging light.. Still waiting for it, it's been like 3 minutes. im on 170 40 mtd settings. K nvm it setup just appeared. For those that are trying, wait for it.
EDIT: K been messing around with it (sorry for all these edit, just trying to prevent a lot of posts and I am awake this late so might as well show some heads up) but problems I found
1) Keyboard is half (missing space bar and the alt function)
2) Screen orientation is choppy
3) Im missing the actual market app, might be firerats issue
I found a pointless feature.. but using the trackball brings up a cursor lol didn't know it'd do that. Making it "click" u have to press the ball then scroll quickly rather than just keep clicking the ball.

Thank you ICS Team. Other than the items listed in the OP, I cannot get data to work. Phone is stuck on No Service and every few minutes will jump to roaming and then back to no service. If I try to call a number with the dial pad, the dial pad disappears after I press send, I assume this is because I have no cell signal. Could not test google apps due to no data. I was still able to play with the home screen, widgets, etc.
@ Majin101, my keyboad seems to be working ok, I do have the market app but haven't tried to use it yet. I am not using firerats mod. If anyone else tries to flash this, make sure you wait a few minutes for the rom to boot as mentioned in the above post. You will see a blank screen but it will eventually boot.

This is going to be a great rom. If you use a different keyboard you also get space and alt to show up.

Findings.
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair

Freeroot said:
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair
Click to expand...
Click to collapse
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.

As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?

jaybob413 said:
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
Click to expand...
Click to collapse
Alright, that did the trick. Really nice work.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
rizdog23 said:
As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?
Click to expand...
Click to collapse
I got the same error. It booted just fine and I thus ignored it. Would be nice to know though.

For those that want to fix the keyboard, just download ics keyboard from market. For those that cannot download from market, use root explorer to go into "cache" and create a folder named "downloads", for those that want to increase scrolling speed etc., flash the TweakZ.zip found in the android general forum here at XDA. I would also recommend setCPU.

I also got Random Offset 0x1ba. Once rebooted, HTC screen showed up then black screen. I waited 10 min but it looked frozen. So I pulled the battery. Then I accidentally formatted my SD card and the fun was over.
Sent from my HERO200 using Tapatalk

The "random offset" comment has to do with the flashing of the kernel. I'm not entirely sure but I think it has to do with the way the boot.img is packed. Should be harmless though..
Good to see you'll got this thing running though.
Sent from my PG86100 using Tapatalk

Another feedback!
pros
1) Ive been texting sending and recieving just fine no problems (havent tried mms)
2) Made calls talked fine (although my face kept hitting the end button..)
3) Installed swype, texting is fine now and changed the dictionary too english to get rid of those red lines under the words
4) Also increased pointer speed to just use the trackball if needed
other bugs:
1) Noticed that some of my notification doesn't make a sound or plays
2) When I play music its coming through the ear piece speaker rather than the back speaker
3) google map fails to login

Darn looks like I have to go back to CM7.1. People try to call me but my won't won't tell me someone is calling and their isn't any sound either. Also the gallery app opens but doesn't show pictures and apps are missing from the market but thats probably a build.prop issue.
-------
Just flashed without mtd and it seems to be working better. I'm receiving calls and can hear my sound now.

Great job guys! Running for about an hour and besides the above mentioned bugs, I've noticed one more.
When I put the phone on the charger it becomes unresponsive and the screen goes dark. No way to wake the phone nor is the charging led on.
The only way I can charge the phone is to do a battery pull and boot the phone while on the charger.

mines charging and im still able to use it?

Very Impressive, to say the least!
*note for the development team - you are the F-ing man!!!!

garyd9's custom kernel feedback

I wanted to post this in the development section as feedback for garyd9's revised kernel for the P6210, but since I am new with fewer than 10 posts, I cannot do so. I PM'd Gary, he suggested I post it here. So here it is:
I have a P6210 and installed your custom kernel_20120101 and it worked beautifully. The tab was very stable, and battery life is better, as you indicated. I then installed kernel_20120105, and the tab immediately started having sleep of death problems. I would shut off the screen, set it down, and next time I came back to it, I had to do a hard reset by holding the power button ~20 seconds and reboot it. This happened consistently. I then tried kernel_20120107, and had charging issues. The tab got very warm while charging from the AC adapter. Uncomfortably warm. I have no idea if this was related to the kernel update, or just a one-time fluke. I am just relaying my experience. Anyway, the heat freaked me out, so I immediately downgraded back to kernel_20120101, and my tab is completely stable again.
Thanks for the work you do on this.... They are cool devices, and it's nice to be able to play with them.
Thanks.
Click to expand...
Click to collapse
I want to add that I am not running setcpu...
I'm willing to try the newer kernel updates again, or provide any other info Gary may need.
Thx

Can you check which version of the samsung firmware you are using? Does it end with "KL1" or something else?
I'm wondering if it might have been a bad flash or some other fluke. Here are the differences (with comments) between the 1st and 5th:
android ram_console support - this could do something unpredictable, but shouldn't. Basically, what this does is on boot up, it asks the kernel to reserve a VERY specific location and size of memory, and writes kernel messages here. On the next reboot, the kernel will check that exact chunk of memory and if certain headers are in place, it will stick a copy in /proc/last_kmsg. In this way, I might be able to see the kernel messages (including any panic) from the previous boot. Of course, the memory often gets trashed between the two boots, so this doesn't always work. Anyway, if something else is trying to use the exact same memory, it could cause problems (but it would cause the same problems for everyone with the same model tablet...)
bootanimation: This isn't actually a kernel change, but a modification to the init script that checks to see if a bootanimation file is present and if so it'll run samsung's own "bootanimation" binary instead of samsung's "samsungani" binary. In either case, the process is killed when the lock screen is first presented.
conservative governor stuff: As you aren't using setCPU, you are still using 'ondemand' so this stuff would have NO impact.
---
Honestly, the issue reported kind of surprises me. The kernel I'd expect to give people problems would be the 0101 one, as I mess with clock speeds and voltages in there. Since then, the changes have been very light. Can you try to delete any copies of Jan07 you might have sitting around, completely redownload it, and reflash it? Let me know if you have the same (or different) issues.
If you do have issues, use the market app called "OS Monitor" to export the dmesg log (while you are having the issue or immediately afterwards, but before rebooting.) Upload the exported log here (or somehow get it to me) with a full description of what was happening, if it was occuring during the time you exported the log (or how long previous to exported it occured), etc.
At that point, go ahead and revert to whichever kernel you are comfortable with and I'll study the log and try to see whats going on over the weekend.
Take care
Gary

Gary,
I flashed "GT-P6210 for US RETAIL" from this thread:
http://forum.xda-developers.com/showthread.php?t=1367478
Here's a screencap.
http://woodsware.aciwebs.com/galaxy_capture_01.png
I'll try the 20120107 kernel again, and let you know. It may be tonight....
Thanks!

i flashed the new kernel last night, and i haven't really had a chance to test it, but i did do some reading on the SOD deal, and i have my wifi set to "sleep when screen off" and i left home an hour ago, just pulled out my tab plus and BAM, fired right up.
I did want to ask you one request, any chance of implementing "smartassv2"? i'm gotten so lazy and spoiled with it...i never got around learning how to set profiles and junk, so this always helped me out...

rswoods said:
Gary,
I flashed "GT-P6210 for US RETAIL" from this thread:
http://forum.xda-developers.com/showthread.php?t=1367478
I'll try the 20120107 kernel again, and let you know. It may be tonight....
Click to expand...
Click to collapse
Okay, that's the older KK3 firmware. Here's what I'd like for you to do (if you could):
1. reflash that from the ODIN thread. That should revert recovery, the kernel, etc. Then attach your tablet to your PC and let Kies run to update the firmware to KL1. It would really be best if your firmware was updated BEFORE changing kernels. There are a couple reasons for this, but most importantly so that we are talking about the same thing (I've only ever tested these kernels with KL1.)
2. Make sure Kies has updated your firmware... settings->about->build number should show something like HTJ85B.UEKL1.P6210UEKL1. If Kies updates the firmware to something beyond "KL1" (if the number is greater than 1 or the last letter is beyond "L") then STOP, reply to this post letting me know the build number. (I'll want to revert my own tablet to stock and get it on the latest build for testing.)
3. Then go ahead and start playing with kernels - you will hopefully be good to go. if not, let me know.
Take care
Gary
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
Thedonk13 said:
i flashed the new kernel last night....
Click to expand...
Click to collapse
Please post this in the proper thread (in the DEV subforum.) I asked rswoods to post his question here in general as he can't post in DEV yet (doesn't yet have 10 posts), but I wanted the "public" to see the troubleshooting steps in case others have similar issues, etc. (I can't complain that people aren't searching for answers if the answers are hidden in PM's.)
Oh, and probably not. The same can be accomplished with SetCPU profiles, and I'm working hard to REDUCE the kernel footprint.
Take care
Gary

Gary,
OK... I reflashed the stock ROM, updated to KL1 through Kies, installed p6210_CWMR_20120107.zip, then flashed your 20120107 kernel. So far so good.
I'll see how it goes the next few days and report back.
Thanks for the help!

Gary,
Things are mostly good, but I'm still getting infrequent SOD's. I never know when it will happen... It will wake successfully several times in a row, but every once in awhile require the long press reboot.

rswoods said:
Things are mostly good, but I'm still getting infrequent SOD's. I never know when it will happen... It will wake successfully several times in a row, but every once in awhile require the long press reboot.
Click to expand...
Click to collapse
SOD's are unsolved. The majority of people having them are using the stock firmware and kernel (and replacing the kernel with mine doesn't seem to help whatsoever.) There's a thread dedicated to the subject here - you might find it interesting reading.
I'm glad the other issues you were experiencing have gone away...
Take care
Gary

Things are running great for me.

Event0 wakelocks

Hey guys, lately I've been having the eventx-xxxx wakelocks that *seem* to keep my phone awake and drain my battery. These wakelocks are usually event0 ones and followed by a four digit number which I believe to be the Process ID.
The current wake lock I am having is event0-2012 shown by BBS. It changes on every so the PIDs are rarely the same. It also happens that the 4 digit number happens to be the process ID of system_server. So there's something that's keeping it awake.
Lastly, the event0 is the synaptics touchscreen. So I'm guessing that this event0 wakelock keeps track of all the touches you make on the screen. This problem only appeared after the new touchscreen firmware updates so that may be the cause. Anyone have any thoughts on this matter?
Screenshots for proof below
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Thanks alot for this thread, very helpful. :good:

i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:

ak said:
Thanks alot for this thread, very helpful. :good:
Click to expand...
Click to collapse
Cool that means alot coming from you
wizyy said:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
Click to expand...
Click to collapse
Thanks! I've never had a 5 star thread before
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

I am on cm11s and have these same wake locks but all are less than 10 on so far a days worth of battery time. I don't think it's much of a problem for me and probably more for cm12? Anyways thanks for the info now I know where to look if it ever becomes an issue
Cheers

i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.

tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Agreed, it only started happening recently and I haven't installed any new apps, but newer Roms and kernels. So I really don't know whats causing it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Update: I flashed AK v30 kernel and the wakelocks seem to be gone now! Prior to this I was on Mahdi with stock kernel which had the wakelocks, and prior to that I was on Mahdi with AK v11 kernel which also had the wakelocks. This is only after an hour of "testing" though, so hopefully no apps I'm going to use will trigger them back :/
Edit: jk, wakelocks returned after a while. Screenshot attached. I rebooted the phone then left it alone for almost two hours.

Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4

mumaster20 said:
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
Click to expand...
Click to collapse
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

abhi08638 said:
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.

mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
I'll look into it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Nice investigating and bug hunting OP.

mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.

tracerit said:
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
Click to expand...
Click to collapse
That's curious. It might be because of new commits that might have been reverted in the kernels. Right now I'm using Ark kernel
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

abhi08638 said:
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?

abhi08638 said:
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Non of that, next to the standard autorotation and auto brightness of android itself. I did see that all the screen off gestures were turned on in synapse so I turned that off but it didn't seem to help. Its not that big of a deal though, probably some necessary stuff happening in the background. Still getting rock solid battery life! 6+ hours sot over 2 days so you don't hear me complain thanks anyways for sharing your info!
Sent from my One using XDA Free mobile app

kandalamv said:
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
Click to expand...
Click to collapse
Yeah I have noticed this wifi issue as well. Iight be related to the new drivers that were implemented but I haven't been keeping up with that so I don't know if it was reverted or not. I usually keep the wifi sleep policy to never. As I said before, I don't really know why they show up, but this "solution" is very dirty. The best way would be to find the cause of it.
I removes the s2w event because whatever triggered it actually uses power by keeping the capacitive keys on. So stopping that process ultimately saved me some battery.
Sent from my LG-P880 using XDA Free mobile app

random freezes on my s6 edge

hello,
I'm having a problem with my G925F
it randomly freezes (sometimes) on any screen, mostly while playing games, until i force reboot it (vol down+power for 7sec)
ROM: the global elite 4.1
Kernel: ROM stock.
any help would be appreciated, i tried different kernels but still problem, is it a ROM problem or hardware?
UPDATE: I tried different Roms too, same problem..
when im with headphones and it freezes, it starts a loud sharp noise that'll rape your ear (that's how it really feels)
and some glitchy lines appear on the screen..
it stays frozen for like 5 or 6secs then it reboots itself with a white solid LED light...
pleas guys what's this problem???

anyone??? ☹

zinou111 said:
hello,
I'm having a problem with my G925F
it randomly freezes (sometimes) on any screen, mostly while playing games, until i force reboot it (vol down+power for 7sec)
ROM: the global elite 4.1
Kernel: ROM stock.
any help would be appreciated, i tried different kernels but still problem, is it a ROM problem or hardware?
UPDATE: I tried different Roms too, same problem..
when im with headphones and it freezes, it starts a loud sharp noise that'll rape your ear (that's how it really feels)
and some glitchy lines appear on the screen..
it stays frozen for like 5 or 6secs then it reboots itself with a white solid LED light...
pleas guys what's this problem???
Click to expand...
Click to collapse
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.

tiktakt0w said:
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.
Click to expand...
Click to collapse
I'm pretty sure its hardware too, but idk which part is exactly damaged?
i didn't drop my phone, water or dust didn't touch it in anyway..
the problem happens while playing PUBG Mobile or similar heavy games.
btw.. can battery cause such problems like this?

tiktakt0w said:
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.
Click to expand...
Click to collapse
It happened again, this time the device wasn't hot, no apps on background, no gaming, nothing. i was just on home screen swiping looking for an app, it suddenly froze. with those glitchy lines, rebooted itself with white solid LED light. i didn't use it for like 10min.. i came back again, unlocked it, swiped up for apps menu.. BOOM, froze again with those glitchy lines. this time it didn't reboot, it blacked out after 5sec.. i tried different button combinations to turn it on again, no luck. i plugged in the charger and waited for 2min, nothing. then i got into download mode [warning screen] (while plugged). i pressed the vol- button to restart, it booted up normally. now I can't really use it cause i don't want it to get worst. btw, sometimes when it freezes & reboot itslef, All settings are reset to default.
Any suggestions on what to do?

zinou111 said:
I'm pretty sure its hardware too, but idk which part is exactly damaged?
i didn't drop my phone, water or dust didn't touch it in anyway..
the problem happens while playing PUBG Mobile or similar heavy games.
btw.. can battery cause such problems like this?
Click to expand...
Click to collapse
I doubt it's the battery, but you'll never know unless you try. Glitchy lines or artifacts are usually the sign of a failing gpu.

tiktakt0w said:
I doubt it's the battery, but you'll never know unless you try. Glitchy lines or artifacts are usually the sign of a failing gpu.
Click to expand...
Click to collapse
okay.. but why it sometimes happens while doing nothing... and sometimes it doesn't freeze at all even while gaming for hours...
one more thing, when i shake thr phone near my ear, i hear something like (tick tick tick...). i taught that maybe that's it. but i asked my friend who has an s6e too (G925T) he said that he has that sound too when he shakes it, but doesn't encounter any problems with his phine... soo??

What I most associate with that sound, and the phone freezing... is CPU hotplugging. Are there any apps that affect these? /sys/class/devices/system/cpu/cpu./online
sys/class/devices/system/cpu/ whichever one isn't cpu 0-7 or cpuidle.

Bryan48765 said:
What I most associate with that sound, and the phone freezing... is CPU hotplugging. Are there any apps that affect these? /sys/class/devices/system/cpu/cpu./online
sys/class/devices/system/cpu/ whichever one isn't cpu 0-7 or cpuidle.
Click to expand...
Click to collapse
i have no idea.. how can I know which apps do this?
and what is CPU hotplugging??

zinou111 said:
i have no idea.. how can I know which apps do this?
and what is CPU hotplugging??
Click to expand...
Click to collapse
Which apps... maybe something related to "editing kernel settings", viewing CPU info (root), etc.
CPU hotplugging is the stopping (and returning when needed) of CPU cores (big cluster, etc), to save power, etc. When it fails, it does... that (maybe not the artifacts?).
/sys/devices/system/cpu/cpu[0-7]/online.
others related to CPU hotplugging...
/sys/devices/system/cpu/... ?
/sys/power/... ?
GPU hotplugging is /sys/devices/14ac0000.mali/power_policy (/sys/class/misc/mali0/device/power_policy). Writing "always_on" disables it, "coarse_demand" enables it, "demand" enables it. I haven't had any problems with this, only temperature reading.

Bryan48765 said:
Which apps... maybe something related to "editing kernel settings", viewing CPU info (root), etc.
CPU hotplugging is the stopping (and returning when needed) of CPU cores (big cluster, etc), to save power, etc. When it fails, it does... that (maybe not the artifacts?).
/sys/devices/system/cpu/cpu[0-7]/online.
others related to CPU hotplugging...
/sys/devices/system/cpu/... ?
/sys/power/... ?
GPU hotplugging is /sys/devices/14ac0000.mali/power_policy (/sys/class/misc/mali0/device/power_policy). Writing "always_on" disables it, "coarse_demand" enables it, "demand" enables it. I haven't had any problems with this, only temperature reading.
Click to expand...
Click to collapse
i don't have any apps of this kind, i used to have Kernel Auditor & Synapse in the past Roms cuz i was using custom kernels.. but now, im on stock kernel.
how can clear all kernel settings and start fresh?
however, it didn't reboot today. i was expecting it every time i use it. but no freezes or reboots.

zinou111 said:
i don't have any apps of this kind, i used to have Kernel Auditor & Synapse in the past Roms cuz i was using custom kernels.. but now, im on stock kernel.
how can clear all kernel settings and start fresh?
however, it didn't reboot today. i was expecting it every time i use it. but no freezes or reboots.
Click to expand...
Click to collapse
Kernel 'settings' are reset to the default (defaults may change after flashing a kernel) on reboot, unless there's a script (init.d, etc) that changes the settings on boot, or later. If it happens again, maybe the error messages are in /proc/last_kmsg.

Bryan48765 said:
Kernel 'settings' are reset to the default (defaults may change after flashing a kernel) on reboot, unless there's a script (init.d, etc) that changes the settings on boot, or later. If it happens again, maybe the error messages are in /proc/last_kmsg.
Click to expand...
Click to collapse
okay.. i flashed Aldeon this afternoon.
after booting, i installed Synapse. after opening it and granting superuser access.. it showed me the screen saying that kernel settings are reset ti default cuz system wasn't stable for 2mins after booting... this usually appear after it really happens...
its weird that it appeared after flashing the kernel directly...
no reboots or freezes so far, since yesterday.

zinou111 said:
okay.. i flashed Aldeon this afternoon.
after booting, i installed Synapse. after opening it and granting superuser access.. it showed me the screen saying that kernel settings are reset ti default cuz system wasn't stable for 2mins after booting... this usually appear after it really happens...
its weird that it appeared after flashing the kernel directly...
no reboots or freezes so far, since yesterday.
Click to expand...
Click to collapse
Hello @zinou111 how has your phone behaved after what you did? I am currently having the same issues you had and I'm looking for a solution.
Yours is the only hope after a couple hours of searching.

really? same symptoms as mine?
well... i didn't do anything at all... I turned it off and threw it for like 4 days... and last few days, i was bored, so i got it back and turned it on.. i faced this problem only 4 times within this week... i didn't do anything..
it used to be +10 times a day... now its just gone i think & i hope... it didn't freeze last 3 days & it works flawlessly!
i hope this can help you

Solution! And Cause!
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Install Synapse or MTweaks
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!

ArkPly said:
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!
Click to expand...
Click to collapse
thanks bro! but i don't think its a software problem, cuz i had it completely fresh & new last week, i mean the guy flashed it using those things called BOXs.. like.. i'm even getting OTA updates lol... still same problem..
but i left it like i said turned off for about 3 days & i can tell that it got better.... probably the CPU is failing i guess
i'll try the 1st solution when i face the problem again

Yes I can safely say...
zinou111 said:
thanks bro! but i don't think its a software problem, cuz i had it completely fresh & new last week, i mean the guy flashed it using those things called BOXs.. like.. i'm even getting OTA updates lol... still same problem..
but i left it like i said turned off for about 3 days & i can tell that it got better.... probably the CPU is failing i guess
i'll try the 1st solution when i face the problem again
Click to expand...
Click to collapse
Ok but I can tell you that for me both ways 1 and 2 worked! (S6 Flat by the way)
I installed the rom(Way2) and no crashes anymore without changing the voltages... On stock rom(odin clean installed) I still had random reboots and freezes!:victory:
But when you flash a custom kernel and changes voltages (Way1) also on stock no more random reboots!
So both ways worked try it out!

ArkPly said:
Ok but I can tell you that for me both ways 1 and 2 worked! (S6 Flat by the way)
I installed the rom(Way2) and no crashes anymore without changing the voltages... On stock rom(odin clean installed) I still had random reboots and freezes!:victory:
But when you flash a custom kernel and changes voltages (Way1) also on stock no more random reboots!
So both ways worked try it out!
Click to expand...
Click to collapse
okay man! that was really helpful! ill try it and keep u up to date!
thanks alot bro!

ArkPly said:
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Install Synapse or MTweaks
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!
Click to expand...
Click to collapse
Hello
I dont understand this : Upvolt all values under 1000mHz to 800mAh in both big and small cores
Maybe have you a screenshot ????
thx