yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Eyenseo:
[MENTION=4217277]Gustavo_s[/MENTION]

I have following problem with this kernel:

If I use the USB-Mode to transfer or delete files from the internal or external SD-card via my laptop (Ubuntu 13.10) the transfer / deletion will fail. Same is true for the CMW-Recovery option to mount as USB-Stick.

Both internal and external are EXT4 formatted.

With the included kernel from [MENTION=1077833]infected_[/MENTION] CMW11 the problem doesn't exist.

I hope you can fix this issue - this kernel is great! :D
[Galaxy S II Android Development] cryogeno:
Same here.
[Galaxy S II Android Development] Gustavo_s:
i'll revert mtp/usb driver update from samsung then we will see

stweaks settings should overwrite rom settings at boot, stweaks settings are applied after all rom-related stuff in initramfs was applied

in theory thats what should happen, but if the rom settings are applied with some delay after boot then it will conflict with stweaks

look in /res/ folder, is there a file lights.exynos4.so there? if yes try to copy it to /system/lib/hw/ overwriting the existing file and set the permissions as the other files there and reboot, it's needed for BLN, it's copied at boot by the kernel but maybe something is preventing that from happening

mass storage test

http://d-h.st/users/gustavo_s/?fld_id=28903#files
[Galaxy S II Android Development] Eyenseo:
I fear to say it but cwm 05.02 doesn't solve the problem with the mass storage mode.

Further information, in the CMW Recovery it seems to be working all right.

But via the Android mass storage mode I'm unable to delete / copy files on the SD-cards.
[Galaxy S II Android Development] Gustavo_s:
i'm re-uploading them with another reverted commit, please try it again
[Galaxy S II Android Development] Eyenseo:
Had to restore a backup after the previous kernel - something broke while trying to delete a file.

Took me quiet some time to get it back running :rolleyes:

With the new kernel (MD5: 6517ee7e4beed80241c9ba37b35b6f79) I was able to delete and copy a file, but while copying (unmounting within Ubuntu) one file to the external and one to the internal the unmountig failed again. Afterwards Ubuntu didn't recognized the SD-cards and I had to reboot the SGS2.

The file for the internal SD-card was copied completely. The file for the external SD-card was skipped.

Copying the file to the external SD-card separate worked fine.

Deleting both files worked fine.

Copying again both files gave the same result as before ...
[Galaxy S II Android Development] Gustavo_s:
i switched to mass storage, tried it on windows, tried to copy a 700mb iso file to external sdcard (ext4 using an ext driver for windows) it failed and i couldnt mount sdcard until the phone was rebooted too. I never noticed this because i use MTP, do you remember when this started or was it always present?

entropy512 pushed this patch:

https://gerrit.omnirom.org/#/c/5307/

if we can't find out when this started then i will try to apply it

also, can someone with a fat32 formated external sdcard try usb mass storage mode?
[Galaxy S II Android Development] j1gga84:
No Problems here to copy (big) files in USB mass storage mode with fat32 formated external SD card ;)

I have problems to connect to my Dell Notebook via Bluetooth but this could also be a driver issue on PC..

Regards
[Galaxy S II Android Development] Eyenseo:
I can't remember how long it's ago. It isn't something recent, I guess it started back at the end of December, but I could be wrong.

the problem with MTP and Ubuntu is, that it works for few small files but when copying many / huge files it'll randomly stop working.

Edit:

I checked the MTP mode:

with your kernel there is only a message that the MTP device can't be mounted (in Ubuntu) and if I try to open the device again the message will reappear.

with the cm11 original kernel I'm able to mount the internal and external memory - but as previously stated it'll randomly 'break'.
[Galaxy S II Android Development] pilgrim011:
Gustavo, what version should we test - 0302 or test version you suggested few hours ago?
[Galaxy S II Android Development] j1gga84:
I copied the file to system/lib/hw but when done the system reboots immediately (softreboot, did not have to enter SIM Pin), after that I set the permissions correctly and rebooted. BLN still does not work..

Regards
[Galaxy S II Android Development] pilgrim011:
Ok, I have tested UMS via recovery - not working. It says it's mounted, but there's no new drives in Windows, nothing...

When the phone is on. both UMS and MTP are working, but randomly - sometimes transfer is not finishing, especially in MTP mode.
[Galaxy S II Android Development] nihilista:
Same here, in recovery no mounted drives in windows. But that was from the first day i used this kernel, 2 or 3 versions ago....

