yashsingh1/xdaforums huggingface dataset:
[Nexus S General] KreAch3R:
I'm glad that's working! :) Another user mentioned that a wipe helped at this point, that's why I proposed it (and that's the reason we post public ;)). I should include it in the instructions.

What exactly is the apktool error output? Did you install the framework in the beginning? Make sure your directory doesn't include spaces. Also, attach the framework you are trying to modify here, to let me take a look.
[Nexus S General] ILCAMPIONE:
This is che point, i didn't understand what mean "install che framework" what is che exact command?
[Nexus S General] KreAch3R:
I have included it in the post:

apktool if framework-res.apk

I am not on Linux right now, but I think that if you run

apktool

only, it will show you the available options.

Also, take a look at this.
[Nexus S General] ILCAMPIONE:
The command "apktool b framework-res" give me this error: (i done "apktool if framework-res" and all other step)

I: Using Apktool 2.0.0-Beta9 on framework-res

W: Could not find sources

I: Checking whether resources has changed...

I: Building resources...

Exception in thread "main" /tmp/brut_util_Jar_6386131952073483242.tmp: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

brut.androlib.AndrolibException: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [/tmp/brut_util_Jar_6386131952073483242.tmp, p, --forced-package-id, 1, --min-sdk-version, 19, --target-sdk-version, 19, --version-code, 19, --version-name, 4.4.2-eng.fyodor.20140313.151711, -F, /tmp/APKTOOL9048715289597489453.tmp, -x, -0, arsc, -S, /usr/local/bin/framework-res/res, -M, /usr/local/bin/framework-res/AndroidManifest.xml]

at brut.androlib.Androlib.buildResourcesFull(Androlib.java:435)

at brut.androlib.Androlib.buildResources(Androlib.java:363)

at brut.androlib.Androlib.build(Androlib.java:286)

at brut.androlib.Androlib.build(Androlib.java:258)

at brut.apktool.Main.cmdBuild(Main.java:236)

at brut.apktool.Main.main(Main.java:88)

Caused by: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [/tmp/brut_util_Jar_6386131952073483242.tmp, p, --forced-package-id, 1, --min-sdk-version, 19, --target-sdk-version, 19, --version-code, 19, --version-name, 4.4.2-eng.fyodor.20140313.151711, -F, /tmp/APKTOOL9048715289597489453.tmp, -x, -0, arsc, -S, /usr/local/bin/framework-res/res, -M, /usr/local/bin/framework-res/AndroidManifest.xml]

at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:470)

at brut.androlib.Androlib.buildResourcesFull(Androlib.java:416)

... 5 more

Caused by: brut.common.BrutException: could not exec command: [/tmp/brut_util_Jar_6386131952073483242.tmp, p, --forced-package-id, 1, --min-sdk-version, 19, --target-sdk-version, 19, --version-code, 19, --version-name, 4.4.2-eng.fyodor.20140313.151711, -F, /tmp/APKTOOL9048715289597489453.tmp, -x, -0, arsc, -S, /usr/local/bin/framework-res/res, -M, /usr/local/bin/framework-res/AndroidManifest.xml]

at brut.util.OS.exec(OS.java:89)

at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:464)

... 6 more

can you understand the error? (may be this "libraries: libstdc++" is the problem, but it is installated!)
[Nexus S General] KreAch3R:
Check this out, use this command:

sudo apt-get install lib32stdc++6

I don't think I have experienced this error. Also, please share the framework file, to let me test. :)
[Nexus S General] ILCAMPIONE:
You are my HERO!! now i try the rest of guide, stay tuned ;)
[Nexus S General] draxxter:
I am finishing some optimizations soon and will post source and pre-compiled kernel with linaro toolchain.

I am trying to backport the latest development for F2FS.

Soon-ish.
[Nexus S General] Jhyrachy:
Any hope for a step.by-step guide on cyanogenmod M10 or precompiled files?
[Nexus S General] KreAch3R:
It needs the exact same steps, using the latest files (CM11-M10, latest Guru or stock CM kernel (boot) img). Do you need a more elaborate guide? Which part seems vague?

I can/will update the ROM files after my exams (ending in the end of September) (I won't have access to the device before that, too). :/ :)
[Nexus S General] Jhyrachy:
can i use your kernel image and your custom recovery even for CM11-M10?
[Nexus S General] KreAch3R:
I am pretty sure you can use my custom recovery (you wouldn't change yours if you just updated the ROM, right?). I am not so sure about the kernel, though. You should better ask at the Guru thread if you can use the version 1.0 (guru10.img) with CM11-M10.

*WARNING, PROCEED AT YOUR OWN RISK* If I were you, I would probably go rogue and try it, what more can happen than a bootloop, that a reflash can't solve? *BRICK WARNING*
[Nexus S General] explorer-10:
This may sound stupid, but is it possible to increase RAM space with this?
[Nexus S General] KreAch3R:
It's not stupid. :) But no, you can't do it with this mod. You can, however, as [MENTION=5528674]draxxter[/MENTION] shows, use some space for /swap. I don't know how that affects the RAM usage. Besides that, there are kernels for our Nexus S which use a big memory mod, that increases the available RAM space to the user, as I understand. Guru uses it, I think. Check in the kernel threads.
[Nexus S General] explorer-10:
Do you know if those specific kernels work for SlimKat?
[Nexus S General] KreAch3R:
I just noticed your signature, it seems you are already using such a kernel. As for the above question, I don't know, ask in their threads. :)
[Nexus S General] explorer-10:
My signature is actually outdated info. I'm not with slimbean anymore, I'm on slimkat with slimkat kernels
[Nexus S General] draxxter:
You can make a logical volume partition for swap usage (I made mine /dev/lvpool/swap with size 256MB and usually only 50-55% is used). Then you have to format it accordingly once with

mkswap /dev/lvpool/swap

Then either on an init.d script or through terminal you have to exec

swapon /dev/lvpool/swap

.

You can then check if swap is mounted by exec

cat /proc/swaps

.

For our device swap file is preferable to ZRAM. 512MB ram is soooo limited.

Thanks,

draxxter
[Nexus S General] ILCAMPIONE:
Hi to all

frist of all many many and many THANKS to [MENTION=3190122]KreAch3R[/MENTION] (you are great and very helpful man !!!) and also thanks to [MENTION=4353291]steven676[/MENTION]

Sorry if i didn't replay sunday but i installed the AOSP rom on my Nexus S "lvm-series" and all go great and smooth so i spent all my time on device :D :D :D

So also with some trouble, now i can say : this guide ROCKS !!!

I can upload the ASOP rom file if you think can be a good thing (can you guess me where i can upload the file?)

Ps. i guess to update the guide, with the Hints that you give to me

* a wipe if you can't restore backup

* "apktool if FRAMEWORK-RES.APK" (it'isnt so clear for me, but i am noob of android kitchen)

* and the right libraries that needs to rebuilt FRAMEWORK-RES.APK

Bye and thanks again (may be i will try this on i9003 :D)
[Nexus S General] noel8211:
Hey, im a noob when it comes to partitioning and commands. Can i flash all this to save me all the fidly work and everything will work as the OP's device? or do i have to actually follow the guides for this?
[Nexus S General] leap_ahead:
u uplodad ?
[Nexus S General] KreAch3R:
You still have to create the lvm partitions. After that, you can skip the parts where you make changes to the twrp, boot.img and the rom, and go to the last step, which is to flash each file.

BE CAREFUL with your data, including your SDcard, at some point they are going to be deleted. Please read the guide carefully.

TLDR; It isn't a flash 'n' play solution.
[Nexus S General] noel8211:
Thank-you for clearing it up for me :)
[Nexus S General] KreAch3R:
You 're welcome! I really think anyone with some basic linux knowledge can pull this off. I would suggest to give it a try. :)
[Nexus S General] noel8211:
Thank you go your words of encouragement, I will attempt this and see how it goes
[Nexus S General] Diokles:
after can update CM9 to CM10 snapshot?

now have snapshot CM10, i already use lvm in nexus s. can i update to CM10 now? i use OTA update(auto update in about phone).

lvm will not work after update? phone will not boot?

thanks.
[Nexus S General] KreAch3R:
I don't think that it's going to work. Boot.img has to be modified.

In 10 days or so, I will update my unofficial lvm CM rom file to M10.
[Nexus S General] Diokles:
thanks.
[Nexus S General] cshnz:
i don't know whats wrong with me, when i using the twrp recovery from daxxter i cant copying ROM.zip via MTP...the userdata is mounted but i can't copy anything...FYI i'm using windows 7..
[Nexus S General] KreAch3R:
Have you formatted the userdata? Can you locate it in "Computer" as an external drive? Why can't you copy anything?

Please wait for [MENTION=3122936]daxxter[/MENTION] to offer recovery-specific help, because I haven't had the time to try it yet. I would suggest a full twrp wipe, as others were helped by this (as you can read in the previous posts).
[Nexus S General] cshnz:
yes i already formatted userdata, the devices is mounted as MTP, it shows the correct remaining spaces...but when i copying something to devices the recovery restarted...then alert on my windows says devices not responding...
[Nexus S General] KreAch3R:
Please post your recovery.log, and in the meantime you can try my twrp img. Also, did you try wiping?
[Nexus S General] draxxter:
Sorry friend.

Yes you are right. Version 2.8.0.0 MTP was not working.

I will upload tomorrow the latest version that everything works.

By the way, you can always use ADB sideload.

Thanks,

draxxter
[Nexus S General] cshnz:
i use adb sideload...its booting but after that says device storage encrypted...and i must insert the password but i have no idea...i flash 3 different roms but the results always same...
[Nexus S General] draxxter:
That sounds like you are mounting the partitions with different filesystem.

Check that the partitions are formatted either from adb shell or within the recovery and try flashing again.

I think i stumbled upon such an occasion when i was implementing F2FS on my sources.

---------- Post added at 02:10 PM ---------- Previous post was at 01:56 PM ----------

BTW is anyone interested in a CM-M10 compiled with linaro 4.9.2 and -03 opt flags for ARM/THUMB and LVM emulated internal storage with /data and /system F2FS formatted?

I hit 6329 on antutu with this on stock cpu speed 1GHz.
[Nexus S General] cshnz:
yeah i wanna try it, please share it :D
[Nexus S General] KreAch3R:
Yep, I am too. Are you using ArchiDroid O3 optimization? Have you noticed any speed difference besides antutu scores?
[Nexus S General] draxxter:
Rom side i am using JustArchi Commit for Thumb and MW LTO enhancements.

Kernel side i use alot of ARM Cortex-A8 specific commits from Linaro and some kernel update commits for libs.

I will post once i finish some extra stuff i am missing.
[Nexus S General] draxxter:
Some delays occurred while working with GCC 4.9.x. Reverting to 4.8.3.
[Nexus S General] Sesme:
Awesome guide.

I use 500mb for system and 13,5g for userdata media is 500mb.

Have trouble with driver w7 XD... microsoft rules
[Nexus S General] draxxter:
Well for everyone wanting to test something out please find below.

https://dl.dropboxusercontent.com/u/8870510/cm-11-20141021-O3-LTO-crespo.zip

F2FS compatible

LVM compatible

03 optimizations with strict aliasing

Link Time optimizations

Built as release to avoid any debugging options/loggers that eat up performance

Linaro 4.8.3 Toolchain

392RAM on my device

You need to flash SuperSU after flashing ROM.

Test and revert with opinions.

I am making some changes on the kernel side but ROM side its pretty much as good as it goes for our device.

Thanks.

https://github.com/vakkasa
[Nexus S General] leap_ahead:
how to use this ??
[Nexus S General] draxxter:
Option A.

If you want to use the zip as is then you have to use the modified recovery i posted earlier.

1) You need to have the LVM partitions /dev/lvpool/system and /dev/lvpool/userdata

2) You need to change /system and /data to F2FS by clicking on Repair/Change Filesystem on the Advanced Wipe menu of TWRP.

