yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units General] dhmsjs:
You might be able to flash the current MCU chip directly while still on-board. To do this you would connect a 3.3v UART device to pins 18 & 19 of the MCU and to your pc, run STC's ISP programming tool on your pc, and then cycle power to the chip. This is referred to as "ISP" programming in the STC device documentation. That documentation also says that MCU pins 20 & 21 need to be temporarily grounded to get the MCU to power up in ISP mode.

An English version of the STC ISP programming tool is available for download from STC's website. Note there is also an open-source STC programming tool "stcgal" (written in Python 3) on github that does the same thing as the STC tool, and more. stcgal will run on both linux and windows systems (needs Python 3 and Python 3 setuptools installed).

To program the MCU this way you would also need to convert the mcu.img to .bin, which you can do using dark simpson's mtcmcutool.exe
[MTCB Android Head Units General] shawndak:
Read through this! http://xdaforums.com/android-auto/m...d-kgl-unit-t3457538/post68656680#post68656680
[MTCB Android Head Units General] Kayhan 17#:
Hi,

i am trying to fix my MTCD HU and did the UART method but flashed the img as .bin, of course it still doesnt works and i think i need to convert it as you say, but how can i convert my dmcu.img (PX3) as mtcmcutool.exe prints this "Input file is too big, not looks like valid MCU FW image!"

Any hints are appreciated, thanks
[MTCB Android Head Units General] marchnz:
Resellers provide encrypted mcu images.

New mcu tool in mtcd forums that can decrypt MTCD firmware - search for it.
[MTCB Android Head Units General] Kayhan 17#:
Hey Mate,

i searched using google and also inside the forums, either i am using the wrong keywords("mtcmcutool" "mtc mcu" "mtc mcu tool" "mcu tool mtcd") or it simply doesnt exists?

i somehow found yesterday the mtcmcutool.exe in v1.0 but was not even able to find it using the forums search(google...)...
[MTCB Android Head Units General] marchnz:
xdaforums.com/showpost.php?p=75097741&postcount=383
[MTCB Android Head Units General] Wadzio:
And https://xdaforums.com/showpost.php?p=74989848&postcount=343 with link to this tool.

BTW

Flashing such a unpacked image will not help you.

As I wrote in post quoted by @marchnz, there is a bootloader that uploads the unpacked image and runs it

At the moment I do not know if someone has such a bootloader that could be flashed to the MCU first

If someone has it, I will gladly dowonload too :)

The only solution for the moment I see is to ask the seller.
[MTCB Android Head Units General] Kayhan 17#:
delete this, i see Wadzios message now.. :(
[MTCB Android Head Units General] dhmsjs:
Just to clarify for anyone reading this thread, the info I posted above applies ONLY to MTCB/C, and NOT to MTCD. The older MTCB/C units use an 8051-type processor for the MCU, while the MTCD units use an ARM processor.. The instruction sets for these two processors are completely different. Also the 8051-type processor is limited to 64k memory space, while the ARM processor is not. This is why the MCU flash images for MTCD units are larger than 64k, why mtcmcutool.exe gives that "too large" error message, and why you can't use an MCU image from MTCD in MTCB/C, or vise-versa.
[MTCB Android Head Units General] cs-x(RU):
In addition, this method allows only to restore the work of the bricked MCU, because the firmware upgrade from the recovery mode will not work
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
It's a minor nuisance, but it did work with my last factory image, the first Marshmallow official image, but since I've been using AOSP it never switches automatically to roaming when I cross the border. I can switch to other available carriers manually, but my home carrier is still in the available list (with 0 signal strength), and since it my home carrier, it selects it automatically. I've got used to switching manually, but I am still curious why this can happen. I've looked at the radio logs, tried to examine the source, but I just can't find an obvious code bit that could result in this bug.

It's not easy to debug, or to make some extensive debug log (because it's not easy to simulate a border crossing. Or is it?), but if you have some ideas, I would be thankful

I've never tried this with other AOSP based roms, that's why I'm interested in your experiences.

