v3.9.4: [market, latestdev]
- fixes
- intro screen for new users
________________

v3.8.8beta:
- workaround for silly Bluetooth bug in Android 2.3.4+ (apparently only affecting some Samsung firmwares)

v3.8.7beta:
- minor fixes

v3.8.6beta:
- added “set minimum brightness” for Brightness
- added per-network “keep enabled” for Location
- AOSP helper fix for 2.3.7
- minor fixes

v3.8.5beta:
- several fixes and improvements

v3.8.3beta:
- added customized sync frequency for sync accounts!
- added per-app custom controls (mobile data, wifi, wifi forced, bluetooth) in the Apps trigger
- support for WiFi-only tablets in the free version
- some fixes

v3.8.2beta:
- fixed night/peak schedules only starting the first time
- fixed a bug in Traffic
- fixed other stuff (honestly I forgot what it was)
- reworked the widgets, improved “user” control
- added network mode widget
- added Bluetooth enable/connect in QuickBox
- sat view on “view location”
- UI tweaks
- updated translations

v3.8.1beta:
- Honeycomb support! (feedback needed)
- better handling of the keyguard during phone calls
- fixed some more bugs
- removed read logs permission, if you want to see the log you must enable JD’s internal logging

v3.8.0: [stable]
- hopefully fixed a really weird issue on Froyo phones

v3.7.9beta:
- more fixes! :)

v3.7.7beta:
- fixes
- partially updated translations

v3.7.4beta:
- fixed “enable on charger” for Bluetooth control
- more descriptive triggers for Bluetooth control (graphical notification)
- fixed QuickBox setting not sticking

v3.7.3beta:
- fixed a regression in Backup
- improvements in Location
- launcher fix for X10 and Optimus V

v3.7.2beta:
- tentative MMS fix part #3
- compatibility fix for Eclair/Froyo
- FC fix

v3.7.1beta:
- tentative MMS fix part #2
- fixed silly Plus/Ultimate regression introduced in v3.7.0
- further improvements in Location
- “quickbox only” mode for Night and Peak
- added hide icon option for text notification
- cosmetic tweaks

v3.7.0beta:
- temporary launcher fix for SE (X10 etc.)
- tentative MMS fix

v3.6.9beta:
- several fixes in Location and Network mode
- added “force reconnect” for Wifi in Troubleshooting
- added option to disable JD via SMS
- added persistent log option
- autodetect LTE devices
- added require USB debugging for AOSP helper installation
- performance improvements
- some cosmetic tweaks

v3.6.8beta:
- improvements and fixes for network mode control
- tentatively added LTE to network mode control (experimental!)
- fixes in wimax location trigger
- added network mode location trigger

v3.6.7beta:
- simplified Location algorithm, new features for manual management of locations

v3.6.6beta:
- improvements in AOSP helper for CM7
- improvements in automated report feature

v3.6.5beta:
- improvements in AOSP helper
- improvements in automated report feature

v3.6.4beta:
- experimental AOSP helper for CM7
- new semi-automated ‘send report’ feature

v3.6.3beta:
- new AOSP helper
- ‘use APN method’ option
- ‘send log’ button is back (oops)

v3.6.2beta:
- tentative workaround for ‘bad array lengths’ FC
- other tweaks’n fixes

v3.6.1beta:
- (fanfare) Bluetooth control! (and already quite sophisticated)
- performance improvements
- many small tweaks and fixes

v3.6.0beta:
- automatic Location merging! Different access points with the same SSID and within 300m of each other will be treated as one (larger) location
- possibly definitive (gotta love oxymorons) fix for G2X
- fixed an overflow bug in Brightness (causing the screen to dim when in bright sunlight)
- fixed a UI bug in Location that caused the user action to be applied to the wrong network
- added “exotic” governors in CPU control
- fixed service not restarting after profile switch
- added 5% threshold fo more

v3.5.9beta:
- Italian, German, Spanish, French, Portuguese, Dutch and Finnish translations – with varying degrees of completeness (please help! translate.juicedefender.com)
- improved Brightness algorithm: the min. brightness is increased between sunrise and sunset
- tentative improvement for cloud backup: a cloud restore request is forced when no backup is found
- partial fix for LG G2X stock Gingerbread

v3.5.8beta
- QuickBox should work now ;)
- new AOSP helper: fixed 2G<→3G issues, also controls GPS+background data
- several other minor fixes

If you’re using CM7+AOSP helper: beware of this issue http://code.google.com/p/cyanogenmod/issues/detail?id=2928

v3.5.7beta
- QuickBox! From the notification and the widgets
- short screen timeout when the keyguard is visible
- added ‘hide status bar icon’ option for the graphical notification
- fixed edge case of regular and peak schedules overlapping
- added ‘filter mode’ to Brightness (in Troubleshooting)
- fixed (hopefully) a rare problem with nonsensical sensor readings for Brightness
- workaround for WiFi being disabled while connected issue
- various other minor fixes
- minor UI tweaks

v3.5.6
- fixed Apps trigger when using custom controls
- fixed JD ignoring “mobile data disabled by user” when being disabled
- fixed Airplane mode issues
- fixed minor bug in Location when manually disabling WiFi
- minor tweaks, cleanup

v3.5.5beta
- launcher fixes

v3.5.4beta
- fixed beta/stable incompatibility regression
- tentative workaround for FC on Donut

v3.5.3beta
- fixed missing Night options with Plus
- workaround for “launcher icon disappeared”/“app is not installed” issue

v3.5.2beta
- improved Location training, added option to force additional training
- removed unnecessary battery checks

v3.5.1
- fixed stupid “rating” bug – sorry folks!
- other minor fixes

v3.5.0
- Brightness is more responsive (please re-set the light sensor setting)
- workaround for potential and unconfirmed Brightness-caused issues
- fixes, fixes, fixes
- some UI cosmetic improvements

v3.4.9beta
- fixes for some rare FCs

v3.4.8beta
- and the winner of Latedroid’s “Get A Compatibility Issue Fixed” special contest is… – drumroll – … the HTC Thunderbolt!

v3.4.7beta
- mercilessly squished lots of tiny cutey bugs (and some big, hairy, nasty ones)

v3.4.6beta
- performance optimizations for Apps
- fixed “can’t add widget” bug
- ugliest workaround ever for the Package-installer-cum-Brightness bug

v3.4.5beta
- Apps is streamlined, simpler to configure and more powerful
- interactive “training” mode for Apps
- added minimum timeout for Traffic
- fixed a Brightness-related FC
- workaround for Timeout “home” detection bug in HTC ROMs

v3.4.4beta – Spring cleaning edition
- “sneaking in” JuiceDefender Plus – soon on the Market!
- started heavy UI reorganization & simplification for the 3 tiers (free, Plus, Ultimate):
- some rarely-used customizations are no longer available in the free version
- the “Customize” profile only has the most used settings, all within one tab
- some settings are moved to the “troubleshooting” section in the About tab
- screen brightness control – yay! And it’s quite sophisticated
- workaround for the bug(s) that sometimes made the UI nonfunctional (“no settings” thread)
- added some Gingerbread compatibility layers (only tested on CM7 RC2/3)
- lots of performance improvements and cleanup
- improved license check
- tablet mode doesn’t need toggling airplane mode anymore
- added a “frequent schedule” mode to Peak
- added adaptive start/end to Night
- Night is delayed if the “Airplane” option is enabled and there’s an ongoing phone call
- added “only on wifi” for 2G/3G band switching timeout
- added overly-paranoid-“Mobile data AutoFix” in Troubleshooting – should never be necessary
- further improvements on detecting user actions/hardware status (lots of workarounds for the uberfragmented ROMs out there)

v3.4.3beta
- added GPS control – root only (I always forget to close Maps before turning off the screen)
- improved CPU control
- check for “USB debugging” before installing system package
- check for “use wireless networks” before enabling Location

v3.4.2beta
- added a separate lock timeout for the home network (yay!)
- fixed some timing issues with the “basic keyguard”

v3.4.1beta
- much improved Gingerbread+root support
- much improved Timeout (and fixed some minor bugs

v3.4.0beta – Sour milk edition
- awesome: support for CM7/Gingerbread+root
- awesome: new Timeout is fully functional across any Android version!
- added background data control (requires root)
- extended support to more kernels for CPU control
- backup/restore to/from sd as well
- improved handling of “xyz disabled by user”
- many internal optimizations

v3.3.7beta
- awesome: quick enable/disable connectivity from the notification!
- more changes to avoid situations of data staying disabled, with a new “force disable” option (controls/mobile data)

v3.3.6beta
- fixed a bug that could lead to data staying disabled
- fixed a bug in license check

v3.3.5beta
- MMS workarounds
- widgets/API operation is much faster
- toggling mobile data from widgets is now situation-aware

v3.3.4beta
- several scattered fixes
- German translation

v3.3.3beta
- fixed a problem with the API
- “disable” apps now obey the Traffic trigger

v3.3.2beta
- new integration API, see developer.juicedefender.com
- fixed cleanup code, should help with freezes on screen unlock after service killed by low memory

v3.3.1beta
- fixed “WiFi disabled by user” caused by other apps

v3.3.0beta
- fixed a bug in night adaptive start
- Italian translation
- added “force English” to frustrate the item above :)

