Hi
My M2 is running on build 18.6.A.0.182 lollipop and tried to downgrade to kitkat 4.4.4 using flashtool. But it resulted in a bootloop.
After that using PC companion I repaired it back to 5.1.1 and got it back working .But now the camera is showing some white noise lines while shooting pictures on indoors where there is a bright highlighted area. This happens only in HDR mode. One time I saw it also in Superior auto mode where the auto scene selection was shown as Backlight HDR. So is this a sensor problem or a software issue?
I had a backup firmware of lollipop that I copied from C:\ProgramData\Sony Mobile.
I copied that to the location before repairing it using PC Companion so that the PC Companion wont download the entire firmware which is about 1.1 GB and there by saving my limited data plan. Is there a problem by copying the firmware before repair process?
zankdroid said:
Hi
My M2 is running on build 18.6.A.0.182 lollipop and tried to downgrade to kitkat 4.4.4 using flashtool. But it resulted in a bootloop.
After that using PC companion I repaired it back to 5.1.1 and got it back working .But now the camera is showing some white noise lines while shooting pictures on indoors where there is a bright highlighted area. This happens only in HDR mode. One time I saw it also in Superior auto mode where the auto scene selection was shown as Backlight HDR. So is this a sensor problem or a software issue?
I had a backup firmware of lollipop that I copied from C:\ProgramData\Sony Mobile.
I copied that to the location before repairing it using PC Companion so that the PC Companion wont download the entire firmware which is about 1.1 GB and there by saving my limited data plan. Is there a problem by copying the firmware before repair process?
Click to expand...
Click to collapse
Did you wipe clean the device when trying to downgrade to KK you must wipe user data and cache in flashtool when going from lollipop to KK and vice versa I'd try another software repair as it'll re-install the whole ftf from scratch. Pretty sure sony pcc will always download the latest available firmware from sonys server's before completing a software repair don't think there's anyway round it. It should fix the camera issue
Hi
Solved the problem. Yesterday I downgraded to KK using flashtool 0.9.18.6 . Previously I used 0.9.19.8, in which there was only an option to clear user data and not clear cache.
Flashtool 0.9.18.6 provided both the options and I also read on an XDA post that 0.9.18.6 is best suited for Xperia M2.
Now I am on kitkat 4.4.4 build 18.3.1.B.1.8. Now the camera issue is gone. No more white noise lines on camera pics. Focusing got faster and better. HDR video mode now equalizes bright and dark areas more efficiently as before. In Lollipop videos shot were wobbly with Steadyshot turned on. That was not a problem with KK then and now. Also I got back about 1 GB of Internal memory that was taken up by lollipop .
I love KitKat. But still I miss Lollipop for it's notification design. Can I get a full Lollipop interface on KK without rooting? . I have no idea about rooting modding and all.
zankdroid said:
Hi
Solved the problem. Yesterday I downgraded to KK using flashtool 0.9.18.6 . Previously I used 0.9.19.8, in which there was only an option to clear user data and not clear cache.
Flashtool 0.9.18.6 provided both the options and I also read on an XDA post that 0.9.18.6 is best suited for Xperia M2.
Now I am on kitkat 4.4.4 build 18.3.1.B.1.8. Now the camera issue is gone. No more white noise lines on camera pics. Focusing got faster and better. HDR video mode now equalizes bright and dark areas more efficiently as before. In Lollipop videos shot were wobbly with Steadyshot turned on. That was not a problem with KK then and now. Also I got back about 1 GB of Internal memory that was taken up by lollipop .
I love KitKat. But still I miss Lollipop for it's notification design. Can I get a full Lollipop interface on KK without rooting? . I have no idea about rooting modding and all.
Click to expand...
Click to collapse
Not that I'm aware of and the one I used on KK that was almost like lollipop needed root and superuser mod anyway. Kk sucks compared to 5.1 lollipop in every way but each to their own and all that and rooting 5.1 is also easy now with linuxcts root tool almost a one click job compared to how it was
Ok. is there any way to integrate kitkat camera firmware to lollipop 5.1.1 ?. Or any better camera firmware for M2 in lollipop? . Camera and Internal storage are the main gripe I have with lollipop.
Also I encountered another problem in lollipop recently as I was changing pattern lock. I forgot the pattern lock and it never asked for Google password for recovery. I had smart lock enabled with face detection. It didn't even asked that and I had to perform an ADM erase. Why does this happen with lollipop.
I would like to know about Deodexing. What is that? Is it like rooting? . Will it compromise security?.
In this link http://forum.xda-developers.com/xperia-m2/development/stock-xperia-m2-deodex-patch-t3243891 , it is mentioned Sony shipped the stock with corrupt odex files. Is there any issues with Sony stock firmware?
zankdroid said:
Ok. is there any way to integrate kitkat camera firmware to lollipop 5.1.1 ?. Or any better camera firmware for M2 in lollipop? . Camera and Internal storage are the main gripe I have with lollipop.
Also I encountered another problem in lollipop recently as I was changing pattern lock. I forgot the pattern lock and it never asked for Google password for recovery. I had smart lock enabled with face detection. It didn't even asked that and I had to perform an ADM erase. Why does this happen with lollipop.
I would like to know about Deodexing. What is that? Is it like rooting? . Will it compromise security?.
In this link http://forum.xda-developers.com/xperia-m2/development/stock-xperia-m2-deodex-patch-t3243891 , it is mentioned Sony shipped the stock with corrupt odex files. Is there any issues with Sony stock firmware?
Click to expand...
Click to collapse
They use different frameworks from KK to LP so it wouldn't be possibly to port over. I thought the M2 had an update that fixed your camera problems?
Deodexing is basically a method to allow for modifications to the system and user apps. Sony accidentally/purposely prevented deodexing, so an alternative method is needed. It's harmless on its own though.
zankdroid said:
Ok. is there any way to integrate kitkat camera firmware to lollipop 5.1.1 ?. Or any better camera firmware for M2 in lollipop? . Camera and Internal storage are the main gripe I have with lollipop.
Also I encountered another problem in lollipop recently as I was changing pattern lock. I forgot the pattern lock and it never asked for Google password for recovery. I had smart lock enabled with face detection. It didn't even asked that and I had to perform an ADM erase. Why does this happen with lollipop.
I would like to know about Deodexing. What is that? Is it like rooting? . Will it compromise security?.
In this link http://forum.xda-developers.com/xperia-m2/development/stock-xperia-m2-deodex-patch-t3243891 , it is mentioned Sony shipped the stock with corrupt odex files. Is there any issues with Sony stock firmware?
Click to expand...
Click to collapse
Camera on 18.6.A.0.182 is fine, if rooted with a few tweaks even better(I'm using cam2 ui with a combination of KK+L settings+z5+x framework files). The corrupted services.odex file shipped with 5.1 on M2,t2u and c3 only these three devices are affected(funnily enough the three not originally planned for 5,1) basically it means deodexing the stock 5.1 firmware is impossible and xposed won't work. To get round this @Gaurav007 and Co ported z1c + z2(the better port) deodexed system+framework this brings ultra stamina bravia engine x-reality(only on locked Bootloader) assertive display(must be edited to correct M2 screen size) and gives the m2 z2 features I've been using it since just after 5.1 was released no problem at all I highly recommend it for a good base to start with if on stock and want xposed, the only bug is just a annoying toast message when turning off Bluetooth it actually works fine as I use it for my sbh20's. There's also z5 style rom by @linuxct this also uses gauravs z1c port as it's base but is heavily de-bloated(to much if you ask me)With root and a few tweeks the m2 is a good device. I'd have a read through the threads in here you'll find all the information you need any problems post in here.
Related
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)
Hi!
I need help regarding my phone Sony Xperia Z3 D6653 - I followed the procedures properly on how to unlock and root the phone via
http://theunlockr.com/2014/10/08/how-to-root-the-sony-xperia-z3/
and
http://forum.xda-developers.com/z3/orig-development/d66xx-cwm-based-recovery-6-0-4-7-root-t2890116
it went well with no errors at all but after the reboot and flashing SuperSU, the wifi won't turn on anymore, I tried everything in the advanced options on wifi but it didn't make any difference at all, Bluetooth, LTE and Mobile Data Works fine, also tried wiping data (factory reset the thing) but still no dice.. please help... thanks!
Edit:
Even the Wifi hotspot doesn't work, my only option left is to flash it back to stock rom
I have the exact same issue. Followed the same processes and with no funny vibrations or anything but WiFi won't turn on.
---------- Post added at 10:05 AM ---------- Previous post was at 09:10 AM ----------
Fixed for me:
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
follow those instructions, using the LATEST img file. Works for me.
URGENT
dear KiDCady,
please help me to solve this problem. my WIFI can't turn on after rooting lock bootloader. I've tried to re-flash using other firmware. but the problem seems like did't solve.
best regard,
Chris
dark_blitz falow the link abow your text witch KiDCady provided. I hade same problem! I rooted my sony xperia z3 and after finishing with superSu my wifi and memory card wont work. i tried all sorts tricks, but nathing worked. Then i found this forum and clicked on KiDCady link, and thats fixed my problem - external memory works and wifi works beter then ever! Thanks KiDCady! you saved my day!:good::good::good:
i have the same problem
already follow the link witch KiDCady provided
but its still the same.
now i upgrade my OS using flashtool from kitkat to lollipop
im using Sony Xperia Z3 d6603 Android version 5.0.2 (lollipop)
nothing is happen wifi still unable to TURN ON
kudzjra said:
already follow the link witch KiDCady provided
but its still the same.
now i upgrade my OS using flashtool from kitkat to lollipop
im using Sony Xperia Z3 d6603 Android version 5.0.2 (lollipop)
nothing is happen wifi still unable to TURN ON
Click to expand...
Click to collapse
Do a full reflash of ROM with flashtool. It should fix it.
As i know, kernel handle the wifi, and if something is wrong in kernel this happens.
Since you are lockedbootloader if i am correct, i dont know why it has this behaviour.
But anyway, backup your things, and do Full reflash, let me know.
You said you are unlocked. Flash another kernel and test it.
TheTeslaCoil said:
You said you are unlocked. Flash another kernel and test it.
Click to expand...
Click to collapse
That or wifi module for that kernel.
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.
Hi all,
A little while ago I downgraded my Xperia M2 to Jelly Bean, so that I could get root access. So I now have 18.0.C.1.13 (central Europe) installed. Now I have decided that I don't need root access any more, so I'd like to get back on the standard OS rollout programme. The Sony update centre regularly reminds me that I can update. However, when I come to update it will download ok, but fails to install.
Any ideas what could be going on, and how to fix it? I could flash a new ROM, but that may not help. I'm wondering if it's unhappy about the region I used for the downgrade (I am in the UK) but it shouldn't worry about that.
Thanks for the help,
Neill
Just reflash the ftf via flashtool updates don't work with root as the system has been modified.
D2303 5.1lollipop customised NCB LB rooted Nuts t2u dual recovery bravia engine 2+x-reality debloated viper audio
No joy I'm afraid.
I upgraded to Kitkat this weekend, using an FTF file I found (unfortunately I can't post a link, as I don't have enough posts on this forum).
I then tried to upgrade using the Sony Update Centre. It downloaded ok, but when I pressed "install" I got the error message "could not verify download".
So, I then tried upgrading using the Sony PC Companion. Again the upgrade downloaded fine, but upon install I was greeted with something like "Could not upgrade, because there are customisations on your existing operating system".
I'm going to have a try with flashing lollipop now, but I don't have high hopes for being able to upgrade after that.
neill.bowler said:
No joy I'm afraid.
I upgraded to Kitkat this weekend, using an FTF file I found (unfortunately I can't post a link, as I don't have enough posts on this forum).
I then tried to upgrade using the Sony Update Centre. It downloaded ok, but when I pressed "install" I got the error message "could not verify download".
So, I then tried upgrading using the Sony PC Companion. Again the upgrade downloaded fine, but upon install I was greeted with something like "Could not upgrade, because there are customisations on your existing operating system".
I'm going to have a try with flashing lollipop now, but I don't have high hopes for being able to upgrade after that.
Click to expand...
Click to collapse
As Aidy said, you can't succeed with PC Companion if you have modified system (unlocked bootloader or root) so use Flashtool 9.18.6 for flashing, make sure you have all drivers instaled and also PC Companion and you can succeed. You can download latest ftf with XperiFirm that is built in Flashtool. You can root it with KingRoot (use Google how to change to SuperSu).
Good Luck!
Sent from my D2303 using Tapatalk
Ouch! That was a bit of a nightmare...
First things first, thanks for pointing me to XperiFirm, it looks like a great place for getting FTF files. It was not obvious what the XF button on Flashtool does. Equally, it's not entirely obvious how to use it. But anyways, it looks good.
I downloaded and flashed the 3 UK kitkat FTF file for the M2. Upon rebooting the phone got stuck on the 3 splash screen, and would not respond to any input (could not even turn off). I thought I had killed my phone. I had to wait an entire day for the battery to die. I have now reflashed a lollipop ROM I downloaded from the internet, and everything seems to be working ok. I'm going to be a lot more cautious about flashing my phone in future.
To power off phone you have 2 options :
1. There's a hole by simcard put some sharp pin in it and phone is off (well, if it's not connected to changer or use on pc )
2. Hold volume up + power button together at same time, you'll feel vibration (that will reboot phone) hold it little more until you feel 3 vibrations, now your phone is off.
Sent from my D2303 using Tapatalk
Three UK use sim free network unlocked devices(bootloader unlockable). So you're better off flashing customised UK no three splash screen or apps then this is what I've done but I'm using customised NCB instead.
D2303 5.1lollipop customised NCB LB rooted Nuts t2u dual recovery bravia engine 2+x-reality debloated viper audio
Thanks all for the help, much appreciated.
I got this problem on my camera results. The color and texture of the images produce is such a big difference before capturing and after it captured. Its quite annoying and disappointing to see such images not quite good in quality after the update to lollipop. Im using a stock rom with Build number 18.6.A.0.175 and says that its my latest rom, I dont receive any OTA update such as 182.
Is there someone who can solve this problem?
Thanks!
if you don't receive update, i think you have root.
if you have root, flash this: http://forum.xda-developers.com/xpe...ashable-camera-blobs-morpho-settings-t3281766
if you haven't root, flash .182 ftf to your phone via flashtool.
Still the problem
I've alredy flash that camera file zip via recovery but nothing has change, still the results are just like using old one which is the stock camera app of. 175. Help please
sorry for my bad english ?
It does work I've flashed it myself to get the updated files. Try clearing the data from all the camera apps and wiping caches