[ROM][2014-12-23] CM12 unofficial ALPHA for ATT HTC ONE M8 - AT&T HTC One (M8)

This is my first attempt at compiling cyanogenmod for my own phone. So far it works OK for me so I decided to share:
WARNING:
As of 20141223 you will need HBOOT version 3.19.000 to be able to use this. in order to get it install the latest firmware from: http://forum.xda-developers.com/showthread.php?t=2696282
WARNING:
This is an ALPHA built, in other words too many things are broken and expect things to suddenly stop working. Make sure you know how to recover your phone in case anything breaks. If you have a grain of doubt that you may not be able to recover DO NOT PROCEED. and in the end of everything: I do not take any responsibility for anything that may or may not happen to your phone. You are flashing at your own risk not mine.
Requirements:
1. Custom recovery (I used TWRP)
2. Latest firmware version 3.19.000
Files that you need:
CM12 built: http://devbro.com/android/cm-12-20141223-UNOFFICIAL-m8.zip Last stable built with no issues for camera and bluetooth is 20141218
GAPPS: http://d-h.st/YQG
SUPERSU: http://download.chainfire.eu/supersu -- no longer needed
Steps:
0. Create a small temple using your favorite objects and pray to your favorite God or Gods for a successful outcome. I did about 2 hours of praying to Eutykhia. I suggest the same to you.
1. Back up your stuff using Titanium backup
2. Go into recovery
2.1 Do one last nandroid backup here of System, Boot, Recovery and Data
3. Wipe Data, System, Cache, Dalvik
4. install CM12 and GAPPS
5. restart upon completion
Things that do not work:
1. Titanium back up and apps that depend on root may hang. Flash SUPERSU from RECOVERY and it should fix it. Fixed as of 20141220
2. Camera does not work.
3. Bluetooth may not see new devices. Restart before adding each individual device.
4. If Calendar is not syncing install the Google Calendar from the Store
5. Apollo(music player) Keeps on crashing. I used Play Music(google music) to play my musics and it works ok so far. fixed as of 2014-12-06 build. Apollo no longer exists but a new music app that works just fine with nuplayer
6. Probably other stuff that I have not come across yet.
7. I have not been able to get the swype gesture on the keyboard. If you know why please tell us.
If you have suggestions:
Simply post it in the forum and I see What I can do about it. If there are
My mods to this code:
1. I had edited the platform.xml to allow write access to sdcard (aka sdfix)
Screenshots:
{
"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"
}

Looks like you may have fixed more than Apollo in that last build. Camera, calender, and multiple bluetooth pairing worked out-of-the-box. Runs good. Only crash I've encounter so far is in trying to access the in-built Superuser settings, but it's redundant if you use the SuperSU app anyway.
Good job!

ugoff said:
Looks like you may have fixed more than Apollo in that last build. Camera, calender, and multiple bluetooth pairing worked out-of-the-box. Runs good. Only crash I've encounter so far is in trying to access the in-built Superuser settings, but it's redundant if you use the SuperSU app anyway.
Good job!
Click to expand...
Click to collapse
For the 2014-12-06 build I got a few more of the drm blobs. Still missing two blobs thought.

Hey, First - Thank You for this ROM it's a great start !
I have been using it since you released it and I just wanted to give my two cents. For being an Alpha build, mostly everything works. I have noticed few bugs but the most annoying one for me is when I'm playing music. 1) I would use Play Music and at first it worked fine but as of today, for some reason, it would play for the first 10 seconds and than it would go off. The music ticker would be increasing but the sound would not play. I would have to skip ahead a track than go back to have it play fully. 2) I also rooted and flashed the ROM on to my coworkers phone and for some reason, his mobile Data wouldn't work yet Wi-Fi works perfectly fine. 3) Something else that I noticed was that, when closing apps, more often than not, after hitting the "close all" tap, I would open the recent apps again and I would have a application running which was closed. 4) I would also get a FC when trying to change the settings in the Messenger app. It's not that important but I thought that I should mention it anyway.
That's all I have at the moment, Thank You again for your hard work.

