Guest gusthy Posted January 9, 2011 Report Posted January 9, 2011 By now most Froyos I used had a rather strong battery consumption, while on the partial wake list available in spare parts, showed that Dialer is the cause of some partial wake. FLB RLS6 replaced Dialer with AOSP one, and it is not in partial wake list anymore. Plus, it seems that battery drain is much lower. It would be nice to understand the reason for this.
Guest oh!dougal Posted January 9, 2011 Report Posted January 9, 2011 My guess would be that its the re-appearance of something that showed up in the leaked prototypes. There's a ZTE 'feature' for 2.2 that is along the lines of "turn the phone screen-down to mute all sounds" and in consequence the cpu spends time/effort and thus battery checking the orientation sensor VERY frequently. IIRC this showed up as Dialler activity ... IMHO, its a somewhat negative feature. I rather like the ZTE smart dialler, but not this aspect.
Guest gusthy Posted January 9, 2011 Report Posted January 9, 2011 My guess would be that its the re-appearance of something that showed up in the leaked prototypes. There's a ZTE 'feature' for 2.2 that is along the lines of "turn the phone screen-down to mute all sounds" and in consequence the cpu spends time/effort and thus battery checking the orientation sensor VERY frequently. IIRC this showed up as Dialler activity ... IMHO, its a somewhat negative feature. I rather like the ZTE smart dialler, but not this aspect. Sure. But finally it turns out that if battery is important, stock dialer is better... BTW with flbR6 the dialer partial wakeup time is almost exactly the same as the sum of phone calls.
Guest oh!dougal Posted January 9, 2011 Report Posted January 9, 2011 My guess would be that its the re-appearance of something that showed up in the leaked prototypes. There's a ZTE 'feature' for 2.2 that is along the lines of "turn the phone screen-down to mute all sounds" and in consequence the cpu spends time/effort and thus battery checking the orientation sensor VERY frequently. IIRC this showed up as Dialler activity ... Found it ! :D THE FIX: Really quite simple, turn off (as in un-tick) the "Turn to mute" setting via: Home Screen > Menu > Settings > Sound > Turn to mute Kudos to Chall32 http://android.modaco.com/content/forum/32...e-dialer-issue/
Guest gusthy Posted January 9, 2011 Report Posted January 9, 2011 Sure, but for example Japanese Jellyfish doesn't contain this option :D
Guest leromarinvit Posted January 9, 2011 Report Posted January 9, 2011 Sure, but for example Japanese Jellyfish doesn't contain this option :D I'm still running RLS3 and I have it. Must have been some change after that. Oddly enough, I had it on and it didn't drain the battery all that fast. Maybe it wasn't working anyway.
Guest OSFUK Posted January 9, 2011 Report Posted January 9, 2011 Sure, but for example Japanese Jellyfish doesn't contain this option :D It does has but under a different name: "turn to forbid phone ring".
Guest _amano Posted January 9, 2011 Report Posted January 9, 2011 With my RSL5 it is unticked by default.
Guest Victor von Zeppelin Posted January 9, 2011 Report Posted January 9, 2011 With my RSL5 it is unticked by default. Same, and my dialler is still using partial wake.
Guest IronDoc Posted January 9, 2011 Report Posted January 9, 2011 In JJ it's not the turn to mute thing any more. Not for me at least.
Guest Victor von Zeppelin Posted January 9, 2011 Report Posted January 9, 2011 Incidentally, can I just replace the Dialer, Contacts and related apks from Flb6 into RLS6? Would that (hopefully) solve some problems?
Guest Frankish Posted January 9, 2011 Report Posted January 9, 2011 Incidentally, can I just replace the Dialer, Contacts and related apks from Flb6 into RLS6? Would that (hopefully) solve some problems? Depends on what Flib did to get them working but i'd say, Nandroid and try please.
Guest Victor von Zeppelin Posted January 9, 2011 Report Posted January 9, 2011 Depends on what Flib did to get them working but i'd say, Nandroid and try please. I will directly! Well, once I super save and backup Game Dev Story.
Guest oh!dougal Posted January 9, 2011 Report Posted January 9, 2011 With my RSL5 it is unticked by default. If you are seeing the issue, it would be helpful to try ticking it, and then unticking it, just in case the problem is that it is not initialising properly in the 'off' condition. (And then seeing over the next hour or so whether that makes a difference.)
Guest Victor von Zeppelin Posted January 9, 2011 Report Posted January 9, 2011 Right, some success in that, just straight copying Flib's apks into RLS6. No idea in battery usage yet, but i'll soon find out. Would you like an clockwork package to help others, do you think?
Guest Victor von Zeppelin Posted January 9, 2011 Report Posted January 9, 2011 Incidentally, a somewhat fail...thing going on. Or, dialer works when it's a link either on the homescreen as an icon, or in the app list. However, in the Launcher Pro dock, it FC's android.proccess.acore. Otherwise, everything working. I haven't had long enough to test wake-lock. But pressing the face buttons doesn't seem to bring up the lock screen.
Guest gingerninja Posted January 9, 2011 Report Posted January 9, 2011 Right, some success in that, just straight copying Flib's apks into RLS6. No idea in battery usage yet, but i'll soon find out. Would you like an clockwork package to help others, do you think? A clockwork zip would be very helpfull. Thanks Andy
Guest Victor von Zeppelin Posted January 9, 2011 Report Posted January 9, 2011 A clockwork zip would be very helpfull. Thanks Andy Ever so sorry, further testing reveals force closes of the main android process, and no actual fix to battery life.
Guest cobhc Posted January 9, 2011 Report Posted January 9, 2011 (edited) You can't just transfer the dialer over to JJ. I've tried, and I get force closes of the dialer process. The default AOSP dialer is integrated into the contacts app as another tab, so it's not a separate apk, which means we need to find out what Flib did to integrate it. Edit:- You had some success Victor? Which files did you copy over? Edited January 9, 2011 by cobhc
Guest Matthew Ferguson Posted January 9, 2011 Report Posted January 9, 2011 By now most Froyos I used had a rather strong battery consumption, while on the partial wake list available in spare parts, showed that Dialer is the cause of some partial wake. FLB RLS6 replaced Dialer with AOSP one, and it is not in partial wake list anymore. Plus, it seems that battery drain is much lower. It would be nice to understand the reason for this. I've had no partial wake issues whatsoever, and I've got the dialer.
Guest gusthy Posted January 9, 2011 Report Posted January 9, 2011 I've had no partial wake issues whatsoever, and I've got the dialer. And what is about battery consumption? It is a very strange thing, though. JJ shows continous battery decrease, percent by percent. flb 6 shows constant battery level, then suddenly battery decreases by 3-5 percent.
Guest Matthew Ferguson Posted January 9, 2011 Report Posted January 9, 2011 And what is about battery consumption? It is a very strange thing, though. JJ shows continous battery decrease, percent by percent. flb 6 shows constant battery level, then suddenly battery decreases by 3-5 percent. It sounds like they're both depleting at the same rate but showing it differently. Have you tried recalibrating your battery? I've had great battery life, with 2 days of use with wifi occasionally on, sometimes for quite a while, and it's been great.
Guest dansken86 Posted January 10, 2011 Report Posted January 10, 2011 I'm on JJ and have the "Cell standby" issue, it can be as high as 50%.. So, I've been using PowerTutor for a while now and like others say, the "Radio subsystem" (Dialer, RIL...) together with "Kernel" are the two things consuming most battery (only when sleeping though, when on it's the screen). I don't know what's normal for android phones and I don't have any other phone to compare with... Well here comes what I found interesting.. maybe.. The two doesn't consume battery because of CPU usage, but almost solely because of 3G usage. Both when screen is on and off, there seems to be irregular 30 seconds "connections", which actually uses a lot of battery. Though sometimes it goes a while between the uodates. Interestingly, I can't see that any data is actually transferred at these points (if you can rely on the notification icon...). If I turn off the mobile internet, they disappear; if I turn off autosync, they are still there... Therefore I assume it's not the "turn to mute" thing spooking again. Maybe some kind of connection error, though only for the mobile internet? And I have full signal strength. If there would be an app updating (gmail, contacts, whatever), I guess that would be shown in powertutor... Maybe these connections are normal on android, just that it uses a lot of battery when connecting? I have very limited knowledge in these areas, so... Anybody has a theory or tried? Gibberish?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now