yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] ROX77:
Yes, you are right about my expression, of course usefulness is absolutely personal.

I hope to write better my concept: never said that there is not a power consumption and heat reduction (so Andrei I don't want to change the physical rules ;)

I only think that this reduction is so low, that I can't appreciate it in a day (I always have to charge one time in a day).

If you add the possibility that if UV is not perfect you could have fc, reboot, sod... that you take time to reach the right configuration, that maybe when you change kernel last settings are no more good and you have to test again... That's all, I'm speaking about "convenience" ;)
[Galaxy Note II Original Android Development] Admiral2145:
Where is the -1 button at for this guy...
[Galaxy Note II Original Android Development] cobraboy85:
Because he makes a valid point? How dare him.
[Galaxy Note II Original Android Development] emprize:
Seriously talk about 3-4% power saving for uv.....so if average use for 8 hours per charge, it around 15 mins....thats talking about you get the exact perfect uv value that wont cause fc, reboot and damage to hardware.

To test the actual amount for power save, if your daily usage is not exactly the same, the environment not exactly the same(sunny day vs cloudy day affect the brightness), the signal strength not exactly the same, the result will be different....is it really worth the effort to test it and change it to find the uv value? Not to mention every device has the different stability for uv even with same hardware
[Galaxy Note II Original Android Development] owl74:
No

It means Andreilux is very good at plugging holes :D

Seriously it means the security hole has been plugged that is why the exploit does not work. But that is only one hole that the exploit is trying to probe. According to Andrei there's more that he fixed silently on earlier kernel builds.

Next time try to read the op as the answer is there mate....

---------- Post added at 07:32 AM ---------- Previous post was at 07:26 AM ----------

Disregard the environmental variables. People are talking about juice saving. The fact is undervolting will save juice.... no matter how small you saved it is still savings.... and it may or may not buy you a little time but it is still a saving.... and yes it is worth the effort to some.
[Galaxy Note II Original Android Development] betoNL:
Some will say "Screen of Death" others will tell you "Sleep of death" or even "Standby of death" .

And unlike the "freezes" that you get when for instance dealing with OC/UV, SOD is another kind of "freeze", meaning screen goes black,while like any other "freeze" it will refuse to switch back on without being hard-rebooted and also appears to drain battery at an alarmingly high rate, causing completely flat batteries in most cases if not caught and forcibly rebooted.

It could be caused by other factors/reasons than OC/UV only.

Spontaneous reboots with or without getting stuck on splashscreen or bootanimation, are also NO SODs.

Anyway, no matter what kind of "freeze" you get, you don't need to "pull out the battery" as many still do, in order to get out of it:

Just press and hold power button till phone reboots.

.
[Galaxy Note II Original Android Development] Suicidal Chicken:
There's a lot of misinformed people in this thread, which I'm not getting involved with. I know as a fact, that undervolting is NOT useless, albeit the difference is negotiable.

The reason that I have capped it at 1.2Ghz, is for every day tasks; this is perfectly adequate.

1.8Ghz is for heavy multimedia, I.E gaming and outputting 1080p to my 60" LED TV.

I promised screen's, which I will share when I've got the time.

My heavy usage consists of the following: Watching 720p movies, perfect 'rip' meaning no data loss (I.E high bit rates,) streaming FLAC'S via A2DP (blue tooth,) YouTube, internet browsing, phone calls, Skype calls (Audio and video,) some gaming (hooked on the bard's tale; I highly recommend) and well, whatever I feel like doing lol...
[Galaxy Note II Original Android Development] snip3r77:
Normal usage for me can't even hit more than 1000mhz as I use CPUSPY to see which speed that I'm normally at. Then I bumped it down in those frequencies by 100mV or more :)
[Galaxy Note II Original Android Development] Suicidal Chicken:
I don't understand what you mean mate. I'm sure if you use an overlay (Cool tool, shows CPU clocks / core usage, battery temp etc,) you'll see it probably goes over 1Ghz unless you've locked it to 1Ghz.
[Galaxy Note II Original Android Development] betoNL:
Why you keep talking about undervolting?

In your case, you are actually UNDERCLOCKING. And quite a lot.

One of the reasons this phone is so expensive, is its power-house processor.

If you want to tame it that much, you should have bought a cheaper phone :laugh:

.
[Galaxy Note II Original Android Development] tdrussell:
This is the last i'll say about this in this context as i concluded my rudimentary practical testing last night. Over the duration of these tests (Monday night, tuesday night, wednesday night) i have not installed or uninstalled any apps and made no configuration changes to the phone other than those stated relating to the kernel. This is on wifi sitting about 20ft from my router.

Stock Kernel: 16% battery drain over 8 hour idle period

Perseus (stock settings): 11% battery drain over 8 hour idle period

Perseus (heavy undervolt based on Exynos voltage study results***): 7% battery drain over 8 hour idle period

If we extrapolate the delta in stock voltage (perseus) vs UV (perseus) drain out over a battery cycle assuming 100% idle time, we're talking about ~73 hours of idle vs 114 hours of idle. Obviously the delta is more dramatic if we use the stock kernel for the comparison.

***Note that i have run these voltages for over a week now and they are completely stable

on my device

.

1000mhz:1000000uV

900mhz: 950000uV

800mhz: 925000uV

700mhz: 900000uV

600mhz: 875000uV

500mhz: 850000uV

400mhz: 825000uV

200mhz: 787500uV
[Galaxy Note II Original Android Development] Suicidal Chicken:
No, I'm undervolting AND underclocking. No disrespect, but don't tell me how I should spend my money. Had you read what I've posted, then you'd know what my uses are. 1.6Ghz is overkill for what I need it for, however when I do need it; I can simply set it to 1.6/1.8Ghz.

The reason why i mentioned undervolting, is due to the posts a few pages back. I've only just had time to read what's been said, so I reiterated what my uses are.
[Galaxy Note II Original Android Development] bervin:
could we see screenshots of your changes?
[Galaxy Note II Original Android Development] Acorns:
Hmm, that actually seems really high. I've done some tests of my own, and at pure stock (USCC version) I get similar to you: ~2% per hour on idle (4g) or 2.2% wifi. Cleaning up wakelocks dropped that to 1.2% per hour (4g from here on). Switching to Perseus (no other changes) 0.5% per hour. Undervolting 0.3% per hour. I always measure from 99% down, as from 100% to 99% takes roughly the same time as any other 5% and skews the stats. After 99% though it is impressively consistent.

Given that the phone spends most of its time idle in most usage situations, I don't get why people say "undervolting has little or no effect". That is a HUGE effect. From 200 hours of idle to 333 hours of idle. Testing how much effect undervolting has under use is harder, but even if it had no effect it would still be worth it.
[Galaxy Note II Original Android Development] tdrussell:
That first statement may be the key difference as these were run in the middle of a charge cycle to avoid that very phenomenon. I'm inclined to agree that my idle drain is a little on the high side, but based on your corroboration i think it's at least consistent across kernel swaps. Thanks for adding your data.
[Galaxy Note II Original Android Development] Laynee1:
Can this kernel be flashed on stock odexed rom ?

And another question : how is it working with wanamlite rom ?
[Galaxy Note II Original Android Development] Mayday_XL:
AW: [Kernel][10/01][N7100 N7105 R950] Perseus

Yes.

Gesendet von meinem GT-N7100
[Galaxy Note II Original Android Development] Laynee1:
thanks for reply..

But what about my 2nd question ?
[Galaxy Note II Original Android Development] honki24:
Okay, so I haven't had any solution to my music stuttering with the screen off. I've found that my phone does great and doesn't stutter at all or very little when I go clear my RAM so that the only app running is google music. When I'm up towards 1.5GB RAM usage I see lots of stuttering. Anyone have suggestions on optimizations? I just barely started getting this issue on version 29, then worse in version 30, and still the same on 31. This has me confused because if it's a RAM issue I could be wrong but I don't see how the kernel has anything to do with that. I'm totally default settings to reduce variables. (I'm on the sprint SPH-L900)
[Galaxy Note II Original Android Development] tdrussell:
I will try to test this.

are you streaming or do you have it stored for offline playback?

---------- Post added at 02:34 PM ---------- Previous post was at 02:25 PM ----------

Well that wasn't difficult. I can easily reproduce the stuttering on Wifi and LTE, streaming from google music, no audio changes made to stweaks or any other apps. hmmm...
[Galaxy Note II Original Android Development] honki24:
Thank you for verifying! Yeah, it still stutters even when I have the music locally stored (no streaming). I've noticed that clearing RAM works for a while (until background apps open and consume more RAM) and so does increasing min freq for responsiveness to like 1GHz... but I know that is not a good solution.
[Galaxy Note II Original Android Development] cobraboy85:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

Good mother of all hell this thread has gotten ridiculous.

First of all I will say this. People with this insane battery drain - speaking of those who have reported anything more than 1% an hour. This phone has a 3100 mAh battery in it. Your issue is not kernel related. Your issue is yours. Read carefully, because that does make sense. When I let my device sit over night, typically over 8 hours I'll see MAYBE a 4-5% drop. Maybe. And I have Google Now running constantly. All of it. So don't blame it on that app because it uses very little resources on this device. Same with your auto sync.

Second, if you are SOO freaking concerned about saving power that you cripple your processor to 60-75% of its ability, you should buy an iPhone with a tiny ass screen or you should get a bigger battery for this device because then your changes to increase power efficiency will actually be noticeable and your $700 you spent won't be an utter waste. You can't even tell me that under clocking makes such a huge freaking difference for your daily routine and saves you from having to charge your device a bajillion times that it is even necessary. Sorry, but yes I am ridiculing such behavior because it makes absolutely no sense to buy a device with a brilliant 5.5" display, a quad core processor and powerful GPU then expect it to be a godsend in power saving capability, and to be honest, even that being said it does pretty damn good considering. What I don't get is this rampant way of thinking where you pay for such hardware and feel the need to take one of its legs away.

Let's do some math here. 1.6x4=6.4 (this is total processing capability in GHz)

1.2x4=4.8 GHz.

Your quad core is now a tri-core. You have just removed an entire core from the equation in raw processing power capability. So when people ask you what kind of processor you have, don't tell them the exynos 4012. Tell them it is a tri-core CPU. That way they aren't confused. Then tell them how you save sooooooooo much battery life throughout the day by doing this.

You might as well disable an entire core and run it at full speed, at least then you will get the performance out of the higher frequencies. And theoretically you would save more power. The voltage difference between 1.2 GHz and 1.6 is pretty unnoticeable. But shutting off an entire core isn't when speaking of physically active cores. At least by doing that you aren't limping around on the active ones.

And music stuttering during playback has nothing to do with your RAM management. But it could have something to do with your IO scheduler, or a screen off profile for the CPU. I have been listening to music over Bluetooth, through headphones, etc ever since I have had this device from day one. Even stock software/Firmware didn't have that issue. It is something you are doing to it. Look into that.

Amazing folks. Simply mind blowing conversations going on in this thread.
[Galaxy Note II Original Android Development] tdrussell:
I give up. Lets return to discussion about the kernel.
[Galaxy Note II Original Android Development] poczynek:
It is sort of funny to watch nerds argue though. And as long as it gets one day battery out of it then who cares? You just recharge over night!

I for one love this kernel and it's battery life is amazing (and to be honest would not change the kernel because I'm scared of the Dev going off at me!). He'd find out - I know it!
[Galaxy Note II Original Android Development] garyd9:
Geeks... Not nerds. No reason to be insulting.
[Galaxy Note II Original Android Development] poczynek:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

Insult?! Compliment! They run the world!
[Galaxy Note II Original Android Development] gabamoner:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

If I overclocked my cpu to 1800mhz and undervolted it.. will it be safe for my cpu ?? Or it is still prone to faster destruction??

Sent from Godfather Gt-N7100

A TRIANGLE AWAY will make your WARRANTY stay

Hit thanks if you love your phone =)
[Galaxy Note II Original Android Development] owl74:
Same as with computer cpu's, overclocking can post a risk when it uses more voltage than the max voltage it is designed to use. Undervolting on the other hand will not damage the cpu but can make your device unstable if too much undervolted. This is why you have to test for stability when undervolting to make sure thw cpu runs properly.
[Galaxy Note II Original Android Development] shawnx1:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

I still have a OG DROID overclocked way more than 200mhz and over volted and is still kicking I use it as a rdio player everyday. Just my 2 cents most likely you will move on to a new phone by the time over clocking kills your phone Knock on wood...
[Galaxy Note II Original Android Development] twe90kid:
does this news also apply to us?

