yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] ashwinds:
Is it just me or is Battery Use data a blank now (Settings -> About Phone -> Battery use)

PS: on 1083.

PPS: For others with a blank battery use screen, clear battery stats by deleting /data/system/batterystats.bin
[Galaxy S I9000 Android Development] purpleraintoxicity:
Works for me
[Galaxy S I9000 Android Development] purpleraintoxicity:
Latest stable vers seems great.

Smooth and the batt seems nice... ill give it a day ot two to test more

:-)

Meenwhile

3%/hr on wifi is nice after installation with no charge...
[Galaxy S I9000 Android Development] ashwinds:
For those with a blank battery use screen, clear battery stats by deleting /data/system/batterystats.bin
[Galaxy S I9000 Android Development] renaud:
r1121 should solve the wifi channels problem

I cannot test right now so, if someone can report..

<4>[ 37.353647] wl_iw_set_country_code: set country JP OK
[Galaxy S I9000 Android Development] zacharias.maladroit:
looks good (according to the commit) ! :)

haven't tested it yet

later, maybe someone is faster

but I'll test the channels 12, 13, 14 which are known to not have worked in the past

Thanks !
[Galaxy S I9000 Android Development] renaud:
Well, I assume they work, I just don't have any AP near me with those frequencies, but

eth0 14 channels in total; available frequencies :

Channel 01 : 2.412 GHz

Channel 02 : 2.417 GHz

Channel 03 : 2.422 GHz

Channel 04 : 2.427 GHz

Channel 05 : 2.432 GHz

Channel 06 : 2.437 GHz

Channel 07 : 2.442 GHz

Channel 08 : 2.447 GHz

Channel 09 : 2.452 GHz

Channel 10 : 2.457 GHz

Channel 11 : 2.462 GHz

Channel 12 : 2.467 GHz

Channel 13 : 2.472 GHz

Channel 14 : 2.484 GHz

Current Channel=3

EDIT: before, you could only see it till channel 11
[Galaxy S I9000 Android Development] KSTu:
quote

Front camera

Replace your old /system/lib/libcamera.so by this one: https://faramir.eriador.org/r/libcamera.so

Or use FadeFX update script: https://faramir.eriador.org/r/CM7_Camera_Update.zip

unquote

this trick also work on MIUI? :D
[Galaxy S I9000 Android Development] Christophe86:
i did it and miui wouldn't boot anymore.. but you can try it out for yourself :p make sure you do a backup of your whole rom before applying this fix, just in case.

let me know if it works.

Sent from my Samsung Galaxy S using MIUI.us 1.8.19
[Galaxy S I9000 Android Development] Zatta:
Did you also set permissions correct that time? If you don't it wont boot cm7 either..

Tapatalked u see
[Galaxy S I9000 Android Development] Mothatt:
Shouldn't be needed if using the latest MIUI ROM, from MIUI.us or MIUIAndroid.
[Galaxy S I9000 Android Development] toddmworth:
Isn't that information outdated now? My front camera works fine without any modification.
[Galaxy S I9000 Android Development] Christophe86:
ahh, the permissions... nope forgot it :D

i'm going to flash latest fugumod today on miui.us 1.8.19 and let you guys know if front camera works without modification ;)
[Galaxy S I9000 Android Development] renaud:
r1131 fixes the FM radio.
[Galaxy S I9000 Android Development] rtfpessoa:
SGS MIUI does not support fm radio yet..

What do i need do copy from cm7 so i can use radiofm?
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks so much ! :)
[Galaxy S I9000 Android Development] jaju123:
Im on 1121 and my phone WILL NOT sleep... huge battery drain :( Ive restarted several times and it won't help. This is straight from stock kernel, which had no problem.
[Galaxy S I9000 Android Development] renaud:
install spirit fm radio app

Sent using internet connectivity
[Galaxy S I9000 Android Development] renaud:
you took it from stable folder I assume? if yes, it's probably an app with wakelocks. use spare parts app to find which one.

Sent using internet connectivity
[Galaxy S I9000 Android Development] renaud:
interactive governor seems to hurt the battery life, I will probably revert to conservative.

Sent using internet connectivity
[Galaxy S I9000 Android Development] siky_dude:
Why not ondemand..

A balance between smoothness and battery life :)

Also which scheduler is default?
[Galaxy S I9000 Android Development] jaju123:
Yeah, I find ondemand is the best... it works fine and gives a large battery life on the stock kernel, maybe even better than fugumod.
[Galaxy S I9000 Android Development] renaud:
on demand is the default for the stock kernel from Samsung. the main problem with interactive is that it keeps the CPU at 400 mhz when Bluetooth is active

