Related
Hi,
I recently bought a nearly new Milestone that had already had the 2.1 upgrade. The weird thing is that the phone seems to want to randomly turn itself on and off on a regular basis.
I've read elsewhere on some forums that others have experienced similar random rebooting issues since they updated to the latest software.
Anyone here experiencing similar problems?
Thanks
serialzapper said:
Hi,
I recently bought a nearly new Milestone that had already had the 2.1 upgrade. The weird thing is that the phone seems to want to randomly turn itself on and off on a regular basis.
I've read elsewhere on some forums that others have experienced similar random rebooting issues since they updated to the latest software.
Anyone here experiencing similar problems?
Thanks
Click to expand...
Click to collapse
build number?
This is a known bug that was introduced in 2.1-update1, it is fixed only in these builds:
SHOLS_U2_02.34.3 and SHOLS_U2_02.36.0, but these are only for China/HK
According to Motorola support forums, a new SIM card could also do the trick.
Other than that, our only chance is to wait until the 2.2 update reaches us : (
I also had the random reboot problem with my Milestone (factory 2.1 update 1, UK 02.31.0). When the HK 02.34.3 came out, I flashed it manually, and haven't had a single reboot since. Current uptime about 188 hours. And my SIM is about 8 years old.
adendum said:
This is a known bug that was introduced in 2.1-update1, it is fixed only in these builds:
SHOLS_U2_02.34.3 and SHOLS_U2_02.36.0, but these are only for China/HK
According to Motorola support forums, a new SIM card could also do the trick.
Other than that, our only chance is to wait until the 2.2 update reaches us : (
Click to expand...
Click to collapse
Thanks for the news - as a first step, I will try to get a new sim card fro vodafone UK. Thanks
for this reason i sent mine back, and i now have another device.
alot of calls to moto support though. they suck!
Issue now resolved - I updated to the leaked ROM U2.36.0 update and not a single random reboot so far...
Did you use the GOT one? I put it last night and no reboot since
serialzapper said:
Issue now resolved - I updated to the leaked ROM U2.36.0 update and not a single random reboot so far...
Click to expand...
Click to collapse
I use 2.36 and still having random reboot. Even it is greatly reduced from previous rom.
The reboot random, sometime when i set an alert on calendar, when it ring... reboot
Sent from my Milestone using XDA App
bijixda said:
I use 2.36 and still having random reboot. Even it is greatly reduced from previous rom.
The reboot random, sometime when i set an alert on calendar, when it ring... reboot
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Same on my MM. I changed SIM and still restarting. One restart per two days
bijixda said:
I use 2.36 and still having random reboot. Even it is greatly reduced from previous rom.
The reboot random, sometime when i set an alert on calendar, when it ring... reboot
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
magmik said:
Same on my MM. I changed SIM and still restarting. One restart per two days
Click to expand...
Click to collapse
Thanks for giving information....
I decided to keep my 02.34.3 after that !
02.36 and no more reboot, alarm work (Got sbf)
serialzapper said:
Hi,
I recently bought a nearly new Milestone that had already had the 2.1 upgrade. The weird thing is that the phone seems to want to randomly turn itself on and off on a regular basis.
I've read elsewhere on some forums that others have experienced similar random rebooting issues since they updated to the latest software.
Anyone here experiencing similar problems?
Thanks
Click to expand...
Click to collapse
I've the same problem here
adendum said:
This is a known bug that was introduced in 2.1-update1, it is fixed only in these builds:
SHOLS_U2_02.34.3 and SHOLS_U2_02.36.0, but these are only for China/HK
According to Motorola support forums, a new SIM card could also do the trick.
Other than that, our only chance is to wait until the 2.2 update reaches us : (
Click to expand...
Click to collapse
when the problem will be solved from Moto side? I need the official Arabic ROM
I believe the source of the problem is in the cell part of the phone. Whenever I do something that requires a data exchange, or right after I end a call, the phone reboots instantly. I'm not saying it happens every time I do those stuff, as far as I see, the phone reboots.
I hope the 2.2 update fixes this.
dpwr
I'm also facing this problem. Does a new sim card really works? I have updated to the newest firmware but still the problem persists. Anyone can help?
Sent from my Milestone using Tapatalk
Is there a fix, or different apk, for the email stock app (not gmail) that will fix the auto capitalization and auto complete? All other apps seem to work fine, but mail.
I am currently on Pinnacle 1.3 for Captivate, but had the same issue on Cognition 5, v1 and v2.
I saw there was a possible fix in the CM7 thread, but I tried to install it with CWM and it failed.
Thank you in advance for help.
Sorry if this post is in the wrong area, but I think I am okay. I have posted this question in the Cog and Pinnacle threads, but got no response.
Is it possible that no one else has this issue? Is it just me? Interesting that I have posted this several times, in different forums, and do not get a response?
Please reply if you do or do not have this issue. Thank you.
I have the same issue with the leaked 2.3.3 GB ROM. I haven't looked for a fix.
It is nice to know I'm not completely alone, but it is still interesting how few responses are here. Not sure what to make of that...
Anyone? Please... I have to get this fixed or I will have to bo back to early releases that didn't have the issue, which I really do not want to do...;-(
I really don't know. Only thing I would try is pulling the email apk from a froyo and using it on your ROM. I don't know if it will work or not.
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?
So I'm running the ics rom from Virtuous Quattro and I can't send MMS and yes I have checked data roaming and I have unlimited MMS.
What to do?
Thanks!
________________________________
Phone: HTC Incredible S
Status: S-OFF - Root
Rom: Virtuous Quattro Rc3
Android version: 4.0.3
Android for life!
+1
Ive got the same problem. and i noticed that it happend after i installed a new gps to the system "Sygic". I tried to change roms and radios but the problem doesnt fix, no mms.
I had the same problem it has something to do with gsm vs Cdma.
Sent from anus using xda crap
I tried again and it send the MMS.. This is weird
________________________________
Phone: HTC Incredible S
Status: S-OFF - Root
Rom: Virtuous Quattro Rc3
Android version: 4.0.3
Android for life!
Your apn settings correct? Can't send mms if it's wrong.
I have had the same issue with every ics/MIUI ics rom that I've used. Turns out that my carrier has a third apn for WAP. Soon as I configured it, I was up and away. Check with your carrier. Hope this helps.
Edit: maybe not. Only worked twice on 2g. Not on 3g.
Is the issue solved or not? If yes please edit the title to let others know.
MMS issues on IceColdSandwich
I'm also wondering if you got this sorted. I have been on the last few builds of ICS loving it but I cant send or recieve mms. Sms is fine and mobile data is fine just mms. I just formatted everything, all partitions except sd card, system, data and boot followed by the sd card for good measure. I then installed ics 7.0 error 404 (love that title by the way). On first boot went through set up excluding restoring from google back up. So no apps installed except what was with the rom. checked my apn, it matches what both a Google search, Nonverbose (and other xda folk) and Optus themselves gave me. Attempted to send via MMS a 5.04kb jpg file and... wait for it... STILL no luck! I'm loving this ICS ROM but I really don't understand why some folks just can't send mms' when others can? I may end up having to go back to Ginger bread and thats like going back to B&W telly after HD LCD lol
Anyone know of a trick that I don't????
I can send them on Niks ICS 1.2 one v Rom so I wonder what the culprit is
TheBeardedDoom said:
I can send them on Niks ICS 1.2 one v Rom so I wonder what the culprit is
Click to expand...
Click to collapse
I'll be back on kaijura's ROM in the next day or so and will have a try.
Thanks mate I put an update in there maybe ten mins ago. I noticed on Niks it had wap 2.0 as a setting in APN and its not there in Kaijura's. It is odd because I have managed to send a couple not long after flashing 7.0 again with tiamat. Then flashed vdd sent 2 then kaput. Its got me buggered, I can do a log cat but it doesnt seem to show much to me.
MMS Help Thread
Kaijura has started a ICS mms/sms trouble dev thread it is here
TheBeardedDoom said:
Kaijura has started a ICS mms/sms trouble dev thread it is here
Click to expand...
Click to collapse
Yea I got the same issue. Tried different apn configs, 3 different kernels, deleting all other apn's on menu (virgin, exetel) nothing worked. Back to cm7....
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.