Develop Bugs

[Q] G2 w/ CM7 Lockscreen, volume down, and home button issue...

Phone:
T-Mobile G2
CM-7.0.0(full wipe then flashed from Post-OTA Stock ROM)
O/Cd to 1.017 Ghz with SetCPU
.26 Radio
Problems:
- Lockscreen never appears at all. Phone wakes straight into last activity
- Volume Down wakes phone. Not set in settings to do so.
- Home button gives haptic feedback on press, but performs no action on short or long press.
- All calls, whether to T-Mo or GV number go straight to voicemail.
Context:
I had just fixed a boot issue with CM7 by wiping cache and dalvik. I then decided to install Zeam Launcher, which has since been uninstalled. Have used SetCPU to set clock with On Demand governor back to max 800 mhz. No effect.
Also have been testing app on device but only has simple activities with no permissions needed and it runs with no errors or warnings.
Anyone have an answer to any of these issues? I have done a soft reboot and a battery pull. Thanks for the help.

Ok, here's the logcat log when I press the power button to turn the screen off, and the again to unlock it.
04-22 20:04:03.297: INFO/power(1485): *** set_screen_state 0
04-22 20:04:03.347: DEBUG/WifiService(1485): ACTION_SCREEN_OFF
04-22 20:04:03.497: DEBUG/SurfaceFlinger(1485): About to give-up screen, flinger = 0x93b98
04-22 20:04:03.507: DEBUG/AK8975(1385): Compass CLOSE
04-22 20:04:08.167: INFO/power(1485): *** set_screen_state 1
04-22 20:04:08.257: DEBUG/SurfaceFlinger(1485): Screen about to return, flinger = 0x93b98
04-22 20:04:08.327: DEBUG/AK8975(1385): Compass Start
04-22 20:04:08.687: DEBUG/WifiService(1485): ACTION_SCREEN_ON
04-22 20:04:16.267: DEBUG/dalvikvm(2483): GC_EXPLICIT freed 11K, 55% free 2708K/5959K, external 461K/973K, paused 76ms
04-22 20:04:31.247: DEBUG/dalvikvm(2491): GC_EXPLICIT freed <1K, 52% free 2789K/5703K, external 0K/0K, paused 60ms
Click to expand...
Click to collapse

Have you tried to reflash? redownload the rom and then flash.
Sent from my HTC Desire Z/G2 Using XDA Premium App

I was trying to avoid it, but I did a complete wipe(user data, cache, and dalvik) then re-flashed. Everything back to normal. With the calls, is there a known issue with Google Voice hijacking email causing issues on T-Mo in general or with CM7 in specific?
Thanks for the help. Just needed someone to convince me that the wipe-and-flash was what I had to do. Just a time suck.

I'm going through the same exact problem, I tried doing a full wipe, fixing permissions, reflashing, I don't know what else to do?

hey, did you ever get this issue resolved? I'm having a similar issue and my volume key won't respond

I'm facing this problem after going from Jellybean back to Gingerbread. Anyone resolved this?
---------- Post added at 11:44 AM ---------- Previous post was at 11:15 AM ----------
Solved. I flashed ICS gapps instead of GB gapps.

[Q] event0 and event2 wakelock preventing deep sleep

Hello,
I'm currently running the lastest (150118) release of mokee, and my phone can't seem to enter deep sleep. In BBS, the event0 and event2 wakelocks take up nearly 50% of the device on time, and I get an average of a few seconds of deep sleep time, resulting in terrible battery life. Attached are the BBS screenshots.
I did some research and figured out that event0 and event2 are the events from the touchscreen and hardware buttons, but I'm not sure how this would affect the battery levels especially when the screen is off.
Any help is appreciated.
Thanks in advance!

it's not, it's a wifi issue, and most likely an issue with your router. it seems that with some routers produce some weird signals with your phone, and leads a rogue app to constantly try and use your wifi whilst you're in deep sleep.

