yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] renaud:
Try to flash CM7 again and then put the kernel.
[Galaxy S I9000 Android Development] Alberto96:
anyone got cmparts working with superosr rom?
[Galaxy S I9000 Android Development] AlexandreT:
My compass is reversed in 1561, even after calibration. My i9000 is from the first generation.
[Galaxy S I9000 Android Development] kimlindo:
1584 seems to be working fine for me. Haven't run into any bugs yet. Well, my compass isn't really working. But I'm indoors, haven't tried it outside.
[Galaxy S I9000 Android Development] farid993:
VPN can not connect in 15XX
[Galaxy S I9000 Android Development] beekay201:
i can't even select user certificate.

edit: i was holding it wrong.

edit: although i can confirm, vpn not working on 1550v.
[Galaxy S I9000 Android Development] KingMetal:
On all latest versions my music is not playing smooth.

It sometimes hangs like a damaged cd.

I use ondemand
[Galaxy S I9000 Android Development] kimlindo:
What player are you using? My music plays fine in PowerAmp.
[Galaxy S I9000 Android Development] KingMetal:
Well i does, t hang often but sometimes, especially when listening music and using browser.

On stock kernel is does, t.

Music player pro

Dsp manager
[Galaxy S I9000 Android Development] kimlindo:
With PowerAmp you can increase the buffer size to prevent music from skipping. You could try that and see if it helps.

And it's a really good player in my opinion.
[Galaxy S I9000 Android Development] KingMetal:
Thanks, tried it but i prefer music player pro
[Galaxy S I9000 Android Development] renaud:
I also use player pro, I didn't see this problem

Sent using internet connectivity
[Galaxy S I9000 Android Development] renaud:
which vpn protocol?

Sent using internet connectivity
[Galaxy S I9000 Android Development] Leegalaxy:
I had the music problem too. Also some pretty serious battery drain on 1561.

GT-I9000. CM7.
[Galaxy S I9000 Android Development] farid993:
PPTP

10 characters
[Galaxy S I9000 Android Development] renaud:
To a windows server? with MPPE?
[Galaxy S I9000 Android Development] farid993:
Sorry I dont know about this :S

I use pptp in vpn setting only :D
[Galaxy S I9000 Android Development] mobidzid:
Hmmm but it works fine with Neo17r12... I will try your advice tomorrow.

sent using xda premium from

sgs+cm7+neo17

jvk bl/jvr modem
[Galaxy S I9000 Android Development] zacharias.maladroit:
perhaps it's a cpu scheduler problem (with poweramp) - dunno

afaik I also had this at the beginning when I started using 2.6.37 kernel-base

try switching to conservative governor + up_threshold 76 and down_threshold to 35

and/or freq_step to 10 (from 5)

nika: you got a pull-request

:)

I'll see what else needs updates & improvements, then do some pull requests
[Galaxy S I9000 Android Development] beekay201:
linux server, openvpn 2.2.1, TCP, lzo compression active, using certs to authenticate (no password);
[Galaxy S I9000 Android Development] rtfpessoa:
Compass in 1584 not working right in here...

Strange....
[Galaxy S I9000 Android Development] renaud:
ok now definitely avoid #104, stay on #103

Sent using internet connectivity
[Galaxy S I9000 Android Development] kasper_h:
Why? (I'm still on #103, so I'm not that worried :D)
[Galaxy S I9000 Android Development] renaud:
this one is funny. the big drop is when I flashed #103 and booted it, after you see the battery charging with the phone not being connected when I flashed fugu again.

Sent using internet connectivity
[Galaxy S I9000 Android Development] FadeFx:
Im interrested too, im on 104 now, had a full system crash with phone fc loop despite i didnt use 2g/3g toggle. Tried to roll back an old backup with no success then i flashed a samsung rom and 104, then i had data mounted ro so i did a nandroid again and a data restore, titanium restored my apps and now everything seems to be good so far. Also my problem with k9 notifications keeping the phone from sleeping seems to be gone

