yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Persechini:
I don't know if it helps, but among changes I've made that had a positive impact in battery life (meaning I only did one of these thing at a time, over different builds in separate moments) were:

uninstall Facebook

uninstall Google Plus

disable a number of facebook receivers via ROM Toolbox Pro (worked in a previous build, in my current 20130110+JellyX it reactivates 6 receivers as soon as I refresh the app)

disabling google location services

Each of them reduced consumption a little, and one time I had a bug were the google calendar app kept failing to sync and retrying every couple of minutes, but was fixed by turning calendar sync off and on again.

The weird part is that today I uninstalled Facebook (yes, I keep coming back) and Office Suite Pro, I think I messed a little with location settings too, but anyway, battery consumption dropped from about 2,5% per hour to about 1,1% per hour, a drop that is greater than the increased battery consumed by facebook when I last installed it (and office suite I had installed for like forever) and other time I activated/deactivated location services. I know Office Suite is a self updating app (meaning one more app looking for updates other than Play store), which takes me to swiftkey flow beta, which was sideloaded and recently updated to swiftkey 4 (so, play store-updated now). Since I always measure my battery with 3g and wifi ON (with wifi set to never sleep), letting the fone switch automatically, and the better reported battery lives are from people who are more cautious about network connections, the whole excessive battery consumption thing might be solely caused by apps chattering up with their servers way more than necessary. The fact that is all shows up as Android power consumption instead of the apps whose active services belong could be the reason this is so hard to track on the kernel?

Maybe I'm far off, I'm not a programmer anyway, just an observant user,
[Defy Android Development] sevenrock:
Uptime 60h, no ringtone bug.
[Defy Android Development] theclaytons:
All good stuff. I have this thought that charging or using the PC to charge, transfer data increases battery life. I.e. if I charge using the wall charger and use "normally" battery life is less than if I charge via PC USB. Not scientific, but if this could make a difference maybe it could trigger some thought for someone smarter than me.
[Defy Android Development] phobos_1984:
From what I remember from my Electronics and Telecomunication Institute studies, if you charge the battery "slowly" (and USB via PC does it slower than the wall charger) you get some more life from it. This is due to the slower and more, let say, controlled enlargment of the Li-on (metal) crystals, that leaves less "holes" beetween each other. In a few words you get more density. Vice versa when you do it fast, you get less density (more empty spaces), so the battery lasts less. It's obviously not a permanent phenomenon.
[Defy Android Development] drunk_ryder24:
so does the stock rom,wich is probably why stock has better battery live generaly than cm
[Defy Android Development] Tapajyoti:
is tha YAFU build running fine??? and what gapps should be installed with this build???
[Defy Android Development] fryta22:
Almost 50 hours rongtone bug did not happend yet. :D

This build is very smooth, preety fast and small battery need.

For me personal YAFU build is the best build for ever for my Defy.

I install minimal gapps from first site thir thread, same gapps for any quarx build.
[Defy Android Development] rugaxp:
guys, mind to share what's this YAFU build about?

has been not following the thread and flashing ever since the buggy performance from the recent previous build.

sounds like good news that latest build is having positive feedback.
[Defy Android Development] niksy+:
Check it out here, mate - http://xdaforums.com/showthread.php?p=38282947#post38282947
[Defy Android Development] YetAnotherForumUser:
Both builds are 'running fine' for the most. Both exhibit some anomalies with regard to reported battery use, mostly manifesting itself through Android OS or Android System taking up the top spot in the battery stats. The have been occurrences of the JellyX-based build booting with a black (but backlit) screen, necessitating a reboot. There is one report of the Quarx build exhibiting the 'ringtone' bug. All this can be gleaned from the posts above this one so I'd advise you to go through them. Having done so you'll have as much information about this subject as anyone else around here...
[Defy Android Development] marcospulido:
Thanks.. it works!
[Defy Android Development] lief.erl:
When you guys say "Android OS or Android System taking up the top spot in the battery stats" thats excluding screen time right?

If you use any android device (including our beloved defy) for about 4-5 hours (not in one go with wifi being on for most of the time), how much battery juice do you get?
[Defy Android Development] YetAnotherForumUser:
When we say Android OS (et al) are on top we mean they are on top. Have a look at those stats I posted a few messages back where one phone had Android OS taking 52% of the (reported) battery time. It is mathematically impossible for something else to be on top in that case...

