Hi guys,
LG G4 would be greatful for me, I like much its specifications, I think it would be my perfect device: microSD support, removable battery, good hardware (G3 is still enough for me).
I want it! It sounds like an improved version of my G3: more color fidelty and screen brightness, no more weak digitizer, outstanding camera...
Why I won't to spend for SGS7 Edge? Because I like modding, I like CM and AOSP roms, I can't accept to live with stock firmware, even if rooted or derivated.
However... I know that it's suffering bootloops: after an unspecified usage time, an hardware component make device unbootable, phone need to be sent in warranty or repaired manually (no, I'm too afraid).
Now I'm asking you, what's your experience regarding bootloop issues?
Please specify also if you've bought device BEFORE or AFTER March.
The Pixel XL seems to have almost identical hardware: a 1440p screen, a SD 821 (which is just a 820, isnt it?), 4GB Ram...
So why is the 10 not "Daydream" ready? Are there sensors lacking?
Elthy said:
The Pixel XL seems to have almost identical hardware: a 1440p screen, a SD 820, 4GB Ram...
So why is the 10 not "Daydream" ready? Are there sensors lacking?
Click to expand...
Click to collapse
I think it's related to AMOLED and refresh rate or something. I think technically the 10 can perform more less fine for daydream but it wouldn't be as immersive as Google would like associated with it.
https://www.google.com/amp/amp.androidcentral.com/google-reveals-hardware-requirements-daydream-vr
So maybe it's the lack of nougat or because not every hardware revision can handle constant 60 fps. Tianama (or something) locks in at like 58/59 fps.
Is it still compatible? If i dont care for 59fps instead of 60?
Or would the software refuse to run?
I don't have the intimate knowledge of some behind the scene, but my understanding after the stuff launched was that it wasn't a special sensor issue, that was one of the advantages of the google VR stuff over the Samsung (or disadvantages, if you're a Samsung person with all the accessories).
Have we received confirmation that after the nougat update, the 10 will be incompatible? It's quite possible it will be for other reasons, just sharing what my understanding was after looking into some of the Pixel and Daydream things, kind of spitballing/bench racing.
Display response time mainly. OLED response time is practically non-existant and since we don't have an OLED display.. Well there you go.
Elthy said:
The Pixel XL seems to have almost identical hardware: a 1440p screen, a SD 821 (which is just a 820, isnt it?), 4GB Ram...
So why is the 10 not "Daydream" ready? Are there sensors lacking?
Click to expand...
Click to collapse
Let's wait for N and find out. If htc don't include it then it may hit the battery which will mean most who adopt it won't keep it.
The amoled screen means that the black is 0% screen usage or very close to, the htc doesn't have that black due to screen type so might be why.
Would be nice to see a proof of concept but if it hits the battery it won't stay. My friends LG has it and it's quite cool for peeking. Guess we'll find out. Did cm have it??
Just an FYI. I've been using my HTC 10 running an aosp slim build with a daydream vr for a couple of weeks. It does work. No lag but it gets really hot. I think all present phones do, its not an issue with the HTC 10.
Followed these directions. A simple edit to and XML file does the trick.
https://www.reddit.com/r/Android/comments/5hno6u/got_daydream_to_work_on_my_5x_might_work_on_other
Sent from my HTC 10 using XDA-Developers Legacy app
I've bought my mom a Pixel XL a few months ago, and over the recent months she complained it handles touches on places she didn't touch.
I've investigates it, and make it short and say it does occur, and I even found a way to reproduce it : scroll in settings screen till it occur.
Made a video about it too:
https://drive.google.com/file/d/1JCsTuMDvMNHh0CO7sF7yoLFT26uNIhUp/
Does anyone know of this issue?
I've read on some places that this is a known issue on Android 8.1, but is it true here too?
Maybe an update to Android P or downgrade to Android 8.0 will fix it?
Hello everyone,
Big problem for the touch screen which is not working fine in a large area, we can clearly see it on the screen recording.
I have already done a factory reset (for another reason), the problem is still here.
I'm not an expert but i guess this is not a problem software can fix?
Thanks for your answers ^^.
EDIT: it's not happening 100% of the time, but when it does, it's a pain in the brain.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Poco has acknowledged the issue and will send a OTA update to fix the issue next patch.
Poco F3 delayed touch response to get optimized in next monthly update
Xiaomi executive says Poco F3/Redmi K40 delayed touch response in CoD & PUBG is set to get optimized in next monthly update.
piunikaweb.com
Edit:
I feel most if not all of these software issues will get ironed out with the roll out of MIUI 12.5 for the Poco F3/Redmi K40.
Here are a list of the current issues:
- Overheating/false temperature report with apps the heavily utilize the GPU causing the screen to dim.
- Touch response delay.
- Uneven brightness slider, 300 nits at 85% while the rest of the 15% covers approximately 250 nits.
- 3rd party launcher gestures.
- DC dimming support, it's available in the developer options for Beta firmware but it's not stable according to Xiaomi.
- Screen tint at lower brightness levels (not isolated to Xiaomi phones, it's an OLED thing), can only be reduced with future updates.
- Low volume with 3.5mm adapter, has been improved with the latest update.
- Some phones taking longer to charge, not the less than 1 hour advertised charge times.
Nemix77 said:
Poco has acknowledged the issue and will send a OTA update to fix the issue next patch.
Poco F3 delayed touch response to get optimized in next monthly update
Xiaomi executive says Poco F3/Redmi K40 delayed touch response in CoD & PUBG is set to get optimized in next monthly update.
piunikaweb.com
Click to expand...
Click to collapse
Hi, thanks for your answer,
The problem in my case is that an area of the touchscreen is completely unresponsive.
The specific area is shown in the screen recording that i have joined with my post. ^^
I'm just waiting to order my Poco F3.
Xiaomi banned shipping to North America due to pandemic, at first I thought it was because of Trump's ban.
I want to see how the phone runs on Xiaomi.EU firmware which is based on the latest China firmware.
My hopes is it runs better than the Gobal firmware and MIUI 12.5 will fix up the rest of the problems when it's rolled out for the phone.
Currently, there's not other phone that has better value and specs for the price in 2021.
Nemix77 said:
I'm just waiting to order my Poco F3.
Xiaomi banned shipping to North America due to pandemic, at first I thought it was because of Trump's ban.
I want to see how the phone runs on Xiaomi.EU firmware which is based on the latest China firmware.
My hopes is it runs better than the Gobal firmware and MIUI 12.5 will fix up the rest of the problems when it's rolled out for the phone.
Currently, there's not other phone that has better value and specs for the price in 2021.
Click to expand...
Click to collapse
Dude, all of that is so true, but could you bring it to a general post, i'd like to only discuss the specific problem of my device here, thanks .
Well... It seems that the issue is not here 100% of the time, i've shut down the device and now the problem is at least momentarily gone (but it was still there after a factory reset ) perhaps it doesn't happen all the time but when it does it's always located in the same area though, so it's still possible that my device has a physical problem instead of just a software problem .
First time I hear of such issue. Have you tried to swipe that areas while charger plugged/unplugged? Sometimes the current make phones behave less responsive.
You must take under consideration apps you installed, miui optimization, launcher... screen protection. Try to switch view to horizontal and see what happens.
If I were you I would try to replace the phone if the issue can't be solved softwarely. As you said it works after reboot - hardware could not randomly pick that moment to work back again.
Seems like a software issue because the recording software is detecting the touches but the UI is not responding to them
If it was a hardware problem, the recording software should not be able to detect the touches as well.
ApexPrime said:
If it was a hardware problem, the recording software should not be able to detect the touches as well.
Click to expand...
Click to collapse
obviously, hehe, that's the first thing to take under consideration
Seems to me most if not all of the problems on the Poco F3 are software/chipset optimization related.
I'm very anal about these things, this is why I avoided the Samsung S20 FE last year (hardware related ghost touches).
Been searching online for weeks now while I'm waiting to place my order for phone about issues, reviews and first impressions.
Did you remove the plastic screen protector it came with? Some people solved this issue by removing that.
I'm using poco from Wednesday. Today right after I added the previous post I encountered this bug for the first time. How ironic. My down-left side of screen was inactive like in your example. Heck if I know what was that but reboot solved that. It was shortafter I got notification about mi screen recording app update. Coincidence? It looked like there was some invisible windows which covered some part of screen. Maybe this floating window mode I'm not familiar with too much.
I hope its a software issue but i bought a s20 fe and the phone was awesome but the problem was with the digitizer and i waited for 4 to 5 months as Samsung claims it was a software issue but actually it was a bad hardware.
Im experiencing exactly the same problem with my newly-bought POCO F3... seems they haven't fixed it yet after all........(..)
Has anybody found any definitive fix for this issue?
Nemix77 said:
Poco has acknowledged the issue and will send a OTA update to fix the issue next patch.
Poco F3 delayed touch response to get optimized in next monthly update
Xiaomi executive says Poco F3/Redmi K40 delayed touch response in CoD & PUBG is set to get optimized in next monthly update.
piunikaweb.com
Edit:
I feel most if not all of these software issues will get ironed out with the roll out of MIUI 12.5 for the Poco F3/Redmi K40.
Here are a list of the current issues:
- Overheating/false temperature report with apps the heavily utilize the GPU causing the screen to dim.
- Touch response delay.
- Uneven brightness slider, 300 nits at 85% while the rest of the 15% covers approximately 250 nits.
- 3rd party launcher gestures.
- DC dimming support, it's available in the developer options for Beta firmware but it's not stable according to Xiaomi.
- Screen tint at lower brightness levels (not isolated to Xiaomi phones, it's an OLED thing), can only be reduced with future updates.
- Low volume with 3.5mm adapter, has been improved with the latest update.
- Some phones taking longer to charge, not the less than 1 hour advertised charge times.
Click to expand...
Click to collapse
Hello
The green tint on poco f3 can be minimaized only by a update software?
Lucyferyna said:
Im experiencing exactly the same problem with my newly-bought POCO F3... seems they haven't fixed it yet after all........(..)
Has anybody found any definitive fix for this issue?
Click to expand...
Click to collapse
I just bought it two days ago, and happened to me on the bottom right side. The phone received an update, but problem is still there.
I have a new UK F3 (Amazon Prime Day sale), and it updated to 12.5.1 as soon as I turned it on (basically) - and it has the same "dead" area of the touch screen.
It's not just "dead", but touches 'avoid' it, and will jump over it.
I turned of dev options and touch tracking to highlight this.
Both images were a single finger swipe from left to right.
Switched from 120hz to 60hz. rebooted. No change. Back to 120hz. rebooted. No change.
This last photo is the most unusual - this was a single straight line from top right to bottom left.
Mine is from UK Amazon also, 12.5.1, no dead areas. No screen protector though.
TheDMV said:
I have a new UK F3 (Amazon Prime Day sale), and it updated to 12.5.1 as soon as I turned it on (basically) - and it has the same "dead" area of the touch screen.
It's not just "dead", but touches 'avoid' it, and will jump over it. View attachment 5352615View attachment 5352617
I turned of dev options and touch tracking to highlight this.
Both images were a single finger swipe from left to right.
Switched from 120hz to 60hz. rebooted. No change. Back to 120hz. rebooted. No change.View attachment 5352621
This last photo is the most unusual - this was a single straight line from top right to bottom left.
Click to expand...
Click to collapse
Try a factory reset (you did a major firmware upgrade). If that doesn't get it, send it back.
Well, been wanting to get a bigger screen AMOLED phone, to replace my View20.
I tend to keep my phones a long time, and I'm not so much a gamer. On a phone, that is
Red Magic 6 (non pro-version) to my eyes seems to be about the best "Bang For Buck" phone, with top of the line CPU & GPU. And a big AMOLED screen... I'd pretty much would put €600 to be the limit for price.
Support and bugs seem to be kinda the point, which still keeps me thinking. I was going to get Xiaomi Redmi Note 10 Pro. As it's €279 now here for a limited time... Then again, it has a smaller display and much weaker CPU/GPU... On that front, it's even slower than my View20...
Decisions, decisions...
What do the people here think about this dilemma?
the screen brightness only 630nits, it is not enough for using outdoor
and the ROM have many bug
chowsingsing9527 said:
the screen brightness only 630nits, it is not enough for using outdoor
and the ROM have many bug
Click to expand...
Click to collapse
Well, my View20 has: "The panel maxed out at 479 nits regardless of whether auto-brightness is enabled or not".
So it's quite much brighter than that, and it hasn't been a problem for me, even with View20.
Bugs are the things, that I'm more concerned with. Also, at the price, are there better phones. With big AMOLED displays?
MSuomi said:
Well, my View20 has: "The panel maxed out at 479 nits regardless of whether auto-brightness is enabled or not".
So it's quite much brighter than that, and it hasn't been a problem for me, even with View20.
Bugs are the things, that I'm more concerned with. Also, at the price, are there better phones. With big AMOLED displays?
Click to expand...
Click to collapse
To give you an idea of how buggy it is, I bricked mine doing a manual update with the software the OEM provided because the phone wouldn't pick up the update on its own.
Also, you can't change the home launcher without root and notifications are unreliable on the lock screen
CyberWolf92 said:
To give you an idea of how buggy it is, I bricked mine doing a manual update with the software the OEM provided because the phone wouldn't pick up the update on its own.
Also, you can't change the home launcher without root and notifications are unreliable on the lock screen
Click to expand...
Click to collapse
Yeah, that doesn't sound very good...
CyberWolf92 said:
Also, you can't change the home launcher without root and notifications are unreliable on the lock screen
Click to expand...
Click to collapse
I just received mine and that is false. You might not be able to use gestures, but you can change the launcher. You need to change it in the default apps. It doesn't work the normal way when opening a new launcher, but there is a way still without root.
I just use it for a month and I didn't face any issue with the latest update. It was pushed automatically via OTA. Previously, i also tried the software update version on their official website by downloading the correct version based on my region. Everything was successfully fine and it is working like the first day i was unboxing the phone.