I'm using 9.6.22 build, some apps have this issue when we try to scroll. The previous items overlap in the list and look like what's there in the bottom. Like playstore, phone, WhatsApp... I've only noticed it happening in these places. I'll attaching screens, but better you guys see it for yourself by trying. Incase you guys are not facing any issue on the same build, tell it in this thread.
You didn't mention you 'issue' in specific.
n00b_dr0id said:
You didn't mention you 'issue' in specific.
Click to expand...
Click to collapse
See the bottom part of the screen
drakov4444 said:
See the bottom part of the screen
Click to expand...
Click to collapse
No such thing on my device.
drakov4444 said:
See the bottom part of the screen
Click to expand...
Click to collapse
Me too, tried scrolling in different ways in playstore and phone but no such issues are present.
I can confirm. Happening to me. In pixel experience and arrow GSI images as well. I think it's a app optimisation problem. With the rounded edges and everything our device has a very weird resolution.
Can someone confirm this is not a hardware problem. ....?
sonalsaha said:
Can someone confirm this is not a hardware problem. ....?
Click to expand...
Click to collapse
I cannot confirm it (as I'm still hoping it's solvable) but I think that scrolling at the sides issue and touch problems don't happen in TWRP recovery. I may be wrong but when I scrolled through files in TWRP it seemed perfectly fine.
I started noticing this after I updated the phone, before that it was perfectly fine. Can people confirm this in the previous build 9.6.14? If so then we might have a big problem
Guess update was not good. That's why they chose to rollback. I changed to miui 10, and now everything is fine again. So it's not a hardware issue.
Confirmed, I had the same issue on my Xiaomi Mi 8 on a gsi.
Try using 9.6.14 build, or update to the recent miui 10, it's a software bug, not a hardware problem. That's probably why they rolled back the recent update.
Related
The camera app on my Droid DNA crashes whenever I open it or another application that uses the camera. I am currently running CyanogenMod (11-20140405-SNAPSHOT-M5-dlx), however it behaved the same way on the stock ROM (4.1.1 and 4.2.2). When this first happened, it would work for about a week, then not work for a week. But now it seems to permanently not be working. I am wondering whether this would be a hardware issue, or if there is something software related that needs fixed. I should also add that the front camera works just fine. I will attach system and kernel logs too. They are filtered to show anything with the word "cam" present. They are in the .docx format because they're color-coded, but plaint .txt files will be there also.
Localhost798 said:
The camera app on my Droid DNA crashes whenever I open it or another application that uses the camera. I am currently running CyanogenMod (11-20140405-SNAPSHOT-M5-dlx), however it behaved the same way on the stock ROM (4.1.1 and 4.2.2). When this first happened, it would work for about a week, then not work for a week. But now it seems to permanently not be working. I am wondering whether this would be a hardware issue, or if there is something software related that needs fixed. I should also add that the front camera works just fine. I will attach system and kernel logs too. They are filtered to show anything with the word "cam" present. They are in the .docx format because they're color-coded, but plaint .txt files will be there also.
Click to expand...
Click to collapse
Can you give a specific set of steps that cause the problem?
crpalmer said:
Can you give a specific set of steps that cause the problem?
Click to expand...
Click to collapse
I just open any application that uses the rear camera, it sits for about 5-10 seconds, and then that application crashes.
I had this when I flashed to the M5 snap from the M4 as well. Clearing the cache from the camera app fixed it for me.
Sent from my HTC6435LVW using Tapatalk
supertoast92 said:
I had this when I flashed to the M5 snap from the M4 as well. Clearing the cache from the camera app fixed it for me.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I actually had already tried this, but figured I'd give it another shot. No such luck.
Localhost798 said:
I actually had already tried this, but figured I'd give it another shot. No such luck.
Click to expand...
Click to collapse
Hmm...Well, this is taking it a micro-step further, and you've probably already tried this: Along with cache, clear the data. Try force stopping the app first, clearing the cache, then the data, in that order. It shouldn't erase your pictures, but as a precaution I'd back them up first.
Maybe even reflashing the M5 snapshot after that, if that doesn't work, would be worth a shot.
Hearing that you've had problems with the camera on the stock rom though makes me feel uneasy lol...it could be faulty hardware at that point.
supertoast92 said:
Hmm...Well, this is taking it a micro-step further, and you've probably already tried this: Along with cache, clear the data. Try force stopping the app first, clearing the cache, then the data, in that order. It shouldn't erase your pictures, but as a precaution I'd back them up first.
Maybe even reflashing the M5 snapshot after that, if that doesn't work, would be worth a shot.
Hearing that you've had problems with the camera on the stock rom though makes me feel uneasy lol...it could be faulty hardware at that point.
Click to expand...
Click to collapse
Still not working. I am almost convinced that it is hardware related, but before I buy a new sensor, I'll hold out for Android 4.4.3 (the next rumored release in a week or two) as this release will supposedly have many bug fixes. That's probably the last step before I call it a hardware issue.
Localhost798 said:
Still not working. I am almost convinced that it is hardware related, but before I buy a new sensor, I'll hold out for Android 4.4.3 (the next rumored release in a week or two) as this release will supposedly have many bug fixes. That's probably the last step before I call it a hardware issue.
Click to expand...
Click to collapse
Before calling it a hardware problem, I would try a clean flash of the latest CM nightly and if it still happens to post logs.
crpalmer said:
Before calling it a hardware problem, I would try a clean flash of the latest CM nightly and if it still happens to post logs.
Click to expand...
Click to collapse
Already done
And the same problem...
The logs are the same as the ones i posted earlier.
Localhost798 said:
Already done
And the same problem...
The logs are the same as the ones i posted earlier.
Click to expand...
Click to collapse
When you say clean flash do you mean not restoring any apps, etc?
If you have nothing but the ROM and gapps installed and it does this (the logs agree with you that not much happened for 6 seconds then the camera stopped) then it is possibly a hardware problem.
crpalmer said:
When you say clean flash do you mean not restoring any apps, etc?
If you have nothing but the ROM and gapps installed and it does this (the logs agree with you that not much happened for 6 seconds then the camera stopped) then it is possibly a hardware problem.
Click to expand...
Click to collapse
I've tried safe mode, and the problem still exists. To my understanding, this is the same as a clean install because only system and gapps are allowed to run.
Hi,
Hopefully I am writing in the correct place about my issue.
I have the Xperia Z2, rooted, bootloader unlocked, CWM recovery.
I flashed the Unofficial PAC ROM by "rcstar6696" and it works fine with tons of features, my problem is that the phone would not lock securely.
I tried to use PIN, Pattern, Gesture locks and they all do not function, the phone will still unlock with slide.
I tried to reset the phone, same thing. I looked all over the forums and could not find anything about this with Z2.
My friend owns a Nexus 5 and I rooted and flashed PAC ROM onto his phone and the Pattern lock works like a charm.
Is anyone facing the same issue? Any suggestions anyone?
Thanks.
EDIT: I have flashed the latest version from 20th of September cleanly and still facing the same issue.
EDIT: after a few resets and wipes, I noticed that when installing/uninstalling apps. The lock chosen works for a limited time (Usually 6 hours) and then stops randomly.
I am still trying to identify if it's an app causing this.
EDIT: ISSUE SOLVED !!
I reset the device one more time with a clean boot, then while setting it up, I did not connect to my google account. I skipped most of the steps, then set the lock screen, rebooted, added my google account manually.
and VOILA ! phone securely locked.
I do not know how my google account caused this, but it seems to be the reason at the moment.
The port for Z2 may have some bugs so post your problem in the rom thread and the devloper may reply and explain
Envious_Data said:
The port for Z2 may have some bugs so post your problem in the rom thread and the devloper may reply and explain
Click to expand...
Click to collapse
Yes I understand that, and I tried posting it there, apparently I need to have at least 10 posts to post on a developing thread.
GeekyAndroid said:
Yes I understand that, and I tried posting it there, apparently I need to have at least 10 posts to post on a developing thread.
Click to expand...
Click to collapse
Oh... Let me call the dev via mention
@rcstar6696
Care to come and help?
Envious_Data said:
Oh... Let me call the dev via mention
@rcstar6696
Care to come and help?
Click to expand...
Click to collapse
Thank you Envi, Hopefully @rcstar6696 will come respond soon.
I've been using pac rom since its release, I have no issue setting any lockscreen security. Pattern, pin etc all work for me, it has to be either a setting or xposed module causing the issue
Sent from my Xperia Z2 using Tapatalk
Mr.R™ said:
I've been using pac rom since its release, I have no issue setting any lockscreen security. Pattern, pin etc all work for me, it has to be either a setting or xposed module causing the issue
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
How is pac, i was concidering trying it out
GeekyAndroid said:
Thank you Envi, Hopefully @rcstar6696 will come respond soon.
Click to expand...
Click to collapse
Xposed would cause it, or any mods or tweeaks because pac is framework sensitive which means even simple mods can cause huge issues
Envious_Data said:
Xposed would cause it, or any mods or tweeaks because pac is framework sensitive which means even simple mods can cause huge issues
Click to expand...
Click to collapse
Yes of course, but I just flashed it cleanly and no apps whatsoever (except GApps & Stock) , and still the issue is the same.
I even did not change any of the ROM built-in settings and still, no secure locking.
Oh and trust me, PAC ROM is amazing (if it wasn't for this issue) , made me hate every minute I spent in CM and TouchWiz (on my old S4) :good:
Did you do a complete wipe? I wiped all partitions including media before installing pac.
And yes pac is excellent and perfectly stable, only issues I have is nav bar dpi seems to reset after every reboot, but if I toggle say screen timeout via quick settings it changed to what it should be and active display reboots my phone but I don't use it anyway
Sent from my Xperia Z2 using Tapatalk
Mr.R™ said:
Did you do a complete wipe? I wiped all partitions including media before installing pac.
And yes pac is excellent and perfectly stable, only issues I have is nav bar dpi seems to reset after every reboot, but if I toggle say screen timeout via quick settings it changed to what it should be and active display reboots my phone but I don't use it anyway
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
I'm not sure how to do that, however, I managed to solve it.
And I am facing the same with nav bar and the PACperformance app, it just doesn't stick after reboot.
EDIT: actually, I just tried a few reboots, the nav bar seems to be fine to me, I did however change the icons via "Android L Navigation Bar" found in the xposed downloads. Maybe that caused it to "stick"?
as for the active display, I would like to use it, but I am a pixel maniac, and that feature isn't FHD yet I guess, so I am not using it either for the moment.
GeekyAndroid said:
Thank you Envi, Hopefully @rcstar6696 will come respond soon.
Click to expand...
Click to collapse
Sorry that i answer so late
i haven't see it before
do you have other Problems or an issue ??
Now i wil help you
rcstar6696 said:
Sorry that i answer so late
i haven't see it before
do you have other Problems or an issue ??
Now i wil help you
Click to expand...
Click to collapse
Thanks Mate, everything is working fine now.
Anyone tried it out yet http://www.androidorigin.com/samsung-galaxy-s5-galaxy-s4-cyanogenmod-11-nightlies/
kill2010 said:
Anyone tried it out yet http://www.androidorigin.com/samsung-galaxy-s5-galaxy-s4-cyanogenmod-11-nightlies/
Click to expand...
Click to collapse
Actually, a lot of people have tried it. Look in the Unified Development thread. Myself, I use it as a daily. I have minor bugs, but that's either due to it being an experimental build or that i'm essentially dirty flashing daily. One of these days I'll probably clean-wipe to see if the issues persist.
Camera: Google Camera FC's and disconnects when taking too many photos in succession. I think it happens mostly when using HDR. I installed PA Gapps (4.4.4) so the issue could be there.
Dialer: When switching to keypad, everything appears white on white. I have to swipe down (returning to favorites) then select dialer again to view keypad correctly. I have an Android L theme running through the CM11 theme engine, it's possible that's causing the interference.
Dialer: When making outbound calls, sometimes the screen remains black while the call is connecting. I can't hear the phone on the other end ringing. Suddenly, the other person picks up or voicemail answers and the screen comes on showing the contact is live and that I'm in call. Again, the theme I'm running or the fact that I'm dirty flashing could be contributing to this issue.
At some point (probably this weekend), I'll do a backup and full wipe and install CM11 clean with CM's gapps package (which I believe the recommended package is 4.3) to see if those issues persist. I don't consider any of them to be major since the functionality of the phone isn't exactly impaired.
Christopher3712 said:
Actually, a lot of people have tried it. Look in the Unified Development thread. Myself, I use it as a daily. I have minor bugs, but that's either due to it being an experimental build or that i'm essentially dirty flashing daily. One of these days I'll probably clean-wipe to see if the issues persist.
Camera: Google Camera FC's and disconnects when taking too many photos in succession. I think it happens mostly when using HDR. I installed PA Gapps (4.4.4) so the issue could be there.
Dialer: When switching to keypad, everything appears white on white. I have to swipe down (returning to favorites) then select dialer again to view keypad correctly. I have an Android L theme running through the CM11 theme engine, it's possible that's causing the interference.
Dialer: When making outbound calls, sometimes the screen remains black while the call is connecting. I can't hear the phone on the other end ringing. Suddenly, the other person picks up or voicemail answers and the screen comes on showing the contact is live and that I'm in call. Again, the theme I'm running or the fact that I'm dirty flashing could be contributing to this issue.
At some point (probably this weekend), I'll do a backup and full wipe and install CM11 clean with CM's gapps package (which I believe the recommended package is 4.3) to see if those issues persist. I don't consider any of them to be major since the functionality of the phone isn't exactly impaired.
Click to expand...
Click to collapse
Link?
kill2010 said:
Link?
Click to expand...
Click to collapse
http://download.cyanogenmod.com/?device=klte&type=
Christopher3712 said:
http://download.cyanogenmod.com/?device=klte&type=
Click to expand...
Click to collapse
I tried it. Wasn't crazy about a number of things, especially the camera app, which I use often for work.
jon123nyc said:
I tried it. Wasn't crazy about a number of things, especially the camera app, which I use often for work.
Click to expand...
Click to collapse
It's obviously a nightly, no point in complaining knowing things were going to be broken
Sent from my SM-G900T using XDA Free mobile app
where is the changelog for the nightlies ?
gdmlaz said:
where is the changelog for the nightlies ?
Click to expand...
Click to collapse
http://www.cmxlog.com/11/klte/
daxecutioner24 said:
It's obviously a nightly, no point in complaining knowing things were going to be broken
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
I said I didn't like it, not that it didn't work. also, complaints tend to be unsolicited. Otherwise they are opinion. Sorry if you didn't like mine.
jon123nyc said:
I said I didn't like it, not that it didn't work. also, complaints tend to be unsolicited. Otherwise they are opinion. Sorry if you didn't like mine.
Click to expand...
Click to collapse
It's alright, I forgive you
Sent from my SM-G900T using XDA Free mobile app
Hi,
I just got the new update B330 at Today (this is the official ota, not the beta version). And now sometimes the fingerprint scanner doesn't work when i want to unlock the phone. Sometimes it is working, but... Somebody else recognised this problem? Any idea how to fix it?
For all my opinion is worth, I thought the fingerprint scanner was fast before but since I have upgraded to B330 today I have not had a problem with it. I would go as far to say its possibly a little quicker.
Morelight said:
Hi,
I just got the new update B330 at Today (this is the official ota, not the beta version). And now sometimes the fingerprint scanner doesn't work when i want to unlock the phone. Sometimes it is working, but... Somebody else recognised this problem? Any idea how to fix it?
Click to expand...
Click to collapse
I had this problem on B180 - I deleted the fingerprint, and added it back in, and it was fine.
lybad said:
I had this problem on B180 - I deleted the fingerprint, and added it back in, and it was fine.
Click to expand...
Click to collapse
Thanks for the advice, but unfortunately it doesn't work. I deleted and reinstalled my fingerprints, but the bug is still there.
boroleigh said:
For all my opinion is worth, I thought the fingerprint scanner was fast before but since I have upgraded to B330 today I have not had a problem with it. I would go as far to say its possibly a little quicker.
Click to expand...
Click to collapse
In this case probably the problem is in my device. By the way i sent an email to the official support with my bugriports and now i just hope the best.
Thanks for the answer.
Morelight said:
In this case probably the problem is in my device. By the way i sent an email to the official support with my bugriports and now i just hope the best.
Thanks for the answer.
Click to expand...
Click to collapse
I don't think so... rollback to previous version and see if scanner is working. If its working then problem is wit software
Hey!
my problem with the fingerprint is cux its slow now when i was in LilliPopp its was so fast but now when im in MM its slow!! anyone have the same problem?
I have it too. Do not worry. Probably because EMUI is a bit slow in response sometimes. Fingerprint is affected and also sometimes "desktop". Yes EMUI has some bugs.
I read that India got B431 that fixes some things, including fingerprint. Not as fast as for EMUI 3.1, but close enough.
Same for me. Sometime work fine and unlock device sometime didn't work. But i found that it reconize the finger because it doesn't vibrate to said finger wrong. I read somewhere that could be a problem with the sleep mode
It's a bit weird, but maybe i fixed it. So i just switched on this option inside of the developer options: Use legacy DHCP client. I just switched on and now it looks like working as well. My theory is the new DHCP client does not fully compatible with the EMUI, and making bugs in the system.
Same issue here : slow fingerprint read.
t-ph said:
Same issue here : slow fingerprint read.
Click to expand...
Click to collapse
Did you try what i wrote in my last comment here?
Legacy DHCP client was on from the start, but still it's same. On or off, same.
Sent from my Huawei Honor 7
Morelight said:
Did you try what i wrote in my last comment here?
Click to expand...
Click to collapse
Yep, no difference [emoji20]
t-ph said:
Yep, no difference [emoji20]
Click to expand...
Click to collapse
This is weird. In this case, i have no idea, what i did, but it worked :S Because now my device is working as well including the fingerprint scanner.
Morelight said:
This is weird. In this case, i have no idea, what i did, but it worked :S Because now my device is working as well including the fingerprint scanner.
Click to expand...
Click to collapse
Now I disabled all animations in developer settings. Now fingerprint scan feels much faster. Maybe placebo maybe real. Try and see if helps you.
Rollback to 180 it's insane to use the fingerprint so slow
I wanna ask, where is the option to use the fingerprint scanner to be a 'back' button? I'm on B330
there is no such thing anymore
Return/Back function with fingerprint
Hi
I also have a problem with the fingerprint but it's only with the "back/return" function...
It's doesn't work and I didn't found the option to activate or unativate it :/
It was so practice.
I have the B330 Android 6.0 :laugh:
Thank you
---------- Post added at 03:11 AM ---------- Previous post was at 03:07 AM ----------
alteristkang said:
I wanna ask, where is the option to use the fingerprint scanner to be a 'back' button? I'm on B330
Click to expand...
Click to collapse
I didn't found this... Maybe they removed the option.
I hope not !
I use Google Photos as my default photo app. Whenever I tap something -
1. image is loaded
2. half second
3. boosted/corrected image is loaded
It's rather annoying, especially when I'm on Display > Image Quality Settings > Standard mode.
I also have Auto Creator Mode off.
Does this happen to anyone else?
Yes is happening to me, just tried. Didn't notice before because I use album app. It's really weird and annoying
Right, thanks for letting me know. It's apparently a bug in Google Photos itself. Not a phone issue.
I sent a mail to the google support, but well, it's really weird since after reinstalling the app, it does well for some times and then the bug appears out of nowhere.
Can confirm it's definitely the app. Revert back to the previous version, and the issue no longer exists.
Thanks guys, it's definitely a pain but very obvious
Hildr said:
I sent a mail to the google support, but well, it's really weird since after reinstalling the app, it does well for some times and then the bug appears out of nowhere.
Click to expand...
Click to collapse
this apparently applies to all devices on sd855 using google photos.
the links must be translated, sumahoinfo being in Japanese: https://sumahoinfo.com/post-33650
rhug0323 said:
Can confirm it's definitely the app. Revert back to the previous version, and the issue no longer exists.
Click to expand...
Click to collapse
The problem is when will it fix. It's been a long time since this issue occurred.
JalenHo said:
The problem is when will it fix. It's been a long time since this issue occurred.
Click to expand...
Click to collapse
I just stopped the auto update and after de-activating reactivating the photo app, I didn't updated it. Bim, fixed. I don't even know what are the changes with all those updates without a proper patch note.
Update google photos has fix the bug
Sori still have that symptom