yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] madmack:
On another note, these are the current packet filters that I have in my kernel:

dhd->pktfilter_count = 1;

dhd->pktfilter[0] = "100 0 0 0 0x01 0x00";

In other words, make sure the first bit of the first byte of the packet header is 0 (i.e. unicast). It works just fine. I'm not receiving any ARP or Broadcast requests on my wireshark or tcpdump streams. (I've also made the filter work permanently and not just when the phone is asleep, but that's another thing).

These filter arguments work like this:

<id of filter> <polarity> <type: must always be 0> <byte to start> <mask> <pattern>

The default polarity (0) is to allow only those packets that match these filters. Switching the polarity to 1 will supposedly drop packets that match the filter. It worked when I tested it; it allowed only broadcast messages and unicast packets were dropped.

I tried adding in "102 1 0 12 0xffff 0x886c" and changing the pktfilter_count to 2 but then both filters stopped working for me :eek: That string is supposed to drop packets that have a pattern of 0x886c on the 12th byte of the incoming packet.

I eventually decided that these control packets that I'm trying to drop are actually necessary (they have a wakelock of 1500 msec each as opposed to the regular incoming packet wakelock time of 1000 msec) so I gave up on trying to filter them out. I do know that they're not supposed to happen so frequently especially that I never used their BT-AMP tech (hell, my bluetooth is completely switched off) so that is definitely a bug.
[Galaxy S III Original Android Development] carbonize:
@gokhanmoral You say "Dual-booting (supports only JB ROMs: Samsung JB and CM10)" but CM10 says you need to come from an ICS rom for it to work properly. Can I install an ICS and then straight away CM10 over the top or does your kernel just make CM10 work even as a fresh install?
[Galaxy S III Original Android Development] Striatum_bdr:
Isn't stock branded Rom ics?
[Galaxy S III Original Android Development] FallenOut:
just type fastdormancy

no need spaces in between

n its there
[Galaxy S III Original Android Development] irony17:
Bumping.

3rd time it did reboot.
[Galaxy S III Original Android Development] bordikun:
No reboots here. Tested the sound, have great difference from before and bass boost is greatly improved too, using beats headphones
[Galaxy S III Original Android Development] tanjiajun_34:
I lose root access after flashing? Anyway to get it back?
[Galaxy S III Original Android Development] irony17:
Okay,

Maybe something with the tweaks I applied then...

Wait and see.

I did put the sched mc on 2
[Galaxy S III Original Android Development] :
Sound tweaks are amazing....my first thought was wow. Until I receive a call or a text. If I don't have phone on silent then after a notification or ring tone, audio at max is barely audible.

Reboots do nothing. Turning all audio tweaks off/disabled does nothing. Increasing amp does nothing.

Flashed back to 1.1, worked fine. Flashed to 1.2.6. Still good. Back to 1.3 and I can duplicate the issue.

Update:

Just flashed 1.3 a 3rd time via mobile ODIN and now it works fine. Weird.... But ya, 10 text notifications, some calls and the voodoo sound is still working fine. I was flashing via CWM before...

Update 2:

Did some reboots, more testing. Seems to be resolved.

***

Update 3:

Problem perseveres. If I open extweaks while listening to music it goes super quiet. If I reboot with headphones plugged in it stays super quiet. If I reboot with headphones disconnected voodoo sound tweaks come back. So something related to tweaks when extweaks loads.

Also I have poor loud speaker volume. From about half way to max it doesn't even sound like it changes, but I am outside so maybe I'm not noticing minute differences

Back to 1.1 for me.. Very interesting work though. And thanks for all the hard work gokhan
[Galaxy S III Original Android Development] currydude:
Likewise, very low loudspeaker volumes with cwm file. With tar through odin and mobileodin it is fine.
[Galaxy S III Original Android Development] mmse88:
Version 1.3 voltage is working

When I set to -100MV my SetCPU voltage part follows but previous version not:laugh:
[Galaxy S III Original Android Development] winwiz:
Fastdormancy app:

https://play.google.com/store/apps/...W5tb3JhbC5mYXN0ZG9ybWFuY3l0b2dnbGUuaTkzMDAiXQ..

I want to flash this kernel with CM9 but I get the silent calls issue

The speaker seems to die when I dial out. Can anyone advise if this is fixed?
[Galaxy S III Original Android Development] bordikun:
Found problems of my own. After unplugging the headphones, speaker became VERY low even at full volume still speaker is hard to hear with the notifications and ring tones.

Reboots and works fine again, plug headphones sounds great, unplug headphones problems occurs again (VERY low speaker volume)
[Galaxy S III Original Android Development] gsw5700:
mine is the same the loudspeaker volume its very low :(

Sent via TCP/IP
[Galaxy S III Original Android Development] EdgaBimbam:
so far no problems with 1.3v, siyah kernel as always the best :)
[Galaxy S III Original Android Development] :
Exact same symptoms. I have to have headphones disconnected when I reboot otherwise it starts back up doing the same thing. I'm going back to 1.1 for now
[Galaxy S III Original Android Development] luen76:
Same here, voodoo sound is great but once I plug out the headphones, the speaker volume decreases by a great deal. Reboot and everything is fine again.
[Galaxy S III Original Android Development] currydude:
Have you guys tried the tar instead of cwm? Mine is fine after using tar with mobileodin
[Galaxy S III Original Android Development] thyttel:
I'm finding too that V1.3 is causing volume/sound problems. Low speaker sounds, and sometimes sound is good with headphones, sometimes sound goes low for no reason when using headphones. Seems Voodoo for SGS3 is very buggy.

Tryed flashing several times both using CWM and Odin. Still problems come and go. Will give it some more testing, but if I can't resolve it will have to go back to v1.2.6.
[Galaxy S III Original Android Development] Mopral:
Sounds works good for me with 1.3

Even try to disconnect headphone while playing music with no issue
[Galaxy S III Original Android Development] bordikun:
Flashed via odin just now, problems still persist. Guess we'll have to wait for the 1.3.1 :D
[Galaxy S III Original Android Development] currydude:
Oh ok, I have no idea :S
[Galaxy S III Original Android Development] :
Worked fine for me until several reboots then flaky behaviour again. I know I shouldn't purposely go bug searching but it's very easy for me to duplicate the issue. It actually resurfaced by opening extweaks, up until then I didn't experience it on headphones or loudspeaker. Then after that it was back to square one lol.

Again could also be something related with ROM or the fact it is a Samsung based ROM. Either way sounds awesome, I like what was done, just in its current state it isn't for me.
[Galaxy S III Original Android Development] carbonize:
1 - There is no rom when you first go to create the 2nd rom space

2 - Sammy stock is now JB

3 - Clearly states in big letters in OP that this kernel now only works on Sammy JB roms and CM10
[Galaxy S III Original Android Development] Stivikivi:
1. Install ICS and upgrade to CM10

2. Install Siyah with DB from CM10

3. Install the desired Rom to 2nd Rom.

Easy
[Galaxy S III Original Android Development] carbonize:
CM10 is my desired second rom, I am running Wanamlite as my first and main rom.
[Galaxy S III Original Android Development] compunerd3:
I am using this with Android Revolution HD ROM along with cm10 nightly and siyahkernel v1.7rc1

Love it!!!!
[Galaxy S III Original Android Development] carbonize:
I just went ahead and installed CM10 as the second rom without installing an ICS based rom first and it seems to be working as well as expected, ie things like camera FC but everything else seems to be working fine.
[Galaxy S III Original Android Development] jnr21:
But what about wifi? ;) Cm10 works even if you are not flashed ics first but wifi may not work.
[Galaxy S III Original Android Development] carbonize:
WiFi worked fine. Even managed to download Gapps over it.
[Galaxy S III Original Android Development] brunodmjr:
It is just me that is having problem with battery stats after flashing Siyah Kernel 1.7rc1? I thought it was my device or any app installed, but i just made a clean install (Omega v29), even formating data and system before flash the rom... Got a ultra clean rom and the first thing i did was flash Siyah kernel after the first stabilizing boot. It is just flash Siyah and battery stats goes rogue =/

I did all the pretty things before flash it: Wipe cache, dalvik, battery stats, etc etc etc etc...

