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.
Related
Hi guys, I have xperia Miro and I think when I changed SystemUI.apk with one like AOSP style with blue icons in status bar, and now when ever I turn off my phone it shows boot animation (actually pretty cool) and when I boot my phone after bootanimation it ALWAYS show text "Android is upgrading. Starting all apps." So how can I make that text dissapear? Maybe it was not systemui.all fault? I think that it may be even boot animation problem, its stock but I installed some in boot animation app (via gplay store) and when I tried to change bootanimation manually it doesn't change, so I had to change it back to stock via boot animation app.
Sent from my ST23i using xda app-developers app
I think that would be because the SystemUI is probably deodexed, and the rest of the ROM is odexed. So Android "optimizes" it every boot.
NSDCars5 said:
I think that would be because the SystemUI is probably deodexed, and the rest of the ROM is odexed. So Android "optimizes" it every boot.
Click to expand...
Click to collapse
Ok, how can I "odex" it? I am a real noob in android, and now when I lock the screen the clock is gone in statusbar, also flashed fly-on mod (gotta say that my miro is running like a beast now) and when I go to recovery (cwm) and click on reboot it says rom may flash stock recovery this can not be undone and when i click anywhere no, yes or go back it just reboots.. I believe that i kinda f*cked up my phone so the best thing would be to flash stock rom on it, i cant find any tutorial for flashing the stock rom with flashtool, and i also need .ftf files...
Edit: found a thread about ftfs but cant find flashtool every page says not found
Edit 2: found the flashtool version 0.9.13.0 on depositfiles, returned stock systemui (for now) and the android is starting is gone but the cwm problem is still there, and the clock hide problem too (i think that the clock should show even in lockscreen)...
jole1999 said:
Ok, how can I "odex" it? I am a real noob in android, and now when I lock the screen the clock is gone in statusbar, also flashed fly-on mod (gotta say that my miro is running like a beast now) and when I go to recovery (cwm) and click on reboot it says rom may flash stock recovery this can not be undone and when i click anywhere no, yes or go back it just reboots.. I believe that i kinda f*cked up my phone so the best thing would be to flash stock rom on it, i cant find any tutorial for flashing the stock rom with flashtool, and i also need .ftf files...
Edit: found a thread about ftfs but cant find flashtool every page says not found
Edit 2: found the flashtool version 0.9.13.0 on depositfiles, returned stock systemui (for now) and the android is starting is gone but the cwm problem is still there, and the clock hide problem too (i think that the clock should show even in lockscreen)...
Click to expand...
Click to collapse
Sure, see this: http://forum.xda-developers.com/showthread.php?t=1462648
Thanks But I solved it, original systemui already had its own .odex, I just moved it out of /system/app, but now the only thing left is the clock... Here's what I'm talking about:
As you can see I can't see the clock in top right in statusbar but on launcher I can... I think I somehow disabled it, but how? And I imported my custom boot animation (I have the same one on my tablet with bigger resolution) my frames end and then they go back, images are placed correctly... And I still have that cwm reboot bug...
Sent from my ST23i.
Uhmmmm. Little question: why do you want thr clock in your statusbar when it's already on the lock screen? ^^. It's normal on android to hide the notification clock on the lockscreen.
Have a nice day!
Sent from a bad phone
MatsPunt said:
Uhmmmm. Little question: why do you want thr clock in your statusbar when it's already on the lock screen? ^^. It's normal on android to hide the notification clock on the lockscreen.
Have a nice day!
Sent from a bad phone
Click to expand...
Click to collapse
Actually, this doesn't happen on stock. It does happen on CM/AOSP, however, so the mod might have disabled it.
Hi,
I am a new user for Android system (Sony Xperia L c2105 classic device) i root it and I have some problems.
1-unknow live wallpaper appear at the end (see attachment photo), I boot my phone on safemode the problem gone.
2-wpspin don't work fine.
3-bacon also don't work.
4-wifi-direct don't work no send or receive, I wait to receive accept notification but nothing done. Just a notification that send is failed. Tethering and hotspot working fine.
Wait for some solutions
Thanks.
reflash the stock ROM.
And use this guide if you need help
WiFi Direct is a really strange thing, because stock Android have bad implementation of that feature. It should work like in Touchwiz-based Samsung ROMs.
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.
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.