yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] mrYoussef135:
New release 1.13.0 :

+ Updated the interface theme.
[Android Apps and Games] travisn000:
Kindle app compatability?

Will this work with Amazon's Kindle app?

Any users care to post their experiences?

Thanks!
[Android Apps and Games] mrYoussef135:
Sorry, I can't help you about that since I don't have an Amazon Kindle.
[Android Apps and Games] mrYoussef135:
New release 1.14.0

+ Updated the user interface.
[Android Apps and Games] mrYoussef135:
New release 1.15.0 :

+ Per-App Settings.

+ Selecting the apps that automatically activate scrolling when they are opened.

+ Selecting the apps that automatically deactivate scrolling when they are opened.
[Android Apps and Games] mascondante:
Thank you for all your hard work and dedication to the app and your community. I haven't tried this app in a while but I'm happy to see the constant updates. I'll give it another try today and let you know my experience.
[Android Apps and Games] mrYoussef135:
New release 1.16.0:

+ Added support for Tasker.
[Android Apps and Games] last1left91:
Does it simulating an invisible finger sliding on the screen...refresh chrome...

This app is amazing...still there would be some remarks:

1) When trying to use the tilting app in Chrome, when it goes from the top it refreshes the page...what can I do around this

2) Per App Settings...

Well, I'm using the app using the widget most of the time...when I'm activating perApp settings I can no longer stop the tilting by displaying widget unless I exit the context app...I feel like driving a car with no brakes :))

What about giving us the option to display the widget too :)...like a force stopping..I guess you got my point.

And the last thing...how much is it to get full features...this app is amazing!

When I bought my S5 G900F phone, 1 year ago I tried this feature: Smart Scroll but it was very buggy and worked only in stock browser...you made something unbelievable with this app...what's the price for the full features? :) Thanks in advance!
[Android Apps and Games] hawkdown77:
How can i change the inclination angle?? Im getting problems whith little inclination angle
[Android Apps and Games] mrYoussef135:
Thank you for your words.

1 ) You can disable the "pull to refresh" feature (see here)

2) When you are in a per-app context , you can switch to widget context by deactivating the scroll using the pause button on the widget.

As for the upgrade fee, it's about 1.5 $
[Android Apps and Games] mrYoussef135:
Do you mean that the app is very sensitive to the inclination or that you want a wider angle for the neutral position ?

For the sensitivity part you can change it in the app settings.
[Android Apps and Games] last1left91:
Actually I set it like this...created a toggle task in Tasker and activated the Tilting Function by using GMD Gestures...click(3 points) in the middle of the screen and this way I can start and stop the Tilting function anytime...this way I don't have to use PerApp Settings at all...Tasker integration helps me a lot!

That price is nothing considering what it can do...

As for the refresh feature is still a problem...because also Facebook app has this pullup gesture implemented and I guess I should disable it per app...anyway I will take a look right away on reddit...Thanks a lot for your prompt answer...I will definetely buy the full version to support its development...Thanks again!

Do you think you can add in the future a tasker option/intent so we can switch from vertical to horizontal scrolling on the fly?:)...or is it already implemented?:)

Last edit: Purchased...keep the good work!!
[Android Apps and Games] mrYoussef135:
Actually you can change it in the widget, and I may also add an equivalent tasker option.
[Android Apps and Games] MarcWhoo:
Nice Idea!
[Android Apps and Games] KostisTTT:
Hello, guys.

I was using this app with my previous ROM (CM Sultanxda MM), but after Nougat installation (lineage OS), I am getting the message "Server not started".

Oneplus 3T, Lineage OS (Sultan), Magisk, Xposed

Any ideas??

Thanks in advance
[Android Apps and Games] Ilyadev:
Nice. Will test as soon as get home
[MX Player] sharwood:
Having problem updating to 1.7.31?! It comes up saying "couldn't install to USB storage or SD card" ?!?! Anyone else have this issue???? I'm running a Lenovo A8 (8" tablet) running Android 4.4.2 the MX Player Pro is in main memory as can't be moved to SD card.
[MX Player] bleu8888:
Hmm. there is a configuration for it. But it is not changed for long time since most people uses Froyo.

Would you try any other app if it can be moved to sdcard?
[MX Player] sharwood:
Yes other apps have moved to SD card

