Related
Thanks to towa, orinoco,sweeney,JoseF,domloff,blinky99,...
But I still have a problem ...
After the installation of "MyTry2.zip" incl. all reg-mod's i don't receive any data from the gps-module.
The bluetooth-manager recognize my gps correctly in SPP-slavemode, but sometimes it will lost the connection.
In the doggingstation the connection will be lost in 2,5 min.
TomTom224 is proper installed.
But TomTom-gps received no data from holux-gps
After 2,5 min the connection will be lost.
I try it with:
"NMEA 0183v2 Bluetooth" and "BT Serielle Schnittstelle COM7:"
"SIRF Bluetooth" and "BT Serielle Schnittstelle COM7:"
"EMTAC Wireless GPS" and "BT Serielle Schnittstelle COM7:"
"TomTom Wireless GPS" and "BT Serielle Schnittstelle COM7:"
(PPCGPS208 (TomTom) gives a message: "No GPS Engine. Please re-install")
... anyone with an idea?
Thanks ... mtc
I am using a MDA II (german/ T-Online) with a
Holux (www.holux-gps.de) Bluetooth GPS receiver ... Features:
- Built in SiRF Star IIe/LP chipset.
- 12 parallel satellite-tracking channels for fast acquisition and eacquisition.
- High speed signal acquisition using 1920 time/frequency search channels.
- Built-in WAAS/EGNOS Demodulator without additional any hardware.
- Compatible with Bluetooth Serial Port Profile (SPP) completely.
- Built-in rechargeable Lithium-ion battery without external power supply.
- Provide Normal mode and Power saving mode for user’s requirement.
- Provide expand terminal and can contact to other system without bluetooth device.
- Built-in rechargeable battery for memory and RTC backup and for fast Time To First Fix (TTFF).
- Support NMEA0183 v2.2 data protocol or SiRF binary code.
- 4 colors LED to show the status of bluetooth device.
- Support active antenna connector to getting better satellites signal.
- FLASH based program memory. New software revisions upgradeable through serial interface
- Small, sleek, and lightweight design easily fits in your hand
- Water resistant
- Enhanced algorithms -SnapLock and SnapStart provide superior navigation. performance in urban, canyon and foliage environments.
- For Car navigation, Marine navigation, Fleet management, AVL, Personal navigation, Tracking System, and Mapping device application.
Specifications
- Tracks up to 12 satellites.
- Receiver: L1, C/A code
- Snap Start: <3 sec(at < 25 minutes off period).
- Update rate: 1 HZ.
- Acquisition time
- Reacquisition 0.1sec.averaged
- Hot start 8 sec., averaged
- Warm start 38 sec., averaged
- Cold start 45 sec., averaged
- Position accuracy:
- Non DGPS (Differential GPS)
- Position 5-25 m CEP without SA
- Velocity 0.1 m/sec, without SA
- Time 1 usec sync GPS Time
- EGNOS/WAAS/Beacon
Position
< 2.2 m, horizontal 95% of time
< 5 m, vertical 95% of time
- Dynamic Conditions:
- Altitude 18,000 meters
(60,000 feet )max
- Velocity 515 meters / second
(700 knots) max
- Acceleration 4 G, max
- Jerk 20 meters/second, max
- Antenna Type: Built in Patch Antenna
- Minimum signal tracked: -175dBW
- Dimension: 77.9 × 56.9 × 22.8 mm
- Weight : < 70g
- On/off push button
- Lithium-ion battery lasts for more than 9 hours of use
- 4 LED function:
Bluetooth , Navigation Update and Battery and changer status Indication
- Protocol and interface:
- Compatible with Bluetooth devices with Serial Port Profile (SPP)
- Bluetooth™ version 1.1 compliant
- Bluetooth™ Class 2 operation (up to 10 meter range)
- Frequency : 2.400 to 2.480 GHz
- Modulation: FHSS / GFSK
- RF channels: 79
- Input Sensitivity: -80dBm
- Output Level: 4dBm
- Output terminal: Mini-USB (TTL Level)。
- NMEA output protocol: V.2.2
Baud rate: 9600 bps
Data bit: 8
Parity: N
Stop bit: 1
- Output format:
Standard: GGA,GSA,GSV, RMC.
Optional: GLL,VTG, SiRF binary
- Operation Temperature:
-10 to + 60
- Store Temperature:
-20 to + 85
- Operation Humidity:
5% to 95% No condensing.
Can any one please help me.
I'm trying to get my XDA II working with a bluetooth GPS receiver. The XDA II does bond to the bluetooth GPS receiver. However when statring TOMTOM it does not work. I have tried to all the setting and com ports without sucess.
I have been informed that there is currently a bug which the manufacturer is working on.
Could some one please help me.
@mtc
Hi, have you enabel (connect gps? in bluetooth manager?)
Then start tomtom gps?
Let me know.
JoseF
JoseF said:
@mtc
Hi, have you enabel (connect gps? in bluetooth manager?)
Then start tomtom gps?
Let me know.
JoseF
Click to expand...
Click to collapse
Hi Josef,
thx for answering, but i fix the problem!
one wrong reg-value ... (2 hours) :-(
mtc
I am having the same problem
To save me 2 (or more hours) which value was wrong?
Thx
Surur
:idea:
I was told that O2 solved XDA II Bluetooth SPP problem for GPS, source disclosed the Bluetooth GPS tested is EMTAC CRUX II / BTGPS unit.
Hope they will posted the upgrade soon, somewhere. :wink:
In the XDA section of MY-XDA.com:
"Upgrade for the Xda II will be available soon."
Let's hope it's very soon.
surur said:
I am having the same problem
To save me 2 (or more hours) which value was wrong?
Thx
Surur
Click to expand...
Click to collapse
Hi Surur,
... sorry, but i lost this damned piece of paper with the correct value on it.
But ... i remember the wrong value is in HKLM\Software\Widcomm so
i backup my actual registry and reinstall my complete "old" registry entries including the wrong value.
After that i delete the whole entry in HKLM\Software\Widcomm and import again the "widcomm.reg" (MyTry2.zip). --> it's working!!
So if you have the same problem like me, your problem may be solved in
this way.
mtc
mtc said:
surur said:
I am having the same problem
To save me 2 (or more hours) which value was wrong?
Thx
Surur
Click to expand...
Click to collapse
Hi Surur,
... sorry, but i lost this damned piece of paper with the correct value on it.
But ... i remember the wrong value is in HKLM\Software\Widcomm so
i backup my actual registry and reinstall my complete "old" registry entries including the wrong value.
After that i delete the whole entry in HKLM\Software\Widcomm and import again the "widcomm.reg" (MyTry2.zip). --> it's working!!
So if you have the same problem like me, your problem may be solved in
this way.
mtc
Don't forget the soft-reset ... ;-)
Click to expand...
Click to collapse
XDA II TomTom 2.24 and Holux GR 230 Bluetooth GPS -PLS HELP
I have an XDA II and I am unable to use TomTom 2.24 with my Holux GR 230 Bluetooth GPS. I have already done the following:
Upgraded to TomTom GPS 2.09
Installed the Pocket Bluetooth Tools (and created the Bluetooth com port)
Tried various settings in TomTom GPS as there is not a listing for Holux GR 230.
It seems as though the GPS will communicate with the XDA II, and shows that it picks up satalite signals. When I start TomTom Navigator, the Blue GPS light on the receiver flashes to show that it is transferring data, but TomTom Navigator states GPS position unreliable.
PLEASE PLEASE can someone out there help me. If there is a solution, please explain in basic terms / step-by-step as I am far from an expert on PDAs.
Thanks to anyone out there that can help.
Alistair[/b]
Have you taken it for a drive? Many gps systems will take ages to get first fix from new and will take even longer if static, go for a drive and see what happens, it is helpful if you click on the gps/status and see how many sats and how many red lines you have.
cruisin-thru said:
Have you taken it for a drive? Many gps systems will take ages to get first fix from new and will take even longer if static, go for a drive and see what happens, it is helpful if you click on the gps/status and see how many sats and how many red lines you have.
Click to expand...
Click to collapse
Just tried it but still no joy.
Any help appreciated.
Thanks,
Alistair
We've already established that a resistor on the micro USB port can be used to force the Galaxy S into download mode, but the USB switching chip used on the phone has a lot of other capabilities that are triggered by different resistors between pin 4 and 5 of the plug.
Update 6 March 2011: Confirmed modes so far:
Desk Dock: 365K (also works with 1K)
Car Dock: 619K
In these modes audio output can be switched to pins D- and D+ of the USB port (D- is left) but this is not done by default, see this thread.
Serial port/UART: RID_FM_BOOT_OFF_UART (523K)
Read the rest of this thread for more details on using this port.
Other resistor values that also enable the serial port:
RID_AUD_DEV_TY_2 (80.07K): Doesn't switch the phone on, but produces bootlog output on the serial port when you switch it on manually. The bootlog output only starts partway through the second bootloader, rather than from the start of the primary bootloader.
UART_CABLE (150K): Same as RID_AUD_DEV_TY_2
Download mode: 301K (this thread).
Here is a list of all the resistor values, from fsa9480_i2c.h in the open source code for JPM. The resistor goes from pin 4 to pin 5 of the micro USB plug (full details on how to wire this up are in this thread). When you connect the plug with the resistor (in Froyo) you should see some messages from the fsa9480 driver in the kernel log, which you can view with the "dmesg" command.
Code:
RID_USB_OTG_MODE, /* 0 0 0 0 0 GND USB OTG Mode */
RID_AUD_SEND_END_BTN, /* 0 0 0 0 1 2K Audio Send_End Button*/
RID_AUD_REMOTE_S1_BTN, /* 0 0 0 1 0 2.604K Audio Remote S1 Button */
RID_AUD_REMOTE_S2_BTN, /* 0 0 0 1 1 3.208K Audio Remote S2 Button */
RID_AUD_REMOTE_S3_BTN, /* 0 0 1 0 0 4.014K Audio Remote S3 Button */
RID_AUD_REMOTE_S4_BTN, /* 0 0 1 0 1 4.82K Audio Remote S4 Button */
RID_AUD_REMOTE_S5_BTN, /* 0 0 1 1 0 6.03K Audio Remote S5 Button */
RID_AUD_REMOTE_S6_BTN, /* 0 0 1 1 1 8.03K Audio Remote S6 Button */
RID_AUD_REMOTE_S7_BTN, /* 0 1 0 0 0 10.03K Audio Remote S7 Button */
RID_AUD_REMOTE_S8_BTN, /* 0 1 0 0 1 12.03K Audio Remote S8 Button */
RID_AUD_REMOTE_S9_BTN, /* 0 1 0 1 0 14.46K Audio Remote S9 Button */
RID_AUD_REMOTE_S10_BTN, /* 0 1 0 1 1 17.26K Audio Remote S10 Button */
RID_AUD_REMOTE_S11_BTN, /* 0 1 1 0 0 20.5K Audio Remote S11 Button */
RID_AUD_REMOTE_S12_BTN, /* 0 1 1 0 1 24.07K Audio Remote S12 Button */
RID_RESERVED_1, /* 0 1 1 1 0 28.7K Reserved Accessory #1 */
RID_RESERVED_2, /* 0 1 1 1 1 34K Reserved Accessory #2 */
RID_RESERVED_3, /* 1 0 0 0 0 40.2K Reserved Accessory #3 */
RID_RESERVED_4, /* 1 0 0 0 1 49.9K Reserved Accessory #4 */
RID_RESERVED_5, /* 1 0 0 1 0 64.9K Reserved Accessory #5 */
RID_AUD_DEV_TY_2, /* 1 0 0 1 1 80.07K Audio Device Type 2 */
RID_PHONE_PWD_DEV, /* 1 0 1 0 0 102K Phone Powered Device */
RID_TTY_CONVERTER, /* 1 0 1 0 1 121K TTY Converter */
RID_UART_CABLE, /* 1 0 1 1 0 150K UART Cable */
RID_CEA936A_TY_1, /* 1 0 1 1 1 200K CEA936A Type-1 Charger(1) */
RID_FM_BOOT_OFF_USB, /* 1 1 0 0 0 255K Factory Mode Boot OFF-USB */
RID_FM_BOOT_ON_USB, /* 1 1 0 0 1 301K Factory Mode Boot ON-USB */
RID_AUD_VDO_CABLE, /* 1 1 0 1 0 365K Audio/Video Cable */
RID_CEA936A_TY_2, /* 1 1 0 1 1 442K CEA936A Type-2 Charger(1) */
RID_FM_BOOT_OFF_UART, /* 1 1 1 0 0 523K Factory Mode Boot OFF-UART */
RID_FM_BOOT_ON_UART, /* 1 1 1 0 1 619K Factory Mode Boot ON-UART */
RID_AUD_DEV_TY_1_REMOTE, /* 1 1 1 1 0 1000.07K Audio Device Type 1 with Remote(1) */
RID_AUD_DEV_TY_1_SEND = RID_AUD_DEV_TY_1_REMOTE , /* 1 1 1 1 0 1002K Audio Device Type 1 / Only Send-End(2) */
RID_USB_MODE, /* 1 1 1 1 1 Open USB Mode, Dedicated Charger or Accessory Detach */
Great stuff. Thanks man.
I wonder, what is really implemented in I9000.
For example, would it be possible, to make a remote controller for music (something like HTC RC-E100 - i've had it for my Raphael and Hero, and it was great).
Well, when i find some time, i'll try to experiment a bit with that.
Good job.
Makes you wonder why Samsung still hasn't released that damn dock yet.
What about "USB OTG Mode"? : o
How did you get into the Home Dock mode?
Helvio88 said:
How did you get into the Home Dock mode?
Click to expand...
Click to collapse
Both a 1k and a 330R resistor triggered Home Dock mode for me, I see they're not on the list either.
19arek93 said:
What about "USB OTG Mode"? : o
Click to expand...
Click to collapse
USB "On The Go" basically lets you connect two USB devices together with no PC in between and have them talk, assuming both devices support it.
For example maybe you could connect your SGS to a digital camera and copy photos off it. Or connect it to an MP3 player and copy songs.
http://en.wikipedia.org/wiki/USB_On-The-Go
snapper.fishes said:
Good job.
Makes you wonder why Samsung still hasn't released that damn dock yet.
Click to expand...
Click to collapse
They did, but only for America for now (at least it's listed in accessories on Samsung's US website).
TheBeano said:
Both a 1k and a 330R resistor triggered Home Dock mode for me, I see they're not on the list either.
Click to expand...
Click to collapse
Well, 1K didn't work for me. I'll have to find 330R (it won't be easy though, cause i have a lot of mess in tools and electronic parts, after moving to another apartement ).
It is 301K, not 330ohms(=330R) +1K. ...for the download mode I presume you are talking about?
szczeslaw said:
Well, 1K didn't work for me. I'll have to find 330R (it won't be easy though, cause i have a lot of mess in tools and electronic parts, after moving to another apartement ).
Click to expand...
Click to collapse
Check in the dmesg log for something like this:
Code:
<4>[15461.339356] [FSA9480] FSA9480_ReadIntRegister
<4>[15461.389352] [otg_clock_enable] clk_enable(otg_clock) OK.
<4>[15461.402600] [FSA9480] FSA9480_ProcessDevice (dev1 : 0x0, dev2 : 0x40)
<4>[15461.402707] AudioVideo
<4>[15461.402769] FSA9480_enable_spk
<6>[15461.402842] set_dock_state : 0X1
<4>[15461.423626] FSA9480_Enable_SPK --- enable
In fsa9480_i2c.c it is going through the branch where the home dock is plugged in, but the device detected is FSA9480_DEV_TY2_AV, which should be 80K, not 1K? So, more testing needed I think.
Also I have Alarm Clock PlusV2 installed which is the app that was triggered by this action. I did try installing the Samsung Desk Home app but it doesn't work on Froyo.
tonymy01 said:
It is 301K, not 330ohms(=330R) +1K. ...for the download mode I presume you are talking about?
Click to expand...
Click to collapse
No this is for Home Dock mode.
tonymy01 said:
It is 301K, not 330ohms(=330R) +1K. ...for the download mode I presume you are talking about?
Click to expand...
Click to collapse
Well, i know a little bit about electronics (even made some devices, like power amps, devices based on microcontrollers etc.), so i know what 330R and 301K means
I already got download mode working.
And right now i got home dock working to, with 1K resistor. I just didn't know, that one needs an additional app for it to work (i thought it's a system app).
Yeah, sorry for the mix up,i am subscribed to both of the threads related to this recent discovery, and mixed them up. I am certainly interested in triggering particular modes, eg entering car to put phone bluetooth on and screen on dim always, and perhaps a basic home page for gps nav etc, and having an alarm clock mode that maybe turns off data etc. the sky is really the limit here, I can't believe samsumg isn't taking advantage of these features!
Question: has anybody ever actually SEEN a chip inside the I9000 labeled "FSA9480", or is it possible that the "FSA9480" is actually just IP licensed by Samsung and incorporated directly into one of their ASICs?
I ask, because I have an Epic4G. I've scrutinized the various publicized teardown photos of its board, and I have yet to find anything that looks like it might be this chip (which would almost certainly be either MLF or microBGA, 3mm x 4mm or larger, and located somewhere between the main processor and the USB port).
By the same token, does a readily-available (though not necessarily "public", if you know what I mean) datasheet for the Hummingbird and its support chips exist somewhere that documents things like how many UARTs it has, which pins they're connected to, how they're configured (baudrate, parity, mode, stopbits, input & out put registers, interrupts, etc)? As far as I can tell, Android itself has no concept of a UART, and everything in the (official Samsung) kernel that's UART-related was omitted, so there's no documentation in there.
I'm personally psyched about the existence of a UART on this phone, because it opens the door for external peripherals that are a half step above "homebrew" -- things like game controllers, folding keyboards, etc. Stuff you COULD sort of implement via bluetooth (if we ever get a kernel that knows how to do HID), but would literally cost half as much and get twice the battery life if you could skip the bluetooth and just connect via a pair of wires instead.
bitbang3r said:
I ask, because I have an Epic4G. I've scrutinized the various publicized teardown photos of its board, and I have yet to find anything that looks like it might be this chip (which would almost certainly be either MLF or microBGA, 3mm x 4mm or larger, and located somewhere between the main processor and the USB port).
Click to expand...
Click to collapse
It's a 3x4mm UMLP, I haven't seen it described online as anything other than a discrete chip so it probably is on the board somewhere.
By the same token, does a readily-available (though not necessarily "public", if you know what I mean) datasheet for the Hummingbird and its support chips exist somewhere that documents things like how many UARTs it has, which pins they're connected to, how they're configured (baudrate, parity, mode, stopbits, input & out put registers, interrupts, etc)?
Click to expand...
Click to collapse
Yes, google S5PC110_EVT1_UM10 .
As far as I can tell, Android itself has no concept of a UART, and everything in the (official Samsung) kernel that's UART-related was omitted, so there's no documentation in there.
Click to expand...
Click to collapse
There is some UART code e.g. arch/arm/plat-s5pc1xx/dev-uart.c but it may be just for Bluetooth. There are a lot of /dev/ttySn ports, not sure what they do yet.
I'm personally psyched about the existence of a UART on this phone, because it opens the door for external peripherals that are a half step above "homebrew" -- things like game controllers, folding keyboards, etc. Stuff you COULD sort of implement via bluetooth (if we ever get a kernel that knows how to do HID), but would literally cost half as much and get twice the battery life if you could skip the bluetooth and just connect via a pair of wires instead.
Click to expand...
Click to collapse
The Froyo kernel does HID via Bluetooth OK, except for the Wii controller which is a not-very-conforming Bluetooth device. If the Galaxy supports USB OTG, and there is at least some detection and setup code for that, it would probably be easier to use that for wired peripherals.
does anybody know what "Factory Mode Boot OFF-USB" does?
The FSA9480 on Aries platform phones does not have any "clear text" etched on it.
It is located under the RF shield (same side with the baseband chip).
The chip is so tiny that it is necessary to have a scope to see the text printed on it. I found no hits with the code printed on the chip (cannot remember what was it).
The component location on Aries platform phones is U301 (schematics).
Richthofen said:
The component location on Aries platform phones is U301 (schematics).
Click to expand...
Click to collapse
Richthofen, does this mean you have access to the schematics? If so what is connected to pins 6 and 7 (TxD and RxD) of the FSA9480, and also pins 1-3 (Audio + Mic)? Thanks.
The schematics do not specify the pin numbers, but atleast video and mic of FSA9480 are left NC.
Thanks! So CP_D+/- are USB from the Call Processor, and AP_D+/- are USB from the Application Processor, and the IF_TXD/RXD are switched to UARTs on either the call processor or the app processor by another chip, is that correct? I'm looking at the GT-S8500 service manual which uses the same signal names.
Do you have the big block diagram for the I9000 please, that would be really useful? I would especially like to know where the BOOT_MODE and JIG signals go, and which UART on the CPU the IF_TXD/RXD gets switched to, and what does the switching. Also where VPS_L and VPS_R are coming from. Ta.
(Samsung GT-P3110 Galaxy Tab 2 7.0")
Recently the tab stopped charging while plugged to AC and in use...
Ok, it's not losing power as fast as when unplugged, but almost!
I have to turn it off and AC charge for hours and hours as the phone seem to think that it's connected to a PC all of a sudden!
Wasn't an issue up until last week then for no apparent reason it says "not charging" in Battery..
After a lot of reading around and confirming that it was not the charger or cable i dug deeper and it seems that USB charging is turned of by default on the Tab 2's except all custom kernels have it turned on and now that's always on!
Since the tab wont change charger state from USB to AC then all I'm getting is a slow trickle charge at the same slow pace, and it don't whether I am plugged in to the AC or into the PC!
So i figured hey, it's just a terminal command to force it to switch and that's when i realized that, no it's not that easy!
As USB charge is not only the default setting in custom kernels, its the ONLY option available!
The ability to have the tab swiftly reach a full charge while in use seems to currently be impossible with custom kernels it seems!
Is there a work around, or have everyone been to busy implementing USB charging to remember that sometimes you don't want to spend 8+ hours with tab turned off to get a full charge?
Below is a logcat from connecting and disconnecting charger cable to my GTP3110 WHILE connected to an AC adapter!
Code:
Android Tuner (logcat)
======================
V/ 96.627105 c1 17 usb ta_nconnected_irq : VBUS ON
V/ 96.627899 c1 17 [BAT_MANAGER] Charger Connected
V/ 96.627960 c1 58 musb-hdrc musb-hdrc: USB/TA Connect
V/ 97.256317 c1 1662 check_charger_type : Charger type is [USB], adc=594
V/ 97.256317 c1 1662 charger_detect_work: cable flag : 1, cable_type : 1
V/ 97.256347 c1 1662 smb136-charger 5-004d: smb136_set_charging_state: set charger current USB & Default
V/ 97.262725 c1 1662 cable detect:USB attach, current device = 0x0080
V/ 97.262756 c1 1662 espresso_con_usb_charger_attached, USB_EVENT_VBUS
V/ 97.262756 c1 1662 otg: otgwl_hold
V/ 97.262847 c0 58 musb-hdrc musb-hdrc: VBUS Connect
V/ 97.262908 c0 58 musb-omap2430 musb-omap2430: runtime resume
V/ 97.263061 c0 58 omap4430_phy_set_clk: clock (0 --> 1)
V/ 97.504699 c0 58 omap4430_phy_power : clock 1, power ON
W/ 103.476745 c0 15 smb136-charger 5-004d: smb136_i2c_read: err -6
W/ 103.476806 c0 15 smb136-charger 5-004d: smb136_read_status : I2C read fail addr: 0x35
V/ 103.535827 c0 15 smb136-charger 5-004d: addr : 0x35, data : 0x40, addr : 0x36, data : 0x31
V/ 103.806243 c1 17 usb ta_nconnected_irq : VBUS OFF
V/ 103.806793 c1 17 otg: otgwl_temporary_hold
V/ 103.806793 c0 78 musb-hdrc musb-hdrc: VBUS Disconnect
V/ 103.806793 c1 17 [BAT_MANAGER] Charger Disconnect
V/ 103.806823 c0 78 omap4430_phy is : ON
V/ 103.806854 c0 78 omap4430_phy_power : clock 1, power OFF
V/ 103.806854 c1 1662 charger_detect_work: cable flag : 0, cable_type : 0
V/ 103.806854 c1 1662 smb136-charger 5-004d: smb136_set_charging_state: Set discharging default
V/ 103.806884 c0 78 musb-hdrc musb-hdrc: ID float
V/ 103.806884 c0 605 android_work: did not send uevent (0 0 (null))
V/ 103.806915 c0 605 otg espresso_otg_work(920)
current device 0080
V/ 103.806915 c0 605 otg current device is not USB Host.
V/ 103.812805 c1 1662 cable detect:USB detach, current device = 0x0000
V/ 104.002899 c0 658 musb-omap2430 musb-omap2430: runtime suspend
V/ 104.002899 c0 658 omap4430_phy_set_clk: clock (1 --> 0)
I use cyanogenmod, and I'm fairly sure that my tablet charges faster on ac than when plugged into my PC. Have you tried a different kernel/rom?
Sent from my Galaxy S4
What kernel are you on, been trying with 5-6 different ones and they all display that bug that they are incapable in detecting if you are really on AC or USB...
It IS a kernel issue I am 100% sure of that since the Tab has USB charging turned off by default exactly to avoid this issue...
Hi guys, some days ago i played with a ubuntu port and was at TWRP. The message (no OS installed) came up and i clicked reboot / power off (iam not sure).
Since that i not get the phone booted. I cant go to fastboot or recovery, too.
When i connect the usb cable to pc or wall charger the led turn on/off green.
i also tried making my own fastboot cable when i connect it the led stay green. but i cant get it up.
Someone had an idea what i can try?
thanks in advance
Did you try holding power+vol down? Try holding that for a few seconds, then hold power and see if it turns on at all.
I think power + cam would give you the menu options as well (fastboot, recovery, etc), see if that works.
I tryed all diffrent combinations. it wont come up :/
arrrghhh said:
Did you try holding power+vol down? Try holding that for a few seconds, then hold power and see if it turns on at all.
I think power + cam would give you the menu options as well (fastboot, recovery, etc), see if that works.
Click to expand...
Click to collapse
Power plus volume up and down will give you the menu options for fastboot, recovery, etc...
Try to get into fastboot and rsdlite back to stock if you can't boot into recovery. A bit tedious, but as long as you can get rsdlite to recognize the phone you can always start over
i know this menu but it wont come up. i tryed all this combinations.
huhu1312 said:
i know this menu but it wont come up. i tryed all this combinations.
Click to expand...
Click to collapse
You've tried holding these key combos for 30 sec right?
Maybe 10 sec is more realistic, but still - you need to hold these buttons...
Does the screen even power on? Perhaps the backlight is not coming on...?
i already tryed it for 2 minutes but nothing happend no backlight at all.
but i get a message at windows looking for driver qhsusb_dload.
the led stay green for 30sec. 1sec pause 30sec green. 1sec pause....
if i try a combination to start the phone the led goes on and off every sec
huhu1312 said:
i already tryed it for 2 minutes but nothing happend no backlight at all.
but i get a message at windows looking for driver qhsusb_dload.
the led stay green for 30sec. 1sec pause 30sec green. 1sec pause....
if i try a combination to start the phone the led goes on and off every sec
Click to expand...
Click to collapse
IIRC, qhsusb_dload is qualcomm emergency download mode. On linux if you execute "lsusb" it should recognize something like "...HS-USB QDLoader..."
Usually indicates a bigger problem which could be resolved with chipset (msm8960 in this particular case) specific eMMC flash programmer files (.mbn) (or device specific, not sure if OEMs have a possiblity to alter those). You would need the correct boot images as well. Perhaps with the use of QPST.
There was some article somewhere about unbricking qualcomm devices by dumping full eMMC partition from a working and clean device (full reset, internal storage included) and flashing it with some partitioning tool by doing raw copy. Seems a bit odd but I have no experience with this.
Usually, the PBL (primary bootloader) should store error information which would tell you why it errored, if only there would be an easy way to extract that information from device's memory.
Depending on what you did to the device, which ubuntu image have you tried and what it did, there is a chance that the process messed up you bootloaders (SBL - second stage bootloader).
it get indentified as Qualcomm, Inc on my Linux.
i typed lsusb two times. the second when the phone was unpluged.
huhu1312 said:
it get indentified as Qualcomm, Inc on my Linux.
i typed lsusb two times. the second when the phone was unpluged.
Click to expand...
Click to collapse
Don't recognize the product (f006). Please try
Code:
lsusb -v -d 05c6:f006
Bus 002 Device 049: ID 05c6:f006 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0xf006
bcdDevice 0.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Device Status: 0xa8b0
(Bus Powered)
i bought a new with sim mod.
but would a battery change solve the problem maybe?
Edit: i not get it out (not wanne destroy more). is there glue between the akku and the board?
i watched a video the guy removed the battery like there is nothing. iam not sure now if the guy who made the sim mod maybe put there something.
is it dangerous to try removing the glue with a cutter?
i read in some threads that the green led is a info for empty battery.
so i tryed to start the phone with a full battery.
when the full battery is in the phone the green led not come up. but i not get the phone started. (tryed all combinations)
after removing the battery again the green led is back. also if there is no battery.
I'm seeing multiple kickstarters for "turn your cell phone into a computer" type appliances. Typically a keyboard thing that includes an OTG adapter, an HDMI output, etc... Most /claim/ that you can charge your cell phone while working. They are all overfunded (and shaky, I'm not recommending them)
I've tried many times to use phones / tablets as OTG devices to interface to hardware of different types. Everything from diagnostic tools to robot arms (no really, I'd post links but I'm a newbie here and linking is always suspect; I don't want to be accused of spamming).
One major issue always comes up: You can NOT charge while running OTG on /most/ phones. I've done a lot of research on this, and found a few older phones / tablets that seem to support it. I can't find a /single/ USB C based device that is known to do it. Perhaps it's just not an advertising point? MFGRs don't see most users doing that, so they don't support it?
So what am I asking?
1. Is anyone with a modern phone, especially USB C based, actually using OTG and charging at the same time? Please note: I'm NOT talking about charging the OTG device /from/ the phone, I'm talking about charging the phone while using OTG devices. If you are doing this, please: What phone, what OTG adapter?
2. Is this something people have an interest in doing? Why yes, why no? For me, I don't have any interest in using my cell as a computer, but being able to plug it into equipment and monitor / control operation while not running the battery flat would be great!
3. Is anyone aware of the actual specs, technical issues, reasons for the current state of affairs? I've started a web page to track this issue (again, not linking, not spamming) and would love to hear from anyone with direct knowledge of the technical issues involved. Why doesn't it always work? What specification needs to be met? What future is there for this sort of feature?
Here are the devices I understand DO support it:
RaspBerry Pi
Amazon FireStick
Amazon Kindle Fire 10???
Dell Venue 8 pro
HTC One M9
Lenovo Miix 2 tablet?
Lenovo Yoga Book
Moto G 4?
NuVision Tab 8 (Windows 10) after restart only?
Nvidia Shield K1 table??
OnePlus One
Samsung Galaxy S3
Samsung Galaxy S4
Samsung Galaxy S5
Samsung Galaxy Note 3
Samsung Galaxy Tab A7?
Samsung Galaxy Tab A8.0
Samsung Galaxy Tab S2??
Samsung Galaxy Tab S 10.5?
Samsung Galaxy View
Snes Classic
And here are some that support OTG, but will not charge at the same time:
Amazon Kindle Fire 7
Asus T100TAM
LG Nexus 5
LG Nexus 7
Samsung Galaxy Note 4
Samsung Galaxy S7
Samsung Galaxy S8+
Samsung Galaxy S9
Samsung Galaxy TabPro 10.1
Please do add on your info?
How's the research going? I've been looking for tabs that support USB-OTG and charging when connected to a powered USB hub as I'm planning a car install. Sort of interested in whether the newer tabs like the Samsung Tab S5E support this or not. That would be sweet installed into the dash!
Prostheta said:
How's the research going? I've been looking for tabs that support USB-OTG and charging when connected to a powered USB hub as I'm planning a car install. Sort of interested in whether the newer tabs like the Samsung Tab S5E support this or not. That would be sweet installed into the dash!
Click to expand...
Click to collapse
..
Sent from my SM-S767VL using Tapatalk
I decided to buy a Galaxy Tab A 10.1 2019 (SM-T515) and will report back with findings once I test with a USB C OTG Y cable adapter. It's possible that I may need to fabricate some discrete switch into the tablet's USB to alternate between OTG and charging. Not an ideal state of affairs.
Additionally, I've pondered whether devices with pogo pin dock connectors such as the Samsung Galaxy Tab S5E can charge that way whilst using the USB port for OTG devices. Whilst not strictly meeting the requirement of the list (one USB port charging whilst using OTG) it does present a compelling alternative.
It seems that with USB C, the "standard" includes OTG host charging but called pass through charging, dual role data or something along those lines. I connected my Tab A 10,1 to a Kingston Nucleum non-powered hub via the connected USB C lead, then plugged in a charger to another USB C port. Charging! Pretty much the same works whichever combination of connections is used. It seems the devices negotiate who is the power delivery and at what level. There are some settings in android to set also.
Prostheta said:
It seems that with USB C, the "standard" includes OTG host charging but called pass through charging, dual role data or something along those lines. I connected my Tab A 10,1 to a Kingston Nucleum non-powered hub via the connected USB C lead, then plugged in a charger to another USB C port. Charging! Pretty much the same works whichever combination of connections is used. It seems the devices negotiate who is the power delivery and at what level. There are some settings in android to set also.
Click to expand...
Click to collapse
Yes, but does it charge while also having other external devices such as a USB hard drive connected to the hub(which also requires being powered) at the same time? The USB hard drive receives power from the hub like it should and the device charges simultaneously?
Sent from my SM-S767VL using Tapatalk
I've tested with a USB mouse dongle, and when it arrives, my Meizu DAC pro. So far it seems positive. It does however default to the 5v charging level, but that's fine.
Prostheta said:
I've tested with a USB mouse dongle, and when it arrives, my Meizu DAC pro. So far it seems positive. It does however default to the 5v charging level, but that's fine.
Click to expand...
Click to collapse
Hey did you ever get this working? Does USB-C charge and connect devices simultaneously?
thx
Yes, everything works fine....sometimes. The Kingston Nucleum USB C hub has a 5v supply plugged into a 12v car charger port that has USB PD and QC3.0 options. The tablet is problematic in that once the power to the charger (and hence the hub) is removed after turning the car off, the tablet decides that it'll take over the role of supplying power to the hub which discharges the tablet battery whilst the car is off. Also, the hub doesn't always arrange the attached devices correctly, leaving the USB SSD unmounted and the tablet sat alone charging. I'm unsure what is happening, however I'll blame USB C for being a dumpster fire.
Prostheta said:
Yes, everything works fine....sometimes. The Kingston Nucleum USB C hub has a 5v supply plugged into a 12v car charger port that has USB PD and QC3.0 options. The tablet is problematic in that once the power to the charger (and hence the hub) is removed after turning the car off, the tablet decides that it'll take over the role of supplying power to the hub which discharges the tablet battery whilst the car is off. Also, the hub doesn't always arrange the attached devices correctly, leaving the USB SSD unmounted and the tablet sat alone charging. I'm unsure what is happening, however I'll blame USB C for being a dumpster fire.
Click to expand...
Click to collapse
Thanks, I've been looking for a tablet for car infotainment and gauges/data logging, finally decided on a Lenovo tab 4 8 plus Verizon model, precisely because it had a USB-C 3.0 port, and it is rootable. Then I started reading about the complicated mess that the USB-C standard is. Anyway I'll make a post in the General Discussion>Connected Car forums in a month or so when I get everything connected... work and kids always stand in the way of progress
Is that the place to discuss these things? I've had a lot of difficulty trying to find the best place for this, as most are either too specific or not quite on-topic.
I'm updating all of my comments in various threads on this. I've found that with my specific setup with the Kingston Nucleum hub, there are issues. I'm unsure as to the cause, but hey. Firstly, the tablet needs to be powered up before I turn on the car or at least supply power to the hub. It seems that if this is done the other way around, that is, to power on the car accessories (and hence the hub) then it seems to end up staying as the "device in charge" of the USB network. The tablet charges (slowly) but doesn't mount the USB SSD drive or the USB DAC. If the tablet is powering the hub (in charge, so to speak) then applying power to the hub via the car accessory supply has it working as expected. This does mean that the tablet ends up with a power drain when the car/USB power supply is powered down which isn't ideal. I've gotten into the habit of turning the tablet off when I park for long periods of time, however I need to boot it up to "take charge" of the USB hub network before I can start the car. It's a bit of a bummer.
Prostheta said:
It seems that with USB C, the "standard" includes OTG host charging but called pass through charging, dual role data or something along those lines.
Click to expand...
Click to collapse
Yes, my notebook has an USB-C port and can be charged via USB-C PD pass trough by a USB-C dock (USB hub with LAN). Why the Android Smartphones/Tablets don't do the same?
JamesMNewton said:
3. Is anyone aware of the actual specs, technical issues, reasons for the current state of affairs? I've started a web page to track this issue (again, not linking, not spamming) and would love to hear from anyone with direct knowledge of the technical issues involved. Why doesn't it always work? What specification needs to be met? What future is there for this sort of feature?
Click to expand...
Click to collapse
I found this diagram of a "accessory charger adapter" (USB 2.0 spec, not 3.0+?): https://superuser.com/questions/1124237/windows-tablet-otg-simultaneously-charge/1124354#1124354
JamesMNewton said:
Supports OTG, but will not charge at the same time:
LG Nexus 7
Click to expand...
Click to collapse
Charging+OTG was possible on Nexus 7 2012+2013 using a custom kernel!
Yeah, the Nexus 7 was one of the rarities amongst pre-USB3.0 spec ports that could be manipulated into simultaneous data and charging.
My ongoing concern is with ennumeration; I can get my Tab A10,1 charging through the hub easily. However, to access devices attached to the hub, the tablet needs to be active first and then power applied to the hub. Applying power to the hub first, then starting the tablet leads to charging only. The problem as I see it is the negotiation over host rights on a USB network, and whether re-negotiation or forcing priority is possible. It could be a hardware issue built into the USB-PD negotiation specs, a hardware issue with the tablet or simply a software issue in the tablet. I'm not really wanting to wade into the USB specs since they're notoriously vague and contradictary these days....
Prostheta said:
It does however default to the 5v charging level, but that's fine.
Click to expand...
Click to collapse
I would want to know why? It was the same with the Pixel C, but Notebooks will charge at faster speed via PD pass through.
skally said:
I tried powering the PixelC and it works but not at the same speed as the same charger connected directly. I estimate about 1-1.2A
Click to expand...
Click to collapse
PD charging of a Pixel 1 via pass trough (interesting read on PD negotiations):
"The USB Power Delivery behavior seen when the Plugable USB-C 3-Port Hub is passing through power from Google Pixel's own USB Power Delivery charger is a lot different from what you get when you plug the charger directly into the Google Pixel." https://gtrusted.com/review/how-the...google-pixel-phone-using-usb-power-delivery-2
JamesMNewton said:
You can NOT charge while running OTG on /most/ phones. I've done a lot of research on this, and found a few older phones / tablets that seem to support it. I can't find a /single/ USB C based device that is known to do it. Perhaps it's just not an advertising point? MFGRs don't see most users doing that, so they don't support it?
Click to expand...
Click to collapse
I was able to use the ethernet, PD pass through and USB host feature at the same time with:
1. Samsung Galaxy Tab A 10.5 2018 (Stock ROM)
2. Google Pixel 2 (LineageOS 17.1)
The USB-C standard really has made things easier! I was not able to use the HDMI output because these devices do not support DP alt mode! :-(
"USB C Charger RAVPower 65W Fast Wall Charger, PD3.0 & GaN Tech 2-Port Power Adapter" https://www.amazon.com/Charger-RAVPower-Adapter-Compact-Foldable/dp/B08MWG612F
"Dockteck 4-in-1 USB C Hub with [email protected] HDMI HDR, 100W PD, USB 3.0 and Gigabit Ethernet, Multiport USB Type C Adapter"
Amazon.com: dockteck 4-in-1 USB C Hub with [email protected] HDMI HDR, 100W PD, USB 3.0 and Gigabit Ethernet, Multiport USB Type C Adapter for MacBook/Pro/Air, iMac, XPS, iPad Pro 2020 2018 and More: Computers & Accessories
Amazon.com: dockteck 4-in-1 USB C Hub with [email protected] HDMI HDR, 100W PD, USB 3.0 and Gigabit Ethernet, Multiport USB Type C Adapter for MacBook/Pro/Air, iMac, XPS, iPad Pro 2020 2018 and More: Computers & Accessories
www.amazon.com
USB Device Info
---
Device Path: /dev/bus/usb/001/003
Device Class: Unknown (0x11)
Vendor ID: 2109
Vendor Name (reported): VIA Labs, Inc.
Vendor Name (from DB): not found
Product ID: 8817
Product Name (reported): PD3.0 USB-C Device
Product Name (from DB): not found
Additional Info
Interface #0
Class: Unknown (0x11)
Endpoints: none
---
Device Path: /dev/bus/usb/002/003
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 0bda
Vendor Name (reported): Realtek
Vendor Name (from DB): Realtek Semiconductor Corp.
Product ID: 8153
Product Name (reported): USB 10/100/1000 LAN
Product Name (from DB): not found
Additional Info
Interface #0
Class: Vendor Specific (0xff)
Endpoint: #0
Address : 0x81 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 1024
Attributes : 00000010
Endpoint: #1
Address : 0x02 (00000010)
Number : 2
Direction : Outbound (0x0)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 1024
Attributes : 00000010
Endpoint: #2
Address : 0x83 (10000011)
Number : 3
Direction : Inbound (0x80)
Type : Interrupt (0x3)
Poll Interval : 8
Max Packet Size: 2
Attributes : 00000011
Interface #1
Class: Communication Device (0x2)
Endpoint: #0
Address : 0x83 (10000011)
Number : 3
Direction : Inbound (0x80)
Type : Interrupt (0x3)
Poll Interval : 8
Max Packet Size: 16
Attributes : 00000011
Interface #2
Class: Communication Device Class (CDC) (0xa)
Endpoints: none
Interface #3
Class: Communication Device Class (CDC) (0xa)
Endpoint: #0
Address : 0x81 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 1024
Attributes : 00000010
Endpoint: #1
Address : 0x02 (00000010)
Number : 2
Direction : Outbound (0x0)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 1024
Attributes : 00000010
---
Device Info
Device Path: /dev/bus/usb/002/004
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 05e3
Vendor Name (reported): Generic
Vendor Name (from DB): Genesys Logic, Inc.
Product ID: 0749
Product Name (reported): USB3.0 Card Reader
Product Name (from DB): not found
Additional Info
Interface #0
Class: Mass Storage Device (0x8)
Endpoint: #0
Address : 0x81 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 1024
Attributes : 00000010
Endpoint: #1
Address : 0x02 (00000010)
Number : 2
Direction : Outbound (0x0)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 1024
Attributes : 00000010
---
SGH-i200 said:
"Charging+OTG was possible on Nexus 7 2012+2013 using a custom kernel! "
Click to expand...
Click to collapse
Actually You don't need to modify anything with certain tablets to do otg and charging at the same time:
I bought a Lenovo tab 8 hd and only by using a so called "charging y cable" (please Google it) I was able to listen music through my USB dac and charge the tab simultaneously.
Maybe getting into developer mode helped? I don't know, but it's so easy to try...
Daniel