yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] deboyz1014:
My usual routine for updating is

1. Install Zip Update

2. Wipe Cache

3. Wipe Dalvik Cache

4. Fix Permission

5. Reboot

Havent ran into any issue doing that up until now with 202/203 amazon app FC. I did the fix permission in rom manager and through the recovery menu. Is there a problem with the way I do update or is there another step that I'm missing?
[Nook Color Android Development] swaaye:
My biggest peeve with the Nook Color is the OS. The stock browser in particular because of how terribly slow it is due to no hardware acceleration. The Iconia A100 has Honeycomb and the Tegra 2 and the combination of the faster CPU and the accelerated browser make for vastly superior browsing.

Opera Mobile is fast but it is nowhere near as friendly to use as Dolphin HD. Will check out Firefox Mobile nightly.

I'm hoping that Ice Cream Sandwich works on Nook Color as that should bring the better stock browser and as a result a hardware accelerated Dolphin as in Honeycomb.

I think a nice tablet would be a 7" 4:3 with an IPS LCD, Tegra 3, 1-2GB RAM and Ice Cream Sandwich. :)
[Nook Color Android Development] Colchiro:
I was referring to clearing the airplane entry from DB in NC Tweaks, not toggling it.

I agree, fixing it in GB would fix it for all devices and a better option.
[Nook Color Android Development] fattire:
It's weird but for me they have different use-cases.

At home, browsing on the couch, I find myself using the TP. The screen is bigger, the response-time is faster. But it's big drawback is that it is too heavy to hold comfortably in one hand. It's kind of like a laptop without a keyboard.

When I go out, I think the Nook is the better choice for a mobile tablet. It's smaller, lighter, and there is something good to say for the increased DPI. It's just a joy to read. It can't compete speed-wise, but the Nook isn't so slow when overclocked...

