[KERNEL & ROM] [RAY] Ray / Stock-based: kernel/rom Repack by 4pda.ru team - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

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 !!

Related

[ROM] zerorom v0.4 (GSM/CDMA, CWM Install)

Hi everyone... here's my first crack at a custom ROM for the Xperia Play. And this is very beta. Once things get more solid, I'll make this first post a lot more proper. As it stands, this is for people who aren't worried about being on the edge.
Screenshots (click to enlarge)
{
"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"
}
Features:
Based upon official firmware R800i 4.0.A.2.368 UK
Supports GSM and CDMA Xperia Play models with a single build (testing needed)
SE Home launcher removed in favor of Launcher Pro.
DooMKernel v3 + Dalvik2Cache Hack
All DooMKernel features supported
Overclocking and Undervolting capable
AdamTT's X-Blue Theme + Reboot power menu
Blue Honeycomb bootanimation
Large APN list taken from latest version in Cyanogenmod
Bravia Display Engine v1
Ad blocking hosts file, combined from MVPS and yoyo
Swapped out official SE Camera for Camera Mod 7
All apks properly Zipaligned, auto zipalign all apks on boot
All apks PNG optimized
SQLite Vacuum at boot
Camera sounds except focus sound muted. Can set silent mode on phone for completely silent camera.
Switched main shell to bash from sh.
Added busybox.
Nano editor for use in terminal emulator, cannot be used by adb... yet.
New Android Market
New Google Maps hacked for global world-wide navigation
New Google Talk with front-facing camera support
Disabled annoying auto-brightness
Disabled annoying USB debugging notification when connected via USB with debugging turned on
CIFS/TUN kernel modules (untested)
Tons of SE default apps removed, including Whatsapp, Music Unlimited, Adobe Flash Player (market is far more up-to-date) and so much more.
Facebook deep integration removed, use FrAsErTaG's Facebook patch if you want it back - http://forum.xda-developers.com/showthread.php?t=1140540
SuperCharger memory management and loopy smoothness tweaks
/data partition has lots of space free.
Data, SMS, MMS, Wifi, Home button, back button, Google Voice Navigation all working.
Installation instructions:
I've been trying to get a proper flashable update.zip which would include the DoomKernel, however I have been getting bootloops, so for now, installing consists of restoring a Nandroid backup. This, of course, requires a kernel with CWM recovery, so you must already have DoomKernel installed at the moment.
These instructions will get much more properly fleshed out later on.
Quick and dirty steps:
1) Enter Recovery menu with preflashed DoomKernel.
2) Wipe all userdata
3) Wipe all caches
4) Wipe Dalvik Cache
5) Install the zerorom zip from your SD card.
At this point, reboot and you should be booting into the ROM. There's a good chance you'll see the boot logo two or three times before it boots properly. This is normal and no reason to be alarmed. This is basically the dalvik2cache and zipalign scripts running.
CDMA Users:
Install with the same build as below. Follow the same instructions. As long as you have not wiped /system when you attempt to install zerorom, it will detect that you are running on CDMA. It checks this by going by what your /system/build.prop says. If that file does not exist, installation could fail.
Installation failure when /system is wiped before install:
If you are missing /system/build.prop, you could write the following into a text file: "ro.product.device = R800x" for CDMA users or "ro.product.device = R800i" for GSM users. Then push this file to /system/build.prop. Then restart installation and you should be good.
Download:
V0.4 - http://www.multiupload.com/HUAY7FTIS7 - CDMA is in testing phase only!
V0.3 - http://www.multiupload.com/J3F7MPHJQZ
V0.2 - http://www.multiupload.com/3W86RKRKOM
V0.1 - http://www.multiupload.com/6H8EE0FMKY
Got a lot of plans in the future for this ROM. Let me know what you think if you take the time to try it out.
Changelog/Roadmap:
v0.5 - Update zips for each version from now on, startup script control, nano/bash included.
v0.4 - CDMA and GSM support in a single installation, hacked Google Maps 5.10.0 with worldwide navigation, loopy smoothness tweaks and V6 SuperCharger memory management scripts on startup. PNG optimized.
v0.3 - Restarted from scratch. Added Google Talk with video. Added new theme. Switched to Launcher Pro from ADW Launcher. Removed more apps. Added new bootanimation. Turned off auto-brightness settings. Turned off most camera sounds. SQLite vacuum on boot. Yet more stuff.
V0.2.1 - Readd Sony Ericsson settings application to fix Messaging app force close when attemping to enter its settings.
V0.2 - Removed Facebook, Sony Ericsson custom Facebook integration, Sony Ericsson sync clients, Sony Ericsson LiveView manager. Added romname/version to build.prop so it is displayed to the user.
V0.1 - Initial release.
Possible future plans and progress:
Single build working for both CDMA and GSM phones without manually installing another zip. - Done pending testing
More switchable user control over various things such as the muting of camera sounds, zipalign, dalvik2cache and many other options through a simple interface. - 10% complete
Add Screenshot function to power menu - Abandoned for now, screenshot intent was Cyanogenmod only?
Switch to Google DNS servers? - Initial look into it complete, reevaluating soon.
Apps2SD - Nothing done yet.
Various build.prop/performance tweaks - 50% complete
Use zerorom as the basis for a rom devoted towards the emulator/gamer - Nothing done yet, waiting for this ROM to be complete.
PNG optimization - 100% complete.
EDT Tweaks for status bar - Some initial looks into it complete, reevaluating soon.
SD Card speedup - Nothing done yet.
Alternate font - Nothing done yet.
Multiple themes - Nothing done yet.
720p playback with replacement of liboxmvdec.so - 100% - failed
Integrate Chainfire3D - Nothing done yet.
Centered clock, status bar changes? - Nothing done yet.
Hot reboot option integrated into reboot menu - Nothing done yet.
Confirmed bugs:
None known at the moment.
Credits, Links and Thank You's
AdamTT - X-Blue Theme, Reboot power menu mod
lpy - loopy smoothness tweak startup script
DooMLoRD - Bravia Engine for Xperia Play, DooMKernel + dalvik2cache hack
KHOLAT - USB debugging notification removal
Steve0007 - Modified Google Maps with world navigation
britoso - Modifed Google Talk with video chat, wifi restriction removed
GrainOsand + JaeKar99 - Electric Blue Honeycomb boot animation
kohllou - Camera sound removal guide
Zoop57 - Modded Camera app with R trigger shutter button
NielDK - CIFS and TUN kernel modules, disable auto-brightness tutorial
Cyanogenmod - Large APN list
dsixda - Android Kitchen, various tweaks and additions including adblocked host file
zeppelinrox - V6 SuperCharger antilag and memory fix script
Synergy ROM Team - Startup script inspiration, automatic zipalign, sqlite vacuum and general ideas
FreeXperia Team - Clockwork Mod Recovery, Cyanogenmod port to Xperia Play
NFHimself, Koush - Documentation of Edify scripting language for Clockworkmod Recovery
tommytomatoe - Android Utility for Linux
Apache Software Foundation - Subversion version control system
Alejandrissimo - Bootloader unlocking for sim-locked Xperia Play
FrAsErTaG + zero_1_2 + chevyowner - Xperia Play CDMA fixes
Logseman, AndroHero, OTOGY2002, FrAsErTaG, thomassafca - Inspiration, ideas, great ROMs and great forum members.
Reserved for future use.
Very good work,great Rom
I will try this tomorrow and report back.
Glad to see someone else making ROMs for this phone. Great work
Sent from my R800i using XDA Premium App
You should recruit Chevy to work on a CDMA version of your rom. He's becoming known for that.
Anyways, good luck.
I've been trying to get a proper flashable update.zip which would include the DoomKernel,
Click to expand...
Click to collapse
Don't go that way: in Sony's Xperia line for this year, kernels are not flasheable through recovery, because the recovery must be contained in the kernel. Thus, kernels must be flashed with fastboot, separate from the rest.
!
This looks good! its like all in one mod
I have most of the features though xD
Sent from my R800i using XDA App
urgh.. facebook *shudders* not quite as clean as i hoped your ROM would be still going to try it out for a while though. seems nice. good work!! ^_^
solitarymonkey said:
urgh.. facebook *shudders* not quite as clean as i hoped your ROM would be still going to try it out for a while though. seems nice. good work!! ^_^
Click to expand...
Click to collapse
Half the world uses that crap, so I can't blame him. I bet people would ***** if it was taken out.
Or did you mean something else?
Logseman said:
Don't go that way: in Sony's Xperia line for this year, kernels are not flasheable through recovery, because the recovery must be contained in the kernel. Thus, kernels must be flashed with fastboot, separate from the rest.
Click to expand...
Click to collapse
Is there any source for this info?
As for Facebook, I'm looking deeper into how tied it is to the other apps. It's definitely something that will probably disappear soon.
solitarymonkey said:
urgh.. facebook *shudders* not quite as clean as i hoped your ROM would be still going to try it out for a while though. seems nice. good work!! ^_^
Click to expand...
Click to collapse
no just another jackass that cant say thank you if you dont like facebook uninstall it simple ehh?
sounds badass man keep up the good work cant wait till i see a cdma version
I'm fully open to a CDMA version being available if someone wants to take up support for it as I don't have a CDMA Play myself.
id attempt it but i wouldnt know where to start but i can test i got a spare cdma play with an unlocked bootlader
zerojay said:
Is there any source for this info?
As for Facebook, I'm looking deeper into how tied it is to the other apps. It's definitely something that will probably disappear soon.
Click to expand...
Click to collapse
If that helps you some, in my old system image GP2Xperia I made Facebook in its wholeness disappear from the phone. It's just a couple of apk's, nothing to be worried about. However, you may want to prepare a Facebook-adding update.zip just in case.
Logseman said:
If that helps you some, in my old system image GP2Xperia I made Facebook in its wholeness disappear from the phone. It's just a couple of apk's, nothing to be worried about. However, you may want to prepare a Facebook-adding update.zip just in case.
Click to expand...
Click to collapse
I removed it completely as a test (along with SE Syncing tools and their custom FB stuff) and found that simply installing FB from the market brings back most of what you'd get anyways, so it'll be removed from the next version. Liveware Manager will also be removed since it can just be installed from the market.
edokassiah said:
no just another jackass that cant say thank you if you dont like facebook uninstall it simple ehh?
sounds badass man keep up the good work cant wait till i see a cdma version
Click to expand...
Click to collapse
i said thank you (though not in those 2 words), gave the dev a thumbs up, and am currently running the rom to test it out and feed back to the dev any issues (if any) there may be in this package. i was just merely pointing out that in my eyes, fb is bloat and (to me) not as clean as i'd hoped.
so far it is a good rom, funcional, and a very good start for the devs first play attempt in a very limited custom rom world (for the play, at the moment), and i greatly look forward to future releases
v0.2 is in the middle of uploading. Sorry, no update.zip to update to the new version yet. I'll start creating those soon.
SE Sync, SE Facebook, Facebook, LiveWare all removed. Added rom name/version to build.prop.
EDIT: Done uploading, link: http://www.multiupload.com/3W86RKRKOM
My facebook patch will work fine
Sent from my HTC Sensation Z710e using XDA App
This is awesome. been using it all morning and love it.
Keep up the good work

