yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] rlorange:
GM some users in this thread:

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

Are claiming that they can use 300mhz GPU frequency with Antutu CPU master app from the market. Is this possible? Something you could implement in Siyah?

Edit: well I'll be damned! I thought this was only a paid app but there it is 300mhz GPU!!
[Galaxy S II Original Android Development] Napalm Candy:
I'm on 2.3.5, now Wifi problems here. I'm on default profile 200-1000Mhz CPU no UV. Pegasusq governor.

Today I had a slowdown when recording a 1080p video, nothing response, video update at 3 or 4 seconds every frame so slow.... I need to restart it.

Never happens before recording a video.
[Galaxy S II Original Android Development] Ritesh:
Random reboots on 3.2.4 and 3.2.5.2 after ExTweaks fuel gauge reset,

I am getting reboots on my device, with both 3.2.4 and 3.2.5.2

The situation:

On Siyah 3.2.4:

About 7-8 hours back I restarted the phone and Observed a 20-25% dip in battery after restart. I waited an hour or so, and then restarted the phone again, saw another dip of about 15%. So I reset the fuel gauge using EXTweaks.

After this, I got multiple random reboots. Tried to reproduce the problem, and found that this is happening when i try to access settings submenus ( battery meter view, or apps running view) . Although there were a few instances outside of this too.

Guessing this is may be due to rogue apps on my device, I did a Cache wipe, dalvik wipe. No change - Random reboots again. Following that, I did a full data wipe. I still had random reboots.

An hour back I upgraded to Siyah 3.2.5.2. I see the same problem, still exists. If I access settings ->Applications->Running->All->Running Items, the device restarts.

Thr trigger for these reboots clearly was the fuel gauge reset. No new apps installs. no other tweaking. I haven't experienced any 'perceived' slowdown of the phone. though I do see an excessive battery drain.

Attaching the last_kmsg and logcat here if this helps with investigation. If you want me to run any specific tests let me know.

Can't map it to any of the issues raised earlier in this thread. Thanks for the help.
[Galaxy S II Original Android Development] tolis626:
Quite frankly,that's bull****.Probably something wrong in the app.Check it yourself.Lock the GPU clock to 300MHz and then to 267MHz.Run benchmarks(Nenamark 2 does the job) and you'll get exactly the same scores.300MHz also wouldn't run fine with 950mV like my GPU does with 267MHz,so I think this myth is busted. ;)
[Galaxy S II Original Android Development] SPBoss:
well i don't know because pc gpu's can be clocked by 1mhz increments. there's probably a hardware based restriction or the architecture may only allow steppings at set frequencies.
[Galaxy S II Original Android Development] Tungstwenty:
Looking at this bit from the last_kmsg:

<2>[ 107.585217] EXT4-fs error (device mmcblk0p10): ext4_readdir:214: inode #68154: block 269638: comm installd: path (unknown): bad entry in directory: directory entry across blocks - offset=0(0), inode=170427146, rec_len=17248, name_len=65
<3>[ 107.585315] Aborting journal on device mmcblk0p10-8.
<0>[ 107.604789] Kernel panic - not syncing: EXT4-fs (device mmcblk0p10): panic forced after error

I'd say there's a filesystem problem on the mmcblk0p10 partition, or /data.

What method did you use to wipe the data, as you mention?

Perhaps some other type of format is required for a proper cleanup of the entire contents, instead of a "quick format". mkfs or something similar???

Another possibility is that your wipe did clean it up, but the problem somewhat returns due to some problem.
[Galaxy S II Original Android Development] Phistachio:
I seem lost on where to find it... Could you direct me please?

Also, can you simply apply the same patch as CM9 did with DSP Manager to make it work on your kernel? I unfortunately cannot find the commit atm.
[Galaxy S II Original Android Development] tolis626:
Well,if I know these things well enough,in SoC's used for mobile devices,things aren't as "simple" and components aren't independent of each other.I think that the GPU stuff is a hardware limitation-the regulator doesn't accept values other than (800/n)MHz,n=1,2,3...So,above 267MHz are only 400MHz and 800MHz.I suppose we all can rule the last one out. ;)
[Galaxy S II Original Android Development] gokhanmoral:
I think Tungstwenty is right.

I recommend you to do a full wipe again.

a simple fsck may fix it but formatting data would be a better solution.

and if it happens even then make sure that you don't use any optimization script that enables writeback or disable any fsync feature if you ever use another kernel (we don't have that option in siyahkernel) because that kind of ext4 problems usually occur when you have crash (or force-boot) your device with those kind of mods.

but if you still have the problem without having any of those test stock rom+kernel for a while. your flash may have been worn out. there is no quick/full format for our devices. in that case the only solution is the service center.
[Galaxy S II Original Android Development] pikachu01:
Getting an error after leaving wifi range, and then phone activates HSDPA. Wifi fails to suspend:

<4>[ 9007.335004] ##> wifi_suspend
<4>[ 9007.335025] wifi_suspend no driver data
<3>[ 9007.335063] pm_op(): platform_pm_suspend+0x0/0x64 returns -16
<3>[ 9007.335097] PM: Device bcmdhd_wlan.1 failed to suspend: error -16
<3>[ 9007.335129] PM: Some devices failed to suspend

When I woke up my phone, saw that I forgot to deactivate wifi, I turned it off using a widget/using the button on "Settings", but it went back to on. Going into the Wifi settings and turning it off then pressing back results in a kernel panic.

Here's the full last_kmsg:

http://db.tt/CDyIJ2NY

As usual, I'm using the latest Siyah ;)
[Galaxy S II Original Android Development] vertrag:
i have random freeze too and is hard to catch the most informative last kernel msg...

When i check after reboot the last kernel msg doesnt seem catch the problem
[Galaxy S II Original Android Development] timberwolf60:
Using 3.2.5.2 since yesterday had no problems untilled I using wifi tethering, it last me few minutes and it turned phone connection off and the wifi tethering icon in the status bar on. Trying reboot the phone and it have the same problem. So I flashed back to 3.2.5.1 and the problem solved. Anyone facing this problem.

**********

I am flashing back to 3.2.5.2 and this time the above problem solved.

Send from my GT I9100 with Gary's DXLP9 using Tapatalk2
[Galaxy S II Original Android Development] codeworkx:
Just for Information:

Afaik it's a kernel bug where MMC_ERASE leaves the MMC in an undefined state.

This problem was known to occour on N7000 only while using the I9220 leaks. Looks like the problem is more bad than everybody thought.

I didn't have a look at the siyah code. Maybe the bug got in while merging with other sourcecode releases from other exynos variants.

Since CM dosn't support any SHW-M250 variant, we'll not take action.

If users are flashing I9100 kernels on their SHW-M250, it's not a developers fault.
[Galaxy S II Original Android Development] xxxstar123:
in miui rom it has it own superuser (LBE Guard) when I flashed siyah 2.5.2 with miui rom I have seen superuser is been installed and LBE is most likely off, I hope that will be fixed in 2.6. good luck and thank you very much, donated :)
[Galaxy S II Original Android Development] Crescendo Xenomorph:
@GM: I'm using v3.2.5.2 now. I got one issue about nandroid again.

After I do full nandroid backup, it delete every apps I got in SD.

So I need to restore it using TiBu.

I'm using stock XXLPS.

Could you please check for it?
[Galaxy S II Original Android Development] gokhanmoral:
thanks for the warning.

I am being very cautious about mmc part after our bad rebase-to-m250l experience in 3.1rc6. I think I will keep it in as it is in update4 sources for a while.

and just as a precaution I applied this: https://github.com/gokhanmoral/siyahkernel3/commit/9b488c578fccd916192649ec93beaf348894228b

and for cwm recovery, I remember there was an int vs long long difference somewhere in wiping/mkfs part which I should check again to be able to tell the exact location.

it gave me a headache while trying to support formatting secondrom data.

if there is no barrier in that formatting function (I did not check it deeply), converting long long to int in CWM recovery without a proper method may result in a negative number and that negative number may result something undesired...
[Galaxy S II Original Android Development] Ogy77:
Can you answer is safety flash Siyah kernel,give us advice if we on bad way:D.
[Galaxy S II Original Android Development] Vaedryn:
Nothing in life is 100% Safe:) but i know Gokhan knows what he do so i am sure it is to 99% safe:)

Cyanogen (mod) 9
[Galaxy S II Original Android Development] gokhanmoral:
I always recommend flashing stock kernel to those asking that question :)

but wait... that bricking problem happened with stock kernel as well...

so... how can we make sure we will not have a bricked device after flashing a kernel?

if anyone knows the answer of that question please tell me because I don't know the answer to that one.

I just try not to enable some CAP_ERASE or anything related with mmc which is potentially dangerous..

nobody was thinking that samsung emmc chips had a firmware bug which wipes some parts which should never be wiped.

and we have a safeguard for that in the kernel.

but I cannot tell you that it works because I did not try it on new kernel base.

