Develop Bugs

Android OS is sucking up all my mobile data!

Got to work this morning to find out I had no mobile data left (attached image). I thought, how strange, yesterday I'd had about ~1GB usage out of my 4GB available, I of course immediately when and looked to see what had used it all and Android OS was at the top with 2.13GB (WTF?).
This also isn't the first time this has happened, I had the same last month. Can someone please explain what is going on because I know for damn sure I've not used all that, I only browsed a few web pages this morning.
Sent from my Pixel XL using Tapatalk

Stop automatic backup

thenessus said:
Stop automatic backup
Click to expand...
Click to collapse
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Sent from my Pixel XL using Tapatalk

pairedprototype said:
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Click to expand...
Click to collapse
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.

Use Data Saver in settings, works a treat

TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.

Just switch to the unlimited data plan..problem solved

TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
alluringreality said:
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.
Click to expand...
Click to collapse
You are indeed correct, I am due an update, however, I'm not rooted currently although, my bootloader is unlocked as I've been assisting with getting Magisk working on stock for Pixel devices.
And what kind of idiot developer/team thought downloading OS updates over mobile data without question was okay!? I've now got to go for 2 weeks without, I'm royally p*ssed about it. Guess I'd better flash the new update then while I have a (non-cellular) internet connection.
I remember when Google targeted power users with Nexus devices, I guess this is not entirely true for Pixel devices. Big boys like to do what they want, even if that means staying on a particular version of Android because we might be testing things... I'd rather not have OS updates forced down my throat, it's the same thing that bugs me with Windows 10.

lucky_strike33 said:
Just switch to the unlimited data plan..problem solved
Click to expand...
Click to collapse
If you're willing to pay the extra, sure thing!

You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data

lucky_strike33 said:
You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data
Click to expand...
Click to collapse
That's what I usually do! Just not had the time to do it recently.

this is caused by update downloading and failing over and over. I went into the dev options and turned off the auto update but it did not work. I had to update the phone manually and now its fine. I think after rooting the phone and going back to stock rom this happens.

IDK man, I was rooted and was pulling like 10gb+. Flashed stock via adb and I think it's still doing it. Project fi.

This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.

FrostyOrDie said:
This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.
Click to expand...
Click to collapse
When you returned to stock did you get to the latest version?

TonikJDK said:
When you returned to stock did you get to the latest version?
Click to expand...
Click to collapse
No. This all happened since returning to stock. Today I sideloaded the August update with adb and my phone says it's on the current version finally. It seems the support people at project fi are clueless for the most part. You have to do everything yourself but they will at least credit your account for the data used by Android os if you call them and tell them what's up. They want screen shots of the data usage. So save one before you go messing with stuff

Nougat 7.1.1 is rolling out!

Hey everyone, been a little while, but 7.1.1 N is rolling out to you guys.

Awesome! Is this the same 108 build that went out to beta testers?

Does it include the battery optimization that was mentioned some time ago?

***

New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?

ipowyourface said:
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
Click to expand...
Click to collapse
Is your bootloader unlocked?

Nextbit_Khang said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?

ipowyourface said:
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
Click to expand...
Click to collapse
Yeah that's kinda weird. It should work. I'll ask around.

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
Yeah, there was another person on the Razer forums who had the same problem as well.

Just got my Nextbit today updated few times before work on 7.0 present and update pending hopefully 7.1.1 , How's the update ? any issues fixed not had it long enough to find any
Sent from my Robin using Tapatalk

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.

ipowyourface said:
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
Click to expand...
Click to collapse
You had to re-lock your bootloader also, correct?

Is anybody having issues with sending text messages (your standard text message) with WiFi on? Not over WiFi, but just with WiFi on. I tried the default messaging app and the Google one. They both work the same. For me to get a text message out, I have to turn off WiFi.

I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Sent from my MotoG3 using Tapatalk

DoobyDroid said:
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Click to expand...
Click to collapse
Why don't you flash the latest factory image?
You can't flash an OTA update via custom recovery.

Loving this new update!
However, if you want to save resources and please your customers at the same time when doing the next update -
skip the nextbit bits.
Just make the next updates (if you plan on making any more of course) stock, for all intents and purposes, except perhaps for the backup/cloud feature.

revert back to 7.0 ?
since i updated to 7.1.1, my pebble 2 would constantly disconnect.
how to revert back to plan 7.0 ?
thanks!

Any word on android 8

