yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] bongmaster:
holy carp, thats much of an improvement to speed, angry birds runs smooth as now :3

as long as gps doesnt cause weird resetting now i should be good to go :3
[Wildfire Android Development] MarkPower:
Are the nightlies serious that good? I read all the good replies about it and I'm about updating. I'm still at 7.1-RC1.

PS : Can someone give me the changelog of the nightlies? I lost it :p
[Wildfire Android Development] .Harshit:
Here it is : http://cm-nightlies.appspot.com/?device=buzz

Regards
[Wildfire Android Development] ErwinP:
Arco, can you perhaps put this link to the changelog in the OP? It has been asked more then once..

--------------------

EDIT: never mind, it is already in the OP..

--------------------

BTW, one should defenitly upgrade from the RC1 to the latest nightly. I'm working with it for some time now, and te be honest, I didn't find any bug so far. Except for the doodle app that isn't working, but that is the same for the RC1 :-)

Erwin
[Wildfire Android Development] Dethox:
I have to agree. I have flashed Nightly 177 and it is very smooth.
[Wildfire Android Development] Lmasta:
174 seems the most stable, latest versions seem to reboot alot :(
[Wildfire Android Development] Solar_:
Where can I find/download the new kernel (2.6.35.14) ?

I'd like to test it with RemPuzzleRom 0.7.3 ;)

edit :

-lol it's at the OP. *is kind of blind*-
[Wildfire Android Development] Dark-Core:
176 is brilliant but the only thing is that i have to manually add in my apn to use data. i can do it and it works but thought that i should just mention it and wondering if anyone came across this
[Wildfire Android Development] -Howard-:
Seems everyone is loving the new builds, i may update my wildfire then :P
[Wildfire Android Development] nhnt11:
Seems the wildfire is still raging then? I'm actually missing mine a bit lol. It was a nice lil phone :)
[Wildfire Android Development] arco68:
Hello darling! Where have you been? :D
[Wildfire Android Development] kevin2516:
I was missing it because melvin was still around :p

Sent from somewhere far far away.
[Wildfire Android Development] paketek:
i'm done with this rome . :( from 100 above i have only problems

-phone reboots ,freezes , its slowly ,

If you are using phone a lot this is not rom for that

,so im staying on 7.0.3 stable
[Wildfire Android Development] DjoeN:
It's wierd

On my Wildfire the Nightly's are perfect, no problems

on my co-workers Wildfire, it keeps on rebooting 3, 4 times a day (sometimes more), I did both Wildfires identical on the same day for rooting etc..., same for putting new rom on it, always the same day., very wierd (but i'm happy, i have no problems :p )
[Wildfire Android Development] stefano2626:
gps still not working on build 177....even after flashing the latest radio....don't know what to do....i really like this rom but i need gps to work to....
[Wildfire Android Development] dcos:
You can try flashing sense rom, GPS should then work. And after that flash CM7.

Maybe it will work : )
[Wildfire Android Development] Dethox:
Gps works but from my experience you need to be outside of a bulding for the gps to properly work ( aka start and locate your position )

I once flashed a nightly without reflashing latest radio. I just intalled maps and when I was downtown I started the Maps to see how it behaves. The gps started and found my position.

I guess if there is not enough gps signal after flashing a new nightly, the gps won't start at all. It's my guess. I will further test it when I have enough time.
[Wildfire Android Development] neoazrael:
i gave my wildfire to my cousin and i am writing this message for him because he doesn't speak English. well as he said he installed nightly 171 and dark tremor's script then rebooted the phone and the simcard was locked and no dialpad to enter the pin code he tried it for a several times but when the phone reboots there is no connection with the operator so he can't call someone or send messages.then he tried 172,173,174,175 and the same result. what can be the solvation for him?
[Wildfire Android Development] :Mania::
Wipe cache and dalvik, installed #177 from RC3. without reboot, i installed latest radio. rebooted twice itself on the process but everything works. GPS gives me no problem. it can locate my exact position in less than 10 seconds
[Wildfire Android Development] Scratch0805:
I had a few problems with gps on 175 I think, flashed 19.25 radio, it then worked so I flashed 20.10 radio back again and it kept working.

Now on 177 and haven't had any problems since.
[Wildfire Android Development] keyra74:
source are down since 3 days
[Wildfire Android Development] arco68:
kernel.org was hacked.

http://linux.slashdot.org/story/11/08/31/2321232/Kernelorg-Compromised
[Wildfire Android Development] keyra74:
pfff fail :/
[Wildfire Android Development] -Howard-:
seems like i need to prep up my wildfire -.- my O2x appears not to like mobile data at all at the moment

why didnt i just wait and get the GS2 -.-
[Wildfire Android Development] Slymobi:
Sim lock

I had same problem, put sim into different phone and entered puk code obtained from network provider then put back into wildfire and was ok. I turned sim card lock off cos I think this was the cause. So just try sim in old phone then replace.
[Wildfire Android Development] neoazrael:
thx i hope it will be ok after trying this.i will tell it to him tomorrow ...
[Wildfire Android Development] Dark-Core:
Since the update to CWM we cant use the old zips we had for adblock as they still use the old amend script style and I want to steer away from using the old CWM. Is there a new/updated file that I can flash or another method to block ads on CM7?

and has anyone tried out the updated google apps package (20110828) or should i stick with 20110613?
[Wildfire Android Development] 3xeno:
Flash this in your new CWM to get temporary 2.5. Your 5.x version will remain unaffected and you will get back to the newer one after a simple reboot

http://xdaforums.com/attachment.php?attachmentid=662193&d=1311319218
[Wildfire Android Development] Dark-Core:
I was hoping to avoid that method but guess I don't have a choice.

Anyway, nobody try google apps 20110828?
[Wildfire Android Development] CosmicDan:
To fix GPS reflash RUU. Then go back to a stable CM7 and please stop complaining about experimental ROMs :)