Thanks.
[Nexus 6 Q&A, Help & Troubleshooting] Dopamin3:
I have Sprint Framily plan and there are very few places near me that I don't get signal. I don't run stock, but primarily run ROMs based on AOSP (Dirty Unicorns right now, but Pure Nexus and AOSiP in the past too). When my signal was non existent, I went into roaming fine on Verizon 3G with no issues. In a certain movie theater and certain sports bar I don't get signal but roaming worked fine. Leaving the places it switched back over to Sprint. I've never tried it outside the United States though.

Did you double check under Settings -> More -> Mobile - that the two options "Data roaming" and "National data roaming" are set to enabled?
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
No, I don't use data roaming, it's expensive as heck, so I always keep it switched off. No it's just simple connecting automatically to foreign carriers.
[Shield Android TV Q&A, Help & Troubleshooting] derern:
Dear all,

I guess we all agree that the SATV is one hell of a machine in terms of value per money, especially hardware-wise. However, being sold with only Android TV doesn't unlock its full potential, so people went on and flashed Ubuntu or L4T on their Shields.

As far as it seems GPU support was always missing due to Nvidia not releasing their sources.

However, that changed in February (hxxp://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=8d1fd61a3723ab8cb6b7bfeb8be38e16282cc1ed) and was even patched in March (hxxps://lists.freedesktop.org/archives/nouveau/2016-March/024305.html) for re-clocking.

I wonder now why it has not been incorporated or am I missing something?

I have to say though that I'm not a coder myself. Otherwise I'd love to do it on my own.

Best,io
[Mate 8 Q&A, Help & Troubleshooting] gardegas:
Hello,after rooting my Mate 8 i can't turn it on in dowload mode anymore because the TWRP keeps popping up and the download option is absent in the reboot menu. Did the root change the sequence of the keys? No longer vol+,vol- and power?Do you have any suggestion please? My phone is in bootloop and the download mode is my only way out. Thanx in advance for help.
[Mate 8 Q&A, Help & Troubleshooting] Electribe:
Hello, i have the same problem. Did you solved is?

Thanks
[Mate 8 Q&A, Help & Troubleshooting] franzyroy:
When you want to go into the download mode, did you plug the µUSB cable? I know that I can't enter inside without that.
[Mate 8 Q&A, Help & Troubleshooting] Electribe:
Yes the USB Cable is plugged in during the entering download mode.
[Micromax Canvas 2 Plus A110Q] nilesh.mcse:
I have rooted my Micromax A110Q Canvas 2+ with CWM Recovery. Some days ago I have installed Freedom ape and tried to use it. But after that my mobiles crashed & not a single google services working. Please help how to restore my google services...
[Micromax Canvas 2 Plus A110Q] nilesh.mcse:
Please someone help...

I have tried everything..:confused:
[Android Q&A, Help & Troubleshooting] metahex12:
Can someone help me? :(
[Android Q&A, Help & Troubleshooting] Trafalgar Square:
Hello,

this is a source error and you have to wait for the developer of your ROM to fix that.

Kind regards

Trafalgar Square
[General Topics] Swissfyre:
Content removed by Moderator.
[General Topics] Darth:
Tesla is a feature of Nova prime. Therefore, you must be distributing a paid app.

Not on XDA please. Thread closed.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] steven3804:
Hello

I have an android ze500kl M

I try to enter the command "adb shell sm set-force adoptable true"

This puts me at end of line "error : java illegal"

what to do ? Thank you for your answers !
[Tilt, TyTN II, MDA Vario III General] sherpa:
I'll start with how I have mine setup right now.

Just thought I would enlighten others on how to accomplish this! :)

I used three files from my XP system: moricons.dll, pifmgr.dll, and shell32.dll. All these files can be found under c:\windows\system32. Basically, just copy these files to your device's \windows directory. Then, use the icon shortcut file in the Games folder and edit them as you would like.

Here's how I have mine setup:

Applications: 1#shell32.dll,-278

GPS: 1#pifmgr.dll,-35

Internet: 1#shell32.dll,-14

Multimedia: 1#shell32.dll,-41

References: 1#moricons.dll,-108

Utilities: 1#shell32.dll,-274

Edit the icon files as shown and place them in respective folders. That is it! I left the Games and Office folders as they were.

Note: shell32.dll is pretty big (around 8.5MB). In case you already did not know this, enjoy this tip. ;) :)
[Tilt, TyTN II, MDA Vario III General] johanromijn:
And how do you read the icons from the DLL file?

