Hey all,
some of us suffer from the robotic voice issue and the discussion in the dev forums gets out of control, so I decided to open an own thread for this topic.
I hope this will reduce the off-topic talk in the ROM threads (which is against xda rules by the way ;) ). Also this will maybe help the devs to find a solution eventually as they dont have to search through the 500pages in the dev forum to find any useful comments on the topic.
Further I would like to share how to live with the problem :D
For many users this issue is a dealbreaker for using a ROM. I personally adapted to it as those ROMs/builds without the issue are extremely poor when it comes to performance and especially battery life for me. The current version of the device tree massively improves those too aspects at cost of bringing the robotic voice issue, which is good so, as the issue only affects a few and it can be easily worked-around.
What you can do to work-around the issue:
I really hope that one of the devs will take a deeper look into that issue sooner or later. I can put up with it, but getting rid of this problem once and for all would of course be way nicer.
What we know about the issue (or think to know :silly: ):
First of all the bug appears only on marshmallow ROMs, not on lollipop ROMs.
As I said before it is connected to the latest changes in the device tree by hennymcc, which switched the phone libs. Considering that it doesnt appear on 2G, one can assume that it is the part that controls the mobile data / voLTE. That also means that basically every new ROM has the same bug because they all share hennymcc's device tree.
The ROMs that have the robotic voice issue are:
CM 13 (there are builds that dont have it, but I am speaking of the latest build)
Resurrection Remix
Tesla
ROMs that dont have the robotic voice issue:
Bliss ROM (latest build used the older version of device tree)
PAC-ROM 5
CM 12.1
I have this issue with every outgoing call others only calling specific numbers/providers and most of the users dont have the problem at all. So, it could be related to the provider one uses or more precisely the frequencies your provider uses.
And thats about all information I can provide to the topic. Feel free to add things that I forgot to mention or just dont know and when someone wants to have any specific logs just tell what you need and I am sure there will come a lot then ;) I will of course add a call log with and without robotic voice (2g/3g) but probably not today.
PS: Please excuse the noob language used here and there, I am obviously no dev :angel:
some of us suffer from the robotic voice issue and the discussion in the dev forums gets out of control, so I decided to open an own thread for this topic.
I hope this will reduce the off-topic talk in the ROM threads (which is against xda rules by the way ;) ). Also this will maybe help the devs to find a solution eventually as they dont have to search through the 500pages in the dev forum to find any useful comments on the topic.
Further I would like to share how to live with the problem :D
For many users this issue is a dealbreaker for using a ROM. I personally adapted to it as those ROMs/builds without the issue are extremely poor when it comes to performance and especially battery life for me. The current version of the device tree massively improves those too aspects at cost of bringing the robotic voice issue, which is good so, as the issue only affects a few and it can be easily worked-around.
What you can do to work-around the issue:
- turn network mode to 2G
Go to Settings => Cellular networks => Preferred network type => 2G
Of course this means that your mobile internet will be way slower. All background service will run without any problems. Only when you for example stream music or videos online or maybe want to use the browser (in fact, therefore it wouldnt even really be necessary) you would have to switch to 3G/4G.
I have the robotic voice issue on every outgoing call when on 3G/4G and never had the problem on 2G. So this is a very stable workaround :good:
Also I have found an app called "Toggle Network Type 5.0" PlayStore - xda
It requires root but using a custom ROM that shouldnt be a deal-breaker. With this app, you can create an widget that toggles between network modes that you can select. So for example to toggle between 2G and 3G/4G :cool:
That means it is only one tap on a widget from ready to take a call to highspeed mobile internet :fingers-crossed: - use dual-boot
I'mTheMr released a dualboot app for our device G800F xda-thread. I am using it quite a while now and never had any problems with it. The ROMs are installed to internal storage. Having a device with 12gb internal storage this is absolutely no problem. You can access files, photos etc. from all ROMs.
So you have one ROM (works with rooted stock ROM as well!!!) that you can rely on, say your work partition and when you want to use a custom ROM with all its fancy features and the robotic voice issue is atm no deal-breaker you just choose your secondary in the app and reboot =)
I really hope that one of the devs will take a deeper look into that issue sooner or later. I can put up with it, but getting rid of this problem once and for all would of course be way nicer.
What we know about the issue (or think to know :silly: ):
First of all the bug appears only on marshmallow ROMs, not on lollipop ROMs.
As I said before it is connected to the latest changes in the device tree by hennymcc, which switched the phone libs. Considering that it doesnt appear on 2G, one can assume that it is the part that controls the mobile data / voLTE. That also means that basically every new ROM has the same bug because they all share hennymcc's device tree.
The ROMs that have the robotic voice issue are:
CM 13 (there are builds that dont have it, but I am speaking of the latest build)
Resurrection Remix
Tesla
ROMs that dont have the robotic voice issue:
Bliss ROM (latest build used the older version of device tree)
PAC-ROM 5
CM 12.1
I have this issue with every outgoing call others only calling specific numbers/providers and most of the users dont have the problem at all. So, it could be related to the provider one uses or more precisely the frequencies your provider uses.
And thats about all information I can provide to the topic. Feel free to add things that I forgot to mention or just dont know and when someone wants to have any specific logs just tell what you need and I am sure there will come a lot then ;) I will of course add a call log with and without robotic voice (2g/3g) but probably not today.
PS: Please excuse the noob language used here and there, I am obviously no dev :angel:
from xda-developers http://ift.tt/25r7YCW
via IFTTT
No comments:
Post a Comment