Franzferdinan51 said:
Any word on android 8
Click to expand...
Click to collapse
Lmao very doubtful

hey there guys i'm having this weird trouble updating to 7.1.1, i'm currently on 7.0 (Robin_Nougat_88) and i have downloaded the 7.1.1 update (560 mb) and when i hit the "reboot and install" button it say restarting in 10 ... 9... 8 blah blah then rebooting now and never get to reboot... i can't install this update is there some solution? do i have to install the N108 image like new following the razer thread? thanks in advice guys have a good day!

Play Store FC trying to buy app

Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified

mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.

mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.

mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?

mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.

mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.

mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.

mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.

mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol

mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!

mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it

mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.

mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is

mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?

mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage

mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.

Restore Old Backup to New RMA

I know this can be a bad Idea. But I am on a time crunch to return this RMA and I have been gone on a business trip. Which now leaves me with only a few days (including shipping) to get my RMA all running and my old phone sent back to Google without having to pay for the phone in full. My problem is I have no way to pull my data off my old phone because anytime I do it say is Analog Audio Accessory Detected. (The Attached Deviced is not compatible with this phone).... So I had to get a RMA. I can't even charge my phone with my original charger. Also my old 6P charger... Only my watch charger which is only .5A...
Is there a way to restore a old backup I have on my computer from my old phone to my RMA without any problems? Also I have done this once but ran into the fingerprint problems and Ti backup with its Android ID issue. Other than that NO problems. Here is something somewhat similar to the problem for the fingerprint sensor. But I notice that the some of the stuff is missing on the Pixel. https://forum.xda-developers.com/nexus-6p/help/fingerprint-issue-restoring-twrp-backup-t3307734

stalls said:
I know this can be a bad Idea. But I am on a time crunch to return this RMA and I have been gone on a business trip. Which now leaves me with only a few days (including shipping) to get my RMA all running and my old phone sent back to Google without having to pay for the phone in full. My problem is I have no way to pull my data off my old phone because anytime I do it say is Analog Audio Accessory Detected. (The Attached Deviced is not compatible with this phone).... So I had to get a RMA. I can't even charge my phone with my original charger. Also my old 6P charger... Only my watch charger which is only .5A...
Is there a way to restore a old backup I have on my computer from my old phone to my RMA without any problems? Also I have done this once but ran into the fingerprint problems and Ti backup with its Android ID issue. Other than that NO problems. Here is something somewhat similar to the problem for the fingerprint sensor. But I notice that the some of the stuff is missing on the Pixel. https://forum.xda-developers.com/nexus-6p/help/fingerprint-issue-restoring-twrp-backup-t3307734
Click to expand...
Click to collapse
I assumed you did a twrp backup of your broken phone, and saved it to your pc. If so, when you get the new phone, unlock it, install twrp, you could, in theory, restore your data partition from the backup you made. Google restore also works pretty good, which should be saved on your google drive. I would also recommend you keep your screen lock set to none or swipe before you begin. Best of luck to ya

Badger50 said:
I assumed you did a twrp backup of your broken phone, and saved it to your pc. If so, when you get the new phone, unlock it, install twrp, you could, in theory, restore your data partition from the backup you made. Google restore also works pretty good, which should be saved on your google drive. I would also recommend you keep your screen lock set to none or swipe before you begin. Best of luck to ya
Click to expand...
Click to collapse
Got it up and ruinning Badger! So how do I go about updating to the latest July Patch on DU ROM? I am on June? Thanks again!

stalls said:
Got it up and ruinning Badger! So how do I go about updating to the latest July Patch on DU ROM? I am on June? Thanks again!
Click to expand...
Click to collapse
I'm not even sure if DU has been updated yet. If it has, then pull the vendor.img from the factory image and put it on your phone. Go into twrp, wipe ART/dalvik cache only! Then flash the vendor.img to the vendor partition, then flash the rom, then the twrp installer zip, boot up, and hopefully everything is ok. Then go back to twrp and flash your kernel(optional) and then magisk. Then you should be good :good:

Badger50 said:
I'm not even sure if DU has been updated yet. If it has, then pull the vendor.img from the factory image and put it on your phone. Go into twrp, wipe ART/dalvik cache only! Then flash the vendor.img to the vendor partition, then flash the rom, then the twrp installer zip, boot up, and hopefully everything is ok. Then go back to twrp and flash your kernel(optional) and then magisk. Then you should be good :good:
Click to expand...
Click to collapse
Do I have to flash the previous Factory image if I might have tried to flash the latest update lol and start all over ?