Those with random rebooted, flash an RUU and format sdcard in PC and try without ext partition. If it still persists, replace sdCard. If it still persists, go back no non-experimental ROM. If it still persists, you have flashed too many ROMs and your NAND is worn out :)

Don't mess around with old hosts zips, just get AdFree from Market its frequently updated.
[Wildfire Android Development] nhnt11:
Not on XDA much ;)

oh and Kevin, LOL I kinda miss Melvin :')
[Wildfire Android Development] 3xeno:
Did you just imply the O2X is not as good? (ie - has issues)? It was one of the devices on my upgrade radar (Which is obviously pretty far away - but, it was there nonetheless) :eek:

Visit the Nexus S forums? :p BTW he still does maintain his Better Cam Mod thread here (I think), although there are 2 of them now.
[Wildfire Android Development] -Howard-:
Yeahh O2x does have problems well mine does, it seems some are lucky not to get any and other have more problems than me, but i mean i still like it it feels solid and once cm is on it, it becomes nice to use. But i cant say i would highly recoment it to people but its good for the money you pay against other dual core devices. I have CM back on thr old wildfire and i remeber why i liked it :P
[Wildfire Android Development] cire6:
everytime im using the viber, gapps is force closing?
[Wildfire Android Development] StratOS_HTC:
Having problem accessing the notification/power bar on #177.

Have tried with different settings nothing worked.

Cannot access the notification power widget after sliding down the status bar.

Any help or other symptoms ?
[Wildfire Android Development] CosmicDan:
I am on build 176 which is identical, there were 0 commits for build 177. I had this problem too but I can't remember rich build it was. I had to do a fresh install (wipe data and system) and also importing CM7 settings from TB caused it. So I had to setup CM7 settings fresh from scratch.
[Wildfire Android Development] StratOS_HTC:
Wipe, fresh install #177 and still the same.

#167 stuck and bootloop.

Guess it's the kernel.

Will try ...
[Wildfire Android Development] CosmicDan:
I am running 176, not 167. Well sorry I dunno, it works fine for me.

Just read that the CM7 buildbot is on-hold because of the kernel.org hacking rendering Android repo's inaccessible :(
[Wildfire Android Development] DjoeN:
Using #177 on 2 wildfires, don't have any problems with the notification bar or power widgets on it, all works great
[Wildfire Android Development] :
using 176 working great it is awesome 2d and 8hours of battery with a few viber, calls watsapp and some searching on web :) I couldnt reach even 2d with cm 7.1

my question is, weren't the nightlies updated all the days? why the last one is the 177? it is because something of the guy of cyanogenmod being hired by some mobile company?

Or it is that they are going to launch another stable version?
[Wildfire Android Development] ErwinP:
It is something about kernel.org that is beeing hacked. I don't know the details (and I'm not having the essential technical skills as well), but as I've understood, it can be that the hackers have put some malignant code in the kernel that is beeing used by all the cyanogenmod distributions. So I suppose they are checking the source code for changes?

