Database Users

Any one single issue that may stop me buying?

so, i've no doubt that many of you have been using your HD2's for a while now, during your experiences have you noticed any one significant problem? For example, the SMS sending issue or maybe with push email on the battery life is awefull?
What is your single biggest issue with it?

The biggest issue for me was the SMS problem. Now fully corrected by HTC. I'm proud of my little Leo I use mine with email in push all the day, and I've about 30% at the end of the day, using my phone every minute

My only real issue is the ultra slow messaging system. Not the sending bug which is apparently fixed. This is just where it takes forever to load your messages making you wait before you can type and send your message!
Very irritating problem but not a show stopper! Still loving the phone
I get 2-3 days of light use(Dont use it much at work just texting) and at least 1 day of heavier use(sitting browsing the web, playing music etc on the weekends). I have a second battery with me most of the time just incase i let it run out

There's tons of information already on here to help you make your own decision.
The question YOU have to answer is whether there are any deal breakers for you from the stacks of info that is already on here. This thread, for example, is a good place to start...http://forum.xda-developers.com/showthread.php?t=583638
There are just so many threads on here now where people are effectively asking others to make a buying decision for them/asking exactly the same thing. The unique features of the HD2 will remain the same no matter how many times this question gets asked.
At the end of the day, whether you buy or not is entirely down to you.
WB

i've read that thread, usefull but far from concise. I am of course reading taking particular interest in this sub-forum, reading much of it but....
I'm not looking for what "most" people are looking for. I've left this fairly open ended question in the hope(?) that someone will mention what is a fairly unobvious to the masses issue but is a serious issue for them.
I'm looking for something that might be silly and therefore probably not mentioned by most of you but could stop it for me. I don't know what "it" might be but for example it could be that you can't put delivery receipts on a text message ....
I will be using ALL the functions of this phone and I wan't to try to eliminate any suprises!

Power hungry!
For me it's the power hungry nature of this beast. You can actually watch the battery draining right before your eyes if you are using it to surf or watch movies. I was shocked just how fast it drains.
Got a second battery now which I keep with me at all times. Batteries are the achilles heels of these powerful mini devices and I am very much looking forward to the new 3D lithium ion batteries becoming widely available as this will surely revolutionise mobile phones. Sorry going off topic there!

Can't say there's one MAIN problem, but it takes a lot of work to get it set up and running how you want it to, especially if you are unfamiliar with Winmo as I am

Hello again,
I quite understand where you are coming from but the approach I would have taken would be to make a private list of all the functions the device absolutely must have for you to be happy with it then confirm there aren't any issues with those functions through the info on here, sufficient for you to say no.
The key thing you have to remember, which new adopters from other devices don't realise, is that the HD2 isn't really a phone in the traditional sense. Its more like a small computer with telephony and messaging capability added on.
It therefore has much in common with the behaviours of a Windows computer (not surprising really as the OS is a "miniturised" version of windows). What kills it for a lot of people is that they expect it to behave exactly like a Nokia phone which it won't.
For many of us who have used winmobile devices for years, the things that may well be deal breakers for you just would not come up on our radar, hence my suggestion above of a different approach from you to get to a decision point. Being able to tweak the device, for example is a major plus as this gives great flexibility to customise the device. That attraction for me is a major deal breaker for others.
I would wager that there is a direct correlation between the numbers of people new to the winmobile platform and the number of posts on here expressing dissatisfaction with the device in one shape or form (SMS issue aside, of course).
Hope this is helpful.
WB

Indeed it is WB! very welcome and very helpfull.
Been in WinMo for years and very skilled with it so its not a new device to me.
Also spent many years in support roles so very adept at extracting relevant info from a mass of other stuff.

Monty Burns said:
so, i've no doubt that many of you have been using your HD2's for a while now, during your experiences have you noticed any one significant problem? For example, the SMS sending issue or maybe with push email on the battery life is awefull?
What is your single biggest issue with it?
Click to expand...
Click to collapse
I dont have these issues at all. As long as you dont mind tweaking things here and there, I think you will enjoy the experience.

Monty Burns said:
...
Been in WinMo for years and very skilled with it so its not a new device to me.
Click to expand...
Click to collapse
And here was I , thinking you were a mere babe in the woods.
WB

It's a great device, but before buying one, I'd suggest to test it if you have the possibility...
In eastern Europe there were very many faulty devices; was unlucky to get one myself...

thanks but won't have that issue, we are very well protected in the UK when buying from a shop.

