yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] aamitabh28:
Awesome!!

Downloading. Wl report back asap!

Thanks man
[ONE Original Android Development] NuLLV01D:
[MENTION=5438598]RenderBroken[/MENTION]

SlimSaber Boots!!!
[ONE Original Android Development] RenderBroken:
What?! Get out of here. . .lol Glad to hear. Now I can finally give it a shot! If no one has figured out by now, I like to run my own kernel and have been wanting to try SlimSaber as well.
[ONE Original Android Development] _ASSASSIN_:
Just wondering, why do you use the westwood TCP algorithm? I personally find that cubic is the best when I'm browsing
[ONE Original Android Development] RenderBroken:
I personally just have had better experiences using Westwood for the longest time. I will swap back to Cubic just to see how it does.
[ONE Original Android Development] abhi08638:
Working great on beanstalk
[ONE Original Android Development] smoki3:
Does it include cm12.1 commits
[ONE Original Android Development] RenderBroken:
yes
[ONE Original Android Development] smoki3:
Great work. Does boot on cm12.1
[ONE Original Android Development] usmani:
Never mind. Sorry I went blind.

Awesome work really liking the percore boost functionality (y)

---------- Post added at 05:40 AM ---------- Previous post was at 05:39 AM ----------

Yes it's working fluid on euphoria 5.1
[ONE Original Android Development] RenderBroken:
They are set to stock by default. Stock is 2A.
[ONE Original Android Development] ahaq:
How would be do a clean ram install if I am on ak
[ONE Original Android Development] usmani:
Btw the default logic is something like when the screen is on the current is topped at 1A-1.2A and when screen's off its at 1.8A. So will this not override that?
[ONE Original Android Development] Renosh:
Dirty flash ROM then flash Render R3
[ONE Original Android Development] clockworkstop:
Dirty flash your ROM and then the kernel you want to clean your ramdisk.
[ONE Original Android Development] RenderBroken:
You will have to do a clean install of the Rom with its stock kernel/ramdisk. I mean, my kernel should work fine when flashed ontop but it could also cause issues that people relate to the kernel when the problem is really a user issue

.

Still not an issue. If you set it so MAX current is 1A then that's the MAX current allowed no matter if screen on or off. You are essentially doing the same thing as setting the max freq. The Governor can still work and do its own thing except there is a CAP to the limit for Max freq. Same for Charge Level Control. You are setting the MAX possible current allowed. I just know that leaving your phone on the charger all the time overnight and QCOM Quick Charge are both not really good for the longevity of the phone's battery. Just cuz you can charge at 2A doesnt mean its a good thing to do 100% of the time. I wanted a way to limit this.
[ONE Original Android Development] usmani:
A quick question, doesn't the usb fast charge basically do the same thing?

And the reason I asked for stock logic is because there was a whole discussion about this in boeffla kernel thread a few months ago, so that guy added an option to use stock current. So maybe you can add an option to disable this and use stock current if it's possible and not asking too much? Thanks
[ONE Original Android Development] RenderBroken:
No, Fast Charge does not do the same thing. It actually does the opposite. Its like raising the Min freq. Like when your phone is very low on battery it will charge at 2A but the closer it gets to 100% it will slow down so by the time you get to 100% its charging at like 300mA. Fast charge would essentially override this slow down. I have thought about working to combine the two but don't have time or the exact know how quite yet. I am not sure what you mean by disable this and use the stock current. If you just leave the controls alone, you are using the stock values. I may add a way to make this clearer in Synapse but its not imperative. So just to confirm, the Stock settings for Charge Level Control are the stock charging values. I am just giving people to slow down the rate of charging when its not needed in order to prolong battery life.
[ONE Original Android Development] ahaq:
Is the ukm version correct as for urs?
[ONE Original Android Development] usmani:
Sorry for not expressing my self clearly. What I mean by disabling charge control is using stock charging logic. charge control is working at 2A screen on or off. Right now I'm using my phone while charging it and it's getting pretty hot at 2A, but the stock charge logic limits the current when screen on to 1A which eliminates the heating factor. when screen is off 2A is okay. So what I mean is to add a toggle that disables charge level control (for people who want to use stock charge logic) and activate stock charge logic, or you can add another logic which uses a different current when screen is on.

To make my myself clear, If you have free time search 'charge' in boeffla kernel thread and look at the comments made in November to see what I'm talking about. I don't know how to quote comments or else I would have done it myself.
[ONE Original Android Development] ahaq:
[MENTION=1546609]gianton[/MENTION] waiting for your profile for Euphoria 5.1
[ONE Original Android Development] gianton:
Not the latest kernel but you can still use it.

