KDE Plasma Active two is a beautiful display manager for embedded devices. Its currently based on MeeGo. Porting is a very difficult task. I would therefore like to be contacted by aspiring developers who would like to help me in this project.
For those of you who don't know what Plasma Active is. It is the Mobile/Tablet version of the popular Desktop Environment/Display Manager KDE. Screenshots below.
Pull Down App Menu.
{
"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"
}
Time And Date Settings
Activity Screen (activity switcher on the left)
YouTube Demonstration
Is that even possible for our devices O.O you have the courage of a jedi...
wow. its look really good. hope that there will be another dev to help u with that
I guess the easiest way is to just run it in chroot and connect via vnc. I.E., just install it in ubuntu chroot.
It may be tempting to run it natively, but there are obstacles.
1. I9100 has unified kernel for boot/recovery, so you cannot, say, replace recovery with custom kernel and boot android/meego based on which keys you hold
2. I9100 stock kernel has a lot of hacks and non-standard/broken drivers (touchscreen, framebuffer) that will need patching/fixing to work with native GNU/Linux build
3. There are no Mali400 opengl/egl libraries for exynos and GNU/Linux. I have not tried ones from st-ericsson u8500, but I guess they should work.
I have been porting i9100 support to vanilla kernel with the aim of running meego or, at least, SHR. I got linux 3.2.0 booting with half hardware working, but there are things to do. Some drivers need rewriting because my aim is to clean them up and submit to vanilla kernel.
-modem driver needs rewriting (userland power interface, better modemctl replacement)
-sensors drivers need rewriting (replace userland interfaces with input/iio like done for mainlined drivers)
-sound driver needs major rewriting (it is too complicated and does not even compile on 3.2. not to say it's crap and will never get accepted mainline in its current state)
-suspend and cpufreq are broken.
-mali400 needs porting from linaro tree
Other hardware (touchscreen, wifi, bluetooth, microsd, internal mmc, camera LED, camera, battery) are working though
sp3dev said:
I guess the easiest way is to just run it in chroot and connect via vnc. I.E., just install it in ubuntu chroot.
It may be tempting to run it natively, but there are obstacles.
1. I9100 has unified kernel for boot/recovery, so you cannot, say, replace recovery with custom kernel and boot android/meego based on which keys you hold
2. I9100 stock kernel has a lot of hacks and non-standard/broken drivers (touchscreen, framebuffer) that will need patching/fixing to work with native GNU/Linux build
3. There are no Mali400 opengl/egl libraries for exynos and GNU/Linux. I have not tried ones from st-ericsson u8500, but I guess they should work.
I have been porting i9100 support to vanilla kernel with the aim of running meego or, at least, SHR. I got linux 3.2.0 booting with half hardware working, but there are things to do. Some drivers need rewriting because my aim is to clean them up and submit to vanilla kernel.
-modem driver needs rewriting (userland power interface, better modemctl replacement)
-sensors drivers need rewriting (replace userland interfaces with input/iio like done for mainlined drivers)
-sound driver needs major rewriting (it is too complicated and does not even compile on 3.2. not to say it's crap and will never get accepted mainline in its current state)
-suspend and cpufreq are broken.
-mali400 needs porting from linaro tree
Other hardware (touchscreen, wifi, bluetooth, microsd, internal mmc, camera LED, camera, battery) are working though
Click to expand...
Click to collapse
My workflow would be :-
extract boot.bin from device
split into kernel, initrd, commandline
recombine to boot.bin
reflash to device
if it still boots andriod move on to
get kernel source and compile
combine new kernel zImage with commandline and initrd
flash to device
if it still boots android move on
edit kernel commandline to set root=/dev/mmcblkXp2 init=/sbin/init to pick up plasma active on partition 2 of a sdcard I have prepared or copied form Archos G9 images on web.
kernel should have a framebuffer device so I can see things but won't be accelerated unless I have Mali drivers for X11 backend, don't think we have seen any working baseband stuff so I don't expect to make calls.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By George I've got it! Not really actually but I do have a pre-alpha release of kubuntu mobile edition running on my gen 8 tablet
check it out here: http://forum.xda-developers.com/showthread.php?t=1052697
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Here are some semi-complicated instruction for creating a bootable KDE mobile install on Archos gen 8 devices for self.
https://wiki.kubuntu.org/ARM/Archos101it
Hi,
You have prebuilt image for n900 there http://cdimage.ubuntu.com/kubuntu-mobile/daily-preinstalled/current/
As it is same processor, you can try, i m doing the test right now.
Babelo
BabelOued said:
Hi,
You have prebuilt image for n900 there http://cdimage.ubuntu.com/kubuntu-mobile/daily-preinstalled/current/
As it is same processor, you can try, i m doing the test right now.
Babelo
Click to expand...
Click to collapse
Yes I saw that but the touchscreen doesn't work. I've actually managed to compile it (you can find my new thread in the developer forum section) I'll add the download link on the new thread in a few hours. The major problem is that my current "build" takes my to the login screen but because there is no virtual keyboard, I can't log in
http://forum.xda-developers.com/showthread.php?t=1052697
It seems workable, but how about 70?
LeoNg628 said:
It seems workable, but how about 70?
Click to expand...
Click to collapse
I have an archos 70, that's what I'm testing it on.
shrewdlove said:
I have an archos 70, that's what I'm testing it on.
Click to expand...
Click to collapse
but he said virtual keyboard is not working and the touch screen is not response sometime.
LeoNg628 said:
but he said virtual keyboard is not working and the touch screen is not response sometime.
Click to expand...
Click to collapse
I use the word "test" loosely, I mean the archos 70 is the device I am testing the .img's I am compiling. I now can log in but the touch screen is still acting weird. You will be able to test it out in a few hours when the .img finished uploading.
This thread is pretty much dead so I suggest you check out my other developer thread, which is the one will be on mainly
http://forum.xda-developers.com/showthread.php?p=13243471#post13243471
I know I should post this to the new thread in the Gen8 Android Development section, but I'm new to the forums and can't post there yet. We know the kernel is fine since we get the kernel and modules from Angstrom. The major issue I see is that Angstrom has some highly customized init.d and rc.* scripts, as well as a ton of udev and xmod files not found in kubuntu by default. The Angstrom xorg.conf doesn't even include this line:
"Option "Device" "/dev/input/by-id/usb-UNITEC_USB_Touch__Win7_-event-if00"
So I'm sure if we traverse through what's in the Angstrom rootfs.img we should find our answer to at least the touchscreen.
Try taking a look at the archos-init.sh script in the /etc folder of Angstrom.
The modifications made on Angström to make it work on Archos are all told on the Archos website, (on the same page where you download the SDE, the button under the "Download AOS" one)
Well... Yes and No
Angstrom is built using a system called OpenEmbedded (OE). OE works much like rootstock but is a little bit more advanced. It not only allows you to build a .img from a certain distro (in this case Angstrom) but also allows you to build for specific embedded devices. Right now though the newest Archos devices aren't located in the OE repo yet, so what's on the site that your seeing is actually an overlay that goes over what you download from OE that has the configs to tell OE how to built for the Archos Gen 8 architecture. It doesn't actually contain any changes to the scripts or files.
Very interesting guys, thanks a lot.
MysticMgcn said:
I know I should post this to the new thread in the Gen8 Android Development section, but I'm new to the forums and can't post there yet. We know the kernel is fine since we get the kernel and modules from Angstrom. The major issue I see is that Angstrom has some highly customized init.d and rc.* scripts, as well as a ton of udev and xmod files not found in kubuntu by default. The Angstrom xorg.conf doesn't even include this line:
"Option "Device" "/dev/input/by-id/usb-UNITEC_USB_Touch__Win7_-event-if00"
So I'm sure if we traverse through what's in the Angstrom rootfs.img we should find our answer to at least the touchscreen.
Try taking a look at the archos-init.sh script in the /etc folder of Angstrom.
Click to expand...
Click to collapse
Do you have any idea if I could build an ubuntu or kubuntu .img with openembedded and then apply archos's changes to that. I've been looking for some documentation but all I have found so far is documentation relating to angstrom.
While it should be possible, as you've seen documentation is lacking for OE and I've personally had a lot of issues with it just from trying to create my own stock Angstrom .img to see how it worked. Plus it just seems like a lot of work as you have to create BitBake (.bb) files for the programs you want to install, compared to using rootstock and just being able to call out the programs you want installed by default with the --seed switch.
I think we're really a lot closer than we realize to start from scratch with OE. We have the kernel and drivers in place as well as the filesystem, we just don't have a way to tell the system to load the drivers the way they need to be loaded through either udev or init.d/rc.d*.
Well the problem was with udev and I've gotten the mouse to work without the need for an xorg.conf. I'll post more when I can but I may scrap this as everyone lost interest. I'm building a new image from Natty instead of Maverick anyway where udev isn't so flaky.
Sent from my PC36100 using XDA Premium App
ive actually been waiting on a work img, the last one i used just gave me an error msg. i'm not afraid to test anything out.
shrewdlove said:
Here are some semi-complicated instruction for creating a bootable KDE mobile install on Archos gen 8 devices for self.
https://wiki.kubuntu.org/ARM/Archos101it
Click to expand...
Click to collapse
I tried the instructions listed there and they DO NOT WORK. Here's what I did step by step. When I boot the device into developer mode, I get the boodting developer editon screen, but never any hits of kubuntu.
Interestingly, if I try to restore a backed up copy of the Linux Angstrom img it won't boot that either. I have to go back and re-install the SDE to get it to boot in developer mode again.
Hi Folks,
I create new thread just for easy that we focus on kernel building here and continue with rom on existeing thread
This kernel is almost all standard very minor changed. config based on "prebuilt" Q8650_perf_defconfig. ramdisk is from 408 firmware. I installed 408 rom by olleh (odexed ... duhhhh). No optimation have been made since I have no idea what should be optimized. Give me idea ... LOL
- download zip file from this thread > no heavy since only 3.3 MB flashable via CWM. Get CMW from TheManii (my Guru in android compilation). See the kernel version is x1123
{
"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"
}
what you get :
- customs kernel
- fully rooted system i.e you can do on fastbot $adb remount to have write access to device.
- suggest flash TheManii Streakdroid4-250 and immediately flash this kernel.
The main reason SD4 250 is hard to install is due to using a stock kernel, it's also the reason I havnt released SD5 250 at all (as there's plenty of alternatives)
If you're willing: just make a kernel with as little changes as possible, but with signature checking disabled for /system apks.
I dont think it's as simple as setting ro.secure=0 as I've made a modified ramdisk and it still fails on modified apks (pretty much every one in SDx 250 as I've added langs back to them)
I dont think I have the time to also learn how to recompile entire kernels, esp since SDx 25x is primarily intended for my own use. But I'd def like to release it with a modified kernal that would allow users to install it easier.
Hi TheManii.
This is my first time recompile linux kernel for android. It is really pain (comparing to recompile for PC). I will check and surf how to do your request. Just currious .. it is the kernel controlling /system/app/*.apk (?) ... need to check and learn kernel code then.
btw installing SD4-250 with default kernel I face FC many times when do setting on sound, receiving incoming calls, connect device to pc via usb port etc. But after flashing my kernel all FC gone ... I personally not sure it is because of kernel. But my venue now run smoothly powered by your SD4-250.
Btw I search on google and no lucks. How to get and add baseband (radio) file on ROM. I succeed to build a plaint rom can live on venue but always lack of GSM function. I dont think it caused by ril.d (ril_htc_d for htc) which is binary (?) or any ril_dell_d ... available
would you release SD5-250 ROM and let us work to do something to make dell venue have more options of customs rom.
Folks,
I can build a version of kernel-v4.06 myself. Run smoothly, no problem found so far. x1123's guide, if strictly followed, can bring such result to you.
It will be the best if you make it little under volt
sent via xda app
chacona said:
Folks,
I can build a version of kernel-v4.06 myself. Run smoothly, no problem found so far. x1123's guide, if strictly followed, can bring such result to you.
Click to expand...
Click to collapse
Navigation and maps crash when using your otherwise smooth running kernel. Can you please look into it.
Sent from my Dell Venue using Tapatalk 2
{
"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"
}
Welcome everyone! I would like to present you with the Official Support thread of the Linux On Android project for the HTC Droid DNA (DLX). In this thread I will answer questions among other things that you may require. I am available to help anyone of all levels. Please do not hesitate to ask questions or provide feature suggestions! This is also a development thread so remember this when you post! Just please remember the search function. Cheers!
What is this all about?/Why put this on my device?
This projects aim is to bring a range of linux distros to your android device through a method known as 'chroot', see it has running a linux distro within a virtual machine on your phone (Although its not! its using native ARM ports and the Android kernel) . You can access this virtual machine and run it on your phone without causing any damage to your device, or having to overwrite anything. Why might you want this? well my apps are designed to make the install and set up process as easy as possible while still giving you some flexibility. Once you have the distro up and running then you can pretty much run and install any linux software you like (so long as there is an arm port or it is not architecturally dependent).
Wait this uses VNC why shouldn't I just VNC to a computer?
VNC is used to access the GUI as at the moment I have not yet implemented a native way of viewing the GUI. But the Linux distro itself is running within the phone and can be controlled via the terminal app so if your a seasoned Linux user you may never even want to use the GUI
What is Chroot?/How does this work?
"A chroot on Unix operating systems is an operation that changes the apparent root directory for the current running process and its children" - http://en.wikipedia.org/wiki/Chroot
This method of running linux distros with android has been around for some time. I have worked on my scripts to make the process more user friendly and give you far more options from the word go.
The scripts start by mounting the linux image file within the android file system and then mounts the sdcard and if you have it internal memory within the linux file system.
Chroot is then used to change the root directory to that of the mounted linux and a bash shell is then opened to allow you to control linux this is kind of like 'booting' the OS.
The likes of VNC and SSH are then set up when linux is 'booted' to allow you to connect to the GUI if you require it.
Interested?
Ok so you want to get one of the support linux distros on your device, great welcome to the team
But first you will need to find out if your device is compatible with the method before anything else, this method 'should' work with pretty much any device but some ROM's/kernels will not work as they do not have loop device support etc.
HERE is a list of working devices and ROM's/kernels but remember just because its not on the list simply means no one has told me its working, it could still work!
Free Apps/Files
App
The App can be download via google play or the open source version can be download via source forge.
Love the project?
Well there are plenty of places you can show your support, of cause you can buy the paid apps, but you can also 'follow' the project on a range of social networks and also keep up to date with news on the projects blog!
Main Site
Sourceforge
Facebook
Twitter
Google+
IRC Channel = #linuxonandroid-dev (This is only for development not support!) #linuxonandroid-help (for help!)
Current Contributors
Project Developers
Zac Powell aka zacthespack
Martin Møller aka tuxling
William Means(myself) aka WEM97
App Translators
Marco Robles - Spanish Translation
Quentin Khan - French Translation
Stefanie Jung - German Translation
Ove Grunnér - Swedish Translation
Nikolay Suknyarov (NikolayS) - Bulgarian Translation
Other Contributors
Johan Vromans
Marshall Levin
Barry flanagan
Device Fund Donators (Those that donated to the device fund that ran from 26/08/2012 till 26/09/2012 and selected a perk)
scottlsteele
aceler
kailuuu
mja747
chrisindie
buki1
mharris867
never__sleep__again
joe95
jmoran1
fedebot
vichev.jordan
apadsethlang
1llu510n157lynx
innovateworld
karrth
AlexanderBalakersky
normenkdindiegogo
MORAZA.E7575
FilipJoelsson
brousch
igray78756
hawkinja
sullytrny
Donators (Those who have donated £5 or more to the project)
Davide Amatobene
Helder Carreiro
Aaron Coakley
Leo Barnard
Gregory Harrison
Chirado OHG
Infamous Webs
Matthew Collins
Rene Donker
David Marceau
Roberto Colistete Jr
cnbuff410
Javier Orozco
Jicaraca
Mine as well!
Q&A for [Dev/Rom] Sero 7 Pro taktiK Android 4.4.2 R13 available
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Dev/Rom] Sero 7 Pro taktiK Android 4.4.2 R13 available. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Awesome ROM
randomblame said:
This is taktiK a highly modified cm11 based rom for the US 8gb Hisense Sero 7 Pro! This is not compatible with the 32gb uk version (if you have one get in touch with me and maybe we can make it compatible)
{
"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"
}
Working:
wifi
hdmi - no audio
bluetooth - no a2dp
audio
usb mtp/ptp
sensors
GPS
Sdcard - both real and emulated now working with mtp
NFC
Selinux - enforcing
Overclocking - set at 1.5ghz default
mp3 playback
usb otg storage
Cameras
torch
netflix
not working:
audio over hdmi
a2dp
*with R13 certain builds of google apps will cause a no boot situation if you wipe /data and install the rom and gapps together before booting android. Setup wizard craps out and never gives you a usable system. TO FIX: wipe data and cache, install rom, then boot to android BEFORE flashing gapps. from android reboot to recovery and install gapps and you'll be golden.
My device tree and vendor tree are open source to encourage development on this awesome device:
Device Tree
Vendor Tree
Download
taktiK R13: http://goo.im/devs/randomblame/sero7pro//tt-4.4-20140225-Release13-m470.zip
Gapps: http://forum.xda-developers.com/showthread.php?t=2012857
Stock rom compatible kernel with taktik features and improvements
taktiK Kernel and module installer for stock based roms (version2): http://jellytime.googlecode.com/files/taktiK_Kernel_for_Stock_v2.zip
Current builds use selinux and require the latest version of cwm or twrp (linked below) to install.
RECOVERIES:
CWM (swipe + selinux enabled) Recovery: http://jellytime.googlecode.com/files/cwm6.0.4.5-selinux-flashable-sero7pro.zip
Twrp recovery (selinux enabled): http://jellytime.googlecode.com/files/twrp2.6.3.0-selinux-flashable-sero7pro.zip
Twrp themed (selinux enabled): http://jellytime.googlecode.com/files/twrp2.6.3.0-themed-selinux-flashable-sero7pro.zip
Installing this rom requires that you have first rooted and installed a custom recovery. If you have not start reading:
http://forum.xda-developers.com/showthread.php?t=2297246
http://forum.xda-developers.com/showthread.php?t=2284022
in progress 3.4.y kernel:
Kernel source (3.1.10 Stable): https://github.com/randomblame/android_kernel_hisense_m470
Kernel source (3.4.y Work In Progress): https://github.com/randomblame/android_kernel_hisense_3.4
Thanks:
davepmer for having the patience to figure out the blob combinations for camera
Click to expand...
Click to collapse
Audio over HDMI works pretty fine for me, on one of my TVs tho. Ithink it's a TV thing.
dead s7p questionable rtc battery is vibrator motor
I could be wrong, but somehow, I doubt that there would be any other battery in your tablet aside from the main one.
Generally, these things run all of their circuits off of the one battery. It makes for a simpler design. Besides, they're pretty well just like phones, but without the 3/4 g radio. There is no solitary BIOS chip since these use the SOC (system on a chip) package design.
It's typically the pc that needs the secondary battery, and that's just to hold the bios settings. The only reason all of this is necessary is because of the different modular components that the BIOS MUST initialize during the POST routine.
My bet is that your problem goes beyond that into some hardware failure.
sero 7 pro taktik download link broken?
Every time I try to download the r13 version it tells me webpage not available
{
"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"
}
Call for all kernel devs with a Sony Z5 Compact who would like to help out building an official NetHunter kernel for that device.
I've started on a NetHunter kernel with support for HID keyboard and mouse, injection, nexmon, & rtl8812au but the HID patch seems to cause a bootloop (might be something else though). I don't have that device and the person requesting it doesn't have a computer.
I've used the NetHunter kernel-builder:
https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
with this local.config:
https://gitlab.com/kalilinux/nethun....config.examples/local.config.example.suzuran
and with these kernel sources:
https://github.com/Re4son/android_kernel_sony_msm8994/tree/nethunter-14.1
following this guide:
https://www.kali.org/docs/nethunter/nethunter-kernel-1-patching/
We need someone that can rollback our commits and find the one that caused the bootloop (maybe the switch from perf to interactive?) and help fixing the offending commit.
Any help will be greatly appreciated.
Thanks heaps,
Re4son
Just received feedback from the person claiming that it was the HID patch which caused the bootloop; he didn't actually test it and just assumed that the issues were caused by that patch.
I'm pretty sure that it wasn't that patch. This bit of info might open the door to kernel hackers that don't want to play with USB drivers
Great project for Sony
Welcome all kernel hackers.. Its free guys, try please..
upp guys..
and 1 upp...
not so hardd..
@yesimxev
@kimocoder
helpppp
If I remember correctly I applied the nexmon patch with nethunter and that's when I experienced problems; more likely that, if the problem isn't fixed yet. BTW, is this Nethunter running a 4.14 kernel in a chroot shell or is this an actual patch to the existing boot.img for 14.1? I can modify the commit, but am unsure how to build an install.(Android SDK)?
&(*) said:
If I remember correctly I applied the nexmon patch with nethunter and that's when I experienced problems; more likely that, if the problem isn't fixed yet. BTW, is this Nethunter running a 4.14 kernel in a chroot shell or is this an actual patch to the existing boot.img for 14.1? I can modify the commit, but am unsure how to build an install.(Android SDK)?
Click to expand...
Click to collapse
kernel version generally doesnt matter. you need to git clone your kernel source and patch then recompile, and you will get Image.gz-dtb or zImage .
https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
Re4son,
Looking at the kernel builder source ( https://github.com/Re4son/android_kernel_sony_msm8994 ) indicates this is dedicated to certain build versions, am I mistaken ? I tried installing this through the .zip installer for 7.1.2 and notice in prompt that patching the boot fails, but the rest installs. I managed to patch the boot image (https://gitlab.com/kalilinux/nethun...ethunter-devices/-/tree/master/nougat/suzuran) , but am unsure if ramdisk needs other libraries as well or if the kernel does (nexmon-fw & system)? Mainly trying to accomplish manually patching of the kernel and installing the rest with the installer if possible. Please advise as to the proper method to get everything in it's right path for Nethunter to be running correctly.
Re4son said:
Call for all kernel devs with a Sony Z5 Compact who would like to help out building an official NetHunter kernel for that device.
I've started on a NetHunter kernel with support for HID keyboard and mouse, injection, nexmon, & rtl8812au but the HID patch seems to cause a bootloop (might be something else though). I don't have that device and the person requesting it doesn't have a computer.
I've used the NetHunter kernel-builder:
https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
with this local.config:
https://gitlab.com/kalilinux/nethun....config.examples/local.config.example.suzuran
and with these kernel sources:
https://github.com/Re4son/android_kernel_sony_msm8994/tree/nethunter-14.1
following this guide:
https://www.kali.org/docs/nethunter/nethunter-kernel-1-patching/
We need someone that can rollback our commits and find the one that caused the bootloop (maybe the switch from perf to interactive?) and help fixing the offending commit.
Any help will be greatly appreciated.
Thanks heaps,
Re4son
Click to expand...
Click to collapse
is this type support nethunter ? i see in wikipedia, suzuran is 3 type = E5803, E5823, SO-02H.
i see in the market, sony xpesia z5 compact is many type like this picture :