yashsingh1/xdaforums huggingface dataset:
[G1 Q&A, Help & Troubleshooting] xtreme_protector:
I installed Destinator 9 (navigation application) from market, but it won't work on the latest Cyanogen firmwares. The error is an unmet dependency in the JNI library implementing most of the Destinator application. The problematic imported function is _aeabi_f2uiz, which I understood is part of the libgcc.

Is there any way to fix this ? Could I just get and install a compatible libgcc.so library ?

Any ideas ?

By the way, it is supposed to work on donut 1.6.

Thanks.
[G1 Q&A, Help & Troubleshooting] xtreme_protector:
thanks a lot man. very useful indeed ;).
[G1 Q&A, Help & Troubleshooting] drpfenderson:
I think it's more that you posted in the wrong forum. Belongs in Apps and Games...since you're not developing anything, only troubleshooting an already-developed app.
[G1 Q&A, Help & Troubleshooting] Z҉A҉L҉G҉O̚̕̚:
-EXACTLY!-
[G1 Q&A, Help & Troubleshooting] nikos_snowman:
thanks
[Windows Mobile Software Development] norcalstoppy:
I'm not sure how it loads, or what the mechanics of it are, but if possible, it would be awesome to just pull up an app to see how my team is doing on real time basis, now that the stat tracker function is free.
[Touch HD Themes and Apps] hsclater:
There are many ROMs which have some apps removed, and people may want to add them back.

Is there an up to date CAB repository anywhere that can be used to download individual CABs by people wanting to add things back into ROMS?

Thanks
[Touch HD Themes and Apps] zamcum:
It's not the official repository, but almost.

Try this
[Touch HD Themes and Apps] hsclater:
That is pretty much perfect, I guess that is Miri's one.

Thanks
[G1 Q&A, Help & Troubleshooting] benzizbit:
I try to update ADP1 to cm-CyanogenMod-4.2.13 (the same issue is with 4.2.12 as well).

The issue is that the market will not download apps (it will try to start but it will not download).

The Google talk will crash on opening, and GTalk service is not running.

Any one has any idea on how to solve this?

Thx for the help
[G1 Q&A, Help & Troubleshooting] robkoehler:
what steps are you taking?
[G1 Q&A, Help & Troubleshooting] benzizbit:
First thx for your reply.

I'm doing the steps in the cm Wiki - from the recovery image

1 Press Alt-W Press home to confirm.

2 Press Alt-A

Pick signed-dream_devphone_userdebug-ota-14721.zip.

3 Press home to confirm and let installation complete.

4 STOP - DO NOT REBOOT YOUR PHONE

5 Once again, press Alt-A (or select "apply any zip from sd").

* Pick update-cm-4.2.x-signed.zip.

6 Press home to confirm and let installation complete

Thx for the help
[Nexus One General] jnougher:
Morning - looks like I am one of the few in the Uk to have got my Nexus - arrived yesterday morning complete with engraving on the back.

As an aside the DHL tracking on the web still shows as only "shipment details received"!

The reason for my post is getting email from my Exchange server - it all works fine with my iPhone and Hero, but when ever I try to connect with the Nexus I keep getting "Setup could not finish - Unable to open connection to the server"

I have tried Touchdown and it is also upable to get the activesync profile from my server! gets a Error 500:

Is there something simple I am missing? I am able to browse the wen and get my gmail on the device but no exchange!

Any help would be great

Thanks

John
[Nexus One General] cottinghamm:
I have been able to use both the Android mail connection & Touchdown to connect to my hosted Exchange server (2007) using SSL, I guess as you have connected from other devices you must know the settings of the server.

Are you connecting via Wifi or 3G ?

Shouldn't make a difference, but which carrier are you on & did you get the 3G correct ?

Can you connect to the server on OWA via the browser ?

Good luck
[Nexus One General] KK43:
Working fine for me, have you tried playing around with the settings? E.g. mine doesn't work unless I've checked the SLL box (but not the accept SLL certificates box), and make sure you precede the username with domain\
[Nexus One General] jnougher:
tried on both 3g and wifi - both no joy

just been looking for roadsync on the market and I don't appear to have any paid apps either...

been using an O2 sim just putting my orange sim to see if it makes a difference but doubt it will as wifi doesn't work...

