SDK: Weird problem w/ GPU acceleration on aptosid and nVidia - Android Q&A, Help & Troubleshooting

Hi!
I just installed the Android SDK to run ICS. For the moment, it's just for a workshop on WebDAV, but later, I'd like to start developing, so guess this is relevant to this place ^^
Well, I followed the guides closely, but I was unable to get anything running at first, but at least, I can run software mode now. It's horribly slow, though, which is why I'd like to describe the symptoms.
- They are the same for any combination of version, resolution and hardware I tried.
- When I start emulator -avd <>, it just sits there as emulator-arm for half an hour and eats all my CPU.
- When I kill -SIGTERM the emulator-arm, it won't react.
- When I close the xterm governing the emulator, its window displays for a brief second.
- When I kill -SIGKILL the emulator-arm, it exit and leaves garbage in /tmp. (Normal, I guess.)
- When I run emulator-arm -avd <>, it boots and tells me
Code:
emulator: ERROR: Could not load OpenGLES emulation library: libOpenglRender.so: cannot open shared object file: No such file or directory
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
- As software mode is extremely slow, I tried copying libOpenglRenderer.so to /usr/lib/android-sdk, putting that into /etc/ld.so.conf, and running ldconfig. When I do that, emulator-arm displays the same symptoms as emulator.
What's happening?
I'm running a recent aptosid (Debian Unstable + patches), and I tried installing both nVidia's DKMS drivers and doing it manually by getting the .run package. No difference. Also, it does not seem to mean anything if I run with or without Compositing. (Tried KDE+Kwin, KDE+Compiz and Fluxbox.)
Also, I should mention that I was able to start the emulator binary ONCE. I have no idea what happened there, as I did not do anything differently. I had just set up a new AVD and started it as usual.
Is there some kind of log I could check out? Or anything else?
Thanks!
David

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Thanks ✟
Moving to Q&A

Related

[Linux] Ubuntu 9.10 on nike

