Related
I have flashed my x10a,but it still at times lags for quite a while,and mysteriously powers off. I see that the new at&t update carries the baseband of 2.1.60. Will this possibly help with the problems that I am having right now? Downloaded 2.1.0435 from xda,which is generic 2.1. I love my phone regardless,I just want to solve some of these niggling problems.
Thank you devs,for all your help in the past and present. I'm new to this,and the tech talk at times goes WAY over my head. But,with the help from you and YouTube,I flashed my mobile three months ago and glad that I did.
Now,all I am looking forward for at&t to roll out the Arc,which I am DYING FOR!!
http://forum.xda-developers.com/showthread.php?t=934486&highlight=speed+up+2.1 enjoy a MUCH speedier 2.1 after youre done will all that
How many times are you going to post about baseband 2.1.60 advertised on SE website that has been proven to be wrong or outdated. First, SE doesn't talk about baseband numbers regarding updates, they use firmware numbers, because the baseband is included in the firmware. The AT&T X10a update is firmware 2.1.A.0.492, which comes with baseband 2.1.65.
2.1.60 would be going backwards in numbers. By using the ATT branded update you are using 2.1.65 which limits data from H to 3G, and has known text message problems.
We are all using X10a 2.1.A.0.435 global generic firmware which comes with baseband 2.1.54 on xda, and we don't have any glitches. Be more specific.
agentJBM said:
How many times are you going to post about baseband 2.1.60 advertised on SE website that has been proven to be wrong or outdated. First, SE doesn't talk about baseband numbers regarding updates, they use firmware numbers, because the baseband is included in the firmware. The AT&T X10a update is firmware 2.1.A.0.492, which comes with baseband 2.1.65.
2.1.60 would be going backwards in numbers. By using the ATT branded update you are using 2.1.65 which limits data from H to 3G, and has known text message problems.
We are all using 2.1.A.0.435 generic firmware on xda, and we don't have any glitches. Be more specific.
Click to expand...
Click to collapse
YOU need to chill out he probably got software version confused with baseband so chill out, everyone here was a NEWB at one time yes even YOU so relax...
leo5111 said:
YOU need to chill out he probably got software version confused with baseband so chill out, everyone here was a NEWB at one time yes even YOU so relax...
Click to expand...
Click to collapse
I have told him 5 different times in 5 different threads that baseband 2.1.60 doesn't exist, but because he saw a screen shot with baseband 2.1.60 he thinks it is real.
He has waited weeks to update via SEUS or PC Companion, because he wants confirmation of baseband 2.1.60.
Please tell him to update himself and see himself. Please.
frothe3 said:
I have flashed my x10a,but it still at times lags for quite a while,and mysteriously powers off. I see that the new at&t update carries the baseband of 2.1.60. Will this possibly help with the problems that I am having right now? Downloaded 2.1.0435 from xda,which is generic 2.1. I love my phone regardless,I just want to solve some of these niggling problems.
Thank you devs,for all your help in the past and present. I'm new to this,and the tech talk at times goes WAY over my head. But,with the help from you and YouTube,I flashed my mobile three months ago and glad that I did.
Now,all I am looking forward for at&t to roll out the Arc,which I am DYING FOR!!
Click to expand...
Click to collapse
if you think there is a baseband 2.1.60, no idea where you saw it but there is NOT a 2.1.60 baseband here is a baseband list http://forum.xda-developers.com/showthread.php?t=960527
leo5111 said:
if you think there is a baseband 2.1.60, no idea where you saw it but there is NOT a 2.1.60 baseband here is a baseband list http://forum.xda-developers.com/showthread.php?t=960527
Click to expand...
Click to collapse
Thank you for confirming, leo.
@Frothe, you are making things too complicated. If you are having a problem different from everyone else, then it is something you did not the firmware....
agentJBM said:
Thank you for confirming, leo.
@Frothe, you are making things too complicated. If you are having a problem different from everyone else, then it is something you did not the firmware....
Click to expand...
Click to collapse
no problem i didnt realise you had let him know in 5 other threads or i would have posted what i did in my last post
Woah! I'm just going by what I saw posted somewhere online! I have a few issues with my phone and thought maybe someone on here could guide me. Yes, I am new to this! Don't attack me for not knowing the proper information, etc., since I am NOT a tech wiz. That is why I come on here for tech support, info on how to make my mobile work for ME! I know there are some software issues that I need to advice on, since the phone randomly powers off, poor response, etc.
Sent from my X10a using XDA App
@JBM;I DO have glitches, and I downloaded the flashtool From xda. I posted my glitches in a previous post on this thread. What I may not have been SPECIFIC is that I used SEUS to get the mobile to work, which it does. But it has so many issues, and have read several different threads on here, that I need HELP for MY concerns.
Sent from my X10a using XDA App
It could be a third party app like a task killer set up too aggressive, among others.
if you are on 2.1 follow this guide will speed up youre phone ALOT ... http://forum.xda-developers.com/showthread.php?t=934486&highlight=speed+up+2.1
Can we use some of the mods in the global sgs dev forum? I know we cant use anything that would change the modem but since the phones are very similar what can and what cant we use from the global Dev forum?
Thanks
As best as I understand the big ones to stay away from are modems, kernels, and bootloaders. As long as you don't mess with bootloaders you'll always have download mode (not that bootloaders by definition are incompatible, but 99% of what is done on a phone should not include messing with bootloaders, unnecessary risk for most people)
Just keep in mind using anything from a different phone is a risk that could make you lose all yours files and apps or worse.
People have accidentally flashed international roms and been able to recover, though it can be an uphill battle for some.
Sent from my SAMSUNG-SGH-I777 using XDA App
Hi,
I would like to know if I can change the baseband on my SGH-I777 from UCKH7 to UHKE2??? Currently the phone is like this:
PDA: I777UCKH7
PHONE: I777UCKH
CSC: I777ATTKH7
My goal is to enable CR carrier options on this phone. Is this possible? Please advice.
Thanks in advance
---------- Post added at 11:51 AM ---------- Previous post was at 11:34 AM ----------
gacuna said:
Hi,
I would like to know if I can change the baseband on my SGH-I777 from UCKH7 to UHKE2??? Currently the phone is like this:
PDA: I777UCKH7
PHONE: I777UCKH
CSC: I777ATTKH7
My goal is to enable CR carrier options on this phone. Is this possible? Please advice.
Thanks in advance
Click to expand...
Click to collapse
Basically what I want to know is if changing the baseband the phone would be able to support "video calling" without using a 3rd party app, just by calling. Like the Global/International SG-I9100.
I see my friend's phone has baseband UHKE2, please advice if changing this, it would make any diff.
Pretty sure your modem isn't going to get the result you want.
Sent from my HTC PH39100
So there's no way at all to make video calls with the SGH-I777 like a normal voice call??? Just like the SG-I9100???
I haven't checked out a i9100 at all, nut I do remember er on my i897 captivate when running an i9000 ported rom we would have the call screen with the video button (until a dev for the i897 removed it). I believe it is part of the phone.apk and another .apk that had to be changed.
So I guessing it is the same on the 9100? Maybe ask one of the devs that have ported over a i9100 rom for us. I think DG is using a i9100 rom as well as the Hellraised rom too (I haven't even looked at these roms but I think they are using i9100 roms with some changes).
This would be a really nice feature too in my opinion. Not sure why it wouldn't work for us also. The reason it had to be removed from the i897 Captivate is it didn't have a front facing camera and the i9000 did. So hope you get it figured out.
Sent From My KickAss ATT SGS2 SPORTING CM7
Thanks for the explanation!
But i havent got it yet, so you say i wont be able to make at&t phone work as the international one? Please dont use too much tech words cause im pretty new using android so i get confused
well then you shouldnt be randomly flashing modems... its a good way to get yourself in a very, very deep hole. especially if you dont know how to get out. id suggest doing some research on what modems do... you cant change the modem and get video calling. here is a very brief explanation of what is going on.
everything on your phone is an app. just like windows has .exe android has .apk. the launcher, calendar, phone, update services and everything runs as a .apk. so when you hit the phone symbol on your launcher you are opening up an app. that app is called the phone app and is on your phone as a phone.apk. to get this video calling capabilities you would need to fins a phone.apk that supports it... but ait there's more. the phone.apk is tied into other things like telephony.apk which does stuff. and other apks, and heck een the framework (its hard to describe this one). if this video calling is specific to samsung, which i think it is, you need to have the samsung rom because you cant just take the phone.apk and make it work, it relies on other things specific to the samsung rom.
having said that, you can find a i9000 rom that has it and hellbreak it but that is a lot more complicated than i think a new guy to android can handle.
It may be that there's a dependency between the phone app and the modem.
I have the video calling button since I'm running Hellraised VillainROM but I have never tried it.
Most likely AT&T's network doesn't support it and will block attempts to use it.
If there are any modem or network dependencies it won't work.
I've been jumping from rom to rom. The previous owner rooted this phone with cm7.1, gps is working fine. Then i jumped to cm9. The gps does detect any satelite. So i jump from one rom to another. Now i am with extreme legend. I saw some people saying bout radio image. Where can i get the latest version. Please i need gps, i am a new driver
Sent from my Legend using XDA
madness8878 said:
I've been jumping from rom to rom. The previous owner rooted this phone with cm7.1, gps is working fine. Then i jumped to cm9. The gps does detect any satelite. So i jump from one rom to another. Now i am with extreme legend. I saw some people saying bout radio image. Where can i get the latest version. Please i need gps, i am a new driver
Sent from my Legend using XDA
Click to expand...
Click to collapse
In my experience last cm7.2 works well with agps (gps and data enabled) and it's tooo slow without data enabled.
In zeubea's cm9 gps seems not to work at all in latest release, at least in my case, fixs satellites but don't lock your position, with data enabled estimates your location considering umts or wifi (precision more than 600 meters).
I'm using 47.51.35.17U_7.13.35.05 but I'm not sure it makes difference.
I have the best experience with Blay0's ROM B 0.8.4 ( forum.xda-developers.com/showthread.php?t=866849 ). When I had a GPS-fix in the last time, I get a new fix in 10-15 seconds. The app GpsFix (market link) helps to get a short fix time.
I'm using legend.radio-47.51.35.17_7.13.35.05.
gianlen said:
In my experience last cm7.2 works well with agps (gps and data enabled) and it's tooo slow without data enabled.
In zeubea's cm9 gps seems not to work at all in latest release, at least in my case, fixs satellites but don't lock your position, with data enabled estimates your location considering umts or wifi (precision more than 600 meters).
I'm using 47.51.35.17U_7.13.35.05 but I'm not sure it makes difference.
Click to expand...
Click to collapse
I am using agps. But when I use waze, my location is just estimated.. It says no satellite found..
alligator_asl said:
I have the best experience with Blay0's ROM B 0.8.4 ( forum.xda-developers.com/showthread.php?t=866849 ). When I had a GPS-fix in the last time, I get a new fix in 10-15 seconds. The app GpsFix (market link) helps to get a short fix time.
I'm using legend.radio-47.51.35.17_7.13.35.05.
Click to expand...
Click to collapse
I am afraid that the gps might still not working after I jump to Blay0's Rom
make a nanroid backup and try it - when it does not work for you, you can go back immediately.
CyanogenMod 7.2 stable - GPS problems
I just installed CM 7.2 on a few HTC Legend phones, only to find that with their radio, version 47.26.35.04_7.05.35.26L, the GPS does not work with CM 7.2 at all. When I start a program that tries to use the GPS, nothing happens. Not even the GPS icon appears in the status bar.
This is strange, because this is the radio version most newer HTC Legend phones come with.
I downgraded the radio to the next-older version I could find, 47.39.35.09_7.08.35.21. With this the GPS icon starts to blink, but never gets a fix. However, after I reboot the phone, it works. It still takes a relatively long time, at least a minute, to get a first fix, but works better afterwards.
This is a bad trap, because somebody who does not try the reboot trick may come to the wrong conclusion that this radio does not work with CM 7.2 and flash an unnecessarily old radio.
I have stopped testing and wanted to ask here first whether anybody has already done some more thorough tests with different radio versions and found which one works best, not only concerning the GPS, but also all the other radio functions. Which radio should I flash with CyanogenMod 7.2?
hgmichna said:
I just installed CM 7.2 on a few HTC Legend phones, only to find that with their radio, version 47.26.35.04_7.05.35.26L, the GPS does not work with CM 7.2 at all. When I start a program that tries to use the GPS, nothing happens. Not even the GPS icon appears in the status bar.
This is strange, because this is the radio version most newer HTC Legend phones come with.
I downgraded the radio to the next-older version I could find, 47.26.35.04_7.05.35.26L . With this the GPS icon starts to blink, but never gets a fix. However, after I reboot the phone, it works. It still takes a relatively long time, at least a minute, to get a first fix, but works better afterwards.
This is a bad trap, because somebody who does not try the reboot trick may come to the wrong conclusion that this radio does not work with CM 7.2 and flash an unnecessarily old radio.
I have stopped testing and wanted to ask here first whether anybody has already done some more thorough tests with different radio versions and found which one works best, not only concerning the GPS, but also all the other radio functions. Which radio should I flash with CyanogenMod 7.2?
Click to expand...
Click to collapse
I don't know where your getting your information from, but its very out dated.
Radio version
47.26.35.04_7.05.35.26L is from what I could find out is the first radio for legend, Radio_47.39.35.09_7.08.35.21
is the second version released, there has been 2 even newer versions released since
Radio_47.51.35.17H_7.13.35.05
&
Radio_47.54.35.20U_7.13.35.13, this one I believe is supposed to be only for America.
If you look in the dev section you will find those 2 newer versions.
Its a pitty that there is no change log available to find out what the difference is between them all.
Sent from my Legend using XDA
ranger4740 said:
Radio version
47.26.35.04_7.05.35.26L is from what I could find out is the first radio for legend, Radio_47.39.35.09_7.08.35.21
is the second version released, there has been 2 even newer versions released since
Radio_47.51.35.17H_7.13.35.05
&
Radio_47.54.35.20U_7.13.35.13, this one I believe is supposed to be only for America.
If you look in the dev section you will find those 2 newer versions.
Its a pitty that there is no change log available to find out what the difference is between them all.
Click to expand...
Click to collapse
What about the version "update_Legend_Radio_7.51.35.17.zip" ?
alligator_asl said:
What about the version "update_Legend_Radio_7.51.35.17.zip" ?
Click to expand...
Click to collapse
is my info out of date too?
I've not seen any info or links about an even newer radio version than those I've posted. Will check it out thanks.
Edit-: are you sure this is legit?
There is only 3 pages including this thread on a google search. Very suspicious to me..
Sent from my Legend using XDA
alligator_asl said:
make a nanroid backup and try it - when it does not work for you, you can go back immediately.
Click to expand...
Click to collapse
A Nandroid backup does not contain the radio.
Apparently the radio firmware is considered as closer to the hardware than to the software, too close to include it in a backup.
---------- Post added at 01:16 PM ---------- Previous post was at 12:52 PM ----------
ranger4740 said:
is my info out of date too?
I've not seen any info or links about an even newer radio version than those I've posted. Will check it out thanks.
Edit-: are you sure this is legit?
There is only 3 pages including this thread on a google search. Very suspicious to me..
Click to expand...
Click to collapse
I had an old, semi-defective Legend and tried the apparently newer 7.51.35.17.zip radio on it. It works very well. Unlike some older radios it got a GPS fix at first try.
The ZIP package has the same structure as the other ones, so if it contains malware, it would have to be in the radio.img file.
My first guess is that, if somebody wanted to write Android malware, he would not start with a software component that is specific to one meanwhile oldish phone and then not care whether it remains mostly unknown. No proof, of course, but I will flash this radio into a couple of Legends and see how it goes.
Another observation: The radio version numbers consist of four numbers, similar to an IP address. However, the first number is always 7, and the third number is always 35. This indicates to me that this is not a hierarchical number, raising the question whether the second or the fourth number is the better indication of progress. What if the second number is just some code for some other characteristic? In that case ...35.26L would be the latest and greatest.
Actually I tend to think that the second number counts up the version. If so, then 7.51 would be a lot newer than any of the others.
hgmichna said:
A Nandroid backup does not contain the radio.
Apparently the radio firmware is considered as closer to the hardware than to the software, too close to include it in a backup.
---------- Post added at 01:16 PM ---------- Previous post was at 12:52 PM ----------
I had an old, semi-defective Legend and tried the apparently newer 7.51.35.17.zip radio on it. It works very well. Unlike some older radios it got a GPS fix at first try.
The ZIP package has the same structure as the other ones, so if it contains malware, it would have to be in the radio.img file.
My first guess is that, if somebody wanted to write Android malware, he would not start with a software component that is specific to one meanwhile oldish phone and then not care whether it remains mostly unknown. No proof, of course, but I will flash this radio into a couple of Legends and see how it goes.
Another observation: The radio version numbers consist of four numbers, similar to an IP address. However, the first number is always 7, and the third number is always 35. This indicates to me that this is not a hierarchical number, raising the question whether the second or the fourth number is the better indication of progress. What if the second number is just some code for some other characteristic? In that case ...35.26L would be the latest and greatest.
Actually I tend to think that the second number counts up the version. If so, then 7.51 would be a lot newer than any of the others.
Click to expand...
Click to collapse
I have read on other threads for lots of other android phones that if you flash wrong radio firmware it will destroy your phone.
The malware side is if it is fake, then flashing it would distroy the phone and you wouldn't get it back.
Sent from my Legend using XDA
ranger4740 said:
I have read on other threads for lots of other android phones that if you flash wrong radio firmware it will destroy your phone.
Click to expand...
Click to collapse
True, but I have just flashed 7.51.35.17 on three HTC Legend phones (a fourth to follow soon), and they all work very well. I have pulled this chestnut out of the fire for you already.
Zubea CM9Beta3
Has someone tested the new CM9Beta3?
Cause I have trouble with my GPS with that new Build. When I start a GPS using App, it does not always show a GPS Symbol like it should. Sometimes theres no Symbol, sometimes there is the symbol but its not blinking.
And the next is, when I end the GPS usign app the symbol remains in its state. Disable and Endable the GPS doesnt change anything on the Symbol but the App tells me that the GPS is disabled.
So is it just the Symbol wich is bugged or also the GPS? Cause it takes veery long.
When I remember Right the problem wasnt there on Beta1 or 2.
Any Ideas?
I've just compared the radio.img inside the versions 7.13.35.05 and 7.51.35.17 ... they are identical! I think, someone made a joke ...
alligator_asl said:
I've just compared the radio.img inside the versions 7.13.35.05 and 7.51.35.17 ... they are identical! I think, someone made a joke ...
Click to expand...
Click to collapse
U're funny!
The name of this Radio is : 47.51.35.17_7.13.35.05. They are identical cause they are the same!
treecity said:
The name of this Radio is : 47.51.35.17_7.13.35.05. They are identical cause they are the same!
Click to expand...
Click to collapse
OK, but we should never give up the search ...
treecity said:
U're funny!
The name of this Radio is : 47.51.35.17_7.13.35.05. They are identical cause they are the same!
Click to expand...
Click to collapse
Oh, so ugly! Anyway, this is the same radio then that we want to have installed anyway.
ranger4740 - you had exactly the right gut feeling. Fortunately the whole thing was harmless.
hgmichna said:
Oh, so ugly! Anyway, this is the same radio then that we want to have installed anyway.
ranger4740 - you had exactly the right gut feeling. Fortunately the whole thing was harmless.
Click to expand...
Click to collapse
After looking at the version numbers for a while I had the feeling that they were the same, the "new" radio had the number 4 missing from the version number lol maybe the op made a honest mistake by leaving it out, the number 4 that is...
Sent from my Legend using XDA
treecity said:
Has someone tested the new CM9Beta3?
Cause I have trouble with my GPS with that new Build. When I start a GPS using App, it does not always show a GPS Symbol like it should. Sometimes theres no Symbol, sometimes there is the symbol but its not blinking.
And the next is, when I end the GPS usign app the symbol remains in its state. Disable and Endable the GPS doesnt change anything on the Symbol but the App tells me that the GPS is disabled.
So is it just the Symbol wich is bugged or also the GPS? Cause it takes veery long.
When I remember Right the problem wasnt there on Beta1 or 2.
Any Ideas?
Click to expand...
Click to collapse
My very first try of GPS on beta 3, it took 218 seconds for lock, this was in the dash of my car driving along.
Btw that was without any mods or "GPS fixes"... straight out of the box.
Sent from my Legend using XDA
Hello, I've flashed the Cyanogen mod for my Samsung Galaxy S2? I've been using it, it works fine.
I'm wondering, do I need to flash a radio? If so, which one? I've seen the links of radios from the Wiki page of Cyanogen under Support Downloads, just don't known which one to use or if I'm supposed to.
Thanks for your help.
Radio is not changed by CyanogenMod.
If you have no call, sms or data issues then i dont think you need to change
-Grift- said:
If you have no call, sms or data issues then i dont think you need to change
Click to expand...
Click to collapse
OK, thanks for your help.
I have successfully installed this rom. I think it's the most amazing jelly bean rom for galaxy s2 at the moment. I like its smoothing and quick response. feel a bit warm at the back and the battery is losing 1% at every minute while wifi is on. Over all is great. Cheers!
Actually, I've been experiencing data connection problems. My phone works, but it won't connect to 2g/3g for internet.
Should I try switching radios?
If so, which one is recommended? Or do you just try them at random?
Thanks again
On first boot normally can't get mobile data to work because APN was not configured properly (or the list empty), after a reboot mobile data will work again. If it doesn't, then you have to key in the APN manually.
For radio/modem, since there are no changelog released and nobody know what are the differences among them, it is assumed that the latest one will be better.
HTCOrangeCat said:
Actually, I've been experiencing data connection problems. My phone works, but it won't connect to 2g/3g for internet.
Should I try switching radios?
If so, which one is recommended? Or do you just try them at random?
Thanks again
Click to expand...
Click to collapse
first and foremost asking or recomending which ROM/KERNEL/MODEM ,is against XDA rules, since all phones are different due to various reasons , hence if u have a an issue with ur modem u have to try a cpl of them on ur own and see the one suits u the best.
link for the same below.
Modem Collection
OK. I'll try a few different radios. I see a list of links in the Cyanogen Wiki page of under Support Downloads.
Thanks for the quick replies!
HTCOrangeCat said:
OK. I'll try a few different radios. I see a list of links in the Cyanogen Wiki page of under Support Downloads.
Thanks for the quick replies!
Click to expand...
Click to collapse
It sounds like your apn settings are messed up. Try to reboot twice and then try. If that doesn't work, you will have to find the settings and input them manually.
Sent from my GT-I9100 using xda premium
After trying over 30 radios I always end up on nelp3. Best signal best data thoroughput and best for battery life.
Sent from my resurrection remixed GT-I9100 using xda app-developers app
Thanks everyone! The radio did it!
I flashed this radio:
galaxys2.radio-XXKDH-signed
Now, the data, 3G, works great.
I've been experiencing an issue and have read several post about RADIOS on the SGS2.
I flashed my mobile with the nightly 10.2 CM and after that it started to ask me for "SIM network UNLOCK" Which I can't unlocked, thought it was the version issue so I dl a the newest one and same issue, I tried the ICS stable 9.1 and same issue.
I've read something like radios on the CM support part. Which I dunno where is it yet . If I need to flash it and u guys can help me out to pick up the correct one I'll appreciate it. my model of SGS2 is the i777 from AT&T.
May I install NELP on my CM 9.1? how? where can I get the files to do it?
I777 modem collection
http://forum.xda-developers.com/showthread.php?t=1361393
Sent from my GT-N7105 using xda app-developers app
Issues
Hello everyone. I tried many modems (XXLS8, NELP4, XXKI4, BVLP7 etc.) but each of them had some different issue. First was loosing network, with second the front speaker stopped working... Just noone worked fine :\ I don't know what to do yet! Any advices?
ac.dc.76 said:
Hello everyone. I tried many modems (XXLS8, NELP4, XXKI4, BVLP7 etc.) but each of them had some different issue. First was loosing network, with second the front speaker stopped working... Just noone worked fine :\ I don't know what to do yet! Any advices?
Click to expand...
Click to collapse
What phone do you have? This is the thread for the i777 S2 variant, and at least one of the modems you mentioned are for the i9100 variant (don't recognize the others you list).
You can only use modems designed for your device, so if you have an i777 see the link directly above your post.
SteveMurphy said:
What phone do you have? This is the thread for the i777 S2 variant, and at least one of the modems you mentioned are for the i9100 variant (don't recognize the others you list).
You can only use modems designed for your device, so if you have an i777 see the link directly above your post.
Click to expand...
Click to collapse
Sorry, wrong thread. Hadn't time to ask for delete my post :\
Hi,
Search everywhere and still stuck!
This is issue that I have bee trying to solve on the 'android-rsap' forum, but am completely stuck, so by posting here I am hoping that someone can shed some light on what is going on.
Link: forum.android-rsap.com/viewtopic.php?f=32&t=871
In short, the device is a Samsung Galaxy 2 (XEU), and the bluetooth rsap functionality works fine with 4.0.4 (I9100XWLPT) but when I upgrade to 4.1.2 (I9100XWLSW) it no longer works at all. What is most weird is that it seems to be only my handset that is affected, it does not seem to be a universal issue. :roll eyes: What could be specific to my handset that stops this functionality working as it should?
I have been going back to 4.0.4 and upgraded to 4.1.2. many times now, via OTA, Kies and Odin, same result every time, sadly. 4.0.4 works every time, 4.1.2 has never worked with rsap and my car
What could be specific to my handset that stops this functionality working as it should? I have tried root'ing the handset to do more testing and to try the rsap app from Google App Store, but that has the same issue. Could some of the radio software be wrong? or?
Picture shows Kies upgrade screen and the 4.0.4 and 4.1.2 versions I am getting.
Any hints would be appreciated.
Regards,
J.
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
gastonw said:
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, so with an XEU handset - what version would you recommend?
realist42 said:
Ok, so with an XEU handset - what version would you recommend?
Click to expand...
Click to collapse
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
..
realist42 said:
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
Click to expand...
Click to collapse
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
realist42 said:
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
Click to expand...
Click to collapse
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Repporte Redan
king_below_my_lord said:
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
HI,
Took a little time to get the phone back in order and then to go an do the trace.
Not knowing what I am really looking for, but it strikes me that the bluetooth stack looks to just be giving up...
Regards,
J.
Hi all,
Well, today I managers to briefly borrow another S2 handset with JB on it. This other handset has the same issues that I have, so this must be something in the packaging of the Bluetooth that Samsung did - but I am guessing here.
Any clues would be appreciated, although I think I am fighting a loosing battle here... (works with an S3, so I should go and upgrade! at least chapter now that there is the S4 - but I like the form factor of the S2 better)
Regards,
J
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Well, thanks for looking anyway...
My thinking on this is now that as it works with newer cars and only the older ones that now have issues, it must be a version issue, i.e. the version of the bluetooth stack is not the one it should be. It would be interesting to know if there is a difference in the version of the bluetooth stack and the rsap daemon between the S3 (which works on JB) and the S2 (which does not). Would that tell me anything interesting?
Regards,
J.
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
djshotty said:
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
Click to expand...
Click to collapse
HI,
I was not aware of this, and are you saying this is specific to the S2, so the fact that is works with an S3 on 4.1.2 is irrelevant?
J.
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
djshotty said:
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
Click to expand...
Click to collapse
Well, my issues are with specifically with rsap, not really A2DP, but if it affects the whole stack, this could be an issue.
To illustrate: I have 2 cars, one older, one newer. With the newer car all is well, and it works at is should (as far as I know) The older car was working pretty much with out issues on 4.0.4, but refuses to work with 4.1.2. Both cars rely on rsap.
Not sure this helps, just wanted to illustrate the problem that I am trying to solve.
Regards,
J.
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
djshotty said:
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
Click to expand...
Click to collapse
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
realist42 said:
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
Click to expand...
Click to collapse
That's why I suggested you look at the forum I provided the link for, there are plenty with the 'Phone calls via Bluetooth into car stereo' issue, including myself...