bad speech quality - baseband problem? which baseband for germany? - Streak 5 Q&A, Help & Troubleshooting

Hi.
I am quite new to the Streak 5 and I flashed the Custom Rom DSC 1.6.
Unfortunately I now have a bad speech quality in calls.
Sometimes I cannot understand the other sometimes I cannot be understand.
I live in Germany.
Can you tell me which baseband do I have to use?
Unfortunately in the german Board nobody answers me, but they are using an original Rom with custom Kernel called Minimal Streak.
This is based on 351 Baseband.
Is this the baseband I have to flash for Germany?
Or is the baseband not based on countrys?

I'd personally recommend 366 or 369.

This means that is a Softbank Baseband.
Can you tell me what that means?
I thougt I need a 00 region Baseband. (Yes I know the Rom ignores the region)

Baseband files are flashed through Fastboot, thus there's no need to match the region of the ROM with the region of the recovery.

Thanks for the answers
But one question:
What is the 00 - 14 number?
I know, that is 14 for Olleh, etc. as the wiki says.
But what does that mean exactly for another device?

The world was divided into regions by Dell. Regions usually represent specific carriers although they may also represent specific countries, e.g. China. The numbers are Dell's internal codes for specific regions. As you figured out, region 14 is for Olleh KT phones. 00 is the region Dell used for unlocked Streaks available direct from them. The complete list of regions (pulled from my work with Multiflasher): 00 Retail, 11 Hong Kong, 12 Softbank (Japan), 14 Olleh KT (South Korea), 15 China, 21 O2 (UK), 31 AT&T (US), and 32 Rogers (Canada).
What this means for Dell devices is simple: there is code within the recovery image that checks for the proper flag in the firmware package. If the two match, then the recovery allows the installation to proceed. If the two do not match, the recovery will throw up an error and halt the installation at that point. I believe most non-Dell devices don't have such a check mechanism within their recoveries. I can confirm that HTC doesn't use such a check. The HTC Liberty phones were branded as the HTC Aria here in the US. The European HTC Liberty was named the Gratia. I installed a Gratia ROM onto an Aria without any difficulty whatsoever.
So, for other devices, unless they're Dell I wouldn't worry too much about the region check. That's something that is virtually unique to Dell.

So the region is nothing more than a flag?
It is not some code, which frequency to use, how to react on calls, how loud the speaker is or something?
Is there a list, which baseband has which properties?
(Except that most are satisfied with 366 and 369)

That's right. But before I continue I do need to clarify something. I mentioned that the baseband files were flashed through fastboot, thus you didn't need to match the ROM to the recovery in that instance. However, in order for the ROM to work properly, the baseband and kernel need to be of the same region or else the home, menu, and back buttons will flash repeatedly. The kernel itself checks the baseband's flags to see if everything matches.
Normally, when installing a stock ROM baseband mismatches don't occur since the baseband is flashed with its accompanying ROM using the matching recovery. The problem occurs however on custom ROMs that use a stock ROM as their base, e.g. DSC. For DSC, _n0p_ recently removed the region check from the kernel so that any baseband could be used on the ROM, though he recommends 366. Before that, DSC users were limited to using the 407 baseband. Cyanogenmod, ROMs based off Cyanogenmod, and MIUI I don't believe ever had the check code, and thus you could flash any baseband you wanted.
The baseband itself contains the low-level code that controls the various radios and possibly the speaker volumes as well. I don't know enough about the innards of the baseband files to tell you more. What I will tell you is that I'm not aware of any such list as what you ask for, because such a list would require disassembling the baseband repeatedly to find the differences, and such a list would be of dubious benefit in any event.
My advice to you? Install the 366 or 369 basebands and use the Phoenix kernel. You should be good to go.

Thanks a lot

Not exactly right.
Region check never existed.
Kernel checks BB version (3 or 4) and blinks on mismatch. Disabled on Phoenix kernel and it's derivatives.

Well, thanks for the correction.

One more question to this.
Is a softbank baseband 366 good for central europe or shoult I install the one most devices 351 here have?
Are the frequencies used in softbank 366 and 351 different?
(except speech quality is better in 366, I know.)