Does anyone have this problem? It can't be possible! =( Can you guys help me giving me some feed back?
[Galaxy S III Original Android Development] Tungstwenty:
Could it be that in addition to the packet type (0x886c), one would also need to exclude the packet only if it carries some other information (say, an origin mac address different than the router's)? Does this make any sense at all?

That could throw userland into the equation - inform the kernel of which MAC to whitelist, once an AP has been connected to (and remove that filter when the connection is lost, to pick up any AP afterwards).

Rob mentioned something about one of the bits in the mac address being changed, was it the origin mac address? Or if it's the destination, then we have the controller in promiscuous mode and userland could be reading the device's mac address from efs and filtering out packets that are not unicast for this address.
[Galaxy S III Original Android Development] Rob2222:
This is what I think at the momemt:

There is some controlling data that needs to be transferred from one S3 subsystem to another S3 subsystem. For any reason I do not know, they transfer the data trough ethernet packets. For that they choosed the ethernet packet type 0x886c. But a ethernet frame needs a source and a destination mac address. Cause they want to send data to the S3 itself, the destination mac is clear. It's the mac address of the S3 itself. But now they need a valid source address. I think it could be a problem/is maybe not allowed, when source mac address is the same like the destination mac address. So they use the destination mac address, flip the x.th bit (cant check which bit it is atm) and use this non-existing mac address as source mac address when sending these packets.

Short:

Destination mac is the S3 wifi mac

Source mac is the S3 wifi mac with one bit flipped.

Edit: It's the 7th bit from the left, that is changed from 0 to 1 in the source mac an cloudshark annotates this bit with 0=globally unique address and 1=locally administered address.

BR

Rob
[Galaxy S III Original Android Development] shahzaib.khan:
Can any one suggest me a best tweak which are in post 1 .....
[Galaxy S III Original Android Development] jayharper08:
Keep in mind, that this is still a development thread. General questions, (especially ones that do not even concern the kernel) do not belong in here. Thank you.
[Galaxy S III Original Android Development] NikkyNine:
Hello!

Please, help me. While installind first rom after cloning sammy rom to second, I do wipe /data, wipe /cache and format /system, but after installation of first rom I have second rom not installed (and free space in my internal SD)... What the reason? If data of 2-nd rom located in

Thanks!
[Galaxy S III Original Android Development] turilo:
hoping to see this great kernel for the n7100 note 2 :D some day :)
[Galaxy S III Original Android Development] enigma1981:
I have to say - I absolutely ****ing LOVE the dualboot feature!!

This way I get to keep my existing wanamlite ROM and all my data and test CM10 nightlies without any undue stress!! What an absolute slice of genius!!

Is there a way to copy your 2nd ROM+data onto an external SD card? If there is, I've obviously missed it lol

Thanks in advance guys :)
[Galaxy S III Original Android Development] topfreitas:
Hey ppl, first of all i just want to tank a lot for this great work. The possibility to dual boot is amazing...

I just have one issue. I flashed stock ICS with Odin and then installed Paranoid on my device. Ok, till here everything working fine, then when i want to install Stock Firmware on second partition, my nfc stop working on Paranoid... I've been trying to flash "NFC FIX" but it doesn't work for me, also tried to put the "libpn544_fw.so" file from Stock firmware by myself, but no changes...

Is anybody there with same problem? I have this issue using Paranoid + Stick XXDLJ1,:eek:
[Galaxy S III Original Android Development] bradputt:
did you by any chance flash the zip file to the first rom instead of the second one.

You must use the siyah recovery instead of the cwm recovery
[Galaxy S III Original Android Development] udimars30:
i have flashed the kernel through cwm and i have the old recovery not the siyah one

plzzzz help!
[Galaxy S III Original Android Development] rock4hell:
its gonna like that only in the latest flashables but u can go into secondary rom utils from stweaks

hope might help u
[Galaxy S III Original Android Development] madmack:
We could do that. Except that I wasn't successful in filtering out all these 0x886c packets in the first place. :(

If you want to filter them out though, we don't have to worry about source and destination mac. The protocol type will always be at the same position in the incoming packet stream.

After observing and printing all kind of debugging messages to dmesg, it seems these packets are related to "GLOM" or glomming. I'm not entirely sure what that is but dmesg spits out a bunch of glom rx and ctrl messages when it receives these packets.

I also replaced some binaries on my file system. I'm now getting these packets roughly every 10 minutes instead of every ~3 previously. I need to test it a little more.
[Galaxy S III Original Android Development] svetliol:
I am curently wunning stock JB with Siyah 1.7. I played with the dualboot options and i managed to instal as a second rom MIUI RGUI v13 and it worked perfectly, but after that i flashed CM10 and now i cannot return to MIUI as a second rom. Please can someone explain what am i doing wrong.
[Galaxy S III Original Android Development] xanthrax:
flash v1.7rc1 again and fix permissions of sec rom
[Galaxy S III Original Android Development] filflame:
Good day, I've just tested it and I have a problem.

