yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] jornbjorn:
battery is a touchy subject it seems ;)

Ofcourse battery drain is not an issue... just like fuel consumption by your car is not... but if my car starts to use 3 litres per 10 km i think i will call it an issue.

We like what you guys are doing here, but calling the battery usage of this rom a non-issue is not completely true.
[Galaxy S I9000 Android Development] FadeFx:
Regarding battery drain, eventually the development should check what hardcore did to speedmod kernel to optimize it. He managed to get froyo to have a drain of 1% in 8 to 10 hours of standby by optimizing the compiler options and some more things. I guess atinm and codeworkx are aware of that and already tried all of this stuff, but just in case they did not, i wanted to remind them...

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

tapatalked
[Galaxy S I9000 Android Development] josteink:
Blah. I like CM as it is and have no intentions of replacing it with anything else at the moment. Go to the Bahamas or whatever. Do as you like. We're still pretty happy here :p
[Galaxy S I9000 Android Development] GeoH2102:
Settings -> About Phone gives:

2.6.35.7-02823-gb401116atin@waltest9-ma #1
[Galaxy S I9000 Android Development] FadeFx:
If your car uses normal ammount of fuel its no issue, but if it uses 15liters where it used 7 before, it definitely is an issue...

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

tapatalked
[Galaxy S I9000 Android Development] DarKprince87:
you never fail?

you always do the right thing?

your system is never crashed?

a good software is able to catch/solve all exceptions and avoid unsafe situations. If you're too stupid to understand this that's not my problem.

I did not said to do that different, I just suggested to do it BETTER
[Galaxy S I9000 Android Development] dhurk:
I flash jpu and than speedmodfroyo kernel for cwm.

But flashing cm7 kernel after i choose reboot now and nothing happened.What is wrong?
[Galaxy S I9000 Android Development] jornbjorn:
why did you just repeat what i said?
[Galaxy S I9000 Android Development] codeworkx:
reboot again
[Galaxy S I9000 Android Development] FadeFx:
Sorry, seems i don't read propperly...

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

tapatalked
[Galaxy S I9000 Android Development] DarKprince87:
@codeworkx : what do you think about my suggestion??
[Galaxy S I9000 Android Development] dbraaker:
imho battery drain is an issue. cm wont give me more than 8 or 10 hours of really mild use. gb stock roms (are crap but atm necessary at least for me) give me more than 3 days with the same usage pattern. actually battery drain is the only reason for me not to use cm as my daily driver as i need the phone to work, its not just a funny gadget for me. if you are at work for 16 hours or more including flights or train trips you cannot be sure to find a power connector for an hour every 6 hours. just my 2 cents
[Galaxy S I9000 Android Development] dhurk:
I did 50 times that :)

But phone rebooting and galaxy s logo appears after cynogenmod logo appears

After this process delaying
[Galaxy S I9000 Android Development] codeworkx:
most people getting their first smartphone will react like this:

"Wow, amazing."

And they'll hardly play around with their phone because it's something new which must be explored. After 4-5 hours it's empty and then it starts:

"BATTERY DRAIN BATTERY DRAIN BATTERY DRAIN BATTERY DRAIN!!! CRAP CRAP CRAP CRAP CRAP".

Same as:

"I NEEEEED LAGFIX, LAGFIX, LAGFIX, LAGFIX!!!!

EVERYTHING NEEEEEEEEDS LAGFIX!!!!

GIMMMMEEEEEEEHHHHH LAAAGFIIIIIXXXX!!!!!! NAO!!!!!!"

That's what i meant.
[Galaxy S I9000 Android Development] rschenck:
If I fail or fail to do the right thing due to my own carelessness, then I take responsibility for it and I don't expect the software to protect me from myself.

Cm7 for sgs is still an "at your own risk" beta and at any rate cm7 is designed for advanced users. As the first post of this thread states, if you have to ask if this ROM is for everyday use, it likely is not for you.

