yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Samhain77:
I'm using Apex Launcher too but no FC with 3.2.5 and force GPU enabled..... Now I've installed 3.2.5.1...
[Galaxy S II Original Android Development] SergeF1:
It's just me or Pegasusq governor stays in 500MHz step too much???
[Galaxy S II Original Android Development] ercxar:
Wifi Channel Problem

Here too. Any wifi channels that above channel 11 will not find in phone.

I know the solution here but this is a problem with new wifi driver I think.

EDIT: The solution won't work! neither if I change my wifi channel to any other! It will not find my wireless network.
[Galaxy S II Original Android Development] ssauger:
No wifi problems for me with latest kernel on cm9 and stock rom.
[Galaxy S II Original Android Development] naveediftikhar:
Hey gokhan i tried what you asked to set the deepsleep as idle...n amazingly it does have a better deepsleep percentage atleast for me than the stock setting..my test was really short termed(spaned over 3hrs) but i got the best % of about 95..first time ever for me...my settings are pegasusq deadline with aggresaive cpu , gpu uv's and uc's..with some parameter tweaks of ma own...battery life is good for me..!

Lastly m pretty sure if someone wud conduct the test for for overnight theyll find same results as mine!
[Galaxy S II Original Android Development] fasst:
Latest 3.2.5.1 definately gives me weaker wifi signal strenght.

Measured from exact same position.

3.2.5.1 - -63db

3.2.4 - -52db

(Lower is better)
[Galaxy S II Original Android Development] coloxim:
GM say that?

Anyways I'm using simple idle...and is much better...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Samhain77:
I know what you're saying but you're saying it inthe wrong way.... if lower is better then 3.2.5.1 is better (-63 is lower than -52) ;)
[Galaxy S II Original Android Development] pikachu01:
The screen hung when I tried to do pattern unlock after sleeping for a while. Kmsg is here

http://db.tt/5K5UFHhB
[Galaxy S II Original Android Development] fasst:
I know :) , but before posting I thought maybe someone would misunderstand if I wrote it in the matematically correct way.
[Galaxy S II Original Android Development] droidphile:
Your kmsg starts from bootloader dump and such from the new boot. No cpu backtrace from last crash could be seen. Did you reboot by long pressing power or by removing battery.
[Galaxy S II Original Android Development] pikachu01:
Pressing power. :/ Didn't check the file before uploading. Nooby mistake >.<
[Galaxy S II Original Android Development] vertrag:
sorry to ask.. is there any differences between bootin with long press power or removing the batt? I mean is it affecting the last_kernel_msg log hehe..
[Galaxy S II Original Android Development] crachel:
Just a reminder for those who missed it

This way the thread is easier to read for those who are looking to help/contribute.

If you would like to say thanks for the awesome kernel, please just click the "Thanks" button.
[Galaxy S II Original Android Development] droidphile:
Kmsg buffer will not be cleared on first boot after a crash/sod if long press power button method was used. Rebooting by pulling battery out wipes log and kmsg is 'reset'.
[Galaxy S II Original Android Development] ShadowSkills:
IIRC, most of my slow down bugs moments occurred when there's an incoming whatsapp message while using another app (which I think will trigger the notification). I never use BLN too. I don't know if this is easily reproduceable though..

Btw, I never had any more slow downs since a few versions back.. just telling the past experiences.

Cheers.

Sent from my GT-I9100
[Galaxy S II Original Android Development] :
I've just encountered the slow-mo bug.

Just minutes before that I did:

- Wipe Data/Factory reset

- Delete Cache

- Delete Dalvik

- flash Slimrom (3.7) (aosp)

- flash siyah (3.2.5.1)

- restore my apps (no system apps) and their data (extweaks and setcpu included)

Governor: pegasusq

200-1200 (all steps) (-50mv all)

gpu 66-133-200 (all uv)

no bln

scheduler: deadline

Then I opened Chrome-Browser and it happened, slow-mo bug.

extweaks and setcpu were not granted su-rights by then, So that probably means that the changes I've made in extweaks and setcpu before restoring them, were not active at the moment I encountered the slow-mo bug.

Hope that helps. Oh and btw, that was the first time I had the bug, Before the Datawipe/factory reset, I've never had it.

edit: I've just found out that my extweaks-settings had been deleted for whatever reasons, so that would mean, that this bug even exists, if nothing in extweaks is changed from the defaults.
[Galaxy S II Original Android Development] olifee:
I can also confirm such an observation.