https://docs.google.com/file/d/0B8mXr0tbx63LV2pUVF9tcWpGWVU/edit?usp=docslist_api
[ONE Original Android Development] störte:
Most probably i ask now like a noob. But i cant figure out the anykernel thing. Does it mean it is a all in one kernel ? CM,AOSP,Omni ?
[ONE Original Android Development] schaggo:
A certain rom/os needs a kernel which comes with a certain ramdisk, fitting the rom/os.

CM kernels with CM-compatible ramdisk don't work on Omni, Omni needs Omni-compatible ramdisk etc.

Anykernel takes the ramdisk the stock (respectively the currently flashed kernel) kernel (the kernel of your rom) comes with and couples it to the custom kernel at flash time.

AK.Render+Omni=Omni ramdisk + Renderkernel.

AK.Render+CM12=CM12 ramdisk + Renderkernel.

AK.Render+CM12.1=CM12.1 ramdisk + Renderkernel.

That's why you should NOT flash AK.Render when you already have AK.ak flashed, as it will take the "dirty" ak-ramdisk (which is already an ak'ified ramdisk) and couples it to Renderkernel. Too much dirt, fu**ups expected. Hence flash rom with stock kernel and stock ramdisk, then flash AK.Render to get a clean ramdisk for it.

Edit: so no, it's not a universal kernel, by no means. But the kernel dev does not have to care about different ramdisk requirements of different roms. As long as the kernel code is compatible with the rom code, it'll run. As 5.1 and 5.0 is compatible codewise, a 5.0 kernel will boot on a 5.1 rom and vice versa. And the differences in ramdisk are being taken care of by ak. No need for the dev to pack the same code up twice, once for rom x, once for rom y only because of different ramdisk requirements. But of course, as with multirom, as with xposed, as with all "dirty mods" you somewhat lose your right to compain if things go belly up.
[ONE Original Android Development] störte:
Thanks a lot for the explanation. So i could try this kernel with my omnibased Darkobas rom.
[ONE Original Android Development] ahaq:
Is msm mpdecision enabled under thermal?
[ONE Original Android Development] gianton:
You mean under "Hotplug", yes it is.
[ONE Original Android Development] RenderBroken:
Si, I just did not adjust the info page yet. Thanks for checking!

Its all good, I am not getting frustrated. But the point is missed, The Stock Charging logic remains intact. Charger Level Control doesn't BOOST the charging mA. It just LIMITS the MAX Charging mA. So your phone getting hot because of this new feature is in your head.. MY phone gets hot too when charging before this. With this it still gets hot if I leave the Charge Level at Stock which is 2A because I am still allowing the charge routine to run uninhibited. It will still Charge at 2A when screen off and when screen on it will charge at 1A. I will still search the thread because there still may be good info.

Booom, another truth bomb! lol . Thanks!
[ONE Original Android Development] störte:
Just tried it over latest Darkobas build with stock kernel. Afraid it is in bootloop. Or did i do something wrong
[ONE Original Android Development] RenderBroken:
No I think there is some changes needed for omni rom to work. I believe it will work with older builds but not the new ones.
[ONE Original Android Development] usmani:
Okay now i get it. Thanks for bearing me lol
[ONE Original Android Development] RenderBroken:
Np ;) we have to learn somehow and someone else may have had the same concerns so it's good to have a record of the convo in the thread.
[ONE Original Android Development] RenderBroken:
O. . . M. . . G. . . .

We are now googletized?! ;)
[ONE Original Android Development] Izachii:
[MENTION=5438598]RenderBroken[/MENTION] thanks for the new kernel!
[ONE Original Android Development] ak:
@RenderBroken

rated. thanks man.
[ONE Original Android Development] skeetzor:
getting a bootloop on SlimSaber with this kernel :(
[ONE Original Android Development] BlakeSm:
Running great on Temasek 8.5 by katinatez. Used your kernel on the G2, good to see you here :)

Sent from my CM12 Temasek OnePlus One.
[ONE Original Android Development] ernestnwanu:
Same here, just like with ak. Perhaps there's something similar in the kernels that causes this for some devices? I'm looking into it.
[ONE Original Android Development] luigirenna:
Really a great kernel.

Bravo!
[ONE Original Android Development] abhi08638:
[MENTION=5438598]RenderBroken[/MENTION]

