Purposes of this guideThis guide want to be a how-to use Gerrit, allowing everyone to contribute on AOSP like projects.
Divided in 3 parts:
Now few important stuff needs to be setup before proceeding- -> Minimal setup to use Gerrit.
How to setup & submit for recurent contributes
How to submit patches one time
Here we will setup clones, outside of the build tree. See faq for commit testing.
This mean you do not need build environement to contribute
Important: for projects using Gerrit, Github pull request will never be merged! This also mean you do not need to create a Github fork for every changed projects :victory:
So firstly, I'll explain few terms that are important for you to learn before going towards a bit tricky side.
Git - To be precise, git is a code-sharing website/software that allows you to share your project resources you can 'Make Software, better, together'(That's what the tag line says )!
Now, before I go to gerrit, read this: Major Open Source Projects, like, CyanogenMod, AOKP, OmniROM etc. don't directly accept pull requests and in case you want to make a change in their source for a fix/feature or anything, you need to send them patches over gerrit which are then reviewed by the trusted members of the community and if they find it valuable enough, gets merged into the git repository!
Gerrit(Copying the definition from Wiki) - Gerrit is a free, web-based team software code review tool. Software developers in a team can review each other's modifications on their source code using a Web browser and approve or reject those changes. It integrates closely with Git, a distributed version control system.
So, now, git and gerrit are so closely related, that a patch verified over gerrit can directly be merged on git without much hassel, also please note that your gerrit and git username must be same.
Pull Requests - Pull requests are sent over Git after you fork a repository, make some changes into it and then want the owner to merge those changes into his repository, and that's how community development and Open Source works.
Patches - In simple terms, any changes you make to repos of Open Source Projects like LineageOS, OmniRom or AOKP and send them over gerrit for code review are called Patches.
You can find the Gerrit URL of the project you are working on, on the contribute webpage of the project. Example: OmniRom gerrit is https://gerrit.omnirom.org/ , LineageOS is https://review.lineageos.org/
How GERRIT works?! Now, Gerrit is deployed in place of this central repository and adds an additional concept, a store of pending changes. Everyone still fetches from the authoritative repository but instead of pushing back to it, they push to this pending changes location. A change can only be submitted into the authoritative repository and become an accepted part of the project once the change has been reviewed and approved.
I found a nice diagram explaining this over the internet that will clear your doubts(if any ) -
{
"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"
}
There is two different way to use gerrit:
With git , on your computer (useful for recurrent contribute)
Using the Gerrit WebUI (useful for punctual contribute)
Now few important stuff needs to be setup before proceeding-
Install up Git:
Debian/Ubuntu:
Code:
sudo apt-get install git
Fedora:
Code:
yum install git
ArchLinux:
Code:
pacman -S git
openSUSE:
Code:
zypper install git
Configuring git:
This step is very very important as those ID will be the one which identify you and you cannot change them later!
WARNING: You need to setup the same email as on github.com !
WARNING: email is case sensitive!
(For username I highly recommend to use the same as on your computer, but you could use any username you want)
Code:
git config --global user.email "[email protected]"
Code:
git config --global user.name "your-username"
Setting up SSH Keys(Skip this if you have already set them up) -
Code:
ssh-keygen -t rsa -C "[email protected]"
Now this will create 2 files in ~/.ssh directory as follows:
Adding SSH Keys to your Account :
Code:
cat /home/username_on_pc/.ssh/id_rsa.pub
This will show up few lines over terminal, copy those and add them into your Gerrit profile (Will not be detailed, there is a lot of guides on internet for this part)
Important: you need to setup your username into gerrit UI, otherwise you will never be able to push changes (on the screenshot there is no option to modify username as it is already setup but you should see one):
Test ssh is correctly working :
Code:
ssh -p 29418 <username>@<gerrit address>
If you see this message, then everything is setup and ready to propose changes :
If you get any errors, reread the howto to ensure you are not missing something.
You can also contact your team (there is probably an IRC channel for this) and ask for help.
Setting up the hook Change-ID :
WARNING: this need to be done in every repository or upload will fail!
Code:
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <username>@<gerrit address>:hooks/commit-msg ${gitdir}/hooks/
Making Changes and Submitting Patches -Way 1. (for recurrent contribute) :
If you have a full build environment setup, the best practice say to not use your build trees for change & submit patches. If you do not have build environment setup, just don't care about this warning
Create a folder (like ~/clones/) where your clones with your changes will reside:
Code:
mkdir ~/clones
cd ~/clones
Go to git where you would make the change and copy the Clone link:
Code:
https://github.com/omnirom/android_device_sony_shinano-common.git
Go back into your terminal and clone the repo (optional: you can specify the branch name with -b <branch name>), then get into clone folder:
Now you can make the change using your favorite text editor (<escape> then ':q<enter>' to exit vim ):
Code:
git status
It tells you what files you modified(In Red color ) and shows on which branch you're currently on.
Now, the committing part,
Run:
Code:
git add -A
Run git status again, and it'll show the files in green color, telling you that the changes have been added.
Now:
Code:
git commit -s
This will commit the changes and open up a Text Editor called NANO. Here you need to edit the commit message that appears at the side of the gerrit window to describe what the patch does.
After writing the commit message, press Ctrl+O and then Enter key to save the commit message and then Ctrl+X to exit the editor. This is the committing part done. :good:
Optional (but better ): you can control what your commit changed, then rework if necessary (see last part of the guide):
Code:
git diff HEAD^
Now submitting the patch -
You need to catch the project path from the Gerrit interface. Go into project, list, and find the repository you changed:
Here the path is android_device_sony_shinano-common. It could include a 'sub-folder' like LineageOS do. For example, same repo on Lineage will be LineageOS/android_device_sony_shinano-common.
WARNING: path is case sensitive.
Go back to your shell and type:
Code:
git push ssh://<username>@<gerrit address>:29418/<repo path> HEAD:refs/for/<branch name>
Way 2. (for punctual contribute) :
Log-in into the Gerrit instance you want to commit into. Go into 'Projects', list, then choose the repo you want to make the change in:
Hit the 'Create Change' button:
This open a popup asking for some information:
Select branch for new change: the branch you want to commit in,
Enter topic for new change: leave empty
Description: Enter commit message
Finally hit Create
Now your change page is open, you can start editing files with the Edit button on the right:
then Add the file you want change:
The file open in an editor, make the needed changes and save with Save button, then Close:
(Redo the step if you need to change multiples files.)
When all your changes are present, hit the Done Editing button to validate your changes.
Your changes are pending and you can display it while clicking on file name:
The changed section is highlighted. If you made a mistake you can use the
icon:
Use the
button to get back on the summary page.
WARNING: your change is only a draft for now, you need to publish it:
Ask for review :
Once your commit is on Gerrit you need to setup a reviewer. This person will comment, reject or submit your patch.
Hardest part is to find the reviewer. You can ask in the dedicated IRC chan of your rom, or use some tricks like check who merged the commits into the repo.
Once you find who will be the reviewer, add it on the dedicated gerrit field:
Once your commit is ok and you want the reviewer take care of it, set-it 'Code-Review +1' and add a comment (will stay on gerrit) about why this change should be merged:
Guess what?! Done!
Congratulations, you just learned gerrit and know how you use it. I hope you'll send some nice patches and respect the Open Source. :victory:
Credits -
v_superuser said:
> Original kanged thread
Click to expand...
Click to collapse
FAQ
Ensure your clone is up to date
Before picking and before writing patch you need to ensure your clone is up-to-date with the remote repository.
Go into the needed folder, then check the remote name:
Here the remote is named 'origin'.
We need to fetch the remote, on the right branch, then switch to that branch:
Code:
git fetch <remote name> <branch>
Code:
git checkout <remote name>/<branch>
(You can notice in my right prompt the current HEAD changed for remote/<remote name>/<branch name> . It is now up to date. )
Warning: Only the checkout command switch your local tree
Warning: git fetch use space between remote name & branch name but git checkout use slash (/) !
How to test pending changes
To test a change pending on Gerrit you need a working build environment for your rom. This guide will not explain how to set it up.
Once you have located the change you want to test,
go into the corresponding folder. Use the project path for hints:
here folder will be device/sony/msm8974-common.
Next use the download button into Gerrit interface
and copy paste the command in your terminal:
If you have merge conflict you will need to solve (with git mergetool, internet search and brain).
Now you can do this step again to merge other commits, or trigger the build for testing.
Update a pending change
You made a commit but notice some problem and it need to be reworked, without creating another one.
You need to follow the Ensure your clone is up to date then How to test pending changes with the commit who need reworking.
Once the commit is fetched locally you can make your changes:
Trigger the amend of the commit:
Code:
git commit [B]--amend[/B]
The git editor open and allow you to change the existing commit message:
Once your change is done, upload it:
The commit is updated (new Patch Set) on Gerrit (no new one was created):
Setup Gerrit as remote for easy reuse
Typing the push command each times could be painful if you upload patches often.
You can add Gerrit as a remote for easy reuse:
git remote add <local name> ssh://<username>@<gerrit url>:29418/<repo name>
Now you can simply use git push command:
Warning: need to be done in each repos!
Warning: This tip do not prevent typing HEAD:refs/for/<branch> each time !
reserved
This is absolutely wonderful guide , thank you for your contribution
git init
Click to expand...
Click to collapse
command should be passed before the below command! otherwise it willl show some error!
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <username>@<gerrit address>:hooks/commit-msg ${gitdir}/hooks/
Click to expand...
Click to collapse
Thanks for your guide, however, on the 3.4 or more version has a little change, can you update the article?
In addition, your article has a defective attachment (in "Adding SSH Keys to Your Account"), please fix it!
I was looking for it from so long
Thanks man
Related
DISCLAIMER
You need to have an unlocked bootloader to use this ROM & kernel. Also I or any contributor in the software DOES NOT take responsibility of damages caused to your phone due to this ROM.
{
"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"
}
1. Copy ROM zip and gapps zip to sdcard
2. Flash any kernel which has recovery (if you do not have any recovery yet)
3. Reboot device and go to recovery by pressing Vol-UP when LED is pink
4. If coming from 4.2 or 4.1 ROM wipedata/factory reset your phone
5. Flash ROM zip
6. Flash Gapps zip
7. Reboot and enjoy.
Official Nightlies (automatically built every 3 days on AOKP buildbox) :
http://aokp.co/devices/yuga
Unofficial Test Builds (will contain experimental changes for testing) :
http://aokp.co/unofficial-builds#odin
Gapps :
http://goo.im/gapps/gapps-jb-20130813-signed.zip
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.
Donate to AOKP
Donate to CyanogenMod
Every donation is cherished and loved.
If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
Latest merges on Gerrit
http://gerrit.aokp.co/#/q/sony+status:merged,n,z
Check out the ROM source on github. Open source, in the spirit of community kangage.
CREDITS
I cannot thank more for the hard work of FreeXperia Team (Jerpelea ( @FXP ), @Bin4ry, @Kali-, @Entropy512, @codeworkx and others) for working on Xperia devices.
Also huge thanks to Sony Mobile AB for having been very developer-friendly and helping us in all sorts of ways.
XDA:DevDB Information
[ROM][4.3.1] AOKP :: jb-mr2 :: nightlies | test builds :: yuga {Z}, a ROM for the Sony Xperia Z
Contributors
championswimmer, @FXP, @Bin4ry, @Kali-, @Entropy512, @cdesai, @codeworkx
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Alpha
Created 2013-09-18
Last Updated 2013-10-12
Reserved
Reserved
AWESOME!
Sent from my C6603 using xda premium
Very Very Good!
For the first build divine
With the build 2013-09-16 I found three bugs:
* Android Keyboard crashes after use the swype function
* the battery indicator updated first at 70%. Previously the indicator shows ever 100%. It's just the indicator in the status bar.
* If I start the Settings => Device Options the Settings will crashed
I will test the new build and will give you then feedback if the bugs are fix or not.
Can I make a mirror for the new build by uploaded and or or Google Drive?
Any feedback on this early version? It may make me think about unlocking my BL...
Yes, read my post!
@championswimmer:
How do you build the build?
When I type:
.build/envsetup.sh && brunch yuga
I become the follow erorr:
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/quincyatt/vendorsetup.sh
including device/samsung/toroplus/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/aokp/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/aokp/vendorsetup.sh
build/core/product_config.mk:205: *** No matches for product "aokp_yuga". Stop.
** Don't have a product spec for: 'aokp_yuga'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Can you help me?
heubergen said:
@championswimmer:
How do you build the build?
When I type:
.build/envsetup.sh && brunch yuga
I become the follow erorr:
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/quincyatt/vendorsetup.sh
including device/samsung/toroplus/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/aokp/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/aokp/vendorsetup.sh
build/core/product_config.mk:205: *** No matches for product "aokp_yuga". Stop.
** Don't have a product spec for: 'aokp_yuga'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Can you help me?
Click to expand...
Click to collapse
repo init -g all,-notdefault,yuga,sony
Thanks for the answer, but I become the same error
After 3 hours or something I destroy my aokp/.repo
When I do report sync it gives me the error
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
fatal: no revision for project AOKP/device_sony_common within /Volumes/android/aokp/.repo/manifest.xml
Can you help me, please?
heubergen said:
Thanks for the answer, but I become the same error
After 3 hours or something I destroy my aokp/.repo
When I do report sync it gives me the error
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
fatal: no revision for project AOKP/device_sony_common within /Volumes/android/aokp/.repo/manifest.xml
Can you help me, please?
Click to expand...
Click to collapse
you need to remove your local_manifest.xml file
new build up
camera fixed
I've successfully built my own version . Thanks for your work.
But my recovery seems not working right. I only get an black screen but I can adb into it and see it booted up. Any idea what could be the problem?
Update:
I found the problem. Recovery is missing "/sbin/minivold" because the AOKPs vold does not provide it.
The missing commit is here:
https://github.com/CyanogenMod/android_system_vold/commit/aa564abda8315ea523180785d0f7e9bf552f8583
@djselbeck:
Do you use for the build the command:
. build/envsetup.sh && brunch yuga?
@championswimmer:
Thanks.
heubergen said:
@djselbeck:
Do you use for the build the command:
. build/envsetup.sh && brunch yuga?
@championswimmer:
Thanks.
Click to expand...
Click to collapse
Code:
source build/envsetup.sh
brunch yuga
is my build command.
Thanks!
Have you never see the follow error or you now what are the mistake?
build/core/product_config.mk:205: *** No matches for product "aokp_yuga". Stop.
** Don't have a product spec for: 'aokp_yuga'
** Do you have the right repo manifest?
I try allways a never found a solution.
Which repo init commond do you use?
I use the repo init a few posts above.
Do you use:
repo init -u git://github.com/AOKP/platform_manifest.git -g all,-notdefault,yuga,sony
Because, by me that command gives me a error called:
...
* [new tag] jb-mr1_milestone-2 -> jb-mr1_milestone-2
error: revision refs/heads/master in manifests not found
First I did
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2
repo sync -j4
after it finished I did:
Code:
repo init -g all,-notdefault,yuga,sony
repo sync -j4
I think I start new and give then a new feedback.
{
"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"
}
Device: mako (Nexus 4)
Why AOKP?
Well, if you are looking for super fast, buttery fluid and stable ROM with bunch of truly useful features, you are in the right place. Believe me, I wouldn't recommend you laggy and choppy ROM as smoothness is everything for me. Just download latest build and turn on The Swagger, right? Let's make that roll. :highfive:
Build description:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3
TARGET_PRODUCT=aokp_mako
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.8.0-30-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JLS36G
OUT_DIR=/home/max/aokp/out
============================================
Screenshot:
» Installation is simple:
If coming from another ROM or another major AOKP version, wipe data in recovery
Make sure you're using the latest CWM or TWRP
Flash ROM
Flash Google Apps (GAPPS)
Reboot
» Check merged commits on AOKP's Gerrit
» 2013-09-26
» 2013-09-25
» 2013-09-23
» Google Apps
» AOKP Gerrit
» AOKP on Github
» SOURCE on AOKP.co
Open your wallet and donate to AOKP Crew!
» Donation options on AOKP.co
Enjoy!
NOTE
The ROM is an unofficial version of AOKP, 100% built from OFFICIAL AOKP source.
I am going to keep on with nightlies 'till AOKP Crew decides to roll out their official builds (it will last for a while)
The whole code is untouched, so you can enjoy pure AOKP (MR-2) based on Android 4.3 :highfive:
ROM is stable, fast, fluid and what's the most important - ready for daily use
USE JSS KERNELS AS THIS ROM IS NOT JWR BASED!
---
Any questions?
Catch ME on Google+ as I don't really reply to xda PMs! :silly:
Build AOKP MR-2 from source yourself!
To build any ROM from source you have to get yourself Ubuntu (12.04 currently as it's latest stable release) Personally, I use it as virtual machine via VIRTUALBOX from Oracle
If you already have Ubuntu, let's set up build environment. Open Terminal and punch some lines:
Code:
$ sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
Python-markdown libxml2-utils xsltproc zlib1g-dev: i386
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
This installed required packages to your PC
Let's grab JDK (Java Development Kit) now:
Code:
$ sudo apt-get install sun-java6-jdk
And we're ready to set up things for the build! :highfive:
Code:
$ mkdir ~/bin
Let's check now if the bin directory which our repo file will stay in exists
Code:
$ PATH=~/bin:$PATH
Now we have to download repo tool:
Code:
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
...and give it proper permissions
Code:
$ chmod a+x ~/bin/repo
Let's download source code now! Create a new directory! :cyclops:
Code:
mkdir RANDOMNAME
Navigate to it!
Code:
cd RANDOMNAME
And now it comes to the tricky part when you have to decide what will be downloaded.
If you want core trees without any device vendor or kernel:
Code:
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2
If you want ALL vendors and kernels supported by AOKP:
Code:
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2 -g all,kernel,device,vendor
If you want to build for particular device:
Code:
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2 -g all,-notdefault,<devicename>,<vendorname>
(example: if you want to build mako, type "mako" instead of <devicename> and "lge" instead of <vendorname> without "" of course )
If you want to build more than 1 device:
Code:
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2 -g all,-notdefault,<devicename1>,<devicename2>,<devicename3>,<vendorname1>,<vendorname2>,<vendorname3>
Click to expand...
Click to collapse
Ok and when repo is initialized:
Code:
$ repo sync
Personally, I use "repo sync -j4" as I gave my virtual machine 2 cores from host PC so 2 jobs are written for each core (2 cores * 2 jobs = 4 jobs generally). It really shortens sync time.
And finally when the repo is synced (it lasts a while and depends on your connection) type:
Code:
$ . build/envsetup.sh && brunch mako
And hopefully you will end up with a flashable zip in ~/RANDOMNAME/out/target/product/mako as well as /system/ dump and some flashable images
Build time depends on your machine efficiency (on my virtual machine (2 cores, 4 GB RAM) it takes about 1,5-2 hours so be patient)
downloading now, thankyou,,steve
mongonexus said:
downloading now, thankyou,,steve
Click to expand...
Click to collapse
Thats cool ?
Give feedback after playing around ?
== Sent from my Carbon Mako ? ==
Good work,
Sorry to ask but does this suffer from deadlocks?
Sent from my Nexus 4 using Tapatalk 4
ben_pyett said:
Good work,
Sorry to ask but does this suffer from deadlocks?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Teoretically it does as it is JLS based
But in fact it happens really really rarely so no worries
== Sent from my Carbon Mako ? ==
Thanks, are you rocking this or Carbon? as that's what your Sig still says? trying not to be a smart arse, just pointing it out
Sent from my Nexus 4 using Tapatalk 4
ben_pyett said:
Thanks, are you rocking this or Carbon? as that's what your Sig still says? trying not to be a smart arse, just pointing it out
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Haha
Forgot to change it in xda app settings
Already done ?
== Sent from my Kanged Mako ? ==
I'm downloading. I'm AOKP starved. Hope this suits me. Someone showing AOKP love.
Sent from my Nexus 4 using xda app-developers app
Added compile guide to OP
== Sent from my Kanged Mako ? ==
That's pretty cool. Thanks. Would you know how to go about "cherry picking" (as they call it) features and such that's not merged yet?
Sent from my Nexus 4 using xda app-developers app
PJcastaldo said:
That's pretty cool. Thanks. Would you know how to go about "cherry picking" (as they call it) features and such that's not merged yet?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You say, you get it
Code:
git remote add upstream https://github.com/xxx/yyy.git
git fetch upstream
git cherry-pick <commit number>
== Sent from my Kanged Mako ? ==
maxio1998 said:
You say, you get it
Code:
git remote add upstream https://github.com/xxx/yyy.git
git fetch upstream
git cherry-pick <commit number>
== Sent from my Kanged Mako ? ==
Click to expand...
Click to collapse
Thanks for this, are you the guy who used to cook roms for xperia 2011 phones?
Rom installed this night... Seems good ! Really smooth
Let's see for the battery consumption now ^^
TheDarkDefender said:
Thanks for this, are you the guy who used to cook roms for xperia 2011 phones?
Click to expand...
Click to collapse
Exactly
== Sent from my Kanged Mako ? ==
Does this ROM have the freezing issues like all the other AOSP roms?
Edit nevermind!!! No-longer in the Mood To FLAME!
nerotix said:
Does this ROM have the freezing issues like all the other AOSP roms?
Click to expand...
Click to collapse
Its been a while, going through a couple of JSS based roms since i experienced a deadlock, although, i think i didnt suffer from em quite as much as pepole reported on forums...so take it with a grain of salt, experience varies between handsets...
nerotix said:
Does this ROM have the freezing issues like all the other AOSP roms?
Click to expand...
Click to collapse
Max says
http://forum.xda-developers.com/showpost.php?p=45860850&postcount=7
Please remove as this now resolved.
I know that this source is not Lineage but I would think the basic principles for building for an supported device under Lineage would also be applicable to any other source repository.
All of the guides I have found only tell you how to build for a supported device and not any help for an unsupported one. I figured out how to sync a suitable device tree and kernel etc but since the rom source repository does not support my device I can't go any further. I can't get it to build from my sync'd local sources it keeps trying to pull stuff from the original source repository so builds fail at the start.
I have setup a local manifest for this project that sync's the device tree and a kernel and the proprietary blobs and this sync completes without error. next I ran - source build/envsetup.sh and then brunch hlte (not a supported device I know) but that throws up this error -
build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.
Device hlte not found. Attempting to retrieve device repository from GZOSP-Devices Github (http://github.com/GZOSP-Devices).
Repository for hlte not found in the GZOSP-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/gzosp_manifest.xml
build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.
So I think that the error basically means that github.com/GZOSP-Devices does not have the hlte device listed so can anyone tell me how to make the build point to my local repository after I have sync'd so that it at least starts to build ?
I am a newbie to rom building and have much to learn but I would really appreciate any help you guys could give.
Thanks in advance for any an all help offered.
{
"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"
}
ALYNX Nethunter Kernel for Pixel 3/3xl - [Stock][Android 12] and [Android 12L PixelDust/ CAF]
What is Nethunter ?
Kali NetHunter is a free & Open-source Mobile Penetration Testing Platform for Android devices, based on Kali Linux.
Click to expand...
Click to collapse
Code:
I'm not responsible for bricked devices, dead SD cards.
Do some research if you have any concerns about features included in this Kernel.
About the kernel :
The Kernel is based on Kirisakura sources for bluecross
Features:
Internal Wifi Monitor Mode Support (packet injection doesn't works as it is based on qcacld-3.0 which is not capable of packet injection yet)
HID gadget keyboard/mouse
USB WiFi, mac80211 (Monitor mode, packet capture, packet injection) [Compatibility List]
RTL88XXAU USB WIFI Support
RTL8188EUS USB WIFI Support
ATH9K_HTC USB WIFI Support
Ethernet Support
Bluetooth USB Support
SDR Support
BadUSB
for more kernel features look into Kirisakura Kernel thread as it is based entirely on Kirisakura sources
warning: please do not update magisk after flashing the kernel, you can update the magisk before flashing the kernel.
Installation:
Boot the device into Twrp recovery .
Backup your current kernel inside Twrp
Download Alynx-12L.zip if you're using Android 12L PixelDust or CAF rom else download Alynx-12-nethunter-bluecross.zip for [STOCK/ PIXELDUST CAF ANDROID 12 ]
Flash the zip (Flashing the kernel/zip will keep root)
Install Busybox
Download Wireless_firmware.zip open Magisk and install the zip as Magisk module
Install Nethunter store
Install Nethunter app & Nethunter terminal from Nethunter store
Open Nethunter app & Download the full chroot kalifs within the app and let the app setup everything. After it finishes it'll start the chroot automatically.
Update the sources with apt-get update && apt-get upgrade in the chroot using nethunter terminal
Reboot the device
Note: if nethunter app crashes open any android terminal in su environment and paste the following.
Code:
pm grant com.offsec.nethunter android.permission.ACCESS_FINE_LOCATION
pm grant com.offsec.nethunter android.permission.ACCESS_COARSE_LOCATION
pm grant com.offsec.nethunter android.permission.READ_EXTERNAL_STORAGE
pm grant com.offsec.nethunter android.permission.WRITE_EXTERNAL_STORAGE
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_SU
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH_LOGIN
Screenshots:
Tested on pixel 3 with tplink wn722n v1 and v3 both working perfectly well : )
View attachment 5636393 View attachment 5636395 View attachment 5636397 View attachment 5636399
Extra:
if you want to replace nethunter terminal with termux (not completely nethunter main app will still launch nethunter terminal everytime for any operation but you can access kali chroot environment from termux.
(i know nethunter terminal sucks)
Follow these steps to access the environment from termux:
Install termux from f-droid or from nethunter store
Open termux and install root repo using pkg update && pkg install root-repo tsu wget
Download the script from termux wget https://raw.githubusercontent.com/name-is-cipher/boot-nethunter/main/install_boot-kali.sh
chmod +x install_boot-kali,sh && ./install_boot-kali.sh
let it setup everything.
restart termux and type boot-kali to access the nethunter chroot environment
Spoiler: Changelog: [2022/10/29]
- Alynx [NE]
- Bluetooth Support (Added MIssing Drivers)
- Ethernet Support
- Fix RTL 8XXX SL (Replaced)
- All the goodies from KIrisakura Kernel
Thanks to @freak07 for his amazing work.
Downloads & Links :
- Flashable Zip: https://mega.nz/file/nIQTlZYT#GOzWmxygnQa-HX41EtLfJCybZvOdXPMUu3Yx64xYTgg
Spoiler: Changelog: [2022/10/02]
Alynx [End of Life] PixelDust Android 13 CAF
- Upstream Kirisakura
- all the goodies from kirisakura kernel + some modifications from @spezi77
Thanks to @freak07 for his amazing work.
Links: https://mega.nz/file/iRBSWDzZ#0gqZgWYmWLCanRkIjts-4VagW5lsPAm7i7zxfYqUj6M
Credits:
Freak07 For KIrisakura Kernel
Team Kali For Nethunter
Kimocoder For wifi patches
Darkar25 For fixing wifi bugs
Special Thanks to Matthias for helping with the toolchain
XDA:DevDB Information
Alynx Nethunter Kernel For Pixel 3/3xl
Contributors: V3rB0se
Source Code: https://github.com/V3rB0se/Alynx-Nethunter
Version Information
Status: Stable
Stable Release Date: 12/06/2022
Created 13/06/2022
Last Updated 13/06/2022
Thank for this build . But i have problem when install TL722v1 on nethunter to use it . Wish you support soon
chiinh9h said:
Thank for this build . But i have problem when install TL722v1 on nethunter to use it . Wish you support soon View attachment 5685105
Click to expand...
Click to collapse
it should be working already. no need to insert anything. just flash the kernel install the firmware module, run wifite and see if it detects your wifi adapter.
Hi, could you provide a Guide for building this kernel? I tried to build, and the build was successful, but the touchscreen is not working. Am I missing something?
I face this same problem when I compile the sources from the stock kernel after modifying the defconfig for nethunter. Could you help?
Toolchain Used: Google toolchain from the Kernel repo tree.
Thanks.
MShivaG said:
Hi, could you provide a Guide for building this kernel? I tried to build, and the build was successful, but the touchscreen is not working. Am I missing something?
I face this same problem when I compile the sources from the stock kernel after modifying the defconfig for nethunter. Could you help?
Toolchain Used: Google toolchain from the Kernel repo tree.
Thanks.
Click to expand...
Click to collapse
you are missing some extra modules
I fixed the touchscreen issue.
Now the kernel panics and reboots whenever I tried to run wifi commands like iwconfig, wifite, airmon-ng. I used b1c1_defconfig and updated it with nethunter kernel configs.
ended up with kernel panic!
which defconfig you have used to build? Could you please update in the kernel sources?
Thanks
MShivaG said:
I fixed the touchscreen issue.
Now the kernel panics and reboots whenever I tried to run wifi commands like iwconfig, wifite, airmon-ng. I used b1c1_defconfig and updated it with nethunter kernel configs.
ended up with kernel panic!
which defconfig you have used to build? Could you please update in the kernel sources?
Thanks
Click to expand...
Click to collapse
try to build it from this source
V3rB0se said:
try to build it from this source
Click to expand...
Click to collapse
With b1c1_defconfig? b1c1_defconfig is with Kirisakura configs.
V3rB0se said:
try to build it from this source
Click to expand...
Click to collapse
I traced back the issue. It seems to be from the ioctl. Have you faced this issue?
MShivaG said:
I traced back the issue. It seems to be from the ioctl. Have you faced this issue?
Click to expand...
Click to collapse
it was a headache fixing these compile time errors i don't even remember them correctly but they're fixed now you should compile the kernel from the link i posted earlier i fixed all these errors in it.
V3rB0se said:
it was a headache fixing these compile time errors i don't even remember them correctly but they're fixed now you should compile the kernel from the link i posted earlier i fixed all these errors in it.
Click to expand...
Click to collapse
After a full research on the kernel hardening I found that this is because CFI conflicts. The kernel freaks out and panic in response to the cfi_failure. After disabling the CFI and LTO the kernel runs smoothly and all the attacks are working fine.
Could you tell me if your kernel had been compiled with CFI disabled?
The kernel source is missing some modules(So far I found files for wiregaurd is missing). Could you please check and update the kernel sources?
MShivaG said:
After a full research on the kernel hardening I found that this is because CFI conflicts. The kernel freaks out and panic in response to the cfi_failure. After disabling the CFI and LTO the kernel runs smoothly and all the attacks are working fine.
Could you tell me if your kernel had been compiled with CFI disabled?
The kernel source is missing some modules(So far I found files for wiregaurd is missing). Could you please check and update the kernel sources?
Click to expand...
Click to collapse
you can check the defconfig cfi is disabled in it. and what do you mean it is missing some modules? it's just another fork of kirisakura kernel with some minor changes. it is clearly mentioned in the post that the kernel uses sources from kirisakura kernel.
MShivaG said:
After a full research on the kernel hardening I found that this is because CFI conflicts. The kernel freaks out and panic in response to the cfi_failure. After disabling the CFI and LTO the kernel runs smoothly and all the attacks are working fine.
Could you tell me if your kernel had been compiled with CFI disabled?
The kernel source is missing some modules(So far I found files for wiregaurd is missing). Could you please check and update the kernel sources?
Click to expand...
Click to collapse
I can't help you if you're not using the source i provided, CFI and LTO were disabled in the source, you shouldn't be complaining about it when you're using the source from i don't know where?
V3rB0se said:
you can check the defconfig cfi is disabled in it.
Click to expand...
Click to collapse
Which defconfig? I already asked it. I don't find any of the defconfig match nethunter configurations. I don't find any defconfig with local version "Alnyx Nethunter".
V3rB0se said:
it is clearly mentioned in the post that the kernel uses sources from kirisakura kernel.
Click to expand...
Click to collapse
I know the source is from Kirisakura.
V3rB0se said:
I can't help you if you're not using the source i provided, CFI and LTO were disabled in the source, you shouldn't be complaining about it when you're using the source from i don't know where?
Click to expand...
Click to collapse
I tried to compile with your source( see the error, missing wiregaurd). I have attached the screenshot. You should have mentioned that the security feature CFI and LTO are disabled in the first place in your post. It is one of the important security features of Kirisakura kernels. We need to fix the CFI conflicts not disable them.
V3rB0se said:
I can't help you if you're not using the source i provided
Click to expand...
Click to collapse
I am not crazy to ask this forum if I am not using the source described here. As your source is throwing errors I used Kirisakura sources and it's working fine. See the screenshot if you don't believe it.
Why are you too confident? By mistake, you should have forgotten to push the code from your machine.
Don't you check once before replying?
Please don't take anything wrong. We are here to help each other.
MShivaG said:
Which defconfig? I already asked it. I don't find any of the defconfig match nethunter configurations. I don't find any defconfig with local version "Alnyx Nethunter".
I know the source is from Kirisakura.
I tried to compile with your source( see the error, missing wiregaurd). I have attached the screenshot. You should have mentioned that the security feature CFI and LTO are disabled in the first place in your post. It is one of the important security features of Kirisakura kernels. We need to fix the CFI conflicts not disable them.
I am not crazy to ask this forum if I am not using the source described here. As your source is throwing errors I used Kirisakura sources and it's working fine. See the screenshot if you don't believe it.
Why are you too confident? By mistake, you should have forgotten to push the code from your machine.
Don't you check once before replying?
Please don't take anything wrong. We are here to help each other.
Click to expand...
Click to collapse
what makes you so confident that it's missing the wireguard ? use the build script from kirisakura that's not how it works, and for the defconfig it doesn't contain alynx nethunter (my bad) but the default b1c1_defconfig doesn't contain LTO and CFI flags and the main reason for disabling them in the first place is my potato system which doesn't have enough ram to compile the sources with lto and cfi enabled. if it doesn't contain some modules regarding nethunter do inform me I'll push them in the upcoming builds.
and if you're looking for a post on "how to compile a kernel" you're in the wrong place my friend. im not here to teach you. you can visit nathan chance guide on compiling a kernel.
if you care about security you shouldn't install nethunter. see this
V3rB0se said:
what makes you so confident that it's missing the wireguard ? use the build script from kirisakura that's not how it works, and for the defconfig
Click to expand...
Click to collapse
I have attached the screenshot in the previous reply. The same issue occurs even when using Kirisakura build script. I don't know why you removed the script 12 days before. try yourself the fresh clone of your source and try to build. I'm tired of explaining.
V3rB0se said:
and if you're looking for a post on "how to compile a kernel" you're in the wrong place my friend.
Click to expand...
Click to collapse
When did I ask you this my dear friend?
V3rB0se said:
if you care about security you shouldn't install nethunter.
Click to expand...
Click to collapse
I do agree and I have already read this before installing chroot.
MShivaG said:
I have attached the screenshot in the previous reply. The same issue occurs even when using Kirisakura build script.
Click to expand...
Click to collapse
why bother asking if you feel "tired of explaining"
for the removal of build script it was the wrong one. i accidentally put it there.
check if your cloud is blocking the connection as the kernel fetches latest wireguard
Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
Alynx nethunter kirasakura sources for pixel 3 and pixel 3xl - Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
github.com
V3rB0se said:
why bother asking if you feel "tired of explaining"
for the removal of build script it was the wrong one. i accidentally put it there.
check if your cloud is blocking the connection as the kernel fetches latest wireguard
Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
Alynx nethunter kirasakura sources for pixel 3 and pixel 3xl - Alynx-Nethunter/fetch-latest-wireguard.sh at backup · V3rB0se/Alynx-Nethunter
github.com
Click to expand...
Click to collapse
OMG! Finally. Thank you for clarifying. This is what I am looking for.
Warranties:
THIS GUIDE COMES WITH NO WARRANTY. I AM NOT RESPONSIBLE OF BREAKING YOUR PRECIOUS TABLET.
PLEASE BACKUP YOUR DATA BEFORE CONTINUING, AS THIS GUIDE WILL WIPE YOUR DATA.
Also, this guide assumes you have the following requirements:
Bootloader unlocked
TWRP installed
Installation:
Before proceeding, pick the tablet and go to TWRP.
Do the normal wipes for clean flash.
Copy the zip to sdcard or on the tab wherever you like.
Flash the zip from TWRP.
Reboot and done, enjoy
Problems:
No SELinux support yet
Cameras will NOT work, as we are using a newer 3.4 kernel for Oreo!
You tell
If you like my work, you can donate here
Download:
espresso3g
espressowifi Thanks to @RDS5
Source Code:
GitHub - MightyM17/android_device_samsung_espressowifi-1
Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.
github.com
GitHub - MightyM17/android_device_samsung_espresso3g-1
Contribute to MightyM17/android_device_samsung_espresso3g-1 development by creating an account on GitHub.
github.com
GitHub - MightyM17/android_kernel_ti_omap4
Contribute to MightyM17/android_kernel_ti_omap4 development by creating an account on GitHub.
github.com
GitHub - MightyM17/android_hardware_ti_omap4: For Android Oreo and above
For Android Oreo and above. Contribute to MightyM17/android_hardware_ti_omap4 development by creating an account on GitHub.
github.com
GitHub - Unlegacy-Android/proprietary_vendor_ti
Contribute to Unlegacy-Android/proprietary_vendor_ti development by creating an account on GitHub.
github.com
GitHub - MightyM17/proprietary_vendor_samsung
Contribute to MightyM17/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
ROM OS Version: 8.1.0 Oreo
Status: Alpha
Initial boot took 6-7 mins for me
Update 13/01/2022
userdebug build
Added zram to kernel
Fixed USB
Added patches for video
Added Terminal, nano, Launcher3Go
Overall, usable build now except wifi is broken
Update 15/01/2022
Fixed adb
Fixed wifi
Rebased zram form 3.15 kernel
Wow
Screenshots:
{
"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"
}
cant wait to try out this new rom!
Mighty said:
Warranties:
THIS GUIDE COMES WITH NO WARRANTY. I AM NOT RESPONSIBLE OF BREAKING YOUR PRECIOUS TABLET.
PLEASE BACKUP YOUR DATA BEFORE CONTINUING, AS THIS GUIDE WILL WIPE YOUR DATA.
Also, this guide assumes you have the following requirements:
Bootloader unlocked
TWRP installed
Installation:
Before proceeding, pick the tablet and go to TWRP.
Do the normal wipes for clean flash.
Copy the zip to sdcard or on the tab wherever you like.
Flash the zip from TWRP.
Reboot and done, enjoy
Problems:
No SELinux support yet
Cameras will NOT work, as we are using a newer 3.4 kernel for Oreo!
You tell
Download:
espresso3g
Source Code:
GitHub - MightyM17/android_device_samsung_espressowifi-1
Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.
github.com
GitHub - MightyM17/android_device_samsung_espresso3g-1
Contribute to MightyM17/android_device_samsung_espresso3g-1 development by creating an account on GitHub.
github.com
GitHub - MightyM17/android_kernel_ti_omap4
Contribute to MightyM17/android_kernel_ti_omap4 development by creating an account on GitHub.
github.com
GitHub - MightyM17/android_hardware_ti_omap4: For Android Oreo and above
For Android Oreo and above. Contribute to MightyM17/android_hardware_ti_omap4 development by creating an account on GitHub.
github.com
GitHub - Unlegacy-Android/proprietary_vendor_ti
Contribute to Unlegacy-Android/proprietary_vendor_ti development by creating an account on GitHub.
github.com
GitHub - MightyM17/proprietary_vendor_samsung
Contribute to MightyM17/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
ROM OS Version: 8.1.0 Oreo
Status: Alpha
Initial boot took 6-7 mins for me
Click to expand...
Click to collapse
i am not an expert at android but i had found some workarounds to use legacy camera on newer kernels on this website
https://review.lineageos.org/q/topic:android-o-mr1-camera-hal1-lineage-15.1
if these changes are made to the os is there a possibility of the camera working?
Mahaadevan said:
i am not an expert at android but i had found some workarounds to use legacy camera on newer kernels on this website
https://review.lineageos.org/q/topic:android-o-mr1-camera-hal1-lineage-15.1
if these changes are made to the os is there a possibility of the camera working?
Click to expand...
Click to collapse
Hi! Cameras here are a bit more complicated than just 7.1 -> 8.1 bump
We changed the kernel as well here which lead to change in the rmsg implementation by TI.
The 3.0 kernel blobs had camera support but since there are no 3.4 ones for our device, we use some from another device without camera, it doesnt work.
There are a few threads trying to get Ducati (OMAP4's imaging subsystem) to work with 3.4 kernel
[WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started
[WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started ~ # cat /proc/version Linux version 3.4.24-00010-g001648b-dirty ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #15 SMP PREEMPT...
forum.xda-developers.com
[ROM][AOSP][4.4/6.0/7.1] Unlegacy Android Project
The Unlegacy-Android Project Introduction Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy...
forum.xda-developers.com
Just search for ducati, camera or something similar and you'll find a lot of info
Mighty said:
Update 15/01/2022
Fixed adb
Fixed wifi
Rebased zram form 3.15 kernel
Click to expand...
Click to collapse
I might be missing some posts, but is it or will it be available for espresso wifi variants as well?
Alotheone said:
I might be missing some posts, but is it or will it be available for espresso wifi variants as well?
Click to expand...
Click to collapse
I use my personal laptop for these builds and have an espresso3g only, so im very quickly running out of space and time if i try and build espressowifi as well.
Since espresso3g depends on espressowifi any build using my sources should work without any issues for espressowifi, its just that i dont have the hardware for it, building two devices takes quite the space and build time
If you can build it yourself and/or have build servers in mind lmk
Mighty said:
Hi! Cameras here are a bit more complicated than just 7.1 -> 8.1 bump
We changed the kernel as well here which lead to change in the rmsg implementation by TI.
The 3.0 kernel blobs had camera support but since there are no 3.4 ones for our device, we use some from another device without camera, it doesnt work.
There are a few threads trying to get Ducati (OMAP4's imaging subsystem) to work with 3.4 kernel
[WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started
[WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started ~ # cat /proc/version Linux version 3.4.24-00010-g001648b-dirty ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #15 SMP PREEMPT...
forum.xda-developers.com
[ROM][AOSP][4.4/6.0/7.1] Unlegacy Android Project
The Unlegacy-Android Project Introduction Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy...
forum.xda-developers.com
Just search for ducati, camera or something similar and you'll find a lot of info
Click to expand...
Click to collapse
thanks for the info. i wasnt aware about this issue with the newer kernel but now it makes sense.
Mighty said:
I use my personal laptop for these builds and have an espresso3g only, so im very quickly running out of space and time if i try and build espressowifi as well.
Since espresso3g depends on espressowifi any build using my sources should work without any issues for espressowifi, its just that i dont have the hardware for it, building two devices takes quite the space and build time
If you can build it yourself and/or have build servers in mind lmk
Click to expand...
Click to collapse
I wish I could build, but unfortunately I can't.
If you turn off the screen by pressing the power button, or by the timer, the screen does not turn on with the power button or volume.
If charge when off, then the screen is always on with a black background. Also, when it is turned off and charging, if you hold down the power button, it will not turn on
Aurora store nightly installs but does not open as in aosp 8.1
Do you have the same problems?
Thanks a lot
upd. if turn on in a horizontal position, it does not respond to pressing and the window "A vendor image mismatch ..." hangs, and if you turn it on in a vertical position, then the window can be closed
Maybe @LR7875 will read this thread and build a ROM.zip.
TidalMist said:
If you turn off the screen by pressing the power button, or by the timer, the screen does not turn on with the power button or volume.
If charge when off, then the screen is always on with a black background. Also, when it is turned off and charging, if you hold down the power button, it will not turn on
Aurora store nightly installs but does not open as in aosp 8.1
Do you have the same problems?
Thanks a lot
upd. if turn on in a horizontal position, it does not respond to pressing and the window "A vendor image mismatch ..." hangs, and if you turn it on in a vertical position, then the window can be closed
Click to expand...
Click to collapse
same with turn on screen. Nothing help. only long press power button to force restart
TidalMist said:
If you turn off the screen by pressing the power button, or by the timer, the screen does not turn on with the power button or volume.
If charge when off, then the screen is always on with a black background. Also, when it is turned off and charging, if you hold down the power button, it will not turn on
Aurora store nightly installs but does not open as in aosp 8.1
Do you have the same problems?
Thanks a lot
upd. if turn on in a horizontal position, it does not respond to pressing and the window "A vendor image mismatch ..." hangs, and if you turn it on in a vertical position, then the window can be closed
Click to expand...
Click to collapse
Could you try enabling volume button wakes device from settings and check if that works?
Not even plugging it into charging wakes it up which is very weird.
Didnt try aurora store, could you send the logcat?
The horizontal/vertical problem is very sus, i get the vendor thingy but i can just press okay and it goes away
alright, im going to build this for espressowifi @Mighty
its nice to finally get off the aging UA code since its not getting updated anymore
lineageos is way nicer
what roomservice.xml are you using and which operating system your using? (im using ubuntu 16.04, but i dont know if its the right version to build this. last time i built lineageos 15.1 for a different device i used ubuntu 20.04, so im wondering if i need to use that.
RDS5 said:
alright, im going to build this for espressowifi @Mighty
its nice to finally get off the aging UA code since its not getting updated anymore
lineageos is way nicer
what roomservice.xml are you using and which operating system your using? (im using ubuntu 16.04, but i dont know if its the right version to build this. last time i built lineageos 15.1 for a different device i used ubuntu 20.04, so im wondering if i need to use that.
Click to expand...
Click to collapse
Shouldn't matter, it's Ubuntu 20.04 in wsl that I use.
Sources are in #1 post
The issue of device not waking up seems to be much deeper, once it's in sleep it doesn't change its state no matter what
RDS5 said:
alright, im going to build this for espressowifi @Mighty
Click to expand...
Click to collapse
If you or @Mighty can share your manifest, or let me know which branch of @Mighty's repos to use, I can try t make a build of LineageOS for microg
Wow! It's amazing! I still use my tablet and I'm glad to see that someone supports it! Looking forward to the Wi-Fi build! Thank you very much!