And i miss auto dual boot function from dorimanx kernel, a bit ;) Btw, most the time i use sambadroid for transfers, that works really good ...
[Galaxy S II Android Development] pilgrim011:
Yes, that's true - since as far as I remember (read december 2013.), there were problems with transferring files, and ums from recovery never worked.

On Apolo kernel mounting was ok.

P.S. All of this on cwm versions - haven't tested twrp recovery.
[Galaxy S II Android Development] nihilista:
Using twrp, no difference.
[Galaxy S II Android Development] cryogeno:
The first time I had issues with UMS was on 5/01 kernel, with fat32 ext sdcard.

I have lost some data and then i change filesystem to ext4.

After the switch UMS has never worked for me.

I hope this can help.
[Galaxy S II Android Development] SkyaTura:
Tested with Pac-ROM 4.3, did not work. It shows Samsung's first screen then turn it black and never changes... it's a pity, this kernel seems nice, and also, i'm with heat issues with dorimanx x.x

edit1:

my mistake, i tried the 4.4 over 4.3 ROM (Genius) XD

Booted with CM10.2 version, i'll evaluate it now \o/

edit2:

With CM10.2 variation it get stuck on bootscreen :/

little note: rapaz, nem vi que era br
[Galaxy S II Android Development] Gustavo_s:
the version i posted few hours ago, but its for testing purposes only

i'll try to apply entropy512 patches today when i have some time
[Galaxy S II Android Development] j1gga84:
Please also have a look again at BLN because it worked in previous versions..

Many thanks for your work

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] pilgrim011:
Please take into account that on CM11 stock kernel UMS via recovery works fine.

Also, few versions ago we had touch CWM, but not anymore. It was very handy feature. Any reason for reverting to non-touch CWM?
[Galaxy S II Android Development] clock51:
@gustavo

hello, Great, I'm using your kernel, "" "excellent" "" would be possible in future versions, the option "Slide2Wake Switch" (present in the kernel dorimanx), and activated with STweaks, it was convenient to activate the screen, with a switch. thanks
[Galaxy S II Android Development] smirciat:
Keyboard Reboot

Instant reboot upon changing from Google voice typing to Android keyboard. Happened several times, then reflashed infected's Omni build without this kernel and the behavior stopped. Flashed the kernel again and behavior reappeared. Any ideas?
[Galaxy S II Android Development] cryogeno:
UMS problem

Hy Gustavo_s,

I'm on last kernel (03/02)

Today I have tryed to copy file from external SD card (ext4) to my pc (linux).

The copy has done, but after I have umount the card, the phone has become irresponsive.

After a reset (long press power button) the phone restart on "CM account" page.

Some application have lost data (GMail, Google Music ...) some others no.

I am on 0402 cm 11 _infected build.

Thank you
[Galaxy S II Android Development] Dr AM:
How to update from older version ?
[Galaxy S II Android Development] j1gga84:
Simply flash over it? :p

Or what do you mean by "older version" ?

Regards
[Galaxy S II Android Development] Dr AM:
Just want to make sure if there is anything else to do before flashing it ^_^
[Galaxy S II Android Development] j1gga84:
No :)

You CAN run the kernel cleaning script but normally it is not necessary, only if you come from another kernel ;)

BTW: [MENTION=4217277]Gustavo_s[/MENTION]

BLN definetely does not work in kernel version of 03.02. after reboot. I tried it several times and I also deleted kernel with cleaning script and reinstalled it. I also deleted profile and set it again manually. I am on SlimSaber ATM and use the SlimSaber version of your kernel. Maybe it is an issue with SlimSaber because some users seem to have no problems !?

Regards
[Galaxy S II Android Development] nihilista:
I'm using same rom and same kernel, but after some little difficulties bln now works, rebooted my phone 5 min ago and it works.

I did deactivate it in stweaks, activated it, gone into performance menu, deactivated it, activated it, rebooted and it stays working.

Bit tricky but for me ok.
[Galaxy S II Android Development] jnetode:
Have you tried deactivating it in the ROM menu and activating in Stweaks?

Enviado de meu GT-I9100 usando Tapatalk
[Galaxy S II Android Development] j1gga84:
you mean in performance menu as described by [MENTION=4471736]nihilista[/MENTION]?

or advanced options - device and then touchkey lightning?

