yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 8 Questions and Answers] nobtiba:
Hello everyone,

I am attempting to make my app display in full screen on an external screen, which requires me to use Odin to upgrade my Note 8 to Android 12. Without this upgrade, I can only update my OS to Android 9, where some windows can be maximized in Dex mode but not all. On my Note 10+ running Android 12, I can use the same app in full screen on Dex mode. Therefore, I opted to use lineage-19.1-20231009-UNOFFICIAL-greatlte to install Android 12 on my Note 8.

Unfortunately, after upgrading, whenever I connect my Note 8 to the Samsung Dex station, the mirror screen on the external monitor flickers and glitches rapidly. Sometimes, the phone even freezes or resets itself. Before upgrading to Android 12, I could use Dex mode to display full screen on the external monitor without any issues (except for the full windows problem with some apps). However, now I cannot even achieve full screen on the external monitor and can only see the mirror screen flickering and being unstable.

I have attempted to disable HW overlays by going into: Setting\System\Developer options\Hardware accelerated rendering\Disable HW overlays, but this function is not toggleable and does not solve the issue. I have also downloaded SecondScreen and Taskbar apps, but I cannot try them out due to the phone's flickering and unstable behavior when connected to the external screen. Additionally, I do not believe these apps can help turn the mirror screen into full screen.

My ultimate goal is to have my app open in full screen on the external monitor. Could someone give some advises or your experiences regarding this please? Thank you!
[Samsung Galaxy Note 8 Questions and Answers] nobtiba:
I found myself an alternative solution: install Android and Playstore for my Raspberry Pi 3.
[Touch Pro, Fuze ROM Development] merten3000:
I'm cooking a localised ROM (DUTCH) build 20931 (and in the future 20954).

I got ROM up and running quite smotely as i may say BUT....

2 problems I really do not understand:

1) I always used the same package "FInixNOverBattery". I didn't change a thing in the package but somehow it shows the original battery icon again...

2) Kinda the same thing happened with the enlarged system status. Ever since I used the baserom 1.95.502.5 it does not show anymore. I already checked registry and touchflo settings and it should be enabled. But I still get 'normal' popups when I hit volume/reception/etc and not the enlarged one which you have to choose again from

somebody got a sollution?

Thanx in advance....

Greetz Merten3000
[Touch Pro, Fuze ROM Development] pfcsabre:
1) FInixNOverBattery needs it's SDKCerts to work. Cook the registry settings and it will work. You may also want to remove the phcanoverbmp in your phone canvas.

2) Do you have the EnlargeStartMenu cooked? :rolleyes: You also need one from the Blackstone build.
[Touch Pro, Fuze ROM Development] pfcsabre:
Just cook it with the rest. Add the registry to any .rgu file and the xml to any .provxml file. Do not create one as for some reason the .provxml will not be executed. Validate your .provxml file afterwards (open it in IE or FF-- sohuld show a valid xml).
[Touch Pro, Fuze ROM Development] merten3000:
Damn did it all but no luck....still the same old battery indicator
[Touch Pro, Fuze ROM Development] pfcsabre:
try putting it in mxipupdate_oemoperators_100.provxml at the very beginning.. not at the end ;)
[Touch Pro, Fuze ROM Development] Da_G:
just an fyi, you dont need certs for stuff that's cooked in, ROM files are automagically trusted.. so look elsewhere for the issue with this loading.
[Touch Pro, Fuze ROM Development] pfcsabre:
I don't know that :D well he may have duplicate phcanoverbmp and BuildOS is overwritting it :) Merten, try renaming your battery icon to another dll and point

[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]

"BaseDll"="<name of your dll>"
[Touch Pro, Fuze ROM Development] merten3000:
You have been a great help....I appreciate it!!

Keep up the good work!
[Touch Pro, Fuze ROM Development] karloe:
Glad to see You back and testing... :D

If You are in need of a beta tester, I'll be available once more :eek:

(but not before Monday afternoon, can't have the gf unhappy :rolleyes: )
[OnePlus Open] the_rebel:
My past about 5 phones were from Xiaomi. Decided to change that and got the OP Open this time. I love this phone and the clean OxygenOS, but I have been using these shortcuts for many years now:

1) Long Press Recents: Lock Screen (works from anywhere)

2) Long Press Back Button: Kill Current App (also works from anywhere)

Could someone pls suggest a way to make these work work in OP Open? (I am rooted)

(Request you to not reply with a 'why you need to kill app' or 'Use X way to lock screen instead' - I'm just trying to not overwrite years of muscle memory that are actually quite efficient shortcuts, but apparently aren't available in this phone)
[OnePlus Open] BoundsChecking:
Give Fluid Navigation Gestures a try - you can customize them to do all of things you mentioned I am pretty certain.
[OnePlus Open] the_rebel:
Nice app! I tried it out and really like it - I really wish it recognised folding screens though, so that it could change the trigger position based on nav button position changing

But since it's not been in active development in about 5 years, I don't have hope for that happening
[OnePlus Open] the_rebel:
Solved this problem with Tasker. Created a navbar button that:

- Locks screen on single tap

- Kills active app on long press

Been using it since this morning and I love this experience and it's much better than FNG for my use case.

(See lower right corner)

View attachment 6035356
[Samsung Galaxy S23 Ultra] superspartan:
I could've sworn I was able to quickly tap the small dot which shows the zoom (ie. 1X) and change it to another zoom level like 3x or 10X) while recording a video live.

I can no longer see that option, I only see the 4 zoom levels before starting to record the video then when I start recording, tapping that icon does nothing. I can pinch to zoom with my fingers but that it not convenient.

I am on Android 14/OneUI 6 and using the Camera assistant. Is there a setting that I might have accidentally activated that causes this?
[Samsung Galaxy S23 Ultra] x3nuqi:
You can only switch lenses whilst recording in modes listed below;

4K30FPS

1080P 60-30 FPS.

For 4K60FPS and above you would have to resort to digital zoom, which isnt bad at all up until 4x from what I've tested so far.
[Samsung Galaxy S23 Ultra] xwonic:
You are probably selecting 8k meaning its stuck on the 200mp lens since its the only 8k supported lens. Same thing for 200mp photo where you actually use a 2x binned and a 3x and 4x digital/hybrid zoom
[Samsung Galaxy S23 Ultra] superspartan:
Thanks! It was on 4K 60 FPS, all sorted now! cheers
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] UglyStuff:
Hi everyone,

I don't know if it's a bug in MIUI 14 or just that I haven't found the right setting to toggle, but with AOD enabled (for 10 measly seconds... Don't get me started...), and regardless of the launcher I'm using at the moment, once the screen is locked, there are no notifications for missed calls or incoming texts.

Like, at all.

I made sure DND wasn't enabled (the phone is on Silent, that's it), and I've chosen the myriad colorful dots option in the animation list, but regardless, I'm still not being notified when a text arrives or if I've missed a call while I wasn't looking at my phone for some reason.

What am I missing here? 🤔
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] katoda_ltd:
I was playing with notification options and I failed. The most what I was able to achieve was displaying a notification at the moment of an event, then the screen goes off and that's all. Not possible to check what was happening without waking up the phone or activation AOD display to see notifications.
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] UglyStuff:
We're on the same boat. Nothing works as it should: no persistent notifications of any kind, which means you have to wake your phone at regular intervals to check for missed calls or texts... 😑

Back in the day, there was an app called (if memory serves) NoLED, which I installed on my girlfriend's phone because it didn't have a dedicated LED for notifications, and it worked like a charm. True, it would suck the life out of your battery at a rather fast pace, but still, it was doing the job.

I can't find it on the Play Store anymore, so I suppose it's gone or deprecated on Android 13.

