yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Questions & Answers] Dr-akbar:
It was already on that. Turned out to be a hardware defect and returned the phone.
[Xiaomi Poco X3 NFC Guides, News, & Discussion] pnin:
Update: Mystic R1.3 released (see https://xdaforums.com/posts/84679149).

As XDA mods/rules are now intent on censoring certain types of resources -- see the Stormbreaker topics to confirm -- we still need reliable sources for info and the corresponding files.

This thread is meant to do just that, let's see how it fares...

Mystic Kernel v4.14 for surya/karna

Repo is at https://github.com/okta-10/mystic_kernel_sdm732-4.14 (check for pointers).

Latest changelog (2021-03-04):

ToDo:

- Stormbreaker (repo at https://github.com/stormbreaker-project/kernel_xiaomi_surya)

- Void (formerly Blink, see https://xdaforums.com/posts/84695197)

- SiLonT

FYI, we already have F1xi's and Optimus Drunk here at PX3@XDA.
[Xiaomi Poco X3 NFC Guides, News, & Discussion] Revontheus:
The previous threads were shut down, not because of censorship.

Various users were reposting the kernels without obtaining the permission of the developers. Have you obtained the permission of the developer for this?
[Xiaomi Poco X3 NFC Guides, News, & Discussion] cahir1495:
Does it work with AOSP or MIUI?

Edit: Will it work with latest Xiaomu EU 11?
[Xiaomi Poco X3 NFC Guides, News, & Discussion] Alin45:
None of them works with stock A11 ROM....stucked to Poco start image.
[Xiaomi Poco X3 NFC Guides, News, & Discussion] pnin:
I'm not claiming ownership or anything. Do I need permission to post links and info? What's next, link tax? That's censorship in my book...

The developer retains the exclusive right to remove his content and/or come in here and disavow any posts he views as abusive. Tit for tat, that's how a community works, IMHO.
[Xiaomi Poco X3 NFC Guides, News, & Discussion] cahir1495:
OK, thanks
[Xiaomi Poco X3 NFC Guides, News, & Discussion] pnin:
Mystic R1.3 released 2021-03-10 (changes at https://github.com/okta-10/mystic_kernel_sdm732-4.14/releases).
[Xiaomi Poco X3 NFC Guides, News, & Discussion] SkaboXD:
Blink kernel changed it's name to Void kernel. I tried it's alpha build and maaaaaaaaaaaaaaaan! It's the smoothest kernel I ever used!

Here are JankBench results which contribute to that:

Void kernel: https://jankbenchx.now.sh/results/293603395244130824

F1xy 0.13: https://jankbenchx.now.sh/results/293083440054534664

MOD EDIT: Link Removed
[P3600 Accessories] smiles:
I’m already 2 full days surfing to identificat my GSM antenna connector on my HTC trinity/P3600. It seems there is no information around about the name….

It looks like a FME (f) or MC-Card connector…..

How knows the real name for sure?!
[Android Stick & Console AMLogic based Computers] Ludoclt:
Hello, last weekend I flashed an incompatible system on my Bqeel Y8 pro and since it doesn't turn on (8-digit display off) and I have no HDMI output, I'm desperately trying to short circuit the NAND so that my android box is recognized by my pc and thus flash the stock rom, but I can't find the pins, I put the links of the photos below, I hope someone can help me.

here are the links of the photos:
[Android Themes] themerclub:
Hi EMUI & MagicUI Users,

Download "Future Density" Theme for EMUI 9.1 / MagicUI 2 devices.​

Theme Information:

Name: Future Density

Size: 65.85 MB

Designer: The Illusionist

Comapatibility: EMUI 9.1 / MagicUI 2

Version: 9.1.1

Features:

Customization of Launcher, Dialer, Message, Settings, Clock, Calendar, Calculator, Notepad, SystemUI and many more.

Key Features:

Full EMUI 9.1 / MagicUI 2 Support, Light Wallpaper, 3D Type icons, New Lock Screen Style

Image Preview:

Video Preview:

To download this theme click the link below

Themer Club​
[Android Themes] watermelon_sugar:
LOOKS GREAT. i will update my experience after installing.
[Android Head-Units] fencer59:
HI

I have a Seicane head unit. I has been working till today. I have tried soft and hard resets. Power is flowing to the unit.

When i turn on the car ACC switch.....

1. My mazda info display reads Raise Tech

2. the unit fails to boot up

Questions

I am not sure if the issue is on the motherboard or core itself. Is there a way to asses if the core is damaged?

Is it possible to boot off a USB stick instead?

Other suggestion?

TIA
[Tilt, TyTN II, MDA Vario III General] nuspieds:
I have a Tilt 8925 and I recently upgraded to WM 6.1. Now I'm unable to set MEdia Net to "Always On".

When I was on WM 6.0, I used KaiserTweak to do it and it worked perfectly, no problem. But since WM 6.1, after I soft-reset, the setting reverts back to "Enabled."

I even tried ACT, and I get the same result after I soft-reset.

As a test, I tried to set the AT&T ISP GPRS connection to "Always On" and that worked. It's only the MEdia Net one that doesn't work.

Does anyone know where in the registry and I edit directly to set MEdia Net to "Always On"?

Thanks!
[Tilt, TyTN II, MDA Vario III General] golfer_boy:
HKLM\Comm\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Media Net

Set Alwayson to 1

You don't really need to do a soft reset.
[Tilt, TyTN II, MDA Vario III General] nuspieds:
Hey, thanks for registry info.

Well, I tried it, set it "1" and as a test, I did a soft-reset. I went back into the registry and the value was back to "0"! :mad:

I know you said I don't have to soft-reset, but the purpose of me doing that is to ensure that the setting lasts when I turn off/restart my phone.

There's something that's definitely setting that value back to "0" when the phone starts up. If I can find a way with some sort of start-up script that will set that value in the registry, then that would work. I'm thinking like how in Windows you can export to a *.reg file and double-clicking on the .reg file imports the entry into the registry. Something like that.
[Tilt, TyTN II, MDA Vario III General] nuspieds:
I solved the problem by using Dotfred's Task Manager (which includes a Registry Editor).

First, I exported the MEdia Net key to a .reg file and then I created a shortcut to the Task Manager and placed the shortcut in my startup folder.

The great thing about Dotfred's Task Manager is that it has lots of command-line switches, including a "silent" mode so that it can load the .reg file without any popups whatsoever.
[Tilt, TyTN II, MDA Vario III General] golfer_boy:
You're welcome.

Sometimes the soft reset immediately after making a registry change is too soon, as in you did the soft reset before the change was saved.

Dotfred's task manager is good and I'm glad it helped you.
[Tilt, TyTN II, MDA Vario III General] rosado1013:
Can You tell how to do this ? I have try Dotfred's Task Manager, but dont kow how use it, also whit the reg of this program I coul set always on to 1 but Medianet keep geating off some times
[Tilt, TyTN II, MDA Vario III General] nuspieds:
This is no longer working for me, ever since I started to receive the "Network Logon" screen at boot-up.

I don't get any errors at startup, but it's just that now when I check the registry, the setting is still set to disabled (0), even though my registry has it set to enabled (1).

However, I am also no longer experiencing any internet disconnect issues.

But if you want to know how I originally did what I did, here are the steps:

Start Dotfred Task Manager Registry Editor;

Navigate to the MEdia Net entry (see previous post by golfer_boy) for the path;

Set/ensure the AlwaysOn setting is enabled;

Export the MEdia Net entry (tap and hold, then select "Export") to your storage card somewhere;

Launch File Explorer;

Navigate to where you exported your MEdia Net registry data file;

Tap and hold the file and then select "Copy";

Navigate to \Windows\Startup;

Tap and hold and select "Paste Shortcut";

Use a text editor to edit the above shortcut .lnk file. In my case, I connect my phone to my PC, then copy the file over to a temp directory on my PC, and use Notepad to edit it;

Edit the file such that the path to Dotfred's Task Manager prefixes your MEdia Net registry file and that the syntax is correct. See the instructions at http://msdn.microsoft.com/en-us/library/ms861519.aspx for the correct syntax;

Note 1: When you edit the .lnk file, make sure that ONLY the entire path to the Task Manager (Registry Editor) is in quotes. The path to your MEdia Net registry file and other parameters must NOT be in quotes.

Note 2: Make sure that you have configured your Dotfred Task Manager to start as the Registry editor by default.

Note 3: Include the Dotfred's Task Manager "/silent" parameter so that it loads the registry file automatically, without prompting you.

Example: 80#"\Program Files\FdcSoft\TaskMgr\TaskMgr.exe" \Storage Card\MEdia Net.reg /silent

Save/copy your file into the \Windows\Startup folder on your phone;

Reboot to make sure it works.

Good luck!
[Tilt, TyTN II, MDA Vario III General] fsb2cool2care:
An easier way.

Nuspieds, you are right on the money up until step #10.

But once you've exported your desired registry value to a .reg file here's what you should do. (You will need Ghisler's Total Commander)

10. Using Total Commander, tap and hold your .reg file and select "Properties". Then select the "Associate" tab in the window that opens.

11. Tap the gray box that says "Associate..."

12. In the "Command:" box, reference the location of TaskMgr.exe (ex. \Program Files\FdcSoft\TaskMgr\TaskMgr.exe)

13. In the "Parameter:" box, leave the "%1" and add "/silent" (%1/silent)

That's all you need! Enjoy!
[Sony Cross-Device General] Fenix46:
Hi, I'm work on port k3.10 for nexus 5, but still won't boot... I will ask you, if I can use this base, and I wanted to know, if to boot, do build rom+kernel
[Sony Cross-Device General] threader:
I've not looked at this for a while, I'm a bit perplexed as to where the problem lies, I have some ideas i would like to try soom but I can't quite understand why devices do not initializing, it's not a very obvious fault, I've not tried it for 8974, yet, i've worked with 8994, but this will not work with nexus 4, you would need a 3.10 kernel from google then merge the difference and pray, as far as i can tell only 3.4 kernels are available.
[Sony Cross-Device General] threader:
Commit 505510e59c86ff283a2eb743f679debc6698d1ed 'clocksource: arch_timer: make virtual counter access configurable' and a problem with arch/arm64/include/hw_breakpoints.h were the reason behind the issues.

The logs tell of some problems, and i don't like a few of the compiler warnings.

----
[ 10.541250] msm8994-asoc-snd fe034000.sound: msm8994_asoc_machine_probe: hdmi audio support present
[ 10.542886] msm8994-asoc-snd fe034000.sound: ASoC: CODEC tomtom_codec not registered
[ 10.542953] platform fe034000.sound: Driver msm8994-asoc-snd requests probe deferral
[ 10.144994] ALSA device list:
[ 10.144995] No soundcards found.
[Sony Cross-Device General] threader:
Very interesting https://source.codeaurora.org/quic/la/kernel/msm-3.10/log/?h=LA.BR.1.3.7.c26 - I spent some time on the arm32 end of LA.BR.1.3.7.c25 today, as aarch64 worked to an extent on the device and seemed quite happy in qemu I wouldn't not have thought 32bit at least to some degree shouldn't , that degree being qemu and the ranchu_defconfig. But the fact that c26 is out here is quite motivating.

2021-10-13	Merge "msm: adsprpc: allocated all remote memory in kernel"	Linux Build Service Account	3	-67/+347
2021-10-12	Merge "asoc : msm: Fix zero size pointer issue"	Linux Build Service Account	1	-0/+6
2021-10-12	asoc : msm: Fix zero size pointer issue	Soumya Managoli	1	-0/+6
[Sony Cross-Device General] threader:
https://github.com/threader/kernel/tree/xperiadev/aosp/LA.BR.1.3.7.c26 is alive on ARM64 but ARM32 does not output anything in qemu, and doesn't get further then the logo on the device(which is an improvement).
[Sony Cross-Device General] threader:
So this is the status of ARM32:

(gdb) stepi
restart () at arch/arm/boot/compressed/head.S:371
371 bl __hyp_set_vectors
=> 0x40010138 <restart+136>: 28 00 8f e2 add r0, pc, #40 ; 0x28
(gdb) stepi
375 sub r9, r6, r5 @ size to copy
=> 0x4001013c <restart+140>: b8 00 90 e8 ldm r0, {r3, r4, r5, r7}
(gdb) stepi
376 add r9, r9, #31 @ rounded up to a multiple
=> 0x40010140 <restart+144>: 03 30 40 e0 sub r3, r0, r3
(gdb) stepi
377 bic r9, r9, #31 @ ... of 32 bytes
=> 0x40010144 <restart+148>: 03 40 84 e0 add r4, r4, r3
(gdb) stepi
378 add r6, r9, r5
=> 0x40010148 <restart+152>: 03 50 85 e0 add r5, r5, r3
(gdb) stepi
379 add r9, r9, r10
=> 0x4001014c <restart+156>: 03 70 87 e0 add r7, r7, r3
(gdb) stepi
381 1: ldmdb r6!, {r0 - r3, r10 - r12, lr}
=> 0x40010150 <restart+160>: 00 80 87 e5 str r8, [r7]
(gdb) stepi
382 cmp r6, r5
=> 0x40010154 <restart+164>: 23 6c a0 e1 lsr r6, r3, #24
(gdb) stepi
383 stmdb r9!, {r0 - r3, r10 - r12, lr}
=> 0x40010158 <restart+168>: 06 0c 33 e1 teq r3, r6, lsl #24
(gdb) stepi
384 bhi 1b
=> 0x4001015c <restart+172>: 70 b9 0e 1a bne 0x403be724
(gdb) stepi
0x403be724 in ?? ()
=> 0x403be724: 00 00 a0 e1 nop ; (mov r0, r0)
(gdb) stepi
0x403be728 in ?? ()
=> 0x403be728: fd ff ff ea b 0x403be724
(gdb)

/* Relocate the hyp vector base if necessary */
#ifdef CONFIG_ARM_VIRT_EXT
mrs r0, spsr
and r0, r0, #MODE_MASK
cmp r0, #HYP_MODE
bne 1f

bl __hyp_get_vectors
sub r0, r0, r5
add r0, r0, r10
bl __hyp_set_vectors
1:
#endif

sub r9, r6, r5 @ size to copy
add r9, r9, #31 @ rounded up to a multiple
bic r9, r9, #31 @ ... of 32 bytes
add r6, r9, r5
add r9, r9, r10

1: ldmdb r6!, {r0 - r3, r10 - r12, lr}
cmp r6, r5
stmdb r9!, {r0 - r3, r10 - r12, lr}
bhi 1b

/* Preserve offset to relocated code. */
sub r6, r9, r6
[Sony Cross-Device General] threader:
Placeholder until recovered from injury
[Sony Cross-Device General] mirhl:
Why aren't you participating to the other mainline trees?

postmarketOS / linux-postmarketos-archive · GitLab

Archive of the issues in linux-postmarketos.git

gitlab.com

Qualcomm Snapdragon 820 Mainline / linux · GitLab

Staging area for Device Tree support and drivers for various Qualcomm Snapdragon 820/821 mobile devices

gitlab.com

GitHub - SoMainline/linux: Linux kernel source tree

Linux kernel source tree. Contribute to SoMainline/linux development by creating an account on GitHub.

github.com
[Sony Cross-Device General] threader:
I read about somainline but last I checked it had little activity, I might have been abit quick there though, reading and poking a bit about. Very much interesting, thank you for the heads up.
[Sony Cross-Device General] threader:
Ok, so I'm taking a look at SoMainline atm, and gathering some info, I remember Rob Clark in regards to the Freedreno project did a panel driver for the Sony Z3 (https://patchwork.kernel.org/projec...2-20162-1-git-send-email-robdclark@gmail.com/) - Started reading the documentation and found this gem (https://github.com/freedreno/freedreno/wiki/DSI-Panel-Driver-Porting) mentioning this gem https://github.com/msm8916-mainline/linux-mdss-dsi-panel-driver-generator .
[Sony Cross-Device General] IGor2Orel:
hey! how's it going? i haven't seen any work done in a while...
[Sony Cross-Device General] threader:
Hey, thanks for asking, I've had to recover from all sorts of ****, got Covid around february 2022, i was in a good flow, but alas, it took it's toll and my lungs were wrecked after, took at least 6 months before i didn't need a break or two going to the store to buy stuff.

I worked on an old huawei kernel trying to pull of a similar thing i did in 2011 or so where i stuffed the drivers in a mainline kernel and such, just doing so with the knowledge i have now, i worked for a month flat out on that until migraines and tinnitus beat the **** out of me, turns out i have a chronic sinus infection which leads to tinnitus, I've gotten some nasal-spray for that and the condition is improving. I'm slowly getting into a flow again, but i wont dare work 24h+ again and let it become too much of an obsession to get **** working as earlier, the body is complaining in all sorts of ways, i had to let everything go for months after the Huawei stuff.

I got recovery booting on the MSM .c25 kernel here though, i got stuck on getting arm32 working, now I've got a similar problem with the Huawei kernel where i need to debug an early boot problem and boot in qemu to get any useful output, I'm hunting for my notes at the time and cursing myself for not posting everything in this forum so i could just go back and copy paste. I know, i think that CAF now Code Linaro has a new branch of this MSM kernel I could try to merge and see if arm32 boots, It stumps me that aarch64 worked, this was supposed to be a continuation of Sony's efforts to unify the kernel having the Z1 and z5 in the same place, I also got sidetracked with https://github.com/SoMainline , and a merge with of a Copyleft kernel to a Z3+, z4 and Z5 kernel, i guess too many balls in the air? I'll see in the coming weeks if i can manage to get around to merging newer branches and see if this work properly, or even boot los 14.1/15 which requires more diligence than just a recovery. As far as i could tell or remember audio wasn't initializing properly though, for reasons unknown, I know of a patch which i applied that fixed audio for the said Copyleft kernel, but that didn't seem to work reading the 'dmesg'. Question is though, is it worth the effort or should i focus on So-mainline, or both,I got to the point of having a generated display driver and was trying to figure out the regulator stuff on So-mainline before Covid screwed me hard. . . I'll get around to trying again, it's just taken me forever, and the years are flying these days, I could use a helping hand.

Cheers.
[Sony Cross-Device General] IGor2Orel:
by the time you answered i already managed to sell the thing... can't help much at this point, my knowledge is near 0 too
[Sony Cross-Device General] threader:
hehe, that makes sense knowing now all the nasty bugs that lurk everywhere in firmware and TZ and such, I can't recommend using old phones for anything serious. I got another z5 to play with but also bought a new phone last year, I'm discovering some rather annoying bugs in this kernel, I don't remember it being this way, or stubborn, i always tested with 'fastboot boot recovery.img' and it worked, now it work's the first time and fail to boot itself if i flash recovery to boot and select reboot, or 'fastboot boot recovery.img' twice without a full power circle. Same goes for getting into TWRP recovery to get the logs, TWRP sometimes fails to boot, i think it's left over NVRAM variables from the previous kernel. ugh. At least i got all the way back around to this in 1.4 years ?
[Magisk] VD171:
Firstly, thank you very much, @topjohnwu

It's just a suggestion.

Why not a way to enable/disable Hide Magisk to all package processes?

Today, if I want to use the CLI, I have to dump the APK, collect all the package processes, and then enable/disable the magisk hide for each by one.

It would be very good if I could replace the name of the process by an asterisk to represent "all processes", like:

magiskhide add name.of.package *
magiskhide rm name.of.package *

And then enable/disable magisk hide for all processes of name.of.package 🤩 :love:
[Magisk] Didgeridoohan:
If you really want John's attention, a Github pull request would be the best way to go about that...
[Magisk] VD171:
I created my account on github.

Thank you for suggestion.

I'm sorry for my newbie question: do I have to write the code of my proposal or can I just write a suggestion like I did here?
[Magisk] Didgeridoohan:
The optimal would be a pull request, but if you can't make one an issue ticket with the described proposal would be the second best thing.
[Magisk] VD171:
Thank you very much, my friend.

I created my account: https://github.com/VD171

and I created the issue: https://github.com/topjohnwu/Magisk/issues/4019

Hope it can help other people too.
[Magisk] VD171:
LOL.

The issue was closed with the tag "wontfix".

And somebody replied with a recommendation that does NOT work.

That can be solved with just some lines of code.

Apparentely that is not an interessting thing for the public !

This is a very strange attitude for developers from an open source tool.

No matter, I will keep dumping the APK using aapt, as I always did:

Android aapt - eLinux.org

elinux.org

Thank you very much for attention, @Didgeridoohan
[Magisk] VD171:
Exaclty that. Sad...

[Suggestion] Enable/Disable Magisk Hide to all proccesses of the package using CLI · Issue #4019 · topjohnwu/Magisk

Android Version: 10 QP1A.190711.020 Magisk Version Code: 22004 (This issue was posted to XDA-Developers: https://forum.xda-developers.com/t/suggestion-enable-disable-magisk-hide-to-all-proccesses-o...

github.com
[Magisk] 73sydney:
Blinking was killed off in html code for a reason, a long time ago now.....

Unmistakeable hint: Change the gif, no one wants to see that or anything animated when theyre trying to read a thread, please, and thank you
[Magisk] VD171:
Really, really (and really) off-topic.

That's callled as gif, my friend.

The first gif released was at 1987.

I don't like coca-cola too, but I see it everywhere.

View attachment 5248833
[Magisk] 73sydney:
There are limits on suignatures to try and stop people posting annoying matter because it ruins the readability of the forums....

Please think of others and knock the gifs off please :)
[Magisk] VD171:
The gif on my signature keeps hide and you need to "toggle signature" to see that.

But, I will think about that.

View attachment 5248859
[Magisk] 73sydney:
not hidden, still blinding people
[General Questions and Answers] zion44:
Hi people.. Im Zion I have a big problem hope our comunity help me!!

I need able an autoclicker on my box android but when the app need accessibility on service. there isn't no section to tap!! HELP ME PLEASE!!
[XPERIA X1 General] ipporek:
Think there are a lot of people out there who have been considering between the 2, and with Touch Pro out (it just released over the weekend here in Singapore) and X1 still yet to have a 100% confirmed released date (still wondering if October's a confirmed date, and even then, whether as the case of Touch Pro, it'd be released even later here), a lot of people have been getting the Touch Pro instead. I myself am really tempted to do so too, but there's still that little bit that's holding me back to get the X1. Thing is there's so many points about the Touch Pro that seemingly give it an edge over the X1.

X1:

* WVGA (this a pro or a con?)

* Larger screen (but 'non standard' screen size that might cause some apps to not work)

* 4 row and supposedly crappier keypad (though good in that the keys are more spaced out)

* 3.5mm audio jack (which doesn't matter to me)

* Better video playback (or am I wrong)

* Slightly thinner and lighter

* Higher capacity battery (1500 vs 1340 mAh for Touch Pro)

* Metal casing

* Possibility of SE splitting (meaning loss in support?)

Touch Pro

* VGA

* 'Standard' screen size that 3rd party apps are built for

* 5 row and supposedly better keypad

* TV out (doesn't quite matter to me either)

* Accelerometer (till now no confirmation whether X1 has)

* Higher RAM (288 vs 256MB in X1)

* Slightly smaller

* Plastic casing

* Larger support community (whether X1 will have one remains to be seen)

GSMArena Comparison

Smape Comparison

Correct me if I've got any point wrong. Lookswise I used to think the X1 looked better, but until lately was starting to feel it looked worse and worse, though most recent videos kinda made me change my mind again (ya... I am just so fickle-minded)

Anyway, what do you all think? Don't wish to be getting the Touch Pro and regret not waiting for the X1 to be out to do an actual comparison. Or is there anyone who has tried both (probably test set of X1) and able to comment on points like the keypad and running of 3rd party apps?

Btw, reason I'm posting this here rather than in other forums that I visit is cos there seem to be more people here with test units and so was hoping to get more opinions here.