Related
I wanted to thank the developers of MR3 in this thread. Liquid, Jester, etc.
I'm a long time lurker of this forum since I got my Thunderbolt. I'm VERY VERY appreciative of the developers for creating a very functional ICS rom for the Thunderbolt. Shame on HTC and Verizon for sandbagging so long with what should be a very simple upgrade for them. I was running Thundershed for awhile but grew tired of the Gingerbread look and feel of Android. My friends all mostly have newer phones with ICS, and I couldn't believe that it was supposed to be out in August and it's now mid-October and it's still not out.
To my surprise, I log on to here and see that an ICS ROM had been released.
My only issues with this ROM are random restarts and the white screen error in Facebook/Gmail/etc. I don't really use the video camera much in general; could you use an aftermarket app, or is it broken period?
Otherwise, I absolutely LOVE this and will never go back to Verizon's bloated software. Even when an OTA is released with ICS I won't go back. My phone is running much faster and much better than with Sense and Gingerbread. With data off I had a 10% decrease in battery in 7 hours; with data on and normal use I'll get maybe 5 hours out of a charge on this ROM. About normal for this phone and it's absolutely terrible battery life with the stock battery.
I have it overclocked to 1.5ghz running interactiveX as my governor. It runs beautifully, other than those two minor issues I pointed out above. I haven't experienced any data drops or anything out of the sort like that.
vashts80 said:
I wanted to thank the developers of MR3 in this thread. Liquid, Jester, etc.
I'm a long time lurker of this forum since I got my Thunderbolt. I'm VERY VERY appreciative of the developers for creating a very functional ICS rom for the Thunderbolt. Shame on HTC and Verizon for sandbagging so long with what should be a very simple upgrade for them. I was running Thundershed for awhile but grew tired of the Gingerbread look and feel of Android. My friends all mostly have newer phones with ICS, and I couldn't believe that it was supposed to be out in August and it's now mid-October and it's still not out.
To my surprise, I log on to here and see that an ICS ROM had been released.
My only issues with this ROM are random restarts and the white screen error in Facebook/Gmail/etc. I don't really use the video camera much in general; could you use an aftermarket app, or is it broken period?
Otherwise, I absolutely LOVE this and will never go back to Verizon's bloated software. Even when an OTA is released with ICS I won't go back. My phone is running much faster and much better than with Sense and Gingerbread. With data off I had a 10% decrease in battery in 7 hours; with data on and normal use I'll get maybe 5 hours out of a charge on this ROM. About normal for this phone and it's absolutely terrible battery life with the stock battery.
I have it overclocked to 1.5ghz running interactiveX as my governor. It runs beautifully, other than those two minor issues I pointed out above. I haven't experienced any data drops or anything out of the sort like that.
Click to expand...
Click to collapse
I second this thread.
A major thanks goes out to all of you who develop, in any way, for the Thunderbolt community. This even includes testers.
To answer your questions...
The video and front camera are broken even with an aftermarket app and will remain broken, most likely, until Verizon releases the OTA. From the OTA, our awesome developers will then be able to fix camera issues and many other issues that will make their ROM's 100% stable.
Also, if you get random reboots, you may want to flash to a different radio.
If you are currently running the OTA radios from the 2.11.605.19 software and still get these reboots, try flashing the combo radio and hopefully the reboots will vanish or, at least, happen less often.
If you go to your settings, about phone, software information, more, and look at the baseband version...
If the numbers you see are:
1.49.00.0406w_1, 0.01.79.0331w_1
Then you are on the OTA 2.11.605.19 radios, which is my recommendation for the radios to use with this ROM. If these are the radio numbers you see, try the combo radio. If the numbers you see under your phones baseband version is not:
1.49.00.0406w_1, 0.01.79.0331w_1
Then it may be:
1.48.00.0930w_3, 0.01.78.0916w_3
If it is:
1.48.00.0930w_3, 0.01.78.0916w_3
Try flashing the 2.11.605.19 OTA radios found here:
http://forum.xda-developers.com/showthread.php?t=1605557
If you have the 2.11.605.19 radios, though, try flashing the combo radio found here:
http://forum.xda-developers.com/showthread.php?t=1864157
If you aren't sure how to flash a radio, here's a video tutorial for you to follow:
http://www.youtube.com/watch?v=eu-KLjHGGhc&sns=em
Sent from my ADR6400L using xda premium
Definitely want to ditto this thread. Thanks for continuing to support the Thunderbolt. I was on the verge of retiring the Thunderbolt. ICS has brought new the Tbolt new life though!
thanks for the links. I'm going to try upgrading tonight and see if that helps. I notice you flash the radio in hboot. If I do a nandroid backup, does it also backup the radio (so I can restore it)? Or if I **** up, will it be permanently bricked?
Ditto to all that has been said. Thank You to all who made this happen, including HTC and Verizon. Their inaction drove me to decide to root and find alternatives. I've been incredibly pleased with MR3.
Thanks all!
Sent from the Great Beyond using XDA App
vashts80 said:
thanks for the links. I'm going to try upgrading tonight and see if that helps. I notice you flash the radio in hboot. If I do a nandroid backup, does it also backup the radio (so I can restore it)? Or if I **** up, will it be permanently bricked?
Click to expand...
Click to collapse
If you backup that ROM after flashing the radio, it will back up the ROM. Hboot is a whole different thing than the recovery. That radio is downloaded to the phone and will automatically run on any ROM after its downloaded, even if you start from scratch. But flashing any of those two radios will not brick you on any ROM. Worst case being you won't have signal or data until you flash different radios again.
Say if you upgraded to the newer radios, and then you flash a ROM based on an older software version, you won't brick. In fact, you may not ever experience any issues. Maybe just signal changes or random signal drops.
But no, it won't brick you. It's almost impossible to brick a Thunderbolt.
I recommend after flashing the new radios, immediately go and either change the name from PG05IMG to something custom, move into a different folder that's off of the root of the SD card, or just delete it once flashed.
This is for in a such case where you need to get back into recovery from hboot, it won't prompt you to install the radio again. Because if you had to get into recovery from hboot, it wouldn't allow you to since it runs a check for the PG05IMG files first... and with that being said... I was always told to never flash the same radio twice without changing to a new one first.
Sent from my ADR6400L using xda premium
i dont' see why these ROMs get so much acclaim... when i tried LiquidSmooth it wouldn't stay connected to the Internet. tried to toggle wifi and 3G/4G. nothing works and i have to reboot the phone every time i want to use the Internet.
Liquid MR3: the setup crashed and now the ROM won't even come all the way up...
unless my phone's broken or something (going to Verizon tomorrow to reflash and check it), i say they're both absolute garbage. i've had much better luck with ROMs on other phones.
moonlightcheese said:
i dont' see why these ROMs get so much acclaim... when i tried LiquidSmooth it wouldn't stay connected to the Internet. tried to toggle wifi and 3G/4G. nothing works and i have to reboot the phone every time i want to use the Internet.
Liquid MR3: the setup crashed and now the ROM won't even come all the way up...
unless my phone's broken or something (going to Verizon tomorrow to reflash and check it), i say they're both absolute garbage. i've had much better luck with ROMs on other phones.
Click to expand...
Click to collapse
Did you try a different radio and redownload? The first shot isnt always the right one....
trter10 said:
Did you try a different radio and redownload? The first shot isnt always the right one....
Click to expand...
Click to collapse
whelp... as you can see from my post number, i'm not exactly the most well-versed member around. idk what that means. any reading you can point me to or explanation?
moonlightcheese said:
whelp... as you can see from my post number, i'm not exactly the most well-versed member around. idk what that means. any reading you can point me to or explanation?
Click to expand...
Click to collapse
Back up 9 posts and you'll see a link to a video tutorial on how to flash a different radio. You'll even see 2 links to 2 different radios to flash and try.
Sent from my ADR6400L using xda premium
RBarnett09 said:
Back up 9 posts and you'll see a link to a video tutorial on how to flash a different radio. You'll even see 2 links to 2 different radios to flash and try.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
well i reflashed Liquid this morning and it didn't crash this time, connected fine via wifi and setup completed properly.
all of my radio issues were on the old version (not sure if there's a difference in radios or whatnot), but if it acts up again i will try your recommendations. thanks a lot.
---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------
moonlightcheese said:
well i reflashed Liquid this morning and it didn't crash this time, connected fine via wifi and setup completed properly.
all of my radio issues were on the old version (not sure if there's a difference in radios or whatnot), but if it acts up again i will try your recommendations. thanks a lot.
Click to expand...
Click to collapse
ah i see what happened now.
the first time i flashed it, i cleared /data after the flash before i brought the OS up, but you've included the launcher as a user app and not a system app. was this intentional? a user could easily screw up by uninstalling the launcher and have no way to interact with the OS. shouldn't there be a default launcher embedded in the system programs?
i'm an Android dev, but my understanding of system development is limited, but if i'm not mistaken, any Android ROM should come with a default launcher that is not uninstallable and has no icon as a backup launcher just in case.
He did install it that way so if the user wants to install their own launcher and remove the default. Its simple to make the new one a system app. All that has to be done is move the apk to /system and it is uninstallable.
Sent from my Thunderbolt using Tapatalk 2
The GPS takes 5 minutes to lock, and it does it at 1600 meters (un)accuracy.
It behaves like this no matter what rom i try (Sky, Slim, CM9/10, Embryo etc), except for stock Rogers ICS.
The agps patch and other gps patches on XDA didn't do anything.
When i first bought it, it had stock Rogers ICS and GPS worked perfectly, never mind the fact that i live in EU.
Then i tried custom roms and it started to funk around and has been doing as long as i run a custom rom.
Today i installed Rogers ICS as a last resort and suddenly the GPS locks in seconds and with great accuracy too (9 meters).
And so the question, what the hell is causing this?
OR
How do i make the GPS work with the custom roms?
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
rpr69 said:
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
Click to expand...
Click to collapse
I'm not sure either.. The phone is canadian with a Rogers brand on battery cover. When i install a stock AT&T rom the GPS more or less dies.
Any other rom and the GPS dies. Stock Rogers ICS rom and voila works like a clockwork.
And it doesn't react at all to any GPS patch, and i've tried like 10 different ones. aGPS is not new to me, i've successfully used it on other phones. But for some reason it doesn't do anything for my Skyrocket.
Mike on XDA said:
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
Click to expand...
Click to collapse
Thanks i'll try that, just don't see how Aroma is going to help if it's the same patch i've tried earlier.
On the other hand, with ghouly issues like this who knows what might help and what won't ?
Worst case scenario is that i'll be stuck with Rogers FW if i want working GPS, which is acceptable with some tweaks especially the Droid Razr M launcher
The thread is here: http://forum.xda-developers.com/showthread.php?t=1732304
--------------------------------------------------------------------
Sent from my Skyrocket i727 running Team Dirt
--------------Nexus 7 running AOKP PUB--------------
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
icenight89 said:
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
Click to expand...
Click to collapse
Nope, it's always turned on.
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Jack_R1 said:
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Click to expand...
Click to collapse
Hi Jack_R1
Software does indeed solve everything. In short: stock rogers ics rom = perfect gps, custom rom/stock at&t rom= no gps.
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Jack_R1 said:
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Click to expand...
Click to collapse
1 The AT&T roms didn't give me an adequate lock, until the JB updates were leaked & released.
2 I'm always using automatic APN's but they don't have any GPS info.
Haven't tried #3..
4 FasterFix didn't help.
5 GPS Status shows 4-7 satellites and only 2-3 locks with horrible accuracy. The thing is now i get perfect locks with any ROMs.. I could've disallowed Google Services to use GPS as I might've confused it with Google Search & Ads wanting my location..
Thanks for your help :good:
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:
Has anyone attempted to install the base LineageOS on their Verizon m8?
If so, what was the level of success? Does everything work?
yes its sweet
yatman60 said:
Has anyone attempted to install the base LineageOS on their Verizon m8?
If so, what was the level of success? Does everything work?
Click to expand...
Click to collapse
I am using LineageOS on my VZW m8. I am having issues with my data disconnecting intermittently. Everything else seems to be working fine.
So ...glad I found this thread, as I was going to create my own (though I think general might be a better place for it...I'll suggest to mods).
Hopefully this can be a good place for all of us VZW M8 users to discuss our LOS experiences.
I just started looking for a new ROM after months of hating the stock MM update. I'm hoping to get another year or so out of my M8.
So far I have narrowed it down to:
NuSenseSeven - A really nice Sense 7 MM build that doesn't seem to have the performance issues of stock MM.
Wolla - Nice clean Sense 8 MM build with a healthy collection of tweaks to configure.
Lineage (LOS) - Nougat build for M8 (only one?). Clean, fast AOSP-like ROM with ability to build extremely light and add what you need from gapps.
So far these are my main issues with Lineage after trying for only a few days:
Not HTC specific. So you are going to lose out on some HTC tools and menus. Something like HTC Connect to cast media, or the comprehensive gesture support HTC has. Some of these you can get back through third party apps, but not all of it and not really as well integrated as you get with HTC/Sense. There are about 5-10 things that a ROM like Wolla has that I can't find the same settings in LOS. Basically I'm deciding if I want to lose out on those to get the benefits on being on the latest possible Android for the phone.
Right now I'm leaning 80% yes on LOS, but I might decide to go back to Wolla or NuSenseSeven. I would need to do some more testing between those two before I decided on which one though.
Although there is a lack of some features in those ROMS, there are other features that you will only get in LOS like the updated Nougat notification system, Privacy Guard, and maybe a few others. So you need to choose what is best for you.
As far as speed/stability/etc. So far I have been really impressed with LOS, though all builds I mention have been way better than stock MM in the few days I've been testing. Here are the only known issues/bugs that I have had with LOS so far:
1) NFC icon. The NFC icon doesn't appear in the status bar, so you can't see at a glance if it is enabled (you can see it in quick launch though). I think this is a regression and there is a bug listed for it. I actually haven't tested the NFC yet though, but it appears that it works, just no notification icon.
2) Double list of APN in mobile settings. This is just a display bug...for some reason the menu option is there twice.
3) I too have had some data/connection issues, but I am not ready to rule the ROM as the issue yet. Basically on the quicklaunch bar it was showing my data connection as "No service" instead of "Verizon Wireless." It would say Verizon sometimes, but not always. I couldn't tell if this was an issue with the display or not because my other ROMS didn't have a comparable icon, so I had to start looking at the hidden phone menus to see what my connection was saying. Sure enough, my phone didn't appear to be getting a carrier name listed when I was using LOS most of the time, but it was there all the time (at least all my testing time) on other ROMs.
As I was trying to compare/troubleshoot this by flashing different ROMS and radios at some point I got to a point where my 4G wouldn't work at all (stuck at 3G). This was the case even when flashing back to pure stock everything. I spent the better part of a day working on this and couldn't find the solution until I found a few other threads of people discussing no 4G connection and the only solution was a new SIM card. Sure enough I got a new SIM from Verizon today and 4G came back immediately. I reflashed LOS and on boot it shows I'm on Verizon, so I'm hoping it stays.
Stumbled into this thread last week, and was curious. Currently running LineageOS 14.1-20170727 and I'm impressed. Been running fine for about a week now with no major issues. Getting a slightly better battery life, better responsiveness, and good 4G connectivity.
Only minor issues have been spotty WiFi connection, though it might have just been due to a weak signal. That and USB tethering doesn't appear to be working yet. Wifi Tethering seems to work fine though.
**Edit** USB tethering does work. Don't know why it wasn't earlier. Perhaps a bad USB cable
How to get it?
I'd like to try this ROM on my M8. Did you guys just flash the ROM for the regular M8 not a ported Version?
If yes, is it safe to do that. I have the GPE ROM installed on my M8 running GSM not CDMA.
Thanks!
Mohamed Yehia said:
I'd like to try this ROM on my M8. Did you guys just flash the ROM for the regular M8 not a ported Version?
If yes, is it safe to do that. I have the GPE ROM installed on my M8 running GSM not CDMA.
Thanks!
Click to expand...
Click to collapse
Yeah, I just tried out the regular M8 version "One 2014 (m8)", and it worked just fine. No special setup coming from the GPE Rom, other than a full wipe. ( That's what I was running as a daily driver before ) It took a long time for the first boot, and it even rebooted on its own after the initial flashing and reboot. Give it a try. I've been really happy with it thus far.
working well except roaming
I've been running lineage on my verizon M8 for a couple months with excellent results - except when I'm out of the country roaming. In Canada and now Chile the same thing is happening - the network appears for one second, then gone the next, and repeat. Sometimes it's connected long enough for a text to get through, but not enough for any data usage. And it keeps asking me to select my sim card, and of course I have only 1.
LOS 15 is amazing. Everything works perfectly fine. I just wish LOS performed as smooth as Sense based ROMs
Any custom kernels available for M8s running LineageOS?