yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] m0han:
log added

not sure if you meant "which KK version of GravityBox is not designed for".

gb v3.2.1 (jb) ran without errors

on the same device

(jb 4.2.1), till a few hours back.

here's an old log i found:

-----------------

Jun 28, 2014 3:29:35 PM UTC

Loading Xposed v54 (for Zygote)...

Running ROM 'XOLO_Q3000_S011_25022014' with fingerprint 'XOLO/Q3000/Q3000:4.2.1/JOP40D/1393321357:user/release-keys'

Loading modules from /data/app/com.oasisfeng.greenify-2.apk

Loading class com.oasisfeng.greenify.pro.FrameworkPatch

Loading class com.oasisfeng.greenify.pro.SettingsPatch

Loading modules from /data/app/com.hamzah.xposedstatustext-1.apk

Loading class com.hamzah.xposedstatustext.Main

Loading modules from /data/app/com.ceco.gm2.gravitybox-1.apk

Loading class com.ceco.gm2.gravitybox.GravityBox

GB:Hardware: mt6589

GB:Product: Q3000

GB:Device manufacturer: XOLO

GB:Device brand: XOLO

GB:Device model: Q3000

GB:Device type: phone

GB:Is MTK device: true

GB:Is Xperia device: false

GB:Has Lenovo custom UI: false

GB:Has telephony support: true

GB:Has Gemini support: true

GB:Android SDK: 17

GB:Android Release: 4.2.1

GB:ROM: XOLO_Q3000_S011_25022014

GB:PatchMasterKey: Patching MasterKey vulnerabilities

Loading modules from /data/app/de.defim.apk.bootmanager-1.apk

Loading class de.defim.apk.bootmanager.Xposed

[BootManager] 2014-06-28 15:29:38 loaded 15 restricted apps

Loading class de.defim.apk.bootmanager.Xcheck

Loading modules from /data/app/de.robv.android.xposed.mods.appsettings-1.apk

Loading class de.robv.android.xposed.mods.appsettings.XposedMod
[Xposed Framework Modules] fbf2201:
I would say 50 % of all of the posts are related to unsupported devices. Just because of the people are not willing to read the OP.

I would really appreciate a disclaimer within GravityBox, when opening it for the first time.
[Xposed Framework Modules] trjlive:
Actually, neither the KitKat nor Jelly Bean version of GravityBox is designed for your device. The fact that the JB version worked for you is pure luck, as GB was not designed for or tested on that particular device.

Regardless of the JB version working on your device, KK is a major upgrade from JB, and a lot of code changes. GravityBox had to be rewritten for KK, and in doing so, was again only tested on and designed for pure AOSP devices - Nexus and GPE.

So obviously something changed between the JB and KK version that makes it not work properly on your device, but unfortunately, that's just the fact of life when using a mod that's not designed for your device.

---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------

Oh I would venture to say it's even higher than that, maybe 75%... ;)

I brought up the disclaimer idea in the past, though I can't remember what the response was at that time. But I agree, something like that would be a good idea. Even though the Xposed repo description is quite self-explanatory, just like this thread's OP, it just amazes me how many people will install something without spending 30 seconds to read about the mod.

Another idea, throw up a "Warning, this is not designed for your device and you WILL experience problems" alert for any unsupported device. You wouldn't even have to maintain a list of all unsupported devices, just have it appear it the device is NOT a supported device - ie "if NOT Nexus or NOT GPE then SHOW ALERT".
[Xposed Framework Modules] m0han:
i guess i'd leave it at that, but, in case you're interested and haven't noticed yet, i just updated my post with a log.
[Xposed Framework Modules] trjlive:
Just realized something, your device is MTK device. The JB version of GravityBox had experimental MTK support, while the KK version does not support MTK. So that's the major difference that affects your device.
[Xposed Framework Modules] cableghost:
Hey thread police...it's not always a ROM issue. It may just be a setting issue, or a conflict with another Xposed mod or even a regular app that discussion herein could ascertain and find a solution to. I have a Moto stock ROM and have the paid-for GB KK mod; 99.9% of the options I've enabled, work. It's only been a conflict with another mod, or some incorrect setting that GB options have not worked. I'm no programmer, but not so lazy as to just call it a ROM issue. Try providing some basic points before resorting to the 'ROM issue' as a response, if you care to provide any assistance.
[Xposed Framework Modules] trjlive:
I guess there are a lot of people who don't understand what the word "unsupported" in the english language means.

