Database Info

walkman stops randomly

So I've been having a problem with my walkman app on the kitkat update. sometimes when playing music, the track goes completely silent for a few seconds. It's not my headphones and it's not the SD card. anyone else have this problem? I am going to do a reset and if it works I will let you guys know what happens
EDIT: to fix the problem, add the following line to your build.prop file
tunnel.decode=false

i have reset the device and the problem still occurs. furthermore it is occurs in any music player that i use

Maybe some corrupted media files? I listen very often and havent any problem on kitkat with this.
Sent from my D2303 using XDA Free mobile app

it's not the files. It also happens only in sleep mode. I'm investigating the possibility that the android.com.media process is being terminated mistakenly. I will do another test and logcat to come up with a definitive answer
EDIT: I've tracked the problem to the qualcomm audio decoder. will update with further info later

same problem
Any luck? I have same problem for all music players and even on apps like iplayer!

update via flashtool..........
pwatkin8 said:
Any luck? I have same problem for all music players and even on apps like iplayer!
Click to expand...
Click to collapse
download your model no ftf and flash it

btw, this problem got fixed in the .40 release

Sorry your speaking to someone who knows nothing about this stuff. But model is d2305, that help?

I also having this problem. Using Xperia M2 Dual, D2302.

pwatkin8 said:
Sorry your speaking to someone who knows nothing about this stuff. But model is d2305, that help?
Click to expand...
Click to collapse
Get xperifirm and flashtool. Download the latest firmware for your device number with xperifirm, open flashtool, go to Tools -> Bundles -> FILESET decrypt and load all the files in the directory where you downloaded the latest firmware to. It will decrypt the files and offer you to make a bundle (ftf) out of it. You can then flash that ftf to your phone.
As ismithx said though, the problem seems to be fixed in 18.3.A.0.40 and the newest firmware for your device atm is .31
You could downgrade to JB (18.0.A.1.30) in the meantime and wait until .40 is released. If you do, get with xperifirm instead.

if you want, you can fix the audio problem by adding this line of code to the /system/build.prop file
tunnel.decode=false
you will need to be rooted and using an app like root explorer in order to do this

Crim Soukyuu said:
Get xperifirm and flashtool. Download the latest firmware for your device number with xperifirm, open flashtool, go to Tools -> Bundles -> FILESET decrypt and load all the files in the directory where you downloaded the latest firmware to. It will decrypt the files and offer you to make a bundle (ftf) out of it. You can then flash that ftf to your phone.
As ismithx said though, the problem seems to be fixed in 18.3.A.0.40 and the newest firmware for your device atm is .31
You could downgrade to JB (18.0.A.1.30) in the meantime and wait until .40 is released. If you do, get with xperifirm instead.
Click to expand...
Click to collapse
Does 18.3.C.0.40 also fix the audio sync issue in games. And if I flash Customized CE1 18.3.C.0.40 with flashtool when my region comes out can I flash my Customized UK 18.3.C.0.37 backup back to phone with flashtool then receive OTA updates and update with PC companion again. When creating .ftf do I leave out cust-reset.ta what does this file do? .ta files scare me
Thanks in advance

gazzag said:
Does 18.3.C.0.40 also fix the audio sync issue in games. And if I flash Customized CE1 18.3.C.0.40 with flashtool when my region comes out can I flash my Customized UK 18.3.C.0.37 backup back to phone with flashtool then receive OTA updates and update with PC companion again. When creating .ftf do I leave out cust-reset.ta what does this file do? .ta files scare me
Thanks in advance
Click to expand...
Click to collapse
Sorry, I don't play android games, so can't say anything about that. As for regions, yes. From what I know all that differs between the customized_xx builds is which language it sets as your default one. I went DE -> FR -> RU -> DE without any problems and my phone didn't behave any different.
I never left out anything when creating the .ftf, I have my TA-Backup of locked/unlocked bootloader anyway, should anything go wrong.

