Been an Iphone user from day one and pretty much know the ins and outs of everything iphone but next to nothing about Android smartphones, so before I take the plunge and get a Galaxy S, I have a few questions that only XDA guys can fully answer.
1.Can the Galaxy S smoothly play 720P MKV's (via the 3.5mm TV out) and can it show embeded subtitles?
2.Does the media player have slowmo (FF/RW) options?
3.Can the Galaxy S capture screen shots (like the iphone home & power button screen grab ability) ?
4.Which Sat Nav software is highly recommended (I'm using NDrive on the iphone which only cost less than £5 when it was available on the app store) ?
Bottom line, The iphone has too many media restrictions, so I'm hoping the galaxy s will be a full portable media device.
Thanks
Anyone ?
Oh, is it able to play MKV's with DTS audio (does it down downmix) ?
1. yes, no, no, need another player software
2. same as above
3. yes, use the shakey shakey app to capture, very easy
4. i like CoPilot, other likes IGo, there are many many more to chose from, there are even open source freewares
Are you saying it can't output 720p mkv's to an external display via the 3.5mm output plug?
The adapter that lets you output video through the 3.5mm headphone jack is a standard composite RCA cable (red, yellow, white). This type of A/V connection is not HD capable and can only output NTSC or PAL (basically 480i res) to an SD television. If you want to do HD out you need to use DLNA to wirelessly stream the video to a supported player (or the just announced Samsung DLNA streaming accessory) or use the microusb-hdmi adapter that has been announced.
Micro USB to HDMI For 720p output.
I understand it can't output 720p res via the 3.5mm but will it output a lower res composite mirror video if it's playing a 720p MKV ?
RE the sat nav.... All android phones have free turn by turn nav using Google Navigation.. Its one of androids best features.
Yes you need data but who gets a smartphone without data?
Sent from my GT-I9000M using XDA App
I've found "over the air" sat nav is never as fast as having a program with maps already stored on an SD card.
Is there an affordable app (like NDrive) that doesn't cost an arm and a leg over it's iphone equivalent but really shows off the capability of the Galaxy S?
Thing is, I'm coming over to Android from an iphone background but find that Android users are asked to pay over the odds for equivalent iphone apps.
there are a few open source ones (that uses downloaded maps), forgot the names
personally i prefer CoPilot for Android, it's the best one out there at the moment
forcedv said:
I've found "over the air" sat nav is never as fast as having a program with maps already stored on an SD card.
Is there an affordable app (like NDrive) that doesn't cost an arm and a leg over it's iphone equivalent but really shows off the capability of the Galaxy S?
Thing is, I'm coming over to Android from an iphone background but find that Android users are asked to pay over the odds for equivalent iphone apps.
Click to expand...
Click to collapse
I dunno what you've tried it with but google nav flies. It also dls everything it needs for the trip you set at the beginning of the trip so that it's not pulling it while you're driving. This improves speed and also keeps the nav working if you go out of service mid trip. However, google nav/maps always flies on 3g for me so you shouldn't be concerned. I also found that a lot of equiv apps are actually cheaper on android, not more expensive.
forcedv said:
I've found "over the air" sat nav is never as fast as having a program with maps already stored on an SD card.
.
Click to expand...
Click to collapse
Not sure what you mean by "As fast as". With 3G i have never had google maps not keep up with my driving.
I used to have a Tomtom and ditched it when I got this. Useless to me now.
Lets make a thread to Show Microsoft we want a Windows Mobile 7 Phone, which operates in Windowed mode, like Windows mobile 6, and comes with a Microsoft-made or HTC-made custom phone specifically for the Windows Moblie 7 Platform
talk about what it might include, what features we'd like, etc..
The Windows Mobile 7 OS would operate similarly to Windows 7 on Desktop PCs, basically a slightly modified version of Windows 7 with flick-panning ability & touch zooming
The Hardware Configuration on the phone should be:
- Quad-core 2Ghz CPU
- 256-512 MB GPU
- 2GB RAM
- 1280x768 4" or 5" Screen Resolution.. 1080p is preferred
- My Display Port (MyDP) with cables & converters included
- 64 GB internal Memory as a Dedicated C:\ Drive
- Dual or Quad Internal (Under the back case) Micro SD Card slots, to hold 2 to 4 Micro SDs which function as removable Disk Drives
- Dual External Micro SD Card Slots, which function as Portable Disk Drives or removable USB Drives
- Each SD Card Slot is Dedicated D:\, E:\, F:\, G:\, H:\, I:\ etc..
- Minimum of 12 external hardware buttons
- Internally Retractable Cable-Attached Full-width telescoping Stylus with 2 hardware buttons and a scroll dial..
- Native Bluetooth External AAA battery-operated Mini Mouse & Foldable Keyboard
- Able to boot any OS, with each separate OS able to boot from each SD card Slot
- Bios Set up for setting default Boot Drive, Memory Settings, etc
- Ability to run x86 Windows 7 Programs..
- Ability to zoom out to full desktop view, eventhough it be small.. we dont need to read ever icon text on the desktop, thats what the icons are for..
- Dedicated 3.5 Video-in & Audio Line-In jacks, as well as a standard headphone jack
- Full-sized USB port for attaching peripherals & USB Hubs
- Rugged, water-resistant, & Shock-proof
- Gorilla Glass
- Bluetooth 4
- 4G
- GPS
- 12 Megapixel Camera pureview quality, with Carl Zeiss Lens
- 2 MP front camera
Now add to this list..
or create your own Windows Mobile 7 Dream Phone
The 12 hardware Buttons could switch back & forth between F1-F12 functionality, or to a set of user-defined other phone assignments
maybe F1-F12 functionality when the phone is docked to a Cradle, Docked into a Tablet Screen, or switched from App Mode to "Windowed Mode" or "Desktop Mode"
the 2 external micro SD Card slots would make it more easy for transferring files between various devices & users, while the internal SD Card Slots would remain protected from possible virus infection from external use
the MyDP connection would be at the bottom left, USB would be at the bottom right.. The Docking Cradle would have Both MyDP & USB Male Ports..
The Docking Cradle would have Common Display Ports VGA, DVI, HDMI, etc.. as well as a 4-port USB hub
Docking the cradle would attach both MyDP & USB, and allow connection from Cradle to HD Display, and use with USB mouse & Keyboard
How Awesome is that?
actually, phones now have 1920x1080 screens, i see...
and I guess 8-core processors may become the new thing as well
we need powerful programs that utilize these upcoming hardware configurations
and I'd like to view the entire Windows 7 desktop at 1920x1080, on my 5 or 6" ACTUALLY smarterphone's screen
yes, i dont care if you cant see it or read it.. I can, i assure you..
and no i dont care if it'd hurt your eyes or make you feel grumpy.. I want it
Has anyone tried installing XP in one of these phones yet?
how far off are we on that?
but we'd need an OS which is made for zooming from full desktop mode to panning mode or something better which takes us from full resolution desktop to multi- application windows
which is where Android should really be putting all of their resources
or Microsoft could take the market with a Windows MOBILE 8 made for this exact purpose
or, Apple, may even suddenly appear on the market with it, making their iPad as useful & functional as the macbooks, and their phones equally as functional & useful as well.. if they can ever stop milking technology & bleeding their customers dry for every last cent they may spend on something before offering the next decades late piece of technology
or we can all sit around gawking at each others swiping methods..
most of you probably already know these things. but still nice to collect anecdata...
first off, usb absolutely refused to work at all no matter what device I tried, hub or no hub.
eventually after the large-ish 12/5 update, and then what looked like another update so brief I almost missed it, things started working. or maybe it was me turning off "usb debugging" that helped? not really willing to mess with it, now that usb generally works.
- generic usb hub, yep. powered or unpowered, good either way. but you all already knew that.
- 'das keyboard' with built in 2-port hub. keyboard works, hub works with flash drives, mice and kbds.
- logitech marble mouse - works, quelle surprise. via hub too.
- amazon brand cheapie keyboard - works. via hub too.
- iogear generic sd/microsd reader - works. via hub too.
- 2 different cameras of generic UVC 1.00 class - work fine with 3rd party software (search for "usb camera" on google play e.g. snapexwebcam). via hub too.
- SATA dock with built in usb hub (SD slot and 2 usb ports) - this thing sometimes worked but more often froze the ouya and had to reboot.
- cmedia hs100 usb soundcard - microphone input + stereo headphone output. this is a super generic chipset supported quite well by linux. dmesg showed it as recognized, but sound output did not automagically switch over to it. probably could be made to work with some hacking around.
most of the time, if I unmounted my usb flash drive from the storage menu, I could remove and then put it back and it would automagically show up under /mnt/usbdrive. again and again.
hotplugging card readers, usb drives etc. there are some nice free 3rd party userland mounters I can personally recommend:
usb otg helper (don't let the "otg" fool you, although it does that too if a device's kernel supports otg. it will mount ALL supported partitions (ext, fat, ntfs) on a flash drive, not just the 1st partition)
play.google.com/store/apps/details?id=net.shajul.usbotg
paragon exfat/ntfs/hfs (not sure if it does ext too)
play.google.com/store/apps/details?id=com.paragon.mounter
Thanks for the information!
Nothing special to add, my western digital 2Tb energy conserving drive works great (no problem with the lag as it spins up). My cheap $10 Walmart keyboard is fine as well.
I have not tired any hubs, or anything else for that matter. A hub is on the list though as some extra flash storage would be nice.
I'm surprised to hear the cameras were working. Google has been blank as far as getting cameras recognized so I wasn't sure if it had been made to work yet. Any luck getting apps such as Skype to recognize the camera? How about that USB microphone? Any thoughts on how it might work for voice-to-text or as a 'generic' input device for voice control (utter!, Autovoice, Tasker).?
Generic USB hub - working
Sandisk microSD adapter - working
Logitech wireless USB keyboard - working
Retrolink USB N64 controller - not working
Sent from my ADR6350 using Tapatalk
haven't tried skype for ideological reasons, sorry.
I have tried linphone-video, loading it thru both f-droid and google play store. in both cases it immediately force-quits.
(I have this problem with more than a few apps, I really need to put in some time to check catlog/logcat...)
csipsimple works, but none of the settings let me choose audio i/o devices. (and csip doesn't support video)
the c-media hs100 usb doodad is definitely supported - I tried "usb audio tester" (also "usb audio tester root") and it worked just fine there (ext mic to ext speaker - I heard myself talking definitely). but no way to select it in the Settings UI. whereas my bluetooth speaker and bluetooth headset both work/switchover fine, but that is sort of standard switching built into most android devices.
I have recently replaced my head unit
Everything works on my unit, but the USB camera refuses to work with any of the available dash camera apps
I have installed a basic USB camera app and I can see the input from the camera, so it seems the other apps, simply don't recognize it
I had the camera installed on another MTCD unit and it was working perfectly well
I suspect there is some configuration that is telling android to use a different input, so I have manager to get to the hidden menu and there is a field for DVR, and changed it from the default (0) to 1, then to 2 then to 3, all to no avail
This unit is an Android 6 unit with a quad core with 2GB Ram
See below some of the device details :
HMI: TSJK_010.2017.04.15.10.51
MCU: TS907.170330
MEDIA: CZJv1.0.1_170411_1815
BTV: BT.17.04.07.1755(17:04:20:21:30:45)
Any help will be appreciated
Follow this: Car Settings>Setting Logo>Set Password:3368>DVR type>USB DVR.
https://www.photobox.co.uk/my/photo/full?photo_id=9775466627
I think this is what you need to do if you have joying.
Unfortunately there is no option to put "USB", the only options are numeric, starting from 0
I already tried 0, 1 , 2 and 3, but no joy
The unit looks very much like joying , but it isn't
I have asked the seller and they sell a compatible usb camera, but it has its own sd memory card to record.
What's the point of having a camera connected to an android unit, it is has its own local storage? You may instead have bought a separate dashboard camera
Anyway thanks for the suggestion
usd dash cam ?
I have heard this first time.
javiermi said:
...What's the point of having a camera connected to an android unit, it is has its own local storage? You may instead have bought a separate dashboard camera
Click to expand...
Click to collapse
1. HD+ video recording is a very CPU consuming task, one would not want to have his/her HU stalled. So let the daschcam use its dedicated CPU and local storage SD to do the task.
2. The point of having a camera connected is (as implemented by Joying) being able to output video on HU display, both live and stored on cam's SD - very handy; connected Joying cam (which does not have own battery) also takes time from HU to stamp video. Other brands are even able to take GPS coordinates from HU.
javiermi said:
What's the point of having a camera connected to an android unit, it is has its own local storage? You may instead have bought a separate dashboard camera
Click to expand...
Click to collapse
Because you do not know how usb works.
HD-video is not only CPU intensive, like ste2002 already mentioned, but it can flood your USB channel if you use raw video and encode it on your android unit.
USB-2, as on ALL android units is "half-duplex", meaning that only one device can use it at a certain time and only in one direction (like a walkie-talkie: only one can speak and you press the button and say "over" (as handshake in digitial language) to let the other speak). If you have 2 devices with your dashcam recording, and the 2nd one polls the usb hub, your video stream is interrupted and thereby immediately corrupt. Or the unit needs to send "something" to the dashcam, it will also interrupt and corrupt the video stream.
The option of encoding it on the dashcam and send the video over USB to the unit is better but not fault-tolerant.
encoding it on the dashcam and saving it over usb directly to your unit, might work but could still run in above mentioned problems.
encoding it on the dashcam, save it on the dashcam (internal "mini"-storage), and then copy the complete video over usb to the unit might work well. These dashcams might even be for sale, but I expect they are quite expensive, whereas a local sd-card in the dashcam is dead-simple and dead-cheap.
Once USB-3 gets to these android units, being full-duplex and having much higher speed and bandwidth, it might be useful to do it over USB (making sure all devices are USB-3 or that you have a real switching USB-3 hub), but only if the CPU can handle the HD raw video and encode it: A PX3 can't, a PX5 can't, a Sofia 3GR can't. Wait for much faster units (specification wise both the PX5 and Sofia 3GR should, but both fail on it).
That is why you should ALWAYS let the dashcam do both the video encoding and the storing of the media files, and NEVER over the usb.
Edit: With the Joying, and a lot of others, you can view back the movies, or get an online view where a MJPEG stream is displayed on the unit.
surfer63 said:
Because you do not know how usb works.
HD-video is not only CPU intensive, like ste2002 already mentioned, but it can flood your USB channel if you use raw video and encode it on your android unit.
USB-2, as on ALL android units is "half-duplex", meaning that only one device can use it at a certain time and only in one direction (like a walkie-talkie: only one can speak and you press the button and say "over" (as handshake in digitial language) to let the other speak). If you have 2 devices with your dashcam recording, and the 2nd one polls the usb hub, your video stream is interrupted and thereby immediately corrupt. Or the unit needs to send "something" to the dashcam, it will also interrupt and corrupt the video stream.
The option of encoding it on the dashcam and send the video over USB to the unit is better but not fault-tolerant.
encoding it on the dashcam and saving it over usb directly to your unit, might work but could still run in above mentioned problems.
encoding it on the dashcam, save it on the dashcam (internal "mini"-storage), and then copy the complete video over usb to the unit might work well. These dashcams might even be for sale, but I expect they are quite expensive, whereas a local sd-card in the dashcam is dead-simple and dead-cheap.
Once USB-3 gets to these android units, being full-duplex and having much higher speed and bandwidth, it might be useful to do it over USB (making sure all devices are USB-3 or that you have a real switching USB-3 hub), but only if the CPU can handle the HD raw video and encode it: A PX3 can't, a PX5 can't, a Sofia 3GR can't. Wait for much faster units (specification wise both the PX5 and Sofia 3GR should, but both fail on it).
That is why you should ALWAYS let the dashcam do both the video encoding and the storing of the media files, and NEVER over the usb.
Edit: With the Joying, and a lot of others, you can view back the movies, or get an online view where a MJPEG stream is displayed on the unit.
Click to expand...
Click to collapse
Surfer63,
Thanks for this post, it's one of the more informative ones I've found when searching for answers about making USB cameras work with these Chinese head units. I'm replying because while I'm far from an expert, my experience does not seem to follow some of what your wrote. In my case, I have an ISUDAR brand PX3, 2GB ram using a 7.1.2 "GS" ROM and have successfully used a UVC compliant 1080p USB Camera (Logitech C922x Pro Stream Webcam) and was able to record no problem using the factory supplied app labelled "DVR". The camera has no built in storage, and the only storage option the DVR app allows requires the file to be written to an attached USB stick (my unit has no SD card slot). Both the camera and USB stick are plugged into ports labelled USB 2.0. Overall this seems like good news as it's more successful than most have found.
For me, however it's still not success and I hoped you could shed more light here. My main goal is not a DVR, but to use the camera to record videos by other apps, such as Torque or TrackAddict. These apps support USB cameras and work fine with my Logitech and OTG adapter on my phone, however on the head unit it only partially works. When opening both Torque or TrackAddict the video displays properly in preview, but once Record is selected it either appears to work but does not actually capture video (Torque) or immediately gives an error "recording failed to start" (TrackAddict). When attempting playback from Torque you hear the audio, but the screen is a static mess of the actual image and various green hues and lines.
From this almost successful experience I am trying to determine what is likely not right, and if/how to check and correct. A few thoughts:
1) I know little about the Android inner workings, but reading some android camera API developer info I'm wondering if the ROM has the MediaRecorder aspect "hardwired" to only the DVR app. In my simple view this could explain why video preview works in other apps but recording does not.
2) In Torque you can select which camera to use, since the unit has no built in camera Back 0 doesn't exist and is not in list, Front 0 doesn't either but is in list (shows nothing). Front 1 shows the USB camera and selecting this makes preview work in the app. Interestingly the list also shows the USB camera by name, but when selected crashes the app. Is the head unit seeing the USB camera, assigning it to Front 1 in the background, and also forcing some record settings to USB stick and DVR app? If I could stop the head unit from automatically assigning the USB camera to Front 1, perhaps selecting it by name in Torque would allow it to function properly and record? I have not found any option in the Factory Settings menu to affect this yet.
Anyway, given I feel a bit closer to success than many on here I was hoping for some guidance on what to chase and how. Your insight would be much appreciated.
I'm struggling with similar issues with Eonon 2170 Android 8:
built in DVR app seems to work when it works, though, often stops recording (red light on USB cam goes off)
Torque's plugin just crashes... even though it's supposed to support USB cam
got somewhere with Dash Cam Travel – from Tomas Valek, dev promised to look into this
and, getting results from USB Camera - Connect EasyCap USB WebCam ShenYao China
abbots said:
I'm struggling with similar issues with Eonon 2170 Android 8:
built in DVR app seems to work when it works, though, often stops recording (red light on USB cam goes off)
Torque's plugin just crashes... even though it's supposed to support USB cam
got somewhere with Dash Cam Travel – from Tomas Valek, dev promised to look into this
and, getting results from USB Camera - Connect EasyCap USB WebCam ShenYao China
Click to expand...
Click to collapse
I just updated from a KitKat unit (4.4.4) where the dash cam apps all worked with the USB camera just fine. I have a Allwinner T8 unit and the USB dash cam is not seen using the apps I have.
The apps that I got from the play store now uses my backup camera for the forward camera, but the supplied Dash Cam App works fine selecting the USB camera.
Trying to figure why the USB selection on the apps refuse to select USB while it always selects the backup cam (video source)
I have even disabled the backup and those apps will not work at all.. I will try the Dash Cam travel to see.
I can't help much with the main question(s) being discussed here but I have one of those standalone USB powered dash cams in my vehicle. It's just a totally generic Chinese eBay one.
It records directly to an SD card on the camera itself and broadcasts a wifi signal so that I can manage/view the feed on a (very unstable) app on my iPhone. The app is called "WCVR-PWD".
I've always wondered if there's a way to just view it directly on the Joying itself an sounds like some of you guys are doing that. All I'd be interested in is a totally live feed to adjust the camera as necessary.
What app/mod/function do I need to do to the Joying to do that?
As most? the head units have multiple inputs:
rear camera video in
video/audio in
USB
any experts care to comment on suitability or pros and cons of using composite video output camera versus USB camera?
Would composite output video camera be a superior choice?
javiermi said:
I have recently replaced my head unit
Everything works on my unit, but the USB camera refuses to work with any of the available dash camera apps
I have installed a basic USB camera app and I can see the input from the camera, so it seems the other apps, simply don't recognize it
I had the camera installed on another MTCD unit and it was working perfectly well
I suspect there is some configuration that is telling android to use a different input, so I have manager to get to the hidden menu and there is a field for DVR, and changed it from the default (0) to 1, then to 2 then to 3, all to no avail
This unit is an Android 6 unit with a quad core with 2GB Ram
See below some of the device details :
HMI: TSJK_010.2017.04.15.10.51
MCU: TS907.170330
MEDIA: CZJv1.0.1_170411_1815
BTV: BT.17.04.07.1755(17:04:20:21:30:45)
Any help will be appreciated
Click to expand...
Click to collapse
How did u solve it then .?
conclusion for dvr with SDCard?
Hi
This is a good summary and helpful since a lot of info on google seems outdated.
I have a new Joying 8 Core intel unit (Nov 2019).
I want to buy a small non-Joying DVR camera, record to sdcard in cam, and use the head unit to review video from cam and manipulate the files as required (ex. send an important video or image).
Will the Joying do this for any cheap DVR camera?
Do I just need to use a different DVR app on the head unit?
Thanks!
surfer63 said:
Because you do not know how usb works.
HD-video is not only CPU intensive, like ste2002 already mentioned, but it can flood your USB channel if you use raw video and encode it on your android unit.
USB-2, as on ALL android units is "half-duplex", meaning that only one device can use it at a certain time and only in one direction (like a walkie-talkie: only one can speak and you press the button and say "over" (as handshake in digitial language) to let the other speak). If you have 2 devices with your dashcam recording, and the 2nd one polls the usb hub, your video stream is interrupted and thereby immediately corrupt. Or the unit needs to send "something" to the dashcam, it will also interrupt and corrupt the video stream.
The option of encoding it on the dashcam and send the video over USB to the unit is better but not fault-tolerant.
encoding it on the dashcam and saving it over usb directly to your unit, might work but could still run in above mentioned problems.
encoding it on the dashcam, save it on the dashcam (internal "mini"-storage), and then copy the complete video over usb to the unit might work well. These dashcams might even be for sale, but I expect they are quite expensive, whereas a local sd-card in the dashcam is dead-simple and dead-cheap.
Once USB-3 gets to these android units, being full-duplex and having much higher speed and bandwidth, it might be useful to do it over USB (making sure all devices are USB-3 or that you have a real switching USB-3 hub), but only if the CPU can handle the HD raw video and encode it: A PX3 can't, a PX5 can't, a Sofia 3GR can't. Wait for much faster units (specification wise both the PX5 and Sofia 3GR should, but both fail on it).
That is why you should ALWAYS let the dashcam do both the video encoding and the storing of the media files, and NEVER over the usb.
Edit: With the Joying, and a lot of others, you can view back the movies, or get an online view where a MJPEG stream is displayed on the unit.
Click to expand...
Click to collapse
samster125 said:
I want to buy a small non-Joying DVR camera, record to sdcard in cam, and use the head unit to review video from cam and manipulate the files as required (ex. send an important video or image).
Will the Joying do this for any cheap DVR camera?
Do I just need to use a different DVR app on the head unit?
Click to expand...
Click to collapse
I do not know if the joying will do this for "any" DVR camera. That is an extremely wide area.
90% of the Chinese dashcams are the same and have more or less the same app. I did not hear yet about issues.
Some dashcams come with internal GPS location logging, some not.
Some apps allow you to view the videos over usb, some/most allow you to copy the videos over usb to your local unit drive.
I use my dashcam as well for Mapillary recording. That results in big amounts of data and I simply take the sd-card out of the camera and do it on my laptop. I have two SD-cards which I simply exchange. A 16-32 Gb-sdcard costs something between 6-12 euros (in the Netherlands). Note that any class 4 or better will do. You don't need extremely fast cards.
What I have also noticed in the past (with 2 dashcams, so statistically perhaps completely unreliable) is that most cheap dashcams simply stop in the middle of a recording when being switched off: no battery whatsoever to nicely finish the recording and nicely unmount the sd-card. This leads to lots of minor corruptions. So when I switch SD-cards, I always do a "checkdisk" on the SD-cards and I always have to repair errors. Be aware of that.
GPS for USB Dash Cam
ste2002 said:
1. HD+ video recording is a very CPU consuming task, one would not want to have his/her HU stalled. So let the daschcam use its dedicated CPU and local storage SD to do the task.
2. The point of having a camera connected is (as implemented by Joying) being able to output video on HU display, both live and stored on cam's SD - very handy; connected Joying cam (which does not have own battery) also takes time from HU to stamp video. Other brands are even able to take GPS coordinates from HU.
Click to expand...
Click to collapse
I recently got an ATOTO A6 Pro and have been frustrated trying to embed GPS in the dash cam files. You mention that, "Other brands are even able to take GPS coordinates from HU." Which brands would that be? ATOTO has not been able to help. They just say it is impossible.
I have an Xtrons PX6 Android 9 headunit with cheap usb dash cam. The cam itself has micro SD card inserted and usb plugs into my usb on the headunit for viewing.
I have bought 3 of these cameras 2 to use in different vehicles and 2nd new Xtrons cam to go with the PX6. All of these cameras generally have pre-installed APK on the camera to install on the headunit.
You'll also find that these cameras have GPS and eDog built in aswell as ADAS. I purchased 2 of these cheap Chinese units from eBay for about £15 each and they work perfectly.
The advantage of having the camera record is that if the headunit goes down you still have the camera covering your ass if theirs a problem.
Sent from my VOG-L29 using Tapatalk
Sorry to hijack this thread.
Does anyone know what might be the problem when GPS signals lost immediately right after an usb camera plugged in?
The signals came back once the camera were unplugged. (the camera functioning fine, apart from not detecting gps as they're all lost)
Would it be a fault of the camera or the head unit itself?
USB thumbdrive works fine though, no issues.
Tbizzness said:
I have an Xtrons PX6 Android 9 headunit with cheap usb dash cam. The cam itself has micro SD card inserted and usb plugs into my usb on the headunit for viewing.
I have bought 3 of these cameras 2 to use in different vehicles and 2nd new Xtrons cam to go with the PX6. All of these cameras generally have pre-installed APK on the camera to install on the headunit.
You'll also find that these cameras have GPS and eDog built in aswell as ADAS. I purchased 2 of these cheap Chinese units from eBay for about £15 each and they work perfectly.
The advantage of having the camera record is that if the headunit goes down you still have the camera covering your ass if theirs a problem.
Sent from my VOG-L29 using Tapatalk
Click to expand...
Click to collapse
I have this usb dash cam,but i can't download the update to have adas and other fatures.i can't communicate with the seller because the store is closed.my cam is the U3 Mini Full HD 1080P Car DVR Camera ADAS ...can you help me with the apk file pls?
Hello everyone
Because I came in looking for a solution to a problem with a camera for my car that has a "head unit", I come to ask my question. The "head unit" is isudar px3 with Android 7.1.2. I bought a forward camera that works well on a cell phone with android 7 (and with OTG adapter) without problems and on the date of its correct recording. When trying to put it in the car through one of the USB ports (there are 2 - one that I will say is normal and the other prepared for 3G/WIFI) and after installing the .apk that comes with the camera, it tells me that there is no card and that there is a problem with the USB, as if it did not exist.
already tried several .apk but none can connect with the camera.
During the time that it is connected, the card in the usb case records image and sound although it does not show anything on the car's media player screen, but these recordings show a much earlier date that has nothing to do with the moment in which it is recorded. That date will be that of the camera itself a few years ago. If the date was correct, it would still leave the camera in its place and for the least. But as it does not, its validity in case of an accident will be very weak, obviously, and so it is not working. Having asked the question, I ask for the opinion of someone who has had the same problem and has solved it. Thanks in advance.