Android beta 3.4.99.110 Feedback thread

Moderators: Unholy, hilaroth

Re: Android beta 3.4.99.110 Feedback thread

Postby khaytsus » Fri Oct 12, 2012 4:59 pm

khaytsus wrote:
deeggo wrote:Some thoughts on Waze closing in the background.

Since a couple of weeks I changed my HTC DesireHD for a HTC One X. I found out fast that Waze closes more often in the background on my new device than on my old, although its specs are higher. That has been this way with the current market version and the last 3.4.99 betas. Switching from Waze to the gmail app and reading an e-mail can be enough to trigger this.

With closing in the background I mean that the Waze icon stays in the task bar, but when switching to it, Waze relaunches as if it wasn't running at all.

Apparently, the One X (or Android 4) memory management is more aggressive. I'm never using any task killers.

Here's some info on this subject, that was found during the development of Flitsnav, a Dutch GPS program that was experiencing exactly the same during development. I hope it can help you improve this behaviour, since several users are reporting this.

Waze closing in the background has to do with Android's Out Of Memory (OOM) management.

Some info on OOM_adj (-17 tot +15): The LOWER the value, the MORE important Android thinks the process is.

Foreground Application: -16 to 0
Visible Application: 1
Secondary Server: 2
Hidden Application: 3 to 7
Content Provider: 8 to 14
Empty Application: 15

Maybe you can adjust Waze, so that it sets is own OOM_adj to -17 and repeats that every 5 seconds for instance?

I've been (attempting to) research this more to help provide specific info on how they can help here.... -17 isn't possible without root, and I believe the app must be a system app to do this at all. And in reality, -17 is probably not a good idea.

startForeground was my next idea, but according to Google engineers this is also a bad idea, unless you want your app running 24/7. We don't really want that.

So I dug into what Waze is running as today using an app called AutoKiller Memory Optimizer (no, it's not a task killer, it's pretty cool low level view of OOM levels etc on apps etc), and it seems to always be a "Hidden app" or "Previous app" in Jelly Bean, which puts it somewhere between 7-9 on the OOM kill list. Lower is better. A "Perceptible service" is better, at around 2, but I'm failing to find how to specify that in the app code/manifest... I think if Waze can figure out how to set itself as a "Perceptible service" it'll unlikely get killed unless memory is truly low.

Today, Waze seems to have the same priority as any other background app, and since it's large it'll probably be highest on the list to be killed. I've pondered some of the tweaks/patches that adjust the ICS/JB OOM priority list but I don't want to patch my ROM constantly, and of course that would only help me out. ;) So it'd be nice if the Waze guys can figure out a way to lower their OOM priority while the app is in the background. I'm sure it can be done, but I can't find any details offhand on what to specify in the startup or manifest or such.

I'm going to experiment with making Waze a system app.. Just for giggles, see what happens. I've heard system apps have better (lower in number) priority and are "harder" to kill.


One more post on this subject.. I've talked to the Tasker dev a bit about this, since I found the following..

If I use Autokiller (a task viewer, lets me see some details) for Tasker I see:
OOM 1, OOM group: Visible, Importance: Visible.

Waze is
OOM: 7, OOM Group: Content Provider, Importance: Background

His suggestion is that maybe that Waze is not doing startForerground method in the Service class.

http://developer.android.com/reference/ ... ication%29

But I'd think this was already being done in Waze. Tasker stays at its settings mentioned above, where I've seen Waze as "Foreground" or "Vislble" and OOM:2 then a few seconds later, it's "Content Provider" "Background" and OOM 7-9. Again, I wish I knew anything about actual Android development to make more specific suggestions on what to change.
USA Country Manager
Central Kentucky Area Manager
AT&T LG G2 (AOKP 4.4.4)
Nexus 7 2012 (AOKP 4.4.4)
Samsung Galaxy Note (i717 AT&T; AOKP 4.4.4)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 857
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 41 times
Been thanked: 80 times

Re: Android beta 3.4.99.110 Feedback thread

Postby khaytsus » Mon Oct 15, 2012 5:13 pm

Colonel667 wrote:I have the push notification feature turned off. Yet when I restart my phone, I got Waze running in the background. 1 process and 1 service:

- PushService
- Waze

Now when I actually run Waze and exit it again, none of them will be running in the background afterwards.

(Android 2.3.7)

Interesting, I had noticed that too but didn't pin it down to just reboots, I thought it was just randomly restarting itself.

I wish Waze would tell us exactly what "Push Notifications" means. I haven't yet seen it here. Does that mean users can be contacted directly via the Client? A post somewhere mentioned from the Forum, but I'd have to guess 98% of users aren't in the forums, etc.. It'd be nice to know what it's doing, how it can be used, etc..
USA Country Manager
Central Kentucky Area Manager
AT&T LG G2 (AOKP 4.4.4)
Nexus 7 2012 (AOKP 4.4.4)
Samsung Galaxy Note (i717 AT&T; AOKP 4.4.4)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 857
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 41 times
Been thanked: 80 times

