Giter Club home page Giter Club logo

nullgram's Introduction

Nullgram

Telegram CI build Crowdin

中文 日本語

Nullgram is an free and open source third-party Telegram client, based on the official source code for Telegram App for Android.

Why Nullgram

Due to the fragmentation of the NekoX and Nekogram communities, and the serious problems with the main developers of NekoX and Nekogram1, I decided to make Nullgram to integrate both of their functions to avoid these problems.

Null used in computer programming for an uninitialized, undefined, empty, or meaningless value. In the name of Nullgram, the purpose is to express that there is no such bad things. Nullgram won't push FCM-Notification "nmsl"2 or somethings like that to your phone, won't send ads3 to channels, won't compete maliciously4 or publish malicious rumors about competitors

How to Contribute

I want to add new feature

Great!

Make sure you fully understand the Development Document. If you haven't read it.THEN GO READ IT.

Then just create a new pull request and I should be review in a couple of days.

I've encountered a bug!

First, make sure you have the latest version installed (check the channel, Play store versions usually have a delay).

Then, if the issue appears in the official Telegram client too, please submit it to the officials, (be careful not to show Nullgram in the description and screenshots, the official developers doesn't like us!).

Then, please detail your issue (ENGLISH ONLY), create an issue or submit it to our group with #bug.

Make sure using the issue template and writing the detailed version number I DO NOT KNOW WTF IS I HAVE BEEN USING THE LATEST VERSION

If you experience a crash, you can use logcat to catch the log (TAG: Nullgram ).

Compilation Guide

You will require Android NDK rev. 21 and Android SDK 14

  1. Download the Telegram source code from https://github.com/qwq233/Nullgram
  2. Download the ccache from here and make sure it is in your PATH.
  3. Replace release.keystore in TMessagesProj/config with your own one.
  4. Fill out RELEASE_KEY_PASSWORD, RELEASE_KEY_ALIAS, RELEASE_STORE_PASSWORD in gradle.properties to access your release.keystore
  5. Go to https://console.firebase.google.com/, create one android app with application ID top.qwq2333.nullgram, turn on firebase messaging and download google-services.json, which should be copied to the same folder as TMessagesProj.
  6. Open your terminal and run ./gradlew assembleRelease to build the APK

Sponsor

Thanks to Jetbrains for allocating free open-source licences for IDEs and CloudFlare for OSS sponsorship

Footnotes

  1. https://telegra.ph/%E6%9C%89%E5%85%B3-Nekogram-Lite-%E7%9A%84%E6%95%85%E4%BA%8B-04-09 ↩

  2. https://sm.ms/image/FAKi3mx6XwqlvRj ↩

  3. https://t.me/zuragram/392 ↩

  4. https://t.me/sayingArchive/15428 ↩

nullgram's People

Contributors

abcdeiko avatar acran avatar alabiaga avatar cinit avatar dependabot[bot] avatar dkaraush avatar drklo avatar github-actions[bot] avatar henvy-mango avatar janka102 avatar jsonchi avatar keta1 avatar kyeongmincho avatar kyuubiran avatar mastergroosha avatar megapro17 avatar nextalone avatar qwq233 avatar reindex-ot avatar ruival avatar sakarie9 avatar slp avatar spagy avatar steve-mr avatar tehcneko avatar trellixvulnteam avatar wuhang2003 avatar xaxtix avatar yorlov avatar zhukov avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar

Forkers

akbarazimifar ets-android5 kyuubiran jplie teaqariawtf trellixvulnteam yuzhizn wuhang2003 awolfafterdark amirulandalib th3-r3p4ck3r steve-mr sakarie9 wynneia p3r5t7u9 zhangjiajun1123 boyxil onion99 ashim-anwar cinit rushizgithub wznpp1 satyamisme 15601560 rj9676564 telvideo lovedolove-forked-projects nextalone young-lord zhnathaniellee megapro17 captswing xiao-limiao temoa synkrosky gitbuzka cdlongbow reindex-ot keeperorowner lovewander

nullgram's Issues

[功能请求] 希望可以增加当用户聊天接收新消息时，过滤某些敏感词(骂人赌博等)消息的功能。

Why do you think you need this feature

在某些用户私聊时会有一些广告、赌博、色情或骂人的词语等，希望可以过滤(不显示)用户发来的包含敏感词的消息，减少部分私聊用户的*扰等。

Describe the solution you'd like

在某些用户私聊时会有一些广告、赌博、色情或骂人的词语等，希望可以过滤(不显示)用户发来的包含敏感词的消息，减少部分私聊用户的*扰等。

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

Online status of a user

Why do you think you need this feature

This feature is important as we don't need to check user profile again again if he/she is online or not.

Describe the solution you'd like

IMG_20230910_132039

IMG_20230910_131749

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[feature] 增加隐藏"全部对话"

Why do you think you need this feature

这很有用，可以使界面整洁

Describe the solution you'd like

就像 nekogram, nekoX 一样

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[feature] Persistence of Blocked User List

Why do you think you need this feature

Currently, blocked user list seems to be kept in the memory of Nullgram but not persisted. When the background process of Nullgram stopped, the blocked list is lost and not rebuilt on a per-user basis until I click into the profile page of a blocked user again (after the Nullgram reconfirms with the server the user is blocked).

The lost of blocked user list undermined the usability of features depending on it, e. g. ignore messages from blocked users. After a certain time of inactivity (for example, one night on my Android phone), the blocked list is forgotten and the blocked user will reappear in the chat log again. I am forced to find a message of the blocked user and click into their profile to reestablish the ignorance again.

Persistence of blocked user list would fix this issue and improve the user experience.

Describe the solution you'd like

As background process of Nullgram liveness changes much more frequently than the blocked list in most use case scenarios, I would suggest create a persistent cache of blocked user list locally. Nullgram can use the cache to populate the blocked user list so that the user no longer need to rebuild the list manually.

If the user unblocked a user remotely, the user can manually flush the cache, or click into the user profile (only) once, so that the cached blocked list can be overwritten.

Describe alternatives you've considered

Periodic automatic poll of the blocked status of previously blocked uses is a better solution. But this requires a persistent list of polling target as well.

Is your feature request related to a problem

The ignoring user feature is not stable right now, as described in the previous sections.

[Bug] 当打开特定 Telegraph 文章的即时预览并加载图片时出现闪退

Steps to reproduce

  1. 打开并登录 Nullgram 客户端
  2. 打开 https://telegra.ph/**GDP有望2035年超美-04-01 的即时预览

Expected behaviour

正常显示即时预览并加载图片

Actual behaviour

Nullgram 闪退

Smartphone Information

  • Device: Xiaomi 13 Ultra (2304FPN6DC)
  • OS: Xiaomi HyperOS
  • Version: V1.0.24.3.25.DEV on Android 14

Nullgram Version

Nullgram v10.9.1-dcb3a2e (1645201463) arm64 基于 Telegram 10.9.1 (4464)

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

log-2024-04-01 (2).txt

Bottom Tabs (Folders)

Why do you think you need this feature

Ease on the hand and on fingers for phones larger than 6.1 inches.

Describe the solution you'd like

I would very much appreciate if the tabs could be moved towards the bottom of the screen as I am a heavy user of the telegram app especially when laying down, most of the time, the phone's balance is lost when trying to reach the tabs which I almost habitually reach for.

Describe alternatives you've considered

Not all phones support the "accessibility" or reach feature which is found on iOS or apps like Kiwi Browser for android.

Is your feature request related to a problem

I mean, no one wants to drop there phone when they are using it while laying down!

[Bug] Unable to open chat page

Steps to reproduce

none

Expected behaviour

proper functioning

Actual behaviour

Open any dialog page and it flashes back

Smartphone Information

SDK: 33
PRODUCT_NAME: meizu_17_N_CN
BOARD_NAME: kona
SUPPORTED_ABIS: arm64-v8a, armeabi-v7a, armeabi

Nullgram Version

v10.2.0-preview-e8f8804(1645201316) arm64

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

crash-top-qwq2333-nullgram-03-11_03-01-57.zip

對於下載的提議

Why do you think you need this feature

現在的 電報 並未對大體積的檔案做出限制，遇到這樣的檔案需要下載很長時間

Describe the solution you'd like

下載加速或是解除對下載的相關限制

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[功能请求] Raised forward/delete limits to 1024 +commit

Why do you think you need this feature

NextAlone/Nagram@f2b7959

Describe the solution you'd like

forward work natively while delete is not. Thats why delete have a "slicer" for a list with the ids.
For folks who ask: "WTF your map value contain list of the lists" well, key can be zero (0), but it in theory can contain the ids (here they check if (newTaskId != 0)) so to avoid rewriting values in this map we just add new chunks with ids.
If they will restrict native forward in future i will add same slicer too. Limit 1024 just to have it. It can be upto 2 billions, but after your client need to send all these chunks (=requests) and you can get api bans (for 5-10min due use abuse their api).
So, when you wanna forward 800 messages OR delete them think that TG servers control your API rates for certain api calls.

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[Bug] 代理列表出现无法删除的【:-1】代理，出现多个时可引发fc

Steps to reproduce

1：全新安装Nullgram
2：登入账户后随意新建或添加任意代理后保存
3：杀掉Nullgram进程
4：再次启动时，代理列表出现一个【:-1】代理，ip地址空，端口号为1，尝试删除后重启Nullgram，该bug代理再次出现。
5：使用一段时间后（也可能是升级Nullgram版本后），列表内出现多个【:-1】代理，
此时代理界面尝试长按多选、删除任意代理条目都会引发崩溃，只能清除应用数据解决。
QQ图片20230423184837
Screenshot_2023-04-23-18-50-06-394_top qwq2333 nullgram-edit jpg

Expected behaviour

代理列表不会出现异常条目，不会引发崩溃。

Actual behaviour

出现了显示为【:-1】的异常代理条目，删除后重启再次出现，多个同时出现时则会引发崩溃。

Smartphone Information

Device: Xiaomi 13
OS: Android 13

Nullgram Version

v9.6.0-66b0ca3

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

--------- beginning of main
04-23 18:28:32.889 19876 19876 D Nullgram: module path -> /data/app/~~3wIAncRrYSXB1kmULIgSSg==/top.qwq2333.nullgram-lB3HhqMocqTwqAlthd_gYQ==/base.apk
04-23 18:28:33.247 19876 19876 D Nullgram: checkSignature: Match Github Signature
04-23 18:28:33.249 19876 19876 E Nullgram: density = 2.75 display size = 1080 2296 413.755x413.849, screen layout: 268435810, statusbar height: 104, navbar height: 44
04-23 18:28:33.347 19876 20039 I Nullgram: emoticon column count = 1
04-23 18:28:33.360 19876 20047 I Nullgram: emoticon column count = 1
04-23 18:28:33.377 19876 20054 I Nullgram: emoticon column count = 1
04-23 18:28:33.395 19876 20060 I Nullgram: emoticon column count = 1
04-23 18:28:33.408 19876 20068 I Nullgram: emoticon column count = 1
04-23 18:28:33.419 19876 20074 I Nullgram: emoticon column count = 1
04-23 18:28:33.471 19876 19876 E Nullgram: density = 2.75 display size = 1080 2296 413.755x413.849, screen layout: 268435810, statusbar height: 104, navbar height: 44
04-23 18:28:33.528 19876 19876 E Nullgram: read string error
04-23 18:28:33.529 19876 19876 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:28:33.529 19876 19876 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:28:33.529 19876 19876 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:105)
04-23 18:28:33.529 19876 19876 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:28:33.529 19876 19876 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:28:33.529 19876 19876 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:28:33.529 19876 19876 E Nullgram: read string error
04-23 18:28:33.529 19876 19876 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:28:33.529 19876 19876 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:28:33.529 19876 19876 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:113)
04-23 18:28:33.529 19876 19876 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:28:33.529 19876 19876 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:28:33.529 19876 19876 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:28:33.529 19876 19876 E Nullgram: read string error
04-23 18:28:33.529 19876 19876 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:28:33.529 19876 19876 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:28:33.529 19876 19876 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:117)
04-23 18:28:33.529 19876 19876 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:28:33.529 19876 19876 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:28:33.529 19876 19876 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:28:33.529 19876 19876 E Nullgram: read string error
04-23 18:28:33.529 19876 19876 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:28:33.529 19876 19876 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:28:33.529 19876 19876 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:121)
04-23 18:28:33.529 19876 19876 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:28:33.529 19876 19876 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:28:33.529 19876 19876 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:28:33.529 19876 19876 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:28:33.529 19876 19876 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:28:33.529 19876 19876 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:28:33.983 19876 20029 I Nullgram: emoticon column count = 1
04-23 18:28:34.674 19876 19876 I Nullgram: useragent: Dalvik/2.1.0 (Linux; U; Android 13; 2211133C Build/TKQ1.220905.001) Nekogram/9.5.8 (3252; 381d52f35f552e10ad1701445dba9cd14acb7e43)
04-23 18:28:35.349 19876 20025 I Nullgram: emoticon column count = 1
04-23 18:28:40.606 19876 20236 E Nullgram: java.net.SocketTimeoutException: failed to connect to dns.google/8.8.8.8 (port 443) from /192.168.2.52 (port 41786) after 1000ms
04-23 18:28:40.606 19876 20236 E Nullgram:      at libcore.io.IoBridge.connectErrno(IoBridge.java:235)
04-23 18:28:40.606 19876 20236 E Nullgram:      at libcore.io.IoBridge.connect(IoBridge.java:179)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.net.Socket.connect(Socket.java:646)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.Platform.connectSocket(Platform.java:182)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:145)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:131)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:90)
04-23 18:28:40.606 19876 20236 E Nullgram:      at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:30)
04-23 18:28:40.606 19876 20236 E Nullgram:      at PZ.doInBackground(ConnectionsManager.java:58)
04-23 18:28:40.606 19876 20236 E Nullgram:      at android.os.AsyncTask$3.call(AsyncTask.java:394)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.util.concurrent.FutureTask.run(FutureTask.java:264)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
04-23 18:28:40.606 19876 20236 E Nullgram:      at java.lang.Thread.run(Thread.java:1012)
04-23 18:30:51.174 29617 29617 D Nullgram: module path -> /data/app/~~3wIAncRrYSXB1kmULIgSSg==/top.qwq2333.nullgram-lB3HhqMocqTwqAlthd_gYQ==/base.apk
04-23 18:30:51.546 29617 29617 D Nullgram: checkSignature: Match Github Signature
04-23 18:30:51.548 29617 29617 E Nullgram: density = 2.75 display size = 1080 2296 413.755x413.849, screen layout: 268435810, statusbar height: 104, navbar height: 44
04-23 18:30:51.618 29617 29729 I Nullgram: emoticon column count = 1
04-23 18:30:51.624 29617 29738 I Nullgram: emoticon column count = 1
04-23 18:30:51.636 29617 29746 I Nullgram: emoticon column count = 1
04-23 18:30:51.648 29617 29752 I Nullgram: emoticon column count = 1
04-23 18:30:51.671 29617 29759 I Nullgram: emoticon column count = 1
04-23 18:30:51.678 29617 29765 I Nullgram: emoticon column count = 1
04-23 18:30:51.711 29617 29617 E Nullgram: density = 2.75 display size = 1080 2296 413.755x413.849, screen layout: 268435810, statusbar height: 104, navbar height: 44
04-23 18:30:51.768 29617 29617 E Nullgram: read string error
04-23 18:30:51.768 29617 29617 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:30:51.768 29617 29617 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:30:51.768 29617 29617 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:105)
04-23 18:30:51.768 29617 29617 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:30:51.768 29617 29617 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:30:51.768 29617 29617 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:30:51.768 29617 29617 E Nullgram: read string error
04-23 18:30:51.768 29617 29617 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:30:51.768 29617 29617 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:30:51.768 29617 29617 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:113)
04-23 18:30:51.768 29617 29617 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:30:51.768 29617 29617 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:30:51.768 29617 29617 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:30:51.768 29617 29617 E Nullgram: read string error
04-23 18:30:51.768 29617 29617 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:30:51.768 29617 29617 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:30:51.768 29617 29617 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:117)
04-23 18:30:51.768 29617 29617 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:30:51.768 29617 29617 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:30:51.768 29617 29617 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:30:51.768 29617 29617 E Nullgram: read string error
04-23 18:30:51.768 29617 29617 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:30:51.768 29617 29617 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:30:51.768 29617 29617 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:121)
04-23 18:30:51.768 29617 29617 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:30:51.768 29617 29617 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:30:51.768 29617 29617 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:30:51.768 29617 29617 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:30:51.768 29617 29617 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:30:51.768 29617 29617 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:30:52.251 29617 29721 I Nullgram: emoticon column count = 1
04-23 18:30:52.657 29617 29717 I Nullgram: emoticon column count = 1
04-23 18:30:56.052 29617 29617 I Nullgram: useragent: Dalvik/2.1.0 (Linux; U; Android 13; 2211133C Build/TKQ1.220905.001) Nekogram/9.5.8 (3252; 381d52f35f552e10ad1701445dba9cd14acb7e43)
04-23 18:30:58.406 29617 29617 W Nullgram: java.lang.RuntimeException: Holder at20 ViewHolder{c01aab5 position=20 id=-8, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at19 ViewHolder{b6cdec0 position=19 id=-7, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at18 ViewHolder{a6b61c1 position=18 id=-5, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at17 ViewHolder{a88cacb position=17 id=-2, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at16 ViewHolder{e88ca8e position=16 id=-3, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at15 ViewHolder{5fbb28d position=15 id=-1766314024, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at14 ViewHolder{8392b78 position=14 id=-1626321945, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at13 ViewHolder{16b87f6 position=13 id=1548466699, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at12 ViewHolder{e3a5415 position=12 id=618177647, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at11 ViewHolder{cddd4a3 position=11 id=1474590930, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at10 ViewHolder{eea4146 position=10 id=688321550, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at9 ViewHolder{5337a5 position=9 id=212216832, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at8 ViewHolder{2677e70 position=8 id=65586930, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at7 ViewHolder{469b217 position=7 id=1444, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at6 ViewHolder{74337ca position=6 id=1444, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at5 ViewHolder{5ef2c79 position=5 id=-704933685, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at4 ViewHolder{ac0ffd4 position=4 id=1056103122, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at3 ViewHolder{bc42b4b position=3 id=-6, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at2 ViewHolder{a50f2c5 position=2 id=-1, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at1 ViewHolder{a9cf4d3 position=1 id=-9, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram: Holder at0 ViewHolder{c81cc37 position=0 id=-4, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram:
04-23 18:30:58.406 29617 29617 W Nullgram:      at Vc2.但是命运二(RecyclerView.java:657)
04-23 18:30:58.406 29617 29617 W Nullgram:      at Vc2.onLayout(RecyclerView.java:8)
04-23 18:30:58.406 29617 29617 W Nullgram:      at lc2.onLayout(RecyclerListView.java:1)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at f1.onLayout(ActionBarLayout.java:94)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at org.telegram.ui.ActionBar.DrawerLayoutContainer.onLayout(DrawerLayoutContainer.java:63)
04-23 18:30:58.406 29617 29617 W Nullgram:      at l81.onLayout(LaunchActivity.java:1)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1829)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1673)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.LinearLayout.onLayout(LinearLayout.java:1582)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:30:58.406 29617 29617 W Nullgram:      at com.android.internal.policy.DecorView.onLayout(DecorView.java:874)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:4196)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3572)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2538)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:9413)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1451)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1459)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.Choreographer.doCallbacks(Choreographer.java:1089)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.Choreographer.doFrame(Choreographer.java:1003)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1431)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.os.Handler.handleCallback(Handler.java:942)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:99)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:30:58.406 29617 29617 W Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:30:58.406 29617 29617 W Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:30:58.406 29617 29617 W Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:30:58.406 29617 29617 W Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:30:58.406 29617 29617 W Nullgram: Caused by: java.lang.IllegalStateException: Two different ViewHolders have the same stable ID. Stable IDs in your adapter MUST BE unique and SHOULD NOT change.
04-23 18:30:58.406 29617 29617 W Nullgram:  ViewHolder 1:ViewHolder{469b217 position=7 id=1444, oldPos=-1, pLpos:-1}
04-23 18:30:58.406 29617 29617 W Nullgram:  View Holder 2:ViewHolder{74337ca position=6 id=1444, oldPos=-1, pLpos:-1} p72{d47b6d1 VFED..... ......ID 0,0-1080,2142}, adapter:r72@34da997, layout:B91@3876784, context:org.telegram.ui.LaunchActivity@a819309
04-23 18:30:58.406 29617 29617 W Nullgram:      at Vc2.是由波兰蠢驴自主研发的一款全新RPG冒险游戏(RecyclerView.java:68)
04-23 18:30:58.406 29617 29617 W Nullgram:      at Vc2.但是命运二(RecyclerView.java:263)
04-23 18:30:58.406 29617 29617 W Nullgram:      ... 54 more
04-23 18:31:02.217 29617 29937 E Nullgram: java.net.SocketTimeoutException: failed to connect to dns.google/8.8.4.4 (port 443) from /192.168.2.52 (port 46708) after 1000ms
04-23 18:31:02.217 29617 29937 E Nullgram:      at libcore.io.IoBridge.connectErrno(IoBridge.java:235)
04-23 18:31:02.217 29617 29937 E Nullgram:      at libcore.io.IoBridge.connect(IoBridge.java:179)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.net.Socket.connect(Socket.java:646)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.Platform.connectSocket(Platform.java:182)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:145)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:131)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:90)
04-23 18:31:02.217 29617 29937 E Nullgram:      at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:30)
04-23 18:31:02.217 29617 29937 E Nullgram:      at PZ.doInBackground(ConnectionsManager.java:58)
04-23 18:31:02.217 29617 29937 E Nullgram:      at android.os.AsyncTask$3.call(AsyncTask.java:394)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.util.concurrent.FutureTask.run(FutureTask.java:264)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
04-23 18:31:02.217 29617 29937 E Nullgram:      at java.lang.Thread.run(Thread.java:1012)
04-23 18:34:51.778   799   799 D Nullgram: module path -> /data/app/~~3wIAncRrYSXB1kmULIgSSg==/top.qwq2333.nullgram-lB3HhqMocqTwqAlthd_gYQ==/base.apk
04-23 18:34:52.138   799   799 D Nullgram: checkSignature: Match Github Signature
04-23 18:34:52.140   799   799 E Nullgram: density = 2.75 display size = 1080 2296 413.755x413.849, screen layout: 268435810, statusbar height: 104, navbar height: 44
04-23 18:34:52.399   799  1048 I Nullgram: emoticon column count = 1
04-23 18:34:52.700   799  1040 I Nullgram: emoticon column count = 1
04-23 18:34:53.059   799  1076 I Nullgram: emoticon column count = 1
04-23 18:34:53.069   799  1088 I Nullgram: emoticon column count = 1
04-23 18:34:53.078   799  1095 I Nullgram: emoticon column count = 1
04-23 18:34:53.080   799  1101 I Nullgram: emoticon column count = 1
04-23 18:34:53.093   799  1107 I Nullgram: emoticon column count = 1
04-23 18:34:53.097   799  1114 I Nullgram: emoticon column count = 1
04-23 18:34:53.120   799   799 E Nullgram: density = 2.75 display size = 1080 2296 413.755x413.849, screen layout: 268435810, statusbar height: 104, navbar height: 44
04-23 18:34:53.158   799   799 E Nullgram: read string error
04-23 18:34:53.158   799   799 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:34:53.158   799   799 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:34:53.158   799   799 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:105)
04-23 18:34:53.158   799   799 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:34:53.158   799   799 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:34:53.158   799   799 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:34:53.158   799   799 E Nullgram: read string error
04-23 18:34:53.158   799   799 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:34:53.158   799   799 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:34:53.158   799   799 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:113)
04-23 18:34:53.158   799   799 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:34:53.158   799   799 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:34:53.158   799   799 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:34:53.158   799   799 E Nullgram: read string error
04-23 18:34:53.158   799   799 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:34:53.158   799   799 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:34:53.158   799   799 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:117)
04-23 18:34:53.158   799   799 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:34:53.158   799   799 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:34:53.158   799   799 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:34:53.158   799   799 E Nullgram: read string error
04-23 18:34:53.158   799   799 E Nullgram: java.lang.NegativeArraySizeException: -1
04-23 18:34:53.158   799   799 E Nullgram:      at rq2.readString(SerializedData.java:51)
04-23 18:34:53.158   799   799 E Nullgram:      at Dt2.但是命运二(SharedConfig.java:121)
04-23 18:34:53.158   799   799 E Nullgram:      at qh0.I(DialogsActivity.java:290)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.ActionBar.ActionBarLayout.引导尼古丁之力(ActionBarLayout.java:12)
04-23 18:34:53.158   799   799 E Nullgram:      at kV0.找回失散的亲人同时(INavigationLayout.java:5)
04-23 18:34:53.158   799   799 E Nullgram:      at org.telegram.ui.LaunchActivity.onCreate(LaunchActivity.java:870)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8502)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Activity.performCreate(Activity.java:8466)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1418)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3798)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3963)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2381)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:34:53.158   799   799 E Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:34:53.158   799   799 E Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:34:53.158   799   799 E Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:34:53.158   799   799 E Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:34:57.313   799   799 I Nullgram: useragent: Dalvik/2.1.0 (Linux; U; Android 13; 2211133C Build/TKQ1.220905.001) Nekogram/9.5.8 (3252; 381d52f35f552e10ad1701445dba9cd14acb7e43)
04-23 18:35:00.585   799   799 W Nullgram: java.lang.RuntimeException: Holder at20 ViewHolder{f8dee1 position=20 id=-8, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at19 ViewHolder{40cba5c position=19 id=-7, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at18 ViewHolder{bbb56c4 position=18 id=-5, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at17 ViewHolder{22e3956 position=17 id=-2, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at16 ViewHolder{e780f5 position=16 id=-3, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at15 ViewHolder{b53200 position=15 id=-1766314024, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at14 ViewHolder{d06dce7 position=14 id=-1626321945, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at13 ViewHolder{93725e9 position=13 id=1548466699, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at12 ViewHolder{a0e0604 position=12 id=618177647, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at11 ViewHolder{2da7d3b position=11 id=1474590930, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at10 ViewHolder{4f8fdbe position=10 id=688321550, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at9 ViewHolder{417b57d position=9 id=212216832, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at8 ViewHolder{eb97928 position=8 id=65586930, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at7 ViewHolder{f380b2f position=7 id=1444, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at6 ViewHolder{79ceec2 position=6 id=1444, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at5 ViewHolder{d47b6d1 position=5 id=-704933685, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at4 ViewHolder{cb3810c position=4 id=1056103122, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at3 ViewHolder{55f0ce3 position=3 id=-6, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at2 ViewHolder{7a49d position=2 id=-1, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at1 ViewHolder{eec9b6b position=1 id=-9, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram: Holder at0 ViewHolder{d83b94f position=0 id=-4, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram:
04-23 18:35:00.585   799   799 W Nullgram:      at Vc2.但是命运二(RecyclerView.java:657)
04-23 18:35:00.585   799   799 W Nullgram:      at Vc2.onLayout(RecyclerView.java:8)
04-23 18:35:00.585   799   799 W Nullgram:      at lc2.onLayout(RecyclerListView.java:1)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at f1.onLayout(ActionBarLayout.java:94)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at org.telegram.ui.ActionBar.DrawerLayoutContainer.onLayout(DrawerLayoutContainer.java:63)
04-23 18:35:00.585   799   799 W Nullgram:      at l81.onLayout(LaunchActivity.java:1)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1829)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1673)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.LinearLayout.onLayout(LinearLayout.java:1582)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
04-23 18:35:00.585   799   799 W Nullgram:      at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
04-23 18:35:00.585   799   799 W Nullgram:      at com.android.internal.policy.DecorView.onLayout(DecorView.java:874)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.View.layout(View.java:23877)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewGroup.layout(ViewGroup.java:6454)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:4196)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3572)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2538)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:9413)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1451)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1459)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.Choreographer.doCallbacks(Choreographer.java:1089)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.Choreographer.doFrame(Choreographer.java:1003)
04-23 18:35:00.585   799   799 W Nullgram:      at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1431)
04-23 18:35:00.585   799   799 W Nullgram:      at android.os.Handler.handleCallback(Handler.java:942)
04-23 18:35:00.585   799   799 W Nullgram:      at android.os.Handler.dispatchMessage(Handler.java:99)
04-23 18:35:00.585   799   799 W Nullgram:      at android.os.Looper.loopOnce(Looper.java:210)
04-23 18:35:00.585   799   799 W Nullgram:      at android.os.Looper.loop(Looper.java:299)
04-23 18:35:00.585   799   799 W Nullgram:      at android.app.ActivityThread.main(ActivityThread.java:8235)
04-23 18:35:00.585   799   799 W Nullgram:      at java.lang.reflect.Method.invoke(Native Method)
04-23 18:35:00.585   799   799 W Nullgram:      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
04-23 18:35:00.585   799   799 W Nullgram:      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
04-23 18:35:00.585   799   799 W Nullgram: Caused by: java.lang.IllegalStateException: Two different ViewHolders have the same stable ID. Stable IDs in your adapter MUST BE unique and SHOULD NOT change.
04-23 18:35:00.585   799   799 W Nullgram:  ViewHolder 1:ViewHolder{f380b2f position=7 id=1444, oldPos=-1, pLpos:-1}
04-23 18:35:00.585   799   799 W Nullgram:  View Holder 2:ViewHolder{79ceec2 position=6 id=1444, oldPos=-1, pLpos:-1} p72{d08a829 VFED..... ......ID 0,0-1080,2142}, adapter:r72@44a5c63, layout:B91@361b060, context:org.telegram.ui.LaunchActivity@800b93c
04-23 18:35:00.585   799   799 W Nullgram:      at Vc2.是由波兰蠢驴自主研发的一款全新RPG冒险游戏(RecyclerView.java:68)
04-23 18:35:00.585   799   799 W Nullgram:      at Vc2.但是命运二(RecyclerView.java:263)
04-23 18:35:00.585   799   799 W Nullgram:      ... 54 more
04-23 18:35:03.592   799  1522 E Nullgram: java.net.SocketTimeoutException: failed to connect to dns.google/8.8.4.4 (port 443) from /192.168.2.52 (port 44180) after 1000ms
04-23 18:35:03.592   799  1522 E Nullgram:      at libcore.io.IoBridge.connectErrno(IoBridge.java:235)
04-23 18:35:03.592   799  1522 E Nullgram:      at libcore.io.IoBridge.connect(IoBridge.java:179)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.net.Socket.connect(Socket.java:646)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.Platform.connectSocket(Platform.java:182)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:145)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:131)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:90)
04-23 18:35:03.592   799  1522 E Nullgram:      at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:30)
04-23 18:35:03.592   799  1522 E Nullgram:      at PZ.doInBackground(ConnectionsManager.java:58)
04-23 18:35:03.592   799  1522 E Nullgram:      at android.os.AsyncTask$3.call(AsyncTask.java:394)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.util.concurrent.FutureTask.run(FutureTask.java:264)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
04-23 18:35:03.592   799  1522 E Nullgram:      at java.lang.Thread.run(Thread.java:1012)

Please add this feature in next update"unlimited use for chat pin"

Why do you think you need this feature

Please add this feature in next update"unlimited use for chat pin"

Describe the solution you'd like

Please add this feature in next update"unlimited use for chat pin"

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[feature] Ads Filter for Channel Messages

Why do you think you need this feature

Some Telegram channels currently employ bots to automatically send out ads in the form of channel messages. These ads are usually repetitive, annoying, or inappropriate, and can be seen multiple times per day per channel, totaling tens of times per day if several channels are subscribed.

Describe the solution you'd like

One possible solution is to implement a keyword-based message filter which allows users to define the keywords they do not want to see. Nullgram may hide the message in case filters are triggered.

Describe alternatives you've considered

  1. Given the common form of advertising, a URL domain-based filter should also work.
  2. If hiding a message from displaying is not possible (e.g., affect the read state, or chances of false positives), a possible alternative is to replace the message text to something like "Filtered message here" and remove the images only.
  3. If Alt. 2 is also not feasible, another possibility is to apply the spoiler effect (click to reveal) universally on the message text and image, optionally with a different visual style than normal spoiler.

Is your feature request related to a problem

This feature request is related and similar to #35, but targets at user/bot-generated channel messages (ads).

The filter can ignore messages in the comment sections or associated groups of channels, if this can reduce development effort, as human discussion participants are unlikely to send out ads.

[Bug] Nullgram导入设置无法使用

Steps to reproduce

进入Nullgram设置，导出配置再点击导入配置

Expected behaviour

导入设置能够正常通过saf选择本地配置文件

或点击配置文件的消息菜单可以选择导入配置

Actual behaviour

导入设置功能需要文件和媒体权限，但权限设置中并没有此权限，导致Nullgram无限请求权限无法导入设置

点击导出到收藏夹的配置文件出现的消息菜单也没有导入设置这一选项

Smartphone Information

  • Oneplus 7
  • YAAP 13

Nullgram Version

v9.6.3-004c212

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

大概无需日志

[feature] Translate

Why do you think you need this feature

translations should be translated in-message instead of pop-up

Describe the solution you'd like

translations should be translated in-message instead of pop-up

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[Bug] 打开超链接时有概率未响应

Steps to reproduce

1.打开超链接

Expected behaviour

拉起浏览器

Actual behaviour

有概率无响应
image

Smartphone Information

  • 设备 红米 Note12 Turbo
  • Android13
  • MIUI14.0.19
  • 浏览器 Chrome 126.0.6478.122 Android

Nullgram Version

v10.14.3-dc2fb1a arm64

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

log-2024-07-10.txt / 384.11K

log-2024-07-10 (2).txt / 390.58K

[Bug] Crash on android 13

Steps to reproduce

Open the app

Expected behaviour

App opens

Actual behaviour

App crashes

Smartphone Information

Os: android 13
One-ui: 5.1

Nullgram Version

v9.6.7-ee9c46b

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

FATAL EXCEPTION: main
Process: top.qwq2333.nullgram, PID: 10717
java.lang.UnsatisfiedLinkError: No implementation found for void org.telegram.tgnet.ConnectionsManager.native_setJava(boolean) (tried Java_org_telegram_tgnet_ConnectionsManager_native_1setJava and Java_org_telegram_tgnet_ConnectionsManager_native_1setJava__Z) - is the library loaded, e.g. System.loadLibrary?
at org.telegram.tgnet.ConnectionsManager.native_setJava(Native Method)
at org.telegram.messenger.ApplicationLoader.onCreate(ApplicationLoader.java:217)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1266)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7619)
at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2400)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8762)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

[feature] Remove Xposed Protection?

Why do you think you need this feature

Can you Remove Xposed Hookinh protection made by nekko?

Describe the solution you'd like

.

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[Bug] 内存泄漏

Steps to reproduce

打开任意群等待一段时间，软件就会闪退

Expected behaviour

不应该闪退

Actual behaviour

闪退了

Smartphone Information

pixel7pro
Android14 qpr3（biuld number：AP1A.240305.019.A1）
已root，root途径是原版magisk
12g ram

Nullgram Version

Nullgram v10.14.5-preview-8486b7e (1645201552) arm64 Based on Telegram 10.14.5 (4945)

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

crash log

[Bug] Some dynamic stickers cannot be previewed

Steps to reproduce

1.Add sticker pack https://t.me/addstickers/Animated_Round_Pretty_Cat
2.To send stickers
3.See this dynamic sticker pack cannot be previewed

Expected behaviour

Dynamic sticker pack can be previewed

Actual behaviour

Dynamic sticker pack cannot be previewed

Smartphone Information

Device: Xiaomi Poco F3
OS: Android 13
Version: 4.19.274-InfiniR_Alioth_v2.47//68d555f0ab92

Nullgram Version

v9.5.4-preview-3b48113 (1645200988)

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

https://github.com/reiuyfan/log/blob/main/logcat_03-19-2023_00-54-46.txt

[Bug] Notification bar does not change color according to background color shade

Steps to reproduce

  1. Go to Settings（设置）
  2. Go to Chat Settings（主题与样式）
  3. Click on Browse Themes（浏览主题）
  4. Switch to a theme with a bright background color. (Such as Arctic)（北极）

Expected behaviour

Like this screenshot (from official Telegram)
Screenshot from official Telegram

Actual behaviour

This screenshot (from Nullgram), notification bar text does not change color according to background color shade.
Screenshot from Nullgram

Smartphone Information

  • Device: Redmi K40 Pro
  • OS: MIUI 13 (Android 12)

Nullgram Version

v9.2.2.df376fc
Only this CI version has bug.

Version requirement

  • I am using latest debug CI version of QAuxiliary and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

Maybe not need log

[feature] 点击链接预览中的图片打开图片而非链接

Why do you think you need this feature

（如果没记错）在 23 年 10 月 28 日的更新中 Telegram 引入了新的链接预览样式，其中点击链接预览中的图片不会打开图片，而是会直接跳转到链接内容。导致查看链接指向的图片比之前多了至少一次跳转，很多情况下并不方便。

Describe the solution you'd like

点击链接预览中的图片使用 telegram 的图片查看器打开，（即与普通消息中的图片相同的处理方式），点击链接预览的其他部分打开链接。必要的话添加为可选开关。

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

More icons

Why do you think you need this feature

nekox and nekogram have really good icons which also support monet theme, its a good idea to have one for nullgram

Describe the solution you'd like

draw one, a simple one

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

Publish APKs in GitHub releases

Why do you think you need this feature

I don't use Google Play Services at all, so I don't have the Play Store, I use Obtainium to get apps directly from GitHub and also auto update them without my interaction.

Describe the solution you'd like

Publish APKs in GitHub release page on every new update, you already built them, so just upload the artifacts while creating a new release.

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

please add features when you type in your own language, you can change it to another language, thank you[feature]

Why do you think you need this feature

please add features when you type in your own language, you can change it to another language, thank you

Describe the solution you'd like

please add features when you type in your own language, you can change it to another language, thank you

Describe alternatives you've considered

please add features when you type in your own language, you can change it to another language, thank you

Is your feature request related to a problem

please add features when you type in your own language, you can change it to another language, thank you

[Bug] 版权声明被错误移除 / Original copyright details removed wrongly

在 2ce3cea 中，TMessagesProj/src/main/java/org/telegram/messenger/BuildVars.java头部的 GPL v2 版权声明 Copyright Nikolai Kudashov, 2013-2020. 被错误移除，并替换为 Copyright (C) 2019-2024 qwq233 <[email protected]>。
虽然您对此文件有更改，但显然更正确的做法是保留此行版权声明，而且我看你在TMessagesProj/src/目录下的其他文件也都是保留了原有版权声明的。

P.S. CONTRIBUTING.md里这个code header是指什么，版权声明吗？我个人认为具体写清楚会比较好
P.P.S. Compilation Guide太旧了，而且有些不清楚（比如说那个two android apps with application IDs），感觉可以直接删了换成指向上游的超链接

[Bug] Application crash after system update.

Steps to reproduce

Just open app from launcher.

Expected behaviour

App works properly.

Actual behaviour

Crash immediately.
Throws java.lang.UnsatisfiedLinkError

Smartphone Information

  • Device: Redmi K30 Pro (lmi)
  • OS: Android 11 (crDroid 7.21)
  • (Kernel?) Version: 4.19.234

Nullgram Version

v8.9.3-preview-3cadedb (1645200792)

Version requirement

  • I am using latest debug CI version of QAuxiliary and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

Taken from MatLog: logcat.txt

And system it's own report:

msg: java.lang.UnsatisfiedLinkError: No implementation found for void org.telegram.tgnet.ConnectionsManager.native_setJava(boolean) (tried Java_org_telegram_tgnet_ConnectionsManager_native_1setJava and Java_org_telegram_tgnet_ConnectionsManager_native_1setJava__Z)
stacktrace: java.lang.UnsatisfiedLinkError: No implementation found for void org.telegram.tgnet.ConnectionsManager.native_setJava(boolean) (tried Java_org_telegram_tgnet_ConnectionsManager_native_1setJava and Java_org_telegram_tgnet_ConnectionsManager_native_1setJava__Z)
	at org.telegram.tgnet.ConnectionsManager.native_setJava(Native Method)
	at org.telegram.messenger.ApplicationLoader.onCreate(ApplicationLoader.java:285)
	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1204)
	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6721)
	at android.app.ActivityThread.access$1300(ActivityThread.java:238)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1914)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:200)
	at android.os.Looper.loop(Looper.java:286)
	at android.app.ActivityThread.main(ActivityThread.java:7666)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

[Force chat blur]

Why do you think you need this feature

I really wish for force chat blur on nullgram, as of now we can only enable blur on telegram default themes but i need to enable blur on all themes,

Describe the solution you'd like

Nothing just looks beautiful than the current one

Describe alternatives you've considered

Hope you will add this in coming updates

Is your feature request related to a problem

Nop

Request: Remove tracker -- Google CrashLytics

Steps to reproduce

With ClassyShark3xodus, I found Google CrashLytics imbedded. This app is a well build and highly versatile Telegram fork app, but as a FOSS software, I think removing all trackers would be more privacy friendly.

Expected behaviour

null

Actual behaviour

null

Smartphone Information

Samsung A54

Nullgram Version

v10.8.1

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

null

[Bug] Large photo size should not be enabled in secret chats

Steps to reproduce

  1. Enabling sendLargePhoto in nullgram.
  2. Create a secret chat with the official client.
  3. Send 2560px image in nullgram.
  4. This image will not be viewed correctly in the official client.

Expected behaviour

This image will be viewed correctly in the official client.

Actual behaviour

This image cannot be viewed correctly in the official client, a very small resolution preview is shown.

Smartphone Information

  • Redmi Note 12 Turbo
  • Android 14
  • null 10.14.5-0893d91 off 10.15.1

