yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] mobuch:
Most important feature is still not working: Ability to read the warnings of other users and Mods regarding spamming this thread. However latest kernel update fixed the bluerhooth calls, but broke wlan a bit. Also some users had luck with running fm radio with one of the apps. So please:

because we dont want to see posts such as 'cant connect to wlan' after upgrade to new experimental kernel.. or got frozen device after using app for radio (but guess what - you need to read some posts back to see what app ;) ) because those are already reported.

btw.. radio woeks for me latest kernel, no freezes, but no sound after closing radio, need to reboot to get it back.
[Galaxy S Plus I9001 Android Development] oisis:
The problem with mac address in newest kernel is because WiFi driver i think.

Drivers are responsible for mac address assignment, they are assign wrong mac address.

So if we want resolve it, we have to change drivers(kernel modules) to oldest one?

Macs like 00:00:00:00:00:00 are rejected by routers be cause they are wrong(arp spoofing) that is why you cannot connect to WiFi router.

I had a strange adventure with bluetooth, at the beginning of the music on the headphones work fine, sound a little better than before. After some time I could not even connect headphones to your phone. After rebooting the phone I heard a strange crackling in headphones, I had to install a kernel again. Now everything works well, I hope it will not break down again. Unfortunately I do not have logs because I was busy.

EDIT1:

You can create init.d script /system/etc/init.d/80macaddr (remember to set permissions: 755):

MAC=$((date +'%Y%m%d%H%M%S%N'; cat /proc/interrupts) | md5sum | sed -r 's/(..)/\1:/g' | cut -d: -f 1-6)

echo $MAC > /data/.mac.info

I'm just testing this solution. I'll know later if it works.

EDIT2:

Works but it is temp solution :). We needs good kernel modules for WiFi.

It is good way to hide your MAC/device in public networks if you want to do something bad :) hahaha

You can do this same with Bluetooth MAC address.
[Galaxy S Plus I9001 Android Development] wintel_mac:
If you want to discuss that any further, please do so in the General section. The 9001 cm state thread is the right place for such thing. Thanks.

---------- Post added at 06:50 PM ---------- Previous post was at 06:50 PM ----------

Clever solution! :D So the best (workaround-) option would be to write down your real MAC and echo this to .mac.info with an init script.
[Galaxy S Plus I9001 Android Development] mobuch:
Post edited as not relevant any more.
[Galaxy S Plus I9001 Android Development] broncogr:
Watch your language and attitude guys...
[Galaxy S Plus I9001 Android Development] oisis:
My solution is for hackers :)
[Galaxy S Plus I9001 Android Development] herzau:
Earlier I said that .mac.info file is not updated on boot...

I posted easy solution here: http://xdaforums.com/showpost.php?p=25420432&postcount=2576
[Galaxy S Plus I9001 Android Development] arco68:
Interesting. Seems like for your device the mac address can't be grabbed from the radio. For the Galaxy W I'm using a custom script to do that. Just to check, can someone check if the following commands outputs a value:

getprop ril.wifi_macaddr

getprop ril.bt_macaddr
[Galaxy S Plus I9001 Android Development] herzau:
return mac address of .mac.info and .bt.info files
[Galaxy S Plus I9001 Android Development] xewier:
*#*# for update camera firmware?
[Galaxy S Plus I9001 Android Development] androabot:
Return the MAC address. bt.info mac.info and files for me too

Hi herzau, The spirit radio works with the experimental kernel now

Only if I recieve a call, break
[Galaxy S Plus I9001 Android Development] arco68:
Try this: boot_exp3.zip
[Galaxy S Plus I9001 Android Development] herzau:
I sent a pm to the dev of the app with this problem

same as boot_exp2. MAC 00:11:22:33:44:55 by modified file
[Galaxy S Plus I9001 Android Development] Alex93917:
Wi-Fi doesn't works.
[Galaxy S Plus I9001 Android Development] arco68:
I'm a little confused, as you don't provide exact enough information.

So, if I understand correctly:

The output from "getprop ril.wifi_macaddr" and "getprop ril.bt_macaddr" are correct valid MAC addresses? And these addresses matches the ones in /data/.mac.info and /data/.bt.info ?
[Galaxy S Plus I9001 Android Development] herzau:
I modif /data/.mac.info with 00:11:22:33:44:55 MAC address

"getprop ril.wifi_macaddr" return 00:11:22:33:44:55

"getprop ril.bt_macaddr" return a correct MAC address

