hi there,
lately i've been having problems with Whatsapp and my hw keyboard....when i try to use it the whole phone locks up! and i have to pull battery!
when i use onscreen i dont have any problems!!
ive been having problems since last version, ive contacted whatsapp but they say it phone related! i sending them logcat logs tomorrort and they are investigating!!
i was just wondering if anyone else had problems atm???
i'm running debloated stock 906!
ive tried; reinstall whatsapp, recover older version of whatsapp, factory reset of phone and recover backup from TB, even full recovery and new whatsapp install! (without recovery!)
Nope, running 7326 works fine in both GB and CM10 with keyboard
Related
Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.
have the exact same problem... can dial out no problem but only receiving calls. so thinking about whether I should flash another rom until this is fixed.....
I was wondering could I just do a factory reset and then flash the rom over again? Do I have to disable the voodo lagfix before? Not too sure how this works heh.
I don't have this problem. But whenever i am in the game "flick kick football," I get some random hangs, and is forced to close. I suspect that happens when I get incoming calls. Anyway to confirm this?
Jule1k said:
Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.
Click to expand...
Click to collapse
I have the same problem. I recived a call, something force closed, the signal dropped and i lost the operator. I had similar problems with bluetooth and file manager before on this ROM, but I re-flashed it and everything worked again.
no problem here with Darky's 5.2 ROM and the Clean Guide Instruction, i just received a call without any problems
I used the easy guide and did not clean anything or do a factory reset, I just followed it like a dumbo. I came from 2.1-update1 stock JM5 kernel with a ton of apps installed, if that helps.
hey I think I found a solution to this. I went to recovery mode, wiped cache, wiped dalvik, did a factory reset and voila, receiving calls works without force closing.
phew.. was about to download another rom. anyhow, hope that works for you Jule!
still a few problems with the ROM that i encountered:
- my AT&T home button is not working.... not to sure whether there will ever be a fix for it
- media volume, even set to max, is not working when playing movies and youtube.
anyone experiencing this problem? I'm getting A LOT of crashes.
I'm not using any task killers what so ever.
Rooted or not rooted? Stock ROM? Custom ROM? Under what conditions does it crash?
Stock ROM and I have no idea what the circumstances are, it seems sporadic.
Hmm. Are you rooted? You could try fixing the permissions using the ROM Manager app if so. If not, perhaps a re-flashing of the RUU might be in order to fix it.
Hi!
I am having the same problem. My Acer Liquid E keeps crashing. It is reproduceable: when I log on the network the first call I receive is without problem, when I receive the second call com.android.phone crashes and the network is dropped (input SIM key). Then I can again receive one call without problem.
My phone is rooted (z4root) and I use Titanium Backup. I can solve the problem by resetting to factory settings. But it keeps coming again after a couple of days. Of course I would like to know what causes this but at first I would be very happy to know how to get rid of the problem when it is there ... Titanium is not so helpful:
When I restore the Titanium backups:
-I first restored my user applications plus settings without problems, after this everything still works
-Then I restored some of the green marked backups in Titanium Backup. After this the phone starts to have this problem again.
Does anybody know which backup this might be? I mean: solving the problem itsself would be great but at first it would be nice to be able to get the phone working quicker than factory reset. Maybe this could be achieved by resetting to an old backup with Titanium Backup (just need to know which one ...)
Help would be appreciated! Been browsing the net a long time and could find lots of ideas how to solve this but none worked so far.
My system settings:
-Acer Liquid E
-FroYo from the start (updated from .8 to .14 when I first had the problem)
-removed some apps from the rom - but nothing essential and I know that non-essential sounding things like maps or talk are actually essential. I removed things like twitter, roadsync, etc.
Daniel
daniu, unfortunately it's unlikely anyone here will be able to help you as you have a completely different phone. This forum is only for the HTC Incredible S.
Hi!
I know ... but I am not really sure this is a problem of my specific phone. I read a lot about this kind of problems for many different phones. Mine is not really that common - but I think I will crosspost - thanks for the hint
Daniel
Actually this is also happened to my IS, running ARHD 1.1.5 with latest radio.
I notice this bug after i flashed my radio to non-stock radio.
I haven't try to revert back to the original radio, and the bug remains mystery.
com.android.phone FCs can be caused by incompatible older version sim cards. Try consulting a retail store of your carrier to check if there's a need to upgrade your sim card.
Sent from my HTC Incredible S using XDA Premium App
Hi!
I read about the old SIM-Card idea but I doubt it in my case cause the problem can be reinstalled with Titanium ...
EDIT: this link may be interesting for this problem.
Regards Daniel
I have had the same prob on virgin AU stock rom. Did factory reset and kept getting the same problem. Sent the phone back and they replaced it. Getting the same FC after about a month on the new phone :/
Hi!
I don't think that this is a hardware problem. That's why I think you can send your phone as often as you want. They cannot give you other software than the one you can get yourself ...
regards
Daniel
Sorry but i can't post in development.
I had Zeus 6.37 installed in my OB but was eagerly awaiting for a ICS or JB ROM.
So I tried CM10. Everything worked fine except for the known issues (video recording and the lack of GPS). These issue made me go back to Zeus since I want a fully functional phone.
I decided to update to Zeus version 7.06. Did full wipe before Rom installation. Then just recovered sms with "SMS backup & Restore".
I found a some problems:
1. Sometimes when I make a call the process "android.phone" closes the phone loses signal and only after a while I can repeat the call.
2. Sometimes the SMS app (Go SMS) shows no texts. But after I close the app or reboot the phone the messages show again.
Usually these problems appear simultaneously. I reinstalled the ROM but the problem is still there!
Does someone have an explanation? And what can be done to solve these problems.
I wish I never changed from Zeus 6.37 :crying:
jonascotch said:
Sorry but i can't post in development.
I had Zeus 6.37 installed in my OB but was eagerly awaiting for a ICS or JB ROM.
So I tried CM10. Everything worked fine except for the known issues (video recording and the lack of GPS). These issue made me go back to Zeus since I want a fully functional phone.
I decided to update to Zeus version 7.06. Did full wipe before Rom installation. Then just recovered sms with "SMS backup & Restore".
I found a some problems:
1. Sometimes when I make a call the process "android.phone" closes the phone loses signal and only after a while I can repeat the call.
2. Sometimes the SMS app (Go SMS) shows no texts. But after I close the app or reboot the phone the messages show again.
Usually these problems appear simultaneously. I reinstalled the ROM but the problem is still there!
Does someone have an explanation? And what can be done to solve these problems.
I wish I never changed from Zeus 6.37 :crying:
Click to expand...
Click to collapse
Go to recovery mode againg and clear the dalvic cache now.. no need to reinstall anythng..
after update i was also having some FC but i cleared the dalvic cache and cleared partion catche..
its working like a charm... only less backup with battery..
My friend's LG 4X HD has problems.
With one (and only that one) SIM com.android.phone crashes. I've tried other SIMs and they do just fine. I've also tried the problematic SIM on my GNex and it works like a charm.
I've tried looking at the logcat, turns out the problem is a IndexOutOfBoundsException caused by com.android.internal.telephony.gsm.LgeSIMRecords.run()
Here is a snapshot of the logcat: imageshack.com/a/img10/4903/9z4q.png
Phone is running 4.1.2
Baseband: L6260-MODEM-SIC-02.1233.00
Build: JZ054K
SW VERSION: P88020a-EUR-XX
Update: Hard Reset done, nothing changes. So I guess the problem lies in some system app.
Update 2: Even after downgrading to 4.0.3 it crashes.
dadino88 said:
My friend's LG 4X HD has problems.
With one (and only that one) SIM com.android.phone crashes. I've tried other SIMs and they do just fine. I've also tried the problematic SIM on my GNex and it works like a charm.
I've tried looking at the logcat, turns out the problem is a IndexOutOfBoundsException caused by com.android.internal.telephony.gsm.LgeSIMRecords.run()
Here is a snapshot of the logcat: imageshack.com/a/img10/4903/9z4q.png
Phone is running 4.1.2
Baseband: L6260-MODEM-SIC-02.1233.00
Build: JZ054K
SW VERSION: P88020a-EUR-XX
Update: Hard Reset done, nothing changes. So I guess the problem lies in some system app.
Update 2: Even after downgrading to 4.0.3 it crashes.
Click to expand...
Click to collapse
Some apps reinstalled from titanium can cause this problem. If you find that is the case just go into app settings and wipe data for restored apps. That normally solves these problems. If you don't want to full wipe again just delete app data for all apps and see how you go.
Never used Titanium. The phone is 3 days old, he installed just Whatsapp but I've hard resetted it.
try another sim in his phone, if it works, atleast then you'll know it's not the phone
Settings / apps / all and clear data in contacts and contact storage. It's a pain to get there because of the pop ups but it's doable
Sent from my 4.2.2 Xperia S via Tapatalk
Possible solution
Can' paste Links yet so I have to give You may want to take a look at the explanation and solution at techsplatter
Seems that you are hitting a similar issue.
Search in Google for www techsplatter com comandroidphone-crashing-solved
(Cant paste links yet , thats why I direct you to a google search.)
Hi everybody, I've recently bought a new I8190N, about two weeks ago, coming from a rooted but messed up Galaxy Ace, I decided to don't root it at all just for now, but a few days ago, when I was texting my gf (with the stock sms app), all new messages I was sending were not sending at all, the sending spinner just stayed there forever.
Then, I pressed back and after a millisecond conversations thread became empty, saying "no messages, to write a new message... etc", so I tried backup sms's with Sms Backup & Restore and it did, they were all still there, but neither stock sms app nor go sms pro displayed them. After a reboot, they magically reappeared. From then, it happened once a day independently from how many messages I am sending.
Also, I read of similar problems on lots of other Samsung phones, but no solution was found all over the internet, so, is this a Samsung's Jelly Bean bug or could it be just an app that interferes with mmssms.db? Or a carrier related issue? :banghead: Thanks to everyone who will help me
Sent from my GT-I8190N using a rocket powered banana
Why don't you try a newer firmware with ODIN? As far as I know, first release of 4.1.2 had some bugs.
flash a newer firmware, or software update your phone.
for SIII Mini, I think you need a CM. stock is too buggy and slow to use
I'd try when I will be ready to start with flashing like I did on my previous phone, till then will try to bear the bug... the only thing is that on my NFC model I'll need to flash a different country firmware (if I want to stay stock) for N, or also the non-N firmwares will work? (Obviously losing NFC capability) for what concerns CyanogenMod, I like it but I'm more like a stock-lover thank you guys
I flashed another firmware (mine is from december while newest is from july), done a factory reset and when I restored SMS with SMS Backup & Restore, when it was approximately reaching the restored messages number of a particular message (a message I sent with GO SMS Pro containing emoji coming from the go sms emoji plugin) message app has crashed and bug happened again, so I revert to my origina FW but this time I'm not restoring that SMS. Hope that will fix my bug, because I'm thinking it was a corrupted mmssms.db database file... I'll see and post what happens so everyone having my problem will probably find a solution!
Ok, just appened again, don't know what to do :crying:
Flash CM 10.1 :thumbup:
Sent from my GT-I8190 using xda app-developers app
I found that the culprit was Viber, it goes in conflict with sms databases and causes the bug (maybe because it has the permission to read and edit sms) so after uninstalling it I've never experienced the bug again... it's a little bit strange I think