Related
Hello,
Please note I posted a similar question in 2012: "[Q] Most stable and fastest ROM (at the end of Dec 2012) -- is...?" http://forum.xda-developers.com/showthread.php?t=2048145
I got some great answers, feel free to check the link above. However, four years later I didn't experiment at all and lots of things happened, so I have similar Q:
In 2016. which NC ROM is most meaningful to install?
This is a perfect question for someone who was willing to try numerous NC builds. I'm not lazy, but there are hundreds of pages on different NC ROMs and their versions. So far, I used only Mirage 7.2, famous for stability and fluidity (as possible on 2010. HW). But, since it's Gingerbread, it doesn't support newer apps. Long ago, I briefly tried CM10 from 2012. and it was pretty slow. I guess things have changed so far.
I've been reading other DEV ROM threads, for instance this ROM was evaluated by users as fast as Mirage 7.2: [ROM] MROM-Encore [4.2.2][LINARO][CM10.1] build:20131003
There are different builds of modified CM10 (up to stable 10.2), and also lots of only nightly builds of CM11. There is even CM13 (Android M), developing as we speak! I don't have enough time to try all these builds, so I kindly ask someone how actually tried them or even worked on them to share a small digest: what's worth of trying and working with today on a daily basis?. Maybe a small comparison.
Are certain versions of CM10 or CM11 close to fluid, everyday use? Which offer same responsiveness (or maybe just a bit slower) but with new options (mostly: possibility of running Android 4+ apps). If yes, which version in particular is worth trying? Feel free to leave links.
Finally, I'm currently on CWM Recovery ver. 3.2.0.1 installed on eMMC (not SD card install). With this ver. I can flash CM 7.2 and CM 10. How about CM11 -- do I need newer CWM Recovery?
I'm really thankful for any hint. Cheers!
CM10 + Swap partition
I am new here and not a lot of experience with Nook Color or Cyanogenmod. I recently picked up a Nook Color (encore) and wanted to try out the CM options. I didn't spend much time with the stock setup. I started CM setups almost immediately. I have tried MROM, MiRaGe CM7.2, CM10, 10.1, 10.2, & 11. The best system setup to me was under CM10. Using the regular gapps collection made it crawl, I used the minimal gapps for CM10 (Android 4.1.2). Adding 1GB linux-swap partition (2gb SD card with p1 Fat32 900mb & p2 linux-swap 1024mb) using 'Swapper 2' made a lot of improvement in usability. Also went with Apex Launcher. I may have missed something obvious but in my recent limited experience, the best CM recipe for BNRV200 was as below...
Installation base:
CWM-based Recovery v6.0.4.8
cm-10-20130421-NIGHTLY-encore
YourZgappsXS-4.1.2-2014.03.16
Changed Settings:
Performance: CPU Interactive min600/max1100, I/O BFQ, 16bit transparency, Surface disable dithering.
Developer: Display - animations off in the three sections.
Apps:
Swapper 2 configured with 1GB linux-swap partition on SD card.
Apex Launcher
Root Checker
SuperSU
Solid Explorer
Dolphin browser
Quadrant (results example = 1513 - CPU 1376, Mem 1110, I/O 4221, 2D 141, 3D 719)
YouTube app required Google Play Services, Play Services made the system crawl & lag (uninstalled both).
Facebook app was laggy. The Dolphin browser was functional.
Today I went back to B&N stock 1.4.1 and I'll use it as a reader with the B&N included apps for a while.
Hello,
This what you wrote is awesome and very helpful! Thank you for that. I liked your review and testing of CM10 and the way you presented all the options. Kudos! :good:
However, I really do enjoy watching YouTube a lot. Having CM10 that's not possible, as you stated? Google Play Services Required, which would slow down the whole system. At the moment I am on Mirage 7.2 and using super-old YouTube app ver. 2.3.4. -- which works fine, but is really old, just the basic options.
Is this definitely: CM10 and YouTube can not go together? Thanks a lot!
What is this topic about?
I've spent quite some time writing fixes for GSIs to work properly on our Mi Max 3.
As part of that, we now have a list of easily flashable fully working Mi Max 3 ROMs to pick from.
This topic will be used to keep track of all fully working ROMs and of course to host the latest set of GSI patches / flash templates.
Available ROMs:
These have been tested and confirmed fully working (sans ROM-specific bugs).
AOSiP
Build date: 2019-05-14
Patch date: 2019-05-17
Flashing guide:
Unlock your device's bootloader.
Flash nijel8's modded TWRP recovery.
Pick and download one of the available ROMs.
Reboot into TWRP recovery and flash your ROM of choice.
Go into TWRP's wipe menu and "factory reset" your device (aka. slide the bar).
Flash Gapps (Opengapps / Bitgapps) if your ROM of choice requires / you want it.
Reboot your phone and set it up to your liking.
How can I get my ROM of choice listed here?
Download the TWRP package template from here!
Grab a GSI of your choice and unpack the system image (if it is compressed).
Rename the unpacked system image to system.img and place it inside the system folder inside the template zip file.
Rename the resulting zip file accordingly, flash it, test it, and after you've confirmed everything's working fine, upload and share it.
How do I enable DT2W (double-tap to wake)?
Create a file named "enable_dt2w" (without the quotes) in your device's internal storage.
Reboot your device.
Changelog:
2019-05-17
Changed cpusets to 0-7 (UX gains)
Set rendering thread to schedule as FIFO (UX gains)
Updated AOSiP to its latest (2019-05-14) build
2019-05-10
Swapped firmware & vendor base to stable 10.3.1.0
Updated AOSiP to its latest (2019-05-07) build
2019-05-01
Added two touchscreen-related properties to build.prop
2019-04-30
Updated the kernel to ResurrectedKernel 5.0 (brings a whole bunch of new governors)
Changed default little core governor to alucard
Changed default big core governor to darknessv5
Updated AOSiP to its latest (2019-04-29) build
2019-04-22
Fixed a mistake on my end that made the screen flicker on brightness changes (sorry guys)
Updated the kernel to ResurrectedKernel 4.1 (kcal support!)
Updated AOSiP to its latest (2019-04-22) build
2019-04-21
Fixed the device fingerprint issue (Magisk users should now be CTS-verified by default again)
Added AptX & AptX HD Bluetooth support
Removed DotOS & PixelExperience from the rooster because the WiFi HotSpot function wasn't working properly in them
2019-04-12
Added addon.d support (which means dirty-flashes won't lose their Gapps, Magisk, etc. anymore)
Tested and added Pixel Experience to the roster
2019-04-10
Added ResurrectedKernel (Unlocks 1.8GHz on Little Core / 2.0GHz on Big Core)
Tweaked Governor to utilize ResurrectedKernel's frequency range fully
Updated DotOS bundle to latest build
Repacked all bundles with latest patch
Dropped "Minimal Package" support as its no longer maintainable in tandem with ResurrectedKernel
It ended up with the lags (AOSIP).
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Germano1980 said:
It ended up with the lags (AOSIP).
Click to expand...
Click to collapse
Where's the lag Germano? Works fine for me.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
Stuck how? If you have "unlock" trouble, as in, your PIN won't let you in, use the "Remove lockscreen" option inside TWRP to remove your previous lockscreen data.
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
MrColdbird said:
Where's the lag Germano? Works fine for me.
Click to expand...
Click to collapse
Before installing their zip, they had some lags in screen transitions and to slide and open apps. Now, everything got more fluid and faster. It was great ... until voLTE is working (and my operator informed me that my device was not compatible with haha).
---------- Post added at 19:14 ---------- Previous post was at 19:07 ----------
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
What vendor is your device on? Many GSI's only start at a particular vendor (Oreo or Pie).
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
Make sure the GSI you picked supports Pie vendors.
Not every GSI does... and the ones that are still stuck on Oreo vendors are... troublesome, to say the least.
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
The last time I had problems in booting the GSI roms I did the following:
1- I reinstalled the latest global version of Miui Oreo via miflash (Beware of ARB)
2- Logged in the Mi account, enabled the USB debugging and installation by ADB settings to install the TWRP
3- I installed TWRP (nijel8's modded), formatted the data and then installed xiaomi.eu
4- I configured the device and made a backup of xiaomi.eu
5- As I already had the files, I installed AOSIP, without deleting the system, just cleaning the data of xiaomi.eu
6- After the boot, I installed the gapps and magisk.
I never had any problems installing GSI's on my device.
When I was in Miui Oreo, I tested some roms that only boot the Oreo vendor (Bootleggers, PixelDust among others), but I think with the Oreo vendor they spend a little more battery life.
(hope this helps you)
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Masacci0 said:
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Click to expand...
Click to collapse
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Skyllery said:
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Click to expand...
Click to collapse
So if i install this rom https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ i'm ok and without arb? I get confused because on the image they say mi max 3 has arb, if they mean the official 10.2 has arb, why even put the image in the .eu version? It just confuses people.
So i go with this rom reach setup screen, recovery and install the gsi rom?
Jesenican said:
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Click to expand...
Click to collapse
Try the xiaomi.eu versions from last month based on installing AOSiP. Today I tried with the versions of this month and did not boot.
I am having the exact same issue. I followed the guide and installed the latest xiaomi.eu 9.3.7 beta and boot no problem then i flash gsi .img and it gets stuck at MI Logo and wont go any further. I have tried latest xiaomi.eu beta, stable, last months, month before that. All xiaomi.eu boot fine without issue but as soon as I flash any gsi .img it gets stuck at MI Logo screen? Am I doing something wrong?
Also the gsi i am using is latest pixel experience arm64 A only.
Any help would be greatly appreciated.
Same. I tried 3 different GSI roms and kept being stuck on the mi logo... :'(
only aosp gsi works, still getting android.process.media and bluetooth crashes
Edit: instead of com.android.media it was android.process.media
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
jngiag said:
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
Click to expand...
Click to collapse
You're my hero! That did the trick. ;D
So can i normaly flash older xiaomi.eu version without fear of ARB?
OP post updated with a new package.
Changelog:
Tweaked the governor to boost properly and use the 1.6 / 1.8GHz maximum little / big frequencies. (Everything's even smoother now~)
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
INSTRUCTIONS
Download latest ROM, Gapps, Magisk
Reboot to Recovery
Wipe system, data, cache and dalvik
Install all
Reboot
Downloads
ROM: https://www.androidfilehost.com/?w=files&flid=306905
Gapps: https://opengapps.org/
TWRP: https://drive.google.com/file/d/1-BZiHJt2uWhVJ8rut72fbSZPDz175DMK/view?usp=drivesdk
NOTE:
Clean Flash is recommended, i.e.. Wipe data,cache,dalvik cache, system
If you dont wipe system, backuptool will reapply your modifications that support addon.d like GApps etc..
Recommended to use Pico Gapps
Device Sources: https://github.com/xiaomi-classic-dev
XDA:DevDB Information
LineageOS 17.1, ROM for the Xiaomi Mi 3
Contributors
vikash1994b, Special Thanks to Xiaomi-classic-dev Team for the sources
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Testing
Created 2020-03-29
Last Updated 2020-04-16
16.04.2020
⚛ Fixed Reboot tile, properly shows reboot to recovery
⚛ Fixed device auto wake up when lockscreen set to none.
⚛ Few kernel improvements and optimisation taken from common msm8974 devices.
⚛ LineageOS latest changes.
12.04.2020
⚛ April Security Patch
⚛ Added Pixel UI, i.e.. framework colors (check settings in dark mode)
⚛ Added Reboot/Recovery/Power off tile. Tap to change mode and long press to activate.
⚛ Improved DT2W implementation
⚛ Fixed Capacitive Keys not disabling when on screen navigation bar is enabled.
⚛Lineage Latest changes
04.04.2020
⚛ Disabled Trust warning notification for selinux and sign.
⚛ lineageOS Upstream changes.
03.04.2020
⚛ Open Gapps Compatibility: Increased Free space in System partition, now we have almost 280MB of free space,so now open gapps can be easily flashed.
⚛ Patched SafetyNet , Now SafetyNet Check passes even without Magisk.
⚛ Added Double Tap to Wake
⚛ Added Three Finger Swipe for Screenshot. Credits to MokeeRom
⚛ Implemented OTA Update, so from now on you can get updates directly via Lineage OS updater.
⚛ Device Tree Cleanup
⚛ Lineage OS upstream changes
30.03.2020
⚛ Updated Fingerprint to fix vendor missmatch
⚛ Bring in some optimsation from Android GO
⚛ Added SystemUI to PRODUCT_DEXPREOPT_SPEED_APPS
⚛ Disable SF Latch Buffer Signaled property
⚛ Enabled GL comp backpressure
⚛ Disabeld SF backpressure
29.03.2020
⚛ Initial Release
Which gapps are recommended?
[email protected] said:
Which gapps are recommended?
Click to expand...
Click to collapse
The one i use is this https://drive.google.com/file/d/1-4_3zTu56gnay4zUV_8NZgKJOXnQhh8Q/view?usp=drivesdk and it works fine.
Here are some screenshots of this rom.
vikash1994b said:
The one i use is this https://drive.google.com/file/d/1-4_3zTu56gnay4zUV_8NZgKJOXnQhh8Q/view?usp=drivesdk and it works fine.
Click to expand...
Click to collapse
And which twrp , multi rom or normal twrp
[email protected] said:
And which twrp , multi rom or normal twrp
Click to expand...
Click to collapse
Normal TWRP!
[email protected] said:
And which twrp , multi rom or normal twrp
Click to expand...
Click to collapse
File can't be downloaded , unsupported.
[email protected] said:
File can't be downloaded , unsupported.
Click to expand...
Click to collapse
As I know, twrp 3310 had some problem, so i still v3210 (3230 should be ok too) and it works fine!
You may download it from TWRP website directly, if v3230 has problem, just let me know, I can upload v3210 to g-driver later!
r30857 said:
As I know, twrp 3310 had some problem, so i still v3210 (3230 should be ok too) and it works fine!
You may download it from TWRP website directly, if v3230 has problem, just let me know, I can upload v3210 to g-driver later!
Click to expand...
Click to collapse
No problem in downloading twrp, can't download gapps.
[email protected] said:
No problem in downloading twrp, can't download gapps.
Click to expand...
Click to collapse
Ok, I will upload the BiTGapps after 10 minutes
(Opengapps doesn't work due to space issue, no matter Pico or Nano )
Edit:
Here you go!
https://drive.google.com/file/d/1-ctmk8kWrclKJ6akg-UJg_NcsSwB_z9o/view?usp=drivesdk
Very good effort...
New Lineage OS Builds is up (30-03-2020)
Download https://androidfilehost.com/?fid=4349826312261757707
Changelogs
Updated Fingerprint to fix vendor missmatch
Bring in some optimsation from Android GO
Added SystemUI to PRODUCT_DEXPREOPT_SPEED_APPS
Disable SF Latch Buffer Signaled property
Enabled GL comp backpressure
Disabeld SF backpressure
Hi, are you thinking about future releases (something like one every month or so) with bug correction and, maybe, improvements?
Can you suggest a specific kernel/camera/video driver for this builds, or the included ones are good?
Thanks.
keru32 said:
Hi, are you thinking about future releases (something like one every month or so) with bug correction and, maybe, improvements?
Can you suggest a specific kernel/camera/video driver for this builds, or the included ones are good?
Thanks.
Click to expand...
Click to collapse
I will most probably be providing monthly security updates. I dont think there are custom kernel available for cancro. So you're left with the the included one. Give it a try rom is stable enough with no major bug or FC.
vikash1994b said:
I will most probably be providing monthly security updates. I dont think there are custom kernel available for cancro. So you're left with the the included ones. Give it a try rom is stable enough with no major bug or FC.
Click to expand...
Click to collapse
Totally agree!
To this old device and with this stable ROM, monthly security updates should be enough!
I install this ROM for 2 days, no FC and no major bug (although i cannot pass the safetynet, but it is ok) very smooth with good battery performance! And the temperature also outstanding when play a game!
Thanks for the great ROM!:good:
r30857 said:
Totally agree!
To this old device and with this stable ROM, monthly security updates should be enough!
I install this ROM for 2 days, no FC and no major bug (although i cannot pass the safetynet, but it is ok) very smooth with good battery performance! And the temperature also outstanding when play a game!
Thanks for the great ROM!:good:
Click to expand...
Click to collapse
There is a workaround to pass safetynet on latest build. You need to install magisk and enabling magisk hide.
vikash1994b said:
I will most probably be providing monthly security updates. rom is stable enough.
Click to expand...
Click to collapse
Excellent, what else is required for a legendary device.
Unbelievable that this solid device will get a stable build of lineage os 17.1 - mother of all custom roms even after so many years. Thank you very much.
vikash1994b said:
There is a workaround to pass safetynet on latest build. You need to install magisk and enabling magisk hide.
Click to expand...
Click to collapse
Thanks for the information, i tried it but no lucky, its okay, to me, not an issue!
But could you check the Bluetooth is functional our not?
Tried to using BT but seems not working?
Thanks in advance!
Installed the rom. It's very smooth and stable. Battery is also doing fine. Didn't put a sim and check it. Installed magisk 20.3 and updated to 20.4.
Gapps by the op is working, opengapps could not be installed.
My son played some games with it and was satisfied with its performance.
Haven't checked BT.
Installed YouTube vanced black edition from magisk download.
Will try to install magisk modules for safetynet bypass.
The speaker of my phone is faulty so can't comment about sound.
The rom is an excellent build and the device has surpassed itself.
I wanted to install a gcam port for it. I tried several builds but none of them could even be installed. (i know I'm off topic here). I'll delete this line if the op takes an exception. So if anyone is aware of any working gcam build/port kindly tell me. The device has an excellent sensor for camera.
Also an option to use power menu on the hardware button long press / double tap would have been very useful. I'm presently using a 3rd party app from play store for power off /reboot /reboot to recovery etc as the power button is on the way to its grave due to old age. Otherwise the device is in excellent condition.
Double tap to wake is a very desirable feature due to power button eol and volume button wake is there but these also might get finished due to regular use.
Am using greenify and gravity based wake up to save the power button.
Now I'm on ArrowOS Pie. I need to move to the other rom because i can't enable data(4g) in this rom, well it can if i do the trick everytime if i want my data still in 4g, but it takes a goddamn time.
So can anyone suggest me best rom for redmi 3x 2gig ram version, i don't need a lot of customization or whatever and not a miui, just almost stable and phone service work like a charm(and oreo,pie, or android 10 I guess).
Please help, and thank you very much, sorry for my bad english
Reportedly Havoc 3.4 works well in 2GB devices. I would think LOS as well.
Personally I am on LOS 15.1 by e/ foundation. microG is built-in and monthly security patches. Almost always 1GB RAM available. But I did make the switch to some lightweight apps as well to reduce memory usage. If you want lots of customization or aesthetics matter more don't bother with it.
---------- Post added at 06:46 PM ---------- Previous post was at 06:42 PM ----------
amn1987 said:
Reportedly Havoc 3.4 works well in 2GB devices. I would think LOS as well.
Personally I am on LOS 15.1 by e/ foundation. microG is built-in and monthly security patches. Almost always 1GB RAM available. But I did make the switch to some lightweight apps as well to reduce memory usage. If you want lots of customization or aesthetics matter more don't bother with it.
Click to expand...
Click to collapse
Edit: You can flash microG in say Havoc/LOS and get decent RAM savings. Although in my experience Oreo(Android OS+System) uses less RAM compared to P/Q.
Also a minimal GApps package like BitGApps if microG isn't to your liking.
Official LineageOS 16.0, without a doubt. Every other ROM has some or the other issue.
If you don't care about Google home/cast, then use the LineageOS MicroG official image, else flash it with pico Gapps.
atomickaushal said:
Official LineageOS 16.0, without a doubt. Every other ROM has some or the other issue.
If you don't care about Google home/cast, then use the LineageOS MicroG official image, else flash it with pico Gapps.
Click to expand...
Click to collapse
but i saw that LOS 16 or some Pie ROM had a problem with mobile data, is that happenned to you? because arrowos has that kind of problem
morod3r said:
but i saw that LOS 16 or some Pie ROM had a problem with mobile data, is that happenned to you? because arrowos has that kind of problem
Click to expand...
Click to collapse
No, never. I use 2 sims all the time. One runs on 4G LTE with VoLTE and the other on 2g.
Data works as expected. No issues with the ROM so far.
You can also flash the android low RAM enabler mod. RAM savings are significant. For instance in AEX Pie RAM usage fell by 100-150MB. That in conjunction with microG is sufficient for a decent multitasking experience. If microG is a tad too radical try a lighter GApps package like BitGApps. It even has GMS Doze Optimization built-in.
Hello everyone!
This is a dotOS port from the Galaxy J3 2016 (made by @lucas000br) to the J2 2016.
Working:
My (basic) testings all seemed to work quite well
Added features and patched bugs:
Patched lock button in boot.img
Pre-rooted the ROM
Added FM-Radio from ViperOS (microG variant only)
Optimized features
Signature spoofing patched on microG variant
[See post #2 for further information]
Known problems:
Gapps variant is laggy (nothing I can do - Google sucks)
Your J2 shows up as a J3 (it's a port that's why)
Download links and installation instructions can be found in post #2
Credits:
Nanolx for Signature Spoofing
PixelBoot for base
lucas000br for modified base
Me for everything else
Obligatory Links:
Kernel Source: Github
Original Build (Abandoned by PixelBoot): XDA Developers (No source code)
Port of Port (by lucas000br): Thread seems to have disappeared?
Variant information (Which one is which?)
GAPPS: This one has most of the stock Google apps (Drive, YouTube, etc) + GSF present. Recommend for most users. RAM usage 640mb on idle
microG: All Google apps have been replaced with FOSS software. Google Services Framework has been replaced with microG. Signature spoofing is also present. RAM usage 560mb on idle
DIY: Want to build your own ROM? This one's for you! Everything except the bare minimum has been stripped out, so that you can decide what to pick for your ROM. (For power users only).
Stock dotOS: The stock dotOS compiled by PixelBoot for J3 2016; with Wi-Fi, Bluetooth, Signature spoofing and Power Button patched. Most stable out of all. You will need to flash additional GAPPS to get Google Services. RAM Usage 500mb.
Download Links:Stock dotOS (Recommended): MEGA
GAPPS: Oreo-Themed dotOS
microG: Oreo-Themed dotOS
DIY: Oreo-Themed dotOS
Installation Instructions:[If you don't have TWRP, get an image and install it from here]
GAPPS:
Boot to TWRP
[Do make sure to backup your data]
Wipe Dalvik, Data, System, Cache
Flash the ROM
Reboot. Done!
microG:
Boot to TWRP
[Do make sure to backup your data]
Wipe Dalvik, Data, System, Cache
Flash the ROM
After rebooting, open microG settings.
Go to self-check and tick the check boxes that are unticked (that will initialize microG)
Go back, and enable Device Registration, Cloud Messaging and Device Attestation
Then go to Location backends, and configure the DejaVu and Nominatim backends.
Done!
DIY and Stock dotOS will be the same as GAPPS variant
Changelog:
v1.2: Initial release06/05/2021: After lucas' comment, I realized that this wasn't the stock dotOS. So I have ported the stock dotOS created by PixelBoot. Try it out!
lucas000br said:
well done!
Also, PixelBoot did the DotOs base rom, i just modified it to be more like Android Oreo
(dont worry because i credited PixelBoot in the original j3 thread)
Click to expand...
Click to collapse
oops I need to credit him
Thanks for informing!
good soon try it out
i have flashed stock rom provided by u of dot os but my phone stuck at samsung logo pls look into it .....i am sure i have flashed it n follow all steps correctly
Uniqueshiva said:
i have flashed stock rom provided by u of dot os but my phone stuck at samsung logo pls look into it .....i am sure i have flashed it n follow all steps correctly
Click to expand...
Click to collapse
okay I'll try flashing it again. wait
NullCode said:
okay I'll try flashing it again. wait
Click to expand...
Click to collapse
btw i don't have stock rom installed before i flash it......I am on viper os....then i boot to twrp wipe sytem cache data n flash your provided dot os stock rom then i reboot but stuck at Samsung logo
@Uniqueshiva thank you for the information. I had made a typo in the updater script that caused the boot image to fail.
Please download the new ROM and flash it. I've confirmed it to work
NullCode said:
@Uniqueshiva thank you for the information. I had made a typo in the updater script that caused the boot image to fail.
Please download the new ROM and flash it. I've confirmed it to work
Click to expand...
Click to collapse
thx for responding so fast btw i will try it tomorrow as my data got finished today sorry for it...i will surely give feedback
edit- I tried stock dos os rom n flash arm 7.1 Pico gapps...boot animation appears but after sometimes black-brown screen appears after 5 min phone started but its written setup wizard failed i am not able to go ahead as setup wizard failed written every time so i turn off the phone maybe it can be the gapps problem now i will try dot os magisk gapps version provided by u btw i am curious that what is DIY dot os u give is all bugs fixed in it just asking..
Uniqueshiva said:
thx for responding so fast btw i will try it tomorrow as my data got finished today sorry for it...i will surely give feedback
edit- I tried stock dos os rom n flash arm 7.1 Pico gapps...boot animation appears but after sometimes black-brown screen appears after 5 min phone started but its written setup wizard failed i am not able to go ahead as setup wizard failed written every time so i turn off the phone maybe it can be the gapps problem now i will try dot os magisk gapps version provided by u btw i am curious that what is DIY dot os u give is all bugs fixed in it just asking..
Click to expand...
Click to collapse
hmm it could be flashing gapps causes problem with the rom...
yes try the gapps version i provided
the diy one is mainly for rom porters. it has many features removed so that rom porters can think about what features to add in the rom
only basic feature available in rom is phone and messaging support
I can't access internal storage after flashing. Stock file manager crashes if i open it. Stock browser says "no sd card, usb storage is required to download the file". There's no internal storage even after connecting the phone to pc. It only shows memory card.
Edit: Just wiped the internal storage and re-flashed it. Works fine now
Thanks for porting this amazing rom
@NullCode, thanks for your work for device j210f...I like the ui of dot os..but i must say your previous build i.e viper os was more stable n amazing atleast for me....btw thanks a lot for keeping this device alive...
Dark theme not working in settings and other apps.Any help?
shayara said:
Dark theme not working in settings and other apps.Any help?
Click to expand...
Click to collapse
there's a theming option in settings > display > scroll to the end
from there figure out what to do (I've confirmed its working)
Uniqueshiva said:
@NullCode, thanks for your work for device j210f...I like the ui of dot os..but i must say your previous build i.e viper os was more stable n amazing atleast for me....btw thanks a lot for keeping this device alive...
Click to expand...
Click to collapse
I know, viperOS was much more stable because I took 1 entire year to port and test the rom (i started testing January 2020 )
however, dotOS was ported in only 1 month
so it is not as polished
but im glad you liked it
NullCode said:
Hello everyone!
This is a dotOS port from the Galaxy J3 2016 (made by @lucas000br) to the J2 2016.
Working:
My (basic) testings all seemed to work quite well
Added features and patched bugs:
Patched lock button in boot.img
Pre-rooted the ROM
Added FM-Radio from ViperOS (microG variant only)
Optimized features
Signature spoofing patched on microG variant
[New] 2 more ROM options to choose from (with varying features)
[See post #2 for further information]
Known problems:
Gapps variant is laggy (nothing I can do - Google sucks)
Your J2 shows up as a J3 (it's a port that's why)
Download links and installation instructions can be found in post #2
Credits:
Nanolx for Signature Spoofing
PixelBoot for base
lucas000br for modified base
Me for everything else
Note: You might've noticed how I didn't put [PORT] in the thread title. It is mainly because this ROM varies from J3's dotOS so much, I don't think it is fair to call this one a port.
Click to expand...
Click to collapse
Hey.
I am using this ROM since 6th May (stock variant) and it is very great but has lots of bugs.
1. Bluetooth Audio stutters really bad (problem in every Android N rom for this phone)
2. Google Meet doesn't work (just shows the logo and then crashes) I am using Open GAPPS
3. Many system app crash randomly (sometimes even the launcher and system ui) requiring me to take out the battery and restarting the phone.
4. Camera quality is significantly bad compared to stock 6.0
But still a great project.
Thank you for keeping this phone updated.
NullCode said:
there's a theming option in settings > display > scroll to the end
from there figure out what to do (I've confirmed its working)
Click to expand...
Click to collapse
Okay.Thnx.
NullCode said:
I know, viperOS was much more stable because I took 1 entire year to port and test the rom (i started testing January 2020 )
however, dotOS was ported in only 1 month
so it is not as polished
but im glad you liked it
Click to expand...
Click to collapse
Omg 1 year......that's y it feels so smooth in viper os i get nearly 900 mb free ram with gapps again thanks for your hardwork.....I know that u may be bored now for working on j210f that is old device but still hoping for more
Uniqueshiva said:
Omg 1 year......that's y it feels so smooth in viper os i get nearly 900 mb free ram with gapps again thanks for your hardwork.....I know that u may be bored now for working on j210f that is old device but still hoping for more
Click to expand...
Click to collapse
My build has more free ram and battery btw.