If you have experience with past WM devices, then the HD2 will blow your socks off!
I've had WM since my MPX200 back in 2004, and the HD2 is by far the best WM device ever, even with it's few minor niggles (and be realistic, what phone doesn't have niggles?).

Well, my main issue was the crappy messaging but with the latest sms-hotfix that is also corrected! No more issues now... loving it every single minute!

No Voice control over bluetooth
Have had an HD2 for a few weeks now, and while it’s a great machine in most respects, the main deficiency for me is the lack of voice control over bluetooth. It's mentioned in quite a few other threads.
I ride a motorcycle and have used a helmet mounted scala-rider headset with a Dopod 838Pro for a couple of years (mostly for initiating and receiving phone calls, but occasionally having messages or calendar entries read out).
The lack of this function on the HD2 is a major drawback for me, and I imagine anyone for whom voice control is important (eg. if you drive/ride a lot).
Have had WinMo since before there were WinMo phones (HP 620lx, then XDA II, then JasJar, JasJam and now HD2) and I bought an iPhone 3GS (surreptitiously for my girlfriend) to see what all the fuss is about and to see for myself if the device is as good as the fanboys in my office gush on about.
I hate the way it's all locked-in to iTunes and you can't really tweak things to the level we're used to with WinMo, but everything "just works" (wi-fi, voice control, SMS conversation mode etc.)
If the voice control isn't enabled in an imminent ROM update I may have to consider selling my HD2 and begrudgingly keep the iPhone for myself.
Just my opinion – hope that helps with your decision.

For anyone with a previous satisfactory experince of winmo it's a no brainer...go for it! I personally had all sorts of problems years back with an Orange MDA and was slightly nervous about going down that road again but so far my HD2 has lived upto and exceeded all of my expectations. My requirements boil down to:
Must work well with a bluetooth headset in a noisy place (I drive a truck)..it does!
Obviously must function well as a phone..it wouldn't be any good if I couldn't speak to anyone but no problems whatsoever on that count!
Must have decent internet access...it does (grabbing e-mails and surfing all day)
Must let me tweak it to add various apps..it does (6 sat nav progs and still adding them!)
Texts I use very infrequently as its easier just to speak but the texts I send and recieve seem to be fine (and thats without any hotfix applied!)
My only slight concern is battery life but as I'm near a charger all day long its no biggy and I've yet to address this with any of the tweaks floating about.
thats my twopenneth..
just seen the post above me...I use Cyberon Voice Speed Dial which works fine for me but as I have to tap a button on my headset to fire it up I guess it's not much use for you (unless you drill a hole in the side of your shoei so you can prod a button)
Retraction time...owing to a PM from Lordbowl I've just checked and it would appear that CVSD actually uses the mike on the HD2 and not the one on my bluetooth headset to obtain the info about which contact I want to call so it's not much use if you are wearing a helmet!

bzdemes said:
My only real issue is the ultra slow messaging system. Not the sending bug which is apparently fixed. This is just where it takes forever to load your messages making you wait before you can type and send your message!
Very irritating problem but not a show stopper! Still loving the phone
Click to expand...
Click to collapse
This was fixed yesterday!

Monty Burns said:
so, i've no doubt that many of you have been using your HD2's for a while now, during your experiences have you noticed any one significant problem? For example, the SMS sending issue or maybe with push email on the battery life is awefull?
What is your single biggest issue with it?
Click to expand...
Click to collapse
To be honest, if you are lucky you may end up with a zero faults device, but you my also consider,that you may have the sms problem which is not solved as many here seem to say.
Also you may get the pink spot that even with htc fix it will still there but not as ovieuse.
Also you must take in consideration that you cannot trust your future phone for making calls, because some times he does not wake up.
And must take in consideration that you may end up with the noise bug while in a call. plus many littel other bugs that you can live with (extrimily difficult to type,with out faults) the screen is over sensitive......Hope it helps for your desition

Audio Booster
Since the SMS outbox bug was fixed yesterday there is only 1 bug that irritates the crap out of me... Audio Booster needs to be re-enabled for every song that is played using Audio Manager unless you want untouched EQ.
I have tried setting AB & hitting "Done"/Home/Back but whatever I do it still dies after 1 or 2 tracks.
HTC reassure me this is to be fixed in a future release otherwise I would be looking for other alternatives.
I think the HD2 is a fantastic piece of kit but let down by HTC's bugginess.

Let's face it: HD2 has many problems.

No need to hide. This phone has many problems, still many people seems to ignore them completely. No need to start the "It's your phone, it's strange, I use it a lot and it never happens" saga. The problems are there. And for everyone. The fact you don't notice some bad behaviours doesn't mean the phone is perfect or that your baby is exempt from problems. Let's start:
1) Suboptimal WI-FI performance. On a 802.11g wireless network, connected to an 8Mbps internet connection, the phone can't even saturate the badwidth of the network. Speedtest.net reports an approximate 2Mbps download capacity (EDIT for those who cannot distinguish: 2 megabits, not megabytes). Test it yourself: try to download something from a fast website and try to figure out which is your maximum download transfer speed. You will be disappointed. As a comparative, this means the phone can use 1/4 of the available bandwidth. A SonyEricsson Satio can fully use the available bandwidth, instead (someone told me "tell me a phone that can do it. Now you have one).
2) Stanby freeze: it's there. The phone freezes randomly while in stanby draining all your battery juice. Sometimes happens rarely, sometimes happens frequently.
3) Poor memory space handling: after just 20 days of use from a fresh ROM update, my free memory space on ROM is just 36MB. Without installing big things or hacking anything. Sure, there are fixes produced by the community, log cleaners, temp files deletion utilities, etc. etc. Still, it's a quite a disappointement: it means this phone can't work properly in a "factory state" for much time.
4) "Always on" features: nice, apart the fact in random periods of time the services just stop to download data. The Twitter client doesn't work well. Sometimes you can hear a tweet sound, sometimes it downloads data without the sound, sometimes it downloads nothing until reboot.
5) Poor stability in general: the OS crashes frequently. Less frequently than the first shipped rom. Still it's not very stable.
6) Poor support in general with the updates: finally the SMS stuck problem has been fixed but they spent 3 months for it without a valid solution. The camera fix doesn't hide the fact the sensor is defective.
I don't say this to start a flame, of course, but only because I'm frustrated with these problems. And people, instead of spreading words about them, just pump the hype, including some notorious web sites that have no scope but pushing the hype even further. But the truth is another: this phone doesn't work as expected.

I honestly do not have the problems you're describing..
Your "truth" is very different from mine, but ne1 is allowed to have no

Can't comment on all those, but i hear you, defo had some of them and i'm on my 2nd unit after 2 weeks.
With Nokia it took them at least 6 months to iron out the flaws in their released phones, defo the case with N95 & N96, i didn't expect it to be the case on this phone.
SMS fix? is it? or only in 1.66, because the hotfix's don't work on the 1.44 ROM
I would like to add the Audiobooster problem to that list

well, I don't pretend mine is perfect but there are more things to love than to hate about it. regarding the problems, I think you cannot generalize because I've never experienced some of your issues but I'm bothered by other myself. finally I guess it's just a subjective call anyway...

I had some of your problems when my HD2 was on the original 1.48 WWE Hong Kong ROM. However, since I flashed HSPL, Merlion LEO V1.90 ROM and Radio version 2.07.50.27_2, it's been faster and absolutely stable. No more freezing/"Sleep of Death"/etc...

jonbaker76 said:
I would like to add the Audiobooster problem to that list
Click to expand...
Click to collapse
That one really annoys me too. Still can't find a way to get video and audio in sync without manually adjusting the offset whilst encoding. And HTC still can't get the hang of getting Audiomanager to handle AAC files properly (ie sort albums in track order, or show.their album art). Still, it's a lot quicker than my Touch Pro was ; )

Yeap! I'm very happy that I could be refunded. Too many bugs for such a device.

^
If you want something that works out the box, get an iPhone

I have none of your issues and i can prove it with tests and videos.
I wish i had an "unlike" button to use it here. You are frustrated because either you don't know how to work with this phone or you have some bad software or even a bad phone. Replace it!
You are emitting false statements here!
PS: I have the phone for 2 months.

I'd love to see a phone or device that was perfect.
Every piece of hardware has its own problems.

I've been waiting for so long for someone to start a thread entitled as "Let's face it: HD2 has many problems". Eagerly watching this thread for some positive and negative input.
All in all, HTC Sense is at it infant stage. This "is" the culprit. Perhaps by end of this year, we will worship it someday...
To the developer/creator of HTC Sense, please use your common "sense" when trying to convince people to buy your idea. The first major mistake was SMS failure. Totally non-Sense.

1. have to say the WiFi (at work) is slow (2.2Mbps) but speedtest.net is SO unreliable I'll hold off commenting until I try at home tonight on my O2 LLU connection.
2. never had it
3. doesn't happen to me, currently got 107MB free of storage and 266MB of program memory free
4. other than Twitter client being a bit crap it's fine
5. mine doesn't crash
6. updates are fine but I've not had any of the issues others have had in the first place, less so now running a custom ROM

Return your phone and get an iphone/android device.
This kind of issues, even if I haven't myself had most of those you list, have been around with EVERY WM phone that has been made.
Of course WM is far from perfect, but as someone already said to me the advantages far outweigh them, and I can live with them and the need for tweaking.
1) Wifi speed, show me one phone that can transfer at full G speed. The processing power/memory bandwidth/flash memors speed can't handle that.
It also depends a LOT of the software used.
I do get 1-1.5MB/s (8-12Mbps) transfer on wifi between the HD2 and one of my home computers, with WiFi remote access, and on balanced wifi performance. With Resco explorer, I get 150kB/s...
2) Never had one.
3) Depends... could be just normal, now that the album and browser caches have reached their limits, and would stop there. Stock ROM has a lot of useless stuff on it.
etc...

dgtel2 said:
To the developer/creator of HTC Sense, please use your common "sense" when trying to convince people to buy your idea. The first major mistake was SMS failure. Totally non-Sense.
Click to expand...
Click to collapse
Sense is fine, but the vanilla Win6.5 fails hard.
And if this thread gets to about page 5, it would probably just turn into another Leo vs iPhone flame war.

For the WiFi "problem": ~ 2 MByte /s is just the normal average speed, even with my laptop I won't get much more on 802.11g .. It also depends on with how many other devices you share your WiFi-channel.

btyeh said:
Sense is fine, but the manilla Win6.5 fails hard.
Click to expand...
Click to collapse
What is manila win6.5?!?! Do you even know what manila is? manila = sense!!!

