Database Develop

[Help] Napoli 6270 (2 din dvd gps car) is stuck in a boot-loop.

Hi, I have this android 2din car auto and stopping load system after tests:
http://produto.mercadolivre.com.br/...apoli-2-din-6270-android-wi-fi-gps-tv-dig-_JM
========================================================================
INFORMATIONS:
CAR MULTIMEDIA "NAPOLI 6270"
ANDROID, WI-FI, GPS, DIGITAL TV (ISDB-T), USB, SDCARD, DVD, TFT, CAPACITIVE, MIRRORLINK (double usb), SUPPORT IPOD, WIFI, Universal 2 DIN Chassis, Panel HD TFT Touch, res. 800x480 6.2 ", 720p HD
Android 4.0 OS.
Processor SIRF Atlas VI, ARM Cortex A9, 800MHz, SDRAM 512MB DDRIII
=========================================================================
Now, I need enter recovery mode to do a factory reset and wipe cache to load the system. How to acess the recovery? I tried some buttons: reset+power, power and vol+,, but nothing happens.
See some pictures:
Stop here (only Ford logo - changed)
cat/proc/cpuinfo:
This is "original firmware" (copy from internal memory "sdcard"):
https://mega.co.nz/#!DQMFDBhb!3WZLh4whv-SBqwjv76gXa5MYgFBrRc-lgpfbi00wLi0
Some videos before boot-loop (system ui, waze, spotify, gps, dvd, radio):
https://www.youtube.com/watch?v=VaCm-b1u6Xc
https://www.youtube.com/watch?v=qhRedQfSSGE
https://www.youtube.com/watch?v=w0-KPyZtLio
https://www.youtube.com/watch?v=mLznc-rf5yw
https://www.youtube.com/watch?v=bwJBxdpUwtc
https://www.youtube.com/watch?v=b0DxZsWkGqE
Now, the current status:
https://www.youtube.com/watch?v=OI6JAtL38Vw
All the videos in Brazilian portuguese.
Thanks
Sorry my english
Frank
=================================

Hello Frank have you repair your dvd car?? im stuck in the same window .
Regards
Jorge

Citroen C4 - can I install a tablet?