Do you know any good third-party alternatives?

I've read an article online recently about an app that draws color circles around the front camera when you have received a text or missed a call, but I can't for the life of me remember its name.
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] katoda_ltd:
I remember some discussions on Reddit on this issue. They mentioned two apps used to somehow overcome this limitation:

Missed Notifications Reminder for audible notifications

NotifyBuddy - Notification LED for visual notifications
[Android Q&A, Help & Troubleshooting] en11gma:
i have T-Mobile Galaxy S21 Ultra (SM-G998U on WK1 Official Stock).

i have no "disable child process restrictions"

i have ""disable app compatibility policies" as its in same place as "disable child process restrictions" was in the video guide.

i get black screen when i follow the guide.
[Thinkpad Tablet General] Octosc:
I have a 50 - Lenovo M9 tablets.

I have rooted one of them, installed a script that basically boots the tablet off if the charger has been disconnected.

My question; How can I easily flash "everything" over to the 50 other Lenovo M9 tablets in the easiest way possible, including the root and script/files/apps - basically all in one solution? Are there any nice ways to do that?

I would prefer if I could avoid rooting and doing everything manually on each device!
[Thinkpad Tablet General] V0latyle:
Doing this on Windows is pretty easy using something like Clonezilla

I have no idea how to do it on Android, however. I do know that with root access on your "source" device you can dump partitions, and you should be able to flash those partition images to the corresponding partitions on your target devices (provided the bootloader is unlocked).

Assuming they're all running the same firmware, and you initially rooted by patching the boot image with Magisk, you could easily flash /boot with the same boot image you initially patched.

As for copying /data...Not sure how well this would work. Back in the CWM and early TWRP days we could create Nandroid backups but AFAIK you can't just write the /data image from one device to another without a whole host of problems. At the very least, all 50 targets would need to be a clean installation.

It's worth a shot at least. Use TWRP to create a Nandroid backup of /data on your source device, then export that backup and restore it using TWRP on a target device.
[Thinkpad Tablet General] Octosc:
Pretty sure that it would defeat the purpose of it if I have to use a rooted service on all 50 devices, i would have to manually root them all. (TWRP)
[Thinkpad Tablet General] V0latyle:
TWRP =/= root, but I don't think you'd have any way to restore /data otherwise.
[OnePlus 7 Pro Guides, News, & Discussion] naeem47:
OnePlus 7 pro volte

#root needed

1.download and install latest Qualcomm driver

2.download and install QPST 2.7.496

3.Download and install OnePlus USB driver

4.download and install adb setup 1.3 .

Go to PC

1.open command prompt

2.type adb devices ...shows device id

3.type adb shell

4.tupe su (phone asked superuser permission grant it)

5.then type- setprop sys.usb.config diag,serial_cdev,rmnet,adb

6.open pdc tool in cdrive. My PC/cdrive/Qualcomm/QPST/BIN/PDC

7.PDC tools detect your device.

8.now change your carrier mbns.

9.choose carrier..sub0 is for sim 1 and sub1 is for sim 2..

8..pdc tool click active .... Wait few minutes then your volte icon will appear..if not change another mbns carrier and try again.

Tested on OnePlus 7 pro

Oos 10,11,12. Cos12
[OnePlus 7 Pro Guides, News, & Discussion] ZG_DEV:
Thanks for the great guide !
[OnePlus 7 Pro Guides, News, & Discussion] naeem47:
View attachment 6035148View attachment 6035149View attachment 6035150View attachment 6035151
[OnePlus 7 Pro Guides, News, & Discussion] ZG_DEV:
I see that you were trying to show some attached images, why don't you attach them to the OP ?
[Google Pixel 6 Pro] dj-luke:
Hello I have a problem and it is that I just rooted my pixel 6pro and it turns out that the whatsapp tells me that I need the official application to verify my number, using magisk and safetynet fix and playintegrity fix the problem still persists, I installed Android 14 keeping the booloader unlock and the problem with the whatsapp followed but when reinstalling Android 14 with bootloader lock if the whatsapp works, Does this happen to anyone else?
[Google Pixel 6 Pro] GROOVYJOSHCLARK:
I'm 100% ROOT'd and use WhatsApp all day long, in a group chat with my two kids and ex-wife. Open magisk, go to settings, enable denylist, find and add WhatsApp. A13 though but at far as I in understand Whatsapp check, this should solve it regardless of android (but I could be wrong). I refuse A14 until LOS so I can't confirm 100% it will work but definitely try to deny root to WhatsApp and let us know:

View attachment 6035163
[Google Pixel 6 Pro] dj-luke:
If I had that done, I was on Android 13 when I rooted and I had Magisk with WhatsApp, Play Store and Play Services on the denial list but it didn't work for me and it asked me to use the official application, and it is the one I had installed
[Google Pixel 6 Pro] majorfigjam:
Have you installed Shamiko? I have WhatsApp on rooted A14, with it listed in the Deny List (not enforced obviously with Shamiko running), and it works fine.
[Google Pixel 6 Pro] GROOVYJOSHCLARK:
It definitely checks out normal on my side, the only WhatsApp thing I ever get, is telling me that I'm using a custom ROM during initial opening but never again. I get that with LOS but that's just a heads up. It doesn't do anything to WhatsApp and I always get it.

Does WhatsApp work for you at all, or it won't let you open it under android 14 with ROOT?
[Google Pixel 6 Pro] dj-luke:
When I have the bootloader unlock neither on Android 13 nor on Android 14 but I do have the bootloader lock if it lets me, in unlock WhatsApp tells me when I enter the phone number that I need to install the official application and it no longer lets me do anything else
[Google Pixel 6 Pro] dj-luke:
shamiko is for banking applications, right?
[Google Pixel 6 Pro] Zaxx32:
Wierd...no probs, rooted 13 or 14. Dunno it'd help but try installing the latest lsposed core patch and/or the Pixel Expert mod, it has an option to bypass sig checking for 5 mins while you're installing. U shouldn't 'need' but maybe it'll help...good luck!
[Google Pixel 6 Pro] majorfigjam:
Shamiko is for hiding root from any application that may be affected by root, not just for banking apps.
[Google Pixel 6 Pro] dj-luke:
with shamiko the error persistsView attachment 6035367
[Google Pixel 6 Pro] Strephon Alkhalikoi:
The OP's error message is that WhatsApp itself has been modified. Since all of you are rooted and none of you except the OP get this error message, logically the issue is the OP's app, not the phone nor root. So OP, remove your existing copy of WhatsApp and replace it with a fresh unmodified copy from the Play Store. Then try again. If it works then the issue was the copy of the app you had on the device. If it doesn't, then something in your setup OTHER than root is causing it.
[Google Pixel 6 Pro] dj-luke:
I do not have modified WhatsApp, I have official WhatsApp, if the bootloader is unlocked I get the verification error telling me that I have to install the official version but if I have the bootloader lock the WhatsApp works fine
[Google Pixel 6 Pro] dj-luke:
Yes i have shamiko installed, the bank aplications work fine
[Google Pixel 6 Pro] dj-luke:
View attachment 6035492I try to restore everything with flash-all and it gives me this error
[Google Pixel 6 Pro] majorfigjam:
I saw that error a while back.

Be sure to use the latest platforrm tools 34.0.5, or maybe pixel flasher as an alternative.
[Google Pixel 6 Pro] dj-luke:
That's what I did, I had outdated platform-tools, but in order to have WhatsApp I had to link the account with another old phone I had
[Google Pixel 6 Pro] Nergal di Cuthah:
Fwiw

I'm rooted (magisk canary 26.4) on 14, only have PIF and systemless hosts. Whatsapp works fine no complaints biometrics enabled.