Thanks for using my profiles. Can't wait to try out the kernel!
[ONE Original Android Development] RenderBroken:
I would say that its configured stock to be have conservative performance and have a decent deep sleep. There are so many thing that users can do to tweak my kernel to their liking. One, you can custom set min freq, max freq, governor values per core. By Default I am using Impulse from Neobuddy89 and to me its interactive when you need performance and conservative when you don't. By default I use a modified version of MSM_Hotplug from Myfluxi and its set so when you are doing nothing, only one core is in use, when you touch the screen a second core in onlined and will remain so as long as its boosted. Then when you stop touching the screen and after 750ms the core is allowed to go offline if the workload is low enough and its not needed.

This is the first time I have ever heard this happen with Synapse and UKM. I use a built in version of UKM modded for my needs with my G2 kernel and I have Never heard of this before. Can you produce any logs?

Please keep me updated! If you find a fix I would gladly give you credit once implemented. Thanks for your help regardless!
[ONE Original Android Development] RenderBroken:
I try to give credit where its due and I used your profiles when I was using AK. They worked great and its always nice to show users that they can easily take control of their screen settings.
[ONE Original Android Development] niko2931:
Good man,hopefully more will do this ;)
[ONE Original Android Development] DerRomtester:
Nice to see one more kernel dev here :D
[ONE Original Android Development] usmani:
Awesome!

Btw Franco tweaked conservative would be nice. :)
[ONE Original Android Development] ponytojas:
Believe me or norte, but your kernel was one of the reasson I buy muy opo.

Really love it con my "old" G2

Thanks for tour awesome work [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] freaky deaky:
wohoo new kernel...
[ONE Original Android Development] clockworkstop:
I like this kernel a lot, nice to see something new come up.
[ONE Original Android Development] mumaster20:
Kernel does not boot on slimsaber! After wiping cache/dalvik it seems to build the cache back up, but as soon as it finishes it goes back into a bootloop.
[ONE Original Android Development] _ASSASSIN_:
Dirty flash your ROM and then flash the kernel. See how it goes
[ONE Original Android Development] sneakerspark:
I don't know why but my device never sleeps. I wonder what could be reason for no deep sleep.
[ONE Original Android Development] abhi08638:
Could be because of google play services. Try disabling the keep awake and wake up permissions through privacy guard
[ONE Original Android Development] acuicultor:
If you are referring to the powered by Microsoft thingy just take a look at this

http://review.cyanogenmod.org/#/c/93029/
[ONE Original Android Development] RenderBroken:
No, I am talking about this!

http://www.xda-developers.com/google-to-acquire-xda-dev-rewards-policy-changes/

OMG! lol
[ONE Original Android Development] Formhault:
In other news, aliens took over the White House.

Oh wait. That's not news.
[ONE Original Android Development] Thunderbolt:
Gianton could You tell me way You disabled drop caches and laptop mode on your settings?
[ONE Original Android Development] Formhault:
I have this handy dandy charger doctor around, so I used it to test if the charge control works. AND IT DOES ! Well, to some extent...

Set

100 mA

in Synapse -> the charger doctor reports 0.09A. Very low current input. At this rate, the 3100 mAh battery in the OPO should charge from 0% to 100% in... ~30 hours.

The 100 mA step is most useful if you go to bed with like 80% and want to have a full battery in the morning (20% of ~3100 is ~620, so 100 mA per hour = ~600 mA in 6 hours).

The

500 mA

step works -> ~0.47A reported by the charger doctor. So, if you go to bed with ~10%, the phone should reach a full charge by the time you're awake (provided you only sleep ~7 hours :p ).

Set 200, 300 and 400 in Synapse -> the charger doctor reports 0.14~0.20A... in all three cases. [MENTION=5438598]RenderBroken[/MENTION], I guess these just don't work. Not sure if it's software related or just purely hardware limitation.

600, 700 and 800 are the same as 500 -> ~0.47A.

Tested with three chargers : a ProCell one (1A and 2.1A outputs), the stock OnePlus charger, and a Samsung 5V~2A charger... it's the same.

900 and 1000 work -> ~0.87A input. But here's how it works :

- Set the limit to 2000 mA and plugged in to the 5V~1A port of my ProCell charger : 4.8 volts, 1.18 amperes.

- Set the limit to 1000 mA and plugged in to the 5V~2.1A port of my ProCell charger : 4.99 volts, 0.87 amperes.

