Turbo Kernel Original Thread
{
"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"
}
Gingerbread support is experimental. Whatever the bug is, don't say it - I already know. I will fix them all when I can.
Full feature list:
Early roots in KRsH 2.6.32.9/4.1.C.0.7 kernel. Has changed drastically since first release; additional changes from CosmicDan, FXP and Irii. Stock-based kernel with manual changes/updates for AOSP and JB support - reported my many to have better batterey life and reliability than FXP-based kernels. Also built with Linaro toolchain and uses some Linaro-optimized memory functions.
Supports GB, ICS and JB ROM's. Configurable via the "Slot Mode" in the specific slot for the Boot Menu (see next point). AOSP-GB ROM's (e.g. CM7) are not supported.
Turbo Boot Menu. Entered by pressing vol-down (acts as a pre-recovery menu). Supports four slots for installing ROM's into - Slots 2-4 are stored on ext2 "image" files inside the /sdcard/turbo/ folder. Powered by the brilliant Aroma Installer GUI by Amarullz - any slot can be changed to your default boot, and each slot's icon and text can be customized
Tweaks and Mods selection for each slot:
- TSDX - CosmicDan's set-and-forget sd-ext script. Ability to share apps between each slot. Can also be uninstalled if desired (for one slot or for all - fully wizard-driven install/uninstall interface).
- Restore random entropy device - By default, Turbo kernel replaces the /dev/random entropy device with urandom. No need for a seeder - in fact an entropy seeder will do absolutely nothing in this kernel, just sit there feeding entropy to the same device. This option can be toggled to set the default device back to random.
- Deasec v2 - When enabled, this slot will decrypt "asec" apps on startup. Helps a lot with App2SD/Link2SD users. Original concept by Giovanni Aneloni, rewritten by CosmicDan.
- Change USB to ### - This option can toggle this slot to force UMS (Mass Storage) or MTP (Media Transfer) mode for USB connections. Please note that some ROM's, e.g. latest CM10 and KXP-JB, have completely disabled UMS in the ROM. Nothing I can do about that.
- Disable ALS - Enable or Disable the ambient light sensor for this ROM. If a ROM has a "disable ALS tweak" built it, this option will not do anything.
- Logging Mode - Change the Logging mode from the default to either Disabled or Extended. Disabled can increase performance (but logcat will be unavailable), extended can help with developers. See the option itself in tweak menu for more details.
Repair Functions. Inside the Boot Menu > Settings and Tools, the repair function will attempt to fix errors on SDCard and Slot2-4 images, and fix permissions. Default full repair and Advanced selection modes possible.
TeamWin Recovery Project. Can also be switched to/from CWM-Recovery in the Boot Menu > Settings and Tools menu. TWRP is recommended though as it's much more advanced and user-friendly. Contains additional fixes thanks to championswimmer, a theme and UI design by myself, plus the "Factory Reset" option will *not* touch the sd-ext partition.
Increased RAM capacity (select devices). zeus and phonex (Play/Neo L) have 379MB of RAM total (on 480p). 720p recording is removed since it is buggy in Jellybean (gives a good chunk of more RAM), and also some of CosmicDan's kernel tuning to squeeze a bit more (smaller kernel footprint = more RAM for Android). Do not ask for a 720p recording version, it will never happen - use a different kernel if you want it. - use 720p kernel at your own risk
Expanded /system and /data partition. 400 MB of space on system (because JB ROM is getting bigger and bigger. :fingers-crossed: )and 500MB+ of space on userdata.
Automatic wifi-module. There is no ZIP install required for Wifi module, the kernel init can detect automatically if the wifi module(s) need to be installed. They are located on the RAMDisk (at {root}/modules) and the kernel simply makes a symlink to the .ko files on boot if it needs to (linking is better than copying them).
Snappy zRAM compression. I personally don't use zRAM at all because it slows things down (still ain't snappy enough, heh), but "Snappy" zRAM compression by Google is apparently a lot faster than the traditional LZO compression and only a tiny bit worse compression ratio.
CPU governors - Intellidemand (default, has my own enhancements for our single-core Snapdragon CPU's - including CPU ramping on touch events ported from "Project Butter"), Lagfree, SmartAssV2, Performance and OnDemand. No, I will not add more governors. More governors = more RAM used by kernel = less RAM for Android.
I/O schedulers - SIO (default), deadline and noop. No, I will not add more schedulers. More schedulers = more RAM used by kernel = less RAM for Android.
CIFS, TUN/TAP and FUSE support built-in. No modules required.
...did I miss anything? Don't think so.
FAQ/Bugs:
Q) When I select "Reboot > Recovery" in my ROM, it boots recovery but there are strange errors!
A) Yes, this will boot recovery but it won't know which slot to use. I can't fix this sorry, so simply don't use it (just use Vol-Down on normal reboot).
Q) My device keeps going into the Boot Menu, even though I never pressed the key to enter!
A) This is a bootloader thing and is rare, to fix it just enter Recovery (for any slot) and select reboot from there.
Q) Camera does not work in my Stock GB or Stock ICS based ROM!
A) Known issue. I *may* be able to fix camera in Stock ICS ROM's later, but Gingerbread will probably never happen.
Q) I get an FC when trying to record video!
A) On 480p version make sure you select 480p for the quality in camcorder settings. Recording only works on ICS-AOSP and JB ROM's with no 720p.
Q) My ROM in slot 2/3/4 is bootlooping, or I'm getting FC's all the time!
A) Your microSD has become corrupted, probably due to a battery pull or an unclean shutdown - and so the Slot images have also been corrupted. Chose the Tools > Repair function in Boot Menu to try and solve it. If not, I'm afraid you'll have to *delete* that slot (a format will not do) and re-create the images. (Note to ROM dev's - best to use Slot 1 for testing/working, since this is the safe slot for battery pulls/adb reboot command).
Q) I have a problem with my ROM - I flashed Turbo Kernel and restored my backup with Nandroid.
A) This is not possible. If you have a Nandroid/TWRP backup from another ROM, it cannot be restored with this kernel. This is because of the custom partitions. The same goes for restoring Turbo Nandroid backups in another kernel (but restoring TWRP backups in another kernel will work fine - as long as userdata is not too big for the new kernel).
Important info on data safety
*Never* unmount/remove SDCard or pull the battery while system is using Slot 2/3/4. But mounting USB Storage or MTP to PC is 100% fine. Dev's - never use "adb reboot" command, instead use "adb shell reboot" for the safe reboot.
Do NOT install a ROM ZIP in Slot 2/3/4 until it is marked "multiboot-aware" by the creator. ROM's that are not Multiboot-aware will format and install to your internal (Slot 1), no matter *what* you do. There are two ways to work-around this:
1) [Easy, temporary] Basic idea is to move the ROM from Slot 1 (Internal) to the new Slot. When you first enter Slot 2/3/4, the wizard to set up the slot begins. You have the option to either create blank system and useredata images, or to copy (clone) it from Slot 1 (Internal). So basically, just install the ROM (e.g. CM9 or CM10) in Slot 1, then you can setup Slot 2/3/4 and chose "Copy from Internal" for system (and userdata if you like). Make sure the new Slot works OK, then you can erase and reinstall whatever on Slot 1.
2) [Detailed, permanent, ROM makers do this please!] Change the updater-script to use generic mount commands. I encourage all ROM makers to do this, it will still work with other kernels and recoveries fine. For details on the specific script changes needed, refer to this post.
Make sure your SDCard is free of errors. If you encounter *any* issues with *any* ROM, do a full Repair in the "Settings and Tools" menu before reporting any issues.
For a better detailed, newbie-friendly guide on Multiboot, or for more help, refer to this thread guide. Big thanks to RC fma965 for the guide!
Click to expand...
Click to collapse
Downloads/Installation
Please Nandroid backup before flashing. I am not responsible for any permanent damage or data loss. I try my best not to wreck your stuff though
This kernel uses a custom partition layout. /system size is 400MB and /data size is over 500MB. Flashing this kernel will DESTROY all your userdata and ROM, so backup first! You have been warned!
GSM ONLY - You must have a vendor-unlocked partition layout - this only needs to be done once, flash one of this full FTF first: R800i_4.0.2.A.0.62_phoenixvendor.ftf or R800i-4.0.2.A.0.79.ftf. You can find on this thread. -big thanks to smokerman and fma965.
CDMA ONLY - No need to flash any FTF, it seems R800x already has an unlocked vendor partition.
Download and flash the kernel - Dropbox folder for Turbo Kernel
First-time users - Enter Multiboot Menu (Vol-Down key) and go to Internal > Recovery, then format system, data and cache before doing anything else. Very important.
Do not install Google Apps straight after ROM install. You *must* boot the ROM at least once before installing Gapps package!
If you cannot enter the Boot Menu or Recovery after flashing, you need to flash the FTF first.
3.1.1 Source
Credits:
- CosmicDan - Obviously
- wedgess
- Kamarush
- DoomLord
- FXP
and other developers who keep Xperia Play still alive
Changelog
Code:
v3.1.1
----
- Expanded system partition (400 Mb)
- Bring back 720p video recording (Use it at your own risk)
- Minor bug fix on googlenow symlink
- default.prop fixed
v3.1
----
- New: Three more slot customization entries (MIUI, Stock GB and Stock ICS)
- New: Tweaks and Mods menu - "Logging Mode" (Default is 'Standard').
The "extended" mode is useful for developers to ask their users to report bugs easier.
- Fixed: UMS on Sock GB (always enabled, no sdcard unmount i.e. "Dual-Auto-Mount")
- Fixed: Various TSDX bugs
- Improved: GB support
- Improved: Shell "reboot" command adapted for better filesystem safety
- Improved: More misc. optimizations and cleanups to ramdisk
What the difference of this and the original version that Dan took down? This is directly copied from the thread he locked...
RoboticBuddy said:
What the difference of this and the original version that Dan took down? This is directly copied from the thread he locked...
Click to expand...
Click to collapse
for now the features are still the same from the original turbo kernel 3.1 apart from the minor change on the changelog. on the future I'd like to optimize it.
itazchu said:
for now the features are still the same from the original turbo kernel 3.1 apart from the minor change on the changelog. on the future I'd like to optimize it.
Click to expand...
Click to collapse
Well done man, keep up the good work. It's always nice to see kernel development is still alive for the Play.
itazchu said:
for now the features are still the same from the original turbo kernel 3.1 apart from the minor change on the changelog. on the future I'd like to optimize it.
Click to expand...
Click to collapse
Alright, sorry for the misunderstanding. Still good to see people still developing.
Does it work on Xperia Neo L?
RoboticBuddy said:
Alright, sorry for the misunderstanding. Still good to see people still developing.
Click to expand...
Click to collapse
it's alright. I'm still learning and perhaps I can't make any big differences with the original turbo kernel but I'll try messing around with this great kernel.
krchi said:
Does it work on Xperia Neo L?
Click to expand...
Click to collapse
I can compile for Xperia Neo L if you want.
bro @itazchu This can be used in neo l, or if not, can you make this work for neo l? thx
Are you planning to fix bugs for GB?
Can you convert it to .ftf? :cyclops:
Thanks... :good:
itazchu said:
it's alright. I'm still learning and perhaps I can't make any big differences with the original turbo kernel but I'll try messing around with this great kernel.
I can compile for Xperia Neo L if you want.
Click to expand...
Click to collapse
yes please
Jecmenn said:
Are you planning to fix bugs for GB?
Click to expand...
Click to collapse
I don't think so. it's beyond my knowledge. :crying:
Alvin Satrio Wibowo said:
bro @itazchu This can be used in neo l, or if not, can you make this work for neo l? thx
Click to expand...
Click to collapse
krchi said:
yes please
Click to expand...
Click to collapse
this is for Xperia Neo L. it's untested though because I don't have the device so use it at your own risk. Link.
itazchu said:
I don't think so. it's beyond my knowledge. :crying:
this is for Xperia Neo L. it's untested though because I don't have the device so use it at your own risk. Link.
Click to expand...
Click to collapse
ty testing now and also btw since this is a 480 kernel that means no 720p recording but can i watch youtube in hd? cause in past with gb roms it didnt work
krchi said:
ty testing now and also btw since this is a 480 kernel that means no 720p recording but can i watch youtube in hd? cause in past with gb roms it didnt work
Click to expand...
Click to collapse
and surely it doesnt work now..kernel is the same,only a little bigger.:good:
for GB roms flash a custom kernel like lupus gb or doomlord..its way faster and gaming is a lot better.
itazchu said:
this is for Xperia Neo L. it's untested though because I don't have the device so use it at your own risk. Link.
Click to expand...
Click to collapse
grab turbo kernel 3.1 for neol and make the same as for play..just make a little bigger,surely it will work fine.
smokerman said:
and surely it doesnt work now..kernel is the same,only a little bigger.:good:
for GB roms flash a custom kernel like lupus gb or doomlord..its way faster and gaming is a lot better.
grab turbo kernel 3.1 for neol and make the same as for play..just make a little bigger,surely it will work fine.
Click to expand...
Click to collapse
So, men you're saying that the lupus o doom kernel are better for gaming?
Im looking for a jb rom and kernel that can handle MarioKartDS whitout lags.
So do you think this kernel can do that? Or you can give me a idea of which combination i can use?
Sorry my english i hope you understand...
janolucero said:
So, men you're saying that the lupus o doom kernel are better for gaming?
Im looking for a jb rom and kernel that can handle MarioKartDS whitout lags.
So do you think this kernel can do that? Or you can give me a idea of which combination i can use?
Sorry my english i hope you understand...
Click to expand...
Click to collapse
a GB kernel is better for gaming on GB roms..if you want a JB rom then this is the right kernel for you..although is multiboot,is still the best kernel for play on any JB rom.(lupus v8 480p is also good) but this has more options,,its more complete.
en espanol vete a mi blog(clica en la imagen que ves por bajo de mis comentarios).
maybe i am just blind, but where are the sources with the changes made??
A bug in kernel....
In Default.prop is written appliance model zeusc ... You're interfering with apps games ... Has not detect nor gamespad the device ... Switch Zeusc to R800i or delete these lines should work ... but this standard has to be done directly in the kernel since changing the ROM does not work ... After reboot back to normal. thank you
Sent from my R800i (Xperia Play) using Racing Speed JB Rom
zeusc is the cdma xperia play. Was it the same in cosmic dan's build prop too?
Related
We are glad to present our kernel and ROM for Xperia Ray (st18i).
Stock-based ROM with cutting all no-necessary software. Kernel assembled from sources with usefull modifications.
ROM is very light-weight but powerful. There are NO any google apps in ROM. This is our rule. You can install it from "standard" GAPPS packadge from CM 7.2 topic.
You may use kernel with our rom or with your own stock-based rom including full stock, with any baseband. (we recommend 58 radio).
Both the kernel and the rom have passed test many weeks before we offer it to you.
ROM features:
- removed bloatware: google apps, SE anonymous statistics, adobe apps, ant+ apps, datamonitor, devicemonitor, facebook apps, timescape and all of their integrations. Thus, you have a lot of space for your programs.
- all other good and useful SE apps are still here: player, gallery, camera (including 3D), FM radio, TrackID, browser, default launcher.
- root and Superuser software are included
- useful switches in notification area, clean and precise battery indicator
ROM downloads:
primary mirror: http://narod.ru/disk/35145199001/ST18i_REPACK4PDA_6.zip.html
secondary mirror: http://www.multiupload.com/VAOQ83X1SX
Kernel features:
- kernel is assembled from SE sources with usefull modifications
- cwm recovery
- light and balanced overclock up to 1.4 GHz (we leave SE frequences grid) (default frequence range: 122 MHz - 1 GHz)
- deep undervolting but working under hard loading
- default and recommended governeur is SmartassV2 (we have been testing power savings for some weeks with many different kernel settings!)
- support for dual channel voice call recording (with CallRecorder software by skvalex)
- as a result, power consuming is just a bit higher in overclocked mode and usually much less than on stock firmware
- guaranted very deep sleep in suspend mode
- very stable work and all-sides-testing
Kernel downloads:
primary mirror: http://narod.ru/disk/36316696001/bootuv5.img.html
secondary mirror: http://www.multiupload.com/UKGMCCMX2C
Installation procedure is usual:
- download rom & kernel
- put rom into sdcard
- you can also put gapps package into sdcard if you want to install Google apps
- reboot your phone to "fastboot mode" (switch off power, press Vol+ button and plug USB cable)
- flash kernel with command 'fastboot flash boot bootuv4.img'
- unplug cable, power on phone, press Vol- when the screen becomes bright for entering to recovery
- select 'backup' option and backup your previous firmware (just for safety reason)
- you DON'T need to clear user data -- wipe is not required!
- select 'install zip', select our rom file, wait for installing firmware
- install gapps package with the same command, if you need it
- select 'reboot'
You get a new rom!
Our plans:
- we are constantly searching for new features to implement into a kernel
- we are testing a kernel with the new approach now, with new compression, with new init.d feature
- stay with us))
I'm considering flashing your ROM, but why wouldn't you let us overclock to 1.9 or 2.0 Ghz and "only" to 1.4 Ghz?
Just flash hartej/DoomLord Kernel if you want to OC higher...
piflechien said:
Just flash hartej/DoomLord Kernel if you want to OC higher...
Click to expand...
Click to collapse
Yeah I have that one flashed already, but I would like to know if this one is "better".
To Aire: What can the kernel of this ROM do more that DoomLord's kernel? In other words, why should I use yours and not DoomLord's?
I am so happy that aire post his great work here!!!!
I am using both kernel and ROM for more than 1 week and I can tell you that is the best in term of stability, speed and battery.
I so frequent checking the 4PDA forum for your work and use Google translate the message. So most of the time is guessing, and now you are here... thank you.. big thank you.
---------- Post added at 03:00 AM ---------- Previous post was at 02:37 AM ----------
Bazonga said:
Yeah I have that one flashed already, but I would like to know if this one is "better".
To Aire: What can the kernel of this ROM do more that DoomLord's kernel? In other words, why should I use yours and not DoomLord's?
Click to expand...
Click to collapse
Actually you can just try it out yourself to compare the difference and tell us about your finding.
What I found is without further setting, compare to DoomLord's kernel, the battery life is much better in this kernel.
aire said:
Our plans:
- we are constantly searching for new features to implement into a kernel
- we are testing a kernel with the new approach now, with new compression, with new init.d feature
- stay with us))
Click to expand...
Click to collapse
Great to see new developer joining us..!..Yay..hope to see stock with CM7 features ported....
thanks for your interest, guys!
while we prepared this first post (translate it) for bootuv4, aire has released a new kernel bootuv5. But translated features remained from previous ver. Now I will write up-to-dated features for you.
(so what you read 'in our plans' -- this is not future but presence release features)))
bootuv5 features:
- extremal undervolting at all frequencies
- filesystem support: ext2, ext3, ext4, yaffs2, vfat, ntfs
- overclock up to 1.4 GHz (work range 122 - 1024 GHz)
- init.d support
- default (and recommended!) governor is smartassV2
- ClockWorkMod Recovery 5.0.2.7
- anonymous services support removed (from kernel)
- fota support removed (from kernel)
- bidirectional calls recording
about 1.4 ghz.. Guys, SE kernel has calculated the manufacturer a grid of frequencies, if we add intermediate frequencies or overclock frequencies in table pll2_tbl (in kernel settings) -- in any case we have increasing a consumption.
We don't know how DoomLord has calculate this expanded table but all our tests says that battery drains more rapidly than on the default table. EVEN IF you will set 'default' 1ghz frequency in overclocked (to 1.8-2 ghz) kernel the consumption will NOT as at SE kernel, SE frequencies grid. The reason consists in it.
In real tasks enough 1.4 ghz, guys! But phone perfectly sleeps)) Any percent doesn't spend for a night. Is this not enough?
About init.d. In last repack4PDA (rom) the training script which is in a folder /etc/init.d is added. It named 'Scpufreq' and consists some commands to init default frequencies range and def. governor. You may try to change it for you taste)) But note that names of your scripts MUST begins from upper-case 'S', and permissions must be as r-xr-xr-x.
We will try to answer your questions, because aire have no time to read this topic.
ps. Don't forget that we tested more than month several kernel assembles and give you checked up Emerald))
Good to see another dev here! I Was using your latest kernel with stock .42 rom from SE for a little week or 2. Worked brilliant. Now I have flashed this rom, the repack4pda .58 version, and I am experiencing severe batterydrain in standby. Overnight I lost 26% when the phone was laying idle on my desk. There were almost nog wakelocks present, phone was awake for 3 times. I had this once before, that was when I flashed the hongkong edition .58 rom posted elsewhere on xda for ray. I think it has something to do with the baseband of this rom.
I found another baseband here on xda (also provided by you, thanks) and flashed that. After the baseband I flashed your kernel. The rom you have made is very fast and sleek, so I hope that this will solve my problem. Otherwise I have to revert to stock .42 again and start deleting bloatware.
See this screenshot of my overnight drain:
{
"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"
}
didn't try this rom+kernel....yet.
I'm currently on stock rom + doomlord kernel (bloatware removed from ROM).
I notice better battery life (@same clock speeds as stock) after rooting "and" 'battery calibration' app (free from market).
So fully charge the phone, then when still on charger at 100%, press "calibrate".
Hopefully this tool will extend battery life further
Please send you comments/experiences about the battery calibration, I used this tool successfully on my previous samsung apollo.
vleutmans said:
didn't try this rom+kernel....yet.
I'm currently on stock rom + doomlord kernel (bloatware removed from ROM).
I notice better battery life (@same clock speeds as stock) after rooting "and" 'battery calibration' app (free from market).
So fully charge the phone, then when still on charger at 100%, press "calibrate".
Hopefully this tool will extend battery life further
Please send you comments/experiences about the battery calibration, I used this tool successfully on my previous samsung apollo.
Click to expand...
Click to collapse
I have used that tool before. On .42, I managed to last 51 hours with the phone. Now, when my battery reaches 10%, it goes to 1% and the phone shutsdown. I will try to erase batterystats from cwm as soon as my phone is fully charged again. I used to have a Desire HD, I wiped batterystats from cwm there all the time and that worked great.
vleutmans said:
didn't try this rom+kernel....yet.
I'm currently on stock rom + doomlord kernel (bloatware removed from ROM).
Click to expand...
Click to collapse
you can try new kernel w/o reinstall rom. this rom just more clean than we can clear it 'by hands')) if your current rom is ok -- no need to reinstall it.
vleutmans said:
Please send you comments/experiences about the battery calibration, I used this tool successfully on my previous samsung apollo.
Click to expand...
Click to collapse
Question is not for this topic, I think. Recalibrate battery statistics file need if you reflash cyanogen after stock or vice versa. If your rom is stock usually no need battery file deleting.
If your battery drains quick (as it seems to you) at first, once a month it is necessary for us to discharge the battery completely, then charge it _without interruption_. And even allow be at charger 20-30 minutes after 100%. (NOT at all night!) Repeats this twice. After that a new statistics will register to battery file and phone will 'know' it real edges of 0 and 100 percents.
At second, need to see which apps wake phone up. You may install any special app for battery and processes monitoring, e.g. battery mix, and see it statistics after some days for who eat battery)).
Bazonga said:
I'm considering flashing your ROM, but why wouldn't you let us overclock to 1.9 or 2.0 Ghz and "only" to 1.4 Ghz?
Click to expand...
Click to collapse
DoomLord's approach is probably wrong, but we do not know what exactly is wrong. His overcloclocking method looks like "brute force" leading to higher power consumption no matter how you are using your Ray, even if you are not using it at all.
aire doesn't modify any frequencies tables in source code, just cheat some part of a kernel showing it than it's not a Ray, but Arc S (oh yeah, you don't get an Arc S for free anyway ). So we get frequency range as it designed by SE developers. Than he add some good governers, apply extreme but stable and tested undervolting, and we got that brilliant... oh, sorry... pure emerald[1] kernel.
Combined with clean REPACK4PDA rom, this kernel give you good starting point to set up your SE Xperia Ray (which me personally assume as one of the best smartphone today) to work fast and long.
[1]About "PureEmerald" name, as we call this kernel on 4pda.ru. There is a tale by a greatest russian poet A.S. Pushkin, "A poem about tzar Saltan". This is a small part of this poem translated to english:
Here's a wonder, though, worth telling -
There's a little squirrel dwelling
In a fir tree; all day long,
Cracking nuts, it sings a song.
Nuts - most wondrous to behold!
Every shell is solid gold;
Kernels - each an emerald pure!
That's a wonder, to be sure.
Bluetooth again ..
.. like so often: nice image with cool features - but I don´t get serial ports from the connected bluetooth device on my pc (to sync with myphonexplorer, works good using stock firmware ).
Same issue in CM7: some versions creating these ports, some not. Maybe I have to change some settings on the phone, any ideas ?
I also have tried to install gapps-gb-20110828-signed.zip, but the market did not appear in the app list.
But anyway: one day it will work and I say THANK YOU
Is there a way to get the quickpanel in stock firmware, just in case.. I don´t believe it is only the QuickPanelSettings.apk right ?
speola said:
Is there a way to get the quickpanel in stock firmware, just in case.. I don´t believe it is only the QuickPanelSettings.apk right ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1392472
need 2 files: SystemUI.apk (with replacements) and QuickPanelSettings.apk. This is offtop))
Good to see new devs with somewhat new approaches of modding. For example, i love the "keep it stock" way you guys do this.
Flashed just the kernel, the battery life is great and call recording works flawlessly, so.. thanks!
I confirm the battery drain with doomlord kernel is very very very fast, even in flight mode without any activities and default clock of 1 ghz
now I will try your kenel
speola said:
I also have tried to install gapps-gb-20110828-signed.zip, but the market did not appear in the app list.
Click to expand...
Click to collapse
Hmmm... It should work. The only problem with gapps is the need to reinstall it each time after installing update to repack4pda. But after reinstall everything works fine for me.
Installed v5 kernel (on stock .58 HK ROM, which is manually cleaned from bloat).
Works fast and stable, but no noticeable battery life improvement. Still drains 1% per hour at night, when it is laying on desk idle (Wi-Fi turned off). So no deep sleep I guess..
Battery stat. is showing that 65% is used by "Idle process". Shall I adjust something ?
After installing gapps-gb-20110828-signed.zip, you need to manually add a google account under accounts and synchronization. After that, the market is there
Patshad said:
After installing gapps-gb-20110828-signed.zip, you need to manually add a google account under accounts and synchronization. After that, the market is there
Click to expand...
Click to collapse
That was the missing link ! Many thanks !!
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 ;/
D-WiZ 3.0.2 [AROMA-BMM] / D-WiZ 2.0.4 [Safestrap 3]
D-WiZ Dev Team Presents:
{
"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"
}
This rom is a try to provide a rom with less battery drain. Most roms are coming without real battery saving tweaks. So we created our own rom with lots of special tweaks. Some tweaks are based on already existing ones, but we wrote most of them ourself to get the most out of the Razr battery.
- STOCK-Kernel-Version -
ATTENTION: We have released untested CDMA-Version! If anyone here with a CDMA device wants to test, please provide some feedback. Thx!
Changelog 3.0.2
- Camera picture quality improved
- Overall Performance improved
- New themed Play Store (no more blue)
New Tweaks:
- V6-Supercharger integrated
- Performance switch modes included:
Open Terminal Emulator and type 'su', then type:
'game' - to activate high performance mode
'stock' - to activate batery saving mode
'scharge' - to configure V6-Supercharger RAM Management
You can use Script Manager to create oneclick-widgets on your homescreen to switch profiles.
This feature will be integrated in the system settings soon, Until then use the Terminal Emulator.
Click to expand...
Click to collapse
Changelog 2.0.5
- Fixed all bootloops issues - REALLY^^
- Updated source
- Fixed CPU Clock Daemon
- Fixed zipalign, sqlite vacuum
- Fixed kernel parameters
- Added Powertop 2.1
Click to expand...
Click to collapse
NEWS:
You can flash D-WiZ now directly to your Stock Slot (BMM ONLY for now).
NOTE: Just to be safe, when Aroma finished the installation DON'T reboot!! Untick the box "Reboot device" and click "Finish". Then go back to the main menu, got to "System Keeper" and select "Install Bootmenu to Stock Slot"!!!
D-WiZ is now available with AROMA Installer! Only for use with Bootmenu Manager 0.3.2
A tutorial for BMM is below!
There are several reasons to switch to BMM 0.3.2:
Much more tweaks - On virtual slots (e.g. SS3 Rom Slots, BMM System 3-6) some tweaks are causing bootloops and freezes
Better battery life
Better performance
Faster boot process
Aroma Installer
Because of that D-WiZ is now available in two different versions: One for Safestrap 3 and one for Bootmenu 0.3.2. The SS3-Version is kind of a "lite-version" because I had to remove several tweaks (were causing lots of issues).
The BMM-Version includes all tweaks, mods and advantages of D-WiZ, but please note that this version will only run on non-virtual slots!
There are several Patches and Add-Ons available in UpdateMe! You can find UpdateMe in the App Drawer.
The current version 2.0.3 can cause Bootloops on some devices. If you have that issue, please reboot (2-3 times) until it boots up completely, then open UpdateMe in the App drawer and download the D-WiZ-Init-Patch from Patches section. Flash it in recovery!
NOTE: If you are using the Undervolt-Patch: The voltage values will be overwritten by the Inid-Patch! You have to flash the Undervolt-Patch again after applying the init-Patch!
D-WiZ is undervolted by default. But you can set lower values for more undervolting. Just download the Undervolt-Patch from UpdateMe patches section and flash it in recovery.
NOTE: The values from the Undervolt-Patch values can be too low for some devices and causing crashes and freezes! If you get problems after flashing the Undervolt-Patch, just flash the Init-Patch to reset the undervolt settings. Now you can edit the 70uvoltc file inside the Undervolt-Patch zip Archive and try it out until you find good settings for your device.
The 70uvoltc file inlcudes some line which looks like the following:
0 100 825 > /proc/cpu_control/tweak_cpu
1 200 850 > /proc/cpu_control/tweak_cpu
2 300 875 > /proc/cpu_control/tweak_cpu
3 400 900 > /proc/cpu_control/tweak_cpu
4 600 950 > /proc/cpu_control/tweak_cpu
5 800 1000 > /proc/cpu_control/tweak_cpu
6 1000 1088 > /proc/cpu_control/tweak_cpu
Click to expand...
Click to collapse
The red numbers are voltage values in mV. Just play around with +25 mV (or +50 mV) and test it. When it works without freezes or crashes you are good to go.
Click to expand...
Click to collapse
How to use Bootmenu Manager 0.3.0f
Download BMM 0.3.2 from Google Play.
.
Download D-WiZ_3.0.1_AROMA_XT910.zip
.
Boot into your Main Rom /Stock Rom
Open Safestrap 3 App and tick "uninstall recovery" <--- If you were using SS3
Unpack the BMM package on your computer
Plug in your device (USB with Debugging enabled)
Run the install.bat from BMM folder
Note: If there are displayed some errors while installation, doesn't matter. Just reboot and if you see BMM, it's ok. But if there is no BMM splash screen you have to install BMM again like described above (you may rstart the adb server before to prevent error)
Now you have to prepare your rom slots:
Reboot and when the BMM screen appears, tick "Settings".
Now Select a slot you want to use, open "Boot Mode" and untick: "2nd-Boot" and "Kexec".
.
If you want to use rom slot 2, please follow the instructions at the end of this quote (How to protect your 2nd Slot Cache)!
.
If you want to use the rom on your stock slot:
If you are coming from another rom, please perform a full wipe, wipe dalvik cache and formant system (in "mounts & format")
flash it directly to stock slot!
NOTE: Just to be safe, when Aroma finished the installation DON'T reboot!! Untick the box "Reboot device" and click "Finish". Then go back to the main menu, got to "System Keeper" and select "Install Bootmenu to Stock Slot"!!![/B]
Continue here when you want to use another Slot (Slot 3-6):
Go back and open "Partition Setup".
Create the slots (System, Datam Cache) with your preferred sizes.
Now go back to boot screen and select recovery.
In recovery switch to your created slot (under Recovery Switch)
Now flash the rom (as usual: "Install zip...") and enjoy AROMA
Now it reboots, hold on in splash screen (select settings or sth like that)
Now you have several options:
You can boot into the slot where you installed the rom.
NOTE: There can be bootloops for some reason only after first installation (still have to figure that out) so I would recommend you to use the rom on Stock or second slot.
To set the default slot to boot, boot into rom, open /system/etc/bmm with root browser and edit "bootmenu.prop":
#bootmenu
default=1 <--- Number for your rom slot!
Click to expand...
Click to collapse
How to protect your 2nd Slot Cache (otherwise it doesn't boot after first time boot)
Reboot into recovery
Switch to slot 2
Flash the rom
Download this: Aromafs-1.80.zip
Plug in the device and select in recovery. "Advanced Options" --> "Mount as USB storage"
Rename the file to "Aromafm.zip" and place it on your internal storage in: /clockworkmod/
Plug off the device
Select "Filemanager"
Now press Menu button in right lower corner
Select "Open Console"
type in the following
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/system
e2fsck -fDC0 /dev/block/system
Now you are ready to go with Slot 2!
Please try around and report issues here!
Click to expand...
Click to collapse
[WIP...] = Work In Progress
Features
- CM10-Based
- tweaked:
Auto brightness a bit darker than default JB [WIP...]
System-Tweaks for RAM-Management, SD-Card-Boost
-- Hotplug-Governor reconfigured:
set as default governor
aggressive downscaling
2. Core wake up only if really needed
2. Core sleep faster
upscaling more slow
scales to higher frequencies if really needed
-- CPU-Tweaks
Undervolted
Underclocked
CPU-Frequecy table: 100, 200, 300, 400, 600, 800, 1000 mhz
"CPU-Clock-Daemon" - sets the CPU back to minimum freq of 100 after kernels QoS request (takes a few minutes sometimes / doesn't prevent device from deep sleep)
-- System Tweaks
fast and stable UI also on very low CPU frequencies
prevent Dirty Writeback Timeout
ram management
SD-Boost
Wifi Power Management On (saves battery, in case you're at home it will set to lower signal strengh but really enough for good signal)
-- Kernel Tweaks
for better memory usage
faster System
power usage
default scheduler SIO
- SystemUI: Razr I Launcher & 3DCircle
- OTA Updates (Updates from my Server)
- GAPPS blacked out
- 4.2 Camera
- 4.2 Gallery
- 4.2 Gmail
- 4.2 Keyboard
-- Full automatic and location based power-controll via integrated Llama (WITH finished profiles):
automatic switch 2G/3G (Browser or Play Store On: 3G Preferred)(Browser or Play Store or Screen Off: 2G)
if connected to WLAN: 2G
if entering home: WLAN ON, Data Off, 2G
*profiles can be customized and extended of course
- CM10- & AOKP-Features
- Root & Permissions-Security included
- Modified, improved Version of Google Now
Click to expand...
Click to collapse
NOTE: This Rom was made for saving battery!!! No overclocking and no super-fast-as-hell-tweaks! If you are looking for sth like that, take another rom! I managed it to get this rom fast and stable also on low CPU usage, just try it!
Click to expand...
Click to collapse
Llama-Profiles:
Here are Instrucions how to use Llama: http://kebabapps.blogspot.de/p/llama-handling-guide-instructions.html
Download Zip File: KLICK
Extract it and copy its content (the folder) to your EXTERNAL SD-Card.
Open up the Llama-App and press the "Menu-Button".
Select "Import/Export Data" and choose "IMPORT from SD-Card".
The profiles are now activated
Now you have to select your home Area on the LEFT tab. Press and hold on "Home" and select the option to detect your home location (some minutes should be enough)
Last thing is to select you home Wifi. Press the menu button and select settings (or options, dunno how its in English). Scroll down to experimental stuff, then choose check for Wifi Networks". Go back into Llama menu and select tab "Recent", search for you Wifi Network and press and hold it, now choose "Add to area" and select home.
IMPORTANT: Now go back into experimental stuff settings and DEACTIVATE the search for Wifi Networks option!
There are some "sync-Rules" in the Llama Profiles, they are experimental (background data sync on for 1 minute everx 20 minutes). Just deactivate or delete them if not needed (maybe they are causing partial wakelocks). But before you delete them, just have a look into them, so you'll see how complex this app can be customized!
Llama is now configured and active! Now you can add your own rules if you want.
Llama is VERY powerful! Have a look into its options and you'll find an option called "Llama Variables". They can be set to whatever you want. So there are very very complex rules possible! If configured the right way, Llama can also help saving battery a lot! Take you some time to learn how it works.
CAUTION: The profiles are made on a German device!! That means for any users from different countries, you must rename the area names in EVERY rule to your areas location names, or you rename your location areas to German: home = "zuhause", etc.., just look for the names inside the rules.
Click to expand...
Click to collapse
What works
- almost everything
Camera
Full HD Video Recording
Camera Flash (temp. solution)
Wifi
Data
Bluetooth (almost)
Google Now
Bugs
- Screen Rotation (zooms out shortly)
- No sound in calls while activated Bluetooth (WIP)
- Sound weird bahaviour when using a BT-Headset
Click to expand...
Click to collapse
- Installation for Safestrap -
Safestrap 3
Wipe Data, Cache & Dalvik, Format System
Flash Rom
load the Llama Profiles (above) or make some by yourself
*GAPPS are integrated
If you are updating from prior D-WiZ version, usually just flash the zip WITHOUT ANY wipe - except for update from < 1.0.5, there you MUST perform a full system & data wipe!!
If you are using BMM check the how-to on the top of this post!
For non-EU users (if you notice battery drain or weird behavior with the rom:
If you notice battery drain or another issue do the following:
1. Download one of these kernels (try them and decide which one is the best for you):
Kernel 9th June
Kernel ICS latest
Place the kernel on your SD-Card
2. Now boot into Bootmenu recovery
3. Select "Firmware Falshing"
3. Select "Backup CID" and confirm with "Yes"
4. Select "Erase CID" and confirm with "Yes"
5. Now select "Backup Kernel"
5. Select "Flash Kernel (boot.img...)", select the boot.img file which you've saved on your sd-card before and confirm with "Yes".
6. If you haven't flashed the Rom yet, do it!
7. Reboot into D-WiZ Rom and enjoy!!
NOTE: If you want flash back your LATAM Kernel for any reason, go to recovery, select "Firmware Flashing" and "Restore CID" (You will find your backed up CID in /sdcard(-ext)/clockworkmod/Firmware/...". You will also find your backed up kernel in that folder!
This rom runs best when you DON'T change any CPU-related settings!
Please DON'T change any kernel parameters if you are not familiar with this stuff!
NOTE: after the each reboot all CPU settings will be restored to default (NOT Kernel- and other Tweaks!)
Sometimes the kernel sets the CPU to 300 min. If you should notice that, just let it be, the rom will set it back to 100 after some minutes. Also ALL frequencies are undervolted, so it won't eat much battery anyway.
Click to expand...
Click to collapse
Some suggestions:
Go to display and brightness settings, select auto brightness, customize and add 2 or 3 more steps (fill the values continuing)
--- GSM || CDMA ---
For more informations visit: http://www.dtrailer.de
MIRROR
[Flash Kernel and Baseband]
Download Kernel / Radio Flasher: KLICK
Donation
If you like our work we would appreciate it if you would send us a small donation. Donations make sure that we can go on providing you Roms and other stuff. We are doing all this in our spare time, but thereby resulting cost. We use this money to buy equipment or pay our servers and workspace environment.
If you want to donate use the Donate Button below my name (below Thanks Meter)
Contributors:
Many thanks to all those who donated to us!
Jack'o (xda)
Wombatino (xda)
Palmin (Handy-Faq)
nischalnischal (xda)
Spectral1991 (xda)
blackhawk_LA (xda)
Gombi123
Drais
BlaXXuN/picz (xda/Handy-Faq)
HornetRider (Handy-Faq / XDA)
maarawoe (XDA)
Ferhat
Mirko
Robert O.
Jan B.
Burnfaker / Xantian
Dennis D.
Rafael P.
Bopp77
Uwe D.
Lukas S
Torsten V.
Faekie
inVi
Sp_Ark
Todi
gorgon
TM4rkuS
Stefan M
Jan S
Slipi
Nizen054
prohto
gelete
Palmin
Stefan K.
Master__p
Ming S. A.
Benjamin
Saratoga79
gehgru
Daniel B.
EntenTrude
Gary N.
Stefan D.
Click to expand...
Click to collapse
D-WiZ Dev Team:
dtrail
Brunomau
Silentjet
DumbleCore
avalakvista
runakai42
Xantian
Click to expand...
Click to collapse
*Thanks to:
Whirleyes for his awesome work and kernel modules!
Frasertag for answering all my questions!
STS-Dev-Team for their work on the Base-ROMs and making them compatible with our hardware!
XDA and its great community!
XlightwaverX for his awesome development social network site and help!
Flashing! Interesting idea to make a ROM battery friendly. I have tested a lot of apps and tweaks to save some juice in my RAZR and I'd like to see your ROM in action.
sounds really good.. maybe try it sometime soon!
Sent from my XT910 using xda app-developers app
CONGRATS!
How can I flash it on second system using BMM 0.2.7? Convert, wipe all, install?
Thank you
heblu said:
CONGRATS!
How can I flash it on second system using BMM 0.2.7? Convert, wipe all, install?
Thank you
Click to expand...
Click to collapse
I suggest you to use BM 0.2.8 beta 2 (or 0.2.9a maybe, but 028 beta 2 should work). But if you want to get sure that everything works well you should use Safestrap 3 because I made this rom for use with it.
btw: SS3 is awesome!
dtrail1 said:
I suggest you to use BM 0.2.8 beta 2 (or 0.2.9a maybe, but 028 beta 2 should work). But if you want to get sure that everything works well you should use Safestrap 3 because I made this rom for use with it.
btw: SS3 is awesome!
Click to expand...
Click to collapse
I have already 2 systems on my phone. Is there an easy way to go from BMM to SS3 without changing first system? Never tried SS3 before.
And if I install 0.2.8 beta 2, do I still need to convert the rom? What are the steps after that? Wipe data, cache, dalvik and then install?
Thanks for your fast reply, hope I didn't put too many questions and may the force be with you
The force is with me all the time! lol
With BM beta 2 you have to convert but without selecting extra options. With BM 0.2.9 you don't have to convert, but better have a look into its thread to get the right information.
If you switch to SS3 your main system will stay. Your 2. system will be gone. But instead of that you can have 4 Systems (+ Main System = 5 Systems). In SS3 you are able to create "Rom-Slots". These slots can be created with custom space (for example: One slot with 3gb of data for daily use, one test Slot with 1gb of data for testing purposes). The Rom slots are located on your INTERNAL storage and App data is located on EXTERNAL storage (so you need an extra SD-Card, if you don't own one, you can keep your internal sotrage as app data storage using a small hack). And make sure you have some space left on internal storage.
SS3 is kinda easy to use. Once installed you will understand it for sure. But be sure that you remove BM completely from your device PRIOR installing SS3. An uninstaller for BM can be found inside the BM app. For further information check the SS3 thread.
I love it dtrail
Thanks
thank god
widget
Circlesw widget dont work after stock installation, neither bootmenu or ss3
Anywaya thank you for this great rom it will be my daily driver!!
Cool. Will test it. Thanx for no TouchWiz by default
1. Request translate "ROM" menu to russian (aokp strings rather, cm sttrings in russian already), please send me xml or strings.
2. Why AOKP toggle enable flashlight, but CM toggle no do it?
3. My operator in notification panel "Megafon|Megafon" instead "Megafon" =(
4. No data work without fix =(
5. Circles widget doesnt work without fix (fix not tried yet)
6. All fast and stable yet, continuing test.
7. Please, add all fixes in Update Me =)
pokatusher said:
Cool. Will test it. Thanx for no TouchWiz by default
Request translate "Interface" menu to russian, please send me xml or strings.
Click to expand...
Click to collapse
Have you tried "set locale" from play store?
XT910 - CM_D-WiZ
fulii said:
Circlesw widget dont work after stock installation, neither bootmenu or ss3
Anywaya thank you for this great rom it will be my daily driver!!
Click to expand...
Click to collapse
There is a workaround in the OP.
XT910 - CM_D-WiZ
I'm updated post =)
All in russian except some strings.
pokatusher said:
I'm updated post =)
All in russian except some strings.
Click to expand...
Click to collapse
The data issue is related to your phone location. On EU devices data works fine.
Most of these issues you listed are related to CNA. So probably I am not able to fix them.
It was and still is hard work for me. So be patient. Thx.
XT910 - CM_D-WiZ
If you bring me non-translated XML, i will translate it into russian.
Which camera app is in this rom? Motorola one or the Jelly Bean without flashlight and FullHD recording?
As to the battery Here are my screenshots...
It doesn't matter which camera app is used - hd video recording and flash won't work anyway. This is a kernel / driver related problem.
You own a Maxx or normal?
Btw: the rom also needs some time to settle in after installing. Give it 5-7 days to normalize its battery consumption.
XT910 - CM_D-WiZ
Your Llama profiles dont work because conflict with russian lang in Llama (e.g. your zone "Zuhause" in my Llama called as "Работа")
System-Tweaks for RAM-Management, SD-Card-Boost
Click to expand...
Click to collapse
Sd Card Boost is disabled in Tweaks menu by default, its normally?
You own a Maxx or normal?
Click to expand...
Click to collapse
Normal.
If you need flash then ZoomCamera is able to make pictures with flash - just select Torch mode for flash and the pictures will be taken with flash.
{
"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"
}
Current device support:
anzu (Arc) (LT15): Alpha in progress
ayame (Arc S) (LT18): Alpha in progress
haida (Neo V) (MT11): Alpha in progress
hallon (Neo) (MT15): Alpha in progress
iyokan (Pro) (MK16): Alpha in progress
phoneix (Neo L) (MT25): Supported
zeus/zeusc (Play) (R800): Supported
Others - No plans, probably never (only HDPI Xperia 2011 devices will be supported by MIUI Australia)
Full feature list:
Early roots in KRsH 2.6.32.9/4.1.C.0.7 kernel. Has changed drastically since first release; additional changes from CosmicDan, FXP and Irii. Stock-based kernel with manual changes/updates for AOSP and JB support - reported my many to have better batterey life and reliability than FXP-based kernels. Also built with Linaro toolchain and uses some Linaro-optimized memory functions.
Supports GB, ICS and JB ROM's. Configurable via the "Slot Mode" in the specific slot for the Boot Menu (see next point). AOSP-GB ROM's (e.g. CM7) are not supported.
Turbo Boot Menu. Entered by pressing vol-down (acts as a pre-recovery menu). Supports four slots for installing ROM's into - Slots 2-4 are stored on ext2 "image" files inside the /sdcard/turbo/ folder. Powered by the brilliant Aroma Installer GUI by Amarullz - any slot can be changed to your default boot, and each slot's icon and text can be customized
Tweaks and Mods selection for each slot:
- TSDX - my own set-and-forget sd-ext script. Ability to share apps between each slot. Can also be uninstalled if desired (for one slot or for all - fully wizard-driven install/uninstall interface).
- Restore random entropy device - By default, Turbo kernel replaces the /dev/random entropy device with urandom. No need for a seeder - in fact an entropy seeder will do absolutely nothing in this kernel, just sit there feeding entropy to the same device. This option can be toggled to set the default device back to random.
- Deasec v2 - When enabled, this slot will decrypt "asec" apps on startup. Helps a lot with App2SD/Link2SD users. Original concept by Giovanni Aneloni, rewritten by myself (CosmicDan).
- Change USB to ### - This option can toggle this slot to force UMS (Mass Storage) or MTP (Media Transfer) mode for USB connections. Please note that some ROM's, e.g. latest CM10 and KXP-JB, have completely disabled UMS in the ROM. Nothing I can do about that.
- Disable ALS - Enable or Disable the ambient light sensor for this ROM. If a ROM has a "disable ALS tweak" built it, this option will not do anything.
- Logging Mode - Change the Logging mode from the default to either Disabled or Extended. Disabled can increase performance (but logcat will be unavailable), extended can help with developers. See the option itself in tweak menu for more details.
Repair Functions. Inside the Boot Menu > Settings and Tools, the repair function will attempt to fix errors on SDCard and Slot2-4 images, and fix permissions. Default full repair and Advanced selection modes possible.
TeamWin Recovery Project. Can also be switched to/from CWM-Recovery in the Boot Menu > Settings and Tools menu. TWRP is recommended though as it's much more advanced and user-friendly. Contains additional fixes thanks to championswimmer, a theme and UI design by myself, plus the "Factory Reset" option will *not* touch the sd-ext partition.
Increased RAM capacity (select devices). zeus and phonex (Play/Neo L) have 379MB of RAM total. 720p recording is removed since it is buggy in Jellybean (gives a good chunk of more RAM), and also some of my own kernel tuning to squeeze a bit more (smaller kernel footprint = more RAM for Android). Do not ask for a 720p recording version, it will never happen - use a different kernel if you want it.
Expanded /data partition (varies per device). 600MB+ of space on userdata. Please note that your /system ROM must be no larger than 310MB to use this kernel. If you don't know how to check this, contact your ROM author for details and to make their ROM compatible with this kernel - also they can contact me for tips on crushing their ROM size =)
Automatic wifi-module. There is no ZIP install required for Wifi module, the kernel init can detect automatically if the wifi module(s) need to be installed. They are located on the RAMDisk (at {root}/modules) and the kernel simply makes a symlink to the .ko files on boot if it needs to (linking is better than copying them).
Snappy zRAM compression. I personally don't use zRAM at all because it slows things down (still ain't snappy enough, heh), but "Snappy" zRAM compression by Google is apparently a lot faster than the traditional LZO compression and only a tiny bit worse compression ratio.
CPU governors - Intellidemand (default, has my own enhancements for our single-core Snapdragon CPU's - including CPU ramping on touch events ported from "Project Butter"), Lagfree, SmartAssV2, Performance and OnDemand. No, I will not add more governors. More governors = more RAM used by kernel = less RAM for Android.
I/O schedulers - SIO (default), deadline and noop. No, I will not add more schedulers. More schedulers = more RAM used by kernel = less RAM for Android.
CIFS, TUN/TAP and FUSE support built-in. No modules required.
...did I miss anything? Don't think so.
Compatibility:
The kernel has been tested and working on the following ROM's -
CM10 (Not multiboot-aware)
CM9 (Not multiboot-aware)
?
Please report if it works or not for other Jellybean/ICS-AOSP ROM's (and the status of it being multiboot-aware).
FAQ/Bugs:
Q) When I select "Reboot > Recovery" in my ROM, it boots recovery but there are strange errors!
A) Yes, this will boot recovery but it won't know which slot to use. I can't fix this sorry, so simply don't use it (just use Vol-Down on normal reboot).
Q) My device keeps going into the Boot Menu, even though I never pressed the key to enter!
A) This is a bootloader thing and is rare, to fix it just enter Recovery (for any slot) and select reboot from there.
Q) Camera does not work in my Stock GB or Stock ICS based ROM!
A) Known issue. I *may* be able to fix camera in Stock ICS ROM's later, but Gingerbread will probably never happen.
Q) I get an FC when trying to record video!
A) Make sure you select 480p for the quality in camcorder settings. Recording only works on ICS-AOSP and JB ROM's with no 720p.
Q) My ROM in slot 2/3/4 is bootlooping, or I'm getting FC's all the time!
A) Your microSD has become corrupted, probably due to a battery pull or an unclean shutdown - and so the Slot images have also been corrupted. Chose the Tools > Repair function in Boot Menu to try and solve it. If not, I'm afraid you'll have to *delete* that slot (a format will not do) and re-create the images. (Note to ROM dev's - best to use Slot 1 for testing/working, since this is the safe slot for battery pulls/adb reboot command).
Q) I have a problem with my ROM - I flashed Turbo Kernel and restored my backup with Nandroid.
A) This is not possible. If you have a Nandroid/TWRP backup from another ROM, it cannot be restored with this kernel. This is because of the custom partitions. The same goes for restoring Turbo Nandroid backups in another kernel (but restoring TWRP backups in another kernel will work fine - as long as userdata is not too big for the new kernel).
Important info on data safety
*Never* unmount/remove SDCard or pull the battery while system is using Slot 2/3/4. But mounting USB Storage or MTP to PC is 100% fine. @Dev's - never use "adb reboot" command, instead use "adb shell reboot" for the safe reboot.
Do NOT install a ROM ZIP in Slot 2/3/4 until it is marked "multiboot-aware" by the creator. ROM's that are not Multiboot-aware will format and install to your internal (Slot 1), no matter *what* you do. There are two ways to work-around this:
1) [Easy, temporary] Basic idea is to move the ROM from Slot 1 (Internal) to the new Slot. When you first enter Slot 2/3/4, the wizard to set up the slot begins. You have the option to either create blank system and useredata images, or to copy (clone) it from Slot 1 (Internal). So basically, just install the ROM (e.g. CM9 or CM10) in Slot 1, then you can setup Slot 2/3/4 and chose "Copy from Internal" for system (and userdata if you like). Make sure the new Slot works OK, then you can erase and reinstall whatever on Slot 1.
2) [Detailed, permanent, ROM makers do this please!] Change the updater-script to use generic mount commands. I encourage all ROM makers to do this, it will still work with other kernels and recoveries fine. For details on the specific script changes needed, refer to this post.
Make sure your SDCard is free of errors. If you encounter *any* issues with *any* ROM, do a full Repair in the "Settings and Tools" menu before reporting any issues.
For a better detailed, newbie-friendly guide on Multiboot, or for more help, refer to this thread guide. Big thanks to RC fma965 for the guide!
Downloads/Installation
Please Nandroid backup before flashing. I am not responsible for any permanent damage or data loss. I try my best not to wreck your stuff though
This kernel uses a custom partition layout. /system size is 310MB and /data size is over 600MB. Flashing this kernel will DESTROY all your userdata and ROM, so backup first! You have been warned!
Install the latest ICS FTF for your device to set it back to stock partitions. Very important. Do not use any custom/enhanced FTF.
Ensure your ROM is less than 310MB system size. If you are not sure or don't know how to check, contact your ROM builder.
Download and flash the kernel -
Mediafire folder for Turbo Kernel
First-time users - Enter Multiboot Menu (Vol-Down key) and go to Internal > Recovery, then format system, data and cache before doing anything else. Very important.
Do not install Google Apps straight after ROM install. You *must* boot the ROM at least once before installing Gapps package!
If you cannot enter the Boot Menu or Recovery after flashing, you need to flash the FTF first.
Sources and Changelog
All sources all on my GitHub (see my sig) in the KRsH kernel (there are a few kernel repo's but the KRsH one with latest update is this one), under "jellybean" branch. TWRP sources are in Team-Win-Recovery-Project repo under "jb-wip" branch (yes, it's TWRP 2.4.1.0+ - I'm just too lazy to branch). CWM sources under android_bootable_recovery.
Changelog: See this post (same changelog for all devices).
When you first enter the boot menu, please press 'Menu' > 'Calibration' and send me your careful and accurate calibration values so I can update the script. Thank you!
thanks for Giving us turbo Kernel.. I have updated my old post with New Release Thread...
Calibration Play calibrations worked fine for me. But better wait others try...
Thanks for the great work
I have run it on the below Roms and it was great...
http://forum.xda-developers.com/show....php?t=1999484 Turbo UI
http://forum.xda-developers.com/show....php?t=2021373 [ROM][JB][AOSP]
http://forum.xda-developers.com/show....php?t=1975851 SlimBean
Also PAC and PA roms from Xperia Play works fine..
Oh OK, makes sense because of the 99.9% identical hardware.
Are those ROM's ports from the Play? Or did you build AOSP from source? Also are they "multiboot-aware" updater-scripts?
thanks
but this kernel can work on CM10.1??
Great big thanks Dan :good: will be flashing it soon when i go home :victory:
Nothing I changed. Just compiled kernel using Neo L config files and made kernel.
So what all configs you had in Ramdisk was there untouched.Because of that all Xperia Play roms will boot as with Neo L kernel.as the Ramdisk identifiy itself as Xperia Play device.
Because of this I didnt need to change anything..
---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------
CosmicDan said:
Oh OK, makes sense because of the 99.9% identical hardware.
Are those ROM's ports from the Play? Or did you build AOSP from source? Also are they "multiboot-aware" updater-scripts?
Click to expand...
Click to collapse
No ports just plain Xperia Play roms.. they worked on Neo L
---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------
Guys some one pls check if the usb mount happen in TWRP Recovery..
At Last .....
somethimg great is coming for Neo v from great cosmicdan:good:
will b there at your side
mido_fedo said:
thanks
but this kernel can work on CM10.1??
Click to expand...
Click to collapse
Where is CM10.1 for Xperiia 2011 devices? There is none. Only CM10.
b00tbu9 said:
No ports just plain Xperia Play roms.. they worked on Neo L
Click to expand...
Click to collapse
So even Camera libs or any other libs don't need changing? Strange. Looks like when I build MIUI I can just skip phoenix and edit build.prop to match Neo L then
b00tbu9 said:
Guys some one pls check if the usb mount happen in TWRP Recovery..
Click to expand...
Click to collapse
Is it not working for you? I used championswimmers' init.semc.usb.rc (from Neo L ICS kernel) so it should come up as Neo L, let me know if it's broken.
Awesome Dan! Downloading the kernel now! Will report back after the installation!
[Edit]: Installation was smooth and successful. The ROM seems nice and very responsive. However display is fixed in landscape mode. Not able to get it back into portrait. Is this normal?
b00tbu9 said:
No ports just plain Xperia Play roms.. they worked on Neo L
Click to expand...
Click to collapse
So camera is not inverted in this case?
Re: [KERNEL][JB][ICS-AOSP][MULTIBOOT][TWRP][CWM] Turbo Kernel v2.0
anandbobby said:
Awesome Dan! Downloading the kernel now! Will report back after the installation!
[Edit]: Installation was smooth and successful. The ROM seems nice and very responsive. However display is fixed in landscape mode. Not able to get it back into portrait. Is this normal?
Click to expand...
Click to collapse
Hmmm. Which ROM are you using? Check for the file /system/bin/lidswitchd in a root explorer - if it's there, delete it and reboot. Let me know.
Sent from Xperia Play (R800a) with Tapatalk
Deleted the lidswitched file. Still the display is inverted.
Sent from MT25i using XDA premium
Device : NeoL
ROM : Turbo UI 4
Kernel: Turbo kernel 2
CosmicDan said:
Where is CM10.1 for Xperiia 2011 devices? There is none. Only CM10.
So even Camera libs or any other libs don't need changing? Strange. Looks like when I build MIUI I can just skip phoenix and edit build.prop to match Neo L then
Is it not working for you? I used championswimmers' init.semc.usb.rc (from Neo L ICS kernel) so it should come up as Neo L, let me know if it's broken.
Click to expand...
Click to collapse
im using this rom
http://forum.xda-developers.com/showthread.php?t=2096068
Re: [KERNEL][JB][ICS-AOSP][MULTIBOOT][TWRP][CWM] Turbo Kernel v2.0
anandbobby said:
Deleted the lidswitched file. Still the display is inverted.
Sent from MT25i using XDA premium
Device : NeoL
ROM : Turbo UI 4
Kernel: Turbo kernel 2
Click to expand...
Click to collapse
Problem is Turbo UI. Need to decompile framework and edit values XML. There is a rotation value set to 90 for Xperia Play, it needs to be 0 for devices without slide.
mido_fedo said:
im using this rom
http://forum.xda-developers.com/showthread.php?t=2096068
Click to expand...
Click to collapse
I don't know. I don't have a Neo V.
Sent from Xperia Play (R800a) with Tapatalk
dan, the tuch is not working in the kernel menu? any ida?
boot_phoenix_turbo-v2.0 this was what i used for my neo l.
[/COLOR]
Kn!ght L!fe said:
dan, the tuch is not working in the kernel menu? any ida?
boot_phoenix_turbo-v2.0 this was what i used for my neo l.
Click to expand...
Click to collapse
In kernel menu use regular volume up and down keys to navigate. Once you enter into TWRP recovery, touch works. :laugh:
Sent from MT25i using XDA premium
Device : NeoL
ROM : Turbo UI 4
Kernel: Turbo kernel 2
anandbobby said:
[/COLOR]
In kernel menu use regular volume up and down keys to navigate. Once you enter into TWRP recovery, touch works. :laugh:
Sent from MT25i using XDA premium
Device : NeoL
ROM : Turbo UI 4
Kernel: Turbo kernel 2
Click to expand...
Click to collapse
ya just found out that
Re: [KERNEL][JB][ICS-AOSP][MULTIBOOT][TWRP][CWM] Turbo Kernel v2.0
Kn!ght L!fe said:
dan, the tuch is not working in the kernel menu? any ida?
boot_phoenix_turbo-v2.0 this was what i used for my neo l.
Click to expand...
Click to collapse
Known issue, forgot to add calibration data for Phoenix device (same as play but I didn't copy to Neo L config).
When I find out how to fix the landscape issue I will post new version. Can somebody please try CM10 because Turbo UI is unofficial for Neo L.
Sent from Xperia Play (R800a) with Tapatalk
CosmicDan said:
Known issue, forgot to add calibration data for Phoenix device (same as play but I didn't copy to Neo L config).
When I find out how to fix the landscape issue I will post new version. Can somebody please try CM10 because Turbo UI is unofficial for Neo L.
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
its all right Dan :laugh: all this hard work, we can excuse tht :laugh: great work Dan. im on the ParanoidAndroid JB Rom now so far works good. :good:
DO THIS AT YOUR OWN RISK.
I AM NOT RESPONSIBLE IF YOU BRICKED YOUR DEVICE.
Do research and reading if you are uncertain about this rom.
Do not PM me about the ROM.
WHAT IS IT?
Xylon is fully transformed distribution for Android Devices. It is designed to take full advantage of the device’s hardware and to provide the user pure Android experience.
The team is constantly working on making things better for the users and is happy to do so. We, the team, believe that for one to experience the pure taste of Android, he/she should be provided with something which is fast, intuitive and fluid – That’s where we come in – To provide you that.
Xylon started as a part of the Fruits & Veggies (FNV) project, a community ROM for the Galaxy Nexus and is now set up individually but its roots are based on FNV. Remicks, the founder of the FNV – inspired Daniel MM (Daxmax, founder of Xylon) to build something that would make users love what they use. In Daniel’s words – “This is an FNV based ROM, not FNV. But it has the winds of FNV, and it has more spacious features around the Android world.”
-http://xylon.androidvenue.com/about
FEATURES:
Phone, Phablet, and Tablet UI
Customized Trebuchet Launcher
A lot of customization
Compiled with Google’s GCC 4.7 toolchain.
Linaro's compiler flags, O3 and Linaro string routine)
Kernel 3.0.66+
CWM 6.0.28
SuperSU
QUESTIONS AND ANSWERS
CHANGELOGS:
Look at XYAOSP source history for further changes, I will not post them.
02/27 – Repo synced, Initial build so there could be many bugs.
03/06 – Repo synced, kernel updated to 3.0.68 with new lowmemorykiller, font size increased a little in statusbar and Trebuchet, you can increase icon size to 120% in Trebuchet, gesture control in Trebuchet, new SuperUser (Koush's).
IMPORTANT NOTES: If you noticed null icons (no action icons) on the NavBar then you need to go to Settings > XY Tools > Navigation Bar > Menu (The vertical three dots) and Reset navbar icons/targets. For Navigation Ring to work, you need to clear data/data1 if you are on previous build.
TO DO LIST:
Lots of things
{
"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"
}
INSTRUCTIONS:
You need to do a full wipe (factory reset and wipe cache) if you are on a different ROM.
You need to wipe data1 and cache if you are SD booting.
You need to reinstall GAPPS after each ROM installation.
In the case you booted and all you see is black screen for a couple minutes, reboot to see if it's fix.
Initial booting can take several minutes.
Copy ROM/GAPPS into your Internal Storage on the device.
Reboot into recovery and install ROM from Internal Storage.
Full wipe can be done before or after installing ROM/GAPPS.
For SD booting, you need to make bootable SDCard first.
There are plenty of guides around.
INTERNAL ROM:
86b333d03739180e428e5cbb2cb9d706 *xylon_acclaim_2.1.1_06MAR2013_16_HD.zip
84ca9aeb88fad3ddcd127a216a34557a *xylon_acclaim_2.1.1_28FEB2013_01_HD.zip
SDCARD ROM: (Single boot) BOOT partition contents, boot.zip
134e175b18da509b37cf0897294214a6 *xylon_acclaim_2.1.1_06MAR2013_HD_SDC.zip
3b46595484586b0e0e99ca856fbb5ad7*xylon_acclaim_2.1.1_28FEB2013_HD_SDC.zip
INTERNAL GAPPS: *Might need to go to advance > fix permission in CWM before flashing GAPPS
4493696a11733e4e2a15d0026211963e *gapps-jb-20130301-signed.zip
c4a07a24e11448824b84e314600cd357 *gapps-jb-20121212-signed.zip
EXTERNAL GAPPS:
e2a80b77153a6bacd3df785742487ea3 *gapps-jb-20130301-signed-SDC.zip
36e9081e0dd29b67193d2db9441683c3 *cm-10.1-20121212-gapps-SDC.zip
RECOVERY: (TWRP 2.4.3.0 + CWM 6.0.2.8)
THANKS TO (CREDITS):
bauwks - Bootloader exploits
CYANOGENMOD
Source - https://github.com/CyanogenMod
Web - http://CyanogenMod.org
CM G+ - https://plus.google.com/+CyanogenMod
XYLON
Source - https://github.com/xyaosp
Web - http://xylon.androidvenue.com/
XYE G+ - https://plus.google.com/communities/102617491638136644864
Members:
Alex (AlexForTomorrow)
Arz Bhatia (arzbhatia)
Bluewall
Daniel MM (DaXmax)
David Vidal (Dorilife)
Varun Verma (D00mSlayer)
NOOK TABLET
Source - https://github.com/CMNookTablet, https://github.com/Kuzma30
Members:
Brandon Bennett (nemith)
Chris (chrmhoffmann)
fat-tire
Hashcode
Kuzemko Alexsandr (Kuzma30)
Kyrylo Mikos (mik9)
Rebell
KINDLE FIRE
Source - https://github.com/loosethisskin, https://github.com/KFire-Android
Members:
Aaron Davis (icemank121)
Andrew Dodd (Entropy512)
Hashcode
IngCr3at1on
JackpotClavin
Jacob (drkhd)
John Craig (x0xhellx0x)
Loosethisskin (twa_priv)
Markus Cisler (bl1nk)
Raymond Jay Golo (intersectRaven)
Scott Brady (sbradymobile)
Shujun
SGT7
Source - https://github.com/sgt7/android_packages_apps_Trebuchet
Members:
Angel666
Chirayu Desai (chirayudesai)
eaut
Humberto Borba (humberos)
jt1134
Koudai Aono (koxudaxi)
pulser
redrebel696
Scott Brady (sbradymobile)
techomancer
COMPILER
Source - https://github.com/succulent
Web - http://iamafanof.wordpress.com
HD (Succulent)
Questions and Answers
Want to clear cache manually?
Delete the dalvik-cache folder inside cache folder with root access & restart.
Is Jellybean running slow on your NT? It might be your SDCard.
microSD Card Benchmark Comparison — CrystalDiskMark
Why do I have to wipe data/factory reset?
Dirty installation can slow the OS and causes side effects due to residue files still on system.
Want to swap your internal storage (EMMC) to SDCARD?
Edit /system/build.prop, persist.sys.vold.switchexternal=0 to 1
My converted MP4/M4v isn’t working?
Use Handbrake 9.4. The current ducati firmware is outdated and doesn’t support newer MP4 codec.
How do I edit system files?
Use FileManager, settings>change access to root access, & click on lock icon, change to RO>RW
How do I take screenshot?
Hold power button + volume down
Where’s Developer options & Performance?
Click Build number several times.
Want to save battery?
Rename system/apps/phone.apk to phone.apk.bk
Change CPU performance to 800 MHz max feq. and use conservative, click set on boot
For better standby battery, go to Wifi Advanced settings > Keep Wi-Fi on during sleep > Only when plugged in
Where’s bluetooth/OTG/USB Host?
…
Do I need to install GAPPS?
Only when updating as the image comes with GAPPS
Yes, you do need to reinstall GAPPS after each update.
Don’t like Media Transfer Protocol (MTP) and want USB Mass Storage (UMS)?
Edit /system/build.prop, change persist.sys.usb.config=mtp,adb to mass_storage,adb
Older Mac might need http://www.android.com/filetransfer/
How to I view sdcard1 (SD card) with FileManager?
Go to Settings and change Access Mode to Prompt or Root.
Google Voice crashes?
Update Google Search
Don’t see folders or files when clicked on Internal Storage or SD card?
Refresh
Do I need to root the device for CM ROM?
Rooting is the ability to use superuser for root permission on a system.
Mainly for stock Android with no superuser.
All CM ROM come with superuser access.
How do I block OTA updates from BN?
You don’t need to. You are running CM software not BN.
How do I wipe data on sdcard?
The latest recovery (Orange theme) has an option “Wipe data1 on sdcard”, that is wipe P3 on sdcard.
It’s similar to factory reset, only that wipe data partition on the internal memory.
Boot animation is messed up?
Yes, for now.
What about tethering?
It’s removed since CM7, I couldn’t get to work with all the outdated patches.
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
http://forum.xda-developers.com/showthread.php?t=1369817
I am stuck in a recovery boot loop?
Flash this, flashable_fix_bootloop.zip, File>Download
GAPPS, stuck at Wi-Fi Connecting…?
Patient. Just wait up to a couple minutes.
Hulu Plus not working?
You need a cracked Hulu APK so search for it on XDA. Hulu works on stock ROM.
How do I increase animation speed?
In the developer options, change animation scale to none or 0.5x.
Succulent, this is awesome. I'll test it out myself
Re: [ROM] Unofficial Xylon Acclaim 2.1.1 [XYAOSP 4.2.2] [Nook Tablet]
Amazing!
Sent from my NookTablet using xda app-developers app
Imma test it out also. Fantastic!!
---------- Post added at 02:46 AM ---------- Previous post was at 02:45 AM ----------
After testing for about an hour, I can name a few problems I came across. First thing I noticed was the text and the icons. They were blurry and was an eye strain for me. Second minor problem but the Nav icons are smaller than on the other builds. I tried youtube and the first video I tried didnt work. Just show's play button.
Keep up the great work!!
I'll try this out, thanks.
Just to be clear, only the top link is for the actual rom right? The source links are just for reference? I assume.
Anyone try it yet?
postulio said:
I'll try this out, thanks.
Just to be clear, only the top link is for the actual rom right? The source links are just for reference? I assume.
Anyone try it yet?
Click to expand...
Click to collapse
The download link is under Internal ROM towards the middle of the post.
Used this ROM for a day, not bad.
Love the customization. To me though, it feels a little laggy. Also i have been having tons of trouble playing youtube videos on it, both on the website and through the app. they either dont start at all or crash (and i still hear the audio, lol). sometimes they simply wont load.
another observation is that pretty much all the 4.2 ROMs i've tried have pretty bad battery life when compared to 2.3. This is unfortunate but doesnt render the tablet unusable. I'd say if you charge it every night, it is fine. Leave the tablet overnight, without charging, with wifi on (although i know it goes into sleep) the battery drops from 85 to 35 in about 8-9 hours, which is awful.
Personally I am going back to PA 3.1 for now, but will check back if development progresses.
I tried out Xylon: for a first build it works really well and is very responsive (even though I am running it off SD). The couple of problems I ran across are the same one I recently encountered on some other ROMs: e.g., MX Player out-of-control when playing some video in HW mode (even when the Player is force-stopped the audio still keeps going), System-UI crashes when switching to Tablet-UI.
I think this ROM has a lot of potential and is really fun to use.
Whenever I adb devices from my PC to NT, it says devices offline, how can I connect my PC & NT? I found some other threat about new adb on 4.2.2 but they didn't help.
bingoz said:
Whenever I adb devices from my PC to NT, it says devices offline, how can I connect my PC & NT? I found some other threat about new adb on 4.2.2 but they didn't help.
Click to expand...
Click to collapse
You might find some helpful pointers at http://forum.xda-developers.com/showthread.php?p=35971559#post35971559.
Also, make sure that you do have the latest update of ADB (see http://forum.xda-developers.com/showpost.php?p=38118551&postcount=9).
FWIW, I re-flashed Xylon ROM with cm-10.1-20121212-gapps-SDC.zip — not only does Google auto-restore now works but also I no longer have the problem of “System-UI has stopped” when switching to Tablet-UI.
been using this for 4 or 5 days now, seems pretty good to me, battery life is a lil suspect, but ive just uopdated to 6th march version, so will see how this goes
CWM Backups
It may be I am using a dated CWM but my 6.0.2.8 version does not correctly calculate the MD5 sums. Anyone able to successfully do backups with MD5 sums ti help me know if the issue is mine or the ROMS?
Looks cool Im going to try flashing this rom today. Thanks for all the work you put into it.
RhinoNelson said:
It may be I am using a dated CWM but my 6.0.2.8 version does not correctly calculate the MD5 sums. Anyone able to successfully do backups with MD5 sums ti help me know if the issue is mine or the ROMS?
Click to expand...
Click to collapse
6.0.2.8 is a very recent if not the latest version of CWM.
How do you determine that "6.0.2.8 version does not correctly calculate the MD5 sums"?
CWM backups
digixmax said:
6.0.2.8 is a very recent if not the latest version of CWM.
How do you determine that "6.0.2.8 version does not correctly calculate the MD5 sums"?
Click to expand...
Click to collapse
When I run the backup, the last step performs the MD5 sum and it gives an error. I had this with a backup with a different ROM as well yesterday. I didn't retry so it could have been circumstantial. I don't have this ROM installed any longer so I can't attempt another backup of it.
RhinoNelson said:
When I run the backup, the last step performs the MD5 sum and it gives an error. I had this with a backup with a different ROM as well yesterday. I didn't retry so it could have been circumstantial. I don't have this ROM installed any longer so I can't attempt another backup of it.
Click to expand...
Click to collapse
FWIW, the couple of times I encountered "MD5 errors" in doing backup using recovery were when I had insufficient space in the sdcard's first partition ("/boot") to accommodate the size of the needed backup.
The Rom seems to think that /sdcard directory is in the external sd card, So I can't download files from the internet (web browser) with out a microsd, it gives me an error "says no such directory." Is this normal for the Nook Tablet, any way to get around that?
succulent said:
....
Want to swap your internal storage (EMMC) to SDCARD?
[*]Edit /system/build.prop, persist.sys.vold.switchexternal=0 to 1
jamesgg said:
The Rom seems to think that /sdcard directory is in the external sd card, So I can't download files from the internet (web browser) with out a microsd, it gives me an error "says no such directory." Is this normal for the Nook Tablet, any way to get around that?
Click to expand...
Click to collapse
Did you try this?
Sent from my ST27i
Click to expand...
Click to collapse