yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] doomed151:
Something's wrong with the mirror network, when I tried to get #5 I get this:

Traceback (most recent call last):
File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/__init__.py", line 515, in __call__
handler.get(*groups)
File "/base/data/home/apps/cmbalance/2.347054236333167992/pages/get.py", line 16, in get
url = getDownloadURL(device, filename)
File "/base/data/home/apps/cmbalance/2.347054236333167992/lib/download.py", line 18, in getDownloadURL
mirror = getNextMirror(file.type + "/" + file.path)
File "/base/data/home/apps/cmbalance/2.347054236333167992/lib/download.py", line 43, in getNextMirror
result = urlfetch.fetch(url)
File "/base/python_runtime/python_lib/versions/1/google/appengine/api/urlfetch.py", line 241, in fetch
return rpc.get_result()
File "/base/python_runtime/python_lib/versions/1/google/appengine/api/apiproxy_stub_map.py", line 530, in get_result
return self.__get_result_hook(self)
File "/base/python_runtime/python_lib/versions/1/google/appengine/api/urlfetch.py", line 331, in _get_fetch_result
raise DownloadError(str(err))
DownloadError: ApplicationError: 5

Seems like the load balancing is having problems?

EDIT: Meanwhile, I'll just use this mirror: http://goo-inside.me/cm6/buzz/nightly/ (Ignore the URL, it's actually CM7)
[Wildfire Android Development] nhnt11:
Hey,

I'm getting a weird error - all of a sudden sound randomly stopped working. This happened twice. Both times phone auto-rebooted and sound worked fine after that. (Sound including mic).

Happened once with nightly #4, then I switched back to froyo, then decided to try again with nightly #0, after which it happened again.

On nightly #4, gStrings tuner didnt recognize my mic but I thought it was a problem with the app... then the phone app crashed when I got a call (i couldnt hear anything after picking up) (embarrassing lol)

On nightly #0 I was using the camera and the shutter sound stopped... then I tried to change my ringtone when it rebooted.

I don't know how to get a logcat since it rebooted immediately. (I'll post one after I learn how to get it)
[Wildfire Android Development] doomed151:
Seems like apps using GPS still force closes in #5, back to #0.
[Wildfire Android Development] 19martin83:
And did it work after you wiped everything?
[Wildfire Android Development] mac4rfree:
any improvements in #5???
[Wildfire Android Development] pinkchicken:
yeh its great hes doing a gingerbread for wildfire but come on if ur gonna briing one out make it so its not fail. like all apps in english would be a awsome start as there in some other laugauge.
[Wildfire Android Development] pl0ppy:
Hey guys, is 26 stable enough for everyday usage? I don't have a data plan so data doesn't matter. I am currently on nightly 18 because of the comments above.
[Wildfire Android Development] Formiak:
Installed just #26 and tested phone , there is no drop call bug .I tested it on 40 seconds call so i think it has gone.
[Wildfire Android Development] Wout2426:
Wiped everything

Flashed #26

Flahed Gapps

Flashed radio

Reboot.

3G issue is solved

GPS workes

No issue with signal loss when screen is off

Fine so far !
[Wildfire Android Development] Formiak:
I didn't flash radio and everything is well too ;-) and gps is working
[Wildfire Android Development] patrask:
So in #26 we're back to HCDR kernel?
[Wildfire Android Development] 3xeno:
Agreed. All seems perfect. Just made a call as well, and no issues. Can't test 3G because 3G signals are not available at my home, only college. 2G works fine :/

No, it uses Arco's nFINITY Kernel, a new version though.
[Wildfire Android Development] rugal316:
Im still getting the signal dropping issue on 26, do i have to flash the newest radio as well?
[Wildfire Android Development] Tetractys:
Flashed #26 over #25 all is ok. Really smooth.

edit: No need to re-flash new radio 13.55.55.24H_3.35.20.10 if this was upgraded before.
[Wildfire Android Development] alangrig:
Well there is no call drop bug even on build #25, if you use corrected build.prop provided by arco. Running fine under smartass and min 19 and max 768 Mhz. No freeze, no reboots. Stable for everyday use. Hit 5.25 Mfloops in linpack. Very fast!!!
[Wildfire Android Development] kai666:
Installed no.26, gps problem seems solved, but now it says my wifi is disabled

anyone else finding this? any solutions?

It scans, finds and drops straight away
[Wildfire Android Development] wildfire_paulie:
I'm on #25 with none of the bugs above.

Never flashed the new radio.

Only issue is that i keep on loosing accounts of facebook and twitter at reboot. Did anybody had this issue before?

