yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] Benik3:
Well show me some good phone for decent price with clean Android...

Xiaomi did it pretty well. I don't want to buy again phone for more then 250$ because I found, that it's not really valuable.

I spend for Nexus 5X around 550$ and I must say, that I regret it a little. The phones are today too much consumer goods so it's pointless to put so much money to it...

Back to topic, 0,5%/h is f**** good. I have to test the phone without apps and google account to see, what happens.

The worse is, that I didn't find anything what cause this power consumption :/
[Nexus 5X Original Android Development] :
For xiaomi I must agree a bit because clean Android devices are:one plus, pixel and Nokia and there are too expensive for what they offer, personnaly I bought my nexus for 250 or 300 because of amazon reduction and 300 is for me a maximum, if I don't like xiaomi it's because it's make me think to huawei but it's very different and even milouk like xiaomi so for my next device I think I will look at it.

Back to topic again ? , I'm using aquariOS with latest sphinx preview and ground zero gapps(they are important for good battery).

Can share you my sphinx configuration in PM if you want.

Sadly the nexus 5X is becoming old and newer Android versions are never improving device performances, they just add power hungry features. So yes considering a new device is an option but I'm a student and without joking my bank account is at 0 ? so I will use my nexus until it dies haha.

PS: you are also using facebook like, facebook is a **** this app is so much power hungry.

PS 2 : for my pc I spent a lot 3/4 years ago and it's lasting, I must just replace the graphic card but I think that smartphones it's not the case and the obsolescence is more visible and that's sad for Android unthousiasts...
[Nexus 5X Original Android Development] Benik3:
Well I bought the Nexus when it was just new, because my old HTC Evo 3D just died (resp. Wifi and microphone died).

I don't like Huawei too, but Xiaomi is different for me :)

I didn't try AquariOS, I will probably give it a chance. Also I was using OpenGapps so I will try the Zero Gapps.

I know that FB apps are bad, that's why I'm using only the Lite messenger. But Kiwi browser is now able open the chat, so maybe it would be possible to use it too...

Why not to share the settings here? Maybe others will find it useful too :)
[Nexus 5X Original Android Development] :
I also looked at development for this xiaomi device and it will be great I think.

I use aquariOS because they need testers but validus,lineage and AOSIP are good too because they have app ops implemented. The best is lineage and milouk will agree too.

For the settings, they require the latest preview (3):

Then my settings are:

-cpu governor: BluActive for both(important to have the same governor for both little and big cores!!!)

-cpu frequencies: not overclock but underclock to 302Mhz for both (big and little cores).

-msm hotplugging enabled

-msm thermal enabled

-core control disabled

-adreno idler idlewait set to 5

-voltage at 640mV for all (works only if you don't overclock because if you overclock you will need higher voltages)

-for memory I disabled zram and uksm (but these settings are in high discussion actually and the dev will find a better way to optimize them but stay tuned, that's the main point of next update.

-io scheduler : Maple 512kb

-wakelocks : you can block all without any problems.

Other settings are good by default so I don't speak about them.

PS 1 : for latest preview ask me in PM if you don't have the link

PS 2 : I don't why but I have problems to control big cores (and I think it's not only related to thermal throttling but not sure as it's very hot where I live) so I don't know if core control need to be enabled with msm_hotplug but milouk told me that no.

PS 3 : a trick that I use when I need my phone during a day but I know that I couldn't reload it, is to lower the screen resolution so I can also lower CPU frequencies and power off big cores and lower gpu for a bit more juice.
[Nexus 5X Original Android Development] Benik3:
Thanks :)

I will wait with reinstall to new official update of Sphinx :)

BTW I'm using LineageOS now and I must say, that it's probably the most stable ROM I had on Nexus 5x...
[Nexus 5X Original Android Development] milouk:
3.1 Preview 4

This is the final Preview before 3.1 release. I'm not going into detail about changelog since i'm going to announce everything once on 3.1 release. This is just for the curious ones that PM me. If you want to get an idea of what has changed check Github. For those who'd rather wait for the official release here is a hint:

Many Many Many Many changes, additions, improvements, fixes.

https://www.androidfilehost.com/?fid=5862345805528063008

P.S: 3.1 will be released right after August Security Patch is released.

Cheers:highfive:
[Nexus 5X Original Android Development] :
Thanks to have improved the lmk module.
[Nexus 5X Original Android Development] milouk:
And its not just that. ;)
[Nexus 5X Original Android Development] :
Yeah but I let the surprise for the other users ?
[Nexus 5X Original Android Development] jugoslavpetrovic:
Preview4 testing. Enabled sleepers and hotplug, also dynamic lmk, for adreno idler wait to 5, both cores to 302-1248mhz.

As awake, performing fluid so far, will see for the battery and waking up.
[Nexus 5X Original Android Development] milouk:
Gentle Fair Sleepers should be disabled for extra smoothness.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Thanks. Anyway want to see how it goes with.

Fast charging, though, seems to not working on my side, AICP ROM, I don't know if that matters, also I have 2m cable so it could be it maybe.
[Nexus 5X Original Android Development] milouk:
Force Fast Charge is only for USB charging through laptops or through charging bricks with up to 1500 mAh. It basically raised the maximum input from 550 mAh up to 1500 mAh. But again you will see the change if you charge your phone through a usb port.
[Nexus 5X Original Android Development] Benik3:
2m is pretty long, I recommend at least 20AWG cable to handle the current...

I use still original LG cable and I didn't saw any problems with charging (I don't look on the text, just assume by the time of charging :) )

P.S. Original cable is 1m 23AWG

That's enabled by default or user must allow it? Because it can be very dangerous mainly when connecting the phone to a PC...
[Nexus 5X Original Android Development] milouk:
First of all let me clarify that USB Fastcharge has been tested and does INDEED work. You can download Ampere from Play Store and see that max Input is now 1500 mAh instead of 550 mAh.

Morever, it is the same commit that exists in other Roms like AOSiP so it is not dangerous (Not even one user has reported issues with it). Nexus 5X can handle a current up to 3A so 1.5A wont do any harm. A PC on the other hand can provide up to 1.5A so no harm there either.

Also the current is not stable it changes dynamically (check with Ampere) and it almost never at its max value (3A for regular charging and 1.5A for USB charging). Finally this feature is disabled by default so unless you want it there is absolutely no reason to enable it.
[Nexus 5X Original Android Development] Benik3:
Wrong! Normal USB PC port has maximum of 500mA! (That comes from old standard for USB 1.1, USB 3.0 has standard 900mA).

There is of course USB Battery Charging standard which allow 1,5A, but that's primary for chargers.

Well I have PC with front 2 USB. These USB are from motherboard through small internal HUB. And I have partially damaged these ports probably by overcurrent.

On the start they worked OK, but now when I put in the port something with higher current (and it even doesn't need to exceed 500mA) these ports "disconnects" and I have to restart whole computer to get them work again.

This is probably caused by overcurrent because I used them also for some electronic projects and I wasn't careful.

So think that every PC USB port is able handle 1,5A is very dangerous, because they can be really designed only for 500mA.

Luckily lot of the PC/NB has overcurrent protection. But I also already saw notebook with fried USB...

Also exist motherboards with specially marked USBs with higher current...

USB of the PC is not mean to charge your phone!

P.S. the charging current can vary because of temperature of the battery and also at the end of the charging it came to the constant voltage mod of charging, where current start to fall down.
[Nexus 5X Original Android Development] milouk:
You are right that is what i wanted to say by "up to 1.5 A" but placed it wrong. (Its 02:46 where im living so excuse my mistake :D)

Though, the cable plays an important role to configuring the current between phone / PC (thus there are verified cables e.x the ones approved by benson leung). Morever the code itself determines what kind of port is on the pc end and adapts the current accordingly. For example when i tested this feature i had 770 mAh input which is higher than 550 mAh (which is the devices stock).

Anyway im sure there still is a risk but there are users willing to take it. Im not the author of the code and thus i gurantee nothing but i know for sure that there are roms out there using this piece of code and no one has complained yet.
[Nexus 5X Original Android Development] synesthete:
Will this kernel work on AOSP/Stock Android even though it is based on LineageOS?
[Nexus 5X Original Android Development] jugoslavpetrovic:
Sure, I believe so.
[Nexus 5X Original Android Development] :
That's the principle of a USB Killer (look on Google if you don't know) but it's no more working on most pc as they are protected again this so that's why nobody have had problems.

So I don't know how old is your computer or if it's a good brand or bad but it's really strange that you have problems.

Furthermore milouk has just added this feature but he left it disabled by default and he is no responsible in any way, you are on your own when flashing a kernel.

Have a nice day.

PS: as you said USB is not mean to charge a phone and that's why milouk has disabled it by default so don't come criticizing this feature please.

PS 2 : [MENTION=5533673]milouk[/MENTION] you last preview is running very well, you are awesome thank you!
[Nexus 5X Original Android Development] milouk:
He didnt criticize anything he just had questions thats is perfectly ok and it promotes healthy discussion.

Hopefully some more nice features will be added today ;)
[Nexus 5X Original Android Development] Benik3:
Well I have 1 year old PC with MSI Z170A Gaming M3 :)

The USB killer can still works. The best way is to use step up convertor and huge capacitor. Charge it up and bang! :P The USB will not survive the high voltage high current peak :)

I just asked for info. If it's disabled by default and the USB recognition still works OK, then I have no problem with it :)

Thanks for the replies!
[Nexus 5X Original Android Development] Doomkopf:
This is a little OT, but I think this is very important :D

There is a general N5X problem (NOT caused by this kernel), that this phone gets stuck at Google-logo when booting. This issue is connected with the big-cluster, so disabling it with a modified boot image solves this problem, but isn't really optimal, because then you can't use big cluster after booting, too, so this hits performance.

(Source:

https://www.xda-developers.com/nexus-5x-bootloop-fix-boot-phone/)

I wrote with milouk about possible fixes, but first it would be important to know if anyone else except me is experiencing this bug. So, is this happening to you guys also?
[Nexus 5X Original Android Development] nirogu325:
It's totally off topic. It's not a bug. It's a hardware problem and it's a widely known one. Partially fixable via developer osm0sis' kernel/recovery patcher. You can find his thread with the universal patcher in the Nexus 5X General forum. I say partially fixable because there have been users who eventually end up losing the other half of the processor as well. With the universal flashable patcher, you don't have to request help or fixes from anyone else. With that said, please let's get back to topic.
[Nexus 5X Original Android Development] Doomkopf:
I think you got me wrong. What you said is correct, I also stated that in my first post - what's makes this problem NOT totally off topic, is that this issue can be solved by for example disabling big cluster at boot, but not completely. This would lengthen the time of boot, so I (and milouk) have the interest to know, how many people are actually affected by this. That problem can be solved without osm0sis zip, which would also be a pretty neat "feature" of this kernel.
[Nexus 5X Original Android Development] nirogu325:
You are losing the point of the word "universal". Meaning you don't have to bother anyone into making a very specific build when you can just flash that zip file at the end of the flashing. What you're asking is totally redundant. Here is the thread for the universal patcher: LINK
[Nexus 5X Original Android Development] Doomkopf:
Yeah, but if that universal solution isn't optimal and a better solution can be achieved specifically in this kernel, why not? I don't get why you refer so vehemently to the universal solution, if milouk can (maybe) achieve a better one. With osm0sis solution, you can't use big cores in android. (Maybe) with milouk's solution, exactly this is possible. Don't be so closed-minded man :D
[Nexus 5X Original Android Development] nirogu325:
I think before you get to insulting, calling other people close-minded, you need to inform yourself better. I'm giving you the solution to your problem, a solution that helped a relative get her N5X back functioning and the speed difference is not huge. You clearly do not understand the root of the problem and why BLOD happens in the first place. Get back to me through PM once you do proper research. One more insult and you'll get reported :D
[Nexus 5X Original Android Development] Benik3:
You can even find modded TWRP wit big cluster disabled to prevent BLOD and to be able still flash the phone :)

Anyway stuck on boot logo can be also caused by Magisk (it happen to me and I thought that it's BLOD, but wasn't)
[Nexus 5X Original Android Development] Doomkopf:
"Close-minded" is no insult to me, but if it is to you, I'll take it back. The thing about the insults applies to you either, I don't like your tone (referring to proper researching). I can only again say that YES, what you say is correct. There is a solution, it's not optimal because it affects performance (no matter at what degree), and there could be an optimal one. So; I would like to end the discussion with you, because none of us benefits from it.

Which gets me back to my initial question, to help milouk assess the situation:

Does someone in this thread encounter the phone being stuck at google-logo?
[Nexus 5X Original Android Development] nirogu325:
You still don't get why BLOD happens and refuse to educate yourself about it. Got it. No more wasting my time.

---------- Post added at 01:40 PM ---------- Previous post was at 01:34 PM ----------

Exactly, it's all in the thread I referenced. Only people that have read about BLOD know it's a physical problem and NOT a software one. :highfive:
[Nexus 5X Original Android Development] :
Hey guys, yeah it's hot today but relax.

So all people here know that nirogu is right, blod is unfortunately an hardware issue and nobody can change anything, the only partial sovling is to disable big cores but someone told me that after a few time it will also impact the little cores so there's nothing to do and if it was the case Google and LG will have solved this problem a long time ago for reputation purpose.

So now I think that de must concentrate again on sphinx development.

Have a nice day all and keep cool, sphinx is the best kernel and best community so don't break this.

PS: It's maybe a dumb question but are all the nexus 5X doomed to BLOD ? (sorry [MENTION=6530865]Lughnasadh[/MENTION] , you already answered me but I'm so scared about this ? )
[Nexus 5X Original Android Development] Doomkopf:
Alright. I agree with you, especially with the last part. What I tried was improving the kernel, no bad intention. Of course I did my best researching that topic before (just to clear this up, I know that it's a hardware issue), but I think it can happen to anybody that he's wrong. What bugged me was how I got treated even though I had no bad intention. Tbh I still don't get why my idea was wrong (I only wrote it to milouk and nirogu, expecting PM's), but I'll just trust you guys on that one I guess haha :D

Have a nice day

Edit: read everything again and realized I might have gotten the wrong end of the stick. Sorry ^^
[Nexus 5X Original Android Development] jugoslavpetrovic:
If you are talking about BLOD, that is something alse and [MENTION=5533673]milouk[/MENTION] might be able to make it by request only for those affected by that like you. Still, it's still his decision. I don't have that issues. But as said there is universal patch that you should use together with this kernel, and there is 4-core twrp as well.
[Nexus 5X Original Android Development] nirogu325:
I hate to be that guy but it's inside the realm of possibility. Take a look at the forum of each device that has the Snapdragon 808. You will inevitably see BLOD incidents. I still have no idea how Qualcomm kept manufacturing that chip without revisions.

Edit: Newer processors don't have that issue. For example the Snapdragon 845 runs super cool on my OP6 and I haven't heard any more BLOD fiascos in a long time for newer processors. Correct me if I am mistaken.
[Nexus 5X Original Android Development] :
Ok I must be more exact "is the blod inevitable, is it going to impact all users or it's random or even manufacturers don't know?"

Oh you have the oneplus 6, how is it compared to the nexus 5x, your answered will be for sure "one million quicker lol".

And yeah I confirm that there is no more problems with that on newer processors but it's normal they surely improved their testing methods because the only fail will drive them to lost millions of dollars.
[Nexus 5X Original Android Development] nirogu325:
That first question would be impossible to answer. You'd have to judge based upon how widespread the issue is. About comparison between N5X and OP6, there's no comparison performance-wise. Granted, we're also talking about eMMC 5.0 versus UFS 2.1, LPDDR3 versus LPDDR4X and a 20nm processor versus a 10nm one. Alright, OT's over, lol.
[Nexus 5X Original Android Development] jugoslavpetrovic:
If enabling the new hotplug do I need to also enable any other thermal or to disable and which one to go fine along?
[Nexus 5X Original Android Development] :
I personnaly enabled msm_thermal and core control.
[Nexus 5X Original Android Development] Benik3:
Well I have Nexus 5X from beginning and it's still working fine, even that I heated the phone many times :)

So maybe I'm just lucky, or the other peoples was "lucky"...

The worst thing for it is heat and cool down the CPU often in high temperature range (because BLOD is caused by cracking of the solder between the chip and his substrate).

