Related
I'm new to rooting and running custom roms. Has anyone tried any of the latest version of CyanogenMod 10 for the evo lte. Is it stable is it fully functioning. Sorry for the noobness but we all start somewhere. Thanks
I have been running it all day, I don't know the differences from the previous nightlies, probably the same tiny bugs. I haven't played around with it too much.
I have always been curious as to what the differences are between the MANY JB ROMS we have here. They all have the same problems...
I've been using codefire cm10 JB ROM now for around 3 weeks it seems to me that everything is working fine so far. you should try it out I haven't had any problems yet... I'm going to stick with it
Sent from my EVO using xda app-developers app
Jrobb2007 said:
I'm new to rooting and running custom roms. Has anyone tried any of the latest version of CyanogenMod 10 for the evo lte. Is it stable is it fully functioning. Sorry for the noobness but we all start somewhere. Thanks
Click to expand...
Click to collapse
Ive been using the CMX CM10 JELLYBEAN ROM as my daily driver for the last six weeks and it is great. Personally i think the bugs are totally minor. Nothing you cant deal with really. I liked the CodefireX tweaks. I just update the Rom using the GooManager and for some reason they changed it from NIGHTLY to EXPERIMENTAL for whatever reason. Also noticed the CMX tweak are gone from the update? dont know why. Anyone here know? otherwise the ROM is really fast and stable enough.
Am I alone here? It looks great and is speedy as hell. But after I leave the house and I'm not on wifi any longer all the problems start popping up. Terrible signal (even confirmed using OpenSignal), only hold 3G half the time and NEVER get a 4G connection in the places I always get one on a ICS ROM. Also, camera is worthless. And MMS doesn't work almost always.
I really appreciate all the work everyone puts into it. I couldn't do any of the stuff these people are doing. I've tried CM10 and ParanoidAndroid and I can't wait until they hit a stable/primetime state. Just not there yet.
But if it's just me please somebody chime in! I have done PRL and profile updates on stock ROM before flashing so I don't believe it's that. Stock ROM and Mean ROM both give me great signal/data and 4G.
right now I'm on codefire jb release date 26 plus I flashed the duocoreAOSPmod my phone is fast, and also I used the 3g uncap codefire tweak. I'm not having any 3g speed problems.
the reason why I'm still on #26 is because when I flashed the 04 nightly the WiFi will not work it just says error. So hopefully they fix that then I will update. If not I really would hate to discard codefire cause I like it a lot.
Sent from my EVO using xda app-developers app
Hi 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.
I had a rooted S3, Multiple ROM's and my google maps(GPS signal) just never worked right. seemed best on the last AOKP milestone....
So I swap over to my friends old i605, Flash that version of the AOPK milestone which is still 4.3 and GPS will not locate at all. What A pain. This phone had an old 4.2 Liquid smooth ROM (4.2) and it worked fine. Flashed AOKP 4.3 now not at all. ROM is rock solid besides that so i'd like to stay on it, but it absolutely kills me to have to use my wife's Iphone when we need Nav.....
Thanks for the help...
freezy74 said:
I had a rooted S3, Multiple ROM's and my google maps(GPS signal) just never worked right. seemed best on the last AOKP milestone....
So I swap over to my friends old i605, Flash that version of the AOPK milestone which is still 4.3 and GPS will not locate at all. What A pain. This phone had an old 4.2 Liquid smooth ROM (4.2) and it worked fine. Flashed AOKP 4.3 now not at all. ROM is rock solid besides that so i'd like to stay on it, but it absolutely kills me to have to use my wife's Iphone when we need Nav.....
Thanks for the help...
Click to expand...
Click to collapse
when i have gps problems in roms, i just install TopNTP, and chose Derek Gordon. in my case it works a lot.
this is the thread in xda http://forum.xda-developers.com/showthread.php?t=2198319
Bonkurei said:
when i have gps problems in roms, i just install TopNTP, and chose Derek Gordon. in my case it works a lot.
this is the thread in xda http://forum.xda-developers.com/showthread.php?t=2198319
Click to expand...
Click to collapse
Didn't seem to work for me, not sure if its just me or not...
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
Hey guys, I've been fresh on a stock and unrooted build over the past several months (no headaches anymore!) and recently, an acquaintance of mine was willing to give me his Galaxy S4 which to my delight was still on MDK. I've been out of the scene and flashing in general for the past five months, and I know that there's this Lollipop business right now, but what is the best ROM for the MDK S4 at this point?
I've heard that Cyanogenmod 12.1 and lollipop builds in general are having a host of problems with bluetooth, the GPS (which I actually very much need), and battery drain. What is an acceptable ROM in your guys' honest opinion that can be used as a very solid daily driver (hopefully on Lollipop, willing to use KK though) that has GPS and bluetooth?
Thanks in advance!
Another CM12.1 tidbit. If your new to you MDK S4 is the Verizon variant, the compass is borked, too. If it's any other carrier users say it works.
FernBch said:
Another CM12.1 tidbit. If your new to you MDK S4 is the Verizon variant, the compass is borked, too. If it's any other carrier users say it works.
Click to expand...
Click to collapse
This, however navigation still works for directions I know what direction I am looking at and moving in most of the time.
Hyperdrive is also a fan favorite but is currently on KK. I was using Dan's GPE lollipop ROM but switched back because I couldn't get Netflix to run over mobile data. If that doesn't bother you, I recommend that to you.
Otakulad said:
Hyperdrive is also a fan favorite but is currently on KK. I was using Dan's GPE lollipop ROM but switched back because I couldn't get Netflix to run over mobile data. If that doesn't bother you, I recommend that to you.
Click to expand...
Click to collapse
HD is great! Currently my DD until a lollipop version of Touchwiz for JFLTEVZW is released.
Sent from my SCH-I545 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2385271&page=226
Rock Solid Super Fast my GPS works fine and Bluetooth with my Jaybird X's is fine !
Illogi.xbone said:
This, however navigation still works for directions I know what direction I am looking at and moving in most of the time.
Click to expand...
Click to collapse
That is because orientation is determined by GPS when moving, not by the compass.
It is now a moot point as invisiblek fixed the compass in CM 11, 12.0, & 12.1 two days ago.
So nice to see the compass and all third party apps that rely on it work properly again.
ROM on android 5.x, verizon?
Ryukouki said:
I've heard that Cyanogenmod 12.1 and lollipop builds in general are having a host of problems with bluetooth, the GPS (which I actually very much need), and battery drain. What is an acceptable ROM in your guys' honest opinion that can be used as a very solid daily driver (hopefully on Lollipop, willing to use KK though) that has GPS and bluetooth?
Click to expand...
Click to collapse
Which lollipop roms are fully working with no major connectivity issues now? Was thinking of trying cyanogen 12.1, but noticed its not officially released. Is this stable enough to use everyday? If not, are there other 5.x roms I should consider?