Related
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
benoitm974 said:
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
Click to expand...
Click to collapse
I have same problem in zombie panic kernel v 1.59 and v 1.61.
after i update to v 1.62, i don't had problem reboots. and everything it's ok.
Problem occurs usually when:
I use the phone for 10/15 minutes, that is running music or radio, or using the phone, like surfing and installing app from market.
I'll try the new 1.63 ...
Benoit
Sent from my U20i using xda premium
Hi, No reboots for me 4 days into 1.63+2.1, I did similar process only difference is I use clockworkmod, someone else will have to confirm but I remember a while back all the roms where coming out with "no longer supporting xrecovery". As said dont know might be nothing but everyone seems to use clockworkmod now for flashing.
Sorry assuming you used xrecovery to flash rom since you mention installing it.
Well strangely, the update to 1.63 did it, no more reboot and I can even OC the phone ! It works great no reboot, even with wavy usage of GPS navigation with CoPilot live over the week end ! this is perfect !
I only have an issue with the radio FM app which is buggy : sound start on the hp instead of head phone, favorite station are not kept, frequencies are written in green on black which is not visible and RDS name is overlapping frequencies ...
Another issue, I'm still not able to fine tune auto brightness to have good reactivity when phone get out of standb by on shiny day it take 1/ 1.5 second for the screen to detect it need to boost lightness ... Same when I'm in a call and I want to use the keyboard to dial, it takes 1/1.5 second for the phone to adjust brightness... I've tried several tutorial from forum but it still have this small lag in brightness reactivity.
Other the phone is now perfect to me in 2.3.5 ! Thanks very much slade87 ! One note I don't like the boot animation some less shiny would have been welcome ...
Cool you got it all working, yes there where instabilities with cross ROM/kernels.
I like the new bootanimation but you can allways change it out if you dont..
(update 7/7/11)[Boot Animation]more bootanim
Bootanimation Installer v3.3
I am writing in desperation.
My Xperia Active is about 3 months old.
It is the ST17a version but that has never made much difference to anything else.
It has been unlocked via testpoint method so warranty is not valid (plus they don't sell this phone in my country anyway).
Phone randomly reboots when it is not plugged in to power, especially when trying to bring the phone out of lockscreen standby, after using any GPS function or just unlocking the phone
The fact that this WILL NOT happen when plugged in to power is telling me perhaps it is a power management issue.
Things I have tried so far: COMPLETE REFLASH formatting all available mounts from recovery mode + format SD card and start fresh.
Combinations:
1.Spartan Rom 1.9.5 + non-oc kernel
2. Spartan Rom + Rage Kernel
3. Different baseband versions including original (56??), .66 and .62 (currently have .62 installed)
4. EX MIUI + ST17 satsuma kernel
Reboots still happen with all of the above configs
The problem started suddenly whilst using GPS SportyPal pro + Bluetooth music I have previously not had any problems in this area but now they will not stop.
I did not experience any reboots with CM9 but I did not stay in that rom very long as there was way too much stuff not working on my handset - it probably would have happened eventually. Sometimes I can get over half a day of usage without a reboot but then will get like 5 in a row.
I absolutely LOVE this phone but I bought it primarily for sports tracking and it keeps crashing and losing my workouts so I'm getting pretty pissed off.
If anybody can tell me what to look at to try and track this down I would really appreciate it. Checking logcats are no good because it will never reboot whilst plugged in to USB. Are there any other logs I should check???
OK - if not any help to identify the cause - can anyone comment on repair cost @ sony service center out of warranty?
Try fully stock 4.0.2.A.0.62 firmware, some other phones had issues with restarting all the time also, this firmware is known to fix this.
SOLVED - have carried out 5 days of testing.
I can confirm the latest version of MIUIex has addressed my reboot woes.
Have been running reboot logger 1.9 on the phone since then and have not had a single unexpected reboot. I am a happy camper.
Not sure if perhaps there is/ was a common driver or something that was causing these problems between a few of the up to date roms - I am just happy the issue seems to have passed for now.
And it's back. I switched back to Telstra, that means back to 850mhz band, reboots are back with vengeance. Might need to try and find a st17a specific Rom and radio.
bandario said:
And it's back. I switched back to Telstra, that means back to 850mhz band, reboots are back with vengeance. Might need to try and find a st17a specific Rom and radio.
Click to expand...
Click to collapse
Flash this via Flashtools: http://www.mediafire.com/?yvjnt0qctun9t6j
Is ST17a Specific ICS Firwmare. It contains ST17a specific baseband(radio).
Hope it helps
pastillero said:
Flash this via Flashtools: http://www.mediafire.com/?yvjnt0qctun9t6j
Is ST17a Specific ICS Firwmare. It contains ST17a specific baseband(radio).
Hope it helps
Click to expand...
Click to collapse
Wow, thanks!
Seems to have done the trick but now is back to vanilla flavour - seems the rooting process has gotten ridiculous lately, I wonder if it would be easier to pull this ftf to pieces and insert the radio detials etc into another rom file.
For now I guess I will use stock phone unrooted, at least it won't reboot.
THanks for your help!
i have also had that problem. I flashed the sti7a ics version and it is gone, after that you can use any rom without any prob.
bandario said:
Wow, thanks!
Seems to have done the trick but now is back to vanilla flavour - seems the rooting process has gotten ridiculous lately, I wonder if it would be easier to pull this ftf to pieces and insert the radio detials etc into another rom file.
For now I guess I will use stock phone unrooted, at least it won't reboot.
THanks for your help!
Click to expand...
Click to collapse
No prob..
You can flash any custom ROM you want, if it start rebooting again then get back to Stock..
Cheers
I had the same problem, it used to happen when signal was scarce or absent, i solved by getting a new sim card
i have just got an xperia s, and unlocked the bootloader through sony's site today. i then flashed the pre-rooted firmware, the correct one for my model, and am stuck in a bootloop. I have had android phones before, and always been able to get out of messes like this, but sony's system seems to be somewhat different from my previous Moto. can anyone tell me how to possibly fix this? many thanks
Flash another firmware with flashtools.
Sent from my LT26i using Tapatalk 2
thanks, currently downloading the 73 version to test. I have an issue with flashtools though, and fastboot in general on my PC, the drivers do not seem to have installed, as when i try fastboot i get blue led for aprox. 5 seconds, then reboot into the bootloop. fastboot works fine on my mac though
Must install them manually. You open the device manager, right clicking on the S1boot, update drivers. Then shows you which folder is the drivers. and voila.
thanks, ive got it to boot again, and tried various roms, but keep having the same wierd issues. first, everytime i boot i have to go through the xperia setup completely from scratch again, as if the phone is brand new.
secondly, im using doomkernel v4a, and have installed the wifi modules as specified, but turning on wifi causes an instant crash and then reboot, sometimes immediately, sometimes after a short freeze
thirdly, somehow 'phone memory' is completely full, whatever i do. Internal memory, when the phone is completely empty, only shows as 25gb, but phone memory is totaly full, regardless of weather i clear app data/cache etc
any help would be greatly appreciated XD
hello,
you must flash doomkernel v1 or v1a , then after modules wifi for v1, before flashing v4a ,
(sorry for my bad english)
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!
Hello!
Is it possible to install Lineage OS 14 on Xperia Mini pro?
If not, what is the latest Lineage OS version that is possible to install on Xperia Mini Pro?
Henrik Jansson said:
Hello!
Is it possible to install Lineage OS 14 on Xperia Mini pro?
If not, what is the latest Lineage OS version that is possible to install on Xperia Mini Pro?
Click to expand...
Click to collapse
CM12.1 (based on Android 5.1.1) should be the latest CM (or LOS) that Xperia Mini Pro support.
Ok, thanks!
Do you know where to download it, and if there is some step by step instruction somewhere on the internet how to install it.
Henrik Jansson said:
Ok, thanks!
Do you know where to download it, and if there is some step by step instruction somewhere on the internet how to install it.
Click to expand...
Click to collapse
Please head over to the DEV forum of this device. The thread is located the top several.
Sent from my D6503 using XDA Labs
Ok, where can I find "DEV forum"?
Xperia Mini, Mini Pro, Xperia Pro, Active, Live with Walkman Android Development
in legacy xperia you can download CM13 (android M). I´ve installed it in my xperia mini pro (mi only phone) and it´s enought stable for me to use it.
in my opinion, works much better than cm11
https://basketbuild.com/devs/AdrianDC/LegacyXperia/mango/LineageOS-14.x
How to install LineageOS 14.1 Rom (Android 7.1.2)
1. External memory card is required to install the rom (Ext4 only 1 partition). At least around 4gb, must be very fast (Class 10 u3), and should be at around 8gb if possible. All apps, data, etc will go here.
2. Flash boot.img (In fastboot mode).
3. Go wipe, swipe. Go advanced wipe and wipe system.
4. Go advanced --> sideload. Connect USB and type 'adb sideload rom-14.1-xxx.zip' & after type 'adb sideload opengapps-7.1-xxx.zip'
5. Reboot to system. Ignore any warning message.
Thanks for the mango link, but where is the boot. Img file ?
babaorum1973 said:
Thanks for the mango link, but where is the boot. Img file ?
Click to expand...
Click to collapse
Did you take a look inside lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip ?
Because I didn't test it yet: Are there any issues with this build (camera working)?
Just tried lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip and the installation overall was like described by Tromponauta.
The problem is that the touch screen is not responding within LOS. Everything else works (keyboard, camera etc.), just the touch screen seems to have problems. It works just fine inside TWRP and booting LOS for the first time it was responding for the first moment and then stopped (no response, like a frozen OS but the hardware keys still work). I've rebooted back inside TWRP to confirm the touch screen is working and it is.
Any ideas?
saljut7 said:
Just tried lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip and the installation overall was like described by Tromponauta.
The problem is that the touch screen is not responding within LOS. Everything else works (keyboard, camera etc.), just the touch screen seems to have problems. It works just fine inside TWRP and booting LOS for the first time it was responding for the first moment and then stopped (no response, like a frozen OS but the hardware keys still work). I've rebooted back inside TWRP to confirm the touch screen is working and it is.
Any ideas?
Click to expand...
Click to collapse
There was a problem with my display cable. Changed the display and it works just fine now.
Just energy consumption seems to be very high. I bought a new battery which is listed as 100% for around 3hours and then drops down to 0% immediately.
saljut7 said:
Just energy consumption seems to be very high. I bought a new battery which is listed as 100% for around 3hours and then drops down to 0% immediately.
Click to expand...
Click to collapse
This problem is caused whenever a SIM card is inserted. Without SIM card the battery lasts a day as expected.
saljut7 said:
This problem is caused whenever a SIM card is inserted. Without SIM card the battery lasts a day as expected.
Click to expand...
Click to collapse
Its probably your phone hardware problem. I'm running CM14.1 on two mango phones.. without gapps and everything works .. well.. one of them have occasional freeze problems I'm struggling to diagnose, so removing battery is required from time to time to reboot it.
Anyway sim card works fine on both phones with normal battery use.
ROM is quite fast (maybe faster then CM11) but I'm using A1 sd card and no gapps ..
btw I also had some freezing problems on this phone when on other ROMs so maybe its hardware..
Its certainly worth giving CM14.1 try (as per other post earlier on)
EvilMonkey88 said:
Its probably your phone hardware problem. I'm running CM14.1 on two mango phones.. without gapps and everything works .. well.. one of them have occasional freeze problems I'm struggling to diagnose, so removing battery is required from time to time to reboot it.
Click to expand...
Click to collapse
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
EvilMonkey88 said:
Anyway sim card works fine on both phones with normal battery use.
Click to expand...
Click to collapse
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
EvilMonkey88 said:
ROM is quite fast (maybe faster then CM11) but I'm using A1 sd card and no gapps ..
btw I also had some freezing problems on this phone when on other ROMs so maybe its hardware..
Its certainly worth giving CM14.1 try (as per other post earlier on)
Click to expand...
Click to collapse
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
saljut7 said:
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
Click to expand...
Click to collapse
On main mango I get between 12-18 hours depending on use.. (its mostly light though.. messengers, emails, phone calls, etc not much browsing) so battery drain is same ish as other ROMs I tried..
2nd mango with CM14.1 works as alarm clock and sometimes squeezebox controller. mostly on airplane mode which gives over week battery life.. (no sim on that one)
3rd mango is on stock gingerbread converted into dashcam .. I get about 6-7 hours battery with HD recording on Daily Voyager (had to use tasker to turn off screen during recording though)
Got two more of those little buggers but sadly as spares now.. (broken screens)
Everyone tells me I'm mad to still use mini pro.. but I really like small phone with great keyboard.. (by today standards I should say tiny phone lol)
Once a while I consider buying new phone but haven't actually done it yet lol
Yes! +1 Thank you devs for all your work on xperia phones!.. Cheers
p.s I'm still hopeful for Android Go one day
Awesome... well I sitll doubt that my battery drain has something to do with the hardware. As far as I remember the battery life was already not very good when I was using the original Android for 2-3 years. My current battery is now at least 5 years old so I think the current battery capacity is quite okay. Before I had a Motorola xt894 with a Cyanogen Mod experimental/snapshot and the battery life was horrible in comparison to the standard Rom so I think it has something to do with a not optimized LOS.
btw: Did you experience any Wifi issues connecting to public Hotspots? Sometimes I have the problem that I can not connect to public hotspots that worked yesterday. The Wifi list says "saved" to the specific Hotspot after I tried to connect (insteadt of "connected").
saljut7 said:
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
Click to expand...
Click to collapse
saljut7 said:
Awesome... well I sitll doubt that my battery drain has something to do with the hardware. As far as I remember the battery life was already not very good when I was using the original Android for 2-3 years. My current battery is now at least 5 years old so I think the current battery capacity is quite okay. Before I had a Motorola xt894 with a Cyanogen Mod experimental/snapshot and the battery life was horrible in comparison to the standard Rom so I think it has something to do with a not optimized LOS.
btw: Did you experience any Wifi issues connecting to public Hotspots? Sometimes I have the problem that I can not connect to public hotspots that worked yesterday. The Wifi list says "saved" to the specific Hotspot after I tried to connect (insteadt of "connected").
Click to expand...
Click to collapse
hmm maybe you could try battery calibration? or "new" battery.. those are very cheap. seriously no excessive drain here on LOS.. managed 19hours and 10% left today..
no experience of public wifi problems.. but I don't really use them tbh
My main problem with LOS is random freeze when display wont wake up (even when notification is working and background menu lights).. sometimes phone is OK for few days but other times it can freeze few times a day. I keep changing settings in kernel auditor but cannot find out cause yet.. for a while I had suspicion freezes are more likely when using build in browser.. but maybe it was just coincidence
EvilMonkey88 said:
sometimes phone is OK for few days but other times it can freeze few times a day.
Click to expand...
Click to collapse
My sk17i lists errors like
System UI has stopped
com.android.phone has stopped
Settings has stopped
and is always rebooting / in a boot loop. I wanted to reinstall LOS but somehow my whole system seems to be read only. I've already tried https://forum.xda-developers.com/droid-turbo/help/accidently-selected-read-twrp-how-undo-t3312533 but everytime I access TWRP after a reboot "Mount" -> "Mount system partition read only" is checked. I tried to reinstall TWRP with
Code:
fastboot flash boot boot.img
but this doesn't affect the checked "Mount system partition read only" setting so I think TWRP is not reinstalled. Any idea how to fix this? In the end I just want to start over with a new installed LOS.
saljut7 said:
My sk17i lists errors like
System UI has stopped
com.android.phone has stopped
Settings has stopped
and is always rebooting / in a boot loop. I wanted to reinstall LOS but somehow my whole system seems to be read only. I've already tried https://forum.xda-developers.com/droid-turbo/help/accidently-selected-read-twrp-how-undo-t3312533 but everytime I access TWRP after a reboot "Mount" -> "Mount system partition read only" is checked. I tried to reinstall TWRP with
Code:
fastboot flash boot boot.img
but this doesn't affect the checked "Mount system partition read only" setting so I think TWRP is not reinstalled. Any idea how to fix this? In the end I just want to start over with a new installed LOS.
Click to expand...
Click to collapse
Hmm not sure what to suggest as haven't experienced this. In my case everything went smooth on 3 different phones (sk17i) when following instructions from other post:
https://basketbuild.com/devs/AdrianD...LineageOS-14.x
How to install LineageOS 14.1 Rom (Android 7.1.2)
1. External memory card is required to install the rom (Ext4 only 1 partition). At least around 4gb, must be very fast (Class 10 u3), and should be at around 8gb if possible. All apps, data, etc will go here.
2. Flash boot.img (In fastboot mode).
3. Go wipe, swipe. Go advanced wipe and wipe system.
4. Go advanced --> sideload. Connect USB and type 'adb sideload rom-14.1-xxx.zip' & after type 'adb sideload opengapps-7.1-xxx.zip'
5. Reboot to system. Ignore any warning message.
Click to expand...
Click to collapse
maybe sd card is corrupted, have you tried different one..?
Try wipe plus format everything and try again?
So does sideload completes fine and then you got error and bootloop?
Out of interest what ROM have you had before?