I read somewhere that Andriod is giving a separate username to each application. However this is not my wheelhouse and I could be grossly mistaken. This makes me think that a user that does not own or belong to the root group would rely on an x in the the "other" group in order to execute the file EG -rwx From what I read it's read write and execute. You are probably right that I don't understand permissions. I hear you saying that I'd have a better chance of figuring all this out if I root my phone. Its clear that you have a very in-depth understanding about these things Larry, Thank you so much for your in-depth engagement here. Other Android developers are much more likely to have the pertinent knowledge, and on an Android forum they are less likely to regard the issue as off-topic which will also improve your odds of getting a useful answer. My recommendation of a different forum was intended to improve your odds of success and help keep this forum on-topic. I do not hope to disabuse you of your hope(s). While you are likely right that my issue is with my environment and not with SQLite, my hope is that other SQLite enthusiasts may have bumped up against this issue and be able to help with how to solve it. IOW, the 'x' bits do not mean quite what you think they mean. (They do not on Linux, and I'm too lazy to check this on other Unix-like systems.) They do not mean that that, once loaded, program image text segments from the file will be physically executable. I would not expect the per-file permission bits to reflect whether the block device was mounted with the noexec option. The per-file execute permission is separate from the effect of the noexec mount option. It suggests that the 'x' bit is less significant (with respect to today's problem) than you seem to think. I saw the difference between "RWXRWX-" and "rw rw -" (on your "emulated storage") as significant and related to the "noexec" mounting. When you said its a clue that the comment noexec is relevant, How can you say that when the permission says RWXRWX- Doesn't that say that the base user should be able to execute? I just don't think that's a constraint that is going to be flexible during troubleshooting or allow you to do the experiments that would allow you to figure out what the relevant factors are that lead to today's problem. I do not question your motivation for wanting to avoid rooting a phone. If it were just for me, fine, but if I want others to use it who may not be as enthusiastic about rooting, wouldn't it be great if it could work? The reason for not wanting to root is that I wanted to develop an application / extension that others could easily use without rooting their phone. I ran into another roadblock on this application so It took me away from this issue, but I appreciate all those who have posted here so responsively, thank you for all your support / engagement on this! I suppose I could do two different sessions and see if the file ownership is the same. However if the ownership happens as i'm hoping, I wouldn't need to rename it to exe.Īnother thing I don't know is if each instance of shell would create its own user, meaning I need to do all my shell commands in one session? Make a file that's owned by shell and make a file that the SD card is recognizing as executable. Hopefully this would accomplish two things at once: Using cat to read sqlite3 and save it to a new file called sqlite3.exe. I have yet to test it but I was considering using something like: Even with the EXE extension, some files are running properly. I also read somewhere some people are getting success with changing a linux file to linux_file.exe on SD card so that the SD card recognizes it as executable. So that means that if I want to execute the file under the user permission, it needs to be owned by shell app ? I found somewhere that Android has a separate user for every application. However if there are dependencies that i'm missing, I'd love to know about it. So from what I understand the version I got is the CLI version MDataSample.The name of the package escapes me at the moment, but it had a folder with three files Source is route.png in drawable folderīitmap bitmap = ((BitmapDrawable) getDrawable(R.drawable.route)).getBitmap() Convert source to bitmap: // MyData class holds image data * Save images like JPEG, PNG, WEBP into drawable folderĢ. Many people ask how to add the image to SQLite database.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |