yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Vinnipinni:
Hello!

I recently activated Online Banking for my Bankaccount. They use pushTAN with their own build app. I used xposed and SuperSU, but decided to flash a new ROM with only magisk. My current device is the Huawei P8lite with OmniROM and magisk 13.3. My device passes SafetyNET and it says certified at the Play Store. I checked magisk hide for the pushTAN app and the normal Sparkasse app. The Sparkasse app works, but it still says that my device is rooted. The pushTAN app however wont start. It says, that the app was closed and opens a website in chrome saying that my device is unsecure because I have root. I just flashed this ROM and I have no other root requiring apps installed. I've uploaded both apps to my G-Drive, so maybe someone can look and see why it still sees root. the pushTAN app is more important.

pushTAN.apk

Sparkasse.apk
[Android Q&A, Help & Troubleshooting] Vinnipinni:
Soo, I used the phone of my brother now. After getting my TAN I was able to set up the normal Sparkassen App. It works fine. But the pushTAN app still doesn't work on my device. I tried another different ROM now, but still no difference.
[Android Q&A, Help & Troubleshooting] Vinc1:
Any news on that?
[Android Q&A, Help & Troubleshooting] pOOBAH1973:
I have the exact same problem. Axon 7 here, rooted via Magisk. Magisk is set to "hide" from pushTAN app and also "hide from various detections" in settings.

pushTAN crashes and redirects to a webpage hinting that i have rooted my device.
[Android Q&A, Help & Troubleshooting] ccdesignz:
Same issue for me :/ once i run Magisk-uninstaller pushtan app works immediately
[Android Q&A, Help & Troubleshooting] JPT223:
I can approve: it works if you temporarly uninstall magisk, without? uninstalling the root patch.

Other way would be to install s-pushtan into an emulator on your PC, like this:

Download S-pushTAN on PC with MEmu

Download S-pushTAN on PC with MEmu Android Emulator. Enjoy playing on big screen. Kommen Sie auf die sichere Seite: Mit der TÜV-geprüften S-pushTAN-App holen Sie sich das praktische und sichere Freigabeverfahren Ihrer Sparkasse auf Ihr Phone oder Tablet.

www.memuplay.com

But, I would NOT trust a download that packs app and emulator into a single package. This massively increases the likelyhood of a special hack applied that spies on s-pushtan. I recommend finding any plain Android emulator then install S-pushtan from Play store. This might be more difficult, though.

Would be a joke if it really worked, since S-pushtan is all about using different devices for login and transaction authorization. This would be broken if you use an emulator on your PC. So it would make the transaction even more insecure than a rooted phone.

I'll have a look if there is an official, viable alternative to s-pushtan.
[Galaxy A3, A5, A7, A8, A9 General] deaniebaby:
G'day y'all.

I'm setting up a network of individuals from all over who are Galaxy A series owners.

The purpose of this group is to open up a public forum for all to communicate and come together in one place. Price of admission is the device right in your hands. Anyone or anybody who has any Galaxy A series, from any year, is welcome. This group is to help others find support and connections; and if a little bonding happens along the way, then so be it.

Feel free to drop on by. https://chat.whatsapp.com/CTC9xdScobi31wo3630D6U

Just a few ground rules though:

1. English will be the language of choice here (easier for many members)

2. No trash talk - all members must be respectful of each other's opinions, thoughts, and views. Failure to do so will result in being removed from the group.

3. Chat about the Galaxy A series is the basic idea of the group, but this isn't a strict rule.

4. RESPECT - can't be stressed enough. Repect each other, and we'll all get along fine.

Stick to these principles and have a great day. Happy chatting ✌
[Nexus 6 Q&A, Help & Troubleshooting] truemon.barger:
Hello all,

I have a Google Motorola Nexus 6 that has been a paperweight for a while now. I was simply listening to music with the phone charging and next thing I knew, I was staring at a blank screen with the phone "bricked". I'm not the most tech savvy guy but I have tried every key combination, checked the charging port, replaced the power strip on the inside of the phone (there was a minor tear in the previous one, thought that was the issue), and nothing has worked. I'd rather not send it in for repair since it's not my main phone anymore. I can't remember the latest update I had but was running latest Cyanogenmod. Can anyone help me?
[Verizon Samsung Galaxy S8+ Questions & Answers] Chucklez:
Okay so long story short, I have a Sprint Galaxy S8+ I preordered and outright bought (for $850) directly from Samsung in April. This last month I decided to switch with my family to Verizon. Turns out the IMEI of the phone is not recognized by the Verizon network and my phone technically works but always shows I am on roaming. Is there anyway to fix this? The phone IS unlocked I got it unlocked by Sprint, and no Samsung is not budging on helping me at all. They basically just say "Go back to Sprint the phone works fine". I was just curious if I rooted the phone and flashed a Verizon ROM onto the device will it get rid of the roaming and possibly make it able to be seen by the Verizon network? I know flashing the ROM doesnt change the IMEI but honestly Im stuck with what to do because neither, Sprint, Verizon, or Samsung is trying to help me.
[Verizon Samsung Galaxy S8+ Questions & Answers] eddyo1993:
You could try the unlocked firmware. I don't know if it would work but doesn't hurt to try
[Verizon Samsung Galaxy S8+ Questions & Answers] eric6268:
The Sprint, AT&T and T-Mobile version of s8/s8+ won't work for Verizon. Verizon's dont work for Sprint either - even you flash it with unlocked firmware. Unless you change the IMEI, but it's illegal. Both Sprint and Verizon required the IMEI in their database. That's the reason I bought unlocked version from Samsung directly. My phone shows OPEN MARKET on sprint. I just ported to Sprint from Verizon to take advantage of the 1 year free service. But I can't use the internet when I'm talking on the phone.

Don't be fooled by that word UNLOCKED, it's still a carrier branded phone.
[Verizon Samsung Galaxy S8+ Questions & Answers] KLY725:
Any luck using unlock sprint s8 plus on Verizon? I'm on the same boat but can't get it to work on Verizon.

If anyone got it to work, please advise. Thanks
[Verizon Samsung Galaxy S8+ Questions & Answers] nataskid:
Blacklisted

It won't work tell you change the imei its blacklisted and the only way around that is to change the imei sorry to break it to you.
[Android Head-Units] Roy360:
I'm thinking about installing this: https://www.amazon.ca/gp/product/B06Y5LBT2N into my 2009 Jetta TDI.

Are there any features I might be missing out on?
[Android Head-Units] ikerg:
Yes. 800x480 resolution (too low) and only 1gb ram. it seems to be an Intel sofia mtcd based unit. Avoid any android headunit with only 1gb ram like that.

I recommend a universal px5 mtcd based (2gb ram. 32gb ROM) like this

Dasaita 7" Android 6.0 Car GPS Player for 2 Din Universal with Octa Core 2GB Ram Auto Radio Multimedia GPS NAVI 4G LTE

http://s.aliexpress.com/bmmm6ZbQ

(from AliExpress Android)

Enviado desde mi D6603 mediante Tapatalk
[Android Head-Units] Roy360:
I was hoping to buy one from Amazon, so I could return it incase it's a dud.

But you might be right about the ram and resolution.

Does the unit you linked support TF card? Judging from the item description, it doesn't look like it does
[Android Head-Units] ikerg:
Normally all units have sdcard slot....but in the case it doesn't it has three USB ports or how to this

Dasaita 6.2" Android 6.0 Car GPS DVD Player for Double 2 Din Universal with Octa Core 2GB Ram Auto Radio Multimedia NAVI 4G LTE

http://s.aliexpress.com/iuuERjYF

(from AliExpress Android)

Or to his 7inch

Dasaita Android 6.0 Auto Radio Octa Core 7 Inch 2 DIN Universal Car NO DVD Player GPS Stereo Audio Head Unit Support DAB DVR OBD

http://s.aliexpress.com/QVvMJzIR

(from AliExpress Android)

Enviado desde mi D6603 mediante Tapatalk
[Android Head-Units] breezeli:
I learned the hard way that 1GB of ram just doesn't cut it. Also be careful with the unit's sizing, a lot of the chinese ones are larger and require modifications to fit right.
[Android Head-Units] Roy360:
Larger than what the item description says? Or just larger than the standard double dash format.
[Android Head-Units] breezeli:
Larger than the usual din size
[Android Head-Units] Roy360:
What do you think about this one:

https://www.amazon.ca/dp/B071JBF5MX/

2GB of ram

1024*600

A quad core ARM cpu
[Android Head-Units] ikerg:
If you want a properly commmunity supported headunit:

https://es.aliexpress.com/store/pro...885.html?spm=a219c.12010608.0.0.5208143T6jna2

Is an OctaCore Processor [2GB RAM & 32GBROM].

