[TEST][Kernel] FloppyKernel [FEEDBACK] - Xiaomi Mi 5s Plus Questions & Answers

Hello,
I am Mi5 dev, and as some of you know what Mi5, Mi5S, Mi5S Plus, Mi Mix and Mi Note 2 have the same source, I have a kernel called "FloppyKernel" for MI5 and decide to add support for those devices, but with that I'm feeding feedback to know if everything is working, because I only have the Mi5, thank you if you can test and give feedback
Download
FloppyKernel for MI5

Installed the non-lite one, it boots at least.
Performance I'm testing right now.
What's the difference between lite and non lite for mi 5s plus?
Geekbench, 1983, 4055. Somewhat strong single core, bit underwhelming multi.
Phone scores 123745 in antutu, 40051, 42940, 31211, 9543.
Bit low actually.
I haven't ran this on my older kernels ( nexus exp, psychedelic ), so no comparisons I'm afraid.
Edit: Double tap to wake is borked. Psychedelic is too, so I don't think it's your fault.
Can't really check if cores go to sleep etc., don't want to break no-root.

Thank you for the feedback of all, I will create an official thread for the kernel, there you can discuss the problems and solutions of the kernel (and post the logs, of course)

Did you implement sweep2wake in this kernel? Can you link the commit where you did it please? I really want to implement this in my own kernel.

theOriginalSuperl2 said:
Did you implement sweep2wake in this kernel? Can you link the commit where you did it please? I really want to implement this in my own kernel.
Click to expand...
Click to collapse
Pass the link I'll take a look

Jonas Cardoso said:
Pass the link I'll take a look
Click to expand...
Click to collapse
No, I wanted your commit if you had enabled it. Never mind then.

Thread closed at OPs request

Related

[Discussion][Perseus Kernel][GT-I9500]

