Related
hilo,
Just created a new thread for this as its issues are pilling up the other one. i think that thread should be clean and should have only and only contain info about progress on the wm6 rom...
Mods if unnecessary please delete...
Tejas
I would not call it a bug but one of the disadvantages of the ROM is that, similar to these ones which come to Qtek and i-mate, it does not recognise the network settings out of the box but you have to fiddle with them manually. When I use Orange ROMs (and it does not matter if the ROM comes from the UK or Switzerland) everything works with flying colours, despite I do not use any Orange network. Just I have to install Opera Mobile (I hate pocket IE) and voila! Everything works!
Channels don't work.
in india AFAIK channels just provide the cell id i.e the area which i m in... not imp though... no use of channels
ok phil.
if u remove windows update, at least supply it as a cab in the extras folder.
channels don't work.
long pressed side button does not work! it used to start voice note record for the sda and i'd like that to work.
mms.
better camera software. btw htc camera makes the phone SLOW..... not a good one. need an alternate
enable profile switching to silent when long pressing '#' key
default folder for saving pictures on storage card is not my documents\my pictures any more but a lame dcim folder. that would be nice to be changed.
also, sometimes when answering a call, the keyboard stays locked, the call is still on, but the home screen is active and not the call screen.
joystick seems much better but sometimes it doesn't want to work as it should. maybe another driver; if not, this one is good
we need wpa2 for wifi enabled.
also add in the extras folder:
moblue
tcpmp with extra codecs
htc audio manager could be good
if u need the cabs for moblue and htc audio, i have them
there is an newer version of sim manager. v6.10. has a couple of new things (got it if u need it)
and maybe add a good version of opera. not the java one.
we also need a good midlet manager
also a good instant messaging program. maybe a multi client one like oz mobile im, or like im+
mmmhhh after read all this bugs, i better wait a while to update my phone, i find a good idea to write here all the problems with the actually ROM.
Good AD2P drivers
Hi,
Is it possible to have good ad2p drivers with the next rom?
Tomtom 6
I have never been able to run tomtom 6 before the update.
Is it possible now with update? and also which is best version to install?
Kindest regards
I have Push mail configured and GPRS seems to be buggy. once or twice a day GPRS seems to stop working. My Activesync fails with (Can not connect to network or waiting for the network to be available), and in that mode even IE can not connect to any site. I switch off and on the phone function only, GPRS becomes available again.
boneym said:
I have Push mail configured and GPRS seems to be buggy. once or twice a day GPRS seems to stop working. My Activesync fails with (Can not connect to network or waiting for the network to be available), and in that mode even IE can not connect to any site. I switch off and on the phone function only, GPRS becomes available again.
Click to expand...
Click to collapse
Actually I would split your post in two separate ones.
1. the instability of WM6 Alpha - obvious thing, and it should be fixed
2. but I also see something else. I see from many posts that one application which sets all the settings with one click is quite urgently needed. I know that something like that exists for Swiss networks http://www.mysmartphone.ch/Freeware/kommunikation/16920.aspx and for the Norwegian ones http://www.smartmobil.no/Article617.phtml but I think that everybody would agree that such an universal solution would be something good. Unfortunately, I do not know anything about programming but I can imagine this kind of program and a separate database. The database would be filled by volunteers - I can, for example, provide all the settings of Polish operators, someone else British, French, etc. It would be good esp. for people who travel a lot.
unlocksmith said:
I have never been able to run tomtom 6 before the update.
Is it possible now with update? and also which is best version to install?
Kindest regards
Click to expand...
Click to collapse
TomTom 6 is made for Pocket PCs. It requires a touch screen to work, so you won´t be able to control it. I have had it running on my 8310 but it´s just silly to even have it installed. Go for 5.2 if you can find it.
I have problems syncing my contacts if i have more than 305 contacts.
The ActiveSync (or WMDC) hangs saying "attention required". Though, i can make 305+ contacts on the WM6 and sync them back to Outlook! But backwards i get 305 contact limit. Vey, very strange!
With previous ROM everything was ok.
I tried syncing with different PCs, tried unistalling ActiveSync and WMDC - no use. Deleting pim.vol doesn't help too.
ActiveSync on WM6 gives me 0x8503001c error.
Thanks for your help. I got my old one to work. I really like the colours in tomtom 6 tho.
Also on my phone i have a problem(s) with tomtom 5, I cant type in the post code B8 followed by anything like B8 3NU. Also I can't use certain Points Of Interest such as hospitals or cash dispensers. These work fine on my Wizard but I wana be able to do it all with TORNADO!
The software of dual sim selector don't works with that new rom (adapter of 10ª generation).
Well, I don't know if it works; the soft does not appear by any side.
I proved several solutions, but no it has worked to me.
Somebody can help me?
Thanks.
tejasphatak please rename the topic to "WM6 Torando bugs/issues" , so we can generally post bugs/issues regarding all WM6 tornado roms
Bugs:
1. The locklevel change to 1 randomly..
2. Sometimes the phone freeze when unloking kepyad.
It happened two times.
Issues:
1. When playing audio the CPU load is ~ 25-30% (@180 Mhz). It is normal ? (can someone with WM5 test?)
If using EQ and other effects the CPU load increase.
A taskmanager with cpu load info can be found here (it's for PPC but works also ,somehow, on smartphones)
More CPU load = more power = less battery
2. The system lags while writing to storage card (big cards, > 1gb). This issue is present on WM5 Tornado roms too (except iphone rom wich seems to deal better with sd).
Need a beter SD driver .
Same when copying via ActiveSync (has anyone tried usbfn driver from HTC VOX?)
3. when TCPMP is playing audio it keeps the backlight alive
Using andot's PEE V6.
bsider said:
I have problems syncing my contacts if i have more than 305 contacts.
The ActiveSync (or WMDC) hangs saying "attention required". Though, i can make 305+ contacts on the WM6 and sync them back to Outlook! But backwards i get 305 contact limit. Vey, very strange!
With previous ROM everything was ok.
I tried syncing with different PCs, tried unistalling ActiveSync and WMDC - no use. Deleting pim.vol doesn't help too.
ActiveSync on WM6 gives me 0x8503001c error.
Click to expand...
Click to collapse
Hello,
I've got a similar problem to this. It used to work fine until last week. I can't remember changing anything in my Hard/software setup but now it just hangs and only some of the contacts sync.
I've searched in the forum but can't seem to find any other reference to this problem. If anyone knows a solution (or any discussion of it) please let me know. Basic device info below:
SPV m3100 (HTC TyTN) running WM6
Windows Vista Home Basic
Windows Mobile Device Center
Thanks.
It seems that with this new build of TomTom 7 smartphones are supported now !!!
The problem with earlier releases was that you couldn't scroll down to select the second, third etc line. This now works. Great news. but...
I installed it on a HTC Tornado (qtek 8310) and it works fine. The problem on the S710 is again the backlight going off after a while. Dit anyone try this new version already and do you have the same problem with the backlight?
I know there was a program called Kahuna TTn6 Focufix.cab to keep the focus on the program. maybe this works? I will try to find this program and see if it helps. Maybe we have to modify the key HKCU\Control Panel\Power\Display again?
I hope some of you can help me find a sollution, so we all can use the newest TomTom version on our Vox !
I found the TTn6 Focufix.cab, but this doesn't work.
I did find a workaround: I set the display time-out when on ac power to never. This works. So when I am in the car the battery is charged and the display stays on.
TomTom 7.915 on Fireburner custom ROM 1.0
I am using TomTom 7.915 since I install the custom ROM from fireburner.
This release works on S710 but with same limitation/problem, but you can select the different icon of the menu without any problem. The navigation can be vertical with the phone close, or horizontal if you have the keyboard open.
These are the Four main problem I have found, and the solution I have use to work around:
1. Backlight going off. When I am using it I plug the phone with the power supply, otherwise battery go away immediately after you arrive at destination or when you are close to it. I solve this problem in the "Settings"+"power Management", and select "never" in "Display time out on AC"
2. Backlight always on after use TomTom. I run an application free that you can download from http://www.tgmaker.com/mobile/
3. Input a destination. The two keyboard of the S710 works, but only with number when present. I means that with the number keyboard TomTom take only the numbers, and with the Qwerty will take the letter if they are alone and the numbers if on the key have both. Same problem was in Opera mini, and you can solve in the menu settings.
Sol. A
I solve this problem saving a contact with the address, and select the destination to contact.
Sol. B
You can browse all the city and the street, you must have a lot of time, or if you know the ZIP code the search became faster.
Sol. C
Fakecursor works but are more the disadvantage that the benefits. When you run it you can use only it, and all the shortcuts with the keyboard doesn't work. I prefer plan the destination and recall them after.
4. Selection: When in the display you have only two possibility there are no problem, but when they are more, the option in the middle are difficult to select. I have find the possibility to select using shift+same key, but I found it very uncomfortable.
Now a challenge to the expert!!
My colleagues use TomTom 7.915 on Experia X1, and you can select all the function using only the keyboard. I have seen also a Touch Pro working very fine with it. The two device have different layout (4 and 5 lines) and the software is working perfectly. I was thinking that most probably TomTom call some driver install on the device for the keyboard layout and allow the software to run properly. My device have a fb custom ROM, and I have a stupid idea which maybe work! If we save the driver of the S710 with the same name of the driver TomTom is looking for the layout keyboard, may be we can use both the keyboard.
I know is a strange idea, but I cannot test since I don't know which driver TomTom is looking for when start up.
Bye
are you sure of number 2? I know that tomtom mobile 5 makes the reg key value HKCU\Control panel\Power\Display if it doesn't exist and set the value to 0 after closing tomtom. I don't think tomtom 7 has the same behaviour. Can you try removing the Display value and see if tomtom 7 creates it again.
number3: I didn't have this experience. I do use another rom. Maybe it has to do with enabling the T9 setting of the keyboard? I can use the number keyboard to make letters and select the right city and street.
number 4: good point. I hope somebody knows this
did some more tests just to be sure:
1. problem is the display goes out after a while. workaround is to set the display timeout in the poweroptions to never when on ac power.
2. tomtom7 doesn't make the value Display after closing, so the ptoblem doesn't exist. (there may be other programs that cause this problem, but it is not related to tomtom7)
3. when using the number-keypad all works fine. when using the full-keyboard there is a problem with the keys also used for numbers (like E R T Y). you get numbers when pressing these keys... I like the idea of whanging the keyboard-layout/driver somehow...
4. I don't really understand what you mean. selecting what?
walram said:
I found the TTn6 Focufix.cab, but this doesn't work.
I did find a workaround: I set the display time-out when on ac power to never. This works. So when I am in the car the battery is charged and the display stays on.
Click to expand...
Click to collapse
TTn6 Focufix is to prevent Tomtom 6 to go back to today screen on smartphones after a while
walram said:
did some more tests just to be sure:
1. problem is the display goes out after a while. workaround is to set the display timeout in the poweroptions to never when on ac power.
2. tomtom7 doesn't make the value Display after closing, so the ptoblem doesn't exist. (there may be other programs that cause this problem, but it is not related to tomtom7)
3. when using the number-keypad all works fine. when using the full-keyboard there is a problem with the keys also used for numbers (like E R T Y). you get numbers when pressing these keys... I like the idea of whanging the keyboard-layout/driver somehow...
4. I don't really understand what you mean. selecting what?
Click to expand...
Click to collapse
Dear walram
I am sorry but I discover that I was running the TTN7.910.9185_vga_black for the Diamond.
I download the new version and I confirm that is working on S710.
1. Ok I have done the same
2. You are right for this point, no need tools for the backlight.
3. Number-keypad all works fine in this version, problem with the qwerty keyboard is still present.
4. In version 9196 the graphic is totally different, in not just a matter of resolution and I believe was developed for specific device. If you press center key pad 6+5 you can see the version of Tomtom , and you have 3 possibility
- copyrigth
- account
- done
I am not able to select Account.
During the installation I was not able to select the correct com port, since look like the cursor was not enable to move, or this version was designed for COM9. I copy the *.exe and *.chk file on the old installation and is fine.
I believe that this version take out from the lolite is the most suitable for the s710. Then finally for who love TomTom, at least they should try it, since interface is almost the same of 5.2 for SP and the overall function looks ok.
If I found bugs or problem I will post later in this section.
Bye
i see what you mean with point 4. I don;t know a sollution for that, but i think you don't really need it for daily use. i could select the right com-port (com 6). installed it on 5 devices already, no problem.
the only bug i found so far is when starting the demo for a route the buttons are switched. so the "ok" and "cancel" are switched. just that you know...
it would be nice if somebody can fix the full-keyboard layout problem... it seems a problem with the s710?
it would also be nice if somebody can write a simple program that creates the registry key to keep the display on when the program is running, and delete the key when tomtom is closed. anybody?
i could select the right com-port (com 6). installed it on 5 devices already, no problem.
Click to expand...
Click to collapse
I'm NOT a big fan of TOM TOM but I've tried for the first time to figure out this problem and so far I totally agree with Dom_LC
COM selection is locked IMHO. I've tried to edit navigator.cfg to use COM7.... DONE...but it was useless
then I tried to add COM9 to my Bluetooth outgoing ports...it was selectable but obviously the system was unable to create the port.
I tried also to mix data file with the exe to see wath's what ...useless.
Tried fakecursor and eCursor...they worked everywhere but in the COM selction MEnu.
well, that's kind a strange isn't it? can you use the up and down-button when selecting a city and when selecting a road? are you using version 7.915 and not 7.910?
Sure! and I'l tell you something more interesting also when composing the destination I can't scroll from the vorious suggestions that are indexed along when you are typing (the only that is always selected is the first in the list as for the COM ports)...so the only way is to write the exact name
interesting. so maybe there are more versions of the 7.915 around? something to do with the rom?
anyway i can scroll from the vorious suggestions everywhere. Maybe i should send you my version and see what it does on your vox.
I had the following files:
ttn7.915.9196.qvga_black.cab
ttn7.915.9196.qvga_blue.cab
ttn7.915.9196.vga_black.cab
i installed the middle one.
a did find a bug, so it seems. How do you select a differect country when typing a city? On a PDA you can select the country on the right side of the screen. but how does it work on a smartphone? eg. I am from the netherlands and the only city's i can select are from the netherlands. In earlier versions of tomtom all city's of europe were in the same list. can anyone confirm this bug?
Yep Walram, this bug is on my StarTrek too, TT started in Belgium for me and i had no clue how to change the country to Netherlands, so i navigated to one of my dutch contacts and that did the trick, so, maybe a bit odd, but you could add a fake contact in the country of your choice to end up over there.
Nevertheless....this is an inconvenient bug since it doesn't allow you to travel or plan through whole of Europe
i wonder if the selection of country is in the map or in the application. eg. if we install an old map (version 7 or 6) do you get 1 list with all city's of europe?
so tomtom has some work to do again to fix this bug.
if you remove the mapsettings.cfg in the map-directory before starting tomtom you get the question once to wich country you want to navigate
so, a little, workaround. you also loose your home adres and favoutites i guess...
but it works... just that you know
well, that's kind a strange isn't it? can you use the up and down-button when selecting a city and when selecting a road? are you using version 7.915 and not 7.910?
Click to expand...
Click to collapse
I tried blue and black version. I think it was black wich did not let me select something with the up and down keys. So try both versions.
By the way installation failed every time on my Vox (Rose v.0.4)
So I extracted the files with win ce extractor, putted them on the root of the SD card and all went well.
Ierlanfdan said:
I tried blue and black version. I think it was black wich did not let me select something with the up and down keys. So try both versions.
Click to expand...
Click to collapse
I Can Confirm that! Smartphone users can take advantages ONLY from the blue one! And this ends my adventure with tom tom.
help
i have a vox with original ROM (mobile 6) and i can't install the tomtom... it start the cab and suddenly stops and go back to home screen...
does anyone can help me... I've tried the qvga version black and the ttn7.915.9196.qvga_blue_cuckoo.cab. both do the same thing.... they start and suddendly stop...
the install bar doesn´t move, and the waiting color circle disappears and go back to home screen...
can you put here the link to the version you have for me to try??
thank you and sorry for my bad english....
It's for PPC, you can't instaqll on a Smartphone, so you have to use this method
http://forum.xda-developers.com/showpost.php?p=3224919&postcount=776
TheBo said:
It's for PPC, you can't instaqll on a Smartphone, so you have to use this method
http://forum.xda-developers.com/showpost.php?p=3224919&postcount=776
Click to expand...
Click to collapse
i try it but i can't copy the shortcut.... said i can't do it... any alternative method to copy it...
thank you...
I was wondering if there is a way to make a Windows Mobile (6.5, if that matters) ignore a specific cell/tower.
The problem I'm trying to solve is that in the area I'm living in I am having issues only when connected to a specific tower (I know, this is a provider issue - they are probably having problems with that tower, but...) - so I'm trying to make my phone (HTC Touch HD/Blackstone) ignore that tower completely.
The usual suspects:
1. The radio software itself
2. The RIL (Radio Interface Layer) - is there any validation callback from the RIL when the cell configuration changes ?
TIA for any info on this matter...
As far I know you can't do anything about it. This stuff is buried deep in the radio ROM itself.
There is nothing in the standard RIL library that deals with it. The call backs are for requests for information via RIL_xxxxxxx calls. There is a possibility that it has been implemented through the driver catch all function RIL_DeviceSpecific(), but as this is defined by the OEM as the device and driver is built, you have to know the parameters to pass, and what gets delivered back to the callback routine.
Even if this stuff is there, it tends to be undocumented, and may change from OEM to another, and maybe even from one phone model to the next.
stephj said:
As far I know you can't do anything about it. This stuff is buried deep in the radio ROM itself.
Click to expand...
Click to collapse
That's what I feared ..
Thanks for the info.
Hi,
This is Stefan from Germany.
I like to raise a question because I´m not getting further with boosting the volume of my
GT-i9105P.
It´s rooted and I have manually updated it to 4.2.2 some time ago.
(I9105PXXUBMI1, Kernel:3.0.31-1571687, Build: JDQ39.9105PXXUBMI1)
I like to have the headphone volume output to be boosted.
I tried to use two methodes – both not succeeding so far.
1. I changed the default gain.config via ES explorer. But changing the relevant parameters did
not change anything in the volume. I was not 100% sure about doing everything right regarding read/write access
and having missed some other files to be changed. Seems that there´s a copy/paste- file available also from XDA-platform
This seems to contain an additional file – volume.db which I have not touched yet on my phone. Downloaded this file and it contains an exe
which I´m afraid of because of virus. But to what I have read it should be enough and working by changing the defaultgain config. But
I have not specifically read about the i9105p/ S2Plus, and then its again special because I have changed the sw to 4.2.2 as my provider did only allow 4.1.2
on the phone…and my knowledge is limited…
Due to this I was looking for another 2nd solution…
2. I read that it should also be possible to do this increase in volume via going into service mode…Service mode should be accessible via
*#197328640# (with different code versions of *# to be left out or added). But If I type this nothing is happening and I was again
Wondering if this is because of having the phone modded. I´m aware of that this way of setting will be gone after a reboot- but that´s better than nothing…
I have already soldered a small PCB with an OP amp - this works almost fine (disturbance in Audio while phone is busy with looking/working on the RF signal – no prob if plane-modus is ON)
…But I still believe it must be possible doing it via the sw mod…..
What else could I do wrong in changing the defaultgain.config?
Are there any special codes available for accessing service mode for this phone?
Appreciating some inputs for my old S2 Plus…
BR
Stefan
My unit allowed me to pair multiple phones (my wife and daughter also drive) but the Bluetooth system would only reconnect to the last phone used.
So if I drove the car last, and then my wife drives, it won't connect to her phone without manually selecting it from the list of devices. It will be stuck trying to find my phone which isn't in the car.
I complained to the manufacturer about this silly bug (Atoto) and they issued an update that made it search for other phones. It seems to work pretty well now, but I'm wondering - is this normal behavior for FYT units? If so, what did Atoto do to fix it? I got a Bluetooth update file, it only flashed the BT system and not the rest of Android. I'm not sure what it did, but wondering if I purchase a different FYT unit, will I run into this yet again?
dishe2 said:
My unit allowed me to pair multiple phones (my wife and daughter also drive) but the Bluetooth system would only reconnect to the last phone used.
So if I drove the car last, and then my wife drives, it won't connect to her phone without manually selecting it from the list of devices. It will be stuck trying to find my phone which isn't in the car.
I complained to the manufacturer about this silly bug (Atoto) and they issued an update that made it search for other phones. It seems to work pretty well now, but I'm wondering - is this normal behavior for FYT units? If so, what did Atoto do to fix it? I got a Bluetooth update file, it only flashed the BT system and not the rest of Android. I'm not sure what it did, but wondering if I purchase a different FYT unit, will I run into this yet again?
Click to expand...
Click to collapse
can you confirm which update you got?
is there a specific patch name i could quote when i talk to them?
i just updaed to the 2023/02/02 release and still have this issue
It's strange they did not include this bug fix in the latest firmware update
thanks for any info you can provide
How do you check for updates?
The Bluetooth 1 system is separate from the rest of the Android OS.
Bt2 is the standard Android stack that you'd normally find on a phone or tablet, But BT1, in order to receive an incoming signal from your phone, is external hardware that exists outside of Android and seems to interface via an app that they call BT1. This does not get updated the same way as the OS does.
In other words, the firmware updates are usually only targeting the Android partition and does not update the MCU, Bluetooth, or other external components. You need to ask them for a Bluetooth update, It is performed by going into BT1 and then clicking on update Bluetooth firmware from within that screen with the file on a storage card or USB. It does not format the rest of the system, it really just update BT1 alone and can be done while the device is on. However I think that they recommend you reboot after performing the update since it is pretty heavily tied into how the rest of the radio operates.
The only thing that I don't like about the way Atoto handles customer support is their updates. They say they are going to be getting better about this in the future hopefully, but right now you need to specifically ask them for updates and there is no way to check for them.
dishe2 said:
The Bluetooth 1 system is separate from the rest of the Android OS.
Bt2 is the standard Android stack that you'd normally find on a phone or tablet, But BT1, in order to receive an incoming signal from your phone, is external hardware that exists outside of Android and seems to interface via an app that they call BT1. This does not get updated the same way as the OS does.
In other words, the firmware updates are usually only targeting the Android partition and does not update the MCU, Bluetooth, or other external components. You need to ask them for a Bluetooth update, It is performed by going into BT1 and then clicking on update Bluetooth firmware from within that screen with the file on a storage card or USB. It does not format the rest of the system, it really just update BT1 alone and can be done while the device is on. However I think that they recommend you reboot after performing the update since it is pretty heavily tied into how the rest of the radio operates.
The only thing that I don't like about the way Atoto handles customer support is their updates. They say they are going to be getting better about this in the future hopefully, but right now you need to specifically ask them for updates and there is no way to check for them.
Click to expand...
Click to collapse
i have reached out to Atoto. in order to asist in getting the correct file from them, can you please quote the filename they gave you, as a the moment they dont seem to know what i am talking about. this may help them find what it is i need.
thanks in advance
@dishe2
did it take long for you to get a response form them and the file in question?
they keep responding at the speed of only 1 email per day
between 5-6 am
constantly asking more info from me about my order
instead of telling me everything they need from me
its extreemly frustrating
have you been able to find the name of the file they shared with you?
so i can let them know exactly what I am looking for?
Maybe if you share the bluetooth update files people can review what this is about as I have not heard about BT update only.
roti86 said:
Maybe if you share the bluetooth update files people can review what this is about as I have not heard about BT update only.
Click to expand...
Click to collapse
yeah, thats all i wanted, was the file/files
at least their names
anyways, support has gotten back to me
I will provide the info I have as well as what hey expect from you in case any of you need the same fix
I figure the least I can do is share the info I have
they did not give me a file to be used in the BT files menu
wha they gave me was a config.txt and lsec6316update
lsec6316update appears to be the same file that is found in a normal update and triggers an actual update process
config.txt seems to simply contain system values and their configs, some of them not even available in the hidden menu
_____the config.txt appears to be specific to your device model
this did seem to trigger a "normal" , "full" update
but as soon as it hit the fastboot/adb/update screen
it simply seemed to apply the config file and then ask to unplug the drive
it then proceedd to boot
after booting the unit will now still search for last connected phone
but if not found within ~10-15 seconds
it tries the next one in the list and so on
I have reached back to support to thank them and ask about future updates
I still sont know if this "change" will be included in the next firmare update or not
or
if at that time a different "fix" may be needd
or
if you simply need to include the config file with the nex upate, as that seems to just be part of the structure
I will follow up when i ge more answers from Atoto
now for details needed when reaching out to them
so you dont have to struggle like I did 1 email at a time with no insight
1- screenhot of the "about device" in sysem showing the MCU version
2- further deails of the MCU by tapping 4 times and scrolling to the bottom of the black screen with all the details
3- date and vendor/site your unit was ordered from
4- order number
5- exact full model number of your unit
6- screenshot showing order and unit exact model
Bluetooth reconnects OK for me, but only on days ending with y
Uis7862 mcu type 116 fyt. Rock on.
pchtc said:
they did not give me a file to be used in the BT files menu
wha they gave me was a config.txt and lsec6316update
lsec6316update appears to be the same file that is found in a normal update and triggers an actual update process
config.txt seems to simply contain system values and their configs, some of them not even available in the hidden menu
_____the config.txt appears to be specific to your device model
Click to expand...
Click to collapse
Would you care to share the contents of the config.txt file?
That appears to be something I haven't seen before.
j0hn83 said:
Would you care to share the contents of the config.txt file?
That appears to be something I haven't seen before.
Click to expand...
Click to collapse
here are the contents of theconfiguration file
nothing really sands out in terms of a parameter that would forcefully scan other paired devices, but its working now
pleas keep in mind that my unit is an A6 PF (performance)
#test
ro.fyt.launcher = com.android.launcher8
sys.fyt.bluetooth_type=1
ro.sys.touchGesture=1
sys.fyt.systemobd=true
persist.lsec.enable_a2dp=true
ro.lsec.btname=Bluetooth 2
ro.fyt.subwoof=5
ro.fyt.message=0
sys.fyt.ec_version=6
persist.sys.ahd = 1
ro.build.go_lasttop=true
ro.fyt.splitscreen=0
sys.fyt.bluetooth_show_voice=true
persist.fyt.alwaysshowsim=false
persist.fyt.showgesture=false
persist.btpair.ssp=1
ro.fyt.amsens=22
ro.fyt.def.sb.aux=2
ro.fyt.def.sb.radio=9
ro.fyt.def.sb.player=5
persist.bta2dpvol.gain=7
persist.fyt.buildnumber=AICE UI 11.0
persist.fyt.productseries=Device Name:ATOTO A6 Performance
ro.fixed.wifi=1
ro.fyt.uiid=2
persist.fyt.enablebtvoice=true
ro.fyt.backcar_radar_enable=0
# persist.syu.backui3rd = true
persist.btmic.gain=4
persist.btautoconnect.count=3
persist.syu.single360=false
bt#ATOTO#0000
# true/false ÊÇ·ñµÚÈý·½µ¹³µÓ¦Óã¬Ä¬ÈϹØ(false)
# sys.syu.reserving_service_pkg = "com.envo.mono.android"
#µÚÈý·½µ¹³µÓ¦ÓðüÃû ±±¾©Ë«÷Ùöè°üÃû£º"com.sjs.vrbackcarapp"
# sys.syu.reserving_service_action = "com.envo.mono.android.service.MonoService"
#µÚÈý·½µ¹³µÓ¦ÓÃaction ±±¾©Ë«÷Ùöèaction£º"com.sjs.vrbackcarapp.AutoStartService"
Thanks for sharing. I don't understand coding but it seems its specific for ATOTO A6 Performance. I suppose its not a copy paste for others units. It has to be adapted. I wonder why other manufactures don't apply a patch like this. Could it be hardware related?
Battoussai said:
Thanks for sharing. I don't understand coding but it seems its specific for ATOTO A6 Performance. I suppose its not a copy paste for others units. It has to be adapted. I wonder why other manufactures don't apply a patch like this. Could it be hardware related?
Click to expand...
Click to collapse
I think it is the property "persist.btautoconnect.count=3".
If you can't find the first, go to the 2nd, and optionally go to the 3rd
surfer63 said:
I think it is the property "persist.btautoconnect.count=3".
If you can't find the first, go to the 2nd, and optionally go to the 3rd
Click to expand...
Click to collapse
Hello Surfer63.
Sorry for this and i'm trying not to be a PITA but your code skills are impressive so my question (and feel free to don't reply) is:
My config.txt only contains this:
bt#VW-PHONE#0000
ro.fyt.launcher=com.android.launcher6
sys.fyt.bluetooth_type=6
sys.lsec.carplay.OTGHdPort=3
sys.syu.dvd_external=1
persist.fyt.selectcolor=3
# ÅäÖÃÀ¶ÑÀÀàÐÍ
# 0£ºÄÚÖÃÀ¶ÑÀ£»
# 1£ºRDA£»
# 2£ºIVT£»
# 3£ºWQRDA£»
# 4: WQBC5
#
sys.syu.dvd_external (9853Íâ¹ÒµúºÏ) 0,1
Should I edit and add the line you refered to "persist.btautoconnect.count=3" after the "persist.fyt.selectcolor=3"? Or it is not that simple?
Thanks in advance.
Battoussai said:
Should I edit and add the line you refered to "persist.btautoconnect.count=3" after the "persist.fyt.selectcolor=3"? Or it is not that simple?
Click to expand...
Click to collapse
First of all: I am not sure that this is the correct property. This one is also new to me, but it is not one of the other properties. So it is an educated guess that this is the correct one.
It doesn't matter where you put the line. There is no specific order. So you can put the line wherever you want in the config.txt.
Hey, OP here. Just wanted to clarify a few things:
I originally asked the question because it came to my attention that the Atoto units handle Bluetooth a little bit differently than other FYT devices.
I was curious to see how others handle it and if they have the same reconnect issues that the Atoto ones do. I'm fairly certain that very little (if anything) would translate over to other brands, however I'm not fully aware of how other brands do it (I've owned 4 Atoto units so far and can't vouch for any others aside from what I've read here). And even stranger, the "fix" differs between Atoto's own devices (the A6 PF is a 8581 devices, and the S8 is a 7862- I own both units and both have BT updates to change how this works after I explained the problem to them, however the updates are very different).
In Atoto's platform, there are two bluetooth UIs:
1) BT2, which is the standard Android Bluetooth stack. It can be used like any other BT connection in an Android device, good for things like a keyboard or other input devices, OBDii dongles, file transfers, internet tethering, etc.
2) BT1, which is a customized Bluetooth UI to act as a receiver (all the headunit-related functions such as handsfree calls and streaming audio, which aren't part of the AOSP Bluetooth stack). They call this custom one BT1, while the standard Android Bluetooth system gets demoted to BT2, probably because they assume this is the most often used one for anyone expecting headunit-style functionality.
I'm not familiar with other FYT units, but it is my understanding that they have only one unified Bluetooth system, and it is likely a customized one only which is why I see people complaining about only being able to use "official" branded OBD readers instead of allowing any standard BT connection like Atoto (@surfer63, is that about right?).
I'm not 100% sure how it works, but it appears that BT1 might actually rely on separate hardware that exists externally from the rest of the Android system, and only interfaces with it via an app (similar to the way the FM tuner works). Essentially it is a Bluetooth receiver that goes into the MCU mixer and controlled inside the app called BT1. The proof to me that this is the case is that:
1) You can "see itself" when searching for bluetooth devices in BT2. I haven't tried this because it feels like a paradox that would unravel the universe at first, but apparently BT2 can see BT1 as an available Bluetooth speaker, and connect to it for audio.
2) After a factory reset, BT1 retains its paired devices information (because it exists outside of Android).
3) BT1 UI has its own "reset" and sometimes even "update" function (S8 Ultra, more on that in a minute), which implies it is operating on a different set of rules than the rest of the system.
When they initially made the update for my S8 Ultra, I was given a file to "flash the firmware of the bluetooth module". It is NOT a system update, but an update that must be initiated only inside of BT1. It does not effect the rest of the system, it does not even reboot the system. You click update, wait for it to finish, then click reset Bluetooth for good measure.
On the A6 pf (5851 device), I was given an actual firmware update to test when they "fixed" it. And not just a new lsec6316update and config file, but a full blown update. It could be that the rest of the update wasn't necessary and just a line in the config was changed, but I'd doubt that since they said the unit currently did not work the way I asked, and their engineers had to "work on a fix".
Either way, the bottom line here is that the Atoto units work different from each other (S8 vs A6 pf) and both of those work differently from every other FYT device I think, so none of this is cross-device useful IMO. I believe this is why they recommended I tell people to contact customer support rather than share the fix online for others, it appears to be very device specific. And for the record, it works much better on the S8 than the A6. The A6 gets stuck if it sees the previous device when it boots up, whereas the S8 can tell when it gets disconnected to start searching for other previous devices. The systems don't work the same way.
dishe2 said:
I'm not familiar with other FYT units, but it is my understanding that they have only one unified Bluetooth system, and it is likely a customized one only which is why I see people complaining about only being able to use "official" branded OBD readers instead of allowing any standard BT connection like Atoto (@surfer63, is that about right?).
Click to expand...
Click to collapse
The FYTs do indeed have one BT app and a "crippled" bluetooth stack. As I do not have an Atoto I can't say anything about the other parts of your theory/explanation, other then that it sounds quite logical.
dishe2 said:
.'m not familiar with other FYT units, but it is my understanding that they have only one unified Bluetooth system, and it is likely a customized one only which is why I see people complaining about only being able to use "official" branded OBD readers instead of allowing any standard BT connection like Atoto
Click to expand...
Click to collapse
Other FYT units operate the exact same.
They have 2 Bluetooth systems installed that behave the same way as your Atoto.
Either way, the bottom line here is that the Atoto units work different from each other (S8 vs A6 pf) and both of those work differently from every other FYT device I think, so none of this is cross-device useful IMO
Click to expand...
Click to collapse
The config.txt commands to change the behaviour of the Bluetooth pairing are FYT config lines and shouldn't be specific to Atoto.
I'll have a play with my unit later and try see how they change the behaviour but I suspect they will have similar outcomes.
j0hn83 said:
Other FYT units operate the exact same.
They have 2 Bluetooth systems installed that behave the same way as your Atoto.
Click to expand...
Click to collapse
@dishe2 mentions "In Atoto's platform, there are two bluetooth UIs:"
On my Mekede 500s I only have one 190000010_com.syu.bt.apk, and it doesn't have an alternative UI for "BT1" and "BT2". Neither is there an second BT apk, nor can I access it from the Settings.
This is already a 7 year old issue that prevents us to connect anything else than the "allowed" BT devices.
Can you please explain how I get to the other other UI with the standard BT functionality?
On my Mekede M500s you can access "Bluetooth 2" by using Marios shortcut app or using his FYT management centre app.
It's a completely separate Bluetooth chip to the BLINK Bluetooth app that handles calls (190000010_com.syu.bt.apk).
The 2 Bluetooth devices have different mac addresses.