SirrJonathan said:
Hey, First - Thank You for this ROM it's a great start !
I have been using it since you released it and I just wanted to give my two cents. For being an Alpha build, mostly everything works. I have noticed few bugs but the most annoying one for me is when I'm playing music. 1) I would use Play Music and at first it worked fine but as of today, for some reason, it would play for the first 10 seconds and than it would go off. The music ticker would be increasing but the sound would not play. I would have to skip ahead a track than go back to have it play fully. 2) I also rooted and flashed the ROM on to my coworkers phone and for some reason, his mobile Data wouldn't work yet Wi-Fi works perfectly fine. 3) Something else that I noticed was that, when closing apps, more often than not, after hitting the "close all" tap, I would open the recent apps again and I would have a application running which was closed. 4) I would also get a FC when trying to change the settings in the Messenger app. It's not that important but I thought that I should mention it anyway.
That's all I have at the moment, Thank You again for your hard work.
Click to expand...
Click to collapse
Thank you so much for the info I will update the thread with these bugs. Here are a few things:
1. for the music player problem go to settings->development options->switch the music option from "nuplayer" to "awesome player"
2. I have no encountered this problem. did you check the APN settings and made sure that network data is enabled?
3. I do sometimes run into this problem
4. Are you using the default messenger app? I use textra which is very similar in look and feel and so far no breakage.
I have been trying to compile a new version but for the past 2 days the latest code off the branch keeps of failing the build at different points. If I get to fix the errors I will try again to upload a new build.

devbro said:
Thank you so much for the info I will update the thread with these bugs. Here are a few things:
1. for the music player problem go to settings->development options->switch the music option from "nuplayer" to "awesome player"
2. I have no encountered this problem. did you check the APN settings and made sure that network data is enabled?
3. I do sometimes run into this problem
4. Are you using the default messenger app? I use textra which is very similar in look and feel and so far no breakage.
I have been trying to compile a new version but for the past 2 days the latest code off the branch keeps of failing the build at different points. If I get to fix the errors I will try again to upload a new build.
Click to expand...
Click to collapse
OK so,
1) I had it checked on and now I unchecked it, I will use it as normal and proceed with an update.
2) I'll be honest, he was being an annoyance so I did not check his APN though you are probably right.
3) I am using the stock messenger app. I had the Google application on here but I was receiving and "message not sent" error for some odd reason.
PS: That was a fast reply, good stuff. :good:

Just an update on the Music bug, I unchecked the box as before and after nearly a 24 hour testing period, I have encountered the bug a few times but not a much as before. I would say that I would have to apply the walk around (Changing the track and than going back to what I actually want to listen too) around five times. That is way less than before, so it did address the bug but it did not kill it.

SirrJonathan said:
Just an update on the Music bug, I unchecked the box as before and after nearly a 24 hour testing period, I have encountered the bug a few times but not a much as before. I would say that I would have to apply the walk around (Changing the track and than going back to what I actually want to listen too) around five times. That is way less than before, so it did address the bug but it did not kill it.
Click to expand...
Click to collapse
Have you tried other other music players such as play music? I want to know if the bug is exclusive to Apollo or not.
I did have the problem at the beginning and simply seeking the music it helped. I have not encounter that problem for sometime. Plus I have been using a bluetooth headphones so that may have something to do with my case.

devbro said:
Have you tried other other music players such as play music? I want to know if the bug is exclusive to Apollo or not.
I did have the problem at the beginning and simply seeking the music it helped. I have not encounter that problem for sometime. Plus I have been using a bluetooth headphones so that may have something to do with my case.
Click to expand...
Click to collapse
I have used Apollo and Play music. Play music is the main one used. On another note, my mobile data also broke just know. I am not sure why so i had to revert to my backed up ROM

Works great so far. Only issue I am getting g is that the screen won't turn off during call. The audio issue happened once and it worked later don't know why. My cars bluetooth works and controls audio but won't get the text messenges. Besides that feels great for being alpha. No crashes so far.

I finally managed to build the source code again. I hope you all like this one.

devbro said:
I finally managed to build the source code again. I hope you all like this one.
Click to expand...
Click to collapse
404 not found

joker96 said:
404 not found
Click to expand...
Click to collapse
Looks like he left out a 1:
http://devbro.com/android/cm-12-20141215-UNOFFICIAL-m8.zip
devbro said:
I finally managed to build the source code again. I hope you all like this one.
Click to expand...
Click to collapse
Where did the flashlight toggle go?

joker96 said:
404 not found
Click to expand...
Click to collapse
I fixed the link. I intentionally killed the linked as the build was not able to boot. I replaced the boot.img with an older one and now it works just fine.

