Hey Guys,
Could you please tell me where / how to get source code for Amlogic devices? I am specifically interested in S912 for my Beelink GT1 Ultimate. The recent firmware updates have made the device performance so bad. Being an octa core device with 3G DDR4 ram, this not what the device deserves. All Beelink does is download their source and just change the logo.
I have made my mind and decided to build a better firmware myself. Who is with me to help?
I have read that Nexbox revealed the source for its tv box but its very old. Tried asking the same in freaktab forum but none bothered.
To download the source from Amlogic website we need to be authorized. i.e., We need to send our ssh key to them so that we can sync the source. I mailed the amlogic team but no response for over a week.
I see some guys like Megandanz ported stock Android TV to these devices... If you are a one of the ROM devs, It would be great if you could add some notes on this.
This is my last effort asking here! Looking with some hope!
No chance..
Ricky Divjakovski said:
No chance..
Click to expand...
Click to collapse
Thanks, still worth a short
I hope someone will help
irfanjunaid said:
Thanks, still worth a short
I hope someone will help
Click to expand...
Click to collapse
Not gonna put anything out there but the mbox is opensource, i also have confidential information on the future of the source code, patience is key
irfanjunaid said:
I hope someone will help
Click to expand...
Click to collapse
neh, only android tv box producers have access , and they signed a document for not giving the source code to others
You can get source to most of it via the Khadas VIM2 github.
Some parts are still just binary blobs though.
https://github.com/khadas
Hi there,
Recently, I was curious to know and learn how to build Android from source code.
I have AceMax M8S+ and I want to install stock Android TV os in it.
I have done the research and found a few repositories that have Amlogic build tools and etc.
I downloaded the manifest, update to the proper revisions and old packages and still got an error after 1 hour of building.
Code:
device/amlogic/n200/overlay/packages/apps/DeskClock/AndroidManifest.xml:39: error: Error: No resource found that matches the given name (at 'theme' with value '@style/DeskClock').
device/amlogic/n200/overlay/packages/apps/DeskClock/AndroidManifest.xml:179: error: Error: No resource found that matches the given name (at 'theme' with value '@style/ScreensaverSettingsActivityTheme').
device/amlogic/n200/overlay/packages/apps/DeskClock/AndroidManifest.xml:194: error: Error: No resource found that matches the given name (at 'theme' with value '@style/TimerAlertFullScreenTheme').
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
make: Leaving directory `/home/t1000/android'
#### make failed to build some targets (01:47:50 (hh:mm:ss)) ####
Here are the sources that I found
amlogic_android_manifest -> github/firmanjml
android_device_amlogic -> github/Android-Amlogi
Related
Hi, I'm VisualTech48 and i own a Galaxy S Plus (I9001).
Our great Developers [Arco98, Ivendor, Doomsday98, Oisis, etc.] are developing ICS Roms and trying to make Jelly Bean too but we are missing a key element of this game.
It's the 3.0.x Kernel. We really need a good coder.
If anyone knows, or can help us code this kernel we are Ready to donate, and help by giving logs if even needed.
If we donate to someone, he/she must:
Help our devs with codeing
Give us a booting kernel
We have done allready a part of the project but we need help with codeing, that is why I even started this thread.
What has oisis done:
Added board-ariesve.c here:
arch/arm/mach-msm/board-ariesve.c
Included Ariesve board to Kconfig and Makefile.
Added missing files:
include/linux/fsa9480.h
arch/arm/mach-msm/include/mach/msm_reqs.h
Click to expand...
Click to collapse
Compilation error:
Code:
arch/arm/mach-msm/board-ariesve.c: In function 'pm8058_gpios_init':
arch/arm/mach-msm/board-ariesve.c:329: error: variable 'sdcc_det' has initializer but incomplete type
arch/arm/mach-msm/board-ariesve.c:330: error: unknown field 'direction' specified in initializer
arch/arm/mach-msm/board-ariesve.c:330: warning: excess elements in struct initializer
error, forbidden warning: board-ariesve.c:330
make[1]: *** [arch/arm/mach-msm/board-ariesve.o] Error 1
What needs to be done:
include and port file from 2.6.35.X - arch/arm/mach-msm/board-ariesve.c
include/find missing drivers for i9001
Click to expand...
Click to collapse
We whould really apriciate if someone can help us because this kernel can open a whole new page for our phone.
Why did i remade a new thread? Because i think we have more chances of reply then in the I9000 Forum.
Thank you for reading this, VisualTech48
Original Thread: http://forum.xda-developers.com/showthread.php?t=1742976
hey, I followed the tutorial about "Compiling JB on Ubuntu" and I stuck on this error:
Code:
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
Device jlo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 59, in <module>
result = json.loads(urllib2.urlopen(githubreq).read())
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 400, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 513, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 438, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 372, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 521, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
** Don't have a product spec for: 'cm_jlo'
** Do you have the right repo manifest?
I have device tree and proprietary files and admint that I have read whole tutorial 10x times but tip at the and didn't help.
I tried making many changes in files but no result.
I spend hours on doing all those things and like always nothing work, please show me the way I should follow.
lozohcum said:
I have device tree and proprietary files and admint that I have read whole tutorial 10x times but tip at the and didn't help.
I tried making many changes in files but no result.
I spend hours on doing all those things and like always nothing work, please show me the way I should follow.
Click to expand...
Click to collapse
From what I can tell it seems you have an error related to python make sure you have the correct version of python installed for building (Version 2.6.x-2.7.x). If that doesn't work I would suggest reinstalling python and see if they fixes the error. You can also ask about your build error here http://forum.xda-developers.com/showthread.php?t=2059939.
Sent from my SCH-I535 using xda premium
Odp: Stuck on building CM10 for jlo - need tip
Okay I'll reinstall python and write here if it works
now this error:
Code:
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
Device jlo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_sony_jlo
Default revision: cm-10.1
Checking branch info
Default revision cm-10.1 not found in android_device_sony_jlo. Bailing.
Branches found:
jellybean
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
** Don't have a product spec for: 'cm_jlo'
** Do you have the right repo manifest?
Use jellybean as your branch.
Sent from my SCH-R950 using Tapatalk 2
How to do this? can you explain? I don't know what you mean exacly.
can you give me proper command?
lozohcum said:
How to do this? can you explain? I don't know what you mean exacly.
can you give me proper command?
Click to expand...
Click to collapse
for cm10 repo init -u git://github.com/CyanogenMod/android.git -b jellybean
you had cm10.1 in the error which is still a work in progress
ah I understand, I have downloaded CM10.1 against CM10, so if I download CM10 will it work?
lozohcum said:
ah I understand, I have downloaded CM10.1 against CM10, so if I download CM10 will it work?
Click to expand...
Click to collapse
Yes this should solve your compile error allowing the build to compile successfully unless it runs into another unexpected build error.
Hey guys, I have device tree from dianlujitao, hardware from codeaurora, Vendor and kernel source from official huawei, and try to compile cm11 for my device(HUAWEI honor 4X), but when making hardware/qcom/audio-caf/hal/audio_extn/ssr.c, I got this error message: no such header file "surround_filters_interface.h".
I search all of sync of source, google, github. still cant find header file "surround_filters_interface.h".
if guys can help, i would be grateful.
Code:
target arm C: audio.primary.msm8916 <= hardware/qcom/audio-caf/hal/audio_extn/ssr.c
hardware/qcom/audio-caf/hal/audio_extn/ssr.c:34:40: fatal error: surround_filters_interface.h: No such file or directory
compilation terminated.
make: *** [/android/cm11/out/target/product/c8817d/obj/SHARED_LIBRARIES/audio.primary.msm8916_intermediates/audio_extn/ssr.o] Error 1
make: leaving directory “/android/cm11”
[email protected]:/android/cm11#
You probably have AUDIO_FEATURE_ENABLED_SSR defined in your device, but audio-caf doesn't contain it. Look for and try to remove this in your BoardConfig.mk file in device tree.
mrjabol61 said:
You probably have AUDIO_FEATURE_ENABLED_SSR defined in your device, but audio-caf doesn't contain it. Look for and try to remove this in your BoardConfig.mk file in device tree.
Click to expand...
Click to collapse
It works, thank you!
Maybe I shouldn't change audio-caf.
Sometimes it's necessary to change something in repos, if you can't get it working.
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
Code:
Assembler messages:
arch/arm64/kernel/entry-fpsimd.S:53: Error: unexpected end of file in irp or irpc
/tmp/cczAQDmw.s: Error: local label `"0" (instance number 1 of a fb label)' is not defined
make[1]: *** [scripts/Makefile.build:344: arch/arm64/kernel/entry-fpsimd.o] Error 1
I got this error, I searched on Google but found nothing about it. I use Google's gcc-4.9 toolchain.
May anyone help me please?
Hi!
This is a preliminary suggestion, the ROM is not made for your phone.
CFCbazar said:
Hi!
This is a preliminary suggestion, the ROM is not made for your phone.
Click to expand...
Click to collapse
But I got this from Samsung OSS, just want to compile my device's kernel :/
Are you sure that you have the floating point configuration correct?
Code:
CONFIG_KERNEL_MODE_NEON
CONFIG_ENABLE_FP_SIMD_SETTINGS
Renate said:
Are you sure that you have the floating point configuration correct?
Code:
CONFIG_KERNEL_MODE_NEON
CONFIG_ENABLE_FP_SIMD_SETTINGS
Click to expand...
Click to collapse
I have CONFIG_KERNEL_MODE_ON as y on my defconfig but I don't have CONFIG_ENABLE_FP_SIMD_SETTINGS on my defconfig.
gorkemoji said:
But I got this from Samsung OSS, just want to compile my device's kernel :/
Click to expand...
Click to collapse
That's not a guarantee. It has happened before. Or you could try the steps from their site. Maybe you missed something.
Maybe the assembler and your FPU type don't agree.