yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] gokhanmoral:
I was not following other threads after moving to S3 and didn't know that he quit.

I think it is very unfortunate because he is one of the few devs that can do something original.

sometimes users are very cruel, sometimes ignorant and even disrespectful in their comments.

"the best" definition is subjective and sometimes devs should just ignore some posts in order not to lose motivation. because nobody says "it is the best for me" or "I have this and that bug and you can reproduce those doing this and that". they just say "wow!! the best!!" or just "buggy! stay away!!".

I hope he will resume his work some day, either with S2 or another device.

EDIT: forgot to respond to CFS question. you can see the defaults in /res/customconfig/actions/cfs-tweaks file.

it simply modifies cpu scheduler latency and granularity values. samsung default is the same as the one used in 2.6 based kernels and I find using linux defaults make the device more responsive although they tend to decrease benchmark scores. I have also added pikachu's thunderbolt script defaults which may be a better choice but I did not make it default to be on the safe side.
[Galaxy S II Original Android Development] alex__sp:
You are totally right about this,Being "The best" it's up to the person and the user and that doesn't mean something else can't be "the best" for somebody else.

I couldn't agree with you more!
[Galaxy S II Original Android Development] Farkonian:
Same for me, Wannam Lite 12.2, didn't try mobile odin flash, just went back to 3.3.2.
[Galaxy S II Original Android Development] snakefreak:
Runing v3.3.3 with lp7 runs very smoth!

Have not testet a lot yet.

Gokhan i tried to rebuild dvb-t driver moduls. But it fails.

Dmesg says:

[ 6176.561555] dvb_core: no symbol version for module_layout

With older git sources from yesterday it worked (i modified vermagic in makefile for kernel 3.0.29 i used before ) played a litle with modules because i want to watch dvb-t tv ;-)

Can you tell me your toolchain?

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] :
You are totally right. There's no such thing as best kernel. I got very disapointed when fluxi announced that he was quiting. Not just because I really liked his work, but the way people lead him to quit.

Benchmarks are bull****. If it increases my performance, it's okay, I don't care. I was using ThunderBolt CFS and could see a little difference. Thanks for the explanation.

I see you included remount scripts there, but are they working? They need to be executed after boot, so it can get applied.
[Galaxy S II Original Android Development] faraaz:
Version 3.3.3b is online xda-members... I got problems with v3.3.3. Gonna flash v3.3.3b now...
[Galaxy S II Original Android Development] :
What kind of problems?
[Galaxy S II Original Android Development] faraaz:
Random reboots, seems to be solved with the new version. Several people had the same problem (see Siyah thread in general section). So far everything is running smooth with v3.3.3b!
[Galaxy S II Original Android Development] alex__sp:
I had no problems but I just flashed 3.3.3b just to be sure.

:good:
[Galaxy S II Original Android Development] Frozenthunder:
I've had the same bug now twice within 2 hours while browsing: Sometimes Evey input just stops working. Neither power key, nor volume, touch keys, home button or touchscreen work while the system itself remains running (because stuff on the display keeps changing, therefore apps and system are still running). using 3.3.3, don't know if this is fixed in 3.3.3b
[Galaxy S II Original Android Development] toxicOne:
Strange for me jt works...

Send via Tapatalk SKYBLUE DELUXE ~ MOTOROLA XOOM2 ME
[Galaxy S II Original Android Development] pikachu01:
Try changing the CFS to Samsung defaults or ThunderBolt!'s CFS and see if it fixes it.
[Galaxy S II Original Android Development] superlik:
just to feedback that the sliding at status bar to adjust brightness still activate the led in siyah 3.3.3b, tried stock cm9 kernel,dorimanx,fluxi etc that this has been fixed
[Galaxy S II Original Android Development] BrandoHD:
Was having freezes right after lock screen, I tried both Samsung and Thunderbolt, same issues, I had to reboot at least three times before I decided to change kernel and grab the logs, I hope the logs would've survived the kernel flash

