yashsingh1/xdaforums huggingface dataset:
[OnePlus Open] dentimarius:
I just switch back to my Fold 4. In my opinion a good phone is 50% hardware and 50% software. I will wait for Fold 6. Samsung has to push something to stay over competitors. I don't like ideea to spend 1800 Eur + another 100-150 Eur( car charger, second wall charger, 2 cables) on a "half phone" when Fold 5 costs 1400 Eur(cameras are a little lower, and a 'remote' form factor). Maybe...just maybe.....If the 1+ had a under 1400 Eur price .

Foldables are sensitive with inner display. With my Fold 4 I had some dead pixels. In one week the phone back in my pocket with standard warranty( no care program). They change inner display, both batteries and some additional Kitt( I don't know what this can be) for free. 1+ is far away of this performance in Europe.

Don't get me wrong. 1+ open is still a nice phone, wider display, good cameras, crease on big display is very very small(almost flat). But he price, customers support, warranty, adițional charger and cable needed.... Just don't worth it, in my opinion.... At almost 2000 euros, a phost must to be perfect.
[OnePlus Open] z1c_wh:
I bet the next Samsung Fold, at its sixth generation -I repeat sixth!- will have an external display that finally makes sense.

After years of boring narrow external screens we'll be grateful to Oppo and other manufacturers (the Pixel Fold itself is preferable at least in my case) who have been able to create perfectly enjoyable devices for all situations.

Samsung wins in software, but in my case that's not all. Those devices are incredibly boring, as an ex-owner or just when I handle them.

Oneplus Open is my actual device

p.s. I really loved the early Samsung Folds, the first one obviously, which was the absolute novelty, I also loved the ZFold 2 which made a notable leap forward, but very little has changed in the last 4 years and what was previously a novelty went with time, at least from the third fold, redesigned for complete uses.
[OnePlus Open] jim262:
It's better!
[OnePlus Open] ultramag69:
A lot of the youtube bloggers are saying that the Fold 6 leaks are swaying towards it having a bigger outer display. Again, these are just leaks.

Besides, the release for the Fold 6 is gonna be at the end of the year. That's around 9 to 10 months before we'll get it in hand...

I still use my Find N3 more than my Fold 4 though waiting to see how fast Oppo pushes updates for their firmware and security updates.

Fold 4 is getting Android 14 as I say this (in some regions), wonder how long it will take Oppo/Oneplus?
[OnePlus Open] goattee:
I'm on the USA with an unlocked non-carrier Z Fold 3. I got that upgrade about two weeks ago.
[OnePlus Open] z1c_wh:
Samsung usually releases new foldables in August.

In my opinion it will be the same size as OPEN because they understood that they would sacrifice little to get a lot (more usability and sense), and with each passing year it makes less and less sense to replicate the identical device from the year before.

We will see the expected (alleged) changes regarding display resistance, crease and thickness. We will talk about it again in August.
[OnePlus Open] irmatt:
Really missing some of the Samsung features. Bixby routines, and Goodlock on the top of the list.

I'm very surprised at how little customization features there really are on this phone. I feel as if I'm stuck with what they give you.
[OnePlus Open] goattee:
It's not that surprising when you consider the size of the respective companies. I'll bet that the Find N3 in it's Chinese version doesn't have any refinements and features that we're not seeing in the Open. I'm assuming that they'll respond to revenue over the next couple of years if it justifies paying for more development resources. But if Samsung is smart they will respond with a competitive form factor-- and that would put a ceiling on Oneplus market share.

I'm tempted to buy a Open but my practical side is waiting to see what Samsung does. Coincidentally my payments on my Fold 3 end in July. Just in time for product announcements
[Samsung Galaxy S22] miraclepotential:
I've been using Android as a development platform for years and recently updated my phone from an S10 to an S22, however the level of aggressive battery optimisations and other device "care features" this phone has makes running processes in Termux very difficult and error prone. I've disabled all the "optimisation" features I can and all the battery features I can but still struggle with this.

I've already run the necessary adb commands to disable the "zombie process killer" and up the required process limits but still doesn't seem right.

I wondered, if I rooted this and flashed a custom rom would I be able to make better use of the device or am I better just selling it and getting a Pixel 7 pro or something closer to stock?
[Samsung Galaxy S22] jojos38:
I don't think it would help a lot unless you know exactly the cause of your processes being killed and you're not able to get rid of it without root

In case you weren't aware you can uninstall almost ANY application using ADB even without root, you can also force an app to go into battery optimized state (in Android settings) or not
[Samsung Galaxy S22] miraclepotential:
I'm pretty sure this is a Samsung change to the AOSP for "battery optimisation"
[Samsung Galaxy Z Flip 5] doczyus:
Dear Z Fip 5 Users,

Did you meet with this animation on your device? View attachment 6044360

It contains about 4-5 sec. randomly, usually when I've got a message (SMS, Meta Messenger) and sometimes at other type of alerts. Not always, just randomly.

I would like turn its off, but did not found any option to set off...

I have the latest stock ROM and has not special installed apps on the phone. The type of the device: SM-F731B

Thank you in advance!

Regards,

doczyus
[Samsung Galaxy Z Flip 5] johnny8910:
That looks like an edge lighting + feature
[Samsung Galaxy Z Flip 5] bbacon:
Yeah that's definitely one of the settings in Edge Lighting + app. Just open the app and turn it off
[Magisk] omegavschaos:
Hello, first of all thank you for your work.

I'm trying to do the same thing as the normal application but I don't know if it's part of this project or if it's a bug.

When I use the Tailscale application, everything works fine.

I can:

1. Access other nodes in my tailnet from my android via :

1.1. subnet ipv4 192.168.x.x

1.2. tailnet ipv4 100.x.x.x

1.3. magiskDNS hostname configured to use self-hosted local DNS (blocky) accessible in my tailnet

With your magisk module in place. I can't get anywhere with this.

I've changed the parameters of the Tailscale command

`tailscale up --accept-dns --accept-routes --advertise-exit-node`

Which runs without any error. The android appear in the Tailscale.com dashboard.

To try to get access to magiskDNS. But I have the impression that Android ignores them completely.

From termux I can't ping a machine from tailnet but I can with `tailscale ping`

I feel like I'm missing something.

I read some of the issues on your GitHub to see try to figure out if there were any subtleties to take into account but it didn't help so I'm trying here.

You seems to use clash mihomo from box for magisk (that I didn't acknowledge before) but I failed to make it worked properly. Maybe I'm not in the good path.

I have a OnePlus 6T running OxygenOS 11.1.2.2 (Android 11) last official update since the end of their support.

I have magisk version 26404 last canary version up to date. With a few modules but none affecting the network other than yours.

I also use LSPosed essentially for gravitybox and some root hide stuff.

Now I'm using your module `Magisk Tailscaled v1.56.1.3` and I start testing it with the version before.

I know it's a long post but I'm not very familiar with the forum discussion and I'm not English native speaker so please apologize for my bad English 🙏.

If you think it's better for my case to fill a bug on your GitHub, tell me to and I will.
[Magisk] alfanveykov:
Thank you for trying my module, about tailscale with magisk dns,routes,exit node, currently I have a lot of problems with this feature, because tailscaled binaries are expected to run on Linux machines, for example tailscale magicdns tries to overwrite /etc/resolv.conf with tailscale dns which on android we don't have.

This module also runs with "userspace-networking", to access other tailscale IPs we need to use local proxies/socks on port 1099, this depends on your usage, for example I use "NekoBox"/mihomo to route my 100.x.x.x to use local proxy on port 1099.

For ipv4 subnet 192.168.x.x, I have no idea for now, you can try the fix available in the official tailscale repository.

I'm sorry, there's a lot of undocumented stuff in the magisk tailscaled repo, next time I'll create clearer documentation on how to troubleshoot any errors.

My english also bad, I always revise my english with translate app before post if I write so manny text in english, because my main language is not english, never talk in english in real life, I just can typing and understand other english text.

Please open issue on github with a logs attached.
[Magisk] mesabogiii:
This is brilliant.

Will it be possible to use for wireguard?

Thanks
[Magisk] Neal27:
I have managed to install tailscale on magisk. I have also started the subnet routing feature which is working perfectly. But the exit node is not working. Can you please help?
[Magisk] Neal27:
Update - I have managed to run both the subnet routing and exit node. Working like a charm. Thanks a lot for the module. Remote access has never been this easy
[Magisk] Neal27:
Tailscale by default use wireguard protocol. Do you have anything specific requirements?
[Magisk] Neal27:
Exactly what is going wrong? Because I am successfully running both the subnet routing and exit node without any problem
[Magisk] RiriAndTheMen:
WireGuard app in the Play store has a root option already in the settings; you can switch to Kernel mode. However it does not work along with another VPN (in my experience). You will get errors when starting another VPN (which makes sense as they overlap).
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] sergey1977:
is there any support for vilte ? volte works
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] mati5000:
This forum is dead :) Even if it can run, no one will help you.
[Magisk] alfanveykov:
Magisk Autoboot​

This repository contains a Magisk module designed to enable automatic booting of your Android device when it's connected to a charger or USB.

Requirements​

Before you can use this Magisk module, you need to ensure that:

Android device rooted with Magisk.

Basic command line knowledge for module management.

Backup of your boot.img to restore in case of issues.

Installation​

Download the latest zip file from the Releases page.

Install the downloaded zip file using Magisk App/TWRP.

Power off your phone.

After installation, your Android will boot automatically on cable connected.

Usage​

This module adds autoboot.init.rc and autoboot.sh to the boot image. The patching process can be viewed in scripts/boot_patch.sh. The scripts folder is obtained from the installed Magisk on Android in the /data/adb/magisk folder. Only some necessary code is imported and then modified for patching boot.img.

In the autoboot.sh file, MIN_CAPACITY=5 is set as the minimum battery percentage threshold before Android boots automatically. If your battery percentage is below 5, the device will wait until it reaches this threshold before booting automatically. If you need to adjust this threshold, change the MIN_CAPACITY value in the autoboot.sh file and reflash this module.

In case of any errors, your current boot image is backed up under /data/adb/modules/magisk-autoboot/AutoBoot-Backup. If something happens, you can safely restore them.

Troubleshooting​

If you encounter any issues while using this module, follow these steps:

Check if your current boot image is backed up under /data/adb/modules/magisk-autoboot/AutoBoot-Backup. If it is, try restoring it.