dont dsc 2.0 uses 366bb by default? or it is included as default streakmod flash?

You cannot flash AMSS/DSP from recovery (or at least i did not find a way so far).
So no defaults here.
I personally use 369 as it's the latest baseband released.

yeah, I already know that
But what about the frequencies :crying:

And what about them?
Supported GSM/3G bands are in hardware.

sorry.. not streakmod flash.. i mean fastboot flash...

As I understand it the baseband tells the phone which frequencies to use. That means if its a Japanese baseband it tells S5 to use japanese frequencies even though the S5 is not capable to use them due to hardware limitations.
The same with EU version.
Softbank is japanese. It tells S5 to use japanese frequencies. AFAIK some of them are identical to EU but not all. So the connectivity is worse than using retail baseband.

I don't think it's the case for Streak.
366/369 simply makes WCDMA default, that's all.

369bb? heh.. nice

Related

[Q] 2.1.1.A.0.6 Rogers rom on ATT?

Has anyone put the new Rogers rom on a locked ATT unit?
Any market problems?
Any problems removing Rogers apps?
I THINK want to go to one of the custom roms but I'm only on Baseband 2.0.46
and I don't have Dual Touch installed. But it seems that I'm required to update to the higher bb at least, and though I see a BB update only thread, it's unclear if all basebands are compatible with all SE 2.1 update-1. And then I would still have to update to dual touch prior to installing a custom rom.
Since these are two independent flash requirements, and it seems that I have to update to some rom higher than 504 anyway, so I was wondering if I could just go to the Rogers one.... getting dual touch and a higher baseband right off the bat in an official package in one shot, and check it out prior to deciding to move on.
Different basebands work with different firmwares and kernels. You can mix and match, to some degree (for instance, .55 baseband works with .435 or 2.1.1.A.0.6 FW), but there's really no reason to.
I own an AT&T X10a, and I always use the X10i Global Generic firmwares. All the features without all the crap.
Check out the link in my signature for an optimized version of the .435 firmware (dualtouch, etc). Follow the instructions, there's a file for flashing the new kernel and baseband on there.
Good luck!
kxhawkins said:
Check out the link in my signature for an optimized version of the .435 firmware (dualtouch, etc). Follow the instructions, there's a file for flashing the new kernel and baseband on there.
Click to expand...
Click to collapse
But even your firmware says I have to flashtool a higher baseband to get it work prior. (Shouldn't you update your screen shots, you show bb 2.0.46 when you really mean 2.0.54) Though what you've put together is very interesting. Do you still have all the SE apps, too, in the collection of applications? (Just asking, I know they have apk's available.)
I'm just trying to avoid flashing multiple times now*, do a straight 2.1.1.A.0.6 update and flash only once and get higher baseband, dual touch and whatever other tweaks there are which don't require flashing. There's no LAM/NAM generic of this version yet?
*flashtool for me a PITA, because I don't have VISTA/Win7 computers generally available and it works better on that than XP which is problematic due to the SE usb drivers which sometimes freeze it in flash mode. I am getting a decent tax refund, I suppose it's time to upgrade to sandybridge and Win7 (since the first SP is out) before they announce Win8.

A list of difference between unlocked and at&t locked streak?

I found the at&t locked one doesn't have "unknown source", "input method" under setting. Found ways to make it work.
I also can't find Chinese Language for the system. Anyway to get this back?
My first streak was unlocked, but has some problem. After changed the streak from Dell, they sent me a locked one. I did get the unlock code, but looks like the AT&T one is very bad.
Why not flash the 354 (hong kong retail) rom to your Streak? Or even the 351 ROM? Search to find discussions of the differences between them.
Truelies, LISTEN to the Marvelous Marvin! He knows his stuff!
marvin02 said:
Why not flash the 354 (hong kong retail) rom to your Streak? Or even the 351 ROM? Search to find discussions of the differences between them.
Click to expand...
Click to collapse
Thanks. I am new to rom rlash. Does Rom flash change everything from locked to unlocked one?
354 and 351 which one is better? I searched someone said after flashed to 354, can't install some application?
I checked here: http://forum.xda-developers.com/wiki/Dell_Streak/Flashing_Guide#Entering_fastboot_mode_on_phone
I am a little confused. Do I need to do "Updating baseband" before I can "Installing a stock rom"?
Changing the ROM doesn't change the lock status of the Streak. Once it's unlocked, it STAYS unlocked.
354 had less bundleware, fewer languages supported, and code that was actually a few hours older than 351. However, 351 is no longer the newest ROM for unlocked Streaks. That honor goes to 360, but the only real benefit of 360 is that the bundleware is updated.
I personally recommend 351 or 360 over 354. The code is newer, the language support is better, and any annoying apps in the ROM can be removed by rooting the phone and running a root uninstaller app. Plus, you don't have to flash a baseband or amss file to get a stock ROM up and running.
Strephon Alkhalikoi said:
Changing the ROM doesn't change the lock status of the Streak. Once it's unlocked, it STAYS unlocked.
354 had less bundleware, fewer languages supported, and code that was actually a few hours older than 351. However, 351 is no longer the newest ROM for unlocked Streaks. That honor goes to 360, but the only real benefit of 360 is that the bundleware is updated.
I personally recommend 351 or 360 over 354. The code is newer, the language support is better, and any annoying apps in the ROM can be removed by rooting the phone and running a root uninstaller app. Plus, you don't have to flash a baseband or amss file to get a stock ROM up and running.
Click to expand...
Click to collapse
I will go to 360. The reason my AT&T locked one doesn't have "unknown source", "input method" is At&t removed them?
That's right. Of course AT&T figured out that blocking sideloading was a losing battle, but they're not the sharpest knives in the drawer. If your Streak is now unlocked, you definitely don't want an AT&T ROM on it, so 360 is a good choice.
Strephon Alkhalikoi said:
That's right. Of course AT&T figured out that blocking sideloading was a losing battle, but they're not the sharpest knives in the drawer. If your Streak is now unlocked, you definitely don't want an AT&T ROM on it, so 360 is a good choice.
Click to expand...
Click to collapse
I also don't know what's baseband mean? Why if I flash 354, I need to flash baseband, but if I go to 360, I don't need to?
I don't know where you saw that about 354. Flashing a package also flashes the correct baseband and amss files for that ROM, so if you installed 354 you should have 354's baseband and amss installed along with the ROM. Same thing for 360. You shouldn't need to change the baseband or amss files at all unless updating to one of the custom Gingerbread ROMs that are available.
The baseband is the software that controls the Streak's antennas.
Strephon Alkhalikoi said:
I don't know where you saw that about 354. Flashing a package also flashes the correct baseband and amss files for that ROM, so if you installed 354 you should have 354's baseband and amss installed along with the ROM. Same thing for 360. You shouldn't need to change the baseband or amss files at all unless updating to one of the custom Gingerbread ROMs that are available.
The baseband is the software that controls the Streak's antennas.
Click to expand...
Click to collapse
Installed 360, the interface is really new and different, good thing is the weather in the start page is my true location this time. Still under setup no way to change the input method, but I can change it with a long press.
Finally I got ride of damn AT&T
Many things are done on the Streak with a long press, there being no option in Settings to do it. I would go to the Wiki and read up. One of the pages has a list of long press shortcuts.

New baseband versions. Does sub-version matter?

I've been happily flashing roms on xda for months now a few were glitchy (not always the bugs mentioned).
My phone is. P500h from Koodomobile (owned by Telus) and last November's update to 2.3.3 included baseband update to their v20a. I see that most roms are v20g or above now. I still use my carrier's baseband, regardless.
Only a handful of 2.3.3-based roms recognize the carrier as koodo and default to telus. I have to manually enter the apn most times to get data and mms to work.
Would updating to v20g (or i) be a good idea? Or am I best off using Koodo's version?
I am surprised this hasn't been asked before.
Sent from my LG p500h using XDA over the inner tubes
I think you should flash a V20G stock rom from lg to update yout baseband to v20g, or only upgrade your baseband with LGMP and verify if it works
The koodo's version only bring you some apps from this operator
I am not concerned about the stock rom version. LG includes too much crap and the battery has never impressed me.
I am more concerned what an upgrade of baseband would do to the radio in regards to my carrier. I've been running CM-based roms and I like them.
Sent from my LG p500h using XDA over the inner tubes
Flashing a V20g with kdz is the easier and safer way to upgrade your baseband, after upgrade your baseband you return to cm
No, your baseband is fine (any V20x works).
Your problem is just that CyanogenMod doesn't include the APNs for your particular carrier, despite the fact it has a huge (I mean HUGE) list of pre-recorded APNs for carriers all around the world.
But you can easily set up your APN with this app, if you don't like to put it manually (I wouldn't like it too):
https://play.google.com/store/apps/details?id=com.tweakker
(It worked for another canadian fellow in a similar situation)
I thought so but had to have a confirmation that I wasn't complicating anything.
That app is a nice find. I'd already used apn backup and restore to save to keep what I had manually entered.
Sent from my LG p500h using XDA over the inner tubes

[Q] S2 Rom supports OTA

Hi all
I have been wondering how I can tell if the custom or claimed-to-be-official S2 ICS rom supports OTA upgrade?
I know it's perhaps impossible for those custom ones, but the ones I downloaded and flashed that claim 'official', how can I be sure if they supports OTA or not? I am a bit tired of keeping flashing the new versions after all.
Thank you!
it is strictly connected to your product code and region the ROM was released for - these two things have to match.
You will have OTA update if you're using ROM officially released for the region you have set in your phone. and you will get OTA updates only to other ROMs released for this region. few examples:
1. you have XEO product code and you use ROM officially released for XEO - you will get OTA updates but only to other ROMs released for XEO;
2. you have TWO product code but you have installed ROM released for XEO - you won't have OTA update at all (unless you change your PC according to you ROM release region - to XEO - and then, again, updates will be only to XEO ROMs)
3. you HAD XEO and ROM released for XEO, but for some reason you changed your PC to TWO - you won't have OTA update at all (unless you match your PC with region your ROM was released for again).
so, check your product code and the region your ROM was released for, match them however you want - change ROM or PC - and you will be having OTA updates. remember that changing PC is wiping all your data so do backup.
other thing is that you won't have OTA update if you use custom ROM, custom kernel or in some cases root (depending on the root method. rooting phone without making changes to kernel doesn't stop your device from getting OTA update until you make changes in your system).
gaeilge said:
it is strictly connected to your product code and region the ROM was released for - these two things have to match.
You will have OTA update if you're using ROM officially released for the region you have set in your phone. and you will get OTA updates only to other ROMs released for this region. few examples:
1. you have XEO product code and you use ROM officially released for XEO - you will get OTA updates but only to other ROMs released for XEO;
2. you have TWO product code but you have installed ROM released for XEO - you won't have OTA update at all (unless you change your PC according to you ROM release region - to XEO - and then, again, updates will be only to XEO ROMs)
3. you HAD XEO and ROM released for XEO, but for some reason you changed your PC to TWO - you won't have OTA update at all (unless you match your PC with region your ROM was released for again).
so, check your product code and the region your ROM was released for, match them however you want - change ROM or PC - and you will be having OTA updates. remember that changing PC is wiping all your data so do backup.
other thing is that you won't have OTA update if you use custom ROM, custom kernel or in some cases root (depending on the root method. rooting phone without making changes to kernel doesn't stop your device from getting OTA update until you make changes in your system).
Click to expand...
Click to collapse
Thanks for the detailed response. So I guess I need to get a stock rom for Australia then as I bought the phone and am using it in Australia.
Where I can find it? What's the code for Australia market? XEO is just for Euro, rite?
Thanks!!
Get the PC version of Checkfus (search for it on here/Google) & download I9100XWLP8/I9100XSALP4/I9100XXLPS/I9100XWLP8 which is an unbranded Australian ICS stock rom. Flash it following the instructions in this thread. You can also download carrier branded ICS stock roms with Checkfus if that's your preference.
MistahBungle said:
Get the PC version of Checkfus (search for it on here/Google) & download I9100XWLP8/I9100XSALP4/I9100XXLPS/I9100XWLP8 which is an unbranded Australian ICS stock rom. Flash it following the instructions in this thread. You can also download carrier branded ICS stock roms with Checkfus if that's your preference.
Click to expand...
Click to collapse
Thanks!
a few more questions:
1. How can I tell a ROM definitely supports OTA before I install it?
2. How can change my s2 region code to match the ROM's in order to get OTA working again?
3. what's the real difference between carrier branded rom and unbranded ones? e.g. is it better to use say telstra branded rom?
1. Be sure that ROM was released for the region/carrier which fits product code set in your phone - it's always written in ROM info on any download page I know. you may also adapt product code in your phone later, to fit the ROM you wish to use (in case you insist on FOTA/Kies updates).
2. *#272*IMEI# changes your product code. Remember that it wipes all your data.
3. Branded FW may include additional apps but also lot of operator's useless trash. Personally I never use branded ROMs and always suggest debranding. Check thread about chosen ROM for more info.
Sent from my GT-I9100 using Tapatalk 2
gaeilge said:
1. Be sure that ROM was released for the region/carrier which fits product code set in your phone - it's always written in ROM info on any download page I know. you may also adapt product code in your phone later, to fit the ROM you wish to use (in case you insist on FOTA/Kies updates).
2. *#272*IMEI# changes your product code. Remember that it wipes all your data.
3. Branded FW may include additional apps but also lot of operator's useless trash. Personally I never use branded ROMs and always suggest debranding. Check thread about chosen ROM for more info.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, Re #2, it seems strange that although I never used that command to change my code, only flashed a stock rom issued for another region a while ago, now the checkfus says my handset's the regional code that fits this new rom, other than the supposed-to-be australian one.
Is this normal? So the flashing process can actually alter the phone prod. region code without warning me?
Theoretically it shouldn't but s... happens. If you were flashing ROMs in which your product code wasn't available then it could adjust itself. Mostly I've seen situations when after such an ROM update, PC just wasn't available for change but it stayed the same as it was. On the second hand I've also heard about few cases like yours. Anyway, are you sure about your original PC if you never used this code option? Maybe originally it was different than you think it ought to be?
Sent from my GT-I9100 using Tapatalk 2
You can also try www.sammobile.com for stock firmware. Just make sure that you input your device and region correctly
Edit : and you'll have to flash through odin
Sent from my GT-I9100 using xda premium
gaeilge said:
Theoretically it shouldn't but s... happens. If you were flashing ROMs in which your product code wasn't available then it could adjust itself. Mostly I've seen situations when after such an ROM update, PC just wasn't available for change but it stayed the same as it was. On the second hand I've also heard about few cases like yours. Anyway, are you sure about your original PC if you never used this code option? Maybe originally it was different than you think it ought to be?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Strange!
1. I use *#1234# command and found my rom info is I9100ZSLPG, which is for the region Hongkong - TGY
2. then I use *#272*imei#* (Product code) to check my phone's current CSC, which is shown already 'TGY'.
Now my question is, why my phone still can't get any OTA update?
Any other bit not matched? How to check if any?
Thanks.

[Q] Mixing stock ROMS and basebands

Hi All,
I have just flashed the Generic AU rom for my Z2, and would like to know if I can now just flash the baseband from my Telco's AU rom. That way I would have the best of both worlds - no bloat and a fine tuned baseband.
Cheers
Doesn't make much sense to me. The D6503 (and 02) is a global model, I believe that all firmwares have the same baseband. For example: The latest firmware 23.1.A.1.28 has the 8974-AAAAANPZQ-00038-40 baseand. The US, GEL and ES firmwares they all have the same baseband number. (I've tested them all)
Ah no worries, thanks for the reply. I've only ever had Samsung and htc phones and the different carriers in Australia all had different radios on the same phone.
I can flash with impunity now, and that makes me happy!

Categories

Resources