Related
I am no Noob to Android, but am to Samsung phones. This is my first time ever encountering kernels and modems that could be flashed separately. All other Android devices I used had everything together as a single package and did not offer a kernel and modem separately.
That said, I am trying to determine a solution for a frustration of mine. I want the newest Gingerbread 2.3.6 version for my ATT Galaxy S2 (NOT Skyrocket), but every time I check for updates, my phone says that I am up to date already. Yet, there have been three newer firmware versions leaked and I dont know what this means, but I am wondering if ATT is leaving me in the dust or something.
I have tried all three of the leaked updates (UCKJ1, J2, and J4), and although the phone works perfectly fine, all versions give me an impossible to deal with problem when I am in a call with someone. The problem is that no matter who I am talking to, they all complain that they cannot hear me because my voice is randomly fading in and out to the point where they cannot hear me at all. Strangely though, when I am on UCKH7, everyone says that I come in nice and clear and no one ever complains about clarity.
So, I was wondering first, what controls the calling portion of the firmware/
ROM? I was thinking that it was the modem, but when I think of modems, I think of something controlling internet, like 3/4G and wifi.
Second, if it IS the modem that controls the calling, then what would happen if I flashed the UCKJ4 firmware and the UCKH7 modem? Will everything work?
I was thinking that since H7 seems to be the only version that doesnt give me voice problems, then by using its modem with the J4 kernel, I could have the newest firmware, but still have people hear me.
If anyone knowledgeable in this area could help me, that would be ridiculously awesome! I dont want to try this unless I am sure that I wont brick my phone or something.
BTW, the voice problem is not caused by finger over microphone or my or the other party's reception. I have tested this as thoroughly as possible and it is definitely the firmwares for some reason.
1) your modem controls both the calls and data connection.
2) you can flash the stock KH7 modem:
http://forum.xda-developers.com/showthread.php?t=1336958&highlight=UCKH7+modem
you can do this without changing your rom or kernel. Hope that fixes your call issues (sounds like it will).
Modem controls calls and data connection, however the Samsung Noise Reduction feature is in the audio libraries within /system and to some degree in the kernel (sound drivers)
Ok, so the modem does handle calls then. Thats good to know!
For the record though, the noise suppression feature seems to have no affect on this problem of mine. It doesn't matter whether it is on or not :-\
I am CURRENTLY running KH7 modem AND kernel and no problems right now.
Soooooo... What would happen if I flashed the J4 kernel, but the KH7 modem though?
Will things work right (data, wifi, phone calls, system stability, etc)? Will I lose noise suppression?
LOL, thanks for the replies so far, but my questions were only half-answered. (Probably too much text in my OP... sorry!)
Sent from my SAMSUNG-SGH-I777 using XDA App
spexwood said:
Ok, so the modem does handle calls then. Thats good to know!
For the record though, the noise suppression feature seems to have no affect on this problem of mine. It doesn't matter whether it is on or not :-\
I am CURRENTLY running KH7 modem AND kernel and no problems right now.
Soooooo... What would happen if I flashed the J4 kernel, but the KH7 modem though?
Will things work right (data, wifi, phone calls, system stability, etc)? Will I lose noise suppression?
LOL, thanks for the replies so far, but my questions were only half-answered. (Probably too much text in my OP... sorry!)
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Most likely not much - the only case where you're likely to notice a change is if you flash my kernel, which pulled in the I9100's latest sound driver a few days ago.
Please forgive me for not fully understanding all of this.... -_-'
So, it isn't worth it to flash the J4 kernel (in order to get Gingerbread 2.3.6) and the H7 modem (to keep my phone calls clear)?
If I flashed your kernel though, how would it affect my phone?
Will I be at 2.3.6?
Would I flash your kernel, but keep the H7 modem?
Also, can you provide a link to your kernel (to make sure I find the same thing you are talking about)?
Again, forgive me for not understanding right away.
Sent from my SAMSUNG-SGH-I777 using XDA App
i bought a used i777 that was advertised to be unlocked, but when i put in my t-mobile (straight talk) sim card to test out, phone was not unlocked so couldn't really test it out. it looked new so i bought it, then called at&t for an unlock code. after i entered code and called someone, i couldn't hear them and they couldn't hear me. phone was running 2.3.6 and after doing alot of research online, i first checked the flash counter (which was zero) then followed 'creepyncrawly' (cnc) thread 'how to prepare phone for return' and flashed the UCKH7-CL503881 stock kernel and system package using odin, then followed 'jack man' thread to upgrade to ics (4.0.3) but still have audio problems.
ok, so why i am i posting this? couple reasons actually. first, if i could ever get the I777_UCKH7_OCD_Root_No_BL.7z file to download before timing out (then having to wait another 30 mins before trying again!) then i would've followed cnc's thread 'How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!!' i'm also thinking of trying entropy512's 'UCKH7/KK6 Return/Unbrick to Stock (or Root)'. also thinking about using the 'AOKP ICS ROM v7.1', but am thinking i am just missing a file or have a bad rom or something simple that is causing my audio problems because i found this in the q&a section for i777 under thread titled 'no audio on phone':
Here is the stock i777 modem (phone) TAR file.
Your audio shall magically return after you flash this:
{ link, but i can't post here because i'm a nooby } <---------- BUT THIS LINK HAS BEEN SEIZED BY THE FEDS!
You will need to flash this in Odin.
Be sure to put this in the PDA slot in Odin.
and although i'm using terms like 'root', 'kernel', rom, etc., i really don't know what the benefits are of rooting, changing rom, etc.
also, the threads referenced above are dated oct 2011 -- almost a year ago and wonder if i should use something more recent.
finally, i'm sure this is gonna sound real stupid, but can someone please tell me where the 'sticky' section is? i see alot of people here say 'i'm sure there's a sticky for this' in the dev section or general section, etc. but am not sure where these stickies can be found.
and yes, i watched the nooby video and know i'm supposed to be brief but wanted to be thorough in describing what i've done and where i'm hungup now before moving forward.
thanks in advance for any insight/assistance with this frustrating condition of my first i777!
Off market purchase can lead to an intimidating amount of Grey area in trouble shooting. I've read of changes in hardware, and boot loaders in a single device over time in production, and off the top of my head, I question the method the seller used to prep the phone for sale. Could have used triangle away for the counter, simply flashed stock rom, and removed root. May have been an incompatible rom. If he said it was unlocked and it wasn't, he either didn't know what he was taking about, or obviously changed something afterwards. You're basically trying to figure out what someone else did wrong, and that's a *****. Were it myself, I'd go with entropy's most recent stock you can find, and if not that, hunt down the potential changes to the production of the phone, and sequentially try stock flashes coinciding with the possible time frames. I expect there's going to be a lot of more helpful advice for you in the future, but I hope these basics might help
Sent from my SGH-I777 using xda premium
The "stickies" are the threads at the top of each section that have a thumbtack icon to the left of the thread title. There are usually 4 to 5 (or more) stickies per section for our phone, and are usually the most important things to remember regarding issues, flashing, etc. They are "stuck" to the top area of each section so people can see/find them easily.
Before doing anything more to your phone u need to spend time reading and understanding what u read. And searching terms you aren't familiar with. I find myself saying this more and more, and it seems redundant. But it's also just common sense. Good luck.
Sent from Team Pirate Headquarters. AKA yer moms basement.
Phalanx7621 said:
Before doing anything more to your phone u need to spend time reading and understanding what u read. And searching terms you aren't familiar with. I find myself saying this more and more, and it seems redundant. But it's also just common sense. Good luck.
Sent from Team Pirate Headquarters. AKA yer moms basement.
Click to expand...
Click to collapse
I agree with Phalanx here - do some in depth reading of the stickies you were pointed to, as that will be your best source of information.
If you are ONLY having audio issues (as in, the phone works fine other than you are not able to hear callers, they are not able to hear you), my first guess as to your issue is that the previous owner flashed a custom kernel with the wrong mic. setup. As you read through the stickies, you will learn about mic-swap vs. non-mic-swap kernels, and when it is appropriate to use each.
It would likely be helpful if you could post the information contained here: menu>system settings>about phone.
Good luck.
removed comments -- didn't use multiple quote feature correctly. will re-post comments
Nice quotes..
Cmoore0965 said:
Were it myself, I'd go with entropy's most recent stock you can find, and if not that, hunt down the potential changes to the production of the phone, and sequentially try stock flashes coinciding with the possible time frames.
Click to expand...
Click to collapse
thanks cmoore. i thought when i flashed to UCKH7-CL503881 stock kernel (return to stock by creepyncrawly) that everything would be returned to original build, but maybe 'everything' isn't. i should have tested out phone before moving on to flash to ics (4.0.3) via kies. guess my thinking was that the le5 build would have addressed 'issues' found over time by those using kh7. i will flash the kh7 again, then test out before moving on from there.
jack man said:
The "stickies" are the threads at the top of each section that have a thumbtack icon to the left of the thread title.
Click to expand...
Click to collapse
thanks jack man. turns out i was reading the stickies in both 'general' and 'q/a' sections. guess i just wanted to make sure i wasn't overlooking some other area. seems like alot of threads display what looks like a square yellow sticky -- the thumbtack icon comment clears up my confusion.
Phalanx7621 said:
Before doing anything more to your phone u need to spend time reading and understanding what u read. And searching terms you aren't familiar with.
Click to expand...
Click to collapse
thanks phalanx. i'm trying to correct these audio probs as soon as possible cuz i bought this phone for a handicapped friend who lives on a tight budget and was paying 35/month for std cricket talk/text service. he doesn't have a tv or computer and can't afford tv or internet service anyways. i convinced him to get an i777 smartphone so he could get news, sports, etc. by moving over to 45/month unlimited service with straight talk (i've been using with my t679 t-mobile with ST service and hope to move up to i777 myself soon) but didn't anticipate someone would screw me over with a problematic phone for $200. not trying to waste anyone's time with this thread or clog up an outstanding website (xda), just trying to rectify phone problems to return it to him fixed soon. i agree i have much to learn (i get confused by different terms that have same meaning) and will hold off on rooting and changing rom for now, just wanted to make sure i didn't need to do certain things first to restore some file that i suspect is missing or corrupt and might be needed in addition to files contained in original kh7 build.
dandrumheller said:
If you are ONLY having audio issues (as in, the phone works fine other than you are not able to hear callers, they are not able to hear you), my first guess as to your issue is that the previous owner flashed a custom kernel with the wrong mic. setup. As you read through the stickies, you will learn about mic-swap vs. non-mic-swap kernels, and when it is appropriate to use each.
It would likely be helpful if you could post the information contained here: menu>system settings>about phone.
Click to expand...
Click to collapse
thanks dandrumheller. all problems are audio related, everything else seems fine. speaker does not work for mp3 files, but headphone jack works. during a call, sometimes putting speakerphone on then off works, and when it does an indicator appears that i can't find in user manual. then (while call is still active) i can hear music from mp3 files w/o headphones, but the audio comes through the phone earpiece. then if i turn speakerphone back on (still during active call) the music comes through regular speaker on bottom/back of phone. once the call terminates however, so does the music (stops coming through speaker) but music can still be heard through headphones. very strange stuff!
current settings (but will be going back to kh7 build shortly) baseband: I777UCLE5, kernel version: 3.0.15-I777UCLE5-CL652575 [email protected] #3, build number: IML74K.CLE5
Multi quote would be your friend in this thread
Raise yer mizzenmast and swab 'er poop deck!
i was thinking the 'mic swap' kernel is the key to audio probs (thanks to dandrumheller's comment) but while researching i stumbled on this comment from 'dayv':
"And if you are using a firmware based on an i777 firmware you don't need the mic swap."
and i'm wondering about when I followed creepyncrawly's thread: "Prepare Your Phone to Return ..." and flashed the UCKH7-CL503881 stock kernel and system package using Odin3 One-Click Downloader, shouldn't that already had the necessary kernel (or some other file) already in the stock KH7 build in order to restore phone back to where audio features work normally?
Or, if i do need some additional 'mic swap' kernel, would i need root status to add it? reason i ask is i am about to flash my phone back to the KH7 build and will use the root version this time if necessary: I777UCKH7_OCD_Root_No_BL
Yes the ucle5 ics u downloaded and flashed had a kernel in it that works fine. However, I'd suggest doing what yer doing right now, flashing back to stock and starting over. If u like stock u can even keep it that way. (gingerbread of curse I mean not jellybean)
Sent from Team Pirate Headquarters.
Phalanx7621 said:
Yes the ucle5 ics u downloaded and flashed had a kernel in it that works fine. However, I'd suggest doing what yer doing right now, flashing back to stock and starting over.
Click to expand...
Click to collapse
thanks again phalanx. that is very helpful to know. i will flash the uckh7-cl503881 again using the one click download method and test again
here is the post from dayv regarding mic swap:
dayv said:
The mic swap kernels are needed for Samsung/miui roms that based on i9100 firmwares - the i9100 hardware and i777 hardware are very similar but not exact matches - thus the software drivers in the kernel for the microphones need to be swapped for our microphones to work properly with i9100 firmwares.
And if you are using a firmware based on an i777 firmware you don't need the mic swap.
Now all you need to figure out is which phone the firmware you are using was based on to know whether or not you need the mic swap version of the kernel.
Click to expand...
Click to collapse
and then he added the following comment:
dayv said:
Oh, and the aosp kernel is needed for cm9 and aokp based firmwares - so if you are running cm9 or aokp ROM you need to choose this version of the kernel in question.
Click to expand...
Click to collapse
Random question, had the phone had the audio issues since you you purchased it? I assumed from your post, that you used the phone to handle unlocking with at&t, but I don't see a specific statement attesting to that fact. My train of thought being, that if showed up like that, hardware could be the culprit. Just a thought. Also if not, and this does sound like a kernel mic issue, there are TAR format siyah kernels used to achieve root, which you might try so as to specifically compare results pertinent only to the mic configuration.
Sent from my SGH i777
Could the in call audio be an APN issue? The op states it is used with straight talk.
adfurgerson said:
Could the in call audio be an APN issue? The op states it is used with straight talk.
Click to expand...
Click to collapse
Nah they have to set up the apns before they can even make calls. Without an apn u wouldn't be able to even connect.
Sent from Team Pirate Headquarters. AKA yer moms basement.
Cmoore0965 said:
Random question, had the phone had the audio issues since you you purchased it?
Click to expand...
Click to collapse
thanks again cmoore. when looking at to purchase this 'unlocked' i777 (craigslist) i tried my straight talk sim card (for t-mobile phone) in the i777 but when powering it up it asked for unlock code, so seller said, "oh, i guess it's not unlocked" so i foolishly assumed everything would be fine cuz it looked new and he said all worked fine. like many others here, i've had plenty of good experiences with cl purchases -- up until now. so i activated the straight talk sim card i bought for $15 (for att phone) and had these audio probs from the start.
it had the uckk6 (2.3.6) gb version so i followed creepyncrawly's thread to return to stock and flashed to uckh7. then i followed jack man's thread to flash to ucle5 using kies. then i phoned att and got unlock code and entered it to test ability to use t-mobile sim card so my friend could see which would be strongest signal for data use at his house and also have ability to test phone using both sim cards thinking maybe one was bad, but audio probs are same regardless of which sim card i use -- i bought this phone for his use and am trying to fix the audio probs before giving it back to him cuz he's never had a smartphone and has limited tech abilities, worse than me if you can imagine that!
so i don't really know if it's h/w or s/w, but obviously am hopeful it's s/w and can be corrected once i figure what file may be bad.
Cmoore0965 said:
Also if not, and this does sound like a kernel mic issue, there are TAR format siyah kernels used to achieve root, which you might try so as to specifically compare results pertinent only to the mic configuration.
Click to expand...
Click to collapse
as you probably already realize, i have only performed flashes above using odin via ocd method and am not confident/savvy enough yet to perform what you are suggesting, but it seems to me that maybe i should flash to the uckh7 version with root though to have ability to do what you suggest i try and then search for that kernel and search for procedures to compare results. since i'm not sure how to do what you are suggesting and only partly comprehend what you think i should try, any additional details how to go about this would be appreciated.
Hello people,
For the past few months I'm having this issue which I find extremely [email protected]!!
Every few minutes, my phones just loses internet connectivity - the 3g signal appears to be normal during all the time, thing is, whenever I try to use any internet application - it just hangs. and then, after a minute or so, connectivity is back(again, for a few minutes).
I have tried flashing so many versions of modems - some improved it a little but most of them didn't help at all, or even made it worse.
Hopefully someone could help me with that as I'm that close to give up on this and buy a new phone.
Thanks in advanced.
Nir.
Which firmware are you running on your phone? What modem do you have right now and where do you live? Do you have problems with all apps that use internet-connection? Do the problems dissapear when you use wifi?
Just some information would be usefull
Donnie Sins said:
Which firmware are you running on your phone? What modem do you have right now and where do you live? Do you have problems with all apps that use internet-connection? Do the problems dissapear when you use wifi?
Just some information would be usefull
Click to expand...
Click to collapse
Yop.. forgot to mention a 'few' things...
Model: GT-I9100
Rom: RootBox V3.8
Kernel: 3.0.31-CM-g7ce58e6
Baseband: I9100DXLPB
Android version: 4.2.2
I live in Israel, bought the phone in Thailand.
I tried flashing all available Israeli modems(from various cell phone providers) - none helped.
Problem disappear when I move to WiFi - as 3g connectivity moves to background...
Thanks.
I assume you've read the Rootbox threads to see if other people experience signalproblems?
Did you compare the connectivity with other roms? Stock-based roms for example...
Donnie Sins said:
I assume you've read the Rootbox threads to see if other people experience signalproblems?
Did you compare the connectivity with other roms? Stock-based roms for example...
Click to expand...
Click to collapse
I've been hovering the internet for weeks in search for a solution..
That's not a RootBox issue in particular as I tried using various roms...
niiiro said:
I've been hovering the internet for weeks in search for a solution..
That's not a RootBox issue in particular as I tried using various roms...
Click to expand...
Click to collapse
That seems quite weird.. The only thing I can come up with is 1) a hardware problem, or 2) you live in an area where the signal is crap
Hopefully someone else knows anything.. Good luck.
Donnie Sins said:
That seems quite weird.. The only thing I can come up with is 1) a hardware problem, or 2) you live in an area where the signal is crap
Hopefully someone else knows anything.. Good luck.
Click to expand...
Click to collapse
Neither of them thanks anyways.
Anyone else...?
If you've only tried flashing the modems bundled with stock roms from Israeli carriers, you haven't done nearly enough. There are literally dozens of modems available, you need to start flashing as many as you need to. This isn't going to fix itself magically.
MistahBungle said:
If you've only tried flashing the modems bundled with stock roms from Israeli carriers, you haven't done nearly enough. There are literally dozens of modems available, you need to start flashing as many as you need to. This isn't going to fix itself magically.
Click to expand...
Click to collapse
I haven't flashed only Israeli modems but others as well. I've tried around 20 so far...
Question is, which direction should I choose? should I look for Thai modems or IL?
That depends. I know Israeli carriers sold (still sell ?) the I9100T, are you sure you don't have one of these ? If that's the case, I'd be trying modems bundled with roms released by the Australian & NZ carriers which sold the I9100T (I have one), and yes, the Thai ones as well.
If you do have an I9100, then keep trying any/every modem you can get your hands on. If it's not a carrier-side issue, this is really all you can try, unless you want to start messing around with RIL's as well. I've not found any difference in connectivity doing this personally (tho many people have) but if you get to the point of trying every single modem & you're sure it isn't a carrier issue, you might as well try. But I would leave this till last given many people find their connectivity messed up even worse by flashing an incompatible RIL.
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...
There seems to have been no resolution to this problem. I have the Galaxy SIII with no sound when I make a call and no one can hear me when I call. I can't hear on speaker phone or earphones but when I use the apps Skype or Vonage to make calls I hear fine.
Android ver= 4.1.2
Baseband ver= XXEMB6
Build no.=JZO54K.IXXEMC3
I have tried the Megawipe successfully many times and flashed 4-5 different Stock roms from sources in this forum and the problem is still there.
Is there an possible answer to this problem. I know others have this problem but I have not found any resolution to this strange problem.
Please can any one help here. It will be much appreciated.
If you've mega wiped and flashed a full stock rom using odin on your pc then it sounds like a hardware fault. Weird if speaker & microphone work in apps but not during calls.
Could be network / sim related. Worth swapping to make sure
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Could be network / sim related. Worth swapping to make sure
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for your reply. Yes I have swapped sim cards to no avail. Is is possible to flash the phone using adb for example how can I flash the modem or even the rom. Yes I know I can flash the rom or modem using odin. I have done that to no avail, but will I would like to flash using adb or Heimdall because if I use vonage or skype the speaker earphones work just fine. I am just experimenting to find a fix that is what guide can I follow to flash the modem or even the rom itself. I want to try to exhaust my possibilities if possible. It doesn't seem to be a hardware problem if it works on skype and vonage to make calls.
Thanks again for your help and others on this forum
i have the same problem i posted here but till now no one answering me >>>>:crying:
see my post http://forum.xda-developers.com/showthread.php?p=44529739#post44529739
mohamedkenzo said:
i have the same problem i posted here but till now no one answering me >>>>:crying:
see my post http://forum.xda-developers.com/showthread.php?p=44529739#post44529739
Click to expand...
Click to collapse
You have been answered like i said stupid thread title nobody bothers with you .
Read this thread and try its posted fixes .
jje
have you solved this issue?
I am having the same problem...
I thought it was my rom problem, but after I have flashed a variety of roms (cm 10.2, pa 3.97, cm10.1, cm9) and modems
and now running on stock rom im still having this problem...what confuses me is that applications like skype , hangout & viber
works fine but if i call or received a call, i cannot hear the other party. I have searched on the forums for a few days now but mostly points
to bugs on roms. but since i am now running stock, should i say it's already a hardware problem?