Help needed with Xposed Bluetooth module in Malaysk ROM - MTCB Android Head Units Q&A

I have installed the Malaysk ROM on my RK3188 pumpkin autoradio. I can see that the Bluetooth module is installed under running apps, but I dont see any icon for it. This means that I cant open it and change the settings. For example I would like to change the settings so that it automatically answers the phone. I can also not open the GUI if I want to dial a number. Incomming calls works fine and the GUI pops up when I try to call my own number. How can I change the settings? How can I open the dialer? Thank you in advance.
Regards
Thomas V.

Related

[Q] CM10 - Change voicemail number

Hi all
If I try to change the voicemail number on CM10 (nightly from 22nd) - I get the message: "Couldn't change the voicemail number. Contact your operator if this problem persists".
This is via Dialler > Settings > Voicemail > Setup
Is there any way to change it in a config file somewhere, manually? I am running CM10 so I'm obviously rooted...
I see this questions asked other places but no answers yet! Any help appreciated.
Thanks
James
surrealjam said:
Hi all
If I try to change the voicemail number on CM10 (nightly from 22nd) - I get the message: "Couldn't change the voicemail number. Contact your operator if this problem persists".
This is via Dialler > Settings > Voicemail > Setup
Is there any way to change it in a config file somewhere, manually? I am running CM10 so I'm obviously rooted...
I see this questions asked other places but no answers yet! Any help appreciated.
Thanks
James
Click to expand...
Click to collapse
For anyone who may be wondering for an answer...
I managed to bodge it in by editing the below file using Root Browser Lite off the market:
/system/etc/voicemail-conf.xml
Thought it might help someone....
Got google voice working again after CM10 update...
surrealjam said:
For anyone who may be wondering for an answer...
I managed to bodge it in by editing the below file using Root Browser Lite off the market:
/system/etc/voicemail-conf.xml
Thought it might help someone....
Click to expand...
Click to collapse
Used Root Browser and couldn't find that "voicemail-conf" file in my CM10+gapps+4.2apps update on my T-mobile Samsung Galaxy II S (T989). From my research, it looks like T-mobile restricts their customers from setting/changing the voice mail forwarding number. I had to call Tmobile and tell them that I needed to change my voice mail number to my google voice number. They did something in the system on their end and I re-booted. Tried to set the number in the normal call settings, still wouldn't take. I then just entered a "MMI" code or something directly in the dialer as follows: *004*1xxxxxxxxxx# "xxxxxxxxxx" is my ten digit google voice number. This method worked! I don't know if other carriers restrict their voicemail in this way, but if you are on T-mobile it should work as I described.

[Q] Issues after upgrading to I9082LUBUBMK1

Hello.
After upgrading to the baseband I9082LUBUBMK1:
1) Favorites contacts tab is missing.
2) Stock browser without history and bookmarks.
This issues are a "feature" of the new version or it is a bug?
Greetings from Paraguay.
Claudio Bogado.
claudiobp said:
Hello.
After upgrading to the baseband I9082LUBUBMK1:
1) Favorites contacts tab is missing.
2) Stock browser without history and bookmarks.
This issues are a "feature" of the new version or it is a bug?
Greetings from Paraguay.
Claudio Bogado.
Click to expand...
Click to collapse
just downgrade back via odin. BUT why not you try Pyramid/GENNXT rom if you need dual sim, its more feature filled. If you dont use dual sim, use one of the kitkat rom available
Actually I want to know if there is another way besides downgrading because there are improvements like:
1) Longer battery life.
2) Better keyboard.
3) now I can lock high speed network, before y just could lock to 2G speed.
Maybe someone knows some command that can be written in the address bar or some hidden setting to turn favorites contacts on.
It also can be that there is another way to achieve the same goal.
I also noticed that merge contacts is also missing but you can merge contacts selecting from dropdown list while modifying the contact's name.
Try flashing ? :/
Solved
XG.Matrix said:
Try flashing ? :/
Click to expand...
Click to collapse
I realized later that the phone was set to simple desktop automatically in the upgrade, that was the reason the favorites tab was missing.
In the browser now you have to press the left or right borders to have access to the commands.
Thanks anyway.

Factory setting problem

Please i have problem in my device KGL . The problem is the bluetooth mic not work after i upgraded to latest malysk firmware . When i checked the default factory setting . I found that the default application for BT is BC6 this is the defult for me and bluetooth was working fine in this driver . After the firmware upgrade bluetooth mic not work . The only way the mic work is to change the BT application to BC6B and in this case the sound is very bad and low . I dont know is it MCU problem or what? My mcu version is KGL 2.83 i tried to downgrade to 2.80 but no change . So please how can resolve this problem
Malaysk has stated before not ever firmware is compatible with every unit what work before might not work if upgraded to the newest version. I am on the latest version and have 0 issues.
Sent from my SM-N910T using Tapatalk
I know . I just need to know how i solve this problem now . I changed the rom to the previous one and still the same problem
I suppose the question is.. did you upgrade the MCU at the same time as the Rom?
What MCU and Rom where you on before you upgraded to the new versions..?
If you have documented this..then try to go back to that same setup and see if it all works.. note if you do this I suggest full wipes..
The other thing you are saying here is that you don't have an option to choose the Bluetooth settings that you where using before..?
If this is correct you can only hope that reverting back to original setup will allow you to choose this setting again..
Then this all points too.. not every machine is going to behave as they should on upgrades..
The variables are.. MCU settings..which no one has cracked yet due to no source..
And the way it interacts with the Android base..
As a note; I haven't touched my MCU..and was able to access my bluetooth settings that I had before..I need to check the pic I posted as I have them in there..
Now i found the problem but dont know how to solve it . My Bluetooth Module:BC6 Stereo Module,A2DP . In the factory setting when i choose BC6 mic not work . When i choose BC6B mic work but with very bad voice . Befor this problem happend the defult setting for bluetooth is BC6 and mic was work perfect with it . So any help ?

Car factory Setting Code ? android onboard Toyota Yaris

Hi everyone. I'm new here !
First, sorry for my english ! I'm french and i try to explain my problem in english... If there is a french discussion, i didn't find it
I've installed an android system in my car (Toyota Yaris)
I'm searching for the Car factory setting code to open the setting for personal setting
I tried " 126 " but it's a four figures code.
I don't know which brand it is.. I found some numbers here but nothing happen, nothing is working :crying:
I took pictures if something can help you about the machine but i can't publish them yet but i've links.
Thanks for trying to help me.
TorvicGall said:
Hi everyone. I'm new here !
First, sorry for my english ! I'm french and i try to explain my problem in english... If there is a french discussion, i didn't find it
I've installed an android system in my car (Toyota Yaris)
I'm searching for the Car factory setting code to open the setting for personal setting
I tried " 126 " but it's a four figures code.
I don't know which brand it is.. I found some numbers here but nothing happen, nothing is working :crying:
I took pictures if something can help you about the machine but i can't publish them yet but i've links.
Thanks for trying to help me.
Click to expand...
Click to collapse
Try 7890
Developper mode asked password
My Honda Civic 2016 (Canadian version) asked me a password to activate the Developper mode. Any one here had the same issue, i have done a complete reset of the system to default and still the same things.
To be clear, after tapping 7 time on Build number, the popup appeared.
My Android Version is 4.2.2 Build: 1.F186.67 and Model number: MY16ADA
Pls help !!
zahurkho said:
My Honda Civic 2016 (Canadian version) asked me a password to activate the Developper mode. Any one here had the same issue, i have done a complete reset of the system to default and still the same things.
To be clear, after tapping 7 time on Build number, the popup appeared.
My Android Version is 4.2.2 Build: 1.F186.67 and Model number: MY16ADA
Pls help !!
Click to expand...
Click to collapse
Try 123456 or 7890
zahurkho said:
My Honda Civic 2016 (Canadian version) asked me a password to activate the Developper mode. Any one here had the same issue, i have done a complete reset of the system to default and still the same things.
To be clear, after tapping 7 time on Build number, the popup appeared.
My Android Version is 4.2.2 Build: 1.F186.67 and Model number: MY16ADA
Pls help !!
Click to expand...
Click to collapse
Got the same car. And same issue.
Funny enough the Developer Mode prompt for a passcord. Probably a typo I guess.
Anyway have you found a way to enable it?

