Kill stats from 5.1 ROM - Android One (First-Generation) Cross-Device Genera

Folks,
just out of curiosity. Can someone with the Android One running LP 5.1 give me the output of the following:
Code:
adb logcat -v time -d | grep Killing | head -1
adb logcat -v time -d | grep Killing | tail -1
adb logcat -v time -d | grep Killing | wc -l
adb shell free
adb shell ps | wc -l
This is what those 5 lines are doing:
1. get the first low-memory-killer daemon's "Killing" message
2. get the last LMKD "Killing" message
3. get the count of LMKD "Killing" messages.
4. list free memory
5. count of all processes in the system
I am just curious about how LMKD has changed in 5.1 and if indeed google has fixed issues with RAM management in 5.1.
Thanks for your help.

C'mon guys... One of you. Please...

devsk said:
C'mon guys... One of you. Please...
Click to expand...
Click to collapse
i didnt have tested this rom but after official ota, will try

Someone has the stats I am looking for. Is it you? Post them then....

here is it.
devsk said:
C'mon guys... One of you. Please...
Click to expand...
Click to collapse
1)'grep' is not recognized as an internal or external command,
operable program or batch file.
2)same as above
3)same as above
4)/system/bin/sh: free: not found
5)'wc' is not recognized as an internal or external command,
operable program or batch file.

anojan__10 said:
1)'grep' is not recognized as an internal or external command,
operable program or batch file.
2)same as above
3)same as above
4)/system/bin/sh: free: not found
5)'wc' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Ah...Windows... I assumed that at least someone here will have Linux running on their PC.
On Windows, you either need to run these commands inside cygwin (unix like) shell or run the commands on the phone (Terminal app) without 'adb' in front e.g. "logcat -v time -d | grep Killing | head -1".
If you decide to run on the phone, you 1. may need to install the busybox app, 2. output of the commands will need to be concatenated in one file on /sdcard and then, 'adb pull' on PC to a local file and attach that file.

Related

System Dump

Has anybody made a system dump of the nook color?
mattpall said:
Has anybody made a system dump of the nook color?
Click to expand...
Click to collapse
Yes, dumps have been made.
pokey9000 said:
Yes, dumps have been made.
Click to expand...
Click to collapse
I don't see where any dumps have been made, not with the commands listed anyway. It doesn't actually say they've dumped them...just lists commands that will do it?
I tried using various commands and can't seem to get it to dump.
gormly said:
I don't see where any dumps have been made, not with the commands listed anyway. It doesn't actually say they've dumped them...just lists commands that will do it?
I tried using various commands and can't seem to get it to dump.
Click to expand...
Click to collapse
I can't get it to work with the those commands. I get a "...mmcblk0 not a file or directory."
I'm getting the same "remote object... ...not a file or directory" thing too. Does this have to be done from a non-windows machine?
I can see the files I am trying to pull in a file manager, just not having any luck pulling them over adb.
I was able to perform the dump in linux.
F8
I was also able to pull (from linux) but the real question is has anyone verified the resulting images? I mean, it's not really a backup until you've done a successful restore with it.
I guess I don't know the quirks of "adb pull" well enough yet to give it the same trust as say, a "dd" generated image...
Well, be it what we need or not, I pulled it on OSX. What I am wondering now is why it doesn't seem to be working on windows (at least on my Win7 x64).
To pull and read the whole disk under Ubuntu, first make sure you have package kpartx installed.
-pull the image
Code:
$ adb pull /dev/block/mmcblk0 nook_emmc.img
1701 KB/s (-645922816 bytes in 2094.821s)
-mount loopback and map it to partitions
Code:
$ sudo losetup /dev/loop0 nook_emmc.img
$ sudo kpartx -av /dev/loop0
add map loop0p1 (252:0): 0 144522 linear /dev/loop0 63
add map loop0p2 (252:1): 0 144585 linear /dev/loop0 144585
add map loop0p3 (252:2): 0 610470 linear /dev/loop0 289170
add map loop0p4 (252:3): 0 14121135 linear /dev/loop0 899640
add map loop0p5 (252:4): 0 931707 252:3 63
add map loop0p6 (252:5): 0 1959867 252:3 931833
add map loop0p7 (252:6): 0 722862 252:3 2891763
add map loop0p8 (252:7): 0 10506447 252:3 3614688
-partitions are now in /dev/mapper. Mount a filesystem:
Code:
$ sudo mount /dev/mapper/loop0p5 /mnt
$ ls /mnt
app build.prop fonts lib media usr
bin etc framework lost+found recovery-from-boot.p
-when done, you have to unmount all mountpoints, release the partition map, and undo the loopback device:
Code:
$ sudo umount /mnt
$ sudo kpartx -d /dev/loop0
$ sudo losetup -d /dev/loop0
You can actually dd within the Nook firmware. I dd'ed all the partitions to /media and then pulled them over via adb.
Also, there's a full factory backup sitting in a zip file on partition 3. I mounted it temporarily and grabbed it.
http://forum.xda-developers.com/showpost.php?p=9536709&postcount=3

Bionic Webtop Chromium (Chrome) Browser

This thread is now obsolete!
Use this thread to do way more!!!
THIS COULD BREAK EVERYTHING IN THE WORLD AND SCREW UP YOUR LIFE FOREVER!!!! YOUR PHONE COULD BE BRICKED!!! YOUR WIFE COULD LEAVE YOU AND YOUR PARENTS COULD DIE!!! DO THIS AT YOUR OWN RISK!!! MAKE SURE TO HAVE A COPY OF THE FASTBOOT FILES FOR THE BIONIC JUST IN CASE!!!
I got Chromium Browser to run on the Webtop. It's a little messy (have to open it through a terminal emulator) but it works. I borrowed heavily from Sogarth who made this thread.
Made it a little easier.
Unzip and place the webtopchromium folder on the root of /sdcard-ext
webtopchromium.zip
If you are plugged into a computer make sure to change USB Mode to charge only before you proceed.
Use a terminal emulator or adb to run these commands:
Code:
su
/usr/bin/sudo -H -u root bash
cd /mnt/sdcard-ext/webtopchromium
sh webtopchromium.sh
This may take 10 minutes or so...
When it is finished reboot...
Use a terminal emulator or adb to run these commands:
Code:
su
/usr/bin/sudo -H -u root bash
cd /mnt/sdcard-ext/webtopchromium
sh installdeb.sh
Now when inside webtop open a terminal emulator in the phone window and run:
Code:
su
/usr/bin/sudo -H -u adas bash
export DISPLAY=:0
chromium-browser
You can just run the installdeb.sh (much faster) if you don't want to backup webtop with rsync. You can always use the fast boot to fix either way.
**Thanks to tallnerd for suggesting the faster method**
**A huge thanks to Sogarth for discovering all this first for the Atrix**
reserved
To uninstall and revert back to the stock webtop:
Using adb with root access:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cd /system/bin
mv mountosh mountosh.new
mv mountosh.orig mountosh
cd /data
rm ubuntu.disk
Reboot
I tried this, but it broke my Xperia Play. The micro HDMI cable I bought also broke the micro USB port on my phone.
v1r7u41 said:
THIS COULD BREAK EVERYTHING IN THE WORLD AND SCREW UP YOUR LIFE FOREVER!!!! YOUR PHONE COULD BE BRICKED!!! YOUR WIFE COULD LEAVE YOU AND YOUR PARENTS COULD DIE!!! DO THIS AT YOUR OWN RISK!!! MAKE SURE TO HAVE A COPY OF THE FASTBOOT FILES FOR THE BIONIC JUST IN CASE!!!
I got Chromium Browser to run on the Webtop. It's a little messy (have to open it through a terminal emulator) but it works. I borrowed heavily from Sogarth who made this thread.
Get a copy of these debs and put them on your sdcard-ext.
chromium-browser
Dependencies
Make sure to unzip the debs.zip and copy the .deb files and the mountosh.new to the sdcard-ext.
Use adb or android terminal-emulator.
Now check to make sure you have at least 1G free:
Code:
/bin/df -h /data
There should be at least 1.0G under the Used column. If not, you won't have enough to create a decent disk. If so, then you can keep going:
Code:
su
/usr/bin/sudo -H -u root bash
mount -o rw,remount /dev/block/mmcblk0p12 /system
/bin/dd if=/dev/zero of=/data/ubuntu.disk bs=1024 count=1048576
/sbin/losetup /dev/block/loop7 /data/ubuntu.disk
/sbin/mkfs -t ext3 -m 1 -b 2048 /dev/block/loop7
mkdir /tmp/osh
/bin/mount -t ext3 /dev/block/loop7 /tmp/osh
At this point, we've created a 1 GB disk file (1,024×1,024=1,048,576), formatted it as ext3, and mounted it in /tmp/osh.
I'll assume that rsync is in /mnt/sdcard-ext:
Code:
mkdir /tmp/deb
/usr/bin/dpkg-deb -x /mnt/sdcard-ext/rsync* /tmp/deb
/tmp/deb/usr/bin/rsync -avx /osh/ /tmp/osh/
And now we have a duplicate of our /osh partition.
After that:
Code:
mv /system/bin/mountosh /system/bin/mountosh.orig
cp /mnt/sdcard-ext/mountosh.new /system/bin/mountosh
chmod 0755 /system/bin/mountosh
chown 0 /system/bin/mountosh
chgrp 2000 /system/bin/mountosh
You can now reboot your device, and you should now boot into the new partition we've just created.
Now Install the debs.
Code:
su
/usr/bin/sudo -H -u root bash
touch /osh/var/lib/dpkg/status
touch /osh/var/lib/dpkg/available
mkdir /osh/var/lib/dpkg/updates
dpkg -i --force-all --root=/osh /sdcard-ext/chromium*
dpkg -i --force-all --root=/osh /sdcard-ext/libxss*
dpkg -i --force-all --root=/osh /sdcard-ext/lzma*
You will get some errors from dpkg but just ignore them. Moto broke dpkg's way of telling what is already installed.
Now to run chromium you will need to start webtop like you usually do
then open a terminal-emulator in the phone window and type this
Code:
su
/usr/bin/sudo -H -u adas bash
export DISPLAY=:0
chromium-browser
Click to expand...
Click to collapse
You should make a chromium icon/app that will run that last command when you click it
Yeah. I definitely need to clean this up, but I just wanted to get things moving .
I'm anxious to try this. I'll gladly be the third person to do it, but I don't want to be the second. Someone with more experience than I give it a try.
updated to make it a little easier
Posting this from Chrome on Webtop. It is noticeably faster than Firefox. Like butta!
Thank you so much for putting this together!
Maybe I'm missing something here but when running the script/install all goes well til the very last line, when I enter the "chromium-browser" command it states bash: chromium-browser not found. Can someone give me an idea of what I'm missing or doing wrong here please
Check your /sdcard-ext/webtopchromium folder before you run the installdeb.sh and make sure these are there:
chromium-browser-inspector_12.0.742.112~r90304-0ubuntu0.10.10.1_all.deb
chromium-codecs-ffmpeg_10.0.648.205~r81283-0ubuntu0.10.10.1_armel.deb
chromium-browser_10.0.648.205~r81283-0ubuntu0.10.10.1_armel.deb
libxss1_1%3a1.2.0-2_armel.deb
lzma_4.43-14ubuntu2_armel.deb
If chromium-browser_10.0.648.205~r81283-0ubuntu0.10.10.1_armel.deb isn't there run:
Code:
cd /sdcard-ext/webtopchromium
/tmp/deb/usr/bin/wget https://answers.launchpad.net/~ubuntu-security-proposed/+archive/ppa/+build/2443315/+files/chromium-browser_10.0.648.205%7Er81283-0ubuntu0.10.10.1_armel.deb
Well this sucks, I did a full wipe/nandroid restore and now that it's done I go to download the files and they're not there. Can anyone re-upload the files for me please?
Why, oh why did Moto not use Chrome? It is faster and I have not had a single low memory warning while using Chrome. In fact, I have yet to have it register over 3% in memory manager. Thanks again V1r7.
I'll setup a host for the files soon. Check back later (im away from computer) tonight.
Sent from my DROID BIONIC using XDA App
Got the file off of my computer, still running into issues though. Verified that all of the correct files are there and installed/uninstalled a few times just to verify. Quick question are you guys running the webtop adaptor or the lapdock? I'm running on the lapdock and wondering if this would make any difference at all if you're using the webtop.
I'm using the lapdock. Sorry I don't know enough to help you out. I'm rooted and followed the instructions and it worked.
Goto your terminal and type
busybox find /osh/usr/bin -name chrom*
Let me know what you find.
Sent from my DROID BIONIC using XDA App
When I type those commands it does absolutely nothing, just goes on to the next terminal line the same as the last.
try:
busybox find /sdcard-ext/webtopchromium/ -name chrom*
v1r7u41 said:
try:
busybox find /sdcard-ext/webtopchromium/ -name chrom*
Click to expand...
Click to collapse
When I type that it comes up with these results:
/sdcard-ext/webtopchromium/chromium-browser-inspector_12.0.742.112-r90304-0ubuntu0.10.10.1_all.deb
/sdcard-ext/webtopchromium/chromium-codecs-ffmpeg_10.0.648.205-r81283-0ubuntu0.10.10.1_armel.deb
/sdcard-ext/webtopchromium/chromium-browser_10.0.648.205-r81283-0ubuntu0.10.10.1_armel.deb
/sdcard-ext/webtopchromium/chromium-browser_10.0.648.205-r81283-0ubuntu0.10.10.1_armel.deb.1
/sdcard-ext/webtopchromium/chromium-browser_10.0.648.205-r81283-0ubuntu0.10.10.1_armel.deb.2
Open terminal:
su
/usr/bin/sudo -H -u root bash
cd /sdcard-ext/webtopchromium
dpkg -i --force-all --root=/osh chrom*
exit
/usr/bin/sudo -H -u adas bash
export DISPLAY:0
chromium-browser

