Page 1 of 3

Waze 3.6: black screen after reporting

Posted: Sun Mar 03, 2013 1:05 pm
by bugjargal
Hi all,

Since yesterday, I'm facing an issue that makes waze almost unusable.

First of, here's the context:
-Waze 3.6
-ROM Omega v44.1 (Android 4.2.1)
-Samsung Galaxy S3 (i9300)

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
-Deactivated autozoom in waze settings (who knows... :roll: )

Did anybody see this before?

Thanks ;)
Oh. And by the way: great software guys! Thanks for all the effort and thanks to all wazers...

Re: Waze 3.6: black screen after reporting

Posted: Sun Mar 03, 2013 2:38 pm
by aigarslv
I'm using Waze on Stock S3 - did not see this problem. Also Cyanogen mod seems to work fine. Due to massively tweaked system in Omega, I think this problem is limited to Omega ROM.

Re: Waze 3.6: black screen after reporting

Posted: Sun Mar 03, 2013 3:46 pm
by bugjargal
This is also what I fear/suspect.
I reverted back to two waze beta releases just to be sure, but no luck.

I'll wait for the next omega release and see...

Thanks anyway ;-)

Envoyé depuis mon GT-I9300 avec Tapatalk

Re: Waze 3.6: black screen after reporting

Posted: Tue Mar 05, 2013 4:56 pm
by bugjargal
Ok. I feel less alone ;)

I reverted back to Omega v43 (Android 4.1.2) and everything is working as it should.

Re: Waze 3.6: black screen after reporting

Posted: Tue Mar 05, 2013 7:41 pm
by bugjargal
This is how I understand it.

As aigarslv mentioned, Omega roms are heavily tweaked. And v44.1 is based on a leaked 4.2.1.
So I'll give it a new try when it will be available based on an official from Samsung.

Re: Waze 3.6: black screen after reporting

Posted: Sun Apr 07, 2013 10:22 am
by bugjargal
Did anybody have a chance to test it against the latest Omega releases (44.2 or 44.3)?

I'm happy with this ROM and would like to stick with it for now. But I did not find time to go through the wipe data process again to be able to test with these versions...

Thanks

Re: Waze 3.6: black screen after reporting

Posted: Tue Jun 04, 2013 5:52 pm
by Chewee91
Same for me on S4 (I9505), waiting for a new update to fix this.... :(

Re: Waze 3.6: black screen after reporting

Posted: Fri Jun 07, 2013 1:03 pm
by Chewee91
Not a real solution but....

After flashing a wrong zip fil through my recovery, i get bootloop so i had too flash back a firmware (MDM on S4 I9505), then do a factory reset before restore my data with titanium and....

Waze it's working again, no black screen at all.... I have not find the real origin for this bug, but now all works fine (independantly of app update)....

Re: Waze 3.6: black screen after reporting

Posted: Tue Mar 05, 2013 8:11 pm
by DonQuijot
[quote="bugjargal"]Hi all,

Since yesterday, I'm facing an issue that makes waze almost unusable.

First of, here's the context:
-Waze 3.6
-ROM Omega v44.1 (Android 4.2.1)
-Samsung Galaxy S3 (i9300)

Hi, I've got the same on Omega v44.1. So i change it to RootBox 4.2.2 and this gone. )

Re: Waze 3.6: black screen after reporting

Posted: Sat Jun 22, 2013 4:24 am
by DrBlast33
I have the same issue with my S4, stock rooted/deodexed. The only way to fix is to use Waze in multimode mode.