As always, you are responsible for your device. Use common sense and make backups
In case anybody wants a pure cm12 for the kltespr, here it is. Was built from cm12 sources, 5.0.2.
Downloads below
Use lollipop gapps, Link Below
I installed over an NKD leak build, after doing a full wipe of data, internal sdcard, cache, system...all of the things
I had a problem with TWRP 2.8.3, so I used the one I built a while ago, link below
***Flashing Directions***
Boot to recovery
Wipe everything
Flash rom zip and gapps zip
***Updating directions***
Boot to recovery
Flash newer version of this rom
Wipe Caches
Everything seems to work so far.
I plan on making some changes, but figured I would throw up a "vanilla" cm12 thread in case anybody wanted it and didn't want to build it themselves.
***Recoveries***
My old TWRP 2.8.0.1-gt build
https://www.androidfilehost.com/?fid=95864024717072487
md5sum 93f46caaac3ce006af5d60795ad16ec8
***GAPPS***
Lollipop GAPPS
http://downloadandroidrom.com/file/gapps/5.0/gapps-lp-20141109-signed.zip
***Downloads***
Original Manual Build
Fully tested and all seems good
https://www.androidfilehost.com/?fid=95864024717072482
md5sum b99c37e1df51739dec9181147ab86c8b
First build with an automated build script
Please let me know if anybody tests this, because I have not yet, but the only changes are pulls from upstream CyanogenMod
https://www.androidfilehost.com/?fid=95864024717073976
md5sum c9c252b907547e44b480046fd82273da
New Build 1/5/2015
Pulling in upstream changes, new su and terminal app included
https://www.androidfilehost.com/?fid=95887005526786941
md5sum 76d264f0fabe38bcef8eb3ecdea84c6b
New Build 1/7/2015
Fixed updater script, more upstream changes. No need to re-flash GAPPS anymore when updating to the newest version, just flash then wipe caches.
https://www.androidfilehost.com/?fid=95887005526788129
md5sum 1366c215ddfa8e46d117c6760f7af441
New Build 1/8/2015
UNTESTED - Pulled in lots of changes from CM upstream, please let me know how things go.
https://www.androidfilehost.com/?fid=95887005526788863
md5 9b2c549705edc80533dc78fc19d3d206
New Build 1/12/2015
Pulled in more upstream commits - see review.cyanogenmod.org branch:cm-12.0 status:merged between Jan 8th and Jan 12th
https://www.androidfilehost.com/?fid=95897840722641504
md5sum b3ace7b8581cbbd55616a70d46ef4e2b
New Build 1/20/2015
Pulled in more upstream, including theme stuff, testing now
https://www.androidfilehost.com/?fid=95897840722646871
md5sum 88c44248bde68284c3878c4c2cf31952
Another New One for today 1/20/2015
Pulled in more upstream, attempt fix on battery drain, inverted colors, themes, notification panel options in settings and a few more things I think
https://www.androidfilehost.com/?fid=95897840722646992
md5sum f4f8ee1e6c9f65ac4852e96ab1c3e629
1/24/15 Build
Honestly didn't really dig through CM changelog, but it seems like the noise is gone, and I don't really know why but it feels generally snappier and less laggy in certain spots
https://www.androidfilehost.com/?fid=95916177934516437
md5sum 44cc73da8b931f0f17aedd5695d8c32a
1/26/15 Build
Lots of Bluetooth updates, along with a few other upstream changes
https://www.androidfilehost.com/?fid=95916177934517707
md5sum 2e4d62f5c00105572ea8ad34d38b3d97
1/26/15 Boost Mobile Test build
I have no idea if this will fix the Radio problem, and no way of testing, so please let me know...Everything is the same as the Sprint build with one or 2 tweaks to try to force it to Boost
https://www.androidfilehost.com/?fid=95916177934517723
md5sum d252b3f5ed04749b8c4fae496ef7b600
Build 1/27/15
Pulling in a few changes I missed yesterday
https://www.androidfilehost.com/?fid=95916177934518355
md5sum daa24071a13ea36330e1c9455b3a7bf0
Build 1/27/15 Boost Mobile
Pulling in a few changes I missed yesterday, Boost Mobile build
https://www.androidfilehost.com/?fid=95916177934518385
md5sum 60062ccc93e7cce2ccd5f40bc5c83b21
Build 1/29/15
Nothing super special, just pulling upstream changes. Missed a few regarding new wallpapers, will be in the next one
Sprint Version
md5sum f3afc625e033c4a7483437ff560e0ec3
Boost Mobile Version
md5sum 4b1f0d2d85d21aeac2561b8f572a1fdd
Build 2/2/15
Pulling upstream changes, looks like some audio and video fixes are included. Still need to pull a few things into my forked repos, but most important commits should be included.
Sprint Version
md5sum 0bc3710bc2fc89dec965b1d18ed95d9e
Boost Mobile Version
md5sum 2143fde6f85f8f5f35a4ca685f79712f
Build 2/6/15
Pulling upstream changes, been a few days and I honestly haven't checked the commit list other than those of my forked repos. Not much special in my forked repos but I am sure there has been plenty of changes upstream in the other repos
NOTE - I haven't tested this build yet, got a few things to do before I can flash it
Sprint Version
md5sum ddb910a56806078529e7359e61412737
Boost Mobile Version
md5sum 0b323c7e8a401fcc9f4c3af65789c915
Initial S5 Sport test buildSorry not working yet
md5sum 5e10ff86a819a4abf48e697490572685
2/9/14 Build
Sprint Version
md5sum 817cc516c6a7547be34b88efa10ceecf
Boost Mobile Version
md5sum d2250ff799ca3ae0ca89995ae1ea0ffc
New Sport test build
Sport Test Build
md5sum 67259518bcc973292eb59f802ae50fbd
Test build 3 for sport, manually modified kernel image with fstab info that was missing and a few other things
Sport test build 3
md5sum 1dc912e626afa448b4b52309d3c4d594
Test build 4
Sport test build 4
md5sum 54403b46c3370cac21df3bece0b24b56
2/14/15 Builds: Should include the 4k camera, snapshots from video and a few other things from upstream. Changes pulled in on the 13th, so anything commited on or before the 13th will be included. Friday the 13th Builds
Sprint S5
md5sum 730365184f1fce03aec31a45ef3a3e9a
Boost S5
md5sum 9b51e4e3ffd1090228cd1a440a78d16b
S5 Sport Test Build #5
md5sum 30baeac0f03c396f0bbb247a4b727ccf
2/18/15 Builds: Does not include wifi scan fix to raise the time between wifif scans, and may have missed a commit or 2 from upstream.
Sprint S5
md5sum 5779e6ca7a5c67f9314dc1059a66cfbd
Boost S5
md5sum 257cb01c561dc63013d5d264fd319673
2/24/15 Builds: Does not include wifi scan fix to raise the time between wifi scans, sorry I fogot to put them in. Fixed the BT problem from last build and pulled in all upstream changes.
Sprint S5
md5sum 1fee6e21e0d16ce0fa116b7a297128b4
Boost S5
md5sum 12a27e7286606af9b188d8fc554f0457
New Sport test builds, these are untested please make a backup before flashing:
test 6
test 7
3/2/15 Builds: Pulled upstream, attempted to change wifi scan interval. Did not test yet, let me know how it goes and if the wifi scan helped
Sprint S5
md5sum f7a2582ef3645892bafd857620da72e1
Boost S5
md5sum c66fc6844b67052d4e495c32588b0586
3/9/15 Builds: Pulled upstream, rebuilt sport sources from the ground up and initial tests are good. Changed build status to weekly and bumped version number.
Sprint S5
md5sum 70281b5359094529af1d2c046923c11b
Boost S5
md5sum 52669293004ba88d84e7422df8cacd02
S5 Sport
md5sum ad13c803d0783ddd82abd0717816492f
3/16/15 Builds: Pulled upstream, trying some new libs on sport build
Sprint S5
md5sum a6bf3da9c8a5d121a2dbfa5734504209
Boost S5
md5sum 8debd7379852d975e03fbf7c7001a8b4
S5 Sport
md5sum 7f41290fe813e967124ff49cef0160f5
3/25/15 Builds: Pulled upstream, nothing else to speak of
Sprint S5
md5sum b0f21e568f49ab6595381d41f27664a7
Boost S5
md5sum 86baf09812f18f8d8628e010eda919b4
S5 Sport
md5sum 28c3a16e7d1b37d951641a2d1b0ec152
***Firmware files for non sport models***
These MUST be flashed in odin, and can be flashed right over your CM install to update your baseband
OA6, no system, no kernel, no recovery
***Thanks***
CyanogenMod Team
The Muppets
Team Nocturnal
Any and all testers of my work, especially those who donate(it is always appreciated)
***Big Thanks to all those who have Donated***
@ToeJullar @Remesar @jphoff @Stealth5325 @jared-wallace @robak1965
Someone also donated without logging in, I can see your real name in paypal but not sure if you want me to mention it. Please let me know your username if you want a mention, and thanks again!!
If you feel that I forgot you please let me know
***Sources***
https://github.com/Linuxdork/android
If you would like me to link you recoveries, gapps or anything else here just let me know and I will be happy to put it in.
Bluetooth, wifi, NFC, Phone, and camera all seem to work fine. No FCs at all yet. Installed a bunch of apps all working fine, even facebook.
Wifi hotspot works, didn't test any other forms of tethering
Must flash gapps to get to the setup process. Tap n go works for account setup. Tap n pay works on the vending machines near me, one time it took 2 taps to pay but that was probably my fault.
Got the incoming call bug fixed, will reserve this post for other known bugs
All in all this feels pretty stable considering how early it is in the Lollipop game, I am using it as my daily driver and haven't been let down by it yet.
**Bugs**
Reported from users:
Moving apps to SD seems to be qwuirky, reports of SD formatted as Ext-SD through philz working, but other formats not working
Time problems - Manually set time zone, instead of leaving it on automatic and things should work fine
Help me find more!!
miked63017 said:
Got the incoming call bug fixed, will reserve this post for other known bugs
**Bugs**
Help me find some!!
Click to expand...
Click to collapse
Thank you very much for the straight CM12 build. This helped me, because it confirms that many (not all) of the problems I've been having with other CM12 builds on kltespr appear to be in the base, and not tweaks or mods. Here's a list that I just posted over in @vinman12 Team Nocturnal CM12 thread.
The good:
Camera, video, audio (with a wired connection), WiFi & mobile data are all good.
The bad:
Bluetooth connections are iffy, at best. BT sharing crashes & BT audio device connections are hit or miss.
Phone calls have been randomly troublesome. Most of the time the dialer works great calling and receiving. There are other times I have to retry 2 or 3 times just to get dialing started. Sometimes I can answer a call, but neither of us can hear the other one even though the connection still appears live. And sometimes the dialer won't disconnect after a call is finished, and even killing the app doesn't free the connection requiring a reboot.
Let me know if you want logs sent. If so, how: PM, just posted here, stuck on pastebin or whatever else you prefer.
Greg Robinson
greogory said:
Thank you very much for the straight CM12 build. This helped me, because it confirms that many (not all) of the problems I've been having with other CM12 builds on kltespr appear to be in the base, and not tweaks or mods. Here's a list that I just posted over in @vinman12 Team Nocturnal CM12 thread.
The good:
Camera, video, audio (with a wired connection), WiFi & mobile data are all good.
The bad:
Bluetooth connections are iffy, at best. BT sharing crashes & BT audio device connections are hit or miss.
Phone calls have been randomly troublesome. Most of the time the dialer works great calling and receiving. There are other times I have to retry 2 or 3 times just to get dialing started. Sometimes I can answer a call, but neither of us can hear the other one even though the connection still appears live. And sometimes the dialer won't disconnect after a call is finished, and even killing the app doesn't free the connection requiring a reboot.
Let me know if you want logs sent. If so, how: PM, just posted here, stuck on pastebin or whatever else you prefer.
Greg Robinson
Click to expand...
Click to collapse
I have heard about everything mentioned, I have yet to run into any of the bluetooth stuff personally but I have noticed the phone call problems. I did actually cherry pick a few commits from a few different repos to get the RIL working properly, so I guess in one way the cm12 base has been slightly modified. I did want to keep it as clean as possible to track the state of base as well, but I do plan on cherry picking more commits here and there to test things. Before pulling in the RIL changes you couldn't even answer the phone, it just used some weird built in ringer that went off until you rebooted, even after the call hung up.
I will try to stay up to date with what other people are doing to fix these problems, but really this build was more for getting a good Lollipop build env setup for other things. I do plan on getting nightlies going, in case you couldn't tell by the filename , but I can't say for sure how much this is gonna stray from base. So I guess for now, if the bugs are in base, and other builds, they will most likely be here too.
Can you give me a good way to run into the bluetooth problems you have had? I only use it for phone calls in my vehicle and haven't noticed any probs yet, it also seemed to work fine for the tap'n'go account setup when I first installed the rom.
miked63017 said:
I have heard about everything mentioned, I have yet to run into any of the bluetooth stuff personally but I have noticed the phone call problems. I did actually cherry pick a few commits from a few different repos to get the RIL working properly, so I guess in one way the cm12 base has been slightly modified. I did want to keep it as clean as possible to track the state of base as well, but I do plan on cherry picking more commits here and there to test things. Before pulling in the RIL changes you couldn't even answer the phone, it just used some weird built in ringer that went off until you rebooted, even after the call hung up.
I will try to stay up to date with what other people are doing to fix these problems, but really this build was more for getting a good Lollipop build env setup for other things. I do plan on getting nightlies going, in case you couldn't tell by the filename , but I can't say for sure how much this is gonna stray from base. So I guess for now, if the bugs are in base, and other builds, they will most likely be here too.
Click to expand...
Click to collapse
And, of course, everything is working perfectly now that I'm actively trying to make something fail while I'm running logcat.
Hey, I know: it's Heisenburg's fault! We can only see when something fails or collect debug data, but not both at the same time. Because uncertainty. Those deranged quantum bastards hosed everything up for all of us normal geeks.
---------- Post added at 09:26 AM ---------- Previous post was at 09:19 AM ----------
And to prove my theory, about 2 seconds after I Ctrl-C'd logcat and cleared it to try again, BT failed in the middle of my favorite AC/DC song. But on the bright side, I have a 9MB logcat file of exactly zero bugs.
greogory said:
And, of course, everything is working perfectly now that I'm actively trying to make something fail while I'm running logcat.
Hey, I know: it's Heisenburg's fault! We can only see when something fails or collect debug data, but not both at the same time. Because uncertainty. Those deranged quantum bastards hosed everything up for all of us normal geeks.
---------- Post added at 09:26 AM ---------- Previous post was at 09:19 AM ----------
And to prove my theory, about 2 seconds after I Ctrl-C'd logcat and cleared it to try again, BT failed in the middle of my favorite AC/DC song. But on the bright side, I have a 9MB logcat file of exactly zero bugs.
Click to expand...
Click to collapse
Lol, well if you get a logcat with the error send it over and I will take a look. I will look around and see if there is any BT specific commits we can pull in to try.
Sent from my SM-G900P using XDA Free mobile app
I left CM12 because it had issues playing videos in Chrome, but I think I'll give this a shot later Thanks for sharing mike!
ghostzyden said:
I left CM12 because it had issues playing videos in Chrome, but I think I'll give this a shot later Thanks for sharing mike!
Click to expand...
Click to collapse
My pleasure, fwiw my daughter has been watching crap all day on my phone in chrome, mostly YouTube(apparently chrome is default app when hitting a link). I do know that I cannot play videos in chrome from my plex server, but the plex app worked when I briefly tested it, and plex worked with chromecast.
Sent from my SM-G900P using XDA Free mobile app
miked63017 said:
My pleasure, fwiw my daughter has been watching crap all day on my phone in chrome, mostly YouTube(apparently chrome is default app when hitting a link). I do know that I cannot play videos in chrome from my plex server, but the plex app worked when I briefly tested it, and plex worked with chromecast.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Ok appreciate it
Anybody notice any other bugs? I see the download counter going up but not much feedback. I haven't rebooted at all since I flashed it, 2-3 days, wondering if everyone else's experience is the same? Anybody else using the hotspot, do you have a tile for it in the notification panel? It looks like its supposed to be there but I didn't see it originally so I found a sqlite table to add to and got it working, but not sure if it works out of the box for anyone.
Sent from my SM-G900P using XDA Free mobile app
miked63017 said:
Anybody notice any other bugs? I see the download counter going up but not much feedback.
Click to expand...
Click to collapse
Not a problem here, just not much time or functioning brain cells to test & post results today.
I started over with a serious cleaning and repartitioned with the original Samsung PIT and a full erase in Odin. Then I installed the NKD firmware from @tdunham, immediately followed by your CM12. Since then, everything I had trouble with on CM12 has been totally stable. No BT issues, no phone issues, and not horrible battery life.
I'm going to give @vinman12's latest Team Nocturnal CM12 another test later this evening or tomorrow morning. I plan to use the latest TW Lollipop for a few solid days after that.
I'm wondering if those of us who frequently flash back & forth among firmware versions, boot loaders, TW & CM have "polluted" our partitions enough over time that simple formatting leaves too much crap in the sd cells that rarely get zeroed out. My I/O is definitely faster after the fresh PIT install.
greogory said:
Not a problem here, just not much time or functioning brain cells to test & post results today.
I started over with a serious cleaning and repartitioned with the original Samsung PIT and a full erase in Odin. Then I installed the NKD firmware from @tdunham, immediately followed by your CM12. Since then, everything I had trouble with on CM12 has been totally stable. No BT issues, no phone issues, and not horrible battery life.
I'm going to give @vinman12's latest Team Nocturnal CM12 another test later this evening or tomorrow morning. I plan to use the latest TW Lollipop for a few solid days after that.
I'm wondering if those of us who frequently flash back & forth among firmware versions, boot loaders, TW & CM have "polluted" our partitions enough over time that simple formatting leaves too much crap in the sd cells that rarely get zeroed out. My I/O is definitely faster after the fresh PIT install.
Click to expand...
Click to collapse
Agreed, I think a wipe should dd /dev/zero to the partition instead of just formating. But theoretically speaking I don't think it should make a difference because any data left over should be written over as new data is saved, and not be skipped to make fragmentation. But I do notice "oddities" when jumping back and forth a lot.
Either way, glad the problems went away, and fwiw I flashed a clean NKD leak in Odin prior to flashing this as well.
Sent from my SM-G900P using XDA Free mobile app
Updated OP with latest build, untested, but it pulls in some upstream code changes from the CM team. Also, re-formatted OP.
Rom
As of right now im having no problems. Installed earlier today and gonna let it run a few days before i say anything. I have noticed that i cant play NBA jam game, the touch screen doesnt work when the game loads. Could be on their end or it just could be a CM issue. Anyway, thanks for the stable rom!
[ROM] Un-Adulterated CM12 5.0.2
miked63017 said:
Got the incoming call bug fixed, will reserve this post for other known bugs
All in all this feels pretty stable considering how early it is in the Lollipop game, I am using it as my daily driver and haven't been let down by it yet.
**Bugs**
Reported from users:
Same, or similar BT bugs as other CM12 builds. I haven't ran into them but I only use BT for calling from my vehicle.
Same, or similar phone call flakiness bugs as other CM12 builds.
Help me find more!!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This has happened twice. I'm using the bot build as of 1/2/15. This also happened with another 5.0.2 CM based rom I tried. The only way to get out of that message is to take the battery out and restart. Any ideas what causing it?
Prince_Basil said:
This has happened twice. I'm using the bot build as of 1/2/15. This also happened with another 5.0.2 CM based rom I tried. The only way to get out of that message is to take the battery out and restart. Any ideas what causing it?
Click to expand...
Click to collapse
I have had it happen once while the phone was in my pocket not being used. I had it happen about 5-6 times on the stock NKD leak, I suspect the auto root kernel on that. Not sure why it happens on CM.
Did you get the log from when it happened by any chance? Its definitely a kernel panic, figuring out what is happening right before the panic would help to troubleshoot. If we can figure out why it might be a simple edit in the kernel build.
Whatever other info you can give might be helpful, like I said its only happened once to me while the phone was in my pocket. It just happened to me the day before yesterday, before that I hadn't had to reboot for any reason.
Sent from my SM-G900P using XDA Free mobile app
miked63017 said:
I have had it happen once while the phone was in my pocket not being used. I had it happen about 5-6 times on the stock NKD leak, I suspect the auto root kernel on that. Not sure why it happens on CM.
Did you get the log from when it happened by any chance? Its definitely a kernel panic, figuring out what is happening right before the panic would help to troubleshoot. If we can figure out why it might be a simple edit in the kernel build.
Whatever other info you can give might be helpful, like I said its only happened once to me while the phone was in my pocket. It just happened to me the day before yesterday, before that I hadn't had to reboot for any reason.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
If you could show me how to do that I can get it for you. I wiped my phone, I installed your ROM, then installed Gapps, then installed Updated SU root. Then I just started using my phone. Installed all my apps and fixed my settings. Also, I've been having issues with moving apps to the SD card. It says I have no room but its a 32 GB SD card with 22 GBs free. And battery life is really bad. I looked to see what might be causing it and it the highest one Miscellaneous... So I'm not sure what that is. The screen shot only shows 11% because my phone just restarted. But before that it was at 67%.
Prince_Basil said:
If you could show me how to do that I can get it for you. I wiped my phone, I installed your ROM, then installed Gapps, then installed Updated SU root. Then I just started using my phone. Installed all my apps and fixed my settings. Also, I've been having issues with moving apps to the SD card. It says I have no room but its a 32 GB SD card with 22 GBs free. And battery life is really bad. I looked to see what might be causing it and it the highest one Miscellaneous... So I'm not sure what that is. The screen shot only shows 11% because my phone just restarted. But before that it was at 67%.
Click to expand...
Click to collapse
Not sure what you mean by updating SU root, CM has all its root stuff built into the settings menu. Did you flash something for SU, and if so did it include a kernel?
I do notice slightly reduced battery performance, but if I setup the auto brightness control and a few other things my battery is at about 10% at the end of the day. I am sure battery performance will get better as more people begin to work on CM 12.
Not sure the best way to get the kernel logs off the top of my head, but if you flashed a SU package that included a kernel it could be related to your kernel panics.
I will look into the logs and your SD card issue over the next few days.
Sent from my SM-G900P using XDA Free mobile app
miked63017 said:
Not sure what you mean by updating SU root, CM has all its root stuff built into the settings menu. Did you flash something for SU, and if so did it include a kernel?
I do notice slightly reduced battery performance, but if I setup the auto brightness control and a few other things my battery is at about 10% at the end of the day. I am sure battery performance will get better as more people begin to work on CM 12.
Not sure the best way to get the kernel logs off the top of my head, but if you flashed a SU package that included a kernel it could be related to your kernel panics.
I will look into the logs and your SD card issue over the next few days.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95784891001616249
Related
This is a dedicated thread for the CM10, CM10.1 and CM10.2 port for the Samsung X Cover 2 (GT-S7710). The port is in a beta state. The source is based on the CM port for golden from OliverG96!
Recovery
A working CWM port with minor issues is discussed and available here.
Download
All files are available here or here.
Changelog CM 10:
2013/07/26: Initial preview
2013/07/27: Fixed Wifi
2013/07/29: Fixed GPS
2013/09/04: Userdebug build to get rid of red frame
discontinued, but porting changes for the camera, USB etc from cm-10.1 branch should not be a big deal
Changelog CM 10.1:
2013/09/15: Alpha release 0:
Phone and mobile data
GPS
WIFI (tethering is untested and probably broken)
Bluetooth (tested a2dp and a headset/car)
Audio (EQ is untested)
Front and rear camera work. Video recording is broken!
USB MTP works. PTP is untested.
SD card
adb
Flash light
Video playback is broken.
2013/09/30: Alpha release 1:
Fixed video playback and recording.
CM updates and account wizard added.
2013/10/14: Alpha release 2:
AOSP lpm animation
Updated video processing (Thanks Oliver)
CM Updates
2013/10/20: Alpha release 3:
Fixed Torch
Removed automatic brightness menu
2013/10/27: Alpha release 4:
Fixed WIFI tethering
Changelog CM 10.2:
2013/11/02: Alpha release 5:
Bump to CM 10.2 - same functionality as in Alpha 4.
CWM build on cm-10.2 branch is broken - use from cm-10.1 if needed.... fixed.
2013/11/19: Alpha release 6:
CM Updates
Added fix for low volume in incoming calls (Thanks Oliver!)
Some source cleanup
2013/11/24: Alpha release 7:
CM Updates: Wallpaper, Bootanimation
2013/12/05: Alpha release 8:
CM: Build with cm-10.2 stable sources
2014/01/12: Alpha release 10:
CM: Source update.
2014/02/04: Alpha release 11:
CM: Source update.
Fixed random reboots.
Changelog CM 11.0:
2013/12/31: Alpha release 9:
Preview CM11 image. OMX/Camera is broken. Just for testing and not ready for daily usage. Needs latest recovery and full wipe.
Known Issues
BT hands free. Connection/pairing works, but the audio path is broken.
stock MMS app
Source
The source is stored in my github account.
Questions and Bug
Please do not contact me directly if you encounter bugs or you have questions about the port. When you're not yet allowed to post is this thread - post somewhere else, but don't send me a PM. Thanks for that.
Disclaimer
Don't flash this image unless you really know what you're doing! I'm not responsible for any damage what-so-ever done to your phone, as with any ROM, you accept this risk. You use this software at your own risk.
Thanks to:
OliverG96 for his CM10/CM10.1/CM10.2 port of golden.
TeamCanjica for the u8500 common stuff.
TheBoegl for hosting the images
You're great, its super:good:
That's the problem with me -
And again you did a very good job :good:
Can I flash the new rom with GPS like an update, so that i do not have to install everything again?^^ just wipe cache and dalvik and leave the rest as it is?
Btw now the camera is the last thing missing for my holiday^^, then I can test your rom for 2 weeks outdoor
So keep on your excellent work :victory:
after flashing your latest rom, there is sometimes a red frame around the display.
Hello, I used the new Custom ROM, I liked but did not know why constantly loses coverage of the mobile operator. I have not tried GPS, WIFI is working well.
I hope you like comment on Custom ROM to help clear the error that occurred. This is not a criticism. I have great respect for you and what you do with it.
Cheers.:laugh:
BTW battery lifetime is much better than on stock rom. 6 h without charging, gps and wifi off, a lot of facebook, whatsapp, email and some gaming, 91% left :good: seems to be that you can use the Xcover now for a couple of days without charging
p.Lipov said:
Hello, I used the new Custom ROM, I liked but did not know why constantly loses coverage of the mobile operator. I have not tried GPS, WIFI is working well.
Click to expand...
Click to collapse
Thanks for testing! I didn't notice any difference by now - the link has been pretty poor with the stock image as well. I'll put it on my list and make a comparison. Anyone knows a app to plot the link quality?
cheers,
flxo
aufdroge said:
And again you did a very good job :good:
Can I flash the new rom with GPS like an update, so that i do not have to install everything again?^^ just wipe cache and dalvik and leave the rest as it is?
Click to expand...
Click to collapse
In this special case: yes. The image from the 29th just has one config file added. Sometimes it's simple
after flashing your latest rom, there is sometimes a red frame around the display.
Click to expand...
Click to collapse
Yep. I noticed that also. No concrete idea where it comes from but I think there's a problem with the settings provider....
cheers,
flxo
GPS is not working for me, any idea how to fix it?
Sent from my GT-S7710 using xda app-developers app
Camera and flashlite(torch) not work
USB connection - windows cannot find drivers
Red frames around display
Wifi ok
Gps ok
Bt not tested
Nice work, thx :good:
Hi guys,
thanks for testing! I will be off for a week. So maybe you can fix some issues in the meantime?
cheers,
flxo
I like the Custom ROM. I can not wait to get the new clean fix. Phone with him is not the same, it is great. Thank flxo
Hey, I am really interested in testing this, just want to verify that I flash latest from CWM correct? I am fairly used to custom roms, but this is my first samsung and they seem to do things a bit different so better ask then sorry. ^^
Great job, keep on goin'. Thank you for your work...
EDIT: flashed it and gapps, and works fine. feels faster than stock. thx
Problems:
- sponatneous reboots
- red frame
Hello,
Loving the mod, could not wait to get away from Samsungs mess.
Does anyone experience call drops after a couple of minutes? (Sound cuts out but does not seem to disconnect)
Also:
Red frame and reboots
Nevertheless, keep up the good work!
Hey, has this project moved somewhere and I missed it or is it just a low peak atm? I am asking as it seemed to have a lot of activity last month but nothing this. I would love to see CM10 fully working on the Xcover 2 as the phone has no custom roms what so ever that I can find.
Superbia said:
Hey, has this project moved somewhere and I missed it or is it just a low peak atm? I am asking as it seemed to have a lot of activity last month but nothing this. I would love to see CM10 fully working on the Xcover 2 as the phone has no custom roms what so ever that I can find.
Click to expand...
Click to collapse
Me too... *push*
Superbia said:
Hey, I am really interested in testing this, just want to verify that I flash latest from CWM correct? I am fairly used to custom roms, but this is my first samsung and they seem to do things a bit different so better ask then sorry. ^^
Click to expand...
Click to collapse
Yep - thats the latest version.
Hi,
Superbia said:
Hey, has this project moved somewhere and I missed it or is it just a low peak atm? I am asking as it seemed to have a lot of activity last month but nothing this. I would love to see CM10 fully working on the Xcover 2 as the phone has no custom roms what so ever that I can find.
Click to expand...
Click to collapse
I've been off for three weeks and hope I can continue working on the port in the next days. Next item is the camera and some annoying stuff like the need to enable/disable the airplane mode once to get mobile data to work..
cheers,
flxo
flxo said:
Hi,
I've been off for three weeks and hope I can continue working on the port in the next days. Next item is the camera and some annoying stuff like the need to enable/disable the airplane mode once to get mobile data to work..
cheers,
flxo
Click to expand...
Click to collapse
Sweet. Your vacation was well deserved! I was just curious if CM team had shut you down for some unknown reason or if you just changed phone etc
The red frame is gone, but therefore an errormessage pops up, when I try to install something from google play --> unknown errorcode "-24". I have flashed the rom 4 times, but nothing changes
Sent from my GT-S7710 using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device: i605 (Verizon Note 2)
Hey all! I am here to bring you the latest version of AOSPA-Legacy to the Verizon Galaxy Note 2! This is always compiled from the latest AOSPA-Legacy sources compiled with the CyanogenMod kernel. I have added some new features to the AOSPA source, but there are no extra apps in the final build.
NOTICE:
This is an unofficial build that I made for myself that I am sharing with all of you. I have a set use for my phone and therefore cannot test everything. Because of this, your warranty is now void. I am not responsible for any damages this ROM does to your phone, but just know I only upload after testing on my phone. Results may vary. Also, this ROM will be updated when I get around to it. I do not have the infrastructure to build nightlies on this computer (it's a laptop btw), and will only update to add new features/fix bugs, maybe weeklies, haven't decided yet. Perhaps I could become this device's new maintainer since everyone seems to be gone, but I'll get to this later.
Without further hesitation, let's get to it!
INSTRUCTIONS:
MAKE SURE YOUR BOOTLOADER IS UNLOCKED!!
Reboot into either the latest TWRP/Philz Recovery
Wipe Data, Caches, etc.
Install this Rom (Download Below)
Install PA-Gapps
Wipe caches again (eh, why not?)
Reboot
???
PROFIT!
Downloads
AOSPA-Legacy 4.6 Beta 6 (Build date: 11/19/14) --> HERE
(Check Second Post for Changelog and Experimental Builds!)
Get your GApps here! --> THREAD
BUGS
Google Chrome v39 always starts in floating mode (fix in second post!)
I can't seem to get a GPS lock, will definitely look into this
Stock Flashlight app doesn't work, anything from the Play Store does though
Anything else from CM/PA that's been a problem on this phone
You tell me (please!)...
THANKS!
AOSPA-Legacy -- For the amazing ROM and sources (Github)
CyanogenMod -- For the kernel sources (Github)
DreamFX -- For Unofficially/Officially fixing the VA/PA texting issue (NOT RELATED TO THIS ROM! But without this I wouldn't have played with AOSP/CM again!) (Link to fix)
UPDATE:
(Downloads in 1st post!)
(Experimental build downloads are under their build dates)
11/22/2014
Experimental Build! (Should still stable, just need some feedback on these 2 new features) -> Download
Added Dynamic System Bars!!! (You'll find this under Settings->Display)
Added Mobile Network Battery Saver Mode(Automatically switches to 2G Network after the screen is for 30 seconds [unless a music streaming service is active] and sets it back to 3G/4G when the screen is turned on!)
11/19/2014
Added a swipe to switch between Quick Settings and Notifications
Added Quiet Hours
COMING SOON!
The new Card-Based Recent Apps
Gerrit is down but being fixed, so I am not able to cherrypick these two items. Hopefully PA can resolve this soon and they will be added.
GOOGLE CHROME UPDATE: There seems to be an issue with the latest build of Google Chrome (v39) where the app will always start in floating mode. To return to full screen Chrome, clear app data after updating from the Play Store and every time you open Chrome pull up the Recents Menu (default is long press home button) and select Chrome again. It will now be full screen. This seems to be an issue for all of AOSPA.
Another fix is to stay on Chrome v38 and not update. Link To apk
Weird issue after installing
Not sure if it is related to this ROM or not but I had not encountered this previously under any other ROM. Installed this last night - wiped everything with all the normal steps. Also installed the latest PA GAPPS (the link in the first post - installed the Full version). Restored most of my apps with TB and everything went as normal. This morning, the phone, while just sitting on my desk, made a noise (maybe like I got a notification). I picked it up and it was pretty much loading and displaying things from different apps and videos on my phone without any input from me. I could not get it to respond to any button presses and was even having issues trying to power it down until I just pulled the battery. I re-loaded one of my backups from another ROM and everything appears to be back as it was and I've not experienced the same issue at this point. Can't say 100% it was this ROM but thought it better to at least note it.
chameo53 said:
Not sure if it is related to this ROM or not but I had not encountered this previously under any other ROM. Installed this last night - wiped everything with all the normal steps. Also installed the latest PA GAPPS (the link in the first post - installed the Full version). Restored most of my apps with TB and everything went as normal. This morning, the phone, while just sitting on my desk, made a noise (maybe like I got a notification). I picked it up and it was pretty much loading and displaying things from different apps and videos on my phone without any input from me. I could not get it to respond to any button presses and was even having issues trying to power it down until I just pulled the battery. I re-loaded one of my backups from another ROM and everything appears to be back as it was and I've not experienced the same issue at this point. Can't say 100% it was this ROM but thought it better to at least note it.
Click to expand...
Click to collapse
Hmmm...That is a very strange issue indeed! Did you install a custom kernel? Were you running any Xposed Modules? Would you be willing to try this ROM again and report if it happens again? Thanks!
Sent from my Galaxy Note II using XDA Free mobile app
I did not install an alternate kernel- usually I find it pays to stick with the one that came with any ROM I install. AGNi kernel always seemed to give me one problem or another. But I digress. I might try to install again to see if I can replicate but it was a little disconcerting as it looked like it was opening apps and displaying data I had entered - almost like some sort of bot. Don't keep much on the phone of a personal nature and it is no longer a work phone since I retired this summer - mostly a toy of sorts so I just try the various ROMs out there.
Won't get to it tonight but i'll let you know when I re-install.
Sent from my Surface Pro 3 using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
Sorry - didn't answer your other question. I did install Xposed installer. Only active module I used was Gravity and changed the battery icon and lockscreen background. I also have Greenify and Wanam Kit active but did not actually use either one to modify anything.
Sent from my Surface Pro 3 using Tapatalk
chameo53 said:
I did not install an alternate kernel- usually I find it pays to stick with the one that came with any ROM I install. AGNi kernel always seemed to give me one problem or another. But I digress. I might try to install again to see if I can replicate but it was a little disconcerting as it looked like it was opening apps and displaying data I had entered - almost like some sort of bot. Don't keep much on the phone of a personal nature and it is no longer a work phone since I retired this summer - mostly a toy of sorts so I just try the various ROMs out there.
Won't get to it tonight but i'll let you know when I re-install.
Sent from my Surface Pro 3 using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
Sorry - didn't answer your other question. I did install Xposed installer. Only active module I used was Gravity and changed the battery icon and lockscreen background. I also have Greenify and Wanam Kit active but did not actually use either one to modify anything.
Sent from my Surface Pro 3 using Tapatalk
Click to expand...
Click to collapse
Well, on my honor, I did not put a bot into this. I'm running the same build I posted and have not had that issue.
Sent from my Galaxy Note II using XDA Free mobile app
Really didn't mean to imply or suggest you did - I was more amazed on what I experienced and was hoping maybe someone else might have some explanation. I think I have installed every Note II ROM that has been out there since I got the phone 2 years ago so I'm not shy in regards to flashing new ones. I appreciate the effort all you developers put into this so again no blame intended.
Sent from my Surface Pro 3 using Tapatalk
chameo53 said:
Really didn't mean to imply or suggest you did - I was more amazed on what I experienced and was hoping maybe someone else might have some explanation. I think I have installed every Note II ROM that has been out there since I got the phone 2 years ago so I'm not shy in regards to flashing new ones. I appreciate the effort all you developers put into this so again no blame intended.
Sent from my Surface Pro 3 using Tapatalk
Click to expand...
Click to collapse
Don't worry about it! I didn't mean to come off as so defensive, I was simply trying to stamp out anymore thoughts of there being a bot.
Has anyone else experienced this issue?
Sent from my Galaxy Note II using XDA Free mobile app
Thanks for adding me to the thanks list. I really appreciate it. Will try out soon. Thanks for this.
Reflashed ROM - No repeat
I did reinstall the ROM last night since I wanted to try to replicate the overall process I followed and I wanted it to sit overnight. I got thru this afternoon without the same problem occurring. I did not activate the Xposed framework so none of the modules were active either. Other than that I re-installed basically all the apps I had installed the initial flash. All went well although I did have the SMS "unable to send issue" happen (it seems to happen every so often after I reflash a new ROM - doesn't seem to be ROM specific) so I ended up following the usual process as outlined by DreamFX and restoring a different ROM. I have consistently found the Unofficial Aokp ROM by apophis9283 to be the most stable ROM for me - I'll try yours again when the next release is out there.
DreamFX said:
Thanks for adding me to the thanks list. I really appreciate it. Will try out soon. Thanks for this.
Click to expand...
Click to collapse
No thank you man! Let me know how it goes!
Sent from my Galaxy Note II using XDA Free mobile app
chameo53 said:
I did reinstall the ROM last night since I wanted to try to replicate the overall process I followed and I wanted it to sit overnight. I got thru this afternoon without the same problem occurring. I did not activate the Xposed framework so none of the modules were active either. Other than that I re-installed basically all the apps I had installed the initial flash. All went well although I did have the SMS "unable to send issue" happen (it seems to happen every so often after I reflash a new ROM - doesn't seem to be ROM specific) so I ended up following the usual process as outlined by DreamFX and restoring a different ROM. I have consistently found the Unofficial Aokp ROM by apophis9283 to be the most stable ROM for me - I'll try yours again when the next release is out there.
Click to expand...
Click to collapse
While testing a few builds I realized the fix for the texting issue wasn't permanent, but it is fixable again. Thank you for trying out this ROM again!
Once Paranoid Android's gerrit is back up (I'm getting 404 errors for everything. :/) I'll cherry pick a few of the new PA features and have a new build up!
Sent from my Galaxy Note II using XDA Free mobile app
This ROM is great. I really like it. Running smooth and fast. So far no problems at all.
Although I'm still on cyanogenmod, it's good to see there's continued development on our device. Great job Dev
rippedwarrior69 said:
This ROM is great. I really like it. Running smooth and fast. So far no problems at all.
Click to expand...
Click to collapse
Glad to hear it! Thanks for trying this out!
Update: There seems to be an issue with the latest build of Google Chrome (v39) where the app will always start in floating mode. To return to full screen Chrome, clear app data after updating from the Play Store and every time you open Chrome pull up the Recents Menu (default is long press home button) and select Chrome again. It will now be full screen. This seems to be an issue for all of AOSPA.
Sent from my Galaxy Note II using XDA Free mobile app
twitish said:
Glad to hear it! Thanks for trying this out!
Update: There seems to be an issue with the latest build of Google Chrome (v39) where the app will always start in floating mode. To return to full screen Chrome, clear app data after updating from the Play Store and every time you open Chrome pull up the Recents Menu (default is long press home button) and select Chrome again. It will now be full screen. This seems to be an issue for all of AOSPA.
Sent from my Galaxy Note II using XDA Free mobile app
Click to expand...
Click to collapse
I'm on Carbon rom until I try yours this weekend. Of course it does this for me and is annoying as hell. It appears to have something to do with all kitkat aosp roms compabilty. My brother is lucky enough to have lollipop and it's not doing this on lollipop.
---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------
I'm really hoping this rom doesn't have that ok Google crackle that plagues most aosp roms for our device.
DreamFX said:
I'm on Carbon rom until I try yours this weekend. Of course it does this for me and is annoying as hell. It appears to have something to do with all kitkat aosp roms compabilty. My brother is lucky enough to have lollipop and it's not doing this on lollipop.
---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------
I'm really hoping this rom doesn't have that ok Google crackle that plagues most aosp roms for our device.
Click to expand...
Click to collapse
Unfortunately the Google Now activate tone does "crackle" on this ROM, however when it talks or makes any other sounds it's clear.
Sent from my Galaxy Note II using XDA Free mobile app
twitish said:
Unfortunately the Google Now activate tone does "crackle" on this ROM, however when it talks or makes any other sounds it's clear.
Sent from my Galaxy Note II using XDA Free mobile app
Click to expand...
Click to collapse
Darn that stinks. Thank for confirming.
I am going to try this ROM out. I will let you know if I have any issues. Thank you for giving is another choice.
Thanks for bringing this up for us, very exciting.
I know this is just getting started, the top features I am hoping to see are:
Quiet hours
Profiles
Long press back button to kill
1px battery bar
swipe between notifications/quick settings
Just my wish list for the cherry picks, but everything seems smooth so far!
Cyanogenmod 12.0 Semi-Official
HTC Evo 4G LTE ( jewel )
Basic Overview
Source built Cyanogenmod 12.0 hot off the server. No changes at all to anything. Sync and build.
This has not been officially released as of yet. Still very early code, there will be random bugs, and missing features still. They are coming.
Please refrain from reporting bugs because of this. Thank you.
Besides that It seems good enough for a "Daily Driver". No major malfunctions, just the random glitches as the code evolves as normal.
Requirements:
S-Off, HBOOT 2.10+ & 4.13.651.4 Firmware Update to function correctly. @Captain_Throwback's TWRP 2.7.1.0b , 2.8.0.x, 2.8.1.x recoveries recommended.
NPL recovery though. That's the only catch here.
Installation...
Wipe, reboot recovery.
Install CM-12.0, reboot.
One it finishes booting, reboot to recovery.
Install gapps, wipe dalvik & cache, reboot.
Profit
ROM Source: https://github.com/CyanogenMod/android/tree/cm-12.0
Original Kernel Source: https://github.com/CyanogenMod/android_kernel_htc_msm8960/tree/cm-12.0
Bugs...
Superuser settings cause Settings to FC currently. But remains functional.
Previous Release:
https://www.androidfilehost.com/?fid=95832962473395998
Current Release:
https://www.androidfilehost.com/?fid=95832962473397836
Current Release Gapps:
https://www.androidfilehost.com/?fid=95832962473397837
Partner Builds & Sub-projects
Partner Builds:
11-29-2014 Build: https://www.androidfilehost.com/?fid=95832962473394878 by @fizbanrapper
And it begins...
First Android 5.0 ROM for Jewel that works... And based off of one of the best Android 4.4.4 ROMs there was for Jewel as well. Enjoy everyone. Much more to come.
Cool. Sounds good. I may give it a try, just to say that I have 5.0. But I would like to have the camera working... But it is probably something that I can live with.
I've tried a flash, for the first time I experienced stuck in the boot, after I restarted again and then succeed, what becomes of bugs on camera?I have tried to take a picture with my camera and it worked fine, but I want to report that when opening the case of mobile networks in settings force close , thanks for dev , sorry for my bad english
ermariio said:
I've tried a flash, for the first time I experienced stuck in the boot, after I restarted again and then succeed, what becomes of bugs on camera?I have tried to take a picture with my camera and it worked fine, but I want to report that when opening the case of mobile networks in settings force close , thanks for dev , sorry for my bad english
Click to expand...
Click to collapse
First off, great work beating me to the punch on this. I was tinkering with CM 12 code all month.
Secondly, I can repeat what was said previously. I got a bootloop the first time, but after I turned it off, it booted up fine.
ocarinaz64 said:
First off, great work beating me to the punch on this. I was tinkering with CM 12 code all month.
Secondly, I can repeat what was said previously. I got a bootloop the first time, but after I turned it off, it booted up fine.
Click to expand...
Click to collapse
same here but it is running great so far
Ok. Camera bugs. I don't know. I just cut what lines out the compiler broke because of. And I have no cam. Idk why. My mobile network seems fine.. But come on guys. This is early code, so there's going to be bugs I have no control over. That would be more CMs thing. I just am basically doing what LSX64 did. No boot loop for me either. Weird...
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
jarheadusmc67 said:
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
Click to expand...
Click to collapse
Ok. No worries. I didn't either. So when I got it to even fire up.. I knew what I had to do. 5.0 for everyone, and making it a UnityROM, just a bonus
Does LTE work?
Psycario said:
Does LTE work?
Click to expand...
Click to collapse
I have no idea. I think so.. I have no LTE where I live
jarheadusmc67 said:
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
Click to expand...
Click to collapse
I can say that as long as I've got my Jewel, and as long as the code works, I'll be cranking things out. I'm really partial to Slim series ROMs, but I was super eager to try out L so I flashed this one. Also, it looks like CM is going to continue to support this thing for the foreseeable future. Once they start their nightly builds, it should be available there, too. Though, without the extra butter.
Thanks for the work and the build.
ocarinaz64 said:
I can say that as long as I've got my Jewel, and as long as the code works, I'll be cranking things out. I'm really partial to Slim series ROMs, but I was super eager to try out L so I flashed this one. Also, it looks like CM is going to continue to support this thing for the foreseeable future. Once they start their nightly builds, it should be available there, too. Though, without the extra butter.
Thanks for the work and the build.
Click to expand...
Click to collapse
No problems there man I know you do your thing. But.. Do you happen to know how to do that dark ui button
ZX64 said:
Ok. Camera bugs. I don't know. I just cut what lines out the compiler broke because of. And I have no cam. Idk why. My mobile network seems fine.. But come on guys. This is early code, so there's going to be bugs I have no control over. That would be more CMs thing. I just am basically doing what LSX64 did. No boot loop for me either. Weird...
Click to expand...
Click to collapse
Well done! Glad to have you back!
This is working surprisingly well for a first build. The first KitKat builds were total garbage, comparatively.
I'm using it as a daily driver for now. The latest Beta SuperSU will get you properly rooted on LP too. I'll post the link when a bit later (have to find it again), but Google will get you there for now.
Issues (none of which are controllable by the OP) and fixes
Issue one - keyboard doesn't always pop up like it's supposed to. So far I've been able to fix it every time by simply turning my phone sideways, then back.
Issue two - Sometimes not all choices are viewable in pop up boxes. I was able to get around this by changing screen density to 280.
Issue 3 - APN menu doesn't do anything of value. To change apn settings, download sql editor. Open telephony.db which is located at data/data/android.providers.telephony/databases. Then locate the 310120 lines and edit the values as you normally would for your carrier. Your phone will now use the desired APN settings.
Is it possible to turn off your modem like it was in 4.4? I don't see any option for that anywhere. The reason being is that I don't like my phone downloading things when I don't tell it to. It wastes my data, and gets annoying.
ocarinaz64 said:
Is it possible to turn off your modem like it was in 4.4? I don't see any option for that anywhere. The reason being is that I don't like my phone downloading things when I don't tell it to. It wastes my data, and gets annoying.
Click to expand...
Click to collapse
Does this help?
http://forum.xda-developers.com/showthread.php?p=56866237
fizbanrapper said:
Does this help?
http://forum.xda-developers.com/showthread.php?p=56866237
Click to expand...
Click to collapse
Theoretically that is what I was looking for. But now that I'm testing my phone, I realized that I'm not able to actually make or receive calls. Idk if that was because of the widget or what. It might also be a carrier problem.
EDIT - It was a carrier problem, but caused by what, I can't say.
fizbanrapper said:
Well done! Glad to have you back!
This is working surprisingly well for a first build. The first KitKat builds were total garbage, comparatively.
I'm using it as a daily driver for now. The latest Beta SuperSU will get you properly rooted on LP too. I'll post the link when a bit later (have to find it again), but Google will get you there for now.
Issues (none of which are controllable by the OP) and fixes
Issue one - keyboard doesn't always pop up like it's supposed to. So far I've been able to fix it every time by simply turning my phone sideways, then back.
Issue two - Sometimes not all choices are viewable in pop up boxes. I was able to get around this by changing screen density to 280.
Issue 3 - APN menu doesn't do anything of value. To change apn settings, download sql editor. Open telephony.db which is located at data/data/android.providers.telephony/databases. Then locate the 310120 lines and edit the values as you normally would for your carrier. Your phone will now use the desired APN settings.
Click to expand...
Click to collapse
Yeah kk was garbage for the first few months even. So LP way better so far in that way. Glad to have me back? I was here before?
Ok so next build I'll set to 280 and see about that. I have no idea on the KB lol I just used google KB cause it has a dark ui option.
But properly rooted... Big must have there. That I want fixed lol.
I have tried this rom full day, very nice, I just restart sometimes problematic when there is no data connection and GPS is not accurate,
I am creating this thread simply to avoid confusion with ##W4TCHOUT##'s Official ROM thread. Note that these are unofficial builds, and I am only posting these because I occasionally find the free time to make a build before ##W4TCHOUT## does. I am rather new to this stuff and still learning, but I will always make sure to run my builds and try to point out any bugs I can find in them before posting them. That said, it is probably still a good idea to go flash the official version when he gets the chance to build them, as he is much more experienced.
For information about ResurrectionRemix ROM, please see his thread here. Rather than copy pasting everything, I will simply post the specifics about my builds.
ROM
GAPPS
CHANGELOG
-- Installing --
Download latest build
Download GApps (pick any 5.1 on the link above, I used the minimal edition)
Get the latest TWRP
TAKE A NANDROID
Flash ROM (see instructions below)
Flash GApps
Reboot
Profit
Flashing Instructions
Due to a current bug in CM12.1, if you are doing the standard procedure of flashing CM11, booting once, and then flashing CM12.1, you will get a constant force close on com.android.phone, and it's a lot easier to fix in recovery than once you're booted up, hence the deletion instruction below. Even still, the bug is causing minor issues. Hopefully it will be resolved in the next couple days. I have not tried a dirty flash, but if anyone does, please report on whether or not it worked. Supposedly people have been dirty flashing CM12.1 over CM12.0 so theoretically it should work.
Wipe data, cache, dalvik cache
Flash the latest CM11
Boot once into CM11 (you don't need to go through the setup)
Reboot to recovery
Using either ADB or TWRP's terminal, delete the file /data/data/com.android.providers.telephony/databases/telephony.db so the system will recreate it at bootup
Example command from your terminal while phone is in recovery: adb shell rm /data/data/com.android.providers.telephony/databases/telephony.db
Flash this ROM
Flash GApps
Wipe cache/davlik cache
Reboot
My Additions
App was compiled with SaberMod 4.8 androideabi toolchain
Kernel was compiled with SaberMod 4.9 armeabi toolchain with -O3 and graphite optimization flags
Known Issues
Your signal bars may disappear after a couple reboots. Service still works, it just doesn't show it graphically. (I might have a workaround for this soon)
MMS does not appear to be working.
Ambient display does not appear to be working
The camera app only works sometimes and when it does it takes almost 30 seconds to load. You can try Open Camera on the play store, but it wasn't that much better in my case.
If you find others, please report them.
Big thanks to everyone that has helped me on XDA, this is a great community for learning and I'm excited to improve my skills at this!
Reserved #1
Reserved #2
Reserved .
According to a just now angry girlfriend, incoming voice calls might not be working...
Adding to known issues
Means can we hold for now flashing this rom... as incoming calls are not working.....
as I just uncovered and posted in a few other CM12 ROM threads, regarding ambient display, try toggling the pick up or camera twist under settings -> gestures. this worked for me on another ROM.
I'll have a buddy give me some test calls later today. It wouldn't be the first time she complained about non existent problems it's also possible she may have been referring to Skype, which I had yet to reinstall.
maroof.saeed said:
Means can we hold for now flashing this rom... as incoming calls are not working.....
Click to expand...
Click to collapse
Nvm the incoming call thing. pretty sure she either used skype or i did something locally. I've tested it fairly thoroughly today and all the calls came through.
I installed this and calls are working fine.
Just to verify, are other people experiencing the empty signal bars as well (after a reboot or two anyway)? I'm experiencing it on an XT1053 on T-Mobile. I feel like I'm on the verge of figuring it out... It has something to do with the contacts provider and the telephony provider. There are a few databases that if I wipe out, then the signal bars will come back, but seem to inevitably disappear again later. The closest thing I've found to a pattern of them disappearing has to do with MMS...
The db files that I wipe out are:
/data/data/com.android.providers.contacts/databases/contacts2.db
/data/data/com.android.providers.contacts/databases/profile.db
/data/data/com.android.providers.telephony/databases/mmssms.db
/data/data/com.android.providers.telephony/databases/telephony.db
The first one will end up wiping out your contacts, but you can just sync them back up with your google account after
The third one will end up wiping all your sms. And sometimes the third and/or fourth will turn off "mobile networks" in your settings.
I'll keep trying to dig... I'm also going to try and figure out how to get the initial deletion into the updater script so it'll happen automatically when people flash the ROM.
On a side note, I've done a new build with a few upstream commits from CM12.1, though they don't seem to have made any difference with the known issues. I also compiled the ROM with the SaberMod androideabi 4.9 toolchain instead of 4.8. I won't bother posting a new build though until at least one of the known issues gets solved or a new version of RR comes out
MikeyNick said:
Just to verify, are other people experiencing the empty signal bars as well (after a reboot or two anyway)?
Click to expand...
Click to collapse
I've rebooted a number of times and my bars have not blanked out. I don't use the stock sms/mms I delete it after first boot and only use hangouts
5.3.8
I don´t understand why you don´t continue de dev of 5.3....
Far I know, your rom cm.RR 5.3.8 is the only one where ambient display work correctly. (I tried all, even the offitial 5.3.9, ambient display doen´t works)
czuppa said:
I don´t understand why you don´t continue de dev of 5.3....
Far I know, your rom cm.RR 5.3.8 is the only one where ambient display work correctly. (I tried all, even the offitial 5.3.9, ambient display doen´t works)
Click to expand...
Click to collapse
ambient display works in all LP ROMs - you may need to go to settings -> gestures and toggle pick up off/on and/or camera twist.
jco23 said:
ambient display works in all LP ROMs - you may need to go to settings -> gestures and toggle pick up off/on and/or camera twist.
Click to expand...
Click to collapse
Yes, if you go into the gestures settings and toggle those then Ambient Display will work again.
SBF''d 4.4.4. did a clean install. Got bootlooped. Re-SBF'd again. flashed CM11 them CM12 . Took a while to boot but eventually she did. I have signal bars and am having the camera issue inherit to 12.1 (i'll check again later to see if it straightens itself out) . Ambient display works. BUT I have no dialer. Let me restate that. I have a dallier to call out on, but no in-call dialer, hence I can't check my voice mail or call any self automated services where you have to press numbers ofr the next menu., such as a bank.
Anyone else having this issue? Any ideas how to fix?
Verizon xt1060 DE
Edit: After further experimentation it appears I get the blank "no dialer" when I pull down the drop down notifications and dial to Vmail that way. I do get the dialer if I place the call manually. very strange. Still, must mess around some more, it seems to be random on some things.
Also, dev's, where can I find the left/right space arrow keys found in nav bar when keyboard is up like in previous RR ROMS? Did I miss it or is it not there yet? Thanks!
kerryh420 said:
SBF''d 4.4.4. did a clean install. Got bootlooped. Re-SBF'd again. flashed CM11 them CM12 . Took a while to boot but eventually she did. I have signal bars and am having the camera issue inherit to 12.1 (i'll check again later to see if it straightens itself out) . Ambient display works. BUT I have no dialer. Let me restate that. I have a dallier to call out on, but no in-call dialer, hence I can't check my voice mail or call any self automated services where you have to press numbers ofr the next menu., such as a bank.
Anyone else having this issue? Any ideas how to fix?
Verizon xt1060 DE
Edit: After further experimentation it appears I get the blank "no dialer" when I pull down the drop down notifications and dial to Vmail that way. I do get the dialer if I place the call manually. very strange. Still, must mess around some more, it seems to be random on some things.
Also, dev's, where can I find the left/right space arrow keys found in nav bar when keyboard is up like in previous RR ROMS? Did I miss it or is it not there yet? Thanks!
Click to expand...
Click to collapse
I've seen that dialer issue as well. I might run a new build tonight when I go to bed. CM has rebased on 5.1.0_r5, and there have been a few upstream commits, although not a new version of RR, but hopefully some things have been sorted out. I would have built it earlier but I took the day off to play GTA V (PC version) :laugh:
New version is up. it's still 5.4.1 but it's got a newer date, 0416
Changes:
Pulled all upstream CM commits, including it now being based off 5.1.0_r5 instead of r3
Compiled ROM with sabermod 4.8 because 4.9 toolchain is mysteriously gone now...
Things I noticed:
Signal bars appear to be fixed
Camera appears to be fixed
MMS still broken
Still need to delete telephony.db if coming from CM11
I had issues with play store until I did a clean flash, this might not be the case for everyone
MikeyNick said:
New version is up. it's still 5.4.1 but it's got a newer date, 0416
Changes:
Pulled all upstream CM commits, including it now being based off 5.1.0_r5 instead of r3
Compiled ROM with sabermod 4.8 because 4.9 toolchain is mysteriously gone now...
Things I noticed:
Signal bars appear to be fixed
Camera appears to be fixed
MMS still broken
Still need to delete telephony.db if coming from CM11
I had issues with play store until I did a clean flash, this might not be the case for everyone
Click to expand...
Click to collapse
Downloading right now??
I'm actually very happy with this last build. The twist to camera and active display are both working great, which are the only two features I cared that much about from stock ROM. I don't really use MMS that often, so as long as the battery life holds up, I think I finally built a good stock replacement
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
Notes: CyanogenMod's stock kernel forces encryption. If you're unencrypted use a custom kernel to keep it.
Also this thread assumes you have kept up to date bootloader and radio !!!
The latest can be downloaded here Shamu Factory images around 1gb!. But i recommand you to flash through TWRP the Bootloader and Radio from here Radio and Bootloader around 60mb.
Installation is simple
1/Download rom + gapps (C-apps optional)
2/flash through recovery (Twrp or CM recovery)
3/Enjoy!!!
----->CyanogenMod Download<-----
----->Open GApps<-----
last--CM13--nightlylast--CM12.1--nightly
Changelog
CyanogenApps
Twrp
Sources: Kernel & Rom
XDA:DevDB Information
[ROM] CyanogenMod14.1 {Nightlies and Snapshots} & Cm13, ROM for the Nexus 6
Contributors
Dead-neM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Up to date firmware (Fastboot+Radio)
Version Information
Status: Nightly
Current Stable Version: Everymonth
Current Beta Version: Everyday
Created 2016-04-22
Last Updated 2016-11-21
Reserved
Q&A
hum yes post your problem here after some research and you'll be helped
...
Reserved
Do not declare a bug here in the idea that they'll be fixed. Here we discuss, share everything related to our CM N6
so this is where we post from now on?
wmfreak said:
so this is where we post from now on?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using Tapatalk
Yay! Best ROM IMHO.
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
caballon said:
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
Click to expand...
Click to collapse
Sure, CM13 has been compatible since at least the beginning of this year
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Has the Sprint LTE issue been fixed by CM yet? IIRC the issue is once the Nexus 6 (running CM13 of course) drops down to 3G, it will never go back to LTE.
@cyrildtm
Going to have to bite the bullet and clean flash then.
Lawlrus said:
@cyrildtm
Going to have to bite the bullet and clean flash then.
Click to expand...
Click to collapse
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Snap camera in this version yet?
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Yeah, I mean I clean flash everything but I know everyone is different.
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Yeah, is the sprint LTE issue fixed?
Sent from my Nexus 6 using XDA-Developers mobile app
cyrildtm said:
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Click to expand...
Click to collapse
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Btw a clean flash doesn't mean to restore data of a previous rom lol
Lawlrus said:
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Click to expand...
Click to collapse
I agree with you. Nightlies sometimes can be awesome but sometimes awful. I went to look at the github page for the dialer app and found they recently put quite a lot of commits so maybe one or two is breaking things but anyways those smart people will figure it out sooner or later. I will just wait and take another free software
I bumped up from a March nightly mainly because of a recent CVE patch (of course that went into the 0401 build mod). Other than that I don't really see any urgent reason for increasing the counters in my daily driver again.
Dead-neM said:
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
Click to expand...
Click to collapse
I'm now on MOB30D radio (34R shown in settings, didn't copy down the version number shown in bootloader, but it did increase after flashing) and I can always make a phone call even now with an older nightly. so I can confirm the radio is working. I also noticed after flashing and first boot, when CM is about to finish "optimizing apps" the system gets a hot reboot (restart from animation) - oh btw another long-time bug is i never get themed boot animation unless i make a hot reboot (by FCing or any other way). Anyone same here?
From what I can remember the Dialer app has been a failure to me for more than a week. They did make a NPE fix there but seemed no help. Maybe I should install the Google's dialer as you do. I can still remember the AOSP English keyboard endless crash :silly: when I was on CM12.1 with an older device
Dead-neM said:
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Click to expand...
Click to collapse
One of the hard lessons I have learned.
Lawlrus said:
Yeah, I mean I clean flash everything but I know everyone is different.
Click to expand...
Click to collapse
Dead-neM said:
Btw a clean flash doesn't mean to restore data of a previous rom lol
Click to expand...
Click to collapse
Oh lol it never means that! A clean "flash" is no more than 90 seconds to me but a clean "install" means recovering a whole shelf of over a hundred apps from .... the play store .... no the auto re-install only works if i got the same android id
Custom Kernel
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
skim7x said:
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
Click to expand...
Click to collapse
Try this one https://www.androidfilehost.com/?fid=24499762636000737
This is the latest singularity kernel
Also on post 2 I've post 2 kernel Blackbird and Singularity which in my opinion are the best
I don't like elementalx and Franco but I'm open mind and I'll add link if you find an other good kernel