Database Info

[Think Tank] Modifying G1 to enable Navigation - THUNK!

This has been solved! Please see around page 8 of this thread.
esmith972 said:
Here guys, all wrapped up.
Make sure you have CyanogenMod 4.2.3.1, by the way.
1) Unzip zip to desktop
2) Run Part 1.bat
3) When prompted to press any key, do so; the phone will reboot
4) When your phone is running again, run Part 2.bat
5) When prompted to press any key, the installation process is done.
6) Make sure GPS is enabled
7) Open Maps and press OK
8) Press Menu
9) Press Directions
10) Enter an end point
11) Click Go
12) Just under "Show on map", click Navigate.
13) When prompted to install the voice codec, do so.
14) Enjoy.
http://www.mediafire.com/?lioyoy2ydzu
Click to expand...
Click to collapse
If you have no navigation option after the above steps try installing Google Voice from the market:
1wayjonny said:
AWESOME !!! Took another users post to install google voice and BAM the navigation button showed up!!!! Woot!
Click to expand...
Click to collapse
===============================================
This is a continuation of a discussion that started in this thread: http://forum.xda-developers.com/showthread.php?p=4918275
My best guess as to why navigation works in the emulator but not on the phone has to do with what kind of device the Maps application thinks it is running on.
For example, if you start maps and press menu->more->about and look at the "Platform" line, that will be different according to the device (emulator or G1 or other) that you are running on. What we need to change (I think) would be that setting.
According to this link, you can programatically get that string (I'm pretty sure they were talking about that string) through the API. Anyone more familiar with the API know where that string is stored?
Also, any other suggestions as to why it won't work on a real phone may be discussed in this thread.

What does platform say on the emulator? According to the info in that link, it should be null.

Cyanogen 4.3.2.1 Instructions http://forum.xda-developers.com/showpost.php?p=4921092&postcount=196

On my way to verizon to see what I can find out off the droid.... wonder if I can bring my laptop in and plug it up.... lol

[email protected] said:
What does platform say on the emulator? According to the info in that link, it should be null.
Click to expand...
Click to collapse
I fired it up to check. The exact string is "android:unknown-generic-sdk"

followinginsanity said:
On my way to verizon to see what I can find out off the droid.... wonder if I can bring my laptop in and plug it up.... lol
Click to expand...
Click to collapse
You should then just do adb pull /system C: and then bring it here. I'm sure they won't mind you trying to break their system

One thing I noticed is that it repeatedly references epc.tmobile.com as the provider. Let's hope they aren't using that and checking for verizon or this is a fool's quest.

Some interesting things to note:
The Version string of the Maps app is different in the emulator than on the phone as well.
Emulator: "3.2.0 (#3232) Web"
Phone: "3.2.0 (#3232) gmm-google"
Also, there was a blog post put up before 1.5 was released showing a way that you could spoof the ANDROID_ID on the phone by modifying a database (article here). I don't know if this is valid since at the end of the article he stated that they were supposed to fix it with 1.5.
Edit: I may have gotten ahead of myself. The ANDROID_ID string I think is not the correct one that I was looking for. That seems to be unique to the phone and not to the model, maker, whatever.

octobclrnts said:
Some interesting things to note:
The Version string of the Maps app is different in the emulator than on the phone as well.
Emulator: "3.2.0 (#3232) Web"
Phone: "3.2.0 (#3232) gmm-google"
Click to expand...
Click to collapse
Hmm mine actually says "3.2.0 (#3232) gmm-android-tmobile" for the version number... interesting.

[email protected] said:
Hmm mine actually says "3.2.0 (#3232) gmm-android-tmobile" for the version number... interesting.
Click to expand...
Click to collapse
I'm thinking that we're going to need someone to go to a Verizon store and see what the droid says there.

JAguirre1231 said:
I'm thinking that we're going to need someone to go to a Verizon store and see what the droid says there.
Click to expand...
Click to collapse
The question is, even if we knew what the droid said - how can we change our Platform string to match. It's clearly not reading off of the build.prop file (and neither is the device string in the about phone menu).
Maybe it's a database issue (the database gets initialized the first time the phone is booted to the values in the build.prop file?) that just needs to be wiped.

octobclrnts said:
The question is, even if we knew what the droid said - how can we change our Platform string to match. It's clearly not reading off of the build.prop file (and neither is the device string in the about phone menu).
Maybe it's a database issue (the database gets initialized the first time the phone is booted to the values in the build.prop file?) that just needs to be wiped.
Click to expand...
Click to collapse
Yeah, I know where your coming from. However, I think it would be easier if we at least knew what build we were aiming for

JAguirre1231 said:
Yeah, I know where your coming from. However, I think it would be easier if we at least knew what build we were aiming for
Click to expand...
Click to collapse
Well let's see... what do we know so far?
The version string shows up differently on different phones and the emulator shows up with a general one, but all have the same number. So it's probably not that, it seems to be building that from information it gathers elsewhere on the phone.
It's probably not reading which network is being used since that would block the emulator(which isn't running off the verizon network).
The only thing left I can think of immediately is the model string. That would actually make perfect sense, check against the model string to make sure that it's either the emulator or the droid. Otherwise turn off navigation. Changing that would be my first thing to aim for.

