i have found an error in the phone software for Herald/4350. I have the Norwegian version: Rom 1.8.409.1 NOR
The first day I used it i had to call my telephone bank. When you use a service like that, you enter a lot of numbers during the call. After maybe 30 or 40 digits the screen went white with an message, and I was unable to enter any more digits.
What did the message say?
Have you tried to replecate the problem?
Does it happen all the time or just every once in a while?
How did you resolve the problem of the screen being white?
Hi everyone!
Been having a problem for days with SMSs not sending or not receiving or both.
came across this fix:
Originally Posted by smacksakes
For Vodacom users in South Africa experiencing the SMS sending problem:
Your current PDU number is 059128721992 but that is too short. The actual full number is 0591287219921100 but it doesn't get recognised so the fix is to change the '05' to '07' and add the 1100 to the end so your new SMSC number is 0791287219921100
Steps:
1) Dial *#*#4636#*#*
2) Select Phone Information
3) Set SMSC number to 0791287219921100 and hit Update
4) Turn radio off and back on
5) enjoy sending an sms
BUT, this fix didn't work for me, so I played around a little and found a number that worked for me. I can confirm I sent an SMS and recieved one, rebooted the phone and repeated and all was successful! Yay!
So here is the SMSC number I used:
0791722819911100
Repeat smacksakes steps but use the above number instead. (You may need to restart phone to power cycle the radio properly)
I hope this works for you! Im over the moon I can stick with CM9 and/or AOKP now
And credit to where it is due to OP!
Thanks for the PM pointing me to this post.
I can confirm that this number IS indeed working for me on Vodacom.
The funny thing is, it SHOULDN'T
I am not sure where smacksakes got the number "0791287219921100" from, because that decodes to an SMSC # of +822791291100, which is incorrect.
Vodacom's primary SMSC # is +27829119 - which encodes to a PDU # 0591722819911100.
The only difference between the above number (which SHOULD work, but doesn't), and your number, is you changed the second hexadecimal number form 5 to 7.
What you effectively did was change the LENGTH of the PDU number, which is controlled by the first two digits. Your working PDU decodes to a SMSC number of +278291191100, which is correct, except for the extra 4 digits (1100) which got added to the end because you changed the length of the number when you changed the 5 to 7.
Well done for fixing this, what made you think of changing the 5 to a 7?
Heya, thanks for the reply!
To be honest, I cant remember what made me change that. I guess I was desperate to get this working and stayed up for a few nights researching and reading up on it.
I also found the +72821991 number and converted it, then tried the "5" to "7" "trick" and it worked. I was in awe but hey, not complaining!
Edit: yea, I think I remember now, you pretty much summed it up: "What you effectively did was change the LENGTH of the PDU number, which is controlled by the first two digits. Your working PDU decodes to a SMSC number of +278291191100, which is correct, except for the extra 4 digits (1100) which got added to the end because you changed the length of the number when you changed the 5 to 7."
I kinda worked backwards in a way and played around until I got the correct length, which must be 16, kinda like having the bits to the answer and fining combinations that work
And for any other lazy b******s like myself out there, pasting it isn't gonna work, at lease not on the latest cm9 nightly... You're gonna have to type it. The horror!
Confirmation
Hi all,
I was having an issue with CM9 nightly 04/21 on sgs2 where sending sms killed the GSM connection.
After following instructions on CM Wiki for SMSC updates still couldn't fix it.
Your advice fixed it!
Thanks alot! That fixes the SMS RIL-crash bug for T-Mobile Austria Users too. I just had to replace my smsc with: 0791347606121100 and now sending sms works just fine.
Confirmed working on Hydrog3n-ICS as well. Nice job guys - I was waiting for a fix for a long time now.
Strangely enough, sometimes my SMS's just refused to send, other times it was just crashing RIL - had to delete the SMS to get RIL stable again. All working great now though.
Very happy it could help out you guys!
Thanks, but
I followed your advice step for step, as well as smacksake's advice, but my sms'ing still doesn't work. Although it did change one thing: previously it would kill the signal connection until I delete the sms. Now it doesn't, but I get an error notification (in notification bar) which says" Message not sent - touch to reviewthe message and try again". My APN is the default "Vodacom ZA - Internet" APN.
Any help would be so much appreciated!
I think I might do a reflash of Resurrection Remix AOKP 1.7 after doing all the wipes, and then follow this step as well.
EDIT:
Don't worry it worked! LOL. Had to reboot more than twice (by switching off and on)
Don't know how the OP got that number. I use twit88.com and I got this number that works well for me:
059172281992
I'm on MIUI.
I have a problem with SMSC as well. Whenever I want to send a message, I lose my network.
My network SMSC is: +38592092
Converted to PDU format (first 16 digits): 0591839502291100
When I enter "Testing menu" and press Refresh on SMSC, it's written without last 4 digits (059183950229, without 1100). When I enter these 4 numbers and press Update, SMS works. After first phone restart, it's dead again.
Interestingly, if I press Refresh immediately after I press Update, last 4 digits are still missing. But SMS works.
Any ideas?
Thanks OP - I had tried GO SMS Pro but that just sucked so badly! Now I can keep my Resurrection Rom after all
Thanks! You're a lifesaver!!!
The problem is back...
I had sorted this out before using the long PDU number, but this morning I tried to send an SMS and it kept failing. Then I got an SMS from Vodacom saying:
Vodacom has upgraded the quality of your SMS service. Please switch your phone off and on again for this to take effect.
Click to expand...
Click to collapse
Now I'm back to where I was before where the phone radio cycles off whenever I try to send an SMS, and the PDU number doesn't seem to work any more.
Is anyone else experiencing this? Or better yet, anyone else got a fix?
EDIT: Just to give more information, I'm having better luck with +27829129 and none at all with +27829119. Of course when I use 0591722819921100 it shortens it to 059172281992 and doesn't hold it after a reboot.
OMW, thank you so much, this thread is PERFECT!!! You guys ROCK!! Thanks OP haha
Resurrection Remix is now PERFECT on my phone, this was the only issue.
Thanks again
Problems Smsing
Good Day Guys!
I am loving RR, but I have tried as much as possible to do the *#*#4636#*#* trick but to no avail. Irrelevant of what number I put in it won't work. I am not 100% sure as to what you mean by hexadecimal conversion, but I have tried all the numbers posted in the previous messages and none work. Am I making a n00b error somewhere, or is this a legitimate problem?
SAGalaxyGuy
x0lani said:
I had sorted this out before using the long PDU number, but this morning I tried to send an SMS and it kept failing. Then I got an SMS from Vodacom saying:
Now I'm back to where I was before where the phone radio cycles off whenever I try to send an SMS, and the PDU number doesn't seem to work any more.
Is anyone else experiencing this? Or better yet, anyone else got a fix?
EDIT: Just to give more information, I'm having better luck with +27829129 and none at all with +27829119. Of course when I use 0591722819921100 it shortens it to 059172281992 and doesn't hold it after a reboot.
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ok, I had similar issues and struggled to make sense of the whole SMSC / PDU story. The issue with this is that the leading "05" apparently dictates the length of the number that your phone would save... so I tried playing around a bit and ended up changing the 5 to a 7... and now SMS seems to work. The numbers I came out to were as follows:
0791722819921100
or
0791722819911100
SMSC number sourced from:
https://help.vodacom.co.za/portal/e...source_id=14&search_keyword=&source_id=topics
converted using:
http://www.smartposition.nl/resources/sms_pdu.html
5-7 idea from:
http://forum.xda-developers.com/showthread.php?t=1607422
I hope this helps someone out there, since I was ready to tear my hair out
I love you man - I had this issue for almost half a year already and thought i won't ever fix it, but this is just great - thx a lot
grJoe said:
I love you man - I had this issue for almost half a year already and thought i won't ever fix it, but this is just great - thx a lot
Click to expand...
Click to collapse
you are very welcome Thought the same way!
- Also, this fix is permanent, having flashed many many many ROMs the PDU number stays put
(Stock 8.0) I noticed that some calls which are say more than few minutes end of showing the wrong call duration, like yesterday i had a call for about 10 minutes and it showed it as 47 mins. Anyone noticed it ? if not then try it and let me know
Calls which are say under 2 minutes show correctly like i had a call for say 20 seconds and it showed correctly !
anyone ?
I noticed the same problem
rrohanjs said:
(Stock 8.0) I noticed that some calls which are say more than few minutes end of showing the wrong call duration, like yesterday i had a call for about 10 minutes and it showed it as 47 mins. Anyone noticed it ? if not then try it and let me know
Calls which are say under 2 minutes show correctly like i had a call for say 20 seconds and it showed correctly !
Click to expand...
Click to collapse
I am using latest version of Google Contacts and Dialer on Lineage OS 14.1 on my LeEco Le 2 Device.
I noticed the same issue regarding the time duration and in my case its showing 40min or 30 min for few minutes of calls.
I was wondering if only I have the problem and after googling found this thread.
If Anyone has solution or already reported the bug plz post here about any update
Thanks :good: