My phone hanged and restarted when playing a game, and now double rap to wake isn't working. I rebooted several times and turned of auto brightness but that didn't help. It used to work fine! Double tap to sleep works though. Please help me.
SaraKumar said:
My phone hanged and restarted when playing a game, and now double rap to wake isn't working. I rebooted several times and turned of auto brightness but that didn't help. It used to work fine! Double tap to sleep works though. Please help me.
Click to expand...
Click to collapse
A little bit more information would be nice to have... Like... Which Romy, kernel, apps, clean flash.?
Sent from my Z1 using my hand
strongst said:
A little bit more information would be nice to have... Like... Which Romy, kernel, apps, clean flash.?
Click to expand...
Click to collapse
I'm running the stock ROM. Not rooted, i didnt do anything with my phone. It had rebooted twice before, while using some apps(I don't remember which). Os version : 12.1-YOG4PAS9IG. All apps I run are from the play store, and none of them have administrative rights. Thanks!
SaraKumar said:
I'm running the stock ROM. Not rooted, i didnt do anything with my phone. It had rebooted twice before, while using some apps(I don't remember which). Os version : 12.1-YOG4PAS9IG. All apps I run are from the play store, and none of them have administrative rights. Thanks!
Click to expand...
Click to collapse
Try turn dt2w off, reboot, then turn it on again. I had this problem too with stock rom.
SaraKumar said:
I'm running the stock ROM. Not rooted, i didnt do anything with my phone. It had rebooted twice before, while using some apps(I don't remember which). Os version : 12.1-YOG4PAS9IG. All apps I run are from the play store, and none of them have administrative rights. Thanks!
Click to expand...
Click to collapse
Sent from my Z1 using my hand
Buddy.. Thats a bug. Dt2w is working inconsistently ? ?
Try what strongst said..
That's the only solution..
Use custom rom for dt2w.
Sent from my ZUK Z1 using XDA-Developers mobile app
Turn off dt2w.
Off from side button.
On from side button.
Turn dt2w on.
Done....until some message appears.
Do again...
strongst said:
Try turn dt2w off, reboot, then turn it on again. I had this problem too with stock rom.
Click to expand...
Click to collapse
Thank you!! This fixed it
Related
I take no responsibility for any harm that comes to your phone as a result of applying this mod.
I'm not really into doing themes but some people have been asking for this and I realised I could do it pretty easily.
Requirements:
- Should be fine for all B136/B160 roms. Please post your results.
Download:
Available Here
Undo package will be available soon
Notes:
- As stated I'm not really that into doing themes, so there may be some errors or places where it looks weird. One error I'm aware of is that if you add a number using the dialer it will show the 11% battery discharge icon next to create new contact. I can't really be bothered fixing this for now as it requires some messing around in the XML.
Screenshots attached, login to view.
working great here - thanks VERY much, I was really missing the dark notification bar after moving from a Desire
Dr_Ash said:
working great here - thanks VERY much, I was really missing the dark notification bar after moving from a Desire
Click to expand...
Click to collapse
+1 works great thank you
Thanks will give it a try
How to install this theme?
Thank you.
loungedogg said:
How to install this theme?
Thank you.
Click to expand...
Click to collapse
I just connected the phone to my pc in recovery-mode and replaced "framework-res.apk" and "services.jar" with stockwells.
Thank you stock youre my hero
Edit: how do you replace the framework-res.apk and the services.jar?
I connected my phone (recovery mode) wo my pc, and when i go mount /system nothing happens?
Sent from my Desire HD using XDA Premium App
Sorry I thought everyone was used to recovery by now! Copy Ginger.zip to your sdcard, boot to recovery then choose install zip from sdcard. Select Ginger.zip and install and you're done.
Is anyone experiencing battery drain? My battery died in about 8 hours yesterday, could be a result of an app or my kernel though..
Sent from my u8800 using XDA Premium App
stockwell said:
Sorry I thought everyone was used to recovery by now! Copy Ginger.zip to your sdcard, boot to recovery then choose install zip from sdcard. Select Ginger.zip and install and you're done.
Is anyone experiencing battery drain? My battery died in about 8 hours yesterday, could be a result of an app or my kernel though..
Sent from my u8800 using XDA Premium App
Click to expand...
Click to collapse
No battery drain here pal, same as normal
Seems I had my wifi policy set to never sleep for some reason. All good, don't worry. I didn't think it was possible for the framework change to cause the battery drain but thought I would check just in case.
im not sure right now, but i think i tried to install from perfect recovery and got an error that it failed, that's why i just replaced it manually.
It works on B137 FLB rom?
I think I found a bug. 11% battery icon has appeared beside the "Create new contact" button.
See partial screen shot below.
REMOVE_THISdl.dropbox.com/u/16950257/bug.jpg
When trying to turn on WiFi from preferences goes to reboot, only at my phone?
ShallNoy said:
When trying to turn on WiFi from preferences goes to reboot, only at my phone?
Click to expand...
Click to collapse
Yep, i had that problem too. Wasnt sure before if it was the theme but guess it is since you have it as well.
IMO this is a REALLY NICE theme, installed it on manufacturer's B160. Now after I upgraded to B162 and installed this it keeps crashing several processes continuously. Is it only on my phone (guess not)?? Would it be possible to fix this for B162 too! Can't wait that!
Nope, I had the same problem...and same thing applies for B138.
How can I remove this theme?
Thanks, I will try
Great!
Thanks for this theme. Looks great! I installed it on Stockwell's B160 ROM. Didn't have any issues with it so far, but I'll post back here when I do.
Howdy all!!
I'm currently running Franco Kernel r111 and the latest CM10.1 Nightly (20130327), and twice now I've woken up and my screen is black and won't turn on. The LED at the bottom is flashing a notification, but I can't wake the device. I have to hold the power button and then turn the device back on. The issue is, that I use this as my alarm clock, so it's made me late a few times now...
Is this the "SOD" that everyone is talking about? I think it's related to this most current nightly, as I've used r111 of Franco's Kernel along with the 23rd and 24th CM10.1 nightly and I didn't see the problem.
I guess my question is, is there something I can do to tell what is causing the crash? It's plugged into the charger, so could I run some app that will take a log that I can check the next morning if it should freeze?
Maybe you have undervolted too much, how much did you UV?. Try raising the voltage and see if that helps.
gee2012 said:
Maybe you have undervolted too much, how much did you UV?. Try raising the voltage and see if that helps.
Click to expand...
Click to collapse
I don't undervolt anymore on top of what Franco does by default.
jsylvia007 said:
I don't undervolt anymore on top of what Franco does by default.
Click to expand...
Click to collapse
Frano default is stock voltages, it is noy UV`d. Then maybe there is an installed app or widget that is going crazy and causes fc`s.
gee2012 said:
Frano default is stock voltages, it is noy UV`d. Then maybe there is an installed app or widget that is going crazy and causes fc`s.
Click to expand...
Click to collapse
That's why I was hoping someone knew of an app that might log things, so I can check after the reboot.
jsylvia007 said:
That's why I was hoping someone knew of an app that might log things, so I can check after the reboot.
Click to expand...
Click to collapse
Try BetterBatteryStatts, it shows activity`s of apps.
gee2012 said:
Try BetterBatteryStatts, it shows activity`s of apps.
Click to expand...
Click to collapse
I'm running that now actually, but I didn't think it's data persisted through a reboot.
Get a logcat via adb.
Sent from my Nexus 4 using xda premium
gravitysandwich said:
Get a logcat via adb.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So, I assume I would do these steps:
1. When I wake up and notice that the device is "frozen", hold the power button to turn it off.
2. Boot the device into fastboot mode
3. Use ADB to pull the logcat
4. Reboot the phone normally
Forgive me, but I haven't used ADB to get a logcat, and I believe that if I do it after a reboot into the full OS, won't the new boot overwrite the logcat from the frozen state?
jsylvia007 said:
Howdy all!!
Is this the "SOD" that everyone is talking about?
Click to expand...
Click to collapse
Sounds like the "SOD" issue many of us have. It's cause is currently unknown although turning WiFi off may prevent this from happening.
xda6969 said:
Sounds like the "SOD" issue many of us have. It's cause is currently unknown.
Click to expand...
Click to collapse
Ok, this is good to know... I've only JUST started to experience it in the most current CM10.1 nightlies... It happened to me once a while back with a CM10.1 nightly, but the update the next day fixed it, and never showed up again until recently.
same here!
Hey all! havin same issues here! ;( Dont know why is it happenin, and most important, why it only happens sometimes.... :silly:
I attached a logcat to molesarecomming and he told me it is some kind of driver mess up I've done a full wipe and going totally stock with no luck, IDK what to do....
PD: I hav a thread here so if you can just take a look!
jsylvia007 said:
So, I assume I would do these steps:
1. When I wake up and notice that the device is "frozen", hold the power button to turn it off.
2. Boot the device into fastboot mode
3. Use ADB to pull the logcat
4. Reboot the phone normally
Forgive me, but I haven't used ADB to get a logcat, and I believe that if I do it after a reboot into the full OS, won't the new boot overwrite the logcat from the frozen state?
Click to expand...
Click to collapse
what I did: when i noticed my phone its frozen I just connect it to pc and use adb to pull logcat, without reboot.
malavi said:
Hey all! havin same issues here! ;( Dont know why is it happenin, and most important, why it only happens sometimes.... :silly:
I attached a logcat to molesarecomming and he told me it is some kind of driver mess up I've done a full wipe and going totally stock with no luck, IDK what to do....
PD: I hav a thread here so if you can just take a look!
what I did: when i noticed my phone its frozen I just connect it to pc and use adb to pull logcat, without reboot.
Click to expand...
Click to collapse
Why don't you open a ticket with Google support and send them the logcat?
No when its frozen plug it in the computer and type adb logcat in the cmd window. A cmd window should pop up with your logcat.
Sent from my Nexus 4 using xda premium
gee2012 said:
Frano default is stock voltages, it is noy UV`d.
Click to expand...
Click to collapse
The 1026MHz slot is UV'd by default on Franco kernel. Though that won't have anything to do with the OP's problem.
Sent from my Nexus 4
Black screen in morning, flashers take warning
VoiD_Dweller said:
Black screen in morning, flashers take warning
Click to expand...
Click to collapse
This made me LOL so hard...
In other news its definitely some combination of CM nightlies & Franco kernel. I'm now on the newest nightly and r116, and it didn't happen this morning.
When it happens again I will try the adb logcat and see what I can figure out.
Ok... So! I am running Franco Kernel r117 & CM10.1 Nightly 20130403... I had the black screen again for the first time in a few days...
I plugged the phone into my computer, started the Nexus Toolkit, and followed the options to pull a logcat over to my computer. The problem is, the screen stayed at "Waiting for Phone" for almost 15 minutes, and then I had to leave for work...
Any help here?
Whenever I restart my phone the brightness automatically goes to 100% rather than sticking to whatever percentage I left it before restarting it. My screen timeout also goes back to 5 minutes (original) rather than whatever I have changed it to. Is this a bug in my phone or is this the standard feature for the G2? Sorry couldn't find anything in the search results. I am using the D802 variant.
100% Stock?
LenAsh said:
100% Stock?
Click to expand...
Click to collapse
Stock ROM, phone is rooted and no custom recovery installed. I am using Xposed Modules but even after disabling all of them the brightness went to 100% after rebooting. I just noticed, the brightness stays the same as before until I unlock the phone, then it automatically goes up to 100%.
All I would say is, Stock doesn't do this.
Since you don't have custom recovery, you cannot try a Cache wipe. You could try a factory reset though.
LenAsh said:
All I would say is, Stock doesn't do this.
Since you don't have custom recovery, you cannot try a Cache wipe. You could try a factory reset though.
Click to expand...
Click to collapse
Thank you. Also, I may as well get this question here since I've been meaning to ask it.
I have only used Nexus/Samsung devices before where the bootloader could be unlocked/locked easily, therefore I could quickly unroot and go back to stock recovery for OTA updates and such. I have read here that if I install a custom recovery I cannot use OTA updates. My question is how can I go back to unrooting and stock recovery? I have seen the stock firmware thread which I think would unroot the device but will it also make the recovery go back to stock?
You just flash one of the stock kdz files. See stickie in General
Sent from my LG-D802 using XDA Premium 4 mobile app
LenAsh said:
You just flash one of the stock kdz files. See stickie in General
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK that's a relief then, thanks for your help and I'll try a factory reset or using a stock kdz file.
Sometimes disabling the exposed modules alone isn't enough, have to use return option disabling exposed entirely. Flash file is in sd parent directory. Flash the zip. OTA isn't currently worth the troubles. Block em atm. Xposed (everything really) plays much nicer with SuperSU btw.
Insert Sim Card?
jayzfan1 said:
Whenever I restart my phone the brightness automatically goes to 100% rather than sticking to whatever percentage I left it before restarting it. My screen timeout also goes back to 5 minutes (original) rather than whatever I have changed it to. Is this a bug in my phone or is this the standard feature for the G2? Sorry couldn't find anything in the search results. I am using the D802 variant.
Click to expand...
Click to collapse
That's not what's supposed to be. Does it happen every reboot?
My G2 brightness jumped to max or fell to min brightness only for a couple of times within the first a few days after activation. I used AndroSensor and Lux auto brightness to find out its light sensor and inertia sensors were shut down when that happened (yes screen auto rotation went off, too). Maybe that's due to indoor/outdoor steep temperature changes. A power off and on solves that.
http://forum.xda-developers.com/showthread.php?t=2570189
Mine does it as well. It is not full brightness but the auto brightness that takes a long time to kick in.
Sent from my LG-D802 using Tapatalk
I searched on Google about this exact behavior and found this post.
I just got an LG G2 before yesterday from someone else who bought it in January (I checked warranty info) and it was fully stock and not rooted. I factory reset it 3 times and each time I reboot it still goes to 100% brightness even though I had it around 50%. At least it doesn't go to 100% while using it normally! phew lol. Then I'd be worried. But it's only after a reboot. That's a weird behavior. I had lots of phones and none did that.
I had the same problem only when the simcard wasn't inserted.
me too had same problem before, now it is disappeared, maybe virus problem
Xenovias said:
Insert Sim Card?
Click to expand...
Click to collapse
That was the reason on my situation. Thanks!
I recently rooted my note3 and installed xpose framework and other tweaks. i later realised that my power button cant lock and put my device into my lock screen.
the power button still works for everything else and i have a software button to bring it to the lock screen which i made using the "greenify app".
whats causing this and is there any fix? or any ways to put the device into safe mode ans see if this is caused by some faulty tweak? bug?
Summary:
"Power button works for everything except putting the phone to lockscreen/screen blackout"
Basic solution is to go to security and check "power button instantly locks" something like that.
Sent from my SM-N9005
not the fix
jdgamble said:
Basic solution is to go to security and check "power button instantly locks" something like that.
Sent from my SM-N9005
Click to expand...
Click to collapse
Thans for the reply.
i do know how to fix that..
but Thats not the issue. It doesnt even go to a black screen when i click the power button. just no response at all.
Rysekhon said:
Thans for the reply.
i do know how to fix that..
but Thats not the issue. It doesnt even go to a black screen when i click the power button. just no response at all.
Click to expand...
Click to collapse
List the modules you installed. It is possible that something is overriding the button function.
Sent from my SM-N9005
factory reset
jdgamble said:
List the modules you installed. It is possible that something is overriding the button function.
Sent from my SM-N9005
Click to expand...
Click to collapse
I removed all my modules and root permissions and used super user to remove my root.
Ive backed up all my data, removed my root access and im planning to do a factory reset. That should fix it right? Is it possible to soft brick my device this way?
Im fluent when it comes to jailbreaking but still a total noob with rooting.
rysekhon2 said:
I removed all my modules and root permissions and used super user to remove my root.
Ive backed up all my data, removed my root access and im planning to do a factory reset. That should fix it right? Is it possible to soft brick my device this way?
Im fluent when it comes to jailbreaking but still a total noob with rooting.
Click to expand...
Click to collapse
Factory reset will delete all data photos, music, vids, contact and messages etc. If you've backed up everything then you are good to go for factory reset and will welcome you back to fresh out of the box phone. And no soft brick can occur by doing this.
Sent from my SM-N9005
jdgamble said:
Factory reset will delete all data photos, music, vids, contact and messages etc. If you've backed up everything then you are good to go for factory reset and will welcome you back to fresh out of the box phone. And no soft brick can occur by doing this.
Sent from my SM-N9005
Click to expand...
Click to collapse
Did a factory reset but the problem is still here. Can't put my screen to sleep with the power button. This is really bugging me. Don't see any posts related to this online
---------- Post added at 05:57 AM ---------- Previous post was at 05:47 AM ----------
rysekhon2 said:
Did a factory reset but the problem is still here. Can't put my screen to sleep with the power button. This is really bugging me. Don't see any posts related to this online
Click to expand...
Click to collapse
my phone can't time out. Think the app greenify must of messed up my phone somehow.
Have you tried a battery pull after FR?
Sent from my SM-N9005
jdgamble said:
Have you tried a battery pull after FR?
Sent from my SM-N9005
Click to expand...
Click to collapse
Battery pull as in remove and put the battery back in? Yes but not in any special way?
Hmmmm...this is odd. Can't seem to figure out anything that would mess up power button in such a manner.
You're on stock rom right? Nothing fancy done to your phone.
Sent from my SM-N9005
jdgamble said:
Hmmmm...this is odd. Can't seem to figure out anything that would mess up power button in such a manner.
You're on stock rom right? Nothing fancy done to your phone.
Sent from my SM-N9005
Click to expand...
Click to collapse
yea im on a stock rom. googled " note3 wont time out" and some people are having the same problem. havent found a fix yet tho. right now just leaving my note3 with battery out.
will try start in safe mode and see fi i can put it to time out
Rysekhon said:
yea im on a stock rom. googled " note3 wont time out" and some people are having the same problem. havent found a fix yet tho. right now just leaving my note3 with battery out.
will try start in safe mode and see fi i can put it to time out
Click to expand...
Click to collapse
safemode didnt work as well. any way to totally fix it?
flash in a brand new rom? like start from totally clean note3
Rysekhon said:
safemode didnt work as well. any way to totally fix it?
flash in a brand new rom? like start from totally clean note3
Click to expand...
Click to collapse
i was playing with boot animations last night. that could of caused it? http://forum.xda-developers.com/showthread.php?t=2486469
Very interesting...
I discovered that if I renamed the boot animation qmg file under \system\media , the screen won't turn off. Once I restored the file, all is well.
Why is this?
how to i reset all this without doing it manualluy?
I'm assuming it's coded as most hardware functions are. Anyway applause for finding the solution on your own, well done.
ddogishere said:
I'm assuming it's coded as most hardware functions are. Anyway applause for finding the solution on your own, well done.
Click to expand...
Click to collapse
i havent found a solution :/.
will try reinstall from a stock rom. first time doing this tho. any tips? or webistes where i can get roms? im scared i might install and download the wrong rom.
Hi guys.
I'm really stuck here. My fingerprint sensor suddenly started showing me 'no match' when I try to scan it, but I can unlock my screen with the emergency password.
However, if I try to access private mode, neither my fingerprint nor my backup password works.
Can anyone shed some light on this matter?
Thanks.
EDIT: My phone is an SM-910F.
s18067 said:
Hi guys.
I'm really stuck here. My fingerprint sensor suddenly started showing me 'no match' when I try to scan it, but I can unlock my screen with the emergency password.
However, if I try to access private mode, neither my fingerprint nor my backup password works.
Can anyone shed some light on this matter?
Thanks.
EDIT: My phone is an SM-910F.
Click to expand...
Click to collapse
Try deleting your fingerprints and adding them again, or maybe restarting the phone would help.
Ashatar said:
Try deleting your fingerprints and adding them again, or maybe restarting the phone would help.
Click to expand...
Click to collapse
I can't even access my fingerprint manager. And I've restarted a few times to no avail.
It also seems that the only place my emergency password works is the lock screen. I can't even change my lock type.
s18067 said:
I can't even access my fingerprint manager. And I've restarted a few times to no avail.
It also seems that the only place my emergency password works is the lock screen. I can't even change my lock type.
Click to expand...
Click to collapse
Are you rooted with custom ROM?
Ashatar said:
Are you rooted with custom ROM?
Click to expand...
Click to collapse
Yes, I'm on a custom ROM. I've been on a custom for months now and it's been fine, though..
Check if runtime is Dalvik.my private mode isn't working on art,completely stock no root
Sent from my SM-N910G using XDA Premium 4 mobile app
RISHI RAJ said:
Check if runtime is Dalvik.my private mode isn't working on art,completely stock no root
Sent from my SM-N910G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't even find the option to switch runtimes in my dev options. I'm running a Lollipop custom ROM.
Bump
s18067 said:
Bump
Click to expand...
Click to collapse
Maybe you should try wiping data and starting all over again, but I'd recommend installing an official ROM from Samsung....
Ashatar said:
Maybe you should try wiping data and starting all over again, but I'd recommend installing an official ROM from Samsung....
Click to expand...
Click to collapse
I was hoping it wouldn't come to that... Oh well...
s18067 said:
I was hoping it wouldn't come to that... Oh well...
Click to expand...
Click to collapse
It's a bummer.Good luck.
having same problem on N910T, wondering what finally fixed it.