yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] squinonx:
Yes been using Quickpic eversince, i was wondering if we can improve the stock gallery we can conserve some space:beer::beer::)
[Wildfire Android Development] squinonx:
Anybody try tethering? Im having problem with this, the other phone can connects but was not able to browse successfuly..

Also noticed bluetooth file trasfer app is not working on this ROM

Any fix??
[Wildfire Android Development] GlennBrownie:
Hi everyone,

I've flashed this rom, and now my home button doesn't do anything? With vibration enabled I can feel a vibration but it doesn't actually do anything?
[Wildfire Android Development] enco93:
I had this rom, tried CM9 and flashed this rom again, and flashed the gapps i had on my sd ,the same as before. and now i think on play store, when i want to download something when im on data, it wont download, just some error, what can it be? what should i do?
[Wildfire Android Development] squinonx:
Switched back to 7.1 cause im having problem when calling, dial pad dont work well...
[Wildfire Android Development] ak0r:
I am getting "Error 492" when trying to download anything from Play Store. Anybody faced this issue?
[Wildfire Android Development] LucidSomnia:
Try wiping cache and dalvik and then reflash gapps.
[Wildfire Android Development] ak0r:
Tried almost evry option available. Flashed ROM again after full wipe. Same issue.
[Wildfire Android Development] Wasimk32:
go to settings>manage apps>google services framework>clear data.

again settings>manage apps>google play>clear data.

then reboot your phone.

wait for 15mins and then try downloading any app.
[Wildfire Android Development] Lesicnik1:
Some people posted that Error 492 has something to do with the servers.
[Wildfire Android Development] ak0r:
Didn't worked.

Trying with another rom. It should be same problem there as well.
[Wildfire Android Development] fabioff:
flashed my sisters wildfire a while ago, she was running 7.1.1 I think and then I decided to update to 7.2.0 but since then the phone is unuseable: random reboots, sometimes when surfing, writing a sms, making a call. the phone can even idle for 2 hours and then bang, random reboot. already tried a clean reinstall of 7.2 but it didn't help. what could this be? is there a way to check whats causing the random reboots? even reverting to the nandroid backup of the version which was working fine didn't help
[Wildfire Android Development] LucidSomnia:
Are you overclocking too much? It causes instability to the system, thus you have random reboots. I get random reboots at 768 mhz. Some people get them even at 729. If so, try 691 and check it out.
[Wildfire Android Development] ak0r:
Market works with other ROMs.
[Wildfire Android Development] fabioff:
Never overclocked the device
[Wildfire Android Development] djpry:
try flashing a fresh radio image...followed by a kernel flash .... instability is mainly caused due to these 2 things.....

cm7.2 is the 2nd best stable rom after official sense....never had a stuck up till date

---------

dj-pry
[Wildfire Android Development] fabioff:
thanks, which ones can you recommend? I live in germany if it matters for best performance/signal
[Wildfire Android Development] djpry:
on cm7.2

kernel - Sympfinity v4.1

governor-smartassv2

i/o scheduler-SIO

min-200+MHz

max-710MHz(more than this is really not required)

LINK-http://xdaforums.com/showthread.php?t=1588480

RADIO IMAGE- Radio_13.55.55.24H_3.35.20.10 (LATEST)

LINK-http://xdaforums.com/attachment.php?attachmentid=974647&d=1333181742

--------

DJ-PRY

press thanks if you found this post helpful
[Wildfire Android Development] fabioff:
flashed the kernel, already had the latest radio but no help... last reboot came when I enabled mobile data.. its just so weird that just after flashing a nightly the phone seems to be broken for good no matter what I do but that doesn't make sense :(
[Wildfire Android Development] djpry:
use cm 7.2 stable release...not night releases
[Wildfire Android Development] squinonx:
Anyone having problem using dialpad while calling? For me seemd zero is not working, its not recognized although you can press it..
[Wildfire Android Development] fabioff:
yeah, I've completely formated the phone, installed a RUU and 7.2 stable now - so far so good
[Wildfire Android Development] eventcom:
Reboots from enabling mobile data rings a bell...

From what I read your problem might not be related to the one I tried to solve last week. Due to the fact that I can't exactly tell what the reason was (same goes for the explicit part of the solution) it might be worth a try at least.

I've been suffering from reboots when turning on 3G data - not more - not random and just 3G everything else worked well. If you have some time you might read a part of the story here (starting from #10)

