Help creating AVD - Android Q&A, Help & Troubleshooting

I'm looking to create an AVD for the HTC One M8.
Code:
./android create avd -n HTC -t [Which ID do I use?] --abi [Which ABI do I use?]
From:
Code:
id: 1 or "android-19"
Name: Android 4.4.2
Type: Platform
API level: 19
Revision: 4
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : default/armeabi-v7a, default/x86
----------
id: 3 or "android-21"
Name: Android 5.0
Type: Platform
API level: 21
Revision: 1
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : android-tv/armeabi-v7a, android-tv/x86, default/armeabi-v7a, default/x86, default/x86_64
----------
id: 4 or "Google Inc.:Google APIs:19"
Name: Google APIs
Type: Add-On
Vendor: Google Inc.
Revision: 9
Description: Android + Google APIs
Based on Android 4.4.2 (API level 19)
Libraries:
* com.android.future.usb.accessory (usb.jar)
API for USB Accessories
* com.google.android.media.effects (effects.jar)
Collection of video effects
* com.google.android.maps (maps.jar)
API for Google Maps
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : default/armeabi-v7a, google_apis/armeabi-v7a, google_apis/x86, google_apis/x86_64
Thank you in advance!!!
Also, how do I create a custom hardware profile?
When trying to do so, I get prompted with:
Code:
Name of the AVD being run:
avd.name [<build>]:
I input my build name and it just keeps asking.
Thoughts?

Related

Nook Tablet root for Linux (updated 11/25/12)