Btw, boot time is absolutely amazing...

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

tapatalked
[Galaxy S I9000 Android Development] toddmworth:
Yeh I tried reflashing because that's what I had read about it in the CM7 thread. Interesting perhaps: it came back, and I realised a commonality between the two events - it was when the battery had run completely dead and the phone switched itself off, that the next boot had the Android OS battery drain issue.

---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------

Battery drain: Did you do 3 full charge cycles before reporting this?

Music skipping: I didn't get any skipping on 1552 or the three before that. Played a game of Hawx for 2 hours on a jet, with Player Pro in the background, no skips at all.

Buffer sizes: You can change that in Player Pro too, using the DSP plug in.

DSP Manager: Why? Listen to it as the artist intended. Opinions aside: Did you try with all that audio bling from DSP manager disabled? Did it still skip? Describe the skipping... was it really skipping, or was it dropouts, or clipping, or....?

---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------

Perhaps I'm not the only one that seems to think that 104 is haunted. I have had so many stupid issues with 104, that I never had before. I'll roll back to 103 ASAP.
[Galaxy S I9000 Android Development] KingMetal:
Govenor conservative works better.

No scratches on my music.

Enjoying new anthrax album faultless now :)
[Galaxy S I9000 Android Development] mobidzid:
:(

Flashed in this order in CWM:

- ultimate kernel cleaning script

- Nightly #103

- JVS radio

- FuguMod 1586

Bootloop.

- ukcs

- #103

- 1586

Bootloop.

- ukcs

- 1586

Bootloop.

- ukcs

- #103

Finally getting the phone to boot.

:(

EDIT: Wifi unable to obtain IP (but no error like before on 1561). Flashing Neo... See you.
[Galaxy S I9000 Android Development] bubblefighter:
it is Nightly then the ultimate kernel cleaning script.
[Galaxy S I9000 Android Development] mobidzid:
Right. Tried that. Bootloop.

UPDATE: On Neo17_r12 no problem with wifi :)
[Galaxy S I9000 Android Development] Moudii:
Here is what I do and never have any trouble.

Phone power off and 3button combo into cwm, NOT reboot to recovery.

Run cleaning script.

Flash new kernel.

Boot.

Works for me :)
[Galaxy S I9000 Android Development] m2677086:
phone.....: SGS i9000

bootloader: JVK <-- sir, if i understand correctly, cm7 (and this kernel (support?)) but are not supposed to run under 2.3 bootloader. I switch between cm7 nightlys, glitch kernels and this kernels without problem even once under2.2 bootloader. (i use reboot into recovery everytime :D i m lazy but it always works)

Kenneth.
[Galaxy S I9000 Android Development] mobidzid:
Yes, indeed. GB BL are supported since approx. Nightly #77. Or was it #84?

Besides, Neo17_r12+#103 works ok for now - I have started getting SoDs every 12h or so on Neo17_r2+#102 after many days of smooth run so I wanted to test with fugu.

BTW: Warning! Glitch still doesn't support GB BL. Afaik.
[Galaxy S I9000 Android Development] silitek:
1586 with SuperORS works great.....againn :)
[Galaxy S I9000 Android Development] rtfpessoa:
Version 1586 working very good in here.....gps, wifi everything working right...
[Galaxy S I9000 Android Development] zacharias.maladroit:
compass ?

for me it's still acting weird

hm, I gotta go out and try again in the next days
[Galaxy S I9000 Android Development] Robot12:
Had the "stuck-on-800mhz-bug" after listening to music with poweramp. Reboot solved it.

I'm on nightly 104 and fugumod1586, but had this bug also on earlier nightlies and different kernels (also on cm7stock-kernel). So im not sure, if its kernelrelated, or a bug in cm7. Just wanted to let you know, apart from that, this kernel is realy working flawlessly and fast, didnt have any other issues.