restoring erased data

i installed wishnu app https://play.google.com/store/apps/details?id=edu.phystech.wishnu&feature=search_resultand tried to run it but it doesnt work , then i remove the app by go to applications manager>wishnu then clear data and uninstall
after that all my data is gone i dont know how
sdcard and internal card but my app doesnt erased
how can i fix or restore my data and files ?
plz help :crying:
Try to reboot and check once.
or use undelete from the playstore
Hi,
with dd command you can extract an image of your sdcard or over & after use data recovery forensics tool (foremost).
ex: dd (try 'mount' for identify block before)
Code:
#dd if=/dev/<blockdevice> of=/extract_image bs=4096
# foremost -t all -i extract_image
or with app but i have no experimented any app
manually is the best way & sure
nokiamodeln91 said:
Try to reboot and check once.
or use undelete from the playstore
Click to expand...
Click to collapse
thanx
but it doesnt work
karamelos said:
Hi,
with dd command you can extract an image of your sdcard or over & after use data recovery forensics tool (foremost).
ex: dd (try 'mount' for identify block before)
Code:
#dd if=/dev/<blockdevice> of=/extract_image bs=4096
# foremost -t all -i extract_image
or with app but i have no experimented any app
manually is the best way & sure
Click to expand...
Click to collapse
can you explain more
i am linux user i can use terminal
but android terminal i dont know how it work
tsar007 said:
can you explain more
i am linux user i can use terminal
but android terminal i dont know how it work
Click to expand...
Click to collapse
Yes of course and with pleasure
It's not android terminal command.
On your Linux (for exemple ubuntu) laptop open terminal:
Code:
$sudo apt-get install foremost
mount your phone on your pc & list disk (mass storage simply way)
Code:
#fdisk -l
or with mount command
Your sdcard for this example named: sdb
Copier sdb with dd command & nane it extract_image. option bs=4096 it's block size & maximizing execution speed significantly.
more option in man (root)
Code:
#dd if=/dev/sdb of=/extract_image bs=4096
Foremost extract (root):
Code:
#foremost -t all -i extract_image
-t - specify file type/ here "all" but you can specifies jpg mp4 pdf etc....
-i - specify input file/ your backup
Foremost create folder but you must be root for open it (/temp directory is good work spaces)
or (not good but simply)
Code:
gksudo nautilus
Enjoy
karamelos said:
Yes of course and with pleasure
It's not android terminal command.
On your Linux (for exemple ubuntu) laptop open terminal:
Code:
$sudo apt-get install foremost
mount your phone on your pc & list disk (mass storage simply way)
Code:
#fdisk -l
or with mount command
Your sdcard for this example named: sdb
Copier sdb with dd command & nane it extract_image. option bs=4096 it's block size & maximizing execution speed significantly.
more option in man (root)
Code:
#dd if=/dev/sdb of=/extract_image bs=4096
Foremost extract (root):
Code:
#foremost -t all -i extract_image
-t - specify file type/ here "all" but you can specifies jpg mp4 pdf etc....
-i - specify input file/ your backup
Foremost create folder but you must be root for open it (/temp directory is good work spaces)
or (not good but simply)
Code:
gksudo nautilus
Enjoy
Click to expand...
Click to collapse
i did execute this
Code:
dd if=/dev/sdc of=/extract_image bs=4096
this is the output
Code:
2904064+0 records in
2904064+0 records out
11895046144 bytes (12 GB) copied, 635.841 s, 18.7 MB/s
then i same directory i did execute this
Code:
foremost -t all -i extract_image
and this is the output
Code:
Processing: stdin
i wait for more than 3 hours and same thing ,nothing happened
look
there is another application "photorec"
in terminal i did execute
Code:
photorec
its look like a guide
after it done i opened the directory and i found folders i opened one and there is txt files and zip files and tar files
i didnt know how i used it
tsar007 said:
Code:
foremost -t all -i extract_image
Click to expand...
Click to collapse
This's a basique commande try with other option
first command Generate audit file and print to the screen, the seconde extract with verbose
Code:
$sudo foremost -avT extract_image
$sudo foremost -vT -t all -i extract_image
-a write all headers
-v Verbose
-T delete the output dir when you running multiple times
For photorec:
A good wiki & site
After using photorec
karamelos said:
This's a basique commande try with other option
first command Generate audit file and print to the screen, the seconde extract with verbose
Code:
$sudo foremost -avT extract_image
$sudo foremost -vT -t all -i extract_image
-a write all headers
-v Verbose
-T delete the output dir when you running multiple times
For photorec:
A good wiki & site
After using photorec
Click to expand...
Click to collapse
thanx a lot :laugh:
For future
Foremost is a great tool simply & faster but photorec detect more files & just read partitions
For sdcard (photos, PDF...) foremost enough
Sent from my GT-N7000 using xda app-developers app

[Q] [help] loss of thouch screen!

hi folks!
last night i had Curiosity Rom, after that i flashed Avatar Rom but i didnt like it and i decided to go back to Curiosity but after booting my touch screen did not respond and it didnt work.
here is what i did to fix it:
* did full wipe
* flash avatar rom again
* flash curiosity rom again
* restore my old back up (before loosing touch screen)
* flashed official rom via flash tools
but i still dont have touch screen!
how can i fix it?
Xperia T LP30
please use search
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+firmware
gregbradley said:
please use search
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+firmware
Click to expand...
Click to collapse
thanks for reply
ive seen that thread before but actually i didnt understand it. can explain more? what should i do exactly?
connect phone to pc and open up a command window.
then type the code from this post
http://forum.xda-developers.com/showpost.php?p=39920703&postcount=11
gregbradley said:
connect phone to pc and open up a command window.
then type the code from this post
http://forum.xda-developers.com/showpost.php?p=39920703&postcount=11
Click to expand...
Click to collapse
is it important where to open command window?
here is what i got:
C:\>C:\Android>adb devices
Access is denied.
C:\>List of devices attached
'List' is not recognized as an internal or external command,
operable program or batch file.
C:\>CB5121SC7S device
'CB5121SC7S' is not recognized as an internal or external command,
operable program or batch file.
C:\>
C:\>
C:\>C:\Android>adb shell
Access is denied.
C:\>[email protected]:/ $ su
'[email protected]:' is not recognized as an internal or external command,
operable program or batch file.
C:\>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\>[email protected]:/ # rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.
img
'[email protected]:' is not recognized as an internal or external command,
operable program or batch file.
C:\>-d /sys/bus/rmi4/devices/sensor00 -r -f
'-d' is not recognized as an internal or external command,
operable program or batch file.
C:\>rmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f
<
The syntax of the command is incorrect.
C:\>[email protected]:/ # reboot
'[email protected]:' is not recognized as an internal or external command,
operable program or batch file.
C:\>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\>
C:\>C:\Android>
whats wrong?
Have you set up adb on your machine?
If not, then extract the folder "Android" from the attached .zip and put it into the C drive so you have this folder structure
C:\Android
Then right click in that folder whist holding the shift key and choose
open command window here.
Then type the code.
https://dl.dropboxusercontent.com/u/24614808/adb_fastboot_and_other_tools.zip
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
The only bit you type are
Code:
C:\Android>adb devices
Code:
C:\Android>adb shell
Code:
[email protected]:/ $ su
Code:
[email protected]:/ # rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img
-d /sys/bus/rmi4/devices/sensor00 -r -f
Code:
[email protected]:/ # reboot
The rest is what the window will return with after pressing enter at the end of each line
gregbradley said:
Have you set up adb on your machine?
If not, then extract the folder "Android" from the attached .zip and put it into the C drive so you have this folder structure
C:\Android
Then right click in that folder whist holding the shift key and choose
open command window here.
Then type the code.
https://dl.dropboxusercontent.com/u/24614808/adb_fastboot_and_other_tools.zip
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
The only bit you type are
Code:
C:\Android>adb devices
Code:
C:\Android>adb shell
Code:
[email protected]:/ $ su
Code:
[email protected]:/ # rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img
-d /sys/bus/rmi4/devices/sensor00 -r -f
Code:
[email protected]:/ # reboot
The rest is what the window will return with after pressing enter at the end of each line
Click to expand...
Click to collapse
so i should type them step by step.
how should i connect the phone? fastboot, flashmode or what?
kamiar1 said:
so i should type them step by step.
how should i connect the phone? fastboot, flashmode or what?
Click to expand...
Click to collapse
yes,one by one and click return
just connect the phone with usb cable
gregbradley said:
yes,one by one and click return
just connect the phone with usb cable
Click to expand...
Click to collapse
is this ok?
C:\Android>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
have you set up the adb correctly?
Follow this
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Or just search google with this
setting up adb on windows
while doing all these stuff, i was downloading stock ics rom, i flashed it via flash tools and now the touch screen works!!!:victory:
any way thank you gregbradley for your help.:good::highfive::fingers-crossed:
no problem.
You should be able to flash your JB backup now.
Also, follow the advice in the thread I linked to that renamed the touch firmware so that it wont happen again.

