 | App Manager | Chat | 223 Members |
| Official room for App Manager. Read community guidelines here: https://gist.github.com/MuntashirAkon/ee30789d2d3db2f97402baa60d89e04d | 18 Servers |
| App Manager | Chat | 223 Members |
| Official room for App Manager. Read community guidelines here: https://gist.github.com/MuntashirAkon/ee30789d2d3db2f97402baa60d89e04d | 18 Servers |
| Sender | Message | Time |
|---|---|---|
| 20 Apr 2024 | ||
 § | F-Droid users should be able to view all changes vs the previous one since they're compared vs previous Stable release only not with any pre-release. You might see new features in Stable but by definition they're actually not new because already tested for RC. | 01:58:19 |
| § | * Confusion about RC https://github.com/amcommunity/TipsAndTricks/issues/17
remove "feature-locked" and "only" should be replaced with "mostly" otherwise it creates confusion. My understanding is Alpha, Beta are for testers & before implementing new features to Stable, it goes through the phase of RC. So by definition it does makes sense to include new features to RC. | 01:58:28 |
| § | * F-Droid users should be able to view all changes vs the previous one since they're compared vs previous Stable release only not with any pre-release including RC. You might see new features in Stable but by our definition they're actually not new because already tested for RC. | 01:59:43 |
| § | * F-Droid users should be able to view all changes vs the previous one since they're compared vs previous Stable release only not with any pre-release including RC. You might see new features in Stable but by our definition they're actually not new because already tested for RC. Stable:
| 02:00:45 |
| § | * Confusion about RC https://github.com/amcommunity/TipsAndTricks/issues/17 Release Candidate:
remove "feature-locked" and "only" should be replaced with "mostly" otherwise it creates confusion. My understanding is Alpha, Beta are for testers & before implementing new features to Stable, it goes through the phase of RC. So by definition it does makes sense to include new features to RC. | 02:01:10 |
| § | * Confusion about RC https://github.com/amcommunity/TipsAndTricks/issues/17 Release Candidate:
remove "feature-locked" and "only" should be replaced with "mostly" otherwise it creates confusion. My understanding is Alpha, Beta are for testers & before implementing new features to Stable, it goes through the phase of RC. So by definition it does makes sense to include new features to RC. --- OR remove the word "new" i.e. bug fixes only for RC & new features included only in Stable, in that case it contradicts the definition of Stable. | 02:04:34 |
| § | * F-Droid users should be able to view all changes vs the previous one since they're compared vs previous Stable release only not with any pre-release including RC. According to (1) You might see new features in Stable but by our definition they're actually not new because already tested for RC. Stable:
| 02:05:03 |
| § | * Confusion about RC https://github.com/amcommunity/TipsAndTricks/issues/17 Release Candidate:
1. remove "feature-locked" and "only" should be replaced with "mostly" otherwise it creates confusion. My understanding is Alpha, Beta are for testers & before implementing new features to Stable, it goes through the phase of RC. So by definition it does makes sense to include new features to RC. --- 2. OR remove the word "new" i.e. bug fixes only for RC & new features included only in Stable, in that case it contradicts the definition of Stable. | 02:05:19 |
| § | * F-Droid users should be able to view all changes vs the previous one since they're compared vs previous Stable release only not with any pre-release including RC. According to (1) you might see new features in Stable but by our definition they're actually not new because already tested for RC. But then Stable ones will be insignificant so (2) seems better. Stable:
| 02:10:18 |
| § | I'm asking about the clear definitions of these because I requested F-Droid to pick RC pre-releases. So from F-Droid users prospective RC (which is not suggested) should include new features in it for those who are interested for testing without waiting for Stable to include them. | 02:21:52 |
 Muntashir Akon | In reply to @marcdw:matrix.orgIt does allow downgrading, but information provided here are insufficient to draw any conclusions. | 07:31:03 |
| Muntashir Akon | In reply to @shuvashish76:matrix.orgAlpha, beta and RCs are meant for testers. So, they’re not suitable for F-Droid if they don’t specifically provide beta testing options. | 07:36:38 |
| 21 Apr 2024 | ||
 stephen_matrix.org | In reply to @marcdw:matrix.org Sorry for late reply. Device Info: Rooted Samsung Galaxy A22 (Android 12) | 04:59:08 |