Dasaita - Latest MCU and Updates for Dasita PX6 1280x720 MAX10

For Dasaita PX6
Updates on Dasaita website: https://www.dasaita.com/blogs/news/update-firmware
-----
Older versions:
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment MTCE_HA_V3.57.zip
v3.60: View attachment MTCE_HA_V3.60.zip
v3.62: View attachment MTCE_HA_V3.62.ZIP
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment dmcu-1280x720.zip - use it if you got a wrong resolution after flashing MCU image and you need to restore your unit to 1280x720 resolution
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
orik13 said:
For Dasaita PX6
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment 5111231
v3.60: View attachment 5111233
v3.62: View attachment 5111235
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment 5111237 - use it if your unit has 1280x720 resolution, otherwise you can get 1024x600 or lower instead (no worries in this case - just reprogram)
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
Click to expand...
Click to collapse
Before even considering this read in the other thread what happen to my unit. User name halloj,
orik13 said:
For Dasaita PX6
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment 5111231
v3.60: View attachment 5111233
v3.62: View attachment 5111235
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment 5111237 - use it if your unit has 1280x720 resolution, otherwise you can get 1024x600 or lower instead (no worries in this case - just reprogram)
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
Click to expand...
Click to collapse
Anyone reading this
*** Do not flash the DMCU.ext listed here together with the MCU ***
OP please edit this post, there is NO reason to flash dmcu.ext when flashing the same vendor MCU.
Suggest expanding on the comment "no worries just reprogram", with clear examples if making this statement.
marchnz said:
Anyone reading this
*** Do not flash the DMCU.ext listed here together with the MCU ***
OP please edit this post, there is NO reason to flash dmcu.ext when flashing the same vendor MCU.
Suggest expanding on the comment "no worries just reprogram", with clear examples if making this statement.
Click to expand...
Click to collapse
I edited it to make it more clear. Your comment is not absolutely correct: it is based on my own experience. Similar issues can be found by googling and even here at xda
Hi all I am a bit confused by how many different downloads please excuse me as a noob and first time flashing my PX6
My question is can I just jump from 3.5.8-1 to the latest 3.6.2 I believe and what files exactly do I need to load onto a flash drive.
Your help in advance is much appreciated. Cheers J
I am running a MTCE HA running 3.5.9
ToyotaJay said:
Hi all I am a bit confused by how many different downloads please excuse me as a noob and first time flashing my PX6
My question is can I just jump from 3.5.8-1 to the latest 3.6.2 I believe and what files exactly do I need to load onto a flash drive.
Your help in advance is much appreciated. Cheers J
I am running a MTCE HA running 3.5.9
Click to expand...
Click to collapse
Suggest NOT changing your MCU unless resolving a known issue. Same for Android. This is a head unit, constantly updating isn't necessary.
Update for mic issue
Hi Experts! If I want to update my Dasaita PX6 Max10 is there any preferred order which update to do first OTA or MCU? In case of OTA update at starting is it necessary to click on WIPE AND FORMAT FLASH option? Somebody is doing this, somebody is doing that... When is it suggested?
The reason why I planning to switch to latest update because during calls my mic is working strange, sometimes the others cannot hear me properly. They are complaining about low volume and faded voice. (If they are calling back they says it is better...) Have you experienced the same thing?
halloj said:
Before even considering this read in the other thread what happen to my unit. User name halloj,
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=83671635&postcount=3655
gomoriz said:
Hi Experts! If I want to update my Dasaita PX6 Max10 is there any preferred order which update to do first OTA or MCU? In case of OTA update at starting is it necessary to click on WIPE AND FORMAT FLASH option? Somebody is doing this, somebody is doing that... When is it suggested?
The reason why I planning to switch to latest update because during calls my mic is working strange, sometimes the others cannot hear me properly. They are complaining about low volume and faded voice. (If they are calling back they says it is better...) Have you experienced the same thing?
Click to expand...
Click to collapse
Are you sure it is not a h/w issue? Did you try other mic?
orik13 said:
Are you sure it is not a h/w issue? Did you try other mic?
Click to expand...
Click to collapse
I use the internal microphone, not yet tried an external one. I checked the mic with apps, basically it is working however its volume seems to be a little bit low, but it is not faded. I feel it is rather a noise suppression issue (coming from sw side), therefore I hope that an update could help.
orik13 said:
I edited it to make it more clear. Your comment is not absolutely correct: it is based on my own experience. Similar issues can be found by googling and even here at xda
Click to expand...
Click to collapse
I respectfully disagree based on years of experience: there's no need to flash the MCU configuration file DMCU with an MCU that matches the manufacturer of your head unit. I.e. HA to HA, JY to JY etc.
Your well meaning advice resulted in a configuration not appropriate (which messed up the screen) for another members screen type/resolution.
The 'similar issues' stated are probably your misunderstanding of what the DMCU file is and possibly where others have installed a different vendor MCU. E.g. GS on HLA
Hello, with dasaita px6 android 10 1024/600 firmware HA3, the update "HA3_rk3399_10.0_ota (20200915) 升级 包" and MCU "MTCE_HA_V3.62": all is ok , thank you
A few questions...
1) Anybody able to modify steering wheel controls? I open the app and it is blank.
2) Also, can you summon siri/google via the steering wheel when in carplay/android auto?
3) I have an OBD dongle but am unable to get the headunit to connect to it. I see it in the available devices but nothing happens after i select "yes" to connect.
I have the max10 600p resolution version for highlander. A canbus was included and I am able to change vol/toggle modes.
h0va4life said:
A few questions...
1) Anybody able to modify steering wheel controls? I open the app and it is blank.
2) Also, can you summon siri/google via the steering wheel when in carplay/android auto?
3) I have an OBD dongle but am unable to get the headunit to connect to it. I see it in the available devices but nothing happens after i select "yes" to connect.
I have the max10 600p resolution version for highlander. A canbus was included and I am able to change vol/toggle modes.
Click to expand...
Click to collapse
When you install a harness with a CAN adapter the steering wheel signals a routed for you to the CAN decoder box. It worked for me to reroute them to my own circuit. It should be equally fine to connect them to the KEY1 and KEY2 inputs, that is if your car has resistive buttons and only one or two. Then you can program them as desired.
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
woggles said:
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
Click to expand...
Click to collapse
I noticed that the first time I installed that update, then I went back to the prior version I had, one more time I gave it a try and I started to try to remove that annoying notification, but then I thought why waste time on that, also I notice that saving a screenshot was giving me an error, so once again I went back to the prior version I had installed.
I can’t decide whether to put this up or Malayk’s ROM. I don't really need pre-installed programs, I know which launcher, music player, etc.. I want to use, but there may be settings in it that I can't solve on this ROM.
woggles said:
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
Click to expand...
Click to collapse
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
bad for me
thienthanty said:
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
Click to expand...
Click to collapse
hello, with this firmware "HA3_rk3399_10.0_ota (20201016) 升级 包", I can no longer make a call with "google voice".
thienthanty said:
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
Click to expand...
Click to collapse
Thanks, the annoying pop up is gone but as another use mentioned using call x from Google Assistant doesn't work anymore!

Categories

Resources