Awesome investigation! And on top of it, a really enjoyable piece of writing. Well done!
This is my very limited understanding so far:
- The Revolution has two radios, one for good ol’ CDMA/EvDO, one for LTE – as demonstrated by having two networks listed in phone status (this seems to be in agreement with the fact that integrated chipsets haven’t been available until very recently)
- Apparently instead of having a properly integrated radio firmware that “abstracts” the two chips into a single entity, LG “patched” LTE on top of the old radio interface layer; it is unclear how “close to the surface” of the Android architecture this hypothetical patch gets, but it’s sufficient to wreak havoc in the APIs used by JD. However if this is the case it seems strange that the Froyo radio firmware didn’t have these issues – why would LG make things worse with an update?
- It may or may not be the case that LG (or Verizon, to avoid excessive network congestion) further “customized” its firmware by adding its own rules to manage the LTE radio. At least it would make some sense for them to implement something like this in a firmware update.
- There is at least one other instance (Tmobile G2X, a GSM phone) of LG doing very silly things (or, perhaps more likely, unintentional bugs) with its radio firmwares.

Anyway, the issue seems definitely related to LTE; here’s some stuff that I need to know with certainty (obviously you must disable WiFi before attempting these tests; also, it’s a good idea to disable ALL the other options in JD – such as WiFi, Location, Brightness, Timeout, CPU, Night/Peak, and Apps – so as to make it easier to find the useful bits in the log):
1) There should be (at least) 3 different settings (menu/preferences/wireless/mobile) pertaining to “network mode”: CDMA only (2G), CDMA+EvDo (3G), LTE (4G). I need to know the complete list. It’d be also helpful to know how each of the settings in the “testing” app (##4636## in the dialer then “phone info”) maps to those network mode settings.
2) If you select “LTE only” in the testing app (and assuming that this setting is allowed in the RIL), then let JD break connectivity (screen off→screen on), are you then able to make a regular voice call?
3) It seems that if you disable the LTE radio (by selecting either CDMA only or CDMA/EvDO for the network mode) JD works as intended. I must be 100% sure of this.
4) On a related note, does JD work if you leave LTE enabled in an area with no LTE service? I understand most of you cannot test this but it’s important to know whether the problem is related to enabling/disabling the LTE radio vs it getting actually connected
5) Some of you suggest that JD is able to correctly re-establish mobile data during scheduled syncs while the phone is sleeping (screen is off) – the problem purportedly only happens at screen on. This seems unlikely to me but it’s potentially extremely important. Set mobile data control and schedule in JD, reboot and leave your phone idle for 30 minutes, then check JD’s log – you should be able to see “schedule start” then “data enabled” then, IF a connection is indeed established, the actual connection info: “Connectivity: NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED”; the important point being (again, IF this occurs at all): is it LTE that’s being connected, or rather 3G? (you’d then see something like “EvDO” for “type”)
6) If you have root, install the AOSP helper, then under Controls disable “mobile data” and enable “network mode switching”. It should show a suboption for the allowed modes, make sure they’re all enabled (2g, 3g and 4g). Set “disable timeout” to 1m. Set a schedule of 5 minutes. Check the log after a while. If network mode control works, it will show a 3G (EvDO) connection at scheduled syncs, and an LTE connection after screen on (maybe preceded by 3G as the mode switching and/or the LTE connection establishing might take a bit longer).
7) It’d be of course nice to get logs for 4), 5) and 6) above. (A rather sobering fact: this thread might well have 170 votes, but I only got logs from two people. This makes statistical assessment impossible and doesn’t even begin to cover all possible scenarios.) For bonus points it’d be even nicer to get both regular and “-b radio” logcats of a) disabling and then reenabling mobile data manually via preferences/wireless/mobile and b) disabling and then reenabling (or attempting to reenable) mobile data via JD’s “toggle mobile data” widget.

1) We’re talking about the “data disabled by user” issue here. How to know if that’s the problem you’re having? Check the notification/widget/log – does it say “Data off: user” (or graphical variants)?
2) Make sure this is NOT caused by a) you explicitly disabling mobile data via Android settings/widgets/etc. nor b) you inadvertently tapping on JuiceDefender’s widgets nor c) another app (either via JD’s API or on its own)
3) Do whatever steps are necessary to replicate the issue (i.e. to make JD come up with “data off: user”)
4) send the log immediately afterwards (mention “data off: user” in the email)

