yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Original Android Development] New Macław:
Any new post about sources will be reported. Kernel sources are GPL and that's all. Your complaining won't change anything and now it's just a spam.
[Galaxy S III Mini Original Android Development] S3miniFin:
Is that reason why mac address wont show in phone?

Finding the MAC Address on Your Android Phone

Depending on your device, attempt to follow one set of instructions listed below:

On the Home screen, tap the Menu button and go to Settings.

Tap About Phone.

Tap Status.

Scroll down to see your WiFi MAC address.

Why i should trust every body here just like that?

And again, no hard feelings. I just ask question, please try takes.
[Galaxy S III Mini Original Android Development] mkruseonline:
And here from cm -> http://www.cyanogenmod.org/
[Galaxy S III Mini Original Android Development] New Macław:
It is showing. You have to enable Wifi to see its MAC address. And it's shown in Settings.

But if you're thinking this way, Oliver's CM also have possibly backdoor (I know both me and his doesn't, but I see you know better).
[Galaxy S III Mini Original Android Development] mkruseonline:
My MAC Address is shown ...

Using Facebook ? Think about trusting...

Is it only to make trouble here ? I am happy like it is and many other also (I think). So why not building your own CM and publish the sources ?
[Galaxy S III Mini Original Android Development] cmgonzalez:
C'mon Report Me!, i will be very happy if a moderator appears here...
[Galaxy S III Mini Original Android Development] ztandroid:
No offense dude. But let me tell you, just give up for asking the source...Long time ago, about hundred years ago, Maclaw has clearly made an answer or response for this topic that he will never give anybody the source....aand whatever you/we/anyone else do, it will make no changes, Maclaw will continue his project with/without "your blessing" as he said. And in the other side, a lot of people here just blessing him doing that. FYI, this type of discussion is actually repeated time after time and you will get the same answer, just stop dude.

Thanks.
[Galaxy S III Mini Original Android Development] stpdkid:
flashed this rom with "my own risk" and i have to admit this rom is worth to flash(recomended by [MENTION=4563056]IvanKurnia[/MENTION])..

*twothumbs* up for [MENTION=514419]maclaw[/MENTION].. :thumbup::thumbup:

i dont wanna spam this thread, arguing this and that with no end..all i know is if you have Knowledge to make roms it is great :thumbup: to share to everybody and help others not to complain and looking around trying to find fact to make others fall..:rolleyes:

oh by the way, if some dev break the rule there will be investigation, warning for the dev or thread will be closed, and any other thing..

no pros-no cons in here..
[Galaxy S III Mini Original Android Development] cholopo:
In my case the battery drains much, I have BLN active. Will that be the cause?

From 9-10 hours battery reaches 15%

The model I have is I8190L, baseband I8190LUBAMH1
[Galaxy S III Mini Original Android Development] evolez:
I have great battery life without BLN. Any case i dont think only BLN can cause that drain. I am only using greenify for saving battery.
[Galaxy S III Mini Original Android Development] samjam:
Kernel binaries without source is a copyright violation as the GPL license is the only thing that permits one to distribute a derived work which is otherwise forbidden by copyright law.

Unless a criminal breach of copyright has occurred, the only people with standing to prosecute are those whose copyright has been violated, i.e. kernel devs whose work has been misappropriated.

A criminal beach probably requires a commercial aspect, but there is also matter of jurisdiction.

The easiest target would be the xda site for contributory infringement.

It may be against the t&c of xda, I don't know how strict they are with respect to copyright.

---------- Post added at 07:53 AM ---------- Previous post was at 07:46 AM ----------

Xda website seems to be based in Texas so you might find a kernel dev with standing willing to file a DMCA request but a friendly email to admin might be better first.

I find it ironic that a dev could be so protective of his own work while abusing the copyright of hundreds

---------- Post added at 07:54 AM ---------- Previous post was at 07:53 AM ----------

BTW, I am grateful to Macław for his work.

The only grounds he has for an "out" of such a situation is if he releases the source for the main kernel but retains those of his proprietary modules and does NOT tag those modules as "GPL" as kernel devs and Linus have often stated that using the kernel API does not create a derived work.

If Maclaw does this, then no-one has any claim against him.

So... obtain a copy of his ROM, and check that his modules do not contain the GPL marker. As long as he provides actual source for everything else, then he has met the requirements.

---------- Post added at 08:06 AM ---------- Previous post was at 07:54 AM ----------

To be clear I personally don't know that any breach has occurred, I'm just providing background on the forms of complaint and resolutions that might be available.

As others have said there is no need to keep going on about it. Either there is a breach and therefore a complaint, or there is not. The only way to find out is to download a ROM and then see.
[Galaxy S III Mini Original Android Development] New Macław:
Guys, but you've kernel sources. I also added temporary smartassv2 today, because it was in latest CM10.1 (for mistake, but it was).

Kernel will be open, it's clear, but nothing else. And don't complain with me, it won't change anything.

Few new commits will be this night, after PAC release.

I promise now every commit will be pushed immediatally. And stop this complaining, other sources will stay closed.
[Galaxy S III Mini Original Android Development] eagleeyetom:
Okay, can I ask you guys to cease this unnecessary chatter? Kernel is under GPL license and its source NEEDS to be posted. Android itself is a mixture of Apache and GPL, so some things like device tree don't have to be posted. Whilst most of CM projects are open-sourced, it was always up to developer to disclose his work, so asking him in public to do so won't change much. As far as I can see kernel is GPL compliant, so I don't see an issue.

Can we move on, please?
[Galaxy S III Mini Original Android Development] Benzonat0r:
So you're saying you'll release device and vendor sources eventually? :p

Lemme ask you a question.

Which commands are the best to compile a kernel from your sources? I'm trying to build a kernel with PegasusQ governor and OC ability (let's say 1.2 GHz) but it's always the same damn issue WIFI doesn't work even if I provide dhd.ko (which is a WIFI module) to flash it with kernel it's still the same damn thing.

