Related
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
LlirasChosen said:
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
Click to expand...
Click to collapse
is the show screen updates or something similar on in developer settings?
dragon1357 said:
is the show screen updates or something similar on in developer settings?
Click to expand...
Click to collapse
Nope, I don't run that stuff because all of the rendering updates and stuff can get annoying to look at while working. I'm able to get the same issues on a fully stock rom, and a pure flashed rom, with a few programs installed. But the fact that the hardware render seems to be the issue to me is just very odd on a non-AOSP rom.
I have been having screen flickering issues ever since I flashed the latest AOKP build (AOSP) I originally thought that it was because of the kernal and the under voting that I applied but even with a different governor and normal volt settings the screen still flickeres. After some poking around I figured you that it is only happening while I am trying to type and by uninstalling the Swype beta keyboard the screen flicker had been reduced to almost nothing. I do not know why the keyboard would amplify the effect but if I use the system keyboard the flickering becomes almost non existent.
Also, the screen flickers anytime a pop up menu is on screen, such as in the tapatalk app, the menu that pops up to allow you to quote someone..
Sent from my SCH-I535 using Tapatalk 2
Had been having the same issue on Baked Bean 6, flashed BB7 last night and it seems the problem is gone. BB7 being 4.2.1 I'm guessing whether intentional or not somewhere along the process of updating the "bug" if it indeed was as it appeared was squashed.
I'd be curious to know what was causing this, if by chance you find a definitive answer please post it.
Thanks
Lk
I had a very similar issue for a while, i flashed LEAN KERNEL
Rebooted twice, and problem went away.
For an update, I flashed kt's latest kernal and the flashing has ceased.
Sent from my SCH-I535 using Tapatalk 2
Hi all,
I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.
Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M
The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.
I have logcat in *:V and nothing is ejected that looks suspect, it just ends.
I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.
My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
Wipster said:
Hi all,
I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.
Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M
The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.
I have logcat in *:V and nothing is ejected that looks suspect, it just ends.
I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.
My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
Click to expand...
Click to collapse
There are people who report crashes when phone connects to GSM instead of WCDMA, you can lock your phone to WCDMA Only on the testing menu (dial *#*#4636#*#* and go to "Phone information").
Also, changing ROM might help. there is officialy built CM10, and CM10.1 is quite stable (I'm using it myself as a daily driver for a month now). Also there are many Sense ROMs which are very stable.
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
Wipster said:
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
Click to expand...
Click to collapse
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
astar26 said:
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
Click to expand...
Click to collapse
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.
I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.
Thanks
Wipster said:
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.
I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.
Thanks
Click to expand...
Click to collapse
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
astar26 said:
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
Click to expand...
Click to collapse
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.
Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.
Edit: Attached is the kmsg for CM10 at a crash.
Wipster said:
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.
Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.
Edit: Attached is the kmsg for CM10 at a crash.
Click to expand...
Click to collapse
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.
You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
astar26 said:
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.
You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
Click to expand...
Click to collapse
It was stock CM9 and CM10 I have tried, no other kernels.
With the CM10 image, can I just install a kernel from another ROM and it 'work' or do I need to change roms over to test?
I upgraded the radio (11.76A.3504.00U_11.24A.3504.31_M) using the latest RUU and then plopped my CM10 backup back on and so far so good, signal seems better however I'm sure that's placebo, will keep you posted.
Edit: OK so upgrading the radio did nothing whatsoever. Still crashing.
Attached is a nice crash, stops at msm_pm_power_collapse something to do with shutting down CPU, maybe for clock change, I have changed the minimum clock freq to 384Mhz just in case mine is a device which cant do 192mhz.
Just tried Albinomans ROM and its still crashing.
Attached is the kmsg and the logcat in verbose mode.
Looking for a stable daily driver for my friend whom I am giving my phone to, now that I have a nexus 5 almost here.
She needs something stable. This phone has ran Cyanogen for a while and I just wouldnt feel comfortable giving it to her with the finicky data, odd call problems from time to time, etc.
So, in terms of stability over features, which would you recommend?
SourcE is maximus with some tweaks. Nothing very special, so the stability isn't really modified. But you have some interesting tweaks in SourcE: better quality pictures, better sound, gif recording, etc.
So I think you can give to your friend your One S with SourcE 2
Envoyé de mon HTC One S en utilisant Tapatalk
Maximus.
The "better picture quality" and "gif recording" can be flashed using pirlano and TheEndHK's camera mod. Better sound quality produced by V4A is also downloadable. The only thing i wanted more from maximus are tweaks, though we can use xposed framework and sense 5 toolbox module.
But you can never go wrong with both source and maximus since both of them uses the same updated firmware..
Atok_fr said:
SourcE is maximus with some tweaks. Nothing very special, so the stability isn't really modified. But you have some interesting tweaks in SourcE: better quality pictures, better sound, gif recording, etc.
So I think you can give to your friend your One S with SourcE 2
Envoyé de mon HTC One S en utilisant Tapatalk
Click to expand...
Click to collapse
Being as I have never used Maximus or SourcE, how does it compare to stock? Same issues with screen on lag as other 3.4 roms? Signal stability compared to stock?
I am in the US
phin586 said:
Being as I have never used Maximus or SourcE, how does it compare to stock? Same issues with screen on lag as other 3.4 roms? Signal stability compared to stock?
I am in the US
Click to expand...
Click to collapse
It is comparable to stock, not the 3.4 roms. Meaning, no lag and signal is good.
I do find it irritating that with the new firmware you need to use the modified twrp which will cannot mount usb storage. Also the backup feature can put your backups in the wrong directory. So you have to move them for them to show up.
So for me, it is just the recovery that I don't like.
tivofool said:
It is comparable to stock, not the 3.4 roms. Meaning, no lag and signal is good.
I do find it irritating that with the new firmware you need to use the modified twrp which will cannot mount usb storage. Also the backup feature can put your backups in the wrong directory. So you have to move them for them to show up.
So for me, it is just the recovery that I don't like.
Click to expand...
Click to collapse
Cool, thanks for the info. I will definitely give it a try for a few weeks and see if she likes it. I can always revert to stock.
phin586 said:
Cool, thanks for the info. I will definitely give it a try for a few weeks and see if she likes it. I can always revert to stock.
Click to expand...
Click to collapse
If you like aosp, CM 10 is very stable, and particularly light ... which makes it quite responsive and quick. If she would prefer sense, then stock 4.1 will be absolutely trouble free. I use rom cleaner to strip out all the bloat, which makes the stock rom fly. In my experience, most women want stability over anything else ... they just want things to work.
wmdunn said:
If you like aosp, CM 10 is very stable, and particularly light ... which makes it quite responsive and quick. If she would prefer sense, then stock 4.1 will be absolutely trouble free. I use rom cleaner to strip out all the bloat, which makes the stock rom fly. In my experience, most women want stability over anything else ... they just want things to work.
Click to expand...
Click to collapse
As stated in my first post, CM has not been very stable. Connection issues, each update always brings a new issue. I run CM as it is..
phin586 said:
As stated in my first post, CM has not been very stable. Connection issues, each update always brings a new issue. I run CM as it is..
Click to expand...
Click to collapse
I wasn't talking about the current CM 10.2 updates (Android 4.3) ... CM 10 (Android 4.1.2) is absolutely stable, and it still has most of the functionality of the latest and greatest.
wmdunn said:
I wasn't talking about the current CM updates (Android 4.3) ... CM 10 (Android 4.1.2) is absolutely stable, and it still has most of the functionality of the latest and greatest.
Click to expand...
Click to collapse
Fair enough. I think she would enjoy the features of the Sense camera and the added apps. Shes a android noob.
phin586 said:
Fair enough. I think she would enjoy the features of the Sense camera and the added apps. Shes a android noob.
Click to expand...
Click to collapse
Then stock 4.1 will be the most stable of all ... it's what my wife runs on her T-Mobile One S.
wmdunn said:
Then stock 4.1 will be the most stable of all ... it's what my wife runs on her T-Mobile One S.
Click to expand...
Click to collapse
Gotcha. Someone stated that Maximus and SourcE are comparable in stability. Wondering what issues are apparent, compared to stock. I wish Dev's would dedicated a 1st or 2nd post to list of known issues. :-\
phin586 said:
Gotcha. Someone stated that Maximus and SourcE are comparable in stability. Wondering what issues are apparent, compared to stock. I wish Dev's would dedicated a 1st or 2nd post to list of known issues. :-\
Click to expand...
Click to collapse
Some have had pretty good success with Maximus, and for the most part stable. Others have had some glitches along the way, and they simply won't be as stable as the Stock RUU. My One S has been rooted and s-off since day one ... and I have tried all the major custom roms. It doesn't bother me when something goes wrong, because I know how to fix it. My wife, however, really gets upset when glitches occur on her phone, so we keep it simple, stable ... everything just works. I might add that the T-Mobile Stock RUU is no slouch ... it runs very well.
wmdunn said:
Some have had pretty good success with Maximus, and for the most part stable. Others have had some glitches along the way, and they simply won't be as stable as the Stock RUU. My One S has been rooted and s-off since day one ... and I have tried all the major custom roms. It doesn't bother me when something goes wrong, because I know how to fix it. My wife, however, really gets upset when glitches occur on her phone, so we keep it simple, stable ... everything just works. I might add that the T-Mobile Stock RUU is no slouch ... it runs very well.
Click to expand...
Click to collapse
Ya I am thinking that is going to be the way. Who knows, maybe we will get luck with KITKAT. =S
phin586 said:
Ya I am thinking that is going to be the way. Who knows, maybe we will get luck with KITKAT. =S
Click to expand...
Click to collapse
That would be wonderful if it were to happen, but unfortunately HTC has turned it's back on the One S. There will most likely be some custom 4.4 roms, but once again it will be difficult to make them completely stable. I am seriously thinking about moving on to the Moto X, and giving my One S a well deserved rest ... it's been a great phone!
wmdunn said:
That would be wonderful if it were to happen, but unfortunately HTC has turned it's back on the One S. There will most likely be some custom 4.4 roms, but once again it will be difficult to make them completely stable. I am seriously thinking about moving on to the Moto X, and giving my One S a well deserved rest ... it's been a great phone!
Click to expand...
Click to collapse
I am picking up a N5, just waiting for it to be delivered.
After this last foray with HTC, I do not see myself leaving the Nexus ecosphere, in well... ever...
phin586 said:
I am picking up a N5, just waiting for it to be delivered.
After this last foray with HTC, I do not see myself leaving the Nexus ecosphere, in well... ever...
Click to expand...
Click to collapse
Good choice ... looks like a great phone. Before my One S, I carried a Nexus device. I really prefer stock Android. I considered the Nexus 5, but it just doesn't fit my hands ... hence the Moto X. Anyway ... have fun with your new phone!
phin586 said:
Gotcha. Someone stated that Maximus and SourcE are comparable in stability. Wondering what issues are apparent, compared to stock. I wish Dev's would dedicated a 1st or 2nd post to list of known issues. :-\
Click to expand...
Click to collapse
Maximus is completely a stock HTC One S 4.2.2 RUU but just you've to install it via manual RUU installation method so it is a bit trouble. SourcE is based on Maximus with little necessary and very important tweaks, they are pretty much the same, I'll strongly prefer SourcE.
You have to install this "Maximus/SourcE RUU" via command prompt and there are just too many noobs around and some probably need to go for English lessons because they fail to read the procedure every time so they never flash it successfully. But remember your One S has to be a S-OFF device to do that.
To the stability problem, there are radio bugs in Maximus/SourcE but that is HTC fault, nothing wrong to the rom developers. This is a case to case by bias, personally I don't have any problem at all. You have to try it out because we don't know if the radio compatible to your carrier network or not.
1. Some got very poor in-call volume
2. Some got mobile data slow problem
3. Some got mobile signal weak problem
Basically, that's all the problem listed but I don't meet any single one. The radio 1.20 in Maximus/SourcE does working with my Hong Kong carrier network quite well. You can flash older radio like 1.1x to fix all above problem but it will create a random data disconnection bug.
TheEndHK said:
Maximus is completely a stock HTC One S 4.2.2 RUU but just you've to install it via manual RUU installation method so it is a bit trouble. SourcE is based on Maximus with little necessary and very important tweaks, they are pretty much the same, I'll strongly prefer SourcE.
You have to install this "Maximus/SourcE RUU" via command prompt and there are just too many noobs around and some probably need to go for English lessons because they fail to read the procedure every time so they never flash it successfully. But remember your One S has to be a S-OFF device to do that.
To the stability problem, there are radio bugs in Maximus/SourcE but that is HTC fault, nothing wrong to the rom developers. This is a case to case by bias, personally I don't have any problem at all. You have to try it out because we don't know if the radio compatible to your carrier network or not.
1. Some got very poor in-call volume
2. Some got mobile data slow problem
3. Some got mobile signal weak problem
Basically, that's all the problem listed but I don't meet any single one. The radio 1.20 in Maximus/SourcE does working with my Hong Kong carrier network quite well. You can flash older radio like 1.1x to fix all above problem but it will create a random data disconnection bug.
Click to expand...
Click to collapse
Appreciate you going into all the detail, but these issues are exactly what many people are trying to avoid with their One S. That is why we were talking about what our better halves were not willing to tolerate.
Same as @TheEndHK, i don't have those issues as well, in fact the in call audio volume on mine is much louder than when i was on viper. The 1.20 radio brought me much stronger wifi signal and stability on mobile data, though some places i have full network coverage became weaker but not that much. Not all of us experienced those issues, and you won't know that if you will or will not experience it either if you haven't tried it yourself. :thumbup:
If anyone has GPS working properly (i.e. When location is set to "device only". Can they please post which ROM and version?
All my searching around hasn't led me to a fix. I'm on Slimkat latest weekly right now... But would switch roms for working gps... But preferably not stock.
This worked for me... Not sure why:
Rumpel78 said:
Try this, it helped me:
* Backup your installation
* Install stock rom, or restore a backup of stock and factory reset
* on stock, go through setup. Then start a gps app like Google maps
* you will be prompted with a dialog, stating location service was turned off and asking you if it would be turned on again. Answer yes.
* restore backup
*gps should now be fixed
Click to expand...
Click to collapse
@r2mahara I'm just curious why you would apparently take any custom ROM over stock, what's the aversion, can you explain? I tried a couple of custom Roms and went back to stock. I'm just really curious.
That's a fair question. In the past when I owned previous phones, it was a matter of the manufacturer not updating the software on the phone.
However with the Moto G, the stock firmware is actually pretty good. Everything works... It's been a nightmare finding a ROM that has everything working consistently (GPS, Camera etc).
With things like Exposed modules nowadays, it's less necessary to install a custom ROM when looking for certain features - so that's now a viable option. It's a bit tricky finding the right exposed module to do what you want, if it exists and involves lots of reboots.
For example, I find it extremely useful customising my navbar and adding my own buttons to perform specific operations. With Exposed & Gravitybox, I think I can add 1 extra button, which doesn't cut it. Maybe there's another module that's better for this specific thing, maybe not - it takes lots of time to search and try them.
Some ROMS feel faster - but with high end processors these days that's less of an issue. It's nice having bloat removed, but one can do that oneself with root and TB for example.
So in short, there's less of a case these days. I've been using Slim for years now. I like the feel of it, and I guess I'm just used to the way things are laid out. I never thought about changing until all these weird camera and GPS issues (which seem difficult to fix because not everyone has them).
I have everything working now - so plan on testing new builds and coming back to the current setup if anything doesn't work. But I just might go back to stock until things stabilise a bit more.
grahamgo said:
@r2mahara I'm just curious why you would apparently take any custom ROM over stock, what's the aversion, can you explain? I tried a couple of custom Roms and went back to stock. I'm just really curious.
Click to expand...
Click to collapse
@r2mahara Thanks for the detailed reply. I am using stock 4.4.3 + xposed (modules DS battery saver, Greenify, gravity box) everything works and battery life is 2 days with average use. Its so good I won't upgrade further (it ain't broke so why try and fix it), that is unless the L version has substantial advantages. You mention xposed and the need to reboot. I believe that this is largely in the past. When I was experimenting and tweaking I don't recall having to reboot at all, or maybe I did the odd soft reboot which is quite quick? - I forget.
Oh, incidently there is a module available that claims to be able to make comprehensive changes to the navbar,
Here is the link
http://repo.xposed.info/module/com.gzplanet.xposed.xperianavbarbuttons
You wrote that everything is working now so this isn't an issue but I thought it was worth mentioning. Cheers!
r2mahara said:
This worked for me... Not sure why:
Click to expand...
Click to collapse
Which ROM do you recommend? I want to try this but I want to flash a rom via recovery. Thanks in advance.
grahamgo said:
@r2mahara Thanks for the detailed reply. I am using stock 4.4.3 + xposed (modules DS battery saver, Greenify, gravity box) everything works and battery life is 2 days with average use. Its so good I won't upgrade further (it ain't broke so why try and fix it), that is unless the L version has substantial advantages. You mention xposed and the need to reboot. I believe that this is largely in the past. When I was experimenting and tweaking I don't recall having to reboot at all, or maybe I did the odd soft reboot which is quite quick? - I forget.
Oh, incidently there is a module available that claims to be able to make comprehensive changes to the navbar,
Here is the link
http://repo.xposed.info/module/com.gzplanet.xposed.xperianavbarbuttons
You wrote that everything is working now so this isn't an issue but I thought it was worth mentioning. Cheers!
Click to expand...
Click to collapse
Ok, thanks - Noted about exposed/reboots. I also get about 2 days with slimkat + greenify + mostly on WiFi.
Will keep the link for future reference.
juliospinoza said:
Which ROM do you recommend? I want to try this but I want to flash a rom via recovery. Thanks in advance.
Click to expand...
Click to collapse
The first thing I did when I installed CWM was to make a nandroid backup of the stock ROM - so I used that for the purposes of fixing GPS.
Perhaps there's a stock ROM on these forums that's CWM/TWRP-installable.
r2mahara said:
Ok, thanks - Noted about exposed/reboots. I also get about 2 days with slimkat + greenify + mostly on WiFi.
Will keep the link for future reference.
Click to expand...
Click to collapse
Hi, well at home on WiFi I get 4 - 5 days, so you might like to try the module DS battery saver, of course I normally use the charger at home but I was curious if DS was doing an effective job and spent a bit of time evaluating it. I was happy enough to keep using it and got the Pro version.
I saw a new "nightly" has been pushed out for the Relay. Based on the changelog (fixing integer overflows and underflows), this looks like a fix for Stagefright.
I've updated from within the 20150607 nightly, and so far, everything looks good. My GPS and camera still work fine, and I didn't bother toggling any settings before updating.
At least I have ONE phone with a Stagefright fix. It's kind of ironic that it's the oldest of my Androids.
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
So I guess it's time to bite the bullet and do the double-twist-and-backflip GPS fix. Let me go over this for a moment, to get it straight.
I need a new CWM recovery, latest'n'greatest.
I need and old 10.1 or maybe 10.2 ROM image.
I need the old baseband firmware to go with the old ROM image.
Is this the full list?
There have been numerous links to all three of these, but I tried last week, and at least some of them have gone stale. Does anyone have a current and working set of links for them?
My wife's Relay is still at CM11M8, and really it's about time I got her properly flashed forward, especially now with Stagefright and Freak both fixed. We've locked out on Stagefright so far because we have voice-only through PureTalkUSA, only do data on wifi, and therefore don't do MMS.
GPS fix:
You need a CM10.1 build (Only ones ever produced were 'experimental'), the ICS stock baseband (modem) and the JB stock baseband. Recovery doesn't particularly matter, so long as you can flash images, but I still recommend the CWM that has been around for a while (I've tested it, it works fine even with upcoming Images)
Procedure:
Boot into recovery, run a full backup on your device.
flash ICS baseband
Flash CM10.1 Image
Factory Reset
Boot into system (Not sure if this is needed, but I always do.)
Once system boots up, shut system down.
Open phone, pull battery.
Wait ~30 seconds, replace battery.
Boot phone.
Once system boots up, (If you have a way to test it, GPS should work now). Reboot into recovery.
Flash JB baseband.
Restore your system backup.
Reboot into system. Your GPS should now work with your current system.
I posted a reply into a thread, there was an up to date link with just the modem... I can confirm that running on CM nightly (june something) I have no issues with GPS, wifi 2.4ghz band doesnt work with bluetooth enabled though
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
phred14 said:
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
Click to expand...
Click to collapse
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
dzl said:
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
Click to expand...
Click to collapse
I got my Relay about a year and a half ago for Christmas, mostly as a learning vehicle, but also for the convenience. The plan from the get-go was to put Cyanogenmod on it. For a while it was wifi-only, then a few months later my wife decided she wanted one, and I found the Family Flex Plan at PureTalkUSA that let us have two phones for the the cost of a Virgin Mobile and TracFone. (What we had before) It's also one of the few ways to get voice-only, and use wifi for data.
The Relay is getting a bit long in the tooth, and perhaps most discouraging "aging" side of it is the ramp-down here. However anything I get will be CM-ready from the get-go.
Flashed the latest CM11 nightly today. No major bugs so far with moderate use throughout the day. So much faster than my Xperia with the stock firmware, actually enjoying Android again.
Sent from my SGH-T699 using XDA Free mobile app
20150823
I had been running M8 since it came out until last weekend. Decided to do a complete wipe and try for the newest nightly to fix the Stagefright bug. Things went real smooth. GPS is working faster than ever.
Everything runs like a dream... except the adaptive light sensor. Adaptive brightness is not working at all. I've check the sensors and the Lux sensor is working fine. If I turn on adaptive brightness, and then adjust, the settings crash. Anyone else experiencing anything like this?
Yeah that is one thing that I have noticed as well, the auto brightness doesn't work. Can't say I've attempted to diagnose it at all though.
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
TPMJB said:
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
Click to expand...
Click to collapse
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
phred14 said:
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
Click to expand...
Click to collapse
I would like for updates to CM12, but we only have unofficial versions of CM12. I am a noob at compiling and I hear it is an arduous task to get it working.
Magamo said:
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
Click to expand...
Click to collapse
Some time between then and now (some time in September, I believe) the stagefright fixes were backported to the omni-4.4 branch. I have a build from this running on my relay right now and Zimperium gives it a clean bill of health.
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
kodimagnyl said:
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
Click to expand...
Click to collapse
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
i have a rooted stock rom, can i move to the latest cm11 nightly build?
phred14 said:
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
Click to expand...
Click to collapse
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
kodimagnyl said:
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
Click to expand...
Click to collapse
Can't reach the second link, but I've already got a copy of the current modem, the old one is what I've been missing. Things are starting to get busy, so I don't know how soon I'll be able to try it.
BTW, I've been told to do a "nandroid backup", then wipe and load the back-level stuff, do the GPS fix, then a "nandroid restore". I'm going to presume that the backup / restore doesn't handle the modem, and on my way back from back-level, I'll first have to use heimdall to reload the current modem?
Thanks