http://www.gottabemobile.com/2013/0...te-n7100xxdll7-causing-battery-life-problems/

I know that R31 seem to drain much more than previously because the exynos fix has been changed to Samsung's fix.
[Galaxy Note II Original Android Development] Evermind10:
well, if you read the change log, it says that the latest kernel is updated with the samsung fix.
[Galaxy Note II Original Android Development] bervin:
He wasn't referring to the fix but the apparent drain that has been reported by the fix. I'm curious to know what Andrei has to say on this
[Galaxy Note II Original Android Development] EdgaBimbam:
for me perseus latest is way better than with stock talking about battery life.
[Galaxy Note II Original Android Development] SirCanealot:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

My battery life is as good as ever. Solid 2 days. But I started playing the band's tale again, so we'll see what it's like!

And yes, needs arguing is awesome. They like to just basically dump all of their knowledge to prove someone wrong, so it can be interesting for other people to read. AndreiLux when 'mildly annoyed' is generally very informative and interesting! :p
[Galaxy Note II Original Android Development] jauhari:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

Wow 2 days? Can you share your configuration, settings, ROM etc please?

On me plug off changer 04.30 AM, on 19.00 battery 10% left. :(
[Galaxy Note II Original Android Development] Evermind10:
+1 for waiting for Andrew's comment

I'm on swed LL4 with perseus 31.2 and.. Yeah, it does drain a little more than usual. But it could just be me.
[Galaxy Note II Original Android Development] Operative:
[Kernel][10/01][N7100 N7105 R950] Perseus

Hi bud, is this with wifi and continuous data? :)

Sent from my GT-N7100

Rom: Android Revolution HD 8.0

Kernel: Perseus 31.2

Rescue: TWRP 2.3.3.2
[Galaxy Note II Original Android Development] twe90kid:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

Some people just can't take the time to read

Sent from my Galaxy Note 2!
[Galaxy Note II Original Android Development] betoNL:
I was being ironical of course and at least I didn't suggest you to buy an iPhone (which is also not cheap).

Now speaking seriously : Power on demand? I mean , un-crippling when necessary? Doesn't make much sense does it?

What are the schedulers and governors and the bunch of available tweaks for?

There are many ways of having fun with this beast other than crippling it.

I think that everybody is forgetting what an amazing battery performance this phone already got, out-of-the-box, specially in comparison with almost all high-end smartphone out there even with smaller screens (if not all).

And once again, I am not talking about undervolting which I gladly do, just for the fun of trying to squeeze even more juice out of this already super energy-efficient device.

But that's how I handle MY device and I am more than satisfied.

If you are satisfied the way you handle yours, so.... everybody is happy...

No need for further discussions.

.
[Galaxy Note II Original Android Development] AndreiLux:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

The new sources have some regressions in terms of power management in them, maybe the stock kernel is affected by that. I don't know and can't prove it though, but you could check it by monitoring hotplug behavior on the stock kernel. I don't even have a Note 2 though.

The kernel here though shouldn't have any battery life changes since v30 though and the fixes don't affect battery.
[Galaxy Note II Original Android Development] betoNL:
How do I do that? There is no Hotplug governor available on stock kernel or I just don't know what you mean :o

However on stock, using the pegasusQ governor and with CFQ scheduler, I didn't notice any regression so far.

Actually the pegasusQ governor is definitely my favorite.

And undervolting even more than what I posted before, seems to be more stable than on re-compiled kernels, but nothing conclusive about that so far.

.
[Galaxy Note II Original Android Development] yahyoh:
HMM i just installed stock LL7 kernel and seems there is bug with hotplugging it takes forever to turn off cores and sometimes for weird reason its goes to 800Mhz and i'm doing nothing ( just in text message and no apps in background ) :eek: and sometimes the cores stuck @200 Mhz without getting off :silly:

( this just a small test though ) ;)

now back to Perseus :)
[Galaxy Note II Original Android Development] SirCanealot:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

Tbh, the biggest saver for me is turning off all sync and location services. I can live without them. Then making sure there's nothing stupid waking your phone up. I have brightness at bottom 90% of the time. I turn off notifications in everything.

