{
"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"
}
I am NOT responsible for any damage done to your device, your neighbor, or any other things you like/hate.
Introduction:
@myself5 and I were in need for a custom stock kernel to mess with. Since all the available Options were not fitting our needs, or gave us bad experience on some aspects, and we knew about Zombie Kernel from Tom, we decided to start working on that. So I brought up support for the Z5, we ported Kexec to it, updated it to 224 and added various things. Since the kernel gave us very good experiences, we decided to make it accessible to the public.
About:
This Kernel is based on @Tommy-Geenexus Zombie Kernel. He was ok with us continuing/porting his projects, so myself5 and I started to create the "oshmoun Myself5 Zombie Kernel" aka OM5Z Kernel.
Features and Commit History:
Check 2nd Post!
Installation Instruction:
THIS DOES ONLY WORK ON UNLOCKED BOOTLOADER!
You can either flash the provided boot.img via fastboot, or flash the zip in recovery.
Additional Information:
The Kernel is underclocked by default. Both Cluster are underclocked to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements. However, due to public demand, V2 features the ability to disable the underclock (in case you need to make some baked Eggs real quick, whatever). All you need to do is run this code after boot (Kernel Adiutor has the abilty to execute scripts at startup, just a reminder).
Code:
echo "0:4294967295 1:4294967295 2:4294967295 3:4294967295 4:4294967295 5:4294967295 6:4294967295 7:4294967295" > /sys/module/msm_performance/parameters/max_cpu_freq
What it effectively does, is resetting the max clock limit for each core to the default (unset) values, allowing you to set whatever frequency (from the ones available ofc) you want.
Download:
OM5Z Kernel (Release Versions)
dl.myself5.de
OM5Z Kernel (Testing Versions)
testing.myself5.de
Thanks/Credits:
Tommy-Geenexus - You can guess why
myself5 - for obvious reasons
FreeXperia Team (especially Jerpelea) - for too many things!
CarbonRom Team - for too many things!
phaseburn - for being a good friend and helping me with almost everything !
infected_ - for help with SM!
If I forgot you, please tell me.
If you think we deserve a donation, I won't stop you
To Donate to Tommy-Geenexus:
To Donate to Myself5:
Thanks a lot to those who have donated!
Additional Information:
Some stock kernels require different Recovery Images than AOSP Kernels. We set an end too this, and fixed init_sony, rather than using some very outdated software which somehow works. This means, you might need to use a different recovery with this kernel if you're currently on a "stock" recovery. We're hoping that other stock kernel devs adapt our solution, so we can set an end to the old scripts.
XDA:DevDB Information
OM5Z Kernel, Kernel for the Sony Xperia Z5 Compact
Contributors
oshmoun, Myself5, Tommy-Geenexus
Kernel Special Features:
Version Information
Status: Stable
Created 2016-06-25
Last Updated 2016-07-16
Latest Version: V2.0
Changelog:
Version 1:
Add kexec-hardboot
ramdisk: use init_sony, no outdated bootrec scripts
ramdisk: fix USB on Stock when using MultiROM
Remove broken Sony MHL driver
Update to 32.2.A.0.224
Merge caf/LA.BF64.1.2.2_rb4.40
Various CVE Fixes
Initial Z5 and Z5C bringup, based on Zombie Kernel with these features
Bug fixes for touchscreen / fingerprint / scheduler drivers
Stripped unnecessary debug nodes, legacy code and disabled KSM
Turquoise LED when EOC is reached (when battery is fully charged)
CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)
Calibrated JDI Novatek Panel to 6500K Color Temperature and 2.2 Gamma
Tomtom-Codec Digital Speaker-, Mic- and Cam-mic-Control
Underclocked both Cluster to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements
Version 2:
Ability to disable the underclock (added on public demand) See OP for instructions
Removed TomTom Audio
Update to 32.2.A.0.253
Update init_sony
include DRM Fix by @tobias.waldvogel
Add support for sumire_dsds (E6633 and E6683). Thanks to @tOrNadO™ for testing
For a detailed Changelog, check the Github Commit history:
https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z/commits/
[KERNEL][Stock 224][Z5C][6.0.x]OM5Z Kernel
Tried to flash this in twrp, but it fails. Downloaded again and tried to flash but still fails
I have stock rom with androplus kernel
I think that should be done a tutorial for the stock users...
Enviado do meu E5823 através de Tapatalk
mele80 said:
Tried to flash this in twrp, but it fails. Downloaded again and tried to flash but still fails
I have stock rom with androplus kernel
Click to expand...
Click to collapse
Can you please say what the error message was? also, maybe your download was corrupt. You can redownload and see if that helps.
I just tried flashing the zip in twrp and it works.
[KERNEL][Stock 224][Z5C][6.0.x]OM5Z Kernel
Zip signature verification failed
Error installing zip file
Flashing from adb worked
This kernel include pacthes from here http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 ?
There is any tutorial to flash this kernel?
Can i flash it up on the stock rom and stock recovery?
Enviado do meu E5823 através de Tapatalk
arhangel78ru said:
This kernel include pacthes from here http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 ?
Click to expand...
Click to collapse
yes "RIC off" and "DRM patch" are included.
jdcchora1533 said:
There is any tutorial to flash this kernel?
Can i flash it up on the stock rom and stock recovery?
Click to expand...
Click to collapse
As mentioned in the thread title, this is for .224, so obviously you can flash it on stock rom.
Not sure what you mean with stock recovery though.
Trying to install the zip file with TWRP 3.0.2 and got this error
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/(folder where i have the zip)
What i am doing wrong?
regards
fridlack said:
Trying to install the zip file with TWRP 3.0.2 and got this error
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/(folder where i have the zip)
What i am doing wrong?
regards
Click to expand...
Click to collapse
Does your folder have weird characters or spaces in the name? Please try moving the zip to another directory.
oshmoun said:
Does your folder have weird characters or spaces in the name? Please try moving the zip to another directory.
Click to expand...
Click to collapse
I try to move to internal storage root folder and same result [emoji21]
fridlack said:
I try to move to internal storage root folder and same result [emoji21]
Click to expand...
Click to collapse
Which TWRP 3.0.2 recovery are you using? I use oshmoun's MultiROM TWRP, and it works very well! (You don't need to install or use the MultiROM part of it.)
Thanks for your great work. I ran into an issue with root acting weird after kernel install. It actually messed up binary folders. I have no idea how but apps were getting root denial with this awesome kernel.
Intsallation went ok with twrp 3.0.2.0. So no issues there.
Have you guys noticed this kind of behaviuor with the kernel?
Sent from my E5823 using XDA-Developers mobile app
I see the underclocked cores and I'm curious about battery life improvement... someone?
Triflot said:
Which TWRP 3.0.2 recovery are you using? I use oshmoun's MultiROM TWRP, and it works very well! (You don't need to install or use the MultiROM part of it.)
Click to expand...
Click to collapse
I am using this revovery http://forum.xda-developers.com/showthread.php?t=3334568 and xpower 3.0 rom with stock kernel
Is the update script checking if the device is correct? Maybe xpower rom have something changed?
Enviado desde mi E5823 mediante Tapatalk
fridlack said:
I am using this revovery http://forum.xda-developers.com/showthread.php?t=3334568 and xpower 3.0 rom with stock kernel
Is the update script checking if the device is correct? Maybe xpower rom have something changed?
Enviado desde mi E5823 mediante Tapatalk
Click to expand...
Click to collapse
ok sorry about that. I think I should update the recovery thread to mention that it's not maintained anymore.
Yes there is a device check, but usually if that fails then it would tell you what it was expecting (in this case that'd be suzuran, E5823, E5803).
Could you please try the multirom recovery. It's basically TWRP only with multirom additions. The multirom recovery works pretty well regardless if you have multirom installed or not.
Good to see another kernel in the panorama! As soon as i get the latest MM update, i'll surely test it.
However i'm interested in the standby consumption during night, did you test it? every stock based kernel-rom combination seems to be plagued by high drainage even in offline mode without particular wakelocks
oshmoun said:
ok sorry about that. I think I should update the recovery thread to mention that it's not maintained anymore.
Yes there is a device check, but usually if that fails then it would tell you what it was expecting (in this case that'd be suzuran, E5823, E5803).
Could you please try the multirom recovery. It's basically TWRP only with multirom additions. The multirom recovery works pretty well regardless if you have multirom installed or not.
Click to expand...
Click to collapse
After installing the multi recovery ( via fastboot, zip file had the same problem) I install zip kernel without problems, thanks so much!
But now I have a new problem, can not update supersu binaries, got an error, I tried to install stable and beta supersu and same result with both, anyone with the same problem?
fridlack said:
After installing the multi recovery ( via fastboot, zip file had the same problem) I install zip kernel without problems, thanks so much!
But now I have a new problem, can not update supersu binaries, got an error, I tried to install stable and beta supersu and same result with both, anyone with the same problem?
Click to expand...
Click to collapse
Yep. I have exact the same issue. Su wants to update binary without success. It doesn't matter which su I use.
Sent from my E5823 using XDA-Developers mobile app
Related
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
You can also watch a video which shows it in action.
Click to expand...
Click to collapse
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Click to expand...
Click to collapse
NOTES
I'm not responsible for anything.
I just compiled it, the hard work was done by the people in the credits section. Please support them.
Please post bugs
Installation with Sony Stock ROM
Your bootloader must be unlocked for this to work.
Make a backup
Flash custom boot.img (fastboot flash boot boot_stock_windy.img / fastboot flash boot boot_stock_pollux.img
Install multirom.zip
Installation with OmniROM
Make a backup
Install OmniRom
Install multirom.zip
more detailed
Make a backup from your recovery
Install a Rom with kexec-hardboot support from recovery
Install multirom.zip from TWRP
Reboot to recovery
Install second ROM from recovery (Advanced -> MultiROM -> Add ROM)
You now have a Xperia Tablet Z with multiboot
Source
MultiROM: https://github.com/pollonamid/multirom
Kernel: https://github.com/omnirom/android_kernel_sony_apq8064
TWRP: https://github.com/XperiaMultiROM/android_bootable_recovery
Click to expand...
Click to collapse
CREDITS
Tasssadar - MultiROM and modified TWRP
Olivier - MultiROM port to Xperia Z
Olivier and Everyone else mentioned here - KEXEC hardboot porting to Xperia Z and Tablet Z
skiwong 20 - building builds while I was away
OmniROM
Click to expand...
Click to collapse
Downloads
Pollux
multirom.zip
Pollux_windy
WARNING! - I don't own this device, so it's untested.
multirom.zip
XDA:DevDB Information
MultiROM v31x pollux, Tool/Utility for the Sony Xperia Tablet Z
Contributors
pollonamid
Version Information
Status: Testing
Created 2014-08-26
Last Updated 2015-02-15
Reserved
Changelog:
26/08/2014 - First release
16/09/2014 - No need to install recovery seperately
21/09/2014 - fixed list rom-view in recovery
Reserved
Supported internal ROMs:
Pollux_Windy
OmniROM
PAC-Man (thanks to skiwong20)
Sony Stock 10.5.1.A.0.xxx Flash this kernel
Pollux
OmniROM
PAC-Man (thanks to skiwong20)
Sony Stock 10.5.1.A.0.xxx Flash this kernel
nice to see multirom here too!
i´ve build it for my own (pollux windy _ aosb) but aosb code isn´t
ready yet, so i decided to hold it till aosb 1.3.7 will be released!
NICE WORK!!!
c0llal0 said:
nice to see multirom here too!
i´ve build it for my own (pollux windy _ aosb) but aosb code isn´t
ready yet, so i decided to hold it till aosb 1.3.7 will be released!
NICE WORK!!!
Click to expand...
Click to collapse
Wow, awesome!
Hi,
Installed multirom yesterday, so far its working, but when i try to add a rom in twrp (then advanced-multirom) i see a screen with something like what type of rom do you want to install, then i select android and then its stuck. No next button or something noting works anymore and I need to reset
Sent from my HTC One_M8 using XDA Free mobile app
Dutchdeveloper said:
Hi,
Installed multirom yesterday, so far its working, but when i try to add a rom in twrp (then advanced-multirom) i see a screen with something like what type of rom do you want to install, then i select android and then its stuck. No next button or something noting works anymore and I need to reset
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I know this bug. Multirom-TWRP doesn't work in landscape currently. You have to change it to landscape. So, go to Settings -> Screen and set rotation to 90.
Hi !
Nice to see a working Multiboot.
Could you help me ?
My SGP311 is flashed with newest Omnirom nightly with "normal" TWRP,
What exactly i have to do to Update to Multirom and to install cm11 as second android ??
Can i do all steps without PC ?
phillipssat said:
Hi !
Nice to see a working Multiboot.
Could you help me ?
My SGP311 is flashed with newest Omnirom nightly with "normal" TWRP,
What exactly i have to do to Update to Multirom and to install cm11 as second android ??
Can i do all steps without PC ?
Click to expand...
Click to collapse
Hi
I updated the installation instructions and made the more detailed. Hope it helps.
Currently it's not possible to install without a pc, sorry.
pollonamid said:
Hi
I updated the installation instructions and made the more detailed. Hope it helps.
Currently it's not possible to install without a pc, sorry.
Click to expand...
Click to collapse
Does it split main partition to install 2nd ROM separately? Or where second ROM stores it data?
pollonamid said:
Hi
I updated the installation instructions and made the more detailed. Hope it helps.
Currently it's not possible to install without a pc, sorry.
Click to expand...
Click to collapse
@pollonamid I flashed your boot for pollux_windy but the recovery is the normal TWRP without multirom, any ideas what i'm doing wrong?
//can you share recovery img so i can flash like this? --> http://teamw.in/project/twrp2/185
Rootk1t said:
Does it split main partition to install 2nd ROM separately? Or where second ROM stores it data?
Click to expand...
Click to collapse
No. It stores the data in the multirom folder on the internal sd-card. You can read more in the original multirom thread http://forum.xda-developers.com/showthread.php?t=2011403
@pollonamid
can i request assistance here? I'm doing something wrong? Can you post recovery.img?
EsEnZeT said:
@pollonamid
can i request assistance here? I'm doing something wrong? Can you post recovery.img?
Click to expand...
Click to collapse
Here you go. Had to compile it. I will upload a new boot.img later, too. Could be that I uploaded the false one. Sorry.
https://www.androidfilehost.com/?fid=23622183712465782
Hi !
Whats about this App ?
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
Does it run on SGP-311 with your Multiboot ??
pollonamid said:
Here you go. Had to compile it. I will upload a new boot.img later, too. Could be that I uploaded the false one. Sorry.
https://www.androidfilehost.com/?fid=23622183712465782
Click to expand...
Click to collapse
That means, this is OK for pollux-windy and your link on your first posting is not OK ??
Better to Update your first posting ??
phillipssat said:
Hi !
Whats about this App ?
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
Does it run on SGP-311 with your Multiboot ??
Click to expand...
Click to collapse
Didn't try yet. Try it and tell us if it works, please.
phillipssat said:
That means, this is OK for pollux-windy and your link on your first posting is not OK ??
Better to Update your first posting ??
Click to expand...
Click to collapse
Thank you for pointing this out. I just forgot it. lol
https://www.androidfilehost.com/?fid=23622183712465782 is a recovery.img. Don't flash it to boot partition.
I updated the OP with the new link.
What happens after a nightly omnirom update which updates the recovery (TWRP) ??
Update 2014-09-04 will change TWRP !?
http://omni.cmxlog.com/4.4/pollux_windy/
Do i have to flash your files again ??
phillipssat said:
What happens after a nightly omnirom update which updates the recovery (TWRP) ??
Update 2014-09-04 will change TWRP !?
http://omni.cmxlog.com/4.4/pollux_windy/
Do i have to flash your files again ??
Click to expand...
Click to collapse
Currently, yes, if it is your main rom. If it is a secondary rom, no.
I found Sony merged Z2 source into Z3 source like unified kernel!
So I build it for D6502/D6503 23.0.1.A.3.12 and it worked fine
Note I don't use Z2 for daily driver now,
so I can only confirm it's working without SIM.
It should be OK with SIM, though.
[UPDATE 3/1]
I sold my Z2, so I can't check if new versions work on Z2.
{
"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"
}
* banner by MysticEnforcer
Download from official website
Changelog
What is FOTA kernel recovery?
[/B]
NOTE: This is old info as we can use official recovery partition on newer ROM.
Xperia doesn't have recovery partition for user,
but we have FOTA kernel partition for OTA.
Since we have to unlock bootloader and OTA won't work on unlocked,
we can re-use useless FOTA kernel as recovery partition using Dees-Troy's "extract_elf_ramdisk".
With FOTA kernel recovery, you can update your recovery without updating kernel.For example, TeamWin provides TWRP images of FOTA kernel for Z2:
http://teamw.in/project/twrp2/232You can flash images to FOTA kernel by fastboot command like
Code:
fastboot flash recovery fotakernel.img
To enter into FOTA recovery, press power key when LED is on.
How to restore DRM functions?
When you unlock bootloader you will lose X-Reality, noise reduction and so on,
but you can restore them!
Original thread is here, but I updated steps for Z2.
1. Download zip from original thread
* Choose KitKat version (for 4.4) or Lollipop version (for 5.0)
2. Place zip in internal or external storage of your device
3. Reboot into recovery and do Factory Reset
4. Reboot into flashmode and flash FTF with Flashtool
Any FTF is OK, but of cource use FTF for same version you are using now.
Wipe: Check APPSLOG and CACHE
Exclude: Don't check
5. Close Flashtool, unplug and plug your phone and reopen Flashtool, then relock bootloader
Click BLU icon to show relock button and click it.
6. Flash FTF (same as 4.)
7. Close Flashtool, unplug and plug your phone and reopen Flashtool, then unlock bootloader
Click BLU icon to show unlock button and click it.
8. Reboot into fastboot mode and flash my kernel
9. Reboot into recovery and install DRM Restore zip
10. Reboot
11. Done!
After doing this, do not restore old data since it will revert DRM restore.
You can restore system with recovery and use Titanium Backup or something to restore app data.
Note: When you flash new ROM (not kernel), you must flash DRM Restore zip.
If you get "net::ERR_NAME_NOT_RESOLVED" when connecting xda,
please disable PrototypeProtection with Titanium Backup or something similar.
How to use F2FS?
Read this:
http://forum.xda-developers.com/xperia-s/s-development/tutorial-migrate-filesystem-to-f2fs-ext4-t3004755
Kernel sources
https://github.com/WedyDQ10/android_kernel_sony_msm8974ac
Credits
DooMLoRD
Faux123
Dees_Troy & TeamWin
Phil3759
Myself5
glocklee
pec0ra
and many other people involved in Z3 development
XDA:DevDB Information
AndroPlusKernel for Z2, Kernel for the Sony Xperia Z2
Contributors
AndroPlus, [#APK_cont]
Source Code: https://github.com/WedyDQ10/android_kernel_sony_msm8974ac
Kernel Special Features:
Version Information
Status: Stable
Created 2014-12-28
Last Updated 2016-04-09
Flashing now
Thanks for the work, will give it a try soon
existenz 4.0.0 is based on stock 4.4.4, so it's supposed to work?
can you share your OC voltages? i recently switched to abricot, now 2,2ghz is unstable at 900mV …
So far so good, boot without any issues and network working fine, I'll report back if I find any issues =D
---------- Post added at 10:50 AM ---------- Previous post was at 10:47 AM ----------
kuhno said:
Thanks for the work, will give it a try soon
existenz 4.0.0 is based on stock 4.4.4, so it's supposed to work?
can you share your OC voltages? i recently switched to abricot, now 2,2ghz is unstable at 900mV …
Click to expand...
Click to collapse
I'm also using Existenz 4.0.0 and stable at the moment, haven't tried over-clocking yet, but at 2265 Mhz, it is working fine.
kuhno said:
Thanks for the work, will give it a try soon
existenz 4.0.0 is based on stock 4.4.4, so it's supposed to work?
can you share your OC voltages? i recently switched to abricot, now 2,2ghz is unstable at 900mV …
Click to expand...
Click to collapse
It's older 4.4.4 firmware 23.0.1.A.0.167, so compatibility will not be 100% but it will work.
I set -36mV for all since I had reboot when I was using Z2 as daily driver and set -48mV.
Just for reference, I'm setting -84mV on Z3 and working well.
Great to see more development on kernel. Already download but not tried yet since I'm currently testing abricot kernel. Can you update with 167 kernel later sir?
Everything apears to work fine
Exept that that you have said isnt working, aka 3.2Ghz OC
If you need a bootsplash ill make one for you unless your capable of that your self @AndroPlus
Edit- OOM Values apear messed up and cause app crashes in certain apps
kumbangdesa said:
Great to see more development on kernel. Already download but not tried yet since I'm currently testing abricot kernel. Can you update with 167 kernel later sir?
Click to expand...
Click to collapse
Update?
23.0.1.A.3.12 is the newest firmware for D6503
I can't revert kernel source only for .167, so I won't make it.
Anyway, it will work well on .167 since hugoprh said it's working on .167 based ROM.
Envious_Data said:
Everything apears to work fine
Exept that that you have said isnt working, aka 3.2Ghz OC
If you need a bootsplash ill make one for you unless your capable of that your self @AndroPlus
Click to expand...
Click to collapse
Thanks, but I have to *force* loading of custom bootsplash on newer kernel and I think it takes some seconds on boot.
It should be one or two seconds, but I prefer shorter booting time.
Oh. Sorry sir. My bad. I don't know that 3.12 is newest than 167.
No. Unfortunately it is not working on ExistenZ 4.0.0 based on 167. Bootloop.
Down reverting would be awesome...
This kernel did work on stock .167, 3.9, 3.12 very well. Reboots when PimpmyZ1 is opened or any other rooted app is opened.
Ahh then it depends on the su permissions.
Is it possible to fix?
The Peterle said:
No. Unfortunately it is not working on ExistenZ 4.0.0 based on 167. Bootloop.
Down reverting would be awesome...
Click to expand...
Click to collapse
I will try this week too in order to confirm incompability.
But dual recovery still works?
NO, dual recovery wont work
This is ot, but how did you done the theming of statusbar, navbar like lolipop i already asked several times noone respond
I'm on eXistenZ and I confirm that dual recovery is working.
Kernel triggers pink led and Sony logo
Dual recovery triggers green led and a vibration with black screen but worked.
NetSkill said:
This is ot, but how did you done the theming of statusbar, navbar like lolipop i already asked several times noone respond
Click to expand...
Click to collapse
I'm using a xposed module, Flat Style Colored Bars
http://forum.xda-developers.com/xposed/modules/flat-style-colored-bars-t2925521
Is there a hidden frequencies or because I'm in .167?
I only see 2.9GHz as highest freq but pimp my ROM says the opposite, there is two more steps 3.0GHz and 3.1GHz
Jhon998 said:
Is there a hidden frequencies or because I'm in .167?
I only see 2.9GHz as highest freq but pimp my ROM says the opposite, there is two more steps 3.0GHz and 3.1GHz
Click to expand...
Click to collapse
It's known issue.
http://forum.xda-developers.com/z3/devs-only/overclock-2-89ghz-t2962012
Testing!.. I don't like intellimm with intellithermal and intelliplug with OC CPU 2.5Ghz and GPU 657mhz, for games is so slow, maybe for save battery, on antutu benchmark I had 26870 points. But I like Smartass V2 with intellithermal and intelliplug with OC CPU 2.5Ghz and GPU 657mhz, on antutu benchmark I had 41862 points. Great!! my best score (I was testing Abricot Kernel and I had 39100 points with fast hotplug and Smartass V2). and I/O Scheduler SIO with 4096 on SD-Card and eMMC in both kernels.
Excellent work!.. Now I will testing the battery, and the battery with screen on.
Introduction:
Welcome to the official XDA thread for NeoKernel, a standalone, feature-rich and highly optimized custom kernel that will push your phone to its limits!
{
"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"
}
Disclaimer:
By downloading and installing this kernel, you agree that I cannot be held responsible for any damage caused to your device while installing or using it. Please keep in mind that it's YOU who chose to do these modifications to your device!
Also, be aware that improper usage of kernel features can cause serious damage to your device! Only use the features below if you know what you're doing!
NeoKernel Features:
Based on latest CAF kernel sources (LA.AF.1.1.c1)
Compiled with ArchiToolchain 4.9 and several Cortex-A9 optimizations
Overclocking up to 1.62 GHz
Underclocking up to 162 MHz for maximum battery life
User-customizable CPU Voltage driver (thanks to faux123)
Intelliactive and IntelliMinMax CPU governors (thanks to faux123)
In-kernel Thermal Driver (thanks to franciscofranco)
SIO and FIOPS IO schedulers
F2FS (Flash-Friendly File System) support (Performance comparison vs EXT4)
FauxSound support for maximum audio gain control (thanks to faux123)
Latest TWRP recovery, including a Materialised TWRP theme by z31s1g
Good to know:
NeoKernel will override any currently installed recovery on your FOTAKernel partition. That means, recoveries installed via Xperia Recovery Manager or similar apps will be replaced with the latest TWRP that is included in this kernel.
During installation, NeoKernel will recursively set a UID of 1023 for your internal storage. If you happen to use a ROM that expects a 2800 UID (which is quite unlikely, actually) and want to uninstall the kernel, make sure to flash the uninstaller zip from "Downloads" section after re-flashing your ROM zip.
The sources used to build this kernel can be found here.
Requirements:
Unlocked bootloader (Obviously )
A CM12.1-based ROM (CM12 is not tested yet)
Installation:
If your ROM includes CM recovery, fastboot flash the boot.img from kernel zip first!
Boot into recovery
Flash latest NeoKernel build (check "Downloads" section)
Reboot
Downloads:
Latest NeoKernel build: Link (Last updated: Sep 29)
Uninstaller zip: Link (Restores SONY's default storage permissions)
Uninstallation:
To uninstall NeoKernel, just reflash your current ROM.
If you face storage issues after uninstallation, also flash the uninstaller zip from "Downloads" section.
Changelog:
- 20150929:
Fixed missing recovery splash screen
- 20150824:
Initial release
If you like my work and want to support me, please hit that thanks button, give some positive feedback or consider a small donation for my efforts.
XDA:DevDB Information
NeoKernel, Kernel for the Sony Xperia V
Contributors
WhiteNeo
Source Code: https://github.com/WhiteNeo-/kernel-msm
Kernel Special Features: Check "Features" section!
Version Information
Status: Stable
Created 2015-09-05
Last Updated 2015-10-01
Reserved for a future tutorial on optimizing the kernel for battery life or performance. :good:
I've been waiting for this
Thank you, master!
I cannot flash this zip in Cynogenmod Recovery. I got this message.
Install Failed
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
Edit:
I cannot find the solution for above problem
So I copied modules folder 24 files to system and flashed your kernel via Flashtool
Currently using ROM : Resurrection Remix 5.5.3
draganz said:
I cannot flash this zip in Cynogenmod Recovery. I got this message.
Edit:
I cannot find the solution for above problem
So I copied modules folder 24 files to system and flashed your kernel via Flashtool
Currently using ROM : Resurrection Remix 5.5.3
Click to expand...
Click to collapse
Actually you can't flash anything with CyanogenMod Recovery
Flash boot.img from zip with fastboot. then flash zip with TWRP
Aria.A97 said:
Actually you can't flash anything with CyanogenMod Recovery
Flash boot.img from zip with fastboot. then flash zip with TWRP
Click to expand...
Click to collapse
I copied zip modules folder files to correct path in system and set permission, flashed kernel via FlashTool. Do I really need to flash again this neo kernel zip?
Update:
I flashed zip again.
Then I suggest OP need to update install instructions for the CynogenMod Recovery also. [emoji4]
Sent from my Xperia V using Tapatalk
My ROM SElinux status is Enforcing. Do I need to change it to Permissive? I really don't know this option. But I saw Neo's CM12.1 ROM using Permissive option.
If you don't mind, can you describe the difference of this Enforcing and Permissive option?
Sent from my Xperia V using Tapatalk
draganz said:
Then I suggest OP need to update install instructions for the CynogenMod Recovery also. [emoji4]
Click to expand...
Click to collapse
Done. Instructions should be more clear now.
draganz said:
View attachment 3463364
My ROM SElinux status is Enforcing. Do I need to change it to Permissive? I really don't know this option. But I saw Neo's CM12.1 ROM using Permissive option.
If you don't mind, can you describe the difference of this Enforcing and Permissive option?
Sent from my Xperia V using Tapatalk
Click to expand...
Click to collapse
It's a security feature in Linux that allows only certain known files to be executed, if enabled.
Permissive is the development mode, more or less. You see possible denials in logs but the security feature itself is disabled.
If you want to use Xposed, Viper4Android or a similar mod, you need permissive SElinux.
Nice work I wanted to make a smiliar kernel but you were faster than me
I had a week with NeoKernel.... and I'm forced to go back to Resurrection's own Kernel.
I'm on Resurrection 5.5.3 and it does not want this kernel.
I had several soft reboots during this week and can not connect them to any combined reasons.
Setting 162MHz as the lowest did give me pain. Sometimes it took 4-5 seconds to get the elements of the front screen, going in to the apps list took another 4-5 secs.
So I raised it back to 384. And no led. I had no led activity with this kernel.
Today I had two black deaths... I had to remove the battery.
So... I think Neo Kernel and Resurrection ROM just do not like each other.
I tried all the ROMs, but stayed on Resurrection as somehow Lux doesn't work on PAC, ICP or Carbon, but DU and Res. But the sound doesn't work on last updates of DU....
Great job Neo, but had to go back to "stock".
stirlitz99 said:
I had a week with NeoKernel.... and I'm forced to go back to Resurrection's own Kernel.
I'm on Resurrection 5.5.3 and it does not want this kernel.
I had several soft reboots during this week and can not connect them to any combined reasons.
Setting 162MHz as the lowest did give me pain. Sometimes it took 4-5 seconds to get the elements of the front screen, going in to the apps list took another 4-5 secs.
So I raised it back to 384. And no led. I had no led activity with this kernel.
Today I had two black deaths... I had to remove the battery.
So... I think Neo Kernel and Resurrection ROM just do not like each other.
I tried all the ROMs, but stayed on Resurrection as somehow Lux doesn't work on PAC, ICP or Carbon, but DU and Res. But the sound doesn't work on last updates of DU....
Great job Neo, but had to go back to "stock".
Click to expand...
Click to collapse
Can anyone confirm the led issues?
I might have to include the lights hal from my cm12.1 builds in this kernel zip.
stirlitz99 said:
I had a week with NeoKernel.... and I'm forced to go back to Resurrection's own Kernel.
I'm on Resurrection 5.5.3 and it does not want this kernel.
I had several soft reboots during this week and can not connect them to any combined reasons.
Setting 162MHz as the lowest did give me pain. Sometimes it took 4-5 seconds to get the elements of the front screen, going in to the apps list took another 4-5 secs.
So I raised it back to 384. And no led. I had no led activity with this kernel.
Today I had two black deaths... I had to remove the battery.
So... I think Neo Kernel and Resurrection ROM just do not like each other.
I tried all the ROMs, but stayed on Resurrection as somehow Lux doesn't work on PAC, ICP or Carbon, but DU and Res. But the sound doesn't work on last updates of DU....
Great job Neo, but had to go back to "stock".
Click to expand...
Click to collapse
I am also using Resurrection Remix.
But I haven't faced any reboots.
also I haven't faced black death issue. I think you done some misconfiguration with the kernel.
I really like Neo kernel. Because of recovery and kernel tweaks. My only issue is battery draining. Beacause Resurrection Remix kernel got 3 hours screen time and neo kernel got maximum 2.15hours with undervolting. Can someone suggest best governor and i/o ?
WhiteNeo said:
Can anyone confirm the led issues?
I might have to include the lights hal from my cm12.1 builds in this kernel zip.
Click to expand...
Click to collapse
lights are working. Sometimes doesnt work. It also happened in Resurrection Remix kernel also. [emoji4]
Sent from my Xperia V using Tapatalk
draganz said:
I am also using Resurrection Remix.
But I haven't faced any reboots.
also I haven't faced black death issue. I think you done some misconfiguration with the kernel.
I really like Neo kernel. Because of recovery and kernel tweaks. My only issue is battery draining. Beacause Resurrection Remix kernel got 3 hours screen time and neo kernel got maximum 2.15hours with undervolting. Can someone suggest best governor and i/o ?
lights are working. Sometimes doesnt work. It also happened in Resurrection Remix kernel also. [emoji4]
Sent from my Xperia V using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback!
I recommend sio scheduler for battery life, also reduce max cpu clock to 1200MHz (if you can afford a minor decrease in performance) and optimize your voltages.
Using IntelliMM governor here, with great effects on battery life.
Thread updated with the latest NeoKernel from my new CM12.1 build. Includes the previously missing recovery splash screen. If you don't miss it, there's no need to upgrade.
you mean now all your cm12.1 from now on will have the NeoKernel? cuz previously I had found difference in the kernels provided here and in previous (sep 9) 12.1 build!
saved-j said:
you mean now all your cm12.1 from now on will have the NeoKernel? cuz previously I had found difference in the kernels provided here and in previous (sep 9) 12.1 build!
Click to expand...
Click to collapse
This standalone NeoKernel is acutally just the extracted kernel files from my CM12.1 builds.
THANKS
{
"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"
}
OMNIROMUNOFFICIAL
He guys. I managed to find the time to port Omni to the z5c. Since it compiled, booted and works well (except camera) I thought I would upload to share. My goal being that we would have greater choices available adding to Stock, CM and AOSP roms. Note: This is not a developer thread. I'm just sharing this because it worked and others might be interested.
About Omni:
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality. https://omnirom.org/
BIG THANKS to...
@humberos - for creating the first omni device tree (that I know of) for the kitakami family. (my suzuran dev tree is largely his work)
@CTXz - for all the work he and the kitakamy dev team have done/will do for CM that will find its way in to the omni flavour of aosp.
@superR - I used his kitchen to make the zip file with sparse dat .img
The Sonyxperiadev team for releasing their sources to the public
The good..
Compiled with latest camera and vendor blobs provided by Sonyxperiadev.
Full working omni features
- Comes with latest TWRP packed in the kernel
- Advanced reboot menu - boot directly in to twrp or boot-loader, or reboot and hold up when led turns purple)
- Omni switch
-Advanced power menu (like kernel auditor)
The not so good..
Camera is slow.
- Colours are inverted on screen for main camera but pictures are fine in photo viewer.
- Colours are fine on screen for front camera but inverted heavy blue tinge in photo viewer.
Security in settings F/C (there is no trustzone for CM yet, when they reverse sonys binary and include it in their code I will kang it )
No fingerprint detection/ firmware (yet - this will be reversed from sony at some point as well.)
-Bluetooth reported to have the same limited functionality as AOSP.
-Root: The ramdisk.img patcher within systemless SU installer is detecting that Omniboot.img is already patched/rooted when its not, so aborts, thus at this stage we cant get full root. (Im working on this)
If anyone is interested in building Omnirom for the z5c let me know and Ill push my device tree and provide a link.
Here is the twrp installable zip for omni. Do NOT install this on another device other then the E5823
Do a factory reset/full wipe in twrp before you install. Make sure wou have GAPS and the latest SU zips ready to go as neither are included.
https://mega.nz/#!kkZRTb5Z!i96cGUNUztTAATQ8mkkv0ivcQI9aOqErZNjgVqNFoAE
Enjoy.
Kernel source is:
https://github.com/omnirom/android_kernel_sony_msm.git
Device tree/s :
https://github.com/joeisgood99/TWRP_device_sony_Omni-suzuran_MM.git
https://github.com/omnirom/
Reserved
wow finally,gonna transfer from cm to it
EDIT:no way to dirty flash from cm,android.phone will crash,will do clean flash.Camera seems better than cm one,keep going!
Really thank you! Will try soon!
Not sent by me!
Best of luck for your project and thank you!
Sent from my E5803 using XDA-Developers mobile app
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Edit : deleted duplicate post.
mangusmeister said:
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Click to expand...
Click to collapse
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Awesome work mate! Always good to have another ROM to choose from
Joeisgood99 said:
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Click to expand...
Click to collapse
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
mangusmeister said:
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
Click to expand...
Click to collapse
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Joeisgood99 said:
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Click to expand...
Click to collapse
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
Click to expand...
Click to collapse
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Does Bluetooth work?
civicsr2cool said:
Does Bluetooth work?
Click to expand...
Click to collapse
Same errors as in cm13.
mangusmeister said:
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
Click to expand...
Click to collapse
LolaPalocz said:
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Click to expand...
Click to collapse
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Joeisgood99 said:
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Click to expand...
Click to collapse
Good luck!!!
Got time to do my own testing with SU.2.7.1
The error Im getting is that su installer detects that the stock omni boot.img is already su patched....
Stay tuned.
Initiated as a personal work for my own use I have compiled from scratch this Rom based on
and derived from SLIMRoms including some LineageOS mods.
Finally, I've decided to share it in case someone might be interested.
Credits to the magnificent team of SlimRoms.
Product Highlights:
Android 6.0.1
Security updates to March 2019
New Kernel Dhollmen integrated, without OC for now
Rooted
Many changes over Slim's base:
Pixel Launcher
Chromium web browser
Amaze file manager
NewPipe YouTube player (without GPlay services)
Sound recorder
Google wallpaper application
Old CyanogenMod's calculator
Navigation bar button's icon
More ...
Available downloads:
Tab2 10.1 & 7.0 inches espresso 3G version for tablets with SIM card
Tab2 10.1 & 7.0 inches espresso Wi-Fi version for tablets without SIM card
Gapps to install along with the Rom (first time Rom is installed)
Gapps to install after rom is initialized (NoInit variant) without wipe data/factory reset.
Uninstallation for both Gapps variants (install with recovery and restart)
TWRP recovery (from Andi)
It includes a slightly modified theme and a more correct spanish translation.
Click here to Download Page
Installation:
Ensure you have installed an adecuated recovery.
Download the .zip file for your model.
Download the Google Apps (optional).
Reboot into recovery mode.
Imperative to do "wipe data/factory reset" (first time only)
Install the Rom zip file.
Install the Gapps .zip file (optional)
Updates:
Download the last .zip file available.
Reboot into recovery mode.
Install the .zip file without doing any wipes.
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: You assumes at your SOLE RESPONSIBILITY and RISK all results produced by the "software" and/or instructions in this thread.
XDA:DevDB Information
Dhollmen- 6.0.1 , ROM for the Samsung Galaxy Tab 2
Contributors
tuxafgmur
Source Code: https://github.com/Dhollmen?tab=repositories
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: Slim Roms 6
Version Information
Status: Testing
Current Stable Version: 6.0.1-20190331
Stable Release Date: 2019-03-31
Created 2019-04-01
Last Updated 2019-04-08
Here, there are some images.
NOTE: This screenshots have been made with a density of 140 points (as I use the tablet) instead of the usual 160 points.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reserved
Estupendo!
I'm quite happy with RR rom at the moment but it's nice to have choice so thumbs up and keep the good work :good:
Nice.
I would like to see OC kernel here, someday
nice, i'm gonna install this afternoon, i just lookinf for a ROM to my old tab5100
Dear tuxafgmur, we have been waiting for you and your special work for long time!
Thanks a lot for coming back to this forum and for sharing your updated galaxy tab2 rom development! This forum needs you and your work!
I am personally using in both my tablets, P5110 and P3110, your kernel until today (links here https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified and here https://forum.xda-developers.com/showthread.php?t=2176563) : it makes a device originaly restricted to 01GHZ to be able to run properly updated software nowadays at 1.52GHZ stable! Thats amazing! Even with battery savings if properly setup is done!
Please let me know if you need specific testing of overcloked kernels with this new slim based rom! As I wrote, updated software today needs overclock with this device to run properly: that is my opinion!
Thanks again.
PS: is it possible to use this old kernel from your previous work with this new rom ?
Hi and thank you for this new rom!
I tried to mount a samba share but it seems there's no cifs mounting support this time ( older Dhollmen roms got it)
levider said:
Nice.
I would like to see OC kernel here, someday
Click to expand...
Click to collapse
I'm working in OC now
It will be available very soon.
galoneta said:
Dear tuxafgmur, we have been waiting for you and your special work for long time!
Thanks a lot for coming back to this forum and for sharing your updated galaxy tab2 rom development! This forum needs you and your work!
I am personally using in both my tablets, P5110 and P3110, your kernel until today (links here https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified and here https://forum.xda-developers.com/showthread.php?t=2176563) : it makes a device originaly restricted to 01GHZ to be able to run properly updated software nowadays at 1.52GHZ stable! Thats amazing! Even with battery savings if properly setup is done!
Please let me know if you need specific testing of overcloked kernels with this new slim based rom! As I wrote, updated software today needs overclock with this device to run properly: that is my opinion!
PS: is it possible to use this old kernel from your previous work with this new rom ?
Click to expand...
Click to collapse
Pleased to have your help. I hope it will be necessary very soon.
I don't now if the old kernel works well here, however, the new one will be available in a few days.
Herrnobiz said:
Hi and thank you for this new rom!
I tried to mount a samba share but it seems there's no cifs mounting support this time ( older Dhollmen roms got it)
Click to expand...
Click to collapse
Please let me a few days to solve this.
EDIT: You can install my new Kernel and check if cifs mounting is solved now.
Wow? New Rom.....Thanks tuxafgmur
ashkineeeeee said:
Wow? New Rom.....Thanks tuxafgmur
Click to expand...
Click to collapse
If you do not know this yet, THANKS button under post is a thank you.
ze7zez said:
If you do not know this yet, THANKS button under post is a thank you.
Click to expand...
Click to collapse
?sorry
Hello, im having a bit of a problem installing this rom. I have a custom rom installed already(bliss rom) but it a bit buggy and randomly reboots. Anyway im trying to install this rom and i have it installed to a sd card(downloaded using the tablet) reboot in the recovery, wipe everything and try to install. I keep getting an error for the zip (status 7). Im pretty new doing this kinda of stuff amd i cant seem to find any info on how to fix this. Can someone please help? Thanks.
Racer27X said:
Hello, im having a bit of a problem installing this rom. I have a custom rom installed already(bliss rom) but it a bit buggy and randomly reboots. Anyway im trying to install this rom and i have it installed to a sd card(downloaded using the tablet) reboot in the recovery, wipe everything and try to install. I keep getting an error for the zip (status 7). Im pretty new doing this kinda of stuff amd i cant seem to find any info on how to fix this. Can someone please help? Thanks.
Click to expand...
Click to collapse
Outdated recovery?
Also, verify the rom's .zip file MD5 sum.
Racer27X said:
Hello, im having a bit of a problem installing this rom. I have a custom rom installed already(bliss rom) but it a bit buggy and randomly reboots. Anyway im trying to install this rom and i have it installed to a sd card(downloaded using the tablet) reboot in the recovery, wipe everything and try to install. I keep getting an error for the zip (status 7). Im pretty new doing this kinda of stuff amd i cant seem to find any info on how to fix this. Can someone please help? Thanks.
Click to expand...
Click to collapse
Make also sure you are using the right file. There is a version for tabs with mobile data capability (having a sim card holder) called "espresso3g" and one for tablets without sim card holder ("espressowifi").
Thanks for the help guys, I found out i had the wrong file(picked the one for mobile data instead of wi-fi). After i figured that out it installed no problem.
Herrnobiz said:
(...)
I tried to mount a samba share but it seems there's no cifs mounting support this time ( older Dhollmen roms got it)
Click to expand...
Click to collapse
Explain why archaic implementations in modern systems?
It is coming:"Adding OMAP4430_CPU and GPU overclick support.
This patch adds the below config variables
OMAP4430_CPU_HAS_MPU_1_2GHZ
OMAP4430_CPU_HAS_MPU_1_4GHZ
OMAP4430_GPU_HAS_MPU_384MHZ
OMAP4430_GPU_HAS_MPU_512MHZ
to enable CPU's 1216, 1360 and 1472 MHz frequencies, also GPU's 384 and 512 MHz.
The patch also ensures that the CPU never starts at boot higer than 1216 MHZ
On the other hand, it adds an interface to allow changing core voltages."
From "github.com/Dhollmen/Kernel_omap4_ti_espresso/commit/8b64123df27d0f3ea8706e198471a41400901bad"
Waiting!
Thanks again!