You can't guess that you have to use -14 for an internet icon. Do you read the DLL's on your pc, or can you do that from your PPC?
[Tilt, TyTN II, MDA Vario III General] wizzzard:
Isn't this like using a sledgehammer to crack a nut? 8.5 MB just for a few icons. I'm sure a smaller solution is possible.
[Tilt, TyTN II, MDA Vario III General] sherpa:
Haha...of course! :D I just tried it at work this morning. I will definitely be looking into smaller dll files for this once I get off work. :)
[Tilt, TyTN II, MDA Vario III General] xmoo:
Looks good, but no need for me :P
[Tilt, TyTN II, MDA Vario III General] strikeone:
Just a quick thanks to sherpa, wizzzard, and vijay555 for the info on how to change icons...works great on AT&T Tilt, and in QuickMenu 2.7!
[Miscellaneous Android Development] ottmi:
This ROM is a genuine CM13 build from source for the Elephone Trunk. It's based on mdeejay's Ark Benefit code with modifications by @BlueFlame4 and @hisname. The source code is available on GitHub.

Working:

Phone

Mobile data in dual-sim configuration

Wifi

GPS

Bluetooth

Audio

Known Bugs:

Torch tile in the status bar is not available

Haptic feedback on soft buttons

XDA:DevDB Information

CM13 for Elephone Trunk, ROM for all devices (see above for details)

Contributors

ottmi, siljaer

Source Code: https://github.com/ottmi/android_device_elephone_trunk

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.10.x

Based On: CyanogenMod

Version Information

Status: Beta

Current Beta Version: 20160902

Beta Release Date: 2016-09-02

Created 2016-06-07

Last Updated 2016-09-02
[Miscellaneous Android Development] ottmi:
Changelog

20160902

First try to fix sdcard issues, will need more testing

Fix thermal-engine to actually start

Fix audio_effects.conf

Tweak auto-brightness

Enable OTA updates

Use Wileyfox Swift blobs for everything but camera

Update to latest CM13 source

20160816

Enable thermal-engine to fix overheating emergency shutdowns

Update kernel to latest MSM8916 to fix Quadrooter vulnerabilities

Re-enable AEC audio effects

Update to latest CM13 source

20160811

Revert changes to mixer_paths.xml and audio_effects.conf to fix echo problems

Update to latest CM13 source

20160803

Update to latest CM13 source to fix surfaceflinger crashes

20160803

Tweak GPS settings to obtain faster locks

Enable input event for headphone jack

Use ACDB libraries from Wileyfox swift, fix some ACDB-related settings

Update to latest CM13 source

20160722

Incorporate [MENTION=7529884]siljaer[/MENTION]'s modifications to mixer_paths.xml to fix echoes and low volume audio recordings

Pull in additional permissions to reflect actual hardware of the phone (light & proximity sensor)

Change screen density to 300dpi

Backport LZ4 compression from Linux 3.12 for use in ZRAM

Try to fix Torch problems by restarting media service after full boot

Update to latest CM13 source

20160708

Fix wpa_supplicant crashes

Update to latest CM13 source

20160706

Switch to generic CyanogenMod MSM8916 kernel

Use Wileyfox Swift kernel configuration as template

Increase partition sizes of system and data to 1.8GB and 12GB

Update to latest CM13 source

20160630

Fix bug in libstagefright properly

Fix sensor glue code to only show actually existing sensors

Fix device permissions

Use own key to sign code instead of testkeys

Set selinux to enforce

Update to latest CM13 source

20160616

Fix mediaserver crashes to a bug in libstagefright (roll back to commit 8f270dc)

Use Adreno binary blobs from Wileyfox Swift (which are more complete)

Update to latest CM13 source

20160614

Enabling of Qualcomm Fluence as suggested by [MENTION=6709669]Bingo Bronson[/MENTION]

Backport of the F2FS driver from Linux 3.12

Enabling of LTE as preferred network on 2nd SIM card as well

Some changes to the auto brightness thresholds

Update to latest CM13 source

20160611

Enable haptic feedback on soft keys

Change default device name for wifi direct and hotspot to "Trunk" (not Benefit!)