Is this supposed to happen even while my WiFi is off? It seems that no matter where I go, the phone just won't enter deep sleep and seems to drain more battery locked and off than unlocked. I've tried switching to nameless 4.4 and it is giving me the same problem, which doesn't seem right.
Sent from my Find7 using XDA Free mobile app

The nature of eventN wakelocks is that they almost NEVER actually hold the device awake for very long.
They're a symptom, not a cause - when the system resumes, they hold a wakelock from the time the kernel resumes, up to the time when the frameworks wake up and process the event (which in the case of a resume is, if I recall correctly, pretty much a null event.)
So if you have high eventN wakelocks - something is causing your system to suspend-thrash.
In older kernels, there was a "suspend_backoff" driver to handle this case, and at least hint as to the nature of the problem. I reimplemented the backoff functionality in Omni's kernel to help debug such an issue. (Way back last spring, there was a bug in the battery/charger management driver that would cause a stuck interrupt to prevent suspend. The device would try to suspend, error and abort, then resume, then immediately try again, over and over and over again. You could actually SAVE power by holding a wakelock to prevent the thrashing.)
You'll probably need to look through dmesg to figure out why your device is suspendthrashing.

Hi Entropy!
I've gone through and attached a dmesg.
I'm not particularly sure how to interpret this, but instead of trying to suspend and abort, it seems as if the device is continuously suspending for 0 seconds and waking up. I'm not quite sure why.
Could you take a look? If you need anything else to figure this out I'd be happy to provide it.
Thanks!

HTC ONE M8- Sudden Power Off When Battery Is Below 50%

Sudden power off when battery is less than 50 percent
Hi community,
I would be very glad to get some help for the problem below. Or maybe you can guide me how to provide more information to investigate it.
Problem
The phone sometimes powers itself off abruptly which can lead to database corruption. So it is very annoying...
However, it only seems to occur in some cases:
It happens as soon as battery is below 50% (this is not exact, but pretty close)
It only happens when the screen is off. May happen after 30 sec to 5 min.
It never happens when a USB cable is connected (power-only or computer)
It does not seem to happen when a "background task" is running
In some rare cases, it does not happen at all, or maybe just has not happened for a longer period of time. I could not determine what is different about the state of the phone then. When I turn the screen on once, and off again, the chances are high that it will power off very soon!
By "background task" I mean something like playing music, but I can not exactly define it. It can stay on like for one hour without any problems (screen turned off). It also stays on when, for instance, the timer is running and the screen is on.
So it does not seem to be a problem of the battery...
ROMs
I tried the following ROMs, all with the same issue. When switching ROMs, I always wiped system, data, cache, dalvik-cache. Never flashed another Zip on top (like Gapps). The device is unlocked using the official procedure by HTC.
Two official versions of cm12.1
A BlissPop v3.9 earlier build than below
BlissPop-v3.9-m8-OFFICIAL-20150827-0154 (currently running)
SkyBliss-v3.2.1-m8 (fantastic ROM, btw!)
Stock v4.19.111.2 + OTA to v4.19.111.3
More details of stock:
Relocked and flashed the Firmware v4.19.111.2 (Android File Host fid=95916177934521492)
Unlocked, flashed TWRP, then Stock v4.19.111.2 (Android File Host fid=95916177934527598)
Relocked and receive OTA v4.19.111.3
Debug
Below is a Logcat session. The numbers are line numbers. Of cource, they are not relevant, but they put things into perspective.
1163: I/PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
1371: I/PowerManagerService: Dozing...
1389-1466, 5 times occured: E/libsuspend: Error writing to /sys/power/state: Device or resource busy
1467: I/PowerManagerService: Waking up from dozing (uid 1000)... (I pressed the power button to see, if it is still alive)
...
2743: I/PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
2931: I/PowerManagerService: Dozing...
2942, once: E/libsuspend: Error writing to /sys/power/state: Device or resource busy
2959: The phone is dead
There are also a log of those lines when the screen is off:
I/qdhwcomposer: handle_blank_event: dpy:1 panel power state: 0
(dpy:0/1 changing a lot)
Troubleshooting
I changed the CPU governor in my current BlissPop ROM: was Lionheart, tried Ondemand, Intellidemand, and Interactive. Subjectively, it slightly reduced the amount of battery percentage when the problem begins to occur. However, the problem persists and I did not take note of the battery charge.
Left default setting for "power safer".
???
What can I do about it?
Are there any tools to investigate the problem in more detail?
Does anyone have the same problem?
Thanks a lot,
Adi

