Related
Hey guys. I've noticed that my new XDA2s is horribly slow and unstable in comparison to the XDA2 which it replaced courtesy of my insurance.
Anyway, thought that as its so appaulingly slow, the "close" feature of pocketplus would be brilliant for speeding things up a tad (and hopefully stopping the chronic crashing).
Anyhow, although it works, it seems to make sending text messages... well interesting. They take up to 4 minutes to send IF they send at all.
My friend with a 2s (with imate ROM) also experiences the same problem. Anyone found a way around it? Sorry if this has already had a thread, I'm a bit of a n00b and I dont think I understand the forum search properly lol.
Cheers -Mike
Hiya Mike,
The trick is to not let Pocket Plus close the Messaging program. To do this, go to Pocket Plus options, select the close button options and select the "Exceptions" tab. Add the messaging program (should be "tmail.exe") to the list and this should solve your problem.
Craig.
that sure helps!
cheers!
I can't believe I didn't think of that! Lol. Cheers bud, I'll give it a go when I get back to my docking station
Perfect Thanks for the help.
I've just added Pocket Plus today and within 4hrs, i've soft reset it 3 times. Does anyone know why? I'm using XDA IIs with Pocket Informant and Pocket Breeze. My wireless standby light still flashes green but the Today screen is completely frozen.
Does anyone know why? or maybe offer some insite as to why?
Thank you.. !
Same for me until I stopped playing with SPB Pocket Plus options. Leave them alone and all should be well. I contacted SPB and they said they couldn't replicate the problem but many others on this forum have had problems.
My Xda 2s need resetting about 4 times a day regardless. It likes to freeze when I press the hardware buttons. I reckon if I do 4 different tasks (ie. recieve a call, send a message, listen to a song and open Word for example) I can rely on having to coft reset. Mina does th same as described above. It also likes to not bring up caller ID, or I get calls which connect, but hang up on the other person. I'm really surprised this thing passed trading standards :s
I love my orbit but there are certain things I want to find out if they can be tweaked/changed.
1, can you modify the registry to use a bluetooth headset for audio on media files being played back through tcpmp ?
2, is there a way to return the phone automatically to the today screen after finishing a phone call ? I hate having to manually shut the screen after a call all the time
3, is there a way to improve the camera quality, its pretty poor ?
4, I use resco file explorer and on the today screen the icon for the battery has started to dissapear at random times, any ideas ?
5,when you finish a call you have the number on the screen, is there anyway to set the scroll key to go through the call history on that screen as opposed to having to go into the call history menu ?
Already reading on the loudspeaker distortion and loudspeaker while using tom tom have been helpful.
thanks. anyone feel free to add any niggles of your own you may have.
the answer to all these is:
buy something else.
wow what a constructive post...
constructive and realistic. Thanks.
1. I thought that was the whole point of A2DP, I don't use this so no real idea. Search "btaudio" and start from there.
2. Mine does this after a few minutes anyway. Otherwise just press the red call end button again. The fastest time you can force it in the settings is 1 hour.
3. It is possible the software could get updated in the future which may make some difference, but to be honest the camera is a bit of an extra thought anyway, phones never beat real digital cameras. don't just snap on default settings though, but good lighting is essential for a half decent shot.
4. Personally I reduce the amount of today plug-ins as much as possible, I don't like them or trust them. If it's the battery monitor itself that is important to you, check out this http://forum.xda-developers.com/showthread.php?t=270751&highlight=battery+status and here http://forum.xda-developers.com/showthread.php?t=263951&highlight=battery+monitor
5. No
6. Don't buy another device
thanks for that, at least some people have sense, I know BTaudio lets you playback the TT voice through a standard headset, wondered if it would do the same for media as opposed to buying a a2dp headset. thanks for the response anyway
So few artemis users on this forum says something, hermes.
Just get on with the rom HTC please.
eh ?
Hi Amino, I always seem to make dumb posts.
What I Meant was, if you consider this site as a whole, then the artemis appears to be an unpopular device. People have love hate things with it. All the active artemis threads are moans. I love mine but it also really pisses me off when it lets me down, which I personally put down to the shoddy rom and why I am waiting for wm6 before I attempt to change the shipped rom. Whereas the Hermes is already running wm6 and got gps and 400mz and a very busy forum.
Yes I am right, I always make dumb posts.
uniqueboy said:
Whereas the Hermes is already running wm6 and got gps and 400mz and a very busy forum.
Click to expand...
Click to collapse
But the Hermes doesn't have GPS.
The only reason that I put up with the Storage Card corruption problem on the Artemis is that it's about the only device with built in GPS that's worth considering.
You are right Philip, GPS is not working yet on hermes but, having read some of the threads they are only short of an arial. Maybe I need one of those eten things.
Trust me Uniqueboy if u want GPS that works DO NOT buy an Eten!!!
They take ages to get a gps lock even when driving with them in a cradle on a nice day, the connection also drops out quite randomly and often takes a good few minutes to reconnect. As you can imagine this is particuarly annoying when using TomTom in an unfamiliar area!!
Not sure if this is a design function but everytime I turn the device off it returns to Today's screen.
Actually even when I toggle to screen in WMP and turn the screen back on the PPC throws me back to Today.
I initially thought it was a problem with my ROM (LSG then Custel 1.3) but after flashing to VP3G 3.0 on my 8525 (I have both an 8525 and TyTN) and without anything else installed it does that.
Any ideas if this can be changed? I'd like to open app to stay visible.
Thanks in advance for the help.
I really don't have this problem on my ROM, see signature. I have especially tested it for you to be sure.....
Perhaps flashing 1 device to a different ROM. Can you see it yourself.
that's what i figured so I had my 8525 that was running WM5.
I HardSPL, SuperCID it then flashed it with VP3G.
There is nothing else on the phone but my exchange and pop account setup, owner info and basic stuff like this.
I also have the clock shown on every apps and the extended rom unlock/mounted (though it does it with or w/o).
My TyTN is running Custel 1.3.
I just can't think what could be causing the device to always minimize open apps when the phone is turned off (standby).
It seems that some plugins force a redraw of the today screen when coming out of stb. Nothing much to do but turn off the offending plugin.
Go to settings/today and on tab for objects remove the flag for timeout. Problem gone.
Nice try, no prize - problem not gone.
This appears to be a WM6 "feature".
This discussion exists in another xda thread here, and in a Microsoft forum here.
HunterST said:
Nice try, no prize - problem not gone.
This appears to be a WM6 "feature".
This discussion exists in another xda thread here, and in a Microsoft forum here.
Click to expand...
Click to collapse
This is a really annoying "feature" of WM6. So far no answer in the Microsoft forums regarding this. Would be glad if i could return to exactly the screen where i switched off the device or in which the timeout forced it to suspend.
If it is not possible to fix this with a registry hacking, would it be possible to develop a small helper application which saves which application was open before the atual suspend takes place and upon a wakeup reads this information and switches to the last active window ? The app itself is still active, isn't it ?
Regards,
Secuspec
Wait. So what exactly happens? I also used vp3G 3.0 and let's say I have Resco File Explorer open and my phone sits idle for 1 minute and goes into standby mode.. when I press the power button to make the screen turn on again, it still shows Resco File Explorer for me.. Is the bug causing it to go back to the today screen every time the phone goes into standby mode?
if a program is left open when the device is turned off (or screen "muted") the program will be minimized when you turn the Pocket PC back on (you're kicked back to Today).
Glad I'm not the only once having issues. Thought it may be a design (flaw) but IMO it's a crappy one. Wish someone can find a fix.
interesting, it looks like if you remove the device password it doesn't minimize the apps. kinda weird IMO.
samw52000 said:
interesting, it looks like if you remove the device password it doesn't minimize the apps. kinda weird IMO.
Click to expand...
Click to collapse
Isn't that what you would expect if you have a device password set!?
Mike
ericc - that's exactly the problem. Are you sure you're really going to "sleep", and you aren't just seeing your backlight turn off? (you should have to hit the power button to wake it back up).
Especially annoying when driving with navigation software - I want to just turn it on and see what I saw before it went to sleep.
MikeC - that's a very interesting point. I have exchange push email going, and my system administrator pushes restrictions onto my phone... I use Zenyee Stayunlock to allow me to change the ridiculous 5-minute lockout to something more reasonable.... perhaps either the device lock or Zenyee is the culprit.
mikechannon said:
Isn't that what you would expect if you have a device password set!?
Mike
Click to expand...
Click to collapse
Actually not really... my Windows workstation locks I expect to see the program I had maximized still on screen not all down in the toolbar minimized. IMO that doesn't make much sense (and even if it did they should have an option to select the default behaviour).
HunterST said:
Nice try, no prize - problem not gone.
This appears to be a WM6 "feature".
This discussion exists in another xda thread here, and in a Microsoft forum here.
Click to expand...
Click to collapse
Works fine on my Tytn with WM6 official Swedish. I don't have a device lock enabled btw.
yes if the lock is turned off the programs will stay open and full screen on resume/screen toggle.
Problem seems to only take place when the device lock is enabled, no matter how long the lock period.
samw52000 said:
yes if the lock is turned off the programs will stay open and full screen on resume/screen toggle.
Problem seems to only take place when the device lock is enabled, no matter how long the lock period.
Click to expand...
Click to collapse
Thanks for the hint samw52000! That perfectly worked for me And it also sped up a lot of programs directly after wake up -what makes perfectly sense since no other program is interfering anymore.
Long time after last reply, but still no solution.
I notice if time in suspend mode is longer that programmed in settings/Lock/Prompt if device unused for... (if you have to tap your password) then screen is same as before suspend.
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
Hi guys I have a problem with the touch response on my G4 (H815)
Basically when I use multi touch (and sometimes just normal scrolling) in certain apps the phone will recognize screen taps at the bottom of the screen at the home and back buttons and sometimes other areas, I have used the 'multi touch app' from the play store to confirm that this is indeed the case. This is extremely annoying as apps exit by themselves because of this. It doesn't happen every single time either, just sometimes but often enough for it to be annoying and so may be hard to prove to my carrier or LG if i send it back cause they may say there's nothing wrong with it.
It seems like a hardware issue and in that case the phone should still be under warranty right? I got it in August and haven't rooted or done anything invasive.
There are many people having issues with the G4 touchscreen. Check with your carrier and see if you can exchange it or what your options are.
Hi,
Same problem for me, the back and home button seems possessed. Se this video dropbox.com/s/540ozmvdnhemv8f/MOV_0005.mp4?dl=0 for an example. I bought the phone Thursday last week and it have been this pretty much since unboxing. After a factory reset the phone acts normal for a couple of minutes or hours, but goes back to that stage were I can't use the phone at all. I've managed to update to the latest software but the problem didn't go away. I'll try to contact the supplier I bought the phone from and exchange it tomorrow.
Since I do not have enough posts to post external links you have to figure out for youself what to type infront of the "link" I included.