Related
I've been obsessing over the N1 since launch. Android is super neat, and unlocked phones rock. The only thing that really held me back from the purchase was the multitouch issue. I could easily see having to reset my screen with a lock cycle would drive me crazy. That said, I love the idea of the N1, and wish to escape my iPhone prison.
I recently purchased a Galaxy S phone, but am annoyed by the lack of support (saw this coming) and non-functioning locational services. The GPS and Compass are totally and utterly busted. Sadly, Google stopped selling the N1 on the day I decided to order one. However, I have been given a second chance, by purchasing the dev phone (which I am now considering).
So, let's make this like ripping off a bandage. Have mercy, internet. I have questions that require honest answers. I'm sorry if you've heard it all before, but this kind of information is annoyingly hard to dig up. Lightning Round, Go!:
Is the multitouch problem with the N1 (inverse axis swapping when two points cross) still present with 2.2?
Do any custom ROMs, apps or tweaks solve this issue? I read that the Moto Droid had a software setting ticked that allows proper multitouch (a sort of software hack), that google had not opted to enable by default? Sounds a bit silly to me, but what's the deal?
Does your screen still lose track of your fingers (inputing the wrong characters on the keyboard), causing you to lock cycle your screen to reset the digitizer?
Are the touch-buttons difficult to use?
A fellow N1 owner I met told me that his phone showed no signs of the multitouch 'bug', when using 'Multitouch Vis Test'. He said he was running the Modaco ROM. Is it true that something in this ROM fixes the multitouch problem?
Thank you, Princes of Internet.
Personally i dont experience any multitouch issues on my n1. Im running stock froyo 2.2. I have only had to re-lock my screen once and it never happened again. The capicative buttons below the screen take a bit of time to get used to at first it might take you a couple of tries to register a click but a few hours of use you get the hang of it.
Sent from my Nexus One using XDA App
Thanks for the reply.
Would you mind taking the 'Multitouch Vis Test' app for a spin, to see if the problem is gone, or if you just don't notice it?
If the issue is gone, would you mind making a youtube vid of it?
The multitouch on the n1 will not be "fixed" unless google/htc decided to use different hardware. If you can live with a device that can only do pinch to zoom, but not true multitouch, then the n1 is fine.
Honestly at this point, I'd hold off until you see the rest of HTC's lineup that's coming up before december.
Jon C said:
Is the multitouch problem with the N1 (inverse axis swapping when two points cross) still present with 2.2?
Do any custom ROMs, apps or tweaks solve this issue? I read that the Moto Droid had a software setting ticked that allows proper multitouch (a sort of software hack), that google had not opted to enable by default? Sounds a bit silly to me, but what's the deal?
Does your screen still lose track of your fingers (inputing the wrong characters on the keyboard), causing you to lock cycle your screen to reset the digitizer?
Are the touch-buttons difficult to use?
A fellow N1 owner I met told me that his phone showed no signs of the multitouch 'bug', when using 'Multitouch Vis Test'. He said he was running the Modaco ROM. Is it true that something in this ROM fixes the multitouch problem?
Thank you, Princes of Internet.
Click to expand...
Click to collapse
1) It was possibly noticable in 2.1, in 2.2 in months now I havn't see it once. You can see with the visualiser you really have to know how to force it to get it to go, its just not something which will occur with correct commands you'll be doing.
2) Its down to the hardware, I'm not aware of any custom ROMs which have anything/anything significant.
3) The only time I EVER get this is with beta super bundles of ROMs, which is either the fault of the ROM, something going skitz in dalvic, how I installed it, or just a self generating bug. All of which are easily fixable. However if you were to stay with stock or more tested ROMs, you'd literally never see this.
4) For me they just work, at the start yes they wouldnt act the same a touch screen, but now they'll act like I want maybe 99% of the time. Sure friends using it to start with have to get used to it, but its not 'broken' if you will. The only thing I will mention is if your using it in weird orientations, there is a chance of hitting the buttons [mainly search] without meaning to with parts of your hand.
5) Again, this problem ONLY shows up if you know how to 'break' it. With 2.2+ its really hard to do it if you handed the phone to someone who's never used it before, because also again you wont be doing any commands which would conflict with the limitations, so you have to be misusing it in the first place to get the bug.
JCopernicus said:
Honestly at this point, I'd hold off until you see the rest of HTC's lineup that's coming up before december.
Click to expand...
Click to collapse
Agree with this.
Multitouch is completely crap on the n1. I loved it otherwise, yes every now and again it goes wack and registers the wrong thing... the capacitive buttons also suck and are hard to get used to... on Multitouch test its wacky and registers the wrong finger and won't register more than 2...
Great device, but galaxy is better.. I don't have any gps issues so can't complain about that.
No. No roms will fix the Multitouch issue. Nor make it any better.. if your into gaming with controls on the same axis forget about it, if ya want Multitouch keyboard forget about it...
I still have yet to ever experience the actual axis switch issue using this phone in real world. Sure the issue exists, but it just doesn't effect a single thing unless you use a certain game. But even that works fine, watch YouTube videos showing emulators on the nexus.
The point is, if you're looking for a reason to not get the nexus, The axis switch issue is not the reason that should sway your decision.
I recently came from an iPhone and I haven't noticed any difference in the multi-touch screen (except maybe in the typing on occasion, which I just attributed to my big fingers). I'd say for a good 95%+ of what you would do on the phone you can't tell any difference between the iPhone or N1 multitouch.
With the touch buttons on the bottom of the screen... Sometimes I hit one while typing, which takes me back to the home screen, but since the N1 has true multitasking all I have to do is reopen the app. A minor inconvenience. Or I could just type in landscape mode and not have any trouble at all.
RogerPodacter said:
I still have yet to ever experience the actual axis switch issue using this phone in real world. Sure the issue exists, but it just doesn't effect a single thing unless you use a certain game. But even that works fine, watch YouTube videos showing emulators on the nexus.
The point is, if you're looking for a reason to not get the nexus, The axis switch issue is not the reason that should sway your decision.
Click to expand...
Click to collapse
Games like toonWarz or nova will mess up. Has the controls on bottom right and shooting on bottom right. So when your running using the left controls and shoot real quick with the right, it'll now wig out and keep shooting even when you let go and the dude will walk a different way be cause now the sensor thinks your touching in a different spot..
Now you can let go of the left finger then shoot but when ya need precision in some shooting games you will be dead if you do that....
Pinch to zoom is fine and emulators with controls on the top and bottom vs just the bottom ( same axis), but for games like nova, heavy gunner, modern combat, ps1 emulator (unless it has opposite axis controls) which mine don't, took Warz, etc. It will not work properly ....
smashpunks said:
Games like toonWarz or nova will mess up. Has the controls on bottom right and shooting on bottom right. So when your running using the left controls and shoot real quick with the right, it'll now wig out and keep shooting even when you let go and the dude will walk a different way be cause now the sensor thinks your touching in a different spot..
Now you can let go of the left finger then shoot but when ya need precision in some shooting games you will be dead if you do that....
Pinch to zoom is fine and emulators with controls on the top and bottom vs just the bottom ( same axis), but for games like nova, heavy gunner, modern combat, ps1 emulator (unless it has opposite axis controls) which mine don't, took Warz, etc. It will not work properly ....
Click to expand...
Click to collapse
this is a good explanation of what is effected. if you're a big gamer then consider it, but things like pinch to zoom in the browser, maps, pics, works just as great as ever.
Thanks for the feedback, guys.
Coming from the Galaxy S, I imagine I will miss a few things. One of them being: media playback and overall storage.
I guess with the N1, I'd need to find a non-bootlegged 32GB microSD card. But my other question would be: is there an easy way to play all of the content that the Galaxy S can handle, or is the GPU in the Samsung phone so much better that the N1 can't keep up?
I really like that about the SGS: I just drop movies (mp4, xvid, divx and so forth) onto the internal ROM and they play without issue. Media capabilities are very nice.
Does the N1 play lots of videos like this out of the box? If not, is there a decent media application?
Also, about HTC's other devices: I'd love to wait, but I'm worried that the newer phones won't have nice accessories. The N1 has that awesome car dock, that I would use all of the time. The SGS doesn't have any accessories like that, and it makes me sad. Most of HTC's N1 follow-up lacked similar docks and cradles.
If I return this SGS (likely), I will probably be jumping to the N1, just for that 'official' feel of it (very sturdy, solid first-party accessories).
You have no idea how sad I was, when Google announced they were giving up on creating their own phones. Hate them all you want: but Apple really has that system (solid build, quality integration / lack of fragmentation) nailed. I was really hoping that Google could bring that unification to Android with their own branded devices.
Loving Android, though. Never going back to iOS.
Anyone saying the n1 doesn't suffer from multitouch issues is sadly mistaken. The one thing that bugs me about the n1 is the touch screen issue. You won't be able to play games like nova, or certain games on emulators (when using dpad plus buttons that are at the same level it has issues) and it does have issues when crossing the axises.
mjm128 said:
Anyone saying the n1 doesn't suffer from multitouch issues is sadly mistaken. The one thing that bugs me about the n1 is the touch screen issue. You won't be able to play games like nova, or certain games on emulators (when using dpad plus buttons that are at the same level it has issues) and it does have issues when crossing the axises.
Click to expand...
Click to collapse
everyone said the issue exists it just doesnt show up unless you...play....games. otherwise its a non issue.
The N1's touchscreen is totaly crap. There is a thread about touchscreen issues at oficial forum. It has more than 2000 posts explaning all problems of nexus one touchscreen. Check it out.
Sent from my Nexus One using XDA App
Jon C said:
Thanks for the feedback, guys.
Coming from the Galaxy S, I imagine I will miss a few things. One of them being: media playback and overall storage.
I guess with the N1, I'd need to find a non-bootlegged 32GB microSD card. But my other question would be: is there an easy way to play all of the content that the Galaxy S can handle, or is the GPU in the Samsung phone so much better that the N1 can't keep up?
I really like that about the SGS: I just drop movies (mp4, xvid, divx and so forth) onto the internal ROM and they play without issue. Media capabilities are very nice.
Does the N1 play lots of videos like this out of the box? If not, is there a decent media application?
Also, about HTC's other devices: I'd love to wait, but I'm worried that the newer phones won't have nice accessories. The N1 has that awesome car dock, that I would use all of the time. The SGS doesn't have any accessories like that, and it makes me sad. Most of HTC's N1 follow-up lacked similar docks and cradles.
If I return this SGS (likely), I will probably be jumping to the N1, just for that 'official' feel of it (very sturdy, solid first-party accessories).
You have no idea how sad I was, when Google announced they were giving up on creating their own phones. Hate them all you want: but Apple really has that system (solid build, quality integration / lack of fragmentation) nailed. I was really hoping that Google could bring that unification to Android with their own branded devices.
Loving Android, though. Never going back to iOS.
Click to expand...
Click to collapse
The gpu is OK. But definitely a lot less powerful than the sgs, you will notice in movies, live wallpapers and especially games... there's a decent video player called rockplayer that plays a lot of stuff like avi and xvid , but its not ad good as the sgs player ...
Put it this way, either stay sgs and have a not so well navigation but awesome everything elsex or go nexus with good GPS but a old touch sensor that will hardly recognize both fingers on anything other than pinch to zoom.....
The only real world scenario i have encountered the axis switch is when you do a pinch on an album in the gallery to have it flick through them, it switches often when doing that.
Nexus One multi-touch sucks for games. I've tried some fancy gameloft games that req two fingers on screen, or PS & gameboy emulators that req this and it drives me insane. Can be so frustrating for gaming and is the only thing that I find a let down for this device. I wish I knew before I purchased it because the gaming although not the only thing I brought it for is something that I thought would be cool on my phone.
Simply put, don't get the N1 if mobile gaming is important to you. I'm not talking about simple single tap games, but the intricate ones (PSX Emu, EA Sports, Gamesloft, etc). If you could live without it, the touchscreen is fine for regular day to day use.
Or just root and carry your favorite bluetooth game controller. I have a mini bt keyboard that works great for emulators
I am going to purchase this but can anyone give me the lowdown on this.
I am a diehard android fan and own every tmobile device, are all functions working on this device?
I mean the important stuff, wifi, browser, games, g-sensor, 3d games?
I was going to get an archos 70 but this looks way cooler and customizable.
Please let me know.
Wifi works fine. I can connect to my home network just fine. Also works connecting to my Samsung Vibrant's mobile AP wifi.
Browsing work. Stock browser is a very sluggish experience. I'm using Dolphin and still find it to be a slower experience than on my Vibrant phone. Wish it was faster. But it's acceptable performance.
G-sensor seems to be working fine. Was playing Raging Thunder and it worked great.
However there is an issue with some games. They will not play at full screen resolution and seem to run in a smaller 4:3 aspect ratio (looks like 600x800) with black borders on the side.
I haven't tried a lot of games. Angry Birds (both) and Paper Toss work in full screen. Solitaire, Raging Thunder don't work at full screen.
But the performance of the games seems good so far.
To me, Dolphin HD (along with the rest of the system) is plenty fast with SetCPU running min 600/max 800 ondemand.
Really, there have been surprisingly few things I've come across that I haven't been able to do-- even without a custom ROM/kernel. I couldn't be happier with this--and development has really just started (I'm sure some brilliant devs found one under their tree today).
If you're looking for a solitaire game, Klondike Solitaire is a full screen app.
Ravynmagi said:
Wifi works fine. I can connect to my home network just fine. Also works connecting to my Samsung Vibrant's mobile AP wifi.
Browsing work. Stock browser is a very sluggish experience. I'm using Dolphin and still find it to be a slower experience than on my Vibrant phone. Wish it was faster. But it's acceptable performance.
G-sensor seems to be working fine. Was playing Raging Thunder and it worked great.
However there is an issue with some games. They will not play at full screen resolution and seem to run in a smaller 4:3 aspect ratio (looks like 600x800) with black borders on the side.
I haven't tried a lot of games. Angry Birds (both) and Paper Toss work in full screen. Solitaire, Raging Thunder don't work at full screen.
But the performance of the games seems good so far.
Click to expand...
Click to collapse
If you install spare parts and uncheck compatibility mode. A lot of games and apps become full screen.
Pinesal said:
If you install spare parts and uncheck compatibility mode. A lot of games and apps become full screen.
Click to expand...
Click to collapse
The problem for some of those games then becomes the graphics are full screen but the touch-UI isn't. So, you have to click above or below the on-screen buttons to hit them. I've also seen a game (Hungry Shark) where the in-game locations no longer correspond to the graphical locations (the shark thought the water's surface was well below where it really was, so he couldn't get up to the actual surface, like he was hitting an invisible wall).
Hopefully these apps will be updated for tablet resolutions soon.
It seems that corner touch screen sensitivity issues are prevalent among all nook color users. What I'm wondering is, does nookie Froyo have this issue as well?
Yes, or at least for me.
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
I'm on a rooted stock, but my edge sensitivity issues went away when I loaded one of the overclock kernels. I don't know how the two could be linked, but it is the only explanation I have for the difference. I'm not sure if that's been explored on Nookie, but I thought I would share since that would point to a software issue rather than hardware.
isolated_epidemic said:
I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
That I'm not so sure of. Using "Touch Test" I see all touches, but they seem to get shifted slightly when I press near the edges. Maybe this could get solved in the driver (maybe with some help of calibration tool). I hope to have time to play with this sometime soon.
isolated_epidemic said:
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
How can you be so sure?
If i use google market, sometimes the search button is hard to press,
but using appbrain market it works 100% of the time without problems.
No its not H/W I think, run some tests and corners work fine.
Its certainly something else, I also have better response after loading OC.
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
I've seen the same behaviour as well, some apps the corners take 18,013,108 tries to get to work, other apps I'm all "Whoa, first try and it worked?!".
I put the 950 OC on my autonoot but then I started playing with Froyo on a C10 SD card (very quick) so I don't know if the OC's actually helped with the corners or not. And of course this is the one day I leave it at home since I got it.
Ultimoose said:
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
Click to expand...
Click to collapse
Use Menu>Search instead of trying to touch the top magnifying glass.
Happens to me with Froyo. I seriously doubt its hardware related. Seemed to work fine on the stock B&N.
It is common for digitizers to be less accurate along the edges but the Nook Color seems worse than normal. I've noticed the problem regardless of kernel or rom used.
I'm pretty sure it has something to do with the LCD Density. All buttons/elements are a lot easier to press when I switched to 240-250. It does look ugly though, it'd be a lot prettier when we get a custom rom running.
Sigvard is right. Fixed for me by chaging my LCD Density. I set it to 200, which is a little too large for me, so I may lower it. But since doing that I have had no problems at all.
Guide here: http://forum.xda-developers.com/showthread.php?t=889951&highlight=LCD+Density
Ha! I have the exact problem even with stock rom. I though it was the problem of the particular corner of the unit I got! It is much easier to press the button in landscape view.
I dont believe its the screen. Download AppBrain and tap the search button. it works 100% of the time
It is the screen. Use a drawing program and notice how it is easy to draw a straight line in the middle and not as easy on the sides and corners. Note, you need to drag your finger slowly or else you will see more interpolation.
Raising the LCD density just hides the problem by making the hit zone bigger. Fortunately, I can live with the it.
Am I doing something wrong, or is this just what everyone's used to? The nook color is horrible for using for, well, anything, even when I first bought it the rom was laggy and sluggish. Rooted and wiped full, tried Honeycomb, CM7, MIUI, all overclocked to 1.2Ghz, and they're all just terribly slow. I had to return my first NC due to a yellow screen, and the replacement is rooted and on CM7 right now. Simple things like scrolling through a list of apps or contacts causes the nook to think I'm tapping on the contact rather than starting to scroll, pressing back in an app hangs forever until I press it again and then it registers both back presses and goes back twice, dragging widgets is nearly impossible due to the device being horrible with recognizing a drag, every animation, app drawer, slide, touch, drag, is painfully and horribly slow.
Again, this is the exact same experience I've had over two completely different new nook colors, with multiple different ROMs, including stock and overclocked. Please, tell me I'm doing something wrong, I hate this nook more than anything in life right now and I want to fix that.
Well, the NC is not the fastest android device around, but with the latest CM7 nightly, at 1.2GHz, 32 bit framebuffer disabled in Nook Tweaks and some decently optimized/accelerated apps (ADW EX instead of whatever other launcher, Opera instead of any other non-accelerated browser, Mobo for videos, etc.) it's mostly silky smooth.
I say mostly because there are some things that could be smoother, like scrolling through lists (I wish they could stop the GC from freeing memory when scrolling once and for all) and some apps that are quite slow, like ES File Explorer (also related to the GC), but otherwise it's perfectly fine to use. I have an HTC Desire and I do notice that the Desire is slightly smoother in some areas (or much smoother when srcolling through lists), but the NC is not far behind for everyday use.
I would say that your experience is not typical. The only problem that some (but not all) people have reported that your problem resembles is touch screen problems reported when using the NC will the charger plugged in.
You MIGHT be having trouble with lots of static electricity due to dry Phoenix air and A/C use. It's a shot in the dark.
You'd probably need to try to reproduce the problem for somebody to observe. I have seen some really weird PEBKAC problems that took a fresh set of eyes to troubleshoot.
I'm on phiremod. I have a few issues with it (mainly apps that I've loaded disappearing). Right now I'm going to leave well enough alone until ice cream sandwich.
With ics, we'll have the aosp (since its also for phones), and its designed to work with 7" screen and with software buttons. ICS will give us a fantastic and stable nook color (I'm only guessing though, lol)
Sent from my DROID3 using Tapatalk
No issues here. I've been running 7.1RC for a while not and have no experienced anything like you say you have. True it can get sluggish at times, but never for an extended amount of time that has made it unusable.
When I used to run the old 7.0.2 stable, I noticed that having a fair amount of widgets running could cause the system to slow down. But even now with a few widgets, about 12 icons per page, and rotating wallpapers using three total pages, I use it daily and have no issues.
I have to admit I found CM7 pretty laggy before I started using the OC kernel. It's super easy now with it built into the nightlies, and it made a huge different in scrolling, etc.
That is not typical at all. I wouldn't be using (and loving) mine if it were. I am using CM7 nightly on emmc and it is a fantastic piece of work! Very responsive for what I do even without overclocking. Your experience is bad even on the stock OS so maybe it is bad hardware?
Just for kicks, I tried HC on a SanDisk 4GB class 4 card. And it is a little sluggish like you described. But not as bad and still very usable. I went back to CM7 because it is so much more responsive.
Ok, to be fair, when I say CM7 was laggy, I mean it wasn't super-silky-smooth like it is after overclocking a bit. I don't have a lot to compare to aside from a fairly new android phone (Thunderbolt). I did try a Honeycomb preview build first and that was a frustrating experience (laggy, stuff didn't work), but it was one of the earlier *preview* builds. CM7 with tablet tweaks is awesome.
To be honest, I never thought I'd register an account on XDA. Seems like theres too many pros for the noobs to fit in. Although the XDA noob video did give me some laughs.
To the OP:
Have you switched over from an Apple device? I previously had an iPhone 3g, and then a 3gs. When I switched to the Xperia X10 I thought either it was me, or the x10 was seriously messed up. It seems like it was me. I think the reason is that to scroll on the iPhone, all you need is a tiny little swiping motion to move between screens. However, it's not the case with Android phones. I found that your swiping gestures need to be a little bigger, otherwise, it's recognized as a click/tap/whatever.
I got used to it, however, I did find that installing a custom rom (CM7) helped a little.
edit:
Also, make sure you use advanced task killer or something to get rid of stuff in the background. **** running in the background Makes it slow. If it's rooted, try SetCPU and have it so that it's not ondemand, but on performance. Or, adjust the sliders until the minimum and maximum CPU speed is the same, making it run full speed all the time (Although I recommend having it set to the minimum while the screen is off.)
Apparently a major cause of the sluggishness in the scrolling of various apps and things such as form lists is due to the OS's garbage collector going nuts and trying to free memory in rapid succession. No ROM available for Nook Color solves this as it's some sort of flaw with Android 2.x itself. I don't know if Honeycomb (3.x) is better but I'm guessing that it is. Honeycomb will probably never be available in source form so Nook Color will never get it in proper form. Supposedly Android 4 (Ice Cream Sandwich) will be released in source, but we're talking a ways off and I'm unsure of how well it will fit Nook Color's hardware.
But yeah Nook Color is very slow compared to say a notebook. The CPU is an Arm Cortex A8 which is very low power, but also very simplistic compared with desktop/notebook CPUs. This is a necessity with a handheld device. However, the newer tablets with the NVIDIA Tegra 2 SoC (for example) use a Cortex A9 dual core where each core is much superior to the Nook's CPU and it has two of them.
Nook Color is a cheap entry level tablet with a nice screen but it has a ton of quirks because in modded form it is a community project with limited resources behind it.
OP, are you installing to an sd card? Maybe the card is unsuitable (quite common problem). I actually underclock mine, installed to the internal drive. Sometimes I get a menu scroll registering as a tap, but I get that on any touch device I've tried. Overall a properly tuned nook runs pretty snappy imo.
selection16 said:
OP, are you installing to an sd card? Maybe the card is unsuitable (quite common problem). I actually underclock mine, installed to the internal drive. Sometimes I get a menu scroll registering as a tap, but I get that on any touch device I've tried. Overall a properly tuned nook runs pretty snappy imo.
Click to expand...
Click to collapse
What he said^^ are you running off SD card? I tried that at first and absolutely hated it, it was soo slow ESP. Scrolling through the interface and app drawer. I have since put phiremod 6.3 on my emc and saw a huge improvement and I'm only at 800mhz. Then I tried the v6 supercharger script and again saw an improvement in scrolling speeds and smoothness. If I OC then its very snappy! You may also try to recalibrate the screen if you are finding its not super sensitive which it is.
selection16 said:
OP, are you installing to an sd card? Maybe the card is unsuitable (quite common problem). I actually underclock mine, installed to the internal drive. Sometimes I get a menu scroll registering as a tap, but I get that on any touch device I've tried. Overall a properly tuned nook runs pretty snappy imo.
Click to expand...
Click to collapse
Oh yeah, there's also that possibility.
I don't have a nook but I've been reading up about it.
Shouldn't you have a class 4 microSD card or higher for it to run decently well?
DillonBladez said:
Oh yeah, there's also that possibility.
I don't have a nook but I've been reading up about it.
Shouldn't you have a class 4 microSD card or higher for it to run decently well?
Click to expand...
Click to collapse
Random block write speed is the most important thing. Sandisk 8 and 16 gig class 4 have the best performance suited to running a SD based CM7. Other brands even in class 6 or 10 have been found to be too slow and resulted in force closes and sluggish responding apps.
Nope, I'm not running it off an SD card. I think the screen issue is a problem with my nook itself; installing a drawing app and trying to draw never gives me a full line, and drawing in some places is just impossible.
As for the slowness... I must be doing something wrong then, because both my nooks have just been horrible.
That's certainly not my experience. I'm running CM7 nightly 151 off sd and I can scroll through my app drawer or through long file lists very smoothly. A simple flick moves easily through hundreds of thumbnails. The only lag I ever experience is changing web pages. Maybe I'm biased because my main computer is a netbook but I really don't think the nook is at all slow.
DillonBladez said:
Also, make sure you use advanced task killer or something to get rid of stuff in the background. **** running in the background Makes it slow. If it's rooted, try SetCPU and have it so that it's not ondemand, but on performance. Or, adjust the sliders until the minimum and maximum CPU speed is the same, making it run full speed all the time (Although I recommend having it set to the minimum while the screen is off.)
Click to expand...
Click to collapse
Do not EVER use a task killer!! This is android 2.3 not 1.5. Task killers screw everything up. Android Handel's itself and apps that task killers say are running in the background are NOT really running they are cached for quicker use. Android is smart, its Linex not windows. Also do not have your CPU going full speed 24/7. Ever heard what heat does to electronics? Its not pretty.
To op:
What version of cm7 are you using? Try a recent nightly.
Sent from my NookColor using Tapatalk
I have to say I had touch response issues like "ghost taps" more often in the first month I had the NC, but they were never a constant thing, and usually resolved by turning the screen off for a second and back on. I haven't had any such issues in quite a while, though I do occasionally have to repeat a tap on the softkeys.
If you haven't, you should track down the touchscreen calibration app for the NC and see if it helps. Some people say a screen protector helped even out their touch response, too. The NC's touch response is not the greatest in general, but your issues sound extreme.
If your finger can't make solid lines in canvas or Sketchbook try recalibrating the screen using nsr (I think its called nook screen recalibrate in the market) otherwise LCD density? Any ideas anyone?
As for ghost taps I used to have that and you know what fixed it? Either cleaning the screen all.day or a screen protector. Since the screen protector I haven't had ghost taps or the zoom in zoom out craziness that the tap of the power button fixed.
OP: try an install to eMMC its quite simple if you make a cwr bootable card to install it with
Taosaur said:
If you haven't, you should track down the touchscreen calibration app for the NC and see if it helps. Some people say a screen protector helped even out their touch response, too. The NC's touch response is not the greatest in general, but your issues sound extreme.
Click to expand...
Click to collapse
To save you a search, it's here.
Has anyone else noticed that the 60hz setting on this phone isn't actually 60hz but 60.3?
Am annoyed with this because I really wanted to use this phone a lot for emulation on the go but am getting micro stutters with emulation because of this.
For example. Ppsspp on games like ridge Racer will micro stutter on races due to the game wanting to play at 60hz but the screen being 60.3hz
Retroarch is the same on emulators.
The best way to check this is happening is to install an emulator like snes9x ex, and run a rom at default settings. You will see the stutter. Mario kart for example on the title screen is easy to spot this.
However, if you allow the game to run at detected screens refresh (which is actually 60.34hz) then the game runs flawlessly.
What gives? I'd assume on a phone primarily sold for gaming purposes this refresh rate would be totally nailed down to 60.00?
Is there anything I can do to fix this?
No one else has this issue?
I've updated to latest official WW firmware and the problem is not solved. I've even done a complete reset and problem still exists. Can only assume at this point that the 60hz mode actually isn't 60hz at all. That'll be enough for me to go back to the black shark 2 until this is resolved, if ever. ?
Does anyone emulate using retroarch or anything on this phone at all?
If so, how do you get literally anything to run smoothly? Messing with the phone even more and I cannot get rid of micro stutter. Im even getting it on 60fps locked android games? Is this issue just my phone or are people just ignoring the problem?
kristianity77 said:
Does anyone emulate using retroarch or anything on this phone at all?
If so, how do you get literally anything to run smoothly? Messing with the phone even more and I cannot get rid of micro stutter. Im even getting it on 60fps locked android games? Is this issue just my phone or are people just ignoring the problem?
Click to expand...
Click to collapse
I emulate through citra mmj, dolphin & ps2damon. Not facing any frame-related issues. I add these apks to armory crate and lock them to 60 fps regardless of the phones global refresh rate. Although I did not face any problems prior to doing this. I've also been playing regular android games in both 60 & 120 fps without issues. The only funny problem I've found is that many game engines lock their speed to fps, so if you force 120 on unsupported games, many will run in x2 speed.
I've never heard of retroarch before, what are the benefits?
EDIT: I'm on WW .34
TheBrutalLicker said:
I emulate through citra mmj, dolphin & ps2damon. Not facing any frame-related issues. I add these apks to armory crate and lock them to 60 fps regardless of the phones global refresh rate. Although I did not face any problems prior to doing this. I've also been playing regular android games in both 60 & 120 fps without issues. The only funny problem I've found is that many game engines lock their speed to fps, so if you force 120 on unsupported games, many will run in x2 speed.
I've never heard of retroarch before, what are the benefits?
EDIT: I'm on WW .34
Click to expand...
Click to collapse
I suppose with emulators for PS2 and GameCube etc the problem will be less obvious because games are prone to slight frame drops anyway because they don't quite run full speed all of the time.
Retroarch is basically an all in one UI that has loads of emulators all under one roof.
I boot all emulators at 60 through the crate but it doesn't make a difference.
I know it's an issue where the 60hz mode isn't actually 60, it's slightly off it. What I'm trying to figure out is whether it's an issue with my phone( some weird hardware fault) or an issue with all Rog 2 phones.
You'll only really see the problem with games or emulators that are a hard lock to 60fps.
So emulators like SNES, genesis, GBA, ppsspp or playstation 1 it's quite easy to see.
Its a common problem in cheap Chinese tablets where they don't nail down the refresh rates, but didn't think it would be in a high end gaming phone.
Edit:
I've had one other person test in snes9xex and he's getting the same issue as me so it seems it might be a phone issue. Hopefully it gets fixed in future firmwares, I don't know