Closed ngoquang2708 closed 8 years ago
Oh dear, lots of RAM. Free to play games :D However, this is a bug of OC Kernel. Seems it exist since patching UKSM
Haha, huge amount of RAM!
share OC kernel !!!
@thanhthuy89 On XDA, Galaxy Ace 4 kernel. I've included CM12.1 version too
Bro, do you know how to build custom recovery? I need that to test f2fs with the phone's eMMC
Replace CM recovery source code with custom recovery source code.
Bad news is: My old HDD was accidentally dead, which was in recovery now. I purchased a new HDD and now have to use Windows to compile kernel :D Edit: OK, it has been recovered, so i'm testing it now
We need sth in the ROM to let it mount as f2fs, at least with update-binary, since my TWRP can't install the ROM with f2fs zip
I don't know. But I think f2fs it not good enough. I tried f2fs on my Raspberry Pi, and when it lose power, the file system is corrupted. It is not the case with ext4.
We use battery to power on the phone, so how can it lose power immediately? At least with insta-reboot, which makes the fs corrupted w/o fsync
And R.Pi uses SD to boot
My 16GB SD has 3GB partitioned f2fs and mkfs.f2fs has successfully mounted it, even formatting CSC partition still be able to mount and copy data there, but I don't understand why the system won't boot with f2fs data partition, at least with me
Now i realized that USB OTG was in the kernel source, and it was in defconfig too LOL
CONFIG_USB_OTG=y
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
Haha, I don't have a cable to test it :D
At first, it was not set, now i have enabled it Need volunteers to test it
Surprise, it doesn't work The main OTG source was removed by SPRD, and i need to port it from another kernels, which is a PITA Nevermind, gotta do it when have time
CONFIG_USB_OTG
just a trick from Linus, doesn't do anything
:)
Do you know how to make AROMA Installer? I'll get my kernels there, so no need separate boot.img. But... that seems can't be flashed
First time heard about it
Oh dear
It allows to install different versions of ROMs or kernels, just in one zip
Yeah, Linux 3.10.18 :D
Haha, this is what we need for USB OTG. Our OC Kernel missing these, so OTG doesn't work https://github.com/sprd-dev/kernel_common/tree/sprdroid4.4/drivers/usb/gadget/dwc_otg
Our current kernel tree has that source. Just need some configuration in fstab. I made some modification in fstab to support it in the future (when I have a OTG cable :D). On 28 Mar 2016 12:33, "Quyền" notifications@github.com wrote:
Haha, this is what we need for USB OTG. Our OC Kernel missing these, so OTG doesn't work
https://github.com/sprd-dev/kernel_common/tree/sprdroid4.4/drivers/usb/gadget/dwc_otg
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/ngoquang2708/android_device_samsung_vivalto3gvn/issues/28#issuecomment-202241198
Yes, but missing some codes, which is needed for OTG I've compiled, but.... white stripes :D
2MB more RAM :D
2G will good :D
I'll give you the broken OC kernel, so you can have tons of gigabytes instead of 2 :D:D
Do you have any ideas about bind mounting with Android fstab?
Bro, any ideas about this? http://hastebin.com/izujazakah.xml
Nevermind, I found the problem
Is that gralloc
?
Nope I was about making a flag in defconfig that only Marshmallow and Lollipop have to use Permissive SELinux, but fails. Now when I boot CM13, it was in "Enforcing", no wonder it can't boot :D
Now let's fix other bugs left. My exams are over
Now I got good news here: My soft keys also broken, because I get the phone to the swimming pool :D
You got a good friend, bro :D
And, you're right. FCs everywhere
Have to increase zRAM size to avoid memory leak, at least 256MB is enough
LOL
I have to remove all HAL modules except hwcomposer
and gralloc
in order to keep the phone in a stable state, not reboot everytime it run out of memory due to memory leak.
All of *.scx15.so?
Have to say, after booted you must kill SystemUI before it grows memory Else after 10-20mins it'll kill itself, then the phone become normal
I am investigating the cause of that memory leak.
You should see this: https://code.google.com/p/android/issues/detail?id=195104
OK, our media codecs cause it.
Anything in logcat? And I see VPX bug. Is that so? Code loop?
I think media server keep trying to load those media codecs and failed.
Need some patch in source. But, make audio work first :)
Let me sync your branch, then add adoptable storage commit IDK Marshmallow even detect the second SD partition
I pushed all of it.
What funny is that the Cyanogenmod File Manger app does not see the SDCard, but Setting's Storage & USB see :)
Track https://github.com/koquantam/android_device_samsung_vivalto3gvn/issues/86 here.