About:
The end-goal is to allow a graphical menu (similar to grub on PC's) that lets you boot different kernels (and ROMs - requires the ROM's to support it) from various media. This includes on-flash, SD based and USB but could theoretically also include network booting as well.
Method:
My current plan is to base the solution on the kexec-hardboot patches my mkasick. I've previously ported those patches to ASUS TF201 and my changes have then been adapted to Nexus 7 and is being used quite extensively.
At present time there is one big disadvantage to this method: It puts requirements on the target kernel. One of my goals in this project is to remove those requirements, so it will also work with stock unmodified kernels.
As far as the graphical part is concerned, the original plan was an extended KxecBoot(.org) or MultiBoot (based on TWRP).
After investigating the available solutions, I decided that I'd (shock-horror) implement my own. The current solutions seem overcomplicated to use and not exactly pretty to look at.
My solution, dubbed Hydra, is a simple - true-and-tried - grid of icons. It's based on recovery's minui graphics and the grid automatically aligns based on how many boot images are present. At present it is limited to 10 boot images, but this will be changed later.
The graphics rendering is optimized and will be improved further, possibly allowing for simple animations and such - but lets leave that for a v2
See screenshots in second post.
It works by reading a simple boot.ini, specifying name, icon, boot.img or raw kernel + ramdisk + cmdline. The device-specific commandline arguments required to boot the kernel will all features are automatically appended to the given cmdline, similarly to how the bootloader does it.
It is going to support multiple boot.ini's which are then merged to give the final set of images. This allows storing a boot.ini on e.g. microsd or usb storage and automatically get a suitable boot icon.
Source and images will come soon, there are a few minor issues that needs to be finished first.
Progress:
Tablet arrived!
06/07/13: Kexec patches tested successfully! Kexec booting is a go!
31/07/13: Multiboot solution is nearly done
Links:
Stock kernel with patches
CM Kernel with patches
Kexec tools with hardboot patches
Credits:
Mike Kasick for thinking up the original kexec hardboot patches
Screenshots:
Actual example of boot images loaded from a boot.ini:
{
"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"
}
Test with 5 icons
Test with 10 icons:
Frequently Asked Questions
FAQ:
How does it work?
In essence, it works by replacing kernel/bootimage in RAM while booting.
What does it allow booting from?
It allows booting from any media the linux kernel can access on the device. This includes internal flash (any partition), external SD card and USB Storage. In theory, it can also be extended to support booting over network
Are there any limitations?
No! Or yes. Due to the way android images mount filesystems, the image needs to be modified in order to boot a full system from e.g. SD. For regular linux this is not the case, because they support the 'root' commandline argument and loads filesystem information from that root.
Will it replace e.g. TWRP or CWM
Yes and no. It will replace the primary boot image of the tablet. This means that whenever the tablet boot, the multiboot solution runs. It can be setup to automatically boot an image after a configurable timeout, e.g. a few seconds usually and as such will add some seconds to the total bootup time. But really, how often do you turn off your tablet?
I'm looking at possibly including a CWM or TWRP image in the flashed image, to always have a backup recovery at hand.
Reserved 3
this one is interesting...
if u can get the kexec to work getting the menu to work is easy... i had created someting similar WAY BACK for the Xperia X10:
Indeed, having a multiple boot options is something amazing, imaging having ubuntu touch and android running on 1 single device.
Please take a look on Boot Menu Manager for Moto RAZR XT910. I guess it would help you somehow. At least for overall concept.
Carved in this thread with my RAZR HD
i would like to see the multiboot option b used. i have a nexus 7 and love multiboot. i have like 5 roms in my list. i also have a droid razr and have tried BMM as mentioned but still think multiboot is the way to go. thanks for this project Rayman can't wait to see it evolve!
i get my tablet tmrw can't wait
Good news! Tablet is here and the work can begin
Once I've tested my changes, I'll post the kernel changes required for initial version.
:victory: YES!
The basic kexec-hardboot port works - sources pushed to github (See original post).
Basic howto for using it while I work on the remaining parts will come later.
nice! good to see big progress already. question are you looking to make this project work with LK bootloader?
skiwong20 said:
nice! good to see big progress already. question are you looking to make this project work with LK bootloader?
Click to expand...
Click to collapse
Eventually, yes.
Lilstevie and I have discussed this possibility (even before we found out we were both selected).
There are definitely advantages in having LK detect the kexec instead and boot the kernel in question instead of the kernel itself handling it.
rayman said:
The basic kexec-hardboot port works - sources pushed to github (See original post).
Basic howto for using it while I work on the remaining parts will come later.
Click to expand...
Click to collapse
so just to confirm,
you have tested the kexec booting to boot a custom kernel over stock kernel of xperia tablet z?
also the most recent patch is over a year old, so you mean to say that no other modifications were required to get this working on the apq8064 kernel of sony?
just saw the sources... from what i understand this will only work with a base kernel which has these patches, meaning it will be of no use on locked bootloader devices... if we are able to create this for locked bootloader i believe this will be much more useful...
DooMLoRD said:
so just to confirm,
you have tested the kexec booting to boot a custom kernel over stock kernel of xperia tablet z?
Click to expand...
Click to collapse
I have tested booting a ram-loaded kernel from a custom kernel using the source I provide.
DooMLoRD said:
also the most recent patch is over a year old, so you mean to say that no other modifications were required to get this working on the apq8064 kernel of sony?
Click to expand...
Click to collapse
No. There were modifications - I just failed at cherrypicking the changes from my private tree. (wrong order)
DooMLoRD said:
just saw the sources... from what i understand this will only work with a base kernel which has these patches, meaning it will be of no use on locked bootloader devices... if we are able to create this for locked bootloader i believe this will be much more useful...
Click to expand...
Click to collapse
That was never part of this task. "Regular" Kexec is a lot harder to get working because you have to actually deinitialize a lot of hardware and reinitialize it without trouble. Not even always possible without a power cycle.
Personally, I'm not interested in solutions for locked bootloaders. The purpose of this is multi boot. In particular being able to boot something like e.g. ubuntu touch or Mer/Nemomobile by just selecting a menu item and the same for android.
At the moment is also requires modifications to the target kernel, but this is one of the issues I plan to address.
do you think it will be possible, one day, to dual boot android and ubuntu touch with this tablet?
yes when his multiboot solution is put together. they did this on the nexus 7
Sent from my SGP311 using xda app-developers app
i could only find dual boot with android and ubuntu, not ubuntu touch.. does the rom have to be modded to work with multiROM?
i'm asking all this questions because i'm considering to buy this tablet. does the roms differ from 16gb/32gb version?
well i am pretty sure ubuntu touch can b dual booted with android. ubuntu touch is built off CM base for most of the devices that have a ubuntu touch port. to multiboot any rom the kernel need a patch that rayman will have on github.
16 nd 32 g dont matter for build, but there are wifi only model: Sgp311= 16g Sgp312=32g . which the nickname for those is pollux_windy. and they have a 3g model=SGP321= nickenamed pollux. u have to make sure when u choose a aosp rom u r getting the right nickname build for the device u buy
Sent from my SGP311 using xda app-developers app
Sacob said:
i could only find dual boot with android and ubuntu, not ubuntu touch.. does the rom have to be modded to work with multiROM?
i'm asking all this questions because i'm considering to buy this tablet. does the roms differ from 16gb/32gb version?
Click to expand...
Click to collapse
skiwong20 said:
well i am pretty sure ubuntu touch can b dual booted with android. ubuntu touch is built off CM base for most of the devices that have a ubuntu touch port. to multiboot any rom the kernel need a patch that rayman will have on github.
16 nd 32 g dont matter for build, but there are wifi only model: Sgp311= 16g Sgp312=32g . which the nickname for those is pollux_windy. and they have a 3g model=SGP321= nickenamed pollux. u have to make sure when u choose a aosp rom u r getting the right nickname build for the device u buy
Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse
The ROM has to be modded to allow multi boot - primarily, the issue is that android mounts system, cache, data etc from a static configuration.
This means a multi-booted rom needs to somehow know where to mount these partitions from. It's a minor change and I'll certainly look into if I can find a good way to do this.
Ubuntu touch on the other hand will probably work unmodified, especially with the recent developments towards running the minimal android environment inside an lxc container.
I'm also hoping to eliminate the need to patch the target kernel (the on-flash kernel needs my patches!), but no guarantees there.
Related
Hello fellow old friends! I've brought something new and cool to this old forum(slow to keep up with the latest stuff).. And exremely cool for guys with non-working sd slots; You can now easily flash roms using "ADB Sideload" feature of TWRP.. bla bla...
UPDATE - 12MAR2013 - TWRP 2.4 Build taken down due to huge size which can't fit in our recovery partition.. Currently trying to slim it down..
Today, I felt like getting my ubuntu up and doing some fun stuff like old day. There! I decided to get another build of TWRP. I couldn't really test is as my bros phone is nowhere to be found . However, since I used the exact same source as the first build it should work just fine. Anyone willing to try their luck is welcome and appreciated..
{
"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:
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for 2.3 features
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
What's new in 2.2 & 2.1:
On-screen keyboard! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups before creation and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.2 features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues: (General TWRP issues)
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Issues I found:
-UMS doesn't work
i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:
Congrats bro on your first source build!!! :thumbup:
shmokeyuk said:
i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:
Click to expand...
Click to collapse
Ill check install from zip. But backup was working good..
rishabh.raj37 said:
Congrats bro on your first source build!!! :thumbup:
Click to expand...
Click to collapse
actually not my first.. I'm building aosp for my nexus
Sent from my Galaxy Nexus using xda app-developers app
Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option
-Grift- said:
Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option
Click to expand...
Click to collapse
Well, yeah you have a point.
Sent from my Galaxy Nexus using xda app-developers app
Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!
Punkiderma said:
Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!
Click to expand...
Click to collapse
Ill see that when my bro comes back home...
XiproX said:
Ill see that when my bro comes back home...
Click to expand...
Click to collapse
Confirmed: can't install zips
Thanks anyway! I'll be waiting for further verions =D
Well thats weird I just checked now and it looked like it flashed AOSP 1.4 successfully.. Ill check again after a full wipe..
And yes battery stats button is gone. Have no idea why.. I had just disable sd_partitioning to lower recovery image size to fit our phone. I dont remember disabling anything else.. Why do you even need wiping battery stats?
did a full wipe including system and flashed:
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.IceCreamSwift RC2 -- FLASHED
As you can easily see, it has no problem flashing android 2.3.7, 4.0.4, 4.1.2...
if you still cant flash, please try some other rom and report.. Thanks1
XiproX said:
did a full wipe including system and flashed AOSP 1.4 and successfully booted..
Ill be testing these roms and report..
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.Miro's Oxygen
Click to expand...
Click to collapse
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?
smileydr0id said:
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?
Click to expand...
Click to collapse
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM
XiproX said:
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM
Click to expand...
Click to collapse
Can you explain me how did you ported it ? i wanna try to port it on my xperia U
smileydr0id said:
Can you explain me how did you ported it ? i wanna try to port it on my xperia U
Click to expand...
Click to collapse
if its TWPR you are asking, I had already got my build environment set up following this, then it was really easy to build TWRP;
you can simply follow those instructions there for ubuntu, udev rules, and other tools like java, then skip Gnex stuff, use the same process for getting repo commands and instead of initializing AOSP source initialize CM source(https://github.com/Cyanogenmod -----...). After getting the cm repo follow The official TWRP guide. NOTE: Youll need device files for your phone. I hope someone has an open-source project
Good Luck! feel free to pm if you need something. And in case of any problem with building twrp or other twr related make sure you check their freenode you'll get your answer faster than you would on the guide thread..
Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!
XiproX said:
Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!
Click to expand...
Click to collapse
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly
coto39 said:
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly
Click to expand...
Click to collapse
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..
XiproX said:
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..
Click to expand...
Click to collapse
That's right I also had that issue but it was because of older binaries.
But I do have another issue, this version backs up my rom without problem but when it comes to restore, i just get bootloops. The thing is that apparently there are no errors restoring the backup. I have TWRP 2.1.4 and 2.3.1.1 flashable zips for when I need to restore
Are you aware of this XiproX?
Although this kernel is ended. I think I should put the downloads here:
http://sourceforge.net/projects/maxfuacm/files/Kernel/HydraNirvana/GT-N7000/
Critical Remind:
Flashing this kernel will make your phone Lose Warranty. So please Fully Get Understand of what you are doing. I have no responsibility of any of your lose by flashing this.
Before you download and flash, to farthest avoid bootloop or bricking your phone, please make sure you have read and understand sections from 4 to end.
Please be wisely use the "search this thread" at the top right corner, if you can not see it, click
{
"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"
}
there. And be sure you have already read the OP. New-asked-but-already-answered questions will be ignored and maybe disliked or even scoffed by other members.
I will never talk about ETAs (Estimated Time of Arrival). So please save your keyboard or touchscreen.
Please forgive me if I did not answer your question, even you asked before some one I answered. Please informe with message if you need me to answer it. Although I can not guarantee I will answer questions promptly, the carefulness of the answers is guaranteed. If the answer is important to you, please bookmark it cause I may edit the answer post with update instead of posting another one.
And if anyone don't like any part of my word. Please send me a message instead of posting here. All words above are my begging for the nattiness of this thread. I won't open another thread of discussion, cause I saw the discussion theads were mostly useless. Holding one thread is easier.
Thanks to:
@g.lewarne, @hardcore, @chandler929, @Formhault, @androidindian, @noteandfound, @chasmodo, @TeamHacksung, @samsung, @CyanogenMod team, ......,
and a lot of names to add.
Brief:
First, I would like to thank the people I mentioned and not mentioned in section 2. Notably g.lewarne, you are always the owner of HydraCore. Thank you for your great work. Galaxy Note now became a legend with your masterpiece.
Secondly, I would like to thank all people who gave me support, encourage and advise. Under your help, HydraCore has became a really universal and almost perfect kernel.
In this new thread, the legendary Universal Kernel has a new name -- HydraCoreNirvana. I think the word Nirvana can tell the story of HydraCore. With the new name, the kernel steped onto a new stage -- bootable on JB leaks. It is not fully functional, but it is a good beginning.
I have to say that I am not a dev. And I am another Child's Slave who use lavatory time as off hours. I really don’t know how far I can go on this. So please, forgive me if someday I got stuck and be absent like Gavin.
......long after n6......
For a long time I kept absent. I really found it hard to go on especially after the CM team upgraded the Mali driver. I am not the right guy to do the library job. So I switched to Samsung Opensource codes.
The first thing I did was building the Speedmod. I succussed. Meanwhile I made a build with Speedmod kernel image and PhilZ touch recovery initramfs. These builds worked fine with new released TouchWiz Jelly Beans. However, the CM code is going away with the Samsung Opensource codes. There are too many differences between them. The HOME button key issue was one result of this. It is harder and harder to combine CM and TouchWiz in one kernel. It is not just an universal initramfs, the kernel image itself needs to be universalized.
So I have to make a lamentable decision that from now on, I will stick with Samsung Opensource codes. So TouchWiz Jelly Beans will be supported prior to CM and other AOSP roms which have good enough kernels. Legacy features of HydraCore will be transplanted to the new builds one by one with careful test. CM and other AOSP roms maybe bootable with the new builds, but the functionality will not be guaranteed.
At last, thank you all for your long time support. I will keep on building this kernel and try my best to keep it Hydra for everyone. But for now, I can only step on one side, and I choose TouchWiz.
......more to add......
Technical Description:
Safety: mem_cap_erase disabled, so this is a safe kernel.
ROM Support:
ICS (4.0.X):
TouchWiz Based: TouchWiz ICS fully supported. Official MIUI still can not boot to system, adb works.
AOSP Based: CM9 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.1.X):
TouchWiz Based: TouchWiz JB, MIUI made by TWJB + Patchrom from http://www.miui.com/extra.php?mod=download/rom&fid=133 fully supported.
AOSP Based: CM10 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.2.X):
TouchWiz Based: Not out even leaked yet
AOSP Based: CM10.1 has bootloop with display.
Recovery: CWM 6 non touch recovery from @Phil3759: http://forum.xda-developers.com/showthread.php?t=1927097.
Root privilege: ADB and LBE superuser.
Usage:
Place the ZIP in the TF card.
Root the phone: If you and if you are sure that you have a safe kernel with CWM jume to next. If you phone is unrooted, Flash the TAR version in Odin to get Root and CWM.
Now you may meet bootloop, Press UP + HOME + POWER until you see the CWM interface. (the phone will never boot to the system with a stock rom flashed a TAR version)
Flash the ZIP in CWM.
Enjoy
Please don't ask me how to use CWM. If you don't know, don't flash any kernel.
Download with Changelog:
Instructions:
These are SourceForge folders, so open in a browser. The corresponding source is included in the same folder.
Not all releases will be kept in this post, find the old ones in the repository. I will keep all files as long as possible. (It seems SourceForge don't delete old files.)
Little trick: maybe you can try middle-click the links, a new tab maybe opened.
Notice: If you met black screen or bootloop after flashing the tar file. Try the zip package (The recovery should be working). The standalong Mali libraries might fix the problem.
n16:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n16/
Changelog:
Kernel: Pushed kernel version to 3.0.83.
Defconfig: Reverted pmem settings to fix video overlap. The bug is reported fixed.
Defconfig: Reenabled Samsung MTP. The hang of the MTP software on my MIUI v5 TouchWiz Patchrom fixed.
Makefile: Brought more legacy HydraCore tweaks including cpu and fpu tweaks.
n15:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n15/
Changelog:
Kernel: Pushed kernel version to 3.0.82.
Network: Fixed wifi tethering.
Audio: Fixed mic in software like talking animals, recoders, etc.
Mali: Tweaked thresholds to reduce lag on some heavy interface like MIUI desktop. Further tweaks may be needed.
Tweaks: Some small tweaks.
Platform: Switched to coLinux. Now it is ideal for me. It is a real linux like vmware, it uses less resource like cygwin, and it is fast like a directly installed linux.
Toolchain: Switched back to Linaro 4.7 with LTO.
n14:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n14/
Changelog:
Kernel: Pushed kernel version to 3.0.81 with cma port.
Superuser: Switched to LBE superuser with some simple permission management.
Defconfig: Brought more legacy HydraCore options which may be not noticeable.
HydraFS: Some workaround to MIUI. Now official MIUI v4 can boot to adb, positive. But the system is still not usable.
Platform: Switched to cygwin.
Toolchain: Switched to cygwin 4.6.3.
Filename: Yes, X.Y.Fu is still me, it is my name in short.
test builds:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Testbuild/
These builds are test builds. They usually contains new features or fixes. These changes need test. Read the README file in folders for more information.
build environment:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Platform/
Just follow the readme file.
TODO and TOFIX:
Add Multi-ROM-on-SdCard support.
Investigate the reason of the CM10 and CM10.1 failure boot.
Make MIUI v4 bootable. Fix CM boot problems.
AOSP MIUI JB support.
Bring back more HydraCore features.
Bring ability to set GPU frequency. This is extremely hard to me.
Bring ability to set CPU voltages. Found the location of the settings. Working on it.
Bring more ability to alter the kernel without reflash.
Tweak all the script included.
Study on offcial source code of JB.
64GB cards. I am not sure. 64GB exceeds Fat32 limitation. and exfat is not supported correctly.
Vibration Strength not alterable on AOSP roms. I am still working on this, maybe compile two different modules will solve the problem.
Q&A Collection:
How to flash: like I said if you don't know how to flash, then don't flash. Or you can read section 4.
Can I flash on ...?: Please get to know you rom type, AOSP or TouchWiz based, then please read section 4.
Bootloop/Freeze/..., help!: please be concrete, I can not answer questions simple like this.
Possible reasons of Black Screen: From n9, standalong Mali libraries are located in the zip. Try to use the zip package. It might fix the problem.
Possible reasons of Bootloop:
Please check your rom type see whether your rom is supported.
Another reason is the unsuppored modules. Look in to /system/lib/modules if it exist. And delete dhd.ko, j4fs.ko, scsi_wait_scan.ko and Si4709_driver.ko if they exist. Deleting dhd.ko may also fix WIFI problem.
Possible reasons of Lag: Check the governor and IO settings. Or maybe just clean the RAM. At last, reboot.
Possible reasons of Freeze: Usually happens after a heavy load work. Try to reboot. Reboot usually works.
...adding...and...collecting...
Old Versions:
n13: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n13/
n12: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n12/
n11: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n11/
n10: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n10/
n9: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n9/
n8: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n8/
n7.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n7.JBT/
n6.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n6.JBT/
n5.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n5.JBT/
n4.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n4.JBT/
n3.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n3.JBT/
n2.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/6th_v7.6.JBT/
n1: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/5th_v7.6.2/
Great maxfu. You have a lot to say and we'd love to listen
Sent from my GT-N7000 using Tapatalk 2
Finally...
ANG.MAHAL.NG.NOTE.KO
maxfu said:
My sixth compilation with experimental TWJB leak support:
https://sourceforge.net/projects/maxfuacm/files/Galaxy Note/MaxFu_HydraCore/v7.6.JBT.1/
Click to expand...
Click to collapse
Seriously? We can finally OC the jb leaks? AWESOME!!!
I guess cm10.1 kernel is next?
ANG.MAHAL.NG.NOTE.KO
It's fantastic, thanks man.
Thanks man a new life for our great Hydracore..............
Another awesome release from Maxfu
thanks man.
Will it really work on JB Leaks ???
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )
Immortal Nerd said:
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )
Click to expand...
Click to collapse
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.
Haints said:
Seriously? We can finally OC the jb leaks? AWESOME!!!
Click to expand...
Click to collapse
Yes, you will have OC. But camera maybe gone.
maxfu said:
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.
Click to expand...
Click to collapse
Is there any critical problems in the sixth compilation for leaked jb? If not, I well flash this right away
Edit : so the camera is break in the latest kernel? Hmm alright I think I will wait for the next compilation really great work maxfu, thank you for make the hydra core can run in leaked JB :good:
XXLSC Wait,.,
Sent from my GT-N7000 using xda premium
Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462
Should be. But not on CM 10.1
cuba462 said:
Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462
Click to expand...
Click to collapse
Hi maxfu. The original HydraCore 7 is unsupported by the awesome jellybam. This would be?
Sent from my GT-N7000 using xda premium
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
download it again ?
capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
Have you already checked md5?
ANG.MAHAL.NG.NOTE.KO
noteandfound said:
Have you already checked md5?
Click to expand...
Click to collapse
Oh, yeah, sure, no doubt...
{
"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"
}
Base: N7100 KK Sources
Linux 3.0.31
Compiled using latest ArchiToolchain 5.2.0
ArchiDroid Optimizations
Using AnyKernel method (compatible with all ROMs for both AOSP and Samsung)
And many other awesome things I have no time to list
ArchiDroid Optimizations:
- Fully optimized for Samsung Galaxy S3 (-marm -march=armv7-a -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp)
- Compiled with O3 optimization level (-O3)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
Click to expand...
Click to collapse
Download
What to expect:
- Awesome stock battery life on AOSP ROMs (due to Samsung sources and not smdk4x12)
- Blazing fast (Deep advanced optimizations, Linaro toolchain, this is the beast)
- High compatibility (AnyKernel method, the kernel should work on all ROMs)
What to expect in future:
- You tell me
What to NOT expect:
- Many CPU or I/O governors # We don't need overhead, you can achieve nearly the same just by tweaking governor to your needs
- Features I don't like/need
- Dualboot (see above ^)
- F2FS (see above ^, however this one depends on kernel upstreaming, as f2fs is merged)
ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.
AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.
AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.
SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)
SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port
ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
Flashing instructions:
1. Make sure that you have stock kernel already flashed (the one which comes with your ROM), if you're running custom kernel already, reflash your ROM without wipe, this will also flash stock kernel. This is ultimately important, DON'T FLASH ARCHIKERNEL ON ANOTHER CUSTOM KERNEL, you may face various issues you've never seen before.
* This is because ArchiKernel uses AnyKernel method - it pulls ramdisk from your current kernel. If you brick your phone by flashing AK on top of custom kernel, you know who will be responsible for that.
2. Flash ArchiKernel zip.
3. Profit!
Updating instructions:
1. If you arleady have older ArchiKernel version flashed properly with above instructions, and changelog doesn't state otherwise, just flash the .zip with new version of AK.
2. No wipes, cleaning dalvik cache or anything else is required, flashing zip is enough.
3. Profit!
Bugs:
None known
XDA:DevDB Information
[EOL] [KERNEL] [AOSP/Samsung/Ports] [ArchiToolchain 5.2] [01/10/15] ArchiKernel V2.1, Kernel for the Samsung Galaxy S III I9300
Contributors
JustArchi, Moster2
Source Code: https://github.com/ArchiDroid/ArchiKernel
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-06-17
Last Updated 2015-11-12
Reserved
Reserved
Last one.
Great job! Amazing to see a dedicated thread for this beauty.
Will report the experience
V1 uploaded in download section on the top of the thread. It should work with all AOSP ROMs but you tell me if it does. Don't flash it on Sammy (yet). Let me know if I screwed up something, it's late .
will test on omni,thanks
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
coto39 said:
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
Click to expand...
Click to collapse
At some point I'll definitely consider adding ArchiKernel support in ArchiDroid app, but it won't come too fast.
However, you can still "tweak it' in various ways. SetCPU, TricksterMod and similar apps are only a few examples. Boeffla Sound Control app (not boeffla config) will work as well. But think twice if you want to do, as ArchiKernel is pretty damn tweaked right after booting.
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
beeeto said:
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
Click to expand...
Click to collapse
If you want to know my opinion - Current smdk4x12 source used in all AOSP kernels is a crap. Somebody screwed up something really hard, I looked at the sources and there are over 7 hundred of different files (comparing to Update13), half of the updates from Update11, Update12 are not even included, while Update13 is not included at all. Whole kernel is one big mess and I have no idea how it even boots. It contains so many merge derps and hacks/workarounds that it hurts. I didn't even want to fix it, too much work to do. I started from clean stable and battery friendly Update13 base.
After flashing first alpha version of my kernel I immediately noticed significantly improved battery life, same as on Sammy ROM. So now I have my perfect combo, ArchiDroid 2.X AOSP speed and ArchiKernel Sammy battery life. Whatever you say, I'm keeping this baby. I love this kernel.
Big credit goes to @Yank555 and @Lord Boeffla because they're true kernel developers, I've made my own kernel based mostly on their commits (but not only, I added my own part as well and I'll add more soon).
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Add it to the OP!
While not everyone actually reads even the first post, even fewer people would actually bother reading the whole first page.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
skim0322 said:
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If need be, but the stock kernel alone should be enough if you get hands on a .zip.
Awesome
Sent from my GT-I9300 using Tapatalk
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
May I ask for a flashable zip file of the stock kernel..Thanks.:good: I would like to try this
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
i am on archidroid 2.4.6 with boeffla kernel.u mean that i cannot flash your kernel over my current kernel?
Are cam bugs gone since you did not upstream it to the 3.101?
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
Hi,
so, this would be the perfect linux phone. If. only. I. could. get. this. to. bloody. work. :crying:
So, I've built a kernel to enable linux containers and booted a plasma mobile system. But the screen stays black. No way to get something to display on the framebuffer. Something is broken. Why does libhybris fail? No idea.
Code:
[email protected]:/home/phablet# test_egl
Segmentation fault
Why can I not get anything to draw on the framebuffer? No idea.
Code:
cat /dev/urandom > /dev/graphics/fb0
XDG_RUNTIME_DIR=/home/phablet weston --tty=0 --backend=fbdev-backend.so --device=/dev/graphics/fb0
And so on.
This needs someone more qualified than me. Maybe we can collect bounties or something? I chip in with 50€ for a running wayland client. :good:
UPDATE 2017-03-24:
Things are coming along better than I hoped. :laugh:
Tony Lindgren et al. and TheKit both independently have wayland running on this device, with mainline (4.12) support nearing completion, and SailfishOS on the other hand successfully driving most hardware via libhybris on a 3.0.8 kernel atop a LineageOS 14.1. base. Kudos! :laugh:
Linux OMAP mailing list: http://www.spinics.net/lists/linux-omap/
SailfishOS local_manifest_maserati.xml: https://gist.github.com/NotKit/95ec76f4eff149e61753ae467f613cbe
Good luck porting a genuine Linux OS to this phone. The keyboard is excellent for semi desktop use. Android is nice but native Linux would be sweet.
I'd just like to wish you good luck with this too.
I don't know how relevant this is, and you've probably seen it anyway, but there's a thread on Maemo about porting Salifish to the Droid 4 (though it doesn't sound like much is happening), but someone there might have some ideas?
https://talk.maemo.org/showthread.php?t=91305
Luck ain't gonna cut it, neither is talking. This needs an experienced developer capable of debugging, distro-building and kernel patching. Perhaps @Mentor.37, @joojoobee666, @Hashcode, @stargo .. or we could collect money to give this phone to another interested developer.
It is not an easy process but very doable for someone with the right experience and skill set. Now how about some substantial encouragement? As said, I chip in at 50€ for any running wayland client. Who else is in
EDIT: Hell what, not that I am wealthy but I am raising to a 100€. Hundred bucks. Who's up for the challenge
FYI,
All of the latest branches for Wayland, libhybris, etc use the DRM API for rendering. (Look at Linux kernels 3.10+). This is probably why you're seeing a segmentation fault as those nodes don't exist in our 3.0 kernel setup.
To add to this complexity you would need new OMAP4430 PVR binaries built for DRM to match up with said newer kernel. (Our kernel GPU blobs use the framebuffer API in 3.0 kernel).
- Hash
Hashcode said:
the DRM API […] don't exist in our 3.0 kernel setup.
Click to expand...
Click to collapse
Mr. Tony Lindgren is working on upstreaming patches to bring up the device on mainline kernel, but that project is in its infancy.
Hashcode said:
To add to this complexity you would need new OMAP4430 PVR binaries built for DRM to match up with said newer kernel. (Our kernel GPU blobs use the framebuffer API in 3.0 kernel).
Click to expand...
Click to collapse
Now that's basically a death sentence for this idea, isn't it? https://github.com/robtaylor/pvr-omap4-dkms is not going to be of much help, eh? :crying:
eMPee584 said:
Mr. Tony Lindgren is working on upstreaming patches to bring up the device on mainline kernel, but that project is in its infancy.
Now that's basically a death sentence for this idea, isn't it? https://github.com/robtaylor/pvr-omap4-dkms is not going to be of much help, eh? :crying:
Click to expand...
Click to collapse
Yes, unfortunately the robtaylor github is based on PVR version 1.9.2166536 which is about 4 years old now. :/
Hashcode said:
Yes, unfortunately the robtaylor github is based on PVR version 1.9.2166536 which is about 4 years old now. :/
Click to expand...
Click to collapse
I think the pyra tree has sgx working for omap3 and omap5, including tiler for omap5 so that might be usable for some omap4 patches too?
Regarding the droid 4 mainline kernel status, I'm still hoping to get the PMIC core support merged for v4.11. Then I have a regulator driver working and and a basic USB and UART multiplexing driver. Those need still cleaning up before posting though. The pending TI LMU patchset seems to get the LCD backlight working for the lm3532, and now I'm trying to get the LCD working for fun :laugh: I guess it should work with omapdrm and panel-dsi-cm with some modifications. Anyways, hoping to be posting more patches over next few weeks and some kernel test branch to play with.
tmlind said:
I think the pyra tree has sgx working for omap3 and omap5, including tiler for omap5 so that might be usable for some omap4 patches too?
Regarding the droid 4 mainline kernel status, I'm still hoping to get the PMIC core support merged for v4.11. Then I have a regulator driver working and and a basic USB and UART multiplexing driver. Those need still cleaning up before posting though. The pending TI LMU patchset seems to get the LCD backlight working for the lm3532, and now I'm trying to get the LCD working for fun :laugh: I guess it should work with omapdrm and panel-dsi-cm with some modifications. Anyways, hoping to be posting more patches over next few weeks and some kernel test branch to play with.
Click to expand...
Click to collapse
OK got the LCD console working last night That's with omapdrm with most of the kernel.org sre/linux-n900.git patches in n950-display branch. I still have some pixelclock getting miscalculated issues and need to clean up things, but then should be able to post a test branch to play with. No idea what it might take to get the rest of the accelerated graphics going but hopefully others people can take it from there.
tmlind said:
OK got the LCD console working last night That's with omapdrm with most of the kernel.org sre/linux-n900.git patches in n950-display branch. I still have some pixelclock getting miscalculated issues and need to clean up things, but then should be able to post a test branch to play with. No idea what it might take to get the rest of the accelerated graphics going but hopefully others people can take it from there.
Click to expand...
Click to collapse
Not very usable at least with just omapdrm.. But still a fun test
{
"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"
}
---------- Post added at 22:34 ---------- Previous post was at 22:09 ----------
eMPee584 said:
Why can I not get anything to draw on the framebuffer? No idea.
Code:
cat /dev/urandom > /dev/graphics/fb0
XDG_RUNTIME_DIR=/home/phablet weston --tty=0 --backend=fbdev-backend.so --device=/dev/graphics/fb0
And so on.
This needs someone more qualified than me. Maybe we can collect bounties or something? I chip in with 50€ for a running wayland client. :good:
Click to expand...
Click to collapse
My guess is that the dss kernel driver is missing LCD command mode flush based on the framedone interrupt if nothing shows up.
Won't help with the segfault though.
tmlind said:
Not very usable at least with just omapdrm.. But still a fun test
OK finally posted the WIP patches I'm using against Linux next currently at droid4-wip-next-20170203:
http://muru.com/linux/d4/patches/
What works currently is MMC, eMMC, WLAN, keyboard, LCD and touchscreen. For UART,
you need the custom cable and make sure VBUS is not connected.
Click to expand...
Click to collapse
wayland jackpot
tmlind said:
Click to expand...
Click to collapse
ultra. you earn half the bounty for firing up wayland, along with https://forum.xda-developers.com/showpost.php?p=71138243&postcount=18 . :good:
eMPee584 said:
ultra. you earn half the bounty for firing up wayland, along with https://forum.xda-developers.com/showpost.php?p=71138243&postcount=18 . :good:
Click to expand...
Click to collapse
Hey thanks and sorry for the long delay in replying, I used it to buy some HD docks at $5 each
And just to update the mainline kernel status, audio and display patches are still pending. 3G data works but reboots the system after 10 - 20 minutes.
Sebastian Reichel has some nice pages about that at:
http://elektranox.org/2017/08/0022-droid4/
Then for booting custom distros directly from any partition, please check out utagboot I posted last night at:
https://github.com/tmlind/utagboot
Regards,
Tony
PostmarketOS has made lots of progress in recent weeks, even has the beginnings of a porting wizard. With nearly full mainline support, this shouldn't be too hard to bring up? :fingers-crossed:
eMPee584 said:
PostmarketOS has made lots of progress in recent weeks, even has the beginnings of a porting wizard. With nearly full mainline support, this shouldn't be too hard to bring up? :fingers-crossed:
Click to expand...
Click to collapse
Yeah should be totally doable and fun project, go for it! I've mostly used alpine as my rootfs anyways for past year as it nicely fits to mmcblk1p23
Also looks like the LCD patches are finally getting merged for v4.16.
Then I'm slowly working on getting a 4MB buildroot-kexecboot bootloader image posted that can be flashed to mmcblk1p13.. For legacy v3.0.8 based kernels we have an issue with kexec where the android images depend on SafeStrap configuration being on vfat mmcblk1p25.. I think we should update the LineageOS based images to have initramfs just parse the current root partition from kernel cmdline if available and that way mmcblk1p25 can be reformatted as ext4 and is usable. Anybody got a chance to work on that?
Regards,
Tony
tmlind said:
Then I'm slowly working on getting a 4MB buildroot-kexecboot bootloader image posted that can be flashed to mmcblk1p13.. For legacy v3.0.8 based kernels we have an issue with kexec where the android images depend on SafeStrap configuration being on vfat mmcblk1p25.. I think we should update the LineageOS based images to have initramfs just parse the current root partition from kernel cmdline if available and that way mmcblk1p25 can be reformatted as ext4 and is usable. Anybody got a chance to work on that?
Click to expand...
Click to collapse
OK I managed to get the first version of droid4-kexecboot pushed out if anybody cares to play with it:
https://github.com/tmlind/droid4-kexecboot
Regards,
Tony
tmlind said:
fun project, go for it!
Click to expand...
Click to collapse
no time/concentration to spare, sorry
but nice stuff! s0o looking forward to libre wayland HARDWARE KEYBOARD phones
tmlind said:
OK I managed to get the first version of droid4-kexecboot pushed out if anybody cares to play with it:
https://github.com/tmlind/droid4-kexecboot
Click to expand...
Click to collapse
Just pushed a 2017-12-20 image with v3.0.8 kexec wrapper script fixed if anybody dares to try it.
It might just work for booting a v3.0.8 based image if you also have SafeStrap installed so the initramfs can use the configuration for the active image..
The initramfs still needs to be fixed for droid4-kexecboot to boot images directly on any partition using kernel cmdline if anybody has a chance to work on that.
Booting mainline kernel images with droid4-kexecboot does not have these issues naturally.
Regards,
Tony
tmlind said:
Just pushed a 2017-12-20 image with v3.0.8 kexec wrapper script fixed if anybody dares to try it.
It might just work for booting a v3.0.8 based image if you also have SafeStrap installed so the initramfs can use the configuration for the active image..
The initramfs still needs to be fixed for droid4-kexecboot to boot images directly on any partition using kernel cmdline if anybody has a chance to work on that.
Booting mainline kernel images with droid4-kexecboot does not have these issues naturally.
Regards,
Tony
Click to expand...
Click to collapse
Doesn't seem to work for me.
It boots fine into kexecboot but pressing any key other than the volume keys causes it to freeze.
Sometimes even the volume keys don't work.
Pressing Q works sometimes, causing the screen to go black and stay that way.
Pressing R also works sometimes causing a reboot, everything else does nothing or causes it to freeze.
I don't have an uart connector so I can't get any details on what is happening exactly.
It is interesting though that utagboot does boot into kexecboot considering that it never booted anything else for me.
Ddroid never worked for me since it requires selinux (to install) which is only present in SS 3.75 but the modules don't work in SS 3.75 (segfaults during kexec).
I have to manually load the modules and run kexec from SS 3.72 to get a mainline kernel to boot.
... by the way, NotKit has made good progress in porting postmarketOS to our droid4 using libhybris: https://github.com/postmarketOS/pmbootstrap/pull/1039
This will probably become usable within a couple of weeks, yeah!
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!