It appears that the shown signal strength by the new driver is the same as it was in the one we had before. Some versions back, people started reporting their WiFi-reception got better.

In fact, it appears only the shown signal strength is higher. I noticed in 3.2.4 (and the other ones with same driver) that I sometimes lose connection (no data transferred anymore, although it shows as connected and can transfer data again when I come to a place with better reception without any reconnect in between) or can't connect although the reception appears to be acceptable.

So I think the newer drivers in >3.2.5 are back to the older reported signal levels, which appear to have been "more correct", so the "reception-thing" feels like some kind of placebo to me.

As I am currently somewhere with WiFi everywhere (the heart of the internet! ;) ) and the phone keeps "roaming around", maybe someone else can try out how the data rate (when really transferring data, not looking at connection status only, that is way off most of the time) drops with distance in comparison between 3.2.4 and >3.2.5 to clarify this. I predict it will be pretty much the same ;).
[Galaxy S II Original Android Development] Hannibal226:
Dunno if already posted but til 6 hours around 2-3 times no wake up...

Had to reboot phone manually...

Think prob with deep sleep

Sent from my Galaxy S2 - I9100 with SensatioN Rom!
[Galaxy S II Original Android Development] mathsmart:
Wifi seem to take longer time to connect and after quite some time it connect butad to reboot the phone and no problem with 3.2.4

swagga baby
[Galaxy S II Original Android Development] :
@gokhanmoral

hi,

please add dormancy hours to the bln

thank's
[Galaxy S II Original Android Development] jack_p75:
2.3.5.1 are so fast but new wifi drivers are very slow to conect revert to 2.3.4 work realy good

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Phistachio:
I disagree. New wifi drivers work very well for me.
[Galaxy S II Original Android Development] stormtroopercs:
Latest cm9 and siyah.
[Galaxy S II Original Android Development] olifee:
We cannot debug this without any log.

Next time, please restart your phone by long press of power button and attach

/proc/last_kmsg

to your post as has been described many times in the last pages. If you are not sure how to report an error or whether it is kernel-related, please use this thread:

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

The thread you just posted in is reserved for development-related topics.

This is a nice feedback to put here:

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

When you do so, please also explain why you had to reboot your phone and what was the problem. If it didn't wake, see my answer some lines above.

You might then also add more info, like what "longer time" exactly means and whether it occured on several access points and so on.

You appear to be referring to the scheduling-function of BLNpro. Things like that are better handled in userspace (read: an app) than in kernel.

You can use BLNpro or something like tasker to do it, but a discussion about that would be better suited for this thread:

http://xdaforums.com/showthread.php?t=1658647
[Galaxy S II Original Android Development] Phistachio:
Clear ExTweaks data, reinstall it.

Try resetting exteaks profiles too.

---------- Post added at 12:59 AM ---------- Previous post was at 12:36 AM ----------

Here are some benchmarks :D
[Galaxy S II Original Android Development] PedroMRP:
Just have that slow motion bug.

My phone is charging and i was using chrome beta to google something.

Using 3.2.5.1 with cm9 + battery profile with sio + pegasusq.

Last_kmsg: http://db.tt/z5Y6L17K
[Galaxy S II Original Android Development] pikachu01:
By any chance, the people who are experiencing slowmo are using SuperSU?
[Galaxy S II Original Android Development] Cristiano Matos:
Interesting question.

I had 2 or 3 slowmos using 3.2.4, all in second rom XXLPD and guess what? With SuperSU.

My first is CM9, where a spend 80% of my time, and never had nothing.
[Galaxy S II Original Android Development] desean:
I have 2 last_kmsg logs to share.

1) On 3.2.5, phone freeze while using app then the phone self reboot. Initially thought the issue had to be with "Force GPU Rendering" enable until I had the same issue again with 3.2.5.1 with "Force GPU Rendering" disabled.

2) On 3.2.5.1, phone freeze again while using app. "Force GPU Rendering" disabled. Reboot using hold power button method.

On both instance above, I was using pegasusq gov. Wasn't using pegasusq previously (at least not with 3.2.4) and back to ondemand for now. I am guessing my 2 "freeze and reboot" occurrence might have to do with pegasusq. Hope the log will provide more info.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
@Gokhan: Could you please check the nandroid backup for PrimaryROM. The backup function did backup the full system including external_sd's App2SD but after backup made, it deletes every apps installed on SDcard.

