Database Develop

[Q] Xperia V - SOD, software or hardware?

Hi,
do we know if the SOD problems are software or hardware related? ( Was gonna link to the SOD thread at Sony, but cant because of few posts. But google "Xperia V random freeze in standby" and your there..)
I am about to send my phone in for service, but since this will propably take a couple of weeks im hoping a software fix would be released.

laaw said:
Hi,
do we know if the SOD problems are software or hardware related? ( Was gonna link to the SOD thread at Sony, but cant because of few posts. But google "Xperia V random freeze in standby" and your there..)
I am about to send my phone in for service, but since this will propably take a couple of weeks im hoping a software fix would be released.
Click to expand...
Click to collapse
should be software problem.
if u were to flash a custom rom, the number of SOD is very little, or dont have.

chunlianghere said:
should be software problem.
if u were to flash a custom rom, the number of SOD is very little, or dont have.
Click to expand...
Click to collapse
Anyone that can confirm that SOD problems disappeared on custom rom?
And if so, which rom?

I set the minimal CPU speed to 486 MHz and it helps.
Sent from my LT25i using xda app-developers app

phhuang said:
I set the minimal CPU speed to 486 MHz and it helps.
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
So you had SOD, set min cpu and it helped?
Which firmware version?
How frequent was the SOD?
How long without?

I use the latest JB rom. I got 1~2 SoD per day before minimal CPU setting change. Now it stands well for more than two days without SoD. The Wifi is on. Maybe my good luck but worth trying.
laaw said:
So you had SOD, set min cpu and it helped?
Which firmware version?
How frequent was the SOD?
How long without?
Click to expand...
Click to collapse

with Wifi off and stock ROM, I'm now on 9 days without SoD.
Though my old Ion on the older ROM has never rebooted even once...

Rashkae said:
with Wifi off and stock ROM, I'm now on 9 days without SoD.
Though my old Ion on the older ROM has never rebooted even once...
Click to expand...
Click to collapse
Wifi of is not an option. Like a sportscar without an engine, but nice to get solid indications that WiFi actual is the problem. Seems like it would be fixable by software then, if only Sony care to take action.

Hmmm... a SoD again. :crying:
phhuang said:
I use the latest JB rom. I got 1~2 SoD per day before minimal CPU setting change. Now it stands well for more than two days without SoD. The Wifi is on. Maybe my good luck but worth trying.
Click to expand...
Click to collapse

laaw said:
Anyone that can confirm that SOD problems disappeared on custom rom?
And if so, which rom?
Click to expand...
Click to collapse
From my experience using Xperia V Stock ROM Singapore FTF Jelly Bean for 3 weeks, I must say that it is the best ROM I ever used for my Xperia V. Better than my stock ROM Malaysia ICS version. Give it a try and feel it.
----------------------------------
Using Xperia V - Bootloader Locked - Non-rooted - Stock ROM Singapore FTF JB - about a month using Xperia V from Malaysia

wantp_LT15i said:
From my experience using Xperia V Stock ROM Singapore FTF Jelly Bean for 3 weeks, I must say that it is the best ROM I ever used for my Xperia V. Better than my stock ROM Malaysia ICS version. Give it a try and feel it.
----------------------------------
Using Xperia V - Bootloader Locked - Non-rooted - Stock ROM Singapore FTF JB - about a month using Xperia V from Malaysia
Click to expand...
Click to collapse
Did you have SOD issues on the Malaysia ICS?
If so, how frequent?
And what more what excatly do you mean with best rom?
No SOD? Less SOD?

laaw said:
Did you have SOD issues on the Malaysia ICS?
If so, how frequent?
And what more what excatly do you mean with best rom?
No SOD? Less SOD?
Click to expand...
Click to collapse
I don't have any problem regarding SOD with my Malaysia stock ROM ICS. But battery drains really fast and really hot even I do not use it (standby mode). Solution: Flash Singapore Stock ROM JB and walla

wantp_LT15i said:
I don't have any problem regarding SOD with my Malaysia stock ROM ICS. But battery drains really fast and really hot even I do not use it (standby mode). Solution: Flash Singapore Stock ROM JB and walla
Click to expand...
Click to collapse
This thread is about the SOD( "Sleep of Death") problems that some users have experienced on their Xperia V.
With the purpose of figuring out if this is a hardware( need to get phone replaced) or software( can be fixed by update).
So if you never had any issues with the SOD on your phone, on either ICS or JB, the information about which rom you think is the best do not help with the question asked in this thread. Please read before posting...

