If you use CPU Temp monitoring (there is an Xposed mod) you will see some scary temperatures (+/- °80) coming from the Exynos CPU at boot, and it takes a while to cool down.
This is mainly caused by Media Scanner, the Android system service. It occurs with every Rom I have used on the Galaxy Tab T-700.
The best, and easiest, way to disable Media Scanner is with SD Fix Tool. Just use it for this function, I wouldn't advise using any other features.
https://play.google.com/store/apps/details?id=ch.upper_cliff.sdfixtool&hl=en
Related
Hi everyone!
OK, I have pretty much isolated issues with battery since I found faulty wiring with Samsung USB cables that come with their chargers.
Not everyone will find issues with the USB cable, but the way it is made will be an issue eventually.
One, the cable is very thin and flexible, so many will stretch over a near by wall outlet to use the charger while using the tablet.
Eventually the wire at the connecter on the tablet end gets bent up to 90 degrees, Eventually causing two issues. One intermittent charging. The other a short. I have had both happen since Owning it in November 2013.I almost had a fire, as the plug had a meltdown. Super dangerous!
Now while messing with trimming down apps and memory, I found a few apps that I use have the ability of keeping the CPU and GPU at their highest frequency. They call it boost mode. Even if you have it disabled, toggling it on and off may clear out the setting if you notice your tablet's battery depleting fairly fast and heating up on the left side.
Now for a odd issue with Google apps... I removed the Google Play Music Player, and disabled DRM/Downloads and made a few adjustments to Media Server. What happens is Music Player will cause playback automatically and Media Server will loop into high CPU usage even during reboot. DRM and Media server can cause this condition quite easily. So far Google is not working on a fix for JellyBean. Only KitKat has this fix, all other previous Androids,Gingerbread for example, do not have the issue. Corrupt files or files with _ or strange symbols will cause this loop until the tablet is turned off completely and restarted.
.
gooberdude said:
Hi everyone!
OK, I have pretty much isolated issues with battery since I found faulty wiring with Samsung USB cables that come with their chargers.
Not everyone will find issues with the USB cable, but the way it is made will be an issue eventually.
One, the cable is very thin and flexible, so many will stretch over a near by wall outlet to use the charger while using the tablet.
Eventually the wire at the connecter on the tablet end gets bent up to 90 degrees, Eventually causing two issues. One intermittent charging. The other a short. I have had both happen since Owning it in November 2013.I almost had a fire, as the plug had a meltdown. Super dangerous!
Now while messing with trimming down apps and memory, I found a few apps that I use have the ability of keeping the CPU and GPU at their highest frequency. They call it boost mode. Even if you have it disabled, toggling it on and off may clear out the setting if you notice your tablet's battery depleting fairly fast and heating up on the left side.
Now for a odd issue with Google apps... I removed the Google Play Music Player, and disabled DRM/Downloads and made a few adjustments to Media Server. What happens is Music Player will cause playback automatically and Media Server will loop into high CPU usage even during reboot. DRM and Media server can cause this condition quite easily. So far Google is not working on a fix for JellyBean. Only KitKat has this fix, all other previous Androids,Gingerbread for example, do not have the issue. Corrupt files or files with _ or strange symbols will cause this loop until the tablet is turned off completely and restarted.
Click to expand...
Click to collapse
bro I will suggest you to take your note 8 to near by samsung service centre....
rabichowdhary said:
bro I will suggest you to take your note 8 to near by samsung service centre....
Click to expand...
Click to collapse
why??? I have no issues.
Oh here is more about draining batterys with 4.2.2
Many who don't have battery drain issues are running 4.2.1 or earlier.
Google Music Player after December 2013 will drain the battery on 4.2.2 ROMs.
Found Samsung OEM USB / Charging cables too weak and flimsy. Gone to Blackberry / Sony / Ericson cables, as they are the best in the business for OEM cables. Not only they are robust they have built-in passive filtering for high throughput connectivity. Also they allow for a good quality USB extension cable to be used with fast charging. I do not recommend any combined lengths beyond 1.8 Meters, or 5 Feet.
Use nomedia in folders not containing media on the SD card. If you are not sure about how to properly use nomedia, redirect your Internet browsers cache to SD, and copy the file from the cache directory anywhere that is needed.
Remove or edit any '_' in a media file's name, as media will run constantly when detecting an underscore.
Watch the data and battery tools in the android system, to assist in diagnoses of rogue apps running.
Beware of Xposed modules... I ran across a few that their updates caused slow booting and errors. Watch your Xposed log after a few reboots with any Xposed updates.
I'll repeat myself from the original entry on top of this thread... Watch for any module or app that has boost/benchmark capabilities. Disable it by all means. I have tweaked with OC tools with custom ROMs and found very little benefit. For those who scoff, here are my current battery and performance info for daily activities.
Charge rate while on AC and active: 20% every 45 minutes.
Sleep with Wifi on during a 12 hour period, total drain: 3%
Drain per hour while being active: 10%
Drain per hour Miracasting Netflix to tv: 12%
Netflix operation no lag or sync issues with high resolution. Note: this is with small tweaks with a stock ROM.
Even with performance tweaks for audio and CPU throughput. No overclocking or under volting was performed. I probably would get better battery drain performance by removing Viper4AndroidFX and keeping with OEM audio driver.
Here are my tweaks.
Xposed App Settings... 220dpi 1000x1600 even though stock parameters default to 320dpi, the system defaults to 180dpi and needs overridden.
360 security with active Android security patch update (Works when you do a manual full scan) and built-in app performance & cleanup tool.
Greenify & Xposed donation with Greenify extras.
Xposed boot manager.
Disabled Google Music Player.
Viper4androidFX set to Medium efficiency with Neon driver.
Trickster Mod with settings for 1024 cache, Zbuffer, and Ondemand set.
Hello,
Lately, my note 8 started to feel warm while I'm using it...
So I decided to watch CPU temperature using System Tuner:
https://play.google.com/store/apps/details?id=ccc71.pmw
First, temperature of the atmosphere here nowadays is about 35c to 40c...
for my note 8:
In idle mode, temp is about 40c, while normal using (wifi off, bluetooth off) like watch videos, using apps,
CPU temp is about 50c and battery is ~38c to 40c
sometimes while gaming, CPU temp could reach ~60c
The tab from the back left side is feeling warm
Is these temps normal??
What's your readings?
Note: I'm rooted on stock 4.2.2, and I didn't modify anything..
I just set the max freq at 1GHZ after overheating
AhmadLight said:
Hello,
Lately, my note 8 started to feel warm while I'm using it...
So I decided to watch CPU temperature using System Tuner:
https://play.google.com/store/apps/details?id=ccc71.pmw
First, temperature of the atmosphere here nowadays is about 35c to 40c...
for my note 8:
In idle mode, temp is about 40c, while normal using (wifi off, bluetooth off) like watch videos, using apps,
CPU temp is about 50c and battery is ~38c to 40c
sometimes while gaming, CPU temp could reach ~60c
The tab from the back left side is feeling warm
Is these temps normal??
What's your readings?
Note: I'm rooted on stock 4.2.2, and I didn't modify anything..
I just set the max freq at 1GHZ after overheating
Click to expand...
Click to collapse
Removing, disabling, or freezing Google Play Music will fix battery drain and temperature issues. Though there are thousands of apps that are buggy, since everyone has different tastes there is no real way to point out exactly what app outside of Googles Play Music that is causing drain without going into system and looking at battery. The top two items listed are the cause of your battery drain. Display should always be on top unless using GPS, Games, or Media without power adapter. Google's Play Music will cause Media Adapter to index in back ground. Depending on media type and media name, Media Adapter will run for 30 minutes to hours on end draining battery as well. 4.2.2 has a bug with media names, So using Windows or Apple's media management to create folder and names can be your issue as well. Search for any media with "_" in the name or folder.
gooberdude said:
Removing, disabling, or freezing Google Play Music will fix battery drain and temperature issues. Though there are thousands of apps that are buggy, since everyone has different tastes there is no real way to point out exactly what app outside of Googles Play Music that is causing drain without going into system and looking at battery. The top two items listed are the cause of your battery drain. Display should always be on top unless using GPS, Games, or Media without power adapter. Google's Play Music will cause Media Adapter to index in back ground. Depending on media type and media name, Media Adapter will run for 30 minutes to hours on end draining battery as well. 4.2.2 has a bug with media names, So using Windows or Apple's media management to create folder and names can be your issue as well. Search for any media with "_" in the name or folder.
Click to expand...
Click to collapse
Google play music is disabled long time ago.
I'm also aware of the media storage drain issue...
That's why I wished to upgrade to 4.4.2 to end the media drain issue.. but kitkat seems buggy too as many users confirmed that.
Also, I've no battry drain problem, it's just overheating!
My battery can last for about 8 hours without charing
ONLY OVERHEATING
AhmadLight said:
Google play music is disabled long time ago.
I'm also aware of the media storage drain issue...
That's why I wished to upgrade to 4.4.2 to end the media drain issue.. but kitkat seems buggy too as many users confirmed that.
Also, I've no battry drain problem, it's just overheating!
My battery can last for about 8 hours without charing
ONLY OVERHEATING
Click to expand...
Click to collapse
Sounds like a hardware issue... if still under warrenty on the Date of registration, I would do a factory reset and call it in.
gooberdude said:
Sounds like a hardware issue... if still under warrenty on the Date of registration, I would do a factory reset and call it in.
Click to expand...
Click to collapse
No, my warranty is void...
I downloaded 2 different apps to check the sensors in note 8.0
it doesn't have temperature sensor at all!
How system tuner could give me CPU temp?? or it's just fake?!
Hello xda. i need your help.
as you all know that the redmi note 4 mediatek version is lagging alot when you play even only mid game processing aplication. when i play games for like 5 minute it starts lagging allready. what i know is that when this device temperature gets 45 degrees, the CPU hotplug will lower the CPU frequency or turn off the other CPU cluster to prevent the device gets overheating and drains too much battery. but this will cost out our gaming performance and cause lagging issue.
so i've modified the thermal policy to bypass the CPU hotpug to get maximum performance out of this device but it only last for 10 minutes and it auto reboots when it gets overheating, but i dont care if this device gets hot because it is common for a mediatek chipset
You can do it by editing the build.prop and change the line ro.build.type=user to ro.build.type=eng and then go to mtk engineering mode and change the thermal policy setting.
for me this device is like not capable of doing anything more than being just like an old device except for whatsapp and other social media. it's like the device has a powerfull processor but only for decoration.
The only problem now is that the device will auto reboot everytime it gets overheating and needs to cool down in order to be used again. and my only question is how to prevent the the device auto reboot when we use the 120deg C thermal ?
I've recently upgraded old Nexus 7 to Nexus 7 2013 in my car semi-permanent setup.
This use case strongly reduces the selection of custom ROM/kernel combinations to support OTG with charging. I finally sticked to the special build of Glitch kernel (https://forum.xda-developers.com/showpost.php?p=72214133&postcount=2876) together with LineageOS 14 (https://forum.xda-developers.com/ne...rom-lineageos-14-1-nexus-7-2013-5-12-t3931482).
So far everything works like a charm with one very annoying exclusion: USB audio streaming runs into virtually continuous buffer underruns, which result in horrible glitching/cracking. Without a workaround described later it's unusable.
Somewhere I learned this is caused by CPU hotplugging implementaction of default mpdecision driver. Here is my investigation (questions are bold):
In Glitch kernel mpdecision is disabled by default, msm_hotplug is used instead. But still no help here. No other hotplug driver is included. Glitch development is dead.
I tried some tweaks of msm_hotplug in Kernel Adiutor. Strangely, switching it off leads to single core operation. So I kept if on and set min_cpus_online to 4, which effectively disables hotplugging (all cores are online all the time). This makes the glitches less frequent but is not a solution.
The only step which makes USB streaming usable is a workaround - running another CPU heavy app in foreground. This helps a lot (like 90% glitches are gone) and in car it is surprisingly easily achievable (e.g. a navigation app does the trick). Still, I would love to make it more robust:
I've tried alternative USB audio driver, namely the app USB Audio Player app. It works perfect. But only covers local files playback and music streaming services which I don't use (no Spotify, which is critical). I could not find any standalone driver. Is there any?
I was not successful trying other tweaks of msm_hotplug. Are there any settings proven to help USB streaming, which I overlooked?
I haven't successfully flashed any other ROM/kernel combination. There is effectively only ElementalX kernel v 5.16 (which in theory should be useable with LineageOS 13/Stock ROM) and old Timur services integrated in LineageOS (https://forum.xda-developers.com/nexus-7-2013/development/rom-usb-host-based-rr-timur-s-t3659332). There were problems which prevented me from setting up these ROMs. Is there any hope it could help?
nalott said:
I've recently upgraded old Nexus 7 to Nexus 7 2013 in my car semi-permanent setup.
This use case strongly reduces the selection of custom ROM/kernel combinations to support OTG with charging. I finally sticked to the special build of Glitch kernel...
Click to expand...
Click to collapse
With "no battery mod" you wouldn't be restricted to a special kernel/old ROM, nor worry about replacing the battery ever again.
Thanks. Interesting idea. But I need to keep my Nexus removable and usable outside the dash.
I did some more experiments. My assumption is that the USB buffer underruns are caused by CPU frequency scaling and/or hotplugging. So I tried to set the CPU governor to 'performance' and min_cpus_online=4. The cores were really all plugged all the time. For some reason they didn't maintain the full frequency (1728 in my setup), but still the available CPU performance was constantly overkill for what was needed. Still no help, audio glitches were roughly the same as in my standard configuration (CPU governor 'interactive', min_cpus_online=1).
The only workable workaround seems to be running a sufficiently CPU-greedy app in the foreground. Problem is that not all apps (which one wants to be running in the foreground) are sufficiently CPU-greedy. Thats why I'm trying to find a real solution.
I am having a very frustrating issue after moving to the S22 from my S9.
In direct sunlight, the screen is nice and bright and readable.
However, after a few minutes in the sun when the phone gets warm, it is automatically dimming the screen meaningfully - to the point where its really not readable.
I have tried both with Adaptive Brightness enabled and disabled. From what I have read it seems to be something the phone does automatically when warm to preserve battery or regulate the heat.
However it makes the phone unusable in the sun on a warm day once it warms up. Has anyone figured out a way to manage/disable this?
Use in direct sunlight should be measured in seconds not minutes if at all, not recommended.
You can severely damage the phone like this if it overheats especially if the ambient air temperature is high!
More than likely the phone isn't optimized and has a lot of junk running in the background contributing to high battery consumption and excessive heat. Tone it down...
thanks for the quick reply.
the phone is very new so shouldnt be that cluttered, and its having this issue that the S9 never had. Its not even 70 degrees today (although its direct sunlight) so its not like I am at the beach.
Would definitely welcome any suggestions on how to "tone it down" though as I would like to make sure I am having it run efficiently...
It seems strange that a brand new phone with better processor, etc should be having this issue in moderate temperature compared to the older phone I had for years...
Toss any social media apps; they should never be installed or activated if preinstalled like FB.
Try temporarily disabling Google play Services; gmail needs it(use manual sync) and Playstore needs it (enable/reboot for Playstore). Paid for apps that need Playstore; activate them, then use Karma Firewall to block Playstore so they continue to work. Firewall block those apps as well if they don't require a internet connection.
Samsung and Google cloud don't help matters, disable if you don't use them. Google Backup Transport* is a prime offender.
Set brightness to manual and keep at 50% or preferably less... don't burn your eyes out.
Clear system cache, don't use SmartSwitch to transfer from old phone... it can cause issues.
Don't use any of the Device Care battery optimization options as they cause erratic behavior and even increased battery usage. Only fast charging should be toggled on if you want it.
Instead find the power hogs and deal with each on a case by case basis. Set display to medium resolution ie the optimized setting and leave it there. If you run at 60hz that will also save power.
Disable carrier, Google, Google Firebase, Samsung and app feedback. Not sure if Package Disabler works with Android 12 yet, that's an easy way to clean up bloatware and easily toggle apps on/off if needed. Stay with the stock launcher as it's efficient and powerful.
Lol, it's a long list and some depends on your own desires/usage. Once optimized block system updates as they can undo everything... be careful before doing them, wait and see if and what issues they may introduce.
Play with it and explore... it's almost impossible to crash a stock Android
Be careful what you install though, you are what you load. One poorly coded app can cost you a factory reset if you can't undo its damage. Rarely, they can alter hidden user settings and this remains even if you uninstall the app! Repairing this can be time consuming and a pain.
*since you don't have an SD card slot to use as a data drive work out a good backup plan for all critical data or you will lose it eventually. A OTG 5tb flashstick can be used for frequent "dirty" backups.
In addition use at least 2 hdds that are physically and electronically isolated from each other and the PC to redundantly backup critical data!!!
Copy/paste folders/files only, Do Not use SmartSwitch to backup any critical data!!!
Like it's predecessor Kies, it can fail you miserably. Verify folder count and data size after a backup, spot check that the data is readable.
Once lost, data can rarely be recovered... plan ahead to avoid this sad fate.
thanks this is thorough and I will examine these things.
I guess my takeaway based on your response is - there is no way to disable whatever is causing the phone to autodim when it gets warm?
because I think its related to the phone itself physically getting warm from sitting in the sun (although I understand these things can exacerbate it).
I am not having any overheating issues other than when its warm out and the phone is in the sun and it then toggles down the brightness
lirong said:
thanks this is thorough and I will examine these things.
I guess my takeaway based on your response is - there is no way to disable whatever is causing the phone to autodim when it gets warm?
because I think its related to the phone itself physically getting warm from sitting in the sun (although I understand these things can exacerbate it).
I am not having any overheating issues other than when its warm out and the phone is in the sun and it then toggles down the brightness
Click to expand...
Click to collapse
Auto dimming is a last ditch effort to protect the phone. The display acts as a heatsink for the mobo as well as producing a lot of heat of it's own. The sunlight has a high infrared component to it.
Thermal stress is best kept as low as possible for OLEDs. The increased temperature causes expansion of the components; that could cause a failure by itself. The OLEDs are made of extremely thin layers (microns thick) so they could potentially overheat unpredictable fast as there's very little mass to them.
Best not to tickle the dragon's tail...
Hi there, just got hands on a S22 myself and observing this dimming issue. Obviously it's all about apps using GPS. I notice that the screen goes dim to about 40% max brightness when I'm in Google Maps or Locus Map. And this doesn't matter if Adaptive Brightness is on or off. Going back to any other app, the screen comes back to max brightness.
That's a no go as I'd buy the phone for my outdoor experience with Locus Map.