Database Info

How to edit build.prop for faster data speeds Inspire CM7.2 RC2

My first post. It wont let me post into correct forum yet. Feel free to move it. Here is a link to the thread I wanted to respond to. http://forum.xda-developers.com/showthread.php?t=982082
This is my configuration of my build.prop
[ro.ril.def.agps.mode]: [2]
[ro.ril.disable.fd.plmn.prefix]: [23402,23410,23411]
[ro.ril.disable.power.collapse]: [0]
[ro.ril.ecc.HTC-ELL]: [92,93,94]
[ro.ril.ecc.HTC-GCC]: [999,112,997]
[ro.ril.ecc.HTC-WWE]: [999]
[ro.ril.enable.a52]: [0]
[ro.ril.enable.a52.HTC-ITA]: [1]
[ro.ril.enable.a53]: [1]
[ro.ril.enable.a53.HTC-ITA]: [1]
[ro.ril.enable.amr.wideband]: [1]
[ro.ril.enable.dtm]: [1]
[ro.ril.enable.sdr]: [1]
[ro.ril.gprsclass]: [34]
[ro.ril.hsdpa.category]: [112]
[ro.ril.hsupa.category]: [6]
[ro.ril.hsxpa]: [5]
Radio : 12.39a.60.19P_26.06.06.30_M
Ril : HTC-RIL 2.2.0079HM
Cyanogenmod 7.2.0 RC2
Kernel Linux version 2.6.35.14 cyanogenmod
This build is getting me almost 7mbps down and 1.5mbps up
Here is a link to my speedtest.net http://db.tt/V8YVeNX3
Location is Boise, ID and was pulling those speeds at -81 to -87 dbm
Credit goes to original posters in development forums linked above and http://forum.xda-developers.com/archive/index.php/t-1401209.html as this build is a mixture of both the threads.

it may be just me, but i fail to see how this is a how to...
But i will give the config a try and see what kind of speed increase i get! Nice work.

Its not a how to it is just the configuration that works for me. I can't post in development forums until 10 posts. I however did link to the dev forum I was reading.
Cyanogenmod 7.2.0 RC2 12.39a.60.19P_26.06.06.30_M
HTC-RIL 2.2.0079HM
Kernel Linux version 2.6.35.14 cyanogenmod-g295e82f

Why not just reply to a few more threads first, get to ten, and then post your dev-related reply to the appropriate thread, rather than starting a new one?
Sent from my Inspire 4G using xda premium

Hindsight I should have. I was in the moment late at night. Sorry for creating multiple threads.
But if this build has helped anyone let me know thanks!

Nokia 6 root and custom rom (Lineageos)

Hello there,
I am looking into root my nokia 6 phone TA-1033.
[cda.skuid.brand]: [NOKIA]
[persist.sys.exif.model]: [Nokia 6]
[ro.board.platform]: [msm8937]
[ro.boot.hardware]: [qcom]
[ro.build.version.sdk]: [25]
[ro.hardware]: [qcom]
[ro.product.brand]: [Nokia]
[ro.product.manufacturer]: [HMD Global]
[ro.product.model]: [TA-1033]
[ro.product.model.num]: [00WW]
[ro.product.name]: [TA-1033_00WW]
[ro.revision]: [0]
My main focus is on TWRP software to use as recovery.
I followed this link (https://forum.xda-developers.com/nokia-6/development/recovery-twrp-3-2-1-0-nokia-6-t3762890) but this is only for recovery mode. Here I am looking to root the phone. SuperSu is good to use?

ggnherofree said:
Hello there, I am looking into root my nokia 6 phone TA-1033...
Click to expand...
Click to collapse
I don't have this device but, you may be able to obtain some member guidance within the following thread within the area of the forum that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3702354
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Android 9 From: HF_px5_9.0_ota.

Hi mates,
I just got it today, I didn't test it or flash it yet, it was created on the following date:
ui_print("Target: rockchip/rk3368/rk3368:9/PQ2A.190205.003/root03 26 1920:userdebug/test-keys");
so its unfortunately not the newest of the newest fw A9 but maybe you guys like to test it too?
DL: https://yadi.sk/d/3b5c-8Mqd67pXQ ... rk3368-ota-eng.root.zip
success

Sure, it is Android 9 and that it should work on px5? Anyone tried this and can confirm?

gforums said:
Sure, it is Android 9 and that it should work on px5? Anyone tried this and can confirm?
Click to expand...
Click to collapse
Hi mate,
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PQ2A.190205.003
ro.build.display.id=rk3368-userdebug 9 PQ2A.190205.003 eng.root.20190326.192040 test-keys
ro.build.version.incremental=eng.root.20190326.192040
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2019-03-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Tue Mar 26 19:20:03 CST 2019
ro.build.date.utc=1553599203
ro.build.type=userdebug
ro.build.user=root
ro.build.host=meng_book2
ro.build.tags=test-keys
ro.build.flavor=rk3368-userdebug
ro.build.system_root_image=true
ro.product.model=rk3368
ro.product.brand=rockchip
ro.product.name=rk3368
ro.product.device=rk3368
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=rockchip
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rk3368
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=rk3368-userdebug 9 PQ2A.190205.003 eng.root.20190326.192040 test-keys
ro.build.fingerprint=rockchip/rk3368/rk3368:9/PQ2A.190205.003/root03261920:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/rockchip/rk3368/system.prop
#
#
# system.prop
#
#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
# Default ecclist
ro.ril.ecclist=112,911
ro.opengles.version=196610
wifi.interface=wlan0
rild.libpath=/vendor/lib64/libril-rk29-dataonly.so
rild.libargs=-d /dev/ttyACM0
vendor.rild.libpath=/vendor/lib64/libril-rk29-dataonly.so
vendor.rild.libargs=-d /dev/ttyACM0
persist.tegra.nvmmlite = 1
ro.audio.monitorOrientation=true
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#add Rockchip properties here
ro.rk.screenoff_time=60000
ro.rk.screenshot_enable=true
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&source=android-home
ro.rk.install_non_market_apps=false
vendor.hwc.compose_policy=6
sys.hwc.compose_policy=6
sys.wallpaper.rgb565=0
sf.power.control=2073600
sys.rkadb.root=0
ro.sf.fakerotation=false
ro.sf.hwrotation=0
ro.rk.MassStorage=false
ro.rk.systembar.voiceicon=true
ro.rk.systembar.tabletUI=false
ro.rk.LowBatteryBrightness=false
ro.tether.denied=false
sys.resolution.changed=false
ro.default.size=100
persist.sys.timezone=Asia/Shanghai
ro.product.usbfactory=rockchip_usb
wifi.supplicant_scan_interval=15
ro.factory.tool=0
ro.kernel.android.checkjni=0
#set default lcd density for rk3399
ro.sf.lcd_density=240
ro.adb.secure=0
#disable task_snapshots
persist.enable_task_snapshots=false
ro.product.locale=en-US
ro.product.manufacturer9=HengChangTong
ro.product.model9=H660000
ro.product.customer=HCT
ro.product.hostname=Android
ro.product.instruction=PDF
ro.product.gpspkname=null
ro.product.screenclock=false
ro.product.videogesture=false
ro.product.weatherhost=yahoo
ro.product.customer.sub=HCT5
ro.product.defaultlauncher=null
ro.product.drvingsafe=null
persist.display.landspace=true
ro.product.disCarNotifi=false
rf.product.recentshow=false
ro.product.bluetoothname=
ro.product.bluetoothpwd=
ro.product.btthreewaycall=false
rw.zlink.foreground.donotreqaf=1
ro.product.isshowbtvoiceico=true
ro.product.gpsmix=null
ro.product.gpstime=1
ro.product.gpsswitch=null
ro.product.gpsphone=null
ro.product.screentimeout=null
ro.product.time_24=null
ro.product.autotime=1
ro.product.powerdelay=null
ro.product.keycustomeq9=null
ro.product.dateformat=null
ro.product.barbacklight=null
ro.product.drivingoverspeed=false
persist.product.shownavbar=false
ro.product.volchannelgain=false
ro.product.dspversion=null
ro.product.brightnessmode=0
ro.product.sdcardswap=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=cortex-a53
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a7
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.expect.recovery_id=0xb4756f65ded248ecd6e994ca2af0a8f45a324652000000000000000000000000

I have installed PX5 and it works.Firmware date 26-03-2019

zeyret said:
I have installed PX5 and it works.Firmware date 26-03-2019
Click to expand...
Click to collapse
screenshots?
time bug still present? split screen working?

zeyret said:
I have installed PX5 and it works.Firmware date 26-03-2019
Click to expand...
Click to collapse
Hi Arkadash / Mate,
first thank you for your reply, can you test the following for "us" pls? the time receiving from the gps only, so you turn off the time received from (wifi) network and put it on gps and then after an hour or so go back to your car and see if the time runs well and does not remain the same when you left it?
Second, what do you think of the UI ((skin)) of this A9 is it nice? can you place a picture of it? if not, can you refer via the Ali -express- site to a similar A9 headunit with the same UI?
I don't have the time for it at the moment and I'm waiting for a newer version (have/use now the HA one) like that one from the/our Danish mate.. if he's got lucky with his headunit seller (Not like my seller with his 0,0 fw+mcu support!) and would give him the newest A9 fw + mcu version? that would be great for "us the mx's owners" .. that's why.
Thanks in advance mate.

Android 9.0 test 26-03-2019
1-GPS time is ok
2-Screen pane does not work.
3-1080p .ts videos are not smooth, video quality is not good.
Edit:I want to make a correction.
When you reset to the unit, the gps clock becomes corrupted.

zeyret said:
Android 9.0 test 26-03-2019
1-GPS time is ok
2-Screen pane does not work.
3-1080p .ts videos are not smooth, video quality is not good.
Click to expand...
Click to collapse
Hi Arkadaş / Mate,
thanks a lot for your reply, are you very sure about the time from gps Only but not from the wifi / network kardeş? and that it works 100% ok? I have no problem with that 1080p, I use mx player here with no problems maybe you need to used too?, I don't watch movies except for my boys and sometimes so not always. the UI looks very nice too .. I think I will try it out, it will certainly take 3 hours to do (install) everything again and incl. the entire iGO navi maps etc.
Zaman ayırdığınız için çok teşekkür ederim ve kardeşimi cevap :good:
Edit:
I'm not Turk so I did not read it good as well but it says: navigasyon otomatik zaman = navigation (gps) automatic time .. means time works from the gps receiving!
Goodluck mates

The best Husky wolf of the 3 A9 which I "already test" them..
Hi Mates,
I couldn't even wait until after noon, I already installed it, the gps time works immediately, but here he indicated the winter time after a few minutes, so an hour later, I have it now set it to gtm times and not to region , so select the time yourself if you get what I got.. I do the rest of installations after noon, I am now a bit too tired for that.
Goodluck.

Do you know if this release can be rooted with a common tool or method?
I would need xposed working on it.
Thanks a lot,
Christan

Time Bug is still exists..
Hi Mates,
Unfortunately, all the problems in the world came from bad communications, as I always tell (said to) my buddies, I was perhaps too soon cheered by my joy that the time bug was finally fixed, but unfortunately it is not, so time bug is still exists, for the rest one of the better A9 so far because of his nice UI.
Time Bug, the time was not updated when I turn off my car and after an hour or 2 I turn it on again, the time does not synchronize well with the local time as it should be while its making contact with the gps immediately.. so all in all, the time bug is still present on this fw version too.. regrettable!
Resume: the receiving gps time it doesn't refresh after I turn the car off!

gforums said:
Do you know if this release can be rooted with a common tool or method?
I would need xposed working on it.
Thanks a lot,
Christan
Click to expand...
Click to collapse
Hi mate,
I'm not 100% sure about that but.. take a good look at this one:
https://forum.xda-developers.com/an...5-oreo-rom-t3736950/post75741195#post75741195
Ps: I had once read about the so called ADB root method => https://www.youtube.com/watch?v=4v9s89fYIZ4 .. maybe?
Success mate.

Android pie speaker call microphone issues

Update hotfix!
So, if you're having the same issue as described below, the solution is apparently to contact HTC support.
Explain to them you have this issue, you could also mention this thread and they should ask you for your SN or IMEI.
A few days later you can check for an update and you should be able to find one. It's about 70MB and only includes the hotfix, nothing else.
This is the direct link to the OTA (European?) if you wish to install it manually:
http://fotadl.htc.com/OTA_IMAGINE_D...2.55.401.1_release_549055s9q6pz2h8oow5ojn.zip
The problem
Ever since the android 9/pie update I've been having issues with my microphone during speaker calls and video calls.
Normally I call my girlfriend every day using a video call in WhatsApp or wechat. But after the upgrade she said: what happened? I can barely hear you.
As it seems, when the phone is in speaker mode during a call, the volume of the microphone from my phone is too low. Unless I shout, the other party can't hear me.
The weird thing is that the microphone seems to work fine in other cases like when you hold the phone to your ear for a phone call, video recording or even voice clip recording. Only speaker mode has issues somehow.
What I've tried
I've factory reset my phone already, without any improvement whatsoever. It seems to me that this is a bug in the update.
Use of this thread
I'd like this thread to be a place for people to find each other with the same problem, and possibly fix it. Or have at least a collection of people to tell HTC: fix this.
List of users with the same problem
Other users, reported so far:
@AtAM1
@harvey1483
@Dehypnotizer
Response HTC and test
I've contacted the HTC live chat support and described the issue. They recommended me to test the following:
A) Dial *#*#3424#*#* and run the diagnostic tool for the audio test and check the Microphone performance.
B) Sometimes the downloaded applications conflicts with the phone's OS making it not to perform in a normal way, so please try to use the phone in the safe mode by following the steps below:
1.Press and hold “power key “till you see the options of Power off and restart option
2. Press and hold on the screen on the power off option till you can reboot to safe mode
4. “Safe Mode “text will appear on the lower left of screen.
C) Check for updates from Menu> Settings> About> Software Updates (preferably using Wi-Fi)
D) If you followed these steps and the issue is resolved, it means that you have downloaded 3rd party application downloaded from the internet which conflicts with you device OS. Please remove it from:
Menu>settings>applications >downloaded >click on the applications and un-install them.
F) If you followed these steps still the same issue, please back up your phone information as resetting your phone will erase your phone data completely and follow the step below:
Menu>settings>Backup & Reset>Reset phone.
Click to expand...
Click to collapse
I'll try this tonight myself and report my findings.
If these test come back negative, the HTC expert told me then he wants my phone for repair. It's unlikely I'll do that however, since I believe this is a software issue and not hardware.
Final response HTC
The tests HTC told me to do passed successfully. After sending a link to this thread with @AtAM1 findings, they made a flag for it for the developers.
The HTC expert told me she hoped it would be solved soon.
Now we wait?

Thanks for making a dedicated thread to cover this bug.
I tried all sorts of hardware and software tests including the ones recommended by HTC in your post but nothing helped.
The only thing I haven't tried is resetting the phone which I am dredding as many services are tied to app activations.. If I had to though, I'll probably unlock the phone and switch to LeeDroid's rom (root) for more troubleshooting and customization options.
However, I did google this issue and it seems it's a software bug, specifically with the OS and mainly with Pie, and nothing to do with the hardware.

Quick update: The bug is most likely with incorrect values set/used for the properties persist.audio.fluence* and ro.qc.sdk.audio.fluencetype and more generally persist.audio* / ro.qc.sdk.audio*. Only way to rectify it without having to wait for a fix from HTC is to root the phone and mod build.prop
Can anyone running factory RUU under Oreo share with us their getprop output via adb shell?
Thank you
Edit: Forgot to mention - The issue still persists after resetting the phone or reflashing Oreo RUU then upgrading to Pie

Update 2: I managed to get the getprop values from Oreo 1.53 - key differences are HTC seems to have either dropped or forgotten to add and/or port over vendor specific values to Pie, specifically:
Missing Properties / Values in Pie [Audio related]
Code:
-[persist.vendor.audio.fluence.speaker]: [true]
-[persist.vendor.audio.fluence.voicecall]: [true]
-[persist.vendor.audio.fluence.voicerec]: [false]
-[persist.vendor.audio.headset.anc.type]: [feedback]
-[persist.vendor.audio.ras.enabled]: [false]
-[vendor.audio.adm.buffering.ms]: [2]
-[vendor.audio.dolby.ds2.enabled]: [false]
-[vendor.audio.dolby.ds2.hardbypass]: [false]
-[vendor.audio.enable.dp.for.voice]: [false]
-[vendor.audio.flac.sw.decoder.24bit]: [true]
-[vendor.audio.hw.aac.encoder]: [true]
-[vendor.audio.noisy.broadcast.delay]: [600]
-[vendor.audio.offload.buffer.size.kb]: [1024]
-[vendor.audio.offload.multiaac.enable]: [true]
-[vendor.audio.offload.multiple.enabled]: [true]
-[vendor.audio.offload.passthrough]: [false]
-[vendor.audio.offload.pstimeout.secs]: [3]
-[vendor.audio.offload.track.enable]: [true]
-[vendor.audio.parser.ip.buffer.size]: [262144]
-[vendor.audio.safx.pbe.enabled]: [true]
-[vendor.audio.tunnel.encode]: [false]
-[vendor.audio.use.sw.alac.decoder]: [true]
-[vendor.audio.use.sw.ape.decoder]: [true]
-[vendor.voice.path.for.pcm.voip]: [true]
Unchanged Properties / Values in Pie [Audio related]
Code:
[persist.audio.fluence.speaker]: [true]
[persist.audio.fluence.voicecall]: [true]
[persist.audio.fluence.voicerec]: [false]
[vendor.audio_hal.in_period_size]: [144]
[vendor.audio_hal.period_multiplier]: [3]
[vendor.audio_hal.period_size]: [192]
New Properties / Values in Pie [Audio related]
Code:
+[media.stagefright.audio.deep]: [true]
Another major change to how the microphone is managed under pie (audio_platform_info.xml)-
Code:
@@ -239,6 +239,7 @@
<usecase name="USECASE_AUDIO_RECORD_LOW_LATENCY" type="in" id="17" />
<usecase name="USECASE_AUDIO_PLAYBACK_ULL" type="out" id="17" />
<usecase name="USECASE_AUDIO_PLAYBACK_EXT_DISP_SILENCE" type="out" id="27" />
+ <usecase name="USECASE_AUDIO_A2DP_ABR_FEEDBACK" type="in" id="40" />
</pcm_ids>
<config_params>
<param key="spkr_1_tz_name" value="wsatz.13"/>
@@ -349,6 +350,388 @@
<device name="SND_DEVICE_IN_HEADSET_AS20_AMBIENT" interface="SLIMBUS_0_TX"/>
<!-- HTC BACKEND END -->
</backend_names>
+ <!-- below values are hardware info from audio HW team: [email protected] -->
+ <microphone_characteristics>
+ <microphone valid_mask="31" device_id="builtin_mic_1" type="AUDIO_DEVICE_IN_BUILTIN_MIC" address="bottom" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="0" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00 20000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 -1.0 0.0" geometric_location="0.0510 0.0 0.0022" />
+ <microphone valid_mask="31" device_id="builtin_mic_2" type="AUDIO_DEVICE_IN_BACK_MIC" address="back" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="1" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00 20000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 0.0 1.0" geometric_location="0.037 0.0195 0.0024" />
+ <microphone valid_mask="31" device_id="builtin_mic_3" type="AUDIO_DEVICE_IN_BUILTIN_MIC" address="front" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="2" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 0.0 -1.0" geometric_location="0.0235 0.1445 0.0022" />
+ <microphone valid_mask="31" device_id="builtin_mic_4" type="AUDIO_DEVICE_IN_BUILTIN_MIC" address="top" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="3" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 1.0 0.0" geometric_location="0.0546 0.1456 0.00415" />
+ </microphone_characteristics>
.... continued see attached file.
Could you respond to HTC and share the above with them so it is escalated to their dev team for an urgent fix release?
Thanks

