yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] Forceflow:
Been trying to keep up with development here.

In short: Arco made a new kernel to enable USB tethering, that didn't quite work. Hope the right kernel gets into RC3 then.

:)
[Wildfire Android Development] melvinchng:
You mean he fix the kernal? (Sorry, I don't quite understand.)
[Wildfire Android Development] neoazrael:
With nightly 31reboot. Problems because of 3g for developers information...without ril replacement nonsolved new kernel isnt useful to fix it too
[Wildfire Android Development] zexcrazy:
No, he made a new kernel to solve screen off bug and with that kernel usb tethring will not be possible for now because he reverted usb drivers.

Esit: in a mater a fact it will work but not natively, you need to install wired tether app.
[Wildfire Android Development] ShyamSasi:
With Build 31 USB tethering works fine for me :confused: You guys using different Kernel than the one that comes with 31 ?
[Wildfire Android Development] zexcrazy:
It works in 31, but it will not in next nightlies because new kernel is not yet aproved, so therefore its not yet implemented. New kernel is posted few pages back, its called 2.6.32.36 and its released to solve screen off bug.
[Wildfire Android Development] ShyamSasi:
Ooops .. Just noticed :)
[Wildfire Android Development] Bi0haZarD:
Information about arco's new kernel 2.6.32.36

Follow link below to get informed about changes in new kernel 2.6.32.36

http://review.cyanogenmod.com/#change,4241

Changes:

buzz: Update prebuilt kernel and module

- Reverted wifi driver to 4.219.248.20

- Default CPU speed set to device original

- Updated stuff from buzz MR sources

- Reverted backported USB drivers (was causing a couple of annyoing issues)

- Update kernel to 2.6.32.36

- Disable option for native USB tethering since it doesn't work after driver revert

- Remove pthread hack

- Move rotary lockscreen style a bit down to avoid overlap on caller screen

Change-Id: I8b8c026975127957a7dc1937144f125020807cf2

And arco gave us the new flashable kernel here to test because it isn't approved yet:
[Wildfire Android Development] Darian90:
anybody having problems with the trackball wake on 31? It worked for me like yesterday but today it somehow can't work anymore
[Wildfire Android Development] Bi0haZarD:
Depends really on what you have initially flashed (rom/gapps/dta2sd/radio/kernel) and if u flashed something after rom reboot (test kernel)...can u be more specific?
[Wildfire Android Development] Darian90:
Well I'm on nightly 31, latest gapps, my radio is 13.45.55.24H_3.35.15.31 (haven't flashed new radio because I'm not really sure what will happen if I go wrong) and also I dont have arco's kernel. I have Jacob's 4.2 running.
[Wildfire Android Development] zexcrazy:
Trackbal wake doesnt work with Jacobs kernel.
[Wildfire Android Development] kevin2516:
Just flashed #31 along with new kernel and SD card read speed fix, tis awesome, and so is smartass :D
[Wildfire Android Development] Peter_Peterson:
getting bootloops after flashing #31. do i need to do a full wipe to get it work?

also applied arcos kernel from today

didn't flash any radio or something like
[Wildfire Android Development] Zorkman:
no need for a full wipe when upgrading from another nightly
[Wildfire Android Development] kevin2516:
No I don't, why would I have 3d and why do you care so much about it lol
[Wildfire Android Development] Peter_Peterson:
Could you guys please try to stick to the topic?

The whole thread already is a mess and now it's getting worse dramatically
[Wildfire Android Development] mike_11:
HTC sync

Hello

I installed this rom' and like it very much.

my problem is that i cant sync the buzz to my pc, becouse i have all my contacts in outlook.

is there eny way to sync outlook contact to my buzz' with this rom?

when i connect it to the pc , the HTC sync will not recognise it, hence no sync.
[Wildfire Android Development] jasonfreeman:
Guys, is it possible to stfu about the sd-card stuff and stick to the topic?

Maybe someone should make a topic where we can discuss random stuff...

MESSAGE FOR EVERYONE:

If you have certain issues involving random development/experimental stuff that does not suit this topic, I would like to redirect you to this new thread:

http://xdaforums.com/showthread.php?p=12459025#post12459025

This way we'll keep the topic nice and clean ;)
[Wildfire Android Development] vimjam:
You can sync those outlook contacts to your gmail account and then re sync them by adding gmail account to your CM7 contacts account