I think there are a lot of 'duff' units, this must be the case with the 'sleep of death' and the crackley call as many of had it but most don't.
I took mine back, got a new one yesterday, no crackles no sleep of death... yet
But true, there are always gonna be problems, it will take months before a near perfect firmware, sorry, rom is out

Thank god for my HTC HD2. No problem here beside the screen shaking. But I hardly notice it.

kilrah said:
1) Wifi speed, show me one phone that can transfer at full G speed. The processing power/memory bandwidth/flash memors speed can't handle that.
It also depends a LOT of the software used.
I do get 1-1.5MB/s (8-12Mbps) transfer on wifi between the HD2 and one of my home computers, with WiFi remote access, and on balanced wifi performance. With Resco explorer, I get 150kB/s...
Click to expand...
Click to collapse
SonyEricsson Satio, for example. I download at 900Kb/s with it on the same network (using the same browser, Opera Mobile 10 Beta 3). Poor implementations doesn't mean it's not possible. Do we need 4Ghz quad core processors to use a wireless g network? Obviously not.
3) Depends... could be just normal, now that the album and browser caches have reached their limits, and would stop there. Stock ROM has a lot of useless stuff on it.
etc...
Click to expand...
Click to collapse
A bad behaviour, even when happens at factory settings is still a bad behaviour. You have a strange definition of "normal". Surely a phone that in 20 days saturate all the available space on the rom cannot be considered "normal". It's a poor implementation of things. A good implementation would have addressed it from the start by allowing the user WHERE to store that files or giving him an option to clear that files without an hard reset. No, it's not normal. Software design it's a much more complicated thing than those "normal" things.

You know you have problems when your best programs are Hd2tweaks, Bsbtweaks and Resco registry editor. And you are continually wiping out your system and trying new roms. Although Xannytech evolution was a good one.

Impressions after a week...

A lot of us have had the device for at least week now so it would be a good time to post impressions after a bit more hands on time. I’ll start...
10 days in I’m still glad I got it but there are plenty of things that could be improved. I’ve been on HTC phones (Desire, Desire Z) before this running at different times standard HTC Sense ROMs as well as various versions of Cyanogen Mod and AOSP based ROMs. My views after 2 weeks of use:
* Loving the fact that Samsung appears to be treating this almost like a developer phone (ala Nexus) in terms of open bootloader, availability of source code etc. I’ve said my goodbyes to HTC precisely because of this.
* Based on the frequency of updates Samsung also appears to be focused on addressing issues. They are one if the first out of the gates for Gingerbread updates to their existing devices so I’m hoping they continue to focus on delivering on the latest versions of Android.
* Touchwiz is not as invasive as HTC’s Sense. It improves on stock android in many ways. My first Samsung phone so I can’t really speak of improvements over previous versions of Samsung ROMs but so far I don’t hate TouchWiz but I do find that they seem to take a lot of inspiration from Apple even when the standard Android implementation is better in some cases (I didn’t hate HTC Sense either but I did find it too far from stock for my liking). Having said that there are some totally brain dead decisions that Samsung appear to have taken which I just don’t get:
1) Default home screen on the left instead of the middle. Why copy Apple on this one when Android’s default makes so much more sense. I love having frequently used apps with a swipe to the right and an agenda widget on the left so I can get to both with a single swipe. Now I have to pick one.
2) Fixed icons at the bottom. I understand Phone and Apps being fixed but not messaging and contacts. I’d like to change those - hell, even Apple lets you change those. *** NEVERMIND *** See posts below. It CAN be edited.
3) Lock screen - talk about making something worse - this one takes the cake. Thank god for widget locker.
4) Dialer logs - I don’t want my SMS messages to show up on my phone dialer logs. There is no option to just view all calls without the rest of the stuff cluttering it up. (Yes I know I can switch to Dialer One but apart from this one major issue I actually like the default Samsung dialer).
* Wireless - Everything wireless about this phone has issues. May be a function of how thin it is but my experience so far:
1) Phone - Much improved after the latest firmware updates but data connection can take a while to latch on when moving out of WiFi coverage and sometimes just drops out for 5-10 minutes at a time for no apparent reason (even when the phone shows five bars in a strong signal area).
2) Bluetooth - The headset I have is not working well at all. Quality seems fine but every few seconds drops out or gets noisy for a second or so. The same headset works perfectly well with the HTC devices as well as with an iPhone.
3) GPS - Sometimes flawless but lock time is definitely a lot slower than the HTC devices. It also has a tendancy to lose lock a lot easier than the HTC devices. Other times it jumps around all over the place before getting a lock. Lots of weird behaviour here.
4) WiFi - Where other phones get weak coverage this one gets none. If you have strong WiFi signals everywhere you use the device this is not an issue. 5 Ghz also performs significantly worse than 2 Ghz.
* Battery life - It appears this phone has only 2 gears. A low gear for phone / SMS / push mail / browsing where battery life is excellent but then kicks into hyper-turbo mode if you use Flash video, games or anything taxing where it burns through battery life in no time. You can easily get through a whole day with power to spare if you stick to only the basic activities but best to use everything else while plugged in.
The reality is even with all these issues, I couldn’t give this device up. The power and speed coupled with the slim form factor and gorgeous screen are just too damn impressive and all the problems pale in significance. I might have had buyers remorse if the HTC Sensation was coming with an open bootloader and a slimmer profile but at the moment I don’t see anything that compares. I’m just hoping Samsung can fix some of the problems I’ve listed in software.