3) You flash the zip and you are good to go.

Option B.

You swap the boot.img in the zip with something CM11 compatible like Guru (which is CM with BigMem + Smartass2) and flash normally.

This way you can enjoy the optimized CM11 ROM without the kernel options (F2FS, LVM).

Hope i helped.
[Nexus S General] KreAch3R:
[MENTION=5528674]draxxter[/MENTION]

I finally got the change to test your recovery and your optimized CM11 rom (w/ f2fs). Have you experienced these bugs?

In the recovery, MTP doesn't work (it crashes) when i try to copy files to the sdcard (twrp just restarts). In the ROM, MTP works correctly.

Some icons in the play store are distorted. I think it is related to the toolchain?

Overall, the recovery works great (except the MTP thing, but I don't think it is related to your changes), the ROM is fast and responsive. How did you make the kernel (boot.img) F2FS compatible? Have you considered adding more governors?

Great job!
[Nexus S General] draxxter:
Hello,

Well regarding recovery, yes 2.8.0.0 had MTP issues. Dees_Troy and team had fixed those in 2.8.0.1+ but i have not recompiled a new recovery due to it getting over-sized cause of the 03 optimizations that increase size overall.

As for the kernel part I initially started trying to backport F2FS from developing branch of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git.

I dropped it after a while because of https://github.com/nowcomputing/f2fs-backports that had already performed the task.

Finally thanks to arter97 i have now used his merge branch of https://bitbucket.org/arter97/f2fs-backport.

You can find a squashed commit of mine for f2fs for 3.0.101 kernel here https://github.com/vakkasa/android_...mmit/575399ca151ae778421325404405b450373742e8.

As for governors, the true fact is that i never thought of sharing before to the public and i was always happy with OnDemand.

When i finish some kernel changes i am trying now and reverting some others that i am not happy with and if i have some free time i might add some governors.

Thanks,

draxxter
[Nexus S General] cshnz:
i just use daxxter kernel from CM f2fs version...i use the kernel on my port PA roms. and works like a charm... with f2fs when transferring file to devices is so fast... :D
[Nexus S General] draxxter:
Are you using it with PA?

How is performance?
[Nexus S General] cshnz:
Antutu just give me score 5763 :D
[Nexus S General] draxxter:
Strange, I get with the CM11 rom i posted earlier from 6100 - 6300.
[Nexus S General] cshnz:
wow thats amazing... on my PA port rom sometimes its really hard to wake the device...so i put the minimal frequecy to 200 Mhz and now no problem at all... i think f2fs is a great potential for nexus s :cool: i hope to see more development about that :D
[Nexus S General] draxxter:
I updated the kernel sources with some arter97 magic.

Bad thing is my nexus s screen broke ...:crying:

and the latest CM11 build i compiled, although probably the fastest, has no working telephony.

Seems that it does not recognize the SIM card.

Any ideas?
[Nexus S General] KreAch3R:
[MENTION=5528674]draxxter[/MENTION]: I am sorry for your Nexus S. It is completely broken or a chip?

As for your latest build, I have no idea. I would look in my latest commits.

I re-tried your ROM / kernel, but had various problems with mtp - f2fs, and due to limited testing time, I regressed to building a CM11-M11/Guru combo with lvm only. I would love to try all the other optimizations though (if my skills allow that). Do you upload your commits here? (If so, hello πατρίδα! :)) Or is it better that I just modify your rom to work with ext4? Which one is correct?

