Develop Bugs

Would a Nandroid help me here?

Recently, my Play has been having some touchscreen issues. It will work perfectly for almost a day and then proceed to lock up. Screen still turns on with the power button and sliding the gamepad out unlocks the phone but the touchscreen becomes unusable.
Also I've noticed that some kernels are not booting either. Kernels that have worked for me in the past. Even some of the ftf firmware files wont work. The only one I can get working is 2.3.2 and UK generic 2.3.4 (4.0.2.A.42). The UK one then prompts me to upgrade to 4.0.2.A.42, which its already running :S
PC Companion says theres a problem updating my phone regardless of what firmware Im running as well and SEUS just closes on me after I click the Xperia Play.
Originally, I thought that this was a damaged digitiser. Now, seeing as Im having all these issues, Im starting to doubt that.
Would a Nandroid of another ROM (one that uses stock kernel i.e 2.3.2 or 2.3.4 from the ftf files I have) be able to correct the dodgy system issues Im having?
Or is my Play dead now?
Any help would be great

Anyone?

I think it would do the trick. As full restore givs ur phone the exact state of ur phone before it was faulty. Same as a pc recovery. Hope that help.

sdojoin said:
I think it would do the trick. As full restore givs ur phone the exact state of ur phone before it was faulty. Same as a pc recovery. Hope that help.
Click to expand...
Click to collapse
Just need to find a Nandroid now to try it out

CTU_Loscombe said:
Just need to find a Nandroid now to try it out
Click to expand...
Click to collapse
I also had this issue, but mine got progressively worse and the screen stopped responding altogether, and had to take it in and get a new one from Verizon due to hardware failure.
I would suggest doing a full backup (if you haven't already) and flashing your firmware and doing a factory reset...if your still having screen issues then its the phone.

ricenlives said:
I also had this issue, but mine got progressively worse and the screen stopped responding altogether, and had to take it in and get a new one from Verizon due to hardware failure.
I would suggest doing a full backup (if you haven't already) and flashing your firmware and doing a factory reset...if your still having screen issues then its the phone.
Click to expand...
Click to collapse
Yeah its the phone. Sold it for parts. Moving to HTC
Long story short, Ive had nothing but issues with SE devices. My brothers Play came with a dodgy power button and volume down rocker. My X10Mini touchscreen and system failed 2 months after getting it. Now my Play has died
Sticking around the Play forums to help people though

Constant Reboots!! PLEASE HELP!!!!

Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!

i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does

First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before

have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay

Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.

XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion

Needs a trip to the Service Centre then by the sounds of it.

XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?

Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium

tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?

plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium

i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always

plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.

lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes

[Q] Unusual issues with camera!

I actually this time have no idea what happened to this phone, but after reinstalling the OS the phone's camera began to work... Up until a day later it stopped working again. So i moved on from CM10.1 to Blackout ICS, which went well I suppose, up until two days later it died again, it just goes to a black screen when launching the camera app, if i have music playing that will stop, and the phone will be unable to play music for a minute or so, im touching on reformatting the SD Card, but before i do that i want to know if theres any ways to get the camera going again, and if theres any hardware faults (which is unlikely because when it works it works perfectly)

humzaahmed155 said:
I actually this time have no idea what happened to this phone, but after reinstalling the OS the phone's camera began to work... Up until a day later it stopped working again. So i moved on from CM10.1 to Blackout ICS, which went well I suppose, up until two days later it died again, it just goes to a black screen when launching the camera app, if i have music playing that will stop, and the phone will be unable to play music for a minute or so, im touching on reformatting the SD Card, but before i do that i want to know if theres any ways to get the camera going again, and if theres any hardware faults (which is unlikely because when it works it works perfectly)
Click to expand...
Click to collapse
Have you tried wiping the cache and dalvic in recovery?

tonylee000 said:
Have you tried wiping the cache and dalvic in recovery?
Click to expand...
Click to collapse
Yes, it still freezes at a black screen, because of the mods applied to my Rom, reinstalling the os is a bit of pain because I have to apply them again
Sent from my Desire HD using Tapatalk 2

humzaahmed155 said:
Yes, it still freezes at a black screen, because of the mods applied to my Rom, reinstalling the os is a bit of pain because I have to apply them again
Sent from my Desire HD using Tapatalk 2
Click to expand...
Click to collapse
Well it seems then that one of your mods is to blame.
have you attempted to install your Rom without your mods?

OMGMatrix said:
Well it seems then that one of your mods is to blame.
have you attempted to install your Rom without your mods?
Click to expand...
Click to collapse
Yup, after the.camera stopped.working again I decided to install.them again, it made no difference to be honest
Sent from my Desire HD using Tapatalk 2

humzaahmed155 said:
Yup, after the.camera stopped.working again I decided to install.them again, it made no difference to be honest
Sent from my Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I think you misunderatood the question, if one of your mods are causing the problems, do you know which one? If yes then why do you install it? If no then reinstall the rom with no mods at allfor a few days then add one of the mods and wait a few more days to see if everythings ok and keep doing that until you can identify which mod is causing the problem. Id do a nandroid before installing each mod. Once identified the mod thats the issue, restore the bavkup from just before it was installed and dont reapply the mod, either do without it or look for an alternative

tonylee000 said:
I think you misunderatood the question, if one of your mods are causing the problems, do you know which one? If yes then why do you install it? If no then reinstall the rom with no mods at allfor a few days then add one of the mods and wait a few more days to see if everythings ok and keep doing that until you can identify which mod is causing the problem. Id do a nandroid before installing each mod. Once identified the mod thats the issue, restore the bavkup from just before it was installed and dont reapply the mod, either do without it or look for an alternative
Click to expand...
Click to collapse
Yup, going.to try it now, I can uninstall all mods from the same AROMA Installer I got them from, I can wait for the new update which has similar mods included
Sent from my Desire HD using Tapatalk 2

Touchscreen stopped working - reflash kernel fixed it

Hi,
Been using an Xperia M since Feb 22, and yesterday I experienced a touchscreen 'crash' for the first time: It seems as if no touch is detected. I panicked and eventually reflashed kernel and reinstalled CM (as per this) - problem solved (but lost data).
Just now the problem happened again and I reflashed kernel only, which fixed it.
I'm a noob, so what's going on here?
1) This is a software problem, right? Since reflashing kernel fixed it.
2) Is this some kind of problem with the CM build I'm using (see link above)
3) Is there anything I can do to prevent this from happening?
Thanks for any help!

Well the same thing happened again. Kernel re-flash did NOT fix it this time.
Does anyone have any idea how to prevent this from happening? And anyone who may be able to explain why this happens?
Thanks for any insights
EDIT: A few reboots later it's fixed again. (just reflashed kernel). The previous times rebooting did NOT help.

in deveoloper options have you set the animations and transistions and durations to 0 ? i found this caused my touchscreen on my old x10 running cm10 to stop working
Sent from my C1905 using XDA Premium 4 mobile app

No I haven't set those options

Ok, so, some updates.
I switched from PecanCM's CM11 build to FreeXperia (311), but the problem still happened, just a few hours back.
Maybe it's just some app that's not playing nice or something, but I have very few apps, and nothing weird, so I don't know what it could be.
Anyway, turns out that if I reboot the phone through Flashtool when the touchscreen is frozen, it FIXES it.
But if I "reboot" by removing and replacing the battery, or through SMS TASKS, this does NOT fix it.
Maybe this is useful to someone out there, and I'll post here if I ever figure out the problem

Well, maybe it's a hardware problem after all...
After about a million reboots, the problem persisted this last time. It even persisted after re-flashing boot, re-flashing ROMs (CM11 / FXP311/312, as well as Sony stock).
Guess it's back to the store...
Unless anyone else has any suggestions??
Thanks in advance.

Sony repaired the phone in 10 days, pretty fast!
They replaced a bunch of components, the touch screen and related stuff, so it seemed.
It's working now. Hopefully I won't have the same problem in 3 weeks.
As a final thought: Whenever the problem was "active" the touch screen also didn't respond in CWM recovery, so maybe that was a giveaway that it was NOT a software problem, but a hardware problem?
Thanks and hopefully I won't be revisiting this thread...

Torious said:
Sony repaired the phone in 10 days, pretty fast!
They replaced a bunch of components, the touch screen and related stuff, so it seemed.
It's working now. Hopefully I won't have the same problem in 3 weeks.
As a final thought: Whenever the problem was "active" the touch screen also didn't respond in CWM recovery, so maybe that was a giveaway that it was NOT a software problem, but a hardware problem?
Thanks and hopefully I won't be revisiting this thread...
Click to expand...
Click to collapse
Just out of curiosity, did they charge extra for the UBL?
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.

Antrikos48 said:
Just out of curiosity, did they charge extra for the UBL?
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Click to expand...
Click to collapse
Unlocked bootloader you mean?
I relocked it first. I unlocked with Flashtool and then could easily relock with Flashtool as well.
Anyway I wasn't charged a thing.

Torious said:
Unlocked bootloader you mean?
I relocked it first. I unlocked with Flashtool and then could easily relock with Flashtool as well.
Anyway I wasn't charged a thing.
Click to expand...
Click to collapse
That's great. I thought that because you were giving your IMEI to Sony to unlock (at least with the official method), even if you relocked it they could still check.
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.

Antrikos48 said:
That's great. I thought that because you were giving your IMEI to Sony to unlock (at least with the official method), even if you relocked it they could still check.
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Click to expand...
Click to collapse
Yeah I requested the unlock code through the official site so I guess they could have checked it.
But maybe I just never used it

Sony does have any fw update plan in near future on Ion???

Since i cant use jb (.211) fw as phone became unresponsive everytime when try to download something whether it is from play store or browser. Sick of using ics from last 1 year. Need a stable solution.

Emrul said:
Since i cant use jb (.211) fw as phone became unresponsive everytime when try to download something whether it is from play store or browser. Sick of using ics from last 1 year. Need a stable solution.
Click to expand...
Click to collapse
sony wont update anymore..i would suggest rooting your device and installing a custom rom

Nope. The months for which the Sony would support the ion is over and seems no future support from Sony
I suggest you to root ur phone, unlock bootloader and install a custom ROM. Its worth it.
Being a ion user I was disappointed with Sony regarding support but installing custom rom has given a new life to my ion
Sent from my Xperia ion using XDA Premium 4 mobile app

Emrul said:
Since i cant use jb (.211) fw as phone became unresponsive everytime when try to download something whether it is from play store or browser. Sick of using ics from last 1 year. Need a stable solution.
Click to expand...
Click to collapse
Install a custom rom or doing a factory reset will help with the problem of freeze during app installation. Or at least it fixes for a month or two, then you have to reset it again. This is what I am doing, if there are other fixes I hope someone will answer.