Related
LCD density change is making our HD2 more pretty looking, but it will cause many applications and games to malfunction or have messy GUI.
I found in this thread a possible solution for this problem, which is disabling the compatibility mode in your system.
Just open the "Spare parts" application and uncheck the "Compatibility mode" option. This may need a reboot.
I have tested most gameloft games and some applications after doing this and they are working fine - like Asphalt and root explorer-.
Some of the games and applications didn't work fine like : Shoot U!.
Up for this! I've also tried to uncheck "comp mode" in spare parts but nothing changes... Splinter Cell Conviction and 2Players Reactor are still not working I mean, they have a messy graphics...
Why do some roms look's bad after change density in build.props? I do not mean comaplibity in spare parts,it's unchek. It seems to me that i must change some other entry to keep proportions. Maybe a small hint from some dev's?
Great stuff, thanks!
this has been known forever. it is stated in the FAQ'S of every build that has other than stock density. reboot isn't optional. you have to do it for changes to take effect. facepalm
Sent from my HTC HD2 using XDA Premium App
wow. thanks i will definitely check this out.
Mine is
Performance
Min/Max 1.2 ghz
Auto dectect
Whats yours?
Really auto detect? After every kernel dev says that auto detect isn't stable?
Really?
what should i put?
RacerXFD said:
Really auto detect? After every kernel dev says that auto detect isn't stable?
Really?
Click to expand...
Click to collapse
???
you have to use auto-detect for setcpu to detect your availble clock speeds
on-demand is BROKEN
performance will drain your battery abnormally
running at 100 min / whatever max on conservative is the most stable option for this device at the current time
Leave the advanced settings alone also?
jt1134 said:
you have to use auto-detect for setcpu to detect your availble clock speeds
Click to expand...
Click to collapse
not to contradict, but you dont have to use it, you can use the setCPU.txt file and i recommend it
here is the one i use currently with the D02 1250LV kernel, it is nothing more than a simple text file which tells the setCPU app what are valid steppings/scaling so it cannot auto-detect incorrectly as it often does
http://dl.dropbox.com/u/12311939/setcpu.txt
all you have to do is edit it to the steps that match the kernel you load and drop it in the root of the sd card, then go into setCPU, hit softmenu to go to device selection, scroll down and choose custom or manual...i forget what its called...then scroll down to the bottom and tell it to use the setcpu.txt file option and restart....done, no more problems at boot with setCPU
I only use performance when benchmarking. I use on-demand day to day. Set to 1250 max 100 min. I actually read the entire setCPU dev page, I suggest you do also, keeping in mind the limitations of the kernel you choose to load. I do not use on-demand scaling. I do not use profiles either. I do however, after testing my own device, use "set at boot". Two things on that. 1. setCPU now has a safe mode feature to get out of a problem and 2. I also use the setcpu.txt option instead of auto-detect which is hit or miss. Using the setcpu.txt file method (be sure to go to device selection and choose the bottom custom option) setCPU cannot accidentally set itself to the wrong frequency, it gets it's allowed steppings from the file you create.
if you read the setCPU dev page you (not directed at you jt ) will learn all of this and also about the advanced settings....but they work fine as they are for my device/kernel/usage
jamesnmandy said:
not to contradict, but you dont have to use it, you can use the setCPU.txt file and i recommend it
here is the one i use currently with the D02 1250LV kernel, it is nothing more than a simple text file which tells the setCPU app what are valid steppings/scaling so it cannot auto-detect incorrectly as it often does
http://dl.dropbox.com/u/12311939/setcpu.txt
all you have to do is edit it to the steps that match the kernel you load and drop it in the root of the sd card, then go into setCPU, hit softmenu to go to device selection, scroll down and choose custom or manual...i forget what its called...then scroll down to the bottom and tell it to use the setcpu.txt file option and restart....done, no more problems at boot with setCPU
I only use performance when benchmarking. I use on-demand day to day. Set to 1250 max 100 min. I actually read the entire setCPU dev page, I suggest you do also, keeping in mind the limitations of the kernel you choose to load. I do not use on-demand scaling. I do not use profiles either. I do however, after testing my own device, use "set at boot". Two things on that. 1. setCPU now has a safe mode feature to get out of a problem and 2. I also use the setcpu.txt option instead of auto-detect which is hit or miss. Using the setcpu.txt file method (be sure to go to device selection and choose the bottom custom option) setCPU cannot accidentally set itself to the wrong frequency, it gets it's allowed steppings from the file you create.
if you read the setCPU dev page you (not directed at you jt ) will learn all of this and also about the advanced settings....but they work fine as they are for my device/kernel/usage
Click to expand...
Click to collapse
Contradict much?
Nice find there james
Im wondering what would happen if you didnt match the increments in your txt file to the kernels native ones?
Lol, I only speak of what I know to be true you guys have far more knowledge but I tested this on my own device and also used it on the ally I had so I know its good
Sent from my SCH-I500 using XDA App
Id say probably either fc or nothing. Either it would try to hit something it cant and fc or it would discard the step, but then the large jump sau from 200 to 600 skipping 400 may cause an issue
Sent from my SCH-I500 using XDA App
Well, if I can keep mine running stable for a couple of days, with no "permasleeps" then I will give start on boot a try. So far I'm having excellent luck with 1100 max 100 min with conservative. Set to auto, it brought the right figures up immediately. So far the thing is really running great with the 1100 LV kernal and the settings I mentioned above. I'm sure my quadrant will be lower than 1200, but for some reason the 1200 kernal was only stable when I was placing load on the device, actually using it. When it was idle the screen would "permasleep". Very odd. Stress testing on the 1200 LV kernal threw no errors, but I still had idle issues.
SirKronan said:
Well, if I can keep mine running stable for a couple of days, with no "permasleeps" then I will give start on boot a try. So far I'm having excellent luck with 1100 max 100 min with conservative. Set to auto, it brought the right figures up immediately. So far the thing is really running great with the 1100 LV kernal and the settings I mentioned above. I'm sure my quadrant will be lower than 1200, but for some reason the 1200 kernal was only stable when I was placing load on the device, actually using it. When it was idle the screen would "permasleep". Very odd. Stress testing on the 1200 LV kernal threw no errors, but I still had idle issues.
Click to expand...
Click to collapse
Maybe check out the 1200SV as well and/or jt's 1200. Heck I tried them all myself at least briefly
saps said:
Maybe check out the 1200SV as well and/or jt's 1200. Heck I tried them all myself at least briefly
Click to expand...
Click to collapse
The SV is working good so far, but where do you get jt's?
SirKronan said:
The SV is working good so far, but where do you get jt's?
Click to expand...
Click to collapse
Right here: http://forum.xda-developers.com/showthread.php?t=804317
Sorry if it is a noob question but
I have the jt's voodoo kernel and just restored my setcpu from the titanium back up...
the max that it gives me is only 1000000....
I thought It should change to 1200000
how can I change it?
if not what should I do to OC this bad boy?
btw I Used the recommended speed...
Thanks
Zirabius said:
Sorry if it is a noob question but
I have the jt's voodoo kernel and just restored my setcpu from the titanium back up...
the max that it gives me is only 1000000....
I thought It should change to 1200000
how can I change it?
if not what should I do to OC this bad boy?
btw I Used the recommended speed...
Thanks
Click to expand...
Click to collapse
Download the 1200 w/ boot animation. This happened to me last night when updating my wife's fascinate. I first downloaded the one without boot animation, which was fine, but only would clock to 1000 and was getting the battery not connected error. So I flashed the 1200 w/boot animation and fixed everything.
mackeydesigns said:
Download the 1200 w/ boot animation. This happened to me last night when updating my wife's fascinate. I first downloaded the one without boot animation, which was fine, but only would clock to 1000 and was getting the battery not connected error. So I flashed the 1200 w/boot animation and fixed everything.
Click to expand...
Click to collapse
Thanks works great now
Sent from my SCH-I500 using XDA App
mackeydesigns said:
Download the 1200 w/ boot animation. This happened to me last night when updating my wife's fascinate. I first downloaded the one without boot animation, which was fine, but only would clock to 1000 and was getting the battery not connected error. So I flashed the 1200 w/boot animation and fixed everything.
Click to expand...
Click to collapse
I just flashed my Fascinate with the 1200 w/ boot animation and then SetCPU from the market but SetCPU only allows my Max slider to 528MHz??? what did i do wrong?
Sorry for another noob question.
rickys08 said:
I just flashed my Fascinate with the 1200 w/ boot animation and then SetCPU from the market but SetCPU only allows my Max slider to 528MHz??? what did i do wrong?
Sorry for another noob question.
Click to expand...
Click to collapse
Think about it for a second... Has it sunk in yet? Didn't think so.
You changed speeds so you need to redetect your speed. Either do that or uninstall the app and reinstall it.
Sent from my SCH-I500 using XDA App
rickys08 said:
I just flashed my Fascinate with the 1200 w/ boot animation and then SetCPU from the market but SetCPU only allows my Max slider to 528MHz??? what did i do wrong?
Sorry for another noob question.
Click to expand...
Click to collapse
that happend too me too man,
what I did was I went to the menu and did an auto speed detect...
and the problem solved! its been running smoothly ever since
Has anyone managed to get N64oid 2.0 working on their Nook Color? I'm running CM7 and the old version, 1.1.4 or whatever it happened to be, worked fine. However now I can open up the load rom menu and whenever I select one it locks up the whole device, I have to hard reset it to do anything. If I change the graphics engine option to the old one, whenever I choose a game, it just reloads the rom list. Has anyone had any luck with this or am I out of luck for now?
Same for me
I thought i was doing something wrong, guess its not just me.
I would love to know as well if there is some kind of fix or workaround for this.
Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Shissu said:
Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Click to expand...
Click to collapse
The initial ghosting occurs (at least in fastmode2.apk) because the apk does not perform 1 full screen refresh after the start (yet).
Try to lock and than unlock the device after starting fastmode2.apk.
The other reason may be that you have 'NoRefresh' installed and it autostarts on boot.
Never use both NoRefresh and FastMode at the same time.Kill one or another using TaskXP (or similar apk).
Edit:
Yeah. I have checked it. Applying 1 full refresh helps a lot. (you can also try do display a white full screen image to get the same result).
If you have time you can edit the source of fastmode2.apk. I won't do this during this week for sure.
osowiecki said:
Applying 1 full refresh DOES NOT helped me.
Click to expand...
Click to collapse
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Mnurlan said:
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Click to expand...
Click to collapse
What I meant by performing a 1 full refresh :
1. you can see extensive ghosting
2. I push the lock button, the screen blinks (full refresh)
3. After unlocking there is no (a little) ghosting effect.
It would be nice to force fullscreen refresh after fast mode gets activated.
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Mnurlan said:
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
"lurk moar"
stock image 1.1 for CWM
https://code.google.com/p/nst-recovery/downloads/detail?name=nook_1_1_update_cwm.zip&can=2&q=
Also..why not use NoRefresh then?
Both modes work on kernel v166.
Mnurlan said:
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
1.1.2 FW straight from B&N
Also..why not use NoRefresh then?
Click to expand...
Click to collapse
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Mnurlan said:
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Click to expand...
Click to collapse
What do you mean by "no effect"?
You should run NoRefresh once (it starts it's deamon), then you run in the second time to get results.
By default the contrast options are set to "auto". Go to "NoRefresh Settings"->"Contrast Settings" and select "appear always".
Add shortcut to NoRefresh to 'quicknav' bar or any other place that you can always reach on the screen.
NoRefresh works only within the application that it was started with. When you change the focus to another apk, it stops.
If you are on stock kernel and 'NoRefreshToggle-debug2.apk' does not work, that means you don't have FW 1.2.1 installed.
Seems like I've now got a bricked device, neither Noogie, nor CWM can help - my PC doesn't "see" my NST anymore and I can't replace the uImage, the NST itself is working now, but this means I will not be able even to restore it to a saved image:crying:
A day later I've found out that for some reason my desktop PC ("floortop") refuses to "recognize" my NST (although "sees" it alright without Noogie or CWM), then I have managed to replace uImage on my NST using my son's laptop, yet FastMode is not working, same as NoRefresh, FW 1.2.1 (I'm positive), FastMode2 works fine but resulting view renders it useless.
Update: 26.04.2013 - NoRefresh is working, but the resulting resolution renders it also almost unusable. Just delivering my SitRep, not whining. Installed kernel 166 with CWM.
dots
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
eraycr said:
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
Click to expand...
Click to collapse
Same here, try many kernels.
I thought it was normal operation of this modification. Oo
Well, I'm late to the party, having generated an apparently useless post here. But I agree with you all who are underwhelmed with the screen appearance using either of these two mods. I like the sprightly Android performance of the NST in FastMode, but there really is a lot of visual "noise" on the screen. NoRefresh is even worse on my Nook. I can hardly get an image at the beginning, the screen is almost an all white overlay so the contrast buttons don't do me any good because I can't see much through the white film (sort of like a bad cataract!). Scrolling a bit gradually brings in a fractured image and by the time the app has closed.
I've tried disabling the NoRefresh app entirely to see if FastMode would work better. No deal. Same poor image quality. Nothing like some of the YouTube videos I've seen.
FW 1.21, kernal 166.
But who knows? At least multi-touch is nice.
Pardon the rather simple problem, but I couldn't find a suitable answer.
I have an old (and functioning) rooted NST that I'd like to revamp, however I have no idea which firmware version and custom ROM is installed in there. Is there a way (via adb or app) to find out what's inside?
marcoNST said:
Pardon the rather simple problem, but I couldn't find a suitable answer.
I have an old (and functioning) rooted NST that I'd like to revamp, however I have no idea which firmware version and custom ROM is installed in there. Is there a way (via adb or app) to find out what's inside?
Click to expand...
Click to collapse
The B&N Settings app should identify the firmware number--unless that was disabled or deleted. If that does not work, put together a NookManager card and start it up. It will identify the firmware (without making any changes.
(or ask and I'll post a copy of the B&N Settings app)
A custom ROM (kernal?) would be harder to figure out. If it's overclocked (one of guevor's kernals?) some kind of CPU governor app (like NoFrillsCPU) would show that it can run faster than 800 MHz. Otherwise, if the status bar display is normal it's probably not the 1337 ROM and could be running some other kernal that is not overclocked. Does it run either NoRefresh or FastMode? Only one kernal (166) runs both and the overclocked kernals typically run FastMode, while those that are not(except 166) typically run NoRefresh.
Probably something more subtle, but I don't know what it might be.
Hi @nmyshkin
Thanks for your help!
I've downloaded and just installed 166 kernel (over whatever was in there before) and NoRefresh, but no joy. Not working. (FastMode2 works) Checked the CPU with noFrills CPU and it runs up to 1Ghz.
Checked the FW, it is 1.2.1.
marcoNST said:
Hi @nmyshkin
Thanks for your help!
I've downloaded and just installed 166 kernel (over whatever was in there before) and NoRefresh, but no joy. Not working. (FastMode2 works) Checked the CPU with noFrills CPU and it runs up to 1Ghz.
Checked the FW, it is 1.2.1.
Click to expand...
Click to collapse
Did you use this NoRefresh: https://github.com/marcelogp/NoRefreshToggle/downloads, i.e., the debug2 version?
I did.
I have a very erratic behaviour, I have 2 different behaviours:
1. when I press "Norefresh", the screen gets a grey-ish layer that make all the app icons in ReLaunch look blur and there is no fast refresh.
2. when I press "NoRefresh", the screen turns into "no refresh" mode, but it disappears at the first scroll down (or up)
FastMode works OK though.
marcoNST said:
I did.
I have a very erratic behaviour, I have 2 different behaviours:
1. when I press "Norefresh", the screen gets a grey-ish layer that make all the app icons in ReLaunch look blur and there is no fast refresh.
2. when I press "NoRefresh", the screen turns into "no refresh" mode, but it disappears at the first scroll down (or up)
FastMode works OK though.
Click to expand...
Click to collapse
What you describe sounds familiar. I think at one time I probably used kernal 166 and was totally puzzled by all the oohs-and-aahs over NoRefresh. I could never get it to display anything useful. My suggestion to you was based on this recent exchange: https://forum.xda-developers.com/nook-touch/general/fastmode-norefresh-nook-simple-touch-t3868484 but now that I have gone back to it I see the guy was running FW 1.1.2. So whether the issue is with FW 1.2.1 or with the debug2 version of NoRefresh, I'm not sure. So, my bad.
FWIW, having run FastMode for a long time before I completely redid my NST, and now having a working NoRefresh instead (with FW 1.2.2), for me there is no contest between the two for text. The dithering and ghosting in FastMode is not good for reading, IMO. I might go so far as to say that NoRefresh is even better at video because I feel the limited contrast options are better than the ghosting of FastMode. But that's me. It's an individual thing and we each use our devices differently.