All in all, I guess this is as close to adjustable charging as we can get...
[ONE Original Android Development] RenderBroken:
Great info! In may be the way the module controls the ohms. It may not be able to really handle the in between states. I was going to play with it some more to see how well the software readings work. There is also a sysfs file that will state the MA being currently used too. On a side note, I plan on doing way more with my version of SYNAPSE (NOT STWEAKS!! Go back to Samsung you! lol jk ;) ) such as Live readouts. Kinda like how the temperature will show up in Synapse. This would be a perfect example of something I would add as a live readout and thats the mA currently being used. Thanks again for giving great info!
[ONE Original Android Development] _ASSASSIN_:
[MENTION=4129455]Formhault[/MENTION]s info should be in the OP :)
[ONE Original Android Development] Formhault:
Yeah I guess so. I don't really know how the charge is actually being controlled. Some sort of variable resistance... but not sure how that's actually ordered to do X and Y. I should have asked a teacher about this today - forgot. :p

Yeah, live readouts would be AWESOME. If they're accurate... Given OnePlus cut corners and put a sh*tty vibration motor in their phones, I doubt they put many sensors for stuff like this :(

And yeah, it's Synapse, not STweaks. Too many s'es. Let's call it the S-Control app :silly:
[ONE Original Android Development] Salam Husin:
Hello,

I noticed your kernel has been intergrated with smoki's build on cm12.1 rom (uber). Would you mind to share me any best configurations in synapse that promotes battery life saver or it is already there as per installed rom? Perhaps you could suggest any better synapse profile for me to configure it by myself?

Thank you.
[ONE Original Android Development] Formhault:
The default settings are awesome. If you want more battery life, I guess turning down the CPU and GPU frequencies a bit would be a good start. Also, disable CPU boost.
[ONE Original Android Development] Salam Husin:
I got that. But particularly, what type of governor would be the best? Despite turning down a bit on CPU's and GPU's, I am currently using optimax governor. Do you think it sounds good?
[ONE Original Android Development] RenderBroken:
Yea, I prefer the default values. But if you really wanted you could disable CPU Boost and use a more aggressive governor like interactive or maybe even smartmax. You could turn down the GPU but to me that is negligible. Still every little bit counts, You could also set the Max freq per core as follows:

cpu0 - 1.9GHz

cpu1 - 1.9GHz

cpu1 - 1.6GHz

cpu1 - 1.6GHz
[ONE Original Android Development] néonaloj:
So its working with cm12.1, with Euphoria 5.1, does someone know if it boots with Resurrection Remix 5.1??
[ONE Original Android Development] RenderBroken:
Yes it should, I personally have not tried but the kernel source is the same pretty much. Only the ramdisk changed and I use anykernel to make my kernel work with their ramdisk.
[ONE Original Android Development] néonaloj:
OK, so it IS working fine on the Resurrection Remix Rom, with UKM, Synapse is all right too.

Thanks for this!
[ONE Original Android Development] NikoZBK:
I can't seem to connect to the server. "Error code 8 The proxy failed to connect to the web server, due to TCP connection rejection (TCP Reset)."
[ONE Original Android Development] RenderBroken:
Thanks, I will look into it.
[ONE Original Android Development] Vallista:
is there a better link for to download? I can't get the kernal.
[ONE Original Android Development] RenderBroken:
I was able to download just fine from the computer. I will create a mirror shortly.
[ONE Original Android Development] Vallista:
I can't download the kernal. Can you make a better link?
[ONE Original Android Development] RenderBroken:
Mirror:

Downloads Mirror
[ONE Original Android Development] NikoZBK:
Can you also upload your UKM? :)
[ONE Original Android Development] RenderBroken:
Here you go!

https://drive.google.com/folderview?id=0B-GVJKBx9-Gnfkh1VEJVTkkzZlN5V0FmbWNrWUkxYXdNcWJEQmNfQnBBckVVMU1pd2dqM2s&usp=sharing
[ONE Original Android Development] Nandeh:
R3 smoothness is amazing with Euphoria 5.1 and battery life even in first cycle great, I have got almost 6 hours SOT in a combined use 50% mobile data and 50% WiFi.

I'm really happy with this combo!! :)
[ONE Original Android Development] RenderBroken:
Glad to hear!

What settings are you using?
[ONE Original Android Development] ahaq:
i am interested too for the settings, i get rougly 4-5hours on 5.1 i got 6.5hours on 5.0 Euphoria via [MENTION=1546609]gianton[/MENTION]
[ONE Original Android Development] RenderBroken:
Both using my kernel or what?
[ONE Original Android Development] ahaq:
Your Kernel

Europhia 5.02 = 6.5 hrs of sot via [MENTION=1546609]gianton[/MENTION] profile

Europhia 5.1 = 4-5hrs of sot via [MENTION=1546609]gianton[/MENTION] profile
[ONE Original Android Development] RenderBroken:
I have heard that 5.1 is alot smoother. there may be something else rom side making that possible but not quite optimized yet. I say this as a guess. I have no clue. But if the same exact kernel with the same exact setup produces different results then its the rom for sure.
[ONE Original Android Development] Norapapa:
Where can I find the profile from gianton?
[ONE Original Android Development] gianton:
Here you go,

https://docs.google.com/file/d/0B8mXr0tbx63LV2pUVF9tcWpGWVU/edit?usp=docslist_api
[ONE Original Android Development] Formhault:
NEVER quote such a long post. Especially just to ask that... :eek:
[ONE Original Android Development] Nandeh:
Nothing special, all settings by default except the governor changed to Smartmax
[ONE Original Android Development] ahaq:
What's the default for ac charing again, 2000 right?
[ONE Original Android Development] Formhault:
Yeah.

---------- Post added at 05:41 PM ---------- Previous post was at 05:34 PM ----------

Hmm... I placed this file in /Synapse/saved_profiles folder and tried to import it in Synapse... "Invalid file" :eek:

Tried placing the file in /Synapse/saved_configs folder and I got a toast saying "None selected" :eek:
[ONE Original Android Development] Thunderbolt:
Placed in saved profile. Start synapse, click profile, restart. Next to profile again, take gianton profile, than click V and restore. Synapse will crash. Start again and click x. At all.
[ONE Original Android Development] RenderBroken:
lol you mind if I just link it in OP?
[ONE Original Android Development] Formhault:
Ohhhh, you gotta press the V before restoring... I get it. Thanks! :)

You also get to see what's changed (grey outline)... then have to press the V again to set it (except voltages). Nice. I never feddled with this part of Synapse, so... :p
[ONE Original Android Development] gianton:
Of course not, go ahead.
[ONE Original Android Development] Formhault:
Hey [MENTION=1546609]gianton[/MENTION]. I'm curious...

Why did you choose to set the read-ahead size to 512 KB? And GPU freq to maximum, while lowering the CPU Freq to 2.3?

Also, swappiness, dirty ratio...
[ONE Original Android Development] gianton:
My setup is:

CPU: 300-2726 MHz

GPU: 200-657 MHz

Smartmax

Rest is default. I think Synapse can't restore the settings correctly.
[ONE Original Android Development] Formhault:
I think so. It greyed out voltage, vibration level and a whole bunch of other stuff which you didn't seem to touch...

I cleared Synapse data. Now CPU freq is at 2.3 GHz and everything else seems to be default lol... How do I actually reset Synapse to default? :eek:
[ONE Original Android Development] RenderBroken:
Yea I too have been noticing weird little glitches with Synapse. Maybe its the new UKM 3.8.1 and will be fixed in new releases.
[ONE Original Android Development] Thunderbolt:
Sometimes i Think, that the Best solution is make a screenshots with settings and do it manual.
[ONE Original Android Development] gianton:
Here is my CPU settings in Synapse on R3 rest is default.
[ONE Original Android Development] RenderBroken:
You, good sir, are the man. Thanks for posting. I have never really played with smartmax much but I will give it an honest try. It is definitely smoother than impluse but not sure the screen on time would be as good. For me though, I want to use my damn phone. I don't want to have to keep it ultra conservative and such. Really if I can make it to the end of the day (6a - 10p) and have about 30% left to plug into the charger. I am happy because I know that if I forget to plug in, I will have about 25% left when I wale up and can charge throughout the day and remain operational.
[ONE Original Android Development] Thunderbolt:
Now i now, that restore profile doesn't work.
[ONE Original Android Development] gianton:
+1 exactly my thoughts.
[ONE Original Android Development] aftmkt:
36 hours of usage with 6hrs of On-screen.

Lovely! :good:
[ONE Original Android Development] ahaq:
do share your settings, as we want to expand this thread for profiles with synapse!
[ONE Original Android Development] aftmkt:
CPU: 146 to 2265 MHz

Smartmax governor.

Rest all is stock.

The kernel seems to be already very power efficient, extra tweaking is unnecessary for regular usage. :)
[ONE Original Android Development] RenderBroken:
YES! Lets get some profiles passing around! If we have some that seem top be popular than I will post a link to the post of your profile. Look at OP#2 and you will see what I did for [MENTION=1546609]gianton[/MENTION] 's post. I may eventually gather them all and host them on my server for easy access.
[ONE Original Android Development] ahaq:
Perfecto!:highfive:
[ONE Original Android Development] _ASSASSIN_:
Maybe we should have a profile sharing thread like AK has.
[ONE Original Android Development] adinkwok:
Scroll back a few pages. He posted one earlier.