for now, I just cherrypick some usb, mali and wifi related parts from the new kernel sources and do not touch mmc part..
[Galaxy S II Original Android Development] codeworkx:
since gokhanmoral is probably developing on a I9100 he can't know if it's working on the korean version. Also non of the CM-Team is owning a korean variant.

If you wan't to make sure, try to get a developer with a korean version on it.

we'll definately not support the korean version until some real developer approved everything. so for now, it's fully your own fault if something goes wrong because you're flashing a kernel/rom to a unsupported device. It's like driving without a license. ;-)
[Galaxy S II Original Android Development] NiceCarpet:
Yes, please fix this. I can't seem to get LBE back on now.

Thanks!

MIUI ASNET v2.5.20

Siyah v3.2.5.2
[Galaxy S II Original Android Development] freregiovannipietro:
Gokhanmoral ... thank you for working on new usb host driver (works fine with mouse, usb sticks and serial port adapters) ... is it possible to use the cable mhl for the screen, and utiliiser usb host (for mouse and keiboard)?? this can possibly afford to replace the PC??

I have v3.2.5.2 and I9100XWLPD stock ... The battery is OK, no bug, really smooth ...
[Galaxy S II Original Android Development] Ogy77:
Thank you for answer,I dont scare to flash for good performance,battery life,etc,but in my f#cked country we dont have samsung repair centre,have some small service who order something from ebay and then we must wait almost mounth to delivered and question now does someone know to replace motherboard or something alse,this is reason why I ask:).Sorry I am from Bosnia,but I more loved Serbia:-)
[Galaxy S II Original Android Development] codeworkx:
Disassembling the device is pretty easy. Also reassembling it. Nothing special. ;-)

Takes about 15-30 minutes to replace the pcb. Can be done by everyone who's able to use a screw driver and is able to plug und unplug some connections.

Where to buy? Dunno, probably ebay.
[Galaxy S II Original Android Development] g00ndu:
I would suggest that you revert back to v3.2.4, where it does not break your LBE Guard. I am using v3.2.4 as of now. Let's give Gokhan some breathing space so that he can concentrate on solving the more important issues right now.
[Galaxy S II Original Android Development] Tungstwenty:
Terminal while in recovery

CWM recovery keeps evolving and I'm not sure what's in the master sources and what gets added by others such as GM (e.g. second rom).

One idea that came to my mind today is the possibility of having an option on the menu to open a terminal + touch keyboard, so we could do pretty much everything while on the go and not require adb and a PC connection for those "safe mode" operations that aren't on the predefined list of menu options.

Does this make any kind of sense? Is it feasible and worth the effort? Does it belong upstream, and if so, who can I suggest it to?
[Galaxy S II Original Android Development] Frozenthunder:
How is this meant? Am I supposed to remove root after I flashed the newest kernel, restart my device and then root again? Or must I remove root before I flash the kernel?

Also, sorry if this is the wrong thread. I was not sure since this is actually a question to gokhanmoral.
[Galaxy S II Original Android Development] gokhanmoral:
it is already answered in the other thread.

removing root and restarting will reinstall superuser in siyahkernel if you do not uncheck "autoroot on boot" option.
[Galaxy S II Original Android Development] Ogy77:
Ne ebay,I buy in one shop,but not official samsung or something like that.
[Galaxy S II Original Android Development] DomButcher:
Hi all,

I don't know, which key words should I use for searching my problem in this huge thread, so I rather ask. :)

I tried to install one Sammy ROM as my 2nd ROM, but after flashing and rebooting I don't see any prompt to reboot to 2nd ROM and in recovery my status says : No 2nd ROM installed (or something similar). I wiped data/cache and dalvik-cache before flashing. I even tried to flash Siyah kernel after flashing the ROM, but nothing helped.

Thanks a lot,

DomButcher
[Galaxy S II Original Android Development] ephraim:
Try first cloning your primary rom to 2nd rom. Flash stock rom as primary then swap the two. That's what i did. When i first tried to flash a stock rom without an existing 2nd rom it didn't work. Try it and post at the siyah thread over at the general section buddy for inquiries. This thread is reserved for development purposes :)
[Galaxy S II Original Android Development] Fire_Paul:
it's not exactly what I needed... ))

I need to know, how to change mount point for NTFS-sticks from /nmt/ntfs to other in SiyahKernel v3.2
[Galaxy S II Original Android Development] gokhanmoral:
mounting ntfs sticks are managed by /sbin/hotplug script which is called on every plugging and unplugging operations and it includes usb sticks.

