This app was mentioned in 24 comments, with an average of 3.00 upvotes
>I9305
I was going to share my modem but it's for S3 i9300 so it won't work for you, sorry.
To troubleshoot why your S3 I9305 is suffering from random reboot you could save & look in the last_kmsg file immediately after a reboot https://www.google.com/search?q=last_kmsg+I9305+random+reboot
Check the free Syslog app to make the process of collecting logs much easier & faster.
> How do I get to /proc?
Or if you have Root: get the free <strong>Syslog</strong> app and let it do all the work for you in about 3 seconds.
The easiest way, if you don't have adb set up on a computer, would be to grab one after a failure with this app: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=en
You probably want to send this to me privately though, I think his app is now stripping things out of logs like your phone number and stuff, but I'm not 100% sure and I'd rather you not plaster your phone number all over the internet. I'll PM you my email address.
Use this app; it's quite easy to use. https://play.google.com/store/apps/details?id=com.tortel.syslog&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS50b3J0ZWwuc3lzbG9nIl0
> Why do bugs like these need a logcat?
Logcat is required as described in LineageOS Wiki > How to submit a bug report. Your report will be rejected if you don't include it.
My guess is that users don't include all the relevant info in their description & there could be many reasons for a bug like other apps or interactions between stuff.
It's a basic troubleshooting tool for devs.
LineageOS Wiki - How to capture logs.
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
Log types supported: * Kernel logs (dmsg) * Last kernel log (last_kmsg, if device supports it) * Pstore logs * Main log (Logcat) * Modem log * Event logs * SELinux audit logs
>...leave unusable the Settings Search, a really useful feature.
The workaround is Settings > Apps & notifications > See all apps > Settings > Storage > Clear Data.
I had to do that twice this month on S5 LineageOS 15.1 klte & it's annoying as some settings choices you made are lost.
There are 2 open bug reports about Settings > search > not returning results @ the present by LineageOS 15.1 users with mido & axon7 phones:
And the oldest ~~BUGBASH-1688~~ Search in Settings can't search Setting item - On bullhead & dumpling phones was closed for some reason.
Under Resolution it says "Not A Bug ". :P
>Aliashab Upvote the issue here: ...REGRESSION-2192
​
>Takuya-Sama ..i can't upvote cause i went after wrote it here and created my account plus that issue...
Both Regressions will be probably marked as Rejected because you guys did not include the required logcat (or use an app like <em>Syslog</em> to do it quickly & easily) as described in How to submit a bug report and/or with a message similar to this because there are already other older Bugbash reports on the same bug for the same 15.1 branch:
>This tracker is for regressions within a given branch, i.e. "I know this worked in last week's lineage 14.1 nightly and it's broken in today's lineage 14.1 nightly"; you must have a last-known-good previous lineage 14.1 nightly for this to be valid.
Best practice is to not clutter Jira with multiple repetitive similar reports which only makes the work of the volunteers devs harder & search Jira before creating a new one, vote up the oldest Open one (smaller report number within Bugbash or Regression) and include in the comments your model's name & build & if possible details similar to the Reporter's including a logcat.
>I have done it https://gitlab.com/LineageOS/issues/android/issues/924
Good but the pesky LineageOS Automation bot closed your report and labeled it "invalid" because in the description you wrote "version lineage-16" instead of the exact version lineage-16.0 as who knows as we may get a 16.1 or 16.x in the future.
Also as you can read in LineageOS Wiki > How to submit a bug report:
> Logcats must be attached for all android bugs, and must be captured right after reproducing the issue.
Users often don't include all the relevant info in their description (like rooting method, etc) & there could be many reasons for a bug like other apps or interactions between stuff.
It's a basic troubleshooting tool for devs.
You can edit your bug report & re-open it.
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
Log types supported: * Kernel logs (dmsg) * Last kernel log (last_kmsg, if device supports it) * Pstore logs * Main log (Logcat) * Modem log * Event logs * SELinux audit logs
@ u/VividVerism maybe you could vote it up, post in that bug report thread & attach a logcat also which would provide more data points for the devs & also show that it affects more than one Motorola model.
> ...I will try to report a bug, and I hope it is not too difficult.
It's not but there are two caveat: * Bugs are not easy to troubleshoot & not enough volunteer LineageOS devs work on them so they pile up & most of them sit there unresolved. There are 454 open 16.0 Issues @ the present as you can see in this bug tracker search. Obviously many of these bug reports are about stuff not supported by LineageOS or poorly done without proper bug description. * If you don't follow the instructions & fill up all the required info & proper device info labels then the LineageOS Automation robot will keep on closing the issue until you get it right like in this example.
See LineageOS Wiki > How to submit a bug report.
Your bug report may be rejected if you don't include the required logcat in your original post as described in that page:
>...Logcats must be attached for all android bugs, and must be captured right after reproducing the issue.
A logcat is an essential troubleshooting tool for devs.
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
Log types supported: * Kernel logs (dmsg) * Last kernel log (last_kmsg, if device supports it & the S5 does) * Pstore logs * Main log (Logcat) * Modem log * Event logs
>... Have you any experience in reporting bugs in LineageOS?
Yes & I captured a logcat after testing AudioFX yesterday. Either you can create a report, post the link here & I can contribute to it or vice versa: I can make one and you could post in it.
Made one here: #784 - 16.0 Dark Style - Invisible Black on Black Icons and LineageOS dev u/npjohnson1 labeled it Platform which I guess means a higher priority but i'st still unresolved 6 months later. Maybe nobody knows how to fix it @ the present or nobody looked into it.
Bug tracker search with the label Platform
>...So far I just use the samsung explorer in combination with Adguard.
Are you talking about the Samsung Internet Browser? If so it works surprisingly well. I used it a while ago but switched to Microsoft Edge which syncs to my Windows 10 PC Edge but still use the stock LineageOS Browser a lot because it's fast & it's low on resources usage.
I tried Adguard a while ago but it's using a VPN & had an impact on battery life while an ad blocking custom hosts file does not & is faster.
What does it say in your S5 about Adguard in Settings > Battery usage from full charge down to 10~20% for example?
>...are you also able to replicate the switching to mono?...
Not yet but may try that later. That can be a useful troubleshooting step for the devs but not something one wants to use as a workaround when listening to .mp3 music files.
>...in DND mode whatsapp calls from a starred contact do come through!...
Thanks for testing & reporting back.
That's what I expected.
My guess is it's a WhatsApp issue with DND & messages related stuff in it broken or missing.
Maybe you could contact WhatsApp Support & report it there?
You could capture a logcat & look into it for WhatsApp errors while in DND mode.
To make the logcat short & relevant: reboot, reproduce the problem & then use SysLog to quickly capture a logcat.
SysLog's Play Store page explains how to give the app the required permission via adb if you don't have root. Syslog on GitHub w/ F-Droid + Play Store links.
Or check LineageOS Wiki - How to capture logs (logcat) without root using adb.
Edit: a fix has been merged and all LineageOS 14.1 devices will receive it soon: 233993 (Merged as e8f9b68 ): ZoneInfo: Exclude boundary tz transitions
Try this workaround: > Settings > Date & time > turn on Automatic date & time and Automatic time zone. If they were already selected by default try toggling off and set date, time & time zone manually, > Settings > Apps > Calendar > Storage > Clear Data.
Turn off the phone then back on (not a soft reboot).
A S3 i9300 LineageOS 14.1 user in time zone UTC+3 reported here on XDA that it worked for him.
No problem with my S3 i9300 LineageOS 14.1 build 2018-11-01 using both stock Calendar & Google Calendar but then I am in time zone UTC-6 Central America without day-light saving changes because near the equator.
What is your time zone as only some of them may be affected? Or it could be related to day-light saving changes.
I checked your BUGBASH-2492 & you did not include the required logcat so it may be rejected but also it's a Regression really because it worked fine before 2018-10-23. Check this REGRESSION-2188 about the Calendar wrong date 1969 or 1970 bug which is also missing a logcat. :\
See How to submit a bug report: "Logcats must be attached for all bugs, and must be captured right after reproducing the issue."
You can use an app like Syslog to capture logs quickly & easily.
It seems related to merged in i9300 build 2018-10-25 zoneinfo: Update tzdata to 2018f and icu: Update tzdata to 2018f those were updated in i9300 build 2018-11-01 with zoneinfo: Update tzdata to 2018g and icu: Update tzdata to 2018g but the bug is still present.
>...This is the bug report I created: https://gitlab.com/LineageOS/issues/android/issues/1328 ...I didn't attach any logs because this issue happens randomly and I have no idea how to replicate it...
A logcat is an essential troubleshooting tool for devs.
Your bug report may be rejected if you don't include the required logcat in your original post as described in that page:
>...Logcats must be attached for all android bugs, and must be captured right after reproducing the issue.
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
If you can't reproduce the issue then how can a dev do it?
>...There is at least a couple more similar reports on gitlab...
Links please?
Edit:
>u/johndoest - ...Official miui firmware does not have this problem. It's purely LOS related.
Got a Pocophone F1 with touch issues? Xiaomi wants your device
See the optimization tips described here including using LineageOS's Privacy Guard Advanced: S5 Remove Animations UI Speedup Test - Taming Google & Apps
Check in Developer options > Running services > and also it's 3-dots > Show cached processes.
You can also use adb. Check these searches: adb shell top and adb shell ram usage
You could also capture a logcat & open it in WordPad, Notepad++ or similar & look at the errors.
To make the logcat short & relevant: reboot, reproduce the problem & I like to use SysLog to quickly capture a logcat.
SysLog's Play Store & Github pages explains how to give the app the required permission via adb if you don't have root. Syslog on GitHub with F-Droid + Play Store links.
>Ok, the stock to lineage didn't work. I also had to include Boot in the restore from backup.
Ahh crap, you are right I forgot that & edited the post above. What TWRP labels as Boot is actually the kernel which in this case is LineageOS's kernel. ↑ Thanks for reporting back about it.
>And if that doesn't work I'll submit a bug(how do I do that, and how do I get logs that are needed?)
Included in the XDA post I linked to above:
>Maybe you could submit a bug report as described in LineageOS Wiki > How to submit a bug report including capturing a logcat after rebooting & reproducing the problem & also include a link to giffgaff's APN settings page?
That bug how-to wiki page includes a link "...Logcats must be attached for all android bugs, and must be captured right after reproducing the issue.".
To make the logcat short & relevant: reboot, reproduce the problem & I like to use SysLog to quickly capture a logcat.
SysLog's Play Store & Github pages explains how to give the app the required permission via adb if you don't have root. Syslog on GitHub with F-Droid + Play Store links.
If you do make a LineageOS bug report, please post a link to it here & also in that XDA thread.
Did you try calling giffgaff support or emailing them?
This web search returns quite a few results: giffgaff data problem including this giffgaff support - Why isn’t my data working?
>Tried the APN from stock again, still the same...
What were they exactly?
In this giffgaff support - Internet APN settings guide it says @ the present:
>Make sure not to confuse "proxy" and "MMS proxy". The first one must be left blank and the value for MMS Proxy is 82.132.254.1
u/kodifies is that exactly what you have currently in your giffgaff APN settings?
>The keyboard switcher notification only appears if you have more than one keyboard enabled. When I only enable Gboard, it goes away. If I also enable stock keyboard, the notification keyboard switcher has the appropriate white font, but it just lists "Gboard" as an option not any of the languages within it.
This is a much better description of the issue. Could you please edit your OP (first post) & include it + your device model & firmware version?
I can reproduce your issue on S5 klte running beta unofficial 16.0 LineageOS klte made by S5 LOS maintainer haggertk: Settings > Display > Style > Style > Dark and back to Settings > Display > Style > Dark mode > Dark.
The workaround shown in the screenshots: Settings > Display > Style > Dark mode > Default: Gboard Change keyboard Dark Style
It's no pure black but can solve your problem until it's fixed. It is the Gboard > long press the Space bar > keyboard switcher like the screenshot linked in your OP.
***
If you want to contribute to solving the problem you can create a Bugbash & include the required logcat.
See the LineageOS Wiki > How to submit a bug report and How to capture logs.
If rooted you can use an app like Syslog to quickly & easily capture logs without the need to use a computer & adb or a Terminal emulator as described in that page.
You could then post a link to your Bugbash in this thread.
I cannot create one @ the present because running an unofficial build.
> ...Due to that bug on LOS 16 build for S3 Neo, I cannot connect to it using that phone, unlike any other... > >...So it is obviously a bug that should be fixed, especially that it isn't present in any other LOS build on other phone models that I own...
You could contribute & submit a bug report but they just seem to pile up.
Your bug report may be rejected if you don't include the required logcat in your original post as described in LineageOS Wiki > How to submit a bug report.
>...Logcats must be attached for all android bugs, and must be captured right after reproducing the issue.
A logcat is an essential troubleshooting tool for devs.
To make the logcat short & relevant: reboot, reproduce the problem & capture the logcat.
See other reports for inspiration & if you do create one please post the link in your OP.
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
>u/1954StarDust - ...Just completed latest update and getting Warning, two so far, Also recently added sim card, had been running on wifi . What's going on? Sending SMS messages 1.(Sim tool kit) 2.(com.qualcomm.qcrilmsg).. is sending a large number of SMS messages. Do you want to allow this app to continue sending messages?
You forgot to mention your device model & LineageOS version + build date.
BTW "last" or "latest" or "most recent" or "today's" will not mean a thing for future readers after the next update so taking 2-3 seconds to type the exact build date that you are talking about is good practice IMO.
Bugs may be created by a merged patch in a given build date for a given device & solved in an other build so that's why the build date is an important troubleshooting info.
AFAIK the SIM Toolkit app varies depending on the device & the menu it contains varies depending on the network provider & network data plan.
On my Galaxy S5 G900M LineageOS 16.0 klte build 2020-02-23, in app's info: SIM Toolkit com.android.stk & a post paid plan sends zero SMS.
Maybe yours is trying to communicate with your network provider?
You could capture a logcat & look inside for clues by searching for com.qualcomm.qcrilmsg.
See https://wiki.lineageos.org/logcat.html
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
You could use an app like MatLog: Material Logcat Reader or Logcat Extreme for example & filter with qcrilmsg for example & save the logcat.
Did you install a GApps package with LineageOS?
Where did you get that Spotify app from?
You could reboot, reproduce the problem, capture a logcat & search it with Spotify.
See https://wiki.lineageos.org/logcat.html
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
You could use an app like MatLog: Material Logcat Reader or Logcat Extreme for example & filter with Spotify & save the logcat.
>u/General-Head - Leeco le2 (s2) model have a problem 16.0 version this model version have mic noise big problem mic capturing all type sounds and background sound please fix it fast
Keep I mind that the LineageOS device maintainers are unpaid volunteers working on this project on their free time.
You could contribute to solving the problem. See LineageOS Wiki > How to submit a bug report.
Your bug report may be rejected if you don't include the required logcat in your original post as described in that page:
>...Logcats must be attached for all android bugs, and must be captured right after reproducing the issue.
A logcat is an essential troubleshooting tool for devs.
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
> My device is OnePlus3T running LineageOS 20191226. I downgraded to this, thinking maybe only 20191230 has the "issue" but it is the same.
Connect your device to a computer & try this in a adb command window:
adb devices
The response should be:
List of devices attached
xxxxxxxx {your device serial number} device
Check current adb debugging status which is enabled obviously if you see that your device is seen by adb:
adb shell settings get global adb_enabled
The response should be:
1
{1 = enabled. 0 = disabled}
Disable adb debugging on the device using adb itself:
adb shell settings put global adb_enabled 0
There should be no response if adb is disabled on the device with this command:
List of devices attached
Reboot the device manually & check if ADB debugging is enabled or disabled in Developer options.
If adb debugging enabled itself see LineageOS Wiki > How to submit a bug report.
Your bug report may be rejected if you don't include the required logcat in your original post as described in that page:
>...Logcats must be attached for all android bugs, and must be captured right after reproducing the issue.
A logcat is an essential troubleshooting tool for devs.
I use the quick & easy Syslog to capture logs without the need to use a computer & adb or a Terminal emulator as described in that LineageOS Wiki page.
See the Play Store page for details, screenshots & how to use it without root but it's also available on F-Droid: Syslog.
This seems to be a bug with the OnePlus 3T and OnePlus 3 as other users reported the same problem: u/cpu2910 & u/gnulynnux.
Grab a logcat as suggested above if you want to know what is really happening in your device.
To make the logcat short & relevant: reboot, reproduce the problem & I like to use SysLog to quickly capture a logcat.
SysLog's Play Store & Github pages explains how to give the app the required permission via adb if you don't have root. Syslog on GitHub with F-Droid + Play Store links.
Or check https://wiki.lineageos.org/logcat.html
See XDA portal article What is ADB? How to Install ADB, Common Uses, and Advanced Tutorials for more info if you don't have it setup already.
Or you could flash the most recent stock official manufacturer's ROM for your device which will update the radios firmwares & it's the best troubleshooting step to confirm or rule out a hardware problem.
> ...this has been happening to me for about 6 months, no idea what causes it or what stops it when the phone finally boots correctly.
Could you provide a setup description?
For example no problem booting on my Galaxy S5 G900M LineageOS 16.0 klte build 2019-12-01 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind.
If you have adb debugging enabled & when it's working authorize the connection to a computer you could capture a logcat of what is happening during a failed or delayed boot to system.
You could upload the logcat somewhere & maybe we could look into it for errors. Or open it in WordPad, Notepad++ or similar & look at the errors & search it with crash or fatal for example.
See XDA portal article What is ADB? How to Install ADB, Common Uses, and Advanced Tutorials for more info.
To make the logcat short & relevant: reboot, reproduce the problem & I like to use SysLog to quickly capture a logcat.
SysLog's Play Store & Github pages explains how to give the app the required permission via adb if you don't have root. Syslog on GitHub with F-Droid + Play Store links.
>Something in software is messing with my proximity sensor calibration on Official Lineage 16 on my Moto Z2 Force
To make the logcat short & relevant: reboot, reproduce the problem & I like to use SysLog to quickly capture a logcat.
SysLog's Play Store & Github pages explains how to give the app the required permission via adb if you don't have root. Syslog on GitHub with F-Droid + Play Store links.
Try syslog, you can get various logs with it. If you're not too savvy about parsing logs, this will be an easier way for you to gather the info I think, and easily share it.
I have the same problem. I sent logfiles using this app. Syslog