Update to latest CM13 source

20160606

Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings

Update to latest CM13 source
[Miscellaneous Android Development] ottmi:
Flashing Instructions

You will have to disable the bootloader lock first:

Enable developer options in Android by tapping the Build version in Settings > About 7 times

Check "Enable OEM unlock"

Next you will have to boot into TWRP, use [MENTION=4729636]hisname[/MENTION]'s TWRP:

http://xdaforums.com/general/device...410-5-inch-t3177753/post66208281#post66208281

You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:

fastboot flash recovery twrp-05042016.img

or

fastboot boot twrp-05042016.img

Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.
[Miscellaneous Android Development] josoft86:
Installation Xposed Rom Ottmi

Installation Xposed Rom Ottmi
[MENTION=7319300]ottmi[/MENTION]

Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work
[Miscellaneous Android Development] ottmi:
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?
[Miscellaneous Android Development] Bingo Bronson:
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.

edit: Updated to 20160606 build, framework still active, all good.

Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.
[Miscellaneous Android Development] marcachas:
Great, so many thanks, but, the link?
[Miscellaneous Android Development] Bingo Bronson:
You have to use the download tab on the top of the thread since this is a DevDB supported thread...

http://xdaforums.com/devdb/project/?id=15607#downloads

Example:

[IMG="notice me senpai"]http://i.imgur.com/yhj1rBm.png[/IMG]

Visit xda with your browser if you are currently on xda labs or some kind of forum app.
[Miscellaneous Android Development] marcachas:
Oh, thanks, you are the best, this rom is so table and smooth, your job is awesome, a hug.
[Miscellaneous Android Development] 21prods:
Thank you. I decided to buy the Elephone Trunk because I was interested in a economic phone that could 'easily' be upgraded with non stock ROM (preferably CM 13).

I have gone through the previous conversation and I must admit I'm impressed with your progress so far. Congratulations and a big thank you!

I will definitely flash your build as soon as I receive the phone.

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] kbezerianos:
Great job!

Great job and super useful guide [MENTION=7319300]ottmi[/MENTION].

Thank you!

I am currently running your previous release (cm-13.0-20160515-UNOFFICIAL-trunk) and have no issues to report at all!

In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?

Thank you for the excellent work.

Kind regards.

P.S. I have downloaded and installed GAPPS (Google Apps) from CM portal and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.
[Miscellaneous Android Development] Bingo Bronson:
Dirty flash is enough, no need to clean everything. Just install the new build, wipe the caches afterwards like it is suggested by TWRP recovery.

Some of your apps may have a survival script, others need to be reflashed (this is just the case for special tools, like Xposed, etc.)

Nano Gapps is a smart choice either way, because all the pre-installed Gapps will be outdated soon enough, so why bother to install a "huge" Gapps pack...

I use microG and have roughly 260 MB left on the system partition.
[Miscellaneous Android Development] josoft86:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you:o
[Miscellaneous Android Development] Bingo Bronson:
But, but... I'm also on 3.0.2-0 and the Xposed zips & ROMs, for example, are processed without error, Aroma installer is also supported...

Who compiled / ported your TWRP version? I used only [MENTION=4729636]hisname[/MENTION] releases and they never let me down. ?

I didn't even consider that possibility, since it has been mentioned numerous times in the old thread, ignorance is bliss (on my side), ahem... :o

I'm out of "thanks" to give, so I'll "upvote for awareness" later...
[Miscellaneous Android Development] ottmi:
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.
[Miscellaneous Android Development] 21prods:
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".

fastboot flash recovery twrp-05042016.img

Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:

Thank you, great job!
[Miscellaneous Android Development] 21prods:
One question, have any of you got to use a SD memory card as internal memory?

I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).

Thanks in advance

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] ottmi:
Bummer. You're right, I've fixed the instructions accordingly. Sorry for that!
[Miscellaneous Android Development] ottmi:
I'm using a 32GB microsdhc to store music and pictures, no issues at all. I've also used 64GB mirosdxc without problems. I've never tried moving apps though.. How does it show in Settings->Storage & USB?
[Miscellaneous Android Development] 21prods:
Yes, that's it. There you have the possibility of formatting the SD card to use it as (more) internal memory.

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] siljaer:
It's a bit conservative: I just modified your file to use stock rom default settings, and I added different settings for handset calls and audio recordings (basically, handset setting are [MENTION=7579766]Wenderer71[/MENTION]'s ones). With this file if you use CM13 sound recorder app you still experience low volume recordings (you cannot change the mic). Same applies for stock camera app. But if you use a camera app that allows you to change mic, you can have really loud video recordings (at last!).

