I've just got D2403 with KitKat 4.4.4. I wanted to switch the runtime to ART. Although I know where this option should be located, it seems to be missing on this phone. Is there any trick how to enable it, or have Sony decided to remove ART competely?
MazeGen said:
I've just got D2403 with KitKat 4.4.4. I wanted to switch the runtime to ART. Although I know where this option should be located, it seems to be missing on this phone. Is there any trick how to enable it, or have Sony decided to remove ART competely?
Click to expand...
Click to collapse
I've tried that when I got my Xperia M2, but, nothing come up. I believe that they disabled the ART Cache Runtime 'cause it wasn't fully developed. They included into Lollipop 5.0 Binaries which is fully based on it. So, you could try flash the Lollipop binaries if you want to enjoy ART Cache Runtime (?)
Regards!
This worked on my D2303
http://www.xda-developers.com/switc...-from-recovery-with-a-single-aroma-based-zip/
Thanks for your replies guys. I decided not to mess around with my xperia this way because it is actually my main telephone. When I move to another one I'll give the Switch D2A_RT tool a try.
Related
Below is my recent drama with technology. I would really appreciate any help or guidance anyone has for this poor novice. Thank you in advance.
Here is my story:
My first android experience was my xperia m2. With a bit of playing about I rooted it (using towelroot), installed super user, xposed, donkey guard and a bunch of other modules. As you can imagine for someone who is a novice and has no clue about coding, flashing, roms, ftf's, bootloaders, fastboots, anything like that. So I was quite pleased with myself that I could block permissons with donkey guard, and the look of my phone with gravity etc....
All was going well when I kept getting a "You have a system update" message telling me that a system update to 4.4 is now availible. So I allow it to install but it wouldn't work. So I figured that its because the phone is rooted, so I did a factory reinstall, flash whateveryou call it using sony pc companion. Once finished I tried to root again using towelroot but that didn't work, so I hunted all over the net to find a way of routing the m2 with 4.4 but wanted to avoid unlocking the bootloader as everything pointed towards that not being a good idea if you don't know what your doing. Nothing that I have found so far I can understand. So thats why I am wanting my old 4.3 back. I Was happy with it, but when I use pc companion to flash, it keeps putting the latest 4.4 software on which I cant seem to root easily (ie. 1 click solution).
Also, I bought an xperia Z2 tablet (SGP511 - 17.1.2.A.0.314) a few weeks ago and as you know they come with 4.4 as standard. i quickly found a 1 click root method, rooted the tablet the installed superuser, busybox, then xposed and donkey guard etc.
I activated donkey guard and other modules in xposed and restarted etc.
I found that donkey guard would not work, nor would most of the other modules. One more thing that I found was that whenever I would shut down the tablet it would boot straight back up again and had to use the force off button next to the sd card to turn it off. So I flashed it again and went through the whole procedure again thinking that maybe I hade done something wrong, but got the same result. I did find out though through ellimination that the shut down issue was being caused by donkey guard being active, so if I deactivated it in xposed no more reboots. I thought that theproblem was with donkey guard and went though the donkey guard forum, but later dicovered that other modules are not working too. So I am not sure if the problems the tablet, 4.4 software, xposed, or something totally different, but all I know is that I was happy when everything worked on the m2 with 4.3, hence why the thought of a downgrade (if I can do it) of the M2 and not sure what the hell to do with the tablet.
Please let me know your thoughts
All the best
Hi,
You can ask for help in your device section here,
> Sony Xperia M2 > Xperia M2 Q&A, Help & Troubleshooting
Good luck!
OS: Official 4.4.4
Device name: Xperia M2 D2303
Device Status: Locked BL, Not Rooted
Question: Can/How i change my runtime from DALVIK to ART?
Installing Lollipop.
Sorry, ART isn't available for KitKat in our phone(s).
CM11/12 builds are heavily bugged
ART isn't even working properly on high end phones, the whole idea of ART is still bugged, we supposed to get more speed with it, but it really isn't giving anymore speed
Well then I think ART work well on Nexus 6 and Nexus 9 only
Sent from my D2303 using XDA Free mobile app
We don't have ART in developer settings, but you can switch to ART using flashable zips, like this: http://forum.xda-developers.com/showthread.php?t=2713622 or this: http://forum.xda-developers.com/showthread.php?t=2707841 and mods, like this: http://forum.xda-developers.com/showthread.php?t=2550478
I did that, but my phone didn't boot. It was stuck at boot animation.
I have LiveBoot, which shows the phone's log during boot. It always showed me the log, except when I switched to ART.
I really want to try ART out, but since it doesn't work on my phone, I can't.
However you can try out for yourself, since I have mods that can cause problems (I uninstalled Xposed before switching to ART) and you can switch back to Dalvik using a different zip (I did that and my phone is working, but I still don't have ART).
I want to switch to a custom ROM, but only if it supports taking photos and recording videos and it is Lollipop, because I have Bravia Engine, XLOUD, and other Sony extras, that I like, but other ROMs don't support and Lollipop is the thing that would be worth it for me.
Good luck!
Head over to my art thread, duh? I made one especially for our phone
http://forum.xda-developers.com/xpe...-rom-trick-t2966765/post57355259#post57355259
I have the D2203 with KK 4.4.4 - 18.5.C.0.19 - rooted
the option system icons in settings which lets you remove the + icon for stamina mode on the right next the battery and other icons is missing.
I really would like to know why it is missing and how I can get it back.
Thank you in advance.
I realized that my friend's M2 has it, and I was surprised to see that the E3 doesn't. But I didn't really mind as it isn't one of my main concerns, and because I no longer have stock xperia firmware installed.
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
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.