Im using twrp recovery for this kernel?
Sent from my GT-N7100 using xda app-developers app
Yep you have to flash it via recovery
All recovery is good
I'm using twrp
You have to manually flash the recovery, isnt in the kernel package
Im using twrp recovery for this kernel?
Sent from my GT-N7100 using xda app-developers app
Yep you have to flash it via recovery
All recovery is good
I'm using twrp
You have to manually flash the recovery, isnt in the kernel package
Hi guys,
just installed fresh SentinelROM 4.8 (and CWM PhilZ Touch 4 6.0.2.8) and now trying to install this kernel - however after installation, reboot and "Samsung Note 2" logo the screen just goes black and nothing happens?
I installed the N7100 CWM version of this.
I was hoping so as well, but tests using stweaks made no improvements in volume for my anemic Plantronics Voyager Legend. Anyway, it's going to the service centre to be replaced for poor incoming audio when on Wifi, perhaps the replacement unit will be better.Since this kernel allows so much control of sound, can "in theory" it control volume/quality for bluetooth too?
And also could it have separate volume control for in-call?
Since this kernel allows so much control of sound, can "in theory" it control volume/quality for bluetooth too?
And also could it have separate volume control for in-call?
BT will only stream the digital data to the receiver. The BT receiver - headset or car or anything for that matter - has its own DAC, which means changes you make in the way the phone's DAC reproduces sound will not affect the Bluetooth...I was hoping so as well, but tests using stweaks made no improvements in volume for my anemic Plantronics Voyager Legend. Anyway, it's going to the service centre to be replaced for poor incoming audio when on Wifi, perhaps the replacement unit will be better.
You shouldn't bother replying, Andrei...
Sent from my GT-N7100 using XDA Premium 4 mobile app
Does undervolting achieve better battery life or worse?
Sent from my SGH-T889 using xda app-developers app
Better. Too much uv could have opposite effect though.
Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
I am running a stock and debloated touchwiz ROM using the US CELLULAR kernel version. MY question is what is the best way to achieve high benchmark scores? I am using AnTu and I can't get above 1700's
Get your head out of your ass, it's not about disagreeing or not, it's about the facts/content you disagree on. You're don't have immunity to criticism and neither do I so don't get upset when you are being called out on something.I'll do that. And I'll be sure you get a pm when I do. Also, you won't have to worry about your device rebooting anymore.
Have a nice day folks. Sorry for disagreeing with the almighty god
The point of undervolting is that it is a disadvantage free method of gaining power efficiency, and it can bring down the dynamic power usage on the SoC down, from, let's pull it out of my ass, 20% by the best estimates from what I have measured over the last year. If you have instabilities then it is your fault in your methodology because you are undervolting too much. We are merely eliminating a manufacturers safety margin by undervolting.Some of these frequencies are set almost -100mv. Processors nowadays are becoming very efficient on power and are absolutely DWARFED by the amount of power your display, radios, and other hw uses. My own personal opinion is to look at other power consumers such as the aforementioned before playing with hw that in the grand scheme of things is not your biggest power consumer culprit, yet is vital to system stability.
No the sampling rate is not when the CPU is polled for load, it's the periods between which the governor does DVFS decisions, load is merely a statistic of the reverse of how much time the CPU is in idle.SAMPLING RATE: 28000 - just to be clear, the sampling rate is the interval of spacing between CPU being polled for load. Use this as you see fit, the small the interval, the more it checks for pending tasks to be executed. I have found great success and performance (and accuracy and decreased latency) with 20000-15000. Battery will not suffer anything noticeable to the end user.
Same thing, again, absolute nonsense as with the CPU voltages above. Internal voltage especially can bring power gains, albeit it is much less than the CPU, but it is a free gain.honestly, I really don't see the need to mess with this either. More potential instability for a minimal gain in battery when analyzed against your main thieves of your voltage - display, radios.
Deadline is alright, but noop just means that you are turning scheduling off. It doesn't bring you any performance gains at all, you are better off using an IOPS and latency designed scheduler like ROW or FIOPS (I'll bring that back when I have time), again, Deadline is ok, and SIO is a compromise of everything.dealine and noop will give you the best performance on these devices in real time, data speeds are also increased significantly with these two IO schedulers.
Maintenance, logging???!!! These are tasks that do not even remotely task the CPU even at 200MHz with any significant load, any single process out there running in the background can be done at 200MHz, it is more power efficient and you are not even aware of it.Also, if i may add this... I would recommend bumping the min frequency to something like 500MHz for the CPU. Reason being is simple - smaller tasks (maintenance, logging, etc) can be handled with ease without causing unnecessary CPU ramping.
So you see how that whole last paragraph of yours is just nonsense and that last phrase is really something one might take out of a PR article. Your settings you suggested were not given more thought.THIS is performance without battery life taking a hit - making your system AGGRESSIVE YET EFFICIENT, not hindering and crippling it to not do what it is programmed to do. Efficiency. "Less is more" as you see thrown around in the Linux world can also be thought of as more is less if you think in terms of more thought, tuning, and logic is less power consumed by your device.
Yes please do deliver your kernel, because I want to see more nonsense delivered with an attitude. We already have a large amount of clueless developers on this site. The problem isn't that they're unskilled or do not know the technical details, everybody was like that including me; It's that they think they are doing some sort of meaningful change without giving the effort of thinking or dwelling into the topic more than 2 minutes. People are suffering from a severe case of the Dunning-Kruger effect (I was so happy when I found out there's a name to that attitude).I'll do that. And I'll be sure you get a pm when I do. Also, you won't have to worry about your device rebooting anymore.