v1.8.0 - new Location, again

[Mark Lowne]

penne all'arrabbiata here: http://juicedefender.googlegroups.com/web/JuiceDefender180.apk

- improved Location - this should be the definitive incarnation of the
algorithm (finally!), but there might still be bugs (it became
complex...)
- toggle data widget is now tri-state (force disable, force enable,
default)
- fixed 'send feedback' stopping service bug
- minor UI tweaks
- AOSP helper only enabled for CyanogenMod
- spanish should be included

[Charles Tan]

I can't seem to make the auto-disable button light up. Is this by design?

[Charles Tan]

Location function is also weird. I needed to restart to make my Wifi work properly. Haven't gone out yet so I'm not sure if location is working fully.

[Smokem_I]

@Charles I was having same problem. I had to clear known locations. Wifi was disabling itself while still in known location. Now its working properly.

On Jul 12, 2010 7:37 PM, "Charles Tan" <charlesd...@gmail.com> wrote:

Location function is also weird. I needed to restart to make my Wifi work properly. Haven't gone out yet so I'm not sure if location is working fully.

On Tue, Jul 13, 2010 at 10:18 AM, Charles Tan <charlesd...@gmail.com> wrote:
>

> I can't seem...

[Charles Tan]

Finally uninstalled and reinstalled 1.7.9. Location does not seem to be working properly for me. It just activates 3G instead of Wifi. Remembers Wifi for a while but activates 3G again next time I unlock my phone.

[Charles Tan]

@Smokem: Sorry but I cleared known locations as well. It just was not working for me. 1.7.9 is working really well for me though.

[Smokem_I]

@Charles lol yes right after I sent that wifi didn't enable on my next screen on. I have had this issue in other builds before and JD figures it out after enabling wifi manually again a couple times. Ill keep trying on 1.8.0 hopefully this build will figure it out.

On Jul 12, 2010 8:46 PM, "Charles Tan" <charlesd...@gmail.com> wrote:

@Smokem: Sorry but I cleared known locations as well. It just was not working for me. 1.7.9 is working really well for me though.

On Tue, Jul 13, 2010 at 11:42 AM, Smokem_I <smok...@gmail.com> wrote:
>

> @Charles I was having ...

[Charles Tan]

@Smokem: Ok. Appreciate your update if you have any luck with it. My experience however is bad. It would work a couple of times and then it will just start enabling 3G instead after a while.

[Smokem_I]

@Mark had a FATAL ERROR. I sent a log your way. It said to uninstall, reboot, reinstall which I did and got another FATAL ERROR. Had to revert back to 1.7.9.

On Jul 12, 2010 9:10 PM, "Charles Tan" <charlesd...@gmail.com> wrote:

@Smokem: Ok. Appreciate your update if you have any luck with it. My experience however is bad. It would work a couple of times and then it will just start enabling 3G instead after a while.

On Tue, Jul 13, 2010 at 11:54 AM, Smokem_I <smok...@gmail.com> wrote:
>

> @Charles lol yes right...

[Matt]

Same problem here.... Just got the same message, so came here to see
if anyone else had the same issue. Will revert to 1.7.9 too.

On 13 July, 06:05, Smokem_I <smokem...@gmail.com> wrote:
> @Mark had a FATAL ERROR. I sent a log your way. It said to uninstall,
> reboot, reinstall which I did and got another FATAL ERROR. Had to revert
> back to 1.7.9.
>

[Ignacio]

Hi

I would like upgrade my version 1.3.7 to this one duo to the included Spanish translation that I made, because I have to test it, but seem that there are a big trouble, isn't it?

Maybe Mark will release a new version soon so I will wait some time before upgrading.

Best regards

[Mark Lowne]

Thanks for the logs, people!
Quick-fix-build here: http://groups.google.com/group/juicedefender/web/JuiceDefender181.apk

Fixed the FC, and changed some stuff - now JD should always pick up
and store the location after you manually enable WiFi (this doesn't
necessarily mean that you won't have to enable it manually more than
once before it stores all possible fixes)
Remember to 'clear known locations' first!

