[Q] Are the CM11s bugs present on the CM11 Snapshots and Nightlies? - ONE Q&A, Help & Troubleshooting

Specifically, the bugs associated with encryption, e.g. compass not working properly, twrp backup unable to decrypt (fixed on 38R update). I don't want to go through the process of wiping and starting over again with CM11 snapshots if I don't have too. CM11s offers nothing to me that I can't get on CM11 snapshots. I'm just done waiting for the tremendous amount of bugs on CM11s!
Basically, I want all the funcationality back I had on my Nexus 4 running CM11 snapshots.... which was everything worked with the phone being encrypted!
Thanks.

I'd like to know as well. Is there anyone who can confirm this?
Thanks,

ndy4eva said:
I'd like to know as well. Is there anyone who can confirm this?
Thanks,
Click to expand...
Click to collapse
So I switched to CM11 snapshot. Kept the encryption through the process, so didn't do a full disk wipe, and the compass is still broken.
The last thing to try would be a full data wipe, disk format and reinstall everything from scratch to see if encrypting from CM11 snapshot keeps the compass working.
Sent from my A0001 using XDA Premium HD app

Not sure about the bug(s) BUT i have noticed a huge difference in benchmarking application scores between CM11 Nightlies and CM11s.
On CM11S my OPO scores 46954 (Version 5.1.5) and on the CM11 Nighlies only 41492 (Also version 5.1.5) - AnTuTu
Not sure how that translates into real world performance, but it was enough to persuad me to stick with CM11s

I made a fresh install of cm11 m11 and my compass is not functional. Decrypting from twrp works flawlessly though.

badaeng said:
I made a fresh install of cm11 m11 and my compass is not functional. Decrypting from twrp works flawlessly though.
Click to expand...
Click to collapse
Damn. The issues doesn't seem to be catching much traction through Jira either. For those that are security oriented like myself, this is a problem. I want my phone decryped and I want it to work properly. Granted, a compass doesn't take away the core functionality; however, it is quite annoying when trying to navigate somewhere.

badaeng said:
I made a fresh install of cm11 m11 and my compass is not functional. Decrypting from twrp works flawlessly though.
Click to expand...
Click to collapse
You encrypted after you installed CM11 M11 then?

stewa2jm said:
You encrypted after you installed CM11 M11 then?
Click to expand...
Click to collapse
Fresh install including data and sdcard wipe, encrypted by cm11 m10.
I did install m10 and not m11 as I wrote above. Just upgraded.

badaeng said:
Fresh install including data and sdcard wipe, encrypted by cm11 m10.
I did install m10 and not m11 as I wrote above. Just upgraded.
Click to expand...
Click to collapse
Thanks! Looks like it is a bigger issue than just between CM11 & CM11s.
I was hoping the snapshots didn't have that issue.
Sent from my A0001 using XDA Premium HD app

They have a lot less bugs, and if they do, they get fixes about a month before.

Related

[Q] Periodic Freezes/Crashes with Cyanogenmod 10.1.3

Has anyone had problems with the new Cyanogenmod 10.1.3 freezing and crashing periodically?
I did a brand new clean full reinstall (not an upgrade). Still have the problem.
Any thoughts on what might be causing this?
Thank you.
Windstorm1981 said:
Has anyone had problems with the new Cyanogenmod 10.1.3 freezing and crashing periodically?
I did a brand new clean full reinstall (not an upgrade). Still have the problem.
Any thoughts on what might be causing this?
Thank you.
Click to expand...
Click to collapse
Are you under-volting?
... and why not try CM 10.2?
Sent from my SCH-I535 using xda app-developers app
epagib said:
Are you under-volting?
... and why not try CM 10.2?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not familiar with volting. How do I know/check to see if I'm doing that?
I was running CM 10.2 and it was working. Suppose I could go back. I'd just prefer to stay at 10.3 if I can fix this. Reason is that I would want to do a clean install of 10.2 and that would require all the formatting, app set up etc. Don't want to load up from my nandoid since I simply installed updates from CM 10.1 up through 10.2 and things started to get corrupted.
Thanks.
Chances are you're not undervolting then. Custom kernels allow us to do that.
Sounds like you've been taking the nightly updates and after awhile the problem arise?
I'd try to clean cache, clean dalvik cache, and fix permissions. Then reboot.
Of that doesn't work, then would have to do a clean reinstall
epagib said:
Chances are you're not undervolting then. Custom kernels allow us to do that.
Sounds like you've been taking the nightly updates and after awhile the problem arise?
I'd try to clean cache, clean dalvik cache, and fix permissions. Then reboot.
Of that doesn't work, then would have to do a clean reinstall
Click to expand...
Click to collapse
No - haven't been taking the nightlies. Only the stable versions.
In installed CM 10.1.3 as a clean install twice - including cleaning the cache and the dalvik cache.
I actually saw another mention on the web about another GSIII user seeming to have the same problem.

CyanogenMod 11

Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk
It IS about time.
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.
robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.
orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)

Apps seem to be reset after cyanogenmod 13 update

I flashed cyanogenmod 13 and gapps for marshmallow (from 6.12.2015) and it boots fine. All apps are installed, as before the update.
BUT
When I start any of these apps they seem to be reset to default as if they are newly installed. For example Threema starts setup process after start.
App data is still present on internal storage (did not wipe), but apps do not seem to have access to any of this data.
Can anyone help what I can try to get the apps back to work with previous data?
Thankful for any help!
Greets
Daniel
At first, try flashing CM13 after a full wipe or try using another rom since CM13 could be buggy.
Primokorn said:
At first, try flashing CM13 after a full wipe or try using another rom since CM13 could be buggy.
Click to expand...
Click to collapse
Thanks for the reply! But well, the phone is working, just the apps are behaving as if they are newly installed ... So a full wipe would not really help as is only deletes more data. The question is why do the apps "think" they are not already set up?
d-trip said:
Thanks for the reply! But well, the phone is working, just the apps are behaving as if they are newly installed ... So a full wipe would not really help as is only deletes more data. The question is why do the apps "think" they are not already set up?
Click to expand...
Click to collapse
That's why we "always" backup user data before flashing a new rom
Primokorn said:
That's why we "always" backup user data before flashing a new rom
Click to expand...
Click to collapse
Full ACK, but data is still available on the internal storage, but the apps do not notice this?
AND this one here (not allowed ot post links... so a missing w at the beginning ww.cyanogenmod.org/blog/a-marshmallowy-cm) says dirty flash from 12.1 to 13 is okay and if the cyanogenmod updater shows cm13 as availabe for update ...
EDIT: Maybe this was a missing info, but it was "just" a normal update via cyanogenmod updater, not a real flash of a new rom!
d-trip said:
Full ACK, but data is still available on the internal storage, but the apps do not notice this?
AND this one here (not allowed ot post links... so a missing w at the beginning ww.cyanogenmod.org/blog/a-marshmallowy-cm) says dirty flash from 12.1 to 13 is okay and if the cyanogenmod updater shows cm13 as availabe for update ...
EDIT: Maybe this was a missing info, but it was "just" a normal update via cyanogenmod updater, not a real flash of a new rom!
Click to expand...
Click to collapse
What do you want me to say? It's always better to full wipe when upgrading to a new Android version. Period.
Moreover, CM13 nightlies are buggy. There are important bugs and fixes everyday. Make a nandroid backup and try from scratch or try another nightly or another custom rom. There's nothing else to say IMO.
Primokorn said:
What do you want me to say? It's always better to full wipe when upgrading to a new Android version. Period.
Moreover, CM13 nightlies are buggy. There are important bugs and fixes everyday. Make a nandroid backup and try from scratch or try another nightly or another custom rom. There's nothing else to say IMO.
Click to expand...
Click to collapse
Just thought it could be possibly just a permission problem, a missing symlink or anything else that could be fixed manually.
d-trip said:
Just thought it could be possibly just a permission problem, a missing symlink or anything else that could be fixed manually.
Click to expand...
Click to collapse
I flashed the first CM13 nighly and I didn't have to do anything to get working apps. Everything has been restored without any issue.

