Hi folks...
My contribution by to the community...
Over the weekend, I figured out how to get a HID Mouse to connect to the Nexus Q.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wrote about it here..
goto : droidcloudshare.blogspot.com
*DISCLAIMER: PROCEED AT YOUR OWN RISK.
This is really pre-beta...
I am not responsible for any damage that your device that may result from doing this. Specifically, DON'T COME COMPLAINING TO ME IF YOU BRICK YOUR NEXUS Q. At this moment, the ability to unbrick a Nexus Q maybe very limited....
SO ONCE AGAIN, PROCEED AT YOUR OWN RISK.
Let me know if you have trouble and I'll try to fix.
Next thing will be to get HID Keyboard and Headset working too.
could you github NexusQTools Source Code
You can also use a usb OTG cable and hook up a usb keyboard / mouse. The cable I use for my XOOM worked just fine.
I couldn't make the Q boot into clockworkmod recovery, it boots to the normal UI with this img, so I used another one, if you are having problem with this step, just reply here and I will give you the link, I'm not sure if I can put links from another forum...
auad, I'd love that link, and if you could also perhaps toss some backups of your Q my way, that'd help me bring it out of a bricked state... thanks!
Followed all the steps, but the Nexus Q Tools baffles me. Attaching a screenshot and some logs.
07-11 17:01:55.968: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:01:55.984: D/OpenGLRenderer(483): Flushing caches (mode 0)
07-11 17:01:56.007: D/HidConnectActivity(2065): Remote BDADDR = 58:1F:AA:EA:FBC
07-11 17:01:56.015: D/HidConnectActivity(2065): Turning on Bluetooth...
07-11 17:01:56.015: D/BluetoothAdapterStateMachine(163): PowerOff process message: 1
07-11 17:01:56.015: D/BluetoothAdapterStateMachine(163): Bluetooth state 10 -> 11
07-11 17:01:56.015: I/bluedroid(163): Starting hciattach daemon
07-11 17:01:56.023: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.039: D/HidConnectActivity(2065): BT state change: STATE_TURNING_ON
07-11 17:01:56.117: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.171: I/ActivityManager(163): Displayed com.droidcloudshare.bt/.HidConnectActivity: +249ms
07-11 17:01:56.218: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.320: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.421: E/brcm_patchram_plus(2078): Done setting line discpline
07-11 17:01:56.507: I/bluedroid(163): bt_enable: ret: -1, errno: 114
07-11 17:01:56.507: W/bluedroid(163): Bluetoothd already started, unexpectedly!
07-11 17:01:56.507: I/bluedroid(163): Starting bluetoothd deamon
07-11 17:01:56.515: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.531: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.546: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.578: I/BluetoothEventLoop.cpp(163): agent_event_filter: Received method org.bluez.Agent:Release
07-11 17:01:56.687: D/BluetoothAdapterStateMachine(163): WarmUp process message: 101
07-11 17:01:56.710: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:02:06.687: D/BluetoothAdapterStateMachine(163): WarmUp process message: 104
07-11 17:02:06.687: E/BluetoothAdapterStateMachine(163): Bluetooth adapter SDP failed to load
07-11 17:02:06.695: E/BluetoothService.cpp(163): setBluetoothTetheringNative false
07-11 17:02:06.734: I/bluedroid(163): Stopping bluetoothd deamon
07-11 17:02:07.234: I/bluedroid(163): Stopping hciattach deamon
07-11 17:02:07.234: D/BluetoothAdapterStateMachine(163): Bluetooth state 11 -> 10
07-11 17:02:07.234: D/BluetoothAdapterStateMachine(163): PowerOff process message: 101
07-11 17:02:07.242: D/HidConnectActivity(2065): BT state change: STATE_OFF
07-11 17:02:07.273: D/DockEventReceiver(427): finishStartingService: stopping service
07-11 17:02:11.289: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:02:11.390: D/dalvikvm(637): GC_CONCURRENT freed 464K, 5% free 12609K/13191K, paused 4ms+4ms
07-11 17:04:14.281: D/dalvikvm(163): GC_CONCURRENT freed 513K, 6% free 15453K/16327K, paused 5ms+4ms
07-11 17:05:35.359: D/OpenGLRenderer(483): Flushing caches (mode 2)
07-11 17:05:35.367: I/EventLogService(444): Aggregate from 1342038935272 (log), 1342038935272 (data)
07-11 17:05:35.421: I/ServiceDumpSys(444): dumping service [account]
07-11 17:05:35.453: D/dalvikvm(444): GC_CONCURRENT freed 331K, 4% free 12860K/13319K, paused 5ms+3ms
07-11 17:07:00.187: D/PermissionCache(99): checking android.permission.READ_FRAME_BUFFER for uid=2000 => granted (244 us)
07-11 17:07:02.804: D/dalvikvm(163): GC_CONCURRENT freed 578K, 5% free 15513K/16327K, paused 5ms+5ms
fredc888 said:
Hi folks...
My contribution by to the community...
Over the weekend, I figured out how to get a HID Mouse to connect to the Nexus Q.
I wrote about it here..
goto : droidcloudshare.blogspot.com
*DISCLAIMER: PROCEED AT YOUR OWN RISK.
This is really pre-beta...
I am not responsible for any damage that your device that may result from doing this. Specifically, DON'T COME COMPLAINING TO ME IF YOU BRICK YOUR NEXUS Q. At this moment, the ability to unbrick a Nexus Q maybe very limited....
SO ONCE AGAIN, PROCEED AT YOUR OWN RISK.
Let me know if you have trouble and I'll try to fix.
Next thing will be to get HID Keyboard and Headset working too.
Click to expand...
Click to collapse
This works well, a small revision in the directions that may help a few people are:
Step #5 item 7 should read:
Update the main.conf ownership and permissions
adb shell chown bluetooth /system/etc/bluetooth/main.conf
adb shell chmod 440 /system/etc/bluetooth/main.conf
I also had a question regarding connecting a second input device such as a wireless keyboard, would I just repeat the Stpe #6 item 4 with the Bluetooth address for the device I wish to input? Also would you happen to know why an on screen keyboard doesn't appear? I can't type anything nor can I open any application that has keyboard input such as Google Play & Gmail (to sign in)
mrjaymillz said:
This works well, a small revision in the directions that may help a few people are:
Step #5 item 7 should read:
Update the main.conf ownership and permissions
adb shell chown bluetooth /system/etc/bluetooth/main.conf
adb shell chmod 440 /system/etc/bluetooth/main.conf
I also had a question regarding connecting a second input device such as a wireless keyboard, would I just repeat the Stpe #6 item 4 with the Bluetooth address for the device I wish to input? Also would you happen to know why an on screen keyboard doesn't appear? I can't type anything nor can I open any application that has keyboard input such as Google Play & Gmail (to sign in)
Click to expand...
Click to collapse
To put it back exactly like it was, you'd issue
chown bluetooth.bluetooth main.conf
note the period, as help for chown on android shows USER[.GROUP] for setting the permissions.
Either way, this worked great for pairing a magic trackpad. Interestingly if i multitouch all 10 fingers on the pad, there's representations for each finger that show up on the display output on the Q
Scrambling my brain!
Hey all, just giving a bump to see if anyone is still watching. I'm sort of novice, but trying hard to wrap my head around this. My Q is rooted properly I believe. Been able to sideload and get the launcher to work, so I'm now onto the bluetooth mouse.
1. I noticed when I ADB SHELL MOUNT, where it should say "rootfs on / type rootfs (rw)" it says "rootfs / rootfs ro,realtime 0 0". If that is not read/wright will it cause me issues down the road?
2. When I fastboot the recovery image I downloaded, it doesn't go into CWM recovery, just boots normally. EDIT: Solved this by using the steelhead boot img.
3. What string would I use to list the main.conf so that I could confirm that my chmod worked?
4. When I get to the step "adb shell am start -a android.intent.action.MAIN -n com.droidcloudshare.bt/.HidConnectActivity --es 00:07:61:EB:1DD", I am returned with a list of am usage commands followed by "Error: Argument expected after "00:07:61:EB:1DD"". EDIT: So I didn't realize that {HID Mouse Bluetooth Address} was part of the string. So this time I entered adb shell am start -a android.intent.action.MAIN -n com.droidcloudshare.bt/.HidConnectActivity --es 00:07:61:EB:1DD {HID Mouse Bluetooth Address} and was returned with this:
Starting: Intent { act=android.intent.action.MAIN pkg=Mouse cmp.droidcloudshare.bt/.HidConnectActivity (has extras) }
Error type 3
Error: Activity Class {com.droidcloudshare.bt/com.droidcloudshare.bt.HidConnectActivity} does not exist.
5. I've been retracing my steps, and when I perform adb install -r NexusQTools.apk I get the amount of data transferred and how fast, but then adb just hangs, no "Success". Originally I just closed the command window and restarted and moved on assuming it installed. If Success isn't confirmed is it safe to say it didn't properly install? Is this apk essential to get the mouse to pair on the Q?
So for now I'm kinda stuck, if anyone has a bit of advice I'll gladly take it and push on.
Cheers
can this be used to connect a keyboard and mouse at the same time?
I think they only reason it won't work for a keyboard right now is because there needs to be a driver present for the keyboard
Related
Here's how to use logcat..There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app..Here are two good examples are either aLogcat or CatLog I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb.
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Please do NOTE: : I am just sharing. Original post is Here.
Don't be a noob. Be a newbie..!!
Details here.
Great guide! I am glad that I can help you by logcat. Thanks.
Sent from my E10i using xda app-developers app
How long take the. Logcat?
Sent from my E10i using xda premium
ruben21 said:
How long take the. Logcat?
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Whatever you want.
Sent from my E10i using xda app-developers app
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
ruben21 said:
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Just press CTRL + C
Thanks bro.
☜ Sent from my X10 MP U20i ☞
This is a port of Ubuntu Touch (Preview) for Huawei Mediapad tablet (s7-30xx).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Keep in mind that:
- its experimental;
- not for daily use;
- only for developers;
- dont try install it if you have no skills at least in working with adb;
- you have to do a nandroid before installing;
- dont blame anyone for broken device
How to install (almost everything the same as for other cm9-10.1 releases):
1. Install twrp/cwm recovery.
2. Make factory reset.
3. Install the device specific part for Ubutnu.
4. Install the generic Ubuntu part.
5. Install dpi fix.
6. Reboot
7. Open terminal at PC, connect tablet via usb cable to it and enter the following commands:
Code:
adb root
Code:
adb shell
Code:
ubuntu_chroot shell
If you want to see GUI then type:
Code:
ubuntu-session
--- Enjoy the testing! --- (or not enjoy )
Download links:
- Device specific part: http://www.mediafire.com/download.php?71147ctm19763n8.
- Generic Ubuntu part: http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip;
- DPI fix: http://www.mediafire.com/download.php?g8granxnx1q2iqt.
Working:
- Ubuntu Touch OS;
- Touchscreen;
- Display;
- ADB;
- Wifi (with manual config).
Some bad screenshots:
Nice
Is working/not working this or more things don't work?
Question : What Works?
Answer : As this is a Developer Build, dont expect much to work. The items that have been confirmed to work are;
Touchscreen
Sound (over speakers)
Display
Internet Browser
WiFi (No WPS)
Camera (Front and Back)
Video Player
ADB
Screen Brightness Controls
Automatic Brightness
Speech Driven HUD (Yes, it works)
GSM Voice (No APN Settings)
The SideStage Seems to be working
Question : What Does Not Work?
Answer : As this is a developer build, dont expect things to work properly, here are a few things that are not working
3G/4G Data
Audio Out via Headphones
HDMI
Bluetooth
Most Applications and Menus
Charging Indicator
Software Center (Note : You can install simple shell applications via apt-get install … once inside the chroot)
Most applications are placeholders
MMS
CDMA Connections
SIM Storage
Auto Rotation (Or any rotation for that matter)
Random Crashes when swiping
Notifications (All of them are placeholders)
Most Applications that do function are web apps like m.gmail.com.
NFC
Click to expand...
Click to collapse
Screenshots
Wow, this is great too bad there is no networking, otherwise it is pretty neat
One bug is that the keyboard is too big for the screen (see messaging screenshot below).
Here are screenshots via ddms:
OMG!!! Thank you!!! Can we expect more of ubuntu touch for mediapad beyond a developer preview?
Sent from my Huawei MediaPad using xda app-developers app
That was a very quick try, so dont wait too much from it. Besides ubuntu touch in very very early stage of developing.
For keyboard Its needed to adjust ubuntu-session, i havent done it in proper way.
Please don't stop developing for the Mediapad.
By the way i have been able to setup wireless connection (to open access point, cant do it for wpa2)
To do it you need from
Code:
adb shell
perform the following:
Code:
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/rtecdc-bcm4329.bin nvram_path=/system/etc/wifi/nvram-bcm4329.txt
Then go to chroot shell via
Code:
ubuntu_chroot shell
and then setup wireless connection from there (in linux way from terminal
For example:
Code:
mount -t proc proc /proc
ifconfig wlan0 up
iwconfig wlan0 mode managed
iwconfig wlan0 essid your_ssid
dhclient wlan0
or something like that.
will this work on s7-931u?
Sent from my GT-I9000 using xda app-developers app
bobo1337 said:
will this work on s7-931u?
Click to expand...
Click to collapse
Not. This build are compatible only for MediaPad S7-30*u/w
Hello, i have tried to get ubuntu touch running, but my screen stays black.
when typing ubuntu-session in adb I see two lines in response:
ubuntu-session
Redirecting output to local session logs
does not look that bad, but my screen stays black all the time
and i can not connect to the device via adb anymore.
any idea what is going on? I used the daily build from 8.03
thx and greetings
Hi
I have tried to flash one more time, here is the log of the first call of ubuntu-session after flash:
Code:
[email protected]:/ # ubuntu_chroot shell
ubuntu_chroot shell
[email protected]:/# ubuntu-session
ubuntu-session
Redirecting output to local session logs
/usr/bin/ubuntu-session: line 21: /home/phablet/.ubuntu-session/logs/ubuntu-sess
ion.log: No such file or directory
Error, do this: mount -t proc proc /proc
grep: /proc/cpuinfo: No such file or directory
Device=
Starting session bus
Started pulseaudio with pid 398 (0 secs start delay)
Started maliit-server with pid 403 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 403 Segmentation fault ${service[1]} $
arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started qml-phone-shell with pid 410 (2 secs start delay)
Got Shell pid = 410
Started chewie_messaging_populate_menu with pid 415 (0 secs start delay)
Started friends-service with pid 420 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 410 Segmentation fault ${service[1]} $
arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started manage-address-books.py with pid 443 (2 secs start delay)
Started ofono-setup with pid 483 (12 secs start delay)
Stopping services...
Stopping pulseaudio
/usr/bin/ubuntu-session: line 38: kill: (398) - No such process
Stopping maliit-server
/usr/bin/ubuntu-session: line 38: kill: (403) - No such process
Stopping qml-phone-shell
/usr/bin/ubuntu-session: line 38: kill: (410) - No such process
Stopping chewie_messaging_populate_menu
Stopping friends-service
Stopping manage-address-books.py
/usr/bin/ubuntu-session: line 38: kill: (443) - No such process
Stopping ofono-setup
Killing session bus...
Session stopped.
[email protected]:/#
Can anybody tell me what went wrong?
Killigrew said:
Hi
I have tried to flash one more time, here is the log of the first call of ubuntu-session after flash:
Code:
[email protected]:/ # ubuntu_chroot shell
ubuntu_chroot shell
[email protected]:/# ubuntu-session
ubuntu-session
Redirecting output to local session logs
/usr/bin/ubuntu-session: line 21: /home/phablet/.ubuntu-session/logs/ubuntu-sess
ion.log: No such file or directory
Error, do this: mount -t proc proc /proc
grep: /proc/cpuinfo: No such file or directory
Device=
Starting session bus
Started pulseaudio with pid 398 (0 secs start delay)
Started maliit-server with pid 403 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 403 Segmentation fault ${service[1]} $
arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started qml-phone-shell with pid 410 (2 secs start delay)
Got Shell pid = 410
Started chewie_messaging_populate_menu with pid 415 (0 secs start delay)
Started friends-service with pid 420 (0 secs start delay)
/usr/bin/ubuntu-session: line 122: 410 Segmentation fault ${service[1]} $
arguments &>"$HOME/.ubuntu-session/logs/$binary.log"
Started manage-address-books.py with pid 443 (2 secs start delay)
Started ofono-setup with pid 483 (12 secs start delay)
Stopping services...
Stopping pulseaudio
/usr/bin/ubuntu-session: line 38: kill: (398) - No such process
Stopping maliit-server
/usr/bin/ubuntu-session: line 38: kill: (403) - No such process
Stopping qml-phone-shell
/usr/bin/ubuntu-session: line 38: kill: (410) - No such process
Stopping chewie_messaging_populate_menu
Stopping friends-service
Stopping manage-address-books.py
/usr/bin/ubuntu-session: line 38: kill: (443) - No such process
Stopping ofono-setup
Killing session bus...
Session stopped.
[email protected]:/#
Can anybody tell me what went wrong?
Click to expand...
Click to collapse
I got issue same you,still can't solve.
chok_thewa said:
I got issue same you,still can't solve.
Click to expand...
Click to collapse
I tried to launch Ubuntu on my MediaPad
It's work onli in wire-to-pc mode. When I disconnect a Usb-wire - I have a blank screen.
Any plans on future work on it? I read that late may build should be for daily use so I finally managed to try it. I used latest raring build but I had no luck with getting GUI working :/
Can I boot directly in, or is this Chroot only?
The install instructions include a chroot, but is that what ubuntu ends up running in? Is it possible to run without loading android into ram as well?
Thanks.
This is mostly a post about a specific problem with Google Play carrier billing.
Here is the problem:
I want to subscribe to a trial of Google Play Music All Access
I want to use carrier billing (with my Verizon Wireless phone)
When I select "Bill my Verizon Wireless account", I get a red message stating "Error processing your purchase"
Notes:
Carrier billing usually works for me with Verizon Wireless
I am NOT using WiFI while trying to make the purchase
I do not have blocks on messaging or web purchases with Verizon Wireless
Verizon Wireless support cannot find any reason why the purchase would fail
I am well below the $25/mo. cap for Verizon Wireless carrier billing (I've only spent $.99 this month so far)
Step by step:
I turned off WiFi on my android phone (mostly stock rooted Samsung Galaxy Nexus running JB 4.2.2 on VzW).
I plugged my phone into my PC with the USB cable.
USB debugging is on.
I fired up adb shell on my PC.
I used su to start a superuser shell in adb
I typed:
Code:
logcat | grep --color=auto -i -E 'play|market|store|carrier|billing|finsky|phonesky|vending'
I launched Play Music (version v5.0.1041J.689753)
I opened the menu (...)
I selected "Settings" from the menu
I selected "Try All Access for free" in settings
I was sent to a "Google play" screen titled "Try Google Play Music All Access"
I selected "Try it FREE"
A modal dialog box opened titled "Google Play Music All Access"
From logcat:
Code:
I/ActivityManager( 378): START u0 {act=com.android.vending.billing.PURCHASE cat=[android.intent.category.DEFAULT] pkg=com.android.vending cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity (has extras)} from pid 8403
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity: +121ms
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity (has extras)} from pid 1708
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity: +153ms
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I clicked "Free"
I clicked "Payment options"
I clicked "Bill my Verizon Wireless account"
From logcat:
Code:
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity (has extras)} from pid 1708
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity: +140ms
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
D/Volley ( 1708): [155] BasicNetwork.logSlowRequests: HTTP response for request=<[ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133> [lifetime=14351], [size=7526], [rc=200], [retryCount=0]
D/Volley ( 1708): [1] Request.finish: 14363 ms: [ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133
I get "Error processing your purchase." in red print
This line really got my attention:
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
I'm assuming "DCB" is "Direct Carrier Billing", and "DCB 2" might be something like a monthly subscription billed with carrier billing. I make purchases with carrier billling so I'm not sure why it would say "Carrier billing config is null."
To make sure carrier billing is working (still), I launched "Angry Bird Seasons", and went "shopping" for 80 power-up bundles for $4.99. I select the same options for "Payment Options" and "Bill my Verizon Wireless account" and "Buy" (bringing me to the "Confirm password" screen, where I canceled the purchase).
This line stood out from logcat:
Code:
D/Finsky ( 1708): [1] PurchaseFragment.runCompleteFlowAndContinue: Start complete flow for DCB3 instrument.
"DCB3" ???. Maybe another "Direct Carrier Billing" purchase type (for a one-time consumable purchase)?
Since Google Play is not open source, I have no way of looking at the code to see what these debug lines actually mean.
Can anybody give me any guidance on this?
Having the same problem with a rooted Droid RAZR. Does it on both the stock rom and CM10.1.
Edit: Called customer service. They are looking into it. Told me they should contact me back in 24/48 hours.
Hello all
I am having some trouble with SDK installing apps to my Android. I've tried to find many forums about my issue, but I've hit a brick wall every time. My rooted device is an LG Optimus C running Android 2.2 (ancient lol). My issue is that I'm getting the error: Failure [INSTALL_FAILED_DEXOPT] for every app I try to install. I've wiped the device twice and then found out that this error happens every time after I've installed a good amount of apps...which I read somewhere that this will happen because of not having enough space in Dalvik..or in the data area and won't allow the install to write anything else..correct me if I'm wrong on this I've also cleared all caches multiple times, including Dalvik.
I've also tried the work around where you try and skip that all together and put the app straight into /system /app. That came up with no resolution, even with the correct properties selected (read/write/execute etc). So now, I really have no other avenues left but to come here and ask.
Here is the Logcat results I get using adb install -r app.apk no matter what app it is. I will use tumblog.apk (compatible with device) for this example:
D/AndroidRuntime( 4201):
D/AndroidRuntime( 4201): >>>>>> AndroidRuntime START com.android.internal.os.Run
timeInit <<<<<<
I/AndroidRuntime( 4201): Heap size: -Xmx32m
D/AndroidRuntime( 4201): CheckJNI is OFF
D/AndroidRuntime( 4201): Calling main entry com.android.commands.pm.Pm
W/ActivityManager( 1356): No content provider found for:
W/ActivityManager( 1356): No content provider found for:
D/PackageParser( 1356): Scanning package: /data/app/vmdl-166230949.tmp
D/PackageManager( 1356): Scanning package com.luckydroid.tumblelog
E/PackageManager( 1356): Package com.luckydroid.tumblelog has mismatched uid: 10
060 on disk, 10061 in settings
I/PackageManager( 1356): Linking native library dir for /data/app/com.luckydroid
.tumblelog-1.apk
D/installd( 1256): DexInv: --- BEGIN '/data/app/com.luckydroid.tumblelog-1.apk'
---
D/dalvikvm( 4211): Zip inflate: partial write (will retry): (24536 of 32768)
E/dalvikvm( 4211): Zip inflate: write failed: No space left on device
W/dalvikvm( 4211): DexOptZ: extraction of classes.dex from /data/app/com.luckydr
oid.tumblelog-1.apk failed
W/installd( 1256): DexInv: --- END '/data/app/com.luckydroid.tumblelog-1.apk' --
- status=0xff00, process failed
E/installd( 1256): dexopt failed on '/data/dalvik-cache/[email protected]@com.luckydroid.
[email protected]' res = 65280
W/PackageManager( 1356): Package couldn't be installed in /data/app/com.luckydro
id.tumblelog-1.apk
D/AndroidRuntime( 4201): Shutting down VM
I/AndroidRuntime( 4201): NOTE: attach of thread 'Binder Thread #3' failed
D/jdwp ( 4201): adbd disconnected
I really have no clue what any of this means lol...pretty new to logcat. I am aware of the file name not matching the original name of the apk..shouldn't matter considering I've installed many apps with shortened names. Any help would be greatly appreciated! Thanks
EDIT: Looks like "E/dalvikvm( 4211): Zip inflate: write failed: No space left on device" is the problem. Not enough space in Dalvik. Still have no idea how to work around.
Bump
Is this not posted in the correct forum? I'm just guessing no one knows of a solution?
Çözüme Yakın
Sizin sorununuz apk~classes.dex~.smali dosyalarının içinde gereksiz kodları siliniz. "Ayrıca Facebook klasörünü bulup siliniz (her clasess.dex'te bulunmaz)" ayrıca kimi classes.dex boyutu 9MB iken yükleniyor bazı clasess.dex dosyaları ise 7,8*MB olunca yüklenmiyor. Tabikide kodlar içinde dexOpt= dex options ayarı vardır ama ben bulamadım sadece bunları biliyorum. Umarım çözüm bulan çıkar. TR
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
MasterAwesome said:
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
Click to expand...
Click to collapse
Hello again,
I've made logcat, here is an interesting part, I think:
I/SecurityManagerService( 671): SMS received security event: App[START/com.android.keyguard]
I/WindowState( 556): WIN DEATH: Window{26a85ad0 u0 Keyguard}
I/ActivityManager( 556): Process com.android.systemui (pid 622) has died.
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
W/ActivityManager( 556): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
D/InputMethodManagerService( 556): --- calledFromForegroundUserOrSystemProcess ? calling uid = 1000 system uid = 1000 calling userId = 0, foreground user id = 0, calling pid = 556dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
I/StatusBarManagerService( 556): binder died for pkg=com.android.keyguard
I/WindowState( 556): WIN DEATH: Window{269b48a8 u0 NavigationBar}
W/InputDispatcher( 556): Attempted to unregister already unregistered input channel '268ba8e8 StatusBar (server)'
D/dalvikvm( 3948): Try to disable coredump for pid 3948
D/dalvikvm( 3948): Process 3948 nice name: com.android.systemui
D/dalvikvm( 3948): Extra Options: not specified
Click to expand...
Click to collapse
I discovered also that when the battery level drops to 99% process starts to work properly.
I include also whole log file compressed to .zip.
Still need help!
I have the same problem, even after a factory reset.
me too having the same issue. Is it hardware failure or just android?
I found a solution in an other tread :
http://forum.xda-developers.com/android/general/review-teclast-x89-baytrail-tablet-dual-t3039961