[KERNEL][MULTIBOOT GB/ICS/JB][TWRP][CWM][NEO L] Turbo Kernel v3.1

{
"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:

[KERNEL][MULTIBOOT GB/ICS/JB][TWRP][CWM][PLAY] Turbo Kernel v3.1.1

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?

[ROM][6.01][MOB30M][11/06/2016]xTraFactory Odex xTreMe Battery You Will Love I

{
"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"
}
xTraFactory
100% Stock Odex Factory IMG debloated from optional Gapps , Systemless Root and No Force Ecrypt
My name is Daniel Tucci, I am an Italian Developer, after great succes of my rom on Nexus 5 , share with you my work.
This rom is created on 100% stock factory.img with the intent to optimize extremely performance and battery consumption without altering the originality.
With xTraSmooth you will have a stable rom like the original factory.img of google, you can leave safely traveling with my rom without risking blocks or problems.
This is my daily rom for nexus 6 uploaded for you at the request of some xda users.
I plan to regularly update xTraSmooth and give support to all users if necessary.
No can add other features ex. advanced power menu,clear all recents, in official factory.img for the moment .
My ROM is a official Nexus 6 factory.img with maximium optimization.
Do not just read the build name, just my xTraSmooth currently offers a 100% stock-based on official factory.img, where they were introduced all optimizations possible without altering the originality and reliability.
Now I work with a Team of my community users and xda users for built all Nexus's xTra Rom.
This group of developers has been called xTraTeam.
You can read the ROM developer on build info on AFH.
xTraROMs Official Google Plus Community
xTraROMs Official Facebook Community
My xTra Rom's has 3 priority:
- Stability on long time.
- Speed
- Battery.
xTraFactory Odex
Features:
Android 6.01
xTraFactory MOB30M Shamu
- 100% Stock MOB30M 6.01 Factory.img debloated from optional's gapps.
- Stock MMB29K Kernel
- Disabled Force Encryption
- Reduced running services and improved ram usage
- 100% Clean System Aligned with new Systemless Root
- No Build Name this is a 100% Factory.IMG flashable ROM.
- Latest Suoersu included in the zip , auto root and patch stock kernel with new systemless Root.
- Fully Odex system/app , priv-app and data/app
- Super Fast and Stable 4 Daily Driver
- Disabled ADS on browser and apps
- Optimized Audio Power on Speaker and Headphones
- Compatibile with xposed framework
- Compatibile with all Layers themes
- Fully led control support with LightFlow
Data Wipe Factory Reset is required , without it layers not work properly , use titanium in future for backup your apps and your data apps.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
​
Bugs:
Ahha Ahha Ahha Is a joke .
No bug here.
This is a daily driver rom, stable as the stock, maybe even more.
**What is ODEX and DEODEX?
TL;DR:
Odex = More speed__Less customization
Deodex = Less speed__More customization
Extensive explenation:
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These odex files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applicationsdifficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating theworry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
I think that you like more speed and less customization (less costumization for dev because is to difficult mod an odex file) and for this reason you press thank and download my work!
Another explanation is this:
If you use a odex rom, you'll have also more space in data (this is important because if you don't have partition ext4 in sdcard, you won't have too free space), increase battery life, more stability and increase perfomance( the Rom is more faster to load system and app) but you can't modifie apk after odex (you can't mod program with classes.dex).
Infact ODEX is an OPTIMIZED-DEX and Android load system and app faster than deodexed (DEOPTIMIZED-DEX) app and system.
When you have a deodex file (a lot of roms are deodexed) you have File.apk in system/app and in data/dalvik-cache [email protected]@[email protected], but with odex file you have File.apk in system/app and File.odex in system/app
​
Advices And Tutorial For xTreme Battery Life and Increase touch response.
Increase Touch Response:
- Set all animations to developer options at 0.5 or disable it to substantially increase touch response;
To drastically increase the battery life:
The system and the kernel need some charging cycles / days of adjustment, Android finished its first installation starts to sync your phone with google server, load the images in the gallery, sync contacts and so on.
My nexus with this rom and FKU beta with power saving profile consumes with good coverage and wireless network,10% of battery with 1 hour SOT.
There are too many variables that affect the battery, cpu temperature, ambient temperature, humidity, mobile network signal, synchronization in the backgroud, applications in your device, so it would be extremely difficult to judge your consumption without knowing all these things.
How to reduce battery consumption xTraSmooth Rom.
1) CPU
To simplify the set-up of the CPU the application FKU integrates three custom profiles that allow you to automatically set all these parameters to suit your needs. However for those who wish Further, use another application or manually change these parameters I provide these simple advice.
- Undervolt, this practice serves to reduce the overall heat of exercise and consumption of the CPU.
A CPU that uses the correct current is still more stable compared to a CPU which uses the standard tables set with average values adapted to all CPUs.
Each CPU is different so you need to calculate their boards UV.
To calculate their boards UV is necessary from a global base of -25 or -50.
Working frequency by frequency by setting the same value as the minimum and maximum frequency and disabling start at boot is that the frequencies of the voltages.
Example set the frequency 300 MHz and 300 MHz as max as min, get off gradually with small steps -5mv until you find the limit, when you restart pinned the value of a piece of paper or on the notepad.
You will find the limit, now set 5/10 mv more and you will have your first value of the table UV.
Now proceed so for each frequency using a moment smartphone before you jump to conclusions.
These values can not be adapted to each kernel, but you will have to redo this procedure for each kernel. Without this you will have your tables UV ready and saved as in my case on google keep.
- Use a frequency that allows to work with a low voltage, in my case a frequency ranging from 1036 MHz (765mv) 1267 MHz (795mv)
- Hotplug limit work on Core 2, setting the use of the 4 Core when the load reaches 99%
- Touchboost on kernel using the touchboost set to values less than the maximum frequency, such as 1267 MHz maximum frequency and touchboost with values between 883 MHz and 960 MHz.
- Hi speed freq set the same frequency as the touchboost.
- Limit the GPU working frequency between 200 MHz and 320 MHz
2) Android
- Disable Geolocation
- Turn off system sounds
- Disable vibration to the touch and keyboard
- Disable adaptive brightness
- Use a brightness value between 5% and 10%
- Manually set in 2G if you are in areas with little signal and if necessary set airplane mode.
- Disable use mobile data and set 2G when using WiFi.
- Use a few applications that use push or remain active in the background, in my case use whatsapp, facebook stable, tapatalk and FKU beta.
- Do not change rom or kernel continuously will make continuous wipe system.
Android is that the kernel need a period of adaptation and some charge cycles to work properly.
- Use a few gapps to reduce app in sync automatically or disable synchronization of the app that you use in the shortest way, and that you do not need a synchronization between multiple devices in real time.
Many gapps have a web version app that saves space in SD and have less app in sync automatically.
- Deactivate Ok google hotword
- No close the app by recent, open and close the app to continued increases fuel consumption and reduces the fluidity of the system, lollipop has a system like iOS and works well with all the app open.
- Do not use task manager to free up RAM.
- Do not use the Clean master or other background task manager , plan to avoid unnecessary.
- Do not use snapdragon battery guru or similar programs that promise lower fuel consumption.
- Avoid heavy 3D games and games continuously running type clash of clans, Simpson, etc. etc.
3) Battery
- With modern lithium battery is not advisable to go below 20%
- Lithium batteries like short courses of charge, does not always pay full charges from 0 to 100, but prefer partial charges.
- 1 charge cycle means from 0 to 100 so if charge the battery from 50% to 100% will have carried out a half charge cycle.
- You can even connect the battery to charge a 10% charge, I repeat the lithium batteries do not damage unplugging and plugging the power supply but working with infeririore charge to 20%.
- Perform a complete cycle 2/3 times in 1 year from death and charge off up to 100%.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
​
Delta Update:
When is possible i'll release a small delta update, to avoid that you have to download the full rom, recommended xTraSmooth Updater for best OTA experience. They allow the upgrade of your xTraSmoth on the go in 4G \ 3G.
Installation instructions:
Instructions From xTraSmooth M and StocK M
-Dirty flash on you rom, the script perform an automatic wipe cache.
FOR LOLLIPOP ROM USERS IS NECESSARY START FROM ANDROID M FACTORY OR UPGRADE YOUR BOOTLOADER AND RADIO.
INSTRUCTIONS
- FLASH TWRP
- FLASH DIRECTLY MY ROM WITHOUT ADVANCED WIPE WITH ANDROID M ARE UNNECESSARY AND WITH THE WIPE YOU BREAK THE ROM INSTALLATION
- BOOT
Downloads:
xTra Folder
https://www.androidfilehost.com/?w=files&flid=24488
3Minit battery for xTraSmooth for info go here :
http://forum.xda-developers.com/showthread.php?p=63357199
For download my ROM and update it over the air install :
xTraSmooth Updater Free
https://play.google.com/store/apps/details?id=com.xtrasmooth.free
xTraSmooth Updater is the best way to update your xTraSmooth ROM over the air. It is fully updated with latest Material Design and has a very clean and user-friendly UI.
Features:
★ Automatically checks for update after a user-set interval
★ Push notification when update is available
★ Automatically checks if you need a delta update or a full ROM installation
★ Reboot into recovery for manual flashing
★ Changelog for all the changes in the latest ROM version
Donations
If you like my work offer me an Italian Coffee, it will help me to stay awake and work for you.
A special thank you to those who appreciate my work and decided to contribute to the project.
Donations
A special thank you to those who appreciate my work and decided to contribute to the project.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
​
Acknowledgements
First my work friend
- Prempal Singh my xTraSmooth Partner Great App Developer
- Cristiano Spada aka @CriGio Best Themes Developer and app icon designer
- Google
- Francisco Franco
- flar2
- sshafranko
- chdloc
- Team Cyanogen
- Adr990
- badboy47
- david279
- GtrCraft
- guerreromanuel
xTraSmooth Signature
MADE IN ITALY
TIGHT
This is the longest OP I have ever seen, in my whole entire life. Excellent info. Sounds like a solid rom for the community. Thanks for sharing.
Sent from my SinLess Shamu
Hi Daniel. Thank you for the bringing your ROM to shamu! I see this has Franco kernel. Is it decrypted/encryptable?
is this encrypted?
He says his ROM had more than 30k downloads.... Impossible... I have not seen one yet with that many.... Anyone vouch for that?
theellucidone said:
He says his ROM had more than 30k downloads.... Impossible... I have not seen one yet with that many.... Anyone vouch for that?
Click to expand...
Click to collapse
Why do we care? Test and try is all I can say.
Sent from my Nexus 6 using XDA Free mobile app
ooooooo.... another rom to flash... i love it!!!
Sent from my Nexus 6
dadoc04 said:
ooooooo.... another rom to flash... i love it!!!
Sent from my Nexus 6
Click to expand...
Click to collapse
That's the spirit! But it won't download for me.
Sent from my Nexus 6 using XDA Free mobile app
markwebb said:
That's the spirit! But it won't download for me.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
working here homie
Sent from my Nexus 6
So far it's downloading fine here. 8 min left.
theellucidone said:
He says his ROM had more than 30k downloads.... Impossible... I have not seen one yet with that many.... Anyone vouch for that?
Click to expand...
Click to collapse
Don't hate if you see the date that is from the n5 which runs great with this ROM.
Guys the xTraSmooth_T1 rom on folder is old test rom sended to beta tester, moved now on other folder.
The final rom with all features is in uploading, you can flash it on this test rom, i have shared folder, the final rom zip name is xTraSmooth_N6 _1.0
My PC upload it at home with slow connection.
The rom for security is encripted , you can Change the encription by selinux changer or by xTraSmooth Updater.
For users with xTraSmooth test version , dirty flash the full version on it after upload is complete....
daniel84cs said:
Guys the xTraSmooth_T1 rom on folder is old test rom sended to beta tester, moved now on other folder.
The final rom with all features is in uploading, you can flash it on this test rom, i have shared folder, the final rom zip name is xTraSmooth_N6 _1.0
My PC upload it at home with slow connection.
The rom for security is encripted , you can Change the encription by selinux changer or by xTraSmooth Updater.
For users with xTraSmooth test version , dirty flash the full version on it after upload is complete....
Click to expand...
Click to collapse
Thanks for the info! I just decrypted today so am hesitant to go through that process again in the same day. I will test soon however.
Sent from my Nexus 6 using XDA Free mobile app
markwebb said:
Thanks for the info! I just decrypted today so am hesitant to go through that process again in the same day. I will test soon however.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I dirty flash on my Nexus 20/30 times on the day, not is a problem only replace the file on your system folder....
On the test version not is all features.
Only a base for test if it boot....
Decripted the kernel or rom, the encription is on kernel not is possible remove the encription of entire rom.
great will dirty flash over the beta version as thats been running great since yesterday
strikerdj2011 said:
great will dirty flash over the beta version as thats been running great since yesterday
Click to expand...
Click to collapse
Thanks for the feed, test if work all features. DT2W work...???....Battery percentage work...???
Now work with my partner for app support, The next download only from app, with ora support........I release small update called delta update for update the rom in 4G over the air....
ROM is uploaded yet?
Do I need to Flash the Radio Zip mentioned in OP?
acheney1990 said:
Do I need to Flash the Radio Zip mentioned in OP?
Click to expand...
Click to collapse
No no not flash modem, update the OT this night, i have copied the N5 OT....
Guys app is ready, no more download in folder, OTA is ready...
App sended to google, now you can download this for rom downloading....
Is final free app sended to google....
https://www.dropbox.com/s/weepb28gboub75j/xTraSmooth_Updater_Free_1.01[1].apk?dl=0
Coming soon on playstore...

