Related
Hello everyone, after a great success on building roms for bacon device. I've decided to share my work with other devices. So I've started with angler! After positive feedback on the rom today I'll publish here the rom.
Kernel and Device tree are untouched so everything should be working smoothly. You can use a custom kernel in case you like, but i'll only give support to stock kernel as I do not yet own an device. So CM bugs are basically also our bugs, and from what I know there is none. Still I'm open to suggestions.
Download
GAPPS
Features:
Updated SQL to 3.9.0.2
Optimized SQL code for faster Read/Write
CM Super User (for now is the most stable one)
Kernel with F2FS support
Improved Code of frameworks
Optimized Build with custom toolchain on ROM and Kernel
Optimizations for our chip
Improved sound with speex resampler
Improved bionic with many optimized libraries (faster rom)
Improved Art with upstream patches
Optimized native frameworks for our device
LZMA updated to the latest
Proguard 5.2.1
Google Webview
F2FS ready for data and cache
Immersive mode
Expanded Notifications
CAF Task Manager
Snapdragon Camera
Network Monitor
More coming soon
I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.
Thanks
As you might know, all credits go to CyanogenMod Team.
Source Code
If you like my work, please consider a donation.
Reverve
Frequently Asked Questions:
Q: What changes have you made between versions?
A: All changes made are the same as CyanogenMod ROM which can be found here: http://www.cmxlog.com/13/bacon/ and all manual changes will be also stated on 2nd post.
You can also check on Settings --> About where is all the changes .
Q: What is LZ4?
A: Read here about the project: https://github.com/Cyan4973/lz4
Q: Was latest build used LZ4?
A: This is still under testing and I'm working on it. It'll be on the test folder.
Q: What is the test folder?
A: Unstable, and test builds where I seek to study a new configuration to enhance user experience.
Q: Why don't you always share change logs?
A: Limited time. Sorry about it.
Q: Why do you many times ask for donations?
A: Well... This work is free, and as you know if you like it and on your own free will you think I deserve and currently wish to help me out as I am currently going to become unemployed and as also I study for my Masters in Finance , I believe is only fair. While you use, I'm testing and investing my time on it. Should be rewarded because of that right? Is only fair.
Q: Do you receive alot of donations?
A: Since last year until today I've received around 300 euro. But I've invested 1000 hours on these android builds. That gives a ratio of 30 cents an hour.
Q: Why do you still invest on android since it doesn't provide you any feasible income? I would have already quited!
A: Basically this forum makes me relax.
Q: Will you leave cm builds when exodus is released ?
A: I didn't plan on giving my cm builds, but if exodus prove to be superior why should i have double work right? Only time and users will tell.
Q: I'm confused. I have no clue which build is the latest!
A: You can always download again!
Q: Your site have ads why?
A: Need help on extra wealth to survive. Leave some clicks while you visit is only nice.
Q: I want more from the rom!
A: Me too!
Q: Why you sometimes ignore users?
A: I never ignore, just don't have time to answer all. Please help one another and also use search button. I think you prefer me learning to bring something nice than post all the time right? hehe
Q: I have so many questions to ask you!
A: I can provide many answers! Just ask!
Q: Can I PM you?
A: Only when is urgent!
Q: How to report bugs?
A: Our bugs are CM bugs. Report on JIRA: https://jira.cyanogenmod.org
Q: Are you CyanogenMod maitainer?
A: No, just an user which wants to have better builds possible. But would be nice to see CM adding me to the contributions list.
Q: Why Slim gaaps? Open Gaaps are so much cool!
A: Open Gaaps has provided many unstable issues which makes the phone unusable until a clean format. Slim gaaps have shown to be better on that.
Q: Why some buttons of UKM don't work?
A: Need time to improve that..
Q: I want an update app to auto update roms. To lazy to check the thread!
A: I understand, for now is not feasible to do it as I need time to analyse and understand best solution as I update tool-chains regularly and also is not my priority. Remember time is limited for me.
Just to clarify, TWRP for Angler still cannot format partitions to F2FS, correct?
tibere86 said:
Just to clarify, TWRP for Angler still cannot format partitions to F2FS, correct?
Click to expand...
Click to collapse
Actually I dont know casue this is old, but TWRP is well advanced now, https://plus.google.com/+ChetKener/posts/7No16fUQaFz
Oh wow.. Ur ROM was the first custom ROM i had on OPO.. Nice to see you here
I have to admit I didn't check yet on cm source but I'll review.
yung40oz84 said:
Actually I dont know casue this is old, but TWRP is well advanced now, https://plus.google.com/+ChetKener/posts/7No16fUQaFz
Click to expand...
Click to collapse
@jgcaap What do you say about that? Is it worth installing the rom without F2FS?
Do we need to flash the correct vendor image from February's security patch?
Kookitza said:
@jgcaap What do you say about that? Is it worth installing the rom without F2FS?
Click to expand...
Click to collapse
Will work both ways... But f2fs is very nice.
jgcaap said:
Will work both ways... But f2fs is very nice.
Click to expand...
Click to collapse
But F2FS is not work on our device so....
jgcaap said:
Will work both ways... But f2fs is very nice.
Click to expand...
Click to collapse
Yes, I have heard good things about it! So if I do not change /system to F2FS then I will be able to flash this ROM and other ROMS as normal correct? As long as they support F2FS of course for the other partitions I have converted. But some recommend system as F2FS as well, if I did that then what is the draw back? I would have to convert ROMS to be able to flash correct?
Sent from my Nexus 6P using Tapatalk
Kookitza said:
But F2FS is not work on our device so....
Click to expand...
Click to collapse
Oh. Didn't know that. I'll remove my comment. Thanks. Please try out everything and let me know if is all working well.
jgcaap said:
Oh. Didn't know that. I'll remove my comment. Thanks. Please try out everything and let me know if is all working well.
Click to expand...
Click to collapse
I don't know this for sure. I read that in one of the previous comments. Maybe someone can confirm this.. [emoji53]
Sent from my Nexus 6P using Tapatalk
When you say no bugs, did you fix the broken Bluetooth?
jclendineng said:
When you say no bugs, did you fix the broken Bluetooth?
Click to expand...
Click to collapse
Cm has also that bug?
Does this ROM force encryption?
Sent from my Nexus 6P using Tapatalk
Tomorow I'll answer all questions calmly as tomorow I have an exam. I want to deliver here what I delivered on bacon. Smooth experience.
Until then please test and let me know any bugs. Thanks!
Is anyone having issues with the camera?
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.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt the changes. We're good at (properly) fixing compatibility issues between newer Android versions and older devices, among other core things. The "bells and whistles" like themes we leave to others.
The first public build here had something exclusive for the Galaxy Nexus, yet unseen on any other OMAP4 device: all RAM carveouts reserved for Ducati (the multimedia subsystem of OMAP4, responsible for hardware-accelerated video decoding, encoding and camera functionality) have been switched over to CMA.
A few words for those who see CMA for the first time:
The Contiguous Memory Allocator (CMA) makes it possible for device drivers to allocate big contiguous chunks of memory after the system has booted.
The main difference from the similar frameworks is the fact that CMA allows to transparently reuse memory region reserved for the big chunk allocation as a system memory, so no memory is wasted when no big chunk is allocated. Once the alloc request is issued, the framework will migrate system pages to create a required big chunk of physically contiguous memory.
Click to expand...
Click to collapse
This means that a total of 996 MB physical memory is available to the system, while keeping Ducati fully working - this is a huge step forward, coming from the 694 MB available in the last factory image released by Google (Android 4.3). This gives the OS access to an additional 300MB of RAM.
While CMA was just recently implemented for this device, thanks to one of our developers (let's just call him Luden), it's quite stable: even under heavy memory pressure, the system manages to free up the required memory in order to start up Ducati and launch the requested multimedia functionality in a few seconds at most.
Installation
For Marshmallow (6.0) and below, 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.
Problems
While we weren't able reproduce any CMA-related problems, hidden ones can still arise. In most cases, these problems will be either lost Ducati functionality (no multimedia capabilities) until rebooting, or a kernel panic (hard reboot) - upon noticing any of these, be sure to grab a logcat/dmesg and/or last_kmsg and send it to us (preferably by attaching it to a post in this thread).
Other than that, these are bugs we're aware of in the current build:
- The RIL on LTE devices (toro, toroplus) isn't fully working; calls and texts should be OK, but expect no data.
- Sound pops can be observed, mostly when using touch sounds (this is being investigated)
- Some exotic video formats or camera modes might not be perfect - if you notice any artifacts or green spots (the issue that happened in the past), report the details in this thread
- Inverted colors mode not working
- Tricky connection to some 5 GHz Wi-Fi networks
- SELinux is in Permissive mode (this isn't a problem for most people, just mentioned it here as extra information)
If you notice anything else, be sure to report it in this thread. While we're kind of busy, we 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.
As usual, feedback is appreciated
Want to support development? You can consider donating, we've spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi
Source Code: https://github.com/Unlegacy-Android/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Created 2016-03-12
Last Updated 2017-04-07
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.
Incredible work! Thank you to ALL the volunteer developers for making this FREE and OPEN SOURCE progress possible! The code is free, but your time is not! Thank you!!!
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
I'm running this right now, and it's awesome. Marshmallow in general seems to have much better performance than Lollipop on our device. I do miss some custom kernel flags, but I'm sure that'll come with time.
@Ziyan Which recovery do you recommend ?
DRM services not working means also Netflix doesn't work?
PythonNut said:
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
Click to expand...
Click to collapse
DDK 1.9 of course
Master94ga said:
@Ziyan Which recovery do you recommend ?
Click to expand...
Click to collapse
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Master94ga said:
DRM services not working means also Netflix doesn't work?
Click to expand...
Click to collapse
Possibly.
Ziyan said:
DDK 1.9 of course
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Possibly.
Click to expand...
Click to collapse
Thanks, 3.0 unofficial or your last recovery?
You are a god!
I'm downloading and will be testing this, I'm super excited about this work.
EDIT: So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
diogofd8 said:
So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
Click to expand...
Click to collapse
Yes Google Play Services can mess it up - I don't recall how, but I managed to press a skip button or something to easily get past it when it started looping. I guess we should add a mini how-to to the OP about it, as I really don't want to hack the framework for this.
Yep, I'm stuck in "just a sec..."
Edit: I restarted the Phone and now it works.
Netflix works too
Big thanks to @Ziyan and all OMAP4 dev for all your contribution so far ! I'll test this immediately [emoji106]
Sent from my Galaxy Nexus using Tapatalk
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
diogofd8 said:
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
Click to expand...
Click to collapse
There are a couple things going on here. The system ROM is an ext4 image, so it doesn't matter what you format it to, because it'll always become whatever is in the image.
Furthermore, only /data benefits from being F2FS, but it's not you fault for not knowing this because it wasn't mentioned in the documentation!
The other thing is that I don't know of a TWRP build that isn't buggy. When I tried to format to F2FS, it didn't work because my particular version of TWRP had a bug. So maybe your /data format failed for the same reason. I personally do not know what version of TWRP will reliably work for this. But this is a discussion for the TWRP thread.
2) Convert system to f2fs
Click to expand...
Click to collapse
Don't do this! F2FS is not supported on /system.
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
vipelp said:
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
Click to expand...
Click to collapse
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
I already tried both and it doesn't matter.
Browser times out opening google.com.
Play store doesn't load images and can't download apps
Wifi automatically disconnects....
rohitchouhan07 said:
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
Click to expand...
Click to collapse
WiFi working fine for me on 5GHz as well.
To other people: when this ROM boots, you may see the Google splash screen, then the screen will go black, and the device will act like it has died. It hasn't. Just give it a minute and the regular Android boot animation will appear.
OK i'm trying a reflash now. Complete wipe.
For me all work correctly, no problem with google play store or wifi
I wanted to ask if HTC 10 and the sense based roms for it support F2FS file system? I've heard this file system results in improved performance and wanted to try it but don't know if it's supported. Thanks.
jhadsfi said:
I wanted to ask if HTC 10 and the sense based roms for it support F2FS file system? I've heard this file system results in improved performance and wanted to try it but don't know if it's supported. Thanks.
Click to expand...
Click to collapse
I don't know off the top of my head but just use the search field above the top post in any ROM thread for "F2FS" and see what you find. If the OP of a ROM or Kernel thread (as far as I know, it only has to be supported by the kernel, there isn't any special needed in the ROM, but don't quote me on that) doesn't mention F2FS than more than likely it doesn't support it. If you take a ROM that doesn't have F2FS support and you find a stock-based kernel that does support F2FS and works with the ROM in question, then you should be able to use F2FS just fine.
I only had F2FS experience with one ROM on a different phone. The main reason I don't pursue it harder is because until every ROM supports it, which would be easiest if the stock ROM supported it out of the gate, then it makes it a PITA since you then have to reformat the respective partitions to Ext4 every time you want to try a ROM that doesn't support it, and then back again if you want to restore a TWRP backup of the F2FS-supporting ROM, at least if you want to still use F2FS at that point.
But if you think you're going to stick with one ROM for a long time or don't mind the chance of hassle...
roirraW "edor" ehT said:
I don't know off the top of my head but just use the search field above the top post in any ROM thread for "F2FS" and see what you find. If the OP of a ROM or Kernel thread (as far as I know, it only has to be supported by the kernel, there isn't any special needed in the ROM, but don't quote me on that) doesn't mention F2FS than more than likely it doesn't support it. If you take a ROM that doesn't have F2FS support and you find a stock-based kernel that does support F2FS and works with the ROM in question, then you should be able to use F2FS just fine.
I only had F2FS experience with one ROM on a different phone. The main reason I don't pursue it harder is because until every ROM supports it, which would be easiest if the stock ROM supported it out of the gate, then it makes it a PITA since you then have to reformat the respective partitions to Ext4 every time you want to try a ROM that doesn't support it, and then back again if you want to restore a TWRP backup of the F2FS-supporting ROM, at least if you want to still use F2FS at that point.
But if you think you're going to stick with one ROM for a long time or don't mind the chance of hassle...
Click to expand...
Click to collapse
Ah. Thanks a lot for the detailed answer. I did search the forum for F2FS but the only relevant thing I could find was in the elementalx thread where a user was asking whether the kernel supported F2FS and was responded with the code does contain references to F2FS but doesn't the dev hasn't explicitly said anything about supporting it. That user also stated he couldn't get any stock based roms to boot on an F2FS file system.
By the way are the performance improvements really noticeable during use or is changing the file system not really worth it?
jhadsfi said:
Ah. Thanks a lot for the detailed answer. I did search the forum for F2FS but the only relevant thing I could find was in the elementalx thread where a user was asking whether the kernel supported F2FS and was responded with the code does contain references to F2FS but doesn't the dev hasn't explicitly said anything about supporting it. That user also stated he couldn't get any stock based roms to boot on an F2FS file system.
By the way are the performance improvements really noticeable during use or is changing the file system not really worth it?
Click to expand...
Click to collapse
You're welcome! To be honest, for myself and also for the ROM/kernel dev who's ROM/kernel I was on at the time, I think I barely noticed it, although I would still feel more warm and fuzzy knowing it was there in the first place. I forgot to add that to the list of reasons why not to bother jumping through any hoops to use it.
roirraW "edor" ehT said:
You're welcome! To be honest, for myself and also for the ROM/kernel dev who's ROM/kernel I was on at the time, I think I barely noticed it, although I would still feel more warm and fuzzy knowing it was there in the first place. I forgot to add that to the list of reasons why not to bother jumping through any hoops to use it.
Click to expand...
Click to collapse
Ah okay thanks. I just wanted to see what the fuss was all about. Frankly this phone is pretty damn fast with or without F2FS.
I don't really care at this point what I'm using, if it is LineageOS or just standard Android, or something else. I just need something which is stable and well supported, where as many features as possible "just work".
Does anyone have any recommendations?
Just give me one name, anything, something official that is supposed to work.
Use LineageOS. It's not perfect but the best you can.
AICP or Resurrection Remix. Both are non stable version but could be used as daily driver since there arent much bug except those common known bugs that are present on cm source ( im tested em myself)
Option58 said:
Use LineageOS. It's not perfect but the best you can.
Click to expand...
Click to collapse
Which one? I tried lineage-14.1-20170116-tilak-n7100.zip (md5sum: 2987ae54e17a816cfcb0a69c0661f0e8) but OTA updates are not working, I created this thread for that problem: https://forum.xda-developers.com/galaxy-note-2/help/lineageos-n7100-updates-tilaks-build-t3569234
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T
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 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. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- GPS; - need a device owner to configure!
- Camera (both);
- Dock special keys (top row);
- Modem on TG and TL;
- GUI crashes; - occure less often
Currently, no one from Unlegacy Team, has TF300T/TG/TL device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
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 (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Transformer TF300T
Contributors
Clamor, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
I worked on this for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY! TF300TG/TL users shouldn't use this as it can harm your tablet.
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash Stock or Bootloader 4.2 attached in Downloads section.
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
androidjel said:
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
Click to expand...
Click to collapse
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
androidjel said:
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
Click to expand...
Click to collapse
All needed files you can find in Downloads tab on top of this thread
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Clamor said:
All needed files you can find in Downloads tab on top of this thread
Click to expand...
Click to collapse
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
androidjel said:
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
Click to expand...
Click to collapse
Nothing, you may install Rom to see current project progress (If you have TF300T there will be no sound). For further developement test device is needed, or a developer with TF300T(better solution). Mostly all major functions are fixed, see buglist, and 3.4 works on all transformers on Tegra 3.
That is KANG TWRP with support of updated F2FS
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Clamor said:
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Click to expand...
Click to collapse
I am more than willing to be a tester if you want. Heck, I will even find a cheap TF300T to load only this on. My mornings are relatively free as my business doesn't pick up till noon or so. Just PM me specifics of what you need. Any more development for our tablets is a blessing as far as I am concerned
I would love to help debugging, testing and developing. I'm currently in possession of a tf300t with dock and an me301t. Do you think it will be possible to port this to the ME301t?
@gs-crash-24-7 please write me in PM. Actually ME301t was supported at early stages of 3.4 bringup. I fully excluded it from board since I couldn't test it and Memopad parts made transformers board really messy. I had enough problems with TF stuff at that moment.
3.4 kernel porting and repartitioning before were just a dream, but now they are real. Memopad bringup depends only on your interest in it.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs here from O for now. I know already about all major issues.
I have some good news. Here is mostly working Oreo build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Any possibility of sharing the 3.4 kernel supporting the ME301t...I have that little bugger and the latest software updates from my TV provider and Netflis like programs are all KK dead for the most part. Having unlegacy on the Me301t would be a dream come true and would avoid trashing this one and getting a new one just because I want to see some shows or TV. Thank you for your work. I will assist to the best of my knowledge.
@AlphaDivxMovies nothing impossible, but first of all, I have no MemoPad and it's hardware isn't that close as my Prime is with TF300T. Second is that I put huge amount of my time and afforts in porting transformer board so I have no desire at all to do this once more time, I can help with suggestions but actual development will lie on your shoulders.
P.S. To just boot rom atm you would need only a kernel port, ROM is mostly compatible. Almost all drivers memopad uses are already included. You may contact @gs-crash-24-7 as well, he has memopad and if he agrees, than work in pair is much more simple.
@Clamor , Where is the oreo version? https://builds.unlegacy-android.org/ here i could only find the 7.1.2 version.
The other downloads in this post dont work anymore (oreo).
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Clamor said:
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Click to expand...
Click to collapse
@Clamor But could you launch a O build again? maybe i could try to help, I have some time to do that at the moment.