laaw said:
This thread is about the SOD( "Sleep of Death") problems that some users have experienced on their Xperia V.
With the purpose of figuring out if this is a hardware( need to get phone replaced) or software( can be fixed by update).
So if you never had any issues with the SOD on your phone, on either ICS or JB, the information about which rom you think is the best do not help with the question asked in this thread. Please read before posting...
Click to expand...
Click to collapse
I just give my opinion. If this method helped other users fixing their SOD, who knows. I suggested to my friend that have SOD problem (Stock ICS Malaysia) to flash his Xperia V with Stock ROM Singapore, and he has no problem with SOD until now (a week of usage).
Just give it a try.

phhuang said:
Hmmm... a SoD again. :crying:
Click to expand...
Click to collapse
Have you tried a factory reset? When I had this issue on my Xperia TL, (before I rooted it and installed XperimenT) I uninstalled a ton of apps and disabled the ATT apps. It was doing the SOD every night. I would go through any recent apps you've installed and delete/disable them. If that doesn't work do a factory reset and _slowly_ reinstall apps. I think this is a case where something is interfering with Sony's stock firmware.

for those still having SOD, maybe u can try this. not sure it helps or not. because before i install jellybean, i review the code in build.prop first. so that is why it didnt happen on me for 2 weeks. well, i test it out yesterday.
use either ES file explorer or Root explorer, go to system -> build.prop.
find this line dalvik.vm.heapsize=36m, put a # in front of it to disable this code.
it could be because there is another similar code, thus conflict. u can find another similar line at the bottom of build.prop.
hope it helps!

chunlianghere said:
for those still having SOD, maybe u can try this. not sure it helps or not. because before i install jellybean, i review the code in build.prop first. so that is why it didnt happen on me for 2 weeks. well, i test it out yesterday.
use either ES file explorer or Root explorer, go to system -> build.prop.
find this line dalvik.vm.heapsize=36m, put a # in front of it to disable this code.
it could be because there is another similar code, thus conflict. u can find another similar line at the bottom of build.prop.
hope it helps!
Click to expand...
Click to collapse
Does SOD happen again until now ?

maxwux said:
Does SOD happen again until now ?
Click to expand...
Click to collapse
no more.

chunlianghere said:
no more.
Click to expand...
Click to collapse
WOW :good:
I will try it.
thanks.

maxwux said:
WOW :good:
I will try it.
thanks.
Click to expand...
Click to collapse
News? My gf needs a new phone. How to find a fix soon.

[ROM/MOD][WIP]CM for locked BL

Hello guys
First, big fat disclamier:
THIS IS NOT WORKING. Please don't try this for fun, only if you're willing to put in some time to help me get this fixed.
@djolivier and @letama worked out a way to get CM10 running on Xperia S with locked bootloader, loosely based on the work @atis112 did for Xperia U.
For the past couple of days I've been trying to port it to our beloved T.
It does sort of boot but there is nothing on screen. Logcat is working however and so is adb shell (though no su) so we have some way of debugging.
At the moment there is a working recovery (CWM 6.0.4.6 for locked BL by @davidmarco), enter it by pressing vol+ when the led is blue (it will turn green, then red). Here you will have an su shell and you can get dmesg and /proc/last_kmsg.
Please read the thread by djolivier to get an idea of how it works. In the last couple of pages you will find everything I have tried so far and some insightful answers from letama.
So the main thing now is to hunt down which are the libs/drivers we need.
I will try to get some more info into this thread asap but first I wanted to get it up so those of you who think they can help can get going.
Download
cm10_lb_mint_b12.zip - 188.72 MB
This includes the .489 stock kernel, which is probably the best for compatibility.
XDA:DevDB Information
CyanogenMod for Locked Bootloader, a ROM for the Sony Xperia T
Contributors
TiMiN8R, letama, djolivier
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-08
Last Updated 2014-01-08

Reserved

I think someone starting this off is a great idea, when i have some free time i'll try to offer you some help mate.
But need to get up to speed with it all from djolivier's thread before anything else. But i'm happy to offer some help when i can, if that be testing, or general de-bugging.

This is awesome.keep up Timn8r
Sent from my LT30p using XDA Premium 4 mobile app

How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app

WhiteNeo said:
How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
Letama already helped me a lot over in the other thread, getting it up to this point. But now we need to find some very device specific stuff, that's best left to the people who actually have the device to test and debug. My time is limited this week and I don't have a need for this since mine is unlocked, it's just for the sport, so I figured, let's get some other people in on the action
Sent from my Xperia T using XDA Premium 4 mobile app

