This thread is for the developing of the JourneymanMod Kernel project.
For now we are in version 3. Its working great, charging while in OTG, and recoginizes if there is a charger connected or if its default OTG cable.
REMEMBER: It will only charge if you power the hub BEFORE connecting to the phone, if you connect to phone and then power the hub it wont connect.
In the attachments are 3 zip files.
We got version 4.1.1 of yakju and takju. And version 4.1.2 of yakju.
all of them are working nice.
This project will be for enabling OTG + Power, since the stock kernel dont enable charging the phone while in OTG mode.
For helping the project, or just following the news, we created an irc channel (##JourneymanMod).
The source-code of the project will be located at the github (https://github.com/caioketo/journeymanmod).
Was just googling to see if this was possible. Ordered my cable a week ago, waiting for it, & was worried that my time with usb otg would be limited by battery. Great mod! Thank you! Can't wait to try.
---------- Post added at 01:49 AM ---------- Previous post was at 01:20 AM ----------
Anyone interested in this, this is the cable I ordered. Hope it works. Clearly a normal usb otg cable would have nowhere to attach power :
URL: http://www.ebay.com/itm/Micro-USB-H...ng-phone-i9100-i9300-i9220-9250-/251127542280
THX.....................
possibl to develop same thg on n7?
Looks great! I'm about to try. Thank you!
psycho2097 said:
possibl to develop same thg on n7?
Click to expand...
Click to collapse
You should read this thread http://rootzwiki.com/topic/30615-can...imultaneously/ and I'm sure it can be done, I will try it when my N7 arrives...
Sure it is possible with others phone/tablets only need time and ppl to de xD
Almost done with the build envoriment, soon should be the firsts beta releases.
Sent from my Galaxy Nexus using xda app-developers app
caioketo said:
Sure it is possible with others phone/tablets only need time and ppl to de xD
Almost done with the build envoriment, soon should be the firsts beta releases.
Click to expand...
Click to collapse
Totally sweet! Thanks for your work on this...
friedCELLS said:
Totally sweet! Thanks for your work on this...
Click to expand...
Click to collapse
first we need this to work on gnex, then we can think about porting to others devices.
but I have faith we can make it.
The version 3 is released!
Hope you guys enjoin.
Credits to highvista.
Add to GNex CM10/CM10.1??
Would the dev be willing to submit a patch to the Galaxy Nexus CM10/CM10.1 project to enable this feature? I am not sure if this kernel could be used as a replacement for the stock CM10 kernel, but third-party kernels aren't supportable if there's a CM issue (hence my request to have it put in native CM10/10.1 kernel). Thanks!
Jim
CNLiberal said:
Would the dev be willing to submit a patch to the Galaxy Nexus CM10/CM10.1 project to enable this feature? I am not sure if this kernel could be used as a replacement for the stock CM10 kernel, but third-party kernels aren't supportable if there's a CM issue (hence my request to have it put in native CM10/10.1 kernel). Thanks!
Jim
Click to expand...
Click to collapse
Sorry for the delay on responding. This thread hasn't been as active as the original one where the JourneymanMod kernel was first introduced.
I've not submitted a patch to CM previously but, if I can set myself up to do it properly, I definitely will.
It's amazing how easy it is to compile this into custom kernels. Looking forward to the fixed patch.
Sent from my Galaxy Nexus using Tapatalk 2
how do you activate this feature in the AOSP available kernel ? I mean do you actually have to incorporate other drivers or is it maybe just an option you can select with menuconfig ? And if so do you have by any chance the specific parameters that are added to the vanilla .config file ?
tigrone said:
how do you activate this feature in the AOSP available kernel ? I mean do you actually have to incorporate other drivers or is it maybe just an option you can select with menuconfig ? And if so do you have by any chance the specific parameters that are added to the vanilla .config file ?
Click to expand...
Click to collapse
There is a modified AOSP kernel source code file that needs to be replaced. After that, it's a matter of building the kernel with this modified source code and then installing this kernel onto your phone.
This thread is pretty dead. You can find an ongoing discussion and the current kernel distributions at
http://forum.xda-developers.com/showthread.php?t=1835720
The kernels included in the ZIP archives are built as described above, from the AOSP kernel source.
I've fixed a bug in this kernel that occurs when detaching external USB power and am looking for some testing before I replace the current kernel distribution ZIP archives. If you're interested, check out the post and thread at http://forum.xda-developers.com/showpost.php?p=35910077&postcount=182. Thanks much.
caioketo said:
This thread is for the developing of the JourneymanMod Kernel project.
For now we are in version 3. Its working great, charging while in OTG, and recoginizes if there is a charger connected or if its default OTG cable.
REMEMBER: It will only charge if you power the hub BEFORE connecting to the phone, if you connect to phone and then power the hub it wont connect.
In the attachments are 3 zip files.
We got version 4.1.1 of yakju and takju. And version 4.1.2 of yakju.
all of them are working nice.
This project will be for enabling OTG + Power, since the stock kernel dont enable charging the phone while in OTG mode.
For helping the project, or just following the news, we created an irc channel (##JourneymanMod).
The source-code of the project will be located at the github (https://github.com/caioketo/journeymanmod).
Click to expand...
Click to collapse
2 Things:
1.I got CM10.1(Android 4.2.1) it will work?if not there is other solution?
2. There is something like that for Nexus7?(wifi)(CM10.1 Android 4.2.1 too)
elichai2 said:
2 Things:
1.I got CM10.1(Android 4.2.1) it will work?if not there is other solution?
2. There is something like that for Nexus7?(wifi)(CM10.1 Android 4.2.1 too)
Click to expand...
Click to collapse
1. No, it may boot but it will drain your battery and give you some issue. Other solution is try other kernel, if you want custom kernel with minimal customization try lean kernel.
2. I dont know about this
Sent from my Galaxy Nexus using Tapatalk 2
elichai2 said:
2 Things:
1.I got CM10.1(Android 4.2.1) it will work?if not there is other solution?
2. There is something like that for Nexus7?(wifi)(CM10.1 Android 4.2.1 too)
Click to expand...
Click to collapse
1. CM 10.1 doesn't include this kernel patch, as far as I know. I'd like to submit it for inclusion, but I'd need to test it, which means installing CM on my Galaxy Nexus, which I haven't wanted to do, since my GN is working very well under stock Android 4.1.2 with Journeyman Kernel V4.
2. Check out this thread on another web site
http://rootzwiki.com/topic/30615-can-you-charge-usb-host-mode-simultaneously/
I haven't followed this thread, but there was a lot of talk about a similar patch for the N7.
highvista said:
1. CM 10.1 doesn't include this kernel patch, as far as I know. I'd like to submit it for inclusion, but I'd need to test it, which means installing CM on my Galaxy Nexus, which I haven't wanted to do, since my GN is working very well under stock Android 4.1.2 with Journeyman Kernel V4.
2. Check out this thread on another web site
http://rootzwiki.com/topic/30615-can-you-charge-usb-host-mode-simultaneously/
I haven't followed this thread, but there was a lot of talk about a similar patch for the N7.
Click to expand...
Click to collapse
I actually have been testing your patch (even though in my own kernel), the results and some things I noticed I have posted on the thread you mentioned earlier when you announced you solved the bug that occurs when detaching external USB power...
Hope to see you there !
Related
I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
i'd really like to help you, but i'm not able... this morning i studied some tutorial such as http://pdk.android.com http://android.git.kernel.org http://d.android.com, but i'm new with linux and i can't understand anything... however i was asking myself the same questions...
Quick catch-up:
Dexter_nlb said:
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
Click to expand...
Click to collapse
Check, Possible: http://forum.xda-developers.com/showthread.php?t=767431
Dexter_nlb said:
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
Click to expand...
Click to collapse
Well, IDK if this easy, but manageable. Both odin (easier) and update.zip (more stable) options available.
Dexter_nlb said:
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
You could contact people at #project-voodoo to get more detailed information.
Best of luck.
Dexter_nlb said:
I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
thanks , very usefull.. so the .md5 extension on odin files are related to?
anyways i have made zImage for other platforms so changing the ramfs should be straight forward...
Finally a person who knows their stuff is attempting at a sense ui port.
Hope you succeed
I really hope you succeed - I have time but no knowledge - if you need help pm me
DesireHD rom? YES PLEASE!!!
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
Same here.
MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
thanks, im primarily persuing this as a personal challenge, but of course if ppl likes my work its great.
one note is, as written earlier, more experienced guys will be required to finish the bluetooth adaption, its alot more complex than the remaining parts.
and im told even on older htc phones it was hard to port drivers for bt.
my 2.1 sense mod on milestone was ok, except milestone only had 256MB, which resulted in many reloads of senseui.. here i think we can stabilize, even with a modified kernel to add swap if needed (if the 512MB utilization becomes a problem)
I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
xan said:
You could contact people at #project-voodoo to get more detailed information.
Click to expand...
Click to collapse
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.
jjwa said:
I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=8254744#post8254744
A thread for bounty to devs porting for SGS succeed
-Fraction
Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
Wasn't the JPM source leaked for a little while about a week back? Is that the source code to which you're referring?
Edit: Sorry forgot to check the post date, so at the time you posted that, the source code had not been leaked
Change of plans, hopefully with the help of anyone who is willing I'd like to compile an aosp build for the Sprint GS2 from source instead of trying to hack a port together, as suggested in this thread and other places, it just feels like it will be a lot more of a fruitful experience for all involved and have a better end result.
(a big thank you to everyone who so far have been super encouraging and friendly with noob questions, it's much appreciated!, I hope that if you wanted to help with the port you'll help with this build as well!)
This is a WIP. Starting out with Samsung's open source platform and kernel instructions on how to build from aosp and I'll take it from there.
I've setup some repos to get this all started in one place:
Samsung SPH-D710 platform source - https://github.com/thefredelement/sph-d710_platform_source
Samsung SPH-D710 kernel source - https://github.com/thefredelement/sph-d710_kernel_source
Team Hacksburg kernel source - https://github.com/thefredelement/android_kernel_samsung_c1spr
Stock kernel initramfs (thanks buddy323!) - https://github.com/thefredelement/stock-initramfs-eg30-epic-4g-touch
https://github.com/thefredelement/Samsung-Galaxy-S2-Sprint-Epic-4G-Touch-AOSP-Build - will be where the build will live after I push over Samsung's platform make and upload it!
--- old stuff that will make your head spin ---
If anyone wants to continue working on this, feel free.
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: you don't want this...
Reserved for changelog, when hopefully it gets that far
Awesome to see a project like this, good luck in the port!
Sent from my SPH-D710 using XDA App
O_OMG <3 :-!
Sent from my SPH-D710 using xda premium
Good luck! Looking forward to this.
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
deano0714 said:
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This boots using the stock Sprint/Samsung kernel.
xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
What kernel are you using?
thefredelement said:
What kernel are you using?
Click to expand...
Click to collapse
im using stock
xploPR said:
im using stock
Click to expand...
Click to collapse
Did you wipe all of your user data before installation?
Do you get to the boot animation?
Constructive criticism would be for me to point out you must not have read the OP because it clearly said nothing works because we don't have a aosp kernel yet but you are just rude.
Sent from my SPH-D710 using xda premium
xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
ehusidic said:
The title clearly states its not ready or stable so chill out while the devs do what they do
Click to expand...
Click to collapse
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic ore infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
Sorry for the horrid insults I aimed at the complaining member. Too uncouth.
Sent from my SPH-D710 using xda premium
Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. I agree this is a much better idea.
jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
i like that mandatory vacations with paid vacations to hawaiii, can xda hook it up or what?
thefredelement , good luck. glad to see new devs... i hope to be there one day but i'm way off...
Thanks!
thefredelement said:
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: http://www.multiupload.com/OF1HXSSOCJ
Click to expand...
Click to collapse
hit me up i can get ur rom working with wifi/3g/4g/whatever. zedomax at gmail dot com
Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
I recall rumor about samsung sending a GS2 to Cyanogen so that he could "get to work". Guess that never materialized - or they gave him something else to do once they hired him...
Sent from my SPH-D710 using xda premium
it was one of the cyanogen devs that got a galaxy2 & they have nightlies for the gs2 now.... It should not be hard to get it ported over
....
One of the devs on teamhacksung was asking for people with the phone to help with it ..he ask on twitter like the 16th so they are probably working on it....
Sent from my SPH-D710 using xda premium
FuguMod is a secure, open, reliable and no nonsense kernel
This is probably the only custom kernel for the Nexus 5 which adds security instead of removing it.
Current features are:
- compiled with linaro gcc4.7.4
- various small fixes
You can download the kernels at:
http://fugumod.org/nexus5
Source and changelog can be found here:
https://github.com/renaudallard/nexus5_kernel
IRC channel:
irc.freenode.net #fugumod
Flashing
Kernel zips are intended to be flashed with CWM ot TWRP, if you want to flash using fastboot, you need to unpack the zip and flash the boot.img which is inside
Versions
Kernels are based on the below version scheme
kernel_FuguMod_20131104_r1-4.4.img
20131104 is the date it has been packaged
r1 is the release number
4.4 is the ROM it is compatible with
Stable vs Testing
There are sometimes kernels in testing folder. These may be very stable or may not boot at all. Be sure to have an USB cable and fastboot under the hand if you try one of these. That said, in general, if they stay into testing folder for more than 15 min, they should at least boot and work more or less. I tend to remove non booting kernels from testing folder in less than 10 min (depending a little bit on the speed testers take them), and so if you see them one hour later, you should assume they are safe enough to flash.
So, in general Stable is the safest bet, but Testing may be the best. I, myself, generally run testing one.
Deprecated folder
In general, unless you really know what you are doing, you should avoid flashing those, they are mainly there for historical reasons.
Check for vulnerabilities
http://www.xray.io
Compatibility with hackish style apps
All apps which require direct memory write, access to symbols or memory offsets or modules will NOT work. And, no, don't ask they won't be supported in the future. Example: Arararagi's light is only provided as a module and will not be supported unless he produces a patch.
Security
If you want good security when your phone is stolen, in addition to encryption, don't forget to turn debugging off. Also, use enpasschanger to change your encryption password, any short PIN encryption can be cracked in a few minutes easily (for example, using my script at http://pastebin.com/Mdu06RZN)
Redistribution
As per GPL, you are authorized to redistribute this kernel with any of your custom ROMs provided you give out the source code like I do. You can link to my github in your distribution site.
However, if you modify the kernel yourself, whatever the modification is (compiling it yourself with a different compiler is a modification), you are not authorized to name it FuguMod, although you can credit me and tell the base comes from FuguMod but you cannot call the kernel itself FuguMod.
XDA:DevDB Information
FuguMod, a Kernel for the Google Nexus 5
Contributors
renaud, http://forum.xda-developers.com/member.php?u=2859799
Kernel Special Features: Open, stable, reliable and secure
Version Information
Status: Testing
Created 2013-11-04
Last Updated 2014-01-29
Glad to see you here renaud. I loved your Galaxy Nexus kernels.
First test version is now available
If anyone can confirm it was flashed correctly and boots, that would be great.
I'll test it right after the postman makes me happy
Haeretik said:
I'll test it right after the postman makes me happy
Click to expand...
Click to collapse
Just got a confirmation that mine will come tomorrow
flashed kernel_FuguMod_20131104_r1-4.4.zip and it reboots to bootloader.
Hello @renaud.
It's really nice to find a lot of people coming from Galaxy Nexus to the Nexus 5. As the Galaxy Nexus is an oldie (yes, two years), there are less and less threads supported. I hope, you will still support the Galaxy Nexus - but also the Nexus 5, of course. Good to have you in here! :laugh:
proxuser said:
flashed kernel_FuguMod_20131104_r1-4.4.zip and it reboots to bootloader.
Click to expand...
Click to collapse
When flashing or when booting?
renaud said:
When flashing or when booting?
Click to expand...
Click to collapse
after booting, i flashed it via bootloader.
proxuser said:
after booting, i flashed it via bootloader.
Click to expand...
Click to collapse
I suppose you meant you flashed with fastboot.
Whatever, till how far does it go?
I am wondering, did you unpack the zip and flashed boot.img through fastboot, or did you flash the whole zip through fastboot??
I'm glad you got the new nexus because I've been waiting for your kernels for awhile now.
Sent from my Nexus 4 using Tapatalk
tried out your kernel, alot of nice features but stock seemed to run faster. cant wait to see what the community has to offer over the next couple of months. pushing the phone to its limits / extending battery life.
dandwhelan said:
tried out your kernel, alot of nice features but stock seemed to run faster. cant wait to see what the community has to offer over the next couple of months. pushing the phone to its limits / extending battery life.
Click to expand...
Click to collapse
Thank you for confirming that it boots. Currently it has no features except being smaller than the stock one. I was waiting for the boot confirmation before developing.
Nice to see you again Renaud. Glad to be owning a device you're deving on again.
I have now received my N5. Real stuff will begin.
OK, thanks for some reporting as booting, but in fact it does not because my img doesn't support dtb yet.
Glad you got the phone and now hopefully fugukernel updater will work for this phone.
Sent from my Nexus 5 using Tapatalk
unforgivenmercy said:
Glad you got the phone and now hopefully fugukernel updater will work for this phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was not doing it myself, but I guess I can ask for the code to not have to rewrite everything by myself
r3 is out.
It boots and is compiled with linaro GCC 4.8
Further optimizations are on the road.
Whats with colour calibration?
Sent from my Nexus 5 using xda app-developers app
UnityROM-2 v.3.0.1
LG Optimus G - Sprint US ONLY ( LS970 )
(INTERNATIONAL VERSION NOT HAPPENING || NO GEE/B EVER!!! || DO NOT ASK)
Basic Overview
Source built Cyanogenmod 11.0 with a bucket of butter poured on top .
Compiled and Built with SaberMod GCC 4.8 Toolchains with a lot of optimization flags set.
BUILDTYPE = SNAPSHOT ONLY
(Not meaning only once a month or so like CM Inc.)
Aroma Installation.
Purpose
Just trying to make a cleaner, faster, and generally more optimized build basically, without changing the ROM itself (apps & such). With some extra nice things thrown in even if there's is no visible difference in the ROM
Credits
@IAmTheOneTheyCallNeo for all of his help getting GCC 4.8 up and running finally. I owe you big man.
@Captain_Throwback for his original commits and help with the original thread & in this one as well.
@gruesomewolf for all of his help learning how to build a custom kernel.
Cyanogenmod Inc. & Google Inc. of course. For everything they do, way too much to try listing here.
LiquidSmooth for some additional build flags.
And please, if you like my work or the work others have contributed to this project, hit the thanks button. Thanks.
Features & Links
*** Global O3 & Strict-Aliasing=3 Optimizations & lots more ***
Full-Modular Aroma ROM & Gapps WITHIN the main package, yet still in separate directories.
Clean or Dirty ROM Flashing Options in Aroma.
Multiple LCD Density Options in Aroma.
System App Remover in Aroma.
Works with or without Gapps Installed
***UnityKernel-3.0.1 Features***
Optimized same as the UnityROM-2 only with GCC 4.9.
I/O Schedulers: SIO & FIOPS.
Governors: Intellidemand & Intelliactive.
LZ4 Compression/Decompression.
Current Release:
https://www.androidfilehost.com/?fid=95784891001602827
UnityKernel-3.0.1 Updater (includes previous 2.7.0 Kernel)
Current Release (UnityKernel Only):
Not available yet sorry
Development Section
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
will this work on geeb?? ill defintely test if so
Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC
dr3adl0ckd said:
will this work on geeb?? ill defintely test if so
Click to expand...
Click to collapse
LiquidSmokeX64 said:
Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC
Click to expand...
Click to collapse
I am fairly certain it will run, but you might not have access to SD card or camera. If not, find out if there is a GEE/b kernel you can flash afterwards or if the OP can create a GEE/b kernel since it looks like it has a new kernel, aside from any other currently available. I know I've never seen UnityMod kernel anywhere.
To the OP, if you ask any of the other kernel devs what changes they made to produce a Gee/b kernel of the same settings I am sure they would provide some advice.
EDIT: some changes may be necessary in the build.prop as well to allow access to GSM.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful
Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".
LiquidSmokeX64 said:
Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".
Click to expand...
Click to collapse
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful
LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
You did a great job, it works fine. I think you should continue to work on perfection of Rom. As far as I understand, you need to go to another forum thread(Optimus G Original Android Development). When using the camera - got two crashes . everything else works perfectly, quickly and smoothly! Antutu received 20673 balls without my optimization. Thank you for a wonderful job. I know little about it, but it seems to me that all is well. This gproj or aosp based? You use the new driver for the camera? Excuse me for my english.
Well thanks for the feedback. I'll run 2.7.0 for LS970 now. Tons of new things added for the build and kernel
dopy25 said:
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
Click to expand...
Click to collapse
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!
+1 would also want a geeb kernel for this.
dr3adl0ckd said:
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!
Click to expand...
Click to collapse
Well if I knew what I need for geeb I would gladly make it for you guys. I just grabbed the stuff listed in CMs LS970 device cm.dependencies file.
I can always add more or a new defconfig file to have it look at while building. Either way will work
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
Yes sir!
LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
with impatience [emoji14] [emoji14] [emoji14]
Vadik56 said:
with impatience [emoji14] [emoji14] [emoji14]
Click to expand...
Click to collapse
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone
LiquidSmokeX64 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone
Click to expand...
Click to collapse
Thank you, download started. I feel will be a bomb-)-)
UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment cm-UnityROM-2-v.2.7.0-ls970.zip.log.txt
Vadik56 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment 2974972
Click to expand...
Click to collapse
Looks like you're flashing for the wrong device, or wrong recovery.
I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.