I've faced a problem recently when I flashed new ROM, eg. SlimBean, c-rom bean, remics-jb, ICS333 2.0.1and some more. Why I flashed so many roms in a week, because at first I found that I can call and answer phone and receive sms. But I can't send sms. Only GB rom can send sms, all the ICS and JB now can't. I've tried different modem like JVU, JVT but no help. Last I found that, in ICS and JB, I've lost my IMEI. So I recover back the IMEI. But still, SMS can't send. So, I guess this maybe a latest ICS or JB problems. Bacause I've used Dark Night 5.5 and tiramisu with no problem at all. Looking for solution. Thanks.
Please refer to Cyanogenmod SMSC Update
shiyingwong said:
I've faced a problem recently when I flashed new ROM, eg. SlimBean, c-rom bean, remics-jb, ICS333 2.0.1and some more. Why I flashed so many roms in a week, because at first I found that I can call and answer phone and receive sms. But I can't send sms. Only GB rom can send sms, all the ICS and JB now can't. I've tried different modem like JVU, JVT but no help. Last I found that, in ICS and JB, I've lost my IMEI. So I recover back the IMEI. But still, SMS can't send. So, I guess this maybe a latest ICS or JB problems. Bacause I've used Dark Night 5.5 and tiramisu with no problem at all. Looking for solution. Thanks.
]
Click to expand...
Click to collapse
Hi! i had the same problem myself after i flashed Slim ICS on my phone, the solution was the wrong SMSC number. Cant help you with stock messenger app, but if you download GoSms , open it then go to Settings-> Send settings -> then scroll to the bottom and you will see an option: Enable customized SMSC, Enable it by ticking it.
Under this is your actual SMSC number, check that the number is the same as your providers SMSC number, if not hen change it to the correct one.
Heres a list of SMSC numbers worldwide: "smsclist dot com/downloads/default.txt" , hope u find it (couldnt post the actual link cause im under 10 posts still -.-)
##EDIT##Ok got over 10 posts
LINK: http://smsclist.com/downloads/default.txt
Related
Hey everyone!
Since the new viber has been release it isn't working for me
I can see contants can send messages to them
but they cant hear me if we made a voice call!!
i tried stock jvt stock kernel cyanogen stock kernel insanity stock kernel insanity platypus kernel
and its not working
if its working for you all dear galaxy s users please tell me your configs cause i miss it iv benn using it for 4 months on iphone and 1 with galaxy s
thank you in advance!
Bump! Please help me or tell me your experience with.viber!
Bump please somebody give.me an advice where is viber tech support?
Hi,
Here we are.
Does it happen on both 3G and WiFi?
Does it happen with everyone or just a specific contact?
Thanks,
Viber Team
IT happens with both wifi and 3g
and none of my viber contacts can hear me
fulii said:
IT happens with both wifi and 3g
and none of my viber contacts can hear me
Click to expand...
Click to collapse
Have you tried clearing data on the application?
What ROM are you on?
Herman76 said:
Have you tried clearing data on the application?
What ROM are you on?
Click to expand...
Click to collapse
At the moment im on insanity cm 56 i.reinstalled it.multiple times i tried.it with stockjvt ,stock cyanogen , stock insanity , insanity with platypus
Evry time i install i get the.same activation code is that normal? I also activated it on my old iphone 3gs i got different activation code and it worked well .
I really dont understand why.it isnt workin
When i.switched to.the galaxy.s.it worked well
Sorry for the lot of dots
Bump!! i gave all the details i will be more calm if someone just says
"it isnt workin for me neither waiting for the next update or something"
At this stage, we don't support custom ROMs with Viber (except basic ones, like CM7 and MIUI). Running Viber on a customized ROM results in various side effects, some of which are severe, but unfortunately we can't afford to support ALL those ROMs at this stage. You might want to contact the ROM developers and ask if any adaptations could be made there in order to support Viber.
FYI - many times microphone problems (like the one you're experiencing) are caused by the fact that the ROM causes the phone to "think" that it's actually a different phone, resulting in a different usage of the phone's microphone by Viber. "Model Number" in "About" page sometimes reflects this issue - so please let me know what phone you're using, which Android version, and what's written under "Model Number" in your "About" page.
To all,
We (Viber) are about to release multilangual support for Viber at last!
Since we know that XDA's great advantage is having so many members from different places in the world, we would appreciate your help with translation to your personal language. This means adding missing translated lines, and confirming the existing translations previously added by users: http://translate.viber.com
Remember - we let the community of our users shape Viber and device what it looks like
If you have any questions please let me know. We thank you in advance,
the Viber Team.
So i will sat it again as i said it in the OP!
At the moment I'm using MIUI mintberry, BUT i tried viber an multiple roms like:
-stock jvt (flashed via odin)
-stock cyanogen
-stock MIUI
-cyanogen with platypus
-stock instanity CM
-insanity with platypus
-miui mintberry with platypus
theese with xxjvk zsjpg and bvjjpg modems
at the general section it says GT-I9000
IMEI is correct its the same as the one behind the battery
so i really dont understand whats the problem
i figured out i can activate with two activation code 4758 and 4759
please help!
When you say "stock MIUI and "stock instanity CM" you're basically saying that your Android is NOT stock. The definition of Custom ROM is installing any ROM that's not the original one you got from your cellular provider.
You can try and contact our support team at http://support.viber.com - they might be able to assist you further.
I said i tried it with stock JVT thats the original stock rom from samsung with stock kernel!
We are going to do our best with investigating this issue, but it is almost impossible for us to pinpoint the source of the problem if ALL of your phone's settings were stock.
All I can offer to you is to wait for our upcoming Viber 2.1.3 and see if the problem is resolved there.
so you re saying viber 2.1.2 is supposed to be working with the GT-I9000 and something s wrong with my device so ill kepp trying you not getting any wrong experience feedback from other i9000 users
On the contrary - Viber fully supports GT-I900, as written in our official website: http://helpme.viber.com/index.php?/.../View/100/0/cant-download-from-android-market
same problem as the OP here... any news about it?
I'm on Teamhacksung's ICS alpha 17 with semaphore kernel.
Hi,
If I understand correctly, you are using Galaxy S i9000 with a CM9 Custom ROM. Is that correct?
Viber Team said:
Hi,
If I understand correctly, you are using Galaxy S i9000 with a CM9 Custom ROM. Is that correct?
Click to expand...
Click to collapse
Correct.
If as "custom" you mean anything other than stock.
Have you tested Viber on Stock ROM on your phone? Does the problem persist even then?
Hi there!
I have tried a bunch of ICS Roms, and I have the same problem with all, namely when I get a call that is in my phonebook, the phone doesn't show a name, it just shows the number!
Anyone ran into this before?
Thanks,
Andreo
I don't have it in ICS Stunner 5.0 or any other ICS roms i have tried. Pulls up all perfect. And trust me i have tried all ICS roms apart from CM9 one.
BOOMED from my BOMBASTIC NOTE
I am actually struggling with this problem. I it is present in all the ics leaks and apparently it doesn't affect eveyone. It's country and/or carrier related.
Some users installed number fixer from the market to fix it, but in my case I can't do it!! cos my contacts numbers r quite complex and different and this app will only make a mess of my contacts ...
Hopefully we will have a leak with this issue fixed,....
Sent from my GT-N7000 using xda premium
Hi Goodm7sn,
I gather that you are from Switzerland, so am I . . . I'm on Sunrise, you must be right about this country/carrier specific note.
Hope we get it solved, as I am not going back to Gingerbread . . . . !
Cheers,
A
Found this rom solves the problem:
[ROM][ICS][04/19][PRE.AOKP.B33] ICS StuNNeR - 1.4.19 [REVAMPED & RELOADED]
http://forum.xda-developers.com/showthread.php?t=1552554
I flashed Elite's GNexus Jelly Bean Port JRO03H 4.1.1 BETA 7a a few days ago and all seamed to work fine, exept: when booting up my phone and making a call (incoming or outgoing did not matter) all was working excellent. But from the second call on I did not hear the caller nor did he hear me. Today I flashed 7b, same problem with either Semaphore & Devil Kernel. I then flashed the older JVU modem driver and at first there was no internet connection. Toggling Flightmode on and off solved the problem - now everything seams to work fine.
Many thanks to all of you hard working developers getting me a Jelly Bean on my SGS. You are the best!
To an Administrator:
Please move this post to, cause i think this is the correct spot: http://forum.xda-developers.com/showthread.php?t=1776738
I obviously cannot post there because I'm new here.
If someone of the developers likes more information to this particular problem, please contact me, I am a Software Developer myself, so maybe I can assist in finding a solution to this KF1 related problem.
Many thanks again on all your hard work!
Elitemovil B7b No MMS Icon
Since nobody seams to read my Thread and I am still not able to post to the correct thread there is no other option than to report my bugs here...
I noticed that when I get MMS there is no notification. Hopefully sombody else noticed that ...
Elitemovil B8 out
flashing now ...
Elitemovil B8 NoWIPE Android Keyboard closes permanently
After flashing the nowipe version of both versions (datadata & nodatadata) I had the problem that the keyboard did not work correctly. (Keyboard closed unexpextedly). I searched in the original forum, but other than do the 3 wipes and reinstall fresh from JVU there seamed to be no solution.
But there is one: delete the data of the keyboard (you will loose all settings for the keyboard) but then it works.
Many thanks to all hardworking developers for bringing me Jelly Bean on my SGS
Still mo woking MMS Notification
Trying next rom
I'm having some troubles with signal reception on my jb. I'm running Liquid JB 2.0-RC1 with asylum beastmode kernel and xxlb2 radio. Every time I receive or send text message I'm loosing reception. Reboot doesn't help and usually I have to wipe everything and flash it again. Everything seems to be working fine I can make and receive calls, browse internet but no messages... can someone help me please? I'm really tired of constant reflashing. I already tried around 6 radios. I'm on Austria T-Mobile.
Anyone please?
try logcat, you may have found a bug maybe someone can analyze it for you
Sent from my GT-N7000 using Tapatalk 2
Well this seems to be a little bit too complicated... Not sure how to use it.
Well, no need for Logcat.. go back to downgrade GB and check back your signal when sending SMS.. if everything's fine.. then flash back that custom ROM again.. if your still getting that issue.. then it's a ROM related thing..
nothing is too complicated on that... right?
I did that already. I have installed CleaNote 6 (Its Ics) and every thing works fine. Nigthly, Asylum, LiquidSmooth, CM10 It happens on all JB roms. GB and ICS wprks fine.
cooba89 said:
I did that already. I have installed CleaNote 6 (Its Ics) and every thing works fine. Nigthly, Asylum, LiquidSmooth, CM10 It happens on all JB roms. GB and ICS wprks fine.
Click to expand...
Click to collapse
perhaps its something to do with AOKP nightlies that causing this issue.. you can raise also your concern to each respective JB nightlies on this forum, I'm sure someone has some answers on your issue . (Since this just happens when your on an JB and not on any ICS or GB Roms)
yeah best to check up on jb thread. See if someone hasbposted before. If not, use something like elixer2 to grab logcat and post it here. Use something like pastebin hosting so you dont get flamed.
Like I said someone else may be able to analyze it for you.
Sent from my GT-N7000 using Tapatalk 2
Well it happens on all JB versions. 4.1.1 or 4.1.4. Already tried nightly, asylum, paranoid, liquidSmooth and one more the name i cant remember. Also tried mixing kernels and radios but no success so far. I tried to send sms woth different app and still nothing. Turned out i only cam recive sms but camt send them.
It's definitely some sort of a bug on AOKP rom. Take a look also on this guy's issue (I guess his issue was pretty much the same as yours) - http://forum.xda-developers.com/showthread.php?t=1789241
letters_to_cleo said:
It's definitely some sort of a bug on AOKP rom. Take a look also on this guy's issue (I guess his issue was pretty much the same as yours) - http://forum.xda-developers.com/showthread.php?t=1789241
Click to expand...
Click to collapse
Thanks, it's a same issue. As soon as i deleted that message signal came back. Sending still doesnt work but maybe it will be easier to figure it out.
This is wierd. On CleaNote wich is 4.0.4 everything works fine but on Paranoid 5 wich is also 4.0.4 with Tablet UI i get that error...
Paranoid 5 is based on latest CM9 nightlies if I'm not mistaken, CLeaNote is based on Stock TW ICS only.. that alone you can figure why your getting that issue on PA5 and not on pure stock based ICS custom ones.
A friend has the same problem with the same configuration...
It has something todo with the combination N7000 + T-Mobile Austria + PA.
But he gave up with trying and stays on a Stock-Rom.
Is your Note unlocked? Did you have tried a other SIM? Only to check if it's related to the provider...
I also had the issue. It is because somehow the system looses the SMSC number. I downloaded GO SMS and entered my carriers SMSC number manually under Settings/Send Settings/Customized SMSC number.
Working now.
Try update the SMSC by dialing *#*#4636*#*#
Sent from my GT-N7000 using xda app-developers app
JonnoSmith said:
I also had the issue. It is because somehow the system looses the SMSC number. I downloaded GO SMS and entered my carriers SMSC number manually under Settings/Send Settings/Customized SMSC number.
Working now.
Click to expand...
Click to collapse
That's it. Thanks a lot man. I don't know how this happend but for once stock app did send my msg without any problems. What I did was right after first boot I go into smsc settings, hit refresh and then update. Thing is that worked just for once. I tried doing this again after re-flash but didn't work. Also I did this after reflashing from 4.0.4 but I dont think that it has anything to do with this. Anyway trick with GO SMS works and I thank you once again.
hey there, i cant find the sms-app since 16th may 2013 using temaseks 10.1 build, kowalski kernel @Old bootloader
there is no possibility to send sms because of missing possibility to write and recieve. other mobile says test-sms gets delivered, but at my p990 there will be no message.
temasek build v62 and v63, http://forum.xda-developers.com/showthread.php?t=2090369 with kowalski kernel exp121v3 or exp122, gapps-jb-mr1.1-noneon-20130221-signed
i wiped to factory reset and reflashed several times, wiped system also, but no sms
tried to write directly into temasec's thread, but i have no permission :/
if you have any idea how to get sms back to life, plz answer here
thx a lot in advance
hradreset + new baseband didnt help
flashed other baseband (P990_V30B_00_CP) and tried both temasek v63 and v60 with (at this times) actual kowalski-kernel and still no sms
really strange because i had no problems with v60, problems started at patching at v62, but now even with new baseband, reset and old versions i cant write or read sms
edit: new mms.apk in /system/app and restarting didnt solve my problem
Try installing gosms from the playstore. See if that helps
Sent from my LG-P880 using Xparent Purple Tapatalk 2
go sms pro works, thank you very much for this information =)
but i'm still wondering why the cm-sms-app doesnt work ... but i have to live with that as it seems