Related
I was using the Synergy RLS1 rom for a quite a while and was very happy with it until recently I started having intermittent trouble receiving texts. I wasn't thinking it had anything to do with the rom itself until I read about others having trouble with newer sense roms. I have read a couple of developers state in various threads that it is a known/common problem with the newer sense roms to have this happen every once in a while. This was a few months ago and I am curious if this problem is still present? I really like some of the newer versions of sense that have the lock ring and the ability to set different notification tones for email and texts.
What sort of problems exactly?
chocolate8175 said:
What sort of problems exactly?
Click to expand...
Click to collapse
Not receiving texts, just as stated.
I know that at one point Synergy did have this issue, so I've not had any issues with any of the newer ROMs. Just try running a different one, and see what happens. I haven't heard of any text issues for months now.
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
Hell everyone,
I recently rooted my phone and installed LiquidSmooth on my AT&T Samsung S3. About three days into using the ROM, I notice some connection problem between my phone and AT&T's network. The problem I experienced was I wouldn't receive texts or calls from other people even though the phone is connected to the network. When I do receive the texts, they come all at once at the same exact moment. Which means my notification ringtone going off like crazy.
This problem usually occurs at night around 9-12PM. I also experienced the same exact problem when I first started using CM10, the stable build. The one thing I also noticed after installing both ROM's is there's no voicemail number. I had to manually add a voicemail number, which is my own number, right?
I decided to unroot my phone and run Samsung's newly released JB update, which totally blows besides the battery life. As of right now with the unrooted phone and Sammy's updates, everything is running fine.
Thanks very much, I appreciate any help I get from you guys. And, I do want to apologize in advance if this question had already been asked. I tried searching, but couldn't find anything on the subject. If you guys need anymore details, please do not hesitate to ask. I will try my best to provide as much detail as possible. Thanks once again.
I'm just trying to keep these straight, since I've seen bits and pieces of various problems on the various dev threads. Would someone be so kind as to check my logic here? Thanks in advance!
Problem: Can't get a GPS lock after flashing any AOSP-based 4.3 rom
Solution: Flash back to stock (RUU?), open up Maps or otherwise get a good GPS lock, flash back to your rom of choice
Burning Question: Why does this happen and why does stock flashing work?
(Idiot Newbie Question: RUU is basically a stock image? I need an encrypted version? Do I need to worry about breaking my rumrunner s-off/root?)
Problem: When on a phone call, and the other party hangs up, you get "call lost" instead of the standard graceful disconnect.
Solution: Isn't one yet. Gotta wait for a fix to be made.
Problem: Signal strength meter shows impossibly low values, despite data, voice, LTE all working as expected.
Solution: No idea. Of the 3 roms I've tried, (CM10, Liquid, Carbon), all do this. Minor problem, but anyways.
Problem: Purplish tint on the camera in dark scenes.
Solution: Phone's defective, send it in. / Or: Wait for a software patch.
Which is it?
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
adrenalinemotion said:
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
Click to expand...
Click to collapse
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Flyhalf205 said:
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Does one need to have the stock recovery to reset from Hboot?
Sent from my HTC6500LVW using Tapatalk now Free
Flyhalf205 said:
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Click to expand...
Click to collapse
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Karunamon said:
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Click to expand...
Click to collapse
check DBM isntead of looking at your bars to see if you even have an issue.
The signal issue sounds the same as AOSP on the Rezound. The signal strength would be same, but the signal icon would be different. Basically, HTC has set the icons to show more than AOSP.
I didn't factory reset after using rumrunner and the only thing I have noticed was I would not connect to 4g as much or as fast as before. It seems to be getting better though. I am running bonestock.
Sent from my phone using an app
Like it was explained to me the bars are kinda like the idiot lights on a cars dash. They really don't do much. Aosp shows your true signal and sense and so on shows a false truth just so people doesn't complain about poor signal. As long as my data works I don't care if I have zero bars.
Sent from my M7 using Tapatalk
Are there any bluetooth issue's ?
nujackk said:
Are there any bluetooth issue's ?
Click to expand...
Click to collapse
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
IR work yet?
exzacklyright said:
IR work yet?
Click to expand...
Click to collapse
IR is working on VanirAOSP.
I'm using Smart IR Remote to control my devices; great interface and works well with the majority of the stuff that I have.
Not sure what the progress is re: IR with the other AOSP ROMs.
With smart ir remote it should work on any Rom.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
The streaming is my main concern, Use is inmy truck and main reason I will try to keep my unlimited data FOREVER
adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
Did this happen using twrp or cwm? Some folks are thinking its cwm causing this.
Sent from my HTC6500LVW using Tapatalk
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Flyhalf205 said:
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Click to expand...
Click to collapse
This happened to people who hardware s-off'd and flashed the gpe rom too. Don't think it has anything to do with it.
Sent from my HTC6500LVW using Tapatalk
First off, before getting into anything, let me just say that yes, I do fully realize that I am posting this in the wrong section. The reason why I'm posting this thread here is to fully ensure that this issue gets the most attention as possible, as I've already posted for help if the Q&A section of the G2 forums and various other help threads, to no avail. This is kind of my last resort here.
Whenever I'm on an AOSP ROM, using either basebands ZV8 (From my understanding, some LS980 ROMs only work with JB/ZV8 modem) or ZVD (The modem zip is named KK_BASEBAND.zip by Cloudy, so I'm ASSUMING that's either ZVD or ZVC), data, outbound calls, texts, everything works, EXCEPT for incoming calls. Just goes straight to voicemail. And this is only with AOSP ROMs. Stock ROMs perform with no problem. I've been trying to get to the bottom of this issue, but I just can't seem to get a finger on it. So I'm currently in stock until I can get some insight on this. Has anybody had any experience with this, or know what's going on? Any and all help would be greatly appreciated. And, for what its worth, I rooted using towelroot+AutoRec.
zv8 baseband works for me on incoming calls, (texting wise i have to use a 3rd party app) *currently running cm 12 at the moment*
jcwxguy said:
zv8 baseband works for me on incoming calls, (texting wise i have to use a 3rd party app) *currently running cm 12 at the moment*
Click to expand...
Click to collapse
ZV8 works for me for a little while, too, and then it seems like a day later or so, all incoming calls go straight to voicemail. I usually call myself at least once or twice a day just to make sure everything still works, and calls get blocked sooner or later. Is there a dialer code I could use to upgrade PRL on AOSP? Going back to stock > upgrading PRL seems to do nothing, so I'm wondering if it'd be better to do it on AOSP, rather than going back to stock.
no way to update profile or prl on aosp unfortunately
iamterence said:
ZV8 works for me for a little while, too, and then it seems like a day later or so, all incoming calls go straight to voicemail. I usually call myself at least once or twice a day just to make sure everything still works, and calls get blocked sooner or later. Is there a dialer code I could use to upgrade PRL on AOSP? Going back to stock > upgrading PRL seems to do nothing, so I'm wondering if it'd be better to do it on AOSP, rather than going back to stock.
Click to expand...
Click to collapse
I was having this issue on stock and aosp turns out sprint was working on towers here upgrading them... And it only affected incoming calls... Might want to call sprint and see...had something to do with spark bands in our phone...next time you try aosp put it on CDMA and see what happens... That was my experience
goast said:
I was having this issue on stock and aosp turns out sprint was working on towers here upgrading them... And it only affected incoming calls... Might want to call sprint and see...had something to do with spark bands in our phone...next time you try aosp put it on CDMA and see what happens... That was my experience
Click to expand...
Click to collapse
I may, or may not have finally found a solution for this. I was on Super G2 ROM with ZVC modem, PRL/Profile updated and everything, and instead of downgrading modem to flash certain AOSP ROMs, I flashed last Mahdi build (which is on KK modem) and just left the radio alone. So far, everything seems to be okay. So far. I've been getting calls and calling myself randomly from Google Dialer to make sure everything is good, and all remains well for the moment. We'll see how this turns out.
Im having this same problem, on Sprint using a G3 on AOSP rom.. its kind of annoying, especially since all my calls go straight to vmail.. is there a fix?
You can also try the ZV7 modem