Related
Hi guys,
I am really losing it with my girlfriend's P990 (originally vodafon branded on the german o2 network). On stock this phone was a nightmare: random crashes, laggy launcher, random reboots / powerdowns etc made it a completely aweful experiance. So I said: ok this should be an easy fix, just install a custom rom and those problems should be gone. Since then I have tried:
- several Modaco Roms
- latest Euro Open Stock LG update (Smartflash)
- Topoggigi with Service Packs and different kernels
- Gueste2x 2.2 with different kernels
- Gueste2x 3.0 and 3.1 with different kernels
- all sorts of different basebands on the roms mentioned above
While I really appreciate the work the devs are doing and the system works alot faster however none of the roms really fixed the other problems: some lost reception, some had non working / freezing wlan, others had gps problems and there are still random shutdowns when the phone is idle.
Can anyone recommend a rom / baseband / ril combination that just works? It's for my gf's phone so I don't need all the ramhacks, undervolt, overclock, underclock gimmicks, I just want a stable phone working for everyday use which does not shut itself off, she does not even care if it's froyo or gingerbread based.
I was trying to avoid pure cm7, which I use and love on my own phone, because well, I can already hear her complain how everything looks different
Big thanks in advance for your tips and suggestions.
For the simple user, with no UV / OC or any tweaks...and great stability and not matching your CM 7 in appearance(obviously urs and hers should not match mate....cause the BOSS is always different...dont take this serious...just joking)
one of the best ROMs I have used was the Topo's 2 with SP3...BBV20E with matching RIL(use GetRIL). If you want stability....the first thing I can think about is Topo's ROM....many developers themselves will agree on this point...he was a big inspiration for the upcoming devs.
Coming to the point of tweaks...this ROM with Spica's HP SR1 Kernel was one of the best results I ever had....three days of battery perf and almost 99.9% trouble free....dont look for 0.01%....you will probably never find tht.
Coming to the point of freezes....or random reboot...i found this hardly in this ROM....nevertheless, you also need to check the correct BB and matching RIL...which you will find in the relevant thread.
tweaks in this....they dont bother your stability....and still remains one of the best GB ROMs.
If you want more info...maybe u can PM me or add your comments to this thread....
But, a word of caution...you will never be satisfied, with the amount of variety and features the other ROMs offer....u still want more....Have flashed more than 14ROMs in less than 4months.thats how the life of a O2X owner is.....and I am enjoying it
SREEPRAJAY said:
For the simple user, with no UV / OC or any tweaks...and great stability and not matching your CM 7 in appearance(obviously urs and hers should not match mate....cause the BOSS is always different...dont take this serious...just joking)
one of the best ROMs I have used was the Topo's 2 with SP3...BBV20E with matching RIL(use GetRIL). If you want stability....the first thing I can think about is Topo's ROM....many developers themselves will agree on this point...he was a big inspiration for the upcoming devs.
Coming to the point of tweaks...this ROM with Spica's HP SR1 Kernel was one of the best results I ever had....three days of battery perf and almost 99.9% trouble free....dont look for 0.01%....you will probably never find tht.
Coming to the point of freezes....or random reboot...i found this hardly in this ROM....nevertheless, you also need to check the correct BB and matching RIL...which you will find in the relevant thread.
tweaks in this....they dont bother your stability....and still remains one of the best GB ROMs.
If you want more info...maybe u can PM me or add your comments to this thread....
But, a word of caution...you will never be satisfied, with the amount of variety and features the other ROMs offer....u still want more....Have flashed more than 14ROMs in less than 4months.thats how the life of a O2X owner is.....and I am enjoying it
Click to expand...
Click to collapse
Thank you for your quick reply, and yes I agree on the boss part =)
I had topos rom on her phone (with another baseband though) but I had 2 problems:
on SR1 kernel:
with wifi sleep policy set to never wlan just stopped working after being connected for a while: it still showed the wlan connected + full reception icon in the statusbar but no data went through untill I manually turned it off and on again.
To fix that I switched the kernel on his rom (I cannot remember exactly to which one) which fixed the wlan issues but caused the phone to randomly lose all mobile reception until a manual reboot. Maybe this was caused by a wrong baseband. According to getril baseband and ril were a match though.
Other than that the rom was perfect (especially battery life)...but those 2 issues made it useless for an everyday rom. Especially because both bugs happend several times a day.
BTW: Topo recommends using the LGP990AT-00-V20c-EUR-XX-AUG-02-2011+0_CP.fls baseband, not the 20E you mentioned.
Why are you so sure it's software?
I bought a P990 almost two weeks ago, been giving it some nice usage (GPS, Wifi, 3G, a lot of gaming in the subway) still on stock software and I've had ZERO issues with it.
Why didn't you try to complain to your vendor about your faulty phone and get a new one?
you seem to be one of a lucky few then, because from what I hear from other owners of the phone it really IS a buggy phone. Have you tried to return a phone based on lags and errors which seem to occur randomly...it is not like I can reproduce the shutdown / reboot problems, anyway returning it is not an option anymore.
Mate,
you are right...Topo recommended the BB you have mentioned. But, if you have observed the complete changelog....then you may see the v2.0 with SP3 is made with V20E as the base. Personally, I used this and had no issues until unfortunately Topo's father fell ill and also the other ROMs came in, to give a variety.
Your wifi dropping might be a BB-RIL combo....you need to change the RIL according to region, operator and call quality etc....the app suggests a few RILs(if you have noticed in LG RIL Version or Get RIL app)....
In addition to this, there is also a V20M version made by another developer which alsy was working perfectly good...infact a few pple think that V20M is one good version which was a fix to BSOD and also better battery perf....
I am presently changing quite often between Django and Civato ROMs....and I have no issues with these ROMs. I have tried Gueste 3.1 which is very stable, great perf and fluidity...but the matter of changing to more what I am used to...
There are a great deal of variety and feature packed ROMs in the O2X cabinet and we need to be testing and staying which appeals the best in different terms for our satisfaction.
---------- Post added at 03:57 PM ---------- Previous post was at 03:42 PM ----------
tr0ner said:
you seem to be one of a lucky few then, because from what I hear from other owners of the phone it really IS a buggy phone. Have you tried to return a phone based on lags and errors which seem to occur randomly...it is not like I can reproduce the shutdown / reboot problems, anyway returning it is not an option anymore.
Click to expand...
Click to collapse
Every phone has its plus and minus mate....I am proud of O2X not because it was made perfect(surely poor quality by LG) but the developers here are striving to make this a perfect smartphone.....and we are very close to that ....
Just believe and you can make it better....
SREEPRAJAY said:
Just believe and you can make it better....
Click to expand...
Click to collapse
lol that's what I have been trying and the reason for this post. My problem is that I can flash a new baseband / rom / ril after work and test everything like wifi, gps, mobile internet and reception when I am at home. When everything *seems* to work I give the phone back to my gf hoping it's fine now. When she has the phone over the day and comes back in the evening and reports errors, so I start over again. That makes the whole process pretty tedious and I was hoping for a recipe, maybe from another user on a german network to shorten the whole process. But you already gave me a few tips I will also try next!
tr0ner said:
you seem to be one of a lucky few then, because from what I hear from other owners of the phone it really IS a buggy phone. Have you tried to return a phone based on lags and errors which seem to occur randomly...it is not like I can reproduce the shutdown / reboot problems, anyway returning it is not an option anymore.
Click to expand...
Click to collapse
I don't know where you're from, but from where I'm from you usually have a two-week no questions asked refund period. And yes, I have tried to return electronic devices based on random problems within this period and usually I don't have any problems. Especially if I'm looking for a replacement for the same phone and not just my money back (I know some people who abuse this two-week period and try almost every phone there is... they almost don't need to buy phones...)
If you're outside this two-week period it might be trickier, I admit. But still I was just trying to be helpful. No matter what we do there will always be products with faulty hardware, and this faulty hardware might cause random lags and errors... if this is your case nothing you do will solve the problem, except for a replacement, that's why I suggested it.
And yes, I do realize I'm lucky. Before I bought the phone I did a lot of reading and I read about the random crashes, and saw people saying that a custom rom usually fixed it, so I was already prepared for this. But I'm not experiencing any of it so I'm happy.
Nonetheless I wish you the best of luck!
Gueste2X v3.1 with Temasek Turbo kernel and 218 BB works great for me.
Best ROM I've ever tried.
Reception drops and Wifi problems can be caused by BB not correctly installed.
No offense intended, but are you sure you did that correctly? Because I've seen manuals for installing BB which are outdated, wrong or just lack important data. I flashed my BB in a wrong way before.
Since you are German:
http://www.handy-faq.de/forum/lg_op...-lg_optimus_speed_p990_aktuelle_baseband.html
I am using temasek`s latest KANG-54, its smooth and stable. No problems whatsoever. Oh, and just today i flashed the kernel to ETaNa. Will see how that goes.
Thanatos2x v5.1 -> been using this for a few weeks now, came from Modaco GR5. It's really a very good rom. Fast, stable, not to different from stock LG. I'm using the 725 BB from v20o (with the RIL that came with the rom), tho get ril suggests I get the RIL from v10d NL (since I live in Holland). Haven't tried it since this setup just works great. Reception is good, battery lasts the whole day easily, no reboots or freezes...
After testing several ROMs I decided to use a ROM which won't let me miss a call. I chose MACODO GR6 . It's the most stable ROM I've ever tested. I'm tired of using buggy ROM just for the speed.
thank you guys for your recommendations!
Now I know what to check out next =)
I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
chipsharpdotcom said:
I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
BWolf56 said:
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
Click to expand...
Click to collapse
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
chipsharpdotcom said:
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
BWolf56 said:
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
Click to expand...
Click to collapse
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
chipsharpdotcom said:
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
Click to expand...
Click to collapse
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
billyjed said:
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for the tip...I'll try that if all of the above doesn't work. At this point, I'm all flashed up and running test cases.
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
chipsharpdotcom said:
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
Click to expand...
Click to collapse
Have you tried it with a different clock app? I mean, if I understand this correctly, it seems to be narrowed down to your current clock apk, which is different than the stock GB one. So I would suggest freezing (or unistalling) your current one with Tibu and trying a different one.
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
chipsharpdotcom said:
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
Click to expand...
Click to collapse
Haha first time I ever get that question but leaving your camera on should do the job (or video playing)
You can get it here: http://get.cm/?device=quincytmo&type=RC
Seems stable. Everything working so far.
I guess I need to go check it out. I'm still on the latest monthly.
As far as I can tell, it is caught up with the nightlies as far as features go: Camera timer, stylus gestures, whatever else is new. Everything I've tested so far works, wifi tether, bluetooth etc,
Yeah, so far so good. It seems pretty stable and fluid. Haven't checked battery life. I noticed on the last nightly that it took longer to charge the battery.
Battery life here seems very good. Very smooth, not getting lagginess that was in a couple of nightlies.
Had a couple of instabilities with a couple of apps. Reinstalling them seems to have fixed the problem. Time will tell.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Going back to M3. Having too many instabilities, random reboots, lock ups.
srpanadero said:
Going back to M3. Having too many instabilities, random reboots, lock ups.
Click to expand...
Click to collapse
I was about to say that I haven't seen any bugs with this latest release, but then I thought for a second and remembered that I had a weird screen issue where my screen was flickering, and then went black until I restarted the phone. It only happened once, so I didn't think much of it. I expect a few bugs with any ROM no matter how stable/baked it is.
Here is a bug report for graphical issues. Now is the time to report any bugs that you see.
https://jira.cyanogenmod.org/browse/CYAN-1057
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Now there's an RC2. Trying it now.
fraughtsigewulf said:
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Click to expand...
Click to collapse
So then could you and anyone else who've seen the issue sign up and vote on the bug report here: https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-1125
Either that or add your own comment and log if you have. Hopefully the devs will then see and fix the problem.
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
hogasswild said:
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
Click to expand...
Click to collapse
Now i'm getting freezes and reboots 5-6 times a day. Today I could hardly use my phone. And that was even after doing a full wipe this morning and reinstalling the latest nightly and Gapps. I think i'm gonna roll back to a version from a couple of months ago if I can find one and see if that helps.
I did go to that dev page that was suggested earlier in the thread and signed up and voted up this issue. I hope it gets the ball rolling.
I'm kinda disappointed. I know these are nightlies and aren't supported, but i'm really used to Cyanogenmod putting out solid builds, even for their nightlies. A few bugs I can deal with, but this is unusable.
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
error when installing
when I try to install the zip file I get this error "assert failed: getprop("ro.product.device)...." this is just the beginning the type is small and its hard to read- any suggestions? Some searches I've done say this error shows when the ROM is for the wrong phone, but don't see how that can be. I have the T-Mobile Galaxy Note for sure. Thanks for any help that I can get. Since it seems like T-Mobil is never going to upgrade OTA to Jelly Bean I really would like to get this ROM.
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod. Here is the links. http://get.cm/?device=quincytmo&type=snapshot
srpanadero said:
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod.
I was using Clockwork MOD. I will admit I'm a bit of a Newb with this custom recovery stuff. I went to install Goomanager on my phone, but when I reboot it reboots it into Clockwork MOD. So do I need to uninstall clockwork MOD somehow? I will try the other ROM you mentioned, but I think I had tried that one as well and got the same error. Of course this was using clockwork MOD.
Thanks,
John
Click to expand...
Click to collapse
This is the twrp page for this phone.
http://teamw.in/project/twrp2/113
It lists several ways to install it. Try them all, one will work.
srpanadero said:
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
Click to expand...
Click to collapse
So M3 is stable enough to use? I couldn't remember whether it was M2 or M3.
Yes M2 and M3 are stable enough for daily use. Actually any nightly from that time is good too. It wasn't until after M3 that things took a dive, and didn't get any better with RC1 and 2.
Only problem I'm aware of is a bug with the Bluetooth on off toggle that affects some. If it happens reboot or force close Bluetooth share.
Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.
using CandyRom 5.0.2
I never faced any touch freezes issue
@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?
im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english
Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.
I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.
1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)
I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.
Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
dont think its a software problem, maybe you should get your phone checked out
njuz said:
Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
Click to expand...
Click to collapse
Its of course a well know bug for all mi5 roms. I read yesterday that last thursday rom update fix this:
"Fix - Accelerometer and gyroscope didn't work after and OTA update (08-12)
Fix - Accelerometer and gyroscope didn't work normally (08-12)"
The problem occured with miui as well as with unofficial CM build, what i am using now. This indicates to me that it has nothing to do with the installed rom directly.
After rebooting, everything works fine again.
I suspect apps like Pokémon go to stay in relation to the bug. Since i am not playing that game anymore it occures much rarer...
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
I was having the same problem. I dont play pokemon. Im still on vendor rom. But now the bug gone i tried to simulate the bug but it rotate normally
I have this issue. I'm on the latest CM 13 build and I get issues where the camera won't take in landscape and full screen videos won't switch to landscape when you rotate the phone. It's so nearly perfect apart from that.
shucrut said:
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
Click to expand...
Click to collapse
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
I installed a couple of Sensor Test apps and neither one can see my accelerometer sensor to even test it. So it's like the sensor isn't even there. I know it works because one of Shade.sh's beta CM 13 builds was able to detect the sensor OK! Any ideas?
Here's the sensors detected in the Check My Android app. There seems to be only two axis detectors working. How does this compare to a healthy Mi 5?
sharkyblunt said:
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
Click to expand...
Click to collapse
Yes, i actualy did. After installing developer version 6.9.18 the problem never appeared again. Now im on 6.9.22 and the rotation bug is gone
Hmm, I've just tried SlimRom and the same bug is present, presumably because it's derived from the same tree as CM 13.
I'm actually tempted to give MIUI 6.9.22 a go then if it's the only way to get this fixed.
I have just flashed the MIUI developer ROM 6.9.2.2 and my sensors are working perfectly now. So it must be something for flaky in the CM stack or Kernel version. See screenshot.