Database Info

Thank you to the developers of MR3

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

[Q] [HELP] CM 9.1 intermittent crashes

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.

[Q] problem with S3 GPS ... and audio out?

I've been fighting with the cm11 d2lte builds since I updated to a nightly in the beginning of September; since then (I believe the 9/7 nightly was the last one that worked), I've had trouble with GPS losing locks, or getting locks at all. I tried several nightly updates in hopes this was a known and fixed problem, as I've seen many complaints about GPS in cm11, but none of the nightly or snapshot updates helped, and some made things worse.
I have tried everything I could find, including toggling between Maps and other map/GPS related apps, full ROM wipes and fresh installs, wipes to flash stock firmware and then come back to cm11 after getting a GPS lock in stock, 3rd party apps like GPS Status to update/wipe aGPS (assisted) data, etc. The state my phone is in now is:
- Did a full wipe of data and cache partitions
- Installed stock backup, got a GPS lock, and rebooted
- Wiped again and installed the most current cm11 snapshot for d2lte (11-20141008-SNAPSHOT-M11-d2lte)
- Using GPS Status and toggling between Maps and Waze to try and get GPS locks
I'm able to get a lock sometimes, but not often enough and not when I need one most: Maps recently turned a 1.5 hour trip into a 3.5 hour nightmare with a really bad route and no ability to reroute.
As an afterthought, I realized that when I'm in my car, I'm usually using the phone for 2 things:
- GPS/maps
- audio output from headphone jack to car aux input
While playing with GPS on the way home today, I unplugged my audio cable from the headphone jack ... and I suddenly got a GPS lock. Plugged the audio cable back in, and lost the lock. Pulled it again, and got a lock. WTF? I've been fighting with this for a month, and don't think I've seen a single mention of audio affecting GPS.
Can anyone else possibly verify this? And any suggestions on a fix?
Thanks!

I've read before that tightening the screws inside the back of the battery sometimes solves this issue
From my Wicked S3 on SOKP

Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.

ShapesBlue said:
I've read before that tightening the screws inside the back of the battery sometimes solves this issue
Click to expand...
Click to collapse
Not sure what you mean, but if you mean the 10 screws surrounding
the frame, I've tried tightening them. I don't know of any screws on or beneath the battery.

MrBrady said:
Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.
Click to expand...
Click to collapse
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?

deesto-xda said:
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?
Click to expand...
Click to collapse
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.

MrBrady said:
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.
Click to expand...
Click to collapse
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.

deesto-xda said:
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.
Click to expand...
Click to collapse
Most custom roms are based off other roms, aicp is one of the many. I switched directly to CM11 today because I was on another version of a cm based rom and the reboots were too much for me.
From my CM11 S3

Cyanogenmod 13 for ATT D850 UNOFFICIAL

I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
Official builds are out and can be found here...
https://download.cyanogenmod.org/?device=d850
I used the 6.0 micro build gapps from here
http://opengapps.org/

SupaAvenger79 said:
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
I used the 6.0 micro build gapps from here
http://opengapps.org/
Nightly Build available here..
https://drive.google.com/folderview?id=0B4rZYkaJF5V0Z3RlR08yclZiVUE&usp=sharing
Click to expand...
Click to collapse
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?

crash4fun said:
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
Click to expand...
Click to collapse
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.

[Thanks! Will definitely follow this until CM puts out an official build. Couple other guys that were building unofficial seem to have stopped for the time.

SupaAvenger79 said:
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
Click to expand...
Click to collapse
Ah, yes it appears to get a lock for me as well, but then won't navigate. I've tried messing with gps.conf in several different manners but no luck.

I'm about to abandon the G3 because there is no official CM support. This is where Cyanogenmod is getting bad press - they claim to offer an alternative OS with the latest updates, but some phones are just left in the dust because no one wants to be the maintainer. Best Buy has started selling the 6P - may head over and pick this up!

Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.

KennyG123 said:
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
Click to expand...
Click to collapse
Sure thing
https://github.com/CyanogenMod/android_kernel_lge_g3

Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!

scsgoal31 said:
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
Click to expand...
Click to collapse
Yeah I am hoping the problems are not D850 specific or we will never see a fix. I will keep posting builds semi nightly until CyanogenMod starts posting an official build or until I get a new phone in August. I really think this is still a good phone and wonder why the community went to hell on this one.
Have a Happy New Year everyone.

I've been using CM13 for almost a month and its been great. However I only just got an SD card for Christmas. Now, I'm assuming moving apps to the SD card has changed since it let's you format as internal storage now. However that doesn't work for me. Does anyone know how to move apps to the SD card without formatting it as internal storage?

How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.

slabity said:
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
Click to expand...
Click to collapse
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
https://source.android.com/source/initializing.html
Then I made a local manifest to include proprietary drivers from https://github.com/TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.

SupaAvenger79 said:
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
Then I made a local manifest to include proprietary drivers from TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
Click to expand...
Click to collapse
Strange. That's exactly what I did too.
I'll give it another shot and see what's going on. I'd like to take a crack at fixing some of the bugs.

Looks like tonight's build will fix the power charging issues. Yay!

Just posted the the 12/29 build and GPS is fixed we can now find our nearest Hardee's with ease. Thanks @invisiblek

is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk

xVermicide said:
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I had data problems too on Tmo, a quick APN adjustment fixed it:
https://support.t-mobile.com/thread/95900?start=0&tstart=0

thanks, I applied the changes so I'll see if I have anymore problems. if not then this 13 is my new daily driver.
Sent from my LG-D850 using Tapatalk

Just flashed, great so far! Thanks OP!
Sent from my LG-D850 using Tapatalk

LineageOS

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?