The last change, the one that improves any audio recording, is not included.

Echo problem is solved for handset calls. I am experimenting with speakerphone calls, but I doubt it can be made with a single mic.

I made a mistake with github, the change in audio_platform_info.xml was not meant to be pulled (it does not hurt, though), even because it should work with a different audio_effects.conf from stock rom. I am sorry, I will make a test branch for the future.

Thank you for keeping on working! :)
[Miscellaneous Android Development] siljaer:
update on audio recordings

I've found something unexpected testing the effect of:

<path name="audio-record">
<ctl name="MultiMedia1 Mixer TERT_MI2S_TX" value="1" />
<ctl name="ADC1 Volume" value="15" />
<ctl name="DEC1 Volume" value="120" />
</path>

that is, "audio-record" settings override "camcorder-mic" and possibly "voice-rec-mic". So, in order to have recording inputs behaving differently, I have to remove a setting from "audio-record". I've choosen to remove analog gain, because different behaviour of microphones (namely, sensitivity to environmental sound) is better achieved by tweaking analog gain. So, with:

<path name="audio-record">
<ctl name="MultiMedia1 Mixer TERT_MI2S_TX" value="1" />
<ctl name="DEC1 Volume" value="120" />
</path>

I get default mic behaving quite good for voice recordings ("global" setting for ADC1 is 6), that is loud and without background noise.

with section:

<path name="camcorder-mic">
<path name="handset-mic" />
<ctl name="ADC1 Volume" value="15" />
<ctl name="DEC1 Volume" value="120" />
</path>

I get much more sensitivity to environmental sound. DEC1 Volume setting is overriden by "audio record", so it can be removed from here.

Most of the apps that record sound will use ADC1=(initial mixer setting) and DEC1 Volume=120. If you use an app that allows you to choose the input, you will find other sources, i.e. "camcorder" and "optimized for voice" (="voice-rec-mic"??) in Open Camera, and having different settings available is useful.

That led me to think about a different strategy to get rid of the echo. It is caused by mic being able to pick up earpiece sound, possibly conducted by phone frame. However, by lowering mic gain it should be possible to obtain a digital signal free from earpiece voice. Then, digital volume could be increased. That is quite different from the current approach that includes decreasing DEC1 digital volume too. I need some more testing on that.
[Miscellaneous Android Development] 21prods:
Wow! Without any good knowledge on my side, but what you have written here makes a lot of sense to me. You people are simply incredible!

You deserve to solve this puzzle!

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] ottmi:
Just in time before the weekend, here's a new ROM for download: http://xdaforums.com/devdb/project/dl/?id=19444

It incorporates [MENTION=7529884]siljaer[/MENTION]'s changes to mixer_paths.xml - let's see whether this solves the echo problems for others as well :)

Apart from that there are only minor changes: I added some more permission files for the lights and proximity sensors, set the screen density to 300dpi, and backported the LZ4 compression from the vanilla 3.12 kernel to use it in ZRAM (the stock rom did so as well). I've also applied a hack that restarts the media service after the phone has fully booted. I've seen this in the Oneplus Onyx source and it seems to improve the issues with the disappearing torch tile.
[Miscellaneous Android Development] Bizen-Ya:
Thank you for your work ottmi !

With the last ROM, i can hear almost anything, and on the other side neither...

I'll try to do some testing on my own ...
[Miscellaneous Android Development] marcachas:
Greetings and many thanks for continued development.

I installed the latest version of the ROM, but I found the following problems.

1. The echo of calls even heard.

2. Before the SD memory was not detected until after doing 3 Restarts about now with the patch flashlight, seems to give a double restart and if you happen to detect the SD memory, that extra restart stops recognize, so it is impossible to have in the SD.

I hope you can take some patch soon to continue using this wonderful rom.