Nullgram Version

v10.14.5-0893d91

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

no need.

secret chat will not automatically transcode a 2560px image to 1280px resolution. The recommendation is to disable sendLargePhoto in secret chat.

[feature] Option to hide avatar/title of a chat from the dialogs list.

Why do you think you need this feature

Privacy feautre

This feature is a good one that is mainly considered or listed under privacy features in the client named ForkClient — Unofficial Telegram Messenger for Android. And i assume it is also there in the client nekox .

well i am not here with the intention of advertising the mentioned repositories.

Describe the solution you'd like

I am noob enough to describe it but the feature i mentioned was located (In those clients) in the dialogs list -- which can be enabled by tapping hide title from the dropdown menu in a chat.

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[Feature Request] Restore NekoX Custom api

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
since unofficial has limitations like limiting to 250 channel and quicker chance for getting reported (i mean getting limits due to it)

Describe the solution you'd like
A clear and concise description of what you want to happen.
restore old api
https://t.me/NekogramX/539

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[feature] 拓展「下拉打开归档对话」功能

Why do you think you need this feature

在 telegram 加入 stories 功能之后，在聊天列表下拉时如果有 story 会优先触发 story 栏的拓展，再次下拉才会进入已归档聊天列表。同时 story 通过点击也可以查看，下拉手势并不是唯一的入口。

