yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
You can't do that. You'll need to build your kernel from source to add governors and io schedulers.

The kernel is gpl, so you should be able to find the source from your manufacturers website.

You are correct, unpacking the boot.img will only produce a ramdisk and compiled kernel. There is no way to un-compile it to make modifications, however, you can make modifications to the ramdisk and swap out the kernel if you have another for your device. You would then need to re-compress the ramdisk using the correct kernel command line for booting your device. If that lead you to the bootloop then you'll need to debug using dmesg/last_kmsg.

I still think your better off building from source, especially if there is a cm for your device, that means there should be a cm kernel you can build for your device ;) its the only way you can add features to a kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
^^ this ...

Just build the kernel from source if you want to add new features. It's the only way to do it. Dicking around with uncompressing images is a pure waste of time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] desalesouche:
f2fs

hi all. hope all of you are fine.P

i am still working on f2fs.

here is the list of all the file i think i have to make change:

https://github.com/DESHONOR/BroodRO...30-common/blob/master/recovery_recovery.fstab

https://github.com/DESHONOR/BroodROM_device_huawei_msm7x30-common/blob/master/ramdisk/fstab.huawei

https://github.com/DESHONOR/BroodROM_device_huawei_msm7x30-common/blob/master/ramdisk/init.huawei.rc

(see line 202 to 216 for last link)

i did made the ext4changed to f2fs but i let files here in original state so may be someone can point me in right way?

so to make a point:

i made all necessary patch and change related to f2fs.

i have f2fs kernel, i can build f2fs rom and binaries, and i have f2fs twrp.

i can also format in f2fs with zip or with adb shell.

i can read that my twrp wipe/format with f2fs.

the only problem is that it refuse to mount cache and data.

so that makes my f2fs rom not booting.

i don't have logcat cos stuck at bootanimation.

how can i make data and cache be mounted for f2fs?

thank you.

edit: i am wondering thanks to NABENDU1 from xda if i should add something like that to my init.rc:

on fs

mount_all ./fstab.mako

but adapted to mine which is huawei...

hope it would do the trick.

will feed back...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Hello folks! I am trying to build slimkat for i717. The build finishes....no problems...but all i get after flash is black screen. Can anybody help me to get this thing booting?? Thanks.

Using slims kk4.4-caf branch

and

Using this kernel here:

https://github.com/patch-Adams/HERC-KERNELS

and I haven't pushed my device tree over yet....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Movm:
Is there a bootanimation?

Gesendet von meinem U8860 mit Tapatalk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Nope. Nada. Just black. Not even Samsung word before the animation??
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Movm:
Hmm... Did the kernel work in other roms ? And - take a look at the image folder. Is all fine there?

Gesendet von meinem U8860 mit Tapatalk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:


EDIT:

my slim out etc etc does not have an external folder....I can only assume it should be there....build flag somewhere??
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Sounds like kernel is busted. I'm derped out right now on Benadryl so looking at source might not be a goo idea ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Kernel works with other roms??? And whenever you have time to look....that would be amazing if you could....

I pushed my device tree so far this is what I have....

https://github.com/patch-Adams/android_device_samsung_quincyatt/tree/kk4.4

Thanks guys!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
I've gotten several SlimKat builds successfully compiled with the CM "next" kernel. See if you can compile a good build with that one.

Got a new SR i727 one brewing right now, in fact ;)

Afaik, the kernel is in /kernel/... not /device/...

EDIT: Can the Note use the msm8660-common kernel? I see that in BoardConfig. Not sure about that one...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Movm:
I mean the folder when you put your device in pinkscreen to computer
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
I'm not familiar with Quincy, however if kernel splash doesn't pop up or it gets stuck on it means kernel is busted lol. You sure you are using correct toolchain?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Not sure which is the correct one. I just assumed that because it built, the kernel was ok??
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Movm:
Easy question: can you use 4.2 CM kernel in 4.1 JB miui rom? What modules to port?

Gesendet von meinem U8860 mit Tapatalk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
I see CM11 is merging the next kernel on our device, but I don't see the changes on github. Does anyone know the path its being maintained so I can add it to roomservice?

