yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] boxster03:
@blodgettmike You are right about not being able to click OK with remote after selecting a key from the remote (I thought second click is for OK but it keeps changing the selected button instead) and have to use scrcpy or keyboard etc. to OK it.

(It still remains those buttons can't be selected on OS 7.2.9.2)
[Fire TV Original Android Development] boxster03:
@cityhunter_1919_xyz , @Pro-me3us So what is the benefit in going through Xposed Edge for remap app ? I just remapped disney and hulu buttons this way and noticed a short delay with a blank screen when I press those buttons. remap app works on its own so why involve XPosed Edge?
[Fire TV Original Android Development] ooftymcgoofty:
Yes, i am on a later version. Thought I would mention it since it took a couple minutes for me to realize. Good luck!
[Fire TV Original Android Development] ooftymcgoofty:
Well, I told myself I would re-read this thread before I do something stupid, but I did not. Yesterday I updated magisk to 26101 and have lost twrp. Still have root through magisk. Should I just be content with having a rooted cube 2 (on 7624/3337)? Would trying to flash twrp and magisk in flashboot result in certain death?
[Fire TV Original Android Development] Pro-me3us:
No I would reflash TWRP. You usually only lose TWRP if you forget to re-flash Magisk immediately after flashing a firmware bin in TWRP. Also if you update Magisk, I would stay off the canary build line, these are pre beta builds that can have issues. Go into Magisk Manager settings / down to APP / and change Update Channel to Stable. It's on Canary by default because the build I include with the bootloader unlock script is a canary build.

To reflash TWRP, you can do it from ADB. Assuming you still have the bootloader unlock files in /data/local/tmp/, the TWRP image is still there:

dd if=/data/local/tmp/twrp.img of=/dev/block/recovery

Or if you prefer, you can reboot to fastboot to flash it with the command fastboot flash recovery twrp.img.

Then you need to figure out why TWRP was deleted, if it was just because you forgot to reflash Magisk immediately after updating to PS7624, in TWRP, you will be fine. You can reboot the Cube once to FireOS, then reboot to TWRP to verify that it's still there.

If you ever boot FireOS without a magisk patched boot image, like after a firmware upgrade for example, when the boot image has been updated, FireOS will detect a change to recovery and delete TWRP. Magisk normally prevents this.

If there really is an issue with Magisk 26.101 not preserving TWRP you should downgrade to Magisk 26.1, I know it works properly on the stable build.
[Fire TV Original Android Development] Pro-me3us:
If you are only interested in remapping the app buttons, and only those app buttons what are not system apps, then the remap apps will do the job. However, I think Amazon has blocked the remap apps from working on the newest FireOS versions. I'm not sure if that change only happened starting in PS7624/3337. That change again could be related to why it's possible to blank out the app buttons and remap them in Xposed in PS7624 but not PS7292.

Xposed Edge has the advantage of allowing A LOT more than just app button remapping. You can look at @supermutant2299's post on just a little what's possible with Xposed Edge in terms of mapping
[Fire TV Original Android Development] ooftymcgoofty:
Oh thanks again! I reflashed twrp and booted to os and all was fine. Rebooted to recovery a few times and twrp was fine. Yes, magisk was in canary-I changed it. I had rebooted to recovery plenty of times and made a backup prior to upgrading magisk, so I think the upgrade had something to do with it?-I did the upgrade from within magisk manager. Thank you!
[Fire TV Original Android Development] Pro-me3us:
Thanks for the confirmation. Maybe I should put out an update with Magisk v26.1 stable. That would set the update channel to stable by default. Since Magisk is blocking updates, double check that updates are still blocked after any Magisk update.

Not having TWRP installed isn't a problem. TWRP offers a layer of protection against accidental updates for Cubes that still have DFU access (bootloader unlocked before PS7273). On these devices an accidental OTA update would brick (and not update) the Cube because of TWRP, and DFU could be used to restore it.

Cubes that bootloader unlocked between PS7273 - PS7292, would just be bricked without a recovery option. If stock recovery is present, an accidental OTA update would just lead to permanent loss of root, and no brick, which is probably a better outcome.

I'm always thinking worst case scenario, but keeping updates blocked shouldn't be difficult, or something that you have to worry about often. Since the bootloader unlocking script also disables DM-verity, you could even delete the OTA app from the system folder. I don't like to edit the system partition, so I haven't made that recommendation.
[Fire TV Original Android Development] boxster03:
So the Cube has a speaker and a listening device/mic obviously. I'm not interested in using Alexa and wondering how to know if it is completely disabled and not constantly listening?

Also after unlock, is there a list/guide somewhere on how/what unnecessary background processes to disable and make the device more efficient?
[Fire TV Original Android Development] Pro-me3us:
I think amazon.speech.davs.davcservice is the app that listens for Alexa requests (through Cube and remote). It is an extension of the actual Alexa app (com.amazon.vizzini).

Because app functions and dependencies change over time, it's hard to make a concrete list. Disabling one app could cause another app to go haywire leading to high CPU usage and a slow down.

FireOS apps are mostly identical between FireTV models, so using one of the Stick lists as a template is ok. I would only disable a few apps at a time, reboot the Cube to make sure it still boots, and check the background processes to verify there are no obvious problems. If the Cube doesn't boot, use USB ADB to re-enable the apps.

Make use of top in adb, this program will show you all the running processes on the Cube, including RAM and CPU utilization. The Cube has 6 cores, so there is a total of 600%. Raven idles at ~520-540%, with ~60% dedicated to Alexa listening.

I use the CPU temp as a crude way to quickly check for problems. cat /sys/class/thermal/thermal_zone0/temp

Idle temp (520-540% CPU) is ~35000 (35C), playing 4k HDR video (400-450% CPU) is ~40000-48000 (40-48C). So something is obviously wrong if the temp is +55-60C, but top is a lot more informative.
[Fire TV Original Android Development] cityhunter_1919_xyz:
Recently, I got a brand new cube (2nd), but luckily it was a PS7206, so I was able to install Bootloader unlock and TWRP. With PS7206, the remote control with an app button was not possible, so I updated to PS7624 from TWRP and was able to pair successfully.

I used "blank_app_button.zip" from the magisk module, but since "key249-key253" in Vendor_0171_Product_0421.kl was blank, I couldn't use it as is. (I was able to use it safely by replacing it with a file in which an arbitrary key was entered in the blank part.)

Thanks to that, I can enjoy cube.
[Fire TV Original Android Development] Pro-me3us:
Thanks to @roligov for providing the data needed to get shrinker working on PS7206. I wasn't sure anyone would actually need it

Let me know if anyone comes across even older 2nd gen Cubes with PS7204 or PS7202 and those can be made to work too 😁
[Fire TV Original Android Development] boxster03:
@cityhunter_1919_xyz You are lucky indeed. Where did you find a brand new Cube 2 ?
[Fire TV Original Android Development] cityhunter_1919_xyz:
Until recently, it was sold for 5,500 yen in inventory on a Japanese electronics website.
[Fire TV Original Android Development] Joejohnson1:
Is anybody having a problem with the appstore crashing everytime you go to search after doing this?

Any ideas on how to fix it?
[Fire TV Original Android Development] Pro-me3us:
You are using a custom launcher?

Search in the App Store depends on the Amazon Launcher, and doesn't work when Amazon Launcher is disabled.

There are a few solutions to this

1) Re-enable the Amazon Launcher (easily done with Launcher Manager) any time you need to search the App Store, or use any Amazon Launcher dependent services.

