|
||||
Quote:
Anyone seeing some strange behavior when using the stylus on the screen? I've aligned and re-aligned several times and it seems to just flake out every now and again... Edit: Okay it must have been the crack talking - or at least it's not something easy to reproduce. I've tested with the phone on (staring at it) and it works, with the phone in standby (again staring at it) and it works and with calendar entries synced over from activesync and it works. Maybe it was a coincidence in my case. |
|
||||
|
||||
can't use wireless + phone at the same time
read all 26 pages. using verizon with minimal cab2 installs as specified. Anyone else can't get them both going at the same time? When I turn wireless on, the phone turns off and vice versa
edited 2-5-07 I did not run the pt_wifiand radio_Apache.cab from the vz extended rom. When I did, the problem was solved
__________________
Ron
|
|
||||
Problem with backlight always reseting to 10 seconds
I have a problem with the Helmi_C ROM, where my backlight timeout (and a few other power settings) reset back to the default values every time my XV6700 comes out of power-down mode.
My backlight timeout always goes back to 10 seconds, regardless of how many times I set it to 30 seconds. As long as the phone stays powered-up, the backlight setting will stay at 30 seconds, until it powers down. Then it resets back to 10 seconds. I didn't have this problem under AKU 2.2. Has anyone found a solution to this? ¿GotJazz? |
|
||||
Re: Fixed Pictures and Video
Quote:
|
|
||||
Quote:
|
|
||||
I have read through this entire thread and have not found anyone else experiencing the same two problems as me, leading me to believe that this is an isolated incident and not indicative of a problem with Helmi_C's AKU 3.3 update, but I wanted to post here in the event that someone might have some words of advice.
I updated my mobile to AKU 3.3 using Helmi_C's AKU 3.3 update and performed two hard resets afterwards to ensure that it took and they everything would clean up afterward. I got the generic Telecom screen and the new Windows Mobile boot screen, and everything seemed to work well. The first issue I noticed though is that the "keyboard icon" at the bottom of the screen seemed to go missing from time to time, so I was unable to bring up the soft keyboard. I am not noticing this as much now, but I am not using it as much as during the initial update and install, either. The slideout keyboard works for most things, it is just when installing a couple programs, like cLaunch, that it really does not like landscape mode and the soft keyboard is preferable. The second problem that I am noticing is that my volume settings do not seem to stick. When I use my mobile at work, I tend to turn the volume off as to not upset my co-workers with the constant clicking. The problem seems to be that after a few minutes, the volume is back at the default level, about 3/4 of the way up the slider. I have turned off the device and turned it back on, and that doesn't trigger it -- the volume stays the same as I left it. I have let it go into sleep mode and turned it back on, and the volume stays as I left it. I have done both of these tests both on battery power and while plugged in. But if I leave the phone for a little while, just a few minutes, and come back, the volume is back at 3/4. Like I said, I have seen no other reports of this, and so it might be just something flakey with my mobile. I am with TELUS Mobility and there is not much in the way of extra software in the extended ROM. I need to search and find a way to go into my extended ROM, then I can provide a list of files in there. Most of it seems to be for setting up the EVDO stuff, though, so it's not too bad. Anyway, any suggestions or things to look at, and I'd appreciate it. Failing that, I might try to flash it again this weekend when I have more time. Thanks for all of the work that's gone into this. I appreciate it. |
|
||||
Did you let the vender/carrier stuff in extended rom install? it seems that is not all good for sprint and verizon - dunno who your carrier is, but its possible something installed there conflicts with aku3.3
|
|
|
|