Hello Everyone,
First my compliments to this forum. It's simply amazing.
I have update my ZR to 4.3 unlocked the bootloader rooted it and did the dual recovery thing.
This all works execellent.
I restored the call log with Titanium Backup (and with SMS Backup +). Now I can not see the call log in the dialer.
Installed "Call Log Monitor" and with that program I can see the complete log.
New calls are visible in the dailer and in the "Call Log Monitor".
I am confused :silly:
Who can un-confuse me please?
Tried a factory reset.
Tried the complete installation of 4.3 again.
Still the same.
??
I used the Nordice RC2 version of the firmware. Because that was the first one I found on XDA.
Should I have used the Dutch RC3 one?
http://forum.xda-developers.com/showthread.php?t=2465088
Am I the only one with this problem?
The default dialer does not display the restored calll log.
Other dialers (and call log monitors) from the playstore display the complete call log.
Is this normal behaviour for the stock dialer?
Related
Hi All,
I was using fido OS_Acer_4.004.12.PA.FIDO_A22F_A rom and everytime I got a call from unknown person (not in my contacts) I could see his/hers name and number in the call log. I have decided to flash to LCR-2 Rom. I have installed Malez Recovery 0.6.2, rooted my Liquid-E and and made nandroid backup.Then I have flashed my Liquid with OS_Acer_4.002.14.EMEA.GEN1_A22F_A, installed Malez Recovery 0.6.2, rooted the phone again and flashed with LCR-2 and everything was working just ok. After few days i have noticed that in the call log there are no names with the phone numbers of callers who are not in my contacts. So I have returned to the official OS_Acer_4.002.14.EMEA.GEN1_A22F_A and tested my phone for the missing names( it was perfect with the fido rom). What i have observed is that when i am receiving a call I can see the caller's name and number. It does not matter if I answer the call or not but when I go to the call log I can see his name for a second and then the name disappearsand only the number stays in bold.
So I have decided to go back to Fido rom but I was not able to do nandroid recovery. I am getting an error:run 'nandroid-mobile.sh restore' via console!
I have spent some time to read about this error and was unable to restore my original (stock) rom.
I have tried to load OS_Acer_4.002.14.EMEA.GEN1_A22F_A again with Malez, do the backup and restore but same error.
I found a source for the stock or modified fido update but the links are outdated...
Any help is welcome,
Thank you
Update
I have changed the SD card for a different one (2GB) and I moved nandroid backup files to it. I was able to restore my stock rom and there is no problem with the missing names. Then I loaded Froyometalv3.1 rom. After that the caller's names started do disappear again...
I was using Samsung 16GB class 2 card. Is there any special preparation of the card before using it with the phone ? Why I couldn't restore nandroid backup from it ? Is it too slow ?
Any idea with the caller log ?
Thank you
Hello,
Sorry if my English is broken, English not my native language.
This is my first post here, i am a noob (yes i watched the noob video). I searched on this forum using the search engine of this website, and i used google to try and find an answer for my problem. so far no succes or match with my problem found.
problem
After succesfully installing CM 10.0 (going from android 2.2, froyo), I recoverd all SMS messages, contacts, user apps etc. from titanium backup. Everything seemed to be working fine, but then I noticed that I can not open any SMS messages. any time i try to do this a pop/up appears showing that Messages has stopped. after some testing i found out that no new messages were shown, while sending messages was no problem. since sending/receiving SMS messages is rather essential on a phone, i would really like to fix this problem
problem details
I CAN send SMS messages
I CAN NOT open SMS messages (view SMS threads)
I can not see any new incoming messages, those might either be not visible or not received at all. (also no notification is shown)
Sending an SMS message to a unknown phone number resulted in a new thread, this could also not be opened.
I think that titanium backup caused this problem, I didnt test it before restoring the back-up of titanium, so it might be something else as well.
phone details
Samsung Galaxy S GT-I9000
android version: 4.1.2
smallband: I9000XXJVT
kernel: 3.0.31-gdabec1a [email protected] #1
CPU: ARMv7 Processor rev 2 (v7l)
CyanogenMod-version: 10.0.0-galaxysmtd
Build-number: cm_galaxysmtd-userdebug 4.1.2 JZO54K eng..20121113.054130 test-keys
Message app details:
Came with CM 10.0
version: 4.1.2-eng..20121113.054130
Who can help me or point me in the right direction?
if possible, i'd rather not do a factory reset or delete all my messages
Deleted, wrong post
I tried two other things so far: deleting all messages and re-installing the messaging app. Neither of these worked... and the messaging app is still closing when trying to open a message.
I also checked the SMSC number, this seems all-right.
sending SMS still works, so i really have no idea what the problem could be... Any suggestions?
edit: upgraded to 10.1.0 RC2, receiving works now, opening does not. I replaced the stock app with handcent, which works well enough.
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
Quick question, although I suspect I know the answer....
Screen shot says it all, backed up my messages under KITKAT and now on last Jelly Bean and cant recover my messages....
Is there any way I can do this.... I have a spare xperia s which could maybe be utilised to help recover and/or backup in a more universal way than I did before.
Its not that I have a massive attachment to my messages except there are some phone numbers I could do with in the backup.....
Device Model is C6903 on build number 14.1.G.1.534. The messages wold have been backed up on C6903_14.4.A.0.108 FW.
I don't understand the 'non-deodexed' term? Maybe this would help me understand why I cant restore the messages?
I wonder if i could install the C6903_14.4.A.0.108 (of firmware version to my Xperia s maybe I could restore the messages on that phone and then export in another way ...........
I have "restored a system app from a previous version' but the only problem is the lac of message restore, oh and by the way my dialer icon has dissapeared "app not installed' any ideas about this.........this is its distressing as I now have a phone that is NOT a 'phone' !!
Thanks again in advance for pointing me i a helpful direction
Hello Everyone...
Posting here first rather than in the "Update Failure" thread because I'm not so sure I have a "failure" with the update....just an issue after the udpate.
I have 2 cloned HTC M9 phones. I say "cloned" as they are exactly the same make, model, ROM, etc (one business, one personal phone). They have the following information if needed:
Sprint HTC M9
SuperSU Free v2.65
Custom ROM ViperOneM9 3.5.0 with no custom kernal
Android 5.1
HTC Sense 7.0
Kernal (standard) 3.10.49-perf-g26c593c
[email protected] #1
SMP PREEMPT
I updated some apps this as I normally do through Google Play. A little while afterward I was prompted to update the SU Binary. I did so on one of my phones. I hit the TWRP option (on the right side of the prompt screen), nothing happened, phone did not reset so I rebooted into recovery. The update ran automatically and the phone rebooted.
I noticed two issues (perhaps there are more). The huge problem is that I cannot make OUTGOING calls. I use a custom dialer PixelPhone Pro. I click on a contact to dial and nothing happens. I type in number to dial, hit the green "send" button to make the call, nothing happens.
I also tried the stock Phone app....same thing, cannot dial out.
I attempted to update the Profile and PRL for the phone, however, as that appears to need to make a "special call" that function is not working either
The other problem I noticed is with an app I have called Quick Settings. The app is always accessible through the pull-down notifications on the phone. Although the app is still installed and functional, it no longer appears in the pull-down notifications. I tried to reset the option to show it there (turning the option off and back on) and it will not show up despite the proper setting chosen.
I still have full root access as I tried a couple root apps (such as Titanium Pro) and have full root access.
I have been prompted on my other phone to update the SU Binary and I am concerned with doing so. Any idea why this is happening and how I can troubleshoot and fit my outgoing call issue??
THANK YOU all very much!!
Scott
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Scudderb said:
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Click to expand...
Click to collapse
**UPDATE**
Still problems....
Right after I first updated the binary the "only" problem was that I could not make calls which I could use the other functions of the phone. I rebooted the phone and I cannot reach any function of the phone because I constantly get the message "...the process com.android.phone has stopped" obviously related to the previous problems.
I dirty-flashed the ROM...that did no help. I even tried to flash an older SuperSU version (I don't know what that would have done....I'm running on HOPE now ) and that didn't help. Re-dirty-flashed the ROM a second time. Again that didn't help.
I flashed an old backup and THAT WORKED fine. Problem is that the backup is 6 months old. I could quit and totally clean/wipe/install the ROM and start again from scratch but I reeeeeeallly don't have time for that at the moment.
Is there ANY way I can simply get my com.android.phone process back?? Why did all this happen in the first place??
ANY help is greatly appreciated!! THANK YOU!!!