I am running CM7 and installed Mint from the market. When I launch it, it's scaled for a phone (i.e. it doesn't fill the screen). However when I was getting my feet wet with the SD bootable Froyo, I installed Mint from the market and it scaled to use the entire screen.
Has anyone encountered this or does anyone have any suggestions on how to correct this?
Note: I have uninstalled\reinstalled and nothing has changed.
Thanks for the help.
Related
i haven't come across anyone experiencing anything quite like this, even after searching the dev forums. after locking my screen, everything goes black, just like it should, but everytime, I'll look at the screen a few minutes laterr to find that the screen is powered on, but onky displaying black. its not a huge problem, but it eats battery. Has anyone found a solution for this problem or even experienced it?
Im using regular nookie froyo 0.6.8 (3/18) flashed to an 8gb sdcard, stock kernels and everything
Just updated to v1.2.0 and re-rooted, but now I have a strange problem. I tried searching these forums, and The Google, but couldn't find anything helpful.
When you click in a text field (e.g., the search box, or the address bar of the browser), the keyboard will pop-up for about 1/2 second, and then minimize again. You can do this repeatedly with the same result - the keyboard just won't stay open.
I've tried rebooting, and even installing a different keyboard (can't get them to appear as an option in NCTools).
Has anyone else run into this? Were you able to fix it?
This used to happen to me when I used a Archos 28 "tablet". It was because there wasn't enough RAM most of the time, so it would close the keyboard to make more.
I doubt that's the case for the Nook Color, though. I've never had a problem with memory on these things.
I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App
ninpo said:
I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Did you do anything to resolve it, or just live with it?
I just live with it, simply changing the angle seems to solve it, that's a simple enough fix for me.
Sent from my NookColor using XDA Premium App
FYI for anyone that runs into this thread later:
There must have been some glitch in the rooting process that screwed up the keyboard. I ended up doing the whole process over again by restoring back to stock 1.1, updating to 1.2, and re-rooting. Everything works like a charm now.
Incidentally, the stock/update/root process is a lot easier the second time you do it.
Hi, I have the exact issue, anyone knows where I can download 1.1 rom or 1.01 rom? I tried all 1.2, 1.3, 1.4.1, they all have the same issue. Thanks.
Every time before install new ROM, I formatted system, data, and cache, but seems still not totally formatted, cause 1, the keyboard part still mess up, now even cm7 on emmc has the issue. 2, the wifi connection still saved because it auto connects to my network every time flashed. Any idea? Thanks.
Having a major issue here with my NC. Running CM 7.1 and I'm getting random hangups during normal use. The touchscreen becomes completely unresponsive, and I can't turn the display on or off. If I'm listening to music, however, the music continues to play. The only way to fix it is to reboot the NC. Has anyone heard of this and can offer me a fix?
Thanks in advance
oriz
Is it an SD card install? If so what is the brand of your card.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Yes, I had the exact same problem with a new install on emmc, and uninstalling Beautiful Widgets on the advice of another thread I found here completely solved the problem. I had forgotten that BW did the same thing to my Incredible when I tried it a long time ago. If you don't have BW installed then take this as a warning not too
Very interesting...
I've had the exact same problem myself for awhile now, and couldn't figure out the cause. I even wiped the Nook and reflashed CM7.1, but the problem still popped up once and awhile.
I'm also using Beautiful Widgets. I think we have a pattern developing here. Can the OP confirm/deny he has BW installed?
Beautiful Widgets messed me up too...hung the hell out of my nook color. They even know of the issue and did nothing about it. Got it on Amazon as a paid app.
Read through the "sluggish" thread and did not see my issue mentioned and thatthread seems to have become sidetracked with benchmarks and game responsiveness issues.
I am running stock nook rom, rooted and with sideloading enabled. I also use GOlauncher as opposed to the nook launcher.
What i have noticed is that after 2 to 3 weeks of use the tablet slowly starts to get slow and unresponsive. Dolphin takes time to open, and pages scroll very very slowly. Sometimes they will not scroll at all, even though theyare fully loaded and rendered. Scrolling is also noticeably slow and unresponsive in the engadget app. It is not smooth, but jerky, ifit scrolls at all. Rebooting does not have any effect.
The first time this happened i did bring the free space down to about 300meg. After reading other posts here i decided that was the issue, backed up and started allthe way over from scratch! The issue went away. I re-installed everything, got it running clean and smooth and set up just how i like it. I then took a cwm backup and put it insafe place. Fast forward 3 more weeks and i was back to slow scrolling and unresponsiveness again. At no time in that 3 weeks did i drop below 8 gig free, so i know that is not the issue.
Here is where it gets a little strange. Today, i did a full backup with titanium, then a restore from my fully config and SMOOTH cwm backup. I then did a restore all appps and system data from the titanium i made earlier in the day. I am back to smooth and responsive. This tells me there is something that is getting corrupted or not released, even with a reboot. Anyone have any ideas on what to try next time other than a restore from cwm and a reload from titanium?
I had the same issues with stock 2.1. Besides the slow game loading and random stutter for games, the device would slowly start to accumulate to slow for everything. I would like to test with 10.1 as my native stock OS, rather than 2.1.
I had a similar experience. Even after disabling nook sync apps and making tweaks, stock would eventually slow down. Something about stock 2.1 just doesn't manage its memory/cache properly.
This isn't the solution you may want, but I'd recommend trying emmc Cm10.1. Its plain, but its virtually bug free and hasn't crashed on me yet.
This isn't the solution you may want said:
I've been rooting and bootloader unlocking Android for about 3 years now and this has to be the easiest tablet to put CM 10.1 on with the latest tools. It's actually easier than my Nexus 7 when it first came out. My hair actually turned grey when I was unlocking my Note 2 bootloader. I wish every Android device was just as easy as the Nook HD+. I think part of the confusion is that in the beginning you had one method (running CM off sd card) and you now have the more current method (replacing Rom which is the most common). The development area needs to be cleaned up better because it does look confusing. I've only been a Nook HD+ owner for 24 hours and I have made my custom micro SD card, installed CM 10.1, reverted back to stock with no backup (needed to return for a bright pixel in the middle of the display), repeated process again with new tablet and made proper backups. Sounds like a lot but this is nothing compared to what I've been through.
Click to expand...
Click to collapse
Seems to be because B&N has trim disabled:
http://blog.davidron.com/2013/10/fixing-lag-on-barnes-and-noble-nook-hd.html
Hey, so I know that this is pretty much impossible, but has anyone here had any luck in running pokemon go on their Nook HD?
I've tried multiple times through various means, I'm also running the latest Nightly cyanogen mod build (11).
I've tried using swap to get some more virtual ram, I've also tried changing the screen resolution. Even though I was able to catch a few pokemon, for the most part the app would simply constantly crash on me and force me to do a full reboot.
Has anyone had any luck with it?