yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] arco68:
Ok, been quite busy figuring out this 3G thing. Here's an attached zip file you can try to flash. Hopefully it should work after that. You might have to fully wipe and format system, then flash rom and flash this fix. The zip includes updated kernel, original libhtc_ril from Wildfire rom and build.prop. If this proves to work, I can add it to CM.
[Wildfire Android Development] nhnt11:
By the way, just fyi, my battery seems to drain really fast when on mobile data - it went from 79% to 78 in an hour during which I sent a lot of messages and played a game, but when I turned on mobile data it droped to 73% in 5 minutes. This is just one example, it happens every time.

Edit - maybe I'll try that fix you just posted.
[Wildfire Android Development] johi69:
trying #23
[Wildfire Android Development] neoazrael:
yeah finally 23 so i am going to try right now
[Wildfire Android Development] johi69:
#23 3g not working :(
[Wildfire Android Development] Michealtbh:
Thanks... :)
[Wildfire Android Development] neoazrael:
no screen responsiveness issue,boot successful with the new kernel,fast,3g works here.wifi and usb storage statuse works .wifi tethering works
[Wildfire Android Development] zexcrazy:
Did you flashed 3g fix posted above or just nightly?
[Wildfire Android Development] Bi0haZarD:
it actually is that precisely, it's disabled by default since #21
[Wildfire Android Development] mn78jag:
23 booted fine with 3gfix and 3g is working. But after reeboot it starts to bootloop....

Maby its my s2e script
[Wildfire Android Development] johi69:
unfortunately 3g-fix does not work for me.

did you do a full wipe?
[Wildfire Android Development] Peter_Peterson:
#23 installed. working fine - no boot issues, no problems with 3g
[Wildfire Android Development] nhnt11:
the new 3g fix with the old libhtc_ril does not work after reboot for me. (reboot on enabling 3g)
[Wildfire Android Development] alangrig:
3g working on the first boot. Installed gapps, constant bootloop.
[Wildfire Android Development] ramdroid77:
had the same problem when I flashed 21 + 3gfix yesterday. First everything was working, but suddenly my data connection dropped. Also I was also unable do make calls. Then I rebooted and from this time on the phone was always rebooting as soon as data connection was established.

After that I went through a weird/funny (or not so funny) drama to make my phone usable again: Usually I always to a nandroid backup before any modifications. Currently I have only a small SD card. so I usually delete my last nandroid backup (or move it on my PC), boot into recovery, create new backup, then flash etc. Unfortunately this time I forgot to create a new backup (and I was not at home, so no access to any older backups). So I just wiped system partition and flashed back to RC 2. Phone started, data connection established, reboot. ****! Tried multiple ROMs, 4.1 kernel, everything, full wipe of all partitions, etc. but never got rid of the reboot issue. Finally I flashed the official HTC Froyo ROM (without hboot of course) had another reboot but after that it's been working. From here I flashed back to RC 2 and finally phone is back to normal. However I also had to flash 4.1. kernel in order to get a working data connection. In the past when trying CM7 nightly builds or RCs I never needed to flash an old kernel. Guess something's broken now which is resisting full wipes gnaaaaaaaa! Oh, and please remind me, I should make a new nandroid backup asap!
[Wildfire Android Development] pan_pietrek:
Applied 23 with that new 3g fix (the one with htc_ril) did not do a full wipe and no go... Screen goes off signal goes bust.
[Wildfire Android Development] mn78jag:
I just flashed newest radio from wildpuzzle thread on top a older nightly and 4.1 kernel and im good to go. Beware of dangers of flashing radio:D
[Wildfire Android Development] zexcrazy:
So we are in a problem here with three latest nighties. I have tried warious ways of flashing rom and 3g fix but none of them worked. 3g issue and signal loss when screen goes off issue still persists. As i'm concerned only way of making this nightlies usable is to flash 4.1 kernel, maybe 4.2, but havent tried. Drained my battery almost with messing with this, so im done with testing till i get home latter.
[Wildfire Android Development] kevin2516:
This new kernel really messed up the nightlies lol, I'm going to wait until i can just flash over nightlies without flashing extra stuff to fix things. Hopefully it gets fixed soon.
[Wildfire Android Development] johi69:
did a full wipe - flashed #23 again - 3g worked only for a couple of minutes. :(

back on RC2 now.
[Wildfire Android Development] neoazrael:
I followed this way

Formatted sd card 6.5gb fat 1.5ext3 transferred cmod nightly 23 gaps etc

