Xperia E3 Running Slow - Sony Xperia E3

Hi, I'm having issues with my Xperia E3 running slow, especially when typing and scrolling. Im rooted with no custom roms, up to date firmware. I've factory reset my phone several times and while it does running better, i'll add a few apps and link most things to SD but not move them to SD. Over the course of the week it'll start running slow again. I'll clear cache and other unnecessary things that may slow it down but nothing seems to work. Is there any way to speed it up whether it be using a custom rom or some other trickery. Thanks.

Update your kernel to one with ZRAM support, so you will use better your 1gb of RAM.
Try vinay's kernel.

Related

[Q] Xperia E Dual: About CWM and ROM

Hello fellas,
My girlfriend have a Xperia E Dual on stock JB and everything is slow, laggy and freeze sometimes. I tried disabling some apps, removing them from RAM, managing start up applications and nothing seems to be very effective.
I have a Galaxy Tab 2 and also had some lag on stock ROM and thanks to the xda community which offers plenty of ROM's for this device, I'm running a perfectly stable version of CM of Android 4.2.2 and have no lags since.Then, I came to the Xperia E forums to find a ROM to give a better performance to the phone. But for my surprise there's not an official version of CM and neither much stable options for this phone, and also I'm kinda lost in this forums due to amount of phones in the same sub forum.
My first question is, which is the most stable and will give me a better performance for the Xperia E Dual?
How is the easiest and complete method for installing? In my tablet I had to root it, install CWM from Play Store, put the .zips in the SD card and flash through CWM. But I have seen that for this phone the process is quite harder, something related with Fastboot and some cmd commands
Can someone provide me some links and fool-proof information to flash a new ROM?
Thanks in advance and greetings from Brazil!
First, Consider Rooting your phone through here http://unlockroot.com
After that unlock your bootloader here http://unlockbootloader.sonymobile.com
When doing the rooting I'm sure you already know that Enabling USB debugging and Unknown Sources is a must
Then install CWM and install CM, And of course CM 10 is unofficial build but still works fine and there is a slight error about the Signal carrier labeling "Unknown"
Please hit thanks if i helped

Lag in Lollipop (ven after wiping cache)

Hi there.
So I've been on lollipop for about 4 and a half months. I've factory reset phone after upgrade from 4.4 to 5.0
But now I'm experiencing lag issues. Litereally every app starts slowly. Also UI is slow in general. When I drag down menu it's not responsive. You can tell the difference. I've tried to speed things up by going into recovery and wipe cache, but lag is still there.
I'm using stock 5.0 Lollipop here. Is it time to try CyanogenMod or any other stable rom? Or just install new kernel? If switching to CyanongemMod or custom rom, can someone suggest which one?
I choose Moto G in the firset place because of the awesome speed despite harsware because of the stock firmware being trimmed down of nasty apps. Hope there is solution without me switch to another rom.

Xperia Z3 5.1.1 - random system restarts

