Sleep of Death befalls my SGN 12.2 - Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting

Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?

To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.

ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).

Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.

Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.

Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?

Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.

Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.

Related

HELP: Phone locks up and dies at random

I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.

Kogan Agora Tablet (TCC8803 based)

This is a continuation of the generic TCC8803 thread at http://forum.xda-developers.com/showthread.php?t=1119778
IMPORTANT - THERE IS A SYSTEM APP CALLED FWTOOL. DO NOT USE IT TO FLASH FIRMWARE OR YOU MAY END UP BRICKING YOUR TOUCHSCREEN. ALSO DO NOT FLASH ANY VERSION OF lk.rom OR YOU WILL BRICK YOUR TABLET.
To install clockworkmod
Download EM73-8K-recovery-signed.zip below. Rename it to update.zip and copy it to the root of your SD card.
With your tablet already turned off, press and hold down the Back button and then press the power on button while still holding down the Back button. This will open stock Recovery.
Use the buttons on the top of your tablet to navigate your way through recovery and to select menu items (menu = down, back = returns to previous menu, home = selects option).
Navigate to apply update.zip & follow the instructions. Reboot.
To use clockworkmod just press and hold down the Back button while powering up your tablet. Navigate the menu via the buttons (menu = down, back = returns to previous menu, home = selects option).
To make a Nandroid (clockworkmod) backup boot into clockworkmod recovery & navigate down to Backup then follow the instructions.
To root your tablet ** please see comment at end of post before continuing past this point
+++Make a full Nandroid (clockworkmod) backup before attempting this+++
Download & unzip Superoneclick from http://forum.xda-developers.com/showthread.php?t=803682 - NB you may need to turn off any antivirus program on your PC to allow downloading & use of Superoneclick.
Download & unzip the relevant Drivers folder (32 or 64 bit) from link below then connect your (powered on) tablet to your PC & point Device Manager to your unzipped drivers folder when it is looking for drivers.
Make sure USB debugging is allowed on your tablet (Settings -> Development -> USB debugging)
Right-click on Superoneclick.exe, select Run as administrator then click on the Root button. It will take 2 or 3 minutes for your device to be rooted.
This procedure has worked for my own tablet but I accept no responsibility if you end up bricking your device!
Another way to root your tablet is at http://forum.xda-developers.com/showthread.php?t=1119778
To stop battery drain & prevent screen from waking every few minutes - **only for original Kogan ROM**
(with thanks to hallokitty for this fix)
This happens because the tablet keeps looking for the 3G signal it cannot ever receive. To fix this, go to System/app using Root Explorer from the Market, delete (or rename) phone.apk and TelephonyProvider.apk. You will immediately start getting errors but just use the reset button at the back of the tablet and when you reboot the problem has been solved. If you ever want to restore these apk's (e.g. if you want to use a 3G modem) just flash the phone+telephony zip file below using clockwork mod.
Clockworkmod rescue backups
I've done a factory reset & wipe of my tablet & made clockworkmod backups which I've linked to below. Make sure you do a full Nandroid backup before applying any of these. Unzip the file & place it in the appropriate Nandroid folder on your SD card (/clockworkmod/backup/), don't try to flash the zip file using CWM! These are a slightly slimmed down versions of the ROMs - for the Kogan ROM I've removed phone.apk, telephony.apk, Email, Facebook, Twitter, FW tool (dangerous to have), ES Explorer, Live Wallpapers and ES task manager. I've upgraded Spare Parts to Spare Parts + and added Astro File Manager as a user app. I had removed most of these things from my ROM before I was ever asked to make this backup so if you want to reinstall them you can get them from the Market or flash the relevant apk's into the system/app folder using CWM. The ROM is still rooted. You will need to do a factory reset & wipe the Data partition & Dalvik cache with CWM prior to doing this. If you want to use a 3G modem you will need to flash the "phone + telephony.zip" file listed below with clockworkmod.
Kogan firmware clockworkmod rescue backup: http://www.mediafire.com/?izfedrz97iowi34
**If you're really lazy you can combine rooting the tablet, removing unnecessary system apps & applying the screen wake fix by installing clockworkmod then restoring the rescue backup (NB make sure you make your own Nandroid backup first!!!).
CM7 runs extremely well on the Kogan except for HDMI out & Camera which don't work yet. You will also need to install Gmail & Youtube apps from the Market if you want them. Make sure you do a full CWM/Nandroid backup before trying this as I had problems with an unresponsive touchscreen after flashing the most recent CM7 ROM. For more info head here.
Tips & Tricks
MoboPlayer is a good video player, particularly for its ability to let you change the volume & screen brightness by swiping up & down directly on the video you are watching. The volume softkeys on the Kogan are not visible if any app is in fullscreen mode.
Titanium Backup may not show all installed apps or any system apps. To fix this go to Titanium Backup's Preferences and tick "Force use system Busybox" and "Force use system SQlite".
OK mine has arrived lets see what we can do
flipside101 said:
OK mine has arrived lets see what we can do
Click to expand...
Click to collapse
Lucky you - they're really dragging their heels with mine. Can you upload the kernel & we can see about getting clockworkmod for it?
How do you rate it as a tablet? Is the keyboard OK? - some people have said it's a bit carp.
I got mine today. It's going back as soon as I can get Kogan to respond.
Turns itself on & off at random, poor quality screen, sound, responsiveness.
Touchscreen activates itself without being touched.
What was I thinking? I guess you get what you pay for.
Now if only I could get them to reply to an email.......
Ok i have to agree you get what you pay for so i had low exectations. Its no flyer,tab,transformer but then it was a 1/4 of the cost. Yes the screen has issues (partly i think due to the screen protecter and battery life is poor though ive had this on for about 2 hrs now and its about 2/3rds down.
All in all im happy though going to live with it for a bit and i reserve the right to change my mind.
Wil right more when i have aproper keyboard
yeh i get the same problem with the screen comming on and off randomly.. i wish i could stop that =P (would save the 3 hour battery life i have to 4 hours!)
you get what you pay for =P but i thought the screen was quite good considering.
did you try the recovery yet?
how nice would it be to port oxygen to the kogan haha
wlee2 said:
yeh i get the same problem with the screen comming on and off randomly.. i wish i could stop that =P (would save the 3 hour battery life i have to 4 hours!)
you get what you pay for =P but i thought the screen was quite good considering.
did you try the recovery yet?
how nice would it be to port oxygen to the kogan haha
Click to expand...
Click to collapse
The screen keeps coming on as the OS is looking for a 3G signal all the time. If you switch it to airplane mode it should stop happening. Or use http://www.appbrain.com/app/airplane-mode-wi-fi-tool/net.geekherd.airplanemode . Or you could even try adjusting the settings to use 2G only.
I can't adjust to 2g only on mine - it's greyed out.
Yes, I've put it back to factory setting a few times, but it's no better.
The switching on/off isn't the main problem (though it has used 30% of the batter life in 8 hours during the night).
The main issue is the touchscreen simply activating itself. If i go into a menu of any kind, it sometimes selects something for me. It happens too often to just ignore it.
Sounds like a faulty screen :-( - let us know how you get on returning it! If mine turns out to be rubbish when it arrives my Plan B is this one http://mp4nation.net/catalog/index.php?main_page=product_info&cPath=68&products_id=496
well im having the random on issues (thanks for the airplane mode idea ill give it a tray) but the screen activations are not a problem.
@dwl99 that mp4nation link is the same as the kogan (a rebranded em73) so its likely to have the same niggles i think
flipside101 said:
well im having the random on issues (thanks for the airplane mode idea ill give it a tray) but the screen activations are not a problem.
@dwl99 that mp4nation link is the same as the kogan (a rebranded em73) so its likely to have the same niggles i think
Click to expand...
Click to collapse
A lot of these tablets are very similar (Herotab C8, Dropad A8) but there seem to be some important differences in the components used. I've been lurking in some Heropad C8 forums and nobody seems to have reported touchscreen problems.
This one look exactl;y the same , button layout etc etc however i know what you saying as even within the same model different components can be swapped in as costs change between runs
BTW
Kernel
2.6.35.7
Build
EM73_SIS_GC2M_V2 20110516
WILL UPLOAD WHEN I GET A CHANCE TO DUMP IT
An app that sticks it in Airplane Mode when you put it into sleep mode is a good work around for now, try "Auto Airplane Mode" (I can't link because I haven't posted enough, it seems...
Hasn't randomly turned on since I installed this. Ahh, forget that, it seems to be doing it again, it just took a lot longer...
In general, this thing is a bit cheap and nasty, but I guess that's what I expected. The button placement is seriously weird, and the touchscreen and accelerometer are just inaccurate and jittery (try playing a game that uses the accelerometer! good luck!)
I feel like it could benefit a lot from a nice ROM though, to fix a few issues (where the hell is the accounts & sync menu?)
hallokitty said:
I feel like it could benefit a lot from a nice ROM though, to fix a few issues (where the hell is the accounts & sync menu?)
Click to expand...
Click to collapse
Been trying to find how to set these before
i found it once earlier on but i cant find it again!!!
it was not where i expected and i think i had to do a round about method to find it.
i have a feeling it had something to do when i was trying to sync email contact with a email app but i forgot which one lol..
dwl99 said:
The screen keeps coming on as the OS is looking for a 3G signal all the time. If you switch it to airplane mode it should stop happening. Or use http://www.appbrain.com/app/airplane-mode-wi-fi-tool/net.geekherd.airplanemode . Or you could even try adjusting the settings to use 2G only.
Click to expand...
Click to collapse
just FYI on the kogans you can activate aeroplane mode in settings then using the power controls widget on your home screen turn on wifi
it will keep the aeroplane mode on but wifi on as well atleast it worked on mine you dont need an app for it.
i actually wonder if the screen wake has something to do with background sync should try turn it off for a night and see.
Okay, so after being plugged in and fully charged, I unplugged it and left to drain overnight to see what would happen.
I had "Auto Airplane Mode" on, but as you'll understand, it helped, but not enough.
Even in Airplane Mode, the tablet would wake itself up, then "Auto Airplane Mode" would see the screen is on, and turn the wifi back on, then back off when the screen faded.
But, I'm thinking this might be because it has Sync enabled. I'm going to try it again with sync disabled.
The battery graph was a joke - it started smoothly going down at a reasonable pace, then -no lie- it spiked down.. then UP, then down, then up, throughout the night. It was at about 75% when I turned it back on after say, 8 hours. Then it dropped to 72%, then I plugged it in, and it immediately reported 98%. The biggest drain by a long way is "Mobile Standby".
However, for the most part, bar the bad accelerometer, terrible button placement, and slightly sharp edges, the hardware itself is not terrible for the money - 512MB RAM and 1GHz processor; I don't mind 800x480 at 7", it looks passable, although it's bad in sunlight. (Of course the viewing angles are bad, but for the cost, that's expected/OK).
But damn the software needs tweaking because it just has problems.
vv
Model number: EM73_SIS_GC2M_V2
Kernel Version: 2.6.35.7
Build number: EM73_SIS_GC2M_V2 20110516
Hi all since installing auto airplane I don't think im seeing wakes issues. I left the kogan overnight at about 50% battery and this morning it was at 35%. Ill test again tonight just to be sure as you seem to have the same build and kernel .
EDIT:
Ok i do still have it
Sent from my HTC Desire using XDA App
Though I have to agree the roms a joke accourding to quick system info 77% of my power useage has been down to mobile standby HUH.
Edit one thought is the 3g component in there for the 3g USB comparability and if so that was a new feature so could there be a rom that exists without it. I have added a topic in this forum asking if its possible to strip the 3g component out.
Sent from my HTC Desire using XDA App
Huh, no, it still seems to turn the screen on now and then even with sync off and in airplane mode. This thing needs a custom ROM as soon as possible. I imagine after a while people will start to sell them cheap because of problems that could mostly be fixed with better software, so I think it could be a pretty popular tablet for people willing to customise it..

[Q] Black screen

Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan
thebguard said:
Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan
Click to expand...
Click to collapse
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!
REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.
orange808 said:
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.
Click to expand...
Click to collapse
my Carbon rom is built differently than fattoad, cm, or omni...doesnt have lbcoders mpdecision touchboost amongst many other differences in its kernel
---------- Post added at 11:23 PM ---------- Previous post was at 11:16 PM ----------
thebguard said:
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!
Click to expand...
Click to collapse
if its at 192mhz go to 384mhz....if at 384mhz try 192mhz...if either dont work bump it up to the next highest mhz
I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.
thebguard said:
I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.
Click to expand...
Click to collapse
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?
REV3NT3CH said:
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?
Click to expand...
Click to collapse
The lowest option I had was 384mhz.
Flashing via CWM recovery: wiping data/system/cache/dalvik. Then CarbonRom and gapps. So clean wipe I think is what you are referring.
Sent you a zip to try via pm. Just let me know if it works.
Sent from my LG-VS980 using Tapatalk 4
Does this issue manifest itself when you have the phone plugged in? Can you get a logcat of the issue? Throwing things at the wall and seeing what sticks may not be the best resolution here. There are ways of finding out the underlying cause.
mpdecision is not the cause here (That only affects the secondary core) nor is min frequency (You can override it in the HypnoToad images too, just set another governor (like say 'conservative). In FatToad it may look like it resets because Cyanogenmod doesn't display the second core in the performance settings, but changing it is sufficient for testing. The official CM 11 builds do not have the touch boost (which only affects things after the phone is awake, and merely sets the secondary core's frequency up to 1184 Mhz when you are touching the screen, but the affect on the percieved performance of the phone due to this is immense)
Deep sleep is likely closer to the main cause because that affects both cores, and if the system isn't receiving the proper signals to wake back up, this can happen. Throughout development on apexqtmo, we've run into similar problems, and it's always helped by getting proper documentation from those who are experiencing the issues.
TL;DR: Trying random things likely won't solve this issue. Getting all the information you can will help.
Thanks again for all the help. I don't usually ask for any but I could not find much on my issue (or maybe I wasn't searching correctly).
I think I did the logcat correctly. See attached.
The thing that popped was:
D/SurfaceControl( 791): Excessive delay in unblankDisplay() while turning screen on: 269ms
Click to expand...
Click to collapse
When I would hit the power button and screen would not turn on, this would be there. I'm not really good with understanding this stuff. Hopefully this leads us in right direction though!
Edit: sorry forgot to answer your first question Magamo. This issue happens no matter if it's plugged in or not.
Edit 2: I watched the logcat from adb for awhile and I guess the above happens no matter what. I don't see any differences between if the screen turns on or not.
It looks like you have a hardware rev we're not supporting in our current kernel (which is why it works on stock). PM me if you want to mail your phone to me for analysis
This happened to a new device i purchased. After lbcoder and nard trailed through my logs, I was prescribed to resell the device. Your symptoms sounds identical to what I was experiencing. JB stock kernal works. But custom roms which since delved into the new edited kernel doesnt work on such devices. Since re-sold the device. Be interested to know if yours gets fixed where mine didn't. Good luck
Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!
sorgo said:
Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!
Click to expand...
Click to collapse
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?
REV3NT3CH said:
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?
Click to expand...
Click to collapse
Thanks for the reply. Yes the bootanimation and initial logo is telling enough about the cause of it. I must admit it's a hw problem. I tried to open/close the keyboard quicky instead of moving it slowly, but it occurs too. I'll try completely different rom with different kernel as the last chance
to hope for a sw issue.
I tried Omnirom with same result, but now I did a clean flash of the latest liquid and my impression is that this happens a lot fewer times than before. Maybe I just got the right velocity and force needed to open it gently I also installed just a few critical apps. Before I messed with Ultimate screen rotate etc.
But it now happens more when closing the keyboard. However, I'll rather buy new one, just ot have a backup of this great phone just in case.
http://www.cellulardr.com/samsung-t699-slide-flex/
Is this "the part" I need?
Do you have any experiences with this shop? It seems to me too much $40+shipping for that cable. Probably I'll just order another one from ebay, preferably new one and leave the current one for spare parts in the future.
Fixed today! You can see the state of the flex cable on the last picture in this post:
http://forum.xda-developers.com/showpost.php?p=56642402&postcount=35

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

My SONY Miro is stuck at Xperia Logo

I have a Sony Miro mobile,
It was working just fine, until one day I threw it gently on the bed
( I'm guessing when I threw it; the battery was shortly disconnected and returned to its position )
and now when I power it on I get Xperia Logo, and it's stuck on it
I tried removing the battery, and putting it back. with no use
I also tried using Volume Up/Down while pressing Power on. also with no use.
The battery bar shows it's being charged when I plug it to power source.
So I don't think there's any battery malfunction.
I'm guessing it's perhaps corruption of the Android OS /or/ bootloader
I'm a newbie in mobile troubleshooting,
is there an easy way to solve my problem
Please guys... your help is really appreciated
Note. Sorry if I posted my thread in an incorrect location, I'm new to your forums
aroma_kt said:
The battery bar shows it's being charged when I plug it to power source.
So I don't think there's any battery malfunction.
I'm guessing it's perhaps corruption of the Android OS /or/ bootloader
Click to expand...
Click to collapse
The issue that Android gets stuck on startup screen could be caused by many reasons:
- You download and install some applications from unknown source. These applications might be malware or be incompatible with your Android version.
- Bugs, glitches and viruses may take control of the Android system.
- The running system might be corrupted or scrambled due to an interrupted or improper update process.
- You flash a custom ROM, kernels or stock firmware
- It is possible that the problem is caused by the hardware problem.
Additionally sometimes your casual clicks or downloads may result in this issue.
My recommendation: Re-flash phone's Stock ROM.
jwoegerbauer said:
The issue that Android gets stuck on startup screen could be caused by many reasons:
- You download and install some applications from unknown source. These applications might be malware or be incompatible with your Android version.
- Bugs, glitches and viruses may take control of the Android system.
- The running system might be corrupted or scrambled due to an interrupted or improper update process.
- You flash a custom ROM, kernels or stock firmware
- It is possible that the problem is caused by the hardware problem.
Additionally sometimes your casual clicks or downloads may result in this issue.
My recommendation: Re-flash phone's Stock ROM.
Click to expand...
Click to collapse
Actually I haven't been using it for months, since it's my backup phone.
When I threw it gently on the bed; I was just checking out the battery level.
This definitely rules out the first four reasons, (for the fifth one I'm not quite sure)
This is mainly why I am leaning towards the interrupted power (battery was most likely disconnected for a split second )
Could you kindly point me to how I can re-flash it.
Can a newbie at mobile-troubleshooting do it; or is it not a straight-forward procedure?
(I mean if for some reason something went wrong, can it lead to the phone being bricked)
Thank you for your reply dear

Categories

Resources