v1.8.5 - fixes
24 views
Skip to first unread message
Mark Lowne
Jul 21, 2010, 2:35:13 AM7/21/10
to JuiceDefender
http://juicedefender.googlegroups.com/web/JuiceDefender185.apk
Special edition for Surfinette! :)
- Setup should now detect correctly when CPU throttling doesn't work
(please confirm!)
- 3G/2G toggling is back for non-CM ROMs
Could it be that all the 'weirdness' problems (that apparently
ultimately all derive from the settings not being stored) are caused
by the new Froyo 'apk update' thingy, whereas sometimes apks are
cached in ways unheard of?
Does rebooting right after updating help? Other ideas?
Special edition for Surfinette! :)
- Setup should now detect correctly when CPU throttling doesn't work
(please confirm!)
- 3G/2G toggling is back for non-CM ROMs
Could it be that all the 'weirdness' problems (that apparently
ultimately all derive from the settings not being stored) are caused
by the new Froyo 'apk update' thingy, whereas sometimes apks are
cached in ways unheard of?
Does rebooting right after updating help? Other ideas?
Mark Lowne
Jul 21, 2010, 2:48:23 AM7/21/10
to JuiceDefender
Also: Superuser.apk is still causing serious trouble; more often than
not it stalls, causing Application Not Responding on apps requiring
su. When this happens with Broadcast Receivers, it will in turn
completely crash the app (receivers have a hard time limit to perform
their stuff; if they fail to complete within the allotted timeframe,
they are mercilessly destroyed by Android).
I confirmed that this often crashes JD on boot (you won't see the FC
dialog on screen, the only way to see this happening is via logcat),
as well as Titanium Backup on app install/remove, as well as a number
of other Broadcast-Receiver-powered apps.
Moreover, while Services don't get similarly killed, this sometimes
causes JD's service to react to events with an unnecessary delay of
several seconds.
not it stalls, causing Application Not Responding on apps requiring
su. When this happens with Broadcast Receivers, it will in turn
completely crash the app (receivers have a hard time limit to perform
their stuff; if they fail to complete within the allotted timeframe,
they are mercilessly destroyed by Android).
I confirmed that this often crashes JD on boot (you won't see the FC
dialog on screen, the only way to see this happening is via logcat),
as well as Titanium Backup on app install/remove, as well as a number
of other Broadcast-Receiver-powered apps.
Moreover, while Services don't get similarly killed, this sometimes
causes JD's service to react to events with an unnecessary delay of
several seconds.
Surfinette
Jul 21, 2010, 4:50:42 AM7/21/10
to JuiceDefender
Great Mark, you rock! I have my 3G button back and the CPU button is
gone :)
Well, that's for the good news, but the bad new is ... 1.85 is very
buggy :(
1) I'm back with the very same issue I had with 1.82 that when JD
should disable data/wifi, wifi is disabled, the JD icon is red-dotted
but data (2G) remains active. A reboot of the phone does not solve
that (like it did with 1.84) and the trick of toggling the screen
button does work only for a short period of time.
2) With the 3G and Data buttons ON and with "prefer wifi" ON (and
Screen OFF and Apps ON), I wonder why JD toggles the phone's state
from 2G to 3G when wifi is activated and working (not toggling to 3G
would save some action and would avoid cutting the cell radio for a
split second, both ways).
3) Even with the 3G button OFF and the phone state manually set to 2G
only, I have JD often toggling data to 3G (phone state turned to "2G/
3G auto")
4) With Screen Button OFF and Apps button ON, data/wifi connection is
not disabled when screen goes to sleep mode. That's an issue because,
for instance if you use a browser to surf on the web, but suddenly
stop for an hour to use your phone, then you'll end-up using one hour
of data connection for nothing. I understand that cutting data while
screen is in sleep mode could be an issue for music streaming apps
(when you don't need the screen to be on while downloading the stream)
but this could maybe be solved by allowing the Traffic button to be ON
when the Apps button is ON but Screen button OFF. Or you could set a
3rd item to the App configuration: Red always disabled data, Green
always enable data (even with screen off) and Yellow enable data only
when screen is active)
Sorry, for being so demanding... JD is the greatest system app ever
for Android, so I want it to be sooooooo perfect :)
gone :)
Well, that's for the good news, but the bad new is ... 1.85 is very
buggy :(
1) I'm back with the very same issue I had with 1.82 that when JD
should disable data/wifi, wifi is disabled, the JD icon is red-dotted
but data (2G) remains active. A reboot of the phone does not solve
that (like it did with 1.84) and the trick of toggling the screen
button does work only for a short period of time.
2) With the 3G and Data buttons ON and with "prefer wifi" ON (and
Screen OFF and Apps ON), I wonder why JD toggles the phone's state
from 2G to 3G when wifi is activated and working (not toggling to 3G
would save some action and would avoid cutting the cell radio for a
split second, both ways).
3) Even with the 3G button OFF and the phone state manually set to 2G
only, I have JD often toggling data to 3G (phone state turned to "2G/
3G auto")
4) With Screen Button OFF and Apps button ON, data/wifi connection is
not disabled when screen goes to sleep mode. That's an issue because,
for instance if you use a browser to surf on the web, but suddenly
stop for an hour to use your phone, then you'll end-up using one hour
of data connection for nothing. I understand that cutting data while
screen is in sleep mode could be an issue for music streaming apps
(when you don't need the screen to be on while downloading the stream)
but this could maybe be solved by allowing the Traffic button to be ON
when the Apps button is ON but Screen button OFF. Or you could set a
3rd item to the App configuration: Red always disabled data, Green
always enable data (even with screen off) and Yellow enable data only
when screen is active)
Sorry, for being so demanding... JD is the greatest system app ever
for Android, so I want it to be sooooooo perfect :)
Mark Lowne
Jul 21, 2010, 5:11:42 AM7/21/10
to JuiceDefender
2) agreed - 3G will be overhauled with this and other improvements
3) that's a known problem (JD often can't figure out the current state
of the '2g only' system preference) - it'll require some serious
hacking to be fixed, but it's not really a priority now
4) agreed again - I'll think of a way to handle that without the need
for a tri-state app configuration, if possible. In the meanwhile,
there's an easy workaround: just press 'home' before putting the phone
to sleep ;)
and now, the most important:
1) just to make sure, repro the problem (will require disabling the
Screen trigger) and send the log (when JD shows 'data disabled' while
it's actually on). The problem *might* in the notification display, as
opposed to JD's internals :)
Also: try to see if the '2g only' system preference and/or having '3G'
enabled in JD have anything to do with the problem.
On Jul 21, 10:50 am, Surfinette <emmanuelle.braconn...@gmail.com>
wrote:
3) that's a known problem (JD often can't figure out the current state
of the '2g only' system preference) - it'll require some serious
hacking to be fixed, but it's not really a priority now
4) agreed again - I'll think of a way to handle that without the need
for a tri-state app configuration, if possible. In the meanwhile,
there's an easy workaround: just press 'home' before putting the phone
to sleep ;)
and now, the most important:
1) just to make sure, repro the problem (will require disabling the
Screen trigger) and send the log (when JD shows 'data disabled' while
it's actually on). The problem *might* in the notification display, as
opposed to JD's internals :)
Also: try to see if the '2g only' system preference and/or having '3G'
enabled in JD have anything to do with the problem.
On Jul 21, 10:50 am, Surfinette <emmanuelle.braconn...@gmail.com>
wrote:
Apostol Apostolov
Jul 21, 2010, 8:32:34 AM7/21/10
to juiced...@googlegroups.com
Installing AOSP fails on rooted HTC Desire. What is AOSP used for? It wasn't attempted to be installed on previous versions, when I had a unrooted phone.
Regards,
Apostol Georgiev Apostolov - RaynerApe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* UPDATED! Mobile +359 (0)894 369 881
* SKYPE: apoapostolov -=<>=- GTALK: rayn...@gmail.com
* TWITTER: http://twitter.com/apoapostolov (activity: low, 5-8 per day)
* FACEBOOK:http://www.facebook.com/#!/apostolapostolov (activity: high, 10-25 per day, IT-oriented)
* LINKEDIN: http://bg.linkedin.com/in/apostolapostolov
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Masthead Studios - Lead Game Designer. We play Earthrise. (http://www.play-earthrise.com/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Computer Bulgaria - Author. Hardware, Mobiles and Top Games (http://www.newteck.bg/computer/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Regards,
Apostol Georgiev Apostolov - RaynerApe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* UPDATED! Mobile +359 (0)894 369 881
* SKYPE: apoapostolov -=<>=- GTALK: rayn...@gmail.com
* TWITTER: http://twitter.com/apoapostolov (activity: low, 5-8 per day)
* FACEBOOK:http://www.facebook.com/#!/apostolapostolov (activity: high, 10-25 per day, IT-oriented)
* LINKEDIN: http://bg.linkedin.com/in/apostolapostolov
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Masthead Studios - Lead Game Designer. We play Earthrise. (http://www.play-earthrise.com/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Computer Bulgaria - Author. Hardware, Mobiles and Top Games (http://www.newteck.bg/computer/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Stefano Z.
Jul 21, 2010, 8:42:23 AM7/21/10
to juiced...@googlegroups.com
also here failed
"AOSP helper couldn't be installed correctly.
setup paused while it was running! hope it's just for permission..."
"AOSP helper couldn't be installed correctly.
setup paused while it was running! hope it's just for permission..."
Surfinette
Jul 21, 2010, 8:49:24 AM7/21/10
to JuiceDefender
Regarding problem # 1, I stepped back to version 1.84 and the problem
came back with 1.84 while I thought I had solved it yesterday by
rebooting the phone.
Maybe I did not test thoroughly enough yesterday.
The problem going on exactly is this: Whenever the phone must move
from a situation where data (or wifi) is enabled (JD icon green-dot)
to a situation where data must be disabled (data red-dot), then
initially data or wifi is cut but after 1 or 2 seconds data is re-
enabled while the JD icon remain red-dot (the red-dot is normal
because in theory the phone is in a state where data should be
disabled). This is not a matter of notification display, because in
such a state, I can still surf the web (for instance with a navigator
that has not been set to "green" in the App config and assuming the
Screen button is off). Even if wifi is available in the area (and was
enabled in the previous state were data wifi were enabled with JD icon
green-dot), ONLY data is enabled when it shouldn't with JD icon red-
dot. So the abnormal situation is always JD-red-dot + data but never
JD-red-dot + wifi
To restore a normal situation (ie JD red-dot without data activated)
I need to go in JD's setting windows and toggle back and forth the
Screen button
I'll send you a log as soon as I can
came back with 1.84 while I thought I had solved it yesterday by
rebooting the phone.
Maybe I did not test thoroughly enough yesterday.
The problem going on exactly is this: Whenever the phone must move
from a situation where data (or wifi) is enabled (JD icon green-dot)
to a situation where data must be disabled (data red-dot), then
initially data or wifi is cut but after 1 or 2 seconds data is re-
enabled while the JD icon remain red-dot (the red-dot is normal
because in theory the phone is in a state where data should be
disabled). This is not a matter of notification display, because in
such a state, I can still surf the web (for instance with a navigator
that has not been set to "green" in the App config and assuming the
Screen button is off). Even if wifi is available in the area (and was
enabled in the previous state were data wifi were enabled with JD icon
green-dot), ONLY data is enabled when it shouldn't with JD icon red-
dot. So the abnormal situation is always JD-red-dot + data but never
JD-red-dot + wifi
To restore a normal situation (ie JD red-dot without data activated)
I need to go in JD's setting windows and toggle back and forth the
Screen button
I'll send you a log as soon as I can
Mark Lowne
Jul 21, 2010, 9:25:37 AM7/21/10
to juicedefender
Agh! Now I want to remove the AOSP helper again :(
Well, I'll remove the various warnings at least. Nothing to worry
about: the AOSP helper is used to toggle between 3g and 2g only. It
*only* works on CyanogenMod and Surfinette's ROM apparently, but since
there's no way (that I know of) of knowing beforehand if that's the
case, Setup will try to install it on all rooted phones - once it
confirms it doesn't work, it'll uninstall it immediately.
Well, I'll remove the various warnings at least. Nothing to worry
about: the AOSP helper is used to toggle between 3g and 2g only. It
*only* works on CyanogenMod and Surfinette's ROM apparently, but since
there's no way (that I know of) of knowing beforehand if that's the
case, Setup will try to install it on all rooted phones - once it
confirms it doesn't work, it'll uninstall it immediately.
@Surfinette: ok, you can see for yourself if the
red-dot-but-data-enabled is a bug in JD's logic: just check the log
(either will do) after it happens and see what's the latest (most
recent) entry about data. If there's a 'Data enabled', then some
trigger is re-enabling data but JD fails to update the notification
accordingly. If, on the other hand, there's just 'Data disabled', then
*something else* (cue creepy, haunted-mansion noises) is re-enabling
data.
I'm now convinced that it must be the latter: try to remember if this
problem was introduced with some JD build (1.8.2 or something), or if
it really was your updating to Froyo, as I think it is (you can always
double-check by installing some old version, say 1.7.9, on your Froyo
ROM). If so, then your special ROM doesn't like JD (unless you have
some other weird apps that could be causing this, but that seems
unlikely).
Apostol Apostolov
Jul 21, 2010, 9:32:27 AM7/21/10
to juiced...@googlegroups.com
Why not implement a question dialog before attempting to install AOSP? Are you using <Put applicable ROMs here>. If not, don;'t try to install it. People usually freak out if something breaks during setup/install/any important process.
Regards,
Apostol Georgiev Apostolov - RaynerApe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* UPDATED! Mobile +359 (0)894 369 881
* SKYPE: apoapostolov -=<>=- GTALK: rayn...@gmail.com
* TWITTER: http://twitter.com/apoapostolov (activity: low, 5-8 per day)
* FACEBOOK:http://www.facebook.com/#!/apostolapostolov (activity: high, 10-25 per day, IT-oriented)
* LINKEDIN: http://bg.linkedin.com/in/apostolapostolov
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Masthead Studios - Lead Game Designer. We play Earthrise. (http://www.play-earthrise.com/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Computer Bulgaria - Author. Hardware, Mobiles and Top Games (http://www.newteck.bg/computer/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Regards,
Apostol Georgiev Apostolov - RaynerApe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* UPDATED! Mobile +359 (0)894 369 881
* SKYPE: apoapostolov -=<>=- GTALK: rayn...@gmail.com
* TWITTER: http://twitter.com/apoapostolov (activity: low, 5-8 per day)
* FACEBOOK:http://www.facebook.com/#!/apostolapostolov (activity: high, 10-25 per day, IT-oriented)
* LINKEDIN: http://bg.linkedin.com/in/apostolapostolov
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Masthead Studios - Lead Game Designer. We play Earthrise. (http://www.play-earthrise.com/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
* Computer Bulgaria - Author. Hardware, Mobiles and Top Games (http://www.newteck.bg/computer/)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<->-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Surfinette
Jul 21, 2010, 2:52:51 PM7/21/10
to JuiceDefender
@Mark
I believe I may have found the beginning of an explanation for bug # 1
You said the words "cue creepy, haunted-mansion noises" about this
bug,.... well you are right to the point, its even worst that creepy,
truly crazy haunty:
It seems that bug # 1 only occur when I'm HOME !!!!
You remember when I said yesterday I tested JD 1.84 and I didn't have
the bug, and this morning I had the bug with JD 1.85 and when I step
back to 1.84 I had the bug again this time with 1.84 !!!! Well
yesterday I only did the test while I was in the office. This morning,
when I had the bug I was home.
This afternoon I re-did the test in various ways with 1.84 and 1.85
while I was in the tube and walking in the street far from home and I
did not have the bug (with neither 1.85 or 1.84).
Now I'm back Home, and I have the bug again.
Also, remember last week when I started to complain about this bug
(see discussion about JD 1.82), this was driving me crazy, and at some
point I was mentioning that the bug was occurring at RANDOM. Well last
week I was not home but on vacation at my parents' home where there is
wifi connection. And I kept testing JD in and out of their house... In
their house my phone was connected to their wifi network, at the beach
I had no wifi connection ;-) hence the reason for the "random"
occurrence of the bug.
My conclusion is that the bug occur only when I'm connected to wifi,
in other word when there is a "choice" of functioning wifi or data
connection for the phone.
This is giving me new ideas to try to understand this bug and do more
test.
As a side note, I want to flag that this afternoon, during my testing
session of 1.85 and 1.84, I tried to install 1.85 after uninstalling
1.84 and JD would keep FC has soon as I would hit the Activate button
in the setting page. The only way around this issue was to uninstall
both JD AND AOSP helper before installing the new version of JD. After
this very fresh install, everything went fine...
Lastly, you say "If my special ROM doesn't like JD"... But my ROM is
not that special! Modaco's Rom by Paul are very popular, as close as
possible to stock roms and usually very stable... (and, from what I
read, JD also seem pretty popular among people discussing on my
"special" Rom's thread ;) so I hope getting rid of this bug will not
only serve me...
On 21 juil, 15:25, Mark Lowne <marklo...@gmail.com> wrote:
> Agh! Now I want to remove the AOSP helper again :(
> Well, I'll remove the various warnings at least. Nothing to worry
> about: the AOSP helper is used to toggle between 3g and 2g only. It
> *only* works on CyanogenMod and Surfinette's ROM apparently, but since
> there's no way (that I know of) of knowing beforehand if that's the
> case, Setup will try to install it on all rooted phones - once it
> confirms it doesn't work, it'll uninstall it immediately.
>
> @Surfinette: ok, you can see for yourself if the
> red-dot-but-data-enabled is a bug in JD's logic: just check the log
> (either will do) after it happens and see what's the latest (most
> recent) entry about data. If there's a 'Data enabled', then some
> trigger is re-enabling data but JD fails to update the notification
> accordingly. If, on the other hand, there's just 'Data disabled', then
> *something else* (cue creepy, haunted-mansion noises) is re-enabling
> data.
> I'm now convinced that it must be the latter: try to remember if this
> problem was introduced with some JD build (1.8.2 or something), or if
> it really was your updating to Froyo, as I think it is (you can always
> double-check by installing some old version, say 1.7.9, on your Froyo
> ROM). If so, then your special ROM doesn't like JD (unless you have
> some other weird apps that could be causing this, but that seems
> unlikely).
>
> On Wed, Jul 21, 2010 at 2:49 PM, Surfinette
>
I believe I may have found the beginning of an explanation for bug # 1
You said the words "cue creepy, haunted-mansion noises" about this
bug,.... well you are right to the point, its even worst that creepy,
truly crazy haunty:
It seems that bug # 1 only occur when I'm HOME !!!!
You remember when I said yesterday I tested JD 1.84 and I didn't have
the bug, and this morning I had the bug with JD 1.85 and when I step
back to 1.84 I had the bug again this time with 1.84 !!!! Well
yesterday I only did the test while I was in the office. This morning,
when I had the bug I was home.
This afternoon I re-did the test in various ways with 1.84 and 1.85
while I was in the tube and walking in the street far from home and I
did not have the bug (with neither 1.85 or 1.84).
Now I'm back Home, and I have the bug again.
Also, remember last week when I started to complain about this bug
(see discussion about JD 1.82), this was driving me crazy, and at some
point I was mentioning that the bug was occurring at RANDOM. Well last
week I was not home but on vacation at my parents' home where there is
wifi connection. And I kept testing JD in and out of their house... In
their house my phone was connected to their wifi network, at the beach
I had no wifi connection ;-) hence the reason for the "random"
occurrence of the bug.
My conclusion is that the bug occur only when I'm connected to wifi,
in other word when there is a "choice" of functioning wifi or data
connection for the phone.
This is giving me new ideas to try to understand this bug and do more
test.
As a side note, I want to flag that this afternoon, during my testing
session of 1.85 and 1.84, I tried to install 1.85 after uninstalling
1.84 and JD would keep FC has soon as I would hit the Activate button
in the setting page. The only way around this issue was to uninstall
both JD AND AOSP helper before installing the new version of JD. After
this very fresh install, everything went fine...
Lastly, you say "If my special ROM doesn't like JD"... But my ROM is
not that special! Modaco's Rom by Paul are very popular, as close as
possible to stock roms and usually very stable... (and, from what I
read, JD also seem pretty popular among people discussing on my
"special" Rom's thread ;) so I hope getting rid of this bug will not
only serve me...
On 21 juil, 15:25, Mark Lowne <marklo...@gmail.com> wrote:
> Agh! Now I want to remove the AOSP helper again :(
> Well, I'll remove the various warnings at least. Nothing to worry
> about: the AOSP helper is used to toggle between 3g and 2g only. It
> *only* works on CyanogenMod and Surfinette's ROM apparently, but since
> there's no way (that I know of) of knowing beforehand if that's the
> case, Setup will try to install it on all rooted phones - once it
> confirms it doesn't work, it'll uninstall it immediately.
>
> @Surfinette: ok, you can see for yourself if the
> red-dot-but-data-enabled is a bug in JD's logic: just check the log
> (either will do) after it happens and see what's the latest (most
> recent) entry about data. If there's a 'Data enabled', then some
> trigger is re-enabling data but JD fails to update the notification
> accordingly. If, on the other hand, there's just 'Data disabled', then
> *something else* (cue creepy, haunted-mansion noises) is re-enabling
> data.
> I'm now convinced that it must be the latter: try to remember if this
> problem was introduced with some JD build (1.8.2 or something), or if
> it really was your updating to Froyo, as I think it is (you can always
> double-check by installing some old version, say 1.7.9, on your Froyo
> ROM). If so, then your special ROM doesn't like JD (unless you have
> some other weird apps that could be causing this, but that seems
> unlikely).
>
> On Wed, Jul 21, 2010 at 2:49 PM, Surfinette
>
Surfinette
Jul 21, 2010, 5:35:53 PM7/21/10
to JuiceDefender
Regarding the Red-Dot-But-Data-Enabled (RDBDE) issue, I have narrowed
the problem and believe I know how to reproduce it.
RDBDE occurs if and only if (i believe) the phone state is moving from
Green-dot-with-active-wifi-connection to Red-dot (ie all data/wifi
connection disabled by JD).
There are mainly 2 ways to reproduce this, shown below as method (a)
or (b), the latter (b) being only possible with recent versions of JD
which include the Apps button:
(a) In JDs expert settings: set Data + Wifi + Screen buttons ON with
the "Only after unlock" button ON. Location can be either ON or OFF (i
don't think it matters). Set the other buttons to OFF in order to
avoid interferences during this test.
Then go to the Home screen of the phone and wait until you have in the
notification bar a Green-dot JD icon and a Wifi Icon (thus confirming
that an active wifi connection is enabled). At this stage, if you
don't see the Wifi icon in the notification bar (along with the green-
dot JD icon) then you won't be able to reproduce the bug.
Then put the phone to sleep and let it sit idle for at least 1 min
Then wake the phone but do not unlock it
Look at the notification bar: The JD icon should be red-dot and there
should be no icon showing data or wifi being enabled. If you see the
data icon in the notification bar (along with the red-dot JD icon),
then you have the "RDBDE" bug.
Older versions of JD (such as 1.79) do not have the red/green/yellow
dots with the JD notification icon, but it doesn't matter for this
test, because then at the last step when you awake the phone you
should still not have any data icon, if you have the data icon (before
unlocking the screen), then you have the bug.
(b) In JDs expert settings: Set the Screen button OFF. Configure the
Apps button with at least one App in green mode (the Market app for
our example) and set the Apps button ON. set Data and Wifi buttons ON.
Location can be either ON or OFF (i don't think it matters). Set the
other buttons to OFF in order to avoid interferences during this test.
Now go to the home screen, and wait a few sec until JD sets up. In the
notification bar, the JD icon should be red-dot and there should be no
data icon showing up (or only for a split second, but not constantly).
If you see at this stage the data icon in notification bar, then you
probably already have the bug...
Then launch the Market app (or any app you have set to green in the
Apps config in JD's setting) and wait until JD settles (this could
take up to 30 seconds). In the notification bar, you should end-up
having a Green-dot JD icon and a Wifi Icon (thus confirming that an
active wifi connection is enabled). At this stage, if you don't see
the Wifi icon in the notification bar (along with the green-dot JD
icon) then you won't be able to reproduce the bug.
Now go back to the Home screen of the phone (by pressing the home
button, or the return button or whatever) and look at the notification
bar: The JD icon should be red-dot and there should be no icon showing
data or wifi being enabled. If you see the data icon in the
notification bar (along with the red-dot JD icon), then you have the
"RDBDE" bug.
I experience the "RDBDE" bug with JD 1.79, 1.82, 1.84 and 1.85 and
Modaco Rom MCR R5 (Froyo + Sense).
Could anyone else make the test to check if this is just my ROM?
the problem and believe I know how to reproduce it.
RDBDE occurs if and only if (i believe) the phone state is moving from
Green-dot-with-active-wifi-connection to Red-dot (ie all data/wifi
connection disabled by JD).
There are mainly 2 ways to reproduce this, shown below as method (a)
or (b), the latter (b) being only possible with recent versions of JD
which include the Apps button:
(a) In JDs expert settings: set Data + Wifi + Screen buttons ON with
the "Only after unlock" button ON. Location can be either ON or OFF (i
don't think it matters). Set the other buttons to OFF in order to
avoid interferences during this test.
Then go to the Home screen of the phone and wait until you have in the
notification bar a Green-dot JD icon and a Wifi Icon (thus confirming
that an active wifi connection is enabled). At this stage, if you
don't see the Wifi icon in the notification bar (along with the green-
dot JD icon) then you won't be able to reproduce the bug.
Then put the phone to sleep and let it sit idle for at least 1 min
Then wake the phone but do not unlock it
Look at the notification bar: The JD icon should be red-dot and there
should be no icon showing data or wifi being enabled. If you see the
data icon in the notification bar (along with the red-dot JD icon),
then you have the "RDBDE" bug.
Older versions of JD (such as 1.79) do not have the red/green/yellow
dots with the JD notification icon, but it doesn't matter for this
test, because then at the last step when you awake the phone you
should still not have any data icon, if you have the data icon (before
unlocking the screen), then you have the bug.
(b) In JDs expert settings: Set the Screen button OFF. Configure the
Apps button with at least one App in green mode (the Market app for
our example) and set the Apps button ON. set Data and Wifi buttons ON.
Location can be either ON or OFF (i don't think it matters). Set the
other buttons to OFF in order to avoid interferences during this test.
Now go to the home screen, and wait a few sec until JD sets up. In the
notification bar, the JD icon should be red-dot and there should be no
data icon showing up (or only for a split second, but not constantly).
If you see at this stage the data icon in notification bar, then you
probably already have the bug...
Then launch the Market app (or any app you have set to green in the
Apps config in JD's setting) and wait until JD settles (this could
take up to 30 seconds). In the notification bar, you should end-up
having a Green-dot JD icon and a Wifi Icon (thus confirming that an
active wifi connection is enabled). At this stage, if you don't see
the Wifi icon in the notification bar (along with the green-dot JD
icon) then you won't be able to reproduce the bug.
Now go back to the Home screen of the phone (by pressing the home
button, or the return button or whatever) and look at the notification
bar: The JD icon should be red-dot and there should be no icon showing
data or wifi being enabled. If you see the data icon in the
notification bar (along with the red-dot JD icon), then you have the
"RDBDE" bug.
I experience the "RDBDE" bug with JD 1.79, 1.82, 1.84 and 1.85 and
Modaco Rom MCR R5 (Froyo + Sense).
Could anyone else make the test to check if this is just my ROM?
Hyatari
Jul 21, 2010, 6:10:23 PM7/21/10
to JuiceDefender
last.fm used to work with just the traffic trigger set @ 50k 2min but
it doesn't work now. also it does not work with the app trigger since
for some reason its called a background app even while on the
notification bar, but it also sits in the system area at the same
time.
On Jul 21, 4:35 pm, Surfinette <emmanuelle.braconn...@gmail.com>
wrote:
it doesn't work now. also it does not work with the app trigger since
for some reason its called a background app even while on the
notification bar, but it also sits in the system area at the same
time.
On Jul 21, 4:35 pm, Surfinette <emmanuelle.braconn...@gmail.com>
wrote:
Breece
Jul 22, 2010, 8:41:37 AM7/22/10
to JuiceDefender
Ok just sent you a log... JD is doing a fine job on my non froyo N1
(still waiting for CM6)
BUT, since the 1.8.x versions JD is disabling WiFi (sometimes) when I
disable the screen... Thats rather annoying, as I would like to stay
connected.
Location does seem to work, training is over:
View known locations:
W-Lan (1389m)
(still waiting for CM6)
BUT, since the 1.8.x versions JD is disabling WiFi (sometimes) when I
disable the screen... Thats rather annoying, as I would like to stay
connected.
Location does seem to work, training is over:
View known locations:
W-Lan (1389m)
Mark Lowne
Jul 22, 2010, 12:23:48 PM7/22/10
to JuiceDefender
Well, another of my posts got lost... But it's not all bad, as I might
have found the cause of the RDBDE problem.
So @Surfinette, try 1.8.7 and let me know!
@Hyatari: I'll test last.fm as soon as I find a way to download it
(Market Enabler isn't really working, apparently) (and why isn't it
available worldwide anyway?!)
@Breece: that might be a side-effect of Location. It'd be interesting
to see exactly what's going on, so could you please 1) enable debug
log (in 'help') and 2) send me a log as soon as you notice JD disabled
WiFi when it shouldn't have?
have found the cause of the RDBDE problem.
So @Surfinette, try 1.8.7 and let me know!
@Hyatari: I'll test last.fm as soon as I find a way to download it
(Market Enabler isn't really working, apparently) (and why isn't it
available worldwide anyway?!)
@Breece: that might be a side-effect of Location. It'd be interesting
to see exactly what's going on, so could you please 1) enable debug
log (in 'help') and 2) send me a log as soon as you notice JD disabled
WiFi when it shouldn't have?
Tony Harverson
Jul 22, 2010, 12:26:05 PM7/22/10
to juiced...@googlegroups.com
Hi Mark,
See the log I sent last night using the feedback option, it was the issue Breece mentioned. I don't use the location option, and debug was on.
Tony
See the log I sent last night using the feedback option, it was the issue Breece mentioned. I don't use the location option, and debug was on.
Tony
Joe Betsill
Jul 22, 2010, 12:39:42 PM7/22/10
to juiced...@googlegroups.com
@Mark Last.fm isn't available outside the US because the record labels are greedy. Same with Pandora, and the same reason why Spotify doesn't work in the US.
Such is the world we live in, sadly.
Mark Lowne
Jul 22, 2010, 1:19:18 PM7/22/10
to JuiceDefender
@Tony: found it! Ok, there's a problem somewhere with JD thinking wifi
gets disabled/enabled by mysterious forces. Will look into it.
@Joe: but I can buy a paid subscription over here! I could (possibly)
listen to last.fm via the browser (+Froyo+Flash), why not allow the
native client? The (Nokia) S60 client used to work, *with* a paid
subscription... This doesn't make any sense...
And the saddest thing is that I can't bring myself to spend the 3€/
month anyway, simply because the thought of Pandora (which is roughly
12 billion times better - ah, the magic days of 2005...) would ruin
the experience. As soon as I find some time (i.e. not before 2016)
I'll buy some EC2 or similar just to proxy Pandora :/
On Jul 22, 6:39 pm, Joe Betsill <joebets...@gmail.com> wrote:
> @Mark Last.fm isn't available outside the US because the record labels are
> greedy. Same with Pandora, and the same reason why Spotify doesn't work in
> the US.
>
> Such is the world we live in, sadly.
>
gets disabled/enabled by mysterious forces. Will look into it.
@Joe: but I can buy a paid subscription over here! I could (possibly)
listen to last.fm via the browser (+Froyo+Flash), why not allow the
native client? The (Nokia) S60 client used to work, *with* a paid
subscription... This doesn't make any sense...
And the saddest thing is that I can't bring myself to spend the 3€/
month anyway, simply because the thought of Pandora (which is roughly
12 billion times better - ah, the magic days of 2005...) would ruin
the experience. As soon as I find some time (i.e. not before 2016)
I'll buy some EC2 or similar just to proxy Pandora :/
On Jul 22, 6:39 pm, Joe Betsill <joebets...@gmail.com> wrote:
> @Mark Last.fm isn't available outside the US because the record labels are
> greedy. Same with Pandora, and the same reason why Spotify doesn't work in
> the US.
>
> Such is the world we live in, sadly.
>
> On Thu, Jul 22, 2010 at 12:26 PM, Tony Harverson <t...@trog.bofh.org.za>wrote:
>
>
>
> > Hi Mark,
>
> > See the log I sent last night using the feedback option, it was the issue
> > Breece mentioned. I don't use the location option, and debug was on.
>
> > Tony
>
>
>
>
> > Hi Mark,
>
> > See the log I sent last night using the feedback option, it was the issue
> > Breece mentioned. I don't use the location option, and debug was on.
>
> > Tony
>
Joe Betsill
Jul 22, 2010, 1:51:15 PM7/22/10
to juiced...@googlegroups.com
Well, I'll be damned. I didn't know that last.fm was available outside the US for a subscription. At the risk of driving this way off topic, the reason Pandora is so much better than last.fm is because last.fm suggests music that other people listening to that song also liked.. so it's like crowdsourcing your musical tastes. Pandora, on the other hand, analyzes the music and suggests other music that is similar to that music.
Austin Hsu
Jul 22, 2010, 2:18:15 PM7/22/10
to juiced...@googlegroups.com
This is exactly why I usually prefer last.fm to pandora. Not only the methodology, but the fact that it's recorded what I've listened to and can make suggestions based on listening history.
Truthfully, they're both good, they just meet different needs. It's a lot like the Firefox vs Chrome debate (I use both).
Pandora is better for finding things way out in left field that you didn't know you would like, but it can also make REALLY terrible suggestions because it doesn't have that scrobbling record (both yours and others worldwide). I even get offended by some of it's suggestions, much like I get offended when I am given a fork in an asian restaurant (being Chinese and all). :D
Back on topic: I wish I could help with the wifi location testing but the router at my office has died and the owner has not seen fit to replace it yet. Unfortunate, as throwing money at the problem is his usual course of action.
Truthfully, they're both good, they just meet different needs. It's a lot like the Firefox vs Chrome debate (I use both).
Pandora is better for finding things way out in left field that you didn't know you would like, but it can also make REALLY terrible suggestions because it doesn't have that scrobbling record (both yours and others worldwide). I even get offended by some of it's suggestions, much like I get offended when I am given a fork in an asian restaurant (being Chinese and all). :D
Back on topic: I wish I could help with the wifi location testing but the router at my office has died and the owner has not seen fit to replace it yet. Unfortunate, as throwing money at the problem is his usual course of action.
Reply all
Reply to author
Forward
0 new messages