Confirm successful installation by checking the presence of the autoboot.sh file in the directory outputted by the magisk --path command, usually /debug_ramdisk or /sbin.

If you continue to experience issues, please raise an issue in the repository with a detailed description of the problem, steps to reproduce it, and any error messages you are seeing.

Disclaimer​

This module is provided "as is" without warranty of any kind, either express or implied, including without limitation any warranties of merchantability, fitness for a particular purpose, and non-infringement. The entire risk as to the quality and performance of the module is with you. Should the module prove defective, you assume the cost of all necessary servicing, repair, or correction.

Tested Devices​

The patch has been successfully tested on the following devices:

Redmi 4X running Android 10

Samsung J3 (2016) running Android 7.1.2

Redmi Note 11 (spesn) Android 13

Links​

Here are some useful links for further reading:

Magisk Details

Lineage OS Auto Boot on Charge Connected

How to Change Files in the Boot Image Using Magisk

Credits​

John Wu & Contributors. for The Magic Mask for Android

bnsmb for the guides at xdaforums.com

tparaizo for the guides at xdaforums.com

License​

This project is licensed under the MIT License.
[Magisk] ln13ln13:
Does not work on my One Plus 8 Pro with Android 13. Does not seem to do anything. I installed via Magisk and have the autoboot.sh in my debug_ramdisk.
[Magisk] alfanveykov:
The init.autoboot.rc is executing autoboot.sh at charger connected.

on charger
exec u:r:magisk:s0 -- /system/bin/sh ${MAGISKTMP}/autoboot.sh 000

You can try execute manual with sh /debug_ramdisk/autoboot.sh, if it working ( your device reboot ) then something cause code can't run properly.

If not working you may modify and see what actually happen with the code.

save this code below to a new file, and execute it manual.

#!/system/bin/sh

CAPACITY=$(cat /sys/class/power_supply/battery/capacity)
MIN_CAPACITY=5
if [ $CAPACITY -gt $MIN_CAPACITY ]
then
echo "CURRENT BATTERY CAPACITY ($CAPACITY) IS GREATHER THAN MIN_CAPACITY ($MIN_CAPACITY)"
echo "REBOOT NOW IN 1 SECOND"
sleep 1
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"

else
while [[ $CAPACITY -le $MIN_CAPACITY ]]; do
echo "BATTERY CAPACITY ($CAPACITY) IS LESS THAN MINIMUM OR EQUAL ($MIN_CAPACITY)"
echo "SLEEPING 60 SECOND"
sleep 60
CAPACITY=$(cat /sys/class/power_supply/battery/capacity)
if [ $CAPACITY -gt $MIN_CAPACITY ]
then
echo "CURRENT BATTERY CAPACITY ($CAPACITY) IS GREATHER THAN MIN_CAPACITY ($MIN_CAPACITY)"
echo "REBOOT NOW IN 1 SECOND"
sleep 1
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
fi
done
fi
[Magisk] ln13ln13:
It works when I run manually as root from terminal, but is not triggered when power is connected. It does not work if I try running wirhout being root in terminal
[Magisk] alfanveykov:
Apologize me, I dont give the simple version of autoboot.rc ( in this case, autoboot without sh script ), I should create a separate zip file for that, but i dont.

Can you do manual patching ?

GitHub - anasfanani/magisk-autoboot: a Magisk module to enable automatic booting/for turning on of your Android device when it's connected to a charger or USB.

a Magisk module to enable automatic booting/for turning on of your Android device when it's connected to a charger or USB. - anasfanani/magisk-autoboot

github.com

With adb, you can easily copy and paste command.

But if you can't do manual, for now I can't help you, because I'm on other job, next time I will add simple autoboot zip.
[Magisk] ln13ln13:
Ok, thanks.
[Magisk] ln13ln13:
Finally got it to work! I guess we need a different different mod for the init.rc for OnePlus 8 on Android 13. The one that worked for me me is here:

android-autoboot/autoboot.op8t12.rc at master · hasanbulat/android-autoboot

Auto boot android devices on charging . Contribute to hasanbulat/android-autoboot development by creating an account on GitHub.

github.com

I used the simple method you describe and reference but replaced the autoboot.init.rc with the file in the above link.
[Magisk] AlmightyZ01:
The module is not working on my HTC one A9 , Android 7.0.

The module is installed successfully with the latest Magsik but when I turn the phone off nothing happen.

Any idea ??

Edit: I checked for "autoboot.sh" in sbin but it is not found
[Magisk] alfanveykov:
Try modify the init rc file, change on charger with one of this.

on property:sys.boot_from_charger_mode=1

on property:ro.bootmode=charger

My planning is create an automated test for detect which init.rc value is work, but right now I doesnt have enough info for that, I'm still learning.
[Magisk] rik-shaw:
To clarify, if a usb power cable is already connected but not powered, then it gets power will the device boot? I am looking for a solution to have a tablet in a car permanently connected to a usb power cable and have the tablet boot when the car is started.
[Magisk] ln13ln13:
Yes. That is what I do.
[Magisk] steven@:
Working perfect with Samsung galaxy S10e(SM-G970N) + Android 13 + LineageOS 20 :)

Even wireless charging support too!

Nice work ;)
[Magisk] r_musthofa:
I get some problem when autoboot run normally. One time my phone bootloped, it was able to enter fastboot or EDL mode in 3 seconds then still restarted at the Mi logo. I forgot not to back up the boot.img file. Can you help me solve that problem, thank you
[General Topics] bluesky3943:
This is one glitchy device and getting notifications in time is a complete lottery. Just recommend you don't get this device. Just one question when I go to background power consumption management it displays 7 Facebooks for some weird reason. Does anyone know why this is?
[Magisk] alfanveykov:
Adb-Root-Enabler​

Description​

Enable unauthenticated adb daemon, useful for devices with a broken screen!

Installation​

To install Adb-Root-Enabler, you must have Magisk installed on your Android device. If you don't have it, you can find installation instructions for Magisk here.

Follow the steps below to install Adb-Root-Enabler:

Download the latest release from the following link: Adb-Root-Enabler-1.2-mtp.zip.

Boot your device into TWRP (Team Win Recovery Project) custom recovery mode.

In TWRP, select "Install" and navigate to the downloaded Adb-Root-Enabler-1.2-mtp.zip file.

Swipe to confirm the installation.

Once the installation is complete, reboot your device.

Alternatively, you can use the following command to install Adb-Root-Enabler via TWRP:

twrp install Adb-Root-Enabler-1.2-mtp.zip

After installation, the Adb daemon will be enabled without requiring authentication, making it useful for devices with a broken screen.

