[Q] Compiling VNC Server Android - Android Q&A, Help & Troubleshooting

Hi all !
I see that project :
http://code.google.com/p/android-vnc-server/
I wan't to compile it on my PC for including the vnc server into my furture APK.
I have compiled it but the vnc client have a real bad image (See attachment)
There is the logs :
Code:
/ # androidvncserver
Initializing framebuffer device /dev/graphics/fb0...
xres=480, yres=800, xresv=480, yresv=1600, xoffs=0, yoffs=0, bpp=32
Initializing keyboard device /dev/input/event3 ...
Initializing touch device /dev/input/event1 ...
Initializing VNC server:
width: 480
height: 800
bpp: 32
port: 5901
Initializing server...
28/09/2011 14:13:44 Listening for VNC connections on TCP port 5901
# I just connect with an VNC Client
28/09/2011 14:14:13 Got connection from client 192.168.70.138
28/09/2011 14:14:13 other clients:
28/09/2011 14:14:13 Client Protocol Version 3.8
28/09/2011 14:14:13 Protocol version sent 3.8, using 3.8
Dirty page: 480x800+0+0...
28/09/2011 14:14:13 rfbProcessClientSecurityType: executing handler for type 1
28/09/2011 14:14:13 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
28/09/2011 14:14:13 Pixel format for client 192.168.70.138:
28/09/2011 14:14:13 8 bpp, depth 6
28/09/2011 14:14:13 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
28/09/2011 14:14:13 Enabling full-color cursor updates for client 192.168.70.138
28/09/2011 14:14:13 Enabling NewFBSize protocol extension for client 192.168.70.138
28/09/2011 14:14:13 Using ZRLE encoding for client 192.168.70.138
28/09/2011 14:14:14 Pixel format for client 192.168.70.138:
28/09/2011 14:14:14 32 bpp, depth 24, little endian
28/09/2011 14:14:14 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
28/09/2011 14:14:14 Enabling full-color cursor updates for client 192.168.70.138
28/09/2011 14:14:14 Enabling NewFBSize protocol extension for client 192.168.70.138
28/09/2011 14:14:14 Switching from ZRLE to hextile Encoding for client 192.168.70.138
# I disconnect the VNC Client.
28/09/2011 14:14:51 Client 192.168.70.138 gone
28/09/2011 14:14:51 Statistics events Transmit/ RawEquiv ( saved)
28/09/2011 14:14:51 FramebufferUpdate : 2 | 0/ 0 ( 0.0%)
28/09/2011 14:14:51 hextile : 1 | 1351415/ 1536012 ( 12.0%)
28/09/2011 14:14:51 ZRLE : 1 | 15792/ 384000 ( 95.9%)
28/09/2011 14:14:51 RichCursor : 2 | 342/ 342 ( 0.0%)
28/09/2011 14:14:51 TOTALS : 6 | 1367549/ 1920354 ( 28.8%)
28/09/2011 14:14:51 Statistics events Received/ RawEquiv ( saved)
28/09/2011 14:14:51 ClientCutText : 1 | 32/ 32 ( 0.0%)
28/09/2011 14:14:51 PointerEvent : 285 | 1710/ 1710 ( 0.0%)
28/09/2011 14:14:51 FramebufferUpdate : 3 | 30/ 30 ( 0.0%)
28/09/2011 14:14:51 SetEncodings : 2 | 64/ 64 ( 0.0%)
28/09/2011 14:14:51 SetPixelFormat : 2 | 40/ 40 ( 0.0%)
28/09/2011 14:14:51 TOTALS : 293 | 1876/ 1876 ( 0.0%)
Do you know why my screen is "green" and "entralaced" ?
With other binarie of vncserver in android, with the same client, the image is good.
Thanks for help !

Please use the Q&A Forum for questions Thanks
Moving to Q&A

Related

[Q][Solved] Void #e and L2TP/IPSec support