On Jul 13, 8:45 am, Ignacio <soyunpla...@gmail.com> wrote:
> Hi
>
> I would like upgrade my version 1.3.7 to this one duo to the included
> Spanish translation that I made, because I have to test it, but seem that
> there are a big trouble, isn't it?
>
> Maybe Mark will release a new version soon so I will wait some time before
> upgrading.
>
> Best regards
>

[Surfinette]

I've just moved to ROM 2.2 with Sense on my HTC Desire. Since then, I
have many problem with JD
- JD version 1.80 and 1.81 does not work at all : the 3G button
disappears from the settings page (while the button is still there in
ROM 2.1 !!! very strange) and The JD service is desactivated as soon
as I leave the setup screen.
- JD version 1.79 works slightly better (the service does always shut
down and the 3G button does not disappear from the setting page),
however the 3G and 2G data connexion does not respond well to JD's
settings
- A pop-up keeps flashing JD has been granted superuser permission

I've tried with ROM MRC R4 here:
http://android.modaco.com/content/htc-desire-desire-modaco-com/313149/13-jul-r4-wip-refresh-modaco-custom-rom-for-htc-desire-with-online-kitchen-froyo-frf85-frf91-with-sense/
This rom is using SuperUser version 2.2.1, which may explain part of
the problem (my previous Rom under android 2.1 was using SU version
2.1)...

rgds

Surfinette

[Surfinette]

Forget about part my previous post, as I finally managed to get 1.81
running with my Froyo Rom (I had to do a full wipe).

But, I still have the problem that 2G/3G still don't work properly. I
cannot manage to have 2G only with the Froyo ROM, it is always 3G
whatever I set in JD.
With Android 2.1, I had no issue with setting 2G only.

On 14 juil, 00:04, Surfinette <emmanuelle.braconn...@gmail.com> wrote:
> I've just moved to ROM 2.2 with Sense on my HTC Desire. Since then, I
> have many problem with JD
> - JD version 1.80 and 1.81 does not work at all : the 3G button
> disappears from the settings page (while the button is still there in
> ROM 2.1 !!! very strange) and The JD service is desactivated as soon
> as I leave the setup screen.
> - JD version 1.79 works slightly better (the service does always shut
> down and the 3G button does not disappear from the setting page),
> however the 3G and 2G data connexion does not respond well to JD's
> settings
> - A pop-up keeps flashing JD has been granted superuser permission
>

> I've tried with ROM MRC R4 here:http://android.modaco.com/content/htc-desire-desire-modaco-com/313149...

[Ignacio]

Hello

I have a HTC Legend 2.1 and I'm having problems with the APN.
Sometimes JD doesn't enable the APN after unclock screen and I have to
lock and unlock it to enable it.

I have enabled the option "Enable after screen unlock"

Best Regard

[Surfinette]