now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?

oddeceed said:
now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?
Click to expand...
Click to collapse
Yes that's just about right. We cannot change the drivers in the kernel but what we can do, and what I've been trying to do, is trying to match the drivers in the rom with the kernel, i.e. swapping out CM drivers for drivers from the stock .489 firmware. But there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
letama said:
There is no easy way to solve that I'm afraid. You can try to play with dlls (check this for a list), but it has big chances to fail. The proper way to do that is to get fxp repo, patch hal to match stock kernel and recompile cm.
Click to expand...
Click to collapse
If @Rimmer1966 wants to help he is welcome of course.

TiMiN8R said:
... there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
Click to expand...
Click to collapse
i know less than you and stuck on windows 8.1 which makes it even harder for me to do anything to help .... i hope that this can get up and running ..... providing you can get screen and touch working its more than enough proof of concept of what can be achieved and if enough different devices get going this way then maybe just maybe teams like CM will revert back from thier custom kernel (which i dont like) and start using stock kernels in builds (we can all dream right?)

Any updates on this? I can help as a beta tester or help with building on my pc.

masterjet said:
Any updates on this? I can help as a beta tester or help with building on my pc.
Click to expand...
Click to collapse
Not much going on on my end. I've been running on the leaked stock 4.3 for the last few days. I did have a little go on using the kernel from that rom to boot CM10.2 but I've not made much progress, seems that SELinux is throwing a spanner in the works.
If anyone wants to have a go, here's what you can do. Get the stock .489 here.
We should try swapping out .so in /system/lib/hw one at a time. You can do this by booting to CWM, mount /system and adb push, chmod 0644 the file and reboot. Get a logcat, reboot to CWM and get dmesg and last_kmsg
Code:
adb logcat > logcat
adb shell cat /proc/last_kmsg > last_kmsg
adb shell dmesg > dmesg
Lather, rinse, repeat. It is a slow and tedious process, so the more the merrier
TiMiN8R said:
I replaced hwcomposer.msm8960.so, that seems yo have fixed it. Also tried a couple of others that didn't work: gralloc.msm8960.so (can't start), copybit.msm8960.so (brought back the camera probs). Still no screen.
Most prominent spam now is
Code:
smd_pkt_open: DATA5_CNTL open failed -19
I also noticed this in logcat
Code:
I/clearpad_fwloader( 681): hanlde_arg: option = [default]
I/clearpad_fwloader( 681): hanlde_arg: saved.module_id = [0x32]
E/clearpad_fwloader( 681): read_sysfs: Unable to open /sys/devices/virtual/input/mice/name
E/clearpad_fwloader( 681): read_sysfs: Unable to open fwfamily
That is the touchscreen. There is indeed no /sys/devices/virtual/input/mice/name. I'm not sure if it is related to the no video issue but it's a problem nonetheless.
Click to expand...
Click to collapse

Thread is dead? No updates, no progress?

masterjet said:
Thread is dead? No updates, no progress?
Click to expand...
Click to collapse
Seems a bit of a dead end. Our stock kernel just seems to be to different from the stock kernel.
No-one else seems to want to pitch in and try some stuff out.
Might have another go with 4.3 when the official Sony's finally out.

it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?

like i mentioned before
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow

lordyka said:
it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?
Click to expand...
Click to collapse
If you had read the other thread, you would have known that I've already tried a lot of .so's from stock firmware but nog all of them work. This is the hard part, finding the ones that work.
jewkhok said:
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow
Click to expand...
Click to collapse
Well the first part, the hijacking, is exactly what does mod is doing. With regards to the 2nd-init program, I'm not sure that init itself is the problem. The "only" problem we have is finding drivers/libs that are compatible with both CM and stock kernel. But I could be off though. If someone wants to build us a 2nd-init go right ahead

Wow just came back to the T forums to see how things were going and I see this! Hopefully Tim can port it I'm sure he can
Sent from my XT1058 using Tapatalk

I honestly don't think 2nd init would make a big difference, as TiMiN8R has already stated, the problems are the drivers. You can now either ask FXP to use drivers from the Sony 4.3 Stock kernel or do it yourself...
Good luck on this, you'll surely make it.
Gesendet von meinem Xperia S mit Tapatalk

got the source codes?
I'm thinking about doing the same with Z1, wouldn't mind take a look at your work

If you asked me: here are the sources.
Gesendet von meinem Xperia S mit Tapatalk

Camera won't snap any pictures after updating