Hi guys,
My girlfriend purchased a brand new Xperia Z3 D6653 not too long ago (about 2 months ago?). I flashed the 5.1.1 pre-rooted firmware for her and it's working fine and all but it does a random reboot every day or so, at random times, with random applications.
I have tried 2 different pre-rooted 5.1.1 firmwares already (yes, the correct model D6653 as well) and it still does it. The System Incident reports don't really say much (in fact you only see details about when it crashed, nothing else), and it seems like Google Play Services is the only thing mentioned in the Application Report.
The same thing also happened (more frequently) when she was on the 5.0 pre-rooted firmware. I'm not sure why, I haven't unlocked the bootloader or anything, it's just stock pre-rooted ROM, that's it. I haven't flashed any other ROMs other than the official pre-rooted ones.
Furthermore, before I flashed the 5.0 and 5.1 firmware for her, the phone came with Android 4.4.4. She used it for a month and reported several crashes as well, so that's with the original factory firmware, unrooted, unmodified etc.
She doesn't run any dodgy or random apps, she's just a typical girl that use Facebook and texting, that's pretty much it. I've done a lot of research on this issue and it seems to be quite common, however there isn't really a solution to this. The same apps she currently use never caused any issues on her older phones.
Also in case anyone asks, the only reason I flashed the pre-rooted 5.1.1 firmware for her is because it makes it easier for me to manage her phone (with Teamviewer, you can remote into the phone as long as it's rooted). Also, I get to backup her phone and do tests etc, makes it easier for me.
Also, I'm not using any custom kernels or overclocking the CPU etc. Everything is just stock but rooted.
Could this be caused by a hardware fault in the phone? I'm not sure what else I can do and would appreciate some suggestions.
Nobody have this issue??
Well, how about you try to flash a full, clean, stock ROM, don't root it, don't install any unnecessary app and see where it goes? If the issue persists, try getting a logcat from the phone and we can take a look at it. If it works fine after returning to stock, there might be a problem with the ROM or some apps you are using.
If it really is Gapps that are causing all the trouble, go to APKMirror and download the latest apps available (Play Services, etc) and see where it goes.
As mentioned already, prior to flashing anything, my girlfriend was running a completely stock, factory version of the phone. It came with Android 4.4.
I could flash a completely stock 5.1 ROM but was hoping that someone would share their experiences or a potential solution to this, considering this is quite commonly asked. I would also like to avoid doing this if possible, because if I were to go back to rooting the device, I'd have to downgrade to v4.4 pre-rooted, then flash to 5.1 rooted with custom recovery. It's just a lot of work for a simple testing that could be answered by others if possible.
Anyway, she didn't have any apps installed other than Facebook and Whatsapp, that's it. I might test with GAPPS and see how it goes, but I thought I'd ask here in case someone knows it's definitely a hardware issue or something else.
i would definitely give a pure stock 5.1.1 a go. I used to get the random reboots on the previous versions but i no longer have such issue.. Make sure you do a clean wipe and do it a few times.
Hi all, it's been a while but I thought I'd post an update and share what I've found/learned so far....
Basically, I'm still getting the frequent random reboots. I've tried reflashing the ROM and also tested out the latest .232 pre-rooted stock ROM, still getting the same issue. I've noticed that other than Google Play Services, sometimes Gapps will crash as well. But most of the time, there's nothing reported in the system or application crash logs. I've tested with everything running as stock, no additional apps installed. I then decided to flash the Minimal GAPPS 5.1.x and that sort of made the phone a bit more stable, but still reboots randomly every now and then.
Later on, I decided to try a custom ROM that still works on a locked bootloader. I found this here:
http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
The chef has provided a .232 firmware for you to flash in recovery, as well as the ROM base for the D6603 model. Mine is a D6653, but luckily the chef has also provided a D6653 patch for you to flash as well. I've flashed the ROM like so:
1. Wipe everything except my external microSD in TWRP. So basically, wipe system, data, cache, dalvik, internal storage etc.
2. Install .232 firmware.
3. Install v10.5
4. Install v12.0
5. Install D6653 v5 patch
It boots up fine but after using it for a while, I still get the random reboots. What's interesting is that I've also tried without flashing the D6653 patch, which essentially means I'm running just the D6603 base ROM on my D6653. It works, but still crashes as well. I just found it quite surprising that a D6653 could run a D6603 ROM, but it does make sense considering the main differences is just the baseband/frequencies.
Anyway, I later on decided to flash the pure 5.1.1 stock ROM, still getting the crash. Again, everything is tested on pure stock, no additional apps etc installed.
I'm starting to think perhaps this is a hardware issue on my phone?? I noticed that sometimes, my screen will show a bit of tearing and then it'll crash not long after. BUT, I also know that as soon as gapps or google play services crash, the phone will crash not long after as well.....
In fact, I later on used Titanium Backup to convert Google Play Services from a System to a User app, the phone will just boot into the lockscreen and then restart every time. This is a bit ridiculous because I've done this several times on other phones before and they never had such an issue. Of course, I'm not saying I always run Google Play Services as a User app, but that was just for testing and I honestly don't think it should cause a bootloop just because of that. I've also cleared dalvik and cache by the way, so it doesn't make sense that the phone boots into the lockscreen and then just restarts randomly.
I haven't tried uninstalling Google Play Services completely, but at this point I'm back to square one as I've exhausted pretty much all my options and it's been a complete waste of time. I'm beginning to hate this phone more and more. The only thing left is to unlock bootloader and play with other custom ROMs. But yeah, flashing the .232 firmware didn't fix it, AND flashing pure stock 5.1.1 Android didn't fix it either...
Just wondering if others have the same issue and any ideas what could be causing it? If I provide some Logcat logs, would someone be kind enough to look into this for me?
Update:
I'm still getting the random reboots and I think it's very likely to be hardware related. But sometimes also a bit related to software, specifically with Google Play services. I've had more time to test out a few things since my last update, they are as follows:
- Tested complete stock 4.4 ROM without root. Still crashes every now and then, but not as much compared to 5.0 and 6.0 (doesn't matter if it's stock or custom ROM).
- Finally gave in and unlocked bootloader (backed up my DRM keys of course). I thought perhaps that the stock Sony roms (and even the stock-based Sony custom roms) have issues for some reason. They are all the same base, so I thought I'd do a fair test by trying a completely different based rom, such as AOSP. I've used CM 1.2.1 nightly here:
forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201/page117
And yes, I know that nightly have bugs, but the nightly build as of 2016-03-03 seemed pretty stable according to most users. I've tried various other AOSP based roms and stock based Sony roms (for unlocked bootloaders) and they all produce crashes.
I've flashed custom kernels as well and updated my recovery to TWRP 3.0, but all the same results. On all of the custom ROMs I've flashed, the only thing I've done was setup my Google account (so I have my contacts and Gmail) and that was it. No other apps installed. I wanted to limit the environment down to just the stock setup of the ROM itself, as this helps me rule out any potential bugs caused by 3rd party apps.
Having done all of the above and still resulting in crashes, it's safe to assume that this is most likely unrelated to the software, but hardware. I've noticed that sometimes when I scroll a page too fast and move it up and down with my thumb, the screen will freeze and restart.
However, sometimes I will get crashes related to Google Play Services. Anything that relies on Google Play Services will crash randomly. If you re-open the apps, it just crashes again. If you force stop the app and open it, still crashes. The ONLY fix is to restart the phone. I have tried flashing different GaPPs, starting with the pico and nano versions, as well as the ones recommended by the ROM chefs. Still the same result.
So the conclusion is, I haven't really gotten anywhere with this annoying issue. There's definitely an issue with the phone somewhere, maybe a bit of software related, but mostly hardware.

User modifications and OTA updates

My mate 7 is rooted and with custom recovery (TWRP) instaled. Due to these modifications I am not able to get OTA updates from Huawei.
In order to get access to them, again, do I have to unroot and instal stock recovery , or can I only instal stock recovery and keep phone rooted?
many thanks
You need to unroot and instal stock recovery.
I decided, seeing as so many mate7 owners are bricking their phone, I will leave mine with root and CWM on kitkat and it can't get an OTA that will spoil it.
If there were a decent recovery flashable ROM I'd have a current backup and try it, but there's nothing out there with full functionality so kitkat stays.
The phone works really well as is. The mods I've applied give good performance and function. Why try to reinvent it just to say I have a newer OS?
RobboW said:
I decided, seeing as so many mate7 owners are bricking their phone, I will leave mine with root and CWM on kitkat and it can't get an OTA that will spoil it.
If there were a decent recovery flashable ROM I'd have a current backup and try it, but there's nothing out there with full functionality so kitkat stays.
The phone works really well as is. The mods I've applied give good performance and function. Why try to reinvent it just to say I have a newer OS?
Click to expand...
Click to collapse
What mods have you applied?
I'm running 5.1.1 on my gold model and found quite a significant performance boost. On KK I was experiencing choppy UI more often than not. The battery has slightly improved as well. Not that it's bad in any way running KK though...
I would kill to get a stock ROM (or a CM ROM) running on this phone, or even just Xposed. But alas, EMUI just won't budge.
Scruffykid said:
What mods have you applied?
I'm running 5.1.1 on my gold model and found quite a significant performance boost. On KK I was experiencing choppy UI more often than not. The battery has slightly improved as well. Not that it's bad in any way running KK though...
I would kill to get a stock ROM (or a CM ROM) running on this phone, or even just Xposed. But alas, EMUI just won't budge.
Click to expand...
Click to collapse
On KK B130 I have unlocked bootloader, root, CWM recovery, de-bloated apps and launcher, installed Viper4Android, xperia keyboard and an old version of xposed withe some modules. It has other stuff too. Runs fast. No urgent need for a new ROM. Modded a lot to be really simple, lol. It is a pleasure to use.
For choppy UI, I enabled the setting to force GPU rendering in 2D applications. It's in developer options. You can also reduce or turn off animations.
I've installed a Kernel adjusting app too. Changed some settings, made the phone respond faster and read ahead performance increased. This made bluetooth streaming perform a lot better and it's just nice to use.
The stock governor settings keep the phone on the low speed cores as much as possible and this kills UI performance and makes UE disappointing. I also removed the Huawei launcher after installing Smart Launcher Pro.
I'm thinking of removing the OTA update app and permanently run B130 with no chance of updating it without use of CWM recovery to flash it.

Problem with any ROM's after reboot

Hello. After install Pixel Experience, LineageOS, VoltageOS, EvolutionX or any new ROM my Redmi 6 Pro work perfectly. Stable, smooth and fast.
But when i reboot my phone, loading is very very long. Sometimes few minutes.
After this main screen show up but without apps icons. Only wallpaper. Still loading.
After 10min i have notifications about
"(app name) stop working"
For example, "google store stop working" etc.
After 20min ROM is ok but not perfect. Laggy and not stable. I dont know why...
I know. I need new phone, cus this is old crap. But maybe....
Maybe is a little solution. Maybe someone has this problem and fix this...
Please help.
Is the phone as slow if you run twrp first and then ROM?
Did you wipe the internal memory before installing the custom ROM?
Sometimes TWRP stuck on screen but this commands fix this:
fastboot format cache
fastboot format userdata
Click to expand...
Click to collapse
Im using lates version on TWRP.
And when i first time want install new ROM cant wipe old files. Need switch ext4 to ext2 and fix partition and again switch ext4.
So yes. Evry new ROM i wipe evrything. Format all data, fresh new files.
Try using the version of TWRP that was released just before the ROM was released, as the developer tested the installation on such a version. A newer version of TWRP is not always better than an older one.
Since you didn't answer directly, I assume you wiped the Internal Storage.
Yes i wiped Internal Storage.
TWRP version is good as recommended.
I think i need new phone.....
sniper512 said:
(...)
I think i need new phone.....
Click to expand...
Click to collapse
Don't give up so easily. Try going back to stock ROM and see how the system behaves for a longer period of time. If OK, flash the custom ROM again.
I try stock ROM and its slower then anything, but works fine. No problems.
I think is something like android version compatibility. Android 9 works perfect. Android 11 or 12 with problems and 13 even worse then togheter.
I need fast and stable ROM, but now Pixel Experience looks great. Functionality and ease of use is better then EvolutionX or LineageOS. This is simple perfect.
Second i think is something about RAM problem on init.
After long boot RAM ussage is 3.95/4GB
Evrything is slow becouse of full RAM.
But after install fresh ROM ussage is 2,7/4GB

Categories

Resources