Other than that, perseus defaults apart from as much uv as I can get away with. That and 1800mhz oc! :)

You'd be surprised how much DUMB drain you get from Google services :(
[Galaxy Note II Original Android Development] hieupham:
@Andreilux - could u pls comment on the kernel UBDLL3 ? Is it newer than the DLL7 or it's the same? And most important - has it fixed the sudden death issue?

THnx many many!

http://xdaforums.com/showpost.php?p=36876307&postcount=1680

Changelist: 749832 UBDLL3 vs 679347 DLL7
[Galaxy Note II Original Android Development] honki24:
I will try to pull out any scrap of helpful information that I can from that very proud and over-reaching post. I can see that your logic is "if it isn't this way for me then it's user error". Understood. I am a huge proponent of this kernel (I'm the one that requested and helped facilitate this kernel be ported to the Sprint SPH-L900) and I fully recognize that I'm learning still and I pale before the knowledge of Andreilux here. This is why I submit my "bug reports" here and hope for him to be able to find out if there's anything he can do.

On all kernels prior to 29 I NEVER had skipping. Just before flashing to 30 I noticed very infrequent skipping (with screen off). On 30 and 31 I have significant skipping with screen off.

((Note that I use Google play music only. No spotify or Samsung or other))

I don't profess to know the answer but I'm simply noting what I've tried. If I increase min freq for responsiveness to inadvisable levels (1GHz) it fixes the problem. If I clear the RAM of all background processes it fixes the problem (until more background processes open). I don't use profiles or have SetCPU installed. I use STweaks, and for troubleshooting reasons my settings are completely default. I don't know much about the IO scheduler so I'll look into that, thank you for the scrap of help that you've offered.
[Galaxy Note II Original Android Development] AndreiLux:
Well I can't really go and start decompiling kernels here now can I.

Open the zImage kernel binary in a hex editor and search for the string "VTU00M" in it. If it's included, then it has the MMC patch.

When booting, check your dmesg for the sensorhub version embedded in the kernel.

When turning Wifi on and off, check your dmesg for the Wifi driver versions embedded in the kernel.

Sensorhub in the outdated sources are 92600, new versions should be 102600 or so, with the Wifi driver being also something older but I don't remember the version.

It sounds like hotplug regressions found in sources older than November. 800MHz might be the touch booster?

I gather the skipping only happens with the screen being off? I changed LPA residency times back to higher values in version 30 to fix the reboots people have had. I'll see what I can do against that, but it's a very odd problem since only Note 2 users are reporting it, and then again, only a few from many.
[Galaxy Note II Original Android Development] yahyoh:
hmm test it again :

seems i cant get any cores off with very very light usage from prefmon app : http://xdaforums.com/showthread.php?t=1933284 then i turned off the screen then the cpu get up the device from sleep with 2 cores and stayed until some high usage the device turned one more core and core 3 still on sleep but the i cant get any of the other 3 sleep while prefmon running :eek:

but then i tested it with system panel app : i went to browser opened many sites then closed everything from task manager then went back to system panel app and it took about 20-25 sec to turn off core number 2 then about 10 sec to turn off core 4 (and core 3 was already sleeping) while no loading at all no touching either :rolleyes:

is that normal ? :cyclops:
[Galaxy Note II Original Android Development] hellDr0id:
How to add more Governor's

Hey Folks,

I want to add more Governor's in Perseus kernel like interactive , ondemand

is this possible ??

if yes then how we can add ??

I am using Omega v10 Rom with Perseus alpha31.2 n7100....

thanks in advance..
[Galaxy Note II Original Android Development] yahyoh:
u can't

no

stay with stock kernel PegasusQ cuz its working great :cowboy:
[Galaxy Note II Original Android Development] SirCanealot:
Re: [Kernel][10/01][N7100 N7105 R950] Perseus

Andrei has said there's not really any point adding other governors since peq can be tweaked to do basically anything now :)
[Galaxy Note II Original Android Development] bervin:
Anyone has got recommended settings to make pega more battery friendly. I'm not familiar with tweaking these quad core cpu governors. I find that my phone scales up to 1600mhz too easily. It's on par with 200mhz in terms of usage time at that clock speed