un·sup·port·ed (adjective): not having assistance for the user available from a manufacturer or systems manager.

I'll try to clear it up. It doesn't necessarily mean it won't work on your device, it means you won't get any support in this thread or from the developer. So regardless of whether it's a ROM issue, or just a simple glitch with another mod, if your device is not a Nexus or GPE device, then

this thread is not the place to post your problems

.

You are welcome to create your own thread for issues on unsupported devices. But C3 has stated that

no exceptions will be made for unsupported devices

. This thread is for people using the two classes of devices that GravityBox is actually designed for - Nexus and GPE devices. Anything else just clogs up the thread and confuses people. Providing troubleshooting steps, as you suggest, for unsupported devices, is in effect, providing support, which is not in the scope of this thread.

So people who insist on posting and asking for support, are basically saying that even though they know they have an unsupported device, they don't think the OP applies to them and they feel they deserve support anyway. You're basically disregarding the OP, and this just feels disrespectful to the developer, if you ask me. He designed GB to be used with very specific devices. You are free to use it on other devices if you desire, but you're on your own for that, in other words, no support from this thread, hence the term "unsupported".
[Xposed Framework Modules] Puzzlegirl:
If it wasn't for you, I wouldn't be able to keep up with this thread. Your patience and efforts are very much appreciated!
[Xposed Framework Modules] Miqueas111:
Moto G GPE

Thank you so much for a full answer.

Last question: Will it work if I turn my Normal Moto G into a Google Play Edition?

Anyway I'm think I'm gonna try, of course, an answer would be great :laugh:

Thanks all.
[Xposed Framework Modules] trjlive:
Absolutely! There have been many users who have converted their Moto G devices to GPE editions, and then have zero issues with GravityBox. In fact, there are several really good threads in the Moto G forums about this very process.

The only caveat, however, is depending on which version of the Moto G you have, if you can unlock the bootloader to be able to flash custom ROMs. For example, in the USA, the Moto devices purchased from AT&T are bootloader locked, and AT&T has prevented Moto from allowing them to be unlocked. Moto devices purchased directly from Moto or from T-Mobile for example, can easily be unlocked on the Moto Developer website.

So if you are able to unlock your bootloader and flash a custom recovery, then you should have no problem converting to the GPE edition. I don't have the thread's link available right now, as I'm on my N5, but I know it's a pretty popular one in the Moto G forum, so you should be able to find it pretty easily. [emoji106]

Sent from my Nexus 5, so please forgive any typos.
[Xposed Framework Modules] PhyerFly:
I have the exact same issue. Nexus 5, Android 4.4.4 stock + rooted and after upgrading GB to 3.2.5 I was getting about 30% of my normal battery life. I had my phone die in my pocket before lunch after charging all night. According to BetterBatteryStats and Gsam Battery Monitor that mCastSocketMultiplexer.mWakeLock is what was causing Google Play Services to use 60% of my battery. Disabling the GB module entirely was the only thing that solved it.

I'd be happy to provide logcat or BBS dump info if that would be useful.
[Xposed Framework Modules] trjlive:
Update: in regards to my previous reply to you, here is the thread I was referring to about converting your Moto G to a GPE edition. I haven't personally tried this MotoTool AIO app, since I don't have a Moto device, but from the thread it appears to be a pretty straightforward process. :good:

http://xdaforums.com/showthread.php?t=2635706

If you are able to convert to GPE, and get GravityBox working, come back and let us know. I, for one, will be interested to know how it worked out for you! :)

---------- Post added at 11:56 PM ---------- Previous post was at 11:51 PM ----------

I looked into a few of the logs that were previously posted about this issue, but didn't see anything conclusive. But if you'd like to post your logs, I'll certainly take a look and let you know if I find anything odd in them. Logcat, Xposed log, and BBS dump would be excellent. Either attach them to a reply post, or upload them to a file-sharing site and link to them.

Just a quick question though, after updating to 3.2.5, have you tried killing the Play Services process and then clearing data for Play Services app? Then re-launch play services and it might ask you to log back into your google account, or if you only have 1 account set up, it should log back in automatically. Reboot your device and see if Play Services is still misbehaving. If so, go ahead and post the logs and I'll check them out for you.

