Related
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
Simply stated, we can't really list features here. There are too many and they change too frequently, and we now support a truly insane number of devices. Chances are, if you like a feature, we have it already. Seriously.
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
Both nightly and release builds are available. Please note that nightlies are for development purposes. This means that they may not work properly, may not flash, may not build for days at a time, and will probably eat your cat. If you flash these, know what you're doing, have backups, and don't complain when something happens. It's on you!
http://carbon-rom.com
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
You can also find a changelog in Settings->Carbon->About Carbon
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our G+ Community: http://community.carbon-rom.com This is where we spend the bulk of our time and the best way to reach us and other community members. We update and frequent this community far more than XDA, simply due to time constraints and the convenience of G+.
5) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Welcome to the unofficial CarbonRom thread for the NTT-DoCoMo Galaxy S III (sc-06d/d2dcm)
Make sure you have the correct device before you flash. These will not work on the i900 series.
These builds are not official because the kernel is not the standard CM kernel at this point in time. This is due to our device being a massive pain in the rear to develop for because DoCoMo likes to change things in their phones to make it "special". Thank you Dorkomo...
These builds are made by a very hard working developer by the name of @interlope. He's not part of the main Carbon team and does not receive anything from them. As a way of saying thank you for these builds we encourage you to donate to him.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=G9NQ5R43K8T8Q
If you are unable to do this, we request that you find some other way to contribute. Debugging is a very good way. Basically, we are looking for people who want to be active contributors and not just leech off others hard work.
The builds are now out of alpha and we have decided to open them up to everyone. However, to those that have and do contribute in the future I will be making modded versions of the roms with some extra goodies and such to show our appreciation. Keep checking those inboxes.
All builds are located here:
http://www.oudhitsquad.com/android/?dir=Samsung/d2dcm/carbon
The latest build (and all future builds) do not have Felica support.
If you are coming from stock there are instructions for rooting this device here:
http://forum.xda-developers.com/showthread.php?t=1895737
Bug reports
If you have a bug to report make sure you get a log of it or you will be ignored and removed from the testers list.
I won't go into the details of how to take logs. There are lots of tutorials on these forums on how to do that. However, there is a convenient app that will take the appropriate logs and upload them to wherever you like.
https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=en
Known bugs as of 08-11-13
none
Are you sure this is the right forum to post this? This is for the international version of the SIII (GT-I9300) AFAIK. Sry if I'm just not aware of any special rules...
nazfalas said:
Are you sure this is the right forum to post this? This is for the international version of the SIII (GT-I9300) AFAIK. Sry if I'm just not aware of any special rules...
Click to expand...
Click to collapse
We don't have our own forum so we piggy-back on the international s3 forum.
DroidZombie said:
We don't have our own forum so we piggy-back on the international s3 forum.
Click to expand...
Click to collapse
kk, didn't know
Check you inboxes folks the latest build just went out.
DroidZombie said:
Check you inboxes folks the latest build just went out.
Click to expand...
Click to collapse
Thank you. Can i do a dirty install or does it have to be a clean install?
dreamers123 said:
Thank you. Can i do a dirty install or does it have to be a clean install?
Click to expand...
Click to collapse
Clean. Wipe your system too.
Just cleaned installed. Everything is working great so far.
Sent from my SC-06D using Tapatalk
At the moment is the PacMan nightly van 7november flashed. To install the PAC rom there is a need to also flash GAPPS.
When I want to try the carbon rom is there a need to flash another GAPPS file?
And if its needed where can I found the correct GAPPS file.
topcads said:
At the moment is the PacMan nightly van 7november flashed. To install the PAC rom there is a need to also flash GAPPS.
When I want to try the carbon rom is there a need to flash another GAPPS file?
And if its needed where can I found the correct GAPPS file.
Click to expand...
Click to collapse
any 4.3 gapps is fine. I use slim gapps personally. They work very well with dark carbon.
Kernel
Which kernel is good for this rom? focusing on battery
Lean?Yank555? They work on the rom? anyother good?
rogerxcamargo said:
Which kernel is good for this rom? focusing on battery
Lean?Yank555? They work on the rom? anyother good?
Click to expand...
Click to collapse
At the moment there are no custom kernels for this device (read the description and make sure you have the device mentioned).
This is a Japan specific phone. If yours does not say sc-06d on the back of the device this is not the thread for you.
DroidZombie said:
Check you inboxes folks the latest build just went out.
Click to expand...
Click to collapse
So builds are 100% non-sharable now? I just wanna be clear so I don't post a link a some point and get yelled at.
Is this a request from OUDHitSquad?
Might want to put JAPAN at the front of the thread title, and move the first lines from post 2 into the 1st post so people can quickly ID this as the Japanese variant thread.
This link might be helpful to people to people (posted on the old thread). Not sure if this is what you're meaning:
http://www.oudhitsquad.com/android/?dir=Samsung/d2dcm
My back button sometimes does not response. Any Suggestion? I am running on the latest version.
Gesendet von meinem GT-I9300 mit Tapatalk
bikeaholics said:
My back button sometimes does not response. Any Suggestion? I am running on the latest version.
Gesendet von meinem GT-I9300 mit Tapatalk
Click to expand...
Click to collapse
You're in the wrong thread. Read the description very carefully
Sent from my SC-06D using Tapatalk
great day! john just made it happen. i've just sent him humble donation.
btw, if anybody wants to cook its own rom based on above i've just modded
well known old jpn cooker for this. you can fetch it from below link
https://app.box.com/s/6z2uj0svw40c5ogli677
dzebrys said:
great day! john just made it happen. i've just sent him humble donation.
btw, if anybody wants to cook its own rom based on above i've just modded
well known old jpn cooker for this. you can fetch it from below link
https://app.box.com/s/6z2uj0svw40c5ogli677
Click to expand...
Click to collapse
Please put that on the rooting thread. And be VERY careful about using it now. There have been massive changes to the kernel which may result in an unstable rom.
And to everyone else please check the second post for updates
RULES1. Read the OP fully.
2. For bug reports, I need a log to assess the issue. Capture a log while replicating the issue.
3. Do not ask ETA's on updates; you will be ignored.
4. Use the "search this thread" feature to make sure your question wasn't already answered by using key words.
5. Only ask a question about this project. Any questions about another ROM or project will be disregarded.
6. If you dont like my ROM then too bad.
7. You want 100% untouched/unmodified AOSP. This isn't the ROM for you.
8. AOKP is open source. so you can always build it yourself.
Instructions:Download ROM .zip file
Download KitKat GApps
Download latest SuperSU flashable (Optional)
Reboot to Recovery
Flash ROM, GApps, SuperSU .zip files
Clear Dalvik/Cache
Reboot and EnjoyIf you want to run art thats fine but use at YOUR OWN RISK as i currently do not support it.
DOWNLOADS
ROM: Mod Edit: Link RemovedGAPPS: HERESuperSU: HERE
Also a quick shoutout to xboxfanj for letting me use his kernel. Thanks bro
XDA:DevDB Information
One M8, ROM for the HTC One (M8)
Contributors
MadTwatter, xboxfanj
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOKP
Version Information
Status: Stable
Current Stable Version: 8.29.2014
Stable Release Date: 2014-08-29
Created 2014-08-31
Last Updated 2014-09-03
Thread closed pending further information and understanding of duplicated thread.
Thread reopened to allow OP to add sources, credits and add more detail regarding the "essence" of this ROM...
It's mostly kernel optimization with a little bit of rom tweaking to make it smoother, when I get time I will sit down and go over the commits that I think are worth telling people about if that makes you feel more comfortable sir.
Sent From The Tardis
MadTwatter said:
It's mostly kernel optimization with a little bit of rom tweaking to make it smoother, when I get time I will sit down and go over the commits that I think are worth telling people about if that makes you feel more comfortable sir.
Sent From The Tardis
Click to expand...
Click to collapse
This thread started out rather poorly and has been cleaned. I'm going to leave the thread open for now so that the OP can update the first post as @LenAsh requested and so that members can help with testing and troubleshooting. I am subscribing to this thread to encourage members to be on their best behavior. Instead of arguing in a thread and posting PMs publicly in a thread, please report the offending posts / PM and let a moderator handle it.
To the OP:
First off, welcome to XDA. We are glad you decided to post a ROM here. A few things:
You are required to post the following. If you do not within the next few days, I will need to close the thread and remove the download links:
1. Kernel source: You mention "kernel optimizations" so you need to upload your source code to Github. If you used a kernel without any changes, then please link to the thread of that kernel.
2. Credits: Link to AOKP at least to give them credit for the base. Also credit for any tweaks you found here that you included.
Suggested things to post. Although these are not required, most threads have them and members expect them so they know what they are flashing (I personally wouldn't flash a ROM without these).:
1. Feature list: what this ROM has that makes it special. You made changes that you liked - what were they?
2. Screenshots
3. Changelog: when you have one since this is the initial release
For more help on what's expected for ROM OPs, please look at these guidelines.
I don't want to close the thread. In fact, I like to encourage people to develop on here. So, please at least post kernel source and credits to keep the thread open. The other stuff is gravy and can be done as you get time or your thread maintainer you mentioned gets to it.
Hope the OP is adjusted according to XDA rules. i'm going to kick things off by flashing and testing this ROM. i'll check for any kind of malware/spyware (crash-test-dummy). Keep your fingers crossed.
Chuckd610 said:
Hope the OP is adjusted according to XDA rules. i'm going to kick things off by flashing and testing this ROM. i'll check for any kind of malware/spyware (crash-test-dummy). Keep your fingers crossed.
Click to expand...
Click to collapse
I wouldn't be holding my breath on the OP providing the info requested by @coal686. I see he's been active around the place, but this mustn't be a priority.
Out of interest, did you flash the ROM, and if you did, how did it go?
OP has stated that he is not going to update the thread to give credits (kernel source is in the download tab), so thread closed and download link removed until he changes his mind.
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, dexter93 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-12-12
Reserved
Changelog
20150921-1824: Changelog: Fixed recovery issues <<-- building
20150918-1152 : initial release [5.1.1_r16]
Downloads
haxynox-6.0-i9300-20151211-2331.zip 236.6MB
33aeb6e59ec686818cd4088502b75fd1
haxynox-i9300-20150921-1824.zip 208MB
MD5:130cea4633f0e9b278aeb3def6d67d08
Reserved
GApps
For Marshmallow 6.0 Roms I recommend the PICO version of OpenGapps
http://opengapps.org/
I have tested @dankoman s GApps ZERO package with this ROM and it works fine.
Here is the link
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
If you want to use anything else, please feel free to post about your experience, but be aware that if you GApps package of choice doesn't work on this AOSP rom, you'll need to convince the GApps maintainer to take a look into it. That being said I am happy to talk with any maintainer.
mcgi5sr2 said:
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, mcgi5sr2 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-09-21
Click to expand...
Click to collapse
^
That is what we always needed. Finnaly someone made it. THANK YOU!
Is there any screen shoots? And do we need GAPPS or is it included? I will try the rom. Thanks for taking your time to make annother ROM for our old S3
@mcgi5sr2 Hey man, I really commend you for doing this. All I've seen lately is Archi, Moster, & co.'s work (Apologies to the many unmentioned) being used as "base" for other users "projects", and of course all the real work is going on at source in the aforementioned dev's repos. I feel XDA has become a really unoriginal and user- (rather than dev-) oriented place recently.
Of course, you're not radically rewriting the fundamental Android code like the PA team did with Hybrid, but with such a ***ch of a chipset* it's pretty sick that you've taken it head-on to get AOSP up.
Sorry if this was a bit aggrandizing, I've just been tired of the constant stream of Sammy ROM ports and zip kangs.
By the way, you refer to yourself: "Ivan_Meler, mcgi5sr2 and myself", I think it should be "Ivan_Meler, dexter93 and myself"?
* "If you've ever glanced upon the sources" ... you bet you ... a glance was too much, I'm scarred ...
Thread cleaned, if you think you spotted a bug please attach logfiles and/or what you tried to fix it yourself etc.
Whiskey
Forum Moderator
Excellent, thanks for creating a thread for haxynox. Better than people posting in the slim/omni thread.
Any idea on how to fix the fact im getting bootloops on this particular rom?
I waited a long time for this! Thanks to all team :highfive::highfive:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
it's pure AOSP code ... without cyanogenmod 12.1 modifications.
if i understood correctly
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
lukewilliams418 said:
Any idea on how to fix the fact im getting bootloops on this particular rom?
Click to expand...
Click to collapse
Could you provide a little more info please?
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
No, in fact it has a lot less, but that is the point.
b0unty said:
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
Click to expand...
Click to collapse
The sources are all freely available, feel free to use them
lukaaa477 said:
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
Click to expand...
Click to collapse
see above...
myshakugan said:
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
Click to expand...
Click to collapse
Yea,sure it does,but i mean something else.
What i mean is, is there anything specific to the device changed, eg. Ram management,performance gains,optimizations etc.
mcgi5sr2 said:
Could you provide a little more info please?
No, in fact it has a lot less, but that is the point.
The sources are all freely available, feel free to use them
see above...
Click to expand...
Click to collapse
I used the latest version of TWRP to wipe all data and then I Installed the haxynox zip file with TWRP and then it just goes in a bootloop.
Bootloop
Enviado desde mi GT-I9300 mediante Tapatalk
any fix for this bootloop???
The Unlegacy-Android ProjectIntroduction
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 Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?
Hello, ladies, gentlemen and non-booleans!
Since I prefer building my own ROMs for various reasons, especially when the device tree source isn't made public, I have now finally gotten a LineageOS 18.0 build together.
"But there's already a build there!"
Fair point, but the sources of the device tree and kernel aren't public anywhere, to my knowleadge.
While I'm nowhere near as much of an open source fanatic as to demand all the source everywhere, it doesn't feel right either.
So since I've got a habit of having my own builds so I myself decide when I get an update, I decided to spin one up and at the same time provide a workaround for others who want to build their own versions.
So, what did I do? Voodoo? Other black magic? No!
I looked at crDroid's Github and the source tree seemed to be largely compatible with the LOS build system customisations.
They seem to often be working pretty closely with LOS build conventions.
They even specifically host a kernel there that has got an Android 11 branch!
And with that, we come to the sources used section:
Sources used:
Xiaomi-common
device
Kernel
So, how would you get your own private builds?
Do a repo sync as normal, then put into
.repo/local_manifests/roomservice.xml the following:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/tissot" name="crdroidandroid/android_device_xiaomi_xiaomi" remote="github" revision="11.0" />
<project path="kernel/xiaomi/msm8953" name="crdroidandroid/android_kernel_xiaomi_tissot" remote="github" revision="11.0" />
<project path="vendor/xiaomi/" name="crdroidandroid/proprietary_vendor_xiaomi" remote="github" revision="11.0-tissot" />
<project path="device/xiaomi/msm8953-common" name="crdroidandroid/android_device_xiaomi_msm8953-common-tissot" remote="github" revision="11.0" />
</manifest>
Do another sync and you're going to have everything you need downloaded. From there it's the usual procedure for builds.
"So, Lilly, that's all well and good, but why upload yet another LOS build?"
Because I've got itchy fingers and while I'm definetely not qualified myself to improve the device tree myself, you could profit from my addiction to doing builds quite frequently and get the latest feature changes pretty quickly.
Aside from that, I also plan on integrating Opengapps into the builds using their build system plugin. I didn't do it right away because last time there were some errors I couldn't figure out and I wanted a build right now.
Another thing I want to get working is having LuciferKernel preinstalled in the overclocked variant, because that overclock is definitely helping performance in my experience. Keep that in mind before installing. If you've got gripes about overclocking and I get the kernel to work (last in tree compilation resulted in an unbootable kernel) you're going to be stuck on the first vanilla version.
All in all, it's just sharing something what I use and trying to fill a tiny niche.
Do keep in mind that I'm definetely not a complete wizard and not an Android ROM developer. I just about know how to build a ROM and how to manipulate it here and there. I provide no support aside from "this build is borked, could you try again?".
That said, here's the download link:
ROM Downloads - Google Drive
drive.google.com
The first build hasn't been tested yet so do not expect to plug and play. I'm in the process of flashing it as I type this. MAKE BACKUPS!
Right, that should just about cover everything. Cheers!
Update: So far it's not booting and throwing up a couple of errors in the logcat. Hm.
I'll examine it a bit tomorrow.
Another update: Flashed crDroid and the same opengapps I used for my LOS build and now it's failing to boot in a similar manner... Weird.
Another update: It boots without that borked opengapps package.
Here's some proof that it boots successfully!
_I did a derp_
I noticed I had synced LOS 18 instead of 18.1
I just finished syncing the other branch and a new build will follow. Should be directly upgradable.
crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards
murtaza1326 said:
crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards
Click to expand...
Click to collapse
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?
lillywho said:
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?
Click to expand...
Click to collapse
i never said that you should not make your own builds but it device side source stuff take reasonable amount of time & hardwork they put about it
imagine you are one of dt maintainers & you publically share your work & people will use it before even waiting for you & giving you first chance (happens alot here)
thus he does this until they get green flag to do so from source side he won't do it
also if i decided to keep my stuff private literally no rom execept abhinav's & sooti (aosp gsi)
would exist for this device (i bet)
you are free to use any of my trees & stuff & make builds but please don't hop over multiple roms (like a mad person) (happens in our community alot)
there are more rom on telegram built by BBots (but they don't regularly update those)
if this is just a personal build & you are not going to update it in feature just don't share it
thanks & regards
What is the current situation?