What is Network operator Theme pack? - General Questions and Answers

As the title says, what is Network operator Theme pack? Ive already googled it and there is nothing close to it.
I was looking through my phones app list with system apps showing and I saw an app with that name, Network operator Theme pack and I dont recall seeing it before. It goes without saying, but I didnt install that app. The package name is "com.android.networksettings.overlay.ct".
There is also an app called Permission controller Them pack and its package name is "com.google.android.overlay.modules.permissioncontroller".
While they may mean nothing at all and be completely harmless, the "overlay" part raised a little red flag for me. Ive also been having severe battery drainage issues, but I dont know if that is related or not. Severe as in losing 1% of the charge every 3-8 minutes when using the phone and about 4%-5% every 45-60 minutes when the screen is off.
I looked at the list of processes running in 3C All in One Toolbox (paid version) and the only thing that was a problem was the mediaextractor kernel process which I killed each time it was a problem as it was eating up in excess of %150+ of the phones cpu. I was also rooted up until a few weeks ago when I updated magisk (through magisk manager) & edxposed, then after the phone restarted I was no longer rooted and unable to re-root without wiping all my data (which, needless to say I did not do as I am not in the mood to start over from scratch right now.
So yeah, if anyone could tell me what the strange app package is and maybe help me figure out my battery drainage problem, Id greatly appreciate it.
My phone is a OnePlus 7 Pro running android 10.
Stay healthy everyone!
P.s. I attached a screenshot of the app info window from both of the strange apps mentioned above.
{
"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"
}

Related

[Q] Why isn't Google Talk working? The application starts, but then closes itself.

My problems are exactly the same as the ones that can be found in this thread.
http://androidforums.com/incredible-support-troubleshooting/85756-gtalk-wont-open.html
The app pops up for a second, i see the icon and the words "signing in..." for about a second, and then it returns me to the home screen.
This is the log got by plugging the phone to my computer.
{
"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"
}
The thread seems to suggest a memory problem, but I've got 29MB free. Oh, and I'm running 2.2.
Does anyone have any idea what might be causing this?
davorb said:
My problems are exactly the same as the ones that can be found in this thread.
The app pops up for a second, i see the icon and the words "signing in..." for about a second, and then it returns me to the home screen.
The thread seems to suggest a memory problem, but I've got 29MB free. Oh, and I'm running 2.2.
Does anyone have any idea what might be causing this?
Click to expand...
Click to collapse
Well, I had the same problem, and I suspected memory as well, since I have been getting the low memory error for a few days now.
I uninstalled flash, which takes an enormous amount of space! 12 MB. But I also changed the Gmail policy for syncing. I had few very large folders set to sync 7 days worth, and one of those had a ton of inline images. I actually think that is what was causing the trouble, but I am not certain.
Either way, I freed up enough memory so that GTalk could turn on. I guess that sucker needs space, too! I wish more apps would use the install to SD card option. Especially giant ones, like Yahoo Fantasy Football (another 12MB one).
Oh well, I hope that helps.
P.S. I am on an original Droid running Froyo.
For me was the memory problem. I"ve uninstalled a 20 mb. prg and that solved the problem for me. I also needed to reboot my device after so the temp files will be erased along to. Now i have like 30 - 35 mb. free on the phone memory.

MJ7 Note 3 Exynos wakelock culprit found!

Yesterday I charged the phone 100% after rurning off the charger kept it untouched for 30 minutes lost 1% battery cause of wakelock.
I had not rebooted the phone for a few days so some apps I used where still running like a dictionary I use which prevents the phone from sleeping.
I used the phone for 70 minutes to watch videos on MX Player for 68 minutes and using tapatalk for 2 minutes then restarted the phone before I went to bed. I had 86% battery left & It was 1.10 am then.
Today I again started using the phone at 12.05 pm or so & I was amazed that my battery was at 83%
{
"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"
}
Conclusion: The wakelock is not the fault of Google' Android OS but it's a but that left unresolved by Samsung which does not kill apps completely after using them.
I had removed the dictionary from current tasks, killed running apps using both task manager's RAM Cleanup & Clean Master's memory boost yet the app didn't get killed completely & it's Battery permission which states that the dictionary will prevent the phone from sleeping triggered the stay awake(wakelock) of the Android OS. When I restarted the phone the dictionary got killed completely and thus the phone ate very very less battery.
This was just one app, we have multiple apps inatalled on our phone which prevent it from sleeping.
I really would like to report this to Samsung before they put KitKat out for Exynos Note 3, posting here since at least there are many people here who can help me do so. So that we can have a better user experience with our phone in the future.
Closing Statement: in short poor Task Management & Apps not geeting killed completely trigger Wakelocks.
Solution: Restart the phone before you keep it unused for long durations so you wint suffer from Wakelocks.
Sent from my SM-N900 using Tapatalk

Has anyone experience flickering/glitching after updated to 23.4.A.1.232?

At first I thought glitches I saw caused by the app (inbox) itself. Then I keep seeing it happens on other apps as well.
It is like some elements (ie, action bar) of apps flashing or the whole screen flickers. It usually happens only a second or two at most; too quick to make a screenshot of it.
Though, this problem is not happen regularly, it is frequent enough to get noticed.
Here are some apps that I remembered glitches happened, it happens in other apps too but usually very quick and random.
In FX File Explorer, sometimes glitches occur during transition animation between folders.
When adding a new Google account in Settings, the big top blue part of the screen flickers.
In Inbox app, sometimes tips bar just keep flashing for almost 2 seconds when I closed it.
And, in A Better Camera app, this can happen sometime:
{
"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"
}
I'm considering reverting back to 23.4.A.0.546.
Even though the old firmware has stagefright bugs, it's very unlikely that someone would use it on me, and I don't use MMS anyway.
for me both cameras are better in .232
and yeah I have these screen problem
and did you notice that the speakers are noticeably lower in music ?? now they are like Z3+ !!!!
I had some screen tearing when I first installed .232, but none since then.
Speakers seem just as loud as before.
I do have the same problem.
Made myself a prerooted fw using PRF, downgraded, rooted and upgraded using the prerooted firmware i made.
Also made a factory reset. Now i'm getting screen tearing while scrolling, video glitches and stutterings.
I saw that at first but not anymore (maybe I haven't noticed them).
Strange thing is that 232 version should be Stagefright free, however, I've runned a test and I'm still vulnerable to one of the flaws.

Should I keep using these Chinese phones? (Doogee, BlackView)

I bought 2 Chinese smartphones: One is from a company called "Doogee", and the second is called "BlackView"
The Doogee one came with many weird apps preinstalled, so I installed Malwarebytes, and it detected 2 malwares. Both removed. After a day, Malwarebytes prompted me that a malware app is trying to install itself (one of those I removed!) - So I stopped using this phone. Hopefully did not risk too much of my personal information (passwords, emails, etc).
Meanwhile, the other Chinese phone I ordered has arrived. Knowing about those security issues now, I immediately installed Malwarebytes, and it detected that the Sound Recorder app is a malware, and is actually using data(?):
{
"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"
}
T
@TroyGuard I would recommend to search for a custom rom build from source to get rid of that stock spy roms :good:
@TroyGuard
personally I wouldn't use them but as you have bought phones you probably want to.
Though on twitter recently Elliot Alderson (@fs0c131y was asking for such phones to analyse, he'd probably be happy to get one!
So If no custom ROM then you should be able to freeze those apps, system or preinstalled, that are risky or unknown (though they often come back, so freeze normally better). If you read the recent threads you will find links to a number of ways to do this, eg using TWRP, ADB, apps like Debloater etc which may work on those phones
WARNING: be careful freezing system apps, freezing an essential app can make your phone unusable, check online first if in doubt
Change all your passwords after this is done, to be safe.
(though there is still the possibility of a hardware backdoor , but I've not seen any reports of this.)
(Note: you probably won't get automatic OTA updates anymore as the ota updater is often part of the problem, besides you would have to refreeze apps after new install, but might be worth updating manually if it gives you important security patches)

Extreme battery drain issue with Bluetooth

Hello,
I've had by Z5 since late 2015 and it's been a real trooper. Sadly it has recently (in the last few days) developed an issue where Bluetooth appears to be draining battery like crazy. I've dug around a bit on the internet and found a few people experiencing the problem but none too recently. One post suggested turning on the 'Enable Bluetooth HCI snoop log' and toggling Bluetooth on and off, then checking the log. When I turn that setting on, it creates the 'btsnoop_hci.log' which very rapidly starts filling with junk. In the space of about 20 seconds it took for me to toggle BT on and off and take a copy of the log, it had grown to 700 KB.
Below are some screenshots showing the battery usage of Bluetooth. I have a copy of my btsnoop_hci.log file too but I couldn't find a way to attach it to this thread. If there's some way I can share this, please let me know. If anyone can help me troubleshoot this issue, I would be most grateful. As far as usage / changes that might have cause this problem, I can't think of anything too crazy but here are some points:
I paired my phone with a pair of Taotronics BH22 headphones last week but have since forced my Bluetooth to "forget" this device.
I use my Sony WH-1000XM3 headphones pretty much every day to listen to music since March 2019.
I don't use my phone for anything other than messaging, and music. The apps I have installed do automatic updates sometimes -- I was actually suspecting that an automatic update that went on for one of my apps might be the culprit, but I have no idea how to check this.
Battery usage screenshot 1
{
"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"
}
Battery usage screenshot 2
I think I've figured out what was causing the problem. It was an update to 'Google Play Services'. The version that recently went on was 16.0.91
I installed the beta version (specifically, 17.1.22 (040400-245988633) beta (040400)) and since then, Bluetooth is behaving.

Categories

Resources