Keep up the great work.....
[Galaxy S I9000 Android Development] omiks3:
Yeah i'm on #104 with 1561 vpn not working for me either
[Galaxy S I9000 Android Development] montrealcityboy:
On zachs neo kernel I get that bug with performance governor.havent tried others im always ondemand governor.which governor are you using?
[Galaxy S I9000 Android Development] Robot12:
Using fugumod-default sheduler and governor (cfq/ondemand). But also had this bug on neo, glitch and cm7stockkernel, using different sheduler/governor. So i would say, its rather a cm7bug, then kernelrelated. But i dont know......
[Galaxy S I9000 Android Development] beekay201:
still on 1550v, i must say this has been very good to me. though i didn't manage to get vpn working no matter what i tried i tried harder and got it working (vpn working fine on pcs and 1 laptop through wireless, also on phone now), it just keeps getting better and better. moving on to 1586.

edit: also working in 1586v.
[Galaxy S I9000 Android Development] bakoyoko:
Portable hotspot in 1586 still not working while in stock cm7 working perfectly.
[Galaxy S I9000 Android Development] rinl:
I can confirm that compass does not work in 1586. back to 1561, it works fine again :D
[Galaxy S I9000 Android Development] toddmworth:
Or maybe poweramp... You seem to be avoiding that possibility ;)
[Galaxy S I9000 Android Development] Robot12:
Before, i only had this bug after playing games like Asphalt5, never after playing music. But, of course, maybe poweramp, maybe sheduler/governor, maybe rom or kernel or something else.Also, it always comes very randomly. As i said, i dont know :-). But, afaik, its a known

Bug and others also had it......
[Galaxy S I9000 Android Development] toddmworth:
What's actually using the CPU when this happens?
[Galaxy S I9000 Android Development] toddmworth:
Sorry to bump but... What's the word on the distorted blacks?
[Galaxy S I9000 Android Development] siky_dude:
That sounds so racist.
[Galaxy S I9000 Android Development] FadeFx:
omg...

btw, mine is biger than yours....
[Galaxy S I9000 Android Development] siky_dude:
That sounds so sexual.
[Galaxy S I9000 Android Development] mikereidis:
What, over 2 weeks now without a nightly flash fix ? Even the humor seems to be deteriorating. :D

I didn't realise that CM was dependent on kernel.org. I wonder why...

Some ports are having no problem. Only official ports ?

(1776 -> 1777)
[Galaxy S I9000 Android Development] stepic:
And what about releasing another RC or final version? Nightly #104 has been already tested for a long time by several people.
[Galaxy S I9000 Android Development] FadeFx:
Thema dependency is buildbot to android.git.kernel.org which is down as well, buildbot tries to repo sync before building and cant.

A stable version is depending on milestones that need to be acchieved i think.

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

tapatalked
[Galaxy S I9000 Android Development] FadeFx:
Look at your sig...

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

tapatalked
[Galaxy S I9000 Android Development] renaud:
I released an updated kernel before supercurio once :)

Anyway the benefits of the updated kernel outweight being able to load a new module for a few hours
[Galaxy S I9000 Android Development] renaud:
this is quite strange, do you still have it with r77?
[Galaxy S I9000 Android Development] zacharias.maladroit:
that can't be the problem

that would mean that the version string (2.6.35.7) was hardcoded in the voodoo app

but I doubt that

I've a 2.6.35.13 kernel running here, too and voodoo sound + other things voodoo

work fine

edit:

I see - talking about voodoo control

plus

FYI:

built/patched in it works
[Galaxy S I9000 Android Development] kasper_h:
FuguMod 71v on nightly #19 works well. Wifi signal seems somewhat better: real test will be tomorrow at work.

About UV: I now only set an UV value for 100MHz. My theory is that if the phone is in use (so above 100MHz), the screen is taking so much juice that the CPU is only minor to battery life. Using UV for battery saving seems to me to be mainly interesting when the phone is idle. Or am I missing something?