Thanks.
[Galaxy S III Mini Original Android Development] New Macław:
Hmmmm.... Only problem with wifi? Contact me at maclaw@maclaw.pl, let's check what is wrong (but I might not reply until the weekend).

BTW: Overclocking is locked on our phone with bootloader.
[Galaxy S III Mini Original Android Development] Benzonat0r:
Yeah only WIFI doesn't work everything else is fine.

I'll contact you now don't worry reply when you can. ;)

So you're saying we can't overclock this thing?
[Galaxy S III Mini Original Android Development] New Macław:
Yup, bagnz0r was testing OC. We cannot do it without dangerous bootloader modification.

Wysłane z mojego GT-I8190 za pomocą Tapatalk 4
[Galaxy S III Mini Original Android Development] Benzonat0r:
Wow that really sounds dangerous, although I have some experience modding bootloaders in the past but if you say dangerous, we better not touch it then. :D
[Galaxy S III Mini Original Android Development] b2dj:
Is there anyway we can disable bln? Or turn the back light off?
[Galaxy S III Mini Original Android Development] New Macław:
You mean completely backlight disable?

Wysłane z mojego GT-I8190 za pomocą Tapatalk 4
[Galaxy S III Mini Original Android Development] b2dj:
Yup! In stock rom i usually turn it off. Bln is nice but im not a fan of it. How can i turn off back light?
[Galaxy S III Mini Original Android Development] Benzonat0r:
[MENTION=5011036]New Maclaw[/MENTION]

Ok so I forked your kernel repo and did some changes

Added Brazilianwax and Hotplug governors

Added ROW scheduler.

https://github.com/Benzonat0r/android_kernel_samsung_golden

Take a look. :)
[Galaxy S III Mini Original Android Development] New Macław:
There's no function for it in CyanogenMod itself, but in free time I'll try to add it myself ;)

I can simply merge them in next release if you want ;) Perform a pull request please, if you could ;)

I'm thinking about add more governor to let people choose their best one. What do you think?
[Galaxy S III Mini Original Android Development] adgud:
Finally some cooperation in this thread, nice.

Maclaw, I suppose the more governors the merrier if it doesn't cost you too much work.

Also, I could work on implementing back light of the keys settings (always on, 1.5s, 5s, always off like in stock rom) if I knew where to start.
[Galaxy S III Mini Original Android Development] vlt96:
I really vote for InteractiveX or some governor with multicore battery saving in standby (put unused cores to sleep) and locked at minimum, or at least not ramp up so fast when sleeping :)
[Galaxy S III Mini Original Android Development] Benzonat0r:
Yeah do that it'll be great, and yes add more of them. I'll make a pull request. ;)

Edit: And don't add to many of them it can slow everything down, max 10 of them then play with it, see if it can handle more than 10. :)

---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------