Regarding your recovery build, I modified it to work with ext4, and works like a charm now. Can I upload the modified recovery here (so that I can change and complete the guide)?

After that, the m11 build will be uploaded. I am also working on a guide with my Nexus S setup (apps/hacks/modifications) that I use.
[Nexus S General] cshnz:
oh my god, thats bad news. i will :crying: too

hmm i've no idea for thats telephony. the telephony keep force closing or the signal wasn't existed without force closed telephony alert?
[Nexus S General] draxxter:
Πατρίδα indeed. :)

Touch screen is broken, phone still works and operates.

It seems the time has come to change over to new phone after 3 years.

Yes, in my github there are commits that i merge in the CM-11.0 tree in order to build my version.

Regarding F2FS and MTP it is strange., it works like a charm on my Windows 7, Ubuntu and Windows 8.1 boxes while rom booted.

It does not work on the recovery though, it crashes while transferring data, but I have not tested TWRP 2.8.1.0 yet.

Finally, the rom works with every filesystem, only limitation is the kernel and mine is F2FS based.

As i stated you can swap the boot.img with Guru and be full EXT4 compatible.

Thanks.

---------- Post added at 12:29 PM ---------- Previous post was at 12:26 PM ----------

No, it is not FC-ing. It does not ask for SIM PIN lock as if I have not inserted the SIM card.

