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 :)

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! :)

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

UPDATE:
Please try both and report back how it works :) And update to 3.4.6 ;)

tl;dr: “remove system package”, update to v3.4.1, report again!
-

This is just AMAZING! Thanks everybody for the awesome feedback!

This is obviously a delicate issue and there are a number of problems to address, so it’s better to handle them one at a time.
Let’s start with the lost-after-reboot one. It took a lot of checks and workarounds coding but 3.4.1 should survive reboots (and updates). It’s been tested on CM6.1.1 and stock Gingerbread – but I’m sure all the ROMs out there do things differently, so keep the feedback coming!

IMPORTANT: “About”/scroll to bottom/“remove system package” BEFORE upgrading to v3.4.1 (or you’ll have to delete a spurious apk with other means – not sure if its presence is harmful for v3.4.1).

To completely remove JD you will probably need to reboot after “remove system package” and before uninstall with the usual means (Android’s Manage applications etc.) – share your experiences on this.

Also, feel free to experiment with and without USB debugging on. I’ll do some testing on my own.

Then we’ll see if the r/w vs r/o (@Tracy any more info on this? It’s the first time I hear of it) is indeed a problem.

I’m pretty sure other problems (corrupt files etc) are caused by timing issues. You could test whether a high vs. low

Known devices

HTC Thunderbolt

stock 2.2.1 – LTE enabled (what’s it called exactly?): 8 – LTE disabled (?): 4 – LTE only (is it available?): ?

stock 2.3.x: LTE enabled (what’s it called exactly?): 8 – LTE disabled (?): 4 – LTE only: 11 or 12 ?

Droid Bionic

stock 2.3.4 – CDMA/LTE: 7 – CDMA only: ?

UNL3ASH3D v1.3 – CDMA/LTE: 7 – CDMA only: 4

Droid Charge

???

LG Revolution 4G

???

Galaxy Tab 10.1

???

Current status

Things might be worse than I expected. I’m getting few and contradictory IGT reports, and it seems possible that every phone (or, even worse, firmware) uses different network mode “codes”.

First, an explanation: network modes are basically just two: LTE enabled or LTE disabled. You can manually switch network mode by going to Home/Menu/Settings/Wireless/Mobile networks – there should be an option called “network mode”, “system selection”, or something similar that allows you to enable or disable LTE. On some phones/firmwares you’ll have more options, like “LTE only”, “CDMA only” etc.
These network modes map to internal codes (numbers), and in order to perform the right action JD needs to know what’s the code for the desired network mode.

I’ll keep a list of what we can discover in the thread status. Please help me fill it in! It’s easy: for every phone/firmware I need to know what network code is associated to what actual network mode.
- disable WiFi if it’s connected
- note your current network mode (settings/wireless/mobile networks)
- run the IGT (at the very bottom of the About tab); it will generate an email
- note the number in the email subject (e.g. if the subject is “[IGT] CDMA + LTE/EvDo auto:8 – JuiceDefender v3.7.3beta” the code is 8)
- send the email
- pick a different network mode in settings/wireless/mobile networks
- for safety, turn airplane mode on, wait 10 seconds, turn airplane mode off, then wait until you see the data connection coming back; it shouldn’t take more than 30 seconds
- run the IGT again, note the number, send the email
- repeat until you’ve exhausted all the options for network mode
- leave a comment detailing your findings (remember phone model and firmware version!) so I can update the list

Thanks!

Update:
@All translators:

First of all thank you again for all the help so far :)
I have good news:
You are done with your translation? You want to help translating, but your language is already done OR you dont feel comfortable translating?
Worry no more !
We need a comment for every string (see attached picture).
The comment should state where exactly this string is to be found so the one translating can take this into consideration for translating it :) (Context is the keyword here)

http://www.imagebanana.com/view/w37tidw9/Example.jpg
First: WHAT is it (in this case a button label, which means it should be short)
Second: WHERE is it

Ps.: To be honest: I know this kinda sucks.. but if we do it together it will be done quickly and improve future translations! You can comment in any language file, as comments are universal through all translations but please comment in english :)

Want to help translate JuiceDefender into your language?
First, you should be aware that translating JuiceDefender is quite the sucky job, as it’s heavily text-based with loooooong tehcnical descriptions, and it’s generally confusing to do it over a web interface often with no knowledge of what the texts refer to in the actual UI. A 100% complete translation from scratch probably requires one week of dedicated work, one hour or so every night (after one hour you’ll go insane, so it’s better to come back the next day).

Still here? Great! If you really want to help, here’s how:

• vote this thread (it’s used to coordinate the translation effort) and introduce yourself in the comments
• go to http://translate.juicedefender.com and sign up and pick your language
• start translating!
• especially for long texts, it could be easier to start with the Microsoft translation (it’s generally much better than Google’s); you’ll have to fix the obvious mistakes and absurdities, but it will usually take you to 50% (depending on how good the algorithm is for your language). WARNING: the automatic translation WILL mess up tags, newlines and placeholders (these things are explained below), be careful to fix them manually

Caveats:

• sometimes two or more related texts that refer to each other (e.g. a button name and a description mentioning that button) are not close to each other in the translation interface. A good memory – or, better, keeping a bunch of additional browser tabs for quick reference – is necessary to remember how a certain concept is translated, in order to keep the whole thing consistent
• single and double quotes MUST be escaped with a backslash – that’s why “doesn’t” is shown as “doesn\’t” or "enable “2G only” in Android settings" becomes “enable \”2G only\" in Android settings". Most languages don’t use apostrophes (single quotes) but beware of this for double quotes.
• newlines are shown as “\n”. Again, these must be preserved where they are (even if it’s at the end of the text). As for double quotes, pay attention to make sure there are no spaces – \ n or \ " will break the resource file.
• some texts have html tags for emphasis. Try to preserve them for the exact word(s) they surround after shuffling the sentence around to fit your language’s syntax.
• in a couple of instances you’ll also see html entities – namely “& amp;” for “&”; keep in mind that the general rule for the texts is to treat them as html (or more precisely xml), so you can’t put “weird” characters in them without the proper care described above
• lastly, some texts have weird groups that look like %1$s or %3$d – these must be preserved (they are placeholders for substitutions). For instance you’ll see “accuracy %1$dm”, this shows up in the UI as “accuracy 1043m” – note how the “m” at the end is not part of the placeholder as they’re always groups of 4: %?$?
• for descriptive texts there are no length constraints, but be careful with short ones as they generally belong to buttons/tab titles/notification elements etc. In many cases for these there is a length constraint – for example if they belong to one button that must fit with 2 others within one row – so try to find a way to express the text in a way as concise as possible

Finally, once you’re done with some major translation work, let me know in the comments so that I can pull the translated resource file and publish a new build – once it’s done you should check for possible inconsistencies in the texts and/or layout problems.