Describe the solution you'd like

拓展「下拉打开归档对话」功能使得在该选项打开的情况下，在聊天界面执行下滑动作时直接进入已归档聊天列表，不再触发 story 栏。

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[Bug] The wrong in-memory order of proxies becomes problematic when proxy list is long

Steps to reproduce

The effects of this bug cannot be detected in a short test. You should use proxies in a daily basis, in a country in which old proxies get suspended everyday (or simulate it)

  1. Add too many proxies per day
  2. Old proxies has more priority in everything. in Proxy rotations, ping checks, order of showing the list, everything is in reverse order.
  3. New proxies (which are luckier to be connectable) can be found harder, either by proxy rotation controller or by the user.

Expected behaviour

The order of checking and viewing proxies should be like the order of the proxies in Telegram X, Desktop, iOS, Cherrygram. Ascending order is a bad choice. The list should be saved in reversed order on the disk. (look at SharedConfig.java)

The latest added proxies are luckier to be working because earlier added proxies are older, so they are usually dead or blocked by ISPs. So the proxy rotation controller should start checking proxies from the latest proxy instead of the earlier proxies which have less chance to be available, to skip checking a lot of old proxies and find the available proxy in less time (Fixing SharedConfig.java is enough, so no need to touch ProxyRotationController.java). Also, the user prefers to see latest added proxies viewed at the beginning of the list, instead of the earliest because scrolling to the end to see the proxies added a moment ago, is hard when it's long. Also, ping checks and ping sort should get started from the latest one, not the earliest. There's a big chance for old proxies to be unavailable when the list is too long. The current in-memory list order should become time descending everywhere in the app.