That's Hotplug, it puts core 1 to asleep and core 0 is still active, frequency doesn't go higher than 200MHz when in deep sleep which means it can charge your battery faster.
[Galaxy S III Mini Original Android Development] IvanKurnia:
what if while charging, my phone never gets into deep sleep. always 200 MHz?

I prefer adding more frequencies. 144 MHz, 300 MHz, 500-700MHz, and 900 MHz.. so the CPU can increase or decrease in a dynamic way and more battery is reserved.
[Galaxy S III Mini Original Android Development] ttocs99:
All great ideas with more govs and io but use lucky people can actualy use the rom weres me when i install i dont have any network signal at all i done clean installs etc etc but to no avail so i went to dmod hope this problem gets fixed :thumbup: still brilliant work tho :p:D
[Galaxy S III Mini Original Android Development] blurblur:
I read through the pages and could not find the answer. Does this ROM work with Samsung Kies? I sync my contacts and schedule in outlook using Kies and not all custom ROMs support it. I have tried 3rd party software (even paid for them) and they usually work via some proxy software or do not work at all.
[Galaxy S III Mini Original Android Development] ztandroid:
Samsung Kies is designed for stock samsung ROM.
[Galaxy S III Mini Original Android Development] chetank628:
totally agree

I think instead of adding more governor we should add more step frequency i read and from my previous experience interactive governor works best when there are more frequency while i think interactivex must be added... we have only two major step frequency 400 mhz and 800 mhz

out of which 400mhz is pretty useless and phone and phone works mostly on 1000 or 800 mhz so we ant ust two midlle frequency one between 400 and 800 i think 650 would be good and one between 800 and 1000 and i think 915 would be great if this is possible this would surely increase our battery life...:fingers-crossed:
[Galaxy S III Mini Original Android Development] mkruseonline:
More freq. would be nice, but here I can not set the max. Freq to 800. It always uses 1000 max.

Is there any trick to fix max Freq. to 800 ? (May I''m to stupid to find it ...)
[Galaxy S III Mini Original Android Development] New Macław:
Adding more steps, Overclocking and other CPU-related stuff cannot be changed because it's all setted in bootloader (yup, I also dunno why).

We can only manage governors.
[Galaxy S III Mini Original Android Development] josip-k:
The bootloader is locked?
[Galaxy S III Mini Original Android Development] chetank628:
what type of commits you are talking about;) i hope that you fixed the issues with the pac you mentioned earlier can you add interactive x and pegasusQ governor in your kernel. i think it is better that interactive..
[Galaxy S III Mini Original Android Development] cmgonzalez:
thanks Thats the Spirit

Enviado desde mi GT-I8190L usando Tapatalk 4
[Galaxy S III Mini Original Android Development] IvanKurnia:
oh no..

how if we make another bootloader? does it possible?
[Galaxy S III Mini Original Android Development] Benzonat0r:
Making a bootloader is essentially impossible but we can mod it. I don't recommend anyone to even try it cause it's too risky and dangerous. Your device could fry or even explode in your pocket.
[Galaxy S III Mini Original Android Development] josip-k:
Yeah,making a bootloader is impossible. But we can unlock it,so we will have the ability to flash custom kernels,like every other samsung device. And then we can port other kernels,like 3.1,3.4 or such,but i think that no one on sg3 mini has such knowledge. But yeah,our possibilites are pretty much countless.
[Galaxy S III Mini Original Android Development] scattoit:
Bug chrome

video player won't work using Chrome or chrome beta. Eg. http://m.youtube.com/watch?v=IUWtAUKYmAQ

It's works using stock cm browser.
[Galaxy S III Mini Original Android Development] daywalk3r666:
Chrome has no flash support
[Galaxy S III Mini Original Android Development] Benzonat0r:
Added InteractiveX V2 and PegasusQ governors to Maclaw's kernel source.

Take a look here.

https://github.com/Benzonat0r/android_kernel_samsung_golden
[Galaxy S III Mini Original Android Development] scattoit:
Strange issue.

I remember that it was working fine on Cm10 20130801...

I don't think Youtube use Flash on mobile wersion
[Galaxy S III Mini Original Android Development] daywalk3r666:
That's right only the desktop version use flash player....
[Galaxy S III Mini Original Android Development] IvanKurnia:
I think stock browser has it.
[Galaxy S III Mini Original Android Development] New Macław:
Bootloader have nothing to port 3.1 or 3.4 kernel. Our bootloader is unlocked by stock, like in most Samsung devices, but CPU is controled by bootloader, not by kernel. That's all.

