yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] PoppaRoxie1986:
Short version: The options I set are Fullscreen: "Prevent" and check the No Fullscreen IME checkbox.

---

Here's a step by step:

First make sure the App Settings Xposed module is enabled in the Xposed Installer.

To get there, go to the Xposed Installer App.

Click on the hamburger menu in the upper left hand corner and go to Modules.

Make sure there is a check in the App Settings Xposed module.

Now go to the App Settings application found in your launcher app drawer

You will see a listing of all the applications installed on the unit

Scroll down and touch the Bluetooth application.

In the upper right hand corner there is a toggle switch, if it isn't clicked to the right, touch on it. This will bring up a listing of per application settings.

Touch on the Fullscreen option and select "Prevent"

Touch on the No Fullscreen IME option (make it checked)

Touch the Save button in the upper right corner

Reboot recommended

It seemed that the changes in this particular case do not take effect until after you reboot. But even if it isn't necessary, a reboot certainly could not hurt anything.

You should be able to get back to your home screen when you are in a phone call. In addition, now you should be able to launch other apps (e.g. maps etc) and do things on your radio while you are on the phone without the Bluetooth app getting in the way.

---------- Post added at 01:54 PM ---------- Previous post was at 01:19 PM ----------

I like the idea of your custom Xposed module to deal with this issue, gtx. I also found that I can revoke the Microphone (RECORD_AUDIO) permission on Google app while a call is in progress to get rid of the noise and improve the sound quality on the other end of the phone call. Perhaps this is why the GVC app kills the Google process upon invoking the bluetooth app. I've had cases where the Google app got relaunched and the audio quality on the receiving end of my phone call was really bad (according to the person I was talking to).

I wonder if maybe there is a way to programmatically know when a call is in progress and revoke that permission to the Google app while the call is in progress and grant it back when the call activity is completed? Truth is the bluetooth app should do it but it's not worth holding breath for joying to make that kind of change to their bluetooth app.
[FYT Android Head Units] gtxaspec:
Yes there is. I'll try to figure it out tonight.
[FYT Android Head Units] edit:
I'm on December ROM with xposed working fine and App Settings ver 1.11 and unfortunately your solution does not for work for me. Thank you !
[FYT Android Head Units] PoppaRoxie1986:
First thing, apologies for earlier (enough said about that) :). I am using gtx v6 custom ROM and it seems to work for me. I've passed a few ideas along to gtx and perhaps his Xposed module that targets this particular issue may prove to be a more useful solution regardless of which ROM is in use.
[FYT Android Head Units] edit:
I would also like to apologies for earlier !

The App Settings that I have it's even a tiny bit newer than what GTX put on his rom... so maybe it's my ROM...

I hope more will test your solution and bring more feedback.
[FYT Android Head Units] gtxaspec:
There's A new verison? Which version do you have? 1.10 is what my rom uses.
[FYT Android Head Units] edit:
Mine is 1.11 :)
[FYT Android Head Units] yuvalmesika:
[MENTION=520205]gtxaspec[/MENTION] does the Xposed module available for download?

The appSettings method doesn't work for me (I'm on V6 rom)
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION], when you are up to it, the monitortop hook works well, I've tested for the past few days on stock and custom v8, we should roll that into your Xposed app. I can do a pull request if you like.
[FYT Android Head Units] surfer63:
Yes, please do a pull request. I had already applied your previous version, but will undo that one. It was not applied to the Xposed global repo yet.

I didn't do (could not do) much past week.
[FYT Android Head Units] yuvalmesika:
[MENTION=520205]gtxaspec[/MENTION] [MENTION=2550900]surfer63[/MENTION] hi guys, did you manage to create us a monitor Bluetooth top Xposed module?
[FYT Android Head Units] Sim08u:
Should this theoretically work with non-Joying devices? I have an Eonon GA2167 device with an Allwinner T8 Octa-core processor. I have found someone who has been able to give me a rooted firmware. And now I am looking for solutions to voice dialling on my unit. I've tried Autovoice + tasker but had no success. So i'm willing to give this a go if you say it works. By the looks of it, so long as I can get to that page where I can select the default dialler, it should work? Thanks!
[FYT Android Head Units] gtxaspec:
In progress
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION]'s xposed app has been updated with the feature to disable the bluetooth app from staying on top.
[FYT Android Head Units] edit:
I might be asking a bit too much here but is it a change to develop the xposed module separately?