How much screen time you'll get on a full charge depends on many things. I'd estimate you'd get about 8-10 hours, more if you just use the thing as a book reader, less if you play games, use a lot of data, play load music, use the screen as a torch, etc.
[Defy Android Development] lief.erl:
I am on 20.02(pure Quarx's ROM) and I have yet to see Android OS top in my defy's list.

If about 10 hours is the expected time (with atleast 4 hours of screen time and always on wifi) then I guess this ROM is not bad after all, in terms of battery performance.
[Defy Android Development] phobos_1984:
I don't think so. The difference exists, but it shouldn't be so huge like we are experiencing between stock and cm10 ROMS.

Btw: 71h uptime the bug is there. Also the phone became almost unusable due to huge lags. 20/02 Quarxs pure ROM, Defy +. :(
[Defy Android Development] illumanati22:
Agree with u my pal even I can't use other mods like Aokp weather icons n lock rings in this build n battery drains very quick
[Defy Android Development] AnTerNoZ:
AW: [JB] CM10 Android 4.1.2 for the Defy(+)

that's why I buy a Samsung travel charger after my Motorola charger dies. they are cheap and deliver fast enough power for the defy with only 0,7A the original charger had 0,85A
[Defy Android Development] przemhb:
To clear some misconceptions concerning battery capacity and charging current please note:

1. Charging current value won't influence how long your battery lasts. Whatever value charging current will have charger's control logic (CC-CV) will ensure battery is fully charged at the end of each charging cycle.

2. "Fast" charging, that is with current >1C (>1540mA for Defy's battery) will reduce battery's life, i.e. it's capacity will drop from cycle to cycle [look here].

3. "Slow" charging, that is with current <1C won't reduce battery's life.

4. When Defy is charged from PC USB port maximum current is about 480mA, that is merely 0,31C. Motorola's charger outputs up to 850mA, and that's still only 0,55C.

Taking the above into account you can be sure that the way you charge your Defy's battery won't result in noticeable difference in working time of your Defy.

You can find more in-depth knowledge about batteries at batteryuniversity.com
[Defy Android Development] rashsalmn:
February 20 build is by far the best build we have. It is extremely responsive and haven't had any lag as such (I have around 110 apps).
[Defy Android Development] kryzeK:
Quarx, update cm updates mms.apk in the future build, please
[Defy Android Development] Floydroider:
I've been seen these lags and slowdowns in many ROMs and devices, every time after a long period of use.

The 20/02 build runs really good, and I don't face these huge lags you say, but you could try these solutions I use to make the phone run smooth.

I started using that greenify app and it's working good, didn't seen a increase in performance or battery life, but the phone stoped to be slow after a long time of use. And I use the es task manager to stop some apps that start with the phone too.
[Defy Android Development] lief.erl:
My phone (on 20.02 vanilla), using smartass governor, constantly jumps between highest and lowest processor cycle rates i.e. 300 and 1100(overclocked). I am pretty sure this was not the case with some earlier ROMS using same CPU governor. If this is indeed a bug then it could also be a potential suspect of battery hog in latest ROM.
[Defy Android Development] rugaxp:
thanks for enlightenment mate!
[Defy Android Development] vic160890:
Hello,

I'm running YaFU's build (jellyx) and i have run into a little problem.

I use 4.2 camera and sadly it has all the axis reversed.. Evem though i used the same patch for every build. On the earlier build with jellyx kernel i had some problems too, the camera wouldn't show the entire picture it would take.
[Defy Android Development] ezantera:
I must say I dont have half problems of some people report. From my knowledge most of weird problems come from not fresh install but clearing only cache and dalvik before instalation of new build. I used to believe that is enough but it is not. I always end up with messed up settings and that is causing weird problems. Full wipe is a must if you want to make sure.

There is and option in development that you can kill apps with holding back key. I kill every program that I will not use again in some time and I dont have problem with battery anymore. If I dont do that, google maps for example would stay open all that time in background. Dont even mention facebook. Use for example IMO to connect only on facebook chat.
[Defy Android Development] mikrom.cz:
Like Te'alc said, indeed. I think it's good as "last in 2012" version.

I dunno why, but YAFU version killed my phone twice. (phone lying on the table and suddenly light up itself, black screen and red led :( )
[Defy Android Development] sUpErwHoO:
I'm using the feb20 build, my USB has stopped working. Any solutions?? I read through and someone said its a port problem, my phone charges fine on the socket but doesn't get recognised on the computer, or on rsd.

Sent by an alien.
[Defy Android Development] kanpurite:
http://www.youtube.com/watch?v=p85xwZ_OLX0
[Defy Android Development] Sajat.:
It seems to me, that doing a wipe chace in STOCK recovery solve the black screen issue!!
[Defy Android Development] lief.erl:
Even my phone's usb port has stopped working. It's a hardware problem and will require motherboard replacement. Believe me, I have tried installing various ROMs but none could correct it. From now on, you can use airdroid(free app) for all transfer purposes.

In case, you are able to find a solution please let me know.
[Defy Android Development] nedywest71:
36 hours with YAFU Rom !!!

So far so good :)

Everything work as it should.

No data drops and Wi-Fi always ON.

I do have a custom Battery (HC Gold 2430.Ah) which charges to 80% but it last for more than 10 hour with everything ON and around 50 apps, and I am happy with that.My phone is hooked to the charger overnight and give me enough power throughout the day easily.I do not have much calls, but instead a lot of e-mails, and checks through social network and internet therefore in my list of what services drain the battery most on the top is listed Screen 50%. Android OS 6%, Android System 5% etc.

I am new to the CM10 so anyone with more knowledge could you please, comment if that is good for what I could expect or shall I check / try something else?

I am looking as well for app that combine all social net. feeds in one interface ( in the way Moto BLUR does). Currently use Flipboard but not verry happy in the way info is displayed.Too many clicks.

Thanks to YAFU for his work and everyone else involved in all development for our DEFYs!

Thanks in advance to everyone reply here!
[Defy Android Development] javlada:
Hi, this weekend I flashed Feb 20 build and now my bluetooth stopped working. I can turn it on/off and it seems to work but it won't connect to any device. Am I the only one having BT problems?
[Defy Android Development] lief.erl:
Has anyone experienced battery drops with latest rom? Mine does quite persistently from 58 to 49% for the last five days, although battery life seems good - 10 to 12 hrs(with heavy usage and always on wifi)
[Defy Android Development] devil1406:
Hi there,

Everyone is talking about new 20.02 version, but I don't know about which one!

So I decided to ask you guys, which version is better, Quarx's or YAFU's?

Thanks in advance. ;)
[Defy Android Development] YetAnotherForumUser:
More wakelock madness - negative values in /proc/wakelocks

While chasing the wakelock daemons which haunt Android in general and the current Defy releases in particular I noticed something strange: negative values in /proc/wakelocks.

For an example of this silliness have a look at an HTML-formatted /proc/wakelocks dump (linked from my own server as this forum does not seem to allow table-formatted data). This dump was taken on my phone which runs the JellyX-kernel.

It would be interesting to know if this phenomenon is limited to a specific subset of phones running a specific kernel - like the JellyX kernel I built. I have not found any other examples of negative values in this file on the 'net. I did some digging, asked some questions (which remained unanswered) and had a look at the code. As the values in /proc/wakelocks are derived from ktime (which can be negative) it is not by definition a bug to see negative values here. Be that as it may, the semantics of negative total times and negative time-outs somehow escape me so I assume there is a bug at play.

I can see several potential causes for this (probable) bug:

toolchain issues

32bit vs 64bit data interpretation issues

A large jump in ktime between the aquisition of the wakelock and the presentation of the statistics

I'll do some more experimenting with this, starting with the toolchain. I built the last releases on a 64bit version of Linux (Mint 14/Nadia) while the earlier JellyX kernels were built on a 32bit install (Debian Sid), using a different toolchain (4.4.3 vs 4.4.0). There have been bugs cq. discrepancies with regard to ktime handling on 32bit vs 64bit installations before, this might be yet another example.
[Defy Android Development] eagleeyetom:
Thread cleaned from the battery chit-chat. It's not a battery life thread, so discussing it here is pointless and clutters the thread. Try to stay on topic.
[Defy Android Development] LeopardSurd:
Review for Quarks JB from 20.02 for Defy+ with minimal gapps and few apps from Google Play (no games): lag, lag, data drops, lag (but no FC-S at all). Not usable if compared with latest CM7. Not recomended for every day usage.
[Defy Android Development] royale1223:
Some lag immediately after installing gapps is to be expected because of the heavy sync.
[Defy Android Development] woodman:
No problem here... And I thing it's the case for the most of us...Did you do a full wipe before flashing CM10 ?

Keep in mind that we'll probably never have as good performance as a CM7 based ROM.

That said I don't agree, this CM10 ROM is a 100% daily use ROM.
[Defy Android Development] gkkovacs:
I agree.

Quarx's 20130220 (and YAFU's 20130216 that's based on it, regardless of the earlier date) are lagging much more than earlier builds:

- app switching and launching are much slower

- free memory is less

- lagging starts after about a day of uptime

I'm not sure what changes/fixes contribute to this lag, maybe the unnecessary rngd (my phone had become laggy with the entropy app installed).

I am seriously thinking about returning to sevenrock's 20130117 or 20130127 build, they were much more fluid, less laggy builds, also without the ringtone bug.
[Defy Android Development] Pacquix:
I am using the 20.02 build after 4 months using the great 18.11: it is even smoother, just with a few (big) lags after 1 day. The only bug is the high battery drain, even in airplane mode, but I'm not sure it always happens.
[Defy Android Development] woodman:
LOL : I'm quoting myself : "...the most of us..." minus LeopardSurd and gkkovacs...and ?

Weird...Why such differences about performances/bahaviours of this 20.02 Quarx build ? In my case, as I said, I have no problem... I also have tested sevenrock's 20130117 and 20130127... And I don't see such lags even after 2 days of uptime with 20.02 build... I even find that it's smoother than sevenrock's builds...

Defy green lens - CM10 20130220 Quarx Build
[Defy Android Development] LeopardSurd:
Me again.

Few more infos about my experience with last JB build on Defy+.

Installed on clean, from zero.

No tweaks added.

Tested 3 days so no improvements in terms of speed from the beginnning of using JB even with the cpu overclocked to 1200 (with right vsel, no reboot), on demand/boosted/performance governor. On CM10 with CPU 1200-boosted is slower than 1000 Mhz-ondemand on CM7 (general usage, not game experience). I don't care about benchmarks but user experience.

It is as slow as original GB for Defy+ even slower.

I encountered few data drops but enought for me.

Also the WiFi power signal is worse than on CM7.

Sometimes when I receive a call, the name of the caller doesn't appears imediatelly. Quite awfull.

I find the stock browser worse in terms of rendering than GB one, AdAway remove the adds but the space of the adds is still there. Chrome is better but slower, too slow.

GSM signal as good as on CM7.

Battery: ok, not worse, not better.

Trebouchet Launcher tends to lag (scrolling and opening app drawer), Holo Launcher also when scrolling. ADW Launcher Ex is better but not on my taste.

I like the interface, is more polished than the one from CM9 but this doesn't make me a happy user.

No FC detected, quite good.

HDW acceleration was on for everithing.

L.E. I'm sick of Android - I own also a Razr HD Maxx purchased for battery but stil lags even if it has a more powerful hardware. My next smartphone is a WP8.

L.E.2: Great job Quarks, hope you'll find a way to improve CM10. Regards.
[Defy Android Development] ktmbikerman:
Have you tried using Interactive governor?

Sent from my Motorola Defy
[Defy Android Development] woodman:
OK, thanks for this big report.

Did you try Interactive governor ? This is the default one and I think Quarx optimized his ROM / Kernel with this governor. So you'd better try "Interactive" and report again.
[Defy Android Development] lief.erl:
How about smartass governor, after all it's an improved version of interactive governor?

That's what i read on a thread, explaining all the governors, here.
[Defy Android Development] woodman:
Sorry but I don't know about smartass governor and generally speaking about governors. I prefer keep default one in order to avoid issues... I can live with Interactive which suits me and which makes my phone run normally...
[Defy Android Development] drunk_ryder24:
i use by default smartass and its way better than interactive,less than reported bugs no ringtone bug or such
[Defy Android Development] LeopardSurd:
Yes, tested few hours from the beginnings (normal usage: internet browsing, chat, sms, calls). Not satisfied with it. So hopped that smartass or performance gov's could be better. Not unfortunately. In the last 24 h I tested only performance gov. It's known that when it is activated, the CPU is on max power most of time if screen is on.

Now I'm back on CM7 nightly build from FuZZ_ (cherry, 18/02/13 build, 1000 MHz ondemand, 4 steps clock) with all my previous apps. Everything it is all right, just proximity bug on call is still there.
[Defy Android Development] LetoKynes:
Regarding these two points - I think Chrome as a whole is pretty buggy and can run slow even on latest devices.. as for launcher, have you tried Nova? I got it in the last sale and it's been perfect for me.
[Defy Android Development] Pacquix:
have you tried SuperchargeV6? I am running very smooth with the correct OOM settings and the lag nullifier
[Defy Android Development] hacktheheaven:
Dude... For me it's working flawless with JellyX kernel not even a single reboot... And coming to the lag its occasional and this rom is perfect for daily usage... (self experience) thnx for quarx.... Blechdose, yafu, seven rock and who ever involved in this project.....!!! You guys rocks...!!!
[Defy Android Development] LeopardSurd:
No, didn't and will not test it soon because I don't have many time to loose with my phone. In fact, Defy+ is used now as a „second/backup” phone.

I'll give a try later, in summer, to see how this project evolves. Until then, hope there will still be clever guys to work for this project.

Just wanted to share my experience and to warn the new possible users of CM10 that it is still not better enought as CM7 is - just my point.
[Defy Android Development] YetAnotherForumUser:
I found at least one of the culprits for these negative values. The problem is limited to JellyX. the cause being commit c9ed17b ("Faster Sleep"). There might be similar patches lurking inside JellyX which need to be changed or reverted but as it is late that will have to wait...
[Defy Android Development] eagleeyetom:
Thread cleaned.
[Defy Android Development] woodman:
Hey guys,

Just found something very interesting (I hope so) about the 'ringtone bug' (perhpas it is)...

I have a Green Lens Defy with 20130220 Quarx build and it seems that the 'ringtone bug' occured twice during an uptime of 68 h...

My observations and actions were :

1) I was listening to music and suddenly music playback stopped.

2) Even after my music player was killed, I wasn't able to start music again...I though it could be a sd card access issue.