Re: Android beta 3.4.99.110 Feedback thread

Postby khaytsus » Mon Oct 15, 2012 9:40 pm

Waze was crashing on me on launch today, couldn't get it to stop so I had to uninstall it and nuke the SD card files, and lost my favorites!? I thought this stuff was stored on the server? Meh.
USA Country Manager
Central Kentucky Area Manager
AT&T LG G2 (AOKP 4.4.4)
Nexus 7 2012 (AOKP 4.4.4)
Samsung Galaxy Note (i717 AT&T; AOKP 4.4.4)
Image
khaytsus
Beta tester
Beta tester
 
Posts: 857
Joined: Tue Nov 03, 2009 10:43 pm
Location: Lexington, KY
Has thanked: 41 times
Been thanked: 80 times

Re: Android beta 3.4.99.110 Feedback thread

Postby Majumdar » Mon Oct 01, 2012 2:59 am

ryanh85 wrote:Noticed this in last beta, and its still in this one. I am listed as having a level of Royalty Wazer but graph shows me as a Baby Wazer


Same here (noticed in last beta as well)...

Cheers,
Rob
Area Manager - Quebec, Canada

Samsung Galaxy Note 3 | Android 4.4.4 | Waze Beta 3.9.3 | Telus Mobility
Majumdar
 
Posts: 131
Joined: Thu Sep 24, 2009 11:34 pm
Location: Montreal, Quebec, Canada
Has thanked: 9 times
Been thanked: 0 time

Re: Re: Android beta 3.4.99.110 Feedback thread

Postby Majumdar » Thu Oct 18, 2012 1:53 am

Autourdupc wrote:Should we have 3 diffrents icons for traffic jam ?
1 icon with 1 car (means little issue)
1 icon with 2 cars (means important issue)
1 icon with 3 cars (means traffic stopped)
Actually, we have the same icon for both cases

This could be clear to read !
Image1.jpg


Interesting suggestion but I suspect 3.5 is "feature-frozen" given that we are at a. 99 beta and the focus is on squishing bugs in the existing feature set.

Robin
Sent from my GT-I9000M using Tapatalk 2
Area Manager - Quebec, Canada

Samsung Galaxy Note 3 | Android 4.4.4 | Waze Beta 3.9.3 | Telus Mobility
Majumdar
 
Posts: 131
Joined: Thu Sep 24, 2009 11:34 pm
Location: Montreal, Quebec, Canada
Has thanked: 9 times
Been thanked: 0 time

Re: Android beta 3.4.99.110 Feedback thread

Postby markcurrancavan » Mon Oct 08, 2012 10:39 am

Feedback on Waze 3.4.99.110:

1. I drove about 350-500km over the past week with this new beta version. Very stable and had no performance issues. If anything I think the battery consumption was better on this version over the last.
2. On New UI, its nice but I find streets hard to see on the map with the new test theme. Primary Streets and higher are OK.
3. Foursquare integration is my biggest gripe. The checkin option is gone! Could'nt believe this is still gone. Really hoping this get re-added in the next beta version.
4. I still noticed that closing Waze takes ALOT longer now over the 3.2 version on Play. I actually thought it had crashed but its actually just slow closing.
5. On my status page it says I joined Waze 1 ago when I'm almost 2 years on Waze. Something wrong with that data its querying.
6. I noticed that in places of poor internet access that the UI does freeze but if picked up again once the network connection improves. The previous version of Waze did not do this.
7. The new closure button does nothing (this is were the foursquare button used to be). I cannot even select the button.
8. I'm not a FaceBook fan at all so could never see myself using that feature. I do find it strange that waze has chosen to align itself with the Facebook community.

General Ongoing Feedback on Waze:

1. I'm using a xperia s HD running android 4.0.4. When you select the Menu or Report on the Waze UI the resulting window is formatted for a 4.1 inch screen, however this phone has a 4.3 inch screen. The display is actually 16 million colours, 1280 x 720 pixels. The buttons really should be larger on this type of phone and expanded to the full width of the screen on these type of phones. I'd imagine all phones with a larger display than 4.1 inch would have this problem.
2. Navigation: Every time I start Waze the navigation automatically asks me if I want to goto work. I wish there was a way to turn off the auto navigation prompts and that you had to manually activate it when you want or need navigation.
3. My Scoreboard: If you go into My Scoreboard and select My Rank, the new page jumped down a little and hides the Me, Friends and All buttons. Its only a minor UI problem but is kinda annoying as you have to scroll back up to see the buttons again.
markcurrancavan
 
Posts: 12
Joined: Wed Feb 02, 2011 10:40 am
Has thanked: 0 time
Been thanked: 0 time

Re: Android beta 3.4.99.110 Feedback thread

Postby Mike-1323 » Mon Oct 01, 2012 12:24 pm