Honestly though, I find that for everyday use I use my phone most of all. It's there in my pocket and can be used for looking things up quickly. Plus 3g. But I'm sure everyone's experiences will differ-- and should my lifestyle change I'd probably find myself using one rather than another. There's no "right answer" for the ideal screen size or anything.
[Nook Color Android Development] newellj79:
If a unimpressed TP user exists who wants to off load it, pm me. I too missed out. :( That said I have been very impressed with my NC from day one, even auto-nootered. Cm7 and its devs have taken it to a level of performance that is in matched in this size portability.
[Nook Color Android Development] psychoace:
I doubt anyone in there right mind would sell it for under $200. Don't think you will get a fire sale price just because that is what they paid
[Nook Color Android Development] 12paq:
lol, that would depend on personal values in regards to profit. Don't ya think?
[Nook Color Android Development] psychoace:
True, you might find someone who is super sweet and nice and who could care less about money. If you do find that person on the internet then you are probably getting scammed.

Dal, how does Firefox nightly run overall on the nook for you? Im running the latest official release and this thing just rapes my tablet. I admit im on a slow connection but to take more then 3 minutes to load a page is ridiculous. Then it took me 5 minutes to close out the app and get my system to run normal again. Opera Mobile with turbo off runs circles around this thing.
[Nook Color Android Development] swaaye:
I tried the FF Nightly today and am still not going to be switching to that browser. It's a lot better than v4 was but they aren't there yet with polish and performance. Opera Mobile is considerably more refined and speedy, but of course missing a lot of features.

---------- Post added at 09:27 PM ---------- Previous post was at 09:25 PM ----------

That's not true if you look at the Iconia A100. It's unfortunate that they went cheap on the LCD though.

There are going to be a bunch of new 7" tablets coming though. It seems to be becoming the new hot thing thanks to Honeycomb 3.2 being available.
[Nook Color Android Development] BitingChaos:
Can anyone explain this to me? I can play 3D games on my Nook Color, a G1, my sister's Droid, etc - but something like looking at a website seems to occur at single-digit framerates, with sluggish, slow, choppy animations. This is with mature, 2011 code.

Meanwhile, an iPhone using 2007 components running at half the speed of my Nook Color and with a quarter of the RAM of my Nook Color will have an accelerated, smooth interface.

Will Android never have an accelerated interface on some devices? Why not?
[Nook Color Android Development] psychoace:
Stock browser is just not well made for 2.3 and below. Honeycomb is accelerated and so will ice cream I assume. Still nook has some slow ram and a high res screen. Most low res phones with the same specs as ours can breeze through a web page with the stock browser. Otherwise opera Mobile is a good alternative if you are looking for speed over features.
[Nook Color Android Development] koopakid08:
Get a different browser. The stock browser is the IE6 of Android. I use a mix of dolphin HD and opera.
[Nook Color Android Development] jeremyshaw:
Archos recently launched an 8" dual core (ti?) @ 4:3

Not the same, but a good step.
[Nook Color Android Development] dalingrin:
Scrolling in the firefox nightly is faster than the stock browser on most websites and doesn't even have hardware acceleration. Firefox mobile 10 should add hardware accel.

In terms of speed comparisons between Iconia A100 and the Nook Color. There's really no comparison. The Nook Color was slow and old when it came out nearly a year ago. Its considerably slower than an OMAP3630, even when overclocked, due to the hobbled memory. Memory bandwidth is a limiting factor in Android for scrolling and overall smoothness and this is the Nook Color's #1 weakness. This is true for phones but with the Nook it is exacerbated because of the resolution increase.

This is not to mention the fact that we have also have a GPU that wasn't particularly fast when the Droid 1 was released 2 years ago =P
[Nook Color Android Development] koopakid08:
Very true, but lets not forget that the Nook costs $100 less at retail and even less if you get it on one of these sales for $180.

That being said I'm really hoping for an upgrade soon.
[Nook Color Android Development] khaytsus:
Of course it'd look fine, you have your NC set to phone DPI.. I prefer my tablet to not have gigantic elements, I want them the same size as my phone, and to use the extra screen space.

I assume you don't realize that Dolphin is just a new GUI on top of the stock browser rendering engine? IE: Performance in that regard will be the same... :rolleyes:
[Nook Color Android Development] koopakid08:
Yes, that is why I use opera when I need speed. I just like dolphins UI a lot better.
[Nook Color Android Development] andyrubin1:
Is the unresponsiveness of the NC related to the speed of its CPU and GPU? I would like to do freehand annotation but it's not possible on the NC at all.

Maybe when Kindle Fire got CM and if it has better screen...

Or NC2... Maybe...

BTW 160 dpi just doesn't cut it... But I think we need to wait for ICS to have a better solution...
[Nook Color Android Development] tsddave:
I think you guys must have different nooks to me because my nook even without an overclock is far from unresponsive.The only thing that slows mine down sometimes is my wireless internet.

Ive compared my nooks speed with other higher priced tablets and frankly its not that much slower and usually has a far better display.For the money you cannot grumble!
[Nook Color Android Development] swaaye:
It depends heavily on what you're doing. For web the Nook Color's stock browser is really bad. For example, posting on forums is extremely frustrating because each letter you type may not show up for a second or so sometimes.

Opera Mobile is much better but it is really sparse for features and the Opera folks are simply unwilling to expand it much. They seem to have a "keep it simple" approach to it. It took months to just get the ability to easily change user agent.

Considering how fast Opera Mobile is, I'm hoping that a future Android 4 release can make the stock browser w/ Dolphin a good experience. But it would of course be nice to see Firefox come along finally too. They call these nightlies v9 but I'm more inclined to call it v0.9.

When you say the RAM is gimpy are you referring to a 16-bit memory bus? Tegra 2 is 32-bit AFAIK.
[Nook Color Android Development] majorpay:
I believe I am on 202 now of the nightlies for CM7 and have noticed that things are starting to drop off of the Market. On one ninety something, for the first time in my Nook's history, I had Netflix in the market. As of 202, I no longer have access to it in the market, nor do I even have access to Kindle anymore. I side-loaded these of course, but what's up with that?

Is it the new market locking out devices more? And why would companies that rely on our money be interested in locking us out of their apps?

edit: is the Kindle initiative part of the greater plan to push the Fire? If so, and the Fire is subsidized in the interest of selling product, why the hell would they think that was a smart business move?
[Nook Color Android Development] nismopc:
That is odd. My Netflix just updated to the new rotating version. I am now on 203 I believe. Whatever was the last one like two days ago...
[Nook Color Android Development] majorpay:
I will have to try 203. I normally don't take the latest and the greatest until other guinea pigs have been through the wringer :D
[Nook Color Android Development] ianPhillips1:
You can always uninstall the update, come on live on the fringe ;) usually its a win. <-----just cursed myself

