Develop Bugs

contacts error

Hi All,
can anyone advise how I can fix an error on my o2 orbit please.
When I try and manually add a new contact to the phones list, not the sim card, I get 'An unexpected error has occured in this program'. I have also tried to use active sync to upload new contacts and that does'nt work either.
This has only occured since upgrading to wm6.
I have also tried it in safe mode with all other 3rd party programs stopped, incase something was interfering with system somehow.
Any ideas please?
cheers
Andy

[Q] Recent-onset problems with SMS/MMS on Galaxy Nexus

Hi all -
I'm running Winner's pre-CM9 ROM (now on latest build) with Franco's milestone 2 kernel. The latest builds of the ROM are 4.0.4-based.
I had no problems on the previous versions, which were 4.0.3-based. A few days after upgrading to the 4.0.4-based versions (yes, I did do a full data/cache wipe first) and the 4.0.4 versions of the Google apps, someone tried to send me an MMS message. I have it set to auto-retrieve, but in this case it didn't. Tried to manually download it, and it failed. This has happened since with messages from other people from different carriers. If I try to SEND a pic via MMS, the app (stock Messaging app) just crashes. I can still receive regular text messages, but trying to delete some message threads causes the app to crash; some delete OK.
I'm assuming that I'm having problems with the database (/data/data/com.android.providers.telephony/databases/mmssms.db). I tried flipping the permission bits with Root Explorer, but that didn't change anything. Short of deleting and somehow recreating it (don't know if just "touching" the file will work) and losing all the data - is there anything else I can do to solve this?
Thanks!
Everything else is working fine.

Finally just deleted the database file (actually, just renamed and moved it) and it's working again, though I "lost" about 400K of data...the database file was somehow corrupted.

[Q] restored MMS has wrong timestamp

I'm having trouble restoring some backed-up SMS and MMS on my new LG G3. I have tried several methods with varying results and I'm starting to think it's an issue with the G3 because I have not had these problems with the myriad of other devices I have been doing this on.
Titanium backup pro: restore messages from snapshot causes messaging to force close (not surprising). restoring from XML works fine with SMS, but the MMS are all timestamped with the date/time they were restored (today).
Mybackup pro: restoring SMS causes them to have a timestamp of today but it fixes itself when you open the thread (not a big deal, have had this happen in the past). restoring MMS causes only the MMS that were sent by me to be timestamped with today.
now I've just started testing any app that let you restore MMS to see if there'll be any luck. just finished trying Easy Backup and it has the same results as Titanium.
any ideas?? anyone have any luck restoring MMS? what app did you use?

Sorry to resurrect a dead thread, but I'm running into this issue now and can't find another thread discussing a solution.
It seems to occur with two different G3 stock-based ROMs when I tried to restore MMS messages that were backed up on a CM-based ROM. Titanium Backup and SMS Backup & Restore both have the same issue: a bunch of MMS messages get the current timestamp (time of restore). Doesn't seem to be a problem restoring to AOSP ROMS, just LG-based ones.
Any ideas? Anyone else see this?

Same problem here on LG-based roms running on my G2. This seems to be the problem of some manufacturer-based ROMs, not just LG but at least also Motorola.
Preparing the mmssms.db file using https://github.com/t413/SMS-Tools on your Linux desktop rather than directly on the phone (using restore programs) seems to be the working workaround. But I do not envy those who still use Windows as their main system.

For anyone having the same problem, i finally found the solution...
the lg g3 has a custom com.android.provider.telephony service : when the restore app send the mms to restore, the "date" field is not read properly, and the current timestamp is store in the "date" field of the "pdu" table in the database "mmssms.db"
But... there is another field in that table, "insert_time" which contains the good timestamp... almost cause it's a microtimestamp.
So, for the solution :
1/ you need to download and open your "mmssms.db" file using you're favorite sqlite editor
2/ apply that sql query to set a good content for the "date" field based on the "insert_time" field :
Code:
update pdu set date = substr(insert_time, 0, 11);
3/ you send the mmssms.db back to your phone and reboot
That's it !
You're welcome
A finally happy LG G3 owner