I tried it with backup to external_sd.

The rest is NICE!!! Thanks bro... Keep up the good work!
[Galaxy S II Original Android Development] pikachu01:
Try using SuperUser rather than SuperSU and see if the slowmo bug is there again. I had my own problems (freezing when calling SU prompt) with SuperSU before this and changnig back to SuperUser solved it.

Offtopic:

Why is everyone referring the new version as 2.3.5 and 2.3.5? It's 3.2.5 and 3.2.5.1 :S
[Galaxy S II Original Android Development] Cristiano Matos:
That's what I meant about CM9. Never happens slowmos probably because Superuser.

About 2.x.x :confused::confused:

Thanks
[Galaxy S II Original Android Development] nitinvaid:
For me still 3.2.3 is better in battery

I have mediaserver wake lock problem in both 3.2.4/3.2.5

Don't know why.
[Galaxy S II Original Android Development] Nerenye:
I´m using superSu on Cm9 and never get slomo

don´t think its superSu related... eventualy by a missed update of superSu but not by the tool itself
[Galaxy S II Original Android Development] baron von bubba:
no body seems have mentioned if the CPU steppings are changed from the 18 step option the cpu wont drop to the lower ranges?
[Galaxy S II Original Android Development] pikachu01:
Just made an observation here regarding the pegasusq governor, setting the down differential to anything higher than 5 (e.g. 10) results in the governor spending a lot of time in the highest frequency.

This is with sampling_down_factor of 1 and a high threshold (e.g. 95).
[Galaxy S II Original Android Development] crm4:
FYI I had slomo with SuperUser also, but with 3.2.4. Didn't happened since 3.2.5. :)
[Galaxy S II Original Android Development] Fire_Paul:
NTFS automounting

Good day everyone. )

I have some questions about "NTFS automounting" (SiyahKernel 3.2):

1. how to change NTFS automounting folder?

2. how to unmount NTFS sticks after automount?

3. how to turn off/on automounting?
[Galaxy S II Original Android Development] JB-007:
3.2.5.1 perf

Hi

I noticed 3.2.4 is better in terms of scrolling (smooth) compared to 3.2.5.1

Wifi signal is also better and does not have strange behaviour...

Back to 3.2.4.
[Galaxy S II Original Android Development] androidkid311:
Nothing to do with kernel. Go to manage apps then all and clear media storage mate :D
[Galaxy S II Original Android Development] johnbeetee:
look overthere:

http://xdaforums.com/showthread.php?p=26454017&posted=1#post26454017

specific thread for these kind of questions..
[Galaxy S II Original Android Development] pikachu01:
Hey gokhan, kept having kernel panics (kernel reboots, but the OS didn't) with the Galaxy S logo but no boot sound.

I'm not sure if my kmsg survived it, as I've said, let me know which part I should look for and I'll troubleshoot this quickly the next time around :)

Both kmsg and last_kmsg is here:

https://www.dropbox.com/sh/s0lhmhpk7m9dif8/YvR6x_PW2s
[Galaxy S II Original Android Development] PedroMRP:
No. I'm using superuser 3.0.7
[Galaxy S II Original Android Development] pikachu01:
Can you describe what does slow-mo means to you? I.e. What apps you were using while the slow-mo was happening, touch becomes insensitive or apps become very slow? What triggered the slow-mo?
[Galaxy S II Original Android Development] PedroMRP:
I explain that in my previous post. But what happened was that chrome beta become very slow with freezes, ie yesterday when i was trying to google for something chrome slows down than back to normal an than slows down until it freezes and i can exit the app neither return to home screen by pressing home button and finally the fc dialog box appears.
[Galaxy S II Original Android Development] gokhanmoral:
actually that was not the slow-mo bug that I was talking about.

the one that bln caused was somewhat different.

it was slow-mo all the way until you reboot... the phone was becoming completely unusable and you see no force-close.

the one you experience is different and may be app, rom or tweaks related.

I also use chrome beta mostly and I never experienced that problem.
[Galaxy S II Original Android Development] jim-bo:
That is almost certainly just the app suffering a crash and a force-close. Chrome is beta software still, and does still have bugs.

What you are describing is perfectly normal behaviour for a crashing app on ICS.
[Galaxy S II Original Android Development] johnbeetee:
Question:

some roms are pre-rooted like Hydrogen for instance.

It installs SuperSU. Siyah installs superuser.

Would it be advisable to de-install/freeze SuperSU, to prevent any problems or can they co-exists without interfering with each other?

Up to now I don't think it ever gave any problems, but I can't be 100% sure, seeing all the discussion on this issue...
[Galaxy S II Original Android Development] gokhanmoral:
v3.2.5.2 is released.

it will force-install superuser.

you will be able to update it but it will force-install superuser once after you flash it.
[Galaxy S II Original Android Development] tolis626:
Well,too high down differentials aren't really a good idea.I'd bet you'll see a similar,if not the same,behavior in ondemand and hotplug governors with high down differentials. ;)

Since I see you are getting lots of them,I'm gonna try the usual stuff.

What bootloader are you using?Did you observe if there is a repeating pattern behind the kernel panics?Like using some app or enabling some stuff in ExTweaks,SetCPU or similar app?I wanted to say something else too,but forgot about it. :p

And to all those who still have the slow motion bug-It's gone.Or at least for the most part.If you still get it,do what Gokhan suggested,which is removing root in ExTweaks and rebooting with the Auto-install root option checked.Also,update the SU binary,even if it's up to date.Superuser or SuperSU,doesn't matter,I used to get it with both.It's also not CPU governor and I/O scheduler related.It was BLN as it seems,and doing what should be done,I haven't got it again since Gokhan said it's fixed.Anything else is just misbehaving apps.Clear app data perhaps? :)
[Galaxy S II Original Android Development] pikachu01:
First time I got these kernel panics. It was when the USB is connected (kmsg states that). Gokhan did some troubleshooting and released a new kernel that might fix it. Haven't got the kernel panics so far.

