I am working with some large open source projects and some smaller custom C code. I can successfully compile and link these using the ndk-build API even when linking against shared object files within the Android tree. I get functional shared object files and executables for the Android platform. However, it seems that when the applications are built as stand alone (meaning outside the Android source code tree using only ndk-build) the stdio functions do not operate properly. When the same code is placed under external within the Android source code tree and built with Android, the stdio functions work exactly as expected.
I have tried building with ndk r4 and r6, then we tried building with the ndk r4 from within the Android tree. (2.2.1)
the functions in question are
close() - hangs a process when the process is forked
fprintf() - nothing gets written
fopen() for write - the file does not get created as a new file
remove()
unlink()
etc.
I have not tested beyond these functions.
The question is why does the stand alone built code not function properly while the same code built within the Android tree executes properly?
Any insight would be greatly appreciated.
Thanks,
Adam
Edit your post and add a meaningfull thread title.
additional info
Seems in particular that close(0), close(1), and close(2) cause a process hang when fork() is used.
When built with Android code under the external directory, everything works as expected.
Hello I have been trying to extract the kernel from Tucana android 10 source. I would like to know if anyone has a working config to be able to build up the kernel.
I have a config but it does not extract everything, well I don't think it does and would like to know what toolchain is best for Xiaomi devices. Been using Google's AOSP toolchain from pre-builts and I can build the kernel. It becomes 16mb for Image.gz-dtb I flash it using fastboot boot Image.gz-dtb and phone boots to splash screen but does not go any further. Is it normal?
This thread has the config and information https://forum.xda-developers.com/t/my-experience-building-the-tucana-kernel.4240985/
I think this is the solution
How To Use
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
Taken from above source link.
need this in order to get the device files for the xiaomi mobile of your choice in the android revision branch of your choice.
Dont think I can use AOSP untill i use this to first get the kernel files built and then able to use the same files with AOSP.
Download Qualcomm Android Enablement Project
Acutally, this step is optional. But this project integrates many tools such as cross compiler which are required for building our kernel. Of course you can use your own tools to compile kernel, but it may be a tough work to configure.
You can download the whole QAEP on Codeaurora
Can indeed confirm that you need the project from Codeaurora instead of AOSP. it has the platform SM6150. over 100+GB download though.
Make sure when after choosing the release branch with your device and about to sync. only use a max of 3 processors. no more then 3. Codeaurora has a bandwidth limiter. so the more you have the longer it will take.
Tested the theory myself.
Downloaded first time, took 9 hours with max -jN then restricted the -jN to -j3, process for over 100GB took only an hour.
instantnoodle-tools-cli-mainHey all!
I've started this project to allow people to use their devices longer, right now with a focus on the OnePlus 8, but eventually spreading to more devices. These scripts are currently for Linux Ubuntu/Debian distros only, but I plan on expanding support to other systems as well. Below is a link to all the files you will need to start using the scripts for beta testing on Linux machines. The only three ROMs available at the moment are Lineage OS 18.1 (with or without Google), ShapeShift OS v2.6, and Pixel Experience, but, again, more ROMs will be supported. I also plan to include troubleshooting support for frequent issues that can be fixed.
GitHub - kyg203/Android-Tools-CLI-
Contribute to kyg203/Android-Tools-CLI- development by creating an account on GitHub.
github.com
setup.sh - this script installs all of the tools and software for the next scripts to use for flashing. Please initiate this script first time and every week or so to keep tools up-to-date and fresh.
autotools.sh - This is the main script you will be executing. The rest will be executed from here. Do not execute any others manually to ensure you don't break anything.
rom-installer.sh - ROM chooser script. downloads the ROM of your choice and extracts the fastboot images from the payload.bin file. Do not execute from here.
In each ROM folder, there will be an info "readme" file. These files basically serve as a directory listing, allowing you to find the project page on XDA/GitHub/Website, look at any known bugs before you flash, and see any special install instructions. Please check these files regularly!
I will be focusing on perfecting the process on the command line on Ubuntu and Debian based distros first before I begin supporting more distros and operating systems. feel free to leave comments about the project below and begin porting your device into the project!
<---------- WARNING ---------->
// THIS IS STRICTLY IN ALPHA TESTING
// USE AT YOUR OWN RISK AND ALWAYS BACKUP YOUR DATA
<---------- WARNING ---------->
<---------- REQUIREMENTS ---------->
YOUR DEVICE MUST BE BOOTLOADER UNLOCKED
PUT THIS FOLDER IN ROOT (~) aka Home
PATIENCE - This project is still in the process of setting up and may produce errors. Feel free to contact me or anyone on XDA to help you with any issues or answer your questions.
BACKUP YOUR DATA - Backup all of your data even before you unlock your bootlaoder, because as soon as it is unlocked the device is wiped. Be prepared and you have been warned.
<-------------- RECOMMENDATIONS ------------>
I highly recommend you root your phone and leave Lineage Recovery or Pixel Experience Recovery on the device. This generally makes troubleshooting faster and easier. Plus, it allows you to backup your persist.img in the chances it does get corrupted. I will be adding a tool to backup and restore this image for you.
If enough support comes through, I will make a Telegram and Discord for this project specifically for support.
This is a really exciting concept and thank you very much for your efforts thus far.
UPDATE [2020-06-03]
- Added a new folder hierarchy to organize the mess a bit
- The entire project does not create anymore folders inside or outside of the branch
- Trying to leave a small footprint, so deletes all .img's, .bin's, and any other files immediately after usage.
- Updated README (and above)
- Brought support for ShapeShift OS (v2.6 Sceptile)
- Trying out an info file in each ROM folder to highlight features, issues, support, and information. Still working on gathering more information.
Hope everyone is doing well! If anyone has tried it out yet, even an older version, did it work for you and how was the overall process?
Can this be already used or not yet ?
dan20063 said:
Can this be already used or not yet ?
Click to expand...
Click to collapse
Yep! Only works on Ubuntu based systems.
Download the folder, execute setup.sh (as sudo) and then execute autotools.sh (as sudo).
You're "average Linux user" (ik basically a meme at this point) will have no issue installing a ROM manually instead, and would most likely prefer the control and ease of mind of the manual way. Especially because they still need to download and get an understanding of ADB/Fastboot and its commands since that's necessary for unlocking the bootloader.
With that being said I'm glad you made this, looking forward to further development, and I'm downloading now to test and for S&G.
Yeah, that's true. I just wanted to get it going and working on Linux where I'm a bit more comfortable and then switch it to Windows once I have a Windows device. I definitely added a bootloader unlock, but that obviously only works for unlocked devices
Nice work!
Thanks for your time, effort and sharing.
Just updated the autotools project!
What's new?
-- Updated all the available custom ROMs and custom recoveries
-- Shorted a couple of scripts to reduce folder size
-- New backup_persist.sh script - self explanatory. Everytime you run this script, it erases the previous backup, so be careful about executing this one!
-- New restore_persist.sh script - self explanatory - Uses the last made backup of your persist.img!
If you want multiple backups of the persist, maybe for different versions of Android, you will need to go in and rename those files separately. To do this from the terminal, just type "mv persist.img new-name-of-file-here.img" or you can rename the file from your local file manager.
Just a reminder: this project is open source! Please port it to support your own device! I'll be finishing up the OnePlus 8 by this weekend and then working towards my Pixel 6 when it comes in by Christmas.
Hello guys!
I started a new project with adb+python a few days ago.
You can find my tool here:
https://github.com/Frxhb/python_adb
Small Description:
This program, which is still in development, uses adb tools + some python commands to modify your device. Right now it only works on Linux.
It uses python3 + pure-python-adb and adb-platform-tools.
Right now you can:
Install/uninstall apk
Reboot your phone
normal
into bootloader
into recovery
List installed packages
Start ADB-shell
Feedback:
If you guys want, you can test this program out and give me feedback. Sure I will add more and more function soon to this program. I already tested it on linux-mint and raspbian os with:
Xiaomi Mi 10 T Lite
Samsung Galaxy S7
Gigaset GS370 Plus
Goals:
My goal in the future is to implement this program into a graphical user interface (GUI) to have a better user experience.
How to run:
Just read the README.md and do the steps to run this program ( https://github.com/Frxhb/python_adb/blob/master/README.md )
As I mentioned in README, this tool is just available right now for LINUX users.
Please give me feedback if you have tested it. Thanks in advance.
Frxhb
placeholer #1
placeholder #2
placeholder #3
Hi @Frxhb. Nice project!
How the hell did you make that ASCII art?
Keep up the great work!
1. Requirement
Code:
1. Windows 10 version 20H2 update.
2. Internet.
3. Google search ability.
3. Patient.!!
2. Credit
Send me a coffe:
0x10Bcc550e1Ac7E7c68D867ef7379C51847300eE3
3. Main step
1. Setup Ubuntu
2. Configure Environment
3. Install ccache (optional)
4. Clone ROM COMPILER source
5. Clone your device source
6.Configure before build
7.Compile rom
8.Fix error occur (optional)
4. Many thank to:
Please read it
Updating picture guide
Popular error:
How_to_build_ROM/Error at 11.0 · LeCmnGend/How_to_build_ROM
These steps for noob to build a ROM. Contribute to LeCmnGend/How_to_build_ROM development by creating an account on GitHub.
github.com
22.01.26:
Update Some error occur:
3 SOURCE: device + kernel + vendor is a must, believe me, noob cannot created i, we should to make first rom.zip
How_to_build_ROM/Error at 11.0 · LeCmnGend/How_to_build_ROM
These steps for noob to build a ROM. Contribute to LeCmnGend/How_to_build_ROM development by creating an account on GitHub.
github.com
Some error can occur during build.
Please share your error here to another
Requirement for guide:
4. Patience
also OP
swears in first line of guide
LOL
AsadP2013 said:
Requirement for guide:
4. Patience
also OP
swears in first line of guide
LOL
Click to expand...
Click to collapse
Sometimes patience doesnt work
Thank you for this. I am seeing all these cool ROMs coming out for OnePlus 9 Pro and want to try them on OnePlus 9. Wasn't sure how to go about it. I only ever built using kitchen tools many years ago and one time I built an Ubuntu Touch port for Samsung Captivate but I haven't done any of this stuff in quite some time.
EDIT: Nevermind