Develop Bugs

New Hotfixes

Just FYI, HTC released a couple of hotfixes for the Tilt 2 and the Pure
http://www.htc.com/us/support/tilt-2-att/downloads/

denco7 said:
Just FYI, HTC released a couple of hotfixes for the Tilt 2 and the Pure
http://www.htc.com/us/support/tilt-2-att/downloads/
Click to expand...
Click to collapse
Sweet, thanks for the heads-up!

oh excellent! they fixed my two issues i have with it.

Sorry for this n00b-ish question, but...
I just see the 3 PDF files from the 2nd of Oct, '09. What am I doing wrong?
Thanks!
~Eric

eknutson said:
Sorry for this n00b-ish question, but...
I just see the 3 PDF files from the 2nd of Oct, '09. What am I doing wrong?
Thanks!
~Eric
Click to expand...
Click to collapse
I had the same problem 'til I flushed my browser cache and tried again. refreshing the page didn't do it for me, I had to delete my browsing history and then click the link again.
HTH
Mike

Bingo! Thanks =)

This is NOT a ROM update and you will not lose your data. Also, these files will survive a Hard Reset so they need only to be installed once.
Click to expand...
Click to collapse
i wonder what it changes to survive the hard reset.

The Jack of Clubs said:
i wonder what it changes to survive the hard reset.
Click to expand...
Click to collapse
It actually runs kind of like a ROM update. It resets the phone then installs the hotfixes before at the AT&T World Phone splash screen with the ROM and Radio info before WM loads. Interestingly the Radio says "None" on that screen when the update program is running.

does the SMS fix helps improving the sense 2.5 SMS client running on the Tilt2?

if you flash a new rom you need to do the fixes again right? any cabs yet?