Flashing my last weeks rom works though.

I have read that CWM-recovery might be the culprit though as i swap to it due to the 03 over-sized TWRP.

I will try building TWRP with 02 again to reduce size and check again.

Thanks.
[Nexus S General] KreAch3R:
I guess it's time then. Perhaps the new Nexus? ;)

I didn't know the ROM can be used with Guru w/ ext4. I will try it the next time I get my hands on the phone.

Regarding my issues, it is definitely my setup's problem, the PC I was using wasn't mine. I didn't understand though, do you have any issues with the Play Store icons (the app icons, e.g. during search)?

Lastly, do I have permission to upload the ext4 recovery? :)
[Nexus S General] draxxter:
The new nexus is GIGANTIC.

I will probably settle with LG G2 or Sony Z1.

Play store has distorted icons due to one of the 03 and linaro GCC optimization flags.

I tried a possible solution JustArchi suggested but it did not rectify the issue.

As for the recovery who are you asking permission from? CWM and TWRP are open source and it is also your thread :)

Thanks.
[Nexus S General] KreAch3R:
It is! :/ I was waiting for it but I am going for the Nexus 5, I think. Nice choices, both of them!

That's what I was referring to, about the icons. Thanks for confirming.

As for the recovery permission, I consider it part of giving credit to you. :) They are open source but you built it, I changed 3 lines of code. Thanks! ;)
[Nexus S General] zalho:
Hi everyone.

I messed up my Nexus. :silly:

Can anyone post an recovery & rom that is working with this method.

I can't install a rom and I don't know why. :mad:

BTW how can I reverse all this and back to the old folders size and restore a nandroid backup before all this.

Best,
[Nexus S General] KreAch3R:
Hello,

Don't stress. Unless it's something unique, it is reversible.

I have uploaded a working twrp+rom combo in the second post. I am in the process of updating it.

If you want to go back, you have to use a normal recovery, format the USB storage from the PC/or recovery (whatever gets access to it), paste inside the nandroid backup and then try to restore the backup. It should reformat the partitions and copy back your data.

If I were you, I would try to use my ROM and then try to get back.
[Nexus S General] zalho:
Hello.

This is what i get after the partitioning:

~ # ←[6n/lvm/sbin/lvm vgs

/lvm/sbin/lvm vgs

File descriptor 8 (/dev/__properties__) leaked on lvm invocation. Parent PID 100

: /sbin/sh

File descriptor 9 (socket:[1993]) leaked on lvm invocation. Parent PID 100: /sbi

n/sh

VG #PV #LV #SN Attr VSize VFree

lvpool 3 3 0 wz--n- 14.82g 288.00m

~ # ←[6n/lvm/sbin/lvm pvs

/lvm/sbin/lvm pvs

File descriptor 8 (/dev/__properties__) leaked on lvm invocation. Parent PID 100

: /sbin/sh

File descriptor 9 (socket:[1993]) leaked on lvm invocation. Parent PID 100: /sbi

n/sh

PV VG Fmt Attr PSize PFree

/dev/block/mmcblk0p1 lvpool lvm2 a-- 508.00m 0

/dev/block/mmcblk0p2 lvpool lvm2 a-- 1020.00m 0

/dev/block/mmcblk0p3 lvpool lvm2 a-- 13.33g 288.00m