<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" />
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Kiltnar:
Change revision to next. revision="next"

Add that at the end before the />
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
Thank you!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
The 'next' branch has already been merged into the 'cm-11.0' branch, and there have been some other changes made to the 'cm-11.0' branch, so the 'cm-11.0' branch is currently ahead of the 'next' branch.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
That is what I thought, but I didn't see the commit's.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] new ion?:
Probably filull wipe. Herc owner too, and that's cuz TC is going to fix a bunch of stuff then release another one... whereas here its just building nifhtlies with cherry picked fixes :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
That one doesn't work for me either. I get the same thing as with Camera FX, black preview screen, and no option to take a picture. Not a big deal for me (although I would like it to work!), I just don't understand why it doesn't work for me, but does for pretty much everyone else.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I have no way to be sure, but I think the new gapps did it for me. I had nothing but trouble yesterday. Fix permissions, reboot, nothing worked for very long. I installed the 803 build, installed 730 gapps, fixed permissions, and so far so good. I'm even trying to fake it out; use it, turn the screen off, come back and start it up to see if it'll hang. Like I said, so far so good. I did a dirty install of everything I did this morning, just to add as many details as possible.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
Yea I'm still getting no luck on rogers 08/03 build with newest gapps
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Locksmith81:
Try the newest inverted gapps
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
Inverted didn't help either
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] iandr0idos:
Just wanted to let everybody know.

Camera is flawless on CameraFX with the earliest build of gapps.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
Just downloaded camera fx and it got my front cam workin now just to fix my back
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] itwin504:
You're not the only one. Same here. Tried all sorts of things.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] iandr0idos:
Have you tried wiping cache and dalvik?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ironcrotch:
Any link to the 730 gapps or the latest, only one I can find is the 0726 one.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] itwin504:
Yes. Did it all and no luck. Camera FX front camera does work, but not the back. So halfway there.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
did a sync about an hour again and building right now. Lots like lots of good stuff got merged today including some camera drivers. Really excited that some great things were added tonight. I'll have it up as soon as it's done building for people to test.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Building as well here. Fingers crossed!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] chinthekng:
cant wait to try out what you guys come up with ive been wanting to build but summer schools been holding me back but next weak im gonna get to business
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I was in a hurry today and assumed the gapps were new. I used what roger posted with his new build. 726
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Let me know and I'll put it up front. Gonna work on building when I get home from my youngest sons first day of tball
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
That sure was a ton of merges today, did you cherry-pick anything for your build that wasn't merged?

Question I briefly looked over the commits on gerrit and didn't see anything related to the Skyrocket camera for JB can you point me in the right direction?

Roger:cool:

---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------

726 is the version I'm using and everything is working, I say if it ain't broke don't fix it but people are reporting success with the newer gapps.

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Decepticaons:
Anyone have the newest build with the newest gapps included?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
Check the Facebook group, posted the gerrit change that interested me the most. Tons of drivers, many camera references. All Samsung.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
The merge commit is there, and all the commits from the 'next' branch are there...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
https://github.com/CyanogenMod/andr...mmit/cdb2769fe42d92f8f0779542459203ee5ee863ae

;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
Man, my github searching skills really suck. I found everything except that. This is what long term exposure to Team Foundation Server does to you folks. Thanks for showing me the way.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Haha, np, you're not alone... I just happened to be poring over the assault of recent commits and merges and remembered that one. I was using the next kernel for a while but now it's merged with cm-11.0.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
I am now building roms and I am trying to incorporate the Diablo kernel into CM 11 to see if the vibrate issue is gone. First build without cleaning with the new kernel was successfully and I got boot with Diablo, but since the build date was from a couple days ago and the vibrate issue was still there, I decided to "make clean" and start the build, but it failed on the qcom files. I removed the qcom source from a few days ago and resynced so I am seeing if it builds now. If it fails, I wonder if I would have to use the qcom from Hellybean's source.

Edit: Yep it failed with the same error: "hardware/qcom/media-caf/mm-video/vidc/vdec/../common/src/extra_data_handler.cpp:246:7: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]"

