yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
I don't know much about the V6 script. I thought it only ran when you started it and then the script would modify the build prop for you. Anyway, if it is changing build.prop, the local.prop can override it if it is not a write once setting. I am pretty sure the heap size can be changed. And I think the wifi supplicant scan interval can also be changed.

EDIT: BTW, there is a way to see what the final settings turn out to be. Just go to terminal, type su (enter), then type getprop (enter). It will scroll off a long list of your properties. You can just scroll up to read it all. You can also change the properties by typing setprop followed by the property setting you want to change.
[Nook Color Android Development] 12paq:
Hey leapinlar or eyeballer,

Can the hierarchy of the build prop files in ICS Android be simply explained? Does one take precedence over another and are both or one written over with a non wipe data CM instal?

I have been editing the files before I flash the rom and just want to understand and learn a bit more about manipulating my builds.

Thanks!
[Nook Color Android Development] leapinlar:
The build.prop file is created when the build is made. (Hence, build.prop, properties that are set during the build.) It is included in the nightly zip and gets written to /system along with all the other nightly files. When the system boots, it sets the properties according to what is there. But when it finishes with build.prop, it looks for local.prop in /data. If it finds it, it loads that too. What is there can override what was set in build.prop only if the setting was not a write once setting (ones starting with ro, for instance, are write once).

There is a way to have a flashable zip that dynamically edits the build.prop from what is in the nightly to what you want it to say. You just have to flash that after the nightly.

Edit: You asked about a non-wipe install. I'm not sure what exactly you meant by that, but if you meant you did not wipe cache or dalvik, neither make any difference. When the zip is installed on emmc, the nightly automatcally formats /system before extracting its files and putting them on /system. /data is not touched.
[Nook Color Android Development] SeaFractor:
Excellent! This is a great reminder on how to check the syntax of any entries we'll be adding to build.prop or local.prop.

Other than waiting for opengl to be resolved again, you've removed my worries about nightly flashing and having to manually re-edit each time afterwards.
[Nook Color Android Development] tnpapadakos:
just posted 3/2, 3/3 and 3/4

click on link in my sig

all three without openGL
[Nook Color Android Development] 12paq:
Thanks man,

That answers everything.

..and, oh I said a non "data wipe" just meaning what part of a build (or build.prop files) specifically is preserved or overwritten from a normal CM install/update that does not touch data. But I have this figured now. Thanks again.

12
[Nook Color Android Development] eyeballer:
The 3/7 opengl nightly is fully functional.. really have no idea what happened there :) but a couple of others in the #nookcolor chan confirmed the same blip..
[Nook Color Android Development] bretzke:
Any chance you can apply your change package (tnp) to the new 0307 OpenGL zip?

Link: http://techerrata.com/file/nightly_...-9.0.0-encore-20120307-0900-opengl-signed.zip

Thanks,

Dave
[Nook Color Android Development] eyeballer:
Why don't you just make a flashable zip people can apply over any nightly?
[Nook Color Android Development] sakisa950:
was the weird rotation in games ever fixed

sorry if it has been addressed but has the rotation issue been fixed
[Nook Color Android Development] EnTg888:
Hey Eyeballer, does your wifi come back up when you come out of sleep? Currently I still have to toggle it off and on again if it's set to turn off with the screen.
[Nook Color Android Development] Soloos:
I have the same problem, so I use Tasker to do the toggling for display on/off.
[Nook Color Android Development] eyeballer:
Apparently not if I use the built-in wifi-off setting. I usually use Green Power to do it and it works fine. I just disabled it for testing sleep this time around.
[Nook Color Android Development] J515OP:
Same problem here. After reading eyeballer's post I also tried changing the wifi setting. I changed to off when screen off unless plugged in. It doesn't come back on when the screen comes back on though so you have to manually toggle it or as suggested use an app. For now I have just gone back to always on.
[Nook Color Android Development] boomn:
Same here, but I'm still toggling it manually
[Nook Color Android Development] mateorod:
I haven't looked into this as much as I will in the next day or so, but I think this is what is killing my battery life as well. When it goes to sleep, it continually searches for a signal and for some reason can't find it.

