Related
OK..so we are all excited about the Kaiser and some of the lucky ones have it already. We all know the specs and we hear about the fun those lucky ones are having with the devices. Needless to say, with new devices, problems sometimes follow. I know there have been a few minor complaints but, let's use this thread to compile the issues (and hopefully the fixes).
I am thinking of jumping ship from my rather good plan in order to get a Kaiser and hearing both sides of the spectrum can help myself and others make a more educated decision.
I am interested in Kaiser also. One of the most issue that i hope being fix in Kaiser was the screen auto-on issue while changing song when listen MP3 with BT stereo handsfree which happened in D810 and P3600i.
Well, I've had my kaiser since the 7th and I have put it through most of it's paces so far.
The only complaint I can think of is the already known problem where storing pocket IE's cache on the storage card causes it to freeze up. I'm fully confident that someone here will figure it out.
That said it's a really nice upgrade from the Tytn I've been using for over a year. If you consider a different browser, like Opera mini it performs extremely well.
I've had one about a month. Overall very pleased with the purchase. Here are my top nits:
1. Audio clicks or audio cut-out when playing long audio files (>5min). click will happen every 5 min, which might suggest it's reading the file into memory in chunks and having trouble at the transition. I'm hoping a new, faster micro-sd card will fix this.
2. screen doesn't turn off by default, just dims to lowest level. Not that the phone doesn't go into standby when it should, it's just that when you are using it you expect the previous TyTN behavior where the screen goes off after a certain period. Annoying only in certain circumstances; for instance, when you play long audio files at night to go to sleep the screen stays on. Solution is easy: just push the power button. Audio keeps playing. Not a big negative per se, just a new behavior to get used to.
3. Hard to select multiple items (e.g. email) with finger. Used to be you could finger one item and then "drag" down the list, selecting multiple items. Now that causes the email list to scroll. Again not a negative, just a new way of behaving.
4. The camera. Takes forever to actually take the shot. Unless you set it on a stable surface or take long shots in good light, the images are blurry. It's a phone so I don't really care that much...
5. Lack of dedicated button for Comm Manager. You can have a soft button, but whatever... Also I haven't found a way to remap the otherwise useless PTT button.
6. Nobody has uploaded the 'cool' HTC rom. I have to install the HTCHome and Comm Mgr app cabs from the Hermes group. The AT&T roms look boring and are bloated with crapware like Ms PacMan eval version (including the frickin' .cab file) and MP3 files.
7. After hanging up a voice call, d-pad in email stops working. That is, I can use the screen to do actions like select and open an email, but the d-pad and center button don't work. Once the mail is open, I can use the d-pad. Seems like this doesn't happen every time, but it's annoying when it does. I'm sure a software update will fix this.
None of these things would prevent me from buying the product again. I personally find the browser perf about the same as the TyTN - downloading full HTML pages takes a while, but it's a phone so it doesn't bother me like it would if it were a laptop.
M
So how do they handle your #3 issue with the semi-touch flow now? How do you go about selecting multiple items?
I hadn't really thought of it until I wrote this... After some investigation I find that if I hold down my finger on the first selected item, wait, then drag it, it works.
how's the in-call voice quality & signal strength from the kaiser's qualcomm chip, compared to previous htc phones (fo example, ones which featured the TI omap chip)?
and also how's the gps? is it really that much worse than a sirfstar to the point where it would become unusable in a city with many tall buildings?
Here is my very small list of gripes..
1. There is no default hardware button that allows you to change the Sound Volume at any time...like when/if you're somewhere quiet and the phone rings loudly or a reminder pops up loudly. Many devices have Vol Up & Down buttons on the side of the device that will let you do this but with the TyTN II you'll have to either use the default Volume control icon at the top of the screen (which is tough to get to using a finger) or use the HTC Touch panel - assuming you have it enabled in the Task Panel settings. You can however adjust the volume during a call using the thumb wheel--which is nice.
2. For some reason, We can't redirect IE cache, cookies and history to the microSD card. I know there's been discussion about this. When you make the registry change, IE freezes when pulling up sites. When you put it back to the default folder or any folder in main storage memory, all sites work fine. Everything else--email attachments, apps, games, GPS maps, etc. seem to do fine when accessed from the card.
3. No HTC TouchFLO 3D Cube
For some reason, the TyTN II has TouchFLO but without the Cube. I would love to get this iPhone Killer app" working on the TyTN II. I know you guys are working on it!
TEC
I live in the US, and this is the reason why im waiting for the AT&T tilt, i want them to fix all the bugs. When the TyTN came out, the 8525 had less bugs, including the screen alignment thing.
Funny, I had just dumped the VERY unstable GPS enabled HP hw6945 in favor of the then new 8525. I was just about to return the 8525 because it was also pretty buggy and prone to hangs. Then I found XDA, applied the tweaks and eventually new roms and now the 8525 is just about perfect.
I'll have my Kaiser in 2 days and am looking forward to what the XDA wizzards will do with it in the comming months.
But a first release from AT&T is bound to be lacking, and probably bloated with less than usefull widgets.
The good you already know so I wont go into all of that, but after all the hype I'm actually dissapointed with this device.
I am a long time treo user (my last machine being a very stable, but dull treo 680).
Last month I bought the HTC Touch (a FANTASTIC machine, especially with HTC Home). But after the Treo, I still need a keyboard as its basically hard work to enter long messages, even with the SIP keyboard (plus TYTN II has 3G and GPS).
So I got my TYTN II 2 days ago and im not enjoying the exeperience, especially when compared to the Touch which was flawless for me. I find that the machine hangs, isnt that responsive, the sound level is much lower than the Touch (both ear and speaker) and while its supposed to be 2x as fast, it really isnt much faster than the Touch. It does have a better screen than the Touch and many other advantages, but none of these are critical for me. Plus I dont know anyone who uses video calling so I have noone to call with it!!!
But the worst part of the TYTN II is that its a MONSTER in both size and weight. Its like walking around with a brick in my pocket! For example, holding the phone while on a long call is very uncomfortable. I just dont like the form factor (actually I miss my Treos front facing keyboard).
So if you own a Touch, have a BT GPS device, can get by with wifi, and can get the hang of the on-board keyboard then I suggest you upgrade the ROM on the Touch and stick with it. Im sorry i didnt.
That said, now I own this device Im going to try to make it work for me and get used to it, or sell it!
About the size and weight, it should be subjective.
For me, it is perfect, not small, but not too big either.
The thickness is good, less than TyTn but more than Touch.
I have no problem handling and carrying it or making phone, etc.
The device is quite responsive, I dont have problem with it. The built-in keyboard is working fine except that I am not used to it yet, so sometimes I missed the key But, I am working on it (to get used to).
The thing that I dont like:
1. Takes a long time to fully charge from 10% to 100% ! More than 4 hours using USB connection.
2. Need more hardware button to map application I want to be able to switch application by using a hardware button. Well, I can replace one of the button, but ...
3. Camera and video recording sucks on indoor situation (low light), but very good on outdoor.
ekerbuddy said:
The good you already know so I wont go into all of that, but after all the hype I'm actually dissapointed with this device.
I am a long time treo user (my last machine being a very stable, but dull treo 680).
Last month I bought the HTC Touch (a FANTASTIC machine, especially with HTC Home). But after the Treo, I still need a keyboard as its basically hard work to enter long messages, even with the SIP keyboard (plus TYTN II has 3G and GPS).
So I got my TYTN II 2 days ago and im not enjoying the exeperience, especially when compared to the Touch which was flawless for me. I find that the machine hangs, isnt that responsive, the sound level is much lower than the Touch (both ear and speaker) and while its supposed to be 2x as fast, it really isnt much faster than the Touch. It does have a better screen than the Touch and many other advantages, but none of these are critical for me. Plus I dont know anyone who uses video calling so I have noone to call with it!!!
But the worst part of the TYTN II is that its a MONSTER in both size and weight. Its like walking around with a brick in my pocket! For example, holding the phone while on a long call is very uncomfortable. I just dont like the form factor (actually I miss my Treos front facing keyboard).
So if you own a Touch, have a BT GPS device, can get by with wifi, and can get the hang of the on-board keyboard then I suggest you upgrade the ROM on the Touch and stick with it. Im sorry i didnt.
That said, now I own this device Im going to try to make it work for me and get used to it, or sell it!
Click to expand...
Click to collapse
gogol said:
The thing that I dont like:
1. Takes a long time to fully charge from 10% to 100% ! More than 4 hours using USB connection.
Click to expand...
Click to collapse
You mean USB cable connected to computer - it always was like that. Hermes was not different. If you use wall charger, it will get job done quicker.
3. Camera and video recording sucks on indoor situation (low light), but very good on outdoor.
Click to expand...
Click to collapse
Well.. what else can you expect? This is a phone, not real camera, it would always suck in low light. But camera is still pretty good, as for phone - while in good light conditions, of course.
demione said:
how's the in-call voice quality & signal strength from the kaiser's qualcomm chip, compared to previous htc phones (fo example, ones which featured the TI omap chip)?
and also how's the gps? is it really that much worse than a sirfstar to the point where it would become unusable in a city with many tall buildings?
Click to expand...
Click to collapse
Both are really good. I was impressed by call quality, really. In terms of GPS, IMHO there is also nothing to complain about...
hardware audio control
technillion said:
1. There is no default hardware button that allows you to change the Sound Volume at any time...like when/if you're somewhere quiet and the phone rings loudly or a reminder pops up loudly. Many devices have Vol Up & Down buttons on the side of the device that will let you do this but with the TyTN II you'll have to either use the default Volume control icon at the top of the screen (which is tough to get to using a finger) or use the HTC Touch panel - assuming you have it enabled in the Task Panel settings. You can however adjust the volume during a call using the thumb wheel--which is nice.
TEC
Click to expand...
Click to collapse
Actually the jog dial on the side defaults to volume control when you are in a call or running (foreground) an app that has volume aspects, like Media Player or HTC Audio Manager. Agreed that there's no general audio control tho. You can install 3rd party apps to give you one-touch scheme changes - check the Hermes forum for apps like O2+ (DiStefano's cab collection is nice).
Problem after phone calls
There seems to be a problem with the Kaiser. After finishing a phone call on the Kaiser the backlight goes off and stays off and I cannot access the Start menu. I can access all other functions but backlight stays off and one still cant get into the Start menu from anywhere on the screen. I have to press the power off button quickly once and then wait a second, press it again to be able to access the start button or the light to come on. This is definitely a bug in the tytn II and I hope HTC is doing something about this.
Reload63 said:
There seems to be a problem with the Kaiser. After finishing a phone call on the Kaiser the backlight goes off and stays off and I cannot access the Start menu. I can access all other functions but backlight stays off and one still cant get into the Start menu from anywhere on the screen. I have to press the power off button quickly once and then wait a second, press it again to be able to access the start button or the light to come on. This is definitely a bug in the tytn II and I hope HTC is doing something about this.
Click to expand...
Click to collapse
No such problems with my Kaiser. Maybe some specific application is causing such behavior? Try uninstalling some of them, and check - but the best test would be hard reset and check on 'clean' ROM. If problem still persists - get the warranty replacement.
Hi
No such problems with my Kaiser. Maybe some specific application is causing such behavior? Try uninstalling some of them, and check - but the best test would be hard reset and check on 'clean' ROM. If problem still persists - get the warranty replacement.
Click to expand...
Click to collapse
This has already been reported and confirmed by a few people and happens when you have a password word set on the device. If no device password is set it works okay and you will not be affected. Workaround at the moment is not to set a password or press the power button again after a call to get the device back on.
Regards
Phil
strange, I have a password and do not experience this problem (thru 3 different AT&T roms). I'm happy to test it out on whichever rom exhibits the problem tho.
The problem only seems to exist on the official HTC ROM.
Hey guys, I just found the weirdest thing.
You know HTCs piss poor touchscreen performance. (Ie using the touchscreen pegs the CPU at 100%).
From my experience so far this is true in all applications. Full screen,
windowed, Software, D3DM OpenGL, GAPI, GDI. In all areas this bug IS present.
But then I installed Astrawares Broken Sword today and while playing it I found that there's no trace whatsoever of the touchscreen bug in this game.
I'm not sure what APIs they use etc. but I figure it must have something to do with it.
Not really sure what to do with this info just thought I'd put it out there.
(BTW Broken Sword is a great game, if you haven't already you should try it right now! )
when it's running, have you tried seeing how other things operate?
hmm, i use the touchscreen to scroll in opera mini and it's as fast as could be.
we should look more into this, later i may install broken sword and see..
is it a game that you touch to make your character move or constantly hold down the stylus to play?
Im sure a fair number of you will have experienced the same thing where you press a key once and you get like 3 of that letter and sometimes for me the Fn key doesnt work too well either
i've tried like swirling the keys around to move dust etc but it didnt help
maybe i should just send it back? becuase its really annoying
I also have this problem sometimes. Thought it might be a software problem or so, but maybe you are right and particles are collecting there.
Did someone try that on X1?
Well, if there was such a solution I wouldn't have to send my X1 to the service centre. And just delaying it as much as possible, but given that my warranty ends next week, I'd probably have to go down soon. And anyway, it's not just repeats that I'm facing. Sometimes it's the other way round, as in the keyboard not responding unless I press the key down real hard.
Mopral said:
Did someone try that on X1?
Click to expand...
Click to collapse
just tried, and seems to work! thanks
settings-personal-buttons-up/down control
delay before first repeat set to long
repeat rate 3 from fast
works good!
I'd say it works about 80-90%. It does save the X1 from the trash piles, so kudos to the friendly guy who dug up the solution, and no kudos to SE and/or MS who can't think of fine-tuning the keyboard settings before they ship a product that was $800-900 unlocked at launch.
Caveat and an inappropriate rant: I remember doing so much research, and everyone across so many different forums said a hardware keyboard is the way to go if you do a lot of texting. Not true. I find that hardware keyboards require a lot of efforts to press compared to a virtual keyboard, even worse if it's not spaciously laid out, and even worse if, unlike the X1, the positioning of the keys relative to each other is off.
Truth is I type even faster on an iPhone/ipod touch than an X1, without feeling like an RSI is coming on, and it's not because of predictive text entry. It's because my thumbs can use a lot less force on the keys. I believe most people still press way too hard on a touch screen trying to be control freaks.
So the keyboard may be 80-90% improved, but I've got my budget ready for an iPhone. And no more listening, no more being open to suggestions!
beingthere said:
Caveat and an inappropriate rant: I remember doing so much research, and everyone across so many different forums said a hardware keyboard is the way to go if you do a lot of texting. Not true. I find that hardware keyboards require a lot of efforts to press compared to a virtual keyboard, even worse if it's not spaciously laid out, and even worse if, unlike the X1, the positioning of the keys relative to each other is off.
Click to expand...
Click to collapse
Well, I don't want to live without h/w keyboard anymore. And I did a fast typing challenge against an iPhone and won. The guy who wrote on that iPhone was a real freak, had an iPhone since it came out and types really fast...but I love the h/w keyboard on the xperia. If it would not have this double-letter error I would love it even more...Now I'm going to fix it with the solution mentioned above. Thanks!
I just want to add one thing...
The reason I say the fix is 80-90%, is because I think CPU speed and/or power settings might contribute somewhat to the keyboard issue. Once last week, I had the phone plugged into AC, and the keyboard suddenly became free of issues, and responded properly to my typical typing efforts.
Using nueCPL-ClockSpeed v1.3 in an unscientific test, the keyboard produces more mistakes on a lower speed (384MHz), but its Max Performance setting didn't exactly reproduce the AC power remedy.
This is not a very stringent observation at all, but since I am stuck with the X1 for a while, I'll keep on trying I'm betting that the next iPhone will be a significant update, so I have to hold off the purchase for now... and kiss NRGZ28's toes for his rom's.
Sapa13 said:
just tried, and seems to work! thanks
settings-personal-buttons-up/down control
delay before first repeat set to long
repeat rate 3 from fast
works good!
Click to expand...
Click to collapse
for two days, since i set this way, not even one double or missed letter!
i've done everything you've all said but it doesnt work does that mean it is a physical problem?
comeradealexi said:
i've done everything you've all said but it doesnt work does that mean it is a physical problem?
Click to expand...
Click to collapse
really dont know, since i set that way no problem at all.. maybe dirt came under your keyboard
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
Seeing videos of people integrating Raspberry Pis into their cars with OpenAuto got me interested in Android Auto. There is one thing I don't like about it, however: you're just adding another device to pass on audio/video/touch to an external display, from the phone. Why not cut out the middle man?
Back in the good old days of my Xperia S, phones had a dedicated micro-HDMI output. Delicous 60fps 720p (and even 1080p, with the UI drawn at 720p, but for instance video playback in full 1080p), and a free charging/OTG port. However, nowadays, we're stuck with MHL, and unless you have a Samsung phone, which has a proprietary connector, you can't use MHL and OTG at the same time, nor does MHL properly support touch functionality (only in theory), so we need the OTG.
DisplayLink to the rescue. We're going to sacrifice a lot of display smoothness/responsiveness here unless you have a modern phone with a USB 3.0 Type-C port (so you can use a newer high performance DisplayLink adapter), but we can use an OTG hub to get both HID touch functionality and HDMI through the DisplayLink adapter at the same time. More on this later. Also, I originally bought a $6 USB to HDMI adapter off eBay thinking it would be DisplayLink (or a compatible off-brand clone), but it turns out to be the really dodgy Fresco Logic FL2000, which is so cheap because it does none of the clever things that DisplayLink adapters do, and instead just spits out full resolution frames as fast as it can, which is completely incompatible with USB 2.0 or low power devices like phones. I found an affordable HP DisplayLink DVI adapter second hand from a Chinese seller that works.
On to the next hurdle: charging while using OTG. This is an interesting one, as it's not something I really gave a lot of thought initially. I mean surely just using a powered hub and giving the phone 5V over its micro-USB port would work, right? Well, it's a bit more complex than that, but Sony used to have an OTG dock that could charge, so I'm confident once I get the right OTG hub, it will work fine on my Z5. The one I got off eBay wouldn't do anything but charge, and when I opened it up, I saw it doesn't even use the 5th OTG pin, which would explain why it didn't work. I soldered a regular Type-A plug onto it and used my Sony OTG adapter to test, and I can get either charging or OTG, so something a bit less hacky is required. I ordered the Acasis H027, so when it arrives, we'll see if that works.
Touch: I haven't tested it yet. I have an HDMI touch screen in storage at my brother's house, so next time I visit I'll see if I can get touches to register on the phone. Based on my Googling most people on the internet seem to have gotten this to work fine, although there is no touch calibration on Android as far as I'm aware, like there is on Windows.
Portrait mode: this is my personal pet project and what I've been struggling with the most so far. It would be by far the easiest to just use a touch screen in landscape mode, but hear me out. Because HDMI (touch) monitors are cheap anyway, and in the 7 inch to 24 inch size range, bigger usually means cheaper, I want Tesla-style portrait mode. In portrait mode we can fit more screen estate in the centre console of the car than in landscape mode, and a bigger screen = bigger text = quicker glancing = safer driving. And it also happens to look extremely cool. If you have a big car you can probably fit a 20 or 24 inch screen, but I think I'm going for 13 inch. However. Using the DisplayLink Presenter app or the DisplayLink Desktop demo app which as far as I can tell does exactly the same things, I cannot for the life of me get native portrait mode to work. Android insists on pillarboxing portrait mode, and no amount of forcing rotation, setting build.props like ro.sf.hwrotation or persist.demo.hdmirotation works to change its mind. More worryingly, it seems that for the HDMI rotation prop to work, you need to also set persist.demo.singledisplay, which prevents apps from accessing secondary displays, which means DisplayLink Presenter, which itself is an app, cannot mirror the screen output any more and you get a sad single stripe of garbage pixels on an otherwise completely black screen. I probably need help here from an XDA developer, to hack the DisplayLink app, or to develop an Xposed module that causes all apps to draw themselves in portrait mode while the system is actually in landscape mode, or something along those lines. I've tried most things in my power that I could think of, and since my phone is unlocked, rooted, magisk'd and xposed, that is actually quite a lot, but nothing helped. So, uh, help?
Lastly there is DPI, which is one of the easier hurdles that I did solve. Android Auto (in phone mode, so not connected to any head unit) has a ridiculously huge UI on my phone's native dpi, and while I understand the reasons for it, with a larger external touch screen attached it just becomes unreasonably huge. With Tasker set to run "wm density 240" the entire Android UI becomes a lot more suited to a large screen, and even though Android Auto is still pretty huge compared to other apps, it's what I would consider reasonable.
More to come!
So, quick update:
While the screen portrait mode issues were "simple" to fix (although root was definitely required), the touch orientation issues as well as charging-during-OTG require kernel modifications to be fixed. I managed to compile a modified kernel with charging-during-OTG support thanks to @nlra 's work on that front, but I couldn't get the new image to boot.
A few things happened in the mean time:
- I discovered scrcpy
- I got an Xperia XZ3 (which I haven't rooted yet)
Scrcpy seems to be basically what Android Auto does, but for the whole Android desktop instead of only one app. I kind of don't like it because it involves adding a computer in between the display and the phone again (probably a Raspberry Pi), but the advantages are so huge it's basically the only realistic option right now.
Scrcpy:
- Basically always runs at 60fps, even on USB 2.0
- Handles portrait/landscape gracefully
- Integrates display, touch, (audio in a future version), and charging in a single connection
- Doesn't require root (although automatically setting the Android resolution to 1920x1080 and keeping the display on at 0% brightness are things that can probably only be accomplished with Tasker, which requires root)
So basically this simplifies and moves the project further immensely, however there are still some blocking issues right now. Touch screens only work on Windows because in addition to generating touch events, Windows also generates fallback mouse click events for touches, something that Linux doesn't do, and because there is no formal touch screen support in scrcpy, multi-touch doesn't work at all. Audio support also seems to be in an experimental state currently, and is not enabled for regular builds.
I hope ROM1V will eventually implement touch screen support (it's been in his GitHub issue tracker since March) as I have enough work to do as it is. I will focus on the hardware part (Raspi, cabling, VESA mount etc.) first and if by that time touch support is still missing I'll take a crack at it myself. Thankfully scrcpy is built on SDL which I'm fairly familiar with, although I've never worked with the touch input API before.
For the charging you need hub with usb-c PowerDelivery passthrough and HDMI. I am testing ones with less power consumption right now. I am not sure why you weren't able to use it.
I think people would be better of using following app for changing resolution, etc. using SecondScreen (I think root is required to run HDMI in portait mode, because it is grayed out for me).
I am doing the same project, but I keep the screen 1600x1200 horizontally and use apps in split view mode. I don't want root. I was thinking of using SamsungDEX for it, but the menus are too small.
The good thing is though, that on Samsung it is possible to create two-apps split screen pair (e.g. google map + music) as a launcher shortcut (using Good Lock (MultiStar plugin) from Galaxy Store). Unfortunately, I don't think it is possible to automate launching two apps in split screen automatically, nor create a split-pair shortcut on other launchers.
It would be good to have some multiwindow manager since I also wanted my BMW-tuning/logging gauges app to run in a floating window on top or minimized to a floating icon. It is possible naturally but it is a lot of manual clicking :/
One more thing that I don't think will be possible, is to completely turn off the phone screen. With the screen on, Note8 doesn't do fast charging. Can the screen be off with scrcpy somehow, I don't think?
So this dead?