[Q] Cannot charge on turned off phone - Omni Q&A

Hi all!
I'm using latest Omni nightlies for the Xperia Z (yuga 6602) and I discovered this bug where if you plug in the charger while the phone is off, the phone starts and boots by itself as if the power button was pressed.
Could anyone confirm this issue and how can it be fixed?
Thanks in advance
Kind regards

I'd check with the forum for your phone first.
It sounds to me as though there is a problem with the way that "init" is detecting a "charger" boot and responding to it.

i did check, this issue isn't reported
Sent from my C6603 using xda app-developers app

Issue still present with latest nightlies 0317
I read on the official gerrit changelog that this issue had been fixed with today's nightly, but I confirm that that's not the case, charger still turns on an turned-off phone

If you haven't already, I'd file this on jira. Much easier to track.

Was a bug report for the originally described issue already filed on (remove spaces):
Code:
ht tp://jira.om nirom.org/secure/Dashboard.jspa
?
I do notice that on my Samsung Galaxy S4 SGH-M919, after the device is powered down and a charger is connected, the device boots to the OmniROM, but without the touchscreen's touch support (hardware buttons still work) and charges otherwise as if the device were already on and charging.
I had freshly installed OmniROM 4.4.4-20150520-jflte-FINAL and then configured the settings and have not installed other apps.
I do notice that under Settings --> Display , there is an option "Wake on plug" with description ""Turn the screen on when connecting or disconnecting the charger". Regardless as to whether the setting is set or not set, the device seems to behave the same.

Related

[Q] Slimport causing sleep of death on 4.3?

Does anyone else experience the sleep of death bug (akin to what happened with Netflix) after having connected your HDTV through Slimport for a short while? It seems to happen regardless of what I'm doing on my phone, just having it connected for a short moment will cause it.
This is on stock Android 4.3 (JWR66V), whereas it was working just fine for me on 4.2. My phone is rooted, but there's nothing running that requires root access while this problem occurs.
Also, I'm using the "official" Slimport adapter, i.e. the only one that existed for quite a while.
Would hate having to send my phone back in, but alas that's what I'll do if it's just affecting me.
I've the same issues since 4.3 Everything was fine before with 4.2.2. When i unplug slimport from nexus4 i cant activate display anymore.
This hapepns sometimes after cahring, too.
So i think your device is ok, just an 4.3 fault like many other bugs
Thanks for the reply. So I'm not completely alone with this!
But I do find it odd that I could not find any existing discussion of this topic elsewhere on the net.. are there just not that many people making use of the HDMI feature or is the majority of people simply unaffected by this problem?
I'm not sure. I've the same issue with charging. I misspelled this on my first post. Same situation, unplug charging cable and i can't activate the display. I found a workaround for this issue, I unplug it only when the display is on. The latest OTA doesn't fix it. Maybe we should create a bug report on googles bug tracker.
There is a thread about this issue in Googles mobile support forum. You should post there, too. So maybe we get more attention about this serious problem. I can't post links yet, search for: "After 4.3 Android updated, the Nexus 4 always shuts off randomly !!! HELP!!!"
I'm having this issue with my Nexus 7 II. Very annoying, can't watch a movie without it disconnecting. Any fix for this?
Currently not, I hope that Kitkat will fix this
I'm having the same problem on 4.4
Does anyone know how to fix this?
Thanks in advance
Same here on 4.4 but it only happens when my photo is low on charge.
E.G when there's low charge slimport works o.k but when I unplug it the phone dies and requires me to push the power button for 10 seconds to get the photo to work again.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Maybe we should dump Logcat to get the reason why it dies. It tried it several times but with no luck. When i received System log ouputs via adb, the phone doesn't die.
Gesendet von meinem Nexus 4 mit Tapatalk
was found a solution for this problem?

[DISCUSSION] Problems & Bugs on stock CM11S

I created this thread in order to share the problems which I am facing on my 1+1. Hope can get resolved by CM soon... As well as others can discuss about the problem and solution (if available) that we are facing. State method if others can try reporduce the problem to confirm will the problem affect all other 1+1 device, if have screenshot the better.
Firstly, please state:
ROM version (Root Y/N, Other than CM11s don't discuss here, Nightly, Color OS etc.):
ROM mod (State which app will affect system files, from your opinion):
Custom kernel (Y/N, If yes please state kernel you've used):
Model & storage (CN/INT ver, 16/64G):
Recovery (Apparently has nothing to do with ROM I think, just state better)
Problem/bugs:
Okay, start with me...
ROM version: CM11s Rooted, XNPH25R - latest at the moment
ROM mod: AdAway, BusyBox 1.22.1, Xposed Framework 2.6
Custom kernel: NO
Model & storage: CN ver 16G
Recovery: PhilZ Touch 6.49
Problem/bugs:
USB OTG will be not functional when plug in while the screen is OFF, if screen is ON then no such problem, even if you insert USB OTG while screen off and reinsert back after waking the phone, the USB OTG still not working (suspect deep sleep cut off USB OTG power) - Temporary solution: Reboot the phone
MX Player crashes more often while playing with H/W decoder, however S/W decoder works flawlessly. Format Played - 480p FLV.S/W uses more battery consumption so I don't like it, I confirm the same type of video played on other phone doesn't have such MX Player FC problem (If it crashes too many times it will stop working at some point, you can't even play MP4 files with H/W decoder and or stock Gallery app - Temporary solution: Reboot the phone
GPS sometimes takes forever to lock - Temporary solution: Reboot the phone
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
As you can see all these problems can be fixed by rebooting the phone, so I guess it's ROM related problem.
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
oneplusonepwns said:
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
Click to expand...
Click to collapse
At battery stats see any other apps are draining your battery. In my case, sometimes Android OS/System, Google Play Service and Media Server are keeping awake draining the battery while screen is off, in that case, enable privacy guard deny them from keeping awake, or reboot your phone.
ROM version: CM11s running XNPH25R
ROM mod: Rooted with xposed framework, AdAway.
Custom kernel: Franco Kernel
Model & storage: 64gb sandstone black
Recovery: Stock
Firstly: I always like to disable the backlight illumination of the hardware buttons. This works perfect but it doesn't stick. After reboot, its back to lit up.
Secondly: Notification sounds can't be set on per app basis. For eg, Hangouts has its own notification tones and I like gmail and other email app to have different notification tone from the system wide one, however it doesn't happen. All apps use the system wide notification tone regardless of what I set separately on them. I guess this has something to do with the theme engine coz I chose tones from it.
Thirdly: when rotation is locked, camera interface doesn't rotate. I thought camera interface is meant to auto rotate regardless of the "rotate setting on or off"
Sent from my One using Tapatalk
ROM version: CM11s XNPH25R rooted
ROM mod: Why mess with a good thing?
Custom kernel: N
Model & storage: INT 64G
Recovery: PhilZ CWM
Lock screen delay doesn't work on built-in custom lock screen. Works fine otherwise.
ROM version: CM11S XNPH25R, not rooted
ROM mod: None
Custom kernel: N
Model & storage: INT 64G
Recovery: Stock
[ ] 2 Google Play Services force closes while setting up phone
[ ] Ringtone and default notification sound were reset to default once randomly
[ ] Double-tap to wake setting becomes checked again randomly after turning it off, but the feature is not re-enabled
[ ] Google Now keeps showing "Good morning / evening! Here are your current cards" and "Google Now is always working for you" cards even after swiping them away many times
[ ] In-call speaker volume is too low, MUCH lower than volume for everything else
[ ] Some ringtones and notification sounds are duplicated with different names
[ ] The screen seems to miss touches occasionally
[ ] "Ok Google" and Google voice searches only work if I speak VERY loudly
[ ] The phone occasionally sticks in landscape orientation and I have to shake it to get it to rotate back to portrait
[ ] Scrolling is not as smooth as my stock Nexus 5 (more dropped frames) in not all, but some apps. This could just be poor optimization, but I'm calling it a bug because really this phone should always perform better than a Nexus 5 because it has an 801 and 3GB of RAM.
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Does this have anything to do with it's multi touch issues?
Sent from my One using Tapatalk
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: Busybox,Xposed
Custom kernel: No
Model & storage: CH 64G
Recovery: Philz
Problem:
Screen not wake when press power button,navigation light is on, but screen not wake. my solution for now is need to force restart.
Sent from my One using XDA Premium 4 mobile app
SleemLDJ said:
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Click to expand...
Click to collapse
Yes, I believe I have experienced this and quite often too.
Apart from the missed keystrokes, my phone reboots randomly every 30 mins or so. I haven't gotten around to root causing it.. Maybe due to ART (?)
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: None
Custom kernel: No
Model & storage: INT 64G
Recovery: Stock
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Maybe I'm just lucky I haven't come across any problems yet.
CM Version 11.0-XNPH25R
Completely Stock.
magnum73 said:
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Oh god that looks terrible.
i haven't seen this mentioned yet, but sometimes when i open the Google keyboard in landscape mode, it will only show 1 line of keys. i fix it by force stopping the keyboard
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One of the moderators on the OP forums replied to my comment about the hotword detection and stated it is a known bug with CM and has been addressed and will be resolved in the next OTA.
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
The speakerphone problem has been addressed in one of the recent nightlies. Call volume is good now. It is scheduled for the upcoming ota.
M9 just came out. Only in a matter of time we get the ota for the next update
jarjar124 said:
M9 just came out. Only in a matter of time we get the ota for the next update
Click to expand...
Click to collapse
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
cas8180 said:
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Where
Sent from my One using XDA Free mobile app

[Q] When I plug in my Note 3 to charge it Samsung tune starts

Hello guys
I am having a strange issue with my rooted note 3 here.
Everytime I plug it in on the AC power for charging, it starts reproducing Samsung tune and there is no way to stop it but by switching it off.
The last app I installed was and Xposed framework tweak (the S5 ultra power saving mode), though I don't think that's the reason causing this.
Please can anyone help me fixing this issue?
Hi, this seems to be the solution:
http://forum.xda-developers.com/showthread.php?t=2853225
Sent from my SM-N9005 using XDA mobile app
yeah its been fixed now it was gravity box 3.2 now uodated to 3.3 alls working

D802 does not want to wake up (backlight is active, but screen stays black)

After upgrading my 16GB D802 from a beautifully working CM 10 to CM 13 the following problem occured:
After the screen shuts off (either by the phone going to standby or the proximity sensor in case of phone calls), it takes several attempts to activate the screen (you see the backlight turning on, but the screen stays black, then you have to click the power button to go into standby and try again til it works; tapping and pushing the power/standby button to wake the screen up work equally bad)
I tried going back to CM 10. On CM 10 the screen activates and deactivates as it should, but I had problems with very very unstable connections to wifi and cellular (which I had not before). (Also: I was stupid enough to not have made a backup of the previously stable CM 10 installation.)
All in all, I tested CM 13, 12, 11, and 10. 13 and 12 have the screen problem and 10 and 11 have the connection issue.
For all testing I used TWRP and the hybrid bootstacks.
Has someone experiences similar issues?
I would greatly appreciate any help.
Thanks so far!
Kind regards,
toas7
Cyanogenmod does not seem to be the problem. I've got the same issues with e.g. Mokee (MK51.1) and the Turbo ROM (Turbo-d802-4.0).
Might the bootstack be the culprit after all? Is there something that could have been gone wrong?
I tried the (zipped) stock ROM: the problem remains
Edit:
Flashing the modem (with a flashable modem) solved the issue with wifi and cellular on CM 11.
Software or hardware
Hello, I have the same issue but in addition the device is extremely lagged. Although I am still with stock mod and no root, by the moment. Could you help me?

Notification lights not working after install cm13 build from mparus

Hi
I ask this question here, as I’m knew in the forum I can’t write it directly in the ROM post where would be more appropriate.
I have installed the in the phone the CM13.0 ROM built by mparus, I have used the cm-13.0-20161118-UNOFFICIAL-mparus-without_root-g760.zip build, the last one in this moment. The phone works correctly, I only had a pair of minor issues:
-phone app was not working, caused a reboot when trying to use it: it’s a vanilla cyanogenmod problem, it’s solved choosing the phone app as default for making calls
-camera app doesn’t detect the camera device: I have read that is a bug of the official camera app, can be solved installing another app as open camera
I have a serious problem for which I have not found information about. It’s with the notification lights, they are not working except for indicating the charging status of the device, not for mails, missed calls, etc. I tried all the possible combinations for this without luck. I have also tried third party app’s like light manager and they don’t work also, perhaps something is broken in the build but I’m not sure.
Any of you has experienced this problem with the mparus mod in the ascend g7? Can you give me any advice? I’m a bit frustrated about this
Thank you
Do a clean re-install of the ROM I'd say..

Categories

Resources