Hmmm, I wonder if this is utilizing the vastly underused Windows Mobile Image Update system. It sure sounds like it, but I can't test since I'm not on a stock ROM.
EDIT: It seems it is using Image Update! I extracted the installer and found two .cab.pku files. According to Da_G, this is what they do:
Update contains a binary delta between a package already on the device, and the updated version of that package. In this manner the limited space is conserved (i.e. if a package change was a simple registry entry - no need to replace the 5mb of .dll and .exe in that package, just alter the .rgu with the new data. These packages are also referred to as "Delta" packages. The concept is similar to the unix implementation of Diff/Patch. The file extension is .cab.pku
Click to expand...
Click to collapse
EDIT2: I've extracted both .cab.pku files, and one gave me a single .dsm, while the other gave me a .dsm, a DLL relating to EZinput, and a .rgu file containing registry entries. Not very useful information, but still nice to see that AT&T is taking the initiative to use this underused Windows Mobile feature.

Question is how to get these updates installed onto a ROM other than the stock one. It seems to do some type of validation before installation, and refuses to install on a ROM other than the stock one.
I suppose chefs will have to cook these fixes in, or someone will need to create a CAB or learn how to mess with the Image Update fixes?

Just as a caution, don't try to apply these updates to a reconstructed ATT Tilt2 ROM (in case you flashed to cooked ROMS and then went back to one that is supposed to be like retail).
The HTC hotfix installation starts as the verification passes, but then at least on my device, it was stuck in a reboot loop. I had to flash to another cooked ROM and then flash back.

It would be interesting if we can find a way to update TouchFlo to the latest release using this method. That way you can update touchFlo while keeping AT&T's stock rom and not have to flash a new one.

jh20001 said:
It would be interesting if we can find a way to update TouchFlo to the latest release using this method. That way you can update touchFlo while keeping AT&T's stock rom and not have to flash a new one.
Click to expand...
Click to collapse
Unfortunately, it's extremely unlikely that will happen with AT&T's stock ROM. Image Updates are signed, and are checked against certs that are cooked into the ROM. This ensures that only the OEM or carrier can release these updates (kinda like how ROMs are signed so only the OEM or carrier can release updates). The Image Updates will refuse to install if the certificates can't verify the update, and there's no way we're going to get AT&T's security certificates. So unless someone gets those, you're out of luck.

I installed the 2 fixes that where on the htc website but now when i go to the start menu i only get a 3 row menu, how do i change it back to a 4 row menu

Okay here's a problem, I installed the SMS fix that was on HTC's website, that went without a hitch, but when I tried to install the inconsistent Caller ID hotfix, it said it was incompatible with my device. I have the stock ATT rom. Anyone else have this issue?

Yep same here...stock AT&T ROM and getting the same error when I try to install the Caller ID HotFix....hopefully they fix it because I have this happen a lot with the CallerID not showing up on my device.

AngelDeath said:
Okay here's a problem, I installed the SMS fix that was on HTC's website, that went without a hitch, but when I tried to install the inconsistent Caller ID hotfix, it said it was incompatible with my device. I have the stock ATT rom. Anyone else have this issue?
Click to expand...
Click to collapse
kizzle07 said:
Yep same here...stock AT&T ROM and getting the same error when I try to install the Caller ID HotFix....hopefully they fix it because I have this happen a lot with the CallerID not showing up on my device.
Click to expand...
Click to collapse
How old are your devices? This fix might be for older devices. I had my original Tilt 2 replaced due to a faulty ROM or radio chip which would boot loop my device before the red version numbers would show on the AT&T logo boot screen. The version numbers on the new Tilt 2 seem to be updated. I would guess if I were to run the updates, I would be in the same boat...

mines less than a month old and the updates ran (att tilt 2)

Issues on CM7 1.0-RC1.5-jordan-signed

First of all, I would like to thank everyone involved in making our Defy's so awesome.
Thanks to you all, as after getting all the info and help, I was successfully able to
upgraded to CM7 1.0-RC1.5-jordan-signed, and after few initial hiccups everything is working fine. Except the battery drainage issue. And I have been loving the new look and feel of my Defy ever since.
Today Morning. I've started getting a new problem. Whenever I want to call someone and I go to contacts, it force closes itself with following error:-
"The Process android.process.acore has stopped unexpectedly. Please try again."
I have restarted the phone and no respite from the problem.
Help please....

Did you change something or install a new app immediately before this started to happen ? Did you restart your phone while it was still connected to the PC or so? Some other people solved this problem by doing a factory reset. But you need to find the specific reason or cause in your case and correct that.

tdlr said:
Did you change something or install a new app immediately before this started to happen ? Did you restart your phone while it was still connected to the PC or so? Some other people solved this problem by doing a factory reset. But you need to find the specific reason or cause in your case and correct that.
Click to expand...
Click to collapse
Well, the last thing I did last night was that I installed two ADW themes. and also downloaded few wallpapers.
Do you think, the themes could have created this problem?

mandhir.s.bajwa said:
Do you think, the themes could have created this problem?
Click to expand...
Click to collapse
As there is, according to my information, no standard cause for this problem, everything could be the reason. Other people reported this error on different devices too and the reasons were diverse.
Some have had the problem after installing a new app, others due to rebooting the phone while it was still connected to the pc. Others made a factory reset and then it worked again and the true reason was never found.
It won't kill you to try and disable/uninstall the new themes or wallpapers (if they are live wallpapers).
Maybe there is another specific well known reason for that out there. In this case I simply don't know one.
If you're lucky, others had the same problem and have identified a more precise cause. Then they will answer hopefully.
I would try to undo the last things you changed before and find out the true cause.

tdlr said:
As there is, according to my information, no standard cause for this problem, everything could be the reason. Other people reported this error on different devices too and the reasons were diverse.
Some have had the problem after installing a new app, others due to rebooting the phone while it was still connected to the pc. Others made a factory reset and then it worked again and the true reason was never found.
It won't kill you to try and disable/uninstall the new themes or wallpapers (if they are live wallpapers).
Maybe there is another specific well known reason for that out there. In this case I simply don't know one.
If you're lucky, others had the same problem and have identified a more precise cause. Then they will answer hopefully.
I would try to undo the last things you changed before and find out the true cause.
Click to expand...
Click to collapse
Thanks for the suggestions.
Will uninstall the new themes.
And as you said, Factory reset. If I do that, what exactly will happen.
Asking this because as mentioned before, I'm no longer on the version which came with phone and I am on CM7. so Factory reset will take me to which phase?

mandhir.s.bajwa said:
And as you said, Factory reset. If I do that, what exactly will happen.
Click to expand...
Click to collapse
Have a look here: https://motorola-global-en-uk.custh...00/~/defy---master-reset-/-factory-data-reset
You may also try fixing permissions before with Rom manager.

tdlr said:
Have a look here: https://motorola-global-en-uk.custh...00/~/defy---master-reset-/-factory-data-reset
You may also try fixing permissions before with Rom manager.
Click to expand...
Click to collapse
well the link tells me what will happen on a stock rom. My question is. If I factory reset on CM7, will it take me to the original state or the default settings of CM7.

Flash cm7 again! maybe it helps.

guys,do i need cyanogen 7.1 installed on my device to install cyanogen 7.5?

Make a backup and try wiping via CWM. Both data and cache partition.
Sent from my ME525+ using Tapatalk

yashank said:
guys,do i need cyanogen 7.1 installed on my device to install cyanogen 7.5?
Click to expand...
Click to collapse
You can flash any CM7 directly via recovery menu if yer on Froyo.
Sent from my ME525+ using Tapatalk

Recenty started getting few more issues.
1.> Phonebook crashing because of FC's. I'm hardly able to use my phonebook now
2.> Last night, messages stopped working. Again FC's.
3.> Today morning the native camera application stopped working.
And I have done following to overcome all the issues with no luck:-
wipes all cache including devik.
Did factory reset
reflashed with CM7 jordon 1.5
All failed to give me any respite from the errors.
Now I have downloaded cm7-110923-0710-Nightly.
Do let me know if this is an OK one. I've faced way too many errors and afraid of showing it off to anyone now as It might crash anytime.

Much to my disappointment, even flashing to newer nightly, I'm still getting the same errors.
Can someone provide me the 3.4.3-36-1.7 SBF? the one in the link provided earlier is not working.
Or any other solution.
The errors are way too much to ignore, and if this continues then I have to go back to Froyo. But I seriously love the new feel of the phone. All thanks to CM7.

need assistance ---defy just rebooting and rebooting after 2ndinit install
need assistance ---defy just rebooting and rebooting
i installed the rom amanger premium
after that i installed the 2ndInit from market for android and installed the latest version .....and after that i uncheck the usb debugging and restarted the defy
since then its auto rebooting from logo to black screen and back to logo ....
please help me i am new to this and really pissed off .......

[Q] viper x reboots when receiving calls

all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?

Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue

Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )

