Related
I Have the android source code and i'm doing some mods... My question is: Do I need to add any APNs to the source... or once compiled, can I just flash and it'll auto work with t-mobile, etc... ?
You know, APNs can be configured through the UI.
whitemonster said:
I Have the android source code and i'm doing some mods... My question is: Do I need to add any APNs to the source... or once compiled, can I just flash and it'll auto work with t-mobile, etc... ?
Click to expand...
Click to collapse
what exactly are you modding
I know, but I dont want to have the end-user have to type in their APNs... I rather it be built in... So are they built in or must I add them to the source before building?
I'm modding the whole thing... like why make the menu come out of the bottom? why not the side? lol..., etc, etc... adding to BIN and some other stuff...
whitemonster said:
I know, but I dont want to have the end-user have to type in their APNs... I rather it be built in... So are they built in or must I add them to the source before building?
I'm modding the whole thing... like why make the menu come out of the bottom? why not the side? lol..., etc, etc... adding to BIN and some other stuff...
Click to expand...
Click to collapse
Good luck with the new ROM whitemonster!
alritewhadeva said:
Good luck with the new ROM whitemonster!
Click to expand...
Click to collapse
yea i'll need it.... just me and my java for dummies lmao
so does anyone have the answer to my APN question?
I can't tell you how to build it into the source but if you place apns-conf.xml in /system/etc then it will ues those APNs, you can even just copy one out of a current build and place it there. You may have to resign the update.zip though.
Hope this helps!
Hello folks.
Does anyone know how to decompile and compile a kernel?
That is the only thing that stops me from developing on my port right know.
What i need to do is to edit some files in ramdisk / init.rc
Thanks in advance.
I used Kernel Kitchen once, and it worked great !
http://forum.xda-developers.com/showthread.php?t=1659584
Hope it helps
RomWiz said:
Hello folks.
Does anyone know how to decompile and compile a kernel?
That is the only thing that stops me from developing on my port right know.
Thanks in advance.
Click to expand...
Click to collapse
When you say decompile, you can only modify the ramdisk. There are two things inside a boot.img, zImage and ramdisk. zImage is compiled via source, where you modify, insert Governers and Schedulers and a lot more. If that's the route you ought to take, you must have Linux, toolchain, source code etc. Ramdisk on the other hand contains few to many things like init.rc where you insert for example g-recovery etc.
Up to you what you wanna do and your definition of "develop".
I need to modify some things in the init.rc
Sent from my phone via tapatalk
Vinzgore said:
I used Kernel Kitchen once, and it worked great !
http://forum.xda-developers.com/showthread.php?t=1659584
Hope it helps
Click to expand...
Click to collapse
There is no download link :what:
Edit: found it
Just use dsixda's Android kitchen: http://forum.xda-developers.com/showthread.php?t=633246
There is an option to decompile the kernel.
N00BY0815 said:
Just use dsixda's Android kitchen: http://forum.xda-developers.com/showthread.php?t=633246
There is an option to decompile the kernel.
Click to expand...
Click to collapse
finally got it working
Thanks
RomWiz said:
finally got it working
Thanks
Click to expand...
Click to collapse
Is it just me or do I not see an option to repack it?
theROMinator said:
Is it just me or do I not see an option to repack it?
Click to expand...
Click to collapse
There should be an option to compile it again.
RomWiz said:
There should be an option to compile it again.
Click to expand...
Click to collapse
It may be because I'm using an older version, I'll download the latest .
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Query on zImage decompile
gabwerkz said:
When you say decompile, you can only modify the ramdisk. There are two things inside a boot.img, zImage and ramdisk. zImage is compiled via source, where you modify, insert Governers and Schedulers and a lot more. If that's the route you ought to take, you must have Linux, toolchain, source code etc. Ramdisk on the other hand contains few to many things like init.rc where you insert for example g-recovery etc.
Up to you what you wanna do and your definition of "develop".
Click to expand...
Click to collapse
I need to decompile zImage, which I extracted from my boot.img, as the Kitchen and other popular tools does not hold any info/way to extract that, could you please help me out.
Links to the tools would be appreciated.
Thanks in advance.
Akshay Goel
aky_style said:
I need to decompile zImage, which I extracted from my boot.img, as the Kitchen and other popular tools does not hold any info/way to extract that, could you please help me out.
Links to the tools would be appreciated.
Thanks in advance.
Akshay Goel
Click to expand...
Click to collapse
sorry for bumping this thread, edited because I didn't read properly >
Has anyone already tried to build cyanmobile from source?I would try but squadzone is constantly updating his github so i should compile in the night...
and the meaning of the thread
dheeraj (dhlalit11) said:
and the meaning of the thread
Click to expand...
Click to collapse
The latest release had some problems for me so if someone had already compiled it i wanted to know his impressions before starting...:angel:
Hi guys...I've just built cyanmobile from source...I created on otapackage with the associated command...I'm waiting for someone wiser than me who could stop me worrying about possible bricks...As far as i know, having chosen the right repos, if something would go wrong, it wouldn't just boot...Am i right???...Waiting for your replies...
EDIT: Installed but not booting...Trying to compile again...
Recompiled and not booting again...I have a doubt: if i git clone the device configuration, do i have to extract also proprietary files?(i think not but i'm new on this so there could be differences)...Thanks for your help...
Asbusto said:
Recompiled and not booting again...I have a doubt: if i git clone the device configuration, do i have to extract also proprietary files?(i think not but i'm new on this so there could be differences)...Thanks for your help...
Click to expand...
Click to collapse
ask squadzone
Messi10 said:
ask squadzone
Click to expand...
Click to collapse
I finally made it...new ui is awesome!!!
Asbusto said:
Has anyone already tried to build cyanmobile from source?I would try but squadzone is constantly updating his github so i should compile in the night...
Click to expand...
Click to collapse
i cant, because i don know about how to build rom from source
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
Before this is flagged as duplicate thread. Or a simple link to the source code of raymanfx source code. Or even the s6 edge plus port.
If I compile just using source code. It doesn't boot, I've tried all I have that I'm limited at.. some driver error Possibly narrowed it down to it being the defconfig.
Need the missing elf file and a working defconfig. (I am trying to fix some bugs until a more suited release is made..
Thank you
@RaymanFX @Ducter
And anyone else with knowledge
LiL_Assassin said:
Before this is flagged as duplicate thread. Or a simple link to the source code of raymanfx source code. Or even the s6 edge plus port.
If I compile just using source code. It doesn't boot, I've tried all I have that I'm limited at.. some driver error Possibly narrowed it down to it being the defconfig.
Need the missing elf file and a working defconfig. (I am trying to fix some bugs until a more suited release is made..
Thank you
@RaymanFX @Ducter
And anyone else with knowledge
Click to expand...
Click to collapse
Have you tried removing the 'OMX' folders from the system lib / lib64 folder? After you compiled the build.
Battlehero said:
Have you tried removing the 'OMX' folders from the system lib / lib64 folder? After you compiled the build.
Click to expand...
Click to collapse
Sorry man my apologies. I am trying the kernel side of things not the actual rom
LiL_Assassin said:
Sorry man my apologies. I am trying the kernel side of things not the actual rom
Click to expand...
Click to collapse
What device variant do you have?
Battlehero said:
What device variant do you have?
Click to expand...
Click to collapse
My friend has c and I have I
LiL_Assassin said:
My friend has c and I have I
Click to expand...
Click to collapse
Upload the build and I'll have a gander.
Battlehero said:
Upload the build and I'll have a gander.
Click to expand...
Click to collapse
I sent you a pm.
Battlehero said:
Upload the build and I'll have a gander.
Click to expand...
Click to collapse
Though if the pm or this doesn't suit you. Here's an upload for you man. We could be doing things wrong.. But we would love the insight. (We think this is the furthest we have managed)
https://www.dropbox.com/sh/oaenmo464fxoycz/AAD1uk-18MaNp0fQVyyjTvPAa?dl=0