This guide is for getting your tablet rooted from Linux. It is similar to the guides made by Indirect and t-r-i-c-k for Windows and OS X respectively.
Get ADB working
If you are running a 64 bit system then you will need to have the 32 bit ncurses library installed.
For Arch Linux:
Code:
sudo pacman -S lib32-ncurses
For Ubuntu (can someone check this?):
Code:
sudo apt-get install lib32ncurses5
Now you will need the Android SDK. you can get it from http://developer.android.com/sdk/index.html
Extract the downloaded SDK to a location of your choice. This will give you an android-sdk-linux directory.
Now we need to install the platform tools. Run the android-sdk-linux/tools/android program and install at least the "Android SDK Platform-tools"
Optionally, you can install the Nook Tablet/Color SDKs.
Choose Tools->Manage Addon Sites
Click the "New..." button and add http://su.barnesandnoble.com/nook/sdk/addon.xml
Also add http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Now install the Nook Color and/or Nook Tablet SDKs.
You will have to manually edit or create the ~/.android/adb_usb.ini file. Make sure it contains the following line:
Code:
0x2080
Now we need to set up the udev rules for your Nook. These instructions work for Arch Linux, let me know if they don't work for your distribution.
create an /etc/udev/rules.d/51-android.rules file and populate it with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_fastboot"
run the following commands:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
$ sudo udevadm control --reload-rules
reference:
https://wiki.archlinux.org/index.php/Android
Enable USB debugging on your Nook
Open up your web browser on your Nook and go to http://comptonsoft.com/test and Download AppMenu.
reference: http://forum.xda-developers.com/showpost.php?p=19421107&postcount=18
After the download completes, open the AppMenu.apk from the notification area (tap on the lower left corner of the nook screen where the three down arrows are)
Choose "Package Installer", when it says "Install blocked" choose "Settings"
Check off "Unknown Sources" and then choose "Development"
Check off both "USB debugging" options and uncheck "Auto Mount"
Bring up the notification window and tap on the AppMenu.apk and install with package installer. This time it should work.
If you ever need to get back to the appmenu you can now access it from the search screen (make sure to show all results). Sometimes the thing likes to reset it's debugging abilities.
Perform a temporary root
Now the fun begins. Let's get the rootkit. Download the zergrush binary from http://forum.xda-developers.com/showthread.php?t=1296916
Extract the zergRush file from the zip and remember where you put it. I put mine in ~/Downloads
Adjust the following instructions according to your location:
Plug in your nook, you should get a beetle icon in the notification area.
Open up a terminal on your computer and change to the android-sdk-linux/platform-tools directory, and do the following commands:
Code:
$ cd ~/android-sdk-linux/platform-tools
$ ./adb kill-server
$ ./adb start-server
$ ./adb push ~/Downloads/zergRush /data/local/
$ ./adb shell
We are now in the nook.
Code:
$ chmod 755 /data/local/zergRush
$ /data/local/zergRush
zerg does it's thing and if all goes well, says it's restarting as root and kicks us out of adb
Code:
$ ./adb remount
It should say "remount succeeded" if the root worked.
Install su to make the root permanent
In order for the root to persist after a reboot we need to install superuser. Get it from http://androidsu.com/superuser/
Make sure to get the gingerbread version. Extract the contents of the zip somewhere, say ~/Downloads/superuser/ and do the following:
Code:
$ ./adb push ~/Downloads/superuser/system/bin/su /system/bin
$ ./adb push ~/Downloads/superuser/system/app/Superuser.apk /system/app
$ ./adb shell
# chmod 6755 /system/bin/su
# ln -s /system/bin/su /system/xbin/su
# chmod 644 /system/app/Superuser.apk
# exit
Install google apps
Of course we are gonna want to get access to the market and what not.
Get google apps from http://goo-inside.me/gapps
Extract somewhere, say ~/Downloads/gapps and do the following:
Code:
$ rm ~/Downloads/gapps/system/app/SetupWizard.apk
$ ./adb push ~/Downloads/gapps/system /system
$ ./adb shell
# chmod 644 /system/app/*
# chmod 644 /system/lib/libvoicesearch.so
# chmod 644 /system/etc/permissions/*
# chmod 644 /system/framework/*
# exit
$ ./adb remount
$ ./adb reboot
When the nook comes up again, choose search, tap the g in the upper left, choose apps, type in market. Choose to add an account, create/sign in.
I had to back out of the market in go back in again a couple times to get the "agree to license screen". If the market just sits there loading for a while, try that.
You can run any apps you install any time by searching for them.
Some tips for getting the most out of your tablet:
I suggest installing a launcher from the market. I use zeam. I think launcher pro and adw launcher are both popular choices also. These will allow you launch apps directly, instead of searching for them.
The Homecatcher app seems to be getting a good reception I haven't had a chance to try it yet, but i plan on it. It allows you to use a different launcher than barnes and noble's by default
Install busybox from here. You'll need to have an sd-card in your tablet for the install to work, but don't need it afterwords (just throw the one from your phone in or something if you don't have one).
To get adbd running as root (to do things like remount or push to system folder) you can run zergRush again as in the temporary root step. I had to su, and then run zergRush, and adb seems a little flakey and kicked me out from time to time when i did it, but it worked. ADB root goes away every time you reboot still.
Happy trails.
Worked great
I'm a noob to both linux and android and your directions worked like a charm, Thanks so much.
flawless
absolutely flawless instructions. thank you!
Works good but now I can't "adb remount" because I get an "operation not permitted", and thus I can't "adb push".
Is this normal behavior after this root?
The only reason I noticed was from attempting to install the newer talk app which is probably possible by other means but I haven't found the right answer out of about a billion search results.
Also the part about installing the color sdk stuff or adding the adb_usb.ini line isn't accurate I don't think. I had to run "android update adb" and then the file was updated, which is the same as editing the file but I think it gets autocreated or updated from something else possibly.
firephoto said:
Works good but now I can't "adb remount" because I get an "operation not permitted", and thus I can't "adb push".
Is this normal behavior after this root?
Click to expand...
Click to collapse
Yeah... :-(
You'll have to su and remount by hand. The following should work:
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# exit
$ exit
$ adb push teh_files
Sadly after you reboot the adb deamon doesn't have superuser permissions anymore and can't do things like remounting filesystems.
I'm not sure why this is tbh. maybe because the SUID bit isn't set, or the version of adb in the tablet is gutted?
I'm sure people would be grateful if someone figured it out (hint hint), it's gonna cause all kinds of annoyances like this in the future no doubt :-/
firephoto said:
Also the part about installing the color sdk stuff or adding the adb_usb.ini line isn't accurate I don't think. I had to run "android update adb" and then the file was updated, which is the same as editing the file but I think it gets autocreated or updated from something else possibly.
Click to expand...
Click to collapse
Weird. It definitely wasn't on my system after installing tablet sdk and before installing the color sdk and definitely was after installing the color sdk. i'll change the original post to get rid of that part, since it's kind of unnecessary anyhow.
There's something that seems more locked down (while allowing root) so maybe it's intentional to maintain some security in certain situations. (guessing).
I did mount the filesystem rw but that still doesn't allow the push. Seem like the standard adb shell user doesn't have the permissions to do the normal things and then the root user doesn't have the commands even though the $PATH is correct.
So some permission bit set strange somewhere I guess but I haven't found it yet.
Oh wow, you are right. And it gets even better...
You can push to the /mnt/media/ directory...
And now for the good news...no cp command, and mv doesn't work to move files apparently.
As a temporary work around you can use cat >< I feel so dirty saying this:
Code:
$ adb push teh_file /mnt/media
$ adb shell
$ su
# cat /mnt/media/teh_file > /system/teh_file
Things are getting really hackey now :-/ maybe i will have to look into the adbd issues after all. Not tonight though.
I'll update the guide tomorrow to get busybox installed so we have a cp command. The market app didn't work for me, but I don't have an sd card in mine atm, and i think it wants to download there.
Anyone with an sd card able to just install the (stericson) busybox market app?
I did some research on adbd. Apparently by default it runs as a "shell" user, not root.
This is pretty standard for stock roms apparently. There are a few ways around this.
For more information, see this thread
Honestly, I forgot the step to remove zergRush from /data/local, so the easiest thing in my opinion would be to just run zergRush whenever you need adb running as root.
Also, busybox from the market installs just fine with an sd-card, doesn't have to be a good one or anything, it just needs a place to park the busybox binary that it is copying over
Great work. Was thinking about writing one once I got an NT but knew someone would beat me to it. FYI you can follow link in my signature to install adb in Ubuntu. Will try this as soon as I get my hand on one (next week). Thank you
Sent from my NookColor using xda premium
I used the first half of these instructions to get sideloading working on my non-rooted NT 1.4.1. Windows messed everything up by installing the "correct" drivers automatically and adb wouldn't recognize the NT so had to flip to Linux. Thanks!
Sent from my BNTV250 using Tapatalk
I get the following error after it begins installing the SDK Platform-tools: Stopping ADB server failed (code -1). Is this normal?
This is a clean install of the Android SDK.
Thanks!
Code:
Fetching https://dl-ssl.google.com/android/repository/addons_list-1.xml
Validate XML
Parse XML
Fetched Add-ons List successfully
Fetching URL: https://dl-ssl.google.com/android/repository/repository-5.xml
Validate XML: https://dl-ssl.google.com/android/repository/repository-5.xml
Parse XML: https://dl-ssl.google.com/android/repository/repository-5.xml
Found SDK Platform Android 1.1, API 2, revision 1 (Obsolete)
Found SDK Platform Android 1.5, API 3, revision 4
Found SDK Platform Android 1.6, API 4, revision 3
Found SDK Platform Android 2.0, API 5, revision 1 (Obsolete)
Found SDK Platform Android 2.0.1, API 6, revision 1 (Obsolete)
Found SDK Platform Android 2.1, API 7, revision 3
Found SDK Platform Android 2.2, API 8, revision 3
Found SDK Platform Android 2.3.1, API 9, revision 2 (Obsolete)
Found SDK Platform Android 2.3.3, API 10, revision 2
Found SDK Platform Android 3.0, API 11, revision 2
Found SDK Platform Android 3.1, API 12, revision 3
Found SDK Platform Android 3.2, API 13, revision 1
Found SDK Platform Android 4.0, API 14, revision 3
Found SDK Platform Android 4.0.3, API 15, revision 1
Found ARM EABI v7a System Image, Android API 14, revision 2
Found ARM EABI v7a System Image, Android API 15, revision 1
Found Samples for SDK API 7, revision 1
Found Samples for SDK API 8, revision 1
Found Samples for SDK API 9, revision 1 (Obsolete)
Found Samples for SDK API 10, revision 1
Found Samples for SDK API 11, revision 1
Found Samples for SDK API 12, revision 1
Found Samples for SDK API 13, revision 1
Found Samples for SDK API 14, revision 2
Found Samples for SDK API 15, revision 1
Found Android SDK Platform-tools, revision 10
Found Android SDK Tools, revision 16
Found Documentation for Android SDK, API 15, revision 1
Found Sources for Android SDK, API 14, revision 1
Found Sources for Android SDK, API 15, revision 1
Found Android Support package, revision 6
Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
Parse XML: https://dl-ssl.google.com/android/repository/addon.xml
Found Google APIs by Google Inc., Android API 3, revision 3
Found Google APIs by Google Inc., Android API 4, revision 2
Found Google APIs by Google Inc., Android API 5, revision 1 (Obsolete)
Found Google APIs by Google Inc., Android API 6, revision 1 (Obsolete)
Found Google APIs by Google Inc., Android API 7, revision 1
Found Google APIs by Google Inc., Android API 8, revision 2
Found Google APIs by Google Inc., Android API 9, revision 2 (Obsolete)
Found Google APIs by Google Inc., Android API 10, revision 2
Found Google APIs by Google Inc., Android API 11, revision 1
Found Google APIs by Google Inc., Android API 12, revision 1
Found Google APIs by Google Inc., Android API 13, revision 1
Found Google APIs by Google Inc., Android API 14, revision 2
Found Google TV Addon by Google Inc., Android API 12, revision 2
Found Google APIs by Google Inc., Android API 15, revision 1
Found Google Market Licensing package, revision 1
Found Google USB Driver package, revision 4
Found Google Market Billing package, revision 1
Found Google Admob Ads Sdk package, revision 4
Found Google Analytics Sdk package, revision 2
Found Google Webdriver package, revision 2
Fetching URL: http://www.echobykyocera.com/download/echo_repository.xml
Validate XML: http://www.echobykyocera.com/download/echo_repository.xml
Parse XML: http://www.echobykyocera.com/download/echo_repository.xml
Found Dual Screen APIs by KYOCERA Corporation, Android API 8, revision 1
Found Dual Screen APIs by KYOCERA Corporation, Android API 10, revision 1
Fetching URL: http://developer.lgmobile.com/sdk/android/repository.xml
Validate XML: http://developer.lgmobile.com/sdk/android/repository.xml
Parse XML: http://developer.lgmobile.com/sdk/android/repository.xml
Found Real3D by LGE, Android API 10, revision 1
Found Real3D by LGE, Android API 8, revision 1
Fetching URL: http://innovator.samsungmobile.com/android/repository/repository.xml
Validate XML: http://innovator.samsungmobile.com/android/repository/repository.xml
Parse XML: http://innovator.samsungmobile.com/android/repository/repository.xml
Found GALAXY Tab by Samsung Electronics., Android API 8, revision 1
Fetching URL: http://developer.sonyericsson.com/edk/android/repository.xml
Validate XML: http://developer.sonyericsson.com/edk/android/repository.xml
Parse XML: http://developer.sonyericsson.com/edk/android/repository.xml
Found EDK 1.2 by Sony Ericsson Mobile Communications AB, Android API 10, revision 1
Fetching URL: http://su.barnesandnoble.com/nook/sdk/addon.xml
Validate XML: http://su.barnesandnoble.com/nook/sdk/addon.xml
Parse XML: http://su.barnesandnoble.com/nook/sdk/addon.xml
Found NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Fetching URL: http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Validate XML: http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Parse XML: http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Found NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Done loading packages.
Preparing to install archives
Downloading Android SDK Platform-tools, revision 10
Installing Android SDK Platform-tools, revision 10
Stopping ADB server failed (code -1).
Installed Android SDK Platform-tools, revision 10
Downloading SDK Platform Android 2.3.3, API 10, revision 2
Installing SDK Platform Android 2.3.3, API 10, revision 2
Installed SDK Platform Android 2.3.3, API 10, revision 2
Downloading SDK Platform Android 2.2, API 8, revision 3
Installing SDK Platform Android 2.2, API 8, revision 3
Installed SDK Platform Android 2.2, API 8, revision 3
Downloading Samples for SDK API 10, revision 1
Installing Samples for SDK API 10, revision 1
Installed Samples for SDK API 10, revision 1
Downloading Samples for SDK API 8, revision 1
Installing Samples for SDK API 8, revision 1
Installed Samples for SDK API 8, revision 1
Downloading Android Support package, revision 6
Installing Android Support package, revision 6
Installed Android Support package, revision 6
Downloading NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Installing NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Installed NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Downloading Google APIs by Google Inc., Android API 10, revision 2
Installing Google APIs by Google Inc., Android API 10, revision 2
Installed Google APIs by Google Inc., Android API 10, revision 2
Downloading NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Installing NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Installed NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Downloading Google APIs by Google Inc., Android API 8, revision 2
Installing Google APIs by Google Inc., Android API 8, revision 2
Installed Google APIs by Google Inc., Android API 8, revision 2
Updated ADB to support the USB devices declared in the SDK add-ons.
Stopping ADB server succeeded.
Starting ADB server succeeded.
Done. 10 packages installed.
Done loading packages.
Did it work? Can adb see the NT? Can you root? The error may not be normal, but it doesn't really matter unless something doesn't work...
Sent from my Desire HD using Tapatalk
winsettr said:
Did it work? Can adb see the NT? Can you root? The error may not be normal, but it doesn't really matter unless something doesn't work...
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Running openSUSE 12.1
I've tried different USB ports but something isn't right:
Code:
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb kill-server
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb push zergRush /data/local
error: insufficient permissions for device
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb devicesList of devices attached
???????????? no permissions
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb shell
error: insufficient permissions for device
*******@arena:~/programs/android-sdk-linux/platform-tools>
*******@arena:~/programs/android-sdk-linux/platform-tools> ls -l /etc/udev/51-android.rules
-rw-r--r-- 1 root root 234 Jan 2 18:12 /etc/udev/51-android.rules
*******@arena:~/programs/android-sdk-linux/platform-tools>
I have even tried running this with SUDO and as ROOT but then I'm am presented with an empty "List of devices attached" after running "./adb devices" command. I have also rebooted my Linux system and the Nook Tablet but no change.
You shouldn't need special permission to push ZergRush (how else could you get it on the NT to root) so that's a problem. When you stop then start the adb daemon, then list devices (before trying to push ZergRush), is the NT listed?
Sent from my Desire HD using Tapatalk
RegLinUsr said:
...
I have even tried running this with SUDO and as ROOT but then I'm am presented with an empty "List of devices attached" after running "./adb devices" command. I have also rebooted my Linux system and the Nook Tablet but no change.
Click to expand...
Click to collapse
winsettr said:
You shouldn't need special permission to push ZergRush (how else could you get it on the NT to root) so that's a problem. When you stop then start the adb daemon, then list devices (before trying to push ZergRush), is the NT listed?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Your question is easily answered with the information from the end of my post...
Fully reading a post before replying is quite the useful trait. It helps to notice that this is not my first time rooting something as well so the obvious isn't the issue here, the problem is something else that is a bit off of the beaten path. Might be something openSUSE specific; missing driver or program but I'm not sure at this point.
Stil remount will not work for me?
ylixir said:
Yeah... :-(
You'll have to su and remount by hand. The following should work:
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# exit
$ exit
$ adb push teh_files
Here's my commands:
$ su
su
reloc_library[1311]: 2959 cannot locate '_ZNK7android6Parcel15setDataPositionEj
'...
CANNOT LINK EXECUTABLE
$ su
mount -o rw,remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
Click to expand...
Click to collapse
Works!
Thank you! tried on the mac and had issues with device not being found. This worked perfect, thanks again for the guide!
Ren
I don't see any option to "Manage add-on sites" in the ADK Manager (the "android" app). Where are you getting this from?
Nevermind, I understand it now.

[Q] MTP installation on debian doesn't work

Hello,
I've compiled the latest version of libmtp (1.1.2) and installed properly. It seems that the device is recognized but still without the ability to connect to it. Here is the log. I got two different outputs. So I'll post both of them:
1.
Code:
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 12
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
2.
Code:
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 13
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
I've read about a samsung-proprietary mtp protocol which would not work with libmtp. I hope those rumors are wrong, aren't they?
I'd really appreciate any help. I've been working on it for a couple of days and it starts really anoying me.
regards, hornby
I have the same issue. I am trying to connect my Linux Mint Debian machine to my SGS2 running CM9 nightly. Debian can see the device but communication is a nogo.
Here is mtp-detect:
Code:
~ $ mtp-detect
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 9
Attempting to connect device(s)
ignoring usb_claim_interface = -110Android device detected, assigning default bug flags
USB low-level info:
Using kernel interface "usbfs"
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 04e8
idProduct: 6860
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 1
Device number: 9
Device entry info:
Vendor: Samsung
Vendor id: 0x04e8
Product: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus
Vendor id: 0x6860
Device flags: 0x08008106
Device info:
Manufacturer: samsung
Model: GT-I9100
Device version: 1.0
Serial number: ????????
Vendor extension ID: 0x00000006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1006: Get number of objects
1007: Get object handles
1008: Get object info
1009: Get object
100a: Get thumbnail
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1017: Reset device property value
101b: Get partial object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9810: Get object references
9811: Set object references
95c1: Unknown (95c1)
95c2: Unknown (95c2)
95c3: Unknown (95c3)
95c4: Unknown (95c4)
95c5: Unknown (95c5)
Events supported:
0x4002
0x4003
0x4004
0x4005
Device Properties Supported:
0xd401: Synchronization Partner
0xd402: Friendly Device Name
0x5003: Image Size
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
3001: Association/Directory
3004: Text
3005: HTML
3008: MS Wave
3009: MP3
300b: MPEG
3801: JPEG
3802: TIFF EP
3807: GIF
3808: JFIF
380b: PNG
380d: TIFF
b901: WMA
b902: OGG
b903: AAC
b982: MP4
b983: MP2
b984: 3GP
ba05: Abstract Audio Video Playlist
ba10: WPL Playlist
ba11: M3U Playlist
ba14: PLS Playlist
ba82: XMLDocument
b906: FLAC
Storage Devices:
StorageID: 0x00010001
StorageType: 0x0003 fixed RAM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0000 read/write
MaxCapacity: 12332314624
FreeSpaceInBytes: 6137163776
FreeSpaceInObjects: 1073741824
StorageDescription: Internal Storage
VolumeIdentifier: (null)
Special directories:
Default music folder: 0x0000001a
Default playlist folder: 0xffffffff
Default picture folder: 0x0000001f
Default video folder: 0xffffffff
Default organizer folder: 0xffffffff
Default zencast folder: 0xffffffff
Default album folder: 0xffffffff
Default text folder: 0xffffffff
MTP-specific device properties:
Friendly name: (NULL)
Synchronization partner: (NULL)
libmtp supported (playable) filetypes:
Folder
Text file
HTML file
RIFF WAVE file
ISO MPEG-1 Audio Layer 3
MPEG video stream
JPEG file
GIF bitmap file
JFIF file
Portable Network Graphics
TIFF bitmap file
Microsoft Windows Media Audio
Ogg container format
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
ISO MPEG-1 Audio Layer 2
Abstract Playlist file
XML file
Free Lossless Audio Codec (FLAC)
ERROR: Could not close session!
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
OK.

No Google Play . Missing Acrobat

Hi,
Google Play does not work for me on the latest Remix_OS_for_PC_Android_M_64bit_B2016082301.iso.
Having done the Play Activation update + Play Activation + Reboot, both Play and new Account protest about not being able to contact Google Servers, even though: 1.Internet connectivity is definitely present and 2. In Apps for Google Play and Google Play Services there is no cache to empty (a suggested remedy in other threads.)
The system is below (minus the touchscreen which was unplugged at the time of running the report).
Incidentally I am running remix via a grub entry:
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/install.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x$
initrd /remix/initrd.img
Remix works beautifully apart from this Play and Acrobat hiccup.
Best wishes
System: Host: localhost.localdomain Kernel: 4.6.2-1-MANJARO x86_64 (64 bit gcc: 6.1.1)
Desktop: Xfce 4.12.3 (Gtk 2.24.30) info: xfce4-panel dm: lightdm
Distro: Manjaro Linux
Machine: Mobo: ASRock model: Z87 Extreme4
Bios: American Megatrends v: P3.40 date: 04/12/2016
CPU: Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13604
clock speeds: min/max: 800/3400 MHz 1: 3400 MHz 2: 3399 MHz
3: 3401 MHz 4: 3399 MHz
Memory: Using dmidecode: you must be root to run dmidecode
Graphics: Card: Advanced Micro Devices [AMD/ATI] Turks XT [Radeon HD 6670/7670]
bus-ID: 01:00.0 chip-ID: 1002:6758
Display Server: X.Org 1.17.4 driver: fglrx
Resolution: [email protected]
GLX Renderer: AMD Radeon HD 6670
GLX Version: 4.5.13399 - CPC 15.201.1151 Direct Rendering: Yes
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:8c20
Card-2 Advanced Micro Devices [AMD/ATI] Turks/Whistler HDMI Audio [Radeon HD 6000 Series]
driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 1002:aa90
Sound: Advanced Linux Sound Architecture v: k4.6.2-1-MANJARO
Network: Card: Intel Ethernet Connection I217-V
driver: e1000e v: 3.2.6-k port: f040
bus-ID: 00:19.0 chip-ID: 8086:153b
IF: enp0s25 state: up speed: 1000 Mbps duplex: full
mac: bc:5f:f4:c7:97:ee
WAN IP: 202.67.36.243
IF: enp0s25 ip-v4: 192.168.1.100 ip-v6: fe80::97f8:3170:7a5a:8f77
Drives: HDD Total Size: 3120.6GB (90.1% used)
ID-1: /dev/sda model: Corsair_Force_GT size: 120.0GB serial: 12147901000015020820
ID-2: /dev/sdb model: WDC_WD30EZRX size: 3000.6GB serial: WD-WMC1T2484449
Optical: /dev/sr0 model: TSST CDDVDW SH-224DB
rev: SB00 dev-links: cdrom
Features: speed: 48x multisession: yes
audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition: ID-1: / size: 39G used: 36G (95%) fs: ext4 dev: /dev/sda3
label: ROOT uuid: c550c05c-bfa9-4d19-ba16-0f6459eb7e93
ID-2: /boot size: 190M used: 42M (23%) fs: ext2 dev: /dev/sda1
label: BOOT uuid: 84060996-08ed-41da-be5c-e0c15a12544e
ID-3: /home size: 71G used: 63G (94%) fs: ext4 dev: /dev/sda4
label: HOME uuid: 56ca1278-38ec-43a7-a83e-7a247242efa7
ID-4: /media/esata/MEDIA size: 1.8T used: 1.7T (96%) fs: ext4 dev: /dev/sdb2
label: MEDIA uuid: f6232cfa-6daa-4d48-a378-9dde17c525f9
ID-5: /media/esata/SYSTEM size: 917G used: 863G (100%) fs: ext4 dev: /dev/sdb1
label: SYSTEM uuid: be0b8822-6339-4051-bbcf-021beb1cf6ff
ID-6: swap-1 size: 1.05GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
label: N/A uuid: cba5f6b8-ebd1-4350-85ae-6c2c844b2538
RAID: No RAID data: /proc/mdstat missing-is md_mod kernel module loaded?
Unmounted: No unmounted partitions detected
Sensors: System Temperatures: cpu: 44.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Weather: Conditions: F ( C) Wind: Calm
Pressure: in ( mb) Location: Altitude: ft
Time: August 27, 3:07 PM Observation Time: ,
Info: Processes: 287 Uptime: 1:30 Memory: 3230.4/7918.3MB
Init: systemd v: 231 Gcc sys: 6.1.1
Client: Shell (bash 4.3.421 running in xfce4-terminal) inxi: 2.3.0
Add a SERIAL=random to your grub.
HypoTurtle said:
Add a SERIAL=random to your grub.
Click to expand...
Click to collapse
Thanks.
I added that to the end of the kernel line. It seemed to have an effect in that when booting up because the optimize app process was displayed. I can't remember seeing that before.
However there was no change to the "can't contact google servers" when trying to create a gmail account.
I did another Activate Google Play and rebooted but still no change.
The Acrobat problem has gone away so I'll edit that out.
Two more problems were noticed.
1. When trying to print as PDF there was a "SAVE as PDF Jide" error.
2.Inability to access EXT4 drives.
Hi,
The "SERIAL=random" needs to be behind "quiet"
*after edit hit "enter" then "b" to boot
If done correctly /setting/tabled/status/serial
Will show a serial number...
About pdf... just try a different app
Goodluck
Hi, this is the modified grub entry:
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/install.img
linux /remix/kernel quiet SERIAL=random root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}
I reinstalled RemixOS, went through the activation and reboot, and still Play "can't contact Google servers".

Android Emulator Does not Start in Android Studio

I have installed Android Studio version 2.3.3 on Windows 7 64-bit Enterprise.
Using the AVD Manager, I created a new device.
Issue: When I start the Android Virtual Device, a screen flashes and disappears. Based on some suggestions online, I read that we need to modify the Graphics settings of the Virtual Device however I don't get the option to modify these settings.
Below are the settings of the Android Device I have created:
Nexus 5X (5.2 1080x1920 xxhdpi)
Nougat (Android 7.0 x86)
Emulated Performance (Graphics -> Automatic)
Device: Enable Device Frame (checked)
Camera: Front and Back (Emulated)
Network Speed: Full and Latency: None
RAM: 1536 MB
VM Heap: 256 MB
Internal Storage: 800 MB
Keyboard: Enable Keyboard Input.
And here is the output of the command: avdmanager.bat list avd
Available Android Virtual Devices:
Name: username
Device: Nexus 5X (Google)
Path: C:\Users\username\.android\avd\username.avd
Target: Google Play (Google Inc.)
Based on: Android 7.0 (Nougat) Tag/ABI: google_apis_playstore/x86
Skin: nexus_5x
Sdcard: C:\Users\username\.android\avd\username.avd\sdcard.img

Troubleshooting an X Server

Hello,
I'm trying to run an X server on my tablet, but it does not launch. The X binaries and libraries are from a 32-bit CentOS ROM I downloaded (Mirror list: http://isoredirect.centos.org/altarch/7/isos/armhfp/); I have the contents of the ROM in /data/local with symlinks to parts of it (e.g. /lib). Componenets of GNU Coreutils like Bash, among others work just fine, so I do not believe any parts of the CentOS ROM are causing problems. Running startx through an ADB shell might not work, so I've been looking for a way to run it on the tablet's screen without success.
More info:
Model: Samsung Galaxy Tab A 10.1 2019 (SM-T510)
ROM: Nexus Stock Android 11
Version of X: 1.20.4
Root status: Rooted
CPU Architecture: armv8l
Code:
Error Message:
expr: Unexpected extra input '/dev/pts/0'
xauth: file //.serverauth.8071 does not exist
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: 4.19.52-300.el7.armv7hl+lpae
Current Operating System: Linux localhost 4.4.177 #2 SMP PREEMPT Fri Mar 12 17:13:34 PST 2021 armv8l
Kernel command line: console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 rcupdate.rcu_expedited=1 androidboot.debug_level=0x4f4c androidboot.force_upload=0x0 androidboot.upload_offset=6880000 softdog.soft_margin=100 softdog.soft_panic=1 androidboot.dram_info=FF,04,10,2G sec_debug.chipidfail_cnt=0 sec_debug.lpitimeout_cnt=0 sec_debug.cache_err_cnt=0 sec_debug.codediff_cnt=0 sec_debug.pcb_offset=7343872 sec_debug.smd_offset=7344896 sec_debug.lpddr4_size=2 sec_debug.sjl=1 androidboot.muic_1k=0 androidboot.sn.param.offset=7342000 androidboot.prototype.param.offset=7345920 androidboot.recovery_offset=7347968 androidboot.fmm_lock=48 sec_debug.fmm_lock_offset=7340680 ess_setup=0x91200000 [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] s3cfb.bootloaderfb=0xec000000 lcdtype=8550668 androidboot.carrierid.param.offset=7340608 androidboot.carrierid= consoleblank=0 vmalloc=384m sec_debug.reset_reason=5 sec_reset.reset_reason=5 ehci_hcd.park=3 oops=panic pmic_info=91 ccic_info=1 fg_reset=0 androidboot.emmc_checksum=3 androidboot.sales.param.offset=7340572 sales_code=XAC androidboot.odin_download=1 androidboot.bootloader=T510XXU4BUA1 androidboot.selinux=enforcing androidboot.ucs_mode=0 [email protected] androidboot.revision=4 androidboot.hardware=exynos7904 androidboot.warranty_bit=1 androidboot.wb.hs=0e03 androidboot.wb.snapQB=CUSTOM sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=R52MA16Z2JK androidboot.ap_serial=0x45B7CD5ABEDC snd_soc_core.pmdown_time=1000 androidboot.cp_reserved_mem=off skip_initramfs rootwait ro init=/init root=/dev/mmcblk0p25 androidboot.dtbo_idx=1 androidboot.em.did=45b7cd5abedc androidboot.em.model=SM-T510 androidboot.em.status=0x0 root=PARTUUID=52444E41-494F-2044-7379-7374656D0000 androidboot.verifiedbootstate=orange androidboot.svb.ver=SVB1.0 bcm_setup=0xffffff80f8e00000 reserve-fimc=0xffffff80fa000000 firmware_class.path=/vendor/firmware ecd_setup=disable factory_mode=0 androidboot.ulcnt=5 androidboot.lassen.apfuse=8 epx_activate=true kpti=n androidboot.cpefs_wp=1
Build Date: 01 April 2020 09:37:40AM
Build ID: xorg-x11-server 1.20.4-10.el7
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 4 04:48:11 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Categories

Resources