Erwin
[Wildfire Android Development] Dark-Core:
177 working great for me as well. no problems that i can really see except for the fact that i have to manually configure my apn so that i can use data. patiently awaiting the next release
[Wildfire Android Development] Slymobi:
177 here too and all ok as of now. just wondering though if it is possible to get the screen timeout to never ?? i have set the screen never sleeps whilst charging but it dims and i want it to stay on full. any ideas ?? or any chance of including this in next build ?? pleeeeeeeeeeeease. regards slymobi.
[Wildfire Android Development] 4EVA:
Can i flash Radio_13.55.55.24H_3.35.20.10.zip using rom manager cwm v5.0.2.0 ?
[Wildfire Android Development] eagleofdeath13:
Easy, go to the display option, and make the "luminosity" to 100% :D
[Wildfire Android Development] Slymobi:
Mmmm can't seem to find that setting.?
[Wildfire Android Development] eagleofdeath13:
erf, i don't know how it's named in english (i'm french, so i use Android in french, and it's called "Luminosité" ^^
[Wildfire Android Development] Slymobi:
Thanks but I think your talking about 100% brightness but I was asking about an option so the screen never turns itself off or dims when I have it plugged into power. Max screen time out I can choose is 30 minutes but I would like a never option. Hope I've made my query a little more understandable !!! Thankyou though.
[Wildfire Android Development] eagleofdeath13:
Have you gone to dev options? Something named "stay active" or something ilke that?
[Wildfire Android Development] Slymobi:
Yes I have set that to stay awake. It does stay awake but my point is that it still dims after a x amount of time x = screen timeout setting. I just want no dimming at all when plugged into power. !!!!!! 3xeno where are you ??? Lol
[Wildfire Android Development] 3xeno:
lol, sorry mate, but whatever solutions I possibly had in mind, you have used it, without success:

- Set Timeout to max

- Settings > Application Settings > Development > Stay Awake (Screen does stay on, but, it does dim, which is something you don't want, obviously)

But, if you are ready to use 3rd party apps to achieve it, there are a lot of options:

- Screebl Lite (And full)

- Screen On

- Keep Screen

There are probably a lot more, so you can dig around a bit to find one that suits you.

Good Luck
[Wildfire Android Development] Slymobi:
Lol. Cool 3rd party here we come then. Cheers.
[Wildfire Android Development] Slymobi:
Screen on did the trick. 3xeno you are my yoda you are.
[Wildfire Android Development] volki2004:
Where # 178 #? :D
[Wildfire Android Development] 3xeno:
Quote by Cyanogenmod: (And arco a few pages back)

The reason there are no CyanogenMod nightlies at the moment is because kernel.org was hacked and the android repositories are inaccessible. They will be back soon.

http://t.co/DxxYATg
[Wildfire Android Development] :
Not vulnerable. The kernel CANNOT be modified that easily in unauthorised way (on kernel.org that is).

Google on how Git makes it impossible to edit past commits without having a warning.

Essentially, any change is rejected if the hashes don't match. If you change the code, hashes change and stop matching which in turn gives a warning. Then the offending code is examined closely or thrown out
[Wildfire Android Development] laraz:
Right i have turned to the darkside and become a young Nightly jedi and flashed the new nightly lol:D
[Wildfire Android Development] DjoeN:
I recently installed #177 on a wildfire from a friend. (Full clean install, wiped everything (Recovery 5.0.2.0)

Since a few days his wildfire randomly reboots and all apps that require superuser crash, Superuser itself crashes also:

"App superuser (proces com.noshufou.android.su) has unexpected stopped, try again"

I tried to reïnstall su from the market, but that doesn't work.

Any ideas

(I guess the random reboots come from the broken SU app?)
[Wildfire Android Development] enteringrunlevel5:
i had similar issues with a different rom. problem was that busybox was not properly installed (go terminal, type busybox and should get a list of commands).if not, do the busybox installer from market, install then do fix permissions from clockwork mod and reboot.

Sadly, if busybox is working ok you have different issues.

all the best.
[Wildfire Android Development] Dark-Core:
I had the same issue when i upgraded to CWM 5.0.1.0 (without reflashing the ROM). Anything involving superuser crashed. after i flashed the ROM I was up and running again.
[Wildfire Android Development] 3xeno:
Did you use Unrevoked to install the new CWM? In such cases, crashing of SU is normal, because Unrevoked installs its own version of Superuser (The icon changes), which clashes with the existing version.

Anyway, a reflash solves it, as you have found it.
[Wildfire Android Development] pliurzis:
i flash radio but GPS still not working any ideas :confused:
[Wildfire Android Development] Posthuman83:
Oh, i so much like this mod. but my phone become so slow. slow respond on browser, market, status bar, sometimes i used to wait up to 30-45 sec to open sms or phonebook.

After flushing radio, my gps starts working fine and phne batt last up to 3 days in normal phone mode.

Should i roll-back to stable mode or to install again nightly builds?

____
[Wildfire Android Development] 3xeno:
Try installing the Nightlies again (After a full wipe). They are much, much faster than the old stable version.
[Wildfire Android Development] kevin2516:
Actually the devs are working on merging the source with BadaOS to form BadaRoid, which is why it's taking so long for the site to come back online.
[Wildfire Android Development] Dark-Core:
Yip I used unrevoked. I didnt mind the reflash coz that was my excuse to upgrade to nightly 177 which is awesome. Still annoyed that I had to hunt down a old version of unrevoked, the newer one gave that dumb error.
[Wildfire Android Development] pliurzis:
flashed radio from clockwork and :D gps working :)
[Wildfire Android Development] steve_032:
I had this issue after updating my CWM using Unrevoked. I cleared app data for superuser permissions and all my problems were fixed! Might be worth a try for anyone else experiencing issues.
[Wildfire Android Development] Posthuman83:
just noticed, that i can not erase my data fully. in botloader i choose wipe/erase, erase cache, and dalvik, and format my sd. after intsalling ROM, i found some apps like Gosms, ang GoPhonebook etc installed.

how to make my phone completely virgin :)