BTW my (paid) voodoo app works perfectly with the Fugu 71v kernel: both sound and color.
[Galaxy S I9000 Android Development] aorth:
Hmm, I just compiled locally from your latest github and Voodoo Sound is working again. I didn't try with your 77, I figured compiling myself would be more fun heheehe.

I'll keep an eye out and let you know if it happens again... cheers.
[Galaxy S I9000 Android Development] toddmworth:
I tried 71n and didn't see that same issue.

77v on nightly 24 undervolted 100mV at 100hz just did 8% battery in 6 hours while I slept - nice!

Wifi seems a little stronger, I can now see two of my neighbours' AP which I couldn't see before.

I have the same theory, hope we're on the money ;)

When you say voodoo works perfectly with 71v, you mean it will insert the module from the control app?
[Galaxy S I9000 Android Development] kasper_h:
I can UV -200mV @ 100MHz now, whereas 100mV was the max on Glitch's kernel, don't know whether the UV works the same on both kernels?

I can now connect to the work-wifi, which I couldn't on older kernels, so there is some improvement. Connection is still barely usable (many disconnects), which is somewhat worse than on stock ROM. But at least there is some improvement.

I get the notification from the voodoo control app "no need to load module, built-in kernel voodoo sounds: v9". (but it tells below that the kernel is not supported, so I assume it can't inject the voodoo module, but as it is build in ánd recognized as such by the voodoo control app, I assume it works).
[Galaxy S I9000 Android Development] aorth:
For the record, I just wiped Dalvik Cache and flashed FuguMod #71 and Voodoo Control is working again. Strange...
[Galaxy S I9000 Android Development] sptorrent:
V/N

Having tried both voodoo and non voodoo version (latest 83 kernel), I much prefer the voodoo one - which of course is personal taste.

Thanks a lot for that fast, battery-friendly kernel.
[Galaxy S I9000 Android Development] ArctiX:
For me the 72 fps cap on latest fugumod isn't working... The cap is now 49 fps. Running latest #30 nightly.

Edit: Something is wrong with quadrant, on the spinning globe graphic test i was getting 56fps now it's only 49... But on neocore i'm getting 64fps.. Strange.
[Galaxy S I9000 Android Development] CaracalSef:
Same here. I was willing to write about that :)
[Galaxy S I9000 Android Development] renaud:
it seems quadrant is broken on this test, I get either 49 or 64 depending on whether I locked the screen before running quadrant. it has never been a really accurate benchmark, but now it's really flawed

I am also not sure putting the cap to 72 gives any bonus since the screen refresh rate is 60 hz anyway
[Galaxy S I9000 Android Development] renaud:
Raising the cap doesn't mean your phone will be able to go over stock one except for lightweight tasks, like the UI.
[Galaxy S I9000 Android Development] zacharias.maladroit:
try setting it to 68 (-> max FPS 65 FPS at the globe in quadrant standard)

that one's the sweet spot for me

72 lead to lower average FPS

68 lead to more or less 65 FPS across the tests where the power was available

