Related
[Challenge] Why is "because X phone won't work with Gear Manager" acceptable?
I find this hard to believe and a slightly lazy answer to a common problem. There is obviously code in the APK that refuses to work on any non-Samsung device. Dozens of threads exist with people offering up the entire Gear APK catalog, some trying to get it to work on Nexus & and others.
fOmey and others have reverse engineered the entire ROM, but no one has figured out a way to "fix" one single app to allow it to work with all phones?
Is this not a work-in-progress somewhere? It's certainly not in any thread I have found.
What are the limitations to such a venture? Has it been tried? Is there a copyright issue? What reason has this not been attempted?
Our community has done some amazing things over the years and this site is the go-to place for rooting and hacking. There has to be one sole out there willing to give this a shot.
I am, by no means, a programmer or coder. I would take this up, but I do not have the skillset. Best I can do is go through XML files and the like hoping to find "if X=Z then A" and remove it.
Ultimately this would give us the missing companion to null_ that allows notifications and interactivity (i.e. Music player controls, etc)
So-- any takers?
I have a Nexus 5, even with the app fully running, I can only get the phone call part to work - talk/listen/incoming caller contact name
The way to get around unsupported device is with the GearManagerStub apk
I've had a bit of a search through most of the code, and from what I can tell all the apks are included so can only conclude there must be something in tw framework. Or I missed something...
http://forum.xda-developers.com/showthread.php?t=2549058
Brendo said:
even with the app fully running, I can only get the phone call part to work - talk/listen/incoming caller contact name
Click to expand...
Click to collapse
This is not helped by the app. I have mine tethered to an iPhone 3gs(not by choice) and it works fine with no software at all.
styz said:
This is not helped by the app. I have mine tethered to an iPhone 3gs(not by choice) and it works fine with no software at all.
Click to expand...
Click to collapse
To load the gear manager app, it is.. You simply connected your gear via bluetooth.
The gear manager app pushes notifications to the gear.
Without the GearManagerStub.apk it fails to load, its depends on this particular app.
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
BarryH_GEG said:
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
Click to expand...
Click to collapse
I am purchasing home automation items and bluetooth adaptors for my vehicle so I don't think of this as a toy. I consider it a great step forward.
fOmey said:
...Without the GearManagerStub.apk it fails to load, its depends on this particular app.
Click to expand...
Click to collapse
I installed the stub and the gearmanager apks and it still gave me a 'unsupported device' message. *sadface*
therealduckie said:
I am purchasing home automation items and bluetooth adaptors for my vehicle so I don't think of this as a toy. I consider it a great step forward.
Click to expand...
Click to collapse
Just because you can doesn't mean you should. Why would an underpowered device with a 315mAh battery, 512MB of RAM, and a 1.63" display be the best "tool for the job" you described? Especially when it requires a host in near-by proximity for the majority of its functions? It's great what people are doing with the Gear outside the mission Samsung released it for but, like I said before, you're talking about parlor tricks more for sport than serving a function unachievable by better means; some of which are more practical. And if you're trying to use the Gear while driving, especially if you've shrunk the DPI with a launcher, good luck. It's hard enough using the basic functions and S Voice while driving without ending up in another lane. I'm not criticizing everyone's ingenuity and cleverness just pointing out how impractical some things can appear when you take in to account what the Gear really is; a shamefully low-spec, low functionality Android "phone" with a tiny screen that happens to have a wrist band.
BarryH_GEG said:
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
Click to expand...
Click to collapse
That's why this is a challenge
Im intrigued.. I want to figure this out, I prefer to use AOSP. Iv been forced to go back to TouchWiz since owning a gear.
I might have to do some more digging around.
therealduckie said:
I installed the stub and the gearmanager apks and it still gave me a 'unsupported device' message. *sadface*
Click to expand...
Click to collapse
Depends how you do it? I moved the apk to system/app and then had to install it (so that it was in data/app as com.whatever as it looks for apk based on that name). May not need it in system app anymore
Which phone?
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
fOmey said:
That's why this is a challenge
Im intrigued.. I want to figure this out, I prefer to use AOSP. Iv been forced to go back to TouchWiz since owning a gear.
I might have to do some more digging around.
Click to expand...
Click to collapse
Do you know how much touchwiz is in google edition roms? Does gear fully work with ge roms?
Brendo said:
Depends how you do it? I moved the apk to system/app and then had to install it (so that it was in data/app as com.whatever as it looks for apk based on that name). May not need it in system app anymore
Which phone?
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
Do you know how much touchwiz is in google edition roms? Does gear fully work with ge roms?
Click to expand...
Click to collapse
Sadly I was able to test extensively using GE, although I did find all the initial APK's installed & completed successfully.
I didn't get a chance to pair up completely, the base keeps randomly rebooting (nothing related to the gear). This could be due a modified gearmanagerstub.apk on the GE base, I'm not entirely sure.
I could easily upload a version of the stub APK, you can give it a go on your nexus ?
EDIT: GearManagerStub.apk : From KitKat Google Edition (i9505) & (Uninstall existing GearManager.apk before testing).
BarryH_GEG said:
Just because you can doesn't mean you should. Why would an underpowered device with a 315mAh battery, 512MB of RAM, and a 1.63" display be the best "tool for the job" you described? Especially when it requires a host in near-by proximity for the majority of its functions? It's great what people are doing with the Gear outside the mission Samsung released it for but, like I said before, you're talking about parlor tricks more for sport than serving a function unachievable by better means; some of which are more practical. And if you're trying to use the Gear while driving, especially if you've shrunk the DPI with a launcher, good luck. It's hard enough using the basic functions and S Voice while driving without ending up in another lane. I'm not criticizing everyone's ingenuity and cleverness just pointing out how impractical some things can appear when you take in to account what the Gear really is; a shamefully low-spec, low functionality Android "phone" with a tiny screen that happens to have a wrist band.
Click to expand...
Click to collapse
Gear, with null_, requires no host. It can also connect to bluetooth enabled devices other than a phone.
I was motivated but this: http://daisyworks.net/btgarage.html
It's brilliant and exactly what i have needed for years.
Other interesting links:
http://www.smarthome.com/android_apps.html
http://www.instructables.com/id/Home-Automation-using-Arduino-Android-Phone/
Fact is, this is not a toy when something like null_ is used. It offers a great deal more functionality in a much smaller and more portable/handy package.
Your bias against the device is obvious so it begs the question: why are you here? Just to raise your post count and stir drama in an otherwise peaceful sub-group? Or, do you own it and you are so disappointed that you refuse to see its potential?
Either way, your negativity will not sway me or change my mind. I know it has potential and I plan to use it fully. The fact that it has a wristband is a feature and a plus.
Oh, and I don't consider something that has multiple times the computing power of the original Apollo moon landings "low specs". <3
fOmey said:
To load the gear manager app, it is.. You simply connected your gear via bluetooth.
The gear manager app pushes notifications to the gear.
Without the GearManagerStub.apk it fails to load, its depends on this particular app.
Click to expand...
Click to collapse
Maybe i wasn't clear in my post. I was responding to the phone call portion of the gear. Even without the software installed it still allows the phone calls to be taken and shows the contact information on the watch just like it did on the g4s with the app. All i was saying is that he commented that he was only able to get the phone portion working with the app and i was explaining that you can do that without the app.
fOmey said:
EDIT: GearManagerStub.apk : From KitKat Google Edition (i9505) & (Uninstall existing GearManager.apk before testing).
Click to expand...
Click to collapse
Tried it. Same result. 2 gear manager apps still refuse to install - music and weather (I believe because they reply on specific apps?). Nfc setup connection still works. App still works, but no details get sent to watch. Perhaps tw framework hooks in and serves data to gearmanagerstub, then stub sends to manager, which sends to watch?
---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------
styz said:
Maybe i wasn't clear in my post. I was responding to the phone call portion of the gear. Even without the software installed it still allows the phone calls to be taken and shows the contact information on the watch just like it did on the g4s with the app. All i was saying is that he commented that he was only able to get the phone portion working with the app and i was explaining that you can do that without the app.
Click to expand...
Click to collapse
Yes, from what I understand, the Bluetooth headset part is the only 'generic' part of the watch. It receives data just like a car headset when it displays contact info etc
Just installed that STUB with both the 1.5 and 1.2 GM and both still showed me a 'device not supported" error message.
I spent about 2 hours with Samsung one night and they told me it had to do with baseband version...or that mine was a 4.1 baseband (even though I am running CM 10.2 with 4.3 OS).
Perhaps there is a lockout on older baseband versions?
This is an SG3 phone, by the way.
therealduckie said:
Just installed that STUB with both the 1.5 and 1.2 GM and both still showed me a 'device not supported" error message.
I spent about 2 hours with Samsung one night and they told me it had to do with baseband version...or that mine was a 4.1 baseband (even though I am running CM 10.2 with 4.3 OS).
Perhaps there is a lockout on older baseband versions?
This is an SG3 phone, by the way.
Click to expand...
Click to collapse
How did you install? Try deleting; move to system/app; installing from system/app
Brendo said:
How did you install? Try deleting; move to system/app; installing from system/app
Click to expand...
Click to collapse
Sorry, I should have been more clear...
I installed them both fine. It's when i try to pair the Gear that I get that message.
therealduckie said:
Sorry, I should have been more clear...
I installed them both fine. It's when i try to pair the Gear that I get that message.
Click to expand...
Click to collapse
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Brendo said:
Tried it. Same result. 2 gear manager apps still refuse to install - music and weather (I believe because they reply on specific apps?). Nfc setup connection still works. App still works, but no details get sent to watch. Perhaps tw framework hooks in and serves data to gearmanagerstub, then stub sends to manager, which sends to watch?
Click to expand...
Click to collapse
If you can narrow down which two of those APK's dont install, I can try figure out why.. First step on getting this working is simply identifying what exactly is not working and why.
Once we can get gearmanager running on other branded phones, I'm confident the notifications may work.. or atleast the "more notifications".
fOmey said:
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Click to expand...
Click to collapse
I'm using Nova Launcher as my launcher on my phone. TouchWiz doesn't even load on boot, that I am aware of.
fOmey said:
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Click to expand...
Click to collapse
Really? I still have tw on my gear :s
If you can narrow down which two of those APK's dont install, I can try figure out why.. First step on getting this working is simply identifying what exactly is not working and why.
Once we can get gearmanager running on other branded phones, I'm confident the notifications may work.. or atleast the "more notifications".
Click to expand...
Click to collapse
I still have to install all the extra apks manually
- SAMusicProvider_signed.apk
- SAWeatherProvider_signed.apk
Can anybody suggest a todo app for the NOOK which is compatible with its e-ink screen? I searched on Google but most of them are either full of fancy (in this case ugly and flashy) animations, or are incompatible with Android 2.1. I find it pretty sad because freqently something cames into my mind when i'm reading, and I can't really take a note of it..
Sagittarius0 said:
Can anybody suggest a todo app for the NOOK which is compatible with its e-ink screen? I searched on Google but most of them are either full of fancy (in this case ugly and flashy) animations, or are incompatible with Android 2.1. I find it pretty sad because freqently something cames into my mind when i'm reading, and I can't really take a note of it..
Click to expand...
Click to collapse
Try: Evernote https://docs.google.com/uc?export=download&id=0B7ODz45fOUKVWlZ0S3lIb3hNNnM
-
Sadly wi-fi is not really available to me, so it is out of question. Any offline apps?
Sagittarius0 said:
Sadly wi-fi is not really available to me, so it is out of question. Any offline apps?
Click to expand...
Click to collapse
Not sure what you are looking for.
Evernote works off-line. Download the apk and side-load it to your nook, There is also a simple notepad app that comes with Android that should be already on your nook after rooting.
https://www.youtube.com/watch?v=66YJFnI18pw
https://play.google.com/store/apps/details?id=com.socialnmobile.dictapps.notepad.color.note
.
Thank you Wozhere! This is what I was looking for!
-------------
And regarding Evernote, Richardcoop, I have to register on the first start. But it doesn't matter now, thanks.
Pleasure. On nook I change the theme to: Dark & black on higher androids for all my devices. Settings: Default color to black & reduce Default font size + reduce List item heights, last option needs app relaunch. On phones/tabs I use Extensive Notes Pro which exports txt files sadly abandoned by it's dev as well as ColorNote.
deleted - please go head search for it in XDA, many same resolution provided in other threads (seach quad view mode samsung), plus some custom ROMs come with this mod...
Nice one!!!
Works a treat on my 8.4 - thank you so much...
My only observation is that I also had to append com.sec.feature.multiwindow.scalewindow.xml with .bak as well to prevent it from being overwritten.
Quad multiview definitely rocks. With 3 or 4 apps open the resizing is spot on :victory:
very nice, thanks, works like a charm
Does this work on other ROMS like CM11
konawayne said:
Does this work on other ROMS like CM11
Click to expand...
Click to collapse
No, TW only. However, you can use Xposed Installer with the XHaloFloatingWindow module, complemented with either MultiWindow Sidebar, or with Floatifications. Though, you need to stay in Dalvik, as xposed is not ART compatible, yet.
For XHaloFloatingWindow - you can leave all by default, but:
- Popup WindowPopup Dim set to 0
- Popup Behavior - check "Force New Windows in Halo"
For MultiWindow Sidebar:
- Check "Start on Boot"
- In "Select Apps" - add your apps
- In "Drag Launch Mode": select ParanoidAndroid Halo
- In "Tap Launch Mode": select ParanoidAndroid Halo
It's probably a dumb question - but is there any version of this that doesn't need root?
@jazzespresso:
you copied everything that is on OP (including the :cyclops: smiley) from my thread there:
http://forum.xda-developers.com/showthread.php?t=2770531
You didn t give credits here, and you didn t even thank me on the original thread..
Easy...
Don t you feel ashamed?
unclefab said:
@jazzespresso:
you copied everything that is on OP (including the :cyclops: smiley) from my thread there:
http://forum.xda-developers.com/showthread.php?t=2770531
You didn t give credits here, and you didn t even thank me on the original thread..
Easy...
Don t you feel ashamed?
Click to expand...
Click to collapse
that's very common solution if you do search "quad view mode samsung" in XDA? go head search it, I am sure you will find bunch of them look like yours....but because you seem like you think you found some kind of unique resolution and you wanted to patent it...I will go head delete OP post....
thank you for letting me know...
Bah, I not talking about a patent, I m talking about a guy (you) that copied and pasted my thread without giving any credits.
You didn t even rewrite it, you just copied an pasted it word for word, and you attached the file I had put in my post.
And now, instead of admitting it, or at least to remain silent, you counter attack and try to make it seems as if I wanted a patent.
You wrote "Thank you for letting me know" , are you kidding me?
You didn t know you were copying my thread?
You know how people like you are called?
Is there any way to make Android Auto force immersive mode with root on my car? I wonder if there is a way to hide the navigation bar.
bunklung said:
Is there any way to make Android Auto force immersive mode with root on my car? I wonder if there is a way to hide the navigation bar.
Click to expand...
Click to collapse
Have you found a way to do this?
bunklung said:
Is there any way to make Android Auto force immersive mode with root on my car? I wonder if there is a way to hide the navigation bar.
Click to expand...
Click to collapse
Ignoring the fact that you will end up with an unusable Android Auto, you can't do that
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
Ignoring the fact that you will end up with an unusable Android Auto, you can't do that
shmykelsa said:
Ignoring the fact that you will end up with an unusable Android Auto, you can't do that
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
Ignoring the fact that you will end up with an unusable Android Auto, you can't do that
Click to expand...
Click to collapse
I didn't realize you had a solution to prove it was unstable, because all root solution are unstable? I'm just trying to figure out where and why you are generalizing here.
You're only about a year and a half old on your response though. Better late than never I guess
bunklung said:
I didn't realize you had a solution to prove it was unstable, because all root solution are unstable? I'm just trying to figure out where and why you are generalizing here.
You're only about a year and a half old on your response though. Better late than never I guess
Click to expand...
Click to collapse
Well, first of all I did not talk about any unstable solution. In fact there's no solution for what you've been asking. Moreover I've talked about Android Auto being UNUSABLE. How would you get through all the menus and screens of Android Auto? Swiping up from the bottom, you'd say. No, it's not implemented in Android Auto.
I did not even talk about root solutions, because it doesn't even matter what root solution you've gone with.
Let me explain this more deeply:
Android Auto user-configurable options are the one you see on the settings of Android + developer options.
What you can change with root are some settings inside Google Play Services. Android Auto actually reads a lot of things from Google Play Services database. There are many flags that modify some aspects of Android Auto (e.g. you can force the new Android Auto UI, or hide the status bar etc.) but none for the navigation bar.
But there's more. You can change the resources inside the package (the APK) and edit how the app behaves. But you can't just decompile the APK and compile it back, because it would break the original signature and therefore make the connection to the car broken. You can edit resources via Xposed, but there are no modules for what you are seeking, and honestly I don't think anyone would be interested in doing that. If you'd like to, go on and make a module yourself.
Lastly, I could be a year and a half old, but giving the fact that you can't actually read what I've wrote, I can think the exact same about you
Greetings
shmykelsa said:
Well, first of all I did not talk about any unstable solution. In fact there's no solution for what you've been asking. Moreover I've talked about Android Auto being UNUSABLE. How would you get through all the menus and screens of Android Auto? Swiping up from the bottom, you'd say. No, it's not implemented in Android Auto.
I did not even talk about root solutions, because it doesn't even matter what root solution you've gone with.
Let me explain this more deeply:
Android Auto user-configurable options are the one you see on the settings of Android + developer options.
What you can change with root are some settings inside Google Play Services. Android Auto actually reads a lot of things from Google Play Services database. There are many flags that modify some aspects of Android Auto (e.g. you can force the new Android Auto UI, or hide the status bar etc.) but none for the navigation bar.
But there's more. You can change the resources inside the package (the APK) and edit how the app behaves. But you can't just decompile the APK and compile it back, because it would break the original signature and therefore make the connection to the car broken. You can edit resources via Xposed, but there are no modules for what you are seeking, and honestly I don't think anyone would be interested in doing that. If you'd like to, go on and make a module yourself.
Lastly, I could be a year and a half old, but giving the fact that you can't actually read what I've wrote, I can think the exact same about you
Greetings
Click to expand...
Click to collapse
Great, you're offering some more explanation here than just some single generalization that leaves everyone guessing. That is something we can discuss.
The question was about implementing immersive mode. I agree with you that you can't navigate Android Auto without, well, navigation. How does immersive mode work? Wait, it has no navigation right? Ah, navigation is hidden, but available with a gesture. So in my question, I'm asking about a solution that has navigation right in the question.
Anyhow, I see some good ideas there, like Xposed which makes me start thinking about Pie Controls which all seem doable with some kind of draw over control.
Answering with "go make it yourself" isn't constructive to the discussion. Just because you don't see value in something, doesn't mean it has value to others. But I see you like to make generalization about what people want too.
You must be the life of the party when you, A) show up a year and half late, B) make generalization about everything and everyone, and C) tell everyone to do it themselves.
shmykelsa said:
Well, first of all I did not talk about any unstable solution. In fact there's no solution for what you've been asking. Moreover I've talked about Android Auto being UNUSABLE. How would you get through all the menus and screens of Android Auto? Swiping up from the bottom, you'd say. No, it's not implemented in Android Auto.
I did not even talk about root solutions, because it doesn't even matter what root solution you've gone with.
Let me explain this more deeply:
Android Auto user-configurable options are the one you see on the settings of Android + developer options.
What you can change with root are some settings inside Google Play Services. Android Auto actually reads a lot of things from Google Play Services database. There are many flags that modify some aspects of Android Auto (e.g. you can force the new Android Auto UI, or hide the status bar etc.) but none for the navigation bar.
But there's more. You can change the resources inside the package (the APK) and edit how the app behaves. But you can't just decompile the APK and compile it back, because it would break the original signature and therefore make the connection to the car broken. You can edit resources via Xposed, but there are no modules for what you are seeking, and honestly I don't think anyone would be interested in doing that. If you'd like to, go on and make a module yourself.
Lastly, I could be a year and a half old, but giving the fact that you can't actually read what I've wrote, I can think the exact same about you
Greetings
Click to expand...
Click to collapse
Although i agree with you, i just wanted to mention that, you can control android auto without softkey. Look my solution :
(If someone could create a way to hide android auto bar, i suppose he could also make a way to control it through gensture, like i do for android). But you are right, there is no solution. Anyway look my video may give some ideas what can be done today and what not:
I too would think this would be cool. even if the bottom icons stayed so you could still navigate and the bottom black bar was transparent or something.
Hi all,
It's been a very long time since I've used this forum so apologies if this is in the wrong place - I did do a quick search already however could be wrong terminology.
I am TERRIBLE with icons with Android especially when every so often an update changes the look and feel of them.
Obvious ones on the phone are fine but the watch and its tiny icon view of the launcher/apps I always struggle to find what I want.
Is there a simple list view available for it? I'm pretty sure maybe the original Galaxy Watch (camera on the strap) had it but all subsequent Tizen and now Wear OS seem to be icon based.
Thanks
AJ