[ROM][CM13][Marshmallow][Android 6.0.1] JBL Nightly Builds - Verizon Samsung Galaxy S 4

Since Euroskank has discontinued his nightly CM12.1 builds for the Verizon S4, I've decided to pick up where he left off. These nightly builds will be very similar to what you'd seen from him, as they're essentially CM12.1 nightlies with some interesting cherry picks along the way.
Edit 1/8/16: I am no longer building CM12.1 for jfltevzw. I am now building CM13 instead. I no longer have an S4, however, so I can't even say if the builds are functioning properly. If you'd like to try them and let me know, that would be great. I know I stopped building for a while in late November and December. If you're a user of these builds, I apologize for that, but my work and personal life stopped me from paying attention to building CM.
Download Link: http://cm.justbloodlust.com/?type=cm130&device=jfltevzw
Latest CM13 Changes Merged: http://review.cyanogenmod.org/#/q/status:merged+branch:cm-13.0
Note that the cherry picks included in my builds are listed on the right-hand side of the page.
In addition to cherry picks from CM's gerrit, I have also included two custom changes:
Hosts file based ad blocking, compiled from several reputable sources online
Specifically: adaway.org, hosts-file.net, and pgl.yoyo.org
The boot animation from the Euroskank builds
Disclaimers:
First and foremost, I am not responsible if any of these nightlies breaks your phone. They are up-to-the-minute (as of compile time) builds with some cherry picks that haven't been completely tested. Things can and will go wrong. You've been warned. Make a backup and know how to recover your phone from situations like boot loops before trying to flash this ROM.
These builds are for the Verizon Galaxy S4 variant (jfltevzw) ONLY. If you flash this build on any other device, it is not guaranteed to work and likely to cause you to have a bad day.
This ROM is CyanogenMod based. It WILL NOT operate on a phone with a bootloader version after MDK. It WILL NOT work with SafeStrap. Do not try.
These builds do not include gapps. CyanogenMod is designed to work independent of the Google applications. If you'd like them, please feel free to download a package from another source.
Please let me know if you have any problems with the website operation or bandwidth (slow downloads, timeouts, etc). My server should be adequate, but I'm unsure how many people may try to download.
While these builds are nightlies, they are not guaranteed to be built on a nightly basis. I am building them manually, so if I am too busy, then a day or two might be missed here or there. I will typically leave the most current build and one or two previous builds on the server. I won't be keeping a long-term history of builds.
I may discontinue these builds at any time. I have upgraded to a Nexus 6 (shamu) and am continuing to build for the S4 at user request. NOTE that I do not have the device any longer, and as such am unable to test any of the builds that I am producing. I produce nearly identical builds for shamu, but different hardware/firmware handles changes differently. I do pay attention to the thread, however, so if cherry picks are made that negatively impact the build, please let me know so I can remove them.
Suggestions and bug reports are welcome. If there are bug reports, I ask that you include as much information as possible and a logcat when able. I reserve the right to ignore any suggestions or bug reports if I feel that they do not warrant attention. I cannot troubleshoot issues if you are using a kernel other than the CM default kernel included in this ROM. Please do not post bug reports if you're using a custom kernel.
Credits/Thanks:
I take no credit for the code that goes into these builds. This is a kang of CyanogenMod. All credit goes to the CyanogenMod team and the wonderful people who contribute code updates to their gerrit.
An extra thanks goes out to Euroskank. I've been using your builds for several years, dating back to my old Galaxy Nexus (toro). They've always been top quality. Thank you for building for the S4 as long as you did.

Thanks for this. I've enjoyed the cherry picks in fitsnugly's builds. I'll probably be upgrading to an S6 in a month so it looks like we're in a similar position.
The bootanimation from the fitsnugly builds is the "night" variant of the CM12 animation? I always thought CM switched back to dark because bright bootanims are horrible.

Kevin M said:
The bootanimation from the fitsnugly builds is the "night" variant of the CM12 animation? I always thought CM switched back to dark because bright bootanims are horrible.
Click to expand...
Click to collapse
I don't know. I only know it from his builds. I assumed since it wasn't branded Euroskank that it was something from the CM team.

