Related
I am compiling Evervolv just to mess around with on the Eris, and I have been getting errors all day, and I have been able to get past most of them. (Sync errors, problems with some folder locations on my desktop) But I just got a long list of errors that are referencing res string values that I've never had before, I will just post a snippet here, but I will also provide a pastebin link to a larger portion of the errors. Any help will be GREATLY appreciated.
frameworks/base/core/res/res/values/public.xml:1532: warning: No comment for public symbol android:style/Widget.Spinner.DropDown
frameworks/base/core/res/res/values/public.xml:657: warning: No comment for public symbol android:style/Widget.TabWidget
frameworks/base/core/res/res/values/public.xml:639: warning: No comment for public symbol android:style/Widget.TextView
frameworks/base/core/res/res/values/public.xml:646: warning: No comment for public symbol android:style/Widget.TextView.PopupMenu
frameworks/base/core/res/res/values/public.xml:647: warning: No comment for public symbol android:style/Widget.TextView.SpinnerItem
frameworks/base/core/res/res/values/public.xml:656: warning: No comment for public symbol android:style/Widget.WebView
Pastebin
lemonoid said:
I am compiling Evervolv just to mess around with on the Eris, and I have been getting errors all day, and I have been able to get past most of them. (Sync errors, problems with some folder locations on my desktop) But I just got a long list of errors that are referencing res string values that I've never had before, I will just post a snippet here, but I will also provide a pastebin link to a larger portion of the errors. Any help will be GREATLY appreciated.
frameworks/base/core/res/res/values/public.xml:1532: warning: No comment for public symbol android:style/Widget.Spinner.DropDown
frameworks/base/core/res/res/values/public.xml:657: warning: No comment for public symbol android:style/Widget.TabWidget
frameworks/base/core/res/res/values/public.xml:639: warning: No comment for public symbol android:style/Widget.TextView
frameworks/base/core/res/res/values/public.xml:646: warning: No comment for public symbol android:style/Widget.TextView.PopupMenu
frameworks/base/core/res/res/values/public.xml:647: warning: No comment for public symbol android:style/Widget.TextView.SpinnerItem
frameworks/base/core/res/res/values/public.xml:656: warning: No comment for public symbol android:style/Widget.WebView
Pastebin
Click to expand...
Click to collapse
This are warnings, no indication in your logs about making your build fail. Something else is going on. Sorry.
well that's what I thought, but upon these warnings, the build aborted and returned to the command line input.
lemonoid said:
well that's what I thought, but upon these warnings, the build aborted and returned to the command line input.
Click to expand...
Click to collapse
Look higher in the logging then, there has to be an error somewhere, unless its gcc -Werror (treats warnings as errors) then it doesn't break the building of the rom. This isn't c/c++ so I don't think this is causing it.
Try rebuilding with make -j1 for a better glimpse of the error
Sent from my GT-P1000 using XDA
help
What is this error?
build/core/product_config.mk:205: *** No matches for product "cyanogen_liquid_mini". Останов.
Device liquid_mini not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for liquid_mini not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:205: *** No matches for product "cyanogen_liquid_mini". Останов.
** Don't have a product spec for: 'cyanogen_liquid_mini'
** Do you have the right repo manifest?
IVAN-ICE said:
What is this error?
build/core/product_config.mk:205: *** No matches for product "cyanogen_liquid_mini". Останов.
Device liquid_mini not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for liquid_mini not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:205: *** No matches for product "cyanogen_liquid_mini". Останов.
** Don't have a product spec for: 'cyanogen_liquid_mini'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
Please don't hi-jack threads. That error tells you what is wrong.
Sent from my Nexus S 4G using xda premium
error
What shall be in the file local_manifest.xml? And where it shall is? thanks!
does anyone know what this can mean...it makes no sense http://pastebin.com/e3vmQd57
xmc wildchild22 said:
does anyone know what this can mean...it makes no sense http://pastebin.com/e3vmQd57
Click to expand...
Click to collapse
These errors are pretty self explanatory. It detected a cycle. There are links to each reported file making a "cycle" when the build detects that it will break.
Sent from my Nexus S 4G using xda premium
Thought I'd start up a general thread where we can come to ask and answer general android building questions. I've been guilty myself of high jacking threads for questions and answering questions regarding porting, compiling, building, etc. Figured I'd try to start up a general thread for just that topic.
I'll start. Having some issues with external/jpeg.
Code:
external/jpeg/jddctmgr.c:350: error: undefined reference to 'jpeg_idct_islow'
external/jpeg/jddctmgr.c:340: error: undefined reference to 'jpeg_idct_ifast'
Have never seen that error before, I'm comparing it to other ROMs that I've built and the file is exactly the same. Not sure what else is linked to it.
@danjull Did you ever find the solution to this? How do you go about troubleshooting build errors (in general)? Do you usually look at what other files that file calls for or so you just kind of stumble through the while source looking for clues?
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
@danjull Did you ever find the solution to this? How do you go about troubleshooting build errors (in general)? Do you usually look at what other files that file calls for or so you just kind of stumble through the while source looking for clues?
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
I haven't yet.
It's a mix. Sometimes it's luck, sometimes it's clear enough so you can just follow the paths. I usually compare the problem source file to CM or another source I know works. Look at commits that happen after a known good build.
danjull said:
I haven't yet.
It's a mix. Sometimes it's luck, sometimes it's clear enough so you can just follow the paths. I usually compare the problem source file to CM or another source I know works. Look at commits that happen after a known good build.
Click to expand...
Click to collapse
Okay, cool. That's pretty much what I've been doing. I've also been doing diff -r between the cm11 source and the rom I'm building for folders that I think may be problematic and printing it to a file. So if you have the cm11 source locally you could try using that for external/jpeg or just external. I tried meld for this sort of thing too, but it didn't seem to be to helpful when it comes to entire directories.
Sent from my Droid DNA using Tapatalk Pro
isnt that gcc related as in the variable isnt defined as used?
figured i should post somewhere where i can find other devs(rather than the omni thread lol)
i got these errors today while building slimkat and after searching every line of code in the whole source, it was only reference once and that was the line that through the error
it makes it more difficult because this is the out/ folder so i really cant compare to CM11:
Code:
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:71: error: undefined reference to 'WebCore::SVGAElement::svgTarget()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:99: error: undefined reference to 'WebCore::SVGAElement::href()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:85: error: undefined reference to 'WebCore::SVGAElement::externalResourcesRequired()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/STATIC_LIBRARIES/third_party_WebKit_Source_core_webcore_derived_gyp_intermediates/SVGElementFactory.cpp:134: error: undefined reference to 'WebCore::SVGAElement::create(WebCore::QualifiedName const&, WebCore::Document*)'
i havent had any success with this
EDIT: nuketown 2025 population slimkat (da fuq did i just say?)
anyways resyncing the repos tonight, maybe it will be better to just start over
EDIT: nuking solves all problems
I'm trying to build tripndroid, I ran into a few other errors that I fixed already, but I'm hitting this now
Code:
In file included from frameworks/av/services/audioflinger/Tracks.cpp:32:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
In file included from frameworks/av/services/audioflinger/Effects.cpp:30:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
frameworks/av/services/audioflinger/Effects.cpp: In member function 'android::sp<android::AudioFlinger::EffectModule> android::AudioFlinger::EffectChain::getEffectFromIndex_l(int)':
frameworks/av/services/audioflinger/Effects.cpp:1343:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/Tracks.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/Effects.o] Error 1
In file included from frameworks/av/media/mediaserver/main_mediaserver.cpp:32:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/EXECUTABLES/mediaserver_intermediates/main_mediaserver.o] Error 1
In file included from frameworks/av/services/audioflinger/AudioFlinger.cpp:46:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
In file included from frameworks/av/services/audioflinger/AudioFlinger.cpp:46:0:
frameworks/av/services/audioflinger/AudioFlinger.h: In constructor 'android::AudioFlinger::AudioFlinger()':
frameworks/av/services/audioflinger/AudioFlinger.h:833:13: warning: 'android::AudioFlinger::mGlobalEffectEnableTime' will be initialized after [-Wreorder]
In file included from frameworks/av/services/audioflinger/AudioFlinger.cpp:46:0:
frameworks/av/services/audioflinger/AudioFlinger.h:779:31: warning: 'volatile bool android::AudioFlinger::mAllChainsLocked' [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.cpp:146:1: warning: when initialized here [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.cpp: In member function 'virtual android::sp<android::IDirectTrack> android::AudioFlinger::createDirectTrack(pid_t, uint32_t, audio_channel_mask_t, audio_io_handle_t, int*, android::IDirectTrackClient*, audio_stream_type_t, android::status_t*)':
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:9: error: 'AudioEventObserver' was not declared in this scope
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:29: error: 'obv' was not declared in this scope
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:48: error: expected type-specifier before 'AudioEventObserver'
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:48: error: expected '>' before 'AudioEventObserver'
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:48: error: expected '(' before 'AudioEventObserver'
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:68: error: expected primary-expression before '>' token
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:82: error: expected ')' before ';' token
frameworks/av/services/audioflinger/AudioFlinger.cpp:653:23: error: 'audio_stream_out_t' has no member named 'set_observer'
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioFlinger.o] Error 1
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
In file included from frameworks/av/services/audioflinger/AudioFlinger.h:440:0,
from frameworks/av/services/audioflinger/Threads.cpp:52:
frameworks/av/services/audioflinger/Threads.h: In constructor 'android::AudioFlinger::PlaybackThread::PlaybackThread(const android::sp<android::AudioFlinger>&, android::AudioFlinger::AudioStreamOut*, audio_io_handle_t, audio_devices_t, android::AudioFlinger::ThreadBase::type_t)':
frameworks/av/services/audioflinger/Threads.h:628:14: warning: 'android::AudioFlinger::PlaybackThread::mScreenState' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/Threads.h:564:26: warning: 'audio_output_flags_t android::AudioFlinger::PlaybackThread::mOutputFlags' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:1050:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h: In constructor 'android::AudioFlinger::DirectAudioTrack::DirectAudioTrack(const android::sp<android::AudioFlinger>&, int, android::AudioFlinger::AudioSessionDescriptor*, android::IDirectTrackClient*, audio_output_flags_t)':
frameworks/av/services/audioflinger/AudioFlinger.h:594:26: warning: 'android::AudioFlinger::DirectAudioTrack::mAudioFlinger' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:541:13: warning: 'int android::AudioFlinger::DirectAudioTrack::mOutput' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:541:13: warning: 'android::AudioFlinger::DirectAudioTrack::mOutput' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:540:33: warning: 'android::AudioFlinger::AudioSessionDescriptor* android::AudioFlinger::DirectAudioTrack::mOutputDesc' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:540:33: warning: 'android::AudioFlinger::DirectAudioTrack::mOutputDesc' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:539:29: warning: 'android::IDirectTrackClient* android::AudioFlinger::DirectAudioTrack::mClient' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:574:14: warning: 'android::AudioFlinger::DirectAudioTrack::mEffectConfigChanged' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:572:14: warning: 'bool android::AudioFlinger::DirectAudioTrack::mKillEffectsThread' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:572:14: warning: 'android::AudioFlinger::DirectAudioTrack::mKillEffectsThread' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:543:30: warning: 'audio_output_flags_t android::AudioFlinger::DirectAudioTrack::mFlag' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp: In member function 'virtual android::status_t android::AudioFlinger::DirectAudioTrack::start()':
frameworks/av/services/audioflinger/Threads.cpp:5565:30: error: 'audio_stream_out_t' has no member named 'start'
frameworks/av/services/audioflinger/Threads.cpp: In member function 'virtual void android::AudioFlinger::DirectAudioTrack::stop()':
frameworks/av/services/audioflinger/Threads.cpp:5577:26: error: 'audio_stream_out_t' has no member named 'stop'
frameworks/av/services/audioflinger/Threads.cpp: In member function 'virtual ssize_t android::AudioFlinger::DirectAudioTrack::write(const void*, size_t)':
frameworks/av/services/audioflinger/Threads.cpp:5593:26: error: 'audio_stream_out_t' has no member named 'is_buffer_available'
frameworks/av/services/audioflinger/Threads.cpp: In member function 'void android::AudioFlinger::DirectAudioTrack::allocateBufPool()':
frameworks/av/services/audioflinger/Threads.cpp:5667:26: error: 'audio_stream_out_t' has no member named 'get_buffer_info'
frameworks/av/services/audioflinger/Threads.cpp:5673:20: error: invalid use of incomplete type 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5666:12: error: forward declaration of 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5674:26: error: invalid use of incomplete type 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5666:12: error: forward declaration of 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5678:30: error: invalid use of incomplete type 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5666:12: error: forward declaration of 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
I don't even know where to start with that... This is the part it's complaining about in Audioflinger.h:
Code:
#ifdef QCOM_HARDWARE
// server side of the client's IAudioTrack
class DirectAudioTrack : public android::BnDirectTrack,
public AudioEventObserver
{
I think maybe it's missing an #include or something? I just don't understand why I'm getting all of these errors. I would assume anyone building the ROM would get the same ones?
jamiethemorris said:
I'm trying to build tripndroid, I ran into a few other errors that I fixed already, but I'm hitting this now
Code:
In file included from frameworks/av/services/audioflinger/Tracks.cpp:32:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
I think maybe it's missing an #include or something? I just don't understand why I'm getting all of these errors. I would assume anyone building the ROM would get the same ones?
Click to expand...
Click to collapse
What have java version are you using?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
What have java version are you using?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'll have to check when I get home. I'm pretty sure I'm using open jdk6 though.
Sent from my Droid DNA using Tapatalk Pro
---------- Post added at 07:23 PM ---------- Previous post was at 06:57 PM ----------
java version "1.6.0_51"
Java(TM) SE Runtime Environment (build 1.6.0_51-b09)
Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01, mixed mode)
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Liquid won't flash. No idea why. It just reboots instantly as soon as it starts flashing.
Sent from my iPad using Tapatalk
jamiethemorris said:
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Click to expand...
Click to collapse
Search for 1024 in the kernel defconfig that is used. There is an config named something with FRAME that sets the size to warn on. You can change it to 2048 to fix the build.
---------- Post added at 06:13 AM ---------- Previous post was at 06:10 AM ----------
jamiethemorris said:
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Click to expand...
Click to collapse
Also, run
brunch dlx 2>&1 | tee /tmp/build.txt
After the build, that tmp file should hold all the text from the build.
crpalmer said:
Search for 1024 in the kernel defconfig that is used. There is an config named something with FRAME that sets the size to warn on. You can change it to 2048 to fix the build.
---------- Post added at 06:13 AM ---------- Previous post was at 06:10 AM ----------
Also, run
brunch dlx 2>&1 | tee /tmp/build.txt
After the build, that tmp file should hold all the text from the build.
Click to expand...
Click to collapse
Thank you. Do you think that has anything to do with why it won't flash?
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Thank you. Do you think that has anything to do with why it won't flash?
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
No, the frame size warning is just there to ensure people don't accidentally so something stupid and breaks the build to let them know. 1K is arbitrary so 2K is also fine.
Can someone give me a little explanation on how the manifest works? Like how it knows which branches to pull of each git project? I'm trying to build carbon and it's running into an issue about BluetoothLwPwrProximityMonitor being undefined. For whatever reason the BluetoothLwPwrProximityMonitor.java file was deleted in the cm11 BluetoothExt repo. This was several months ago though. Both CM11 and ProBam build fine, and they don't have any of the pxpmonitorservice stuff. So it looks like they're using the cm-10.2 or stable/cm-11.0 branch. But it the manifests I don't see anything that differentiates which branch they pull from. Basically, I think I need to have Carbon use stable/cm-11.0 instead of cm-11.0 and then I think it will build, but I just want to make sure I'm doing it right.
EDIT: I tried that, but it doesn't matter now because it gives me this all of a sudden:
Code:
make: *** No rule to make target `/run/media/jamiethemorris/LinuxExternal/android/carbon_kk/out/host/linux-x86/bin/mkbootimg', needed by `/run/media/jamiethemorris/LinuxExternal/android/carbon_kk/out/target/product/dlx/boot.img'. Stop.
Really weird. I'm guessing it's misleading. I tried putting BluetoothExt back to how it was but I get the same error. It got way further than this before.
Code:
find -name mkbootimg*
./system/core/mkbootimg
./system/core/mkbootimg/mkbootimg.c
./external/genext2fs/mkbootimg_ext2.sh
Also, liquid is now hitting this kernel error:
Code:
liquidsmooth_kk/kernel/htc/m7/drivers/video/msm/mipi_novatek.c:569:37: warning: argument to ‘sizeof’ in ‘snprintf’ call is the same expression as the destination; did you mean to provide an explicit length? [-Wsizeof-pointer-memaccess]
error, forbidden warning: mipi_novatek.c:569
I don't know why it's having so much trouble. I'm guessing I will find this in the defconfig as well?
Maybe building ROMs is just not for me...
Don't get discouraged. I'm fixing to start learning, and I need you to figure it all out so I can ask you all my noob questions.
Sent from my HTC6435LVW using Tapatalk
armydog13 said:
Don't get discouraged. I'm fixing to start learning, and I need you to figure it all out so I can ask you all my noob questions.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Thanks. For starters, read this http://xda-university.com/as-a-developer/getting-started-building-android-from-source and this http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code also this link is helpful because you will need to sync CM's repos at the same time for the device tree and kernel, and sometimes other repos http://xda-university.com/as-a-developer/repo-tips-tricks
jamiethemorris said:
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Click to expand...
Click to collapse
I came here to ask some questions about building liquid myself but since you got it booting guess i might as well give on up huh? I guess I should bring up what im doing anyways so I dont accidentally start on a port one of the pros is starting on lol
DREWHAMM974 said:
I came here to ask some questions about building liquid myself but since you got it booting guess i might as well give on up huh? I guess I should bring up what im doing anyways so I dont accidentally start on a port one of the pros is starting on lol
Click to expand...
Click to collapse
No, don't give up, nothing wrong with teamwork and some learning experience. I don't have it booting, it fails when I flash it and I can't get it to build with the stock kernel
Sent from my Droid DNA using Tapatalk
Q&A for [SOURCES][DEVONLY] CyanogenMod 11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SOURCES][DEVONLY] CyanogenMod 11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CM11
Thank you for your efforts and hardwork. I look forward to running cm 11 on the alpha.
Congo from India. Pl. Check it and tell if all features working or not..
what about CM12 any news on that?
HELLO?
Hi. Nice to catch this thread.
I just wanna know... Can korean alpha get this cm11? Or...can get g850f only?
And i wanna talk to you. Cheer up!
Thank you for developing this alpha, modfunk!
Finally, good luck for my ss g alpha....
(i just wanna 'plus alpha' yeah!)
We will only know if you try. I don't know your hardware I only own a G850F
Hi there,
I can hardly wait to get CM11 on my device. Otherwise using this phone is pointelss for me. I would throw the whole Samsung stock ROM to somewhere that it can burn slowly and flawlessly to the ground.
Thanks guys for your efforts!
Can anybody show video hows cyano 11 on alpha ?
thnx
Simona Simmy said:
Can anybody show video hows cyano 11 on alpha ?
thnx
Click to expand...
Click to collapse
CM11 isn't ready for consuming yet on the alpha.
Yet this is called "Devonly" (developers only) and "source".
This means: get github access, get the source, get the tools, compile it, debug compilation process, fix compilation process, get a image.
Pray, push it on your device, hopefully you won't have softbricked your device.
Debug the features that are missing, fix the bugs, find solutions, recompile.
At the moment, modpunkt still has the following (major) issues:
http://forum.xda-developers.com/showpost.php?p=57233732&postcount=46
https://www.youtube.com/watch?v=1_H4AlQaNa0 seems to be a video that explains how to compile from source, it is not mine, but looks good from a first glance at google.
Simona Simmy said:
Can anybody show video hows cyano 11 on alpha ?
thnx
Click to expand...
Click to collapse
It's not useable. No network connection is working yet ...
Thank youu
Thanks to dev(s) from me too. It's interesting to follow your progress, it reminds me of the good old zte blade 1 ages where few devs hacked the **** out of that device.
How can I help ?
Hello guys, I have a Galaxy Alpha for over a week now... And just can't stand that touchwiz stock rom anymore..
So what can I do to help you guys ? I have no experience in porting roms, but I have SM-G850F and just want to help you guys.. For example I can test everything you give me and other things Just let me know
will try to help
Hello, @modpunk
Although I have no CM porting experience I know C and Java. I have set up my CM environment, built and deployed my own unofficial ROM to one of my other devices.
My SM-G850F should arrive this coming week and I just may try help with the TODO. I'm a little confused trying to find out what are your repos to place in my local manifests, can you please list and describe them?
TIA,
Nuno
nuno.f.ferreira said:
Hello, @modpunk
Although I have no CM porting experience I know C and Java. I have set up my CM environment, built and deployed my own unofficial ROM to one of my other devices.
My SM-G850F should arrive this coming week and I just may try help with the TODO. I'm a little confused trying to find out what are your repos to place in my local manifests, can you please list and describe them?
TIA,
Nuno
Click to expand...
Click to collapse
Everything is in the readme of the cm-11.0 rep
http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-11.0
Building CM11 for Samsung Galaxy Alpha
Hello,
Was trying to post in http://forum.xda-developers.com/galaxy-alpha/orig-development/sources-cyanogenmod-11-0-t2933305 but apparently need to do it here.
Building with this instructions http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-11.0 have the following error. Thought I ask before starting to dig...
<CONSOLE>
target thumb C++: hwcomposer.exynos5 <= hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'bool hdmi_is_preset_supported(exynos5_hwc_composer_device_1_t*, int)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:462:32: error: aggregate 'hdmi_is_preset_supported(exynos5_hwc_composer_device_1_t*, int)::v4l2_dv_enum_preset enum_preset' has incomplete type and cannot be defined
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:469:45: error: 'VIDIOC_ENUM_DV_PRESETS' was not declared in this scope
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'int hdmi_get_config(exynos5_hwc_composer_device_1_t*)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:577:27: error: aggregate 'hdmi_get_config(exynos5_hwc_composer_device_1_t*)::v4l2_dv_preset preset' has incomplete type and cannot be defined
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:578:32: error: aggregate 'hdmi_get_config(exynos5_hwc_composer_device_1_t*)::v4l2_dv_enum_preset enum_preset' has incomplete type and cannot be defined
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:586:39: error: 'VIDIOC_G_DV_PRESET' was not declared in this scope
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'int hdmi_output(exynos5_hwc_composer_device_1_t*, hdmi_layer_t&, hwc_layer_1_t&, private_handle_t*, int, int*)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:1159:52: error: invalid conversion from '__u32 {aka unsigned int}' to 'v4l2_buf_type' [-fpermissive]
In file included from hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.h:52:0,
from hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:27:
./hardware/samsung_slsi/exynos/include/exynos_v4l2.h:76:5: error: initializing argument 2 of 'int exynos_v4l2_streamon(int, v4l2_buf_type)' [-fpermissive]
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: At global scope:
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:4586:1: warning: missing initializer for member 'hw_module_t::dso' [-Wmissing-field-initializers]
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:4586:1: warning: missing initializer for member 'hw_module_t::reserved' [-Wmissing-field-initializers]
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'int hdmi_get_config(exynos5_hwc_composer_device_1_t*)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:592:1: error: control reaches end of non-void function [-Werror=return-type]
cc1plus: some warnings being treated as errors
make: *** [/opt/android/system/out/target/product/slte/obj/SHARED_LIBRARIES/hwcomposer.exynos5_intermediates/ExynosHWC.o] Error 1
</CONSOLE>
TIA,
Nuno
nuno.f.ferreira said:
Hello,
Was trying to post in http://forum.xda-developers.com/galaxy-alpha/orig-development/sources-cyanogenmod-11-0-t2933305 but apparently need to do it here.
Building with this instructions http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-11.0 have the following error. Thought I ask before starting to dig...
<CONSOLE>
target thumb C++: hwcomposer.exynos5 <= hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'bool hdmi_is_preset_supported(exynos5_hwc_composer_device_1_t*, int)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:462:32: error: aggregate 'hdmi_is_preset_supported(exynos5_hwc_composer_device_1_t*, int)::v4l2_dv_enum_preset enum_preset' has incomplete type and cannot be defined
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:469:45: error: 'VIDIOC_ENUM_DV_PRESETS' was not declared in this scope
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'int hdmi_get_config(exynos5_hwc_composer_device_1_t*)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:577:27: error: aggregate 'hdmi_get_config(exynos5_hwc_composer_device_1_t*)::v4l2_dv_preset preset' has incomplete type and cannot be defined
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:578:32: error: aggregate 'hdmi_get_config(exynos5_hwc_composer_device_1_t*)::v4l2_dv_enum_preset enum_preset' has incomplete type and cannot be defined
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:586:39: error: 'VIDIOC_G_DV_PRESET' was not declared in this scope
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'int hdmi_output(exynos5_hwc_composer_device_1_t*, hdmi_layer_t&, hwc_layer_1_t&, private_handle_t*, int, int*)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:1159:52: error: invalid conversion from '__u32 {aka unsigned int}' to 'v4l2_buf_type' [-fpermissive]
In file included from hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.h:52:0,
from hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:27:
./hardware/samsung_slsi/exynos/include/exynos_v4l2.h:76:5: error: initializing argument 2 of 'int exynos_v4l2_streamon(int, v4l2_buf_type)' [-fpermissive]
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: At global scope:
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:4586:1: warning: missing initializer for member 'hw_module_t::dso' [-Wmissing-field-initializers]
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:4586:1: warning: missing initializer for member 'hw_module_t::reserved' [-Wmissing-field-initializers]
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp: In function 'int hdmi_get_config(exynos5_hwc_composer_device_1_t*)':
hardware/samsung_slsi/exynos5-insignal/libhwc/ExynosHWC.cpp:592:1: error: control reaches end of non-void function [-Werror=return-type]
cc1plus: some warnings being treated as errors
make: *** [/opt/android/system/out/target/product/slte/obj/SHARED_LIBRARIES/hwcomposer.exynos5_intermediates/ExynosHWC.o] Error 1
</CONSOLE>
TIA,
Nuno
Click to expand...
Click to collapse
seems you haven't applied this patch: http://review.cyanogenmod.org/#/c/78565/
Thanks for the reply.
Hmm, I have CyanogenMod/android_hardware_samsung_slsi_exynos5-insignal in my local manifest and repos are synced. Do you mean there are patch sets that have to be applied manually? If so, do you know if anymore besides this one?
nuno.f.ferreira said:
Thanks for the reply.
Hmm, I have CyanogenMod/android_hardware_samsung_slsi_exynos5-insignal in my local manifest and repos are synced. Do you mean there are patch sets that have to be applied manually? If so, do you know if anymore besides this one?
Click to expand...
Click to collapse
yes, you have to apply that patch manually. No more patches are needed to build cm at this moment.
Thanks. Did that.
Now I have this. Is this known?
<CONSOLE>
Package OTA: /opt/android/system/out/target/product/slte/cm_slte-ota-67a8ffa7a4.zip
MKBOOTIMG= \
./build/tools/releasetools/ota_from_target_files -v \
-p /opt/android/system/out/host/linux-x86 \
-k build/target/product/security/testkey \
--backup=true \
--override_device=auto \
\
\
/opt/android/system/out/target/product/slte/obj/PACKAGING/target_files_intermediates/cm_slte-target_files-67a8ffa7a4.zip /opt/android/system/out/target/product/slte/cm_slte-ota-67a8ffa7a4.zip
unzipping target target-files...
running: unzip -o -q /opt/android/system/out/target/product/slte/obj/PACKAGING/target_files_intermediates/cm_slte-target_files-67a8ffa7a4.zip -d /tmp/targetfiles-6wcH3r
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 1132, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 1075, in main
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/opt/android/system/build/tools/releasetools/common.py", line 155, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(zip, d["fstab_version"])
File "/opt/android/system/build/tools/releasetools/common.py", line 227, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: "%s"" % (line,))
ValueError: malformed recovery.fstab line: "/efs ext4 /dev/block/mmcblk0p3 flags=backup=1"
make: *** [/opt/android/system/out/target/product/slte/cm_slte-ota-67a8ffa7a4.zip] Error 1
</CONSOLE>
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking
SGP712 comilation of 28.0.A.7.251 fails
@jerpelea
Code:
CC drivers/input/touchscreen/maxim_sti.o
drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt':
drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
pdata->stylus_support = (u16)val;
^
drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg':
drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed
make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:815: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I will revert your stylus (really?) patches to version .31
Or please update a declaration struct maxim_sti_pdata at the proper location.
EDIT: I added
Code:
u32 stylus_support;
to 28.0.A.7.251/kernel/include/linux/maxim_sti.h
EDIT2:
I flashed the DE 28.0.A.7.251 - works.
I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.
I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop
EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58
DHGE said:
@jerpelea
Code:
CC drivers/input/touchscreen/maxim_sti.o
drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt':
drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
pdata->stylus_support = (u16)val;
^
drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg':
drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed
make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:815: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I will revert your stylus (really?) patches to version .31
Or please update a declaration struct maxim_sti_pdata at the proper location.
EDIT: I added
Code:
u32 stylus_support;
to 28.0.A.7.251/kernel/include/linux/maxim_sti.h
EDIT2:
I flashed the DE 28.0.A.7.251 - works.
I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.
I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop
EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58
Click to expand...
Click to collapse
28.0.A.8.251 compiles and boots first time for me on Z3+. EDIT: seems to perform better too, with Antutu benchmark score going up from 47,800 to ~53,000
28.0.A.8.251 compiles and boots first time for me on Z3+
Click to expand...
Click to collapse
I hope they tested the source on this device.
Maybe they do not test all kitakami devices e.g. SGP712
DHGE said:
I hope they tested the source on this device.
Maybe they do not test all kitakami devices e.g. SGP712
Click to expand...
Click to collapse
Seems ok for now. I'm running it at the moment on a custom rom that has xposed installed and it's so far stable. This is the kernel in the current firmware, so I'm sure it's been tested.
AOSP uses a different kernel source
https://github.com/sonyxperiadev/kernel
please clarify
@jerpelea
All I write on compiling applies to my SGP712.
AOSP uses a different kernel source
Click to expand...
Click to collapse
Than what?
The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:
@kholkkholk on 29 May input: TS: Add Maxim SmartTouch Imager driver
Click to expand...
Click to collapse
I think that is OK for karin_windy.
I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...
I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).
Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.
btw: # CONFIG_DM_VERITY is not set
Hi
i have recompiled the kernel
https://github.com/sonyxperiadev/kernel
i have tested karin_windy here with same V11 archive and flashed all 3 partitions
i have touch screen and device working fine
br
J
DHGE said:
@jerpelea
All I write on compiling applies to my SGP712.
Than what?
The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:
I think that is OK for karin_windy.
I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...
I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).
Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.
btw: # CONFIG_DM_VERITY is not set
Click to expand...
Click to collapse
Thanks @jerpelea for the update!
I am mostly interested in the stagefright patches.
I do not find them in my repo synced AOSP tree.
The (compiled) patches are in ROM 28.0.A.8.251 though and last week I finally managed to get this rooted and running on my karin_windy.
I will try AOSP again if I have more time.
How is the AOSP source for the Z4, does it build yet? Looks like things are building towards a TWRP/AOSP release.
Sent from my SGP712 using Tapatalk
Is there a news on a ASOP build for the Z4?
Sent from my SGP771 using Tapatalk
FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?
streilu said:
FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?
Click to expand...
Click to collapse
FreeXperia has "karin windy" builds too.
Look here: http://fxpblog.co/aosp/aosp-5-1/ and choose the first of the 2 possible mirror providers (different sets of files are offered at each), scroll to the buttom and the latest ASOP for the Z4 is there. I have yet to try and install it as the download consistently fails and then forces me to wait for 24 hours.
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J
Is anybody able to download any of the ASOP builds from http://fxpblog.co/ ?
Could they be mirrored, at a more "normal" file host?
I can upload it later today to your preferred hoster if you tell me.
streilu said:
I can upload it later today to your preferred hoster if you tell me.
Click to expand...
Click to collapse
How about https://www.androidfilehost.com/ that would seem appropriate. But frankly any host which does not force you to pay for downloads.
Got no dev account on AFH, sorry.
Hope this is ok: https://mega.nz/#!aEZlnZJS
@HotBlack77 please tell me how AOSP feels on the Z4 tab. I'm unsure about the BL unlock thing.
Gesendet von meinem SGP712 mit Tapatalk
Hi all
We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Enjoy
J
Hi, I'm build cyanogenmod with CAF kernel LA.BR.1.1.3-05510-8x16.0 with small modifications. I'm running into a problem where any function defined in include/linux/cpufreq.h is causing implicit declaration warnings, which are treated as errors. I know I can use cc call-disable, but that is likely to cause errors later on. I have uploaded a log of building and the error, and the defconfig I'm using to build the kernel. http://1drv.ms/1QyaAXD Any help would be appreciated.
zowpow said:
Hi, I'm build cyanogenmod with CAF kernel LA.BR.1.1.3-05510-8x16.0 with small modifications. I'm running into a problem where any function defined in include/linux/cpufreq.h is causing implicit declaration warnings, which are treated as errors. I know I can use cc call-disable, but that is likely to cause errors later on. I have uploaded a log of building and the error, and the defconfig I'm using to build the kernel. http://1drv.ms/1QyaAXD Any help would be appreciated.
Click to expand...
Click to collapse
Hi,
I've been into same error;
It mostly happens when you try to compile 64 bit kernel for a device that is currently running 32 bit one.
I FIXED mine by by removing the '-Werror' related warnings. Go to the main Makefile in your kernel directory and search for 'werror' whatever the error is; remove the lines or use '#' before to comment it out.