For the solution of my problem I can only make a few conclusions what might have been successful - some steps could have been unnecessary - no idea. What I think what might have done the trick is, downgrade radio by flashing an older one (Radio_13.53.55.24H_3.35.19.25) and upgrading again by flashing the newest (Radio_13.55.55.24H_3.35.20.10).

I've also installed a different recovery (due to unconfirmed reports that format/wipe wouldn't work correctly sometimes) plus I did always a complete wipe/factory reset.

It depends on you if you like to do all the steps - you can follow them in the thread linked above. For the files/versions I have used: CyanogenMod 7.2 Final(GWK74/2.3.7), recovery and radios all available here: The Complete Wildfire Index Good luck! :fingers-crossed:
[Wildfire Android Development] GlennBrownie:
*COUGH*

anyone had this problem, I doubt it can be just my single phone out of all Rooted Wildfire's ?
[Wildfire Android Development] eventcom:
nope I didn't have this problem - I used the stable for quite a while before I went on with LeWa (and I haven't heard of that problem anywhere else).

Have you done a fresh install or did you flash it over?

I always do it this way: format system / wipe cache / flash new ROM / flash gapps
[Wildfire Android Development] Munckster:
What I did when I had the reboot issue:

- Flash 2.5.x recovery;

- Flash the one before the most earlier radio (Radio_13.53.55.24H_3.35.19.25 - You can find all the resources here : http://xdaforums.com/showthread.php?t=1029318)

- Flashed a new CM 7.2 ROM (the Nandroid backup wasn't booting, so I did this)

- After first boot, reboot on recovery again, flash the latest radio

- With the new radio, flashed the ClockWorkMod v5.0.2.8 recovery,

- In my case, I had a previous update nandroid backup, so I restored it (as far as I use MTD partitions, I flashed the bravo boot thing).

For me, it worked out, remembering that worked for me, don't quite know if should work for you, So use this with care :). Hope it helps
[Wildfire Android Development] eventcom:
Almost similar to my problem - whole story in this thread (starting @ post #10)
[Wildfire Android Development] ilDuceo:
i have one problem with mic. when i call someone that person hear me like i speak from the barrel. any suggestions how to fix that?
[Wildfire Android Development] saadislam:
There is hole in the back cover for mic. Try cleaning it. I used a needle to clean the dust blocking it.
[Wildfire Android Development] ilDuceo:
its not that. this happend after flashing stable 7.2.
[Wildfire Android Development] saadislam:
I dont know but flashing cm 7.2 stable would not do that. I had this problem thats why I replied with what I think is the solution as it was in my case.
[Wildfire Android Development] eventcom:
I would at least check saadislams suggestion - either your description doesn't sound as if software or OS could be the cause, I never heard/read about related problems with CM (any version) and I also didn't notice myself while using the stable or now with LeWa OS which is based on 7.2 stable also. What you could also try is remove the back cover and give an air blast to the microphone.
[Wildfire Android Development] cecenac:
Guys is this the fastest rom for this phone? What rom do you use as your everyday rom, this one or some cm7 modification?

And also, can someone give me a link to rooting the phone procedure. thx ahead!
[Wildfire Android Development] eventcom:
fastest depends on settings and use - but most of the slim ROMs are based on CM7.

Re. guide: what hboot are you on? - 1.01.0002? - then you might find this one useful: > HTC Buzz: Wildfire > Wildfire General > [FULL GUIDE] Rooting HTC Wildfire (BUZZ) 2.2.1 with HBOOT 1.01.0002 !! (5/8/2011)
[Wildfire Android Development] dcamanni:
CM7.2 stucked when reboot

Hi all,

I currently have CM7.1 stable, fully working. I tried to update to CM7.2 stable just by flashing it as in instructions, but it gets stucked in reboot. I'm not able to get the /proc/last_kmsg file because I'm not able to connect to my PC after that, mounting the USB storage.

Any help?

Thanks.
[Wildfire Android Development] eventcom:
probably something went wrong during flashing or some leftovers of CM7.1 cause problems.

To avoid this I usually do the following when flashing an updated ROM (not a totally different):

- format system

- wipe cache

- flash new ROM

- flash Gapps

This usually prevents from any problems. Have you done so, too. If not: try it. If yes: hopefully you made a nandroid backup...? You could do a full wipe, then and if that works do a partial restore (data) of your nandroid backup ("advanced restore" in CWM).

Other ideas: do you have custom mtd partitions (and forgot about the bravo boot file)? Do you have apps and/or data on an ext partition?

--- EDIT ---

the OP says formatting/wiping not needed: yes - I'd also try it this way first when updating from a previous version (but also wipe cache). In case it doesn't work I'd first clear the dalvik-cache to see if that works - else I would try above method... ;)
[Wildfire Android Development] dcamanni:
Thanks for your answer. I have a backup and I restored it at the moment. I do have a custom MTD partition. Is that a problem? I would like to avoid full wipe, but just update the current OS. I did it in the past, when 7.2 was an RC with no issues, but I did not have a custom MTD partition at that time.

In this case, should I need to do something different?

Thanks.
[Wildfire Android Development] eventcom:
shouldn't make any difference but have you flashed the bravoboot file directly after flashing the ROM (as advised by the instructions)?

Regarding a full wipe: when just upgrading to a new version I usually don't do that, too, but formatting just /system and wiping caches avoids a few possible problems like leftovers etc.

Swyped from my HTC Wildfire (Buzz)
[Wildfire Android Development] dcamanni:
I was able to upgrade it by flashing bravo boot image after CM 7.2. I didn't remember to flash custom partition too. Did not format system and everything went fine. Just a question: what are issues may raise when upgrading without formatting?

Thanks!
[Wildfire Android Development] eventcom:
Most likely an upgrade up to the next version (or a few above) will do without formatting or wiping - it's just more secure and clean. If you look around here there are often threads with loads of problems resulting in just flashing over. In most of all cases people won't remember every little tweak they made. There might of course also be changes to essential parts of the system sometimes. Problems might also show up later (when installing other things or making changes, tweaks) and you can't exactly narrow down to the problem anymore.

If you flashed over say 2 or 3 updated versions you might end up in a completely individual (and unique) ROM and your problems most likely couldn't be solved even by experts.

That's why I (and a few others) prefer to clear the system (more than that a lot of Flash-o-holics do a complete wipe/factory reset). This means lesser problems and work because if you have issues - it's most likely the ROM and not your special, individual setup ;)

If you're an expert Android developer you might crawl through the changelog and every little commit to find out if you should make a fresh install or just flash it over - but I guess almost nobody would do that.
[Wildfire Android Development] dcamanni:
So, which steps would you recommed to do?

1) Format /system

Which wipe operations would you recommend then?

Thanks.
[Wildfire Android Development] eventcom:
That's what I would do when udating CM versions (also done when flashing a CM based ROM over CM - although this could be considered as "dirty method" as well lol)

- format /system

- wipe cache

- flash CM

- flash gapps

- flash bravo boot

- reboot

If by any means something doesn't work as expected I'd most likely reboot into recovery and wipe dalvik-cache also and if this would go wrong again I'd either do the whole procedure again or directly do a full wipe. But that normally shouldn't be necessary while upgrading a newer CM version.

Please note that - although not confirmed - it has been reported that CWM sometimes fails with wiping (therefore the second attempt before a full wipe...)
[Wildfire Android Development] dcamanni:
I restored my latest backup and updated CM7.2 as per your instructions. Everything went fine without issues.

Thanks!
[Wildfire Android Development] Posthuman83:
Please help me to flash my old wildfire buzz with default stock ROM. I used to install CM, but for now I like to roll back. Looks like due to HBOOT downgraded I have no possibility to install stock.
[Wildfire Android Development] mrkosta13593:
when the flash of the camera is turned after taking a picture sound not working (music, ringtone, media sounds, all sounds) and after the restart device sound working. fix that bug.
[Wildfire Android Development] eventcom:
If you just want to go back to a stock ROM you could try to use a flashable RUU. You can find some links in the Complete Wildfire Index thread: http://xdaforums.com/showthread.php?t=1029318

If you want/need to completely revert to unrooted and s-on - there's a thread in "General": http://xdaforums.com/showthread.php?t=1511155
[Wildfire Android Development] Slymobi:
Search through the cm7 settings and turn off camera sound option. Its a known bug.

Forum fishing.... Who's biting!
[Wildfire Android Development] eventcom:
Just an additional explanation

please note that this is an official release of the CyanogenMod team. The thread has just been opened to discuss the ROM related stuff - but bugs should go to the devs (wrong place here) ;)
[Wildfire Android Development] WaPeR32:
I did that last weekend. THe proccess:

