Database Info

[Q] [Q / Dev / USB] Unable to claim interface (official ICS)

Hello. That's a vague question :
I have a custom USB device (class 0xff) and I want to communicate with it using my Android phone. I'm on ICS "stock" (original), and official API provides USB functionnalites.
I use a Java and C API to communicate with my device from my computer (libusb), so I though that it could be possible to do the same with my Androphone, and an OTG USB cable.
But my problem : When I plug the device to the Smartphone, it is correctly detected (and powered). Endpoints are correctly listed, and I can retrieve the serial name. But when I call the "claimInterface" function (Android API), it fails. I don't understand why, because the class of my device is unspecified and shouldn't be handled by Android OS or other App.
When I do a diagnostic with the XDA USB Host test software, I get "yes" in line "claimed" (Base API).
I realize that my question is too specific. My hope is to find someone who has already worked on this kind of problem, or who knows the limits of the USB host.
Thanks in advance.
(My phone is not rooted)

EDIT : Rooted. Same problem :/

[Q] Kernel module for ethernet SMC2208 adapter

I have an Ethernet SMC 2208 adapter which does not work with shield out of the box. I have my shield updated to lollipop. Upon insertion I can see that the device is recognized by the system in the sense that there are messages in dmesg stating that it is "Procduct SMCSMC2208USB". After that there are some messages mentioning "audit" and "avc: denied". In contrast on my Nexus 5 (also lollipop) the device works correctly, I can see some messages mentioning pegasus driver if I got it correctly. It's a bit hard to provide complete output since I'm running the commands from android terminal and can't easily copy output here. But if that would help I'll grab it somehow.
I was thinking about compiling the module for the device but it not as easy as on regular linux. I found the driver source on that page: "edge-core.com/temp/edm/old_downloads/old_downloads.html" "edge-core.com/temp/edm/old_downloads/dr/DR_SMC2208_LinuxDRV.zip" (because this is my first post I can't insert URLs So I deleted " h t t p : / / w w w ." prefix, sorry for inconvinience)
But I don't know how to compile it for android in general and for my tablet in particular. I would greatly appreciate if someone could compile it for me or point me to steps I need to follow to do it myself.
Thanks in advance for your help

[FIX] Unknown USB device (Device Descriptor Request Failed) Fastboot Windows 10

First of all, I have a HTC Droid DNA. I was searching for about a year. Finally I got a solution for my problem and I know some of you are still out there with no solution.
The Fail Code is: Unknown USB device (Device Descriptor Request Failed)
Windows has stopped this device because it has reported problems. (Code 43)
So I found a German solution where you have to go to regedit.
Step 1: You need to install the HTC drivers (Google, Samsung etc...) in the normal mode your PC will find your phone, but when you turn into Fastboot you get that error "Unknown USB device (Device Descriptor Request Failed) "
Step 2: Make sure you see that error in your Device Manager under USB - Controller
Step 3: Open "regedit"
Step 4: Navigate to : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
Step 5: Create a new Key called
0BB40FF00100
Step 6: In that Key you create a Binary Value
Name: SkipBOSDescriptorQuery
Value: 01 00 00 00 (ignore the "0000" at the beginning)
Step 7: Reconnect the Phone and enjoy your FIX
I hope I helped you. I can just tell you that it worked for me. I m not sure if it works on all HTC devices.

tried it with a S7 right now, didnt work. thanks for your post tho!

Had the solution for windows 8.1, from a blog on microsoft MSDN. (Sorry can't link to it. Since I'm new @ xda)
But as it turned out the Datatype for SkipBOSDescriptorQuery has changed from windows 8.1 to 10. Instead of a DWORD Value in Windows 8.1 it should be a Binary Value in Windows 10 .
So thanks :good: Now I can connect via fastboot to my HTC Incredible S.
Ps. Google this:
why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43
And blogpost will show as top result

Thank you very much the regedit method worked for sure..
I spent 5 hours on my computer and laptop different usb cables different ports installing uninstalling drivers and ADB nothing
Thanks BoBo Rich:good:

Thnx!!

Didn't work for HTC Explorer (Pico)

Worked with the HTC Aria on Win10 x64!
Thanks a ton.
edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100

Has anyone else gotten this to work?
My Pixel XL isn't recognized at all when plugged in while in system, but it shows up as unrecognized when plugged in while in fastboot. But despite installing the drivers, Windows still refuses to recognize the phone. I tried the various solutions in this thread, but none of them worked. Perhaps it's because my Pixel's fastboot hardware ID is different, but I can't seem to find out what it is.

work perfectly for htc one xl (evita). Thanks !!

Thanks
After 48 Hours of searching!! thanks man! HTC ONE S (Ville)

Thanks! I have this problem with my Shield TV Pro, will try this after work.
Here's some PowerShell code for doing the registry editing, if anyone is interested.
Code:
#Requires -RunAsAdministrator
[string] $Path = 'HKLM:\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100'
[string] $Name = 'SkipBOSDescriptorQuery'
if ($false) {
# Create the path if not exist
if (-not(Test-Path -Path $Path)){New-Item -Path $Path -ItemType 'Directory'}
# Set "SkipBOSDescriptorQuery" to $true
Set-ItemProperty -Path $Path -Name $Name -Value 1 -Type 'DWord'
# Set "SkipBOSDescriptorQuery" to $false
Set-ItemProperty -Path $Path -Name $Name -Value 0 -Type 'DWord'
# Remove item
Remove-ItemProperty -Path $Path -Name $Name
# Remove path and item(s)
Remove-Item -Path $Path -Recurse -Force
}
Edit: This did not work for my Shield TV 2015 Pro unfortunately..

The error changes to "Port Reset failed". Error code remains the same 43. In my case I am trying to connect an LG G3 D858HK. I have tried many different cabels but no solution.

Unknown usb device error Motorola

Doesn't work on lg v20... Haven't been able to fix this issue for a while now..

Thanks for the info mate !
The registry key worked just great in my Windows 10 x64 computer at home and at my work laptop.
I have a Huawei P9 mobile Device.
Had this issue and nothing i tried seemed to work.
Your key did.
Thanks again !!!:good::good:

V20 Method prior to attempt....
@texas### whos still having trouble with a V20 stuck in the firmware screen ( like me) and I have a theory so I'm posting this prior to attempting it but someone please let me know if I have this wrong.
I read this post on the first page of the thread by someone whos name I've forgotten now (sorry) but they wrote....
--------------- edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100 -----------------------
and based on this --- my V20 hardware ID reads "USB\VID_0000&PID_0002\5&2BF451F8&0&2" or rather the instance path does and using this I should be able to correct the value of the binary string to fit this corresponding ID for the VVVVPPPPRRRR correct? so value will be "0000000252BF451f02" ????
Im making the key and binary value now and I'll repost results later
I'm so invested in this phone both in time and sheer ignorance of what else I can do to get this damn thing out of the firmware screen.
* I've tried loading the "LG drivers from both LG composite device and VZW versions" to no avail.
*On a side note, tapping the power button brings up a "download mode" sub screen where is searches for wifi connections and after finding mine I went ahead and tried to connect 1- normally 2- removing my wifi password 3- using the WPS button to connect, all of which ended in "connection failed" so can someone explain the actual purpose of this option if there is no way to connect? or am I finding the wrong signal so to speak>?
Thanks
I'll gladly post all of my results or screen shots, (all failed so far) using ADB, uppercut, LGUP, odin, placing TOT files on the SD card, plus a few absolutely embarrassing methods but had to try something.
Please tell me someone knows a way out of this

Otherwise start a *.bat file containing
Code:
REG ADD HKLM\SYSTEM\CurrentControlSet\Control\UsbFlags\0BB40FF00100 /v SkipBOSDescriptorQuery /t REG_BINARY /d 01000000 /f
or use this in the Run window that you can call by pressing the Windows button and R, Win+R.

DEAD
Hi
Hope there's still anyone here that could help. I got the same error {The Fail Code is: Unknown USB device (Device Descriptor Request Failed) Windows has stopped this device because it has reported problems. (Code 43)} that appears on windows when watch is connected and i press the red button. I tried to get the identifier via device manager and microsoft message analyzer but it is not detected. What else can i do?
Thanks!

didnt work for the V40. anyone got any ideas?

SuperMike393 said:
didnt work for the V40. anyone got any ideas?
Click to expand...
Click to collapse
Have you tried going to device manager > universal bus controllers, right click USB Root Hub and unintall. Restart the PPC/Laptop and reconnect the device. It works on both Xiaomi and other brands as well.

[Resolved] OnePlus One + NetHunter - no power on otg AND LKM support issue

Hello everybody! Noobing the shoozle out of my:
OnePlus One, model A0001 / 64GB currently with: Android 6.0.1 / Cyanogen OS version: 13.1.2-ZNH2KAS3P0-bacon / CyanogenMod API level: Elderberry(5) (just FYI, not sure if helpful)
Kernel version: 3.4.112-cyanogenmod-g8fbc62e
Unlocked, rooted with BaconRootToolkit/ TWRP ROM, downloaded latest ver -3.0.2-0 via official App, from Play Store
Kali images from: build.nethunter.com/nightly, as offensive-security's kali-nethunter wiki on github says (no external links for noobs, sorry )
apt-get updated, upgraded and dist-upgraded via KALI terminal
The first issue is with the OTG, not powering the USB WiFi adapter properly... with the regular USB-OTG adapter, lsusb WORKS, and returns proper info about 3 different adapters (Alfa Awus036h, TP-link WN725N and WN722N), BUT does not power them. No indicator lights get lit whatsoever 0mA status from lsusb -v
I bought a powered USB-OTG hub, that appears to not charge my phone, when plugged in two different chargers AND a powerbank. Still lsusb -v returns: 100mA current for the hub.
I tried plugging an A4Tech receiver for kbd+mouse, both work fine, with the tplink WN725N plugged in the second USB socket. lsusb shows the hub, the receiver and the WN725N data... Both regular and hub OTG's work fine with mouse+kbd, read and write data to USB Memsticks. Regular OTG transfers files to a computer and charges the phone.
I noticed that when in Android, the WiFi is turned off, ifconfig omits wlan0 and p2p0, that is the phone's main WiFi adapter.
So I thought that manually loading (insmod) the rtl drivers would start the OTG wlan.... Thus coming to the second issue:
The kernel is without LKM support - no modprobe, lsmod returns:
Code:
libkmod: ERROR: ../libkmod/libkmod-module.c: 1655 kmod_module_new_from_loaded: could not open /proc/modules: no such file or directory
Error: could not get list of modules: No such file or directory
When "apt-get install linux-headers-$(uname -r)" is typed, returns:
Code:
E: Unable to locate package 'linux-headers-3.4.112-cyanogenmod-g8fbc62e'
E: Couldn't find any package by glob 'linux-headers-3.4.112-cyanogenmod-g8fbc62e'
E: Couldn't find any package by regex 'linux-headers-3.4.112-cyanogenmod-g8fbc62e'
"apt-cache search linux-headers" returns some options for version linux-headers-4.9.0-kali1-all-armhf (the only armHF, others are armmp)
I cannot find a way to recompile my kernel and enable Loadable Kernel Modules support. Would you say this would be necessary for the external WiFi to work?
Do you know if there is any way out of this mess, as I am really tired fighting a "Our preferred device"-release issues??? Overall I'd love it if I could run external antenna
I am kind of new around.... In forums - in general, so I kindly ask for understanding. If any screenshots/pics/additional info is required - I'll make sure I update this thread. Not sure if I could've posted this thread in XDA assist, so I did it here.
EDIT: everything went fine when I tried third, different USB - WiFi adapter. Works properly. Still no LKMs.

PostmarketOS

Hello, physical keyboard geeks!
I've added basic support for the galaxy s relay to the postmarketos project. You can now build a new kernel with a modern compiler that will boot on our sliders. Tested: Boot, usb ethernet, flashing with heimdall, nothing else.
Something like this might work to install:
apt-get install -y python3
Clone the repo and cd into it.
git clone https://gitlab.com/postmarketOS/pmbootstrap.git
cd pmbootstrap
Start the install wizard
./pmbootstrap.py init
Chose samsung-apexq for device and use the xfce4 gui. (unsure if graphics will work, but if it does it's the one you want)
./pmbootstrap.py install --android-recovery-zip --no-fde
Now export the zip file
./pmbootstrap.py export
It should give you a path to a zip you can flash with CWM or TWRP. If that doesn't work, then run install without --android-recovery-zip and try flashing with the heimdall wrapper like this:
./pmbootstrap.py flasher flash_rootfs
./pmbootstrap.py flasher flash_kernel
(Obviously, make sure you have a good usb data cable and not just a charge only cable, oh and make sure you have backups of your favorite android rom so you can go back to android).
Go forth and test! My dev phone's screen died so now it's up to YOU! File bugs in the postmarketos gitlab project issues. Complaints, insults about my mother, and general snark are welcome here. If you have a problem, I'm happy to ignore you while you figure it out, so don't be shy!

Here's a flashable zip: https://gitlab.com/5ilver/apexq/blob/master/20190329-pmos-samsung-apexq.zip
I can't test it (no working screen), but the root/boot heimdall flash version is working for me via download mode at least far enough to ssh into the phone and poke around.

Hi i managed to follow your Steps.
Thanks for that wonderfull Howto.
Installed FatToad on my regular Phone and PostmarketOS from you on my Spare t-699.
Your Display is broken?..how is that happend?
Managed to make a flashable CWM Zip and i did not go further than the PostmarketOS Screen.
ADB is not working and now after use Install via Fastboot..it stay postmarketscreen.
I let it stay the next 10 Minutes on this..maybe something usable come out
btw:
Do you come from Germany?
Maybe i can Donate you with my Spare T-699?
Many Thanks for your work..a second Post from me will come when i am little further.
And i had to laugh loud in the Moment where i saw that i can use simply the git Software Downloader for Gitlab too..and i thought i need a special Gitlab Software :good:
Thanks for teaching me this

ingoreis said:
Hi i managed to follow your Steps.
Thanks for that wonderfull Howto.
Installed FatToad on my regular Phone and PostmarketOS from you on my Spare t-699.
Your Display is broken?..how is that happend?
Managed to make a flashable CWM Zip and i did not go further than the PostmarketOS Screen.
ADB is not working and now after use Install via Fastboot..it stay postmarketscreen.
I let it stay the next 10 Minutes on this..maybe something usable come out
btw:
Do you come from Germany?
Maybe i can Donate you with my Spare T-699?
Many Thanks for your work..a second Post from me will come when i am little further.
And i had to laugh loud in the Moment where i saw that i can use simply the git Software Downloader for Gitlab too..and i thought i need a special Gitlab Software :good:
Thanks for teaching me this
Click to expand...
Click to collapse
Awesome! This is great to see! I'm in the US, but thanks anyway. Ok so the kernel booted on your phone. This is cool. Now the next steps are to get X working so we can use the screen and run programs. If the phone is connected to your computer with a usb cable, it should identify itself as a usb ethernet adapter that you can get a dhcp address from. Something like sudo dhclient -v enp0s19f2u1 and then ssh [email protected] should allow you to access the phone. The errors are in /var/log/Xorg.log.0 I think. Need to get that dumped and give it a good hard look, maybe enable some fallback display mode or something. Need to probe around in /dev/input too and see what sort of input devices are detected. This is good progress though. We're getting the phone back into a supportable state.
Not sure how my display broke. One day it was just blank when I tried to wake it, but it worked after a few tries. It got harder and harder to use with the keyboard out, and so I got another one. When I started working on this port the screen had to be held very still or it would blank out. Now, it just won't come on at all. It is possibly a bad flex cable.

silvermagnet said:
If the phone is connected to your computer with a usb cable, it should identify itself as a usb ethernet adapter that you can get a dhcp address from. Something like sudo dhclient -v enp0s19f2u1 and then ssh [email protected] should allow you to access the phone.
Click to expand...
Click to collapse
had this Error in my Linux:
Code:
[email protected]:~/Downloads$ sudo dhclient -v enp0s20f0u10
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on Socket/fallback
DHCPREQUEST of 172.16.42.2 on enp0s20f0u10 to 255.255.255.255 port 67 (xid=0x2be8f493)
DHCPACK of 172.16.42.2 from 172.16.42.1
RTNETLINK answers: File exists
bound to 172.16.42.2 -- renewal in 395804 seconds.
[email protected]:~/Downloads$ ssh [email protected]
ssh: connect to host 172.16.42.1 port 22: Connection refused
[email protected]:~/Downloads$
Unfortunaly Connection Refused @ Port 22
But you are right..Kernel seem to boot fine and it is a "NetworkDevice"
Phew Ameria is on the other Side of the World from here..thanks again for help to get it work.
Btw i saw an Android Device in my File Explorer from Linux but it cannot be mounted via MTP.
Edit:
I can connect but need a Password

ingoreis said:
had this Error in my Linux:
Code:
pando[email protected]:~/Downloads$ sudo dhclient -v enp0s20f0u10
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on LPF/enp0s20f0u10/62:3d:43:73:74:09
Sending on Socket/fallback
DHCPREQUEST of 172.16.42.2 on enp0s20f0u10 to 255.255.255.255 port 67 (xid=0x2be8f493)
DHCPACK of 172.16.42.2 from 172.16.42.1
RTNETLINK answers: File exists
bound to 172.16.42.2 -- renewal in 395804 seconds.
[email protected]:~/Downloads$ ssh [email protected]
ssh: connect to host 172.16.42.1 port 22: Connection refused
[email protected]:~/Downloads$
Unfortunaly Connection Refused @ Port 22
But you are right..Kernel seem to boot fine and it is a "NetworkDevice"
Phew Ameria is on the other Side of the World from here..thanks again for help to get it work.
Btw i saw an Android Device in my File Explorer from Linux but it cannot be mounted via MTP.
Edit:
I can connect but need a Password
Click to expand...
Click to collapse
The password is password

silvermagnet said:
The password is password
Click to expand...
Click to collapse
Thank you tried it but did not work.
"ssh [email protected]"
gave me an error
"ssh: connect to host 172.16.42.1 port 22: Connection refused"
and
"ssh [email protected]"
ask for a Password and do not accept "password"
I am near..only this last Step to get the Important Files
Now i tried another USB Port and something is working but not working:
Code:
[ 8406.035731] rndis_host 1-9:1.0 enp0s20f0u9: unregister 'rndis_host' usb-0000:00:14.0-9, RNDIS device
[ 8406.366663] usb 1-9: new high-speed USB device number 34 using xhci_hcd
[ 8406.515928] usb 1-9: New USB device found, idVendor=18d1, idProduct=d001
[ 8406.515934] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8406.515938] usb 1-9: Product: Android
[ 8406.515942] usb 1-9: Manufacturer: Android
[ 8406.515945] usb 1-9: SerialNumber: 0123456789ABCDEF
[ 8406.519381] rndis_host 1-9:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-9, RNDIS device, 66:93:21:86:d9:50
[ 8406.529243] rndis_host 1-9:1.0 enp0s20f0u9: renamed from usb0
[ 8406.555024] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u9: link is not ready
[email protected]:~/Downloads$ sudo dhclient -v enp0s20f0u9
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp0s20f0u9/5a:14:3c:18:78:36
Sending on LPF/enp0s20f0u9/5a:14:3c:18:78:36
Sending on Socket/fallback
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 3 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 5 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 6 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 11 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 13 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 9 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 11 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 20 (xid=0x810a2043)
DHCPDISCOVER on enp0s20f0u9 to 255.255.255.255 port 67 interval 20 (xid=0x810a2043)
but do not stop that

ingoreis said:
Thank you tried it but did not work.
"ssh [email protected]"
gave me an error
"ssh: connect to host 172.16.42.1 port 22: Connection refused"
and
"ssh [email protected]"
ask for a Password and do not accept "password"
I am near..only this last Step to get the Important Files
Click to expand...
Click to collapse
172.16.42.2 is your own computer. Maybe ssh didn't successfully start on the phone. Try restarting it. Don't worry about getting the logs for me, I have a copy from mine. I just need to go through them and find the errors.

Restarting phone did not start ssh but i have an Idea:
gmtp had Errors too because i tried to vonnect with MTP
HTML:
[email protected]:~/Downloads$ gmtp
Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
Device 1 (VID=16c0 and PID=0489) is UNKNOWN in libmtp v1.1.13.
Please report this VID/PID and the device model to the libmtp development team
LIBMTP PANIC: Unable to find interface & endpoints of device
Fehler: Verbindung zu Gerät nicht möglich.
LIBMTP PANIC: Trying to dump the error stack of a NULL device!
LIBMTP PANIC: Trying to clear the error stack of a NULL device!
Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
Device 1 (VID=16c0 and PID=0489) is UNKNOWN in libmtp v1.1.13.
Please report this VID/PID and the device model to the libmtp development team
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
Fehler: connection not possible.

Edit:
I have the Connection now
EditEdit:
Here is the Log that you want inside the Attachments:
EditEditEdit:
Fixed the Logfile..last Part was missing

Hey this is great! I still take out my Relay "for a spin" occasionally, so I'm thinking of testing this.
I'm guessing the .zip is flashable withTWRP, not CWM?
I don't have any dev tools and I'm running Win10 (been ages since I've had a running Linux rig), so I'm not sure how much feedback I can provide. Should I wait until the build is a little more stable?

cucumbers said:
Hey this is great! I still take out my Relay "for a spin" occasionally, so I'm thinking of testing this.
I'm guessing the .zip is flashable withTWRP, not CWM?
I don't have any dev tools and I'm running Win10 (been ages since I've had a running Linux rig), so I'm not sure how much feedback I can provide. Should I wait until the build is a little more stable?
Click to expand...
Click to collapse
It should work in either recovery, or at least the documentation I've seen so far does not specify. You shouldn't need any tools, just put the image I linked from gitlab on an sd card. Stability... well things are quite stable in their current very broken state. I ran my phone for almost a week straight, so no worries there. Getting X working is probably the next big step. It will likely be a while. The frame buffer driver doesn't seem to be giving very useful errors but I'm sure someone has bumped into the same problems on another phone, so we'll get there.

i tried little with startx xinit and others
and it seem to need xterm but xterm is not installed
(see the attached Picture)
I tried to change the Config from Display 0 to Display 1 but no success
and no Screen on the Relay for now.
And a little good Information:
Touchscreen is working.
When i touch the Display i see touched Coordinates in dmesg
Sometimes i had the Message that Xserver is already running on Display 0
but after trying some Things not more.

Starting X over ssh probably will not work since your local term is not graphical. I tried putting a default screen section in the xorg config, but that didn't make the X service work. I've read that disabling 3d accel for the msm chipset in the kernel can help so I'll try that next.

No luck with disabling MSM_KGSL, seems to have the same stream of errors followed by a segfault in the X log. I also tried including an additional package xf86-video-fbdev which had no effect either (I think it must have already been pulled in by a dependency). The msm-fb-refresher package appears in the similar looking samsung-jflte APKBUILD, so I'll try that later today.
Maybe the weston graphical environment is worth a try instead of X? Seems some other msm based phones like it.

silvermagnet said:
No luck with disabling MSM_KGSL, seems to have the same stream of errors followed by a segfault in the X log. I also tried including an additional package xf86-video-fbdev which had no effect either (I think it must have already been pulled in by a dependency). The msm-fb-refresher package appears in the similar looking samsung-jflte APKBUILD, so I'll try that later today.
Maybe the weston graphical environment is worth a try instead of X? Seems some other msm based phones like it.
Click to expand...
Click to collapse
About that i have no Knowledge but thanks that you try so much

any News?

I dropped my phone, got a dead spot in the camera, got another relay on ebay, and here we are with a perfectly good dev phone with a good screen. So I can hack on the display now. X11 is broken, but weston works fine. No update on last time, just select weston instead of xfce4 in pmbootstrap init. I'll get hackin on the 'red' problem, which from what I gather is pretty common and easily patchable.
https://i.imgur.com/vy18cjJ.jpg

Wow Great News,thank you for still working on it.
When you send me your Paypal Adress via PM then i want to donate little Bit for you because you bought another T-699 over Ebay for us all.
This Picture look good and this "Red Error" is little bit funny and
i am glad to see Weston is working.
Touchscreen worked good?

The touch screen worked great. The keyboard even works too! Some small gotchas, like numeric symbols being selected with shift instead of alt, but it works!
https://i.imgur.com/lE3x4OK.jpg