Need help to install Android studio

Hello all,
It's been 4 days I'm trying to install Android studio on my 12.04 linux box. I'm desparate with this. I must have loaded all web pages in the world on this problem so far and still not able to have this to work properly.
The errors I get is :
Unable to locate adb within SDK
Error running app: Unable to obtain debug bridge
My system is 32 bit and I reverted to the previous platform-tools.
If I do this:
[email protected]:~/android-sdk-linux/android-sdk-linux/platform-tools/platform-tools$ sudo adb devices
I get this:
List of devices attached
09630e71021fbc89 device
I really don't know what to do. If someone could help I would greatly appreciate.
Thanks,
Marc.
Type in a terminal env | grep -i android
and let us see .
edward.snowden said:
Type in a terminal env | grep -i android
and let us see .
Click to expand...
Click to collapse
Hello, this is what I get.......
[email protected]:~$ env | grep -i android
ANDROID_EMULATOR_FORCE_32BIT=true
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/marc/android-sdk-linux/android-sdk-linux/tools:/home/marc/android-sdk-linux/android-sdk-linux/platform-tools:/home/marc/android-sdk-linux/android-sdk-linux/tools:/home/marc/android-sdk-linux/android-sdk-linux/platform-tools:/home/marc/android-sdk-linux/android-sdk-linux/tools:/home/marc/android-sdk-linux/android-sdk-linux/platform-tools
[email protected]:~$
soltel.ca said:
Hello, this is what I get.......
[email protected]:~$ env | grep -i android
ANDROID_EMULATOR_FORCE_32BIT=true
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/marc/android-sdk-linux/android-sdk-linux/tools:/home/marc/android-sdk-linux/android-sdk-linux/platform-tools:/home/marc/android-sdk-linux/android-sdk-linux/tools:/home/marc/android-sdk-linux/android-sdk-linux/platform-tools:/home/marc/android-sdk-linux/android-sdk-linux/tools:/home/marc/android-sdk-linux/android-sdk-linux/platform-tools
[email protected]:~$
Click to expand...
Click to collapse
Hello, Anyone who can solve this?

Categories

Resources