1. Install HTC and Android drivers

2. Reboot to fastboot to install those drivers

3. Once you installed drivers, restart

4. Create a goldcard

5. Download and run latest ruu (.exe)

6. Use the tutorial to make S-ON again
[Wildfire Android Development] eventcom:
1st he didn't explicitly mention that he wants to go s-on again

2nd please guys, I think it's not a good idea to hijack this ROM thread for some Q&A totally OT ;)

Swyped from my HTC Wildfire (Buzz)
[Wildfire Android Development] WaPeR32:
Sorry, I didn't want to hijack this thread, I only wanted to help because I did that recently.
[Wildfire Android Development] eventcom:
no worries - I almost would have given that hint before your post (but for some reason I haven't done it). It's in no way your fault as - like you said - you just wanted to help.

But it would be nice if everyone would just think a moment or two where his question would match best as this is not only a question of OT clutter in posts but also if someone else is looking for a solution for a similar problem he most likely won't look here :eek:

Today my awareness for this had been refreshed somewhat because I stumbled across that nice forum rules vid yet again :D

[YOUTUBE]JmvCpR45LKA[/YOUTUBE]​
[Wildfire Android Development] mrkosta13593:
I thought that the cyanogen mod rom without any bug... just perfect rom without any little issue... :( but still great rom... :D
[Wildfire Android Development] eventcom:
not sure if you're referring to that camera sound issue... if so: please consider that our little Willy is almost a legacy device. It's not really a bug more an incompability of our Willy (if I didn't miss this thing happen on other devices, too)
[Wildfire Android Development] infernovip:
NOT TRUE!!! the bug is anyway you will turn on or turn off... i have using the cyanogen mod about 2 years and the best working camera in on stock wildfire rom....
[Wildfire Android Development] eventcom:
lol sry to say but I've been using the stable for some time, too and the RC1, 2 and 3 and a lot of nightlies - plus my current ROM is also based on the 7.2 stable. I always turned the shutter sound off and I never have experienced that bug ;)

And what exactly is not true? I knew of that bug (from older versions though) but it's still not the right place here. Again: you won't find anybody to solve it here (for the official CM7 ROM at least) - you have to tell the developers (CyanogenMod) ;)
[Wildfire Android Development] aq79:
Yes, shutter on/off seems to be working for very long. I always turn off camera shutter every ROM I install or wipe data. Never seen any bug around that feature. You might have something wrong elsewhere which is causing this issue.

Stock camera is different, but i don't believe its better than CM, some on-screen controls are not available in the Stock camera, makes it a bit less handy
[Wildfire Android Development] DooMMeeR:
Hi there

I updated a Wildfire from an old <7.1 nightly to 7.2 table and got a problem… the phone ist stuck in DockMode (did not even know the Wildfire had one…)

I fixed the symptoms (cannot fix that calls are going to speaker by default) but it still annoys me…

home lead to desk clock instead of ADW and as said calls are on speaker per default…

what is this…? I have no freaking idea…
[Wildfire Android Development] eventcom:
There are 2 threads in the Q&A section whith similar problems - not long ago. If I'm not mistaken it hasn't been discovered yet what exactly causes the problem(s) and no idea if the suggestions did help - I'll have a look, too.

--- EDIT ---

These are the threads:

http://xdaforums.com/showthread.php?t=1830835

http://xdaforums.com/showthread.php?t=1797118

And if I remember correctly it could be caused by dirt particles in the usb port which messes up some contacts and let the phone think it was in car mode.

Solution: cleaning the usb port (carefully! I remember that, too, that particles could be blown under the display etc.)
[Wildfire Android Development] Posthuman83:
Many thanks bro!
[Wildfire Android Development] sreekuax:
Hello All,

Last Saturday I rooted my Wildfire and installed Cyanogenmod7. Its brilliant and super fast now. But I found that 3g is not working. Anybody do have a solution?

Asking because I do have a good 3G plan and I dont want to waste it. :( Also as a techy I do have to check my emails time to time

---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------

Hello All,

Last Saturday I rooted my Wildfire and installed Cyanogenmod7. Its brilliant and super fast now. But I found that 3g is not working. Anybody do have a solution?

Asking because I do have a good 3G plan and I dont want to waste it. :( Also as a techy I do have to check my emails time to time
[Wildfire Android Development] drewniany92:
Which version you have installed? maybe try newest one from official CM site and it should work. I have it now and it works perfect for me (:
[Wildfire Android Development] lo2ay:
Check your APN settings
[Wildfire Android Development] handisetyadi:
can anyone please upload the stock apk cm7

-> message apk

-> dialer apk

please i need them to solve bug on JoyOS

regarding to this post

your help will be appreciated really high
[Wildfire Android Development] eventcom:
if I''m not totally mistaken those don't exist in CM7...

This is the complete /system/app:

AccountAndSyncSettings.apk

ADWLauncher.apk

AndroidTerm.apk

ApplicationsProvider.apk

Bluetooth.apk

Browser.apk

Calculator.apk

Calendar.apk

CalendarProvider.apk

Camera.apk

CertInstaller.apk

CMParts.apk

CMScreenshot.apk

CMStats.apk

CMUpdateNotify.apk

CMWallpapers.apk

Contacts.apk

ContactsProvider.apk

DefaultContainerService.apk

DeskClock.apk

Development.apk

DownloadProvider.apk

DownloadProviderUi.apk

DrmProvider.apk

DSPManager.apk

Email.apk

FileManager.apk

FM.apk

Gallery.apk

HTMLViewer.apk

LatinIME.apk

LiveWallpapersPicker.apk

MediaProvider.apk

Mms.apk

Music.apk

PackageInstaller.apk

Pacman.apk

Phone.apk

PicoTts.apk

Protips.apk

Provision.apk

QuickSearchBox.apk

RomManager.apk

Settings.apk

SettingsProvider.apk

SoundRecorder.apk

SpareParts.apk

Stk.apk

Superuser.apk

SystemUI.apk

TelephonyProvider.apk

ThemeChooser.apk

ThemeManager.apk

Torch.apk

TtsService.apk

UserDictionaryProvider.apk

VoiceDialer.apk

VpnServices.apk

--- EDIT ---

Dialer should be Phone.apk and messaging should be MMS.apk - could upload these if you need ;)
[Wildfire Android Development] eventcom:
just in case I won't find the time later...
[Wildfire Android Development] metapolis:
Freezing problems

Hi, tried to find out in which blog I can find a solution but I had no luck. Wildfire down, charging, red light is on. Try to start it but it doesn't work. Have to take out the battery :(

Any solutions?
[Wildfire Android Development] Slymobi:
this sounds like the charging bug caused from cwm? upgrade your cwm version. search for term "offmode charging bug" to review solutions etc. i recommend cwm 5.0.2.0 :)

R.V.3 (MokeeOs)
[Wildfire Android Development] cceerrtt:
I am living with this bug in clockworkmod v2 almost for two yeas... this is not really an issue. just charge your phone before it completely dies. And if it dies, charge it for few minutes, then remove battery and turn the phone on... I also worried regarding this bug but now I can say that during these two years I had to do it once, maybe twice.. I always charge my phone before it dies. On the other hand, without clockworkmod v2 I wouldn't be able to flash some updates.
[Wildfire Android Development] Slymobi:
if you must charge your phone in the power off mode then you will always get this issue unless you upgrade your cwm,i however in 2 years have never turned my phone off to charge! just sleep.

you can use temp cwmV2x if required when using an upgraded cwm via a flashable zip or from rom manager. so there is no reason not to upgrade really :)

R.V.3 (MokeeOs)
[Wildfire Android Development] ka9090:
Force close error

Whenever I try to save a contact I get an error :

The process android.process.acore has stopped unexpectedly. Please try again.

And also the screenshot feature is not working properly.

Any fix for this?

Gratitude in advance :good:
[Wildfire Android Development] alamgirqazi:
1) screenshot is still an issue with cm7.

2) try the latest nightly. no such issue with that.
[Wildfire Android Development] bilal1947:
which version is better cm stable 7.2 16 june 2012 or cm nightly 7 01 March 2013?
[Wildfire Android Development] elia222:
It's better latest nightly :good:
[Wildfire Android Development] bilal1947:
The best rom, thanks cm7 team, i use mtd to have 140 10 values, Whereas sense rom needs 250 10. So still have 150mb ram

have latest viber no issues at all, default browser works great. A total of 45 apps.

Have 1 and half day battery life heavy usage of 5 hours screen on time and wifi and gsm always on. connectivity,

Loved it.
[Wildfire Android Development] Cheshire_Puss:
Slow WiFi

Hi guys!

I installed this mod long time ago but still can't figure out why my WiFi is so slow. Here is my problem: when I go to Whireless $ Networks > WiFi settings , networks are updated very slowly, when I choose desired network to connect the screen stucks, then it takes long time to enter the password letter by letter, so slow! as if it used up all the processing power. Actually, I overclocked phone to 729 MHz . Can it help if I flash to Radio_13.55.55.24H_3.35.20.10 . Now I have Radio_13.53.55.24H_3.35.19.25 .
[Wildfire Android Development] bilal1947:
Try latest nightly from get.cm under buzz
[Wildfire Android Development] bilal1947:
Just wanna know which is fater cm 7 or 6.1, any ideas.