Regarding fixed items at the bottom: you can edit them from within the applications screen.
Sent from my GT-I9100 using XDA Premium App

2) Fixed icons at the bottom. I understand Phone and Apps being fixed but not messaging and contacts. I’d like to change those - hell, even Apple lets you change those.
You can change those - Go to app drawer-> menu -> edit -> and drop the app you wants.

EleCtrOx666 said:
You can change those - Go to app drawer-> menu -> edit -> and drop the app you wants.
Click to expand...
Click to collapse
Works! Thanks

Interesting thoughts indeed.... I hope there is some help out there ^^

Here's a solution for 1
http://forum.xda-developers.com/showthread.php?p=13825680#post13825680

Nice honest and informative post. Most of the issues will hopefully be fixable once we start getting some custom ROMs I'm hoping. Or hopefully fixes direct from Samsung in regards to GPS, WiFi, and 3G. I guess time will tell.

gstar_raw said:
Nice honest and informative post. Most of the issues will hopefully be fixable once we start getting some custom ROMs I'm hoping. Or hopefully fixes direct from Samsung in regards to GPS, WiFi, and 3G. I guess time will tell.
Click to expand...
Click to collapse
Very puzzling that Sammy would have issues in key connectivity areas on such a high profile phone. Wonder if they''re all antenna related? As you say, hopefully not, and it's all solvable with SW.

Homescreen order
C'mon guys - it's not that hard to reorder your homescreens...
Just pinch zoom (helicopter mode) longpress & drag.....
Hope this helps you...
---
Regards,
Ian.

EleCtrOx666 said:
Here's a solution for 1
http://forum.xda-developers.com/showthread.php?p=13825680#post13825680
Click to expand...
Click to collapse
Thanks! Will try it.
BatterBits said:
C'mon guys - it's not that hard to reorder your homescreens...
Just pinch zoom (helicopter mode) click & drag.....
Click to expand...
Click to collapse
The issue isn't re-ordering. It's changing the default home screen from the left (on TouchWiz) to the middle (As on stock Android / Sense etc)

Abra_Cadabra said:
Thanks! Will try it.
The issue isn't re-ordering. It's changing the default home screen from the left (on TouchWiz) to the middle (As on stock Android / Sense etc)
Click to expand...
Click to collapse
in the old TW, it allowed users to change the default home screen. I have no idea what happened to the new TW

Abra_Cadabra said:
Thanks! Will try it.
The issue isn't re-ordering. It's changing the default home screen from the left (on TouchWiz) to the middle (As on stock Android / Sense etc)
Click to expand...
Click to collapse
Doh!
Sorry, Didn't quite catch that - I understand now where you're coming from.
<note to self - dont respond to posts you haven't read properly>
---
Regards,
Ian

After my first day with this phone I switched to the the ADW Launcher, Samsung really didn't think the TouchWiz launcher through - not only the default homescreen being on the left, but also the fact that Apps in the drawer aren't sorted alphabetically.

I used to own the Samsung Galaxy Vibrant. It's disturbing that Samsung is still not getting the GPS working right!

briansj said:
I used to own the Samsung Galaxy Vibrant. It's disturbing that Samsung is still not getting the GPS working right!
Click to expand...
Click to collapse
My gps works like a charm
Sent from my GT-I9100 using XDA App

I'm on the latest firmware but it's still pretty buggy...
I've tried switching to launcher pro but I still get crash reboots and loss of sound.
Last night I entered the pin and the phone just reboots.
I also loose the clicks on the pin screen. When this happens you have to reboot go get audio back...I tried playing an mp4 video with no sound when it was in this state and it just said unable to play. Of course it worked fine after a reboot...
So pretty buggy at the moment

mine has no bugs or what so ever, after 2 weeks of used i can never compare it to other phones performance either android or iOS,i used both before but this one is simply way above them..

no built in stock music widget was a dissapointment for me as well as the horrible lock screen style and the lag during wakeup..apart from that this phone is really amazing..but touchwiz needs some serious thought...
Sent from my GT-I9100 using Tapatalk

Agreed that this phone is as speedy and steady as the HTC Desire and iPhone 4 that I have owned. The trick to all these phones is that if you play around too much with settings,tweaks,launchers you are likely to get problems.

[Q] Sleep/Charge death issue, think I've tried everything...