Down_differential of 10 is the default for the ondemand governor :) With it, the CPU frequency doesn't stay a lot in 1.2GHz. It was in pegasusq that I noticed this problem. Not sure why though.
[Galaxy S II Original Android Development] ssauger:
Will this affect also second rom?
[Galaxy S II Original Android Development] MaKTaiL:
What about the people who already have SuperSU?
[Galaxy S II Original Android Development] gokhanmoral:
they will lose it and have superuser after installing v3.2.5.2.

but after flashing and rebooting for the first time you can reinstall supersu from the market if you want to use it.
[Galaxy S II Original Android Development] Bonscha:
What about NTFS HDD support? Like 2.5"/3.5" HDD with external power cord?

Can't check NTFS flash drive support out at the moment, but my WD myBook doesn't work.
[Galaxy S II Original Android Development] bclark:
Well the new update just was released but I just got a weird freeze with 3.2.5.1. Screen froze then suddenly started slowly fading to black

Last kmsg

http://db.tt/tWAezamd
[Galaxy S II Original Android Development] Tungstwenty:
In fact the SuperSU app is probably still there and you only need to open it so it complains that the su binary is not its own and suggest updating it, right? Or are you not only replacing su but also removing the SuperSU app?

IIRC you can have both SuperSU and SuperUser APPS installed and whenever opening either of them it will check if the su binary is the appropriate one.
[Galaxy S II Original Android Development] gokhanmoral:
hmm, you are right..

I have reuploaded 3.2.5.2 by modifying the script a little to remove supersu apk files on first boot. thanks for pointing that out.
[Galaxy S II Original Android Development] Tungstwenty:
That's not exactly what I meant :D

Probably the best behavior is to leave SuperSU.apk (if it's there) and merely install Superuser.apk and its binary. Those who eventually wish to move back to SuperSU mechanism would only need to open the app and accept updating the binary, instead of needing to go to the market. Those who want Superuser or don't worry about it, just need to respond to its prompts.

No big harm done in leaving SuperSU there ...

Either way, I'm good. Just clarifying my previous thought ;)
[Galaxy S II Original Android Development] paryav:
Why?

I am using SuperSu. It's no problem.

1. Run superSu - grant root permission for it in superuser request.

2. SuperSu update su binary.

3. Run Extweaks and disable autoroot.

4. Uninstall superuser.

If yuor uninstall SuperSu it's more steps to replase superusers with superSu.

Please nand secondrom. I am waiting...
[Galaxy S II Original Android Development] Josuhu:
Problem with dual boot

Here is my problems and how it happened.

- I had second rom installed.

- I fully deleted it in CWM dual boot options.

- Then directly after well done delete I made CWM to make clear cache in dual boot options for the second rom.

- Everything went great exept I seem to have lost about 2gb of internal memory.

How to get the lost 2gb back ?

This might be a dual boot bug that I dont want to regenerate for anyone just show that it really happened ;)