Same FRontal as the one you posted and same dimensions....

This is claimed as 178mm*100mm as well as the one you posted.
[Android Head-Units] Forevis:
Do you think it's the best option? Why? Is that possible to upgrade Android in the future?
[Android Head-Units] ikerg:
Afaik .... Android 7 is coming on some weeks (currently under testing)

But why that need for continuous upgrading...if Everything works as expected (even with new phones and devices)...

Enviado desde mi D6603 mediante Tapatalk
[Android Head-Units] Forevis:
I'm thinking about upgradability for the product last years. I didn't know that it could upgrade.

I saw a tread about the Ownice C500, it's have a lot of comments, do you know if it's better? https://xdaforums.com/android-auto/android-head-units/ownice-c500-released-t3478747/page145
[Android Head-Units] ikerg:
All units have their pros and cons....

What's real is that never the manufacturer/seller will get your issues solved.....the community yes.

IMHO I will get that unit with more community support

Enviado desde mi D6603 mediante Tapatalk
[Android Head-Units] Forevis:
Sorry, I'm lost. Which you think that have more community support? The Dasaita V600 ( https://m.es.aliexpress.com/s/item/...spm=a219c.12010608.0.0.5208143T6jna2#autostay ) or the Ownice 500 that have a support forum here in xda ( https://m.pt.aliexpress.com/s/item/...pm=a2g03.12010612.0.0.29bd38ccCCV5A0#autostay ).

Where is the community support for the Dasaita V600? Here in xda site?
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
So I managed to get my Nexus working by enabling only the little cores, however, I would like to try to get the big cores working.

Here's the console-ramoops I pulled from my device: https://pastebin.com/ddinyPzz

The first major error relating to the BIG cpu (that I noticed), was at lines 317 and 318 "_cpu_up: attempt to bring up CPU 4 failed"

However, the fatal error seems to occur at lines 439-451. Multiple errors about pll_clk_enable occur, here's some lines that I noticed.

Line 440: "variable_rate_pll_clk_enable: PLL a57_pll1 didn't lock after enabling for L value 0x50!"

And then at line 451: "Kernel panic - not syncing: failed to lock a57_pll1 PLL" From that point on, the kernel appears to go through the shutdown process.

For those who don't know, the cortex-a57 cores are the ones that make up the BIG cpu.

I tried to do some research on what PLL was (disclaimer, I am no expert whatsoever, so what I say may be wrong)

From what I could find, the PLL stands for phase-locked loop, and it's purpose is to control the frequencies of a CPU.

Intel has a post on possible causes for PLL losing lock: https://www.altera.com/support/support-resources/operation-and-testing/pll-and-clock-management/pll-loss-lock.html

I did some digging around in the kernel source code, and there are entries for "pll_clk_disable" in the PLL driver https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-o-preview-3/drivers/clk/qcom/clock-pll.c

So maybe this means there's a way to somehow disable PLL?

So if any Devs, or anyone with experience on this, have an idea on how to possibly fix this, please give your thoughts. This problem is a relatively prominent one in this device, and it would be awesome if we could fix it.

Here's my questions to anyone who knows more about this,

Would it be possible to disable PLL?

Is PLL hardware based, or software?

And would it be possible to somehow build a kernel to fix this problem?
[Nexus 6P Q&A, Help & Troubleshooting] Nathan-K:
Caveat: I'm a mechanical, not electrical engineer. Take this with a huge grain of salt.

Phase locked loops can't be "disabled". They are a very important, low-level aspect of modern electronics. As you point out it is useful for signal synchronization such as a CPU bus. They also have many important electronic components, the failure of any single one will result a cascade of failures. So basically, I think your logs just further suggest it is a fundamental hardware issue.

As a theoretical example (this is completely made up by the way, my own hypothetical amateur understanding): let's say a solder pad is broken on the CPU or tin whiskers formed on one of the two signals for which the PLL comparator is operating. One signal will be a nice sine wave, the other will be random noise. The comparator output will be random noise. So in this case, the "PLL lock failure" will indicate a broken solder joint.

As another theoretical example (this is completely made up, etc.): let's say the Voltage Controlled Oscillator circuit develops a non-monotinic output, which is described in the video as sometimes occurring. (I'll just say "silicon wear".) This would result in system instability at certain frequencies. Ergo, another hardware problem. (In this case, maybe downclocking the CPU would be a test? Do the Big cores operate at different frequencies at boot?)

