Related
Heya all.
Changelog:
1.1 - Added orientation switch and propagation (open "Reading Now") to Nook reader
1.0 - Initial release with home and CoolReader option.
Working on:
Investigating the way to distinguish if opening reading now book and not other epubs in order not to show menu on any library book click.
History/Idea:
Just got nook last Sunday as gift and immediately noticed after root that back/menu buttons in status bar is great, but would be even better to use book button as home OR as menu, was messing with framework, etc. to no avail, but finally got a better and simpler solution, but with cons.
After installing CoolReader I noticed that "reading now" button will trigger android select app menu with Nook Reader and CoolReader, so it is broadcast event, opening with CoolReader shows it is getting started epub.
So, here it is. Simple app, registers as one of the epub readers, by having last read in native nook reader any epub - and by pressing "reading now" button it will trigger app select dialog with my app in list (you can check to always open epubs with it).
It will show styled popup menu (see screenshot) containing only Home (will open default one or list of available homes if none selected as default), orientation switch, CoolReader shortcut (hardcoded now) and Nook Reader (this one will open remembered "Reading Now" book)
Cons:
1. Will be triggered on any broadcast event to open epub. (I don't care as I read in fb2)
2. If nothing in "reading now" it will not be triggered as well if "reading now" is not epub
3. hardcoded shortcuts for now
If it generates enough interest I can improve app (in current state functionality is enough for me). I could think of adding next features:
1. Add/Configure any shortcuts, e.g.:
* Back/Menu buttons in addition to home (this will required root to run)
* Add/Configure any shortcut
2. Add ability to propagate event data, e.g. if "reading now" sending "warandpeace.epub" to this app - send it to launching app if configured. This will allow to register this app to open epub and then open configured reader with epub data - done, besides configuration
3. Investigate launch origin (launching activity) and if it is not opening from status bar, but for example from astro/library - open configured reader propagating data.
4. Organize shortcuts as tree
5. Add recent apps submenu
Really interesting
It could even replace Button Savior in a subtler way
BTW, in the same spirit, do you know if it could be possible to change the app launched when you click on the home button in the menu that appear when you press the n button ?
hi,
i tried it and it works great, thanks!!
isn't it possible to launch the default app automatically, when pressing the button?
(on a side note: wouldn't it be possible to reconfiger the home button of the standard nook menu (the one that opens when you press the n-hardware-button) to launch the default android home?app?
edit: ok, somebody was quicker, i swear i didn't copy..
XorZone said:
If it generates enough interest I can improve app (in current state functionality is enough for me). I could think of adding next features:
1. Add/Configure any shortcuts, e.g.:
* Back/Menu buttons in addition to home (this will required root to run)
* Add/Configure any shortcut
2. Add ability to propagate event data, e.g. if "reading now" sending "warandpeace.epub" to this app - send it to launching app if configured. This will allow to register this app to open epub and then open configured reader with epub data
3. Investigate launch origin (launching activity) and if it is not opening from status bar, but for example from astro/library - open configured reader propagating data.
Click to expand...
Click to collapse
Consider my interest highly generated. This is flat out great, especially if the option to go to Reader is built into Nook Book Button menu, and with the options of Back and Menu. I like Button Savior, but this has all of the same potential with a less obvious footprint and more seamless execution.
I'm running it now and this is really fun - if #2 can be done as well I see this as becoming an indispensible app for the nook touch root.
Sent from my NookColor using xda premium
Thanks. I'm trying to get a clue if it was launched from "Reading now" button or from other app. I can easily distinguish between "Reading now" and let's say Astro, but cannot distinguish from Nook Library.
And... great news - I'll post update soon with working landscape/portrait button.
Working on: opening only from "Reading now" or other nook app, but skips to configured reader otherwise. Also, instead of CoolReader I'll have configured reader in the menu.
For the back/menu buttons this will require root.
It is possible to change "n" button, I have it configured as Search button and assigned SoftKeys to search button long press. I'll post instructions soon as well as modified SoftKeys to handle Search long press without need of external app and also with a bit more friendly colors for eInk (background of recent apps white instead of blured)
unattached said:
isn't it possible to launch the default app automatically, when pressing the button?
Click to expand...
Click to collapse
Do you mean just to launch let's say CoolReader instead of NookReader by the press of "Reading now" button?
I think you've done a great job. and I guess adding a list of (programmable) shortcuts on that button would be neat (like when copying several chunks of text from a pdf to a doc text or something of the sort).
Ok, story number 1:
I dissembled (smali) framework jars and now have good idea how that book button works, basically it send custom broadcast, problem is that broadcast not ordered, I can change service.jar to broadcast mine event and this will allow to configure how to act, e.g. you can configure as default (reading now so I'll just send original broadcast), popup this menu or launch any app including home or softkeys directly.
Will play a bit more if androidriority indeed works even for unordered sendBroadcast and if I can abortBroadcast to not allow original reader spawn - we can avoid modification of the service.jar.
story 2:
WindowManagerPolicy/WindowManagerService seams like directly invoking native (JNI) code on home button, I was playing with remapping keys and finally found one that works with single press (Call not bringing dialer at all, camera only sends broadcast at long press, etc.), but by default it will not awake device, will have to play if I can awake from broadcastReceiver, if yes - it means we can configure "n" (home) button to do whatever we want.
Well, I don't use coolreader, but the extra home button and portrait/landscape button works very well.
Great job!
For me, the only thing missing is adding 2-3 apps on the list, and I'll be quite happy.
I don't use the N button much, but it could become a neat menu or back button.
Great App
Thanks for spending time making this app for us Nook Touch users.
I think this app is definitely a candidate for partial refresh. Having the full screen refreshed to draw the small dialog seems to be overkill. Not sure if that's under your control or not...
I definitely have an interest in remapping the N button to home. Perhaps long press launches the original menu?
cheers! gr8 post,
XorZone said:
Do you mean just to launch let's say CoolReader instead of NookReader by the press of "Reading now" button?
Click to expand...
Click to collapse
thats what i meant! launching just one app automatically, let's say cool reader.. (maybe launching the home app automatically would also be possible? then we would have all the standard buttons in the task bar!)
cheers
Sent from my HTC Desire using XDA App
Well, I've noticed that not all apps are turnable (haven't tried all yet, but I can spend like 30 minutes trying them all).
BUt great job nonesoever.
Having trouble
Would anyone know how I clear the default selection for the Reading Now icon in the status bar? The NookBB menu now will not come up anymore when I press the Reading Now icon.
It was working out great for me until this:
1) When I first installed NookBB (v1) and then pressed the Reading Now button, it would pull up a dialogue box asking which action I'd like to set as the default - either the Nook BB menu or the default Reading Now application (which would be the B&N reader app).
2) I selected as the default the Reading Now application (B&N reader). Then I decided I wanted to use the Nook BB as the default but couldn't figure out how to do it. The Manage applications for NookBB won't let me clear default there as it is greyed out.
3) I tried uninstalling, and installing v2. It loads the app icon to my app drawer, but the only way to invoke the Nook BB menu is to press this icon. Pressing the Reading Now button takes me to the B&N reader.
I have just found a very interesting app while searching something on github
(I posted it here mainly because I didn't want to start a new thread)
Relaunch (coded by yiselieren) is a filemanager / launcher / task manager for Nook Simple Touch. and it has very interesting features.
One of them is that when you click on the Home, library, shop or search button in the menu of the n button, you can choose to start ReLaunch instead of the default app.
I think it would be great if you could add something (more or less) similar to that in your app.
For clearing uninstall and reinstall should work. You can try installing any epub reader (such as coolreader) and it should bring selection popup back to choose default one.
Anyway I've done patching services.jar so it will load Nookbb by pressing that button with option to go directly to reading now not relying on epub files and *only* by pressing that button.
Also for the nook menu (n button) I done remapping (easy one) and almost done custom small app so n button will act as stock Android home one, e.g. it will go home with short press and bring recent apps (using softkeys now) on long press. Still have to tinker device wake if it's locked instead of going to home behind screensaver.
I plan to post it both tonight or tomorrow.
Then I can spend time adding customizations and partial refresh.
Sent from my SAMSUNG-SGH-I897 using xda premium
XorZone said:
For clearing uninstall and reinstall should work. You can try installing any epub reader (such as coolreader) and it should bring selection popup back to choose default one.
Click to expand...
Click to collapse
Thank you, uninstall didn't fix it but installing cool reader did.
Can't wait for the new fixes, very impressive already.
Sent from my NookColor using xda premium
I'm loving this app and very excited to see a Touch specific app. If you further tweak the Book Button Menu I'd like the ability to subsituite the E-reader software of my choice instead of Coolreader. I'm currently using Mantano Reader and enjoying the software.
ryanpl said:
I'm loving this app and very excited to see a Touch specific app. If you further tweak the Book Button Menu I'd like the ability to subsituite the E-reader software of my choice instead of Coolreader. I'm currently using Mantano Reader and enjoying the software.
Click to expand...
Click to collapse
I'm currently finishing n button mod to act as stock android home (short click - goto home, long click recent apps list with all buttons (back, home, menu, search, orientation). Almost done - testing and trying to apply partial refresh.
Next step - I'll publish patched services.jar so BookButton will be launched only by this book button not relying on epub files.
Next will be settings for the BookButton to configure all aspects of the menu, e.g. appearance of Home, Orientation as well as custom shortcuts.
thanks, I realy like your application. Very usefull but I don't use "Cool reader". I use "read it later" and "ezPdf" for reading.
I bought a preloaded FTV so I dont know anything about how these are setup. I tired to search but I cannot find anything as Im sure Im using the wrong wording. Anyway, there is an Internet option on the XBMC home screen that was tied to FF browser. I wanted to change which app that button launches. How can I do that? I have the app already side loaded... Thanks!
I need to find out here the app is so I can assign the ' Default select action '
Depends on the skin, you can customise some skins and change the buttons around. It's under appearance and then skin settings, depends on the skin how it is implemented though.
What skin are you using? What do you want to add to the home screen menu?
ITs Aeon Nox. I did find where the options are to change button name, what shortcut to apply to it etc. Im going to assume that I need to use the Custom option and type in the location of it on the storage where its located. Since it'll be pulling the app from the FireTV side of the AFTv ( Its side loaded... ) The only way I can access it now is by going all the way back to AFTv screen and going to settings and all apps ( or something like that )
mroneeyedboh said:
ITs Aeon Nox. I did find where the options are to change button name, what shortcut to apply to it etc. Im going to assume that I need to use the Custom option and type in the location of it on the storage where its located. Since it'll be pulling the app from the FireTV side of the AFTv ( Its side loaded... ) The only way I can access it now is by going all the way back to AFTv screen and going to settings and all apps ( or something like that )
Click to expand...
Click to collapse
If you want a button for firefox in aennox just add firefox to your favorites, then select it from your favorites when setting up the button.
Or if your using Aeon Nox 4, you can add it directly to the Home screen.
Go to System > Appearance > Skin (Settings) > Custumizer (Main menu item customizer)
Then on the Main menu, select the item you want to add as a custom menu item and select it. If if has a red X on it, then select "disable" to enable it, then select "Choose Type".
Now select "Custom" and in the keyboard box type in:
StartAndroidActivity("your.app.apk")
So for example Netflix would be:
StartAndroidActivity("com.netflix.ninja")
You can do this for either the main menu item or for sub-menu items.
Thanks!!!
How do I add Firefox to my favorites
Or how do I find the directory where Firefox is so I can type it in the custom StartAndroidActivity section
Finally got iy. I had to go back into the Confluence ++ skin, add the app to my favorites and then go back into the custom Aeon Nox skin and then add the app from favorites...
Hit THANKS button if you like it!
Or buy me a cup of coffee, donation-link on GitHub
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AppStarter
AppStarter: An AppDrawer and Kodi / SPMC Updater for Amazon FireTV:
This App is Open-Source, visit AppStarter on GitHub: https://github.com/sphinx02/AppStarter
Lists all user-installed apps including sideloaded / adb installed apps.
Apps can be easily sorted / ordered by settings-button or click-drag-and-drop (long-click to start drag-and-drop).
Apps can be hidden from app drawer (see settings).
Kodi and SPMC can be installed and updated directly out of AppStarter (see Updates section).
Possibility to change the time of no action the FireTV waits to go to sleep.
Possibility to import / export settings.
Show system and device informations like Android-Version, Build-Version, Hostname, WiFi- / WLAN Name (SSID), IP Adress and Uptime.
Automatic update mechanism.
__No root required!__
Reviews / Articles:
Just google for "AppStarter FireTV"
Install AppStarter:
Easy installation in less than 5 minutes with only the FireTV
https://github.com/sphinx02/AppStarter/wiki/Install-AppStarter-and-Kodi-(only-FireTV-needed)
Standard installation via ADB
If you don't know how to sideload/install apps via ADB, read a tutorial (e.g. this one)
Download latest AppStarter APK and sideload/install with adb:
adb install -r AppStarter_v4.0.apk
Enjoy..
TO UPDATE APP: Simply use the integrated updater mechanism.
Why using it:
AppStarter provides a nice possiblity to show all user installed Apps.
AppStarter provides an Updater for Kodi and SMPC which allows to keep these two Apps up to date in a very convinient way.
Changelog:
v4.0
Renamed App to AppStarter
Renamed package to de.belu.appstarter
Removed home button observation as not needed anymore
v3.2.3
Added SPMC updater (possibility to install and update SPMC).
Added simplified chinese translation (thx lostindark).
v3.2.2
Fixed wrong app start of apps using the leanback-lib (e.g. MagineTV)
Updated translations
v3.2.1
Fixed "parse packet error" for Kodi updates
Added setting to decide which Kodi version is installed / updated (stable, beta / rc, nightly)
v3.2
Added possiblity to install / update Kodi (see Updates section). Thank you very much attilaszasz for your contribution!
Made "Background for App Names" a bit brighter. Thanks semitop7 for your contribution!
Added semi-transparent background for system, updates and settings section if the "Background for App Names" setting is enabled. Thanks semitop7 for your contribution!
v3.1.1
Fixed flashing screen / start app problems (disabled JumpbackWatchdog for FireOS5).
Updated translations
v3.1
Added setting to show background for app names in the app drawer (helps to read app names when wallpaper is used).
Added setting to hide left selection bar when on the main screen (app drawer).
Fixed backup (export/import) settings feature for FireOS5.
Updated russian and ukranian translations (thanks sem_top7 and Kramar111).
v3.0
Optimized ADB connection mechansims for FireOS5. Should now work without disable + enable ADB after reboots. Still no parallel ADB connections possible.
Added shortcut to ADB settings in AppStarter settings.
Added first try of completely new detecting home-button clicks without adb (which is also used as Fallback after 3 failed ADB connects). The new non-ADB observation of the home-button works only if you are on the original Amazon FireTV Home screen. This means if you are in any other App like Kodi, you have to click the home button once to get to the Amazon FireTV Home screen and then you can single or double click the home-button to perform the action desired. In practice that means, you can also add one home button click if you are in another app. If you are for example in Kodi, you can do a double-click to the home-button to perform the single click operation and according to this you can do a triple click to perform the double click action. Sorry for this strange behaviour but due to technical limitations of Android, there is no other possibility without ADB at the moment.
Removed restart-option and replaced it with notification how to restart with the remote.
Better handling of the jumback-detection -> fixes some unnessecary jumpbacks especially when the click-action is "- No Action -" or "FireTV Home". You can again safely use the jumpback detection (e.g. with default of 5000ms)!
Option to start click-action apps with FLAG_ACTIVITY_CLEAR_TASK -> Previous instances of the App are cleared before start (e.g. AppStarter then starts always on the first icon which is useful for some people with programmable remote's).
Everything only tested with FireOS4 on FireTV and with FireOS5 Developer Preview on FireTV-Stick. I am not yet able to test on a FireTV2 with the real FireOS5.
v2.7.2
Show device uptime and boot time in system tab
Back button returns to main app view if on another tab
Removed Go-To-Sleep functionality, as it is anyway possible via long-press home-button. The existing implementation was not reliable enough and made some problems under specific circumstances.
v2.7.1
Added russian and ukranian translations (any other language contributions are welcome). Thx to XDA user sem_top7 for the translations!
Fixed bug in file selector (no image files found in root-folder)
Fixed (hopefully) bug in manual language selection which sometimes lead to a mixed language
v2.7
Little redesign of the GUI
Added date & time information at top
Made the app-icons a little bit smaller (5 apps per row and still big enough)
Added customizable icon-size in settings
Added possibility to export / import settings
Added more informations to the system-tab
Added possibility to modify the time of no action till the FireTV goes to sleep
Added possibility to go directly to sleep from AppStarter (little hack, setting the time-to-sleep to a very short value and set it back after wake-up)
NOTES:
Be carefull with the go-to-sleep feature, only tested it on FireTV not on FireTV-Stick. Advanced users give me feedback if it works please .
The setting of the general time of no action till FireTV goes to sleep is safe to use. It is a default Android-Setting which can be edited by apps (I don't understand why Amazon isn't giving us this feature..).
v2.6
Custom wallpaper via settings (JPG / PNG cropped to fit screen)
Renamed "All Apps" to "Apps" and "Infos" to "System"
Added WiFi name to System-Tab
Added possibility to reboot FireTV to System-Tab
Added FLAG_ACTIVITY_NEW_TASK and FLAG_ACTIVITY_CLEAR_TASK to startup-action (perhaps helps some people reporting weird colors when starting Kodi as startup-action)
NOTES:
Tried to add sleep-button to bring FireTV to sleep-mode but it seems as this is not possible without root, if anyone knows anything else, please report...
Settings ex-/import and more themeable GUI are still on my TODO.
v2.5
Check out settings-button: Added menu for apps to move app (same than long-click) or to open app-specific settings
Items in the left selection bar are now also clickable with a mouse
Added german translation and manual setting of the current language
Spelling corrections
v2.4.1
Apps are not started with FLAG_ACTIVITY_CLEAR_TASK which lets app resume their last activity.
Replaced some icons / made some visual optimizations
For timing settings, now the correct inputtype is used (number only keyboard is displayed).
Adjusted default-timings (only for fresh installations).
Minor fixes.
v2.4
Implemented jumpback prevention watchdog which prevents amazon home from coming to the foreground after click-actions (configurable in settings). Thanks XDA user harlekinrains for this idea.
Removed now unnessecary action-delay setting.
Added FireTV settings application to apps-list. Thanks XDA user fsi09 for this idea.
Some code cleanup / optimization.
v2.3
Fixed ugly bug in settings (kind of endless loop), which caused huge cpu-load and weird behaviour of settings storage.
Fixed bug when sysapp were set visible and apps were reordered, sysapps were not hided again on settings change.
Allow greater double-click interval and action delay (up to 1000ms).
v2.2
Added adjustable double-click interval and action-delay
Reordered settings
When going to app-drawer, first icon is automatically focused (configurable in settings)
Update service (able to update itself)
v2.1
Fixed problems on FireTV-Stick (which by default has multiple local adb-devices), thanks to harlekinrains for logcat-infos
Added AppStarter version to info view
v2.0
Real Home-Button detection, even double-home-button-clicks are captured
Completely new GUI with settings and additional Infos
Completely configurable actions
Hide-App feature
Screenshots:
Hit THANKS button if you like it!
Or buy me a cup of coffee, donation-link on GitHub
.
You can also include some informative things; time, date, weather etc. to the corners maybe.
Different backgrounds option might be a good feature to have.
@legendnexus
The current version is my "first shot" and for the beginning a good working solution was more important. But yes I also thought about adding some informative things.. Thank you, I will put it on my ToDo-List
@harlekinrains
Thank you for your detailed (and merciless^^) feedback:
You are right, the replacement-icon is grap, but I'm not a designer and in a quick way it shows the replacement capability and is better than the original IkonoTV-Icon. I think about a better one
Hiding apps is definetly planed, I add it to my ToDo-List. But at the moment I am not "guessing" which apps the user dont want to see, I simply do not show system apps but only user installed apps (except for kftv-launcher/amazonhome).
I am with you, that look&feel is very important and I try to work on this part
Your requirement:
I do not really understand your requirement, do you mean to simply start another app instead of the App but with the same home- and startup-detection? Is this not what AFTV Launcher Helper already does?
Ok I understand now, perhaps I will add this in future as an option.
For me it feels more attractive to have only one app without huge configuring steps.. For me the most important part is, that also beginners are able to use the App. That is why on the top of my ToDo-list are better installation instructions and possibility to install / keep updated some of the most famous apps from the App directly. So in the end my focus is really the usability espspecially for non-experts. I also think about a little (windows-) installation tool with auto-detection of the FireTV and Wizard-Charakter for the installation of the App. But this all is a lot of work and I dont know when I find the time to..
Anyway I am really happy to hear other's opinion and to get more inspiration by users, thank you again harlekinrains for your constructive feedback
BTW: Thanks for your uninstallation hint, perhaps I should also add an uninstallation routine, which cleans up the .imagecache-folder and triggers the the App uninstallation then..
v2.0
Forget what I realeased in v1.0, I am proud to present a completely new way of detecting the home-button-click in v2.0
The XDA-user g4rb4g3 http://forum.xda-developers.com/showpost.php?p=56319876&postcount=87 pointed me to the right corner of the home-button detection and I think it works brilliant (as long as you keep adb-debugging enabled on the FireTV). As some requested, everything is completely configurable, so you can use my app also to only start your favourite apps.
v2.0
Real Home-Button detection, even double-home-button-clicks are captured
Completely new GUI with settings and additional Infos
Completely configurable actions
Hide-App feature
Hit THANKS button if you like it!
sphinx02 said:
Forget what I realeased in FireStarter v1.0, I am proud to present a completely new way of detecting the home-button-click in FireStarter v2.0
The XDA-user g4rb4g3 http://forum.xda-developers.com/showpost.php?p=56319876&postcount=87 pointed me to the right corner of the home-button detection and I think it works brilliant (as long as you keep adb-debugging enabled on the FireTV). As some requested, everything is completely configurable, so you can use my app also to only start your favourite apps.
FireStarter v2.0
Real Home-Button detection, even double-home-button-clicks are captured
Completely new GUI with settings and additional Infos
Completely configurable actions
Hide-App feature
Hit THANKS button if you like it!
Click to expand...
Click to collapse
Just tried your app. Works great. Very straightforward.
Thanks for your work
harlekinrains said:
On the Fire TV Stick - I get a toast "Starting Home Button observer takes to long"....
Click to expand...
Click to collapse
Hey harlekinrains, too bad that it is not working on the firetv-stick out of the box. I had no firetv-stick to test, as my sister has it at the moment .
Thank you very much for the log's thats very helpful! I think we can rule out the performance of the firetv-stick, as the new way of catching the home-button click via adb is very performant. The only hard-coded timing is the waiting-time for the second click in the double-click detection. The other timings are only to trigger these informative toast messages. I think the reason could be, that on the firetv-stick usb-debugging is not possible? Could that be? That would not be an problem, I only have to change the way I connect to the local adb.
EDIT : Normally it must not be enabled in the settings. On my FireTV it is disabled and everything works perfect. The question was only: Is there a setting for usb-debugging on the FireTV-Stick?
If you have (and really only if you have) the time to, you can chek the following things (I do it on my own as far as I have the time to and have mit FireTV-Stick back):
From the shell of your pc go to the shell of the FireTV-Stick:
Code:
adb connect [IP of your FireTV-Stick]
adb shell
Then in the shell on the FireTV-Stick enter the following commands and tell me whats the output:
Code:
adb devices
adb logcat -c
harlekinrains said:
Give me just a sec - and thank the all mighty RNG for you having access to a FIre TV Stick. ....
....
Click to expand...
Click to collapse
"All mighty RNG" - I dont get it :crying:
Thank you for the output, I think everything is clear now, the fact that there are by default two devices listed is the problem. I have to change my code to use adb with an explicit device. On my FireTV by default I have only the "emulator.."-entry which let it work without specifiing the adb-device..
Perhaps I can provide an update this afternoon, at the moment I am too busy
I have a Fire TV box and after a restart it says observer needs too long. That message is only viewable for seconds. The app doesnt work so far for me . Too bad
v2.1
After your feedback, I tried to fix the remaining problems especially on the FireTV-Stick. I had again no FireTV-Stick to test the changes but I'm pretty sure my changes will rule out the problems. Please tell me if it works on your devices
v2.1
Fixed problems on FireTV-Stick (which by default has multiple local adb-devices), thanks to harlekinrains for logcat-infos
Added app version to info view
Hit THANKS button if you like it!
Thanks for your quick support! I can confirm that this even works on the Fire TV BOX now! Big Thanks! One of the must have apps.
harlekinrains said:
Works now on the Fire TV Stick as well - as intended.
Allthough - it doesnt work all the time, depending on memory load
....
But as with Fire TV Helper - it seems to be possible to set a condition, even without root - that a jumpback - to the amazon menu is not - triggered. I wander if a timed jumpback block would be helpful here as well - the logic goes:
Button pressed - jumpback block blocks execution of the Amazon menu for *user setable time in seconds* - App launches (has said seconds to launch without the risk of getting interrupted) - jumpback block to the Amazon menu is removed.
.....
So idk if it will be fixable by the approach above (prevent the Amazon launcher to (re)start for a set time window after pressing the home button).
Click to expand...
Click to collapse
Hey harlekinrains, thank you again for your feedback
I dont have this behaviour on my FireTV but yes you're right, that sounds like a timing problem. The problem can be, that the new home-button detection method is too fast, which means that the launch of the custom-app is initiated before the launch of the amazon home launcher. Then it can happen, that the amazon launcher cames up instead of the custom selected app.
I can not imagine, that there is a way to prevent the amazon launcher from starting.. Dont know the feature of Fire TV Helper and I also cant jump into the sources, as it is not open source..
Two possibilities:
either I make a litte (customizable) delay for the custom start action (so e.g. the App or FiredTV is started with a little delay after the home-button-detection)
or somebody provides me with the ability to block the amazon-launcher from comming up..
I tried a little bit around and let TuneIn-Radio run in the background and then clicked like going wild^^ And infact when I set ES File Explorer as One-Click-Action and repeated clicking very fast single-clicks one after each other, I endend in a curious half-loaded amazon home screen. But a short view in the logcat showed, that not the App made something wrong but ES File Explorer was the reason, as it was in a "wake-lock" situation. Going to FireTV settings and force-stop ES File Explorer get it working again, perhaps thats the behaviour you ment? But thats some kind of monkey-test, I think nobody will switch apps that fast..
Anyway, in the next version I will add adjustable second-click-interval and also an adjustable delay for click-actions, perhaps this helps to prevent these situations..
v2.2
New Version with more adjustable settings and an integrated updater mechanism
@harlekinrains
Please check if your problems are solved by a little action-delay (I think something around 50ms should be enough).
@ all
Have fun with the new update
v2.2
Added adjustable double-click interval and action-delay
Reordered settings
When going to app-drawer, first icon is automatically focused (configurable in settings)
Update service (able to update itself)
Hit THANKS button if you like it!
Hmmm, ok none of this problems on my FireTV, it's hard to solve problems I can not reproduce.. But I have now again a FireTV-Stick of a friend of mine, so perhaps I can reproduce the behaviour on this device. But I guess you have to wait a little bit as I am on a little trip over the weekend.
One question: Are you now using the App (in daily use) or still only install it for testing? Would really feel happy if I got you as an user
harlekinrains said:
....
May I also suggest, that you set up single click "no action" and doubleclick "the App" as the default action. It somehow makes the program feeling less "intrusive" (like its taking over a Fire TV functionality) and just delivers an added value (launching an alternative launcher). Which I guess would encourage more users to try using your app. At the same time, it doesnt focus on your launcher so much, so its a toss up. Im not invested personally either way - as you integrated the user setable options - Its just a thought. (And might not even be the right one.)
Click to expand...
Click to collapse
I like your thoughts about the default-actions.. I think about it on the weekend Thank you for your frequent feedback, keep it up
i'll give this a try next week but right now i'm too busy to test it.
Ps: Sorry für den Abstieg :<
Hume Button Settings
First things first....great work....love the clean look of FireStarter-Launcher :good:
my only concern is the action taking, by clicking the HomeButton once.
Is there a chance to get back to the Amazon Home by clicking the HomeButton only one time and not by doubleclicking the homebutton?
I think this part is missing in the settings menu for the HomeButton single click action.....or am i wrong? :silly:
kind regards
Hey thanks for this Launcher, I really like it
I testet FiredTV Launcher too and the only thing that it missing in your app is: please let the app show the settings app so I can start it via your launcher, so i dont have to use the Amazon launcher anymore
(With show system apps I cant find the settings app)
v2.3
Hello everybody, back from my WE trip I found a really bad bug in the settings handling which on one hand caused that the action-delay have not been saved and on the other hand also caused unnessecary cpu-load. I fixed that bug and another bug with show-sys-apps setting. I also tested the App on a FireTV-Stick and it worked quite good. With the now working action-delay setting, I got very good results by leaving the double-click interval default and setting the action-delay to 100ms. But also with the default 10ms I had never one of theses half-amazon-home, half-app-screens.. Perhaps its also depended on what else is installed or running on the stick, I will keep an eye on it..
Thank you all for your feedback and have fun with the new bugfix-release which can be updated in-app via the updater-mechanism
v2.3
Fixed ugly bug in settings (kind of endless loop), which caused huge cpu-load and weird behaviour of settings storage.
Fixed bug when sysapp were set visible and apps were reordered, sysapps were not hided again on settings change.
Allow greater double-click interval and action delay (up to 1000ms).
Hit THANKS button if you like it!
I'm using a replacement launcher (Firestarter) and a 3rd party wireless keyboard /mouse (Mele F10 Deluxe) -- things are working well, but one issue is that the "home" button on the Mele acts like the "HOME" key on a QWERTY keyboard. Instead of returning to the home screen, it sends keyboard event "KEYCODE_HOME" (Constant Value: 3 - 0x00000003).
On a (rooted) AFTV2, is there a way to assign a keyboard event (in this case, "KEYCODE_HOME") to launch a particular app (in my case, firestarter) regardless of what else is open?
Alternatively, is it possible to have the keyboard event "KEYCODE_HOME" perform the system "home" event?"
Thanks in advance for your thoughts!
http://www.mobileread.com/forums/showthread.php?t=159538
Thats five minutes on google.
The way I have solved this was to remap the keyboard layout of my Macbook Air to adb commands - whenever I run a script that can only be exited by clicking a button on a prompt. I actually remapped the entire MBA's keyboard to send the corresponding keys to the Fire TV as adb keyevents.
Code:
adb shell monkey -p your.app.package.name -c android.intent.category.LAUNCHER 1
does what you want in that case (de.belu.firestarter is the package name btw).
I dont think every button press will show up in the Fire TVs logs the same way HOME does ("nice little keylogger you sell there, A."), so instead you might have to do the remapping at another point. Your keyboard itself is too dumb to even know what being scripted means - that leaves you either messing with the OS itself - or forfeiting the keyboard in favor of an Ultrabook. Which by the way - allows you to actually work, or browse the net - and still control the Fire TV in the background.
But people seem to be happy with their Bluetooth keyboards - because, single purpose = neato.
On my k900 plus keyboard it has a home button, why not Just map Firestarter to start up when you press home twice, then you just press the home button twice on your keyboard?
Hope this helped press thanks button
harlekinrains said:
http://www.mobileread.com/forums/showthread.php?t=159538
Click to expand...
Click to collapse
Thanks for the links. For anyone else using a media airmouse such as the Mele F10 (with a "home" button that does not send the same code as the amazon remote), it's very straightforward to create a custom keyboard map that makes it function like the Amazon remote:
1) For each button that you would like to remap, use Ketest App to discover its ScanCode (for example "102" is the "Home" button on the Mele F10 Deluxe).
2) Determine the Product ID and Vendor ID for your input device with "cat /proc/bus/input/devices" and create a copy of /system/usr/keylayout/Generic.kl with the name Vendor_XXXX_Product_XXXX.kl. This custom key layout file contains your new mapping (for example, I changed the entry next to "Key 102" to "HOME" instead of "MOVE_HOME").
3) Set ownership (chown system.system) and permissions (chmod 644) for your custom key layout file.
deanr1977 said:
On my k900 plus keyboard it has a home button, why not Just map Firestarter to start up when you press home twice, then you just press the home button twice on your keyboard?
Hope this helped press thanks button
Click to expand...
Click to collapse
Thanks for sharing your experience. The issue is that on the Mele F10 Deluxe (and other combo devices that aren't designed specifically for the Fire TV box), the home button does not send the same key code as the Amazon remote -- requiring that the user create a custom key map file.
harlekinrains said:
http://www.mobileread.com/forums/showthread.php?t=159538
But people seem to be happy with their Bluetooth keyboards - because, single purpose = neato.
Click to expand...
Click to collapse
Thanks! Given the cost difference (plus, portability, and the fact that it lasts longer on a charge), I can understand why people might choose a media remote instead of a script-friendly keyboard with a screen (like an Ultrabook). Fortunately, if your 3rd party remote doesn't work like the Amazon remote out-of-the-box, it is easy to create a custom keymap. Unfortunately, this still means that, by default, FireStarter has to use ADB to listen for the home key. I was hoping that if I use a different button instead of the home key on the amazon remote, I can have the OS "listen" in a simpler way (that doesn't tie up ADB), and simply have the OS launch firestarter when this button is pressed.
Bluetooth keyboards are less clunky - thats right. So portability and also price are valid arguments for them.
But - there is also a lot that you "lose" by not using an ultrabook (beside the remote which at some point becomes just an easy to use muscle memory extension).
The argument here goes as this way -
1. Screen Mirroring is a very, very, stupid idea. Let the battery powered device do all the processing, then let it encode a video feed on top of that, and then let it transfer...
2. Link sharing on the other hand is "where its at". So for the Fire TV this means, you use the Chrome Plugin "Play to Kodi", which covers youtube and a few other sources - and you also use Video Download Helper (Chrome Plugin available as well) to get any direct video link that isnt a rtmp stream and heavily segmented and a little script that launches http://www.multilinkr.com/ in your browser, then you paste the url in your clipbord into that, use the site to generate a clickable link and then use rightclick and Play to Kodi to cast the direct video link to the Kodi Box.
Which brings me to -
3. Discoverability is pretty lousy on remote based interfaces (Kodi has the best interface for it there is out there.). Its also pretty bad on phones (which is part of why more and more content becomes facebook native and why you are so dependent on content surfacing within an app "you like") or tablets. Its actually pretty excellent on laptops. So in some sense - I see the ultrabooks as the last bastion of non curated content and real discoverability out there.
Kodi with keyboard at that stage simply doesnt cut it. Also if you are more than a novice user you need a device you use to do maintenance on Kodi - so again - why not an Ultrabook...
-
Regarding your previous question - I know that the adb way of Firestarter noticing "that the Home button was pressed" depends heavily on certain lines within a log that only indicate that _that_ button is being pressed. I dont know how its dev handled the non adb implementation - you have to ask him. It is very unlikely - that you'd find the same or an equivalent "event indication" when you press a random key on a connected keyboard.
Remember that the watcher routine has to look for something occurring, and that in the case of Firestarter this preferably has to show up on non rooted devices also. In fact - that Firestarter (and its predecessor) exist is a little miracle in its own right - because Amazon could make a very small change and it would never be able to work again. In that sense its a hack - that relies on a very specific pattern showing up in something the OS is reporting and that is accessible by any app (userspace).
Its not based on a featureset, its based on a hack.
All-in-One tool for Windows. Wear OS Tools v10
It's a tool for use with any Wear OS watch. I am releasing today an improved and optimized version with several new features.
What does it do?
It is an All-in-One tool for Windows that makes it easy to do certain things with the watch, such as:
Send files to the watch such as MP3s, images, PDFs, or download files contained in the watch.
Install applications (Sideload).
Install applications in bulk
Uninstall apps of watch (Debloat).
Enable/disable Watch apps
Remove bloatware with Universal Android Debloater. [new]
Extract all the apps you have installed on the watch and mass restore them when necessary (Backup/Restore).
Get APK for Wear OS from "legacy" APK files for the phone.
Get APK for Wear OS in bulk.
Change ringtone, notification sound and alarm sound of the watch.
Mute ringtone, notification sounds, and alarm watch.
Manage vibration of ringtone, notifications or a specific application. [new]
Change screen density
Change font size.
Use the computer keyboard to type on the watch.
Force pairing the watch with Bluetooth without resetting to factory defaults.
Repair synchronization in old watches such as Moto 360 Gen 1 or Sony Smartwatch 3.
Enter ADB commands via command line
Perform advanced reboot (Recovery Mode and Bootloader Mode)
View and control the watch from the PC with scrcpy (only Wear OS 3). [new]
Take screenshots of the watch screen, and send them directly to the PC (Screenshot).
Record the watch screen, and send it directly to the PC in MP4 format (Screen record).
Optimize the Watch.
Apply custom settings such as adjust screen timeout
View watch information such as serial number, build version, Android version, resolution, battery status...
Connection to the watch can be made via Wi-Fi, via Bluetooth or via USB cable.
History of connected devices. [new]
New way to pair and connect for Wear OS 3.
Suggest the IP of the watch.
Changelog:
v1.0 (Feb 13, 2021) - Initial version
v1.1 (Feb 21, 2021) - Compiled again with Pro version of the EXE converter.
v2.0 (May 19, 2022) - Added new features (backup and restore tool, screen recorder and watch information)
v3.0 (Aug 27, 2022) - Added new functions (Change font size, change watch sounds), debugged code, optimized menus
v3.1 (Aug 30, 2022) - Fixed bug in option to change ringtones and sounds.
v4.0 (Oct 15, 2022) - Added new function (optimize Watch) and restructured main menu.
v5.0 (Nov 05, 2022):
- Added "Install apps in bulk" (in option 1)
- Added "Enter ADB commands via command line" (in option 7)
- Added "Restore optimizations to default values" (in option 8)
- Added help option to get IP address and secure Wi-Fi network (in tool startup)
- Improved optimization tool (redesigned and more detailed info)
v6.0 (Jan 02, 2023):
- Added "Advanced Reset Options" (in option 7)
- Added "Enable/Disable apps" (in option 1)
- Added option to list system apps, user apps, enabled and disabled apps (in option 1)
- Added separate window for listings (in option 1 and option 4)
- Improved function to use PC keyboard (in option 7)
- Improved function for sending/receiving files (in option 3)
v7.0 (Jan 09, 2023):
- Added option to debug by Bluetooth in older watches, as Moto 360 Gen 1 or Sony Smartwatch 3 (in previous connection).
- Added option to repair synchronization in old watches (in option 7.5)
- Added option of links for reference such as news about Wear OS, firmware table... (in option 7.6)
- Added guide to download and install AOSP Wi-Fi Keyboard (in option 7.2)
- Added guide to download and install NavExplorer (in option 3)
- Improved wired connection with USB debugging (on previous connection)
- Correction of bugs
- Debugged code
v8.0 (Jan 23, 2023):
- Added tool to get APK for Wear OS from "legacy" APK files for the phone (in option 7.7)
- Added tool to get APK for Wear OS in bulk (in option 7.8)
- Added option to set ringtone and watch sounds to mute (in option 4)
- Bug fix when installing APKs (now the APK is not kept in the watch, avoiding it to occupy space).
- Fixed several bugs
v9.0 (apr 19, 2023):
- Added option to apply custom settings such as adjust screen timeout (in option 8.1).
- Added feature to suggest the IP of the watch (not Pixel Watch) by typing "find" (in previous connection).
- Added new way to pair and connect for Wear OS 3, for now, only Pixel Watch (in previous connection).
- Improved error messages when installing, uninstalling, enabling, disabling APKs (in option 1).
- Improved option to change custom sounds in ringtones, notifications and alarms (in option 4).
- Fixed bug for adding muted sounds.
- The tool is now also available in German (by @Anarchon
v10.0 (Jun 06, 2023):
- Added function to view and control the watch from the PC (screen mirror) with help of scrcpy (in option 9).
- Added tool to manage vibration for ringtone, notifications or for a specific app (option 4.4).
- Added system to automatically download adb drivers in case of absence (on previous connection).
- Added to automate downloading of necessary files (in option 3 and option 7.2).
- Added Universal debloater to remove bloatware (in option 1.6).
- Added history of connected devices by typing "log" (in previous connection).
- Added specified folder where backup/restore is located (in option 2).
- Improved screen recording function, now through scrcpy (in option 6.2).
- Improved system for entering file and package names when installing/uninstalling or other operations, no need to type it anymore, just select it from the list (in option 1).
- Improved system for selecting sound files and IDs (same system as above) (in option 4).
- Improved optimization tool (in option 8).
- Improved simultaneous connection pre-check of several devices.
- Debugged all the code and reorganized the menus.
- Resized all tool windows.
Requirements
Windows O.S.
Have the ADB drivers installed. Here is the link to download them. During installation, make sure to enable the "Add to System Path Environment" option. Here you have more information about ADB drivers. Since v10, if you don't have ADB drivers installed, they are automatically downloaded and installed as soon as you open Wear OS Tools. [new]
Connect the watch and the phone to the same Wi-Fi network.
Enable debugging over Wi-Fi on the watch. On the watch, go to Settings > system > About and tap "Build Number" several times until you see a message that says "you are now a developer". Then go to Settings > developer options and enable "ADB debugging" and "Debugging over Wi-Fi".
If you want to connect the watch to the phone via Bluetooth or Cable USB, follow the steps detailed on the tool.
Considerations
The tool is available in English (EN) and Spanish (ES)..
Tested on TWP3 and TWP5, please give feedback on other watches.
To find out the IP address of the watch, just go to "Debugging over Wi-Fi" in Settings > developer options. Under that option, you will see the IP. You can also see it in Settings > Connectivity > Wi-Fi > "Your Wi-Fi network".
You can connect the watch by USB cable, by bluetooth or by Wi-Fi network.
Wear OS watches are a bit unstable to stay connected to the Wi-Fi network especially if it is connected by Bluetooth with the phone, to make sure it connects smoothly when using the tool enable the "Enable Wi-Fi automatically when charging" option in Settings > developer options, and plug the watch to the charger. Another trick is to momentarily deactivate Bluetooth in the watch, the Wi-Fi network will be activated in a few seconds.
Since v10 you can use the tool in multitasking mode, i.e. you can for example backup watch apps while you are applying custom configurations. [new]
When you have finished, turn off "ADB debugging" on the watch, otherwise it will drain your watch battery...
Where to download?
Wear OS Tool v10
Method
Download and unzip in a folder the file from the "Where to download" section.
Make sure you meet all the points in the "requirements" section.
Locate the IP address of the watch as explained in the "considerations" section.
Run Wear OS Tools and enter the IP address.
If your watch is Wear OS 2 enter 5555 or nothing in the port number, and skip to step 7.
If your watch is Wear OS 3, enter the port number, which will be different from 5555
.
Select "Pair new device" or "Wireless debugging" (This step is only performed the first time) and enter the IP, port and pairing code, then re-enter the IP and port number as in the previous step
.
A notification will probably appear on the watch asking "Allow debugging?", select "Always allow from this computer".
In the tool, choose a function to run and follow the instructions on the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Clarification on the new pairing procedure in Pixel Watch.
In the update in March 2023 for Pixel Watch, Google has implemented the new adb pairing procedure that had already been for some time on Android 11 and higher phones. It should be remembered that Wear OS 3 is based on Android 11, that is, watches like Pixel Watch, Galaxy Watch 5 or Fossil Gen 6. For now, this procedure is only implemented on Pixel Watch, but probably in the coming months it will be implemented on the other Wear OS 3 watches.
The process is that you must first pair the watch with a device such as a PC or smartphone, entering a random pairing code and a random port number (only the first time you pair to the device) and then the connection is made through the IP address as it was done so far, but with the difference that the port number is random (it is not 5555 as before) and you will have to consult it on the watch every time you connect the watch in developer mode.
Wear OS 2 watches, and for now Wear OS 3 watches (except Pixel Watch) connect the watch as usual and with fixed port number, i.e. 5555.
What custom settings and optimizations are offered?
Apply Custom Settings on the watch from the PC (option 8) :
Hide/Display developer options menu.
Enable/Disable GPS location.
Adjust screen timeout beyond limits.
Enable/Disable ambient display.
Enable/Disable theater mode.
Enable/Disable auto brightness.
Adjust brightness manually.
Apply optimizations (option 8):
Double the speed of animations and transitions.
Optimizations to improve performance and reduce battery consumption.
Enable/disable adaptive battery management.
Enable/disable the processing speed management system.
Enable/disable useless configuration items in Galaxy Wtach 4/5.
Manage Vibration (option 4):
Enables/disables vibration when receiving calls.
Enable/disable vibration when receiving notifications.
Enable/disable vibration when touching the watch screen.
Enable/disable vibration for a specific application.
Delete cache memory (option 8).Optimize performance (option 8) .Reduce battery drain with the dexopt optimization method (option 8) .
To-Do
Force pairing with Wear OS 3 watches
Improve optimization tool with more optimization tasks (any suggestions from this thread for Samsung Galaxy devices or this thread for Pixel devices?).
Porting code to Linux and Mac via Java or Python.
I share this tool for free, to code the tool as it is now having taken me quite some time, I just ask for some feedback for the one who download it and try it.
If you are going to use it, please comment what you think or what bugs you see or what new features you suggest. Any opinion is interesting.
Version Information
Status: Stable
Current Version: v10.0
Release Date: 13/02/2021
Last Update Date: 06/06/2023
Original source: https://forum.xda-developers.com/t/tool-all-in-one-tool-for-windows-wear-os-tools-v9-0.4485439/
Thanks, looks interesting! I don't have my Pixel Watch yet, but what does "Optimize the Watch" do? That sounds a bit vague.
mko000 said:
Thanks, looks interesting! I don't have my Pixel Watch yet, but what does "Optimize the Watch" do? That sounds a bit vague.
Click to expand...
Click to collapse
The tool is compatible with any Wear OS watch.
It optimizes the watch in 11 steps, which you can skip each of them or apply. The optimizations perform tasks that improve the transition speed of animations, disables useless configuration items, improves audio quality, can disable the touch sound if you have it, improves the speed of opening apps, removes cache, optimizes battery...
I tried everything out and was able to get the ringtone to change, but the notifications and alarm sounds don't change. The alarm seems to always be the same sound, but I have noticed at least two different sounds for varying notifications. Not sure if that will influence how well this application works for the Pixel Watch, but I wanted to at least mention it. Thank you for all you hard work to help the community!
Exactly what I needed! Thanks a lot!
Talon705 said:
I tried everything out and was able to get the ringtone to change, but the notifications and alarm sounds don't change. The alarm seems to always be the same sound, but I have noticed at least two different sounds for varying notifications. Not sure if that will influence how well this application works for the Pixel Watch, but I wanted to at least mention it. Thank you for all you hard work to help the community!
Click to expand...
Click to collapse
Try pushing an audio file to the watch and set it again?
Anyway, this worked great for me, the battery life was so-so at first but after a day or so it's noticeably better and snappier. Thanks for your contribution!
GuyInDogSuit said:
Try pushing an audio file to the watch and set it again?
Anyway, this worked great for me, the battery life was so-so at first but after a day or so it's noticeably better and snappier. Thanks for your contribution!
Click to expand...
Click to collapse
You were able to get notification sounds to change on the Pixel Watch? Huh. I guess I'll have to try it again.
I've noticed this watch seems to have a sound for the calendar, a sound for any message app, and a sound for any other general notification – when you got the sound to change, did all of those notifications change, or just the general one?
In any case, though, thank you for the input! I'll try it again tonight and comment if it seems to work.
Oh, I personally haven't done that yet, but it had occurred to me that it could work for you.
I'll give it a shot and see if it does.
Hey, is it possible to change the APN settings somehow?
Does adb give you the ability to edit these settings?
If you mean to use it on a network other than T-Mobile, it doesn't seem it can be done yet. At least not for Mint Mobile, anyway. As far as adb goes, I don't know of any, sorry.
Thank you very much - great work. Im using it to push watchfaces to the pixel watch i´ve made with Galaxy Face Studio and it works great.
First i have had some trouble with Debugging over Wlan - thats a Pixel Watch problem i think.
But i found a good solution:
- setting up my old second mobile phone as Hotspot (there is no need for sim or internet connection)
-connecting my laptop to the phone-hotspot
-deleting the old wlan on the watch, switching BT off and connect to the phone hotspot
-enabling ADB debugging and debugging over Wlan
thats how i got a very save and good connection for the ADB
it doesnt connect with the pixel watch. It does work with the galaxy watch 5 though
edit: working now. Changing DPI is SO helpful. Its always way too high/big on these watches.
is it possible to export the camera app from the galaxy watch 5 and install it on the pixel watch? I would like to use the remote camera shutter app with my fold 4
Motawa88 said:
is it possible to export the camera app from the galaxy watch 5 and install it on the pixel watch? I would like to use the remote camera shutter app with my fold 4
Click to expand...
Click to collapse
Try it, the watch will not break, at most the app will not work on Pixel Watch and already, however, I doubt it will work, it is an app specific to the Samsung universe. Tell here your experience.
A while ago I wrote about alternatives to use the remote camera, in case it helps you.
https://www.reddit.com/r/WearOS/comments/r7a0pq
https://www.reddit.com/r/WearOS/comments/r8ot3i
I tried and it doesn't launch the camera. I can't install google camera on my fold 4 it says parsing error
Can there be anything done about the always on display turning off by itself when you are sitting still? I hate that
Motawa88 said:
Can there be anything done about the always on display turning off by itself when you are sitting still? I hate that
Click to expand...
Click to collapse
I did not understand very well. Do you want to prevent the screen from turning off when "sitting down"?
Motawa88 said:
Can there be anything done about the always on display turning off by itself when you are sitting still? I hate that
Click to expand...
Click to collapse
You mean like an "always on" option? Settings > Display > second-to-last option, Always-on screen.
You could also set the time-out to 30 seconds and the "return to watch face" option to a higher wait time, if that's also something you wanted.
No. The aod turns off sometimes randomly.
please how to pair watch with phone without wiping watch? dont know what to write :
Indicates IP address of the watch (you see it in settings / connectivity / Wi-Fi / "Your Wi-Fi"):
watch is with enabled dev ops, enabled adb with wifi
Thank you.