If you are too stupid to follow simple instructions, that is not my, or the devs, problem.
[Galaxy S I9000 Android Development] pcboyy:
Suddenly i have no network n lots of FCs. I check imei n its corrupted. A reboot doesnt solve it. Flasing nightly doesnt solve. The only thing i can do is reflash initial which wipes everything :(
[Galaxy S I9000 Android Development] codeworkx:
We have to make sure that the recovery is running on ~ 20 different devices.

It's not everytime as easy as it sounds.

It's no problem like it is. If you've deleted the initial zip, you'll stuck at a bootloop if you've fuct your system. But this would happen anyway. 3-button recovery is the only thing you can do then.

But maybe we can add a message in general if extendedcommands fails.
[Galaxy S I9000 Android Development] Uss_Defiant:
Yeah, would be great if someone looked into this plz, sensor values are not working.
[Galaxy S I9000 Android Development] AmTx:
So,ok.

1.Which kernells support CM7?

2.What google pack is stable? I`ve downloaded 29\7 ,it always crashes.

3.Is it possible to make led notification working on CM7? If yes,how?
[Galaxy S I9000 Android Development] siky_dude:
works very good

you dropped your phone and light sensor gone poof :D
[Galaxy S I9000 Android Development] pfannenwender:
im on nightly #89 and had a weird bug just now.

there where no transition animations.

tried to change it via the settigns menu and spare parts.

nothing happened.

a few minutes later i used the phone again and the animations were back.

dont know what happened o_O
[Galaxy S I9000 Android Development] Uss_Defiant:
Given that other people notice this bug, but you keep on coming up with non helpful remarks, I must wonder why....

Pray tell, what values is your light sensor outputting?
[Galaxy S I9000 Android Development] siky_dude:
try custom kernel...see if that helps...:)
[Galaxy S I9000 Android Development] Red_Vex:
Someone received a mail from Steve Kondiak with the closed source driver code as attachment? :D
[Galaxy S I9000 Android Development] Uss_Defiant:
I did, why won't you answer my question? :(

what values does your non-broken light sensor give you?
[Galaxy S I9000 Android Development] Bork84:
1. fugmode , neo , glitch - find the posts in the dev section

2. use the gapps-gb-20110613

3. only with a custom kernel

next time use the search button!!
[Galaxy S I9000 Android Development] cHarOn99:
Hahahahaha that would be awesome :D ;)
[Galaxy S I9000 Android Development] fackamato:
Sure, but CM7 comes with the free version. The free version in the market is way faster than the free version in CM7. <- my point

Perhaps the one in CM7 just needs to be updated?
[Galaxy S I9000 Android Development] KennyLegend:
Dude go and read a bit......all ur questions have been done to death now.

Only 3 custom kernels work on cm7.

Glitch (which is out of date), fugu and the best one which is platypus (Neo).

With neo kernel

.. led notification works out of the box without bln app. Create shortcut on homepage by long press and set notifications by app in miscellaneous settings.

Next time use the search button
[Galaxy S I9000 Android Development] DROCSID:
Glitch version v12 beta is not that old imo?
[Galaxy S I9000 Android Development] gaspernemec:
What settings for voodo color you use on neo kernel, because my colors are totally screwed :/
[Galaxy S I9000 Android Development] adams.alex:
That would be the most wonderful news this year, but dreams not become true very often :rolleyes: An who knows maybe there is a Santa.
[Galaxy S I9000 Android Development] KennyLegend:
Didn't see v12 to be honest ..sorry
[Galaxy S I9000 Android Development] madd0g:
Yeah, I went back to stock CM7 kernel without led notif. because of ugly Voodoo Colors. Even supercurio said it sucks balls :]
[Galaxy S I9000 Android Development] KennyLegend:
Well dammit...would u believe I've just been offered a Galaxy 2 at a price I can't afford to pass up !!!

Shucks ....guess ill just have to go see what roms are available !!! :)
[Galaxy S I9000 Android Development] fackamato:
If he really said that, then he should grow up.

Voodoo colors are great. But they're not for everybody, because apparently not all screens behave the same. Without it, my screen looks like some pastel colored piece of ****, so because Samsung ****ed up (again), I need it to have a phone that's not retarded.
[Galaxy S I9000 Android Development] madd0g:
There was a discussion about it already in Semaphore kernel thread : http://xdaforums.com/showpost.php?p=16390745&postcount=1372
[Galaxy S I9000 Android Development] atinm:
CM7 is already available on it . . . and has been for a while. Only major thing still missing is bluetooth audio. http://xdaforums.com/showthread.php?t=1176411
[Galaxy S I9000 Android Development] aoprea:
siky_dude i think your phone is damage ... beacause everybody know that from the ~ #50 - #60 nightly (i dont remember witch) the light sensor driver generate inaccurate values....

the luminosity is too low on auto brightness compared with sammy rom
[Galaxy S I9000 Android Development] fackamato:
thx :) mofo'ing 10chars
[Galaxy S I9000 Android Development] gaspernemec:
I haven't said that color sucks, actually I found that they are preety vivid. But I am asking of anyone got good color configuration.
[Galaxy S I9000 Android Development] gjroeleveld:
I 'm getting 10, 160, 225, 320, 640.. and that's about it with the lights around the house..

From the lightsensor that is. Stock n88
[Galaxy S I9000 Android Development] KennyLegend:
Yes....so I see !! And I think cm7 will be my rom of choice too since I'm loving it on my sgs at the moment.
[Galaxy S I9000 Android Development] w1ll1m:
Bluetooth problems persist in the latest nightly. Currently on GB Bootloaders so that may be an issue, any help?
[Galaxy S I9000 Android Development] FadeFx:
can you try fugumod and check if the problems persist? i dont have any problems with bluetooth at all, can pair connect and use several devices.
[Galaxy S I9000 Android Development] mbutandola:
At last I don't feel lonely anymore lol. Think I just have to go for an sgs 2 lol.
[Galaxy S I9000 Android Development] F_R_I_T_Z:
Atinm!!!

Maybe a stupid question..

I'm playing with last aries kernels paths from repos with mine G9000.

One that give me atention was the mfc and camera things. After I changed one obvious things like the bitrate from media_profiles.xml main camera to record video. Something scare me. I'm already in bitRate="30000000" And video still fine same in dark conditions. So! Mine question. This is a real situation? Someone more tried this? OR its a bug someplace where the bitrate string by itself is not working ?

Another thing. and related!

Independent he bitrate limit be or not working.

The video quality record after the sams universal driver and the parser. seems the video quality become worst. A LOT WORST. More granularity.

Obvious all you guys are aware of this. But I'm curious about developers comment side ( since we don’t have our morning breakfast read from developers channel anymore).

I do some changes and tries but mine code skills are far limited to play more hard with with kernel and driver stuffs to contribute by myself in a useful way.

Not speaking bad or relating a bug. I'm just curious about this points.

Thanks..
[Galaxy S I9000 Android Development] KiRAdot47:
Sorry to bother again but any way to play hd video? Except dice player?

I've tried all and useless, max 10 fps :/

Cm #88 stock kernel
[Galaxy S I9000 Android Development] KennyLegend:
Edit ...having trouble getting to cwm from rom manager now. rooted with speedmod. For some reason I can't post in s2 q&a thread.

Nevermind....ill figure it out.
[Galaxy S I9000 Android Development] siky_dude:
neo kernel has a stock color kernel too...

check it out :)
[Galaxy S I9000 Android Development] Necrolust:
A quick question,

Any reason why ADB won't find my phone? Its never actually worked for me on CM7, ever, and its only bugging me now. Works fine on a stock rom.
[Galaxy S I9000 Android Development] nagi603:
Wake (call) problem?

Hi!

I've been using the nightlies since 77, then got to 80 the day it was released. JVR modem, and I think still JVK bootloader. (flashed from JVK to JVR to Nightly) The kernel is the one that came with the nightly. I've installed voodoo control app, proximityOff and setCPU.

My problem is, whenever I'm called, (viber / regular) the phone just vibrates, and at first, I can't even wake it. Then it wakes, but is quite unresponsive. As if something keeps hogging the CPU so hard it can't really take the time to process the inputs. Response time is measured in the seconds, and frankly, the best stopgap solution I've come up with is just letting the caller hang up, then call them back, because that works. I did manage to take a call, and it worked OK, but this is quite a big problem for me. Not that I have that many calls regularly, but stock never played this with me.

This also just happened to me with a (Alarm Clock Plus) clock alarm.

I'd appreciate some help, will try disabling/uninstalling setcpu, I'm not sure if updating the bootloader would help in any way. Tried cleaning Davlik & cache, and after that, I got the alarm issue above.

Slightly related, maybe retarded noob question: I can get to the download mode for Odin/Heimdall using the 3 figer salute, and also to the recovery menu from the reboot options and the ROM Manager. But can't (or haven't figured out how to) access the recovery menu without the app/reboot option. Am I just being blind and is there something I forgot to do?
[Galaxy S I9000 Android Development] jbuk__:
@Necrolust If you're on windows, you need to install the Nexus S USB drivers. See http://developer.android.com/sdk/win-usb.html
[Galaxy S I9000 Android Development] montymintypie:
Just one more question... When I ran out of space on /datadata, there was no warning whatsoever. It is also impossible (as far as I can tell) to find out the free space in /datadata without jumping into the terminal.

Are there any plans to make the phone think of /datadata as the internal storage? That way, it might mean the OS's built in 'low data' warnings might activate before the strangeness starts to occur.
[Galaxy S I9000 Android Development] siky_dude:
heard someone with the same problem..try reinstaling viber and uninstalling proximityoff(idk why that would help, but give it a try)

if you flashed from jvk to jvr with odin, then you have jvr bl, not that taht would matter...just sayin`

going to recovery : vol up + home + power :)
[Galaxy S I9000 Android Development] mbutandola:
Finding the right neo kernel is not that straight forward. There seems to be multiple threads and some look out of date. But well, this is not the place to discuss this. Will carry on my research :)
[Galaxy S I9000 Android Development] uberberben:
Hi,

