Related
I've used a few Jelly Bean ROMs since switching to Straight Talk last night on my unlocked Note. Everything works fine on Straight Talk except GPS. Just can't seem to get a signal no matter what I do.
Are there any non-stock ROM's (preferably JB) that GPS works 100%?
Thanks!
I have tried almost all the roms...And use gps daily...The worst I seen is its lock time connecting...but it eventually works..also a gps fix I seen somewhere.Plus a Gps app that helps fix connection gime to satellites
But the best fix is to change out you cong files to a better region...
And you can also save google maps for OFFLINE so you can use it????
Just save the files..and open it up when needed!
CM10 nightlies lock on pretty quickly and repeatedly. May want to give them a try.
https://play.google.com/store/apps/...tatus2&feature=nav_result#?t=W251bGwsMSwyLDNd
The above app has a feature that will reset the aGPS data and download new data as well. Works extremely well when traveling overseas or in a new area.
Trying CM10 now (latest build)...gotta get this GPS working...other than this the Note and Straight Talk has been awesome!
Padawan v3 soon to be v4
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I have no problems with GPS, been using Dagr8's ROMs for a while, King Kang, currently using the AOKP JB B5.
I found this for saving offline maps..hope this helps: http://forum.xda-developers.com/showthread.php?t=1412755
Well I installed Cryagen Nightly CM10 (version released today) and still no GPS...tried King Kang and AOKP with the same results...even been outside fir a while with still nothing.
Download the app for the play store in my first post. It will give you an option to download a-GPS data. Once the note has that lock on is about 5 seconds.
Tried this and still doesn't work. I'll be calling Straight Talk tomorrow if no one has any more suggestions!
Thanks!
AndroidVageta said:
Tried this and still doesn't work. I'll be calling Straight Talk tomorrow if no one has any more suggestions!
Thanks!
Click to expand...
Click to collapse
why not connect to wifi so its faster at home or what not..Then just save the maps for offline use? ..for now anyways till you find a more stable connection..least it will help if you need to get somewhere..the maps you can save are huge...
I am on straight talk as well for about two weeks. I needed navigation and realized i couldn't get it to work. I have tried a few different thing as well. No dice. I would be interested in how your conversation goes with ST. Please give a update.
Sent from my SAMSUNG-SGH-I717 using xda premium
TO Kinz1980:
Have you actually tried to go out and about with the GPS or are you just sitting inside trying to get it to work? Also, have you tried different ROM's and what not? Read below to see my (possible) fix and current experiences.
Well, while on the phone with Straight Talk to see what the issue COULD be I was standing outside with them on the phone and all of a sudden my GPS started working. Maybe I wasn't thorough enough in my own testing (actually walked out to the street today...previously I was just on my porch)?
I tested it a few times with closing the app, restarting it...locks on to my position damn quick and is very accurate...to a degree (see below). Also my phone died this morning so maybe the battery hitting 0 then recharging or something did it, I don't know for sure.
All I know is that its working (using CM10 nightly build) with Google Navigator for the most part. I will use it later today IRL when I've got to go to a friends house then update once I know its actually WORKING turn-by-turn.
I know when I was outside today it was a tad slow in updating my position (walked about 100ft up the street a few times and it was very slow to notice the change in location/direction or didn't change at all on some occasions) and a couple times the GPS signal would drop for a few seconds, etc. So like I said, I'm going to do more thorough testing here in a bit and update with my final results.
All I do know is that it is at least WORKING...may not be super good at this point, but I am getting a lock. Its a start!
I was driving when it was not working. When i am at home it uses wifi. i am using the blackstar Rom right now. I like cm roms but i like yo use the s-pen. I guess i could flash a different Rom and see if this makes a difference. I don't use gps on a daily basis but when i use it i need it to work. I will be watching this thread closely.
Sent from my SAMSUNG-SGH-I717 using xda premium
GPS works fine on BLACKSTAR.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Well after leaving my house GPS has ceased to function. Really starting to make me wonder what the actual issue here is. I'm guessing ROMs? Will just have to try a stock ROM later tonight. Weird how it works fine for some and not for others...like, what's the missing link here?
bigfau said:
GPS works fine on BLACKSTAR.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Hey big is there a setting or something i don't know about? I love your Rom. But this gps is killing me. I am at a lose of what to do.
Sent from my SAMSUNG-SGH-I717 using xda premium
I was having the same issue, and slowly realized that the jb gapps was the issue for me. If I used the July gapps for JB it would get a signal and work, but if I used an updated version of gapps, it would not work. Might try installing the July JB gapps and see what happens. It only took me four days to finally figure out what was wrong, becuase it was working before the update to a newer gapps.
This is after 20 min moving around inside and outside.
Sent from my SAMSUNG-SGH-I717 using xda premium
Just about right said:
I was having the same issue, and slowly realized that the jb gapps was the issue for me. If I used the July gapps for JB it would get a signal and work, but if I used an updated version of gapps, it would not work. Might try installing the July JB gapps and see what happens. It only took me four days to finally figure out what was wrong, becuase it was working before the update to a newer gapps.
Click to expand...
Click to collapse
So do you just have to NOT update them gapps then? I understand what you are saying...but Google Maps isn't even part of the gapps package. So what is updating in the gapps that breaks functionality?
I love the CM 10.1 build of 4.2.2. It is my dream phone right now. The problem is that no WIFI tethering works on it as of yet. If anyone has anything working I'd love to be proven wrong. This is a show-stopper for me. I can't use bluetooth because my laptop doesn't have bluetooth.
I tried every tethering app out there. Barnacle was the best in that it reported the errors it was seeing instead of just refusing to work.
Anyway, I am thinking of working around the problem by keeping a ROM stored as a TWRP backup that I can restore when I need tethering. I don't need tethering on a moment's notice.
I would like the tethering ROM as slim as possible. I haven't tried any yet. Would a restore be any faster with a slim ROM?
Can someone suggest what ROM I should use that has a small footprint and can restore quickly? I'm thinking that I won't have any apps and no account logged in. If I'm tethering I will be using the other device for email etc. And I'm sure the phone will work no matter what I'm running.
Can anyone suggest a better workaround than this?
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
crutzulee said:
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
Click to expand...
Click to collapse
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
mchahn said:
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
Click to expand...
Click to collapse
Sounds like a bad download...Did you download straight to your phone? While I've never had this issue, I have heard that some prefer to download to their computers and transfer the zip to their phones..
You might be right. I did download it to my PC and copy over the zip. However, I had trouble copying and I had to copy a second time. So, I'll try again.
I did a fresh download, copied, wiped, flashed, and it didn't work. Apparently bam won't run on my phone.
...and your using the latest version of twrp?
Yes. I checked. I might be doing something wrong but I doubt it. I'm guessing there is a bug somewhere that rarely shows up. Until the source code is available these custom roms are somewhat a shot in the dark.
I'm just going to go back to my ICS backup when i need tethering. I guess I started this thread with the hope that someone would have a workaround. I really like 4.2.2 and I've decided to live with this. Maybe it will be fixed soon?
Thanks for your help.
The only tethering app that seems to work is "Open Garden." It's in the Play Store but you'll have to side-load it if on AT&T.
Sent from my SAMSUNG-SGH-I717 using xda premium
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
How do you keep AT&T from seeing that you're tethering?
knoshann said:
How do you keep AT&T from seeing that you're tethering?
Click to expand...
Click to collapse
I don't know who you are replying to, but I tethered all the time with ATT when using ICS. I didn't know they were trying to block it.
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
knoshann said:
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
Click to expand...
Click to collapse
I know that Verizon has folded tethering into the normal data plans. They make it sound like a benefit but they're raising the overall price so they are really forcing you to buy tethering. I thought ATT and the others were going the same way.
I assume they realized they couldn't enforce it any other way.
mchahn said:
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
Click to expand...
Click to collapse
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
chp said:
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I've been to their home page a million times because everyone said you could get the apk there. I was going crazy because all I ever saw was a big orange button to download a version for windows. I had just now typed a reply to you that said you were crazy and then it hit me. You meant to go there on the phone! I'd only been there from my laptop.
Thanks, I'll give it a try now.
-- later --
As I feared, open garden is bluetooth only.
I was researching the hotspot issue that only a few users have been having and found that it is inherent to android 4.1.2 and newer. What I found out:
"Throughout the previous iterations of Android (<4.1.2), Android has not identified for the carriers which data is for tethering, and which is not.
Android 4.1.2 introduced that ability (and requirement) for Android devices to properly flag when data is for tethering purposes. This is the first time this has been used in a vanilla release of Android...
For everyone frustrated by this update to Android: Android respecting a carrier's request to know if data is for a tethered device IS NOT A BUG. IT IS A FEATURE. It's not a feature for users like you and me, it's a feature for manufacturers like Samsung and HTC, so they can in turn build devices that carriers can have more control over.
So, to be clear, THIS IS NOT A BUG. Google INTENDED to respect carrier tethering rules. The only way to circumvent this is to either get a plan from your carrier that allows tethering, revert to a build of Android of 4.1.1 or earlier (I used wugfresh NRT tools, google it, they're amazing and simple: FOR NEXUS DEVICES ONLY, SORRY), or for a developer to find and KILL THE ****ING ABILITY FOR ANDROID TO TAG DATA AS TETHERING DATA and release that to the public; either by providing an modded Android image, or as an app (much less likely to work unless you're rooted)."
Copied from a past on another forum, and apparently I can't post a link to it.
Even though I clicked on Thanks, I'd like to thank you again for that clear explanation. I'm sure it won't take long for that to be hacked.
i think the next nightly may fix it
Next to fix on next Nightly
msm8660: Add Wi-Fi AP module args (i wonder if this is it?)
rkpsym ftewed
I sent JamieD a message about it a few days ago. I'm not sure if all developers were aware with source of the problem. Its especially hard when only some users report having an issue. Hopefully they get it working soon.
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.
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
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.