Related
This is an experimental build of CyanogenMod 10.1 for Asus TF300T and TF300TG with the new bootloader 4.2.
If you are an experienced CyanogenMod user, please give it a try and let me know anything I broke.
But please see "Known Issues" below.
Would also be interesting to hear about results on different boot loaders.
Note that this is an unofficial build.
I will provide updates, as things are being fixed, but I don't plan to provide regular nightlies.
Instead I hope that my changes will be merged by CM, once all is working as expected.
Supported Bootloaders
Installed by Asus ROM v10.6.1.15.3 (aka bootloader 4.2).
Should also work with v10.6.1.8 (aka bootloader 4.2).
The current download does not work on the old JB 4.1 bootloader installed with Asus ROM v10.4.2.20.
Testing or fixing this is currently not a priority; even might not work at all.
Extras
Some extras I included that are not part of the official CM distribution:
My kernel patch to make DriveDroid work. See the app thread for more details:
[APP][2.2+] DriveDroid - host ISO/IMG files to boot your PC from
Known Issues
Camera is crashing since 20130430 version. Sorry!
Audio and YouTube videos play about 9% too fast. MX Player works fine.
[WHEN CAMERA WAS WORKING...] Setting camera to burst 20 pictures will stop after 8-14 on average.
No radio on TF300TG.
Downloads
Get the latest version:
cm-10.1-20130509-EXPERIMENTAL-tf300t.zip - 160.11 MB
Older downloads for comparison:
cm-10.1-20130506-EXPERIMENTAL-tf300t.zip - 160.21 MB
cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB
cm-10.1-20130428-EXPERIMENTAL-tf300t.zip - 163.58 MB
cm-10.1-20130427-EXPERIMENTAL-tf300t.zip - 163.58 MB
The latest source code is available from branch cm-10.1 in these two repositories:
https://github.com/f69m/android_device_asus_tf300t
https://github.com/f69m/android_kernel_asus_tf300t
For more details, please see "Building from Source" below.
Changes
Coming Soon:
Fix audio, when keyboard dock is connected; unfortunately this removes support for USB audio.
2013-05-09:
WLAN and audio working on TF300TG.
Small fix for camera, but not working yet.
Properly setting Bluetooth MAC address.
2013-05-06:
Bluetooth working fine for me.
WLAN should be stable for everyone now.
libsurfaceflinger is built from source again, the segfault is fixed.
The screen flickering is definitely gone; running really smooth now.
2013-04-30:
Updated all blobs and config files.
Included libsurfaceflinger from Asus to avoid segfault.
Include patch for DriveDroid.
2013-04-28:
Merged Asus kernel v10.6.1.15.3.
ROW scheduler is back and is default.
GPS updated and tested.
Bluetooth working, but can't re-enable once turned off.
2013-04-27:
New kernel based on Asus v10.6.1.8.4.
Some blobs and configs updated.
These are only the changes made by myself and jsfrk specifically for this build.
The latest changes from CyanogenMod are also included, but not explicitly listed.
Instructions
This experimental ROM is targeted at experienced users that can help test and make it work.
If you are new to CyanogenMod and you need instructions on how to use the download, it is not for you yet. Sorry!
Building from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b cm-10.1-tf300t
You can also run this command in an existing repository.
Credits
The whole amazing CyanogenMod team.
jsfrk for testing and fixing issues on TF300TG.
Asus for breaking bootloader compatibility again.
First download is available!
Of course in my "final" build, I had borked WLAN.
So did a "more final" build, which is now available for download.
Just confirming, it does NOT work with the 4.1 bootloader. The boot animation freezes.
Just another reason for me to update my tablet this weekend. I'll be flashing this for real some time today. Thanks.
Update available:
Merged Asus kernel v10.6.1.15.3.
ROW scheduler is back and is default.
GPS updated and tested.
Bluetooth working, but can't re-enable once turned off.
Really awesome rom! very quick and smooth. But the screen keeps flickering.
crazynitro said:
Really awesome rom! very quick and smooth. But the screen keeps flickering.
Click to expand...
Click to collapse
Yes, I noticed that too.
First step is to update the graphics drivers, I hope that will fix it.
Still getting a segfault with the new drivers though.
Thanks for your feedback!
Sent from my TF300T using Tapatalk HD
I'll be following this thread closely, as I am just too lazy to downgrade my bootloader. Do you need any internal testers? I'm available.:good:
*Edit 1* Flashed without Gapps, it's buttery smooth with no issues (besides bluetooth.) Burst mode in camera works unless you set it to 20 shots, then it takes about 8-14 (average) before stopping. The calculator works. Wifi is a little spotty (randomly disabling and re enabling itself.) Random screen flashes,i'm not bothered by it.
*Edit 2* Flashed with Gapps, all of the above true. WiFi needs a lot of work, it unbearably slow on this ROM.
Downtown taco said:
I'll be following this thread closely, as I am just too lazy to downgrade my bootloader. Do you need any internal testers? I'm available.:good:
Click to expand...
Click to collapse
Hmm, not sure, what you mean with "internal tester"? But I am sure happy about everyone giving feedback, thanks!
*Edit 1* Flashed without Gapps, it's buttery smooth with no issues (besides bluetooth.) Burst mode in camera works unless you set it to 20 shots, then it takes about 8-14 (average) before stopping. The calculator works. Wifi is a little spotty (randomly disabling and re enabling itself.) Random screen flashes,i'm not bothered by it.
*Edit 2* Flashed with Gapps, all of the above true. WiFi needs a lot of work, it unbearably slow on this ROM.
Click to expand...
Click to collapse
Have not seen any WLAN disconnects yet, but indeed, the whole WLAN and Bluetooth code needs redoing (same chip, same driver).
When trying to fix Bluetooth, I usually break WLAN completly, without making Bluetooth work properly.
Next update will be mostly blobs and config files. Doing that slowly to figure out, where that segfault is coming from.
After that will restart the WLAN/Bluetooth code from scratch. Well, from the Asus code that is.
Currently using the code from official CM BL4.1 kernel.
New download that has now all blobs and config files updated!
Seems the random screen flickering is gone, please let me know, if you still see it.
Well, being a bad boy, I included libsurfaceflinger from Asus, though this should really be the one compiled from the CM sources.
But for now it avoids a segfault and it seems OK, while we have worse issues with WLAN and Bluetooth.
Also included a little extra patch that has not been merged into the official CM kernel.
It makes DriveDroid work on our beloved TF300T. For more details see the app thread:
[APP][2.2+] DriveDroid - host ISO/IMG files to boot your PC from
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
kykc said:
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
Click to expand...
Click to collapse
Sorry, I don't have access to a TF300TG, so can't test it.
Of course I am happy to clean up and push out my current sources, if there is a developer who wants to port it to the TG.
Otherwise I'd save the time for cleaning up now and push it out, once I am happy.
Sent from my TF300T using Tapatalk HD
kykc said:
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
Click to expand...
Click to collapse
Glad to let you all know that we found a developer owning a TF300TG!
So I did a big cleanup and pushed things out to GitHub. Please see the first post for details.
Also the graphics lib I had replaced is back in; the segfault is fixed.
It is running incredibly smooth now!
But the camera is still broken. :crying:
I'll have another go at the camera issue, before releasing a new update.
f69m said:
Glad to let you all know that we found a developer owning a TF300TG!
So I did a big cleanup and pushed things out to GitHub. Please see the first post for details.
Also the graphics lib I had replaced is back in; the segfault is fixed.
It is running incredibly smooth now!
But the camera is still broken. :crying:
I'll have another go at the camera issue, before releasing a new update.
Click to expand...
Click to collapse
I'll take whatever version is up now for a spin. I expect most to be the same, minus screen flickers. Am I right?
Sent from my Galaxy Nexus using Tapatalk 2
Downtown taco said:
I'll take whatever version is up now for a spin. I expect most to be the same, minus screen flickers. Am I right?
Click to expand...
Click to collapse
Yes, in the 20130430 version the screen flickering is gone and it is running very smooth.
But also the camera is broken, which worked in the previous versions.
The camera is giving me quite a headache...
Sent from my TF300T using Tapatalk HD
f69m said:
Yes, in the 20130430 version the screen flickering is gone and it is running very smooth.
But also the camera is broken, which worked in the previous versions.
The camera is giving me quite a headache...
Sent from my TF300T using Tapatalk HD
Click to expand...
Click to collapse
It's always the camera...
Sent from my Galaxy Nexus using Tapatalk 2
Just tried a quick install of the ROM. gotta say that it is very smooth and it just feels so snappy its nuts! But yeah, the camera force closes
Sent from my ASUS Transformer Pad TF300T
pcoussa said:
Just tried a quick install of the ROM. gotta say that it is very smooth and it just feels so snappy its nuts! But yeah, the camera force closes
Click to expand...
Click to collapse
Thanks!
Yeah, luckily I have a very strong head, so eventually the camera will have to yield.
Temporarily the camera has won though; I put it aside and first looked into WLAN and Bluetooth.
Good news is, here I am hearing music via Bluetooth from my Laptop speakers!
And even after switching off and on.
So I guess there will be an update later today with WLAN more stable and Bluetooth working.
We are also working on WLAN on the TF300TG and have that somewhat working, too!
Though might not be in today's release yet.
Sent from my TF300T using Tapatalk HD
New update available!
Sorry, the camera is still broken... :crying:
BUT... Bluetooth is now working fine for me.
I don't own any real Bluetooth devices though. I tested using my laptop as a Bluetooth audio sink.
Was funny to hear the music and notification sounds come out of the laptop!
Also WLAN should now be stable for everybody.
I changed the kernel code over to the Asus code and more important fixed an issue with loading the WLAN firmware.
The latter might explain the different responses I got: from "not working at all", over "spotty, random disconnects" to "working fine".
Probably your mileage depended on the WLAN firmware installed by your previous ROM.
Well, please let me know, how it works for you now.
Thank you all for your feedback!
f69m said:
New update available!
Sorry, the camera is still broken... :crying:
BUT... Bluetooth is now working fine for me.
I don't own any real Bluetooth devices though. I tested using my laptop as a Bluetooth audio sink.
Was funny to hear the music and notification sounds come out of the laptop!
Also WLAN should now be stable for everybody.
I changed the kernel code over to the Asus code and more important fixed an issue with loading the WLAN firmware.
The latter might explain the different responses I got: from "not working at all", over "spotty, random disconnects" to "working fine".
Probably your mileage depended on the WLAN firmware installed by your previous ROM.
Well, please let me know, how it works for you now.
Thank you all for your feedback!
Click to expand...
Click to collapse
I'll give it a run later tonight
Sent from my Galaxy Nexus using Tapatalk 2
Hmm, 10 downloads and no one speaking up so far...
I take that as a good sign!
More good news: we got WLAN working on TF300TG too.
There are still issues with sound though.
Is there any developer with a TF300TL around? Would be great to cover the lot!
Currently updating my Ubuntu Touch port to the new code for BL 4.2.
Apart from getting some work done on UT, I hope that using Ubuntu, I might gain another view on the camera issue.
It's so frustrating: everything between the Android camera HAL and the kernel is a black box. No documentation and no source code.
Just some error messages in logcat and some in dmesg... but why?
Sent from my TF300T using Tapatalk HD
[#Intro]
Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.
[#Why]
[#Info]
I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use 4G LTE (or mobile data in general really) as much as you; you get the idea.
[#HowTo]
Latest BuildKitKat/Stable: N/A
KitKat/Beta: omni-4.4.4-20141015-toroplus-FML.zip (162.13 MB)
Lollipop/Beta: FML-AOSP-5.0-20150108-toroplus.zip (195.53 MB)
LOLLIPOP INFO:
USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
They are based on PA's GApps, huge thank you to them!
Known Issues
- Camera can be a little touchy, but it generally works.
Lollipop Changelogs can be found in the post below!
(KitKat) BETA INFO:
Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
Currently broken with the new GPU drivers:
- Hardware Video Decoding FIXED 2014/10/06
- Hardware Video Encoding(?) FIXED 2014/10/08
- Camera (PARTIALLY) FIXED 2014/10/08
- The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
See the Changelog post below for..... well..... changelogs.
[#GApps]
Known Issues- The screenrecord command does not work directly, however it does work via the Power menu.
- There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.
[#Thanks]
[#Donations]
XDA:DevDB Information
FML: Fork My Life, ROM for the Samsung Galaxy Nexus
Contributors
MWisBest
Source Code: https://github.com/MWisBest/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2015-01-08
Created 2014-10-13
Last Updated 2015-01-08
Changelog, News, Etc.
Lollipop Beta Changelogs:
- Updated the camera HAL.
This is going to be a little... fragile, at first, but in the long run it's needed. Stock camera app saves pictures now at least.
You may also notice that there's a 5.1MP resolution now (clear your camera app's data if you don't see it), despite our camera supposedly being 5.0MP all these years. Turns out the sensor's native resolution is indeed a whopping 16 pixels taller and 16 pixels wider than we've been using.
2015/01/04
- Added back some of the classic FML optimizations and more.
Built with -fstrict-aliasing flag, C++11, and the Linaro GCC 4.9 toolchain.
- Updated to AOSP "android-5.0.2_r1" tag.
As usual, the only real change was them bumping the version number.
- Improved flashing.
The speed of flashing the ROM zip is now much faster.
- Superuser is now built-in.
There's no need to flash SuperSU. You can find Superuser in the Settings app. You may have to enable the "Development Settings" menu to see it.
Some apps are a little sketchy with this Superuser though, most notably Titanium Backup. If you have issues, try flashing SuperSU.
- Video playback should be fixed.
YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
- The camera situation has improved and also regressed.
The stock camera is kinda back to the point of where it was with the KitKat Beta builds:
---- Preview works. Saving photos does not work. Video recording kinda works.
--- However:
---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
- Audio quality is improved, with support for 192kHz FLAC as well.
This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones. It also has far better quality than the stock Android resamplers.
- WiiMotes can now be paired via Bluetooth.
I used to be a bit of a Wii hacking enthusiast... I think I still need to add some more stuff to make it useable as a gamepad or something, but yeah.
- Fixed location services issues.
- (toro) Fixed switching between 4G/LTE and 3G/CDMA network settings.
- Kernel changes:
Reclaimed 38MB of RAM from the carveout stuff.
Removed HDMI's framebuffer, saving an additional ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old HWComposer, so might as well save some RAM in the mean time.
Added overclocking support, as well as adjusted the stock frequencies a little.
Added the GPU kernel driver back into the kernel, rather than building it as a separate module.
Switched to LZO compression for the kernel. It results in a slightly larger size to the kernel, but it boots faster.
Added the "purple tint fix".
Added compiler flag to tune code for Cortex-A9 CPU.
Built with Linaro GCC 4.9 toolchain.
Older Builds:
2014/11/16
- Fixed the RIL.
(I think, still unsure of toroplus's status.)
There were a few things that went into this, and I can't really take much credit for it other than being persistent in trying to fix it.
1. rild needed a little fix-up to somewhat return it to pre-Lollipop form. Basically Google is forcing Qualcomm's junk upon the world. @dhiru1602 pointed me in the direction of some commits from rmcc to hardware/ril that fixed this part of the problem.
2. The kernel needed a commit to support some new junk related to networking in Lollipop. @Ziyan linked me to the change in question.
- Updated to AOSP "android-5.0.0_r6" tag.
Really the only change is that the build number is bumped to LRX21T.
- Switched out a couple small proprietary binaries with a reverse-engineered open-source version.
Thanks to @stargo who has really been killin' it for the Motorola OMAP devices recently, we now have a reverse-engineered pvrsrvinit binary (the executable that fires up the GPU drivers on boot-up). This is especially important because the proprietary pvrsrvinit wasn't compiled as PIE (position-independent executable). With Lollipop, they're forcing everything to be PIE, which is good because PIE is better from a security stand-point. Previously I had been adding a workaround to enable support for non-PIE, which I now don't need.
2014/11/11
- Switched back to the old OTA package format.
With Lollipop they're now, by default, flashing something similar to a system.img. I switched back to the old format. THIS IS CAUSING VERY LENGTHY FLASH TIMES NOW HOWEVER, I HOPE TO FIX THESE SOON.
- Changed the kernel to build with GCC 4.7.
With Lollipop, Google switched to GCC 4.8. GCC 4.8 has never been kind to the Galaxy Nexus kernel, I'm surprised it was booting at all in the first place.
- Added "Ambient Display".
Apparently I need to add a "pick-up" or "significant motion" sensor for it though, so it displays something when the phone is picked up.
- Fixed chromium crashing.
This fixes Browser crashing upon open, among other things. This fix has been in chromium itself for nearly 4 months now, I don't know what the heck Google is doing to AOSP to make it so FUBAR lately...
- Fixed lag in Recents menu.
Now it's smoother than KitKat's, in my opinion.
- Added back F2FS support.
F2FS is now supported again, HOWEVER, it is NOT supported on the /system partition. It really didn't do any good for /system anyway.
- Updated various icons.
The Dialer icon in particular was bothering me. Other things that aren't visible in the launcher, e.g. SettingsProvider, have been fixed as well.
- Fixed FLAC playback, among other media decoding issues.
Just needed a sync-up in the device tree with one thing that I think Google DID do a nice job of with Lollipop actually.
- Built the ROM with "WITH_DEXPREOPT := true" defined.
This basically has all the system apps compiled before flashing, to cut down on the initial boot-up time which is ridiculously long with ART.
- Changed the "Android is upgrading..." screen to prevent burn-in.
Instead of using the white Lollipop-like look, it now should show up as the old, darker theme.
KitKat Beta Changelogs:
2014/10/15
- Cleaned up the kernel.
Ziyan went over all his work not long ago and cleaned up the commit history and whatnot. He's letting me do the task of merging in the GPU driver stuff, so I'm currently just getting the kernel to a "clean slate" of sorts for other kernel devs to fork and build off of. Basically this should hopefully be the new "stock" or "Google" kernel. As a result, there's some bells and whistles missing from this build. It does however include some new audio updates that weren't in the previous kernel, which leads me to this...
- Changed audio sampling rate to 48kHz.
Previously the sampling rate has been 44.1kHz. The Galaxy Nexus supports 48kHz though! Here's what mainly sparked this change: since KitKat, the UI audio effects (e.x. touch sounds) have been switching over to 48kHz. With the Galaxy Nexus still using 44.1kHz, UI sound playback became kinda sluggish, and this was a big contributor to it. The UI sounds use the "fast track" audio path (where it tries to do as little processing as it can to the audio in order to play it with a minimum amount of latency), however a requirement of using this is that no resampling (e.g. converting 48kHz to 44.1kHz, like it has been doing currently with KitKat) can be required on the audio being played. Therefore the UI sounds were taking the "deep buffer" audio path, which has a delay to it. In switching to 48kHz, the "fast track" path is actually even faster now than it has ever been previously, and the Galaxy Nexus was already TOP OF THE LINE when it comes to audio latency believe it or not!
Another thing about this is that there is now support for playback of 96kHz audio files.
- Some updates to the camera HAL.
This hasn't fixed the situation of stock and stock-based camera apps crashing when taking a picture, but it's a start on it though.
NOTICE: Poweramp (and probably most other media players that use their own native code for audio playback rather than straight-up using the built-in Android APIs) is being pissy about the sampling rate change. If you experience issues with music playing, especially things like popping or crackling, please try Play Music or Apollo and see if your issue is still present. I know the UIs for Play Music and Apollo are pretty awful, but I can't write my own media player because I'm dealing with this camera stuff!
KitKat Stable Changelogs:
N/A
Reserved
Reserved.
Reserved
Reserved.
Finally got FML up for you toroplus guys! Sorry for the long delay.
Awesome...thank you very much MW!!!!!
Wonderful
Currently uploading this to my server and will seed until a stable version is uploaded, then I will replace it. Thank you so much for bringing life into an otherwise fading device. :crying:
Donation sent.
Downloading. Will be my second rom I try;
Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.
BennyDS said:
Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.
Click to expand...
Click to collapse
Maguro Build is Here.
I've always wondered about this rom as I saw it on the toro thread... will give it a whirl
MWisBest said:
Finally got FML up for you toroplus guys! Sorry for the long delay.
Click to expand...
Click to collapse
Running good so far! I dirty-flashed over the official Omni build I've been running. No problems to report outside of the expected camera weirdness. Play Store camera apps are all over the map in their behavior - CameraZoomFX works perfectly as you reported, Google Camera crashes like the stock camera, Focal doesn't have any display at all. Video recording works but the audio is a bit out of sync, playback is a little choppy on the phone but is smoother on my computer. VideoCam Illusion (which does its own video encoding via software) does not work at all. Video hangouts seem to work fine.
Also, I used the torch quite a bit today, and at one point it quit working and I had to reboot to get it back. It's a bit early to tell, but I'm suspicious that this ROM is affected by the same 'Camera quits working' bug as Ziyan's 'stable' OMAP kernel.
Anyway, thanks again for your amazing work!
I had the same Torch issue as stated above, fixed with a reboot. Im currently running on Ting/ a Sprint MVNO and they are known for having APN issues with 4.4.x roms. When switching to LTE in the settings, the dialer app would crash loop until I switched back to 3g/2g. Flashing an APN zip on their forum fixed the crashing, but havent been able to tell if 4g actually connects as its pretty shotty coverage in my area. But I thought Id share incase someone else is on Ting.
---------- Post added at 05:15 PM ---------- Previous post was at 05:04 PM ----------
Coming from CM 11 I guess I have been lucky as far as not having to do my own work as far as updating the Sprint Profile, and PRL as it was still within the system settings. I have been unable to figure out how to update Profile/PRL on my own as of yet. Any chance one of you may want to share this info? I'd greatly appreciate it.
New build is up.
The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.
bloopblah said:
The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.
Click to expand...
Click to collapse
1. Root works here on FML. THe official build of OmniROM does not include superuser, you need to flash it yourself from recovery.
2. That's been a longstanding bug with Omni on toroplus for some reason.
3. There's no 20141014 build of FML for toroplus - are you using the Omni official build?
4. That's turned off by default - Settings/Bars/Activity Indicators.
Alright, another new build to try out! I will have a couple of ROMs to try on my GNex which is a good thing!
@MWisBest...hopefully you get some donations coming in as well as Musical_Chairs since you guys are putting time and effort into providing new goodies for us.
Hopefully you get some $$$ coming in. It's going to be about a week for me to donate. One thing people don't realize is that donations don't exactly flood in for devs. I released 4 Venum Ice ET4G ROMs and 2 fully inverted black and white Note 2 ROMs including icons, all inverted apps etc. I actually got over 1000 downloads on all 6 ROMs within the first 24 hours and had excellent feedback.... I received a total of 3 donations totaling $12! Lol. What you guys are doing is harder so hopefully some people who are still here show you guys some love for not making this a thread that got closed for inactivity.... Thanks again to both of you.
Sent from my Knox-Blocked P.O.S Tab 3 running same hardware as my GNex using Xparent Gray Tapatalk 2
Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.
cr08 said:
Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.
Click to expand...
Click to collapse
That's the same issue as the torch issue mentioned above. It's a hard bug to track down because it takes so long to show up, and AFAIK nobody has found a reliable way to trigger it (other than just wait a day or two for it to show up). If somebody can figure out how to trigger it more quickly, I would like to try a git bisect on Ziyan's stable OMAP kernel (which is affected by the same bug) and see if I can pinpoint what is actually causing it. But without a reliable way to tell if a particular test kernel is good or not, a bisect is more or less useless.
Hi guys. How are you? I'm fantastic right now:
EDIT: Let me fix that a little...
A few years ago, I have been building Mackay ROM, based on CyanogenMod for a number of devices. Due to being busy at work, I have stopped with that. I recently picked it up with again with a Mackay ROM based on LineageOS.
It is actually LineageOS, with a few extras that I always miss:
-SU build into the ROM
-No hash sign when using SU
-Network traffic speed option for statusbar
-OMS Substratum theming
-OmniClock in stead of Lineage Desk Clock
The bootanimation is made by my brother. It is the family coat of arms of the Scottish Mackay clan to which my family is linked.
I try to build this ROM on a weekly basis, but it mainly depends on when interesting features are available/merged
Download:
AndroidFileHost
Installation:
-Make sure you have recent TWRP installed (3.2.1-1)
-Make sure you have recent hardware blobs from MIUI (minimum 8.1.4)
-gapps can only be flashed on clean installs
-clean install (factory reset) if coming from another ROM, dirty flash if updating
I am open to suggestions for additions, but I prefer a clean ROM, just some basic extras over stock LineageOS has always been my approach for Mackay ROMs.
Credits:
This ROM would never have been possible without the hard work of bgcngm to make LineageOS for our mi5 and the other LineageOS developers.
Source:
ROM: https://github.com/LineageOS
Kernel: https://github.com/kasperhettinga/android_kernel_xiaomi_msm8996
XDA:DevDB Information
Mackay ROM, ROM for the Xiaomi Mi 5
Contributors
kasper_h
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Beta
Created 2017-04-26
Last Updated 2018-04-02
Reserved
Hi, has your Mi5 experience random mobile signal drop? LTE signal drop?
Has this issue been resolved in this ROM? Thank you!
lenra06 said:
Hi, has your Mi5 experience random mobile signal drop? LTE signal drop?
Has this issue been resolved in this ROM? Thank you!
Click to expand...
Click to collapse
I don't use LTE, so I can't say for sure. In general, because this ROM follows LineageOS, it will have to deal with the same problems as well.
kasper_h said:
I don't use LTE, so I can't say for sure. In general, because this ROM follows LineageOS, it will have to deal with the same problems as well.
Click to expand...
Click to collapse
Thanks! Following up, any mobile or data signal drops encountered?
lenra06 said:
Thanks! Following up, any mobile or data signal drops encountered?
Click to expand...
Click to collapse
I use it myself in dual-SIM mode and never encounter any signal loss.
hi and thanks for this first of all. I'm surely going to try it, even just for seeing the bootanimation..i love all that matters Scotland.. your country and national anthem, rugby, braveheart etc
personally i don't use LOS for a very few and not so intrusive things i think. first of all date in status bar, like in most all other los roms. could you add it? don't think it would be too intrusive, but it is a real deal breaker for me
other thing i look for is multiple actions for HW buttons (like in RR.. show volume panel, show quick settings panel etc and not only the los standard ones) but that's secondary as i can also use a hw button remapper app for that
ah, and dt2s everywhere in lock screen would be great also!
bye will report after trying your rom!
@kasper_h wow! that is THE surprise. For the young ones in the community, Mackey kernel/rom was the goto option for our Galaxy S(1) ! Glad to have you in this part of the forum. Are you planning on getting involved with the Mi5 kernel business as well?
tested the rom quicky. enabled root in Dev settings for apps but couldn't get root access for mixplorer?
@kasper_h perhaps adding QC3 fix from this commit?
ngoralph said:
@kasper_h perhaps adding QC3 fix from this commit?
Click to expand...
Click to collapse
Thanks, I'll do a build today with that commit to see if it fixes erratic charging behaviour!
georgekav33 said:
@kasper_h wow! that is THE surprise. For the young ones in the community, Mackey kernel/rom was the goto option for our Galaxy S(1) ! Glad to have you in this part of the forum. Are you planning on getting involved with the Mi5 kernel business as well?
Click to expand...
Click to collapse
I still have my S1 lying around, but stopped developing for it long time ago.
At the moment, I first want a robust ROM being build, then I'll look into the kernel as well. On S1, performance depended a lot on the kernel, I haven't seen such spectacular results on mi5 yet.
FcukBloat said:
hi and thanks for this first of all. I'm surely going to try it, even just for seeing the bootanimation..i love all that matters Scotland.. your country and national anthem, rugby, braveheart etc
personally i don't use LOS for a very few and not so intrusive things i think. first of all date in status bar, like in most all other los roms. could you add it? don't think it would be too intrusive, but it is a real deal breaker for me
other thing i look for is multiple actions for HW buttons (like in RR.. show volume panel, show quick settings panel etc and not only the los standard ones) but that's secondary as i can also use a hw button remapper app for that
ah, and dt2s everywhere in lock screen would be great also!
bye will report after trying your rom!
Click to expand...
Click to collapse
Date in statusbar is something I may look into. I actually use the calendar status pro widget, which also gives day of month in the status bar. May other apps can do the same as far as I know.
Remapping HW buttons is not something I'm interested in
kasper_h said:
I still have my S1 lying around, but stopped developing for it long time ago.
At the moment, I first want a robust ROM being build, then I'll look into the kernel as well. On S1, performance depended a lot on the kernel, I haven't seen such spectacular results on mi5 yet.
Click to expand...
Click to collapse
That's true, kernels are more mature now, performance-wise we may not win much (save it for the 32GB Mi5 with mild OC to 2.15Ghz). However, I think that due to Xiaomi's not 'fully' functional sources, there is space for improving the functionality aka charging speed, sound quality, maybe EAS or interactive governor tuning etc. Your expertise on kernel modding would be valuable to this community as well!! thanks
kasper_h said:
Date in statusbar is something I may look into. I actually use the calendar status pro widget, which also gives day of month in the status bar. May other apps can do the same as far as I know.
Remapping HW buttons is not something I'm interested in
Click to expand...
Click to collapse
thanks for the answer! yes I'm using an app right now to visualize the date in status bar in jdc's aosp, but i don't like so much having to use an app just for that
kasper_h said:
Thanks, I'll do a build today with that commit to see if it fixes erratic charging behaviour!
Click to expand...
Click to collapse
OK, so here is a build with the QC3 patch and today's Lineage codebase. Also includes upstream OMS substratum patches:
https://www.androidfilehost.com/?fid=457095661767156880
Seems to work fine for me, will monitor charging speed in coming days.
it seems meanwhile miui released updated kernel sources with working QC code...! :victory:
FcukBloat said:
it seems meanwhile miui released updated kernel sources with working QC code...! :victory:
Click to expand...
Click to collapse
But the version now in the making for LOS still seems to suffer from problems. The latest build I posted few days ago does work with QC.
What a great surprise to see you around here! Another one who was following your work on the i9000. Great times and marvelous phone :') Hope to see more from you for the mi5, for sure trying out this, although RR is my comfort zone since november when i got the phone, hard to beat that loyalty on a phone of mine
Thank you for kasper_h for the old, present and future work!
kasper_h said:
But the version now in the making for LOS still seems to suffer from problems. The latest build I posted few days ago does work with QC.
Click to expand...
Click to collapse
thanks but I can't use this rom for the reasons i poster earlier, so I'm sticking with RR for now. i am trying the boot.img from your rom in RR though, let's see if it fixes QC in RR too for sure it did boot and everything seems to work, so already better than i thought!
Info:
Target Device: SM-T560NU only (gtelwifiue)
OS: Android 6.0.1 Marshmallow
Variant: LineageOS 13.0
Status: Usable as daily driver, but still to be considered experimental
This project is a side project of mine to bring Lineage 13.0 back to the SM-T560NU.
I recently purchased one of these, and use a few apps that have not been updated in years. These apps do not work on Nougat, therefore I needed Marshmallow.
vince2678 had a great Lineage 13.0 build, but had started to shift his efforts towards the more popular and updated Android Nougat by the time that I got this tablet. vince had started to warn that he was going to be dropping Marshmallow to focus on Nougat.
Therefore, using his code base, and attempting to apply some more modern patches to keep Lineage 13.0 up to date, I started creating my own builds in private. There was one single, obsecure link to it, on my website, and it was discovered. Since the community has shown interest in this project, and vince has now officially dropped support for 13.0, I am willing to release my private builds.
Please keep in mind that while vince's builds were designed to be as stock as possible, my builds are tailored towards my needs.
They are not perfect, but they work for me. There are still some issues to be ironed out, and sometimes new issues sneak in when you think you are just building a security update
But, since you wanted them, here they are. At the time of this post there is only one, but this will grow over time, when I have spare time to try to fix any issues and apply security updates.
All builds use my optimized kernel.
Releases and known issues:
You can find my builds over at:
https://losupd.zefie.net/builds/full/?C=M;O=D
lineage-13.0_j199_20170720
Android Security Patch Level: July 1, 2017
USB MIDI Support (example video of controlling Logic Pro X with the SM-T560NU)
No changes to previous issues in this build (same issues apply)
lineage-13.0_j196_20170617
Android Security Patch Level: June 1, 2017
AudioFX is missing (disabled in build due to unsolved issue in ROM causing crashes)
Updater is untested. You may or may not get a notification when a new build is available.
Flashing the recovery that comes with these builds is advised against. It may work but is untested. Use my TWRP Build.
Device encryption does not yet work
There is a strange issue that prevents you from taking still images using the built-in camera app. Preview and video works. As a workaround, use any third party camera app. I suggest Open Camera.
Just flashed it, everything works great so far.
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Solidium said:
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Click to expand...
Click to collapse
I knew about the encryption but the camera issue is interesting and strange. I just tried it and see what you mean.
I will see what I can do about these issues in the next update, which will probably be mid-august.
Thanks for the report.
The issue seems to be with the Camera app itself, and not any issues with communicating with the hardware (despite the error message), since other camera apps appear to work fine.
In the mean time, if you would like to take still images with this build, I would suggest this great and free (ad free as well) camera app from the play store:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
I have just tested it (with both rear and front cameras) and it can take still images.
560?
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
bluedesire said:
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
Click to expand...
Click to collapse
This is for the T560NU only, not T560. From what I know they have entirely different processors so there is no way for a universal ROM.
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
jon355 said:
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
Click to expand...
Click to collapse
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Any progress on Audio FX and Camera issues?
Jacsd said:
Any progress on Audio FX and Camera issues?
Click to expand...
Click to collapse
Unfortunately I have not had the time to work on this in a while. When I don't have time I just update the source and build (and hope it works) for the security updates. This only takes a couple of minutes as the build process does all the work. One should be coming in the next few weeks. Once the automated build finishes, I test it locally for about an hour and if its good, I release it.
I am not sure when I will have time to actually sit and go through the code to try to debug it to fix the outstanding issues. This can take hours or even days of dedicated time which I just don't have at the moment due to trying to keep my bills paid.
Stay tuned to this thread for updates though, and I apologize for the delay.
zefie said:
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Click to expand...
Click to collapse
After uninstalling 3rd party music app, volume is good again.
EDIT:
Unfortunately I am discontinuing this ROM. I made this ROM for my personal use, and it is no longer useful to me, and I do not have the time to debug it. Therefore, I am discontinuing it. The current builds and source will remain up, and if you guys are not having the issues I am having, and would like me to continue doing security updates, I will, so long as it still compiles without much work on my part.
There will be no updates to the existing issues though.
Despite my previous aversion to Android N, I would highly suggest vince's Lineage OS 14.1 builds. They have come a long way since I last tried them, and Android N isn't so bad after all
I haven't gotten a chance to do a logcat or anything, but I'm getting an instant bootloop after installing Nova Launcher.
It wasn't an issue until Nova updated a few weeks ago, and it affects both your builds. That's my favorite launcher, but I guess I can live without it
EDIT: I see that you're discontinuing this, so I guess this post is more of an FYI to other users.
Hey! So, I've tried some AOSP ROMs and I encountered with the same problem in all of them. AOD, dt2w and pocket detection are BATTERY KILLERS. Specially AOD, because, when it's activated, the device doesn't enter into deep sleep.
Don't get me wrong, they work as they should, maybe pocket detection with better results in some ROMs than other.
You can easily say "Turn them off" and yeah, I disabled them and the battery drain is almost nothing, no matter what ROM I'm into.
But, I really like having AOD, enjoy my AMOLED panel and squeeze as much as I can, but not in behalf of HUGE battery drain.
And it sucks, because, in MIUI you can have them enabled and working with less battery draining, but I don't like MIUI like many of us here.
I use BBS app to check the draining, and there is Wakelock named PowerManage.SuspendLockout, that is always active when I have AOD enabled, to consider...
Is it related to Xiaomi not releasing the code or whatever is call, or some hardware issue, or maybe a poor ROM optimization?
Have you find any ROM where these features, specially AOD, are not battery killers?
PS: In every ROM I do a clean install, no backup restore, and almost 0% background apps consumption, so, no, it's no a setting or app related issue...
DotOS 5.12
I tested only 3 AOSP roms (crdroid, havoc and evoX) and they all have this issue. The MIUI didn't. I'm also wondering why that is and I would really like to use AOD. As you said, we have an AMOLED panel and not being able to use it fully kinda sucks no matter if is is just a gimmick. Not sure if it's a kernel issue or a rom issue but it definitely isn't a hardware issue since it's working without flaws on MIUI. Would be great to hear from some rom maintainers about this.
Can someone confirm if it's really working with deep sleep on DotOS? I won't flash it, even if that's true but maybe the maintainer can share the fix with the other roms?
REDOTHELLO said:
DotOS 5.12
Click to expand...
Click to collapse
Have you tried? Does this ROM solve this issue?
I am not using AOD and pocket mode and dt2w is on statusbar DotOS use pixel launcher
REDOTHELLO said:
I am not using AOD and pocket mode and dt2w is on statusbar DotOS use pixel launcher
Click to expand...
Click to collapse
So, how can you recommend the ROM if you are not using what I need? xD
Oxnap said:
So, how can you recommend the ROM if you are not using what I need? xD
Click to expand...
Click to collapse
I tried so many kernels and specific fixes that claims to fix the issue all ended up in failure, like you I love to have AOD but not at the expense of huge battery loss.
Just my opinion. I think there is nothing we can do about the battery. Its a hardware/quality issue. I mean, the battery of poco f3/mi 11x is not good as you see from other giant brand like samsung.
maybe we need a special Kernel for the best result between AOD and Battery
I did a clean flash of my own Lineage rom as something got screwed while trying fixes for AOD, this is a week ago, brightness was being reset to lowest on each wake up.
So, I decided to try AOD just now to see if it works, and it does!
For the first time the cpu goes to deep sleep even though AOD is switched on.
I have built and flashed no less than 80 builds, It pays to do a clean flash once all source code have settled.
This is the Commit that I believe fixed the issue:
alioth: Enable config_powerDecoupleAutoSuspendModeFromDisplay · AliothDevelopment/[email protected]
Contribute to AliothDevelopment/android_device_xiaomi_alioth development by creating an account on GitHub.
github.com
As I said above, I dirty flashed with the commit above and still with AOD on no sleep, so only after a clean flash it is working perfectly, Clean flashing is important if you have flashed many builds with many changes in the Kernel/device trees.
cheers
-GREY said:
Just my opinion. I think there is nothing we can do about the battery. Its a hardware/quality issue. I mean, the battery of poco f3/mi 11x is not good as you see from other giant brand like samsung.
Click to expand...
Click to collapse
You trolling, for sure. My battery is great, better or the same as s21++++
LiNe1771 said:
You trolling, for sure. My battery is great, better or the same as s21++++
Click to expand...
Click to collapse
I could not agree more, I never get less than 10 hours SOD, usually I charge my phone once every 50 hours. Best battery on a Smart phone I have ever had.
Barracuda77777 said:
I did a clean flash of my own Lineage rom as something got screwed while trying fixes for AOD, this is a week ago, brightness was being reset to lowest on each wake up.
So, I decided to try AOD just now to see if it works, and it does!
For the first time the cpu goes to deep sleep even though AOD is switched on.
I have built and flashed no less than 80 builds, It pays to do a clean flash once all source code have settled.
This is the Commit that I believe fixed the issue:
alioth: Enable config_powerDecoupleAutoSuspendModeFromDisplay · AliothDevelopment/[email protected]
Contribute to AliothDevelopment/android_device_xiaomi_alioth development by creating an account on GitHub.
github.com
As I said above, I dirty flashed with the commit above and still with AOD on no sleep, so only after a clean flash it is working perfectly, Clean flashing is important if you have flashed many builds with many changes in the Kernel/device trees.
cheers
Click to expand...
Click to collapse
Cool, did you make your own LOS ROM?
Oxnap said:
Cool, did you make your own LOS ROM?
Click to expand...
Click to collapse
Yes, I have been since i got the phone more than two month ago.
I am an open source advocate/fanatic
Barracuda77777 said:
Yes, I have been since i got the phone more than two month ago.
I am an open source advocate/fanatic
Click to expand...
Click to collapse
Why don't you start your own ROM thread? Maybe I could help you on testing
Oxnap said:
Why don't you start your own ROM thread? Maybe I could help you on testing
Click to expand...
Click to collapse
I am not sure many would like the fact that mine runs on MicroG, I have many of the apps that usually comes with the ROM taken out and replaced with other better open source alternatives.
Gallery, messages, music to name a few
As I am 100% self dependent on my services, I don't rely on anyone else:
I run and maintain. The following services:
1) XMPP secure and fully encrypted chat server (prosody) for family and friends)
2) run my own VPN server when out of the house.
3) run my own email servers since 2008
4) Run my own password manager server (Bitwarden)
5) run Synching server to keep all my Linux servers, Linus PCs and Android Live Backed up.
6) Run my Own Cloud Server ( NextCloud)
7) My own Music personal server I use Gelli (open Source) to listen.
8) my own open source router (pfsense)
9) my own DNS server ( Pihole )
I also build most of the apps I use :-]
Everyone needs differ than others, my sources for building my ROM are here, feel free to download, use or fork.
barracuda777 - Repositories
barracuda777 has 116 repositories available. Follow their code on GitHub.
github.com
Happy building.