Gruß
[Galaxy S II Android Development] nihilista:
That will not work, touchkey light has nothing to do with that (set on and 3 sec here, advanced/device. Performance settings option will do, but if you disable that you have no bln and stweaks setting is useless.
[Galaxy S II Android Development] j1gga84:
It worked once after I tested BLN in STweaks but then no function again. :(

This weekend I will change ROM and see if BLN works then, maybe something is wrong with ROM setup..

Regards
[Galaxy S II Android Development] nihilista:
One thing more, i unmarked "force disable touchkeys" in stweaks, maybe that has something to do with that, and i set led to 3sec there like rom standard. Don't know why force disable is satndard setting, because not needed. Try that, maybe thats the cause.
[Galaxy S II Android Development] Gustavo_s:
i'll be posting updated kernels later:

- Disabled AIO (asynchronous i/o) and dynamic fsync

- These two are great features but are a bit dangerous, if your phone freezes (for uv/oc or other reasons) and you pull the battery you can get corrupted data

- Updated recoveries

i won't have much time from the next week until june/july, so i won't be updating and adding new stuff in the kernel as often as i have been doing the last 2 months. There are two major problems:

- BLN on slim roms:

seems that slim roms have bln settings in the rom and it causes conflicts with the stweaks settings, a solution may be enabling bln & blnww for default in the kernel, and see if when disabled it would keep the settings (probably most users have bln & blnww enabled anyway) [MENTION=4699854]j1gga84[/MENTION] i will send you a test kernel later

- USB mass storage mode

i tried to apply entropy512 patches, it only made things worse, it's obvious that something broke it along the way, i tried to get logcats/kmsgs when the transfer stopped, logging them to /data/, but all I/O stops and what really happens never gets recorded in the logs, maybe that means its not related only to sdcard storage. I will have to get a clean kernel code and apply some suspicious commits that could mess with filesystem/volumes, then test them. I'll try to do it this weekend.
[Galaxy S II Android Development] Resync:
Can you do something about app data corruption after phone freeze? (need to hold power button)

It kills Swiftkey etc... every time... :(

Also why does Stweaks reset to default dont work?

It keeps the old settings regardless, you need to change every single option back and forth always save and only that will change the settings...
[Galaxy S II Android Development] Gustavo_s:
ok the usb mass storage device problem seems to be gone, can someone using slimkat test bln?

http://d-h.st/users/gustavo_s/?fld_id=28903#files
[Galaxy S II Android Development] Eyenseo:
I can confirm it for [MENTION=1077833]infected_[/MENTION] CM11 07.02 with CMW :D

Thank you :good:
[Galaxy S II Android Development] AF_624:
tested with slimkat.. bln ok...

did you change something in the colors? they seem diferente than the previous version :confused:
[Galaxy S II Android Development] Gustavo_s:
didnt apply the i9300 update 12 screen drivers, will do later, started the kernel from scratch in a test branch to remove the usb bug

i identified the commit that caused the problem, i'll roll back to master branch now
[Galaxy S II Android Development] mode2006:
Warning!The new Kernel from today is bad!My S2 not starting!But now in Download Modus!

I have the Infected Rom!
[Galaxy S II Android Development] fubo73:
It started ok to me. But I noticed a blink in Samsung I9100 logo. I'm on slim saber.

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Android Development] twindad:
+1 on cm11

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Android Development] djthorne:
Same here. Odin recovered to previous kernel. Infected CM 0602.
[Galaxy S II Android Development] Vernyak:
08/02 kernel

08/02 kernel didn't start on SlimSaber mod of SlimKat. Boots into Sammy logo and reboots again.
[Galaxy S II Android Development] Bitman64:
With Omni everything is working well.

Gr.

B.
[Galaxy S II Android Development] pilgrim011:
Sooo, should we try this on CM11 or wait for Gustavo's next build? I see different experiences...
[Galaxy S II Android Development] fubo73:
Here it runs

Sent by my kitkat'd I9100
[Galaxy S II Android Development] filipeataide:
Same here with cm11 infected.

Enviado do meu GT-I9100 através de Tapatalk
[Galaxy S II Android Development] scorpion.hbs:
i've tried 08/02 kernel on cm 10.2.1 infected.

phone doesn't boot:(
[Galaxy S II Android Development] _Atom_:
No issues in my device running latest gustavo kernel...are u sure u flashed the gustavo kernel for cm10.2
[Galaxy S II Android Development] pilgrim011:
Ok, the phone booted on cm11 infected. There was a blink/hiccup on Samsung logo, but the ROM boots.

Everybody with problems, try to perform a kernel settings wipe from recovery, then install 0802 build.
[Galaxy S II Android Development] scorpion.hbs:
yes.

ure rom is infected build??

i use kernel wipe settings and then install kernel.
[Galaxy S II Android Development] pilgrim011:
Ok, UMS from recovery still not working on 0802 build...
[Galaxy S II Android Development] _Atom_:
Yes it is build from infected
[Galaxy S II Android Development] fubo73:
No need for kernel settings wipe but the blink/hiccup was same here on slim saber.

Sent by my kitkat'd I9100
[Galaxy S II Android Development] farisyi1:
[MENTION=4217277]Gustavo_s[/MENTION] latest kernel (08/02) backup failed with omni TWRP
[Galaxy S II Android Development] nihilista:
Tested 08/02 kernel, got bootloop and has to install tar via odin.......not good...
[Galaxy S II Android Development] endstille:
same for me!

and odin didn't work on first try, i nearly freaked out :(

I got it to work now.

edit: omni / twrp
[Galaxy S II Android Development] maxpower_303:
same here, took me 4 hours to get the phone up and running again (had to go back to zero and start from the scratch with samikernel.com)...not good, dont try that version with linaro/sabermod newest CM11 version..
[Galaxy S II Android Development] endstille:
i downloaded dori 7.35 tar (7.43 didn't work via odin...)

then in this old recovery i could'nt install recent omni nightly, so i restored old gustavos-kernel via Recuva from my SD-Card.

then i was able to install the recent nightly, after rebooting into this recovery.

so i'm back to my old system, only playstore and g+ has gone..

i will install the gapps again and see if this solves the issue.
[Galaxy S II Android Development] Dr AM:
Yes same here
[Galaxy S II Android Development] nihilista:
No problem here, i started download mode, installed dori 9.43, did a kernel wipe, installed 03/02 kernel, booted, used triangle away....(long time that i never needed to use this ;), and i installed thousands of beta kernels...)

Eh, and first rule [MENTION=2120911]maxpower_303[/MENTION]: Make nandroid backup before every flash of something and have tar version of some kernel, now you see why ;)

