v1.8.2 - "Blue roof" edition
4 views
Skip to first unread message
Mark Lowne
Jul 16, 2010, 5:09:04 PM7/16/10
to JuiceDefender
spritz aperol here: http://groups.google.com/group/juicedefender/web/JuiceDefender182.apk
- let's see... Apps trigger!! ;)
- new 'training progress' indicator (in 'View known locations') and
other improvements for Location
- UI improvements
- many fixes here and there
See the relevant request thread about the Apps trigger - let's try to
focus on Location and other bugs/problems here.
- let's see... Apps trigger!! ;)
- new 'training progress' indicator (in 'View known locations') and
other improvements for Location
- UI improvements
- many fixes here and there
See the relevant request thread about the Apps trigger - let's try to
focus on Location and other bugs/problems here.
Nitin Philip
Jul 16, 2010, 9:10:55 PM7/16/10
to juiced...@googlegroups.com
JD seems to disabling my wifi with the new apps trigger when Pandora is running.. this happens when the screen is on btw.. more test results later!
Julian
Jul 17, 2010, 5:02:41 AM7/17/10
to JuiceDefender
A truly superb solution!
Works like a charm for last.fm, I will try other apps later.
Found one bug already: Because I didn't look properly initially I had
last.fm set to "leave disabled" in the app list. Even after chaning it
to "leave enabled" the HSDPA was lost once last.fm was in focus. A
reboot solved the problem. I will later try if I can reproduce.
As for the triggers in the app list a minor suggestion: Make "leave
enabled" the first option when clicking on the app and "leave
disabled" the second, as most probably will use it to leave enabled
when chat / stream app is running.
Works like a charm for last.fm, I will try other apps later.
Found one bug already: Because I didn't look properly initially I had
last.fm set to "leave disabled" in the app list. Even after chaning it
to "leave enabled" the HSDPA was lost once last.fm was in focus. A
reboot solved the problem. I will later try if I can reproduce.
As for the triggers in the app list a minor suggestion: Make "leave
enabled" the first option when clicking on the app and "leave
disabled" the second, as most probably will use it to leave enabled
when chat / stream app is running.
vgyliu
Jul 17, 2010, 2:03:57 PM7/17/10
to JuiceDefender
I tried to rerun the setup for my Samsung Moment on 2.1 stock
firmware. when it comes to the connectivity check it failed even tho
before the setup i used the web browser and it works fine.
firmware. when it comes to the connectivity check it failed even tho
before the setup i used the web browser and it works fine.
vgyliu
Jul 18, 2010, 2:38:34 AM7/18/10
to JuiceDefender
i downgraded to 1.80 and then reupgraded to 1.82 and it works fine now
decrypt
Jul 18, 2010, 11:07:00 AM7/18/10
to JuiceDefender
It seems that the service is not starting on boot on CM 6 RC1 on my
nexus one.
nexus one.
Surfinette
Jul 18, 2010, 1:38:34 PM7/18/10
to JuiceDefender
Mark,
I very much like the way you built the Apps feature, it seems to work
very well.... when JD works correctly.
BUT there is a big issue, I find JD to be very unstable (at least with
Froyo MCR v. R5) : Very often, despite JD being activated and supposed
to block data/wifi connections (for instance, when screen button is
off) data/wifi are actually not blocked by JD. So in the notification
bar, I have the JD icon with a red dot (thus confirming JD is supposed
to block connection) and at the same time I have the E or H or wifi
icon on (demonstrating that actually JD is not blocking anything). In
the meantime JD'sLog is not showing anything funny like "data
enabled".
This behavior seems to be very random, sometimes JD works like a
charm, sometimes it doesn't block anything as it should (red dot) and
I haven't found a pattern that would cause this bug...
Surfinette
On 18 juil, 17:07, decrypt <d3cr...@gmail.com> wrote:
> It seems that the service is not starting on boot on CM 6 RC1 on my
> nexus one.
>
> On Jul 17, 5:09 am, Mark Lowne <marklo...@gmail.com> wrote:
>
> > spritz aperol here:http://groups.google.com/group/juicedefender/web/JuiceDefender182.apk
>
> > - let's see... Apps trigger!! ;)
> > - new 'training progress' indicator (in 'View known locations') and
> > other improvements for Location
> > - UI improvements
I very much like the way you built the Apps feature, it seems to work
very well.... when JD works correctly.
BUT there is a big issue, I find JD to be very unstable (at least with
Froyo MCR v. R5) : Very often, despite JD being activated and supposed
to block data/wifi connections (for instance, when screen button is
off) data/wifi are actually not blocked by JD. So in the notification
bar, I have the JD icon with a red dot (thus confirming JD is supposed
to block connection) and at the same time I have the E or H or wifi
icon on (demonstrating that actually JD is not blocking anything). In
the meantime JD'sLog is not showing anything funny like "data
enabled".
This behavior seems to be very random, sometimes JD works like a
charm, sometimes it doesn't block anything as it should (red dot) and
I haven't found a pattern that would cause this bug...
Surfinette
On 18 juil, 17:07, decrypt <d3cr...@gmail.com> wrote:
> It seems that the service is not starting on boot on CM 6 RC1 on my
> nexus one.
>
> On Jul 17, 5:09 am, Mark Lowne <marklo...@gmail.com> wrote:
>
> > spritz aperol here:http://groups.google.com/group/juicedefender/web/JuiceDefender182.apk
>
> > - let's see... Apps trigger!! ;)
> > - new 'training progress' indicator (in 'View known locations') and
> > other improvements for Location
> > - UI improvements
Surfinette
Jul 18, 2010, 1:40:54 PM7/18/10
to JuiceDefender
By the way, I still miss the 3G button (see my comment on the 1.80
topic). I now have to switch manually in the Phone's setting between
3G and 2G (that was not the case with 1.79)
topic). I now have to switch manually in the Phone's setting between
3G and 2G (that was not the case with 1.79)
Smokem_I
Jul 18, 2010, 1:49:07 PM7/18/10
to juiced...@googlegroups.com
Id have to agree JD is not always turning off apn/wifi when screen is off on myTouch Slide either.
On Jul 18, 2010 10:40 AM, "Surfinette" <emmanuelle...@gmail.com> wrote:
By the way, I still miss the 3G button (see my comment on the 1.80
topic). I now have to switch manually in the Phone's setting between
3G and 2G (that was not the case with 1.79)
On 18 juil, 19:38, Surfinette <emmanuelle.braconn...@gmail.com> wrote:
> Mark,
>
> I very much like...
Surfinette
Jul 18, 2010, 2:19:52 PM7/18/10
to JuiceDefender
I believe I have found a pattern for generating the bug I described
previously.
Let's assume you use the phone with JD's screen button ON...
Then suddendly you decide you don't need data/wifi connection anymore
when screen is on. So you go in JD's setting and press the screen
button OFF then leave the setting area using the return button of the
phone (or home button). Then, you'll notice that JD cuts data/wifi
connections BUT just for a few seconds after which data connection
will come back while JD's icon remains red-dot... That's when the BUG
occurs.
To get rid of the bug, you have to go back into JD's setting and then
press the screen button ON then press it OFF again right away (without
leaving the setting section while toggling on then off). Then you can
leave JD's setting area and you're done. The bug is no more there and
data/wifi is cut for good while screen is on....
That's how it seems to solve it so far... ( never had this bug in
previous version (1.79 version and below))
previously.
Let's assume you use the phone with JD's screen button ON...
Then suddendly you decide you don't need data/wifi connection anymore
when screen is on. So you go in JD's setting and press the screen
button OFF then leave the setting area using the return button of the
phone (or home button). Then, you'll notice that JD cuts data/wifi
connections BUT just for a few seconds after which data connection
will come back while JD's icon remains red-dot... That's when the BUG
occurs.
To get rid of the bug, you have to go back into JD's setting and then
press the screen button ON then press it OFF again right away (without
leaving the setting section while toggling on then off). Then you can
leave JD's setting area and you're done. The bug is no more there and
data/wifi is cut for good while screen is on....
That's how it seems to solve it so far... ( never had this bug in
previous version (1.79 version and below))
Surfinette
Jul 18, 2010, 4:15:24 PM7/18/10
to JuiceDefender
I found another bug:
When the screen is ON in JD's settings, then data is always active
when the phone goes to sleep mode. When the screen is in lock
position, I can see JD's icon with the red dot and the Edge icon
together in the notification bar (despite having set ON the "only
after unlock" button).
Only data is activated while screen is in locked/sleep mode.
So for instance, if I have the data, wifi and screen buttons ON in JD,
then I will have wifi active when the phone screen in on (and the JD
notification will show a green dot) and data only active when screen
is locked/sleep and JD notification icon showing a red dot...
Hope I'm clear in describing the bugs I encounter...
Sending you JD's log would be useless, because the Log does not
describe the actual phone's behavior (but what it should do with a bug-
less JD)
I have not found (yet) a way around this second bug :(
I hope you can reproduce these bugs and correct them soon in 1.83
When the screen is ON in JD's settings, then data is always active
when the phone goes to sleep mode. When the screen is in lock
position, I can see JD's icon with the red dot and the Edge icon
together in the notification bar (despite having set ON the "only
after unlock" button).
Only data is activated while screen is in locked/sleep mode.
So for instance, if I have the data, wifi and screen buttons ON in JD,
then I will have wifi active when the phone screen in on (and the JD
notification will show a green dot) and data only active when screen
is locked/sleep and JD notification icon showing a red dot...
Hope I'm clear in describing the bugs I encounter...
Sending you JD's log would be useless, because the Log does not
describe the actual phone's behavior (but what it should do with a bug-
less JD)
I have not found (yet) a way around this second bug :(
I hope you can reproduce these bugs and correct them soon in 1.83
ac75
Jul 19, 2010, 5:55:43 AM7/19/10
to JuiceDefender
I've noticed another strange behaviour bug, it's not a major thing but
worth mentioning all the same.
Clicking on 'Setup' after it has already been run will display a
dialog saying JD is already configured and asking if you want to run
setup again. If you choose 'Cancel' on this dialog it takes you back
to the JD screen but disables everything.
Subsequently, if you hit 'Setup' again you get the full Welcome dialog
which explains about running JD configuration for the first time.
So there seems to be some odd logic in there to determine whether it's
a fresh or existing installation and how the Setup button should
behave in each case.
I would expect JD only to be disabled if the user cancels out of Setup
on first install, and also that they cannot enable JD without
completing Setup. If cancelling out of Setup on an existing and
previously configured install it should just take you back to the
previous state without changing anything.
On a separate note.... Location on v1.8.2 seems to be behaving itself
much better now, I'd gone back to v1.7.6 for a while because of the
noted problems with later builds.
worth mentioning all the same.
Clicking on 'Setup' after it has already been run will display a
dialog saying JD is already configured and asking if you want to run
setup again. If you choose 'Cancel' on this dialog it takes you back
to the JD screen but disables everything.
Subsequently, if you hit 'Setup' again you get the full Welcome dialog
which explains about running JD configuration for the first time.
So there seems to be some odd logic in there to determine whether it's
a fresh or existing installation and how the Setup button should
behave in each case.
I would expect JD only to be disabled if the user cancels out of Setup
on first install, and also that they cannot enable JD without
completing Setup. If cancelling out of Setup on an existing and
previously configured install it should just take you back to the
previous state without changing anything.
On a separate note.... Location on v1.8.2 seems to be behaving itself
much better now, I'd gone back to v1.7.6 for a while because of the
noted problems with later builds.
Surfinette
Jul 19, 2010, 7:59:52 AM7/19/10
to JuiceDefender
I found a bug with the App trigger and the XDA app
I've set the XDA app to green, and effectively when I launch XDA, JD
would activate data/wifi connection. When I surf through the list of
threads in the XDA forum, every thing goes fine and data/wifi remain
activated. However, once I click and enter a specific thread, JD cuts
the data/wifi connection and becomes red-dotted. This causing a FC of
the following process: com.quoord.tapatalkxda.activity. This FC
doesn't kill the whole XDA app, but only the thread I'm attempting to
go to, so after FC, I'm back to the thread menu part of XDA.
It is as if entering a thread in XDA is launching this new service
that JD does not recognize as requiring data connection...
I've set the XDA app to green, and effectively when I launch XDA, JD
would activate data/wifi connection. When I surf through the list of
threads in the XDA forum, every thing goes fine and data/wifi remain
activated. However, once I click and enter a specific thread, JD cuts
the data/wifi connection and becomes red-dotted. This causing a FC of
the following process: com.quoord.tapatalkxda.activity. This FC
doesn't kill the whole XDA app, but only the thread I'm attempting to
go to, so after FC, I'm back to the thread menu part of XDA.
It is as if entering a thread in XDA is launching this new service
that JD does not recognize as requiring data connection...
Matt Passell
Jul 19, 2010, 10:20:40 AM7/19/10
to JuiceDefender
I'm actually having the opposite problem on my unrooted Droid
Incredible from most of the others who've commented here. After
upgrading to 1.8.2, I did the following: turned on the Apps trigger,
hit the "Configure apps" button, and touched the Pandora listing twice
(so that the green arrows are displayed). I assumed (am I wrong?)
that this would tell JD to not turn off my connectivity even when the
screen was off as long as Pandora is running. Here's what actually
happened, I left Pandora playing in the foreground and the screen
eventually turned itself off due to inactivity. Pandora kept playing,
but when it came time to advance to the next song, it was unable to do
so. When I turned the screen back on, it was showing a "looking for
connectivity" (or something like that) dialog. I'm guessing that
while the screen was on, it buffered the current song, but lost
connectivity prior to fetching the next song.
Incredible from most of the others who've commented here. After
upgrading to 1.8.2, I did the following: turned on the Apps trigger,
hit the "Configure apps" button, and touched the Pandora listing twice
(so that the green arrows are displayed). I assumed (am I wrong?)
that this would tell JD to not turn off my connectivity even when the
screen was off as long as Pandora is running. Here's what actually
happened, I left Pandora playing in the foreground and the screen
eventually turned itself off due to inactivity. Pandora kept playing,
but when it came time to advance to the next song, it was unable to do
so. When I turned the screen back on, it was showing a "looking for
connectivity" (or something like that) dialog. I'm guessing that
while the screen was on, it buffered the current song, but lost
connectivity prior to fetching the next song.
Surfinette
Jul 19, 2010, 12:01:15 PM7/19/10
to JuiceDefender
My understanding is that the Apps features is activated only when
screen is on and the app is active or present through a notification
icon. In other words, the Apps button is equivalent to the Screen
button with more refinements (ie Screen button + App filter).
Maybe the Apps feature should be moved upwards above the Data
features, so that Data feature would supersede the Apps feature, ie
would keep data on as long as data is being download (even if screen
is off/standby)?
On 19 juil, 16:20, Matt Passell <mpass...@grovehillsoftware.com>
wrote:
screen is on and the app is active or present through a notification
icon. In other words, the Apps button is equivalent to the Screen
button with more refinements (ie Screen button + App filter).
Maybe the Apps feature should be moved upwards above the Data
features, so that Data feature would supersede the Apps feature, ie
would keep data on as long as data is being download (even if screen
is off/standby)?
On 19 juil, 16:20, Matt Passell <mpass...@grovehillsoftware.com>
wrote:
Surfinette
Jul 19, 2010, 4:04:46 PM7/19/10
to JuiceDefender
@ Mark,
Just starting to test Location with 1.82
I'm still having the "problem" that when I'm away from home (even 1000
m away) wifi is on for about 30 sec right after unlocking the screen,
until JD realise there is no available known network to be connected
to. This is an issue if I'm not constantly keeping the screen awake
(and as I've set the screen to go to sleep mode after 30 sec, I end-up
spending a lot of juice to look for a wifi network that does not
exist...).
Just starting to test Location with 1.82
I'm still having the "problem" that when I'm away from home (even 1000
m away) wifi is on for about 30 sec right after unlocking the screen,
until JD realise there is no available known network to be connected
to. This is an issue if I'm not constantly keeping the screen awake
(and as I've set the screen to go to sleep mode after 30 sec, I end-up
spending a lot of juice to look for a wifi network that does not
exist...).
Mike
Jul 19, 2010, 4:56:07 PM7/19/10
to JuiceDefender
Location appears to work after I cleared my known locations, but my
testing has been somewhat limited and I have only been to 1 wifi
location.
testing has been somewhat limited and I have only been to 1 wifi
location.
Mark Lowne
Jul 20, 2010, 7:19:02 AM7/20/10
to JuiceDefender
@Surfinette: let me know if any of your problems persist with
1.8.3/1.8.4.
About Location: 1000m isn't that far in cell-location terms... but
generally yes, it should be better. What's the UI saying about the
distance? Also: if you manually disable WiFi within that 30 seconds
period, JD should proceed to tweak the saved Location to exclude the
current one; try that and send me a log.
XDA app: interesting finding, I'll have a look!
@ac75: thanks, fixed!
Apps trigger: it works independently from the Screen trigger - but
it's still quite experimental... Keep the feedback coming so I can
iron out the bugs! @Matt: is it fixed in 1.8.3? If not, does
'minimizing' Pandora before turning off the screen make a difference?
1.8.3/1.8.4.
About Location: 1000m isn't that far in cell-location terms... but
generally yes, it should be better. What's the UI saying about the
distance? Also: if you manually disable WiFi within that 30 seconds
period, JD should proceed to tweak the saved Location to exclude the
current one; try that and send me a log.
XDA app: interesting finding, I'll have a look!
@ac75: thanks, fixed!
Apps trigger: it works independently from the Screen trigger - but
it's still quite experimental... Keep the feedback coming so I can
iron out the bugs! @Matt: is it fixed in 1.8.3? If not, does
'minimizing' Pandora before turning off the screen make a difference?
Reply all
Reply to author
Forward
0 new messages