kaiser ubuntu port based on zubuntu by Omegamoon for Sharp Zaurus was successfully launched on HTC Nike!
Instructions:
1. download kernel
http://84.23.71.227/kerneloftheday/zImageUbuntu
2. download ubuntu basefiles and rootfs
3. place ubuntu.img, haret, initrd.gz and zImageUbuntu to Storage Card/ubuntu/
4. place this default.txt there too
Code:
set RAMADDR 0x10000000
set MTYPE 1724
set KERNEL zImageUbuntu
set initrd initrd.gz
set cmdline "pm.sleep_mode=1 mddi.width=320 mddi.height=480 lcd.density=160 board-htcnike-keypad.keypadlayout=1 board-htcnike-keypad.sticky_timer_time_ms=350 no_console_suspend"
boot
5. change board-htcnike-keypad.keypadlayout=1 to 0 if you have 20key nike.
6. run haret and press "Run", ubuntu & kernel will be loaded to login prompt, login with username root and no password, you will get root shell.
7. write
Code:
export TSLIB_TSDEVICE=/dev/input/event0
ts_calibrate
and calibrate your screen.
8. write startx and see LXDE running on your nike! you've got real linux box in pocket!
Note, rootfs for ubuntu needs 1GB of free space on your sdcard!
For now, you cannot work with screen, we have some difference from kaiser panel's, i.e. ubuntu gui is completely unusable, this thread were started to find out why.
based on this thread from kaiser forum.
Credits: dzo, Omegamoon, domy007, mblaster and guys from Rhodubuntu thread.
I dont get any response when i try to calibrate screen on niki 200
thats strange, it must work.
I will debug on touchscreen problems, but ubuntu running and that is great, now we have only input-devices problems, and this is more better than nothing.
Sounds great, but wouldn't it be better to try something smaller like puppylinux or Feather linux ?
zubuntu is only we have compiled for ARM and working with our hardware that starts X and tested on other htc's devices.
rzk333 said:
zubuntu is only we have compiled for ARM and working with our hardware that starts X and tested on other htc's devices.
Click to expand...
Click to collapse
Ok thanks for the information, did some reading before and was always wondering why they use ubuntu but this answer set things straight.
Greetz,
Great to see a full linux distro around for htc devices. I will fix the '_' tomorrow... Any other missing characters?
How is the speed of ubuntu? Is it very sluggish or usable?
'=' character maybe, for export line.
zImageUbuntu is updated (your link is still valid).
'=' and '-'are on '*'-button, '_' is Alt-
I have included the msm_fb_refresh and the keypad changes into my auto-updated-kernel, so you should be able to use the fresh kernels from my thread with ubuntu if you want recent updates (zImageUbuntu is not automatically updated).
got some progress,
1) msm refresh thread seems to disable sleep mode in android, thread polls framebuffer many times in second and drains battery.
2) linux logo on bootup must be disabled - logo gets over ts_calibrate's first crosshair point.
2) still trying to make touchscreen and tslib friends - i2c bus debug messages logs saying that touchscreen is connected and recieves data correctly.
found some data:
/dev/input/event0 - htcnike-kbd
/dev/input/event1 - htcnike-ts
but still no data from touchscreen...
rzk333 said:
got some progress,
1) msm refresh thread seems to disable sleep mode in android, thread polls framebuffer many times in second and drains battery.
2) linux logo on bootup must be disabled - logo gets over ts_calibrate's first crosshair point.
2) still trying to make touchscreen and tslib friends - i2c bus debug messages logs saying that touchscreen is connected and recieves data correctly.
found some data:
/dev/input/event0 - htcnike-kbd
/dev/input/event1 - htcnike-ts
but still no data from touchscreen...
Click to expand...
Click to collapse
Disabled msm refresh thread from the android kernels again. The kernel you linked in your first post is now automatically updated with anything new in the repository. Bootlogo is disabled, too. Good luck with tslib, let me know if when you need something else to be hacked into the kernel.
mblaster
I've just test the usb ether function in the zImage from the post
showthread.php?p=6675397
and it works just fine.
(Just when I had managed to make adbd works... but ssh is more reliable)
Thanks gTan64.
wow, that is good, now I can dump system state without hours of keyboard typing
I've managed to get internet by usb (cdc only) thanks to gTan64: just apply the patch from is post ("Debian on the vogue"), you can extract it from the download links.
And the TOUCHSCREEN WORK!!!!!!!
But you need to compile tslib from the tslib git (github.com/kergoth/tslib.git), the one in the rootfs from this post doesn't work.
Will make a more complete post later, I think.
Bye.
Ubuntu always shows me a black screen when I try to startup it!
What can I do make it work?
omg, I knew that something is wrong with tslib in this rootfs!
thanks for r&d, if you will make some packages & mans, I'll add them to first post.
Maybe you can upload some pics ?
But you need to compile tslib from the tslib git
Click to expand...
Click to collapse
I tried to compile - but no luck, autoconf fails to make configure...
I also uploaded debian rootfs and posted links in gTan's Debian on Vogue thread.
nothing happened last month?

The HP Touchpad Sticky Master Thread

