[Q] [ROM] CyanogenMod 11 with 3.0.16 kernel - Network connectivity - HTC Sensation

Hi
I have successfully flashed the ROM from sultan on my device. I started off with the 1st of July build and could practically watch my battery drain on it.
Since I updated to the 25th of July build this seems to be solved and the ROM makes a very good impression, except that I'm having a hard time getting connection to my carrier. I was able to do one call after rebooting the device and after that it dropped off again. Even if I manage to keep it connected for a few minutes, mobile networking never works. On the other and wireless works like a charm.
As i have read through most of the related forums and somehow nobody else seems to have this problem, I'm wondering if I might have done something wrong during the upgrade process? I skipped wiping anything, as that should not be necessary when updating from same ROM.
Anyone had a similar problem? Any ideas?
Cheers,
Espen

I've had this issue too. It seems It only affects Kit Kat builds based on AOSP (Carbon / Uno / CM etc). Mind you we don't have sense one to test do we, so it could be all 4.4 roms. Don't know why. I can't figure it out.
Are you super CID by any chance? Or do you know if you CID matches your current carrier?

Related

[Q] Phone (G2X) Freezes after long calls

Hi,
I rooted my phone a couple of days back & upgraded to ICS using Hellfire v1.8 rom.
Since I was getting lags, I also got the flak0's lag fix.
I have started facing an issue the phone would freeze post a long call on the phone screen, I can't even get it to reboot by pressing 'lock+vol up' button. The only way is to remove the battery & put it back.
I saw a similar issue seen in this thread from partzman2:
http://forum.xda-developers.com/showthread.php?p=28342782#post28342782
But unfortunately, I am unable to comment on the thread as I don't have enough posts in my name. I searched the forums for this issue, but couldn't find a solution.
Any help is appreciated.
My sincere thanks to dev folks
Just wanted to take a moment to thank the dev folks who put in a lot of work in creating these roms/mods - experience is so much better, I can't even begin to explain.
I have had g2x for more than 14 months now & I had been running stock froyo 1st & then GB (2.3.3) - the experience was so bad, that I used it only for making phone calls or occasional emails, as i couldn't even browse or do anything w/o hitting some problem or the other. Even phone calls used to crash at times.
After updating to ICS, I haven't stopped using the phone be it browsing, watching you tube videos, trying new apps, emails etc, with occasional phone calls .
Again, thanks a lot for so much hard work, its really appreciated.
gg84 said:
Just wanted to take a moment to thank the dev folks who put in a lot of work in creating these roms/mods - experience is so much better, I can't even begin to explain.
I have had g2x for more than 14 months now & I had been running stock froyo 1st & then GB (2.3.3) - the experience was so bad, that I used it only for making phone calls or occasional emails, as i couldn't even browse or do anything w/o hitting some problem or the other. Even phone calls used to crash at times.
After updating to ICS, I haven't stopped using the phone be it browsing, watching you tube videos, trying new apps, emails etc, with occasional phone calls .
Again, thanks a lot for so much hard work, its really appreciated.
Click to expand...
Click to collapse
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here: http://download.cyanogenmod.com/?type=nightly&device=tenderloin
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Blazing angel said:
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here:
[//gg84 - I had to snip out the link as I am not even allowed to post a link which actually someone else had put & I am just quoting //]
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Click to expand...
Click to collapse
Thanks for the info. Actually, I went through quite a bit of dev threads before deciding to go with ICS - I was quite curios about its features & was ready to take the risk.
Only thing is that owain's recent 79 build seemed to have quite a bit of issues from the posts, & hellfire seemed a bit old/stable, so went with that. I didn't consider using old owain's builds (which might be an overlook from my part).
Is there a way I can find what I might lose (& possibly gain), if I switch to owain's 77 build?
I am using Jul15, 2011 baseband & kernel is 2.6.32.59-CM9-faux123-050.
Is there a better baseband/kernel that I should try?
I switched the kernel to harsh kernel & I feel that the speed has improved, but "freezing on a call randomly" issue still exists. Also, it crashes & reboots once in a while but I still feel that its worth all the pain as now I am actually able to make use of the phone.
Blazing Angel, did you find the latest baseband which I can try using?
Another bug I found is that I cannot really configure the lock screen buttons/shortcuts - as in adding a an app to be able to accessed from the lock screen like we do for camera. I see the option of changing this in setting but it doesn't persist when I try to change it.
Anyone seeing this?
gg84 said:
I switched the kernel to harsh kernel & I feel that the speed has improved, but "freezing on a call randomly" issue still exists. Also, it crashes & reboots once in a while but I still feel that its worth all the pain as now I am actually able to make use of the phone.
Blazing Angel, did you find the latest baseband which I can try using?
Another bug I found is that I cannot really configure the lock screen buttons/shortcuts - as in adding a an app to be able to accessed from the lock screen like we do for camera. I see the option of changing this in setting but it doesn't persist when I try to change it.
Anyone seeing this?
Click to expand...
Click to collapse
The latest baseband is march 2012. To update, you need to install Tmobile's V21Y update.
Follow this guide
http://forum.xda-developers.com/showthread.php?t=1674901
Note: If you install this, and try to use a rom other than CM7 7.2.0, you need to flash owains New_baseband fix after flashing a rom from here
http://owain.hopto.org/T-Mobile LG...w_baseband.zip
Hi just want to add info with new baseband the bluetooth doesn't work.
Blazing angel said:
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here: http://download.cyanogenmod.com/?type=nightly&device=tenderloin
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Click to expand...
Click to collapse
some of that i experienced my self , most of the times the camera and hdmi port is sacrificed in the g2x
Thanks for the info guys. Say my gps works/locks already (takes a bit of time though) with the hellfire ICS, is there anything I get by flashing this new baseband?
Does it or would it fix the random freezing on calls by any chance?
Basically, I read the instructions & it seems that I'd have to go back to stock, unroot & then re-root + reflash + restore my apps etc - seems like too much if I am not getting something out of it.
If it doesn't add much value, then I will consider doing it once another stable version of hellfire or owain's rom is released..
BTW, did anyone experience the lock screen config issue I posted in my earlier post - basically I can't add custom short cuts to the lock screen, there is an option to do this in the settings but they dont stick (I am on hellfire v1.8 right now)

[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.

Stock 4.1.2 on Sim Modded phone

Been running cm 10.2.1 for a bit now its works but has several issues, and was wondering if the Stock Rom 4.1.2 capable or running GSM? i know once flashing it back ill need to unlock the radio, but is it capable, CM is nice but too many little issues to make it practical on the photon q
so is it possible, if so how?
or is it not possible, why?
Why aren't you running a newer ROM, e.g. CM11? It's under the device name of "moto_msm8960".
Sent from Google Nexus 4 @ CM11
havent been running a newer rom because i hadnt gotten around to updating the recovery for flashing CM 11 since the photon q is no longer supported offfically by any of the updates and there arent currently any stable releases of CM 11 only nightly builds
Most of the Issues im dealing wirh are annoying and id rather not repeat them if i didnt haveto, many folks are still complaining about the broken data hand shaking issues for 3g data
Morecrabs said:
havent been running a newer rom because i hadnt gotten around to updating the recovery for flashing CM 11 since the photon q is no longer supported offfically by any of the updates and there arent currently any stable releases of CM 11 only nightly builds
Most of the Issues im dealing wirh are annoying and id rather not repeat them if i didnt haveto, many folks are still complaining about the broken data hand shaking issues for 3g data
Click to expand...
Click to collapse
Man, the only time to crank out a stable build is when the next Android version is out... Don't expect stable releases in the middle of something. Nightlies have always been stable for me. And isn't updating the recovery a simple one-time thing?
Sent from Google Nexus 4 @ CM11
Morecrabs said:
havent been running a newer rom because i hadnt gotten around to updating the recovery for flashing CM 11 since the photon q is no longer supported offfically by any of the updates and there arent currently any stable releases of CM 11 only nightly builds
Most of the Issues im dealing wirh are annoying and id rather not repeat them if i didnt haveto, many folks are still complaining about the broken data hand shaking issues for 3g data
Click to expand...
Click to collapse
Photon Q is officially supported by CyanogenMod (I'm maintainer).
http://wiki.cyanogenmod.org/w/Moto_msm8960_Info
I recommended to use OpenRecovery 2.09, download link can be found here: http://forum.xda-developers.com/showpost.php?p=48551561&postcount=75
CM11 is what I run on my phone and I'm not aware of any issues worth mentioning.
I have no idea what you mean by
broken data hand shaking issues for 3g data
Click to expand...
Click to collapse
. If people complain but don't post
Code:
adb logcat -b radio
, there's no way to help them. My data work fine.
(Issues reported by CDMA users are something else, outside of my scope as I'm in GSM land, but CDMA fixes are still in progress in the generic CM code).
When I search https://jira.cyanogenmod.org for xt897, I see only three bug reports.
There's not much moto_msm8960 specific progress happening right now as we mostly wait for the release of 3.4 kernel source by Motorola (it would be waste of time to backport more 3.4 code to our current 3.0 kernel as 3.0 will become obsolete hopefully soon).
Anyway, back to your original question: you can use the stock 4.1.2 firmware on SIM modded Q just fine.
on version 10.2.1 I had issues with 3G data, I had data when the Phone was connected with H+ but the Moment it switched to 3G i lost Connectivity, after a small amount of Google searching I found other folks had this issue as well except the Photon Q community had Not reported this issue explicitly, the Loss of 3G isnt something most would notice since the Coverage has been improving Signifcantly but for me in my area its fairly apparent because its more Rural, so we have some holes in the At&ts 4g coverage
I installed the Latest 2.7 Twrp and flashed CM11 Nightly lastest, working ok, but the Install of Gapps Keeps failing, this phone being my daily driver i want it to be as seamless as possible
Flashed latest Nightly and 3-22_gapps_Standard_4.4.2_Signed.zip
its failing on the gapps install
the 3G issues on the Nightly seem eliminated as i Havent Noticed the Coverage Loss as of yet, but was hoping to Get Ingress Running which made the Loss of Connectivity very apparent Go resistance!
thank U for the reply guys, I really do appreciate your works and didn't mean to come off as a whiner, just need it to work seamlessly since its a daily driver and this roms are experimental and Im no expert, I really do enjoy the Features Implemented and the Debloating especally but simply wondered if the stock would be able to provide me a more stable environment until till more kinks got worked out
Morecrabs said:
on version 10.2.1 I had issues with 3G data, I had data when the Phone was connected with H+ but the Moment it switched to 3G i lost Connectivity, after a small amount of Google searching I found other folks had this issue as well except the Photon Q community had Not reported this issue explicitly, the Loss of 3G isnt something most would notice since the Coverage has been improving Signifcantly but for me in my area its fairly apparent because its more Rural, so we have some holes in the At&ts 4g coverage
I installed the Latest 2.7 Twrp and flashed CM11 Nightly lastest, working ok, but the Install of Gapps Keeps failing, this phone being my daily driver i want it to be as seamless as possible
Flashed latest Nightly and 3-22_gapps_Standard_4.4.2_Signed.zip
its failing on the gapps install
the 3G issues on the Nightly seem eliminated as i Havent Noticed the Coverage Loss as of yet, but was hoping to Get Ingress Running which made the Loss of Connectivity very apparent Go resistance!
thank U for the reply guys, I really do appreciate your works and didn't mean to come off as a whiner, just need it to work seamlessly since its a daily driver and this roms are experimental and Im no expert, I really do enjoy the Features Implemented and the Debloating especally but simply wondered if the stock would be able to provide me a more stable environment until till more kinks got worked out
Click to expand...
Click to collapse
I am based in Australia where 3G 850mhz GSM band is used on a sim modded phone. I am running ICS. did you manage to get gapps installed?

[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

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?

Categories

Resources