I'll try #26 and new radio.

... uhm, can anybody get me the link to that radio zip?
[Wildfire Android Development] mn78jag:
wildpuzzle thread.
[Wildfire Android Development] Tetractys:
http://rom.tat.tw/wildfire/wildpuzzlerom/radio/
[Wildfire Android Development] Michealtbh:
Facebook account thing happens to me too, think it's because Im using DTa2sd
[Wildfire Android Development] wildfire_paulie:
But i am not. So it is not related to dark tremor's script.
[Wildfire Android Development] zexcrazy:
I'm still having 3g and call drop issues, no matter what I do. For a past few days all I do is reflashing nightlies in all ways and nine of them work. And as soon as I flash Jacob's kernel everything is fine. No drooped calls, no signal loss, 3g is working fine. Maybe someone should take a look into that kernel, really.
[Wildfire Android Development] metapolis:
Phone issue: Tried to call someone, after few seconds the connection disappear. The phone can not find any operator for few seconds, than it connect with my operator. Tried the 3g-fix but it does not work. Swith back to ImProOs
[Wildfire Android Development] MariusWildfire:
so I flashed #26. everything works so far. but when the screen turns of, the 3G connection is lost.. how can I solve this?!
[Wildfire Android Development] nhnt11:
does your carrier support simultaneous voice/data?
[Wildfire Android Development] f0xy:
who's currently doing the nightlies for buzz?
[Wildfire Android Development] nhnt11:
the teamdouche buildbots :D :p
[Wildfire Android Development] zexcrazy:
Can someone with 3g and signal loss issues confirm that flashing Jacobs kernel solves them, please?
[Wildfire Android Development] nhnt11:
hmm, i just looked up telenor, and they DO support SVD. I need to get my hands on a vodafone/airtel sim...
[Wildfire Android Development] zexcrazy:
Sorry mate didn't catch your question, I'm very pissed with this problems.

Anyway I don't think they do, at least at Serbia, because as soon as I make a call the data icon disappears. Maybe I'm wrong.
[Wildfire Android Development] nhnt11:
oh then i guess that's not it.... :(

i'm going to try with a different sim as soon as i can get my hands on one anyway to see if i can get anything to happen.
[Wildfire Android Development] falkenbein:
For me #26 still Signal lost when screen of. Back to #18

Sent from my HTC Wildfire
[Wildfire Android Development] falkenbein:
Same for me.

Sent from my HTC Wildfire
[Wildfire Android Development] fasix:
what is the last nightly version without 3G bug?

my wildfire with #26 reboots when I switch on . :(

I use the lastest Gapps, DTapps2sd and the lastest RADIO.
[Wildfire Android Development] -Howard-:
Moved to #26 and i have had no problems ot one.. no loss of signal or 3g problems..ect :S I wonder whats causing it for some people and not others? :/
[Wildfire Android Development] zexcrazy:
Well my phone is locked to Telenor, so no help from me. But, here is this, maybe it will help.

Besides Jacob's kernel solves issues I noticed few more things.

1. Wether data is on or off call will drop as soon as screen turns off. If I make a call and turn on speakerphone call will naturally last longer (till screen goes off).

2. If I turn off data I would be able to turn it on. But if data is turned on when screen goes off it will not reconect when signal is back. In matter a fact its imposible to turn it on again. Need to switch to 2G only, then back, and then it is possible to have 3g again.

3. All this issues are happening and when I use 2g only.