I don't want to use Hellyybean's qcom source because recently CM merged the FFMpeg and the Github's qcom for Hellybean is 4 months old. Any ideas?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
What was the vibrator issue you were having? I fixed one on my device with a patch from Google to the char device driver. The issue was it wouldn't always load on boot and it was very random when it happened. Is that the same as your issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
The official CM nightlies have an issue where certain reboots would not allow any form of vibration to be turned on. This seemed to be caused by the merge from the -next branch of the kernel to the cm-11.0.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Try applying this commit to your kernel:

https://github.com/titanic-fanatic/...mmit/ada41591fa705cf407d91337c0d3b370eb06ee4b
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Do you think that will fix the qcom error I had before or is the fix for the vibrate? I think the kernel is not compatible with the new mm-video that was merge with CM.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
This is for the vibrator issue.

For the other issue, are you using media-caf from cm or one forked in HK? if it's forked, I would diff that file with the one from cm to understand better the differences. From there you may be able to determine a fix. It appears to me that both types are in fact unsigned int so one might need to change to the other and a diff might show that.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
That isn't an error, that's a warning. Compile warnings are everywhere when building the ROM; they're normal.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Yeah but I get lots of that exact message before it suddenly stops building. The only change I made to cause it not to build after using make clean was to add the Hellybeans Diablo kernel source. I made sure it is msm8660 and the source in the roomservice file is correct. I don't want to download the 17GB of all the files if I know it still might not work as I have a download cap with my ISP. I wonder if that is one reason why new builds of the CM 11 with Diablo kernel hasn't been updated on Goo.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
If your building with multiple threads (-jxx) then the make error could be way earlier in the output in the console. Check higher for lines starting with make to find the errors.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Thanks I did notice it but didn't copy down the other error. Thanks for the help. This is my first time building and decided to give it a shot. I may wait a couple days and give it another shot.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Np. Just another tip, if you run into a bunch of build errors, it may be useful to run your build again with -j1 so that you get the error messages in the right order ;) also, you can record all error output by spending this to the end of your mka command
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Yeah I ran the build normally again after rebuilding the repo and here is the make error: "make: *** [/home/andrew/android/out/target/product/skyrocket/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec.o] Error 1."

The next line just says waiting for unfinished jobs. I made sure to start a fresh build and my out folder was empty, but I will use your make bacon to see if it builds using that without clearing my out folder and look at the error log.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
I know you are being sensitive to data usage but I had similar issues with a corrupted repo when syncing using more that 4 threads. Once I figured that out, random compile messages went away and i get consistent compiles every time now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Are you saying that you use repo sync -j4 instead of the posted instructions showing repo sync -j16?

I have seen plenty of non-repeatable build errors lately, and I might try that to see if there's any difference. Thanks.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
My rule of thumb that works when repo sync is -j5 ;) I think I read that somewhere a while ago. If you setup special keys on your Linux, then you can do faster syncs. I think it mentions this I the aosp build instructions ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks. If this turns out to be what has been plaguing my builds, I'll be thrilled. The randomness of the errors I've gotten isn't explained by anything else that I've found.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ya, look up further. Thats not an error...[-Wformat]" If you need to, compile on fewer threads. Ex. make -j2 instead of 4. or make instead of mka. You will see more of the error the next time.

Also you guys. It's called next for a reason. lol Meaning it's not ready for use till it disappears. That happens when it gets merged so there is no real reason to change your roomservice.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Yeah I thought only using one different source from CM would work. I am using CM-11.0 instead of next. Maybe because of all the changes is why its not building with Diablo kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
I'm super excited to see you are building, Andrw. I usually find myself looking to see if you've commented on items lol.

If you need a tester, I will gladly try it out for you whenever.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
What commands do you personally use to build. I am using some custom sources for CM 11, but will the standard "brunch cm_skyrocket-userdebug" work?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
Your timing couldn't be better, I was going to start a similar discussion.

I keep a build script in my build directory for repeat ability.

~/CM11/mybuildscript.sh

repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
make clean
repo sync -j4
. build/envsetup.sh
vendor/cm/get-prebuilts
repo sync -j4
breakfast cm_skyrocket-userdebug
mka bacon -j4 2> log.txt