devbro said:
I fixed the link. I intentionally killed the linked as the build was not able to boot. I replaced the boot.img with an older one and now it works just fine.
Click to expand...
Click to collapse
Camera/flashlight are not working. The camera apps are crashing and the flashlight apps I've tried are not detecting an LED light.

ugoff said:
Camera/flashlight are not working. The camera apps are crashing and the flashlight apps I've tried are not detecting an LED light.
Click to expand...
Click to collapse
I uploaded a new built of for today so please re-download the file. The old file had a problem and I intentionally made the link 404 to prevent others from downloading the bad file.
As for Camera app problem it is a known issue with but using the google camera instead of the stock camera should fix this issue.
As for Flash-light app, I used it from the quick setting and it worked just fine for me.

devbro said:
I uploaded a new built of for today so please re-download the file. The old file had a problem and I intentionally made the link 404 to prevent others from downloading the bad file.
As for Camera app problem it is a known issue with but using the google camera instead of the stock camera should fix this issue.
As for Flash-light app, I used it from the quick setting and it worked just fine for me.
Click to expand...
Click to collapse
I'll try re-downloading. With the build I got, not even the Google camera was working.
*Update: That did it. Works great now.

Just a quick update for those using this. I have created a new built for 20141223 but so far i cannot get it to flash on my phone. Something to do with incompatibility between recovery versions. If i get to fix it i will post further updates.
Sent from my One M8 using XDA Free mobile app

Are you only using the CWM recovery? I've flashed the last 2 versions of this with TWRP. Care to put up a link?
devbro said:
Just a quick update for those using this. I have created a new built for 20141223 but so far i cannot get it to flash on my phone. Something to do with incompatibility between recovery versions. If i get to fix it i will post further updates.
Sent from my One M8 using XDA Free mobile app
Click to expand...
Click to collapse

I also use twrp if you want i will put a link and you can try at your own risk.
Sent from my One M8 using XDA Free mobile app

Related

[Q] Q&A CM11

Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

[ROM][4.4.4][UNOFFICIAL]AOSPA Legacy 4.6 [BETA 6][11/19/2014]

