How well does gravitybox work with the flex? I searched for it and didn't find really anything.
It works like a charm..i allways use the smart radio to save battery..it switches automatically between 3g/2g..
Everything I read about it says don't use unless you have a CR. Unfortunately, I do not, so I am leary of using it without one.
I wouldn't do much of anything with xposed mods if I didn't have a custom recovery. So many mods can be so wishy washy especially when you have to reboot.
Right.
Related
I know that custom ROMs do this easy as pie, especially CM-based ROMs which tend to still be my favorite ones overall, but since the Active has a locked bootloader and apparently not enough serious interest so far to possibly ever get such a thing, does anyone have any idea of how to add such functionality to the stock AT&T ROM (SGH-i537 is my device, of course)?
I know PowerAMP claims to have such capability but I swear that I've tried that app on several devices and it's never worked even when I enable the option in the settings of the app so I'm not even going to try anymore with that one.
My GS4A is carrier unlocked and rooted as well (geohot's method) so I'm not sure if I need to install some root-required app to patch something, or just install a patch of some kind or whatever. If it's a kernel based thing then obviously I'm out of luck there, but if there's some way to enable that aspect it would be a great thing.
And yes I know about the torch functionality with a long press of Volume Up, but I don't have any real use for that so being able to control the music playback (Next/Previous with long presses) would be awesome.
If anybody has any info, I'd be grateful to hear it.
You need to install the Xposed framework and Wanam Xposed. There are a ton of options to tweak Touchwiz in addition to enabling volume rocker support for music apps. I use it and it works perfectly.
http://forum.xda-developers.com/showthread.php?p=44067239
Also check out the Wanam module. I use both this and Nottach.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Devo7v said:
You need to install the Xposed framework and Wanam Xposed. There are a ton of options to tweak Touchwiz in addition to enabling volume rocker support for music apps. I use it and it works perfectly.
http://forum.xda-developers.com/showthread.php?p=44067239
Click to expand...
Click to collapse
OUTSTANDING!!! Thanks for the info, will get on it when I get some free time today for tinkerin' around.
EDIT:
Yep, it works exactly as noted, so thanks again. Funny though, it doesn't work for the native music app on GS4A (presumably a mod of the stock Android music player since it appears to be a bit modded, I don't know for sure). Works with Play Music which is fine, I still keep my tunes local on the microSD card anyway, no sense wasting bandwidth for nothing.
Awesome...
Please read forum rules before posting
Questions and Help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Don't know if this has been reported, but the last couple of nightlies cause certain GB QS tiles to be blank (e.g. data, location), and the battery tile to register 0%.
Sent from my Nexus 4 using Tapatalk
bruce7373 said:
Don't know if this has been reported, but the last couple of nightlies cause certain GB QS tiles to be blank (e.g. data, location), and the battery tile to register 0%.
Click to expand...
Click to collapse
Installed GravityBox on 2013-12-08, worked nicely. Upgraded to 20131210 nightly via OpenDelta today, having to reinstall Xposed framework now.
husky69 said:
Installed GravityBox on 2013-12-08, worked nicely. Upgraded to 20131210 nightly via OpenDelta today, having to reinstall Xposed framework now.
Click to expand...
Click to collapse
Reinstalling the Xposed framework didn't help.
Sent from my Nexus 4 using Tapatalk
bruce7373 said:
Reinstalling the Xposed framework didn't help.
Click to expand...
Click to collapse
It helped for me. I had to open Xposed framework app again and to reinstall the framework parts, reboot- and it looks like GG works again.
It's always been the case that the framework had to be reinstalled and it does reactivate GB, but the QS tiles are still messed up. Are you saying you're not having this problem?
Sent from my Nexus 4 using Tapatalk
GB/XPosed also say explicitly not to use them with custom ROMs, or at your own risk.
dibblebill said:
GB/XPosed also say explicitly not to use them with custom ROMs, or at your own risk.
Click to expand...
Click to collapse
True that. It was working on N4 up until the 12/9 update. I tried reinstalling GB and restored data from a Titanium backup and it seemed to work... until I rebooted again. Ah well, I can live without those tiles if everything else is working.
Sent from my Nexus 4 using Tapatalk
dibblebill said:
GB/XPosed also say explicitly not to use them with custom ROMs, or at your own risk.
Click to expand...
Click to collapse
Yup. While I am a big fan of Xposed, and GravityBox is awesome on devices without custom firmwares, use of either of them is an unsupported configuration that is invalid for bug reports.
Entropy512 said:
Yup. While I am a big fan of Xposed, and GravityBox is awesome on devices without custom firmwares, use of either of them is an unsupported configuration that is invalid for bug reports.
Click to expand...
Click to collapse
Is there anything that comes close to being a viable alternative?
Sent from my Nexus 4 using Tapatalk
I read somewhere that 4.4.1 broke GB.
Sent from my Nexus 7 using Tapatalk
The main reason I installed Gravity Box is because of the customizable QS tiles and the lockscreen shortcuts. I believe sooner or later these features will be implemented on OmniROM. Then I won't have the need for it.
If your tiles are messed up after restarting / updating, try to disable Gravity Box from Xposed framework app, clear the Gravity Box settings, reboot, re-enable Gravity Box, reboot again, customize Gravity Box and try not to restart the phone again because you will face the problem again.
Quick Settings
Omni will have Quick Settings customization ?
timbalong said:
Omni will have Quick Settings customization ?
Click to expand...
Click to collapse
I'd be very surprised if it didn't. But I doubt it's up high on priority list...
Another reason to use GB is their circular battery has the correct kitkat color (not always 100% white) and it's vertically aligned with the rest of the icons.
I noticed that toggles, that mess up are "flippable" ones. I don't use that exclusive feature of omnirom, so it would be very nice if developers added checkmark in settings that would disable this feature.
p.s. Hoped that new 4.2.2 omni update will fix this problem, but it didn't.
p.s. 2. If you want to use other features of GG, just don't touch quick toggle settings, or they will mess up after reboot
I noticed this also and it was asked about in the t-mobile note II omnirom thread. Someone said that if you disable the module, reboot, clear app data, re-enable the module, reboot, then just leave all the tiles as is (for example, don't modify anything) then the tiles survive a reboot. Kinda defeats the purpose, since you can change anything but at the very least all the tiles still work and you can still flip them without it breaking. Hopefully it gets fixed soon
The title of this thread is not entirely correct. Omni didn't break GB; KitKat is moving forward, 4.4.2 is progressing and GB is an xposed module that's not keeping up the pace for now (not that it should, thought).
Native customization will be coming soon, I believe. Omni devs are working on the foundations, we can't ask from them to drop that to get their hands on customization right now. But it's on the roadmap, and considering how fast they brought us a clean code and stable KitKat, that will probable come fast.
For now, we got other options too. For example, there are apps that bring toggles to the notification drawer without needing xposed.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Title for this thread should be "Latest nightlies doesnt work with a mod that is recommended not to be used with omniRom"
Sent from my phone using some app
I've been trying to fix this the past few days, glad to know it's not user error but lack of official current support. GB should definitely take the opportunity to merge or stand out as a reliable module very soon. Once someone else takes what they have and can keep up, who knows.
Let me join this discussion to make things more clear.
I don't intend to write too many lines about GB's history, its main goal and policy but I'd like to mention one important thing.
GB is basically a non-flashing custom ROM which primary goal is to bring custom-rom like experience to closed-source platforms (like MediaTek) which currently don't have opportunity to have custom ROMs built from source.
Later while evolved, the secondary goal was established - to bring custom-rom like experience to devices running stock Android.
What I see happening around Xposed Framework recently is that people are basically often turn to using it to "patch" what they can't find in a custom ROM. However, Xposed modules (especially the complex ones) should not be used to supplement missing features in custom ROMs built from source. The best option for a user is to go ask devs of the custom ROM he uses and request those missing features. (This is also clearly mentioned in GB's official thread). People don't combine two ROMs in one device to get more features, neither (thanks god it's not possible!)
GB is not here to keep track of what's changing in all custom ROMs available out there. It is simply unmanageable. GB is here to extend the stock Android experience just like any other custom ROM does.
And words like "GB can't keep up pace with KitKat" sound funny. Actually, it keeps up with stock KitKat pretty well.
I understand these words come from people who have zero experience with GB, but anyway.
GB is currently fully compatible with the latest stock KitKat and is even bringing Dialer tweaks in upcoming version which none of custom ROMs have to this day (flip actions, call vibrations, etc.).
I've been running into Daydream problems in conjuction with Xposed Installer. Specifically with Clock plus DayDream by @martinpelant.
You can find all the information I was able to gather here: http://forum.xda-developers.com/showpost.php?p=54258696&postcount=31
As I think this is more a problem of that app I posted the information there. However, when I uninstalled Xposed Framework (that is to say the patches to the system, not the Installer nor the applications that use Xposed) the problem was also gone. Before that step I also tried unselecting ALL Xposed modules and rebooting, deactivating them, uninstalling, etc, etc. As I said the app began working correctly after uninstalling Xposed Framework and problem arose again upon installing the Framework. I must also mention that this problem only happen when using Clock plus Daydream as I tested with other "daydream" apps and they work properly.
In the aforementioned post you will find catlogs, a video and some other information that might be useful.
PS: I repurposed this post as I first posted the problem here before realizing the culpruit was Clock plus
J_M_V_S said:
I've been trying to solve this for the last couple of days. I'm not certain that this is an Xposed bug/problem but seems to be the most likely and that's why I post this here.
Click to expand...
Click to collapse
This looks like a short wakelock to me. As Xposed doesn't use any wakelocks, it seems unlikely that it's the culprit. I obviously can't speak for all the modules, so you should try if it still occurs if you disable them. Or even easier: Just press the uninstall button in Xposed Installer and reboot. If it still occurs, you can be sure that it's neither Xposed nor any module.
rovo89 said:
This looks like a short wakelock to me. As Xposed doesn't use any wakelocks, it seems unlikely that it's the culprit. I obviously can't speak for all the modules, so you should try if it still occurs if you disable them. Or even easier: Just press the uninstall button in Xposed Installer and reboot. If it still occurs, you can be sure that it's neither Xposed nor any module.
Click to expand...
Click to collapse
I'm really sorry @rovo89. I was in the middle of this post when I was able to find the problem. Somehow it seems I pressed the Post button on the unfinished post. Really sorry about that. The problem was (is) on Clock Plus Daydream. I will repurpose the OP as Xposed might still be somewhat responsible.
Is it possible to enable 180 and 360 rotation for the whole phone on a stock based rom?
It was possible on the S4 using Wanam Xposed, so you will probably need that if it's made for the S10 line or something similar to it.
StoneyJSG said:
It was possible on the S4 using Wanam Xposed, so you will probably need that if it's made for the S10 line or something similar to it.
Click to expand...
Click to collapse
Yeah every solution seems to need exposed which Im trying to stay away from since xposed will not pass safetynet anymore from what I understand. I was hoping there was a file edit some where that could do it. Therr used to be a way to do with build.prop edits but seems that doesn't work on newer Android os. I did however find someone who posted and ingenious way that works temporarily, if you open google maps, navigate to anywhere and then exit maps you can rotate any direction, doesn't work for apps with forced orientation though but better than nothing for now.
Hi. I use a tablet permanently in landscape mode. But in many apps when keyboard pop up, it uses all the screen. In many cases you don't even see what you typing regardless the all screen view.. I really don't understand why they made it this way. I remember in past there was an xposed plugin to fix this. Can't be done something with magisk? I think it is just to much to install xposed only for this. Is there any way to use xposed only for this, without making the system slower?
Thanks,
sosimple said:
Hi. I use a tablet permanently in landscape mode. But in many apps when keyboard pop up, it uses all the screen. In many cases you don't even see what you typing regardless the all screen view.. I really don't understand why they made it this way. I remember in past there was an xposed plugin to fix this. Can't be done something with magisk? I think it is just to much to install xposed only for this. Is there any way to use xposed only for this, without making the system slower?
Thanks,
Click to expand...
Click to collapse
It's so so annoying, I fully agree! Unfortuately I don't know other ways to do that, but you caught my attention with this Xposed module... Do you remember its name? If it's old, it probably won't work on newer Androids, but maybe worth a shot since I use Xposed
sosimple said:
Hi. I use a tablet permanently in landscape mode. But in many apps when keyboard pop up, it uses all the screen. In many cases you don't even see what you typing regardless the all screen view.. I really don't understand why they made it this way. I remember in past there was an xposed plugin to fix this. Can't be done something with magisk? I think it is just to much to install xposed only for this. Is there any way to use xposed only for this, without making the system slower?
Thanks,
Click to expand...
Click to collapse
Actually I did a quick research and found out that this module is present in Play Store. And moreover, it's still working on Android 11! Thank you so much for the hint!
As for Xposed, these days we have much more device-friendly Xposed solution named LSPosed. It allows to hook only the apps that are necessary for a module to work. I really recommend it for you if you won't find any other solution. Also I use many other useful modules, if you are rooted and familiar with Xposed to some extent, it's a great field to explore
Lord Sithek said:
Actually I did a quick research and found out that this module is present in Play Store. And moreover, it's still working on Android 11! Thank you so much for the hint!
As for Xposed, these days we have much more device-friendly Xposed solution named LSPosed. It allows to hook only the apps that are necessary for a module to work. I really recommend it for you if you won't find any other solution. Also I use many other useful modules, if you are rooted and familiar with Xposed to some extent, it's a great field to explore
Click to expand...
Click to collapse
Thanks.. I already reading how to install xposed.. I'll read about LSPosed then...
I readed that an xposed plugin, Apps settings reborn, is still has a working version of full screen keyboard fix per app, and dpi changing per app. And jt works in android 11.. It looks good.
sosimple said:
Thanks.. I already reading how to install xposed.. I'll read about LSPosed then...
I readed that an xposed plugin, Apps settings reborn, is still has a working version of full screen keyboard fix per app, and dpi changing per app. And jt works in android 11.. It looks good.
Click to expand...
Click to collapse
Oh, I have this module installed too and didnt know it has this feature! By the way, LSPosed doesnt have the official thread on XDA (the one existing is unofficial, created by a regular user to discuss about it), but they have official Telegram chat and channel, easy to find
Well i installed it, it looks promising. But for full screen keyboard fix, it doesn't looks like app settings reborn sstting is working.. Most other settings work, so it looks like, some do, some doesn't.. Perhaps i must find an xposed plugin especially for this if it still works..
I'll post if i have a solution.
Edit, it works after all. I set to not display keyboard in full screen, to the app i wanted + system ui + SwiftKey keyboard.. And reboot. Something of all this did the trick..