Hello, there.
I installed void #e a while ago on my O1, everything went smoothly until I had to setup a VPN with L2TP/IPsec.
After poking around with adb logcat, I found that the bundled kernel (mik_os's one) missed support for NETKEY sockets, IPSec over IPv4 and PPP altogether, so I rebuilt the kernel from source adding all missing options to .config.
I flashed the new kernel, boot it and tried to start the VPN, but it failed again.
This time - however - racoon was able to set up an IPsec security association with the remote host, but pppd complained about missing PPP support in kernel:
Code:
I/racoon ( 4330): ISAKMP-SA established <scrubbed>[500]-<scrubbed>[500] spi:<scrubbed>
I/racoon ( 4330): initiate new phase 2 negotiation: <scrubbed>[500]<=><scrubbed>[500]
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[0]-><scrubbed>[0] spi=<scrubbed>(0x<scrubbed>)
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[500]-><scrubbed>[500] spi=<scrubbed>(0x<scrubbed>)
I/mtpd ( 4532): Tunnel established
D/mtpd ( 4532): Received ICRP (remote_session = 65060) -> Sending ICCN
D/mtpd ( 4532): Received ACK
I/mtpd ( 4532): Session established
I/mtpd ( 4532): Creating PPPoX socket
I/mtpd ( 4532): Starting pppd (pppox = 13)
I/mtpd ( 4532): Pppd started (pid = 4533)
I/pppd ( 4533): Using PPPoX (socket = 13)
E/pppd ( 4533): This system lacks kernel support for PPP. This could be because
E/pppd ( 4533): the PPP kernel module could not be loaded, or because PPP was not
E/pppd ( 4533): included in the kernel configuration. If PPP was included as a
E/pppd ( 4533): module, try `/sbin/modprobe -v ppp'. If that fails, check that
E/pppd ( 4533): ppp.o exists in /lib/modules/`uname -r`/net.
E/pppd ( 4533): See README.linux file in the ppp distribution for more details.
I/mtpd ( 4532): Received signal 17
I/mtpd ( 4532): Pppd is terminated (status = 4)
D/mtpd ( 4532): Sending STOPCCN
I/mtpd ( 4532): Mtpd is terminated (status = 36)
I double-checked /proc/conf.gz and sure enough it contains all ppp options:
Code:
# zcat /proc/config.gz | grep PPP
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
CONFIG_PPPOE=y
CONFIG_PPPOL2TP=y
CONFIG_PPPOLAC=y
CONFIG_PPPOPNS=y
I noticed in mik_os's sources that LG also set CONFIG_ANDROID_PARANOID_NETWORK to y, while in mik_os's build it is set to n.
Does anyone know if they are related and/or if I'm running into another issue (permissions, maybe)?
Thanks in advance
Sure enough, it was CONFIG_ANDROID_PARANOID_NETWORK.
For future reference, if this option is undefined AID_NET_ADMIN and AID_NET_RAW have no special meaning for the kernel (iow, CAP_NET_ADMIN and CAP_NET_RAW are not granted to non-root processes belonging to those special groups).
Moreover, network access restrictions are completely ignored, so any application can create sockets and/or access the bluetooth stack even if its manifest does not specify the relevant permissions.

Connect USB Webcam

I am trying to connect my usb webcam to my Transformer Prime. The webcam uses a generic Realtek chipset, which should be supported by the linux kernel. When I connect the webcam via usb I can see the device when executing the lsusb command in the terminal. I can also see that the file /dev/video0 is created after I plug in the webcam, but I cannot find an application that is able to display the stream from the webcam. Is is possible to open this stream using an app under Android?
The problem is probably more that apps like Skype don't expect this to happen and will not provide an option for the webcam and instead rely on the in-built ones.
You might be able to access /dev/video0 from within ubuntu/BT5 on the TFP. I doubt the video performance would be stellar though.
I now found a way to access the webcam. I found an eclipse project under this url: http://brain.cc.kogakuin.ac.jp/research/usb-e.html
The application works and displays the picture from my webcam, but before running the app I had to execute the command "chmod 777 /dev/video0" in the terminal and every time I reconnected the device again.
Thenetstriker said:
I now found a way to access the webcam. I found an eclipse project under this url: http://brain.cc.kogakuin.ac.jp/research/usb-e.html
The application works and displays the picture from my webcam, but before running the app I had to execute the command "chmod 777 /dev/video0" in the terminal and every time I reconnected the device again.
Click to expand...
Click to collapse
nice find
so do you know what app allows you to use those cameras?
or is his app the only once that works atm?
I too am trying to get this to work, I have downloaded and compiled the kogakuin app but how do I compile/load the v4l2_camera_v2.patch? and/or make the necessary kernel mods?
Please Help.
lil-devil said:
nice find
so do you know what app allows you to use those cameras?
or is his app the only once that works atm?
Click to expand...
Click to collapse
This app is the only one I found that works. But so far it works only on my Transformer Prime. On my Samsung Galaxy S2 (Cyanogenmod 9) it crashes the phone when using /dev/video0 and when using /dev/bus/usb/002/003 it just doesn't work. (Maybe I have to compile a custom kernel using the settings the developer describes on his BitBucket page, I will try this tonight)
pjames1972 said:
I too am trying to get this to work, I have downloaded and compiled the kogakuin app but how do I compile/load the v4l2_camera_v2.patch? and/or make the necessary kernel mods?
Please Help.
Click to expand...
Click to collapse
On my Transformer Prime the app just works, I did not make any modifications to the kernel. Just compile the app and upload it to your TF201 and it should work.
Thanks Thenetstriker,
I failed to mention that i am using Iconia A500 rooted stock 3.2 not the TF201.
Today I bought a UVC compliant webcam and I now have the kogakuin eclipse project working on my device.
have you tried putting "chmod 777 /dev/video0" in your ueventd.xxxx.rc script?
Paul
http://forum.xda-developers.com/showpost.php?p=22884164&postcount=3
Thenetstriker said:
This app is the only one I found that works. But so far it works only on my Transformer Prime. On my Samsung Galaxy S2 (Cyanogenmod 9) it crashes the phone when using /dev/video0 and when using /dev/bus/usb/002/003 it just doesn't work. (Maybe I have to compile a custom kernel using the settings the developer describes on his BitBucket page, I will try this tonight)
Click to expand...
Click to collapse
I tried to compile my own Kernel with video 4 linux enabled and the app still doesn't work on my Samsung Galaxy S2. But the device shows up on android. Using the app "USB Device Info" I was able to get the following information about my Logitech webcam USB interfaces, but I don't have the knowledge on how to communicate with USB devices over these interfaces. I think someone who has this knowledge could write an application using the USB Host feature from Android 4.0 to show the webcam picture even without root access.
Code:
Device Info
Device Path: /dev/bus/usb/002/002
Device Class: Miscellaneous (0xef)
Vendor ID: 046d
Vendor Name: Logitech, Inc.
Product ID: 07d2
Product Name: not in db
Interfaces
Interface #0
Class: Video Device (0xe)
Endpoint: #0
Address : 135 (10000111)
Number : 7
Direction : Inbound (0x80)
Type : Intrrupt (0x3)
Poll Interval : 8
Max Packet Size: 16
Attributes : 000000011
Interface #1
Class: Video Device (0xe)
Endpoints: none
Interface #2
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 192
Attributes : 0000000101
Interface #3
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 384
Attributes : 0000000101
Interface #4
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 512
Attributes : 0000000101
Interface #5
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 640
Attributes : 0000000101
Interface #6
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 800
Attributes : 0000000101
Interface #7
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 944
Attributes : 0000000101
Interface #8
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 2688
Attributes : 0000000101
Interface #9
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 2848
Attributes : 0000000101
Interface #10
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 3040
Attributes : 0000000101
Interface #11
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 4992
Attributes : 0000000101
Interface #12
Class: Video Device (0xe)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 1
Max Packet Size: 5116
Attributes : 0000000101
Interface #13
Class: Audio Device (0x1)
Endpoints: none
Interface #14
Class: Audio Device (0x1)
Endpoints: none
Interface #15
Class: Audio Device (0x1)
Endpoint: #0
Address : 134 (10000110)
Number : 6
Direction : Inbound (0x80)
Type : Isochronous (0x1)
Poll Interval : 4
Max Packet Size: 68
Attributes : 0000000101
I've just found a video on YouTube which shows an "UVC Player" which seams to be able to access UVC compatible webcams, but the website that is mentioned on this thread is written in japanese and I didn't find any source code or a sample application:
http://www.youtube.com/watch?v=aieJMBFLEdA
http://www.infinitegra.co.jp/technology/rd_android_uvc1.htm
And another link here:Google crimsonwoods UVCCapture (Sorry not enough posts yet)
Have compiled just need to work out what to do with it
Thenetstriker said:
I now found a way to access the webcam. I found an eclipse project under this url: http://brain.cc.kogakuin.ac.jp/research/usb-e.html
The application works and displays the picture from my webcam, but before running the app I had to execute the command "chmod 777 /dev/video0" in the terminal and every time I reconnected the device again.
Click to expand...
Click to collapse
Are you rooted?
jazzcat007 said:
Are you rooted?
Click to expand...
Click to collapse
Yes, the device has to be rooted for this application, The Android API does not seam to support the isochronous USB interfaces, so no non rooted access possible at the moment.
Thenetstriker said:
Yes, the device has to be rooted for this application, The Android API does not seam to support the isochronous USB interfaces, so no non rooted access possible at the moment.
Click to expand...
Click to collapse
Check this out
someone has already created an app for it .. we just need to cook a new kernel for it
josh_m said:
Check this out
someone has already created an app for it .. we just need to cook a new kernel for it
Click to expand...
Click to collapse
Ok, where do I find this app?
this is a good find, what's the image quality like? is it substantially better than the front facing camera of the Prime?
http://forum.xda-developers.com/showpost.php?p=22884164&postcount=3
josh_m said:
http://forum.xda-developers.com/showpost.php?p=22884164&postcount=3
Click to expand...
Click to collapse
Has anyone tried the files in that link? The thread is for the Xoom, so would the "Development Overlay" and "Tiamat Kernel" work with the other tablets ( I have the Acer A500, but I realize this is a transformer thread) ?
tried to compile my own Kernel with video 4 linux enabled and the app still doesn't work on my Samsung Galaxy S2. But the device shows up on android. Using the app "USB Device Info" I was able to get the following information about my Logitech webcam USB interfaces, but I don't have the knowledge on how to communicate with USB devices over these interfaces. I think someone who has this knowledge could write an application using the USB Host feature from Android 4.0 to show the webcam picture even without root access.
Click to expand...
Click to collapse
Thenetstriker,
Your USB Device info looks OK to mine and it looks like the USB stub is being created OK but my first non UVC compliant cam did the same and it just did not work.
Make sure your device is listed in http://www.ideasonboard.org/uvc/, if not you may need to buy a new cam.
For some reason I have to occasionally reboot my A500 with the webcam inserted, unplug it, start the app and then reinsert the webcam to get mine to work.
Normally though, mine works if I start the app first before plugging in.
Paul,

[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.

[Q] updated to 4.0.4 Bionic cant be found by adb on osx

1st I'm a noob, so be kind. After getting the 4.0.4 update pushed from Verizon, my Motorola Bionic has disappeared from adb radar. terminal command "adb devices" returns nothing under list of devices attached, when its usb connected. (I've updated my android sdks. to latest platform tools).
I have tried each of the 3 usb settings 4.0.4 offers (Mass Storage, Media Device(MTP) and Camera (PTP), with debugging both on and off. Still no joy. I have killed and started adb server and rebooted both the macbook pro and the bionic. BTW - the original android os it started with had a "Charge Only" mode, which was the usb connection type that adb connection had previously required, but that's gone from this 4.0.4 upgrade for some reason. I have searched numerous forums and threads, but haven't found anything that seems to specifically apply to what i'm encountering. Those forums that did have posts about adb not finding connected device, mostly suggested rebooting and updated sdks. A couple suggested editing some config files, but I couldn't locate those. Any and all suggestions/solutions will be gratefully attempted. Thanks in advance for your analysis.
I'm running osx lion 10.7.5 on a MacBook Pro. I can provide phone system info if necessary. I've copied below the info I've gathered about the usb port the device is connected to from USB Prober.
Using usb prober the device appears as "Composit device: "XT875" in the bus probe. Port Info shows as: 0x1018, not captive, external device, connected, enabled. Device Descriptor shows as: Descriptor Version Number: 0x0200
Device Class: 0 (Composite)
Device Subclass: 0
Device Protocol: 0
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x22B8/0x4353 (Motorola MDS)
Device Version Number: 0x0216
Number of Configurations: 1
Manufacturer String: 2 "Motorola"
Product String: 3 "XT875"
Serial Number String: 4 "0A3BAA470C01100C"
Interfaces show as: Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Device Qualifier Descriptor
Descriptor Version Number: 0x0200
Device Class 0 (Composite)
Device Subclass 0
Device Protocol 0
Device MaxPacketSize: 64
Number of Configurations: 1
bReserved: 0
Other Speed Configuration Descriptor
Length (and contents): 69
Number of Interfaces: 2
Configuration Value: 1
Attributes: 0xC0 (self-powered)
MaxPower: 500 ma
Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Same issue
I am trying to root a Bionic running 4.0.4 and it is having the same issue with the ADB driver. Using the same computer and a rooted razr, the ADB drivers show up as soon as it is pluged in. Any help with this matter would be a big help.

Galaxy Mini S3 "sleeps" and cannot recieve msgs/calls

I have a Samsung S3 mini, which I flashed with Kit Kat Cyanogenmod 11.0 from novafusion.pl
Everything in the installation was OK.
However my phone randomly falls "sleep" and cannot recieve msgs or calls. I have to turned Airplane mode on and off, to give it a "shake" and "wake" it up.
These is a report from Logcat, plus the log from yesterday,
Code:
build.board: montblanc
build.bootloader: unknown
build.brand: samsung
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: golden
build.display: cm_golden-userdebug 4.4.4 KTU84Q d39c1e8ca0 test-keys
build.fingerprint: samsung/cm_golden/golden:4.4.4/KTU84Q/d39c1e8ca0:userdebug/test-keys
build.hardware: samsunggolden
build.host: novafusion.pl
build.id: KTU84Q
build.manufacturer: samsung
build.model: GT-I8190
build.product: cm_golden
build.radio: unknown
build.serial: 47900592d6cb30c0
build.tags: test-keys
build.time: 1436279173000
build.type: userdebug
build.user: root
version.codename: REL
version.incremental: d39c1e8ca0
version.release: 4.4.4
version.sdk_int: 19
I can't attach my full log because I'm new on the forum.
This is the top 30 unique lines processed by me in Bash,
Code:
[email protected]:~/Dropbox# cat 2015-07-28-10-25-50.txt | grep " E/" | cut -d "/" -f 2- | sort | uniq -c | sort -rn | head -n 30
166 Drm ( 1669): Failed to open plugin directory /vendor/lib/mediadrm
144 SpannableStringBuilder( 4288): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
118 ActivityThread( 2565): Failed to find provider info for com.google.android.wearable.settings
87 AuthorizationBluetoothService( 2483): Proximity feature is not enabled.
85 ConnectivityService( 2088): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_use_userconfig: open failed: ENOENT (No such file or directory)
85 ConnectivityService( 2088): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_delack_seg: open failed: ENOENT (No such file or directory)
70 audio_a2dp_hw( 1669): adev_set_parameters: ERROR: set param called even when stream out is null
59 WifiNative-wlan0( 2088): doBoolean: disable
57 WifiNative-wlan0( 2088): doBoolean: enable
49 CallDetails( 2409): list is null in setConfUriList
48 ActivityThread(14438): Failed to find provider info for com.google.android.wearable.settings
31 MDM ( 2388): [64] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
31 BluetoothPhoneService( 2409): Could not get a handle on Connection object for the call
30 MDM ( 2388): [89] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
26 MDM ( 2388): [67] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
25 LocationReceiver( 6879): Received bad location: null
17 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x414b3f80 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
16 SpannableStringBuilder(25691): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
15 YSNP_TAG( 5072): [NetworkHelper] : [thread:1]checkNetworkChange() - no active network!
14 bp ( 2374): onStartInput event aborted: com.touchtype.keyboard.c.ag: could not obtain extracted text (class com.touchtype.keyboard.c.ag)
13 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x411acd98 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
11 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x4161b3a0 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x419f8f40
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x416a0f08
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x41490f68
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x412c9f58
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x412c8f48
8 VFM ( 1669): ! getSupportedVideoSettings RETURN_XXX_IF_WRONG, condition=(index<mNbVideoSettingsSupported[nPortIndex]), error=-2147479538(0x8000100e)(OMX_ErrorNoMore) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:407
8 VFM ( 1669): ! getSupportedProfileLevel RETURN_XXX_IF_WRONG, condition=(index<mNbProfileLevelSupported), error=-2147479538(0x8000100e)(OMX_ErrorNoMore) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:379
8 VFM ( 1669): ! getParameter RETURN_OMX_ERROR_IF_ERROR, condition=pParam->getIndexParamVideoProfileLevelQuerySupported(pt), error=-2147479538(0x8000100e)(_error) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:140
carlosalomar said:
I have a Samsung S3 mini, which I flashed with Kit Kat Cyanogenmod 11.0 from novafusion.pl
Everything in the installation was OK.
However my phone randomly falls "sleep" and cannot recieve msgs or calls. I have to turned Airplane mode on and off, to give it a "shake" and "wake" it up.
These is a report from Logcat, plus the log from yesterday,
I can't attach my full log because I'm new on the forum.
This is the top 30 unique lines processed by me in Bash
Click to expand...
Click to collapse
Hi, you might get better results asking in your specific device help forum.
http://forum.xda-developers.com/galaxy-s3-mini/help
Good luck!

Categories

Resources