posted via XDA APP
[Wildfire Android Development] Zorkman:
might it not be interesting to raise the default size in CM?
[Wildfire Android Development] Peter_Peterson:
Indeed but it's also nice to have a decent gallery, a fine looking theme and some cool apps under CM7 but those topics also don't belong in here.
[Wildfire Android Development] ex-slym:
#31 launcher pro plus 0.8.3 works very laggy, sometimes it FCs or hangs
[Wildfire Android Development] johi69:
fully agree
[Wildfire Android Development] mn78jag:
Try 0.8.4 it came out today:D. But adw ex is really smooth..
[Wildfire Android Development] DaXmax:
RC3 not out but the similar one is out... #32...:)
[Wildfire Android Development] fasix:
eh eh.. now RC3 is out :D
[Wildfire Android Development] neoazrael:
rc3 out right now :D
[Wildfire Android Development] DaXmax:
Whoops... My bad... So what's new on kernel? Sorry if i m being noob...
[Wildfire Android Development] Formiak:
Nothing interesting has been merged into RC3.
[Wildfire Android Development] zexcrazy:
Is new kernel in it?
[Wildfire Android Development] 3xeno:
Nope, didn't make it. (I am assuming it is the latest one arco posted), i.e., this one:

http://review.cyanogenmod.com/#change,4241
[Wildfire Android Development] Formiak:
Yes.. it hasn't been merged.Hope soon will be and the carrier hide label too

You can check what is in the newest builds at this site

,

:-)

P.S

Guys see that the new builds now are coming at 3-5 pm GMT +2
[Wildfire Android Development] kai666:
This kernel caused my wifi to say that it had an error, makes a change from the usual disabled message of late I guess!
[Wildfire Android Development] infectedtr:
RC3 lost :S on http://mirror.teamdouche.net/?device=buzz

only nightly #32

edit:

i think they added somethings :)

it is back..
[Wildfire Android Development] jasonfreeman:
It's because the .zip file was corrupted.

No-one was able to properly flash it...

They are most likely re-uploading a rebuild of it.
[Wildfire Android Development] zexcrazy:
Its reuploaded http://download.cyanogenmod.com/get/update-cm-7.0.0-RC3-buzz-signed.zip
[Wildfire Android Development] volki2004:
But where stated in RC3 new Kernel?
[Wildfire Android Development] Peter_Peterson:
Im on nightly #14 i think (is there a way to determine that exactly?)

Radio 13.45.55.24U_3.35.15.31

Kernel 2.6.32.21-HCDRJacob - g606a571-dirty root@HCDR #2

Build number GRI40

Didn't flash any RIL, 3g fix or other zip's.

Should i flash nightly #32 or RC3?

Are there any fixes i also need to flash? (Had problems with connection lost and 3g on earlier nightlies)
[Wildfire Android Development] infectedtr:
u can see changes here http://cm-nightlies.appspot.com/?device=buzz
[Wildfire Android Development] zexcrazy:
Flash RC3, and flash this http://www.megaupload.com/?d=FT6R9W42 if you have signal loss issues.

New kernel wil be in one of next nightlies and signal bug will be fixed. Or you can find it few pages back, it is called 2.6.32.36
[Wildfire Android Development] jukethehitman:
Dude i have a fix to get wifi working :D it's really silly and you shouldnt have to do it this way to get it working but follow these instructions it works for me everytime with lastest nightly :)

Step 1: turn on wifi (duh! lol)

step 2: connect to wireless network ie. bthomehub. "Password has to be correct"

step 3: turn screen off, wait 30 seconds or a minute and then turn the screen back on.

Step 4: if not connected to the internet. turn screen off again and wait a few seconds and then back on until you are connected :P

step 5: if it works for you i would love a HELL YER! :)
[Wildfire Android Development] wildfire_paulie:
Uhm, is it safe enough to flash RC3 on #30

without the wipe (as i usually do with nigthlies) ?
[Wildfire Android Development] daddyspud:
No I wud do fresh install
[Wildfire Android Development] kai666:
Didn't work :-(

Thanks for the suggestion though

So far RC3 and #21-32 all disable my wifi.
[Wildfire Android Development] jukethehitman:
you have to turn the screen off a few times and leave it off for a while and then turn it back on then off on then off checking the signal bar everytime. it really works for me i wouldnt lie. Anyways im still waiting for a proper fix because i dont like doing it that way because it takes to long lol
[Wildfire Android Development] cybertyk:
just to clear things up

if im using Rc3 or newer nightlys i can fix the signal lose when screen is off with this	kernel_2.6.32.36.zip (which is experimental and not signed for CM7 just yet)