So I don't think that there's any real cause to make new bootloader. Too much risk for too less profits.
[Galaxy S III Mini Original Android Development] New Macław:
Look at your sources. InteractiveX is the same as Interactive, but with worse values ;) Really ;)
[Galaxy S III Mini Original Android Development] Benzonat0r:
I got that as soon as I compiled a kernel, results were worse than I expected. Thanks anyway. ;)

Removing it and adding Smartass V2 again.
[Galaxy S III Mini Original Android Development] New Macław:
No problem ;)
[Galaxy S III Mini Original Android Development] sosznik:
HI, is there any chance to implement AVRCP 1.3 ? on Dmod I have track titles on my BT mw600 and on CM10.1 not....BTW nic, fast rom :)

Dziękuję i pozdrawiam :)
[Galaxy S III Mini Original Android Development] Benzonat0r:
Ok folks so I've compiled a kernel from Maclaw's sources. Everything works except WIFI

Screenshots anyone? Yes yes here they are. :)
[Galaxy S III Mini Original Android Development] josip-k:
Great :)
[Galaxy S III Mini Original Android Development] Benzonat0r:
You have an e-mail from me, check it please.
[Galaxy S III Mini Original Android Development] New Macław:
New release is out!

You can get it from:

http://maclaw.pl/
[Galaxy S III Mini Original Android Development] scattoit:
Please, can someone investigate html5 video issue using Chrome?

Thanks
[Galaxy S III Mini Original Android Development] New Macław:
I don't think so, because Stock/Firefox doesn't have any issues.

Wysłane z mojego GT-I8190 za pomocą Tapatalk 4
[Galaxy S III Mini Original Android Development] mauam:
Dolphin & opera browsers works just great here too. Try to clean chrome data or unistall it & reinstall it again or go in recovery & wipe only cache & dalvik cache. Last solution, try another browser:p
[Galaxy S III Mini Original Android Development] evolez:
Incoming call voice is perfect now.

resolved low volume when switching between spearker and earpiece (in calls)

confirmed. good news

Just left offline charging
[Galaxy S III Mini Original Android Development] scattoit:
I've tried but still not working. Any other had the same problem?
[Galaxy S III Mini Original Android Development] New Macław:
Nice to hear that. Offline charging: working on it.

So you've to deliver logcat to us.
[Galaxy S III Mini Original Android Development] Fgroia:
testing now, sound during calls is working fine!

Interactive is the best governor?

Anyway to make the statusbar transparent?

Where is the usb debugging option?
[Galaxy S III Mini Original Android Development] Benzonat0r:
Maclaw you're violating GPL you'll hear it from a recognised developer any minute now.

Cheers. ;)
[Galaxy S III Mini Original Android Development] zatloide:
i guy, i have installed the oliver cm but now i wanna try the maclaw version i must do any wipe or data/factory reset not needed?
[Galaxy S III Mini Original Android Development] New Macław:
Nope, as I said on Maclaw.pl: just install it ;)

1. Yes, Interactive is the best.

2. Check in some mod thread, I dunno.

3. TAp a few times on build number in Settings. Developer settings will appear. There you can enable adb.
[Galaxy S III Mini Original Android Development] Sultanxda:
GPL Violation

[MENTION=5011036]New Macław[/MENTION]

You are violating the GPL regarding the kernel source you posted in the 4th post of your thread. The source on your GitHub does not match the kernel that you have put inside of your ROM, and I have four pieces of evidence that prove this GPL violation. The strongest pieces of evidence are listed first. Note: I compiled your kernel source using cm_golden_defconfig (because you made commits to it).

1. Using the kernel source you have provided, the WiFi module dhd.ko is built, however, this module does not exist in your ROM. I have downloaded your September 7th release of this ROM and there is no dhd.ko in /system/lib/modules. Even though there is no dhd.ko module in your ROM, WiFi works perfectly. dhd.ko is the only WiFi module being built by your kernel source so it should be necessary for WiFi functionality. Additionally, the WiFi firmware path in the bcmdhd driver in your kernel does not math the actual firmware path in your ROM. The actual firmware path in your ROM is /system/vendor/firmware/fw_bcmdhd.bin whereas the firmware path in the bcmdhd driver in your public kernel source is /system/etc/wifi/bcmdhd_sta.bin_b2. The file "/system/etc/wifi/bcmdhd_sta.bin_b2" does not exist in the September 7th release of your ROM. This proves that the kernel source you have locally on your computer has a different WiFi driver than what is in the kernel source you have provided.