All in all I think it's great you got it this far, and is brilliant work. Way to go. I hope (*cough*) Google considers signing a "hotfix" firmware image that implements your workaround, so that people with locked/stock bootloaders may possibly have the opportunity to fix their phones. I'll pass this on to Techno Bill, our firmware volunteer guy. He's the one who successfully argued for publishing signed Full OTA "Rescue images" way back when. I'll ping whomever I can, and keep my fingers crossed.

Here's some helpful references:

https://www.electronics-notes.com/articles/radio/pll-phase-locked-loop/tutorial-primer-basics.php

https://www.youtube.com/watch?v=A9qt0JYdvFU

TL;DR: Likely still a hardware problem. I am out of the loop (pardon the pun) on this topic, and am only a volunteer so my views are my own, etc. However I suspect Google was being honest about it from the get go.

If you have a bootlooping phone, the official line from volunteers like me is to call in and ask about Warranty Service.
[Nexus 6P Q&A, Help & Troubleshooting] robcore:
Hey man, do you have your current kernel tree online? I a) don't own the device and b) am no expert. However, I am a very resourceful kernel hacker, and working around the impossible is my specialty. Just looking at the clk driver from the same source you shared, I can see some glaring issues in online cpu refcounting. Also the logs lean closer to device tree/platform data errors than anything else. Though the following init sequences should definitely be checking for the population instead of just progressing based on trust. I would be happy to submit some patches if you have a build up :)
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
The nougat kernel source for the 6P is here, not sure if that's the same thing as a kernel tree, correct me if i'm wrong. Thanks for working on this!
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Ok that makes more sense, thanks for clearing that up. I do know that some people have said simply underclocking their big cores have worked, personally it didn't work for me, but maybe I just need to clock it lower, I'm not sure. Regardless, it shocks me how blatantly erroneous the Nexus 5X/6P devices are, and somehow, Google/Huawei/Qualcomm/LG haven't done anything to address or fix the problem, other than Google and Huawei getting into a pissing contest over who's fault it is.
[Nexus 6P Q&A, Help & Troubleshooting] robcore:
For sure, I meant moreso if you were working on a kernel personally for it :)
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
I'm thinking of working on a kernel to optimize it for using only the little cores, for now though, I'm just trying to get this fix out to as many devices as I can. Apparently Qualcomm 808/810 SOCs have tons of problems.
[Nexus 6P Q&A, Help & Troubleshooting] robcore:
If you do, please reach out to me. Judging from your logs, the big cores aren't being found during initialization, and the other errors (pll, clocks) are from assuming that the cores are already registered with the driver. Now, given that the big cores have been identified as the culprit for the loops, maybe we could work on a custom solution to delay their initialization to a later initialization stage.

While upstreaming a legacy device of mine, I had to rewrite the Qualcomm cpufreq driver in order to make it register with the cpufreq core, and it was a learning experience that would be a pity to keep to myself!
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
This sounds promising, it's weird though how devices would randomly bootloop, not even right after an update.
[Nexus 6P Q&A, Help & Troubleshooting] kronflux:
My thought would be that, being that this is clearly a hardware issue, would there be a way to track it to a specific core? Then simply disable -that- core, rather than disabling all "big cores" as they're being referred to.

I have minimal experience related to this, but that's just what's on my mind at the moment.
[Nexus 6P Q&A, Help & Troubleshooting] trax7:
The issue is hardly any specific core but rather kernel/driver related to the whole BIG cluster as specified above. I think that if there were any real production defects they would have noticed them by now.

I have a Sony Z5C, which uses the same SoC and has a similar issue but is nowhere near as severe. Our hotplugging is inefficient and the CPU readings and IRQs were botched. Until recently the only viable/stable CPU governor was interactive (even on custom kernels)...:rolleyes: Anything else gave erroneous data, locked frequencies, deteriorated performance and didn't survive a reboot (or 10 minutes of use) without defaulting back to interactive. We don't have reboots or lockups or anything but the issue's still quite similar once you think about it.
[Nexus 6P Q&A, Help & Troubleshooting] Pineapplelaw:
Is there anyway to enable one core in big cluster? If only part of the big cluster is bad, we can isolate it and use the other cores.

Booting with one core at a time we can test which one is the problem.

Maybe we could disable the core or set freq to 0? Or voltage to 0.
[Nexus 6P Q&A, Help & Troubleshooting] trax7:
Look at my last post.
[Nexus 6P Q&A, Help & Troubleshooting] robcore:
Strange? Yes. Workable? Perhaps!

