moto g lollipop upgrade from kitkat 4.4.4, I can send SMS, receive call.
But, whenever I dial a number, try to call someone, I get this message :
Call not sent
What can I do ??
moto g lollipop upgrade from kitkat 4.4.4, I can send SMS, receive call.
But, whenever I dial a number, try to call someone, I get this message :
Call not sent
What can I do ??
When using aLogcat to view my Android log files, I find very few messages showing up in any of the views.
Selecting Verbose level and no filter, I see that Main contains mostly garbage collection debug and info messages, but I rarely more than about 20 messages every minute. Events mostly contains info log messages from alogcat itself, at about the same rate, while Radio remains steadfastly empty.
Being relatively new to Android, I wonder whether this is normal. Is this rate typical of the main system log file on Jelly Bean?
Answer
Not very active if you use apps like aLogcat. The permissions system regarding to logs was changed with Jelly Bean: The permission to read logs "READ_LOGS" is now systemOrSignature, which means that an app that is not signed with the ROM/system key can only view its own log. You can still view the full android log with adb logcat from the SDK.
I think that this was a long overdue change in the log system.
So I am trying to flash my OnePlus One with CM12s through fastboot on command prompt, but whenever I type fastboot update romname.zip I am presented with:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
the specific build I am using can be found here It is the build ending in 8, or the one submitted on 2015-07-08
What have I done wrong?
I am only 5 days into my Billing cycle, and noticed that already like 1/3rd of my data has been used (thanks to My Data Manager)... So I looked to see what has used all this data, and it says it is "Media Storage" that has used up most of my data (it's used up over 35 MB!). This is a system process if i'm not mistaken, so my question is: is this in fact a system process? And why would it be using up so much of my data? What exactly does this process do? Would it be safe to deny it network access?
I have a Google account, and my android is a Galaxy S. I want to transfer all my contacts from my cellphone into Google contacts. If you use the phones syncing option by default, it is a one way sync from Google contacts to your phone. I have also tried CardDav, which I downloaded from the play store. It does the same time, it just syncs from Google, to your phone.
Can some one please tell me how I can sync all the contacts from my android to my Google contacts?
Answer
Just tested this on my phone and my gmail, and it seems to work. I'm running 4.4 with the stock Contacts app on my phone.
:)
I have Samsung Galaxy S2, that was sent to the lab for repair. The phone arrived and all the internal memory was deleted. All the data that was on the internal memeory: Media, SMS, Contacts (actually I synchornized the contacs with my google account, but some contacs were deleted from my phone..)
Is there any way to recover this internal memory? I know that some application can recover an SD card.. but which one can recover the internal memory ?
Answer
There is some hope to recover data which was stored on the “internal SD card”. Samsung Galaxy S2 supports USB connection in the mass storage mode (unlike some other more recent models). This mode provides the required block-level access to the partition which holds your media and other files (but not contacts, SMS and app data). Therefore you can connect your phone to PC in the USB storage mode (not MTP), then use the same utilities as you would use to recover files from an SD card which was accidentally formatted (one free option for Windows is Recuva).
Recovering data from the internal memory is much more harder for several reasons:
You need to root the phone in order to get access to raw partitions (with some phones which have an unlocked bootloader there is an option of flashing an alternate recovery image with root access through ADB). Note that the rooting process in most cases involves writes to the /data partition, which could overwrite the data you want to restore.
The internal file system is not the usual FAT or NTFS, like in Windows (recent models in most cases use ext4), therefore many recovery tools designed for use with Windows filesystems won't work well (scanning the raw disk for pieces looking like data in a well-known format might give a useful result even if the filesystem is not supported, but see the next point).
In most cases the app data is stored in some format not used outside of the Android OS (e.g., contacts and SMS/MMS messages are stored in SQLite databases with the Android-specific schema), and these formats are unlikely to be supported by commonly available data recovery utilities.
And this assumes that the phone repair lab did not just replace the main phone board (which they often do, unless the problem was obviously in some other component).
I am not sure what an app can do to me if it is able to discover my account, to what extent?
Thank you very much.
Answer
This permission is of moderate-high importance. This allows the application to read what accounts you have and the usernames associated with them. It allows the app to interact with permission related to that account. An example would be an app that was restoring your contact, would discover your Google account then send you to Google's login screen. It doesn't actually get to see your password, but it gets to work with the account. This is also legitimately used by applications to add contacts to your accounts, such as dialer replacements and contact managers/backup/sync/etc.
I backed up my Samsung Galaxy S2 on Kies before updating to Ice Cream Sandwich. After the upgrade I tried to restore, but the restore fails ...