So in my oppinion it is related to kernel and they way how it tries to reduce battery usage when screen is off by reducing cell usage and communication with radio.
[Wildfire Android Development] rahulkrathod:
isnt it the edge class that our phones supports? perhaps when you dont have 3g signal, you are automatically dropped to edge. and wildfire has class B edge, which doesnt allow simultaneous voice and data. class A does.
[Wildfire Android Development] fasix:
what is the last nightly version (previous of the #26) without 3G bug?

my wildfire with #26 reboots when I switch on 3G.

I use the lastest Gapps, DTapps2sd and the lastest RADIO.
[Wildfire Android Development] nhnt11:
I was able to use simultaneous voice/data when i was on vodafone, on edge. strange.

edit: afaik both carrier and phone have to support it.
[Wildfire Android Development] wildfire_paulie:
Flashed #26 over #25 and got bootloop.

Restored #25 with nandroid, and again, bootloop (wtf?)

Re-flashed latest radio and my build #25 is back, working again.

The battery is draining fast, after 20 minutes i'm already at 90%,

from full charge.

Not really making sense
[Wildfire Android Development] DjoeN:
I tested this myself awhile ago and just today to verify your post.

I'm able to call, put on speaker, go to my homescreen and surf the internet, check my mail and read a few newsfeeds while talking to my wife and go back to my phone cal screen without losing the voice connection, Also no 3G issue here when when switching between 2G/3G/WiFi (No 3G reception anyway), no reboots or FC while calling (called for 10 minutes and get called for 10 minutes)

I'm on Mobile Vikings (Belgium) that uses the BASE network and on EDGE (no 3G as stated above in my regio)
[Wildfire Android Development] wuud:
has #26 a better battery usage than #22? #22 was empying my battery way faster than any other nightly, so I went back to #15...
[Wildfire Android Development] nhnt11:
This leads me to think that this IS a network related thing. Unfortunately my parents are refusing to lend me their SIMs to test it out :(

So I have to get a friend's somehow, but that might not be possible anytime soon... :(
[Wildfire Android Development] DjoeN:
Battery drains empty after 2 days of normal use, it drains empty within 1 day on heavy usage (play a few mp3's, surf regular the internet, flash a new rom and backup through titanium backup and making a nandroid, check the market, make a few calls and recieve a few calls)
[Wildfire Android Development] jim-bo:
Not sure how this can be a network issue?

Fundamentally, to rule out everything else, I can test by disabling wifi, 3g and 2g, so the phone only has a GSM connection (stable four bars of signal).

I can then hit the power button to turn the screen off, and immediately watch the radio lose it's connection to the cell. 100% repeatable, every time. The signal is back in 3-4 seconds, and everything is good again. If I switch on the phone quickly enough, you can see the no-signal error and no bars, as well as watching it in logcat.

Alternatively, to rule out anything call related, using a headset, or speakerphone mode, I can make or receive a call (tested both), and keep it alive indefinitely, provided I keep the screen awake, and data continues to work fine (tested 3g and wifi, didn't bother with 2g).

The only thing that fails is that when the screen goes off, so does the cellular connection. Every time. Immediately.
[Wildfire Android Development] nhnt11:
not a problem with signal/network being busy/etc, a problem based on the type of network your carrier uses (the radio bands, etc etc)
[Wildfire Android Development] Phinxy:
Flashed #26 over #21 (full wipe), latest radio and kenel 2.6.32.33-nFinity. Works perfectly well.
[Wildfire Android Development] volki2004:
What means 13.55.55.24U_3.35.20.10 radio, whiсh I have?
[Wildfire Android Development] zexcrazy:
Ok, so if it is carrier and network issue, how come that in earlier builds this haven't been a problem. It all started with build #21, so changes in code made from that point are causing this. Only obvious thing that is changed is kernel. Not to mention, as I stated many times before with old kernel everything is fine. But as with old kernel USB storage is not working this is not a solution.

I like new kernel, its smooth and definetly more stable but its useless for me and many of other people with this issues, at the moment.
[Wildfire Android Development] nhnt11:
its definitely something in the kernel, what I meant was, the bug might be occuring based on network types.
[Wildfire Android Development] mn78jag:
Mms doesn't work for me.

Nightly 26. 3 sweden
[Wildfire Android Development] rugal316:
sorry to be a pain guys, can someone point me in the direction to obtain the 2.6.32.32-nFinity #1 kernel please, thanks
[Wildfire Android Development] arco68:
Those with call drop issues, can you try to flash attached zip.

Am I right in that this only happens when screen goes off?
[Wildfire Android Development] prakka:
Doesnt work, flashed not right after rom install after an used rom that already was installed nightyly 26. And you are right it is only at the balck screen.
[Wildfire Android Development] pan_pietrek:
Formatted boot, system, wiped dalvik and then flashed #26 + your patch. Still no joy. And it only happens when the screen goes off.
[Wildfire Android Development] falkenbein:
Same for me. Dont work

Sent from my HTC Wildfire
[Wildfire Android Development] :
I can confirm this. Same operator and country. Not a failure with the operator as my girlfriend can send MMS fine, with the same one.

I have only tried sending MMS, not receiving. The messages app just says "Sending", but nothing happens. I guess the APNs haven't changed, atleast they look alright. I haven't compared filesizes though. Tell me if someone wants a logcat or something.

Otherwise everything seems to be alright with #26, atleast for me. I might find something later though, haven't played with the phone that much today.
[Wildfire Android Development] arco68:
Try this. Contains a different ril library.
[Wildfire Android Development] :
Still the same thing, just keep saying "Sending".

Will check the apns and so forth a bit later, gonna eat and watch a movie now :)
[Wildfire Android Development] arco68:
It was for the drop call issue. :) MMS must be something different.
[Wildfire Android Development] D3VICE:
I'm planning to use this rom again.

How stable is #26?

Any issues?
[Wildfire Android Development] NickHu:
Can you not read..?
[Wildfire Android Development] D3VICE:
Sorry for not having the sheer time to go through 10 pages trying to find what I need.

If you can read, and have time too, is it that hard just to say if it is stable or not?

I'm in kind a hurry.
[Wildfire Android Development] nhnt11:
you shouldnt be flashing nightlies if you're in a hurry, a working out of date phone is better than a non-working but up to date phone.
[Wildfire Android Development] D3VICE:
Its not like I will be needing my phone for something important.

I need to leave in like 5 minutes, and I wanted to try it, to see if it had improved from the previous nightlies.
[Wildfire Android Development] btrst:
seems like 26 bootloops whenever screen turns off. on #25 it was same too but i made it GSM only and no problems so far.
[Wildfire Android Development] :
Aha, I tried it anyways :p
[Wildfire Android Development] D3VICE:
Thank you.
[Wildfire Android Development] prakka:
Tried it thought it fixed the problem but after a few times trying the Connection broke again.
[Wildfire Android Development] zexcrazy:
Still the same for me.
[Wildfire Android Development] djdevine2:
Got a problem, did a clean install of 26 (fancied a fresh start!) but my sharing function doesn't work. When you take a photo and press share the app just crashes! Not had this before
[Wildfire Android Development] rklomp:
Fixed the 3g problem bij just upgrading to #26 and than flashing the latest radio
[Wildfire Android Development] fasix:
why is necessary flashing the lastest radio after flashing the #26 ?
[Wildfire Android Development] f0xy:
Lol the mentality of some people!

I had 3g issues and signal dropped when screen off with nightly 21.

But after wiping everything and wiping dalvik in between flashing rom and radio this worked.

Unfortunately didn't check calls when signal was dropping.

Edit it just dropped lol
[Wildfire Android Development] arco68:
I'm totally baffled by this. Been having no problems whatsoever for a whole day. Then I messed around a bit with kernels and ril libraries, and suddenly got a reboot on 3G. So wiped everything and flashed #26 again. But still it rebooted on 3G data, every time. So I immediately switched to airplane mode on next boot, before 3G activated, went into Rom manager and flashed radio. And so far 3G is fine. :confused: Arrghh, what a mystery this is.... :mad:
[Wildfire Android Development] f0xy:
Can't wait for it all to work with this smooth new kernel :)
[Wildfire Android Development] zexcrazy:
Seems to me that everyone of us with this issue have a bit different "simptoms".

Me for example never had reboot on 3G. It just disappears along with signal when screen goes off and after few seconds signal is back but i cant get 3G or any kind of data connection till I switch to 2G only or to airplane mode and then to 3G again. Or if I'm on 2G and screen goes off need to switch to 3G or airplane and then switch back to 2G. Also one more thing if data connection is on and phone loose signal due too bad reception as soon as signal is back data is back too.

So this is related somehow to screen off only, at least in my case. But weird thing is that i never had phone reboot on 3G which few people reported. :confused::confused::confused:
[Wildfire Android Development] btrst:
i wonder if this new kernel works on sense based roms.
[Wildfire Android Development] arco68:
You will have no USB support if installing it on a sense rom.
[Wildfire Android Development] arco68:
Ok, here's another test kernel for the dropped call problem. I removed some patches from it, too see if they might be causing it. If problem is there still, I'm afraid I have to start all over again with the kernel.

http://www.multiupload.com/UVJNI975K9
[Wildfire Android Development] zexcrazy:
Thanks, but still the same. Screen off -> everything off.
[Wildfire Android Development] arco68:
Anyone can provide some full logs?

Output of logcat, radio and kernel after it looses connection?

logcat > logcat.txt

logcat -b radio > radiolog.txt

dmesg > kernel.txt
[Wildfire Android Development] zexcrazy:
Here you go, hope i did it right. Didnt manage to catch kernel log, gives me some errors
[Wildfire Android Development] arco68:
Thanks. I see some errors in the radio log, that I don't have in mine.

Can you check that those files exist, and that you can write to them?

For example, echo 1 /sys/camera_led_status/led_ril_status
[Wildfire Android Development] arco68:
Actually, forget that. I have those errors too. Just had to initiate a call for them to appear in the log.

A kernel log would be appreciated.
[Wildfire Android Development] btrst:
i had 3g-screen-off bug and here is what i did

flash #25 from scratch

turn on gsm only

flash #26 over it without wiping anything

flash newest radio before first boot

boot and turn off gsm only

it worked for me no problems with 3g so far. maybe its just luck:p
[Wildfire Android Development] zexcrazy:
Ok. Im available for next few hours so just post if you need anything elese. Would like to help to solve this.
[Wildfire Android Development] zexcrazy:
Cant get it. Returns only empty file.
[Wildfire Android Development] zexcrazy:
Got it.

10char
[Wildfire Android Development] arco68:
Alriiighty.. I think I might be on to something here. Is it correct that you don't have an Atmel panel? Can you check on the H-BOOT screen what it says?
[Wildfire Android Development] f0xy:
Definitely with the screen off state! It just as if the phone dies :)
[Wildfire Android Development] zexcrazy:
Yep. Its SYN3KY_01
[Wildfire Android Development] f0xy:
I've got atmel with screen off bug
[Wildfire Android Development] arco68:
Darn it! :(
[Wildfire Android Development] nhnt11:
talking about weirdness, this just happened to me - yesterday night, my battery was at 100%. I listened to some music and went tto sleep. (still 100%, around 1.30am). this morning at around 7.30, my phone was dead. 0%. this has never happened to mme before... normally I lose around 2-5% overnight.

oh, and it was on 2g only with data off.
[Wildfire Android Development] nhnt11:
I've been clearing battery stats every time I reflash.... Most of the time I lose around 5 or maybe 6% overnight. Ages ago on CM6/Wildpuzzle I used to lose around 2 or maybe 3%, but I've gotten used to that now... but I've never EVER had my battery drain completely like this in just 6 hours, without using it at all.
[Wildfire Android Development] arco68:
Yeah, that's strange. I'm putting back original battery driver, together with some other changes. Will upload here when done.
[Wildfire Android Development] ariebart:
Flashed kernel 4.1 solved the network drop bug for me.

Only it messed up my wifi.

Personally I prefer a stable call envi, so 4.1 is a good temporary solution
[Wildfire Android Development] nhnt11:
Alright, thank you... By the way, I thought it was just my phone since nobody else reported this, but if I charge to 100%, then it stays at 100% for an abnormally long time (maybe even 2 hours of continuous use) and then starts drastically decreasing after that. But, if I charge to around 90 or something, it drains much more normally. Any ideas?
[Wildfire Android Development] zexcrazy:
But you will not be able to mount usb storage with 4.1 kernel.
[Wildfire Android Development] ariebart:
I didn't test usb storage yet. But at last it is nice if a phone can make phonecalls :-)
[Wildfire Android Development] arco68:
It's quite normal I think. It does the same for me too, and on my Tattoo as well. From 100-90 always takes longer than 90-80.
[Wildfire Android Development] nhnt11:
Nono, it drains extremely fast (relatively) from 99-0, but it stays at 100 for a very long time.
[Wildfire Android Development] sevarii:
Someone tested #28 ? I have to go to school and have not much time...
[Wildfire Android Development] arco68:
It stays a long time at 100 for me too. I read an explanation somewhere about why it does that, but can't remember the technical details about it, or where I read it. Something to do with how the battery is constructed and how it's charged I think.
[Wildfire Android Development] nhnt11:
Hmm alright, I asked because this has been happening to me only since recently, didn't use to happen with the older nightlies and back when I was using CM6 either... these days battery life is very erratic and unreliable (not BAD battery life, just not consistent)
[Wildfire Android Development] arco68:
Test kernel, as promised. Changes are in the commit log on github.

http://www.multiupload.com/KSBBO9NJXH
[Wildfire Android Development] alangrig:
Build #27, battery drained down to 59% in 2 hours. Never has happened before. I don't think it's relates to my settings under CPU governer:smartass min 19 and Max 768, always and no one freeze has ever happened. Call drop has incurred to me as well at 40th second. Gonna try your test kernel. Thanx lots!!!
[Wildfire Android Development] nhnt11:
Flashed it, can't say anything yet but I'll tell you if the battery problem has improved. Obviously I can't comment on the signal problem since I've never had it.
[Wildfire Android Development] volki2004:
What means 13.55.55.24U_3.35.20.10 radio, whiсh I have?

There is new or old radio?
[Wildfire Android Development] DjoeN:
Pulled out my Wildfire from my power outlet (100%), drove to my work, (45 minutes) took out my wildfire, battery is @ 16%, didn't do a thing with it.

(Nightly 26)

Gonne update to #28 with the new test kernel.

[EDIT]: This happended 1 time before on an earlier build, only happened 1 time, I'm not gonna test it, but i bet once i recharge, it will not happen again, just like the previeous time.