Please note that modifying your device with root access can void your warranty and may lead to potential risks. Proceed with caution and make sure you understand the consequences of rooting your device.

Disclaimer​

This software is provided "as is" and without any warranty. The author and contributors shall not be liable for any damages caused by the use of this software. Use it at your own risk.

Copyright​

© 2023- lexavey

© 2023- Topjohnwu & Authors for Magisk
[General Questions and Answers] will734:
Now i can't enter system ! how should i do ? sp flash tool reflash rom or flash what .img in boot-loader ?
[LG V30 Questions & Answers] mgoat:
Hi. Hope I'm posting this to the right place:

I'd like to know where I am in the process of installing a LineageOS on my Verizon v30, and where to go from here. I have been diligently trying to follow along the XDA instructions (thank you very much!) but am finding it very confusing (and many links dead). I have installed LOS on two other phones, but that was over a year ago, so quite rusty.

I believe the phone has been rooted as I get the dire warning at boot up. The phone boots up normally then.

I have the TWRP app and MAGISK installed.

About phone shows:

Software version US99820b

Android version 8.0.0

Kernel version 4.4.78

Build number OPR1.170623.026

Security software version MDF v3.1 Release 2

I did try to flash a "joan" ROM but that ended up with a bootloop that I cured. But if I open a terminal session on it I see "joan:/ $"

(does not jibe with "Software version US99820b, right?)

This phone has been retired to being just a music server on my internal WiFi. That's all I need it to do. I decided to try a LineageOS because I have some experience with them and wanted to have the latest and greatest software installed for this platform (I'm also retired from 25 years in IT, so...)

I think I need to figure out if the firmware, etc. is up to date and working properly, and how to proceed with getting the latest LineageOS ROM on it, whatever that is, it's not clear for this phone.

Much thanks, to the devs who made rooting these phones possible and those who hang here supporting them.
[Vivo X90 Pro Plus] MarkezG:
First of all, forgive my English.

A friend has a Vivo X90 pro and when recording a video it doesn't let him select the zoom dial or change the lens. Do you know if there is a solution?

If you record at 4K in 30 or 1080p you can do the clamp gesture but at 60 fps it won't let you do it.

It seems strange to me that no one has commented on it. I have used the search engine with keywords and I have not found anything.
[Vivo X90 Pro Plus] Bl3s:
From my experience in 4k 60 you can only zoom in and out on the lens to start recording with, you can't switch lenses.
[Vivo X90 Pro Plus] virtualknowledge:
I believe it's available only in Google pixel phones switching from one lens to another while recording 4k 60. It's available only for 30fps in Vivo unfortunately.
[Vivo X90 Pro Plus] Bl3s:
X100p can do this as well, so there's a chance we will get it with software update as x90p/pp definitely has the hardware capable enough of doing this.
[Vivo X90 Pro Plus] virtualknowledge:
Wow. Didn't know that.

I really would like to receive it. If Google can achieve with that tensor chip why other brands are not doing it.
[Redmi Note 12 Pro / Pro Plus 5G] hyperefe:
Hey, does anybody know if there is any pen that can be used with the redmi note 12 pro? I mean a pen with palm rejection for taking few notes, not those one to use as a finger. Thanks!
[General Questions and Answers] mastanbaa1:
I installed googledriver to command prompt, now i am getting 2 prompt command,?
[General Questions and Answers] Renate:
You mean that you have installed Google's driver for ADB and now you can access a command shell through ADB?
[General Questions and Answers] mastanbaa1:
Yes
[General Questions and Answers] Renate:
Sounds good. What do you do next?
[Moto G30] TwinTurb000:
hi, 1 year ago i put a GSI on my moto G30 (ArrowOS), but now i need to go back to stock rom because of banks apps that i need to install so i can work...

but the problem is that i ins't the most experience guy doing this kinda of stuff, so i dont know how to start the process to flash the stock rom again...

i would really apreciate if someone have a tutorial, like yt videos, that explain how to flash the stock rom again... because i really need to use thoses apps.
[Moto G30] michael_hamada:
If you have a PC, use Lenovo's Rescue and Smart Assistant.

All you need is Windows PC, reliable USB cable, internet connection and IMEI of your device.

You can download it from below. https://download.lenovo.com/consumer/mobiles/rescue_and_smart_assistant_v6.7.3.19_prod_setup.exe.

No need for tutorial. This app would guide you well.