Well, this is an odd issue and i'm sure many other have it because all of my friends with GS3's have this problem. I have a rogers GS3, my friend has a Telus and other videotron and multiple times a week, when we try to send a moderate or long sms (3 lines and more) the phones fails to send the message. This is very odd because i've tried everything from a factory reset, full odin wipe, different roms, and nothing works. I'm on CM10 M2 now and the problem is also there.
When i try to send a long sms, it fails, then i sent a short one right after, it works, then i copy and resetn the original one that failed and it faisl again. I pretty sure many of you have it because we have 3 different GS3 on 3 different networks and it happens to all of us
I tried looking around, i have not found much, maybe somebody has such problem and perhaps a solution?
This happened to me earlier this morning. No idea what can even cause an issue like this.
nobody??? im sure many people have this
I think this is based on all aosp roms.
I don't know if it's fact or opinion, but I always get the "sent" message after receiving the "not sent" error.
In other words, it seems like it still sends the whole text, but just throws you an error initially.
Can someone correct me if I'm wrong?
Well i can correct you wrong because i've tested it it does not sent the messages nor does it have anything to so with AOSP roms because i've used both AOPK and they both have the issue,
I send long sms no problem.. some in fact so. Long it automatically breaks them into two. What firmware are you on.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
First off this belongs in Q&A so I will move it
Second AOKP is also considered an AOSP type ROM
There should be an option in your mms app to split messages over 160 characters. Make sure it is checked.
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Friendly Neighborhood Moderator
Contact your carrier
Especially if you're having this issue on and off
Do other apps work? I use ChompSMS (fixes lots of annoying bugs in the TW SMS app) and I can send long messages fine.
kennyglass123 said:
F
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Click to expand...
Click to collapse
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
polish_pat said:
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
Click to expand...
Click to collapse
are you using a mms app other than what's provided with the rom? And are you able to send any messages at all? or does it fail to send only on long ones?
If you were on stock and still can't send any/long messages, check your apn settings and make sure it's correct for your provider, especially if you are installing roms (stock or custom) that are specifically developed for AT&T phones. From your profile I'm assuming you have a Canadian version.
Check the APN settings. If that's all correct, return the phone for a new one
all apn settings are fine and this is not an issue with the phone because like i said, it would be one hell of a coincidence if this happened to both of my friends with gs3s on different providers. Also i am using stock sms app and this only happens with moderately long sms, it doesnt always ahppen, its random
If it's intermittent, and it's not just you but also your friends, it sounds like a provider problem. From what I have been reading on different forums, it seems service in Canada has been sketchy because they're adding LTE towers everywhere.
I don't know if that's really the case, but all I can say is texting works well for me down here on the AT&T network, both on AOSP (which also includes AOKP as you were mistaken earlier) and stock-based ROMs, although I do get the error on AOSP based roms for long messages. I've asked my friends and they say they receive the whole message just fine.
Last thing I can think of is if you flashed a custom kernel and it messed with some of your drivers. I know KToons kernel has modified drivers, and you're supposed to flash the stock kernel provided in that thread if you're going back to stock. Try that and see if that fixes your problem.
yup, i've flashed ktoon kenel as i had major issues with faux kernel as per this thread: http://forum.xda-developers.com/showthread.php?t=1937476
i'll report back in a week to see if any different
thanks for you help
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844
ok, googled the past couple months with no results. searching here still no results...
my s3 seems to have sluggish wifi wherever i go, no matter what modem, no matter how many settings i changed advised by posts ive found. *#0011# turning off psm does not work. changing advanced settings will not, static ip does not, flashing roms tw or aosp only same results in all.
im beginning to think this is a hardware problem, not software. cant get a new one cause i don't find it a need for insurance cause if something breaks its cheaper to fix ordering online, plus the fun doing it yourself.
does anyone know if we ever had a flash-able zip to fix like the international version? tried and bricked of course. or any steps that i haven't posted i didn't find searching?
creep138 said:
ok, googled the past couple months with no results. searching here still no results...
my s3 seems to have sluggish wifi wherever i go, no matter what modem, no matter how many settings i changed advised by posts ive found. *#0011# turning off psm does not work. changing advanced settings will not, static ip does not, flashing roms tw or aosp only same results in all.
im beginning to think this is a hardware problem, not software. cant get a new one cause i don't find it a need for insurance cause if something breaks its cheaper to fix ordering online, plus the fun doing it yourself.
does anyone know if we ever had a flash-able zip to fix like the international version? tried and bricked of course. or any steps that i haven't posted i didn't find searching?
Click to expand...
Click to collapse
Is it a newer one or an older one? The reason I ask is because all S3s are not built the same. I've had mine since they 1st came out, and have never had 1 issue with wifi speed. I just rooted a newer Sprint 1 and a Boost 1, both of them had wifi issues even after I set a static IP for each on my network.
joeyhdownsouth said:
Is it a newer one or an older one? The reason I ask is because all S3s are not built the same. I've had mine since they 1st came out, and have never had 1 issue with wifi speed. I just rooted a newer Sprint 1 and a Boost 1, both of them had wifi issues even after I set a static IP for each on my network.
Click to expand...
Click to collapse
its the newer build. forgot to mention zeroed out some of the http settings in ##data# for the speed boost. 4g zips.
i cant even find a diagram online to find where any wifi chips are located. went as far as taking a heat gun to the board itself and applying weight to it after like the famous ps3 fat fix. yea, i went that far lol:silly:
Hello all. I'm Trying to figure out what I'm doing wrong here. I lost my IMEI and all, did the stock ROM to get it all back (which was a 4.3), rooted it and then got rid of KNOX. I have flashed to various custom ROM's since then and continue to have the same problems, which are bad GPS locks (or no GPS locks and its using cell tower and wifi for a position) and loss of mobile data (no 4G or 3G, think it happens when I'm on 3G for extended amount of time or something). I've tried AOKP, Cyanogen, and other various AOSP ROM's, different modem's, and different kernels. From what I understand you can't do PRL updates on AOSP after 4.2, and to accomplish this you have to flash back to stock, do the PRL update, then restore your previous custom ROM from a backup. Anyone have any idea where a good tutorial or where some info I could use. Also I would like to get a better understanding of some other things, like why flashing the ROM does not change the modem, kernal, prl ect. for starters (writes to certain portions of the file structure, while leaving others alone?) I need to start understanding Linux and stop trying to relate it to a Microsoft O/S. Any help would be appreciated (even a really big flow chart). Thanks.
fhaq said:
Hello all. I'm Trying to figure out what I'm doing wrong here. I lost my IMEI and all, did the stock ROM to get it all back (which was a 4.3), rooted it and then got rid of KNOX. I have flashed to various custom ROM's since then and continue to have the same problems, which are bad GPS locks (or no GPS locks and its using cell tower and wifi for a position) and loss of mobile data (no 4G or 3G, think it happens when I'm on 3G for extended amount of time or something). I've tried AOKP, Cyanogen, and other various AOSP ROM's, different modem's, and different kernels. From what I understand you can't do PRL updates on AOSP after 4.2, and to accomplish this you have to flash back to stock, do the PRL update, then restore your previous custom ROM from a backup. Anyone have any idea where a good tutorial or where some info I could use. Also I would like to get a better understanding of some other things, like why flashing the ROM does not change the modem, kernal, prl ect. for starters (writes to certain portions of the file structure, while leaving others alone?) I need to start understanding Linux and stop trying to relate it to a Microsoft O/S. Any help would be appreciated (even a really big flow chart). Thanks.
Click to expand...
Click to collapse
Personally I stopped using ASOP and AOPK roms, because you lose a lot of the key functions of what the phone was designed for mainly SPEN features... If you flash a TW rom and it has the sprint app, you can update prl and profile that way.. I personally us goodness 3.03 MC2 the last one that was made.. It comes with the prl write function, so you change your prl any time you want..
I'm starting to look into the MIUI ROM's out there. I want to keep some of the Samsung functionality (like screen mirroring), but I guess I want my cake and eat it too.
doubledragon5 said:
Personally I stopped using ASOP and AOPK roms, because you lose a lot of the key functions of what the phone was designed for mainly SPEN features... If you flash a TW rom and it has the sprint app, you can update prl and profile that way.. I personally us goodness 3.03 MC2 the last one that was made.. It comes with the prl write function, so you change your prl any time you want..
Click to expand...
Click to collapse
No you don't.
Not if you search Google for superior alternative apps for 30 seconds.
Skripka said:
No you don't.
Not if you search Google for superior alternative apps for 30 seconds.
Click to expand...
Click to collapse
First I have heard of this.. Plus many users have stated the same thing.. So what is the reason behind the lousy sound with these roms, plus the unstable connection issue.. Two more reasons why I switched back to TW..Now the roms themselves look real nice, but somethings still need to be worked out before I would even consider trying them again..
doubledragon5 said:
First I have heard of this.. Plus many users have stated the same thing.. So what is the reason behind the lousy sound with these roms, plus the unstable connection issue.. Two more reasons why I switched back to TW..Now the roms themselves look real nice, but somethings still need to be worked out before I would even consider trying them again..
Click to expand...
Click to collapse
People repeat the same wrong thing often enough, they start to believe it. About the only thing you can't do is the useless air command crap as of now.
Don't know about "unstable connection issues", just about any ROM data either works or it doesn't. Sound issues are often kernel related. Latest Plasma does wonders.
yeah, first thing i accomplished successfully tho not without a lot of wiping an rewiping and installing and reinstalling stuff, was unlocking the phone, then i put in the aio and it did it's thing on it's own and connected wonderfully. first time trying to go back to tmob, it started this misconnection issue. it's basically intermittent closer to non operational, tho i did get a random text tonight from a friend i was unable to respond to, because im like kinda connected for a sec, sometimes i'll see the opposing 4g arrows working in the notification area, but not long enough to get info set in the apn settings, you know where i'm talking about. half of those settings work only when you have a signal, for ex. i do the manual part correctly, hit the save apn button ... nothing saves, nothing happens better after that.
i bet you i need to update that radio huh? just tried to flash a newer rom and it said no because my radio was too old. i could have sworn my stock rom, which is supposed to be the latest... which maybe was old right? its in the threads here, first stock you'll find. probably that rom was cool with the uvle1... confusing stuff. okay, til someone answers otherwise i'm just gonna keep trying to update this radio. i guess it is only good now for unlocking...
okay, so i just flashed jedi mind trick which updated the radio, but the stock rom didn't. so does that mean that some roms will not touch the radio while others will? and what was wrong with the radio before? was it made to work only for the associated older versions of android?