When it is set to always connect, it will lose the signal periodically when it tries to go to sleep. It spends the rest if the screen-off time continually attempting to reconnect, never being able to until I turn the screen on and manually toggle wifi. That results in the battery draining at a rate similar to low-powered usage.

I will try an outside toggle (elixir or green power or some such) and see what happens. I will also try had remember to consult the battery stats and run a dmesg here and there.
[Nook Color Android Development] freonchill:
i keep my wifi off (airplane mode) 90% of the time and still only get 2-3 days before the battery is drained.
[Nook Color Android Development] worldindo1:
Rotation issue? I remember waaaaaaaaaay back there was an issue on Fattire's sneakpeek-fullofbugs2 but that has since long been fixed. Are you referring to how the screen looked funky when you went from portrait to landscape? Or possibly if that isn't what you're talking about, could you post a video of what you're talking about?
[Nook Color Android Development] leapinlar:
Early on, like you said, there was a rotation issue. Fattire fixed it by putting the necessary rotations in the kernel rather than a setting in build.prop. Recently (4/27), keyodi discovered that a fix to ics had been made that made fattire's kernel rotation unnecessary. So he removed the kernel rotation and re-inserted the build.prop setting.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] freonchill:
tired BBS and "partial wakelocks" over the last 4d 36m 9s - the overwhelming offender was *backup* android system @ 1h 1m 51s; while the next item was my google reader sync @ 2m 20s...

i am at 33% battery, it was (before it updated) at ~70% this afternoon when i came home. i had not touched it for 1-2 days.

cpu spy says that its been up for 101:57:54, since i booted last (which was after i came back to it and the battery was dead)

1100mhz 0:12:54 0%

800mhz 0:1:22 0%

600mhz 1:44:42 1%

300mhz 0:00:00 0%

deep sleep 99:58:55 98%

i disabled backup and going to see if it will stay @ 33% for the next couple of days without use.
[Nook Color Android Development] worldindo1:
On an unrelated topic, does your modded NookColorUMS have any problems mounting /boot on Win7? I'm trying at this very moment (because I want to install TWRP as a uAlt recovery) and the app seems to have no effect. Win7 just reads it like a normal MTP and shows me eMMC and SD partitions. Is there some sort of command I can run in CMD to get it to work? This is my work computer so I can't install ADB. In the meantime however, I will get ADB on my Ubuntu workstation. But for now is there some sort of workaround?
[Nook Color Android Development] eyeballer:
I haven't used NookColorUMS in a while, but if you want to flash TWRP to alt then you can find my flashable zips here: http://xdaforums.com/showthread.php?t=1469732
[Nook Color Android Development] leapinlar:
I think you may be running too old of a CM9 nightly. UMS has only been activated a short time (since 4/22). You have to go to settings, storage, menu, USB Computer connection and there should be an option 'mass storage'. Select that. If it is missing or greyed out, update to a newer nightly. (I just updated my tips post to reflect this).

But it would be easier to flash eyeballers zip.
[Nook Color Android Development] shumash:
The latest eyeballer build restores the problem. The display rotates, but landscape is portrait (upside down) and portrait is landscape and the touchscreen is wonky and ... I reverted.
[Nook Color Android Development] leapinlar:
Are you sure you have the right kernel? Do you have the build.prop setting that says hwrotation=270? You may be using a custom build.prop from some supercharging or something. See my earlier post about what keyodi did recently to the kernel and build.prop.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] worldindo1:
I run the newest as they drop on his techerrata mirror. I never actually realized there was an option for UMS. Thanks :) And as for TWRP I'll use the aformentioned ZIP.
[Nook Color Android Development] shumash:
I'll check that out. I did use the 2.6.32.59 kernel when I flashed it 'cause the build kernel looked older. Probably my bad.

EDIT:

Yup, that was the problem. All is well.
[Nook Color Android Development] freonchill:
well, that wasnt it

down to 14% after a day without using it (30% - 14%)

ideas?
[Nook Color Android Development] derekr:
Is your battery getting to be old and tired?
[Nook Color Android Development] RASTAVIPER:
28/4 non open gl has problem for downloading.

P.S. Working fine from my PC.

Unleashed from my Revolutionized Desire HD
[Nook Color Android Development] freonchill:
lets hope not. i never had a problem with it losing power during sleep in cm7.