{
"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!

[ROM] dOPE-PSOA 4.4.4-A HYBRID WITH PURE AOSP-Multi-Themed-SuperFAST&SMOOTH4SAFESTRAP

[ROM] dOPE-PSOA 4.4.4-A HYBRID WITH PURE AOSP-Multi-Themed-SuperFAST&SMOOTH4SAFESTRAP
gogolie/gigilie presents:
dOPE - PSOA v1,2&3
for Safestrap Users on Verizon
Features:
Pure AOSP 4.4.4 Dialer and Contacts - Themed by gogolie
The Most Minimalistic ROM for VZW S4
A Ton of Tweaks
A Lot more I don't have time to write them all out! Will update OP soon!!
To install download the ROM and Open Safestrap.
Create a new ROM Slot and Install the .zip
Still working on Aroma Version so install is automatic.
If your not on NC2 or NC5 Firmware You May have to flash Modules in order to get the WiFi etc to work!
Downloads:
dOPE-PSOA - BurntGrass v3 - The BareBonez Version - Super Dark and Inverted Backgrounds
dOPE-PSOA DarkMeat v3 - The BareBonez Version - With Darkened AOSP & Gray Backgrounds
dOPE-PSOA DarkMeat v2 - The Regular Version - With Darkened AOSP & Gray Backgrounds and Google Apps and Files to Theme Like AndroidL!
Screenshots:
{
"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"
}
More Screenshots
Other Thanks and Credits: @Joe-Tech for his themed MMS and Calculator! @reggiecheeks for some elements from his previous themes!
Thanks GUYS!
Older Versions:
PSOA Stock Beta V1
Has a few bugs and known issues with Signal Bars displaying and 2 FCs at the beginning that dont affect the ROM a new better Stock Themed AOSP version is in the works
GREAT!! Downloading it now. Many thanks for the efforts.
Been meaning to try the new HyperDrive, but just hate TW so much. Eclipse is giving me problems so I was going to go back to HyperDrive, but I'll give this a shot first. So sick of my phone lagging...... didn't do it on GPE, but I had problems with GPS on that..... As well as no Google Wallet......
Gig, before I download this. Can you install this on the stock slot?
Sent from my GT-N5110 using XDA Premium HD app
taz1458 said:
Gig, before I download this. Can you install this on the stock slot?
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
id imagine yes no problem but I havent tried. no reason you shouldnt be able too tho.
Got it installed, but gmail will not open. Keeps saying unknown google play services error.
EDIT: guess whatever it ways woke up. Gmail finally synced. No options for any themes or anything?
It's snappy, I'll say that. I am having a wifi issue. It was working before, not sure if it was working before I installed Xposed (hadn't looked) but it's not working now. Won't turn on. I tried the NC5 ones again, which had been working. No dice it seems. Overall, getting like 200mb free more on boot compared to using a TW rom. I mean that's awesome, but I need to have WIFI =[
Edit: GMail refuses to sync, that was happening from the get-go, just hasn't started working. Just had a reboot while reading a text also.....
taz1458 said:
Gig, before I download this. Can you install this on the stock slot?
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
All 3 versions worked fine on SLot 1 and Stock for me.
I did have a few issues trying to get WiFi working but other than that it seems to be working well.
Only bug I've found so far, is the fact that the copy paste option, after you copy something and long press to paste, the word does not come up anywhere and you cannot paste anything.
Edit: been running darkmeat 2, and it will not remember wifi after a reboot. Have to manually reconnect everytime. I can honestly say, this thing is ridiculously fast!
LGtMgG2t said:
All 3 versions worked fine on SLot 1 and Stock for me.
I did have a few issues trying to get WiFi working but other than that it seems to be working well.
Click to expand...
Click to collapse
How exactly did you get Wifi fixed? I've tried a few different gogolie fixes and so far nothing!
@liv3dn8as
It was more difficult than most ROMs for some reason. I think I ended up using wififix-VZW-NG6-w-modules-modem-w-hlos-SS.zip but had to flash it a few times and do a couple fast boots/soft reboots after I got booted up. I definitely had the problem where WiFi is not saved after each reboot as mentioned above. I had to go connect and enter the password each time I booted.
@LGtMgG2t
Just got it working with that as well! Thanks for the reply. Glad to know it was the same fix! Now I can get back to fixing my original error, com.android.phone stops working. Thankfully it only happens when it first boots. I did just notice though that my SMS aren't sending sometimes. Not sure why yet! Time for a logcat!
liv3dn8as said:
@LGtMgG2t
Just got it working with that as well! Thanks for the reply. Glad to know it was the same fix! Now I can get back to fixing my original error, com.android.phone stops working. Thankfully it only happens when it first boots. I did just notice though that my SMS aren't sending sometimes. Not sure why yet! Time for a logcat!
Click to expand...
Click to collapse
I also get that phone force close at boot too. Usually happens twice. I believe it may be an AOSP issue though. I know on the GPE rom it was doing it as well.
taz1458 said:
I also get that phone force close at boot too. Usually happens twice. I believe it may be an AOSP issue though. I know on the GPE rom it was doing it as well.
Click to expand...
Click to collapse
Correct. The phone FC issues happens twice only on boot up near as I can tell. Doesnt seem to cause a problem and also happens in the BlackBox ROM twice on boot.
LGtMgG2t said:
Correct. The phone FC issues happens twice only on boot up near as I can tell. Doesnt seem to cause a problem and also happens in the BlackBox ROM twice on boot.
Click to expand...
Click to collapse
I cant tell you how many different options I tried to stop the FCs then I finally came up with a working non FC and had built this ROM up with a working aroma installer for multiple themes and tweaks and a ton of options then someone stole my laptop and my 2tb external hd when my roommate had a party... sucked I had to start all over again about a week ago. and was apparently too intoxicated to replicate that FC fix thus far... that version had a lollipop all white custom themed aosp 444 took me forever. thieves suck.
im not sure as to the wifi settings not saving I also noticed that only allowing unknown sources to install only works for a single package install.... glad to hear most of you got the wifi issues figured out by installing one of the generic fixes I made for anyone on NC firmware it should work on install.
the gmail issue might be due to a newer version available. if its an issue for anyone just delete it via the safestrap filebrowser and reinstall via playstore.
i'll keep working on the ROM and this aroma installer with themes and what not i have a hard time deciding what to put into it I had like 20 different options for dialer and contacts, mms, systemui and framework was coming up with some interesting themes probably giong to just do that again. i had the option to either use TW or AOSP too
thanks for the feedback guys!
gigilie said:
I cant tell you how many different options I tried to stop the FCs then I finally came up with a working non FC and had built this ROM up with a working aroma installer for multiple themes and tweaks and a ton of options then someone stole my laptop and my 2tb external hd when my roommate had a party... sucked I had to start all over again about a week ago. and was apparently too intoxicated to replicate that FC fix thus far... that version had a lollipop all white custom themed aosp 444 took me forever. thieves suck.
im not sure as to the wifi settings not saving I also noticed that only allowing unknown sources to install only works for a single package install.... glad to hear most of you got the wifi issues figured out by installing one of the generic fixes I made for anyone on NC firmware it should work on install.
the gmail issue might be due to a newer version available. if its an issue for anyone just delete it via the safestrap filebrowser and reinstall via playstore.
i'll keep working on the ROM and this aroma installer with themes and what not i have a hard time deciding what to put into it I had like 20 different options for dialer and contacts, mms, systemui and framework was coming up with some interesting themes probably giong to just do that again. i had the option to either use TW or AOSP too
thanks for the feedback guys!
Click to expand...
Click to collapse
Of note, I hacked the unknown sources before the first thing I installed, have installed a couple more and it hasn't asked me yet. I flashed the ng6 and nk1 (whatever the new one is) modules just to see if it made a difference saving wifi and it didn't. Love the quickness of this thing so far!
Just a thought, but have you guys tried Instabridge? It works great for saving wifi passwords. Well auto connect also. I know having a completely working room would be nice, but it could help those wanting this as a daily driver. I've been playing with empty galaxy myself. dOPE was faster, just couldn't rock it as a daily. ....
Sent from my GT-I9505 using XDA Premium HD app
Anyone else getting a boot loop with the PSOA-BB-DarkMeat-v3-gogolie ROM? I clean flashed on the stock slot. Guess I'll try v2 and see what happens and might need to download v3 again.
todd3835 said:
Just a thought, but have you guys tried Instabridge? It works great for saving wifi passwords. Well auto connect also. I know having a completely working room would be nice, but it could help those wanting this as a daily driver. I've been playing with empty galaxy myself. dOPE was faster, just couldn't rock it as a daily. ....
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Will try it today. Thanks
Sent from my GT-N5110 using XDA Premium HD app

[ROM][S5 Sprint/Boost/Sport]Un-Adulterated CM12 5.0.2

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

invisibleseek cm 14.1 rom for hp touchpad (tenderloin)

newer give up
here is a new rom from invisible
invisiblek.org/roms/cm-14.1/tenderloin/cm-14.1-20161125-UNOFFICIAL-tenderloin.zip[/url]
getting Google services stopped error
Sent from my HTC One_M8 using XDA Free mobile app
Which gapps version do you use? Where did you downloaded them?
download arm /gapps /nano from opengapps.org and no use even with cm14. 1 28/11/16, Android keyboard also error its closing always but i am using SwiftKey, rest everything is good
Sent from my HTC One_M8 using XDA Free mobile app
is the camera working
and what bugs are there in this rom
camera is not working
any one successfully gapps with working playstore?? i still can't open play store
Sent from my HTC One_M8 using XDA Free mobile app
Hi guys, I've just found my touchpad for the 1st time in years I'm currently on cm9.... Can I go straight from this to a nougat rom like cm14? Thanks for any info offered.
Sent from my SM-T800 using Tapatalk
gingerdude said:
Hi guys, I've just found my touchpad for the 1st time in years I'm currently on cm9.... Can I go straight from this to a nougat rom like cm14? Thanks for any info offered.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
The /system partition size is probably not enough. I believe cm14 needs at least 1.3GB.
tsoheq said:
The /system partition size is probably not enough. I believe cm14 needs at least 1.3GB.
Click to expand...
Click to collapse
Ah I suspected that might be the case, I'll look for a guide as I'm wayyyyy out of practice these days. If you know of a good guide I'd appreciate any help.
Regards steve
Sent from my SM-T800 using Tapatalk
gingerdude said:
Ah I suspected that might be the case, I'll look for a guide as I'm wayyyyy out of practice these days. If you know of a good guide I'd appreciate any help.
Regards steve
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2321397
Perfect. Thank you very much.
Sent from my SM-T800 using Tapatalk
Updated info
shumash said:
http://forum.xda-developers.com/showthread.php?t=2321397
Click to expand...
Click to collapse
Thanks Shumash I've updated the thread and links. I'm working on a dedicated android 7.x install thread, video in production now.
CM14.1 Note: You may need to install another keyboard app (here) if the AOSP one crashes at start
(New)How to install Android 7.x Nougat builds on the HP TouchPad
How to install Android 7.x Nougat builds on the HP TouchPad(new step by step guide)
Video about Flitmans excellent Rom here, Performance and battery drain info included
Timecode:
How to install 7.1 @ 2:34
Nougat 7.1 on my HP TP @ 5:08
How to enable super user @ 5:58
Antutu benchmark nougat vs Kitkat @ 7:48
Battery life nougat vs Kitkat @ 8:16
Link to Images
Browsing around this afternoon and saw this and was curious.
Link in first post doesn't seem to work so I followed the links in the CM13 thread to get to the CM14 images -=- HERE -=-
Might just give this a try for grins & giggles...
_Dan
CM14.1 info and links
middle_road said:
Browsing around this afternoon and saw this and was curious.
Link in first post doesn't seem to work so I followed the links in the CM13 thread to get to the CM14 images -=- HERE -=-
Might just give this a try for grins & giggles...
_Dan
Click to expand...
Click to collapse
Hey Dan here's some info and links I added to my guide. The rom itself has really great performance, battery stats and the 3D score is notably higher then Evervol 7.1.1. However I haven't been able to overcome issues with the play store force closing and AOSP keyboard crashing at start. Additionally sometimes when you flash the rom you get a blackscreen at boot but some builds worked fine. Let me know how it goes for you and if you have better results. I've tried both the open and base gapps packages with the same results.
[ROM][UNOFFICIAL][7.1] CyanogenMod 14.1 Unofficial (Invisiblek)
Rom Details: Low battery drain (-2mA to -15mA), h/w video, Audio, Camera(doesn't work), Bluetooth.
Note: This rom **REQUIRES a minimum of 1312MB System Partition. Change the size with Jcsullins TPtoolbox after selecting to install android
Note: You may need to install another keyboard app (here) if the AOSP one crashes at start
Note: May have issues with the Play store force closing.
{
"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"
}
I perhaps should have waited and thought this one through. - I didn't.
I don't think I wiped it properly. Not entirely sure. I think I did a 'sort-of' dirty flash of this over top of EV7.1.1
First boot was not pretty. Went back into recovery twice and did the wipe(s) then installed.
Came up OK, did have a couple of FC's. Just flashed OpenGApps Nano and am waiting for it to reboot.
I need to keep a better logbook, I think that I have all three of these 'testers' configured the same but that may not be the case.
So I might be heading back to 'GO' and firing up the ol' ToolBox.
EDIT: Might have to nickname it ForcedCloser... Can't setup and account. PlayStore FC'ing May have to start from scratch...
What is with all the "Default ######" accounts? and the one labeled 'Alice'?
I also got same problem ,fallow Roland ...the way he ask us to install ,u have to installstable version 1st Cm11. Then wipe system only to install.. see before Post he has given link
Sent from my HTC One_M8 using XDA Free mobile app
Night two: no joy, can't get in to play store or create account. Keeps FC'ing
Started off with clean install. 1.5GB
Loaded swiftkey, and that's working well. Grabbed a logcat, but can't upload here at xda-developers.com........
EDIT: (Evening_12-29)
Hardly functioning. Going to have to sideload apps or go with an alternative to Playstore.
Even the Email App is FC'ing.
I'm going to have to figure out what I am doing or did wrong.
EDIT II : (Later Same Evening)
Surrendering. Tried flashing 12-25 a short while ago, then rebooted into CM, then restarted into recovery to flash
OpenGApps Nano, rebooted. Fired up play store - FC. Went into: Settings, Add Account - FC...
Need an emoticon waving a white flag... I can't get it to go.
If someone who does have it running would post up a screenie of 'DF' under terminal, I'd appreciate it.
_Dan
Well, I thought I'd give it another try tonight.
Wipe everything - twice. Flashed the ROM - booted. It came up fine. No errors at all.
Rebooted back into TWRP and flashed GApps: "gapps-711-base-20161218-1-signed.zip"
Rebooted , 'Google Play Services have stopped' and the 'Keybd has Stopped' Errors
tried setting up a Google Acct, <FAILED> Stuck at "checking info" then returns a Play services error.
Tried going into Play Store, same result.
I've tried some many different GApps that I've lost track....
maybe need to figure out how to get rid of the 'Extra Accounts labeled "Default #####" ' ?
Seems quick and snappy. I don't think though that I feel like side-loading everything...
Well this has been a wasted afternoon... After trying different methods of trying to fork in different versions of Play Services and Play Store I gave up and did a clean install of 12-26. No GApps.
Keyboard is NOT crashing... (so far)
Then loaded Amazon App - Underground. Figured I'll just use those apps until...
er, nope. Amazon keeps stopping also... So much for that grand plan. Worth a shot.
Interestingly though, it crashes after selecting 'Sign In'... If you don't sign in it goes for just a couple of more screens, then crashes.
Just not yet ready for prime time - it's going to be something simple (hopefully)...
Harvested APKs from a couple of tablets and copied them over.
Been installing & trying them out for the last few hours while watching movies.
Most Apps stopping immediately. Swiftkey is working maybe 80% of the time before a close.
Root Explorer running at around 90%.
Loaded up a couple of older notepad type apps and they ran ok. Dolphin was a nogo.
AB Rio would go for a round then crash. First run the audio when bonkers.
Tried setting a custom wallpaper - finally got it.
Just isn't stable. Drat.
-----
Before I wipe it and take it back to EV7.1.1. I thought I would install Play Services and Store via ADB.
Didn't work. It reported that Play Services had Stopped as soon as it came up from reboot...
It did list a note in the pulldown that said that Play Services needed to be updated...
middle_road said:
Well this has been a wasted afternoon... After trying different methods of trying to fork in different versions of Play Services and Play Store I gave up and did a clean install of 12-26. No GApps.
Keyboard is NOT crashing... (so far)
Then loaded Amazon App - Underground. Figured I'll just use those apps until...
er, nope. Amazon keeps stopping also... So much for that grand plan. Worth a shot.
Interestingly though, it crashes after selecting 'Sign In'... If you don't sign in it goes for just a couple of more screens, then crashes.
Just not yet ready for prime time - it's going to be something simple (hopefully)...
Harvested APKs from a couple of tablets and copied them over.
Been installing & trying them out for the last few hours while watching movies.
Most Apps stopping immediately. Swiftkey is working maybe 80% of the time before a close.
Root Explorer running at around 90%.
Loaded up a couple of older notepad type apps and they ran ok. Dolphin was a nogo.
AB Rio would go for a round then crash. First run the audio when bonkers.
Tried setting a custom wallpaper - finally got it.
Just isn't stable. Drat.
-----
Before I wipe it and take it back to EV7.1.1. I thought I would install Play Services and Store via ADB.
Didn't work. It reported that Play Services had Stopped as soon as it came up from reboot...
It did list a note in the pulldown that said that Play Services needed to be updated...
Click to expand...
Click to collapse
middle_road said:
Well, I thought I'd give it another try tonight.
Wipe everything - twice. Flashed the ROM - booted. It came up fine. No errors at all.
Rebooted back into TWRP and flashed GApps: "gapps-711-base-20161218-1-signed.zip"
Rebooted , 'Google Play Services have stopped' and the 'Keybd has Stopped' Errors
tried setting up a Google Acct, <FAILED> Stuck at "checking info" then returns a Play services error.
Tried going into Play Store, same result.
I've tried some many different GApps that I've lost track....
maybe need to figure out how to get rid of the 'Extra Accounts labeled "Default #####" ' ?
Seems quick and snappy. I don't think though that I feel like side-loading everything...
Click to expand...
Click to collapse
Thanks for giving the Rom a thorough testing and reporting back with your results. I had the same issues and never got past the playstore problem, eventually I gave up. Its a shame CM14.1 came to an end before reaching its full potential on the HP TP.
Edit: If you're ready for a new adventure test out Invisiblek's Lineage OS rom here I've made a thread about it below and yes the play store is working
[ROM][UNOFFICIAL][7.1.1] Lineage OS [3.4 KERNEL](Invisiblek)

Categories

Resources