Hi,
I have a Citroen C4 with some kind of an aftermarket Windows CE system which is horrible - link my system: http://qdis.co.kr/NewQdis/?page_id=11956
The way that the unit is installed goes like this:
OEM radio (RD-5) connected to the QNAVI2 module. the screen is connected directly to the QNAVI2 module.
I found on Ali some head-units which will replace my current OEM radio and display panel with Android 4.4 OS and will keep all of the car features as is (steering wheel control, car menus for setting features like internal lights delay, units (Kph / Mph) etc').
I would like to know how can I put an Android tablet which will be connected to the original car radio (RD-5) but will keep all the features.
Is that possible?
How can you make Android tablet (or Head-unit) to "talk" to the car CAN-BUS system?
Hope you guys can help me figure it out.
Thanks,

guys, please see if you can help me out...
The thing that I really wish to know how can I make android tablet to read the can-bus massages like errors and also how to make the tablet access the configuration of my car...

Which OBD2 adapter?

I have old OBD2 v1.5 adapter. Chinese, big one. Which pairs with HU and works well.
I wish to buy new one, that call 'mini'. I know I have to look for v1.5 (as 2.1 is a crap) and with PIC18F25K80 chip.
But I read that even much of these new mini are PIC based, that have some strange Mac address like AA:BB:CC:11:22:33.
Anyone has experience with such adapters? Do they pair and work with Torque on our HUs?
If anyone is using such an 'mini' adapter, please post link to eBay/AliExpress where you purchased it. Will be very grateful (and it may help other people here, too, as many have issues pairing/using crap adapters).

I personally bought https://www.ebay.com/itm/Auto-16-Pi...le-Diagnostic-Adapter-For-elm327/152700822059 and https://www.ebay.com/itm/2017-ELM32...uto-Car-Scanner-Scan-Tool-Cable-/112070132071 so I connected it over USB and only thing I've made is HW MOD to get ACC+ instead BAT+ from OBD2 so that it is powered only when Key is turned on.
Resolved pairing issue with no pairing and all works along with BT and WiFi free for other devices.

PekeMM said:
I personally bought https://www.ebay.com/itm/Auto-16-Pi...le-Diagnostic-Adapter-For-elm327/152700822059 and https://www.ebay.com/itm/2017-ELM32...uto-Car-Scanner-Scan-Tool-Cable-/112070132071 so I connected it over USB and only thing I've made is HW MOD to get ACC+ instead BAT+ from OBD2 so that it is powered only when Key is turned on.
Resolved pairing issue with no pairing and all works along with BT and WiFi free for other devices.
Click to expand...
Click to collapse
Thank you for sharing. I was not considering USB option, but it sounds interesting.
I see you both the 'big' one (same as my old one). And they really work very good.
But I would like to buy some of 'mini' models as my OBD2 port is in such place (under steering wheel and just above brake pedal) that big one is too big and my feet is hitting it while driving. Here is obe model I consider
Hardware V1.5 Chip PIC18F25K80 ELM327 Bluetooth V1.5 Auto Code Reader Super MINI ELM 327 Works ON Android Symbian FW V1.5 BEST
http://s.aliexpress.com/I3i26fy2
There are 2 models of these (not colours): old design with 2 PCB boards, and new one with just 1 board. I wonder if anyone has any of these?

pa.ko said:
But I would like to buy some of 'mini' models as my OBD2 port is in such place (under steering wheel and just above brake pedal) that big one is too big and my feet is hitting it while driving.
Click to expand...
Click to collapse
:silly: I do not see the problem there as if you checked both links from my post you would see that I use extension cable that do not have issue with connector position. Mine is located right above gas pedal so I could not drive car normally with any OBD Adapter unless I used extension cable.
pa.ko said:
Here is obe model I consider Hardware V1.5 Chip PIC18F25K80 ELM327 Bluetooth V1.5 Auto Code Reader Super MINI ELM 327 Works ON Android Symbian FW V1.5 BEST
http://s.aliexpress.com/I3i26fy2
Click to expand...
Click to collapse
PIC is programmed micro controller and not actual ELM327 see https://www.elmelectronics.com/products/ics/obd/ and v1.5 nor v2.1 exist officially as they are clones and you should use https://play.google.com/store/apps/details?id=com.applagapp.elm327identifier to test actual model and support.
Re which one: I ordered 6 different models and kept two that worked flawlessly with my car 1 was broken (got refund) and resold other 3 to get my money back.

PekeMM said:
I personally bought so I connected it over USB and only thing I've made is HW MOD to get ACC+ instead BAT+ from OBD2 so that it is powered only when Key is turned on.
Resolved pairing issue with no pairing and all works along with BT and WiFi free for other devices.
Click to expand...
Click to collapse
How did you mod this?

gazenbeek said:
How did you mod this?
Click to expand...
Click to collapse
It is fairly simple MOD:
1. Soldered positive wire of lighter connector that have power only when Ignition is turned on.
2. Bought FLAT cable that I can easily cut the wires like in picture s-l1600.jpg
3. Cut Wire on pin 16 BAT power see ODBII%20Master%20Pinout.jpg
4. Connected wire that goes to OBDII to Positive wire I prepared in step 1
5. Connected OBDII to connector from FLAT CABLE
6. Connected USB to HU SINGLE USB CABLE
7. Tested if all works with Toque
8. Used cable ties to secure all cabling behind dashboard
and now I enjoy the all the diags on HU

PekeMM said:
so I connected it over USB and only thing I've made is HW MOD to get ACC+ instead BAT+ from OBD2 so that it is powered only when Key is turned on.
Resolved pairing issue with no pairing and all works along with BT and WiFi free for other devices.
Click to expand...
Click to collapse
Thanks for this info, very helpful, just got Android 8 Eonon 2170, and I've been struggling to pair OBD, Kiwi 3 doesn't show (BLE not supported? Don't know), Tomtom unit won't pair, no name unit seems to work, but, I've thought, why not USB, started searching for USB Android supported, luckily came across your post.
To change BATT to ACC, is that just so it's ' done properly'?
Surely battery drain would be miniscule, or not? I guess makes sense to have it not powered all the time.
Going by your posts, so, some of these units didn't work properly,ECU side or Android side? Thanks again, A

I just looked into factory settings, there is a CANBUS section, currently set to NONE, should that that altered to car maker's CANBUS ?

abbots said:
Thanks for this info, very helpful, just got Android 8 Eonon 2170, and I've been struggling to pair OBD, Kiwi 3 doesn't show (BLE not supported? Don't know), Tomtom unit won't pair, no name unit seems to work, but, I've thought, why not USB, started searching for USB Android supported, luckily came across your post.
Click to expand...
Click to collapse
Glad I helped someone
abbots said:
To change BATT to ACC, is that just so it's ' done properly'?
Click to expand...
Click to collapse
Yes, it is safe no issues at all
abbots said:
Surely battery drain would be miniscule, or not? I guess makes sense to have it not powered all the time.
Click to expand...
Click to collapse
It is not the problem that it drains a ot but all small drains can pile up so eventually you have a problem. I have park mode security enabled on my dashcam system so it drains some, OBDII can drain a littl, but it is known that in some cases keeps ECU awake that can drain a lot due teh number of sensors it keeps awake also
abbots said:
Going by your posts, so, some of these units didn't work properly,ECU side or Android side? Thanks again, A
Click to expand...
Click to collapse
All was ECU side due the different pinouts see my pics, I have seen in the past several USB -> COM chips that are not supported on Android due the OEM build and specific drivers like some factory that are not recognized on laptop till you install their licensed software (Usually JUNGO Based Drivers).
---------- Post added at 00:24 ---------- Previous post was at 00:20 ----------
abbots said:
I just looked into factory settings, there is a CANBUS section, currently set to NONE, should that that altered to car maker's CANBUS ?
Click to expand...
Click to collapse
Only if you got specific cables with canbus decoder (black little box). even then USB OBDII is used to diagnostic and clear codes. I use Toque 1.83 and it works on one unit that v1.52 didn't worked with. Usually ELM v1.5 works better than v2.1

thanks! I have now got USB OBD unit 1.5 (still need splitter/extender), tried yesterday with Torque as well as with Palmer's DashCommand:
it kinda worked - during first trip, 45min, Torque app crashed twice or more, worked after restart, on return trip, DashCommand also choked once or twice, thenm I relaized, as fuel tank level is not reported, unless I run app 100% of the time, fuel consumption won't be correct - and, realsiticall, I need TomTom on the screen more than gauges....
I see there are OBD spliters that 'allow' two or three OBD devices plugged in, wouldn't you know, is it OK to split/use multiple OBDs ?
like, I have TomTom 'Curfer' OBD data logger - just logs 'quality of driving", thoiught to get splitter to log data, AND, if so desire, call gauges on screen ?
thanks for explaing CANBUS!
do you use TPMS tyre pressure units, if so, which ones ? my radio has an app to read such, wonder if it's worth it ?

I have connected my USB OBD. Torque not recognised device. How to check that Scanner is properly installed on android system?
OBD scanner is generic just like this:
https://www.amazon.co.uk/ELM327-USB-Interface-Diagnostic-Scanner/dp/B00IWLLX1Y
BTW I have MTCE with android 8.0 with KLD MCU.

Torque lite ain't work with android/usb, only in bluetooth mode.

I have torque pro so there is no problem there.
Any way problem solved. Bought Bluetooth version.

Xtrons Ford android problems with canbus!

Ford 6000cd replacement unit is not working correctly! Doesn't turn on and off with key! Randomly powers off! And illumination not working nor screen dim! Maybe canbus not working! Please help me

You probably should be posting in the Android Head Unit forum. First of did you get a CANbus box with your HU? If so are the orange and red wires connected to it? Otherwise go to the factory menu and check/try other CANbus settings.

Hi thanks for the reply yes it did come with a can bus all leads were supplied for ford plug and play replacement

!!1!!1!!!.
Biff, is that really you? !!11!!1!

You can check if the CANbus box is talking to your HU by typing LOGCAN from the factory settings menu instead of the password if all you get is a black screen then the CANbus decoder is either disabled in the CANbus menu or set to the wrong type or the wiring is wrong. I remember seeing something about 2 wires being connected backwards but I can't find it. This post has a pinout diagram that might match your HU.

Can you diy a USB Dongle 'PC' stick - Android Auto - Full Android?

(Ya'll are smart people, I have to be missing something obvious, my apologies if this post is comedy and I'm a bad researcher)
Without linking to any specific product i'm curious about the tech related to these 'USB Sticks' that plug into my cars 'Android Auto' USB port and provide a full Android experience for my factory OEM touchscreen radio.
I'm not sure of all the acronyms used in the posts i'm finding on XDA, I don't believe I'm looking for a head unit as I want to use my existing radio. Android Auto enabled, touchscreen.
Can you make such a device from a Raspberry PI, or Arduino, or boot off an SSD/SD/USB Adapter? Plug and Play, hijacks the OEM software and bootloads full android?
TIA!

My understanding is that if you're car is not Android Auto enabled then you will not get anything to work.

CarDongle
CarDongle: USB Car PC Computer Dongle for Vehicles
CarDongle is an Octa-core USB Car Donggle Computer Stick, Up to 4GB RAM 64gb ROM, Mic, MicroSD slot | Check out 'CarDongle: USB Car PC Computer Dongle for Vehicles' on Indiegogo.
www.indiegogo.com

I've been trying to build such "dongle" using Odroid N2 running Android OS acting as Android Auto client. The main problem is that Android Auto connects but I see only black screen on the car's infotainment (audio works - I hear Odroid playing music)
I have no idea what the problem is.

itamarbh said:
CarDongle
CarDongle: USB Car PC Computer Dongle for Vehicles
CarDongle is an Octa-core USB Car Donggle Computer Stick, Up to 4GB RAM 64gb ROM, Mic, MicroSD slot | Check out 'CarDongle: USB Car PC Computer Dongle for Vehicles' on Indiegogo.
www.indiegogo.com
Click to expand...
Click to collapse
Knock off, Chinese origin unit astroturfing on indiegogo.
These are of poor quality and poor experience. They may work for a while then break as google/apple update their products.
Unfortunately indiegogo is being used more often by unscrupulous Chinese origin resellers peddling their grey wares.
[Most of the projects on Indiegogo are cheap Chinese junk already on the market and repackaged as a crowdfunding campaign.]
247 Indiegogo Reviews: Is It legit? | ConsumerAffairs
Read reviews and complaints about Indiegogo, including funding choices, promotional options, analytics, credit fees, accessibility and more.
www.consumeraffairs.com

I'm afraid of being a "hostage" of some short term projects (exactly as Marchnz wrote - working for a while until the first update). Therefore I want to build my dongle using standard components - SoC (Odroid, RPi, ... ) with a supported Android (Lineage, ...) and "common" protocol (Android Auto, Mirrorlink, ....).
At the moment I'm stuck with Android Auto showing only black screen (the car is authorized and play the sound but no screen output). Mirrorlink (as an alternative to AA) can't be used because the device is not certified for that and I haven't found an "unlocked" Mirrorlink APK.
I have to investigate the Carplay option (aka "Apple Pie").

I have cardongle for a month new and work 100%

I wishing you being satisfied with that for years.
Personally, I wan;t to avoid being locked with a proprietary product without uncertain updates.

@mseg
I use odroid n2 with Screen2auto its works

adrien974 said:
@mesg
I use odroid n2 with Screen2auto its works
Click to expand...
Click to collapse

adrien974,​could you please describe your working setup including used versions?
I have been testing these components (trying their combination) without success:
- Odroid N2 (there's nothing to discuss)
- Android OS (Hardkernel Android PIE 32 bit 20200520 and PIE 64bit versions 20201105, 20210414, and 20210531) installed on eMMC
- Bluetooth module v5.0 with enabled BT stack (although BT stick blinks its' not visible and can't find out other BT clients). Tested also without BT stack and BT module inserted - the same result
- Open GApps arm64 9.0 pico (20200918, 20210619, and 20210518). The only version 20210518 seems to provide AA support - when Odroid N2 connected to the OTG cabel, AA starts on N2 (however, no video output). The other versions didn't start AA on N2.
- Google app (version 12.18.11.23 and the latest one)
- Google Maps (always the lates one - installed via Google Play)
- Android Auto arm64 (5.9.604644, 6.3.611334, and 6.5.612134) - Google is enforcing to update to the latest AA. I was able to try 5.9 a month ago, now it requires to update to the latest one.
- time synchronized via the Internet

Hi,
all my applications are up to date except Android auto which is in version 6.2

Did you do any "special configuration" (disabled ADB, enabled bluetooth stack, changed rendering, ....)?
I suppose you added you Google account to Play and disabled automatic update for Android Auto?
Do you have a HDMI display connected or are you using fixed resolution (so you don't need connected display)?

mesg said:
Did you do any "special configuration" (disabled ADB, enabled bluetooth stack, changed rendering, ....)?
I suppose you added you Google account to Play and disabled automatic update for Android Auto?
Do you have a HDMI display connected or are you using fixed resolution (so you don't need connected display)?
Click to expand...
Click to collapse
Yes adb activate, i dont have screen and no bluetooth, update off
I've just youtube black screen :/ magisk 20.4

Thank you for the precious information. I'll give it another try

I've just finished testing with this setup. However, the result is still the same - Android Auto starts on N2 once connected to the car but only black screen appears.
Setup:
- Odroid N2 + eMMC + BT USB + GPS USB
- Hardkernel Android Pie 64bit (up to date)
- OpenGapps pico arm64 20210701
- Google app (up to date)
- Google Maps (up to date)
- Chrome (up to date, just to be sure)
- USB mode = no data transfer
Android Auto:
- 5.9 doesn't connect to the car
- 6.0 doesn't connect to the car
- from 6.1 to 6.5 connects to the car but only blank screen appears
I also tried:
- restarting car infotainment (no change)
- installing Google and AA as system-priv app (using Magisk and Systemizer, no change)
- clearing storage and cache of AA after each upgrade (no change)
- changing USB mode (no change)
- changing Odroid HDMI resolution (no change)
- changing AA mode in developer settings from release to developer (no change)
I suppose I'm not the chosen one and going to use the old dedicated phone, which I wanted to replace by N2 (or any other SoC).
Btw. to be able to use older AA than the current one I had to clean cache and storage of Google Play sevices and Google Play store and deny internet access for them using AFWall+. Otherwise, the AA wizard required to update AA to the latest one.

When you connect to Android Auto for the first connect you have screen on odroid n2?

Yes, connecting N2 to the ca, for the first time (or after cleaning the storage for the AA), I get a wizard on the N2 (therefore I have connected HDMI <--> USB converter to see that on the laptop) asking for six or seven permissions regarding the location, microphone, ... and another one related to let AA show notifications over UI. During this time there's a message on the car's infotainment to "look at the phone's screen once safe". Therefore I believe AA is "ready to be used".
Connecting to the car for the second time (and all other tries) pop ups the info at N2 screen that AA is connected to the car and navigation is running. At first I thought it was Google Maps error as it was the application auto- started after connection so I tried to use AA-Tweaker to keep the home screen of AA after connection and not starting any navigation app. Unfortunately, AA-Tweaker (version 4.0.2) was crashing every time.
Never mined I checked that not only Google Maps (or Waze as a default navigation) didn't produced any screen but the same applied to the audio app (Google Podcast) as I had physical buttons on the infotainment joystick (Renault).
Therefore, I'm sure it's an issue of AA itself.