Related
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.
Hey all!
I have been following closesly the development of the Ubuntu Phone OS on ny Nexus 5 and I was pleasently surprised to find out that the lastest builds are pretty usable. However I have one problem, atm, which is that the GPS never turns itself off, no matter how many times I turn it off, it turns itself back on again. Anyone know how to fix this? I'd appriciate any help
(I have tested the latest dev build and the latest stable one)
Thanks in advance!
That doesn't work on the officially supported Nexus 4 either. Therefore, I guess that it's on their TODO list. If you, however, want to make sure it's fixed, you can as always create a bug report on launchpad.net.
So I have built PAC LP Alpha, and everything works great except for the signal. Now if I remember correctly there was someone long ago that was working on getting the KK RIL working, anyone know who that was or if anyone wants to take a stab at it and see if they can fix the RIL or point me in the right direction. PM me if you'd like to try the LP Alpha, can't release til RIL is fixed and til the PAC team is ready to drop their 5.0.x nightlies.
Screenshots if people want to see some life for this phone.
MDMower has an operation CM12 build you can find info at http://forum.cyanogenmod.org/topic/104580-cm12-unofficial-for-fireball/. It boots and runs no problem, I can't check Signal issues because I don't have a Verizon SIM anymore. He does run a modified recovery to swap internal storage and data to make more room. Looks like this is the CM commit that gets radios working http://review.cyanogenmod.org/#/c/81243/.
Beeko said:
So I have built PAC LP Alpha, and everything works great except for the signal. Now if I remember correctly there was someone long ago that was working on getting the KK RIL working, anyone know who that was or if anyone wants to take a stab at it and see if they can fix the RIL or point me in the right direction. PM me if you'd like to try the LP Alpha, can't release til RIL is fixed and til the PAC team is ready to drop their 5.0.x nightlies.
Click to expand...
Click to collapse
Thank you I messaged him, and now I'm really curious how he got his CM12 to boot up, because when I built mine it wouldn't even boot.
wmuflyer said:
MDMower has an operation CM12 build you can find info at http://forum.cyanogenmod.org/topic/104580-cm12-unofficial-for-fireball/. It boots and runs no problem, I can't check Signal issues because I don't have a Verizon SIM anymore. He does run a modified recovery to swap internal storage and data to make more room. Looks like this is the CM commit that gets radios working http://review.cyanogenmod.org/#/c/81243/.
Click to expand...
Click to collapse
Pretty incredible what has been accomplished here.......I am going to be charging the old DINC 4g tonight!
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
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.