Why Android 4.2 must be on mt6577? - Micromax A110

Thats becouse Android 4.2 - start point to compile new MIUI with dual-sim support from sources on github. Thats why we can donate for developers and hope for a good feature. Thats all from me.
Sorry for my Engish

Related

Source Code IceCreamSandwich Is Out

INTRESTING NEWS!!!:
Over at our Android Open-Source Project git servers,the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Hey dude, this is the development section. If you wanna post in here, you better have something to offer.
If you wanna post relevant news updates, shouldn't it go in the general section or something? Just sayin'
nrvnqsrxk said:
Hey dude, this is the development section. If you wanna post in here, you better have something to offer.
If you wanna post relevant news updates, shouldn't it go in the general section or something? Just sayin'
Click to expand...
Click to collapse
True, but is the code not something to develop a icecream rom?, if not then i will delete it, sorry if i put it in the wrong section
nrvnqsrxk said:
Hey dude, this is the development section. If you wanna post in here, you better have something to offer.
If you wanna post relevant news updates, shouldn't it go in the general section or something? Just sayin'
Click to expand...
Click to collapse
Sounds alot like a development related post when a source code is out
Developement means something you've developed, all developers know the source is out, that's why we don't need a thread in Dev, also this is like the 5th thread I've moved to general about the subject..
TheDeadCpu said:
Developement means something you've developed, all developers know the source is out, that's why we don't need a thread in Dev, also this is like the 5th thread I've moved to general about the subject..
Click to expand...
Click to collapse
Then move it or delete it if u want i dont care, just wanted to share thats all
korrel2008 said:
Then move it or delete it if u want i dont care, just wanted to share thats all
Click to expand...
Click to collapse
Nice attitude
It's nothing wrong, it's just that it's so big news it's hard to miss
No need to keep this thread open mates.
There is another one in the general section.
Thread closed
Cheers

[Q] What device tree I can use for Qumo Quest phone

Hi there!
I want to compile CM 10.1 for my phone, but stucked with device tree and i don't know what tree to choose for this.
Phone mentioned in the subject is Qumo brending of chinese i9220 PAD 5" MT6575 (e1809c_v75) Android 4.0.3
Great thanks if anyone can help.
PS. Sorry for my English.
rippak said:
Hi there!
I want to compile CM 10.1 for my phone, but stucked with device tree and i don't know what tree to choose for this.
Phone mentioned in the subject is Qumo brending of chinese i9220 PAD 5" MT6575 (e1809c_v75) Android 4.0.3
Great thanks if anyone can help.
PS. Sorry for my English.
Click to expand...
Click to collapse
I dont think there is one for that as that is not an official version of Android. Very few China based Android phones are supported by AOSP. You may have to start it yourself if you want it. The first thing you will need to do is have the OEM post the kernel source code for the device. This will be your biggest challenge. As most China OEM dont respect the GPL laws
zelendel said:
I dont think there is one for that as that is not an official version of Android. Very few China based Android phones are supported by AOSP. You may have to start it yourself if you want it. The first thing you will need to do is have the OEM post the kernel source code for the device. This will be your biggest challenge. As most China OEM dont respect the GPL laws
Click to expand...
Click to collapse
Ok
What if there is no source of kernel? Can I use compiled kernel (3.0.13) from current firmware (4.0.3) or this is impossible?
rippak said:
Ok
What if there is no source of kernel? Can I use compiled kernel (3.0.13) from current firmware (4.0.3) or this is impossible?
Click to expand...
Click to collapse
Without kernel source your kinda out of luck. No that kernel will not work on AOSP as that 4.0.3 is not an official android version. It is a hacked together version. Your best bet would be to sell it and get something that is not a knock off.
zelendel said:
Without kernel source your kinda out of luck. No that kernel will not work on AOSP as that 4.0.3 is not an official android version. It is a hacked together version. Your best bet would be to sell it and get something that is not a knock off.
Click to expand...
Click to collapse
Just for fun: wrote to "developer" for sources.
rippak said:
Just for fun: wrote to "developer" for sources.
Click to expand...
Click to collapse
Got to write to the OEM. Only they will be able to release the kernel source. Good luck. Dont hold on to hope though. They are not forced to post kernel source like everyone else.
zelendel said:
Got to write to the OEM. Only they will be able to release the kernel source. Good luck. Dont hold on to hope though. They are not forced to post kernel source like everyone else.
Click to expand...
Click to collapse
Don't you know is it real to compile with another kernel for same CPU MT6575?
Found some links to kernel sources for other phones - seems to be working for different devices.

Port of released Broadcom CPU and GPU drivers to AOSP based ROMs for BCM21553 SoCs

Hi to all Broadcom BCM215XX armv6 devices running android!
I'm glad to announce that, our organisation, BroadcomCM will start working on the port of AOSP ICS drivers for our CPU and GPU, BCM21553. First of all, I've asked moderators to close all my threads, why? We know we have [GENERAL] Thread for our projects but most users don't care, so this will be the thread to talk about it, development!.
Samsung stopped the development on this devices long ago, but their drivers where not ever released. Thanks to our petition, we have managed to force Broadcom to release the drivers, and we managed to release them on ICS, android 4.0+, way!
Index:
Post 1 (this) ...................................... Information about drivers
Post 2 .............................................. Frequently asked questions
Post 3 .............................................. Drivers on Github (Opensource)
Post 4 .............................................. Videos showing HW working
Click to expand...
Click to collapse
A bit of introduction:
Broadcom gave to us test driver builds, which were prebuilt, .so libraries, and we could not edit them, but they gave us the code to patch framework to make those prebuilt libraries work with our AOSP project (by that time, CyanogenMod 7.2). After some re-search and lot of work on our team (thanks Legolas93), I managed to implement AOSP Alcatel drivers to our CyanogenMod 7.2 Based ROM. This was the biggest change ever happened to that device, as we managed to fix 100% HW and as a cosnequence, libstatgefright was fixed too, and HGL. This resulted on camera/vide recordi (media profiles, encoding and decoding) to work, this was RC1. REMEMBER: As we extracted this libs from sotck AOSP alcatel ROM they are prebuilt, so we can not modify them at all.
SInce that moment, project on HW was stopped, and we focused to fix other issues not releted to HW (ext4, backlight, led, tethering, BT...), and we managed (most of them), and everyone enjoys now a CM, AOSP and Cyanmobile port brought to you by broadcomCM.
What else?
Broadcom released, or seemed to, BCM21553 driver source for AOSP ICS source. They released the source, so now we can know how our chip work. What is weird about it, is that this chip is released for ICS source, when it is an armv6 chip, and any device of our family has official ICS. (Maybe BROADCOM are really nice people, or maybe they trolled us). We will add new tag to be defined on Boardconfig.mk to make the drivers work on it.
So.. We did it?
Yes, we forced Broadcom to release the source, you, we, we all did this possible, and we should be prud of ourselves.
Will with this come BroadcomCM to develop?
Well, yes and no, we already have some surpises for BroadcomCM ROMs owner, which were not reletated to drivers at all, and they affect all devices. As this work is nearly finished (first alpha), we will release this next week, and then we will start working on it. Keep calm, good things make people wait for it don't ?
What is now?
Now, nice question. We will implement this source code on our CM9, ICS, branch. (all sources can be found on our github), and implement them on the build, will that be easy? OF COURSE NOT. Broadcom trolled us with first test builds of drivers, so maybe expect the same from that sources, we don't know and we will not know unitl we build it, and we have to compare each file, ONE PER ONE, so it will be a hard work.
Frequently asked questions can be found on the second post, as well as a video to show you what was having a device with drivers, and what was not. (Qualcomm vs Broadcom [armv6]).
ANY ETA? (Estimated Time of Arrival)
No. I can not tell any eta, I'll maintain you informed to you on this thread. I'll start my work next week (Exams on this one, need to study ), and I'll keep calm, I'm as amazed as you, but we have to be very down to earth. Broadcom lied to us, maybe they made it too. It will take some time to study and implement, and then make them work!
WILL THAT FIX ALL THE ISSUES WE HAVE ON ICS?
No, but will fix the most important one, HW. What I mean by hardware is the animations will be smooth, video on second post. So hopefully we will run a good ICS build, but expect camera and Audio not working too. Audio? Well some progress have been made on shadows, camera? That will be hard, really hard. Even Cooper (Galaxy Ace MSM7x27 based chip wasn't able to run camera at the first, since Qualcomm not release their source too).
AND WHAT ABOUT CM7 (2.3.7 based roms)?
We hope 2.3.7 ROMs will benefict from it, but we are not sure, we will have to test them and implement on our CM7 tree, but as they are for ICS, or this seems to, first goal is ICS, as we have 100% HW working, but with prebuilt, for the moment is OK and not our priority,
CAN I IMPLEMENT THE DRIVERS ON MY DEVICE?
No, to implement those dirvers you will need big knowledge of BroadcomCM devices, and I think our team has. We have managed to solve many bugs, and, talk with broadocm to solve first driver errors we had.
Ok, we have managed to get drivers working on our CyanogenMod 9.1 Ice Cream Sandwich version 4.0.4. Remember the drivers were given in 4.0.1 which were a bit different from actual 4.0.4 used.
After the release of the ROM with first version of those drivers included, we are glad to announce that, as always, we opensourced this "4.0.4 drivers" as well as Broadcom did. Feel free to take them, and use it at your own, to build diferent ROMs, such as AOKP, Paranoid, AOSP... Or Jelly Bean . This are drivers source, you will need to cherry-pick them to your local repo:
/bionic
/frameworks/base
/hardware/libhardware
/system/core
Broadcom was nice, and they created a new HGL lib, which they open-sourced too, and give the name of libv3d, kind of a new HGL lib, which should complish all patches and BCM21553 requiriments, also opensourced on BroadcomCM.
/brcm_usrlib also known as libv3d
You can also find original patch on Broadcom's page (4.0.1 patch) and the diff files I've made, which they will give you more clues on how to implement them on other sources.
On those videos, we can see that those drivers are fully working! Thanks for those youtubers, we can show to the world that WE DID IT!
ME presenting those drivers:
COOPERVE:
TOTORO:
TASSVE:
CORI: (WIP)
you guys are amazing,thanx for all............
Does this mean we can build other roms as well?
like aokp / paranoid android / pac /miui etc.
Anyhoo, I wish you goodluck.
u doing a great job buddy.
keep it up. :thumb:
n best of luck for ur exams..
---------- Post added at 11:18 PM ---------- Previous post was at 11:18 PM ----------
CharsiBabu said:
Does this mean we can build other roms as well?
like aokp / paranoid android / pac /miui etc.
Anyhoo, I wish you goodluck.
Click to expand...
Click to collapse
yup..
Always Great biel and his team..
using the great ace -i
Only these lines in legacy_prebuilts.mk already made me start to give up the drivers must be another troll source, maybe I'm wrong...
libEGL_POWERVR_SGX530_121.so \
libEGL_tegra.so \
libGLESv1_CM_POWERVR_SGX530_121.so \
libGLESv1_CM_tegra.so \
libGLESv2_POWERVR_SGX530_121.so \
libGLESv2_tegra.so \
Maybe they gave us fake one or another test builds. Still will take time months/year. Just buy new phone. This doesnt worth it.
Good luck, BroadcomCM!
It means,that we can expect cm9 only woth not working camera and sound?
This is some real good news if the broadcomCM have given the proper sources... Well, let's hope bielt.v keeps us updates
Dr.Pepper said:
It means,that we can expect cm9 only woth not working camera and sound?
Click to expand...
Click to collapse
If we get stable cm9 thats also great for us..
using the great ace -i
I highly doubt a big manufacturer would "troll" its consumers and volunteer developers with "fake" driver sources.
Sent from my GT-I9195 using xda app-developers app
I don't think they trolled us, they wrote a documentation and made an announcement for Fake drivers? A big manufacturer like broadcom will not play hide and seek with us, they know that they will lose their respect.
Sent from my GT-S5360 using Tapatalk 2
NICE!
CharsiBabu said:
Does this mean we can build other roms as well?
like aokp / paranoid android / pac /miui etc.
Anyhoo, I wish you goodluck.
Click to expand...
Click to collapse
We can leterally "port" those, (copy paste u know, lol)
Mitko said:
I highly doubt a big manufacturer would "troll" its consumers and volunteer developers with "fake" driver sources.
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
Its natural, lol, happens once in a millenium, but these maybe true... but one thing is serioussly doubtful that the readme says
Readme.txt: last line:
make -j8 TARGET_DEVICE=generic_armv5
Click to expand...
Click to collapse
and armv5 doesn't exist ?? && moreover our bcm21553 devices are more likely to be armv6 variations....
really confuses me
Code:
I havent done enough research tho (due to less time on pc)
can anybody explain me that ??
There a long-long way to go. hopefully the awaited days come with good news.
XDA-Developer App
So I'm noodling through the source code, and I guess I'm gonna see what I can do to try and compile something for the Raspberry Pi. Fingers crossed.
EDIT: Also, according to wiki, ARMv5 is in fact a thing. Who knew?
http://en.wikipedia.org/wiki/ARM_architecture

Wondermedia WM8880 SoC TABLET's - JB/KK ROM and KERNEL+Recovery's Development

Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. So don't be an *** ****
*/
hi.. i'm already started make some modifications on ROM with other Brazilian DEV's for "Evertek S.A - SKMtek Genesis Tab GT7305"... we already found the source kernel from another Netbook or Development Board PC who uses the same SOC... but nothing already have been maked to kernel, we use the provided kernel from stock (Kernel 3.4.5+)... and about the ROM we already have two custom ROM's... One is Stock Modded (4.2.2) and another is KitKat Ported ROM from another Evertek Device... *Portuguese-Brazil Language Site/Forum
And we already make some modifications to this KK port...
- ROOT
- BusyBox
- Init.D support
- Build.Prop Mods
- SuperUser
- zipalign apps after boot
.. and other mods.
we already make too much on ROM but nothing about kernel... we want make a better kernel with optimizations and a better TCP/Clock Table, More Governors , More I/O Scheduler and maybe Overclock to 1600mhz to start after have a custom Kernel booting...
Now we need someone who understand about recovery's like CWM or TWRP and Kernel Compilation better than me to we can start make something awesome =D i think this can be used to another company's/Chinese tablets too, using the same SOC (WM8880) evidently... . . . (Found^^Working^^Recovery's)
i can't start testing here because if i flash this kernel using the Stock Recovery (WonderMedia Recovery tool) maybe i can possible brick my tablet... so if someone understand about CMW recovery to start would be nice =D
Update Progress / ChangeLog ¬
Code:
# 25/12:
- [STRIKE]Found Possible match [URL="http://forum.xda-developers.com/showthread.php?t=2305268"]CWM port[/URL] from [URL="http://forum.xda-developers.com/showthread.php?t=2216390"]Asus MeMo Pad 7{ME172V}[/URL] on XDA Forum[/STRIKE] #NOPE...
- FOUND WOKING [URL="http://blog.hadi-cpu.com/2013/09/cwm-recovery-6036-w8850-rc2.html"]CWM Recovery[/URL] from Malasya Blog from Generic WM8850 SOC tablet , Founded [URL="http://blog.hadi-cpu.com/2013/10/twrp-touch-wondermedia-wm8850-jb-version.html"]TWRP recovery[/URL] too but not tested (Thanks to #Rollidark to notify me about and #osinaldi to discover that from malasya blog) [Mirrors -> [URL="https://www.4shared.com/rar/2POyc0B0ba/CWM_WM8850_NSFAT-RC2.htm?sop=true"]CMW[/URL] -> [URL="https://www.4shared.com/rar/rJBfUTQF/TWRP-JB-NSFAT-WM8850.htm"]TWRP[/URL]] // [URL="https://www.facebook.com/groups/NewSmartFrenAndroTab/"]Facebook Group of Recovery Developers[/URL]
- Studying some way to introduce the missing Touch driver to kernel from [URL="https://gist.github.com/psachin"]psachin Github[/URL]|[URL="http://cdn.liliputing.com/wp-content/uploads/2013/01/rock_02.jpg"]apc-rock-II-[/URL]|[URL="https://github.com/psachin/apc-rock-II-kernel"]kernel[/URL] how already modded the Source to work with [URL="http://tinyurl.com/oqxmuam"]Generic Netbook[/URL] who uses the same SOC
-- Merry Christmas to #ALL
# ?? to 23~24/12:
- ROM JB and KK + ADV. Patch developed by Brazilian Dev's team
- found Source Kernel to WM8880 SoC
Brazilian Developers who already help this projects from forum - genesiseries :
Code:
# KK ROM:
- #paulomsilva2006 {KitKat ROM Port}
- #Rollidark {KitKat Patch}
- #Wcfuria
- #? - Pedro Alves
- #? - Pedro Victor
- #? - Walter Moretti
- #? - Moises Teixeira
Code:
# JB Stock ROM:
- #ylukasy {ROM Dev.}
- #Rollidark
- #paulomsilva2006
- +?
if i forget someone.. please comment below :highfive:
Reserved
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
funtikar said:
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
Click to expand...
Click to collapse
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
DvDwx. said:
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
Click to expand...
Click to collapse
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
funtikar said:
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
Click to expand...
Click to collapse
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
what a coincidence , I was wondering today when you will reply lol
ah I see too bad, maybe you will share it at techknowme forum, ... wow Malaysian ?, Im asking because I'm Malaysian, can you pm me the link where its shared?
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
tuyenat3 said:
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
Click to expand...
Click to collapse
man... i just don't want blame anyone but... to we can do something to your tablet we need the kernel source and that don't stay open to developers... on this Chinese tablets we have some little configurations to can work with... but the custom kernel project i need to abandon for two reasons... first i don't have much time to can work to create a stable and functional custom kernel to everyone... second i don't have a kernel source compatible with tablets... what i found is from a electronics engineering Project computer Board ... and to it can fit on tablet is missing too much drivers compatibles with to can work smoothly and functional... someday if i found a new source maybe i can try comeback developer something to that =#
please continue developing this project
I use a genesis 7305 his kernel is very poorly optimized would like to make this usable tablet sorry for my bad English I use Google translator ;-;
2021... I tried to put a Chinese rom, but I brick the tablet, it only responds to fastboot, when I put the sudo command fastboot flash:raw boot uzImage.bin ramdisk.bin and plug in the charger and press power it appears a genesis screen.
Boot FOSSEE-OS from SCARD | FOSSEE-Laptop
laptop.fossee.in
GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
A low cost fossee-laptop based on wm8880 ARMv7 SoC - GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
github.com

[rom][aosp][grouper-tilapia][ua]android-8

Hello guys This is AOSP unlegacy android build.
It is a android version-8 (TESTING) .
Sources-
Source code- https://github.com/Unlegacy-Android/android
device- https://github.com/Unlegacy-Android/android_device_asus_grouper/tree/aosp-8.1
kernel- https://github.com/Unlegacy-Android/android_kernel_nvidia_tegra3
vendor - https://github.com/Unlegacy-Android/proprietary_vendor_nvidia/tree/aosp-8.1
Sorry links might be broken or removed
Issues
no camera
does not function with Gapps
no proper otg support
Thanks
@unlegacy android team
@Ziyan
@aosp
Status-testing
This security patches dupes and is faked
****disclaimer
Im not responsible for any kind of damage to device
If you point your finger at us we'll laugh at you
Guys I have got 2021 security patch level at the first flash and at the second flash I found it 2018. Just comment me your security patches.
Works on tilapia and grouper
download Link https://drive.google.com/file/d/10VaRPsRlJTsnKXLkmOiwpcD9pQP9wZNW/view?usp=sharing
Thank you!
I will use it!
edit:How did you write local_manifests?
Also, did you use the Tegra3 hardware tree?
Hey guys how is this rom
few__ said:
Thank you!
I will use it!
edit:How did you write local_manifests?
Also, did you use the Tegra3 hardware tree?
Click to expand...
Click to collapse
Yup I used the normal repo commands (I don't remember properly as I started compiling it 1.5 year ago)
SORRY for if any wrong sources aye!
Hi
Is ROM better than @ud4's 8.1.0 ROM? I currently have @ud4's and there an issue where some apps (like RedReader, Magisk Manager stable, Play Store, etc...) won't launch; they just show a blank screen. Does this ROM also have that issue?
Thanks

Categories

Resources