yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] siky_dude:
Closed source
[Galaxy S I9000 Android Development] jscurtu:
• Period! ;)
[Galaxy S I9000 Android Development] jbdroid:
I have not experienced this yet. I left it charged 3 times now to full overnight and idle battery drain is still normal (meaning battery still lasts for about 2 days). But may not really CM7-related, after flashing #80 to #85, fancy widget eats up battery like a sumo wrestler. On #77 it wasnt like that. Overall though. CM7 is way better than stock roms now, from battery life to UI speed. ;)
[Galaxy S I9000 Android Development] melorib:
#84 had front camera image times 4 and poorer battery, #86 has image sideways again... :confused:

Going backwards now... :rolleyes:
[Galaxy S I9000 Android Development] beekay201:
i don't think it's about MIUI or CM7; imo it would be nice to have such a feature in CM7. but it's not totally necessary, of course, i was only making a suggestion, not really a request. some prefer to use some 3rd party app to do it, fine, that's their choice.
[Galaxy S I9000 Android Development] Funnnny:
It's not just about that feature, CM7 still have a lot of work in term of usability. Look at how MIUI done it, CM7-based and they did alot in GUI and feature.

I would love to help the team, but I hate Java so much (lol)
[Galaxy S I9000 Android Development] zacharias.maladroit:
just call it "Super-Standby" :D

thanks for the info !
[Galaxy S I9000 Android Development] melorib:
Super ****-by... :(

#86 drained 22% in 4 hours iddle, strange that it said DISPLAY 60%, it was off... :mad:

Re-installed #80, status bar force closed, flashed again, same result...

Back to #86, #80 again, same ****... :confused:

So I have to be back in #86, I already deleted #84, and it takes over 2 hours to download... :o
[Galaxy S I9000 Android Development] siky_dude:
You really need to calibrate your battery.
[Galaxy S I9000 Android Development] melorib:
What makes you think that all this hapened because my battery is not calibrated... :confused:
[Galaxy S I9000 Android Development] KennyLegend:
I think melorib knows well about calibrated batteries ....he's flashing roms quite a while..... ;)

KEN
[Galaxy S I9000 Android Development] CROrION:
this rom is gr8 for me, here is my battery life, if only there is some way to get phone signal more stable...
[Galaxy S I9000 Android Development] siky_dude:
Flash another modem...see signiture
[Galaxy S I9000 Android Development] w1ll1m:
Bluetooth isnt working on n85, doesn't turn on. Other than that fantastic rom.
[Galaxy S I9000 Android Development] siky_dude:
the 22% drain in 4 hours :)

and you mentioned you flashed 84 then 86 then 84 again then 80...or something like that...

that messes up your battery :)