Thanks for picking this up! Works great so far!

Senate9690 said:
Thanks for picking this up! Works great so far!
Click to expand...
Click to collapse
Glad to hear it!
Also, just dropping a note that my web server maintenance is done. So downloads should be available again (and now I can build directly on the web server!).

The build that's up today includes two cherry picks that hopefully will help with one of the annoying issues that's been going on in CM. Cherry picks 98728 and 98729 are changes to the RIL code that should (hopefully) stop the issue where your phone's LTE doesn't start on boot-up. Let me know!
Also, please let me know your experience with Bluetooth on these builds. I feel like my Bluetooth connection to my car has gotten better lately, but I'm not sure if it's from one of CM's merged changes or a placebo effect. Thanks!

Has anyone tried this yet with a smartwatch like the Moto 360 to test out the Bluetooth LE to see if it's fixed yet?
Edit: I just tried the 5/19 build and it works with my Moto360! Fantastic!
Thanks Cilraaz!
Edit2: Looks like Bluetooth still crashes, about once or twice per day.

ktraub said:
Has anyone tried this yet with a smartwatch like the Moto 360 to test out the Bluetooth LE to see if it's fixed yet?
Edit: I just tried the 5/19 build and it works with my Moto360! Fantastic!
Thanks Cilraaz!
Edit2: Looks like Bluetooth still crashes, about once or twice per day.
Click to expand...
Click to collapse
There is a new change in the gerrit today that I'm merging in. Hopefully it fixes things. It's commit 98804: Revert "bluedroid: Support dynamic A2DP stream parameters". This is reverting a change (88747) that was first merged into CM12 on Feb 17, which is (I believe) around the time when the Bluetooth issues started. I don't know if this will fix the smartwatch BLE issues, but I'm hoping it will at least fix the car audio issues that lots of us are having.
I'm in the process of building the nightly now, so it should be up in an hour or two.

5/20 build
Cilraaz said:
There is a new change in the gerrit today that I'm merging in. Hopefully it fixes things. It's commit 98804: Revert "bluedroid: Support dynamic A2DP stream parameters". This is reverting a change (88747) that was first merged into CM12 on Feb 17, which is (I believe) around the time when the Bluetooth issues started. I don't know if this will fix the smartwatch BLE issues, but I'm hoping it will at least fix the car audio issues that lots of us are having.
I'm in the process of building the nightly now, so it should be up in an hour or two.
Click to expand...
Click to collapse
D/L'd and installed 5/20 build about an hour ago. So far, so good. Reconnected to my Moto 360 without issue.

ktraub said:
D/L'd and installed 5/20 build about an hour ago. So far, so good. Reconnected to my Moto 360 without issue.
Click to expand...
Click to collapse
It seems much better for me as well. I disconnected from and reconnected to my Honda multiple times (including once accidentally deactivating Bluetooth while a song was playing). It seems to be acting as it should. Here's hoping this fix finally ends the long series of broken Bluetooth builds.

5/20 Build Bluetooth
ktraub said:
D/L'd and installed 5/20 build about an hour ago. So far, so good. Reconnected to my Moto 360 without issue.
Click to expand...
Click to collapse
Well, the 5/20 build seemed OK, but as soon as I got in my 2015 Accord, Bluetooth sharing crashed. I rebooted the phone and it reconnected fine to my Moto 360, the Accord, and an OBD II Bluetooth adapter. I guess it just didn't like the 1st request. Hasn't crashed since though. Here's hoping!

ktraub said:
Well, the 5/20 build seemed OK, but as soon as I got in my 2015 Accord, Bluetooth sharing crashed. I rebooted the phone and it reconnected fine to my Moto 360, the Accord, and an OBD II Bluetooth adapter. I guess it just didn't like the 1st request. Hasn't crashed since though. Here's hoping!
Click to expand...
Click to collapse
I had a Bluetooth Share crash this morning randomly between songs in Pandora this morning. Bluetooth is definitely more stable as of 5/20, but not 100%. I'm also having issues with my Honda not displaying the "now playing" information. However, it's getting better, so I'm happy to see the direction it's going in.

