Testing appreciated
CyanogenMod 11 unofficial 2014/03/24 (Android 4.4.2 "Kit Kat")
Download: http://d-h.st/MIs
MD5: 877d1ab510f1592c45f121c0f11fd41e
Gapps (optional): http://goo.im/gapps/gapps-kk-20140105-signed.zip
Before installing, please make a nandroid backup of your data and then wipe your phone using Chillybean's Anti-Venom Super Duper Wipe inside of 4EXT Recovery. Install and use this ROM at your own risk. I am not responsible for any data loss or damage that happens to your phone. You have been warned.
On January 29, 2014, polymath257 posted an unofficial build of CyanogenMod 11 that he had compiled using Chillybean's instructions. I have now done the same thing, but with a newer build. I am merely a compiler, not a developer. All credit goes to @chillybean, Evervolv, and the CyanogenMod team. I also want to thank @polymath257 for helping me get started.
GPLv2 compliance:
https://github.com/Evervolv/android_kernel_htc_msm7x30-3.0
https://github.com/chillybean
https://github.com/Evervolv
https://github.com/CyanogenMod
From my very limited testing, here's what I've been able to determine about what does and does not work.
Verizon CDMA works, but from what I can tell GSM does not (at least on my particular phone and SIM), even with a GSM patch applied. Camera doesn't work. Screenshots work. I am unable to test cellular data because I have it disabled on my plan. Further testing appreciated.
If a stable, fully functional daily driver is what you're looking for, this is NOT the ROM for you! In that case, I currently recommend Chillybean's unofficial CyanogenMod 10.1 with these settings. My build is intended for people who use an Incredible 2 as a secondary device and don't mind if certain things don't work. Indeed, Chilly's CM10.1 will be my daily driver until Kitkat becomes stable and fully functional for our phone, and I do not have the programming skill to make that happen.
To get an idea what's in my CM11 build that wasn't in polymath's CM11 build, read the release notes for CM11 Milestone 3 and CM11 Milestone 4.
YouTube videos aren't playing for me. I get the error "There was a problem while playing. Touch to retry." Does anyone else have this problem?
Im downloading now and about to test it and Ill let you know here in a little while if mobile data is working yet or not.
I can confirm that mobile data doesn't work so we can assume that mms doesn't either. Youtube does the same thing for me on both the app and on the mobile site.
Thanks. Sounds like I need to make a new build to try to fix those problems. I'll see what I can do.
not a problem. always willing to contribute any kind of help when i can.
how's the new build coming? any luck yet?
Nope. No luck. It compiled and I was able to flash it, but it wouldn't boot. I think it may be because of changes chilly has been making to his repo. He also posted about having boot issues.
For now, I suggest that people don't use the 2014/03/24 build of my ROM, which is the only build I've uploaded so far. It boots, but basic features like YouTube and mobile data are broken. If you want CM11, use polymath's build for now.
Great rom
Great work
Thanks. much Appreciated.
Well thats no good. Well thanks for trying anyways. With Polymath's i assume the camera is still broken, thats gonna be a source issue?
Yes.
Thats what i figured. Anyways thanks again for all your help and contributions.
New build
I have just uploaded a 4/08/2014 build of CM-11.0:
http://d-h.st/0qa
The source from this is from chilly's and evervolv's material. From what I can see, YouTube works, but the camera is still non-functional. Wifi works. I do not have this connected to any other networks, so I cannot comment on anything further. This does require a kitkat compatible recovery to install.
Standard disclaimers apply. I am not a dev; I am just a compiler. All credit goes to chilly, evervolv, and CyanogenMod.
Please test and report back!
Sweet thanks @Poly. Do you need testing to see if mobile data works or can u confirm that it does?
jam0688 said:
Sweet thanks @Poly. Do you need testing to see if mobile data works or can u confirm that it does?
Click to expand...
Click to collapse
Please test!
Downloading now will let you know something soon.
---------- Post added at 04:24 PM ---------- Previous post was at 03:25 PM ----------
From what I can see no mobile data and after you flash the gapps it shows the sim icon and no service. wifi works fine. youtube works fine as well just as you confirmed.
I can use gapps thorugh wifi. No app that uses the camera works (of course), but GPS seems to work according to GPS Test. My Inc2 is not activated, so I cannot test anything beyond wifi.
wifi works fine when i flashed the gapps. but theres no service. weird thing is before i flashed gapps i had service bars. could it be a gapps corrupt issue?
---------- Post added at 11:51 PM ---------- Previous post was at 11:48 PM ----------
on chilly's first build 3G works both with the gapps and without. which is what is weird.
Related
Team EOS XOOMICS 4.0.4 Wingray MZ604NIGHTLIES
Welcome to the evolution of TiamatXOOM.
With the AOSP release of Android 4.0 begins the next dawn of the Android operating system. And with this release comes Team EOS, the natural evolution of the TiamatXOOM development team.
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. The launching point for this development effort is the Motorola XOOM.
For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated once every 24 hours and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS Xoom is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS Xoom Nightly builds: http://goo-inside.me/devs/teameos/roms/nightlies/wingray/
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:
Use the latest available gapps package available from http://goo.im/gapps
*Note - You will need to re-flash G-Apps after you flash an updated nightly build. You can do this before you reboot after the installation of a new nightly.
Also note that if you are coming from an earlier G-Apps package you will need to wipe prior to installation of this package in order to avoid FC issues.
--
Current Known Issues:
This builds is only for the MZ604 Wingray (WiFi XOOM) It does not support data on any GSM or 3G only Xoom
Features:
Because these are nightly builds the included features are constantly evolving. Change logs are generally generated on a daily basis.
Change logs can be viewed at http://nightlies.teameos.org/changelogs/
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Tiamat ICS Xoom kernel
Support for OC;Under/Overvolt
Governors: lagfree, interactive, conservative, ondemand, userspace, performance
Kernel Note: In compliance with GPL kernel source can be found at: http://git.tiamat-dev.com/tegra2/tiamat-xoom/
--
Installation Notes:
These builds are designed to be installed from your favorite recovery (Solarnz R4c, Rogue, Clockwork)
Perform a full wipe (read Factory Reset) prior to installing this over ANY Honeycomb based rom (this includes all Tiamat roms)
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
FEATURE REQUESTS!
We need YOU, yes YOU to help us build the best AOSP rom out there. Have an idea for a feature you want to see implemented then let us know!
Team EOS Feature Request
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
EOS Motorola Xoom Boot Splash
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
Welcome to the XOOM evolved. Welcome to Team EOS.
For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
Also a note on 3G/4G Xooms- You can infact flash and install this rom on 3G/4G xooms. You will not however be able to use the 3G/4G radio. There are new basebands that are needed in order for the 3G/4G radios to be able to communicate with the RIL and until these updated basebands are released we are in a holding pattern for radio connectivity.
Also there are sporadic reports of HDMI partly functioning. Full HDMI functionality is dependent on additional proprietary binaries that Google has not been able to release yet due to licensing issues.
Also, please note that while the current builds are proving to be very stable, and for users that do not use their cellular radio they can be used as a daily driver these are still nightly builds and are subject to constant development. If you find strange or otherwise unexplained errors logcats are greatly appreciated as it makes it much easier to track down issues.
Thank you all for your support!
*Updated G-Apps Package*
The developers working on CM9 have released an updated G-Apps package for 4.0.3 AOSP based builds
New version is 4.0.3 V8
A Special Thanks goes out to gpstar this G-Apps build
Download: http://www.multiupload.com/54DD4VIXZ6
MD5: 4a6a7543b025a17f9536eccc4e5afc17
*Note - Because of changes made to the G-Apps package a wipe will be required if installing this version of G-Apps over a previous G-Apps package in order to avoid FC issues. This version of G-Apps appears to address some of the communications issues that have been plaguing Google services on AOSP builds.
Bug Reporting:
As you test out the platform and you discover bugs please report them to:
https://bugs.teameos.org/
A couple of notes about bug reporting. If it is an application issue (IE a particular game generates FC errors) please do not report it. There is nothing that we can do about specific application issues.
If you do report an error please, Please, PLEASE include logcats showing the errors. It is often time difficult if not impossible to replicate errors and logcats make resolving issues much much easier. Please feel free to add the logcats as attachments to the bug report.
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
Eos Motorola Xoom Boot Splash
Thank you again for your continued support of Team EOS!
I can say from personal experience that this ICS Rom is working beautifully. Yes, there are a few bits missing but it's clear that this is taking the Xoom to another level, altogether.
Cudos to Team EOS for taking this step. I can't wait for the next nightly.
Do we need to do a full wipe and reset if coming from razorbladex's rom?
double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
I didn't. Just wiped cache.
double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
Since I have no idea what rom that is the answer is yes. The only time you do not need a wipe is if you are coming from a factory OTA. Generally speaking all custom roms will require a wipe prior to install.
Did you have to reflash gapps and also will the su root file from razorbladex's rom conflict with this rom because I'm supposing this comes with root I just wanted to know if the two root files would conflict?
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
Nusince said:
Since I have no idea what rom that is
Click to expand...
Click to collapse
That's the original Xoom ics rom posted a few days ago here on xda by member razorbladex.
Again, since I have no way of knowing anything about razorbladex's ICS rom as I have never flashed it my inclination is to tell you to wipe first to ensure there are no residual or unforeseen conflicts. With that said, what you choose to do is up to you.
When you flash a new rom /system gets overwritten which includes the su binary so this is a non-issue. This build includes the latest changes to the su binary.
double1 said:
Did you have to reflash gapps and also will the su root file from razorbladex's rom conflict with this rom because I'm supposing this comes with root I just wanted to know if the two root files would conflict?
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
That's the original Xoom ics rom posted a few days ago here on xda by member razorbladex.
Click to expand...
Click to collapse
That first part of my question was for okantomi, sorry I should have quoted him since he stated that he had flashed this over that rom.
double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
I didn't wipe anything coming from his rom, just flashed the rom then flashed gapps and everything is fine, really quick and smooth
Is it possible to update the first post with a list of broken stuff so that it's easier to keep track?
Sent from my Galaxy Nexus using XDA App
Can anyone comment on HD youtube and netflix working ?
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
rockhumper said:
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
Click to expand...
Click to collapse
Because you clearly have no cell network signal! Mine has it too. Give it a while: ICS roms are new and have yet to be extensively tweaked for little details like this.
bumbernut said:
Can anyone comment on HD youtube and netflix working ?
Click to expand...
Click to collapse
Both play content. Navigating Netflix isn't the smoothest.
It's because these builds are essentially ready for 3G/4G connectivity. However for the time being the cellular radio icon will show regardless of if you have a stingray(3g/4g) or wingray(wifi) board. This will be addressed once we have the necessary components to bring life to the cellular radios.
rockhumper said:
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
Click to expand...
Click to collapse
---------- Post added at 04:59 PM ---------- Previous post was at 04:40 PM ----------
HD content in Youtube works fine. Don't know about netflix.
bumbernut said:
Can anyone comment on HD youtube and netflix working ?
Click to expand...
Click to collapse
Very interesting. On the other rom HDMI worked but calendar didn't. Now on this rom calendar works but HDMI don't lol. Small trade off but I find this very interesting.
James
Netflix works fine for me
cant wait to flash this, just downloaded it and will be flashing when I get home, good work guys!
Can we assume that further updates will be flashable over this ROM without wiping ?
I'm uploading a build of CyanogenMod 12 for the t0lteatt I've built. This build is still very alpha, so not everything will work as expected, but much of the basic functionality is there and this may be capable of being a daily driver for those who have to live on the bleeding edge. I'm not sure how long I'll work on keeping the build updated, but it looks like I'll be working on it for now. Hope y'all like it.
Known Issues:
Battery life may be shorter than normal (Turning off Adaptive Brightness will greatly help with battery life)
Netflix and other DRM protected apps do not work.
Media sharing services, such as Snapchat, may not work or may have issues.
Twitch may not work.
Bluetooth can be sorta glitchy.
And much, much more (As stated, this build is very alpha, so issues can be expected)
Instructions:
Download ROM here: https://www.androidfilehost.com/?w=files&flid=22696
Download GAPPS here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Reboot into recovery
Full wipe: Wipe cache, dalvik, wipe data/factory reset, clean to install a new rom, format system.
Flash ROM downloaded above.
Flash GAPPS downloaded above.
Reboot into system.
Let the system rest for a bit and settle in. (It seems the system can be a bit temperamental if you try to use it too soon... At times.)
If things don't work after letting the ROM settle, you may need to reboot a couple of times for everything to work properly.
Enjoy the lollipop goodness!
I would like to give thanks to the following:
sbrissen, DerTuefel1980 and all other contributors (I know I'm missing a lot, but they're the only ones I can think of right off hand, so I appologize to anyone who deserves mentioning for not mentioning y'all by name, and swear yall have my deepest respect) for their contributions to developing and maintaining the t0lte and related device trees that eventually allowed lollipop to be built for our device.
Ivan_Meler for the original camera fix http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
mr.nth.na.vn for his work-around to get sbrissen's i605 build to work correctly on t0lte.
Voyebanm for his posts and links which helped me to find the answers I needed.
fkfmfz for his gps fix that I have baked into the ROM and miji2 for cleaning up the fix.
And all the developers, maintainers and contributors of CyanogenMod in their pursuit of advancing and freeing all our android based devices.
If you would like to read more about the development of CyanogenMod, you can find extra information at the following links.
CyanogenMod: http://www.cyanogenmod.org/
CyanogenMod Wiki: http://wiki.cyanogenmod.org/
CyanogenMod Source: https://github.com/CyanogenMod
CyanogenMod Code Review: http://review.cyanogenmod.org/
Other threads on XDA I found useful:
CM12 for T0LTE by Voyebanm: http://forum.xda-developers.com/galaxy-note-2-att/development/cm12-t0lte-t2967836
[Rom] [alpha] [Unofficial] CM12.0, malir3p2 [20141214] by DerTuefel1980: http://forum.xda-developers.com/gal...rom-cyanogenmod-12-0-malir3p2-build1-t2958358
[12/12]{CM12-Unofficial} T0lte-Everything Almost Work+Incall by mr.nth.na.vn: http://forum.xda-developers.com/gal...05/rom-10-12-14-cm12-unofficial-data-t2969067
[ROM][I605]Cyanogenmod 12.0 [12/12/14] by sbrissen: http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
Have a good one!
AzraelsKiss said:
I'm uploading a build of CyanogenMod 12 for the t0lteatt I've built. This build is still very alpha, so not everything will work as expected, but much of the basic functionality is there and this may be capable of being a daily driver for those to have to live on the bleeding edge. I'm not sure if I'll work on keeping the build updated, but it's always a possibility. Hope y'all like it.
Known Issues:
GPS may not work (GPS Test does not see any satellites, but navigation still seems to work, so I don't know)
Battery life may be shorter than normal
Camera issues (see below)
And much, much more (As stated, this build is very alpha, so issues can be expected)
Instructions:
Download ROM here: https://www.androidfilehost.com/?fid=95857557620392172
Download GAPPS here: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Reboot into recovery
Full wipe: Wipe cache, dalvik, wipe data/factory reset, clean to install a new rom, format system.
Flash ROM downloaded above.
Flash GAPPS downloaded above.
Reboot into system.
Skip initial setup.
Go to Settings > Language & input > Current Keyboard.
Check on "Hardware".
Setup Wifi, APN, Google account, etc in Settings.
If you have problems with camera (no back camera/Can't connect to camera):
Download Google Camera from the Play Store.
Download Terminal Emulator (Terminal Emulator for Android) from the Play Store.
Open Terminal Emulator
Type: su
Press Enter
Type: sh etc/init.d/80cfw
Camera may now work (Sometimes, the camera may, again, not connect, but should start working again after a reboot)
Enjoy the lollipop goodness!
I would like to give thanks to the following:
sbrissen, DerTuefel1980 and all other contributors (I know I'm missing a lot, but they're the only ones I can think of right off hand, so I appologize to anyone who deserves mentioning for not mentioning y'all by name, and swear yall have my deepest respect) for their contributions to developing and maintaining the t0lte and related device trees that eventually allowed lollipop to be built for our device.
Ivan_Meler for the camera fix http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
mr.nth.na.vn for his work-around to get sbrissen's i605 build to work correctly on t0lte.
Voyebanm for his posts and links which helped me to find the answers I needed.
And all the developers, maintainers and contributors of CyanogenMod in their pursuit of advancing and freeing all our android based devices.
If you would like to read more about the development of CyanogenMod, you can find extra information at the following links.
CyanogenMod: http://www.cyanogenmod.org/
CyanogenMod Wiki: http://wiki.cyanogenmod.org/
CyanogenMod Source: https://github.com/CyanogenMod
CyanogenMod Code Review: http://review.cyanogenmod.org/
Other threads on XDA I found useful:
CM12 for T0LTE by Voyebanm: http://forum.xda-developers.com/galaxy-note-2-att/development/cm12-t0lte-t2967836
[Rom] [alpha] [Unofficial] CM12.0, malir3p2 [20141214] by DerTuefel1980: http://forum.xda-developers.com/gal...rom-cyanogenmod-12-0-malir3p2-build1-t2958358
[12/12]{CM12-Unofficial} T0lte-Everything Almost Work+Incall by mr.nth.na.vn: http://forum.xda-developers.com/gal...05/rom-10-12-14-cm12-unofficial-data-t2969067
[ROM][I605]Cyanogenmod 12.0 [12/12/14] by sbrissen: http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
Have a good one!
Click to expand...
Click to collapse
Thanks for the hard work! I got navigation but no gps lock but not an issue, camera fix worked for me. The only issue I had was no screen rotation. I flashed a sensor fix and all is good. Here is the link for the sensor fix: https://mega.co.nz/#!1xkSxTDJ!o8DQkNT6UvjNoxfgoxjNq2UnZz_6bO3ivYwMmvRv7dc
I am using this as my daily driver and I am grateful for everyone's time and hard work for giving our phones new life!
Shrek77 said:
Thanks for the hard work! I got navigation but no gps lock but not an issue, camera fix worked for me. The only issue I had was no screen rotation. I flashed a sensor fix and all is good. Here is the link for the sensor fix: https://mega.co.nz/#!1xkSxTDJ!o8DQkNT6UvjNoxfgoxjNq2UnZz_6bO3ivYwMmvRv7dc
I am using this as my daily driver and I am grateful for everyone's time and hard work for giving our phones new life!
Click to expand...
Click to collapse
Thanks for posting the sensor fix. I had forgot all about someone mentioning flashing it to fix proximity sensor issues as well. I don't seem to have the sensor issues myself, so it just slipped my mind. I'm glad ya liked the build. Have a good one!
This is fantastic! Did you port this from the N7100? Was it difficult? Anyone else noticing any major issues?
greddy91 said:
This is fantastic! Did you port this from the N7100? Was it difficult? Anyone else noticing any major issues?
Click to expand...
Click to collapse
This is built from CyanogenMod source with a couple of cherry picks of commits by sbrissen in code review. Many, many other, much more intelligent than me, people worked their arses off to get the t0lte and related device trees brought up for lollipop. All I did was build it with the t0lteatt specific information already coded for CM-11.0. Glad you're enjoying the ROM.
Have a good one!
everything works perfectly
AzraelsKiss said:
I'm uploading a build of CyanogenMod 12 for the t0lteatt I've built. This build is still very alpha, so not everything will work as expected, but much of the basic functionality is there and this may be capable of being a daily driver for those to have to live on the bleeding edge. I'm not sure if I'll work on keeping the build updated, but it's always a possibility. Hope y'all like it.
Known Issues:
GPS may not work (GPS Test does not see any satellites, but navigation still seems to work, so I don't know)
Battery life may be shorter than normal
Camera issues (see below)
And much, much more (As stated, this build is very alpha, so issues can be expected)
Instructions:
Download ROM here: https://www.androidfilehost.com/?fid=95857557620392172
Download GAPPS here: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Reboot into recovery
Full wipe: Wipe cache, dalvik, wipe data/factory reset, clean to install a new rom, format system.
Flash ROM downloaded above.
Flash GAPPS downloaded above.
Reboot into system.
Skip initial setup.
Go to Settings > Language & input > Current Keyboard.
Check on "Hardware".
Setup Wifi, APN, Google account, etc in Settings.
If you have problems with camera (no back camera/Can't connect to camera):
Download Google Camera from the Play Store.
Download Terminal Emulator (Terminal Emulator for Android) from the Play Store.
Open Terminal Emulator
Type: su
Press Enter
Type: sh etc/init.d/80cfw
Camera may now work (Sometimes, the camera may, again, not connect, but should start working again after a reboot)
Enjoy the lollipop goodness!
I would like to give thanks to the following:
sbrissen, DerTuefel1980 and all other contributors (I know I'm missing a lot, but they're the only ones I can think of right off hand, so I appologize to anyone who deserves mentioning for not mentioning y'all by name, and swear yall have my deepest respect) for their contributions to developing and maintaining the t0lte and related device trees that eventually allowed lollipop to be built for our device.
Ivan_Meler for the camera fix http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
mr.nth.na.vn for his work-around to get sbrissen's i605 build to work correctly on t0lte.
Voyebanm for his posts and links which helped me to find the answers I needed.
And all the developers, maintainers and contributors of CyanogenMod in their pursuit of advancing and freeing all our android based devices.
If you would like to read more about the development of CyanogenMod, you can find extra information at the following links.
CyanogenMod: http://www.cyanogenmod.org/
CyanogenMod Wiki: http://wiki.cyanogenmod.org/
CyanogenMod Source: https://github.com/CyanogenMod
CyanogenMod Code Review: http://review.cyanogenmod.org/
Other threads on XDA I found useful:
CM12 for T0LTE by Voyebanm: http://forum.xda-developers.com/galaxy-note-2-att/development/cm12-t0lte-t2967836
[Rom] [alpha] [Unofficial] CM12.0, malir3p2 [20141214] by DerTuefel1980: http://forum.xda-developers.com/gal...rom-cyanogenmod-12-0-malir3p2-build1-t2958358
[12/12]{CM12-Unofficial} T0lte-Everything Almost Work+Incall by mr.nth.na.vn: http://forum.xda-developers.com/gal...05/rom-10-12-14-cm12-unofficial-data-t2969067
[ROM][I605]Cyanogenmod 12.0 [12/12/14] by sbrissen: http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
Have a good one!
Click to expand...
Click to collapse
Everything works perfect , just one little bug ... My contacts from google dont displey when someone calls nor are the showing up in messaging app. Any ideas
And the camrea is working front and back
Tried to get the camera to work sadly I couldn't. Other than that and some graphical glitches on chrome beta(which is probably just not completely ready for lollipop) everything is running great.
I tried to install this an it gets stuck in bootloop.
try ...
mtech5 said:
I tried to install this an it gets stuck in bootloop.
Click to expand...
Click to collapse
Try installing CM 11 First and going through the set up then boot into recovery and install cm12 have fun
Hit thanks if it helped
Joshua Mr PC Repair said:
Try installing CM 11 First and going through the set up then boot into recovery and install cm12 have fun
Hit thanks if it helped
Click to expand...
Click to collapse
What I ended up doing was I was able to boot the rom for the 7105 so I installed it then dirty flashed this one over it. Runs like a charm.
mtech5 said:
What I ended up doing was I was able to boot the rom for the 7105 so I installed it then dirty flashed this one over it. Runs like a charm.
Click to expand...
Click to collapse
Look for the Lolipop shift kernel and install it , it fixes fron and rear camrea
After I did the dirty flash the camera works without doing anything extra.
Got a quick question for you guys. I have flashed this on my note 2 and have an unofficial CM12 I am working on flashed on my Note 4.
I however cannot figure out why Netflix will not work on either build. It is not a lollipop issue, because it works on my tablet, it seems to be an issue on CM12 only.
Would love to know if you guys have a solution, or know what might be missing from the build, so I can bring it back over to the CM12 note 4 thread. Thanks!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
ShrekOpher said:
Got a quick question for you guys. I have flashed this on my note 2 and have an unofficial CM12 I am working on flashed on my Note 4.
I however cannot figure out why Netflix will not work on either build. It is not a lollipop issue, because it works on my tablet, it seems to be an issue on CM12 only.
Would love to know if you guys have a solution, or know what might be missing from the build, so I can bring it back over to the CM12 note 4 thread. Thanks!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Netflix just updated , try it again , i just updated mine and seems to be working ,
Joshua Mr PC Repair said:
Netflix just updated , try it again , i just updated mine and seems to be working ,
Click to expand...
Click to collapse
So this is the error I am getting.
Any ideas
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Everything seems to be working just fine, except for after a few hours it starts rebooting when the screen is turned off. Manually or automatically.
Full charge .. Seems radio is killing my battery
ShrekOpher said:
So this is the error I am getting.
Any ideas
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah other build have the issue .. ROM still work in progress beta
Sent from my GT-N7105 using XDA Free mobile app
I will try this later tonight and see how it is... I just upgraded to the z3. The front speakers were what made me get it... Lol. I will still lurk here once in a while.
Okay... Did a new build... This should fix some soft reboots, the first boot setup keyboard issue, some of the camera issues and maybe a few other issues. https://www.androidfilehost.com/?fid=95863780491132977
There's over 200 downloads for the first build, so it seems a fair few have given it a try. Thank y'all for that. Just keep in mind, this is still an alpha stage ROM, so there will still be issues and errors, but hopefully, they'll be few enough to make it usable. Have a good one!
Hello, I've gone from regular Samsung SG3 rom to CyanogenMod about 3 months ago. I at first was using their snapshot (stable) version, which was a CM 12.X. But I thought of being adventurous and switched to their nightly updates. That got me to CM 13.X, Marshmallow. Well, I'm finding a few problems with my use.
So I ask, are there other ROMs that have a stable/snapshot Marshmallow available. By "stable", I mean that all the bugs have been ironed out.
bbwarfield said:
Hello, I've gone from regular Samsung SG3 rom to CyanogenMod about 3 months ago. I at first was using their snapshot (stable) version, which was a CM 12.X. But I thought of being adventurous and switched to their nightly updates. That got me to CM 13.X, Marshmallow. Well, I'm finding a few problems with my use.
So I ask, are there other ROMs that have a stable/snapshot Marshmallow available. By "stable", I mean that all the bugs have been ironed out.
Click to expand...
Click to collapse
Simple answer, no. There are a a few M builds out there that are "relatively stable" but will have bugs. It all depends on what features you absolutely need.
Hw4ng3r said:
Simple answer, no. There are a a few M builds out there that are "relatively stable" but will have bugs. It all depends on what features you absolutely need.
Click to expand...
Click to collapse
What I need:
Incoming phone calls
Wifi
Camera
Those are my top 3. What could you recommend? I have an S3 bought in Canada.
bbwarfield said:
What I need:
Incoming phone calls
Wifi
Camera
Those are my top 3. What could you recommend? I have an S3 bought in Canada.
Click to expand...
Click to collapse
I haven't seen any issues with incoming phone calls and WiFi. Right now, there's an FFC (front facing camera) issue with the official CM13 nightlies, but I think they are close to figuring it out. OctOS M is another Marshmallow ROM, I believe it has the same FFC issue as it is an AOSP based ROM and FCC is an AOSP issue (someone correct me if I'm wrong please).
Hw4ng3r said:
I haven't seen any issues with incoming phone calls and WiFi. Right now, there's an FFC (front facing camera) issue with the official CM13 nightlies, but I think they are close to figuring it out. OctOS M is another Marshmallow ROM, I believe it has the same FFC issue as it is an AOSP based ROM and FCC is an AOSP issue (someone correct me if I'm wrong please).
Click to expand...
Click to collapse
No, you're not wrong at all. The quirk is a little strange though, as when there's a lot of light in the picture, it will crash when you attempt to snap it. This is usually foxed with apps like Google Camera or Open Camera though, it's specific to the stock camera. I would suggest OCT-M though, OP; I just switched to it from the official nightlies and it's much smoother than those builds.
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
Woot! ? OctOS FTW! Lol, jk. Pretty much all d2att MM ROMs will have the same issues. Our builds may be a little more stable than official/unofficial CM builds at times because we test extensively & we choose what we merge carefully before building out. However its most likely we will have the same issues 99% of the time. Our final LP release build is very stable. Our current MM R1 release & weeklies are except for Bluetooth audio & FFC.
? d2att Oct-M KrAkEn Kernel ?
canodroid15 said:
Woot! OctOS FTW! Lol, jk. Pretty much all d2att MM ROMs will have the same issues. Our builds may be a little more stable than official/unofficial CM builds at times because we test extensively & we choose what we merge carefully before building out. However its most likely we will have the same issues 99% of the time. Our final LP release build is very stable. Our current MM R1 release & weeklies are except for Bluetooth audio & FFC.
d2att Oct-M KrAkEn Kernel
Click to expand...
Click to collapse
@ the moment my datt always pops up an unrepentant dialog box saying "unfortunately the setup wizard has stopped" alternatively, the setup wizard always force close. And this occurs immediately I install "any" gapps. I have tried virtually all the MM roms on here I.e nightlies, octus, matrix unofficial. Yet all were futile. Don't know if ur next update will look into that issue... And BTW, I normally clear my systems, cache & delvik cache whenever I flash, and I am on the latest twrp.
So what gapps are you using? Not getting that here. I'm on the latest Oct-M weekly. I'm using OpenGapps aroma package & on TWRP 3.0.2-0 d2att
? d2att Oct-M KrAkEn Kernel ?
---------- Post added at 03:08 PM ---------- Previous post was at 03:05 PM ----------
Also, how are you flashing? You have to flash ROM & gapps at the same time using the add zip button in recovery. If you're coming from an older rom/android version you may need to wipe internal SD as well as system, cache, dalvik
? d2att Oct-M KrAkEn Kernel ?
Am sorry for the noob question.. But how is that possible to flash Rom and gapps at the same time?? Tought its ROM after gapps without rebooting the phone ..... And is wiping of the internal SD mandatory.. ? Although I came from 4.4.4 to 6.0.1. And haven't wiped the internal yet.
---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------
canodroid15 said:
Woot! OctOS FTW! Lol, jk. Pretty much all d2att MM ROMs will have the same issues. Our builds may be a little more stable than official/unofficial CM builds at times because we test extensively & we choose what we merge carefully before building out. However its most likely we will have the same issues 99% of the time. Our final LP release build is very stable. Our current MM R1 release & weeklies are except for Bluetooth audio & FFC.
d2att Oct-M KrAkEn Kernel
Click to expand...
Click to collapse
canodroid15 said:
So what gapps are you using? Not getting that here. I'm on the latest Oct-M weekly. I'm using OpenGapps aroma package & on TWRP 3.0.2-0 d2att
d2att Oct-M KrAkEn Kernel
---------- Post added at 03:08 PM ---------- Previous post was at 03:05 PM ----------
Also, how are you flashing? You have to flash ROM & gapps at the same time using the add zip button in recovery. If you're coming from an older rom/android version you may need to wipe internal SD as well as system, cache, dalvik
d2att Oct-M KrAkEn Kernel
Click to expand...
Click to collapse
Am sorry for the noob question.. But how is that possible to flash Rom and gapps at the same time?? Tought its ROM after gapps without rebooting the phone ..... And is wiping of the internal SD mandatory.. ? Although I came from 4.4.4 to 6.0.1. And haven't wiped the internal yet.
Hey guys,
I've just managed to make a build of Cyanogenmod with lots of help by a guy called sultanqasim (actually he did most of the work), thanks a lot bro
Probably it's very bugy. Let's call it Pre-Alpha. Anyway, the build is ready and I need guys who'd like to try it out.
I chase GDrive for the first CM build. All Beanstalk builds are uploaded to the official Beanstalk AFH.
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
NFC
Broken:
Audio through built in speakers or headphones
RIL
Camera
Mic
Various other smaller things
Some Sprint users also report that it doesn't work for them. Just try it out if you like. Every tester's report takes the project a bit closer to stable builds.
Download Cyanogenmod (GDrive)
Download Beanstalk (AndroidFilehost)
To flash it:
in TWRP, reformat the userdata partition as unencrypted ext4. Go to Wipe->Advanced Wipe, select data, click on repair or change filesystem, change file system, and choose ext4.
in TWRP, go to Wipe -> Advanced wipe, and erase system, data, dalvik, and cache
flash the file by pushing it to your sdcard or you can use adb sideload. Also you can flash GApps optionally.
reboot into the system
Looking forward to your reviews. Thanks a lot
Good luck to all of you
Remember: I'm not responsible for anything that could happen as a result of following my instructions or anything else.
XDA:DevDB Information
[Testing][ROM] Cyanogenmod 13 - Unofficial, ROM for the HTC 10
Contributors
krassermensch, sultanqasim
Source Code: https://github.com/sultanqasim
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2016-06-10
Last Updated 2016-07-13
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
Nice!
Moderator Information,
Thread re-opened to allow OP to upload file on XDA host.
Can't wait for CM13 on this phone. I know Squid2 has been a ton of work into this, from what I know, already a solid month behind the scenes.
device boots up? display?
thought this thread was closed till a download link was posted...
i don't seem to find any link or me gone blind lolll
edit:- just read that its opened for uploading the link so it seems upload is in progress
Maybe change the title with correct spelling of " Unofficial "
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
i guess we would need to wait for the upload to be finished to see if its any different or the same as the Op doesn't seem to be much of responding to any comments
@krassermensch - Can you give us a list of what is and isn't working in your experience, at least?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
krassermensch said:
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
Click to expand...
Click to collapse
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
psych0r3bel said:
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
Click to expand...
Click to collapse
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
I'm really glad to see this coming along! Keep up the good work. I'm not much of a tester normally but I think Im going to give it a shot later tonight and let you know what issues I can find.
krassermensch said:
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
Click to expand...
Click to collapse
So glad to see the credits given, and insight to what testers will find.
Didn't want to see any drama, I thanks for putting the time in and squid for laying these ground work!
Sent from my HTC 10 using XDA-Developers mobile app
@krassermensch, thanks for your efforts but... If you're going to publish his work, how about updating the OP with his bug list and the title with pre-alpha. Just so users have more information, instead of the vague "it might be buggy". We know its buggy. Specifics about what works and doesn't is what people would like to know.
This still accurate?
squid2 said:
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
Broken:
Audio through built in speakers or headphones
RIL
Fingerprint sensor
Camera
Various other smaller things
Click to expand...
Click to collapse
Moderator Information,
Thread has been moved to general, as the OP is only hosting the work for another user.
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
matteosaeed said:
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
Click to expand...
Click to collapse
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
rav101 said:
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
Click to expand...
Click to collapse
Sweet. I can test more at nights when I am at home. Doing the nanodroid now of this build.
---------- Post added at 09:17 PM ---------- Previous post was at 08:52 PM ----------
question, I am trying to go back but I am getting the failed to mount '/system' (invalid argument), any tips on how to bypass that?
I have some previous experience building rom from the WIko Wax and the Huawei P8.
I run the Xiaomi A2 Lite as my daily driver, so I can't afford to test this ROM.
I do not know if this will even boot. As I said, I need you members of this forum to test this and tell me what works and the ROM's performance.
This ROM is based on LineageOS 17.1, so that is Android 10.
With a bit of luck this should work out of the box. It is here, that I should thank the pople from the Team Potato here https://forum.xda-developers.com/mi-a2-lite/development/10-0-posp-v3-q-daisy-t4011191 They are the ones who made most of the work to bring Android 10 to this device. I have just modified it a bit. Once again, props to them.
And here are the links to the different versions:
Version 0.1
No device audio
No camera
Link V0.1
Version 0.2
LED not working when charging
Fixed Camera
Fixed Audio
Link V0.2
Version 0.2.1
Fixed LED
Link V0.2.1
Version 0.3
More breaking than fixing
Wireless display fixed
Link V0.3
Version 0.5
Everything should be fixed now
OTA crashes whe nhitting install
Link V0.5
Version 0.6
Uses right microphone for camcorder
Link V0.6
Version 0.7
Fixed wireless display
Fix decoder.avc errors
Build tinymix
Build libldacBT_dec
Link V0.7
Version 0.8
Everything should work
Stable flashlight behaviour
Fixed green camera tint in low light
Link V0.8
Version 0.9
Camera switching fixed
Everything works
Working OTA
Link V0.9
Version 0.9.1
Fixed back video recording
Link V0.9.1
Version 0.9.5
Fixed flash issue
Should be bug-free
Link V0.9.5
Version 0.9.5.1
Fixes GCAM
Link V0.9.5.1
Version 1.0
Everything is stable now
New HAL1/HAL3 switch
Link V1.0
Always latest url: https://github.com/a-huk/otaserver/releases/download/09/lineage-17.1-20201115-UNOFFICIAL-daisy.zip
It is a zip, I suppose that it will be possible to flash it through TWRP, just clean flash as much as possible. I am not responsible for any harm this may do to your devices.
Again, please only post with feedback on the ROM, logcats would be useful as well or some benchmarks. I would like to make this stable and if possible official with Lineage. I know this forum is a mess, but again it is only for development. I will make propper one if this ever works. I need testers, thanks in advance. And props to the Potato Team
XDA:DevDB Information
LineageOS 17.1, ROM for the Xiaomi Mi A2 Lite
Contributors
reujea0
Source Code: https://github.com/a-huk/device_xiaomi_daisy
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Beta
Created 2020-04-02
Last Updated 2020-04-04
It boots, it runs great. No audio of any kind and camera (stock and GCam) not working. So far..
In any case, thanks for the rom and fast delivery.
Sorry, BT and headphones audio works for music and notifications.
celrau said:
It boots, it runs great. No audio of any kind and camera (stock and GCam) not working. So far..
In any case, thanks for the rom and fast delivery.
Sorry, BT and headphones audio works for music and notifications.
Click to expand...
Click to collapse
Thanks for the quick logcat
I will try and fix these, in the meantime, could you try this app https://play.google.com/store/apps/details?id=com.footej.camera2?
reujea0 said:
could you try this app https://play.google.com/store/apps/details?id=com.footej.camera2?
Click to expand...
Click to collapse
I tested camera with a camera app "vanilla" camera2 and it's not working..
reujea0 said:
Wew building for a wiko phone must have been a pain in the ass welp welcome in the community and good luck
~ Lacia
Click to expand...
Click to collapse
lacia-chan said:
reujea0 said:
Wew building for a wiko phone must have been a pain in the ass welp welcome in the community and good luck
~ Lacia
Click to expand...
Click to collapse
Yeah, plus that one was based off a Nvidia SOC
Click to expand...
Click to collapse
celrau said:
I tested camera with a camera app "vanilla" camera2 and it's not working..
Click to expand...
Click to collapse
Second testing version was released 0.2, see the link above
reujea0 said:
Second testing version was released 0.2, see the link above
Click to expand...
Click to collapse
heyo,
I have a few things to say:
- Your bringup is a mess
- Do your bringup on these trees https://github.com/PotatoDevices/device_xiaomi_daisy/tree/6180e3d5870834981e5f41424014047038ca235c
https://github.com/PotatoDevices/vendor_xiaomi_daisy
That will fix audio and cam
Thank you so much for your work. Imma fan of Lineage since the beginning and would prefer it over stock rom.
I dont want to be rude or anything but your bringup is quite a mess in my eyes and why is audio and **** not working for you since almost everything works fine here besides the wifi dsplay and fm radio
Click to expand...
Click to collapse
WTF!? It's for testing purposes only as OT says. Maybe u can contribute and help solving those issues?
reujea0 said:
Second testing version was released 0.2, see the link above
Click to expand...
Click to collapse
Everything I've tested works now, thanks for prompt delivery.
celrau said:
Everything I've tested works now, thanks for prompt delivery.
Click to expand...
Click to collapse
Sick, could you test some more things, like sd, calls, LTE, and run an ANTUTU benchark?
reujea0 said:
Sick, could you test some more things, like sd, calls, LTE, and run an ANTUTU benchark?
Click to expand...
Click to collapse
SD card works, calls I just tested with my other phone, LTE later since I don't have it at my current location. GPS works pretty good. I never used ANTUTU but will give it a try later.
---------- Post added at 11:34 AM ---------- Previous post was at 11:19 AM ----------
Notification/charging light not working
Cappucinto said:
Thank you so much for your work. Imma fan of Lineage since the beginning and would prefer it over stock rom.
WTF!? It's for testing purposes only as OT says. Maybe u can contribute and help solving those issues?
Click to expand...
Click to collapse
XD, I took a look at his commits and they looked like a mess and i linked him to my updated trees that have the audio and cam issue solved so next time read further into the message instead of trying to become a white knight thanks
lacia-chan said:
XD, I took a look at his commits and they looked like a mess and i linked him to my updated trees that have the audio and cam issue solved so next time read further into the message instead of trying to become a white knight thanks
Click to expand...
Click to collapse
Yeah they are a mess, getting started ?, haven't done this in a while. Yeah, this is pretty much your tree with your latest commits and some changes to convert it to a lineage tree. I also ignore neverallows to let the build finish. I will have to eventually deal with them to make it into an official build. In the meantime I plan on hosting an OTA server on my own. I am not hiding that most of this is your work, it is forked and I thank the POSP team and other devs who worked on the A2 Lite, thanks again. I just prefer LOS and there seems to be demand for it so I'm here trying to build it.
I don't think that there is a need for anyone to argue, we all have the same phone, more ROMs are always welcome and merit should be given where it is due, which I think has been done.
I will make another post in the following days, where everything is properly outlined with some more explanations.
reujea0 said:
Yeah they are a mess, getting started , haven't done this in a while. Yeah, this is pretty much your tree with your latest commits and some changes to convert it to a lineage tree. I also ignore neverallows to let the build finish. I will have to eventually deal with them to make it into an official build. In the meantime I plan on hosting an OTA server on my own. I am not hiding that most of this is your work, it is forked and I thank the POSP team and other devs who worked on the A2 Lite, thanks again. I just prefer LOS and there seems to be demand for it so I'm here trying to build it.
I don't think that there is a need for anyone to argue, we all have the same phone, more ROMs are always welcome and merit should be given where it is due, which I think has been done.
I will make another post in the following days, where everything is properly outlined with some more explanations.
Click to expand...
Click to collapse
oh no you got me wrong, Your credits were alrights its just that your source is a mess and that trees i linked have the issues like cam and audio fixed and nope more roms is not a great idea because we had a buildbot apocalypse earlier during the pie days we had like 42 roms at that point
That's awesome news @reujea0, congratulations!
LineageOS is all I need for this phone.
I'll move to this ROM as soon as it gets close to official (I use it as my daily driver).
lacia-chan said:
oh no you got me wrong, Your credits were alrights its just that your source is a mess and that trees i linked have the issues like cam and audio fixed and nope more roms is not a great idea because we had a buildbot apocalypse earlier during the pie days we had like 42 roms at that point
Click to expand...
Click to collapse
Yeah, can completely agree with this, but tbh I feel like Los is a must for any phone. I'm not saying that it is better/worse than other ROMs but anyone in the scene knows it and most of them are stable and close to AOSP.
reujea0 said:
Sick, could you test some more things, like sd, calls, LTE, and run an ANTUTU benchark?
Click to expand...
Click to collapse
LTE works fine
---------- Post added at 05:32 PM ---------- Previous post was at 05:20 PM ----------
lacia-chan said:
XD, I took a look at his commits and they looked like a mess and i linked him to my updated trees that have the audio and cam issue solved so next time read further into the message instead of trying to become a white knight thanks
Click to expand...
Click to collapse
Your intervention, well intended as you say it was should have been private, otherwise it is what it looks like.
---------- Post added at 06:26 PM ---------- Previous post was at 05:32 PM ----------
Please enable signature spoofing for MicroG
LineageOS still my favorite ROM.
Well, hope will be official soon.
EDIT : Could you please share the change log if the update is released ?
1st of all thank you so much, for starting this missing project, this afternoon i'll report more!
1. ZIP wouldnt install through TWRP (error: to Edit later) (deleted System/Data/Cache Stuff, from Android 9), so unpacked payload.bin, and flashed manually in fastboot from stock 9.
2. One permission which is needed for MicroG with Playstore (no gapps) I think something like certificate/signing spoofing is missing. (Specify later)
Besides that feels quite stable, safety net passed with opengapps/magisk, can comfirm wifi, camera, sound works. Noticed nothing wrong, will test more today, right now writing in this Rom!
Someone asked for antutu Benchmark? Could not run it, inside the tutorial the "which OS are you using" wasnt clickable, probably because off the app itself? But:
3D Mark
853 points - my A2 Lite LOS 17.1 > 56% than other A2 Lite's
(Average)