just sayin` :D
[Galaxy S I9000 Android Development] Bork84:
I had Bluetooth working fine on #85. still working fine on #86.

flash #86 and see if it works out...
[Galaxy S I9000 Android Development] shayvasa:
hi,

i have with a problem with the market, it auto updates it and when it updates the market to the newer market i get fc, i cant do anything. and so i have to downgrade but then it upgrades it again by itself.

is there any solution for this??

thanx
[Galaxy S I9000 Android Development] francomile:
Had no problems either with #85. Worked fine for me.

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] mohitdabbaail:
Freezing the

Market Updater

using Titanium Backup may solve your problem.
[Galaxy S I9000 Android Development] shayvasa:
ok, but how can i get the new market to work?
[Galaxy S I9000 Android Development] benjieg:
I know this thread isn't about launchers, but I'd like to recommend Zeam. It's lean and mean and is the perfect complement to the speed of CM7.
[Galaxy S I9000 Android Development] ktuluz:
Yes +1 Zeam + CM7 Works well for me. Would be nice it it would check global orientation setting for landscape mode, instead of having to set it in app settings... thats my only beef
[Galaxy S I9000 Android Development] ock:
iirc this behavior may be related to the change that reports battery life as a % of overall (or something like that ;) )

That change stopped the reports of "my battery doesn't charge up to 100%" but one effect is that from 100% to about 97%, the drop is slightly faster.
[Galaxy S I9000 Android Development] montymintypie:
On #86, getting massive battery drain in Maps. This is after cache, dalvik cache clear and flashing #86. Also fixed permissions. Also interesting to note: Wifi sleep is set to 'never when plugged in' but did not switch off the entire time the phone was unplugged and screen off.

Maps seems to be keeping the phone awake and battery sucking, I think it's related to Latitude (which is switched on). Thoughts?

Oh, and I'd post a logcat, if it wasn't filled with so much useless junk.
[Galaxy S I9000 Android Development] katsooba:
flashed 86 the minute it was out - i had only 1 charging cycle

1% lost in 9 hrs :)

i dont know what u guys talking about heh
[Galaxy S I9000 Android Development] FadeFx:
Yesterday i charged to 100%, then unplugged imidiately and battery drain is normal 1%/2hrs which is acceptable for me, only to 97 it drooped relatively fast. Will try to charge overnight to see how it behaves tomorrow...

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] rschenck:
Latitude is almost certainly the culprit as it is a long standing battery hog. Disable it and you should be fine. Trust me, you are better off without your friends knowing where you are.
[Galaxy S I9000 Android Development] montymintypie:
I still like to know where they are though! :P I've disabled location sharing for now, hopefully that reduces the drain.
[Galaxy S I9000 Android Development] rschenck:
Probably all together, talking about how much they don't like you...best if you don't know.
[Galaxy S I9000 Android Development] katsooba:
Anotjer issue i forgot to mention on all the latest cm7s i flash, after flash, it doesnt matter what modem i use, i get no signal, reboot doesnt help, reflashing a modem doesnt help, and when i scan for networks it find all the networks around EXCEPT for mine hehe.

Is there any reaaon for that?

Also another issue - tried connecting bt at the car, it froze the settings menu, gave a fc and dropped my cell signal.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Zatta:
You use the app Viber? It kept my wifi on all the time.. annoying. Uninstalled and everything was fine again. Now using skype.

Tapatalked u see
[Galaxy S I9000 Android Development] gaspernemec:
Yeah, dont care about that few % drop after you unplug your phone, its normal, that protects battery from overcharging and makes its life longer....

As for #86 i ran into bootloop after flashing it, however after re-flash it was all good, dunno it could be my mistake, so i wanna know if any of others ran into bootloop as well....
[Galaxy S I9000 Android Development] melorib:
The abnormal drain happened before all the flashing, thats why I flashed...

Status bar force closing when flashing #80, regardeless of wiping cache, fixing permissions, flashing #86 again, etc, means #80 after #86 currupts something, wich is a shame, because #80 was the best nightly so far... :rolleyes:
[Galaxy S I9000 Android Development] shi.indra:
New Market FCs

Exactly same problem!!

Instead of freezing an update cant the problem be fixed.

It was working fine when I ran the leaked version. Later did a clean update and then old market came back.
[Galaxy S I9000 Android Development] gaspernemec:
that happened to me on nightly #64...try performing factory reset and reflash CM7, that solved my problem
[Galaxy S I9000 Android Development] FadeFx:
I don't care about that, but i do if my battery drains 3-4%/h all down to zero if i charge overnight...

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] montymintypie:
Ahhh, the bastards -_- Shall do...
[Galaxy S I9000 Android Development] kraven001:
Got today the Android OS bug.

The "suspend" process drained about 10%/bat/hour. Checked logs in System Panel / Watchdog and the suspend process was constantly at 10% CPU usage.

There is no scientific way to reproduce this - didn't get it in a while - but it seems certain games have something to do with it.

Changed the settings in Watchdog to notify when system processes take more than 10% of CPU - but I'm not exactly sure if this will trigger alerts when it happens maybe I need to buy Watchdog Pro and put CPU threshold for system processes at 1% and exclude things that work well and usually eat a tad more CPU.

A bit annoying, woke up with 20% battery and I will be away from a charger during the day ...
[Galaxy S I9000 Android Development] rschenck:
Two points...

First, I would take an educated quess that both the "sudden battery drain" issue and the Android OS bug are due, at least in part, to some kind of conflict in apps and/or settings that suddenly gives your phone a problem to labor at, endlessly, when it should be idle.

This view is supported by the fact that numerous users suffering from those two mysterious maladies have said they solved their problems, at least for awhile, with a data wipe. This would obviously remove any kind of conflict and allow the phone to stabilize.

I would suggest that for now, anyone who has the Android OS bug or radical battery drain try a data wipe and see if that helps things.

Secondly, just a question I have wanted to ask for awhile, for everyone who complains about leaving their phone on the dresser at night and having it drain off 20 percent while idle. Is there a reason why you don't charge the phone while you are asleep, therefore having a full charge in the morning despite whatever idle drain issues you are having?
[Galaxy S I9000 Android Development] montymintypie:
See, I also don't understand this kind of mentality. I know my smartphone, being amazing, drains battery at the best of times. So even if it's at 70-80% at night, I always put it on the charge before I go to sleep. That way, if there's any issue whatsoever, I can at least work it out before my phone kills itself.

:confused:
[Galaxy S I9000 Android Development] melorib:
Maybe, but I have been flashing almost every nightly since before #40, and this never happened... :confused:

Over night it drained 7% battery, back about 20 nightlies in battery drain... :o

I dont feel like installing everything back, even with Titanium, will wait for next nightly, hope they correct front camera and it is as good as #80... :rolleyes:
[Galaxy S I9000 Android Development] jodmos:
I had status bar force close from #80 onwards, put it down to theme I was using (ice cream theme)- took it off, no force close. Put another nightly on (82 or 83) applied theme again - status bar f/c. Have ditched that theme and everything is ok.
[Galaxy S I9000 Android Development] melorib:
I moved back to CM7 because it is the only ROM that will run that theme, I use the theme from the first flash, only now I had this problem, and going back to a nightly where it worked fine, sorry, I dont buy that... :rolleyes:

If CM7 stops supporting Honeycream I move back to Samsung ROMs...
[Galaxy S I9000 Android Development] kasper_h:
I have the android OS bug sometimes as well (once every 2 weeks or so). Mainly if I've been running a range of apps. However, for me a simple reboot was/is always enough to solve the problem...so before wiping things, first try whether a simple reboot already solves it.

In airplane mode at night, my battery drops only 2-3% since I use GB bootloaders. Since then, I've stopped charging overnight...(although I didn't use it that often on froyo bootloaders: I often just turned the phone off - still have an old-fashioned alarm clock).
[Galaxy S I9000 Android Development] jaju123:
Nightly 87 is out.
[Galaxy S I9000 Android Development] rschenck:
Looking at the changelog, unless you need CGI Wireless APns, this may be another one to skip.
[Galaxy S I9000 Android Development] rschenck:
If I am right, and the problem has its genesis in some kind of app conflict, then it makes sense that rebooting could solve it...anything that kills all background processes and starts again at zero should have that effect.

Therefore yes, first reboot. If it continues after the reboot then the conflict may be from some application running at startup...so then consider a data wipe.
[Galaxy S I9000 Android Development] jaju123:
What happened to all the merges yesterday like oc/UV etc? Are those just not in the changelog or not there at all?
[Galaxy S I9000 Android Development] rschenck:
When they actually go into the repo they will appear in the changelog. It is a process and it can take a little time, especially when they concern the stock kernel.

Read the changelog, watch the skies, clap if you believe in fairies.
[Galaxy S I9000 Android Development] FadeFx:
Ha, got one....

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] melorib:
Connected USB, copied #87 to sdcard, unplugged, battery 14%, this #86 is crazy... :eek:

Have to wait to charge to flash #87, hope it is better... :rolleyes:
[Galaxy S I9000 Android Development] siky_dude:
Told you...uncalibrated battery.
[Galaxy S I9000 Android Development] melorib:
Only with #86, I would say it is uncalibrated nightly... :p

By the way there is no such thing as uncalibrated batteries, it is a lame excuse for ROM problems... :rolleyes:
[Galaxy S I9000 Android Development] kraven001:
It is in fact triggered by some apps. But doing a wipe and installing the same apps will most likely lead to nothing (for example for me it seems that the Spirit game triggered it; installed it yesterday, played it for a while, went to sleep and boom in the morning Android OS bug). Probably if I installed only general apps (Facebook, Twitter and other small things) I would never see this, but I have diverse apps installed, which I like and want installed. That's why I'm trying to monitor things better to be notified when this happens so I can reboot the phone and get the system to stabilize.

I would say is a conceptual bug, to have some sort of process that for whatever reason is not able to do something, to just pool the resource endlessly and drain power and use resources. I can give the benefit of doubt that there are some "drivers / proprietary" software out there that cause this alongside with poorly written software but if you "brag" you designed an operating system these things should be there and implemented properly - thus I blame google on this one (we are at version 2.3.5 after all). I would prefer to be in complete control and manage the situation (notifications about things not working properly). After all embedded systems are critical systems and they should work properly - some say maybe someones life depends on that, but I don't want to go there, it's a phone after all.

Me for one don't keep the charger in during the night since I don't want to always be at 100%. These batteries need cycles to work properly thus I give them that. I don't see a reason to charge when at 100% especially when the damn thing should not drain more that 10% during the night let's say which should be acceptable and it's the case when random google bugs don't hit the OS.

To sum it up I would be happy if I could systematically reproduce this issue, look at logs, etc. For now I will stick to having Watchdog monitor system processes that jump over 10% (and exclude the Andorid System which handles calls / syncs which requires processor power from time to time), will see how that scales (hopefully it will catch processes like suspend and others misbehaving - I can already see in the System Panel logs that suspend drained power since it's the top most cpu intensive app, and it has a constant 10% cpu usage during the period).
[Galaxy S I9000 Android Development] zacharias.maladroit:
^^

nice one
[Galaxy S I9000 Android Development] siky_dude:
o_O
[Galaxy S I9000 Android Development] beababe:
Hi everyone!

Im currently on InsanityCM and miss the DSPmanager app :p anyone here who could pull the apk and upload it? :)

PM me or quote me if posting in this thread!

Regards.

EDIT: http://db.tt/Tx9p4el
[Galaxy S I9000 Android Development] bajica:
After 7 days of stock nightly #80 with GB bootloaders and JVR modem have to say battery is great for me, idle drain is same as stock samsung roms, did 3 full discharge cycles and battery is performing like a champ, will stay on this one for another 7 days and see if there is any new change (camera) :) worth flashing
[Galaxy S I9000 Android Development] gaspernemec:
Are you on GB bootloaders?
[Galaxy S I9000 Android Development] melorib:
After #80 there are some files related to battery charge in system\media folder, so something changed, and it is afecting the battery usage somehow... :rolleyes:
[Galaxy S I9000 Android Development] pawitp:
Media files affecting battery usage. :eek:

They are for low power mode (charging while off) which is being enabled.
[Galaxy S I9000 Android Development] KennyLegend:
I have great battery life on #86. ...

1.5 days up so far and currently showing 19%. Medium usage...wifi with xda, FB..emails etc. few sms and calls.

I'd suggest wiping data/ factory reset maybe ?

KEN
[Galaxy S I9000 Android Development] ktuluz:
Is there an ignore button in this.forums? :)
[Galaxy S I9000 Android Development] FadeFx:
Yes, but i am pretty sure it has nothing to do with them, as i don't suffer that drain if i stop charging before the battery is at 100% so for me now its best to charge to 97% and unplug then. However, i can not always sit there and wait for tasker to remind me to unplug the phone.

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] francomile:
Sure sure...Is so hard to dowload the rom and extrac the app by yourself??

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] rschenck:
There may be, to be honest I have never explored the option.

That is because CM7 is based on a spirit of cooperation, however strained that may be at times. Though the regulars here may tease newbies at times, even swinging a flaming sword when the idiocy of oft-repeated questions gets to be too much, overall we are very tolerant and understand that everyone's input is needed to help improve CM7 as well as our general knowledge, even if we may not find all of it valuable to ourselves personally.

We are so tolerant that we even allow situations like this, where someone who has had CM7 installed for what seems to be about two weeks now and has contributed very little to the community beyond thanks thus far, appears to dis the views of a long-time forum member who has added a tremendous amount to the discussion and is always one of the first to help people with the thorniest of problems with his often unique insights.

If there were an ignore feature in this forum then likely a lot of people, myself included, would ignore you for such an apparent display of churlish disregard and false arrogance as seemingly calling for a veteran and valuable member of the CM7 community to be ignored over their input...after of course giving you a chance to explain yourself and apologize.

Which of course I am quite sure you would...and will...do.
[Galaxy S I9000 Android Development] pawitp:
Should be fixed soon. (Maybe the next prebuilt kernel or the kernel after that one.)

Actually, the feature does exist ;)
[Galaxy S I9000 Android Development] KennyLegend:
Nicely put ;)

KEN
[Galaxy S I9000 Android Development] KennyLegend:
Maybe I'm the one who's dreaming so ..lol :)

Have to admit I've never noticed it.

KEN
[Galaxy S I9000 Android Development] pawitp:
Nor did I. :)

It's one of the things you don't notice until it's missing. (And once it's missing, you'll probably blame yourself instead of your phone.)
[Galaxy S I9000 Android Development] siky_dude:
Just saw that on the teamhacksung account :)
[Galaxy S I9000 Android Development] beekay201:
LOL you wish it was so. It's not. Like Pawit said, they're just media files. Take a look at the file "extension": it's *.qmg, which, if you search w/google, you would find they are image, actually, qmage files, which are proprietary from what i've seen.

flashed #86, no issues as always. format /system really works wonders. you're calling on battery drain on #86. my phone lost 1% over 8hrs sleep. off to work now..:mad:

/me waits for new kernel
[Galaxy S I9000 Android Development] gaspernemec:
I asked if you are on GB bootloaders because battery had drains like you describe on froyo bootloaders....
[Galaxy S I9000 Android Development] frauhottelmann:
There is a new ignore function, just click a users name and then add him/her to your ignore list! This is part of Operation "Iron Fist", so it is relatively new!
[Galaxy S I9000 Android Development] k9nadav:
well put :cool:
[Galaxy S I9000 Android Development] rschenck:
Interesting...thanks.
[Galaxy S I9000 Android Development] beekay201:
when my phone gets to 97%, it's very fast to jump to 100%. never seen 99% battery full, nor 98. it jumps straight from 97 to 100. i unplug and it stays there for a little while..but if i reboot the phone, battery will come up with 96% most of the times. so i don't think it matters if you left it on the charger or not, or took it out at 97%: it won't keep charging no matter what. only if you replug.
[Galaxy S I9000 Android Development] melorib:
My English is not the best, but you guys should think before you say stupid things like this... :rolleyes:

I said that the new files in Media mean something changed in the new nightlies, and that change screwd things up, capisce... :confused:
[Galaxy S I9000 Android Development] melorib:
Thanks my friend... :cool:

This are the guys that dont read the posts, dont try to understand what others are trying to say... :rolleyes:
[Galaxy S I9000 Android Development] beekay201:
what? it didn't screw up anything! most of us are running #86 no issues. those media files are just images! that enable you to have images like this while charging with phone turned off.

edit: and Pawit (as you know, the dev responsible for that change) told you that they were preparations for Low Power Mode, those files under /system/media. media (audio, images, video). how can they mess with battery life??
[Galaxy S I9000 Android Development] melorib:
The files beeing there, and not beeing there before, mean something changed, or are they there for decoration... :confused:
[Galaxy S I9000 Android Development] beekay201:
dude, Pawit said like 3 or 4 times that as the change also needs updated kernel, until new kernel is released, that part of the code and files won't even be called/used. it's not for decoration, it's already there because it will be used in the near future.
[Galaxy S I9000 Android Development] beardedwonder:
FDS; PARA COM OS 'ROLLEYES'

(FFS stop using 'rolleyes')

Listen to the people who know what they're talking about and learn from them.
[Galaxy S I9000 Android Development] kinghorsey:
First attempt at gb bootloaders with cm7 and so far (the caveat here is I know my battery isn't calibrated yet) I don't have any noticeable improvement in battery life but the web browser seems to work a lot faster.

720p video is still choppy and there seems to be a longer delay in taking pictures with the camera.

I could live with most bugs but camera/video issues are disappointing.
[Galaxy S I9000 Android Development] beekay201:
dice player, no choppy 720p.

edit: if they're that disappointing for you, you know what you need to do right?
[Galaxy S I9000 Android Development] rschenck:
I think the issue here is that of course those files SHOULDN'T have any effect on phone behavior, especially as they are not part of the kernel yet...however what Melo is saying is that those files being added were the only change he noticed before his phone had a nervous breakdown of some kind.

Therefore they are a good place to start in figuring out what is going on. No one is saying the files actively caused the nervous breakdown, and as usual, Melo's phone seems to be having a totally unique problem, but perhaps something else is going on that was triggered by adding files to that folder.

Who knows..remember this is Melo's phone...who can ever guess why it does ANYTHING.