yashsingh1/xdaforums huggingface dataset:
[Touch GSM General] xxxxchrisxxxx:
I seem to have a problem with my HTC Touch (ELF)

I recently upgraded to another phone (diamond) and was giving my Touch to my brother.

After leaving it unused for a couple of weeks, I got round to flashing a new rom onto the phone (Blue Elves 5)

I gave the phone to my brother (without testing anything I didn't have time).

He then told me that there is a problem with the sound - nothing is heard at all via the earpiece during calls, however it works fine from the external loudspeaker.

I guessed that it may be that the rom didn't install properly so I talked him through a hard reset - no joy. Still no sound.

I have today installed another ROM - PDAVIET - latest version, and flashed the radio to the latest version. The problem is still there.

My brother insists that he has not dropped / knocked the phone at all, and I don't doubt him. I am however at a complete loss as to why all of a sudden there is no sound from the earpiece. I have used the phone for a year, with various different ROMs and never had any loss of or distorted sound from the earpiece.

Has anyone else experienced this? Does anyone have any ideas as to what the problem may be? How can I fix this?

Any help very much appreciated!

(Also - yes - the volume is turned up)
[Touch GSM General] thedaddyy:
I think you better read this

http://xdaforums.com/showthread.php?p=2273492#post2273492

let me no how you get on
[Touch GSM General] xxxxchrisxxxx:
thanks but this doesn't help as my warranty and contract are ended. any other ideas welcome.

thanks.
[Touch GSM General] xxxxchrisxxxx:
Could this be a problem with the registry? would flashing ROMs fix the registry? Is there a registry setting for disabling the speaker?
[Touch GSM General] scots jim:
I have the exact same problem. Let me know if you find a solution please !
[Touch GSM General] thedaddyy:
I think you guys need this:

http://cgi.ebay.co.uk/SPEAKER-EARPI...39:1|66:2|65:12|240:1318&_trksid=p3286.c0.m14

good luck!!
[Touch GSM General] bfarkin:
I have the same problem, but I did prefer to use the speaker anyway. So now I use this:

http://xdaforums.com/showthread.php?t=369399

Works fine on the Elf!

Bernard
[Touch GSM General] xxxxchrisxxxx:
Thank you 'thedaddy'.

You were right. I disassembled the phone and found that one of the copper connections of the earpiece speaker had broken. Bought a replacement from eBay which fixed the problem.

Thank you.

Chris.
[Touch GSM General] thedaddyy:
My pleasure mate glad you got ur baby working again,

and its 'thedaddyy'.......
[Touch GSM General] vette95:
I had the exact same problem

I had to buy an earpeace speaker for my touch on ebay for about US$15.

Look it up on ebay, and they are really easy to replace.

Look for the hong kong guys that ship it with the tools to get the job done.

Good Luck.
[Xiaomi Poco X3 NFC Questions & Answers] SebixWolf:
Hi all!

Would you recommend a specific custom kernel to use with this Custom ROM?

currently I am using stock kernel and I am happy with the results,but if I can get more juice that will be great!

I look for any recommendations or reviews about the custom kernels results.

Thanks!
[Xiaomi Poco X3 NFC Questions & Answers] Kenora_I:
https://xdaforums.com/t/kernel-surya-optimus-drunk-kernel-v11-29-19-07.4198627/

You can try this, haven't used it personally but if you are happy with the stock kernel then it's fine to stick with it.

The custom kernels have some useful optimisations, but it's ultimately your choice whether or not you want it.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
The gnss hwbinder patch have been incorporated into the Aug 25 17.1 builds.

Please take 10 minutes to read all of post #1 and #2. DO NOT USE this thread to report any other problems, it's only for troubleshooting random reboots or reboots into TWRP for S2 exynos5433 tablet users. If this is unreasonable, then stop reading. Thank you.

If you cannot provide the logs below, please do not participate in this thread. Thank you.

I will take a look at all logs uploaded. The more the better to help find root cause or causes.

At this point, I have no solution to fix random reboots, but gathering data that might help narrow down which app or process is causing this.

Instructions

1. If you are experiencing random reboot or reboot into TWRP, you MUST supply tombstone logs. It's super easy and simple to do. Connect your device to PC using micro usb cable.

Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.

adb root
adb shell
cd data/tombstones
ls -al
# if you see files tombstone_00, tombstone_01, etc then
exit
mkdir t
cd t
adb pull data/tombstones/

Zip all the files and upload here. Alternatively, you can send me the zipped logs via xda PM.

2. The better log would be adb logcat of the problem (random reboot, stuck at boot animation due to random restart) that just happened or happening.

adb logcat > crash.txt
# wait 30 seconds then hit ctrl-c to stop capture

Please zip the .txt file before uploading. For some reason, I cannot see .txt files here.

FAQ

Q1. When will this random reboot be solved?

A1. Set your expectations that it will never be solved. At this point, I'm only gathering data to try and help. There may never be a fix if it's due to a proprietary Samsung blob that can never be updated. DO NOT ask when or if this can be fixed. It is not productive and I will completely ignore the question. Thank you.

Q2. Will you provide updates?

A2. I will only provide updates if I think we have found a solution. Otherwise, assume I'm not working on this problem because like you, I have other responsibilities and interests in life.

Q3. What will you do with the logs?

A3. I will look at every uploaded log and try to find a common pattern among them. If I find something that I think it's worth reporting, then I will post it here. If I need more information, I will revise the instructions and ask for more.

Q4. Why are you doing this?

A4. Let me be clear. I'm not experiencing any random reboots myself, I'm just trying to help if I can. The more logs you can provide, the more likely we can narrow down the problem. No logs from the commuity means the random reboot problems will never be fixed.

Let me be clear again, DO NOT ask when or if this can be fixed. Thank you.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Yogi555:
Hi @retiredtab,

thanks for your offer to analyze the crash-logs!

I'm using a T810 Tab (gts210wifi) and are experiencing random reboots since updating to lineage-17.1 (ripee).

The reboots itself are of different types:

1) Stuck at bootanimation - only exit by three-button-reset.

2) Reboot to unlock-screen, but after unlock-code endless other unlock-screens come up - only exit by three-button-reset.

3) Reboot to unlock-screen, but after unlock-code the screen is empty and after some time (few minutes) it resets and ends in the same sequence - only exit by three-button-reset.

4) Reboot to unlock-screen, everything ok after unlocking.

For most of the reboots it was my observation, that there was an event, which did wakeup the tablet from deeper sleep (plugin to charger, switching on the screen, alarm, ...).

That caused me to write a small Tasker-app profile, which is pinging my dns-server all 2mins (to prevent a deeper sleep). With that profile active I did not experience any reboot for at least 2 months. Before that I had about one reboot per day.

To support your analysis, I disabled that Tasker-profile and the reboots are back.

During the last 24hours I had two reboots of type 4, and I was capturing the logcat and tombstones afterwards.

Looking into the captured data I got the impression that it might contain sensitive data (found my server-names, calender-events and so on) so I'm unsure if it can contain even more sensitive data like login-information or wifi-passwords.

So I'm hesitating to upload them to this public forum.

Would you agree to receive the zipped logs by PM instead?
[Galaxy Tab S2 Q&A, Help & Troubleshooting] lpedia:
Hi, @Yogi555.

Your reboot types 2 and 3 are interesting - I haven't seen them happen with my device. I only get types 1 and (occasionally) 4.

And type 5: reboot to TWRP. On my device this has happened more often than type 4, but both are much less common than type 1.

It does sound like the device waking from deep sleep could be triggering these events. Certainly, my device most often goes into type 1 when it's been left alone for a while, such as overnight (so my workaround has been to turn it off at night).

But I've also seen it drop into type 1 while I was actively using it, so waking up mustn't be the only trigger.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Yogi555:
Hi, @Ipedia,

Maybe types 2 and 3 are somehow related to the individual homescreen app - I'm using Nova Launcher. Only guessing here.