___

fixed: my ext partition was not formatted!
[Wildfire Android Development] zexcrazy:
Wipe /data and /system and that should be it.
[Wildfire Android Development] kakarot_22:
i have a big problem!

i cant use UOT with 177 , my phone gets bootloop after i aply the .zip

the .zip is correct and i know how to use the kitchen...

i cooked for wildfire rc7.1 but i got only bootloop... anybody knows something about that?

big tnx
[Wildfire Android Development] varalex:
Re

after more than two week break - cm_buzz_full-197
[Wildfire Android Development] enteringrunlevel5:
yeah,just flashed latest nightly from previous nightly.all good so far.
[Wildfire Android Development] pliurzis:
is it possible listen radio trought bluetooth headset ? :rolleyes:
[Wildfire Android Development] Slymobi:
I can't say yes/no but had strange situation otherday. Had Google navigation on and also Bluetooth car kit for calls. Now when I received a call whilst Google navigation was on, the sound from call AND navigation came through Bluetooth kit. When Call ended the sound from navigation went back through phone and no longer on car kit !!!

sent from my wilderbeast/buzz
[Wildfire Android Development] acaptake:
Flashed #196 yey! It's been 12 hrs since then (I think) and no bootloop yet. Hopefully the prob is fixed :)

Update: Phone starts to restart by itself again...
[Wildfire Android Development] darkstep:
i hade some random freezes and had to pull the battery, the nightly is little fast without juwes ram script
[Wildfire Android Development] dud3me:
You mean it's faster without the ram script?
[Wildfire Android Development] darkstep:
yes for me it is and i tested the new updated one and the old one, i will test it again this days cos its a great script
[Wildfire Android Development] kakarot_22:
Anyone is still flashing themes with uot? What are the right settings?
[Wildfire Android Development] jazzymc:
lag in phone.apk with CM7

Hallo,

Until now I've used the stock froyo rom, but since last week I rooted and s-off-ed the phone and now I'm with the latest CM7 Nightly build (177 and them upgraded to 192 if not mistaken the version number).

My sd card is the stock 2GB and is formatted with an ext partition of 512MB and swap of 128 MB. Actually I didn't installed any custom app2sd scripts yet but I think the CM7 use the partitions on card.

I installed LauncherPro and the phone is very responsive when I scroll launcher screens or open settings menus. but if i try to open some app (camera for example) it shows a blank black screen and the app is coming in 2-3 seconds later.

This is annoying but I can live with it, the main problem is that the phone. app has similar behavior. When the phone i s locked it shows the in-call lock screen and if I pickup the call it shows a blank screen and I can't close , to activate speaker. Also when I try to call somebody the phone app just stuck on black screen and it shows the in-call screen few seconds later. When I press the red phone icon the in-call screen stays on display for few seconds too.

I've tried to use another dialer (GoDialerEx, TouchPal Dialer and more) but I have the same experience.

I think this is probably a problem of low ram, and the phone tries to free some ram before opening any app, but I have no idea how to deal with it.

Please tell me is this a common problem with CM7 or it is my phone only?
[Wildfire Android Development] arco68:
No such problem here. Try to see if it's better with the standard launcher.

