Hello,
I got XPERIA Mini Pro a couple weeks ago. It was on stock firmware with android 4.0.4. It's warranty ended a long time ago but the phone was still in a very good shape. I really like trying custom ROMs from different developers as I did on my previous XPERIA X10i. So I chose Unofficial CM11 from LegacyXperia with KitKat for start. I unlocked bootloader without any problems. Flashed kernel with flashtool, then flashed ROM with kernel's build-in recovery. It worked fine although sometimes It hung when I wanted to wake my phone and I had to pull battery out. It happend occasionaly and I though I can live with that. But after a couple days proximity sensor as well as front camera gone. I tried whiping cache, factory reset, pulling battery out for about 20 seconds, flashing ROM again, even flashing stock firmware again. Nothing helped. I did research and it appeared that this is common problem with mango after android 4.2. I think. OK, I thought I can live with that. I returned to CM11 but after a while problem with hungs on wake up started to annoy me. I decided to try the highest cyanogenmod for mango on stable stage of development, not nightly like CM11. It was CM9.1. Again, it worked fine and in fact, it was stable. But after a while I noticed that not only front camera and proximity sensor are gone but ALL OF MY SENSORS died. I tried a couple of things like before (whipe, reset, flash etc.). Tried going back on stock. Tried apps from market which test and reset sensors. Every one I tried said my phone does not support sensors. Accelerometer is crucial for me as I use SleepAsDroid app every day. I flashed CRDROID (based on CM11 but much much more stable) which I use till now. Tried doing research on Internet but I found nothing. Tried hitting my phone and dropping It (that helped a lot of people), tried heating battery by overloading processor (that helped a lot of people too). Nothing helped. Tried repleacing files responsible for sensors with the ones from stock firmware. Now test programs show that I have working light sensor but it does not change it's values at all. I accepted the fact that I won't restore my sensors but I must ask:
Is there anything more I can do? Did I missed something?
Is the only way to fix my problem buying a new motherboard? It appears strict hardware problem, right?
Please help, any suggestion will be much appreciated.
Best regards
Related
hey folks,
i have encountered an annoying problem that has made using the s2 quite an unpleasant experience recently.
I bought my s2 about 4 months ago. after 2 weeks or so i switched to miui (galnet) and have stuck to miui ever since. later i switched to langthangs releases as well as siyahs kernels (loving both, major props to them).
around mid of december, my phone suddenly started to crash. up till then i had a couple of freezes here n there, maybe once or twice a months. but since then, even though i did not change anything, my phone has been crashing more often, like 5-10 times a week. updating kernel and rom didnt help.
i experience two types of crashes:
a) freeze: phone just stops working. i have to take out the battery to reboot
b) reboots: phone just reboots out of the blue. sometimes it reboots 3-4 times in a row, like after the first reboot the phone does nothing for 2-3 minutes, then reboots again and so on
i am not sure if that helps, but most of the time the freezes occur while using the internet, the market and playing games. reboots occur randomly, even if the phone is not used at all.
i haven't done any overclocking, just undervolting using voltage control. but i had been using the reduced voltages for weeks, long before the crashes started to occur. and yes, i did try switching back to the stock voltages.
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Anyone else having the same experience?
Is there a way to check if -maybe- the ram/rom is defect? If nothing helps, i think i ll have to flash a stock rom and submit a warranty claim
I would go on a limb saying its MIUI's fault. Wich version of Syiah are you using? Try to reflash different version, I found that 2.6.2 is stable. Also the new one 2.6.6 wich I'm currently testing is stable to, other ones were kinda buggy.
Also are you undervolting or UC'ing ?
If all else fails flash different ROM, after testing many of them I found the latest Criskelo to be stable as a rock.
The only way to really tell is to flash back to a stock rom and see if the freezes/reboots still occur...
Sent from my GT-I9100 using Tapatalk
well, i have tried different roms. and yeah, i am undervolting and underclocking (200-1000).
but isnt it strange? i have been using miui for months without any problems, and baaam ... suddenly the phone starts crashing? i mean at the time the freezes and reboots started to occur, i had been using the same system (kernel,rom,setting,apps) for weeks without any problems.
i ll try going back to stock. if that doesnt help, ill send it in.
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
dabrain23 said:
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
Click to expand...
Click to collapse
Yep, hence you flashed original firmware the dredded(by some) yellow triangle will dissapear.
It will reapear as soon as you root your device.
that last sentence was supposed to be "if i flash stock via odin ..."
ok. ill try that and report back.
BUT
if flashing a stock rom helps, the problems much likely lies with the custom rom. but if so, why did they work perfectly fine until recently?
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Logic says that is the answer .
jje
u think so?
the phone just slipped out of my hand a couple of times, but it never fell on the floor (lets say 30cm or more).
and why would sth like that cause freezes like that? i mean my sisters ace has a totally shattered glass and its still working perfectly fine.
anyway, backing up all my stuff and trying a stock rom tmr
A while ago I have a weird problem. When my phone is on charge and I turn on 3G it keeps turning off like I would removed the battery. Everything fine until I start an app which uses internet, but when I do it turns off almost immediately. Wi-Fi works fine just the 3G is the problem. I got this problem on two different ROMs (FXP 115, FeraLab v14) and two different kernels (basic FXP115, DoomKernel v6 - medium overclocked), so it must be hardware related, am I right? If not hardware, what else could it be?
Sent from my Xperia X10 using Tapatalk
I had the same exact problem with my Motorola Backflip stock. In fact, if I moved locations where 3G wasn't available to where 3G was broadcasted, it would reboot. I could not fix it with any rom I installed (even tried CM7 which made the phone excellent except for the 3G reboots). I tried full wipes, stock Motorola Motoblur kernel, and everything else. I'm no dev so I didn't try tweaking anything myself and ended up getting rid of it and going with the X10. You can try the SEUS method but it can very well be hardware unfortunately. I hope you have more luck than I!!
If your phone is overclocked that could be a problem. Have a good search though sure I seen this before and think u have to either change something in build-prop or alter/remove a certain process (don't quote me though)
Sent from my X10S using XDA
laneyofdeath said:
If your phone is overclocked that could be a problem. Have a good search though sure I seen this before and think u have to either change something in build-prop or alter/remove a certain process (don't quote me though)
Sent from my X10S using XDA
Click to expand...
Click to collapse
My phone has been overclocked since months, but I've never got this problem earlier, so I don't think that causes it, but I'll give it a try. And I'll search again maybe this time I find the answer. Thank you
Hi, I got a similar problem. Since a few weeks ago, flashed a ROM and when I've tried to use the phone, it keeps turning off randomly, sometimes after a few minutes, sometimes after hours. So, I tried to take it back to the clean original 2.3.3 ROM, but it keeps happening. ¿Any idea? ¿Any solution? Please, help me. Oh, something else, it only happens when the phone's used with the battery, when it's attached to my laptop as modem, the problem doesn't appear.
Hello all,
I've been experimenting with custom roms lately. First I tried resurrection since it got lotsa attention and then I tried sensation, all causing the same problem.
I was lucky to have a NAND backup so I quickly went back to my stock rom. But now I am wondering why are these roms causing heating problems but not the stock rom? Interestingly, many people are using them without any complaints.
I thought this might be a problem with my phone. I contacted amazon and asked for a replacement, they were nice to replace the product even after 3 months! (kudos to them).
But now I'm wondering if this will solve my problem. Moreover, I sometimes had heating while charging the phone, bolstering my thesis that the phone is faulty. Any ideas anyone?
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
atifsh said:
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
Click to expand...
Click to collapse
Lol calm down! I've not returned it, I am going to replace it. I've had heating problems with stock rom as well, especially while charging. I've changed the battery, thinking the problem was the battery but it didn't help at all. Also today, after being back to stock rom, it still heats up even with simple tasks. So I assume there is some kind of fault.
It's normal for your phone to heat up. If it heats up its perfectly normal because the cores are working fine. If u got battery heating warnings or any other phone heating warning thats the problem and you should investigate =D
Hi! I've been reading this forum on and off for few years, but never actually posted. Hope someone here can help me sort out my issue, thanks in advance!
Basically, I've flashed a cm13 via custom recovery on my second phone - Xiaomi Mi4, and I'm having all sorts of issues with it. I bought the phone in China, and for a while
used the stock MIUI interface, but I hated all the bloated apps and weird pop-up advertising, so decided to flash. it was the first time i've attempted it, so it took some
time to figure it out
My two main issues with cm13:
1. It crashes and restarts two/three times daily for me. I mean, I've cleared cache, I basically have no apps on the phone (apart from few messaging apps and facebook).
Is it just because it's an early cm13 build, or it's a nature of custom roms? I'm wondering if switching to a snapshot cm12 build would be better? I don't really care for
android 6 features on this phone that much, I just want a stable experience.
2. The charging became uber slow, painfully so. On MIUI it'd charge to 100% in about 3 hours or so. On cm13 it takes 3-4 hours to get to 30-40%! Never seen anything like
this. Also, if the battery depletes to 0%, the phone wouldn't turn on, even plugged in for charging. It'd turn on after an hour or two into the charging process. Seems weird,
as every other android phone I've owned previously would turn on even with 0% battery if I'm plugged in.
Anyone else experience any of the listed issues? Is it just an early build, or I've done something wrong in the flashing process? I really just want a stable simple os, no advanced
features or whatever, just need it to work
Thanks!
I have been using latest nightly.. No issues no reboot.. Charging time is 3hr
mmrx said:
I have been using latest nightly.. No issues no reboot.. Charging time is 3hr
Click to expand...
Click to collapse
Thanks for reply! Would you mind telling me which gaps you've used for your build? I remember I had some sort of an issue with few gaps
I tried, I think only the smallest package worked for me. Maybe that's the issue and something in the gaps i've installed freezing/rebooting my os?
Thanks
Xiaomi Note 3 Pro 2/16GB
Hi,
i am currently on a nightly cm13 build. before i had the same issue on the snapshot build.
Used also different kernels but with the same results.
Issue is shown in the video below.
https://www.youtube.com/watch?v=HI43XX0WIpY
This happens probably once a day and only when i am waking up the phone from deepsleep with the fingerprint sensor.
The screen keeps being black for a second when this happens. When i turn off the screen and wake it up again, everything is fine.
What do you think, hardware or software issue?
EDIT: Just found out, that it could be potentially a LiveScreen issue on cm13
EDIT2: No, LiveScreen is not the problem
I'm also facing this issue. Are you using any custom kernel?
I'm using the Blaze kernel.
Yes, was using Blaze kernel as well but i tried different others as well.
I am now on Exodus ROM without these issues.
Seems to be a cm bug.
I've had the issue also while charging my phone last night.
CM13 with Redon kernel.
Scared the sh*t out of me...
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
MiripRedmoon said:
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
Click to expand...
Click to collapse
i know its long time ago, but could you repair the device?
screen glitches
same problem, flickering and mistyping too. Please anyone resolve, this has happened after the latest update
I had this issue, rom and kernel reinstall solved the problem. Maybe something is cached/crashed or both (the phone acted weird other ways too, random apps crashed and so on), before reinstall wipe cache, dalvik, data and system, then install the latest versions of the rom and kernel you want to use. Don't forget to flash firmware.
Since I did this everything is fine.