en
Feedback

Don't get caught by a cheater! Telemetrio finds and tags such channels 👉 If you want to see the tag, subscribe

Real Nullptr

Real Nullptr

Open in Telegram

Nullptr's personal channel Support me: https://github.com/sponsors/Dr-TSNG TRC20:TYG2MCMcXWsko9DZkVXjX3P1Xv7dhNAarx

Show more

📈 Analytical overview of Telegram channel Real Nullptr

Channel Real Nullptr (@nullptr_dev) is an active participant. Currently, the community unites 21 587 subscribers, ranking 6 140 in the Technologies & Applications category and 10 899 in the China region.

📊 Audience metrics and dynamics

Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 21 587 subscribers.

According to the latest data from 21 November, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 382 over the last 30 days and by 7 over the last 24 hours, overall reach remains high.

  • Verification status: Not verified
  • Engagement rate (ER): The average audience engagement rate is 53.91%. Within the first 24 hours after publication, content typically collects 18.34% reactions from the total number of subscribers.
  • Post reach: On average, each post receives 11 637 views. Within the first day, a publication typically gains 3 959 views.
  • Reactions and interaction: The audience actively supports content: the average number of reactions per post is 126.

📝 Description and content policy

The author describes the resource as a platform for expressing subjective opinions:
“Nullptr's personal channel Support me: https://github.com/sponsors/Dr-TSNG TRC20:TYG2MCMcXWsko9DZkVXjX3P1Xv7dhNAarx”

Thanks to the high frequency of updates (latest data received on 22 November, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.

21 587
Subscribers
+724 hours
+917 days
+38230 days
Posts Archive
Repost from 5ec1cff
对 tango 支持的一些说明 - 该功能可在任何设备手动开启或禁用,如果设备无 tango 转译,开启后也可正常注入 32 位 app。 - 开启该功能可能会减慢开机速度。 - 除上一点外,对于无 tango 转译的设备,该功能开关与否应无差别。 - 对于使用 tango 转译的设备的用户,如果没有 32 位 app 注入需求,可以关闭该功能,这不会影响 32 位 app 的正常运行。
16 Feb 2024, 07:02

Changelog Correctly check whether tango is enabled Fix a bug causing apps to crash
15 Feb 2024, 23:11

Changelog Correctly check whether tango is enabled Fix a bug causing apps to crash
15 Feb 2024, 23:11
15 Feb 2024, ~23:11

Explanation of article 4 of copyright terms: We do not restrict on continuing development based on the previous fork, while only prohibiting claiming / implying to be the successor. This refers to the trademark, instead of the code. To be more specific, you are allowed to use such module names: "Zygisk Next Mod", "Zygisk Next Next", etc. However, you are NOT allowed to use "Zygisk Next" without any change. This is similar to Topjohnwu forbidding Magisk forks to release with the name "Magisk".
15 Feb 2024, 06:20

Changelog Copyright license change Minor bug fixes Experimental: Support Xiaomi tango translator. This function is enabled by default for supported devices (e.g. Xiaomi 14), however it will lead to some performance loss. To disable this function, write 0 to /data/adb/zygisksu/tango
15 Feb 2024, 01:52

photo content
15 Feb 2024, 01:52

之前犯了个低级错误,导致某些检测结果不显示
24 Jan 2024, 02:31

NativeTest-v21.apk5.09 MB
21 Jan 2024, 09:00

16 Jan 2024, 05:20

修复部分假阳性和闪退
13 Jan 2024, 14:00

具体更新内容:检测未卸载的 Zygisk 模块(可用 lsp 测试),强度有点高,可能存在假阳性
13 Jan 2024, 10:54

增强检测 调整 Malicious Hook 判断标准
13 Jan 2024, 10:42

Seems that someone is spreading rumors that this event is related to kisune magisk. I have to clarify: NO.
08 Jan 2024, 11:02

笑点解析:已被删评拉黑
08 Jan 2024, 09:59

photo content
08 Jan 2024, 09:59

公开两个检测 resetprop 的方法: 通过 setprop/getprop 等手段操作property 实际上是操作了位于 /dev/__property__ 下的文件。按 property 各自的 SELinux Context 存储,相同的 context 分为一组,存储在一个文件内。每个文件大小为固定的 128KB。需要使用的 prop_bt prop_info 等对象由一个线性内存分配器实现,每次分配内存时只是简单地 bump 地址,不支持释放内存。 更多细节可以查看 https://blog.canyie.top/2022/04/09/property-implementation-and-isolation/ Magisk 的 resetprop 在删除 property 时,会将 prop_bt 中指向 prop_info 的引用置空,然后清空整个 prop_info 的内存。问题就发生在这里,prop_info 的内存被清空但并没有被释放,这就导致对应内存位置出现一片很大的空区域。通过检测这里,应用可以检测到对应属性区域有属性被删除了,进而推断出设备已经 root(因为正常情况 property 是不支持删除的)。 什么时候会发生删除操作?通过 resetprop 重置 ro 也就是只读属性时。而保存着 bootloader 锁定状态的多个 property 和保存着 native bridge 的 ro.dalvik.vm.native.bridge 还有经常被修改的设备指纹都是只读属性。也就是说,除非避免修改这些属性,否则就会被检测到,而不修改 bootloader 状态的属性又会导致里面直接存着“已解锁”,应用一样可以读到。 在 https://github.com/topjohnwu/Magisk/commit/f41994cb52ca08856216a8da0a28ed148c833f4e 过后,作为副作用,上面的问题刚好被缓解,但还有另一个问题: prop_info 上有一个字段叫 serial,当这个 prop_info 被更新时,serial 会自增 2。也就是说,prop 被更新的次数 = serial / 2。而对于 ro 属性,它们是只读的,正常情况根本无法被更新,因此 serial 应该始终保持为 0。也就是说,如果发现 serial 不为 0 的只读属性,就代表它被 resetprop 过。 我们调查发现已经有应用在使用这些方法检测 root,Shamiko 1.0+ 已经尽全力隐藏了相关痕迹。我知道有很多人并不愿意使用 Shamiko,而其他隐藏方案的开发者并不知道这两个检测点,也就没有办法处理它,所以我公开了。
06 Jan 2024, 10:46

This is actually why I think open source really sucks sometimes
06 Jan 2024, 05:11

First he copied our open source code and then accused us of being thieves in turn. Then he starts accusing us of not opening source Shamiko because we are not able to behave like Jesus did to forgive all those who modified our packages for commercial use. And finally, he couldn't help but attack and spread rumors directly. I really don't want to start a war, but seems he enjoys it.
06 Jan 2024, 05:04