Btw, CM7 doesn't use any extra partitions you may have on the sd-card. Any ext or swap partitions on the sd-card is useless for standard CM7, unless you use some custom app2sd scripts.
[Wildfire Android Development] jazzymc:
Thanks for the tip regarding the app2sd. I've tried it with the stock gingerbread launcher and the adw launcher which comes with the cm7, but there is no difference.
[Wildfire Android Development] vijaykirann:
I have enabled swap on my wildfire using though just 32mb.

swapon /dev/block/mmcblk0p3

It definitely had effect on the responsiveness

Sent from my HTC Wildfire
[Wildfire Android Development] DjoeN:
#198 is working great, no problems so far (except, can't find the new updated google+ app in my market, even market enabler doesn't work)

Speed is very good

BT works perfect

WiFi / Data works perfect

Internal 141MB Free from the 183MB (Got lotsa stuff installed)

a2sd works great with "S2E" from the market

Everything works smooth :)
[Wildfire Android Development] cedriccc:
I'm on 176, any1 would recommend to update to a new version?
[Wildfire Android Development] zexcrazy:
Market says that G+ app is not comatible with wildfire. :confused:
[Wildfire Android Development] DjoeN:
Well, downloaded it on my 7" tablet and then placed it on my TF of the Wildfire

Installs fine, works fine (it's a 10mb apk)

Google+ v1.0.7
[Wildfire Android Development] hacktrix2006:
anyone getting issues with #199 with reboots after it fully boots. Going to go back to #198 just wondering if anyone has the same issue.

I have done a full wipe 8 times same thing happens each time.
[Wildfire Android Development] komunistvb:
no issues with #200 it is fast and working with dtapps2sd-2.7.5.3-beta03-signed and with Juwe_Update18082011_RAM_Script no problem wich i have in #198
[Wildfire Android Development] thestory101:
After flash ROM,

It's automatically change a partition size ? or we have to do something else ?

If yes , which 's one should be a first step.
[Wildfire Android Development] nhnt11:
LDPI makeover just missed getting into #36 haha :D
[Wildfire Android Development] ernestnwanu:
What exactly is the LDPI makeover?
[Wildfire Android Development] Eddster3000:
I think LDPI is the low density screen resolution that the wildfire has. I guess the makeover is a change to the rom graphics to make it fit more nicely and look sharper on our screens. I could be wrong in which case can someone clarify
[Wildfire Android Development] nhnt11:
You are right. If you've seen my CrispyBread theme (themes and apps section), the graphics from it are now integrated into CM. Next nightly will have it.

http://review.cyanogenmod.com/#change,4350
[Wildfire Android Development] DjoeN:
seems like the beautiful widgets problem has nothing to do with #35 but with launcher pro plus, installed GOlauncher EX and it worked without closing down, also works fine under ADWLauncher.

Seems like the new Launcher Pro gives me more problems then before the old version.
[Wildfire Android Development] -Howard-:
Dam as if it just got missed out :( anyone have a local build with it haha ;) can't wait for it now nice work
[Wildfire Android Development] ernestnwanu:
So basically, if I have been using the CrispyBread theme, there will be no difference? It's a great theme btw ;)
[Wildfire Android Development] nhnt11:
No difference if you've been using CrispyBread. BUT you should stop using the theme, it will be redundant after this.

BTW, just the LDPI makeover doesn't change our build, the change to our PRODUCT_LOCALES to incorporate compiling with LDPI resources has to be merged as well. http://review.cyanogenmod.com/#change,4373
[Wildfire Android Development] ernestnwanu:
Oh ok, thanks for explaining! It'll probably be in the next build then?
[Wildfire Android Development] stefand:
Here you go.

My private build #36

http://db.tt/7up0sNR
[Wildfire Android Development] alangrig:
Due to LDPI merge, will be it possible to revert to MDPI in the upcoming builts?
[Wildfire Android Development] nhnt11:
why would you want to do that?
[Wildfire Android Development] -Howard-:
Thanks ill try it out :)
[Wildfire Android Development] nhnt11:
even on private builds you wont get the makeover.
[Wildfire Android Development] -Howard-:
Aww Damn okay :/
[Wildfire Android Development] stefand:
No???

I did change the buzz.mk file myself. ;-)

Just check it out yourself.

Btw, the makeover looks great.
[Wildfire Android Development] -Howard-:
He's right he has just flashed it and makeover is very nice :D
[Wildfire Android Development] stefand:
@Howard: The Gallery app in my build is Gallery3D, so it will we a bit slower.