Related
I've been having problems with copilot - it fails to acquire any satellites until I soft reset; then it works fine. A couple of days later I try using copilot again and the same thing happens. Anybody got any suggestions (other than use TomTom which I found was much more useable on my last XDA)?
are you updating the quick gps software every 3 days ? that may help but doesnt sound good enough
no - i'll give this a try, but it shouldn't stop it acquiring a fix even if it does take longer - I've waited for at least 10 minutes which is how long stone age GPSs used to take...
I definately think it's Co-Pilot verifiying the NMEA data that gets sent down. It's good because it ensures you don't get eratic positions (or most of the time anyway), but bad because as you've found out it takes a while longer to aply a fix. Can't really recommend anything other than to ensure QuickGPS is upto date.
Put it this way, the GPS program we wrote at work I've tried on my Orbit and I can get a signal lock in about 4 seconds with a pretty damn close position of where I am, so it's definately not the hardware (unless it's your particular phone).
The only reason I didn't buy a Touch Pro was the problem with GPS accuracy and lag when using TomTom (I use TomTom all the time on my Eten Glofish M700 and have got used to the quick locking and excellent performance of the SIRF III chipset in this phone).
Does anyone know if the GPS lag problems have been fixed in the Touch Pro 2?
I searched around and didn't see an answer to this yet.
Has it been fixed?
Seeing the tips and tricks section contain the same suggestion as we had for the TP makes me think not . . .
I now own a TP2 and can confirm that there is virtually no lag with either iGo8 or TT7 - both are perfectly usable
Using tt7 side by side with a TomTomGO they talk at the same time.....so no lag.....
I have been using TP2 with Garmin and Igo8 and comparing the lag with my in dash car Garmin side by side (using the same map).. can confirm that TP2 perform as good as my Kaiser .... no lag....
TP2 GPS
If TP2 GPS is the same as Kaiser, it's pretty bad. It takes forever to lock in Kaiser
rotaflex said:
If TP2 GPS is the same as Kaiser, it's pretty bad. It takes forever to lock in Kaiser
Click to expand...
Click to collapse
Both devices have different qualcomm chip and TP2 has an almost instant fix if you setup QuickGPS to update automatically.....
No problems here either, I have a fix within 20 seconds and it works great with TomTom 7! So I'd say go for it...
I also don't have any lag.
But I make sure that all other programs are closed.
Try installing you TomTom program files (not the rest) in main memory.
And try a softreset before you start navigating.
Using it with Navigon and no lag at all. Plus i get an almost instant GPS fix which is way better than the Touch Cruise I had before.
for me the TP2's GPS lock-on is almost instant, especially if you use advanced config and enable A-GPS
I'm pretty gutted reading all these posts, as my GPS is a small nightmare. It fixes VERY quickly - no probs there.
But - and I have done all suggested tweaks - there is a serious lag issue for certain. TT has to play serious catchip when you turn etc.
Think there are others in same situation as well if I remember correctly from previous threads.
martinjclarke said:
It fixes VERY quickly - no probs there.
there is a serious lag issue for certain. TT has to play serious catchip when you turn etc.
Click to expand...
Click to collapse
Same here.
All tweaks applied, fix is instant, but turning on the highway on a exit ramp is a nightmare.
TT is always 20 meters behind.
Also, when i boot the TP2 the GPS fix is instant, when the phone has been running for a few days and I start TT, the fix takes ages.
A restart of the TP2 solves this, after the reboot the fix is instant again.
Second problem: Sometimes using the TT for more than 30 minutes, the nav completely locks the current location.
Like there is the same location coming from the GPS.
Restarting TT solves it. This effect occurs rarely, but is annoying none the less.
Fanman1976 said:
Same here.
Second problem: Sometimes using the TT for more than 30 minutes, the nav completely locks the current location.
Like there is the same location coming from the GPS.
Restarting TT solves it. This effect occurs rarely, but is annoying none the less.
Click to expand...
Click to collapse
Same here but this is TomTom problem....
Fanman1976 said:
Same here.
All tweaks applied, fix is instant, but turning on the highway on a exit ramp is a nightmare.
TT is always 20 meters behind.
Click to expand...
Click to collapse
Just a thought.... do you think it could have anything to do with the read speed of a slower class SD card. I have a 16GB class 2 microSD card. Or maybe it's just an issue with reading the maps off the card.
I noticed that as well as my maps lagging, my music skips as well when the GPS is running.
Maybe it has nothing at all to do with the GPS.
Just my two cents!
I have bad lag on mine as well. The lock is pretyt much instant, no problems there, but lag on TT7, iGO8, Navigon are all the same - they all lag by at least 2 seconds and it's incredibly frustrating.
I've done so many different suggested tweaks, gone through advice from HTC, nothing changes it at all. So I don't know if it's a hardware problem if some are getting no lag and others aren't?
I'm running an 8GB class 6 SanDisk card. It's formatted correctly and everything, and ran like a dream on my Kaiser, but like a dog on TP2. I'm giving it another month or so (since it's a new phone), but if there's no fix from HTC by then, the phone's going into them to get looked at and will keep going back until my gps runs as well as some those with no lag.
[double post]
Well, this is slightly encouraging, but at the same time there were plenty of people who claimed their TP worked great and we all know the majority of those were ****ed with GPS lag.
Guess time will tell as more people get these in the US esp.
Yep - works fine using Memory Map too - bit slow on googlemaps, but that's just the time it takes to download the pictures.
runs great on my tp2...try to uncheck poi`s. more poi`s activated on mapview means more lag...i`ve had this problem on my i780 too.
===============UPDATE==============
The application was the SPB Fullscreen Keyboard v4.11 that was the culprit, verified over 3 hard resets that this is the offending program.
I hope this saves anyone else from going through the grief I have suffered. I completely forgot to include it on my list below so I am glad I had the patience to test one more time. (I ussualy forget to install it, then go to txt message or something and install it).
==================================
I am pretty much at wits end here and am preparing to return this huge lump of crap to the store. It seems that if I install "pretty much anything" and NOT use the touch-flo garbage... the phone will work great.... until i need or want to soft-reset it....
then the logo comes up, the ROM/RADIO numbers, and then the screen turns black, to never come on again.
Having worked for Sprint for 5 years, and moreover having built my own custom roms at PPCGeeks for 2 years I feel that I have a pretty good grip on the ins & outs of windows mobile.
I have NO clue what is going on with this phone.
I have three of them in my possession. It happens on all three.
I install each application, ONE-AT-A-TIME, soft reset after every single install, its fine. I wait a day or so, soft reset... SURPRISE you gotta redo your phone.
I have narrowed it down to a few programs that *may* be the cause of my irritation...
-Phonealarm (overrides the notifications...???)
-Ptravelalarm (and three other alarm programs) notification flaw???
-Memmaid (deals with notifications...???)
I dont expect anyone to know the answer, maybe someone else is having this issue (i hate Touch-Flo) and is trying to install programs to make the handset usable from the today-screen.
I am going to list my installed programs, and maybe, just maybe, someone smarter than myself can pinpoint the culprit.
-batti 2.4
-calendar plus
-sbp fullscreen keyboard 4.11
-google maps 3.21 (never GPS locks btw)
-iContact 95
-phonealarm 2.30
-pTravelalarm 2.81
-Resco File Explorer 7.05
-rlToday v22b
Thats it, thats all i use on my phone, im a creature of simplicity. On the todayscreen i have phonealarm, rltoday, ptravelalarm, calander+
I went to the forums for both phonealarm & memmaid, and there doesnt seem to be any threads with my issue. ptravelalarm has no support, but I have tried g-alarm, gsalarm & poweralarm, and they all seem to fail as well.
Again I cant narrow it down to a single application because after an install and reset it works fine. Its like "after the program simmers" that it wants to "Black-Screen" the phone.
I am 100% sure that a custom ROM will alleviate all of my issues as I am using all of those programs on a 6800 and a 6900, with WM 6.1 & WM 6.5 respectively.
They even work on the stock roms for both handsets....
Any ideas? How far out is the HARD-SPL? I have about 3 weeks left before I have to return these things.
Thank you for reading, and any help that may be forthcoming.
I'm having the exact same issue, it's very frustrating to pay $400+ for a phone only to have it blackscreen of death you every time you try to boot it up. Touchflo seems nice but it just adds extra button presses to what should be straightforward tasks. I hope things turn around but right now I'm not impressed.
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
I'm currently using an EnergyROM w/ Sense 2.5 on my Touch Pro 2 and am happy with everything so far, however my only let down with Windows Mobile is the types of applications made available for it.
I'm wondering whether it's worth me installing Android on my phone for the sake of having better quality applications and games?
Or is it still too early in development for something like that? I remember awhile back people were saying the sound wasn't working.
As far as Android go and whether its worth installing really depends on what type of apps you need. The sound is still not working on the external speaker at the moment as well as some other functions. With your current Windows build you are using, it will still be there. Android is installed on the external storage card. You can switch back after running Android by doing a soft reset.
Actually you dont need to even soft reset (well not with the stylus anyway), just hold down the lower right button and it will ask you to power down? then it starts back up in WM
Some people are using it as their main operating system but I just 'Play' with it. As mentioned ring tones etc is not working yet.
Mayflix said:
As far as Android go and whether its worth installing really depends on what type of apps you need. The sound is still not working on the external speaker at the moment as well as some other functions. With your current Windows build you are using, it will still be there. Android is installed on the sim card. You can switch back after running Android by doing a soft reset.
Click to expand...
Click to collapse
I think he actually means the external storage card. It doesn't hurt to try it out to see if it's something you'll like. You can always go back to WinMo by soft resetting your device.
if android worked as well on my touch pro 2 as well as it does on my touch pro, i would be using it as my daily driver. sound doesnt work, power management doesnt really work, but the apps are good and with sense its very pretty, and i feel i can jump in and play games and stuff without having to worry about not having a phone since it can still make calls are send texts. if the camera, sound, gps where working, and the battery could last for more than 2 hours, i would have no reason to go back into windows really. hopefully the touch pro 3 will be android or something. if just for getting sense on 2.1 in landscape.
The Jack of Clubs said:
if the battery could last for more than 2 hours
Click to expand...
Click to collapse
20+ hours standby with push email is WAY longer than 2 hours....
Besides, REAL tech flashing geeks wouldn't need to ask this question. Its a matter of trying it yourself, and coming to an educated conclusion on whether or not its worth it for YOU.
As started before it really comes down to teh apps you need. I been trying out android on my TP and besides the inaccurate battery meter its actually pretty good. I haven't made the ful switch over yet since I haven't found replacements to all my apps on WinMo but definitely found some good additions on android. Just tried it out for a while loading off the SD card and see how you like it.
Once they get TomTom on Android and that little app that transfers all sounds to your bluetooth headset in wm is when Android will become my prefered choice of OS. I like the idea of beeing able to "Dual Boot" back and forth from WM and Android. I would be completely OK with it if everything worked just using Haret.
As of right now personally I'm not satisfied with android on the tp2 as I was on the Kaiser but if they got that far on a 3+ year old device why not on the Tp2? I'm just hoping no one gives up on it.
starmena said:
Once they get TomTom on Android and that little app that transfers all sounds to your bluetooth headset in wm is when Android will become my prefered choice of OS. I like the idea of beeing able to "Dual Boot" back and forth from WM and Android. I would be completely OK with it if everything worked just using Haret.
As of right now personally I'm not satisfied with android on the tp2 as I was on the Kaiser but if they got that far on a 3+ year old device why not on the Tp2? I'm just hoping no one gives up on it.
Click to expand...
Click to collapse
Tomtom!?? Screw tomtom! Google maps navigator!!!!
I've used tomtom since my early days using palm phones. I love the ap but google maps make it look obsolete. Once they get the GPS working on our phones I'll probably start using the android WAY way more.
Here are the apps I MUST HAVE to switch 100%
1. calendar exchange - need to know when to get to meetings
2. google market - after download and before install with 2.38gb free on storage and hundreds of mb free on device get not enough storage error. need this to install google voice for free calls.
3. way to get repeating reminders and sms alerts. need to get to meetings or know when I have to call in for something.
4. wireless router app.
5. evernote - haven't checked it prob an app for it.
6. quick upcoming appts view and weather conditions with wind and number of unread messages for each account on home page.
I can reboot for music if needed.
Thanks guys for all your comments.
I decided to run the AOSP 2.1 as I heard Sense UI version causes a few issues.
Everything looks pretty normal, only that unfortunately most of the apps I want to run are not found in the market. (I've heard that developers filter apps based on phone model, locale or features)
The big issue for me is battery life.
I can charge the phone no problem but it always stays at 62% and the battery drains very quickly.
Games-wise: I tried to install a "3D" if you can call it that game called 'Replica Island' and couldn't even run it as it was too laggy, didn't even get past the intro stage. All the other simpler games I have had no problem with. I also installed Scummvm with a plugin/game but don't know where it was saved to on the SD. Most likely that will lag too as it did even in WinMo.
My issues so far:
Cannot get Gen Y Dualboot to work, it just says that Android cannot be found. (When installing Android I used the .rar version not .cab)
Can't get sound to work via earphones. It says "(in call mic and earpiece work)" Does that mean it only works if someone calls me?
Overall user experience in Android is much better than WinMo. In Windows mobile, I have to click many times to get to wanted app or menu entry, while I usually clicks once or twice to get there.
One big thing for me is Google Voice integration. My folks uses phone card from Rebtel to call relatives overseas. Their fingers aren't usually fast enough for Rebtel to accept all digits. Google voice eliminated all the hassle and steps of using phone card. I LOOOOOOOOOOOOOOOOOVE IT!!
I really like it and wish they would fix the sound and 3d so that you can run games.... I use it for testing only for now.
No sound, still ?!? Not worth it as a phone device. A play device yes, thats about it. Winmo for me I get to all my apps and prog in just one or two clicks. Learn to use your quicklinks.
ilabstudios said:
I'm currently using an EnergyROM w/ Sense 2.5 on my Touch Pro 2 and am happy with everything so far, however my only let down with Windows Mobile is the types of applications made available for it.
I'm wondering whether it's worth me installing Android on my phone for the sake of having better quality applications and games?
Or is it still too early in development for something like that? I remember awhile back people were saying the sound wasn't working.
Click to expand...
Click to collapse
Well, it's fun to play with for 10 minutes, but without working sound it's still pretty useless.
And I'm beginning to think the lack of sound problem will never be resolved
I'm beginning to think the lack of sound problem will never be resolved
Click to expand...
Click to collapse
Don't lose faith. It takes time because the developers have to go through extensive testing to make sure the features will work properly.
They are most likely focusing on improving the battery life first before they finish porting the other features, because what good is it having sound when the battery drains within 30-60 minutes.
I thought the battery is fine, it's just the readings/meter that is inaccurate
Wish it's not running in software emulation mode too though..it's a bit "laggy" to my taste
ilabstudios said:
Don't lose faith. It takes time because the developers have to go through extensive testing to make sure the features will work properly.
They are most likely focusing on improving the battery life first before they finish porting the other features, because what good is it having sound when the battery drains within 30-60 minutes.
Click to expand...
Click to collapse
20+ hours of standby with push email running is NOT 30-60 minutes. The battery IS fine, its just the meter that needs work. Charging even works now.
michaelra said:
I thought the battery is fine, it's just the readings/meter that is inaccurate
Wish it's not running in software emulation mode too though..it's a bit "laggy" to my taste
Click to expand...
Click to collapse
Just FYI, it's not emulated, HaRET unloads Windows Mobile and then loads Linux (and eventually Android) like a bootloader. Like Loadlin, if you know what that was. The slowness results from a lack of hardware OpenGL coupled with the fact that the Rhodium is a WVGA device running on an underpowered MSM7xxx chipset. While that lag can be improved upon with proper GPU support and some performance optimizations (and even a little overclocking), this device will never be as fast running Android as the Nexus One, or the Hero, or most other native Android devices.
The touch pro 2 uses the same (or very similar) processor as the Hero, correct? I guess the big "problem" going forward for the TP2 is the higher resolution screen. Even if HW support for graphics rendering comes to fruition for Android on the TP2, the processor will likely be the "bottleneck" in regards to performance..