Hey guys!
I've got 2 of the T-Mobile HD2 handsets, both 'yellow reset button' revisions. One runs Windows Mobile 6.5 (have yet to find an alternative for texting through Outlook/Exchange), the other running some flavor of Android. This setup has been working just fine for months, but last month I started experiencing random restarts, sleep death, and charge death. In two known instances, this happened during calls.
Now having been educated on How to ask a question properly, I have done my best to attempt all the due diligence I could muster...
--The Android handset is presently running the Nexus ICS 1.5 ROM with the Dormanix ICS kernel. After the first few random restarts, I tried it with the regular kernel (tyung's?) and had the same issue. I then reverted to my mainstays of Typhoon Cyanogen and Hyperdroid, both with stock kernels, both demonstrating the same issue after the first day or two.
--I've tried every radio release from 2.10-2.15, being careful to only install the '50' releases, not the '51's. None of these have alleviated the issue.
--I used setCPU to try overclocking, underclocking, then just set it back to stock and uninstalled setCPU.
--The most recent format attempt, while I didn't task29, I did format /system and /data from within CWM.
--Also with the most recent attempt, I didn't install any backup software or create any backups, except with text messages through GoSMS. I did not restore any backups with Titanium Backup or MyBackup Pro.
--I have not uninstalled any system apps with ROM Toolbox.
--I have tried updating my CWM install version to 5.x.
--I have attempted switching the OSes of the two handsets; both have had the same issue with Android but neither have SoD'd with Windows Mobile.
Just about the only thing I haven't tried was switching the the cLK bootloader instead of MagLDR; my logic for not doing so is that I do keep an archive of all the old versions of the ROMs I've installed so that, in cases like these, I could try some older known-stable-to-me releases, and all the ones I've downloaded were for MAG. Additionally, none of the other threads I read indicated that the seemingly mature MAG platform was found to be the cause of anyone else's issues; all the other threads seemed to relate to either titanium backup restoring something in an extremely wonky manner, or an unstable/incompatible release of the baseband firmware.
The only other thing I could think of that could cause the issue that started roughly around the time that this problem started was my use of LBE Privacy Guard. I'm hesitant to blame LBE for the following reasons:
1.) LBE has been perfectly stable on my Incredible 2.
2.) LBE hasn't been blamed for any of the other SoD issues discussed in these threads.
3.) The Google Play page for LBE indicates no such issues reported in either the dev writeup or the first five pages of reviews.
4.) The SoDs don't seem to coordinate with the times that LBE blocks things.
5.) Uninstalling didn't make the issue go away.
However, given the nature of LBE and the kind of low-level access it gets to the system, I felt it worth mentioning.
Thanks for reading my lengthy plight; any assistance (including thread links if I missed a thread in my searches) would be greatly appreciated. In the meantime, I'm going to give Task29 and installing CLK a try.
Joey

Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Have you ever felt that your device is overheating or lagging a lot ?
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )

Marvlesz said:
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
Click to expand...
Click to collapse
I do my best to walk all the beaten paths before I ask for help. If I'm going to ask everyone else to spend their time helping me out, the least I can do is demonstrate that solving the issue is worth my own time.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Click to expand...
Click to collapse
I've got five different batteries I rotate regularly. Two do admittedly need replacing, but the batteries all work perfectly in the WinMo handset. Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Click to expand...
Click to collapse
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Click to expand...
Click to collapse
The closest I had to that was a radio revision whereby the bootloader never got past the 'loading' prompt, but neither that, nor the MagLDR install, nor any of the radio installations I've tried have required a reflash due to a botched installation attempt.
Have you ever felt that your device is overheating or lagging a lot ?
Click to expand...
Click to collapse
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Click to expand...
Click to collapse
Not weird, perfectly understandable, and I'm pretty good with keeping my gear unsmashed
Hope it helps!
Joey