Thank you
[FYT Android Head Units] surfer63:
Techically it is extremely easy to do that, especially as you only need the hook and you can switch the module on/off in the xposed Installer. No settings screen necessary.

But why? Simply because you only need one module and want it to be as simple as possible? (note: no sarcasm, really want to know)

Note that multiple "dedicated" Xposed modules all working on the same apk, might lead to conflicts and might cause performance decreases.
[FYT Android Head Units] edit:
Because of the Play/Pause issue of you mod with media players (you press pause to pause the active media player and at the same time another player that it's in the background paused starts to play). I am still on December ROM (semi-stock because I made a lot of modifications to it, removing a lot of the Joying apps) with [MENTION=3917592]DBestman[/MENTION] Sofia NoKill Custom keys mod that handles playing and pausing well. I have xposed installed running fine with it's great addons (gpsfix and app settings). I would have liked the module separately because so far my unit runs fine as it is and I don't feel like changing it.

On top of that I admit I kinda got tired of testing, reflashing, tearing the dash apart and so on.... I kinda need a break and since my headunit runs fine as it is I would like to take advantage of that and bring only minor modifications to it if possible.

Thank you for understanding and help !
[FYT Android Head Units] gtxaspec:
[MENTION=309187]edit[/MENTION] thats a bug in the stock ROM. The mod doesn't cause that. You can use the Xposed modules other features if you don't want to use the custom keys.
[FYT Android Head Units] edit:
I am probably asking too much (again) but if that's the case why didn't you revert back to the stock december rom and build on it?

I am just curious and asking because for me it's a major issue and one of the reasons I am not using your ROM even if It's so good...

Thank you !
[FYT Android Head Units] gtxaspec:
That same bug is in the December and Jan builds...even older than that.

January is newer, has newer bt firmware and a newer kernel... You can use dbestmans Sofia server on my rom...
[FYT Android Head Units] edit:
Then how come on the December ROM that I am using everything works fine ..... I mean the Play/Pause button works as intended, only the active media player executes the command even if in the backgrouns PowerAmp is always present (the PowerAmp by design likes to be in the backgreound, loaded, ready to go)? (the reason I am still on this rom like I said)
[FYT Android Head Units] gtxaspec:
Weird, because I installed the Dec ROM to test and it was there, and gusten patched the bug in the September ROM...in his modded server.

Weird huh
[FYT Android Head Units] edit:
yeah... there is something going on... of course I don't have the knowledge to figure out what is and share it with you guys but on the other hand I am glad that it works.... i got so tired of all he firmware issues this headunit had since they decided to push it to android 6... and my stupidity for taking the jump from day 1.

I still believe that the answer is on the [MENTION=3076686]gustden[/MENTION] way of modding the Sofia server
[FYT Android Head Units] gtxaspec:
It will be fixed soon stand by
[FYT Android Head Units] edit:
My hope is on you and [MENTION=2550900]surfer63[/MENTION] . You guys are the only ones that still struggle to make things better for this headunit and I for one I am grateful for that.

If you can iron out the Play/Pause issue I'll say that your ROM it's the best ROM this unit will ever have.

BIG Thank you !
[FYT Android Head Units] ste2002:
No good the thread is used for that - it is also very important to be hidden in other's topic thread. IMHO.
[FYT Android Head Units] pcmicro:
Under Android 8.0, I am unable to change the dialer being used by Google Assistant to make a call. After telling assistant who to call, I click on the blue circle with the sideways "[" character, and then click the 3 vertical dots and go to Settings, but I don't find any options to select a dialer.

Is there a different way to select the dialer under Android 8.0?
[FYT Android Head Units] Oldpapa49:
I was wondering with out going through pages of posts, will this or can this be made to work on other units than joying
[FYT Android Head Units] surfer63:
I can't even find the app in the Google Play store on my PX5 on Andorid 8.0
[FYT Android Head Units] sweetnothings:
this is strange. i cant find any reason why this should not be listed in play store using Android 8.

i do not have any device with android 8, so i cant really check.

Can look someone with a android 8 phone if this is the case on non joying devices too? not that it makes any sense to install it on a phone but this will proof that its os and not device related.

when i have the time i will try to lift the target sdk version to oreo, may be i can see something going wrong.
[FYT Android Head Units] sweetnothings:
did you check under the app settings if any of the permissions requested is enabled? did you found the app on play store or sideloaded it?

i do not have any 8.0 device to test until now

edit: can you make a screenshot showing this a bit more clear to me?
[FYT Android Head Units] sweetnothings:
"Can", yes, but i am not sure if it would make any sense.

this app was made because the Joying BT Phone app DOES have an Activity accepting a phone number as input but does REJECT numbers with spaces, slashes or other non numeric characters (except "+")

As we cannot change the format Google passes the number to whatever dialer app we set to use, even if we reformat the numbers in the Google account, i made this tool as "middle man" to reformat the number while passing it to the dialer.

So in short, if really another dialer app, other than Joying, on a Android HU has the same lack of flexibility on accepting different number formats, i can integrate that, all i need to know is the pakage name and activity name of the dialer app.

atm, the folowing packages/activity are hardcoded in the tool and tried to find to pass a call:

- package: com.syu.bt , Activity: com.syu.app.PhoneActivity

- package: com.syu.bt , Activity: com.syu.bt.PhoneActivity
[FYT Android Head Units] Oldpapa49:
So I wonder on a Allwinner T8 if this could be possible..

I look for answers. But it is not Sofia type.... Does they Joying Software, is it Android Windows or Other
[FYT Android Head Units] surfer63:
No screenshot, sorry, but a more detailed "what did I do".

As mentioned: Using my Joying PX5 on Android 8 I could not find the app in the Play Store, not even when using the full address (https://play.google.com/store/apps/details?id=com.judlis.googlevoicecallhandler4joying).

So I downloaded it on my Motorola and copied it to my Joying and installed it. My motorola G5Plus runs Android 7.0 and is the phone I use in connection with my Joying unit.

Upon installation and first start it does not ask for permissions, so I went into apps and gave GVC handler phone access.

I also set the DPI to 161.

Now when I use "OK Google", "bel thuis" (call home), it finds the number, opens some kind of dialer window, where I can select top-right above the google street view image* of the address, the dialer app option to use: 3 option where I choose the GVC call handler.

I close everything and start again.

So after the "OK Google", "bel thuis" (call home), the dialer starts dialing, but it uses the last dialed number of my phone, not the number I "commanded" OK Google to use.

Note that my phone number has the correct +31 ........ international prefix (for the Netherlands) as I need to call it sometimes from abroad as well.

So with some tweaking it does work, but it somehow doesn't forward the selected number. Instead the BT dialer dials the last number.

Something I need to do, or something with Android 8?

(* I find it freaky that when using a contact which also has an address, it immediately shows the google street view image. But some might find this a "wow, great!" feature. I'm not sure what Google does with my contacts, but now it also has the address connected with that contact. If I was a facebook user, I would now immediately freak out)
[FYT Android Head Units] sweetnothings:
I have recompiled the app against api 27 , may this helps.

Can you please check if you can see the app in play store now?

Did you check or uncheck option to "Initiate Joying BT App twice" in settings activity?
[FYT Android Head Units] surfer63:
I still can't download it from the play store, so I downloaded it again on my phone and copied it to and installed it on my unit.

Now it works nicely.

If I enable the "initiate twice" option it doesn't work. Error: "can not dial in current state".

But without that it works now. Thanks a lot.
[FYT Android Head Units] reckert:
I can't download either, when I tried the link via a browser, it looks like it may be marked as compatible with phones and not tablets.
[FYT Android Head Units] sweetnothings:
OK guys, i have just uploaded a new build.

The new build hopefully has PlayStore compatibillity for PX5 Oreo now, but i cannot test it.

Please check out, if you can load it from PlayStore now.
[FYT Android Head Units] reckert:
I was able to download this one. Will test it out.
[FYT Android Head Units] Argevalo:
My Allwinner t8 head unit had the same problem with google voice call. This is how I made it work:

1_ Unistall the google application and install one that is for lolipop (older version)

2_ disable auto updates in google play services

3_ download and install google contacts from google store

4_ transfer your contacts from your cellphone to your head unit

5_ that is it. Follow instruction using the first time

If you want to use google search call offline you have to install google text to speech from play store and download the requiere language for offline call.

Let me know if you need help
[FYT Android Head Units] janlwi:
Hi ! Updated october 8.0 update. Installed the apk from Plays store. Phone permission. Ok Google works and stops with a Bluetooth bubble. Did a wrong thing ? Thanks

Installed JET 60 update. No change.
[FYT Android Head Units] RAN555:
Hi,

This app works on 10.25 chinese units?

10.25'' Android 8.1 Car Gps radio player navigation ID7 for BMW X1 E84 6 core wifi bluetooth 2GB RAM 32GB ROM?

Thank you
[FYT Android Head Units] Fredjbm:
hello,

I tried this app today.

But I can not find it in google assistant to chose this app to make voice call :/
[FYT Android Head Units] Spastro:
Just installed on my android 8.1 joying headunit and worked perfectly after setting it as default.

I'd gladly shoot you through a few bucks for sorting this out.
[FYT Android Head Units] Spastro:
Spoke to soon sadly.

So this is what happens for me.

1. Go to settings / apps

2. Clear defaults for Google app.

3. Say okay Google. Call home

4. Google says app not installed.

5. Press where is says call home.

6. Choose app prompt comes up.

7. Choose your app as default and Google starts calling using the Bluetooth dialler.

8. Hangup.

9. Try calling again. Works perfectly.

10. Doesn't work a third time.

11. Repeat the process of clearing Google default and follow the steps and the second voice call always works but never again.

Any thoughts? I tried clicking that first option in the app to dial twice, didn't work.
[FYT Android Head Units] pcmicro:
Thanks for your past work on this. I just bought a Joying head unit using the current USI7862 chipset which has 6GB RAM/128GB ROM. Surprisingly Joying apparently never fixed this issue, as when I tell Google Assistant to call someone, it responds with "Sorry, I can't make calls yet".

I gave your app a try, but when I gave Assistant tthe voice command the result was the same, and the 3-dot menu button never appears. I don't know if it's because I'm running Android 10, or because your app is specifically made for the sofia chipset. Do you have any suggestions? Also I'm curious if you ever released the source code.

I contacted the seller and they send me an updated firmware "Android 10.0 1024X600 1280X720 2021.7.5.zip" which I installed, but the results were the same.
[FYT Android Head Units] pcmicro:
The "GVC Callhandlert 4 Joying" app did not appear to be compatible with the Joying 7862 firmware. However after doing a factory reset I tried a suggestion from @Allan_Hun on changing the "Smallest Width" to 400 DPI under Settings > System > Developer options. The first few times I tried to make the call using Google Assistant it failed, but then it prompted me to choose which phone dialer to use, and I selected "BlueTooth", and "Use every time". When I told Assistant to "Call Mom", it displayed a confirmation icon which just says "Call", and I had to touch that before Assistant would dial the number.

Next I tried to set a higher "Smallist Width" DPI value, and I found that it works when I set it to 596 DPI. This resolution looks much better, but the icons are still noticeably bigger then when it is set to 720, so I continued to look for a better solution. I tried disabling the "Developer Options", and this restored the high resolution and allows Google Assistant to make the call! :)

Now the only annoyance is the confirmation button that says "Call" which I must touch with my finger before GA will dial the phone number. I had the same issue with my Dasaita PX6 after I allowed the Play Store to update the Google App (com.google.android.googlequicksearchbox) to a version higher then 11.30.12.29. The Dasaita firmware came with version 10.65.11.21 which is much smaller in size then all later versions (which became larger with each version). I upgraded it to version 11.1.9.29 which I found to also be fast -GA makes the call about 3 seconds after I tell it to call.

In comparison, version 11.30.9.21 took 6 seconds to make the call, and version 11.30..12 took 8 seconds.

I would like to downgrade the Google App on my Joying 7862 to use version 11.1.9.29 but since this is a system app and my Joying is not rooted, I don't know how it can be done. Perhaps the Google App can be replaced with the older one in the Joying firmware. Perhaps someone with more experience can tell me how ?
[Samsung Galaxy S8 & S8+ Cross Device Development] yash92duster:
Samsung - For Firmwares

To Rom Users - XDA Members

yash92duster - Google Edition

amarullz - Aroma Installer

SuperR - SuperR's Kitchen

ASSAYYED - Assayyed Kitchen TOOL

Ticklefish -Tickle My Android APK Tool

topjohnwu - Magisk

Chainfire - SuperSU

osm0sis - Busybox Installer

jesec - TWRP Recovery, Jesse Kernel

geiti94 - For Help/Guides

::indie:: - For Help/Guides

farovitus - For NOTORIOUS-KERNEL

amtra - For Help/Guides

malbert16442 - For Help/Guides

somadsul - For Help/Guides

tdunham - TouchWiz Unified Help/Guides

asc1977 - Help/Guides

thereassaad - Help/Guides

ambasadii - For Help/Guides

venkat kamesh - For Help/Guides

BlackMesa123 - For Help/Guides

Tkkg1994 - For Help/Guides & BatStock Kernel

ryan42680 - Boot Animations

zeroprobe - Zero Camera Mod

Winb33 - SamsungSans 1060 Fonts

Grouxho - GooglePackageInstaller Overlay

palaych - Help/Guides

edzamber - Help/Guides

one_love_420 - Help/Guides

CNexus - Help/Guides

Ouweshs28 - Help/Guides

djb77 - TGP Kernel

DRSDavidSoft - Galaxy Animations

AlexisXDA - Note 8 Port Apps

kill-switch - Note 8 Port Apps

Repulsa, thereassaad & Ouweshs28 - Air Command

thereassaad, a.raul, Wuby986 & koko115 - Private Mode

BlackMesa123 - Fix For Auto SMS Bug, Camera Fix & Many Guides
[Samsung Galaxy S8 & S8+ Cross Device Development] yash92duster:
*** Guide to Set Google Dailer InCallUI as Default ***

Open Settings App,

Locate to Application Manager and Open Default Application List

Choose Google Phone as Default Dailer

View attachment 4498216 View attachment 4498217

*** Guide to Install Apps to Data/App Folder ***

When new version of ROM comes out, then you can use this trick to install apps instantly.

* Firstly, Backup all Apks to SD card using the following app

Take a look at "App / SMS / Contact - Backup & Restore"

https://play.google.com/store/apps/details?id=mobi.infolife.appbackup&hl=en

* Then do a Full wipe ( System, Internal, Data, Cache, Dalvik/ART Cache )

* Install the new version of ROM, let it boot

* Then, Copy all apks to "data/app" folder using "Root Explorer" app

* Finally do a Reboot, and all apps gets installed, you just need to sign into them

*** RMM State Lock Information ***

Read the following post to know about RMM State Lock

https://xdaforums.com/showpost.php?p=75360965&postcount=22

by [MENTION=6911575]BlackMesa123[/MENTION]

*** Guide to Hide Navigation Bar And Use Swipe Gestures ***

Download the App

https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures&hl=en

Edit build.prop,

Add this line

qemu.hw.mainkeys=1

Reboot

Now the Nav Bar will be gone,

Open All In Gestures app

Set Gestures for home

(swipe up) Recents (swipe left edge, swipe right bottom corner) and back (swipe right edge)

​
[Samsung Galaxy S8 & S8+ Cross Device Development] yash92duster:
[YOUTUBE]t5UiXytUrTE[/YOUTUBE]

1. Google Edition Battery Life?

A:

2. Antutu Scores?

A:

3. Why did you add " KNOX " Apps inside ROM AROMA Zip?

A: Some users need them for AirWatch to work.

Klms Agent.apk is required for AirWatch MDM App to work.

4. How to Set Google Dailer InCallUI as Default?

A: open Settings App,

Locate to Application Manager and Open Default Application List

Choose Google Phone as Default Dailer

5. Netflix not working.How to fix?

A: Use Root Explorer app

Locate to system/lib folder

Rename

liboemcrypto.so.

To

liboemcrypto.so.bak

Reboot

6. UPSM - Ultra Power Saving Mode not working?

A: To use UPSM you must use Samsung Keyboard.

Make sure you checked Samsung Keyboard in Aroma while installing the ROM

7. No Finder in Samsung Launcher?

A: For Finder you must use S_Finder app.

Make sure you checked S_Finder app in Aroma while installing the ROM

8. My Second Sim not working, shows emergency calls only. How to fix it?

A: If Only SIM1 Slot works ( eg. Vodafone ) and SIM2 Slot ( eg. Jio ) shows Emergency calls,

then issue is STK, STK2 app

Make sure you checked STK, STK2 apps in Aroma while installing the ROM

9. My Samsung Sans Fonts disappeared after updating them in Galaxy Store? How to fix it?

A: ROM has custom Samsung Sans.apk with 1060 fonts,

So don't update this app in Galaxy store

View attachment 4440762

How to fix it:

Delete the samsungSans app in both

Data/app/SamsungSans & System/app/SamsungSans

Then

Reboot once

ThenCopy the SamsungSans.apk from rom zip to system/app

Set Permissions

Reboot and Enjoy

Dont forget, Never update this app again.

10. Fingerprint not working? How to Fix it?

A: Flash ROM,

In Aroma Choose Stock Apps,

Let the ROM Boot,

Setup your Fingerprint,

Then Dirty Flash ROM And Choose Modded Apps,

Reboot.

Now Fingerprint will work fine and you will have modded settings too.

11. ?

A:

​
[Samsung Galaxy S8 & S8+ Cross Device Development] _moelle:
i got an issue writing the symlinks on recovery :(