What other modules, plugins, lsposed do you have.

I feel like part of your answer will be LP but I'll wait and see your answer.
[Google Pixel 6 Pro] dj-luke:
I had SafetyNet, PlayIntegrity and Shamiko, I don't know which else can be used anymore I'm a newbie to this
[Google Pixel 6 Pro] Nergal di Cuthah:
Are you using usnf and pif concurrently? Only use pif, safety net fix is broken.

You have no lsposed? No overlays? No whatsapp affecting modules?
[Google Pixel 6 Pro] dj-luke:
I tried one by one and today I tried Magisk Delta and it doesn't work for me either
[Google Pixel 6 Pro] sieger007:
did both . YASNAC says ok for both levels and root is hidden ( AFAIK ) cos whatapp will just quit - no questions asked if root was exposed. I am using Kitsune 26.4 that uses whitelist approach. So its hidden default. This has something to do with your having 1) used a modded WA in past ( ;course I was forced to change & I did > 1 year ago ) and then 2) wanting to migrate 3) whilst wanting to , do 2) ....something triggers the migration module ( consider Phones P1 P2 P3 P4

P1 : Original Phone that I had to reflash due to some issues Thats where WA was intended. and now I am greeted by Ugly Official WA bouncer . Rooted b/l Unlocked Stock 2) P2 : just moved /data/data/com.whatsapp folder with correct chown & WA started right away no hassles . P2 : GSI + b/l unlocked + root P3) test phone b/l locked & stock : Login Poss p4) P3) test phone b/l UNlocked & stock : Login Poss
[Google Pixel 6 Pro] turhvjbufv:
Try to use bootloader spoofer (only on Whatsapp) and don't forget to clean data when tryin gto login again
[Google Pixel 6 Pro] wizzeteren:
IT WORKS PERFECTLY, THE MOST USEFUL ARTICLE I'VE EVER SEEN IN MY LIFE AQ BUT I DON'T WANT TO INSTALL ANOTHER KEREL, SO I THINK KERNELSU IS GARBAGE BUT I WILL TRY IT WITH MAGISK TOO. HAVE A GOOD DAY.
[Google Pixel 6 Pro] turhvjbufv:
Use it with kitsune magisk, if you are using a14 ROM flash kitsune prerelease
[Google Pixel 6 Pro] CanerKaraca:
KernelSU is not garbage, it's best root solution in my opinion.

But if you too lazy to change kernel, i recommend APatch instead of Magisk or Kitsune Mask.
[Google Pixel 6 Pro] turhvjbufv:
Patch much better than ksu(at least in root hiding and modules, since it can use both ksu and magisk modules)
[Google Pixel 6 Pro] k41th1ng5:
Did it work???
[Google Pixel 6 Pro] wizzeteren:
Yes for me works I even installed WhatsApp Plus on it with Corepatch.
[Google Pixel 6 Pro] sieger007:
unfortunately I found out to my utter dismay that my kernel is closed source .I cannot get the source code for my kernel the manufacturer 's a cheap Chinese company aka cc company that does not even bother to respond to emails but I found several phones with the exact same SoC and one of them could have an open source kernel. WRT the fact that KernelSu on Non GKI cannot be compiled unless and until you have the source code for the kernel

where do I go for here for my phone I'm still stuck. should I use the kernel of another similar phone and hope for the best ?

what's corepatch is it part of that lucky patcher or something else
[Google Pixel 6 Pro] wizzeteren:
I didn't understand much of what you said, but I can explain Corepatch. Corepatch is an lsposed mod that disables the Android APK verification process, thanks to which you can downgrade applications without deleting them.Or you can install a modded application over the original application like I did.
[Google Pixel 6 Pro] wizzeteren:
Changing the kernel is easy, but it caused heating problems on the device and even touch zoom was not working🤔
[Google Pixel 6 Pro] brunoaduarte:
app/custom-rom doesn't mean WhatsApp detected a custom rom, it only means WhatsApp executed the custom rom check routine.

