Related
Latitude would be so much better if it would let me save my pic anyone else have this issue with the new rc33. It allows me to select one and then crop it but as soon as I get outta that menu it doesnt save and cant see an option to do so. Anyone else have this issue or know how to fix?
Dirtay said:
Latitude would be so much better if it would let me save my pic anyone else have this issue with the new rc33. It allows me to select one and then crop it but as soon as I get outta that menu it doesnt save and cant see an option to do so. Anyone else have this issue or know how to fix?
Click to expand...
Click to collapse
By default Latitude uses your Google pic. Have you tried setting a pic inside Gmail?
http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=35529
argh
jashsu said:
By default Latitude uses your Google pic. Have you tried setting a pic inside Gmail?
http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=35529
Click to expand...
Click to collapse
I guess when I selected the pic it updated igoogle but not on my phone I dont understand????
One possible explanation is that the phone is showing cached icons rather than the freshest ones from the server. When you upload the pic to Google's servers (either via phone or computer), the phone is still using the cached old pic. It might take a few hours for the app to get the new pic from the server. You can see this same behavior in the Google Talk pc client.
BOO
jashsu said:
One possible explanation is that the phone is showing cached icons rather than the freshest ones from the server. When you upload the pic to Google's servers (either via phone or computer), the phone is still using the cached old pic. It might take a few hours for the app to get the new pic from the server. You can see this same behavior in the Google Talk pc client.
Click to expand...
Click to collapse
Lame ok I wait thanks let you know later if that worked
RC33 Jf mod latitude stuck in agree and share screen
Hi
I just upgraded to RC33 jf mod. have been trying out the new features.
I cant get Latitude to worl. whenever i try to start latitude, i get stuck at the agree and share screen. i get a busy icon with the message "saving your selection" and nothing happens
I have tried saving it using edge,3G and wifi.
the browser works fine so it should not be a network issue.
any ideas?
I'm also experiencing same issue
Upgraded to JFv1.41_RC33 w/ wifi and maps gets stuck on "saving your selection" after agreeing to latitude TOS.
Do you know if this issue is specific to JF/RC33. Would like to try out latitude.
Thanks
g4m3rz said:
Hi
I just upgraded to RC33 jf mod. have been trying out the new features.
I cant get Latitude to worl. whenever i try to start latitude, i get stuck at the agree and share screen. i get a busy icon with the message "saving your selection" and nothing happens
I have tried saving it using edge,3G and wifi.
the browser works fine so it should not be a network issue.
any ideas?
Click to expand...
Click to collapse
Resolved
I previously had JFv1.41_ADP1.1 installed, then switched to JFv1.41_RC33 (to use latitude).
I did a wipe in recovery mode (alt+w) then installed JFv1.41_RC33, and followed http://forum.xda-developers.com/showthread.php?t=452316 - phone doesn't have a sim card), and now latidude let's me agree to TOS, and works fine. I wonder if there was an issue with the google account since it was registered w/ ADP1.1 instead of RC33.
androiddemo said:
Upgraded to JFv1.41_RC33 w/ wifi and maps gets stuck on "saving your selection" after agreeing to latitude TOS.
Do you know if this issue is specific to JF/RC33. Would like to try out latitude.
Thanks
Click to expand...
Click to collapse
a wipe fixed the problem
Not a day goes by where I don't see someone having issues cos they didn't wipe after an update. I don't care if you are going between build types or not. If you update, you wipe. Case closed.
WTF is wipe? Sorry just don,t get it :S
hey when i try do the mod for rc33 it doesnt work i have spent hours and hours trying endlesssly to mod to rc 33 i modded it got multi touch so im at jf 1.4.1 i watched all the video tutorials looked at ones online but nothing works i getting sick of being stuck with rc 30 do u think if i did alt w the hack might work or alt b which im not completly sure what it does i think it wiped your sd card does anyone know what i should do plz respond by emailing me at [email protected]
do a wipe
Yes, I've found you must do a wipe (alt+w) when installing jf1.4.1 to get latitude to work correctly.
tom93 said:
hey when i try do the mod for rc33 it doesnt work i have spent hours and hours trying endlesssly to mod to rc 33 i modded it got multi touch so im at jf 1.4.1 i watched all the video tutorials looked at ones online but nothing works i getting sick of being stuck with rc 30 do u think if i did alt w the hack might work or alt b which im not completly sure what it does i think it wiped your sd card does anyone know what i should do plz respond by emailing me at [email protected]
Click to expand...
Click to collapse
So I used this app a while back and loved it but recently I have been doing a lot of flashing and such and just wasnt using it. Now I figured I want some custom ringtones again but after downloading Rings Extended I cant change the ringtones. When I go to the picker I only have the default options and not the option of launching Rings Extended. I also cannot launch it from the Market, I get an error "Rings Extended" could not be launched. I have tried uninstalling, restarting a couples times and installing again with no luck. Does anyone have any ideas?
If you ever backed up your phone go into the folder where your backups are kept (on your card) and find the .apk and install it by pushing it onto your phone?!??!
Try going into "Manage Apps," scrolling down to Rings Extended, and hitting "Clear Defaults." See if that helps.
same problem here. but...NOTHING helps. i realy tried everything. looked up a lot of forums, concerning this problem...like i said. nothing works
last time i had this problem, i gave the backup a trie, but it didn't work.
so my next idea was flashing the rom again, didn't work either.
finally i wiped my phone, flashed the original 1.6 rom from HTC and then flashed the newest rom, i want to use. THAT works...and yes, it was a long long evening.
well, i gess there must be another way, too. i must admit, don't know very much about program structures and things like that. so please i guess we need a expert for this problem -.-'
thanks in advance for any helping ideas!!!
Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "registered on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!
zimphishmonger said:
Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "used on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!
Click to expand...
Click to collapse
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.
ItsDon said:
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.
Click to expand...
Click to collapse
Doesnt work for me, and I've been working with support and tried EVERYTHING (uninstall\reinstall, re-register, all the suggested fixes, etc)
I signed up for the beta, downloaded the file and installed it. I could swype all day and nothing appeared in the text box. Installed one of the previous unreleased versions and it worked fine, uninstalled and tried the beta again with same failure mode. Swype doesn't make it easy to comply with their requests to use approved software.
Both Swype support and myself have no idea why, but we were finally able to get Swype up and running on my phone.
Huge thanks for Brian from Swype support for his help, and I recommend anyone having issue to contact their support to see if you can get the issue resolved.
The app has a somewhat complicated (encrypted) registration process, and somehow that was not completing successfully, so def let support know if you are running into similar issues
This happened to me too. I gather it happens every time I install a different ROM, I need to contact Swype to get my Beta account re-authed.
Stuff that, I can't be bothered, I'll just wait until the paid version comes out.
Thought I'd give it another try and still get the "Limited Functionality..."...As usual with restricted access, DRM, etc, it is the ones who try and follow the rules who lose...the pirates will always find a way. Back to the leaked version for me, I guess, though I do think the HTC IME keyboard is still faster and more accurate.
I also get the "limited functionality" message, but only occasionally.
I haven't tested this hypothesis, but seems like it only does this to me when I am at home--and when I'm at home, I'm usually on wifi.
Maybe there's some kind of DRM that didn't take into account that people may occasionally switch from 3G to wifi connections.
If I had more time I'd try messing with it a bit, but I'm just headed to sleep.
There's probably a call home check on first application start up. When you wipe or switch ROMs, that will be cleared, but their servers already have the product registered.
Try backing up the app-data for Swype in between wipes/ROM updates.
I got the "limited functionality" message every time, no ROM updates between download and install. I even reinstalled the installer, redownloaded, etc and it just doesn't work. Glad it didn't work, because it convinced me to go back to HTC IME which is faster and more accurate for me.
http://www.mediafire.com/download.php?toniw2xejzz
its from the other swype thread and this worked for me.
hope for the rest also
well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.
I have confirmed with a swype tech that there is a registration\call back home immediately following the install of the apk. If successful it will have a quick spinner stating "reristering swype" and the ask you to "enable swype".
I, unfortunately, seem to have major issues getting it to actually call back home, where it states "Swype has already been installed. please uninstall and try again" (I had previously uninstalled it).
In the end, had to revert back to the leaked versions
m_kayali said:
well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.
Click to expand...
Click to collapse
Ive tried MULTIPLE times to uninstall and reinstall swype w/o rebooting, so I think it wouldn't have a chance to zipalign until the next reboot.
Kind of sad that Swype hasn't gotten back to me yet
Somehow, I am using the Beta version I downloaded myself. I was trying out Super D for a week which is when the Beta was open, later I went back to Dwang and Swype broke when using the Beta installer but I got it working using AppMonster. Here's the steps I followed over that time:
- Wipe phone and install Super D
- Install AppMonster from Market
- Sign up for Swype Beta
- Download SwypeInstaller and install Swype Keyboard
- Perform backup with AppMonster
- Wipe phone and install Dwang
- Download SwypeInstaller and install Swype Keyboard
At this point I got the "Limited Functionality" message
- Wipe phone and install Dwang again
- Install AppMonster from Market
- Restore backup of Swype with AppMonster
Now I can go into Settings and enable Swype in the usual way. I have been using it without a problem for a couple of weeks now.
What solved it for me
I had Swype installed and working on a G1 with Cyanogen latest but after an uninstall it stopped working for me with the same error messages as described here in this forum.
What solved it for me is not pushing the done button on the touch screen after the package install but pushing the back key on the phone. This got me in the registering Swype screen after which the swype installer crashed. Swype is fully working however using these steps.
just go back to installer , log in and reinstall. Everytime i flashed a new rom i did this. I found out u can do this 10 times, before they cut u off. Obviously they know whats up?!
obviously i like the real beat with vibration option and more stable. im using now the final pre release that was made available in a couple posts above mine. no vibration, but it works. this keyboard is fantastic!
**THIS FIX DID NOT WORK LONG TERM FOR ANYONE NEW READING THIS** Below information is for review and trial & error purposes only.
*Another main thread in Vibrant Q&A is found here for further issue tracking as well: http://forum.xda-developers.com/showthread.php?t=847403
This may help some of you out and maybe not but wanted to share to help out.
I had MMS/Picture Messaging problem (Error in Server Response) with Obsidian v2 & v4.2 ULF until I followed steps below:
This fixed it perfectly for me:
Go to your main menu settings.
Than Applications, Next Manage Applications, than Running Applications.
Click on "Messaging", Click "Clear Data"
Exit back to main screen.
Now open messaging.
Go to messaging settings by hitting the menu button on the phone.
While in messaging settings page, hit the phones menu button again,
only one option appears to "Restore Default Settings".
Click it & exit.
Now try to send a MMS/picture message. Worked like a charm for me.
Hope it helps some of you all out.
I'm running on Axura 2.4 and been having this problem. Thanks a bunch for the remedy!
Your welcome. When I had the issue I kept seeing other posts about the issue with no real fix solutions offered. Some one suggested to type a 1 in front of your contacts to get it to work but I thought their had to be a better way if my SMS worked just fine. So I explored further and this worked perfectly for me.
Thinking problem is from lag fix conversion process or from flashing between 2.2 ROMS. But was easy fix either way now that I know.
Thought it might help other 2.2 ROMS as well with similar issues.
does not work....eugenes froyo odin
I also briefly tried telling the phone to connect automatically to a preferred network when I explored fixing the issue on my phone. So other people could try that as well if still no luck with the above method. I'm just glad if ti fixes some peoples MMS problems mainly Obsidian ROM since that's what I'm running.
If does not work with Eugenes or others...well that why I put in CAPS "POTENTIAL FIX" lol
Nope... it doesn't work. Putting a 1 in front of the phone number does work.
Edit
I am running Obesidian V5 Beta btw. But i had this same problem in Obesidan V4.2
Tried to send another mms and it didn't work anymore. Went back and repeat your setting steps again and it still didn't work. Thanks for the effort. It was fun getting that one mms to send.
Export your contacts to your sim card, and you might show double contacts, but use the one on your sim, and BAMM , it will send without a hitch.
This POTENTIAL FIX did not fix after all permanently. Problem appeared again. Tried and still no luck. Going to look into further. If something else comes to mind will share again. At least it was a glimmer of hope to have it work normally even if briefly without a "workaround" approach.
Same mms problem here. Mms seems to work when using wifi calling app though. Obisdian 5
Sent from my SGH-T959 using XDA App
feelx77 said:
This may help some of you out and maybe not but wanted to share to help out.
I had MMS/Picture Messaging problem (Error in Server Response) with Obsidian v2 & v4.2 ULF until I followed steps below:
This fixed it perfectly for me:
Go to your main menu settings.
Than Applications, Next Manage Applications, than Running Applications.
Click on "Messaging", Click "Clear Data"
Exit back to main screen.
Now open messaging.
Go to messaging settings by hitting the menu button on the phone.
While in messaging settings page, hit the phones menu button again,
only one option appears to "Restore Default Settings".
Click it & exit.
Now try to send a MMS/picture message. Worked like a charm for me.
Hope it helps some of you all out.
Click to expand...
Click to collapse
Excellent Work! This fix worked for me as well. That's what's up!
Spoke too soon. I stopped working for me as well, and I cannot make another go thru. Darn!!!
Didn't work for me but I found that using another sms app like chomp worked for some reason. Kind of a hassle but it worked.
Sent from my SGH-T959 using XDA App
Hi guys, I really hope I can get some help here, can't find anything about the problems I am encountering.
I am using this phone for about 4 weeks now, and it's working fine, except for some problems with widgets. I have problems with 3 apps/widgets now; they all worked fine on my old phone, a HTC Sensation XE (rooted, with different ROM's and Android versions). They all have strange behaviour. At first I thought I had some settings set wrong in the apps themselves, but I tried everything I could think of and now I have to conclude that the problems start with the phone itself.
I am encountering problems with the following apps:
aCalendar+: widget, but also opened app get in some kind of update loop; sync icon starts spinning, stops and immediately starts again, and on and on. It does sync properly though in the meantime.
Plume: Most of the time the widget does not respond to manually syncing. Only after I open the app and sync manually (which works fine), and go back to the widget, I can finally sync using the widget.
Transparent clock & weather: Most of the time, the clock does not keep track of the time, it just hangs. Only when I tap the widget, or refresh the weather, it syncs with the internal clock, like it should. Sometimes though, the clock does keep track for a short time, but in the end it will hang again.
I tried out a lot of different things with the P7 energy- and network apps settings. Also I upgraded to firmware version 126, but it all doesn't make any difference. It's all really annoying, especially because I never had those issues on my old phone.
Anybody got a clue?
flupke02 said:
I am encountering problems with the following apps:
aCalendar+: widget, but also opened app get in some kind of update loop; sync icon starts spinning, stops and immediately starts again, and on and on. It does sync properly though in the meantime.
Plume: Most of the time the widget does not respond to manually syncing. Only after I open the app and sync manually (which works fine), and go back to the widget, I can finally sync using the widget.
Transparent clock & weather: Most of the time, the clock does not keep track of the time, it just hangs. Only when I tap the widget, or refresh the weather, it syncs with the internal clock, like it should. Sometimes though, the clock does keep track for a short time, but in the end it will hang again.
I tried out a lot of different things with the P7 energy- and network apps settings. Also I upgraded to firmware version 126, but it all doesn't make any difference. It's all really annoying, especially because I never had those issues on my old phone.
Anybody got a clue?
Click to expand...
Click to collapse
Can you provide the play store links of this apps?
I would try and test it.
This apps are enabled in protected apps?
flupke02 said:
Transparent clock & weather: Most of the time, the clock does not keep track of the time, it just hangs. Only when I tap the widget, or refresh the weather, it syncs with the internal clock, like it should. Sometimes though, the clock does keep track for a short time, but in the end it will hang again.
Click to expand...
Click to collapse
I have test this app.
I think you mean this app: https://play.google.com/store/apps/details?id=com.droid27.transparentclockweather
I was able to reproduce your problem and solve it.
Please set this app as "protected app". You didn't have set it, so the app would be closed then the screen get off.
You can set this: Settings -> Protected Apps -> Check the checkbox of this app.
Then your widget is working.
Then an app don't set up as protected, the app would be closed on screen off.
DJ BlackEagle said:
I have test this app.
I think you mean this app: https://play.google.com/store/apps/details?id=com.droid27.transparentclockweather
I was able to reproduce your problem and solve it.
Please set this app as "protected app". You didn't have set it, so the app would be closed then the screen get off.
You can set this: Settings -> Protected Apps -> Check the checkbox of this app.
Then your widget is working.
Then an app don't set up as protected, the app would be closed on screen off.
Click to expand...
Click to collapse
Thanks for your help, I already tried that out before. It do not think it made a difference though. Anyway, the time freezing issue also happened when using the phone for some time, I mean without screen off time, so it should not make any difference. But in the meantime I updated the app, and that seems to work.
The links for the other apps:
https://play.google.com/store/apps/details?id=org.withouthat.acalendarplus&hl=nl
https://play.google.com/store/apps/details?id=com.levelup.touiteur&hl=nl
I contacted the developer of Acalendar+, and as far as I understood there should be an update coming in the near future that should resolve the problem. I installed another calendar app in the meantime, which just works flawlessly, so maybe I just stick to that one...
I hope Plume gets a working update too, so I can enjoy me phone without being annoyed
Thanks again for your effort!
flupke02 said:
Thanks for your help, I already tried that out before. It do not think it made a difference though. Anyway, the time freezing issue also happened when using the phone for some time, I mean without screen off time, so it should not make any difference. But in the meantime I updated the app, and that seems to work.
The links for the other apps:
https://play.google.com/store/apps/details?id=org.withouthat.acalendarplus&hl=nl
https://play.google.com/store/apps/details?id=com.levelup.touiteur&hl=nl
I contacted the developer of Acalendar+, and as far as I understood there should be an update coming in the near future that should resolve the problem. I installed another calendar app in the meantime, which just works flawlessly, so maybe I just stick to that one...
I hope Plume gets a working update too, so I can enjoy me phone without being annoyed
Thanks again for your effort!
Click to expand...
Click to collapse
Oops, I just found out you were right about the protected apps thing. I have not had the issue with the screen active since the last update, but indeed, after screen-off time, the issue is back again. So I guess I should indeed use the protected apps setting.
I don't understand why this is necessary though. I mean, the internal system clock just carries on ticking in standby mode, so why wouldn't the app just sync with that automatically when I activate the screen? Or would it be so that the app has always been active in standby mode on my old phone, and is it only because I now have this protected apps mode on this new phone that I am getting aware of this? If you understand what I mean, this is quite hard for me in English...
flupke02 said:
Oops, I just found out you were right about the protected apps thing. I have not had the issue with the screen active since the last update, but indeed, after screen-off time, the issue is back again. So I guess I should indeed use the protected apps setting.
I don't understand why this is necessary though. I mean, the internal system clock just carries on ticking in standby mode, so why wouldn't the app just sync with that automatically when I activate the screen? Or would it be so that the app has always been active in standby mode on my old phone, and is it only because I now have this protected apps mode on this new phone that I am getting aware of this? If you understand what I mean, this is quite hard for me in English...
Click to expand...
Click to collapse
I've experienced similar issues. Like you I use aCalendar+ which is very good. However I don't use any of the widgets that come with this app. I prefer Smooth Calendar instead. So far, no problems at all. And as for the clocks, it seems a bit hit and miss. I was using DIGI Clock Plus but had no end of trouble with it. It just won't update on wake up. Protected or otherwise. I've given up on it. The clock widgets from HD Widgets work just fine. There's an amazing array to choose from. Maybe it's an Android issue, maybe Huawei. Who knows? I think the best solution is to find apps and widgets that work and discard those that don't.