There's still loss of gps when any popup appear on screen. I've noticed it on thanks notifications and alerts. There's also loss of gps when the nearing destination or approaching destination message is spoken.

Image Image Image
AM - Northern Virginia - Fairfax/Ft. Belvoir
SM - Virginia & CM - USA

Required reading: Quick Start Guide, Best Practices, USA Road Types
Mike-1323
Area Manager
Area Manager
 
Posts: 1026
Joined: Fri Jul 15, 2011 11:06 pm
Location: Lorton, Va
Has thanked: 3 times
Been thanked: 186 times

R: Re: Android beta 3.4.99.110 Feedback thread

Postby mmennella » Thu Oct 04, 2012 10:11 am

khaytsus wrote:
deeggo wrote:Some thoughts on Waze closing in the background.

Since a couple of weeks I changed my HTC DesireHD for a HTC One X. I found out fast that Waze closes more often in the background on my new device than on my old, although its specs are higher. That has been this way with the current market version and the last 3.4.99 betas. Switching from Waze to the gmail app and reading an e-mail can be enough to trigger this.

With closing in the background I mean that the Waze icon stays in the task bar, but when switching to it, Waze relaunches as if it wasn't running at all.

Apparently, the One X (or Android 4) memory management is more aggressive. I'm never using any task killers.

Here's some info on this subject, that was found during the development of Flitsnav, a Dutch GPS program that was experiencing exactly the same during development. I hope it can help you improve this behaviour, since several users are reporting this.

Waze closing in the background has to do with Android's Out Of Memory (OOM) management.

Some info on OOM_adj (-17 tot +15): The LOWER the value, the MORE important Android thinks the process is.

Foreground Application: -16 to 0
Visible Application: 1
Secondary Server: 2
Hidden Application: 3 to 7
Content Provider: 8 to 14
Empty Application: 15

Maybe you can adjust Waze, so that it sets is own OOM_adj to -17 and repeats that every 5 seconds for instance?

I've been (attempting to) research this more to help provide specific info on how they can help here.... -17 isn't possible without root, and I believe the app must be a system app to do this at all. And in reality, -17 is probably not a good idea.

startForeground was my next idea, but according to Google engineers this is also a bad idea, unless you want your app running 24/7. We don't really want that.

So I dug into what Waze is running as today using an app called AutoKiller Memory Optimizer (no, it's not a task killer, it's pretty cool low level view of OOM levels etc on apps etc), and it seems to always be a "Hidden app" or "Previous app" in Jelly Bean, which puts it somewhere between 7-9 on the OOM kill list. Lower is better. A "Perceptible service" is better, at around 2, but I'm failing to find how to specify that in the app code/manifest... I think if Waze can figure out how to set itself as a "Perceptible service" it'll unlikely get killed unless memory is truly low.

Today, Waze seems to have the same priority as any other background app, and since it's large it'll probably be highest on the list to be killed. I've pondered some of the tweaks/patches that adjust the ICS/JB OOM priority list but I don't want to patch my ROM constantly, and of course that would only help me out. ;) So it'd be nice if the Waze guys can figure out a way to lower their OOM priority while the app is in the background. I'm sure it can be done, but I can't find any details offhand on what to specify in the startup or manifest or such.

I'm going to experiment with making Waze a system app.. Just for giggles, see what happens. I've heard system apps have better (lower in number) priority and are "harder" to kill.

+1
Great work
My phone is rooted and when i do long travel i modify nice lebel by hand using terminal.
This post can help to avoid my maniacal practice.


Inviato dal mio GT-S5300 con Tapatalk 2
mmennella
 
Posts: 43
Joined: Wed Jul 18, 2012 5:01 am
Has thanked: 0 time
Been thanked: 1 time

R: Android beta 3.4.99.110 Feedback thread

Postby mmennella » Thu Oct 04, 2012 10:28 am

On my device, samsung galaxy pocket, i have always same font issue from the first v3.0.
I'm embaraced to report always the same issue.
For detail, please refer to old topic "font issue"

Inviato dal mio GT-S5300 con Tapatalk 2
mmennella
 
Posts: 43
Joined: Wed Jul 18, 2012 5:01 am
Has thanked: 0 time
Been thanked: 1 time

R: Re: Android beta 3.4.99.110 Feedback thread

Postby mmennella » Fri Oct 05, 2012 6:42 pm

FreeMan12 wrote:Am I the only one still having text display issues?
CAP2012100511381.png

This has been going on since the first 3.x beta. I've never heard a peep from anyone else about it.

I post yesterday the same issue. You don't see it :grin:

+1

Inviato dal mio GT-S5300 con Tapatalk 2
mmennella
 
Posts: 43
Joined: Wed Jul 18, 2012 5:01 am
Has thanked: 0 time
Been thanked: 1 time

PreviousNext

Return to App Beta Testing

Who is online

Users browsing this forum: No registered users

cron