[email protected] said:
Well let's see... what do we know so far?
The version string shows up differently on different phones and the emulator shows up with a general one, but all have the same number. So it's probably not that, it seems to be building that from information it gathers elsewhere on the phone.
It's probably not reading which network is being used since that would block the emulator(which isn't running off the verizon network).
The only thing left I can think of immediately is the model string. That would actually make perfect sense, check against the model string to make sure that it's either the emulator or the droid. Otherwise turn off navigation. Changing that would be my first thing to aim for.
Click to expand...
Click to collapse
How tough is that to do?
Just wondering since if easy someone would of tried already.

Coderedpl said:
How tough is that to do?
Just wondering since if easy someone would of tried already.
Click to expand...
Click to collapse
No clue, probably need someone with experience making ROMs for that info. I'm guessing it has to be in some file somewhere. Seems highly unlikely they'd have done something as crazy as building that into the hardware.

Well, I modified cyanogen's build.prop file to include the lines below:
ro.build.id=ECLAIR
ro.build.version.sdk=5
ro.build.version.release=2.0
ro.product.name=sdk
ro.product.device=generic
ro.product.manufacturer=unknown
As well as put the Maps.apk into the system/app folder in his update file. Then I resigned the file, put it on my SD card and wiped my phone. I installed the "new" rom and booted up. The maps app works exactly as it should sans navigation options. The Version string i have now is the "3.2.0 (#3232) gmm-androidd-tmobile" one but the Platform string is unchanged.
I noticed in the "About Phone" menu, the Model Number (T-Mobile G1) was unchanged but the Firmware version said "2.0" and I'm pretty sure it said "1.6" before.

octobclrnts said:
Well, I modified cyanogen's build.prop file to include the lines below:
ro.build.id=ECLAIR
ro.build.version.sdk=5
ro.build.version.release=2.0
ro.product.name=sdk
ro.product.device=generic
ro.product.manufacturer=unknown
As well as put the Maps.apk into the system/app folder in his update file. Then I resigned the file, put it on my SD card and wiped my phone. I installed the "new" rom and booted up. The maps app works exactly as it should sans navigation options. The Version string i have now is the "3.2.0 (#3232) gmm-androidd-tmobile" one but the Platform string is unchanged.
I noticed in the "About Phone" menu, the Model Number (T-Mobile G1) was unchanged but the Firmware version said "2.0" and I'm pretty sure it said "1.6" before.
Click to expand...
Click to collapse
You would be right, cyanogen only makes builds from soure code. And the source code for 2.0 hasn't been released yet. So, obviously we need to have a modified build.prop before we flash a rom, or it won't read it correctly

I was wrong. I had that same modified build.prop on my phone before I wiped, I just hadn't noticed that the firmware version number had changed. Perhaps I didn't modify the right valued to also get the model number to change.

I have decompiled Maps.apk using dedexer 1.7. Here is all the stuff it gave me. I used dexdump last night and it gave me something similar. Im using notepad++ to search through all the files for keywords but I cant find anything interesting. Maybe you can...
http://rapidshare.com/files/305162283/Maps.apk-dedexed.rar.html

staulkor said:
I have decompiled Maps.apk using dedexer 1.7. Here is all the stuff it gave me. I used dexdump last night and it gave me something similar. Im using notepad++ to search through all the files for keywords but I cant find anything interesting. Maybe you can...
http://rapidshare.com/files/305162283/Maps.apk-dedexed.rar.html
Click to expand...
Click to collapse
Cool I'll go through it in a min. and see if I can find anything interesting.
edit: opened it up and there is googlenav stuff com/google
There is also an android folder too. I'm going to look there first
As I'm going through these I found that Google has these things filled with static locations. Haven't found any that seem to lock it down, but that's not to say there aren't any