Ian

sent from my ereader
[Nook Color Android Development] jameshmiller:
Have you tried clearing data for market? I haven't had to do that in a while, but it may be worth a try.
[Nook Color Android Development] newellj79:
Nope.

10 characters
[Nook Color Android Development] Artood2s:
Does the SetCPU profiles problem occur with CPUTuner as well? I've been using it with the profiles on with no noticeable issues. I'll monitor the CPU to make sure it's not maxing out.
[Nook Color Android Development] jkurl:
In v11 change the LCD density to either 168.33333 or 169.33333. i have used both and they both work really well. That seems to be the sweet spot right now for alot of the apps.
[Nook Color Android Development] philburkhardt:
First off, I applaud your thoroughness!

Just a quick note...

When you reboot after wiping chache and dalvik, you should reboot back into recovery. It is my understanding that dalvik is rebuilt on first boot. So if you reboot into android and go through ROM Manager, you would need to wipe dalvik again.

Somebody correct me if I am wrong, but I am pretty sure that is how it works.
[Nook Color Android Development] buffalosolja42:
Yeah I set it to 160 which is the default for the nook right? And my market and everything works out of box... so I may just run v11 for a while given the screen density being set to its native state.
[Nook Color Android Development] faceman66:
...wiped /cache

...flashed nightly 12

...flashed oc kernel

-booted fine

-market/MyApps ok without any fix (yet)

-some apps not upsizing that used to (unblock, tic tic)

-setCPU profiles still pegs cpu

Overall, nothing major except maybe not having to adjust lcd density for market to work steady

Edit - after reboot:

-market opens, but no carousel or MyApps

--Dalingrins work around clearing cache and framework data did NOT fix

--changing lcd density to 161 and rebooting: does fix (so now the issue seems to be a pure lcd density issue and not cache/data/etc) ?

still playing around.
[Nook Color Android Development] Artood2s:
Just an update on my earlier question.

Using CPU Tuner with the profiles on, the CPU seems to scale just fine. I used Process Monitor and the most CPU usage I could get at any given time was ~50% while playing Gun Bros (40% with Angry Birds). As soon as I exited the app, CPU usage came back down to normal. It also let me visualize the frequency changes, and it seems like everything is in order. I'll continue monitoring, but I think it is safe to use CPU Tuner with the profiles on.

P.S. Can someone let me know in which instances SetCPU pegs the processor at max? I'd like to see if I can replicate it with CPU Tuner. Thanks.
[Nook Color Android Development] Snyperx:
Hey folks I hope you all know you do not need to use any of the Market CPU adjustment apps to OC. Cyanogen has it built into it. Go to Cyanogen Settings and its under Performance.
[Nook Color Android Development] buffnutz1:
But there's no profiles. I like to underclock to 200 when the screens off.
[Nook Color Android Development] Artood2s:
Yes, I've noticed that, but having different profiles for "Screen off" and "Low Battery" is nice. That being said, since I just downloaded the process monitor and tested for 30 mins, I'm not sure yet it it is switching over to the low batt setting. I'll keep watching it.
[Nook Color Android Development] faceman66:
Sure... with setCPU, all you have to do is Enable the profiles and wait about 2-5 seconds, the cpu ramps up and stays. don't have to DO anything, odd.

It's not the OC ability I want, it's the profiles so I can squeeze battery life by dynamically underclocking when power isn't needed... I'm gonna try CPU Tuner out.
[Nook Color Android Development] crashdau:
Current build: v12

Customizations: None

USB Mass Storage not connecting to PC: Flashed v12 directly over v11 without wipe

Steps to reproduce the problem:

1) pull down notification bar

2) pressed 'USB Connect' notification.

4) NC jumped to USB Mass Storage screen.

5) pressed "Turn on USB storage" button

6) NC goes to "Turn off...' button few 2 - 5 seconds, reverts to home screen and SD card is prepared according to notification status bar. NC never connects to pc

Edit:

7) goto settings and turn off USB Debugging, goes to USB Mass storage screen.

8) press "Turn on..." button and NC connects. Able to view files on pc.

Describe the issue as well as you can:

USB Connect to PC issue-no longer cycling through connect/disconnect, but still does not connect to view files on SD card.....Edit: until USB deubbing is de-selected in application -> Development section. Attaching additional log files.

