yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] sudokamikaze:
Sure, can you try this build?

I've re-enabled High Brightness mode in this experimental build

https://www.androidfilehost.com/?fid=818070582850505606
[Nexus 4 Android Development] Cristiano Lira:
Is anyone also suffering of dying wifi? When it happens only a device restart can fix it. UA 7.1 ROM. Also, does this exp build work with UA?
[Nexus 4 Android Development] faabricjs:
Thanks sir, finally i can use this kernel :D thanks for the build. :cool:
[Nexus 4 Android Development] sudokamikaze:
NP, thanks for testing!

I'll add this fix to new builds!
[Nexus 4 Android Development] sudokamikaze:
Do not use experimental build which I provide for users whose experiencing problems

Always use builds which downloads from OP post

Do you tried to flash latest Oreo?
[Nexus 4 Android Development] FluffyFuyumi:
I have a Nexus 4 running LineageOS 14.1 with SINAI. I wanted to try using USB OTG so I got the Y cable, an external power source (power bank) and enabled it in misc settings in Kernel Adiutor Mod but nothing happens when I plug in my USB stick. Anyone know how to fix this or if I'm doing something wrong?
[Nexus 4 Android Development] d_g_m_2000:
which version can i flash?

Hello OP.

i've been using for the past 12 hrs Carbon Rom (8.1 oreo) but i have some really heavy battery drain...

i know that my battery is not the original oem (it a chinese replacement. it suppose to have 2100mah but i doubt it). In short...

I want to flash sinai kernel but i have a doubt:

Carbon rom declare that is an AOSP base rom but in "settings > about phone" it shows this kernel version "3.4.113-lineage-gae9e3dc"

do you recommend to flash your nougat/oreo AOSP based verion?

thanks in advance for your reply.
[Nexus 4 Android Development] d_g_m_2000:
hello OP.

whits this new post of custom oreo roms based on lineage (rr, crdroid, etc..) Are you planning to release your kernel for lineage_oreo?

I'm asking 'cause your kernel give my battery like 5 hours of extra life.

thanks in advance for your comments and for your khard work!
[Nexus 4 Android Development] Sam Nakamura:
I'm using latest kernel (4/4/18) but getting extremely dimmed screen brightness on recent lineageOS, switching off adaptive brightness helps but it's still subpar as I need to turn brightness up to 80% to see enough indoors - no chance outdoors...

Otherwise great kernel and I'd love to provide logs if needed but I cannot think of any useful log showcasing the actual issue...

Cheers

Edit: sorry for bothering, search before you post, I know :laugh: lol

https://xdaforums.com/nexus-4/development/sinai-n4-kernel-t3614605/post74943557

----------------------

WOW, what a great kernel, lots of fun stuff packed inside - lots of stuff I can only dream of on a so called modern device like OP3T... :good:
[Nexus 4 Android Development] d_g_m_2000:
hello, are you talking about nougat or oreo?

if oreo... which kernel do you flash?
[Nexus 4 Android Development] Sam Nakamura:
No, I'm talking about official lineageOS which still is nougat...
[Nexus 4 Android Development] d_g_m_2000:
hello, thanks for your reply.

https://xdaforums.com/nexus-4/orig-development/rom-lineageos-15-1-google-nexus-4-mako-t3786885

https://download.lineageos.org/mako

i guess i'll have to wait for the dev.
[Nexus 4 Android Development] Sam Nakamura:
Yeah, the kernel probably needs updating to Oreo...
[Nexus 4 Android Development] Sam Nakamura:
Using the UA kernel on latest UA (from Mai '18) build makes the camera app hang, I tested stock and open camera, which both were working before....

Logcat:

https://drive.google.com/file/d/1FW367mdZcPUFKVDyOjXmXNgkYdqhqYWV/view?usp=drivesdk

...otherwise this kernel is just awesome, the device runs immediately mich quicker, great responsiveness and display colors are also much better on the eyes and esthetics, I still hope this to be a local issue with my device system but it doesn't look like, I rebooted several times, checked permissions, etc. but no dice and it was just working with stock kernel...

--------------

Edit: don't know why but issue solved, it just started working out of the blue, ignore this report!

Edit2: that was too fast, issue just returned, seems to be random in nature but mostly fails - camera then needs forever to open up... weird
[Nexus 4 Android Development] TundraLK520:
I'm on nitrogen stock kernel, the camera app hangs the first time I open it, have to close it and reopen it for it to work. Haven't really looked too much into this, since i hardly use the camera The issue might not be kernel related. Could be something in oreo.
[Nexus 4 Android Development] Sam Nakamura:
Well the thing is that it worked with stock UA kernel as expected, after switching to this kernel it's more of a hit and miss, taping the camera app icon let it hang usually (not always) instead of opening it, chances are best to use the camera shortcut (double tap power), sure I don't depend on this camera and it's really a minor thing to sacrifice when considered what the kernel offers, thanks for your feedback...
[Nexus 4 Android Development] bgoel4132:
i tried sinai n4 and it unexpectedly dimmed my screen even when i turned off adaptive control and extend the brightness tu full it was not clearly visible and then i flashed quanta v21 and the issue remained so i had to flash the rom again i had a bad experience from sinai n4 and initially the kernel was quite a laggy and causing too much heat off my phone so i planned to be stuck my dearest combination of fake nexus and quanta v21
[Nexus 4 Android Development] Sam Nakamura:
For the "dimmed screen issue" (actually not an issue), it's known and you can turn this behavior off by using kernel adiutor, refer to this post just a few posts above your's...

https://xdaforums.com/nexus-4/development/sinai-n4-kernel-t3614605/post76431359
[Nexus 4 Android Development] moriel5:
Alright then, I have decided to start undervolting my CPU.

Currently with a subtle undervolt, at -25mV from stock.

I'll let everyone know the stability results in a few days (at which point, if the system is stable, I'll go on to -50mV, and so on, until I reach the limit.

[MENTION=7970097]sudokamikaze[/MENTION], what do you think about adding my undervolt results, assuming that everything goes smoothly, to SINAI's defaults?

As to my CPU settings (only CPU settings), everything is set to stock, aside from me limiting the CPU frequency, as well as the max temps (which I do not reach in any case, unless I stress my phone under the sun in the middle of the summer), and of course, globally setting the undervolt across all cores.

Hopefully, this should bring better life, with lower CPU temperatures.
[Nexus 4 Android Development] jamescable:
Maybe I missed something but, is there an Oreo kerlen for los based ROMs like RR?
[Nexus 4 Android Development] bgoel4132:
i used sinai for over a day and had experienced a battery drain from 97 to 82 overnight it didnt seems normal as quanta v21 gave only a max of 6% batery drain overnight

i only tweaked cpu to max 1026 and enabled dt2w else all.are.stock

presently i am testing quanta reborn and it is really liquid smooth even more than quanta v21 hope the battery life be stable too
[Nexus 4 Android Development] sudokamikaze:
I've already discovered that

-25~75 values are stable

And if you want I can add your tested values to kernel
[Nexus 4 Android Development] sudokamikaze:
Have you used the newest build?

I have some drain too
[Nexus 4 Android Development] sudokamikaze:
Thanks for remind for users :)

I'll enable "High Brightness" mode in next build
[Nexus 4 Android Development] bgoel4132:
yes i have used the latest build

currently i am on quanta reborn with no lag and great battery life
[Nexus 4 Android Development] sudokamikaze:
OK, thanks for the information

I'll do more research on it
[Nexus 4 Android Development] Sam Nakamura:
Nope, according to post #1 of this very thread nothing available for lineageOS Oreo based ROMs like RR but for AOSP 8.1 (unlegacy android) Sinai is compatible... For lineageOS a little more patience is needed, this dev is on it already and franco mentioned to support mako again as it's back on the official lineageOS device list - however franco's kernel is usually relatively strictly pre-defined, leaving lesser control to the actual users, some prefer that, some (like me) rather don't... That's why I'm very happy with Sinai, as it offers the ultimate freedom in many aspects even "modern" devices only can dream of...
[Nexus 4 Android Development] xenyz:
Changing default voltages is dangerous, I really advise against it!

Anyone who wants to undervolt has the opportunity to do so, while some devices won't even boot any more with non stock voltages.
[Nexus 4 Android Development] moriel5:
Which is why I intend of checking stability first.

Since [MENTION=7970097]sudokamikaze[/MENTION] has already verified this at their end, this will make two corroborating sources about the stability settings.

Additionally, I was thinking of recmmending this after my results with the modest 25mV undervolt, I was thinking that [MENTION=7970097]sudokamikaze[/MENTION] could release a test version of the kernel containing these settings, so that anyone who may have issues could report them, and only if everything is alright, would the undervolt make it to a stable version.

Finally, and this is not coming from me, but rather from the Overclockers forum, as long as the modifications are not too far off, generally there is no danger (and by replacing the kernel sources used (which is what almost all updated ROMs use nowadays (how do you think the Nexus 4 has ROMs beyond Lollipop?), you are also replacing the drivers, which is also potentially dangerous, since the device was not meant to be modified).

While I am a rookie with voltage modifications, I have been reading on the subject these last few months, in order to properly understand what I am doing (and this is something I had been planning for a few years).

Third, I had never intended to get a steep undervolt as default, in order to avoid issues. I was thinking something like 50-100mV, no more, and even that would depend on the users, if even one would have issues, then the undervolt would have to be toned down before becoming the default on the stable version of the kernel.

Update: [MENTION=7970097]sudokamikaze[/MENTION] had already posted that up to 75mV was stable on their end, so I will not offer anything beyond that to be the default.
[Nexus 4 Android Development] TheGrinder77:
Undervolt values are very CPU dependant. Before giving advices you should at least mention what kind of chip you have installed.

Refer to this thread for more info https://xdaforums.com/nexus-4/general/uv-nexus-4-uv-thread-post-undervolting-t2155495

Basically the faster is the CPU, the more you can undervolt it.

Personally I'm running with -100mV on all frequencies with a "faster" CPU without any issues. Probably can go even further but I'm already fine with these values.
[Nexus 4 Android Development] moriel5:
I have a "fast" cpu (value: 3) (I had posted this on another thread that is also dedicated for this), which is what most people have.

Additionally, while this is generally correct, there have been multiple reports of even "slow" binned CPUs outperforming the "fastest" binned ones (including by someone who had managed to get ahold of all the differently binned ones, I'll share the link when I'll find it again), which is why I am not too worried (that, and the fact that I am not going to recommend anything which is too far off from the stock settings).
[Nexus 4 Android Development] xenyz:
Again if you guys want to undervolt, go right ahead: this kernel provides the sysfs entries for you to do whatever you wish with it on your devices! Kernel adiutor (mod) can even set them on boot, so you'll only ever have to do it once.

However changing the default kernel voltage values is a BAD IDEA as again, there will be a non-zero number of Nexus 4 which will be unable to boot to even be able to get to changing the undervolt back to stock.

I just don't understand why you're advocating to change default kernel values with this, the one setting which is dangerous to change, as it can result in devices being unusable.
[Nexus 4 Android Development] moriel5:
Actually, according to what I have read (and this includes sources such as der8auer), the main danger is in raising voltage, not lowering it (we are not trying to get subambient, undervolting to such a degree will require both serious overclocking, and extremely overkill cooling, and will have a high probability of damaging the phone due to freezing, however that is not a realistic situation in the first place).

The thought that there will even be one Nexus 4 thrown into a situation where this specific changes will be irreversible is completely mistaken.

The worst that can happen from this specific undervolt, which is a modest one, is that a device will run into a soft-bootloop, one which will be fixed by flashing any other kernel (the recovery is not affected, and at the worst, the bootloader won't be modified at all).

The hardware won't be damaged at all from this, and there wont be any situation where a Nexus 4 will have to go to the recycling bin as a result of this undervolt, which as a reminder, is a slight one.

However, I do agree that having two presets is a good idea, with the stock voltages as a failsafe mode, similar to what motherboard and graphics cards provide.

And please do not think that I am going completely gung-ho here, I am taking possible hazards into considerations, and thinking about the required precautions.
[Nexus 4 Android Development] TheGrinder77:
+1 to this

Not really sure about the flashing any other kernel part (if the new one allows voltage modifications they should apply on boot as well, correct me if I'm wrong) but for sure to revert to stock values you can just manually delete KA data folder from twrp or, more easily, boot in safe mode and clear KA app data from settings

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Android Development] moriel5:
That would not help if the settings are the default, which is why a failsafe option may have to be a backup kernel, to be flashed frok the recovery and/or the bootloader.
[Nexus 4 Android Development] bgoel4132:
any update for sinai n4 battery drain fix
[Nexus 4 Android Development] sudokamikaze:
Hi guys!

I've just built fresh version with battery drain fix! If everything goes well i'll release it tomorrow!

NOTICE for Unlegacy-Android ROM users

Do not use current build with newest rom build because you'll get bootloop

Because my changes got merged to official Unlegacy trees and my kernel isn't updated yet

I'll release everything tommorrow(including drain fix & spectrum support)
[Nexus 4 Android Development] sudokamikaze:
You're right. By the way, I think safe we can safetely undervolt to -25~50~75 for official builds

And someone who have "faster" cpu can manually undervolt to '-100'
[Nexus 4 Android Development] bgoel4132:
i am using the latest unlegacy build with the latest kernel unlegacy build for oreo 8.1 and it is running fantastic no bootloops great battey life everything seems perfect
[Nexus 4 Android Development] bgoel4132:
here are the screenshots
[Nexus 4 Android Development] Sam Nakamura:
Same goes for me...

Running UA build of May '18 with latest available SINAI, great experience, no issues, definitely no bootloop!
[Nexus 4 Android Development] sudokamikaze:
Strange, as you can see there's new commits that enables 64-binder

Anyway, they'll probably release new build with 64-bit binder enabled
[Nexus 4 Android Development] moriel5:
I apologize for my disappearance today, I was helping out at home.

The results from my 25mV undervolt are rather surprising (or unsurprising, I still do not have enough experience to truly judge this), however I need to turn off my phone now, and I'll be offline for the next ~50 hours or so, so I'll post them then, and after updating the kernel (which will be after the results will be posted), I shall move on to 50mV.

Other than that, this experiment has brought me a reminder of something I had noticed in the early days of SINAI-N4, and even in the HellSpawn days, which I am not sure whether anything can be done in the matter.

This too, I shall share when I am back online.
[Nexus 4 Android Development] d_g_m_2000:
wow

thanks for your work!

this new version with battery drain fix is for nougat or oreo? aosp or los? or both...

man can wait :fingers-crossed:
[Nexus 4 Android Development] sudokamikaze:
Of course for all
[Nexus 4 Android Development] d_g_m_2000:
thank you jesus:victory:

again.. very much thank you for your efforts
[Nexus 4 Android Development] bgoel4132:
is the new build ready to be published i am waiting for it eagerly
[Nexus 4 Android Development] bgoel4132:
what happened [MENTION=7970097]sudokamikaze[/MENTION] isn't the new build stable or upto your mark.. ??
[Nexus 4 Android Development] d_g_m_2000:
dude, it will be released when it's ready..

why do you wanna flash something that it's not finish and then bomb complaints about performance...

no ask ETA.. read the rules!
[Nexus 4 Android Development] bgoel4132:
i was just curious unlike you who has second phone for daily use
[Nexus 4 Android Development] d_g_m_2000:
nexus 4 is my daily driver... my other phones is a nokia 105 :( we have to wait.

hope OP can release soon.
[Nexus 4 Android Development] sudokamikaze:
I'm using my mako still as daily driver

And yeah, I've tired of those drainings too

I had 95 to 79 % overnight

That's why I didn't release it yet
[Nexus 4 Android Development] Sam Nakamura:
Secondary phone or not... it's still impolite and against the xda-developers rules, there's a "no ETA policy" in place for a reason, no matter how much a individual user needs the custom software (ROM, kernel, APP, Mod, etc.) or how many devices the user has, besides that it wouldn't be the first project on XDA I see dying because users keep ignoring basic rules, this can kill motivation, Devs are just humans and it's a hobby here after all, they don't get paid, they owe nobody nothing - what I mean is, be careful with such questions as they can make nice threads go sour & closed and this isn't in our interests, isn't in your interest, not saying that this is what's going to happen, not at all, but patience is a virtue and we all shouldn't forget that...
[Nexus 4 Android Development] bgoel4132:
Had you just read what i said i never asked for eta first grt that confirmed, before blaming someone atleast you should have confirmed whether the person is guilty or not and about those guidelines i have already read though. It was [MENTION=6807656]d_g_m_2000[/MENTION] who said ETA i was just asking about problem in the new build nothing else.
[Nexus 4 Android Development] Sam Nakamura:
No bad blood from my side but you're technically pressuring the Dev about his new release by impatiently questioning, which is by it's nature "ETA", when asked to not do it you justify it with "I have no secondary phone like you", without even knowing if that's true besides that it's irrelevant...

Believe me, I read it all but I'm still not out to blame you, I just say you might hurt yourself and other with being impatient, let them do their job, rest assured that progress or test builds will be announced here when the Dev feels like it - now please let us stop the off topic discussion and wait for the actual release, so that we can discuss about what this thred was intended for!
[Nexus 4 Android Development] sudokamikaze:
Hey guys

Battery drain fix has worked. I'll implement Spectrum support & cosmetic changes on kernel sources

And, proabably, release in the evening if everything's fine
[Nexus 4 Android Development] moriel5:
That sounds great.

Also, to everyone, I'm sorry I did not appear yesterday, I had fallen asleep.

I had to restart the testing a few times at the beginning, since I had to modify /system for several things, however I can say that my 25mV undervolt went without a hitch (the CPU Info overlay really helps with monitoring), however any differences were slight enought to be within the margin of error, so 25mV does not make a percievable difference.

My average temperature at idle was ~32-36°C, and under load, ~46-50°C

As to the issue I had noticed, this is probably a hardware limitation, however 720p at 60 hertz heavily taxes the CPU (overclocking CPU and GPU does not help), causing the phone to overheat (within 10 minutes I was almost at 65°C, with the only thing running being a Gamers Nexus clip running at 720p60hz via NewPipe).

The reason why I haven't seen this in a long time, is simply because I prefer to open clips with either my laptop or desktop.

I do not use GAPPs, in case anyone is asking, and I keep my running apps to a minimum (including disabling autostarts).

I utilize lightweight apps, such as Lightning Browser and MiXplorer, and I prefer WiFi over cellular (even though I have a 20GB plan (no more "unlimited" in my country since a few months ago (it used to be 20GB at normal speeds, and then unlimited at 2G speeds)), to the point that cellular is disabled most of the time (I don't have to be online all the time).

Next, I'll go back to stock voltages, update the kernel, and install the newer modded Kernel Adiutor, just to have a baseline, and then I shall undervolt by 50mV and test that.

---------- Post added at 08:46 PM ---------- Previous post was at 08:33 PM ----------

For some odd reasone, XDA Labs won't allow me to edit my post, so this is a seperate post.

Update: I'll wait for the for the kernel's new version's release, before commencing with the 50mV undervolt.

Update 2: XDA Labs seems to be drawing more system resources than it should, which is making the CPU stay between 44-48°C, even at idle (at least it does not usually go past 48°C, and the few times it had, it did not go beyond 50°C, except for once (today), since ambient temperatures were higher today, 30°C at the time I had started typing this post (and it was mid-to-late evening back then).
[Nexus 4 Android Development] sudokamikaze:
Just check that out!

It's almost working!
[Nexus 4 Android Development] sudokamikaze:
Here there is! Long-waited update!

Changelog as always:

Cleaned sources, removed unneeded commits

Battery idle drain fix(I hope that would work)

Spectrum support

Upstream changes from aosp 3.10 repos

Minor fixes

Also all wakelocks has been disabled

If you having some problems with them you can freely re-enable them back in KA

AutoSMP as default hotplug

Infromation about spectrum. Read that, please

You will have problem with switching governors if you using KA-Mod + Spectrum

Use only one of these app, do not combine them. I have already reported that problem in frap's thread

And there's an explanation: KA(Kernel-Adiutor) Changes permissions on governor's sysfs entries and spectrum can't change governos without changing permissions before. I'm not sure if this problem would appear on official KA or on other kernel tweak apps

There's possible workaround:

Disable 'Apply On boot' in CPU section and do not touch options that related to CPU frequencies & governor

Here's describe of which profile

Balanced:

Will be default state, rock solid options which I use every day

Performance:

That profile overclocks GPU, setup ASMP hotplug in best way to provide best performance

And changes governor to hellsactive

Disables FSYNC to provide best performance & ArchPower

Battery:

Smartmax governor, Lower max frequency

Decreases GPU freq to 120 MHz & Descreases RQ affinity to 1

ASMP tweaks as well

Gaming:

Default(400Mhz) GPU freq

Screenoff freq will be 91800

ASMP Hotplug tweaks to provide smoothness

And disables Arch_power

If you don't like these options or you think that you know better - Let me hear your suggestions and *may be* they would get merged
[Nexus 4 Android Development] bgoel4132:
Thats fantastic [MENTION=7970097]sudokamikaze[/MENTION], i am installing the kernel and will report you back by tomorrow.
[Nexus 4 Android Development] sudokamikaze:
I will be waiting for your results :)

I hope fixes will work
[Nexus 4 Android Development] bgoel4132:
is your new build updated for unlegacy also