Related
Guys i've downloaded cm-13.0 source code
while building am getting these error please help me to fix
please see the log for the errors.
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
LineageOS 17.x Unofficial for Galaxy A3 2017
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Camera (both photos and video)
NFC
Sensors
Vibration
Others I have forgot
What isn't working?
Echo present in calls for the other side (no fix currently found)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
Stretched preview in camera, photos are fine (fix has more downsides than upsides)
Supported variants
Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest OrangeFox build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
In OrangeFox wipe everything except SD and OTG.
Flash LineageOS.
Optional: Flash GApps (rightafter).
Optional: Flash Magisk.
Reboot.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Downloads
• ROM
get.mcfy.fr
Google Drive
• Recovery
OrangeFox
• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH
• Root
Magisk: GitHub
Credits
Huge thanks to:
@Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
@McFy for help along the way and letting me use his server as a mirror.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-08-26
Telegram group
Join here!
Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more
Changelogs
- 20200221
Initial build
- 20200403
March security patches
Many optimisations and smaller fixes
Rootdir updated from A6 2018 Q, along with some proprietary files
Graphics now r29, from A6 2018 Q
Way too much stuff to list here, thx @Astrako for the work
- 20200613
Fixed GPlay crashes
June security patch, and all other LineageOS source changes
SEPolicy Enforcing
Reworked shims
Now using new power HAL
Many smaller optimisations
- 20200713
July security patch and all other LineageOS source changes
Reworked overlays
ROM now passes SafetyNet out of the box
Defined location provider to *hopefully* fix location with MicroG
Updated OMX libs
Other smaller fixes and optimisations
- 20200825 20200830
August security patch and all other LineageOS source changes
Updated FP from coral's April patch to keep passing SafetyNet
Switched to proprietary audio HAL - fixed in-call echo
Other smaller fixes and optimisations
NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
- 20210118
January security patch and all other LineageOS source changes
Other smaller fixes and optimisations
Reserved
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
banciii said:
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
Click to expand...
Click to collapse
I'm dumb for not testing this, I gotta look at home
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
yann29 said:
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
Click to expand...
Click to collapse
I am not the author of Lineage 16.0, I only use the same mirror
The maintainer of LineageOS 16.0 is @McFy.
If you have the problems with the camera, this sounds like an app using the camera when you try to use it and I haven't been able to reproduce the problem. Please check all your apps and report back.
Hope you like the ROM
Ok thanks. Another issue : I can't get split-screen working with any apps. And you?
Other issue : the echos in calls...but well-known issue on lineage. Hope you will find something...
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
starbright_ said:
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
Click to expand...
Click to collapse
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
MartinYTCZ said:
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
Click to expand...
Click to collapse
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
starbright_ said:
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
Click to expand...
Click to collapse
Yup, ROM is not spoofed out of the box, so your only hope is nanodroid patcher, which doesn't seem to work in Q :/
Also if you've already got Treble, you can flash this with the TWRP you are currently using
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I am building myself and running the latest at this time (using the crdroid device tree) and everything is running perfectly for me! (even with a few patches of my own like enabling dark mode in defaults app and a few command-line programs like rtl-sdr, no gapps (f-droid only)). Added screenshots to prove it indeed boots.
If I'm not mistaken this ROM uses the android_samsung_universal7870 device tree as it is on Gitlab?
Then the only few bugs I can talk about are the USB settings unable to be changed live while that worked on the outdated device tree from Github (screenshot can be provided), and the Camera, but I know that's already WIP.
(Sure there's echo in calls but... No one was successful at fixing this and even the crappiest patches I tried myself didn't work)
Thanks to all those who works on this device tree.
The provided Rom of the dedicated XDA thread run fine on my device but when building myself, I have the same problem : traped on bootanim.
Strange, I supose it's my buid env, my laptop is on Debian 10 and I did not make any mod on the standard base.
I will try with a VM and Ubuntu LTS as sugested by AOSP Project.
MartinYTCZ said:
LineageOS 17.x Unofficial for Galaxy A3 2017
How to install
Make sure you have latest bootloader and modem before installing this.
Created 2020-02-22
Last Updated 2020-02-22
Click to expand...
Click to collapse
Thank you for great work, can I ask from where can get latest modem and boot-loader without download whole firmware?
Hello,
Problems are solved ?
Echo present in calls for the other side (investigating)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (investigating)
Stretched preview in camera, photos are fine (probably unfixable)
And stay at home.
Best regards
Migrate doesn't detect it as an installed rom, any help?
pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I have pushed some changes to GitLab yesterday which fix this problem. You should be able to boot a new build just fine now :highfive:
Just another ROM Built from source by me guys, I hope you all will like it.
{
"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"
}
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.
What Works:
•everything
Bugs:
•none
ROM Download link:
Download | Alternate
Source:
GitHub - lenovo-devs/android_device_lenovo_TBX304: lineage device tree for Lenovo Tab 4 10 (TB-X304)
lineage device tree for Lenovo Tab 4 10 (TB-X304). Contribute to lenovo-devs/android_device_lenovo_TBX304 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_device_lenovo_tb-common
Contribute to lenovo-devs/android_device_lenovo_tb-common development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_kernel_lenovo_msm8953
Contribute to lenovo-devs/android_kernel_lenovo_msm8953 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/proprietary_vendor_lenovo
Contribute to lenovo-devs/proprietary_vendor_lenovo development by creating an account on GitHub.
github.com
Android Version: Android 10
Kernel: Linux 3.18X
Based on: LineageOS
Status: Stable
wow!! such a beautiful rom, best rom for this device I tried so far, thx alot for this great rom
Good to see there is someone who is working hard to keep this tablet alive, Thanks alot for your hardwork, Cheers
Nitiín said:
Good to see there is someone who is working hard to keep this tablet alive, Thanks alot for your hardwork, Cheers
Click to expand...
Click to collapse
what version is that, L or F? Since this rom is built on top of lineage, then most likely it's target for L version as well?
ravenchaser210 said:
what version is that, L or F? Since this rom is built on top of lineage, then most likely it's target for L version as well?
Click to expand...
Click to collapse
I have the L or lte variant, but as specified in the title it must work perfectly on F variant as well.
Nitiín said:
I have the L or lte variant, but as specified in the title it must work perfectly on F variant as well.
Click to expand...
Click to collapse
unfortunately, I tried the L version from Lineage os side, both 16/17, it stuck in boot screen forever...I doubt this gonna work either, but could try later
Akash23q2 said:
Just another ROM Built from source by me guys, I hope you all will like it.
View attachment 5387233
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.
What Works:
•everything
Bugs:
•none
View attachment 5387249
ROM Download link:
Download | Alternate
View attachment 5387247
Source:
GitHub - lenovo-devs/android_device_lenovo_TBX304: lineage device tree for Lenovo Tab 4 10 (TB-X304)
lineage device tree for Lenovo Tab 4 10 (TB-X304). Contribute to lenovo-devs/android_device_lenovo_TBX304 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_device_lenovo_tb-common
Contribute to lenovo-devs/android_device_lenovo_tb-common development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_kernel_lenovo_msm8953
Contribute to lenovo-devs/android_kernel_lenovo_msm8953 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/proprietary_vendor_lenovo
Contribute to lenovo-devs/proprietary_vendor_lenovo development by creating an account on GitHub.
github.com
View attachment 5387251
Android Version: Android 10
Kernel: Linux 3.18X
Based on: LineageOS
Status: Stable
Click to expand...
Click to collapse
Thanks Bro Everything working good BUT OTG is not working in this built and I badly need it.
@Akash23q2 Bro can You port any custom ROM for my device lenevo TBX304L.
NEED RECENT APPS LOCK FEATURE AND ONE TAP CLEAN ALL APPS FEATURE
You are legend and please make more ROM for lenevo TBX304L
Thank You
I AM SHARING SOME OF MY SCREENSHOT OTHERS HELP
[email protected] said:
Thanks Bro Everything working good BUT OTG is not working in this built and I badly need it.
@Akash23q2 Bro can You port any custom ROM for my device lenevo TBX304L.
NEED RECENT APPS LOCK FEATURE AND ONE TAP CLEAN ALL APPS FEATURE
You are legend and please make more ROM for lenevo TBX304L
Thank You
I AM SHARING SOME OF MY SCREENSHOT OTHERS HELP
Click to expand...
Click to collapse
Glad you liked it, mtp host or you can say it otg, is broken in device tree, so I will need to fix it in device tree, it's not rom side issue.
Apart from it, for lock option and clear all in recents, you can consider flashing this magisk module.
Here is the link to module - https://drive.google.com/file/d/1DbnNV3GvoT_3lyEZ6xiwKCx17Ktzkd6o/view?usp=sharing
Akash23q2 said:
Glad you liked it, mtp host or you can say it otg, is broken in device tree, so I will need to fix it in device tree, it's not rom side issue.
Apart from it, for lock option and clear all in recents, you can consider flashing this magisk module.
Here is the link to module - https://drive.google.com/file/d/1DbnNV3GvoT_3lyEZ6xiwKCx17Ktzkd6o/view?usp=sharing
Click to expand...
Click to collapse
Glad you Replied it, Please fix it in device tree as soon as possible.
And the module link that you send is not working on my tab, it's enlarge app icon size and disable recent options.
If You can provide me your Telegram I'd or your group I'd ,it will be helpful for me to contact you directly
Thank You
[email protected] said:
Glad you Replied it, Please fix it in device tree as soon as possible.
And the module link that you send is not working on my tab, it's enlarge app icon size and disable recent options.
If You can provide me your Telegram I'd or your group I'd ,it will be helpful for me to contact you directly
Thank You
Click to expand...
Click to collapse
I am a bit busy these days with my studies so I will look into it when I will get time.
For launcher stuff, check this guide Link
Hi, @Akash23q2 I had it installed but had issues with the worn out tablet and reinstalled. Now I can't get it to boot. Would you mind looking at log to see if you can identify where the error is. I pulled logcat while stuck at boot animation so it is complete from startup to freeze. If you have time, no rush.
well, can't get log file to load. will keep trying. had to upload to mediafire acct as I could not attach it here.
logcat.txt
There is an issue with the site blocking certain .txt files according to content. Have to compress them to get past screening.
Akash23q2 said:
Just another ROM Built from source by me guys, I hope you all will like it.
View attachment 5387233
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.
What Works:
•everything
Bugs:
•none
View attachment 5387249
ROM Download link:
Download | Alternate
View attachment 5387247
Source:
GitHub - lenovo-devs/android_device_lenovo_TBX304: lineage device tree for Lenovo Tab 4 10 (TB-X304)
lineage device tree for Lenovo Tab 4 10 (TB-X304). Contribute to lenovo-devs/android_device_lenovo_TBX304 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_device_lenovo_tb-common
Contribute to lenovo-devs/android_device_lenovo_tb-common development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_kernel_lenovo_msm8953
Contribute to lenovo-devs/android_kernel_lenovo_msm8953 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/proprietary_vendor_lenovo
Contribute to lenovo-devs/proprietary_vendor_lenovo development by creating an account on GitHub.
github.com
View attachment 5387251
Android Version: Android 10
Kernel: Linux 3.18X
Based on: LineageOS
Status: Stable
Click to expand...
Click to collapse
sir, i have been using this rom from past 1 year and i can surely say it is the best rom but pls fix screen recording issue in this rom, am unable to share or record my screen.... and thats the only issue from my side, i hope you will fix it soon..
sir, pls fix screen recording issue.. am unable to record or share screen...
Yes, I know you are busy with studies and stuff. But can you please make a custom ROM of pixel experience for lenovo tab x304 f/l?. I would be grateful if you can make the file.
Hey
I thought of trying this on my tablet however the oem unlocking option is greyed out and when i try unlocking using adb, I get a message saying "oem unlocking is not allowed". Can someone help me in this
Infernape_35 said:
Hey
I thought of trying this on my tablet however the oem unlocking option is greyed out and when i try unlocking using adb, I get a message saying "oem unlocking is not allowed". Can someone help me in this
Click to expand...
Click to collapse
This guide works quite well.
tek3195 said:
This guide works quite well.
Click to expand...
Click to collapse
I had seen this but i get a message saying "Status 21 device is not ready" or status 6 as well. Really want to install the rom on this tab to keep it alive
Infernape_35 said:
I had seen this but i get a message saying "Status 21 device is not ready" or status 6 as well. Really want to install the rom on this tab to keep it alive
Click to expand...
Click to collapse
make sure you are in 9008 mode by running lsusb and run qdl commands as root
edit; just realized you get that message using the guide for getting bootloader unlocked, right ?
tek3195 said:
make sure you are in 9008 mode by running lsusb and run qdl commands as root
edit; just realized you get that message using the guide for getting bootloader unlocked, right ?
Click to expand...
Click to collapse
Yes, using that guide
I did make sure I was in 9008 but I didn't know about the commands. Will check again
Akash23q2 said:
Just another ROM Built from source by me guys, I hope you all will like it.
View attachment 5387233
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.
What Works:
•everything
Bugs:
•none
View attachment 5387249
ROM Download link:
Download | Alternate
View attachment 5387247
Source:
GitHub - lenovo-devs/android_device_lenovo_TBX304: lineage device tree for Lenovo Tab 4 10 (TB-X304)
lineage device tree for Lenovo Tab 4 10 (TB-X304). Contribute to lenovo-devs/android_device_lenovo_TBX304 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_device_lenovo_tb-common
Contribute to lenovo-devs/android_device_lenovo_tb-common development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/android_kernel_lenovo_msm8953
Contribute to lenovo-devs/android_kernel_lenovo_msm8953 development by creating an account on GitHub.
github.com
GitHub - lenovo-devs/proprietary_vendor_lenovo
Contribute to lenovo-devs/proprietary_vendor_lenovo development by creating an account on GitHub.
github.com
View attachment 5387251
Android Version: Android 10
Kernel: Linux 3.18X
Based on: LineageOS
Status: Stable
Click to expand...
Click to collapse
this is great. can you join our telegram group where we discuss about the issues and other stuff for the tablet. it would be really helpful for us. thank you. the link is
LOS Builds(Unofficial) [Lenovo Tablets]
You can view and join @LenovoTabletsLOS right away.
t.me
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!