Relevant logs(logcat, dmesg)

logcat and dmesg attached
[Nook Color Android Development] dalingrin:
Thanks so much for using the template. I'll look into this.
[Nook Color Android Development] Paul22000:
How is the performance for you?

It's a 100% slideshow for me, about 1 fps.

Is it smooth for you in the browser, and if so, how?
[Nook Color Android Development] tony1208:


Same as u....smooth at times but when there's alot of movement its like 1 fps ....better than nothing....audio is clear though..
[Nook Color Android Development] tony1208:
I don't understand how TV show stream app works so well with video...smooth as heck on the nook but YouTube wont work...or works like at 1fps haha....I dunno ....I'm no dev so I'm clueless haha..
[Nook Color Android Development] donballz:
Certain apps like throttle copter rendered to the full screen for nightly 8 but not on 11 or 12. Now it renders phone size to part of the screen. Is there a way to adjust settnigs or build.prop to fix this? Thanks.
[Nook Color Android Development] faceman66:
ok, it's not just me. I haven't played games much the last few days, but I swore that some of my apps that used to size with an earlier nightly didn't anymore... it amazes me how much lcd density seems to be causing disruptions.
[Nook Color Android Development] elwood1229:
I am not able to connect my NC CM7 through my Droid 1 Adhoc. I have not used the adhoc patch for other roms and have tried using the Wireless Tether and Barnacle apps. Wireless Tether will not connect at all while Barnacle seems to connect but I can not get to the internet. Any suggestions?

Note: I apologize if this is not the correct thread for this question. I did search this thread on this topic and while I found other mentions of the problem, I did not come across a solution.
[Nook Color Android Development] bonobomidwest:
Honestly guys everything works perfectly for me at 169.33333 . I have cm7 running with no tweaks. Each update I have flashed over the previous one. I skipped from v5 to v8. beyond that i have flashed OC both with and without reboots inbetween.

My understanding is that 169.33333 is the stock setting. Am I missing something cm7 devs? Is there a reason not to make this the default for build.prop? Just asking to learn, not to criticise. :)
[Nook Color Android Development] 12paq:
Exactly, go for it! The fun is in the hackery of it all.

At $200 bucks, the dual core of the Amazonian Fire seems like deving fun, we'll see..
[Nook Color Android Development] koopakid08:
Good luck ;) No SD slot limits space by a ton and how is clockwork going to work with one hardware button?

It will be interesting to say the least.
[Nook Color Android Development] inportb:
Hm... we might just have to try TWRP 2.0!
[Nook Color Android Development] koopakid08:
That looks sick. Now clockwork seems even more boring. Lol
[Nook Color Android Development] 12paq:
Thanks, good info.

Like I said, we'll see. I have I thing about under utilized devices and having fun. No removable SD and one hardware button are large obstacles tho.
[Nook Color Android Development] psiphi:
What is upper limit to total number of apps installable?

Finished experimenting with upgrading from last stable build to nightly 200 serries... (currently on 202...)

SD card size is NOT a factor.

Number of apps on SD card is NOT a factor.

Total number of installed apps IS a factor (around 250 apps) [256 on a guess] if you have at least one app installed on the SD card. Problems start after a reboot or two... Limit seems to have started when the Kernal was first upgraded from the one in the 7.0.3 stable build.

Amazon AppMarket does not seem to like the upgrade. I uninstalled AppMarket, upgraded to latest nightly, then reinstalled fresh copy AppMarket. (Titanium restores of AppMarket seemed to make entire system unstable.) This seems to have started in the 200 series of nightlys... Have not tried 203 and above yet... (Earlier msg suggests 203 might fix this.)
[Nook Color Android Development] majorpay:
Worth a shot!
[Nook Color Android Development] BitingChaos:
I'm just use to iOS. I got my 3GS back in 2009, and it was like my interface was operating at 60FPS. Everything was accelerated and smooth. Nothing lagged. It was like night and day compared to every other device I had ever used. I hated the lag in all my other phones.

When I first used Android: a G1, then some Droid, then a Droid 2, Droid Incredible, and then my Nook Color - they all had one thing in common: interface lag. It was like 1998-2007 phones all over again. Scrolling is choppy, web pages jerked when scrolled, there was sometimes lag when typing, etc.