I have now enabled only msm_thermal.
[Nexus 5X Original Android Development] milouk:
Hey guys!! What happened here? I just came home from a night out and WOW that took me by surprise.

First of all, i would like to say that [MENTION=7472582]Doomkopf[/MENTION] PMed me about his issue. He politely asked if i could just disable big cores while booting and enable them once the phone has booted just to avoid a bootloop. I too told him about 0sm0sis BLOD zip, and he himslef understood that he made a mistake and apologized for that. -even though mistakes are meant to be made so no reason to apologize-

I would like to point out too that this thread has been for me too a source of joy and inspiration. I have learned a million new things and i have improved myself in many different ways as i believe all of you too. Dont break this please. There are still many things one can offer to another and you all are great people with much knowledge and passion about android. Respect, patience and passion are key . This thread is more than a kernel thread. This thread is a place where everyone can share their opinions and ideas -right or wrong- without getting judged, and inthe same time get wiser. No one should feel uncomfortable or shy. There are no stupid questions, observations, comments etc. Everything is acceptable. So lets all shake hands and keep it rolling!! Share the Knowledge!

I personally cannot wait to release 3.1 i have so many things i wanna share with all of you!

Peace out my friends!

P.S: im not drunk , i dont even drink alcohol but it hurts to see so many good people "fighting" over pointless things.
[Nexus 5X Original Android Development] Lughnasadh:
I know we talked about this earlier, but the BLOD is not necessarily inevitable, but not highly unlikely either :cyclops: . I would just make certain to keep the big cores as cool as you can, e.g. no overclocking and no thermal throttling mods or tweaks that would increase the temp at which the big cores throttle or go offline. Maybe even think about underclocking the big cores. I also have VDD restriction enabled on my BLODed Angler and that helps with keeping the voltage down (maybe consider undervolting the big cores as well?).

There are a few things to make a BLODed device faster, but the most simplest one, without messing with the cores (imo), is to turn animations in developer options off (or to .1x like I have done on my Angler). Its amazing how this affects the speed of the device. My Angler, although not as fast as before the BLOD, is still pretty snappy after I did this.

Just do the little things that you can, forget about the things that are out of your control, and enjoy your device, would be my unsolicited advice :)
[Nexus 5X Original Android Development] nirogu325:
For my BLOD unit I set those animations to 0.5x and undervolted -20mV all across. The performance difference compared to my main N5X is not big and the device is almost always cool despite the very hot and humid weather we're having. Had no idea what VDD restriction was so thanks for that, it might help some more.

Also [MENTION=5533673]milouk[/MENTION], no one is breaking anything, no need for campfires, etc. The right information was pointed out and the person apologized both publicly (no need) and privately. Evidence that supported the information was also given privately and that's what matters: to be informed to keep our devices alive and as fast as possible.
[Nexus 5X Original Android Development] milouk:
I have exlained VDD restriction in previous post but users reported that it didnt play well. Anyway i have noticed that jolla removes it s part of his thermal patches so in 3.1 it will be removed. (I can bring it back i you want but im sure he kmew what he did and personally i dont miss it)
[Nexus 5X Original Android Development] nirogu325:
Hmm, in that case I'll follow.
[Nexus 5X Original Android Development] Lughnasadh:
Yeah, I would recommend only using VDD restriction if you have a BLODed device. In that case it helps (with no negative side effects on my BLODed Angler) and I "believe" Osm0sis has that enabled by default in his BLOD_Workaround_injector zip (assuming kernel support for it). At least it is enabled by default on my BLODed Angler after using his zip.
[Nexus 5X Original Android Development] jugoslavpetrovic:
[MENTION=5533673]milouk[/MENTION] thumbs up for the speach. Such a guy you are.

As for jolla kernel I am not sure how he was concerned about BLOD and his kernel was having thermal threshold at 60 and as at the time it was not such big deal for most ppl. It is now seems different, so I guess if there is no harm VDD can be left included and off by default.
[Nexus 5X Original Android Development] milouk:
This is the commit https://github.com/milouk/Sphinx-Kernel-Bullhead/commit/6b6134a499c77114fc08d4b1afda9cdb3da8cebc . It just disabled VDD. If you all want it , i can easily revert it.