Noticed my Android OS is using almost 1gb of which doesn't seem right.
https://m.imgur.com/p1bAilv,XvmBuaw
Any ideas?
Edit 3: Updating will fix this properly.
Edit 2: That didn't fix it...
Edit: I've seemed to "fix" it. From my reading it is a background service trying to do a seamless update in the background. I disabled "com.qti.service.colorservice" using titanium backup and restore and it seems my background data usage has stopped. No negative consequences so far but it may prevent seamless updates. Another fix would probably be updating to the latest patch version...
Idk but I hope you get an answer... Been killing my battery.
{
"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"
}
Also seems to hit Wi-Fi...
for me the issue did not go away until I did a factory reset
danw_oz said:
for me the issue did not go away until I did a factory reset
Click to expand...
Click to collapse
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
jhs39 said:
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
Click to expand...
Click to collapse
It has been a while but I'll reply so anyone else who comes will know. My state before and after was the same. All that changed was my OS version. Flashed the flash-all.sh after removing the -w, flashed the April bootloader (so no boot signing stuff, not the safest or recommended thing), booted TWRP, flashed twrp, flashed supersu, and then rebooted. No other mods besides adaway.
Are you on stock, rooted or unlocked bootloader? I had the same issue on stock (unlocked bootloader) where it was trying download an update repeatedly. I had to actually flash a custom rom to make it stop. Verizon did credit me back for the data it used.
Feel free to read my forum post there and try those steps. - https://community.verizonwireless.com/message/1500910#1500910
Don't ask me how I know but this is a backdoor to access your device. Be careful!
paulJW said:
Don't ask me how I know but this is a backdoor to access your device. Be careful!
Click to expand...
Click to collapse
downloading the security update(s) is a backdoor in?
Riiiight
y2grae said:
downloading the security update(s) is a backdoor in?
Riiiight
Click to expand...
Click to collapse
he said dont ask him how lol
I had to factory reset before this stopped
Related
I got to thinking the other day after I got the "Firmware Update" notification for the umpteenth time that it would be really cool if there were a way that I could run the factory non-rooted ROM so that I could check my work email easily and then use some sort of app or sequence to switch in to a rooted ROM to do everything else. Is that possible?
No dual boot for us yet...
Sent from my SPH-D710 using xda premium
By firmware update are you talking about an ota update? If so, there are several zips you could flash to get rid of it.
Sent from my SPH-D710 using XDA
Dual booting a zImage is tricky. Not to say its impossible but it isn't easy like a standard bootimg dual boot. The main problem lies in the recovery being packed with the kernel. When dual booting android if u run into an issue such as a bootloop you flash a zip to boot back to your main rom, the zips are recovery specific. With Tue recovery changing between zImage flashes you could quite easily end up in limbo til you get to a PC with Odin/heimdall to flash a new firmware and be able to boot back up. There's been some work done on it but you can't boot across versions only same build/version and its not really stable in the secondary rom due to kernel conflicts
{
"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"
}
Bannjio said:
By firmware update are you talking about an ota update? If so, there are several zips you could flash to get rid of it.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Do I need root for it?
mfenske said:
I got to thinking the other day after I got the "Firmware Update" notification for the umpteenth time that it would be really cool if there were a way that I could run the factory non-rooted ROM so that I could check my work email easily and then use some sort of app or sequence to switch in to a rooted ROM to do everything else. Is that possible?
Click to expand...
Click to collapse
let me get to the root of the problem. no pun intended.
why do you need to be unrooted to check work email? do you use an app like 'Good for Enterprise' that checks for root or something?
calisro said:
let me get to the root of the problem. no pun intended.
why do you need to be unrooted to check work email? do you use an app like 'Good for Enterprise' that checks for root or something?
Click to expand...
Click to collapse
I have to use Touchdown for email and if it detects root (Superuser) it kicks you off the network-which I can't have.
mfenske said:
I have to use Touchdown for email and if it detects root (Superuser) it kicks you off the network-which I can't have.
Click to expand...
Click to collapse
I have a similar issue. chk my post for how I work around the stupidity.
http://forum.xda-developers.com/showthread.php?p=33088059
Hello i've some problem with my T-Mobile Galaxy Note 2.
Last week i updated my phone on Android 4.3 version.
Unfortunelly i had a wifi bug and I couldn't connect to internet, so I decided to downgrade it to 4.1.2. I've flashed my stock ROM with the newest one. (thanks to this link http://forum.xda-developers.com/showthread.php?t=2102380 )
Afterward, i would rooting my phone and install custom binary CWM by this thread, option 2.
However i can't modifiy system files. I consequently would verify my status root by Titanium Backup. And that's really strange because it is already rooted.
{
"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"
}
...
So i'd like to know how to resolve my problem, i how to modify system files?
(PS: sorry for my bad English!)
PS2: That's the same thing if i connect it on SSH/FTP protocols, unable to modify too.
I have T889 version and I just updated today with 4.3 with no problem.
I would say the best thing is just start from scratch and reinstall your app.
I don't even use TB anymore, I used to but I just happen to run into problem a lot.
I decided to just reinstall apps everytime I flash rom.
DLinkwit said:
I have T889 version and I just updated today with 4.3 with no problem.
I would say the best thing is just start from scratch and reinstall your app.
I don't even use TB anymore, I used to but I just happen to run into problem a lot.
I decided to just reinstall apps everytime I flash rom.
Click to expand...
Click to collapse
So, do you advise me to re-install the 4.1.2 version and re-root again?
update: I've re-installed and re-rooting my stock rom and nothing has changed. Can you help me please?
Zebra_Cat said:
So, do you advise me to re-install the 4.1.2 version and re-root again?
update: I've re-installed and re-rooting my stock rom and nothing has changed. Can you help me please?
Click to expand...
Click to collapse
Try using the Odin again and when you full wipe don't even do anything just update to the original 4.3 via Tmobile.
After that install CWM or TWRP, Like I said I never had any issues installing Rom back and forth.
Just don't skip a step and never rush things.
DLinkwit said:
Try using the Odin again and when you full wipe don't even do anything just update to the original 4.3 via Tmobile.
After that install CWM or TWRP, Like I said I never had any issues installing Rom back and forth.
Just don't skip a step and never rush things.
Click to expand...
Click to collapse
I didin't understood that happened to me,
After several minutes and after downloading an alternative file explorer, SU granted to me to modify system files.
In the last couple days I ended up moving my way up the Stock firmware going from N900TUVUDNE6 4.4.2 w/ root Knox in tact to N900TUVUDNF4 4.4.2 w/ root K.I.T. Within the last 24-hours I was tinkering around with the ROM and I cannot believe I was so derpy but I made a few changes with some apps and ended up doing a reboot. Well when I went to reboot the normal first boot screen came on
{
"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"
}
(mine is the N900T, I pulled the image from a google image search) and it goes blank after that. I can get into Download Mode and Recovery no problem, and I almost feel like if I just try to re-flash the stock firmware I will be good to go again. My biggest concern about doing this is losing my root and I wouldn't very much like that simply because to get it back would mean tripping Knox. So, I guess what I am looking for is someone who might have a stock System Dump of the N900TUVUDNF4 with root. Even better if it were in a flashable format for Odin or Recovery. I'm also open to suggestions to other-work arounds. I've tried reflashing bootloader, CSC, modem, non_hlos, and recovery with no luck. Before updating the ROM I did to a factory reset so that it cleared all data for a fresh install and have since cleared data/factory reset and clear cache. So, like I said, I am open to suggestions ideas, etc. I've done a lot of research and tinkering around trying to figure this out, but it finally came down to needing to reach out to someone.
Additional Info:
At one point I was getting ADB when it was sitting on the black screen, but now I can only get ADB when I choose update with ADB in recovery, otherwise Odin is picking it up.
here
http://forum.xda-developers.com/not...-to-root-nf4-knox-0x0-effortless-nf4-t2846142
you start with nf4, flash ne4 kernel, root with towel root and reflash nf4 kernel
worked great for me
pete4k said:
here
http://forum.xda-developers.com/not...-to-root-nf4-knox-0x0-effortless-nf4-t2846142
you start with nf4, flash ne4 kernel, root with towel root and reflash nf4 kernel
worked great for me
Click to expand...
Click to collapse
Thanks so much, you are a life saver. Back on NF4 with root access!
So I was driving back yesterday and my phone notifies me that I'm reaching my data limit. I thought, "That's odd, I've only used 0.1 GB". So I look down and see this monstrosity of data being used by the damn Android OS. How the heck can you see what would individually be using data in the "Android OS" package cause it could be any number of things. I'm guessing it could have been a system update pull but I did disable OTA updates in developer settings. I have root as well and I would like to freeze that process with Titanium Backup if anyone knows what that process might be on the Pixel. Also any other suggestions as how to further troubleshoot this would be appreciated.
{
"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"
}
It's the update pull even though you are updated. We have seen this a few times with others. Get it updated.
TonikJDK said:
It's the update pull even though you are updated. We have seen this a few times with others. Get it updated.
Click to expand...
Click to collapse
Well when I go to system update and choose to install update it says that it failed. Any advice on that? Can you not properly install updates while rooted?
In terms of updating to the latest OTA I followed How To Geeks - FlashFire Guide which put my device into a endless bootloop so I don't recommend doing that.
Still looking to see if anyone knows what to freeze in Titanium Backup on Pixel to block OTA updates from downloading. Thanks.
ThePieMonster said:
Well when I go to system update and choose to install update it says that it failed. Any advice on that? Can you not properly install updates while rooted?
Click to expand...
Click to collapse
You must of modded something that is stopping it. There is a way to sideload the OTA, but the third post in the thread below is how I do it each month. Have ro reroot afterwards.
Pay attention to the part where you remove the-w from flashall bat file. That is what saves your data.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
TonikJDK said:
You must of modded something that is stopping it. There is a way to sideload the OTA, but the third post in the thread below is how I do it each month. Have ro reroot afterwards.
Pay attention to the part where you remove the-w from flashall bat file. That is what saves your data.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I ended up flashing the original stock ROM off Google's website and then went threw the systemless root methods mentioned here.
I now have the below:
Android: 7.1.1 ROM: Factory (Rooted) Kernel: 3.18.31-ElementalX-P-1.08 Build: NOF27B
im having tons of data through the same thing. I ran a data manager app and it said its google.uid.system:1000 . I reset the rom to original as I have not installed any other rom then googles originals. I have some of the highest data downloads its crazy. I even turned off back up picture folders. Here is the data.
Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"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"
}
You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk
So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse