I finally managed to get java to work with firefox. I test out runescape and it works great on minimum graphics setting may be able set higher.
Im on 4.1.8.3 with full ubuntu mod. HAS NOT BEEN VERIFIED WITH AN UNMODDED WEBTOP
Here a little guide that I wrote. It should work
Basically
Google Java arm and click Java Embedded
Download ARMv7 Linux - Headful from there
Extract the ejre1.6.0_25 folder and move to phone
Copy the ejre1.6.0_25 folder to
/usr/lib/
Ingore this code if you are running from lxterminal
Code:
su
/usr/bin/sudo -u adas bash
In lxterminal or whatever terminal
Code:
sudo ln -s /usr/lib/ejre1.6.0_25/lib/arm/libnpjp2.so /usr/lib/firefox-addons/plugins/libnpjp2.so
sudo chmod 755 /usr/lib/ejre1.6.0_25/bin/java
sudo chmod 755 /usr/lib/ejre1.6.0_25/bin/java_vm
sudo chmod 755 /usr/lib/ejre1.6.0_25/bin/javaws
sudo chmod 755 /usr/lib/ejre1.6.0_25/bin/keytool
If you get "link failed File exists" run this. then run the ln command
Code:
sudo rm /usr/lib/firefox-addons/plugins/libnpjp2.so
You can also use root explorer to set permission for the files
Set to this:
read write execute
X --- X----- X
X ---------- X
X ---------- X
Then it should work
I attach a screenshot of runescape running
I'd like more information if you would regarding the installation of java as I am a diehard runescape fan myself. I've downloaded the Java embed but it was version _25 and not _21, not sure if it matters. And also, do I have to be rooted or not?
If you come pm me or reply here, that would be great.
I tried this and was able to get the plugin to load, but all I get is black boxes where the applets are. Any ideas? The java plugin shows under plugins. I'm using 1.6.0_25.
I'd like to know how you exactly got it to work? I cant get the lxterminal to run on my webtop, I'm really new and found out basically everything else but how to install the plugin. Thanks for the info.
And according to a thread on xda, cant remember which - the lxterminal was removed from the phone on the most recent update... so how would I get around that?
I did all the commands using Android Terminal Emulator from the Market.
Are you fully updated on your phone? as in 4.1.8.3
because ive tried more than once to get it to work. and no avail.
exactly what commands did you do anyway? because that could quite possibly solve my problems.
I'm on 4.1.83. I used the commands that are in the OP, changing out ejre-1.6.0_21 with ejre1.6.0_25 (which is the folder name for the version I downloaded). Make sure you do not have a folder in a folder. I never got it fully working, just black boxes on the web pages. The plugin does show to be installed though.
OHHHHHHHHHHHHHHHHH, thats why.
actually, nvm ... my files are in the exact location his are. >_<
Should I type the lines 1 at a time? I've been copy and pasting them all at once.
I did one at a time.
?.?
Ok this is my situation as of yet, I currently have rooted atrix, running newest version. I open terminal emulator from market, type in the first line "ln -s /usr/lib/ejre-1.6.0_25/lib/arm/libnpjp2.so /usr/lib/firefox-addons/plugins/libnpjp2.so" and it returns "link failed File exists, so im guessing i've already placed it into the plugins folder.
So far so good, now onto second line -
"chmod 755 /usr/lib/ejre-1.6.0_25/bin/java"
and my return being
-unable to chmod /usr/lib/ejre-1.6.0_25/bin/java: No such file or directory
I would type the rest but i'm sure they would return the same
My files are in the correct location /usr/lib/ejre-1.6.0_25/
any suggestions?
Well I have the full ubuntu mod on my phone. I have not test it doing it though anything other than lxterminal
If you see the plugin in firefox that is good. Im betting the permission are not set properly
you can use root explorer to set the permission on the files that are chmod. Make sure all check boxs under execute are selected.
Check what you copied to the phone and make sure you don't have two ejre-1.6.0_25 folders (one within the other) from when you extracted it.
I extracted it to my sd card then moved the folder, so my locations are exactly what he lists. nothing different aside from the _25 instead of _21 which i change in what I type. I just tried to allow permissions, lets see if this changes anything...*crosses fingers*
Edit: When I type the first line, I get
link failed Permission denied
Stephen Who said:
I extracted it to my sd card then moved the folder, so my locations are exactly what he lists. nothing different aside from the _25 instead of _21 which i change in what I type. I just tried to allow permissions, lets see if this changes anything...*crosses fingers*
Edit: When I type the first line, I get
link failed Permission denied
Click to expand...
Click to collapse
Do you have root?
I have root, plugin shows in firefox, permissions are correct, but all applets just show as a black box. I'm running stock. Do you think it only works with the ubunto mod?
Ok I edited the OP so the commands can be run from android terminal or adb.
Im not sure why it doesnt work for you must be the full ubuntu mod.
I might try downloading a new version of java see if it works
Update
I tried the the 25 version and it worked. I updated the commands. I was able to get it to work using adb.
password for adas:?
edit: and yes, I'm rooted. It's asking for a password when I type the second command line. :|
Related
Is there an ADB push nautilus script out there?
That'll be handy, but i'm no scripting expert. I suspect it'll be bit tricky since adb is terminal only, I'm sure someone will have to figure out a way to pipe the output from terminal to GUI pop up dialog box to display progress bar, with success or failure message.
this one seem to work but no progress bar or success/fail message tho. YMMV
Code:
#/bin/sh
adb push $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS /sdcard
save this as adb_push.sh
be sure to set this file with permission:
Code:
chmod a+x adb_push.sh
think of this as rough draft, not perfect. Above code will push straight to sdcard. Suppose you could create few scripts like this..
ADB - Push to System APP
Code:
#/bin/sh
adb remount
adb push $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS /system/app
ADB - Install APK
Code:
#/bin/sh
adb install $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS
EDIT: Forgot to mention this, it'll work only if you've already set path to Android's SDK tools folder in .bashrc
awesome, thanks! I'll test it in a minute
Simple scrip to push files to your android device.
Just put it in your Nautilus script dir (HOME/.gnome2/nautilus-scripts) and make it executable (chmod +x Push\ sdcard). also set path for ADB inside script (ADB=...)
I did something similar a while back for both Konqueror and Dolphin in KDE, but I realized, I just don't use a file manager since I prefer the command line instead. I had a working ADB zsh completion script, but somehow forgot to back it up before my previous hard drive failure.
https://code.google.com/p/send-to-android/
this is interesting
So I have been reading quite a few threads here on XDA, and the one thing I noticed for noobs to linux/unix world is that they are struggling with some basic command once adb shell is gained. I decided to whip out this quick tutorial to help those noobs out to become more of an expert...like me...lol j/k
Here we go:
Prerequisites:
You must know how to invoke a adb shell command already to drop into your phone.
ALL commands in Unix/Linux are case sensitive
For more details, go to this ADB tutorial (very good one): http://forum.xda-developers.com/showthread.php?t=517874
Let's get going:
Once a shell is gained via adb, let's look at some of the basic commands you can do to navigate around the filesystem. Note: you must remove the double-quotes (") for the actual command.
Code:
"cd" = is change directory
to change to any directory, you type: cd dir_name (where dir_name is a full path)
Example: I want to go to /data/local/tmp in my phone, I would do
cd /data/local/tmp <hit ENTER>
You can also use the ".." to go UP one directory.
Example: I'm in /data/local/tmp and I want to go up to /data folder, a command would be: cd ../.. alternatively, if I do cd .. then i'll drop into /data/local folder instead.
Code:
"ls" = list files/directories
to list files/directories within a folder, the command should be:
ls <hit enter> => this will list all NON-HIDDEN file/directories within your CURRENT directory.
ls /data/local/tmp => this will list all NON-HIDDEN file/directories within /data/local/tmp directory.
ls -l => this will list all NON-HIDDEN file/directories within your CURRENT directory, plus additional details. Consider this is like a "Details" view in Windows Explorer.
ls -a => this will list all files/directories (including hidden files) within your CURRENT directory.
ls -la => this will list all files/directories (including hidden files) within your CURRENT directory, plus details.
Code:
"chmod" = change mode
Goes to wikipedia for more details: https://secure.wikimedia.org/wikipedia/en/wiki/Chmod
Most commonly used modes on android phones are:
"755" or "777".
So if you have a root.sh shell script that you downloaded from XDA, and uploaded to your phone and try to execute it with ./root.sh and it said "Permission denied". That means your script does not have the execute permission. You need to do:
chmod 755 root.sh <hit enter>
[B]IMPORTANT: There is *NO* negative sign (-) in front of the mode bit. So it is NOT chmod -755 root.sh[/B]
If you get a "File or directory not found" error, which means you are chmod-ing a file that doesn't exist in your current directory. To execute a chmod on root.sh in /data/local/tmp you do:
chmod 755 /data/local/tmp/root.sh
If you want to chmod an ENTIRE DIRECTORY and ALL files underneath it you do:
chmod -R 755 /data/local/tmp => this will set /data/local/tmp and ALL files/folders underneath it to be 755.
Code:
"chown" = change ownership
Go to wikipedia for details: https://secure.wikimedia.org/wikipedia/en/wiki/Chown
Most common used chown for android is: "root:root" or "root:shell"
Example: if you want to change ownership of root.sh to root:shell then you do:
chown root:shell root.sh
NOTE: the -R (recursive) option is also available for chown.
chown -R root:shell /data/local/tmp
Code:
"pwd" = print working directory
so when you are within a directory and you want to know which directory you are in, then you issue the command:
pwd <hit enter>
The system will reply back with the currently directory you are in.
I'll try to add more if I think of anything else useful, or if you have suggestions, please feel free to add.
so what does it mean to add adb to your path? thats holding me back from temp rooting on my mac. Im a total adb noob clearly.
hockey4life0099 said:
so what does it mean to add adb to your path? thats holding me back from temp rooting on my mac. Im a total adb noob clearly.
Click to expand...
Click to collapse
The easiest way to explain it is that you can run ADB from anywhere...do a search and you can find a more detailed (and more proper) explanation and directions on how to set it up.
hockey4life0099 said:
so what does it mean to add adb to your path? thats holding me back from temp rooting on my mac. Im a total adb noob clearly.
Click to expand...
Click to collapse
What OS are you using?
vboyz103 said:
What OS are you using?
Click to expand...
Click to collapse
mac
______________
hockey4life0099 said:
mac
______________
Click to expand...
Click to collapse
Like I said, do a search on XDA...there's a great guide on how to set up ADB properly. I'll link to it tomorrow when I get on the computer.
-- Sent from my 3VO Shooter --
hockey4life0099 said:
mac
______________
Click to expand...
Click to collapse
If you use mac, open a Terminal, and you should be at your home directory and type:
nano ~/.profile
if the .profile doesn't exist yet, then you'll see an empty.
Put this into the file
PATH=$PATH:/path/to/your/android/platform-tools
export PATH
save and exit out of Nano, and type:
source ~/.profile
then after this type adb and if adb is in your PATH then you see adb help.
Overview Of Permissions via ADB SHELL
Example = drwxrwxrwx
To Check Permission at anytime in ADB just Type:
ls -l
The First character defines the Directory, Link, Binary.
Below are some examples
Example = d---------
d = Directory
l = Link
b = Binary
The next 9 characters define the file permissions. These permissions are
given in groups of 3 each.
The first 3 characters are the permissions for the owner of the file or directory.
Example = -rwx------
The next 3 are permissions for the group that the file is owned by.
Example = ----rwx---
The final 3 characters define the access permissions for everyone not part of the group.
Example = -------rwx
There are 3 possible attributes that make up file access permissions.
r - Read permission. Whether the file may be read. In the case of a
directory, this would mean the ability to list the contents of the
directory.
w - Write permission. Whether the file may be written to or modified. For
a directory, this defines whether you can make any changes to the contents
of the directory. If write permission is not set then you will not be able
to delete, rename or create a file.
x - Execute permission. Whether the file may be executed. In the case of a
directory, this attribute decides whether you have permission to enter,
run a search through that directory or execute some program from that
directory
In addition to the file permission, you can also modify the owner and
group of the file. The chown program is used here and its syntax is very
simple. You need to be the owner of a file or root to do this.
Understanding Owner Permissions:
The first command is for owner ID, the Second Command is for Group ID.
exp. root.root ( First Root is owner, Second Root is Group ).
Chmod 644 some file, Like Build.prop For testing & then Veiw the Resulted Changes!
Refer to the table below as a quick reference.
Command Line for Both would look like this
chmod 644 build.prop = -rw-r--r--
\/
Chmod Guide
0 - ---
1 - --x
2 - -w-
3 - -wx
4 - r--
5 - r-x
6 - rw-
7 - rwx
SH Chown Guide
\/
chown root.root build.prop
root.root = Root
root.shell = Shell
Busybox SH Chown Guide
\/
chown 0.0 build.prop
0.0 = Root
0.2000 = Shell
I'll update the chmod with more with More Complex Commands Later
Side Note:Always set owner ( chown ) before Setting Permissions ( Chmod )!
Hope this Clears up things & is Helpful to everyone
~Eugene373
Add adb to your path in Windows.
As has been explained above all it does is allowing your adb to be called out from any location.
To set it in windows you will need to add path to your adb.exe file to your PATH in widows XP or CLASSPATH in windows7.
You can find it in start->contro panel->system->advanced.
There is a tab called "Inviromental Variables".
Click on that tab and new window will pop up. New window has 2 field in it. We are interested in bottom field called "System variables".
Windows XP user should look for line with variable "Path".
Click that line and choose edit below. New pop up will apear and you can edit path line in there. You should add path to your adb.exe to that line.
Example.
I did install windows sdk in c:\android\android-sdx-windows so my adb.exe file is in that folder. I did add path to that folder in "Paht" line of system variables. Add path to your adb.exe after semicolon.
;c:\Location\of folder\where you have\adb exe file\
Save changes, apply them. Now you can use call for adb commands from any location.
Widows 7 users.
Same changed need to be appied as for Windows XP.
There is only one difference that that path in Inviromental variables in windows7 is called "CLASSPATH".
Rest is same. Just add the path to folder containing your adb.exe file to CLASSPATH line and you would be able to use adb in any location.
Hope this make sense and will help.
My mac keeps sayin no device but I can access adb from anywhere basically its in my path but won't pick up my phone
Sent from my PG86100 using XDA Premium App
snoopy1e11 said:
My mac keeps sayin no device but I can access adb from anywhere basically its in my path but won't pick up my phone
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Make sure your phone is in debugging mode.
ADB won't see phone if debugging is not enabled.
It is on
Sent from my PG86100 using XDA Premium App
I'm a windows user.
Can't think of anything else.
Sorry.
agat63 said:
Make sure your phone is in debugging mode.
ADB won't see phone if debugging is not enabled.
Click to expand...
Click to collapse
If you have USB debugging turned on, you should see a triangle with exclamation mark on task bar. Secondly, try to do this:
adb kill-server => kill off current server first
then
sudo adb devices => u need to enter password
Basically, you are running adb with escalated privilege, sometimes it needs root access.
This is Wat I got
Sent from my PG86100 using XDA Premium App
snoopy1e11 said:
This is Wat I got
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
hmmm interesting...just wondering if you have your device turned on to be disk usage instead of just Charge Only?
Check on your desktop to see if you SD card had mounted, not sure if it makes a difference but worth a try. Another thought is that maybe your USB port doesn't work?? Did you check your phone to see if you have a triangle with exclamation mark in it on the task bar? (to the left)
Also, try it on a different computer if u can, and if it still doesn't work, afraid urs is defective.
I really appreciate ur help I re did the sudo command and hit "adb devices connect" and my device popped up
Sent from my PG86100 using XDA Premium App
snoopy1e11 said:
I really appreciate ur help I re did the sudo command and hit "adb devices connect" and my device popped up
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Ha, interesting cuz I never have to issue that command. Good to know you got it to work.
I am adding some mod files and tweaks to an android 2.3.3 image. It is a Livesuit flashable image for the Alpha 2 Skypad. I use unimg.exe to extract the files then fileaddsum and unimg to repack the file under Windows.
I mount the extracted image in Linux Mint then make my changes. I have tried different tricks people have suggested to set the permissions of the file, but whenever I umount and repack the img, it will install, but I have to go into adb and chmod the files. I have written a simple command file so it only take a second, but being new to Linux I am not finding any way to set the permission when I copy over the files to the mounted image.
Any suggestions/ Thanks in advance.
bump..........................................
re-bump .............................................
Not sure if this will help, but in unix permissions are set with chmod. so to ad the exicutable permission you enter:
Code:
su
chmod a+x filename
exit
However if youve had suggestions on setting permissions, you must already know this?
matts95 said:
Not sure if this will help, but in unix permissions are set with chmod. so to ad the exicutable permission you enter:
Code:
su
chmod a+x filename
exit
However if youve had suggestions on setting permissions, you must already know this?
Click to expand...
Click to collapse
That wasn't working for me. But I found a cheat, I guess you could say. Once the image was open I would pull the files from the emulator or a pad directly to the image+folder. Not elegant but it worked.
[Guide][ARM now supported] Android development/debugging on ChromeOS - ADB & fastboot
What you need to know before we begin:
ChromeOS (Or Chromium OS if you installed it on a non-chromebook) is based on Unix, and you can access a terminal with button combinations. This part of the guide is easy, but if I can get apt-get working, that's where it gets really complex.
What you'll need
A computer running ChromeOS/Chromium OS
An internet connection on it, or the files on a USB drive (and you to copy them to Downloads)
A little Linux knowledge
Some patience
1.) Download the correct files for system:
ChromeOS/ChromiumOS on an x86 based PC
ChromeOS on an ARM based PC
2.) When the zip has downloaded, extract it so both the adb and fastboot files are in the Downloads folder
3.) It's now time to access the terminal mode. It might be a good idea to get this guide on a phone or some other device so you don't have to switch out at any time.
If you're using a chromebook or an official chromeOS build, you need to access developer mode. Note: this will wipe all your data for security reasons. Full info is here: Chromium Project: Developer mode
4.) Press Ctrl-Alt-F2 on your keyboard, and the whole screen will be a terminal. Read the info at the top, and then login
NOTE: If you're using Chromium OS vanilla builds, the username and password are as follows:
Code:
User: chronos
Pass: facepunch
5.) You now have a localhost terminal, with no root permissions.
6.) Run this code, to locate the location of your Downloads folder:
Code:
ls /home
7.) Mount the filesystem as follows:
Code:
mount -o remount,rw /
8.) Using the name other than "root" and "user", run these commands:
Code:
cp /home/<name>/user/Downloads/adb /sbin/adb
For example, the Chromium one would be:
Code:
cp /home/chronos/user/Downloads/adb /sbin/adb
Repeat for Fastboot (replace "adb" with "fastboot" without the quotes)
9.) Test that it has worked by running:
Code:
adb
It should result in adb working
10.) You're done, adb and fastboot should work. You might need to reboot in some cases for it to work fully
11.) For more stuff, like Java and ant, wait a while until I work out how to get apt-get installed from dpkg
Credits:
Thanks to KMyers for compiling Fastboot for ARM devices, thread here
Reserved
And again
Once more, just in case
Whenever I go to check my path I get this response:
"cat: /usr/local/bin:/usr/bin:/bin:/opt/bin:/home/chronos/user/Downloads/android-sdk-linux/platform-tools: no such file or directory"
Help?
awacker89 said:
Whenever I go to check my path I get this response:
"cat: /usr/local/bin:/usr/bin:/bin:/opt/bin:/home/chronos/user/Downloads/android-sdk-linux/platform-tools: no such file or directory"
Help?
Click to expand...
Click to collapse
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Quinny899 said:
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Click to expand...
Click to collapse
And so it seems! Now it appears that any adb command returns a "Permission denied" message. Ideas?
Update: Same response for fastboot commands.
awacker89 said:
And so it seems! Now it appears that any adb command returns a "Permission denied" message. Ideas?
Update: Same response for fastboot commands.
Click to expand...
Click to collapse
Try this:
Code:
cd /home/chronos/user/Downloads/android-sdk-linux/platform-tools
chmod 755 adb
chmod 755 fastboot
Then exit back to the login screen on the terminal, login again and try running adb
Quinny899 said:
Try this:
Code:
cd /home/chronos/user/Downloads/android-sdk-linux/platform-tools
chmod 755 adb
chmod 755 fastboot
Then exit back to the login screen on the terminal, login again and try running adb
Click to expand...
Click to collapse
Still no dice
I'm starting to lose hope. I just keep getting "permission denied."
I thought maybe trying this would do the trick but still no response.
Code:
sudo ./adb devices
[code]
P.S. Guess I should mention that running just adb returns command not found, so I've been using ./adb. Maybe I just don't know what the hell I'm doing but I just can't get it to work.
Hmmm. Well, The SDKx86 (87mb) that were in the instructions so, I downloaded the ADT (399mb) instead, just a hint.
Is there a specific branch that is required to be on in chromeos in order for terminal to act correctly? I never get any chance to login once i get into the "crosh" terminal.
Quinny899 said:
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Click to expand...
Click to collapse
Instead of doing
Code:
cat $PATH
you should do
Code:
echo $PATH
The cat command is trying to concatenate a file with the name of your full path, which obviously doesn't exist. echo tells you the value of the $PATH variable, which is what you're actually trying to do.
I was trying to get this to work on my Chromebook Samsung Series 5 550
Furst thing I noticed was the absence of an f2 key - tried a usb keyboard no joy
I assume what I am trying to launch is Shell which can only be accessed with a Chrome OS device in developer mode. I really want to get this working so I will try activating developer mode and report back.
Update:
So Developer Mode resets and wipes your device (doh!) back to Step 1
Update 2: (Dev Mode activated function key labelled as "->" works as f2 and launches shell successfully"
Has anyone got this working? I noticed that the folder coming out of the SDK zip is called "sdk" but all the commands listed in the guide use "android-sdk-linux"
I used "sdk" and just get the Permission Denied issue even after chmod on adb
Will this work on the Samsung Series 3 with the ARM processor?
imtoomuch said:
Will this work on the Samsung Series 3 with the ARM processor?
Click to expand...
Click to collapse
Supposedly pulling the adb binary from an android device (/system/bin/adb) and using that would work. Don't know about fastboot though
Sent from my Galaxy Nexus using Tapatalk 4 Beta
jambamkin said:
I was trying to get this to work on my Chromebook Samsung Series 5 550
Furst thing I noticed was the absence of an f2 key - tried a usb keyboard no joy
I assume what I am trying to launch is Shell which can only be accessed with a Chrome OS device in developer mode. I really want to get this working so I will try activating developer mode and report back.
Update:
So Developer Mode resets and wipes your device (doh!) back to Step 1
Update 2: (Dev Mode activated function key labelled as "->" works as f2 and launches shell successfully"
Has anyone got this working? I noticed that the folder coming out of the SDK zip is called "sdk" but all the commands listed in the guide use "android-sdk-linux"
I used "sdk" and just get the Permission Denied issue even after chmod on adb
Click to expand...
Click to collapse
I had the same problems. And just stopped trying about 2 days of trying to figure it out.
I was able to find a version of adb compiled for ARM but it was from an older version which made it a no go on my Nexus 4 (4.2.2 requires updated adb to work with the new security enhancements built in).
I tried it on my Series 5 550 chromebook. Can't seem to get it to work.
I do all the commands and it shows up in echo $PATH but then when i try adb anything it says permission denied. I do the chmod 755 and still permission denied.
i tried to exit back to the login and then the folder wasn't in the echo path anymore. adb not working either. I tried rebooting chromebook and it wasnt there either.
Would it be cheating to get it running with crouton? Because I did get that done.
Sent from my NookColor using xda premium
yeah i've been having the same issue with my samsung 5 series chromebook. "permission denied" and all that. But on the fun side, i learned if you want to really make your chromebook bug-out; type cat adb whilst in /platform-tools.
Background:
I have an App that needs to read files generated by a process outside of its control. These files end up in a folder on the device and they have permissions set so that the App is not allowed to open these files.
The device is rooted and I have access to these files via adb shell and here I can simply do a chmod and the app can read the files. Problem is that these files are generated now and then when the App is running so it is not practical or possible to do the chmod via adb shell. The App needs to be able to operate without being plugged in to adb shell.
So what have I tried so far:
*Searched the internet for answers, YES but no luck
*Searched XDA, Stack Overflow etc YES but no luck
*I have chown the App.apk in /data/app to be root:root and to have the same uid and group id as the files I'm trying to open and read. I have also changed the App userId in /data/system/packages.xml to root.
In all these cases the app is started with its default user id if I check it with ps and the files cannot be opened. Yes I made sure the App was actually off/killed before starting it again after changing these things.
*In java I have tried p = Runtime.getRuntime().exec("sudo chmod 777 /thefolder/*"); but I get IOException same for swapping to "su…" or "sudo su…" Leaving out the superuser returns ok but doesn't do anything to the files in thefolder.
The preferred solution is that this is done in code in either Java or in JNI/C but some sort of one off magic via adb that stays there when device is power cycled is also ok.
Anyone has any good ideas or hints on how these files can be read?
Thanks in advance!