yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Bad news :( As you said, this is a hardware fault, so I'm getting very inconsistent results on boots, sometimes it randomly won't vll lock, and sometimes I get random fatal interruptions, (most likely the BIG cpus failing or something of that nature) I'll do some more testing, but I think that this is a lost cause, thank you for your help though.
[Nexus 6P Q&A, Help & Troubleshooting] programmargorp:
Alternatively if it is the plls I believe you can I init pll_a57_0 and mux that to the big cores.
[Nexus 6P Q&A, Help & Troubleshooting] fuadhdmini:
I still have faith in Nexus 6p and you guys are going somewhere. Keep the awesome progress!
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Do you have any idea how would I go about doing that?

In the clock-pll driver there's this entry at the bottom:

MSMCLK_PARSER(votable_pll_clk_dt_parser, "qcom,active-only-pll", 0);

MSMCLK_PARSER(votable_pll_clk_dt_parser, "qcom,sleep-active-pll", 1);

MSMCLK_PARSER(votable_pll_clk_dt_parser, "qcom,votable-pll", 2);

Does this mean that pll_a57_0 is in charge of CPU frequencies while the CPU is active, and that pll_a57_1 is in charge of the CPU while it's in deep sleep?

If I'm correct, then does that basically mean that the a57 cores would work, but they would always be active and not able to go into deep sleep?

I also saw a post somewhere about if you could make a vll lock failure non-fatal, but someone said that could be dangerous, is that true?
[Nexus 6P Q&A, Help & Troubleshooting] programmargorp:
Will have to investigate how the pll is set up to say for sure.

You can ignore pll locks at the expensive of system stability, i.e. you have no guarantee that your clocks are stable.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
I'm almost certain this file is where you would mux a57_pll1 to pll0: https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-nougat-mr2/drivers/clk/qcom/clock-cpu-8994.c

I have no idea where the hell to start with muxing this though, do you have any idea on how to mux it?
[Nexus 6P Q&A, Help & Troubleshooting] AndreiLux:
https://android.googlesource.com/ke...at-mr2/drivers/clk/qcom/clock-cpu-8994.c#2296

Problem is you need to know the register maps on how to set the PLLs and MUXes properly, right now they're just hardcoded with some values. Even if you reverse engineer it to properly change it you still need to know what the secondary PLL is actually clocking and if you can tap into that.

https://android.googlesource.com/ke...gat-mr2/drivers/clk/qcom/clock-cpu-8994.c#781

The mux you need to change is a57_hf_mux_v2 for it to use source3 (PLL0) over source 1 (PLL1).

Any way it looks like the PLLs are chained together so I doubt this will lead to anything. You can confirm it's the PLLs at issue by clocking into GPLL0 fixed at 600MHz, but again, good luck with the registers.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Damn, ok. I'm trying to make a kernel for hotplugging right now, but SELinux is being a b*tch. Do you/or anyone else have any idea how to disable it? I've tried disabling everything in the config, but it still won't go away.

Update: Apparently deleting the security folder doesn't work... lmao
[Nexus 6P Q&A, Help & Troubleshooting] myfluxi:
Another attempt to work around the obvious* hardware issue: Change line 316 to "udelay(2000);". See how it goes.

* They went from recommended 5 to 10 to 50 to 200us there. Not normal.
[Nexus 6P Q&A, Help & Troubleshooting] myfluxi:
Here is another one on top. Instead of panic'ing, just error out and let the clock and cpu infrastructure's error checking mechanisms do the rest. After the follwing load check a few ms later another attempt to boot the cpu will be made, no harm done. If it works, the kmsg spam should be in a conditional for debugging purposes.

clk: qcom: clock-pll: Return error if PLL clk enable fails

I do not own the device, I built my last kernel almost a year ago. I just learned about the issue here today.
[Nexus 6P Q&A, Help & Troubleshooting] myfluxi:
Oh, and there is an error in the cmdline in probably all those "fixed" boot images that restrict cpus to the small cluster.

Command line:

console=ttyHSL0,115200,n8 androidboot.hardware=bullhead [B]boot_cpus=0-4[/B] maxcpus=4 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 buildvariant=user

cpus are enumarated from 0 and thus it should read "boot_cpus=0-3" (overriden by "maxcpus=4" anyway...).
[Nexus 6P Q&A, Help & Troubleshooting] _Ghost:
[MENTION=5288606]XCnathan32[/MENTION] I'm willing to test this on a 5X if you could do it. I'm not a dev but I can help in this areas by testing.

All the Luck man!
[Nexus 6P Q&A, Help & Troubleshooting] ryanbg:
RE: Hardware fault. I'm starting to wonder if chips were binned improperly, and that the voltage/frequency table could use a little adjustment in the device tree. It almost seems as if they aren't getting enough power. Have you looked into this at all? I don't have a failing device but it'd be interesting to see if we bumped up the table 50-100mV universally to see if the issue would persist.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
At first I did boot_cpus=0-3, but after realizing that it was irreverent due to maxcpus=4, I stopped changing that setting, purely due to lazyness lmao.

This looks promising, this patch is exactly what I was looking for, hopefully this can be the fix.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Awesome, if this works on the 6P, then i'll PM you for testing.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
I'll try this if the above patches don't work.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Update: applied the 3 commits and the device is stuck on the Google logo, no bootlooping though, will wait a bit longer.

Update 2: Looks like we might finally have some good news, I waited a couple minutes and it didn't boot, so I hard reset it, and pulled the console-ramoops, and uploaded it: https://pastebin.com/CGx07hNP

It seems very hopeful, init made it to the second stage, the problem seems to be being unable to mount partitions/dm-verity errors, will do a couple more boots and see if anything changes.

Update 3: Tried booting again, and this time it bootlooped, after pulling the log: https://pastebin.com/N8tKSLJi the PLL didn't lock, but the system didn't panic, as intended, so it kept booting, unfortunately, this time watchdog seemed to shut it down. Not sure why PLL appeared to lock the first time but not the second... ughhhh. After looking up some stuff, Watchdog "Bites" (resets device) if it is not "Pet" (system resets the timer I assume) at certain intervals. So basically if the system becomes unresponsive, watchdog resets it. It makes sense looking at the random time gap in the log, from the last event, to the watchdog bite. Not sure why the system would become unresponsive if it's only supposed to use CPUs 0-3 for boot...

Update 4: Interesting find: After pulling multiple logs, I found that most of them looked almost exactly identical the the second log in the 3rd update. (although in one log, watchdog bite failed and ended in kernel panic) tried powering off the system from recovery, but it would start up automatically, ramoops said the power-on reason was "watchdog" So I rebooted to recovery, selected reboot to recovery in recovery (to reset the watchdog power on) and then when recovery booted again, I powered off the device, it stayed powered off this time, so I let it sit for about a minute, and powered it on again, now it's hanging at Google logo instead of resetting. So for some weird reason, cold boots cause vll to lock (I think) and restarts cause it to fail lock and become unresponsive, and then watchdog bites. Here's the ramoops from that boot: https://pastebin.com/wjb9EQvF Seems to be same errors as the first boot, verity errors/files not found/stuff not mounted, etc.

Also, after looking over the logs from when it bootloops, I noticed more errors like "BUG: scheduling while atomic: swapper/4/0/0x00000002 (line 497, and happens more later) CPU 4 also is tainted in the log, and "WARNING: at drivers/clk/qcom/clock.c:419 clk_disable+0x84/0x15c()

a57_clk is unbalanced" (lines 580 and 581)

I uploaded the rest of the logs to my pastebin account here: https://pastebin.com/u/xcnathan32/1/0/1/?o=a1 so anyone can look at them if they want, however I didn't think they were important enough to link each one individually.
[Nexus 6P Q&A, Help & Troubleshooting] myfluxi:
Try these patches separately. 2000us first, if the device does not boot, it's useless and can be forgotten. Then the second one that just errors out instead of panic'ing. The third one is a bit weird, dunno if it does any good.

Oh, and try with "boot_cpus=0-3" as well, especially the boot phase is critical.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Ok, will do.
[Nexus 6P Q&A, Help & Troubleshooting] ryanbg:
Let me know if you need help. I'd like to note I believe this might be the case because not every device is affected, and there's been obvious issues with the quality and consistency of batteries amongst devices. Definitely worth giving a shot. If the issue were the PLLs, you'd think the issue would be universal amongst all devices.
[Nexus 6P Q&A, Help & Troubleshooting] Bobbaloo:
This is amazing. I don't have this problem (yet?) but, I totally enjoy watching all these great minds getting together trying to puzzle it out. Almost like Einstein and his physicist friends at the blackboard
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
All of the first logs I did with all patches were 0-3, I did a couple tests with all patches and 0-7 boot cpus. I noticed some interesting differences, Try 1, this was right after flashing it, vll failed to lock, but at the end, it seems to end earlier than 0-3, and it says "Fixing recursive fault but reboot is needed!" as opposed to the watchdog bite with the 0-3 cpu boot.

I tried powering it on from a totally off state next Try 2, and it made it didn't bootloop, just stayed stuck on google, log reveals the same errors with verity/unable to find files etc. T3 log is the same as the first one, Vll lock fail, "Fixing recursive fault but reboot is needed"

Then I tried only the 2000us patch, did 3 tries with 0-3, Try 1, and 2 tries with 0-7, first try. All 5 of them were pretty much exactly the same, cold boot or restart, bootcpus=3 or 7, same error, didn't PLL lock, shut down. When the phone automatically booted up after I shut it down, boot reason was "watchdog_nonsec" as opposed to the boot reason "watchdog" with all the patches. I doubt that means anything. Rest of the logs are on my pastebin, not much to see though.

Going to try building the kernel from EX kernel source, and applying all patches, as EX kernel has dm-verity disabled, so maybe that could solve the problem with verity errors and not finding files.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
That would make sense, but the person I bought it from had just replaced the battery, so unless he got really unlucky and bought a defective battery, I wouldn't think that the reason my device won't boot would be a battery error. After I'm finished testing the Github commits, I'll work on the voltages.
[Nexus 6P Q&A, Help & Troubleshooting] ryanbg:
Yeah, from the sounds of it now, the 20nm process the Snapdraon 810 was built on wasn't finFET and wasn't very great. So I'm wondering if they just binned very 'generously' and some chips slipped out of the factory that really shouldn't have. It would explain the PLL issue I guess, who knows.
[Nexus 6P Q&A, Help & Troubleshooting] programmargorp:
I somewhat doubt that's the issue. I don't have the sources to back this up but I'm pretty sure the <--> indicates voltage range. Vdd is likely set to 0 to save power.

If anything the PMIC is giving out correct voltages later on in the log.
[Nexus 6P Q&A, Help & Troubleshooting] TheIronLefty:
You mean this guy is the culprit for the battery and bootloop problems?
[Nexus 6P Q&A, Help & Troubleshooting] ryanbg:
I don't think the voltage is wrong, I don't think there's enough and the chips were not properly binned.
[Nexus 6P Q&A, Help & Troubleshooting] adbanginwar:
firstly, thank you so much for providing the fix. my 6p did bootloop few days ago but it started working after i cleared dalvik and cache. it is now up and running though i don't know how much more it will last.

were you able to replace PMIC XCnathan32? I am planning to visit ubreakifix guys and ask if they can replace PMIC and battery for me.

Edit 1 : they do not replace ICs.
[Nexus 6P Q&A, Help & Troubleshooting] ryanbg:
To fix the voltage issue, we wouldn't replace the PMIC. We would adjust the device tree to increase voltage for each frequency step in the cpufreq tables. No need to replace hardware here.
[Nexus 6P Q&A, Help & Troubleshooting] adbanginwar:
could you please point me where i can do that? i am on dirty unicorn latest official build.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Update: Sorry for kind of abandoning this project, with the core utilization fix, the device runs so well now, that I feel like getting a fix for all 8 cores is not necessary. I would rather focus my time and attention on improving and maintaining the 4 core fix. With all 8 cores enabled, the 6P gets rather hot, which means it's more uncomfortable to hold, as well as it can impact the longevity of other components. Increasing voltage would also make the thermal issue worse, and reduce battery life more, so I feel like the better option for longevity is to use the 4 core fix.

However, many bright minds have given good suggestions in this thread, so if anyone else would like to pick up the torch on development, feel free to go ahead.
[Nexus 6P Q&A, Help & Troubleshooting] fuadhdmini:
This explanation and your semi-angry-rant on the fix thread makes sense.

No point of getting all cores working if in the end the SD810 itself is the root cause of the issue.
[Nexus 6P Q&A, Help & Troubleshooting] fmatosqg:
I've heard this fix won't work on O preview, is that right? Can't remember where I saw it.

I had O preview 3 and applied the fix, but it was stuck on the logo. Then I flashed 7.1.2 and only after doing a factory reset (was it necessary?) the phone finally booted. The first 2 complete boots were quickly followed by a crash message and a few seconds later there was a reboot. After that it started behaving as expected.

Thanks a lot for bringing it back to life.
[Nexus 6P Q&A, Help & Troubleshooting] fuadhdmini:
Yup, it's mentioned in the fix thread OP https://xdaforums.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
[Sprint LG G6 Questions & Answers] tri_cchan:
How can I force roaming on other networks on my Sprint LGE LS993? Sprint signal isn't too good travelling through rural parts of West Virginia, and in those rural areas, Sprint will sometimes roam on AT&T, which has amazing speeds there. I'd like to force roaming while travelling through there. How can I do that without rooting? LS993 roaming on AT&T (Phono showing AT&T logo): LS993 not roaming (Phono showing Sprint logo):
[Sprint LG G6 Questions & Answers] Mr nerd:
I'm pretty sure you need root for that, since you have to change the prls and pretty much trick the phone into force roaming with prl file, you need root in order to write it to the phone sysyem
[Samsung Galaxy S8 Questions and Answers] tenaciousj:
My S8+ has randomly froze a handful of times so far. Every time its done so the screen has been on and nothing will turn it off or reboot it. The only way to get it to work again is if I put a headphone jack into the port. Then it will unfreeze and starts playing catch up with all the buttons I hit while trying to get it to work again.

Anyone else ran into this or know what may be causing it? Phone is bone stock AT&T fully updated.
[Samsung Galaxy S8 Questions and Answers] lennyk1313:
I am having the same exact problem today.
[Samsung Galaxy S8 Questions and Answers] tenaciousj:
I figured I wasn't the only one. Just a weird issue. Never had anything like this before.
[Samsung Galaxy S8+ Questions & Answers] mike26301:
For the past couple of weeks everytime I download an app it doesn't show up in the launcher or home screen. I've able to launch the app form the play store and by BIxby. I can also search the app launcher and it pops up, but the icon its self wont show up. Can anyone please help me. I already deleted the data in the app information on Touchwiz home and restarted my phone. Factory resetting my phone is not an option because I'm enrolled in the Samsung Insights program which grays out the option to factory reset the phone. Any help would be appreciated.
[Samsung Galaxy S8+ Questions & Answers] Mr. Orange 645:
Well, without a factory reset, I'm not sure. Can you contact the Insights Team and explain it to them? Maybe they can help you or tell you how to factory reset it.
[Samsung Galaxy S8+ Questions & Answers] Itaintrite:
Why don't you use a 3rd-party launcher until somebody figures this out?
[Samsung Galaxy S8+ Questions & Answers] onkarsingh_pardeshi:
Which apps ? can you name those ?
[JAMin, XDA Neo, S200 Software Upgrading] mike_bite01:
all i can see is the boot screen of i-mate w/ "I PL 2.13.001" and "SPL 2.G4.4PDA" and "GSM 02.20.21". i tried to follow WM6 upgrade guide. i did HardSPL. Help please.
[JAMin, XDA Neo, S200 Software Upgrading] dioxda2:
go to my signature ( the link )

Enjoy ~~ :D
[Zenfone 5 Q&A, Help & Troubleshooting] KauzDs:
Hi, I'm new to the forum.

Lately I'm having this problem where my phone ALWAYS freezes right after the main screen appear (sometimes I get to mess around but it always freezes). Resetting it to factory setting sometimes fix it but if I disconnect the charger it immediately freezes and I have to reset it again. In the past it only froze when the charger was turned off but now it is freezing even on the boot screen (2nd asus logo).

WW

Unlocked Bootloader

TWRP recovery

Xposed framework latest version

Rooted

android 5.0

I saw some threads about unlocked bootloader freezing the phone but I don't know if my problem is related to it but later in the weekend I may try the "fix".

Thanks.
[Xiaomi Mi Max 2  Questions & Answers] lacort:
Is there a way to remove the noise reduction/cancellation when you're recording a video?

Sound quality is good when recorded in a quite place. But if it is recorded in a noisy environment (like a live band), the sound quality becomes garbled. Friend of mine told me that there's a noise reduction. I have no idea how to turn it off.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] JT1510365:
Hello there everyone my recommended shortcuts in the notification panel for earphones plugged in are disappearing after 5 or 10 minutes can someone help me figure out this problem? It happens only on my tab 4 sm-t230nu
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Casey98:
Okay so i have been using my s6 edge for a while and got bored with the stock rom and the root was successful but when i flashed twrp onto it i rebooted and it stays on the Galaxy S6 Edge sreen (the one before the flashing samsung logo) it also says "kernel is not seandroid enforcing " but just stays on this screen until the batter dies out i have tried using odin and odin can't read it i tried samsung kies but that can't read it either so i have deemed my pc useless in this situation

really need this phone to work so any advice would be much appreciated
[Galaxy S6 Edge Q&A, Help & Troubleshooting] callumbr1:
Can you get into download mode or recovery mode?

If you can get into recovery mode then wipe data/cache.

If you can get to download mode flash stock firmware and start again.

To get into recovery hold only down and power for 10 seconds, as soon as the screen goes off to reboot switch to recover combo, home and up amd power for 20 seconds until it boots to recovery. Try that first.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Casey98:
this is where my problem begins the home button on the phone clicks but doesn't work the fingerprint sensor still works fine thats it so i was using adb commands from the terminal to boot it into recovery/download mode but now it just gets to the galaxy s6edge screen then just stays there so my computer can't read it so its stuck
[ONE Q&A, Help & Troubleshooting] Sarabveer:
Hello,

For the past few months, I've been having Signal issues on my OnePlus One. It started randomly. I have tried different modems and roms, but to no avail. Also, my back cover was broken (around the antenna part too), so I bought a brand new StyleSwap cover, and still the issue is there.

The issue is that I rarely if ever receive LTE signal on my phone, when I used to go to school, I had 3-4 bars of LTE, now I only get EDGE at school. At home, I get 4-5 bars of LTE, but when I do a Speedtest, I get 0.5mbps download and 0.1mbps upload.

There is something definitely wrong, and it just started happening one random day.

FYI, im currently running Sultan 14.1 with the 241 modem, I also tried the OOS 2.4.1 Modem, which still had the same issue.
[ONE Q&A, Help & Troubleshooting] Mr.Ak:
I think you should test all available firmwares.

https://xdaforums.com/oneplus-one/general/firmware-modem-oneplus-one-t3462214
[ONE Q&A, Help & Troubleshooting] Sarabveer:
I already tried that.
[General Questions and Answers] tafds163:
I am able to connect my phone (lenovo vibe c2 k10a40) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. I would appreciate any help.

I'm sorry for my English, I'm brazilian
[General Questions and Answers] Droidriven:
Try connecting a USB mouse to your device, you will need an adapter or an OTG cable to use it, you can use the mouse to make your selections instead of the volume buttons..

If you need to be connected to more than thing, you can connect a USB hub to your phone then connect to the things you need.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[General Questions and Answers] Ranisblogru:
Otg not work in fastboot :(
[General Questions and Answers] GPSSlovakia:
Any news about how to "press VolumeUP" in fastboot ?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Shtiff1:
Has anyone been able to get adt pulse v8.0.4 working on any rooted devices?