Related
Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.
Count me in. I am getting a Tab tonight and I plan to develop for it. Currently, I have got the froyo source on my machine and want to integrate the open source code that Samsung released for this device.
Has anyone successfully built a custom ROM using the Samsung source code? Any help on this will be appreciated.
Awesome!
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
I've put a small amount of stuff into the Dev Environment, most just shell files etc to make installing everything easier. One click sort of thing.
My first task though is going to be to try and fix the failure that is the Samsung display driver. Most noticeable are the 4 by 1 widgets that don't stretch across the whole screen.
After that I'm going to start work on a GUI for the environment and the iOS Emulator.
thoughts?
Whats wrong with Android SDK and Eclipse?
It's not the most straight forward thing. I'm looking to make something that includes its own libraries too. It's aimed at beginning developers mostly, so you can literally download one file which includes everything you'll need then start editting and then one click to compile and have it all work. Simplicity
I'm also interested in this... The SGT is my first android device, and my company will want android apps for internal and external uses... and a one click dev environment would be a most welcome option!
DevShroom said:
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
Click to expand...
Click to collapse
Straight up AOSP? Could you have a crack at CM?
Anything you need, including testers, I'm in.
I have programmed some programs in android. If you need my help, i will be glad to help,
Sent from my GT-P1000 using Tapatalk
i'm currently setting up a new galaxy Tab ubuntu 10.10 VM but I always fail at installing java5-jdk, but when im ready i'm going to have a look at the CM and AOSP source and i !try! to port CM to the tab!
I am working on a custom rom , if you need any help do not hesitate
yann06 said:
I am working on a custom rom , if you need any help do not hesitate
Click to expand...
Click to collapse
are u building from source or are you modifing a stock rom?
DevShroom said:
Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.
Click to expand...
Click to collapse
I'll be interested in getting involved in a community driven project for the SGT. I'm a unix admin with lots of experience in the OS and system development field. Interested in what ideas you have on this.
Try using openjdk. It works for me.
Sent from my GT-P1000 using Tapatalk
Thanks everyone for the positive feedback on all this! it'll be good to have as many people on board as possible.
if you have troubles downloading the sun-java5-jdk there is a good tutorial on it on this site, it doesnt come as part of the repository by default so until you add it in sudo apt-get install sun-java5-jdk will not work.
atm i am only working with AOSP not CM, i am trying to set this dev environment up for a nice simple build and then i'll start working on more complex builds so we can start developing custom roms.
@paulshields - do you know much about linux/android drivers? i wanna fix the widget sizing problem on SGT but my driver knowledge is limited
I understand there are some builds available on github ( https://github.com/omnirom/android_device_oppo_n1 ). Please could anyone guide on how to build it so we can test it on our devices. Thanks.
That would be a pretty in-depth guide.
Omnirom has their own wiki page that can teach you how to compile and port to your device.
http://docs.omnirom.org/Main_Page
:good:
Thank you Harfainx for sharing the guide, I'll try following it and post my finding(s) for everyone.
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
nospam said:
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
Click to expand...
Click to collapse
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Harfainx said:
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Entropy512 said:
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Click to expand...
Click to collapse
Glad to hear an official response. Thanks for the update. :highfive:
viperdream26 said:
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
Click to expand...
Click to collapse
Maintaining a thread is more work then you would ever think
At the moment I am more then full doing that at oppoforums
I'm going to take a crack at compiling the Cyanogen Source code to take a peek at the o-click issues.
I'm fairly knowledgeable in C, but haven't done any android/bluetooth coding before, so I think I have a snowball's chance in hell.
But it'll be an interesting exercise anyway.
So I'm following random links in:
http://wiki.cyanogenmod.org/w/Development
Mainly using this:
https://skydrive.live.com/view.aspx?cid=B3BFF0D42AE1E534&resid=B3BFF0D42AE1E534!107&app=OneNote
To set up virtualBox/Ubuntu/android SDK.
Although I am a bit confused about required JDK versions.
Is there a list of prefered JDK versions for different CM versions?
I also just noticed the page for the Find 5: aka
http://wiki.cyanogenmod.org/w/Build_for_find5
So I guess I'll use that as the instructions until the actual source code pull?
- Frank
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Entropy512 said:
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Click to expand...
Click to collapse
This is based on the Google BLE sample. It allows pairing with the o-click and will recognise single and double clicks on the remote
Sent from my N1 using Tapatalk
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
ChodTheWacko said:
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
Click to expand...
Click to collapse
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
add_lunch_combo cm_n1-user
add_lunch_combo cm_n1-userdebug
add_lunch_combo cm_n1-eng
Click to expand...
Click to collapse
Could you just be using the wrong vendorsetup script or should that one run first? Like I said, I'm still very new to this but wanted to at least point this out.
mybrotherischad said:
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
Click to expand...
Click to collapse
You're right, the n1 directory's vendor explicitly lists them.
I was looking at the wrong one I guess. Or it's not being used for some reason.
My Brunch n1 is also complaining with:
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
which doesn't look right, but I'm taking stuff one step at a time.
- Frank
Hi! Because of lack of time I was unable to continue my development of LineageOS/Android Wear 2.0 for Moto 360. I created this thread to find someone who can help fix SGX drivers (probably lack of some code in Android 8.0(, because Android does not start because of them. I'm publishing all repos and sources I've already created.
Firstly we need to focus on booting LineageOS, because It is the easiest way to boot Android 7 on Moto 360. Google didn't publish sources for Android Wear 2.0, so we will need to port it using image from other watch and our Android 7.1 drivers.
https://github.com/artas182x/android_device_motorola_minnow (branch cm-14.1)
https://github.com/artas182x/kernel-omap/tree/android-7.1-wear (branch android-7.1-wear)
https://github.com/artas182x/vendor_motorola_minnow (branch master)
Logcat with SGX error: https://pastebin.com/WKDhjEzX
If you have a problem with SGX Driver you can take inspire from this project: Unlegacy-Android. They took an Omap4 Device (Samsung Galaxy Nexus) and try to import all the necessary source from omapzoom repository to build a fully functional android 7.1.
retsef said:
If you have a problem with SGX Driver you can take inspire from this project: Unlegacy-Android. They took an Omap4 Device (Samsung Galaxy Nexus) and try to import all the necessary source from omapzoom repository to build a fully functional android 7.1.
Click to expand...
Click to collapse
Moto 360 user newer SGX driver and newer kernel than Galaxy Nexus.
Wysłane z iPhone za pomocą Tapatalk
I Hope this project Will continue, because i want wear 2.0 in my moto 360!!
I am very helpful with troubleshooting builds that boot.
I've worked on GS6 for sprint.
I've done a TON of testing for moto e 2015.
I currently have GS7 and moto 360 1st gen.
Please let me know how I can help get lineage/wear 2.0 going.
I will help as much as I can and willing to donate monetarily.
Good to see people working on this. Just got my moto 360 and was bummed to see the lack of development for it.
Let's make this happen! Going to Google your issue and see of it has dropped up before.
Thanks for all the time you've spent already dev!
I also just made my interface cable. Not tested yet. Will tonight.
I also sent a pm to a Dev who has ported wear 2.0 to the LG g watch. Hopefully I hear back and he can help us out!
Edit:
I got a response from another Dev. He had ported AW 2.0 for the LG G Watch.
Mentioned it might be easier to use another os and swap out libs and other files. I will copy text and post his full reply next.
His response:
"Unfortunately, I have no experience of working with OMAP devices.
Anyway, why are you building lineage? I think, using system image of another device as a base and patching it with device-specific configs and libs would be easier"
Thoughts on this @artas182x ?
crazynapkinman said:
His response:
"Unfortunately, I have no experience of working with OMAP devices.
Anyway, why are you building lineage? I think, using system image of another device as a base and patching it with device-specific configs and libs would be easier"
Thoughts on this @artas182x ?
Click to expand...
Click to collapse
Hmm Moto 360 is only one smartwatch based on OMAP3. What's more it's has newer kernel and SGX drivers than Galaxy Nexus and other OMAP Android devices. I don't know how to fix SGX problem. Probably it's the last problem we need to solve. Everything else should work.
Unfortunately, we don't have open-source SGX drivers for Moto 360. There are some on the internet but in earlier version than we need. So we need to find how to run prebuilt drivers.
All my sources are on my GitHub, you should be able to build Lineage OS from that files.
What do you mean by "prebuilt drivers"? The drivers already on device?
And we would need to make everything work with those existing drivers rather than getting new drivers that work with everything else?
@artas182x could you point me in the direction for the sgx drivers online? Are they Intel drivers? Or....?
Sorry for all questions. Trying to research and see what I can do or find someone to help us.
I did just find this one:
https://github.com/nemomobile/ti-omap3-sgx
What about this one?
https://01.org/intel-softwareguard-extensions/downloads/intel-sgx-linux-2.0-release
Hey to both of you. I have had a moto 360 for a while and am more than willing to help. Do we wanna maybe setup a telegram chat or something similar. For easy communication.
dylanneve1 said:
Hey to both of you. I have had a moto 360 for a while and am more than willing to help. Do we wanna maybe setup a telegram chat or something similar. For easy communication.
Click to expand...
Click to collapse
Sure. I have never used it. But ok
Im rly glade to see that some ppl are trying to bring Wear 2.0 on the Moto 360 Gen1, i would like to help but i can´t program ^^
So i just can say thanks
Great to see some news
I am willing to help if you need any testers etc.
Keep it up guyz!
Spoke with Motorola today.
I took a picture of the convo. No luck...
Does anybody know if there is some android based device compatible with our hardware? If it's popular in community we could help devs with development and maybe be able to get working driver...
Deleted
Here's the wiki.
I have a nook color! But is that too old?
What about droid?
https://t.me/joinchat/FPu8TkfPJE8URYWg9x7HxA
Here's a group link
crazynapkinman said:
Here's the wiki.
I have a nook color! But is that too old?
What about droid?
Click to expand...
Click to collapse
Seems like Moto Droid 4 has OMAP as well and working 7.1. But idk if that OMAP is compatible.
https://forum.xda-developers.com/droid-4/development/rom-cm14-1-nougat-t3499338
viktorkovarik said:
Seems like Moto Droid 4 has OMAP as well and working 7.1. But idk if that OMAP is compatible.
https://forum.xda-developers.com/droid-4/development/rom-cm14-1-nougat-t3499338
Click to expand...
Click to collapse
It's omap4 not sure
PostMarketOS on the Xiaomi Mi A2 Lite
KEEP IN MIND THIS PROJECT IS VERY WIP AND I'M LOOKING FOR HELPERS TO GET A WORKING OS. THIS IS IN NO WAY SHAPE OR FORM A FUNCTIONAL ROM AS OF NOW.
I'm trying to make progress on running postmarketos, a linux distro for various devices including android phones, on the Mi A2 Lite.
I have gotten a lot of stuff to work such as: ssh, screen, Weston, usb, and more stuff. The repo is not updated yet, but will be updated soon.
My progress is logged on this Github repo: https://github.com/matthew-5pl/pmos-xiaomi-daisy
If you feel like helping, write a comment here! There are instructions on how you can help on the github readme.
The requirements are:
A linux machine with the necessary tools installed (pmbootstrap etc.)
A Xiaomi Mi A2 Lite (i have the 4GB ram model, so if you have the 3GB one your mileage may vary) with an unlocked bootloader and access to fastboot and twrp
20-30 Minutes to compile the kernel
The current focus is getting the touchscreen to work.
If you get any further than I did, make sure to make a pull request on the Github repo!
Thanks for reading and good luck :fingers-crossed:!
Interesting project
interesting
i will look at this project, when i take a time
Update:
Weston works!
Matt 123456789 said:
Update:
Weston works!
Click to expand...
Click to collapse
Congrats! Though I think this project is somehow approached backwards. As I've seen on the wiki page all devices can have a screen but only one does the basic functionality of a phone, calls, wifi, gps, camera, sound and such and it's probably the device for which the OS was developed. Honestly I would've been more enthusiastic about this project if it only worked in terminal but had all those functions working. GUI is the easy part these days (that's not a comment on your work).
celrau said:
Congrats! Though I think this project is somehow approached backwards. As I've seen on the wiki page all devices can have a screen but only one does the basic functionality of a phone, calls, wifi, gps, camera, sound and such and it's probably the device for which the OS was developed. Honestly I would've been more enthusiastic about this project if it only worked in terminal but had all those functions working. GUI is the easy part these days (that's not a comment on your work).
Click to expand...
Click to collapse
This is my first experience dealing with compiling kernels, patching drivers etc. so I'm pretty happy I got the framebuffer to work at all. To each his own though!
Matt 123456789 said:
This is my first experience dealing with compiling kernels, patching drivers etc. so I'm pretty happy I got the framebuffer to work at all. To each his own though!
Click to expand...
Click to collapse
Which is commendable, that's why I said "that's not a comment on your work". I was referring to PostmarketOS project in general.
celrau said:
Which is commendable, that's why I said "that's not a comment on your work". I was referring to PostmarketOS project in general.
Click to expand...
Click to collapse
Oh ok!
Ho Postmarketos is interesting project ))
I will compile and test for curiosity
Matt 123456789 said:
PostMarketOS on the Xiaomi Mi A2 Lite
KEEP IN MIND THIS PROJECT IS VERY WIP AND I'M LOOKING FOR HELPERS TO GET A WORKING OS. THIS IS IN NO WAY SHAPE OR FORM A FUNCTIONAL ROM AS OF NOW.
I'm trying to make progress on running postmarketos, a linux distro for various devices including android phones, on the Mi A2 Lite.
While I have gotten two different kernels to compile, (daisy-q by xiaomi and kernel_loki by Aarqw12) and the device to boot both, I have not been able to get to a desktop environment to load.
My progress is logged on this Github repo: https://github.com/matthew-5pl/pmos-xiaomi-daisy
If you feel like helping, write a comment here! There are instructions on how you can help on the github readme.
The requirements are:
A linux machine with the necessary tools installed (pmbootstrap etc.)
A Xiaomi Mi A2 Lite (i have the 4GB ram model, so if you have the 3GB one your mileage may vary) with an unlocked bootloader and access to fastboot and twrp
20-30 Minutes to compile the kernel
The current focus is getting the display/framebuffer to work, to be able to load a desktop or mobile environment, as well as getting functional ssh and telnet connections.
If you get any further than I did, make sure to make a pull request on the Github repo!
Thanks for reading and good luck :fingers-crossed:!
Click to expand...
Click to collapse
Update: Ssh working. Looking for help with patching the touchscreen drivers.
Hi , I can pm you in xda or discuss in telegram app ?
Matt 123456789 said:
Update: Ssh working. Looking for help with patching the touchscreen drivers.
Click to expand...
Click to collapse
ada12 said:
Hi , I can pm you in xda or discuss in telegram app ?
Click to expand...
Click to collapse
Sure, add me on telegram: matthew5pl
Closing thread as a better port of PMOS has been made for daisy.
Following this thread, I recently built e/OS 0.22q for Motorola One xt1941-4 (deen). Please refer to https://e.foundation/e-os/ to learn more about e/OS.
After several weeks of usage this ROM seems to be very useful. Find the zip file with the images of the Andoid 10 version here. Unzip and flash using adb and fastboot. Please use at your own risk!
I used the following repos in my local manifest:
https://github.com/electimon/device_motorola_deen, branch Lineage-17.1
https://github.com/electimon/vendor_motorola_deen, branch Lineage-17.1
https://github.com/100Daisy/android_kernel_motorola_deen, branch android-10-release-qpks30.54-22-13
In addition, I included
https://github.com/LineageOS/android_system_qcom, branch Lineage-17.1
which is obviously needed by some stuff from vendor. Vendor files are from 2019, so if someone could provide a more recent repo, I would be glad to know (last stock rom provided by Motorola is from October 2021)
All credits go to the creators of the LineageOS 17.1 port (link to thread at the top of this post)! Very good job guys!
Works just fine, thanks.
LSV12 said:
Works just fine, thanks.
Click to expand...
Click to collapse
Thanks!
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
01nick07 said:
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
Click to expand...
Click to collapse
I'm sorry, but I have no time and I am not good at making tutorials at all. Please refer to the thread referenced at the beginning of the initial post. There you should find all necessary information. If this is not enough, do some more searching and reading on XDA. If you still feel uncomfortable, stay with the stock rom.
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
xdadevc said:
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
Click to expand...
Click to collapse
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
HerrElling said:
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
Click to expand...
Click to collapse
I read your article and managed to follow it and compile my own e/os. I'm also not an android developer. I did some kernel work in the early days, around Android 2.0 but my path diverged and now I'm completely lost.
Let's keep in touch. If you restart your efforts, I'll be happy to contribute. Meanwhile I'll try my best to get some info from the e/os forums and (pray) the lineageos residual devs.