newdayrocks
Member
I did the same with my N6. So much smoother on 6.0.1.so i rolled back from the N preview. that shit was infuriating, not even close to daily driver material.
this march update on the 6p though unf unf unf
I did the same with my N6. So much smoother on 6.0.1.so i rolled back from the N preview. that shit was infuriating, not even close to daily driver material.
this march update on the 6p though unf unf unf
Heh, so N is definitely no good for daily use? Glad I waited. Like I said, the March 6P update is fantastic.
so i rolled back from the N preview. that shit was infuriating, not even close to daily driver material.
this march update on the 6p though unf unf unf
Heh, so N is definitely no good for daily use? Glad I waited. Like I said, the March 6P update is fantastic.
Why am I supposed to hate the 9? I've had nothing but a positive experience with it.
Only issue I have with N now is Chrome locks up overnight for some reason and have to force quit it. Everything else is smooth as silk.
Dirty flash? Ah, that's probably the reason you weren't able to daily drive it. Just like L preview, just like M preview.i had the N preview lock up on me, apps taking forever to open and switch between, lag and once even the system ui kept force closing over and over and i had to hard reset.
could have been because i didn't factory reset after the update, but eh. i'll wait and see what happens with next month's update.
Well this is one bizarre day. T-Mobile CEO John Legere is going to bat for the SD820 Galaxy S7. Maybe the Un-Carrier doesn't want to be the bad guys after all.
http://www.xda-developers.com/unlikeliest-of-heroes-john-legere-working-to-free-the-s7/
I might have to switch to T-Mobile sooner than I thought. I wonder if they have LTE out here where I live yet.
they probably do if you're in the US, you should check their coverage map. I was clearly snoozing and completely missed out on how much shit they turned on last year.
Probably not even a 'N' issue. If the 'O' release is simply a non-shitty Chrome with no other changes, I'll be happy.
That's a problem with certain websites and how they render. There's a few sites it will always say that to me you can just ignore it as it will constantly happen on that siteOn Chrome on my 6P I keep getting a warning that WebGL "hit a snag". Anyone know how to fix this? It seems to have just started after I rolled back from the N beta.
Dirty flash? Ah, that's probably the reason you weren't able to daily drive it. Just like L preview, just like M preview.
Previews are so awesome. I'm so happy Google started it. I especially love how they launched it. They just did it. No stupid keynote or major fanfare. It just went out. That's how you do it. Today's keynotes are just plain awful and unnecessary. They're deserved once in awhile, like totally new hardware, but stuff like iPad version faster is such a waste of time.
No reason to hold back iOS development just so the few petty people who demand they get features first can be appeased. They have separate teams working for iOS and Android and it isn't rocket science that the iOS version of any app is going to be developed faster since they aren't optimizing it for as many devices.
Reasonably speaking it would just be plain silly to higher more developers just to accelerate app development by a few weeks. I am confident Google already has large software teams so the solution to just throw more money at a problem is dumb. Doing it "forever" doesn't change anything. Every time they push a new app update out they probably have to run-test it on dozens upon dozens of different devices making sure there are no compatibility issues or bugs specific to that hardware. If anything it probably just gets harder as time goes on and more phones come out alongside newer versions of Android.1. Your attitude is petty.
2. Holding up the IOS version is not the only way to bring parity to the teams. Its google, they can afford to grow the Android Hangouts team.
3. You are a wrong if you think the reason why Android Hangouts has been behind for ages is because there are more devices to optimize. The team has been dogging it forever. Ever heard of apps like Google Maps, Gmail, Drive, Calender, Docs, Keep, Photos which all are leading their IOS versions?
4. Hangouts is used in the business world heavily. People notice when one phone cant do the same thing a coworkers can. Its about brand perception. Google wants Android to be the best and sell the most.
Reasonably speaking it would just be plain silly to higher more developers just to accelerate app development by a few weeks. I am confident Google already has large software teams so the solution to just throw more money at a problem is dumb. Doing it "forever" doesn't change anything. Every time they push a new app update out they probably have to run-test it on dozens upon dozens of different devices making sure there are no compatibility issues or bugs specific to that hardware. If anything it probably just gets harder as time goes on and more phones come out alongside newer versions of Android.
Honestly I just find the whole argument silly. People crying on Reddit "Google doesn't care" because they push out iOS app updates faster than Android is dumb as hell.
So with dual window coming in Android N I assume the minimum specs to run it smoothly will be bumped up. Tempted to get a 5x but don't think 2gb of ram will cut it when its on N.
So with dual window coming in Android N I assume the minimum specs to run it smoothly will be bumped up. Tempted to get a 5x but don't think 2gb of ram will cut it when its on N.
Split screen is old news baby, at least maybe for tablets. Freeform Window multi-tasking is in the N code.
http://arstechnica.com/gadgets/2016...roid-n-code-hints-at-a-freeform-windows-mode/
Don't have patience for this. They're going to delay that shit until Android O. They took too long and Remix OS does this well already.
Interesting, think I'll hold out to see what this years nexi bring. This g2 is running like a champ on cm13.Depends on what you're doing. In most cases not significantly - the reason videos aren't working on split screen apps at present until developers update them is because the OS pauses most of the app that's not currently in focus, and will only activate the relevant sections. So a developer needs to activate the relevant section specifically.
If that's video, then the decode is done by the hardware decoder in the processor and doesn't really need to touch the RAM much at all.
If you try and run a 3D game next to a Twitch commentary feed you're more likely to hit issues. But for the most part RAM won't be as big a concern as other factors (RAM issues on Android are hugely overstated. The problems are usually elsewhere).
Interesting, think I'll hold out to see what this years nexi bring. This g2 is running like a champ on cm13.
It really is, if only the camera didn't go to crap with custom ROMs...God-tier device. I just sold mine on Swappa and sending it away is going to hurt.
Don't have patience for this. They're going to delay that shit until Android O. They took too long and Remix OS does this well already.
[...] Just as it did with KitKat (Key Lime Pie), Lollipop (Lemon Meringue Pie), and Marshmallow (Macadamia Nut Cookie), Google has an internal name for N: New York Cheesecake.
On the one hand, it doesn't seem like something that would be caused by a hardware issue. But on the other hand, it doesn't seem like an account issue since it's specific to just this one device. Looking around it seems this is a relatively common error, but just removing and re-adding the Google Account should normally fix it.
I'm not running a custom ROM or anything, not even rooted, just running the tablet as it comes (with updates installed)
Hardware storage of the Google root certificates could be corrupt. That's the only thing I can think of. Hopefully your replacement will work better.
(Really should have been caught by the SOC QC process tbh).
Certificates could be the issue given where the error happens. The error occurs at the stage the Play Store attempts to access my payment details. I get the usual prompt for Permissions, then when I accept those I get the error. On my 6P, accepting those brings up the details of my Google Play Balance and the Buy confirmation button.
It's just a bit disheartening, the tablet was a birthday gift from my parents and it makes me feel bad about it having to be replaced, since I know they'll feel bad about it not working perfectly right away.
Shit happens with tech, it sucks but it does. They're making good on it so don't worry about it so much, and tell them not to worry. At least you can still surf the web and whatever on it without apps.
T-Mobile is pretty legit these days, they were my first carrier way back before the first iPhone and a little bit into that era but I ended up switching due to service. Finally moved from Verizon back to T-Mobile last year when my girlfriend and I decided to get a family plan together; now we have two more people on our family plan and pay $120 for 4 lines with 10 GB each (not a shared bucket, each).
After having it for a day, my Pixel C is already getting replaced under warranty.
Whenever I try to make a purchase of a paid app on it, I just get an error message "Error retrieving information from server [RPC:S-7:AEC-0]". Purchases work fine on my Nexus6P so the issue seems specific to the tablet. Downloading updates, pre-purchased apps or new Free apps works fine, error only happens when trying to make a purchase.
Have tried all the troubleshooting steps I can find online, clearing data from Play Store and Google Framework Services, no effect. Have removed my Google account from the device, rebooted and then re-added the account, no effect. Done a complete factory reset but still the same issue when I go to the Play Store and try to make a purchase of any paid for app.
I had several payment methods on my account, one of which was expired, but I've removed that and still the same error. I've got over £11 of credit on my Google account anyway and was only trying to purchase something that costs less than £3, so payment cards shouldn't have come into it.
Contacted Google Support and they called me back, said they're going to send a link for me to order a brand new device and instructions on returning the old one.
On the one hand, it doesn't seem like something that would be caused by a hardware issue. But on the other hand, it doesn't seem like an account issue since it's specific to just this one device. Looking around it seems this is a relatively common error, but just removing and re-adding the Google Account should normally fix it.
I'm not running a custom ROM or anything, not even rooted, just running the tablet as it comes (with updates installed)
I used to have this issue when flashing custom ROMS I couldn't do anything with the play store at all. I take it you tried Factory Reset etc? for me when it happened I either had to wait for the play store to update/Kick in properly, Reflash the ROM or uninstall the playstore updates and update it manually.
Yep, did a factory reset but still the same issue. I'd never even rooted it, let alone flashed a custom ROM onto it.
Yeah it's a weird issue I haven't had it happen to me since the days of Jelly Bean but figured i'd ask anyway.
Out of curiosity hows the motion blur on your unit? mine is fricken awful but that could be partly to my eye sight. it's the main reason I haven't changed my TV yet as the one time I did the motion blur on it compared to my old one was insane.