is this right also could i ask whats the best GApps for install on Rc3 or Nightly 30+
[Wildfire Android Development] kai666:
Thats what i did do more or less. Let me have 1 more go, before going back to #18 again
[Wildfire Android Development] jukethehitman:
I know your pain :( if i didnt get it working on 32 i would be going back to 14 :(
[Wildfire Android Development] zexcrazy:
Just flash that kernel and signall loss will be fixed. Kenel is approved but it didnt catch the train for RC3 i guess it will be in #33.
[Wildfire Android Development] cybertyk:
kernel_2.6.32.36

Hi i installed kernel_2.6.32.36 in recovery how ever its reporting in the about phone that im still using kernel_2.6.32.33 is this a bug or has it not installed
[Wildfire Android Development] zexcrazy:
Just checked it says clearly 2.6.32.36.

From where did you downloaded it? Are you sure that recovery didn't returned you error?
[Wildfire Android Development] cybertyk:
I downlaoded it from about 3 pages before this from this link "http://xdaforums.com/attachment.php?attachmentid=554190&d=1301316555"

and yep it said it was installed. only thing i can think of that might be a issue is that i use 3.0.0.6 recovery...

i just reinstalled the rom and with out a reboot i installed the kernal and i get

updating kernel

extracting system files

extracting kernel files

installing kernel

done

now rebooting fingers crossed

just looked in about phone and its still the same 2.6.32.33-nfinity arco@tuxbox #1

and i just checked the zip and it is def 2.6.32.36
[Wildfire Android Development] zexcrazy:
I'm using too recovery 3.0.0.6

Try this one, its the same, but maybe it will work and try to flash it form rom manager.

Edit: Attached another kernel, previous actualy been corupted.
[Wildfire Android Development] priv8:
Confirming.

I confirm that this kernel is now working and no longer corrupted unlike the previously posted attachment.

Flashed and works perfectly for me.
[Wildfire Android Development] cybertyk:
Cheers its all good except the wifi is not working :(
[Wildfire Android Development] zexcrazy:
Well, i cant confirm that cause i dont have wifi near but will try it out later.
[Wildfire Android Development] Formiak:
The next nightly will be with new kernel. http://review.cyanogenmod.com/#change,4241
[Wildfire Android Development] doomed151:
You don't need to, just enable WiFi and it'll write "Error".
[Wildfire Android Development] infectedtr:
i don't comfirm too.. my wifi works good ;)
[Wildfire Android Development] arco68:
Error when enabling wifi, means that the wifi module belongs to a different kernel. The correct module should be installed along with the kernel, so if anyone gets that error, something didn't go right when flashing.

For those with problems connecting to wifi routers, try flashing the attached zip.
[Wildfire Android Development] volki2004:
This is the last working kernel to for RC3?
[Wildfire Android Development] bluedragon1982:
I can confirm, with this LATEST kernel erverything (3G/WiFi) is working on RC3.

Great job arco ;) i think you fixed it - Thanks
[Wildfire Android Development] kai666:
Everything is not working with RC 3. For me at least it disables my wifi
[Wildfire Android Development] bluedragon1982:
Try the last kernel (post from 07:01) a few post above. Working perfect including wifi
[Wildfire Android Development] Bi0haZarD:
-1st of all...sorry for the long post but i think it is somehow needed...read on-

Hey Arco what's up? Hey in this kernel the difference from the last one you posted is the wifi driver...correct? have you used an older driver from an older kernel because the one included in the new kernel has caused problems for several people?

Just a side note...i have only been using HCDR.Jacobs v4.1 kernel with the old nightlies (pre rc1 and pre rc2 and latest nightlies until build #18) and since you released your own kernel i have been always using the stock one, the one included in rom in latest nightlies.

I have never had any serious problems with wifi, only some really problematic builds caused my wifi to behave a little weird...it was scanning for 1sec, not scanning for 1sec, scanning for 1sec endlessly but it would eventually connect (i'm always using 2G/nodata/wifi because i dont have a data plan and here in CY its 1eu for 1mb! :mad:), no signal drop issues, no proximity sensor terminating my call...nothing! Maybe i'm just doing it right or maybe it's just my wildfire got lucky with CM? :p

The only weird thing that i noticed with Wildfires in general is:

a) several Wildfires used to work properly with overclock @768mhz - no freeze no issues and used to work well on HCDR.Jacobs v4.2

b) several Wildfires couldn't handle 768mhz overclock and froze if set that high and they only worked well on HCDR.Jacobs v4.1 @max 729-748mhz

My wildfire is on b) and my conclusion is that there must be a newer/older version of motherboard installed in each type of Widfire with probably updated/downgraded components....and the "only way"(chk * below) to find out is to dissasemble the unit and check the version on the board...thats probably why some of us work without any issues and some have serious issues...

I would dissasemble my unit just for the record but the thing is that the phone is only 2-3 months old and has 2yrs warranty...but if anyone else that is facing the issues noted above, that his/her wildfire used to work well only with HCDR.Jacobs v4.2 and overclock @768mhz with no freeze issues, is willing to disassemble his unit to check motherboard version i will disassemble mine so we know wtf is happening here.

* Btw, if there is a tool that displays above info without opening the unit...that would be awesome, but i didn't have time yet to play enough with market... i mostly play with CM :p

Any volunteers - donators? :D
[Wildfire Android Development] mn78jag:
I cross my fingers that the lense loockscreen will be fixed in next nightly along with the rotary answer button doesent hide the callers name. When that is fixed i can rest with the neverending flashing of nightlys:mad:. Then cm7 is perfect to me.:D
[Wildfire Android Development] melvinchng:
HMm, I installed launcher pro plus, it is very+a lot fast, swiftly, speedy compare to adw ex. It loaded my apps within 45seconds after phone reboot. It doesn't force close too... remember to try it out if you can.
[Wildfire Android Development] 3xeno:
Pretty sure it has nothing to do with the motherboard, but, the quality of the silicon used in making the CPU. (The process is known as 'binning'). High binned chips will be stable at higher frequencies, low binned chips will not.

It's just like computer CPU's. Someone's Core i7 will be stable at 4.2 GHz, and someone's will max out at 4 GHz, with all same settings and components. No two chips are ever identical.
[Wildfire Android Development] doomed151:
The nightlies will continue even after a stable release.

I love the neverending flashing of nightlies, being stuck in a single version is boring.
[Wildfire Android Development] nhnt11:
both are fixed and lense unlock is waiting for approval. rotary fix will be in the next nightly (or has it already come out? haven't checked)
[Wildfire Android Development] nhnt11:
+1. hardly any chance of it being the motherboard.
[Wildfire Android Development] Bi0haZarD:
Bro, I know enough about overclocking,undervolting,overvolting, temperatures, regarding cpu, gpus, chipset, fsb etc etc... im in IT as a computer tech and i have been buiding pc's since 12yrs old, now i'm 31...and have an "only for gaming" pc liquid cooled cpu, gpu, hdd, dimm modules etc etc built for overclocking the balls out of it but running stock...cool and quiet...and faaast :p

My question wasnt regarding the way a cpu is built but maybe other components,chipsets for wifi/radio/bluetooth/fm radio are different make/model on one mobo and different on another...that would require different set of drivers for each component/chipset to properly "talk" to each one respectively.

And my conclusion is that people that have wifi/3g/gsm/data/bootloop issues are using hardware with non compatible drivers, thats probably why using an older ril file or from another htc model i.e. ace solves their driver issues regarding 3G/wifi etc etc. Because that specific ril "talks" properly to radio.

So if arco or nhnt11 or you or anyone else can shed some light at the end of the tunnel, my question would be: is these what im saying make sense for anybody? Is this a case of different hardware revision that needs different sets of drivers for each hardware revision???

Sent from my HTC Wildfire

Running Gingerbread 2.3.3

Cyanogenmod 7
[Wildfire Android Development] Bi0haZarD:
I have been using it since the 1st nightlies pre rc1 and confirm that its much faster and smoother than adw.

Sent from my HTC Wildfire

Running Gingerbread 2.3.3

Cyanogenmod 7
[Wildfire Android Development] melvinchng:
Hmm, I start assemble my gaming computer since 12 too, I'm just 16 now.. start from core2duo to core2quad, 160gb to 2tb, 2gb ram to 12gb XD, 7600gs to 9500gt...

Hmm, I understand what you meant. You can visit xda.cn (Chinese xda). There are steps and picture to show you how to open your wildfire into pieces.
[Wildfire Android Development] zexcrazy:
Wifi is working fine here, no error or anything.

I must agree on that there ara some differences beetwen our devices. For example, since the day i rooted it i was rooning spu on max speed, and nevere had issues with that, but some people had. And remember that some people was reporting earlier that wifi doesnt work for them with jacobs kernel 4.2, but for others it worked. And the lattest thing signall drop issue, some of us has and some don't.
[Wildfire Android Development] mn78jag:
When u are in cm7 or 2.3.3 I agre that LPP is smother in scrolling the homescreens if u have more than tree homescreens. But if u have, like me, three homescreens ADW is smoother for me. As a little experiment, compare the appdrawers for smoothness, ADW wins hands down if u choose "fast" as a preset. The appdrawer is still choppy in LPP and when u make a scrollstop u often start a app by accident....
[Wildfire Android Development] melvinchng:
Hmm, but loading widget speed and apps in app drawer speed after reboot it just use 45sec to load all my apps (250apps, 800mb) and lpp win.. I use 7 home, it is smoother in adw, but my app open a lot faster in lpp. When I open the drawer in adw, it actually lag sometimes, but no lag in lpp. And adw ex's drawer is smoother, but it has bug in new vertical, the last row of app can't show probably. I don't use dock in drawer, sometime it lag and when I press the twice, it opened the drawer and then the app in drawer.
[Wildfire Android Development] doomed151:
Guys, this thread is about CyanogenMod 7 Nightlies, not about launchers, SD speed boosters etc.
[Wildfire Android Development] Bi0haZarD:
Bro i have 3 homescreens blank, only CM wallpaper, i have no widgets both on adw and launcherpro, just to scroll the wallpaper ;)

I didnt tweak any settings for testing only, just to compare the two home launchers at default settings...for me launcherpro wins at smoothness and speed in app drawer as well. Plus since using launcherpro i never had any freezes or stuttering either when using the device normally or after rom flash...always smooth :D

I also have to note that since arcos kernel, and cpu governor settings that have been fixed and working properly i stopped using setcpu instantly - another plus for smoothness here...the whole experience in CM like window animations and transitions are way smoother now compared to the 1st nightlies.

I have been using the nightlies since build #0 and i'm really satisfied with the CM team and our Devs...without you none of this would have been possible on our wildfire.

For one more time i will say a BIG THANK YOU to ALL CM Team and our HARD WORKING DEVS that sacrifice their free time, and their efforts that they put into this project WILLINGLY.

I as well would share any information and help if needed any member in this forum, not just in this thread, because i feel doing so and it doesn't always have to do anything with money...I'm not rich, i have to work for 1000eu a month because this is life...there have been many difficult periods lately especially when you have a family and 3 kids...anw enough said...

- ON TOP OF EVERYTHING ESLE THERE SHOULD ALWAYS BE RESPECT TO EACH ONE OF US. WE ARE ALL COUNTING ON EACH OTHER FOR THIS PROJECT TO SUCCEED IN A TRUELY AWESOME STABLE MOD - (sorry for the caps i felt it was needed.)
[Wildfire Android Development] Bi0haZarD:
Sorry bro, i just commented on the home launcher posts because it really improves the responsiveness of the nightly build and i thought that somehow it should be related with the thread as well...anw
[Wildfire Android Development] daddyspud:
this thread is for only issus about the rom nothink else come on guys chill out a bit if people have issus which are related to the rom then this thread is where it meant to b placed people last few days have been takin thing a bit to seriouse if u guys really wana chat privatly go here

http://webchat.freenode.net/

##wildfire
[Wildfire Android Development] nhnt11:
Tl;dr.

For heaven's sake, USE PUNCTUATION!
[Wildfire Android Development] daddyspud:
for heaveing sake, get over it.

Im not at school,
[Wildfire Android Development] Bi0haZarD:
if u wanna think so np, but at least fix ur sig...its "KERNEL" not "KERNAL" sounds something like "ANAL" or so.
[Wildfire Android Development] ramdroid77:
...and it's spelled "HCDR" and "Clockwork" actually!

EPIC FAIL!!!!
[Wildfire Android Development] kevin2516:
Guys... lol
[Wildfire Android Development] Bi0haZarD:
I used to rent a shop and turn it into a -cell phone workshop, only repairs- 5-6 yrs ago but due to family obligations and the need of stable income, I had to move into IT in an offshore company, not the best income but at least stable...Anw back to the subject, I know how to disassemble, repair and assemble back a cell phone ;)
[Wildfire Android Development] melvinchng:
PLease correct me if I'm wrong.

Sd boost - speed of sd- related to this Rom right? Every Rom has different amount of cache (or I dunno what it mean) and it effect the speed of sd.

Adw launcher- it is launcher in cm7, still related. We discussed loading speed of apps in home.

Hmm, please correct me if I'm wrong. I really confused what to discuss here...
[Wildfire Android Development] Bi0haZarD:
lol hehe ;)
[Wildfire Android Development] Bi0haZarD:
Problem was that we were somehow off topic, because the thread is mostly for nightly bug reporting but discussions are allowed as well, as long as they're nightly-related bro.
[Wildfire Android Development] Bi0haZarD:
Check link below - what is cache in general

http://en.wikipedia.org/wiki/Cache
[Wildfire Android Development] nhnt11:
lolz. read ahead is just that your phone reads some extra stuff before whatever is trying to actually read it asks for it, so that its ready to spit all that out as soon as it DOES ask for it.
[Wildfire Android Development] nhnt11:
normally people learn punctuation in school for use in the outside world. :P :P

alright, I know I know I'll stop.