Related
For some odd reason, my wife's phone will randomly lose sound output and input.
For instance, cannot make calls because no sound is heard through speaker and it seems the mic becomes non-functioning, therefore the person on the other line hears nothing.
I've noticed at the same time that no other sounds (system, media, key presses, etc.) can be heard as well.
If the phone is rebooted the problem is fixed. This problem occurs usually once or twice a day. Its running a nearly stock 2.1 w/ root (although no root apps used or installed), I have also tried a different custom rom and have the same issue.
Any ideas? (I have searched and read up on some things, but did not see a definitive answer)
** Working on a fix now **
DrewX2, I'm having the same exact problem. Thought I was crazy! So I have the Damageless 2.08.1 (Android 2.1) ROM installed, and I thought I was being punished for not using Sprint's official ROM image . But you say that your wife's phone exhibited this behavior in more than one setup? What do you mean by "nearly stock"? Maybe someone out there knows of a way to look or download the internal error logs on the Android platform so we can at least get some stack trace info? Thanks!
Here guys, try this thread.
http://forum.xda-developers.com/showthread.php?t=657244&highlight=Audio+fix
-------------------------------------
Sent via the XDA Tapatalk App
danaff37 said:
Here guys, try this thread.
http://forum.xda-developers.com/showthread.php?t=657244&highlight=Audio+fix
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
This is the exact fix I installed. So far no problems, will report back in a day or two.
Also, for the earlier question, when I said nearly stock, I should have said I am using nfinitefx45's Stock Sprint Deoxed ROM.
Has anyone else had issues with tracks jumping or freezing briefly in the walkman player? I've only had it happen a few times, but it never normally happens with the files themselves. Any ideas?
Ill reply this happened previously on one of the last java Sony Ericsson phones think it was the c905 - cant remember. But I fixed it somehow.
Anyways,
Are the songs on phone or memory card?
What bit rate are the songs? What format?
Sent from my LT26i using Tapatalk 2
Sound issues
Hello!
I have the same problem with freezing music not only in walkman app, but also in player pro. It happens more often when device is using multitask (for example, browsing and music at the same time), but sometimes there are pauses even if screen is off.
All the media is [email protected] stored on microsd.
And i have never noticed this problem in media apps that use their own media decoder. Sound in videos played by mxplayer is ok, and music has no longer these freezes as i started to use playerpro with DSP pack.
As far as i can see, the problem is caused by software, not hardware. I hope sony will fix it by firmware updates.
DarkKrypt said:
Ill reply this happened previously on one of the last java Sony Ericsson phones think it was the c905 - cant remember. But I fixed it somehow.
Anyways,
Are the songs on phone or memory card?
What bit rate are the songs? What format?
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
They're stored on internal memory as I need to get round to buying a 64gb microsd. Songs are 128kpbs and mp3.
It freezd when listening FLAC music.
Sent from my C6603 using xda premium
any other ideas? this is seriously bugging me - listening to music is probably one of the main things I use my phone for outside of calls/texts
Um have you cleared the cache for the walkman app?
Or like windows pcs.
Clear the phone - factory reset it - start from scratch do a clean wipe.
Try another music player.
Or try a different bit rate mp3
Sent from my LT26i using Tapatalk 2
DarkKrypt said:
Um have you cleared the cache for the walkman app?
Or like windows pcs.
Clear the phone - factory reset it - start from scratch do a clean wipe.
Try another music player.
Or try a different bit rate mp3
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
Have done all but cleared the cache and bit rate so will try that today. Also getting my sd card today so will see if it makes any difference once they're on that instead, as is it possible it could be to do with the read speed of the internal memory?
As i have already said, it looks to be walkman app problem.
I have noticed no such issues since i started to use another player app.
Sent from my C6603 using xda app-developers app
van2z said:
As i have already said, it looks to be walkman app problem.
I have noticed no such issues since i started to use another player app.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
See, I'm having the problem regardless of what music app I use, which is a bit weird. Although last night, I wiped all my music again and transferred just a few of the songs, so will continue to see how that goes.
Ok so have tried everything now - different bit rate, clearing the cache, factory reset, phone repair, using different music players, trying it on both internal memory and SD card and it's STILL skipping.
Could this therefore just be a hardware fault?
That's really weird.
You know, i had same problem, some people were reporting about this problem both here and on local russian forums, but the feedback about the issue was not that massive as it would be in case of hardware fault. And at the moment everything works fine on my device.
If you dont mind, i'll contact you in a moment via private message, hope i can provide some help.
Sent from my C6603 using xda app-developers app
van2z said:
That's really weird.
You know, i had same problem, some people were reporting about this problem both here and on local russian forums, but the feedback about the issue was not that massive as it would be in case of hardware fault. And at the moment everything works fine on my device.
If you dont mind, i'll contact you in a moment via private message, hope i can provide some help.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I mean if it was a hardware fault just specific to my phone. It's annoying if it is as I haven't experienced all the other issues people have had like dead pixels, LED light problems, stamina mode not working, etc. so would be reluctant to swap my phone and potentially end up with any of those issues.
Had this problem' solved by using player pro and having audio buffer set to very high and priority set to high sorted it for me.
Daza2020 said:
Had this problem' solved by using player pro and having audio buffer set to very high and priority set to high sorted it for me.
Click to expand...
Click to collapse
Using player pro with DSP enabled, so will try editing the audio buffer and priority settings as well.
Well, everything is possible.
But i can't see the way for hardware to cause this problem with music, but not to affect any other use-cases of the device. As you said, you experienced no other troubles like random rebooting or graphic disfiguration, which would point to defects of cpu or memory or somewhat.
My guess is that system lets the device to fall into "deep sleep", that's why music decoder stops its work for a moment and causes the freeze. Just a software bug. But i can mistake, though.
Yes, i forgot to notice this: the priority of decoder in dsp settings of playerpro is also set to max.
Sent from my C6603 using xda app-developers app
van2z said:
Well, everything is possible.
But i can't see the way for hardware to cause this problem with music, but not to affect any other use-cases of the device. As you said, you experienced no other troubles like random rebooting or graphic disfiguration, which would point to defects of cpu or memory or somewhat.
My guess is that system lets the device to fall into "deep sleep", that's why music decoder stops its work for a moment and causes the freeze. Just a software bug. But i can mistake, though.
Yes, i forgot to notice this: the priority of decoder in dsp settings of playerpro is also set to max.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Ok so I downloaded playerpro from the link you sent me after uninstalling the player pro and DSP pack I already had on my phone and weirdly, it seems to have improved. There's still the occasional jump/pause but nowhere near as bad as it was. Will keep testing and update. If it continues to be buggy though, I still might pop into CPW tomorrow and see whether I should get it swapped.
Update: It seems you could be onto something regarding it going to sleep - I don't know how it would go to sleep so quickly, but in look and feel, when I selected to keep the screen on, and it didn't get locked, I experienced no jumping in the tracks.
Looking at this http://androidforums.com/captivate-...-playback-stock-player-samsung-captivate.html
I wonder if it could be anything to do with CPU throttling? It is definitely the case that it only skips when the screen is off, so I'm assuming I have no way of fixing this.
Anyone able to get Lastfm scrobbling to work with Walkman?
Tried the Xperia App but it only works with the official Lastfm app and it's a piece of crap.
C1emen7s said:
Looking at this http://androidforums.com/captivate-...-playback-stock-player-samsung-captivate.html
I wonder if it could be anything to do with CPU throttling? It is definitely the case that it only skips when the screen is off, so I'm assuming I have no way of fixing this.
Click to expand...
Click to collapse
I have sent a request to sony's support via e-mail asking for their response about this music problem. I hope the answer will come today, so i'll post sony representatives' comment on the issue.
Still believe it is software to cause bugs. Playerpro decoder, set to maximum process priority, doesn't let system to sleep, which increases power consumption, but fixes freezes and pauses. The original sound decoder has lesser priority, maybe there are some bugs in power management, so the issue we decribe happens.
The problem is, there can be no firmware updates for XZ until the end of March or beginning of April, when android 4.2 will become available for our device.
Sent from my C6603 using xda app-developers app
Has anyone found a solution of new firmware (custom or stock)
that fixes this issue where you have no idea of your battery
level and your battery can be ruined because it drains too far?
Can anyone confirm if SONY is aware of this major problem?
How do you use your device with this issue? Any tricks you use
to live with it?
Can anyone confirm when they upgrade to firmware 4.2.2
ie: 10.3.1.A.0.244 or 10.3.A.0.423
they have killed their battery completely?
(ie: it won't take a charge anymore and the phone is ruined?)
> It happens when your battery is 20-35% and u do a battery reset (power+volup)
SO, as long as you don't do this, you don't get the bug?
-Why are you performing this action anyhow?
-Why not just hold the power button and restart your device that way if needed?
Can anyone confirm if a regular reboot (using either the reboot command from terminal or by using an app to reboot) also triggers the bug?
> Installing the 4.1.2 binary does NOT fix the issue;
What if you roll back to stock 4.1.2, or you are on 4.1.2?
Is the bug for sure not there?
Is the bug just on all versions so far of stock and custom 4.2.2?
Is the bug on 4.3?
Does the bug cause the device to think there is more charge than
the battery actually has, thus draining it too low and killing it?
What is the best way to fix the bug once it occurs and is
there any way to tell if the bug is occurring? Someone mentioned
charging it all night is the only way you know you are at 100%?
What devices is the Battery BUG on besides SONY XPERIA Z (ie: model C6602)?
So, to live with this bug, never reset your device, and if you do,
do it before you put it on your charger for a very long time?
Btw, how long would it need to be on the charger worst case?
Battery bug is most likely due to battery stats. Once they are cleared/ reset then the bug goes away. See if u can reset them in cwm or twrp. It has nothing to do with the hardware. I always flash roms on full battery and never had that bug.
Sent from my C6603 using Tapatalk 4 Beta
Wiping battery stats does nothing.
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
Also, the bug is very real - http://forum.xda-developers.com/showthread.php?t=2348174
Sent from my C6603 using Tapatalk 4
I found a solution don't reboot or turn off your phone
Sent from my C6603 using xda premium
Maybe I didn't got the bug because last time I had to was about a month ago, when flashing new rom. Well I did flashed some mods as well. Maybe reset stats while on 100% and flash new rom.
Sent from my C6603 using Tapatalk 4 Beta
LOL. Resetting stats does nothing! It deletes the batterystats.bin file. That file is deleted every time your phone is charged anyway and doesn't have any effect on the battery percentage that is displayed.
Please read the article I linked you to earlier.
Sent from my C6603 using Tapatalk 4
I never had the battery bug!
I've a C6602 and from the original 4.1.2 and the following updates (now the 4.2.2 [0.244]) always the battery was correct!
I've also used all the above-mentioned method of reboot...
because of some games (specially Let's make pottery) and reboot to CWM or normal Reboot with Powerwidget never made the bug!
hope that helps!
The bug is fixed on the latest 244 update.
Hi.
I never had this battery bug on my XZ.
Me too, I don't have this bug before and after 4.2.2
I've had this bug for a long time, but once i've flashed cm 10.2 it's gone.
Gesendet von meinem C6603 mit Tapatalk 4
sebastianlow said:
The bug is fixed on the latest 244 update.
Click to expand...
Click to collapse
Don't think it is
Sent from my C6603 using xda premium
MAJOR BUG Check
Odd. Some people have this MAJOR BUG and some do not??!?!
I will upgrade my UNITED STATES phone by flashing an .FTF.
I'll see if I get this BUG or not. Anyone have a link to
C6602_10.3.1.A.0.244 .FTF for UNITED STATES that doesn't
think they have this bug?
> u shud calibrate the battery in order to get exact output.
Anyone know how to do this?
emrause- you say you don't have the bug on 0.244.
Did you flash your .ftf and which one did you flash?
Are you on stock rom? What is your region?
sebastianlow-
I have read several posts that the bug is still there in the 0.244 thread.
Is it gone for you and did you flash the .FTF? Which one?
> It seems that Spanish FW is free from this bug.
I thought if we flash the .244 .FTF there is no difference in regions!?
Can we safely flash it to our United States phone?
Anyone have a link to it? Will anything change to Spanish?
Does anyone know where to get the latest good .244 .FTF
10.3.1.A.0.244 that we can flash to our United States phone?
I was going to use C6602_10.3.1.A.0.244_Generic India.
Is this one not good and Spanish one is?! Will it change
our keyboard or language or radio stuff incorrectly?
kingvortex- Do you have the bug? Which firmware are you using and did you flash a .FTF?
Did you roll back to 4.1.2 or are you living with the bug?
As long as we don't reset the phone around 20-35% with a battery reset (power+volup)
are we ok? Also if we do reset, just put it on the charger for a long time?
Anyone know how long it takes to fully charge a SONY XPERIA Z roughly before it
switches to trickle charge on the standard US plug adapter?
Anyone have quick answers to any of these or any input on this battery bug?
I'd like to flash the latest to my phone. I have a United States Phone.
Is flashing an FTF a good way to update? What method and
which .FTF should I use? Does the region matter? Anybody have any ideas or links?
Anyone know if the New firmware: 10.3.1.A.1.10 addresses this BATTERY BUG
or is this MAJOR BUG still there?
TIA
its a sony kernel level bug, no solution unless you use a custom kernel which is NOT based on sony source, unfortunately, we have no such kernel at this moment
My xz has battery level bug with 4.2.2 423 and 244 versions. it had not any bug when 253.
Does 10.3.1.A.1.10 fix it possibly?
Do they list frmwares and what is in them anywhere? (ie what fixed)
Also, how do you live with this bug? ie- what do you do so your battery doesn't get ruined and so
you know when your phone is running low if the battery indication is not reliable?
Is the trick to this bug to never reboot your phone during the day and if you do, always charge it
for a long time (ie 100% plus trickle charge) and then the battery is always correct?
This is a pretty major bug. Does SONY know about it?
kkd28- Are you going to roll back to another firmware which does not have the bug?
Do you never reset your device so the bug isn't much of a problem for you?
Anyone else roll back because this battery bug is so bad?
Anyone suffering from this bug can kindly post here a few debug info about the battery?
Those relevant files are on this folder: /sys/devices/platform/msm_ssbi.0/pm8921-core/pm8921-charger/power_supply/battery
The charge_full, charge_now, voltage_now and capacity are the relevant ones. The the last one should be the same number as the capacity listed on the Android user interface, but it wouldn't be true if it is a ROM issue rather than a kernel one.
It is possible to analyze the health of the battery with those numbers. There is also a health file on that folder, whose content should be "Good" otherwise you are on a bad shape.
It should be noted that Android will use the current voltage, not the current charge, to decide when to turn off or stop charging a battery. Also it should be noted that as long as the battery is healthy, there is no risk ruining it even with a bug on Android. Those batteries have a swicth which will be activated in case of low voltage and it will suspend the power supply.
There is no risk in ruining your battery except you are draining it too quickly.
It would be even better if one could post the content of those files right before and after the bug happening.
Regards,
I meant to create this thread a while ago, but thought it was now time to do so given the fact I'm getting 2-3 reboots per day, and doing lots of different things.
The last reboot was just as I begun to upload a YouTube video, but it can happen when doing anything - or when doing nothing (as in it will sit on a desk and restart by itself).
I can now see other people talking about it, but it would be good to establish just how big a problem there is and perhaps work out how/why it's happening?
jonmorris said:
I meant to create this thread a while ago, but thought it was now time to do so given the fact I'm getting 2-3 reboots per day, and doing lots of different things.
The last reboot was just as I begun to upload a YouTube video, but it can happen when doing anything - or when doing nothing (as in it will sit on a desk and restart by itself).
I can now see other people talking about it, but it would be good to establish just how big a problem there is and perhaps work out how/why it's happening?
Click to expand...
Click to collapse
Have done a factory reset? I've seen a few reports of reboots and soft-reboots and it could very well be user installed apps, settings and other stuff causing it.
Try a full factory reset and install the most "needed" stuff only. Try it for a day or two.
Sent from my C6903 using Tapatalk
I'm really not keen on doing that if I can help it. I'd sooner wait for an update, or someone figuring out what is causing the problem if there's a workaround temporarily.
Over the years I've done loads of resets and reinstalls, only to find it doesn't fix the problem and just wasted hours of my time.
Getting the random reboots as well. On a couple of occasions I had a running out of memory message just before reboot. Nothing installed I didn't have on previous Samsungs with no issues.
Sent from my C6903 using Tapatalk
travisb said:
Getting the random reboots as well. On a couple of occasions I had a running out of memory message just before reboot. Nothing installed I didn't have on previous Samsungs with no issues.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I've been at an exhibition today and it was quite embarrassing (and frustrating) to have it crash twice. Once when uploading the YouTube videos (as mentioned) - which fortunately resumed okay, and then later when I was trying to watch the Apple event (via The Verge).
One thing I've noticed from the beginning, is that changing settings sometimes required a reboot to take effect
Sent from my C6903 using Tapatalk
I'm not expecting much, but I'm now downloading the Central Europe FTF and will flash that to see if it makes any difference at all (currently on commercial/journalist version).
Anything I can try that won't force me to start from scratch has to be worth it.
http://www.xperiablog.net/2013/10/22/minor-xperia-z1-update-14-1-g-2-259-certified/
looks like a minor bug fix fw is coming real soon.
In the interest of scientific research (and reading the high CPU thread) I've backed up my sd card, re formatted it and just copied the music and DCIM folders back in, to see if that makes any difference. Card is genuine SanDisk 32gb class 10 card. Watch this space.
Sent from my C6903 using Tapatalk
Gitaroo said:
http://www.xperiablog.net/2013/10/22/minor-xperia-z1-update-14-1-g-2-259-certified/
looks like a minor bug fix fw is coming real soon.
Click to expand...
Click to collapse
Good news. Some weird stuff happening here.
Latest issue was the phone vibrating solid when pinch zooming (in or out) which was rather annoying!
jonmorris said:
Good news. Some weird stuff happening here.
Latest issue was the phone vibrating solid when pinch zooming (in or out) which was rather annoying!
Click to expand...
Click to collapse
Glad to see Sony keeping up with the updates
I have the same problem with the Z1. Also on ...257 and using 4G/3G. On the old firmware the phone hard-crashed several times and needed at 'hard-reset' at the simcard. But that happens not now - only 'soft restarts'. But very annoying. It happens both when using the phone and when its idle (in the night for example it restarts several times). You can see the restarts in the log on the phone.
I have some 'old' samsungs and they almost never restarts (sometime app's closes - but thats different) . I didn't expect such an unstable product from Sony when it's so expensive.
The value doesn't matter. It's just a silly bug that they need to fix quickly. I fear it will be a few weeks potentially for us to get it.
jonmorris said:
The value doesn't matter. It's just a silly bug that they need to fix quickly. I fear it will be a few weeks potentially for us to get it.
Click to expand...
Click to collapse
I've not had a single random restart.. I've been on Global LTE firmware for a week and have just changed to Central Europe one.. Will report if anything happens...
Two this evening with central Europe firmware, so clearly need new version ASAP. It's almost getting to the point where I can't use it because reset will happen at any moment.
Yes, also had 2 in last 30 minutes. So sd card reformat not a cure.I've contacted @SonyXperiagb on Twitter to see if they are aware of problem.
Sent from my C6903 using Tapatalk
it is a bug on sony fw and appear on google 4.1 - 4.2 android. it has something to do with wifi sleep power policy and wakelocks, im not sure. I had experience this problem with many devices on 4.1 and 4.2, include samsung ones. The easiest way to fix is to reset to factory and trace back your steps, anything to do with wifi (auto update, auto upload) is the culpit. Or if you can remember, try to trace back so you dont have to factory reset .
on .534, i had this problem when turning on update via wifi only in update center settings, get sod and constant restarts. disable it does not help, only to find out has to reenable again backlight optimisation.
Good luck!
I don't think that's it. Just need to wait for fix. Didn't have problem before this update, ever.
jonmorris said:
I don't think that's it. Just need to wait for fix. Didn't have problem before this update, ever.
Click to expand...
Click to collapse
the fix are only those i told , further more updates will fix it but you can do it manually your self
A factory reset with a whole world of pain, and no guarantee it won't still mess up, isn't really a solution to me. Sorry!
Is anyone else suffering from audio stutter since the update to 4.3 and if so has anyone found a solution? I've read about lots of issues with other devices and music stutter on 4.3 but can't find anything on the Xperia Z.
I'm running the Generic UK rooted update from the Android Dev section, and I have narrowed the stutter down to when the device is sleeping.
At first I had my headphones (MDR-1RBT) on bluetooth and assumed it was that, but after connecting them with the wire the issue continued. Next I switched to Walkman player instead of the Google Music one (all music on both apps is local, on the SD card, not streamed).
The issue still continued, however, every time I wake the device the stuttering stops. I ran CPU spy to see what is going on and noticed my device has never entered deep sleep since the update (is anyone else seeing this also?)
One suggestion was that Wifi optimisation could be the issue, I turned that off, but it didn't help, and even turning wifi off doesn't seem to help, but wifi on seems to make it worse I'd say.
It's driving me insane and I use my phone/headphones to listen to music several hours a day and can't deal with the stutter, I'll have to go back to 4.2.2 unless I find a solution.
alias_neo said:
Is anyone else suffering from audio stutter since the update to 4.3 and if so has anyone found a solution? I've read about lots of issues with other devices and music stutter on 4.3 but can't find anything on the Xperia Z.
I'm running the Generic UK rooted update from the Android Dev section, and I have narrowed the stutter down to when the device is sleeping.
At first I had my headphones (MDR-1RBT) on bluetooth and assumed it was that, but after connecting them with the wire the issue continued. Next I switched to Walkman player instead of the Google Music one (all music on both apps is local, on the SD card, not streamed).
The issue still continued, however, every time I wake the device the stuttering stops. I ran CPU spy to see what is going on and noticed my device has never entered deep sleep since the update (is anyone else seeing this also?)
One suggestion was that Wifi optimisation could be the issue, I turned that off, but it didn't help, and even turning wifi off doesn't seem to help, but wifi on seems to make it worse I'd say.
It's driving me insane and I use my phone/headphones to listen to music several hours a day and can't deal with the stutter, I'll have to go back to 4.2.2 unless I find a solution.
Click to expand...
Click to collapse
+1
Yep. Same problem here.
Sent from my C6602 using Tapatalk
Same problem as well, except it does not stop when I wake the device - the stutter still continues no matter what. I'm using the default Walkman app as well as have tried other music apps, but same problem throughout
no issues with poweramp. try apollo or some other player (not walkman or play music) and see if that helps.
No stutter here with walkman app.
But if I run the Walkman app, the accu usage shows that Mediaserver sucks my Battery,
+2
Same here and for @AngelBob
It's annoying and I've not been able to find a solution to it yet...
I went back to 4.2.2, so i have one question: can someone test if stuttering are not present using PowerAmp?
Thanks all
+1
I believe it's kernel related. We had this exact issue in the past and Sony fixed with am update.
CM builds are also suffering audio 'stutters' so I think it's something we're going to have to live with until Sony push a new kernel/libs
Sent from my C6603 using Tapatalk
AngelBob said:
CM builds are also suffering audio 'stutters' so I think it's something we're going to have to live with until Sony push a new kernel/libs
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
You're right, after investigation, I can say with some certainty that the cause is the new bluetooth stack Google switched to in 4.3. I tried modifying some of the bluetooth configs but it made no difference. It'll need a fix to those libs and perhaps a kernel update as you say.
I don't know if it's been fixed in 4.4 yet, since I no longer own any nexus devices, but I wouldn't count on us getting the fix any time soon unless Sony decide to resolve it themselves.
alias_neo said:
You're right, after investigation, I can say with some certainty that the cause is the new bluetooth stack Google switched to in 4.3. I tried modifying some of the bluetooth configs but it made no difference. It'll need a fix to those libs and perhaps a kernel update as you say.
I don't know if it's been fixed in 4.4 yet, since I no longer own any nexus devices, but I wouldn't count on us getting the fix any time soon unless Sony decide to resolve it themselves.
Click to expand...
Click to collapse
I would have agreed, but for those of us not using Bluetooth still suffering the same effect
Sent from my C6603 using Tapatalk
AngelBob said:
I would have agreed, but for those of us not using Bluetooth still suffering the same effect
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
You're right, I tested wired and it's the same problem.
In this case, I'm going to put the issue down to kernel and power save/sleep mode. I switched straight back to 4.2.2. I really like the new UI, but I can wait, hopefully 4.4 fixes it. I wouldn't count on a maintenance release from Sony before 4.4
I had this problem on 4.2.2 ROMs when I had Wi-Fi on. I think it was probably due to media server scanning for other devices over Wi-Fi network. It was going crazy when I was at uni as there were so many devices around me. Had to keep my wi-fi disabled just to listen to music.
You guys getting the same issue?
Sent from my C6603 using Tapatalk
kamalmawa said:
I had this problem on 4.2.2 ROMs when I had Wi-Fi on. I think it was probably due to media server scanning for other devices over Wi-Fi network. It was going crazy when I was at uni as there were so many devices around me. Had to keep my wi-fi disabled just to listen to music.
You guys getting the same issue?
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Unfortunately not, even worth wifi disabled it still happens, makes no difference.
It seems to be kernel related, perhaps something to do with cpu states or such because it only happens for me in sleep mode, it also happens when apps install so could be I/O related.
I'm starting to think sony rushed the Z 4.3 update, the T leak does not suffer this bug and it also has transparent nav bar by default!
Sent from my C6603 using Tapatalk
Can we use bluetooth/a2dp libraries from other devices or versions of Android?
For example can we put Xperia Z 4.2.2 bluetooth files into the Xperia Z 4.3 firmware?
Thanks
On 4.3 Drummerjeds stock pre-rooted and deodexed rom with PXA23 I don't get any stutter when streaming. Is it only a problem with music stored on the device? (Doesn't appear to be an issue either with music from Google Play music stored on my external card). Just wonder if it could be related to my having the kernel tweaks on Power Guard Pro running in learning mode, if it's related to a problem in sleep mode?
Just want to inform you guys that I have no stutter whatsoever with walkman but I'm on the official C6602 4.3 ROM, but the screen sometimes flickers in chrome, the most annoying bug so far
mervluk said:
On 4.3 Drummerjeds stock pre-rooted and deodexed rom with PXA23 I don't get any stutter when streaming. Is it only a problem with music stored on the device? (Doesn't appear to be an issue either with music from Google Play music stored on my external card). Just wonder if it could be related to my having the kernel tweaks on Power Guard Pro running in learning mode, if it's related to a problem in sleep mode?
Click to expand...
Click to collapse
I only use Streaming from Play Music, issue still appears,
Though I am leaning to the kernel going to sleep causing the issue,