[ROM][UNOFFICIAL][JB] PAC-Man ROM for olympus

palmbeach05

Senior Member
Oct 12, 2012
4,292
1,795
243
Ok, you're right. It might be something wrong with TWRP. I used fastboot method and it worked, but wifi is still grey.
Thats where your problem is then. Kernel packages are not meant for fastboot. Use CWM or TWRP to flash.

Sent from my MB886 using xda app-developers app
 

torque

Senior Member
Dec 11, 2006
126
29
0
Wroclaw
Thats where your problem is then. Kernel packages are not meant for fastboot. Use CWM or TWRP to flash.
You don't get it, do you ? :p I tried to flash package via TWRP, but kernel won't change or wifi not working. I pushed libs then and write boot via fastboot with your img from package. After that new kernel is working without wifi, like before with mine build.
 

palmbeach05

Senior Member
Oct 12, 2012
4,292
1,795
243
You don't get it, do you ? :p I tried to flash package via TWRP, but kernel won't change or wifi not working. I pushed libs then and write boot via fastboot with your img from package. After that new kernel is working without wifi, like before with mine build.
Use CWM.

Sent from my MB886 using xda app-developers app
 

palmbeach05

Senior Member
Oct 12, 2012
4,292
1,795
243
You don't get it, do you ? :p I tried to flash package via TWRP, but kernel won't change or wifi not working. I pushed libs then and write boot via fastboot with your img from package. After that new kernel is working without wifi, like before with mine build.
ok I did find an error with my package. the boot.img inside is called new_boot.img instead of just boot.img. After testing this out on my own device with the modification to reflect just boot.img, the kernel did change, bt works, but wifi is down. not sure why :confused:
 

torque

Senior Member
Dec 11, 2006
126
29
0
Wroclaw
ok I did find an error with my package. the boot.img inside is called new_boot.img instead of just boot.img. After testing this out on my own device with the modification to reflect just boot.img, the kernel did change, bt works, but wifi is down. not sure why :confused:
This ROM has two wifi drivers: bcmdhd and bcm4329. It might be related.

Anyway, even w/o wifi, this ROM with newest build of kernel is mega fluid and stable.
 

palmbeach05

Senior Member
Oct 12, 2012
4,292
1,795
243
This ROM has two wifi drivers: bcmdhd and bcm4329. It might be related.

Anyway, even w/o wifi, this ROM with newest build of kernel is mega fluid and stable.
those are the two common wifi drivers for this device. And since they both were incorporated into the ROM, I included them in the kernel package. I mean if there are no problems with both of them present in the original ROM, I don't see a reason on why they would be a problem in the upgrade package. I'll try tweaking the package later on today and see if it just needs one or the other.
 

ASwagBoy

Member
Oct 20, 2012
26
34
0
24
Alajuela
those are the two common wifi drivers for this device. And since they both were incorporated into the ROM, I included them in the kernel package. I mean if there are no problems with both of them present in the original ROM, I don't see a reason on why they would be a problem in the upgrade package. I'll try tweaking the package later on today and see if it just needs one or the other.
Maybe if you change this line "wifi.interface=wlan0" on build.prop to "wifi.interface=eth0" wifi will work on other kernel.
 

palmbeach05

Senior Member
Oct 12, 2012
4,292
1,795
243
Maybe if you change this line "wifi.interface=wlan0" on build.prop to "wifi.interface=eth0" wifi will work on other kernel.
Maybe. I mean that kernel is the one just released by krystian, and he built the package for epinter's cm10.1 which does say wlan0, so idk, but I will give it a shot.
 

torque

Senior Member
Dec 11, 2006
126
29
0
Wroclaw
I remember that in older kernels (epinter's source) we had problems with tethering. Tethering was a problem of module libraries. New kernels have bcmdhd (if I'm correct). So solution for compatibility with PAC is to change module for rom on new kernel. I don't know exactly if it's only kernel related OR it can be change somewhere in ROM to force use new kernel libs.
 
Last edited: