4.4 STOCK ( Rooted ) Bug Reports - Nexus 5 Q&A, Help & Troubleshooting

So I have been rooted on the stock ROM for a few weeks now, and I have noticed that i get about 15 - 20 bug reports show up in my notification area.
Does anyone else experience this ? I am using Frankos kernel and adaway in this setup.
Is there a way of disabling bug reports ?

seen it happen three times, i think it's a button combination that I'm pressing....
but I'm not totally sure

Related

List of issues with AOSP rom's

There are a bunch of AOSP rom's for our phone, most of them share the same issues since it's the same code, with slight differences based on which commits they've added. I'm hoping we can list the common issues in one thread as a reference.
1. Data handoffs between 3g/4g - I believe this is now fixed in most of them after the RIL patches, right?
2. Call volume - This CM10 commit (http://review.cyanogenmod.com/#/c/24564/) should fix this. Not in most rom's yet
3. Bluetooth pairing, call connect, streaming - does this work fully in any AOSP rom?
4. Sleep of death
5. Wakelock caused after playing media (DirectTrack)
6. Camera issues, like save to sd. The JB mod camera hasn't been updated yet.
7. Misc battery life issues - are most of these due to #5?
8. Activation issues after a flash
9. Low video recording volume
10. Notification light problems
11. 160 char sms limit, MMS doesn't work
12. Problems waking up with home button
13. Screen redraw issues (these can be fixed by turning off hardware overlays, but that increases cpu consumption)
I think it would be very helpful if we could track which rom's had which fixes merged, since otherwise it's hard to tell without asking in each thread, doing a lot of searches, and trying out.
Slimbean:
-Wake lock issue still seams to be an issue, battery life is bad
-notification light not working when call/text/email etc come in. Will be patched on next release
-data seams stable enough (ril patch is active on most recent build)
-horrible battery life
-call volume will be patched on next release
-home button to wake up phone is hit or miss
-odd screen glitches every now and then (fully live withable)
-mms sending takes forever, needed several reboots to even get it to work
-if usb fast charge is available in your kernel, it has a toggle for it in the notification tray (awesome)
-did I mention the battery life is bad?
-soft key light options do not work
I'll report more as I find them. I like these threads, good call.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Great idea for a thread!
Add low video recording in all AOSP Roms. As far as I know this has not been fixed yet.
Sticky?
Sent from my SCH-I535 using xda app-developers app
- continuous WiFi connectivity issues (none of the AOSP roms worked reliable for me)
annoyingduck said:
Slimbean:
-Wake lock issue still seams to be an issue, battery life is bad
-notification light not working when call/text/email etc come in. Will be patched on next release
-data seams stable enough (ril patch is active on most recent build)
-horrible battery life
-call volume will be patched on next release
-home button to wake up phone is hit or miss
-odd screen glitches every now and then (fully live withable)
-mms sending takes forever, needed several reboots to even get it to work
-if usb fast charge is available in your kernel, it has a toggle for it in the notification tray (awesome)
-did I mention the battery life is bad?
-soft key light options do not work
I'll report more as I find them. I like these threads, good call.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
I am using slimbean 2.5 and I am getting anywhere from 16 to 24 hours of battery life on a single charge (3-4 hours of screen) which is about normal for any AOSP/AOKP based rom.
I actually made a similar list, but deals with comparing TW quirks to AOSP quirks:
Touchwiz VS. AOSP
Touchwiz:
- No Bluetooth and Aux input simultaneously
- Wallpaper Cropping forced to non-scrolling
- No way to disable auto volume reduction upon headset plug-in
- God awful front end interface design (this is more of an opinion)
- Google Music will randomly stop working, requires screen to be turned on for it to start playing the next track
AOSP:
- Volume Quirks (upon reboot, media volume will play quiet regardless of where the slider is, if maxxed you must turn it down and then up again similar to the call volume issue)
- Call Volume at Max every call (wasn't this fixed recently?)
- Wrongly uses noise reduction mic for recording (thus quieter)
- Inferior Camera (features mainly)
- Worse battery life
- Sometimes drops data
- Not as buttery as ICS for some reason (recents excluded)
- Will frequently kill background apps, making 2GB of ram somewhat pointless
- Bluetooth streaming issues (This doesn't personally affect me but I thought I'd throw it in anyway)
Basically, the one with the shorter list wins. So, I'm on TW for now but I yearn for the AOSP list of quirks to shrink.
Div033 said:
- Wrongly uses noise reduction mic for recording (thus quieter)
Click to expand...
Click to collapse
I've been told this has been fixed, but I still experience it. Is there a workaround for this currently?
I believe that there is a big tracker which is linked to on the irc chat. I would link to it but I'm not at my pc.perhaps someone could do so?
#verizons3 on freenode
Sent from my Galaxy Nexus using Tapatalk 2
bobloblaw1 said:
I believe that there is a big tracker which is linked to on the irc chat. I would link to it but I'm not at my pc.perhaps someone could do so?
#verizons3 on freenode
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This 1? http://tinyw.in/25QW
Number 6 is not really a problem. It's all based on personal preference.
Number 1 was fixed. Sleep of death could be kernel and/or clock speed settings. Mms works fine. There is a fix somewhere for direct track. Battery issues? Umm mines been perfect. That could be contributed to people not knowing what's causing wake locks and not fixing it. Not sure how anybody is getting screen redraws I haven't disabled hardware overlay and mine is fine, using apex if that makes a difference.
Most if not all of those issues are non existent in liquid smooth.
Hope this is the right spot to post this question. I tried flashing 2 separate roms today (Slim Rom and Liquid Smooth) which I believe are both AOSP, but I could be wrong. On both occasions, it starts to boot and gets to the google account login screen and the screen on the phone just keeps flickering and goes black.
I am unlocked, obviously rooted, with CWM 6.0.1.1 and have flashed JB TW rom in the past with no problems but went back to TW ICS, which I am currently running now.
Anyone know or direct me to the right thread as to why the screen flickering happens after flashing these AOSP roms? I haven't tried CM10 yet because these other roms actually sound more stable than CM10 right now.
Any suggestions? Thanks in advance.
bales3795 said:
Hope this is the right spot to post this question. I tried flashing 2 separate roms today (Slim Rom and Liquid Smooth) which I believe are both AOSP, but I could be wrong. On both occasions, it starts to boot and gets to the google account login screen and the screen on the phone just keeps flickering and goes black.
I am unlocked, obviously rooted, with CWM 6.0.1.1 and have flashed JB TW rom in the past with no problems but went back to TW ICS, which I am currently running now.
Anyone know or direct me to the right thread as to why the screen flickering happens after flashing these AOSP roms? I haven't tried CM10 yet because these other roms actually sound more stable than CM10 right now.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Disable hardware overlay in developer options
Neverendingxsin said:
Disable hardware overlay in developer options
Click to expand...
Click to collapse
That might work, but I cannot even get into the OS to disable anything. It is completely unusable when I flash any of these roms.
Would there be something out there that I could flash in CWM to disable this in the rom pre-boot?
bales3795 said:
That might work, but I cannot even get into the OS to disable anything. It is completely unusable when I flash any of these roms.
Would there be something out there that I could flash in CWM to disable this in the rom pre-boot?
Click to expand...
Click to collapse
Nothing that I know of sorry.
One of the main reasons I don't use any AOSP roms is because of the bluetooth sync issue. In two of my cars, it will sync for the first time, but any other time I get in the car it won't pair up. I have to manually connect it every single time.
wifi errors, i get out of range and or wps failed on any aosp rom.
I find that signal is just not as strong as compared to Touchwiz roms.
Sent from my SCH-I535 using xda app-developers app
ROM: CM10 M2
Using Android Pro Widgets (the APW People widget in particular), it lags (the widget, not the ROM). Anyone run into this issue? Not a big problem, just curious.
Any word on when the call volume is going to be merged into the CM10 build for d2vzw

CM 11 C2 Nightly - Bug Status

Hello xda,
my girlfriend and I are using the latest nightlies from CM11 out of THIS thread since a week, and I want to report some bugs we expericened. I would post this in the official thread of the ROM, but I don't have enough posts to post in there. :/
So, here is a list of the issues we experienced:
- camera doesn't work --> not focusing, crashing (known issue that exists since a long time)
- freezing when you try to unlock it --> sometimes if you want to unlock it with pressing the power button it just does not respond, you have to restart it when this happens (only read once, so I don't know if I am the only one with this kind of issue)
- WiFi still does not work after the update 30012014 (also known, for a few people it works, not for us)
- battery life is pretty... awkward for us since CM11 (both of our C2's where in repair a week ago and both our batterys got changed, so it doesn't bugs because of this reason)
Hope I can contribute with this little listing to fix these issues, if you can, could you say to me how the fixing status is?
Greetings,
- sinkingFX

[Q] Pixelated flashing lines on display screen

I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
Are you completely stock? Any custom kernel? Any rom?
Usually it's a kernel issue - tearing, but it's only present on custom kernels (never came across on the stock cm11 kernel). You might wanna try a different kernel though, if you're comfortable with that.
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
mupper said:
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
Click to expand...
Click to collapse
Was it working before those changes?
edit:
Perhaps this might help?
http://forum.xda-developers.com/oneplus-one/general/ghost-touches-flickering-graphics-t2900756
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
I had exact same issue during recording a video yesterday night !! I am latest mahdi and latest franco...
Funny thing is it went away once i exited the camera... what rom and kernel are u using ?
I've been having the same issue too. I don't have a solution for you, though. I haven't been able to find much about it.
Same issue here, stock all the way, only been since latest update. The update didn't flash properly, it gave an error stating it couldn't be located but i went through the files and it was there and then upgraded OK
I had the same problem. Selecting "Force GPU Rendering" in developer options cured it.
i have stock everything. i'm not rooted.
a reboot fixes the problem temporarily. shoot, all the issues i've ran into with this phone thus far (like the GPS not locking on) is fixed by a reboot. i know a reboot is good to do every now-and-again regardless, but having to do it constantly to fix issues is the sign of a failing device and is very annoying; it shouldn't be something you have to do with a brand new device.
i am facing this too randomly. Am on rooted 38R with Franco kernel. Rebooting is a temp cure but it will frustrating to keep doing it.
This happened to me after getting 38R. Fortunately it hasn't been back since a hard reboot. It would show up on Youtube & when dragging down the notifications area.
I had this today on PAC ROM. When I unlock phone and lock ring animation dots flash up made lines come across screen not sure what it was or why. Just rebooted phone. Back to normal. But trying out vanir later tonight try something abit different.
Also experiencing this here.
Stock ROM, clean 38R install.
Stock kernel.
Rooted, with a few xposed modules.
Started a day or two ago. Haven't found a way to recreate it. When it does happen, a reboot remedies it, but only temporarily.
I will attempt to screenrec it the next time.
I find it interesting that I only see mentions of this starting recently.
Same problem for me since the last update. Restarting the Phone solves the problem for some times. Maybe a driver issue?
Glad to see that it is not a hardware issue.
Same here
Same here, mahdi-2.8-bacon-20141001 ROM, enabled "Force GPU rendering" in Developer options, let's see if this comes back!
I have the same problem on latest cm nightly with stock kernel. And dev options works sometimes but it resets on reboot and my phone reboots randomly all the time. I'm starting to hate this device
Sent from my A0001 using Tapatalk
I also have the same issue on Stock 38R update + franco kernel r27
It happens after the latest kernel update, before I never had this lines.
Lucky for me I don't have any reboots now but I fear that will come to pass as well.
Got the same problem with Mahdi Rom 2.8 - 20141016
Will be solved in Franco Kernel r28,he just confirmed this on his kernel thread.
Sent from my OnePlus One using XDA Free mobile app
same issue here. i have to reboot. its happened on stock and AK kernel. will try enabling force gpu rendering and see if it comes back

SystemUI freeze and crash after device unlock

Since Monday I've encountered some strange bugs where unlocking my device with the fingerprint sensor leads to a freeze sometimes which leads to a UI restart. Happens approx. every 12 to 16h.
I use:
- OOS 9.0.3
- xXx 4.5a
- Smurf 2.0.53
The issue started occuring on Monday after updating xXx from 4.4 l. Before that I never had such issues at all. I don't think xXx is responsible though but I'm not sure.
Did anyone encounter a smiliar problem or does anyone want to help me debug the log files. I looked through them but couldn't find the issue causing it. I'm trying to debug it myself but it's difficult as the issue isn't easily reproducible.
Thanks!
I guess step one is to see if disabling xxx from magisk makes any difference.

Mi Note 10 Black Screen Delay Issues [PLEASE HELP]

The phone is 2 years old, unlocked it a few months ago to play APK apps that required rooting.
Phone started lagging after that a bit, eventually it updated to MIUI 12, when the phone drastically started lagging.
I tried installing ArrowOS custom ROM, hoping that it would fix the issue, assuming that MIUI 12 is too heavy for the phone to handle - nope.
The problems started to occur more often and new issues started appearing.
Current major issues:
* Screen delay when trying to unlock with fingerprint / power button.
* Black screen / unresponsive screen on power button press.
* Notifications don't show up (black screen).
* When someone calls me -> phone vibrates/rings but the screen is black.
* Double tap to wake up -> black screen.
^All of the issues mentioned above that contain the black screen problem, sometimes but rarely the phone is responsive but it's like 2 times out of 20.
Things I have tried:
- Turn off all animations from Developer Options.
- Wipe Data / Dalvik Cache / Phone Cache / Factory Reset / Custom ROM.
- Installed stock ROM for Europe (since I live in EU) for my phone (latest MIUI 13) -> problem still persists.
- Wiped Cache / Dalvik after installing stock ROM (problem persists).
- Multiple factory resets (didn't fix the issue).
- Disable HW overlays -> this seemed to somehow give better performance but it disabled my Fingerprint function and I need this for banking security reasons, etc.
Overall the phone is still fast enough, no other issues, the most common issue is the black screen and the phone having this huge delay where sometimes it would turn on the screen for half a second and then go pure black again.
Most of the times I have to hold the power button for 10 seconds to force reboot it in order to access my phone.
Help is appreciated, thanks in advance people!
Snorlax1337 said:
The phone is 2 years old, unlocked it a few months ago to play APK apps that required rooting.
Phone started lagging after that a bit, eventually it updated to MIUI 12, when the phone drastically started lagging.
I tried installing ArrowOS custom ROM, hoping that it would fix the issue, assuming that MIUI 12 is too heavy for the phone to handle - nope.
The problems started to occur more often and new issues started appearing.
Current major issues:
* Screen delay when trying to unlock with fingerprint / power button.
* Black screen / unresponsive screen on power button press.
* Notifications don't show up (black screen).
* When someone calls me -> phone vibrates/rings but the screen is black.
* Double tap to wake up -> black screen.
^All of the issues mentioned above that contain the black screen problem, sometimes but rarely the phone is responsive but it's like 2 times out of 20.
Things I have tried:
- Turn off all animations from Developer Options.
- Wipe Data / Dalvik Cache / Phone Cache / Factory Reset / Custom ROM.
- Installed stock ROM for Europe (since I live in EU) for my phone (latest MIUI 13) -> problem still persists.
- Wiped Cache / Dalvik after installing stock ROM (problem persists).
- Multiple factory resets (didn't fix the issue).
- Disable HW overlays -> this seemed to somehow give better performance but it disabled my Fingerprint function and I need this for banking security reasons, etc.
Overall the phone is still fast enough, no other issues, the most common issue is the black screen and the phone having this huge delay where sometimes it would turn on the screen for half a second and then go pure black again.
Most of the times I have to hold the power button for 10 seconds to force reboot it in order to access my phone.
Help is appreciated, thanks in advance people!
Click to expand...
Click to collapse
Well, if the same thing happens to you both on MIUI and custom ROM, the only thing I can think of is that you are installing something (most probably with root access) that gives you this issue. MIUI is obviously laggy itself, but Arrow/Octavi/Cipher are smooth and fast. Personally I use Octavi and face no such issue like yours.
Lord Sithek said:
Well, if the same thing happens to you both on MIUI and custom ROM, the only thing I can think of is that you are installing something (most probably with root access) that gives you this issue. MIUI is obviously laggy itself, but Arrow/Octavi/Cipher are smooth and fast. Personally I use Octavi and face no such issue like yours.
Click to expand...
Click to collapse
I wish an app was the issue, the only app that I have installed is YouTube Vanced and it doesn't even require root access, the problem is that on a fresh installed stock ROM, the problem still persisted which brings me questions;
1) Am I installing a stock ROM Android 11+ which is too heavy for my phone causing lags?
2) Could it be a hardware issue considering that the problem exists on a freshly flashed ROM? But I need to exclude 1) first.
Snorlax1337 said:
I wish an app was the issue, the only app that I have installed is YouTube Vanced and it doesn't even require root access, the problem is that on a fresh installed stock ROM, the problem still persisted which brings me questions;
1) Am I installing a stock ROM Android 11+ which is too heavy for my phone causing lags?
2) Could it be a hardware issue considering that the problem exists on a freshly flashed ROM? But I need to exclude 1) first.
Click to expand...
Click to collapse
As I said, MIUI is heavy skin and it definitely lags more than AOSP custom ROM, but it shouldnt give you black screen issue. You could try to install Xiaomi.eu rom, which is a debloated, better version of MIUI than the stock one: https://sourceforge.net/projects/xi...MINote10_MICC9Pro_22.5.25_v13-11.zip/download
If multiple factory resets didnt help, then yes, it may be the hardware issue I think. But Im not that knowledgable to tell this definitely
Lord Sithek said:
As I said, MIUI is heavy skin and it definitely lags more than AOSP custom ROM, but it shouldnt give you black screen issue. You could try to install Xiaomi.eu rom, which is a debloated, better version of MIUI than the stock one: https://sourceforge.net/projects/xi...MINote10_MICC9Pro_22.5.25_v13-11.zip/download
If multiple factory resets didnt help, then yes, it may be the hardware issue I think. But Im not that knowledgable to tell this definitely
Click to expand...
Click to collapse
I was already recommended by Scarlet on discord (if not mistaking the username) to install EU stock ROM which I did but the problem still occcurs, I guess I will try and give it on a mobile service check just to make sure it's not a hardware issue, I will still however wait for more replies in case someone else had the issue and managed to fix it software wise, thanks for the suggestions buddy!
Snorlax1337 said:
I was already recommended by Scarlet on discord (if not mistaking the username) to install EU stock ROM which I did but the problem still occcurs, I guess I will try and give it on a mobile service check just to make sure it's not a hardware issue, I will still however wait for more replies in case someone else had the issue and managed to fix it software wise, thanks for the suggestions buddy!
Click to expand...
Click to collapse
You're welcome. However, Mi Note 10 XDA forum isn't particulary active, if you use Telegram, you can try to ask in the groups for tucana:
Mi Note 10 /10 Pro | OFFICIALâ„¢
Xiaomi Mi Note 10/10 Pro - Official Telegram Group - Our Channel: @MiNote10Updates - Our Off-Topic group: @XiaomemeOT - Our Photography group: @XiaomemePhotography - Our Customization group: @XiaomemeCustomization
t.me
Octavi - Tucana and Bitra
Discussion group for OctaviOS and Phobos kernel maintained by @erikdrozina News channel: @erikdrozinastuff
t.me
Good luck

Categories

Resources