Has anyone successfully used synCE with the hermes over USB?
I am using Ubuntu Feisty and Hermes with the schaps WM6 rom.
Has anyone done a similar sync? If so, how?
Uff!
Tried, tried, tried ... but no luck.
When I had Windows Mobile 2003 synce was good with W2002. Now I have WM6 and synce goes good with W2003.
I'll wait
Just be patient. Unlike winblows software its open source so it has a bunch of people working on it. The last time I checked they were working on it now. Probably should be ready in the next release. What I wish is that I could find a version of linux to run on the 8525. Familiar doesn't support it yet... :'(
nomb
kamatsu said:
Has anyone done a similar sync? If so, how?
Click to expand...
Click to collapse
I just posted how I'm doing it yesterday.
http://forum.xda-developers.com/showpost.php?p=1550906&postcount=4
xor_ said:
I just posted how I'm doing it yesterday.
http://forum.xda-developers.com/showpost.php?p=1550906&postcount=4
Click to expand...
Click to collapse
I am pretty new at this and just can't get this thing connected to Ubuntu. On a Cingular 8525 with Black X (RC) ROM.
On Linux I have Gusty and I can see the 8525 in several ways, but I cannot do anything like transfer. Can someone point me in the right direction please?
Using Bluetooth Manager I can see the 8525 when I browse, but I can't connect without error.
Code:
Couldn't display "obex://[00:17:e4:3c:43:39]".
Check if the service is available.
On a USB connection I get:
Code:
[email protected]:~$ lsusb
Bus 004 Device 025: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
Bus 004 Device 024: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard
Bus 004 Device 023: ID 413c:1002 Dell Computer Corp. Keyboard Hub
Bus 004 Device 022: ID 050d:3201 Belkin Components
Bus 004 Device 016: ID 04a7:0362 Visioneer
Bus 004 Device 013: ID 04f9:0006 Brother Industries, Ltd HL-1240 Laser Printer
Bus 004 Device 014: ID 0424:2524 Standard Microsystems Corp.
Bus 004 Device 012: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 004 Device 005: ID 413c:0058 Dell Computer Corp.
Bus 004 Device 003: ID 413c:0058 Dell Computer Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 006: ID 0bb4:00ce High Tech Computer Corp. mmO2 XDA GSM/GPRS Pocket PC
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 413c:8000 Dell Computer Corp.
Bus 001 Device 001: ID 0000:0000
[email protected]:~$
I have been scouring the net and tried many things but can't get past this point.
TIA,
zeddock
hi
12v powered usb hub, with pocket pc charge and upto 4 device cabled network (or wifi). using smb network share of any plugged in disks, and having a directory set set asside for a print queue and for windows GDI drivers for printers which may be attatched. maybe a cat5 too. useful as a print file station, also with power cable gen of -12 and 5 for supplying disks.
a power efficient mobile office hub. MediaMobileHub.
any ideas??
very very few htc pdas have usb host functionality so they can only use usb for charging and being sync'd with by an usb host like a pc
ideas for min cost max function
things I need to know.
1. does pocket ICS route both ways as this would mean bluetooth and wifi were not needed as standard as a pocket pc could provide this extra connectivity. along with routing of other connected pockets.
2. how standard are GDI driver files.
3. how standard are disk drive enclosure power connectors.
4. active sync between devices would be good, with selection set being done via a cab download. and date criterian.
5. about usb printer scanner combo devices such as this lexmark. the scan button would scan and save to a fixed directory?
6. DVD writer auto do from directory on blank disk?
well more later,
a master hub yes
sorry for the confusion but the intent is the hub is a bus master.
when plugged as a slave into a pc
the hub when plugged as a slave into a pc would export a network interface with smb shares and pretend to be a pocket pc (with set name). this would also act as a routing gateway to any device ICS. so a dhcp server and nat would be needed within the device. this would be far better than exporting multiple usb devices. and sync up all pocket pcs with the one desktop, while keeping the need for desktop power consumption to a minimum. chains of hubs would present possible device naming problems, and so mac addresses would be the logical choice for the merged virtual power pc.
So I upgraded to ICS last night...
This morning when I go to plug my phone into my MHL adapter...
Sound stops coming out of the phone.
No audio/video get routed to the TV.
I am disappoint
Anyone have a fix / run into this?
I'm using the Menotek adapter, does ICS only work with the Samsung adapter?
Did you OTA or oneclick preservedata? Or did you no data.
Grabbed the manual OTA zip in this thread http://forum.xda-developers.com/showthread.php?t=1768479
and then flashed it using stock recovery.
So do I have to wipe my phone to get it working then?
That would really suck.
Is there an app I can just clear data on?
Does anyone else have MHL working on stock ICS?
I don't personally use the MHL adapter, but I remember folks mentioning it wasn't working on the early betas.
it works.. ive used in since early builds on all stock roms and custom roms.. just wont work on a aosp rom yet.. i have a generic brand for like 5$ off amazon.. try another cable/adapter..
Sent from my SPH-D710 using XDA
I don't have another adapter...
But I've used two different HDMI cables, power cables, power adapters, and TV's
The first time I connect it, it beeps and transfers audio (shuts down local phone audio, TV still gets no audio/video... but does get blank signal)
If I disconnect it and plug it in again it reboots the phone
It was working fine yesterday on GB :/
maybe a bad adapter or something.. im on ff18 right now and mine works.. just wierd if it reboots your phone.. do you have any other device to test it with? if it works with another device its your phone.. if it doesnt its your adapter
Sent from my SPH-D710 using XDA
orb360 said:
So I upgraded to ICS last night...
This morning when I go to plug my phone into my MHL adapter...
Sound stops coming out of the phone.
No audio/video get routed to the TV.
I am disappoint
Anyone have a fix / run into this?
I'm using the Menotek adapter, does ICS only work with the Samsung adapter?
Click to expand...
Click to collapse
Can u be more specific on which ics u upgraded to? Aokp aosp cm etc as far as i know don't support hdmi, at least i never got them to work but most of ur stockish ics custom roms will or ate u speaking about the actual ota real sprint stock ics which i can't speak on because i will prolly never run it lol
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
I'm on stock FF18
Sent from my SPH-D710 using xda app-developers app
Best question ever
Did it work on gb
Sent from my SPH-D710 using xda app-developers app
donsh00tmesanta said:
Best question ever
Did it work on gb
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
yes. lol just the early ics leaks and now aosp roms.. but since we have source id hope it gets ironed out.. aosp with mhl support would be awesome.. im tired of flashing back to a tw ics rom to use it but at least theres plenty tw ics roms to choose from
Sent from my SPH-D710 using XDA
It worked on GB just fine a few hours before I flashed ICS.
Here's a log cat of what happens when I plug in:
Code:
1903 I TvoutService_Java TvoutService Action : android.intent.action.HDMI_PLUGGED
1903 I TvoutService_Java TvoutService HDMI : android.intent.action.HDMI_PLUGGED status : true
1761 I Tvout HDMI Cable Connected
1753 D SecTVOutService virtual void android::SecTVOutService::setHdmiStatus(uint32_t) HDMI cable status = 1
1903 V WiredAccessoryObserver Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/hdmi, SEQNUM=1704, ACTION=change, SWITCH_NAME=hdmi}
1903 V WiredAccessoryObserver newState = 16, headsetState = 16,mHeadsetState = 0
1753 E EDIDRead() failed!
1753 I Change mode into DVI
1753 D bool android::SecHdmi::setHdmiOutputMode(int, bool)::calibration mode(0 -> 2)...
1753 E int android::hdmi_resolution_2_std_id(unsigned int, int*, int*, v4l2_std_id*)::unmathced resolution(1080924)
1753 E int android::hdmi_resolution_2_std_id(unsigned int, int*, int*, v4l2_std_id*)::unmathced resolution(7209601)
1753 E int android::hdmi_resolution_2_std_id(unsigned int, int*, int*, v4l2_std_id*)::unmathced resolution(7209501)
1753 E bool android::SecHdmi::setHdmiResolution(unsigned int, bool)::hdmi cannot control this resolution(1080930) fail
1753 I =============== HDMI Audio =============
1753 I ========= HDMI Mode & Color Space =======
1753 I =========== HDMI Rseolution ========
1753 I =========== HDMI 3D Format ========
1753 I =========================================
1753 E tvout_v4l2_start_overlayVIDIOC_OVERLAY failed
1753 E tvout_v4l2_stop_overlayVIDIOC_OVERLAY failed
1753 D PermissionCache checking android.permission.HARDWARE_TEST for uid=1000 => granted (3100 us)
1903 I TvoutService_Java Acquire the lock for Wake status
1903 I TvoutService_Java TvoutSetDefaultString : HDMI not available while application is running. Application will display on phone only
1761 I Tvout TvoutSetDefaultString = HDMI not available while application is running. Application will display on phone only
1903 D PowerManagerService acquireWakeLock flags=0x20000006 tag=TvoutService_Java uid=1000 pid=1903 myUID=1000 myPID=1903 myTID=1922
1903 I DrmManagerClientImpl(Native) DrmManagerClientImpl::processDrmRequest::calling managerservice
1755 I DrmManager(Native) DrmManager::processDrmRequest eneterd
1755 I DrmManager(Native) DrmManager::processDrmRequest::No decrypt session open not need to handle TV out or HDMI
1903 V AudioService Broadcast Receiver: Got ACTION_HDMI_AUDIO_PLUG, state = 1
1903 V WiredAccessoryObserver Intent.ACTION_USB_HEADSET_PLUG: state: 1 name: hdmi
Clearly it doesn't like the resolution or something....
The resolution my TV shows as being displayed by the MHL Adapter is [email protected]
Can anyone with an adapter working on ICS tell me what their reported resolution is?
Another update...
My friend's Galaxy Nexus works on the adapter... So the adapter DOES work.
orb360 said:
It worked on GB just fine a few hours before I flashed ICS.
Here's a log cat of what happens when I plug in:
Code:
1903 I TvoutService_Java TvoutService Action : android.intent.action.HDMI_PLUGGED
1903 I TvoutService_Java TvoutService HDMI : android.intent.action.HDMI_PLUGGED status : true
1761 I Tvout HDMI Cable Connected
1753 D SecTVOutService virtual void android::SecTVOutService::setHdmiStatus(uint32_t) HDMI cable status = 1
1903 V WiredAccessoryObserver Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/hdmi, SEQNUM=1704, ACTION=change, SWITCH_NAME=hdmi}
1903 V WiredAccessoryObserver newState = 16, headsetState = 16,mHeadsetState = 0
1753 E EDIDRead() failed!
1753 I Change mode into DVI
1753 D bool android::SecHdmi::setHdmiOutputMode(int, bool)::calibration mode(0 -> 2)...
1753 E int android::hdmi_resolution_2_std_id(unsigned int, int*, int*, v4l2_std_id*)::unmathced resolution(1080924)
1753 E int android::hdmi_resolution_2_std_id(unsigned int, int*, int*, v4l2_std_id*)::unmathced resolution(7209601)
1753 E int android::hdmi_resolution_2_std_id(unsigned int, int*, int*, v4l2_std_id*)::unmathced resolution(7209501)
1753 E bool android::SecHdmi::setHdmiResolution(unsigned int, bool)::hdmi cannot control this resolution(1080930) fail
1753 I =============== HDMI Audio =============
1753 I ========= HDMI Mode & Color Space =======
1753 I =========== HDMI Rseolution ========
1753 I =========== HDMI 3D Format ========
1753 I =========================================
1753 E tvout_v4l2_start_overlayVIDIOC_OVERLAY failed
1753 E tvout_v4l2_stop_overlayVIDIOC_OVERLAY failed
1753 D PermissionCache checking android.permission.HARDWARE_TEST for uid=1000 => granted (3100 us)
1903 I TvoutService_Java Acquire the lock for Wake status
1903 I TvoutService_Java TvoutSetDefaultString : HDMI not available while application is running. Application will display on phone only
1761 I Tvout TvoutSetDefaultString = HDMI not available while application is running. Application will display on phone only
1903 D PowerManagerService acquireWakeLock flags=0x20000006 tag=TvoutService_Java uid=1000 pid=1903 myUID=1000 myPID=1903 myTID=1922
1903 I DrmManagerClientImpl(Native) DrmManagerClientImpl::processDrmRequest::calling managerservice
1755 I DrmManager(Native) DrmManager::processDrmRequest eneterd
1755 I DrmManager(Native) DrmManager::processDrmRequest::No decrypt session open not need to handle TV out or HDMI
1903 V AudioService Broadcast Receiver: Got ACTION_HDMI_AUDIO_PLUG, state = 1
1903 V WiredAccessoryObserver Intent.ACTION_USB_HEADSET_PLUG: state: 1 name: hdmi
Clearly it doesn't like the resolution or something....
The resolution my TV shows as being displayed by the MHL Adapter is [email protected]
Can anyone with an adapter working on ICS tell me what their reported resolution is?
Click to expand...
Click to collapse
Well, the EDID read that failed is where an HDMI devices queries the display device to find out its capabilities. That seems to have failed so it switched to DVI mode, which is an older standard which supports video but not audio and also doesn't do the encrypted copy protected keys (which I don't know if E4GT using)
Anyway, basically the auto negotiate failed and it dropped into an older compatibility mode, which ironically may not be "compatible" with your HDMI port.
That's just based on reading the log messages. It might not actually reflect reality if some of those log messages are red herrings.
Well that's strange...
I'm not rooted atm, but if I rooted could I wipe the data just related to the tv out apk? I would like to avoid a data wipe if possible...
I will also try using my other TV's AnyNet+ port as well and see if that makes a difference. (I'll get the logs from that too if they differ)
Although with other people having success with ICS and MHL, I may end up having to ODIN and data wipe in order to get it working
orb360 said:
Well that's strange...
I'm not rooted atm, but if I rooted could I wipe the data just related to the tv out apk? I would like to avoid a data wipe if possible...
I will also try using my other TV's AnyNet+ port as well and see if that makes a difference. (I'll get the logs from that too if they differ)
Although with other people having success with ICS and MHL, I may end up having to ODIN and data wipe in order to get it working
Click to expand...
Click to collapse
I think the quickest way is to root and install CWM, make a nandroid backup of your current setup, then do the factory reset and see if it helps, if not, then you can CWM/nandroid restore back to your current setup and pickup where you left off knowing that factory reset didn't help. If it did help you can investigate further.
If you just want to remove the data for TVOut, look for something appropriately names in settings->applications (or whereever it is now in the menu system) and close the app, then clear data and clear cache, then reboot.
ODIN'd FF18 rooted nodata... Exact same log files... I'd rather not wipe the phone :/
I cleared data on all of the Samsung apps on my phone and that didn't help either.
I guess the adapter just doesn't like ICS on my phone.
I'm going to see if I can pick up a Samsung branded one locally and see if that works. Maybe they will let me test it out in-store.
U get that mhl thing going? I'm on my 3rd ff18 and all 3 work.super galaxy 1.5 touched by a s3 and blazer and I'm using a cheapo Chinese mhl. Now if i could just get flippin otg lol
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Not yet :/ Im going to try a different adapter, then wipe completely. If neither of those work im going to see if sprint will exchange my phone.
Sent from my SPH-D710 using xda app-developers app
Has anyone tried to use Google's "Ethernet Adapter for Chromecast" (combined power and OTG Ethernet adapter, 2 meters of cable, Realtek R8152 chipset)?
Averix said:
plugging in the Chromecast ethernet/power combo into the Nexus 5 will charge, but is not recognized as an ethernet network.
Click to expand...
Click to collapse
Sure the Kernel has to support USB Host Mode + External Power at the same time, like Timur's USB host kernel and others do.
But maybe a driver is missing?
the Chromecast kernel includes only one driver (asix.ko / USB_NET_AX8817X), but that supports a large family of ASIX parts (AX88xxx), and is very common today. if you search for "USB AX88179" in Amazon/Newegg/Google/wherever, you should be able to locate something cheap.
Click to expand...
Click to collapse
https://productforums.google.com/forum/#!topic/chromecast/xo_NDh5CZA8
tks teamm....
'Ethernet adapter for Chromecast' uses the Realtek R8152 chipset
The Chromecast kernel includes only one driver (asix.ko / USB_NET_AX8817X)
Click to expand...
Click to collapse
This seems not to be true. The original 'Ethernet adapter for Chromecast' by Google uses the Realtek R8152 chipset says this raspberry user:
https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=131379
Chipset:
Code:
[email protected]:~ $ lsusb
Bus 001 Device 002: ID 0bda:8152 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~ $ lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 480M
Speedtest:
Code:
[email protected]:~ $ iperf -c 192.168.0.62
------------------------------------------------------------
Client connecting to 192.168.0.62, TCP port 5001
TCP window size: 43.8 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.0.60 port 48478 connected with 192.168.0.62 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 112 MBytes 94.2 Mbits/sec
Which N7'13 kernel has the drivers for the Realtek R8152 included? How can I find out?
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=55&Level=5&Conn=4&ProdID=323
The Realtek RTL8152BN-CG 10/100M Ethernet controller combines an IEEE 802.3u compliant Media Access Controller (MAC), USB bus controller, and embedded memory. A linear regulator (LDO) is incorporated for reduced BOM cost.
Click to expand...
Click to collapse
So, it seems this has been added to LineageOS on a device-by-device basis: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_msm8996/+/253772
Double-checking the MAC address owner confirms this is indeed a Realtek chip (not ASIX): https://aruljohn.com/mac/00E04C