[HOWTO] Enabling built-in VOIP/SIP client and Messaging app

I managed to get the native SIP client working. I did it with Slim Bean (current GIT version), but it will probably work with most other ROMs as well. These instructions are for building your own ROM.
This also builds the messaging app, which might be interesting for DEB/LTE users (replace 'flo' with 'deb').
Modifications:
device/asus/flo/device-common.mk
add line: $(call inherit-product, $(SRC_TARGET_DIR)/product/telephony.mk)
device/asus/flo/overlay/frameworks/base/core/res/res/values/config.xml
change: <bool name="config_voice_capable">false</bool> to true
add line: <bool name="config_sip_wifi_only">false</bool>
add line: <bool name="config_built_in_sip_phone">true</bool>
device/asus/flo/system.prop
change: ro.telephony.default_network=9 to 3
(3 = SIP)
Build the ROM.
These changes will result in the proper packages being built, added to the ROM and make the Phone app show up (while the app shows up as phone, it's not actually part of 'Phone.apk', it's in 'Dialer.apk').
Both incoming and outgoing calls work.

Sweet, and first to comment. Double sweet
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 02:33 PM ---------- Previous post was at 02:29 PM ----------
So by what my limited brain is reading changing those lines of code plus the play store apk will allow flo to make calls on sip?(I still gotta Google sip lmao)
Sent from my Nexus 7 using XDA Premium 4 mobile app

Does that mean this can be use to implement gsm calls on deb?
Sent from my Nexus 7 LTE (deb) using Tapatalk 4

Crwolv said:
[/COLOR]So by what my limited brain is reading changing those lines of code plus the play store apk will allow flo to make calls on sip?(I still gotta Google sip lmao)
Click to expand...
Click to collapse
Yes. Got it working without the app. One additional file needs to be changed.

Raverbunny said:
Does that mean this can be use to implement gsm calls on deb?
Click to expand...
Click to collapse
Maybe. The hardware most likely has the required capabilities, but I have no idea if the firmware does and if the required drivers are there. Some more changes/configuration may be required.
At least, you would get the messaging app.

Will see if anyone wants to try, gsm calls was attempted on the old Nexus 7 tilapia but never achieved, just hope the same limitations aren't on place here
Sent from my Nexus 7 LTE (deb) using Tapatalk 4

Raverbunny said:
Will see if anyone wants to try, gsm calls was attempted on the old Nexus 7 tilapia but never achieved, just hope the same limitations aren't on place here
Sent from my Nexus 7 LTE (deb) using Tapatalk 4
Click to expand...
Click to collapse
I tried this. GSM calls are no go with a regular voice enabled SIM. SIP does work but the sound quality is very choppy for some reason both with BT and speakerphone.

I tried this for DEB, but the tablet will not boot - could not even display the boot animation.
Any suggestions?

I am currently setting up a build environment to try this..
Shame Google would deprovision the ability to configure, make and receive sip calls from the stock Nexus 7 LTE/WIFI Rom..
I guess that's the trade off if they want the carriers to pick the tablet up..
Sent from another unlocked T-Mobile iPhone 5, Because they haven't released the Nexus 5..!

For those who don't want to build their own rom:
Google Voice and Groove IP (together) from the play store allow making and receiving voice and text calls. I'm using a flo unit in the US.

tobdaryl said:
For those who don't want to build their own rom:
Google Voice and Groove IP (together) from the play store allow making and receiving voice and text calls. I'm using a flo unit in the US.
Click to expand...
Click to collapse
But that's US only. At home I don't need SIP enabled. Using an AVM Fritz!Box and Fritz!Phone is working well. While travelling I could use a VPN connection to connect to my home network and again use Fritz!Phone, but havent tried it so far.

JobSup said:
But that's US only. At home I don't need SIP enabled. Using an AVM Fritz!Box and Fritz!Phone is working well. While travelling I could use a VPN connection to connect to my home network and again use Fritz!Phone, but havent tried it so far.
Click to expand...
Click to collapse
Native SIP support was the goal of this thread, not promoting what you use.. Please refrain from cluttering up the thread.
I tried tri.andro's mod on a DEB and got the sane results as HowardZ..
Sent from another Nexus..
7 LTE...