Insufficient storage error when installing certain apps

I followed the instructions given to me in my "new here" thread and was able to wipe my OS and install resurrection remix 7.1.2 last night. However, I was only able to install gapps mini and now I can't take a screenshot or install other items like google chrome or facebook. However, I was able to install other apps like firefox. I've tried a factory reset, removing my google account from the play store and re-adding it. It should definitely not be a cache problem as the install is brand new. I even used twrp wipe on all folders and reinstalled RR and still no change. Do I need to repartition or just try another mod?
*edit*
I found another thread here through a search that had a very similar issue to mine, but it looks like they were able to resolve theirs by uninstalling some app (they didn't say what). I'm having this with a fresh install, every time. So that fix didn't work for me, and I couldn't find anything else.
As an update to this issue, I have been able to install OkCupid (I'm a single girl, what can I say?) and the Android WebService that it required to function. Still have original issue though.
briannam said:
As an update to this issue, I have been able to install OkCupid (I'm a single girl, what can I say?) and the Android WebService that it required to function. Still have original issue though.
Click to expand...
Click to collapse
That's strange.Try Clean flashing the rom with opengapps.org .
Mr.Ak said:
That's strange.Try Clean flashing the rom with opengapps.org .
Click to expand...
Click to collapse
Yeah, I think it might be the resurrection remix mod. I think after I get off work tonight I'm going to try the newest CM13? mod listed here and see if that doesn't help
briannam said:
Yeah, I think it might be the resurrection remix mod. I think after I get off work tonight I'm going to try the newest CM13? mod listed here and see if that doesn't help
Click to expand...
Click to collapse
It ain't no mod.I'm taking about using open gapps instead of whatever gapps you were using before.
The mod I'm referring to is the resurrection remix which is the OS mod. I used the open gapps mini with that OS, so I've tried that.
briannam said:
The mod I'm referring to is the resurrection remix which is the OS mod. I used the open gapps mini with that OS, so I've tried that.
Click to expand...
Click to collapse
What does PS say when you try to install facebook,etc?
It just says downloading and never changes. I also don't get the notification in the status area indicating it's downloading. It doesn't ask for permissions either, I don't know is that's normal for a rooted phone or not
briannam said:
It just says downloading and never changes. I also don't get the notification in the status area indicating it's downloading. It doesn't ask for permissions either, I don't know is that's normal for a rooted phone or not
Click to expand...
Click to collapse
I'm rooted,and downloading works fine for me.Umm,try clearing data and cache of play services and play store?
Mr.Ak said:
I'm rooted,and downloading works fine for me.Umm,try clearing data and cache of play services and play store?
Click to expand...
Click to collapse
One of the first things I did yep. It's almost as if the system storage is somehow full or locked or something.
briannam said:
One of the first things I did yep. It's almost as if the system storage is somehow full or locked or something.
Click to expand...
Click to collapse
Try with flashing different gapps(bean,dynamic etc) then.
Mr.Ak said:
Try with flashing different gapps(bean,dynamic etc) then.
Click to expand...
Click to collapse
Well, here's why I don't think that's it. After flashing the OS, I tried to flash the super version of the open gapps. That was a huge file, almost a gig I think, so when that errored out I wasn't surprised. So when I tried the stock at 700 mb, and that failed, I tried the mini. That was 200 mb, and when that flashed successfully, I got suspicious. So I do think it's an issue with the system partition. I know the resurrection remix was a few GB in size, so perhaps it was too big. I haven't tried downloading CM13 or any others yet, so I don't know if there's a huge size difference or not. But I think that may be what it was. Just too big for our phones.
briannam said:
Well, here's why I don't think that's it. After flashing the OS, I tried to flash the super version of the open gapps. That was a huge file, almost a gig I think, so when that errored out I wasn't surprised. So when I tried the stock at 700 mb, and that failed, I tried the mini. That was 200 mb, and when that flashed successfully, I got suspicious. So I do think it's an issue with the system partition. I know the resurrection remix was a few GB in size, so perhaps it was too big. I haven't tried downloading CM13 or any others yet, so I don't know if there's a huge size difference or not. But I think that may be what it was. Just too big for our phones.
Click to expand...
Click to collapse
System partition has a size,just like internal storage has.Though,in the former case,you can increase it,but there's no point in increasing it,as you can just flash mini/nano/pico gapps and install all the other G-Apps you need after that.Infact,stock/heavy gapps is nothing but bloatware.
Anyway,what I meant was, flash other gapps except opengapps:
https://www.google.co.in/amp/s/foru...id/software/gapps-dynamic-gapps-t3487192/amp/
https://forum.xda-developers.com/android/general/gapps-gapps-7-0-nougat-minimal-t3474980
https://androidfilehost.com/?w=files&flid=124631
https://www.google.co.in/amp/s/foru...d-slim-gapps-6-0-7-0-unofficial-t3462088/amp/
https://plus.google.com/+DaanST/posts/ZMo18YATkc4
Okay,enuff spam for now.
Mr.Ak said:
System partition has a size,just like internal storage has.Though,in the former case,you can increase it,but there's no point in increasing it,as you can just flash mini/nano/pico gapps and install all the other G-Apps you need after that.Infact,stock/heavy gapps is nothing but bloatware.
Anyway,what I meant was, flash other gapps except opengapps:
https://www.google.co.in/amp/s/foru...id/software/gapps-dynamic-gapps-t3487192/amp/
https://forum.xda-developers.com/android/general/gapps-gapps-7-0-nougat-minimal-t3474980
https://androidfilehost.com/?w=files&flid=124631
https://www.google.co.in/amp/s/foru...d-slim-gapps-6-0-7-0-unofficial-t3462088/amp/
https://plus.google.com/+DaanST/posts/ZMo18YATkc4
Okay,enuff spam for now.
Click to expand...
Click to collapse
I think I just figured it out. I went outside on break and went to take a selfie to test the camera for this OS, and voila, it told me to enter an SD card. So it looks like it may be some sort of permissions issue. I'll just re-flash it with a different OS later. I'm not really attached to this one anyway. Brand new phone, nothing to back up.
briannam said:
I think I just figured it out. I went outside on break and went to take a selfie to test the camera for this OS, and voila, it told me to enter an SD card. So it looks like it may be some sort of permissions issue. I'll just re-flash it with a different OS later. I'm not really attached to this one anyway. Brand new phone, nothing to back up.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/official-dotos-v1-0-t3703159
Kthnxbye.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/development/official-dotos-v1-0-t3703159
Kthnxbye.
Click to expand...
Click to collapse
Looks good to me, I'll give it a shot tonight, thanks!
So, I flashed DotOS last night, everything is working. Looks like Resurrection Remix was the problem. Thanks again!
briannam said:
So, I flashed DotOS last night, everything is working. Looks like Resurrection Remix was the problem. Thanks again!
Click to expand...
Click to collapse
Feel free to drop by the thread when you run into any issues.

[ROM][4.4.4][Ovation][EMMC][UNOFFICIAL] SlimKat

Change-log:
2018-01-08: First release.
2018-01-10: Removed the camera app. Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180110-1016.zip
2018-01-23: Updated the SlimKat apps. Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180123-1611.zip
2018-02-08: Updated the SlimKat apps, removed Chromium apk, updated the security patch, and updated the webview stuff. Slim-ovation-4.4.4.build.9.15-UNOFFICIAL-20180208-0028.zip
XDA:DevDB Information
[ROM][4.4.4][Ovation][EMMC][UNOFFICIAL] SlimKat, ROM for the Barnes & Noble Nook HD, HD
Contributors
secretwolf98, SlimKat (for the latest sources)
Source Code: https://drive.google.com/drive/folders/1YkPtDKPvoVbU1CP3VjgRS0yNYR_c9EC-?usp=sharing
ROM OS Version: 4.4.x KitKat
Based On: SlimKat
Version Information
Status: Stable
Current Stable Version: SlimKat
Stable Release Date: 2018-02-08
Created 2018-01-09
Last Updated 2018-02-24
Glad to see you're working on the ovation version as well. I've upgraded from your 14.1 version to this one but I've been getting an error on the slimkat boot. I've used the twrp 3.1.1, factory reset, fresh install. The error was about data mounting. In the 14.1 I had both data and cache under the f2f system. When I installed back your 14.1 version, everything was back to normal, no errors. Do I need to format data and cache to ext4 for this slimkat version to work?
zspeciman said:
Glad to see you're working on the ovation version as well. I've upgraded from your 14.1 version to this one but I've been getting an error on the slimkat boot. I've used the twrp 3.1.1, factory reset, fresh install. The error was about data mounting. In the 14.1 I had both data and cache under the f2f system. When I installed back your 14.1 version, everything was back to normal, no errors. Do I need to format data and cache to ext4 for this slimkat version to work?
Click to expand...
Click to collapse
What build are you using?
I used this one Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180108-1016.zip and this one lineage-14.1-20171216-UNOFFICIAL-ovation.zip as well as open_gapps-arm-4.4-pico-20180110.zip.
I saw you've put a 01-10 build today, I will try it and report back.
I tried the 01-10 build and it didn't work for me either. But this time I took a photo of the error. Hopefully this will help.
update:
went straight back to twrp and format data and cache to ext4 and it worked. I didn't do a factory reset or reinstall, just changed the formats and reboot.
Looks good so far, thank you for all the hard work #secretwolf98
zspeciman said:
I tried the 01-10 build and it didn't work for me either. But this time I took a photo of the error. Hopefully this will help.
update:
went straight back to twrp and format data and cache to ext4 and it worked. I didn't do a factory reset or reinstall, just changed the formats and reboot.
Looks good so far, thank you for all the hard work #secretwolf98
Click to expand...
Click to collapse
Your welcome.
Google play seem to gives me problems, either crushes, or exists often. Also the nook button doesn't seem to work. Otherwise this new interface is beautiful and this rom looks very promising.
zspeciman said:
I tried the 01-10 build and it didn't work for me either. But this time I took a photo of the error. Hopefully this will help.
update:
went straight back to twrp and format data and cache to ext4 and it worked. I didn't do a factory reset or reinstall, just changed the formats and reboot.
Looks good so far, thank you for all the hard work #secretwolf98
Click to expand...
Click to collapse
Could I have some feedback, so I can see if I could try to fix it within the next build?
secretwolf98 said:
Could I have some feedback, so I can see if I could try to fix it within the next build?
Click to expand...
Click to collapse
Testing Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180123-1611.zip, this is a logcat with amaces TWRP, all partitions wiped, and only the rom installed:
https://pastebin.com/LW6QFY27
This is the same as above, but with with verygreen cwm and I opened more apps:
https://pastebin.com/FQnTR1c2
This is the same as above after switching to art:
https://pastebin.com/4vJE7miZ
The biggest issue is with Chromium, it crashes with this strange error:
java.lang.UnsatisfiedLinkError: Couldn't load chromium_android_linker from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/system/app/Chromium.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]]: findLibrary returned null
The graphics seem unstable with hardware overlays, you can really see it when opening/closing Downloads and DSP Manager.
fddm said:
Testing Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180123-1611.zip, this is a logcat with amaces TWRP, all partitions wiped, and only the rom installed:
https://pastebin.com/LW6QFY27
This is the same as above, but with with verygreen cwm and I opened more apps:
https://pastebin.com/FQnTR1c2
This is the same as above after switching to art:
https://pastebin.com/4vJE7miZ
The biggest issue is with Chromium, it crashes with this strange error:
java.lang.UnsatisfiedLinkError: Couldn't load chromium_android_linker from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/system/app/Chromium.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]]: findLibrary returned null
The graphics seem unstable with hardware overlays, you can really see it when opening/closing Downloads and DSP Manager.
Click to expand...
Click to collapse
A new build is currently being tested. And released soon.
Anyone using this as their daily? Currently on 7.1.2 and wondering if anyone has an opinion on performance as I probably need another rom as alot of background apps are slow like hangouts/voice.
xdause said:
Anyone using this as their daily? Currently on 7.1.2 and wondering if anyone has an opinion on performance as I probably need another rom as alot of background apps are slow like hangouts/voice.
Click to expand...
Click to collapse
Performance is awesome.
Recovery Version
I haven't done much with my HD+ since loading up CM a while back (I'm on 4.4.4 I think). Wanted to give this ROM a try since the CM one likes to reboot every day or two when it get's thinking too hard.
Question is, can I flash this with my current recovery? I'm using CWM 6.0.4.6 right now. Not sure if I needed to switch to TWRP and if so what version?
Other then wiping Data / Cache and installing the zip, anything else off hand I need to know?
Thanks all!
findmike said:
I haven't done much with my HD+ since loading up CM a while back (I'm on 4.4.4 I think). Wanted to give this ROM a try since the CM one likes to reboot every day or two when it get's thinking too hard.
Question is, can I flash this with my current recovery? I'm using CWM 6.0.4.6 right now. Not sure if I needed to switch to TWRP and if so what version?
Other then wiping Data / Cache and installing the zip, anything else off hand I need to know?
Thanks all!
Click to expand...
Click to collapse
It should work.
secretwolf98 said:
It should work.
Click to expand...
Click to collapse
Yup got brave and gave it a try once I got a backup done. Installed just fine but didn't seem to like the gapps package I installed too much. Going to play around with it a bit now that I feel slightly more confident I won't brick the thing. Thanks!
findmike said:
Yup got brave and gave it a try once I got a backup done. Installed just fine but didn't seem to like the gapps package I installed too much. Going to play around with it a bit now that I feel slightly more confident I won't brick the thing. Thanks!
Click to expand...
Click to collapse
Your welcome. Nooks can't get bricked.
Gapps
Which gapps do I use with this ROM? All that I've tried crash. I've used Open gapps and I dug up a zip from Slimroms.
Aside from the inability to use google play services, this rom is looking great.
jaydeedid said:
Which gapps do I use with this ROM? All that I've tried crash. I've used Open gapps and I dug up a zip from Slimroms.
Aside from the inability to use google play services, this rom is looking great.
Click to expand...
Click to collapse
I'm having the same problem.
open GAPPS - play store partially loads then FCs
PA - fails to install "incompatible gapps already installed" even though there isn't any.
slim gapps from the old site - can't sign in, play services FCs
Also, why isn't there a browser built in?
EDIT: It seems CWM doesn't completely clear my previous attempts when wiping. Is there a recovery that'll do an actual full wipe? Latest TWRP is broken for older android versions.
JerichoKru said:
I'm having the same problem.
open GAPPS - play store partially loads then FCs
PA - fails to install "incompatible gapps already installed" even though there isn't any.
slim gapps from the old site - can't sign in, play services FCs
Also, why isn't there a browser built in?
EDIT: It seems CWM doesn't completely clear my previous attempts when wiping. Is there a recovery that'll do an actual full wipe? Latest TWRP is broken for older android versions.
Click to expand...
Click to collapse
use twrp 3.1.1
Is there a root or magisk alternative for this that works with netflix?

Categories

Resources