[ROM][6.0.1][GTI8552] Pac-Rom for Samsung Grand Quattro

[Krush206]

How is battery life and all? Can you make a kernel for this ROM?

I think this is more like a physical than a logical issue. Most Samsung devices are crap, especially their batteries. Like most people, my Galaxy Win Duos started consuming much more power after some months. This is due to poor manufacturing process, not a direct issue in the kernel or the OS. But of course, there are a couple of tweaks to save power on every Linux device. You could use the powersave governor, set laptop mode to 2 and use the NOOP scheduler.

su
echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo powersave > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
(This reduces I/O activity) echo 2 > /proc/sys/vm/laptop_mode
echo noop > /sys/block/mmcblk0/queue/scheduler
(If using a SD card) echo noop > /sys/block/mmcblk1/queue/scheduler

I'm not new into programming but kernel development. I will eventually learn about it.

TWRP is working fine Finally :silly:

But the PAC ROM isn't, I followed all your adb steps exactly and booted successfully. Soon or later, it will start rebooting randomly. Few times, it did not boot at all which I again have to flash the ROM. Even WiFi was working, all good except these boot issues.

I don't recall mine rebooting or having boot issues. But this ROM made my device heat a lot. Also, note that camcorder, bluetooth, mobile network search and Chrome downloads won't work on this ROM.

EDIT: Actually, Chrome downloads do work. To get Chrome downloads working (and apps which require personal data access), go to Settings > Apps, tap your app, select Permissions, enable Storage permission and restart your app (force stop).

 

[Krush206]

I've fixed the boot animation for this ROM and installed a bootloader from a first revision device. I thought the black screen issue on second revision devices was due to bootloader code so I installed (with shell commands) a bootloader from a first revision device. Unfortunately, it didn't work out as expected (though I only tried to boot a recovery image incompatible with second revision devices). The black screen issue is still present. I must also note that not all bootloaders from first revision devices will work out as expected on second revision devices. Be careful, they'll also show the black screen issue and you won't be able to install the original bootloader back with Odin because it'll believe your device's model is the one from which the image should be installed on. Though I haven't tried, it's merely a theory, it's good to note that, when you change the bootloader, you're able to install, without signature check failures, a original firmware with Odin for another device model, which is the upside of changing the bootloader. Other than that, I can't think of and didn't notice any other upside for changing the bootloader since I didn't have the time to check the system at all.
To change the bootloader it's required to have TWRP installed since I don't know if the device will still be able to boot if you install a bootloader with black screen issue. However, when I've installed such bootloader Odin still did recognize the device.

Download the file below, boot into TWRP, plug the device to the computer and use ADB to input the following commands to install the compatible bootloader.

adb push bootloader_rev1.zip .
adb shell cat dev/block/mmcblk0p1 > qcsblhd_cfgdata.mbn.bak
adb shell cat dev/block/mmcblk0p2 > qcsbl.mbn.bak
adb shell cat dev/block/mmcblk0p5 > oemsbl.bak
adb shell cat dev/block/mmcblk0p6 > appsbl.bak
adb shell "unzip -p bootloader_rev1.zip qcsblhd_cfgdata.mbn > dev/block/mmcblk0p1"
adb shell "unzip -p bootloader_rev1.zip qcsbl.mbn > dev/block/mmcblk0p2"
adb shell "unzip -p bootloader_rev1.zip oemsbl > dev/block/mmcblk0p5"
adb shell "unzip -p bootloader_rev1.zip appsbl > dev/block/mmcblk0p6"

This bootloader is from a first revision device model but should work with most devices from both revisions.
Bootloader for first and second revision devices.
To check if the bootloader has been successfully installed, boot into Odin mode and check the version label. It should be labeled as I8552XXANF1.

Download the file below and input the following commands to install the fixed boot animation.

adb push bootanimation.zip system/media/
adb shell chmod 0644 system/media/bootanimation.zip

Fixed boot animation.

I've also compiled the latest kernel update from GitHub which includes minor changes. Download the file below and input the following commands to install the new kernel image.

adb push boot_update.zip .
adb shell "unzip -p boot_update.zip > dev/block/mmcblk0p8"

Kernel update.

 

[Krush206]

Can you make a kernel for this ROM?

If you still care, @SonOfSparda, I made a new kernel with ZRAM and swap support for this device. It works fine so far.
I'm also porting Linux kernel 3.10 to it.