2. When installing the compiled kernel and its modules (namely the dhd.ko WiFi driver) built from your public source (using cm_golden_defconfig and the GCC 4.6 arm-eabi toolchain included in the CM10.1 source), WiFi does not work. I tried modifying the firmware path in the WiFi driver to match the actual firmware path in your ROM and WiFi still did not work, meaning that the WiFi driver in your public kernel source isn't compatible with your ROM at all.

3. In the second post of this thread you have this listed as a feature: "New BT/GPS/Wifi/audio drivers – no longer buggy Samsung’s ones!"

Even though it says there are new BT, WiFi, and audio drivers, you have not committed any significant changes to these drivers to your GitHub after forking the kernel from OliverG96. Assuming that what you said in the second post of this thread is true, not only have you not uploaded the source code for your new WiFi driver (which has been proved above with other pieces of evidence), but you have also not uploaded the source code for your new BT and audio drivers.

Please update the kernel source you have linked to in the fourth post of this thread to make it inline with the kernel source you are using to build the kernel included in this ROM. You may want to do this as soon as possible in order to avoid moderator intervention.
[Galaxy S III Mini Original Android Development] New Macław:
Dude, BIG THANKS! Really. I don't have any problem with that.

I'm glad that you've discovered that.

Will upload my local kernel sources tonight. Dunno why github didn't saw a change when I was doing "git commit -a". Any ideas?

Thanks and cheers!
[Galaxy S III Mini Original Android Development] evolez:
Known ones are coming... run people :D

Really they came. i got that awful smells
[Galaxy S III Mini Original Android Development] New Macław:
Nope, everything is allright now ;) I'll just try to discover why git don't see my wifi changes...
[Galaxy S III Mini Original Android Development] evolez:
Just messing around mate. No worries.

except you no one working on that and mistakes are for us(human)...
[Galaxy S III Mini Original Android Development] m.ali.ozkaya:
Sms not sending and video record max 10 s and galery stoped :rolleyes:

GT-I8190 cihazımdan Tapatalk 2 ile gönderildi
[Galaxy S III Mini Original Android Development] New Macław:
And then you woke up...

And seriously: if really, logcat please!
[Galaxy S III Mini Original Android Development] Sultanxda:
Lying is only going to make things worse. You know how to commit and push to GitHub seeing as how you have five commits to your kernel source, all which were done in the past seven days: https://github.com/GoldenMod/android_kernel_samsung_golden/commits?author=maclaw

Additionally, you have several other repositories on your GitHub which you have successfully committed to for the past several months. According to your changelog, the WiFi driver changes were introduced on August 29th which is well after the older commits you have on your GitHub. This sufficiently proves that when you modified the WiFi driver you were already well-versed on how to commit and push to GitHub.

Also, assuming you weren't lying in the second post, you need to upload your audio and BT driver changes.

UPDATE: Proof of your old commits: https://github.com/GoldenMod/android_device_samsung_golden/commits?author=maclaw
[Galaxy S III Mini Original Android Development] New Macław:
Nope, BT/audio doesn't have any kernel changes. Only in system (audio libs, BT - binaries from other device and several device changes). The best prove is that you can easily run BT and audio on github's sources.

But it doesn't matter, I'll just paste whole my sources from VPS. I'm not at home so I don't have a possibility to make nice commits right now.

But yup, Wifi have to be updated. I'm not at home, but will try to push latest kernel from my VPS as soon as possible. I promise, latest kernel will be up tonight.

But please, let me update sources and stop writting about it right there. We have clear situation, sources is in uploading, if you want to talk with me, use PM.
[Galaxy S III Mini Original Android Development] Benzonat0r:
Actually Sultan figured it out, I just asked him to help me with WiFi. :)
[Galaxy S III Mini Original Android Development] New Macław:
Latest kernel sources are up. Sorry for all problems.

I was able to upload it only as tar.gz for this moment.

It's my local copy. There's no way that something is missing. So thanks for report, and please, stop complaining about my sources.
[Galaxy S III Mini Original Android Development] New Macław:
We will try to get NFC working soon. If you want to help us with testing, write email to:

experimental@maclaw.pl

Please, add [NFC] on beggining of email's topic.

Thanks!
[Galaxy S III Mini Original Android Development] zatloide:
Where I can find governor select :)?
[Galaxy S III Mini Original Android Development] New Macław:
Tap a few times on build number in Settings, then Performance menu will appear. There you can manage CPU ;)