voyager529 said:
Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Click to expand...
Click to collapse
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
voyager529 said:
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Click to expand...
Click to collapse
From the redded part, I can understand that the issue started on Alpha, and soon thereafter it had affected Bravo.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Maybe an sdcard ? Have you tried booting android from sd? have you tried booting android from NAND without an sdcard?
voyager529 said:
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
lol, okay then, it's not the device overheating.
Let's narrow it down, your both devices started to have charging/screen issues. With a relatively close time from each other.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
You also said that: on Winmo, both devices ran fine and on Android both devices had SoD's .
This may mean, the ROM you are/were using is simply malfunctioning. Have you tried various ROMs or it is just one ROM ?
Sorry for being late, awaiting your reply

Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
Click to expand...
Click to collapse
Ironically, Bravo (the one presently running Android) was warranty replaced less than a month ago due to an actual, legit unresponsive screen. The fact that the pattern is consistently "screen stops responding/SoD/CoD -> hot reboot -> phone resumes working perfectly", and has been on both phones, leads me to put that particular explanation towards the bottom of the pile. Rather selfishly, the supplemental reason to that is that T-Mo isn't going to honor a warranty replacement for an issue that only happens on an operating system that is an unofficial port, so if it is some bizarre hardware issue, it's gonna be mighty expensive to get the phone swapped.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Click to expand...
Click to collapse
I have a thought about that that I'll get to in a moment...
Have you tried booting android from sd?
Click to expand...
Click to collapse
No. good catch =)
have you tried booting android from NAND without an sdcard?
Click to expand...
Click to collapse
I always use the NAND methods, but data is a bit hard to store without an SD card. You have inspired me to do a MicroSD shuffle though. I'll give that a try.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
Click to expand...
Click to collapse
That is, in fact, the answer lol. Originally, Alpha ran Android and Bravo ran WinMo. This problem started, so I switched them around: Bravo was configured to run Android, and Alpha became the WinMo phone. Alpha, which would SoD with Android, has not done so in the weeks since it became the WinMo running handset. Bravo, now sporting Googleware, exhibited the same issues.
To answer your last question regarding whether it was the ROM, I tried the ICS ROM with stock kernel, Dormanix's kernel, Typhoon CyanogenMod (the most reliable in my experience), and HyperDroid. All of these ROMs did the same thing after the first day or two, but hadn't done so in the past: I used both the latest release and older releases that I've used and am 100% certain have worked for me, on my hardware, without fail. As such, this is starting to ratchet back to being a PEBKAC/ID10T issue, but I was never able to pinpoint anything specifically that would earn me a dunce cap. This morning though, I had a breakthrough...
Yesterday, I decided to ditch MAGLDR and opt for CLK instead. I must admit that I do greatly prefer MagLDR, but I was determined to try as many things as possible to get to the bottom of this. I Task29'd, got CLK in along with CWM Recovery, Flashed the ROM again, and started restoring apps from the Google Play Store. No reboots at this point, but then again, most flashes have worked wonderfully the first day. As an aside, I'm torn: I do like the greatly decreased boot time and increased internal storage availability, but MagLDR was much simpler to work with for frequent flashing chores. Oh well.
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Thus, I have foregone MagLDR, foregone ATK, and foregone pulling out stuff in ROMs I don't want. Also, I bought the GOTO lockscreen to help me get rid of the camera launching problem. So far, my system uptime is 6 hours, 14 minutes
Joey

voyager529 said:
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Click to expand...
Click to collapse
lmao !! xD
But that is weird. Why would your phone reboot when the app is frozen ? When you freeze an app, it disappears from the app launcher, but being available on the lockscreen may be the cause.
I don't think it's ATK, since I was on the SD versions of Android, I used to use ATK. And never had a problem. On the other hand, I did notice some random reboots on ICS after freezing some system apps with Titanium Backup.
That said, these reboots shouldn't occur when on typhoon, Hyperdroid or any non-ICS ROM, should they ?
I'm still confused about this "Originally, Alpha ran Android and Bravo ran WinMo. This problem started"
There is no way in hell, two separate devices, would face the same issue without any relation.
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )

Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey

voyager529 said:
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
Click to expand...
Click to collapse
I don't know if it was just me not reading this whole thing properly (which it probably was, given the amount of information you're providing) but you never seemed to have actually answered the questions about bent battery pins. You mentioned that you are often swapping batteries which makes the battery pins vulnerable to being unintentionally bent out of shape, and they may not be making contact with the battery properly. I have no clue as to how this would really help you (maybe the reboots, not the screen issue), but it wouldn't do any harm to check it out
---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------
Marvlesz said:
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Click to expand...
Click to collapse
Didn't see this earlier, but surely the question is 'why would you leave the HD2 on the world's worst OS?'

I'm disinclined to believe it's the battery pins for the following reasons:
1.) in certain cases, the screen is unresponsive, but the send/end buttons light up, indicating that power is indeed flowing.
2.) in certain cases, I've had the phone do a 'hot restart' (i.e. not going through the bootloader, just showing the boot animation) mid phone call or during other kinds of use. If it was a momentary disconnect, wouldn't it be doing a complete, cold restart?
As for why I'm using Windows Mobile, two reasons:
1.) Android has been giving me issues lately, as this thread clearly illustrates. For all the crap Windows Mobile 6.5 gets, it's been pretty stable, ALWAYS rings, is significantly less demanding on battery life.
2.) Its killer feature for me is that it enables text messaging through Exchange/Outlook 2010, something no other mobile OS presently provides. Additionally, it does all of the core phone functions I use (calls, texting, tethering, web browsing with Opera Mobile, Facebook notifications/caller ID sync, USB mass storage, video/music playback, Swype input, etc.). It might not have 100,000,000,000,000 apps, but the Sencity flavor of EnergyROM is extremely reliable.
Joey

voyager529 said:
If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
Even if you can't feel it overheating, try putting it in a cool place for some time until you can feel that the aluminium back cover is cold to touch, then do something which would normally cause a hot reboot or any other issue. An open window with a slight breeze is normally good enough to cool the phone down (so long as it isn't too sunny or hot obviously).
I guess you're right about WinMo being the most stable OS (although from what I've heard WP7 is very good as well) but I just couldn't live with it. Even if I started experiencing large issues I would do everything in my power to not use that OS again! Used it the other day on my friend's HD2 which he now keeps purely as an alarm clock and it's ghastly, I found it painful to use again.

voyager529 said:
I'm disinclined to believe it's the battery pins for the following reasons:
Click to expand...
Click to collapse
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.