stumpted!
[Nexus One General] bugsy:
I originally had a problem connecting with the native activesync with a similar error, however touchdown worked fine. I would try touchdown quick config and see if it can figure it out. You also might need to look at the certificate options under touchdown. Forcing that might help.
[Nexus One General] jnougher:
I have tried again with Touchdown - and managed to capture these results from the log:

I have reset my hero and reconnected to my exchange server and it connects fine...

I have called HTC to arrange a hardware replacement but the guy on the phone didn't seem to know what he was doing.

Checking Certificate...

Checking ActiveSync with SSL...

ActiveSync location returned HTTP code 500 : ( The request was rejected by the HTTP filter. Contact the server administrator. )

ActiveSync Version :ActiveSync ERROR :500

Trying activesync protocol 121...

ActiveSync provisioning returns HTTP:400

Error provisioning ActiveSync: Policy status is 0

Trying activesync protocol 2.5...

ActiveSync provisioning returns HTTP:200

ActiveSync provisioning success

The following policies have been requested :

- Allow Simple password

Refreshing AS folders

Error refreshing folders

Socket is not connected:Exception performing request

ActiveSync version check returned negative, but still trying for 12.1

Checking 2007 with SSL...

attr value delimiter missing! (position:START_TAG <HTML dir='null'>@2:11 in java.io.StringReader@447cc910) for operation: Subscribe-> Error renewing a subscription

Socket is not connected for operation: Subscribe-> Error renewing a subscription

Checking 2003 with SSL...

Checking 2003 without SSL...

Socket is not connected:Exception performing request

Would welcome any help from someone wiser than me

Cheers

John
[Nexus One General] mark925:
How did you capture the log from Touchdown?

I'm using Touchdown here as well and have no issues to speak of. From what it looks like it might be something server-side?
[Nexus One General] jnougher:
Quick connect in touchdown captures the log as it tries to connect.

I agree it all points towards a server issue, but what is different between the nexus and the hero? I have reset my hero and reconnected with the standard android active sync connnector and it works fine. I use a neuxs with the exact same settings on either touchdown or the android connector and it fails!

It is driving me mad - I have synced my outlook contacts with my gmail account so I at least have numbers etc. but without email this phone is going to end up on ebay real fast

:confused:

John
[Nexus One General] bugsy:
Not sure, but have you set the simple password in Touchdown? It looks like that is a required policy and if touchdown doesn't report back that it is set you won't be able to configure.
[Nexus One General] jnougher:
because the hero doesn't support the simple pin I got my exchange admin to remove this requirement for me ;)
[Nexus One General] Robster83:
An even bigger thing for me was the lack of Exchange Calendar Sync on the N1. Seems a terrible omission when the Droid/Milestone supports it without trouble.
[HD2 General] kolomnik:
Hi,

One iPhone fan boy suggested to compare my HD2 with his iPhone by simple test as described here:

http://labs.moto.com/diy-touchscreen-analysis/

What I saw on my screen looked less good than Motrola Droid. In some places there is splashes on the line (close to center of the screen).

Do you have straight lines on your HD2 devices ? Please let me know because I think that's explanation of troubles typing with built in keyboard, positioning is quite bad.

Thanks !
[HD2 General] freyberry:
Tried it yesterday and I have straight lines.

Edge performance seems to be not so good on mine, more like the iPhone.
[HD2 General] Marwyn:
No problem here...