Hello guys please help topic say it all it just wont take any pictures.. Camera app loads fine then when i press the snap button am stuck like this (pictures attached)
Im on 757 deodexed unlocked boot loader
Sent from my C6903 using xda app-developers app

try clearing the data in all camera apps in
settings/apps

Tried that already still no avail
Sent from my C6903 using xda app-developers app

Well please elaborate on what you have already done so I don't keep giving you advice that you have already done
Also, knowing which kernel and ROM you are on will help

I tried clearibg cache n data
Forced atop
Disable re enable
Maybe its a hardware issue it only saves front camera pics
I tried turning flash off changed mods
Sent from my C6903 using xda app-developers app

gregbradley said:
Well please elaborate on what you have already done so I don't keep giving you advice that you have already done
Also, knowing which kernel and ROM you are on will help
Click to expand...
Click to collapse
Posted everything i done so far in earlier post forgot to mention changed save directory
Sent from my C6903 using xda app-developers app

Hello nxkr. I also have this EXACT problem. See my post here: http://forum.xda-developers.com/showthread.php?t=2727289
I think that the reply I got was interesting, (the flashin procedures he talke about)
Unfortunately I won't be able to experiment more today, but one thing that hit me, is that I haven't done a real wipe data/factory reset in Philz recovery for some time (have done a few updates). Maybe this should solve the problem?
If you try a full wipe first make a backup of your important apps of course...
Whatever you try from now on, please let me know, I will try everything myself tomorrow, I doubt that the camera is broken, it's just software I think....

which kernel and which ROM?

As I haven't access to the phone today I can't answer that question, but downloads was made from NUT if I remember right.
Also, more duplicates of this problem start to appear, we are not alone on thisone. See:
http://forum.xda-developers.com/showthread.php?t=2706426
I am starting to think that maybe just a kernel update would solve it? Maybe Doomslords kernel? Ahh I want to try but I cannot until tomorrow... Sigh...

I had the same issue, it just cant snap a photo and it can not focus. I had it when i dirty flashed ihackers 4.1 without flashing the full 4.4.2 firmware, the newest one. I solved it by flashing the newest firmware, central europe for me, and then i continued with the fastbooting kernel, installing rom and all the classic stuff. After that the camera works really nice. All i can say is try to flash the full ftf, and then once again your rom of choice, that should get it working properly! Also please do tell what rom and kernel you are using. I use doom btw and its working fine.

VR2014 said:
As I haven't access to the phone today I can't answer that question, but downloads was made from NUT if I remember right.
Also, more duplicates of this problem start to appear, we are not alone on thisone. See:
http://forum.xda-developers.com/showthread.php?t=2706426
I am starting to think that maybe just a kernel update would solve it? Maybe Doomslords kernel? Ahh I want to try but I cannot until tomorrow... Sigh...
Click to expand...
Click to collapse
Right now am using Doom kernel even before the problem was there
gregbradley said:
which kernel and which ROM?
Click to expand...
Click to collapse
deodexed 757 doom kernel
VR2014 said:
Hello nxkr. I also have this EXACT problem. See my post here: http://forum.xda-developers.com/showthread.php?t=2727289
I think that the reply I got was interesting, (the flashin procedures he talke about)
Unfortunately I won't be able to experiment more today, but one thing that hit me, is that I haven't done a real wipe data/factory reset in Philz recovery for some time (have done a few updates). Maybe this should solve the problem?
If you try a full wipe first make a backup of your important apps of course...
Whatever you try from now on, please let me know, I will try everything myself tomorrow, I doubt that the camera is broken, it's just software I think....
Click to expand...
Click to collapse
I did a full wipe data before flashing but it was with Philz sometimes it doesn't work as good as cwm or twrp will check out your thread.. Do you recommend keeping same id in titanium backup
thanks all
Sent from my C6903 using xda app-developers app

[Q] Should I downgrade to 4.3?

I had enough with bugs of 4.4.2
But I never used the 4.3 before, I just bought it new
Should I downgrade? Does 4.3 have bugs?

Try it and see.
I find 4.4.2 rock stable. You say it has bugs.
So no one can tell you, that's the beauty of android. try it yourself and see what you are happy with

gregbradley said:
Try it and see.
I find 4.4.2 rock stable. You say it has bugs.
So no one can tell you, that's the beauty of android. try it yourself and see what you are happy with
Click to expand...
Click to collapse
Well i am using the latest (14.3.A.0.757) one and I have bugs like;
*Sound delay in few games
*Wifi connectivity is low
*Wifi drops sometimes for no reason
It is not that stable or the problem just with my phone