it could sit @ 99% for 2-3 days without use. in cm9 it lost about 5% in the last 10-12 hours in cm9.

ive only had it since late last summer; so its not even a year of battery usage.

been running cm7 on SD cards, since i got it, june/july 2011

and running cm9 on SD cards, since january/february 2012

it could be the battery sucks after a year, but since others are also complaining about the same sleep battery drains in cm9, i am guessing i am not the only one.

im @ 46% right now. ill boot to the nook stock software and let it sleep overnight, see if i am still @ 46% tomorrow night.
[Nook Color Android Development] nagi603:
I've been using 4/28 non-GL since it came out, and so far absolutely zero problems with battery drain in sleep, and not one SoD (having an automate it script to turn wifi of and generally not having it on should be partially responsible for these).

Speed is acceptable, 2D GUI (still using launcherpro) is not as fast as it was on stock rooted 1.2, but more than manageable. Shame about the lack of hw video playback and 2D acceleration.

All-in-all: good job!
[Nook Color Android Development] leapinlar:
Since the devs updated the kernel to .59, SODs are not a problem anymore. I leave my wifi on all the time and have not gotten one SOD and used to get them often.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] freonchill:
12 hours later of sleep in nook software and still @ 46% battery life

its something to do with cm9, that i didnt have a problem in cm7.

going to upgrade to 5/4 non-openGL release and see how that turns out

if still have "long term sleep battery drain" with the 5/4 release; then i will do a clean install and see what happens then.
[Nook Color Android Development] sakisa950:
srry no videos but when im try to play xplane 9 or jet car stunts it shows the game in landscape but the motion controls are in potrait running the 03-10 nightly (no problems for me except hd video and this rotation issue)
[Nook Color Android Development] leapinlar:
The rotation has been changed in the newer nightlies. Try one 4/28 or later.

Sent from my NookColor running ICS and Tapatalk
[Nook Color Android Development] RASTAVIPER:
Unfortunately, I can't download any ROM from terracheta sure from my Nook.

I am trying from Cm9 boot of Racks dualboot ROM and tried with 3 different browsers (Opera, Dolphin and stock ).

From PC is fine.

Any ideas for direct download?

Unleashed from my Revolutionized Desire HD
[Nook Color Android Development] bcvictory:
Hey eyeballer, Can you build CWM Recovery and post it please. I really need it and I can't build it myself because I have slow internet.
[Nook Color Android Development] bdcrim:
I had the same issue. I installed the goo manager app referenced in the OP and downloaded with no problems.
[Nook Color Android Development] leapinlar:
There is a recent one here:

http://xdaforums.com/showthread.php?p=23537853

Or you can get TWRP recovery here:

http://xdaforums.com/showthread.php?p=21932561
[Nook Color Android Development] stolenmoment:
hard freeze