2) Use bootless Magisk to specifically disable the home screen function of the Amazon Launcher, keeping the rest of the package active/working. Magisk is only temporarily needed for this, it can then be disabled/removed.

3) Use full Magisk (requires bootloader unlock method), to set your custom launcher as the default, and keep Amazon Launcher fully active, letting you visit it with an icon on your homescreen like it's just another app.
[Fire TV Original Android Development] Joejohnson1:
Thanks that worked!

I have one more question.

I set my firecube to put up a black screensaver after like 30 seconds of inactivity to expand the life of my oled tv, but everytime it pops up there’s a little text box at the bottom right saying “press x for screensaver settings” that stays up for a while. Any way to disable this?
[Fire TV Original Android Development] Pro-me3us:
If you only want a black screen, you can turn off the screensaver, and set the sleep timeout:

raven:/ $ settings put secure screensaver_enabled 0

raven:/ $ settings put secure sleep_timeout 30000

This can also be done through Launcher Manager / Other settings / Screensaver

Set screensaver off, and sleep timeout to 1 for 1min. The adb command will let you set the timeout to less than 1min (30000 = 30,000 milliseconds).
[Fire TV Original Android Development] Pro-me3us:
Minor update to raven_shrinker, added support for PS7201/942, in case anyone finds a 2nd gen Cube from the first lot in a warehouse. Thanks to @rocker0 for the firmware.

raven_shrinker should cover just about any firmware between PS7201 and PS7624. For PS7633 and PS7645, check out raven_buf
[Fire TV Original Android Development] fiy雨夜10086:
There is an easy mistake to make. It's the same as #124.

I use way2 bootless magisk to root.

Firstly, I initially followed all the instructions. And I want to use su command in adb to check whether I root successfully.

It says I don't have su command. So I mistakenly thought that root failed.

Then I checked the Launcher Manager, I find that it's blank, it doesn't have my command. This further deepens my judgment of root failure.

So I add the start.sh command again, and reboot it. Now it's stuck on android recovery, and I can't choose botton to reset.

I didn't know that the su command was originally invalid until I read other's post, and also don't know Launcher Manager Command disappearance is normal, so I add twice. So it's broken. I think you should add it to you post.

Anyone know how to save the cube, I will be grateful.
[Fire TV Original Android Development] roligov:
Unfortunately you can't fix it, best case you can get a refurbished replacement from Amazon if it's still in warranty.
[Fire TV Original Android Development] Pro-me3us:
@fiy雨夜10086 Once you are in that recovery menu, there isn't any known way to exit out of it. Amazon implemented that menu for all FireOS7 devices (Sticks too) a few firmware ago, but didn't implement any navigation options. There have been a number of unsuccessful (1, 2) attempts to use the physical Cube buttons, remote, and keyboard. I'm not entirely sure what error or event triggers a device to boot into it.

I'd like to better understand what might have led to this on your device.

I've not seen this happen before. Is it possible you didn't press the save button when you first entered the ADB command? The known issue with Launcher Manager is that Amazon has been remotely disabling the app, which makes the entire app disappear, not the ADB commands. If that happens, the bootless Magisk script isn't started, which isn't a problem in itself.

After you re-added the ADB command to Launcher Manager to automatically start bootless Magisk on boot, did you reboot right away, and the Cube went to the recovery menu? Or did the Cube boot successfully at least once, and then boot to recovery on a later reboot? The bootless Magisk script isn't run until FireOS boots to the homescreen successfully. If the device doesn't boot to FireOS, it never has a chance to attempt to initiate the start.sh / bootless Magisk.

Did you ever run the start.sh script manually from the ADB command line? What version of FireOS is your Cube on?

One way to check if bootless Magisk has started is to check if /sbin/magisk is present. This is created only after it starts. The other way is to check Magisk Manager, and see if Magisk is still listed as not installed.
[Fire TV Original Android Development] fiy雨夜10086:
My fireOS: PS7614/3227

Concrete behavior:

For the first time I add start.sh command, then I reboot cube, it startup and shows incomplete desktop and don't have internet., After 30s, the desktop display normal. Maybe it's because of sleeping 30s. Then I go to Launcher Manager, the command was disappeared. I haven't checked /sbin/magisk or open magisk app. I'm ensure press the save button.

Then I add start.sh command for the second time, I reboot cube. Then it also startup, and shows incomplete desktop, but after some seconds, the cube reboot itself, then it enters recovery mode.

And I never run the start.sh script via adb command line, I also know I can't run it twice. The only diffrent command is I use the "adb install magisk_manager.apk" to install magisk, because I can't use "adb shell pm install -r /data/local/tmp/magisk_manager.apk" command.
[Fire TV Original Android Development] Pro-me3us:
Thank you for the details. I'm not sure what the cause of the incomplete desktop and no internet might have been. Bootless Magisk is different than regular Magisk, it has no processes that boot with FireOS. The 30sec pause, is to give FireOS time to startup before running shrinker and starting Magisk. The reboot may have been due to shrinker, since it has a ~15% chance of crashing the 2nd gen Cube upon running. But if shrinker crashes the Cube, root is never achieved and the start script for Magisk isn't run. Running 'install' rather than 'install -r' for Magisk Manager isn't a problem.

The only thing I can think of is that magiskinit v21.2 may not play well with PS7614/3227 since this was the same firmware @roligov was on too. I will add a note to the bootless Magisk instructions, that PS7614 may be incompatible.
[Fire TV Original Android Development] SpranklesXDA:
Hello can this be run on windows 10 Pc using CMD or ADBLINK .