3) So I opened my file explorer application to see if I could access to my sd card files. It worked well.

4) I tried to call myself with another phone (bacause I though I could perhaps reproduce the 'ringtone bug' in this state) and YES, the phone didn't ring at all. Apart from this, my phone ran flawless... No other symptoms...With these observations, I though that one of the culprits of this 'ringtone bug' could be a media process related bug or both media AND "SD card access process" related bug ...

5) With phone still running, I tried to unmount my sd card and then to mount it.

6) Back to my music player and playback WORKED since my sd card was unmounted/mounted.

7) Again, I tried to call myself with another phone and YES, the phone rang without problem !

So, without rebooting my phone, I was able to workaround the 'ringtone bug' with a MANUAL ACTION. I'm not sure that it's exactly the 'ringtone bug' but it seems to, beacuse this is very similar, isn't it ?

So even with 20130220 Quarx build, it seems that the 'ringtone bug' is still here (even with a 2.6.32.9 kernel compilation).

I will have a try again with sevenrock's build (also with a 2.6.32.9 kernel) to see if I have the same behaviours....

Cheers
[Defy Android Development] rubjonny:
This is a different issue I think, some do hear the ringtone but its not playing correctly, lags and stutters (I had this problem)

you seem to loose access to the SD card for whatever reason, maybe mediaserver bug?
[Defy Android Development] Shrewdy:
Exactly the way you did it now.... and while trying to point you to your mistake even i did so....:p

But seriously this is a development thread...things like battery drain, how to flash this rom and things like those should not be discussed here...

May be you did something wrong....

Thanks
[Defy Android Development] woodman:
OK, perhpas... But as I said in point 3 : "I opened my file explorer application to see if I could access to my sd card files. It worked well."

So it could be only mediaserver that wasn't able to acess to the sd card ??

Perhaps in the case of "ringtone [...] not playing correctly, lags and stutters...", it could be not a no-reading but a a bad-reading by mediaserver ?

BTW, don't you think it could be one clue ?