Actual behaviour

Some ISPs destabilize all network protocols randomly with an interval, causing proxies sometimes get unavailable (red) temporarily and then available again. So the user constantly removes them by mistake and adds new proxies (or just adds new proxies and doesn't remove the old ones, so the list becomes longer and longer, with older and dead proxies being ping-checked firstly and also viewed at the top of the list when there's no ping sort). The in-memory sort is correct (time descending) In Telegram Desktop, Cherrygram, etc so there's no problem when the list is long, because the latest added proxies (which are probably healthy and working) are always accessible at the top of the list in these clients. A long list becomes problematic only when the order is wrongly reversed, e.g. in Nullgram, so the user needs to remove the unavailable proxies constantly (An unneeded difficulty) to shorten the list (despite most of the list items being usually healthy and just temporarily unavailable). Having a short list, sometimes causes lockups too, because there's more chance for all items of the list to get unavailable at once when the list is short.

So, for users who add proxies everyday, it's much easier to get online with other clients (e.g. TDesktop, Cherrygram, ...) despite not having ping sort, auto switch and other proxy features which Nullgram has.

Smartphone Information

All devices, everywhere

Nullgram Version

All versions after Telegram internal proxy feature has been created

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Based Chin..

Why do you think you need this feature

Due to the fragmentation of the NekoX and Nekogram communities, and the serious problems with the main developers of NekoX and Nekogram1, I decided to make Nullgram to integrate both of their functions to avoid these problems.

Null used in computer programming for an uninitialized, undefined, empty, or meaningless value. In the name of Nullgram, the purpose is to express that there is no such bad things. Nullgram won't push FCM-Notification "nmsl"2 or somethings like that to your phone, won't send ads3 to channels, won't compete maliciously4 or publish malicious rumors about competitors

Describe the solution you'd like

Lmao

Describe alternatives you've considered

No response

Is your feature request related to a problem

No response

[Bug] Weird Dex Classes Found, Explanation Request

Steps to reproduce

There are many weird dex classes found by Inure App, containing several uncomfortable words, like the following example shown in the appended image.
Screenshot_20240515_192445_Inure

Expected behaviour

An explanation of the purpose of these weird dex classes is requested.

Actual behaviour

Weird dex classes found.

Smartphone Information

Samsung A54

Nullgram Version

v10.12.0-a9bddd5

Version requirement

  • I am using latest debug CI version of Nullgram and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs

Null

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.