To me this is exciting news, what are your thoughts?
Source: androidpolice
Mmh, little bit disappointed?
End of next week the beta? When will roll out official then? End of February?
That means the touchscreen latency will not be fixed till then.
maybe they do not have any solution for the touch input lag.
Sent from my PH-1 using Tapatalk
stryver said:
To me this is exciting news, what are your thoughts?
Source: androidpolice
Click to expand...
Click to collapse
Im not even mad. Oreo beta 3 works fine for me only issue is the signal bars going mad ( not actually effecting signal)
Either way it's a good choice 8.1 is a more significant update than 8.0 was.
I'm glad that they are so open about their development. I love this phone I'm in Beta3 rooted with all the Magisk modules I wanted working.
B3 working well for me. No root.
Lately we had all sort of rushed software going out with all sorts of problems. Apple, Intel and so on.
I rather wait for a quality version than have something rushed out of the door because someone in marketing decided it was a good idea or because of impatience.
I'm happy that they're skipping 8.0. PH-1 isn't the only phone that has had issues with 8.0. I'd rather they take their time and get a good stable build, than release some buggy **** that disappoints. I'm also on Beta 3 running AOSiP 8.1. It's pretty great.
From a software build perspective it's not a big deal to go straight to 8.1. Kind of silly not to.
Sent from my PH-1 using XDA Labs
To me it's not exciting news, because as someone else mentioned it means any possible fixes for the touchscreen problems are going to be further delayed. I will be happy to be proven wrong, but the skeptic in me thinks that this is just a delaying tactic because Essential still does not have fixes for the touchscreen ready yet. They know by shifting the release target to 8.1 they are giving themselves a lot more time to get things sorted out, as now I'm sure there are going to be multiple 8.1 beta releases. Their problem was that there were already three 8.0 betas released, and I think everyone was expecting that the 8.0 final would be coming next. But if Essential releases a final Oreo build with the touchscreen issues still present, it's really going to be bad for the company. By switching to 8.1 they have given themselves a few more chances to fix the touchscreen before a non-beta release comes.
Whats wrong with the touch screen? I took off the screen protector I was using it has been night and day. Feels more responsive with one not installed
Sent from my PH-1 using Tapatalk
chereko said:
To me it's not exciting news, because as someone else mentioned it means any possible fixes for the touchscreen problems are going to be further delayed. I will be happy to be proven wrong, but the skeptic in me thinks that this is just a delaying tactic because Essential still does not have fixes for the touchscreen ready yet. They know by shifting the release target to 8.1 they are giving themselves a lot more time to get things sorted out, as now I'm sure there are going to be multiple 8.1 beta releases. Their problem was that there were already three 8.0 betas released, and I think everyone was expecting that the 8.0 final would be coming next. But if Essential releases a final Oreo build with the touchscreen issues still present, it's really going to be bad for the company. By switching to 8.1 they have given themselves a few more chances to fix the touchscreen before a non-beta release comes.
Click to expand...
Click to collapse
PUT THE MAGNIFYING GLASS DOWN...
If you don't pay attention to this "touch jitter," it's just not there...
Sent from my PH-1 using Tapatalk
rignfool said:
PUT THE MAGNIFYING GLASS DOWN...
If you don't pay attention to this "touch jitter," it's just not there...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I think is not about magnifying the issue.
The touchscreen issue is quite obvious when one try to tap the screen with the phone on a flat surface.
rignfool said:
PUT THE MAGNIFYING GLASS DOWN...
If you don't pay attention to this "touch jitter," it's just not there...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
yeah I agree, and I don't even like this phone. But the jitter thing was a bit overblown.
Um yeah, my comment has nothing to do about scrolling. It has to do with the fact that, several times a day, my phone's touchscreen becomes wildly unresponsive and does not register most touches. I then have to lock the phone and unlock it again to be able to type properly. This is a well-documented issue with this phone unless you've been living under a rock (or don't look at reddit, which has much more active of a community than XDA for this device).
There will be monthly security released for 8.0 and 8.1 betas until an official goes out.
Sent from my PH-1 using XDA Labs
I am not sure what the jitter thing is, but I am hoping that we get official Oreo soon and fix the bugs that are there...
Only issue that bothers me is the crazy ghost touches registering every blue moon. A reboot fixes it, but it happens here and there still.
stryver said:
Only issue that bothers me is the crazy ghost touches registering every blue moon. A reboot fixes it, but it happens here and there still.
Click to expand...
Click to collapse
When i get those all i do is wipe the screen off and it goes away.....
chereko said:
Um yeah, my comment has nothing to do about scrolling. It has to do with the fact that, several times a day, my phone's touchscreen becomes wildly unresponsive and does not register most touches. I then have to lock the phone and unlock it again to be able to type properly. This is a well-documented issue with this phone unless you've been living under a rock (or don't look at reddit, which has much more active of a community than XDA for this device).
Click to expand...
Click to collapse
Yes, this ^
I've been having this issue since day one. I've tried factory resets to no avail. It happens with stock launcher 3 and nova prime. I'm not rooted and now running ob3. The problem has persisted and I'm quite disappointed. I'm ready to pack it in and go to another device. I hate giving up on something but I believe that this phone was a mistake for me to purchase. It's a real shame because there is a lot of potential here and who doesn't love the simplicity and weightlessness of stock Android. Just my 2¢
Related
Just wondering what people's experiences are so far with the physicalilty of the device. I really like the way it feels and fits in my hand, with the keyboard open and in landscape mode. Also love the feel of the keyboard, tho i might change a couple things in the key layout.
The one thing i'm seeing is my keys are already getting quite scuffed, perhaps from being pressed with my thumbnails? A few of the printed letters are wearing down and i'm afraid i won't be able to see them after not too much longer! Is anyone else seeing this?
Other than that, the overall build quality is ok, maybe a tad cheap-ish(?), but i like it. In some ways it could be my favorite qwerty phone yet.
Physically the phone is solid. Mentally.. not so much.
Agreed on the mental instability bit.
The things my Photon would do, but not limited to:
1. Notifications go into the ether (don't pop up in notification bar)
2. Apps that go fullscreen will sometimes cause the nav/status bar to black out
3. Vibrate completely at random
4. Take 5 minutes to unlock
5. Regularly see my SD card as "corrupted"
6. Autopunctuation fails at random
And that's all I can remember off the top of my head. It seems to have some real crazy quirks. Hoping CM10 makes it better.
Xodium said:
5. Regularly see my SD card as "corrupted"
Click to expand...
Click to collapse
...YES...and now is my 32GB SD definitely dead
For me is this problem only with 32GB cards.16GB works fine.
I forgot to mention, the touchscreen seems a bit wonky to me.... Not very responsive, gotta press a few times sometimes to open an app, and it sorta freaks out sometimes and doesn't swipe from side to side and opens stuff i didn't mean to open. I had a Moto Cliq 2 and had similar touchscreen issues.
I think CM10 would be great on this device, we oughta get cracking on that build. I don't know for sure, but I'd be surprised if we ever got official support from the CM team.
yogi2010 said:
I think CM10 would be great on this device, we oughta get cracking on that build.
Click to expand...
Click to collapse
Done.
Now to get it functional...
I still think we should focus on CM9, then worry about getting 10. But that's just me...
arrrghhh said:
Done.
Now to get it functional...
I still think we should focus on CM9, then worry about getting 10. But that's just me...
Click to expand...
Click to collapse
Sounds good to me, we do have ICS source, right? How come the source download is only a few MB tho? Did they just release the drivers, and you gotta add them in to the rest of the code?
yogi2010 said:
Sounds good to me, we do have ICS source, right? How come the source download is only a few MB tho? Did they just release the drivers, and you gotta add them in to the rest of the code?
Click to expand...
Click to collapse
Moto released the kernel source, they are under no obligation to release userland source.
I have gotten CM9 booting, but not much else. Interloper didn't have the device and was working on CM10... it never booted. I'm hoping he'll make some progress with the device in his hands.
arrrghhh said:
Moto released the kernel source, they are under no obligation to release userland source.
I have gotten CM9 booting, but not much else. Interloper didn't have the device and was working on CM10... it never booted. I'm hoping he'll make some progress with the device in his hands.
Click to expand...
Click to collapse
For fun i have built an HTC kernel or two, and the source downloads were always almost 100 MB tho, so i was confused when i looked at our source, haha. I'm not real experienced tho.
From what i hear, getting it to boot is a huge part of it, so that's great. Hopefully we'll get further along soon!
yogi2010 said:
For fun i have built an HTC kernel or two, and the source downloads were always almost 100 MB tho, so i was confused when i looked at our source, haha. I'm not real experienced tho.
From what i hear, getting it to boot is a huge part of it, so that's great. Hopefully we'll get further along soon!
Click to expand...
Click to collapse
The actual kernel source is something like 2gb uncompressed on my machine...
arrrghhh said:
The actual kernel source is something like 2gb uncompressed on my machine...
Click to expand...
Click to collapse
Ah yes, i see it now lol. Had gone to the wrong link before.
CornholioGSM said:
...YES...and now is my 32GB SD definitely dead
For me is this problem only with 32GB cards.16GB works fine.
Click to expand...
Click to collapse
64GB cards do this as well.
I have a fix: Go to a Mac (haven't tested this on PC) and have Disk Utility repair the SD card. Twice for good measure. Usually clears it right up. It's annoying when it happens and I'm nowhere near my computer, though.
arrrghhh said:
Moto released the kernel source, they are under no obligation to release userland source.
I have gotten CM9 booting, but not much else. Interloper didn't have the device and was working on CM10... it never booted. I'm hoping he'll make some progress with the device in his hands.
Click to expand...
Click to collapse
They have a 3 month obligation before they violate the GPL for every kernel/software update.
The phone has some issues but so did my evo shift to a certain extent which is why I was re-flashing ROMS all the time. Go to any phone forum and there are always bugs
- I only have the weird touchscreen problems, that someone mentioned above, only when the phone is charging. A little weird. if I overtax the phone i can cause some hangups. I blame Android more than the touchscreen or processor.
- I'm in and out of cell service alot because of the location of my job. I've been blaming that for the fact that notifications come at weird times and out of order. When I'm in service all the time, notifications seem pretty solid.
- The physical keyboard seems to double-type occasionally, but overall I'm ok with its performance. Keyboard slide out mechanism is good, where on my evo shift I thought was a bit too..."loose"?
- I have the wifi drop problem that someone mentioned in another thread. I blame software on that as well. Maybe the next patch will get it right. These companies are just trying to push phones out the door these days. Remember when video games couldn't be updated over internet and how solid they were out the box? Nowadays, everything needs OTA patches at some point. Shame, but I digress.
- camera could be WAY better (auto-focus, poor lighting scenarios). This may be my biggest complaint, because this should be solid out the box given how far phone cameras have come. How long have phones had cameras now? I had a phone camera in 04.
I could give a long list of good physical and software points. Overall I'm really happy. JB would make me happier, but ICS on the Q is pretty darn good.
I have a few scrapes/scratches on my spacebar from sliding the phone open and closed so often, but that's it.
Also, that little oval/dot thing on the left side of the keyboard face of the phone to the left of the number 1, what is that?
Sent from my GT-N8013 using Tapatalk 2
dpwhitty11 said:
Also, that little oval/dot thing on the left side of the keyboard face of the phone to the left of the number 1, what is that?
Click to expand...
Click to collapse
Caps lock indicator.
cmags said:
Caps lock indicator.
Click to expand...
Click to collapse
Is it supposed to light up or something?
Sent from my XT897 using Tapatalk 2
yes bro..it supposed to light on when we activate caps lock key..
Sent from my XT897 using xda premium
cloud_9 said:
yes bro..it supposed to light on when we activate caps lock key..
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Oh. Mine doesn't. Oh well.
Sent from my GT-N8013 using Tapatalk 2
Ever since I updated, my keyboard backlight is no longer "automatic". Have to set it always on because it stops turning on when set on automatic.
Physically, phone is solid.
Somebody has to be working on this. This is getting kinda irritating. Listen to music, flash black lines, watch movies, flash black lines, type notes in supernote, flash blacklines. Not a big deal in terms of performance, just an irritating bother for a $600 tablet!
Sent from my ASUS Transformer Pad TF700T using xda premium
doesn't bother me but I only paid $500 for mine.
lafester said:
doesn't bother me but I only paid $500 for mine.
Click to expand...
Click to collapse
I laughed.
I have them as well, and while I would like them to pack up and leave, I concur with the OP that it is not a deal breaker of any sort.
I can't remember having them on ICS -- would this be a JB thing?
Only happens to me very rarely, only when browsing, once or twice a day at most. Never in games, films, music or documents...
Working on it?-- That implies that they still care about us. They don't. I have almost 50 of these that I support, all have the issue and even after working with Tien and Gary to get a resolution.... they have given me absolutely nothing as far as support goes.
They have suggested cold boots and factory resets... that is all. And NO, those actions fix NOTHING.
Tien... you even abandoned my support call..
Last communication that I had with him was this on 11/7:
Hi Jordan,
Sorry for the late reply, but I just wanted to inform you that we have passed all this information back to HQ so they can test and figure out a solution. I am confident, with all the material we've supplied, that they can duplicate and figure something out. I just want to thank you for sticking through this. Hopefully the new firmware update will address all these issues.
Tien
-----Original Message-----
From: ----
Sent: Sunday, November 04, 2012 6:14 AM
To: Tien Phan (ACI)
Subject: RE: Transformer Infinity Tf700 [ID=RPTM20121019101273-616]
Tien,
I am assuming by now that you or your company has been able to reproduce the graphics issues, reboots and issues that have been happening with the TF700. If you are having trouble with that, there are large groups of users getting these problems, documented here: http://forum.xda-developers.com/showthread.php?t=1811538&page=14
Please let me know what asus plans to do to resolve these issues. Again, these are company machines that are relied on everyday as a primary work space for some. Please email me asap to let me know a time frame that I can expect some sort of resolution.
Jordan
SO-- a month ago was the last response, despite emailing him on 12/1 for an update-- got nothing.
MartyHulskemper said:
would this be a JB thing?
Click to expand...
Click to collapse
Yeah its a JB thing. ICS was fine. I'm sure the fix will be out soon
I was having them, but didn't notice any since the update I got today. I *think* they fixed it... I'm looking for somebody to confirm that I'm not dreaming...
I've never noticed them. When and how do they appear?
acme99 said:
I was having them, but didn't notice any since the update I got today. I *think* they fixed it... I'm looking for somebody to confirm that I'm not dreaming...
Click to expand...
Click to collapse
I confirm, no black flashing lines post 23 update on JB
sbdags said:
I've never noticed them. When and how do they appear?
Click to expand...
Click to collapse
From time to time, a black horizontal line flashes across the screen, usually in the upper third (at least when I noticed), seems to be random. Looks like a GPU driver issue (maybe NVidia's fault?) because it appeared first with the JB updates.
sbdags said:
I've never noticed them. When and how do they appear?
Click to expand...
Click to collapse
Need the display to be mostly white, then just wait. It's real quick maybe 1/4 to 1/2 a second.
I see this once every couple minutes on cleanRom 2.7.x
dishinit said:
I confirm, no black flashing lines post 23 update on JB
Click to expand...
Click to collapse
Good. Then I'm not crazy... I think I saw one... But it's hardly noticeable now. It's way better than before. This is good! Thanks Asus for this one.
acme99 said:
Good. Then I'm not crazy... I think I saw one... But it's hardly noticeable now. It's way better than before. This is good! Thanks Asus for this one.
Click to expand...
Click to collapse
Hardly noticeable?... why can't they just be gone already?!?!
jordanmw said:
Hardly noticeable?... why can't they just be gone already?!?!
Click to expand...
Click to collapse
Well, I'm there with you on this one, but for me it went from unbearable to just annoying. But yeah, there are still there. I just noticed one 2 mins ago.
So thank you Asus, but don't sit on this one yet cause it's still an unresolved issue........
acme99 said:
Well, I'm there with you on this one, but for me it went from unbearable to just annoying. But yeah, there are still there. I just noticed one 2 mins ago.
So thank you Asus, but don't sit on this one yet cause it's still an unresolved issue........
Click to expand...
Click to collapse
Yep, correction on my earlier report of none after 23 update, thought I saw one last night, know I saw one this morning, no developers options ticked.
But frequency and duration greatly reduced....still needs more work though.
I concur with above poster, still not totally resolved
Definitely less than last update, but still there every once in a while.
Thanks for the improvement, but keep looking.
There was an update yesterday?! OMG, I hope CROMI Dev picks it up soon! Its soo irritating. Certain apps seem to trigger it more often than others! I'm using CROMI 2.7.2 .
Sent from my ASUS Transformer Pad TF700T using xda premium
Darksurf said:
There was an update yesterday?! OMG, I hope CROMI Dev picks it up soon! Its soo irritating. Certain apps seem to trigger it more often than others! I'm using CROMI 2.7.2.
Click to expand...
Click to collapse
I'm pretty sure sbdags is applying his magic as we speak. He has a lot to go over, so give it a few days. I do hope the new update remedies it to a large extent, because they are annoying.
The remark of "no developer options ticked" seems to deny me the pleasure of disabling 2D GPU GUI rendering and seeing them leave automagically. I had that idea yesterday evening -- well, I'm going to try anyway. (If it should somehow work out, that'd be a strong lead to suspect a driver issue. Damn you, NVIDIA! )
PS: are we all on CROMI? (Me: v2.7.2) I guess stock ROM is no different to all intents and purposes as far as the black line issue goes. Do any of the people in here that use AOSP/AOKP/CM10 have them too?
My Nexus 7 used to do this as well. I think it's a problem with the Tegra 3 while the wifi is being used. I haven't noticed it on my Nexus 7 since 4.2 though.
yohojones said:
My Nexus 7 used to do this as well. I think it's a problem with the Tegra 3 while the wifi is being used. I haven't noticed it on my Nexus 7 since 4.2 though.
Click to expand...
Click to collapse
Interesting suggestion! I hadn't noticed anuyhthing partiucular in connection with the WiFi being on while the problem occurred. I am curious to see if I can ''fix'' this myself. Anoter workaround for an -- essentially -- hardware issue? (If you are correct, and that carries a rather high probablility, you'd suspect the Tegra3 to be susceptible to some kind of EMF reception and static build-up internally or something,. Ugh, another unsolvable issue to contend with. And still I like this device very much.
I just got an OTA update. The "details" weren't detailed at all... just "improvements to android." This is just a heads up if you want to check for one. I'm also curious if anyone knows if this brings any improvements?
I don't have a wireless charger (Samsung has it and is supposed to be fixing it) but maybe this will fix the wireless charging problem?
Hezzennater said:
I just got an OTA update. The "details" weren't detailed at all... just "improvements to android." This is just a heads up if you want to check for one. I'm also curious if anyone knows if this brings any improvements?
I don't have a wireless charger (Samsung has it and is supposed to be fixing it) but maybe this will fix the wireless charging problem?
Click to expand...
Click to collapse
So far in the Verizon notes it's a security patch only
Verizon Wireless Technician using Tapatalk on Note 5
Are we supposed to be getting anything else soon?
Sent from my SM-N920V using Tapatalk
@Hezzennater, wat's the build no.? If it's oi1 or oi# then most probably it's Samsung Pay update all Samsung devices in US are being treated with right now.
itskapil said:
@Hezzennater, wat's the build no.? If it's oi1 or oi# then most probably it's Samsung Pay update all Samsung devices in US are being treated with right now.
Click to expand...
Click to collapse
Are you referring to the last three numbers?
It's OGJ
Wireless charging is working for me. Just got my phone today and it updated during setup.
Sent from my SM-N920V using XDA Free mobile app
I want to update and enable Samsung Pay and fix the wireless charging but security patches always take away possibility of root etc
I got it and I see the updated kernel, etc.
Still fails the stagefright check!
jes24cap said:
Wireless charging is working for me. Just got my phone today and it updated during setup.
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
On the official samsung wireless not-fast charger?
cpufrost said:
I got it and I see the updated kernel, etc.
Still fails the stagefright check!
Click to expand...
Click to collapse
Stage fright?
Someone in the other thread said they worked for Verizon and that the last update allows for Samsung pay to work, but since they aren't officially supporting it, the last step is Samsung making a special update to give it the feature, somehow not through Verizon?
Everything is hearsay, anecdotal, and annoying. But that's all we've got I suppose.
The update makes the wireless charging worse for me using the older mini charger, it worked fairly well before the update.
Correct, It unlocks the functionality needed for Samsung Pay, Verizon and Samsung are still negotiating official support. Samsung is not willing to activate Verizon members cards until Verizon makes an agreement.
I hesitantly took this update on my Note5, and so far regret it. Everything was running absolutely fine until the update, then things got weird. I get ANRs, which isn't a terrible thing when seldom, but then the lock screen crashed over and over, and wouldn't let me do anything. Also, during the crash, it showed my home screen wallpaper and contents, which I'm pretty sure is a security concern. Anyways, I had to do a hard reset, and it cleared that issue up, but now boot time is significantly longer and the finger print reader is giving me problems. Not once did I have a problem with the finger print reader before the update. I'll look into this and see if anything in my control is causing this instability.
shadolis said:
I hesitantly took this update on my Note5, and so far regret it. Everything was running absolutely fine until the update, then things got weird. I get ANRs, which isn't a terrible thing when seldom, but then the lock screen crashed over and over, and wouldn't let me do anything. Also, during the crash, it showed my home screen wallpaper and contents, which I'm pretty sure is a security concern. Anyways, I had to do a hard reset, and it cleared that issue up, but now boot time is significantly longer and the finger print reader is giving me problems. Not once did I have a problem with the finger print reader before the update. I'll look into this and see if anything in my control is causing this instability.
Click to expand...
Click to collapse
Interesting. I took the update and nothing is wrong for me as far as general day to day tasks go. Fingerprint scanner still works and everything feels just as smooth as before.
Sent from my SM-N920V using Tapatalk
david_hume said:
Interesting. I took the update and nothing is wrong for me as far as general day to day tasks go. Fingerprint scanner still works and everything feels just as smooth as before.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Same here, it runs just as good as the previous build
Mayze23 said:
Same here, it runs just as good as the previous build
Click to expand...
Click to collapse
Ditto, mine is running just as good if not better since the update.
Hezzennater said:
Stage fright?
Click to expand...
Click to collapse
Get Zimperium stagefright detector from the play store and it will show the device is still vulnerable.
Now I'm not having issues like other users but Antutu scores dropped and things like crossy road are unplayable.
If this is how things are to come I'm done. This device was nearly perfect and now not so sure. I'm still in my 14 day period to return this device, may just do that.
More than likely it's due to the new kernel. With a locked bootloader this is impossible for the user to fix.
shadolis said:
I hesitantly took this update on my Note5, and so far regret it. Everything was running absolutely fine until the update, then things got weird. I get ANRs, which isn't a terrible thing when seldom, but then the lock screen crashed over and over, and wouldn't let me do anything. Also, during the crash, it showed my home screen wallpaper and contents, which I'm pretty sure is a security concern. Anyways, I had to do a hard reset, and it cleared that issue up, but now boot time is significantly longer and the finger print reader is giving me problems. Not once did I have a problem with the finger print reader before the update. I'll look into this and see if anything in my control is causing this instability.
Click to expand...
Click to collapse
Weird, I had no issues. Hopefully it was a fluke and it clears up fo ryou.
Also, it seems to be confirmed that the OTA update does allow for Samsung Pay to work. Now we have to wait for the app to be released to the play store.
This is the Tweet from Will Graylin saying, "soon to be down loadable on Google Play for Verizon customers. Hoping in the next week or so."
https://twitter.com/wgraylin/status/648896346297004033
it is so frustrating that they release phones so often with no chance to really refines them. then there is google that puts out versions of android before developers get a chance to master or migrate fully to the latter.
i heard the new storage security in android 11 can cause hiccups like slow loading and crashes due to the new storage activity due to the new security rules.
should i stay on android 10 just like so many stayed on android 4.x.x for so long to keep compatibility
Just look at xda's complaint on scooped storage
https://www.xda-developers.com/android-11-features-developers-new-apis/
gloege said:
it is so frustrating that they release phones so often with no chance to really refines them. then there is google that puts out versions of android before developers get a chance to master or migrate fully to the latter.
i heard the new storage security in android 11 can cause hiccups like slow loading and crashes due to the new storage activity due to the new security rules.
should i stay on android 10 just like so many stayed on android 4.x.x for so long to keep compatibility
Click to expand...
Click to collapse
I'm going to upgrade ASAP, never had any issues with the upgrades and I've been in android since 2009.
update to 11 with no second thoughts
Upgrade. No 2nd thoughts about it.
ggrant3876 said:
I'm going to upgrade ASAP, never had any issues with the upgrades and I've been in android since 2009.
Click to expand...
Click to collapse
Check out the link i put in the original post. Even xda sees scooped storage as a failure. Just scroll down to scooped storage
gloege said:
Check out the link i put in the original post. Even xda sees scooped storage as a failure. Just scroll down to scooped storage
Click to expand...
Click to collapse
I did and as I said I've never had any issues with an update in 11 years. I'm sure Sammy will have it figured out before they release it. All my phones have been rooted until the Note 7, and you take more chance flashing a rom written by some dev than an update from a major player.
ggrant3876 said:
I did and as I said I've never had any issues with an update in 11 years. I'm sure Sammy will have it figured out before they release it. All my phones have been rooted until the Note 7, and you take more chance flashing a rom written by some dev than an update from a major player.
Click to expand...
Click to collapse
But samsung does not work or develop the third party apps or what not that you install on your phone. Any unsupported app you use will likely be crippled(heard that loading times can be 100× longer to start the app) and any dev too aggravated to to fix it may stop supporting his or her project. Also most devs have not even cought up to android 10. Yea i hope to many update and google learns their error in this mess
gloege said:
But samsung does not work or develop the third party apps or what not that you install on your phone. Any unsupported app you use will likely be crippled(heard that loading times can be 100× longer to start the app) and any dev too aggravated to to fix it may stop supporting his or her project. Also most devs have not even cought up to android 10. Yea i hope to many update and google learns their error in this mess
Click to expand...
Click to collapse
If it does happen and I seriously doubt it, I'll just reflash with odin and restore my backup. My glass is half full, not half empty. I have friends on other forums running 11 beta on Pixels with no issues.
Am I in a pixel or oneplus thread? Note 20 ultra users most likely get Android 11 before March 2021 and chances are that any kinks should be ironed out by then. I don't understand why this conversation needs to happen this early.
Edit: https://www.phonearena.com/news/sam...-android-11-update-one-ui-3-t-mobile_id127042
Guess I stand corrected! One Ui 3.0 AKA Android 11 is already in Beta in South Korea and coming to T-mobile according to this article.
Sent from my SM-N986W using XDA Labs
gloege said:
it is so frustrating that they release phones so often with no chance to really refines them. then there is google that puts out versions of android before developers get a chance to master or migrate fully to the latter.
i heard the new storage security in android 11 can cause hiccups like slow loading and crashes due to the new storage activity due to the new security rules.
should i stay on android 10 just like so many stayed on android 4.x.x for so long to keep compatibility
Just look at xda's complaint on scooped storage
https://www.xda-developers.com/android-11-features-developers-new-apis/
Click to expand...
Click to collapse
I will absolutely update as soon as its available. I always sign up for the beta each year to get the update ASAP. Most people complain that Samsung doesn't update fast enough. Haven't heard anyone complain yet that they update TOO fast, LOL.
These concerns happen every year, and they always end up being a non-issue.
As far as app compatibility issues, that's the developers' issues. They are advised long in advance what they need to do to remain compatible with the current OS.
mrnovanova said:
Am I in a pixel or oneplus thread? Note 20 ultra users most likely get Android 11 before March 2021 and chances are that any kinks should be ironed out by then. I don't understand why this conversation needs to happen this early.
Edit: https://www.phonearena.com/news/sam...-android-11-update-one-ui-3-t-mobile_id127042
Guess I stand corrected! One Ui 3.0 AKA Android 11 is already in Beta in South Korea and coming to T-mobile according to this article.
Sent from my SM-N986W using XDA Labs
Click to expand...
Click to collapse
Yup! Sammy has stepped up their update game the last few years. I think last year they were pushing the official Android 10 before the end of the year to some devices. I think, but I could be wrong. I know it was earlier than the previous years.
Mr. Orange 645 said:
I will absolutely update as soon as its available. I always sign up for the beta each year to get the update ASAP. Most people complain that Samsung doesn't update fast enough. Haven't heard anyone complain yet that they update TOO fast, LOL.
These concerns happen every year, and they always end up being a non-issue.
As far as app compatibility issues, that's the developers' issues. They are advised long in advance what they need to do to remain compatible with the current OS.
Yup! Sammy has stepped up their update game the last few years. I think last year they were pushing the official Android 10 before the end of the year to some devices. I think, but I could be wrong. I know it was earlier than the previous years.
Click to expand...
Click to collapse
Guess you just lucked out. But i try not to be the one stuck with a dodgy os. When they updated to android 5 no phone would run my fave application and then the android 5 memory leak. Not to mention other things os updates can bring untill they fix them. And that is googles fault not the phone maker
gloege said:
Guess you just lucked out. But i try not to be the one stuck with a dodgy os. When they updated to android 5 no phone would run my fave application and then the android 5 memory leak. Not to mention other things os updates can bring untill they fix them. And that is googles fault not the phone maker
Click to expand...
Click to collapse
LOL. I don't think I lucked out. I think issues with OS updates are far less common than you think. I'd say you are definitely in the minority.
I've been on Android since the original Moto Droid. I've had almost every Moto, LG, Samsung, Nexus, and Pixel. I've been through beta OS updates, official updates, side loaded updates, unofficial ported updates, you name it.
You're going back 5 YEARS and saying because an update broke your favorite application, that Google/Samsung updates too often? Is every update perfect? No, but they certainly don't break everything the way you think they do.
~
Android updates on Samsung phones are always an anti-climax. Samsung tend to have implemented all the best features that a new Android update brings already. What you end up with is a range of bugs or security features that break your apps. I will always go for the update that's offered but I am not excited about it or bothered if there's a delay in any roll outs.
~
Mr. Orange 645 said:
I will absolutely update as soon as its available. I always sign up for the beta each year to get the update ASAP. Most people complain that Samsung doesn't update fast enough. Haven't heard anyone complain yet that they update TOO fast, LOL.
These concerns happen every year, and they always end up being a non-issue.
As far as app compatibility issues, that's the developers' issues. They are advised long in advance what they need to do to remain compatible with the current OS.
Yup! Sammy has stepped up their update game the last few years. I think last year they were pushing the official Android 10 before the end of the year to some devices. I think, but I could be wrong. I know it was earlier than the previous years.
Click to expand...
Click to collapse
No you are absolutely right. I'm out in Canada and if memory serves me right we got Android 10 at the beginning of January a month or so after the US. It was the years prior that the OS update came out with the S series release. And to your point Samsung has stepped up their game, tremendously. It's right after the Pixels and Oneplus which is not too shabby. And getting faster to boot. No complaints here. :good:
Sent from my SM-N986W using XDA Labs
Mr. Orange 645 said:
I will absolutely update as soon as its available. I always sign up for the beta each year to get the update ASAP. Most people complain that Samsung doesn't update fast enough. Haven't heard anyone complain yet that they update TOO fast, LOL.
These concerns happen every year, and they always end up being a non-issue.
As far as app compatibility issues, that's the developers' issues. They are advised long in advance what they need to do to remain compatible with the current OS.
Yup! Sammy has stepped up their update game the last few years. I think last year they were pushing the official Android 10 before the end of the year to some devices. I think, but I could be wrong. I know it was earlier than the previous years.
Click to expand...
Click to collapse
Yeah, Note10+ got Android 10 in December I believe. Definitely was super fast compared to Note9 getting Android 9 (February/March).
---------- Post added at 01:00 AM ---------- Previous post was at 12:59 AM ----------
apprentice said:
~
Android updates on Samsung phones are always an anti-climax. Samsung tend to have implemented all the best features that a new Android update brings already. What you end up with is a range of bugs or security features that break your apps. I will always go for the update that's offered but I am not excited about it or bothered if there's a delay in any roll outs.
~
Click to expand...
Click to collapse
So true. I read one of the big changes with Android was bubble-like messaging, much like FB Messenger. Uh... I've had that in Samsung for a couple years now I think? My text app always pops up in a bubble instead of the notifications panel.
PsiPhiDan said:
Yeah, Note10+ got Android 10 in December I believe. Definitely was super fast compared to Note9 getting Android 9 (February/March).
Click to expand...
Click to collapse
Thats what I was thinking, but couldn't remember 100%. Unless there's somd major issues, it looks like we're on the same timeline for Android 11, since the beta is already out for the international S20 series. US Note 20 won't be too far behind.
gloege said:
Check out the link i put in the original post. Even xda sees scooped storage as a failure. Just scroll down to scooped storage
Click to expand...
Click to collapse
Spot on. What a wrenched mess.
My 10+ is still running well on Pie.
Google is insane to emulate Apple.
I don't think Google will fix it, another Vista.
Probably stay on Pie for the life of this phone and hope Google regains their sphincter control with 12 or 13...
So true. I read one of the big changes with Android was bubble-like messaging, much like FB Messenger. Uh... I've had that in Samsung for a couple years now I think? My text app always pops up in a bubble instead of the notifications panel.[/QUOTE]
you know you can change/turn that off to get the notification view of it
gloege said:
So true. I read one of the big changes with Android was bubble-like messaging, much like FB Messenger. Uh... I've had that in Samsung for a couple years now I think? My text app always pops up in a bubble instead of the notifications panel.
Click to expand...
Click to collapse
you know you can change/turn that off to get the notification view of it[/QUOTE]
I saw that too, wtf? Messenger does that all the time with Pie.
Lol, half of the time I disable it because it's a nuisance.
I've backed up all my Playstore apps with APK Export because of them either being taken down in Playstore or turned into a bloody mess to adapt to 10/11.
I also have a couple trusted apps the use overlays, Q would render them useless or a pain to use.
I remember the horror of Vista and Lollipop... Pie is running very well, WYSIWYG
The most I'll do for now is an occasional reload of Pie if needed. All my data including the all apks/system updates are stored on my SD card so reloads are much easier. No screwing around with or waiting for Playstore. Any app that allows it's setup to be exported is also saved there.
With over 230 GB of data it saves a lot of time coping it from the laptop too.
I never have a phone without an SD card slot... you know like an Apple.
I saw that too, wtf? Messenger does that all the time with Pie.
Lol, half of the time I disable it because it's a nuisance.
I've backed up all my Playstore apps with APK Export because of them either being taken down in Playstore or turned into a bloody mess to adapt to 10/11.
I also have a couple trusted apps the use overlays, Q would render them useless or a pain to use.
I remember the horror of Vista and Lollipop... Pie is running very well, WYSIWYG
The most I'll do for now is an occasional reload of Pie if needed. All my data including the all apks/system updates are stored on my SD card so reloads are much easier. No screwing around with or waiting for Playstore. Any app that allows it's setup to be exported is also saved there.
With over 230 GB of data it saves a lot of time coping it from the laptop too.
I never have a phone without an SD card slot... you know like an Apple.[/QUOTE]
thanks for the info i have a few apps i want to get off my lg g4 that are a miss in the android store
Anyone else experiencing problems with the 6a fingerprint.It's unlocking even with the non-registered fingerprint. Is this a widespread issue?
Yes, seems widespread looking at various reports. A fix will probably come.
Hope 6a is not a phone with a bunch of various issues just like its big brothers.
Don't worry, an update will probably fix the problem.
Virgo_Guy said:
Yes, seems widespread looking at various reports. A fix will probably come.
Hope 6a is not a phone with a bunch of various issues just like its big brothers.
Click to expand...
Click to collapse
I'm not seeing this as a widespread issue. Where did you see that? From AP there were only 2 devices that supposedly showed this bug whereas the staff none had the problem. I mean it hasn't even been delivered yet.
bobby janow said:
I'm not seeing this as a widespread issue. Where did you see that? From AP there were only 2 devices that supposedly showed this bug whereas the staff none had the problem. I mean it hasn't even been delivered yet.
Click to expand...
Click to collapse
Virgo_Guy said:
Click to expand...
Click to collapse
One guy with a pre release version does not a widespread issue make. We'll know more tomorrow. It very well might be but isn't yet.
bobby janow said:
One guy with a pre release version does not a widespread issue make. We'll know more tomorrow. It very well might be but isn't yet.
Click to expand...
Click to collapse
The units with the said issue tested by the reviewers are not pre-production units, those are the final units without a retail imprint.
Here's another one(at 14:47):
Virgo_Guy said:
The units with the said issue tested by the reviewers are not pre-production units, those are the final units without a retail imprint.
Here's another one:
Click to expand...
Click to collapse
Ok that's 2. Pre distribution then. Let's wait this one out before you jump to conclusions. AP couldn't replicate the issue so I'm a little leery on assigning a flaw because of 2 reports. As I said it might be more widespread but we'll know more tomorrow.
Aside, who hands someone a phone that's locked? If anyone handles my phone it's because I've given them access. I wonder if the FPR (possible flaw) will unlock a banking app that is bio-metric? That would be an interesting test and bigger issue if there is indeed a problem.
bobby janow said:
Ok that's 2. Pre distribution then. Let's wait this one out before you jump to conclusions. AP couldn't replicate the issue so I'm a little leery on assigning a flaw because of 2 reports. As I said it might be more widespread but we'll know more tomorrow.
Click to expand...
Click to collapse
Counted the one from beebom as the 3rd one?
At 1:23
There are actually more reports via a Google search.
But yeah, I'm not worried yet because I don't think a software update will not fix it, I just hope the update arrives before the retail units go to hands. But since Google took a very long time to fix issues with its big brothers, I'll not get a retail unit until it's fixed first.
@Virgo_Guy A mere bag o' shells. I'll make sure that it works correctly when I get it tomorrow and gloat. ;-) If it has a flaw I'll keep it in my sight at all times. But my wife knows all my passwords and our joint account number. So now what? Sleep with one eye open, shower with her to keep her honest? Decisions, decisions.
Just got mine. All set up. Zero issues with the finger print sensor. Works first try with only fingers registered. Went around my office letting people try to unlock with zero success.
This phone is so amazing. I'm coming from the pixel 6, to the S22. I prefer this all day long over them.
RoccoN4 said:
Just got mine. All set up. Zero issues with the finger print sensor. Works first try with only fingers registered. Went around my office letting people try to unlock with zero success.
This phone is so amazing. I'm coming from the pixel 6, to the S22. I prefer this all day long over them.
Click to expand...
Click to collapse
Let us know about heating issue when on Mobile Data..
Also let me know if heating issue can be reduced by disabling 5G..
It took like an hour to set up yesterday. Downloading all my apps. Setting everything up. Phone got a little warm which is usual. Since using it normally, including YouTube and playing with the camera, honestly didn't feel the phone get warm at all.
I've disabled 5G as LTE is just as fast where I am (Toronto) so couldn't really help you there.
hello, I just received mine and no problems with the fingerprint reader, I'm the only one who can unlock it.
received mine today and my fingerprint works perfectly fine, and no issue with unlocking it with anyone`s finger prints or my other fingers that are not registered.
Got mine today. Only registered my right thumb, but left thumb opens it too. None of my other fingers do though.
And no, none of my previous devices do this. Not my Pixel 5A and not my OnePlus 7 Pro. My fingerprints are not identical, which is almost statistically impossible.
So yes, the fingerprint sensor is not secure. Please stop going out of your way to defend Google. They are not your friend, they just want your money.
Cheesethief said:
Got mine today. Only registered my right thumb, but left thumb opens it too. None of my other fingers do though.
And no, none of my previous devices do this. Not my Pixel 5A and not my OnePlus 7 Pro. My fingerprints are not identical, which is almost statistically impossible.
So yes, the fingerprint sensor is not secure. Please stop going out of your way to defend Google. They are not your friend, they just want your money.
Click to expand...
Click to collapse
Did it open any other biometric apps?
ILoveAndroidCustomization said:
Anyone else experiencing problems with the 6a fingerprint.It's unlocking even with the non-registered fingerprint. Is this a widespread issue?
Click to expand...
Click to collapse
Yes. I just got mine setup yesterday and registered both thumbprints. Then, was able to unlock it with my right index finger (which was NOT registered.) So, it is definitely an issue. Also to note, I'm on T-Mobile and haven't received an OTA update yet. OOTB it is on the April security release. **Interesting note: it seems that Google doesn't even have an unlocked OTA update yet: https://developers.google.com/android/ota
The Google Pixel 6a is getting its very first OTA update
The Google Pixel 6a is already receiving its first software update, packed with the June 2022 security patches. Read on to know more!
www.xda-developers.com
Did you guys receive the update above?
Install it and then share the unlocking experience.
Virgo_Guy said:
The Google Pixel 6a is getting its very first OTA update
The Google Pixel 6a is already receiving its first software update, packed with the June 2022 security patches. Read on to know more!
www.xda-developers.com
Did you guys receive the update above?
Install it and then share the unlocking experience.
Click to expand...
Click to collapse
After the update only registered FP will unlock. Before I could use my other thumb but not other fingers. Seems fixed already.