as added bonus on top everything might be smoother too (if it's not already with the 72 set)
[Galaxy S I9000 Android Development] renaud:
What I think is that quadrant is broken.
[Galaxy S I9000 Android Development] phzi:
It's not just quadrant that will see fractions of the max fps. Values too high seem to result in a divider on fps more often then not. I agree with zach that 68 seems to offer the best consistency from the kernels I have tested.

Sent from i9000m on cm7, with xda premium.
[Galaxy S I9000 Android Development] zacharias.maladroit:
FYI:

your latest wifi changes (which I also included in my test kernel for testing - so thanks for that !)

seems to break channels >12 or something in that range again (we already had that in the past with a testing driver)

at least channel 13 doesn't work for me with it

don't know which commit exactly did break it (again) :\

edit:

the offending commit is:

"net: wireless: bcm4329: Update to version 4.218.248-23" (commit 8d994329cbb33bd7edc9)

(related: "net: wireless: bcm4329: Update example locale table" but not likely causing any issue)

perhaps you can figure out on how to fix the higher channels

thanks !
[Galaxy S I9000 Android Development] boarder.2k9:
just to confirm, bln is off with this kernel?

I have installed and cannot see the option in interface.
[Galaxy S I9000 Android Development] zurchpet:
The option has been disabled in the ROM, not the kernel. so you need a nightly that supports BLN to see the option or install an old CMParts.apk from an earlier nightly (whatever this might break) or create a shortcut to the LEDNotification action on your homescreen. But also the kernel does not support BLN as it is not supported by the ROM devs.

Hope this clears things up :)
[Galaxy S I9000 Android Development] R34L2Pac:
I think that it´s just opposite way - the Led-notifications was disabled in the kernel, but ROM still support it. So if somebody wants LED-notif he just choose a custom kernel with this feature turned on (Zach makes two version of his kernel with/without this feature and Glitch´s kernel has this feature turned on all the time). Also there was never an option to turn on/off this feature. If it´s in the kernel, it is just working or if you didnt want that you could set the Quiet hours for all the time and just tick to Dim LED.
[Galaxy S I9000 Android Development] siky_dude:
of course :D

was on xda app and could not see it :)

also this post made mine bigger ...
[Galaxy S I9000 Android Development] FadeFx:
Lol, so lets stop that ot, before your pants cant hold it anymore...

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

tapatalked
[Galaxy S I9000 Android Development] Alberto96:
:rolleyes::cool:
[Galaxy S I9000 Android Development] dherre65:
Hi,

i'm running Galnet MIUI Chameleon Final on my SGS. Runned it with Vorbeth kernel and Neo kernel, but Vorbeth has too few features and Neo gives SODs.

So i tried Fugumod. Very stable etc, but wifi won't work. I tried Fugumod 1586 and 1581, other radio, fixing permissions, rebooting, kernel clean script before every flash, no wifi. But if i flashed back Neo, wifi instantly turned on.

Now i noticed that with Fugumod i got no mac address. I think that's the reason why i can't get wifi turned on. But i'm wondering how that's possible? Especially because it returns with another kernel...
[Galaxy S I9000 Android Development] siky_dude:
At least read the op.
[Galaxy S I9000 Android Development] dherre65:
I did. What I understand is that if your ext4 filesystem is corrupted, your wifi can fail. But MIUI doesn't run on ext4. At least not on my phone.
[Galaxy S I9000 Android Development] FadeFx:
open a terminal on your phone and enter

mount

then post the output here. i am pretty sure your /data/partition is mounted r/o and thus wifi can not work.

if so, go to recovery, do a nandroid backup, format your data partition and then do a nandroid advanced restore.
[Galaxy S I9000 Android Development] siky_dude:
It runs on yaffs2 and ext4
[Galaxy S I9000 Android Development] dherre65:
It is mounted r/o indeed. I'll try your solution, thanks in advance.
[Galaxy S I9000 Android Development] zacharias.maladroit:
ok so those JVR+

compass driver changes break it

it probably needs updated userland (gps daemon and/or drivers in the ROM)

so best bet probably would be to revert the update and stay with the old driver state for now

I did quite some research and looked for similar drivers & devices on newer kernels but what I've come up with so far

is

the the yas529 is also used on the meego platform but with 2.6.35 so probably won't help since the driver probably works differently than on our device (different libraries)

using the ak8975 compass from the SGSII as reference driver - but there's no newer driver than 2.6.35 right now - right ?

using the compass driver from the Nexus S as a reference and look whether a kernel port for 2.6.38 already is there (afaik netarchy works on one)
[Galaxy S I9000 Android Development] mobidzid:
Big THANK YOU! Solved my bootloop and no-wifi problems with FuguMod :) Running 1586 now and hoping fo SODs and random reboots to be thing of the past...
[Galaxy S I9000 Android Development] beekay201:
i just had one sod on 1586 this afternoon.