Format system,data,cache

Wiped all,cache,dalvik battery

Format system one more time

Flashed cmod and gaps

Boot absolutely perfect no problems with 3g gps wifi screen and everything else evem after a few reboots
[Wildfire Android Development] nhnt11:
I dunno guys, I don't have any issues at all with my local build and the build.prop fix, its running smooooooth... except that mobile data drains battery but that's been happening for a while.

all I did to fix the reboot issues was format system and reflash rom+radio, and the build.prop and boom it works great.

oh and I've never found the need to reboot between flashing rom, gapps, apps2sd, etc, always do.everything in one go.
[Wildfire Android Development] zexcrazy:
Which build.prop u used? The latest one with kernel included?
[Wildfire Android Development] pan_pietrek:
OK, did a full wipe, formatted system and boot, flashed #23 plus the latest 3G fix. Booted up and 3G crashes were gone, but my phone kept loosing the signal when the screen was turning off. Then i enabled surf. dithering, rebooted and... my phone crashed just after establishing 3G. Hell... Maybe it's the buildbots messing it up? Could you share your local build?
[Wildfire Android Development] nhnt11:
no that one doesn't work for me, I use the first one with only the build.prop
[Wildfire Android Development] nhnt11:
latest fix does not work after reboot. I doubt there's any difference between the nightly and my local build in a way that the nightly is broken, but if it comes to it ill try to upload my build later. right now I'm not at home and battery is at 14%

edit - then again, it could be..... :confused:
[Wildfire Android Development] alangrig:
Well, I've replaced in build 23 build.prop and reflashed again and still 3g crashes system by bootloop. Strange. Reverted back to build 21 by clean install and new kernel works like a charms.

NHNT11 could you share your latest working build.prop please.
[Wildfire Android Development] pan_pietrek:
How come, that the fix doesn't work after reboot? Shouldnt it be persistent? It's flashed after all, right? Anyway, there was an issue with buildbots in the past, which caused nightly compilations to break and bootloop

while hackworks' local build was OK for him.
[Wildfire Android Development] nhnt11:
guys, here's something you need to understand - once you get the 3g crash, simply flashing the build.prop will NOT fix it as some persistent ccorruption or something seems to be happening. you need to reflash the nightly, the radio and the 3g fix to make it work again from my experience. my build.prop has nothing changed ffrom the one Arco posted.
[Wildfire Android Development] nhnt11:
I dunno, I just told you what I found after testing it. I can't do any digging either since I'm not at home. like I said, ill try and upload my build after I get home if this isn't resolved by then.
[Wildfire Android Development] pan_pietrek:
Oh, nhnt11! If you do upload your local build, could you please put your working build.prop in it as well? This will make it a no confusion-all-in-one package.
[Wildfire Android Development] zexcrazy:
Tried older build.prop and still same problems. I think that kernel is causing this somehow, because 4.1 works like a charm
[Wildfire Android Development] pan_pietrek:
I'm betting the bots.
[Wildfire Android Development] nhnt11:
here's a VERY wild guess - are u using setcpu? if so, uninstall it and see if anything happens.

also after some experimenting the 3g problem is back here, looks like you HAVE to revert to an older nightly to fix it. unfortunately my battery is critical, could someone please do a nandroid backup, CLEAN install older nightly and radio in one go, restore nandroid and 3g fix in one go, and tell me if it works?
[Wildfire Android Development] falkenbein:
I think it's a kernel problem. after the first start of the # 23 with 3G fix is the following message. "Legal system not responding"
[Wildfire Android Development] johi69:
same message after reflashing RC2 with full wipe
[Wildfire Android Development] pan_pietrek:
Which version of the 3G fix do you mean nhnt11? And no I did a full wipe and never had setcpu in any of the recent #20 series builds.
[Wildfire Android Development] Bi0haZarD:
Nightly build problems - probable solution

Guys...with different sorts of problems since #20/#21...

NOTE: ABSOLUTELY NO REBOOTS in between flashing individual zips!

-

Go to recovery

-

1)Fully wipe everything

2)Restore a previously backed up nandroid prior #19 where everything were smooth and working properly

3)Reboot Recovery (Do not reboot into CM7)

4)Flash #23 (this is a must! NO gapps) and/or dta2sd (if u are using it only)

5)ONLY NOW REBOOT.

6)TEST if everything works properly after 1st boot into CM7, if it does work properly, reboot again to confirm that after 2nd reboot everything just works.