If there’s no connection, but you see “data on: something”: that’s an entirely different problem, which is
1) due to your carrier (it refuses to reconnect you for some reason) – not JD
2) rarely and randomly occurring
3) usually fixable by cycling airplane mode off and on (perhaps waiting a couple of minutes inbetween)
Wanna check for yourself? Perform the following lame test (it’s gonna take quite a while – perhaps north of 15 boring minutes of tapping and staring): Uninstall JD and reboot. Now go to settings/networks/mobile data and toggle it off and on repeatedly, ad infinitum. Eventually the connection won’t come back.
So, if you have this second problem: open a new thread, and let me know how often it happens. I might be able to code a workaround for it (by automatically doing the airplane mode cycling when necessary – unfortunately JD can’t bribe your carrier)

Addendum: the OP’s problem (mobile data getting stuck on “turning on” until reboot) is caused by a low level issue (at the driver level) which should be greatly minimized (thanks to a timing workaround) in v3.2.9 or perhaps some later build, I don’t remember anymore. Given that this (old) thread has been “hijacked” anyway, I’ll edit the title.

Current status

v3.7.5beta should fix the issue for SE X10 (and variations), X8, and LG Optimus V.

Procedure:
- uninstall JD (or JD beta) and JD Plus/Ultimate
- reboot
- reinstall JD beta + JD Plus/Ultimate
- reboot
- hopefully there should be no FC :)

If it works, please report in the comments!

If the launcher still crashes:
- open JD, go to the About tab, scroll to the bottom, tap on ‘send log’, tap ‘ok’, pick your email app
- edit the subject by inserting “LAUNCHER” at the end
- send the mail

Temporary workaround

Quite simply, use a different launcher, like LauncherPro or ADW – they’re on the Market

Why does this happen?

The cause is a rather poor implementation of their “differentiating” customized launchers by the manufacturers. JuiceDefender uses one particular API call, which is admittedly rarely used, but part of the standard API nonetheless. It seems that Google forgot to insert that specific case into their Android compatibility test suite…

Thanks for your patience!

Dear Users,

we are back on track fixing those ICS bugs / problems you are having.
If you are on a Galaxy Nexus please visit this thread:
https://latedroid.uservoice.com/forums/70437-feedback/suggestions/2765962-ics-galaxy-nexus-lte

If your screen does not turn back on please visit this thread
https://latedroid.uservoice.com/forums/70437-feedback/suggestions/2790553-ics-screen-will-not-turn-back-on

What problems are you having? Please state your device and the specific problem.
So far we know of these ones (please also tell us if you are having one of those problems !)

Timeout function
Interactive Apps trigger doesnt notice apps
CPU freezes
Wifi enabling / disabling problems
ASOP helper cannot be installed (does it still work as IF it is installed?)

Thank you very much. On a side note: Please make sure you installed the latest beta of JD from the android market AND try these steps:

Uninstall JD & JD+ & Ultimate
Reboot
Delete the JuiceDefender.backup file in your “Download” folder on your SDcard.
Reboot
Install JDbeta & JD+ / Ultimate (depending on what you purchased)
Do NOT restore your settings.

UPDATE: v3.6.8 is out (latestdev) with a brand new Location algorithm. For the sake of testing, please clear all your locations (or try the new view/auto-reset) and restart from scratch :)
Training works as before (conceptually) but the uber-expansion should be prevented in most cases.
Share your results!
_______________
Ah, that’s interesting! (@Bubo)
This is what I mean by “location gets polluted by stray readings” – for whatever reason (ahem radio firmware bugs) the normal cell kicks out the phone, which then connects, even if for only a couple of seconds, to a cell much farther away; in the long term this will result in pitiful Location accuracy.

So, some possible ways to circumvent this:
- have an option to set lat/lon/accuracy manually
- have a manual ‘freeze’ button for each location that would prevent further “expansion”
- have a global “max radius” option for all locations
- have a supersmart and complex algorithm doing the “freezing”/max-radius-enforcing automatically by keeping track of location reading accuracies over several days (my favorite solution as it would imply me going into deep-coding mode possibly for weeks – it would also surely introduce bugs and unwanted side effects, at least for a while until they’re ironed out)

What’s your vote? And what are, in your opinion, the pros and cons of each solution? Or do you have a wholly different idea? DIZCUZ! :)

After updating JuiceDefender/Plus/Ultimate the app doesn’t work anymore!

Sometimes Android doesn’t handle well app updates – it’s quite rare, but it happens. The solution, however, is simple and reasonably quick: uninstall JuiceDefender (the free one), reboot, and reinstall.
In case you encounter issues after restoring your settings (from About→Backup/Restore), try the uninstall/reinstall without restoring your settings – i.e. reconfigure your settings manually.