| stephen_matrix.org | * Sorry for late reply. Yes, downgrading worked on 3.1.5. The only rooted device I have is this mobile I am using, so I cannot try on other Android versions Device Info: Rooted Samsung Galaxy A22 (Android 12) | 05:02:09 |
 obersuppenruehrer | Muntashir, does AM-Debug have any signature verification? I unintentionally signed it (=AM-Debug 4.0b1) with my personal test key and could not get past the liability message. Reinstalled with original key, and it works. | 12:07:08 |
| Muntashir Akon | In reply to @obersuppenruehrer:matrix.orgNo, AM does not check its own signature. It’s unnecessary because crackers can easily bypass those checks. Also, liability albeit limited does not pass to the original authors when the software is modified even if it’s only the signature. | 12:58:47 |
| obersuppenruehrer | I thought so. Must have been a glitch then. | 13:23:20 |
| 25 Apr 2024 | ||
| obersuppenruehrer | Muntashir, AM 4.0b1 finally fixes the problem of the empty main screen list in Android 6 (Galaxy Note 4), which had been there since AM 2.5.x (2.5 was the last working version that i can finally retire today). Dunno what u changed, but it works! PS: If anyone wonders why I still use such an ancient fone: It has several features that no current fone has. Perfect Call Recoding, IR emitter and receiver (perfect universal remote) and more. I also use it for landline calls via an app from my ISP. Obviously, it is NOT my primary fone. | 19:39:29 |
| 26 Apr 2024 | ||
| Muntashir Akon | In reply to @obersuppenruehrer:matrix.orgA lot of people still use Android Lollipop based TV. | 02:10:02 |
| 29 Apr 2024 | ||
 noobzhang changed their profile picture. | 11:41:50 | |
| 30 Apr 2024 | ||
 永雏糖肥 joined the room. | 00:50:52 | |
| 永雏糖肥 | Wireless debugging mode using paircode cannot be completed in ROMs without freeform windows mode that can be displayed in Settings(of course includes Development Options ) App Manager can get the port but the pairing code needs typing manually, but once the focus switches from Settings to others, the pairing code becomes invalid immediately. Some apps like Shizuku use a notification to solve this problem, like these screenshots below. Can App Manager add this feature in the future? Thanks | 01:05:19 |
| 永雏糖肥 |  Download Screenshot_20240430-083018_App_Manager.png | 01:05:49 |
| 永雏糖肥 |  Download Screenshot_20240430-084416_Shizuku.png | 01:05:50 |
| 永雏糖肥 |  Download Screenshot_20240430-084448_Settings.png | 01:05:51 |
| 永雏糖肥 | * Hello. Wireless debugging mode using paircode cannot be completed in ROMs without freeform windows mode that can be displayed in Settings(of course includes Development Options ) App Manager can get the port but the pairing code needs typing manually, but once the focus switches from Settings to others, the pairing code becomes invalid immediately. Some apps like Shizuku use a notification to solve this problem, like these screenshots below. Can App Manager add this feature in the future? Thanks | 01:06:30 |
| 永雏糖肥 | * Hello. Wireless debugging mode using paircode cannot be completed in ROMs without freeform windows mode that can be displayed in Settings(of course includes Development Options ) App Manager can get the port but the pairing code needs typing manually, but once the focus switches from Settings to others, the pairing code becomes invalid immediately. Some apps like Shizuku use a notification to solve this problem, like these screenshots below. Can App Manager add this feature in the future? Thanks | 01:06:49 |
| 永雏糖肥 | * Hello. Thanks to developers for creating this wonderful app. I found that Wireless debugging mode using paircode cannot be completed in ROMs without freeform windows mode that can be displayed in Settings(of course includes Development Options ) App Manager can get the port but the pairing code needs typing manually, but once the focus switches from Settings to others, the pairing code becomes invalid immediately. Some apps like Shizuku use a notification to solve this problem, like these screenshots below. Can App Manager add this feature in the future? Thanks | 01:08:12 |
| 永雏糖肥 | * Hello. Thanks to developers for creating this wonderful app. I found that Wireless debugging mode using paircode cannot be completed in ROMs without freeform windows mode and split mode that can be displayed in Settings(of course includes Development Options ) App Manager can get the port but the pairing code needs typing manually, but once the focus switches from Settings to others, the pairing code becomes invalid immediately. Some apps like Shizuku use a notification to solve this problem, like these screenshots below. Can App Manager add this feature in the future? Thanks | 01:13:35 |
| § | https://github.com/MuntashirAkon/AppManager/issues/892 | 03:51:02 |