7)If u still have radio related issues flash radio, repeat whole procedure from step 1) to step 5) but this time flash rom/dta2sd/

radio

as needed. (All in one go) then go to step 6)

Personally i'm using #23 with no issues (not using 3G/Data only 2G/wifi)

(nandroid backup #18 -> no wipe, flash #23 along with dta2sd)

Also note #23 new setting in Cyanogenmod settings -> Performance -> Allow purging of asets (new option)
[Wildfire Android Development] alangrig:
That's is the problem 3g gives system crash, even if build.prop is replaced with corrected one by acro inside .zip build #23. However after first clean flash #23 everything worked fine untill reboot, which causes system to crash unless 3g data is disabled. I've unlimited HSDPA data so I am real heavy HSDPA data user.

However performing the same trick for the builds 21 & 22 has no issues with 3g.
[Wildfire Android Development] fasix:
I would know how I can install DarkTremor APPS2SD in my wildire with CM7 nightly (without e with TOTAL WIPE)

thanks :D

Now I use RC2, but I'm downloading the last nightly :D
[Wildfire Android Development] Bi0haZarD:
http://xdaforums.com/showthread.php?t=925982
[Wildfire Android Development] zexcrazy:
Tried x500wm6 method, also no luck. Flashed #23 about 10 times in various ways and none of them work until I flash 4.1 kernel. With that, everything is back to normal.
[Wildfire Android Development] mishooo:
Ok so is #23 stable ?
[Wildfire Android Development] jim-bo:
That only applies to problems with 3g data connections causing boot loops. It doesn't apply, as far as I can see, to those of us who are having a problem with the radio dropping out completely for 2-3 seconds when the screen goes off.

Replication of this is easy, here, just make a call, put the phone to your ear, wait for the proximity sensor to kill the screen, and listen to your call die :(

For those interested in my findings, I've just spend an hour flashing, wiping, and testing. Here's the summary.

* complete wipe, format system, boot, data, sd_ext, cache, wipe dalvik cache and battery stats.

* flash n23 and the second 3g data fix zip

* boot

Data works perfectly, no reboots, every time screen goes off, libhtc_ril segfaults and radio loses contact with all network. Recovers in moments, but it is enough to kill a call.

* wipe again

* flash n23 and this time the first data fix zip

* boot

phone boot loops whenever it tries to get 3g connection

* reflash latest radio

* boot

results are now exactly as with second data fix, data is fine, screen-off kills radio.

* restore n18 from nandroid

* reflash radio

back to normal.

Basically, it seems that reflashing the radio is required after you get a 3g-data bootloop situation, but that either of the fixes posted will prevent this.

Now I just wish someone could work out what is causing the screen-off radio kill
[Wildfire Android Development] pan_pietrek:
A properly done ROM shouldn't cause such problems. These are just workarounds and will not fix the core issue. I'm investigating one possible reason of such behavior and will let you know about my findings.
[Wildfire Android Development] nhnt11:
It would be very helpful if someone with the signal problem could post a logcat of this. Just saying.

I'm uploading my local build for anyone who wants to try.

edit: the damn thing failed at 95%, for no apparent reason, and i'm a little busy right now to do it again, sorry.
[Wildfire Android Development] pan_pietrek:
Already did yesterday: http://pastebin.com/0FWKgmL6

The right part of the log starts from line 743.

Similiar issues have already been happening in previous builds of Cyanogen for different devices, heer's an intresting thread: http://xdaforums.com/showthread.php?t=988557
[Wildfire Android Development] nhnt11:
Flash this and see if the screen off signal problem is solved.... (I'm not responsible for anything that happens, do a nandroid)

edit: this has the build.prop fix too for good measure

edit2: i used the update script from my 3g fix package so it says "installing build.prop" so ignore that.
[Wildfire Android Development] jim-bo:
Thanks, flashing now
[Wildfire Android Development] falkenbein:
don´t work :-( same problem
[Wildfire Android Development] nhnt11:
damn.. so thats not it... i'll try doing some digging..
[Wildfire Android Development] falkenbein:
You're doing good work. I hope you make it soon. I have to wait patiently
[Wildfire Android Development] neoazrael:
The only issue is about screen rotation at home screen with programs it works well no network, data,reboot,3g issues have been detected in mycase

Edit:screen rotation works perfectly with launcher pro plus so no issue is left
[Wildfire Android Development] pan_pietrek:
Did you install it after making a full wipe? What's your radio version?
[Wildfire Android Development] nhnt11:
ummm... who are u talking to there???? :p
[Wildfire Android Development] neoazrael:
A

A few messages before i wrote how to install it radio version is 3.35.20.10 the latest one as i know
[Wildfire Android Development] jim-bo:
As reported, no luck.

I cleared the logcat buffers, and captured a log just covering from about a second before powering the screen off, through until the radio naturally reacquired a signal.

logcat http://pastebin.com/aiqjS1S7

logcat -b radio http://pastebin.com/Ens9dFXP

from the radio log, it seems to be doing a full reload of the SIM data, though I have no idea if that is normal for getting a radio lock or not.
[Wildfire Android Development] nhnt11:
What I don't get is why this is not happening to me. Calls are working just fine here. Can you check if you have the setting "Keep screen awake" or something like that in Settings->Call
[Wildfire Android Development] jim-bo:
didn't have that set, tried it, no change :(

But it isn't only while you're in a call, it is every time the screen goes off, it is only really a problem in calls, but it isn't related to the call itself.

Edit: just also tried disabling Wifi, 3g, and even all mobile data, so it is JUST GSM connected, but made no difference at all

I'm going to leave the phone on this image for a while, I have a headset here so I can still use it fine if anyone calls. :)

If you think of anything else for me to try, let me know.
[Wildfire Android Development] neoazrael:
Keep screen awake is unticked
[Wildfire Android Development] nhnt11:
All this leads me to think that maybe this IS a problem with the nightly build, maybe i'll try uploading my local build again (hopefully it works this time)
[Wildfire Android Development] arco68:
Here's another testfix with a different kernel. Please test.

If you already have got the 3G boot crash, there seems to not help just flashing fix. What seems to work fine for me is to fully wipe all, format all partitions, flash nightly and then flash fix before boot.
[Wildfire Android Development] daddyspud:
erm i come from cm7 rc2 i installed nightly 18 worked fine rebooted and then installed 23 worked fine at home went out on my motobike and was playin music and turned 3g on and bang continues bootloops

i seen a few days back a 3g zip am i right to asume this will fix the error

i thought it would ov been fixed and but in the 23 nighlt ow well

will c how it goes
[Wildfire Android Development] nhnt11:
Here's my local build, if anybody wants:

http://www.mediafire.com/?ji1rh9p80dcpjiw

edit: this includes the build.prop fix. I have no screen off signal issues with this build.

To test properly, do the following.

1. Format system

2. Flash ROM. Flash gapps, apps2sd, whatever. DO NOT REBOOT DURING THIS PROCESS OR AFTER IT.

3. Flash radio. NOW reboot.
[Wildfire Android Development] jim-bo:
Just flashed... 3g seems fine with this one, but then, 3g seemed fine to me with your previous two as well.

Still getting the radio drop out when the screen goes off though, no change there
[Wildfire Android Development] alangrig:
Thanx body (NHNT11), downloading and gonna test out this evening!!!
[Wildfire Android Development] f0xy:
Guys, I've been using my wildfire today getting the 3g issue but no boot loop. Just the data goes off.

I've noticed if I go into, *#*#4636#*#*. into phone info change preferred network type and change it back the 3g comes back on?

Can this help solve your problem?
[Wildfire Android Development] doomed151:
Never had any problems with builds using the new kernel.

Maybe it's because I replaced the build.prop file with this one in every build flashed: http://xdaforums.com/showpost.php?p=12115005&postcount=3396

I don't know why but I reattached it. I guess you guys should replace the build.prop in later builds with this to avoid further problems unless someone verified that it's fixed.

The only thing that still bothers me is the screen on/off animations, they still refuse to work consistently.

About the 3G bug being persistent, how is that even possible?

Edit: Hmm, never tried mobile data with the newer builds as I don't have a data plan going on currently.
[Wildfire Android Development] nhnt11:
Screen on/off animations are now completely disabled. the menu settings are just dummies.

the 3G bug seems to involve some sort of buffer corruption or something that is getting written to persistant memory somewhere. Even flashing a stock rom does not seem to fix it. Only way to fix it currently is to flash rom and radio in one go after formatting system. (arco said full wipe but that isnt necessary as i've seen)
[Wildfire Android Development] doomed151:
Somehow, doing that "resets" the config for the radio and everything goes back to normal?

Man, this is a unique problem. Does restoring a previously working nandroid backup fix it?
[Wildfire Android Development] nhnt11:
Nope. if you restore a previous nandroid backup, you still need to reflash radio without rebooting for it to work.
[Wildfire Android Development] f0xy:
hmmm time to flash ruu? And just root and use stable nightly for now? :)
[Wildfire Android Development] nhnt11:
Not a bad idea. I was thinking of switching to a sense rom for 2 days just to enjoy the "freshness" of it (even though sense sucks imo compared to CM7). :D
[Wildfire Android Development] f0xy:
True true but you can't beat a working phone! Ha
[Wildfire Android Development] patrask:
where do I get the radio? ..
[Wildfire Android Development] :
what a nightmare today ive had after flashing from 18 to 23,

Bootloops after reboot even using 4.1 kernal and reflashing radio.

in the end not even a clockwork recovery image could save me.

Solution was to wipe and start a fresh with nightly 18+4.1 kernal.

over all very happy this happened as my old install of nightly 18 seemed really

slow and jerky to open menus etc... maybe from the fact id just been updating on top of each other!

Im sticking with 18 now till stable, is better the devil you know!
[Wildfire Android Development] 3xeno:
Available here:

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

On another topic, it is really unfortunate the new kernel (Or is the lib file?) messed this up. I was really loving the short time I had there with the new kernel. It provided a far more smoother experience, which, somehow, I am unable to get anymore with others.

Should just be a matter of time though. :)
[Wildfire Android Development] pan_pietrek:
Aaaaaand... No go. I've just flashed nhnt11's private build and the screen off/signal off problem persists. It wasn't a full wipe, what I did was: Format system/boot, flash the ROM, flash gapps, flash dta2sd, finally the radio. Lastly wipe dalvik cache and reboot. Everything in one go.

This rules buildbots out I guess.
[Wildfire Android Development] nhnt11:
one final thing.... can you see if this happens with 2g only mode? (if you're not already on 2g only)
[Wildfire Android Development] pan_pietrek:
Already on 2G. Bummer.
[Wildfire Android Development] daddyspud:
well i did a complete reinstall of 18 to 23 and tryed the 3g fix but as soon as i get a 3g connection reboot

ow well lol

so my question is which nighlty has the ability to use the cm7 cpu setting it 18 or older?????
[Wildfire Android Development] nhnt11:
only the ones with the 3g problem. (21 and newer)
[Wildfire Android Development] daddyspud:
cheers buddy thanks for quick reply
[Wildfire Android Development] NickHu:
Somebody said at some point something about setting the network provider manually rather than automatic?

I don't know though, and I'm not really willing to try these "broken" nightlies - I need my phone :P
[Wildfire Android Development] Bi0haZarD:
Bro im since this morning on 2G/wifi/no data no bootloops and i had 10-15 calls...now its 20:50 night....battery life seems better and overall experience is really smooth

Sent from my HTC Wildfire

Running Gingerbread 2.3.3

Cyanogenmod 7
[Wildfire Android Development] zexcrazy:
I've been decided to give up on this and wait for new nightly, but devil inside me doesnt give me a break so i will try to make it work again. If it works for someone, then it should for everyone.

One more thing. Did anyone on nightly 23 with kernel 4.1 tried usb storage? Doesnt seem to work for me.
[Wildfire Android Development] alangrig:
Uploaded build 23 works like a charm, no 3g issue!
[Wildfire Android Development] Michealtbh:
Even after reboot? Did you flash the fix too?
[Wildfire Android Development] nhnt11:
you mean my local build that i uploaded? if so, great. technically if you do the same thing with a normal nightly (i mean instructions that i gave in the same post) except u flash the 3g fix as well, it shd work fine.

usb will not work on new builds with the old kernel due to new vendor config.
[Wildfire Android Development] pan_pietrek:
Offtop, for those of you who need a nice, build summarized list of changes in cyanogenmod: http://cm-nightlies.appspot.com/?device=buzz
[Wildfire Android Development] makaaaa:
site doesnt work for me...
[Wildfire Android Development] melvinchng:
built 23 is up. I'll try it now.
[Wildfire Android Development] zexcrazy:
Build 23 is from yesterday.
[Wildfire Android Development] melvinchng:
oh man, i am outdated =S
[Wildfire Android Development] doomed151:
You don't really need to tell us you're getting a new build to try out.

A better thing would be reporting after you tried out the build.
[Wildfire Android Development] melvinchng:
i feel that #21 much smoother than #23. Anyone has this feelings?
[Wildfire Android Development] nhnt11:
well, as everyone is a bit prepoccupied with the radio issues, nobody has really been worried about smoothness.