Thanks for picking this up, will continue getting this.

Sorry about the lack of builds this weekend. Between the holiday and some things that I had to get done for work, it slipped my mind a few days. I have a new compile running now. Hopefully (barring some screw up on the server), it'll be up in a few hours!

5/25 build seems much smoother than 5/26
The 5/25 build seems much smoother and faster than the 5/26 build. Any idea why?
I compared both by making a backup of 5/25 and then installing 5/26 and running it and later restoring 5/25 and running it.
5/25 seems just buttery smooth and quick. 5/26 runs fine but just does not seem as responsive.
Maybe it's me. Has anyone else noticed this?

ktraub said:
The 5/25 build seems much smoother and faster than the 5/26 build. Any idea why?
I compared both by making a backup of 5/25 and then installing 5/26 and running it and later restoring 5/25 and running it.
5/25 seems just buttery smooth and quick. 5/26 runs fine but just does not seem as responsive.
Maybe it's me. Has anyone else noticed this?
Click to expand...
Click to collapse
There we no new cherry picks in the 5/26 build. I didn't see any merges that should have effected anything like that. I'll do a clean build for today. It'll take about 5 hours to compile (unfortunately my server is a Core2Duo E8500 with 4GB RAM), but it will be fresh, clean code. Hopefully that'll help.
Edit: As a side note, the cherry picks that I'd been grabbing for improved screen brightness response and Bluetooth issues have been officially merged into the CM-12.1 branch. So those changes should now be in any and all CM 12.1 builds. As such, you'll probably want to make sure today's build (when it finishes) works in these two respects.
Edit2: It looks like I'll be changing from a Verizon S4 to a Sprint Nexus 6 on 6/6 (that's a bit ironic). Let me know if you'd like me to continue building for this phone. I'll be selling my jfltevzw, but can continue compiling builds if you guys want. Most of the picks I use are global (frameworks base or things like Bluetooth), so they'd be used for both builds. At that point, it's just a matter of checking for device-specific picks.

Yes, please keep building!
Edit2: It looks like I'll be changing from a Verizon S4 to a Sprint Nexus 6 on 6/6 (that's a bit ironic). Let me know if you'd like me to continue building for this phone. I'll be selling my jfltevzw, but can continue compiling builds if you guys want. Most of the picks I use are global (frameworks base or things like Bluetooth), so they'd be used for both builds. At that point, it's just a matter of checking for device-specific picks.[/QUOTE]
Yes, please keep building. I expect to my using my S4 for another year. Thanks in advance!
---------- Post added at 02:14 PM ---------- Previous post was at 02:11 PM ----------
Cilraaz said:
There we no new cherry picks in the 5/26 build. I didn't see any merges that should have effected anything like that. I'll do a clean build for today. It'll take about 5 hours to compile (unfortunately my server is a Core2Duo E8500 with 4GB RAM), but it will be fresh, clean code. Hopefully that'll help.
Is the cm-12.1-20150527.122759-JBL-jfltevzw.zip build the new, clean build, or will that be tomorrow?
Click to expand...
Click to collapse

ktraub said:
Is the cm-12.1-20150527.122759-JBL-jfltevzw.zip build the new, clean build, or will that be tomorrow?
Click to expand...
Click to collapse
That is the clean build.

Today's build includes another new Bluetooth cherry pick. This one fixes an issue with the Bluetooth buffer. It was previously being calculated incorrectly, resulting in a smaller buffer, which could lead to random stuttering or other problems. I haven't had a chance to load the build yet (it just finished compiling). Please post if it causes any issues and I'll remove that cherry pick.

I'm not sure if it's coincidence or not, but I had some terrible problems with Bluetooth today. I'm going to compile a new build now that has that Bluetooth commit removed.
Edit: I researched a little further. It appears this code change reverted the changes from the earlier code change that fixed the A2DP issues for us. I've commented on the change to see if that was intended or not. For the time being, I have removed the "bad" 5/28 build. A new 5/28 build is compiling now and will be up in about an hour or two.
Edit2: Note that cm-12.1-20150528.205529-JBL-jfltevzw.zip is the updated version with the offending change removed.