patoulich said:
For anyone having the same problem, i finally found the solution...
the lg g3 has a custom com.android.provider.telephony service : when the restore app send the mms to restore, the "date" field is not read properly, and the current timestamp is store in the "date" field of the "pdu" table in the database "mmssms.db"
But... there is another field in that table, "insert_time" which contains the good timestamp... almost cause it's a microtimestamp.
So, for the solution :
1/ you need to download and open your "mmssms.db" file using you're favorite sqlite editor
2/ apply that sql query to set a good content for the "date" field based on the "insert_time" field :
Code:
update pdu set date = substr(insert_time, 0, 11);
3/ you send the mmssms.db back to your phone and reboot
That's it !
You're welcome
A finally happy LG G3 owner
Click to expand...
Click to collapse
Thank you for the explanation!
Although your solution didn't work for me (no insert_time column on my new Axon 7) I ended up joining my old table with my new table and fixing the date, date_sent (and creator...) columns. That worked, and helped me not looking for another 20 apps on playstore that wouldn't work anyway.
Now one major hassle I didn't realized for long hours, google messenger had some sort of cache issues and was not showing me my new data.. so I kept trying stuff with no result... till I tried the stock messaging app and realized it worked.
Anyway, I've been looking at this for 2 days now, so thank you so much, I can finally move on

[Q] [LINE] Can't use SD card. Please confirm SD card settings

Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks

try to apply kitkat sdcard fix
click

I have the Xperia Z3 running on Lollipop.
Same issue, all apps such as whatsapp, fb, etc can access the SD card except for line.
The error message when trying to send a photo to someone in Line is "Can't use SD card. Please confirm SD card settings"
Reinstalled the app several times, unmounted and remounted the SD card, even moved the app to the SD card with the app itself still working fine. But still cannot send or receive photos or download stickers.
Also applied the suggested that sd card fix even though it wasn't really needed since all other apps can access the SD card just fine..anways it didn't help.
Any other ideas?
Oh yeah, even tried installing a Line version which was 6 months old - didn't help either.

mcdimm said:
Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks
Click to expand...
Click to collapse
I have the exact same issue after a full wipe and re-flashed custom ROM. The naver LINE app have the same issue as mentioned above. All other apps functions normal. Anyone found a solution to this yet?
HTC One M7
Vipeone sense-based ROM 9.0.0.

Hi. I've encountered a similar problem recently. The interesting thing is that my telephone does not have SD card at all. So my first thought was that the problem is in permissions or cache.
I checked the permissions - app had full access.
Then I cleared programm cache on my phone. both inner memory cache and telephone memory cache (at least that's what they are called in my native language)
After that I tried to upload the image, yet it gave another error. something like: "cannot perform the action now, try again later"
I was quite short on the inner memory on my phone (around 70 MBs free), and thought it can be the problem. I deleted the biggest app and was able to upload the screenshots again.
Probably worth mentioning: I did not reinstall the Line app.
My device:
Telephone called ImSmart C471. China at it's best. Assembled in Ukraine though, company called Impression.
Android 4.4.2

In the latest build, Line apk cant send photo from internal/sdcard..it said line cant use sdcard..?

i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.

where's the settings?
andrew_susanto said:
i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.
Click to expand...
Click to collapse
I can't find any setting for permission to storage from the application manager, is there any? did I overlooked?

Try updating the app in play store. I had the same issue but solved with the updated version.

I had the smale problem. I deleted some pictures and videos and then restarted the phone. Works like magic

Garmin Connect Problem on Mi9 SE

Hi,
i think the following is a Mi9 SE / MIUI Problem (I am on the newest stable global rom), maybe one of you can help me figure out what it is:
Garmin Connect is the workout/activity sync app on android for all garmin watches.
It lists your workouts and you generate an image from either your gallery or directly from camera and overlay it with data of your workout to send to another app, say instagram, whatsapp, telegram and more.
The problem is that the generated image (which i assume is temporarily stored in RAM and not written to storage) always fails to be sent to the receiving app. For example if I send it to Total Commander, which I use as a file explorer, to save the image to storage it always throws "error opening file: src". I can't send the image to any app.
Tried multiple reboots/reinstalls (of Garmin Connect ) but this problem still persists.
This works flawlessly on my girlfriends Umidigi A3S (running their up to date Android 10 rom) with the same permissions given to the app. Thats why I think this is a MIUI problem.
Does someone have an idea what could be the cause of this?