Edit: oh and just for the record, I seem to have the same set up as you: Nexus 5, stock 4.4.4, rooted with Superuser in recovery, Xposed and GravityBox 3.2.5, and I'm not getting any excessive wakelocks. So I'm really curious what exactly is different about yours then with mine.
[Xposed Framework Modules] PhyerFly:
It wasn't originally clear the GB was the cause so I tried to systematically diagnose it. Other than the obvious settings like turning wifi on/off, explicit screen brightness etc. each time I made a change I rebooted, set a new reference point in GSam battery monitor and waited about an hour.

Here's what I tried:

Settings -> Accounts -> Google -> Unchecked every sync item

Settings -> App -> All -> Google Play services -> Clear Cache

Settings -> App -> All -> Google Services Framework -> Force Stop + Clear Data + Clear Cache

Settings -> App -> All -> Google Search -> Force Stop + Clear Data + Clear Cache

Settings -> Location -> Mode -> Changed to battery saver + disabled Google location reporting

Do you have a Chromecast on any of the wifi networks around you? I have a gut feeling it has something to do with Google Play Services enabling screen casting recently on Android because I have at least three Chromecasts on my work wifi network and one at home. This was two days ago, but I *think* I saw that wakelock more often when I was on wifi.

I'll re-enable GB 3.2.5 tomorrow and see if I can reproduce it enough to get you some useful logs.
[Xposed Framework Modules] trjlive:
Ok so you've cleared the data as I suggested, I just wanted to check that since I've seen some Play Services issues resolved with a clear data. But since you're still having issues after that, then something else must be going on. So yes, logs would be great. When you post them, make sure to mention me so I'll see them, and I'll take a look and offer any help I can.

To answer your questions about the Chromecast, yes I do have 2 CCs at home on my wifi network. I'm not sure if there are any on the wifi I use at work, but since it is a Google building, I'm sure there probably are. ;) I've just not noticed or used them there. I'll have to look Monday and see if my device can see any CCs on the network.

My two CCs are both connected to my Apple AirPort Extreme wireless router, which is also what my N5 and N7 (2013) connect to, along with about 15 other networked devices between mine and my girlfriend's various laptops and devices. Between the 2 of us, we're usually casting something to our tv's each night using the Netflix or Hulu apps. I'll usually cast from my N5, and she'll usually use the N7, which is also stock 4.4.4, rooted, Xposed and latest GB, just like my N5.

And I also cast music using the Google Music All Access, and recently started using the screen casting as a way to get Spotify music on our outdoor speakers by the pool. I do notice that spotify sucks down a lot more battery streaming than the Google music app, but I assume that has to do with the screencasting vs. Play Music actually streaming directly to the CC.
[Xposed Framework Modules] belloni:
Hi, when I edit lockscreen features, it doesn't change my lockscreen at all?! Keeps stock, any ideas?
[Xposed Framework Modules] aavvaallooss:
Supported device?
[Xposed Framework Modules] belloni:
Using an Xperia Z2..
[Xposed Framework Modules] kingvortex:
Then you should go ahead and read the first post carefully, like you should have done before installing this module.

Pay close attention to any parts regarding compatibility.
[Xposed Framework Modules] aavvaallooss:
The read the OP, please (Red lines)
[Xposed Framework Modules] Pep Streebek:
Bricked

Hi, Can someone point me in the right direction, I think I've been a silly boy.

Have locked up / bricked my HTC One max running NuSense rom.

Made cwm recovery backup,

Installed framework (got working via soft reboot)

Updated sense toolbox via xposed installer, rebooted working fine.

Installed gravitybox via xposed installer. then on a soft reset its locked up (black screen, not responding, red charging led stays on when power is unplugged).

can't get to recovery via vol/power buttons.

can't see device via adb devices.

Would be removing the battery at this point on my HTC DHD but thats not happening on One max.

JTag or the bin maybe?

Bbit screwed at the moment, can anyone help?
[Xposed Framework Modules] ffejy462:
Make sure device is NOT plugged in while trying to boot to recovery with button combo. You may have to hold the power button for quite a while to reboot or power down (30s-1min). I highly doubt it's gravitybox related...
[Xposed Framework Modules] mdamaged:
If I'm reading right, you are trying to use GB on a HTC with Sense, if so, that might be the cause of your problems, since the OP explicitly states it is not compatible with Sense.
[Xposed Framework Modules] Pep Streebek:
hi, tried a few time with the power out holding down vol/power for 30secs, 1min, 2mins to no avail.