Is there any way to solve wifi disconnect problem? Sometimes my wifi gets locked up after waking up phone and it cant connect to last known AP. Im using option to turn off wifi after some time after locking phone.
[Galaxy S I9000 Android Development] nagi603:
Oh, volume UP it is... so my reading comprehension still sucks :)

I did not check the "flash bootloader" option in odin, and the "baseband version" still shows JVK, hence my unsure claim about the bootloader :)

Will try testing it in the morning & also fumble with the #89. Thanks for the tips & help!
[Galaxy S I9000 Android Development] siky_dude:
huh?...its just one thread...o_O...but you are right...another time another place...come to the platypus irc and we will talk :)
[Galaxy S I9000 Android Development] mbutandola:
Link plz. thx

Edit: Found it
[Galaxy S I9000 Android Development] siky_dude:
there is no need to chack flash bootloader :)...it will flash anyway

and baseband is radio/modem which is jvk i presume..

it doesn`t say anywhere what bootloaders you have :)
[Galaxy S I9000 Android Development] Francois88:
I posted something similar a few days ago; someone replied that it was perfectly reasonable behavior for the os to crash/become unusable when the user fills that partition through apps. I didn't bother arguing, but I wholeheartedly disagree. As to see the paritition's usage easily without needing the terminal, you can get "Partitions Info Lite" on the market. My biggest culprits were "Ivona text to speech", Tweetdeck and all my browser's image caches.
[Galaxy S I9000 Android Development] beekay201:
if you're on linux you need to check for vendor id with lsusb, create udev rule under /etc/udev/rules.d/ like so and restart udev:

# # Google
SUBSYSTEM=="usb", SYSFS{idVendor}=="18D1", MODE="0660", GROUP="adbusers"

if it's giving you '????????? no permissions' when entering 'adb devices', restart adb server with root. oh and add your username to group 'adbusers', create it if needed.
[Galaxy S I9000 Android Development] davidmore:
idVendor for SAMSUNG is "04e8" and you can add permission to all if you want (MODE="0666"); (I don't use GROUP prameter because i have only a group )

SO the result is:

SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"

If after restart udev (command is: /etc/init.d/./udev restart) the "adb devices command" give you the same answer "???????? no permission" then do:

adb kill-server

adb restart-server
[Galaxy S I9000 Android Development] madd0g:
Can you post it ?
[Galaxy S I9000 Android Development] PartyVirginX10:
http://xdaforums.com/showthread.php?t=1053304
[Galaxy S I9000 Android Development] ristokoo:
There's been messages about the light sensor every now and then. I just noticed mine seems to have something wrong. I get either 10 or 160 lux, nothing in between. And the automatic brightness does nothing to screen brightness. I just installed #90 but had the same with #88, probably also with earlier nightlies.

Any suggestions?
[Galaxy S I9000 Android Development] trenje:
I don't see one without Voodoo Color.
[Galaxy S I9000 Android Development] madd0g:
Yeah, that's the main thread, but no stock color kernel there (yet). I found it on irc though as a public test.
[Galaxy S I9000 Android Development] siky_dude:
Stop talking about custom kernels in cm7 thread.
[Galaxy S I9000 Android Development] trenje:
tencharacters
[Galaxy S I9000 Android Development] mbutandola:
Hi guys,

Could anybody tell me what could cause deep sleep and how to solve it?

I'm on #89 and sometimes I have to pull the battery and reboot as it won't wake.

Thx.
[Galaxy S I9000 Android Development] Mothamoz:
Deep sleep is a good thing, it means your battery usage is on an ultimate low during standby.

The thing you are experiencing is called sleep of death. Probably caused by your OC/UV.

Try looking at that, removing any OC/UV and see if it's still happening.
[Galaxy S I9000 Android Development] mbutandola:
Thx. But I haven't played with oc/uv yet coz I don't quite understand it.
[Galaxy S I9000 Android Development] FadeFx:
Thats normal, the light sensor reports in steps 10, 160, 225, 320, 640... the only problem atm is that the lightsensor got damned slow in one of the last 10 nightlies, this is no problem most of the time, but it is when u lock the screen under dark conditions, and unlock it in bright conditions, then it takes up to 10 seconds while the sensor reports -1 which i think means "disabled" untill he starts to report propper values.

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

tapatalked
[Galaxy S I9000 Android Development] encho:
Is that a bug or we have to live with it? It seems those steps are to big.
[Galaxy S I9000 Android Development] rschenck:
I am pretty sure that the Devs will not be changing the settings for auto brightness, or at least not due to user commentary.

Auto-Brightness is a feature like Voodoo Color...where you just can't please everybody. As soon as the Devs respond to the sudden flurry of fairly kneejerk complaints about the Auto-brightness by adding more increments or changing the ones that exist, a whole bunch of new kneejerk comments, complaining about the new settings will emerge, running the same gamut as the recent batch, from "Dood, y iz ato-bright thing busted...U SUK" to "After analyzing my screen output using a Sykes-Fairburn Ocular Chromatosphere configured to a perfect set of parameters as ascertained by myself, I can attest to the fact that the Auto-Brightness settings are completely wrong for optimum viewing, in ways that your feeble minds will never comprehend. Just accept that it is so. Fix this now, or Daddy will spank".

To be honest, it is simply not worth the trouble, since the current settings seem fine for the majority. Beyond that, I don't think I have ever had a rom installed where the auto brightness wasn't a bit odd and jerky. Therefore I seldom use it, preferring to set the Brightness fairly low and then, when there is a need (here is the innovative part), manually adjusting it.

I know that having your phone automatically adjust everything without you having to do a damn thing is cool beans and very attractive to some, but it can all too easily go Brazil on you, and then you have your toast in your coffee cup and Bob Hoskins in your ducts.

No one wants that, now do they? Now lets talk about other things, such as battery drain and the lack of ponies in this ROM...or Daddy will spank.
[Galaxy S I9000 Android Development] ktuluz:
I agree about the auto brigthness I find I have more contorl by using status bar brigthness control. Change the brigthness. To either low or high .. all i seem to need anyway.

I must say I am loving cm7 again .. very much an improvement over Sammy roms .
[Galaxy S I9000 Android Development] madd0g:
Since I come freshly from a stock SGS ROM, I find CM's auto brightness brilliant. Samsung's never was on full brightness except on really hard sunlight, if I covered the phone with my hand it went back to lower setting, which is ridicolous. Here I can at least change the values myself. I think that only 3 brightness settings are relevant anyway, low for inside the house/dark (20-50), then 100 and then full brightness (255). Lets face it, AMOLED is useless on the outside, specially if there's sun, so nothing less then 255 is limiting.
[Galaxy S I9000 Android Development] ristokoo:
Oh yes, my bad, the sensor actually works. I was sitting in too dark a place when I tested the sensor, a very rainy day around here :D

It was the slow auto-brightness that tricked me into thinking something was wrong. But I agree with rschenck, this is a very minor thing and a matter of taste. I'll try manual adjustment.

Edit:

By the way is this brightness thing kernel related so that a custom kernel could have different settings from stock kernel?
[Galaxy S I9000 Android Development] suua:
Back to CM7 :) i must say that CM is much smother than MIUI :)
[Galaxy S I9000 Android Development] encho:
Yes, it could be just the speed of it. Otherwise as you say it's just a minor issue. Although I could swear that I had more steps some time ago, maybe early nightlies.
[Galaxy S I9000 Android Development] melorib:
I remember when Hardcore started tweaking brightness on speedmod kernel, big war, all of a sudden no one was happy, before no one complained... :rolleyes:
[Galaxy S I9000 Android Development] FadeFx:
you are right melorib, but i think most of what some felt as complaints, were more like bugreports. and the only thing hardcore did change was what we can do by ourselfs in cmsettings. however, the steps the lightsensor reports were the same from beginning and will never change as that is a hardware limitation. the only option to make brightness go up faster is to set up the steps like 0-24, 25-174-175-239... so it reacts qite fast to more light, but it will take longer to lower the light,which is no problem normally...
[Galaxy S I9000 Android Development] sago62:
next changelog: Modified stock MFC settings to match Samsung

I've found this to Improve Somewhat 720p recording, but in the worst

homes, it will just 8MB free RAM for the more userspace.

Requires kernel patch

.... I feel good, what you say?:D
[Galaxy S I9000 Android Development] pawitp:
I'd say that it's not what you're hoping for. (and how the heck did you mess up my message?)
[Galaxy S I9000 Android Development] sago62:
.... I'm sorry .... wait!:(

...mess up your message?? i don't understand....