David
-
881 votesstarted ·
AdminMark
(Dev, Latedroid)
responded
Quite some builds since v3.6.6! Development is moving forward fast on several parallel paths; as of v3.7.3, this is the feedback I need:
- AOSP helper (rooted only): if installation failed before, try again – if it fails again send the log and let me know here: http://feedback.latedroid.com/forums/70437-general/suggestions/1053767-aosp-helper-all-you-need-to-know
- LTE-capable phones (only if the AOSP helper installed): http://feedback.latedroid.com/forums/70437-feedback/suggestions/2235451-4g-lte-support-
- the new Location is getting fixes and improvements at every build – lemme know if it works better or worse: http://feedback.latedroid.com/forums/70437-feedback/suggestions/1319595
- MMS problems: MMS should work reliably as of v3.7.3 but it’s 100% untested, so please share your findings: http://feedback.latedroid.com/forums/70437-feedback/suggestions/1172191-mms-sending-receiving-not-working
- remotely disable JD via SMS: try it and tell me if it works! http://feedback.latedroid.com/forums/70437-feedback/suggestions/2126315-enable-data-if-the-phone-receives-a-sms-with-a-cer
David
gave this 2 votes
·
-
15 votescompleted ·
AdminMark
(Dev, Latedroid)
responded
Fixed at last! UJ is now updated on the Market and AndAppStore.
Sorry guys, there was an unexpected problem with the delicate JD/UJ interaction (in fact I think JD v3.0.0 has problems anyway – please also update JD to v3.0.1), and to complicate things further I inadvertently updated the Android SDK which broke (as always) my build script – but it took three whole days to fix this time… :(
David
gave this 3 votes
·
David
commented
·
Agreed on 3.0
-
147 votesstarted ·
AdminMark
(Dev, Latedroid)
responded
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
-… more
David
commented
·
My version 3.0 keeps force closing, so I am back to the non-beta version for now.
David
gave this 3 votes
·
David
commented
·
I have the same issue I believe. It also appears to hinder wifi turning on again.
-
30 votescompleted ·
AdminMark
(Dev, Latedroid)
responded
I’m closing this v2-related thread – please keep me posted on the new one here: http://feedback.latedroid.com/forums/70439-juicedefender-beta/suggestions/1319595-jd-v3-location-trouble
David
commented
·
Not really better when disabling location.
David
gave this 3 votes
·
David
commented
·
2.1.2 location not working. It crashes the app on trying to either view locations or remove them. Droid 1 2.2.
-
19 votescompleted ·
AdminBreece
(Support, Latedroid)
responded
Please use the new thread and v3 of JD :)
The following text used to be the old status!
_______________
@Reverend Paul (and others with this problem): what’s your phone? Do you have CPU, Timeout, Apps or Location enabled in JD? If so, try disabling them and let me know if it helps with the sluggishness. Are you sure it’s WiFi-related? Is it gone if you disable WiFi control (so as to leave WiFi either always on or off) in JD? Can you check whether manually enabling/disabling WiFi results in some sort of similar sluggishness?
(I’d much rather find what’s causing it and fix it, if possible; if not, I’ll see to add the delay option you requested)@Kiwi78: that doesn’t look good, but it’s an unrelated problem. However, it might be gone in v2.1.8 – lemme know! (if it’s not fixed, start another thread!)
David
commented
·
Not really better disabling the location triggers.
David
gave this 3 votes
·
-
1 votecompleted ·
AdminMark
(Dev, Latedroid)
responded
I’m guessing this was fixed some time ago?
David
commented
·
Yes I just checked it thanks!
David
shared this idea and gave it 1 vote
·
For some reason I am not getting the new build notifications.