This is some of the info that I have put together and I figured it may help some of you also. Let me know if I need to add anything. Looking forward to working with this device. Hopefully the Devs will take an interest in it also. With these hardware specs I feel like they will. Anyway, carry on............
Dev/Config/Soft/Tools
CyanogenMod team Touchpad port
HP Site
SDK - Multiple Platforms Instructions
Command line tools
Java - WIndows 32 and 64 Bit Instructions
****Note - Be sure to add the Java Bin path to your Environment Variables PATH
Java - Linux
Bluetooth with Non-WebOS device
Enabling Developer Mode (Rooting)
How To: Connect TP to network shares​HW
Exploded and PCB
Quick sum up/start up guide Thanks KameoRE
Bill of Materials
Specs 16GB
Specs 32 GB
Repair Manual / Teardown
Comparisons​
Extra info
Enabling Developer Mode (Rooting)
In general, simply installing the Palm SDK gives you everything you need for full access to the Linux operating system on any webOS device. There is no special "rooting" or "jailbreaking" process. Simply installing the SDK provides you with unlimited access to the Linux operating system.
Download & install the Palm SDK for Linux, OS X or Windows.
Enable developer mode on the HP Touchpad:
Launch Device Info and tap its top-left menu.
Select "Custom Application..." and type in: ##3386633#
In the application, move the Developer Mode slider to the On position.
Tap Reset the Device.
When reset is complete, Developer mode is enabled.
Plug the device into the computer via the USB cable, and just close out the USB storage mode thing.
The next step varies:
Mac OS X / Linux: Type novaterm into terminal to directly access the Linux command line for the HP Touchpad.
Windows: you will need to download and install a novaterm program.
On Windows 32-bit, download novacom-win-32.tgz and install novacom with NovacomInstaller_x86.msi.
On Windows 64-bit, download novacom-win-64.tgz and install novacom with NovacomInstaller_x64.msi.
Then, just like the Mac and Linux users you can just type novaterm.
At this point you will have a window with a prompt that says [email protected]: or something similar.
You are now logged in as root on your webOS device and can do anything you would normally do on a Linux device.
DISCLAIMER: We cannot be held liable for any loss of data, damage, bricking, or other malfunctions of the device. We solely provide the information needed to achieve root access.
This quick sum up/start up guide might come handy:
http://forums.precentral.net/hp-touchpad/293028-new-touchpad-heres-your-get-started-guide.html
[Q] What is wrong with my touchpad?
RESET: Hold Power Button & Home Button until the tablet resets.
Doing the above solved the below issue.
My touchpad won't turn on I used it until it had about 30 % battery last night, but didn't put it to charge. When I woke up this morning, it was at 28% battery. I used it to check facebook and xda, locked it and put it down to watch the price is right but when I went to use it again, none of the buttons unlocked it. I plugged it into mulitple outlets and held the power button for about 30 seconds each time, but nothing is happening I don't know what to do. Can anybody help?
Click to expand...
Click to collapse
solution #2
this happened twice:
plug it in to pc
open webos quick install
tools - command line
type "reboot" and hit enter
Bill of Materials
$318 Bill of Materials
Comparisons
Comparisons
Exploded and PCB
Exploded and PCB
First non-webOS phone to be fully tetherd with HP TouchPad
First non-webOS phone to be fully tetherd with HP TouchPad
Worked for me, I had to fool with it a couple of times to get it to work. My screenshot is attached
The messaging does not work but the phone calls do.
How To: Connect TP to network shares
How To: Connect TP to network shares
spud101
Member
Join Date: Jun 2004
Location: Netherlands
Posts: 574
Likes: 34
Thanks: 43
Thanked 69 Times in 34 Posts
Updated (Sep 7th 2011):
Rewritten to include a method for stock kernel, make shares usable for KalemSoft Media Player & automount at (re)boot. Thx to everybody who contributed to this thread! (Under construction, finished later)
Updated (Aug 9th 2011): processed some comments from this thread and the fact that uberkernel now also supports CIFS (& NFS).
Prerequisites:
- HP Touchpad, webOS 3.0.2 or later.
- One of the following Kernels:
---- Stock kernel
---- Uberkernel 3.0.2-52 or later (Next to support for CIFS & NFS this kernel also supports UTF-8. More info here: WebOS Internals Uber-Kernel
---- F15C,.. (completed later)
- Terminal access to your TP, either via webOS Quick Install or Xecutah + Xserver + Xterm (install from preware)
- Internalz Pro with show hidden files set to yes
Three parts:
This guide has three parts:
Basic Mounting
Mounting with shares visible in apps like Kalemsoft Media Player
"Sticky" mounting: Auto mount at (re)boot
Definitions:
hostIP = IP address of the computer or NAS you want to connect to. You can use hostnames too, but need to also edit /etc/hosts then.
sharename = The share name you want to connect to as configured on your computer/NAS
mountpoint-path = as discussed above, e.g. /mnt/nas
cifs = type of filesystem to mount (cifs is better version of smbfs, I've been told)
auto (or can also be noauto) auto/noauto determines if the share is mounted automatically at startup.
username & password = share login credentials. There are probably safer ways to do this instead of having this plain text on your device, anyone can tell me how to do that?
rw = access mode, in this case read & write, other possibilities exist too
The numbers have someting to do with filesystem check at boot.
1a: Basic Mounting (without fstab)
- Create a mountpoint, a path where the share will be accessible, e.g. /mnt/nas or /mnt/media/internal/nas I used Internalz Pro in master mode for this.
- In a terminal type:
mount.cifs //<hostIP>/<sharename> <mountpoint-path> -o username=<username>,password=<password>
Example: mount.cifs //10.0.1.26/DataVolume /mnt/Shared -o username=foo,password=bar
1b: Basic Mounting (with fstab, not supported by stock kernel)
To be finished later
2: Mounting with shares visible in apps like Kalemsoft Media Player
To be finished later
For now please refer to:
Road to Success - How to allow NAS to show up under /media/internal on Touchpad Apps?
How To: Connect TP to network shares
How To: Connect TP to network shares
3: "Sticky" mounting: Auto mount at (re)boot
To be finished later
For now please refer to:
Road to Success - Mounting SAMBA/CIFS Permanently on Touchpad
-------------------------------
Original post:
In short: The stock kernel on a webOS 3.0.2 Touchpad does not support CIFS. Or at least I didn't get it to work just the same way I do get it to work out of the box on a 1.4.5 Pre-.
Then I saw this thread: F15B & F15C test kernels
It says CIFS support! So I hesitantly installed this experimental F15C kernel, quickly ran Govnah to set max speed to 1.5 GHz (I don't want no real overclocking beyond this speed). But, YES, it does work, I now can access my NAS!
After I initially posted this thread webosinternals also added support for CIFS (& NFS) to the uberkernel (as of version 3.0.2-36). Thanks a lot for that guys!!
So how to go about:
- Install the F15C kernel from the testing kernel feed
The rest is standard linux stuff for mounting Samba shares:
- Create a mountpoint, a path where the share will be accessible, e.g. /mnt/nas or /mnt/media/internal/nas I used Internalz Pro in master mode for this.
- Open /etc/fstab again you can use Internalz Pro in master mode for this
Add a line:
//<hostIP>/<sharename> <mountpoint-path> cifs auto,username=<username>,password=<password>,rw 0 0
hostIP = IP address of the computer or NAS you want to connect to. You can use hostnames too, but need to also edit /etc/hosts then.
sharename = The share name you want to connect to as configured on your computer/NAS
mountpoint-path = as discussed above, e.g. /mnt/nas
cifs = type of filesystem to mount (cifs is better version of smbfs, I've been told)
auto (or can also be noauto) auto/noauto determines if the share is mounted automatically at startup.
username & password = share login credentials. There are probably safer ways to do this instead of having this plain text on your device, anyone can tell me how to do that?
rw = access mode, in this case read & write, other possibilities exist too
The numbers have someting to do with filesystem check at boot.
- Save the file
- Open a terminal
- type in this command:
mount -t cifs //<hostIP>/<sharename> <mountpoint-path> -o username=<username>,password=<password>
No idea whether all the -o options are still needed, as they are in the fstab line already as well.
Apparently mount -a should also mount your shares inside fstab. But for me that didn't work, maybe because I have it set to noauto.
This should do it.
Unmounting as follows:
umount <mountpoint-path> e.g. umount /mnt/nas
Note: as soon as you have a kernel running that supports CIFS, you can also use the xt tools. See this thread and the threads referenced inside it. samba filesharing - install/support thread
The xt tools will take over all the fstab editing and directory creation.
I agree this is still cumbersome. On an Android phone for example this is buildin in every decent filemanager. So I really, really hope that either or both Gemini and Internals HD will have some easy solution for this (both configuring and the actual mounting/unmounting). Or a solution straight from HP, this is also aimed at enterprise market after all!
Last edited by spud101; 09/08/2011 at 07:41 PM.
Thanked by 60milesmile, cookie_42, El_Titi, flyers333, ichi2k, Major Payne, mivoligo, Nightburn, obarthelemy, PF Graham, phil71, pre101, RickNeff, runner77, sf3000, sjp770, sps_2k1, tabaloos, teng_lin, thomaz, timjhenry, tlaswell​
Weird shortcut to USB mode
Has anybody else seen this?
While connected to PC in "just charging" mode I reached out and accidentally hit the Volume Down and Power buttons at the same time. The TouchPad instantly switched to USB Storage mode.
Interesting behavior and I couldn't seem to find any mention of it anywhere.
PreCentral had it as a tip on their web site about a week ago and I spotted it there - http://www.precentral.net/access-usb-mode-touchpad.
Quite a few other useful titbits crop up on there - it is worth following. I use the webOS News app from the App Catalog. That gives heads-up on the free software codes as well.
dmarchant said:
PreCentral had it as a tip on their web site about a week ago and I spotted it there - http://www.precentral.net/access-usb-mode-touchpad.
Quite a few other useful titbits crop up on there - it is worth following. I use the webOS News app from the App Catalog. That gives heads-up on the free software codes as well.
Click to expand...
Click to collapse
LOL, I think you mean "TIDBITS."
Too bad there is no reverse version of this.

[Q] Finding CPU time for a web app

I want to measure the real, system and user time for running a web benchmark (Can't post the link right now because of forum rules). It basically runs some pre-stored site data emulating basic human interaction and contains index.html, results.html and some java script files.
I was able to modify the index.html to autostart without pressing a start button and then using android intents to start web browser.
Code:
time adb shell am start -a android.intent.action.VIEW -n com.android.browser/.BrowserActivity -d file:///storage/emulated/0/benchmark/bbench/index.html
But the above code gives me the time for only the process which starts the index.html file. The time value is not for the entire benchmark run.
Possible solution: I can call the above intent in a script and then run the script using time function, the catch is that I need to get some kind of feedback or end of task status from the benchmark. I can't understand how to do it.
When I open results.html file, there is a for loop which basically runs the benchmark for some predefined number of iterations, I can perhaps modify this or get some status flag from here. BUT, the main question is can I poll a function/ variable in java script from shell script?
I am doing everything on android platform 4.2.2 .
Thanks!

[Q] Cannot start Android L Preview in emulator

I am trying to set up an Android Virtual Device (AVD) running Android L Preview so that I can begin developing an app using the new Material Design theme. I already have AVDs set up running KitKat and Gingerbread, it is only the Android L Preview that is not working. I have tried both the AVD Manager built-in to Android Studio, as well as from a separate installation of the Android SDK.
Here is my config.ini:
Code:
avd.ini.encoding=ISO-8859-1
abi.type=armeabi-v7a
disk.dataPartition.size=1024M
hw.accelerometer=yes
hw.audioInput=yes
hw.battery=yes
hw.camera.back=webcam0
hw.camera.front=emulated
hw.cpu.arch=arm
hw.cpu.model=cortex-a8
hw.dPad=no
hw.device.hash2=MD5:2fa0e16c8cceb7d385183284107c0c88
hw.device.manufacturer=Google
hw.device.name=Nexus 5
hw.gps=yes
hw.keyboard=yes
hw.lcd.density=480
hw.mainKeys=no
hw.ramSize=2048
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images\android-L\default\armeabi-v7a\
sdcard.size=1024M
skin.dynamic=no
skin.name=1080x1920
skin.path=1080x1920
tag.display=Default
tag.id=default
vm.heapSize=64
When I start the AVD I just get a black screen. I ended up letting it run for 5 hours and it never booted. Looking through the logcat, the following errors are repeated continuously:
Code:
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/default/accept_ra_rt_table: No such file or directory
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/eth0/accept_ra_rt_table: No such file or directory
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/lo/accept_ra_rt_table: No such file or directory
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/sit0/accept_ra_rt_table: No such file or directory
06-27 13:32:32.293 320-320/? E/SurfaceFlinger﹕ hwcomposer module not found
06-27 13:32:32.293 320-320/? E/SurfaceFlinger﹕ ERROR: failed to open framebuffer (No such file or directory), aborting
06-27 13:32:32.295 320-320/? A/libc﹕ Fatal signal 6 (SIGABRT), code -6 in tid 320 (surfaceflinger)
Here's the full logcat: http://pastebin.com/Ctjy5YLF
Does anyone have any idea what I did wrong or why the emulator isn't working? How can I get this up and running?
Thanks!
Same here
I'm having the exact same issue but not getting any errors in the LogCat. Hopefully someone has a solution. I've downloaded the new Android Studio and tried it but it didn't work. I also re-downloaded the ADT Eclipse bundle and tried it with that. Still no joy.
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Black screen with the emulator running android L
same problem here.. tried host GPU and no luck...
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
Can confirm enabling 'Use Host GPU' has made the emulator work.
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
Now I feel like an idiot. I initially had that selected for my Gingerbread AVD but it displayed an error when starting and disabled the message. I assumed my GPU wasn't compatible for whatever reason so I never tried it with the Android L AVD. Or perhaps it had something to do with trying it over an RDP remote desktop session before. Or my RAMDISK being full. Anyways, it's working now, so thank you.
GPU + Atom x86 has made the emulator go from a black screen to the android startup screen. And now, we wait
Edit: To be clear, I tried GPU + ARM, didn't work.
Edit2: It work, still slow as hell though
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
That worked for me. Thanks a million. :good:
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
This does work for me on Linux
Just an update - I discovered two things.
1 - this was not an issue with the L Preview, but rather with emulating a Nexus 5.
2 - there are two ways to solve the issue, one way is to use host GPU, the other is to select a skin rather than choosing no skin. The nice thing about the second method is that the snapshot feature can be used, greatly increasing the emulator start time.
FWIW.. I noticed..
So apparently the x86 version of Lollipop in the emulator requires the GPU or else you get a blank screen and missing hwcomposer module support files.. (I don't know if the files are in the preview .imgs but haven't gone looking).
If you create an arm (SLOW AS MOLASSES) arm image.. after the forever of booting you can do actual screenshots. It's 32-bit and the colors band, but there ya go.

[Q] Compiling directly on Hardware

I've been working on porting Octave (command line only) to the m8 for a few days now. I have all of its' dependencies compiled now, except for SuiteSparse. It requires output from some components during compile (it first compiles one program, then runs it to generate some data, then uses the data to compile others.) Since I can't run these on a computer, I've created a toolchain to compile on the device itself. Surprisingly, I can get the compiler to run on the device. Unfortunately, I have to use ld to run anything. The command looks something like this:
~$ ld-linux.so /path/to/gcc/tuple-gcc
It outputs just fine. But I can't simply run
~$ tuple-gcc
I have added the path to PATH, but still can't figure it out.
To compile anything I need to specify CC, as well as the other tools, but I can't figure out how to do this if they have to be executed using ld.
Any ideas?
Also, for anyone trying to do this, many configure scripts require "ls -t".
The coreutils that are installed in the base system are extremely stripped down, and ls doesn't support many of its normal switches.
I have compiled coreutils and will be testing them shortly. Hopefully they don't also have to be executed using ld!
***UPDATE***
I now have a fully-working compiler, to compile on the hardware itself.
Will try to make the 10 post minimum soon, to post a tut.

Categories

Resources