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
Now I know Google has a lot of very smart people, but you would be hard pressed to prove that to me based on some of the rather inexplicable design decisions made for Android Auto, especially when you consider that one of its primary goals is to minimize distraction when interacting with Android.
Let's start with the voice button. I know it is in the top right corner of our phones and tablets, but that is a lousy reason to locate it in the same place on your car's display. For US drivers, it seems the most inconvenient place for it.
Moving on to how messages are handled, it feels as though Google wants your right hand off the wheel, and your eyes off the road. Consider that when a message comes in, Android Auto interrupts your audio to inform you of that. Does it read it to you, or offer to read it to you at that point? No. It expects you to touch the top of the screen, but you better do it quickly as it will be gone in a few seconds. Then you will most likely have to make several taps on the screen to have Android Auto read you the message, and return to the screen you were previously on.
And when it does read you a message, it tells you can reply by tapping the voice button (that one at the far right corner of the screen). Why doesn't it just ask you if I want to reply instead of requiring more physical interaction with the screen?
There are other distractions as well, albeit fairly minor when compared to the above. For instance, when my phone is connected solely via Bluetooth and I am listening to something, when I exit and then return to my vehicle, playback resumes. But if I'm connected to Android Auto, again I am required to interact with the screen. It is the same with navigation... turn off the car for any reason and you will have to reestablish your route again when you startup.
Now maybe it's just me, but having Android Auto for just a week or so, these seem like pretty big potholes on the road of usability, and some seemingly so obvious that I'm was surprised to experience them.
So, is it really just me? How do you feel about Android Auto's workflow? Do you find it unnecessarily distracting? Does it require more of your attention than it should?
AA has many issues that need to be fixed.
But I feel confident that Google WILL fix these things.
Connected cars are and will be BIG business and Google will not abandon it as they've done with some other things.
Consider how much was fixed and improved in Android itself from v1 through to 5.1.
Note that we've all been waiting for decades for something like AA in our cars. Google has been working on AA for years, and it will take years more to work out the kinks.
Plugging a phone into an AA head unit is a model that has problems but is somewhat temporary. Googles goal is to have Android itself running in the car or HU* and this solution will be superior. I think we will hear more about this at I/O; Android 6 allegedly has AA "baked in".
*Many HUs (Pioneer, Chinese) are already running Android and I think Honda is working on this now.
AFAICT, most people who have seen AA and Apple CarPlay prefer AA, so Google has the advantage here.
mikereidis said:
Consider how much was fixed and improved in Android itself from v1 through to 5.1
Click to expand...
Click to collapse
I have... which is a big reason why I bit the bullet. For me, Android was way too rough 'till JB (which is when I switched from iOS). I am hopeful AA's path will be on road with a much higher speed limit.
I have experimented with both RemixOS for PC and Remix Player on my Intel z8700 tablet over the last 9 months. I have seen noteworthy improvement in the development of both.
I am still unable to boot RemixOS for PC on my tablet (I think due to some issue with my UEFI boot loader), but RemixOS Player now starts up OK. That being said, it is pretty much unusable with input from the touchscreen on the tablet. The RemixOS Player tries to use the touchscreen input to emulate mouse/touchpad input. That doesn't work well at all.
If RemixOS Player is running on a Windows 8.x or Windows 10 system with a touchscreen (like a tablet), it should detected that and map the relevant portion of the touchscreen as it it was a touchscreen tablet running Android.
This is shocking to me. It's like touchscreen support was removed. Thought I had found a good emulator for my surface pro 3, now the search continues.
Yeah, completely insane. No fullscreenmode available either. It's work in progress. Should be declared pre-alpha.
I have posted the same some weeks ago here
I am using AmiDuOS so far. Works way better. Or maybe I should say 'it works'.
Remixos just don't. Hoping for a solid version of it though, later next year.
It's killing me too
diehard2013 said:
It's killing me too
Click to expand...
Click to collapse
almost dead...
I think I got your fix!
Hopefully you guys are still subscribed, I came across this thread looking for help with my touchscreen because just like you I found it pretty much sucked to use. After reading above the statement regarding touchscreen working like a mouse I remembered one of the experimental features. I'm not sure about Player, but in settings of Remix OS, Enable trackpad is in the settings under Experimental features. The description is a little misleading "Enabling this setting allows you to use your trackpad as a mouse" well WTF else would you use it as lol. When I first booted I was docked and thought everything worked awesome as I used the keyboard with trackpad and only a tap on the screen here and there, so when I came across this setting I recalled a past experience with x86 (or was it my motorola Lapdock) and the trackpad working like a touchscreen digitizer and me guesstimating where on the trackpad I had to touch to hit the exact spot needed on screen. Anyway I did not want a repeat of that fond memory of fun and thought it best to leave enabled.
Long story short I revisited said setting, disabled it, and after a reboot the touchscreen now works like it's supposed to! Haven't found out if it stops working still after waking up from a deepsleep, but that's likely a seperate issue anyway. It's nice doing the helping for once, hope it works for you guys, let me know if it's the same for you Player users.
PS if you're setup like me make sure you also turn on the onscreen keyboard even when hardware keyboard is detected before you undock, evidently the touchscreen is recognized as a hardware keyboard input as well, at least on my Switch 11.
The track pad option does not appear to be present in Player, using version 3.0.307 at the moment. The only setting that even remotely relates is track pad / mouse speed slider under input.
Remix on Surface 3 ugh
Like an idiot i didnt consult xda before loading the dual boot. power and volume hard buttons dont function except for hard reset then it bypasses the boot menu and boots into remix.. i can get into safemode still but the lack of support or even the show of effort for touch support is a deal breaker on all fronts. i was really hoping to find an update...
Dell venue 11 pro, touchscreen doesn't work at all, even after disabling Trackpad option in experimental features, so confusing as this is a touch screen based OS lol and it's the only thing not working!! zzzzzz
Hello,
I am new here and have no experience programming Android systems. I am looking at buying an Android platform in dash radio unit that has some hard key buttons and hard hey knobs.
I don't know if this differs from other Android platforms such as a cellular telephone or a tablet but here's what I am wanting to accomplish (I am under the impression anything is possible since it's just a computer program comprised of 1s and 0s but I'm sure all of you will set me straight).
Okay so essentially I would like to customize the interface, easy enough I know lot of people accomplish that, perhaps only rooting would be required... however I think my vision is more complicated than most. My intent is to create a vector cartoon image of my vehicle, during boot I would like to have the image load on the screen and as the booting phase is progressing (like a status indicator) different lights will turn on, and perhaps have some audio that plays. Then on the home screen I would like to have the same image (or similar) with different status indicators shown, which lights are on, if the vehicle is running, TPMS values, also time of day would be reflected with either a sun progressing across the sky from Sun rise to sun set, then the moon will come out with Northern Lights dancing in the sky. While driving perhaps the wheels could turn.
So yes to me it seems highly ambitious and very in-depth. All of that information will be available to the unit via other applications except for the lighting which I could route through separate circuitry (perhaps through a USB interface??) unless there's another?
My intent is not to open the unit or rebuild it physically. But rooting, reprogramming, flashing, and wiring outside of the unit I am comfortable with.
I believe that's a good start for now, I appreciate your time.
P.S. I don't mind learning and doing the work myself, I am starting from scratch though. Is this viable? Would it be expensive to pay someone? Is it even possible?
I have left out the brand and product because I'm assuming it wouldn't matter, it is running Android 8.0, 4G+32G, 8-core CPU, it has the hard buttons and is touch screen.
Sorry, there is another feature I was looking at having. It has a dedicated hard key "Navigation" button. I was hoping to have two or three specific navigation applications, that as I press that button, it will jump to the last used application, and with each button press it will cycle through all the other 'designated' gps applications.
Also I might want to customize some other hard key button functions, but that's the major one, so I am hoping/assuming it can be done in the first place.
Also simple default startup options, running programs, screens and layout.
Thank you for your time and knowledge.
No one even has any advice or help or anything constructive?
Am I posting this question in the right forum?
Usually forums aren't this quiet. ?
What your looking to do sounds like it would require a decent amount Android programing knowledge. If your starting from scratch with no experience in programing or building Android applications I do not think it's worth your time.
Yes the headunits run a mostly normal version of Android with some customization to do things like interact with the can bus and play Bluetooth audio.
Thank you for the reply, so for an experienced programmer, is this reasonably achievable?
Would it be with contacting someone to do this?