Regarding type 5: Yes I did see it as well sometimes - but I'm not sure if it is a type of it's own. If I remember correctly type 1 - 3 are rebooting itself after some time of stalling. And - not sure here - after some unsucessful reboots in sequence we end up in TWRP. (In the embedded business where I'm working, it is the desired behaviour to jump to a flashing-bootloader after a number of resets within a certain time).

I've seen the reboots while busy using it as well some time ago, rare, but it happened - but when I activated my described tasker-profile, they were gone as well. I've no explanation for that.

At the moment I'm only facing type 4 resets. I did many changes, since I saw type 1 - 3 (update to latest 17.1 linageos, latest Magisk, exchange of the wifi-blobs) so not sure if any of this solved these reboots, or if they are yet to popup ...
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
@Yogi555 , you can send zipped logs using PM. Thank you.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Max_C:
can you help me to get logs? I receive this error message

c:\adb>adb root
c:\adb>adb shell
gts210ltexx:/ $ cd data/tombstones
gts210ltexx:/data/tombstones $ ls -al
ls: .: Permission denied
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Yogi555:
Maybe have a look how my adb root problems were solved in this thread: https://xdaforums.com/t/troubleshoo...-version-of-andriod-10.4308193/#post-85353551

Worth a try, but maybe your issue is different
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Max_C:
i see, my device not rooted. I need install Magisk first, then enable rooted debugging. I have no rooted debugging in developer options
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Yogi555:
Magisk is hiding the option - without magisk you should see it - even with an unrooted device
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Max_C:
oh. i see. I have no "rooted debugging" option in my developer settings in Havoc OS

another problem is i have old Android SDK on my PC. I installed latest one, and got this

c:\adb>adb root
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Yogi555:
I had exactly the same issue with magisk being the one hiding the setting. Are you sure that you are not having magisk installed? Don't know Havoc ...
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
Boot into TWRP then. You can get the same data/tombstones from TWRP using the same commands.

If you have the SM-T710, you will need my TWRP in order for adb to work. The official ones posted on twrp.me don't work with adb or mtp.

retiredtab - Browse /SM-T710/TWRP at SourceForge.net

sourceforge.net

Mine works, but it takes 10 seconds before mtp and adb work after the TWRP home screen is shown.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Max_C:
thanks! got it, please check attached
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
I have downloaded them, but will examine tomorrow. It's been a long day and it's 12:40 AM. Time for sleep.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
After 17 days of gathering data and troubleshooting, we think we may have solved the random reboots. Huge thanks to @lpedia, @CuckooPenguin and @Yogi555 for testing the various gnss patches until we finally figured out the hwbinder solution.

Details at

https://github.com/universal5433/android_device_samsung_gts2-common/pull/4

If you are one of those people who experienced random reboots, it's not too late to submit your data/tombstones or check them yourself for the error message that I listed above. In particular, you are looking for

#0 pc 00056baa /system/lib/android.hardware.gnss@1.0.so (android::hardware::gnss::V1_0::BsAGnssRilCallback::requestSetIdCb(unsigned int)+450) (BuildId: 30ee8b14270ae2b3ae675a7f9b4de136)
#1 pc 0000e8dd /system/vendor/lib/hw/android.hardware.gnss@1.0-impl.universal5433.so (android::hardware::gnss::V1_0::implementation::AGnssRil::requestSetId(unsigned int)+32) (BuildId: d0033c7cb8d0d1a2c99f977719d0d967)
#2 pc 0000fb05 /system/vendor/lib/hw/gps.default.so (broadcom::GpsiClient::marshal_agps_ril_request_setid(broadcom::IpcIncomingMessage&)+160) (BuildId: fe39be024fc2f98450c8d2fc07cda956)

Once the git pull requested is approved, this patch should make it into the next August security patch build for all flavours of the tab S2 including all the variant OS.

Finally, a huge thanks to @ananjaser1211 for tips, suggestions, code and acting as a sounding board for ideas.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Max_C:
sorry, I'm not sure i understand how it works... Should I wait when my HavocOS ROM will be updated in this thread? Or there is another way how to apply the patch
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
We tried modifying the manifest.xml directly, but the results were inconsistent. On my t710 the instructions below worked, but 2 people with the t810 it resulted in a system not booting properly. These 2 had to reflash the rom to get a working system back. On the t810, the below changed had to be compiled into the code.

If you want to try, backup your data first and be ready to reflash the old rom in case it fails. If it fails, you will have to wait for a new Havoc build or build it yourself.

# Turn off gps in OS before booting into TWRP
# boot into TWRP

adb root
# touch mount, system
adb pull /system/vendor/etc/vintf/manifest.xml
# use a text editor and look for this section of code

<hal format="hidl">
<name>android.hardware.gnss</name>
<transport arch="32">passthrough</transport>
<version>1.0</version>
<interface>
<name>IGnss</name>
<instance>default</instance>
</interface>
<fqname>@1.0::IGnss/default</fqname>
</hal>

# change passthrough to hwbinder like so

<transport arch="32">passthrough</transport>

to

<transport>hwbinder</transport>

# save text file
# now push file
adb push manifest.xml /system/vendor/etc/vintf/manifest.xml

# verify that line manifest.xml has changed in the gnss section
adb shell cat /system/vendor/etc/vintf/manifest.xml | more

# Important. Wipe dalvik/art cache and cache

# reboot into OS, enable GPS and make sure GPS works
# Note you may have to go into your setting, apps and wipe cache data as well if GPS doesn't work.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Max_C:
Thanks, on my SM-T815 all working fine, I followed your instructions, pushed revised manifest.xml, GPS is working fine. I will test if it helped to solve the problem and leave message here with result in several days.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
Well, I'm surprised it worked on the t815 when it failed on the t810. That's why I stated it was inconsistent.

So if you were getting daily random reboots due to gnss crashing, then the gnss hwbinder fixes that. We have now had 2 testers go > 150 hours uptime with this patch. Before, they were getting daily reboots/crashes due to gnss (as shown in adb logcat and tombstones).

At first, we thought going 72 hours without a reboot would qualify as a successful fix, but we decided to extend it > 100 hours.

Again, the data/tombstones and adb logcats will show you which process/app is crashing. That's why it's important to view and share them otherwise we would have never figured this out.

Please report back if/when your device reaches 100 hours of uptime.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] manhart:
I run my SM-T810 with lineage-17.1-20210718-UNOFFICIAL-gts210wifi.zip including the patch for the WiFi.

