Related
just flashed jb 4.2 on my gnex and wanted to move pictures back to sdcard/dcim folder (from sdcard/0/dcim), so i moved with root explorer but now everything is messed up because the all pictures have the same date and time...
luckily i've a backup on my pc, but if i try to copy/paste using mtp connection the pictures will lose the date property again.
how can i get the old cronology?
Did you ever receive an answer for this question? Im having the same issue with my nexus 4
beren said:
just flashed jb 4.2 on my gnex and wanted to move pictures back to sdcard/dcim folder (from sdcard/0/dcim), so i moved with root explorer but now everything is messed up because the all pictures have the same date and time...
luckily i've a backup on my pc, but if i try to copy/paste using mtp connection the pictures will lose the date property again.
how can i get the old cronology?
Click to expand...
Click to collapse
May I ask why you want to move them? It doesn't really make much of a difference does it? I would imagine that they revert to the time and date that they were moved since that would count as the last time they were 'edited'? 4.2 is set for multiple users, so you as the primary user get sdcard/0 and (if it ever becomes active for phones) the next user would have sdcard/1.
ArmandHammer said:
Did you ever receive an answer for this question? Im having the same issue with my nexus 4
Click to expand...
Click to collapse
actually i find out how to show files in correct order:
go to gallery--> camera album (or whatelse)-->option, group, time
now you see pictures grouped by time, go back in the album and pictures will be in correct order.
i think the time is tagged in the foto, and don't care if the files have wrong date.
joeb3786 said:
May I ask why you want to move them? It doesn't really make much of a difference does it? I would imagine that they revert to the time and date that they were moved since that would count as the last time they were 'edited'? 4.2 is set for multiple users, so you as the primary user get sdcard/0 and (if it ever becomes active for phones) the next user would have sdcard/1.
Click to expand...
Click to collapse
mmm from what i know the right path for sdcard is /storage/emulated/0 for main user, ../emulated/1 for second and so on.
but i got ../emulated/0/0 (because of known cwm problems), so wanted to manually fix, and also because didn't like to see the "0" folder under sdcard
maybe i'm wrong but didn't want to wipe and format sdcard after flashing new cwm...
I've been going nuts on the latest CM11 nightly 4.4.2 with the camera not being able to save its pictures to your sd card automatically and also multiple crashes...some fixes I found, writing new permissions mostly just didn't work or wouldn't stick if you rebooted.
I now have 2 different optional APK file and INSTALL fixes...1st is just the camera apk which I ripped out of the liquidsmooth cm based kitkat 4.4.2 which works flawlessly. The 2nd is a gallery apk fix that I ripped out of the slimbean 4.3.1 rom and it reinstalls the gallery apk which also has its own camera that will install along with it...both fixes work, both camera's are slightly different from each other though and function differently based on the gallery that is installed
This method requires Titanium Backup...you can get it on the play store and the free version will work just fine
HERE'S THE CAMERA APK FIX:
-backup your systems "camera" app before doing anything! don't blame me for losing the camera if something fails
-once backed up, uninstall the camera app and if using titanium backup, move the backup files to another location out of the titanium folder located in your INTERNAL storage
-download the camera zip files I made here
-extract the zip file and you'll get a folder named "camera files"...copy and paste the files inside, do not extract any of these files, to your titanium backup folder located on your INTERNAL storage
-once copied over, open up titanium backup and look for the camera apk file with a line through it and should say beneath it "1 backup"...click on it, hit restore and choose app and data, that's it! it should now be there and fully functioning
HERE'S THE GALLERY APK FIX:
-backup your systems "gallery" and "camera" apps before doing anything! I won't be held responsible if this doesn't work for some users
-once backed up, uninstall the gallery and camera apps
-download the "com.android.gallery3d_1.1.40012.apk" file I made here
-install the apk file by simply clicking on it and choosing install, it shouldn't need any special permissions but if so, refer to next step
-install the gallery apk by using a root file manager (I use root browser lite) and move the apk file to system>app, change the permissions to rw-r--r-- then select "ok" and then install it and reboot. after reboot, you should now have your gallery back and a newer camera icon that is darker gray in color with a dark blue center camera lense, open the camera app
-go to it's settings>more settings and to the right you'll now see an sd card icon, click and select the sd card and test it out!! that's it
video of using root browser lite to change permissions...in the video, it's a silent screen recorded guideline, my app was already installed, so I highlighted the options that show how to change the permissions and then when I highlighted showing "cancel/view/uninstall", if it wasn't installed the option would say "cancel/view/install"
https://www.youtube.com/watch?v=Uow9OyLVGRI&feature=youtube_gdata_player
*Newly added!!*--reinstalling sprint zone and voicemail
to install, follow the exact same steps as installing the camera/gallery apk files
-voicemail apk link: com.coremobility.app.vnotes
-sprint zone apk link: com.sprint.zone_4.6.017
if this worked for you, please post up and let us all know
giving this thread a bump...i revised the apk installation steps since redoing this process after a few updates of cm11, they fixed the camera as far as adding the option for sdcard storage but I've been getting a lot of hang ups and crashes then "unable to retrieve camera" error messages when trying to open back up, even after a reboot.
I even installed today's release of the cm11 nightly and the camera was a crashing mess over and over, so for any having these camera issues, here you go!
im wondering if i will ever be able to use the sprint voicemail. since i loaded carbon 4.4.2 and wondeing if there was any way of making it easy to make a call from your messaging by just sliding either right or left instead of tapping?
using sph-l710
villaf7420 said:
im wondering if i will ever be able to use the sprint voicemail. since i loaded carbon 4.4.2 and wondeing if there was any way of making it easy to make a call from your messaging by just sliding either right or left instead of tapping?
using sph-l710
Click to expand...
Click to collapse
yes you can! I have done this already, I installed the voicemail and sprint zone apps on my cyanogenmod 11 4.4.2 and they work...I'll make apk's for them as well and post them up, give me a few
edit...all uploaded for you my man, just do exactly the same as I noted doing for the gallery app installation, where to place it and changing the permissions, any issues post back up
Just wanted to say, tried most if not all AOSP roms and for some reason all of them freeze when switching back and forth. This is the only one that works 100%.
Thanks for the find.
ssmercurys said:
Just wanted to say, tried most if not all AOSP roms and for some reason all of them freeze when switching back and forth. This is the only one that works 100%.
Thanks for the find.
Click to expand...
Click to collapse
you're welcome and thanks for posting that it works! I kept having the same issues with the cameras on the cm11 and 10 roms, this 1 never failed me
Just a heads up, the stock camera in slimkat (4.4.2 ROM) works perfectly, the devs fixed it on that rom
Sent from my SPH-L710 using Tapatalk
noles4life50 said:
Just a heads up, the stock camera in slimkat (4.4.2 ROM) works perfectly, the devs fixed it on that rom
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
awesome, this camera apk I have listed here is from the slimbean 4.3.1 rom which is probably why it works perfectly on 4.4.2 slimkat, same devs
thanks working on att gs3 on metropcs running unnofficial Beanstalk 4.4.2 rom 20140206 release... fix "cant connect to camera" error. Thanks again
Thanks so much! I first created a backup. I used root explorer for the whole thing. I tried uninstalling via TiBu first, but it didn't actually remove the camera and gallery apks. I then tried ES File Explorer, but that requires you to set root to Apps and ADB, and I had deselected ADB some time ago.. I downloaded the apk and copied it to /system/app. I then manually deleted the two apks, changed permissions on your apk and installed. Rebooted and works wonders. Thanks!
I would like to suggest a n00b-oriented, step-by-step guide.
1. Use your favorite recovery manager and back everything up. This way, you can always go back if you mess something up.
2. Download and install Root File Explorer (Free).
3. Launch Root File Explorer. It will ask to download and install a few tools. Let it.
4. Go to where you downloaded the file (probably sdcard/Download). Hold your finger on the name and select copy.
5. Press the "Home" icon on the bottom left of the screen.
6. Click on the folder named "system" and then click on the folder named "app".
7. Select paste to copy the file here.
8. Press and hold the newly copied file, and select "Permissions".
9. Set the permission to rw-r--r--, or 0644. In other words, select "Read" for all three, and then select "Write" for Owner. Everything else should be unchecked, and hit OK.
10. Scroll down and fine GoogleGallery.apk and GoogleCamera.apk. Select GoogleGallery.apk and press uninstall. Then long press the apk and delete it. Do the same for GoogleCamera.apk.
11. Find the new apk that you just downloaded (com.android.gallery3d_1.1.40012.apk) and press it. Select install.
12. Once installed, back out of everything and reboot your device. When the device reboots it will say it is updating 1 application.
13. You are now rebooted with the new, fixed, camera. The icon is now darker, and with a blueish/purpleish lens.
14. No, none of your files have been deleted. Enjoy your working camera!
15. Check out the new options! In the extended settings, you can now click on the SD card icon and instantly select to use your internal storage or your external SD card (if present) to save your photos to!
16.Give goku2778 your Thanks!
Is there a way to disable the shutter sound?
LaRocky said:
Is there a way to disable the shutter sound?
Click to expand...
Click to collapse
unfortunately no it doesn't have that option. I did however find another camera apk that works, gonna upload that and link in here around 10am eastern time this morning.
thread bump...newly added camera only apk and revised a bit of the initial part of the guide...enjoy!!
goku2778 said:
unfortunately no it doesn't have that option. I did however find another camera apk that works, gonna upload that and link in here around 10am eastern time this morning.
Click to expand...
Click to collapse
Found this out last night, the camera that comes with the Gummy Nightly (AT&T Galaxy S3 Android Development forum) comes with a camera that has more settings and the shutter sound can be disabled via the android system settings/sound options. I don't know if the shutter sound option is always there in system settings as I didn't check the previous roms.
LaRocky said:
Found this out last night, the camera that comes with the Gummy Nightly (AT&T Galaxy S3 Android Development forum) comes with a camera that has more settings and the shutter sound can be disabled via the android system settings/sound options. I don't know if the shutter sound option is always there in system settings as I didn't check the previous roms.
Click to expand...
Click to collapse
the other camera I listed does have more options to it if you wanna give it a try, can't hurt none, actually let me try it on mine right now see about the shutter sound....
nope, shutter stays on, it just gives the option to make the power button shutter (take the pic)...sorry man, I could care less about the shutter sound myself lol if I come across another 1 i'll bump this again, maybe I can find that gummy camera apk online and test it out
goku2778 said:
the other camera I listed does have more options to it if you wanna give it a try, can't hurt none, actually let me try it on mine right now see about the shutter sound....
nope, shutter stays on, it just gives the option to make the power button shutter (take the pic)...sorry man, I could care less about the shutter sound myself lol if I come across another 1 i'll bump this again, maybe I can find that gummy camera apk online and test it out
Click to expand...
Click to collapse
Thank you, I'll have to try it out. I have verified that the Shutter Sound option (under System Settings/Sound) is not available in another rom (Liquid Smooth) so it looks like the developer has to manually add the option (not built in to the camera). And Liquid Smooth's camera settings are detailed.
LaRocky said:
Thank you, I'll have to try it out. I have verified that the Shutter Sound option (under System Settings/Sound) is not available in another rom (Liquid Smooth) so it looks like the developer has to manually add the option (not built in to the camera). And Liquid Smooth's camera settings are detailed.
Click to expand...
Click to collapse
been wanting to try that rom out myself, maybe I'll install that today and check out the camera...and then, rip it out also lol I'll bump the thread again if I do that
edit...so I've been to liquidsmooth and back lol same exact camera as the 1 I added yesterday, only differences is the system settings with more options like disabling the shutter sound. so I guess just stay on that rom for now for the shutter options, I tried lol
Trying to do this fix on beanstalk on my galaxy s3, and when I try to install, I'm getting a parsing error. Any idea when I'm doing wrong?
I've backed up and uninstalled my original camera app, and moved the first linked camera app into my system/app folder. Changed the permissions to rwrr,and then when I try to install I get the parsing error.
Gareee said:
Trying to do this fix on beanstalk on my galaxy s3, and when I try to install, I'm getting a parsing error. Any idea when I'm doing wrong?
I've backed up and uninstalled my original camera app, and moved the first linked camera app into my system/app folder. Changed the permissions to rwrr,and then when I try to install I get the parsing error.
Click to expand...
Click to collapse
weird...try this then, delete that out of the system folder, download it again and just open it and hit install, see what happens then...is this beanstalk 4.3 or 4.4? if it fails again, try the 2nd optional fix, that has been the more all around solid fix so far for both 4.3 and 4.4 roms
Gareee said:
Trying to do this fix on beanstalk on my galaxy s3, and when I try to install, I'm getting a parsing error. Any idea when I'm doing wrong?
I've backed up and uninstalled my original camera app, and moved the first linked camera app into my system/app folder. Changed the permissions to rwrr,and then when I try to install I get the parsing error.
Click to expand...
Click to collapse
Try this:
Uninstall stock camera.
Reboot.
Install goku camera apk.
Change permissions.
Convert to system app with titanium backup.
Reboot.
Hope this help
Sent from my SAMSUNG-SGH-I747 using xda premium
hi all
so my transition to kitkat hasnt been without its hiccups and the latest one is probably quite big. So since 4.4 we're not allowed to write in the external SD as I have seen it put. my problem is shown by 2 different apps. one is the gallery (or quicpic that I use) when trying to delete a photo I took (and since I have my photos being saved on the SD) I get a message saying it failed! gallery seems to let me do it and delete the photo but when I check in quicpic or the files themselves the photos are still there. the other app is my sms backup and restore app where again I have my backup saving to the SD but when I try to select it it says I wont be able to use it and as is expected when I try to back it up it doesnt work.
why would they implement such a policy?! that goes completely backwards! is there a fix or a workaround?
really appreciate the help
You can fix it by rooting (+ e. g. NetApp SDFix) or wait for app developers to change their apps (in terms of storing data in private data folder, for instance '/storage/extSdCard/Android/data/com.google.earth') - or if possible change the storage path by yourself.
Sent from my black pearl using Tapatalk
nunein said:
You can fix it by rooting (+ e. g. NetApp SDFix) or wait for app developers to change their apps (in terms of storing data in private data folder, for instance '/storage/extSdCard/Android/data/com.google.earth') - or if possible change the storage path by yourself.
Sent from my black pearl using Tapatalk
Click to expand...
Click to collapse
how can developers change their apps since they wont be allowed to write on the SD? and what do you mean change the storage path by myself? as in to have stuff save on my phone? cuz thats what Im avoiding
As I wrote: every app has write access to its 'private' data folder of the SD card (if it creates such a folder). The folder name has to match the app name.
For instance '/storage/extSdCard/Android/data/com.example.app'
Disadvantages are that other apps do not have write access to these folders - and that data of an app will be deleted from its 'private' data folder if the app will be uninstalled.
The temporal solution is to root and use any KitKat fix to write in SD, there are single apps xposed modules flashable zips write some string in some system file.
fburgos said:
The temporal solution is to root and use any KitKat fix to write in SD, there are single apps xposed modules flashable zips write some string in some system file.
Click to expand...
Click to collapse
any pointers on where I could find such a thing?
See post no. 2: SDFIX (from NextApp), available here or at Play Store
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar? Ans: Apparently yes, it is a "feature", aren't we lucky.
Am I missing some special setting? Ans: No.
Any thoughts on what the issue could be or if there is a fix? Ans: It can be fixed using root magisk.
Are your mount points similar/different? Ans: Guessing not and isn't related to the problem.
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)? Ans: Not the cause of the problem.
Thanks
meltwater.
i thought i was the only one with zero bytes files. and when you transfer them back- all good
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
dvijetrecine said:
i thought i was the only one with zero bytes files. and when you transfer them back- all good
Click to expand...
Click to collapse
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
SUPERUSER said:
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
Click to expand...
Click to collapse
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
meltwater said:
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
Click to expand...
Click to collapse
Magisk is the new "supersu" standard when it comes to root.
So it is the root per say. Yes you need root. But you root your phone by installing Magisk, its kind of a multi-tool.
You need to unlock your bootloader, if not already unlocked if you bought it that way like I did from Tradingshenzhen.
It will say Unlocked on the bootloader mi splash screen when you turn the phone on if the bootloader is unlocked.
And then you need to properly flash TWRP. Other than that you can stay on stock rom and use Magisk
Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ExSDCard Write Access Enabler module thread https://forum.xda-developers.com/apps/magisk/module-exsdcard-write-access-enabler-t3670428
I see something I did not see before.
In the thread OP mentions:
Since the v3.3 ZIP version, a feature has been added especially for Oreo (Android 8) users, on this Android version, several special permissions can be used by any app.
For exemple, theses specials permissions are used to get access to reading logs, managing the power of the device.
If you want to use this special feature, you just have to follow theses easy steps:
- creating a simple file named "ExSDCard_Oreo_apps" in the module path, so: /sbin/.core/img/ExSDCard/ExSDCard_Oreo_apps (remove any extension).
- Write all the apps package names that require a special permissions, one by line, for exemple:
Click to expand...
Click to collapse
So with this you can apparently create custom rules for apps that don't support selecting the external SD card path.
Maybe you should look in to that and experiment
This bug happened across android 8.0 in various brand.
Since I familiars with ES File Explorer, I solved by root the phone, convert ES File Explorer into System app via Titanium Backup, then everything work perfectly fine. No more 0 bytes copy file.
ES File Explorer still work even I un-root my phone by uninstall Magisk.
If you're really not want to root your phone or any other reason. Just copy file that you want then restart your phone. Copied file will now become usable file.
My bootloader isn't unlocked and for now I'd rather avoid rooting my phone (may well do so later).
Good to know there are work-arounds, and that my device hardware is ok.
Will have an experiment and see if I can live with it until I have a go at rooting. Even if I do the temp fix of ES explorer.
Thanks for the info and tips.
Same **** for me. 1 year to solve this stupid bug and they dont have fix this **** yet
Say thanks to xiaomi[emoji108][emoji867]
Enviado desde mi MI MAX 3 mediante Tapatalk
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Wmateria said:
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Click to expand...
Click to collapse
Yep, looks like it is a solid bug. For now, I'm living with it and use the space I have on internal memory to transfer data to before using a System file manager to transfer to SDcard.
Been trying some app development and now found the "Install via USB" bug.
Again can work around it, but it does spoil debugging with Android Studio.
There are certainly some odd bugs on this phone, I suspect down to Xiaomi going "off plan".
meltwater said:
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar?
Am I missing some special setting?
Any thoughts on what the issue could be or if there is a fix?
Are your mount points simlar/different?
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)?
Thanks
meltwater.
Click to expand...
Click to collapse
no need for this post. erased.
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
jorgeepelos said:
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
Click to expand...
Click to collapse
Get a Mi Mix 2S
Wmateria said:
Get a Mi Mix 2S
Click to expand...
Click to collapse
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk
jorgeepelos said:
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk[/QUOTE.
It's people like you who make the community bad when you out your hatred in the forums or is not knowledgeable enough because main post talks about THIRD PARTY FILE MANAGER APPS not 1ST PARTY Xiaomi File Manger APP and thinks it's the end of the world on here and the Xiaomi forums. And trust me there is plenty of you people around pushing Devs and OP here by complaining when other people already stated the fact many times on a thread, and trust me, I hardly take offense. "Read", it works.
Click to expand...
Click to collapse
Simple mod to back up all your photos in Original quality to Google Photos without it being only in High Quality.
Requirements: Root
1st Method
Instructions:
1. Download Root Explorer
2.Download the Nexus.xml file
3. In Root Explorer go to system/etc/sysconfig
4. Paste the .XML file there
5. Change to file permissions to 0444 (read only)
6. Clear Data/Cache from Google Photos
7.Reboot
8.Enjoy unlimited original photos backup
For those who this method doesn't work, there's another method I've found.
2nd Method
For this method you'll need BuildPropapp.
Download the app from the file I've provided or from playstore.
Open the app , At top right corner you'll find a pencil icon. click on it, You'll see a list of codes.
Now you can either manually find the following values or use the find option in the menu from top right corner.
Change The Following Values:-
<strong>ro.product.model=Pixel 2 XL </strong>
<strong>ro.product.manufacturer=Google</strong>
<strong>ro.opa.eligible_device=true</strong>
After changing the values. Click on save icon and close the app.
Again wipe the user data of Google photos and reboot your phone.
That's all...
1st parking and wait for people try out
Edit: it actually works. But it adds on top of your current google drive storage (my max storage 19GB + extra 11GB from this mod, total I have 30GB now)
Yayy...!! It's working
It works thx
Didnt work for me [emoji17]
Thanks working great
It's working.
zhosi said:
It's working but the google photos app it's not working as it should now. When i try to edit a photo just says loading an nothing happens. Any idea?
Click to expand...
Click to collapse
Try reinstalling the app and makes sure to follow every step. This method works fine on my 9T Pro Global ROM. Idk about custom ROMs. Edit works on mine. Idk if it works but Hide GPhotos in Magisk and got to app management and give every permission to GPhotos.
Mickxalix said:
Try reinstalling the app and makes sure to follow every step. This method works fine on my 9T Pro Global ROM. Idk about custom ROMs. Edit works on mine. Idk if it works but Hide GPhotos in Magisk and got to app management and give every permission to GPhotos.
Click to expand...
Click to collapse
Thank you very much, indeed it works as it should now and no issues with the app ????
Did you check if your Google Drive used space increased or not when backing up new photos?
Didnt work on pocophone f1.
Does not work with me, unfortunately. Is there any other way that I would really like to use??
Thank you so much.
Works on K 20 Pro and on One Plus 6.
Work on my mi 9 t pro; i've only set different rw/r/r (644) cause 444 doesn't work for me
Now Gphoto says that my ''pixel'' has unlimited space in original quality thanks for sharing
When I paste xml file its says its blank is that ok?
Milots said:
When I paste xml file its says its blank is that ok?
Click to expand...
Click to collapse
Long press using Chrome and click download link
Just so you guys know, if you guys moving from android to ios, the Google photos will consume all your free storage ( 15gb for gmail,gphotos,contact etc ) , so better think twice if you want to do this.
ShazlieyAzizan said:
Just so you guys know, if you guys moving from android to ios, the Google photos will consume all your free storage ( 15gb for gmail,gphotos,contact etc ) , so better think twice if you want to do this.
Click to expand...
Click to collapse
This is true even for a Pixel device.
Just buggered my buildprop and my phone doesn't boot properly anymore, do you guys have the original value for "ro.product.mod_device" for this device? Not sure if global/non-global makes a difference?
Thanks
timvonlee said:
This is true even for a Pixel device.
Click to expand...
Click to collapse
I find this stupid, I used to do a full quality backup. Later then I switch my device to an iPhone then found out that my storage is overused 44gb/15gb. I cannot receive any email because there is no free storage left so I have to subscribe to 100gb storage for 2dollar per month. Ezmoney for google