Database Develop

Waze app not working properly on [ROM][4.1.2 JB]Ultimate N7000 XXLSZ JellyBean 4.1.2

kudos for this great rom as I am using it with no problem until i installed Waze.
My issue:
Waze seems to work ok until I click the 'Report' button located bottom right. Whether I go on and report something or simply go back without reporting anything, I end up with a black screen with only the two buttons available. No more map display.
If I tap one of the two buttons, I can see the map (and all wazers or events) displayed in the background of the menu that pops up. But as soon as I get out of the menu, I'm back on that black screen.
Note that only the 'Report' button triggers this problem, if I tap the main button bottom left, I can go back to the map with no pb.
Workaround: Not really. Only exiting the app restores the map.
I also noticed that if I stay on that black screen, my device will shutdown its screen (Waze option to prevent this does not work). As long as I'm seeing the map, it behaves as expected on that topic.
What I tried to fix this (with no luck):
-Removed Waze after wipping data/cache
-Removed remaining files manuallly
-Went to recovery and wiped cache/dalvik +fix permissions
and what does rootbox do? will rootbox fix this?

Up !
Same for me on my international I9505... App new release doesn't fix it... Any chance from xda's brains to find a clue ?
The same version works just fine on my i9300 on 4.1.2...
I have seen this issue is related to hd screens...

jay185 said:
My issue:
Waze seems to work ok until I click the 'Report' button located bottom right. Whether I go on and report something or simply go back without reporting anything, I end up with a black screen with only the two buttons available. No more map display.
Click to expand...
Click to collapse
I had the same black screen problem when using the report feature. I finally figured out what was causing the problem on my phone. I am using a rooted S4 with multi window manager. The problem occurs when I enable Waze for multi window mode. When disabled, Waze works perfectly.

kentonn said:
I had the same black screen problem when using the report feature. I finally figured out what was causing the problem on my phone. I am using a rooted S4 with multi window manager. The problem occurs when I enable Waze for multi window mode. When disabled, Waze works perfectly.
Click to expand...
Click to collapse
did use the native multi window manager and rebooted, failed
used the multi window manager from app store and rebooted, failed.
same result. i removed the waze app from doing multi window.

Try open multi window waze with other app, for me I open whatapp and then waze
Sent from my GT-N7000 using Tapatalk 2

OnePlus One: Xposed disables double tap status bar to sleep

When installing Xposed on the OnePlus One, the double tap status bar to sleep the screen feature is completely broken. Uninstalling the framework does not fix it.
Hope you can fix this issue in a future version.

donalgodon said:
Uninstalling the framework does not fix it.
Click to expand...
Click to collapse
Uninstalling the framework reverts all the changes Xposed made. If the problem still occurs after rebooting, then the framework didn't cause it.

GermainZ said:
Uninstalling the framework reverts all the changes Xposed made. If the problem still occurs after rebooting, then the framework didn't cause it.
Click to expand...
Click to collapse
I thought that was true also, but yesterday, I did three clean, full-wipe flashes, and the only A/B changes I made was to install and uninstall the Xposed Framework.
Before installation, tapping the status bar sleeps the screen.
After installation and/or removal, it does not.
Any idea why?

Xposed problems
donalgodon said:
I thought that was true also, but yesterday, I did three clean, full-wipe flashes, and the only A/B changes I made was to install and uninstall the Xposed Framework.
Before installation, tapping the status bar sleeps the screen.
After installation and/or removal, it does not.
Any idea why?
Click to expand...
Click to collapse
And the answer is? Anybody? This is a OnePlus One COS 12.1?

bmaz121 said:
And the answer is? Anybody? This is a OnePlus One COS 12.1?
Click to expand...
Click to collapse
Works fine for me - same COS 12.1 - only have two modules though - so maybe disable all modules first and then retry.
TBH - I've never used that function - until you mentioned it - as I use the power button to lock.

That does not answer the question. It is not about it working to lock but what it does when it locks. The Notification screen should not be displaying when Unlock. On the first tap of the double tap the Notification screen or Status screen drops down before it goes to sleep. That should only happen when I swipe down not tap once. Why don't people read the post before they answer it?

You've got confused mate! There's no mention of 'what it does when it locks' as you say. The thread is about the double tap on status bar not working after installing xposed.
No worries - it can be a little confusing doing all that reading.

Xposed modules on G900A_OF2 - 5.0

Which modules work on S5 Lollipop?
Wanam Xposed used to work on the the older OS KitKat but hardly works on Lollipop.
Really looking to get rid of the startup and unplug usd notifications and have the torch active with a button..

davidalindsey said:
Which modules work on S5 Lollipop?
Wanam Xposed used to work on the the older OS KitKat but hardly works on Lollipop.
Really looking to get rid of the startup and unplug usd notifications and have the torch active with a button..
Click to expand...
Click to collapse
Xposed g-touchwiz works for me, got rid of the popups. Some parts of gravity box (lp) work. Was able to change battery icon and long back to kill. Torch on gravity box caused errors though, haven't found something for that.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

I found a build that works:
Wanam Xposed for Lollipop (Download link at bottom of page)
Post #5296
Main thread

Can't unlock from lockscreen

Hi there,
I'm facing a weird issue here. I can't seem to be able to unlock my phone, when I do the icons show but the widgets and the nav bar don't. Also the wallpaper turned in to a black screen.
This happened to before although I can't seem to remember how did I fix this. the phone works, I can access the homescreen and everything else if for example I pull down the settings and click on settings or something, basically anything that makes me skip the lockscreen unlock.
The phone is rooted, running 4.4.4 latest stock with xposed and @serajr 's xposed for kk.
vid:
https://www.youtube.com/watch?v=_MT1bfh6A_A

Try disabling Xposed, video reminds me of constant crash of systemUI which I had after enabling some mods in Xposed.

_mysiak_ said:
Try disabling Xposed, video reminds me of constant crash of systemUI which I had after enabling some mods in Xposed.
Click to expand...
Click to collapse
I've tried messing around with disabling and re-enabling the xposed modules, but no luck there.
I ended up just flashing in my backup again. So far so good, had the phone running for almost a week now.

[SOLVED] Why does my phone not unlock on 47.1.A.16.20 with Xposed?

[FOR REFERENCE ONLY]
Problem solved!
The confounding variable was NOT Xposed Framework, but conena's Gesture Control app that was set up to use Immersive Mode to hide the navigation bar. And according to this post that I landed on purely by chance, if you don't exempt the Lockscreen Settings app, it causes all these problems.
Note that this problem has nothing to do with the app, it's the Immersive Mode setting to blame, on which any setting change at all will cause these same problems (to be fair, conena's app does preemptively discourage this)
Solution
Use a Substratum overlay to hide the navbar instead; do NOT use GravityBox to do that by setting navbar height to 0, or qemu.hw.mainkeys=1 in build.prop (which doesn't work, BTW). Next, backup your gesture bar data and wipe the data of the app, then restore the bar data – just don't fiddle with that Immersive Mode setting again!
Well, some explanation is in order because it wouldn't make for a great thread title:
I am running the last stock Oreo build on this G8441, which is 47.1.A.12.20, for the primary reason of being able to use rovo89's Xposed Framework because the original XPrivacy module that's vitally important to me does not run on any of the EdXposeds or LSPoseds.
Using systemless Xposed with the latest Magisk version (and older ones too, nothing changes) I find that if I were to set a lockscreen to anything other than "None" and reboot, I will have times where I simply can't see the display when pressing the power button -- but weirdly enough the touchscreen still keeps taking touch input! The only way around is to remove the lockscreen, reboot, then set your locking method and try not to have it restart for any reason.
It's quite obvious that systemless Xposed is causing this problem (Xposed can't be installed normally on this firmware version) because this problem can be reproduced even without any modules active. But I'm at a complete loss as to what's actually causing this lockscreen interference, because I've tried taking system logs with and without Xposed and there's simply nothing at all different except it taking insanely long times for the display to activate upon unlock (but the touch input working just fine for some reason?) and there's a small, dim red LED near the proximity sensor that stays stuck as long as the display is.
Please help me, I'm absolutely out of ideas -- and no, I can't upgrade to Pie, I have to stay on Oreo for the sake of the XPrivacy module.

So it seems like 47.1.A.12.75 is the last problem-free Oreo version for normal Xposed Framework, and I wouldn't mind using that, if it weren't for the fact that there doesn't seem to be any VoLTE-activating SIN file for India for it below 47.1.A.12.270. There's a 2G phaseout in progress with the largest carrier and it's only a matter of time before there'll be no fallback network and I'll have to have VoLTE at any cost.