If it's not attached, blame Samsung and XDA and probably Dolphin browser If you want to
[Galaxy S II Original Android Development] pikachu01:
Got an SOD. Attached. Seems like a gparted error? Or wlan? Ioctl? Not sure.

http://db.tt/VhyByXOu
[Galaxy S II Original Android Development] :
Can reproduce? I'm taking a look at your log.
[Galaxy S II Original Android Development] Farkonian:
3.3.3b fixed my problem, booted up just fine now. Thanks Siyah!
[Galaxy S II Original Android Development] moneyover:
Edit...Wrong forum
[Galaxy S II Original Android Development] #illidan:
This is a dev thread so people please let's keep it to that & don't clutter it up with not only discussions about the usual ot bits also with discussions about other kernels. There is a separate discussion thread for all of this so kindly take it over there.
[Galaxy S II Original Android Development] mtrax:
Just install the siyah 3.3.3b kernel on the RR 2.5.3 ROM.

mostly ok , but I have two issues.

1. when I connect OTG cable and switch back to standard USB cable for ADB

system hangs and reboots.

2. I can't get OTG to recognise my USB device , note used to work with SG2 running RB but not ICS. and works with the Xoom Team EOS ROM, so why not SG2 ROMS?
[Galaxy S II Original Android Development] pikachu01:
Nothing so far. It's a one off issue right now. I'll try to reproduce it if I can.
[Galaxy S II Original Android Development] viscocesco:
Flashed now on Miui Rom, boot without problem and seems work very well.

Thank you!
[Galaxy S II Original Android Development] zaphod777:
NTT Support?

Any reason for dropping support for NTT in 3.3.3? 3.3.2 worked just fine on NTT.
[Galaxy S II Original Android Development] marbulas:
Be careful... some of people here are unkindful when you're not a i9100 user and takling about supporting SGS2s not a i9100 :cool:

I just gived up few months ago and changed my ROM from stock to CM9...
[Galaxy S II Original Android Development] mtrax:
ok some progress on my OTG USB problem, now Android is saying my SD card (USB) is damaged, and both my Windows , Linux and my Xoom (EOS Rom) boxes have no problems with device
[Galaxy S II Original Android Development] icecore:
Just installed 3.3.3, since then i have 2 freezing screen and 2 random reboots,that starts from bootloader animation.
[Galaxy S II Original Android Development] LogeshMenon:
delete, wrong thread.. silly me
[Galaxy S II Original Android Development] #illidan:
Had a soft reboot on screen off. Log attached

Config:

CM9, siyah 3.3.3b, cpu & gpu uv, pegasusq, sio & thunder bolt cfs

DK being dark knight so are you even aware on which thread are you posting this?
[Galaxy S II Original Android Development] johnbeetee:
I'm starting to get a feeling that the problems are mostly occuring on non-stock roms??? Or is it just my imagination?

edit: ...nevermind, guess it's randomly distibuted stock vs non-stock
[Galaxy S II Original Android Development] vizdak:
3.3.3b works fine on rootbox 1.5. I only have one freeze after the kernel installation. Then I reboot and all is good for now.
[Galaxy S II Original Android Development] confusedmuse:
No. I'm using XWLPG stock and i have issues too. The phone freezes frequently with 3.3.3 and 3.3.3b.

Sometimes i get a soft reboot if waiting a few minutes, sometimes it just remains frozen...

Also sometimes i still can trigger the negative effect and animations (widgets, charging) are still running, but the screen can't be turned off with the power button.

Sometimes it's completely frozen: no animations, no negative toggle.

Maybe my UV isn't stable anymore with the new versions...

But i never had soft reboots while undervolting.... only freezes or normal reboots. :confused:

I'll try to stay with Thunderbolt defaults now for a while to see if it helps.

EDIT: Just had another freeze followed by a soft reboot after an hour with Thunderbolt defaults... (3.3.3b)