Btw, there is something really bad with newest kernel, hope gustavo can fix that before he runs out of time ...
[Galaxy S II Android Development] roydest:
Confirm little blink/ small delay on Samsung Logo, but otherwise the phone starts without any further problems...

I use CWM 6.0.4.7 and Bam 2.0 RC2 (Kitkat 4.4.2)
[Galaxy S II Android Development] Gustavo_s:
re-uploading slim kernel in ~10min
[Galaxy S II Android Development] pilgrim011:
Have you identified the cause of the problems in latest build? Is it now safe to flash 0802 CM11 kernel?
[Galaxy S II Android Development] Gustavo_s:
i used the initramfs from official slimkat build instead of slimsaber builds as other times
[Galaxy S II Android Development] pilgrim011:
What I meant was - have you found what was the general problem on latest build that almost all users experienced, not only Slimkat/Slimsaber users? Are you saying that you have used Slimkat initramfs even on CM11 and Omni builds?

Also, since my phone booted fine, I don't understand why people were forced to use Odin? I mean, recovery was still there, right? They could just hold power, home + volume up and flash another kernel from recovery? Or the recovery was gone for some people? I just don't understand..
[Galaxy S II Android Development] Stef021:
I am on Beanstalk, i used 03/02 kernel and flashed 08/02 over and i can't boot my phone. It doesn't even gets into CWM. Any solution? Can someone provide me 4.4 kernel with .tar so i can flash it with odin, please?
[Galaxy S II Android Development] Gustavo_s:
the latest slimkat build was bugged, then i re-uploaded it with slimsaber init files, the other bug was the usb mass storage not working, which was fixed

that's the problem with dozens of roms out there, i test the kernel on official builds, then the guy building unofficial builds modify init files and then we have phones stuck on boot logo
[Galaxy S II Android Development] Stef021:
Have you uploaded working files? Can I download now and be sure they work?
[Galaxy S II Android Development] Gustavo_s:
i'm sure it works on cm11 official nightly build aswell as omni and slimkat official builds, in fact im using it right now in my phone
[Galaxy S II Android Development] scorpion.hbs:
and what about cm 10.2 ?

i use odin and cm kenel to using recovery and flash ure 03/02 kernel on phone.
[Galaxy S II Android Development] endstille:
fyi could'd reach recovery, as it bootlooped there as well.

so we were forced to use odin
[Galaxy S II Android Development] Stef021:
Your updates [MENTION=4217277]Gustavo_s[/MENTION] still doesn't work on my beanstalk. Can somebody post 03/02 kernel zip please?
[Galaxy S II Android Development] Gustavo_s:
i have an unified kernel that boots the 3 roms with a single zImage, if you are interested in testing pm me so we can deal with this multiple roms mess
[Galaxy S II Android Development] fubo73:
Got latest zip, still working but blinking at boot.