A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...

webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January

Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...

What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.

Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!

Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue

Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW

Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing

webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH

webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!

[Q] Sprint LG G2 GPS issues with 4.4.2

I recently flashed to cyanogenmod 4.4.2 now my GPS is totally inaccurate. Anyone got any ideas what went wrong?

Himay85 said:
I recently flashed to cyanogenmod 4.4.2 now my GPS is totally inaccurate. Anyone got any ideas what went wrong?
Click to expand...
Click to collapse
I've had the same problem when flashing to cm11. The only way I could get it to work properly was to flash back to my stock backup and get a gps lock, then reflash cm11 again and try locking with gps. People recommend running an app called GPS status too, it shows the number of satellites available and the number of satellite connections.

roper15 said:
I've had the same problem when flashing to cm11. The only way I could get it to work properly was to flash back to my stock backup and get a gps lock, then reflash cm11 again and try locking with gps. People recommend running an app called GPS status too, it shows the number of satellites available and the number of satellite connections.
Click to expand...
Click to collapse
Thank you I'll give it try. I'll have to find the stock ROM for my phone. I didn't back it up like a newb

I have been reading that the GPS issues are hardware related and it can be due to the lack of contact on the connector which is causing this issue. Most people were able to fix it by opening up the phone and putting some electrical tape to make a nice contact on the connectors.

