Related
****UBER IMPORTANT NOTE****
It would appear that the fix I found described below seems to stop working after a day or so I haven't found any sensable way to way to get it back yet
I have left the rest of the post how it was incase you still want to try it or if anyone wants to work on it as for me I'm giving up on it for now and going back to APD1.1 (where latitude works anyway)
Sorry guys I really thought I'd cracked it sob
I have manged to to get it to keep the UK and German local settings so no xxx-xxx-xxxx format on numbers and things but the phone would show as a ADP1.1 Dev phone but if there are any people who are only on RC9 for the local and language settings who would like to keep them and have latitude and voice search I have that one sused just PM me if you want it. If enough people are intrested I'll do a write up on here but for now I want beer
<----Original Post---->
***NEW LINK IN (Thanks to LucidREM)***
Hi not sure if anyone else has worked this out I have read through as many posts as I could and haven't seen it anywhere else.
I can assure you that Latitude is in the RC9 update (I was one of the people who it didn't show up for), when I was reading throught the millions of posts on the matter I noticed that all the people who claimed it was there are all on networks outside the UK. I assume that if you have a MCC that is in the UK (or something simular) it is set somewhere simply not to show up. I guess T-Mobile UK think us Brits can't be trusted with letting our friends know where we are.
Anyway after giving you this sad news I have some good news. I know how to get it back (YEY) but more bad news its quite sloppy and it does involve a full wipe.
I basicly did a small bit of tinkering with the JF RC9 (hope he doesn't mind) I will add my version to this post if you want to do it quicky but also explain what I did if you want to try it yourself.
First with the origanal JF RC9 I opened the zip and added the lines below to the ADDITIONAL_BUILD_PROPERTIES section of the /system/build.prop file...
ro.setupwizard.mode=OPTIONAL
keyguard.no_require_sim=true
These options allow you to use the phone for the first time without a sim card and allow you skip the sign up to your google account screen (as obviously you won't be able to sign up without a simcard) These two options are standard in ADP and I just did a lazy man copy and paste.
Once you have done this you will need to replace the original in the zip with your nice new file. You will then have to resign your zip file there is a good guide how to do this on http://modmygphone.com/forums/archive/index.php/t-10591.html (again the amazing JF was involved in this tool)
Once you have done all that stick it on your SD card, call it update.zip, <--*take out your simcard*--> and wipe/update/reboot in the normal way.
When they No Sim Card Screen pops up press menu and it will take you to the sign into your google account screen. When you get to the bit where you can create a new account or sign in with your current account scroll down and there will be a nice skip button press that.
Next go into setting and connect to a wifi network once you are connected run any google app that connects to your account (gmail, IM, etc) this time put in your sign in details and wait for your address book and stuff to resync.
Next run maps and the Latitude info screen thing will pop up, press ok and then press the Join Latitude button. Once its all registered turn your phone off stick your sim back in and turn it back on and YEY Latitide will still be there. Install all your apps and set up your phone back up and happy days.
If you are not brave enough to make the changes to the JF RC9 update (or you just can't be arsed) I have attached the one I made below. Note I have removed the Amazon MP3 thing from this image as it only works if you live in the US and Shazam defaults to it and not Amazon UK if it's installed and that makes me a sad panda. As for voice search that isn't in RC9 at all, I will have a mess to see if I can port it from ADP or RC33 at some point.
Obviously I would like to thank JF for doing all the hard work in the first place hope he doesn't mind me fiddling with his stuff.
Hope you all find this post useful and let me know how you get on
***NEW LINK***
http://www.kyubinc.org/files/JFv1.43_RC9_LatFix.zip (Thanks LucidREM and to the others who offered to host)
***KEEP YOUR CURRENT USERDATA AND STILL HAVE LATITUDE*** (Thanks to TonyHoyle)
Perform prodecure as above to enable latitude.
Flash data.img from backup. Reboot. Do not replace SIM. Do not enter maps yet.
Using adb, Add the following to /data/data/com.google.android.apps.maps/shared_prefs/com.google.android.maps.MapsActivity.xml
<boolean name="FF_SHOWN" value="true" />
<boolean name="SHOW_MY_FRIENDS" value="true" />
(the second line will already be there - just modify it to 'true')
Now enter maps. Hit 'menu' and the Join Lattitute button will be there. Join, and it'll stay when you replace the SIM.
Like, WOW. I mean, erm, yeah, I was just about to do that, you beat me to it.
Nice work!
Kudos!
Havent tried it yet though
Hang on, you waited 3.5 years to make your first post?
Lol yeah I had a XDA something on O2 years ago but never had anything intresting to say about it Hadn't really been back since as after that broke I decided I would't get sucked into new mobiles and went back to a Nokia 3310. Then the G1 got me so tempted I joined the dark side again and now I'm toally hooked.
Nicely proven that it is a UK issue.
I wonder if it will be enabled across the board at some point. The only reason I can think of that TM would disable it is bandwidth usage. How much traffic does Latitude generate?
Can't see it been very much just a tiny bit of text sent to google every so often. No idea why T-Mobile wouldn't want us to have it they might think its a privacy issue us Brits tend to make a fuss over things like that. I could see the daily mail now 'New Google Phone Allows Government Track Every Step You Take'
Very true...
You mean something like this.
http://www.dailymail.co.uk/sciencet...Google-lets-track-friends-family-mobiles.html
That's a point, its available for other mobile handsets?
Obviously TMUK being £$%$s again!
They even block internal access to google.com / latitude!
zabouth said:
You mean something like this.
http://www.dailymail.co.uk/sciencet...Google-lets-track-friends-family-mobiles.html
Click to expand...
Click to collapse
LOL WOW well that just proves the point
And the greatest thing is, we'll never know why its not included. TMUK will blame google, and google will blame TMUK. So easy for them to do.
We should hunt the person who decided not to include it down and slap them.
PeepoTurton said:
As for voice search that isn't in RC9 at all, I will have a mess to see if I can port it from ADP or RC33 at some point.
Click to expand...
Click to collapse
Having tried voice search on the iphone, you're not missing much.. it's tuned to an american accent and comes up with some hillariously bad interpretations of british accents.. it's *way* quicker to type than try to pronounce the same thing 50 times with a vague american drawl... (although strangely I believe it fares quite well with the welsh accent).
As an experiment I enabled latitude then reflashed my data.img from the nandroid backup, and latitude vanished again... so it's a setting on the maps app itself somewhere.
TonyHoyle said:
As an experiment I enabled latitude then reflashed my data.img from the nandroid backup, and latitude vanished again... so it's a setting on the maps app itself somewhere.
Click to expand...
Click to collapse
I have a feeling you will have to set up all your apps and stuff from scratch and then back that up with nandroid. Once maps has stored the fact you shouldn't have latitude in your user data it wont appear even if you have no sim in. So as soon as you flash your old user data back it will vanish again.
I have tried it with a backup made with nandroid after my latitude fix and that works fine.
The maps app itself is identical to that in RC33 and ADP1.1 as far as I can tell, I think T-Mobile have done something in the framework to check if its a UK sim and if it is it writes something to your user data that stops latitude from working. This is a guess however I'm sure someone much smarter then me will be able to figure out where it is and remove it.
What finally worked for me to preserve my settings:
Perform prodecure as above to enable latitude.
Flash data.img from backup. Reboot. Do not replace SIM. Do not enter maps yet.
Using adb, Add the following to /data/data/com.google.android.apps.maps/shared_prefs/com.google.android.maps.MapsActivity.xml
<boolean name="FF_SHOWN" value="true" />
<boolean name="SHOW_MY_FRIENDS" value="true" />
(the second line will already be there - just modify it to 'true')
Now enter maps. Hit 'menu' and the Join Lattitute button will be there. Join, and it'll stay when you replace the SIM.
I'm not sure that all of the above is needed, but that combination works consistently for me.
PeepoTurton said:
After the update before it restarts pull out your sim card, turn your phone on.
Click to expand...
Click to collapse
Hi and thanks for solving this bloody annoying problem that has bugged me since I received RC9.
I have no problem doing what you suggested so thanks for that and for supplying the ready made up file (Thanks to JF also) but the only concern I have is the section I have quoted above.
It's the restart bit, can you give a clearer indication when to switch the handset off and did you just battery pull? I'm guessing it's when they update is finished and the phone switches off and just before it restarts just remove the battery? I just want to seek a bit of clarification really
Hope that makes sense
PeepoTurton said:
I can assure you that Latitude is in the RC9 update (I was one of the people who it didn't show up for), when I was reading throught the millions of posts on the matter I noticed that all the people who claimed it was there are all on networks outside the UK.
Click to expand...
Click to collapse
I am on T-Mobile, but my SIM card was in another phone when the RC9 update arrived.
When the update was complete, I had Latitude, and was able to play with it using WiFi.
I shut down my G1 to insert my SIM card, but after rebooting, Latitude vanished, and I was back to old Maps. :-(
So very annoying.
RapidShare link is gone.
Anyone care to re-upload?
citizen71 said:
Hi and thanks for solving this bloody annoying problem that has bugged me since I received RC9.
I have no problem doing what you suggested so thanks for that and for supplying the ready made up file (Thanks to JF also) but the only concern I have is the section I have quoted above.
It's the restart bit, can you give a clearer indication when to switch the handset off and did you just battery pull? I'm guessing it's when they update is finished and the phone switches off and just before it restarts just remove the battery? I just want to seek a bit of clarification really
Hope that makes sense
Click to expand...
Click to collapse
Sorry about that I will change it on the main post soon. I just did a battery pull. However you can take take the sim out before you even do the update then you dont have to worry about it. Just update and then home and back to reboot
***Over the last 2 months, I have been through more issues with T-Mobile then just the issues from the software side. I have spent the majority of that time working with them to try and fix a data connectivity issue I was having. After hard resets, ROM update, and then a site survey, T-Mobile found that the area where I live does NOT have adequate enough coverage to competently supply data coverage to my phone. Notes from the tech said that towers were noted as needed but NO BUDGET was available to deploy a new tower in the area. Because of this, the account rep I spoke to immediately offered a full refund on my unsubsidized HD2 and a refund for all services rendered to-date, including accessories for the phone. As of last night, I left T-Mobile and joined AT&T with a 32gb iPhone in preperation for the upcoming 4G. I'll either trade it in if within 30 days, or give 3GS to wife and get a 4HD on a second line. I have been a Windows Mobile user for YEARS. I still love the HD2 and would never have gotten rid of it, except for the fact I know that AT&T's Edge bands are going away to make room for 3G, and I don't want issues of trying to run HD2 on AT&T's network. I want to stress how much I LOVED the HD2. To me, the phone had a lot of improvement needed, but for what MS and HTC had to work with, it was the best Windows Mobile phone to-date, IMHO. That being said, I have lots of friends with the iPhone, our company exclusively carries it, so I also got a nice discount. I've used one from a distance several times, but never really had one that was mine to really dig into. So far, I am REALLY happy with the phone. I'll jailbreak it and start tweaking it, just like I have my Windows Mobile phones for years, but it's something new for me to play with. =) So, with that being said, I am going to retire from this thread and anybody is more then welcome to take it over. Nibbley15 might be able to do this. I'm still need to get him setup with some software issues he was having, but baby and family haven't left me with a lot of time. Nibbley15, I haven't forgot about you, I just haven't been home to get things configured yet. I'll be in touch soon.
Thanks! ZIMMAY!***
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
I have finished making a CAB. Use at your own risk. I played guine pig and did this myself with no ill effects.
Here are the reg keys that are changed:
Settings from HD2Tweak:
[HKEY_LOCAL_MACHINE\Drivers\TouchPanel]
"PressureThreshold"=dword:000162f2
This is the setting that seems to help the most with being able to click/touch items on screen, especially the corners:[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
Settings from HD2Tweak:
[HKEY_LOCAL_MACHINE\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
"SpeedHigh"=dword:00000000
"SpeedLow"=dword:0000000e
I am still curious what the other settings that Nibbley15 found and how they relate.
***Update 5/21: Added cab to enable Screen options in System Settings to do a screen calibration.
***UPdate 5/22: Reg entry for new CAB is as follows:
[HKEY_LOCAL_MACHINE\\ControlPanel\Pen]
"Hide"=dword:00000000
zim2323 said:
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
Below is what I found to work for me, better then anything I've tried so far. I will be the first to warn you that I have NO IDEA what I'm really doing in relation to TouchResponse, but I do have a good understanding of the registry. The values I've applied may really be nothing more then a happy thought in my head. Though I seem to be able to actually use the close/ok buttons in the upper right part of the screen.
I can make a CAB later, but these are the settings I adjusted my settings to.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
I'd like to see if others could test and post what your experience is. Even better, we may get some help from the chef's to confirm, deny, correct, extrapolate, etc, etc, to find a better fix.
***Edit: Forgot to mention. While the bottom 2 did help, the first FingerThreshold settings seemed to be what made the real difference for being able to competently hit buttons without feeling like I was jackhammering the phone. =)
Thanks!
Click to expand...
Click to collapse
I would have to say that there would be a way to adjust the touchscreen on 2.13 as 2.10 does not have those registries...Well I'll give it a try when I upgrade to 2.13.
Thanks
secano said:
I would have to say that there would be a way to adjust the touchscreen on 2.13 as 2.10 does not have those registries...Well I'll give it a try when I upgrade to 2.13.
Thanks
Click to expand...
Click to collapse
Thanks. Personally I'm running these exact reg and it's working a million times better. But like I said, could be in my head. The only other things I changed sensitivity wise is the scrolling affects that HD2Tweak has. I'll be adding those to whatever I CAB up for a complete fix. I used SKTracker to find out which reg entries changed.
Yes,
Thanks! Please keep the ideas flowing here. Thanks to all that are working this!
I'm posting this reply for folks that are using the 2.13 STOCK ROM and you may want to know the original settings to revert back too or other places to look for you REG peeps to look at.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031 STOCK SETTING
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
STOCK 2.13 version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
STOCK 2.13 version doesn't have this key
Did find these keys:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 20
"FingerThreshold"=dword:31 (0X00001F) <- NOTE:
"NoiseThreshold" = dword: 20
NOTE: if you change the key[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel] to "FingerThreshold"=dword:0
then this value will change to 20, hmmmm.
Other notes: I think that BaseThreshold is where it starts?
I think that the Fingerthreshold here is where it all starts from after learning?
I think that the NoiseThreshold is the amount of "noise" from your fingertouch is allowed before it recognizes before it knows your finger is really touching the screen?
2nd half of post: I'm posting this for folks that may want to know what was in the 2.10.1 STOCK ROM:
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
STOCK 2.10.1 version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
STOCK 2.10.1 version doesn't have this key
Did find these keys:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 0
"FingerThreshold"=dword: 20 (0X000014) <- NOTE: now this is interresting
"NoiseThreshold" = dword: 20
This is what I recommend folks to change their 2.13 Builds to match the 2.10.1 Build for Touch Response.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 0
"FingerThreshold"=dword: 20 (0X000014) <- NOTE: this may change automatically on you from the above change (Setting\TouchPanel)
"NoiseThreshold" = dword: 20
i'm a newbie!!!!
can anyone tell me how cani get to those registry or what kind of program that i need to see the registry? do i need to connect with the computer to see it and change it?
ipsaa said:
i'm a newbie!!!!
can anyone tell me how cani get to those registry or what kind of program that i need to see the registry? do i need to connect with the computer to see it and change it?
Click to expand...
Click to collapse
Hello,
I will try to put this simply, please do not mess with your registry unless you know what you are doing it can crash your phone. When we finally find the fix for this, a cab file will follow shortly. The cab file will do the work for you and you don't have to worry about killing your phone.
If you really really really want to try then please search the threads and there you will find your answers.
Please refer to post #5
zim2323 said:
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
Below is what I found to work for me, better then anything I've tried so far. I will be the first to warn you that I have NO IDEA what I'm really doing in relation to TouchResponse, but I do have a good understanding of the registry. The values I've applied may really be nothing more then a happy thought in my head. Though I seem to be able to actually use the close/ok buttons in the upper right part of the screen.
I can make a CAB later, but these are the settings I adjusted my settings to.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
I'd like to see if others could test and post what your experience is. Even better, we may get some help from the chef's to confirm, deny, correct, extrapolate, etc, etc, to find a better fix.
***Edit: Forgot to mention. While the bottom 2 did help, the first FingerThreshold settings seemed to be what made the real difference for being able to competently hit buttons without feeling like I was jackhammering the phone. =)
Thanks!
Click to expand...
Click to collapse
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
mmeyer4663 said:
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
Click to expand...
Click to collapse
I just tweaked the ones that I posted (to a 21903 2.13 BASE build);
I did not add those other 2 registry keys and it is a great improvement;
still testing myself.
Nibbley15 said:
I just tweaked the ones that I posted (to a 21903 2.13 BASE build);
I did not add those other 2 registry keys and it is a great improvement;
still testing myself.
Click to expand...
Click to collapse
Interesting. I do not see the last two entries in my reg.
I guess the difference is, the HTC version for TMO HD2 leaked last week is 21892.
Nibbley15 said:
I'm posting this reply for folks that may be using 6.5.X and not know the original settings to revert back too or other places to look for you REG peeps to look at.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
6.5.X version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
6.5.X version doesn't have this key
Did find this key:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\]
"FingerThreshold"=dword:31 (0X00001F)
[HKEY_LOCAL_MACHINE\\HARDWARE\SETTING\TOUCHPANEL]
"FingerThreshold"=dword:31 (0X00001F)
some others worth looking at possibly:
[HKEY_LOCAL_MACHINE\\SOFTWARE\HTC\TouchGL]
"DBCLKFingerDistance"=dword:45
"DBCLKFingerInterval"=dword:350
Click to expand...
Click to collapse
THANK YOU for posting this info. I hadn't got back to do that yet.
mmeyer4663 said:
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
Click to expand...
Click to collapse
Both of those keys/values were there. Although the one thing I had already installed and run was BSBTweaks and HD2Tweaks. Either of those 2 could have created the values. They seem to actually work, but that's kinda why I was posting, to see what others experience was with it.
mmeyer4663 said:
Interesting. I do not see the last two entries in my reg.
I guess the difference is, the HTC version for TMO HD2 leaked last week is 21892.
Click to expand...
Click to collapse
Just to clarify,
I am using a completely stock build of the new TMobile ROM. Based on the information I've read and that has been posted here, it looks like older ROMs may, or may not have those reg keys/settings implemented depending on the ROM timeline.
For those that have had a chance to try these settings, does it seem to improve things?
The numbers I used were just numbers I kept increasing. I have no idea what the max value is or could be.
I'm hoping tomorrow I'll have a chance to post the reset of the reg tweaks I used from HD2Tweaks that would be apart of the entire TouchResponse "package" that I've been working with.
Also, just in case someone wonders, don't ask for permission, TAKE PERMISSION to use this information however you want. You can say you figured it out and incorporate it into "My Awesome ROM". I really don't care. It's about getting things fixed we don't like, and making them better. I could care less who gets credit. I know for a fact that there are chef's and others out there that know a bazillion times more about this stuff then me. I just like know that I helped, if in fact it really does help.
Peace out!
I only had the first value in my registry:
"[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031"
But I did make the change and it absolutely made a huge difference, for the better.
Thank you for this. I just made the first tweak and things are 100% better. That eliminated my one big gripe about the new stock ROM.
xanderdad said:
I only had the first value in my registry:
"[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031"
But I did make the change and it absolutely made a huge difference, for the better.
Click to expand...
Click to collapse
So maybe that alone is the fix. I included the other keys because they were apart of the HTC Sense settings in HD2Tweak. Those keys may be more for scrolling issues.
Please put out a cab file for this mod. The lack of responsiveness is killing many here. Thanks.
NickPP said:
Please put out a cab file for this mod. The lack of responsiveness is killing many here. Thanks.
Click to expand...
Click to collapse
Well, before I did that I wanted to know exactly what was "fixing" the problem and what exactly those settings were doing or how it may interact or affect other functions of the phone. So far I have had nothin but positive response to this.
I have a little more testing to do and then I will putting out a CAB with all the fixes I apply that are related to making TouchResponse behave like I would expect it to. Expect something in the next 24 hours. In the mean time, you can always use a registry editor and apply the reg values yourself.
I'm dealing with job and a new baby so my time is short. =)
hi all i just got my htc hd 7 i want to know what benefits unlocking will bring to me + i read about touch explor and windows decive manager from where and how to download these?
thanks in advance
I think Unlocking is not important in my opinion because the available app outside Marketplace are not good app, as you register your credit card in Zune, you can buy very nice app and games better than those outside marketplace.
A very important reason to stay locked is to have the latest radio and firmware versions, but unlocking makes you with old ones.
verynuclear said:
I think Unlocking is not important in my opinion because the available app outside Marketplace are not good app, as you register your credit card in Zune, you can buy very nice app and games better than those outside marketplace.
A very important reason to stay locked is to have the latest radio and firmware versions, but unlocking makes you with old ones.
Click to expand...
Click to collapse
that's a bold statement. firmware or radio versions have nothing to do with UnlockState.
if you want to configure your phone beyond what's possible natively, there are a few apps that can be sideloaded that allow you to do what the NoDo OS for example cannot do, only two here. a) changing accent colors, b) adding your own ringtones.
Schaps has his own website with a forum and download section. If you google it you won't need much time to find it.
Hello,
wholly, the fact of unlock the WP7 allows to put some programs such as accent etc her personify sound wp7
derausgewanderte said:
that's a bold statement. firmware or radio versions have nothing to do with UnlockState.
if you want to configure your phone beyond what's possible natively, there are a few apps that can be sideloaded that allow you to do what the NoDo OS for example cannot do, only two here. a) changing accent colors, b) adding your own ringtones.
Schaps has his own website with a forum and download section. If you google it you won't need much time to find it.
Click to expand...
Click to collapse
As a Mozart user, I can not unlock the device with the latest Radio and Firmware, So I miss the camera update and loading speen which are important additions to me
Adding ringtones are not important because the internal ones are very nice.
Also changing the color and editing the device system may cause my system to be unstable.
Just an opinion.
Sorry for my English.
Actually it's up to the individual,some might stick to lock phone some might not.The best for those who unlock is that they can explore what their phone can do just like win mobile 5 to 6. and they can do the same as lock phone ie: update etc. so on and so forth.
Just my 2 cents.
Just wondering if anyone ran into this issue. I've been playing bug village for a little while now, Avoiding paying for coins, I would set a few tasks a day for the bugs and check back to make sure they are fed.
For a few days in the game, I started getting black screens but, it came back and worked. Yesterday, it just stop totaly working, it loads to a black screen then exits. I can not enter the game any more and I am afraid of losing my place at level 15.
Does anyone know a fix for this or a way I can really backup this game, so I can uninstall it and not lose my place ???
Thanks for any advice !!!
There was an update releases yesterday. Did you update?
Sent from my TITAN X310e using Board Express
Yea try updating it, either by waiting for the notification or by going to the game and hit update.
drupad2drupad said:
There was an update releases yesterday. Did you update?
Sent from my TITAN X310e using Board Express
Click to expand...
Click to collapse
Yea, I ran the update and still the same problem
My Ants have not eaten in days, someone help !
Why did this happen ? Others have claimed this issue but, no result.
Does anyone know a fool proof way to backup/restore my save data so I can attempt to uninstall/reinstall ?
Depends on your phone model and firmware version. For Samsung or certain older HTC firmware, it's possible to back up the data.
GoodDayToDie said:
Depends on your phone model and firmware version. For Samsung or certain older HTC firmware, it's possible to back up the data.
Click to expand...
Click to collapse
Verizon HTC Trophy running 8107 (newest build)....Does that mean no ?
I said firmware, not OS build, but probably.
Are you able to interop-unlock your phone?
GoodDayToDie said:
I said firmware, not OS build, but probably.
Are you able to interop-unlock your phone?
Click to expand...
Click to collapse
Yes, my phone is interop-unlocked. I am not fully unlocked due to having a CDMA based phone (no one really lets us play) and no one supports a full unlock on my phone
There are two apps you can try: TouchXplorer (on http://touchxperience.com) and HtcRoot Webserver (see my sig). Both can access the filesystem of HTC phones and let you move or back up files (backup is a little tricky with TouchXplorer but it can be done). You can also try using DiagProvXML if you know the path to the data you want to move/copy/whatever (it'll be under \Applications\Data\<GUID_OF_APP>\Data\IsolatedStore)
These apps use a variety of different hacks to access or modify the filesystem (provxml is currently write-only). Without knowing your firmware version, I can't tell you which ones will or will not work. Give it a shot, though...
GoodDayToDie said:
There are two apps you can try: TouchXplorer (on http://touchxperience.com) and HtcRoot Webserver (see my sig). Both can access the filesystem of HTC phones and let you move or back up files (backup is a little tricky with TouchXplorer but it can be done). You can also try using DiagProvXML if you know the path to the data you want to move/copy/whatever (it'll be under \Applications\Data\<GUID_OF_APP>\Data\IsolatedStore)
These apps use a variety of different hacks to access or modify the filesystem (provxml is currently write-only). Without knowing your firmware version, I can't tell you which ones will or will not work. Give it a shot, though...
Click to expand...
Click to collapse
Thanks for your help. TouchXplorer stopped working after Mango, it stopped working on Interop unlocked but, still works on Fully unlocked devices, as far as I know. I have it installed, it loads but, does not do anything beyond that, the Dev closed the discussion due to it not working any more.
I looked over your Webserver, I'm not a programmer so it's out of my skilset to make it into a installable file.
and sad to say, with 8107 firmware Connection Setup no longer works (error "Carrier not in Database"), so proXML is out too...
I am running stock Firmware, 2305.13.20110.605
Any other thoughts ?
Um, there's pre-compiled XAPs of the webserver attached to the thread...?
Mind you, if TouchXplorer isn't working for you, then HtcRoot won't either.
GoodDayToDie said:
Um, there's pre-compiled XAPs of the webserver attached to the thread...?
Mind you, if TouchXplorer isn't working for you, then HtcRoot won't either.
Click to expand...
Click to collapse
I wish there was a way to get TouchXplorer working, but, I didnt notice any pre-compiled ones in the thread, I'll try that.
Any other way ?
Look on the webserver thread, not the HtcRoot thread (there's a precompiled XAP on there too, but it's just a test app; doesn't *do* anything except check compatibility).
I've pretty much outlined all the viable options for you already. If none of them work, then... hope there's a fix released soon, or a better backup option? I don't know, I've never played the game, it sounds awfully Farmville-esque, so maybe waiting that long isn't an option...
GoodDayToDie said:
Look on the webserver thread, not the HtcRoot thread (there's a precompiled XAP on there too, but it's just a test app; doesn't *do* anything except check compatibility).
I've pretty much outlined all the viable options for you already. If none of them work, then... hope there's a fix released soon, or a better backup option? I don't know, I've never played the game, it sounds awfully Farmville-esque, so maybe waiting that long isn't an option...
Click to expand...
Click to collapse
I tried your webserver.... but, browsing the device just gives me a "System.Runtime.InteropServices.COMException (0x8007001F): A device attached to the system is not functioning. "
I saw a post by you saying it's not compatable (someone else had the same error)..
That is pretty cool tho (a web server on my phone, very cool)... I wish I could get my HTC Trophy fully unlocked so I can play with these cool tools....
The game was fun, kind of like you said, Farmville-esque, but, instead of spending real cash, you can just time go by, it was fun and I would play it one or 2 times a day to get my ants working and build up acorns (money in the game). After playing it 2 weeks, every day, 2-3 times a day, it died before I could get all the achivements. I just wanted to finsih the game..
I want to thank you for trying to help, I know there is only so much that is possable with my phone now but, thanks for trying
Even I have d same problem on my HTC radar and d black screen blocks d vision but d icons R visible & if I drop some food then the house did is visible otherwise only small areas are visible what to do
This happened to my Titan once, a reboot fixed it.
Phil_123 said:
This happened to my Titan once, a reboot fixed it.
Click to expand...
Click to collapse
I have rebooted, Pulled the battery and everything else I could think of, It still does not work.
@DavidinCT: Off-topic, but there's a version of the WebServer (which my project was actually built on) that does not use HtcRoot or even interop-unlock. Aside from its own data folder though, the only place it can access is read-only for \Windows.
GoodDayToDie said:
@DavidinCT: Off-topic, but there's a version of the WebServer (which my project was actually built on) that does not use HtcRoot or even interop-unlock. Aside from its own data folder though, the only place it can access is read-only for \Windows.
Click to expand...
Click to collapse
Interesting, I'll have to check it for the coolness factor. It does not help on my quest tho
On the subject of Bug Village, I am not the only one with this issue, if you look over the reviews in the marketplace, there is ton more with the same issue. I guess I can hold tight for an update, I guess...
Yeah, if it's a common issue, there are good odds the developer will fix it. If they don't, they won't get any more money from it...
Hello,
In all my excitement over Tango, I neglected to read any of the warnings posted around the forums/web. I installed Tango via the cab sender method (neglected to make a backup) and everything still worked, or at least the homebrew apps I launched still did. Searching the forums, I found the Samsung firmware somewhere in the replies to the cab thread, and pushed it also. This was late at night and it wasn't until the next day I noticed I can't launch almost half of my homebrew apps. It's said restoring from a backup (don't have one) or flashing back to Mango is the only way to fix this. Is that true? Well ****. Because there is no ROMs (stock nor custom) for the Focus S..
What should I do?
Thanks in advance,
6-4.
64GUNSHIP said:
Hello,
In all my excitement over Tango, I neglected to read any of the warnings posted around the forums/web. I installed Tango via the cab sender method (neglected to make a backup) and everything still worked, or at least the homebrew apps I launched still did. Searching the forums, I found the Samsung firmware somewhere in the replies to the cab thread, and pushed it also. This was late at night and it wasn't until the next day I noticed I can't launch almost half of my homebrew apps. It's said restoring from a backup (don't have one) or flashing back to Mango is the only way to fix this. Is that true? Well ****. Because there is no ROMs (stock nor custom) for the Focus S..
What should I do?
Thanks in advance,
6-4.
Click to expand...
Click to collapse
Yeah... I want to say you're unfortunately screwed :-\.
To make matters worse, the Wireless manager no longer appears to work for configuring MMS when carrier unlocked. I guess I'll just go back my Quantum's for hacking and hard reset this device ..ill wait a while though.
Sent from my SGH-i937 using XDA Windows Phone 7 App
Do you have *any* homebrew apps that
A) you can still run
B) you marked as Trusted in WP7 Root Tools?
It sounds like what happened is that your phone reverted from interop-unlock to simple dev-unlock (you presumably have an AppHub account?). However, this does *not* revert root-unlock as applied by WP7 Root Tools. Root Tools itself requires ID_CAP_INTEROPSERIVCES, and as such can't be run without interop-unlock. However, the apps that it has marked as Trusted will continue to run with full permissions (root unlock).
So, here's what you do.
First, identify an app that you can run (i.e. that isn't interop) and that is marked as Trusted.
Second, take the GUID of that app, and use that GUID to replace the ProductId of the Tango-update-workaround app (which essentially just restores interop-unlock).
Third, remove homebrew apps from your phone (but not the target app, the trusted one you can still run) until you are able to deploy an app (usually, this means reduce to 9 homebrew apps).
Fourth, use a XAP deployer that supports updating, and do an update-install of the workaround app (upgrade, because it's using the GUID of the already-installed target).
Fifth, run the workaround app, and then re-install your normal apps.
I did as you instructed, however I still have the 10 sideload limit and am unable to deploy any interop services.By tango workaround app, you meant relockprevent, correct?
Is there something I may have missed?
Like I said, I installed the Samsung LE2 update for the Focus S which is basically the KK2 equivalent, so provxml will no longer work.
Also, I do not have an apphub account.
Bump. Anyone have any ideas? A friend put a support ticket in with Samsung internal support to see if they can get the ROM.
64GUNSHIP said:
Bump. Anyone have any ideas? A friend put a support ticket in with Samsung internal support to see if they can get the ROM.
Click to expand...
Click to collapse
Oh so it was that firmware update that just broke interop. Yeah I want to say at this point you are stuck. I doubt that Samsung will give the ROM since it isn't an issue that is preventing you from doing out of the box functionality.
Sent from my SGH-i917 using XDA Windows Phone 7 App
snickler said:
Oh so it was that firmware update that just broke interop. Yeah I want to say at this point you are stuck. I doubt that Samsung will give the ROM since it isn't an issue that is preventing you from doing out of the box functionality.
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
isnt the provxml method using diagnostic tools the reason for this no longer working, what i mean by that is if you were to install the older version of the diag tool would that not restore functionality, or has the lock down of that gone much deeper? if you are able to install XAPs then find an older OEM update version pre KK2/LE2, open it up and rip out the diagnostic tool XAP, remove any previous installed version then send over the XAP....
just a thought, it might not work, but essentially i think thats what happens unless of course there are other dlls or drivers that the tool needs that have also been updated....
course it would be great to find someone willing and able to help crack the bootloader
dazza9075 said:
isnt the provxml method using diagnostic tools the reason for this no longer working, what i mean by that is if you were to install the older version of the diag tool would that not restore functionality, or has the lock down of that gone much deeper? if you are able to install XAPs then find an older OEM update version pre KK2/LE2, open it up and rip out the diagnostic tool XAP, remove any previous installed version then send over the XAP....
just a thought, it might not work, but essentially i think thats what happens unless of course there are other dlls or drivers that the tool needs that have also been updated....
course it would be great to find someone willing and able to help crack the bootloader
Click to expand...
Click to collapse
Yeah I gave the suggestion to him in the Cab Sender thread to try and look on here for the Diag v 0109 or even 0210. That's the version that I have. Actually in the Cab Sender thread, I posted the cab file to the samsung firmware for Mango that should have that diagnostics version in the cab. You may be able to push that to your device
The old version was still installed after updating, it didn't work.
64GUNSHIP said:
The old version was still installed after updating, it didn't work.
Click to expand...
Click to collapse
Ok, that means that the firmware also pushed out new Dlls to prevent proxvml. You are stuck unfortunately :-\
Ive been asking around and doing some research and as of today your stuck, sorry!
I did some poking around on DFTs website as well and there is absolutely ZERO work being done on it, mostly because it seems like the focus S is an AT&T only phone, there just isnt a pressing needed to do anything, plus most folk dont have a focus S to work with.
i dont know what it would take to get some help or even guidance on getting the bootloader replaced but at the moment, until another method is found, thats all there is.
Tho This might be interesting to look in to but DONT DO IT!
did i read somewhere else you dont have a preupdated backup or was it that the backup didnt work?
snickler said:
Ok, that means that the firmware also pushed out new Dlls to prevent proxvml. You are stuck unfortunately :-\
Click to expand...
Click to collapse
There is a lot of changes in those updates, if we could insert our own certificate to allow us to build our own signed cabs we could probably work it out, but alas we can only add a cert in to a custom ROM then flash it...
Yes, unfortunately I bought the phone from a guy here on XDA in May, never had to update it (had been cab updated to 8107 before I got it), never made a backup before installing tango (it's a small update, what could it possibly **** up, right?) Anyway the Focus S was announced yesterday as being available online at some Australian website so maybe there will be ROMs available in the future. I still haven't heard back from internal Samsung support, but have also asked the user I purchased the phone from if he has any backups, which I would restore from and immediately reset again to ensure his privacy.
Honestly, I wouldn't mind losing interop-unlock until 7.8 comes around, or WP8 (whichever I can afford first), but MMS also can't be configured using the Wireless Manager anymore, and that's an absolutely vital feature for me. Although, the WM has been known to not work for a lot of people, even pre-tango, but it worked flawlessly OOB for me prior to updating.
64GUNSHIP said:
Yes, unfortunately I bought the phone from a guy here on XDA in May, never had to update it (had been cab updated to 8107 before I got it), never made a backup before installing tango (it's a small update, what could it possibly **** up, right?) Anyway the Focus S was announced yesterday as being available online at some Australian website so maybe there will be ROMs available in the future. I still haven't heard back from internal Samsung support, but have also asked the user I purchased the phone from if he has any backups, which I would restore from and immediately reset again to ensure his privacy.
Honestly, I wouldn't mind losing interop-unlock until 7.8 comes around, or WP8 (whichever I can afford first), but MMS also can't be configured using the Wireless Manager anymore, and that's an absolutely vital feature for me. Although, the WM has been known to not work for a lot of people, even pre-tango, but it worked flawlessly OOB for me prior to updating.
Click to expand...
Click to collapse
so you updated to the LE2 samsung update, was that via zune? (the last update it does in a row 3rd or 4th perhaps!) or did you cab send that as well?
if you went via zune then it does a backup as well, settings>update>restore
It was all done through the cab sender. There is no backup.
Just wanted to mention here... you know that CAB Sender is perfectly capable of making backups, right? It's one of the core operations the tool is capable of. Don't blame CAB Sender for you pressing S instead of B.
I just don't want people getting the impression that "through the cab sender" implies "there is no backup."
Fully aware, thank you.
?
Hello guys!
Got my device on the 8773 and did the samsung update...
Is there anyway to get my interop back ?
I have my backups (one the last 8773 without samsung update and the other is 7740 without anything =] )
Thanks a lot.
Restore your backup, do a little bit more reading on the subject of Tango with Interop Unlock, install the prevention app and mark it as trusted, and have at it. (Specifically, Tango will reset the "prevent relock" registry values, so you have to avoid the phone connecting to Microsoft until you have cleared them again).