"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit [ROOTED]
"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit
To avoid confusion, below is a picture of the unit this thread relates to.
I am aware of a previous unit using the same design, but it runs an older version of Android. This thread is for the unit running 4.1 as standard.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specification / Features
Hardware
CPU: ARM Cortex A9 MST786 Dual Core 1GHz
GPU: Mali-400 MP
RAM: SKHYNIX 1G DDR3 RAM H5TQ4G83AFR
iNAND: SanDisk 8GB SD1N5C2-8G (1GB system storage, 6GB internal USB storage)
MCU: STM8AH ST
Bluetooth: BlueCore5 CSR
Screen: Capacitive 800*480
GPS: SiRF Atlas V GPS Processor
Radio: Philips TEF6624
Sound Effect Processor: BD37534 ROHM
Outputs: 4x 45w outputs, Toshiba TB2929
Additional Outputs: 1x Subwoofer, 4x pre-outs
Microphone: Built in microphone
Supported Features
Bluetooth connection to phone for calls.
WiFi and 3G dongles. These must be plugged in before turning the device on, and are not hot-swappable.
Compatible 3G Dongles
ZTE MF190 Clone (Qualcomm MSM6280 + RTR6280)
Huawei E171 (Qualcomm MSM6290)
Huawei E180
Huawei E261
Huawei E1752
Non-Compatible 3G Dongles
Generic Orange/Black eBay dongle (Qualcomm MSM6280 + RTR6275)
Huawei E220
Huawei E352
Huawei E367
Connection of multiple USB devices through a USB hub, including wireless keyboards, USB memory sticks, and wireless dongles. These types of devices are hot-swappable.
Multiple USB memory sticks can be plugged in. They mount at "mnt/usb/sda1", "mnt/usb/sdb1", and so on. The limit is not known, three have been tested at once.
Wiki Page
This unit has a very useful Wiki page with a lot of good information.
Tonghai Create AN-21 U Wiki
It would be really appreciated if before posting any questions, you take a read of it, this main post, watch the video review, or do a search of this thread to avoid any repeats.
Video Review
Other videos showing specific features are also available on my channel.
News
2014.01.20Download links and bugs section updated.
2013.12.05Root is now possible.
Previous News
2013.11.16The manufacturer intends to add new features to the unit, they are currently developing an OBD II system, I assume this would be via USB. They say it will require additional hardware.
Sooner than that, they plan to release wireless mirror link for Android phones.
I asked about Bluetooth compatibility, they said my request would be sent to their engineer to include Bluetooth modules. Whether this actually gets included or not, we will have to see.
File Repository
This site has links to most of the files in this thread, including firmware and MCUs.
Android 4.1 Car Stereo File Repository
All files are of course used at your own risk.
Firmware Updates
To update the unit, extract the update files from the downloaded RAR and copy them to a MicroSD Card, insert the card, go to Settings -> General Settings -> System Update or turn the unit on whilst holding down the 'Menu' and 'Volume' buttons until the update starts.
System Version 2.7.29
Mirror 1 - Click here
Previous Versions
System Version 2.7.28
Mirror 1 - Click here
System Version 2.7.11
Mirror 1 - Click here
System Version 2.7.9
Mirror 1 - Click here
System Version 2.7.4
Mirror 1 - Click here
System Version 2.6.96
Mirror 1 - Click here
System Version 2.6.93
Mirror 1 - Click here
System Version 2.6.77-2
Mirror 1 - Click here
System Version 2.6.77
Mirror 1 - Click here
System Version 2.6.73
Mirror 1 - Click here
System Version 2.6.70
Mirror 1 - Click here
Mirror 2 - Click here
System Version 2.6.68
*WARNING* This update appears to cause issues with GPS *WARNING*
Mirror 1 - Click here
Mirror 2 - Click here
Password
System Version 2.6.62
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.60-2
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.60
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.40
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.23
*WARNING* This update appears to cause unrecoverable bricking of the unit when changing model or MCU. *WARNING*
Mirror 1 - Click here
Mirror 2 - Click here
Password
"4.2.2" Versions
Please note that these are actually Android 4.1, but the menu text has been changed to "4.2.2"
System Version 2.7.11
Mirror 1 - Click here
System Version 2.7.22
Mirror 1 - Click here
System Version 2.7.26
Mirror 1 - Click here
System Version 2.7.26-2
Mirror 1 - Click here
System Version 2.7.26-3
Mirror 1 - Click here
Changelog (Unofficial)
System Version 2.7.29
Unknown
Previous Versions
System Version 2.7.28
Unknown
System Version 2.7.11
Unknown
System Version 2.7.9
Unknown
System Version 2.7.4
Unknown
System Version 2.6.96
Unknown
System Version 2.6.93
Unknown
System Version 2.6.77-2
Unknown
System Version 2.6.77
Unknown
System Version 2.6.73
Unknown
System Version 2.6.70
When changing panel keys or steering wheel controls, the notification bar is still displayed
New menu option for backing up and restoring both panel key and steering wheel control mappings
System Version 2.6.68
Homescreen design reverted back to four large widgets per page
App icon for SWC settings
Setting in "Extra Settings" to force USB1.1
Factory reset is password protected (See FAQ)
Developer options are password protected (See FAQ)
System Version 2.6.62
Bluetooth icon in notification bar (appears Bluetooth is turned on by default now, cannot turn it off)
Bluetooth menu, accessed via an app, has "SEARCH FOR DEVICES" and visibility option, however nothing functions when pressed
All extra applications removed (ES File Explorer, GPS Test Plus, QuickPic)
WiFi Hotspot can be activated without re-plugging the 3G dongle in
Background is winter-themed
System Version 2.6.60-2
New home screen design
System Version 2.6.60
Default applications changed back to original theme
APK Installer application install by default
Bluetooth renamed back to Phone
Screenshot feature now fixed and works correctly
System Version 2.6.40
Larger notification bar
GPS icon removed from notification bar
Home, back, menu, and screen off buttons added to notification bar
Default applications changed to red theme (music player, radio, video player, phone)
Phone application renamed to Bluetooth
ES File Explorer installed by default
GPS Test Plus installed by default
QuickPic installed by default
Non-functioning screenshot featured added in settings menu
Bugs / Issues
KeyUnresolved
Workaround
Resolved
Updated 2014.01.20Newest issues will be put at the top, solved issues, or issues with workarounds will be moved to the bottom.
Unable to remove applications that are device administrators without factory reset due to security menu being disabled.
Many applications are unable to "see" the MicroSD card, so the choice of music players is limited. The mount point is "mnt/usb/mmcblk1p1".
Despite selecting "Front Speakers Only" for navigation sound, the sound comes out of the rear speakers too. Setting to "Front Right" appears to work correctly.
Bluetooth is restricted to phones only. (Unsure if this is hardware or software related, talking to manufacturer suggests hardware limitation).
Bluetooth dongles do not work.
There is a "pop" from the speakers sometimes when changing applications that control sound, this is extremely obvious if you have a subwoofer installed. It happens when the unit is turned on, and when going from mute, to a volume level.
Screen brightness when buttons illuminated is not user-configurable. This means it may be too bright or dark depending on the conditions. For example, when it is only mildly dark outside, and you have your lights on, the screen is very hard to see.
Workaround: Enable constant illumination from the "Extra Settings" menu by setting the option to "CLOSE", this will set the keys to always illuminate. Then use an application such as Twlight to control the screen brightness based on sunset and sunrise.
Random issue when downloading large applications. The progress will usually get to more than 50%, and then no progress is made.
Workaround: The only fix I have found so far is to stop the download, reboot the unit, start the download, and repeat until download continues. It should download from where you cancelled. This appears to be caused by a limited download cache size.
Steering wheel controls only work with default applications.
Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, allowing steering wheel controls to function with other apps.
Most recent default application always opens on boot and continues to play, even if paused. This includes the radio, music, video, and iPod applications.
Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, and no default app will open on boot.
USB Debugging is password protected.
Resolved: The password is "[email protected]". Credit to @nikko82
Screenshot feature does not work, when trying to save the screenshot, a save error appears.
Resolved: This is solved in system version 2.6.60.
Root
Root is now possible thanks to help from some great XDA members.
Credits to @WonderEkin for the Root My AN-21 U app and @bmj67 for supplying SettingsProvider.apk
2014.06.06 - A new rooting tool named Baidu Root has been added to the repository. You can use this tool as an alternative to following the guide below.
Files required
Root My AN-21 U - [ Mirror1 | Mirror2 ]
Root My AN-21 U has been updated since this video was taken, the app should now correctly show "Step 2".
Download the required files above.
Install Android Terminal Emulator on your unit.
Open the AUX application and close it.
Install Root My AN-21 U and create a link on the homescreen.
Run Root My AN-21 U and press the "Step 1" button.
Reboot the unit.
Once the unit has rebooted the screen will likely be black, press the Home button to display the homescreen.
Run Root My AN-21 U and press the "Step 2" button.
Reboot the unit.
Open Android Terminal Emulator and run the following commands.
Code:
su
rm /data/local.prop
Reboot the unit.
FAQ
Can I root this unit?
Please see the "Root" section above.
HELP! My unit is stuck in a boot-loop!
Place the update files on your MicroSD card (see "Firmware Updates" section). Then turn the unit on whilst holding down the volume knob and home button. This should start the update process.
Can I use Bluetooth OBD devices with Torque?
Not at the moment, Bluetooth is only for phones and Bluetooth dongles do not work.
Does it have the full Play Store?
Yes, it has the Play Store and all compatible applications are available for download.
What is the boot time?
18 seconds to home screen, 22 seconds until music application starts. If you use the radio application rather than the music player, the radio sounds as soon as the unit receives power.
Where can I buy one?
There are many listings on eBay/AliExpress under the search term "android 4.1 car", some have resistive, and some have capacitive screens. There is also the mention of a faster 1.2GHz dual core, however the unit actually has a 1GHz dual core CPU.
How good is the radio?
The radio reception seems fine, as does the sound quality.
Is there a Wiki page?
Yes.
Tonghai Create AN-21 U Wiki
What is the USB Debugging password?
[email protected]
What is the Factory Reset / Developer Options password?
7890
What is the Extra Settings password?
123456
Orisai said:
Android doesn't have NTFS support, let alone EFS which is built on top of Microsoft's filesystem, but it's capable of using the same cypher algorithms as EFS (AES, SHA, DES) though. The only thing Android needs to be able to decrypt them during the upgrade process, is the manufacturer's or firmware developer's public key, which I believe is stored among the system root certificates.
This, providing EFS or a compatible file encryption mechanism was used to encrypt those files.
Click to expand...
Click to collapse
If we think about it, Android isn't even part of the equation reading those files really, just a bootloader or the unit's firmware. So the decription layer would have to be built into the bootloader or the raw firmware (read assembly or whatever)... I highly doubt it would be EFS.
As another observation, all filenames remain the same across the two updates and only one file has changed (and it's name remains the same. There goes the hash/sum/md5 like naming theory)...
Code:
diff android-4.1-2.6.40/ android-4.1-2.6.60/
Binary files android-4.1-2.6.40/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 and android-4.1-2.6.60/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 differ
That I'm guessing is our system file
@tin2001 @Orisai @chris.r.r <- in case you missed the switch to new thread
sciallo said:
If we think about it, Android isn't even part of the equation reading those files really, just a bootloader or the unit's firmware. So the decription layer would have to be built into the bootloader or the raw firmware (read assembly or whatever)... I highly doubt it would be EFS.
As another observation, all filenames remain the same across the two updates and only one file has changed (and it's name remains the same. There goes the hash/sum/md5 like naming theory)...
Code:
diff android-4.1-2.6.40/ android-4.1-2.6.60/
Binary files android-4.1-2.6.40/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 and android-4.1-2.6.60/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 differ
That I'm guessing is our system file
@tin2001 @Orisai @chris.r.r <- in case you missed the switch to new thread
Click to expand...
Click to collapse
Yes, as you say, it is the only file that changes between the updates, and it is also the largest file so I think we can assume this contains the data we want.
Looking at the third update I have, it seems that file is again the only one changed. I will be testing this update out and uploading it shortly.
The file names must have some importance, as otherwise they could just call them "system.img", or something simple, but still encrypt them.
KID52 said:
Many applications are unable to "see" the MicroSD card, so the choice of music players is limited.
Click to expand...
Click to collapse
Have you tried to see if it will read an external mass storage attached to usb? (usb stick, card reader, 2.5" portable hard drive)?
sciallo said:
Have you tried to see if it will read an external mass storage attached to usb? (usb stick, card reader, 2.5" portable hard drive)?
Click to expand...
Click to collapse
The default application yes, although I did not try what happens with multiple USB drives. The doubleTwist music player was unable to read a USB memory stick, or the MicroSD card. The actual unit seems to be able to cope with multiple memory sticks, I have tried three, and all were accessible using the ES File Explorer application.
The internal storage is mounted at "mnt/sdcard".
The MicroSD card is mounted at "mnt/usb/mmcblk1p1".
USB memory sticks are mounted at "mnt/usb/sda1", "mnt/usb/sdb1" etc.
KID52 said:
Many applications are unable to "see" the MicroSD card, so the choice of music players is limited. The mount point is "mnt/usb/mmcblk1p1".
Click to expand...
Click to collapse
Have you checked for the presence of a hidden file called, ".nomedia" in the MicroSD card? The presence of this file will let most media players to skip this path for scanning for multimedia files.
donaldta said:
Have you checked for the presence of a hidden file called, ".nomedia" in the MicroSD card? The presence of this file will let most media players to skip this path for scanning for multimedia files.
Click to expand...
Click to collapse
Yes, this file is not present.
KID52 said:
The default application yes, although I did not try what happens with multiple USB drives. The doubleTwist music player was unable to read a USB memory stick, or the MicroSD card. The actual unit seems to be able to cope with multiple memory sticks, I have tried three, and all were accessible using the ES File Explorer application.
The internal storage is mounted at "mnt/sdcard".
The MicroSD card is mounted at "mnt/usb/mmcblk1p1".
USB memory sticks are mounted at "mnt/usb/sda1", "mnt/usb/sdb1" etc.
Click to expand...
Click to collapse
You might want to try a few different players to see if it's the unit or the player...
From http://www.doubletwist.com/help/question/how-do-i-switch-from-internal-storage-to-sd-card/
We recommend only using one volume to store your media. If you choose the memory card, please do not store media files on the internal storage location.
Also, there is not standardized way of implementing SD card support so each manufacturer implements SD card supportly differently. This is why doubleTwist may not always support the SD card on your device.
Devices reported by users to not work includes the following devices:
LG Motion 4G
LG Optimus L5
LG Optimus LTE2
LG Optimus 4X HD
Motorla Razr i
Motorla Razr M
Click to expand...
Click to collapse
I don't know if you can without root but you should be able to as normal user in a virtual terminal link /mnt/sdcard to /sdcard
Code:
ln -s /mnt/sdcard /sdcard
... Something to try. I think it won't survive reboot, but if it works you can possibly make a script for it to happen on boot.
sciallo said:
You might want to try a few different players to see if it's the unit or the player...
From http://www.doubletwist.com/help/question/how-do-i-switch-from-internal-storage-to-sd-card/
I don't know if you can without root but you should be able to as normal user in a virtual terminal link /mnt/sdcard to /sdcard
Code:
ln -s /mnt/sdcard /sdcard
... Something to try. I think it won't survive reboot, but if it works you can possibly make a script for it to happen on boot.
Click to expand...
Click to collapse
It depends on the player.
All file explorer applications such as ES File Explorer, and Astro, have no issues seeing the files. In fact, if you choose an MP3 file and select the player of your choice to open the file, it will indeed open and play, however it does not show up in the list of available songs.
One example of a player than can see the files is Poweramp.
"/mnt/sdcard" is already linked to "/sdcard", but this is the internal USB storage, not external. Perhaps it can be unlinked, and the MicroSD card, "mnt/usb/mmcblk1p1" linked there instead.
Orisai said:
Peter's listing on eBay mentions the headunit supports wireless keyboards, which are bluetooth devices. Also, being it Android 4.1, it should support USB OBD2 scanners like this one on Amazon:
http://www.amazon.com/OBDLink-OBD-II-Interface-Adapter-425101/dp/B002M07XHO
This one is pretty expensive compared to the bluetooth ones, but I've seen it used by dealers to diagnose their cars during repairs.
Click to expand...
Click to collapse
Best to keep discussion for the 4.1 unit in this thread now.
My keyboard is not Bluetooth, it has a small receiver that is probably 2.4GHz, and it works fine.
Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...
I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Orisai said:
Have you tried a Linux compatible bluetooth dongle yet? I believe, if the headunit supports external wireless keypads, then BT dongles should work, as well as anything connected through them.
Click to expand...
Click to collapse
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
KID52 said:
Best to keep discussion for the 4.1 unit in this thread now.
My keyboard is not Bluetooth, it has a small receiver that is probably 2.4GHz, and it works fine.
Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...
I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
Click to expand...
Click to collapse
KEEP IN MIND ALL MY EXPERIENCE IS WITH THE 2.3 OUKU but this might help:
Usb Keyboard is natively supported on all of them, if it's wireless with its own dongle (not bluetooth) that's just all it is, a usb keyboard.
For the bluetooth menu install Quick Bluetooth Lite from Market. I was lucky enough one of the dongles I had lying around worked (one didn't) mine sais "KINIVO" on it.
There is a similar app on the market to use bluetooth keyboards.
...but with both of the above it all depends on the ability to add a BT dongle, the internal one is not visible to android as I understand it (and as it was with the other units OUKU, winCE etc.
I have that exact ODBII reader mainly because I wanted a reliable one that could get the most codes... off topic here, but there is differences. Torque forums are a good resource. I haven't tried USB with it yet. There is cheap usb only out there, but I guess there is two different kinds of usb-to-serial chips... you MIGHT have one of the two installed if they included it....
Bottom line, it doesn't matter what Android supports. What matters is what modules the chinese manufacturer compiled in the kernel or included as a loadable module...
You could get a hint looking at the /home/rick/OUKU/stock/4.1/test/lib/modules/ folder...
sciallo said:
KEEP IN MIND ALL MY EXPERIENCE IS WITH THE 2.3 OUKU but this might help:
Usb Keyboard is natively supported on all of them, if it's wireless with its own dongle (not bluetooth) that's just all it is, a usb keyboard.
Click to expand...
Click to collapse
Yes, exactly my thoughts.
sciallo said:
For the bluetooth menu install Quick Bluetooth Lite from Market. I was lucky enough one of the dongles I had lying around worked (one didn't) mine sais "KINIVO" on it.
There is a similar app on the market to use bluetooth keyboards.
Click to expand...
Click to collapse
Thank you for the advice, I will try it out soon, see what happens.
The info you have regarding the OUKU unit may well be relevant to this new one too.
KID52 said:
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Click to expand...
Click to collapse
No, you don't have to buy such devices just for testing purposes. I have plans on buying one for my Santa Fe i45, because USB OBD2 scanners are faster and way more reliable that BT ones, and I'll need it to plug directly into my laptop or the OTG adapter in my SGS4.
KID52 said:
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
Click to expand...
Click to collapse
Try to plug them when your stereo is turned off. I recall someone saying that you have to plug in WiFi and 3G dongles with the headunit turned off, so they get detected by Android when it boots up. Perhaps this is the case with BT dongles too.
Orisai said:
Try to plug them when your stereo is turned off. I recall someone saying that you have to plug in WiFi and 3G dongles with the headunit turned off, so they get detected by Android when it boots up. Perhaps this is the case with BT dongles too.
Click to expand...
Click to collapse
Hmm, I said that. I put it in the main post too. Maybe someone said it about OUKU too, I don't know.
But yes, I do usually turn off the stereo and plug the device in before booting.
Then it must be like sciallo said, kernel has to be compiled with the required modules to make bluetooth dongles work, much like Hal9k's firmware.
KID52 said:
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
Click to expand...
Click to collapse
Might want to get a terminal for android, like Android Terminal Emulator. Then you can check to see what sort of linux modules/drivers are pre-installed. For example:
Code:
$ lsmod
lsmod
blackberry 1084 0 - Live 0xbf10a000
cdc_acm 15311 0 - Live 0xbf100000
sierra 9201 0 - Live 0xbf0f7000
option 13120 0 - Live 0xbf0ea000
usb_wwan 8010 1 option, Live 0xbf0e2000
hso 29290 0 - Live 0xbf0d3000
tnx_mxt_ts 15886 0 - Live 0xbf0c9000
cp210x 10931 2 - Live 0xbf0c0000
pl2303 10925 0 - Live 0xbf0b7000
usbserial 26415 8 blackberry,sierra,option,usb_wwan,cp210x,pl2303, Live 0xbf0a8000
88w8688_wlan 362475 1 - Live 0xbf041000
tun 13189 2 - Live 0xbf037000
omap3_isp 97716 0 - Live 0xbf014000
omap_hsmmc 14041 0 - Live 0xbf000000
$
This will give you an example of modules installed. In the above example is from the Parrot Asteroid Smart. The output gives you an idea of the sort of devices that you'll be able to use with the unit. For example, there are the cp210x and pl2303 drivers for Serial UART to USB devices. So, for example one could use a USB ODB2 cable as long as they use either a Prolific or Silcon Labs UART.
KID52 said:
I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Click to expand...
Click to collapse
Something that is not well known is that Torque Pro supports USB ODB2 cables. The product linked earlier from Amazon is an ODB2 scanner by Scantool which is a professional model. (Analagous to buying a Fluke Multimeter vs an Innova) They do have another model that costs a little bit more and supports USB and Bluetooth or even WiFi if you prefer. But, there are some less expensive knock offs that you can get for less a fraction of the price. So, if you know the AN-21 U supports a particular Serial to USB driver then you might be able to use one with Torque Pro. The nice thing about USB ODB2 cables over Bluetooth ones is that the data stream is closer to real time and has less lag than a BT ODB2 adapter around the same price.
KID52 said:
Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...
Click to expand...
Click to collapse
Some places hide various menus from the settings control panel, but you can often them bring them up using intents through Activity Manager. However, finding the available intents sometimes requires root but you do not need to be root to execute them. For example:
Code:
$ su
su
# dumpsys package com.android.settings | grep BluetoothSettings
dumpsys package com.android.settings | grep BluetoothSettings
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068bc48
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
# exit
exit
$ am start -n com.android.settings/.bluetooth.BluetoothSettings
am start -n com.android.settings/.bluetooth.BluetoothSettings
Starting: Intent { cmp=com.android.settings/.bluetooth.BluetoothSettings }
$
However, not all Bluetooth software conforms to the Android standards and will force close if it doesn't. In most cases if a Bluetooth driver is installed then a good app to get is Bluetooth Auto-Pair. It allows the manual settings to pair various devices even if the manufacturer implements an artificial limitation on the devices that they will support.
donaldta said:
Snip.
Click to expand...
Click to collapse
You definitely seem to know your stuff!
That is an extremely informative post, thank you.
I'll take another read tomorrow and do some tests on the unit, see what I can find out.
Orisai said:
Android doesn't have NTFS support,
Click to expand...
Click to collapse
This is actually a pretty bad blanket statement. It actually depends on the Linux modules included with the Android device. And in fact, I played with an Android TV device that had fuse.ko modules installed and supported NTFS partitions. The best way to tell what sort of filesystem that your Android device supports is through "/proc/filesystems".
Code:
$ cat /proc/filesystems
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev devpts
cramfs
squashfs
nodev ramfs
vfat
msdos
nodev mqueue
nodev mtd_inodefs
nodev oprofilefs
nodev ubifs
$
The first column signifies whether or not the filesystem is currently present on your android device and the second column shows all the various types that it supports.
---------- Post added at 11:06 PM ---------- Previous post was at 10:49 PM ----------
KID52 said:
I'll take another read tomorrow and do some tests on the unit, see what I can find out.
Click to expand...
Click to collapse
While you're at it, you might consider installing SRT AppScanner. If the device is vulnerable to Master Key either exploit bug 8219321 and/or 9695860 then there's a good chance that Cydia Impactor can root your device.
donaldta said:
While you're at it, you might consider installing SRT AppScanner. If the device is vulnerable to Master Key either exploit bug 8219321 and/or 9695860 then there's a good chance that Cydia Impactor can root your device.
Click to expand...
Click to collapse
I thought you needed to connect your device to a PC to use Cydia Impactor? Also, not sure if it would be required, but USB debugging is password protected.
KID52 said:
I thought you needed to connect your device to a PC to use Cydia Impactor? Also, not sure if it would be required, but USB debugging is password protected.
Click to expand...
Click to collapse
Well, technically you don't have too. It works off of Android Debug Bridge and can work over WiFi or USB. However, it does need debugging to be enabled. I missed the part that it is password protected. However, the masterkey scripts might still be able to help gain access to root if it hasn't been patched on the device.
Is there any way to send the nook color display to a TV? With hdmi cable or wirelessly?
Is there an app that allows mirroring the display possibly?
Nook Color rooted CM7, Phiremod returns
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
HDMI is not possible. See http://forum.xda-developers.com/showthread.php?t=1287410.
gryphon101 said:
Is there any way to send the nook color display to a TV? With hdmi cable or wirelessly?
Is there an app that allows mirroring the display possibly?
Nook Color rooted CM7, Phiremod returns
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Chrome cast works, but only with apps that support it
Streaming.
I second Chromecast. The list of supported apps as well as the contents of anything in the Chrome browser are usable with more coming soon.
f1jim
If you have a ROKU the twonky beam app will send videos to your TV
Have you tried the 'Cast Screen' feature in cm11 aka Miracast in KitKat? You will need a Miracast enabled LCD/led TV. Amazon sells Miracast HDMI dongles. Go to settings, display, cast screen. There you will see Miracast TV to pair and send wireless content. I don't know if direct wi fi is enabled on the nook color yet.
Edit: WPA supplicant has p2p disabled. Missing p2p supplicant (config_p2p=y). Tried connecting to my sister's Sony 42" LED Bravia which is Miracast enabled, but no joy. See second pic.
http://wireless.kernel.org/en/developers/p2p/howto
Senior xda member s107ken has enabled Miracast for the Nexus line.
He has a great write up in his github here. He includes code for the WFD (wifi display) settings menu, modifications to framework (av and base) to modify the Nexus tablets. This might be helpful to enable Miracast for the Nook Color. As mentioned in my post above, the nook color doesn't have p2p configured in the wifi supplicant. It's one thing to be able to connect to a Miracast enabled receiver (TV, projector). It's another thing to be able to stream wireless content mirroring the nook color to the receiver. Most Miracast dongles connect to the HDMI port of the receiver. Don't know if there are USB3.0 versions. These dongles use H.264 video codec for 1080hd/5.1 Dolby Surround.
Here are the results of my attempt to add wifiP2P and WifiDisplay to the nook color
Wifi doesn't turn on in the settings menu. WPS and add buttons don't work. Everything is greyed out in the 3 dot menu except the advanced tab. There were a bunch of messages about "missing translation" in Koush/Superuser folder when compiling the wifi.display.settings.java for the settings UI. I suspect these errors are the cause. I also attached dmesg from wifi and p2p trying to connect to my AP. Address Conflict.
Remote submix is added to audio policy and hardware.
android.hardware.wifi.direct.xml is added to permisions
DirectWifi section is added to init.encore.rc
I have not made changes to video code.
See the pics attached for the file names and code additions I made. I also need to look at the wpa_supplicant to see if it is configured for AP and P2P.
Here is my second attempt to miracast the nook color.
I started this time with CM-11-Snapshot-M6. My previous attempt was made on an unofficial compiled ROM with modifications made to init.encore.rc, but there was a conflict with wifi and p2p due to the single-role firmware loaded (wl127x-fw-4-sr.bin ver. 6.3.10.0.139). Removing the single-role firmware does not work. There is an error message in dmesg stating wl12xx cannot find wl127x-fw-4-sr.bin. To get the multi-role firmware wl127x-fw-4-mr.bin ver 6.5.7.0.47 to load, I stashed the single-role firmware, copied and renamed wl127x-fw-4-mr.bin to wl127x-fw-4-sr.bin and pasted to /etc/firmware/ti-connectivity/ (see dmesg pic). Rebooted. Wifi is working at this point. I'm connected to Netgear86. My sister's Sony Bravia tv is direct wifi capable (see wifi settings pic). Without making modifications to init.encore.rc, I used terminal in root mode to find the MAC address of the Sony Bravia tv.. The wpa_cli p2p commands were able to find the MAC address (see terminal pic). Wifi is still working at this point. One step closer to miracast for nook color.
Testing with the 5/22 cm-11 nightly yielded the same error message for sr and mr wl12xx firmware.
P2P-GO-NEG-FAILURE status=-1 (see pic).
Peer cannot communicate with AP (softap or hostap). My next attempts will include softapd and/or hostapd in an unofficial compiled build.
Loaded the iw binary compiled for android to check the wifi capablilities of the wl1271 chip. Also used iw to add p2p0. The device capabilities are shown in the pics. I'm using TI reference to add p2p. Looks like nook color has p2p capabilities.
Great findings so far!
I added hostapd to the BoardConfig.mk file and compiled the ROM. CM-11 and hostapd do not play nice together. The quick settings rollup panel does not respond to pull down. I copied the hostapd binary and hostapd.conf files from the target out bin folder and pasted into my working copy of CM-11 5-22 nightly. I ran hostapd and p2p scripts using terminal as root. The results are below (see screen pics). The interface p2p0 comes up but does not connect (3rd pic). Stay tuned.
Edit: The sockets wlan0 and newly added p2p0 have permisissions set at wifi wifi. That's why the terminal returned an error (3rd pic last line). Will add to init.encore.rc and see what develops.
I did more testing today. The results are shown in the pics attached. The p2p0 socket is created. The p2p0 interface is still not connecting to wpa_cli. I suspect wifi.c is the culprit. It has a 2008 copyright. I will see if I can find an updated version. The p2p commands work with the wlan0 interface, but we need it to work on p2p0 interface.
While searching for a newer version of wifi.c, I stumbled upon something interesting. It seems there were some changes made to wifi.c to allow using p2p0 as a secondary interface for a p2p connection. These changes were made by Hashcode on December 15, 2012 and Irfan Sheriff on December 27, 2011. The wifi.c file in CyanogenMod github does not have these changes. Do they not work? I do not know. If they do work, why weren't they added to CyanogenMod's github? Is that the reason none of CyanogenMod builds have p2p? I have attached screen shots of my findings.
Shifting gears. Leaving miracast in my rear view mirror. Moving forward to chrome cast here
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
http://forum.xda-developers.com/showpost.php?p=54195946&postcount=761
Hi all
Cast screen is not working on g4 plus. Can anybody confirm if there is any additional setting. Thanks
Sent from my Moto G (4) using Tapatalk
I used cast function last night on my moto g4. no extra setting at all. When you view the photo or video, the cast icon will appear automatically if there is any paired device nearby.
I paired it with my JBL pulse 2, it shows cast icon. But m not able to pair it witj my led
Sent from my Moto G (4) using Tapatalk
you might need to sort out the pair process with your led even without playing anything.
i use google chrome. but i didn't install the chromecast app as what i did on my moto g1. but on my moto g4, it automatically found the chromecast.
you need to root your device.
1.Download Root Browser from play store.
2.Go to root directory > System folder > Open build.prop.
3.Add these two lines in the end :
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=1
4.Reboot your device.
5.Connect to your TV using wifi direct.
6.After connecting, go to Settings > Display > Cast.
7.You will see 3 dots on upper right of screen, tap it and tap "Enable Wireless Display".
8.Your TV will be listed there. Tap on it and Screen Casting will be started.
I tried adding the lines to build.prop however it is not allowing me to save it
Less than 5 minute fix to flawlessly cast my phone to pc!
wizard-dima said:
you need to root your device.
1.Download Root Browser from play store.
2.Go to root directory > System folder > Open build.prop.
3.Add these two lines in the end :
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=1
4.Reboot your device.
5.Connect to your TV using wifi direct.
6.After connecting, go to Settings > Display > Cast.
7.You will see 3 dots on upper right of screen, tap it and tap "Enable Wireless Display".
8.Your TV will be listed there. Tap on it and Screen Casting will be started.
Click to expand...
Click to collapse
Cant thank you enough!
Spent an hour downloading and installing Intel and MS bloat on PC and some half dozen apps on the phone, but your solution took mere 4 minutes to get my phone cast on to PC flawlessly.
Build prop won't save after modification everytime it fails, please help
I do This all as you said ... But still is not connect to my LG tv
wizard-dima said:
you need to root your device.
1.Download Root Browser from play store.
2.Go to root directory > System folder > Open build.prop.
3.Add these two lines in the end :
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=1
4.Reboot your device.
5.Connect to your TV using wifi direct.
6.After connecting, go to Settings > Display > Cast.
7.You will see 3 dots on upper right of screen, tap it and tap "Enable Wireless Display".
8.Your TV will be listed there. Tap on it and Screen Casting will be started.
Click to expand...
Click to collapse
As above all procedure .. its shows enable wireless display options and also shows a tv name too but after long waiting of connecting period ..its disappeared and not coonect to my LG Miracast TV
By Motorola Moto E 2 4g LTE CM 14.1 Nougat 7.1.1
Sorry for reviving an 18mo thread, but... I just received my Moto G5 Plus today, and to my surprise, the official position of Motorola/Lenovo is "It works only with Chromecast". That don't fly with me. So, I applied the two lines to the build.prop file as described above, and lo-and-behold, my Roku TLC TVs showed up just fine.
However, when I select them, I get a prompt telling me that Wifi is active and must be turned off. After accepting, the MG5 connects directly to the TV, excluding the wifi connection to my router. That means, it rolls over to LTE service.
Is there any fix to this? It's certainly better than no screen casting, and will work just fine when trying to show local phone content - but since I'm on a capped data plan, it would really suck to be casting YT videos in a home with 100mbps WIFI, and still be forced to use VZ LTE to show it.
I cant use cast too on my samsung tv
My understanding based on various forums:
I do not think it connects to LTE even if its asking for switching off wifi.
Android as an OS supports Miracast (direct mirroring protocol without common wifi router) since JellyBean. Although OS supports it, some android hardware devices cannot support Miracast without turning off wifi.
Nexus, Samsung S3,S4,S5... can support Miracast without turning off wifi in your mobile. But G4 Plus's hardware will be able to support Miracast only by turning off wifi. Hence they disabled it at the software level. So we have to enable it by rooting!
Miracast protocol does not require the mobile manufacturers to display "Miracast" logo and so nobody explicitly mentions it in their products. So no clear way to know if a device supports Miracast! But my understanding is that it is present in all android from jellybean and above (but hidden at the software level for some phones like G4 Plus because of hardware restriction that disconnects wifi while mirroring).
Some more observation which might be helpful:
Though Miracast is a common protocol, every company can have its own implementation! This means Miracast of my Samsung TV and Miracast of my G4 Plus may differ in implementation. You may ask what is the impact of different implementations - Will it work or not?
The impact is although TV and Mobile both supports Miracast (but having different implementations),they cannot connect directly without common wifi router !!!! (which is what miracast is supposed to do!!!)
My some Samsung mobile like S4567 can connect to Samsung TV without a common wifi router (same is the case for Sony and LG I think) -- This is because Samsung's own implementation of Miracast in both TV and mobile makes it to work without common wifi router.
build.prop can't be edited !
I tried to edit build.prep file, but it is not allowing me to make changes to that file. Please help !
Cast Screen does not work on LG TV
wizard-dima said:
you need to root your device.
1.Download Root Browser from play store.
2.Go to root directory > System folder > Open build.prop.
3.Add these two lines in the end :
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=1
4.Reboot your device.
5.Connect to your TV using wifi direct.
6.After connecting, go to Settings > Display > Cast.
7.You will see 3 dots on upper right of screen, tap it and tap "Enable Wireless Display".
8.Your TV will be listed there. Tap on it and Screen Casting will be started.
Click to expand...
Click to collapse
Tried the suggested changes in build.prop (after rooting) but "cast"
doesn't work from mobile (LG Nexus 5, Marshmallow, hammerhead,
Android 6.0.1, US make) on a smart tv (LG 55UC970T) with a built-in
Chromecast, purchased in India. Content sharing works with third
party apps. Under Screen Share option on TV, mobile does show
the TV name '[LG]WebOS' but soon disappears without allowing
us to click. Tried including
wlan.wfd.hdcp=disable
in build.prop but no success. Kindly suggest a workaround. Thanks in advance
The build.prop patch worked. I had to make sure Root Explorer doesnt reset file permissions and ownership (otherwise camera and torch would stop working)
I added the lines in build.prop but it still doesn't list my Roku TV under Cast.
wizard-dima said:
you need to root your device.
1.Download Root Browser from play store.
2.Go to root directory > System folder > Open build.prop.
3.Add these two lines in the end :
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=1
4.Reboot your device.
5.Connect to your TV using wifi direct.
6.After connecting, go to Settings > Display > Cast.
7.You will see 3 dots on upper right of screen, tap it and tap "Enable Wireless Display".
8.Your TV will be listed there. Tap on it and Screen Casting will be started.
Click to expand...
Click to collapse
i know this thread is old but i cant save the changes when i try to edit the build prop. How can i save the changes? Please help me.
Build prop editor method WORKS
Recommended build prop method is working as perfect. My g4 did not have wireless display option earlier. After following this, everything worked flawlessly. Thanks xda and person who suggested the trick.
Hi all,
first of all I am pretty much beginner level for Android rooting.
Actually what I want to do is play around a bit with the system files and see if I can find some way to turn off HDMI CEC. There is some post here where someone did this by modifying a file on the Amazon FireTV.
But for starters I am even failing to access the file system via my PC
I have rooted following the tutorials, I have installed ES File Explorer , I have granted root to ES Explorer when the SuperSU popup appeared (and it also shows as being granted in the SuperSU app).
Also I enabled Root Explorer in ES File Explorer.
Then when activating Remote Manager when /sdcard is set as FTP root directory I can access the file system (below /sdcard) via FTP from my PC and do see the files - so FTP access basically works and I am pretty sure there is no issue on the PC side.
However when I set / as FTP root directory and then connect from my PC via FTP (using Total Commander, FileZilla.... the client makes no difference) then I can't see anything at all, it lists an empty directory (or not even that as on an empty directory I'd have the ".." entry and I don't even have that.
Also when I try setting anything else except /sdcard as FTP root directory in Remote Manager in ES File Explorer it's the same thing.
It seems when accessing the file system via FTP I just don't have the necessary privileges to browse the root file system.
Within ES File Explorer itself on the other hand it's no problem to browse everything, there I do seem to have the necessary privileges.
Can anyone help me please, either this is an issue with rooting on the Shield or with ES File Explorer on the Shield or I am making some dummy mistake.
I have searched on Google for hours looking for a solution to this but I hardly even find people having this problem.
So now I am a bit puzzled.
How is one supposed to gain access to the root file system via the PC?
Also how do I get SSH access with root privileges?
tbh this all seems a bit strange to me, I am rooted, but it seems almost impossible to gain access to the root file system from the PC!?
I am also amazed because something like this can be achieved on any jailbroken iOS device by any beginner within 5 minutes without any issues, and I always thought for the much more open Android environment there would be 100s of entry paths and 1000s of tutorials but I seem to find hardly anything at all and after hours and hours of trying and research I still fail even accessing the damn root file system from my PC
FireAustria said:
Hi all,
first of all I am pretty much beginner level for Android rooting.
Actually what I want to do is play around a bit with the system files and see if I can find some way to turn off HDMI CEC. There is some post here where someone did this by modifying a file on the Amazon FireTV.
But for starters I am even failing to access the file system via my PC
I have rooted following the tutorials, I have installed ES File Explorer , I have granted root to ES Explorer when the SuperSU popup appeared (and it also shows as being granted in the SuperSU app).
Also I enabled Root Explorer in ES File Explorer.
Then when activating Remote Manager when /sdcard is set as FTP root directory I can access the file system (below /sdcard) via FTP from my PC and do see the files - so FTP access basically works and I am pretty sure there is no issue on the PC side.
However when I set / as FTP root directory and then connect from my PC via FTP (using Total Commander, FileZilla.... the client makes no difference) then I can't see anything at all, it lists an empty directory (or not even that as on an empty directory I'd have the ".." entry and I don't even have that.
Also when I try setting anything else except /sdcard as FTP root directory in Remote Manager in ES File Explorer it's the same thing.
It seems when accessing the file system via FTP I just don't have the necessary privileges to browse the root file system.
Within ES File Explorer itself on the other hand it's no problem to browse everything, there I do seem to have the necessary privileges.
Can anyone help me please, either this is an issue with rooting on the Shield or with ES File Explorer on the Shield or I am making some dummy mistake.
I have searched on Google for hours looking for a solution to this but I hardly even find people having this problem.
So now I am a bit puzzled.
How is one supposed to gain access to the root file system via the PC?
Also how do I get SSH access with root privileges?
tbh this all seems a bit strange to me, I am rooted, but it seems almost impossible to gain access to the root file system from the PC!?
I am also amazed because something like this can be achieved on any jailbroken iOS device by any beginner within 5 minutes without any issues, and I always thought for the much more open Android environment there would be 100s of entry paths and 1000s of tutorials but I seem to find hardly anything at all and after hours and hours of trying and research I still fail even accessing the damn root file system from my PC
Click to expand...
Click to collapse
Are you doing this to just turn off HDMI CEC? You can do that without root on stock in the settings>HDMI
I haven't rooted my Shield TV pro. I prefer it stock with the lean back launcher so I can't help accessing the root file system.
Sent from my Nexus 6P using Tapatalk
Acid0057 said:
Are you doing this to just turn off HDMI CEC? You can do that without root on stock in the settings>HDMI
I haven't rooted my Shield TV pro. I prefer it stock with the lean back launcher so I can't help accessing the root file system.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Well basically yes I am doing this only for the HDMI CEC. It is kind of a big deal in actual usage of my Shield actually.
Apparently there is a bug in the Shield firmware related to HDMI CEC, that for me (and many others) results in this behavior when the Shield TV is connected to an AV receiver.
In my case the Shield is connected to an Onkyo TX-RZ3100 and then from there to a Samsung TV.
HDMI CEC is enabled on both because if it wasn't then the ARC audio return channel wouldn't work (but this is needed, otherwise I won't have audio when watching terrestrial TV which is being received by the Samsung TV).
Now what happens is that whenever I turn on the TV, then the AV receiver also switches on via HDMI CEC (in this case this is wanted and normal behavior).
However when the Shield is connected to the AV receiver (which it normally is), then the Shield will *also* turn itself on and switch the AV receiver to the input of the Shield.
So e.g. if I want to turn on the TV to play with the PS4, then I end up with the Onkyo turning on, showing me the PS4 screen as the AV receiver is switched to the input of the PS4. But then 20s later suddenly the Shield turns itself on and switches the Onkyo to its input.
So the end result is this: whenever I turn on the TV to do anything else (PS4, satellite receiver, HTPC, cable box....) then 20s later the Shield will switch to its input and force me to manually switch back to what what I actually intended to watch.
It looks like the issue was introduced with the 5.x firmware as it didn't happen before.
Now you say I should switch off HDMI CEC via settings - however there are no settings to switch it off unfortunately.
There is no Settings/HDMI (in 5.x) .
What's there is Settings / Display & Sound / Power Control, and there you can switch "CEC TV on" and "CEC TV off", however this only controls whether the Shield will turn on (or off) the TV when switching it on/off - and I have these settings set to disabled. But this doesn't help.
Unless I am missing some other settings there seems to be no way to completely switch off HDMI CEC via the UI.
Ah so turning off CEC TV in the normal settings doesn't solve it. Yes that's the options I did mean. In Display and Sound. Sorry I can't be more help. Maybe try the app Settings Editor in the play store on the shield. It might have the settings to completely disable CEC
Sent from my Nexus 6P using Tapatalk