Hi guys, I have a very irritating issue with my international Galaxy S6 Edge (SM-G925F) and hopefully someone could help me fixing it.
I'm experiencing frequent lockups mostly when trying to wake up/unlock the phone. The device becomes totally unresponsive to screen or home, back, window button taps and eventually after lots of tries it comes back to life and behaves as normal. The problem becomes way less frequent (almost disappears) if I connect it to a charger.
What I tried up to now with no luck fixing the problem is:
Disabled all the TouchWiz smart features, location services, wifi and radio broadcasts, rotation, nfc, sound, bluetooth, fingerprint scanner,
Checked all the sensors from the *#0*# menu and they seem fine,
Flashed through Odin, Smart Switch, TWRP official and custom roms (5.1.1, 6.0.1),
Tried rooted and non-rooted roms,
Tried odin's NAND erase all option and repartioned the phone using the ZEROLTE_EUR_OPEN.pit file,
Wiped the persistent partitions (sda11, 13) using the ADB commands dd if=/dev/zero of=/dev/block/sda11, dd if=/dev/zero of=/dev/block/sda13, which however gave me:
dd: /dev/block/sda11 (sda13): No space left on device,
so I don't know if it was successful or not,
Updated (PASS) the TSP FW version from the *#2663# menu,
Opened the phone and powered it up after disconnecting all components apart from screen and battery,
Tried different battery.
Does anyone have a similar problem and knows how to fix it? Unfortunately, my device is out of warranty so I wouldn't like to visit a Samsung service centre.
I haven't tried alternative PIT files with hidden partitions of various sizes yet. Do you think that it will make any difference or, furthermore, is there a chance of further damaging my phone?
Could someone please with a similar device dial the *#2663# code and give me the following information? Phone's and part's TSP FW version, TSP threshold.
Is there a Phone's and Part's Touch key FW version available? In my phone I cannot see the Phone's, Part's Touch key FW version paragraph at all and I'm curious if this is related to the problem.
Looking forward for your tips! Thanks!
Hi UlmGS6, i have the same problem... my G925F XSG reboot random.
I try many things but without sucess.
Nelson_s said:
Hi UlmGS6, i have the same problem... my G925F XSG reboot random.
I try many things but without sucess.
Click to expand...
Click to collapse
Hi mate, sorry to hear that.
Since it appears in both the flat and the edge version of the Galaxy s6, there is a similar thread in the flat galaxy s6 forum.
http://forum.xda-developers.com/galaxy-s6/help/lockups-app-crashes-phone-freezes-t3346837
Keep an eye there too for future updates, because it seems more active.
Related
Hi to all,
I have a strange problem with my p500.
Sometimes when the phone is in standby mode, the screen freezes and the touch screen does not work. after a few seconds (after pressing any key) the phone reboots itself and everything returns to normal
Does anyone have a similar problem?
What can i do for fix it?
Thanks
You may be facing the random sd card unmount issue (which sometimes results in rebooting of the phone).
LG has released a new firmware which addresses this issue (it worked for me ). Use the LG suite to update the firmware...
If you are the adventurous type then refer here http://forum.xda-developers.com/showthread.php?t=876447
Thanks for the answer,
I tried to update the firmware, but LG suite say that is already updated (v10a) .
My carrier is vodafone. It may be that different operators will have different versions of firmware? (I'm newbie here)
Hey,
My phone continuously has a problem in which the W on the keyboard does not work. It presses the letters either side. Paired with this, now and then the screen appears to think i'm touching it, when I am not - the menus change, applications open, and the bottom buttons freeze - the screen becomes completely unresponsive.
Is there a solution to fixing this? I've tried switching roms and kernals?
noj123 said:
Hey,
My phone continuously has a problem in which the W on the keyboard does not work. It presses the letters either side. Paired with this, now and then the screen appears to think i'm touching it, when I am not - the menus change, applications open, and the bottom buttons freeze - the screen becomes completely unresponsive.
Is there a solution to fixing this? I've tried switching roms and kernals?
Click to expand...
Click to collapse
Tbh, I have no idea what to say. Do one thing, try flashing official firmware through odin and check if this error persists. If it doesn't then root the phone again and go to your favourite ROM. If it does, It could be a hardware problem of some sort. Best of luck
You can try Siyah kernel, I think it has some fixes for the touchscreen.
Sent from my Galaxy S2 GT i9100
boki9999 said:
You can try Siyah kernel, I think it has some fixes for the touchscreen.
Sent from my Galaxy S2 GT i9100
Click to expand...
Click to collapse
I have tried that kernal and the problem did continue. I haven't however flashed an official stock ROM since my first custom ROM. The problem is quite random which makes it impossible to replicate, I can just be using my phone for a few seconds and it will freeze up, then not do it for a week and it'll come back.
I am going to put on
"Official Stock ICS Firmwares
I9100XWLPT Download (Thanks To SamMobile!)
Base Firmware: I9100XWLPT (4.0.4)
Region: Europe"
And see if it'll sort out the issue. Currently my phone is essentially unusable due to the error - doesn't help I need this phone for tomorrow when I go on holiday.
Hi, I'm having a curious problem with my S3 and I've been unable to solve it. I watched the "noob" video and tried searching these forums as well as a google search with various combinations of the wording for my problem. Nothing matching my issue turned up, I hope I didn't miss anything.
I recently bought a S3 second hand (yes, i know, i should have known better). It was rooted and running some kind of custom ROM when I first turned it on, but I was willing to deal with it until I double checked the procedure for getting it back to stock and starting again myself (nothing against the original rooting and flashing, just like to know exactly what I'm running).
When I purchased the phone I obviously checked that all of the main things worked - calling, texts, mobile data, wi-fi etc. I get home and connect to my home wi-fi and start checking things out and setting stuff up. The phone randomly rebooted. I carry on after the reboot and about 10 mins later, another restart.
To cut a long story short, there is something wrong with the wi-fi. If I turn off wi-fi in the settings menu and reboot, everything works great. No crashes, no reboots. If however I enable the wi-fi about 50% of the time it will crash while wi-fi is activating. The other 50% of the time, it will crash as it goes into the screen lock (either via timeout or pressing the button).
I've re-flashed to it's stock version of Android (using the 'Samsung GS3 Toolkit and Odin), same problem. Anyone got any ideas?
Thanks in advance
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
boomboomer said:
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
Click to expand...
Click to collapse
After much experimentation and flashing of various files to my phone I have further narrowed the problem. I've still not solved it, but getting closer I feel.
After a clean ROM flash it works like a charm regardless of how much i use the wifi etc. It's only after the first reboot that the trouble starts. It will begin randomly restarting. If I perform a factory reset from recovery mode, it works again, but starts resetting again after a reboot.
Any ideas?
I hope someone has some experience of this problem, I will do my best to explain in some detail.
It is as out of the box currently running version 4.0.4 firmware.
The history, initially stock firmware version 4.0.3 was running, the USB was a little loose, so I swapped the complete pcb with another S2 I have with a faulty display, to make things a bit more complicated I also put in a 2Gb SD card, when I rebooted the problem appeared, on pressing the power button to wake up, the screen comes on to the lock screen in dimmed mode, and it will stay like it for anything from 5 to 15 seconds, then the screen will go to full brilliance and the screen can be unlocked.
What I have tried, removed and rebooted with sd card removed, swapped back the original USB pcb, and swapped back again as the problem remained, also upgraded to firmware version 4.0.4, that is more or less where I am now, the problem remains.
Have tried researching but unable to find anything relating to this problem, do you have any ideas?
Update:
After further reading, it appears the original firmware may have been customised, because I was not able to get Kies to connect with the device and the CSC was stated as 'unknown', which from what I have read indicates a custom ROM.
Having flashed the stock firmware , on the recovery menu I get still the message #Manual Mode# Appling Multi CSC.... Applied the CSC code: XEU Successfully applied multi CSC, which was also present with original firmware but it never actually applied the code as it stated CSC 'unknown'. but I can now connect with Kies and the CSC code is stated as I9100XEULPA.
Is it normal to get this message at the recovery menu?
Is it a symptom of the same lock screen delay issue?
Solved
I spent 6 weeks trying to fix this, the most aggravating of problems are sometimes very easy to cure when you know the answer!
Disable auto brightness, easy, your long wake up delay has now gone.
Let me know if it helped you.:good:
Galaxy S III 19300 has developed a problem where every time i try to use the phone i.e press power button and then swipe, the screen sleeps, Sometimes it sleeps after 10 seconds sometimes before i even swipe. Factory reset done, have now rooted it, but need to ascertain if it is a hardware failure or bug. I managed to set time out for the longest setting and obviously usb debug mode but wonder if its a power issue or gpu or driver issue etc.... please can anyone help?
Hopefully you're still on a stock rom.. Theres a ussd code to bring up a test app. You'll be able to test the proxy sensor etc from there.
If everything seems OK or if you have a custom rom then you'll have to download the firmware and odin on a pc and flash the phone back to stock. You'll need to flash the firmware, factory reset and flash again. That way you know there isn't any remnants left over from the last time it was used/flashed/rooted. This is the only way to find out if it's a hardware or software issue without all the faff.
Beyond not having the phone in my hand that is the only advice worth giving. If you keep chasing shadows you won't find the problem. Best to nip it in the bud.
ussd code
shivadow said:
Hopefully you're still on a stock rom.. Theres a ussd code to bring up a test app. You'll be able to test the proxy sensor etc from there.
If everything seems OK or if you have a custom rom then you'll have to download the firmware and odin on a pc and flash the phone back to stock. You'll need to flash the firmware, factory reset and flash again. That way you know there isn't any remnants left over from the last time it was used/flashed/rooted. This is the only way to find out if it's a hardware or software issue without all the faff.
Beyond not having the phone in my hand that is the only advice worth giving. If you keep chasing shadows you won't find the problem. Best to nip it in the bud.
Click to expand...
Click to collapse
Hi, thanks for your response. Yes i'm still on still on the stock rom and do not believe it was ever flashed/rooted. I will take your advice and try your suggestion. Where would i find the USSD code for the test app?
Dial *#0*# for the diagnostic screen.