I know a lot of people have created custom roms based on cyanogen or carbon, but what about just enhancing the stock rom? is that even possible? i know leapinlar has added a few scripts that do things like "enable unknown sources" but what about adding a cm-like "performance" menu to the nook stock rom? or merging elements from certain roms into the nook stock rom? sorry if this has been asked before, i was just thinking about how awesome it would be to have everything good about nook and android running on one rom as opposed to switching back and forth
i was thinking about something similar to this too. there are several things i like about the stock nook rom, mainly the gui, the keyboard etc. it just looks more pleasant from an aesthetic standpoint. however, i also like the extra performance offered by cm. so i guess best case would be if someone could 'import' some of the gui elements from the nook rom into a modified rom. however, i doubt something like that would ever happen
I like the stock ROM if someone could add a full bar with a home button it would be awesome
Sent from my Nook HD+ using xda app-developers app
nook hd rom porting
i wanna use my wiimote on my nook hd with epsxe the bt update in android 4.2 screws that up i have cm7 on my nook color and wiinote works can someone help me port it to my nook hd
I like the Nook Stock Rom Interface & Carousel
I also like the Nook stock rom gui and specially the cool carousel! I only wish that we could hava OTG and MHL easily, the ability to do folders for the apps and have a more powerfull settings interface. I like how the flow was conceived for menus and back bottoms because it makes it easy to navigate and very intuitive, it just works. I wish it was as fast as the CM 10.2 I have on emmc. Did I said I love the app Carousel?
anyone happen to know of a good paper theme on the play store? i was thinking maybe i could kludge together a mediocre facsimile of the gui. i know a few of the launchers support themes but i've tried searching the play store but i've found theres nothing that really comes close to it.
I would also like to see an enhanced stock rom. I actually like the GUI too, and rooted with the 3rd party app script it's pretty good. Add some customization and performance options and it would be really excellent.
sent by Nook HD+ using tapatalk
I must be doing something wrong. I have run CM 10.1 and 10.2 off an SD card and stock performance is way better. I like the Nova launcher interface, but definitely thing stock runs better.
sflesch said:
I must be doing something wrong. I have run CM 10.1 and 10.2 off an SD card and stock performance is way better. I like the Nova launcher interface, but definitely thing stock runs better.
Click to expand...
Click to collapse
It is because you are running from SD. On these devices the SD install runs slower because of i/o issues. That was not true on the Nook Color. If you try CM10.1 on internal memory, it runs faster. Or you could try the hybrid, it runs faster too because /data is on internal memory.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
It is because you are running from SD. On these devices the SD install runs slower because of i/o issues. That was not true on the Nook Color. If you try CM10.1 on internal memory, it runs faster. Or you could try the hybrid, it runs faster too because /data is on internal memory.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
So, 10.1 (10.2 too?) at least runs about as good (or better from some of the above threads) when loaded right on the Nook?
I'm tempted, but my wife says she is getting random reboots. I supposed I could install it (I have my squaretrade warranty after all) and see how well it works. The only other issue I think I'd have to deal with would be the package file is invalid and error (-24). So far those haven't come up on stock.
Nook Stock Rom performs best compared to CM ROM variants
sflesch said:
So, 10.1 (10.2 too?) at least runs about as good (or better from some of the above threads) when loaded right on the Nook?
I'm tempted, but my wife says she is getting random reboots. I supposed I could install it (I have my squaretrade warranty after all) and see how well it works. The only other issue I think I'd have to deal with would be the package file is invalid and error (-24). So far those haven't come up on stock.
Click to expand...
Click to collapse
Actually the Nook Stock Rom runs faster on my HD+ than CM 10.2, CARBON-JB-UNOFFICIAL-20131006-0213-ovation and Xperia-2.3.9-CARBON-JB-B11-ovation (CM 10.1) Roms running from emmc. I experience lag time while moving from App Drawer to home screen and vice versa. The only reason I use a CM ROM instead of the Stock is because I want to use the USB OTG function to use USB devices from the charging port (Thanks to verygreen for enabling this on the CM Rom).
My favorite and best performing ROM so far is Stock Rom with Enable Unknown Sources (to sideload apps) and Root (thanks to leapinlar). I will try probably today or tomorrow the Stock Rom and use the USB OTG App (USBHostSwitcher.apk) included in the Xperia Carbon Rom to see if it works on Stock ROM with root. If so... back permanently to Stock and bye to CM Roms until they perform better than Stock.
sflesch said:
So, 10.1 (10.2 too?) at least runs about as good (or better from some of the above threads) when loaded right on the Nook?
I'm tempted, but my wife says she is getting random reboots. I supposed I could install it (I have my squaretrade warranty after all) and see how well it works. The only other issue I think I'd have to deal with would be the package file is invalid and error (-24). So far those haven't come up on stock.
Click to expand...
Click to collapse
It does run better on internal memory.
Sent from my Galaxy Tab 2 using XDA Premium
anyone know how, or if its even possible to pull the stock nook wallpaper and/or color scheme and apply it to other 3rd party roms? i really like the soft, textured paper theme, but i still cant find anything remotely similar in the play store.
x000x said:
anyone know how, or if its even possible to pull the stock nook wallpaper and/or color scheme and apply it to other 3rd party roms? i really like the soft, textured paper theme, but i still cant find anything remotely similar in the play store.
Click to expand...
Click to collapse
Just go to this post http://forum.xda-developers.com/showpost.php?p=46292526&postcount=2
I explained where they are located and also uploaded the Stock Rom wallpapers as attachments.
thanks
gmicalzoma said:
Actually the Nook Stock Rom runs faster on my HD+ than CM 10.2, CARBON-JB-UNOFFICIAL-20131006-0213-ovation and Xperia-2.3.9-CARBON-JB-B11-ovation (CM 10.1) Roms running from emmc. I experience lag time while moving from App Drawer to home screen and vice versa. The only reason I use a CM ROM instead of the Stock is because I want to use the USB OTG function to use USB devices from the charging port (Thanks to verygreen for enabling this on the CM Rom).
My favorite and best performing ROM so far is Stock Rom with Enable Unknown Sources (to sideload apps) and Root (thanks to leapinlar). I will try probably today or tomorrow the Stock Rom and use the USB OTG App (USBHostSwitcher.apk) included in the Xperia Carbon Rom to see if it works on Stock ROM with root. If so... back permanently to Stock and bye to CM Roms until they perform better than Stock.
Click to expand...
Click to collapse
Did the usb otg work for the stock?
Related
Hey, for some reason all CM6 builds/ROMs based on CM6 crash pretty badly for me. Programs don't seem to fc but rather the phone freezes and the capicative buttons become unresponsive. I wipe everything before each flash but I still get the same problems.
I'm currently running the asim rom which has zero problems and excellent battery life. MCR21 (What asim rom is based on) also runs perfectly. CM 5.08 worked just fine but any builds after this point cause the above issues. I run stock kernels most of the time so I've ruled that out.
I don't currently have a2sd and install only a handful of applications:
adbWireless
Adfree
Adobe Flash 10.1
Bloo
ChromeToPhone
Dolphin HD
Flikie Wallpapers HD
Folder Organiser
Lastpass
Launcher Pro
Music Mod
Mute
OI File Manager
PSX4Droid
Quick Boot
Set CPU
SMS Popup
Titanium Backup
Trackball Alter Pro
Set CPU doesn't use profiles and I simply set it to On Demand. I can't see anyone else running into the same problems with CM6 so it must be something on my end, however other roms work just perfect so I'm baffled. Any ideas guys?
Thanks!
Have you tried another Froyo based ROM, such as Enom's? At a glance, it looks like all of the ones that work for you are Eclaire, which points to problems with software.
Have you tried running the system with NO apps installed? I know, it's hard to consider, but might help isolate an app problem vs ROM problem vs hardware problem.
khaytsus said:
Have you tried another Froyo based ROM, such as Enom's? At a glance, it looks like all of the ones that work for you are Eclaire, which points to problems with software.
Have you tried running the system with NO apps installed? I know, it's hard to consider, but might help isolate an app problem vs ROM problem vs hardware problem.
Click to expand...
Click to collapse
Yep r21 is based on 2.2. I'm starting to think it might be an app problem as you say. Weird that it is only caused on CM6 though.
Try flashing wildmonk's latest CFS 950mV kernel and see if it helps...
chobie said:
Try flashing wildmonk's latest CFS 950mV kernel and see if it helps...
Click to expand...
Click to collapse
I've tried this for the past couple of hours and while it does help to some extent I am still getting the occasional reboot. It seems to occur most when accessing internal memory such as Titanium Backup or browsing the SD card. I had previously thought the SD card might be playing up so I bought a new 8GB Class 6 card
I have been using cm7 for about 6weeks now, currently using rc1 but now that Gingerbread is available should I revert to that or stick to cm7? What is the difference?
Sent from my Nexus One using XDA App
Gingerbread builds (GRI40) are all built using the google OTA version. It includes the new drivers issued by google for our device. CM7 is a mixture of the OTA and a lot of AOSP. You have seen CM7 in action. Albiet on an older build. The GRI40 builds are mostly stock (depending on the one you choose) with a couple of addons that have been reworked (trackball alert for example) for gingerbread. Trackball wake/unlock, however, does not work on any OTA based build.
Trackball wake works on cm7, what I want to know is, has the official gb build got more to offer than cm7 or better to offer than. Cm7?
Sent from my Nexus One using XDA App
The very definition of CM7 is that it has more to offer than Gingerbread. CM7 takes the latest Gingerbread and adds more features to it.
CM7 uses source from AOSP. That is why trackball wake still works on it. Same as [email protected] and leoginger. Those are built on AOSP. Any ROM using source from the latest OTA, as of yet, can not allow for trackball wake. Google has pretty much put the kabash to it since the button push from an sleep state doesn't register anything anymore.
sparkyryan said:
Trackball wake works on cm7, what I want to know is, has the official gb build got more to offer than cm7 or better to offer than. Cm7?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
is this a serious question?
Know-Fear said:
CM7 uses source from AOSP. That is why trackball wake still works on it. Same as [email protected] and leoginger. Those are built on AOSP. Any ROM using source from the latest OTA, as of yet, can not allow for trackball wake. Google has pretty much put the kabash to it since the button push from an sleep state doesn't register anything anymore.
Click to expand...
Click to collapse
CM7 latest nightly uses the code from the latest OTA, and trackball wake still works. The trackball wake that was broken was the style that apps could use on an unrooted phone. The trackball wake in CM7 is a system change, completely different and unaffected.
CM7
Just get the nightly builds. They are built from the ota and modded "cyanogenmodly" so they are what i choose. I am on v11 of cm7 its smooth. no probs. BTW they compile and upload everyday i have to flash everyday man!
To be honest I'm gonna wait for a stable version and stick with rc1 for now, I got sick of constantly re-doing my phone every time I flashed a new nightly.
Sent from my Nexus One using XDA Premium App
Is there a stock Gingerbread ROM + Root?
If so... where is it. My wife wants stock for a change, but needs root for some of her apps.
I've been away from the n1 a LONG time.
s15274n said:
Is there a stock Gingerbread ROM + Root?
If so... where is it. My wife wants stock for a change, but needs root for some of her apps.
I've been away from the n1 a LONG time.
Click to expand...
Click to collapse
There's a few of them in the development thread
yeah, very vague... i guess i was curious if one came more recommended. I know their basically stock, but if there are variants, one must be better...
Clarkster said:
CM7 latest nightly uses the code from the latest OTA, and trackball wake still works. The trackball wake that was broken was the style that apps could use on an unrooted phone. The trackball wake in CM7 is a system change, completely different and unaffected.
Click to expand...
Click to collapse
Wrong. CM is still using AOSP in the nightlies with GRI40 bits added to it. Any OTA stock/deodexed rom does not have trackball wake because of the way google has changed the way the trackball clicks register. Many are working on a solution but it hasn't been found yet.
modaco custom rom, i baked my own in his kitchen and it's running smooooth.
Just flashed the latest CM7 nightly and gapps over RC1 and couldn't be happier. Scrolling, swiping and animations running really smooth now. No hiccups!
Trackball wake is still the most important feature for me too.
Definitely CM7. I went back to stock N1 gingerbread to check it out and came to a conclusion that it offers no advantages over CM7 -- it doesn't feel faster (the opposite, moving between desktops felt a bit jumpy) and lacks the customizability (for example, non-customizable power control was a deal breaker).
I beg to differ from most of this thread.
For anyone looking for stable ROM, CM7 is a pure disaster and the very definition of instability and bugs (found lots of them, starting with the ill-famous wonk, but the latest volume dropping was what finally got me to revert back to Enomther's Froyo).
I didn't test the stock Gingerbread yet, but I believe it to be much less buggy than current CM7.
Both of them don't work well with custom launchers, loaded with more than 5 screens. Even 5 screens performance is barely acceptable. Also, no 720p and no camera enhancements on stock Gingerbread yet, no SGS power bar, and no trackball wake - and the camera enhancements aren't there on CM7 either. If you value these more than the new look, cool screen off animation, better stock keyboard and proper copy-paste - stay with Froyo.
DirkGently1 said:
Just flashed the latest CM7 nightly and gapps over RC1 and couldn't be happier. Scrolling, swiping and animations running really smooth now. No hiccups!
Trackball wake is still the most important feature for me too.
Click to expand...
Click to collapse
You mean the home screen scrolling that turned choppy on ginger bread is now smooth again with the latest cyan nightly?
I've had no issues with CM7 since starting to use RC1. Nightly #14 is speedy and rock solid. It's so easy to flash to the latest build using Rom Manager each time too. Just download and flash the latest ROM, without clearing anything, and you're soon running the latest build without having to reconfigure or reinstall anything.
I've replaced ADW with the stock Gingerbread launcher found in the market and use the Nexus Revamped, LWP app. Scrolling lists, Homescreens, App Drawer, you name it... is all much faster, smoother and glitch free.
I'm using RC2 now, and I've had no issues at all, the Rover theme I'm using perfectly compliments the rom too, I like the extras cm7 offers and it seems to be quicker than gb on my mates desire!
Sent from my Nexus One using XDA Premium App
It is finally here!
http://reviewhorizon.com/2011/03/cyanogenmod-7-0-rc-4-release-candidate-for-nook-color-available/
...and brings hardware acceleration
Straight from nightlies to RC........ wow
Ok, for those interested, i do not believe this will have the video lag fix.. i do not get how this can be an RC level release....
I just installed it and it seems to work fine, including YouTube. No lag detected, at least on my Nook Color.
Anyone know if the sleep issue has been resolved?
Or if the menu lag/garbage collection issue has been fixed? When I tried it about a week ago certain apps such as Reddit is Fun were basically unusable due to the extreme menu lag.
thank you XDA
You've given me a very nice tablet for cheap.
Glad to donate. This is really fun!
CyanogenMod-7.0.0-RC4 has arrived
CyanogenMod-7.0.0-RC4 has arrived
http://www.cyanogenmod.com/blog/cyanogenmod-7-0-0-rc4-has-arrived
The next round of RCs have arrived. From RC2 until now has mainly been bug fixes and we’re getting near the final state. In this release, there may still be some lingering GPS issues on the Evo and the N1 call audio bug hasn’t been fully fixed. But if you were happy with the previous RCs/Nightlies on your device, there is no reason not to update to this one.
That being said, this is the most stable version of CyanogenMod 7 to date and will probably be the last RC before the final rolls around. The most notable new fixes are on the tablet side of devices. The Nook Color, for example, now has working hardware acceleration. Because of these fixes, many of them are receiving their first RC. There was also a big fix from AOSP for EGL issues, which is why all devices bumped to RC4 from RC3.
Feel free to grab CM7-RC4 (or RC3.14159265358979323846264338327 as we call it internally) from ROM Manager, our forums, or our mirror network if you prefer manual downloads.
Click to expand...
Click to collapse
Get it here:
http://download.cyanogenmod.com/get/update-cm-7.0.0-RC4-encore-signed.zip
efaden said:
Anyone know if the sleep issue has been resolved?
Click to expand...
Click to collapse
Try the new version of Wake Timer in the Market. Works for me on Froyo.
Are there any major issues in RC4 that should make me hesitate to move up from Nookie Froyo to CM7?
Does the internal media partition work properly on this ROM?
Sent from my Nook Color!
Only issue I had was that I had to manually install google apps to get the market working.
Other than that- I miss the Tablet Tweaks.
can i flash this over the 29 nightly with out wiping
Yes.
10char
Nightly over nightly gave me no problems.
You might be fine.
Worst case is that you would have to boot into recovery to re-flash the rom and wipe data and cache, so just make sure to back up your current rom.
cmstlist said:
Try the new version of Wake Timer in the Market. Works for me on Froyo.
Are there any major issues in RC4 that should make me hesitate to move up from Nookie Froyo to CM7?
Does the internal media partition work properly on this ROM?
Sent from my Nook Color!
Click to expand...
Click to collapse
The issue was that you couldn't actually sleep the device... death sleep or something in the kernel and the nook color. Basically this means the device was always on and using about 2% of the battery per hour even while "off". That pretty much means it can't go on the wifes NC.
Where do you get Android marketplace apk? I just flashed this and now I don't have a market place. I'm coming from phiremod 5.2.
Sent from Fascinate SuperClean 2.9.2 Voodoo Using Xda Premium App
ajd88 said:
Where do you get Android marketplace apk? I just flashed this and now I don't have a market place. I'm coming from phiremod 5.2.
Sent from Fascinate SuperClean 2.9.2 Voodoo Using Xda Premium App
Click to expand...
Click to collapse
There is a gapps zip for Gingerbread, linked from the CM wiki.
Sweet. thank you.
Sent from Fascinate SuperClean 2.9.2 Voodoo Using Xda Premium App
quick question from someone who's never messed with nightlys before my nook...why would I install this instead of nightly build 32? I'm guessing the RC4 would be just a really good nightly build that they feel is ready for release, yes?
Edit: I just noticed that the RC4 was just posted, so I think what I said is basically right.
Another edit (sorry): also, can someone tell me what clearing the cache does (or doesn't do if you decide not to do it) when you switch or update roms?
JLCollier2005 said:
quick question from someone who's never messed with nightlys before my nook...why would I install this instead of nightly build 32? I'm guessing the RC4 would be just a really good nightly build that they feel is ready for release, yes?
Edit: I just noticed that the RC4 was just posted, so I think what I said is basically right.
Another edit (sorry): also, can someone tell me what clearing the cache does (or doesn't do if you decide not to do it) when you switch or update roms?
Click to expand...
Click to collapse
The cache consists entirely of files that can be thrown away as they get regenerated by apps as needed. When you upgrade your ROM it's recommended you clear the cache so that the system and its apps don't get confused by cached files that represent scenarios that are not relevant to the ROM you're running.
efaden said:
The issue was that you couldn't actually sleep the device... death sleep or something in the kernel and the nook color. Basically this means the device was always on and using about 2% of the battery per hour even while "off".
Click to expand...
Click to collapse
I would really like to know if this is fixed in the RC release too.
Just flashed it to my NC. I went back to Zeam launcher just becuase it's what I was using on Nookie Froyo and I had all the settings & shortcuts backed up already. I also added Button Savior for those times when the status bar buttons are hidden. I really like the "lens" lock screen as it's much more convenient to swipe down on a 7" screen than across.
So far I haven't run into anything that doesn't work. Titanium Backups of my user apps went in quite happily. My Angry Birds can rest easy, their hard work has not been in vain
The only hitch so far - my Titanium restore of Thumb Keyboard did not work as expected. Under input settings, the checkmark refused to go on. I re-installed from the Market, enabled it successfully, and then restored the data only from Titanium.
Is there any reason to go from CM7 to the 1.41 update?
The only thing I was looking forward to that I can't do on CM7 is run the Hulu Plus app like the Nook Tablet can do. But it looks like that won't even be possible with the Nook Color update.
Is there any reason to bother with the 1.41 update for those running CM7?
No Hulu...at least not yet
Netflix, Rhapsody, UStream, Showtime, MOG, Grooveshark and other crap.
I'm pissed. They F'd the Nook Color up as far as I'm concerned. I'm going to try and go back to 1.3 maybe. I needed the native Reader app and they messed it up for me. It does auto-rotate now which is nice, but it does not format my companies manuals correctly now.
Paul22000 said:
Is there any reason to go from CM7 to the 1.41 update?
The only thing I was looking forward to that I can't do on CM7 is run the Hulu Plus app like the Nook Tablet can do. But it looks like that won't even be possible with the Nook Color update.
Click to expand...
Click to collapse
Wait, what's wrong with Hulu Plus app on CM7? I just watched the latest Colbert Report episode on High quality mode using that app on my Nook Color.
You'll have to manually install the apk and restore data from TiBu to get it to work, but it does work and has for months.
Thread below has the files you need. Drop 3 files in zip into Timbuktu Backup folder (I can't remember if /sdcard/TimbuktuBackup is the default), then install the APK by double-clicking on it but do not open after installation is done --- restore data only setting in TiBu for Hulu Plus first. You should be up and running without a hitch after that (I'm running it without a modded build.prop)
http://forum.xda-developers.com/showthread.php?t=1182668
Maybe a little off but think this way
+ ICS = Windows 8
+ CM7 (Gingerbread) = Windows 7
+ Stock (Froyo) = Windows XP
Do you want to go back to XP from W7?
angomy said:
Wait, what's wrong with Hulu Plus app on CM7? I just watched the latest Colbert Report episode on High quality mode using that app on my Nook Color.QUOTE]
Do you know if it checks the IP address for location? For the most part Hulu adn most video streaming only work in the US.
Click to expand...
Click to collapse
angomy said:
Wait, what's wrong with Hulu Plus app on CM7?
Click to expand...
Click to collapse
You'll have to manually install the apk and restore data from TiBu to get it to work,
Click to expand...
Click to collapse
I think you answered your own question, hah. Natively, the app does not work, which is what is wrong with it.
I believe Conde Nast magazines like Wired require Nook native software (and not the Nook Android app). Not sure if the magazines work on 1.3 or require 1.4.
I re-flashed to 1.4.1 today to try things out. The interface is outwardly the same as on the Nook Tablet now, though I understand it's still Froyo underneath. Wired Magazine does load now -- no more "not on this device" message like on 1.3 -- and all the neat, interactive features in the magazine work just as on the NT.
I actually like the 1.4.X interface. Unfortunately, my experiments with rooting it on my NC have not worked, and the bloody thing just wiped itself. If I could get it to function like the rooted NT, I'd probably stay on it for a bit. It's a shame the B&N launcher isn't available as an overlay. I guess they're scared I'll buy stuff from them?
votinh said:
Maybe a little off but think this way
+ ICS = Windows 8
+ CM7 (Gingerbread) = Windows 7
+ Stock (Froyo) = Windows XP
Do you want to go back to XP from W7?
Click to expand...
Click to collapse
Android is linex based but I guess you could put it that way.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Is it possible just to apply 1.41 update onto the CM7 - what would happen then? My bro does not care about root n all stuff - he just wants stock back because CM7 eats the battery and shouldnt have done it in the first place...
eenbox said:
Is it possible just to apply 1.41 update onto the CM7 - what would happen then? My bro does not care about root n all stuff - he just wants stock back because CM7 eats the battery and shouldnt have done it in the first place...
Click to expand...
Click to collapse
CM shouldn't be eating your battery but if you really want to get back to BN's walled garden check out the restoring to stock section of the guide in my sig.
Sent from space
Just got my Nook HD+ 32GB today - very excited to put CM on it!
I'd like to hear opinions/recommendations on which version I should try first. I'm mostly interested in stability, but I also wish to have the latest'n'greatest.
CM-10.1.3-RC2 -or- CM-10.2-20130914-NIGHTLY ?
Try cm10.2. If you feel it unstable, try cm10.1.3.
Sounds like a good strategy. I'll give CM 10.2 a try first.
software_samurai said:
Sounds like a good strategy. I'll give CM 10.2 a try first.
Click to expand...
Click to collapse
If I remember correctly, I had trouble with Amazon Kindle on CM 10.1.3-RC2. It is working on CM 10.2.
dmullens said:
If I remember correctly, I had trouble with Amazon Kindle on CM 10.1.3-RC2. It is working on CM 10.2.
Click to expand...
Click to collapse
The dalvik dump tweak which allowed the Kindle App to work in 10.2 is in 10.1.3-RC2. Some are still reporting issues, but defiantly a minority.
Just a quick update:
I installed cm-10.2-20130915-NIGHTLY-ovation and the gapps, and so far it's been running very well for me. Chrome occasionally crashes, and I've experienced a few hiccups relating to WiFi, Bluetooth, and the nav menu button. But overall I'd say it's pretty stable.
software_samurai said:
Just a quick update:
I installed cm-10.2-20130915-NIGHTLY-ovation and the gapps, and so far it's been running very well for me. Chrome occasionally crashes, and I've experienced a few hiccups relating to WiFi, Bluetooth, and the nav menu button. But overall I'd say it's pretty stable.
Click to expand...
Click to collapse
Have you tried any other browsers to see if they crash as well?
I've used the default browser a few times now, and it hasn't crashed on me like Chrome.
I just installed 10.1.3 on a brand spanking new unit and the kindle app closes right away. The hdmi output also has black bars all around the picture. Going to try 10.2 tomorrow. Any recommendations on which build works best?
cutefuzzybunny said:
I just installed 10.1.3 on a brand spanking new unit and the kindle app closes right away. The hdmi output also has black bars all around the picture. Going to try 10.2 tomorrow. Any recommendations on which build works best?
Click to expand...
Click to collapse
The one you are running. There is an easy fix for Kindle. Just set the heap size to 384M in /system/build.prop.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
The one you are running. There is an easy fix for Kindle. Just set the heap size to 384M in /system/build.prop.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
What is the downside of increasing the heap size?
---------- Post added at 04:04 AM ---------- Previous post was at 03:49 AM ----------
software_samurai said:
I've used the default browser a few times now, and it hasn't crashed on me like Chrome.
Click to expand...
Click to collapse
The 2 apps that cause occasional crashes for me are Playstore, when updating apps and stock browser, with tab with video graphics. Chrome was a problem that I abandoned.
Crashes are spontaneous reboots. I also get rare incidents of screen having no sensitivity to touch but the hardware keys remain functional. I have to shutdown and restart when that happens. The browser is active when that happens too.
leapinlar said:
The one you are running. There is an easy fix for Kindle. Just set the heap size to 384M in /system/build.prop.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Guess I'll need to figure out how to edit that file. I know what it is and have edited other system files, but so far not that one! Are there any downsides to setting the heap size to that? If not, any reason you can think of why it isn't that way by default? Hasn't this been an issue for a while now?
I'm not doing well with this build. I put 3 apps on it. Kindle didn't run, my sons "my math app" (free in the play store) doesn't display properly. Its supposed to put two numbers and a plus/minus/multiply/divide symbol and a total line. Puts the two numbers way apart and the sign in the middle of them, and its either showing part of the same problem off the bottom of the screen or its the next problem...didn't really look at it that hard. And the nfl sunday ticket app gave me bars around the video and wouldn't go into full screen mode. When I tried full screen, I had to tap the icon about 30 times, it did get larger but not full screen, then when I tapped it again it went to quarter size and was very resistant to going back to sort-of-full-screen.
Been running the stable 10.1-10.3 on my old 7" nook tablet for a while now with great success. Surprised to find this a little less 'stable' than prior stable CM releases.
I don't think the hdtv adapter picture size is fixed until 10.2 and given my results with display issues with other apps, does it make sense to just plow ahead to those or are the bricking problems I've seen here and there still a concern with those nightlies? Is one considered particularly stable vs the others? I ran 10.1 nightlies on the old tab for a while without any major issues cropping up.
cutefuzzybunny said:
Guess I'll need to figure out how to edit that file. I know what it is and have edited other system files, but so far not that one! Are there any downsides to setting the heap size to that? If not, any reason you can think of why it isn't that way by default? Hasn't this been an issue for a while now?
Click to expand...
Click to collapse
The developer did just change the heap size to fix the Kindle problem. The problem now is Amazon keeps changing the app because other devices were having trouble too. My older version of Kindle works fine with the recently changed heap size, but the newest versions on Play Store don't work with it.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
The developer did just change the heap size to fix the Kindle problem. The problem now is Amazon keeps changing the app because other devices were having trouble too. My older version of Kindle works fine with the recently changed heap size, but the newest versions on Play Store don't work with it.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the info. These things are always harder than they look.
leapinlar said:
The developer did just change the heap size to fix the Kindle problem. Kindle appThe problem now is Amazon keeps changing the app because other devices were having trouble too. My older version of Kindle works fine with the recently changed heap size, but the newest versions on Play Store don't work with it.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
It's a strange problem. The 0927 build has 402 heap. Kindle FC on my HD+. I increased to 480 and Kindle runs. I keep reading here that 384 works so I tried that. AND no FC.
Would build.prop in a folder, "storage/emulated/0/system/etc" work?
king200 said:
Would build.prop in a folder, "storage/emulated/0/system/etc" work?
Click to expand...
Click to collapse
No. But you could try putting just that heap size line in /data/local.prop. Local.prop gets loaded after build.prop and for some settings can override the build.prop setting.
EDIT: I just tried that and it works. You can put this line in local.prop and it will override the build.prop setting. That means it will survive the flashing of a new ROM with other settings:
dalvik.vm.heapsize=384M
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
... try putting just that heap size line in /data/local.prop. Local.prop gets loaded after build.prop and for some settings can override the build.prop setting.
EDIT: I just tried that and it works. You can put this line in local.prop and it will override the build.prop setting. That means it will survive the flashing of a new ROM with other settings:
dalvik.vm.heapsize=384M
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Handy tip for Nightly flasher.
As an FYI, I installed the 9/26 10.2 nightly since the info for the 9/27 and 9/28 wasn't particularly good. Kindle runs fine. NFL Sunday ticket works so far but I haven't tried it on a real game or tried the hdmi output yet to see if its formatted correctly. My Math App displays more correctly, with the numbers and signs showing up formatted correctly, although the seconds on the timer in the lower right corner are clipped off, you just see hours and minutes, but only part of the first two digits for seconds.
Didn't update gaaps, but everything that was on there was either updated or runs fine with what was on there. Tried chrome, play store, google search,etc. Everything ran but I didn't put them through an exhaustive test.
Just did the CM updater from 'about tablet' from 10.1.3 to the nightly and then told it to update. Thats it.
---------- Post added at 04:46 PM ---------- Previous post was at 03:51 PM ----------
Alright, weird. As I mentioned above I installed the 10.2 9/26 nightly and it made most of my problems go away. However, under 'about tablet' it says android version is 4.2.2 and cm version is 10.1.3. Same as it was when I installed cm 10.1.3, yet my apps work now and they didn't before I did the update. Hmmmmm....
---------- Post added at 05:24 PM ---------- Previous post was at 04:46 PM ----------
Alright...weird. I put the 9/26 nightly of 10.2 and the latest 10.2 gaaps on the sd card I made for the 10.1.3 install, booted into that, applied 10.2 and gaaps, everything looks good but kindle is back to FC'ing and the sunday ticket app still displays a 3/4 size image in the middle of the screen on the tv with the hdmi adapter just like 10.1.3 stable did. Thought that was supposed to be fixed in the later 10.2 releases. Doesn't appear to be, unless there's a magic trick. Full screen on the tablet, not on the tv.
Wondering what magical thing happened when I tried the in-place upgrade from 10.1.3 stable to 10.2 using cmupdate on the tablet, where it didn't actually go to 10.2 but the kindle app started working without editing anything or doing anything.
10.1-20130813-NIGHTLY-Ovation
cutefuzzybunny said:
I just installed 10.1.3 on a brand spanking new unit and the kindle app closes right away. The hdmi output also has black bars all around the picture. Going to try 10.2 tomorrow. Any recommendations on which build works best?
Click to expand...
Click to collapse
I'm running 10.1-20130813-NIGHTLY-Ovation on my Nook HD+ and I'm having very few issues. I had attempted to apply one of the 10.1.3 updates and it caused some apps to crash, so I switched back. I've not tried using HDMI out with it, though.
I have a Sandisk 32GB MicroSDHC Class 4 Memory Card that I have dedicated to holding the stable CM release (and accompanying CWM and GAPPS files) so I can always flash the HD+ to a known working state if something goes haywire. It also helped out when I bought an HD+ for the wife.
Cheers,
Dave\Esotic
Bluetooth issues on 10.2
Esotic said:
I'm running 10.1-20130813-NIGHTLY-Ovation on my Nook HD+ and I'm having very few issues. I had attempted to apply one of the 10.1.3 updates and it caused some apps to crash, so I switched back. I've not tried using HDMI out with it, though.
I have a Sandisk 32GB MicroSDHC Class 4 Memory Card that I have dedicated to holding the stable CM release (and accompanying CWM and GAPPS files) so I can always flash the HD+ to a known working state if something goes haywire. It also helped out when I bought an HD+ for the wife.
I had been running 10.1.something hybrid for the longest time on my Nook HD+, without any issues.
Yesterday I decided to go to 10.2.latest and now bluetooth is not working; I can not pair with Creative D-200 .....
Any ideas? (Apart from going back to 10.1.x ?)
Thanks,
A
Click to expand...
Click to collapse