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...
Related
The dreaded face unlock bug. I have been experiencing this for several days now, on and off with no particular rhyme or reason. I'll explain the bug. I press the power key to enable the phone, after 2 or 3 seconds the camera comes on, this is where is gets sticky. Sometimes it does not recognize me (like if I have my glasses on, or a hat) and gives me the keyboard to enter the pin. Other times it just dies, picture still on the screen, no combination of buttons unfreezes the phone, I have to yank the battery and start all over again.
I am rooted running Phone Bricker 2.1, stock kernel, and everything else, although I was going to try a different modem, apparently in my area a different modem works better.
I've seen numerous posts on the international version of our phone but nothing for the I-777, do I have a phone problem, or is this just an expected errata from running 'leaked' software?
Also are there any fixes anyone is aware of? I love the face unlock feature and I guess I could disable it.
One clue that might shed some light on the subject, as soon as I unlock my phone, if I use the pull down menu and mess with Wifi at all, the phone all but dies. It does recover but it takes awhile.
Thanks for any insight or a link I missed.
And happy Easter!
Wink
Phone-Bricker is not based on the leak, its from i9100 LP3 (o2 carrier) base.
Not sure what the face unlock bug is but I tried it before without any problems.
Try using Entropy's latest kernel named Zombie Ass!
I am running Phone Bricker and also use the Face Unlock feature, with no problems whatsoever. But then, I've only had my phone since Friday.
Sent from my SGH-I777 using xda premium
LiLChris06 said:
Phone-Bricker is not based on the leak, its from i9100 LP3 (o2 carrier) base.
Not sure what the face unlock bug is but I tried it before without any problems.
Try using Entropy's latest kernel named Zombie Ass!
Click to expand...
Click to collapse
I was able to find the Kernel, thanks again.
Thank you my friend.
Wink
Were you over/under clocking?
I don't think the ICS kernels support that. I would get the same problem with the slide unlock screen, and all I did was change the governor, using the stock frequencies.
Sent from my Galaxy S II (i777)
Well I had SetCPU installled, but the Kernel does not support overclocking so I saw no need for the application and removed it.
I started from scratch, I did a factory wipe/ cleared Dalvik cache and reinstalled the ROM, both versions 2.0.1 and 2.1, also the mail fix. I installed the modem that shows the best performance where I live now, and also installed Entropy's new Kernel (again at least from a cursory look it maxxes out at 1.2 GHz)
I'll know more after today, I'll post here tonight after work and we'll see how things are going now.
Wink
Well face unlock seemed to work perfectly, i'll chock it up to some strange code bug.
Odd thing my mic out would not work all day, however connected to headphones here at home it's working fine. I guess it could be the radio at work or a co-worker who is sick of my music who borked it so I can't use my phone as an MP3 player.
Overall I gotta say I am extremely happy.
Thanks all for your help!
Wink
Great thread title.
Thread title added.
I noticed I omitted it and tried to add it after the fact....
No such luck, sorry.
Hi LiLChris06 - Is the face unlock an app? If so do you think it would work on your gingerbread 2.3.6 rom?
Thanks
superdog404
superdog404 said:
Hi LiLChris06 - Is the face unlock an app? If so do you think it would work on your gingerbread 2.3.6 rom?
Thanks
superdog404
Click to expand...
Click to collapse
Doubt it would work, its meant for ICS.
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 :\
I have recently updated to JB 4.1.2 LS8. All working well generally.
I have found that the bluetooth connection stutters badly when connected to my docking station and it is impossible to listen to music.
When my S2 was running 4.0.4 it worked perfectly without stutters. My iPod touch still works perfectly with the docking station so there is nothing wrong with that.
My question is, could I flash back just the modem from my previous XEU 4.0.4 to see if the problem is resolved (via Mobile Odin PRO)? Or could this cause other complications?
Yes.
TheATHEiST said:
Yes.
Click to expand...
Click to collapse
I realise that I didn't ask my question very well now...
Do you mean yes I can flash the old modem - or yes, flashing it will cause problems?
dimbo33 said:
I realise that I didn't ask my question very well now...
Do you mean yes I can flash the old modem - or yes, flashing it will cause problems?
Click to expand...
Click to collapse
Yes you can flash other modems. You could have answered this easily yourself by reading the topics that discuss modems.
Indeed. I have read your posts ATHEist and was expecting an answer like this, but at the same time it's clear that you know what you're talking about.
So thank you.
The searches I was able to make related to other hand sets and when I attempted to search the S2 forum I got a message from the xda site that the search function was temporarily unavailable. Believe it or not, not all less experienced users are either lazy or unprepared to spend time reading around.
As it happens, it turns out that my S2 doesn't like the specific bluetooth device for some reason as tests with another 2 bluetooth receivers have shown the S2 running stock LS8 to be working just fine. Very odd.
So as it stands I see no reason to go down the route of flashing the old modem - I see little point in flashing stuff without a clear reason.
Update: I flashed just the modem XXLQ6 from 4.04 - it doesn't make any difference to the BT problem with the BT receiver.
Just got the new OTA, but still no Jelly Bean. I777UCLL6
IMEISV is now at version 7. No other changes I can see.
ou812bkewl said:
Just got there new OTA, but still no Jelly Bean. I777UCLL6
IMEISV is now at version 7. No other changes I can see.
Click to expand...
Click to collapse
Maybe it fixed the sod problem, one can only hope.
Sent from my Zanpakuto using Getsuga Tensho!
It looks like it updated Kies Air, and now the Facebook app won't open. I haven't noticed any other changes yet.
Hey all,
As some of you have already noted, an update is available for the Samsung Galaxy SII.
The update includes fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions. It also enhances security to protect against malware vulnerability. You will receive a notification on your phone to update.
NOTE - You must have updated to Android version 4.0 to receive notification of the new software update
From community manager on ATT forums:
http://forums.att.com/t5/Android-Di...hutting-off-in-idle-mode/td-p/3247765/page/18
What a complete waste. Sprint just pushed 4.1.2 to their gs2.
cfili said:
fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions
Click to expand...
Click to collapse
By rare, they must mean multiple times a day... hope that finally fixes the problem...
Had my hopes up for JB even though I know the phone will not get it from AT&T.
I guess it is good that they are still trying to improve the phone.
scottwood2 said:
I guess it is good that they are still tring to improve the phone.
Click to expand...
Click to collapse
There's at least as much cya and marketing motivation involved as anything else.
I previously rooted and flashed Siyah 4.3.3 which resolved my issue with the sleep of death. This seems to prevent this new update from installing as when the phone reboots it shows the Siyah boot image and then boots back into the OS, when I unlock the phone it tells me that the update failed to install. I'm not in a hurry to install an update that resolves something I've fixed through other means, but I thought I'd share for those interested.
Notmare said:
I previously rooted and flashed Siyah 4.3.3 which resolved my issue with the sleep of death. This seems to prevent this new update from installing as when the phone reboots it shows the Siyah boot image and then boots back into the OS, when I unlock the phone it tells me that the update failed to install. I'm not in a hurry to install an update that resolves something I've fixed through other means, but I thought I'd share for those interested.
Click to expand...
Click to collapse
You really shouldn't accept OTA updates unless you are 100% stock.
nimper said:
You really shouldn't accept OTA updates unless you are 100% stock.
Click to expand...
Click to collapse
You really CAN'T accept them if you remove system bloat ware or change kernels far as I know.
Hopefully it fixes the SOD problem. I was getting ready to call or go to AT&T and demand I be let out of my contract.
NBA Brawler said:
Hopefully it fixes the SOD problem. I was getting ready to call or go to AT&T and demand I be let out of my contract.
Click to expand...
Click to collapse
That's the best joke I've heard today.
cfili said:
Hey all,
As some of you have already noted, an update is available for the Samsung Galaxy SII.
The update includes fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions. It also enhances security to protect against malware vulnerability. You will receive a notification on your phone to update.
NOTE - You must have updated to Android version 4.0 to receive notification of the new software update
From community manager on ATT forums:
Link Omitted
Click to expand...
Click to collapse
This has been happening to me for the past few months, on more than "rare occassions" though. I never knew what to call it until I saw people on here refer to it as Sleep of Death. Yep, sounds about right. And it would rapidly drain my battery when it happened.
I've successfully updated, so hopefully this will take care of it. It gets VERY annoying! And all the much worse since I use my phone for my alarm, haha. I have my wife's as a backup though.
Anyone pull the modem yet?
Sent from my SGH-I777 using Tapatalk 2
I'm only a curious now, about whether this fixes the SOD. After hours on the phone with ATT and Samsung, and a few factory resets and a new phone, it was still doing it. And each time I called them about it, they'd say they were not aware of such a problem. Anyway, not an issue anymore for me, since going to Task's AOKP ROM, which got me so many better features than an ATT update ever would have - warranty or no.
The only reason why this OTA was pushed was because a ton of users were posting this issue on the ATT forums for 4 months straight. Even then ATT pushes an OTA for 4.0.4 instead of using one of the many 4.1.2 firmwares from Samsung.
c0ldburn3r said:
The only reason why this OTA was pushed was because a ton of users were posting this issue on the ATT forums for 4 months straight. Even then ATT pushes an OTA for 4.0.4 instead of using one of the many 4.1.2 firmwares from Samsung.
Click to expand...
Click to collapse
My understanding is that it is up to Samsung to produce the firmware, and because it's a carrier-branded device, I have a hard time believing that they'd do that unless instructed to.
Really? You think Samsung is the one making the decision? Its really the carrier.
Can someone pull the modem from this update? Pm or post a download link once extracted please.
Sent from my Transformer Prime TF201 using Tapatalk 2
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.