Bluetooth settings fault Eonon G5153F + Malaysk ROM

[mindriot]

Im running the Malaysk ROM for RK3188 on my Eonon GA5153F

Since flashing the Malaysk ROM my bluetooth settings keep reverting to default, carkit device name etc.

Even if I manage to change them and even hold the settings for a coupe of boots on rare occasions they always revert to carkit and the default pin.

This problem has repeated over 2 versions of the ROM and posting in the Malaysk RK3188 thread brought nothing useful in the way of info.

Anyone have any ideas or suggestions how to sort this out, its very annoying and I desperately need bluetooth handsfree back for work purposes.

 

[robbo990]

Dont know if its relevant - I also have the GA5153F and although everything was fine with Malaysks 4.4. ROM - when i updated to his 5.1 version - bluetooth did not work until I changed the bluetooth adapter in Factory Settings to the non "b" version (same model number) since then it works great.

 

[mindriot]

Yep, youll get nothing with the wrong adapter set.

Unfortunately this is a different fault.

 

[mindriot]

Anybody?

I know others have suffered this problem, doesnt anyone have any other suggestions?

 

[m00n61]

Anybody?

I know others have suffered this problem, doesnt anyone have any other suggestions?

Get a Parrot BT. I am using a MKI9200. It is simple to install and call quality is 100x better.

 

[mindriot]

Get a Parrot BT. I am using a MKI9200. It is simple to install and call quality is 100x better.

Im sure it is, but it doesnt help solve the real fault with the kit Ive already purchased, fitted, and seriously need to function as I regularly need to take calls when driving, Im a courier.

Frankly I didnt have any call quality issues when it was working, its the total lack of function thats a bit of an issue!

Is this a hardware fault? Is it a Rom fault? IS it a media board fault? IS it as simple as a file somewhere being over written or with bad permissions?

 

[zine1959]

Non b worked for me but now I have no wifi

Sent from my SM-N915T using XDA-Developers mobile app

 

[m00n61]

Im sure it is, but it doesnt help solve the real fault with the kit Ive already purchased, fitted, and seriously need to function as I regularly need to take calls when driving, Im a courier.

Frankly I didnt have any call quality issues when it was working, its the total lack of function thats a bit of an issue!

Is this a hardware fault? Is it a Rom fault? IS it a media board fault? IS it as simple as a file somewhere being over written or with bad permissions?

It is essentially a manufacturer (software) issue. Malaysk has mentioned somewhere that Chinese developers messed up the BT stack. You must understand that these units use a plethora of BT boards from various suppliers AND in various HW revisions. Nobody will work on a universal BT service that accommodates all these boards. Your best bet, if you want to use the on-board BT, is to find a ROM that works, through trial and error, and stay with that one.

 

[mindriot]

It is essentially a manufacturer (software) issue. Malaysk has mentioned somewhere that Chinese developers messed up the BT stack. You must understand that these units use a plethora of BT boards from various suppliers AND in various HW revisions. Nobody will work on a universal BT service that accommodates all these boards. Your best bet, if you want to use the on-board BT, is to find a ROM that works, through trial and error, and stay with that one.

Thanks I am aware of the hardware diversity. It is frustrating that these companies have a weak attitude to stability. However the original rom had functional Bluetooth, and the Malaysk rom is supposed to be based upon it, thats what is also frustrating.

I tried posting in the Malaysk thread but it was largely ignored, scoffed at and lost in all the noise.

 

[mindriot]

Anyone else?