I just had my first hard freeze in a looong time. I had installed the daily non-opengl incremental about an hour before (it was posted later than usual, with lots of "optimizing" to do), and used it lightly since then, mostly plugged in to AC. I unplugged, pocketed, walked around a bit, then came back to my desk (I'm at work), plugged in. The screen lit up as usual with the lockscreen, showing the correct time, but has stopped updating the time or responding to inputs. The status bar shows only the WiFi SSID, signal strength, and battery icon. The lockscreen shows the circled lock, the date and (now incorrect) time and the time of the next alarm (I use alarm clock plus), and "Charging, 98%". The background image is correct (NatGeo daily).

It's now been ten minutes, and the back is getting warm to the left of the speaker grille, like earlier freezes.

What should I look for in the log after I reboot?
[Nook Color Android Development] friedsonjm:
For what its worth, I highly recommend TWRP. Much more capable and user friendly.
[Nook Color Android Development] eyeballer:
Couple of updates.. in the next builds (5/8) I'm cherry-picking in this patch http://review.cyanogenmod.com/#/c/15698 This should reduce the amount needed to scroll when you open settings, please provide feedback.

Also, there's a pending change to the way cm builds will be named: http://review.cyanogenmod.com/#/c/15662/

So i'm including that so I can make sure my changes to my own build scripts work. Shouldn't affect you other than you'll see a new name for each zip. Goo updater/incremental updates should still work just fine. (i hope...)
[Nook Color Android Development] stolenmoment:
Yes! Thank you! I seldom change the things that pop up. I still miss the CM7 Power Widget...

Yep, worked fine, so far.
[Nook Color Android Development] leapinlar:
Eyeballer, this pending change is very bad for verygreen SD installers. Verygreen's script requires that the file name start with update- or it won't install the zip. Users will have to rename their zip everytime they want to install a new one. I could modify his script for new users, but for existing users it's not good. Can you see if you can use your influence with the team to modify this pending change somehow? At least can you modify your own script to put the update- back on your nightlies?
[Nook Color Android Development] eyeballer:
The decision has pretty much been made for cm to dump the update- and -signed portions of the filename. I could go back to using it, but in the long-term it's probably best to just modify the installer script and get everyone updated to the new scheme. If/when we move to official nightlies it'll be needed anyway.
[Nook Color Android Development] leapinlar:
I'll see what I can do to modify his script. What would you suggest I use as a test for the file name? cm-, or something else? I will leave the update- in there for backwards compatibility, but I want to be sure I've got the future covered.

But, I would appreciate it if you could change your script also so there will be some transition time for the users.

Sent from my NookColor running ICS and Tapatalk
[Nook Color Android Development] bigbob23:
I updated using Goo Manager/twrp and it handled the change (with a diff-) just fine.
[Nook Color Android Development] mwalt2:
Thanks for the builds eyeballer. Are there any settings to get videos to play more smoothly? I can't get the sling player to play at all really. It's really choppy.

Sent from my Galaxy Nexus
[Nook Color Android Development] eyeballer:
Since it seems like a lot of you are using the goo manager integration, I've decided to add it to my builds, so it will now ship on each nightly as default. :)
[Nook Color Android Development] freonchill:
looks like nagi603 was right about the 4/28 release

i installed 5/4 over 2/25 and it seems to have fixed the slow power drain

though i did have a weird pseudo-SoD during the first deep sleep after rebooting

rebooted twice since then and havent had any other problems
[Nook Color Android Development] lorddunlow:
I'm so happy with the quality of CM9 on my nook. Thanks for the nightly builds! The incremental updates are awesome. I have only one major issue with my setup that is the only thing that is annoying me. I'm not sure if it's build specific or just the state of CM9 at this point. I use 2 programs that worked flawlessly on CM7, but on CM9 I have a wifi related issue that prevents syncing with other devices. I use DataSync by Quint Stoffers and ComicRack by cYo Soft on both my phone and Nook. Both of these programs sync data between my nook, my computer and my phone via wifi. It seems on CM9 I can't initiate these syncs from my Nook. DataSync is useless because of this on CM9, and I have to initiate the sync from my computer to get ComicRack to sync up (nothing happens when I click the wifi sync in-app on the nook). Both have no problems in CM7. I don't know if this is due to a known wifi issue, but I would love to help squash this bug. Let me know what logs/info/etc. I can provide to help.
[Nook Color Android Development] DigitalMD:
More likely these issues are due to applications being not compatible with ICS. Have you checked with the developer of the apps?
[Nook Color Android Development] ganovim:
cm9 earlier versions wotk at 240 density

The newer verisions fail when build.prop contains a density setting of 240

Any way to fix this?
[Nook Color Android Development] bcvictory:
This might be a stupid question but would we be able to use any of the enhancements from the MiRaGe forum?
[Nook Color Android Development] DizzyDen:
Leave lcd_density out of build.prop... or set it to 160 there and set it to 240 in data/local.prop
[Nook Color Android Development] RASTAVIPER:
Finally did it through Goo manager.

Proceed with upgrade, but even after that I still have random FC of different apps. :-(

Unleashed from my Revolutionized Desire HD
[Nook Color Android Development] stolenmoment:
Lots of "optimizing" to do?

Why should there be so much "optimizing" when an incremental update runs? I understand that there are replacement .apks (44 in today's) and .jars (21) that need to get Dalviked, but I would think that the process of copying off and restoring the existing .apks should be able to restore the modification times of the originals, yes? Do the incrementals even do that?

It's also quite possible that I don't know enough about what and why it recompiles, so my thinking may be completely wrong-headed. I'm an old Unix kernel hacker, and Things Are Different Now.

I don't tick the box to clear caches for the incrementals, and I've occasionally gotten a smaller number of optimized apps, but all 170+ seems excessive, and this is taking much longer than actually flashing the update.

Yes, I know, always asking for more.

The incrementals are apparently working very well.
[Nook Color Android Development] meklord:
The optimization that it shows after an update is the dalvik cache being rebuilt for all apps, including system. The update script that runs during flashing clears the cache, which is why it always rebuilds after a new update.
[Nook Color Android Development] lorddunlow:
I did contact the developer of DataSync and sent him some logs, but I thought that after another program had problems syncing from (but not to) my Nook that it may be ROM related. I'll contact the ComicRack dev as well. I hadn't seen any comments on Google Play from stock ICS users having the same problems, but that doesn't mean anything, I know.
[Nook Color Android Development] gambit07:
Hey guys haven't been around here in a while, what's the status of OpenGL? Any advancement?
[Nook Color Android Development] b.roid:
i see it getting most the downloads, but don't hear much talk on it
[Nook Color Android Development] lorddunlow:
I switched to the opengl version about a week ago, and have downloaded every nightly since. Chrome worked for me without any crashes at all, so far (even in the settings), so that makes me happy. Youtube will now play videos, but only the low quality (HD says there was an error playing the video), but it's pretty choppy. the home (I use Apex) is much smoother than on the other builds. Other than that, no big issues except for a once daily freeze that needs a hard reset (although this happened on the non-opengl build as well) - that did not occur on the samiam303 builds.

Truly, my only complaint is the wifi sync issue I mentioned above that may be app related. Either way, I hope for it to be fixed soon.
[Nook Color Android Development] mateorod:
My sync (email, Voice et al) is inconsistent as well. Sometimes new messages show up in the notification bar, other times I have to open the apps and manually check the messages. Please report back if you fix it. I have been having the issue for weeks while flashing every night.

Could be non-rom related, I haven't had the time to uninstall and reinstall app by app. That's why I haven't said anything before now.
[Nook Color Android Development] nicatronTg:
So would you say that it's better or worse with OpenGL?
[Nook Color Android Development] leapinlar:
I did prepare a revision to the verygreen SD installer script to now recognize the new pending standard name of cm- at the beginning of nightlies. I also added the new Goo Manager prefix of diff_. Zip install files starting with either of those will install in the new script I prepared. Any install zip starting with update- will also continue to install to provide backward compatibility. You can get the modified scripts at my post here. If you would prefer not to update to my new script, you must make sure any install zip file is named with update- at the beginning of the file so that the existing script can recognize it.
[Nook Color Android Development] lorddunlow:
Overall better.
[Nook Color Android Development] riceboyler:
I know I must be missing something obvious, but I'm unable to connect to any WPA2 Secured Wi-Fi. I've reflashed 3 different recent builds (0508, 0509, 0510 all non-OpenGL) with no avail. I was having no issues in CM7.2, and I have previously run ICS builds on my NC without this issue, so I'm wondering what's up.

Am I missing an easy fix?

UPDATE: Never mind, I'm an idiot and didn't do the typical AdHoc fix. Working fine now. Thanks for including GooManager eyeballer!
[Nook Color Android Development] incubus26jc:
Does the Grid Size not work or something? I hate that there is so much space at the top and bottom of the screen that i cant use. If i change the grid size it doesnt seem to do anything. Or the vertical and horizontal padding.
[Nook Color Android Development] ganovim:
update-softkey-240dpi etc

Am running the Latest CM9 with Gapps on sd, and am trying to get it to run at 240dpi, but the launcher fails and I cannot see the bottom softkeys.

I tried the updated script, but to no evail.

Have never had any issues with 240 dpi on CM7.

Why is it so hard to set 240 on ICS?

160 is too small for my old eyes.
[Nook Color Android Development] leapinlar:
It has to do with the tablet gui vs the phone gui. It is all explained in my tips thread and a solution is given so you can have 240dpi and soft navigation keys. Look here:

http://xdaforums.com/showthread.php?p=25355850
[Nook Color Android Development] ganovim:
update-softkey-240dpi-5-06-Rev16.zip

I have installed your	update-softkey-240dpi-5-06-Rev16.zip to the

eyeballer latest, but that does not seem to work.

It did work on an older eyeballer version.

Thanks for everything you do.