I have no problem with this test on my HD2 nice stright lines... anyway i am using fix for touchscreen sensitivity.
[HD2 General] here4info:
mine are nice straight lines as well.. seems like OP has unsteady hands!!
[HD2 General] lorin.bute:
Straight lines here too. I tried that test as soon as i saw it on the web. The HD2 performs well.
[HD2 General] Xeon:
I have exactly the same problem. Not with my first HD2 but the last one ! is it a hardware fault? HTC support is not able to help :(
[HD2 General] eskasi:
That sensitivity (and straight lines) fix v3.3 will solve your problems! I installed it and its straight as an arrow... search the forum for it....
[HD2 General] freyberry:
I've not installed anything...
[HD2 General] Xeon:
I repeat. I did not have any problem with my old HD2 that had the earpiece broken. But I have it with my last HD2. I tested both. Could that be a faulty touch screen!?
[HD2 General] freyberry:
No, certainly not. Maybe they're using touchscreens from different manufacturers.

What exactly is your problem? Cause what you see is in the first post is not a problem, a problem would be it the lines jumped several millimeters, but that's just a slight inaccuracy there (~1mm), nothing to worry about.

Wait for some more answers here, and I hope people will post screenshots, it might turn out that HTC uses two different touch panels.
[HD2 General] Xeon:
My problem is that sometimes the screen is accurate but suddenly it makes weird jitters like this :

http://www.youtube.com/watch?v=t54m1dSLnV8&feature=related

and specially this !

http://www.youtube.com/watch?v=N8MmIErLhag&feature=player_embedded
[HD2 General] freyberry:
Ah OK, I see. That's something different, not the normal inaccuracy that the OP was talking about. In this case, yes, looks like a faulty device.

Have you tried if it goes away when you apply the tweaks here: http://xdaforums.com/showthread.php?t=604831&highlight=touchscreen
[HD2 General] kolomnik:
I haven't tried sensitivity fix myself, but I noticed that by default my device can't handle slow motion of finger. It starts jumping around as it was presented on you tube video as well.
[HD2 General] brandi:
i do have really straight and continous lines here too
[HD2 General] DuoM:
Yes, I saw that and the first thing I thought of was the fact that I've yet to try an HD2 with a usable keyboard.

It would be nice if people could try this test without the sensitivity tweaks and see what kind of lines they get and also let us know if their keyboard is okay or not.

It would also bee good to know if the sensitivity tweaks affect the outcome of this test.
[HD2 General] freyberry:
Look at my screenshot in the second post. I've not done any sensitivity tweaks.

And my keyboard is perfectly fine.

Actually, th screenshot in the first post doesn't look bad either. Definitely not as bad as the Moto Droid, more like the HTC Droid Eris, and that's fine.

The only thing that's not fine is what you see in that youtube video. But that's another story, there's definitely something wrong with the device you see there.

Here's my screenshot again. As you can see, perfectly straight lines without any tweaks.
[HD2 General] bronx:
mine seems to be quite good, but I've done other experiment. breathe on the glass in Your window and draw same pattern. do it slowly... wth?? I have a faulty doubleglazed window... :D imho this test is not that relevant, as sometimes when sliding finger slowly it shakes slightly... or maybe it's just me?? :P
[HD2 General] freyberry:
Here are two more. Looks perfectly fine, IMO.
[HD2 General] DuoM:
Thanks. This is the kind of information I was hoping for.

I'm really just wondering if people with poor line results are those with unusable keyboards. I remember there have been a few threads here about the keyboard and some people have no issue at all while others find their keyboards unusable.
[HD2 General] Karlos G:
What program are you using to draw the lines fella's?
[HD2 General] freyberry:
Notes......
[HD2 General] RussKingUK:
Fault or Feature?

My first htc HD2 purchased in December was perfect and didn't exhibit this problem at all. I have now received another one and now I understand what everybody is talking about. The screen on this one is crazy! I can't type a message without making loads of mistakes (somehow hitting keys the other side of the screen to the one I want which is quite an achievment on a screen this size!) and also scrolling is somewhat unpredictable and "jittery".

The issue is mostly resolved by appling the sensitivity fixes found on this forum but the question is, on a unit that is only a few days old, should I be doing this or should it go back as faulty? Even with the fix applied, I would say that the sensitivity of the screen is still noticably better on my older unit without any fixes applied. That unit is a real pleasure to use with the newer one just being acceptable.

The ROM versions on both units are exactly the same so this would seem to be a change in the scren hardware itself. Maybe it's a different screen or a bad batch? Who knows? What would you do?
[HD2 General] Archer:
I'd send it back straight away mate. I wouldn't even stop to mention it on here I'd be that eager to get it sent off!
[HD2 General] eDaniel:
Best and worst from 10 tries - see the attachments.
[HD2 General] ewok666:
How fast were you moving you finger? If you move it fast enough the lines will always be straight.
[HD2 General] Tanmay®:
Yes! The real test is to move the finger slowly, and even after that you get a straight line then it is indeed accurate.

On my HD2 half of the lines are slightly uneven, on my iPod Touch, every single line seems straight!
[HD2 General] eDaniel:
Is this slow enough? I moved my finger as slow as I can.

Edit: I don't have any tweaks/hacks/mods, etc. The only thing that is tweaked is the taskbar.
[HD2 General] DuoM:
Send it back and hope for the best. I've been trying HD2's for over two months and I've yet to find one with a usable screen.

I was hoping that HTC would have fixed this problem by now since it seems to be either a hardware fault or a calibration issue but no joy yet.

Perhaps when they release their WM 6.5.3 ROM they will have switched to using native WM support for capacitive screens and multitouch and the screen related issues will disappear.
[HD2 General] freyberry:
There is no difference in WM6.5.3 concerning capacitive screens. I think by "native support", they mean that everything is more finger friendly.

But look at my screenshots. I drew the lines VERY slowly, and as you can see, they're really good. There's nothing wrong with my screen.
[HD2 General] eDaniel:
I'm absolutely satisfied with my HD2. What do you think of my video?
[HD2 General] freyberry:
Looks quite good, IMO.
[HD2 General] DuoM:
I'm not talking about leaked ROMS I'm talking about the final ROMS and from the information that came out yesterday it seems that WM 6.5.3 supports capacitive screens and multitouch i.e. there will be no need for HTC to implement this themselves in future versions.

Back in Aug/Sept last year I heard that MS would release WM 6.5 in October followed up by another release in February 2010. At the time the information was that the February release would finally make the whole OS finger friendly but if that was the only change I couldn't see why they needed four months to implement it especially since many of the changes were seen to have been implemented in newer ROMS before 6.5 was officially available. However at the same time there was additional information around about MS adding support for capacitive screens to WM 6.x but it wasn't tied to a specific release date.

The information on capacitive screen and multitouch support was first posted by theunwired.net after they received the information from Microsoft via email. This has since been confirmed by ZDNet who requested a feature list from MS.

http://www.theunwired.net/?item=rel...-mobile-6-5-3-professional-for-windows-phones

http://blogs.zdnet.com/microsoft/?p=5111

"I asked Microsoft for a feature list for 6.5.3 and was provided with the following:

Ease of Use features

* Capacitive touchscreen support

* Platform to enable multitouch

* Touch controls throughout system (no need for stylus)

* Consistent Navigation

* Horizontal scroll bar replaces tabs (think settings>system>about screen)

* Magnifier brings touch support to legacy applications

* Simplified out-of-box experience with fewer steps

* Drag and drop icons on Start Screen

IE Browser Performance

* Page load time decreased

* Memory management improved

* Pan & flick gestures smoothed

* Zoom & rotation speed increased

Quality and Customer Satisfaction features

* Updated runtime tools (.NET CF 3.5, SQL CE 3.1)

* Arabic read/write document support

* Watson (error reporting) improvements and bug fixes"

There may be nothing wrong with your screen but it seems that there is something wrong with more than 50% of the screens out there (polls, information from vendors, etc). This is incredibly high and the screens seems to have a number of different faults some of which may or may not be present 100% of the time. Some only manifest periodically. As I said above I think that it could be a hardware fault or a calibration issue (something that is done in the factory before shipping). I'm obviously hoping for the latter.
[HD2 General] freyberry:
No, that's just wrong. There's really no difference. They're just talking about finger friendlyness.

"Platform to enable multitouch" tells you that it's still the OEMs who have to enable it, there's no native support for multitouch, as well as there's no difference in how it handles touch input.

The screens probably come from different manufacturers. I just wanted to point out that it's not true to say that they're all faulty. Only some are (definitely not more than 50%, that's nonsense).
[HD2 General] DuoM:
Erm, well you'd better take that up with Microsoft who have been saying there is via their Press Office. Both theunwired.net and ZDNet site MS as the direct source.

It's possible that the screens come from different manufacturers but considering the relatively low volume that this product has compared to other HTC products e.g. HTC Hero and Magic I would be surprised if they needed multiple manufacturers for it.

HTC is no stranger to capacitive screens, why is this device the one with all the problems? My other thought about calibration comes from seeing attenuation problems with other electronics where the calibration is actually done manually.

As for more that 50%, yes, that's what I'm seeing and what I'm being told by vendors. It may or may not be correct but unless you have something to dispute that with then you really have nothing but a feeling.

Let me also add that if you had to install the sensitivity reduction cab to get a usable screen then the device IS faulty. A user generated patch does not mean that the device isn't faulty. Now considering all those who have had need of the patch (or who have finally had a usable screen after installing a screen protector), I think that the over 50% number is correct.

Anyway lets see what happens when HTC release the WM 6.5.3 version of the ROM.
[HD2 General] freyberry:
There's no difference at all in how it handles touchscreens. Unless, of course, OEMs implement their own drivers, like HTC has done on the HD2.

What does that mean? It simply means that if you have a faulty screen, WM6.5.3 won't change anything.

Your assumption that the WM version is in any way linked with the touchscren problems is... well... nonsense, sorry ;)

And the screens coming from different manufacturers actually makes a lot of sense. It explains the huge differences (you either have a screen that behaves totally weird or you have one that works perfectly) and it would explain the 50% of faulty screens, if your claim was indeed true.

Anyway, I don't really care, as mine works perfectly. But of course, such a high number of faulty touchscreens shouldn't happen, HTC really screwed up there (especially since they could have come up with a fix like the one posted here of the forum months ago).
[HD2 General] DuoM:
As I understand things WM 6.5 doesn't support capacitive screens or multitouch and this was added to the HD2 specifically by HTC but according to Microsoft WM 6.5.3 supports both those things.

When Microsoft are saying that they have now added support in 6.5.3, why do you keep saying that they haven't?

Now if there is native support by the OS for capacitive screens and multitouch, while a driver will be needed it may be possible to allow the OS to deal with the location calculations based on charge and with determining how many fingers are on the screen, etc - all the additional stuff that HTC had to do themselves. This may reduce the number of factors in the equation if the problem is calibration meaning that screen related issues could disappear for all new units.

You may have noticed that I also said that the hardware could be faulty.

However going back to WM 6.5.3 the question is what exactly does it add in relation to capacitive screens and multitouch. Depending on what it adds it could make the difference especially if the work HTC has done isn't as robust as the work the work that MS has done. If the support that MS has added to 6.5.3 requires new drivers and allows HTC to bypass their capacitive and multitouch work then that is a good thing. I'm sorry to say that where the software is concerned HTC's work on the HD2 has been less than stellar.

Of course HTC may choose not to make any changes to their software regarding the new touchscreen support until WM 7.

Considering the number of faults and the ongoing nature of the faults, screens coming from different manufacturers certainly make a lot of sense but then again the possibility of manual calibration being the culprit is also equally likely in this scenario.

Both should be solvable by HTC but I'm sorry to say that things like the sensitivity tweak actually reduce the chance of that happening (while making many devices usable) because fewer units get sent back as faulty.
[HD2 General] freyberry:
WM6.5.0 DOES support capacitive screens. There's no difference in whether the screen is resistive or capacitive, it just sends the info about where it's touched to the OS and that's it, no matter whether it's capacitive or resistive.

By "support for capacitive screens" Microsoft just mean that it's finger friendly, that's all.

Multitouch is a different thing. There is no native support for multitouch in WM6.5.0 and, as I said, there is also no native support for it in WM6.5.3.

HTC had to implement this themselves in WM6.5.0 and they will have to do it the same way in WM6.5.3.

Or it could just be different and behave weird because HTC uses the same drivers/settings for two different types of hardware.

It adds nothing that would be relevant to this topic, that was my point. It changes nothing about the fact that it's HTC's screens or drivers/software that are faulty and thus won't fix the issue, unless HTC decides to deliver new drivers/software along with a potential WM6.5.3 update (that may never happen).

I don't think that the majority of HD2 users is on this forum and knows about the fix.

That's true, unfortunately. To say it directly: They screwed it up. Very sad, because all the problems ought not have happened (they shouldn't have replaced the SMS app in the first place, and adjusting the camera and touchscren software would have been easy, actually).
[HD2 General] DuoM:
Ah, okay. I understand your point now. Sorry, I know that you said some of this before.

Now this is something that I never considered.

Yes, this was what I was hoping would happen, a rewrite for 6.5.3 - then I started wondering if they would actually do anything anyway until a rewrite was forced by 7 (this was, of course, based on my previous belief that new API level functionality for screens had been added by MS).

I'd hope they do - I see it being suggested to people on other sites so I would hope that the "natives" here are aware of it.