you can write a script which mounts rootfs in rw and replace that script to modify the location.

OR

you can create a symbolic link to /mnt/ntfs/sda1

I would choose the first one...

just create an init script which will

1- mount -o remount,rw /

2- rm /sbin/hotplug

3- echo some lines to /sbin/hotplug to create the string you have prepared

4- chmod 755 /sbin/hotplug

5- enjoy
[Galaxy S II Original Android Development] t00dy:
don't understand quite, but :D

check ASWO they have franchise in Sarajevo or Belgrade (whoever you love more) and ask for motherboard, samsung code GH82-05732A or design LOC QMP01. The price is quite high, around 260 € i think :/
[Galaxy S II Original Android Development] Ogy77:
Thank you but I dont need motherboard,thanx God.I live in Bosnia,but my heart belongs Serbia:).
[Galaxy S II Original Android Development] Tye:P:
To Gokhanmoral,

'fixed ntfs mounting' - Was there a bug related to the above hotplug script? Why does kernel 3.2.2 mount flash drives to mnt/usbdisk rather than /mnt/ntfs even though the above script exists?

Is the ntfs-3g added back to the kernel the latest version (15-01-12) and if not is there any good reason why? I'm thinking of compiling it and trying it out, but if your including it already there's not much point. The reason I ask is the version in the kernel I'm using is about 7 months old and haven't seen anyone else using the latest so I thought maybe there's a problem with it I don't know about.

I've been trying to learn as much as possible about ntfs in the kernel and in general, everything I have so far learned has come from hours of searching the threads and even that is very little. Any comments or direction to a resource would be much appreciated.

PS. Could you clarify the changelog entry mention of the usage of the ntfs mounter application? Is this for auto-mount of ntfs-3g RW only, otherwise Linux Kernel ntfs (RO) is used.
[Galaxy S II Original Android Development] gokhanmoral:
I am using the older version but there is no specific reason for it.

I just didn't have any problems with that one and kept it...

and v3.2.6 is up, by the way :)

if you have ntfs mounter app, the hotplug script will not mount anything...

if you don't have it, it will mount to /mnt/ntfs/sdXX folder in read only.

I will add a simple button to extweaks to make it rw and make it back ro...

but I didn't have time to do that today.

I will be away for some time (tomorrow and the weekend)

I hope v3.2.6 will work fine..
[Galaxy S II Original Android Development] so_ony:
fast updates as hell ! Good job !

Very great kernel and support is also best !

---------- Post added at 06:01 PM ---------- Previous post was at 05:03 PM ----------

Hey !

Flashed your new Kernel and have to say that i noticed a little problem. If my phone goes into deep sleep and you wanna wake it up it takes about 5 seconds untill display reacts for unlocking or taking the call of the person who is calling me. Reflashed your 3.2.5.2 Kernel and everything is working fine. Don't know if it is a kernel problem or whatever ;)
[Galaxy S II Original Android Development] ephraim:
It doesn't happen to me.

Edit: it reacts as soon as the screen goes on.
[Galaxy S II Original Android Development] Heroeagle:
after flashing 3.2.6 i think that the screen has a noticable blue tint
[Galaxy S II Original Android Development] ssauger:
I think its cause the low gpu clock of 66 MHz, try to increase like in older version.

Edit: and i cant set lower CPU speed than 1200 Mhz, 1200 is allways in use with default gov.
[Galaxy S II Original Android Development] aashgaur:
cpu - pegasusq .. 18 steps ... 200 - 1000 ... where shud i set the smooth scaling ?? 1000 ?? or 800 ?
[Galaxy S II Original Android Development] Heroeagle:
also happened with me the screen gives no respones for seconds then i can unlock my phone
[Galaxy S II Original Android Development] timberwolf60:
"disabled force-install of superuser but I highly recommend you to “remove root” in extweaks and restart after flashing this kernel to prevent lockups and force-closes."

Did you fellow above as it mention I. GH site.

Send from my GT I9100 with Gary's DXLP9 using Tapatalk2
[Galaxy S II Original Android Development] Vaedryn:
With the latest update the phone works like butter, with this feeling i think i sell my coming S3 :D

Can't find any problem for now, wifi looks good again, connect very fast.

Great work Gokhan. Thank you again. Have a good time when you are away.

Best Regards.

Cyanogen (mod) 9
[Galaxy S II Original Android Development] angelshie:
^

...from Siyah V3.2.6

hi gokan, please explain how this, what do you mean remove root? is this means i will not be rooted anymore after installing this update?