Related

A Message From the Creator of Rootbox (as per request)

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.

CM10.1, AOKP and Exynos4

Hi all,
I have an AT&T Galaxy SII (I777) which as everyone knows has the unsupported un-open Exynos4 chipset. I am currently on CM 9.1, which I like and is pretty stable for me.
I've been watching the nightlies in the CM10, CM10.1 and now CM10.2 threads hoping to see some sort of M or RC release. I think at some point, we were close to having an RC, but I guess the decision was changed.
As you might expect, I am looking for a daily driver build that is stable because I don't have as much time now as before to flash on a daily, weekly or even monthly basis, but I would like to get close to the cutting edge of software.
I noticed that AOKP has released jb-mr1 Milestone 1 back in April 2013 for the Samsung Galaxy S2 (i9100 INTL Exynos) (I777 ported by Task650). Then Milestone 2 in July 2013 (with I777 ports). So I am very interested in this.
My question/confusion: How is it possible that somewhat stable (i.e. milestone build) AOKP is available for i9100 when we haven't had anything but nightlies by CM. I thought AOKP is partly based on CM. Have they been able to fix certain things that the CM team couldn't? Or have they decided to have milestone builds despite some known bugs/issues? Can these AOKP builds (and their counterpart I777 ports) be considered daily drivers?
Thanks in advance!
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Butchr said:
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Click to expand...
Click to collapse
I agree. I went from task ics to sho stock jb and i can tell that is by far, imo, the most stable rom. But it is 4.1.2, now mr cook has the official att version moded and seems to be good. I've been on pac man for about 4 months now with sti kernel and it's been great. Don't update always to the latest build because nothing is broken for me. I agree with butcher, try it out and you will see.
Sent from the second to last Galaxy
PACman Rom 23.0
STI kernel 2.38
Hi guys,
Thanks a lot for the recommendations.
This past weekend I started by flashing Task650's AOKP ROM. It seemed awesome at first, but then I ran into the following annoying issues which were non-issues with my previous CM 9.1 ROM:
I am unable to turn ring or notification vibrate off even though I uncheck all the boxes I am aware of.
Battery life *feels* worse than CM 9.1. Also, I sometimes get the sudden drop in battery percentage on phone reboot, even though I re-calibrated the battery by discharging and charging it fully.
Voice dialer using Bluetooth doesn't work/ gets stuck at Start up. It also freezes with Google Search. Seems to be a known JB issue so I am very surprised. This functionality is critical as I commute 2 hours and it's safer for me to use the Voice Dialer for calls.
Audio defaults to Bluetooth when I have both my headphone jack and Bluetooth connected. I have to unplug my headphones and plug them again to get the sound re-routed to the headphones. With CM 9.1, it always defaulted to the headphones.
I think I will try PACman next because at least I see it at RC1, which gives an indication of some sort of stability. I hope the above issues are fixed.
As a last resort, I would probably go to Shostock3.
The battery going from somewhere under fifty percent down to the teens on reboot is a known issue for any jellybean rom. I found the battery on Tasks rom not so great as well. Flashing Sti kernel helped mine drastically. Never had all the Bluetooth problems everyone else complains about. I mean sometimes it was a little wonky, but a simple phone reboot always took care of any issue with my Bluetooth. Granted I only use it once a week or so with my LG headset when I mow the grass. I am waiting on Pac to release 4.3 for our phone before I flash back to Pac.
Thanks for your reply, Butchr.
A couple of nights ago was an interesting night for me. I was already on Task's AOKP and I decided to give PAC a shot. After copying the ROM's ZIP to my internal SD card and formatting system, the flash failed because it couldn't identify my phone as an I777. So I had to comment out the first lines of the updater scripts in order to bypass the check. However, I didn't have a way to push the updated ZIP file over to the internal SD card. I tried adb but it didn't work in recovery. Also, USB mounting in recovery doesn't work, at least not with Windows.
After a couple of hours, I wound up having to flash creepyncrawly's rooted 4.0.4 build using Odin. From there, I put PAC. It seemed awesome at first. Unfortunately, it had the exact same problem with Bluetooth that is affecting 4.2.2--bluetooth audio works fine, but bluetooth dialing causes the Voice Dialer or the Google Search to hang up at startup and fail initialization. It would be awesome if this is fixed in the last build, even though it seems like a Jelly Bean issue.
Immediately afterwards, I jumped on SHOstock's 4.1.2 ROM. Here are my thoughts:
- Not a big fan of touchwiz, but it's a little better than the Gingerbread days.
- I also don't like the notification panel because it's just packed with things, not leaving enough space for the actual notification. Could be a little more compact. Even after removing the brightness adjustment section. Cannot get rid of all the quick settings buttons.
- Another thing was when I downloaded Google maps, it always force-closed when attempting to start navigation. I had to uninstall it and download the APK for the latest version of Google Maps (with the interface changes). That worked fine.
- GPS locks very quickly.
- Battery life is awesome.
- No Bluetooth dialing issue. Had to use Google Search because Voice Dialer is not packaged in it.
- There is a known issue with notification sounds sometimes getting cut off. My first alarm this morning got cut off very quickly that I didn't wake up, but the first snooze alarm was fine, and that's when I woke up (10 minutes late).
I am interested in PAC if the bluetooth problem is fixed.

