Does anyone know what the files from http://opensource.samsung.com/ are?
Can you build the stock rom that way? It doesn't seem like you can, i downloaded it and tried to build it following the instructions but i didn't have much luck
did anyone else try to compile it?
the readme file
Code:
1. Get android open source.
: version info - Android gingerbread 2.3.3
( Download site : http://source.android.com )
2. Overwrite files that you want to build.
[...]
3. Add the following lines at the end of build/target/board/generic/BoardConfig.mk
[...]
4. make
- ./build.sh user
First of all, you are in the wrong section. All questions should go to Q&A section.
Secondly, that site is only for Kernel Source codes I believe (Correct me if I'm wrong) and I guess, you won't get their ROM source codes.
sorry for posting in the wrong section
i'm not sure it's just the kernel, there;s also a platform archive there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the platform folder contains convincing folders
The platform folder contains a small subset of the ROM, in fact the instructions instruct you to download the official source code from source.android.com. There isn't any proprietary Samsung software (i.e.: Touchwiz).
With those files you should be able to compile a pure AOSP ROM without Google proprietary apps (Play Store, GTalk, ...).
hrk said:
The platform folder contains a small subset of the ROM, in fact the instructions instruct you to download the official source code from source.android.com. There isn't any proprietary Samsung software (i.e.: Touchwiz).
With those files you should be able to compile a pure AOSP ROM without Google proprietary apps (Play Store, GTalk, ...).
Click to expand...
Click to collapse
well i am definitely interested in compiling a pure aosp rom that will run on my samsung, i tried it multiple times by those instructions but haven't had much luck
Related
Sorry guys. I was hoping there was a backdoor that I may have missed to get this to work. After working with a couple folks there is no way to make this a user friendly install even with the corrected partition map info. As soon as you guys get unlocked I will revisit this and I will be checking back on a regular basis.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am looking at yet another Universal release. This time it's not a universal MotoBlur ROM but a possible Universal Ubuntop/Webtop+ release but I need testers. It is based on the latest Webtop release for the Photon (WT-1.2.0-180) and is successfully running on the Atrix, Electrify and Photon. We've been running Ubuntop/Webtop+ since September with minimal issues and I have received multiple requests to port. If successful, the advantage of this universal release is that any improvements and enhancements will carry over to all devices.
Prerequisites:
Unlocked
CWM Recovery (Bootstrap MAY work)
GB Blur based ROM with Webtop support (for now)
/osh be located at /dev/block/mmcblk0p13 (if osh is not located at mmcblk0p13 PM me with the correct partition location)
/osh be atleast 755.9MB
Not afraid of using terminal
Latest version of 7Zip
Ubuntop.7z - 264.3 MB (MD5- AA02B21D7A8D733621AD48B1425E95C8)
DO NOT POST RESULTS - PM ME YOUR RESULTS - IF THIS WORKS I WILL BE RELEASING TODAY
Installing:
Make a full backup including webtop (this is key so you can revert any changes)
Extract the UbunTop.7z file (this requires you have the latest version of 7zip installed)
Copy the Ubuntop folder to internal storage (again this is a must)
From CWM recovery, flash the Univ_Ubuntop_v1.0.0.zip
Reboot and launch webtop
Follow the instructions in the "READ ME!!!" file in the Ubuntop folder
(Right now I'm looking for install success and menupatch success. If you want to install applications and report on that as well that's great.)
Haven't slept in over 24hrs and just realized I need to use Aroma Installer. Gonna get some sleep, fix and reup Universal Ubuntop. For those that know what they are doing, edit the scripts to point ot the proper partition to play with it.
Sorry guys. I was hoping there was a backdoor that I may have missed to get this to work. After working with a couple folks there is no way to make this a user friendly install even with the corrected partition map info. As soon as you guys get unlocked I will revisit this and I will be checking back on a regular basis.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am looking at yet another Universal release. This time it's not a universal MotoBlur ROM but a possible Universal Ubuntop/Webtop+ release but I need testers. It is based on the latest Webtop release for the Photon (WT-1.2.0-180) and is successfully running on the Atrix, Electrify and Photon. We've been running Ubuntop/Webtop+ since September with minimal issues and I have received multiple requests to port. If successful, the advantage of this universal release is that any improvements and enhancements will carry over to all devices.
Prerequisites:
Unlocked
CWM Recovery (Bootstrap MAY work)
GB Blur based ROM with Webtop support (for now)
/osh be located at /dev/block/mmcblk0p13 (if osh is not located at mmcblk0p13 PM me with the correct partition location)
/osh be atleast 755.9MB
Not afraid of using terminal
Latest version of 7Zip
Ubuntop.7z - 264.3 MB (MD5- AA02B21D7A8D733621AD48B1425E95C8)
DO NOT POST RESULTS - PM ME YOUR RESULTS - IF THIS WORKS I WILL BE RELEASING TODAY
Installing:
Make a full backup including webtop (this is key so you can revert any changes)
Extract the UbunTop.7z file (this requires you have the latest version of 7zip installed)
Copy the Ubuntop folder to internal storage (again this is a must)
From CWM recovery, flash the Univ_Ubuntop_v1.0.0.zip
Reboot and launch webtop
Follow the instructions in the "READ ME!!!" file in the Ubuntop folder
(Right now I'm looking for install success and menupatch success. If you want to install applications and report on that as well that's great.)
Haven't slept in over 24hrs and just realized I need to use Aroma Installer. Gonna get some sleep, fix and reup Universal Ubuntop. For those that know what they are doing, edit the scripts to point ot the proper partition to play with it.
After a whole lot of long evenings, odd hacking sessions and other fun things, I'm proud to present a full-system emulator for pebble.
This differs from existing solutions by actually emulating the pebble firmware using QEMU rather than simulating system calls!
It's still very much work in progess, but it currently boots a slightly modified firmware and allows navigating around the menus.
The long-term goal is to get it to a state where installing apps using libpebble is possible and hence allow using it for development.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Limitations:
Needs a full dump of the internal flash to boot (Working to allow it to boot a tintin_fw.bin directly)
Requires a modified firmware (BT initialization disabled)
Requires an SPI flash dump to be usable (Needs modified firmware to dump!)
There's currently no way to install apps
It has only been tested with firmware version 2.0.0
Sources:
https://github.com/pebbledev/qemu_pebble
DumpPebble: https://github.com/Hexxeh/DumpPebble
Dump Pebble SPI Flash: https://github.com/EnJens/DumpPebbleSPIFlash
Required patches:
On a full internal flash dump of Firmware 2.0.0 (ev2_4 - e.g. original kickstarter watch!), the following patch needs to be applied to get it running in the emulator:
patch 0x0803d910 1BE0 (Inside a full dump, the offset will be -0x8000000, e.g. offset 0x3d910)
Reserved2
Does this compile and run under android? I could see this being useful on watch devices like the Omate TrueSmart
fg said:
Does this compile and run under android? I could see this being useful on watch devices like the Omate TrueSmart
Click to expand...
Click to collapse
I doubt the CPU in the Omate is sufficiently powerful to do this right now. (I say right now, because it might theoretically be possible to optimize emulation since the cpu could directly execute most instructions...Similar to x86 on x86 emulation).
But no, this doesn't compile and run under android. It's intended for development of apps, rather than daily usage.
How do you run this under Windows? I can't seem to find a .bat or .exe file. Or does this only run with Linux?
Hello everyone,
imgui/examples/example_android_opengl3 at master · ocornut/imgui
Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies - imgui/examples/example_android_opengl3 at master · ocornut/imgui
github.com
My project is based on this C++ project in Android Studio (ImGui). I had successfully compiled and run the project using the older Android Studio version 2021.3.1.17. However, upon upgrading to Android 2022.2.1 Patch 1, I encountered numerous errors, some of which remained unresolved even after several attempts at restarting, reinstalling, cleaning, and rebuilding the project.
Additionally, I have question: When I press the Run ► button, the app on the emulator does not start. According to the logs, the app, was successfully installed. However, when I touch its icon (ImGuiExample), I get the message "App isn't installed". Can anyone suggest a solution to this problem?
I have a difficult question that I hope someone can help me with: Is there a lightweight version of Android Studio that I can use to build my project without having to download so many SDK files? I believe a lightweight software with fewer SDK files will make it easier for developers to fix bugs, the Android Studio I use has so many SDK files.
Thank you in advance for your help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not entirely certain, but I believe that the project was working fine with the old Android Studio 2021, likely because Imgui 1.89 worked but this is Imgui 1.89.6 (a newer), and I uninstalled the old Android Studio.
The solution for me is to downgrade to android-studio-2021.3.1.17. If the breakpoints don't work too for ndkVersion "25.1.8937393" for example then downgrade to ndkVersion "21.4.7075529". The key is then to switch between versions, and you can stick on one version without changing to another version for a long time.
But why, Android Studio has so many versions, I mean a lot? And it's difficult to find the perfect version.
I use the virtual machine in ubuntu and follow the tutorial on the offical sony website want to flash AOSP android 13 into my 1ii(XQ-AT52) but I stuck at the final step(flash .img into phone) ,becauce there're no .img file in the "product" folder as said in the tutorial.How to solve this problem?
link of tutorial:https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/build-aosp-android-13
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In step 5 it says "Build AOSP images that can be flashed", did you ever build one?
Tadashi_Sakura said:
In step 5 it says "Build AOSP images that can be flashed", did you ever build one?
Click to expand...
Click to collapse
What will terminal say after finshed buuild?
My terminal will be normal at the beginning,but after about 15~20 minutes it will stuck(it seems like virtual machine have not enough ram)after another 30 minutes terminal close! but the the number of files in the folder has increased.I'm not sure build is success or not...
Since you can't find any .img file I strongly suspect that the building process is not done yet. And I quite doubt that it is not the ram but the lack of free space of your virtual machine that interrupts the process.
No less than 50GB free space is suggested for building process.
By the way, why not try los 20.0(which is an A13 version of lineagOS)? It seems like clfbbn didnt release it on XDA but you can easily find it on the website.
Here is the download URL:
LineageOS Downloads
download.lineageos.org
And you can find the tutorial here:
Install LineageOS on pdx203 | LineageOS Wiki
wiki.lineageos.org
Tadashi_Sakura said:
Since you can't find any .img file I strongly suspect that the building process is not done yet. And I quite doubt that it is not the ram but the lack of free space of your virtual machine that interrupts the process.
No less than 50GB free space is suggested for building process.
By the way, why not try los 20.0(which is an A13 version of lineagOS)? It seems like clfbbn didnt release it on XDA but you can easily find it on the website.
Here is the download URL:
LineageOS Downloads
download.lineageos.org
And you can find the tutorial here:
Install LineageOS on pdx203 | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
but I have enough space , even available space is more than 50GB! that's why I feel so weird...
lineage may cause PotoPro failure and can't use some unique function made by sony,so lineage I think is not suitable for me~