Sent using internet connectivity
[Galaxy S I9000 Android Development] siky_dude:
Just reporting., battery on your kernel is worse than stock. :)
[Galaxy S I9000 Android Development] renaud:
with the same governor?

Sent using internet connectivity
[Galaxy S I9000 Android Development] siky_dude:
With ondemand, just like stock :)

Interactive is worse.
[Galaxy S I9000 Android Development] Christophe86:
just flashed your latest kernel on miui.us 1.8.19

so far everything seems to work fine. front camera works, but aspect ratio isn't correct. when i switch sheduler in pimp my cpu to noop i get data loss and fc's, so i stick with cfq. changed cpu governor from interactive to ondemand to save battery life.

Sent from my Samsung Galaxy S using MIUI.us 1.8.19
[Galaxy S I9000 Android Development] ock:
Btw, just noticed your new website design, thanks!

Edit: FM radio works perfectly with my non-stock headphones. Just needed to install spirit fm and change its settings to Galaxy S cm7.

Great work!
[Galaxy S I9000 Android Development] FadeFx:
Hi Nika, seems like fm radio is working now as intended, or, wait, nearly as intended... there was a bug in samsung kernels causing fm to work mono only, eventually there was a fix later on, i remember i had fm stereo on speedmod kernel later on. Maybe you could have a look into this if u find time and passion...

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

tapatalked
[Galaxy S I9000 Android Development] zacharias.maladroit:
afaik this issue has long been resolved and only was a problem with early Froyo kernels
[Galaxy S I9000 Android Development] rtfpessoa:
To have FM on MIUI is not needed any module, or binariy?
[Galaxy S I9000 Android Development] FadeFx:
But its still an issue with cm7 stock kernel and also with fugumod. Do u think its spirit-fm bug? Mike thinks its a kernel issue...

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

tapatalked
[Galaxy S I9000 Android Development] kkube:
Hey niks, appreciate your work, have been on your kernel for long, but lately when I install your kernel, I have these data losses after reboot, like contacts, sms, settings getting erased.

I experienced it on 995, and some previous build also, last was 995, after which I switched to zachs kernel, which didn't give that problem atall.

Well I dont oc at all and like your kernel better(suits me well) but this problem has affected, I want to come back to your kernel, bt hesitating..

You have any idea why is it happening???

BDW I am on galnets miui rc1.
[Galaxy S I9000 Android Development] renaud:
I have no idea about what miui does since I don't plan to ever use it. I know some people have had this issue. I never experienced this on CM7 though, even when testing kernels with early crashes.

my kernel is synced with CM7 nightly userland, miui is not, so this may have some effects. it's strange to lose contacts since they should be synced with gmail.

Sent using internet connectivity
[Galaxy S I9000 Android Development] rtfpessoa:
I use miui but i use gmail so if i lost contacts they appear again..don't seen anything like that happening in here
[Galaxy S I9000 Android Development] ock:
Listened to the radio last night, turned it off and went to sleep. Strange thing is that alarm didn't ring, and there was a "pop" sound when I tried to play audio.

Will monitor to test what triggers this.
[Galaxy S I9000 Android Development] mikereidis:
Thank you !

I'd be interested to know the fix. I2c address allocation ? If you built any modules for the V4L driver, I'd be very interested in testing that.
[Galaxy S I9000 Android Development] mikereidis:
I spent a lot of time working around the audio routing issues and haven't listened too closely and figured users would report if it's mono or not.

I added 3 register setting commands to restore the frequency response issues that the CM7 and original Samsung kernels had. It works on CM7 kernel, but won't work on any kernel that doesn't have a way to write the registers via /sys/devices/virtual/misc/voodoo_sound/wm8994_write .

Yes, ideally the kernel/drivers would automatically set the FM related registers to allow stereo and good frequency response, or at least provide a way for a user space app to set them.

The Voodoo control app allows setting some of these registers on some kernels.
[Galaxy S I9000 Android Development] mikereidis:
Yes I'm afraid some rough edges need to be tackled. I just got my Galaxy S a week ago and started with other kernels/ROMs.

FYI, I'm taking 4 days of family vacation so won't be too available until Tuesday.

Thanks for your reports and patience. :)
[Galaxy S I9000 Android Development] renaud:
Multiple things, there were no hooks from FM radio in the sound driver, and I also unfortunately used the samsung Si4709 driver instead of the si470x. I don't know if your app is able to address the si470x instead of the Si4709. I don't mind too much if stock radio app is not working as I think most people will just use yours.

https://github.com/renaudallard/and...mmit/42d1dcceaadf0a6a940a5cb697be4668a35a280f
[Galaxy S I9000 Android Development] mikereidis:
I want to support V4L in my app as soon as I can.

But please see my next post for something far more important.
[Galaxy S I9000 Android Development] mikereidis:
ALERT/WARNING: IF YOU HAVE A GALAXY S and running Spirit FM or CM FM !!!

My worst nightmare ! :(

I think it's possible permanent speaker damage may be occurring.

Only for Samsung Galaxy S or other Silicon Labs based devices: Do not run my app. Do not run the CM7 FM APP.

I think the CM FM app was doing the same thing, and I think that at least part of the problem lies in the CM kernel.

I removed all older versions of my app and the only left, including on the Market is the "August 27" version. This version disables all support for Silicon Labs FM chips.

Angry mobs: Please put the torches down and let's discuss this calmly.

I hope beyond hope this isn't true, but I flashed a completely new ROM (Darky 9.2 Resurrection) and pulled the battery, and the speaker still sounds awful.

Some food for thought: http://xdaforums.com/showpost.php?p=8218737&postcount=194

"This one's a real gem: it can cause real damage. What the buggy code tries to do is disable the Left and Right inputs from the FM radio: the pin enables as well as the mixer.

What it really does in the process is: disable the on-chip thermal sensor (WM8994_TSHUT_ENA) AND thermal shutdown capability (WM8994_TSHUT_OPDIS), again because the _MASKs are inverted, but nothing's ORed in so these bits are set to 0. Go figure!

Clock output on GPIO (WM8994_OPCLK_ENA) is disabled as well, but that's probably not a biggie compared to the rest..."

AFAICT, the CM kernel still has the bugs in the earlier Samsung kernels.
[Galaxy S I9000 Android Development] toddmworth:
Is that when bluetooth is enabled, or only when connected to a device like a headset?

FWIW I also prefer ondemand. The guys on the neo thread seem to like ondemandx, whatever that is...
[Galaxy S I9000 Android Development] toddmworth:
I may be wrong, but my interpretation of this is that the possible damage would occur to the chip, not the speaker. That being said, if the chip fries the output lines to the speaker....

If you'd like me to be sure, grab the datasheets and I'll check it out.
[Galaxy S I9000 Android Development] renaud:
When connected to a headset, at least it does with the Parrot CK3100 in my car.
[Galaxy S I9000 Android Development] renaud:
What is the sound going out? Is it a high pitched screeching sound? My first SGS had this less than one week after I bought it.
[Galaxy S I9000 Android Development] toddmworth:
Well, the damage done would be by overheating, so it would vary from one chip to the next... I guess? I'm glad I don't know from experience.
[Galaxy S I9000 Android Development] renaud:
Well, I got a replacement on the same day for mine, but still I would have liked to know if it is the same issue.
[Galaxy S I9000 Android Development] toddmworth:
Sorry, I too am curious to know if it's the same thing. I didn't mean for you to think that I didn't want you to ask... I guess I am just thinking out loud.
[Galaxy S I9000 Android Development] lpalvaro:
i've runned spirit FM one time, about 2 minutes, and then i uninstalled it. is it dangerous for me? do i have to do a wipe or something like that?
[Galaxy S I9000 Android Development] toddmworth:
The code will improperly treat the audio chip in your phone, only when trying to do certain operations with the radio. Once those operations are done, the chip will remain incorrectly configured until it is re-initialised, which should happen when you reboot.

TL;DR: No. Just reboot and don't use the radio until this is fixed.

PS: To the devs, I'm sorry if I am overstepping my mark here, I am just trying to help out so that you don't have to post too much and can focus on other things you might prefer. Feel free to tell me to shut up :)
[Galaxy S I9000 Android Development] toddmworth:
Are the bluetooth enhancements from cm7 nightly 96 in any of the fugu builds yet? I was doing some testing and didn't get the expected response...
[Galaxy S I9000 Android Development] lpalvaro:
ok, thank you :D
[Galaxy S I9000 Android Development] Zatta:
Happy as i was yesterday I've been listening to FM yesterday night and nothing bad happened. Now I'm hoping for some "good" news like Mike blowing up his own speaker by playing some loud noisy music.

Anyway, about to buy his app so he can continue searching for improvements..

Edit: This is not an encouragement to just use it, I don't for now. Consider it a heads up for Mike and Nikademus.

Tapatalked u see
[Galaxy S I9000 Android Development] renaud:
which enhancements are you talking about?