[ROM][6.01][MTC19V][09/06/2016]xTraFactory Odex xTreMe Battery You Will Love It

{
"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"
}
xTraFactory
100% Stock Odex Factory IMG debloated from optional's Gapps , Systemless Root and No Force Encrypt
My name is Daniel Tucci, I am an Italian Developer, after great succes of my rom on Nexus 5 and Nexus 6 , share with you my work.
This rom is created on 100% stock factory.img with the intent to optimize extremely performance and battery consumption without altering the originality.
With xTraSmooth you will have a stable rom like the original factory.img of google, you can leave safely traveling with my rom without risking blocks or problems.
This is my daily rom for nexus 5x uploaded for you at the request of some xda users.
I plan to regularly update xTraSmooth and give support to all users if necessary.
No can add other features ex. advanced power menu,clear all recents, in official factory.img for the moment .
My ROM is a official Nexus 5x factory.img with maximium optimization.
Do not just read the build name, just my xTraSmooth currently offers a 100% stock-based on official factory.img, where they were introduced all optimizations possible without altering the originality and reliability.
Now I work with a Team of my community users and xda users for built all Nexus's xTra Rom.
This group of developers has been called xTraTeam.
You can read the ROM developer on build info on AFH.
xTraROMs Official Google Plus Community
xTraROMs Official Facebook Community
My xTra Rom's has 3 priority:
- Stability on long time.
- Speed
- Battery.
xTraFactory Odex
Features:
Android 6.01
xTraFactory MMB29M Angler
- 100% Stock MMB29M 6.01 Factory.img debloated from optional's gapps.
- Stock MMB29K Kernel
- Disabled Force Encryption
- Reduced running services and improved ram usage
- 100% Clean System Aligned with new Systemless Root
- No Build Name this is a 100% Factory.IMG flashable ROM.
- Supersu 2.65 included in the zip , auto root and patch stock kernel with new systemless Root.
- Fully Odex system/app , priv-app and data/app
- Super Fast and Stable 4 Daily Driver
- Disabled ADS on browser and apps
- Compatibile with xposed framework
- Compatibile with all Layers themes
Data Wipe Factory Reset is required , without it layers not work properly , use titanium in future for backup your apps and your data apps.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
​
Bugs:
Ahha Ahha Ahha Is a joke .
No bug here.
This is a daily driver rom, stable as the stock, maybe even more.
**What is ODEX and DEODEX?
TL;DR:
Odex = More speed__Less customization
Deodex = Less speed__More customization
Extensive explenation:
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These odex files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applicationsdifficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating theworry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
I think that you like more speed and less customization (less costumization for dev because is to difficult mod an odex file) and for this reason you press thank and download my work!
Another explanation is this:
If you use a odex rom, you'll have also more space in data (this is important because if you don't have partition ext4 in sdcard, you won't have too free space), increase battery life, more stability and increase perfomance( the Rom is more faster to load system and app) but you can't modifie apk after odex (you can't mod program with classes.dex).
Infact ODEX is an OPTIMIZED-DEX and Android load system and app faster than deodexed (DEOPTIMIZED-DEX) app and system.
When you have a deodex file (a lot of roms are deodexed) you have File.apk in system/app and in data/dalvik-cache [email protected]@[email protected], but with odex file you have File.apk in system/app and File.odex in system/app
​
Advices And Tutorial For xTreme Battery Life and Increase touch response.
Increase Touch Response:
- Set all animations to developer options at 0.5 or disable it to substantially increase touch response;
To drastically increase the battery life:
The system and the kernel need some charging cycles / days of adjustment, Android finished its first installation starts to sync your phone with google server, load the images in the gallery, sync contacts and so on.
My nexus with this rom and FKU with power saving profile consumes with good coverage and wireless network,10% of battery with 1 hour SOT.
There are too many variables that affect the battery, cpu temperature, ambient temperature, humidity, mobile network signal, synchronization in the backgroud, applications in your device, so it would be extremely difficult to judge your consumption without knowing all these things.
How to reduce battery consumption xTraSmooth Rom.
1) CPU
To simplify the set-up of the CPU the application FKU integrates three custom profiles that allow you to automatically set all these parameters to suit your needs. However for those who wish Further, use another application or manually change these parameters I provide these simple advice.
- Undervolt, this practice serves to reduce the overall heat of exercise and consumption of the CPU.
A CPU that uses the correct current is still more stable compared to a CPU which uses the standard tables set with average values adapted to all CPUs.
Each CPU is different so you need to calculate their boards UV.
To calculate their boards UV is necessary from a global base of -25 or -50.
Working frequency by frequency by setting the same value as the minimum and maximum frequency and disabling start at boot is that the frequencies of the voltages.
Example set the frequency 300 MHz and 300 MHz as max as min, get off gradually with small steps -5mv until you find the limit, when you restart pinned the value of a piece of paper or on the notepad.
You will find the limit, now set 5/10 mv more and you will have your first value of the table UV.
Now proceed so for each frequency using a moment smartphone before you jump to conclusions.
These values can not be adapted to each kernel, but you will have to redo this procedure for each kernel. Without this you will have your tables UV ready and saved as in my case on google keep.
- Use a frequency that allows to work with a low voltage, in my case a frequency ranging from 1036 MHz (765mv) 1267 MHz (795mv)
- Hotplug limit work on Core 2, setting the use of the 4 Core when the load reaches 99%
- Touchboost on kernel using the touchboost set to values less than the maximum frequency, such as 1267 MHz maximum frequency and touchboost with values between 883 MHz and 960 MHz.
- Hi speed freq set the same frequency as the touchboost.
- Limit the GPU working frequency between 200 MHz and 320 MHz
2) Android
- Disable Geolocation
- Turn off system sounds
- Disable vibration to the touch and keyboard
- Disable adaptive brightness
- Use a brightness value between 5% and 10%
- Manually set in 2G if you are in areas with little signal and if necessary set airplane mode.
- Disable use mobile data and set 2G when using WiFi.
- Use a few applications that use push or remain active in the background, in my case use whatsapp, facebook stable, tapatalk and FKU beta.
- Do not change rom or kernel continuously will make continuous wipe system.
Android is that the kernel need a period of adaptation and some charge cycles to work properly.
- Use a few gapps to reduce app in sync automatically or disable synchronization of the app that you use in the shortest way, and that you do not need a synchronization between multiple devices in real time.
Many gapps have a web version app that saves space in SD and have less app in sync automatically.
- Deactivate Ok google hotword
- No close the app by recent, open and close the app to continued increases fuel consumption and reduces the fluidity of the system, lollipop has a system like iOS and works well with all the app open.
- Do not use task manager to free up RAM.
- Do not use the Clean master or other background task manager , plan to avoid unnecessary.
- Do not use snapdragon battery guru or similar programs that promise lower fuel consumption.
- Avoid heavy 3D games and games continuously running type clash of clans, Simpson, etc. etc.
3) Battery
- With modern lithium battery is not advisable to go below 20%
- Lithium batteries like short courses of charge, does not always pay full charges from 0 to 100, but prefer partial charges.
- 1 charge cycle means from 0 to 100 so if charge the battery from 50% to 100% will have carried out a half charge cycle.
- You can even connect the battery to charge a 10% charge, I repeat the lithium batteries do not damage unplugging and plugging the power supply but working with infeririore charge to 20%.
- Perform a complete cycle 2/3 times in 1 year from death and charge off up to 100%.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
​
Installation instructions:
Instructions From xTraSmooth M and StocK M
-Dirty flash on you rom, the script perform an automatic wipe cache.
FOR LOLLIPOP ROM USERS IS NECESSARY START FROM ANDROID M FACTORY OR UPGRADE YOUR BOOTLOADER AND RADIO.
INSTRUCTIONS
- FLASH TWRP
- FLASH DIRECTLY MY ROM WITHOUT ADVANCED WIPE WITH ANDROID M ARE UNNECESSARY AND WITH THE WIPE YOU BREAK THE ROM INSTALLATION
- BOOT
Downloads:
xTra Folder
https://www.androidfilehost.com/?w=files&flid=45572
Donations
If you like my work offer me an Italian Coffee, it will help me to stay awake and work for you.
A special thank you to those who appreciate my work and decided to contribute to the project.
Donations
A special thank you to those who appreciate my work and decided to contribute to the project.
Guys if you like my work and dedication in helping all of you, to consider making a small donation, I am working day and night to provide the best for all us.
All donations will be appreciated, just press on donate button..
​
Acknowledgements
First my work friend
- Prempal Singh my xTraSmooth Partner Great App Developer
- Cristiano Spada aka @CriGio Best Themes Developer and app icon designer
- Google
- Francisco Franco
- flar2
- sshafranko
- chdloc
- Team Cyanogen
- Adr990
- badboy47
- david279
- GtrCraft
- guerreromanuel
xTraSmooth Signature
MADE IN ITALY
Hi! Ciao!
Nice to see an italian rom on xda.
I'll try it for sure in the next few days. Just a question on the installation.
If i am on another custom rom, i have to do a full wipe before flash your rom? Or am i wrong?
BartLuke94 said:
Hi! Ciao!
Nice to see an italian rom on xda.
I'll try it for sure in the next few days. Just a question on the installation.
If i am on another custom rom, i have to do a full wipe before flash your rom? Or am i wrong?
Click to expand...
Click to collapse
I would say yes all ways good to clean install
I guess we have to flash unsu zip if we are on system root
Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
@daniel84cs
Bit of confusion here. The title states MMB29K as the build number, so does the file at your download page. But, no such build number exists for this device, it does for the Nexus 5X, but not the Nexus 6P.
Just flashed with Cataclysm mod all working great
Thanks op
Heisenberg said:
@daniel84cs
Bit of confusion here. The title states MMB29K as the build number, so does the file at your download page. But, no such build number exists for this device, it does for the Nexus 5X, but not the Nexus 6P.
Click to expand...
Click to collapse
Was wondering the same as i see it has listed Bullhead as the build name too.
Heisenberg said:
@daniel84cs
Bit of confusion here. The title states MMB29K as the build number, so does the file at your download page. But, no such build number exists for this device, it does for the Nexus 5X, but not the Nexus 6P.
Click to expand...
Click to collapse
Think his copied and paste from his x5 thread lol and forgot to change a few things
I'm on Cataclysm myself over stock (systemless root) with elemental x kernel and it's great!
So you flashed the mod over this rom? Is there any difference? Is it snappier?
Just looking for a quick opinion. Thanks in advance
jaythenut said:
Just flashed with Cataclysm mod all working great
Thanks op
Click to expand...
Click to collapse
bkrickles said:
I'm on Cataclysm myself over stock (systemless root) with elemental x kernel and it's great!
So you flashed the mod over this rom? Is there any difference? Is it snappier?
Just looking for a quick opinion. Thanks in advance
Click to expand...
Click to collapse
not had long enough to tell the difference but had to wipe to get it to work dirty didnt work
Thanks, appreciate the response.
Of course I understand you need to run with it a while before forming an opinion.
I'm working and won't get a chance to flash until probably late tonight so if you have anything to add ,would love to hear it.
Thanks again
jaythenut said:
not had long enough to tell the difference but had to wipe to get it to work dirty didnt work
Click to expand...
Click to collapse
Long time no see, glad your in the Nexus6 P forum! Cool
Does it support CM Themes? Just read layers. So no go. Thanks otherwise.
Gesendet von meinem Nexus 6P mit Tapatalk
Thanks to all guys , fixed the name of title and zip name , sorry I have copyed by Bullhead page and zip name. This is my first ROM for Nexus 6P , bug I grant continuate supports for this Great Device.
Inviato dal mio Nexus 6 utilizzando Tapatalk
I'm getting nfc and play store crashes when installing xposed. Anyone else with xposed working?
Elemenopee said:
I'm getting nfc and play store crashes when installing xposed. Anyone else with xposed working?
Click to expand...
Click to collapse
Working fine on my side, I'm using v79.
Elemenopee said:
I'm getting nfc and play store crashes when installing xposed. Anyone else with xposed working?
Click to expand...
Click to collapse
Yes work perfect , make a Wipe data from recovery if your problem persist....
Inviato dal mio Nexus 6 utilizzando Tapatalk
Wow!! Great news!!! Had you roms for months in my old Nexus 6. I'll wait for January security fixes to return.
Enviado desde mi Nexus 6P mediante Tapatalk
Hi guys, I tried searching the OP for it but does anyone know if Android pay is supported in this ROM?
Ramenn00dl3s said:
Hi guys, I tried searching the OP for it but does anyone know if Android pay is supported in this ROM?
Click to expand...
Click to collapse
its stock with systemless root so i would think yes it does

Categories

Resources