I recently bought a Nexus 4 and I would like to transfer my photos of my previous device to it. My previous Android phone used the standard USB mass storage which gave 0 problems to copy back and forth stuff, but the Nexus 4, like many other modern Android phones I suppose, uses MTP instead, which has the interesting feature of refusing to copy the original dates/timestamps of the files, using instead the date at which the files are being copied. This is obviously a huge bummer when it comes to photos; not only because one cannot check the original date at which the picture was taken while browsing on the phone, but also because they end up completely unsorted. Is there a way to transfer photos to a Jelly Bean Android phone that doesn't support USB mass storage preserving the original timestamps? Things I've tried so far: - Transferring via USB MTP - ADB push (both full folders and individual files) - Transferring via SSH (using SSHDroid + WinSCP) - Uploading and downloading from Dropbox - Transferring a ZIP file via MTP and uncompressing the file on the phone - Transferring from the other phone via Bluetooth None of them preserved the timestamp, and this is driving me insane. (Also, I am not rooted yet, but if the only viable way requires root I would welcome that answer as well.)

> The app WhatsApp would like to have permission to access my device's > photos, media and files. If I grant permission, exactly what can (could) the application access? Can it access all of the photos on my phone? Or just the photos I have shared or downloaded with the app? Can it access all of the phone's media? Can it access all of the files on the phone? Or does Android restrict what it can access? If so, what does it restrict it to and how? I'm not interested in what WhatsApp says it will or won't access, or even what it has promised in its EULA. I'm more interested in what it could access, if it wanted to when granted the access.

I messed up flashing a beta Android Q build on my phone. After that, I can't flash my stable ROM without error 7 in TWRP - device mismatch. Removing the assert works, but not a permanent solution. So, I digged through google and my own phone for hours and found out why. My device is identified as raphael in recovery, but it is identified as raphaelin in fastboot and while the phone is booted. In recovery:

# getprop ro.product.device
# raphael

In booted mode (i.e. while the phone is booted):

# getprop ro.product.device
# raphaelin

In fastboot:

> fastboot getvar product
product: raphaelin

I checked my build.prop and the value in that file is raphaelin too. I tried setprop and it showed that it can't set that property. So, please advise me on how to set the value using setprop in recovery mode. Or, if you know, please let me know from where the recovery is pulling data for getprop and if I can change that file.

What is the difference between properties manipulated in /system/build.prop file and properties manipulated by setprop, for example setprop persist.adb.tcp.port? Where is the latter property stored? Is there another properties file somewhere?

I want to change device's serial number. I have researched and finding some places that android stores prop file: /default.prop /system/build.prop /system/default.prop /vendor/build.prop /data/local.prop /factory/factory.prop On my device, there are just 2 places for storing prop file: /default.prop /system/build.prop But I view those two files and don't see serial number storing here. I also see that serial number is storing at: /data/property/. But as I researched, this directory is just a memory mapping. So I have tried modify and reset device, all values come back to normal value. Please tell me where android store imei/serial number ... Thanks

I am running Android-x86 4.4 on VirtualBox. Everything works fine. But when I am modifying build.prop (with ES File Explorer or BuildProp Editor) with other manufacturer or model and save it. After reboot nothing happens. In About Tablet stores the old information. Seems that android cache this info somewhere. Any thoughts? How to force Android to update from build.prop

I have a file of unknown type that does not display properly in es file explorer and I have no other app installed that can open it. Can I use the terminal emulator (or some other method?) To determine it's file type so as to google the extension and find an appropriate app?

I've been testing one of my apps to see how it handles filenames in UPPER-CASE. I *thought* the Android libraries and system was case sensitive for filenames, however I eventually discovered that files on the SD card are matched without case-sensitivity. Here's an example taken from a Samsung Ace phone (my Nexus 4 behaves similarly)

adb shell

$ pwd
/mnt/sdcard/testDaisyReader/casesensitivebook

$ echo "" > NCC.HTML
$ ls -l
-rwxrwxr-x system   sdcard_rw        1 2013-11-19 18:57 NCC.HTML
$ ls -l NCC.HTML
-rwxrwxr-x system   sdcard_rw        1 2013-11-19 18:57 NCC.HTML
$ ls -l ncc.html
-rwxrwxr-x system   sdcard_rw        1 2013-11-19 18:57 ncc.html
$ ls -l
-rwxrwxr-x system   sdcard_rw        1 2013-11-19 18:57 NCC.HTML
$ 

I would have expected the commands ls -l ncc.html wouldn't find the file I created, however it seems to do so. My Android app also matches files without case-sensitivity. Do any of you have any counter-examples? I'd like to know whether it's safe to assume filenames are matched on the SD-Card in Android, like Windows, without case-sensitivity. Notes: 1. the filesystem on the SD-Cards are FAT32 2. I've found 2 related posts that imply files on the sdcard are case-sensitive: https://android.stackexchange.com/questions/4775/how-can-i-open-an-html-file-i-have-copied-from-pc-to-sd-card-of-phone/47444#47444 https://android.stackexchange.com/questions/55481/how-can-i-determine-the-sd-cards-path/55482#55482