Reverting to 3.3.2 for now.
[Galaxy S II Original Android Development] diemadedrei:
Just had a complete freeze while browsing. Could be the browser but never had that before. I'm on 3.3.3b with cm9 latest. Unfortunately there is no last_kmsg file there. Anyone know why that is?
[Galaxy S II Original Android Development] #illidan:
Look for it at /proc/last_kmsg.
[Galaxy S II Original Android Development] Phistachio:
Only had 1 random reboot while charging. Other than that, spectacular performance. No home button lag anymore, cheers GM!
[Galaxy S II Original Android Development] Markox89:
Everything works fine for me on stock LPF with 3.3.3b ;)
[Galaxy S II Original Android Development] diemadedrei:
That's where it should be, I know but it isn't there
[Galaxy S II Original Android Development] zOe999:
Hi gokan did you Read This?

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] OrangePL:
Hm, the weirdest thing.

Flashed 3.3.3 yesterday evening and enabled the new 'deleted wakelock details' feature.

This morning, RILJ drained 30% of my battery while running for 4,5 hours during nighttime.

I'm not sure if this is related - but did anybody experience a similar behavior?
[Galaxy S II Original Android Development] Markox89:
For me RILJ wakelock is 30 seconds on 4 hours, normal. Me too with the new feature ;)
[Galaxy S II Original Android Development] robertobsc:
Unfortunately I had another freeze followed by soft reboot. Seems a lot of EXT4-fs errors in last_kmsg.

This is so bad, this version is just amazing in responsiveness...

Oh, just forget, my configs are:

3.3.3b

CFS Thunderbolt defaults

Wannamlitte xwlpg rom
[Galaxy S II Original Android Development] LogeshMenon:
is it possible to use the open source sensor for light sensitivity in siyah 3.3.3b like in fluxi?

I rarely use the compass, prefer the light sensor more. Would like to know this before testing with siyah.
[Galaxy S II Original Android Development] johnbeetee:
Ok...then could it be the newly added tweaks in tweaks.sh that are causing the random problems, and not agreeing with different device setups? As some people are having problems, and some aren't.

(duely noted: these are on their own good tweaks, coming from Thunderbolt scripts, but maybe not in every situation)

+# Remount all partitions with noatime
+for k in $(busybox mount | grep relatime | cut -d " " -f3);
+do
+#sync;
+busybox mount -o remount,noatime $k;
+done;
+mount -o noatime,remount,discard,barrier=0,commit=60,journal_async_commit,noauto_da_alloc,delalloc /system
+mount -o noatime,remount,rw,discard,barrier=0,commit=60,journal_async_commit,noauto_da_alloc,delalloc /cache
+mount -o noatime,remount,rw,discard,barrier=0,commit=60,journal_async_commit,noauto_da_alloc,delalloc /data
[Galaxy S II Original Android Development] :
Get sensors.exynos4.so.os file at /sbin/xx/files/sensors [on fluxi], rename to sensors.exynos4.so and paste it on /system/libs/hw. Then you can flash Siyah again.

---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------

It was always there. It's from ThunderBolt! scripts, and the only problem pikachu01 reports is that it may corrupt your data.I also think that some sods and problems are somehow related to the mmc.
[Galaxy S II Original Android Development] minidou-77:
Sorry but home button lag CAN NOT be improved by kernel

Only the ROM effects this
[Galaxy S II Original Android Development] Gammelgustav:
One question:

Can I just replace images in /res/images/charger with own?

Like you do with bootanimations? :P

Sent from my GoaTrip Galaxy S2
[Galaxy S II Original Android Development] :
I don't think so. They are at the initramfs, so when you restart, the stock images will come back. Why not extract initramfs, edit and repack?
[Galaxy S II Original Android Development] Gammelgustav:
I'm not that experienced :D

But shut down and charge does not mean restart/loading Kernel, so it could work for one time each.. ;) :P

Sent from my GoaTrip Galaxy S2
[Galaxy S II Original Android Development] Kikko2000:
It is /system/lib/hw (instead of /system/libs/hw).
[Galaxy S II Original Android Development] cheewaca:
Hi Gokhan, is a pleasure see you again.

On XWLPG odex rom with first 3.3.3 version and default settings i have not issues.

All runs perfect. Thanks
[Galaxy S II Original Android Development] :
oops. typo, sorry. But it doesn't matter, there isn't libs but there's lib ;)

---------- Post added at 09:41 AM ---------- Previous post was at 09:40 AM ----------

Try yourself :) It won't work. [absolutely almost sure, kinda interesting]
[Galaxy S II Original Android Development] johnbeetee:
did a little bit of comparing...

remount with noatime has always been there for cache and data

new parts are for system

and all other mounts....
[Galaxy S II Original Android Development] edwardeutsch:
Installed 3.3.3, all was fine > Freeze > freeze after boot everytime with .3 and .3b.

Solutions?

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] :
Oh. Noticed this too.

Here's the main script for ThunderBolt!

#!/system/bin/sh
#ThunderBolt!

# Remount all partitions with noatime
for k in $(busybox mount | grep relatime | cut -d " " -f3);
do
#sync;
busybox mount -o remount,noatime $k;
done;

mount -o noatime,remount,rw,discard,barrier=0,commit=60,noauto_da_alloc,delalloc /cache /cache;
mount -o noatime,remount,rw,discard,barrier=0,commit=60,noauto_da_alloc,delalloc /data /data;
mount >> /sdcard/fsck.log;
echo "Remount Done! Please see /sdcard/fsck.log for your new mount options.";
echo "If this script works, you'll see most of your mounts being noatime, and";
echo "/data /cache having barrier=0 and commit=60.";

And here some words from pikachu01...

Note: The remount script is launched using Script Manager as any ROM lagfix will remount the partitions again later after init.d scripts finished launching hence reverting the mounts to stock lagfix mounts. This is true for MIUI/CM7, Voodoo and other lagfixes where partitions will be remounted to relatime just before Android OS appears, thus nullifying the init.d remount.The script then has to be launched only after the Android OS has launched.

Is the script being properly executed? I don't know whether the script is being executed after or before AOS. If before, then the script have no effect [or yes]. Either way, it may cause something to /system, preventing the system of loading stuff on RAM.

Also, the reason for setting it to /system is improve reading speed? [btw, sorry if I said something stupid, it's what I can conclude]
[Galaxy S II Original Android Development] andresousa90:
+1
[Galaxy S II Original Android Development] johnbeetee:
tweak.sh is called from post-init.sh, so I guess this should be ok...I'm just not sure about the rest (I just noticed that it was one the many small tweaks added, and might be accountable for the random spread of the problem ; other than that I can't find any logic in the problem not being consitent...)

GM will certainly have a look at it ( he has a far more better comprehension of it all than me....)
[Galaxy S II Original Android Development] pikachu01:
It doesn't affect reading speed. System is in RO mode hence atime updating won't happen.

Also, got another SOD. Uploading now.

http://db.tt/nlxgaMAz
[Galaxy S II Original Android Development] zaphod777:
To support the NTT GPS it was a small patch that just required us to push a value to enable support. I just thought he might have forgotten since it has been supported for many releases now.
[Galaxy S II Original Android Development] :
What's your ROM? Are you using any mod or tweak? Sorry, I'm kinda out of ideas, I have to configurate an iPhone 4S [not for me, thank god] and it's been a freaking painintheass. #fkyouapple
[Galaxy S II Original Android Development] sefrcoko:
No problems or SODs with 3.3.3b on Wanam 12.2 UHLPS for me.
[Galaxy S II Original Android Development] pitum:
3.3.3b working perfect with I9100XWLPM (4.0.4) Stock

Thank you! :D
[Galaxy S II Original Android Development] pikachu01:
Even the camera too?
[Galaxy S II Original Android Development] Many40:
I posted in discussion thread my initial observations of 3.3.3b with two roms: stock 4.0.3 and AOSP 4.0.4. If someone is interested:

http://xdaforums.com/showthread.php?p=28497062.

Sent from GT-i9100 using XDA Premium.
[Galaxy S II Original Android Development] pitum:
NO!!!

:S

sorry no preview camara!
[Galaxy S II Original Android Development] pikachu01:
The ext4-fs errors are due to corruption on your /data partition. I'll upload a auto fsck CWM zip in ThunderBolt! thread later to fix this. Note however, that fixing it might render your phone unbootable caused by a lot of data in /data/lost+found that was recovered when doing fsck. Hence, do a Titanium Backup first (you can still boot to recovery) and use ADB to delete off the files in /data/lost+found.

Also note that formatting your /data will not remove off the leftover corrupted data in your /data. A format then fsck is the best choice.

I don't see any errors :/

Aside from GPARTED errors, I can see this:

[ 29.984266] dhd_wl_ioctl_cmd: WLC_GET_VAR: cisdump, error = -23
[ 29.984350] dhd_check_module_cid: CIS reading failed, err=-23
[ 29.985861] dhd_wl_ioctl_cmd: WLC_GET_VAR: p2p, error = -23
[ 29.986557] dhd_wl_ioctl_cmd: WLC_GET_VAR: p2p, error = -23
[ 29.986609] Firmware up: op_mode=1POWER_VAL = 1
[ 29.996395] dhd_customer_set_country: get country ccode:GB country_abrev:GB rev:0
[ 29.996452] dhd_customer_set_country: set country ccode:FI country_abrev:FI rev:0
[ 30.020712] [if_usb_suspended]
[ 30.075335] Firmware version = wl0: Jan 17 2012 09:18:41 version 5.90.100.311 (CCX)
[ 30.086970] Broadcom Dongle Host Driver: register interface [wlan0]dhdsdio_probe : the lock is released.
[ 30.240423] sec-thermistor sec-thermistor: notify_change_of_temperature: uevent: TEMPERATURE=440
[ 30.281316]
[ 30.281322] Dongle Host Driver, version 1.15.11
[ 30.281326] Compiled in drivers/net/wireless/bcmdhd/src on Jul 8 2012 at 22:06:55
[ 30.283360] CFGP2P-INFO2) wl_cfgp2p_supported : wl p2p error -23
[ 30.300774] [if_usb_resumed]

And this on both my logs:

[ 5094.430554] PM: Device alarm failed to suspend: error -16

This on one of my logs:

[ 8996.043363] PM: Device power.0 failed to suspend late: error -11

Something CPU related PREEMPT SMP?

Stock XWLPG with Jkay :)
[Galaxy S II Original Android Development] Krendelrus:
Camera preview and bluetooth is not working in latest XWLPM release + latest Siyah, everything else seems to be good
[Galaxy S II Original Android Development] LogeshMenon:
+1
[Galaxy S II Original Android Development] Tungstwenty:
There's a bit of a confusion with the wakelocks new feature.

The deleted wakelocks details are always there regardless of the setting. Just activate WiFi, let it on for a while till it shows up on BBS, and then disable WiFi again. On BBS you should now see "deleted: wlan_wake" and "deleted: wlan_rx_wake" with the respective individual counts / times.

Note however that there's only details for the last 2 deleted WLs, after that it ends up in the "deleted_wake_locks" as before. To see this, enable WiFi again, let it consume some time, and disable again. The previous 2 wakelocks are merged in the global deleted counter, and the 2 new deleted ones are shown as "deleted: X".

The part of the individual stats for the last 2 deleted WLs is always there.

What the ExTweaks setting controls is something else. When it's on, the time reported to BBS is not the entire time that each WL was active, but only the time for which that particular WL was the responsible for the power being on. If you have e.g. "multipdp" waking the device up, and then while it's still locked "secril_fd-interface" also being locked, the time for this 2nd one isn't counting. Only if "multipdp" is unlocked and there are additional wake locks active, will one of the remaining ones be selected as the responsible for power on. There is no overlapping counting, unlike the regular stats.