Problem still exist in 4.4.4
I am using D2302, M2 dual, and now running in latest 4.4.4.
I still having this problem long long time ago. And there is nearly no way to fix it?
Anyone having this problem or someone solved it?
Device : Xperia M2 Dual, D2302, Android 4.4.4, stock, non-root...

henrylim96 said:
I am using D2302, M2 dual, and now running in latest 4.4.4.
I still having this problem long long time ago. And there is nearly no way to fix it?
Anyone having this problem or someone solved it?
Device : Xperia M2 Dual, D2302, Android 4.4.4, stock, non-root...
Click to expand...
Click to collapse
If you have ever disabled a system app then enable it because that's usually the problem, but if not then I am afraid I can't really help you.
Because on all KitKat ROMS, disabling a system app is deadly.
Good Luck.

ismithx said:
if you want, you can fix the audio problem by adding this line of code to the /system/build.prop file
tunnel.decode=false
you will need to be rooted and using an app like root explorer in order to do this
Click to expand...
Click to collapse
shouldn't it be
tunnel.audio.decode=false ?

lozohcum said:
shouldn't it be
tunnel.audio.decode=false ?
Click to expand...
Click to collapse
I'm just following what sony put in build.prop. They commented that it was a reuse of the fix on the xperia Z. I did a bit of research and it turns out the Z had the exact same problem. It has to do with the changes made to kitkat in the way it handles audio
@henrylim sorry, don't know of any other way to fix this

I cant believe this!
With BSplayer music play ok!
It would be that error is in audio codecs in software update?! Bad update...

fix the problem
the issue is with google now, u need to disable the "ok google" voice feature. To do so, simply Just go into google now and tap on Settings. Then tap on Voice and uncheck “Hotword detection.” “Okay Google” will be disabled for both your home screens and within Google Now. but music players will work perfectly again.

I rooted my Sony Xperia M2 Aqua today just to fix this anoying problem, but I still can't change the build.prop file.
It says that I couldn't change the permissions or mount as R/W even though I have root permissions.
Anyway. "tunnel.decode=false" is already in my build.prop and it still doesn't work.
Same as the "google now" solution. Google Now is turned off and my songs still keep stopping.
Has anybody solved this problem? (Android Version 4.4.4)

[Q] The old problem comes back

My phone, sony xperia m2 d2303 4.4.4 18.3.1.c.1.15
I was so impressed by the battery s life of this phone. one charge could last 10-15days! however, recently, i have upgraded the softwair to latest version. the problem started it again. The battery leaks like a sink without a plug. I had the problem before, but sovled it by resetting the phone, but this time, nothing seems working! one charge only last less than 10 hours. What is wrong? I have tried everything suggested, but no use at all, and i am very frustrated!
Please can someone kindly lend a helping hand here? Many big thanks in advance.

beilun said:
My phone, sony xperia m2 d2303 4.4.4 18.3.1.c.1.15
I was so impressed by the battery s life of this phone. one charge could last 10-15days! however, recently, i have upgraded the softwair to latest version. the problem started it again. The battery leaks like a sink without a plug. I had the problem before, but sovled it by resetting the phone, but this time, nothing seems working! one charge only last less than 10 hours. What is wrong? I have tried everything suggested, but no use at all, and i am very frustrated!
Please can someone kindly lend a helping hand here? Many big thanks in advance.
Click to expand...
Click to collapse
Phone status? Root? Locked unlocked bootloader?

Have you tried a factory reset, or a complete fresh install of the ftf. I am on 18.3.1.C.1.15 myself and my battery life is as good as before I updated also it can take a while to settle down after a update. Also there's no way a full charge would last 10-15 days unless the phone wasn't used at all n it just sits there like a paperweight
D2303 18.3.1.C.1.15 kk deodexed rooted philz touch recovery bravia engine 2 + x-reality viper audio