I'm on PA 2.22 and i've restored my stock Sammy rom that was on 4.0.4 as my 2nd ROM , and whenever I try to boot the 2nd rom, nothing happens, it just show the countdown again and boot the 1st rom. Sometimes it just wont boot at all. Please help, thank you guys
[Galaxy S III Original Android Development] Mopral:
Siyah does not work anymore with ICS since kernel 1.6.8
[Galaxy S III Original Android Development] filflame:
Thanks mate!
[Galaxy S III Original Android Development] udimars30:
thnxxx it works
[Galaxy S III Original Android Development] ChrisHRocks:
this has happened to me too.

anyone have an answer??

Edit: i can get to the siyah recovery through stweeks but not if i reboot into recovery i just get the normal one.

Can i run the siyah recovery as my normal recovery?

I'm feeling really like a noob right now, someone please help me out of this slump!
[Galaxy S III Original Android Development] Striatum_bdr:
I think it's explained in OP. Siyah modded recovery can't be run as default one.

Only when rebooted specifically with STweaks.
[Galaxy S III Original Android Development] Rob2222:
This sounds like the normal behaviour on my good router. What have you changed?

BR

Rob
[Galaxy S III Original Android Development] CountZer0:
I think i run siyah modded recovery as default. Flashed tar from within mobile odin i think and now i got it as default.
[Galaxy S III Original Android Development] naveediftikhar:
Ok i believe this has been mentioned before but wat the heck

Did any body notice the high freq useage of luzazctive gov..i mean for me it doesnt go below 800mhz (touch boost lvl) itt remains amongst the higher values for most of the time...ive had this issue with lulzactive ever since it was introduced by gm but only reporting now as i dun even use it anyways!
[Galaxy S III Original Android Development] ChrisHRocks:
I'm sure I've run it as default recovery before, possibly when I flashed it as part of the fox hound rom.
[Galaxy S III Original Android Development] xanthrax:
Post some screen shots with BBS and cpuspy stats . Lulz/deadline works fine here and not only ... you've got apps running in background and you don't know nor the developer. Be decent and provide proper info , you're in the wrong section anyway
[Galaxy S III Original Android Development] BlockbusterF:
bcmdhd from update4 in CM10 / tethering

Hi gokhanmoral,

first I have to say that you've done a really great job here! Dualboot works great und the SGS3 is notably faster and smoother with your kernel than with the default CM10 kernel. Also Colours are really better and thanks that you don't forced us to view at some ugly boot screen like other kernels sometimes did in the past.

Oh, and camera seems also to be faster. Switching between front and back and so on. No problems with battery at all.

So thank for this great kernel. But here it comes ;)

Would it be possible to implement these 2 patches:

http://review.cyanogenmod.com/#/c/25165/

http://review.cyanogenmod.com/#/c/25169/

Daniel switched back to samsung update4 for bcmdhd to get the wlan tethering to work again. If your kernel could also do tethering again this would be really great. So I could stick to your kernel :)

Regards, Eddy
[Galaxy S III Original Android Development] hawks-SOAD:
Hey noticed the audio tweaks reset when I get 2 notifications at once, to get it back just switch preset to something else then back again. Here is a new dmesg http://db.tt/tykpJgHt
[Galaxy S III Original Android Development] Tweak90:
Long boot

I've flashed the kernel

Siyah-s2-v5.0b1-CWM.zip

with cwm recovery and now my device is booting for around 10minutes just showing "Samsung Galaxy S3" start screen.... What do i have to do now? just wait? How long?
[Galaxy S III Original Android Development] rickgillyon:
You've flashed an S2 Kernel on a S3? I suggest you look in the forums for recovery procedures...
[Galaxy S III Original Android Development] Tweak90:
xDDDD thats it ;D shame on me :D k now ill try the s3 one :P thanks^^
[Galaxy S III Original Android Development] enigma1981:
That's a good idea, should work better ;) lol
[Galaxy S III Original Android Development] megasanyi:
Siyah Recovery tar download link please!

not kerner, only the recovery!

thank you!!!
[Galaxy S III Original Android Development] gokhanmoral:
I take this as a feature request for having a single kernel image for s2 and s3 :)

for now, I will modify the script in s2 zip to prevent it to be flashed on s3 or other variants.
[Galaxy S III Original Android Development] Tweak90:
xD thank you :P

with the correct s3 kernel its booting now, but after AOKP boot animation screen turns black, when i press lock key i can see lock animation, if i press again - nothing(when screen should show me the screen for PIN enter. When i press again - the lock animation is shown again.
[Galaxy S III Original Android Development] FadeFx:
Gokhan,

Could you please remove standard entries from 2ndromutils like "install zip from sdcard" which are in fact softbricking the device most of the time if used accidently...?

_________________________

tapatalked from GalaxyS
[Galaxy S III Original Android Development] sharingan92:
You cant get seperate recovery it is included in the kernel
[Galaxy S III Original Android Development] erto90:
i dont want recovery, neither dual boot.. can i only flash Kernel?
[Galaxy S III Original Android Development] Striatum_bdr:
If you don't install a second Rom you won't have dual boot... you can set in STweaks to get rid of dual boot logo in that case, and you'll have a normal boot.

You can't remove specific recovery. But if you don't use it you'll never know it's there.
[Galaxy S III Original Android Development] mondeo-rs:
Thanks for this kernel, but got battetydrain with lightmanager on chriskelo v 16. Does anybody got the same problem or an idea to fix it?
[Galaxy S III Original Android Development] Trek55:
if you don't want to install recovery, only kernel you need to flash it using mobil Odin, in mobil Odin select kernel to flash, make sure you download tar version of kernel, not cwm one..
[Galaxy S III Original Android Development] ziotempa:
Good evening to you all.

I have a little problem, don't know if it's related to siyah, anyway today I saw that aLogcat doesn't work, it stays blank and it repeats "reading logs" without giving results. As I said I don't know if it's a siyah problem. Does anybody have the same issue? Thanks

Zio
[Galaxy S III Original Android Development] bmwbasti:
Ist it not possible to set mimimum frequency to 100Mhz anymore?

On ICS i was on Syah 1.5 and there i could set it down to 100Mhz now on JB the minimum is 200Mhz.
[Galaxy S III Original Android Development] andip71:
When I am not completely wrong, Android Logger is disabled per default.

You would need to run a init.d script that inserts the logger module again.

Put the following command into a script in init.d:

insmod /lib/modules/logger.ko

Should work.

Cheers

Andi
[Galaxy S III Original Android Development] madmack:
system/
system/bin
system/bin/brcm_patchram_plus
system/bin/brcm_poke_helper
system/bin/bcm_dut
system/etc
system/etc/wifi
system/etc/wifi/bcmdhd_p2p.bin_b1
system/etc/wifi/bcmdhd_sta.bin_b2
system/etc/wifi/bcmdhd_sta.bin_b1
system/etc/wifi/bcmdhd_mfg.bin_b2
system/etc/wifi/bcmdhd_mfg.bin_b1
system/etc/wifi/bcmdhd_apsta.bin_b1
system/etc/wifi/bcmdhd_apsta.bin_b2
system/etc/wifi/bcmdhd_p2p.bin_b2

I copied these binaries from sprint's LG8 rom because v1.15 of the wireless drivers that gokhan is using is from that source drop. I can upload them here if you want.

Edit: I upped them to mediafire anyways for those who want to test: http://www.mediafire.com/?5w4adrrrqmfr8wf
[Galaxy S III Original Android Development] ziotempa:
Thanks for help Andi. I've done what you have suggested but nothing has changed. Should I have logger.ko in lib/modules? In that case there's no such file...
[Galaxy S III Original Android Development] Tungstwenty:
Check if you have an entry for enabling/disabling the Android Logger in STweaks, Misc tab.
[Galaxy S III Original Android Development] ziotempa:
Ooh yes! It works, thanks a lot, maybe now I can understand something more about the email issue.

Thanks again
[Galaxy S III Original Android Development] erto90:
why,if I type FREE in terminal emulator, it shows 0 ? is normal?
[Galaxy S III Original Android Development] Erahgon:
Yes, it's normally zero under "swap" unless you use z-RAM (not present in the kernel) or you use the hard swap mod by Yank.
[Galaxy S III Original Android Development] thekoRngear:
I got a question. My current rom is UltimaRom. Now I want to install another custom Rom like Omega or Wanam. Now after the installation is done through Aroma I got the "Reboot" button and nothing else. In that case when should I perform Fix permission and flash siyah again (step iii and iv) ?

And sorry if it is already been answered.
[Galaxy S III Original Android Development] erto90:
ok,but with my "circumstances" can i flash the multitasking fix by mattiadj?
[Galaxy S III Original Android Development] yokbob:
I was installed the dual boot but now I do not have any more space of storage available on the 2 partition... Can someone explain me how do to a clean format of my internal sd card to start again a good basis..
[Galaxy S III Original Android Development] csutikisx:
He can get the recovery by installing 1.7b1 or 1.7b2 then install the one he wants. So for those who want to get the Siyah recovery: first install 1.7b1 or 1.7b2 then flash the kernel that he likes.(I think it doesn't have to be Siyah.)

Edit: link removed as GM's wish is not to use his recovery for other kernels.