Marvlesz said:
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Click to expand...
Click to collapse
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey

voyager529 said:
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
Click to expand...
Click to collapse
Ah, OK thanks for clearing that up (I, like Marvlesz, thought you simply were refusing to check the battery pins for some odd reason). Did you try the fridge trick? I've read in many places that it works for some people, maybe it could help you too (although don't leave it in there for too long; I'm no expert but I would assume phones aren't designed for that ) and report back.

Just thought I'd follow up with everyone...
On April 22, I task29'd, MagLDR'd, and installed HyperDroid-CM7-Observant-Opossum -v5.9.0. Since then, my phone has been working properly.
Thus, I am chalking the whole ordeal up to one of three things:
1.) an issue with a backup of some kind.
2.) an issue with the internal memory that I managed to 'partition around' when I installed MagLDR again.
3.) an issue with ICS/kernel compatibility that was unique to my phones for some odd reason.
Regardless, for the past ten days, the only reason I've had to reboot the phone was due to a dead battery. Thank you everyone who watched this thread and helped me with my issue. I am greatly appreciative of your willingness and patience.
Joey

How do I test for true missed touches?

OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Enable developer options and see the touches
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
May82 said:
OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Try playing some heavy multitouch games. I'm playing Terraria. Requires fine motion. You'll notice anything in that game.
Sent from my Nexus 7 using XDA Premium 4 mobile app

kotivalo said:
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
Click to expand...
Click to collapse
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/

lomonic said:
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/
Click to expand...
Click to collapse
Interesting!

lomonic said:
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
Click to expand...
Click to collapse
Thanks lomonic, an interesting link.
I had the former/original Nexus 7 (until my oldest daughter accidentally dropped it in May), and it had no touchscreen issues, at least nothing as bad compared to my new Nexus 7 (2013 model). Yes, it lagged sometimes, as does also my Nexus 4 (mostly noticeable when you slide down the notification menu or open the open applications list), but it had no similar problems with the precision of the touchscreen of the new Nexus 7.
I just tried to reboot the device and also noticed the touchscreen performing a bit better. Though, the problem came back in no time, and after a couple of minutes using Google Maps was the same mess as before. Twisting/rotating the map with two fingers results to pinching/zooming and the map centers somewhere else you want it to. Also in Chrome zooming and scrolling doesn't work as expected, and selecting text is also problematic. Using the keyboard might get you a sticky backspace, which is somewhat annoying. I can only imagine how it would be to try to play touchscreen intensive games, which demand fast and precise touches.
On my Nexus 4 I've also noticed that Chrome seems to slow the whole device, and for this reason I've also been using Dolphin for a while now (but I've yet not deleted Chrome, I just don't use it). Maybe I should dump the whole app from my phone. Also using Clean Master to clean up the memory from apps/processes helps for a while, but only for a while.
Google (or Asus) could verify if there's a sw patch on the way. I'm not a gamer, I mostly use the tablet for surfing and reading, but also these task are not a pleasure with the touchscreen issue. If this problem still persist after a month or so, I really think about returning the device (I bought it just a week ago).

Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.

May,
I have the exact same issue--but my missed touches are once every 5 minutes--quite annoying when typing an email or typing a password. I haven't unlocked the tablet yet to apply sfhub's fixes--will let you know how it goes.

player911 said:
Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.
Click to expand...
Click to collapse
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
I think the reality is that many are having problems but do not know about it. They may just dismiss it as not being accurate with their own touches. Also for some users, it could likely be their first touch devices and have no prior experiences to compare with. When i've gotten this device, it was working well and all, but it just feels like typing aint that smooth and slowly over time, the problems starts to be more frequent.
There was an incident i had when after a few days of usage, i tried using it with it lying on the bed and it was going crazy - which never happened before. I picked it up (attempt to earth it) and lay it back down again but the results are the same. So i did a reboot with the system on the bed, and all the problems went away. So i'm not sure it has to do with the earthing factor which many are citing.
I think it is a combination of GPU/CPU/memory and touch related event handling factors that causes the problems to occur more frequently after extensive usage. There should be no reason for hardware to perform perfectly after a reboot only to fail over time.
Oh well, only time will tell when these problems would eventually be addressed.

lomonic said:
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
Click to expand...
Click to collapse
I guess you mean the stock android browser. It may not be available as an app but it's still there as a WebView component available to developers. I guess Dolphin and many other 3rd party browsers are based on the WebView component or on the source code of it.
The problem with the so called stock browser and WebView is that is uses some legacy HTML and JS engine that has not been updated since 2010 or so. That is another crappy developer "feature" from Google that for 3rd party developers there's no "web browser" component that is based on some up to date rendering engine like Chrome's.

In the Themes and Apps thread, there is a method to allow you to install the stock Browser on a stock rom without being rooted.
Also using Sfhub ts10 gave me a 90% fix but it would still spaz out occasionally and would miss touches or click weird stuff. ts20 really fixed me up right. I can play games now and type with no errors.
ts10 is a really good fix, but ts20 really hit it home.