[KERNEL] 2.6.29.6-nAa-jb-03 [23/11/12] Custom JB kernel + CWM Recovery - Sony Ericsson XPERIA X10 Mini

Before unlocking your bootloader, read this thread
If you brick your device, you are the sole responsible.
Preface:
Read through this post. Don't rush into flashing. Be sure you understand the process before you start
This is a custom kernel developed for Android Jellybean
Do NOT try this kernel on other Android versions - you are totally unsupported
This kernel introduces custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Features:
Forked from nAa-ics-04 (all ICS features are already in there)
Built with linaro-4.7.1 toolchain
CWM-Based Recovery 5.5.0.4
Custom mtd partitioning scheme suitable for JB
Modular recovery flashing support (more on that to come...)
Tracing support for JB
pmem: bring up2date with CAF 2.6.38
genlock/kgsl fixes
Triple buffering support for msm framebuffer
Much more RAM for improved multitasking experience (shakira: 186MB, robyn/mimmi: 187MB)
FAQ:
If you have any issues, please read the FAQ thread first: http://forum.xda-developers.com/showthread.php?p=30297163
Requirements:
Unlocked bootloader --> http://forum.xda-developers.com/showthread.php?t=1254225
MiniCM10 or any JB, source-based ROM (install this kernel first, format /system, /data and /cache, then install the JB ROM)
Flashtool tested to be working with your phone, e.g. from here: http://www.multiupload.com/GYL7A7XQBT Original flashtool thread: http://forum.xda-developers.com/showthread.php?t=920746
Install:
Backup
Unlock your bootloader as described here: http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3 or here: http://forum.xda-developers.com/showthread.php?t=1254225
Download the kernel ftf file from here and move it to Flashtool\firmwares so that Flashtool can pick it up
Flash the kernel via Flashtool
Reboot and you should see the kernel boot animation
[*] (First time only) Get into recovery and format /system /cache and /data manually
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uninstall:
Flash back to stock using SEUS.
OR
[*] Format /system /data and /cache via CWM and THEN flash another kernel via Flashtool
Sources:
The linux kernel is GPL'ed, everyone who does modifications should make them publicly available.
https://github.com/nobodyAtall/nAa-kernel-jb
Donate:
If you are enjoying my work please consider donating:
.
Donations are voluntary but allow me to spend more time on this project.​
Disclaimer:
I can't be held responsible if this Kernel bricks your device or makes it explode in your hands! Use it at your own risk!
​

Changelog:
### nAa-jb-02
* Ramdisk changes
* Increase vm_max_readahead to 1024Kb
### nAa-jb-01
* Forked from nAa-ics-04
* Tracing support for JB
* pmem: bring up2date with CAF 2.6.38
* genlock/kgsl fixes
* Triple buffering support for msm framebuffer
* Much more RAM
* Custom mtd partitioning for JB

MTD partitioning for Jellybean:
localhost / # cat /proc/mtd
dev: size erasesize name
mtd0: 10500000 00020000 "system"
mtd1: 00500000 00020000 "cache"
mtd2: 0bfc0000 00020000 "userdata"
mtd3: 00a00000 00020000 "recovery"
localhost / # df -h
...
/dev/block/mtdblock0 261.0M 238.1M 22.9M 91% /system
/dev/block/mtdblock2 191.8M 86.5M 105.3M 45% /data
/dev/block/mtdblock1 5.0M 780.0K 4.2M 15% /cache
...

YYYEEEAAAHAHHHH !!!!
SANKYUUU !!
Going to test ASAP

nobodyAtall said:
MTD partitioning for Jellybean:
localhost / # cat /proc/mtd
dev: size erasesize name
mtd0: 10500000 00020000 "system"
mtd1: 00500000 00020000 "cache"
mtd2: 0bfc0000 00020000 "userdata"
mtd3: 00a00000 00020000 "recovery"
localhost / # df -h
...
/dev/block/mtdblock0 261.0M 238.1M 22.9M 91% /system
/dev/block/mtdblock2 191.8M 86.5M 105.3M 45% /data
/dev/block/mtdblock1 5.0M 780.0K 4.2M 15% /cache
...
Click to expand...
Click to collapse
How to use mtd partiton???
Sent from my U20i using xda premium

I tried to move on, to use another phone, but nAa keeps surprising us with impossible ROMs so i´ll stay with my mimmi as long as nAa continue to make it´s magic. Congrats, you´re the best dev.

Does this kernel suports linux swap partition ?

