Hi,
This thread is not meant as an exhaustive research, rather it should serve as a place for people to share the behavior of their device, and other can get an idea what expect.
I'll go first - my device restarts roughly once a day, mostly while using the radio - either trying to make a call, or during a call.
Lately it also crashed when connecting to a Wireless 802.11b network.
Usually when it crashes, the screen 'fades' into blackness (with strange horizontal stripes) then it restarts itself a few times until it stays off. I then restart it and it works just fine.
Device details:
Dopod 818pro
ROM Prophet Shadow Vista "My Edition" by varanusvincent
OS 5.2.2021 (Build 19521.1.1.0)
IPL 1.00
SPL 2.G3.4PDA
GSM 02.69.21
Programs:
Spb Mobile Shell, Spb Phone Suit, Spb Backup, Spb Diary, Spb Araball II, S2U2, WkTASK, Resco Explorer, QuickMenu
Please include your device details in your post (especially if your device rarely crashes )
my dvice slows dwn when using wireless too...seldom crash...
but it rarely crashes during call/sms or normal time...
I can't remember the last time it chrashed. It is pretty stable.
my device display often whited out..then,poofed...the device resetted and stuck on the OS bootscreen..
oh...the batteries run out of power
I think the crash problem is because of 3rd party software that you installed.
Last time as I use Vista Edition and using wifi with it. I have no problem at all.
It works perfect on me.
And its stable. My Device is G4.
my device also runs very stable. it crashed once a month i guess.. only if i use to much progs at time.
varanusvincent said:
I think the crash problem is because of 3rd party software that you installed.
Last time as I use Vista Edition and using wifi with it. I have no problem at all.
It works perfect on me.
And its stable. My Device is G4.
Click to expand...
Click to collapse
Interesting , mine is G3.
dwizard said:
Usually when it crashes, the screen 'fades' into blackness (with strange horizontal stripes) then it restarts itself a few times until it stays off. I then restart it and it works just fine.
Click to expand...
Click to collapse
Funny, when my Prophet crashed it would always do so in exactly the same way. The difference was that after it crashed the first time, it would restart and work fine. (For a while, anyway.) I noticed this happened a lot when I was trying to download larger files (say, over 1 meg) while connected using GPRS. The same would happen when using Google Maps; I deliberately panned around so that it would load more and more terrain, until it had buffered around 2 megs, at which point it crashed again. I'm tempted to think that the crashes have something to do with how internet files are being cached, although I'm not very technical and wouldn't know how to start testing this idea. It might be also that the Prophet simply ran out of RAM altogether.
All of this happened a lot (a lot a lot a lot) when I was using Transformer 1.1. When I switched to Korand 3.1 it got better, but it would still happen from time to time. Now I'm using Merged Reversal. I don't think the new ROM makes much difference, but not using HTC Home made a HUGE difference. Even when using rlToday+Ultimate Launch+BatteryStatus+PhoneAlarm+PocketWeather, my system is still much faster than when I was using the Home plugin.
I've hard-reset my device, will run it clean with no 3rd party apps (other than those pre-installed on the ROM), and see if it still crashes (and how often ).
Related
I'm thinking of upgrading from XDA I to II, has anybody else who has upgraded come across anythings that was worse on the XDA II than on the XDA I, for example battery life and using the screen outdoors? Also I find PocketPC 2002 very buggy and the phone is unreliable - have these issues been resolved in XDA II/PocketPC 2003?
some people have this issue
http://forum.xda-developers.com/viewtopic.php?t=10088
some people feel that the screen dont like like it's 65k colouer screen
http://forum.xda-developers.com/vie...postorder=asc&highlight=color+colour&start=50
some people dont like the bluetooth stack from ms which xda2 use
which are a bit limited in just about every way you can think of
http://forum.xda-developers.com/viewtopic.php?t=9618&highlight=bluetooth
Wow, wasn't aware of so many potential problems on the XDA 2... I didn't notice any problems with the color while playing with a demo unit. Next time I do get my hands on one I'll scan it more carefully.
I too am using a XDA I, but I do not plan on pouncing on the XDA 2 because there are a few new units on the horizon.. most notably the HP 6300 and MDA III.
well it's not like the colour is worse then xda1 just that some people dont think it's true 16bit colour
Everything is fine with my unit; I just don't like the MS Bluetooth Stack, doesn't let you listen to music through your Bluetooth Headset
WeatherB said:
Everything is fine with my unit; I just don't like the MS Bluetooth Stack, doesn't let you listen to music through your Bluetooth Headset
Click to expand...
Click to collapse
Will the MDA3 have this fixed?
i think when no other info is given about bluetooth stacks
then they are using the free and not all that great ms stack
Rudegar said:
i think when no other info is given about bluetooth stacks
then they are using the free and not all that great ms stack
Click to expand...
Click to collapse
Thats too bad... I may actually consider the HP63xx if this turns out to be the case...
markh said:
I'm thinking of upgrading from XDA I to II, has anybody else who has upgraded come across anythings that was worse on the XDA II than on the XDA I, for example battery life and using the screen outdoors? Also I find PocketPC 2002 very buggy and the phone is unreliable - have these issues been resolved in XDA II/PocketPC 2003?
Click to expand...
Click to collapse
I use XDA1 with WM2003 with no problems. I never use the 2002. What problems are present?
- If you lose reception it will sometimes not automatically reconnect to the network
- If you lose a GPRS connection you have to do a soft-reset to connect again
- Sometimes it won't do a GPRS connection - again a soft reset. Sometimes when it does connect can't download any information
- SPB Full Screen Keyboard sometimes doesn't work because of some fault in the OS. One has to take out the SD card and do a soft reset but when you do that you can't access the SD card
- When you put in a new SD card it won't recognise it - one has to do a soft reset.
- Sometimes the device will do a soft reset on its own, though I think that is down to a lose SIM card.
- If you have the SMS client open while in standby mode you won't get any audio alerts for incoming SMSs
- On some days I get double alarms on one alaram
- One seems to have to do a soft reset before uninstalling programs, if you don't, it tries to uninstall it but you get a busy icon forever
Some of the above are probably hardware problems though some are OS bugs. I wish the device would be a bit more reliable
do you have an xda2 ?
because your profile says xda1 ?
I use my Wallaby about 5-6 moths. (Yes I have an XDA1)
- If you lose reception it will sometimes not automatically reconnect to the network
This happends for me once. But I think the whole OS freeze, maybe from other problem, or program. I lose the network twice a day, because I travel with underground. But no problem to loging on.
- If you lose a GPRS connection you have to do a soft-reset to connect again
Oh yes, this is a roblem. I try GPRS when I bought my device, use internet for one month, and yes, it happends often for me too.
- Sometimes it won't do a GPRS connection - again a soft reset. Sometimes when it does connect can't download any information
Yes, yes. Now, I remember that problem.
- SPB Full Screen Keyboard sometimes doesn't work because of some fault in the OS. One has to take out the SD card and do a soft reset but when you do that you can't access the SD card
I don't use this program
- When you put in a new SD card it won't recognise it - one has to do a soft reset.
I used SD card rarely. Only 5-6 times, when I borrowing one from my friend. But I had no errors like this.
- Sometimes the device will do a soft reset on its own, though I think that is down to a lose SIM card.
Never happend to me
- If you have the SMS client open while in standby mode you won't get any audio alerts for incoming SMSs
Hmm. It mean, when inbox was open? I never tested it.
On some days I get double alarms on one alaram
Only happend for me, when load back a backup, and there was double everithing (contats, appointments....) when I synced with outlook. I think I make something wrong.
- One seems to have to do a soft reset before uninstalling programs, if you don't, it tries to uninstall it but you get a busy icon forever
It is a software failure I think. maybe for the wrong programmed softwares, and the OS.
I hate one thing with this MS phone:
I use startup password. When I receive a call, I can pick up the phone, without enter the password, but can't change the volume. :evil: I hate this bug well.
I think the XDA 1 is the best value phone/pda on the market today and the xda developers have made it even better value with their flashing software and bespoke roms. I use one as a phone, navigation system, book reader, mp3 player, internet explorer, pop3 email downloader, games, and much more, there is nothing that comes near to the functionality for the price. I have bought several used 64meg devices for friends and they are all amazed at the value for money, when coupled with gps and tomtom its still cheap but packed with features and options.
I have an XDA1 my only 2 problems are that it does not have a SDIO socket & Bluetooth, and as Cruisin thru said the developers here enhanced the device to be the best working PDA PHONE in the market they could just do that to the Himalaya's as well since it has all the missing features in the Wallaby but it need a lot of hard work.
Hi,
Running w2k3se 2.06 wwe for a day now. Looks quite stable. As this is intrim build (in between dcs and CHS version) there are bound to be bugs.
Most have noted camera failing the landscape. I think it would be better if we can list the bugs so that we can try to solve them.
I found many of the bugs cropped if we used older external rom files with w2kse .
Good that many of us are coming out with home cooked extended rom files. The big problem is to find which of these files are better and which are not.
Let me give you example MIDI56.sa.CAB give a better performance than MIDI561.sa.CAB. And rember the cleartype of 1.60 to 1.72 and so on.
The other problem with cooked extrom is that 70-80% file are same in many of them with very few new files. I am on dialup and it takes quite a bit of time to down load 6MB file just to get a customised cab. Also the server will have that much of load.
So my sugestion is we need a repository of file which are included in extrom. Why not seperate the cab files and just publish their customised config.txt in the post.
I think we need to create a thread of only those files. Suggestion are welcome.
RE
OK! Lets starrt the ball rolling.
Noted the followings for v2.06 ROM posted by mystery man:-
1) Sometimes the bluetooth icon on the Today screen would mysteriously disappear. Worst case is when the Today Settings don't even have the Bluetooth Profile although the blue light is blinking.
2) The camera menu got stuck in landscape mode after repeated switching from portrait-to-landscape and vice versa. Soft reset could not resolve the problem. However, after some time of use the problem automatically resolves itself.
:roll:
"The phone is not ready. Wait 15 seconds then try again"
This is when accessing the phone icon in the settings menu, or when trying to send an sms message.
Jez.
Re: RE
FOSA said:
OK! Lets starrt the ball rolling.
Noted the followings for v2.06 ROM posted by mystery man:-
1) Sometimes the bluetooth icon on the Today screen would mysteriously disappear. Worst case is when the Today Settings don't even have the Bluetooth Profile although the blue light is blinking.
2) The camera menu got stuck in landscape mode after repeated switching from portrait-to-landscape and vice versa. Soft reset could not resolve the problem. However, after some time of use the problem automatically resolves itself.
:roll:
Click to expand...
Click to collapse
same here the Today Screen BT will play games with em :twisted:
hi,
few more bugs on 2.06
1. After playing around with landscpae and portrait several times, phone would loose last two rows of buttons both in landscape as well as potrait mode. Soft reset corrected it.
2. MMS composer is not started if you choose from programs, but this can be bypassed by going to the outlook and start coposing.
If you notice startup folder of w2k3se several of the w2k3 startup programs are missing. Is that why SE is faster and I noticed my battery now lasts longer than W2K3 ;-)
Jez said:
"The phone is not ready. Wait 15 seconds then try again"
This is when accessing the phone icon in the settings menu, or when trying to send an sms message.
Jez.
Click to expand...
Click to collapse
This is something I've always seen if trying to access any of the phone's advanced functionality right after a reset, even with my old XDA.
This is akin to trying to access phone numbers on ye olde ubiquious nokia phone SIM card right after turning on.
I've been trying various versions of dcd's mods hoping to remedy a problem with my mogul. It seems that my unit locks-up/freezes when all of the following are true:
1. Bluetooth is on
2. Phone is locked
3. Goes into sleep mode
When i try to awake phone; none of the buttons work; simply black screen and needs a soft reset. This does not happen all the time, just enough to be annoying.
Any thoughts? Is this a radio 1.47 problem??
Thanks guys.
bump. i have the same problem with DCD 1.6.8 Rom. i thought it was codyppc battery/performance hack so I uninstalled that(still happened), then i thought it was s2u2 so i uninstalled that( still happened today).... so any ideas?
can we verify whether this happens on dcd_titan_1.6.10 rom with NO software, tweaks, etc etc installed? it does not happen for me (i have been using BT lately) but that doesnt mean it wont happen for you guys.
Are you by anychance using S2U2 with the Power Off setting?
I was having this problem, and since I've set S2U2 not to Power off the phone, I have not had this problem. Being going well over 24 hours now.
Mine also freezes/locks up from time to time. I'll make the changes in S2U and see what happens.
Sorry for the newb question, but what is S2U?
got it; slide to unlock.
Is this app worthwhile?
I'm running 2.17 ROM and I get this error, although I'm NOT running S2U2
I have got the same problem. I just flashed to custel 1.1 6mb pagepool (awesome rom for alltel users) had no time to install anything extra paired bt locked phone about 10 mins later tried to make call and it was froze. i did however find out if you constantly use the bt it dont freeze (I finaylly installed ms voice command and if i constantly ask for date or time it stays unfroze.).
edit: I just upgraded to radio v2.13 ( ftp://xda:[email protected]/Titan/Radio_Roms/titan_2.13_CDMA.rar ) totally cured bt reception problem on both ends but once again same problem phone freezes. helppppp!!!!!!
I just thought that amidst all the abusing by various people, and asking and begging etc, the people who actually have the rom should post their findings on it so far. Maybe say what os u used to flash, and then any problems you have had with it.
I used XP SP2 32 bit, and these are the bugs ive found:
1)I have this weird thing with the battery where even after being on 80% at night, then charging overnight, both pocketplus4 and resco today say its on 95%. The light is also green before i pull the charger out.
2)I had a problem with wisbar not showing the full start menu, in that some parts only had icons and no text, but a reinstall fixed this.
3)Opera also doesnt load my homepage properly. I have set it to the athena mobile 6 forum, and whenever i load it, it goes to www.htc.com. But when i click settings, it userdefined is selected and its the right URL.
4)Theres no top line on the tabs at the bottom in settings just the lines between "personal" "system" and "connections", ill post a screen shot if needed...
5)finally, audio sometimes doesnt resume when i pause a video and resume it.. but the video does..
Im not trying to complain here, just thought it would be good for the team to ahve somewhere to look to see the bugs people have, and maybe you can try and iron them out for the full release. that is why there was a prerelease after all.
Fianlly, please REFRAIN FROM POSTING unless you have the rom.
If your device has been "bricked" by the prerelease spl, please post in this thread : http://forum.xda-developers.com/showthread.php?t=385148 not here.
Solutions to bugs:
The battery bug: no soultion yet
Opera Homepage bug: instead of going to a page, then settings and clicking use current page, copy the url, and click user defined and paste the link there
The settings tabs graphic problem: Solved by a hard reset. a hard reset may also solve all graphics problems
The audio not resuming problem: disable wow hd [ people said this, i tried it, didnt work for me]
Thanks to the team for all their hard work!
Rory
3) Opera homepage was wierd for me in not working initially when I set it but ok now.
Think what I did different was to set it in "User Defined"
Its not obvious but you can finger scroll the opera settings pages down to show more options
4) Line is ok for me, running RealVGA 96dpi
5) try turning off WOW HD Settings
AP4 works great for me. Other than a few missing icons I have zero problems. The battery (new) shows 100% when fully charged.
Agile Messenger
http://www.agilemobile.com/
is an example of several applications that appear to install fine, but when you try and run them, don't start. Maybe a WM6.1 problem rather than AP4.0 ?
I REALLY do not like Agile anymore. First, they charge. Second they send your password as plaintext! How stupid is that???
And yes I do have the 95-96% battery bug.
Flashed using XPSP2 - followed the PDF exactly by updating radio to 1.57 first and then installing enableRAPI.cab before starting the update process. Have flashed before so did not need to install the drivers from boot loader mode, they were already there.
1: Task Manager icon missing at 96dpi
2: logmein seems to be an issue with WM6.1
3: camera album hangs when opening a video, needing a soft reset
4: WMP will not open in Portrait orientation in 96dpi.
5: The comm manager is still only filling a quarter of the screen in 96dpi mode.
6: Device hangs when trying to open BT SAP settings in 96dpi.
I know some people have mentioned issues with the USB to PC storage mode, but i have not tried this yet, but will report back when i do.
gonna keep testing to see what i can find and update this as i find them.
EDIT:
Fixed no. 4. - Whenever i tried to open WMP in 96dpi portrait it simply crashed and closed again. fixed in the following steps.
set real VGA back to 192 and reboot device
open WMP in portrait.
Got to menu/options and select the skins tab.
Wait for the skin to appear (this will take several seconds)
Once it has appeared on the screen, tap OK and then close WMP.
reset VGA to 96dpi and you're good to go.
This was exactly the same way i used on the WMP bug in AP2/3.
USB to PC storage actually worked VERY well for me Saved me from having to download WM5torage.
I haven't had any of thoose problems. I flashed it via xp and just clicked on the athena wrapper. my thoughts so far is that its a nice rom some annoying problems I had were the screen oriention changing when ever I soft reset. soultion was to copy the toggle to windows\startup and reset and it won't change by itself. as for opera I hated the 9.5 so I uninstalled and installed 8.65 I cant get tomtom to install on this rom. but was able to run route 66. had problems with palringo(im client) and it upgrades itself. I installed schaps configurator and maxed at all the settings. runs super fast now! questions I have for the team is why do they recommend upgrading to 1.57 radio? im using 1.38 with out any problems. another is does the new home screen require net frame 3.0 to run? or why include it in the rom. if im wrong correct me but isn't it a beta?
overall good jobs guys
tomtom 6.03 installed and running fine for me.
Only odd thing is that as you drive screen keeps swapping between landscape and portrait, so just used the icon to disable auto rotate.
What about a option for no bugs?
another thing i just noticed is that the device runs much qiucker using the netcf 2 rather than the 3 thats installed on it. another thing i noticed is that if your sending a message using the attached keyboard when your typing the sender it wont pre guess it. but if i use the sip it works fine
still existing the problem with the watch, as for AP 3. The phone each time you reset moves the zone to GMT +2
I don't understand the brick advice. It is a regular update of rom.
There too much programs no needed, still waiting for a vainilla version.
Now i see what you mean by the battery bug. I had not noticed it previously.
If i charge the device to 100%, showing in the settings menu, DCI battery bar, and also green light, as soon as i unplug the device, it drops to 96% almost immediately. I can actually watch the battery bar clicking down each percent over around 15 seconds!!
Windows media player not opening in portrait at 96dpi has been solved, simply go back to 192 and open WMP in portrait. Got to menu/options and select the skins tab.
Wait for the skin to appear (this will take several seconds)
Once it has appeared on the screen, tap ok and then close WMP.
reset VGA to 96dpi and you're good to go.
beginner said:
I don't understand the brick advice. It is a regular update of rom.
Click to expand...
Click to collapse
Have you read nothing on AP4.0? It certainly ISN'T a regular update of ROM!
marka2k said:
What about a option for no bugs?
Click to expand...
Click to collapse
i mispellt opera in the poll too, and want to change it, but cant, i put it up with the view that i could add more options if people had other bugs, but i cant. sorry
Confucious said:
Have you read nothing on AP4.0? It certainly ISN'T a regular update of ROM!
Click to expand...
Click to collapse
Exactly mate.
Btw, I was on modaco yesterday and saw youve got like 5k posts, 5th biggest poster there.. not bad mate not bad at all... must be on here or there pretty much all day lol
Rory
fixed the poll
cheers midget
Several bugs
I have installed AP4 according to the manual and it went like clockwork.
After four days of havy use I have noticed some problems:
1. On sunday and monday I had several problems with the microdrive. Several times the drive vanished in Resco Explorer or there were strange files, or complete directories were read only. Everytime a softreset solved it. I decided to flash my device again and now everything works fine.
2. I use TomTom very often. Installing works fine but with the latest versions 6.032 build 8351 and build 8355 I have problems. It happens very often when I am navigating and I change te route, that when TomTom is recalculating, the program gives a error saying that because of an error it can not calculate the route. Only a softreset solves the problem. Tomorrow I will test the wm2003 version 6.03 on AP4 to find out if WM6.1 is the problem.
3. Today I had several problems with the radio version 1.57. It was already installed when I used AP3. After entering my pin the device connected to the intenet but there was no trafic possible. A softreset solved it. But this happened several times today while driving on the road. I also noticed a problem I had in the past with my universal. While I had te problem I disabled the phone, but the connection stayed. There was also trafic. Very strange.
4. Another thing that bothers me is TouchFlo itself. Sometimes it makes it impossible to select text. Within TomTom the screen does not respond as it did in AP3. You have to press hard and for a longer time before TomTom noticed that you pushed the screen. The same TomTom has no problem on my HTC Touch Cruise (Polaris).
5. I used F-Secure for months now but now it will not install. I had to install compact framework 2 first.
6. I noticed another thing this aftenoon. When I was in TomTom te diable call button will minimize TomTom and you cannot see it anymore with WkTASK. First I thought it hd crashed but after starting it again I noticed that the program was running in the background.
7. This evening I was browsing with RSS hub and Opera. I was hitting a link and on te page was a flashvideo. After Opera had started the page was loaded but just before it was finished Opera shutdown completely.
8. I want to end this review with saying that I also have the probem with the battery indicator not showing the 100% energie level, the htc album freezing my device, iGO8 not wanting to start, Opera not wanting to start mediaplayer after hitting an mms link. Internet Explorer does, and several websites use a specific fonts which result in a webpage with very large text. E.g. http://mobiel.nu.nl/pda which normaly shows small fonts. I have no probem with it on AP3.
Beside all these problems I like the rom. Route66 workeds perfectly on AP4 so I can live with the TomTom problem. A few weeks ago my plus account ended and I did not renew it yet.
QAN
OK, battery bug seems to be getting worse, charges fully and light goes green, all battery meters read 93%, even when still plugged in!
I am also experiencing problems with the internet as detailed by Qan. It works fine for a while and then it stops and i have to soft reset. Am going to flash back to 1.50 radio as i never had a problem with that - although i am a bit worried about flashing a radio on the pre-release as it does not have the locked SPL that would be in the final release, but i suppose if i use an updater that only contains the radio, it shouldn't be a problem (famous last words!!).
I have noticed that my touch screen seems to be much less sensitive. This I am guessing is down to touchflo waiting to see if you are going to scroll and therefore it is not picking up the quick taps. Annoying, and possibly the one thing that will send me back to AP3 dual. The touch itself bugged the hell out of me for being so unresponsive on the touch screen, but the touch dual was much better. This seems to be at the level of the original touch and not sure it is something i can live with.
This is not to detract for the rest of the ROM. It is superb, and the current bugs are minor, and no doubt the guys and gals of the AP team will fix them all in no time. I just am not a big fan of touchflo and would rather it was not there. but hey, we all have our own personal tastes.
I am unhappy with the autorotation of the screen (you can imagine while you are driving).
The device is times no responding because maybe touchflo way of work.
I don't see special speed or capacity improvement from ap 3 and times speed is lower than generic 6.1
Bluetooth disconnect more often, but not sure if it is because I moved radio 1.53
The other point I see is that there are too much stuff programs for me. I use other ones and the problem is memory...
still waiting a vainilla version, if it is possible.
I would like to be a technician in order to understand the memory improvement this rom has meaning, may I ask somebody to explain please?
Hello together,
at first: sorry about my english
since today i get touchscreen settings
despite the fact that everything worked, it suddenly appears as of today.
but also between the normal operation can not use my touch screen
sometimes i need 10-20 few times more than 30 tries to get back in system...
im on blanc build actually
i have testet this builds (today only!!!)
Mdeejay FroYo HD v.3.7 (this is actually on my card)
Mdeejay FroYo HD v.3.6
Mdeejay Froyo Sense v. 2.4.2
Mdeejay_eVo_Sense_v._1.8
Mdeejay_eVo_Sense_v._2.0
this programs are installes by default on first installation:
Superuser, root explorer, es file explorer, gscript lite
actually im on 7.6 - kernel
Radio Rom: 2.15.50.40 (but i have tested the 14 too)
the deactivation of my G-Sensor with the known script wont work too
i have tried to format my sd cards, u tried 3 cards, that cant be the problem there...
please help me *cry* i wont go back to wm6.5
soundclub said:
Hello together,
at first: sorry about my english
since today i get touchscreen settings
despite the fact that everything worked, it suddenly appears as of today.
but also between the normal operation can not use my touch screen
sometimes i need 10-20 few times more than 30 tries to get back in system...
im on blanc build actually
i have testet this builds (today only!!!)
Mdeejay FroYo HD v.3.7 (this is actually on my card)
Mdeejay FroYo HD v.3.6
Mdeejay Froyo Sense v. 2.4.2
Mdeejay_eVo_Sense_v._1.8
Mdeejay_eVo_Sense_v._2.0
this programs are installes by default on first installation:
Superuser, root explorer, es file explorer, gscript lite
actually im on 7.6 - kernel
Radio Rom: 2.15.50.40 (but i have tested the 14 too)
the deactivation of my G-Sensor with the known script wont work too
i have tried to format my sd cards, u tried 3 cards, that cant be the problem there...
please help me *cry* i wont go back to wm6.5
Click to expand...
Click to collapse
It seems to be a hardware problem rather than software or Android problem Did you remember if your HD has fallen in the last days? Try to make it work in Windows or try to hard reset your Phone if everything goes wrong. Maybe you are lucky. With my previous phone I had similar problems.
it isnt a hardware-problem, in windows mobile is no problem, i have tried the last 30 minutes without freeze
and no, my hd2 has not fallen, till yesterday 5 pm were everything ok, without any freeze in last months
I get that occasionally too. I have just reported sometimes as many as 3 times before it behaves.
Sent from my HD2 using XDA App
me too
happens to me too, from time to time.
freeze last about 2 secs max.
Im using evo kernel (20?, oct) and the android 2.2.1 build.
okay....it was a silent death of my TS ...
now under windows mobile wont work too (with original wm build...)
i wrote htc support for repair/change of the phone...i hope they will answering fast *cry*
iAm also having this problem, iThought it was my android build at first but iTried a different one and it still continued to freeze. Then iUsed wmo for a whole day and the freezing attacks continued.
I am having the same problem myself!
Whenever I use the red power button, whether it is for waking up out of standby or using a long press to activate the Phone Options menu, the touch screen stops working.
I have found that waking up the phone, then quickly putting it back to sleep and waking it up again gives me about a 90% chance of it working. So I have to press the power button 3 times in quick succession to wake up my phone now.
I hope I won't have any serious long term effects on my phone, but I'm definitely going to be talking to HTC and T-Mobile about this soon.
it happenned with me also when im using 16 gb memory that come from the phone. but when im using smaller one (8gb class 2), it work fine. maybe 16 gb took long time to read.my suggestion try it with smaller capacity or you can buy new one with higher class(6 or maybe 10)
joeispopular said:
iAm also having this problem, iThought it was my android build at first but iTried a different one and it still continued to freeze. Then iUsed wmo for a whole day and the freezing attacks continued.
Click to expand...
Click to collapse
Most annoying posting style ever.
iRecommend selling your HD2 and buying an iPhone.
Have you wifi on ? If I use wifi or wifi hotspot then after the phone wakes up I always get a touchscreen freeze it's definitely not the hardware.
Tried G sensor fix? i.e. editing AK8973Prms.txt
This has something to do with android on the hd2 eventually causing it, I work for tmo n see all the issues with the hd2 n this has never been an issue so I thought it was just me when it happened to me I just exchanged my hd2 and its fixed but now I see more people having the issue n the only thing thats common is we use android
Sent from my GT-I9000 using XDA App
apallohadas said:
Most annoying posting style ever.
iRecommend selling your HD2 and buying an iPhone.
Click to expand...
Click to collapse
iRecommend for you not to replay if you dont have a solution to the problem at hand.
I think it's due to the G Sensor. I have meet this before and have some test on my HD2. I found that if some application running on G Sensor, it may cause the freeze, ie GPS, Google Map， Compass. I am not sure this is due to my setting.
I shut down the G Sensor by Gscript and the script below found in XDA and seems this help. I hope this can help you too.
1. Create a script name 'Stop'.
SU is required, input
mv /system/bin/akmd /system/bin/akmd2
killall akmd
save this script and run, it will shut down the G Sensor.
2. Create a script name 'Start'
SU is required, input
mv /system/bin/akmd2 /system/bin/akmd
/system/bin/akmd
save this script, and you can run this to restart the G Sensor while u need it again.
I dont' know whether there is some widget or application to control the G Sensor better, but you can try this first to check if G Sensor cause this problem.
I found if shut down G Sensor, the GPS won't work. If anyone have idea how to make GPS work without G Sensor please advice.
apallohadas said:
most annoying posting style ever.
Irecommend selling your hd2 and buying an iphone.
Click to expand...
Click to collapse
hahahahahahahahahhahahaha
Turn your WIFI off then put it to sleep, works for me 100% of the time.
Same problem here. All ROMS based on HTC Sense freeze. Press the turn off button once and wait for 5 or 10 mins, and then the phone doesn't come back from lock anymore. This issue doesn't seem to be happening with any Nexus one Roms.
I have tried all possible solution, WM roms change, SetCpu, etc...
Jade.N said:
Same problem here. All ROMS based on HTC Sense freeze. Press the turn off button once and wait for 5 or 10 mins, and then the phone doesn't come back from lock anymore. This issue doesn't seem to be happening with any Nexus one Roms.
I have tried all possible solution, WM roms change, SetCpu, etc...
Click to expand...
Click to collapse
If press turn off button while it's freeze, it's hard to come back from lock. While it's not freeze, press any key while the phone is locked, if the screen is not come back, I still can touch the screen and the unlocked screen will be come back again.
I think it's a problem that the screen won't turn on immediately after we press the button, but at that moment, the phone can receive our control by touch the screen. If it's freeze, touch screen is not work, so keep dark. But if it's not freeze, the screen will be on. So I think it's the problem to solve the freeze problem.
HD2 t9193 touchscreen repair
Anyone know where I can buy this part?