I'm still experimenting JD with Froyo. And actually the issue with the
3G button disappearing in the set up has come back with version 1.81.
I install version 1.79 and the 3G button in there (but whatever the
setting with the data and 3G buttons I can't get 2G only, only 3G).
I install v 1.81 on top of v1.79 and the button is still there, but I
still have the issue with 2G setting
I re-run setup with 1.81 and the 3G button disappears (after setup and
never comes back). And JD is still not able to force 2G.

With Android 2.1 I get none of these issues...

[Surfinette]

You'll think I'm crasy, because I will again contractict my previous
post, but actually, JD 1.81 is driving me crasy !!!!

I tried again with Android 2.1 and now I encounter the same issues
that I had with Froyo: 3G button disappearing, JD service
disconnecting each time I leave the setting screen. These problems
have started after running the setup in 1.81, but it does not occur if
I install 1.81 on top of 1.79 without running setup with 1.81.
After getting these problems with 1.81, I tried to step back on 1.79,
but then the bugs occured also in 1.79, even if I uninstalled 1.81
(with Linda manager) or rerun setup in 1.79. I had to do a nandroid
restore to get back to a normally functionning 1.79.

Also, in version 1.81 I notice the following:
- there is a new "sync" button but it can't be activated under Android
2.2 or 2.1
- there is a "cpu" button that appears instead of the "lock" button in
Android 2.2. This CPU button does not show up in Android 2.1. The CPU
button seems uneffective in lowering the cpu there seem to be some
error in the log.

Could you advice an apk that would calculate the effective cpu rate of
the phone so I could check how this CPU button actually operates?

In the mean time, I'm reverting to JD v 1.79, because I have too many
issues with 1.81 (be it with Android 2.1 or Froyo)

[Joe Betsill]

This may not have anything to do with your problems, but for me, I installed the latest JD immediately after upgrading to the newest 2.2 source based rom, and I noticed JD started acting up- it would randomly "disbale" the CPU feature and setup didn't display all the options I'm used to seeing during Setup.  As it turns out, the latest SuperUser app (I confess I forget the version) sometimes hangs up during a reboot and does not give any app after the hang su permissions.  Once I downgraded back to my old version of Superuser everything worked soothly.

[Mark Lowne]

@Surfinette: answering the various threads... :) from now on 3G
toggling is ONLY available on CM roms, and the AOSP helper will ONLY
install on CM roms. As you don't have CM, it won't work anyway (and in
fact it didn't work) on your phone.
If you see 'Sync' it means Setup pretty much failed. Do a full
uninstall and try again (with 1.8.2). If you keep seeing CPU-related
errors, send more logs my way.

@Joe: indeed the superuser app is causing all sorts of troubles - not
just the recent bug, but since it introduced the 'notify' feature,
which basically creates and destroys an activity just for that (*even*
if you disable notifications completely) *every* time an app requests
su. Considering that JD might request SU up to 5 times or so at every
enable/disable (but many root apps tend to do so), it's easy to see
how this course of action is really unwise - at the very least, things
will be unnecessarily much slower with all the
activity-lifecycle-related bookkeeping that Android needs to do (not
to mention that most apps save and restore their state at every
'interruption', as per Android guidelines), but sometimes things might
just break because of the unexpected (and frankly unreasonable)
timings.

I wanted to address the problem since I first noticed that (more than
one month ago) but needless to say I never found the time to look for
the relevant XDA thread and source repo, fix the code, submit a patch,
and discuss the thing with all the people involved - ok, I never even
attempted the first step :)

If any of you guys hang out on XDA, *please* tell the people involved
that those notifications are a BAD, BAD idea...

[Breece]

Had a rough time at university, but I expect to go on with testing
next week :) Just wanted to tell you:
Keep up the good work :)

[Surfinette]

@Mark: Sorry for my ignorance, but what means "CM" when you mention
"CM rom"?... Ii'm still pretty noob on cetain things relating to
android :)

Also, I still do not understand why you cannot implement the 3G button
in Froyo system beyond version 1.79. I really miss this feature which
seems to be working in JD 1.79 (I just double check again). With Froyo
+ JD 1.79, I have the 3G button toggling the phone's network mode
between "GSM ony" and "GSM/WCDMA auto". This I guess is what the 3G
button should be doing, so why can't it be implemented along with
Froyo in 1.81 or 1.82?

[Nitin Philip]

Surf: CM means CyanogenMod - a custom built ROM made by a group of developers for a variety of Android devices.

 www.cyanogenmod.com

[Stefano Z.]

this is the latest version working on my Acer Liquid with Xian 0.9 ROM
based on 1.100.39 eclair bin version.

On Sat, Jul 17, 2010 at 8:54 PM, Mark Lowne <mark...@gmail.com> wrote:
> @Surfinette: the problem is that the AOSP helper (the thing doing the
> 3g/2g toggling)

[Stefano Z.]

setup run, no errors, but after i click on the 'enable' button it show
me again the setup window...

On Thu, Jul 22, 2010 at 10:11 AM, Mark Lowne <mark...@gmail.com> wrote:
> @Stefano: I'll need more info: what's exactly is *not* working on
> later builds? Setup completely failing, or something more specific?