Both stats are kept updated at all times, the setting just reflects which of the stat types are reported and you can change it without needing to reboot and start counting from scratch.

Check the 2 attached dumps for an example of the 2 counts, they were taken only a few seconds apart.

You mean you also have the feature active but have no problems with RILJ, right?

Well, I'm not putting my hands in the fire (GM is :D), but I've been using this for a while now and didn't have any hanging issues so I hope I'm not the responsible for the 3.3.3 complains :o
[Galaxy S II Original Android Development] BrandoHD:
@pikachu

That's weird, it probably didn't survive when I reverted to an older kernel, reverting was the only way I could use my device, it was freezing within a minute of completing boot process

Samsung Galaxy S II Tapatalk2
[Galaxy S II Original Android Development] robertobsc:
Hi pikachu, that's totally weird. I'm a little worried now!

These fs errors that are making the problem? If yes, why it don't happen in older versions? I went back to 3.2.7.1.

Pls send the link to fix my /data!

If I do a nandroid bkp, format, fsck and restore nandroid, I'll restore the corruption too?

Thx for helping !
[Galaxy S II Original Android Development] :
Let me post something useless: no Uc UV or whatever, getting a freeze, sod or random reboot every few minutes using my phone, sometimes even right after boot. I had to switch back since my phone was unusable, so I got no logs to attach for the time being, it was quite impossible to get it done without troubles.

Now I will sit back waiting for a fix from our experts or the master himself :)

Sent from my SGS2 - SlimICS Rom & Fluxi Kernel
[Galaxy S II Original Android Development] apk_xiz:
well just flashed this kernel version 3.3.3b 5 hours ago and now i am getting freaking freezes it sucks ! OP please fix it :mad:
[Galaxy S II Original Android Development] Markox89:
Yes :good:
[Galaxy S II Original Android Development] af974:
Dude, check here if you want to fix your problems with this kernel.

this isn't the way to ask something, the developer is not working for you so or you ask in a kind way or either just move on and note that i spoke you in a kind manner!

@ Gohan...mate, i must be lucky but i find your last kernel a piece of art, using 3.3.3 from when it was out and got no freeze, no random reboot not a freaking problem.

It is smooth and battery last a lot compared to the previous version.

Thanks for your work.
[Galaxy S II Original Android Development] diemadedrei:
Got another freeze after pulling out USB cable. The screen lit up and I put it in my pocket. Next time I got it out it wouldnt turn on... last_kmsg attached
[Galaxy S II Original Android Development] DeshTwo:
I'm running Shun Andromeda kernel (based on Siyah and no bugs or freez).

envoyé avec Tapatalk 2 - Wanamlite v12.2
[Galaxy S II Original Android Development] fatjivi:
Went back to 3.3.2.... Too many freezes with 3.3.3 even the 3.3.3b

No freezes now using 3.3.2
[Galaxy S II Original Android Development] issy_i:
Siyah 3.3.3 works best with?

AOSP

AOKP

sammy's

MIUI

?

---------- Post added at 10:23 PM ---------- Previous post was at 10:21 PM ----------

wich rom are u using?
[Galaxy S II Original Android Development] Rawi666:
I'm on CM9 9/07 with 3.3.3b for whole day and not a single issue :)

No UV/UC, PegasusQ, sio
[Galaxy S II Original Android Development] Namoi:
Using wanamlite xwlpg and vertumus theme + jkay : no problems at all.

extweaks settings : performance, cfs thunderbolt AND no undervolting, OC or BLN.

Thanks Gokhan
[Galaxy S II Original Android Development] pinkster:
Same here with ParanoidAndroid and no single issue yet. The mDNIe toggle made me come back from fluxi. Thanks mate!
[Galaxy S II Original Android Development] d3l1:
Can't go into airplane mode with 3.3.3b back to 3.3.3

Sent from here using Tapatalk