Sent using internet connectivity
[Galaxy S I9000 Android Development] toddmworth:
Sorry there were a few:

(android_packages_apps_CMParts)Music: Bluetooth AVRCP 1.3 feature changes

(android_packages_apps_Music)frameworks/base: bluetooth: AVRCP 1.3 feature changes

(android_frameworks_base)Bluez: Changing AVRCP connect timeout to four seconds.

(android_external_bluetooth_bluez)Bluetooth: Ignore the Genre attribute length for AVRCP 1.3 Metadata request

(android_external_bluetooth_bluez)Bluetooth: AVRCP 1.3 feature changes

( from http://cm-nightlies.appspot.com/?device=galaxysmtd )

...I looked at these and I don't know why, but I thought I saw one of them modified the kernel, but now that I look again, I think I must have been looking at the wrong patch. Sorry!
[Galaxy S I9000 Android Development] FadeFx:
As u can see, most of the changes affect Bluetooth librarys and not the kernel i think.

Edit: I'd really better read everything to the end...

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

tapatalked
[Galaxy S I9000 Android Development] FadeFx:
Sorry for doubleposting, but this could be of interest for you Nika:

http://xdaforums.com/showthread.php?t=1233072

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

tapatalked
[Galaxy S I9000 Android Development] l3enjamin:
I also have this issue and I am using CM7 82. I will try the latest CM7 to see if the same happens.
[Galaxy S I9000 Android Development] Chief_Death:
For me using CM7 from time to time I get all kinds of FCs starting from Viber, Google Framework Service, Whatsup and the Market come first then all others follow up.

I noticed that only happens when I have the wifi turned on (nothing else specific just wifi). I tried rebooting, rebooting to recovery to clean the dalvik and cache then fixing permissions (this sometimes fix it for a while but most of the time it doesn't).

the only fix I found which is temporary (lasts couple of days) is flashing CM7 again.

P.S. I even tried flashing Samsung stock ROM and then returning to CM7 but it gave me the same effect as flashing CM7 straight away.

Thanks for your help niki.
[Galaxy S I9000 Android Development] FadeFx:
!q1

Sounds like u have a full /datadata/ partition, try uninstalling some big games.

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

tapatalked
[Galaxy S I9000 Android Development] Chief_Death:
thanks dude it seems really to be the problem I have it almost full (94%) will delete some apps and report back.

THANKS and sorry for being stupid
[Galaxy S I9000 Android Development] stenka85:
Your lastest stable kernel runs great on miui rc, good work nikademus.

Enviado desde mi GT-I9000
[Galaxy S I9000 Android Development] kimlindo:
Does BLN work with MIUI and FuguMod? I flashed that ROM earlier today to try it out and because it looks slick. But forgot to test BLN. I restored a nandroid anyway since I don't like having all apps on the "desktop", like the iphone. :P and I never find icons that I can be satisfied with. :p

Sent from my Galaxy
[Galaxy S I9000 Android Development] renaud:
No idea, it works with CM7. Since miui is closed source, it's hard to tell what will work or not.
[Galaxy S I9000 Android Development] tanu_invincible:
Should i use the stock CM7 kernel or this?..Im new here..SO plz inform which would be better?
[Galaxy S I9000 Android Development] siky_dude:
Test them out...
[Galaxy S I9000 Android Development] mikereidis:
Re: FM Speaker damage issues:

Just to remind you I'm visiting family until Tuesday and I'm trying to catch up now, so I'll respond to several posts:

In general: It's possible my speaker or chip got fried early on and on the last versions of my app speaker output was OK. I was incorrectly assuming the awful speaker output was due to software issues, but it may just be that my speaker/chip were already broken.

If anyone can say they were using my app on Galaxy S with a CM7 or related kernel via speaker and it sounded OK, then that version of my app may not have had the problem. I'm not absolutely certain that anyone but me has had permanent damage. At least one person claimed so on a GalnetMIUI thread, but the level of conversation there by some seems so juvenile it's not funny IMO.

toddmworth: Yes, damage could be to chip, or speaker or both. Any help/info you can provide is appreciated.

nikademus: On my phone it doesn't seem to sound like a screech. It sounds as if the speaker is highly overdriven or has holes punched through it. At this point this is true even using other non-FM apps.

lpalvaro: No, just don't run the app, and do remove it. Quite a few people seem to have no problem, especially perhaps because they use headphones only. But anyone running it is warned that they proceed at their own risk,

Zatta: Thanks... at this point my speaker or chip seem permanently damaged. I installed DarkyROM, removed the battery overnight and the bad speaker sound persists running stuff that sounded fine in the past. At this point there is no way to accurately determine exactly what or when my hardware damage was caused.

toddmworth: I'm very happy to have your feedback on this issue. It might be better on my own thread where nobody seem to be talking about this.

I thought there was a comment by you or someone else that indicated my app was "at fault". Perhaps I'm wrong; there was a lot of nasty, silly stuff on the Galnet MIUI thread, including a death threat (serious or not) against the OP (not me).

Anyway "blame" for software issues is a difficult topic. I think it's somewhat like bad relationships; Is one person at fault or should we just say they are incompatible ?

It's too early IMO to point fingers. I believe my app was pretty much just calling APIs that were available and expected to be used. My app generally doesn't directly access audio hardware (although that's somewhat debatable).

My app uses AudioManager->SetParameters ("fm_on=2055") and "fm_off=7", as I think the CM FM app and/or CM audio libraries do for FM. It also opens the ALSA controlC0 and sets values for the FM path to 0 (nothing) or 1 or 2 for speaker or headset.

If the damage happened due to CM kernel code (derived from known buggy Samsung code and known to have some original Samsung FM bugs), that was triggered by my app's calls to those APIs, then I'm not sure my app can fairly be blamed.

But I'm not sure this is what happened, and I'm not sure we'll ever know exactly what happened and I don't think anybody is too interested in extensive testing that could result in numerous devices/speakers getting toasted.
[Galaxy S I9000 Android Development] FadeFx:
Mike, did u think about the possibility that your speaker died just now by coincidence and would have died anyway? At least that is my impression about my own speaker, that died before cm7 had FM radio support iirc. And yes, it sounds like the speaker is broken or a hole got punched in, or some tiny particles got into the speaker. I remember there was a front-page article on something like this with another phone some time ago. I am thinking of getting me a replacement speaker on eBay sometime next month, if anybody has a possibility to change the speaker earlier, please report on the result.

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

tapatalked
[Galaxy S I9000 Android Development] toddmworth:
Maybe that was someone else.

I'll post more on this in your thread. :)
[Galaxy S I9000 Android Development] Zatta:
Mike, relax. Just posted in your own thread to report for duty.

Meanwhile I'm enjoying my phone with fugumod kernel 1157, fully at my convenience.

Tapatalked u see
[Galaxy S I9000 Android Development] olivercervera:
Are there any issues using this kernel on MIUI?
[Galaxy S I9000 Android Development] siky_dude:
Why don`t you stop asking stupid questions and start reading for awhile :)
[Galaxy S I9000 Android Development] FadeFx:
Nika, i just tested your new wifi driver for chanel 13 and can report a positive result... dont know if already someone else tested yet, could not read anything yet at least.

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

tapatalked
[Galaxy S I9000 Android Development] Bess833:
Hey Nika, just wanted to tell you that nightly #100 + 1157 is working amazing.

Keep up the great work, great kernel.
[Galaxy S I9000 Android Development] bubblefighter:
On 1155 and Nightly #98, tested stock kernel and then Fugumod. Stock kernel, on Launcher 7 was jerky, lags here and there. Switched to to fugumod, problems gone and phone just a whole lot smoother and snappier.

Great work.
[Galaxy S I9000 Android Development] Bess833:
I have one question for this kernel - is there any way to turn off the BLN since it's not in the CM settings?
[Galaxy S I9000 Android Development] FadeFx:
Just use silent hours or what its called. But don't worry about your battery, the leds consume nearly nothing.

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

tapatalked
[Galaxy S I9000 Android Development] renaud:
it's in the cm settings, it's called quiet hours

Sent using internet connectivity
[Galaxy S I9000 Android Development] Bess833:
Oh thanks. Btw 1157 is amazing.

Edit: Wasn't wondering because of battery.
[Galaxy S I9000 Android Development] kasper_h:
1157v works very well with nightlies 98&101 over here.

I was wondering why cfq was the default IO scheduler? I thought bfq is the cm7 default...
[Galaxy S I9000 Android Development] renaud:
my kernel is very far away from stock. furthermore I didn't really notice much improvements from bfq. as you said it works fine so why switching?

Sent using internet connectivity
[Galaxy S I9000 Android Development] zacharias.maladroit:
indeed it's more than 1+ generations in kernel development ahead

hopefully I'll find some time today then I'll add some of my patches & see whether they all apply and work with it

once that experimental branch works stable for me I'll do some further tests or even go so far to post some test kernels

hope you don't mind :)

thanks !
[Galaxy S I9000 Android Development] FadeFx:
I think that's why nika makes this kernel, so future kernels can be based on his work...

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

tapatalked