Added Debug section

Battery drain due to automatic screen wake up

Hi Friends,
In my SM-G920P, my screen wakes up automatically every 10-15 seconds. This doesn't happen 24X7 but whenever it happens it continues for a long time and stops automatically. I have disabled gesture wake up, raise to wake etc and also tried safe mode but all in vain. Disabled all notifications, turned on airplane mode also but same issue. Tried Wake Lock powermanager which helps some times but it drains the battery. The issue started when I flashed official 7.0 ROM after rooting my device. So as you can see the knox is broken and can't take to Samsung.
I love my S6 a lot. Any suggestion would really help.
Thanks

Jena-HtcOneM8 said:
Hi Friends,
In my SM-G920P, my screen wakes up automatically every 10-15 seconds. This doesn't happen 24X7 but whenever it happens it continues for a long time and stops automatically. I have disabled gesture wake up, raise to wake etc and also tried safe mode but all in vain. Disabled all notifications, turned on airplane mode also but same issue. Tried Wake Lock powermanager which helps some times but it drains the battery. The issue started when I flashed official 7.0 ROM after rooting my device. So as you can see the knox is broken and can't take to Samsung.
I love my S6 a lot. Any suggestion would really help.
Thanks
Click to expand...
Click to collapse
The good news is that it is not your phone or the operating system. I am pretty sure that there will be one app that turns out to be the culprit.
Wakelock Detector should help you find that.
If that doesn't work, wipe everything and reinstall. Here are instructions to install: https://forum.xda-developers.com/showpost.php?p=73232175&postcount=352

koop1955 said:
The good news is that it is not your phone or the operating system. I am pretty sure that there will be one app that turns out to be the culprit.
Wakelock Detector should help you find that.
If that doesn't work, wipe everything and reinstall. Here are instructions to install: https://forum.xda-developers.com/showpost.php?p=73232175&postcount=352
Click to expand...
Click to collapse
Thanks a lot. I have installed wakelock detector just now and waiting for the problem to reoccur.

Deep Sleep Issue In nougat rom

I have been using Aex rom ,the phone goes into deep sleep mode which cause fingerprint unlocking delay and some notifications are not right on time...Any solution for this ?

did you block something in alarm blocker?
it works fine in my experience .
If you use greenify, read the welcome screen , there is an option for user,if they use fingerprint often ? if you choose no at this stage, greenify will block relevant sensor while screen off.

locolyric said:
did you block something in alarm blocker?
it works fine in my experience .
If you use greenify, read the welcome screen , there is an option for user,if they use fingerprint often ? if you choose no at this stage, greenify will block relevant sensor while screen off.
Click to expand...
Click to collapse
did you block something in alarm blocker?
no
couldnt find this option in greenify

vatstarun18 said:
I have been using Aex rom ,the phone goes into deep sleep mode which cause fingerprint unlocking delay and some notifications are not right on time...Any solution for this ?
Click to expand...
Click to collapse
Try clean flash

Dhinesh1999 said:
Try clean flash
Click to expand...
Click to collapse
Already done that dalvik/cache-system-internal data

Clean flash
Dont use greenify
Use naptime + background restrictor instead
Aet apps that you need notifications from as 'not optimising' in app settings - special permission - battery optimisation