Sorry if this is a noobish question!
I'm currently working with the CyanogenMod 9 ICS source, and I'm looking at some files for Framework.apk (specifically frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/tablet/SettingsView.java) and I'd like to make a few changes, just to play around and learn. Now my question is, how would I go about adding this to my ROM? Would I have to run `. build/envsetup.sh && brunch otter` again (otter being for Kindle Fire), and have to take the update.zip file and flash it through recovery? If so, is there anything that I'd have to wipe for it to work properly (like /system)?
Thanks for the input!
Chiggins said:
Sorry if this is a noobish question!
I'm currently working with the CyanogenMod 9 ICS source, and I'm looking at some files for Framework.apk (specifically frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/tablet/SettingsView.java) and I'd like to make a few changes, just to play around and learn. Now my question is, how would I go about adding this to my ROM? Would I have to run `. build/envsetup.sh && brunch otter` again (otter being for Kindle Fire), and have to take the update.zip file and flash it through recovery? If so, is there anything that I'd have to wipe for it to work properly (like /system)?
Thanks for the input!
Click to expand...
Click to collapse
Make -j4 SystemUI then push it to your phone.
Sent from my SGH-I777 using xda premium
Sweet deal, thanks for that!
Related
Hey guys!
I'm trying to port AOSP (as a learning experience), and I've successfully run "make -j2"
But whenever I try to run "make otapackage -j2" I get:
Code:
make: *** No rule to make target `otapackage'. Stop.
Can anyone help me?
Thanks!
rohan32 said:
Hey guys!
I'm trying to port AOSP (as a learning experience), and I've successfully run "make -j2"
But whenever I try to run "make otapackage -j2" I get:
Code:
make: *** No rule to make target `otapackage'. Stop.
Can anyone help me?
Thanks!
Click to expand...
Click to collapse
make otapackage doesn't exist in AOSP iirc, when you make it, you're given yaffs img files on output.
Sent from my R800x using Tapatalk 2
I believe you should be able to look for that script in the Cyanogen Mod source, I think it's a python script typically under " device/yourDevice/release tools/" it something like that.
Sent from my SCH-R760 using Tapatalk 2
paxChristos said:
make otapackage doesn't exist in AOSP iirc, when you make it, you're given yaffs img files on output.
Sent from my R800x using Tapatalk 2
Click to expand...
Click to collapse
Yep thats what I was getting. I tried to flash them and combine the ramdisk with kernel to make a boot.img but it was not booting properly.
thewadegeek said:
I believe you should be able to look for that script in the Cyanogen Mod source, I think it's a python script typically under " device/yourDevice/release tools/" it something like that.
Sent from my SCH-R760 using Tapatalk 2
Click to expand...
Click to collapse
Okay cool I will check it out. Thanks!
Sent from my HTC One X using xda premium
By not booting can you even get a logcat? Or at least pull /proc/kmesg I think it was?
Nope I can't get a logcat, it wouldn't get past the splash screen. And I'm like 90%sure my kernel was just screwed up so that's probably why it wasn't booting.
Sent from my HTC One X using xda premium
If you can reboot without having to pull the battery /proc/kmesg should still be there, and that may provide some insight.
wpa-supplicant error while building AOSP for Huawei U8818
Hi paxChristos
I had done with Android ICS source compilation.It's working fine with emulator.
But when I start a build for real device Huawei Ascend G300 U8818.I get the following error.
make: *** No rule to make target `out/target/product/u8818/obj/STATIC_LIBRARIES/lib_driver_cmd_wext_intermediates/lib_driver_cmd_wext.a', needed by `out/target/product/u8818/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant'. Stop.
Please help me I am googling for 15 days but no clue,guidance.
Can you guide where am I missing?
Thank You.
Recovery image in the OTA zip?
I noticed there is a recovery folder in the OTA zip file. I usually delete this before flashing? Is it okay to leave it or will it overwrite CWM recovery?
How do I remove it when building the otapackage?
Click to expand...
Click to collapse
Never mind I found a makefile patch to remove the recovery img from being included in the OTA zip. I got it working on AOSP ICS. I hope it still works for 4.1 Jellybean
Add ability to enable or disable recovery
Okay almost got camera. Anybody have any ideas on camera please let me know. And I haven't been working on it to much because I've been spending most of my time getting jellybean on the galaxy player.
Don't get mad at me if they brick your device. Infact treat them with a high chance of brickage, unless otherwise noted.
Source: https://github.com/gmillz
cm9:
Stable: Testing
Nightlies:here Not sure if I'm gonna do nightlies
Debloated:here Not sure about this either
gapps:gapps-ics-20120429-signed.zip
International patch: INTL_patch.zip untested so please don't try this unless you know what you are doing. And if you try this please start with your home button not working.
Navbar addon: Almost done. Testing
Okay I think I covered everything
Thanks:
cyanogen
ambrice
zaclimon
Samsung
JackpotClavin
Supermaster34
Okay first reboot to recovery...
Make a backup......
Factory reset........
Mounts and storage > format system.......
Advanced > Wipe Dalvik Cache.......
Install Rom......
Reboot......
If you find something that doesn't work, get a logcat......
Anything I'm missing? let me know
Build Instructions.
For those people that want to help but aren't sure where to start.
Okay first you need ubuntu or linux mint installed and setup.
I might make a guide on how to do this eventually.
But here's the guide.
1. Make a working directory and cd to it.
Code:
mkdir ~/cm9
cd ~/cm9
2. Initialize the repo.
Code:
repo init -u git://github.com/CyanogenMod/android.git
3. Sync the repo. (this will take a while)
Code:
repo sync
4. Get the device tree and vendor files.
Type: gedit .repo/local_manifest.xml
Paste this in the text editor:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="gmillz/device_samsung_venturi_usa" path="device/samsung/venturi_usa" remote="github" revision="ics" />
<project name="gmillz/vendor_samsung_venturi_usa" path="vendor/samsung/venturi_usa" remote="github" revision="ics" />
</manifest>
5. Choose the device.
Code:
. build/envsetup.sh
lunch cm_venturi_usa-eng
(notice the period in front of build)
6. Build
Code:
make -j4 bacon
7. If its successful the rom will be in out/target/product/venturi_usa/
This is a great idea! I will test your CM9 build.
THE EDIT: SystemUI FC'S. After wiping everything. Also, is theme Chooser working for cm9? And did you happen to fix anything/upgrade anything in cm7? Will also post feedback on cm7. And yes changelog please. Sorry if I annoy you haha
ANOTHER EDIT: DO. NOT. FLASH. CM7! Gets your player bricked, stuck on Sammy logo, can't boot into recovery! Do not flash!!
Sent from my YP-G70 using xda app-developers app
Thanks for your hard work, looks great...
Great work! Much needed!
Will help testing ASAP if needed/possible. And on the other hand, I saw your CM10 build section empty. Are you posting anything soon?
Sent from my YP-G70 using xda app-developers app
YoBob said:
Great work! Much needed!
Will help testing ASAP if needed/possible. And on the other hand, I saw your CM10 build section empty. Are you posting anything soon?
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I have a few cm10 builds, but for some reason they won't install properly it hangs on flashing the kernel
gmillz said:
I have a few cm10 builds, but for some reason they won't install properly it hangs on flashing the kernel
Click to expand...
Click to collapse
Check your updater script. Might have some issues there. Also does anyone know why the system UI crashes? I'll see if I can fix it tomorrow
Sent by my Robot Butler
Supermaster34 said:
Check your updater script. Might have some issues there. Also does anyone know why the system UI crashes? I'll see if I can fix it tomorrow
Sent by my Robot Butler
Click to expand...
Click to collapse
with this one
Nope, you just boot up and it tells you that it's crashed and that's it. I was going to replace the .apk of Jackpots CM9 with this one and see if it would work, but I'm recovering my Galaxy Player from a brick
EcHoFiiVe said:
with this one
Nope, you just boot up and it tells you that it's crashed and that's it. I was going to replace the .apk of Jackpots CM9 with this one and see if it would work, but I'm recovering my Galaxy Player from a brick
Click to expand...
Click to collapse
How did you brick?
gmillz said:
How did you brick?
Click to expand...
Click to collapse
Haha you didn't read my other edit did you? Your CM7 Nightly bricked my playaa! It's cool though as I am recovering right now! Couldn't boot into CWM so back to Odin3
EcHoFiiVe said:
Haha you didn't read my other edit did you? Your CM7 Nightly bricked my playaa! It's cool though as I am recovering right now! Couldn't boot into CWM so back to Odin3
Click to expand...
Click to collapse
Sorry. Guess I gotta do a lil more with the kernel source. I'm rebuilding it with the prebuilt kernel for now
New build posted
@gmillz so you are saying that it may be possible for you to port CM 9 and CM10 to the Galaxy 4.0?
Wow, ambitious goals considering that we don't have a booting ICS kernel yet on the 4.0. Do you plan on forming a team? I tried too early on, but it fell apart after awhile. Good luck to you!
EcHoFiiVe said:
with this one
Nope, you just boot up and it tells you that it's crashed and that's it. I was going to replace the .apk of Jackpots CM9 with this one and see if it would work, but I'm recovering my Galaxy Player from a brick
Click to expand...
Click to collapse
Yeah try replacing the apk file. Also Jellybean is soo smooth
Sent from my Nexus 7 using xda app-developers app
Supermaster34 said:
Yeah try replacing the apk file. Also Jellybean is soo smooth
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Damn you!!!!!!!!!!!!!! I wish I had a nexus 7 right now
I'm having some toruble compiling cm7 for the 4.0 player. it hangs when looking for flash_kernel
gmillz said:
New build posted
Click to expand...
Click to collapse
CM7 build? Also, if you are forming a team, I would be more than happy to be the beta tester!
EcHoFiiVe said:
CM7 build? Also, if you are forming a team, I would be more than happy to be the beta tester!
Click to expand...
Click to collapse
Yeah. A new cm7 build. It has the same name but its been updated.
And I may form a team.
You can definitely be the beta tester
Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Jurellz said:
Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Click to expand...
Click to collapse
hope someone contacted him
ztotherad said:
hope someone contacted him
Click to expand...
Click to collapse
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
Did you tell QuBe2 that?
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Jurellz said:
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Click to expand...
Click to collapse
I have used that exact code to boot sense myself!
notta said:
I have used that exact code to boot sense myself!
Click to expand...
Click to collapse
On the Fascinate??
istealhome said:
On the Fascinate??
Click to expand...
Click to collapse
Yes it was but now the fassy has a 1gb sys partition!
notta said:
Yes it was but now the fassy has a 1gb sys partition!
Click to expand...
Click to collapse
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
istealhome said:
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
Click to expand...
Click to collapse
Yes I am speaking of Jt's new partition layout for the 1gb!
notta said:
Yes I am speaking of Jt's new partition layout for the 1gb!
Click to expand...
Click to collapse
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
istealhome said:
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
Click to expand...
Click to collapse
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
notta said:
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
Click to expand...
Click to collapse
Ahhhh I see! Hey! You should talk to xboxfanj; he's been trying to get Sense 2.1 to boot on the fassy for a while now but hasn't been successful, tell him about the new partition layout and it should help him get 4.0 working for our phones! I'd be glad to test out for a dev duo like that
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
this wouldnt work on the showcase right?
Jurellz said:
this wouldnt work on the showcase right?
Click to expand...
Click to collapse
It would still boot most likely on the showcase if it does on the fascinate. I think kernels should be interchangable.
i flashed it and it rebooted and looped in recovery
Jurellz said:
i flashed it and it rebooted and looped in recovery
Click to expand...
Click to collapse
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
xboxfanj said:
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
nevermind i flashed it and this is what i get .
http://pastebin.com/YMQVULvZ
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
Well you could do that if you have the repo as well...
You could also save yourself some time by running "make bootimage"!
I just got done initializing the AOSP JB_SOURCE for the Nexus 7, and am getting ready to attempt a first build, I'd also like to be able to compile CM10 and who knows maybe others but CM10 for sure. My question (although I'm pretty sure the answer is yes) is do I now have to make a new SOURCE directory for CM10 and repeat the process of downloading the whole thing locally for each build I'd like to attempt i.e. CM10, AOKP,MIUI
ect. If so the 150gb I used to create my virtual hard drive isn't going to be enough. I apologize in advance if this question is posted in the wrong place
and I did search first. Thank you.
Vektor67 said:
I just got done initializing the AOSP JB_SOURCE for the Nexus 7, and am getting ready to attempt a first build, I'd also like to be able to compile CM10 and who knows maybe others but CM10 for sure. My question (although I'm pretty sure the answer is yes) is do I now have to make a new SOURCE directory for CM10 and repeat the process of downloading the whole thing locally for each build I'd like to attempt i.e. CM10, AOKP,MIUI
ect. If so the 150gb I used to create my virtual hard drive isn't going to be enough. I apologize in advance if this question is posted in the wrong place
and I did search first. Thank you.
Click to expand...
Click to collapse
For each different ROM type (aosp cm etc.) you need different source code as they are different ROM
Sent from my LG-P350 using xda premium
Sorry it took so long, Thanks for the response. So it seems that for each particular flavor of Android I need the whole source repo synced to my machine.
That doesn't apply to different devices does it? I have an SGS 3 d2spr, and a Nexus 7 it would be fun to run a self built os for each.
Vektor67 said:
Sorry it took so long, Thanks for the response. So it seems that for each particular flavor of Android I need the whole source repo synced to my machine.
That doesn't apply to different devices does it? I have an SGS 3 d2spr, and a Nexus 7 it would be fun to run a self built os for each.
Click to expand...
Click to collapse
No it doesn't apply you just need different device folders and when you compile you use the folder you want.
Sent from my LG-P350 using xda premium
Hi guys, first i want to say that i'm a noob in android developing and i'm trying to learn, so don't kill me for my ignorance. I must also say that i'm not english, so pardon my bad english. Said this, let's go to the point: i want to create a flashable zip of PA's HALO
for my stock and rooted nexus 4. For all i know i must take the commit files and merge them in my decompiled ROM's folder, compile them and flash (or maybe try to run it in an android emulator first?) Well i'm facing a lot of problem: 1 i can't even get git commit files (yes i have git installed) 2 even if i succeed to get the files and compile my ROM and it all works flawlessy i don't know how to make HALO as a flashable mod (i don't even know if it's possible) So, can someone please post here some links where i can learn how to accomplish this (or something similiar, it's just for learning) Also, is someone else interested in doing this? It's just a suggestion ^^
Thanks to all
P.s. Sorry if it's the wrong section.
P.p.s. Error in the title, should be "Create a flashable zip from a git commit"
Sent from my Nexus 4 using xda app-developers app
You can't. Halo is deeply ingrained in the frameworks and system.
Wayne Tech Nexus