Wow, amazing stuff @AtAM1 !
I've just relayed the information to HTC, I talked to Arya and she promised she raised a flag at the development team.
Not sure how soon to expect a fix for this with the current state of HTC, but I hope we'll get it soon.

Unluckily same issue after pie update! And now? I know Htc and probably we have to wait Android Q if u12+ will receive it.

harvey1483 said:
Unluckily same issue after pie update! And now? I know Htc and probably we have to wait Android Q if u12+ will receive it.
Click to expand...
Click to collapse
The same bug here. People can't hear what I'm saying while in Speaker Mode.
Have you noticed another sound-related bug? Pressing Volume Up/Down changes volume of the media, not the ring tone.
This is almost as much annoying as messed up microphone's settings.
I just hope HTC is alive enough to release yet another fix OTA.

Dehypnotizer said:
Have you noticed another sound-related bug? Pressing Volume Up/Down changes volume of the media, not the ring tone.
Click to expand...
Click to collapse
This is NOT a bug. This is how Pie works in other devices, not just HTC. Definitely more logical as people don't always change ringtone volume all the time and it can even ruin your "default" ringtone volume level by accidentally increasing/decreasing it.

This post should've been deleted, sorry for that.

ijuanp03 said:
This is NOT a bug. This is how Pie works in other devices, not just HTC. Definitely more logical as people don't always change ringtone volume all the time and it can even ruin your "default" ringtone volume level by accidentally increasing/decreasing it.
Click to expand...
Click to collapse
You are WRONG. I have two devices running on Pie and that's how it works in Huawei and HTC 11 Lite:
https://drive.google.com/file/d/10Gw7XBuKjIM3Y3wR365jlGJYpsgnWgJV/view?usp=drivesdk
Besides, I disagree with you. A phone is a device primarily designed to make telephone calls. That's why, for years, volume buttons have been changing ring tone's volume, by default. If the phone was playing music - that's the other story.
Now, by default, I change volume of internal speaker (sic!). That's just insane - I have to go to Settings to change the volume of the ring tone.
Don't get me wrong: I love HTC, that's why I have U12+ even though I knew the HTC was dying at the time I bought the phone. But bug is a bug.

ive just updated my cellphone and im having the same problem and sometimes i can't unlock the phone using the double touch or swiping up ?, any news about when they gonna fix this? and can someone tell how to not see when ur touching the screen those little white dots, how to deactivate that thing?

No problems here on USA version
---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------
larrymtz said:
ive just updated my cellphone and im having the same problem and sometimes i can't unlock the phone using the double touch or swiping up ?, any news about when they gonna fix this? and can someone tell how to not see when ur touching the screen those little white dots, how to deactivate that thing
Click to expand...
Click to collapse
Go to settings>system>developer options>turn off show taps

Usa version unlock
teh_pwnrer said:
No problems here on USA version
---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------
Go to settings>system>developer options>turn off show taps
Click to expand...
Click to collapse
i have that version and i found the reason why it was showing the taps, the glove mode was enabled, gedtures still not working properly...

Yet another bug
After Digital Wellbeing app downloaded itself, during routine check of updates in Play Store, the only way to start it is to search for it in Settings. There's no entry in Settings for it. Fortunately, application has an option to place its icon in the app list.
HTC 11 Lite, on the other hand, has it done correctly.
Hopefully, someone from HTC reads that and they will ultimately release an update... Such a sad story. I loved HTC 10 and basically all their flagships and such a great company dies

I have here the same problem, this is all afther the update to Android 9.
Good that there is a topic about it, hopefull there will be more people with the same problem.
In addition to sound problems, I almost always have my phone on do not disturb. Despite this function, sound is just ringing and sound notifications come through with the apps.
Have already looked at the settings, these are only alarms and media on.
Last week I had the duration of not disturbing turned on at number of hours, the time format that he indicates was wrong, by the way still miss the option between switching off when your alarm goes off. this was still standard in Android 8.
Finally, I think it is a shame that they have moved the clock, had first used an appe to switch it off, because on my home screen I have the clock in large, but because it did not work, I left it. I have to say that I am used there for the rest. Only would have preferred that room for the reports.

I have it to

Maybe a stupid question, but why can't we manually edit the audio-related props to insert the missing lines?

MNoisy said:
Maybe a stupid question, but why can't we manually edit the audio-related props to insert the missing lines?
Click to expand...
Click to collapse
You'd need root. If you have root you're welcome to try and report back the improvements

WPtE said:
You'd need root. If you have root you're welcome to try and report back the improvements
Click to expand...
Click to collapse
I would be happy to. Any recommendations on tools to perform the edits along with backing them up first?

MNoisy said:
I would be happy to. Any recommendations on tools to perform the edits along with backing them up first?
Click to expand...
Click to collapse
Don't do that. You open yourself for possible attacks. Rooting phone for fun is cool but it's best to use a test Google account and a phone you do not use for normal, regular daily usage.
Others may and probably will disagree but if we're talking about your main device I'd keep it unrooted.

Question Original Android FM App Crashed - FYT Android Car Unit (CPU: UIS8141E)

Hello everyone
I have an android car unit that I bought from AliExpress (here's the link). It works perfectly in most cases. The only drawback is that when I am using the navigator (Google Maps or any other) along with the original FM radio app, the original FM radio app (in the background) crashes and closes constantly (every 10 seconds after reopening it). This is very annoying and I can't seem to solve it.
I spoke to the seller and he gave me some "update files" for my Android car unit. But honestly, I'm not very confident about using them as the instructions the seller gave me don't match the interface of my device. The salesman told me that my device is a TS18, but I don't know exactly what he means by that.
I have used the HWGetinfo.apk application to check if my device is FYT and indeed it is. To solve the FM radio problem, I tried installing the NavRadio+.apk application which was supposed to be compatible with my device, but when I installed it, it told me that it is not compatible.
I want to solve this problem, but I don't know what else to do and I'm afraid to update and leave my radio unusable....
I attach images of the characteristics of my device. Also, I attach here the link to the update files that the seller sent me.
My questions are:
1. Can anyone think of a solution to stop the native FM app from crashing?
2. Can I update my Android system somehow?
I would be very grateful if someone could help me. Thanks in advance for your time.
Regards.

Your unit is not a uis8581a, but the cheap sc7731. It is indeed a FYT.
I am not going to download a 1.5GB file. Please share a listing of the contents of the rar, and of the config.txt inside it if there is one.
Edit:
The properties.txt inside your HWGetinfo.zip also says it is a sc7731: [ro.product.hardware]: [sc7731e_1h10_v1.1.0] and [ro.product.board]: [sp7731e_1h10]
The sc7731 can be considered a RaspberryPi 4 (ARM A7).
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]

