Related
I know, I'm supposed to search but I wasn't getting anywhere....
My device (Originally AT&T Tilt)
Now running Dutty WM6.1 WWE 4/29/08 (phone suggests.)
Radio 1.64.08.21
Location NYC
ISSUES:
Internet waaaaaaaay too slow. Never had a problem before.
The 3G (square box) is present and 3g over signal.
Signal- I average 2 to 3 bars TOPS
prior it used to be full
Can someone suggest anything?! Downloading Cab files is slow and or it freezes. My Youtubeplayer.cab doesn't even work anymore because of this problem.
Also...prior to using the Rom..my phone hates the Hollywood/ Beverly Hills area which is my second home.
Thanks in advance.
TheNotSoGeekyGirlAfterAll!
Just thought of something else... why does my touch keyboard and touch keypad stop working after about 10 times?
What's going on??????? I love the Rom but damn too many problems with my device.
DAI500 said:
I know, I'm supposed to search but I wasn't getting anywhere....
My device (Originally AT&T Tilt)
Now running Dutty WM6.1 WWE 4/29/08 (phone suggests.)
Radio 1.64.08.21
Location NYC
ISSUES:
Internet waaaaaaaay too slow. Never had a problem before.
The 3G (square box) is present and 3g over signal.
Signal- I average 2 to 3 bars TOPS
prior it used to be full
Can someone suggest anything?! Downloading Cab files is slow and or it freezes. My Youtubeplayer.cab doesn't even work anymore because of this problem.
Also...prior to using the Rom..my phone hates the Hollywood/ Beverly Hills area which is my second home.
Thanks in advance.
TheNotSoGeekyGirlAfterAll!
Just thought of something else... why does my touch keyboard and touch keypad stop working after about 10 times?
What's going on??????? I love the Rom but damn too many problems with my device.
Click to expand...
Click to collapse
1st put on some flame retardant, 2nd you should try duttys thread, not start a new one, how long have you been running this rom, did you hard reset after the first flash, have you tried to reflash, have you tried a different radio, radios make a huge difference base on location, many radio threads out there, and last if it has to many bugs try another rom, i have used this rom and i love it.
lupe
overhaulengines said:
1st put on some flame retardant, 2nd you should try duttys thread, not start a new one, how long have you been running this rom, did you hard reset after the first flash, have you tried to reflash, have you tried a different radio, radios make a huge difference base on location, many radio threads out there, and last if it has to many bugs try another rom, i have used this rom and i love it.
lupe
Click to expand...
Click to collapse
Minus the rudeness, you actually helped because I didn't know if it was the rom or radio. And for the record I did search for my specific problem using keywords. I'll try changing the radio because I can connect to the internet..its just edge is faster than my dumb phone. If all else fails, Ill sell the crap.
Thanks for your assistance.
DAI500 said:
Minus the rudeness, you actually helped because I didn't know if it was the rom or radio. And for the record I did search for my specific problem using keywords. I'll try changing the radio because I can connect to the internet..its just edge is faster than my dumb phone. If all else fails, Ill sell the crap.
Thanks for your assistance.
Click to expand...
Click to collapse
He wasn't being rude, you should post this in the thread for dutty's rom. My guess normally would be that you don't have 3G turned on, rather than a radio or a rom issue, as i remember several of dutty's roms do not have 3g enabled by default. bit apparently you're getting a 3G signal. Have you tried other roms to be sure it's somethign rom specific and not your network? In the future post your questions in the appropriate thread to TRY to reduce the clutter in the forum. Also, it is the xda policy, so there's another reason to do it.
DAI500 said:
Minus the rudeness, you actually helped because I didn't know if it was the rom or radio. And for the record I did search for my specific problem using keywords. I'll try changing the radio because I can connect to the internet..its just edge is faster than my dumb phone. If all else fails, Ill sell the crap.
Thanks for your assistance.
Click to expand...
Click to collapse
no rudeness, thats why there is a smile, like this one, search ultimate radio, and you will find alltheways radio thread with all kinds of radios, good luck
Lupe
So far my Fuze is amazing, I love it but Im having issues with it and I want to know what I can do to fix these issues.
1) I can't get my phone to go into Vibrate only... I will select it from the list but it just makes the phone silent!
2) My ringtone stops working as in if I call my phone, it only vibrates but my ringtone does not play. Sometimes it does, but lately it doesn't at all and I've checked my settings tons & tons of times. My notification sounds all play perfectly fine.
3) Backlight. If I turn off the backlight sensor/auto management of the backlight and keep the brightness fully cranked or at any setting, once I turn the screen off and turn it back on (just pressing the power button), my screen stays dim unless I go into Power and just tap where my brightness setting is!
Also, is there anyway to for example if Im reading a text message in Portrait mode and I slide open my keyboard to reply to just switch the orientation instead of having to open the message up again?
Thanks
I forgot to mention, Im using RRE's ROM. Im coming from a Samsung Jack so I know how to change things, etc. in Windows Mobile.
RJ45 said:
I forgot to mention, Im using RRE's ROM. Im coming from a Samsung Jack so I know how to change things, etc. in Windows Mobile.
Click to expand...
Click to collapse
Which RRE ROM version are you using? 4.4.5 SE ?
I believe its the one before 4.4.5
How can I check? I didn't flash it myself, the seller I bough it from flashed it for me before he sent it out.
RJ45 said:
I believe its the one before 4.4.5
How can I check? I didn't flash it myself, the seller I bough it from flashed it for me before he sent it out.
Click to expand...
Click to collapse
I have flashed every RRE version that Arup has released and have not once had any of the issues you have noted except the time I had a bad flash. My suggestion to you is to read this thread http://forum.xda-developers.com/showthread.php?t=448008 and fallow the directions completely and flash the newest version of RRE. I would however go ahead and flash the original official AT&T ROM first just to make sure you don't have any bad blocks. good luck and if you need any help send me a PM.
I was thinking of flashing to the newwest RRE ROM anyways, so I will give it a shot and see if that solves my issues.
Where can I find the original AT&T ROM? Im not on AT&T, Im on Fido in Canada (I know that wouldn't matter, just mentioning)
RJ45 said:
I was thinking of flashing to the newwest RRE ROM anyways, so I will give it a shot and see if that solves my issues.
Where can I find the original AT&T ROM? Im not on AT&T, Im on Fido in Canada (I know that wouldn't matter, just mentioning)
Click to expand...
Click to collapse
I thought you were on AT&T. You might want to check your radio version before flashing the AT&T's official ROM. official shipped ROMs usually contain a radio also. if your buddy flashed a different radio onto the device you will lose that radio version and be left with the AT&T stock radio. your radio version should match the one in my signature if it's the stock AT&T radio.
Whats the best/easiest way to check what radio version I have? Also whats the difference in having different radios?
Thanks for all your help!
RJ45 said:
Whats the best/easiest way to check what radio version I have? Also whats the difference in having different radios?
Thanks for all your help!
Click to expand...
Click to collapse
The radio is what is responsible for your signal. different radios will have different signal strength. To see what radio version you have go to start\settings\system\Device Information
My radio version is 1.10.OliNex.
Does that sound right? Which Radio do you reccomend? Im just at work right now and Im gonna flash it when I get home.
RJ45 said:
My radio version is 1.10.OliNex.
Does that sound right? Which Radio do you reccomend? Im just at work right now and Im gonna flash it when I
get home.
Click to expand...
Click to collapse
I would probably try and keep the radio version you have on the device currently. I can't really suggest one for you. You have to take a look at the radios listed in the touch pro wiki for your country and test them all out to see which on works best in your area. If you get a good signal and good data transfers using your current radio I would just stick with that one for a while.
Sounds good. Thanks! I will let you know how the flash goes and if that fixes my issues.
RJ45 said:
Sounds good. Thanks! I will let you know how the flash goes and if that fixes my issues.
Click to expand...
Click to collapse
Good luck!
I have a TON of these 37mb files on my SD card. They are all *.bins. What are they?
Anyone.....
sounds like a crash dump from a debug version of a radio app.
Sent from my Nexus S using XDA App
There are literally like 100 of them. The dates and and times are Xmas and every five minutes.
this also happened to me, but yesterday. do you have the app tunein radio? i think that may be the problem.
Nope....
jaker.the.skater said:
this also happened to me, but yesterday. do you have the app tunein radio? i think that may be the problem.
Click to expand...
Click to collapse
Sent from my Nexus S using Tapatalk
well ok. nevermind then haha
hah2110 said:
I have a TON of these 37mb files on my SD card. They are all *.bins. What are they?
Click to expand...
Click to collapse
Same here. I had approximately 30 of them. My guess is from failed ota attempts due to rooting.
Sent from my Nexus S using XDA App
Just checked my phone today and I have the same thing, dated Jan. 10.
I'm running CM7 Alpha 2-2.
I have 4 of these I wonder what it is.
I had about 20 of them today. My phone seems to reboot randomly when using a Bluetooth headset. Anyone know if there is a radio update anywhere?
Sent from my Nexus S using XDA App
nobody knows? this practically filled up all my space and i had to delete them
Paul O'Brien thinks it's a crash dump of the ril.
He's tweaked his MCR custom ROM to not write it.
I haven't seen it yet on my phone...stock. Weird how some get it and some don't.
I have like 6 of these files on my stock gingerbread NS too.
Is it safe to delete them?
sagech said:
I have like 6 of these files on my stock gingerbread NS too.
Is it safe to delete them?
Click to expand...
Click to collapse
Yes. Delete away.
I've got this problem once in a while too (twice today, last time before was 5 days ago)
I think it's the same problem as here http://forum.xda-developers.com/showthread.php?t=906435
Since some have it and some don't, might it be related to an app? The only app i think i have launched today and not on previous days is "Antennas" (great app, but seems to stay in background when you think you closed it)
Stock Nexus S i9023 Rooted.
i've got 33 of them
not sure if i can delete them or not, but looks like you guys have without problems.
i.imgur.com/4j3YS.png
nexus s, CM7
had 4 of them on my stock 2.3.4
removed them now.and will monitor when there will be a new one.
so far only radio using apps i have are the stock apps.
I am also having this issue with nexus S with baseband i9023XXKD1, randomly it asks for pin code and a radio_dumpxxxx.bin file is created in the 'sd card'.
Using simyo (kpn) in Spain which uses Orange network.
Has anyone found what the problem is?
Radio dump bin files seem to get created when the phone loses its 3G connection - they're safe to delete and should be deleted to save space, since 37 MB each adds up. Also, not every baseband version works on every carrier. Some ROMs do include baseband, so you may end up with a new one without realizing. My Nexus S originally came with baseband B1 which worked find on my carrier. Now I've got D1 which also seems to work fine. Maybe your D1 isn't compatible with Orange - try B3 or B1 instead.
Hello,
I have been experiencing a bug where the phone acts as if there has been a long press of the search button (and the appropriate dialog comes up) when I have not touched the search button at all! (I am not pressing it by accident, it will do this while sitting on a table untouched). When it happens, the search button is not lit up (as if it were pressed), and none of the other buttons can be pressed, nor can anything on the screen, other than responding to the dialog. This can last two to four seconds (it's REALLY annoying). What's worse is that this can happen up to once a minute sometimes!
I've discovered that this happens only when I have 3g data turned on. When data is off, or when on wifi only, it does not occur.
Is anyone else having this problem, and (hopefully) has found a fix? I did do a search (both on Google and in here). I discovered a Google forum where people talk about experiencing the problem (a Google employee chimes in with questions) but no solution as of yet. I was hoping to find something about this in Xda, but as stated, couldn't find anything Though this person may be talking about the same problem:
http://forum.xda-developers.com/showthread.php?t=1069765
Here is the link for the Google forum:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
Since it only happens when 3g data is turned on, could it be my radio image? Or something else? Any help or thoughts would be greatly appreciated! My current running specs below:
Nexus S
Android Version 2.3.3
Baseband version NO DGSXKD1
Kernel Version 2.6.35.7-g1 d030a7 [email protected] #1
Mod Version Cyanogenmod-7.0.3-NS
Build Number GRI40
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Rooted, bootloader unlocked
I was about to post this exact thread! I am having the same issue with my NS i9020a running stock unrooted 2.3.4. I to have noticed a link between data connection type and the issue occuring. One theory i read said that static charge may be to blame?... but that didn't seem right to me....
Anyway... I would also love some more info on this subject of anyone has any input. I bought my phone off ebay less than a week ago, and if the issue is hardware i am going to have to file a claim with paypal...
Sent from my Nexus S using Tapatalk
This is exactly what I posted in a separate thread. However, I'm not sure about the 2G / 3G changing.
I'll experiment.
Which radio are you using - seems like this was at least temporarily related to my switch to KD1 ?
Sent from my Nexus S using XDA Premium App
I reflashed radio KB3 and problem , at least for now is not happening. It was almost making the phone unusable this am earlier before changing radio
??!
Sent from my Nexus S using XDA Premium App
How can I find what radio I am using? Also, How long have the two of you had your devices? Is this issue something that manifested after you changed something on your phone (thus indicating it is not hardware related) or has it always been there? Thx, and i hope we can get this sorted out.
Cheers
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
jcrompton said:
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Baseband Version
NO DGSXXKD1
Kernel version
2.6.35.7-ge382d80
[email protected] #1
Build number
GRJ22
Please update as to whether the radio change is a permanent fix. Thx.
Cheers
Edit: I am assuming that this (NO DGSXXKD1) is the KD1 radio that you switched to and are theorizing may be the culprit...it is also something that all three of our devices have in common. I am eager to see if changing the radio permanently fixes your issue.
I'm on a Telus 9020a radio KB3 and i have the same problem.
Not sure at this point what the deal is! But changing from the upgraded radio KD1 back to KB3 has up to this point solved the issue. Maybe six or seven hours without the phantom search firing.
????
Sent from my Nexus S using XDA Premium App
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Matridom said:
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Click to expand...
Click to collapse
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Hey guys, got the Sprint Nexus S 4g just this last Friday. Phantom search button presses and long presses started up soon after. Still going on now. Have not been able to narrow down culprit as far as 3G/4G/Wifi go. Running completely stock everything:
Android 2.3.4
Baseband D720SPRKD8
Kernel 2.6.35.7ge382d80 [email protected] #1
Build Number GRJ22
Just thought I'd add my stat to the growing list.
Sophos1 said:
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm on my phone so it's as little hard to link. In the general section there is a thread to a stock nandroid backup with the kb3 modem.
Sent from my Nexus S
I've now been about 9 or 10 hours after switching back to KB3 - no more issues yet! Pretty strange huh?
Sent from my Nexus S using XDA Premium App
Finally got my device rooted and switch to the KB3 radio.... it's has been a few hours and I have yet to experience the search button bug. I'm crossing my fingers that you found the solution! Thx.
Sent from my Nexus S using Tapatalk
Ok. So it's now been almost 24 hours. No repetitive firing of the search button on my Nexus S since flashing back to the KB3 radio.
Beware anyone experiencing this should not flash to the KD1 radio. I have a 9020a device. I assume it is Canadian since it had ATT 3G bands prior to any mention of ATT devices.
I think they are all a bit different when it comes to hardware which baffles more when I read on a Google forum post about a T-Mobile device that was stock Ann's doing this.
Sent from my Nexus S using XDA Premium App
Where to dowload KB3 radio image? (And advice)
Hey jrcompton,
Wow, that's great news! I tried a bunch of things, including going back to stock 2.3.3 via ROM manager (am now on 2.3.4, as I was prompted almost immediately for an OTA upgrade), and the bug still persists. It seemed after returning to stock that the issue didn't present itself until after installing certain apps (Dialer 1, Handcent, Extended Controls) but after removing them, am still seeing the bug. Was thinking that maybe it was these apps and uninstalling still let some trace and another factory reset might be necessary, but your results give me hope! As it is, on mobile data the bug can present itself several times in a minute! (Making the phone almost unusable).
All that being said, any chance you could share where I could download the KB3 radio? I did search and was only able to find a thread with mostly Tmobile users, and was thinking that the radio in that thread might not be the right one. I'm on Bell, so sounds like the radio that you're using would be right for me (since your phone uses AT&T bands).
Also, never flashed just a radio before, and am a little nervous. I know that there are a ton of threads with instructions, but I hope it's ok if I ask a couple questions. I'm assuming that I download the image, and put it in my ANDROID-SDK-TOOLS directory, then just (in command prompt from that same directory) type "fastboot flash radio *********.img (with the phone in bootloader, and connected via usb). And that I should NOT disconnect, power down, touch, or even look at phone during process, and make sure that PC doesn't power down, reboot, etc. If all of that is correct, do I need to wipe/factory reset or anything else beforehand or afterwards?
Thanks so much in advance, and so glad that you've at least had 24 hours bug free!
If this works for me as well, will post in the Google help forum thread as well.
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
If this worked for you guys then that's great, but do you have any suggestions for a NS4G user? I realize we don't have our own subforum but up until that happens, we have to have our questions fielded here. I'm still getting the search button going nuts on me issue. have tried data off/only wifi and still doing it. Wondering if I just got a defective unit...
Sophos1 said:
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey Sophos1 (or anyone else who might know),
My Nexus is now running the following:
Android Version: 2.3.4
Baseband Version: NO DGSXXKD1
Kernel Version: 2.6.35.7-ge382d80 [email protected] #1
Build number: GRJ22
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Would the KB3 radio that you downloaded for your phone work for mine? Also, just for confirmation, will I be ok following the steps that I listed above? Lastly, what's the worst that can happen if I flash the incorrect radio? Would I still have the opportunity to flash the correct radio (or reflash stock including the correct radio) via fastboot?
Thanks so much guys!
It hasn't been a problem to me until recently but ever since I rooted my Inspire 4G my GPS hasn't worked at all. Everytime I put a location in, it just says "Searching for GPS" and it never connects. I don't know if this will help but here are some things I've found on my phone
When I dial *#*#4636#*#* I get a bunch of info. In that info it says "GPRS service: Disconnected" (I think that's the problem)
After reading that I think I have the wrong radio version? When I go to "About Phone" in the settings I found my Baseband version. It is 12.39.60.19P_26.06.04.06_M
I don't know anything about radios or how to fix or update them (If that's the problem)
BTW I'm running Android Revolution HD 6.1.3
You're running the radio that came with the phone originally, and that could be the problem. Best bet for help would be to ask in the AR Q&A forum-Searching would have been a good idea. Also, you might want to read the radio sticky in the DEV forum.
I tried 3 different radios and none of them worked. I also tried a different rom. I tried Android revolution with the new radios and nothing. And i tried the newest beta of Ice cream Sandwich and still nothing. Maybe it's not the radio. Could it be something else? The new radios I tried were said to work with ARHD...
Radio shouldn't matter. Perhaps is is just loose. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1101066
I pulled the GPS antenna off and pulled up the gold contacts and cleaned off the contacts on the antenna with a q tip. I put everything back together and tried the GPS but.....nothing. It still won't connect and the GPRS service still comes up as disconnected...
But now knowing that those metal contacts are for antennas... I pulled up the 2 little metal contacts that are under the battery door and under the sim and sd card cover and now my WiFi and cell reception are WAY better than they ever were. I used to get 2 bars of cell sitting on my couch but now I have full bars. Same with my WiFi when I am on the second floor.
Well, glad to hear that you improved signal. Bummer about GPS, but even though GPRS has all three of the GPS initials, it has absolutely nothing to do with GPS. GPRS is "General Packet Radio Service" and is the lowest level of data communications on our phones. I'ts more-or-less 1G data. 2G is "Edge", then there's 3G and 4G, but none of those have anything to do with GPS.
I had the same issue with ARHD being 6.1.3 ,6.1.5 or the newest 6.2.0...
Gps just wouldnt lock...there's a Q&A in that thread for possible GPS fixes and this one worked best, all others no dice.
[Trick] Speed Up Satelite Fix for GPS on Android
I get lock in about 10sec at 8meters accuracy...give it a try
Sent from my HTC Inspire 4G using XDA App
jadeus0831 said:
I had the same issue with ARHD being 6.1.3 ,6.1.5 or the newest 6.2.0...
Gps just wouldnt lock...there's a Q&A in that thread for possible GPS fixes and this one worked best, all others no dice.
[Trick] Speed Up Satelite Fix for GPS on Android
I get lock in about 10sec at 8meters accuracy...give it a try
Sent from my HTC Inspire 4G using XDA App
Click to expand...
Click to collapse
Thank you so much!! That worked for me! I lock onto 10 satellites in like 8 seconds and in the GPS app it locks on before the map even loads! The GPS on this phone hasn't worked for about 6 months I'm so happy it's working again.
Thank you everyone who gave their input on here. I fixed my GPS and learned a few things I'd be so lost without you guys lol
Glad you found your fix for the issue. I had a similar problem when I first rooted and installed ARHD 6.1.0 with the recommended radio. This also fixed my issues.
does fix only work for ARHD? because im using rcmix3d runny v4.0, and im having issues with gps also.