[ROM][5.1][JEWEL]CyanogenMod 12.1

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

[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S4 (jfltevzw)

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.

CM-12.1 dailies (nightlies) for GT-N5100 Note 8 continuing

Since the CM official "nightlies" have gone to CM-13.0, and since CM-13.0 on the GT-N5100 is presently a train wreck and totally unusable, I've decided to continue building CM-12.1 updates on my own. For the time being, until CM-13.0 becomes barely usable, I'll be posting updates every couple-few days HERE. (Broken link repaired; sorry.) Let's hope CM-13.0 for N5100 comes up to speed soon. Meanwhile, development continues on CM-12.1 and it ain't bad.
Edit 2016-07-25
The usability of CM-13.0 has improved greatly. There is still one serious flaw – that is, CM-13 consistently uses the programmed-in dummy wifi mac address (00:90:4C:C5:12:38). For some reason CM-13 on the N5100 is unable to detect the device-specific wifi mac in /efs. I have spent a couple of days sorting through undocumented, uncommented "C" kernel code trying to sort it out, but no luck. So I am continuing to build CM-12.1 versions as above until the problem gets fixed.
wseverin said:
Since the CM official "nightlies" have gone to CM-13.0, and since CM-13.0 on the GT-N5100 is presently a train wreck and totally unusable, I've decided to continue building CM-12.1 updates on my own. For the time being, until CM-13.0 becomes barely usable, I'll be posting updates every couple-few days HERE. (Broken link repaired; sorry.) Let's hope CM-13.0 for N5100 comes up to speed soon. Meanwhile, development continues on CM-12.1 and it ain't bad.
Click to expand...
Click to collapse
does it work on n5110 ? i miss the unmount external sd button and the ability to send apps to sdcard ( even if it's the instern sd card like thing
Thank you for your work.
Any improvements on voice gsm call since last 'official' cm12?
Hi, could you please provide a little more information about what is working and what are the known bugs? I would like to try this but only if there are no deal breaker bugs for me. Thanks in advance.
Sent from my GT-N5100 using Tapatalk
youtube app glitch is common on cm12.1
dose anyone not have youtube problem ?
Downloaded CM12.1 stable for my Note 8 last night. Runs Awesome!
Only issue I have is Netflix won't run. Had this problem with CM builds on many other devices.
What is the easiest fix for the Note 8?
bhalbower said:
Downloaded CM12.1 stable for my Note 8 last night. Runs Awesome!
Only issue I have is Netflix won't run. Had this problem with CM builds on many other devices.
What is the easiest fix for the Note 8?
Click to expand...
Click to collapse
2 problem:
-when the phone enter sleep,the screen will briefly rotate to landscape
-the home button wake up option got no effect, I set it to not wake up the screen when pressed, it still wake up the tab
thanks for support CM12.1 longer.
@wseverin
.. fixing ..

Categories

Resources