useful links :
[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
$find other useful link in miniCM7/9 miniFAQs $
Perfomance :
recomended settings :
perf related :
CPU: keep default, but enable UnderVolting (and set on boot if you don't OverClock) (settings>performance>CPU)
RAM : to optimize RAM usage, use KSM, zram (18%, default) and allow purging of assets (settings>performance>memory managment)
I/O : keep NOOP, this is the default and the best for flash memory
other :
in settings>developer options
enable USB debugging,
debug notification,
set all animations to 0.5 (electron beam CRT animation will happen no more)
enable "kill with back button"
________________
for whose who feel the system slow and laggy, just try the SWAP (SDcard class6+ recommended)
SWAP, there is two "kind" of swap : using a partition on the SDcard, or using a swap file
both are good, but some SDcard/phones react better with the one or the other​
let us start with the partition way : it is more complicated than the file method, but as some advantages
pros: once it is set up, no need to care about it anymore, the SDcard can be mounted to PC easily without latency
cons: a little complicated to set up, and once it's done, it is as complicated to revert as to set up; to change swap size, you need to repeat the process (formating and partitioning SDcard)
needs a clean install of miniCM10:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size) any data on phone memory will be lost
set up your swap:
==> go to /advanced/Partition SD Card
if you don't want to use a2sd, then choose the minimal size for ext, and the size you want for SWAP
it will FORMAT your SDcard ! any data on SDcard will be LOST
and install the rom
swap partition should work
what doesn't work is the swap info menu
to revert : format SDcard in phone settings : it will FORMAT your SDcard ! any data on SDcard will be LOST​
____________________
now, the swap file way : it is really simpler than the swap partition, works great but has some drawbacks
pros: easy to set up, easy to revert, and the size can be choosen at wish at anytime (in settings>performance>memory>Swap settings)
cons: high latency when mounting SDcard to pc, it can take forever (really quicker to use CWM mount and storage capability to use the SD on the PC, than using android way)
you must perform a clean install of miniCM10 (by formating /system, /data and /cache) any data on phone memory will be lost
install the rom zip, the gapps, and boot up your phone
set it up
once your rom is ready to use,
go to settings>performance>memory>Swap settings
choose "enabled"
choose the size
allow system to get SU permissions
wait for the pop up "swap enabled"
enjoy, it is simple and can be disabled on wish​
to see if you swap works, open terminal, and type the following :
Code:
free

I can`t in to recovery, I try reflash the kernel but nothing happened, and yes I press back bottom, any help, with nAa-13 work the recovery...

The "Reboot into recovery" option isn't working (from within recovery or jellybean), always have to do it manually w/ multiple back button presses.

herbesi01 said:
I can`t in to recovery, I try reflash the kernel but nothing happened, and yes I press back bottom, any help, with nAa-13 work the recovery...
Click to expand...
Click to collapse
The same issue. After formating on nAn-13 kernel /system, /data and /cache and flash the kernel i cant get into CWM on nAn-jb-01 kernel. Any ideas what seems to be a problem?

Mitchio said:
The "Reboot into recovery" option isn't working (from within recovery or jellybean), always have to do it manually w/ multiple back button presses.
Click to expand...
Click to collapse
Works here. You have to press home after a little bit and it will reboot fine rather than being stuck on rebooting
X10man
Sent from my U20i using xda premium

x10man said:
Works here. You have to press home after a little bit and it will reboot fine rather than being stuck on rebooting
X10man
Sent from my U20i using xda premium
Click to expand...
Click to collapse
It reboots fine, when I select reboot into recovery (either from within cwm or within the os) it just boots as normal and goes into the os; as opposed to booting straight into recovery.

Very good kernel!
Now my cpu can run also at 787mhz without problem! (with naa-ics-04 mi limit was 748mhz).
Inviato dal mio U20i con Tapatalk 2

noob question here, how do you format /system /data and /cache manually in CMW ??
---edit
found it in mount & storage n.n

SleepingTurtle_I said:
noob question here, how do you format /system /data and /cache manually in CMW ??
---edit
found it in mount & storage n.n
Click to expand...
Click to collapse
In CWM recovery go to mounts or something that like name and go into that menu and you will see these options.
Sent from my U20i using xda premium

This doesn't work for me
I can't get back to recovery

@all the complains about stuck restart.
IF YOU ARE STUCK:
Install U20_nAa-ics-04_2.6.29.6-nAa-ics-04.zip flashing the same way.
wipe /cache /data /system via CWM then follow the instructions from nobodyAtall
IF YOU ARE NOT STUCK:
wipe /cache /data /system via CWM then follow the instructions from nobodyAtall

@naa
Could you implement the 200mb ram fix on the cm7 or cm9 kernels or would there be side effects?
Sent from my U20i using xda app-developers app

ales47 said:
@naa
Could you implement the 200mb ram fix on the cm7 or cm9 kernels or would there be side effects?
Sent from my U20i using xda app-developers app
Click to expand...
Click to collapse
No, this is only for JB. Other android versions will probably have issues.
Sent from my Galaxy Nexus using Tapatalk 2

Related

[DEV] [ROM] [N1] Evervolv Jellybean (4.1)

Jellybean 4.1
ALL USERS SHOULD UPGRADE TO JELLYBEAN 4.2
Known Issues:
USB Tether
P2P: (not supported by hardware)
...
Click to expand...
Click to collapse
New BLACKROSE Hboot required for jellybean
Downloads: MD5SUMS
System: 260 Cache: 8 Userdata: 168 (recommended, future proof, fits any gapps)
System: 250 Cache: 8 Userdata: 178 (should be safe)
System: 230 Cache: 8 Userdata: 198 (possible but you need to use bextons gapps installer and dont install offline voice recognition)
System: 210 Cache: 8 Userdata: 218 External gapps required (see 3rd post)
Why does /system need to by so big? Well to put this in perspective the gnex and n7 have 600mb /system partitions. So their /system is larger than our entire nand (~430mb usable). The 'base' android build is <200mb. The real bulk comes from gapps which are like +40mb the bulk of that is the new voice recognition dictionaries for google now. So theres the gist. Now heres the problem. Dalvik-Cache will be no smaller that 100mb so we're pretty much left with 60mb for apps and data. Which is way too small. Which makes a2sd pretty much required. If youre like me and have <10 apps the builtin a2sd should work fine otherwise you will need m2sd (see QA below) or you wont be able to install /anything/ from the market due to 'low storage space' errors.
To flash
Code:
adb reboot bootloader
fastboot flash hboot hboot_jellybean_260-8-168.nb0
fastboot reboot-bootloader
Should see "Jellybaby" on second line
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase cache
Boot recovery. Flash your zip
QA:
**I dont have enough space for all my apps? A: try m2sd
**Where can I get info on the builtin a2sd? A: see here for quick run down.
**What is blackrose? A: Please do NOT try and flash this until you find out. And do NOT ask in this tread
**Why is my screen not working? A: Reformat your sdcard. Sounds stupid but its the answer
Click to expand...
Click to collapse
----------------------------------------------------------
For tarball: It is now xz compressed (depreciated new method below)
Code:
tar -xaf <release>.tar.xz
fastboot erase system
fastboot flash system system.img
fastboot erase boot
fastboot flash boot boot.img
To flash with fastboot: use the zip appended with "-fastboot-update"
Code:
fastboot erase boot
fastboot erase system
fastboot update Evervolv-3.1.0-<release>-fastboot-update.zip
DOWNLOADS
Downloads: http://dl.evervolv.com/
Nightlies
For nightly changelogs reference gerrit. or the changelog.html in the dl directory for shortlog (blank means no changes were pulled)
These are automated builds and might not work properly but the general rule: its probably fine.
Gapps:
Usually the newest is best (http://goo.gl/LJiTC)
Releases
thanks to bexton for the host for releases
Note about *mini* builds: Strips out video editor, boot animation, international dictionaries, some fonts and ringtones to fit on smaller /system. needs ~230mb /system (wont fit on stock hboots)
Changelog
Evervolv-Perdo-3.1.0p1-passion (10/17)
Merge android 4.1.2
fix trackball notifications
transparent lockscreen
some kernel changes to ondemand governor for better meshing with userspace powerhal
Enable vsync
Click to expand...
Click to collapse
Evervolv-Perdo-3.0.0p6-passion (10/05)
Bump JRO03R
Partialy working camcorder
Misc updates*
Click to expand...
Click to collapse
Evervolv-Perdo-3.0.0p5-passion (9/19)
fix 3g network discovery
a2dp: bluetooth audio (via tyler hall)
more dictionaries
launcher rotation
new kernel
update openssh, busybox
no more legacy camera, using gallery version now (preview has some issues)
new default wallpaper
a2sd supports new jb folder app-asec
fix capacitive button backlight with autobrightness
webgl in stock browser
ctr-screen off animation
Click to expand...
Click to collapse
Evervolv-Perdo-3.0.0p4-passion (8/10)
bump JRO03L
add more features: battery percent, powermenu screenshot, t-9 dialer, 6bar signal
update adreno libs
split long sms instead of convert to mms
experiments with power hal to extend battery life on standby
linaro bionic optimizations for a bit of speed
Camera should be able to take pictures
Click to expand...
Click to collapse
Evervolv-Perdo-3.0.0p3-passion (7/31)
Kernel update: data usage shows up in settings, add avs, switch to caf ondemand gov
Update Superuser
Port jumpytouch filter from ics (thanks thoemy) for better pinch to zoom
bump to JRO03H
HWA now working (no butter)
EVToolbox is back (trackball/volume wake, vol music control, ics lockscreen)
Click to expand...
Click to collapse
Evervolv-Perdo-3.0.0p2-passion (7/19)
I'm pretty tired and dont feel like rebuilding just to bump the version. So here is a p2 'nightly'. That was really only built to test a cron script. but should work just fine.
Fixes:
Wifi tether (used it all day today)
browser rendering
paid apps (untested)
googles apps on sd (untested)
Superuser
Click to expand...
Click to collapse
Evervolv-Perdo-3.0.0p2-passion (7/16)
Wifi signal. (switched to bcmdhd) (maybe broke wifi tether)
Apps2sd (cant format the partition, i forgot to add e2fsprogs to the build)
Sound. (probably)
Reboot menu
Usb mass storage
Trackball (no wake yet)
Click to expand...
Click to collapse
Evervolv-Perdo-3.0.0p1-passion (7/14)
Initial release
Click to expand...
Click to collapse
HOWTO: external gapps
Cautions:
-This is an alternative to flashing the gapps zip in recovery. Do not do this if you have flashed gapps through recovery
-For m2sd users see here
Gist:
Instead of wasting nand space installing 50+MB of gapps to /system we will place them on /sd-ext and create symlinks to /system. This means you can reduce the /system partition to 210MB safely and still have full gapps. In principle, after the initial setup this will survive wipes and updates (assuming you dont format /sd-ext).
The main reasoning is reading from the sdcard should be just as fast (or faster especially with journaling disabled which is now done automatically by the init mount script) than from nand. But random writes to the sdcard are going to me much slower than nand. So if we are only reading from the sdcard and writing all our data to nand it should be much faster.
getting the gapps in the right place
# via adb
Code:
# extract the gapps zip on you desktop
# create directory on device
$ adb shell mkdir -p /sd-ext/gapps/system
# push the system folder to device
$ adb push ~/Downloads/gapps/system /sd-ext/gapps/system
# make sure directories are right init script depends on this exact placement (mainly check we dont have gapps/system/system/)
$ adb shell ls /sd-ext/gapps/system
app etc framework lib usr
# enable extgapps (quotes needed)
$ adb shell "echo x > /sd-ext/gapps/.extgapps"
# gapps dir should look like this (if .extgapps doesnt exist the init script wont run)
$ adb shell ls -a /sd-ext/gapps/
.extgapps system
# reboot and wipe device
$ adb reboot bootloader
$ fastboot -w
$ fastboot reboot
# via root explorer (these are fairly rough)
Code:
-click on the gapps zip on sdcard to open
-long press the system folder -> extract -> 'go to extracted'
-long press the system folder (the extracted one) -> copy
-navigate to /sd-ext
-menu -> new folder -> name it 'gapps'
-open gapps -> paste (system folder)
-menu -> new file -> name it '.extgapps' the dot is required
# directories should now contain:
# /sd-ext/gapps should have: .extgapps, system
# /sd-ext/gapps/system should have: app, etc, framework, lib, usr
-reboot recovery -> wipe data
once its setup
# on reboot
Code:
# symlinks will be created on boot
# look at beginning of logcat to ensure links were created
$ adb logcat -C
.....
I/extgapps( 137): Removed Provision
I/extgapps( 139): Removed QuickSearchBox
I/extgapps( 145): Created /system/app/Talk.apk
I/extgapps( 148): Created /system/app/ChromeBookmarksSyncAdapter.apk
I/extgapps( 151): Created /system/app/GoogleBackupTransport.apk
I/extgapps( 154): Created /system/app/GoogleCalendarSyncAdapter.apk
I/extgapps( 157): Created /system/app/OneTimeInitializer.apk
.....
let me know how it works for you.
You will now never need to flash gapps again.
Nice work! i tested on my device and its running very nice.
Function Tests:
- boot without errors
- UI (HW) is very good (cool Animation ). Touch input slowly
- HSDPA / GSM works
- WLAN works verys good, but system show wlan connection very low.
- Android Browser has render problems (Google Chrome works fine)
- sound volume keys works with sound
- sound in media player works
- phone sound doesn't work
- gallary works nice
- widgets works with auto position
- m2sd script doesn't work (http://forum.xda-developers.com/showthread.php?t=1342387)
Google Apps:
- Google Play works fine
- Google Maps - multitouch is not useable
- Google Mail works fine
- Google Calendar works fine
- Google Contact works fine
- Google Talk works fine
Its a very stable alpha! THX
I might give this a shot in a bit. How are the ui and animations feeling? Are they noticeably smoother on Jelly Bean than ICS or does project butter not make a difference on the nexus one?
the ui and animation is very smooth. i love the animation between the switch of activitys...
only the touch events are slowly. if gapps works -> n1 with 4.1
Cannot wait to try this. Serious props!
Sent from my Nexus One using xda premium
Someone çan tell me which is thé Best hboot
Sent from my Nexus One using Tapatalk 2
xeloni said:
Someone çan tell me which is thé Best hboot
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
This will probably change as system will probably grows!? For this pre-release you can use the same as for TexasIce Cream Sandwich (220 for system partition).
edit: you should be fine with 210, too. That is the disk usage after installation:
Code:
1|[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 202M 32K 202M 4096
/mnt/asec 202M 0K 202M 4096
/mnt/obb 202M 0K 202M 4096
/system 220M 178M 41M 4096
/data 200M 56M 143M 4096
/cache 16M 1M 14M 4096
It's already smooth with the first prealpha. I can't wait the next prealpha's !
Good job and thanks
Sent from my Nexus One using xda app-developers app
For those who care: USB Mass Storage works with my "old" UMS App for ICS (v1.1.4). However, you need root to use it. So you have to flash Superuser-3.2-arm-signed.zip via recovery first.
------
Edit: Confirm that everything on the "what works"-list, works for me too (including mobile data). Only thing so far are some tiled graphic glitches noticed in browser and email:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What are the commands for flashing this via fastboot?
creebefu said:
What are the commands for flashing this via fastboot?
Click to expand...
Click to collapse
Make a NANDROID backup via recovery. Then boot into bootloader mode and from command line type:
Code:
fastboot -w
fastboot flash system /local/path/to/system.img
fastboot flash boot /local/path/to/boot.img
fastboot reboot
----
jelly easter beans
is the HBOOT the same as ics?
Yes
Sent from my Nexus One using Tapatalk 2
It's incredible the fastness of this release! It's a prealpha and it can operate faster with things than ics! e.g. recent apps, app drawer, etc
I can't thank texasice enough for your work and effort in ics and jb's stuff
Bexton said:
Make a NANDROID backup via recovery. Then boot into bootloader mode and from command line type:
fastboot flash boot /local/path/to/boot.img
Click to expand...
Click to collapse
What is the boot image?
creebefu said:
What is the boot image?
Click to expand...
Click to collapse
Download the tarball file on the OP and extract the images.
OMG I'm an idiot... thanks.
I know It may be early to ask, but here It goes:
DO you guys feel that "Project Butter" made difference for the N1? Is the Interface smoother than ICS for us? (I know reports indicate slow Touch input, but It may be just regarding touch Input really... I ask about the UI(transitions and Kinecting scrolling speed) in general...]
I really cn't test on my own, cause my N1 is my Daily Driver.

[KERNEL] 2.6.29.6-nAa-jb-03 [23/11/12] Custom JB kernel + CWM Recovery

Before unlocking your bootloader, read this thread
If you brick your device, you are the sole responsible.
Preface:
Read through this post. Don't rush into flashing. Be sure you understand the process before you start
This is a custom kernel developed for Android Jellybean
Do NOT try this kernel on other Android versions - you are totally unsupported
This kernel introduces custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Features:
Forked from nAa-ics-04 (all ICS features are already in there)
Built with linaro-4.7.1 toolchain
CWM-Based Recovery 5.5.0.4
Custom mtd partitioning scheme suitable for JB
Modular recovery flashing support (more on that to come...)
Tracing support for JB
pmem: bring up2date with CAF 2.6.38
genlock/kgsl fixes
Triple buffering support for msm framebuffer
Much more RAM for improved multitasking experience (shakira: 186MB, robyn/mimmi: 187MB)
FAQ:
If you have any issues, please read the FAQ thread first: http://forum.xda-developers.com/showthread.php?p=30297163
Requirements:
Unlocked bootloader --> http://forum.xda-developers.com/showthread.php?t=1254225
MiniCM10 or any JB, source-based ROM (install this kernel first, format /system, /data and /cache, then install the JB ROM)
Flashtool tested to be working with your phone, e.g. from here: http://www.multiupload.com/GYL7A7XQBT Original flashtool thread: http://forum.xda-developers.com/showthread.php?t=920746
Install:
Backup
Unlock your bootloader as described here: http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3 or here: http://forum.xda-developers.com/showthread.php?t=1254225
Download the kernel ftf file from here and move it to Flashtool\firmwares so that Flashtool can pick it up
Flash the kernel via Flashtool
Reboot and you should see the kernel boot animation
[*] (First time only) Get into recovery and format /system /cache and /data manually
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uninstall:
Flash back to stock using SEUS.
OR
[*] Format /system /data and /cache via CWM and THEN flash another kernel via Flashtool
Notes:
Dualtouch (for synaptics):
If you want to enable the fake DT by dx (instead of andrej456's which is the default), you have to insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_dt.ko
Click to expand...
Click to collapse
If you want to remove the fake DT altogether, insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_no_dt.ko
Click to expand...
Click to collapse
Sources:
The linux kernel is GPL'ed, everyone who does modifications should make them publicly available.
https://github.com/nobodyAtall/nAa-kernel-jb
Donate:
If you are enjoying my work please consider donating:
.
Donations are voluntary but allow me to spend more time on this project.​
Disclaimer:
I can't be held responsible if this Kernel bricks your device or makes it explode in your hands! Use it at your own risk!
​
Changelog:
### nAa-jb-02
* Ramdisk changes
* Increase vm_max_readahead to 1024Kb
### nAa-jb-01
* Forked from nAa-ics-04
* Tracing support for JB
* pmem: bring up2date with CAF 2.6.38
* genlock/kgsl fixes
* Triple buffering support for msm framebuffer
* Much more RAM
* Custom mtd partitioning for JB
MTD partitioning for Jellybean:
localhost / # cat /proc/mtd
dev: size erasesize name
mtd0: 10500000 00020000 "system"
mtd1: 00500000 00020000 "cache"
mtd2: 0bfc0000 00020000 "userdata"
mtd3: 00a00000 00020000 "recovery"
localhost / # df -h
...
/dev/block/mtdblock0 261.0M 238.1M 22.9M 91% /system
/dev/block/mtdblock2 191.8M 86.5M 105.3M 45% /data
/dev/block/mtdblock1 5.0M 780.0K 4.2M 15% /cache
...
reserved for FAQ
Read Before Asking Please
FAQ for MiniCM10 and nAa kernel
reading may answer to lots of your questions !
for X10mini, X8 & x10miniPRO
i decided to create a new thread dedicated to Q&A about miniCM10
so please, as usual, read FAQ, use search option or anything else before asking commonly answered questions
the FAQ will be incremented when needed
the Q&A is written as Q are asked
something else that is useful to read before asking :
Here we (nearly all? XDA members, regardless of being devs or only users [like me], me at least ) don't care about your good/bad English the important is trying to be understood and to understand the content of the threads
only ask things you can't find, or you don't understand, please if you don't understand something in any process tell us exactly where is your problem : it will optimize the answer
sometime rephrasing things can make you understand better, feel free to help us for making the most understandable sentence for anybody
BUT if you don't make the effort to read, I won't make the effort to answer (ok, you can't read everything... but read the minimum )
Chatroom for support is now available (http://minicm.ie.tc/)
clic on the red text above
register, and then enjoy ​________________________________
clic here for : FAQ
this post will be updated with the very last Questions added to FAQ about the ROM for quick view
________________________________
bug tracking template :
twins.7 said:
#BUG Report
DO
Reboot - Recovery
BUG
the screen stuck in rebooting dialog. It should just rebooting
ACTION
press home key (or any key maybe) to make it reboot
Click to expand...
Click to collapse
_________________________
useful links :
[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
$find other useful link in miniCM7/9 miniFAQs $
Perfomance :
recomended settings :
perf related :
CPU: keep default, but enable UnderVolting (and set on boot if you don't OverClock) (settings>performance>CPU)
RAM : to optimize RAM usage, use KSM, zram (18%, default) and allow purging of assets (settings>performance>memory managment)
I/O : keep NOOP, this is the default and the best for flash memory
other :
in settings>developer options
enable USB debugging,
debug notification,
set all animations to 0.5 (electron beam CRT animation will happen no more)
enable "kill with back button"
________________
for whose who feel the system slow and laggy, just try the SWAP (SDcard class6+ recommended)
SWAP, there is two "kind" of swap : using a partition on the SDcard, or using a swap file
both are good, but some SDcard/phones react better with the one or the other​
let us start with the partition way : it is more complicated than the file method, but as some advantages
pros: once it is set up, no need to care about it anymore, the SDcard can be mounted to PC easily without latency
cons: a little complicated to set up, and once it's done, it is as complicated to revert as to set up; to change swap size, you need to repeat the process (formating and partitioning SDcard)
needs a clean install of miniCM10:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size) any data on phone memory will be lost
set up your swap:
==> go to /advanced/Partition SD Card
if you don't want to use a2sd, then choose the minimal size for ext, and the size you want for SWAP
it will FORMAT your SDcard ! any data on SDcard will be LOST
and install the rom
swap partition should work
what doesn't work is the swap info menu
to revert : format SDcard in phone settings : it will FORMAT your SDcard ! any data on SDcard will be LOST​
____________________
now, the swap file way : it is really simpler than the swap partition, works great but has some drawbacks
pros: easy to set up, easy to revert, and the size can be choosen at wish at anytime (in settings>performance>memory>Swap settings)
cons: high latency when mounting SDcard to pc, it can take forever (really quicker to use CWM mount and storage capability to use the SD on the PC, than using android way)
you must perform a clean install of miniCM10 (by formating /system, /data and /cache) any data on phone memory will be lost
install the rom zip, the gapps, and boot up your phone
set it up
once your rom is ready to use,
go to settings>performance>memory>Swap settings
choose "enabled"
choose the size
allow system to get SU permissions
wait for the pop up "swap enabled"
enjoy, it is simple and can be disabled on wish​
to see if you swap works, open terminal, and type the following :
Code:
free
Sorry, are you some you forgetting where you are!!:silly:
This is a Development thread so treat it like one!
Take this as your warning, any further off spam posts and you will be infracted.
@nobodyAtall
Why there isnt 6.0.1.1 recovery in the kernel? Not possible or you tried and you got errors?
And second thing. Is possible to get 192 MB free in Gingerbread kernel?
whr is kernal?
monu09 said:
whr is kernal?
Click to expand...
Click to collapse
this is kener for CM10
Xmaster8 said:
@nobodyAtall
Why there isnt 6.0.1.1 recovery in the kernel? Not possible or you tried and you got errors?
And second thing. Is possible to get 192 MB free in Gingerbread kernel?
Click to expand...
Click to collapse
This kernel has modular recovery. This means that you will be able to flash any recovery you like without the need to flash another kernel. There's no need to change everything at the same time! Existing recovery is pretty stable.
And 192MB isn't possible for GB without breaking stuff.
I can't download the kernel...
Sent from my E15i using xda app-developers app
me too cant download
DJ_Mike_Jams said:
I can't download the kernel...
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
And neither the ROM
EDIT: Sorry, problem solved
now can download thank you NAa
will try this kernel and cm10
What happens if I use this on MiniCM 9 just curious
RohinZaraki said:
What happens if I use this on MiniCM 9 just curious
Click to expand...
Click to collapse
It's nAa ICS 4 with a new ramdisk and more features i guess, but it won't boot up due the new ramdisk (not sure about it).
Anyway it's working really fine.
Much more RAM for improved multitasking experience (shakira: 192MB, robyn/mimmi: 195MB)
LOL you are the BEST!!!!!!!!!
I have a problem with the kernel. When I reboot after flashing the kernel, the nAa logo appear, the LED turns purple and the phone reboots. What is the solution please ?
Try to flash phone with pccompanion or seus and flash naa jb kernel.
Neur0Nerd said:
I have a problem with the kernel. When I reboot after flashing the kernel, the nAa logo appear, the LED turns purple and the phone reboots. What is the solution please ?
Click to expand...
Click to collapse
I have same problem ;/

[KERNEL] nAa-jb-03 [23/11/12] Custom JB kernel + CWM Recovery

Before unlocking your bootloader, read this thread
If you brick your device, you are the sole responsible.
Preface:
Read through this post. Don't rush into flashing. Be sure you understand the process before you start
This is a custom kernel developed for Android Jellybean
Do NOT try this kernel on other Android versions - you are totally unsupported
This kernel introduces custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Features:
Forked from nAa-ics-04 (all ICS features are already in there)
Built with linaro-4.7.1 toolchain
CWM-Based Recovery 5.5.0.4
Custom mtd partitioning scheme suitable for JB
Modular recovery flashing support (more on that to come...)
Tracing support for JB
pmem: bring up2date with CAF 2.6.38
genlock/kgsl fixes
Triple buffering support for msm framebuffer
Much more RAM for improved multitasking experience (shakira: 186MB, robyn/mimmi: 187MB)
FAQ:
If you have any issues, please read the FAQ thread first: http://forum.xda-developers.com/showthread.php?p=30297163
Requirements:
Unlocked bootloader --> http://forum.xda-developers.com/showthread.php?t=1254225
MiniCM10 or any JB, source-based ROM (install this kernel first, format /system, /data and /cache, then install the JB ROM)
Flashtool tested to be working with your phone, e.g. from here: http://www.multiupload.com/GYL7A7XQBT Original flashtool thread: http://forum.xda-developers.com/showthread.php?t=920746
Install:
Backup
Unlock your bootloader as described here: http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3 or here: http://forum.xda-developers.com/showthread.php?t=1254225
[*]Download the kernel ftf file from here and move it to Flashtool\firmwares so that Flashtool can pick it up
Flash the kernel via Flashtool
Reboot and you should see the kernel boot animation
[*] (First time only) Get into recovery and format /system /cache and /data manually
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uninstall:
Flash back to stock using SEUS.
OR
[*] Format /system /data and /cache via CWM and THEN flash another kernel via Flashtool
Notes:
Dualtouch (for synaptics):
If you want to enable the fake DT by dx (instead of andrej456's which is the default), you have to insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_dt.ko
Click to expand...
Click to collapse
If you want to remove the fake DT altogether, insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_no_dt.ko
Click to expand...
Click to collapse
Sources:
The linux kernel is GPL'ed, everyone who does modifications should make them publicly available.
https://github.com/nobodyAtall/nAa-kernel-jb
Donate:
If you are enjoying my work please consider donating:
.
Donations are voluntary but allow me to spend more time on this project.​
Disclaimer:
I can't be held responsible if this Kernel bricks your device or makes it explode in your hands! Use it at your own risk!
​
Changelog:
### nAa-jb-02
* Ramdisk changes
* Increase vm_max_readahead to 1024Kb
### nAa-jb-01
* Forked from nAa-ics-04
* Tracing support for JB
* pmem: bring up2date with CAF 2.6.38
* genlock/kgsl fixes
* Triple buffering support for msm framebuffer
* Much more RAM
* Custom mtd partitioning for JB
MTD partitioning for Jellybean:
localhost / # cat /proc/mtd
dev: size erasesize name
mtd0: 10500000 00020000 "system"
mtd1: 00500000 00020000 "cache"
mtd2: 0bfc0000 00020000 "userdata"
mtd3: 00a00000 00020000 "recovery"
localhost / # df -h
...
/dev/block/mtdblock0 261.0M 238.1M 22.9M 91% /system
/dev/block/mtdblock2 191.8M 86.5M 105.3M 45% /data
/dev/block/mtdblock1 5.0M 780.0K 4.2M 15% /cache
...
useful links :
[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
$find other useful link in miniCM7/9 miniFAQs $
Perfomance :
recomended settings :
perf related :
CPU: keep default, but enable UnderVolting (and set on boot if you don't OverClock) (settings>performance>CPU)
RAM : to optimize RAM usage, use KSM, zram (18%, default) and allow purging of assets (settings>performance>memory managment)
I/O : keep NOOP, this is the default and the best for flash memory
other :
in settings>developer options
enable USB debugging,
debug notification,
set all animations to 0.5 (electron beam CRT animation will happen no more)
enable "kill with back button"
________________
for whose who feel the system slow and laggy, just try the SWAP (SDcard class6+ recommended)
SWAP, there is two "kind" of swap : using a partition on the SDcard, or using a swap file
both are good, but some SDcard/phones react better with the one or the other​
let us start with the partition way : it is more complicated than the file method, but as some advantages
pros: once it is set up, no need to care about it anymore, the SDcard can be mounted to PC easily without latency
cons: a little complicated to set up, and once it's done, it is as complicated to revert as to set up; to change swap size, you need to repeat the process (formating and partitioning SDcard)
needs a clean install of miniCM10:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size) any data on phone memory will be lost
set up your swap:
==> go to /advanced/Partition SD Card
if you don't want to use a2sd, then choose the minimal size for ext, and the size you want for SWAP
it will FORMAT your SDcard ! any data on SDcard will be LOST
and install the rom
swap partition should work
what doesn't work is the swap info menu
to revert : format SDcard in phone settings : it will FORMAT your SDcard ! any data on SDcard will be LOST​
____________________
now, the swap file way : it is really simpler than the swap partition, works great but has some drawbacks
pros: easy to set up, easy to revert, and the size can be choosen at wish at anytime (in settings>performance>memory>Swap settings)
cons: high latency when mounting SDcard to pc, it can take forever (really quicker to use CWM mount and storage capability to use the SD on the PC, than using android way)
you must perform a clean install of miniCM10 (by formating /system, /data and /cache) any data on phone memory will be lost
install the rom zip, the gapps, and boot up your phone
set it up
once your rom is ready to use,
go to settings>performance>memory>Swap settings
choose "enabled"
choose the size
allow system to get SU permissions
wait for the pop up "swap enabled"
enjoy, it is simple and can be disabled on wish​
to see if you swap works, open terminal, and type the following :
Code:
free
Thanks!!!!!!!!!!!!!!!!!!!!!!!!!!111
I have a problem trying to go from 2.3 to 4.1:
- i flash the new JB kernel
- restart the phone
- when is loading the "nAa" startup, exact when its on "freed" of "freedom" it freeze and reboot, i cant go into in cwm to flash the JB
if i reflash 2.3 kernel, it boot ok.
any has the same problem?
ty.
(my english suck, sry )
SOLVED: http://forum.xda-developers.com/showpost.php?p=30329524&postcount=16 , thanks he.
after i flashed kernel, the phone turns on but nothing happens. the boot logo doesnt show up. then i tried to flash the ics kernel, wich i used before, and its the same. repaired the phone with pc companion and tried again, same result. :-/ if im condemned to use stock kernel and rom, ill break the phone -.-
MiniCM10 on the way
Sent from my Nexus One using Tapatalk
This Guy can do Anything... nobodyAtall is genious.
First of all, thanks for your great work! :victory:
Then, just a question: i have already unlocked bootloader (in fact, i put MiniCM7-2.2.1 & nAa-13 Custom Gingerbread kernel - both by nAa - on my X10 Mini)...should i to repeat the process describe here? ---> http://forum.xda-developers.com/showthread.php?t=1254225 ?
If i don't understand badly, i have "only" to perform factory reset, wipe cache partition and wipe dalvik cache from recovery, isn't it? Then flash custom kernel & ROM. Like described there ---> http://forum.xda-developers.com/showpost.php?p=30329524&postcount=16
Thanks again
Greetings from Italy
sith.warrior said:
First of all, thanks for your great work! :victory:
Then, just a question: i have already unlocked bootloader (in fact, i put MiniCM7-2.2.1 & nAa-13 Custom Gingerbread kernel - both by nAa - on my X10 Mini)...should i to repeat the process describe here? ---> http://forum.xda-developers.com/showthread.php?t=1254225 ?
If i don't understand badly, i have "only" to perform factory reset, wipe cache partition and wipe dalvik cache from recovery, isn't it? Then flash custom kernel & ROM. Like described there ---> http://forum.xda-developers.com/showpost.php?p=30329524&postcount=16
Thanks again
Greetings from Italy
Click to expand...
Click to collapse
you don't have to relock or reunlock your bootloader, follow the instructions of format /system and others in cwm menu, and then flash the jb kernel. Happy testing
Hey nAa, the link you gave in the OP to download the kernel is the E10 kernel.
That's why many people complain that didn't work.
I downloaded the right kernel on minicm.googlecode.com
EDIT: This thread is right, on MiniCM10 for x10 mini pro Thread, you send people to this Kernel, instead the u20 kernel. that's the thing
first of all... i installed jb via recovery...then installed kernel and came upto home of launcher but the touchscreen is unresponsive...i mean the side buttons home keys etc. work fine but the touchscreen doesnt...help....
Password Protections
Hey nAa, is there anyway so we can password protect the clockworkmod recovery?? Just for security reasons (prevent someone from wiping the data partition)....
Hi,for x10 mini the kernel is E10 or u20?
mauwri37 said:
Hi,for x10 mini the kernel is E10 or u20?
Click to expand...
Click to collapse
Take off your back-cover, you will find a sticker with the model-number of your phone... Download the kernel corresponding to that number.
X10 Mini = E10 (i or a) = Robyn
X10 MiniPro = U20 (i or a) = Mimmi
how to access cwm in this kernel!!! help.... menu button? back button?? just a bootloap..
Flashed wrong kernel
Guys,
I know this will be a really noob question, but still... After spending some time reading this guide, I ended up dowloading X10 Mini (e10 or whatsoever kernel and I installed it to my u20 (X10 Mini Pro. Now FlashTool gives me error - flashing aborted messages every time I want to install the correct kernel.
Is there anything /i can do?
Thanks,
Regards
kog said:
Guys,
I know this will be a really noob question, but still... After spending some time reading this guide, I ended up dowloading X10 Mini (e10 or whatsoever kernel and I installed it to my u20 (X10 Mini Pro. Now FlashTool gives me error - flashing aborted messages every time I want to install the correct kernel.
Is there anything /i can do?
Thanks,
Regards
Click to expand...
Click to collapse
Yes, just flash the correct kernel and you should be fine.
nobodyAtall said:
Yes, just flash the correct kernel and you should be fine.
Click to expand...
Click to collapse
If didn't work, try use SEUS to put phone with default kernel and then try using u20i kernel. Loock for my post above you find it.

[Experimental]Resized Partition Discussion v2

Hello peeps
So I am opening this thread to discuss re-sizing of MTD partitions ...
I would like this discussion to be restricted to advanced users and devs only :angel: :cyclops:
Disclaimer : I don't give a damn if your device bricks ...Resized MTD blocks are recipe for disaster ...Phones can be bricked at will ...So proceed with caution...
I am using Xperia Mini Pro Sk17i
This my Current work so far !
Post 1: Features
Post 2artition Setup & sources
Post 3:Reserved
Partition Table
http://forum.xda-developers.com/showpost.php?p=45072234&postcount=37
I have attached the basic zImages for Mini-Pro,Mini & LWW ... repack them and use it at your own discretion ...
I have tested on Minipro
Features :
4.4.3 toolchain
Based on Stock .587
ext3/4 support and btrfs support
/data size increased from 430MB to 513MB
/cache reduced from 100MB to 8MB ...
To Do:
Fix JFS bug ...I like JFS file system ...btrfs is good but not as good as JFS
Hmm..dunno ...
Try to modify partition layout
Instructions :
Installation:(x=device code)
Unzip the Zimage_x.gz
Rename zImage_x to zImage
Pack the Zimage with Ramdisk ...
fastboot the boot.img ...
Format Data and Cache via recovery !
Deinstallation:
Flash any other kernel
Format Data and cache via recovery
FAQ:
1.)Device is not responsive :
Pray that you can boot to flash mode ...It could be hard brick for all I know
2.)The kernel is bootlooping
wipe data and cache
Credits:
CosmicDan:His tutorial on Partition Editing is Fantastic
@kast: For keeping Kappa Alive
Sony for sources ...
Download:
Alpha Boot.img for SK17i
http://www.mediafire.com/download/oofuw76cb0hv1li/Alpha_SK17i.7z
The rest of devices will get zImages since it's annoying to package for four devices for now for me///
Original Partition Setup of SK17i
Code:
Name ID ?? Type Offset Size Type [email protected] Size in MB
s1boot 01000000 22000000 00000000 01000000 unknown [email protected] 128KB
ta 02000000 01000000 08000000 08000000 unknown [email protected] 1MB
adsp 08000000 22000040 5C010000 6C000000 elf [email protected] 13MB
amss 05000000 22000040 10000000 E4000000 elf [email protected] 29Mb
amss_fs 06000000 01000040 F4000000 68000000 unknown [email protected] 13MB
fota0 0B000000 22000040 C8010000 5C000000 elf [email protected] 11.7MB
fota1 0C000000 22000040 24020000 5C000000 elf [email protected] 11.7Mb
boot 03000000 22000080 80020000 64000000 elf [email protected] 12.8MB
system 04000000 01000080 F4020000 800C0000 yaffs [email protected] 409MB
data 09000000 01000080 D0120000 200D0000 yaffs [email protected] 430MB
cache 0F000000 01000080 A40F0000 2C030000 yaffs [email protected] 103MB
appslog 10000000 01000080 740F0000 30000000 yaffs [email protected] 6MB
This is how nand is laid out
S1Boot--Unknown--TA--AMSS-AMSS_FS--ADSP--fota0-fota1--boot-Unknown--system--appslog--cache--data--Unknown
Click to expand...
Click to collapse
Current edits I made :
/cache
Click to expand...
Click to collapse
Code:
[email protected]
to
Code:
[email protected]
/data
Click to expand...
Click to collapse
Code:
[email protected]
to
Code:
[email protected]
Problems : the 6MB appslog partition is playing spoilsport ...I can seem to boot kernels if I change the offset of appslog :/
Fixed
Sources :
Nothing much to boast about ...
Grab the Sony Stock Sources
Open the defconfig of your device
Search for
Code:
CONFIG_CMDLINE="console=ttyMSM2,115200n8 androidboot.hardware=semc"
And change to
Code:
CONFIG_CMDLINE="console=ttyMSM2,115200n8 androidboot.hardware=semc mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache)"
CONFIG_MTD_CMDLINE_PARTS=y
Enable ext4 ,JBD,JBD2 abd btrfs ...
Compile the kernel and you get the current zImage
Logs:
Code:
df
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 173728 76 173652 0% /dev
tmpfs 173728 0 173728 0% /mnt/asec
tmpfs 173728 0 173728 0% /mnt/obb
/dev/block/mtdblock0 409600 312092 97508 76% /system
[B]/dev/block/mtdblock1 525824 90276 435548 17% /data
/dev/block/mtdblock2 8192 1200 6992 15% /cache[/B]
Screenie
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reserved #2
Nice will test right now!! :good::good::good::good:
Aneel said:
Nice will test right now!! :good::good::good::good:
Click to expand...
Click to collapse
lol ..Good luck and post the results ...Remember it's experimental and WIFi doesn't work
So does this mean more ram less cache?
yash296 said:
So does this mean more ram less cache?
Click to expand...
Click to collapse
This means more /data and less /cache ... :/ ...It's MTD partitioning resizing ....which is resizing the NAND ROM and has no relation to RAM :/ ...
Roughly 85MB of /cache is now usable in /data ...
I think We should resize system partition
Making data partition larger doesnt make sense eh?
Sent from my WT19i using xda app-developers app
There is a 6MB barrier between system and data...known as appslog
I would actually like a smaller system ...but the kernel doesn't boot ...
I like larger /data
karandpr said:
There is a 6MB barrier between system and data...known as appslog
I would actually like a smaller system ...but the kernel doesn't boot ...
I like larger /data
Click to expand...
Click to collapse
yeah
that is exactly right
ROM's size can be reduced to be fit in /system
but users always use more and more data
Is there any chance to get recovery partition ?
Jawor245 said:
Is there any chance to get recovery partition ?
Click to expand...
Click to collapse
Yes and no ...I might resize system to allocate some space for recovery ,It "might" boot ...But I wouldn't be able to boot from the recovery Partition due to bootloader booting only from boot partition ....
karandpr said:
Yes and no ...I might resize system to allocate some space for recovery ,It "might" boot ...But I wouldn't be able to boot from the recovery Partition due to bootloader booting only from boot partition ....
Click to expand...
Click to collapse
Hi i'm very intersting by enlarging our /data by reducing /cache to 2Mo max and by reducing /system to 300 Mo max but I have some questions ...
How to use ramdisk with a particular kernel ?
Could we do without appslog in reformating all the nand ?
zegoo said:
Hi i'm very intersting by enlarging our /data by reducing /cache to 2Mo max and by reducing /system to 300 Mo max but I have some questions ...
How to use ramdisk with a particular kernel ?
Could we do without appslog in reformating all the nand ?
Click to expand...
Click to collapse
Just Google unpack/repack boot.img ...
You can use Android Kitchen or Champion swimmer's script ...
https://github.com/championswimmer/kernel-tools
Grab any kernel ,Unpack boot.img ,Replace the zImage with the zImage attached ,pack boot.img ...
I would personally like to nuke appslog but that partition is "allegedly" read only ...
Kernels with modified appslog doesn't boot.
See my signature for the guide..
Sent from my WT19i using xda app-developers app
Thanks for all guys. I will try all of that.
About appslog, i don't understand why some models of Sony Ericsson allows us to modify nand partition and why not SK17i for example. I thought bootloader was "bypassed" with a particular kernel and i thought it was just the kernel which determines nand's partition, so what ? It should possible to rewrite/reformat/repartitionnate completely the NAND?
Where are located the specifications about allocation in the NAND ? In the kernel or not ?
Hum, excuse for my bad english ...
zegoo said:
Thanks for all guys. I will try all of that.
About appslog, i don't understand why some models of Sony Ericsson allows us to modify nand partition and why not SK17i for example. I thought bootloader was "bypassed" with a particular kernel and i thought it was just the kernel which determines nand's partition, so what ? It should possible to rewrite/reformat/repartitionnate completely the NAND?
Where are located the specifications about allocation in the NAND ? In the kernel or not ?
Hum, excuse for my bad english ...
Click to expand...
Click to collapse
Bootloader can't be bypasses ...Since bootloader instructs the device to boot using kernel ...You cant actually repartition a nand with a kernel ...you can just reallocate the space ...Mostly even unlocked bootloaders are partially locked ...You can just access/modify boot/system/userdata/cache but cant access modify anything else...On positive note ,it's good since it makes SEMC devices very hard to brick ...
Boot.img("kernel") for Mini Pro ...
The stuff I use
WiFi supposedly works...
http://www.mediafire.com/download/oofuw76cb0hv1li/Alpha_SK17i.7z
Remember :
1.)Wipe data/cache AFTER flashing kernel ....
2.)Wipe data/cache AFTER flashing another kernel ....
DO NOT USE NANDROID RESTORE....It might theoretically brick device ...I am not going to verify it practically ...If you want to do it ,please do and post the results ...
Sometimes device bootloops for lulz ...laugh with device...but then it's an Alpha build ....
IF after flashing another kernel ,device doesn't boot then
A)Re-Flash ROM
B)if still kernel bootloops ,then Flash Stock FTF ...
I tried your kernel and it doesn't work. Bootloop !
I think problem is about the kernel himself with my own rom. I'm using a stable 2.3.4 ROM with the KrSh 2 ghz kernel version (6060K).
When i flashed your own kernel, i made wipes of data and cache and after i installed my zip ROM and got bootloops.
Maybe my own kernel modified (partitions) could work but i don't understand how to pack my kernel, modifying the config.properties (Where is it ?) and how to repack it ...
It's an ICS kernel ...
Based on STock .587 ...
Needs ICS bootloader and ROM ...
Config properties are needed if you want to compile the kernel ...
I think GB and ICS are partitioned slightly different and I would advise you to make a partition setup just in case

Moving dalvik-cache from /data to free up some space

Hi guys !
I wanted to share some thoughts on more efficient dalvik-cache placement.
There are two paths we can take here:
- move some or all of dalvik-cache to /cache partition,
- increase size of cache partition using other, unused parts of or flash.
I'll write all the stuff in order from the easiest to most complicated.
1A. Moving some dex files to /cache
Open your /system/build.prop and make sure that parameter dalvik.vm.dexopt-data-only is set to zero - either change it or explicitly set it, if is not there. This will cause dex files for all apks from /system partition to go to /cache - for Vanir it's about 65M. Good start
In theory you could move an apk from /data/app to /system/app and after reboot the dex file would move to /cache, but this creates two kinds of problems:
- after an update the app is on /data again and the dex file also,
- if you flash another rom, you'll most likely loose those apps, which isn't always desired, but this has a solution I'll give later.
1B. Moving entire dalvik-cache to /cache partition
If your dalvik-cache is smaller than /cache partition you might as well move it there entirely. There are few ways to do it, I'll show one of them.
Copy /fstab.samsungjanice somewhere (like /data/local/tmp/) and append (at the end!) the following line
Code:
/cache/dalvik-cache /data/dalvik-cache none bind defaults
Reboot into recovery and ensure that /data and /cache are mounted. Connect with adb and then run those:
Code:
mkdir -p /cache/dalvik-cache
chown system.system /cache/dalvik-cache
chmod 771 /cache/dalvik-cache
cp -a /data/dalvik-cache/* /cache/dalvik-cache
rm -f /data/dalvik-cache/*
Now move the modified fstab.samsungjanice to /efs/common/overlay/fstab.samsungjanice and reboot.
If everything went fine, you've just earned up to 300M more on /data
BEWARE that those two solutions are exclusive - either one, or the other. I don't know what happens if you use both - either nothing or it won't boot. You can of course switch between them - just don't enable both at the same time.
But... what if 300M is not enough? Then you can either stay with solution 1A or:
2. Enlarge /cache partition
Since preload, fota and kernel2 partitions aren't used (usually), we can extend /cache with them. This can be achieved either with repartitioning the flash or using lvm. I suggest the latter.
[MOD][EMMC][I9070/P][8/16GB] Internal Memory Repartition
Converting Cache and Preload to LVM
This way you can have over 600M of /cache, and if you throw in fota and kernel2, even around 670M.
Having done that you can use either 1A or 1B depending on what you want. If you don't intend to switch to ART, you can safely assume 600M is more than enough - use 1B. If however you want to give ART a try, I suggest trying 1A first - after switch to ART /cache usage increased from 65M to 195M and total dalvik-cache size went from 285M to 780M!!!
That's it for now - I'll extend this tut later.
Now the homework I gave you the ideas, now if someone could create recovery scripts that do this automatically, many more people could use them Any volunteers? It's not difficult - of course I'll help (as in check them and do minor corrections, not as in doing it all). If nobody does it, I'll probably do it... eventually... I'm kind of lazy ;P
I'm thinking about creating a repository of scripts/plugins for mk kernel on github - those will be a good addition.
Now tell me how many people are interested in using this - hit 'thanks' on this post since that's the easiest - by all means DON'T write posts "I'm interested" etc
@ChronoMonochrome, @ace2nutzer - it might be useful on codina as well.
P.S.
ART is awesome (using with my Vanir build which I'll make available soon)!!! Now Janice is even faster ;D
Just an add on/ info / guide if someone wants to use RE-PARTITION FLASH DRIVE by @AntaresOne
[MOD][EMMC][I9070/P][8/16GB] Internal Memory Repartition
And
@mkaluza
i really want to move devik from /data to another partition but i'm still using stock based rom so lvm method won't work for me and i still didn't thoroughly understand re-partition method from above.
but your opt 1B. seem to interesting to me so i'm goona try it now and let you know the results
btw is there any way to move delvik to /preload ? ( the stock base rom i'm using SamiOS more precisely don't use /preload partition so that 300MB is free so is there any way to use this instead of /cache ? )
jineshpatel30 said:
Just an add on/ info / guide if someone wants to use RE-PARTITION FLASH DRIVE by @AntaresOne
[MOD][EMMC][I9070/P][8/16GB] Internal Memory Repartition
Click to expand...
Click to collapse
Yes, thank you (did I say I'm lazy...?)
i really want to move devik from /data to another partition but i'm still using stock based rom so lvm method won't work for me and i still didn't thoroughly understand re-partition method from above.
Click to expand...
Click to collapse
Yes it will. The only real requirements are to have free /preload partition (so JB is ok, just don't use Samsung crap) and have a kernel that supports lvm. Using my kernel and overlay system it's only easier, but it is not required.
but your opt 1B. seem to interesting to me so i'm goona try it now and let you know the results
Click to expand...
Click to collapse
Ok, just remember that overlays work with my kernel only (this /efs/... stuff is overlay). (I'll soon make better stock ramdisk recovery zip)
btw is there any way to move delvik to /preload ? ( the stock base rom i'm using SamiOS more precisely don't use /preload partition so that 300MB is free so is there any way to use this instead of /cache ? )
Click to expand...
Click to collapse
Yes - just replace /cache with /preload in the fstab line there's no (straightforward) way to do it with 1A.
mkaluza said:
1B. Moving entire dalvik-cache to /cache partition
If your dalvik-cache is smaller than /cache partition you might as well move it there entirely. There are few ways to do it, I'll show one of them.
Copy /fstab.samsungjanice somewhere (like /data/local/tmp/) and append (at the end!) the following line
Code:
/cache/dalvik-cache /data/dalvik-cache none bind defaults
Reboot into recovery and ensure that /data and /cache are mounted. Connect with adb and then run those:
Code:
mkdir -p /cache/dalvik-cache
chown system.system /cache/dalvik-cache
chmod 771 /cache/dalvik-cache
cp -a /data/dalvik-cache/* /cache/dalvik-cache
rm -f /data/dalvik-cache/*
Now move the modified fstab.samsungjanice to /efs/common/overlay/fstab.samsungjanice and reboot.
If everything went fine, you've just earned up to 300M more on /data
Click to expand...
Click to collapse
well it's not working atleast for me
ROM : SamiOS 1.3.1
kernel CoCore 8.2
did everything as you said
put fstab.samsungjanice to /efs/common/overlay/fstab.samsungjanice ( with 777 and system as owner , PS : also tried with root as owner )
but every time i reboots after all this procedure it generates dakvik in /data/dalvik-cache again via optimizing apps 1 of xxx.
anyway as of know i removed common folder from /efs ( which was there before ) and wiped /cache & /dalvik-cache via recovery ...i'm hopping it these reverted all the changes i have may by those commands ...right ?
...................................................................................................................................................
Edit : @mkaluza
sorry i didn't know that 1B. works with your kernel only
i'm not using your kernel on stock ROMs bcz i get tearing on some apps while rotating screen and also it take much time to load some games like COC and stuck on loading screen with black screen.
also it's much brigher with auto brightness on stock roms.
some of these things were fixes by polishvodka in his version of your kernel for JB but he didn't posted any sources so we don't know what changes he made
so if there will be some fixes for these things in future i'll give it try again & check 1B. also
PS: you can contact me if you want to fix these things and make bug free kernel for stock roms..and need beta tester ...i'll be happy to help
I like that scripts/plugins repo idea.
And wow, ART takes a lot of space, I never knew that
Never try ART before, so I'm just gonna wait for your Vanir build so I can try it
mkaluza said:
Now tell me how many people are interested in using this - hit 'thanks' on this post since that's the easiest - by all means DON'T write posts "I'm interested" etc
@ChronoMonochrome, @ace2nutzer - it might be useful on codina as well.
Click to expand...
Click to collapse
Hmm, I read everything above wholly, and didn't understand, why we can't accomplish this goal just by repartition. Default partition where dalvik cache is stored is data, so why just don't decrease another partitions in order to increase /data ? That way we already can achieve upto ~3.1Gb space on data(furthermore, /system size can be increased as well). As for automatized scripts, take look at this thread http://forum.xda-developers.com/galaxy-ace/ace-2-develop/guide-cwm-reparted-t2895673 . Decreasing /sdcard size is optional however, even without this there are a lot space on /data because of decreasing /cache and preload partitions.
ChronoMonochrome said:
Hmm, I read everything above wholly, and didn't understand, why we can't accomplish this goal just by repartition. Default partition where dalvik cache is stored is data, so why just don't decrease another partitions in order to increase /data ? That way we already can achieve upto ~3.1Gb space on data(furthermore, /system size can be increased as well). As for automatized scripts, take look at this thread http://forum.xda-developers.com/galaxy-ace/ace-2-develop/guide-cwm-reparted-t2895673 . Decreasing /sdcard size is optional however, even without this there are a lot space on /data because of decreasing /cache and preload partitions.
Click to expand...
Click to collapse
Because repartitioning is quite "invasive". Besides using lvm has imho more educational value I'll look at the thread you link tomorrow.
Sent from my GT-I9070 using XDA Free mobile app
nss357 said:
I like that scripts/plugins repo idea.
Click to expand...
Click to collapse
GitHub repo
So far only ramdisk images, but I'll slowly add stuff...
And wow, ART takes a lot of space, I never knew that
Never try ART before, so I'm just gonna wait for your Vanir build so I can try it
Click to expand...
Click to collapse
Yeah, it's huge... But it's fast as well I've decided to try it after briefly using hasta's lollipop - while it's far from being usable for me, it was fast (although there's a very aggressive governor set as well). And i don't regret it - in fact with Art running I don't even care much about lollipop anymore - I like my KitKatVanir very much
I'll upload it soon - still need to work on few details.
ChronoMonochrome said:
Hmm, I read everything above wholly, and didn't understand, why we can't accomplish this goal just by repartition. Default partition where dalvik cache is stored is data, so why just don't decrease another partitions in order to increase /data ? That way we already can achieve upto ~3.1Gb space on data(furthermore, /system size can be increased as well). As for automatized scripts, take look at this thread http://forum.xda-developers.com/galaxy-ace/ace-2-develop/guide-cwm-reparted-t2895673 . Decreasing /sdcard size is optional however, even without this there are a lot space on /data because of decreasing /cache and preload partitions.
Click to expand...
Click to collapse
mkaluza said:
Because repartitioning is quite "invasive". Besides using lvm has imho more educational value I'll look at the thread you link tomorrow.
Sent from my GT-I9070 using XDA Free mobile app
Click to expand...
Click to collapse
Here is script for SGSA/i9070 to Re-Partition , modded by me from ChronoMonochrome's Script
Must Read this post before using this script
Download : SGSA i9070 Repartition 2.5GB Data 8MB Cache 5MB Preload
it'll murge /cache & /hidden (preload) partition to /data
so you will get 2.5 GB in /data
8MB in /cache
5MB in /preload
( if you are changing values for self use DON'T FURTHER DECREASE /CACHE & /PRELOAD SIZE otherwise u won't able to format it via recovery ( even though AntaresOne suggested min 128kb for /preload it won't let you format /preload via cwm so min 5mb require for that)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cradits:
Concept&Research by @AntaresOne
Script by @ChronoMonochrome
Moded for SGSA by Me
mkaluza said:
Because repartitioning is quite "invasive". Besides using lvm has imho more educational value I'll look at the thread you link tomorrow.
Sent from my GT-I9070 using XDA Free mobile app
Click to expand...
Click to collapse
yeah, I know what you mean. It's quite straight-line but what importantly, practical way. I tried to implement lwm feature being guided your wiki on github but caught myself thinking that I'm too lazy for that and decided to stick with repartition
ChronoMonochrome said:
yeah, I know what you mean. It's quite straight-line but what importantly, practical way. I tried to implement lwm feature being guided your wiki on github but caught myself thinking that I'm too lazy for that and decided to stick with repartition
Click to expand...
Click to collapse
i second that... actually i never properly understand what Antras's guide is suggesting to do, due to my lack of knowledge of adb and only one example in guide.
but after checking your script i thought logically this is straightforward and i can remove UMS and add all things to DATA as i wanted. so i checked my partition sizes as per Antras's guide and changed some values and on second trial i get all right (on 1st trail i got /preload not formatting due to very less size )
also did you checked my modification in scripts ? is it good ? or some cautions/addition needed ?
@mkaluza with all due respect , even though LVM method is much safer than Re-partitioning i think Re-partition script is easier to use if one knows what to do. plus it doesn't require kernel support.
btw it's always better to have alternatives so your work on LVM is much appreciated
jineshpatel30 said:
@mkaluza with all due respect , even though LVM method is much safer than Re-partitioning i think Re-partition script is easier to use if one knows what to do. plus it doesn't require kernel support.
btw it's always better to have alternatives so your work on LVM is much appreciated
Click to expand...
Click to collapse
I write those things in case someone was interested... my little wierdness ;P repartitioning is stone age (in terms of current state of knowledge) - lvm is much more flexible when one knows how to use it (like you can create new partitions on-the-fly i.e. to test f2fs or sth), while repartitioning is kind of a major surgery
But in no way I want to force them upon you Use whatever works for you I'll also prepare a cwm flashable version of lvm at some point probably...
jineshpatel30 said:
also did you checked my modification in scripts ? is it good ? or some cautions/addition needed ?
Click to expand...
Click to collapse
I haven't noticed big difference between original variant and this. Did you something besides of change of partition sizes? Btw, it is odd that you can't format preload partition, when it's too small (I've used script that resizes it to ~60kb, and it is still formattable, at least via shell script).
ChronoMonochrome said:
I haven't noticed big difference between original variant and this. Did you something besides of change of partition sizes? Btw, it is odd that you can't format preload partition, when it's too small (I've used script that resizes it to ~60kb, and it is still formattable, at least via shell script).
Click to expand...
Click to collapse
well i removed UMS part from your script as my janice is 16GB one so i don't need extra space there
and changed values according to Janice partitions.
that's pretty much
anyway when i set /preload for 128KB i got this message in recovery on formatting it
Code:
/preload
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
jineshpatel30 said:
well i removed UMS part from your script as my janice is 16GB one so i don't need extra space there
and changed values according to Janice partitions.
that's pretty much
anyway when i set /preload for 128KB i got this message in recovery on formatting it
Code:
/preload
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
Click to expand...
Click to collapse
If you don't need preload for anything then it doesn't need to be formatted... You're fine the way you are now. But remember you can't remove it completely because them partition numbers would change.
jineshpatel30 said:
Here is script for SGSA/i9070 to Re-Partition , modded by me from ChronoMonochrome's Script
Must Read this post before using this script
Download : SGSA i9070 Repartition 2.5GB Data 8MB Cache 5MB Preload
it'll murge /cache & /hidden (preload) partition to /data
so you will get 2.5 GB in /data
8MB in /cache
5MB in /preload
( if you are changing values for self use DON'T FURTHER DECREASE /CACHE & /PRELOAD SIZE otherwise u won't able to format it via recovery ( even though AntaresOne suggested min 128kb for /preload it won't let you format /preload via cwm so min 5mb require for that)
Click to expand...
Click to collapse
@jineshpatel30 @ChronoMonochrome
I'd like to have a variant of this script with 3,5GB of data , a system partition of 1GB and the rest to reduce sdcard (UMS) size for S Advance. Can you help me to edit this script? Unfortunately I didn't understand AntaresOne guide to edit it on my own.
My partition is this:
https://s18.postimg.org/b863m8lnd/Screenshot_2017-06-01-16-10-09.png
I know there is a safer solution like Repit, but it requires a TWRP kernel while I have a CWM kernel and I want to avoid the hassle to change rom or kernel (I''m using a vanir 4.4.4 with cwm recovery).
isaak said:
@jineshpatel30 @ChronoMonochrome
I'd like to have a variant of this script with 3,5GB of data , a system partition of 1GB and the rest to reduce sdcard (UMS) size for S Advance. Can you help me to edit this script? Unfortunately I didn't understand AntaresOne guide to edit it on my own.
My partition situation is this:
https://s18.postimg.org/b863m8lnd/Screenshot_2017-06-01-16-10-09.png
I know there is a safer solution like Repit, but it requires a TWRP kernel while I have a CWM kernel and I want to avoid the hassle to change rom or kernel (I''m using a vanir 4.4.4 with cwm recovery).
Click to expand...
Click to collapse
Sorry but i been away from SGSA for long time now (2+ years) and i don't even remember how i managed this script at 1st place so i'm afraid i can't help you with the script, as i don't have device and patience now
you may ask some of active experience members at i9070 they might able to help you :good:
isaak said:
@jineshpatel30 @ChronoMonochrome
I'd like to have a variant of this script with 3,5GB of data , a system partition of 1GB and the rest to reduce sdcard (UMS) size for S Advance. Can you help me to edit this script? Unfortunately I didn't understand AntaresOne guide to edit it on my own.
My partition is this:
https://s18.postimg.org/b863m8lnd/Screenshot_2017-06-01-16-10-09.png
I know there is a safer solution like Repit, but it requires a TWRP kernel while I have a CWM kernel and I want to avoid the hassle to change rom or kernel (I''m using a vanir 4.4.4 with cwm recovery).
Click to expand...
Click to collapse
Why TWRP is a requirement for the Repit, is there some tehnical dependence on TWRP (like /cache partition being unable unmount on CWM)? Anyway can't you flash TWRP kernel just to flash this zip, then flash your currently used kernel back?
I'd be keeping away from using command line instructions without fully understanding how it works. You can also check CWM reparted topic on codina forum, there are some internal memory layouts available (that can be theoretically be flashed on janice), though you need to thoroughly check whether the partition numbers used are matching with janice (I'd suggest anyway being cautious with it - check twice, cut once).
ChronoMonochrome said:
Why TWRP is a requirement for the Repit, is there some tehnical dependence on TWRP (like /cache partition being unable unmount on CWM)? Anyway can't you flash TWRP kernel just to flash this zip, then flash your currently used kernel back?
I'd be keeping away from using command line instructions without fully understanding how it works. You can also check CWM reparted topic on codina forum, there are some internal memory layouts available (that can be theoretically be flashed on janice), though you need to thoroughly check whether the partition numbers used are matching with janice (I'd suggest anyway being cautious with it - check twice, cut once).
Click to expand...
Click to collapse
After many attempts I solved using a TWRP kernel and flashing Repit zip with this name:
lanchon-repit-20160317-system=1.0-data=3.1-cache=same-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
The result of this command is in the attachment below.
But, if want more data space, you can try something like this:
lanchon-repit-20160317-system=1.0-data=4.1-cache=same-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
With this command, the additional data space would be taken directly from UMS (internal sdcard). Not from cache because it has the "same" parameter.
**If you don't know what is REPIT**
Read REPIT manual before using:
https://github.com/Lanchon/REPIT
Main topic support:
https://forum.xda-developers.com/galaxy-s-advance/development/flashable-emmc-repartition-t3369278
REPIT download (all versions):
https://androidfilehost.com/?w=files&flid=49911
Don't try it with stock Samsung ROMs. Only for custom ROMs. Make a backup first (including internal sdcard)!

Categories

Resources