Another issue, why u put the min CPU freq to 122 MHz? I think that causes stability problems
[Galaxy S Plus I9001 Android Development] arco68:
Really? That's insanely weird. Can you delete the .mac.info file, then reboot and post the output from the getprop command. I need all the output from it.
[Galaxy S Plus I9001 Android Development] herzau:
deleted file and reboot, wifi still works with a correct MAC address :)

Everything works now

Another issue, why u put the min CPU freq to 122 MHz? I think that causes stability problems
[Galaxy S Plus I9001 Android Development] xewier:
this not work for camera?
[Galaxy S Plus I9001 Android Development] arco68:
With boot_exp3.zip? Or with boot_exp2.zip also?

It shouldn't cause stability problems. It's the default min freq used in stock rom and kernel.
[Galaxy S Plus I9001 Android Development] herzau:
I tested with boot_exp3.zip.

testing boot_exp2.zip...

EDIT: works with boot_exp2.zip

I removed .mac.info before installing boot_exp2.zip
[Galaxy S Plus I9001 Android Development] androabot:
Yes.

When I remove the Mac.info before installing boot_exp2.zip or boot_exp3.zip,

The wifi works perfectly.

But it is necessary that the wifi is activated at boot for you have a good mac. If you activate it

later, no longer works, even if you restart again, because it writes the MAC to 00:00:00:00:00

I have also noticed that the mac changes every time if you delete

the mac.info. This is not good if you use mac filtering on the router.
[Galaxy S Plus I9001 Android Development] arco68:
It shouldn't change to some random number every time the mac.info file is deleted. It should stick with the pre-programmed mac address assigned to the phone. If someone could just send me the output of getprop, which I requested earlier, I could check if the S+ radio provides this value, as it does for the Galaxy W. I'm guessing it doesn't, and I have to modify the script that makes the mac.info file.

But please, I need output of getprop to verify. To make sure it's clean, turn off wifi, reboot, and then get the output from getprop.
[Galaxy S Plus I9001 Android Development] arco68:
Try this: http://www.mediafire.com/?dcy9zdyamdifskb
[Galaxy S Plus I9001 Android Development] R341M@N:
With boot_exp2 and turned off WiFi removed file .mac.info several times. got ramdom mac, first three numbers every time just same, last three are random. Didnt tryed boot_exp3 cuz other says that nothing is changing. Flashing boot_exp4 and gona test it.

first Attach is with boot_exp4 (WiFi - off, reboot)

second Attach is with boot_exp2 (WiFi - on, .mac.info removed)
[Galaxy S Plus I9001 Android Development] TheMrCaveman:
Morning all:p

Wifi works with exp4.
[Galaxy S Plus I9001 Android Development] mobuch:
Steps:

1.Turn off wlan

2.Remove .mac.info

3.Flash exp_Boot4, clean caches

4.Boot

5.Getprop (seems that reads bt mac but not wlan, gives 0s).

.mac.info not recreated, but mac present in wlan settings -> advanced, and i'm able to connect to waln (wpa2)

a/local/bin:$PATH <
app_36@android:/ $ su
app_36@android:/ # getprop
(...)
[ril.bt_macaddr]: [somemac]
[ril.wifi_macaddr]: [00:00:00:00:00:00]
(...)
[Galaxy S Plus I9001 Android Development] R341M@N:
yes, and file .mac.info is disapired :confused:

should be so ?
[Galaxy S Plus I9001 Android Development] arco68:
Yep, that's correct. It's not needed for your device, and the radio just provides zeros for the mac address, so I removed the mac.info file generation from the script. It's instead taken care of in the wifi driver directly. So all good now then it seems. :) Thanks for testing guys! :)
[Galaxy S Plus I9001 Android Development] 30adi:
i just flashed boot_exp4, wifi works, but phone feels very bad (jerky) when scrolling, after deep sleep.same problem after a ended call. does anybody have same problem? after flashing boot_exp4, and tested, went back to original kernel, wifi did not work either, made a restore, all good now. hope someone needs this info, i'm just a simple user :)
[Galaxy S Plus I9001 Android Development] goorek:
Min freq with 122 mhz was causing these problems to me, also phone was almost unable to use for 5min after deep sleep, I had problems with unlocking, so I think it would be better to set it to 245mhz.
[Galaxy S Plus I9001 Android Development] arco68:
I've no such problems with 122 MHz on the Galaxy W. No wakeup lag or issues at all after sleep or calls. Can you try to disable automatic brightness and see if it improves? I remember reading somewhere that this was an issue on some other phones with CM9.
[Galaxy S Plus I9001 Android Development] Harrocan:
For me boot4 work perfect. I don't have any problem with unlock phone in sleep. Meaby really you have turned on auto brightnes? :D
[Galaxy S Plus I9001 Android Development] Mirceabadea:
And what's your CPU governor ? i set mine back on ondemand because interactive was pretty laggy and after some calls the phone didn't respond for a couple of seconds. And with interactive it hangs very often.

