Related
Here's a video with ADWLauncher installed incase people didnt like the Notion Ink UI. It worked very well. I'm not too familiar with the settings in ADWLauncher, so bear with me for a bit.
I really hope the XDA community can help me getting the natural google experience back on this device. the hardware with PQ is really nice, Adam's Specific Programs run well, but UI is a bit beta still with some FC.
------------------------------------
update with two more videos
------------------------------------
another view demonstrating the gps error, google maps, and the gyroscope
and Notion Ink Adam's ability to handle online adobe flash applications (www.sumopaint.com)
-------------------------------------
I dont take credit for this, but the people at notioninkhacks.com and xda-developers have finally rooted Adam and installed the Android Market!
How is the touchscreen in terms of sensitivity? Also is there any give to the display when you press on it?
The screen seems very responsive. seems comparesble to the nexus one minus the screen issue
Sent from notion ink adam
Thanks for the walk though.
BTW, Appbrain uses official Android Market for access, so since it isn't on the Adam, it can't work.
Care to try applnet and or the other "alternate" markets?
-CC
How is the Pixel Qi in terms of brightness/evenness? Are the colors washed out enough to make you consider the LCD model? Thanks again for the walk-through!
Video looks good, it's the only video of the Adam that I've watched without wanting to throw up.
How're you liking the non-backlit Pixel Qi? Decent for everyday use? Or only in situations where LCD has problems (sunlight) or battery saving?
bemymonkey said:
Video looks good, it's the only video of the Adam that I've watched without wanting to throw up.
How're you liking the non-backlit Pixel Qi? Decent for everyday use? Or only in situations where LCD has problems (sunlight) or battery saving?
Click to expand...
Click to collapse
the non-backlit PQ is interesting. i dont know whether it's a good thing or bad thing long term, but for battery wise, it's a good thing. but i've been using it in color mode mostly. but with the PQ mode, the view angel are much better. I say it'll take a bit getting use to seeing things in b/w lol~~. It's like kindle but more responsive in a nutshell
What about in portrait mode? Saw some apps that you used in portrait, but what about like homescreen, facebook, twitter, etc. Was a bit saddened how the stock launcher seemed to be fixed to landscape.
I am impressed.......!!!!!!!!wow ..
is there any website in particular you used to download the .apk files
Sent from my Nexus One using XDA App
benyameen said:
What about in portrait mode? Saw some apps that you used in portrait, but what about like homescreen, facebook, twitter, etc. Was a bit saddened how the stock launcher seemed to be fixed to landscape.
Click to expand...
Click to collapse
ADWLauncher is not locked in landscape mode. the home screen can rotate. it resizes the icons and widgets and it's not too bad. facebook can rotate too, but it's rotates according to the app as you see it on your smartphone
posted some new videos for you guys
inspiron41 said:
ADWLauncher is not locked in landscape mode. the home screen can rotate. it resizes the icons and widgets and it's not too bad. facebook can rotate too, but it's rotates according to the app as you see it on your smartphone
Click to expand...
Click to collapse
Thanks for the reply and video.
The biggest worry I had about the Adam was that it would only be usable in landscape mode - this is clearly not the case =]
Just can't wait for the next round of open orders... Definitely buying...
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
zabaknilesh said:
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
Click to expand...
Click to collapse
i never rooted anything, but i'm following the development section carefully trying to learn as i go. i dont want to do anything to brick my device lol. i'll let you know when i figure things out
zabaknilesh said:
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
Click to expand...
Click to collapse
It is not pre-rooted but rooting is work in progress:
http://notioninkhacks.com/forums/viewtopic.php?f=29&t=345
Also NI had to release a complete recovery procedure due to an issue with the first update. This procedure includes a bootloader and recovery image which should recover any bricked device.
http://notioninkhacks.com/forums/viewtopic.php?f=29&t=364
two new videos
2-finger Rotation on Google Maps
I noticed on one of your videos that the two finger rotation on Google Maps is not working. There is a file called /system/etc/permissions/handheld_core_hardware.xml that tells Android about the hardware. I don't have my Adam (yet -- 1/29 shipping -- I hope), so I can't check. However you might check if the the following permissions are included:
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
<feature name="android.hardware.touchscreen.multitouch.distinct" />
These are needed for "independently-trackable multiple-finger multitouch," or so it says in the associated xml file (that you could alternately include if it exists in the same directory):
<feature name = "android.hardware.touchscreen.multitouch.distinct.xml"/>
Good luck.
ptok said:
I noticed on one of your videos that the two finger rotation on Google Maps is not working. There is a file called /etc/permissions/handheld_core_hardware.xml that tells Android about the hardware. I don't have my Adam (yet -- 1/29 shipping -- I hope), so I can't check. However you might check if the the following permissions are included:
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
<feature name="android.hardware.touchscreen.multitouch.distinct" />
These are needed for "independently-trackable multiple-finger multitouch," or so it says in the associated xml file (that you could alternately include if it exists in the same directory):
<feature name = "android.hardware.touchscreen.multitouch.distinct.xml"/>
Good luck.
Click to expand...
Click to collapse
/etc/permissions/handheld_core_hardware.xml
where do i start looking for that file? on root drive?
Oops sorry, its /system/etc/permissions
Device Info:
Nook Color running B&N 1.2 (Android 2.2.1)
ManualNooter 4-6-16
OC at up to 1.2GHz using Froyo 1.2 dalingrin OC emmc 090111
Problem: Text in some apps cannot be seen (ie Titanium Backup "Filters" screen).
Observations: This problem seems to happen with B&N Software Versions ABOVE 1.2 (I am currently running 1.2 because of this issue).
Search Results: I've only found mention of this problem (or something close to it) in two places: HERE and HERE.
Recommended Fix or Workaround: NONE
I just inherited a Nook Color about three weeks ago, it was reset to factory defaults (B&N 1.1). The person I got it from was running B&N Software version 1.2 with the latest recommended ManualNootered version (manualnooter-4-6-16) at that time. He could not get B&N Version 1.3 to work right. When I got the Nook, the first thing I did was to update it to B&N 1.3 and root it with the latest ManualNooter procedures, which worked great (the procedures had been updated since the person I got it from had tried to root B&N 1.3). Thanks GabrialDestruir!
One of the first apps I purchased was Titanium Backup. I noticed in Titanium's Filters screen there were Radio Buttons that had no text next to them. I was brand new to Android and had a lot to learn, so I made note of this issue to return to later. When I finally got around to addressing this issue, I discovered others had the same problem, but so far it was not addressed within the development community.
In my experimenting I have crashed and re-rooted the device many times, so I know the problem is consistent. I was becoming frustrated and asked the previous owner if he had the same issue with B&N 1.2. He did not. As of this morning, I have returned to B&N Software Version 1.2 and I can now see all the text that was invisible before - in every app I've tested and remembered had the issue.
The specifications above are the only changes needed to reproduce the problem. As soon as I was up and running, I downloaded Titanium Backup from Market. When I rooted the Nook using B&N Software version 1.2, all text was visible. Following the procedures to get the system up to the same place with B&N 1.3, the text problem reappears (text disappears).
Any help with this problem would be greatly appreciated. If you have any questions for me or if I have forgotten a critical piece of information, please do not hesitate to post what you need here, I will be checking it daily.
Thank you for your time, effort, and help XDA! You've made a complicated procedure very simple.
I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk
milliman said:
I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk
Click to expand...
Click to collapse
Changing the dpi in build.prop to 160 helps, but does not cure the problem.
framitz said:
Changing the dpi in build.prop to 160 helps, but does not cure the problem.
Click to expand...
Click to collapse
Can I do that with LCD resolution?
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
Yea, so far, that's what I figured - the Nook is using a white background and if a program does not explicitly define the background and foreground text colors, but assumes the background is black, this is when the problem occurs.
I guess what I was wondering is if there is a way to change the default background color for the Nooks to black, and the default foreground text color to white. I read somewhere about "theme-ing," though, like I said, I am new to Android, could theme-ing be a solution?
I don't get your second statement. I already use CM7 (but only so far as for booting to use ManualNooter), and I have no idea what "Nook market app" you are referring to, or the Kid Reading stuff - do you meant the stock B&N stuff?. Am I missing a key concept here?
Or, possibly, are you suggesting I use CM7 to install a different ROM and skip the Nooter method altogether? I was actually beginning to research this - I can do without all the B&N stuff, it doesn't work right anyway and I have disabled much of the B&N apps. If flashing a different ROM fixes this and "does much more," I'm all for it. It will just take me doing a little more research and someone confirming this is what you are referring to.
khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
I see! I will have to see if I can dig into the nook a little deeper and see if I can do anything about that. It is annoying but I'm not annoyed enough to change to CM7 yet! Plus I have a People subscription that I am enjoying ATM.
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.
Anemailname said:
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.
Click to expand...
Click to collapse
Ah, thank you, I was wondering how some people were runnig higher versions of Android - now I know.
Is it weird I love this stuff?
Well, as they say, back to the drawing board....
EDITED
The theory below is NOT the problem, but I left it up because I cannot delete it and is serves as reminder. Sorry.
ORIGINAL
I have made a discovery; the problem seems to happen, not because of background color assumptions, but when styles are used (an app developer, who was kind enough to debug and redesign his app for me, discovered this).
I am almost to the point in my self-education with Android and Java programming that I can verify this myself, but I am not quite there yet. If someone does verify this, could you please post your findings here?
As you can tell, I haven't flashed the ROM yet, and may not for awhile. It's running OK and I really want to concentrate on programming for the time being.
As more and more developers use styles though, I may not have a choice.
Please use this thread to ask questions about bugs the atrix is suffering related to the Linuxonandroid project, or to ask questions about the webtop version of this project.
For bug and fixes reporting use the development thread HERE
For general questions about Linuxonandroid use the main thread HERE
How is the develop of the dock version ??
Sent from my MB860 using xda app-developers app
Will you still be using the chroot method, or some other way?
Waiting eagerly.:laugh:
Where to start...
Zac,
A wonderful thing to see this thread start so quickly. / I was the one who posted a few days ago about running Deb Wheezy based on your build guide. But I'd like to help push this effort in any way i can. (and I can always run 2 img files since I boot my image from term as opposed to the app...)
My goal reason for the purchase was to be able to bring up X, and launch VPN and RDP / With the build I hacked together I am able to do so with XFCE / VPNc and remmeia / and as far as browsers go, iceweasel was the only one that would semi work. (chrome seg faults / and web would seem to launch and then just disappear...)
When it comes to the webtop, I know there have been some posts about chaning the resolution down to 120 that seemingly puts JB into tablet mode, but I found that to be less than useful once i got into chroot. I've never been happy with the display fonts on the webtop. (once i had a config where the fonts were clear etc, but i did something and lost it... ) But the biggest hurtle there I think in part is that it seems to mirror the 960x540 res / and once you increase it you have to pan. / If you use fit to screen in the menu it will fit it to screen but then the mouse clicks don't pass through...
If you are looking for bugs - what image would be the most helpful / easiest for your to work on? (deb/ubuntu/etc) and full/small etc.
as i will load that to be more useful...
and does it matter what the base rom is. (currently I'm on epinter's CM10 rom updated yesterday) if keeping things more uniform would help I can pop something else on for the time being...
One of the main issues I was getting when running the images was the desktop being gray on the ubuntu 12.04 image like everyone else, but even after getting another desktop loaded on certain programs would not launch. When i would try to launch them from terminal I would get a seg fault. also when I tried to step through the commands in the ~/.vnc/xstartup I was getting a seg fault there as well. (So I am guessing that's why the gray screen when I VNCed. / So the second question is, when I do get a Seg Fault, is there anything additional I can provide that may aid in diagnosing the issue?
Thank you again!
James
Bluemotion said:
Will you still be using the chroot method, or some other way?
Waiting eagerly.:laugh:
Click to expand...
Click to collapse
The 'normal' method is to use chroot (after all it does work very well just needs refining), when it comes to the webtop not 100% yet
Goindrinkn said:
Zac,
A wonderful thing to see this thread start so quickly. / I was the one who posted a few days ago about running Deb Wheezy based on your build guide. But I'd like to help push this effort in any way i can. (and I can always run 2 img files since I boot my image from term as opposed to the app...)
My goal reason for the purchase was to be able to bring up X, and launch VPN and RDP / With the build I hacked together I am able to do so with XFCE / VPNc and remmeia / and as far as browsers go, iceweasel was the only one that would semi work. (chrome seg faults / and web would seem to launch and then just disappear...)
When it comes to the webtop, I know there have been some posts about chaning the resolution down to 120 that seemingly puts JB into tablet mode, but I found that to be less than useful once i got into chroot. I've never been happy with the display fonts on the webtop. (once i had a config where the fonts were clear etc, but i did something and lost it... ) But the biggest hurtle there I think in part is that it seems to mirror the 960x540 res / and once you increase it you have to pan. / If you use fit to screen in the menu it will fit it to screen but then the mouse clicks don't pass through...
If you are looking for bugs - what image would be the most helpful / easiest for your to work on? (deb/ubuntu/etc) and full/small etc.
as i will load that to be more useful...
and does it matter what the base rom is. (currently I'm on epinter's CM10 rom updated yesterday) if keeping things more uniform would help I can pop something else on for the time being...
One of the main issues I was getting when running the images was the desktop being gray on the ubuntu 12.04 image like everyone else, but even after getting another desktop loaded on certain programs would not launch. When i would try to launch them from terminal I would get a seg fault. also when I tried to step through the commands in the ~/.vnc/xstartup I was getting a seg fault there as well. (So I am guessing that's why the gray screen when I VNCed. / So the second question is, when I do get a Seg Fault, is there anything additional I can provide that may aid in diagnosing the issue?
Thank you again!
James
Click to expand...
Click to collapse
Hey James,
Really the biggest issue with know of right now is the grey screen, and with the large ubuntu image unity not rendering correctly. So this will be the image I will be working on first.
As far as base ROMs it really shouldnt matter to much (of cause you will need a stock based ROM for webtop) I will be sticking to a stock base for now so if you where testing from a CM ROM that would be very useful to cover both main bases.
Just pointing out the issues is a good start, on Monday I plan to get cracking with it (had to push it back after not finishing unpacking and sorting my office yet) and should start on the bug squishing, and webtop version will be once I get a lapdock which should be once the device fund has finished.
2x mouse pointer
hello
I have the Atrix with the HD Dock and bluethooth mouse and keyboard.
I'm running Nottachtrix ROM which has HDMI landscape mirroring, this means I can use linuxonandroid with a mouse and keyboard in the dock. The problem is it doesn't see the mouse as a true mouse. I get two pointers, one from the VNC and one which is the bluetooth mouse.
Is there away of using the mouse normally?
thanks for any help
Jonnym
Hitting the menu button or fn-f1 should bring up the vnc program options. One of the choices is "input method" there's a few choices and you may to see what works best for you. (The options are like touch,pan,zoom and various combos if those. I haven't found the perfect one but it would the there I expect.
I've got problems on epinter CM10.
1. I can run only Debian
2. can't get su in Debian
3. sometimes, VNC says "disconnected"
ovitz said:
I've got problems on epinter CM10.
1. I can run only Debian
2. can't get su in Debian
3. sometimes, VNC says "disconnected"
Click to expand...
Click to collapse
Ovitz - yes. This is in part why Zac has this thread too. It seems the tegra2 is a little finicky. I was only able to run Debian as well and only with xfce. I created my own image to do so. It seemed to me that the desktop manager would seg fault and then everything else was an issue. A good start may be to go in to the home did for your user and look in the .vnc hidden directory. There will be a file localhost:0.log (the number may change but should be 0 on the standard image. When you locate the file you can use "cat localhost:0.log" to view it or even better add "> filename.txt" to redirect it to a file. And then you can post it. My guess is you will see a segmentation fault in there.
*disclaimer - I'm just an excited user that has been hoping and waiting to get this worked out on the atrix and not a dev...
Goindrinkn said:
Hitting the menu button or fn-f1 should bring up the vnc program options. One of the choices is "input method" there's a few choices and you may to see what works best for you. (The options are like touch,pan,zoom and various combos if those. I haven't found the perfect one but it would the there I expect.
Click to expand...
Click to collapse
I tried all the input method options available on androidVNC none were that good.
I'm a bit ruined as I've just unlocked the bootloader and installed nottachtrix with faux1.3 kernal and webtop flys, no lag at all, it even runs bbc iplayer HD.
I was hoping to to find a webtop replacement, as I use it alot, so I can run ICS or Jellybean but the combination of the pointer and the complicated start up is making me hesitate. Great to have it working though big thanks to the devs.
jonnym
Jonnym said:
I tried all the input method options available on androidVNC none were that good.
I'm a bit ruined as I've just unlocked the bootloader and installed nottachtrix with faux1.3 kernal and webtop flys, no lag at all, it even runs bbc iplayer HD.
I was hoping to to find a webtop replacement, as I use it alot, so I can run ICS or Jellybean but the combination of the pointer and the complicated start up is making me hesitate. Great to have it working though big thanks to the devs.
jonnym
Click to expand...
Click to collapse
This is a product of the client. My mouse arrow floats above the remote one but anytime I click it jumps to the location and clicks as well. / I am not sure if there are "seemless" 1 to 1 clients with regards to the mouse. But there certainly are a number of vnc clients out there beyond androidvnc. I am sure for each one someone could tell you why it is the best ever or sucks....
Jonnym said:
I tried all the input method options available on androidVNC none were that good.
I'm a bit ruined as I've just unlocked the bootloader and installed nottachtrix with faux1.3 kernal and webtop flys, no lag at all, it even runs bbc iplayer HD.
I was hoping to to find a webtop replacement, as I use it alot, so I can run ICS or Jellybean but the combination of the pointer and the complicated start up is making me hesitate. Great to have it working though big thanks to the devs.
jonnym
Click to expand...
Click to collapse
I would suggest trying another vnc viewer others might handle it better
p.s Im back guys my internet finally got sorted
Can someone make a guide to make this work?...I read a lot but I cant make it..
from the (m)ATRIX...
Cocolopes said:
Can someone make a guide to make this work?...I read a lot but I cant make it..
from the (m)ATRIX...
Click to expand...
Click to collapse
Sure what issues are you having
Sent from my Nexus 7 using xda app-developers app
Dude, what the heck? Are you going to post this same thing in every thread you come across? Posting the same thing multiple times is against the forum rules. You opened a new thread about this, that is more than enough.
zacthespack said:
Sure what issues are you having
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well..I download the img...and run the terminal...but in the vnc I cant get the gui...its just a blank screen.
from the (m)ATRIX...
Cocolopes said:
Well..I download the img...and run the terminal...but in the vnc I cant get the gui...its just a blank screen.
from the (m)ATRIX...
Click to expand...
Click to collapse
Ok do you get any errors n the terminal while its booting?
balintmaci said:
ics was leaked finally so it would be nice to have a linus inside ics webtop once you get there. thanks
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Great! Well my lap dock will be here tomorrow (got held in customs) so we can get down to business
Sent from my Nexus 7 using xda app-developers app
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.