I've moved other apps to my SD card in the past but some programme won't let you I guess MX Player Pro is in this camp.
[MX Player] sharwood:
All OK now :)

"I tried moving an app to SD card and it had a problem so did the old 'switching off and on again' and it sorted out the problem and allowed me to move the app over and also update MX Player Pro so all good now" :)
[Verizon HTC One (M8)] ImHavenHart:
Hello,

I have a Verizon M8 that i'm using with AT&T. Is there a way to convert my Verizon M8 to AT&T so that I can get LTE? Or can I at least flash the AT&T radio? I noticed this video shows a method for converting Verizon M8 to Tmobile https://www.youtube.com/watch?v=6GhybCyd4Pg He is getting Tmobile LTE with Verizon M8 no problem.

If someone can point me in the right direction that would be great!
[Verizon HTC One (M8)] Sam3gX:
This phone doesn't have the bands for At&t LTE. Best you would get is HSPA+.
[Verizon HTC One (M8)] ImHavenHart:
Yes I know it doesn't have compatible bands for AT&T LTE. It doesn't have compatible bands for Tmobile LTE either, but someone demonstrated how to convert it so now he's using the Verizon M8 and is able to get Tmobile LTE without a problem. So there seems to be a way.
[Verizon HTC One (M8)] ImHavenHart:
I figured it out. For anyone else out there that has a Verizon M8 and are using it on AT&T, you can convert your phone to the AT&T variant. I'm getting LTE but not constantly, it switches between LTE and HSDPA but it's staying mostly on LTE. Yay!
[Verizon HTC One (M8)] M9guy:
So how did you get it to work ? On the verizon forum all there is, is for converting to tmobile lte and nothing on converting to get at&t lte. Also what lte bands of at&t are you running on ?
[Verizon HTC One (M8)] ImHavenHart:
Hey there. I posted how I did it somewhere in the AT&T forum. I'm not sure where the post is though as it's been a few months and I don't have the M8 anymore. I sold it and bought a One Plus One, then sold that and bought a Note 4, so that was a couple of phones ago. :(
[Samsung Gear 2] noellenchris:
I think your thread should probably go in the Dev section for Tizen. Have you made any development? If your want it moved, report your own post with the button in top right labeled report. You can then suggest your thread be moved to the new Tizen Development section. Ok, I wish you all the luck, you seem to be very talented programmer/dev. Thanks for your contributions.

Chris
[Samsung Gear 2] javispedro:
Well, some mod already moved this thread from Development, where I originally posted it, into Q&A. This is not exactly "Tizen" development (SAP is used in may Samsung devices seemingly).

Yes, lots of progress. I have been able to write a program that connects to the Gear2 from my PC, succesfully "completes" the setup program and synchronizes the date&time. Things like changing the background color etc. are now trivial. I will soon port it to my Jolla.

I am now looking into how to send notifications to the watch. I've not been able to get Gear Manager to actually send any notifications (to use as "reference"), because goproviders crashes when I try to simulate notifications on my android_x86 VM :(

If anyone can send me an HCI / Bluetooth packet capture of their Android device while it is sending notifications to the Gear2 I would really appreciate it.

Unfortunately, the main problem here is that Samsung uses some cryptographic authentication as a form of "DRM". I am not exactly sure why.

There was no way for me to discover how the crypto worked so I took the unclean approach and dissasembled their crypto code (libwms.so). That means there's no way I would be able to distribute the code now without risking a lawsuit from Samsung.

Sadly this means that while I can distribute the protocol specifications I obtained, legally distributing "Gear Manager replacements" is probably impossible.
[Samsung Gear 2] noellenchris:
Ya, I was kinda in a Gear 1 mind set, and they have separate threads for Android and Tizen....:P

Chris
[Samsung Gear 2] Antartica:
I would gladly write a MIT-licensed C library implementing your protocol specifications. That would be correctly following the chinese-wall approach to reverse-engineering, right?

Anyway, AFAIK, being in Europe decompiling for interoperability purposes is allowed -- I know that wikipedia is not to be taken at face value, but: en.wikipedia.org/wiki/Reverse_engineering#European_Union
[Samsung Gear 2] javispedro:
Well, the problem is not the protocol specifications per se, which I'm actually quite confident I'd be able to redistribute (I'm in EU). The problem is the cryptography part, which is basically ripped off from the Samsung lib "libwsm.so" . Unless we can find out what cryptographic method that lib uses, distributing alternate implementations Is a no-go.
[Samsung Gear 2] Antartica:
If you have the time, I don't mind researching the possible crypto used (although I've only studied DES/3DES, AES and Serpent, hope that whatever scheme used is not very different from them).

Some ideas to start from somewhere:

1. As you have used its functions, it is a block cipher? I will assume that it is.

2. What is the key size and the block size?

3. Are there signs that it is using a stack of ciphers? (that is, applying one cipher, then another to the first result and so on)
[Samsung Gear 2] javispedro:
Hello, I've not forgotten about this, just somewhat busy and been using the MetaWatch lately :)

1. Yes it is clearly a block cipher, and the block size Is 16bytes.

2. I don't know about the key size, it is obfuscated.

3. Doesn't seem like a stack of ciphers. It looks like some overcomplicated AES. But to be honest AES is the only encryption I know of :)

By the way I think I will upload my current test "manager" source code to somewhere after removing the crypto specific files . Since the protocol itself has been obtained cleanly. Note I've used Qt (not the GUI parts) so it's useless for creating a library; the code will probably need to be rewritten to do so, but it may be useful as "protocol specs".
[Samsung Gear 2] Antartica:
No problem. Curiously, I've transitioned from the metawatch to the Gear1 fully (null rom, not pairing with bluetooth to the phone but gear used as a standalone device).

[off-topic]I'm not using my metawatch anymore. I was modifying Nils' oswald firmware to make it prettier and to have some features I wanted (calendar, stopwatch), but it was very inaccurate, supposedly because of missing timer interrupts (the existing LCD drawing routines were too slow). I rewrote the graphics subsystem just to stumble into a known mspgcc bug, and trying to use the new redhat's mspgcc resulted in more problems (memory model, interrupt conventions). In the end I couldn't commit enough time to fix that and my metawatch is now in a drawer[/off-topic]

Returning to the topic:

Good. We can at least say it isn't DES/3DES nor blowfish (64 bits block size). Regrettably there are a lot of ciphers using 128-bits block size; that I know: AES, Twofish and serpent.

Perusing the wikipedia there are some more of that size in use: Camellia, sometimes RC5 and SEED.

I understand that to mean that you cannot use that library passing your own key, right?

What a pity! One way to test for these ciphers would have been to just cipher a known string (i.e. all zeroes) with a known key (i.e. also all zeroes) and compare the result with each of the normal ciphers :-/.

Perfect. I don't need anything more :).
[Samsung Gear 2] Antartica:
About that 65-byte bigint... that is a 520-bit key. The usual length of ECDSA keys is exactly 520-bits, so we may have something there: it is possible that they are using ECDSA signing (just like in bitcoin, so there are a lot of implementations of that code).
[Samsung Gear 2] Antartica:
Not forgotten about this!

Just an status update:

I'm still in the process of defining the API of the C library using javispedro's sources as template.

It's tougher than I originally supposed because the C++ code has a lot of forward-declarations of classes, which is very difficult to map into C. To counter that I have to move elements between structures and I'm not so comfortable with the codebase yet.

And then there is still the hard work of translating the Qt signals/slots to plain' old callbacks... and implementing the bluetooth part using bluez API... and... well, I hope that is all.

Anyway, patience :).
[Samsung Gear 2] javispedro:
I've now had access to a Samsung S2 and thus I have been able to obtain more traces. The latest Git now contains code to connect to the notification manager service, thus allowing to send notifications from the phone to the watch.

That was the last missing part to be able to use the Gear 2 as a 'daily' smartwatch with my Jolla, so I've now also ported the code to run under Sailfish. In fact I'm using this setup at the moment. My first comment is "wow the vibrator IS weak".

You can find a log of sapd's (ie my code) startup qDebug() messages; they may be useful (if you can't yet get your code to run)

I suspect that there may still be some important battery issues because the watch keeps printing error messages about SAP services it can't find on the phone (and instead of sleeping, it starts busy polling for them.... :/ ). It does not seem to happen while the watch is out of the charging cradle, so it may not be important, but not sure yet.

As for the encryption, I'm not sure how to proceed. I could describe the code to you, but that would be risky, because I don't understand what it does. Thus the only way (for me) to describe it would be to pass on the mathematical formulas/pseudocode ... Apart from that, we also have the problem of the keys...

They do use ECDH indeed, and they link with OpenSSL and import the ECDH functions. However it's not clear if they use ECDSA; while the crypto algorithm DOES resemble DSA, I cannot fully identify it.
[Samsung Gear 2] Antartica:
Congratulations for managing to make it work with the Jolla :).

I have finally found a suitable "flattened" class hierarchy as to be able to map your code into C; see the attachs. Basically, I have to move the functionality of SAPConnectionRequest, SAPSocket, CapabilityPeer and SAPConnection into SAPPeer, and then it is suitable for my needs.

If you manage to describe it using mathematical formulas as in

http://en.wikipedia.org/wiki/Ellipt...ture_Algorithm#Signature_generation_algorithm

it would be perfect, but I reckon that to be able write that you need intimate knowledge of the code and don't know if you have time for that :angel:

And identifying the hash function used would be a problem in itself...

One idea: how about a ltrace so we have the calls to the openssl library? That may uncover new hints.

Anyway, I have a lot of work before me until I need that, so don't fret over it.
[Samsung Gear 2] gidi:
Hi there! Any chance that the Gear can (really) work with an iPhone?
[Samsung Gear 2] Digiguest:
agreed. Needs iPhone support please.
[Samsung Gear 2] javispedro:
You may want to look at the official Samsung SDK docs to match their class hierarchy. I tried to match my hierarchy to theirs, but this happened very late in the development process, so there is some weirdness.

I more or less know what it is doing with OpenSSL, but that's because I looked at the dissassembly. They use OpenSSL for key derivation (ECDH), but the actual cryptographic algorithm is their own. This 'block cipher' is the part they have tried to obfuscate. Not much, but still enough to require more time than what I have available :) It is basically a set of arithmetical operations with some tables hardcoded in the libwsm.so binary, so no external calls to any library. The hardcoded tables are probably derivated from their private key, which is most definitely not on the binary. In fact I suspect this is basically AES with some changes to make it hard to extract the actual key used, so that's where I've centered my efforts.

Technically it should not even be copyrightable, so maybe I could just redistribute my C reimplementation of the algorithm, but as with any other DRM who knows these days... and that still leaves the problem of the tables/"private key".

Well you are welcome to implement one such iPhone program yourself. Will be happy to resolve all the protocol questions you have.

(But please stop with the nagging).
[Samsung Gear 2] Digiguest:
Wasn't nagging at all. Just agreeing with him. I am no programmer so I have to rely on others for answers. Sorry if you thought otherwise.

Looking for to see more work on it though. Keep it up.
[Samsung Gear 2] Duobix:
Hi there! Nice work on getting Gear2 to work with Jolla.

I'd love to get Gear1 to work with WP8.1. Do you have the code for Jolla

on github/bitbucket so I could give it a peek? :D Thanks in advance.
[Samsung Gear 2] Antartica:
javispedro had the sources in gitorius, but they are not there anymore (surely related to gitlab buying gitorius).

I attach a tarball with javispedro sources as of 19 October 2014.

Note that it lacks the files implementing the crypto, so just porting it is not enough to be able to communicate to the gear. OTOH, I know that there are some differences in the protocol between the Android Gear1 and the Tizen Gear2 (if the gear1 has been updated to Tizen, it uses the same protocol as gear2). Specifically, to be able to communicate with both watches, the gear manager package has both gear manager 1.7.x and gear manager 2.x. javispedro's code implements the gear 2 protocol.

Personally, I have my port on hold (I have problems with bluetooth in my phone, so there is no point in porting sapd right now as I would not be able to use it).
[Samsung Gear 2] javispedro:
I'm still alive too :)

sapd has been moved to https://git.javispedro.com/cgit/sapd.git/ .

I actually started cleaning it a bit , but so far i only moved the sailfish specific parts into an external library.

I'm planning to get a Gear S via a promotion which means that the project might get a bit more steam from my part.

The crypto/DRM "problem" is still unsolved (meaning: the only way to actually use this publicly is by using samsung's binary). I've tried putting some pressure on Samsung from the Tizen side to actually open up SAP, but silence has been the only answer so far...
[Samsung Gear 2] Antartica:
:)

(off-topic)

Is sapd really needed for the gear s? I thought that a watch-phone would be best used as standalone (or with a bluetooth earphone like the "HTC mini+", "Sony BRH10" or "Samsung HM5100" although of those only the samsung would work with the watch AFAICT).

I say this because I've been pondering getting a gear S myself now that there is some traction in XDA to port some android to it after the success with the gear2 and android wear . In the end I will pass as I can't justify such expense only for toying (the cheapest one I have been able to find "new" is 269EUR at amazon.de, and second-hand is not really cheaper than that -- they go for around 250EUR).

If (and it is a big IF) they can port CM11 to the gear S, a sailfish port to it could be doable ... and that would be really interesting

(end off-topic)
[Samsung Gear 2] javispedro:
From what I've been able to see so far, it is still basically a Gear 2 with a larger screen, with a dialer that can actually place calls and programs that can access the web, either via direct 3G or a "new" IP bridge mode in SAP (which I assume is going to be trivial to implement once I get my hands on it).

Most of the builtin software is pretty much the same. One still cannot install programs on it without sap (or sdb). I also assume synchronization of files (voice memos, etc.) still requires it.

In fact, I wouldn't be surprised if it turns out you cannot set time/date/timezone from the watch itself, as in Gear 2 (fortunately, that is something I already know how to do via sapd).

Unsurprisingly I guess, my thoughts are more or less around the same lines. :)

Even if the stock Sailfish interface doesn't work at all, I could probably make one for the Gear (reusing all the Sailfish middleware) much easier than on top of the Samsung middleware.
[Samsung Gear 2] Antartica:
But, isn't tizen too limited? I've my gear with the android ROM (null) just for the hackability (able to put new binaries, able to connect to the internet using bluetooth, install programs from the watch using f-droid, etc). With that it is usable as a watch (alas, without notifications, but my life is not that interesting so that I need them in the watch :angel: )

About porting CM11 to the gear S, it seems possible, but the TODO list that biktor_gj posted is somewhat daunting (i mean this one: http://xdaforums.com/showpost.php?p=60789398&postcount=95).

About the interface: I've been happy using nova launcher in the gear with standard android apps (frequently used: coolreader, narau, kana drill, kanji draw, opera classic, 2048, f-droid, vlc, ghost commander, nectroid, opensudoku, urecord...). My bet is that the sailfish interface "as is" would be usable, even if not ideal.

EDIT: Re-reading my post,it sounds too pessimistic. I'm not. I'm hopeful on the viability of a port. The point I was trying to do is that it will be a lot of work, even a little more than the effort required for the wear port to the gear2. And it is difficult to have a developer commit as much time as biktor (I'm really impressed by his commitment), so it will be a long road ahead. If only it was a little cheaper (and had a camera, which is my other grip with the gear s)...
[Samsung Gear 2] Duobix:
Gear 1 was originally called Galaxy Gear, it had android. But Samsung gave an update to Tizen, and now it's able to run it.

I simply don't care about the protocol of communications Phone<->Android Gear, as the watch can run what I want already.

The Tizen seems better in terms of battery life (and developing a communication app for WP for tizen watches seems more future proof).

Thanks for a fast reply, anyways!

Moving sailfish specific parts into external library seems like a lot of help for me!

BTW, what is the exact name of the binary we are speaking here about?

Anyways, thanks for fast reply, guys!
[Samsung Gear 2] javispedro:
libwsm.so
[Samsung Gear 2] javispedro:
So I just got a Gear S (cheap -- can't complain). I had to make a few changes to get my implementation working with it (different knocking sequence), but now it works as good as the Gear2. It's clearly the same protocol and the same crypto, including keys.

The "IP bridge mode" turns out to be a plain HTTP proxy, which they wrap inside their protocol (Samsung's well-known NIH syndrome). This proxy is used by the stock News app at least.

And they've added some kind of acknowledgement-based flow control (on top of Bluetooth's one -- more NIH), but it only applies to some services, including the above proxy. Until I fix that I'm getting hammered by timeout packets which seem to kill battery life.

It seems that there's no end to the amount of overengineering Samsung can pull on this :)

I guess once I get web + notification forwarding and remote music control working I'll be happy.