Also, can you provide us with a changelog of what was changed in the new kernel ? compared with the one when you didn't merge the 3 kernels from the 3 phones.

The kernel works great, no lag here, but i'm on ONDEMAND governor.

And one more question for arco. Is this CM9 source updated to the latest sources from cyanogenmod nightlies ? or it's an older version ?
[Galaxy S Plus I9001 Android Development] BzArEx:
I've also got the same problem on kernel from 21 April, stable from 20 is perfect phone works great after unlock and when someone calling to me. Disabling automatic brightness didn't solve those bugs. Only no response touch screen bug.
[Galaxy S Plus I9001 Android Development] 30adi:
automatic brightness is turned off, i've changed minimum freq to 245 MHz and seems to work well. i have changed governor to see if it helps somehow. thanks for reply
[Galaxy S Plus I9001 Android Development] Common Sense:
Same thing happens to me as well, I sometimes get lag when phone is waking up from sleep. Entering CPU governor and changing something in the settings will fix the problem instantly. I had the problem with both on demand and interactive governor. I will try and set the min. freq to 245 mhz and see if it disappears.

I never had the problem with the old kernels, before arco was using the same kernel for both galaxy w and galaxy s+.

Anyway, really great progress on the rom now, most things working :)

@ All

anyone else still experiencing that volume cannot be changed during a call (when not using bluetooth headset)?
[Galaxy S Plus I9001 Android Development] drummer1839:
Boot 4 work great no lags wifi is perfect. Great work arco.
[Galaxy S Plus I9001 Android Development] Mirceabadea:
Yep, after i used Interactive kernel for 5 minutes, when i received a call the phone hanged and it kept ringing, and i couldn't touch anything. The screen was black. After 5-10 seconds, it worked again but the call dropped and the phone was laggy. I switched back on ONDEMAND and it's working great.
[Galaxy S Plus I9001 Android Development] uberto.costanzo:
freq min 245 governor ondemand all work good bt in call and music wifi 3g gallery very fast and also gps work good, ram free is very good, now is time for CAMERA. thanks arco68 and all work in this project. when i return home from my work 4 days i have donate for you for your free time for this rom thanks bye;):)

sorry for my english
[Galaxy S Plus I9001 Android Development] Mirceabadea:
Yep, only camera left now. :D
[Galaxy S Plus I9001 Android Development] oisis:
And voice call volume :).
[Galaxy S Plus I9001 Android Development] abbradar:
Here is the link to the last test build (CWM recovery):

http://www.mediafire.com/?zxqbd3lvckh88ja

Fixed sensors, possibly GPS, WLAN.

I don't take responsibility for your phone damage etc etc, in other words - please, be careful! Post back reply after your testing if you'll find other bugs than listed in the first post, it'll help greatly.

Switching to Bluetooth fixing now...
[Galaxy S Plus I9001 Android Development] nail16:
Testing the latest build now

What's working

WLAN (speed seems to be normal)

Auto-rotate works fine, switching between the orientation is fast just like the stock firmwares

both 3g and 2g internet works (even the network reception is good)

adb is working

external sdcard (can be read through massstorage)

What's not working

phone takes a while to wake up after sleeping, approximately about 30 seconds feels like a sod but it wakes up eventually :)

Sound still doesn't work(earpiece,microphone,loudspeaker)

Camera now giving FCs, before a white screen would appear

Installed maps to check gps it doesn't seem to lock, it couldn't even determine my location using wifi network

Bluetooth

cant read external sdcard on phone(shows empty in root explorer and es filemanager)

internal sdcard read via massstorage doesn't work (strange, if usb debugging is turned off both the internal and external sdcards don't pop up via mass storage, sometimes it shows safe to remove emmc in the notifications)

that's it for now, but i'm still testing the build, might continue using this rom for the next2 days :)
[Galaxy S Plus I9001 Android Development] Naruto98:
f-a-n-t-a-s-t-i-c the most big problem is: "Sound still doesn't work(earpiece,microphone,loudspeaker)"
[Galaxy S Plus I9001 Android Development] abbradar:
I think so too, it's main problem for me before I can start using my ROM in everyday life. Unfortunately, sound, with camera, will be the most difficult part because it looks like it's most heavily modified by Samsung specially for that phone, so I've postponed it till I repair communications - they seem easier, and they are much needed, too. (not GPS, it'll be the last part, at least only after audio)

Bluetooth news - it looks like magic for me now - it works.... sometimes, and most of time it is not. I cannot catch any factors which correlate with it. I also replaced our firmware for WLAN and Bluetooth with HTC's one - nothing changed. For now it enables like every tenth try.
[Galaxy S Plus I9001 Android Development] Whiskey103:
Thread cleaned.

Guys..keep it nice and friendly please ;)

cheers

Whiskey

Forum Moderator
[Galaxy S Plus I9001 Android Development] insestito:
I would like you to do a test with antutu, out of curiosity
[Galaxy S Plus I9001 Android Development] reklrekl:
GREAT!

i'd be happy if its getting really finished and perhaps improved.

is there any eta? (i know it's a stupid question, because u work hard on it)

thanks anyway for this great project!
[Galaxy S Plus I9001 Android Development] rayiskon:
the thread was cleaned bcoz of posts like this, do we really have to go through this all over again ?
[Galaxy S Plus I9001 Android Development] annqx:
Hm actually it was cleaned up because I reported someone for harassing / violating rules ^^ but you're right
[Galaxy S Plus I9001 Android Development] skywalker01:
Great work, YardE. I also fiddled a lot with modules and my own kernel and here is what I've found so far:

I was able to compile my own param_sec.ko and bthid.ko (both belong into ramdisk which I also modified a lot) and they work without a flaw. So that kernel tainted message mess (see dmesg) from these two is finally gone.

BT: does your bthid.ko start with errors or do you have other problems ? I can have a look into your dmesg and logcat and compare with mine when you attach them.

libra is not needed at all when you use the bcm driver module (dhd.ko).

I was also able to compile at least 10 different dhd modules (from different Nexus, I9000, gtab, HTC Flyer, Huawei kernels and so on) and they even start when I replace them in /system/etc/wifi. But they exit after some seconds, sometimes with error sometimes without (in logs). Seems that this is related to failed platform registering which means the whole ROM must be compiled in one piece and not just the kernel alone what is what I did so far. Therefore I still need to download the android source but repo and other tools don't work correctly on my old Debian lenny, so I have to upgrade first to squeeze and this will take some time.

But in the meantime I can share more of my kernel experience: firmware and nvram path are both read from wifi.conf or you can also hardcode them into the dhd module or even use your own insmod with the proper parameters, but all of this doesn't change anything. My best guess so far is that some lib in /system/modules must match with the dhd module and the kernel (my culprit is libhardware_legacy.so) ie. system and kernel must be compiled together to avoid all errors and warnings. Could be the same for BT and maybe other drivers (audio etc.) but that is still speculation.

The wlan source has its own debug option, if you set -DDHD_DEBUG in the bcm4329 makefile this will generate some additional info in the logfile but I guess you already did that. Maybe it is similar for BT although I don't have problems with that.

Hope this might help a little bit, maybe I can continue my work tomorrow.
[Galaxy S Plus I9001 Android Development] abbradar:
I have them compiled from source too, I'll post my dmesg later - haven't checked its logs for a while. I have known problems only with dhd.ko - I just could not find module which will work for us other than pre-compiled Samsung one.

Confirmed.

I had same problems when I tried to do this, too - I've tried two or three versions. While looking though the source, I've stumbled upon fome defines of platform type, like ARIES (cannot remember exactly), so it looks like we'll need some AriesVE modifications to compile it from source.

I think that for WLAN it's not that - in my build WLAN already works, and libhardware_legacy does exactly what is written in wifi.conf - loads module with specified arguments, and calls wpa_supplicant though init.rc. (though version from Cyanogen does not have even that file, and module arguments can be only hardcoded) It works when I use combo of libhardware_legacy from Cyanogen with hardcoded module paths, name, etc, dhd.ko from stock firmware, wpa_supplicant and it's related arguments in init.rc, and firmware (either our or from Cyanogen, which seems to be different), without any problems so far, so the problem must be in the module itself. You can check my device repo - it can give you some info on my configuration.

Hmm, I have tried this on WLAN modules, but I should try to add something like this to Bluetooth part too.

Little story on how Bluetooth works there - we have combo of rfkill switch, and userspace utility, named brcm_patchram_plus, which downloads firmware into FPGA. I haven't checked yet in which sequence it is done, and thought of adding some delays, because of strange appearance of my problem. I have Bluetooth started up one in about ten times, without any real modifications, just looking like based on pure luck, and I think it got to have something with delays.

Also, good work and thank you, hope we'll get though this problems.
[Galaxy S Plus I9001 Android Development] abbradar:
Bluetooth is finally fixed! It may be a funny story how: while groking brcm_patchram_plus code I've encountered delay which was performed when some special definitions were set. So I've done this, and it works now! This setting was created as workaround for SEMC devices, btw, but it helps us too.

I've commited my changes. Should I make another test build?
[Galaxy S Plus I9001 Android Development] broodplank1337:
Sound good! And if you make a test build I'm willing to test it (if you can confirm it won't hardbrick my device :P, I'm okay with softbrick but hardbrick nothnx :D)
[Galaxy S Plus I9001 Android Development] nail16:
Im always ready to test new builds :)
[Galaxy S Plus I9001 Android Development] knank:
Can you check if its possible to use bluetooth stack (the standar android bluetooth) with the i9001 (it's needed to use bluetooth game controlls (ps3 or wii).

Thanks ;)
[Galaxy S Plus I9001 Android Development] abbradar:
I'll post build after some more development, so it will be more interesting. I'll make benchmarks after I got everything, primarily GPU acceleration, working, it's pointless to do this at this moment. For now I'm messing with audio.