probably means nowt but there's a very quite "click-click" from the speakers (only heard at ear). charging light stays on without power cord.

---------- Post added at 08:57 PM ---------- Previous post was at 08:49 PM ----------

yeh it's HTC One max with NuSenseSIX rom & I shouldn't have installed GB

just thought I would be able to cwm recover if went wrong.

now Im stuck. any ideas how to get recovery?
[Xposed Framework Modules] mdamaged:
Sorry, no idea, I do not own that device. You would probably get quicker help here...where I see you already posted.
[Xposed Framework Modules] Pep Streebek:
seen thx anyway.

gonna let it go totally flat kind of emulating a battery pull i guess , see what goes on...

EDIT:

sorted it out thanks to thayl0. got the one max to reboot fully.

better go remove GB.
[Xposed Framework Modules] areq1987:
Unfortunatley it slows down moto g while charging. :(
[Xposed Framework Modules] trjlive:
Well, for starters, as is clearly stated in the OP, GravityBox isn't designed for the Moto G, so bugs are to be expected. But I'm curious what you mean by "it slows down ... while charging". What exactly slows down? I have not yet heard of this particular issue with Moto devices, so clarification would be good.

---------- Post added at 03:23 PM ---------- Previous post was at 03:19 PM ----------

Yeah, I wouldn't recommend using GravityBox with a Sense device, since GB is only designed for Nexus and GPE devices. Any other custom ROMs, which include OEM custom like TouchWiz and Sense, have been changed so much that they are not compatible and cause issues. There are other Sense-specific mods and toolboxes in Xposed repository, just make sure you are installing mods designed for Sense devices.

On another note, I'm going to recommend you also get in the habit of fully reading a mod's OP before you download and install it. Your troubles could have been completely avoided by reading this thread's OP, and you would have known beforehand that it's not designed for Sense devices. Just trying to offer some friendly advice, reading OPs in their entirety before installing things will greatly reduce the frustration and potential problems later down the road. :)
[Xposed Framework Modules] areq1987:
It was animated battery status indicator. It has slowed down my phone performance while charging. I changed to static indicator and now everything looks great. :)
[Xposed Framework Modules] trjlive:
Ok, well that's good to know the animated battery indicator causes additional issues on Moto devices. I'll also mention that the most common bugs that occur when using GB on Moto devices have to do with status bar and nav bar mods. Motorola has changed these two components significantly from stock AOSP that it causes many issues for GB trying to inject its changes. So any time you're experiencing problems having to do with either the nav bar or status bar, I would recommend disabling any related GB mods, and your issues should go away.

On another note, if you want to have a much better GravityBox experience with your Moto G, I would suggest you consider converting it to the Moto G "Google Play Edition", which is a pure AOSP ROM which is 100% supported by GravityBox. Here is a thread that describes how to do this. Provided you have a Moto G that allows to unlock the bootloader and install a custom recovery, you should be able to do the conversion pretty easily.

http://xdaforums.com/showthread.php?t=2635706
[Xposed Framework Modules] kinganu123:
I think this may be where the issue lies. Not many people have multiple CCs on their network, and I did notice that mine didn't really come up UNTIL I got to work, where there are at least 4 in one area. Of course, this is assuming that the wakelock is for CCs.
[Xposed Framework Modules] spychodelics:
Is it possible to add a reboot tile in the quickest tings?
[Xposed Framework Modules] cd69:
If it helps. Long press on sleep tile opens reboot panel.
[Xposed Framework Modules] ffejy462:
You can also add a quickapp tile and set the activity to show power menu.
[Xposed Framework Modules] グリッチ:
I looked for the log in the directory specified in the OP, but there was no such thing. Another fix I use, that seems to be working fine, is just going into Settings > Personalization > Status Bar Icons > Uncheck the battery icon(s).
[Xposed Framework Modules] spychodelics:
Thank you guys, that was what i was searching for
[Xposed Framework Modules] android addicts:
After activating this module CM11 (Galaxy S3 i9300 Android 4.4.4) ROM, randomly I face, unfortunately the system UI stopped the error. Then it automatically locks the screen.
[Xposed Framework Modules] kingvortex:
I suggest you thoroughly read either the description of the module in the Xposed repo or the first post of this thread, like you should have done before installing this module, paying close attention to any sections regarding compatibility and use on custom roms.
[Xposed Framework Modules] yochananmarqos:
You can save an log directly from the Xposed Installer now. Choose Logs then Save to SD Card from the menu.
[Xposed Framework Modules] laogiacodai:
Hi All,

After changed battery icon, if we plug charging cable, the stock battery icon will appear along with the mod icon?

Do you have the same issue?

Send from Lenovo P780 KK ROW214
[Xposed Framework Modules] aavvaallooss:
No, because we're on supported devices/ROMs
[Xposed Framework Modules] trjlive:
As is clearly detailed in the OP, but I'll mention it here again,

GravityBox is designed for Nexus and Google Play Edition devices

. If you choose to use it with a device it wasn't designed for, then you do so at your own risk and fully away that you will properly experience some problems with it. And just because a feature may work for you today is no guarantee that it will continue to work. At any time, either a ROM or GravityBox update may break any/all GravityBox features.

I'm also going to recommend that you get into the habit of reading a thread's OP it its entirety, preferably before you even download and install something, but at the very least when you experience problems and before posting. This way, you would have already known why you were experiencing problems, and could have save some frustration for yourself, as well as prevented the frustration of other users in this thread who get annoyed seeing the same questions day after day from users who don't read the OP.
[Xposed Framework Modules] Conan179:
hello whrer i can deaktivate the transperity on my notifaction bar (this menü, i swipe down) ?
[Xposed Framework Modules] kingvortex:
Statusbar tweaks -> Notification drawer style -> Background transparency.
[Xposed Framework Modules] Conan179:
hmmm 0% my notifictaion is transparency, 100% my notifictaion is transparency.

also by my not working.
[Xposed Framework Modules] yochananmarqos:
Sounds like you could be using either a custom ROM that already has notification drawer settings or you have an another app / module that is conflicting.
[Xposed Framework Modules] trjlive:
What device and ROM are you using?

Sent from my Nexus 5, so please forgive any typos.
[Xposed Framework Modules] Sabissimo:
Hey guys,

I've tried to search the thread, but no luck

In 3.2.3 i had enabled non-intrusive call + heads up + show expanded

So that all incoming calls had heads up, and pop-up had answer/decline buttons by default, without the need to expand it manually

But there was a problem, that after first call - top part of the screen was becoming inactive and unclickable

After the update (both 3.2.4 and 3.2.5) there is just no heads up for the call, and I just can't find the option to enable. Call appears in the drawer, but no heads up. I've got enabled non-intrusive + heads up + ongoing + show expanded, have tried all possible combination with default settings, but no luck :(

Can you help me with that issue?
[Xposed Framework Modules] aeroman1:
Any fix about 10 seconds disappearing notification on lock screen.
[Xposed Framework Modules] yochananmarqos:
GB does not have lockscreen notifications. If you're referring to the heads up notification, that's how it's supposed to work.
[Xposed Framework Modules] Alex0901:
Here all works fine. Did you make the Option in telephone settings?

Gesendet von meinem Nexus 5 mit Tapatalk
[Xposed Framework Modules] dhalham:
Where did the transparency settings go?
[Xposed Framework Modules] mdamaged:
They disappeared! :laugh:
[Xposed Framework Modules] dhalham:
Seriously?
[Xposed Framework Modules] mdamaged:
Which do you mean? Like status bar?
[Xposed Framework Modules] dhalham:
Yes in launcher.
[Xposed Framework Modules] trjlive:
Translucency settings are where they've always been: Display Tweaks --> Translucent decor
[Xposed Framework Modules] cellardoor04:
Display acting weird

Edit: Nevermind, I found out the settings to one of my apps had changed, and it had nothing to do with GB. My bad!
[Xposed Framework Modules] petrsiri:
I have an issue lately (past 2-3 days) with the notification head up during the incoming call. In some cases I answer the phone and the notification doesn't go away like it should. After I manually clear the notification the part of the screen it covered remains unresponsive until a new notification appears. Anyone else experienced that?
[Xposed Framework Modules] shalevmo:
Hi, can you add speaker button to the call notification?

It would be really nice. Thanks!