[email protected] said:
Have you tried a factory reset, or a complete fresh install of the ftf. I am on 18.3.1.C.1.15 myself and my battery life is as good as before I updated also it can take a while to settle down after a update. Also there's no way a full charge would last 10-15 days unless the phone wasn't used at all n it just sits there like a paperweight
D2303 18.3.1.C.1.15 kk deodexed rooted philz touch recovery bravia engine 2 + x-reality viper audio
Click to expand...
Click to collapse
i have tried factory ret but no use. how to do a complete fresh install ftf? my phone is not root but unlocked. thanks.

Either software repair option in pcc or just flash whole ftf via flashtool.
D2303 18.3.1.C.1.15 kk deodexed rooted philz touch recovery bravia engine 2 + x-reality viper audio

Install some battery app like GSam to see what draining you battery, and if you have unlocked bootloader, flash ftf, PC Companion won't work.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4

[Help] Z1 DualRecovery does not load anymore after Update

Hi folks,
my Sony Z1 (Germany) is still on KK 4.4.2 and I'm looking forward to update to LP 5.x because my new car will support "Android Auto" and I'm excited about to test what can be done with it (below Android 5.x only Mirrorlink is supported which does by far not offer as many options and supported Apps than 5.x). That is the story about my intention.
I tried to use the "search" to find other equal/ similar threads and found tons of posts saying "Recovery". I did not find any which lead me to an answer. So here I go.
My Z1 is rooted and I had the dualrecovery version 2.0.0 installed until yesterday. After reading this thread http://forum.xda-developers.com/xperia-z1/general/stock-rom-14-5-0-270-customized-sg-t3113543 I thought it would be a good idea to start with an update of the DR as the recommendation is version 2.8.3. I went ahead and downloaded the latest flashable version of the DR 2.8.9 and flashed it through the existing recovery. The installation worked smooth and easy. But ...
Now my Z1 is not booting into the recovery anymore. No matter what I try. After turning it on it vibrates and the green LED still turns on but pressing vol +/- does not bring up the (any) recovery menu. Allthough using the NDR utils app ends in the same result.
So I decided to download the 2.8.3 installer version and flashed it with my phone connected to the PC via USB. Again the installation finished without error messages but I still can't access the recovery.
Unfortunately I did not make a backup of the "chargemon" file (as recommended in the other post) before. :crying:
So I'm lost at the moment. Someone told me that he made a similar experience and that he found that the version of the DR he used was somehow to new and not supported. He was able to install an older ("supported") version again and the recovery was back up working like charme.
I tried to find my previous 2.0.0 DR version but I couldn't.
Does anyone here know which version of the DR I can use with my device and where I can get it? The NUTs download section does not have such a long history ...
Can I do anything else without having to restock, re-reoot, etc. my phone?
Thank you very much for your help!
Best Regards
Forever1972
Edit: I'm sorry but I just saw that there is a specific Q&A thread for the Z1 DualRecory here: http://forum.xda-developers.com/showthread.php?t=2647487 So maybe it is possible to move it over!? Thank you and sorry for screwing up! I'm not used to the board structure yet. I was believing that this is the correct (and only) Q&A section and followed the rules to post all help questions here.

tamam
SM-T532 cihazımdan Tapatalk kullanılarak gönderildi

Well, what worked for me was to go back to stock root it and so on... That took me 2 days and was real pain in the ass. Try to delete your recovery partition in fastboot. I am not sure how it is with stock ROM because I always use aosp roms. If you can and if you won't brick your device install custom kernel with recovery. I'm using m5. Tho even with kernel installed my recovery didn't work. But then I used nuts duall installer and it worked. NDT Utilis has an option to choose which recovery to load. Hope that helps. Don't blame me for nothing. ;p good luck
Sent from my Xperia Z1 using XDA Forums Pro.

Should we upgrade to 5.1 ?

Hi, I have D2403 with zexperience installed on it and I wanted to hear your guys oppinions on 5.1.I have locked bootloader and I can't unlock it and I dont understand is it safe to root now or no with Locked BL? Is it worth to update 5.1 or should i stay with my current system etc..?
cheers

