Conversation
updated so that telegram-reports will actually work
mastrolube
left a comment
mastrolube
left a comment
There was a problem hiding this comment.
some things to discuss :)
|
|
||
| rm -rf /data/data/com.termux/files/home/.cache/pip | ||
|
|
||
| # Delete python completely |
There was a problem hiding this comment.
but is should be reinstalled at some point
There was a problem hiding this comment.
I think the pointless bash does it, I never reinstalled it manually
|
|
||
| # download the config examples and put them in the correct folder | ||
|
|
||
| wget -O - https://github.com/GramAddict/bot/archive/master.tar.gz | tar -xz --strip=2 "bot-master/config-examples" |
There was a problem hiding this comment.
that's cool but we already have the config-example is we git clone and we can gramaddict init your_username if we're using pip
There was a problem hiding this comment.
I didn't have the config-example folder, after following the old installation instructions
| # enable wake lock to make sure your device does not go into deep sleep | ||
|
|
||
| termux-wake-lock | ||
|
|
There was a problem hiding this comment.
should be nice to have the adb shell setprop persist.adb.tcp.port 5555 pointed out from Fallen to have adb on boot
There was a problem hiding this comment.
Agree, but requires root, would be nicer if someone found a way to do this without root on all devices
There was a problem hiding this comment.
I am pretty sure you can just use termux:boot instead and let it run adb tcpip port
There was a problem hiding this comment.
That'd be kind of weird though, no? Since what is it going to adb? When I run adb tcpip 5555 on an unconnected device, it just says: error: no devices/emulators found.
The whole issue is that without root, you cannot open a static port (which makes sense). There is an open port for pairing + a pairing code, which are randomised every time they are requested, so you cannot use these on boot (unless you could somehow access this info automatically with a script).
I've been trying to find a workaround, but I haven't found one so far. The closest thing to a solution for an unrooted phone seems to be installing TWRP and changing system files in recovery mode, but at that point you've already unlocked your bootloader, and you might as well tell people to just root their phones. So that's not a solution.
There was a problem hiding this comment.
you are supposed to be connected to localhost already, not sure if that works via usb adb only?
SELinux just prevents you from accessing persistant adb options has nothing to do with a static port.
You can relock the boatloader after you are done changing files, problem is that is way too much effort.
There was a problem hiding this comment.
How would you already be connected to localhost?
The static port part refers to the wireless pairing not having a static port. If it had a static port + pairing code, this would be 3 lines of code with Termux:boot.
I don't know about other brands, but on samsung unlocking bootloader trips knox and voids warranty, which is irreversible.
There was a problem hiding this comment.
Well that is the part I was trying to figure.
If it were static then yes but it isn't.
I don't really see the point of dedicating a whole section for people who want to bot on their personal device instead of a thorwaway phone anyways.
made some changes
|
I don’t see what it has to do with personal or throwaway devices? I don’t
even use my personal phone for this
…On Tue, 1 Feb 2022 at 13:52, FallenKN ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In termux.md
<#6 (comment)>:
> +nano accounts/[your-account-name]/config.yml
+
+nano accounts/[your-account-name]/filters.yml
+
+nano accounts/[your-account-name]/telegram.yml
+
+# etc
+```
+
+## Step 5: Run
+
+```
+# enable wake lock to make sure your device does not go into deep sleep
+
+termux-wake-lock
+
Well that is the part I was trying to figure.
If it were static then yes but it isn't.
I don't really see the point of dedicating a whole section for people who
want to bot on their personal device instead of a thorwaway phone anyways.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAU2QIQAKBZNVZOAMVTL3LDUY7QRDANCNFSM5NGE3NPA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
you have a section dedicated to people who already have termux installed. |
Yeah, that's because I had gramaddict installed through the previous guide and had issues installing pandas for telegram reports. I had to deinstall everything to get it to work. That's the only reason I rewrote this |
3 participants
updated so that telegram-reports will actually work