[Q] Best place to report bug - Galaxy S 4 Q&A, Help & Troubleshooting

device: 9505G
issue: audio over bluetooth does not work 2nd time a device is connected. Must toggle BT off/on (works sometimes) or restart device
This issue persists on all AOSP-based 5.0 and 5.1.x ROMs I've installed (mostly CM-based). My question is, where should I report this issue? I could report it on individual ROMs' threads, but I don't think that will fix the source of the issue. I've never reported a bug to AOSP. Upon investigating that option, it looks like that's meant for developers https://source.android.com/source/report-bugs.html
Does anybody have any experience in troubleshooting this sort of bug that can advise on the best course of action to take? Let me know if you need more information on the issue.

If the developers do not know there is an issue, how are they going to fix it?
In addition to mentioning the presence of a bug on the ROM thread you need to provide the developer with a logcat showing the activity as it occurs. If no logcat is provided, your statement will either be brushed aside or outright ignored.

Related

Camera Driver or Firmware Bug: Torch + Autofocus

I apologize if this isn't the correct place to post this, it seemed the most logical group.
I am coming up against some unique issues on a Nexus S. I don't have any mods on this device, it is stock Android 2.3.1 running 2.6.35.7-g7f1638a android-build (at symbol)apa28 #1.
There appears to be a bug on this device which results in the LED torch being disabled when the autofocus callback is called. To reproduce the issue simply:
Set the flash mode to Camera.Parameters.FLASH_MODE_TORCH
Set the focus mode to Camera.Parameters.FOCUS_MODE_AUTO
Start autofocus
This behavior is unique to this device, although I can only admit to having tested on 7 other Android devices. DroidX suffers from a similar bug but rather than the LED turning off, it blinks.
Inspection of the camera parameters inside the callback shows that flash-mode=torch so it is not an issue of the camera parameters being overwritten.
Has anyone seen this issue that might know how to work around it without modifying the device? My attempts at contacting and submitting bug reports to Samsung has failed miserably. It would be appropriate to make the remark that "Samsung is where bug reports go to die".
My primary concern is that the torch feature behaves so differently on every device, yet all of these devices claim to support Camera.Parameters.FLASH_MODE_TORCH. I'm really hoping to find a generic way to work around this issue since I believe there will be a lot more variation in camera driver implementations in the future.
Regards
Are you saying your camera isn't working because mine isn't working it keeps force closing
Sent from my Nexus S using XDA App
Wouldn't you rather submit the bug to Google via their bug tracking forum? I think Samsung is out of the picture.

Android 6.0 AOSP ROM crash/reboot with Chrome Location

Hi all, first post so can't report this in the Dev forum.
I have flashed Marshmallow onto my Nexus 4 according to the instructions in the "official" ROM thread.
All seems to be fine, I had duplicate apps for the clock/calendar etc which didn't bother me much, and I was getting network connectivity issues which have largely gone away. I'm happy to have upgraded as it means I don't need to get a new Nexus phone just yet :good:
However, there is a pretty serious crash trigger, that I can easily reproduce on my handset anyway. Allowing any website to access my location in Chrome will trigger a reboot, every time. Just wondering if any other users have experienced this, whether the ROM developer is aware of it, or whether there is anything I should do to fix the problem or assist in finding a fix?
I found a fix in the very thread I linked above, guess I should have read all 50 pages of it
Here is the fix for anyone coming here from Google in the future.

location based reboots on cm loss of service on oxygen

Okay as the title suggest that is exactly what is happening. On CM based Roms at certain locations in my city it will just reboot for no apparent reason.....on Oxy/Hydrogen based Roms I will temporarily loss service in these same locations.....I was wondering if anyone has ever encountered this issue and if so how did you fix it...Also this has been an ongoing issue since purchase least year....the phone was brand new when I got it.

Notification lights not working after install cm13 build from mparus

Hi
I ask this question here, as I’m knew in the forum I can’t write it directly in the ROM post where would be more appropriate.
I have installed the in the phone the CM13.0 ROM built by mparus, I have used the cm-13.0-20161118-UNOFFICIAL-mparus-without_root-g760.zip build, the last one in this moment. The phone works correctly, I only had a pair of minor issues:
-phone app was not working, caused a reboot when trying to use it: it’s a vanilla cyanogenmod problem, it’s solved choosing the phone app as default for making calls
-camera app doesn’t detect the camera device: I have read that is a bug of the official camera app, can be solved installing another app as open camera
I have a serious problem for which I have not found information about. It’s with the notification lights, they are not working except for indicating the charging status of the device, not for mails, missed calls, etc. I tried all the possible combinations for this without luck. I have also tried third party app’s like light manager and they don’t work also, perhaps something is broken in the build but I’m not sure.
Any of you has experienced this problem with the mparus mod in the ascend g7? Can you give me any advice? I’m a bit frustrated about this
Thank you
Do a clean re-install of the ROM I'd say..

OP2 Screen rotation periodically stops working

Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13
Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.
Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.

Categories

Resources