Dispositivo: HTC Tytn II Italia
Rom: Originale-25.83.40.02
Radio: Originale-1.65.17.56
Operatore: Wind
unfortunately I do not speak English, translator
I do not know if it's a conscious failure, before the SW is completely open (green screen written 6.1) can be seen below from screen to open something that you see are the notes for registration, telephone letters (C, d, e, f ) and the keyboard and all buttons unresponsive, sometimes does not meet even the power button from standby.
Sometimes having no battery for some time has begun to work well for a few hours. I noticed that when it does not work does not meet even the bootloader (camera-power-reset)
In December I had sent for service and warranty, but having been without a battery I have sent and wrote''no defect''.
The defect exists and is unusable after a while because of all crashes, time to start no problem everything works perfectly.
thanks
-------------------------------------------
Non so se è un difetto consciuto, prima che il SW si apra del tutto (schermo verde scritta 6.1) si vede sotto partire qualcosa che a schermo aperto si vede siano le note di registrazione, telefono con lettere (c,d,e,f) e la tastiera e tutti i tasti non rispondono ai comandi, a volte non risponde nemmeno il tasto di accensione da standby.
A volte tenuto senza batteria per un po di tempo ha ricominciato a funzionare bene per qualche ora. Ho notato che quando non funziona non risponde nemmeno il bootloader (camera-power-reset)
A dicembre lo avevo mandato in assistenza e garanzia ma essendo stato senza batteria me lo hanno rimandato e scritto ''nessun difetto riscontrato''.
Il difetto esiste ed è inutilizzabile perchè dopo un po si blocca del tutto, quando in avvio non presenta problemi tutto funziona perfettamente.
grazie
I added the video file
--------------------
Ho aggiunto il file video
I also have this problem. I have disassembled the phone and used a compressor to clean it. No improvement I also disconnected the qwerty keyboard which made no difference
Now under pressure after data with HSDPA (battery very hot) has begun to work
but I do not know how long continue
garand_it said:
Now under pressure after data with HSDPA (battery very hot) has begun to work
but I do not know how long continue
Click to expand...
Click to collapse
returned the defect
sometimes i can no longer turn on to stantby, reset or take out the battery
Some issues about it.
I'have the same trouble since I instal an Spanish version of WM 6.5. At the beginning works fine, but then, when I told to A. Sync, not do nothing except connect to device, my contacts dessapear from WM contacts, and the camera stop working at some time from that; may be, and I'm guessing, could be the problem when you mix those factors, the foreign language, conecting without sync and having the PC conected to the WEB. Could it be?.
My conf.
This is my conf:
Windows Server 2003 R2.
Active Sync v4.5
My mobile (this program causes errors sometime, it seem that it try to write to the protected memory of W2003, and give WEP problems).
Windows Mobile INT2MIL WM6.5 ROM 0C0A V1.0 23071.
HTC AT&T 8925.
I hope this help to fix errors in the future.
michael_llewellyn said:
I also have this problem. I have disassembled the phone and used a compressor to clean it. No improvement I also disconnected the qwerty keyboard which made no difference
Click to expand...
Click to collapse
anything new? have resolved the defect TyTN2?
garand_it said:
anything new? have resolved the defect TyTN2?
Click to expand...
Click to collapse
I was again playing with the data hsdpa when suddenly has 4 sounds event / error and started to work well.
I decided, HTC has not yet replied (pretty seriously, I think that if I can not buy more HTC) returns as soon as I open the kaiser.
Related
OK well while waiting for someone on here to help me with my activesync problem, ive figured out that the culprit is the kaspersky A/V and firewall. I totally uninstalled them both and activesync worked fine. But i want to use kaspersky so does ne one have true expierence with these products and can tell me how to go bout settin it up before i put a bullet in my pc and pocket pc!
il faut désactiver la sécurité réseaux dans kaspersky. ou une mise à jours vers la version 5.0.391 minimum, elle intègre le patch correctif de compatibilité.
There's a fix on the Kaspersky website:
http://www.kaspersky.com/faq?qid=180455931
i figured out the problems for my bluescreens was Kaspersky too. My friend had the same problem with GDATA Anti-Virus-Kit, which uses the Kaspersky Engine too. Now im using Bitdefender, but i will try the registry fix. Theres no better AV than Kaspersky.
Crazy: I only had bluescreens with my MDA Vario (Wizard). I have an iPAQ hx2110 with WM5 and no problems...
I finally found the cure. someone from kaspersky's lab forum told me to try the newest version os A/v and a beta version of A/H and it worked fine. no more crashes no problems no nothing.....yet. the A/V version is http://www.kaspersky.com/productupdates?chapter=146244099 and the beta version of A/H is http://d5y.kaspersky-labs.com/beta/kah/english/setup.exe, hope this helps ne one with the same peoblems i had[/url]
Hi all,
There are several threads talking of this problem: as soon as you install VoIP on the diamond, the GPS cannot be accessed, whatever the application you use (TomTom, GoogleMap, HTC GPS Tool ...).
It seems that for now, the only way to get back GPS is to hard reset the device.
There must be a way to know what files or settings are overridden by VoIP so as to get them back to the correct version.
If someone has another solution than Hard Reset, please post it here.
For reference, here are the threads dealing with this problem:
http://forum.xda-developers.com/showthread.php?t=396605&page=2
http://forum.xda-developers.com/showthread.php?t=402850&page=2
http://forum.xda-developers.com/showthread.php?t=402712
Thanks
Thank you for sharing this. I'll avoid VOIP for a while...
I use fring and there is no probleme
nickytheshaft said:
I use fring and there is no probleme
Click to expand...
Click to collapse
same here
Hi,
I use fring too and no problem
lmr2003 said:
Hi,
I use fring too and no problem
Click to expand...
Click to collapse
This issue is with the WM implementation of VoIP. I have had that same problem too. I was hoping to use it because it is transparently integrated into the dialer (you can switch GSM and VoIP dialing on the fly). This problem doesn't affect Fring ,Skype or SJphone etc. because they implement VoIP independantly from windows - they use their own signalting stack and probably codec implementation.
I used WM6 VoIP on the cruise and it worked *sort of* ok - echo sometimes, and often pretty bad delay - more than 300ms, even when network conditions would allow for a much better performance.
Still, Anyone out there knows if the WM6.1 VoIP implementation was fixed for the Diamond yet?
What about fring ? is it slow on the diamond ??? is there any problems about delay or else ?
Regards
Tony
tony28 said:
What about fring ? is it slow on the diamond ??? is there any problems about delay or else ?
Regards
Tony
Click to expand...
Click to collapse
I installed and tested it with my 3mbit wireless connection with no problem. The sound was not as clear as if you use GSM, but hey, you can call for free!
Try this link:
http://forum.xda-developers.com/archive/index.php/t-344429.html
I tried to delete the following files:
ipdialplan.xml, dnsapi.dll, voipphonecanvas.dll, rtcdll.dll.
I could not delete the third one. Then after a power cycle, I got back the GPS. This was done on 1.34.
i cannot confirm the gps "lost" problem.
GPS is still working after installation of the VOIP package.
Only the sound level of SIP calls is really low.... (and i am locking for a solution)
xweber said:
i cannot confirm the gps "lost" problem.
GPS is still working after installation of the VOIP package.
Only the sound level of SIP calls is really low.... (and i am locking for a solution)
Click to expand...
Click to collapse
Which VoIP package did you use? You're about the only one for who it does work fully properly. If you could supply us with the ROM you've used, including the Radio ROM, that'd be great
OnePointOh said:
Which VoIP package did you use? You're about the only one for who it does work fully properly. If you could supply us with the ROM you've used, including the Radio ROM, that'd be great
Click to expand...
Click to collapse
i used this package: destr0_VOIP_WM61___SIP_Config_1.1.CAB (http://forum.xda-developers.com/showpost.php?p=2326934&postcount=50)
on one diamond applied step by step (without the cab install) and on a second diamond with the cab install. On both GPS is still functional and running.
ROM and Radio is german stock O2.
the low volume problem: ivestigations shows that the rear speaker (which is on top on the diamond) is used for the output. So this "sounds" like low volume on the internal speaker (since both speakers are close to each other).
xweber said:
i used this package: destr0_VOIP_WM61___SIP_Config_1.1.CAB (http://forum.xda-developers.com/showpost.php?p=2326934&postcount=50)
on one diamond applied step by step (without the cab install) and on a second diamond with the cab install. On both GPS is still functional and running.
ROM and Radio is german stock O2.
the low volume problem: ivestigations shows that the rear speaker (which is on top on the diamond) is used for the output. So this "sounds" like low volume on the internal speaker (since both speakers are close to each other).
Click to expand...
Click to collapse
Thanks!
Weird, that's the one most of us use. It's probably to do with your specific ROM and Radio. I hope one of the dev's who know infinitely more than me on this could shed some light / use this info to make it work for the rest of us
For us, though, the internal speaker is used! This might also have to do with the ROM differinces. Very weird.
Hi,
same here on my 1.37.0 german ROM. But I used jasjaming "VOIP drivers.cab" from http://wmblack.info/addons/enchantments.rar and those can be uninstalled. So installing them, VOIP up and running, just need to tell it in the settings->phone->internet tab to use VOIP (everytime I reinstall the drivers).
But GPS goes dead. If I unstall the drivers via Remove program the VOIP will not connect anymore, but GPS is up and running again.
Did anyone try it with ROM 1.93?
Thanks,
Seven
I use googlemaps and the new Skype for 6.1. Before that I used Fring.
Reporting NO problems here SIR!!!
To solve the problem just rename file /windows/dnsapi.dll to for example dnsapi.dll_bck and make soft reset or turn off and on your device.
There will be created a new file with the same name and you can delete the old renamed one. Then the GPS working properly as well as VoIP. Good luck...
file not created after soft reset
I renamed this file but it isn't created again after a soft reset. On the other and everything seems to work properly (exept SIP for the moment, but it wasn't before I deleted the file!).
Does anybody know how I could re-create it or where I can find it ?
(btw it's a Touch HD)
thanks !
I've got the same problem, renaming let everything working... except voip...
...damn...
SPOOKY
Solution
Bonjour,
Excusez je n'ecrit que le Français je vous met une traduction en anglais en fin de message
------------------
Je tiens a donner une info qui servira c'est certain a beaucoup d'entre nous (3 jours de galères que je vous fais profiter.
Ca concerne la version de VoIP qui plante le GPS, hélas me suis fait avoir et mon HD1 avec Tomtom ne trouvé plus le GPS, voici la solution qui permet de retrouver le GPS sans Hard Reset:
1) désinstaller dans l'ordre les programmes cités:
SipConfigTool puis Voip.cab puis WM6VoIP.CAB puis Total Commander ( je l'ai inclus mais pense pas que ce soit un impératif) faire un soft reset après Voip et WM6Voip, pour les autres laissez les en place.
en parallèle j'avais installé Advanced_Configuration qui nécessite FrameWok3.5 j'ai aussi désinstallé mais avant les manips ci dessus.
Euréka mon Tomtom refonctionne il détecte le GPS a nouveau
Voilà
Pour ceux qui veulent toujours le SIP j'ai remis la bonne version de WM6VoIP, le GPS continu a fonctionner , J'ai maintenant le GPS et le phone SIP qui fonctionnent
JC
Traduction en English:
I want to give information that will for sure has a lot of us (three days of hell that I enjoy doing.
It concerns the version of the GPS VoIP plant, unfortunately got my HD1 and have only found it with Tomtom GPS, here is the solution that finds the GPS without Hard Reset:
1) uninstall the programs in the order listed:
SipConfigTool Voip.cab and then WM6VoIP.CAB then Total Commander (included but I think that that is a must) do a soft reset after WM6Voip Voip and for other leave them in place.
I had installed in parallel which requires Advanced_Configuration FrameWok3.5 I also uninstalled but before the manipulations above.
Eureka operates again it detects my Tomtom GPS again
Here
For those who always want the SIP I gave the correct version of WM6VoIP, the GPS function is continuous, yet again the install complete but I am hopeful.
I have this problem with my htc kaiser:
When the phone is under edge or gprs network and I received (or send) a calling, the phone switch off. (scuse me my english).
If I'm under 3g or Hsdpa I can make and receive calling regulary.
I tryed a lot of radio (1.71-1.70-1.65) and rom (also originaly) but the problem is the same.
Can somebody suggest me a solution?
ITA.
quando ricevo o invio una chiamata telefonica sotto rete gprs o edge il telefono si spenge da solo. Funziona invece regolarmente sotto rete 3g o Hsdpa.
Ho provato tante rom e radio, qualcuno ha da suggerirmi una soluzione?
sounds like a battery problem, try replacing
sounds like a battery problem, try replacing
How does that sound like a battery problem?
It doesn't work on the slower less battery aggressive data, but does work just fine with the power draining 3g..
This sounds like a problem people have had before, something that has been posted a few times.
here are some threads that may help.
http://forum.xda-developers.com/showthread.php?t=366217&highlight=dropping+calls
http://forum.xda-developers.com/showthread.php?t=360490&highlight=dropping+calls
http://forum.xda-developers.com/showthread.php?t=442446&highlight=3g+calls
http://forum.xda-developers.com/showthread.php?t=547710&highlight=3g+calls
same happenin for me.. i just ordered a battery for my phone to replace it.. lets see what will happen next..
mystik_khmer said:
same happenin for me.. i just ordered a battery for my phone to replace it.. lets see what will happen next..
Click to expand...
Click to collapse
me too. I wait the battery than i post the result
meto o same problem i ordered 2800Mah with back door today from 4u-kidi.com
solved with battery replacement I'm too happy
Hi everybody.
Sorry to disturb you but i have a serious problem with my xperia.
I recently tried the new nand version of sp3dev's CM 7 with his new kernel wich solved the problem of wifi suspend ecc...
now, i got back to WM.
I thought i did all right but now i phone is stuck in Gsm mode,
only sometimes it gets to EDGE and never to 3g or HSDPA.
When in GSM i have full coverage, but i can't call nor recieve..
I tried everything:
Task 29
new ROM (Dynamics)
new RADIO (1.17)
Task 29
new ROM again (Energy (just to try..))
but nothing seems to solve..
I tried the sim on another mobile phone, and i can call/recieve.
Thank you for the answers you will give me.
PS. i'm italian and my provider is TIM
hai la 3? Se si anche io sto avendo un sacco di problemi da qualche giorno su una scheda si e sull'altra no
Hem.. i feel a little stupid, but now everything works fine..
I mean, i don't know why, i changed nothing on my phone.
Half an hour after the boot (it still showed Gsm signal)
I recieved a call... and a minute later all the messages that were sent to me during the "blackout".
Now 3g/HSDPA is fully working (i am listening to an album on youtube..)
I really don't know what happend.. maybe flashing the radio helped... but i don't know why it worked just after half an hour.
I feel sorry for occupying space on the forum.
Close or delete
PS. grazie per l'interessamento lemon88. Ero tre, ora sono Tim.. e comunque ora va tutto bene..
Because the problem was solved after half an hour, I think it wasn't a flashing-related problem.
Either there was a problem with your mobile network (even if the signal is strong), or maybe a problem with wm (maybe it's busy searching for media/images on first boot).
Glad your problem was solved, though
Hello all!
I have identified a delay when i receive a phone call, my watch starts vibrating some seconds after (i haven't measured, but 5 to 10 seconds). Sometimes I have even finished the call before the watch starts vibrating... Does anyone of you meet this? How could I solve it?
Thx...
I have the same problem. I would be finished with the call and 10 seconds later my watch alerts me of the call. One time my watch alerts me of the call. I answer the call and the watch kept alerting me for about 30seconds.
Sometimes it happens too but only when watch connects through wifi.
Still the same problem... Only SMS are notified on phone and watch at the same time... I feel pretty alone with this issue
I tried to use the stock faces instead of watchmaker ones, but still the same... Could the problem come from the phone itself? (G S4 mini)
solutions?
francyesco said:
solutions?
Click to expand...
Click to collapse
:crying::crying::crying:
Nooooo! Either I'm the only one meeting this issue, or nobody cares about this delay.......
zarnox said:
:crying::crying::crying:
Nooooo! Either I'm the only one meeting this issue, or nobody cares about this delay.......
Click to expand...
Click to collapse
I'm also having this issue...only calls seems have this bug... I've also disable phone vibration/sounds when watch is connected so sometime as result i will lose the call
Probably you guys are having Touchwizz. I have used the watch with Nexus 6 and OnePlus X; everything works perfectly.
bioan said:
Probably you guys are having Touchwizz. I have used the watch with Nexus 6 and OnePlus X; everything works perfectly.
Click to expand...
Click to collapse
G4 with W100..
I did some tests, but no success up to now:
- With or without Nova launcher
- With or without Wear Mini launcher
- With or without "Ignore alerts and calls when connected to the phone"
I still don't know what could interfere regarding notifications. I will try to clean the watch completely without any app to see if it's better... I'll keep you informed.
No success. Watchmaker premium unistalled, Wear Mini launcher uninstalled, hard reset of the watch, complete new install, still the lag... What I don't understand is that I had no issue 6 month ago when my watch was brand new (and same phone)... Could it be the LG firmware?
zarnox said:
No success. Watchmaker premium unistalled, Wear Mini launcher uninstalled, hard reset of the watch, complete new install, still the lag... What I don't understand is that I had no issue 6 month ago when my watch was brand new (and same phone)... Could it be the LG firmware?
Click to expand...
Click to collapse
Probably the issue come with the latest versions of android wear...
For me the issue was here from the first use .... Just realized later.
CA Y EST!!! J'AI ENFIN TROUVE!!!!!!!
Le problème vient d'Android Wear installé sur le mobile... Les versions 1.3 et 1.4 sont buggées et génère ce décalage de notification.
J'ai installé une ancienne version d'AW (la 1.1) trouvée ici: http://www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-1-1-2113877-android-apk-download/
Depuis cette installation, ma montre notifie les appels dans la seconde qui suit celle du téléphone... Pourvu que ça dure! :fingers-crossed:
J'espère que ça servira à tous ceux qui ont le même problème.
:highfive::highfive::highfive:
zarnox said:
CA Y EST!!! J'AI ENFIN TROUVE!!!!!!!
Le problème vient d'Android Wear installé sur le mobile... Les versions 1.3 et 1.4 sont buggées et génère ce décalage de notification.
J'ai installé une ancienne version d'AW (la 1.1) trouvée ici: http://www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-1-1-2113877-android-apk-download/
Depuis cette installation, ma montre notifie les appels dans la seconde qui suit celle du téléphone... Pourvu que ça dure! :fingers-crossed:
J'espère que ça servira à tous ceux qui ont le même problème.
:highfive::highfive::highfive:
Click to expand...
Click to collapse
Oups I was so happy that I wrote it in French
Here is the translation:
"I found a solution, the issue is linked to Android Wear software installed on the phone. Rev 1.3 and 1.4 are bugged and it brings delay between phone call notification and watch call notification (up to 30 seconds!)
I installed a previous revision of AW found here: http://www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-1-1-2113877-android-apk-download/
Since this installation, my watch notifies calls within one second after the phone one. May it continue like this!!!
zarnox said:
Oups I was so happy that I wrote it in French
Here is the translation:
"I found a solution, the issue is linked to Android Wear software installed on the phone. Rev 1.3 and 1.4 are bugged and it brings delay between phone call notification and watch call notification (up to 30 seconds!)
I installed a previous revision of AW found here: http://www.apkmirror.com/apk/google...roid-wear-1-1-1-2113877-android-apk-download/
Since this installation, my watch notifies calls within one second after the phone one. May it continue like this!!!
Click to expand...
Click to collapse
Its just a workaround with version 1.1 of AW i think we will lose a lot of nice features done later.
Btw thanks for the feedback.
I too get this sometimes. Phone is Sony Xperia Z3 compact running Android 6.0.1.
I had the same issue for months. Then I had to factory reset my phone (Note4). After reinstalling, restoring backup, the watch did resync and the problem was gone..
Same here. Note 3 with android 6.0.1
Seems i've found a "workaround" try to active always on display calls will be show immediately
(Sorry for my bad english)
I got my watch a month ago, and it bothers me a lot that the caller ID takes almost 10 seconds to show the name or phone number. Before I had the Sony SmartWatch 2 and had no problems with this feature. Everything works great, but this is a major flaw. Having display on, doesn't work for me. I hope that we won't have this problem with Google wear 2.
I have it paired with my Huawei p9