EDIT: With these lost 2GB I mean that the kernel somehow got mixed up and made double reservation after this procedure. Cant get them back even by deleting the second rom again in CWM.
[Galaxy S II Original Android Development] jim-bo:
Clearing the cache and data for it effectively recreates a blank second rom

have a look on your sdcard for folder called

.secondrom

with files called data.img and cache.img in it. If you don't want dual boot, delete them, including the folder
[Galaxy S II Original Android Development] Phistachio:
Gokhan, how can I force the .ko file of DSP manager so it works with Siyah?
[Galaxy S II Original Android Development] gokhanmoral:
Just delete second ROM in recovery. Wiping data and cache recreates them
[Galaxy S II Original Android Development] gokhanmoral:
Is there a module for it? If it is open I can add it to next version. If not you may not load it.
[Galaxy S II Original Android Development] Tye:P:
Auto-mounting is handled by vold.fstab. (Backup before any changes)

To auto-mount to different location:

You'll need to create the new folder that you want to auto-mount to and make sure it has the right permissions then edit vold.fstab to mount to that directory.

It's the line after '# USB storage device'. Change default mount point (/mnt/usbdisk) to newly created directory, it should auto-mount there by default now.

To unmount external storage:

At terminal as SU: umount (followed by mount point eg. /mnt/usbdisk)

To turn off auto-mounting:

Delete '# USB Storage device' lines in vold.fstab

Also see this post:

http://xdaforums.com/showthread.php?p=26286381&highlight=ntfs-3g#post26286381

Any further questions should probably be asked in the discussion thread here:

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

before we both get in trouble.
[Galaxy S II Original Android Development] Josuhu:
Thanks for your Help. I found the secondrom folder with my computer and deleted it. Seems to be fine now ;)
[Galaxy S II Original Android Development] nedooo:
mDNIE tune

Hi gokhanmoral, you seem like man who teaches other developers a lot, so I thought that you might be the one who will add mDNIE tune like in FLUXI kernel which is just for AOSP ROMs.

Thanks, and I hope you will make this happen on Samys ROM.
[Galaxy S II Original Android Development] RovG:
Will removing supersu.apk be enough to uninstall it properly and cleanly? The reason that I ask is that within SuperSU app there are specific cleanup options. See screenshot.
[Galaxy S II Original Android Development] gokhanmoral:
you can call it anti-brick patch for samsung emmc chips.

https://github.com/gokhanmoral/siyahkernel3/commit/9b488c578fccd916192649ec93beaf348894228b

although update4 sources are safe, I applied it anyway because it will prevent further bricks if someone takes the sources from my repo and apply some new mmc patches from newer samsung sources on top of it.

we already have some mdnie tunables.

and somebody have already suggested a value to prevent yellow tint in this thread (you have to search)

if you guys can suggest some defaults in the other thread (general section) I can add some presets to extweaks.

I don't want to add a slider having values of 0 to 254...
[Galaxy S II Original Android Development] gokhanmoral:
removing the apk, removing su binary and clearing the dalvik cache should be enough.
[Galaxy S II Original Android Development] fasst:
What are the improvements, if any, of the new wifi driver introduced with v.3.2.5.1 ?

The only thing I experience is lower signal strength, also with v.3.2.5.2.
[Galaxy S II Original Android Development] Mister Jozo:
Why are you using Superuser instead of SuperSU?
[Galaxy S II Original Android Development] fridlack:
Same problem here with wifi signal
[Galaxy S II Original Android Development] droidphile:
Writeup on kmemhelper for those who are interested. It's a powerful thing to use if we know of many static symbols in the kernel.
[Galaxy S II Original Android Development] Josuhu:
Dual Boot problem solved.

Hey Gokhan,

Few pages ago I asked help for lost memory after these steps below and there really happened a memory loss. I figured it out. The lost 2GB of memory where dumped in to SDcard/Lost Dir and they where not in Secondrom file.

Steps and screenshot are below. Problem solved, but maybe there is something that might be worth to look at.

- I had second rom installed.

- I fully deleted it in CWM dual boot options.

- Then directly after the delete I made CWM to make clear cache in dual boot options for the second rom.

- The CWM erased the latest Secondrom data but at the same time had lost the previous secondrom files in to the SDcard/Lost Dir. Or then I just had very bad luck :)