[anon(19759)]

So I'm running the 1443 leak and really want to get rid of the black bar on certain apps. Most important to me is Waze. I use it frequently to let customers and associates know where I am as well as letting my family know when I'll be home. It's accuracy is uncanny....

Anyhow, it's not functional right now because of the black bar - there are certain features I need that are hidden under that bar. To get rid of that, I understand I will need to sideload the new runtime 4.2.2, but that means it's locked and Waze may not work.

1. Will the newer leaks like 1725, 1743 and 1761 allow me to get rid of the black bar but keep unlocked runtime so I don't have to use debug tokens?

2. Is the only way to do this to use the locked runtime with debug tokens?

thanks in advance!

[thurask]

Any runtime from 1725 and higher will allow you to hide the back bar. However, all of these runtimes are locked.

So the choice is no back bar or no debug tokens.

[Gearheadaddy]

Why not use Debug Tokens? It's not that difficult. Use "Android Pak". Link to it is available in these forums.

Trusted Member Genius

[anon(19759)]

Why not use Debug Tokens? It's not that difficult. Use "Android Pak". Link to it is available in these forums.

Trusted Member Genius

I'll read up on it....thanks!

[Cranky]

Swipe down from top of screen to hide the bar.

If we lose the Right to Bear Arms, who will protect your Right to Free Speech?

[anon(19759)]

Swipe down from top of screen to hide the bar.

If we lose the Right to Bear Arms, who will protect your Right to Free Speech?

Nope, won't work on 1443/unlocked runtime. Now that I've read up on it, as thurask says above, must have higher than 1443 with locked 4.2.2 runtime and debug tokens.

[toobs623]

Maybe it's a Q specific thing but waze works fine for me with Z10STL100-3/10.2.0.1761 stock runtime.

[anon(19759)]

Maybe it's a Q specific thing but waze works fine for me with Z10STL100-3/10.2.0.1761 stock runtime.

Yes, it does work for me right now on my q10 - the issue is that the persistent back bar is covering up some buttons at the bottom of the waze screen and I can't get to it. The primary reason I use Waze is to let my wife know when I'm going to be home (I have a wicked long commute) and the back bar on the Q10 is covering up the buttons to choose the type of messaging to use when sending her my location and approximate arrival time. The choices are sms, email, fb and twitter I think, but I can't even see them right now on the q10 and it doesn't scroll. If I can get rid of that back bar, I'll be able to send my waze tracking again. The nav functions work fine - I just need more screen to use it fully.

[Gearheadaddy]

Study up on the debug token. It's really not that hard to do... you can do it.

Trusted Member Genius

[thurask]

Yes, it does work for me right now on my q10 - the issue is that the persistent back bar is covering up some buttons at the bottom of the waze screen and I can't get to it. The primary reason I use Waze is to let my wife know when I'm going to be home (I have a wicked long commute) and the back bar on the Q10 is covering up the buttons to choose the type of messaging to use when sending her my location and approximate arrival time. The choices are sms, email, fb and twitter I think, but I can't even see them right now on the q10 and it doesn't scroll. If I can get rid of that back bar, I'll be able to send my waze tracking again. The nav functions work fine - I just need more screen to use it fully.

Try extracting the bar file (that works on your Q already) with 7zip/IZArc/etc, loading the new runtime and tokening the APK that pops out.

Posted via CB10

[anon(19759)]

Try extracting the bar file (that works on your Q already) with 7zip/IZArc/etc, loading the new runtime and tokening the APK that pops out.

Posted via CB10

Yep, that's exactly what I'm going to do, right after I upgrade my OS above the current 1443 I'm running, which I've read will not work with the 4.2.2 runtime and debug. Is that correct or can I just leave 1443? It's really proven to be stable for me, which I absolutely must have as this is my daily driver for work.

[thurask]

Yep, that's exactly what I'm going to do, right after I upgrade my OS above the current 1443 I'm running, which I've read will not work with the 4.2.2 runtime and debug. Is that correct or can I just leave 1443? It's really proven to be stable for me, which I absolutely must have as this is my daily driver for work.

I don't think there should be any problems loading the latest Android runtime (10.2.0.123 from 1725, 10.2.0.125 from 1743/1761) over 1443. Load the bars, reboot, load your debugged Waze bar and see what happens.

[anon(19759)]

Finally sat down to deal with debug tokens and now Waze runs perfectly and I have enough screen with the permabar gone that I can use the extra functions I wanted. Wish they would just make a native bb10 version, but I don't see that happening anytime soon. Got Waze, candy crush and a few others running now without the bar, on 1443 and running great.