[MOD] HTC Car Mode Xposed! (Version 2.3) [Lollipop Compatible!] - Xposed Framework Modules

The HTC Sense Car Mode app had some features removed or changed from the previous versions. Namely, statusbar pulldown has been blocked, along with switching apps and basically multitasking.
The reason for this is probably safety; to discourage drivers from tinkering too much with their phones while driving - and while I'm fully behind that I believe in giving people options - which is why I created this module!
So far it allows you to:
Bring back multitasking (status bar and 'recent apps' functionality).
Release the 'Home' button to let it go back to the default launcher.
Replace the default 3-Tap gesture action with anything you want!
Turn Wi-Fi and GPS on or off at startup and shutdown.
Bypass the exit confirmation dialog.
Automatically close apps opened from within the Car App on shutdown (requires root to be fully functional!)
And more features coming in all the time!
If you love the HTC Car app as much as I do, you'll enjoy this!
{
"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"
}
Download
You can find it on the Xposed repository right here.
(It's marked as 'beta' so set your installer filter accordingly).
XDA:DevDB Information
HTC Car Mode Xposed!, Xposed for the HTC One (M8)
Contributors
Ambious
Source Code: https://github.com/eladavron/HTCCarXposed
Xposed Package Name: ambious.htccarxposed
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2014-11-02
Current Beta Version: 2.3
Beta Release Date: 2015-05-15
Created 2014-06-01
Last Updated 2015-05-16

Changelog
Latest Versions:
Version 2.3 Pulled! This version seemed to cause other things to malfunction.
Version 2.2
Added Sense 7.0 Compatibility
Fixed an issue with the screen not staying on in older versions (Android 4.4)
(Not Tested on Sense 6.* Versions!)
Version 2.1
Fixed a bug that would cause the 3-finger gesture to crash the "Car" app even when not running.
Added a "Logging" option for better future debugging (saves log to file on the SD Card).
Version 2.0:
Now Lollipop Compatible! (not tested on KitKat)
Click to expand...
Click to collapse
Older Versions:
Version 1.9:
Added the option to turn off the screen when exiting the car-app - requires enabling Administrator Privileges (prompted when enabled).
Version 1.8:
Brought back the GPS startup and shutdown mods, should work fine now.
Version 1.7:
Added the option to override the "3-Fingers tap" gesture with either Google Hands-Free, Google Now or a custom app of your choice!
Fixed a bug with the Toggler where it would launch the settings app instead of the car if triggered by 3rd party app (such as NFC or Tasker).
Version 1.6:
Added the "App Toggler" which allows to shut down the car app through a global shortcut, or launch it if it's already closed.
Fixed a bug where Wi-Fi would turn off even by navigating away from the Car app and not just closing it.
Re-did the icon - again! (One day I'll be pleased with it).
Click to expand...
Click to collapse
Version 1.5:
Fixed "Multitasking"! Yes, the "Recent Apps" button now works and doesn't break anything! Thanks to the brilliant RichmondoUK for pointing me in the right direction.
Removed GPS mods - it wasn't working as well as I had hoped due to android privacy overrides.
Click to expand...
Click to collapse
Version 1.4:
Added 'Exit mods':
Change GPS and Wi-Fi states on exit
Close apps opened from the Car App (either using a regular shut-down which doesn't always work or the more powerful 'root' method).
Moved the "Exit without confirmation" option under this category
Some code touch-ups
Still no fully-working multi-tasking mod, sorry... that's one tough nut!
Click to expand...
Click to collapse
Version 1.2:
Default settings will bow be applied upon installation.
Added an option to bypass the exit confirmation dialog
Added the option to turn GPS and Wi-Fi on or off at startup.
You can also choose to - obviously - not change them at all.
I'm still working on turning them on and off when exiting the app, it's not working so well so far...
Click to expand...
Click to collapse
Version 1.1:
Interface added! You can now turn mods on and off selectively.
Added the option to release the 'Home' button.
New icon, slightly less ugly I hope.
Click to expand...
Click to collapse

Information
Why disable a safety feature?
The HTC Car App introduced those blocking 'features' for an obvious reason: to discourage people from fumbling around with their phones while driving.
That's a good and important cause, but unfortunately it's not a very smart method of doing it - which is why this module was created. Consider the following scenario: You're in your default navigation app with the music player (which is controllable by the car app) running in the background. You want to skip the currently playing track. If everything's at stock, the new restrictions make it an annoyingly long process: You have to click the home button, enter the music control applet, skip the track as you normally would, then click the home button again, find the navigation app's icon and re-launch it. Without those restrictions all you do is pull down the statusbar, click the 'skip' button on the music player's active notification tile, and pull it back up.
HTC's restrictions - which are supposed to increase safety and attention while driving actually make it longer and more attention-consuming to perform such tasks.
This module allows you to overcome those restrictions, mostly, but I must still say - and I can not overstate this enough:
DRIVE SAFELY!
DON'T OPERATE YOUR DEVICE WHILE DRIVING !
Play music, navigate, make and take calls - but do so safely without fumbling around.
If anything doesn't work with less then three touches of the screen, or if it requires you to look at your device for more than a split-second glance - either forget about it or pull over! It's not worth it!

Works as advertised. Upgraded from Sense 5.5 just so I could enable this mod and get to my notifications. Thanks!

Very cool. I use the HTC car app quite a bit and always hated that I had to close it to access anything else. What other tweaks are possible? It would be nice to be able to switch the default music app to Google Music. Disabling wifi on launch would also be slick.
BTW, this works fine on the M7 with Sense 6.

linuxsense said:
Very cool. I use the HTC car app quite a bit and always hated that I had to close it to access anything else. What other tweaks are possible? It would be nice to be able to switch the default music app to Google Music. Disabling wifi on launch would also be slick.
BTW, this works fine on the M7 with Sense 6.
Click to expand...
Click to collapse
Currently I'm mostly battling with basic things like making the 'recent apps' button work and making the settings toggleable without restarting. Once I get the basics working, I'll start seeing what else I can tinker with. Switching the default music app is not going to be easy because it's deeply integrated within the app, but I'll see what I can do.
As for the wifi, that shouldn't be too difficult.
Glad to hear it's working on other devices as well.

Please add support for all apps in car mode! Currently you can add only a few apps .. For example you can't add Torque

Looks like the 1.1 version changes caused it to stop working with the M7 :crying:
ETA: Looks like it functions properly if "take over home button" is disabled. With that unchecked you can access the pulldown menu as well as reach the desktop or recent apps using the home button.

linuxsense said:
Looks like the 1.1 version changes caused it to stop working with the M7 :crying:
ETA: Looks like it functions properly if "take over home button" is disabled. With that unchecked you can access the pulldown menu as well as reach the desktop or recent apps using the home button.
Click to expand...
Click to collapse
It might be something else, I noticed that the settings won't take until you run the settings interface at least once.
Please try to re-enable the setting and see if anything changes.
Thanks for the report!

Ambious said:
It might be something else, I noticed that the settings won't take until you run the settings interface at least once.
Please try to re-enable the setting and see if anything changes.
Thanks for the report!
Click to expand...
Click to collapse
I am pretty sure that I ran settings app prior to trying it out, not completely sure though. I just toggled the home screen option and get the same results. It only works if it is not selected.

linuxsense said:
I am pretty sure that I ran settings app prior to trying it out, not completely sure though. I just toggled the home screen option and get the same results. It only works if it is not selected.
Click to expand...
Click to collapse
Hmm. I'm not getting that on the M8, but I'll look into it.
Unfortunately I don't have an M7 to test on.
Could you for the sake of testing go to the settings interface - uncheck both boxes, then recheck both boxes, then restart your device and see if it works then?
Thanks!

Ambious said:
uncheck both boxes, then recheck both boxes, then restart your device and see if it works then?
Thanks!
Click to expand...
Click to collapse
Its work :good::good::good: thanks

ahlot18 said:
Its work :good::good::good: thanks
Click to expand...
Click to collapse
Thanks for the info, I think I know what's causing it:
The mods don't take if the car app is running in the background because it hooks into methods as they load.
There's a command to kill it if it's running in the background and settings have been changed, but it might not have taken - or rather, it also won't be run if settings are at their default state, so if you install the mod, then run the car app, then load the module interface and change nothing - it still won't be set.
Next version will handle this more properly, I hope (currently writing it).

Reyzis said:
Please add support for all apps in car mode! Currently you can add only a few apps .. For example you can't add Torque
Click to expand...
Click to collapse
I can add Torque to Car...?

agentdr8 said:
I can add Torque to Car...?
Click to expand...
Click to collapse
Torque free or the paid App? I have torque free and can't add it to car mode ... :/

Reyzis said:
Torque free or the paid App? I have torque free and can't add it to car mode ... :/
Click to expand...
Click to collapse
Torque paid. Maybe free is different, but from what I can tell, HTC Car doesn't blacklist any apps from being added to one of the screens.

I agree, there doesn't seem to be a limit on which apps you can add and which you can't.
Your issue must be related to the app itself. Since I'm unfamiliar with Torque, I really can't tell.
Are there any other apps, as far as you can tell, that you can't add?

Ambious said:
Hmm. I'm not getting that on the M8, but I'll look into it.
Unfortunately I don't have an M7 to test on.
Could you for the sake of testing go to the settings interface - uncheck both boxes, then recheck both boxes, then restart your device and see if it works then?
Thanks!
Click to expand...
Click to collapse
If I do that when I run the HTC car app the home button will open recent apps if double tapped but otherwise it just returns to car mode when home is pressed. If I disable it pressing home takes me to the desktop and double tapping it takes me to recent apps. I am running NuSenseSIX based off the m8-base fwiw. If you have any tweaks you would like tested let me know, I can provide logcats and such.

Dialer not working
Thank you for this awesome mod. I'm not sure if it's the ROM I'm running, but I can't seem to launch the dialer using this module. All other buttons work normally, as well as the added functions of this module.
I'm running the Venom ROM on the M8.
Does anyone else have this problem?

dafob said:
Thank you for this awesome mod. I'm not sure if it's the ROM I'm running, but I can't seem to launch the dialer using this module. All other buttons work normally, as well as the added functions of this module.
I'm running the Venom ROM on the M8.
Does anyone else have this problem?
Click to expand...
Click to collapse
Good catch. Just shows how much I actually use my 'phone' for calls...had not even tried it yet :laugh:
I have the same issue on an M7, the 'Dialer' button in the car mode app doesn't do anything.

Related

[MOD][XPOSED] Phab7 v1.00 no-reboot UI Switcher

Phab7 is an on-the-fly UI switcher: select Phone, Phablet, or Tablet, then tap the Change button. The switch happens immediately - no reboot needed. A separate option lets you switch settings screen layouts (e.g. the Settings app) between Phone-style (separate screens for categories and details), and Tablet-style (categories and details, side-by-side).
Unlike other solutions, Phab7 has no effect on your apps beyond for their Settings screens. In particular, it will not alter the size or layout of your launcher's icons or dock (nor will it cause the tablet-style app-drawer icon to appear).
Note: Google removed Tablet mode from KitKat, so it is not available if you're running Android 4.4.x.
Installation
Important: if you have a beta version of Phab7 (v0.9x) currently installed, you must uninstall it before installing v1.0. Android will refuse to install it if one of the betas is present.
if you don't already have XposedInstaller on your system, see this thread
install Phab7.apk the same way you'd install any other sideloaded app
enable Phab7 by reopening the XposedInstaller app and selecting 'Modules'
tap directly on the checkbox next to Phab7, then back out and reboot
after the initial reboot, you can open the Phab7 app and change UIs as many times as you wish without further reboots
Notes
Tablet UI mode is only available when running ICS or JB (v4.03 thru 4.3x). While Phab7 supports KitKat, it does not add back the Tablet mode that Google has removed.
Whether Phab7 works on your device depends almost entirely on your ROM's creators. If they removed the graphics and layouts needed for a given UI mode, SystemUI.apk is guaranteed to force-close when you select that mode. A "Keep-Or-Cancel" dialog will automatically restore your settings after 12 seconds if this happens when you choose an incompatible UI mode. Clear the "Unfortunately" popup and you're good to go.
the Settings-layout feature takes effect when an app is first launched. To see its effect on running apps (e.g. the system's Settings app). tap the "Recents" button and swipe the app away , then reopen the app.
File
Phab7.apk - v1.00
Credits
barrmulio - the first to identify the system changes needed to implement alternate UIs
_TB_TB_ - author of TabletUI trigger who first realized that UI-switching could be done by an Xposed module
History
2014/01/22 - v1.00 - initial stable release
2014/01/05 - v0.99 - added keep-or-cancel dialog
2013/12/13 - v0.97 - added scaling for all modes
2013/12/10 - v0.96 - fixed KitKat-specific bug
2013/12/09 - v0.95 - added Tablet UI scaling
2013/11/30 - v0.92 - added support for KitKat
2013/11/27 - v0.90 - initial release
Gonna try it on S4 v4.3
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 08:08 AM ---------- Previous post was at 08:02 AM ----------
Ring of FC ;p
Sent from my GT-I9505 using XDA Premium 4 mobile app
Tried it, changes fine to tablet mode. Just a few layout issues. And the nav glow doesn't fade.
See screenshot.
Xperia Z running eXistenZ 4.10 rom.
Subscribed, this looks promising.
{
"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"
}
Sent from Z Beast
For me with android 4.1 only settings work and status bar and nav bar don t work
Sent from my LT26i using Tapatalk
Great job. tested working on CM10. status bar looks monster
it could have better you provided DPI settings along with phab7. though i can manage with app settings
the give attachment is flashable zip i just extracted phab7.apk and installed normally
why this is not available in xposed Repo..
reversegear said:
why this is not available in xposed Repo..
Click to expand...
Click to collapse
I think because it's new and in beta
Sent from Z Beast
Now we need not wait for updated Paranoid!! OK Paranoid does do some of this stuff better/more consistantly than AppSetting and this module, but ...
Great!
Wanna outdo Paranoid: Tablet mode mostly more usable in landscape, so ... get the idea?
EDIT: Results using the mod on my LG P500 running cm-10.2 with 4,4 Google Now launcher: I can use AppSetting module to force this launcher to rotate but it does not handle this correctly.
Settings UIs work as promised! This is what I really missed not having Paranoid.
Navigation bar: Question -- what if I do not use one (phone has HW buttons--remember those)? Module should accept phone setting.
Anyway, tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Went back to default: Icon bar, no navigation bar.
If I remember from Paranoid, tablet mode put notifications bar on the bottom right. Phablet left it on top, opening to half-height, had to change dpi to fit it to screen width correctly. So tablet mode, once working, would either have both at bottom right justified or just the notifications as chosen in the phone's settings! Someone check current Paranoid.
Compatible with KitKat?
Wysłane z mojego Ascend G510 przy użyciu Tapatalka
Don't flash that zip!
reversegear said:
the give attachment is flashable zip i just extracted phab7.apk and installed normally
Click to expand...
Click to collapse
OMG!!!! My apologies! The zip that was posted (in error) was only for the Hisense Sero 7 Pro and contained a tablet-specific mod to SystemUI.apk.
The script in that zip checks for the model, so it should have failed if you tried to flash it on any other device. However, if somehow you succeeded in flashing it, you will have to restore your ROM's original SystemUI.apk. The original, along with SystemUI.odex if present, is in your /system/app folder with '-org' appended to it. If you have problems handling this, I can create an update.zip to do this for you.
Again, my apologies - it was late...
This's amazing. Thanks a lot dev. Looking forward for new versions:laugh:
Saeedblack said:
For me with android 4.1 only settings work and status bar and nav bar don t work
Click to expand...
Click to collapse
Dovidhalevi said:
tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Click to expand...
Click to collapse
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings.
Setting default ui to phablet didn't help either.
Debug log: https://www.dropbox.com/s/zlp89tbus6o23qi/xposed_debug_20131127_194414.log
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
for me it have been FC for first run and after reboot it never appear again but don t have FC
also here you are i attached log that you notice
No TabletUI in KitKat
MMeester said:
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings. Setting default ui to phablet didn't help either.
N7(flo)-Rastakat-franco.kernel
Click to expand...
Click to collapse
Is this a KitKat-based ROM? Sadly, all of the code and resources needed to support Tablet UI have been stripped from Android v4.4. Because Phab7 v0.9 doesn't make provisions for this change, the UI switcher doesn't work. I will fix that ASAP so that at least Phone and Phablet are available. Restoring Tablet UI may be more than an Xposed module can/should do, but I'll investigate...
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Dovidhalevi said:
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
Click to expand...
Click to collapse
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
dolorespark said:
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
Click to expand...
Click to collapse
I first tried it before rebooting, then realized that it cannot work that way and rebooted. Then Phab7 worked as described.
Since wisdonsky operates on the notifications bar, could be that the interaction with tablet mode trying to move that is what is noted.
dolorespark said:
Is this a KitKat-based ROM?
Click to expand...
Click to collapse
Yes.
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Click to expand...
Click to collapse
Sadly, no change in settings app after a reboot. Do you need any logs?
Thank you for looking into the issue.
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Any help appreciated.
Metallijim said:
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Click to expand...
Click to collapse
Phab7 is designed to do as little as possible to achieve its goals - in some cases, perhaps too little. For Phone and Phablet, it does some setup when SysUI starts and that's it. For Tablet, it has to be slightly more intrusive but not much.
Sadly, I had no way to test compatibility mode so I'm not surprised that it has issues. Recovery from most any problem should be as simple as switching to another UI. In this case, getting out of TabletUI, then returning without touching the compatibility button should cure what ails you.
If you get repeated FCs in SystemUI, one way out is to leave the toast up there, then from ADB, delete /data/data/com.e_vertise.dopa.phab7/shared_prefs/settings.xml. When you dismiss the toast and SysUI restarts, you should be back to your device's default settings.
Note: if I understand things correctly, Android may try to reload SysUI's Java code several times using the same process before it gives up and kills that process. Once it restarts SystemUI using a new process, you're certain to be back to normal if you've deleted Phab7's settings file.
We'll soon find out if it works on KitKat. Yes I know how to disable Xposed from recovery. Using it on KitKat doesn't seem to cause any crashes, but it doesn't do anything at all on KitKat.
Sent from my Nexus 7 using Tapatalk 4

[Mod][Xposed] Alarm Clock Plus 2.0

There was a similar tweak for iOS back in the days when i was an iphone user which i was always missing on my Android device.
Now i just created it myself because i was bored yesterday :>
Do you enjoy snoozing in the morning as much as i do? Hate how you always have to look at your phone to determine if you can snooze
one more time or not?
This tweak tells you the time, everytime you snooze your alarm. Actually, it can tell you about anything.
You can set your own text and use a variety of variables. (Currently there are only a few. More might follow, if people like this tweak - for example unread mail count, weather, etc.)
Screenshot:
{
"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"
}
Compatibility:
I tested this tweak on a Nexus 5, running 4.4.2 Stock.
Alarm Clock Plus should be working on about any Device and any version of Android that has the stock Clock app.
(Please let me know if it works for you or if you have any issues, thanks)
This only works with the standard Google clock!
Package: com.google.android.deskclock | com.android.deskclock
Currently the Interface is still pretty raw and ugly.
I will work on that soon. Also I have some ideas for more features, which I'm going to implement over time.
Changelog:
1.0
Initial release
1.0.1
Small bugfix (disable dismissed now working)
1.1
added: Can hide icon from launcher
added: Auto save settings on exit
added: Voice speed control
added: Voice language selector
added some logging for debugging
possible fix of the TTS not firing
1.2
added: Support for CyanogenMod 11
(and possibly other roms that use the standard aosp clock app or derivates of it)
Thanks @pdcrzylazy for testing!
1.2.1
added: Support for Android 4.4.3+
(Let me know if this still works on 4.4.2 and lower please)
2.0
complete rewrite of the module.
it should be much more stable and reliable now.​
added: Tasker support (You asked for it and here it is!)
added: New Variables - %I (Hours 12h), %p (Am/Pm)
changed: Settings - No more need to reboot the device after changing settings
2.0.1
fixed: Test tasker-task on dismiss
fixed: Forgot to shut down the TTS engine
2.1
added: Check if your device/ROM is compatible
added: Check if you have TTS installed
added: Button to let you install more language files
reduced package size
2.1.1
fixed: Bug that broke the module on some devices
2.1.2
added: Option to remove leading zeros for the time and date variables
Click to expand...
Click to collapse
Download:
[QRCODE]http://repo.xposed.info/module/com.chrisxe.xposed.alarmtelltime[/QRCODE]
http://repo.xposed.info/module/com.chrisxe.xposed.alarmtelltime
If somehow you really like this tweak and want to support me, you can also buy this tweak from google play for little money
(This is the same version as the free one in the Xposed repo. It is just a donation package)
Alternatively you can click here to donate via paypal
Thanks to:
- rovo89 for the Xposed Framework.
- MohammadAG for all of his source codes on github.
Great idea. Like this very much. But unfortunately I'm using cyanogenmod 11 on my nexus 5.
And cm is not using the standard google clock. Is it possible that you can port this module to run also on devices with cyanogenmod?
Thank you.
Great potential...when it is ported to work with cyanogen I will definitely give it a try.
Sent from my LG-P936
thanks for the feedback. i'll try to look into it, to get it to work for cm
andreasf93 said:
Does it require internet to work? Because I tried it this morning and I snoozed it twice without hearing anything.
PS: Stock 4.4.3
Click to expand...
Click to collapse
have you tried to open the settings of the tweak and then hit the "save" button?
seems like for some people you need to do this first (im working on it!)
or maybe your locale isnt supported by text-to-speech. currently the tweak uses the default locale which is set by the system (i'll add a switcher to set a custom locale soon)
andreasf93 said:
My locale is English (UK) so it should be fine. When I press the Test button the voice is just fine. And yes I've pressed the Save button multiple times, still not working.
PS: Are you Greek?
Click to expand...
Click to collapse
it should work just fine then. are you using the standard aosp clock from google? (com.google.android.deskclock)
PS: no i'm not
andreasf93 said:
Oh okay, because Mythos is a Greek word
Yep, I have the default clock since I bought my Nexus 5 and did not install any other alarm apps :s
Just tried rebooting, reinstalling the app, still did not work
Click to expand...
Click to collapse
can you try to set an alarm and watch your logcat for errors when you hit the snooze button?
or maybe check the log in xposed installer
__EDIT:
oh and you did enabled the module, right? sorry, im not assuming you are dumb, just making sure
andreasf93 said:
Ye I have enabled it, I checked myself twice to make sure
Nothing shows up in xposed log, not sure how to check logcat though.
Click to expand...
Click to collapse
mhm. then im out of ideas for now, sorry ;(
maybe it is not 4.4.3 compatible. i dont know if the clock app changed or anything else xposed related.
i'll look into it
Another possible feature that you might look into -
Announcing the time on request (say, when I press the volume button) - BEFORE the alarm goes off. When I'm half asleep in the morning and not sure whether it is time to wake up, I want to be able to press the volume key and hear what time it is. I was trying to do it via tasker this weekend but didn't quite achieve what I was looking for.
So, if you can implement something to this effect in your module, that would be awesome.
Is not work on my galaxy s5
Sent from my SM-G900F using XDA Premium 4 mobile app
Please check the first post, I updated the module.
Changelog also in first post. Might have fixed the bug andreasf93 was experiencing
(Please let me know if it works now (Encountered the same bug as you, another reboot seemed to fix it for me))
@bagarwa
very good idea!
I'll probably implement that soon
Not sure if their name is copyrighted, but you may wanna change the name of this:
https://play.google.com/store/apps/details?id=com.vp.alarmClockPlusDock
Would hate to see a wonderful developer get a lawsuit! How about "Alarm Clock ADVANCED"
can you add option to turn off/on all the alarms that are setted ?
super charge for clock
It doesn't work on my GS4 on stock GPE 4.4.2. Voice is heard when press test buttons but when alarm goes off.. Snooze our cancel alarm didn't produce any sound.
Any ideas?
MythosXe said:
Please check the first post, I updated the module.
Changelog also in first post. Might have fixed the bug andreasf93 was experiencing
(Please let me know if it works now (Encountered the same bug as you, another reboot seemed to fix it for me))
@bagarwa
very good idea!
I'll probably implement that soon
Click to expand...
Click to collapse
Suggestion: an option to perform a tasker task when alarm is snoozed/dismissed would be awesome!
Will be useful for news, custom text, unread messages/emails/whatsapp messages, opening custom apps, etc
Would absolutely love this, thanks!
Great idea and very cool module! Working good on my Galaxy S4 running 4.3.
- Sent from my Galaxy S4 using the XDA app.
also rocking cm 11, this clock seems interesting tough. Would definitely try it if you came around to making it available to cm roms.
Can someone on CM 11 test if this one is working? (see attachment)
If it doesnt work first try, can you reboot a second time and try again? thanks :>
MythosXe said:
Can someone on CM 11 test if this one is working? (see attachment)
If it doesnt work first try, can you reboot a second time and try again? thanks :>
Click to expand...
Click to collapse
I'm running CM11. I installed the test APK and used the Test functions in the app interface. Those are working. Tested the clock app and the voice worked when I snoozed the alarm. Seems successful on CM11. Nice job.
pdcrzylazy said:
I'm running CM11. I installed the test APK and used the Test functions in the app interface. Those are working. Tested the clock app and the voice worked when I snoozed the alarm. Seems successful on CM11. Nice job.
Click to expand...
Click to collapse
Thanks for testing :>

Tips and tweaks for running with CM

Thanks to @biktor_gj and his development skills, it all started here, below are the things I've managed to get working either partially or fully. Once a stable CM 13 is released, this post is likely to be updated.
Fully charge your watch first. Things below will take considerable time to configure to your liking; it's better to have enough battery to fully test the configuration.
1. Because CM 12 is a 5.1 build, you'll have to get Play Services from a Lollipop apk (I got mine from apkmirror), and install Gapps (mine is a modular nano; it will take 10-20 minutes). I suggest wiping Dalvik cache from TWRP after installing Gapps - my unit was very unresponsive until I wiped Dalvik and it rebuilt all 98 apps (your app count may vary).
2. Push notifications - get the Desktop Notifications app. Until Bluetooth is working properly, get Desktop Notifications (yes, it's only via WiFi tethering, it's cloud-based, which sucks, I hate it, but oh well). Configure and test it on another Android device first (provided you have one) or a computer, so that you can successfully get notifications to begin with and aren't wasting your time on the tiny 200-dpi Gear S screen. Keep in mind that because it's Wifi-tether, the battery life may suffer. Because I'm still testing various things on and off (primarily with Tasker), I haven't had a chance to test the battery from 100% in a fully-working state.
{
"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"
}
3. Tasker profiles on the watch; this section is likely to be updated every now and again, as I tweak more and more settings. You have to install Tasker on the watch.
3.1. Watch notifications -> Wake Device and Vibrate.
Get Secure Settings as well as Auto Notification from Play Store, go to Tasker and create a new profile. Profile details/conditions are "Notify" and "Display State Off". "Notify" comes from the Auto Notification module/plugin. Configure -> Action Type = "Created Only"; Persistency = "Non-Persistent", Apps = check "Desktop Notifications". Task would have Vibration and Wake Device (Secure Settings -> Actions -> Wake Device). Vibration duration is whatever you choose; mine is set to 200ms.
3.2. [not ideal but most reliable] Cover to Wake -> upon covering the device light sensor while the screen is off, it wakes the device and briefly lights it up for a couple of seconds so you see the time, etc.
Profile conditions are "Light Level 0 to 1" and "Display State Off". Task is - "Wake Device" from Secure Settings. Configure that as you wish.
-LBT- said:
Thanks to @biktor_gj and his development skills, it all started here, below are the things I've managed to get working either partially or fully. Once a stable CM 13 is released, this post is likely to be updated.
Fully charge your watch first. Things below will take considerable time to configure to your liking; it's better to have enough battery to fully test the configuration.
1. Because CM 12 is a 5.1 build, you'll have to get Play Services from a Lollipop apk (I got mine from apkmirror), and install Gapps (mine is a modular nano; it will take 10-20 minutes). I suggest wiping Dalvik cache from TWRP after installing Gapps - my unit was very unresponsive until I wiped Dalvik and it rebuilt all 98 apps (your app count may vary).
2. Push notifications - get the Desktop Notifications app. Until Bluetooth is working properly, get Desktop Notifications (yes, it's only via WiFi tethering, it's cloud-based, which sucks, I hate it, but oh well). Configure and test it on another Android device first (provided you have one) or a computer, so that you can successfully get notifications to begin with and aren't wasting your time on the tiny 200-dpi Gear S screen. Keep in mind that because it's Wifi-tether, the battery life may suffer. Because I'm still testing various things on and off (primarily with Tasker), I haven't had a chance to test the battery from 100% in a fully-working state.
View attachment 3609050
3. Tasker profiles on the watch; this section is likely to be updated every now and again, as I tweak more and more settings. You have to install Tasker on the watch.
3.1. Watch notifications -> Wake Device and Vibrate.
Get Secure Settings as well as Auto Notification from Play Store, go to Tasker and create a new profile. Profile details/conditions are "Notify" and "Display State Off". "Notify" comes from the Auto Notification module/plugin. Configure -> Action Type = "Created Only"; Persistency = "Non-Persistent", Apps = check "Desktop Notifications". Task would have Vibration and Wake Device (Secure Settings -> Actions -> Wake Device). Vibration duration is whatever you choose; mine is set to 200ms.
3.2. Shake to Wake -> upon shaking the device while the screen is off (you flick your wrist), it wakes the device and briefly lights it up for a couple of seconds so you see the time.
Profile conditions are "Shake Up-Down" (sensitivity High, duration Very Short) and "Display State Off". Task is - "Wake Device" from Secure Settings. Configure that as you wish.
Click to expand...
Click to collapse
I appreciate your advice! I personally like to install (no frills Cpu) and clock the device do 300-600mhz for extra battery savings. You said it right, we are lucky to have Biktor!!!
GOIGIG said:
...clock the device do 300-600mhz for extra battery savings...
Click to expand...
Click to collapse
Don't we have to have a compatible kernel for that? If so, do you know we actually have it?
No frills Cpu works like a charm, I have been using it since day 1, I test it on every device I get honestly its the best interface with the most compatibility, depending on Your kernal it works on the note 5 lol
Sent from my SM-N920T using Tapatalk
GOIGIG said:
its the best interface with the most compatibility
Click to expand...
Click to collapse
Does it affect WiFi performance or range?
-LBT- said:
Does it affect WiFi performance or range?
Click to expand...
Click to collapse
Not at all, I apply on boot, games don't play well when it's clocked that low on powersave but it lasts and the more updates the better it gets stability wise, I always thought no frills caused some of the issues. Enable SU in developer settings if you have not
Sent from my SM-N920T using Tapatalk
1. For some reason, the shaking profile isn't working as well as I had hoped. I'm looking into either adjusting it further, or incorporating the accelerometer "face-up", proximity or pressure sensing profile, which I'm not entirely sure would work since there may be no sensors for that on Gear S.
Accelerometer isn't that great, either, see below - the watch is on its side, yet the accelerometer says that it's facing up.
2. Tasker light sensor isn't working for me either - with the condition of "Light sensor values 1 through 5 + Display State Off" followed by "Wake Device" task, nothing is happening when I cover the light sensor while the device is off. I'll have to do a bit more digging on how the light sensor is handled in Tasker.
3. Neither proximity nor orientation sensors are being detected by the Sensor Test app. My hopes for the pressure sensor quickly vanished when I discovered that it's not the screen pressure but atmospheric pressure.
4. The light sensor monitoring was off (genius) - got the light sensor to work. Set the profile to "Screen Off + Light Level 0 to 1" -> Wake Device. So far, this seems to be the most reliable waking option. EDIT: unless you're wearing long sleeves, of course. Just can't catch a break with this screen wake.
Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.
nghiaxp said:
Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.
Click to expand...
Click to collapse
I'll be waiting for the CM 13 update. If Bluetooth becomes a reliable tethering option (right now I'm paired to the phone but cannot browse internet) and sensors get a better implementation, I'll think of more things to do. So far the shake sensor presents a concern, as it works on the first try but stops on the third or fourth attempt (the shake movement of the wrist is literally identical).
nghiaxp said:
Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.
Click to expand...
Click to collapse
I recommend either dynamic notifications, or acdisplay for a better lockscreen. You can configure them to turn on the screen for a few seconds when you get notification.
Set their background to pure black for battery savings.
Edit: they're nice but I have to say don't bother with the little ram we have. I feel kitkat rom would've been better to port to Gear S
Edit 2: Install this https://play.google.com/store/apps/details?id=org.azasoft.free.swapper set it to 120mb. helps with ram.
Also this https://play.google.com/store/apps/details?id=com.chummy.jezebel.blacked.out and apply in themes app. helps with amoled power savings
Not available on "Next" to update the application .apk. This is due to the resolution of 200dpi. Therefore it is necessary to change the settings at 180dpi resolution. But it comes a full restart of the interface. After the installation is restarted again to return 200 dpi. Is it possible to update the application without changing the dpi? I have no established GAPPS for ideological reasons.
Shum Channel said:
Not available on "Next" to update the application .apk. This is due to the resolution of 200dpi. Therefore it is necessary to change the settings at 180dpi resolution. But it comes a full restart of the interface. After the installation is restarted again to return 200 dpi. Is it possible to update the application without changing the dpi? I have no established GAPPS for ideological reasons.
Click to expand...
Click to collapse
There's an experimental lollipop version of app settings xposed module that lets you choose dpi of specific apps. I'll post a link when i can get to a computer. (At work). Then you can set dpi of package installer only
According to the link below, pushbullet allows you to sync notifications between two or more android devices, so this should have the desired feature of receiving notifications from the phone that the Gear S is paired with.
http://www.androidauthority.com/pushbullet-notifications-update-384910/
scottgl9 said:
According to the link below, pushbullet allows you to sync notifications between two or more android devices, so this should have the desired feature of receiving notifications from the phone that the Gear S is paired with.
http://www.androidauthority.com/pushbullet-notifications-update-384910/
Click to expand...
Click to collapse
I think it's a paid feature and works through internet though. I actually installed SWAPPLink and it does notification through bluetooth connection (It crashes often, but notifications still work, just hit ok on the crash message and it'll keep working)
Also I got it from the Swapplink Google + community, where he posts beta versions. I don't know when last the play store version has been updated.
Fitting Calculator App
nghiaxp said:
Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.
Click to expand...
Click to collapse
Have a look at this:
Calculator App called "Rechner" , from TricolorCat
It is a Perfect fitting and working calculator. (Sorry, still not allowed to post any Links...)
No need to change the Dpi any longer...
---------- Post added at 08:02 PM ---------- Previous post was at 07:29 PM ----------
G1NT0NN1C said:
Have a look at this:
Calculator App called "Rechner" , from TricolorCat
It is a Perfect fitting and working calculator. (Sorry, still not allowed to post any Links...)
No need to change the Dpi any longer...
Click to expand...
Click to collapse
The rondo Icon pack is a free pack of very Clear and simple icons. It fits perfectly to the small Display of the gear s.
what is this tasker thingy?
Hi guys! I dont know if this thread is alive anymore. But I'm currently using the latest? android 5.1.1 on my gear s and its awesome! compared to regular tizen...
For notifications i'm using m2d sender / receiver. it works perfectly! pushes all notifications from my phone to my watch. in the new update you can set m2d receiver up to be used on a watch. works very well!=) check it out!
The only issue I have with running android on is the RAM. i only have amax of 100MB ram free! Anyone being able to free up more?
Hello,
how can i use on CM the Heart Rate Sensor and UV Sensor?
there is an app for bluetooth notifications between gear s cm and android phone?
How stable is cm on the gear s?
Sent from my SM-G955F using Tapatalk

[XPOSED] Pokémon GO Controls Xposed Module

Pokémon GO Controls is an Xposed module that lets you add a 4 way controller to the game and enables youto move around the map without having to actually walk around by providing fake GPS location to Pokémon GO.
{
"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"
}
Working video:
Click to expand...
Click to collapse
Pokemon GO Controls requires
• Root access
• Xposed framework
Instructions
• Download and activate in Xposed installer.
• Reboot the device to complete activation.
• If you are on Android 6 or above, please grant Draw over other apps permissions.
• Press and hold on the Map to set your initial location.
• Press the play button to display the controls, you can drag it around screen by holding on the central blue button.
• Use the options in notification to hide/stop the controls service.
Updates:
Module Updated to V2.1
Download : http://dl-xda.xposed.info/modules/com.axndx.prithvee.pokemongocontrols_v8_03064b_0.apk
Changes:
• Stopping the service no longer requires a reboot. Just press the stop button in the notification and clear Pokemon GO from recents.
• The module now sends proper altitude values.
Tested and working on Pokemon GO v0.37 with Magisk.
V2.0
Minor update V2.0.1 (Added auto walk distance option) :
Updated again at 9 AM GMT, if you downloaded previously, please update again.
Download : http://dl-xda.xposed.info/modules/com.axndx.prithvee.pokemongocontrols_v7_4a08f3.apk
Note: Uninstall previous version app before upgrading to this version.
This update mainly focuses on fixing performance issues in the previous versions, new features will be added in the next update. Please give feedback after trying this version.
Changes:
• Changed the complete working mechanism of the module, now it does not use mock locations and only changes the location inside Pokémon GO. This significantly decreases the memory usage and battery consumption. The only drawback is that there will be a slight delay between the button press and the player movement in game, I'm working on removing this delay. Your actual GPS location is not at all affected now and you can use other apps without any changes.
• Minor UI changes.
V1.4
Download here: http://dl-xda.xposed.info/modules/com.axndx.prithvee.pokemongocontrols_v5_2bb38c.apk
Changes:
• Reduced auto walk speed, now you can hatch eggs.
• Added hide/show controls option in notification.
• Minor UI changes.
V1.3
Download here: http://dl-xda.xposed.info/modules/com.axndx.prithvee.pokemongocontrols_v4_1d222f.apk
Changes:
• Added a search option for map.
• Added auto walk feature, now long press on a button to walk continuously in that direction.
V1.2
Module Updated to V1.2
Download here: http://dl-xda.xposed.info/modules/com.axndx.prithvee.pokemongocontrols_v3_1cc371.apk
Changes:
• Fixed controls disappearing problem, now it stays in memory.
• Added a brand new controller with diagonal navigation support.
• Added ability to set the distance covered on each step.
Tips: Now hold the center blue button to drag around the controls, tap the notification to stop the service.
Image:
V1.1F
Module Updated to V1.1F
Please uninstall the previous version first.
Download here: http://dl-xda.xposed.info/modules/com.axndx.prithvee.pokemongocontrols_v2_f5a2a3.apk
Changes:
• Fixed 'Allow mock location' settings problem
Click to expand...
Click to collapse
Note:
If you have rubber banding problem, download Disable Service app from play store: https://play.google.com/store/apps/d...disableservice
Open the app and go to System tab
1. Search for Fused Location and disable it.
2. Search for Google Play Services and inside it disable Fused Location Service.
Doing this might affect the 'Search a place' functionality.
Thanks to aiversonx3 for the tip.
Click to expand...
Click to collapse
Note : If you try to jump too far or try to skip countries in the game, your Pokemon GO account may get banned. The app developer is not responsible for anything that happens to your Pokémon GO account.
Downloads
Xposed Repo: http://repo.xposed.info/module/com.axndx.prithvee.pokemongocontrols
Click to expand...
Click to collapse
---solved---
Thanks for the mod. Its not working for me. Its allways jumping between the real position and the position i want. Gps is "Gps only". With other mock apps , it was the same. For people it workd, but not for me. I think it is because of my rom. I am using the paranoid rom 6.0.1. Nexus 5x
The same for nexus 5X with latest CM ROM. The same problem is actual for other fake GPS apps and pokemon go. Google maps works fine.
Yes thank you very much for this module, but it does keep rubber banding me back to location, and when it does seem to work i cant catch anything, they run away and the pokestops won't work as well.
Great module, but I've noticed that if the module is installed, if I were to enable mock location, it unchecks itself and doesn't stay checked when I exit the development options menu.
kolayuk said:
The same for nexus 5X with latest CM ROM. The same problem is actual for other fake GPS apps and pokemon go. Google maps works fine.
Click to expand...
Click to collapse
Please try this and let me know, move the apk to system/priv-app, restart and change location
prithvee said:
Please try this and let me know, move the apk to system/priv-app, restart and change location
Click to expand...
Click to collapse
Tried with another app - better, but problem still exists. Btw I found a solution: androidforums dot com slash threads slash fake-gps-use-gmaps-keep-switching-between-real-fake-location.1050124 slash
DeadRubberDucky said:
Yes thank you very much for this module, but it does keep rubber banding me back to location, and when it does seem to work i cant catch anything, they run away and the pokestops won't work as well.
Click to expand...
Click to collapse
Deleted
Whenever I install this module it won't allow me to turn mock locations on. Pls halp
rackerblade said:
Whenever I install this module it won't allow me to turn mock locations on. Pls halp
Click to expand...
Click to collapse
Exact same problem on my A9 Pro
DeadRubberDucky said:
Yes thank you very much for this module, but it does keep rubber banding me back to location, and when it does seem to work i cant catch anything, they run away and the pokestops won't work as well.
Click to expand...
Click to collapse
Had those problem before with other gps haccs. It's not a soft ban so don't worry. What's going on is that the fake gps is just getting overridden by the real one. The best way to test to make sure a gps mod will work is open up googled maps and see if it works there. I'm actually doing about 20 accounts at the same time of this game.
Zaiaku said:
Exact same problem on my A9 Pro
Had those problem before with other gps haccs. It's not a soft ban so don't worry. What's going on is that the fake gps is just getting overridden by the real one. The best way to test to make sure a gps mod will work is open up googled maps and see if it works there. I'm actually doing about 20 accounts at the same time of this game.
Click to expand...
Click to collapse
It's works with google maps it puts me where I placed the mark in the controls
Zaiaku said:
Exact same problem on my A9 Pro
Had those problem before with other gps haccs. It's not a soft ban so don't worry. What's going on is that the fake gps is just getting overridden by the real one. The best way to test to make sure a gps mod will work is open up googled maps and see if it works there. I'm actually doing about 20 accounts at the same time of this game.
Click to expand...
Click to collapse
I'mma need proof or I'm calling bs lol
Hey guys jus thought I'd share how I made it work, first I'm on a nexus 5x pure nexus rom with Xposed of course. Rubberbanding locations solved, go to play store get app called "disable service" disable system files fused locations and inside Google play services same file again fused locations, reboot and you should be not spawning back and forth, check in Google maps to confirm before starting Pokemongo
yes, this was a nexus 5x problem. not the problem of the modul here.
Please help me, I can't tick "allow mock locations"
same here when active mock location they deactivated it automatically
I am not able to reproduce the errors mentioned here, and that is why I can't test the solutions I am creating. Please private message me if anyone is interested in testing the fixes before I upload a new version.
Thank you.
Edit:
1. Please test this and let me know if it solves the Allow Mock Location problem: http://bit.ly/pokecontrolv1_1test
2. If you have rubber banding problem, download Disable Service app from play store: https://play.google.com/store/apps/details?id=cn.wq.disableservice
Open the app and go to System tab, search for Fused Location and disable it.
prithvee said:
I am not able to reproduce the errors mentioned here, and that is why I can't test the solutions I am creating. Please private message me if anyone is interested in testing the fixes before I upload a new version.
Thank you.
Click to expand...
Click to collapse
Hi OP! Thanks for this, it works brilliantly.
I am willing to assist with Testing, you can contact me on Tapatalk or PM on here...
A couple of suggestions right off the bat:
Could we get Diagonal Movements?
Possibility of adjusting the speed or distance of each click?
Temporarily hiding the Controls (Without switching the Service Off)
The test fix for the 'Allow Mock Location' has not worked. At least, not for me. Same issue as before mentioned without any change. Thanks for the updates!
Works fine in my mate 8 without any problems
Life is beautiful

[APP] 21st Oct. ◦ Edge Sense Plus 1.10.0 ◦ Customize Active Edge on your Pixel3

{
"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"
}
Featured by:
XDA-Developers: Customize the Google Pixel 2’s Active Edge to do any action with Edge Sense Plus [XDA Spotlight]​
What is Edge Sense Plus?
Edge Sense Plus was initially just meant for the HTC U series. It let's you customize the squeeze action and adds some more squeeze gestures and features.
But with the Pixel2 and Pixel3 also coming with a squeezable frame I found a way to make it compatible too.
Since google locked active edge down to just only be able to start Assistant it will require a device rooted with magisk
Requirements
You need to run a STOCK based ROM, because Active Edge is broken on AOSP roms.
You need to be rooted with magisk to use it.
Install the Active Edge System Mod Magisk Module from the MagiskManager Repo and the EdgeSensePlus from the playstore and you are ready to go!
Telegram Group
Join Telegram Edge Sense Plus Group
How does it work
To make it working on the Pixel3 I had to modify the SystemUIGoogle.apk that runs the ElmyraService (Service that processes the squeeze gestures).
I intercept the events and pass them to the EdgeSensePlus Application that starts the appropriate action then that you selected.
Some more adjustments were made, so the squeezing also works when you are in immersive mode, camera or when Google Assistant is deactivated/uninstalled.
What can it do?
Custom actions:
Currently you can choose from over different actions
Quickly Start camera - Also when screen is off and locked
Per App Action - Execute different squeeze actions depending in what app you are!
Sidebar
Gesture Panel - Draw custom gestures to start different actions
Custom App
Shortcuts - e.g. to make direct calls, start tasker tasks and more!
Scroll up/down
Flashlight
Recent Apps
Toggle Autorotation
Autobrightness (6 states: Auto, Min, Low, Mid, High, Max)
Split Screen
Expand/Collapse Statusbar
Toggle NFC
Toggle Display on/off
Toggle Autorotation
Toggle DND
Toggle Vibration
Toggle Bluetooth
Toggle WiFi
Music Play/Pause
Previous Track
Next Track
Toggle Keep awake
Google Assistent
Lock Screen
Back
Home
Toggle Sync
Sync all accounts
Previous App
Take Screenshot
Clear all notifications
GPS
Answer/End call
Immersive Mode
Shell command
Per app actions:
With the per app action, you can define different squeeze actions per app. So the chosen action will be executed dependent in what app you are currently are.
Double Squeeze: (Premium)
If you often accidentally trigger a short squeeze, that won't happen anymore if you map your desired action to the double squeeze gesture.
You can define a double squeeze interval, to ensure you are quick enough to trigger it every time.
Long Squeeze:
Missed a long squeeze action on your Pixel? Edge Sense Plus has it!
G-Sensor usage: (Premium)
If enabled, will be able to execute different actions depending on the current position of your device, whether it is flat or upright in your hand.
That way you can have six different squeeze gestures: short, long, doublepress in flat or upright device position.
Media control:
The media control will override your set squeeze actions while media is playing so you can control your media.
That includes play/pause, increase/decrease volume and skip to next and previous track.
Squeeze sounds:
Ever thought it would be funny if a squeeze of your Pixel3 would make a sound, if it is a *click*, *oink* , *fart* or whatever you think of?
You can use any .mp3 file to make that happen!
Sidebar:
The Sidebar has 4 different panels, Applications, Shortcuts, Recent Apps (Premium), Quicksettings (Premium).
Panel colors are customizable
Instructions
You must be on at least Oreo 8.1 to to be able to use it. Root with Magisk is required since the magisk module is mandatory!
It is recommended to have a working TWRP backup in case something goes wrong. Check the FAQ for help too.
Like always: Flash on your own risk. I'm not responsible for any damaga to your device
Flash the Magisk Module either in Magisk Manager or TWRP
Install Edge Sense Plus
Enjoy.
Downloads
Now also available via the MagiskManager Repo:
I recommend to install and update the Magisk Module directly via the MagiskManager repository directly in the MagiskManager app.
All releases will be also available on the GitHub repository
Edge Sense Plus:
FAQ
Q: Will it also work on the Pixel 3 XL?
A: Yes, it will. The Magisk module is multi device and version compatible. There is a separate thread on the Pixel 3 XL forum. though
Q: My device bootloops after flashing the magisk module.
A: Ensure you are on the latest Pixel 3 OTA. To get out of the bootloop, go to the magisk thread and install the magisk uninstaller and then reinstall magisk again.
Q: The magisk module zip is greyed out when I try to install it.
A: I have no explanation why it happens for some. Install a FileManager like SolidExplorer or FX File Explorer, then Select that File Browser in the System File Explorer to select the path
feature request
Would it be possible to add squeeze to take a photo? Really enjoy your app, thanks!
bloodsand said:
Would it be possible to add squeeze to take a photo? Really enjoy your app, thanks!
Click to expand...
Click to collapse
Enable the root toggle at the very bottom. It'll unlock some more action, one of them is "Camera" and it will take a photo, if you are within the camera app.
If you are not, it will start the camera app first, then you need to squeeze another time to take a picture.
j to the 4n said:
Enable the root toggle at the very bottom. It'll unlock some more action, one of them is "Camera" and it will take a photo, if you are within the camera app.
If you are not, it will start the camera app first, then you need to squeeze another time to take a picture.
Click to expand...
Click to collapse
Just what I was looking for! Cool
bloodsand said:
Just what I was looking for! Cool
Click to expand...
Click to collapse
You are welcome. Leave a rating in the play store if you don't mind.
Sent from my HTC U11 using Tapatalk
Awesome job brother, works perfect on my Pixel 3! Left you 5 star feedback on the Play Store,,,keep up the great work! As an added benefit, because of the way your app draws from framework its transparent on my Translucent Substratum theme which means one less app to theme,,look cool to me
How does one unlock premium? It doesn't seem to work...
arodey said:
How does one unlock premium? It doesn't seem to work...
Click to expand...
Click to collapse
Switched to dark mode?
There is a little bug after switching to it, that dialog is empty. Close the app completely and remove it from the recent apps screen and it should work.
Will fix that bug later today though.
Sry for the troubles.
Sent from my HTC U11 using Tapatalk
j to the 4n said:
Switched to dark mode?
There is a little bug after switching to it, that dialog is empty. Close the app completely and remove it from the recent apps screen and it should work.
Will fix that bug later today though.
Sry for the troubles.
Click to expand...
Click to collapse
Thank you!
Hmm. It seems to not want to unlock premium anymore?
State.of.mind said:
Hmm. It seems to not want to unlock premium anymore?
Click to expand...
Click to collapse
You purchased it on your Pixel3, it unlocked premium and then suddenly premium was gone?
That sounds weird. PM me your mail adress please.
j to the 4n said:
You purchased it on your Pixel3, it unlocked premium and then suddenly premium was gone?
That sounds weird. PM me your mail adress please.
Click to expand...
Click to collapse
Mine does it too at times...when I go to app premium is gone.
That really shouldn't happen.
The above post is a bit missleading, since he purchased on the Pixel2 and installed it now on the Pixel3. The Premium Version is per device though.
Once you are premium on a device, it will stay premium.
j to the 4n said:
You purchased it on your Pixel3, it unlocked premium and then suddenly premium was gone?
That sounds weird. PM me your mail adress please.
Click to expand...
Click to collapse
drocny87 said:
Mine does it too at times...when I go to app premium is gone.
Click to expand...
Click to collapse
I had this happen too immediately after I purchased it. However, killing the app and restarting it brought it back.
j to the 4n said:
That really shouldn't happen.
The above post is a bit missleading, since he purchased on the Pixel2 and installed it now on the Pixel3. The Premium Version is per device though.
Once you are premium on a device, it will stay premium.
Click to expand...
Click to collapse
Curious as to if the premium version being per-device is a licensing limitation or a personal decision?
I only purchased it on my Pixel 3 and have the issue. Sometimes killing the app and restarting it will bring back premium
cambunch said:
I had this happen too immediately after I purchased it. However, killing the app and restarting it brought it back.
Curious as to if the premium version being per-device is a licensing limitation or a personal decision?
Click to expand...
Click to collapse
Personal.
Put so much time into this app and also a lot into the magisk modules for the Pixel.
Unfortunately limited to a small userbase since it needs root and the app works just works just on a couple devices, since it is tied to the squeezable frame.
Just trying to fill the vacation saving for my family a bit and a new baby seat for our 2nd son.
I'm really not mad at anyone though pming me and asking for a free premium key if they bought it on the Pixel2 already.
Already did that a couple of times today.
j to the 4n said:
Personal.
Put so much time into this app and also a lot into the magisk modules for the Pixel.
Unfortunately limited to a small userbase since it needs root and the app works just works just on a couple devices, since it is tied to the squeezable frame.
Just trying to fill the vacation saving for my family a bit and a new baby seat for our 2nd son.
I'm really not mad at anyone though pming me and asking for a free premium key if they bought it on the Pixel2 already.
Already did that a couple of times today.
Click to expand...
Click to collapse
No need for justification, just curious as I am working on an app with some IAPs and wanted to know more about your setup. Wasn't sure if there was something different due to Magisk, etc.
Keep up the good work! Long squeeze for killing the foreground app and toggling the flashlight on screen off are enough to justify the purchase for me!

Categories

Resources