I just got an HP TouchPad this week, and webOS is similar to iOS in how it performs. The interface is accelerated and very smooth. It isn't as smooth as iOS, but it is still way better than anything I've experienced on Android 1.x-2.x. There is the issue of apps seeming to take forever to load on webOS compared to iOS and Android, but once they load, they work pretty smoothly.

Now, I know Android can be smooth. When I used the Asus Transformer, I was really surprised at how well the browser performed.

On my Nook, web browsing is just painful.

Opera performs better, but the interface is just horrible. At DPI <180 or something, it is OK. Once you go above a certain DPI, the interface changes to some comically huge mess of buttons that take up half the screen. I use my Nook Color at 240 DPI (good for LauncherPro, the status bar buttons, compatibility with some apps and games, etc) - and Opera is just too annoying to use at that DPI.

Using my Nook Color has just been a series of compromises.

On Launchers:

- LauncherPro is very smooth, but looks horrible at low DPI (it doesn't scale icons correctly), and has bugs drawing the App Drawer sometimes.

- ADWLauncher (and all other launchers) scale correctly with DPI, don't have any big bugs (except for Go Launcher drawing menu items *behind* the status bar), but the performance is always horrible with them. My interface is much laggier than when using LauncherPro.

On DPI:

- At 160 DPI, the Market looks better (less crowded), Opera looks fine, but some apps don't work correctly (one I use for browsing another forum), Twitter displays text with the wrong margins, some games won't work, and the status bar buttons are too tiny and close together.

- At 240 DPI, the Market overlaps text, Opera's interface is cluttered, there is no room on the status bar to show any icons. All my other apps work correctly though and the status bar buttons are easy to press.

There is no in-between I've found that works with everything. Any DPI in between and I still end up with issues from one end or other. Since I know things can work, then I know it's not the Nook Color that is the issue, it's the individual apps and even Android itself that are the problem.
[Nook Color Android Development] Gin1212:
Being use to IOS in my opinion is a lame excuse =\. I've owned Iphones and Ipod Touches in the past and sure... Some things were a bit smoother, but not to a point that I would prefer IOS over Android.

I remember with IOS I had some emulators and the only way to get to the right folder to put the roms in, was by ftping them in =\... How stupid is that?

Not a problem with android, works just like it should, drag and drop, or I can even download directly to it. IOS was fickle about downloading anything it didn't recognize =\.

To each's own I suppose.
[Nook Color Android Development] majorpay:
I'll agree that the IOS world is buttery smooth (a term that gets thrown around way too much in the Android world), and at first glimpse, it blows away any Android device.

But then you start looking at functionality and expandability (freedom), and Android is king. There really can't be a comparison in that arena.

Here's one thing we have to remember in these comparisons, however:

Nook = $200 and does everything you need it to.

iPad = $500+ and looks prettier.

Android is your Dodge pickup - great in the snow, gets you where you need to go, and is practical, but not necessarily "pretty."

IOS is your Ferrari - terrible in the snow, can't clear a speed bump, costs a fortune, but is a beautiful and powerful car.
[Nook Color Android Development] dalingrin:
Archos 80 G9 > Amazon Fire.

If I were to get another tablet for developing(I'm not) it would probably be the Archos.
[Nook Color Android Development] majorpay:
My "guess" would be that the device will not be a dev paradise. They have purposely omitted any type of external storage, and are attempting a walled garden. The purpose for this device is to be controlled by Amazon's cloud and software (think Kindle, Amazon Videos, Amazon Apps).

While all things in the Amazon world are mature and fairly nice, I would NOT buy this device with the misguided notion that they are going to make it easy for devs to get in to.
[Nook Color Android Development] 12paq:
Well, drat.

Agreed. Thanks for the input.
[Nook Color Android Development] psychoace:
Not many devices have been easy to hack. Getting root can take weeks for some phones and tablets. Just because it looks hard doesn't mean squat. The galaxy s phones looked hard to work on with its proprietary file system and lack of a full source (some drivers were not decompiled). So until someone gets there hands on it we shouldn't jump the gun
[Nook Color Android Development] majorpay:
Locked boot-loader, and an infrastructure close to RIM would be my first guess.

"Hard" can turn into "Damn near impossible" sometimes.
[Nook Color Android Development] khaytsus:
The device will be rootable. How easily it can get Market, CWM, custom ROMs, etc, is a very different question.