Yes you can update of you want to, it does take up slightly more room than kk did. it took about two weeks for my battery life to settle down but once it does battery life is better than kk for me never get less than 5-6hrs screen time sometimes a bit more and that's with the zram as Sony intended. yes root is available for LB but only by flashing a pre-rooted zip via recovery on rooted kk and recovery is only available at the minute by using t2u nut dual recovery(not ideal but it does work). If you're totally stock and don't want root I'd update by Sony pcc. Only thing I'm really missing is xposed I think it was worth the wait myself.
D2303 5.1lollipop customised NCB rooted LB t2u nut dual recovery bravia engine+x-reality debloated

Weekend Offender said:
Hi, I have D2403 with zexperience installed on it and I wanted to hear your guys oppinions on 5.1.I have locked bootloader and I can't unlock it and I dont understand is it safe to root now or no with Locked BL? Is it worth to update 5.1 or should i stay with my current system etc..?
cheers
Click to expand...
Click to collapse
Rooting is as safe as ever. Just more complicate to enable it (basically start from KK, root it, install recovery, make PRF file with 5.1.1 system, flash PRF file from recovery, flash rooting zip from recovery, flash remaining 5.1.1 components with Flashtool and restart all over downgrading to KK if anything goes wrong).
Regarding if it's worth it.. The current issues are:
- The camera sucks for many. Even Xperia Blog reported it now.
- It uses more RAM (which is vey disappointing. I thought ART was going to need less memory?!). Disabling the zram and setting the minfree as they were in KitKat one gets nearly zero multitasking
- Frequent I/O wait even with the zram disabled (but not as bad as with the zram. Unfortunately see above)
- The WiFi has different functionalities from KK (it stays connected to the WiFi even if the AP drops the internet connection. The option to disable it has gone. In other cases it shows an exclamation mark due to something with Captive Networks)
- It seems to me it lags more. But I have plenty of apps installed.
- Few old apps perform poorly
- Many old KK Xperia themes won't work in full , yet (at least the ones I liked the most)
- Potential issues with the GPS (it seems to be a bug in Lollipop generally speaking)
- I hate the new notifications
The Pros:
- Better Stamina mode
- The slick new UI, I especially love the new open applications list (which finally puts a separate window for apps open inside other apps. IMDB from TV Sideview excluded, though)
- Some newer apps make full use of the Lollipop API and more will follow
IMO KitKat is more stable and efficient. But I like Lollipop nonetheless so I decided to stick with it. The few bugs around aren't a deal breaking to me.

Yes you should always upgrade to the newest android.

After battery drain,gps and camera issue I am back to 4.4.4 and ALL work fine and i am happy.

I'm holding back to see if we can get a working recovery (other than Nut's T2U) on a locked bootloader and hopefully then @linuxct will cook us up a new version of his Lite ROM based on 5.1.1 with all the kinks of the official software ironed out

gordonthegopher said:
I'm holding back to see if we can get a working recovery (other than Nut's T2U) on a locked bootloader and hopefully then @linuxct will cook us up a new version of his Lite ROM based on 5.1.1 with all the kinks of the official software ironed out
Click to expand...
Click to collapse
We (@AleksJ and I) are currently working on a fully functional recovery solution for both Lollipop and KitKat (No need to use T2U solutions anymore, which is quite RISKY as I explained in some threads before).
If there aren't any inconveniences, we should be releasing it soon. After that I'll start the Z4 eXPERIence 4.0 (it'll be a light edition) development.

Yea true, two days ago linuxct told me that he's found a way to use a good bueselinux module by zxz0O0 in our recovery installer.
Well fine the installer is back on the game, it can be used on the recent Android release with old recovery. But....recently we also noticed a very nasty touch screen issues the reasons for which are unclear for now.
p.s.
The PhilZ Touch project is "End Of Support", but believe or not with this recovery boot.img I can install and run on my unlocked M2 the latest Omnirom and CM (without sensors lib) in the same way as CWM and TWRP..)
Of course I can't and don't want to tell anyone what and how to do. Just share my opinion.

