Kernels work on any phone type. Doom's GB kernel (gsm) had wifi issues, other than that, you're good.
Sent from my Xperia Play using xda app-developers app
Sent from my Xperia Play using xda app-developers app
fastboot erase system
fastboot erase userdata
Hmm strange, I dunno then. So you (1) flashed the FXP-Turbo boot.img (the original one, not 180 mod), then (2)
then (3) Installed AOKPlay ROM, and it's just stuck? ADB hasn't started (no logcat possible)?Code:fastboot erase system fastboot erase userdata
Is it working on AOKPlay for anyone else?
Yea I'm on the latest aokplay and I restored from nandriod I made with lupus kernel. I wiped system, userdata and no problems here.
Turbo1a kernel released.
- Wifi modules will automatically be installed to the system if needed (does some smart checking)
- BFS, BFQ and Fudgeswap removed. They all hurt performance and shouldn't be used (I did a lot of testing)
BFS is a sad story since it took me many days to port Basically it's not optimized for Android, it causes thread starvation on many background processes and I noticed very poor/unstable performance with media and sync when using BFS.
- Default I/O scheduler set to CFQ (it's specifically optimized for android and faster than V(R) in most cases)
- New boot logo and Recovery graphics in style of new Turbo UI ROM
- 180MB on /system modified version replaced with 200MB version, needed for new Turbo UI ROM
- Less aggressive dbus_input ramping on intellidemand
Awesome, but could you upload a version with the old boot logo as well?
Sent from my Kindle Fire
Kernel works great, its really nice to have options when it comes to govnrs. Any chance of bringing voltage control to the kernel? I always found this to be the best way of maximizing battery life while maintaining performance; its really the only thing I miss about GB (as doomkernel had this capability).
I'm 90% sure there is already vdd in sysfs.
EDIT: Nope, guess not. I'll think about it, it doesn't really do anything useful and would take a lot of my time. The focus on this kernel is performance and not battery life, so if you want that maybe try a different kernel.
EDIT2: VDD sysfs interface coming in next version
When you're saying performance and not battery life I hope you're not saying half a day of juice. Other than that I want to ask you if there are any issues with NeoDroid?
thq you very much
I'm confused about the different sized partition message. Does this kernel change partition sizes, and thus everyone needs to run those commands? I'm coming from Mjolnir.
Those commands only nid to be ran if ur changing the partition size.. Btw the smaller sys partition is for turbo ui.. So there is no need to run those commands.. Unless u want to use turbo ui.
Sent from my Xperia Play using xda premium
Your kernel rocks bro. I'm using it with FXP 133 and it simply rocks. With medium usage I got 2 days+ of battery life. Right now it's at 65% left and it will probabily die today but haven't had this much battery life from this phone from like never
- Intellidemand tweaks - better performance and powersavings (fine-tuning for R800 hardware)
- zRAM now using "Snappy Compression" by Google. Much faster but slightly worse ratios. I'm using 40% zRAM myself and it's great :eek:
I just tested with FPSe... as you know the dev implemented the touchpad on ICS previously (using onGenericMotionEvent) and the touchpad recognition is fine.
As the mod uses this method to send the event to the "onTouchEvent", as GB does, then everything is fine with the kernel because the event is reaching the onGenericMotionEvent as it should
Edit: My app didn't FC with me. It's kind weird
Other thing, dude:
Usually, FPSe don't recognize the touchpad if the ALWAYS ACTIVATED behavior is ON. I just tested it, and the touchpad worked OK, even with this option. It'a looks like a framework problem. Probably some fix implementation issue, or maybe something changed in the sources that make the fix don't work anymore... I need to check it
r13
---
- New: Two-stage RAMDisk (easier dev'ing, safer booting) - big thanks to championswimmer for backporting the idea from 2012 series
- New: Slot 4 added
- New: Boot Menu completely redone
- New: Ability to switch Recovery between TWRP or CWM
- New: Option for custom image sizes in Slot creation
- New: Boot will detect if SDCard has an error and will launch repair (adds a few milliseconds to boot, don't stress)
- New: Tweaks and Mods menu - TSDX (Turbo SD-eXt) Install/Remove
- New: Tweaks and Mods menu - Set urandom as default entropy device (not a seeder) (enabled by default)
- New: Tweaks and Mods menu - Option to deasec (decrypt) apps on startup, will greatly help with App2SD issues
- New: Tweaks and Mods menu - Switch ROM between MTP (media) or UMS (mass_storage).
- New: White LED "thinking" indicators when Multiboot/tweaks is casting its' sorcery
- Removed: Entropy seeder binary (made obsolete by new urandom device method)
- Improved: Slot creation now verifies for free space and tells you what space will be left
- Improved: Reliability of created images (requires new image generation)
- Improved: ICS-AOSP support (Log spam, Video and GTalk FC's)
- Improve: [Repair Tool] Fix Permissions will always try to mount sd-ext (fixes sd-ext/Link2SD enabled slots)
[COLOR=DimGray][B][COLOR=black]TODO[/COLOR][/B] [strike] - Improve: [TWRP] Factory Wipe no longer formats sd-ext (you can do that in another option)[/strike][/COLOR]
- Improve: [TWRP] Various minor layout things (better spacing and placement to avoid accidental touches)
[COLOR=DimGray][COLOR=black][B]TODO[/B][/COLOR] [strike] - Fix: [TWRP] Backup and restore supports compressed or uncompressed option again[/strike][/COLOR]