ericdabbs said:
I have been reading that the GPS issues are hardware related and it can be due to the lack of contact on the connector which is causing this issue. Most people were able to fix it by opening up the phone and putting some electrical tape to make a nice contact on the connectors.
Click to expand...
Click to collapse
I don't think it's primarily hardware related when most of us didn't have issues before 4.4.2.

I've tried numerous roms for the Sprint LG G2 that did not have GPS, but I think I've found a sort-of solution to it... I basically stole the gps ".so" files from the only rom that I know had working GPS... Paranoid Android. This was over a month ago however, and I've been reusing the same files over CM and Mahdi ever since, so I'm not sure if their updates could have broken GPS, but if that's the case I can share the files that I've been using with CM. Not sure how to make it into a flashable zip however, so they have to be replaced manually.

Hakukoru said:
I've tried numerous roms for the Sprint LG G2 that did not have GPS, but I think I've found a sort-of solution to it... I basically stole the gps ".so" files from the only rom that I know had working GPS... Paranoid Android. This was over a month ago however, and I've been reusing the same files over CM and Mahdi ever since, so I'm not sure if their updates could have broken GPS, but if that's the case I can share the files that I've been using with CM. Not sure how to make it into a flashable zip however, so they have to be replaced manually.
Click to expand...
Click to collapse
Can you share these files? Would they work on a stock based ROM?

ledvedder said:
Can you share these files? Would they work on a stock based ROM?
Click to expand...
Click to collapse
I don't mind sharing them, but not sure if they work on a stock based ROM as I haven't tried it. All the ROM's I've been testing have been AOSP-based... CM/PA/Mahdi/Omni/PAC/etc. I don't claim to know or understand how or why it works... but if it works for you too, great! If not, please don't blame me if it causes a brick or something.
Additionally, I don't know how to make this flashable... my method has been to extract the files, then reboot into Phil's CW Recovery and manually copy the files over with the Aroma File Manager. I included a GPS.conf file that I've modified to improve gps for my region, you may wish to exclude it.
[Edit] If this "does" work, be sure to thank the Paranoid Android team for whatever voodoo they did to make GPS work on their ROM.

Hakukoru said:
I don't mind sharing them, but not sure if they work on a stock based ROM as I haven't tried it. All the ROM's I've been testing have been AOSP-based... CM/PA/Mahdi/Omni/PAC/etc. I don't claim to know or understand how or why it works... but if it works for you too, great! If not, please don't blame me if it causes a brick or something.
Additionally, I don't know how to make this flashable... my method has been to extract the files, then reboot into Phil's CW Recovery and manually copy the files over with the Aroma File Manager. I included a GPS.conf file that I've modified to improve gps for my region, you may wish to exclude it.
[Edit] If this "does" work, be sure to thank the Paranoid Android team for whatever voodoo they did to make GPS work on their ROM.
Click to expand...
Click to collapse
Thanks, but it didn't work. Gave me a bootloop

Second hand htc one m8s cant update software.

Okay so I recently bought a HTC one m8s second hand and it works 100%.. only thing is. When I try to install the update it is aborted every time. Boot loader appears telling me that certain files were not recognized and stuff like that. Does anyone know what I can do to fix this?
Cheers guys

I have the same issue. From what I gathered on Google it is because of a modified system partition (I installed xposed which I believe causes this)
Only fix AFAIK is to fully revert to stop like the guide here shows. Problem is I tried it and it said the 0PKVMG.zip or whatever it is wasnt the correct one (when it was)

fraggz99 said:
I have the same issue. From what I gathered on Google it is because of a modified system partition (I installed xposed which I believe causes this)
Only fix AFAIK is to fully revert to stop like the guide here shows. Problem is I tried it and it said the 0PKVMG.zip or whatever it is wasnt the correct one (when it was)
Click to expand...
Click to collapse
I don't quite know what that means. But I will research it and give it a go. And tell you if it works

You can only flash an official ota if you are completely stock AFAIK.

Anybody have a link to a guide on how to do this?

Carrentempler1 said:
Anybody have a link to a guide on how to do this?
Click to expand...
Click to collapse
you can factory reset the phone an try