Sent by my kitkat'd I9100
[Galaxy S II Android Development] trawel:
Will your slimkat kernel work with fusionjacks SlimSaber?
[Galaxy S II Android Development] OskarUA:
Just installed latest OMNI build(not from _infected) and with latest kernel it doesn't boot
[Galaxy S II Android Development] jiannist:
[MENTION=4217277]Gustavo_s[/MENTION], there are two bugs in your kernel I would like to point out:

1. The charging animation and home button wake, when the phone is off and charging, is not working. The fix is described here: http://xdaforums.com/showpost.php?p=50114064&postcount=8827, thanks to HardCorePawn.

2. In STweaks, if "Led on Touch" is unchecked, and "Force Disable Touchkeys" is unchecked too, LEDs should turn on when I touch the touch keys, and turn off after their timeout. When I set these options in STweaks, it works as intended, however after a reboot LEDs don't turn on anymore and I must check and uncheck "Force Disable Touchkeys" checkbox for them to work again.

Additionally, if "Led on Touch" is checked, LEDs do not turn on on key touches, but only on display touches.

---------- Post added at 10:39 PM ---------- Previous post was at 10:37 PM ----------

Yes, it works!
[Galaxy S II Android Development] cryogeno:
Someone here have 08-02 running in _infected cm11 last build?

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Android Development] pilgrim011:
Yeah, it's blinking here, too... Does anyone know why is that happening?

P.S. MTP seems to be broken. UMS working, even from recovery, but MTP refuses to copy larger file (CWM backup) from extSD to computer. To be fair, I only tested this on netbook, not on a regular PC, but on the same netbook (Win7) UMS works good. Anyone else tested MTP file transfer?

---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------

I'm running it on the 0702 infected's build.
[Galaxy S II Android Development] metalgearhathaway:
Awesome performance on latest Cyanfox!

Testing endurance of system now :)
[Galaxy S II Android Development] mauriicio21:
flashed omni TWRP 8-2 and cant acess recovery, seens to be broke anyone can check this ? archive is ok
[Galaxy S II Android Development] shiniyoyo:
Be sure to report back!
[Galaxy S II Android Development] Gustavo_s:
ok after the mess with the last builds i decided to make a single kernel that boots on all roms, the ramdisk is generic and should boot on any aosp kk rom

i tested on cm11, omni, slimkat official and slimsaber builds, oh a note here, i also took the time to test bln in both slimkat official and slimsaber builds, and bln settings stick fine with slimkat official but does not with slimsaber, you can report this to the rom developer but i doubt he will give any attention for this

the source is here:

https://github.com/gustavoss/android_kernel_samsung_smdk4412/commits/test2

if everything goes well on your side with these 3 main roms i'll put this in OP for download

http://www.androidfilehost.com/?w=files&flid=11947
[Galaxy S II Android Development] Eyenseo:
CWM works fine with [MENTION=1077833]infected_[/MENTION] CM11 ROM :victory:

thank you :good:
[Galaxy S II Android Development] 089man:
Can I used this latest build with beanstalk rom?

I9100 Tapatalk 4, Rom1 Beanstalk 4.4. 2
[Galaxy S II Android Development] kircchoffs:
contunuos bootloop

flashed 10.2 2-8 kernel on slimsaber 4.3.1 and im having continuous bootloop

I tried ODIN but it can't detect my phone

anyone can help me how to fix?
[Galaxy S II Android Development] Dr AM:
Just try another usb port .. Had the same problem changed usb port and my phone has detected ... Last kernel version sucks :(
[Galaxy S II Android Development] Hopper8:
Click the link in my signature, and go to the section 'if Odin doesn't recognise the phone'. Try the things listed there, see how you go.

Sent from a galaxy far, far away
[Galaxy S II Android Development] kircchoffs:
looks my laptop having some issue on samsung usb driver. tested on my desktop and it works
[Galaxy S II Android Development] fubo73:
Blink is gone on unified build. Working on slim saber

Sent by my kitkat'd I9100
[Galaxy S II Android Development] fubo73:
BTW, the BLN works also on SlimSaber.

Sent by my kitkat'd I9100
[Galaxy S II Android Development] pilgrim011:
+1 - no more blinking on CM11 infected's build.
[Galaxy S II Android Development] maxpower_303:
whats the use of nandroid backup if you stick in a triangle bootloop and cant enter cwm anymore? I had to go back to unrooted stock to root the phone again and get cwm up and running again..
[Galaxy S II Android Development] endstille:
as your data and backups are still "there" you just have to flash a working kernel [tar] (e.g. Dori's) and then use it to install your recent kernel [zip] to restore your backup.

at least this it, what i did.