CyanogenMod 10.2 UNOFFICIAL for LG Optimus L9 p769This is unofficial build. Use at your own risk. I am not responsible for anything that may happen to your phone.
Only for P769 version of the phone. Do not attempt to flash on any other device.
The phone bootloader has to be unlocked and correct recovery installed.
Please avoid discussing general unlocking, rooting, and other unrelated to development issues in this thread.
Watch for bugs. Report with logcat and dmesg.
Features
- Continuation of the CM 10.1 ROM
- No emulated internal storage. Single external SD card configuration (read note in this post)
- Apps 2 SD support
- Support for Notification Lights, either native or with BLN (read note in this post)
- Analog amplifier gain control with Voodoo Sound support (read note in this post)
- Microphone preamplifier gain adjustments
- Performance kernel with OC/UV
- Advanced Settings to control kernel clocks
Kernel
- Compiled with Linaro 4.7
- Extended frequency table with 200MHz, 1200MHz, 1350MHz (overclocking doesn't work on some phones)
- Slightly undervolted
- Userspace voltage control. Use SetCPU, VoltageControl, or similar. Warning: Save a recovery script with either of these programs before playing with voltages!
- GPU is extended with 384MHz, IVA with 430 MHz
- Selectable screen-off maximum frequency
- Included SmartassV2 governor, SIO scheduler.
- Few performance tweaks.
Bugs
- No 1080p in camcorder
Installation
- If going from non-CM10.* ROM, backup your data and do full reset. If updating from CM10.* it is usually not necessary.
- Copy to SD and flash with CWM.
- Flash correct version of Gapps
Download
cm-10.2-20140430-UNOFFICIAL-p769.zip (Mega)
cm-10.2-20140430-UNOFFICIAL-p769.zip (Dropbox)
Sources
Github
History
Upstream merges
04/30/2014
cm-10.2-20140203-UNOFFICIAL-p769.zip
- Repo synced
02/03/2014
- Repo synced, CM10.2.1+
01/20/2014
cm-10.2-20140120-UNOFFICIAL-p769.zip
- Repo synced
11/26/2013
cm-10.2-20131126-UNOFFICIAL-p769.zip
- Repo synced, CM10.2 RC1
11/15/2013
cm-10.2-20131115-UNOFFICIAL-p769.zip
- Repo synced, CM10.2 M1
10/28/2013
cm-10.2-20131028-UNOFFICIAL-p769.zip
- Repo synced
10/18/2013
cm-10.2-20131018-UNOFFICIAL-p769.zip
- Reduced call microphone volumes even more
10/04/2013
cm-10.2-20131004-UNOFFICIAL-p769.zip
- Reduced call microphone volumes
- Repo sync
09/27/2013
cm-10.2-20130927-UNOFFICIAL-p769.zip
- Repo sync
- minor tweaks
09/20/2013
cm-10.2-20130920-UNOFFICIAL-p769.zip
- Repo sync
09/16/2013
cm-10.2-20130916-UNOFFICIAL-p769.zip
- Repo sync
09/09/2013
cm-10.2-20130909-UNOFFICIAL-p769.zip
- first build with CMAccount
09/06/2013
cm-10.2-20130906-UNOFFICIAL-p769.zip
- minor tweaks
08/30/2013
cm-10.2-20130830-UNOFFICIAL-p769.zip
- updated blobs to LGE v20f
- minor tweaks
08/26/2013
cm-10.2-20130826-UNOFFICIAL-p769.zip
- upstream merges, AOSP updated to JSS15Q, slow GPS lock is fixed
- removed disabling of touch lights from Parts app
08/23/2013
cm-10.2-20130823-UNOFFICIAL-p769.zip
- reduced Bluetooth in-call microphone volume
- adjusted power profile
- upstream picks and minor tweaks
08/20/2013
cm-10.2-20130820-UNOFFICIAL-p769.zip
- enabled auditing in kernel
- hwcomposer updated to use 1.0 interfaces
08/18/2013
cm-10.2-20130818-UNOFFICIAL-p769.zip
- device tree adopted to cm-10.2
- LgeL9Parts is now separate app
- added BLN timeout to kernel
- added BLN controls to Parts app
- ADB is run as root by default
- few tweaks
CM 10.1 history here
Notes
Notes from 10.1 still apply.
You will probably see some annoying notifications that cannot be removed no matter what you do. It's not a bug, it's a feature of Android 4.3. You can read about it here.
Extras
T-Mobile V20f radio: Mega, Dropbox. Flash with CWM.
TWRP 2.5.0.0 for p769: post
Here we go with CM 10.2.
It seems to be running fine so far, but it's the first build so anything can happen.
Persistent notifications in Android 4.3 suck.
No need to do anything special when updating from CM10.2, just flash with CWM on top.
Watch for Gapps, you need a different version now, link is provided in the OP.
CM10.2 does not support DeviceParts extension to settings anymore. I have converted the Advanced Settings into a separate Optimus L9 Settings app.
I extended the settings with some BLN options. Neldars's BLN app is not required anymore, you can just enable notification lights with L9 Settings. If you want scheduling you still need his paid app though.
I set ADB to run as root by default (ro.secure=0). Just got tired from switching to root all the time. If everybody thinks it's terrible idea let me know.
I will still do some updates to CM10.1, it's not dead yet, plus it maybe a little too early to jump to CM10.2.
Thanks for the rom! Notifications & the inability to record videos at 1080p are the only faults I see. :good:
Upgraded from AntonX's CM10.1 ROM, no data wipe just caches. Installed new gapps and it runs great. At first glance stock vibration intensity for haptic feedback seems a little less, no complaints just an observation. My only annoyance is that sometimes when hitting the home button to leave an app it takes me straight to the widgets screen. No big deal though, might just end up having to wipe data. Smooth ROM as usual though. Thanks for bringing 10.2 to the P769 AntonX!
Sent from my LG-P769 using xda app-developers app
ThrIsNoSpork said:
...stock vibration intensity for haptic feedback seems a little less, no complaints just an observation.
Click to expand...
Click to collapse
Settings->More... has adjustment for vibrator, it's new CM feature.
Massive merge today of Gallery fixes just after I had built. Well, it's expected, I'll just try to keep up and sync every few days.
Instaling now and Checking out.
Thank you so much for your efforts man, greatly appreciated. :good:
I can't find the Thanks button
But, thanks for all the work on this. I'll check it out when I get a chance.
Can we possibly get another mirror. The dropbox link is a dead end and I was having a hard time with mega.
Sent from my LG-P769 using Tapatalk 2
Juanito216 said:
Can we possibly get another mirror. The dropbox link is a dead end and I was having a hard time with mega.
Click to expand...
Click to collapse
Dropbox link was malformed, you can try it now.
cm10.2 already?
wow......
time to give this a try. thanks AntonX!
If @AntonX & @mateo1111 are okay with it here's another addition to our library of roms.
Sent from my LG-P769 running PACrom JB 4.3 using Tapatalk 2
I've got the stock android 4.3 launcher here of anybody else prefers it over trebuchet. Just install as a normal apk.
Alex Griffith shared "Launcher2.apk": https://skydrive.live.com/redir?resid=6E86634129081CAE!54407&authkey=!AG7osCpWj1OcqX0
Sent from my LG-P769 using xda app-developers app
OP updated
Repo synced today. Quite a bit of changes.
Enabled auditing in kernel to tame extensive error logging from auditd daemon. It's related to SELinux. I still haven't enabled it in the kernel, somehow don't want to do that.
GPS. Somehow I feel it locks a bit slower. It does lock in the end but not in very few seconds as it used to. I haven't touched anything related to it, but I have updated radio on my phone to L6260_MODEM_SIC_01.1305, so it's quite possible it has something to do with it. If you also notices slower GPS lock I wonder what radio are you running.
AntonX said:
OP updated
Repo synced today. Quite a bit of changes.
Enabled auditing in kernel to tame extensive error logging from auditd daemon. It's related to SELinux. I still haven't enabled it in the kernel, somehow don't want to do that.
GPS. Somehow I feel it locks a bit slower. It does lock in the end but not in very few seconds as it used to. I haven't touched anything related to it, but I have updated radio on my phone to L6260_MODEM_SIC_01.1305, so it's quite possible it has something to do with it. If you also notices slower GPS lock I wonder what radio are you running.
Click to expand...
Click to collapse
Please no selinux until it is more stable and widely used.
GPS is a lot slower for me. I'm on the v20d radio. Does it always take a minute for you? Maybe it was just slow the first time because it was downloading AGPS data
Edit: first fix took 1 minute 47 seconds. Next fix took only 17 seconds. It seems to vary a lot though, I did ten tests after the first and they vary from 17 seconds to 1 minute 30 seconds.
Sent from my LG-P769 using xda app-developers app
Had anyone else noticed audio completely crashing with V4A?
Sent from my LG-P769 running PACrom JB 4.3 using Tapatalk 2
pisherthefisher said:
GPS is a lot slower for me. I'm on the v20d radio. Does it always take a minute for you? Maybe it was just slow the first time because it was downloading AGPS data
Click to expand...
Click to collapse
First time after reflash it's probably possible to be slower. But I noticed that it takes about 10-20 seconds now to start hot instead of 5 or even under before. Nothing interesting in logs.
leolawliet said:
Had anyone else noticed audio completely crashing with V4A?
Click to expand...
Click to collapse
I don't even know what V4A is (OK, Googled it) Anything in logcat?
AntonX said:
First time after reflash it's probably possible to be slower. But I noticed that it takes about 10-20 seconds now to start hot instead of 5 or even under before. Nothing interesting in logs.
I don't even know what V4A is (OK, Googled it) Anything in logcat?
Click to expand...
Click to collapse
Please recommend a good logcat app
What to do? I've never worked with logcats before I feel like a noob
Sent from my LG-P769 running PACrom JB 4.3 using Tapatalk 2
I did a quick Google search and it looks like the slow GPS lock is a problem with 4.3 that Google has admitted: https://code.google.com/p/android/issues/detail?id=58459
Hello James,
Thank you for contacting Google Play Support Team. I understand your concern with your gps working on your device. I want you to know I am here to make sure to resolve any issues you may have with your device.
It is a know issue that Google is aware of and we are currently working on a update to fix the issue. I do apologize for the inconvenience this may cause.
Feel free to reply to this email and I will be able to further assist you.
Regards,
Osiguy
The Google Play Support Team
Click to expand...
Click to collapse
Sent from my LG-P769 using xda app-developers app
Related
Trickster MOD app is a tweaking tool to change various settings included in your kernel and other tweaks to your phone. It was made by me and my friend.
Screenshots and more information at links below.
Links
Google Play Store
AndroidPIT
Donate
WebsiteIf you like the app please rate it 5 stars and if you can, please donate.
Feature requests
Please post & vote features on our feedback site. So we can keep track of them
Bug Report
Please read the FAQ at our website before reporting any problem
If the FAQ does not help, use the Bug Report feature in our app & reference your ID here (the number in the mail subject).
Credits:
- Google
- Our great kernel devs
- grilledbacon for your beautiful icon
- Beta testers and translators for your contributions
- Anyone that helped us in some way
Disclaimer: This is provided with NO GUARANTY whatsoever. Use your common sense.
Initial version has been pushed to Google Play https://plus.google.com/u/0/116709542966452959662/posts/NZBEEJcuY5d, still pretty basic ATM moment. More stuffs will be added in later versions.
Thanks for adding support for the Nexus 10!
New version uploaded to market, should be available to you shortly
https://plus.google.com/u/0/116709542966452959662/posts/796By1dhjso
New version has been uploaded to Play Store, more info https://plus.google.com/116709542966452959662/posts/KDqLwP8gMH7
I had backed up my stock kernel using trickster mod, then flashed franco.kernel r-4. I confirmed everything on my phone was working properly, then paid for the donate version of the app so I could restore my stock kernel back to my nexus 10 4.2.1. All was well until I started using my device,
- OTG support was intermittent and my applications were running abnormally slow.
- Most of the folders that had write privileges could not be written to anymore when I tried making a new TWRP backup and ended up corrupting some of my existing application backups (combination of program not being able to write properly and OTG fading in and out).
I had to go into TWRP and restore from a nandroid after the fact and run Titanium to restore all my apps - OTG and worked fine after that. Any ideas, or a possible fix? I'd like to get the most out of the restore kernel function of the app.
bigdog2k7 said:
I had backed up my stock kernel using trickster mod, then flashed franco.kernel r-4. I confirmed everything on my phone was working properly, then paid for the donate version of the app so I could restore my stock kernel back to my nexus 10 4.2.1. All was well until I started using my device,
- OTG support was intermittent and my applications were running abnormally slow.
- Most of the folders that had write privileges could not be written to anymore when I tried making a new TWRP backup and ended up corrupting some of my existing application backups (combination of program not being able to write properly and OTG fading in and out).
I had to go into TWRP and restore from a nandroid after the fact and run Titanium to restore all my apps - OTG and worked fine after that. Any ideas, or a possible fix? I'd like to get the most out of the restore kernel function of the app.
Click to expand...
Click to collapse
Hi there,
The code to do the backup/restore couldn't possibility do that (e.g. it does not contain anything to change permissions). As I don't have the device, previous tests were done by my testers and I had positive results, so I will ask them to check again. For now, can you provide more information:
- ROM: I guess stocks?
- busybox: which app did you use to install it? busybox version?
- If possible do a new nandroid backup and do two bug report (Trickster MOD menu): once before you do a new backup and another when you restore kernel so I can check if there's anything goes wrong. Also send me the list of contents in /sdcard/kernel_backups
bigeyes0x0 said:
Hi there,
The code to do the backup/restore couldn't possibility do that (e.g. it does not contain anything to change permissions). As I don't have the device, previous tests were done by my testers and I had positive results, so I will ask them to check again. For now, can you provide more information:
- ROM: I guess stocks?
- busybox: which app did you use to install it? busybox version?
- If possible do a new nandroid backup and do two bug report (Trickster MOD menu): once before you do a new backup and another when you restore kernel so I can check if there's anything goes wrong. Also send me the list of contents in /sdcard/kernel_backups
Click to expand...
Click to collapse
Thanks for the quick response! I can do that later today. Yes, Rom is stock Jellybean rooted 4.2.1, busybox was installed using the stericson tool from the play store. Ill pm you later with extra info.
heya, loving the app. got one question if anyone can answer. does anyone have a list of kernels that support s2w? I'm using kmanta but it doesn't show CPU temp.
also on a side not, where would the options show up if its able?
edit: stock kernel from paranoid android for n10 and franco kernel doesnt show temperature either
Big eyes, I'm running trickster for the first time on the gnex and have a question. If I change the max freq from 1700 to 1600 and hit save. Then exit and go back in, its back to 1700. I then tried the freq lock option and that seems to work and it stays at 1600.
What's odd, is on the main screen (device status, core 0/1) it only goes to 1000mhz max. In realtime I mean....if I put my finger on the screen and move around it gets to 1000 but nothing higher. I'm wondering maybe if locking it down by checking that option basically locked it down to 1000 rather than 1600?
Confused..... Any thoughts? Thanks, great app
chugger93 said:
Big eyes, I'm running trickster for the first time on the gnex and have a question. If I change the max freq from 1700 to 1600 and hit save. Then exit and go back in, its back to 1700. I then tried the freq lock option and that seems to work and it stays at 1600.
What's odd, is on the main screen (device status, core 0/1) it only goes to 1000mhz max. In realtime I mean....if I put my finger on the screen and move around it gets to 1000 but nothing higher. I'm wondering maybe if locking it down by checking that option basically locked it down to 1000 rather than 1600?
Confused..... Any thoughts? Thanks, great app
Click to expand...
Click to collapse
Kernel/ROM issue. The app always reads frequency settings from the kernel itself so if it's at something then it's there, if a setting doesn't stick then something else changes it, and if the frequency does not go to the max that is because the set governor and its correspondent tunables, as in load is not high enough for the governor to set it to max.
bigeyes0x0 said:
Kernel/ROM issue. The app always reads frequency settings from the kernel itself so if it's at something then it's there, if a setting doesn't stick then something else changes it, and if the frequency does not go to the max that is because the set governor and its correspondent tunables, as in load is not high enough for the governor to set it to max.
Click to expand...
Click to collapse
Fair enough...I appreciate the quick response. It's Franco's latest R8, so I'm guessing its his kernel. Dam.... good to know. Maybe time to go back to stock kernel on Sentinel ROM...wonder if I can change the freq's in that kernel
chugger93 said:
Fair enough...I appreciate the quick response. It's Franco's latest R8, so I'm guessing its his kernel. Dam.... good to know. Maybe time to go back to stock kernel on Sentinel ROM...wonder if I can change the freq's in that kernel
Click to expand...
Click to collapse
You might wanna read our FAQ as it contains some information of what inside a JB device that might change the set frequencies. This should be patched in the kernel or worked around in the ramdisk. I coded for the N10 without a device so it's hard for me to say more. As for the frequency doesn't go to max, it's likely because of the load as I told you. Touching the screen is a relatively light load so it might not go to max frequency at all. That's normal.
Sounds good...last question, how do u reset the CPU spy like stats? Sorry if this is already covered in the faq
chugger93 said:
Big eyes, I'm running trickster for the first time on the gnex and have a question. If I change the max freq from 1700 to 1600 and hit save. Then exit and go back in, its back to 1700. I then tried the freq lock option and that seems to work and it stays at 1600.
What's odd, is on the main screen (device status, core 0/1) it only goes to 1000mhz max. In realtime I mean....if I put my finger on the screen and move around it gets to 1000 but nothing higher. I'm wondering maybe if locking it down by checking that option basically locked it down to 1000 rather than 1600?
Confused..... Any thoughts? Thanks, great app
Click to expand...
Click to collapse
You can't change the max clock freg because you need a kernel with a patched PowerHAL, which Franco doesn't have.
It only goes to 1000mhz because this is how the interactive governor is tuned. If you put it under increased load it will eventually increase. If you go into the governor parameters on trickster for interactive you will see "hispeed_freq" will most likely be set to 1000000 (1GHZ), which means the CPU will jump to this immediately. You can play around with these parameters for battery/performance but Franco and a few testers tune them significantly, although his N10 kernel is very young compared to his N4 and N7 kernels where the settings have been tuned to a tee, and I think the N10 settings might have just been copied over as a reliable base.
We're going to close individual device thread to consolidate our app thread into one at http://forum.xda-developers.com/showthread.php?p=28659480 , please go there if you need to discuss anything related to our app.
Thread Closed as per OP....
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
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
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
Evervolv is back
Here you can find latest Oreo Builds
http://evervolv.com/devices/tenderloin
New builds every day ?
Ok,
Download is ok
http://evervolv.com/get/ev_tenderloin-8.1.0-nightly-2018.08.26.zip
korporalkarotte said:
Evervolv is back
Click to expand...
Click to collapse
I noticed. Anyone know what’s going on?
Well, the logs for all the Tenderloin builds have no commits - the intriguing thing is looking at Gerrit and seeing all the Android P commits going on. None that I saw for Tenderloin, but a lot of work being done on P.... I know Flintman has said he had P booting on Tenderloin elsewhere - so who knows what's up, but it seems something is baking!
Just like to know if is there similar with durty-unicorns ?
Any way to root this build??
A_Pac1 said:
Any way to root this build??
Click to expand...
Click to collapse
Yup
Excellent news
Is there any reason to have a new update on a daily basis?
I guess it is automatic.
You can click on log to see the changes :
"2018.09.25..2018.09.26
No new commits found."
Steelskinz said:
I guess it is automatic.
You can click on log to see the changes :
"2018.09.25..2018.09.26
No new commits found."
Click to expand...
Click to collapse
I saw that; However, I didn't test it though, to have an opinion about it.
Steelskinz said:
I guess it is automatic.
You can click on log to see the changes :
"2018.09.25..2018.09.26
No new commits found."
Click to expand...
Click to collapse
It's just a bot. It mindlessly pumps out builds of the entire ROM, not just the tenderloin (HP) device.. It may or may not have commits in other parts of the ROM.
shumash said:
It's just a bot. It mindlessly pumps out builds of the entire ROM, not just the tenderloin (HP) device.. It may or may not have commits in other parts of the ROM.
Click to expand...
Click to collapse
I installed the ROM from 9-26-2018 and it does have changes to it. Now you can see the external USB partition when connected to a PC, it did not worked before. It may be a bot but the new commits are been apply and fixing bugs. The most important is that new commits are uploaded, then the bot will regenerate the new build. If anyone working on the TP ROM have access or that can upload the commits, this ROM will be very close to perfection by now. Is a shame is not been taking care of properly as we get new builds very fast! ( Even the camera partially works, you can see yourself when opening the app, it may need a very small tweak! )
There is even work been done for p-9.0 or at least files that are updated!
https://github.com/Evervolv/android_device_hp_tenderloin-common/tree/p-9.0
I'm having an issue with 10/6 build. If the tablet sleeps for more than a couple minutes, I need to force a reboot by holding the home button and power buttons. It will drain the battery quickly while in this state.
Ideas?
The Evervolv oreo 8.1 builts are not stable, the issue that you are experiencing is one of the bugs.
Another one is activating battery saver and deactivating will reboot.
Use DU built, is stable.
https://cdn.dirtyunicorns.com/api/download/tenderloin/Rc/du_tenderloin-v12.5.1-20180920-1118-RC.zip
greetings and thanks for so much effort and desire are excellent really appreciate and recognize their work
---------- Post added at 11:07 PM ---------- Previous post was at 11:00 PM ----------
https://github.com/Evervolv/android_device_hp_tenderloin-common/tree/p-9.0
http://evervolv.com/devices/tenderloin
HP_TOUCHPAD said:
The Evervolv oreo 8.1 builts are not stable, the issue that you are experiencing is one of the bugs.
Another one is activating battery saver and deactivating will reboot.
Use DU built, is stable.
https://cdn.dirtyunicorns.com/api/download/tenderloin/Rc/du_tenderloin-v12.5.1-20180920-1118-RC.zip
Click to expand...
Click to collapse
The DU build lags badly on my device. The Evervolv nightly from November 1st seems very snappy by comparison. Haven't tested it much but first impression is that I haven't found a ROM this responsive for the TouchPad in quite a long time...
crabnebula said:
The DU build lags badly on my device. The Evervolv nightly from November 1st seems very snappy by comparison. Haven't tested it much but first impression is that I haven't found a ROM this responsive for the TouchPad in quite a long time...
Click to expand...
Click to collapse
What makes a ROM faster is the Kernel and the CPU speed plus governor settings.
One setting does not work for every user as everyone uses the tablet differently.
Yes the last Evervolv is a good one. But also DU works great if you do not need to use the camera.
You can make the tablet faster by using the overclock kernel and change the CPU settings to your likes.
HP_TOUCHPAD said:
What makes a ROM faster is the Kernel and the CPU speed plus governor settings.
One setting does not work for every user as everyone uses the tablet differently.
Yes the last Evervolv is a good one. But also DU works great if you do not need to use the camera.
You can make the tablet faster by using the overclock kernel and change the CPU settings to your likes.
Click to expand...
Click to collapse
I do not need the camera, but all ROMS I've tried past KitKat suffer from bad slowdowns, where everything appears to regularly freeze for several seconds, scrolling in web pages is very jerky, etc. Overclocking helps a little, but not much. I unfortunately experienced the same behaviour with DU 12.5, even after a full wipe.
crabnebula said:
I do not need the camera, but all ROMS I've tried past KitKat suffer from bad slowdowns, where everything appears to regularly freeze for several seconds, scrolling in web pages is very jerky, etc. Overclocking helps a little, but not much. I unfortunately experienced the same behaviour with DU 12.5, even after a full wipe.
Click to expand...
Click to collapse
Unfortunately not all touchpads were build the same and there are variation on their parts, the most important CPU . That is the reason that an optimized setting can not be apply to all, because it will make some unusable.
That does not mean that the one with the worse quality parts can not perform well, all of them can with the right settings and it takes just some basic testing that the user must do and apply its own settings, there is only one that matters:
Find the lowest and maximum CPU frequency: Get the Overclock Kernel and an app that will allow to change the frequency, there are a lot out there.
Change the lowest it will work and the maximum by selecting one by one, if once selected it freeze or reboots then it will be the previous frequency:
In general this is the basic for maximum frequency:
All should perform at the maximum 1782000
Better: 1836000
Best: 1890000
At those higher frequency there could be some reboots depends on the settings:
All should be stable at when overclok 1782000.
Now comes the trick settings:
Some Kernel app will allow to apply settings to each cpu core individually.
Set the cpu0 to highest 1782000 and select Governor to Performance ( it will run constantly at that speed)
Set the cpu1 to lower anywhere from 1674000-1512000
Also select your minimum on both 192000 - 384000
Now change the voltage: Maximum to be stable 1400000 (it can be apply in increment until it reach the maximum to the 1782000 frequency.
Set the zRAM size to 2gb size ( maximum )
That is all!
Now the browser is important, use the latest version as of right now, some are faster than others, try them all!
All ROMS should be able to perform decent and give you great performance.
In the latest DU, using Opera or Firefox you can browse the web even go to youtube website and use it as if it was the native google app, no delays fast playing no lag ( all depends on your internet speed )