Hey guys, I live in a rural area in the USA and I use to get a pretty steady 1-2 bars my house. Recently I started flashing my ROM with some of the ROMs here and I've noticed I can now only get maybe 1 bar by my window. I was wondering if somehow my radio got changed or something else? I'm on T-mobile. Thanks for you help.
Beaver2
What radio version have you got installed?
(in case you don't know, look under 'start>system>settings>device information>software information'.)
Here's a thread with lots of different radio versions for download: http://forum.xda-developers.com/showthread.php?t=549939
Different radio versions are often better suited to different geographic areas/carriers. Take a read and see whether there are any comments about a particular radio version from someone who lives near you/uses the same carrier.
It says:
4.49.25.17
I'm knew here and I understand the concept of ROMs but what is the radio for and does flashing the ROM change it?
Beaver_2 said:
It says:
4.49.25.17
I'm knew here and I understand the concept of ROMs but what is the radio for and does flashing the ROM change it?
Click to expand...
Click to collapse
You can go here...http://forum.xda-developers.com/showthread.php?t=549939 and read about the different radios. Some roms work better with certain radios. Flash some and see what works best for you..
The radio (not to be confused with the internal FM-radio) is the firmware which controls the device's various antennas (among other hardware). It sits between your device's hardware and Windows Mobile. The radio is a huge factor in your reception in a given area, so changing radio versions may help you. The only problem with radios is that your situation is completely unique, and therefore, nobody can tell you which radio is best for your location. My advice is to simply try the latest ones, and see how those work, and using older and older ones until you find one that works for you. The procedure for flashing ROMs and radios is the same. Just ensure you don't flash a CDMA radio, or you'll brick your device. Visit cr1960's link for all GSM Rhodium radios.
Beaver_2 said:
Hey guys, I live in a rural area in the USA and I use to get a pretty steady 1-2 bars my house. Recently I started flashing my ROM with some of the ROMs here and I've noticed I can now only get maybe 1 bar by my window. I was wondering if somehow my radio got changed or something else? I'm on T-mobile. Thanks for you help.
Beaver2
Click to expand...
Click to collapse
Aluminum foil wrapped around a fork and tied to my phone seems to work for me.
Flashing a cooked ROM won't affect your radio version. But if you flash an official ROM, that usually comes with its own radio version too.
I have a Sprint tab. I wan't to upgrade to gingerbread, and I don't care about CDMA service, but I have to have wifi. GPS would be preferred but I can live without it. It would also be nice if it wasn't a brick afterwards.
What are my options? Can I just flash Overcome without a modem file? Is there some sort of null modem file I can flash? Is there a different ROM or kernel I should use?
http://forum.xda-developers.com/showthread.php?t=1020167
jiminitaur said:
I have a Sprint tab. I wan't to upgrade to gingerbread, and I don't care about CDMA service, but I have to have wifi. GPS would be preferred but I can live without it. It would also be nice if it wasn't a brick afterwards.
What are my options? Can I just flash Overcome without a modem file? Is there some sort of null modem file I can flash? Is there a different ROM or kernel I should use?
Click to expand...
Click to collapse
Also very interested in this.
I recently put quite a bit of effort into getting GB to run on my Sprint tab. I use WIFI only so I was not concerned with a working CDMA radio. I attempted to flash the European GSM firmware to my device. I tried flashing the kernel and system only, leaving the CDMA radio file intact. I also tried flashing several GSM radio files to the device. In the end I was unsuccessful, and it took several hours to recover the device to an operational state.
If you WERE to get GSM GB working, there is a good chance that GPS and BT wouldn't function. That's kind of a deal breaker for me.
tldr; Sprint users are screwed until the official release of GB because the Overcome team doesn't care about us and the only guy who seems to know how to work the CDMA is making a crappy honeycomb build instead.
IMHO other devs should make a version of the ROM with all data taken out because it'll work for Sprint users and GSM users who tether instead of paying out the rear for a data plan on their tab.
----------------------------
tonman23: Thanks, but i was looking for gingerbread, not honeycomb. It's great that spacemoose can prove it in concept, but I don't like the honeycomb interface, and I'm not interested in flashing a half broken version of it to my phone. I want a stable gingerbread build for the improved performance and minor UI features.
etvaugha: BT & GPS are handled by chips completely independent of the modem. I can't post a link because I'm still new here but the ifixit galaxy tab teardown shows clearly that GSM tabs have distinct BT/WLAN & GPS chips. That's pretty standard fair for android devices, so I doubt they changed it simply for the CDMA models.
It also clearly shows that the modem is a GSM only chip, so the bin files are completely incompatible. The only solution is ROMs that will boot even if the modem isn't working right.
----------------------------
According the the Overcome 2.0 FAQ, the problem is that the phone won't finish booting if a valid modem.bin is not installed. Apparently the phone waits indefinitely (one user, PFOI, mentioned something about it working after 30 min or so) or crashes during the boot because it doesn't get a proper response from the modem chip.
This could easily be overcome if the devs would compile a WIFI only version of the rom/kernel, that doesn't require or support either modem (CDMA nor GSM). It seems to me that the this would be good for both sides, as the data plans for tabs are a rip off and smart users are going to tether their tabs in a mobile situation anyway. It would also probably be better for battery life considering there'd be one less chip running and less bus activity.
I'd imagine all that would be required is removing the modem initialization during the boot sequence. There might be a need to replace the functions that query the modem's status with static value return statements, but when the tab first boots it reports no service, so it's got an inherent ability to deal with not having network access. All that's needed is a couple little snippets to tell the device it doesn't, and to keep it from trying to get it.
I was sent this by XDA user: coreless88 who asked me to post this in the dev section (he doesn't have enough posts yet).
** WARNING: I HAVE NOT TESTED THIS PERSONALLY -- USE AT YOUR OWN RISK -- KEEP A BACKUP HANDY **
** THIS ROM IS INSTALLED WITH SAFESTRAP BOOTSTRAP. DO NOT USE KOUSH'S BOOTSTRAP OR YOU WILL SOFTBRICK YOUR DEVICE **
I dabbled in files for some time, twaked the build.prop a little (added some generally known hacks into it for faster touch reaction, better HSPA reception etc.), and added some files .lib/.ro files from Droid 2 Global.
It all worked out nicely. However, as I cannot use a CDMA network (I live in Turkey, so I have only GSM access), I cannot guarantee this will work with CDMA too. I will appriciate it if someone can test it.
Also, Your GSM card will be recognized instantly, but you need to activate the 3G network form the settings, you will need to add your APN manually, atleast in my case I had to put my carriers APN into the list, so this might not be necessary."
Here is the link: http://www.mediafire.com/?d17l4z4885ph4ov
Thanks needs to go to Hashcode, as I just modified and added a missing feature to it.
Click to expand...
Click to collapse
Thanks for the help Hashcode!
I got my clearence to Dev forums, so I will try to contribute even more to this community =] .
First of all, as in my quote in the first post, I cannot guarantee this will work in CDMA network, Hashcode will inspect the files and try to integrate the GSM feature to his original release.
You can find a screenshot of my phone working under the GSM network and 3G enabled.
!!!However, just like any other custom rom, I cannot accept any responsibilities if this rom bricks your phone. !!!
For installing, just use Hashcode's safestrap, for the rest i think you know the drill.
BUGS:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken,
Also be aware, notification and ringtone sounds are silent by default, you just need to go to settings menu and choose a ringtone for yourself =] .
Edit: Also as I have only 1 Droid 3 at the moment, I need as much testers as I can find for checking if this works for all Europe SIM Cards.
Referved for future use/updates/etc...
Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....
thank YOU !! Hashcode and Coreless88
No thank you guys, for trying it and giving me an easy breath as it is my very first development attempt!
nikeusfr said:
Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....
Click to expand...
Click to collapse
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Right now bluetooth doesn't work, but GPU and CPU working properly, if not better than before.
Here are some more screenshots, for Quadrant, SpeedTest, and A Samurai Vengance 2 (BTW Game runs incredibly smooth).
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
nikeusfr said:
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
Click to expand...
Click to collapse
Hi,
First of all, thanks for your input. I need your opinions to make this better. So here we go,
All notifications and ringtones are silent by default.
You need to get to:
"settings>sounds>ring tone/notification tone" menus and choose your ringtones from there.
Sounds are in this built generally low, because there isn't any proper sound resources prepared with OMAP 4 series of SoC's. I will try to enhance them, but I will need time.
But you can make the phone louder on the speaker by going to:
settings>cyanogenmod settings>sound menu then choose the settings you like the most.
What "general" GSM build.prop tweaks are we talking about here?
DoubleYouPee said:
What "general" GSM build.prop tweaks are we talking about here?
Click to expand...
Click to collapse
Hi,
I've added Tweaks for getting stronger reception, making the GSM default network at the boot, tweaks for faster response, etc... You can download the file and look at the system>build.prop (open it via wordpad if you are on windows) and compare it to Hashcode's build.prop.
BTW I am experimenting with audio and video files right now. Post I will post the results when I finish the testing.
Could I apply these build.prop changes my XT862 rom?
Or did you use droid 2 global hacks like someone tried before?
DoubleYouPee said:
Could I apply these build.prop changes my XT862 rom?
Click to expand...
Click to collapse
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.
coreless88 said:
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.
Click to expand...
Click to collapse
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)
DoubleYouPee said:
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)
Click to expand...
Click to collapse
Oh!
I completely misunderstand you, I thought you were asking about Hashcode's Cyanogen release. You cannot use these fixes for Motorola roms or any rom that based on a Motorola rom. These fixes and libraries are only for Cyanogen builds, at least thats what I think, as I don't have any development experience with any Motorola rom.
You may try, but that will only make the risk even bigger.
Please be patient, I am trying to fix camera and sound problems right now, and I will try to fix bluetooth in a later date, as I didn't see anyone using bluetooth for ages =] .
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
coreless88 said:
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Click to expand...
Click to collapse
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
Willis111 said:
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
Click to expand...
Click to collapse
Hi,
Your thanks are appriciated, and I am sorry for this rom also did not worked for your XT860 =/ . I guess Motorola did everything they possibly can to protect their region based software versions.
I guess the fix will be simple, but I am afraid either Canadian Android developers are rare (BTW I don't think so), or they don't want to develop for / they don't have this device.
The Solutor said:
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
Click to expand...
Click to collapse
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
coreless88 said:
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
Click to expand...
Click to collapse
Indeed this is the only reasonable explanation, the same behavior in five ROMs can't be a bug.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
Click to expand...
Click to collapse
Maybe is omething hardcoded in the libril or whatever in the userland, surely is not the radio itself.
XT883 is not affected, so we should try to replace some piece to spot the culprit, BTW this process would be easier when the bootstrap will be fixed to work on XT883, (why doesn't work on that rom is a another nice mystery).
Indeed, a GSM ROM would be great
FYI, audio and video codec issues are being addressed in my next build of CM7.
I'm going to give the GSM ROM a test drive and see how the CDMA stuff is affected. As well as look at the differences by file.
Hopefully, i can incorporate coreless88's changes back into the main ROM so that we don't end up with 2 CM7 ROMs (CDMA and GSM).