Hi, when can we expect the new Z4 eXPERIence 4.0to arrive? if You need some Beta testers, I would be happy to asign
(Sorry if this isn't the right thread for the question!)

@semil
Linuxct said he will work on updating that rom after he and AleksJ finish working on a legit recovery for LB.

[Completed] How to restore my Sony Z1 back to its original state (custom -> stock recovery)?

Hi, a few months ago I decided to install a custom ROM on my Sony Xperia Z1. In order to do that I first followed [1] to install a custom recovery (I think I followed the tutorial pointed by the link, but I did that a few months ago so I might be wrong). This way or another I installed a custom recovery - now when entering recovery it says: PhilZ Touch 6.59.0, ClockworkMod v6.0.5.1. Unfortunately I didn't have time to play with it and finally I didn't even install any custom ROM. So my Z1 is now on 14.5.A.0.270.
Now I'd like to use the standard OTA upgrade to move to Android 5.1 (14.6.A.1.236) and my Z1 offers me that. But once downloaded the upgrade cannot be installed for some reason (I suspect it's the custom recovery). When the upgrade procedure starts it asks me to reboot the phone, after a while the Android guys and a progress bar shows up, but it stops after like 10% of the progress bar. Once booted back to normal operation the phone says there was an error upgrading software.
So I'm trying to figure out how to bring back the stock recovery hoping that it would solve my problem. I thought about using Xperia Flash Tool (aka Emma) to flash a generic ROM for my Z1 which would hopefully also contain a stock / generic recovery but the tool requires an unlocked bootloader. Unlocking the bootloader would force me to loose my DRM keys and so on. I don't want to follow this path. Is there a way to restore my phone back to its original state before installing custom recovery so that it was able to use OTA upgrades? I'd simply like to use all stock firmware to avoid further complication.
I know it's probably strange to ask on instructions on going back to pure stock software on such forum but you're my last resort.
[1] http://forum.xda-developers.com/showthread.php?t=2261606

XDA Visitor said:
Hi, a few months ago I decided to install a custom ROM on my Sony Xperia Z1. In order to do that I first followed [1] to install a custom recovery (I think I followed the tutorial pointed by the link, but I did that a few months ago so I might be wrong). This way or another I installed a custom recovery - now when entering recovery it says: PhilZ Touch 6.59.0, ClockworkMod v6.0.5.1. Unfortunately I didn't have time to play with it and finally I didn't even install any custom ROM. So my Z1 is now on 14.5.A.0.270.
Now I'd like to use the standard OTA upgrade to move to Android 5.1 (14.6.A.1.236) and my Z1 offers me that. But once downloaded the upgrade cannot be installed for some reason (I suspect it's the custom recovery). When the upgrade procedure starts it asks me to reboot the phone, after a while the Android guys and a progress bar shows up, but it stops after like 10% of the progress bar. Once booted back to normal operation the phone says there was an error upgrading software.
So I'm trying to figure out how to bring back the stock recovery hoping that it would solve my problem. I thought about using Xperia Flash Tool (aka Emma) to flash a generic ROM for my Z1 which would hopefully also contain a stock / generic recovery but the tool requires an unlocked bootloader. Unlocking the bootloader would force me to loose my DRM keys and so on. I don't want to follow this path. Is there a way to restore my phone back to its original state before installing custom recovery so that it was able to use OTA upgrades? I'd simply like to use all stock firmware to avoid further complication.
I know it's probably strange to ask on instructions on going back to pure stock software on such forum but you're my last resort.
[1] http://forum.xda-developers.com/showthread.php?t=2261606
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Wow, this recovery's install is pretty much a toolkit! What I don't get is why it doesn't offer to back up the original recovery. Oh, 'cos Sony does not have a stock recovery.
This post should help. Or this post (for navigation purposes).
Any questions, you can post in the following thread (once you have an XDA account):
> Sony Xperia Z1 > Xperia Z1 Q&A, Help & Troubleshooting > I can't enter Recovery mode what should I do
Or..
> Sony Xperia Z1 > Xperia Z1 Q&A, Help & Troubleshooting > Sony Xperia Z1 Ask Away help thread.
Hope this helps, and good luck!