dnzdeniz said:
Well i am using the latest (14.3.A.0.757) one and I have bugs like;
*Sound delay in few games
*Wifi connectivity is low
*Wifi drops sometimes for no reason
It is not that stable or the problem just with my phone
Click to expand...
Click to collapse
I know the bugs you are having, I read the other thread you created about it.
Like I said, its your choice....try and it and see

gregbradley said:
Try it and see.
I find 4.4.2 rock stable. You say it has bugs.
So no one can tell you, that's the beauty of android. try it yourself and see what you are happy with
Click to expand...
Click to collapse
gregbradley said:
I know the bugs you are having, I read the other thread you created about it.
Like I said, its your choice....try and it and see
Click to expand...
Click to collapse
I will going to flash another countrys firmware, maybe that can make difference

dnzdeniz said:
I had enough with bugs of 4.4.2
But I never used the 4.3 before, I just bought it new
Should I downgrade? Does 4.3 have bugs?
Click to expand...
Click to collapse
Personally I've been using android 4.3 on my Xperia Z and it was much smoother for me than kitkat now on Xperia Z1.
So downgrading is a good option, I would do it too, but the viper4android isn't fully supported on 4.3 ROMs.

Maybe using some Custom Roms will solve all your problems?
As I wrote in some threads Evo4 for Z1 is stable as a rock I never had problems with it.

Camera crashes
Kyouran said:
Maybe using some Custom Roms will solve all your problems?
As I wrote in some threads Evo4 for Z1 is stable as a rock I never had problems with it.
Click to expand...
Click to collapse
Does anyone experienced lag and phone crash and random reboots, or when ever I take too many pictures with it?
I tried custom roms like RomAur 8.0, currently I am on rooted stock. But it still does crash and reboot itself.
I bought phone when it was on 4.3 and I never had any crashes then, so now I am also thinking to downgrade it. Any recommendations?

visualizer2k said:
Does anyone experienced lag and phone crash and random reboots, or when ever I take too many pictures with it?
I tried custom roms like RomAur 8.0, currently I am on rooted stock. But it still does crash and reboot itself.
I bought phone when it was on 4.3 and I never had any crashes then, so now I am also thinking to downgrade it. Any recommendations?
Click to expand...
Click to collapse
Yep, I have that. Although it's not been crashing when using camera on 761 yet.
But it has crashed once when using mxplayer and once when browsing the movies.
The "camera not available" pops up aswell from time to time.
I tried 4.3 and it never rebooted. Still touchscreen issues though.
Sent from my C6903 using XDA Free mobile app

So what about that Z1 TOUCHSCREEN ISSUE?

We had a lot of threads about the continuity of Z1 touchscreen issue. Sony admited it and tried to fix with updates what seemed tp be a hardware issue.
I still got the issue on my phone when playing games for a time. I'm running rooted stock 4.4.4 from NUT.
So, did this issue got 100% corrected?

ffp. said:
We had a lot of threads about the continuity of Z1 touchscreen issue. Sony admited it and tried to fix with updates what seemed tp be a hardware issue.
I still got the issue on my phone when playing games for a time. I'm running rooted stock 4.4.4 from NUT.
So, did this issue got 100% corrected?
Click to expand...
Click to collapse
Ghost touch syndrome?

bigb0bby said:
Ghost touch syndrome?
Click to expand...
Click to collapse
This issue:
https://talk.sonymobile.com/t5/Xperia-Z1-Z1s/xperia-z1-touchscreen-problems/td-p/410611

Why people still use 4.4.4?

Because my model is C6943 which have digital TV and I don't think there are kernels/roms compatible with this version. Besides I already have my phone all configured with Xposed modules for this version.
Why, have the newer version fixed the issue? And which version do you use?

This rom fixed ghost touch's for me
http://forum.xda-developers.com/xpe...om-aosp-jaguar-lp-5-1-1-r13-official-t3188925

ShadyGame said:
This rom fixed ghost touch's for me
http://forum.xda-developers.com/xpe...om-aosp-jaguar-lp-5-1-1-r13-official-t3188925
Click to expand...
Click to collapse
Does this have to do with the android version? Because thsi rom doesn't work for C6943 version and I'd probably need a kernel for it as well.

ffp. said:
Does this have to do with the android version? Because thsi rom doesn't work for C6943 version and I'd probably need a kernel for it as well.
Click to expand...
Click to collapse
No, i had 5.1.1 stock with those issues, guess its kernel related

are you sure? It was the same issue described in the link I posted? Which kernel with digital TV (C6943) should I get?