Something tells me the hmp scheduling has been a largely failed experiment as well. As well, the Google/oem sources are far from perfect, and every device needs its own specific workarounds for these types of issues.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
I'm seeing this error "msm_thermal:Failed reading node=/soc/qcom,msm-thermal" and CPU-z doesn't report any temps for my device whatsoever, is this universal for 6p's? Or is it another problem with the SoC?

Edit: Also seeing this error? (not sure if it is an error) come up a lot "(name of module/driver)0 <--> 0 mV" Do you think it's possible that the BIG CPUs are somehow not getting power?
[Nexus 6P Q&A, Help & Troubleshooting] programmargorp:
[MENTION=5288606]XCnathan32[/MENTION] see . / drivers / clk / qcom / clock-cpu-8994.c

The pll lock bit is defined as BIT(31), which is the MSB of register pll->status_reg.

On the log you posted, pll->status_reg is 0xca000100 with MSB set, this suggests the pll has locked by the time that debug message has set.

Conclusion: the cpu is not giving the pll enough time to lock.

Suggested possible solution: change line 53 in clock-pll.c from #define ENABLE_WAIT_MAX_LOOPS 200 to #define ENABLE_WAIT_MAX_LOOPS 100000 to give the pll 100ms to attempt a lock.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Will try it.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
Just realized this, would I need to uncomment "#define"? Because I would think that line would be ignored when commented.
[Nexus 6P Q&A, Help & Troubleshooting] robcore:
No no this is the proper way to define things for the c preprocessor!
[Nexus 6P Q&A, Help & Troubleshooting] Vency77:
Damn, I hope I'm not offending anyone but, I feel very sad that I don't have a broken 5x/6p (and my nexus 5 does not want to die) to work on this fix.

Will follow this thread and help with whatever I can (which is limited to some C programming and a few linux kernel builds...).

Good luck and congrats for this progress.
[Nexus 6P Q&A, Help & Troubleshooting] IM0001:
I too am no dev however I am interested as my 6P just ran into this issue. One thing about PLL I have seen from OC'ing PC's is that voltage helps stabilize it and I wonder if by chance there is any way to increase it a little on the 6P? In being that it could be either the solder giving out, or by the random chance electrolysis happening in a specific area of our CPU's, but a small voltage bump could help get over the hump that our CPU's have now run into perhaps.

Just because we are increasing the PLL timeout doesn't mean the CPU will ever lock in if there is an issue deeper down. But trying all the variables is always fun at this point.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
HOLY **** DUDE!! I think you fixed it! Your a goddamn genius. It didn't boot the first time flashing it, but after checking the log, the PLL clocks registered successfully. I just forgot to build the kernel without dm-verity, so a dm-verity error is why it didn't boot this time. I'm gonna rebuild the kernel with dm-verity disabled, and try it again, but I really think you might have fixed this!
[Nexus 6P Q&A, Help & Troubleshooting] ahdoublexl:
It would be crazy if some random internet developer rather than Google or Huawei fixed this issue lol.
[Nexus 6P Q&A, Help & Troubleshooting] XCnathan32:
[MENTION=5054209]programmargorp[/MENTION] > literally Google's entire dev team

lmao
[Nexus 6P Q&A, Help & Troubleshooting] IM0001:
This may not be a complete fix because if the CPU is taking longer to get a PLL lock, it may not actually lock even with unlimited time down the road.

However if this at least gives the phone another 6months of life or something for some of us, that would be a worthy gain.

My 6P was starting to act a little funny before it did the bootloop. First WiFi was acting funny and wouldn't stay connected (seemed like it was turning off and on repeatedly on its own) and then when it finally crashed to bootloop, it was having connectivity issues to any data while I was trying to look something up on google maps. So would it continue to work even if you could get it past the PLL boot issue? Guess we will find out soon.
[Nexus 6P Q&A, Help & Troubleshooting] programmargorp:
If the pll isn't locking within a specific time it suggests a hardware fault. I'm not going to say that I permanently fixed the issue, just enough so you may be able to get a few more months out of it.

If anything, there's a big gash in the arm and I'm applying a band aid.

Either way, glad it worked!
[Nexus 6P Q&A, Help & Troubleshooting] IM0001:
Either way if you need a test device hit me up. I have an RMA coming already but while I still have my old one I am dinking around with 4 cores right now. If I can get the 8 up and working again just to fart around with a little to test your fix all the better.