Deleted
ffboy2009 said:
Hi all
Here is a twrp-3.0.2 for our device that support f2fs
this recovery is just released for the next cm or mokee build which support f2fs and sdcardfs features
you can search the forum to know how to convert partitions to f2fs file system
And next release of cm & mokee will use brand new source compiled kernel that updated with CAF LA.HB.1.3.2-29100-8x96.0
the cm14 with android 7.1 also in progress
Thanks
Link: https://pan.baidu.com/s/1pKYpIXl password: 98ju
Click to expand...
Click to collapse
thank you! what does f2fs do? also are you working on the miui 8 with manosp as well to bring a cleaner version of miui to the phone?
Installed recovery. If i understand you correctly, we can not convert now to f2fs because current cm/mokee builds doesn't support it?
Sent from my Le X820 using Tapatalk
this is good news... cant wait for Android N
better than the official twrp, thank you.
xterminater07 said:
thank you! what does f2fs do? also are you working on the miui 8 with manosp as well to bring a cleaner version of miui to the phone?
Click to expand...
Click to collapse
Without googling, I believe it speeds up read/write speeds
meangreenie said:
Without googling, I believe it speeds up read/write speeds
Click to expand...
Click to collapse
it actually saids 20% slower than ext4 when I googled it
I have submitted a change to twrp gerrit so the official one can support it even though i think its stupid for our device due to the UFS storage chip we have there will be almost no performance gain.
Is that cm 14 nougat for le max 2
Sent from my Le X820 using Tapatalk
xterminater07 said:
thank you! what does f2fs do? also are you working on the miui 8 with manosp as well to bring a cleaner version of miui to the phone?
Click to expand...
Click to collapse
F2FS is 'flash oriented' while ext3/4 offer 'flash support' with newer kernels. Actually my enthusiasm for it has waned a bit, since I have run both side by side on rather similar Android tablets, one an Asus transformer TF100, the other an Acer Ionia 500, both Tegra 2 devices several years old with 32GB flash each.
The Asus uses ext3, the Acer f2fs, and the Asus beats the Acer into a pulp. I do trim storage religiously on the Asus, something you don't need to do on F2FS and I also believe the Asus Flash has been higher quality for starters.
What I also noticed on another Asus Nexus 7 (2012) device, is that somewhat counterintuitively you shouldn't use the ext4 journal on stupid and slow Flash, such as what's built into the Nexus 7.
LeMax2 uses a smart UFS controller, so in theory the details of the underlying hardware are actually hidden from F2FS, which likely means it cannot exploit its 'knowledge' of the flash hardware (e.g. erase block size vs. block size) to auto-trim-on-write, so in fact it may be detrimental long term. There is a whole indirection layer F2FS cannot punch through.
I'd recommend playing it safe with ext3/4 but I'd welcome any comparative benchmark and reliability data anyone wants to produce.
ffboy2009 said:
Hi all
Here is a twrp-3.0.2 for our device that support f2fs
this recovery is just released for the next cm or mokee build which support f2fs and sdcardfs features
you can search the forum to know how to convert partitions to f2fs file system
And next release of cm & mokee will use brand new source compiled kernel that updated with CAF LA.HB.1.3.2-29100-8x96.0
the cm14 with android 7.1 also in progress
Thanks
Link: https://pan.baidu.com/s/1pKYpIXl password: 98ju
Click to expand...
Click to collapse
I assume that changes haven't been merged yet since there is no trace of them in the changelog of mokee's nightly releases. Am I right?
Also, what exactly does it mean that the new kernel is going to be updated with CAF LA.HB.1.3.2-29100-8x96.0?
So where are your sources? You'd rather delete your mokee thread than publish kernel sources that are REQUIRED by GPL? Pretty shady practice there buddy. How about it @ffboy2009
Thread cleaned. Pleace keep it nice and friendly.
Whiskey
Forum Moderator
Which roms has suport for f2fs?
Related
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
STATS: 500+ kernel downloads in 2 days, wow!
RELATED: Make sure you check out my TRIM-enabled kernels updated with the FPBug fix.
UPDATE: A fix for FPBug has been merged into CyanogenMod's cm-11.0 branch! The fix has not made it to the stable/cm-11.0 and cm-12.0 branches yet. Changes: this one and the previous 12. Commits: this one and the previous 12. The 20150111 nightlies are the first official CM 11 nightlies to incorporate the fix.
A little bit of history
As Android got more complex, the effects of this bug grew more visible, to the point of making the platform completely unstable for some users. Complex apps would fail for no reason, GSM, 3G and WiFi connectivity would randomly be lost, music playback would stop and require a reboot, camera would fail, internal storage and SD cards would become inaccessible, installed apps would disappear, users would experience battery drain issues ranging from inability to enter deep sleep all the way to phones becoming very hot, and the list goes on and on.
These failures all seemed unrelated and their cause was very hard to track down. Partly because events happened randomly and were not reproducible, but mostly because the bug undermines the very assumptions programmers deal with when creating any kind of code. And so years passed and the common cause of all this pain was never identified. Many ROM developers abandoned the platform out of frustration.
Then finally this past March, when analyzing the random loss of access to storage, user cgx observed a corruption event for the first time, and a connection between all these unrelated issues, sometimes hypothesized, was suddenly found. The corruption seemed to have happened in the stack, but it was later suspected then confirmed that the corruption actually happened directly in the registers of the floating point unit of the CPU. Yet processes that did not use floating point at all were also affected, because the GCC compiler typically spills registers into the FPU and uses FP and NEON instructions for optimization.
These findings allowed the creation of a stopgap fix for the "music bug" that shielded the FUSE process (which manages access to storage) from corruption in the FPU. The fix was widely applied and effectively eliminated all bugs resulting from sudden loss of storage access and returned the platform to pre-Android 4.3 stability levels: ie, sort of stable enough to be used as a daily driver. Later a working detector for the elusive bug was made and it was confirmed that all kernels since Gingerbread were affected (a thing that was already suspected given that the FirefoxOS people had described similar symptoms in 2012 under stock Samsung ICS). Finally enough of a root cause was hypothesized and a fix was worked out. And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
A short description of what the fix does can be found here.
Update
User zeitferne worked non-stop throughout this weekend and made amazing progress. He found a couple of missing commits that are apparently needed for the FPU state tracking to work through power state changes, he discovered that the FPU in CPU0 is the one that actually gets the corruption, he found an explanation why this bug never affected the 4412 platform (Galaxy S3, Note 2, etc), he narrowed down the conditions for the corruption, and finally output an alternative patchset that apparently fixes the FPU state restore optimization rather than just disabling it as mine does.
Kernel developers are encouraged to merge his changes in lieu of mine once enough testing is done and @zeitferne green-lights the patches. This is important as it might fix as-of-yet undetected bugs or prevent bugs arising from future changes. In the meantime, eager maintainers can merge my fix which is by now well tested. Users will only see a small (<< 1% ?) performance increase with zeitferne's patchset and don't really need to bother with this; my advice for them would be to wait for the changes to trickle into their kernel of choice. AMAZING JOB ZEI!!!
2nd UPDATE: @zeitferne has green-lit his patchset! Kernel maintainers merging it please take note: 1) Make sure my fix is removed before applying his, otherwise there will be a small performance hit in the resulting kernel. 2) Both our fixes also affect the 4412 platform (i9300, n7100, etc) in slightly different ways, and the effects of this have not been properly tested. I must recommend that some testing be done before distributing FPBug-fixed 4412 kernels. Please report your test results back to this thread.
WARNING: A problem was reported with zeitferne's patchset.
FOLLOW UP: @zeitferne made some changes to his patchset and initial testing looks good.
AND FINALLY: The patchset was merged into cm-11.0! (See this change and the 12 previous ones.)
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here. These kernels are guaranteed to work only with the exact matching version of CM specified in the last part of their filenames. But in reality they should work with most versions of CM that are close enough. (Don't ask me about this, I don't know, I don't even have any of these phones! Just try them and see for yourself if you are feeling a little adventurous.) For other ROMs i expect this fix to be merged in a matter of days after some more testing is done. Please be patient, and KitKat users can flash my music bug fix in the meantime.
FAQ
Q. I have flashed your music bug fix in the past. Can I flash your kernel?
A. Yes! The music bug fix has no downsides. In fact, as a side effect, that fix makes your phone slightly faster and saves some battery so it should be merged in all ROMs IMHO. If you already have it installed leave it in place, but do not flash it again the next time you upgrade the OS. Please do not flash it just for the sake of optimization: since it is based on CM11 M10, it would actually be a downgrade.
XDA:DevDB Information
FPBug-i9100, Kernel for the Samsung Galaxy S II
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2015-01-14
(reserved)
Is the BLN included ?
Lanchon said:
And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
Click to expand...
Click to collapse
It's not about i9100 ? Right ?
Can't wait till testing is complete and you merge the fix into your trim kernel for the i9100 lanchon. Thanks to all the programmers, testers and commenters in the bug thread for their hard work.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
yes, he refers to the i9100 and the n7000
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
these are all standard CM kernels. please request features on the CM thread.
Lanchon said:
yes, he refers to the i9100 and the n7000
Click to expand...
Click to collapse
Oh God ! Lollipop
I am anxious
@Lanchon thank you very much for ur hard work [emoji122] [emoji122] [emoji108]
Dammit... Never wanted to use CM again... I think I will have to at least for now until it gets integrated in other kernels
Great Job @Lanchon
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
so no bad battery life any more?
Vidura Dissanayake said:
so no bad battery life any more?
Click to expand...
Click to collapse
Yes exactly. With a little more testing a final version should be coming soon. What an awesome Christmas gift!
Thindboy said:
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
Click to expand...
Click to collapse
No it won't solve gps problems. I've had good luck using GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 and Faster GPS https://play.google.com/store/apps/details?id=org.fastergps from the Google play store. GPS status will download assistance data (A-GPS) and faster GPS setups the proper ntp server for your area. I get fixes in about 10 seconds now.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
Everything is somehow faster with this kernel. I flashed the music bug fix with this kernel. Waiting for trim kernel, it will further accelerate the phone.
I noticed that the phone is not heated as before.
You're a genius because you've done a lot for us, s2 community ... And we know that you do not own this legendary phone
Thank you @Lanchon
Sent from my GT-I9100 using Tapatalk
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
Cm12 is available?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
Waiting for your review for Spirit ROM once you've flashed it.
Lanchon said:
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
Click to expand...
Click to collapse
OK so FPBug-V1-src.zip is a flashable zip for fpbug fix for every rom stock jb and kk?And cm-11-M10-i9100-music-bug-fix.zip is for cm11 m10 only?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
x3dnd3x said:
Waiting for your review for Spirit ROM once you've flashed it.
Click to expand...
Click to collapse
Im on neatrom now ,will be on kk once a stable kk apolo kernel comes out!
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Mockingbird said:
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Click to expand...
Click to collapse
Lanchon bases his kernel on stock cm kernel, so cwm recovery is built in.
Its been more than a month since the kernel source for MIPAD has been released.Have been closely following xda and MIUI forums ,but haven't seen any development work being posted in any of them.
Do we have development work going on for MI PAD??
Last i heard was there was some issue with vendor blob , which was preventing an android upgrade.
Has that problem been solved?also i heard that for many devices emulation or wrapping is used when vendor blobs are not available...
Please let us know for development work so that we can also be able to contribute for the betterment of our device
It's not 2 ez as u think
Artemka2008 said:
It's not 2 ez as u think
Click to expand...
Click to collapse
I understand that,I am trying to develop from my side as well.
Highwaystar_ru has done great work in implementing CM 12.1 for mipad.Its in the beta mode but usable,its has some issues such as micro lags,camera,No sounds in certain apps such as go to meetings,Skype etc.
Just wish someone works on the kernel from source as the current CM 12.1 uses stock smoke kernel
Woah,kitkat in 2018? You got to be crazy!
Hello guys, you may have noticed my absence from the forums as of late. 2017 was a really busy year for me. I had some free time during the holidays, and i finally got to bringup up kitkat for the z7 max from scratch, something that was on my mind for a long time. I consider kitkat to be the pinnacle of android as far as UI, performance and efficiency go, and while i use oreo on my redmi note 4x, i object with what google has brought to the table since lollipop in all areas.
My build is not vanilla lineage11/cm11 sources, i have used pac-rom kitkat(best rom ever for me) sources as well and ported all features to lineage11(or rather backported all the security fixes to the pacrom frameworks), therefore the rom has all the customization one could need.
The device tree is a heavily tweaked(almost built from scratch) oneplus one tree with many drivers from the opo(like wifi and bluetooth) ported to our device.
Kernel is pure nubia nx505j kitkat kernel as released from ZTE with the addition of opo wifi prima driver and some fixes to get it to compile and restore features like native panel d2tw, vibrator strength control and keydisabler(thanks to paolow8). Antutu scores about 52000, but the phone feels insanely faster than the heavily customized cm12.1/cm13/nougat kernels and battery life is the best i have ever seen on the device. I may add some features like f2fs support in future as well as upstream it to the latest linux version(3.4.113).
Vendor blobs consist mostly of the latest from nubia 1.64 firmware(last kitkat version), some opo blobs from latest cos11, and some from the latest lollipop 3.89 version.
Without further ado, here is the folder with the rom, newly built recovery by me with decryption support(encryption works fine on the rom) and some camera apps to improve your camera experience(i like oppo cam best): https://mega.nz/#F!10RmSaAJ!NhWzzW_E9Wimxi_LG3KlKA
To install it , you don't have to downgrade to kitkat or anything, the rom has unified partition support, and works fine with the latest 3.89 baseband(may even add the installer to flash it in later builds). Wiping data, cache and system should do(if you come from official lollipop or any of the new roms with unified data partition). Keep in mind that f2fs is not supported yet, therefore you will have to format your data partition to ext4 if you use f2fs.
I built this rom for my usage, therefore since i plan to use xposed and microg, signature spoofing and xposed work out of the box. No need to workarounds, patchers, modules or anything. The (un)official installers work without hiccups.
For the crazy enough to use this rom, have as much fun as i did developing it. Things i have to test yet are 2 sims together(both sim slots work with mobile data, just didnt have a second sim to test them together) and sdcard(should work fine). Everything else is tested and works fine.
Special thanks to paolow8, a great dev and his sources were a huge help.
PS. I will get my sources up on github as soon as i can.
Thank you for your work!
thank you for your work too !
Thanks, this is the most complete 4.4.4 Z7 Max ROM ever.
Are there any roms or custome recoveries for the ZTE Max Blue?
I agree 100% with you: 4.4.4 is state of the art. Questions: IR and screen trasmission works fine?
Edit: CHECK! Screen Trasmission works like a charm! IR says "not supported".
Thx's a lot, you have made an happy man
Edit 2: SDCARD don't work, for me. If you have a fix please share
Edit 3: For more precision: The unmountable partition is Ext Card.
While everything works perfectly (in recovery and in other ROMs) it is impossible to format or unmounting external card from Android-> Settings-> Storage.
The only flaw of an otherwise perfect ROM for me.
Is it a common problem? Did it happen to anyone? Please, if you have a fix share it
I need my settings to know what kind of phone I have
The SD card don't work! :crying:
SD card issue fixed, since it's been almost a year i got in touch with the friend to whom this phone was donated...
Just redownload and reinstall the rom, no wipes needed. It was a simple fix in the kernel ramdisk.
pchatzop said:
SD card issue fixed, since it's been almost a year i got in touch with the friend to whom this phone was donated...
Just redownload and reinstall the rom, no wipes needed. It was a simple fix in the kernel ramdisk.
Click to expand...
Click to collapse
Thx's a lot, pchat. I'm very grateful <3
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 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:
- Touchscreen failure (sometimes occurs, if touch works after reboot it will work till next reboot);
- Camera (both);
- Dock special keys (top row);
- GUI crashes; - occure less often
Currently, I'm only one from Unlegacy Team, who has TF 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.
Latest information about OREO builds can be found HERE.
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 Eee Pad Transformer Prime
Contributors
Clamor, Ziyan, Narkolai
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
TF201 users know well what is repartition. While flashing 4.2BL from HB internal storage is reformatted. This thing is exactly the same.
I worked on it for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY!
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 HB bootloader or Bootloader 4.2 attached in Downloads section.
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
MalibuKoKo said:
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
Click to expand...
Click to collapse
Actually you can't build fully working ROM from my source for now. If you would like to help in developing - PM me.
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
goosebickel said:
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
Click to expand...
Click to collapse
Based on latest 4.2 bootloader (like Hairybean). I'll provide a bootloader + new TWRP and separate TWRP as soon as I get a stable recovery build.
General Feedback
Finally got around to flashing your ROM a week ago, following your instructions, everything went fine. I installed your UA-bootloader and flashed _that16 kernel.
Running pretty smooth with Pico gapps installed, after a week, the usual happens, slow loading apps etc, but that is not the ROMs fault, the very slow memory that Asus put into it and Google is slowing it down with constant syncs etc.
Was wondering if you had added compatibility for using MicroG?
Thanks for keeping this old tablet going.
@goosebickel sorry for such a long silence. MicroG are supported as I can say (I installed them but didn't test much).
P.S. If you are still on UA rom there is an update.
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 from O for now. I know already about all major issues.
Thank you!
Great to see some development for the Transformer Prime
I have some good news. Here is mostly working 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
Clamor said:
I have some good news. Here is mostly working 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
Click to expand...
Click to collapse
Are you planning to work on Pie as well once 8.1 is somewhat stable?
shinzz said:
Are you planning to work on Pie as well once 8.1 is somewhat stable?
Click to expand...
Click to collapse
I'm planing to bring up P as well. If O works, P should work as well.
Can the ROM be installed by using the latest KANG TWRP 3.2.3 or do I need to use the TWRP found in the download section?
@shinzz TWRP from download section
any update?
shinzz said:
any update?
Click to expand...
Click to collapse
Noticed the link to the ROM is 404'ed also. - NP
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Clamor said:
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Click to expand...
Click to collapse
My 201 is on KANG's - TWRP 3.2.1-0 and KatKiss, if this ROM just a simple wipe and flash with KANG's - TWRP 3.2.1-0 and the Harry Bean bootloader on my 201 or will I need a different recovery console, bootloader ext. ext? - NP
Just received this phone, and want to install a custom ROM on it. I have only two requirements:
1. Must support exFAT on external storage (including the micro sd card). No reason exists now for ROMs not to have this - Microsoft released the specification last year, and the Linux kernel now contains the code for it.
2. Must NOT have gapps installed (with preference given to ROMs that have microG installed, or at the very least are microG ready).
Any suggestions? Thank you in advance.
I did installed MIUI 11 and it's good but Pixel Experience is better and then again but Android 10 is comming to Mi A3!
Just wait till the end of the month!
hdnote said:
I did installed MIUI 11 and it's good but Pixel Experience is better and then again but Android 10 is comming to Mi A3!
Just wait till the end of the month!
Click to expand...
Click to collapse
I don't believe that any of those meet my requirement of a Google-free ROM.
n.p. said:
I don't believe that any of those meet my requirement of a Google-free ROM.
Click to expand...
Click to collapse
There are quite a number of gapps-free ROMs, one of the popular one is LineageOS. (I don't know if it support exFAT tho, you can always try it)
MarcusMario0605 said:
There are quite a number of gapps-free ROMs, one of the popular one is LineageOS. (I don't know if it support exFAT tho, you can always try it)
Click to expand...
Click to collapse
I am quite aware of LineageOS (and yes, it does support exFAT). Even better, a microG subsite (https://lineage.microg.org/) automatically rebuilds all LineageOS ROMs with microG support. However, LineageOS ROMs only exist for a few devices (just over a dozen Xiaomi phones, and specifically NOT, at least yet, including the A3). I hope they will add official support for it soon (and that will become my choice). In the meantime (particularly if the A3 never gets added to the list of supported devices), I continue to look for an alternative (as evidenced by creating this thread).
there is a section here with lot of ROMs, just use your time and read them.