I detected one case (1) with the endless loop in the boot logo. I had several crashes with waking up of the device from standby. The last one was today at approx. 0730 local time.

I can't say what triggers the crash. It was never connected with the charging cable during such a crash. I extracted the tombstone files and attach them here.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
Thanks for providing the tombstones.

Tombstones 2, 3, 4 and 5 all point to gnss crashing. #5 shows timestamp "Timestamp: 2021-08-07 07:08:18+0200"

The gnss hwbinder fix submitted to github will likely fix this problem.

Two people already tried manually applying the fix to the T810, but were unsuccessful, so you will have to wait until it's compiled into the next August security patch.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] manhart:
My Tab S2 (TM810) was on standby last night. I could not bring the device back to normal operation this morning. Screen stayed black. I had to use the 3 keys for the download-mode and exit there. Now the devices started normal. Battery level was on 35%.

I assume, that the device made a restart this night and could not boot LOS.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
Tombstone file called .temporary3 output below for Aug 9 shows it's the same gnss crash message. .temporary1, 2 and 3 all shows the same gnss crash all around the same time at 1:05 or 1:22AM.

To mitigate until ripee's August build is out, you can try one of the following.

1. turn off your tablet when you go to sleep at night.

2. turn off gps functionality and hope it doesn't crash with gps turned off (disabled).

3. build sm-t810 yourself -> it's not has hard as it seems

Timestamp: 2021-08-09 01:05:52+0200
pid: 17513, tid: 17824, name: Thread-10 >>> system_server <<<
uid: 1000
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x69007f
r0 00000009 r1 00000011 r2 00430000 r3 ac93b084
r4 6923db6c r5 81429240 r6 0069006f r7 aeb2f260
r8 693bd44b r9 693bd216 r10 6923daf8 r11 693c0010
ip 00000000 sp 6923dad0 lr 824994cf pc 693d6baa

backtrace:
#00 pc 00056baa /system/lib/android.hardware.gnss@1.0.so (android::hardware::gnss::V1_0::BsAGnssRilCallback::requestSetIdCb(unsigned int)+450) (BuildId: 30ee8b14270ae2b3ae675a7f9b4de136)
#01 pc 0000e8dd /system/vendor/lib/hw/android.hardware.gnss@1.0-impl.universal5433.so android::hardware::gnss::V1_0::implementation::AGnssRil::requestSetId(unsigned int)+32) (BuildId: d0033c7cb8d0d1a2c99f977719d0d967)
#02 pc 0000fb05 /system/vendor/lib/hw/gps.default.so (broadcom::GpsiClient::marshal_agps_ril_request_setid(broadcom::IpcIncomingMessage&)+160) (BuildId: fe39be024fc2f98450c8d2fc07cda956)
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
I didn't mention it earlier, but the gnss hw binder patch has been accepted and approved so it will be included in the next build. See

