CyanogenMod 12.1 Unofficial
For the HTC EVO LTE 4G (jewel)
Requirements
You need to be on the new partition layout, have S-OFF, and have Captain_Throwback's TWRP recovery.
Installing
Download the ROM.
Download the appropriate GAPPS
Boot into recovery.
Wipe system and data.
Install the ROM.
If you wanted GAPPS install them.
Wipe cache and dalvik cache.
Reboot (this will take several minutes)
Profit
Bugs
Release is unofficial & very new. Hope for the best, but prepare for random reboots and instability.
My phone is no longer activated, so all I have is WiFi on this device. Please let me know if you have issues with data.
Sources
ROM
Kernel
Downloads
ROM Download​
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sprint HTC EVO 4G LTE
Contributors
fizbanrapper
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: hboot 2.10+
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-08
Last Updated 2015-04-07
Reserved
Reserved
You actually don't have to have S-OFF to get this to work. I have never been able to get that unlocked on my device, because I updated to the new partition table, and I've never seen a successful way to get S-OFF from 2.10+. Anyway, what I do is flash like normal, then I extract the boot.img from the .zip and then run "fastboot flash boot boot.img" under fastboot, and you're gold.
Thanks for the update. You get a gold star for being the first Jewel 5.1 builder.
So is anyone anyone up and running this yet? If so, how is it? I really like the Pacman build as well as DU but DU keeps locking up on me as I get almost all of my apps installed... Especially themes. Greatly appreciate the continued new builds though!:thumbup::thumbup:
Sent from my EVO using Xparent Gray Tapatalk 2
I have to download CM12.1 ASAP! I have been running the latest CM12 nightly and it has been working well along with the builds from this dev!
On a side note, I read that Spirit FM Radio 1 stopped working after KitKat and that the new Spirit FM 2 broke on this device with the kernel after CM11 but I decided to try it anyway and its working just fine! Most Nexus, Samsung, Motorola, etc devices have the hardware disabled but the good old Evo 4G LTE is still going strong!
Oh, I am running the Beta version of Djdarkknight's BlakKat theme...not sure if its public yet but best bet is to check Team Blackout site or inverted/transparent apps app:thumbup::thumbup:
Sent from my EVO using Xparent Gray Tapatalk 2
JohnCorleone said:
So is anyone anyone up and running this yet? If so, how is it?
Click to expand...
Click to collapse
I've been running it for a couple of days.
GOOD
I haven't seen any FC issues, which is very good.
Data works fine, and cell strength seems to be normal.
I also like being able to use the new Gapps package, which is more up to date, with 5.1. That's not particular to this ROM, though.
BAD
I have had random reboots every few hours with this.
I'm pretty confident that it's not showing the proper cell strength, because it lists no bars, although it seems normal.
I couldn't get the Gmail widget to work with this. I had to resort to using the stock email app, which isn't nearly as nice.
At the end of the day, this ROM isn't ready to replace the solid 5.0 build yet. I wouldn't recommend it for a daily driver. But hey, this is really early in the game. In a couple of weeks or in a month, things will probably be right as rain.
ocarinaz64 said:
I've been running it for a couple of days.
GOOD
I haven't seen any FC issues, which is very good.
Data works fine, and cell strength seems to be normal.
I also like being able to use the new Gapps package, which is more up to date, with 5.1. That's not particular to this ROM, though.
BAD
I have had random reboots every few hours with this.
I'm pretty confident that it's not showing the proper cell strength, because it lists no bars, although it seems normal.
I couldn't get the Gmail widget to work with this. I had to resort to using the stock email app, which isn't nearly as nice.
At the end of the day, this ROM isn't ready to replace the solid 5.0 build yet. I wouldn't recommend it for a daily driver. But hey, this is really early in the game. In a couple of weeks or in a month, things will probably be right as rain.
Click to expand...
Click to collapse
Thanks for the feedback! I am grateful that fizbanrapper is compiling these different Lollipop ROMs because they are running exceptionally well on this device.
Sent from my EVO using Xparent Gray Tapatalk 2
JohnCorleone said:
Thanks for the feedback! I am grateful that fizbanrapper is compiling these different Lollipop ROMs because they are running exceptionally well on this device.
Sent from my EVO using Xparent Gray Tapatalk 2
Click to expand...
Click to collapse
Actually, I don't know what's going on recently, but I can't get mobile data to work on ANY recent builds (Cyanogenmod, LiquidSmooth, PacRom). Not even my own AICP builds anymore. I don't know if there is a new setting that I need to fiddle with, or what. Nobody else seems to be having this problem. This CM 12.1 build is the only new one that works for me now. Otherwise, I have to go back to my AICP build from several weeks ago. Has anyone else experienced this? Know how to fix it? I use Ting (Sprint) network.
EDIT
I found the answer by @fizbanrapper! Now I think I'm gold.
ocarinaz64 said:
Actually, I don't know what's going on recently, but I can't get mobile data to work on ANY recent builds (Cyanogenmod, LiquidSmooth, PacRom). Not even my own AICP builds anymore. I don't know if there is a new setting that I need to fiddle with, or what. Nobody else seems to be having this problem. This CM 12.1 build is the only new one that works for me now. Otherwise, I have to go back to my AICP build from several weeks ago. Has anyone else experienced this? Know how to fix it? I use Ting (Sprint) network.
EDIT
I found the answer by @fizbanrapper! Now I think I'm gold.
Click to expand...
Click to collapse
Yeah, I switched to T-Mobile (I was on Sprint and T-Mobile for a while) so my Jewel, Sprint Galaxy Nexus and Nexus S 4G are all WiFi only devices so if WiFi works, I am good. In fact, the WiFi range on this build is much greater than my HTC One M7 on T-Mobile.
I guess its a moot point because next week I am ordering either the SIM unlocked Nexus 6 or the SIM unlocked M9 directly from Motorola or HTC. I am still trying to decide which. My M7 is SIM unlocked as well but that only helps those on GSM.
If anyone is hurting for a Sprint device, I have a few older ones but they are in great shape...especially this Jewel! Its like a new device since flashing Lollipop
Sent from my EVO using Xparent Gray Tapatalk 2
JohnCorleone said:
If anyone is hurting for a Sprint device, I have a few older ones but they are in great shape...especially this Jewel! Its like a new device since flashing Lollipop
Sent from my EVO using Xparent Gray Tapatalk 2
Click to expand...
Click to collapse
I you want to get rid of your phones, you should list them on Swappa.
ocarinaz64 said:
Actually, I don't know what's going on recently, but I can't get mobile data to work on ANY recent builds (Cyanogenmod, LiquidSmooth, PacRom). Not even my own AICP builds anymore. I don't know if there is a new setting that I need to fiddle with, or what. Nobody else seems to be having this problem. This CM 12.1 build is the only new one that works for me now. Otherwise, I have to go back to my AICP build from several weeks ago. Has anyone else experienced this? Know how to fix it? I use Ting (Sprint) network.
EDIT
I found the answer by @fizbanrapper! Now I think I'm gold.
Click to expand...
Click to collapse
Glad it helped! Ting runs on GSM now too, if you're interested. I got an AT&T M8 running on T-Mobile's network, but still with Ting and same pricing. APN's rarely seem to matter on GSM Ting.
I ran this for a couple days and only issues I had was that poweramp and mx player kept freezing up and fc'ing It's very fast and smooth otherwise and had no issues with data or reboots.
Sent from my EVO using XDA Free mobile app
So I guess that I wrongly assumed that CM was already rolling out 12.1 nightlies for the Jewel. But I checked their Jewel downloads page, and it still says "12", not "12.1". So is that a typo, and CM is still using 12.1, or are they not doing nightly 12.1 builds? If people want this ROM updated, I could try my hand at it.
EDIT - I'm trying my hand at it. Squashing through build errors now.
ocarinaz64 said:
So I guess that I wrongly assumed that CM was already rolling out 12.1 nightlies for the Jewel. But I checked their Jewel downloads page, and it still says "12", not "12.1". So is that a typo, and CM is still using 12.1, or are they not doing nightly 12.1 builds? If people want this ROM updated, I could try my hand at it.
EDIT - I'm trying my hand at it. Squashing through build errors now.
Click to expand...
Click to collapse
So sorry guys. I just assumed cm would have picked up nightly builds a few weeks ago.
Ocarinaz has been doing a hell of a job picking up the slack for the roms I used to build.
Any interest in becoming an official maintainer for SOKP jewel?
fizbanrapper said:
So sorry guys. I just assumed cm would have picked up nightly builds a few weeks ago.
Ocarinaz has been doing a hell of a job picking up the slack for the roms I used to build.
Any interest in becoming an official maintainer for SOKP jewel?
Click to expand...
Click to collapse
No worries. If you don't have the time, and if you aren't even using the device, it's nothing to be bashful about leaving behind.
What all would be entailed in an "official maintainer"? I'm willing to keep building it, it's easy enough. And I can keep up my XDA thread. But if I have to register in a million places, I might just rather stick to my unofficial builds and call it quits.
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
I did get a CM12.1 build off though. It wasn't that hard. Enjoy!
CM-12.1-Jewel-Files
FYI - I have been using this since last night. I noticed a couple of FCs when it came to putting my gadgets where I wanted them to be the first time, but after that I haven't had problems. It seems to be a good build overall.
I just rebuilt CM 12.1 from scratch. It built start to finish without even one error. It means that if you like CM, you should update to the newest one. But it also means that I would wager a fair bet that CM might start nightlies for Jewel soon.
I've managed to stay happy on the official 12 builds so far. Down side is I'm pretty established on it. So I have that nag in the back of my mind to try dirty flashing to 12.1 against my better judgement. Lol
I don't know if I should keep making new posts for every new build, but *bump*, I got one off again. And while I don't recommend dirty flashing over 12.0, I would say it's worth a go.
Oh yeah, purely for science. And after making a good backup
Related
I'm new to rooting and running custom roms. Has anyone tried any of the latest version of CyanogenMod 10 for the evo lte. Is it stable is it fully functioning. Sorry for the noobness but we all start somewhere. Thanks
I have been running it all day, I don't know the differences from the previous nightlies, probably the same tiny bugs. I haven't played around with it too much.
I have always been curious as to what the differences are between the MANY JB ROMS we have here. They all have the same problems...
I've been using codefire cm10 JB ROM now for around 3 weeks it seems to me that everything is working fine so far. you should try it out I haven't had any problems yet... I'm going to stick with it
Sent from my EVO using xda app-developers app
Jrobb2007 said:
I'm new to rooting and running custom roms. Has anyone tried any of the latest version of CyanogenMod 10 for the evo lte. Is it stable is it fully functioning. Sorry for the noobness but we all start somewhere. Thanks
Click to expand...
Click to collapse
Ive been using the CMX CM10 JELLYBEAN ROM as my daily driver for the last six weeks and it is great. Personally i think the bugs are totally minor. Nothing you cant deal with really. I liked the CodefireX tweaks. I just update the Rom using the GooManager and for some reason they changed it from NIGHTLY to EXPERIMENTAL for whatever reason. Also noticed the CMX tweak are gone from the update? dont know why. Anyone here know? otherwise the ROM is really fast and stable enough.
Am I alone here? It looks great and is speedy as hell. But after I leave the house and I'm not on wifi any longer all the problems start popping up. Terrible signal (even confirmed using OpenSignal), only hold 3G half the time and NEVER get a 4G connection in the places I always get one on a ICS ROM. Also, camera is worthless. And MMS doesn't work almost always.
I really appreciate all the work everyone puts into it. I couldn't do any of the stuff these people are doing. I've tried CM10 and ParanoidAndroid and I can't wait until they hit a stable/primetime state. Just not there yet.
But if it's just me please somebody chime in! I have done PRL and profile updates on stock ROM before flashing so I don't believe it's that. Stock ROM and Mean ROM both give me great signal/data and 4G.
right now I'm on codefire jb release date 26 plus I flashed the duocoreAOSPmod my phone is fast, and also I used the 3g uncap codefire tweak. I'm not having any 3g speed problems.
the reason why I'm still on #26 is because when I flashed the 04 nightly the WiFi will not work it just says error. So hopefully they fix that then I will update. If not I really would hate to discard codefire cause I like it a lot.
Sent from my EVO using xda app-developers app
Hi I'm relatively new on the forums. I purchased a 64GB One from AT&T a week ago. Last night I was able to root it and flash CM 10.1 without any issues. This is the second phone I've rooted but the first one I've flashed a custom rom. I flashed the newest 5/29 nightly build of CM 10.1 and at first glance I noticed no major issues because I had wifi on the phone the entire time so I could download large apps and files quickly.
But this morning I turned off wifi and realized I'm not connecting to my local data network on AT&T LTE.
When my wifi is on, both wifi and mobile data icons are blue, indicating data connection.
But when wifi is off, I'm not connecting to data networks at all (and the cellular status bar icon is gray, indicating no data connection), even with mobile data turned ON in the settings menu.
In my settings Wireless & networks>Mobile networks> Data Enable is checked
Preferred network mode> LTE/GSM/WCDMA is selected.
Has anyone experienced this problem and found a solution? Appreciate the help. Thanks.
Check the apn?
Sent from my HTC One using xda premium
spitfire2425 said:
Check the apn?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Bingo, thank you, that worked.
APN was set default to a defunct att network (wap.cingular). I changed it to ATT LTE (pta) and mobile data is working again.
I never even knew what APN was.
Don't forget the thanks button.
Sent from my HTC One using xda premium
OP. It's because you flashed the old unified m7 build and not the m7att build which is also more up to date. 5/29 is the last unified build. Cm announced AT&T users should use the AT&T builds now due to the APN and probably will be more reasons in the future.
Sent from my HTC One using Tapatalk 2
tiny4579 said:
OP. It's because you flashed the old unified m7 build and not the m7att build which is also more up to date. 5/29 is the last unified build. Cm announced AT&T users should use the AT&T builds now due to the APN and probably will be more reasons in the future.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Is it stable enough for day to day use?
Aren't you using cm 10.1 already? The AT&T build branched from the m7 build.
Edit: quoted myself. Meant to quote previous post.
Edit: nevermind I was thinking of op. It's not ready for me yet due to issues with bt music and bt calls.
Sent from my HTC One using Tapatalk 2
tiny4579 said:
Aren't you using cm 10.1 already? The AT&T build branched from the m7 build.
Edit: quoted myself. Meant to quote previous post.
Edit: nevermind I was thinking of op. It's not ready for me yet due to issues with bt music and bt calls.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
We're those questions for me? I am using CM 10.1, and yes I'm having issues with BT music and phone which is my only real issue with the build right now. Also I find the camera performance not as good with panoramas
Would the AT&T build improve on these BT issues?
kayone73 said:
We're those questions for me? I am using CM 10.1, and yes I'm having issues with BT music and phone which is my only real issue with the build right now. Also I find the camera performance not as good with panoramas
Would the AT&T build improve on these BT issues?
Click to expand...
Click to collapse
The questions were directed at you initially but I saw later someone else commented. I was asking if you were on the regular M7 build as it split after 5/29 and ATT build would have corrected the APN issue which isn't an issue if you select the right one.
The AT&T build may help. The last build I was on before I went back to sense for now was the 6/6 build. It had BT music issues and phone was not usable over BT then. I didn't see any fixes since then but performance may be a bit better now. They're almost identical to what you're running which is the UL build. I'd recommend keeping an eye on both the ATT HTC One and International HTC One threads. The international one is the one in HTC One Original development started by codeworkx.
tiny4579 said:
The questions were directed at you initially but I saw later someone else commented. I was asking if you were on the regular M7 build as it split after 5/29 and ATT build would have corrected the APN issue which isn't an issue if you select the right one.
The AT&T build may help. The last build I was on before I went back to sense for now was the 6/6 build. It had BT music issues and phone was not usable over BT then. I didn't see any fixes since then but performance may be a bit better now. They're almost identical to what you're running which is the UL build. I'd recommend keeping an eye on both the ATT HTC One and International HTC One threads. The international one is the one in HTC One Original development started by codeworkx.
Click to expand...
Click to collapse
Yeah I flashed the regular M7 build which ended nightlies on 5/29. It's not encouraging news that your 6/6 build still has BT issues. I really don't want to go back to sense. I have the 64GB model and like the space. I understand that the google experience version HTC One will only have 32GB on board.
So I just reflashed the latest m7att build that was available and sadly BT still doesn't work.
It seems to run a bit smoother than the last build but I noticed they took away the invisible middle capacitive button just above the HTC logo and instead incorporated menu soft buttons into most of the apps, but not all of them so a few I could not figure out how to access the settings menus which was irritating.
If BT streaming would just work, this setup would be perfect for me.
Good news, i reattempted BT pairing with my car (2013 Hyundai) and it was successful, both for calls and music streaming.
I noticed only a couple minor bugs:
When I dial numbers remotely from my car touch screen, there is a bit of delayed response.
Phone won't respond when I tap the 'hang up' button on my car touch screen at the end of the call. It's always worked with previous phones.
So I think im good with this official build for a while.
Sent from my Nexus 7 using Tapatalk 2
Here is a message from Bajee Baskararasa the creator of Rootbox ROM on Google+:
"Bajee Baskararasa - 23 minutes ago
Hey guys I know I've gone missing from G+ and XDA but I've been extremely busy with work these past few days. Unfortunately I won't be able to invest any time for RootBox for at least a week or two. I planned to get 4.3 builds rolling by this week or so but my situation clearly didn't allow that to happen. I'll try my best to set aside time for RootBox but since I got this new job it'll take some time to adjust myself and get a proper schedule. Another factor that will eventually impact my time is University starting in about 3 weeks.*So enjoy stable V4.2 build for now (which I'm running as well) or you can *always try out other roms who released Android 4.3, until then enjoy the summer and the good weather! (wherever you are)
Post this message in your device's thread. Thanks +Myles Nystrom*in advance since you will eventually post this message in almost all the threads "
I think this says it all....enjoy the summer and enjoy V4.2
Except data don't work for our phone
Edit: unless you know something I don't.
Sent from my SCH-I545 using Tapatalk 4 Beta
jova33 said:
Except data don't work for our phone
Edit: unless you know something I don't.
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
On the 4.2 build, I could intermittently get the data to work by messing with settings in the network settings. I just turned LTE off/on a few times, then turned data off/on a few times, and also would cycle airplane mode. After doing these things randomly, I eventually got data to turn on, but it doesn't stick. If you turn data off or reboot, it back to not functioning and I have to try getting it to work again. It's very strange.
JamesPumaEnjoi, do you maintain this device at all? if not, do you know who to direct this problem to? The data worked fine on the 7/3 nightly, but hasn't worked correctly since that. I've seen a few posts on G+ Rootbox community about it, but they get very few responses.
I wish I knew a dev that could have a looksee at it. Bajee is maintaining this for like 20 devices, with a few maintainers for their specific device. I mean, I emailed Bajee directly about it lol, but it probably landed in his "waa waa waa! This is broke!" mailbox.
Sent from my SCH-I545 using Tapatalk 4 Beta
Yeah, I'm not sure why no one has fixed it yet. It would be one thing if the problem was trivial, but data is a pretty important thing on a smartphone. I'm pretty sure it's one of the only roms that has this problem. It also happens to be the only rom I want on my phone! Lol! I've even gone as far as making a build box and attempting builds myself, but still haven't had luck getting things to work.
Someone else I asked to look at it said it must be the drivers. It's stuff pulled from three different ROMs that do work on our device. I might start building and putting stuff together like Frankenstein
Sent from my SCH-I545 using Tapatalk 4 Beta
yeah, I just don't know enough at this point to pinpoint the cause of the problem. I wish I knew more.
He's just been super busy lately 4.3 will be out soon enough
Well something was up with data on the Rootbox builds fir 4.2.2. Was he aware of it?
Sent from my SCH-I545 using Tapatalk 4
JamesPumaEnjoi said:
He's just been super busy lately 4.3 will be out soon enough
Click to expand...
Click to collapse
Well, only 1 official rootbox build for verizon in the last month and a half (including 2 "stable" builds) has had working data. I don't know how it can be considered stable with data problems, but maybe that's just me. I'm not knocking Bajee or anything, since he has a lot on his plate... it's just a little frustrating is all since that's the only issue I've seen on the builds and it hasn't been addressed.
If any there's any dev that has any ideas on how to get data working properly, I know there's a few of us who would greatly appreciate it. I've searched all over for details on how to fix no data, but had no luck in finding a solution (tried porting the rom, swapping lib files from working roms, building my own build)... I've also got a logcat of the data not working, then turning on for about 3-4 secs and turning back off, if there's someone knows how to interpret them.
Something to do with the RIL?
Sent from my SCH-I545 using Tapatalk 4
I tried looking into any RIL files from the 7/3 (working) and 7/7 (next nightly stopped working) releases to see if that might be it, but I don't know enough to determine if it was a problem. I also checked the changelogs between those releases on rootbox(dot)basketbuild(dot)com to see if there were any specific changes that might have affected the verizon s4. There were 2 commits that I'm not exactly sure how they affected things:
7/4: "jf: revert ril changes"
7/6: "jf: bring back samsung ril. problems with slow data on certain modem"
I'm definitely an amateur when it comes to dev stuff though, so I would need someone else to explain if these might have been what broke data again. Either way, I'm slowly learning more about building, github, and such.
Attached is a picture of what the BSOD looks like. Also attached is a last_kmsg that caught "a" crash. The last_kmsg for this crash appears to not have any info for the crash.
Has anyone found a fix for this?
Alias8818 said:
Attached is a picture of what the BSOD looks like. Also attached is a last_kmsg that caught "a" crash. The last_kmsg for this crash appears to not have any info for the crash.
Has anyone found a fix for this?
Click to expand...
Click to collapse
I'm pretty sure anyone who can help is going to ask about your ROM and any other setup details you think are relevant.
Sent from my LGLS990 using XDA Free mobile app
MikeDroid said:
I'm pretty sure anyone who can help is going to ask about your ROM and any other setup details you think are relevant.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
This has happened on 3 different ROMs. CM12, Blisspop, and Illusion. This has happened on the stock kernel and RIN Kernel 1.65.
Kernel crash, thats what that is it usally happens when the is a kernel based error I recommed staying away from any 4.4.4 roms for now I have had the same problem with thoughs for now the only rom that I don't get that on is this one from clark44:http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197 I recommed you find a rom you like and that works and DO NOT modify/change the kernel. This could also be of you over clocked way to high. So each just reboot and find a rom that dosen't do this and just stick with it without changing kernels.
I believe I will revert back to a Kitkat ROM, sadly, until it's figured out. I haven't played with any kernel settings or OC'd.
Blue Screen
Sadly, I have also been getting these demigod modem crashes with pretty much any 4.44 rom - carbon, liquidsmooth, vanir, my own cm11 build, etc.
Seems to happen every couple days at least - which I can't have with needing alarms, missed calls, etc.
It's a shame as these roms run really well, much better than stock. For the moment I am running barrin rom (stock based) and have no issues - I haven't had any issues with any stock based rom.
Hopefully some of the devs can at least let us know what they are experiencing, and what this means.
mo1991 said:
Sadly, I have also been getting these demigod modem crashes with pretty much any 4.44 rom - carbon, liquidsmooth, vanir, my own cm11 build, etc.
Seems to happen every couple days at least - which I can't have with needing alarms, missed calls, etc.
It's a shame as these roms run really well, much better than stock. For the moment I am running barrin rom (stock based) and have no issues - I haven't had any issues with any stock based rom.
Hopefully some of the devs can at least let us know what they are experiencing, and what this means.
Click to expand...
Click to collapse
Have not experienced this at all but looked at the kmsg in the first post and it indeed seems like a kernel crash based around the soc. It's a modem crash but these phones have different system on chips, not all ls990s are created equal. The same stuff happened with rin when I first built it, green watchdog kernel crash for roughly 3-5% of users. The voltage spectrum was widened to include these other socs and voila, no more green screen for anyone.
I can't promise a fix, I'm overloaded currently - but if I find anything to help you guys, I won't keep it a secret.
News on BSOD
No News here regarding this huh? Too bad as there are a lot of good roms out there and none of them working without BSOD on what appears to be "only some" of the LS990's - sadly mine is one of those.
If any of the Dev's that are more knowledgeable then me want me to do any testing or try to pull some of the files from my phone let me know. Stock based roms work fine. CM11 and AOSP based roms all get the blue screen modem crash - SOC.
mo1991 said:
No News here regarding this huh? Too bad as there are a lot of good roms out there and none of them working without BSOD on what appears to be "only some" of the LS990's - sadly mine is one of those.
If any of the Dev's that are more knowledgeable then me want me to do any testing or try to pull some of the files from my phone let me know. Stock based roms work fine. CM11 and AOSP based roms all get the blue screen modem crash - SOC.
Click to expand...
Click to collapse
I have a T-Mobile sim with an at&t device d850 and I only get the blue screen when using LTE. If I turn off LTE then no problems. Hbu
Sent from my LG-D850 using XDA Free mobile app
Test
4NDROID4LIFE said:
I have a T-Mobile sim with an at&t device d850 and I only get the blue screen when using LTE. If I turn off LTE then no problems. Hbu
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the info. I will give this a test one of these days and see if turning off LTE makes a difference. I don't think I could deal with that as a long term solution as I need fast mobile data, but it would be good to know that the issue is caused by LTE to narrow down potential fixes for the devs.
Fix
Anyone know if the new version of modem helps things?
Or any other fix?
cm12 crash
Just for information, I have also received this modem crash blue screen on the latest cm12 build from 3/1.
Hopefully we will have some idea why this is happening before too long. If anyone has any ideas please let me know. Happy to test.
IMPORTANT INFO:
-You must be on the VRUAMDK bootloader or you aren't going to be able to use this ROM. I'm sorry =(
(run this in a terminal to find out: getprop ro.bootloader )
-We have de-unified the Galaxy S4 line. This is for the Verizon variant (SCH-I545) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=jfltevzw&type=nightly
We have de-unified the Galaxy S4 line. Too many issues with having them all in one and a maintainer's nightmare. Look for jfltevzw builds now as opposed to the jflte builds you previously used.
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S4 (jfltevzw), ROM for the Verizon Samsung Galaxy S 4
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: VRUAMDK bootloader
Version Information
Status: Nightly
Created 2015-04-20
Last Updated 2015-04-19
I guess I'll post first.
Up and running on 4/20 (flashed a few hours ago). So far I have noticed:
As soon as you open the stock messaging app a notification appears saying a message could not be sent. Choosing "Discard" from the menu of the unsent message does not discard it.
The compass is not working properly. Orientation is slow to respond and is off by 180 degrees. This only happens when stationary. When viewing the sensors using Advanced Sensor Tester the magnetic sensor is showing some changes, the gyroscope sensor shows very little changes, and the orientation sensor shows one line out of three showing very little change. Don't know if it means anything.
Not sure if I am using the correct term here, but, Adaptive brightness does not seem to be responding well and overall the lower brightness setting of the display seem to be too dark. In an outdoor environment any brightness setting below 50% is pretty much unusable and the brightness when in direct light doesn't increase enough. (May not have described that correctly).
BT seems good with a Jabra earpiece. I have yet to test it with something like music play over Ford's Sync and vehicle BT.
Not sure if it is an Android 5.1 issue or not but I have had to reinstall several third party apps since going to CM12.1. Opening them results in a force close. If I navigate to the APK using root explorer, selecting it, and choosing install (to reinstall it) the app works correctly afterwards.
So far everything else seems to be working.
Logcat attached:
https://www.dropbox.com/s/khdo1uicmj8l7j8/Log_2015-04-20_14-07-16.txt?dl=0
ran the 4/18 and 4/19 build. BT works, connects but won't stream anything. First my "Music" app was force closing every time it tried to play, it kept trying so it was a loop of force closes from it. I disabled the Music app, i then started getting bluetooth share has forced closed errors.
im flashing the 4/20 build but won't be able to test bluetooth playback to my car until tomorrow.
i also have the damn #in my status bar all day long. can't get rid of it, have no idea what its doing up there. even stays through reboots.
Ok, I have come across another issue. I disconnected my Jabra BT earpiece earlier. Now it will not reconnect. BT has turned off and will not turn back on. Cycling airplane mode does not help.
Logcat:
https://www.dropbox.com/s/h86esc88wmth8pd/Log_2015-04-20_17-55-16.txt?dl=0
---------- Post added at 09:01 PM ---------- Previous post was at 08:57 PM ----------
Ok, a reboot seems to have straightened BT out for now. It is on and I can connect my earpiece.
BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message
Sent from my SCH-I545 using Tapatalk
gmp029 said:
BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
get the same error. welcome to the club, looks like more bluetooth issues.
dansan382 said:
get the same error. welcome to the club, looks like more bluetooth issues.
Click to expand...
Click to collapse
I actually expected it, happens after every version change.
FernBch said:
I actually expected it, happens after every version change.
Click to expand...
Click to collapse
yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.
I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol. i signed up for a motorola credit account, waiting for the account number to come in the mail and then ordering my 64GB nexus 6. my nano sim card came yesterday which I know verizon will give me a hard time activating. I also have a sim card cutter, some cases and a screen protector coming tomorrow so either way this is happening.
dansan382 said:
yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.
I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol
Click to expand...
Click to collapse
I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.
So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me
vanberge said:
I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.
So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me
Click to expand...
Click to collapse
good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol
dansan382 said:
good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol
Click to expand...
Click to collapse
MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.
FernBch said:
MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.
Click to expand...
Click to collapse
Yea I followed your APN edits awhile back, still was hit or miss. the MMS would eventually come in but wasn't 100%. great roms though, i'm really liking lollipop
I started a bounty for the compass - http://forum.xda-developers.com/galaxy-s4-verizon/general/bounty-make-compass-cm-12-1-t3088991
Hello,
Thanks for you working on this ROM. My issue is I can't install it.
So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.
I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.
Thanks in advance.
Otakulad said:
Hello,
Thanks for you working on this ROM. My issue is I can't install it.
So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.
I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.
Thanks in advance.
Click to expand...
Click to collapse
You may have to go back to stock first (either by nandroid restore or via Odin).
FernBch said:
You may have to go back to stock first (either by nandroid restore or via Odin).
Click to expand...
Click to collapse
Thanks. I was thinking about that but since they are only nightlies and not everything is working, I'll wait.
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
dansan382 said:
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
Click to expand...
Click to collapse
another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.
dansan382 said:
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
Click to expand...
Click to collapse
Well, you'll be missed here but you gotta do what you gotta do......
I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]
Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.
phonedawg said:
another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.
Click to expand...
Click to collapse
FernBch said:
Well, you'll be missed here but you gotta do what you gotta do......
I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]
Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.
Click to expand...
Click to collapse
well its time to move on, i really love the GS4 even more than my galaxy nexus but its been 2 years. I had this GS4 since launch date, actually had it 3 days early. she served me well and i honestly could have gone a little longer with it but I got tired of dealing with flashing stock roms on my phone just for certain key things not to work right. Got tired of having to explain to people when something didn't work it was because of custom software. Plus looking at my GS4 it just feels small now. Honestly would have preferred a 5.5inch phone but I dont see this thing being a problem once i get use to it. I'll probably keep the GS4 around as a mess around device so I'll probably still flash some roms with it. Don't think there is much of a demand in the resale space for a 2 year old phone like this. I've learned my lesson though, and I should have learned it from having a galaxy nexus but from now on out I'll only be using nexus devices.
I debated switching to T-Mobile and honestly I'm still very interested in doing so. Like others, coverage is a big concern and even though here in Southern PA (right outside of Philly) I get great T-Mobile coverage, I'm still worried about the one time to go somewhere that has 0 coverage. I drive back and forth to Long Island, NY where I'm originally from every few weeks and T-Mobile coverage is outstanding that entire trip so that would be nice. If I was still on the island I would switch in a heartbeat. Being in PA now, 75% of this state is a blackhole for T-Mobile coverage which very much worries me, even though I never really go that far. Maybe by the end of the year I might make the switch but for now I'm sticking with big red, unfortunately.