on a unrelated subject, i added tun to /etc/init.d/04modules to autoload on each reboot. fixed permissions manually. bcm4329 loads fine, tun does not. tun.ko can be found under /system/lib/modules/. ran a quick search around, can we load it automagically with /sdcard/userinit.sh script?
[Galaxy S I9000 Android Development] Mothatt:
On JVS with Dark Core for cwm and all partitions ext4

Realised how terribad stock firmware is

Flashed #104, rebooted into recovery to then flash

gapps + JVS modem + FuguMod #1586

Bootloop.

Tried again with #103, still problematic. Tried a few other combinations, still no go

Flashed #104, rebooted into recovery, made a backup, formatted /data, restored /data, flashed #1586, all good.

None of this happened before I went to stock and was just updating as each release came out.

The moral of the story boys is that fresh installs of CM7 seem to have issues.
[Galaxy S I9000 Android Development] mobidzid:
Hmmm can't use keyboard on 1586 - like it is totaly uncalibrated. Very strange. Back to Neo again..........

sent using xda premium from

sgs+cm7+neo17

jvk bl/jvr modem
[Galaxy S I9000 Android Development] zacharias.maladroit:
Y U NO UNDERSTAND problem ;)

stock kernel -> 2.6.35 version of ext4 + yaffs2

fugumod -> 2.6.38+ version of ext4 + also updated yaffs2

ext4 has some fundamental changes (among those superblock changes)

so it DOES NEED a format to enable all those changes from the start

it's not a general issue with fresh cm7 installs/caused by it - but due to the change of the kernel base :)
[Galaxy S I9000 Android Development] Mothatt:
Oh ok, I wasn't aware. Thanks for clearing that up :)

Unfortunately after doing all this and it all running smoothly beforehand, browser, Google search and f5 (a Reddit app) now all force close after trying to use them, whilst they were all working properly before the phone went to sleep :/

I was jumping the gun and blaming it on stock as nightlies 103 and 104 both have had other issues with them, one of the most notable ones in my case being the fact my carriers APN was no longer available by default, even though I was sure the apns-conf.XML was the same as it had been in previous releases and that nikademus had previously said 104 was buggy or something along those lines.

Heh, noobs gon' noob :)
[Galaxy S I9000 Android Development] FadeFx:
Just found out there is something wrong with automatic brightness, but i am not sure if its a kernel problem, it sometimes does not apply the correct brightness. The sensor value does change and so does the filtered value, but not the brightness.

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

tapatalked
[Galaxy S I9000 Android Development] toddmworth:
I wonder if that's related to the brightness issue that was introduced a little while ago...?

Speaking of which, I noticed a very strange behaviour there:

Scenario 1

Filter off, dark room. Turn on a light. Raw value stays the same. Wait 3 seconds or so. Raw value moves and screen brightness adjusts.

Scenario 2

Filter on, dark room. Turn on a light. Raw value stays the same. Filtered value changes immediately, screen brightness adjusts. After 3 seconds or so, raw value updates. Screen is already adjusted.

WTF?
[Galaxy S I9000 Android Development] FadeFx:
Afaik this was solved recently, i am also not sure if my problem is kernel related at all, as raw and filtered show correct values, just the brightness does not adjust. I am on nightly 104 btw...

Edit: it does apply brightness after a screen lock...

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

tapatalked
[Galaxy S I9000 Android Development] kasper_h:
I've had this issue for quite some time. I don't use auto brightness anymore :)

Sent from my CM7 galaxy
[Galaxy S I9000 Android Development] toddmworth:
Thanks mate. Seems we have a few bugs atm: Brightness, Compass, and Hotspot :/ (did I miss anything?) I'm on 104 and 1552, I'll test the latest and see if I get them too, before I take that advice to downgrade to 103 and test there...