https://github.com/universal5433/an...mmit/9ef0bd12999823662afc0cd03645f31c37e258a5
[Galaxy Tab S2 Q&A, Help & Troubleshooting] lpedia:
Did holding Power+Volume Down not do anything? That can usually force either shutdown or restart system (shutdown if it's attached to a charger at the time, restart otherwise).

If this happens again, it'd be useful to know whether your blank-screen issue was due to something we haven't come across before. Before you force-restart the device, first check whether adb can see the device.

If it can, you can grab a logcat. Also, if you're able to get root on the device via adb when the screen's blank, you can run the htop command via adb shell to see what's using the most resources. I've seen a totally blank screen on my T710 a couple of times recently, and it was because the fingerprint manager was going crazy. This (for some reason) prevented the screen from displaying anything. adb could still access the device, though, so with htop I could find the fp manager process number. Killing that process brought the screen back ( the process restarted automatically and was then behaving itself).
[Galaxy Tab S2 Q&A, Help & Troubleshooting] manhart:
I had this black screen the first time with LOS 17.1. I will try the checks next time.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Max_C:
112 hours uptime, 88% deep sleep. Thanks a lot for your help!
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
The gnss hwbinder patch have been incorporated into the Aug 25 17.1 builds.
[WebOS Software and Hacking General] xda_user_dev:
Some people have been successfully rooted their systems. Congratulations!

Is it good idea to collect some apps for backup or sharing? They can be easily obtained as long as /usr/palm/applications is mounted.
[iQOO 7] flubber999:
Is there any option to disable data usage for specific apps in IQOO7 - funtouchos 11.1
[iQOO 7] Kenora_I:
Head over to your phone Settings. You can do this by swiping down from the top of your phone's screen. Then tap the settings icon at the top-right corner.

Go to Network & Internet > Data usage. You'll see the amount of data you've used at the top of that menu.

Select App data usage to see how much data each app has used recently.

Check through the list and tap the app that uses the most data. For instance, you may be surprised how much data YouTube alone uses.

Toggle off Background data to turn off cellular data for specific apps.

Turn off Unrestricted data as well if it's not off already. That keeps the app in check when data saver is active.

Not disable entirely but restrict to some extent.
[iQOO 7] flubber999:
Thank you for the information Kenora. I have disabled background data usage and unrestricted data as well. But I want to completely restricting data.
[iQOO 7] Kenora_I:
I am not aware of that feature in android.

This is the way of restricting data as I have discovered before.

I do not know if it is possible but I will look into it.
[iQOO 7] Kenora_I:
Depending on your model and version of the Android OS, the specific settings' names might be slightly different.

1. Start the Settings app.

2. Tap "Wireless & networks" and then tap "Data usage."

3. Tap "Network access."

4. In the list of apps, clear the checkbox for any apps you don't want using cellular data.
[iQOO 7] flubber999:
OnePlus View attachment 5366105

Funtouchos :

View attachment 5366109

In OnePlus you can completely restrict data usage of an app.
[iQOO 7] Kenora_I:
Yeah, maybe depending on oxygenOS and other stuff.
[iQOO 7] Kenora_I:
T

Did this work?
[iQOO 7] flubber999:
No, even through that option . I'm able to restrict background data only.
[iQOO 7] Kenora_I:
Well thats basically like no data. Unless you use the app they cant use data in the background.
[iQOO 7] flubber999:
Yeah, but it uses data.

For example : I use this option to stop ads while playing some games, which do not require any data . These games use data just to display ads. So I used to disable data and I can play games without any ads.

Now in this mobile(IQOO7), first of all we don't have an option to restrict data usage completely . Even if you restrict the background usage, still these ads are coming up in the games.
[iQOO 7] Kenora_I:
Hmm yeah unfortunately we cant disable it because the software isnt having rhe feature. Im sure Samsung and other flagship phones have it though.
[iQOO 7] flubber999:
Yes , most of the smart phones have this feature. It's an basic feature. I don't know why #iqoo not included this feature in this flagship mobile.
[iQOO 7] flubber999:
Hi @RockStar8

Any idea about this ?
[iQOO 7] nikhilkaushik:
Android doesn't disable complete internet access by default in any of its OS. This can be done however using third party VPN based ad blocking apps.

Ehen the VPN would be connected, the disabled access app won't connect to internet.