CAN temporary root be run from the cube/ firetv app to copy and paste commands or does all methods require Linux. Thanks for everything been reading for a few months. Just have to put Linux on a PC if windows won't due
[Fire TV Original Android Development] Pro-me3us:
No Linux isn't needed. raven_shrinker is run directly on the Cube to gain root access. You only need a program or app to run the commands on your Cube. You can use ADBLink for windows to copy and past the commands.

You can use the android app Remote ADB Shell on an Android phone, tablet, or install the app directly on the Cube. It would be a bit more work entering commands with a remote and on screen keyboard.

btw what firmware version is your Cube on?
[Fire TV Original Android Development] SpranklesXDA:
Hello thanks but I can't get adb not found. Have the raven shrinker file on my cube but can't get it started. Been about 7 years since I've really messed with anything so I know it's something easy I'm missing. ( I can push APK with adblink all day long to my cube but can't get raven shrinker started on windows / or Chromebook.

Cube was on 7.2.9.2 out of the box and I blocked update with Adguard and cleared pm updates but I logged out my Amazon account into another and while messing with this forgot apps weren't still there so took an update to 7.6.1.4 and i blocked updates with Adguard trick and luckily cleared and OTA that was ready to install

7.6.4.6 wew at least I can still use custom launcher once I figure out what I'm doing wrong with raven shrinker

Oh yeah 4 more cube's do to soon lol
[Fire TV Original Android Development] Pro-me3us:
Use ADBLinks's 'Console' button, rather than 'ADB Shell' button.

ADBLink Console button (remember to put raven_shrinker in your ADBLink folder on your Windows machine)

$ adb push raven_shrinker /data/local/tmp/

$ adb shell

raven:/ $ chmod +x /data/local/tmp/raven_shrinker

raven:/ $ /data/local/tmp/raven_shrinker

raven:/ # echo '<?xml version="1.0" encoding="utf-8" standalone="yes" ?><map><set name="DenyListKeyPackages"></set></map>' > /data/system/PackageManagerDenyList

raven:/ # exit

raven:/ $ pm clear com.fireos.arcus.proxy

At this point a reboot is required for the package protection changes to take effect, but the Cube will immediately contact an Amazon server on bootup and rebuild the package protections list. So before rebooting disable your internet, by disconnecting the internet cable going into your router. This will allow you to still connect to your wireless devices in your house, but they won't be able to contact the outside world internet. Now reboot

$ adb shell

raven:/ $ pm disable-user com.fireos.arcus.proxy

raven:/ $ pm clear com.fireos.arcus.proxy

raven:/ $ pm disable-user com.amazon.adep

raven:/ $ pm clear com.amazon.adep

raven:/ $ pm disable-user com.amazon.device.software.ota

raven:/ $ pm clear com.amazon.device.software.ota

raven:/ $ pm disable-user com.amazon.device.software.ota.override

raven:/ $ pm disable-user com.amazon.tv.forcedotaupdater.v2

Done, this will disable package protections (can disable/enable any app without root), disable Amazon's AppBlockList (Let's Amazon disable apps they dont' like on your Cube, eg Launcher Manager), and disable OTA firmware updates. Go ahead reconnect your internet, and reboot your Cube one last time and verify the apps you disabled are disabled with:

raven:/ $ pm list packages -d

NOTE: raven:/ $ --> raven:/ #, the '$' to '#' switch indicates that you have switched to root user. raven_shrinker doesn't work 100% of the time, for best results, run it 1-2min after a fresh reboot. If it reboots, or fails to gain root, reboot and try again a second time.

In the future if you want root acces again, you only need to run

raven:/ $ /data/local/tmp/raven_shrinker

That's too bad you lost PS7292 on that device, it was the last firmware version that could be bootloader unlocked.
[Fire TV Original Android Development] SpranklesXDA:
Awsome that worked

and this was the end so all good right ?

raven:/ $ pm list packages -d

package:com.android.nfc

package:com.amazon.tahoe

package:com.fireos.arcus.proxy

package:com.amazon.firehomestarter

package:com.amazon.tv.forcedotaupdater.v2

package:com.amazon.device.software.ota

package:com.amazon.tv.launcher

package:com.amazon.device.software.ota.override

raven:/ $

I can disable any TDUK blockers etc no problem now correct.

only step i got an error was this but maybe its normal fyi

raven:/ $ pm disable-user com.amazon.adep

Exception occurred while executing:

java.lang.IllegalArgumentException: Unknown package: com.amazon.adep

at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:21014)

at com.android.server.pm.PackageManagerService.setApplicationEnabledSetting(PackageManagerService.java:20957)

at com.android.server.pm.PackageManagerShellCommand.runSetEnabledSetting(PackageManagerShellCommand.java:1610)

at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:201)

at android.os.ShellCommand.exec(ShellCommand.java:103)

at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21600)

at android.os.Binder.shellCommand(Binder.java:634)

at android.os.Binder.onTransact(Binder.java:532)

at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2796)

at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3954)

at android.os.Binder.execTransact(Binder.java:731)

255|raven:/ $ pm clear com.amazon.adep

Failed

1|raven:/ $ pm disable-user com.amazon.adep
[Android Head-Units] cneufy:
It appears i have bought an android head unit that boots showing android 11, says its running android 12 in device information app but has API 27. Should i download an update to make this run better or just use it as is.

ALPS 8227L_demo

1 rom 16 ram

JCAC1003-OC2-V1.0.45R2-221014_1723

CPU ARMv7 Processor rev 3

Thanks for any help with this.
[Android Head-Units] cneufy:
In addition to this I notice no canbus version...will I have to load anything to have the canbus work for my mercedes ml320?
[Android Head-Units] cneufy:
Seems as if it's very bare bones as I don't even have any canbus settings under factory setup.
[Samsung Galaxy Watch 5] KUMARKING:
How to enable ECG and Blood Pressure features on the Samsung Galaxy Watch 5

Model:SM-R 910

Softwear Version: R910XXU1AWB1

AP: R910XXU1AWB1

CSC: R9100XM1AWB1
[Samsung Galaxy Watch 5] galaxys:
Hi, check the information and references in this thread:

https://xdaforums.com/t/how-to-get-ecg-and-bp-gw5.4533063/
[Samsung Galaxy S23] chao596:
I got a new s23 from America, and the model is SM-S911U1, and go back to Taiwan.

All the device is much better than my previous s20 FE.

However, one of the important function: NFC sim card is not work functionally in the s23.

I can not select the default NFC method to SE SIM card to use my nfc sim as transport card.

Is there any solution?

Thanks a lot.

This two pics is from my old phone s20 fe.

View attachment 5883811View attachment 5883815

And this is from s23.

View attachment 5883817
[Wing, P4350 General] ilikepu:
It was a nice ride with everyone here on the herald forum but :( sadly (and pissed off:mad:) i must say goodbye i bricked my phone and i stopped caring enogh to fix it u might see me on the rapheal thread in about a couple month

thanks to Ivan, PApa, tran and everyone esle who helped me make my phone a hell of a lot better :cool:
[Wing, P4350 General] dougstoner:
Wow, you dont even want to try to unbrick your phone? I hear you though. Im getting so tired of my wing, and I am about ready for a new phone myself. i just bought a 46 inch sony bravia, so i cant justify spending any more money on a phone, but there is a runor at our office we will be getting our bonus check next week so who knows. anyway, best of luck, and thanks for all the help you have given to me, as well as everyone else. i might have to look into the raphael. im still not impressed with the g1, so not sure what i want.
[Wing, P4350 General] ilikepu:
lol i did try to fix it i broke the lcd screen n i spent a total of 54 hours sodering and taping and other stuff trying to fix it lol i just dont care about it anymore it wont power on anymore
[Wing, P4350 General] ilikepu:
rapheal is worth it i have had a lot of hands on with the Sprint touch diamond and pro
[Wing, P4350 General] dougstoner:
Yeah, I believe after 54 hours it's time to call it quits!!! It's officially a doorstop now. :(
[Wing, P4350 General] dougstoner:
Yeah, I'll have to look into those. I've been busy and haven't had time to research phones yet, but we did get our bonus, so I might have to buy myself a phone soon! :) Let me know what you decide to go with. I would love to hear feedback.
[Wing, P4350 General] ilikepu:
ive had a lot of hands on with the GSM model (Fuze) and the Sprint TP both work so i cant describe but i preferrably would go with the Fuze just so i can keep flashing my phone lol but i get a major discount from sprint so most likely ill go with sprint

the Fuze actually mless programs space than the Sprint TP thats easily fixed by rom flash for a clean version