The buidlding of aokp is not complete and this error appear..can any developer(s) help me..
using device-specific extensions in device/samsung/common
unable to load device-specific module; assuming none
Traceback (most recent call last):
File "./device/samsung/u8500-common/releasetools/u8500_ota_from_target_files", line 115, in <module>
main(sys.argv[1:])
File "/home/syafiq0408/aokp/build/tools/releasetools/ota_from_target_files", line 873, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./device/samsung/u8500-common/releasetools/u8500_ota_from_target_files", line 63, in WriteFullOTAPackage
if OPTIONS.backuptool:
AttributeError: 'Options' object has no attribute 'backuptool'
make: *** [/home/syafiq0408/aokp/out/target/product/janice/aokp_janice-ota-eng.syafiq0408.zip] Error 1
[email protected]:~/aokp$
SOLVED
Does the syncing part work properly for you. I got some error.
Sent from my GT-I9070 using xda premium
Abhinandh Ajay said:
Does the syncing part work properly for you. I got some error.
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
yup! work nicely and about time to publish my first ever source-built rom..
Edit : and btw, what errors that you facing?
assassin0408 said:
yup! work nicely and about time to publish my first ever source-built rom..
Edit : and btw, what errors that you facing?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43344115&postcount=26
I had posted it here quiet some time back
Abhinandh Ajay said:
http://forum.xda-developers.com/showpost.php?p=43344115&postcount=26
I had posted it here quiet some time back
Click to expand...
Click to collapse
try renaming your local_manifest to local_manifests
assassin0408 said:
try renaming your local_manifest to local_manifests
Click to expand...
Click to collapse
OK thanks and I see you have built AOKP from source. Nice
Sent from my GT-I9070 using xda premium
Related
Welcome! This is MutePatcher: a "one-click" flashable solution that replaces your libaudio with the one from a CM7/CM9 nightly that has the mute/unmute fix in it. This *should* work on any Gingerbread or ICS ROM that uses the CyanogenMod aries libaudio. Anyway, enough chit chat.
NOTE: You'll have to use MutePatcher each time you update to a new version of a ROM.
Download
1.1: androtransfer
Older versions: androtransfer
Changelog
Code:
[b]1.1[/b]
* Removed invalid statement in GB side of updater.sh
[b]1.0[/b]
* First release
To any developers...
Any "chefs" wanting to implement this fix can simply pull the libaudio out of CM7/CM9 and use it in their ROM. Any developers who work from code, can use the changes in this commit.
Disclaimer
I hope this libaudio change is not causing problems for 911, a failure report existed before it was applied in the THS alpha. But just incase, you're flashing this patch yourself, and acknowledge that it could break 911 and indemnify me of any problems or 911 failures caused by this patch.
Thanks
sixstringsg - Hosting
Reserved
Thank you ~~~
which modem best? KA7?JL3?
OrangeYoY said:
Thank you ~~~
which modem best? KA7?JL3?
Click to expand...
Click to collapse
You shouldn't have to change modems for this patch.
OrangeYoY said:
Thank you ~~~
which modem best? KA7?JL3?
Click to expand...
Click to collapse
I find KB5 to work the best for me.
v1.1 posted. Removed invalid statement in GB side of updater.sh.
Thanks FE for making this much easier than it already was.
Just want to thank FE for this... I used this my latest vibrant rom...Hope everything goes better
vibranturk said:
Just want to thank FE for this... I used this my latest vibrant rom...Hope everything goes better
Click to expand...
Click to collapse
Did this work?
On what rom?
Sent from my SGH-T959 using XDA Premium HD app
Panamon said:
Did this work?
On what rom?
Sent from my SGH-T959 using XDA Premium HD app
Click to expand...
Click to collapse
He put it in his Vibrant ICS ROM in his signature. If you have doubts about this, you could always try it on whatever ROM that you're currently running. It's made to work on both GB and ICS ROMs as long as it's based on CyanogenMod code.
Sent from my SGH-T959 using xda premium
I have a question. Is it suppose to be a .htm
Sent from my SGH-T959 using Tapatalk 2
playonline53tms said:
I have a question. Is it suppose to be a .htm
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Click the download link, then download MutePatcher-1.1.zip.
File downloading as htm
both files downloaded as htm, tried zipping the file with same name but could not run on recovery. Any ideas??
Thanks !
Now if we could only get the CM7 HD Videocam to stop the stuttering.
Sent from my SGH-T989 using xda premium
shalomhr said:
both files downloaded as htm, tried zipping the file with same name but could not run on recovery. Any ideas??
Click to expand...
Click to collapse
What browser?
Opera
Sent from my SGH-T959 using xda premium
shalomhr said:
Opera
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
Could you upload the htm file that downloads and send it to me?
Hello guys.
As i know, Broadcom is working with the GSY devs and most probably will release the GPU source. Once the source is out, your device will get CM too. But just to speed up the process, i have started the base of building CM for the cooperve by setting up the device config and makefiles on my github here.
Anyone who wants to go to the next step and extract the proprietary modules and files is welcome to work. Please send me a pull request only when you are sure that the files are correct and up-to-date. Then i will add the files and patches if any.
So lets start building CM. Why wait if we can complete a few things and wait till Broadcom releases the GPU source.
Why don't you post this in the Android Development section?
Sent from my GT-S5830i using xda premium
RubenStauttener said:
Why don't you post this in the Android Development section?
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
The Android Development Section is only for development purposes. I haven't compiled CM. These are just the basic config and makefiles. So this is the correct section..
You are right man
Sent from my GT-s5830i using xda premium
:good:
vkv1995 said:
You are right man
Sent from my GT-s5830i using xda premium
Click to expand...
Click to collapse
carry on bro, gud luck
any news ?
Well some guy in the gal y section got paranoidandroid 4.0.4 working
Sent from my GT-S5830i using xda app-developers app
How we can extract the proprietary modules and files?
I have to wonder a thing? Why
gpu drivers, not extracted from
stock rom ? Using this driver in
cm7. this is very hard to
Just run the mkvendor script in the build environment.
Shaaan said:
Just run the mkvendor script in the build environment.
Click to expand...
Click to collapse
So I connect my phone to pc (with a linux distro right?) and run mkvendor?
Qeemi said:
So I connect my phone to pc (with a linux distro right?) and run mkvendor?
Click to expand...
Click to collapse
You need the source synced from CM github.
Sent from my GT-S5360 using xda app-developers app
Shaaan said:
You need the source synced from CM github.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
One post dude for 1000 posts
I don't get it, Wasn't the user Qeemi sending the signatures to broadcom/samsung so they look back at us?
Fixed swapped colors in cm7 and cm9 with this patch:
Thanks for the information whitexp.
Based on your feedback, we've noted the following issues with the current BCM21553 CM7 port, and will investigate to see if we can help resolve them:
1) Colors are swapped when using software rendering. There are fixes for this, which involve copying libraries from the stock firmware, but they introduce stability issues.
2) libGLES_hgl.so has many shared library dependencies and does not work with the stock surfaceflinger/libui.
I was able to build CM7, with a couple modifications to your device tree, and replicate the color swap issue seen with software rendering.
We're working on a solution to formally release our software, but in the meantime, we have a test patch to fix the color swap issue without using any additional prebuilt libraries.
To try this, please copy the gralloc folder from hardware/libhardware/modules/gralloc ([-LINK-]) to your device tree and apply the attached patch to use the correct fbFormat for the hardware.
You will also need to modify the LOCAL_MODULE in Android.mk with the correct board name.
Thanks,
David
Patch inline:
bcm21553_gralloc_fb_format.patch
Code: [Select]
Code:
diff --git a/modules/gralloc/framebuffer.cpp b/modules/gralloc/framebuffer.cpp
index fe57a8a..a46d46e 100644
--- a/modules/gralloc/framebuffer.cpp
+++ b/modules/gralloc/framebuffer.cpp
@@ -355,7 +355,7 @@ int fb_device_open(hw_module_t const* module, const char* name,
if (status >= 0) {
int stride = m->finfo.line_length / (m->info.bits_per_pixel >> 3);
int format = (m->info.bits_per_pixel == 32)
- ? HAL_PIXEL_FORMAT_RGBX_8888
+ ? HAL_PIXEL_FORMAT_BGRA_8888
: HAL_PIXEL_FORMAT_RGB_565;
#ifdef NO_32BPP
format = HAL_PIXEL_FORMAT_RGB_565;
Click to expand...
Click to collapse
Thanks to dhsu from Broadcom and WhiteXP, Galaxy Y Dev
Does this mean the CM is on the way again? Wasn't the binaries just going to be released?
When the ROM is available for this version of ACE?
NEVER.
Ok?
Qeemi said:
NEVER.
Ok?
Click to expand...
Click to collapse
qemmi
why never ?
Because noobs cant wait.
Inviato dal mio GT-S5830i con Tapatalk 2
Here is the dsixda kitchen edify file I have been using for Nexus 4 (mako).
If using cygwin copy mako file to your cygwin\home\username\tools\edify_defs folder.
Thanks to mskip for mount points
UPDATE:
As promised download the dsixda_JB42.zip and copy the files to the appropriate folder. This will help with Deodexing and by help I mean it will allow all files to be deodexed.
Hi goldfingerfif, first of all thanks a lot for the file, then I would like to use this to build a rom with latest dsixda kitchen release (0.214) but when I’m trying to deodex core.odex I’m getting an error, only with this file, the others works fine. Did you have the same problem? How do you solve it? I tried to do it with api level 16 and 15 but I have the same error. Maybe you did it manually? Or using the kitchen?
Thanks in advance
I'll upload the other changes...I forgot I changed api to 17 and updated smali and baksmali and the version to use file.
Sent from my Nexus 4 using xda app-developers app
Was about to say about updating the smali/baksmali files - I did all that but it was this file I was missing so thanks a lot!
EddyOS said:
Was about to say about updating the smali/baksmali files - I did all that but it was this file I was missing so thanks a lot!
Click to expand...
Click to collapse
Updated OP
goldfingerfif said:
Updated OP
Click to expand...
Click to collapse
Thanks so much!!
Edit: I'm Having troubles with wifi like you with my dsixda's rom, can you tell me how you solved it please?
nitsuajd said:
Thanks so much!!
Edit: I'm Having troubles with wifi like you with my dsixda's rom, can you tell me how you solved it please?
Click to expand...
Click to collapse
I haven't found the script file to add some things that it misses. You can compare the updater-script against mine or I'll post the lines you have to add.
Sent from my Nexus 4 using xda app-developers app
goldfingerfif said:
I haven't found the script file to add some things that it misses. You can compare the updater-script against mine or I'll post the lines you have to add.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks dude, you're right!
Exactly these two lines:
Code:
symlink("/data/misc/wifi/WCNSS_qcom_cfg.ini", "/system/vendor/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/data/misc/wifi/WCNSS_qcom_wlan_nv.bin", "/system/vendor/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
nitsuajd said:
Thanks dude, you're right!
Exactly these two lines:
Code:
symlink("/data/misc/wifi/WCNSS_qcom_cfg.ini", "/system/vendor/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/data/misc/wifi/WCNSS_qcom_wlan_nv.bin", "/system/vendor/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
Click to expand...
Click to collapse
Were you guys using Cygwin when you saw this issue? I know that Cygwin sometimes messes up the symlinks that are not under /system/bin; whereas Linux / OS X are sometimes nicer. In other words, I try not to recommend Cygwin due to these kinds of issues.
@goldfingerfif - thanks for the edify_defs file. I've updated the kitchen to add Nexus 4 support in version 0.216.
I've just added this to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
dsixda said:
Were you guys using Cygwin when you saw this issue? I know that Cygwin sometimes messes up the symlinks that are not under /system/bin; whereas Linux / OS X are sometimes nicer. In other words, I try not to recommend Cygwin due to these kinds of issues.
Click to expand...
Click to collapse
I was using Cygwin
goldfingerfif said:
I was using Cygwin
Click to expand...
Click to collapse
The Windows application that is used to extract the files from the rom has an issue because it removes the symlinks. You will not see this happen in Linux or OS X. However, I have fixed your problem for those specific files in Cygwin.
dsixda said:
The Windows application that is used to extract the files from the rom has an issue because it removes the symlinks. You will not see this happen in Linux or OS X. However, I have fixed your problem for those specific files in Cygwin.
Click to expand...
Click to collapse
Yes I just picked up a 120gb ssd and going to dual boot with Linux as it will make life with android so much easier.
Sent from my Nexus 4 using xda app-developers app
Hello Evereryone,
i have a problem with my first selfmade Rom. I made a rom for me because i want to have a smooth and stylish rom. For this i used cm7..
All things a clear but when i try to install it i become a error: ``E: Can't open /sdcard/roms/x8.zip (bad)
in log :"minzip: Filename contains a invalid character '357' minzip: Invalid filename {at 84}".
I can't find the problem in update script at line 84: symlink("busybox", "/system/xbin/ps");
I hope you can help me:good:.
ItzTazzy said:
Hello Evereryone,
i have a problem with my first selfmade Rom. I made a rom for me because i want to have a smooth and stylish rom. For this i used cm7..
All things a clear but when i try to install it i become a error: ``E: Can't open /sdcard/roms/x8.zip (bad)
in log :"minzip: Filename contains a invalid character '357' minzip: Invalid filename {at 84}".
I can't find the problem in update script at line 84: symlink("busybox", "/system/xbin/ps");
I hope you can help me:good:.
Click to expand...
Click to collapse
You get this error in starting or in middle
(Bad) error means file is wrongly zipped.....
Use winrar & choose 'normal' method while creating your zip from files..
Sent from my X8
rishabh.raj37 said:
You get this error in starting or in middle
Click to expand...
Click to collapse
at starting
@Gogeta i use winrar and i use the normal method
ItzTazzy said:
at starting
@Gogeta i use winrar and i use the normal method
Click to expand...
Click to collapse
Try another methods & see...
But I'm sure its not zipped correctly, happened with me..
U can try clicking 'test' to see if the zip is corrupted...
Sent from my X8
Gogeta said:
Try another methods & see...
But I'm sure its not zipped correctly, happened with me..
U can try clicking 'test' to see if the zip is corrupted...
Sent from my X8
Click to expand...
Click to collapse
I used all methods in winrar and 7zip every time the same sh**. I tested it too but it say nothing.
Simply re-download the zip file.
Sent using Aerodynamics
takeoutttt said:
Simply re-download the zip file.
Sent using Aerodynamics
Click to expand...
Click to collapse
Its a selfmade rom
Sent from my X8
takeoutttt said:
Simply re-download the zip file.
Sent using Aerodynamics
Click to expand...
Click to collapse
Lol
Sent from my E15i using xda app-developers app
takeoutttt said:
Simply re-download the zip file.
Sent using Aerodynamics
Click to expand...
Click to collapse
No
Sent from my SCH-I500 using Tapatalk 2
takeoutttt said:
Simply re-download the zip file.
Sent using Aerodynamics
Click to expand...
Click to collapse
Give this guy a medal. He managed to make me chuckle on a Q&A
Sent from my HTC One X using XDA Premium
RohinZaraki said:
Give this guy a medal. He managed to make me chuckle on a Q&A
Sent from my HTC One X using XDA Premium
Click to expand...
Click to collapse
He deserves a cookie
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
He deserves a cookie
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
A jar-full
Sent via the muffin launch _/^\_
TeeJay!! said:
A jar-full
Sent via the muffin launch _/^\_
Click to expand...
Click to collapse
Hah. I see what you did, there.:good:
In file included from development/tools/emulator/system/camera/EmulatedCamera2.h:28:0,
from development/tools/emulator/system/camera/EmulatedFakeCamera2.h:26,
from development/tools/emulator/system/camera/EmulatedCameraFactory.cpp:28:
hardware/libhardware/include/hardware/camera2.h:112:39: error: 'HAL_PIXEL_FORMAT_IMPLEMENTATION_DEFINED' was not declared in this scope
make: *** [/home/syafiq0408/slim/out/target/product/janice/obj/SHARED_LIBRARIES/camera.goldfish_intermediates/EmulatedCameraFactory.o] Error 1
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
can someone please help me.. i'm trying to build slim rom but during build, this error appear and i dont to how to deal with HAL_PIXEL_FORMAT_IMPLEMENTATION..
Grab the string from system/core/graphics.h and add it to the camera2.h file
Sent from my GT-I9070 using Tapatalk 4 Beta
Maybe you are missing the framework mods for camera hal, pixel format, vibrator, etc from github cause they don't sync automatically with a repo init and sync I guess unless you manually edit your default.xml in .repo folder
Sent from my GT-I9070 using xda app-developers app
Shaaan said:
Grab the string from system/core/graphics.h and add it to the camera2.h file
Sent from my GT-I9070 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I will look into graphic.h and try as u suggested..thanks shaan
frapeti said:
Maybe you are missing the framework mods for camera hal, pixel format, vibrator, etc from github cause they don't sync automatically with a repo init and sync I guess unless you manually edit your default.xml in .repo folder
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
No2 i did not manually edit the default.xml..so what is your suggestion then?btw, i will try as shaan suggested and report back here..
Sent from my GT-I9070 using xda premium