currently i am on SiyahV3.2.5, and am loving it because Deep sleep is perfect.
[Galaxy S II Original Android Development] manny05:
If you open extweaks and go to misc you'll see the option to remove root. Press it and then restart your phone..that's it

The kernel will automatically root your phone once it boots up

Sent from my GALAXY.
[Galaxy S II Original Android Development] Heroeagle:
at first time i followed what GM said but the problem happend ... i tried again and i think it is fixed now :)
[Galaxy S II Original Android Development] Rankec:
usb-host driver is better now. i can use my keyboard without kernel panic. but there is still a bug with connectet mouse. you can't go back with right click.

hope for a fix.

and thank you for this wonderful kernel :)
[Galaxy S II Original Android Development] Markox89:
It happens also to my phone, I'm on stock rom, with 2.3.6 and battery profile.
[Galaxy S II Original Android Development] so_ony:
Have you activated the battery script in cwm Mode?
[Galaxy S II Original Android Development] gokhanmoral:
Try increasing GPU frequency or just use default profile. It is also very battery friendly . I cannot remember the differences but you can compare /res/customconfig/battery.profile and default.profile files . I don't test battery profile and only make some changes when I receive feedback. It is better to start from default and create your own profile.
[Galaxy S II Original Android Development] mrsilva1986:
Hello, im having the delay too and im in the default profile without any changes in extweaks. Any ideas?

Sent from my GT-I9100
[Galaxy S II Original Android Development] angelshie:
^

updated kernel to v3.2.6, reboot and seems fine however i still open

extweak>misc>remove root and restart.

again went back to extweak>misc> un-checked auto install root, because i dont want to auto root everytime i need to restart for some reason. is this correct????

i will share my observation later just resetted cpu spy timer, i will checked deep sleep mode if same as latter version.
[Galaxy S II Original Android Development] wurzelsepp3:
3.2.6 seems to be the best one yet. Cpu stays at lower frequencies more often and the phone is still smooth as butter.
[Galaxy S II Original Android Development] JimboJoe:
Same here with default profile and BLN activated...
[Galaxy S II Original Android Development] Markox89:
Don't know if this is usefull but I've noticed that if BLN shows and wakes the phone (I intend without turning on the screen) after, when I turn on the screen, there's no this kind of problem.

EDIT: no problem in charge mode, so it seems deep sleep related.
[Galaxy S II Original Android Development] ssauger:
For me in default profile the lowest gpu clock is set to 66 Mhz, try to encrease and see if your problem is solved.
[Galaxy S II Original Android Development] hellsgod:
here you have a logcat which maybe tells something about wlan probs. i turned it on, saw my avaiable networks, but was not able to connect to them. turned wlan off an on, was the same, one mor time off and on and it was able to connect.

oh, and btw. i'm on siyah 3.2.6

hells
[Galaxy S II Original Android Development] mrsilva1986:
Just another thing. I usually never had wifi probs but for the first time i have low signal.

The rest seems fine.

Sent from my GT-I9100
[Galaxy S II Original Android Development] thunderteaser:
Thanks for your efforts, gokhan! You've become some kind of a god for the SGS2 community! :)

Siyah development seems at a stable point now, so here I am with my feature request :p: what about implementing didle (deep idle)?
[Galaxy S II Original Android Development] Boat Traveller:
What GPU setup is the most battery friendly ?

40/133/267 or 100/160/267 ?

thx !
[Galaxy S II Original Android Development] Ritesh:
Solved : kernel panic due to problem in /data partition

An Update:

Thank you both @Tungstwenty and @gokhanmoral for your responses. I followed what you said and I haven't had a reboot in last 5-6 hours. For now it seems I have averted the service center scenario.

It was quiet a situation, as I was not able to take a back up of my device. The moment Nandroid Backup reached /data every time, the device restarted due to the partition being corrupt.

If it helps others, I must highlight, that I had to wipe both /system and /data from CWM followed by a new install of the ICS ROM (I9100XWLPD).

Thanks guys. Now time to upgrade to Siyah 3.2.6 .
[Galaxy S II Original Android Development] Ritesh:
Read droidphile's thread here for that information.
[Galaxy S II Original Android Development] Boat Traveller:
Thx I've read the thread but i still don't know what's the better for battery.

For now i've set the steps with 40/133/267 and the go up and down thresholds 85/30/100/40
[Galaxy S II Original Android Development] coloxim:
GM said that is possible have same app but not same data...or not?

Inviato dal mio GT-I9100 con Tapatalk 2