I have a rooted **Samsung Galaxy S22 Ultra** (**SoC: Snapdragon 8 Gen 1**) and want to control RAM clock frequency (DVFS). How can I perform RAM DVFS on a Samsung Galaxy smartphone? First of all, I tried searching available governors. And the followings are the governors of S22 Ultra.

/sys/devices/platform/soc/1d84000.ufshc/devfreq/1d84000.ufshc/available_governors
/sys/devices/platform/soc/3d00000.qcom,kgsl-3d0/kgsl-busmon/devfreq/kgsl-busmon/available_governors
/sys/devices/platform/soc/3d00000.qcom,kgsl-3d0/devfreq/3d00000.qcom,kgsl-3d0/available_governors

By the way, 1d84000.ufshc is related to ufs storage, and 3d00000.qcom,kgsl-3d0 is related to GPU. Thus, there is no system file related to LPDDR. Besides, I found a directory /sys/devices/system/cpu/bus_dcvs/DDR also. However, the system files on this directory do not allow files modified. Additionally, at soc:qcom,memlat:ddr:gold of the previous directory, I tried modifying max_freq system file though. The result was not changed. Is there anyone who knows about how to control **Memory DVFS on Galaxy S22 Ultra** smartphone???

I'm planning to buy a new android smartphone, and I've heard that while high processor clock speeds are good, they are also accompanied by high heating effects. Is there a way I can obtain the heat (in watt possibly) and the clock speed (in GHz) of the processor? (I'm quite new here, and I'm not really a very informed person when it comes to anything digital technology).

Hello Masters of Android! I am using Galaxy S5(SM-G906S)(Qualcomm SnapDragon 801). I have a problem. The problem is that I can't handle CPU Max Clock.. Available Max Clock is 2457Mhz but system always set to 1728Mhz.. It causes some lags... How can I Solve this.. I already did factory reset using Kies...

I know that SSDs wear out with time but it takes a long amount of time for the wear out noticeable affect performance (not 2 or three years). I can TRIM the SSD as far as I know to bring back it's old performance. I believe that RAM and CPUs/GPUs don't slow down with time (not 2 years that is usually the amount of time after which people start feeling like they need a new phone). So is it possible for a phone to be as fast as it was 2 years ago if the apps in the current age are also not more CPU demanding than they were 2 years ago? PS. also my last question is unanswered so please consider replying to that

I'm using the App ClockSync on a Android 7.0 device (Huawei P9 Plus) and on a Android 5.1 device (Huawei MediaPad M2) and I face two problems. 1. I'm synchronizing the time with ClockSync on my Huawei P9 Plus device. When I then restart the device, the clock has a local offset of around 76 seconds. Why is that? By the way the device is rooted (TWRP). This only happens when I restart the phone. 2. On my Huawei MediaPad M2 device the local offset of the clock (shown by ClockSync) increases over time. After one hour I have an offset of 1 second. How can I decrease this massive offset? Automatic time synchronization is no option because I'm recording sensor data and I don't want to have a sudden jump in the timestamps. On the other hand on my Huawei P9 Plus device the offset is not monotonically increasing but just jumps around and is always lower than 1 second. Why is the local offset jumping around? I have disabled automatic time synchronization in ClockSync and also in the system settings.

My alarm clock app has been occasionally failing to ring in the morning, but I don't believe the problem is due to the app. In other news I recently added a lock screen app that happens to display the time in two locations on the screen (one from app itself and other my widget) and on days when the alarm fails to ring I noticed that the second clock just stops, (which today says 3:52 am) I have been checking the two clocks before bed, but last night when I checked it was good, yet the alarm failed this morning and now the times are different I presume there are two internal clocks and the lock screen and alarm app are both using the problem clock, which is probably being killed by some task killer. I can't afford to oversleep again! Have Note 3 with latest android update Any ideas?

I know that T-Mobile clocked it down to 384 to extend battery life on the G1, and I believe that the processor was designed for 528. With all that said, does anyone have experience with what a good, safe speed is? I'm new to Android (less than 1 week), so all this is new to me. Thanks! Update: the processor is the MSM7201A.

Okay, here's the deal- I received a generic Chinese tablet from a friend in early January, and it worked well for about two-and-a-half months. Then, just recently, I discovered rooting and the wonderful things it allowed you to do, and my problem followed shortly after. I decided to download a system-tweak app, which included a CPU control. I was a little wary of overclocking my CPU, having heard it may decrease its life expectancy, but finally I thought "What the heck?" and in a brilliant stroke of genius cranked my 1Ghz processor up to 1.5Ghz, and it promptly froze, forcing me to power it down. When I turned it back on, I discovered that it had been factory reset. I re-installed my apps, including the system-tweak app, and decided not to touch the CPU controls for a while. Soon after, while at my sister's talent show, I discovered I had about 30% battery life, and I was still supposed to record her. So I figured I'd underclock it to save the battery. Unfortunately, as my finger touched the slider, my brother bumped my arm and caused me to lower the CPU frequency to its lowest setting. It became extremely sluggish, almost to the point of being unresponsive, and finally I had to shut it down. When I restarted it, it started to boot but then got stuck on the shimmering Android logo, and now that's all it does. I can't even boot into recovery mode, and unfortunately I had just turned off USB debugging that same day. I would like to know if there's any way to get it working again, and if so, how. Any help would be GREATLY appreciated!

I have a Beaglebone Black which runs Android. It has a 1GHz CPU. Bu when I read it's clock speed from adb I got 300MHz. I'm using following commands: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq All of them returns 300000. I'm using Android image from Texas Instruments. Is tehere a problem? Is my Beaglebone Black running on 300MHz or is it just a system error? I try couple of apps to learn my CPU speed. All of them says 300MHz. But i think they are reading those files too.

I am going to overclock my 600 MHz to around 700-800+. Nothing too big of a jump, and don't need any help either. The question I'm concerned about is what kind of performance does this slight speed increase yield? Will it make any big difference that can be noticed? Note that this is simply overclocking the CPU and changing **nothing else** with my configuration in idle. I have heard some argue that raising clock speed alone doesn't really guarantee better performance, since microarchitecture and bus speeds are what determines ultimate performance. For example, on Super N64 emulator I am getting like 7 frames per-second running Super Mario 64 on my current 600 MHz. Will the increase make any immediate difference? How can this be properly estimated by incremental clock speed, etc.? Will some apps run faster, will more background apps do their job better, will I execute/boot faster, etc.? Basically, I want to know what to expect within the range of aforementioned clock speed increase.

Can it be done? I'd like to be able to set clock limits based on a number of conditions, such as battery temperature, charging/not charging, and what radios are turned on. I'm aware that there are apps for rooted phones that will allow me to do this, but I'm wondering if there are any that don't need my phone to be rooted.

I have tried a few alternative ROMs, and underclock using SetCPU, but I can't seem to find a truly effective way to have my Samsung Skyrocket's battery last for more than a day. My average usage time adds up to around 1 hour per day, comprising mainly of sending texts or looking up something with the browser. Is the Skyrocket just battery-inefficient by design, or is there something I am missing? EDIT: It seems that formatting everything/factory resetting/reapplying stock ROM seem to help significantly enough that it's no longer an issue.