I'd suggest replacing with a FYT uis7862

surfer63 said:
Your unit is not a uis8581a, but the cheap sc7731. It is indeed a FYT.
I am not going to download a 1.5GB file. Please share a listing of the contents of the rar, and of the config.txt inside it if there is one.
Edit:
The properties.txt inside your HWGetinfo.zip also says it is a sc7731: [ro.product.hardware]: [sc7731e_1h10_v1.1.0] and [ro.product.board]: [sp7731e_1h10]
The sc7731 can be considered a RaspberryPi 4 (ARM A7).
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
Click to expand...
Click to collapse
Hello.
First of all thank you very much for your answer, now I have much more information about my device.
In the image "Screenshot_1.png" you can see a list of the content of the .rar file. Also, I attach the text file with additional information that comes inside the .rar ("TS18更新记录.txt").
What should I do now?

marchnz said:
I'd suggest replacing with a FYT uis7862
Click to expand...
Click to collapse
Hello, thank you for your reply.
What do you mean by this, could you pass me a link with instructions?
Thanks in advance.

juanka1995 said:
Hello.
First of all thank you very much for your answer, now I have much more information about my device.
In the image "Screenshot_1.png" you can see a list of the content of the .rar file. Also, I attach the text file with additional information that comes inside the .rar ("TS18更新记录.txt").
What should I do now?
Click to expand...
Click to collapse
Maybe you expect an answer from me, so I give it, but it might not be of much use.
It is a FYT but a topways firmware structure. I do not know much about that.