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!
Related
Hello everybody,
Based on the kernel from DooMLoRD and FXP and wanting to make a more clean kernel in relations to Stock Kernel and add some personal changes, I make my own kernel that I am posting below.
He is based on 4.0.2.A.0.61_62 source kernel, and adding the follow changes:
v1.0:
New Governor Option:
SmartAssV2
Smartass
Smoothass
BrazilianWax
Interactive
Savaged-Zen
Scary
I/O Schedulers:
Noop (default)
Anticipatory
Deadline
CFQ
Overclock option to 1.9 Ghz
Enabled SWAP support
Enable some file systems:
EXT2
EXT3
EXT4
NTFS (Read & Write)
CIFS
DoomKernel Ramdisk:
With autorooting (prerooted)
init.d scripts/binaries execution support
support /sd-ext backup/restore
modCWM-v04 TouchEdition Recovery
and other (see http://forum.xda-developers.com/showthread.php?t=1172885 for full changelog of DoomKernel Ramdisk)
Default Sony Xperia boot logo.
v1.1:
Have the same features that v1.0, only bug fix on compiler configuration.
v1.2:
Improve battery life
Change Sony source code base, now base on 4.0.2.A.0.61_62 source
v1.3:
Great improve of battery life by disable NETWORK_FILESYSTEMS (CIFS and NFS)
v1.4:
Enable CPU undervolting options (the kernel frequencies is not undervolted, but you can undervolt (recommend using IncrediControl)
WiFi undervolting
v1.5:
Disable duplicate voltage scaling frequency, for better manager of cpu frequency and better battery life.
From FreeXperia: salvage some more ram by removing unused pmem_adsp_cache
From FreeXperia: salvage some more ram by removing unused pmem_audio
Disable verbose procfs contents
Adding scripts for better battery life and overall performance:
Internet speed tweaks
Misc kernel tweaks
Battery tweaks
Journali smoff
Defrag DB
Loopy smoothness
Sick
Zipalign
Zipalign Defrag DB
Change sched_latency_ns to 600000
Change sched_wakeup_granularity_ns 400000
v1.6:
WiFi Power Management Tweak
Increase CPU voltage of some frequency for better stability
CPF Frequency Tweaks and Enable CPU AVS (Adaptive Voltage Scaling)
Revert: change sched_latency_ns to 600000
Revert: change sched_wakeup_granularity_ns 400000
Enable EXT3 and EXT4 Posix ACL and XATTR
Disable YAFFS ECC Check
Enable YAFFS empty lost and found folder at mount
Disable YAFFS block refreshing
Change pll2_fixup onverclock control
New compiled WiFi modules
WiFi modules included in Ramdisk
In general this version is for improve the battery life and resolve the problems of WiFi don't work because of user using not default WiFi modules (DoomKernel Modules)
Ps. For user with WiFi don't work just restart twice.
v1.7:
Enable 1200Mhz frequency
Add IO SCHEDULE BFQ
Add CM torch interface (base on Blendkernel v02 from Jason Stain)
Use disable_irq_nosync() from within irq handlers (base on Blendkernel v02 from Jason Stain)
Prepare I/O context code for BFQ
Custom tweaks in kernel config
v1.8:
Revert change in acceleration sensor support. Fix acceleration sensor error.
v1.9:
Upgrade busybox to fix the execution of user script (init.d).
Remove some scripts that were causing problems.
The instalation is the same from other kernel:
Code:
fastboot flash boot boot.img
PS.: for CPU undervolting I recomend using IncrediControl (https://market.android.com/details?id=com.incredicontrol)
{
"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 want to warn that THIS IS A TEST KERNEL, so he may have some bug.
By
Adriano Martins
-----------------------
Source at https://github.com/AdrianoMartins
I'm testing... thanks.
Just flashed it! I will report soon! Thanks for sharing!
Subscribed....
Sent from my LT15i
kindly tell me what do u mean by a
less "invasive" kernel in relations to Stock Kernel
Click to expand...
Click to collapse
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
try get some more features to Xperia 2011 device kernels...
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
or if no one is interested then atleast tell me that way i wont spend my time working on ARC... wait may be i should stop all kernel work for ARC...
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
DooMLoRD said:
kindly tell me what do u mean by a
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
try get some more features to Xperia 2011 device kernels...
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
or if no one is interested then atleast tell me that way i wont spend my time working on ARC... wait may be i should stop all kernel work for ARC...
Click to expand...
Click to collapse
Doom, although it's not my place to say anything, I figured I'd go ahead and do it anyway.
I understand your frustration because I know how much work you put in your kernels and you are without a doubt one of the most active developers.
And I have to agree that you are the "leader" around here, in the sense that if you don't introduce new features for our phones, no one else does.
The only thing that I wanted to point out is that, in my view, you shouldn't be disappointed when people use your work, if of course they credit you properly,
which I feel is the case here. Adrianom compiled this kernel for his personal use and thought he'd share, which objectively is not such a bad thing.
It's certainly not something that should make you feel like giving up on the Arc altogether, as this would be very sad.
And maybe also consider the way you started compiling kernels using zdzihu's sources and ramdisk (legendary Power To The People )
and slowly learned and shifted to your own sources...
So maybe that will be the case for the people currently using your sources.
I am sure that at the end of the day, your work is truly appreciated the way it deserves to be.
Just my 2 cents.
DooMLoRD,
DooMLoRD said:
kindly tell me what do u mean by a
Click to expand...
Click to collapse
I just wanted to say I wanted a cleaner kernel compared to Sony, that's all. I did not want at all say that something is wrong with your kernel.
DooMLoRD said:
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
Click to expand...
Click to collapse
Here I think you're wrong, I did not say anything was wrong with your kernel, on the contrary, said even that was based on his and the FXP kernel, and I believe that I don't have to ask permission to use an Open Source code, you ask Sony? Google? Linus? I think not.
DooMLoRD said:
try get some more features to Xperia 2011 device kernels...
Click to expand...
Click to collapse
I don't want new features, that is the point....
DooMLoRD said:
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
Click to expand...
Click to collapse
I am searching... on my own, or do you think that a developer community should consist of only one person developing and the others sending it logs?
I think you misunderstand my post, I just wanted to provide something that I'm using.
This is the principle of an open source system, people can move the way they want it. And that's what I'm doing.
Just wanted to help someone who wants the same as me.
By.
iridaki said:
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the feedback.
I don't have this problem but, I'll see what can be.
iridaki said:
Doom, although it's not my place to say anything, I figured I'd go ahead and do it anyway.
I understand your frustration because I know how much work you put in your kernels and you are without a doubt one of the most active developers.
And I have to agree that you are the "leader" around here, in the sense that if you don't introduce new features for our phones, no one else does.
The only thing that I wanted to point out is that, in my view, you shouldn't be disappointed when people use your work, if of course they credit you properly,
which I feel is the case here. Adrianom compiled this kernel for his personal use and thought he'd share, which objectively is not such a bad thing.
It's certainly not something that should make you feel like giving up on the Arc altogether, as this would be very sad.
And maybe also consider the way you started compiling kernels using zdzihu's sources and ramdisk (legendary Power To The People )
and slowly learned and shifted to your own sources...
So maybe that will be the case for the people currently using your sources.
I am sure that at the end of the day, your work is truly appreciated the way it deserves to be.
Just my 2 cents.
Click to expand...
Click to collapse
Iris u have known me since X10 days... so thanks for ur post...
adrianom said:
DooMLoRD,
I just wanted to say I wanted a cleaner kernel compared to Sony, that's all. I did not want at all say that something is wrong with your kernel.
Here I think you're wrong, I did not say anything was wrong with your kernel, on the contrary, said even that was based on his and the FXP kernel, and I believe that I don't have to ask permission to use an Open Source code, you ask Sony? Google? Linus? I think not.
I don't want new features, that is the point....
I am searching... on my own, or do you think that a developer community should consist of only one person developing and the others sending it logs?
I think you misunderstand my post, I just wanted to provide something that I'm using.
This is the principle of an open source system, people can move the way they want it. And that's what I'm doing.
Just wanted to help someone who wants the same as me.
By.
Click to expand...
Click to collapse
very interesting point of view...
this is not the first time such a thing is happening and may be i am a bit edgy today... anyways...
FYI, kindly read
12. Using the work of others.
Click to expand...
Click to collapse
REF: http://forum.xda-developers.com/announcement.php?f=965
regards,
DooMLoRD
iridaki said:
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
Click to expand...
Click to collapse
iridaki,
I think I found the problem, I compile a new version and did some testing for a while and did not generate any deleted_wake_locks.
I would appreciate if you can test again. The boot image is on attach.
Thank you again for your feedback.
adrianom said:
iridaki,
I think I found the problem, I compile a new version and did some testing for a while and did not generate any deleted_wake_locks.
I would appreciate if you can test again. The boot image is on attach.
Thank you again for your feedback.
Click to expand...
Click to collapse
That was fast! I'll update this post with my findings!
Thanks!
iridaki said:
That was fast! I'll update this post with my findings!
Thanks!
Click to expand...
Click to collapse
It would be nice if you could clear the cache before also, to eliminate any problem of applications that may be interacting with the kernel.
Thanks.
adrianom said:
It would be nice if you could clear the cache before also, to eliminate any problem of applications that may be interacting with the kernel.
Thanks.
Click to expand...
Click to collapse
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
iridaki said:
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
Click to expand...
Click to collapse
I think version 1.1 was the same problem that version 1.0.
I was led to understand that was not happening because of what I think is a bug in BetterBatteryStats. It change the name of the wifi wakelock to deleted_wake_locks when wifi is disable. I'll keep looking, now for the wifi problem.
Thanks.
iridaki said:
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
Click to expand...
Click to collapse
+1
I'll test your kernel for a few days and give a feedback.
I flashed to v1.1 and doing a full charge and delete batterystats to ensure freshness of battery.
Sent from my LT15i
superlimau said:
I flashed to v1.1 and doing a full charge and delete batterystats to ensure freshness of battery.
Sent from my LT15i
Click to expand...
Click to collapse
Just bear in mind that when you wipe batterystats, you might notice battery percentage decreasing faster at first or inconsistently, so test the kernel for at least 2 battery cycles.
iR¡[email protected]!* via Tapatalk
Doing so now.
Sent from my LT15i
Made test with 1.0. I think battery drain here too.
my settings that i only changed is:
122Mhz - 1.4Ghz
smartass v2
com.sonyericsson.android.server.dormant = 642 wakeups What is it?
tRippinthehead said:
com.sonyericsson.android.server.dormant = 642 wakeups What is it?
Click to expand...
Click to collapse
It's Fast Dormancy, a network feature. Does your provider support it?
iR¡[email protected]!* via Tapatalk
Hello Guys,
Here is a plasma active build:
{
"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"
}
Don't expect much support on this, for me it seems unusable as it is, too slow and not finished. I just wanted to take a look at the way they boot from sdcard.
Installation:
1) You need SDE activated.
2) Unzip files to a directory
3) Copy plasma_rootfs.img to root of storage
4) Flash kernel+initramfs.gz in recovery (details with pictures there).
5) Boot sde
6) Wait, wait, wait! First boot is very slow, I didn't even try a second boot
Download is there (big file, 447 MB)
Thanks to cajl for pointing this and pushing me working on it.
Looks great !
Thank you for your excellent work ! I will try your ROM later....
Yet Another Stupid Question
Does this work also on hdd models?
tapatalked from Desire
BTW, someone promised a KDE-based buid as the usual SDE 'firmware' for gen9. Probably on behalf of Archos itself... Two months ago. Still there are no more signs of progress...
Not allowed to post links here yet, look at dot.kde.org
PLEASE READ:
I talked to a developer working for Archos, the Plasma Active based firmware is going to be the official SDE firmware!
But they're not working on it at the moment, they're trying to get ICS firmware out asap!
ALSO NOTE THAT:
the current plasma active image has no wifi (this is what I was told, haven't tried it yet) and that XORG is not HW Accelerated! The developer who made the Plasma Active based image is waiting for the kernel v3 to be released together with ICS firmware, hoping that a new kernel will fix the issues with WiFi and Hw acceleration.
Thank you, faenil - any piece of information is useful... but why so many capital letters?
faenil said:
I talked to a developer working for Archos, the Plasma Active based firmware is going to be the official SDE firmware!
But they're not working on it at the moment, they're trying to get ICS firmware out asap!
Click to expand...
Click to collapse
Quite reasonable approach for a vendor. No more questions. At least, it is a very good sign that the vendor does not go blindly within the entire Google-driven mainstream but has a broader insight and does try the alternatives. A bad thing IMHO is that the heaviest desktop environment is selected, the least appropriate for XDAs. Yet some people really like it...
the current plasma active image has no wifi (this is what I was told, haven't tried it yet) and that XORG is not HW Accelerated! The developer who made the Plasma Active based image is waiting for the kernel v3 to be released together with ICS firmware, hoping that a new kernel will fix the issues with WiFi and Hw acceleration.
Click to expand...
Click to collapse
well, without wifi it it a pretty useless toy... hw acceleration is less critical for me (but not for others, I think).
On the other hand, once Archos is officially involved into this project, why couldn't they use the existing 2.6.x kernel? It does work within the Android, hence, there are all necessary modules and kernel options being known, written and placed properly. Excuse my ignorance, what is the problem in building the kernel with all the hw features for a particular device yet without Android-specific sw components? Or what is the problem in running a generic Linux userspace on top of it?
Hi gen_scheisskopf,
gen_scheisskopf said:
Yet Another Stupid Question
Does this work also on hdd models?
Click to expand...
Click to collapse
No, still the same issue, I didn't make any progress on this. Sorry :-(
See this information from Basyscom
« Hi Jean-Luc ,
unfortunately we’ll have to wait a bit as the developer edition is required to install plasma edition. Archos wants to publish the developer edition after icecream sandwich being released.
Regards,
Eva »
But letama is faster .....
iourine said:
On the other hand, once Archos is officially involved into this project, why couldn't they use the existing 2.6.x kernel? It does work within the Android, hence, there are all necessary modules and kernel options being known, written and placed properly. Excuse my ignorance, what is the problem in building the kernel with all the hw features for a particular device yet without Android-specific sw components? Or what is the problem in running a generic Linux userspace on top of it?
Click to expand...
Click to collapse
The problem is the guy who's currently building PlasmaActive images is not from Archos the guy from Basyscom http://basyskom.com/news/78-plasma-active-on-archos.html
I don't know if there's any agreement, but I think they'll probably use his work and add the missing features at Archos
Hello letama, nice work here!
Do you have WiFi working in this image?
a1Pha said:
Hello letama, nice work here!
Do you have WiFi working in this image?
Click to expand...
Click to collapse
Thanks, but didn't do much... No, I don't think this build has wifi support yet. They are working on it though.
News?
Hello @ all...
i will test the rom from the first post later today on my Archos G9 101!
The last post was on 8th february, what´s up... is there a developing or not? Because i´m very interessted in this rom for my Archos!
Do anybody knows something about a ubuntu-rom for our Archos G9???
Thank you!
Echse27
Well, I didn't check their progress on it. I'm not really following it, I just did it more as a proof of concept and to get a taste of it. I saw that few builds have been compiled after this one, but I'm out of time to repackage it.
Echse27 said:
Hello @ all...
i will test the rom from the first post later today on my Archos G9 101!
The last post was on 8th february, what´s up... is there a developing or not? Because i´m very interessted in this rom for my Archos!
Do anybody knows something about a ubuntu-rom for our Archos G9???
Thank you!
Echse27
Click to expand...
Click to collapse
as I said earlier, this firmware is actively developed by Basyskom and should become the official firmware for SDE, but they're waiting for Archos to release ICS (with the new v3 linux kernel) hoping that the new kernel will fix the problems with WiFi and hw acceleration
o.k. thank you both!
I hope the offical ICS Build will be released soon.
I think the Archos G9 tab will be more potential with an full useable unix-system.
I´m looking forward to that! ;-)
Echse27 said:
o.k. thank you both!
I hope the offical ICS Build will be released soon.
I think the Archos G9 tab will be more potential with an full useable unix-system.
Click to expand...
Click to collapse
Well, quite logical and reasonable roadmap. But I do not expect much from KDE-based software. Out of all existing desktop environments, they selected the heaviest one, the least suitable for portables. Surely this is just to have fun and see if it can reallу fly (better to say, crawl) on a tablet. It is very unikely to be a viable product for everyday use.
Ubuntu version looks more promising, at least from performance viewpoint... if only it were not its destructive "innovations" like Unity and Ubuntu One...
Anyways, both have the same problems with hardware support, and both are waiting for the new kernel, first... Second, both will prove their inconsistence in the real life... Third, both will serve only as generic Linux booting platform, waiting for someone to compile a more realistic version. Probably it might be a Gentoo-based compilation with LXDE or XFCE - am I the only person in the world to whom this idea comes? 8-(( Sabayon team is now doing some moves in this direction, but their product is very heavy even for desktops...
iourine said:
Ubuntu version looks more promising, at least from performance viewpoint... if only it were not its destructive "innovations" like Unity and Ubuntu One...
Click to expand...
Click to collapse
Personally I'd love to see Xubuntu (or Lubuntu) running
iourine said:
Well, quite logical and reasonable roadmap. But I do not expect much from KDE-based software. Out of all existing desktop environments, they selected the heaviest one, the least suitable for portables. Surely this is just to have fun and see if it can reallу fly (better to say, crawl) on a tablet. It is very unikely to be a viable product for everyday use.
Click to expand...
Click to collapse
I have used Plasma Active on my Nokia N950 (developer phone, which has a 1ghz single core CortexA8 cpu + SGX530!!) and it was really fluid, I mean 60fps...
don't see your point about performance, given what I've seen on my n950
I tested this ROM yesterday evening...
I think you are right, when you say that there ist a lot of development need before it runs smooth on our devices!
It was very very slow but it looks very goog, i think.
No WLAN or 3G
some funktions are without any funktion! ;-)
realy slow... Booting tooks 15 min.
At this time, this rom isn´t allday useable.
Do anybody know something about a ubuntu-release for tabs like our.... like the old netbook-remix?
Any news about new Plasma-based firmware from Archos? A lot of time has passed since release of kernel v3.x...
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...
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.
Moretz Kernel 0.2.2 - Galaxy Note 8.0 EditionGT-N5110 & GT-N5100
Features:
Linux 3.0.101
Frandom
Network speed enhancements
Dynamic read ahead
CPU OC to 1.8GHz
GPU OC to 533MHz
CPU Voltage Control (OV/UV)
Tuned ZZMoove CPU governor (removed all other governors)
Intelligent CPU core hot plugging
Touchboost control, set to 800MHz
ARM CPU topology
LCD frequency switching (40Hz on screen dim, 60Hz on active)
Intelligent GPU scaling (Mali GPU control)
Lots of other fixes/tweaks
Intelligent zipalign at boot (init.d)
Intelligent sql db optimization at boot (init.d)
So, what's so special here?
A few things actually. I grabbed various code bits from many well known developers and worked some of my own magic on this build. First, I bumped the kernel up to 3.0.101 (FINAL) form kernel.org as a base on top of the stock CM 11.0 kernel. Once I pushed all of the enhancements listed above, I focused on tuning ZZMoove to balance performance and battery. I believe I've succeeded in that realm, so all other governors have been removed. This is a flash and forget kernel package. That's what makes it special ... the users do not have to do any tuning, it works, and it works well.
Credits:
Faux123, Andy P, googyanas, psndna88, ryukuri, sbrissen, Cyanogenmod team and may others. Please let me know if I missed you.
Source Code:
https://bitbucket.org/carvsdriver/android_kernel_samsung_smdk4412 (Moretz-New Branch)
Standard Disclaimer:
By flashing this you hold the developer (car vs driver) and anyone else not responsible or liable for any damage to your device, up to and including hard bricking. Basically, there's no warranty - flash at your own risk.
This release is not affiliated to CyanogenMod or Cyanogen Inc. This is my own personal work with lots of kangs from others.
This was tested with CM-11 on a GT-N5110 device. Any other devices or ROMs may not work or exhibit poor behavior. That being said, I only support use of this kernel with CM-11 and the GT-N5110.
Requirements:
Device - Samsung GT-N5110
ROM - CyanogenMod 11.0
XDA:DevDB Information
Moretz Kernel - Galaxy Note 8 Edition (N5110 & N5100), Kernel for the Samsung Galaxy Note 8.0
Contributors
car vs driver, psndna88, faux123, googyanas, AndiP, sbrissen
Kernel Special Features: GPU/CPU OC, UV/OV, UKSM, HotPlug, ARM Topology, LCD Freq Scaling, Linux 3.0.101
Version Information
Status: Stable
Current Stable Version: 0.2A
Stable Release Date: 2014-03-21
Created 2014-03-21
Last Updated 2014-07-03
Change Log:
Moretz 0.2.2 -- Upstream CM11.0 Changes Merged -- 7.4.2014
98865a3: n_tty: Fix n_tty_write crash when echoing in raw mode
7735075: mc1n2: Allow swapping of microphone ADC channels
ed8b659: smdk4412: update sound soc and codecs
5e96596: d710: build stage2 initramfs into kernel
8a5d38c: Fix CVE-2014-3153
6922ae0: Merge "synaptics_s7301: add disabling keypad" into cm-11.0
daf9635: Merge "smdk4412: cypress-touchkey - add keydisabler" into cm-11.0
fd94358: n_tty: Fix n_tty_write crash when echoing in raw mode
969b384: mc1n2: Allow swapping of microphone ADC channels
eba4e20: smdk4412: update sound soc and codecs
Moretz 0.2.1 -- Upstream CM11.0 Changes Merged -- 4.8.2014
c0dce37: dm crypt: optionally support discard requests
15b6c83: dm table: share target argument parsing functions
1886fef: dm: ignore merge_bvec for snapshots when safe
2b791d9: dm: suppress endian warnings
Moretz 0.2a -- Initial Release -- 3.21.2014
Instructions:
1. Download the flashable zip
2. Reboot into recovery
3. Flash the zip
4. Reboot
5. Done
I like to make things simple. Let your device boot up and that's it. No configuration necessary. But, if you want to screw with the CPU governor and ZZMoove settings, I made that easy for you. Just edit the zzmoove file in your init.d directory with the settings you want and reboot.
Click to expand...
Click to collapse
Code:
[CENTER][SIZE="5"][COLOR="Magenta"][B]GT-N5110 Download link:[/B][/COLOR][/SIZE]
[url]http://d-h.st/Gkd[/url]
[B]Version[/B]: Moretz-0.2.2
[/CENTER]
Code:
[CENTER]
[SIZE="5"][B][COLOR="magenta"]GT-N5100 Download link:[/COLOR][/B][/SIZE]
[url]http://d-h.st/ZyZ[/url]
[B]Version[/B]: Moretz-0.2.2
[/center]
Just a couple more things ...
Please do not post mirrors, if one is needed just let me know and I'll post one.
Please leave a review on this project by clicking here.
If you like my work, feel free to buy me a beer or pack of guitar strings by donating.
Click to expand...
Click to collapse
[/CENTER]
How to properly report bugs:
When reporting a bug, you must provide me with some very specific information so that I am able to either reproduce the problem or diagnose it based on logs. If you cannot provide information that I need, I cannot attempt fix the issue.
If the device is crashing:
Please make a copy of your last_kmsg immediately after rebooting the device.
Please make a copy of your logcat for the subsequent reboot.
Attach both files to your bug report and specifically state exactly what happens (are there steps to reproduce it?).
In all cases, please provide a logcat of when the issue occurs or specifically describe what is happening and how you can reproduce the error.
If you have any current issues prior to flashing my kernel, don't expect me to fix them.
The more detail you provide, the more helpful your bug report will be for me.
Feature Requests:
I'll make this one easy, I don't do feature requests. I used to do that, it became a real pain in the ass to keep everyone happy and the project I was working on bug free. Put simply, I put this together to work specifically for me and then decided to share it here. If at some point I decide to add new features, then I'll release new versions to you.
car vs driver said:
Reserved just in case.
Click to expand...
Click to collapse
I'm looking into building my own kernel for the konawifi because I feel like we need more kernel options, so thank you for this awesome customized kernel.
ztotherad said:
I'm looking into building my own kernel for the konawifi because I feel like we need more kernel options, so thank you for this awesome customized kernel.
Click to expand...
Click to collapse
You're welcome, that's what this one is for. Makes the device scream and battery life is excellent.
Sent from my Nexus 5 using XDA Premium 4 mobile app
car vs driver said:
You're welcome, that's what this one is for. Makes the device scream and battery life is excellent.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
freakin' nice. definitely can't wait then! thanks again for your awesome gift to the Note 8.0 family.
is n5100 model will be supported in next future ?
messi2050 said:
is n5100 model will be supported in next future ?
Click to expand...
Click to collapse
Would you be willing to test? Only reason I didn't publish for n5100 is because I don't have one to verify that I didn't break anything.
I just have to update a few configs and run a new build, let me know.
as an owner of the n5100 I´ll be very interested in your work. so my first question - will this kernel work with probam 1.3.2? maybe I could test it
redukt said:
as an owner of the n5100 I´ll be very interested in your work. so my first question - will this kernel work with probam 1.3.2? maybe I could test it
Click to expand...
Click to collapse
I suppose it should, I did a quick check and looks like that ROM uses the same base 3.0.y kernel that CM 11.0 does. The partition scheme on the devices is the same too (both devices us /dev/block/mmcblk0p5 for the boot partition) ...
There's only one real way to find out though, someone has to flash it - worst case is that it doesn't boot up.
Go ahead and give this a rip and let me know how it goes. It's the same build as the OP with the 5100 defconfig updated to include the features that I added for the 5110.
Download:
REMOVED ... SEE OP FOR DOWNLOADS
MD5:
7864a8e5eb18321c2201cba314fc7a06
If it doesn't boot, just reflash your previous ROM - that'll replace this kernel with whatever one is included there.
Yeah, kernel runs nice So I`ll kept my device on standby, make a wow raid and check the battery stats
Thx for your hard work
Assuming all goes well, I'll update the op to state that both devices are supported and working.
Sent from my Nexus 5 using XDA Premium 4 mobile app
car vs driver said:
Would you be willing to test? Only reason I didn't publish for n5100 is because I don't have one to verify that I didn't break anything.
I just have to update a few configs and run a new build, let me know.
Click to expand...
Click to collapse
i'm using original rom 4.1.2 now so i can't test it sorry
3,5 h standby time loosing NOTHING in battery percentage - full 100% So I`ll check this tomorrow and report my results
edit: very nice
{
"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"
}
edit: bug: no 3g network :/
Hmmm ... no 3G? Y'know what, I think I know why. I'll post another build for you to test in a bit.
Edit: @redukt .... give this one a rip: <EDIT>SEE OP FOR DOWNLOADS.</EDIT>
car vs driver said:
give this one a rip:]
Click to expand...
Click to collapse
3G runs now
Many thanks for your quick reply
Excellent. I'm going to update the OP and support both devices then. Thanks for the quick turn around with testing, I appreciate it.
does anybody tested it on AOSB rom?
lolek2382 said:
does anybody tested it on AOSB rom?
Click to expand...
Click to collapse
yeppp, runs with AOSB 1.3.2
car vs driver said:
Hmmm ... no 3G? Y'know what, I think I know why. I'll post another build for you to test in a bit.
Edit: @redukt .... give this one a rip: <EDIT>SEE OP FOR DOWNLOADS.</EDIT>
Click to expand...
Click to collapse
3G is working on my N5100 did I download the updated file just install a few minutes ago oh thankyou for supporting our tab the the Devs on the the better