~ # ←[6n/lvm/sbin/lvm lvs

/lvm/sbin/lvm lvs

File descriptor 8 (/dev/__properties__) leaked on lvm invocation. Parent PID 100

: /sbin/sh

File descriptor 9 (socket:[1993]) leaked on lvm invocation. Parent PID 100: /sbi

n/sh

LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert

media lvpool -wi-a---- 1.00g

system lvpool -wi-a---- 552.00m

userdata lvpool -wi-a---- 13.00g

~ # ←[6ncat /proc/partitions

cat /proc/partitions

major minor #blocks name

31 0 2048 mtdblock0

31 1 1280 mtdblock1

31 2 8192 mtdblock2

31 3 8192 mtdblock3

31 4 480768 mtdblock4

31 5 13824 mtdblock5

31 6 6912 mtdblock6

179 0 15552512 mmcblk0

179 1 524288 mmcblk0p1

179 2 1048576 mmcblk0p2

179 3 13978607 mmcblk0p3

179 4 64 mmcblk0p4

179 16 1024 mmcblk0boot1

179 8 1024 mmcblk0boot0

254 0 565248 dm-0

254 1 13631488 dm-1

254 2 1048576 dm-2

~ # ←[6nls /dev/block

ls /dev/block

dm-0

dm-1

dm-2

loop0

loop1

loop2

loop3

loop4

loop5

loop6

loop7

mmcblk0

mmcblk0boot0

mmcblk0boot1

mmcblk0p1

mmcblk0p2

mmcblk0p3

mmcblk0p4

mtdblock0

mtdblock1

mtdblock2

mtdblock3

mtdblock4

mtdblock5

mtdblock6

platform

ram0

ram1

ram10

ram11

ram12

ram13

ram14

ram15

ram2

ram3

ram4

ram5

ram6

ram7

ram8

ram9

zram0

After that what should I do?

In wich point should I flash boot file?

I cannot mount USB Storage on PC. I wiped data and sdcard but still can't.

I transfer the rom file to /sdcard/ with adb push but in recovery in sdcard I only have TWRP folder. It seems that it is not the same folder.

Can you help? Can you add me on skype "andre_alho"?

Thanks
[Nexus S General] KreAch3R:
I think that you have created the lvm partitions correctly. So, I guess you are in the 3iv step: Mount the USB Storage and format it like a normal USB Stick (FAT32, VFAT).

What problem do you encounter when you try to mount USB Storage? Are you using Windows or Linux? Did you check in Disk management? The problems you are experiencing were common when I first tried to do this, it was always due to my mistakes. I would suggest to re-do everything from the beginning. This means that you should delete the lvm partitions, as the LVM guide says (I don't have it open right now).

The guide does not pinpoint a step where you should flash the boot.img. Instead, I choose to include it in the ROM .zip. Please follow the guide.

As I have said to others, I think that we should continue solving the problem here, so that others can benefit from it. So, this is better than PMs or skyping.
[Nexus S General] draxxter:
After making the partitions you either have to format them from ADB Shell or from within recovery.

Just creating them is not enough in order to use them.

Then you can either copy the ROM to the /media partition or ADB push/sideload it.

As for mounting the usb storage in Windows that sounds like a driver issue to me.

Please try updating drivers from device manager.

Thanks.
[Nexus S General] KreAch3R:
2.0 Update!

It is LONG TIME overdue, but I finally managed to get my hands on my loaned Nexus S and modified the latest snapshot of CM11 to use LVM (links in the third post). I didn't use guru kernel in this version because I was having bootloops and remained with the stock CM11 kernel.

Besides that, I have uploaded the modified version of latest [MENTION=5528674]draxxter[/MENTION] twrp recovery (I modified it to use ext4, but he built it specifically for our mod, to make use of the internal SDcard storage, so kudos for that!), and updated the guide. No more hacks with the 1G partition, now everything is as polished as a stock newer phone.

Any questions, please ask. Happy New Year!
[Nexus S General] Sesme:
Awesome thx for your update !!!

Happy new year!!!