How's the progress on finding out what is causing all these issues? Anyone got any idea apart from turning off WiFi?
I've tried AOSP (kangXperiaProject 4.1.2 r3), The SuperSport version, and in the 4.1.2 i didnt have the SOD problems, but some other missing parts / issues made me go back to stock.
Now I'm having issues with it rebooting basically every time I unlock the screen. (reflashed with my own FTF, and relocked the bootloader to stock).
Any ideas?
Other XV dosnt have SoD with the stock 4.1.2 ROM, i think is a hardware Problem.
Some SoD users become a new motherboard(contact the sony support) then is the SoD go away. But the sony support make mostly the firmware new, but that dosnt help.
I have my SoD XperiaV send back to the dealer and become back my money. I wait and buy ist to an other time, i thing some charges of the Xperia-V are bad.
Related
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Cheshire-Cat said:
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Click to expand...
Click to collapse
try in stock rom/eclair about a week ,I think it is about nAa issue !!
just full wipe and flash stock rom..........using flash tools......or try using song update service........
binhari said:
just full wipe and flash stock rom..........using flash tools......or try using song update service........
Click to expand...
Click to collapse
I did, as I stated before. Still not working properly.
What I don't understand is how flashing a new kernel/ROM can break it in a way that not even flashing back stock Eclair solves the problem. I can only think of hardware failure but... it would be akin to a computer failing because you installed a different version of Windows.
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
illusionist.h1 said:
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
Click to expand...
Click to collapse
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Cheshire-Cat said:
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Click to expand...
Click to collapse
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
illusionist.h1 said:
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
Click to expand...
Click to collapse
I don't know exactly how ROM flashing works -- I've seen a "backing up system files" message, and I think that there's a reason why the stock 2.1 image is about 200 MB while CM7 ROMs rarely exceed 100 MB. I guess that some files are kept. Maybe if one or more of those files (say, a driver) is replaced with an incompatible version... but then, flashing stock should solve it. Maybe someone can shed a bit more light on the subject?
Another possibility is software-caused hardware failure, where some kind of misconfiguration physically damages the hardware. It's very uncommon, but who knows.
Hello. As some of you may remember - I have serious problems with wakelocks and it's related to a "SMSDispatcher" service (for those who are interested - http://forum.xda-developers.com/showthread.php?t=2138980).
I had no issues at all on ICS before I upgraded to official JB. Great battery life, huge screen-on time, ~3 days on battery with small usage was something normal for me.
But after upgrading to JB I started to get wakelocks. Loads of wakelocks. I checked battery stats - the Dialer apk showed up. I installed Better Battery Stats and it showed me that "SMSDispatcher" prevents my phone from goind into deep sleep. I thought it was a bug so I flashed back my .195 4.0.4 FW. And guess what. The problem was still there. It... transfered from JB to ICS?! I have this problem for 3 weeks now and even today I still don't know how can I get rid of this.
I tried wiping every partition on the phone including both SD's. Tried deleting contacts on SIM card. Tried deleting all contacts from GMAIL and manually adding them again. Tried flashing stock JB and use my T without restoring ANYTHING. But I haven't tried one thing:
Yesterday I installed unofficial CM10 (from original android development subforum). Almost clear android could have bringed a peace to me finally. It runs great but not perfect. Why? I still have SMSDispatcher issue. LOADS of wake-ups from the Dialer apk (sometimes it shows as com.android.phone, sometimes as RILD).
What I discovered is that on ICS these wakelocks are shorter than on JB. About 1/1,5h of wakelocks for ~22h on battery. On Jelly Bean it was 3h for 8h on battery.
As far as I remember on 4.0.4 .195 FW there was -19 baseband. Both official JB and CM10 use -33 baseband which may be a problem, I don't know.
So my next step in my long path to get rid of this annoying bug is changing to ICS baseband.
And my question is - which files shoud I pull from .195 stock SONY 4.0.4 FW?
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33. So I probably need binaries/files pulled from ICS and I don't know which ones.
Can you help me? Maybe with your help I could finally get rid of this or at least make the problem less annoying...
Can you just flash an ICS firmware and exclude everything except baseband?
Not sure if it wise but it may help you.
romcio47 said:
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33.
Click to expand...
Click to collapse
I already did that. No result.
Another idea - is it possible to repair software on the phone with unlocked BL?
EDIT:
Ok, found Jozinek's thread with .ftf to relock my bootloader. I will try to repair my software and see if this fix my problem.
Problem solved. It was my old SIM card's fault. It was more than 6 years old and I had to manually cut it from mini-SIM to micro-SIM shape. I probably damaged its inside structure or something. I went to my carrier and requested a new SIM card factory cut to a micro-SIM shape and now everything is ok! No strange wakelocks at all!
Hi mate!
I just was wondering after all that u've experienced what do you thing about JB , which is better for performance and battery life management ICS or JB? I'm just thinking is it worth it to upgrade to JB or stay on ICS
Stay on ICS if you don't like charging your phone once a day (in good scenario). Or twice.
ICS has definitely much better working Extended Standby Mode. It gives you amazing battery life sometimes. I'm on JB because of better multitasking and higher RAM available but speaking about the battery - ICS wins. JB just has to be fixed and tweaked by SONY. It's just a first public release. So bugs are something common. We have to wait.
Hey.
This is my first thread so welcome all. If this issue was fixed or if there is similar thread please close it down.
I have Xperia T that was branded by Vodafone DE. I updated it once from the standard firmware (I think it was the 4.1.2 android) to 4.3 (9.2.A.0.295), everything was fine, except that on two occasions the screen just could not be forced to turn on. Everything was working, sound, calls etc. I just had to hard reset it to enable the screen. Once when I was receiving call I could not answer it, the screen was jumping, blinking and I could not do anything with it. Hard reset helped again. I thought that those were bugs from the 9.2.A.0.295 but now I'm not so sure.
I downloaded the newest version of flashtool and the UK 9.2.A.1.199 firmware from this site, not branded, not modified. I unlocked the phone using the instructions on the sony site but since i didn't wanted to root the phone I locked it again. I flashed the mentioned UK firmware without problems and then the phone started to randomly reset itself. Usually it is getting hot under the camera and it resets mainly after using facebook or basically internet. It mostly resets when my phone is in the pocked. I tried using pc companion's repair option, used the firmware from Italy, Greece and almost all 9.2.A.1.205 except the Bond release. I think it's not the firmware, I've reverted to the 9.2.A.0.295 to no success. There are from one to six resets a day at random hours. Did someone had this problem? Is it related to the firmware flashing or could be just a coincidence and my xperia is dying from motherboard\battery failure? I replaced my sim card with new one. It also happens with or without the sd card.
Hi, the most common restart's are:
a) Sim card ( you change that)
b) Software ( you change that)
c) Very rare SD card ( try to do that) get the SD out end boot the phone. Edit .. you all ready do that.
d) End must common is the Battery ( first try de c) version ,then if fail , you need to buy a new battery end try.
e) motherboard (well new phone? )
This not exactly the order, but from i have read , point d , b ,a , are the order .
So Good Luck.:good:
I think it could be the battery or the board, since it happens on all firmwares. The thing I would like to know is that using flashtool for an example could somehow damage the phone or the battery? I never found any info on this.
Nekris said:
I think it could be the battery or the board, since it happens on all firmwares. The thing I would like to know is that using flashtool for an example could somehow damage the phone or the battery? I never found any info on this.
Click to expand...
Click to collapse
I have heard that upgrading to 4.3 could actually damage the battery. So yes, it is possible.
I don't know the reason tho
Sent from my Xperia V using Tapatalk.
I have a problem that my phone automatically reboots itself everytime my mobile data is on even when it's not overheated. My phone is using android 5.0.2 build number 10.6.A.0.454 (HK version), kernel 3.4.0-perf-g8fa3dae that comes with it, and it was rooted.
This problem only happens since I update to 4.4.4 or later versions. It never happened on 4.3 (originally installed on the phone).
Anyone got the same problem or any solution for this?
Did you try to wipe data/cache/dalvik?
did you try to fix permissions?
both with recovery
khoale1802 said:
I have a problem that my phone automatically reboots itself everytime my mobile data is on even when it's not overheated. My phone is using android 5.0.2 build number 10.6.A.0.454 (HK version), kernel 3.4.0-perf-g8fa3dae that comes with it, and it was rooted.
This problem only happens since I update to 4.4.4 or later versions. It never happened on 4.3 (originally installed on the phone).
Anyone got the same problem or any solution for this?
Click to expand...
Click to collapse
I am having the same problem, it's rebooting it self only and one thing i measured which is actually strange that while it is under charging then it does not reboot itself so what should be the problem??
Help me to sort out this ASAP.
I had also that issue recently. After so much rom flashing i decided to try to replace the battery and it worked. Just try to replace battery may be that wil also work for you guyz.
The other day, my friend gave me his old Xperia T as it had started to act up and eventually stopped turning on entirely. I took it home, downloaded a generic 4.3 ftf and flashed it. Although the phone now boots, it occasionally reboots or just flat out turns off (without warning - the screen just goes black and I have to turn it back on again). I have tried flashing a few different ftfs, and the problem still persists. Does anybody know how I can stop this and finally be able to abandon my Arc S for good?
hi dude i have the same problem but on xperia v, i installing a stock rom many times but the phone after 5 minuts reboot, i thought was the battery but it isnt. meaby the kernel modify i think, please let me now i u resolved this
alusan20raziel said:
hi dude i have the same problem but on xperia v, i installing a stock rom many times but the phone after 5 minuts reboot, i thought was the battery but it isnt. meaby the kernel modify i think, please let me now i u resolved this
Click to expand...
Click to collapse
I'm fairly certain my problem is just with the battery, as I've installed a 4.0.4 ftf,a 4.1.2 ftf and a 4.3 ftf and the problem is consistent on all of them. Once I've bought a new battery, I'll let you know if the problem still persists.
PluckyJokerhead said:
I'm fairly certain my problem is just with the battery, as I've installed a 4.0.4 ftf,a 4.1.2 ftf and a 4.3 ftf and the problem is consistent on all of them. Once I've bought a new battery, I'll let you know if the problem still persists.
Click to expand...
Click to collapse
i bought a new battery but the problem persist i hope u can resolve this with a new battery