HowardZ said:
I tried this for DEB, but the tablet will not boot - could not even display the boot animation.
Any suggestions?
Click to expand...
Click to collapse
Ok, my booting problem seemed to be related getting proprietary files off the tablet (problems running extract-files.sh)
The easiest way to get all the proprietary files off the tablet without error is to install offical CM-deb on the tablet and then extract the files. Using a Google stock android tablet results in a few errors.
I now have a working CM branched off the official CM-deb with SIP working OK.
Thanks Ops, for the instructions.

Care to post your build.? To save me/us the trouble..? Your time is greatly appreciated..
Sent from another unlocked T-Mobile iPhone 5, Because they haven't released the Nexus 5..!

maconsultant said:
Care to post your build.? To save me/us the trouble..? Your time is greatly appreciated..
Sent from another unlocked T-Mobile iPhone 5, Because they haven't released the Nexus 5..!
Click to expand...
Click to collapse
If you want my builds, they are here:
https://drive.google.com/folderview?id=0B88bR12MKYUKVFZtTGpNel8wTjA&usp=sharing#list
My github is AAN3AC/android_device_asus_deb

Hi, thanks for the sharing, though It didn't work out on my device, does it matter if I'm not in the US?

Can I do this on a stock rooted 4.4.2 Nexus 7 2013? I just picked mines up yesterday so its not rooted yet, I am willing to root if I can send text messages on my wifi model

navigation bar

Do anyone know how to hide the navigation bar in L29 ?

loiuslim said:
Do anyone know how to hide the navigation bar in L29 ?
Click to expand...
Click to collapse
1. Need write to Huawei and ask add option (Chinese AL00 has this option already)
2. Need to modify hw_defaults.xml in cust and add setting. But there is no way to modify cust. His state returned to default after phone's restart Do not edit hw_defaults.xml - it is wrong way.

GMD Immersive from Google Play

5[Strogino said:
;70574588]1. Need write to Huawei and ask add option (Chinese AL00 has this option already)
2. Need to modify hw_defaults.xml in cust and add setting. But there is no way to modify cust. His state returned to default after phone's restart
Click to expand...
Click to collapse
Already written to Huawei support regarding this. They answered: unfortunately it is not possible.
Local (CZ) official phorum answered like this: this function would be barely required by users in Europe.
So no interest from Huawei to help in this matter. :silly:

Tomas___ said:
Already written to Huawei support regarding this. They answered: unfortunately it is not possible.
Local (CZ) official phorum answered like this: this function would be barely required by users in Europe.
So no interest from Huawei to help in this matter. :silly:
Click to expand...
Click to collapse
It's possible they just don't want to do it. Everything is possible on Android...

bossei said:
It's possible they just don't want to do it. Everything is possible on Android...
Click to expand...
Click to collapse
Yes they dont want to do it. The reason why? It is much easier to say: unfortunately it is not possible, then to be open to the customers and actively approach to their wishes.
And it WOULD NOT require so much activity from Huawei, because Asian version of Mate 9 is able to hide the nav bar.

This does the job, but it is a bit of a nuisance at times.
https://play.google.com/store/apps/details?id=com.gmd.immersive

Google Assistant's Call screening (From pixel 3)Partially Working on our beloved Mi A

I don't know if you guys've heard about it but Google introduced a (of many) new feature (exclusive to pixel lineup) with the pixel 3 and later coming to pixel 2 and.
Since the early days of Google now and later Google Assistant I've dreamed of a way to make your AI ASSISTANT speak for you on your calls, but sadly then it was just a dream... Until this was announced and then I came up on this thread
By Mr George Burduli
[email protected]
https://www.xda-developers.com/enable-pixel-3-call-screening-pixel-2-pixel/
I'm not a Dev by any means and am not gonna be held responsible for anything that happens to your phone.
Your doing this on your own freedom.
Requires Rooted device
Text editor
Google dialer built in rom(maybe will work if installed?)
Android pie based rom(
maybe)
I tried it on our Mi A1 and it works... Well partially... For me the phone does show the words the other person is taking but he can't hear the assistant's voice.
While following the steps on the above thread you may notice that lines of code may or may not be missing!
Just add them on... Or if you're lazy just copy paste the below lines of code
To above the line
{
<\map>
}
{ <boolean name="__data_rollout__SpeakEasy.CallScreenOnPixelOneAndTwoRollout__launched__" value="true" />
<boolean name="__data_rollout__SpeakEasy.OverrideUSLocaleCheckRollout__launched_" value="true" />
<boolean name="G__enable_speakeasy_details" value="true" />
<boolean name="G__speak_easy_bypass_locale_check" value="true" />
<boolean name="G__speak_easy_enabled" value="true" />
}
As shown in screenshot
/data/data/com.google.android.dialer/shared_prefs/*dialer_phenotype_flags.xml.
Save then fstop the dialer app and boom!
All thanks to George Burduli
I just shared my happiness to other mi A1 users (others may try it too!)
I'm on Pixel Experience Rom based on pie
Hope someone capable can help fix the problem with the other person not being able to hear the assistant:laugh:.
Let me know if it worked for you.

interesting

Hehehe
xxqxpxx said:
interesting
Click to expand...
Click to collapse
if possible try it!!!

i'll try it on stock pie rom next!

tried on AEX oreo didn't work

xxqxpxx said:
tried on AEX oreo didn't work
Click to expand...
Click to collapse
Try on pie... Since pixel 3 was on pie...
Also try using a us VPN the first time since it is only released in the United States as of now

Since the first day this method has been out I've been trying for days to make the person hear the assistant on my Mi A1. It doesn't work. IDK why is this. Even the first Pixels have it working. I thought an update to the app will make it work on the 1st Pixels and every other phone but no. Some voice packages core seem missing? I have no idea.

I m on nougat device moto e4 plus With a patched google dailer apk I can't find the file dialer_phenotype_flags.xml
Can J just add that xml file in the folder and wil it work.. Would anybody mind sharing that file here...

Question Help me! Samsung Galaxy S22 Ultra Call Recording not available

Hello guys!
Recently I bought Samsung Galaxy S22 Ultra. BUT there is no way that I can record calls. I'm from Bulgaria and it is some kind of regulation crap. I mean when I go to the options in the dialer app the option for call recordings is not present at all.
Most of my calls are for work with tons of instructions about this and that and I take them either from the car or somewhere without access to notes and pens etc. On my previous phone I found an app that enebled native call recording without rooting somehow... It was P30 Pro and the app in question I found here in XDA. However for my new phone I can't find anything... I tried all of the free and paid Google Play apps but they record only me and nothing from the person I'm talking with... Help me please!!!
Somewhere I read that I need to change the CSC code. Whatever it means... No idea how tho... Other thing I read was to root the phone. I've never done that as well... Basically I'm thinking of going to some randome phone repair shop and ask them to find me a solution whatever it takes... But first I decided to ask here.
If you have any idea what to do please include some instructions for dumb people like me with no experience in fiddling with phones etc..
Big thanks in advance!
I should probably tell you that I've tried this
https://forum.xda-developers.com/t/...cord-phone-calls-from-the-phone-line.1441643/
And lots of things that are already written here as suggestions but... nothing....

I am trying out CallApp Contacts. So far it seems to work for 2 way recording. I am in the US and we do not have call recording here.

First of, do you know your phone model and CSC code? You should be able to spot it in Settings ->About phone -> Software information under Build number and Service provider software information.
Samsung only activates native call recording on the India firmware, so you will probably have to download that version of the firmware.

Do you still have said old phone (P30 Pro) & the download for the app on it?
Just asking cause you could send the app to your S22 from the other phone...

dalepl said:
I am trying out CallApp Contacts. So far it seems to work for 2 way recording. I am in the US and we do not have call recording here.
Click to expand...
Click to collapse
Thanks for the suggestion but I've tried that app both as free and paid version without any success...

ShaDisNX255 said:
First of, do you know your phone model and CSC code? You should be able to spot it in Settings ->About phone -> Software information under Build number and Service provider software information.
Samsung only activates native call recording on the India firmware, so you will probably have to download that version of the firmware.
Click to expand...
Click to collapse
Following your steps I found this - oxm eux. That is it right?
About the firmware - do you know how I would do that? I mean how to download and install the indian version? Would that affect the warranty or anything important?

AlphaTekk Epoch said:
Do you still have said old phone (P30 Pro) & the download for the app on it?
Just asking cause you could send the app to your S22 from the other phone...
Click to expand...
Click to collapse
Yes I still have the app. I tried to install it but it returns some error. I'll attach a screenshot here.

In my previous phone Xiaomi Mi11 Ultra, TruePhone app work perfectly with call record's, but now with Samsung S22 Ultra and Android 12 don't work.
For me also call record's is very important, but i don't have the time and experience to change regions with Sammobile to make the call records work.
I am also from Bulgaria and have tried most of the available recording offers.

Her are some options
Non Root :
Change CSC. You needs paid tool, search SamKey and you will find lots result on XDA. This option is OK if you don't want to root but here your CSC will needs to change and network optimization won't be same as your own CSC
Root :
Modify CSC and enable call record, bit difficult if you are not pro witn modding
Use a ROM with Auto call record option (check development section)

dr.ketan said:
Her are some options
Non Root :
Change CSC. You needs paid tool, search SamKey and you will find lots result on XDA. This option is OK if you don't want to root but here your CSC will needs to change and network optimization won't be same as your own CSC
Root :
Modify CSC and enable call record, bit difficult if you are not pro witn modding
Use a ROM with Auto call record option (check development section)
Click to expand...
Click to collapse
Thanks for the suggestion! Maybe will try to do that... But can you give me some more info about what it means that network optimization won't be the same as my own CSC? Does that mean that I'm gonna lose connection here and there or some kind of fees?
Also how this change of the CSC code is going to affect my warranty?

csc change will void your warranty, and yes it is possible that your call, internet connection over mobile data may not be as good as it was/is on your current csc, but not a guarantee, you should check to find out if your prepared to sacrifice warranty for call recording, you could always reflash your original firmware

gav83collins said:
csc change will void your warranty, and yes it is possible that your call, internet connection over mobile data may not be as good as it was/is on your current csc, but not a guarantee, you should check to find out if your prepared to sacrifice warranty for call recording, you could always reflash your original firmware
Click to expand...
Click to collapse
Well... The essentials of my work is talking on the phone and usually that includes tasks that I need to do with all of the details about them. We are working on communicating through e-mail but we are not there yet. The warranty is not that big of a concern but potential problems with the reception etc ... now that scares me...
Thanks for your time! I'll think about it... If you come up with something that is less risky please share!

My phone doesn't have call recording in the call app, but I just tried this one after some research, configured it, and made a call and it works
If this app ain't available in your country you could try an "index of" search or I can pull and upload the apk for you

gav83collins said:
My phone doesn't have call recording in the call app, but I just tried this one after some research, configured it, and made a call and it works
View attachment 5596183View attachment 5596185
View attachment 5596187View attachment 5596189View attachment 5596191View attachment 5596199
If this app ain't available in your country you could try an "index of" search or I can pull and upload the apk for you
Click to expand...
Click to collapse
I will try it as soon Is I can and will post the results here. If for some reason I cannot find it or cannot download it I will contact you for assistance! Thank you!

yeah no wor
AVTOfficial said:
I will try it as soon Is I can and will post the results here. If for some reason I cannot find it or cannot download it I will contact you for assistance! Thank you
Click to expand...
Click to collapse
yeah no worries, ive got it, and app cloner, (an app to clone and modify apk files) uploading to gdrive ready to link you if needed, good luck

gav83collins said:
yeah no wor
yeah no worries, ive got it, and app cloner, (an app to clone and modify apk files) uploading to gdrive ready to link you if needed, good luck
Click to expand...
Click to collapse
I've tried the app. Sadly with no luck... I copied all the settings from your screenshots with the exception of enabling auto recordings. However the app doesn't create files... I'll upload screenshots of my sad empty folder... Do you know if I did something wrong? I have enabled all the permissions...

AVTOfficial said:
I've tried the app. Sadly with no luck... I copied all the settings from your screenshots with the exception of enabling auto recordings. However the app doesn't create files... I'll upload screenshots of my sad empty folder... Do you know if I did something wrong? I have enabled all the permissions...
Click to expand...
Click to collapse
give me a couple of minutes, im creating a youtube video and xda post, its currently uploading

Deleted

gav83collins said:
Check this video
oh the video editing software is glitching hiding that number lol, nm, thats what happens when you rush lol
Click to expand...
Click to collapse
Thank you very much for the trouble with the video!!! However no luck with me... I reinstalled the app to be sure that I follow your exact steps. I made some screenshots proving that I have the accessibility permissions enabled correctly ... But still my recordings folder stays empty...

AVTOfficial said:
Thank you very much for the trouble with the video!!! However no luck with me... I reinstalled the app to be sure that I follow your exact steps. I made some screenshots proving that I have the accessibility permissions enabled correctly ... But still my recordings folder stays empty...
Click to expand...
Click to collapse
oh wow, really strange, sorry then, idk what to say, it worked for me as you seen, you could try flashing the latest eux firmware its a european unlocked, and im in the uk im also unrooted