To keep Andrei from going crazy with non-development related questions, I've opened the following thread. That way we keep the development thread for development topics and this for general discussion.
Good deal.
First feature request: Fading in/out LEDs! I've pinged the dev for LightFlow, and while he can implement it on a software level, it would be supremely inefficient and probably drain the battery like crazy.
cmd512 said:
Good deal.
First feature request: Fading in/out LEDs! I've pinged the dev for LightFlow, and while he can implement it on a software level, it would be supremely inefficient and probably drain the battery like crazy.
Click to expand...
Click to collapse
Actually that's something which belongs in the dev thread. If anything you can just post on the issue tracker on Github, I've grown vary of XDA.
There's a new TI LED controller so I can't port the old Philips controls from the old phones. I'll rewrite it eventually but I got other things to do now.
AndreiLux said:
Actually that's something which belongs in the dev thread. If anything you can just post on the issue tracker on Github, I've grown vary of XDA.
There's a new TI LED controller so I can't port the old Philips controls from the old phones. I'll rewrite it eventually but I got other things to do now.
Click to expand...
Click to collapse
Done, posted on Github!
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
astoncheah said:
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
Click to expand...
Click to collapse
Congrats, you win the award for the first post about useless benchmark scores in this thread.
cmd512 said:
Congrats, you win the award for the first post about useless benchmark scores in this thread.
Click to expand...
Click to collapse
thanks for you response. as i mentioned i got it only one day, without touching anything on u/v & o/c. i guess this is considered lower score than the stock one? i merely care about bench mark, i just want to know is this normal? or i need few days to let it settle down? fyi, i tried more than 10 times and it only score between 20k-21k. perhaps you can be kind enough to give me some idea rather than congrats me.
astoncheah said:
thanks for you response. as i mentioned i got it only one day, without touching anything on u/v & o/c. i guess this is considered lower score than the stock one? i merely care about bench mark, i just want to know is this normal? or i need few days to let it settle down? fyi, i tried more than 10 times and it only score between 20k-21k. perhaps you can be kind enough to give me some idea rather than congrats me.
Click to expand...
Click to collapse
It is normal for benchmark to be lower than on stock kernel all devices differ. Following the development of this kernel it has been stated that the kernel is not intended for high benchmarks but more for overall stability, smoothness and better battery life.
Benchmarks is just a number and a high benchmark does not always mean your phone is smooth and performs very well under normal user conditions.
Hope this answers your question and should I be mistaken about anything anyone welcome to rectify me on those points.
Sent from my GT-I9500 using Tapatalk 2
xtacy1 said:
It is normal for benchmark to be lower than on stock kernel all devices differ. Following the development of this kernel it has been stated that the kernel is not intended for high benchmarks but more for overall stability, smoothness and better battery life.
Benchmarks is just a number and a high benchmark does not always mean your phone is smooth and performs very well under normal user conditions.
Hope this answers your question and should I be mistaken about anything anyone welcome to rectify me on those points.
Sent from my GT-I9500 using Tapatalk 2
Click to expand...
Click to collapse
i never meant that perseus is running low on benchmark, in fact, it's the highest between chainfire's cfroot, wanam's adam. i tried all these 3 kernel, all score only between 19k-21k. i just wonder if i have accidentally limited my cpu speed? i will do a factory reset and re-test it.
again, i dont or merely care about benchmark, i just care if my s4 is running normally.
astoncheah said:
i never meant that perseus is running low on benchmark, in fact, it's the highest between chainfire's cfroot, wanam's adam. i tried all these 3 kernel, all score only between 19k-21k. i just wonder if i have accidentally limited my cpu speed? i will do a factory reset and re-test it.
again, i dont or merely care about benchmark, i just care if my s4 is running normally.
Click to expand...
Click to collapse
I have kanged Andrei's response with respect to benchmarks.
Originally Posted by AndreiLux
Samsung cheats during benchmarks by enabling a thermal boost mode which raises the throttling temps by 10°C (90° -> 100°C). I disabled the permissions to this. Practical effects is things like Antutu will give lower scores. This is more realistic of actual performance and I will leave it as such. Benchmark freaks can enable the boost mode manually: /sys/class/thermal/thermal_zone0/boost_mode .
The first throttling speed is 1400MHz and that's why it spends a lot of time there during benchmarking.
Effectively, overclocking on this device makes very little sense unless you can achieve more thermal headroom with undervolting. I personally couldn't get over 1.8GHz on random loads, and couldn't get over 1.7GHz on benchmarking (Antutu 31300).
Nevertheless, the option is there for people who want to stick their phones into their freezers. For everybody else, stop being concerned about numbers.
This seems to affect only a rare number of people and I still don't know the cause. Just cycle the screen once and be done with it.
jlevy73 said:
I have kanged Andrei's response with respect to benchmarks.
Originally Posted by AndreiLux
Samsung cheats during benchmarks by enabling a thermal boost mode which raises the throttling temps by 10°C (90° -> 100°C). I disabled the permissions to this. Practical effects is things like Antutu will give lower scores. This is more realistic of actual performance and I will leave it as such. Benchmark freaks can enable the boost mode manually: /sys/class/thermal/thermal_zone0/boost_mode .
The first throttling speed is 1400MHz and that's why it spends a lot of time there during benchmarking.
Effectively, overclocking on this device makes very little sense unless you can achieve more thermal headroom with undervolting. I personally couldn't get over 1.8GHz on random loads, and couldn't get over 1.7GHz on benchmarking (Antutu 31300).
Nevertheless, the option is there for people who want to stick their phones into their freezers. For everybody else, stop being concerned about numbers.
This seems to affect only a rare number of people and I still don't know the cause. Just cycle the screen once and be done with it.
Click to expand...
Click to collapse
"This seems to affect only a rare number of people and I still don't know the cause" guess i am one of them:silly:
did you guys note the download link for perseus alpha 4 rc1 on andrei github? , dont flash it unless you know whats in there
edit: just flashed it (couldnt resist). based on the newer sources it seems, camera works fine with latest cam firmware
lets wait for Andrei release......build seems to be a release candidate....so its should not be for long....
bala_gamer said:
did you guys note the download link for perseus alpha 4 rc1 on andrei github? , dont flash it unless you know whats in there
edit: just flashed it (couldnt resist). based on the newer sources it seems, camera works fine with latest cam firmware
Click to expand...
Click to collapse
Thanks for sharing bro but i'm too stupid to find the link would you mind sharing more please?:victory:
update: found it: deleted. sorry
astoncheah said:
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
Click to expand...
Click to collapse
I received mine yesterday, rooted, flashed doc rom to remove bloatware, flashed perseus kernel.
I ran a few antutu and I was getting 27-28k without changing any setting.
Sent from my Nexus 4 using xda premium
@GSeeker
Pls remove the link since we dont know the nature of the version or lets wait unitl andrei unveils it.
bala_gamer said:
did you guys note the download link for perseus alpha 4 rc1 on andrei github? , dont flash it unless you know whats in there
edit: just flashed it (couldnt resist). based on the newer sources it seems, camera works fine with latest cam firmware
Click to expand...
Click to collapse
@Power, What rom are you running? I suspect it's rom related.
I'm using omega 7, one of the user experienced the same as mine. Going to flash new rom.
Sent from my GT-I9500 using xda app-developers app
astoncheah said:
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
Click to expand...
Click to collapse
With Omega / Perseus, is your camera still working????
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
HassanM said:
With Omega / Perseus, is your camera still working????
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
Click to expand...
Click to collapse
From recovery flash Perseus kernel + Camera Fix https://www.dropbox.com/s/20kyqg154h8w198/camera-ISP-fw.MEAplusFix.zip
Then reboot. Your camera should be working.

TouchControl app vs Custom kernel s2w-dt2w

Hi, I've been using the TouchControl app for a while and I really love it but the battery drain is huge. I want to know if the custom kernel s2w and dt2w are more battery friendly than the TouchControl app. Thanks
Enviado desde mi Nexus 5 mediante Tapatalk
Yes more battery friendly.
I have a love hate relationship with Touch Control for the same reason, but Im ignorant to s2w-dt2w. But youve peaked my attention.
That's an intersting question. In fact i was going to create a topic about it my self. :good:
IMHO, if you leave out the battery consumption issue, Touch Control is better than s2w and dt2w because it supports more customization.
I tried s2w and dt2w in a few kernels and couldn't find a way to set the “delay time” like in Touch Control e.g. I can swipe slowly to turn off the screen, but I want the delay to be short (i.e. you have to swipe really fast) to turn the screen on because otherwise the screen could be accidentally turned on when I'm walking around with the phone in my pants pocket.
I love TouchControl for the exact same thing, I think that TouchControl and s2w - dt2w might have the same battery consumption because it's the digitizer always on that cause the battery drain but it's just my theory.
Enviado desde mi Nexus 5 mediante Tapatalk
Touch control would be better if the developer ever bothered to update the app or fix the huge battery drain. Also if you use a kernel like bricked with the same amount of money you can buy his app and have the benefits of controlling the kernel tuneables in addition to having s2w and dt2w.
MLopez14 said:
I love TouchControl for the exact same thing, I think that TouchControl and s2w - dt2w might have the same battery consumption because it's the digitizer always on that cause the battery drain but it's just my theory.
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
Is this correct?
MLopez14 said:
I love TouchControl for the exact same thing, I think that TouchControl and s2w - dt2w might have the same battery consumption because it's the digitizer always on that cause the battery drain but it's just my theory.
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
I think that all s2w dt2w code has been created by a single developer - showp. Here is a link to his kernel where it all started. http://forum.xda-developers.com/sh...el Hammerhead | Sweep2wake | KnockKnock/Dt2w
I also believe that both the app and all other kernels had taken advantage of showp's code with some minor modifications.
The reason why the battery drains is because of hardware architecture that is different in nexus5 (I suggest you read detailed explanation in kernel thread I referenced above) - but as I recall the chip being activated for s2w is also soldered to digitizer or something, which activates it. Showp mentioned that if lg shared hardware architecture details it would be possible to eliminate battery drain by deactivating specific chip until it is needed. Again, read the thread for details. The thing is that lg is not inclined to share the information, and kernel developers are making no money on their work, except for optional control software which is not free. App developer is probably charging for compatibility with multiple kernels, including stock, plus additional configuration settings. But in terms of s2w I don't know if anyone can do anything to improve battery usage until additional hardware specs are released. While showp created the original code - I think that all developers referencing his code should take initiative and try to address the issue from different angles. Hammering any individual thread would change nothing. And while showp already expressed his honest opinion - I don't know if other developers had done the same. Maybe all developers may admit that they are not planning to do anything (especially those who simply refer to showp for s2w). But if someone takes initiative then it would be great.
delacrow said:
… I also believe that both the app and all other kernels had taken advantage of showp's code with some minor modifications …
Click to expand...
Click to collapse
I'm not sure about that because Touch Control has been around since the Nexus S days… (by the name of PGM) and @bponury wrote the kernel module himself.
However, the code to make them (swipe/double-tap to wake) work on Nexus 5 could be similar based on available hardware architecture detail like you mentioned :fingers-crossed:
I am gonna give more points for Custom kernel s2w-dt2w as this is better option for the one who love to save the battery or need battery for the longer time as he keeps himself busy in journey.

[BOUNTY] Custom kernel SM-G935F/FD

Okay. So apparently Samsung have made some changes to the kernel in S7 compared to other Samsung's.
In order to make the kernel boot, you have too disable tima_rkp. But disabling tima_rkp makes the kernel unstable.
We can make the Kenrel stabel, by disabling the FP lock. But then again. A very used feature of the phone is useless
I figured out by putting out a bounty, maybe some developers are willing too have a look at it, and see if it's a way too make this work. Currently Samsung have 4 kernel sources out here
Anyway. Don't let me disturb you any more, and let's start this bounty tread.
I'll start with pledging $50 for the one who can make a stable custom kernel for our beloved S7 edge. (935F/fd)
Please notice, there is no minimum pledge. You are free to pledge what ever amount you want too.
Current status : $396 bounty
i am in with 50$ too..!!
Same here i will pledge $50 worth every penny :highfive:
£50 here which is about $71
$50 from me too
Sent from my SM-G935F using Tapatalk
i already asked the hacker for help to built a kernel but he doesnt have his S7 anymore..
Sent from my SM-G935F using XDA-Developers mobile app
Okarina26 said:
i already asked the hacker for help to built a kernel but he doesnt have his S7 anymore..
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, I think he Sent it back the same day unfortunately :/
USD 75
I'm an S7 930F user, but Edge 935F development is more active, and there is little to no difference anyway. I'm sure , if needed, it can be recompiled for 930F.
Out of curiosity, why is a bounty needed for making a custom kernel for the S7? The rom development was quite active on the S6, so why is it so "dead" at least from a kernel perspective here? I mean, is a custom kernel just not happening for the S7 or will we set some in the near future?
Faspaiso said:
Out of curiosity, why is a bounty needed for making a custom kernel for the S7? The rom development was quite active on the S6, so why is it so "dead" at least from a kernel perspective here? I mean, is a custom kernel just not happening for the S7 or will we set some in the near future?
Click to expand...
Click to collapse
As its my understanding, the major problem with a custom kernel, is the implementation of tima_rkp, Samsung have been using on this kernel. Just in order too have the kernel boot, you have to disable it, but then again, you will have a unstable kernel. It can be some stable, if you don't use any hard-coded security features, like fingerprint unlock and so on.
Swipe to wake works, with very few too none reboots. But still it isn't stable.
That's why it's a little bounty out, too trigger the willingness of other developers too take some of their free time and have a look at it.
As you prob noticed, there isn't any custom kernel out yet, tho the S6 hade a few kernels out just a week after release.
I'll take a look at it later, but I can't promise anything.
Faspaiso said:
Out of curiosity, why is a bounty needed for making a custom kernel for the S7? The rom development was quite active on the S6, so why is it so "dead" at least from a kernel perspective here? I mean, is a custom kernel just not happening for the S7 or will we set some in the near future?
Click to expand...
Click to collapse
To make it simple, its as simple as
Open Source
and No Source.
exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)
I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
dave7802 said:
To make it simple, its as simple as
Open Source
and No Source.
exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)
I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
Click to expand...
Click to collapse
Nope
Samsung's already release KERNEL source for exynos S7 or else this thread won't even exist.
This thread is here because of the new change samsung had made to S7 kernel (mostly security stuff) make modifying the kernel without too much trouble hard
Also S6 had only Exynos version because of the underperforming sd810.
Sent from my SM-G935F using Tapatalk
dave7802 said:
To make it simple, its as simple as
Open Source
and No Source.
exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)
I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
Click to expand...
Click to collapse
That's only for custom roms, which is the reason we *might* never see a stable AOSP Rom. There are sources out for the kernel.
Bla cba with the response, I was more down the lines of AOSP
as i dont see any other real benefit to a custom kernel.
Its not like the S7 suffers from Lag / Performance issues or battery draining.
(My original replay was much longer going into detail, stupid page timeout)
dave7802 said:
To make it simple, its as simple as
Open Source
and No Source.
exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)
I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
Click to expand...
Click to collapse
s7/ s7edge also got its own Snapdragon Version
pigmich said:
s7/ s7edge also got its own Snapdragon Version
Click to expand...
Click to collapse
Closed bootloader...
dave7802 said:
Bla cba with the response, I was more down the lines of AOSP
as i dont see any other real benefit to a custom kernel.
Its not like the S7 suffers from Lag / Performance issues or battery draining.
Click to expand...
Click to collapse
Indeed. The main reason for a custom kernel for me has always been for permissive, which V4A requires to work. But there is now a work around for this on enforcing kernels so I'm really not that bothered. It's not as if Exynos S7/S7E devices suffer from battery life issues or overheat problems which underclocking and/or undervolting could fix. It works very well as is, I get between 6 and 7 hours SOT on average and it's very stable in all other departments. In short, the need for a custom kernel has greatly diminished on this device, especially in comparison to the S6/S6E/S6E+ which all had terrible battery life. But if it's important to some people then good luck in getting one sorted.
I'M a 930 user, but it will fix our problems as well.
50$ from me.
Here are the temporary solutions.
Way A:
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Way B: (If you want to completely disable (or bypass) TEE)
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Replace /system/lib64/hw/gatekeeper.exynos8890.so,/system/lib64/hw/keystore.exynos8890.so with these i uploaded.
Both of them will make your FP Sensor not working.
(Lock Screen will work)
But,at least,you get a stable custom kernel.
I am trying to re-implement FP sensor support to system with TEE disabled.
Here is some files from somewhere confidential and a simple kernel compiled by me and my build.prop.

Underclocking for better battery life?

Will lowering the voltages improve battery life? If so, how can I go about doing it? I don't really need so much power since I rarely game and all I do is stream media and normal web-browsing.
fist steps are to root and install a custom kernel, if available..the use a kernel modifying program and make your changes that way..
I think you can't since kernel is closed source for our device, might be able with custom ROM. The thing is you don't really want to. Processor has 4 small cores for simple tasks and power saving, it only uses big cores on heavy use. The manufacturer has alredy given you the best option and if the phone is working fine why mess with it? For extra 30 min battery life? It's just not worth it. If you wanna try custom roms buy some older device or Nexus and try it out. Huawei just works from the box.
Without a custom kernel it's impossible. We should get sources soon so just wait
But yeah. Underclocking should improve battery life..
Edit: Sources are up!
ante0 said:
Without a custom kernel it's impossible. We should get sources soon so just wait
But yeah. Underclocking should improve battery life..
Edit: Sources are up!
Click to expand...
Click to collapse
Sources for?
Jaimesco12 said:
Sources for?
Click to expand...
Click to collapse
Mate 9 Kernel source.
ante0 said:
Mate 9 Kernel source.
Click to expand...
Click to collapse
Is there a thread about this or where did you find out? That's awesome news
Jaimesco12 said:
Is there a thread about this or where did you find out? That's awesome news
Click to expand...
Click to collapse
I just checked Huawei open source download site and noticed MHA at the top
arminbih said:
I think you can't since kernel is closed source for our device, might be able with custom ROM. The thing is you don't really want to. Processor has 4 small cores for simple tasks and power saving, it only uses big cores on heavy use. The manufacturer has alredy given you the best option and if the phone is working fine why mess with it? For extra 30 min battery life? It's just not worth it. If you wanna try custom roms buy some older device or Nexus and try it out. Huawei just works from the box.
Click to expand...
Click to collapse
Makes sense. Thank you! I'm still happy with the device. I was just curious as to how/if it was possible and if there were really any benefits. But yeah, for 30 minutes? Might as well just turn on (Ultra) Power Saving mode.

Custom Kernel for OnePlus 7 Pro (OOS) - Which one to pick

Hello everyone!,
I have been the proud owner of the OnePlus 7 Pro for 1 month now, but I still feel that Screen On Time is expandable.
But also because of the better settings I'm looking for the most suitable custom kernel. Fortunately, there are a lot of busy developers out there who give us a large selection of it. But this doesn't make the decision which kernel to use any easier
I'm just looking for a custom kernel that improves screen-on time without affecting performance in everyday use.
I'm looking forward to experiences with certain kernels & would be very happy if someone would make it easier for me (but also other undecided ones out there) to make the decision.
Many thanks for any help in advance
Kirisakura, because of EAS, common patches, well tuned initial parameters.
Kirisakura.
I also use Kirisakura, but I don't think a different kernel will give significantly more screen on time.
Although it may not be the answer you are looking for, I think biting the bullet and just trying each kernel out for a few days would give you the best answer.
Everyone has different setups/uses on their phones which is why there isn't really a one size fits all type answer for this question.
Yep, try some and compare is your best bet...
Can someone on Kirisakura rom show me what the screen calibration menu looks like. Is it as basic as stock oos?
Sent from my GM1917 using Tapatalk
Limeybastard said:
Can someone on Kirisakura rom show me what the screen calibration menu looks like. Is it as basic as stock oos?
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
It's not a rom, just a kernel with a magisk module as a helper
I easily get 9hrs SOT with SmurfKernel. Every decent kernel has a focus. Smurf is overclocking and unified support, kirisukura is EAS, ElementalX is close to stock with a few extra features.

Categories

Resources