I purchased JuiceDefender Plus/Ultimate, but when I open it it brings me to the Market to download the free version!

JuiceDefender Plus and JuiceDefender Ultimate are addons – they work on top of JuiceDefender (free) and they need it to be installed to work. So simply go ahead and download the free one as directed ;)

I tried to buy JuiceDefender Plus/Ultimate from the Android Market, but my card is refused/the purchase doesn’t get through.

Unfortunately there’s nothing I can do. I DO NOT process payments on the Android Market – Google does; so whatever the issue, it’s about Google Checkout, not JuiceDefender. However, most of the times the problem is specific to the credit card you’re using; it’s worth trying with a different card and/or contacting the card issuer for further assistance.
(it also seems that Google, on its end, is slowly sorting out most Checkout issues.)

I purchased Plus/Ultimate from the Market, but I can’t download it!

It might take some time for Google/your credit card company to authorize the transaction. This is usually done within hours, but in some rare cases it might need up to two or three days.

Unfortunately there’s nothing I can do to speed up the process; at any rate rest assured that it will work eventually – or you’ll be automatically notified that the transaction couldn’t be completed and was canceled; in the latter case your card will not be charged – see the previous question for further information. For step-by-step troubleshooting please see here: http://market.android.com/support/bin/answer.py?answer=1067233

I purchased JuiceDefender Plus/Ultimate from the Market, then I lost/changed/wiped my phone, and now it says I have to buy it again!

App purchases on the Android Market are linked to your Google account and the purchase never expires.

This means that whenever you wipe your phone, or get a new one (or even a dozen), all your purchased apps will immediately be available (in fact they’ll be downloaded automatically) as long as you set up the phone with the same Google account that was used to purchase the apps in the first place. Again: purchased licenses are tied to your Google account – they cannot be transferred to another account.

I have bought Plus/Ultimate, but I can’t see any added functionality

If you’re using one of the preset profiles, Plus and Ultimate will add WiFi control to that profile. To enable other features you have to choose the “customize” or “advanced” profile. After you tap on either button, scroll down a bit and tap on “confirm”.

Also remember that some features might not be supported by your ROM.

JuiceDefender Ultimate “deprecated”: what’s the deal?

If you have the “deprecated” version – formerly called “alternative” – you DO NOT NEED to buy Ultimate again. Your version works and will be updated.
It’s marked as deprecated because in the past (for Market problems) some users required a slightly different version – that’s no longer necessary so this alternative legacy version is now exactly the same as the “regular” Ultimate.

JD shows “there was a problem checking the license”

The license check requires internet connectivity and some time. Once you enable JD, leave it running for a couple of hours. If you don’t have a data plan, please connect to a WiFi network.

Refund policy

If you want a refund, please use the “contact seller” link for your order at Checkout – http://checkout.google.com – and choose “request refund”. All requests submitted within one week after the initial purchase will be honored – while the free JuiceDefender is more than enough to make an informed purchase decision, it’s also true that the Google-enforced 15 minutes refund window is ridiculous.
Requests submitted via other means cannot be taken into consideration.

FEEDBACK REQUIRED:
- Nexus 1/S + CM7: anybody can confirm whether this issue http://code.google.com/p/cyanogenmod/issues/detail?id=2928 has been fixed? I.e. is network mode switching working without nasty side effects?

- Installation failures (other than on HTC devices with S-ON)? (remember to send a log! If the app gets stuck, terminate and reopen it – or reboot – then send log immediately)

- LTE phones: more reports are needed! See here: http://feedback.latedroid.com/forums/70437-feedback/suggestions/2235451-4g-lte-support-

GENERAL INFORMATION

What’s the AOSP helper?

The AOSP helper circumvents some Android limitations that would otherwise make it impossible to perform certain operations.

Currently the AOSP helper, if installed and functioning, can:
1. perform network mode switching (sometimes called band switching) between 2G/3G/4G
2. control the Background Data setting (in addition to the Auto-sync setting)
3. enable and disable GPS

While #2 and #3 are only really useful, from a battery consumption perspective, in some very specific circumstances, #1 often allows for substantial battery savings.

What are the requirements for successful installation?
1. Your device must be rooted
2. Your device must be running at least Android 2.2 (Froyo)
2. If you are on Android version 2.3.4 or greater, read-write access to the system partition is necessary, as the AOSP helper must be installed there

These are the minimum requirements; it might very well be possible that the AOSP helper cannot function on your phone even if it meets these.

In particular, point #3 implies that on Android 2.3.4+
- the AOSP helper will need to be reinstalled if you flash a new firmware
- the AOSP helper can’t be installed on HTC devices with S-ON