Bluetooth stack should work now, I have used Android standard interfaces and they are working. I'll make checks later, if you'll give me some piece of software to run.
[Galaxy S Plus I9001 Android Development] haydar100:
Cant wait :)
[Galaxy S Plus I9001 Android Development] knank:
Great news Bluetooth STACk on i9001 ;).

Only BLN isn't working :) (next step) XDDD

Thanks a lot for your time and effort
[Galaxy S Plus I9001 Android Development] Shtsh:
Bug reports:

Installed CM from backup.

Here bugs:

Keyboard is very small;

"USB Connected" notfication shows when phone is not connected;

Litghtening sensor don't work (no option in settings to use it);

On my phone adb does not working (but also in stock ROM - seems it my personal issue)
[Galaxy S Plus I9001 Android Development] abbradar:
Day of disassembling, reading avaliable source, and disassembling again... Close to no progress in both fields (camera and audio). I'm in process of understanding structure of audio drivers now, and for camera - Samsung's libcamera.so requires modified libcamera_client, using one from stock firmware for now. Camera is now crushing when starting yet again, so I'm studying logs now.
[Galaxy S Plus I9001 Android Development] herzau:
Good news for FM radio fix

I need more testers

http://xdaforums.com/showpost.php?p=25433617&postcount=3212

Arco with boot_exp4.zip the mac is real of the device or is it generated?
[Galaxy S Plus I9001 Android Development] silviu_iliescu:
Could someone please tell me if I risk fubaring my phone with that problem.Thanks!!!

---------- Post added at 01:46 PM ---------- Previous post was at 01:45 PM ----------

Camera should come in first place.

---------- Post added at 01:48 PM ---------- Previous post was at 01:46 PM ----------

How is the battery life with this new kernel and did the low quality calls problem disapeare or is it still there.Thank you very much arco for your great work!!!
[Galaxy S Plus I9001 Android Development] herzau:
works for me

try open "CMW ROM Manager" app and concede root access
[Galaxy S Plus I9001 Android Development] Mirceabadea:
Arco, you told me to give you feedback on in-call sound quality with all the kernels.

Well, with every single version you released from the begining when you ported CM9 for our phone, the in-call sound quality WAS LOW. Even today, with the newest one, two friends of mine told me to SPEAK LOUDER and they told me i'm in a war zone or something like that, they can't hear me well.
[Galaxy S Plus I9001 Android Development] mobuch:
Will test later on today and let you know what i get.

Seems to be real mac, since i get the same as i had on stock GB. Need to find my box to check if there is a mac printed on it to be sure (no info about mac on the sticker under battery :mad: )

Edit:

I'm blind or Samsung didn't give us mac of the wlan nic in the paperwork nor on the box or sticker.. but as I said - now I get the same mac as I was getting on stock GB
[Galaxy S Plus I9001 Android Development] chopin00:
It's a possibility to upload the newest kernel? All last links are dead.

Good job arco! Thanks!
[Galaxy S Plus I9001 Android Development] :
Tested it with 3 phones so far (1 was stationary one), speech quality and volume are very good!

For new kernel just can say, best build so far! BT, WIFI, BT-Calls, Sensors, all functionally. If any logs are needed, pls just ask for them.

Great job arco!