S Pen SDK for Note 9 - Samsung Galaxy Note 9 Questions & Answers

I was looking at the S Pen sdk documentation that samsung has posted on their site, and it doesn't seem to have been updated for the remote S Pen features. Am I missing something or is it buried deep in there somewhere? The version is 5.1 and was updated in March 15, 2018. I've got some ideas I'd like to play around with concerning the remote S Pen capabilities.

From the Developer website. Current version 5.1 is from March 2018, so looks like they haven't released the new SDK yet.
In the Pen SDK v5.0, Dynamic version is not supported, only it supports Static version
Static version has two types, namely:
Full Version : Supports all features of Pen SDK.
Light version : Only supports simple drawing features of Pen SDK.
       Please download the Full Version for advanced drawing brushes
Click to expand...
Click to collapse

Related

SDK and new Chromecast Update

Just received the following in an email from Google:
Thank you for developing for Chromecast.
Just wanted to let you know that we've updated the Receiver, Chrome, and Android API references.
And today, we've updated both the iOS and Android SDK's to 1.0.1. *This is a bugfix release. *For iOS, it fixes the namespace so that it should be compatible with Objective C++. *For Android there are a few fixes to the network scanning code.
Over the last several weeks we've also updated the sample code on github.com/googlecast
We also released this blog post that may be of interest today:
TITLE: *Chromecast and Google Cast Update
The Chromecast device has been updated to build 12940. *This update will be rolled out over time, and you do not need to take any action to receive it. It contains the following updates:
Better discovery of Chromecast devices
Improved Google Play Movies stability
Additionally, we have published version 1.0.1 of the Google Cast SDK preview, including libraries for Android and iOS, as well as documentation on the Receiver, Chrome and Android APIs. *This is a bug fix update with one key developer facing change for iOS -- ‘namespace’ renamed to ‘protocolNamespace’ to allow Objective-C++ development.
More information about the Chromecast device is available on the Chromecast site. Information about the Google Cast SDK is
Sent from my Nexus 4 using XDA Premium 4 mobile app
Interesting read, the most obvious is that they continue with the "preview" tag. One thing I didn't notice before is the email address for people who want their apps published. So, I guess, if they OK the app, it can be released, regardless of the SDK. I could be wrong though.

Google released Google Cast (Beta)

Google released Google Cast (Beta) with new beta features"
https://chrome.google.com/webstore/detail/google-cast-beta/dliochdbjfkdbacpmhlcpmleaejidimm
This is the *BETA* channel of the Google Cast extension. It is intended for developers and advanced users who want early access to upcoming APIs and features in advance of public release. Most users should install the stable Google Cast extension (https://chrome.google.com/webstore/detail/google-cast/boadgeojelhgndaghljhdicfkmllpafd). The beta channel will often be less stable and contain more bugs.
Click to expand...
Click to collapse
Google Cast Release Notes:
https://developers.google.com/cast/docs/release-notes
Shawn Shen - Yesterday 9:49 PM
Public beta channel for the Google Cast extension
Earlier this month, we made the Google Cast SDK publicly available, allowing anyone to enable multi-screen experiences in their apps/sites. In Chrome, this functionality is provided by the Google Cast extension, which was automatically updated to enable SDK features.
Going forward, we’ll continue to fix issues and add features to the Google Cast extension. Similar to Chrome’s beta channel, today we’ve released a public beta channel for the Google Cast extension, so developers can test out the latest features before they’re released to the public. Our goal in doing this is to work with the community to achieve several goals:
- Input & Feedback: Developer input on the preview SDKs helped greatly in shaping the APIs and user experience of our public SDK launch. We want to make sure that developers and passionate users can stay involved as things evolve.
- Early Access: New SDK features don’t help users until they’re adopted by developers, so the sooner we can get capabilities to developers, the better. We also want to make sure that changes never come as a surprise.
- Stability: We want to make sure that new versions of the Google Cast extension don’t inadvertently break sites that integrate with the SDK. Providing pre-release versions to the community is the best way to ensure we detect and address any issues prior to a public rollout.
The beta Google Cast extension is available immediately, and can be installed from the Chrome Web Store below (note that you’ll need to disable the public Cast extension to avoid conflicts). It updates automatically, so you’ll always have the latest features and fixes. The main updates in this initial public beta are as follows:
- Added support for callback on completion of API script loading.
- Fixes for media metadata inconsistency between Chrome and receiver SDKs.
- A real-time logging window can be launched under “Options”.
- Sender SDK can now extrapolate currentTime.
You can find more information on the beta channel here: https://developers.google.com/cast/docs/chrome_sender#setup. We’re looking forward to your feedback and to experiences that you create!
Click to expand...
Click to collapse
source:
https://plus.google.com/+ShawnShen/posts/aVXSHyceNbR?e=-RedirectToSandbox
In Google Cast extension options there are additionally:
Developer Settings:
Enable Log Window
Additional receiver IPs
"Custom mirroring settings" is unavailable in this version.
Initial source:
http://www.androidpolice.com/2014/0...-should-provide-early-access-to-new-features/

Google Pushes Android Wear 2.0 Back To 2017, Issues Third Developer Beta

Google Pushes Android Wear 2.0 Back To 2017, Issues Third Developer Beta
Google announced Android Wear 2.0 alongside what later became Android Nougat at Google I/O a few months ago, but aside from a second Wear 2.0 developer preview build in July, we haven't heard much since. There's good and bad news on that front: the good news is that Google is releasing a third Wear 2.0 developer preview today with some new features and tweaks. The bad news is that the final release of the software is being delayed.
Wear 2.0's release date has been pushed back from a vague "this fall" window to an equally vague "early 2017" window, presumably so Google can keep testing and tweaking. To that end, Google will release a fourth developer preview build, and the 2.0 update will begin trickling out to supported watches after that.
The biggest addition to the Android Wear Developer Preview 4 is a watch version of the Google Play store that can browse and download watch apps and watch faces without your phone—developers told Google that they wanted watch apps to be easier to find, and this is Google's answer. Text entry still looks painful, and relatively wimpy watch hardware may slow things down, but if the eventual goal is to make watches that can operate independently of phones, this is an important step.
The watch-exclusive store also means that developers can release watch apps that are totally independent of phone apps. Historically, Wear apps have been bundled in standard phone apps—download a phone app, and then the wearable app would be downloaded to the watch from the phone. Apps can still be downloaded and installed this way, but as of Wear 2.0 it will no longer be strictly necessary.
Other tweaks in the new preview build include permission requests for watch complications, a "recycler view" that lets developers display vertical lists of items in a way that will look good on square and round watch faces (the Wear 2.0 app picker uses the same view), and inline actions for new notifications (you would previously need to swipe down on a notification to expose a quick action menu).
Whether your new watch will receive Wear 2.0 is going to be up to its manufacturer, at least in part. The LGE Watch Urbane 2nd Edition and Huawei Watch are safe bets since they're still the only devices you can use to test these preview builds, but we already know that early Wear watches like the LG G Watch and first-generation Moto 360 will be missing out.
There's a toggle in Settings for NFC on LG Urbane 2nd LTE on Preview 3.
kalinskym said:
There's a toggle in Settings for NFC on LG Urbane 2nd LTE on Preview 3.
Click to expand...
Click to collapse
What does that really have to do with this article?
Just for the note: The setup wizard only finishes in the third developer preview if the system language of BOTH watch and phone are English (US). Did not test other english variants. It hangs at the setup screen if I select German for any of the devices.
Of course, you also need to join the beta group of the android wear compagnion app as stated in the install doc (Same symptom if not done).
Installing wear apps from normal android apps with embedded wear apps:
For windows users: see the post below (Thanks for the tool!).
Otherwise:
1. Enable developer options on wear device & adb access.
2. Download the normal android apk.
3. Open the apk with a zip tool.
4. Extract the wear apk from the folder that is referenced in "META-INF/MANIFEST.MF" (search for the string 'apk') in the apk file.
5. Connect the watch to your pc & grant adb access (if not done already).
6. In a shell / command promt type : "adb install <name-of-the-wear-apk>.apk" (Adb drivers & adb tools must be installed therefore).
Diewi said:
Just for the note: The setup wizard only finishes in the third developer preview if the system language of BOTH watch and phone are English (US). Did not test other english variants. It hangs at the setup screen if I select German for any of the devices.
Of course, you also need to join the beta group of the android wear compagnion app as stated in the install doc (Same symptom if not done).
Installing wear apps from normal android apps with embedded wear apps:
1. Enable developer options on wear device & adb access.
2. Download the normal android apk.
3. Open the apk with a zip tool.
4. Extract the wear apk from the folder "res/raw" in the apk file.
5. Connect the watch to your pc & grant adb access (if not done already).
6. In a shell / command promt type : "adb install <name-of-the-wear-apk>.apk" (Adb drivers & adb tools must be installed therefore).
Click to expand...
Click to collapse
for installing apps, you can use this
http://forum.xda-developers.com/huawei-watch/general/android-wear-2-0-apk-installer-t3472766

Are you upgrading to 10/OneUI 2.0 yet?

Hello there,
Since Android 10 is finally out in final version for our beloved Note 9 Exynos, how many of you are upgrading, and why? Also, for whom will choose to stick with Pie, again, why? And last, for those who are still on Oreo, what are you waiting for?
Personally, I didn't see that much new features that I really want to use right now. Mostly some tweakings here and there in some interfaces, but nothing really new, looks more like a modded version of Pie . I'm not a fan of the new gestures either, I think I'd keep the navbar anyway so... I'm gonna wait a moment before upgrading. And I'm mostly waiting for Swift Installer/substratum/Goodlock compatibility too, can't live without those
The thing I'd like to try out is DeX on PC, but again I don't really have a need for it. I'm more sad to lose Linux On Dex when I'll upgrade.
What are your opinions?
Mwyann said:
Hello there,
Since Android 10 is finally out in final version for our beloved Note 9 Exynos, how many of you are upgrading, and why? Also, for whom will choose to stick with Pie, again, why? And last, for those who are still on Oreo, what are you waiting for?
Personally, I didn't see that much new features that I really want to use right now. Mostly some tweakings here and there in some interfaces, but nothing really new, looks more like a modded version of Pie . I'm not a fan of the new gestures either, I think I'd keep the navbar anyway so... I'm gonna wait a moment before upgrading. And I'm mostly waiting for Swift Installer/substratum/Goodlock compatibility too, can't live without those
The thing I'd like to try out is DeX on PC, but again I don't really have a need for it. I'm more sad to lose Linux On Dex when I'll upgrade.
What are your opinions?
Click to expand...
Click to collapse
Still no upgrade here ? middle east user N960F/DS
There is no question about should you upgrade or not. Unless you want to keep vulnerabilities, you have to update to the newer OS (if any) to get the latest security fixes.
fabienpascal said:
There is no question about should you upgrade or not. Unless you want to keep vulnerabilities, you have to update to the newer OS (if any) to get the latest security fixes.
Click to expand...
Click to collapse
True. Or to get newer vulnerabilities ?
Will upgrade the second the official OTA drops. I'm a non-root user and have been waiting for the battery limiter feature that's finally present in One UI 2.0.
Edit: No toggleable charging cap in One UI 2.0. It seems the battery limiter means preventing draining your battery too low when using wireless power sharing in the S10 and up.
Waiting for a decent rom like The Galaxy Project to offer it. Only one so far is Dr Ketan's which won't even boot for me despite 3 clean download and install attempts.
FerretallicA said:
Waiting for a decent rom like The Galaxy Project to offer it. Only one so far is Dr Ketan's which won't even boot for me despite 3 clean download and install attempts.
Click to expand...
Click to collapse
Have you updated your bootloaders and modem files to the latest version?
It usually works with the bootloops.
all the best
Except dex on windows and say good bye to linux on dex, nothing really new.
Only one big problem, as samsung block you to revert back to a stable pie os version. Latest pie is a no with bootloader 4.
Its all marketing I see
I received it yesterday in Morocco, I was using VPN (Germany) but I can't confirm, it is a bless, smooth and new features, I tried dex on pc : amazing, I still need to Check the battery
Just a quick update, to tell that I've finally upgraded because the "new update" notification kept showing up and I got bored of it. It went pretty well, and I'm trying to get used to the new gestures after all, I'll see if I can use them nicely. I'm only afraid to be confused when using my older S7E which doesn't have those. I'm using Hexed+ as a replacement for Swift Installer, waiting for the latter to be updated. Also waiting for Goodlock apps to be updated (for example, to put the clock on the right side again).
No upgrade yet i m from The Balkans. Still waiting for the update OneUI 2
No upgrade. i am afraid of battery life. On pie april patch, my phone battery last longer than pie july patch. I am living with it. but i do not want to lose more juice of battery. will upgrade if battery life improves.
Mwyann said:
Just a quick update, to tell that I've finally upgraded because the "new update" notification kept showing up and I got bored of it. It went pretty well, and I'm trying to get used to the new gestures after all, I'll see if I can use them nicely. I'm only afraid to be confused when using my older S7E which doesn't have those. I'm using Hexed+ as a replacement for Swift Installer, waiting for the latter to be updated. Also waiting for Goodlock apps to be updated (for example, to put the clock on the right side again).
Click to expand...
Click to collapse
Can you confirm what else was working in pie and not working in Q ?
Also give a try with linux on dex.
For clock on right you can use systemui tuner.
Software update notification can be disabled too.
LucianGL30 said:
Can you confirm what else was working in pie and not working in Q ?
Also give a try with linux on dex.
For clock on right you can use systemui tuner.
Software update notification can be disabled too.
Click to expand...
Click to collapse
What's not working:
- Linux On Dex (displays an error like "you must be on latest firmware", so I guess it doesn't recognize the phone as compatible anymore, which is the case as I've read - it's a kernel issue)
- Substratum and other overlay systems like Swift Installer (you could still install unsigned overlays on Pie on the Note9 but that's a thing of the past now. Hopefully there's Synergy (https://play.google.com/store/apps/details?id=projekt.samsung.theme.compiler) which allows using some overlays by using themes - the Android 10/OneUI 2.0 compatibility is in progress).
- Some SystemUI controls, like the clock position (I've tested it all, even the tips involving right_clock_position)
- Good Lock, which isn't updated yet (and it should solve the clock position problem)
So fat that's the only things I miss on my Pie install. Most of them will simply become available again soon, or can be replaced by other means, so that's not so bad. About the new gestures though, I miss my browser shortcut I had setup with NavStar, and also I kinda don't like the wasted space it introduces to allow for gestures. Well, I'll see when NavStar is updated it I simply go back to the navigation bar (I'll be able to use some gestures with OneHand Operation +).
About Linux On Dex problem, on my rooted S7E I'm using Linux Deploy (https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy) but on my unrooted Note9 I'm currently trying a combo of Termux (https://play.google.com/store/apps/details?id=com.termux) and AnLinux (https://play.google.com/store/apps/details?id=exa.lnx.a).
And I couldn't disable the notification, didn't find a way to do it at the time. I guess now it's too late
Mwyann said:
What's not working:
- Linux On Dex (displays an error like "you must be on latest firmware", so I guess it doesn't recognize the phone as compatible anymore, which is the case as I've read - it's a kernel issue)
- Substratum and other overlay systems like Swift Installer (you could still install unsigned overlays on Pie on the Note9 but that's a thing of the past now. Hopefully there's Synergy (https://play.google.com/store/apps/details?id=projekt.samsung.theme.compiler) which allows using some overlays by using themes - the Android 10/OneUI 2.0 compatibility is in progress).
- Some SystemUI controls, like the clock position (I've tested it all, even the tips involving right_clock_position)
- Good Lock, which isn't updated yet (and it should solve the clock position problem)
So fat that's the only things I miss on my Pie install. Most of them will simply become available again soon, or can be replaced by other means, so that's not so bad. About the new gestures though, I miss my browser shortcut I had setup with NavStar, and also I kinda don't like the wasted space it introduces to allow for gestures. Well, I'll see when NavStar is updated it I simply go back to the navigation bar (I'll be able to use some gestures with OneHand Operation +).
About Linux On Dex problem, on my rooted S7E I'm using Linux Deploy (https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy) but on my unrooted Note9 I'm currently trying a combo of Termux (https://play.google.com/store/apps/details?id=com.termux) and AnLinux (https://play.google.com/store/apps/details?id=exa.lnx.a).
And I couldn't disable the notification, didn't find a way to do it at the time. I guess now it's too late
Click to expand...
Click to collapse
What about SystemUI Tuner , doesn't let you to move the clock? It's on play store.
For linux like ubuntu kali debian arch parrot fedora manjaro give a try with AndroNix ,same is on playstore.
For navbar, you can get back as in pie from settings.
LucianGL30 said:
What about SystemUI Tuner , doesn't let you to move the clock? It's on play store.
For linux like ubuntu kali debian arch parrot fedora manjaro give a try with AndroNix ,same is on playstore.
For navbar, you can get back as in pie from settings.
Click to expand...
Click to collapse
As I said in my reply, I did try SystemUI Tuner (I used it on Pie too), and it just doesn't work, the clock doesn't move anymore.
I indeed tried AndroNix and one of their optimized OS, it's good stuff
There was a adb command to move clock too
LucianGL30 said:
There was a adb command to move clock too
Click to expand...
Click to collapse
Looked for this too, but I always find commands that gives permissions to SystemUI, which doesn't really help If you have something to try out, I'd be happy (but if it involves the keyword right_clock_position I can already tell that it doesn't work)
Do not like an iOS like software experience thanks to Google wanting to copy Apple.
Mwyann said:
Just a quick update, to tell that I've finally upgraded because the "new update" notification kept showing up and I got bored of it. It went pretty well, and I'm trying to get used to the new gestures after all, I'll see if I can use them nicely. I'm only afraid to be confused when using my older S7E which doesn't have those. I'm using Hexed+ as a replacement for Swift Installer, waiting for the latter to be updated. Also waiting for Goodlock apps to be updated (for example, to put the clock on the right side again).
Click to expand...
Click to collapse
Updated and so far so good except that annoying white/ black bar at the bottom of Gboard . Any ideas on how to get rid of it ?

Desktop Mode in Android 11

Hi, I'm not a Pixel owner but I've heard about a full desktop mode being baked into Android 11. Has anyone had to the to look for or test it out on the latest beta release?
I am aware that it was an experimental feature in 10. I'm a fan of Samsung Dex and this is one of the few things that prevents me from switching.
There is no desktop mode on any Pixel devices.
In developer option there is a experimental desktop mode. It was there in Android 10 and Android 11 beta 1 also, but i never tried it.
I haven't flashed 11 yet but from my understanding it's in dev options, is still experimental and requires connection through HDMI.
Sent from my coral using XDA Labs
Haxxan7 said:
In developer option there is a experimental desktop mode. It was there in Android 10 and Android 11 beta 1 also, but i never tried it.
Click to expand...
Click to collapse
Still experimental I see... Thanks for your replies everyone.
Just tried it on my Pixel 4XL with latest Beta of Android 11. No go. I don't know why google refuses to enable HDMI out over USB-C on it's devices when nearly every other device supports it. Chromecast is not a viable alternative.

Categories

Resources