I have been doing this for each build directory which duplicates a lot of data.

I was considering leaving the CM11 as is but referencing it from other build folders that also use CM sources to cut down on space used. See the repo command.

~/CM11-Sultan/mybuildscript.sh

repo init --reference=~/CM11 -u git://github.com/CyanogenMod/android.git -b cm-11.0
make clean
repo sync -j4
. build/envsetup.sh
vendor/cm/get-prebuilts
repo sync -j4
breakfast cm_skyrocket-userdebug
mka bacon -j4 2> log.txt

I was curious how others are structuring their builds to be more efficient, and what pitfalls this might create.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Thanks, I am running a build as a test using your msm8660 from the device and kernel to see if it builds successfully. I was just referencing HK kernel in the roomservice.xml with all other CM 11 sources for the skyrocket left by default. I made sure before I synced to remove the msm8660 folders and the git for the kernel so it would pull the new HK source. I did notice when my only build that was successful without cleaning the build folder, did have a 5-second delay so the media-caf may be to blame.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
I think that's what I used recently to build CM. After struggling with SlimKat for a long time, I needed some success therapy, lol.

Interesting... How many processor cores are you running, and are you running Linux native or in a VM like me? I was under the impression that the -j(whatever) should be 1 more than the number of processor cores you have. Since I changed my repo sync command from -j16 to -j5, I stopped getting build errors in different random locations.

My VirtualBox Linux Mint 15 x64 VM is running on an AMD 965 quad core @ 3.6GHz with a 2.7GHz cap, and with 4 GB RAM.

Here's my Slim commands:

~/slim44/

repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4-caf
make clean (or make clobber, depending on what I've edited/changed since last run)
repo sync -j5
. build/envsetup.sh
lunch (choose slim_skyrocket-userdebug,#53 typical)
make bacon -j5 2> log.txt
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
I am running my Linux with VirtualBox, I have tried to use Diablo Kernel from HellKat, but using CM's sources for the msm8660, seems to be causing problems. I found [MENTION=2993366]ThdDude[/MENTION]'s guide for Unofficial CM 11, but his sources haven't been updated for some time and Fetching Project freezes at 99% when trying to sync.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
I also ruin mint 15 but not in a vm. The j command tells the compiler how many individual threads to run concurrently while building. I use 24, but have a pretty powerful quad core processor so each core runs 6 concurrent threads.

I also use a build script that can be found here

https://github.com/titanic-fanatic/android_build_scripts

It's a little more robust and accepts command line arguments ;) your welcome to use it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
I was initially running Ubuntu 12.04 in a VM on my Win 7 build box and having lots of issues with threads, space, and build time. I decided that I no longer needed the Win 7 instance, so I wiped the box entirely and went native Ubuntu 14.04 and that is the build box I use today. My cable system runs 30-50 Mbs and unlimited so downloading data is not an issue, and build times are usually about 20 min.

Hardware:

AMD Athlon(tm) II X2 B26, 8GB RAM, 300GB SSD

Curiously, what does your manifest for slim 4.4 look like? It would be nice to get some updated manifests for all the KK flavors.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
I am currently building a slim rom to see how it goes. Can you keep the local_manifest/roomservice.xml file to grab from different sources or is it a different file?

Edit: Nevermind when I tried building, it created another folder with slim's manifest and I found it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Here's their main platform_manifest.xml (creates manifest.xml in the .repo folder):

https://github.com/SlimRoms/platform_manifest/blob/kk4.4/default.xml

and my .repo/local_manifests/slim_manifest.xml is slightly modified from stock so I can update and try some things. Also note that my slim.dependencies file in the device tree contains only open and close square brackets. This way, when I lunch it doesn't overwrite my custom local slim manifest:

I'd like to find a good, inexpensive dedicated build box at some point... I can't part with my Win7 x64 as it serves up DVR, Photos, Music and acts as a Backup server for a few other PCs in my home. I tried to get the DVR functionality/sharing running under Mint but I had some problems with it when I tried it a while back. :)