Hi All,
Who I Am: My name is Mauro Ribeiro I'm from Brazil and I HATE long walks its gets even worst if its on the beach. I have 15+ years of experience on Linux, 5+ on Java. I do work as a Network Admin for a Large Brazilian Company.
Why: It comes my time to help this nice community that gaved me so much.
What: Linux Kernel 3.0.15 based on Samsung sources with Speedmod Patch's.
This kernel DOES NOT HAVE MMC_CAP_ERASE so it SHOULD be safe.
Its basicly Speedmod K3-3 Kernel with A TON OF MODULES. There are modules for USB Ethernet, USB Sound, USB Serial and Much much more.
BE CAREFUL WHEN YOU LOAD MODULES, MODULES USES MEMORY AND MEMORY IS A PRECIOUS RESOURCE.
MODULES ARE AT: /data/local/modules
IF YOU DON'T KNOW HOW TO LOAD A MODULE THIS KERNEL IS NOT FOR YOU.
ITS NOT A DAILY DRIVER KERNEL HAS ALOT OF STUFF. ITS FOR TESTING.
Be patient when I say that I'm working on something, My computer is a P3 with 1 Gig of ram. So everything takes time and I have to work too.
I'm 100% open to sugestions. Wanna chat about this kernel? I'm mdrjr @ freenode! come on IRC and chat with me. Leave this topic for development only.
I'm always at #project-voodoo .. come and chat.
DON'T PM ME. COME AND CHAT
Attached file is a ZIP that SHOULD BE FLASHED THRU CWM!
kernels are at:
http://www.mdrjr.net/kernel
v5:
Now that modules aren't on initramfs anymore
We have USB Serial and USB Wifi adapters!
YAY!
Let your BackTrack / Wifi Sniffing go
Also, moved files from XDA to my Hosting.
v4:
Added some missing stuff.
Build another TON of modules.
To make kernel smaller and friendly on RAM. Modules from now on will be at /data/local/modules.
v3:
Fixed some errors most of the stuff is pre-built inside the kernel now.
Removed USB-Serial Support. Ask me if you need this back.
v2:
Some idiot (ME) forgot that hardcore disable's logging for his kernel I have it enabled now.
Enabled logging and more logging.
v1:
Samsung ICS update 3 + Speedmod Patch K3-3.
Compiled with a tons of modules
modded initramfs
PS: Sorry for the typo on the date or.. i'm posting from the future.
Thanks goes to:
Linux (Linus)
Google (Android)
Samsung (For the phone)
Francisco Franco (For his work that I stoled... sorry, just few lines of code I'm using on this kernel)
Speedmod (For releasing all his work too and making this possible)
Chainfire (Plenty of instructions around and his work for android is HUGE)
Supercurio (Greate guy talked couple of lines with him. And his awesome job on Sound/Video on android)
If I'm missing someone else.. PM and I'll give you credit.
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Inviato dal mio GT-N7000 con Tapatalk 2
You should not include the modules in the initramfs. The initramfs is always in memory, so this way the modules waste the precious RAM even if not loaded. It is better to have them on the large emmc partition.
BTW, the kernel's copyright license is GPL, a link to the binary should always be accompanied by a link to the source.
MatanZ said:
You should not include the modules in the initramfs. The initramfs is always in memory, so this way the modules waste the precious RAM even if not loaded. It is better to have them on the large emmc partition.
BTW, the kernel's copyright license is GPL, a link to the binary should always be accompanied by a link to the source.
Click to expand...
Click to collapse
Its on the OP KERNEL IS SPEEDMOD KERNEL! Get the source from there. Its the same source.
And again on OP its a NOT A DAILY DRIVEN KERNEL. ITS FOR TESTING ONLY.
gattari said:
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
I don't know what Chipset your USB DAC uses ;( sorry.
mdrjr said:
IF YOU DON'T KNOW HOW TO LOAD A MODULE THIS KERNEL IS NOT FOR YOU.
Click to expand...
Click to collapse
gattari said:
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Click to expand...
Click to collapse
No no, dont fill development threads with this rubbish - google it and learn - then you can use this
panyan said:
No no, dont fill development threads with this rubbish - google it and learn - then you can use this
Click to expand...
Click to collapse
I simply want to test usb + dac.
I don t able to test no problem I don t test.
Pardon for rubbish.
Inviato dal mio GT-N7000 con Tapatalk 2
gattari said:
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
A lot of USB DAC's are supported by the USB audio soundcard standard. The E7 (note not the E17) is confirmed to be working on S3. Some users have suggested a firmware upgrade for the E17 might solve things. Things are moving along nicely though. It seems Samsung are ahead of us but being tight lipped about it.....
Can't load module.
insmod says
'unknown symbol in module or invalid parameter'
Also I found this, it details what modules the Nook Colour Dev team took to enable usb DAC.
Looks like we're missing a module?
insmod /drv/snd-hwdep.ko
insmod /drv/snd-rawmidi.ko
insmod /drv/snd-usbmidi-lib.ko
insmod /drv/snd-usb-audio.ko
From this page
Also, @mdrjr where can I find you on freenode?
krypton_the_slayer said:
Can't load module.
insmod says
'unknown symbol in module or invalid parameter'
Also I found this, it details what modules the Nook Colour Dev team took to enable usb DAC.
Looks like we're missing a module?
insmod /drv/snd-hwdep.ko
insmod /drv/snd-rawmidi.ko
insmod /drv/snd-usbmidi-lib.ko
insmod /drv/snd-usb-audio.ko
From this page
Also, @mdrjr where can I find you on freenode?
Click to expand...
Click to collapse
#project-voodoo
and Yes, I got that issue as well... rebuilding stuff now.
mdrjr said:
#project-voodoo
and Yes, I got that issue as well... rebuilding stuff now.
Click to expand...
Click to collapse
Another xda dev pointed me to this dmesg output from an s3 when connecting a c media dac
http://pastebin.com/nHmTRUN6
This is something like we'll see on success.
Sent from my GT-N7000 using XDA
nice job
but too many logging may cause battery goes faster?
Anyone test the module for usb dac?
Cmedia I suppose.
Inviato dal mio GT-N7000 con Tapatalk 2
Qoome said:
nice job
but too many logging may cause battery goes faster?
Click to expand...
Click to collapse
Yes.. it may cause battery and RAM usage.
krypton_the_slayer said:
Another xda dev pointed me to this dmesg output from an s3 when connecting a c media dac
http://pastebin.com/nHmTRUN6
This is something like we'll see on success.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Drivers are built-in on V3. You shouldn't need any modules to get it working.
Wow I don't know much about kernels but os this mean I can connect external usb dac like galaxy s3? I like that! Now my note will be an ultimate sound machine!
Sent from my GT-N7000 using XDA
Well done and thanks mdrjr , we have the device (cheap c-media, but it conforms to usb generic audio) recognised, listed under /dev/snd and
alsa-aplay -l
gives
{
"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"
}
And also a bunch of new devices listed in /dev/snd
audio1
controlC1
dsp1
mixer1
pcmC1D0c, pcdC1D0p
Now for a bit of alsa.conf hacking!
For others reading, if you have a USB DAC and are rooted on a Samsung based ICS ROM, if you want to test, first, download and flash the kernel from CWM (reboot recovery, flash zip from sdcard, flash M1v3.zip) reboot
then please download Alsamixer from the Market - link below. It will install ALSA components and a handy app, (please be careful with it, you can damage you speakers/possibly hearing!)
https://play.google.com/store/apps/details?id=com.skvalex.alsamixer&feature=nav_result#?t=W251bGwsMSwxLDMsImNvbS5za3ZhbGV4LmFsc2FtaXhlciJd
And install a terminal app
Then in a terminal type these
su
alsa_aplay -l
If you have more than one device listed, should be USB generic audio, then you have advanced to level 1 on the "get usb audio on my note" challenge!
If it says anything other than USB generic audio, let us know what. There is a chance that many more devices can be supported, if they work under a linux environment. So feel free to test there first.
Next up, custom alsa.conf configuration - level 2!
Still testing, but Alsamixer app might yeild some results if you play with it but I think we need an entry in alsa.conf or somewhere first.
Big boss at the end of level 3 will be a custom app for selecting input/output devices
I tried appending this code below in /system/etc/asound.conf
pcm.!default {
type plug
slave {
pcm "hw:1,0"
}
}
This is pretty much what others have been doing (same code to get USB devices working under linux)
And I tried various other ways of doing the same thing but ultimately got the output below each time :-( You can see I used a standard PCM 16bit stereo 44kHz wav file.
[email protected]:/sdcard # alsa_aplay -D plughw:1,0 test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1117: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 88200
TICK_TIME: 0
not sure if I'm missing something in asound.conf or if we're missing support in another library.
EDIT:
I've been poking around other sources that have USB audio support working.
One suggestion is that the order of module loading matters, and I wonder how we are affected since you compiled all the drivers into the kernel.
The drivers in order of insertion others are using are as follows
snd-hwdep.ko (this is part of speedmod kernel)
snd-rawmidi.ko
snd-usbmidi-lib.ko
snd-usb-audio.ko
Don't know about the order of these but pretty sure they're essential
snd-mixer-oss.ko
snd-pcm-oss.ko
krypton_the_slayer said:
I tried appending this code below in /system/etc/asound.conf
pcm.!default {
type plug
slave {
pcm "hw:1,0"
}
}
This is pretty much what others have been doing (same code to get USB devices working under linux)
And I tried various other ways of doing the same thing but ultimately got the output below each time :-( You can see I used a standard PCM 16bit stereo 44kHz wav file.
[email protected]:/sdcard # alsa_aplay -D plughw:1,0 test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1117: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 88200
TICK_TIME: 0
not sure if I'm missing something in asound.conf or if we're missing support in another library.
EDIT:
I've been poking around other sources that have USB audio support working.
One suggestion is that the order of module loading matters, and I wonder how we are affected since you compiled all the drivers into the kernel.
The drivers in order of insertion others are using are as follows
snd-hwdep.ko (this is part of speedmod kernel)
snd-rawmidi.ko
snd-usbmidi-lib.ko
snd-usb-audio.ko
Don't know about the order of these but pretty sure they're essential
snd-mixer-oss.ko
snd-pcm-oss.ko
Click to expand...
Click to collapse
Loading sequence does matter that's the main reason to leave it to kernel handle.
When you build modules as built-in kernel keeps the loaded all time at ram so you don't have to worry about loading.. its all there.
I'll check and see if snd-mixer-oss and snd-pcm-oss are there...
Meanwhile can you run alsa_aplay -D plughw:1,0 -vvv test.wav
and give us the output? getting that extra verbosity may help.
no difference with more verbosity
Sent from my GT-N7000 using XDA
Related
CM9 4.0.4 ICS HTC Desire C (Ice Cream Sandwich)
Here is development thread for Desire C
I'm not responsible if you do something wrong to your phone using this rom, so you doing that on your own risk!
Currently working and not working:
What works:
Auto-brightness
Bluetooth
Browser
Keyboard
Overclocking
Phone radio (calling, sms, data)
Sensors (light, proximity, rotation, acceleration)
Superuser
Touchscreen (with multitouch)
Vibration & Haptic feedback
Gallery
Hardware acceleration (EGL)
Live wallpapers
Screenshots
Screen off/on animations
Wallpaper scrolling
bootanimation
Audio (not full working, need some fixes)
CM9 ramdisk
Camera
What not working:
WIFI
Everything other is untested!
What working but not good:
everything other is untested
IMPORTANT !!!
Somehow boot.img can not be flashed without "fastboot", I tried using dd, using recovery, using some other tools... it can not be flashed this way!
To get everything ok and corectly for CM9 you need to flash these boot.img from these zip using fastboot !!! Its only a way!!! So after installing rom (or before installing the rom), reboot phone to the bootloader, flash boot.img this way:
fastboot flash boot boot.img
Its reguired because audio and other things not working if you not flash boot.img !!!
Google Apps for Ice Cream Sandwich:
You can find it here -> http://goo.im/gapps/
My android git for Desire C: https://github.com/munjeni
If you like my work and if my hard work on this device helped you to get something better, please give full credits "at least" to my hard work, thanks! If you use source code from my git please do not miss my name in your post, thank you! Happy porting!!!
IMPORTANT if you compiling CM9 from source!!!
Double check build.prop because some lines is replaced by new line, so you need to back these new line into original line, if you not do it you will get boot loop! Its easy for figuring out, simple open build.prop file and fix these lines, its something like:
ro.ril.blablabla
1,15 US
ITA
blabla
but need to be in one line like this:
ro.ril.blablabla 1,15 US ITA blabla
Kernel: kernel is Htcdev stock rom source code.
https://github.com/munjeni/kernel_htc_golfu
Download rom - 19.Apr.2013.:
Sorry I deleted file acidentaly... if some one have mirrired link please pm me!
Thanks:
Qualcomm for userspace drivers!!!
CyanogenMod Team
cute_prince
cm2pico
speed_bot
Pico devs for audio lib
MIUI rom based on my CM9 rom
{
"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"
}
IMPORTANT !!!
- Somehow boot.img can not be flashed without "fastboot", I tried using dd, using recovery, using some other tools... it can not be flashed this way!
- To get everything ok and corectly for MIUI you need to flash these boot.img from these zip using fastboot !!! Its only a way!!! So after installing rom (or before installing the rom), reboot phone to the bootloader, flash boot.img this way:
fastboot flash boot boot.img
Its reguired because audio and other things not working if you not flash boot.img !!!
- Do not install superuser or any other permission tool because MIUI have his own security feature Superuser, Supersu...etc will break compatibility and other apk will not work corectly!
- To get MIUI security feature working you need to give and remember permissions to the MIUI LBE guard (it will enable byself), but to invoke these settings menu you need to initiate these menu by settings submenu (cpu control)... run cpu control from setting menu, you will be prompted for root permissions, enable root permissions, open again cpu control submenu and apply for example an cpu frequency, you will be prompted for root permissions, aply them, reboot phone, after next boot you will be prompted for LBE guard security, APPLY AND REMEMBER permissions for LBE, reboot phone and you are done! After this settings your root permissions manager, startup manager...etc and everything other which using LBE feature will be full working now!
Download rom:
Unofficial_MIUI_GOLFU_1366462688.zip
Source code:
https://github.com/munjeni/miui_sony_xperia
Initial patch for Desire C is done, git for MIUI is updated, almost everything working in MIUI rom but have some small bugs... you can fix all other bugs! Happy porting!!!
Oh yeah, flashing this right now. i'll try to help.
No responses? ...I will sell this phone now
munjeni said:
No responses? ...I will sell this phone now
Click to expand...
Click to collapse
Give it time, its still a very new device.
If I had the technical knowledge I would definitely offer my help, but unfortunately, programming with linux/android is beyond my ability.
The wildfire s was also very slow to receive development for some time after its release, but now its buzzing with both cm9/10.
Whatever you decide is best for you Munjeni, we do appreciate all your efforts mate:thumbup:
Thanks for the share.. works great.
yeah man, i didn't have the ability to work with android and linux too... sorry !
but i'm a very good tester haha, only things i really need to work right now it's the wifi.
Appreciate the work. Hope this can be further progressed.
I'm not great with linux and porting, but I hope theres others who can help out.
I would like to help, but I don't know how to port sense 2.1 and 3.5 for our device.
Sent from my HTC Desire C using xda premium
Munjeni,
would it be useful to use some of the sources from the HTC explorer/pico, its using the same cpu. I'm not sure about the other hardware, board or radio etc.
Here's the thread link: http://forum.xda-developers.com/showthread.php?t=1821582
The guys github might be useful.
keep it up! thank you
intel007 said:
Munjeni,
would it be useful to use some of the sources from the HTC explorer/pico, its using the same cpu. I'm not sure about the other hardware, board or radio etc.
Here's the thread link: http://forum.xda-developers.com/showthread.php?t=1821582
The guys github might be useful.
Click to expand...
Click to collapse
Thanks, will try to build audio libs from explorer. Wifi chip is diferent in desire but I have idea how to fix it... new build will be soon! Did you tested gps?
Edit:
I'm unable to get audio and wifi, still have no idea which audio libs is inside stock rom (is it qdspv2 or what??), I just wont to compile it from source! About wifi, I have compiled/tried many compact wireless modules in combination with compiling/configuring it with android source and still no way/idea how to fix it (with every compiled modul I am unable to find/create wlan0 still only sucess if I use at6kl_sdio.ko from stock rom but unable to fix wifi...). Do you have idea/link to source for sdio version of the Atheros 6kl modul, I am unable to find it, only I have found ath6kl without _sdio prefix... ??? Any info will help me! Why these s**ts is harcoded in Desire C... very stupidly and boring thing that we need hard work to get this s**t working. but CM9 and Jelly Bean is very fast and smooth in Desire C ! I am unable to sell this phone (do it mean it is realy an s**t phone...?? I think too! Missing compas, mising camera autofokus, mising button backlights (very strange that htc selling this phone without lights for butons), its 600mhz only...etc) so I will leave this development for sure when I buy an another phone in next few weeks (what you mean about Sony Xperia Go 1ghz dual core, display 3.5inch, cam autofocus, blic!...etc???)! If you need cm9 source three let me know!
@Munjeni
This helped me to link a modfied kernel to get the wifi working on differents roms. Not sure if this is what you need.
In the About phone information of the rom, it looks like:
2.6.35.7-ge382d80
[email protected]
The important part above is -ge382d80, and we have to reference this when compiling the kernel. Make sure the part preceding -ge382d80 does match the output of the following command:
$ make kernelversion
The trick is to write that -ge382d80 in a .scmversion file in the kernel source tree (obviously, you need to replace -ge382d80 with whatever your device has):
so in the root of the kernel source type
$ echo -ge382d80 > .scmversion
This may work if you are having problems with wifi. If you need me to compile a kernel with your version reference let me know; just post this from the cm9 rom - 2.6.35.7-ge382d80
[email protected]
If you do move on with phones, please post the CM9 source, hopefully others can help too.
info from http://glandium.org/blog/?p=2214
Thanks, but dude, first, we speaking here about CM9 android, not about stock android. I speaking here about enabling wifi under CM9 only! But about stock rom and wifi you no need to hack kernel in order to change version, you have a better way to do that, you just need to edit golfu_defconfig, change version string, and you can compile kernel that will have the version like stock kernel...its not problem...I know that allready! But wifi under cm9 not working now! Problem is why these wifi libs/firmwares/modules is hardcoded and why missing from public kernel source! It mean its not part of the golfu kernel, its part of compat wireless source and wifi module is compiled from there!!! I tried many compact wifi modules to compile from source but still no one working... unable to enable wifi from android settings menu... I think there is something hardcoded in ramdisk init (binary) because cm9 init binary could not giving cm9 rom to boot! So "init" is allso hardcoded! I got wifi (not stock modules) working but only manualy init! Still wifi enabled from android settings menu could not be enabled and I have no idea why! I found ideal kernel wifi "sdio bassed" source for our desire c but these kernel is 3.6 and ath6kl module reguire a lot of works if we want to port it to our kernel, still unable to compile! But I found compat wireless but on my look into source I am unable to find compatible ath6kl source for example I am unable to find sdio bassed source "ath6kl_sdio" that have definitions "path to firmwares" inside core.h:
Code:
/* AR6003 3.0 definitions */
#define AR6003_HW_2_1_1_VERSION 0x30000582
#define AR6003_HW_2_1_1_FW_DIR "ath6k/AR6003/hw2.1.1"
#define AR6003_HW_2_1_1_OTP_FILE "otp.bin"
#define AR6003_HW_2_1_1_FIRMWARE_FILE "athwlan.bin"
#define AR6003_HW_2_1_1_TCMD_FIRMWARE_FILE "athtcmd_ram.bin"
#define AR6003_HW_2_1_1_UTF_FIRMWARE_FILE "utf.bin"
#define AR6003_HW_2_1_1_TESTSCRIPT_FILE "nullTestFlow.bin"
#define AR6003_HW_2_1_1_PATCH_FILE "data.patch.bin"
#define AR6003_HW_2_1_1_BOARD_DATA_FILE AR6003_HW_2_1_1_FW_DIR "/bdata.bin"
#define AR6003_HW_2_1_1_DEFAULT_BOARD_DATA_FILE \
AR6003_HW_2_1_1_FW_DIR "/bdata.SD31.bin"
If you help me to find compat wireless source that have definitions for path to firmwares than I will maybe fix wifi! I no want "stock" files, I just want to compile custom from source!
Other problem:
Android source code (cm9, jelly bean) allso mising something about ath6kl thing! For example, found all references about ath6kl with "all paths to"... see here -> http://paste.ubuntu.com/1187235/ ...expecialy this line:
Code:
/./system/lib/libhardware_legacy.so:ath6kl_sdio
so what these LINE mean? These line mean that ath6kl is referenced too in android source code (libhardware_legacy folder !) and allso hardcoded for our desire c because libhardware_legacy inside CM* android source code missing these ath6kl things! So we have BOOTH problem/missing source code for ath6kl_sdio in android and in kernel for our desire c wifi and we first need to find them, import them into android source, import them into kernel source, and finaly compile...
About audio:
I have absolutely no idea which source code is used for compilation for desire c ... its like another hardcode We probably can use audio libs from stock rom and fix some errors/mising lines in cm9 framework to get these libs working, now I have "SIGSEGV" with these libs! I have no idea, generic audio libs compiled from from cm9 source code not working, I am unable to fix it, its very annoying and hard !
Edit:
Possible solution for android only -> https://github.com/vegaics/libhardware_legacy/blob/master/wifi/wifi.c this need to be modified for Golfu
Guys, I sold my Desire, I will not continue developing for this phone so I will upload cm9 source tomorow on my git so you can finish them, sorry and happy porting!
Thanks for your work. I don't know enough about linux to help with the porting. Hope some others are out there to continue
Link to my Desire C android source code used for this build is here -> https://github.com/munjeni so if you like my work and if my hard work on this device helped you to get something better, please give full credits "at least" to my hard work, thanks! If you use source code from my git please do not miss my name in your post, thank you! Happy porting!!! :good:
Thanks munjeni, good luck with your future developments mate:thumbup:
I'm gonna start learning some of this development stuff for future projects, I have an upgrade in a month or two so I'll wait till then before I start messing with my phone, don't wanna be left phoneless.
I'm sure development will pick up soon guys, this is still a pretty new device, and I'm sure experienced devs will arrive soon (fingers crossed)
This would be an even greater/faster device with cyanogenmod and little bump to the cpu frequency.
It has great battery life, even in comparison to my sons s3 and my brother's too, which is a great feature for any recent smartphone.
HTC Desire C uses MSM76XXA Audio libraries .. since munjeni left the project, if anyone else is interested i will share the source
here's a mirror to the download above with the stock ROM files already added http://www.filefactory.com/file/4sc9kje5y6cx/n/cm9_golfu-ota-eng.root.zip
{
"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"
}
Triangulum kernel is a custom kernel series specifically for the galaxy gear.
This is the first fully custom kernel for the Galaxy Gear. This is not a complete ROM, This is just a replacement kernel.
Features:
Restored Exynos 4212 frequency table - Full 1.6GHz clock available.
Dual core enabled
init.d support
autoroot including superuser
MTP as default.
Click to expand...
Click to collapse
Known Issues:
Second core isn't enabled on first boot after flashing.
Click to expand...
Click to collapse
Download links are in the second post.
Installation Instructions:
Heimdall:
Boot device in download mode.
Click browse to open package.
Open triangulum-1.0-heimdall.tar.gz with Heimdall
Start flash.
Click to expand...
Click to collapse
Odin:
Boot device in download mode.
Make sure that only Auto Reboot is checked, and select file in AP
Open triangulum-1.0-odin.tar.md5
Start flash.
Done.
Click to expand...
Click to collapse
Recovery:
Note: This requires running _null TWRP
Copy triangulum-1.0.zip to device
Reboot to recovery
Select zip from file picker
Install
Click to expand...
Click to collapse
Signature banner for those who like showing what they are running on their devices:
Code:
[PLAIN]
[URL="http://forum.xda-developers.com/showthread.php?t=2610071"][img]http://files.lilstevie.geek.nz/assets/triangulum/images/triangulum-600x150.png[/img][/URL][/PLAIN]
Root powered by SuperSU - Logo created with Universe Sandbox
Downloads:
Heimdall Package md5: 5ec89392ccccd15b20eb585a4ffe2d3c
Odin Package md5: 2dbb366f275481f20fe18d628ef83ebb
Update.zip Package md5: 18852abd04f82c0e3ea89bf97af557e6
Source:
samsung_sm-v700_kernel
Old Versions:
0.1:
Heimdall Package
0.2:
Heimdall Package
Odin Package
Update zip
1.0:
Heimdall Package
Odin Package
Update zip
F.A.Q:
1. Will this kernel drain my battery faster?
It depends on usage. In most cases you will however see a faster battery drain unless you change the frequency settings using an application such as SetCPU or Voltage Control.
2. Where did the name Triangulum come from?
The name Triangulum comes from the name of a galaxy within our local group. You can read more about it here.
3. What settings do you recommend in <insert cpu control app here>?
It really depends on what you find works best for you, it is a balance between battery life, responsiveness and how much heat it is going to produce on your wrist. Personally I have set the device to use the powersave governor which is more conservative on when it steps up the frequencies, but also bumped up the minimum frequency to 400MHz as to aid in response times, but have full clock at 1.60GHz.
4. Before installing I had adb enabled, why isn't it now?
I don't believe in enabling adb by default, for the same reason I will not run the kernel in insecure mode. As part of the process to enable MTP the system forgets if you have enabled adb.
Changelog:
1.0.1:
Fixed no sound bug
Fixed no video recording bug
1.0:
Reworked init.d support
MTP enabled on boot
Moved out of beta
0.2:
Unlocked second core
Added init.d support
Autoinstall root if not present
Switched to LZMA for kernel and ramdisk
0.1:
Initial Release
lilstevie said:
Reserved 3
Click to expand...
Click to collapse
can i flash this in odin??
red rocket said:
can i flash this in odin??
Click to expand...
Click to collapse
At this stage no, I will work on an odin package a bit later.
This is great !
I cant wait to see what you whip up in the future..
EDIT: Perhaps init.d support ? MTP being the default storage mount ? SWAP support ?
Nice work! Will be interesting to see how it behaves if you are actually able to unlock the second core
fOmey said:
EDIT: Perhaps init.d support ? MTP being the default storage mount ? SWAP support ?
Click to expand...
Click to collapse
init.d support is definitely possible, as is MTP. SWAP I'm a little more hesitant about, I'm not fond of swap on mmc devices due to wear cycles, but also the limited available memory (4GB) means it would be a sacrifice.
lilstevie said:
init.d support is definitely possible, as is MTP. SWAP I'm a little more hesitant about, I'm not fond of swap on mmc devices due to wear cycles, but also the limited available memory (4GB) means it would be a sacrifice.
Click to expand...
Click to collapse
I agree with swap although it would be nice to experiment with.
MTP on the other hand tho I think would be a excellent idea pre-enabled.. Make life easier for more novice users who are not very confident with adb.
Brendo said:
Nice work! Will be interesting to see how it behaves if you are actually able to unlock the second core
Click to expand...
Click to collapse
is the second core locked/unlock on the stock kernel?
cyberone3 said:
is the second core locked/unlock on the stock kernel?
Click to expand...
Click to collapse
On the stock kernel it is turned off. So far it appears to be done by a userland process (most likely init)
heimdall
first - thanks for the work, exciting stuff.....can't wait to see where this goes...
If we can get uv/oc and some ram advantages, it'll be great.
I was chatting to f0mey about swap...I see you're not a fan of swap.
sorry for OT, but relevant (i guess in a remote kinda way )....for the life of me I just cant get Heimdall to flash this, keeps giving me a libusb error-12.
I have used Heimdall before often, but it just doesn't want to recognise the device. (Windows7 x86)
I tried reloading zadig (drivers), reinstalled C++ framework etc but no gravy
When I try to reload the Heimdall driver files, it says drivers already installed
I guess I'll wait for the Odin or TWRP flashable kernel, unless you have it available as a Boot.img ?
How high is the stock clock on the cpu on the gear? Great with a new kernel for the gear! thank you!
kashortiexda said:
first - thanks for the work, exciting stuff.....can't wait to see where this goes...
If we can get uv/oc and some ram advantages, it'll be great.
I was chatting to f0mey about swap...I see you're not a fan of swap.
sorry for OT, but relevant (i guess in a remote kinda way )....for the life of me I just cant get Heimdall to flash this, keeps giving me a libusb error-12.
I have used Heimdall before often, but it just doesn't want to recognise the device. (Windows7 x86)
I tried reloading zadig (drivers), reinstalled C++ framework etc but no gravy
When I try to reload the Heimdall driver files, it says drivers already installed
I guess I'll wait for the Odin or TWRP flashable kernel, unless you have it available as a Boot.img ?
Click to expand...
Click to collapse
Sorry I cannot help for most of the Heimdall stuff. I use linux on my workstation which Heimdall just works with
I can however help with just the boot.img here you can find it in kernel boot.img format. Also the heimdall package is just a tar.gz which can be opened with winrar et al.
tyvar1 said:
How high is the stock clock on the cpu on the gear? Great with a new kernel for the gear! thank you!
Click to expand...
Click to collapse
On the stock kernel it is 800MHz
I was contemplating making a cwm/twrp flashable zip with boot img but am not sure what mmcblk partition for the script
Sent from my GT-N7100 using Tapatalk
kashortiexda said:
first - thanks for the work, exciting stuff.....can't wait to see where this goes...
If we can get uv/oc and some ram advantages, it'll be great.
I was chatting to f0mey about swap...I see you're not a fan of swap.
sorry for OT, but relevant (i guess in a remote kinda way )....for the life of me I just cant get Heimdall to flash this, keeps giving me a libusb error-12.
I have used Heimdall before often, but it just doesn't want to recognise the device. (Windows7 x86)
I tried reloading zadig (drivers), reinstalled C++ framework etc but no gravy
When I try to reload the Heimdall driver files, it says drivers already installed
I guess I'll wait for the Odin or TWRP flashable kernel, unless you have it available as a Boot.img ?
Click to expand...
Click to collapse
Same for me, windows 8 x64
Can't wait for a flashable zip. This looks great
Sent from my SM-N900T using Tapatalk
Rename triangulum.img to boot.img
Copy to null_ 19.zip
And flash null_ 19.zip (no wipe if already installed)
Kernel work very well thank you :good:
Please a Tarball Im on stock and I wanna flash this baby aswell
Sent from my SM-N9005 using XDA Premium 4 mobile app
{
"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"
}
Hello guys,
let me present to you my Moto G Kernel. Its based upon the stock Moto G kernel source and was build for the stock ROM.
The main goal for this kernel is to improve battery life while keeping up a reasonable performance.
Features;
Added my own hotplug-driver (disabled mpdecision)
Improved and updated interactive governor with touchboost
Simple ondemand GPU governor
Vibrator control with additions from me
Real Voltage Control
It just works and is stable (on all devices for stock ROM)
Many small improvements e.g. updated subsystems and fixed memory leaks
I tried to keep this kernel as clean as possible with useful features. Always make a backup before installing and if you are coming from
a different kernel keep in mind that you'll need to reflash the stock modules (if changed). This kernel should work for all stock roms (dual sim as well as GPE).
How-To-Install;
be sure to make a backup first
via fastboot; fastboot flash boot /path/to/boot.img or fastboot boot /path/to/boot.img (if you just want to try it without flashing)
via zip; install zip in your favorite recovery
Keep in mind that /system/lib/hw/power.msm8226.so should be renamed or deleted if flashed via fastboot (zip does it automatically).
Download
Changelog
Looking for the CM-Kernel? Head over to this thread!
If you want to tweak it, you can also do with my own app.
If you like this work and want to donate something;
Donate to Quarx
PayPal: [email protected]
---------------------------------------
Donate to Blechd0se
PayPal: [email protected]
Click to expand...
Click to collapse
Enjoy!
How-To-Build:
Go to my Github (kernel as well as ramdisk source are available).
Code:
git clone https://github.com/Blechd0se/kernel-moto-g.git
cd kernel-moto-g
git checkout kitkat-mr2-release-falcon
export CROSS_COMPILE=/path/to/your/toolchains/arm-eabi-4.7/bin/arm-eabi-
export ARCH=arm
make msm8226_defconfig
make -j64
I use googles default 4.7 toolchain as well as 64 jobs, you might change this value depending on your system.
Once build, you'll need to repack the ramdisk.
For repacking the boot.img i use the following;
Code:
mkbootimg --pagesize 2048 --base 0x10000000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags' --kernel kernel-moto-g/arch/arm/boot/zImage-dtb --ramdisk kernel-moto-g/ramdisk/ramdisk.cpio.gz -o /output/boot.img
How does the hotplug driver work here?
My hotplug driver is based upon @franciscofranco idea to keep minimum two cores online while the screen is on.
In addition to this there are load counters on both of those cpus. If they reach a certain threshold another core gets onlined.
So cpu0 is bound to cpu2 and cpu1 is bound to cpu3 in terms of onlining. If onlined, cpus stay a certain amount of time
online before they consider to eventually go down again. Since hotplugging is kind of an intensive and expensive operation and threads
might be migrated my algorithm always offlines the lowest load core.
If screen is off, there is only one core online.
Here is a quick overview about the hotplug driver tunables;
all_cpus_threshold:
The threshold for the average load of all currently onlined cpus to online the next core. If you lower this value, cores can get more easily online.
hotplug_sampling:
The sampling rate of the hotplug driver. Lower this value and decisions will be made quicker in regards if a core should be onlined or not.
min_online_time:
To prevent core off-/onlining when they are near the threshold. This is the minimum online time for a core.
single_core_threshold:
The threshold for a single core to online another one. For example; if core 1 is at 100% and the average load is above 60% core 3 will get online.
low_latency:
If enabled (1) it let's the hotplug driver react really quickly to short load spikes (100% CPU load) and onlines cpus accordingly.
up_frequency:
The minimum cpu frequency to start hotplug operations. If the current frequency is below this value, no hotplug operations will perform.
Default is the maximum frequency.
battery_saver:
If enabled (1), only one core will stay active as soon as you turn off your screen. If you are getting strange audio quality while the screen is off, try
switching it off via 0. This will let both core stay active during suspend.
Click to expand...
Click to collapse
.
Why do i have to rename/delete this lib?
Because it interferes with my changes to the interactive governor. You can keep it, but it might produce very strange issue. You can just
rename the file if you want to restore it later.
Can i tweak this kernel or do i have to?
Of course you can. You can use any of your favorite kernel tweaker app. I have also made one if you might want to use it, here is the
play store link.
You don't have to tweak it. It ships with well tested values and is already preconfigured.
As always, just enjoy your device.
How can i control the vibrator strength?
This option is not yet available in my kernel app. The actual sys path is; /sys/devices/virtual/timed_output/vibrator/vtg_level
The default value should be 18, the maximum is 31 and the my lowered minimum is 10.
e.g. echo 10 > /sys/devices/virtual/timed_output/vibrator/vtg_level
Coming from a different kernel?
If you come from a different kernel its likely that your modules are overridden. This kernel uses stock modules. You can
use this flashable zip by @justjr to restore your modules.
How to use color control?
Use the following in your terminal; echo 255 230 210 > /sys/devices/platform/kcal_ctrl.0/kcal
First value are reds, second value are greens and last value are blues.
Turn your display off -> on and profit
Very nice! Competition is always welcomed. I'll follow this development. Seems promising so far.
Good to see a second kernel for stock rom.
The vibrator control alone is making me want to switch.
Oh man!, great, it's awesome to have you here developing for Moto G, I'm gonna test your kernel right away, I have a question though, I'm coming from faux kernel, what would be the safe procedure then? You recommend me to re flash the stock images of kernel and system or just install your kernel via recovery it's enough?
[*]Vibrator control with additions from me
Does this mean that we're able to adjust the vibration intensity? If so you're my hero
Nice to see another stock rom kernel xda! I will have an eye to this topic and your development...
Bye Flamey
Gesendet von meinem XT1032 mit Tapatalk
Bleak3993 said:
Oh man!, great, it's awesome to have you here developing for Moto G, I'm gonna test your kernel right away, I have a question though, I'm coming from faux kernel, what would be the safe procedure then? You recommend me to re flash the stock images of kernel and system or just install your kernel via recovery it's enough?
Click to expand...
Click to collapse
I just did this. Hope you did a nandroid backup so you can restore boot and system. Then install this this kernel.
Sent from my XT1034 using Tapatalk
guapinoy said:
I just did this. Hope you did a nandroid backup so you can restore boot and system. Then install this this kernel.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I have a backup of stock boot and system already, so, is there any problems of installing over faux kernel?
Bleak3993 said:
I have a backup of stock boot and system already, so, is there any problems of installing over faux kernel?
Click to expand...
Click to collapse
Should be no problems.
Sent from my XT1034 using Tapatalk
Sorry for the question but will this kernel work on GPE Moto G or just the stock from Motorola?
how the heck did you do 64 jobs??? that should of totally blown up your computer and only one i know of that could take that is cyanfox's server. over at drdevs we max out at 32 for one person thats crazy abuse of your computer.
Well, I had to use the backup to recover the wifi modules, then I installed the kernel, and now is everything working perfect. Now, can I configure the vibration vibrator control?
Edit: will there be an OC version?
Hey! Welcome to the club.
I would really like to know
1) which model does it supports (i have xt1033, quarx should be having tge same)
2) which rom does it supports (stock ot aosp)
Very good blech, nice to see you developing for the Moto G.
Would like to try the kernel, but unsure wich .imgs I should flash to get stock kernel and wifi modules back, coming from faux, as nobody has provided any wifi modules files yet (not in faux kernel thread). I don't have a backup with stock stuff, my bkps also have faux modules on it.
abhifx said:
Hey! Welcome to the club.
I would really like to know
2) which rom does it supports (stock ot aosp)
Click to expand...
Click to collapse
Stock
cool
Thank you for this kernel, does not have choice for the stock, now have a choice, the other custom kernel for stock having problems autonomy at the moment, so I'll test it
And not pay to be able to control the kernel is really appreciable, thank you
So... I know it kinda has been answered already, but can anybody give a step by step guide how to flash this most effectively over faux kernel?
Do I just have to flash stock modules and kernel via mfastboot before fishing the zip file for this kernel via TWRP?
Where can I find those files?
I am on stock German version btw...
Gesendet von meinem XT1032 mit Tapatalk
confirmed not working on dual sim XT1033.
have to wait for a kernel which works on stock XT1033
Bleak3993 said:
Well, I had to use the backup to recover the wifi modules, then I installed the kernel, and now is everything working perfect. Now, can I configure the vibration vibrator control?
Edit: will there be an OC version?
Click to expand...
Click to collapse
The sys path is; /sys/devices/virtual/timed_output/vibrator/vtg_level
Default value should be 18, the maximum is 31 and my lowered minimum is 10. I'll add this later to the startpost
About OC; not sure yet, i dont feel its necessary, have to experiment with it.
Cameron581 said:
how the heck did you do 64 jobs??? that should of totally blown up your computer and only one i know of that could take that is cyanfox's server. over at drdevs we max out at 32 for one person thats crazy abuse of your computer.
Click to expand...
Click to collapse
I always use -j64, linux can handle it pretty nicely. It wont slow down the whole system, SSDs help a lot
abhifx said:
confirmed not working on dual sim XT1033.
have to wait for a kernel which works on stock XT1033
Click to expand...
Click to collapse
Could you explain this a little bit more? As far as i know kernel is the same for all devices. The only difference could be in ramdisk which is easily fixable.
Are you using motos stock rom?
Gesendet von meinem Nexus 7 mit Tapatalk
DISCONTINUED SUPPORT
OKAY SO
I present to you: Kali NetHunter 3.15.4 for the ZTE Axon 7.
(yes, a custom kernel for the ZTE Axon 7 on MiFavor!)
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The NetHunter installer zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local/nhsystem, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
NetHunter also includes its own Busybox that gives you full large file support and some extra applets.
It will not overwrite your current one, and will happily install alongside it as busybox_nh.
DOWNLOAD
Current version: 3.15.4 (stable, 2017-01-22)
Please be careful to download the right version based on this table:
A2017U (North America): kernel-nethunter-ailsa_ii-*
A2017G (Europe / Hong Kong): kernel-nethunter-ailsa_ii-*
A2017 (China): kernel-nethunter-ailsa_ii-*
All others be sad.
For the apps, chroot, and everything other than just the kernel, you will also need to download:
nethunter-generic-arm64-*
See installation instructions before proceeding!
Downloads are available at the official NetHunter build server: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: The Kali NetHunter installer requires write access to your data partition!
This means that if your data partition is encrypted, you will need to use the [Format Data] button in TWRP to remove encryption.
This will delete all your data, including internal storage.
You should back everything up first before installing Kali NetHunter.
The Kali chroot and apps are installed on your data partition (in /data/local/nhsystem for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The generic NetHunter installer will automatically install SuperSU. We try to keep it up to date, but it isn't always.
If you already have SuperSU or another root method installed, please simply delete the supersu.zip from the root of the zip file before installing it.
** If modifying the installer zip, you will have to disable ZIP signature verification as modifications will break it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
FULL INSTALLATION STEPS
Install Team Win Recovery Project (ailsa_ii) to your recovery partition.
{
"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"
}
Recommended: If you have a custom kernel or SuperSU installed, restore your stock kernel. (called Boot in TWRP)
This isn't entirely necessary, but you may need to flash the NetHunter kernel again if SuperSU replaces it.
For new installations: Download the nethunter-generic-arm64-kalifs-full zip.
For upgrades: Download the update-nethunter-generic-arm64 zip.
Without exiting TWRP, transfer the NetHunter generic arm64 installer zip to your device over MTP* and flash it using [Install] in TWRP.
Download the kernel-nethunter zip specific to your device.
Without exiting TWRP, transfer the NetHunter kernel installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD OR UPDATING YOUR ROM
Follow the installation steps above. NetHunter can be installed over itself as many times as you'd like.
If you don't want to lose your chroot, flash the smaller update-nethunter-generic-arm64 zip instead.
DEVICE RECOMMENDATIONS
The ZTE Axon 7 internal wireless does not support monitor mode. This means you'll need to use an OTG adapter and a wireless card that does.
I highly recommend these two items:
Alfa Networks AWUS036NEH: https://smile.amazon.com/802-11g-Wireless-Long-Rang-Network-Adapter/dp/B0035GWTKK/
iXCC USB Type-C to Type-A OTG adapter: https://smile.amazon.com/iXCC-Adapter-Charge-Supported-Devices/dp/B017TJN22C/
* I am not affiliated with these sellers
The AWUS036NEH is the most tested and stable adapter available, and also comes in a very convenient portable form factor allowing antenna swaps for greater scanning ranges.
The iXCC USB adapter is compliant with USB Type-C specifications and provides up to USB 3.1 Gen 2 compatibility. It's also well built.
I don't recommend using smaller OTG adapters - they can break your ports if you accidentally put too much pressure on them or your phone falls with them plugged in.
THE KERNEL
The NetHunter kernel for the ZTE Axon 7 is (somewhat) based on A2017U B27 kernel sources.
It has the following changes:
Carefully updated to Linux 3.18.47!
Merged with the latest CodeAurora tag for Android 6.0 msm8996: LA.HB.1.3.1.c1-20600-8x96.0
Many bug fixes and cleanups to ZTE's code, including disabling of debug tasks for battery life
SELinux Permissive (required for DriveDroid until I fix policy injection rules, it will pretend to be Enforcing)
Paragon UFSD drivers replaced with Samsung's latest open-source exFAT drivers
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
DriveDroid compatibility
USB HID Gadget keyboard & mouse support - temporarily disabled until issue solved
mac80211 packet injection support
savoca's KCAL color calibration driver built in (currently no invert support on msm8996)
Additional drivers built in for the full Kali NetHunter experience
Kernel module support, insert your own modules! (modprobe available in Kali chroot)
CIFS, NFS, USB Serial available through included kernel modules
VerifiedBoot=green status hack to pass SafetyNet (may not work with SuperSU, remove SuperSU from the installer if this is important!)
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
If your issue is with a specific app, it might be better to contact the developer of that app.
For Kali NetHunter bugs/issues, you can open a ticket at: https://github.com/offensive-security/kali-nethunter/issues
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
Video Recording - The rear camera video encoder will corrupt the video on the first frame. Happens after restarting camera app.
HID attacks - There's an issue with USB descriptor breaking when HID gadget mode is enabled, so it is disabled for now.
DEVELOPMENT & CONTRIBUTIONS
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Kali NetHunter Official device updates: https://github.com/offensive-security/nethunter-devices/commits
ZTE NetHunter kernel source: https://github.com/jcadduono/android_kernel_zte_msm8996_old/tree/nethunter-6.0
If you wish to donate to the NetHunter project, you can donate directly to me through the Donate button under my name.
This will generally go towards supporting my next flagship device purchase, which will receive NetHunter and TWRP support from myself.
You can also use "Basenji Rescue and Transport" as your Amazon Smile charity and that will make me really happy!
(in my avatar, if you see a dog, that's a Basenji!)
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the ZTE Axon 7, Kernel for the ZTE Axon 7
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.15.4
Stable Release Date: 2017-01-22
Created 2016-12-16
Last Updated 2018-07-31
Work on a2017G too? I have open bootloader and on A2017G b29. And that Work perfekt
Kevinkuensken said:
Work on a2017G too? I have open bootloader and on A2017G b29. And that Work perfekt
Click to expand...
Click to collapse
you'll have to let me know if it works, i can't really understand if you're asking if it works or if it does work
IT Work for A2017G. I have installed IT but have no Hunter app
Guess I know what I'm doing tonight
Sent from my ZTE A2017U using XDA-Developers mobile app
https://www.kali.org/kali-linux-nethunter/
Seems like this is a "Hacker's" kernel with no real gain for the "regular" user.
KyJelly69 said:
https://www.kali.org/kali-linux-nethunter/
Seems like this is a "Hacker's" kernel with no real gain for the "regular" user.
Click to expand...
Click to collapse
Yea.... What are we supposed to do with this kernel if it doesn't improve anything over stock? We are not "Hackers"
Anyone He has flashed The kernel, have The Kali NetHunter App? For Me ist dont find the app
XblackdemonX said:
Yea.... What are we supposed to do with this kernel if it doesn't improve anything over stock? We are not "Hackers"
Click to expand...
Click to collapse
Don't use it. Not everything that is developed or posted here will be for everyone.
I'm sure there is more people here that find this useful, or you can try to use it useful and learn something new
jimbo77 said:
or you can try to use it useful and learn something new
Click to expand...
Click to collapse
I still don't need to hack WiFi networks lol
XblackdemonX said:
I still don't need to hack WiFi networks lol
Click to expand...
Click to collapse
That's one of its uses but there is more
Good work! Glad to see some more development for our device.
KyJelly69 said:
https://www.kali.org/kali-linux-nethunter/
Seems like this is a "Hacker's" kernel with no real gain for the "regular" user.
Click to expand...
Click to collapse
We don't care.
VinylJStar said:
We don't care.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=70122463&postcount=1356
Oh how very clever you are. And we still don't care...
Can I install update-nethunter-generic-arm64 zip instead of nethunter-generic-arm64-kalifs-full zip if I don't want to have all the apps? I basically just want this kernel to bypass SafetyNet.
Thanks
With this kernel, is it now possible to flash Substratum Themes, without causing a boot issue?
Or is that something that needs changed in the ROM itself?
XblackdemonX said:
Can I install update-nethunter-generic-arm64 zip instead of nethunter-generic-arm64-kalifs-full zip if I don't want to have all the apps? I basically just want this kernel to bypass SafetyNet.
Thanks
Click to expand...
Click to collapse
If you only want the kernel then just install the kernel lol update-nethunter is the apps, nethunter-generic is the apps + kali system
This is only my initial build for getting feedback on things that might be broken before I start merging in CAF/updates.
anyways, I'm not sure how safetynet will handle permissive since I had to use that for DriveDroid support. I haven't tested if exFAT works in enforcing (it probably doesn't), but here's an alternative kernel for you that is only safetynet+exfat+kcal (things typical xda users might care about):
https://build.nethunter.com/misc/axon7/ailsa_ii_xda_safetynet_kcal-1.0-20161216-1849.zip
Thank you very much i'll try it!
Loved it. Installed, used the Kcal app and it works great! I hope you keep bringing more and more features to a custom kernel!
Appreciate it!!
---------- Post added at 01:49 AM ---------- Previous post was at 01:29 AM ----------
@jcadduono do you have any idea why any of the apps that set options on boot work? I have tried with folder mount and Kcal and it seems boot commands are not executed. I need to get in the app after the phone has booted and apply the settings manually instead of then being applied on boot. Probably you can shred some light on this issue?
jimbo77 said:
@jcadduono do you have any idea why any of the apps that set options on boot work? I have tried with folder mount and Kcal and it seems boot commands are not executed. I need to get in the app after the phone has booted and apply the settings manually instead of then being applied on boot. Probably you can shred some light on this issue?
Click to expand...
Click to collapse
probably related to power management i guess, i know at least on my device any autostart apps don't start till like 20 seconds after the device is booted because the OS spreads out everything.
make sure your app policies allow auto start though, and that you hit the save button with start on boot and color service enabled:
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!