stalls said:
Do I have to flash the previous Factory image if I might have tried to flash the latest update lol and start all over ?
Click to expand...
Click to collapse
Either that, or just stay on stock July and wait for DU to be updated

Badger50 said:
Either that, or just stay on stock July and wait for DU to be updated
Click to expand...
Click to collapse
But Man I love to screw things up and have to fix them

stalls said:
But Man I love to screw things up and have to fix them
Click to expand...
Click to collapse
Then have at it Big Dog! ???

I'm curious if anyone has restored a TWRP nandroid from their original phone to the RMA. My understanding is that it should be fine as long as you make sure you're on the right base factory image first.

Reechings said:
I'm curious if anyone has restored a TWRP nandroid from their original phone to the RMA. My understanding is that it should be fine as long as you make sure you're on the right base factory image first.
Click to expand...
Click to collapse
I've seen it done on the 6P without issue. Should be ok on the P2XL so long as it's just the data partition your restoring :good:

Badger50 said:
I've seen it done on the 6P without issue. Should be ok on the P2XL so long as it's just the data partition your restoring :good:
Click to expand...
Click to collapse
Yeah that makes the most sense, I'll restore my data then "dirty flash" the rom I'm using over top.

Reechings said:
Yeah that makes the most sense, I'll restore my data then "dirty flash" the rom I'm using over top.
Click to expand...
Click to collapse
That's what I did and it works perfect
Sent from my Pixel 2 XL using XDA-Developers Legacy app

stalls said:
That's what I did and it works perfect
Click to expand...
Click to collapse
How did your RMA turn out?

Reechings said:
How did your RMA turn out?
Click to expand...
Click to collapse
Pretty good so far
Sent from my Pixel 2 XL using XDA-Developers Legacy app

stalls said:
Pretty good so far
Click to expand...
Click to collapse
How's the screen? What's the manufacturing date of replacement unit?

Reechings said:
How's the screen? What's the manufacturing date of replacement unit?
Click to expand...
Click to collapse
Normal blue tint thing still but not bad.. it was in October
Sent from my Pixel 2 XL using XDA-Developers Legacy app

stalls said:
Normal blue tint thing still but not bad.. it was in October
Click to expand...
Click to collapse
Ok. My last RMA was from October too. We'll see what this one is.

The Unlocked s10+ (U1) is receiving Android 10

The Samsung Unlocked s10+ is now receiving the Android 10 update. the notification just popped up on my phone.

Yeah I grabbed the tar files earlier I'm uploading it now.

Finally!

Just got my update ?

Make sure you guys backup any files you may have on your phone before updating. My fruity ass didn't and an error popped up during the update it wiped all my apps and settings and booted into safe mode now i'm forced to do factory restore and start from scratch.

Still waiting on mine

I got the Android 10 like two weeks ago

I'm running a U1 device on Sprint Network. I got pushed the android 10 update 12/26.

mc_365 said:
I'm running a U1 device on Sprint Network. I got pushed the android 10 update 12/26.
Click to expand...
Click to collapse
Were you on the android 10 beta when you got the update, or still just official Pie?
Sent from my SM-G975U using Tapatalk

jsmcmahon89 said:
Were you on the android 10 beta when you got the update, or still just official Pie?
Sent from my SM-G975U using Tapatalk
Click to expand...
Click to collapse
No never tried the beta. I just looked and saw the update available.

Finally got my update today.

EdinM30 said:
Make sure you guys backup any files you may have on your phone before updating. My fruity ass didn't and an error popped up during the update it wiped all my apps and settings and booted into safe mode now i'm forced to do factory restore and start from scratch.
Click to expand...
Click to collapse
Bruh, Samsung didn't one up the iPhone with their own integrated Cloud back up with 3 times the free starter size for nothing! Get that auto back up set up!

schwift said:
Bruh, Samsung didn't one up the iPhone with their own integrated Cloud back up with 3 times the free starter size for nothing! Get that auto back up set up!
Click to expand...
Click to collapse
nope, Samsung can go pound on sand i'll integrate my foot where the sun doesn't shine before i setup some remote upload of my personal files. The only loss i took was my contacts i didn't update them since i bought the phone and lost a few numbers, i have my stuff copied either on the sd card on the pc

Not here in Australia yet ☹

How about usa? IM on beta and no final yet for me. Unlocked 975u1View attachment 4916653
Sent from my SM-G975U1 using Tapatalk