If a custom rom was detected you would see something like app/custom-rom debug or a custom rom name like app/custom-rom xdandroid and that would trigger a custom rom warning popup in WhatsApp screen.

I have a device with factory settings, locked bootloader, official rom, non rooted, etc, and WhatsApp displays this log message. It's perfectly normal and expected. Don't worry about app/custom-rom
[Google Pixel 6 Pro] sieger007:
stuck between rock n hard place cos my target phone is a cheap chinese one that has hardly a thread or 2 on XDA - so now TWRP / root and traditional magisk "hider" mods

# Rhetoric Begins

This WA is a POS. I have to keep this garbage pile running ( FP all over the s/w of $100k + salaried clerks who do nothing but impose policies ) cos my groups and conversations are in there. But its time we get our act together and move to alternatives like TG even if it means viral vids of people loosing their $ & 📲📶 on WA & WA is a dangerous, predatory env that will steal your info.

# End of Rhetoric

Coming to facts

-- well, .... hmm then anyway to know what triggered that ugly offical rom bouncer by seeing the logs

-- I am upto my neck with this getting me nowhere. magisk mods that "hide stuff" aren't working the way they should. I installed a bunch of these . I can get it to run on unlocked b/l + stock which means that b/l status is not an issue ...& if it detects root it quits ...

So I assumed it has to be my Cust ROM but just then.. I get the same bouncer to come to a rooted stock ROM ( b/l unlocked )

with magisk failing ....

- I looked around : KernsSu : my target phone is a CC cheap chinese type that hasn;t made its code public ( & there's no root guide or twrp for this one ) so without kernel source I cant compile this . I dunno should I look for similar SoC phones ?

-- Apatch : get segmentation error using manager apk while patching boot.img and so tried it on my Linux another weird bunch of errors
[Google Pixel 6 Pro] Farrukhi:
Thank you for sharing this hack with us.

Can you please guide help me with this somehow?

So first. I have to install KernelSu modules, right from their website, right?

Second. Where do I have to get LSPosed Bootloadersper?
[Google Pixel 6 Pro] sieger007:
I can't take this approach because kernel source for my phone isn't available ..... for non GKI ROM you have to compile kernel oukitel wp15 ..... any hope ?
[Google Pixel 6 Pro] Farrukhi:
I've just realized that my bootloader was unlocked. Could it be a reason for banning my acc?

And can I still use the method described above with kernelSU and LSPosed Bootloadersper?
[Google Pixel 6 Pro] protunez123:
How to implement this using kernelsu
[Google Pixel 6 Pro] Nergal di Cuthah:
Clear whatsapp data?
[Google Pixel 6 Pro] dj-luke:
I've deleted data from WhatsApp, Play Store and everything remains the same
[Google Pixel 6 Pro] Nergal di Cuthah:
There's got to be something that doesn't work on yours but works on mine. What version of PIF are you using, if not using v13+ that maybe your issue, do you pass play integrity?
[Google Pixel 6 Pro] dj-luke:
The PIF version is 13.7 and I just looked at the Play Store and it's not certified

the pif version 13.8 and with 13.7 and 13.4 the same thing happened to me
[Google Pixel 6 Pro] Nergal di Cuthah:
Ok the first thing is to get you passing Play Integrity and certified playstore.

That, i can 99% guarantee is what's different between our two devices.
[Google Pixel 6 Pro] dj-luke:
before going to bed I'm going to install the evo rom and test without magisk if the play store is certified
[Google Pixel 6 Pro] dj-luke:
Well, I installed the evo rom and I installed magisk and pif 13.8 and the play store shows me not certified
[Google Pixel 6 Pro] Nergal di Cuthah:
Probably the custom rom, not sure why you switched rom from stock,that makes likely different problems