Is anybody that does their own Lineage builds having issues with the gallery app? When I open it, after about 3 seconds it totally freezes my Pixel XL and forces it to reboot. Running logcat and then opening the app until it reboots gives me nothing out of the ordinary and reverting the one commit that I thought may have caused it, based on some research, and rebuilding did nothing.
The strange part is that over in the Pixel XL board, Invisiblek does unofficial builds for us and his May 12th build does not have this issue. There haven't been any gallery related commits forever and there is only one Pixel XL specific commit done after his May 12th build and it's the one I reverted which didn't fix the issue.
Related
So, I know there's been a lot of video playback issues with the Nexus 7 over the years after upgrading to lollipop or marshmallow, but I never had any of those issues until getting the July security updates for marshmallow.
The problem I'm getting is this: video streaming playback stops working after about 15 minutes. Video works fine, but after watching a few in a row, online video stops working across all applications. Facebook, Twitter, Instagram, YouTube, and embedded video on web pages, no matter the source, all stop working. I have to reboot to get it back. Having to reboot dozens of times a day to keep video working. There's another part of this bug... Sometimes, when playing video, if I close the application that is playing it the audio from the video will continue to play in a loop, even after closing the app and swiping it out of memory.
This has been happening for nearly 3 months, and I started calling nexus support about it shortly after it started. I got ahold of someone, who, when I explained the bug said "I know this problem. You have kernel 3.4.0-gad29d11 dated July 2nd" I checked, and he was correct. "The engineers know about this, and are working on a fix. It's a video driver issue in the kernel. It'll be fixed with the next update." Good enough for me. I got my August security updates (actually 2 updates in August) and the bug wasn't resolved. Called them back and got another guy who knew of the bug, and insisted it would be fixed in the next security update. I now haven't gotten any more updates since then. I got sick of waiting... 3 months with this problem... and decided to call nexus support again. After 2 days and 6+ hours on the phone, I can't get anyone at Google who knows about this bug. They are all insisting I have to get it fixed with Asus. Called Asus. They insist it's a software problem, and I have to get it fixed with Google.
Does anyone know how I can fix this? I know from Google it's an issue with this kernel, and the video drivers within. I'm not gonna hold my breath that google will fix it for me.
Google has discontinued updates of this device.
You can downgrade stock OS or upgrade to custom ROM.
I have no video issues on CM13 - 6.0.1
I was hoping to avoid going to a custom ROM, but if I have no other alternatives, I'd rather do that than downgrade the OS. Perhaps I'll wait until CM 14 is out for the n7. Very frustrating that this problem presents itself just a month before security updates are discontinued. Feels a little like planned obsolescence.
I was also thinking I could try flashing a different kernel only. ElementalX looks interesting, and I was thinking it might take care of my video driver issues. I'm a novice at this type of stuff, and I really only have experience rooting a couple other devices. I've never tried flashing a kernel or a custom ROM before. Anyone have suggestions?
Hey guys,
lately, my m8 is giving me a headache. It randomly decides to not being able to connect to the camera and opens the front-facing camera instead.
I can manage to connect to the back camera by using Open Camera and only see an inverted image which is from the second camera above the actual one.
The thing is, these things happen randomly. Sometimes it doesn't work, sometimes it does.
I can't reproduce how to keep it fixed all the time and I am a bit clueless.
Things I try: Clearing cache, fix permissions. Sometimes that fixes it, sometimes it doesn't.
I am currently on Android 7.1.1 and I am using the Resurrection Rom version 5.8.0-20161224
Kernel 3.4.113-Team-M8_1.2 [email protected] #1 Fri Dec 23 21:05:38 EST 2016
Baseband 1.25.214500021.06G_20.68.4196t.01_F
Thanks!
Xiaofeng Wei said:
Hey guys,
lately, my m8 is giving me a headache. It randomly decides to not being able to connect to the camera and opens the front-facing camera instead.
I can manage to connect to the back camera by using Open Camera and only see an inverted image which is from the second camera above the actual one.
The thing is, these things happen randomly. Sometimes it doesn't work, sometimes it does.
I can't reproduce how to keep it fixed all the time and I am a bit clueless.
Things I try: Clearing cache, fix permissions. Sometimes that fixes it, sometimes it doesn't.
I am currently on Android 7.1.1 and I am using the Resurrection Rom version 5.8.0-20161224
Kernel 3.4.113-Team-M8_1.2 [email protected] #1 Fri Dec 23 21:05:38 EST 2016
Baseband 1.25.214500021.06G_20.68.4196t.01_F
Thanks!
Click to expand...
Click to collapse
I had same problem.3 times phone was in repair,they all sad its software fault.But its not.4 time,my friend opened phone,he coudnt find the problem to fix this(he also sad it's software),but accidentally he touched some contact or cable and camera was working(+ sim reader was working again).after some time, problem came back,camera stopped working or is inverted with only upper small cam(zoe cam) working,and sim is losing contact.So it most be hardware.Which part,this is the question...
Sent from my HTC M8
Hi all,
A colleage is having issues with the Wileyfox Swift on LineageOS Nightlies (currently running lineage-14.1-20170306-nightly-crackling). When recording video using either back- or front-camera, the camera freezes after 30-32 seconds and continues to record a frozen video. Even worse, the camera can no longer be initialised until the phone is rebooted.
- I have tried with the stock LineageOS camera, Google Camera, OpenCamera apps. Same problems.
- I have tried to reduce the resolution up until 480px but that's not the problem apparently.
- I have tried this with both the back and the front-camera
- I've cleaned Dalvik/Cache aswell.
- I've also turned off flashlight entirely.
This does not seem to be a known issue, I don't find any article anywhere. Can someone else please try if they can reproduce it on their Wileyfox Swift running LineageOS? Taking pictures seems to be fine. The user reported to me that it had initially worked using lineage-14.1-20170217-nightly-crackling. I did not dare to downgrade to try this myself though.
Any advice would be appreciated. If someone can reproduce this, please be so kind and mention this is the dev thread.
I just tried. Exactly the same here.
Same issue here.
Thought this would resolve it, but no : https://review.lineageos.org/#/c/165102
Jup. Same issue here.
Same issue for me with lineage-14.1-20170328-nightly-crackling-signed installed.
Bugreport on JIRA: https://jira.lineageos.org/browse/BUGBASH-395
Fixed
Fixed in 20170410 build. Enjoy.
it works with 20170410
I tried the 20170410 build and it is fixed indeed !
Moved from CrDroid to LOS after having Snapchat and Sync for Reddit crash on me constantly. Told it was a Gapps issue so I reinstalled multiple times; no changes. Thought it might be a ROM issue so I went to LOS. Now not only does my apps crash constantly, my OPO now restarts by itself at least once a day. I don't know what to do or what I'm doing wrong and I'm at my wit's end
I've had this phone for less than two years guys if anyone can help me out I would be suuuuper appreciative I don't want to think Oneplus makes bad phones because I know they don't
Thanks!
Should I bump the thread...? Is that allowed...?
Starting today, my camera opens to a blank black screen when I launch the app. If I reboot the phone, I can successfully launch the camera app and take photos. However, if I attempt to use the camera built into Android Messages, Facebook, and even the bar code scanner app I have installed, the issue starts again. I have tried uninstalling the updates to the camera app, clearing data, and I even did a factory restore. I booted up into safe mode, then duplicated the issue there as well (this eliminates 3rd party apps as the cause). Some other threads I have read say to toggle Bluetooth or turn on airplane mode. Nothing fixes the problem.
I hopped in chat with Google Support and they had me follow this guide (which didn't fix anything). They requested the factory reset. After the factory reset, they required me to gather a bug report to send to them. I requested a replacement device, but the support technician declined and said this issue isn't something that can get a replacement device. I am very irritated I spent so much money on this device and it is already (two and a half weeks later) starting to not work.
Has anyone else on the Pixel 3 XL had this issue? Any other recommendations to fix it?
try flash-all.bat from googles factory images. could be a corrupt persist partition
I don't have an unlocked bootloader. That's required for that, right? Would I need an unlocked bootloader to flash the image?
tallymatty said:
I don't have an unlocked bootloader. That's required for that, right? Would I need an unlocked bootloader to flash the image?
Click to expand...
Click to collapse
believe so
then you can relock
process takes 5 minutes to complete
Blank camera screen when camera opened from from another app
I have the same issue with my pixel 3 xl. Blank camera when it's opened with messages app, fb, WhatsApp, Instagram, fb messages. Called Google support and they had me clear cache, uninstall cam updates restart phone and in the end factory reset but it didn't fix it. They can't identify if it's a software issue. They even had me boot up in safe mode and had screen sharing session.
After multiple calls and hours of troubleshooting, Google will be replacing my phone. Hopefully the new phone don't have this problem.
No luck for me, unfortunately. I unlocked the bootloader and flashed the factory image. The issue persisted after the flash. I contact Google Support again and they continue to tell me the issue is going to be resolved by engineering and they will not replace the defective device. Total bummer for such an expensive brick.
On support contact #3, Google has decided to replace the device for me. Just FYI, in case anyone else has this problem with their phone. I asked for a manager during contact #2 and didn't hear anything back for 24 hours. The person I got on #3 was very nice and assisted in the replacement order.
Had the same issue with 2 of my pixel 2 xl phones. First one was sent away for 2 weeks and then replaced. replacement one lasted a couple months before it had the same issues, I demanded a RMA from google so i could get it swapped in store. The second phone that was replaced lasted a day, it had a weird bright screen flash when locking, unlocking, hanging up from a call etc. That was also RMA and returned and replaced in store.
Hope my 3 doesn't have these issues.
camera hardware is crashing when used by any app other than the "Camera" app
I have the same issues during one week. What I find is the playground and any app other than the "Camera" app attempts to access the camera hardware, the camera itself becomes unresponsive.* After that, the camera cannot be accessed by any application, including the "Camera" app. There Google support told me the engineers will fix that problem. But I'm not sure if that's a hardware issue or software issues.
I'm wondering if this is a November update issue - anyone try flashing back to first release?
Similar issue here, on November, will try to flash november again and test.
Edit:
and..... did not fix a thing. Looks like it is hardware related or if there is a hardware rev in a specific part that is not coded properly.
I can assure you that it is not an issue with November patch or any patch. I have this issue and I am still running with the stock September security patch that came with the phone. I was hoping that updating to the latest patch would fix the issue, but now I'm beginning to think that won't resolve the problem.
Sent from my Pixel 3 XL using Tapatalk
I'm the new one ?
Same problem here ?