So I was given an amiibo display at work. I was tinkering with it and got it to go to the android settings page. where I was able to delete the amiibo app. and now its essentially useless. it has an option to install apk files from SD or USB. yet I cant run any apk files thru this option. At first I accepted the display for the amiibos inside. but now that I know this thing runs android, I really want to do something with it.
I will post all the specs below, but is there any way to run this thing into recovery mode, or even flash some sort of firmware to make it a working tablet? It has the security dongle with it, which I realized was stopping anyone else on the web from altering the device.
Even if there is no way to make this thing a tablet again, I would still like to make it do something usefull enough to donate to a local business or even a church... idk
Nothing is to farfetch'd here. if u have an idea then I'm willing to try it.
ABOUT TABLET:
CSR version - A003_20160304
MCU version - V20140829
Model # - DT185-ACA-720
Android version - 4.1.1
Baseband version - 1.5rc5
Kernel version - 3.0.8+ Sat Aug 1 17:29:06 CST 2015
Build # - crane_hw_general-eng 4.1.1 JR03C C20160503U
There is also a STUPID amount of ports underneath for various plugs.
And sorry if this is posted in the wrong spot, I wasn't sure where to post this
Here you go! I figured something out!
Rororoolz said:
So I was given an amiibo display at work. I was tinkering with it and got it to go to the android settings page. where I was able to delete the amiibo app. and now its essentially useless. it has an option to install apk files from SD or USB. yet I cant run any apk files thru this option. At first I accepted the display for the amiibos inside. but now that I know this thing runs android, I really want to do something with it.
I will post all the specs below, but is there any way to run this thing into recovery mode, or even flash some sort of firmware to make it a working tablet? It has the security dongle with it, which I realized was stopping anyone else on the web from altering the device.
Even if there is no way to make this thing a tablet again, I would still like to make it do something usefull enough to donate to a local business or even a church... idk
Nothing is to farfetch'd here. if u have an idea then I'm willing to try it.
ABOUT TABLET:
CSR version - A003_20160304
MCU version - V20140829
Model # - DT185-ACA-720
Android version - 4.1.1
Baseband version - 1.5rc5
Kernel version - 3.0.8+ Sat Aug 1 17:29:06 CST 2015
Build # - crane_hw_general-eng 4.1.1 JR03C C20160503U
There is also a STUPID amount of ports underneath for various plugs.
And sorry if this is posted in the wrong spot, I wasn't sure where to post this
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/help/commercial-grade-android-tablet-issues-t3594279
Related
Hi,
I am new to this forum, I am having a problem in my mobile Bluetooth receiving mechanism for which I need your expert opinions.
The problem is that when someone (either through PC / mobile) send multiple files through Bluetooth to my mobile I have to accept each number of files separately by going again and again in the notification area and after clicking the file and click 'accept'. In short if someone send me 5 files I have to go to the notifications 5 times and have to click accept 5 times as well.
I want to know is this the standard feature or I have some problem in my set? I am not using any apps for this purpose just using the standard feature of the set.
Kindly help me in this regards.
Following are the details of my Android Set:
Set Name : Star A5000 Android 2.2 Dual Sim
Model Number: e1000_pxht2 2010/11/16 11:8:23
Android Version: 2.2.1
Baseband Version: MAUI.10A.W10.48. 2010/11/29 22.57
KERNEL VERSION: 2.6.32.9
[email protected]#1
thu Dec 16 14:03:12 CST 2010
Build Number: ALPS.10Y.W10.48 p27.MP.VO
thats just how Bluetooth file transfer works bro. You could zip up the files and just unzip it when you receive them.
I have checked the same feature on another Samsung android phone and the phone receive continuously all the files without separately accepting the files in notification area.
yeah well Samsung is crap anyway so don't be mad you don't have a Samsung its just the Bluetooth that ya got and the company that made your os hasn't enabled all the bells and whistles its probably a dated most general version available. Nothing you can do other than check out the different apps if there are any availble. Or archive the files and unzip them so you only have to do it once. I don't know much about the device you have but not everything is capable of doing 100 things at once. Patience my friend patience.
If anyone know please answer the question.....
Question: are those sending devices already paired with your phones ?
Try 1: Mark the sending device as "trusted" after you pair (might depend on your device how to do it in the bluetooth settings), this way no further notice will appear in accepting the files that you are getting from the other phone or pc.
Try 2: Use a 'folder browsing' (not 'object push') profile for transfering files.
Take a look at this neat program to handle bluetooth connection from your PC, I find it really useful (free & lightweight & works)
ObexCommander
I'd bought this WE a little box from Engel Axil with Android 2.3.
This box is powered by an ARM CORTEX (armv7) processor with 512Mo of RAM and 2Go stockage.
More info HERE.
I'd installed openssh and I can see the return of 'uname -a':
Code:
Linux localhost 2.6.34 V1.3.0-70-gee2481e(20120217.100957) armv7l GNU/Linux
A spanish community seem to have succeed to make a ICS release for it HERE, but they don't say anything about the procedure to install this.
Is there somebody here which will be able to explain me how to upgrade my Engeldroid ?
With 'busybox installer' and ssh terminal, I am able to get root access.
Now I try to set the default home launcher to something else than original spanish launcher....
I'm interested in this too!
The EngelDroid 1007M looks just like what I need, but I don't like that its software is in spanish.
maisondouf said:
Is there somebody here which will be able to explain me how to upgrade my Engeldroid ?
Click to expand...
Click to collapse
Hello Guys,
I'm living in Spain myself and bought me one of these nifty boxes as well and started to fizzle around with it.
Here are my findings with it so far:
Android:
The box comes standard with Android 2.4.3 (or was it 2.3.4, I'm at work right now and can't remember correctly ) but can be upgraded to a 4.0.3 version that is made by Mygica.es.
The link to download the upgrade is indeed the link you've posted.
To install this upgrade you will need to download the zipfile, rename it to update.img and copy it to a clean SD Card.
Make sure that the Engeldroid is powered off and put the SD Card in the Engeldroid.
Than take something pointy and press and hold the reset button on the back (the smal little hole) and plug in the power connection to boot the Engeldroid in update mode. You can release the reset button when you see the restore-android-logo appearing on the screen.
The droid will now look for the update.img on the SD Card and start updating your box. There will be a random offset message but that is nothing to worry about and does not give any problems with the installation.
The first time after installing this new Android version the unit will take up to 15 minutes to boot it due to installing all settings and default apps from this custom rom.
The normal remote control with the keyboard on the back won't work anymore, but the motion controller will. It is highly advisable to connect a wireless keyboard and/or mouse or combination. Myself, I'm using a Logitech K400 keyboard/touchpad combination which works flawless.
Another option for the Media Center tweakers would be to install Linux with XBMC on this.
It is nowhere comfirmed but that is how I am using my Engeldroid at the moment and it turned my droid box into a proper XBMC media center and Samba file server that shares all my movies from the connected disc on the network as well.
The install procedure is the almost the same as with the other ROMS, download, unpack the zipfile, make sure the file is called update.img, copy to the root of the SD Card, plug it in and reset the droid with the reset button hold.
The link for the specific build of XBMC Linux that is working with our droid I can't post here yet, but search on google for: Pivos XBMC-Linux Beta 100912 and you will find the Pivos forums with the release topic of this ROM.
Don't try the Android ROM from Pivos, it is not compatible with the Engeldroid EN1007M. No worries if you want to try it, it won't blow up our box but just won't install.
If you have any more specific questions, please ask or send me a message or email and I will get in touch with you.
Official update
There is an official update for this device to ICS 4 (site in spanish though)
engeldroid . com
Got to "Nueva ROM Android 4 ICS" --> "ROM Android 4 ICS" (I'd link it but I don't have 10 posts yet )
Hi, I'm having troubles with rooting my GooApple V5+.
I've tried multiple ways like "SuperOneClick v2.3.3.0", "AnexonelChineseRootRec(3gand2g)" and "MTKdroidTools 2.3" but it never succeeds on rooting. And I also installed Android SDK and did the 2.3.3 update. At the bottom of the post I typed all the info I can get of my phone.
-----
SuperOneClick v2.3.3.0:
Click to check the image
Process:
1. Install Android-SDK , Update to 2.3.3.
2. Copy the files in SuperOneClick v2.3.3 to the android-sdk folder.
3. Check USB debugging, Stay awake, Allow mock locations and Unknown sources
4. Unmount SD Card
5. Connect the phone to my PC with USB
6. Start SuperOneClick v2.3.3.0 as Administrator and click on Root.
5. When it freezes at step 7, I unplugged the USB cable and plugged it back in and it says END.
- Not working
-----
AnexonelChineseRootRec(3gand2g)
Click to check the image
Process:
1. Install Android-SDK , Update to 2.3.3.
2. Copy the files in AnexonelChineseRootRec(3gand2g) to the android-sdk folder.
3. Check USB debugging, Stay awake, Allow mock locations and Unknown sources
4. Unmount SD Card
5. Connect the phone to my PC with USB
6. Start root-rec.bat and press a key. After it tries to copy Superuser.apk, my phone reboots.
- Not working
-----
MTKdroidTools 2.3
Click to check the image
Process:
1. Install Android-SDK , Update to 2.3.3.
2. Copy the files in MTKdroidTools to the android-sdk folder.
3. Check USB debugging, Stay awake, Allow mock locations and Unknown sources
4. Unmount SD Card
5. Connect the phone to my PC with USB
6. Run MTK Droid Root & Tools v2.3.0 as administrator.
7. Click on ROOT
-----
Info that MTKdroidTools gives me
Hardware : MT6575
Model : Android
Build number : ALPS.GB2.MP.V2
Build date UTC : 20121109-142422
Android v : 2.3.6
Baseband v: MAUI.11AMD.W11.50.SP.V2, 2012/05/02 15:56
Kernel v : 2.6.35.7 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 Fri Nov 9 22:19:59 CST 2012
Info that the GooApple V5+ gives me
Build number: 5.0.1 (9A406)
Build date: 2012/11/10 5:19
Model number: 4GS
Info that MobileUncle gives me
CPU: ARMv7
Hardware: MT6575 rev 65fb8a00
Kernel: Linux version 2.6.35.7
SDK: 10
Release: 2.3.6
Display: ALPS.GB2.MP.V2
If you need more specific info, you can always ask me !
By the way, does anyone has a ROM for this phone or the original files on the SD card? I accidently removed them by finding out how to root this...
Thanks !
Just tried z4root and doesn't work either. It says
Sorry!
The application z4root (process com.z4mod. z4 root ) has stopped unexpectedly. Please try again.
Getting desperate here !
-------------------------
Has been rooted : http://forum.xda-developers.com/showpost.php?p=36078598&postcount=192
At least I'm not alone with this
Hi!
I'm waiting for the V5+. It will arrive in about 20 days and have been investigating the rooting problem.
It's quite frustrating to read that everything I had in my list have already been tried by you unsuccessfully
I will continue reading in forums, but my question is if no matter I do with it I can restore factory settings pressing inside the 3.5mm audio jack?
Thanks a lot for your comments, I hope this issue will be fixed soon.
Hey Q, the ROOTING of this phone finally works, but I should improve my tutorial a bit as some didn't understand it and that day I was pretty euphoric.
You can also improve internal storage but I think the phone boots a bit slow then & works a bit slow too + lot's of apps just close out of nothing.
Another thing I'm trying to figure out is getting GPS to work. Maybe I should wait about 10-20 min untill I have a GPS signal I don't know but I'll see into that.
I'm just waiting now untill I recieve a second GooApple V5+ so I can backup that phone and restore it on mine as I want to have it stock and start all over again.
Thanks for replying,
That's great that you found a way to root V5+.
Your tutorial will be very interesting indeed.
About GPS I planned to install iGO Nav&Go for Android.
I have no idea about the GPS chip of the phone, but if it is SIRF maybe can change protocol from NMEA to SIRF improving dramatically speed.
I did it in my ASUS P535 Wmobile and perhaps can find for Android
for instance SirfTech+2.22
But I'm beginner in Android, V5+ will be my first ...
No problem man.
I've got Sygic atm but I just can't get a GPS signal, even for 20 minutes :/
Now I'm hoping someone else finds out why this is happening as I would like to use Sygic Offline in my car (if its possible).
& Yeah this is my first Android too & liking it !
Regarding GPS malfunction, I found in some chineese web, information pointing an interference problem concerning Gooapple V5 GPS receiver and Wi-Fi (BT perhaps too).
Maybe you can see satellite signals with all systems disconnected (phone, WiFi and BT)
"Q" said:
Regarding GPS malfunction, I found in some chineese web, information pointing an interference problem concerning Gooapple V5 GPS receiver and Wi-Fi (BT perhaps too).
Maybe you can see satellite signals with all systems disconnected (phone, WiFi and BT)
Click to expand...
Click to collapse
WiFi works ok but you have to get pretty close to the router to get internet.
BT works fine for me
But GPS is a pain, I've tried copying a new gps.conf to /system/etc but no help
I tried GPS Status & Toolbox to reset & download AGPS, no help either...
I also tried a new ROM but no help either :/
Hi.. I have been trying to fix a tv stick for a few months now (basically is more about the knowledge i am getting - I am not desperate in fixing it). It is a strange piece, probably clone that i have been tricked in buying. It has an Allwinner A20 dual core cpu with an AP6210 wifi module...
Tried to flash another firmware ti improve it, ended up with the wifi problem. Wifi (and bleutooth) will not start. When i press the button, it just slides back to off... I have read and tried anything i could find on the internet. I have also tried tens of firmwares, but the wifi problem persisted (the original firmware is nowhere to be found).. To cut the story short, the device will not connect to a computer through ADB (it just doesn't seem to support this function - is not a matter of drivers). So everything i have been trying did not include this option...Also the recovery can not be changed to support backup and restore from custom recoveries (i.e CWM, or TWRP)..
What i did manage was to extract a backup from the rom, of another identical device, with the Nandroid App (online version, not through the recovery). Then i used the Dragonface program to edit another similar firmware (MK808C). While loaded, i open the FSOP folder which is the folder that dragonface collapses the loaded firmware for editing and then, i replaced the existing system folder with the one i had backed up trough the Nandroid procedure... Then hit the save button of the Dragonface...
I flashed the new *.img to my tv stick with the phoenix tool, and the tv stick booted normally, looking EXACTLY the same as when i first bought it. I even managed to get the bleutooth going this time, BUT, the bloody wifi still refuses to come on :-/
I must tell you, I know my way through some computer technical stuff but I am not an expert into the coding level and i haven't had the experience of Linux systems (thus i don't really understand coding). I really thought all settings and drivers are included in the system file and copying the original system file into another firmware, would do the trick.. but i guess is not that simple... The thing is that, the way i see it, the problem is probably hidden at the booting level... hitting the system configuration in the advance settings of the Dragon face, will open some coding thing which i don't understand.. but i do see the AP6210 module in that coding, which means that the new firmware includes those drivers..If anybody have any idea or can point me to the right direction I would really appreciate it.. Thanks
I have the same problem with AP6210 on H3 Allwinner STB box. After firmware ugrade from Android 4.4.2 to Android 10 Wifi just don't work, button slides back to off. Drivers are present. Have both firware files unpacked.
Please help! What i have to do? Sys_config? Init.rc?
Ok, I decided that we need to collect the different ROMs made by the DEVs and sort them into 1 place.
What I like to do here is to try to explain the different ROMs Kit Kat and Lollipop by Malaysk, ###8310 and Booroondook.
And while we now know that MCU's need to stay via KLD, KLD2, KLD6 etc, you can upgrade within those parameters with only changing factory settings (KLD6-V2.83 to KLD6-V2.97 is ok)
I have played with these roms and follow an certain rule.. Before you go from Factory to a custom rom, take pictures of settings and factory settings.
Don't update unless you are sure you know how to revert back. Know what buttons to push. Know what screen resolution your unit is! All those minor points.
All the roms we are talking about look like a filename as "update.img". 4.4.4 and 5.1.1 all for MTCB and MTCC are called out this way. I do believe MTCD is something different (dupdate.img ???)
MCU for MTCB and MTCC are "mcu.img".. and are found on the file servers as KLD?-V2.?? .. sub your version (others are available)
The fileserver can be found under typos1 name on most posts. I will link it soon.
I would suggest you read his very informative wiki as well.
Malaysk (MTCB 4.4.4 and 5.1.1) is probably the most popular ROM here. He and like the other DEVs make the ROMs to their liking's. They will on occasion add suggestions to the ROM image if they think it is beneficial.
Malaysk and ###8310 (MTCB to MTCC fake out via xPosed does a reboot once to complete loading) will have 2 files to chose from which are for resolutions. 800x480 and 1024x600. Choosing the wrong one will make the your display look awkward. (reason to know how to get back into recovery if you make this mistake)
Booroondook has a setup that creates the resolution size, thus 1 file to get and run and answer questions.
Bloatware may be added to customize roms. The reason they are customized.. Right Even factory roms have it, don't like it.. well...
So little memory, so many apps.. 1g, 2g.. well Malaysk does the FUSE trick which opens up the full memory. Booroondook, I don't recall, maybe maybe not. ###8310 has it set to 3g right now I think, but I think there might be choice of default.
Malaysk has customized Launchers. JY5.1.1 typically (one other too)has a speed display on his 4.4.4 and 5.1.1 roms
Booroondook has a few and DSA8310 is mostly clean and factory based (Klyde)
###8310 uses what factory firmware uses. The Windows like and some other with the old time flip card time piece.
You may install the rom image via MicroSD card (plugs normally into the GPS slot) or the USB port 0 (Normally the Mini port front plug thingy behind the door)
If you have update.img with mcu.img, both will get programmed to the device.
If you are going from factory to any rom, you should do the wipe data/factory cache option after the rom is flashed. You can do this anytime after the reboot. And the 1st reboot takes a long time.
If you go from and DEVs rom to another, do the data/factory cache wipe option as well, in fact you can do this anytime you update.
Stopping here since at work and will edit and add later. This is the start.
##8310, Typos1 and others, I like input..
If you had a problem and fixed it, let me know
Hands Free Messaging
If you want to hear and reply to messages on your radio from your cell, get the app from Google Playstore readitotme and install on your phone
Under Profiles: Make sure you link it as "CAR KIT" and enable it
And set to BT Mono
If you want voice reply, enable that (you get 2 weeks free) and you'll need to download addition app
It will automatically use your Messages app on the phone for the app. So under the Apps, do not enable it.
But you can select additional apps and how you like to hear them Header, message etc
Under Contacts, you can also what to hear.. One area has ALL, so selecting anything under that will enable ALL contacts with that feature.
Other features and more stuff are listed, but this should work fine.
Adding Launchers from 5.1.1
5.1.1 update.img:
Both Malaysk and Booroondook load their images with a few launchers. If a launcher is in their ROM image, you can grab it from the image by using a program called "RK3xxx Firmware tools" (google it)
Simply load the update.img via the tool (select Img... box) , extract it (Extract under Firmware image tools), then extract again under System.img tools.
Then "Open folder..."
Locate folder "priv-app"
Find the launcher you like (Launcher2mtc3_5_1_1) example
copy to a USB flash drive
Some launchers use weather on their screen, so grab the weather one too folder "app" (MTCWeather) and copy to the USB Flash drive
take the flash drive and reverse the procedure.
To copy from the USB flash drive to the system, look for "mnt" in root of the device. Find the usb drives and locate your drive.
Copy the MTCWeather to "app" (this will make it appear in the apps folder) and set permission to 755 for folder and the apk in the folder 644 using Root Explorer
Copy the (Launcher2mtc3_5_1_1) launcher to "priv-app" folder and set permission to 755 for the folder and the apk in the folder to 644
Reboot
I have been trying to get the JY5.1.1 speedo to work.. ran out of time.. WIP
Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)
Radio had MAL 5.1.1 800x Aug file.
Fuse vs Standard RAM
1st: Flashed MCU from V2.97 to V2.91
2nd: Flash Factory ROM.
Reboot had issue,
3rd: Did a Data/Factory Cache and Wipe..
4th: Flash Factory ROM again.
5th: System rebooted to Factory Images
Results are that V2.91 and Factory 5.1.1 works fine. Will be adding apps and place JY5.1.1 launcher soon. (Can't, no root!)
The settings retained Factory settings
The About Device says MTCC -KLD6-V2.91 5.1.1 800x480
Its all good from MTCB
Oldpapa49 said:
Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)
Click to expand...
Click to collapse
Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...
Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?
eblackie said:
Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...
Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?
Click to expand...
Click to collapse
MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image.
I use to have KLD6-V2.81, Pumpkin told me they had a newer one and it is KLD6-V2.91. I have installed KLD6's 2.83, 2.85. 2.91, 2.95 (I think) and 2.97
Just remember to get your FACTORY Settings recorded. so you can set the right info.
MCU file are not attached to any ROMs by any Dev.
Dev roms are rooted and they supply a remap apk for keys. I have never used it.
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1. But make sure you have all the info settings in factory, Very important!
I'm just a basic person and like certain things... So I look and set my HU to my likings.
I change my ROM evrytime a DEV makes a change to tests. I'm on MALs latest 4.4.4 ..
Note: I rarely use radio, I use Sirius App. Radio signals stink where I live.
Oldpapa49 said:
MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image. *i did*
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1.
I'm just a basic person and like certain things... *so am i*
Click to expand...
Click to collapse
Thanks for this detailed answer! As i know now i can step back to 4.4.4 i will give it a try, maybe things are a bit faster then.... i also read in a Xposed thread, dsa8310 plans something about resoldering bigger RAM's, sounds interesting! Maybe i can find one who can do this for me and take away the laggyness, but first i want to do this Sound-Chip-Mod which looks easy to do, as this unit here has only poor sound and settings to offer... If the device survives, i will play around with the rk3xxx_firmware_tools
Oldpapa49 said:
MCUs are improvements...
Just remember to get your FACTORY Settings recorded. so you can set the right info.
... But make sure you have all the info settings in factory, Very important!
Click to expand...
Click to collapse
Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.
So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.
Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).
2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).
Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.
dhmsjs said:
Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.
So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.
Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).
2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).
Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.
Click to expand...
Click to collapse
Ina cases of issues with/after loading mcu.cfg (problems, incomparibility,...) you may reset my to default (factory default / clear) state by creating empty mcu.cfg (don't forget to check permissions)
Empty MCU.cfg forces MCU to reinitialise ... At least Russians are saying so, in some previous MCU vers, I didn't check in code for myself
Truck with empty MCU.cfg reset us better than reglazing my as reglazing is not overriding that particular memory area of config params
Call Home...
Ok, I have tried this on 4.4.4 and 5.1 (both roms)
1. Works better on 5.1 and not 4.4.4. It seems to crash google using 4.4.4 unless I did something incorrect.
2. You need to get the mtcservice (headunit 2.34 or 2.35) to make it function. I tried the one off playstore and I just don't really know about it.
When you use the mic to call the 1st time, make sure you select 'mtcsevice' (steering wheel icon) to make calls. It should complete after.