Hi All,
I've been using Gullum's Prophet Touch VIII ROM for a couple of weeks now, and for the most part, it's performed very well. However, I do have a few problems (sorry about cross-posting this, but I thought that some of these issues may be related to WM6 and/or the touch interface in general, rather than Gullum's ROM):
1) The screen seems to become misaligned very easily, and I have to regularly align it again.
2) Screen taps/drags are very unresponsive. I usually have to click firmly (with the stylus), and pause briefly before I can then drag. Otherwise, the UI doesn't register the drag.
Could this issue (and no. 1) be related to the "flow" or "touch" interface? If so, I'd rather have responsive click/drag, so is there any way to disable the touch interface?
3) The speaker often goes into mute/vibrate mode. I've noticed that this seems to happen more often when I'm connected to ActiveSync, but that could just be a coincidence.
I wonder if this is related to the HTC "auto" profile? I'm not using auto, but just "normal". As a related issue, is there any way to edit the settings for these profiles?
4) Battery life. The batter life seems to be very poor. I see that other people have had this problem with the Touch VIII ROM as well, so at least it's a known issue. Some people say to remove HTC camera 4.11, but I don't think that software is part of the VIII ROM. Also, for the record, I don't use or have enabled wifi, bluetooth, or gprs.
Thanks for any help that can be offered on any of these issues.
Try Korand 2.6 WWE , it is the most stable dan fast ROM
Related
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?
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 ).
I had some problems with some of the latest (>20000) builds of Prophet roms when using together with TOMTOM 7.450 and an external bluetooth GPS antenna. It happened that, while running TomTom7 WITHOUT connecting my Prophet to a power source (i.e. my car's cigarette lighter plug) after 2-3 minutes the PDA auto-powered off. You can imagine the stress...
TomTom programmers managed to bypass the power management in order to prevent this annoying (and also very dangerous while driving) feature.
Unfortunately seems that latest builds' power management settings are completely ineffective at least with TomTom7. You can set the battery power management to NEVER OFF but it still will go down after a couple of minutes when running TOMTOM. All the latest roms that I've tried seem to be affected by this bug...
But maybe I've found a solution...
Use your favourite Registry Editor and check this:
HKEY_LOCAL_MACHINE\\System\CurrentControlSet\Control\Power\DisableGwesPowerOff
In my case it was set to 0.
I've changed it to 1 and voilà!!!
Seems that now everything works correctly:
1) TomTom Anti-AutoPowerOff is OK
2) OS's Battery power settings are OK
Hope I helped everyone who faced this annoying problem and I also kindly ask all the cookers to check this registry setting before releasing a new one.
Your,
Bodhi3
Bodhi3 many thanks for your information, I was having this problem and the only way that I found to solve it was to increase the sound in periods of time.
I will try it soon.
BR
Rui
It must depend on the build i am playing with a ROM build 21015 and this reg key doesn't exist but it uses Gwes i will look into this on my version thanks
curious did this work for anyone?
i tried it and no luck on build 7.915.9196
am starting to think its my ROM if more people are not having ths problem. i'll report back after i flash.
after trying everything possible and nothing working having blammed problems on bug in TomTom, it seems the problem was the ROM.
so i flashed a different ROM and can confirm TomTom is working fine and stays on regardless of power settings in OS
bodhi3 said:
I had some problems with some of the latest (>20000) builds of Prophet roms when using together with TOMTOM 7.450 and an external bluetooth GPS antenna. It happened that, while running TomTom7 WITHOUT connecting my Prophet to a power source (i.e. my car's cigarette lighter plug) after 2-3 minutes the PDA auto-powered off. You can imagine the stress...
TomTom programmers managed to bypass the power management in order to prevent this annoying (and also very dangerous while driving) feature.
Unfortunately seems that latest builds' power management settings are completely ineffective at least with TomTom7. You can set the battery power management to NEVER OFF but it still will go down after a couple of minutes when running TOMTOM. All the latest roms that I've tried seem to be affected by this bug...
But maybe I've found a solution...
Use your favourite Registry Editor and check this:
HKEY_LOCAL_MACHINE\\System\CurrentControlSet\Control\Power\DisableGwesPowerOff
In my case it was set to 0.
I've changed it to 1 and voilà!!!
Seems that now everything works correctly:
1) TomTom Anti-AutoPowerOff is OK
2) OS's Battery power settings are OK
Hope I helped everyone who faced this annoying problem and I also kindly ask all the cookers to check this registry setting before releasing a new one.
Your,
Bodhi3
Click to expand...
Click to collapse
Thanks for your fix i have made a cab file to automate the Job can you please test this and leave feedback all if it works we can add this fix to future Builds
I've tried the fix but it doesn't work when i start cab the system reboot and nothing happened.The rom is WM6.1 Build 21054 ...
Wap you are the best
Sidecar12
I have been tampering with my hero the last few days and now i have a problem. The part of the screen where the "^ phone + " is, is not working anymore. Even if i disable sense. When i'm in a game, that part works just fine. And when i press "menu" that part woks aswell.
I've put back backups wich didn't have the problem.. buit the problem persists. 'm wondering whether this could be hardware related. And what i can do softwarewise to resolve it.
Has anybody heard of a similar problem before?
(i'm on modaco 2.9 atm)
edit: when i wipe and install a new udate.zip (for instance 1.6 ion) the problem persists.
are you talking about the screen not working (e.g. a black bar, weird lines or something) or the TOUCH not working (e.g. graphics are fine, but screen is not responding in the lower area)?
kendong2 said:
are you talking about the screen not working (e.g. a black bar, weird lines or something) or the TOUCH not working (e.g. graphics are fine, but screen is not responding in the lower area)?
Click to expand...
Click to collapse
Oh sorry, that was unclear. The display is fine. Touch is not working.
So, did a wipe. Did a rom update. did a radio downgrade. All these things did not solve my problem. Maybe it IS hw related? Should i contact HTC?
I also got the same problem : very few time, the bottom part works... I just sent email to HTC (in French, because I am ), I'm waiting the answer...
i have that issue too since last week. i made this video.
.youtube.com/watch?v=j9wTVpqur_I
Often this needs sent off to HTC to get fixed, from what I've heard