I found a file called "PPPPStrand_xxx_Ricky" in my Internal Storage, anyone know what this is? It almost seems like a virus. I opened it as a text file and it seemed like a random string of alpha characters, there's a "VSTA" and "VSTB" in the string.
I tried Googling this but came up with nothing, thought maybe one of you devs would know what this is.
There is some consistency with this file however, it exists on my two Android devices:
1) Nvidia Shield K1 running LineageOS 14.1, Magisk, Adaway
2) Samsung Galaxy Note 4 - Verizon running MODest ROM, Magisk, Adaway
I found this file on both platforms, I thought maybe there's something common between the two?
Can anyone help me with this please...
For me , galaxy s5 the same. an my parner also the same file in root dir. Original rom. What is it?
Curious, do you use any IP cameras from Vstarcam? I use Vstarcam with their Eye4 software on my Android devices and Windows machines, and both Android devices had this file, I deleted the Eye4 software from my Android device, and the file still remained, I deleted the file, and the file never came back.
I installed the Eye4 software, no file, but after logging into my Eye4 profile to access my cams, the file came back. So the conclusion is that it's tied to the Vstarcam/Eye4 in some way...
Just to chime in, I also found that file on my phone and I also use Eye4. Has anyone tested it using Suneyes TS instead to see if this file also comes up? If not, I might switch back as they both are very compatible with each others cameras.
nuclear_bullet said:
Curious, do you use any IP cameras from Vstarcam?
Click to expand...
Click to collapse
Just to confirm that I do use Vstarcam's PNP VsCam and I do have that file.
I have the same...and i use StarCam.Olsow i have bitdefender full license and they tald me that this is not ,,a problem,, . S9 Samsung
Related
Hello XDA, I'm new here and I haven't found any info regarding root on the aforementioned tablet. I know its only been out a short while and isn't anything to shake a stick at, however I believe that the ability to root and install custom ROMs on this device would allow it to run much smoother even with the low grade hardware.
Anyhow if anyone is willing to look into rooting I would be appreciative. I did find something where a fella tried kingoroot, towelroot, and one other method which apparently worked on the ellipsis 7, but had no success. If anyone else is in favor reply and let's get some attention. Thanks XDA.
stealth_sli said:
Hello XDA, I'm new here and I haven't found any info regarding root on the aforementioned tablet. I know its only been out a short while and isn't anything to shake a stick at, however I believe that the ability to root and install custom ROMs on this device would allow it to run much smoother even with the low grade hardware.
Anyhow if anyone is willing to look into rooting I would be appreciative. I did find something where a fella tried kingoroot, towelroot, and one other method which apparently worked on the ellipsis 7, but had no success. If anyone else is in favor reply and let's get some attention. Thanks XDA.
Click to expand...
Click to collapse
It's a real shame that no one's done this. There are guys, here, that write whole ROMs for tablets they don't even own and no one's taken a shot at a root. Not being a coder, i can't but there are so many talented guys here i'm just really surprised someone didn't lean over, fart, and put out a root. lol.
Just no real demand for it for these tablets.
Verizon is charging more for these than what you would pay for a MUCH better tablet like a Nexus 7, or Gpad 8.3, etc...
The only people that are "buying" them, are the ones that VZW is giving away for free with you upgrade your phone and add the tablet to your data plan for $10 a month. If not for them giving them away for free, nobody would have one.
I'm stuck with a nexus 8 and require root.
the latest update was forced and now hundreds of my apps will not work due to not being allowed to change sd card files. Root for me is not cool or optional.
zerothis said:
I'm stuck with a nexus 8 and require root.
the latest update was forced and now hundreds of my apps will not work due to not being allowed to change sd card files. Root for me is not cool or optional.
Click to expand...
Click to collapse
Hundreds of apps don't work with the small and incremental update? Like which ones?
For 1, I cannot imagine even having hundreds of apps... But the update was a small one, nothing significant, and I don't see why they would have stopped working?
Disabling writing to the SD is hardly incremental!
can't add new accounts
about half my created files on SD were deleted (save games, notes, configurations)
since existing files on SD cannot be changed, and new SD files cannot be created, the following apps will not function as I need them too, or fail to do anything:
roguelike classics
angband variants
angband
humble bundle app
es file manager
astro file manager
retro arch
and bible
hacker's keyboard
teamviewer for remote
teamviewer quicksupport
android VNC
scummvm
gdosbox
unipatcher
andftp
nesemu
snes9x
gbaemu
androgens
freeciv
That's just a few of the top of my head. Since some of those are emus, each adds hundreds more games and software that will not work (I own over 8000).
zerothis said:
Disabling writing to the SD is hardly incremental!
can't add new accounts
about half my created files on SD were deleted (save games, notes, configurations)
since existing files on SD cannot be changed, and new SD files cannot be created, the following apps will not function as I need them too, or fail to do anything:
roguelike classics
angband variants
angband
humble bundle app
es file manager
astro file manager
retro arch
and bible
hacker's keyboard
teamviewer for remote
teamviewer quicksupport
android VNC
scummvm
gdosbox
unipatcher
andftp
nesemu
snes9x
gbaemu
androgens
freeciv
That's just a few of the top of my head. Since some of those are emus, each adds hundreds more games and software that will not work (I own over 8000).
Click to expand...
Click to collapse
What format is your SD card formatted in? Maybe something changed with the update... like the Shield Tablet cannot write to the SD card if it is over 32GB and formatted with exFAT... it needs to be in NTFS for anything higher than 32GB...
Maybe the same case here? Try copying the files to your PC, format the SD card with your PC(and specify NTFS and defaults for everything else), not the tablet because the tablet will format in exFAT even if it is larger than 32GB...
Try that and see if it works.
My Ellipsis 8 is on the latest update, and I can read and write to the SD card just fine... Not sure what the issues are that you are having.
What size SD card do you have?
I have this tab, and rooted. It took me a while to get the right combination though. Go here (it's in Chinese): http://www.kingroot.net and click on the download button with the Android icon to download the kingroot apk. Find a way to install the downloaded apk to your tab. You are rooted. I didn't like the kinguser root manager so I used this Replace_Kingroot_With_SuperSU.zip to change to SuperSU for root managing. The zip is attached. Just unzip, copy the "mrw" folder to your tab and use adb as root (either terminal emulator or adb shell from your computer) to run this command:
sh /sdcard/mrw/root.sh
Click to expand...
Click to collapse
. Ignore the errors that may appear. After a while SuperSU will open and ask you to update binary. Do so and reboot. you are still rooted, but with SuperSU as root manager.
Now if only there were any custom ROMs...
immortalsoule said:
It's a real shame that no one's done this. There are guys, here, that write whole ROMs for tablets they don't even own and no one's taken a shot at a root. Not being a coder, i can't but there are so many talented guys here i'm just really surprised someone didn't lean over, fart, and put out a root. lol.
Click to expand...
Click to collapse
Rooted using Kingroot just download and open click root let it do its thing if it fails select try again.... After root is established install suoerSUme let it do its thing.. Viola Root
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
Just want to start out by saying, I HATE HATE HATE how Android has to keep everything so secretive and hard to access. Android works great, but when you want to do something as simple as grabbing files from an app, everything tries its hardest to stand in your way from root access bs to apps detecting if Magisks non functional anti hide is on the system. Enabling root and using root file access apps are so damn useless and crash all the time. Worst part is, they don't even show the files you are looking for when you find the right directories so wtf, what's even the point. /rant
I have a game/app that stores files on my expanded SD card storage. The files get downloaded *somewhere* and my phone detects the 5 GB of storage its using. How can I find the exact directory my phone is using that calculates the size of the files, and how can I gain access to these files to copy over FTP / USB / ADB etc to my computer.
I've spent so many hours trying to figure this out. Closest I got was making ADB backup pulls for the app but the archive is corrupt / incomplete every time so nothing will extract in full.
My device is a Samsung Note 3 running Android 7.1 Lineage.
Figured I would come here for help since I bet there's some Android developers that know a simple trick or two to just extract some simple unencrypted files. Very very much appreciated for any tips or guidance!
blalnstk200 said:
Just want to start out by saying, I HATE HATE HATE how Android has to keep everything so secretive and hard to access. Android works great, but when you want to do something as simple as grabbing files from an app, everything tries its hardest to stand in your way from root access bs to apps detecting if Magisks non functional anti hide is on the system. Enabling root and using root file access apps are so damn useless and crash all the time. Worst part is, they don't even show the files you are looking for when you find the right directories so wtf, what's even the point. /rant
I have a game/app that stores files on my expanded SD card storage. The files get downloaded *somewhere* and my phone detects the 5 GB of storage its using. How can I find the exact directory my phone is using that calculates the size of the files, and how can I gain access to these files to copy over FTP / USB / ADB etc to my computer.
I've spent so many hours trying to figure this out. Closest I got was making ADB backup pulls for the app but the archive is corrupt / incomplete every time so nothing will extract in full.
My device is a Samsung Note 3 running Android 7.1 Lineage.
Figured I would come here for help since I bet there's some Android developers that know a simple trick or two to just extract some simple unencrypted files. Very very much appreciated for any tips or guidance!
Click to expand...
Click to collapse
There is a note 3 section
https://forum.xda-developers.com/galaxy-note-3/help
Sent from my mata using XDA Labs
sd_shadow said:
There is a note 3 section
https://forum.xda-developers.com/galaxy-note-3/help
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
? I need help with Android the software, not Note 3 hardware
blalnstk200 said:
? I need help with Android the software, not Note 3 hardware
Click to expand...
Click to collapse
Every manufacturer implements Android differently
Sent from my mata using XDA Labs
As you might know, palm rejection on non stock roms has not worked for a long time. The symptoms are that when you try to draw with the s-pen in apps like squid or OneNote, often what you draw gets immediately erased.
I went back to CM13.0, where it supposedly did work, and checked what the difference is. I got lucky, and found the right files. It seems that palm rejection was removed from the file InputReader.cpp in frameworks_native/tree/p/services/inputflinger.
I'm sure there was a very good reason for that removal, probably because this is not the right place to do it. I tried to see what would happen if I put it back. I compiled XenonHD with the change, and now my s-pen works great! I tried squid, one note, gboard handwriting and others, and all works. I think this change can probably be easily incorporated into all AOSP/LOS roms.
The files are at https://github.com/ghostwheel/frameworks_native/tree/p/services/inputflinger , and you need InputReader.cpp and InputReader.h
As I said, there is probably a better way to enable palm rejection, but this works for now.
Update Actually, it seems the change was introduced between 14.1 and 15.0 . Look here: https://github.com/LineageOS/android_frameworks_native/blob/cm-14.1/services/inputflinger/InputReader.cpp. But I can't find the particular change that
caused this. Maybe it didn't have a great reason?
help me how to implement this to a rom
Might be interested in trying this (assuming I just replace/modify some files, right?) I'm assuming its harder than that.
Can you please make detailed tutorial? Both Havoc and LineageOs android 10.0 have this problem.
You just need to take InputReader.cpp, InputReader.h and also InputDispatcher.cpp from the github above to the code, in frameworks_native/services/inputflinger/. The problem is that usually you don't have control of that dir. If you take control, it is easy.
ghostwheel said:
You just need to take InputReader.cpp, InputReader.h and also InputDispatcher.cpp from the github above to the code, in frameworks_native/services/inputflinger/. The problem is that usually you don't have control of that dir. If you take control, it is easy.
Click to expand...
Click to collapse
Im suspecting you can use something like ES File Explorer (yes I still use an older version I have saved in TB) to just copy those files into the directory?
Dave
I used to use ES file explorer...
All these are source files that need to be compiled together with the android dist.
It might be possible to just copy the result, maybe services.jar inside framework??? Not sure. The right way is to download a distribution, copy the files into the right place, and compile. XenonHD has nice instructions of how to do all that. Though, XenonHD already has all that built in, for exactly that reason....
Thanks a lot, I am really new to all the terms you are using. All I know is to download zip file and flash it with TWRP recovery installer. I can also get the files fro github. What I dont know is: How to modify rom zip file and recompile it back to flashable zip?
Due to this issue, I am keeping my Note 4 in stock android 6.0 unfortunately, this will be life saver for me if you can help anyhow,
Thanks a lot.
I've just had a stock OnePlus Nord N10 running Android 10. For years now I've kept a html file on the internal storage of my Android devices that I've used as a homepage for my web browsers that have all my favourite links laid out nicely. On my older OnePlus 3 running Android 8 I open this using the following URL in the browser url bar:
file:///storage/emulated/0/Dropbox/Other/Web_Links.html
And it opens fine.
On the Nord N10 it is failing with an ERR_ACCESS_DENIED error in the browser. I'm getting this in both Chrome and Edge. The URL appears to be correct (typos give me a file not found error) so I'm at a loss to know what's causing this. It feels a bit like the browsers aren't asking for the right permission to open files from file:///storage/emulated/0/ but I don't know how to get them that permission.
If I open the file from a file browser sending it to the web browser it opens fine, but gets a url in the form of content://media/external/file/39531 in the url bar only that url seems to only last until the next reboot.
Just to muddy the waters more - I had a couple of Moto G 5G Plus's running Android 10 a couple of months back that had to be returned because I just couldn't get a decent 4G signal on them and I had the same issue on them, but did "something" and got it working for the file:///storage/emulated/0/... url. Only I wasn't sure even at the time what I did to get it working.
Any help would be appreciated. Even if it's a dummy's guide to how apps relate to file:///storage/emulated/0/ and what specific permission they need to access it.
Hal18ut said:
I've just had a stock OnePlus Nord N10 running Android 10. For years now I've kept a html file on the internal storage of my Android devices that I've used as a homepage for my web browsers that have all my favourite links laid out nicely. On my older OnePlus 3 running Android 8 I open this using the following URL in the browser url bar:
file:///storage/emulated/0/Dropbox/Other/Web_Links.html
And it opens fine.
On the Nord N10 it is failing with an ERR_ACCESS_DENIED error in the browser. I'm getting this in both Chrome and Edge. The URL appears to be correct (typos give me a file not found error) so I'm at a loss to know what's causing this. It feels a bit like the browsers aren't asking for the right permission to open files from file:///storage/emulated/0/ but I don't know how to get them that permission.
If I open the file from a file browser sending it to the web browser it opens fine, but gets a url in the form of content://media/external/file/39531 in the url bar only that url seems to only last until the next reboot.
Just to muddy the waters more - I had a couple of Moto G 5G Plus's running Android 10 a couple of months back that had to be returned because I just couldn't get a decent 4G signal on them and I had the same issue on them, but did "something" and got it working for the file:///storage/emulated/0/... url. Only I wasn't sure even at the time what I did to get it working.
Any help would be appreciated. Even if it's a dummy's guide to how apps relate to file:///storage/emulated/0/ and what specific permission they need to access it.
Click to expand...
Click to collapse
If device's Android is rooted try this
Code:
adb devices
adb shell "chmod 0644 /storage/emulated/0/Dropbox/Other/Web_Links.html"
jwoegerbauer said:
If device's Android is rooted try this
Code:
adb devices
adb shell "chmod 0644 /storage/emulated/0/Dropbox/Other/Web_Links.html"
Click to expand...
Click to collapse
It's not rooted, and I don't really want to root it. The Moto wasn't rooted either.
Does Android do anything "odd" with permissions when copying files around that might be causing this? It was copied in from a memory card.
Hal18ut said:
Does Android do anything "odd" with permissions when copying files around that might be causing this? It was copied in from a memory card.
Click to expand...
Click to collapse
By default, when you create a file as a regular user, it’s given the permissions of 644 ( means: rw-rw-r– ). These permissions don't get stored with the file but within the filesystem where the file is located. Hence when you transfer a file from one filesystem ( here: external sd-card ) to another one ( here: internal sd-card ) , the initially granted permissions get lost.
jwoegerbauer said:
By default, when you create a file as a regular user, it’s given the permissions of 644 ( means: rw-rw-r– ). These permissions don't get stored with the file but within the filesystem where the file is located. Hence when you transfer a file from one filesystem ( here: external sd-card ) to another one ( here: internal sd-card ) , the initially granted permissions get lost.
Click to expand...
Click to collapse
Any tricks for copying (or moving the file) so it gets the correct permissions? Also, any non-root way of viewing them to confirm this is cause of the issue?
The best I've come up with so far is to save the .html files in Android/data/com.microsoft.emmx/files/Download/ and then reference them with file:///storage/emulated/0/Android/data/com.microsoft.emmx/files/Download/Web_Links.html which appears to work. Presumably substituting com.android.chrome for com.microsoft.emmx will work for Chrome.
Still don't understand why Edge and Chrome don't have access to URLs via file:///storage/emulated/0/ nor how I got around this on the Moto.
There might possibly be another way, but I cannot recall the details on how to do it or whether it requires root or not. Some devices have special internal URI's that enable, e.g., debug mode, which can be invoked via omnibox in the form of in-line commands. I remember in particular my car's Android head unit had this for it's native browser and after enabling debug mode,. I was able to browse `file:///` and its subdirectories. My unit did have root at the time, but I want to say that regardless this wasn't accessible without the debug command being enabled, so I would infer it might not require root (but that's purely conjecture). This is not a persistent state, but the command could be saved as a bookmarklet for ease-of-use. I've never looked into whether this is a common or unique Android function, or something the OEM developed.