Develop Bugs

[Q] Screen won't turn on after timeout (cm7)

Screen goes black wont turn on power button and volume rocker unresponsive. Have to pull battery everytime. Disabled the lockscreen. Any suggestions

Turn on screen animation, turn min CPU up from 128 or whatever. If it keeps up you might have to reflash
Sent from my PC36100 using xda premium

Has anyone consistently had this problem, and then had it permanently fixed by raising the minimum CPU speed or re-flashing their phone? My friend and I both have Nexus S, both on CM7, and both have this issue of perma-black screen with non-responsive volume rocker/power button. The 4 capacitive buttons at the bottom (turned on due to a notification?) respond to touching and blink (turn) off when pressed and re-light when released. Screen animations are on, lockscreen is enabled. This has only started happening after rooting and flashing the CM7 mod, and not on an unrooted stock rom.
Should I be increasing the minimum CPU speed, or increasing the maximum CPU speed? I have SetCPU and am currently on smartassV2 when screen off, which has CPU speed from 100-200 MHz. Since the phone goes to deep sleep anyways, would I need to be raising the deep sleep cpu speed (is it 0?) to over 128, or what? The maximum speed is already over the 128 MHz, and the min speed of 100 MHz shouldn't have an additional effect (since deep sleep is already lower than 100 MHz).
Is a reflash necessary, or just a wipe of the cache/Dalvik cache?
Anyone with personal experience in fixing this issue?

I had a a similar issue and I found that for some reason with my phone and particular roms I just could not use them. Not 100% sure Y. I would try a different Rom and see if the problem happens again.
Oh and if you are going to re-install the same one again to make sure it was completely done I would wipe both caches and user data just to be sure.

Power Saving mode with customer kernel and OC settings

Does Power saving mode still work when using an app like SetCPU, or do the OC apps overrule the CPU underclock setting of that mode?
I understand that power saving mode does other things as well as just underclock the CPU (ie lower brightness etc), but I was specifically thinking about the clock settings.
I've not decided whether I will OC or not yet. I will definately play with the voltage settings though. I'm finding that my tablet gets extremely warm in the lower left hand side when put under intensive use. But back to my original point. Id like to be able to underclock it on the fly at a push of the button and find im enabling that setting alot with the stock set up...
Thanks

How to increase max brightness on power saving mode?

I found that I get better battery life if I keep power saving mode on during my daily use, problem is that it lowers the screen brightness too low sometimes even when slide to max brightness. Is there a way to retain my brightness on normal mode when I am in power saving mode?

inspireyue said:
I found that I get better battery life if I keep power saving mode on during my daily use, problem is that it lowers the screen brightness too low sometimes even when slide to max brightness. Is there a way to retain my brightness on normal mode when I am in power saving mode?
Click to expand...
Click to collapse
You can try lumos brightness manager but you will no longer be able to use the slider in the quick menu.

You may want to try the app "Night Screen" as well.

What does Battery Saver Mode "Extended" actually change?

The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.

BasicallyCP said:
The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.
Click to expand...
Click to collapse
Only thing I've noticed is when I have my phone set to Extended and I've set Max Brightness to 80%. However, I've seen my Brightness go over 80% on Auto especially when I was outdoors (saw it hit 100% and Boosted). Under Manual Brightness, I can have it go to 100% too. So that 80% is misleading?

Good find. I was wondering too since the prediction page instantly applies a gain in standby hours (and a significant one at that) by just enabling the "max brightness" feature. Since it can not know when or for how long the display will be on and what range the "auto" feature will use in a given situation, it seems like a very optimistic value, especially if you just use a limit of 95% for example.
But regarding your question, it's indeed strange to see "auto" exceeding the max brightness limit. I mean, the limit is there for the auto mode only. Might be a bug, unless we struggle to see the logic behind acting like that.
Personally, I would leave max brightness alone since it's more useful to have the display ramp up to max in order to actually see something when needed. If "auto" generally sets up the display as being too bright, one can still adjust the slider (even in auto mode) to tune the point of optimal brightness. I think it acts as an offset to the actual (internal) value the automatic comes up with. At least, that's how I perceived the feature on this and other phones so far.

Question Adaptive Brightness - Disable maximized "Sunlight Mode"?

Hello!
I bought a Base S22 a few weeks ago and so far, I'm loving this device. But one thing that bothers me is the adaptive brightness implementation from Samsung, because its not really "adaptive". Even on some cloudy days, the brightness gets maximized and I can not change it to a lower level, because I always get the "maximized for best viewing in bright light" notification. In all other scenarios the adaptive brightness algorithm works perfectly.
Is there a way to disable this kind of behavior?
My current solution for sunny days is a Bixby routine to quickly disable adaptive brightness when I'm longer outside to save some battery.

Use manual brightness control. Adaptive brightness never worked right... no surprise it still doesn't.

You can manually lower the brightness even in adaptive mode, and hopefully it will adapt to you too.
Another options are:
- Battery Saving mode has optional "10% lower brightness "
– Battery Guardian module of Good Lock (with dependencies!) may be configured to lower brightness when phone's temperature is high

MakaanPL said:
You can manually lower the brightness even in adaptive mode, and hopefully it will adapt to you too.
Click to expand...
Click to collapse
That never works right either... The only draw back to full manual is finding the slider in bright light to jack it up. Auto is easier to temporarily use then. That said using the device in direct sunlight should be limited to seconds not minutes. Avoid whenever possible.
50% or less is best for battery and AMOLED conservation.
Using manual brightness control saves battery, display and your retinas

MakaanPL said:
You can manually lower the brightness even in adaptive mode, and hopefully it will adapt to you too.
Another options are:
- Battery Saving mode has optional "10% lower brightness "
– Battery Guardian module of Good Lock (with dependencies!) may be configured to lower brightness when phone's temperature is high
Click to expand...
Click to collapse
The problem is that the phone puts the brightness to the maximum and locks it there in bright light. Even when I use battery saving to lower the brightness by about 10%, it doesn't let me change the brightness to a lower level.
I don't know if this is just a thing on Samsung phones, because I heard that they use the adaptive brightness algorithm with KI from Google.

Mayamos said:
The problem is that the phone puts the brightness to the maximum and locks it there in bright light. Even when I use battery saving to lower the brightness by about 10%, it doesn't let me change the brightness to a lower level.
I don't know if this is just a thing on Samsung phones, because I heard that they use the adaptive brightness algorithm with KI from Google.
Click to expand...
Click to collapse
Which is why I use full manual control almost always. Invariably auto is many time too bright and has a tendency to "jump" around. Lol, human vision in much more adaptable and its nearly seamless.
The brightest stars burn the quickest... my plan is to have a display that's perfect for the life of my heavily used devices which likely will be in excess of 4+ years. Batteries are easy and cheap to replace, the displays aren't. Samsung's plan is to sell you a new phone every year.