Related
This thread is for everyone who compile's Cyanogenmod Kang build's from source and would like to post/share with everyone. If you want your build included in this post just pm me and I will update this post asap.
Warning these are unofficial CM7 build's (with myself cherry-picking comments from CM's Gerrit for testing) which may have unfinished mods and/or broken code that is continually changing, ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM. Don't file bug reports on the Cyanogenmod issue tracker from any of these build's. Please don't bother cyanogen or #teamdouche as you have been warned these build's are unofficial and come with no support except on this thread. If you have any question's try searching as your question might have been already asked and answered. Note: I, nor is anyone else is/are responsible for any bricks or problems you may encounter.
I no longer have a G2 as I gave it to my mom, but will update this periodically. Sorry for the delay I have been super busy with the move, my new job and fixing this house I am now living in.
All credit goes to cyanogen & #teamdouche, thank them not me as all I do is compile
Items from CM's Gerrit that I cherry-picked:
* Give me time
Last Commit repo synced before building-
* Enable access to Audio Effects Settings
I understand that this build is unofficial and I take no responsibility if you brick your phone- Will be update in about an hour and half as I plan on running it when I get home
Please visit @cmsrc, CM's Gerrit or Nightly Device Changelog for a complete list of changes or commits.
Also those who don't know a Kang is an unofficial nightly that someone builds from CM's github.
I will update this post as often as needed to stay current or change as necessary.
Hey everyone, here are the kangs and cherry picks that i will be providing. I want to thanks plasmadragon007 for allowing me to post here.
Everything in the above post applies to here. We will most likely be making these at a different time of day with possible different commits. I do not own a g2 but i do have a couple of decent guys willing to test each kang before posting. If they are not available, i will let you know that the build has not been tested. I do this because i enjoy it and want to. I hope you enjoy it also.
All credit goes to cyanogen & #teamdouche.
Items from CM's Gerrit that I cherry-picked:
Lockscreen background http://goo.gl/5p5Np
you can find my builds on Euroskank http://goo.gl/U7xx6
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
All Builds + recoveries can be found here. I have included a date + md5sum
http://xdafiles.net/rhcp/
More Builds/Gapps can be found here:
gridlock32404 - cm7rc0 built by gridlock will be http://www.crackflashers.com/ cause of dropbox excessive traffic, will build new ones tonight if new commits
I uploaded it just now.
You will need to flash CWRecovery 3.0+. Which can be found at
http://xdafiles.net/rhcp/
This has been all built from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
If you want to see protected apps. You need to edit your build.prop in system with the following:
Code:
ro.build.description=soju-user 2.3 GRH55 79397 release-keys
ro.build.fingerprint=google/soju/crespo:2.3/GRH55/79397:user/release-keys
This is built from current src as of 30 mins ago.
So, there is a few video fixes and others.
You can read the updates at: http://r.cyanogenmod.com/#q,status:merged,n,z
I appreciate it man. I just moved and I don't have an internet connection yet. It's hard to repo sync on a 1mbps Android tether.
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
smjfosho said:
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This one is more recent, with the newest commits.
Is your link supposed to point to recovery.img?
bivio said:
Is your link supposed to point to recovery.img?
Click to expand...
Click to collapse
Thanks. I mistyped fixed now.
Camcorder still borked?
rhcp0112345 said:
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
The rom can be found at: http://www.mediafire.com/?15l284rnq1zjt1h
I uploaded it just now.
You will need to flash this with CWR 3.0. Which can be found at
http://mrcellphoneunlocker.com/recovery.img
This has been all buit from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
Click to expand...
Click to collapse
the link to the recovery img is broken because it says reovery not recovery
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Vandale said:
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Click to expand...
Click to collapse
Sure your not Thats why your watching these threads like everyone else, including me!!
Downloading now, Thanks for the build!
Been waiting for this all day. Thank you!
[ROM]cm7 gingerbread flavor
[Recovery]clockwork 3.0.0
Glad everyone likes.
My pleasure
Sent from my HTC Vision using XDA App
do you know if usb issue was addressed in this build
Have not tested it. Nor do I see any commits. So I assume same issue.I don't mount usb so doesn't bother me. I use adb
Sent from my HTC Vision using XDA App
is the "unknown" thing still showing up in phone number? its the only thing keeping me from sticking with Gingerbread @[email protected] silly, i know.
having problem flashing the img help
I get an assert failed error trying to flash the ROM, too bad I was really looking forward to trying CM7 .
cough..... cough http://forum.xda-developers.com/showpost.php?p=10083640&postcount=151 cough..... cough... man I'm really sick
OmniROM Galaxy 551/Callisto port [OmniARMv6]
Current port status: beta - may not be suitable for daily use. For experienced users only.
Latest Google Apps package: not yet available
Pre-requisites:
ClockworkMod or TWRP recovery
Initial install:
Download the latest build that supports OTA updates from: http://dl.androidarmv6.org/callisto
Reboot to recovery, wipe data and install the update package normally.
How to perform OTA (over the air) update:
Go to Settings -> About phone -> System updates. The latest diff between your current ROM and the latest build will be downloaded, which will be used to create a new update zip in the /sdcard/OpenDelta folder.
If you are using OmniARMv6 TWRP recovery, it can flash the new update automatically [not yet tested].
If you are using CWM recovery, you can flash the patched package (/sdcard/OpenDelta/omni-*.zip) manually.
Source:
Complete project: https://github.com/omniarmv6
Device (note: relies on shared device configuration): https://github.com/omniarmv6/android_device_samsung_callisto
Kernel: https://github.com/androidarmv6/android_kernel_samsung_msm
Reserved #1
Reserved #2
I have tested and found camera is not working , document (file manager) unable to open apk file and need some work on lock screen except that rom is smooth.
Thank for creating thread.
thanks
ROM is very smooth and fast. Works much faster than CM11.
Very thanks
@psyke83 omni rom will be used kernel 3.×.× as per source given above.
@psyke83 omni project has been abanded ? after bunch of ota failed ota disappeared from Jenkins. This rom is smooth and fast except few problems like camera,keyboard back light and lock screen resize.
Last builds (also for other devices) are dated June 15. And the last Android version was 4.4.3. Is it just a build process that got stuck, or is it more serious?
Links are down!
Hey man,
Thank you and others in armv6 team for their incredible work. You guys brought CM11 to a number of devices and that's a BIG DEAL.
Since our device is quite old now, I can see why the project died.
Now, the only thing we want is the links of the latest stable (RC) builds of the devices hosted somewhere. I can (at-least) host (CM11 and OMNI) stable builds of callisto in my GDrive.
Anyone knows what the license for ready-built ROMs is? That is, if the original source goes down, would anyone be allowed to upload a copy?
I'm not thinking about modified images yet - but it'd be easy to make people download something that isn't identical to the original thing, and the md5sum files have also gone - would archive.org be able to help? https://web.archive.org/web/*/http://download.androidarmv6.org/_builds/callisto/* seems to return something at least
Can Someone reupload this?
[Q&A] [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Q&A for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ansh2000 said:
result is same as before.
Click to expand...
Click to collapse
TWRP 2.6.0.0 and ClockworkMod v6.0.5.3 upload pls.
can't install it
Hi ! I need help with this installation procedure, cause i put the code on the terminal emulator, and then, my cwm is deleted.. I want to try this cm rom ! Please help !
Problem with recovery
I didn't have problems before with installing any rom or recovery, I think I've passed through all of possible combinations, but this time, it's terribly buggy :/
I started from stock rom 2.3.6 XEO (as always) then installed CWM Custom Recovery "CWM-5.0.2.8_GAZZY.tar" (need some cwm to update, right?) but stock rom didn't find "flash_image" just like few other roms (arkas for ex.)
Finally Burnmode's KitKatSpecialEdition didn't alert about anything missing and it just jumped to the next line. (success I think, right?) The problem is that when I reboot into recovery it flashes a blank, black screen and reboots leaving my phone recovery-less ! What do I do wrong? Since then I tried many roms and most of them don't work anymore (no luck with cm10.2 for example, KitKat special edition works, so it's the only thing I can now run without bugs, but it's BurnMode's rom, it always works well)
I downloaded recovery.img "2014-12-04 22:43:18" which is the newest (at least now!) is there a problem with the recovery, my phone or maybe I am doing something wrong? My options are now very limited since many things crash my phone (can't flash a stock rom anymore, might be hard to do it again)
Hi
Thanks for your great work. I updated my cooper (s5830) to the latest release but my device won't boot. So I return back to the previous version.
For totoro??
Hi Sir, Im on Galaxy Y s5360 , no possibility for our totoro device?
Help!
help me when i'm trying to download cwm on github is error that i'm missing the Overall/Read permission. How can i fix it? Help
recovery
I couldnt download u recovery, u wot m8 with it i havrnt got perms, upload it normal or get REKT
Can we expect working cm12 on our devices? Or this is the end of the unofficial support?
The page is closed now. Is anybody known how long will be unable to download ROMs on this page? Are there any other links in which we can get RC14 for Callisto? Thanks for help!
Updates? LinkS?
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
anasahmad17 said:
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
Click to expand...
Click to collapse
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
steve8x8 said:
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
Click to expand...
Click to collapse
I tried finding the rom and the only one i could find on the inter-webs is here but the website is paid one so i cant download and i cant check the checksum
http://chomikuj.pl/kaktus47/Telefon....0.0-GT-I5510-callisto,4616249982.zip(archive)
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Prerequisites:
You must have flashed CWM6 using Odin before.
Also you need a second partition on your sdcard, formatted as ext4.
Preparation:
Put the files you need on the sdcard (normal vfat partition), shut down the phone.
Charge the phone's battery.
Now the really tricky stuff (if you mastered Odin, that's just a piece of cake though):
Start the phone into recovery.
Flash the ROM image, and wipe data.
Boot into Android, install and setup s2e to use the sd-ext partition.
Reboot into recovery.
Flash the gapps package, and possibly one of the keyboard zips (see http://forum.xda-developers.com/showpost.php?p=56625731&postcount=162 for those). You may have to switch off package checks in between.
Reboot into Android, and change your governor and io scheduler settings.
Done.
Edit: I've got requests to share the filespace - which should be accessible by link. I'm re-adding the URL now. Apologies to everyone who tried in vain
@steve8x8 Hi, I know it's been a long time but i hope you see this, but could you please be more specific with the steps? what files to use, what keys to press? Sorry it's been a while since i used this phone or any android phone, what odin version should i use?
Have you searched the 'net (and the archive.org) for the original 551 blog? It has/had a quite good explanation of almost everything related to this particular phone. Odin version doesn't matter much, I had used 4.34 (that was current when the instructions were written) and 4.43 IIRC, no difference. Make sure to get good instructions for the CWM flash, as this is the stage where most bricks happen.
To make things easier, I'm uploading the stuff related to the Odin step from my HD ("Odin" subfolder on GDrive), more than two years old. Use them on your own risk, and check the URLs provided.
Note that I didn't go directly for CM11, but installed CM10.2 first. I would have to read the instructions to tell whether this was actually necessary...
On the way, I upgraded the recovery (from the jenkins server that doesn't exist any longer, http://jenkins.androidarmv6.org/view/Developers/job/cm-recovery/24/ of Oct 2014) to 6.0.5.3. (IIRC I did this using the terminal emulator, not Odin, but that should be possible too. I'll upload the recovery.img)
You perhaps max have to create your own Odin-flashable recovery similar to the following (again, I assume no liability at all!):
- take a .tar.md5 as starting point, and unpack it (it's just a tar with a checksum appended)
- replace the recovery.img
- create a new tar file x.tar (name it as you like)
- (cat x.tar; md5sum x.tar) >x.tar.md5
- Odin flash that
I admit it becomes more and more difficult to keep the necessary tools, files, and instructions available and in shape for devices as old as this one (I'm still confused by the "KERNEL3" series.)
---------- Post added at 09:22 AM ---------- Previous post was at 09:00 AM ----------
Quick addendum: there's a new, stagefright-fixed cm11 available for callisto, see http://forum.xda-developers.com/showthread.php?t=2453085&page=27 - which is currently being debugged but looks promising (see page 29 of that thread)
---------- Post added at 10:09 AM ---------- Previous post was at 09:22 AM ----------
It seems that there's a lot of stuff still around if you search for the "galaxy-551" tag.
Bebek's GD might also be interesting (with Odin, CWM5, and more, but stopping at Gingerbread): https://docs.google.com/folderview?...SURkMEE&tid=0B-QaRW7SLPQPTHpaQXR5b1ZVMHc#list
1
bro help
thx for sharing
steve8x8 said:
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Click to expand...
Click to collapse
Please don't remove those files from gdrive!:good:
Danke sehr
I didn't plan to, and indeed they are still there. Is there anyone using a Callisto running CM11?
Last night I had a dream: There was a recent ROM upgrade for the Callisto (not sure whether Nougat or Oreo), and I had started to dig out all the old instructions and notes to make it happen.
Only in the morning, after having a big mug of coffee, I realized it was only a dream :'(
armv6 ghosts haunting...
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Click to expand...
Click to collapse
You ARE the ONLY one, who IS responsible for your device health. NObody in this thread (especially author) is NOT responsible! Live long and prosper
Important:
I cannot help you with ROM problem if:
you cannot formulate, what is wrong
you've made some modifications in ROM or Kernel
you do not know, how to follow instructions
I would be very grateful for help with debugging and searching for errors and non-working features
Also I would be grateful for advices about how can be solved some problems
Instructions
First install of ROM with New Storage Layout:
BACKUP ALL DATA
if it wasn't done already:
Unlock your device via http://www.htcdev.com if you haven't done so already
Read the post by @Thömy about how to migrate to the New Storage Layout
Factory Reset / Wipe data
Copy CM-12.1.zip to SD card (optionally copy gapps to SD card)
Boot into recovery
Flash CM-12.1.zip
Optionally flash gapps
Reboot to bootloader
Flash boot.img from CM-12.1.zip via fastboot
Reboot
Wait for "Optimizing apps" (it can take up to 30 minutes in some cases, so, please, be patient)
Use CM
Updating from CM 12 or 12.1 with New Storage Layout:
BACKUP ALL DATA
Copy CM-12.1.zip to SD card (optionally copy new gapps to SD card)
Boot into recovery
Flash CM-12.1.zip
Optionally flash new gapps
Reboot to bootloader
Flash boot.img from CM-12.1.zip via fastboot
Reboot
Wait for "Optimizing apps" (it can take up to 30 minutes in some cases, so, please, be patient)
Use CM
Coming from another ROM with New Storage Layout:
BACKUP ALL DATA
Factory Reset / Wipe data
Copy CM-12.1.zip to SD card (optionally copy gapps to SD card)
Boot into recovery
Flash CM-12.1.zip
Optionally flash gapps
Reboot to bootloader
Flash boot.img from CM-12.1.zip via fastboot
Reboot
Wait for "Optimizing apps" (it can take up to 30 minutes in some cases, so, please, be patient)
Use CM
Downloads
2015-04-29(28) (mirror)
2016-07-21 (mirror)
ChangeLog
2015-04-29(28)
First test build from CM GitHub
2016-07-21
One more first test build from CM GitHub
Known Issues
Stock camera issues
Battery drains
Unexpected dissapearing of Mobile Data or WiFi
Volume changes during playback when returning to home screen
FAQ
Is there any problem when dirty update from CM 12/12.1?
I haven't found any problem
When will be a release of newer version?
Nobody knows that
XDA:DevDB Information
CyanogenMod 12.1, ROM for the HTC One X
Contributors
VaskivskyiYe
Source Code: https://github.com/CyanogenMod/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-05-04
Last Updated 2016-07-21
Reserved
Reserved
5.1.1?
Thank you.
Thank you bro.
Sent from my Galaxy Nexus using XDA Free mobile app
downloading ....
@VaskivskyiYe
Wow!
Welcome to XDA-Developers community! Very grateful for your contribution.
Expected Thömy to release this after his exams.
Are you expecting to maintain CM 12.1 builds?
Rowlf said:
@VaskivskyiYe
Wow!
Welcome to XDA-Developers community! Very grateful for your contribution.
Expected Thömy to release this after his exams.
Are you expecting to maintain CM 12.1 builds?
Click to expand...
Click to collapse
Thanks (
Yes, I'll continue support of this builds. Unfortunately, I'm not such a pro, as Thömy, and I'm not sure, I can deal with all the bugs and problems in builds. But I can try (
Hi, I want to try this, first I was wondering if there are more bugs/more unstable than latest cm12. Thanks!
Can someone upload telephony-commons.jar from this rom in system/frameworks?
I accidentaly rewrote it with wrong one.
scottjay said:
Hi, I want to try this, first I was wondering if there are more bugs/more unstable than latest cm12. Thanks!
Click to expand...
Click to collapse
This build is as (un)stable as 12.0 builds. But you have to keep in mind, theoretically it can consist issues, that weren't already found and they could be critical
GrizCro said:
Can someone upload telephony-commons.jar from this rom in system/frameworks?
I accidentaly rewrote it with wrong one.
Click to expand...
Click to collapse
system/framework/telephony-common.jar
Mirror please.
o1100101 said:
Mirror please.
Click to expand...
Click to collapse
Yeah... I vote for basketbuild or androidfilehost.
o1100101 said:
Mirror please.
Click to expand...
Click to collapse
Regnas said:
Yeah... I vote for basketbuild or androidfilehost.
Click to expand...
Click to collapse
AndroidFileHost mirror added to Download section
So far everything seems stable, except network. It breaks completely randomly and reboot is required to reconnect.
VaskivskyiYe said:
AndroidFileHost mirror added to Download section
Click to expand...
Click to collapse
Great.
Thank you.
Thank you for this awesome ROM
@VaskivskyiYe
Have you changed anything in the device sources (so post a link to your git pls) or only downloaded from CM and ran the build?
crusader727 said:
@VaskivskyiYe
Have you changed anything in the device sources (so post a link to your git pls) or only downloaded from CM and ran the build?
Click to expand...
Click to collapse
@crusader727
This first build was just taken from CM sources. Now I am trying to fix important functions (like mobile data and WiFi crashes). After I'll succeed in dealing with any problem of ROM and post new build, I'll also add git source to the thread
VaskivskyiYe said:
@crusader727
This first build was just taken from CM sources. Now I am trying to fix important functions (like mobile data and WiFi crashes). After I'll succeed in dealing with any problem of ROM and post new build, I'll also add git source to the thread
Click to expand...
Click to collapse
Thanks for the hard work, it already seems more responsive than CM12. I've noticed that swipe typing now works, but swipe to wake no longer seems to work. Or I just aren't looking hard enough.
Any update on the device crashing when you enter the multitasking in landscape?
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.