{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Features
FlokoROM v4 is based on crDroid 7.x , but there are some differences.
Floko-specific features:
OmniSwitch included
Trebuchet as a default Home Launcher
Bromite as a default Web Browser
Kawaii Easter Egg in Floko Settings
Remove Music Player (install what you like)
Remove Navbar design customization
Remove non-free LongScreenshot
Remove non-free FaceUnlock feature
Remove non-free font packages
crDroid and LineageOS features:
Battery bar
Lockscreen customization
Navigation bar customization
Network traffic monitor
QS columns
QS/Notifications opacity
Screenshot quality
Statusbar Quick/Smart pulldown
Style(Theming)
Switch 4G/LTE icon
Volume panel customization
VoLTE icon customization (if available on your device)
Known Issues
When the phone is powered off from Lineage and the battery is not removed, the battery charge will fall at an approximate rate of 2% per hour of time that the phone is powered off without the battery having been removed since it was powered off. This does not occcur when powering off from TWRP, having first powered up to TWRP or rebooted to TWRP from Lineage. It also does not occur if the battery is removed from the phone before being put back in, either after powering off from Lineage or being pulled out while Lineage is running. This bug has affected the apq8084 chipset since Oreo (as described by the S5 Plus community, which uses the same chipset). However, the S5 Plus had received official lineage-15.1 and 16.0 support despite being affected by this bug. Furthermore, we have deduced that it must be caused by one or more of the 652 commits that separate the Nougat and Oreo kernel branches. We will never have the time to go through each and every one of these commits to fix this bug outright, but we are always open to suggestions.
If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
The 2nd SIM slot does not work in any trlteduos variant.
VoLTE is not supported, and will not be supported for the foreseeable future.
If you encountered other issues, please tell me
How to Install
MAKE A BACKUP OF ALL YOUR DATA.
(First time) Wipe Data, Cache, Dalvik
Flash ROM, GApps, Magisk(optional), ...
Reboot to System
Enjoy.
Thanks
love. respect. and love.
crDroid
LineageOS
OmniROM
Team
@1indwurm
Credits
ripee
Inkypen
IogosA
ghostwheel
ananjaser1211
khalvat
triplLr
lindwurm
Flominator
Downloads
FlokoROM Initial Release:
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos (experimental)
- SM-N915F/G/P/R4/T/W8: tblte
FlokoROM September release:
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos (experimental)
- SM-N915F/G/P/R4/T/W8: tblte
Changelog:
- fixed lag on bromite in certain videos
- fixed cpu performence settings
- selinux is enforced
- updated security patches
Reporting Bugs
DO NOT report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Source Codes
FlokoROM: github.com/FlokoROM
Device tree: apq8084
XDA: DevDB Information
FlokoROM v4, ROM for Samsung Galaxy Note 4
Contributors
Flominator, ripee, Inkypen, logosA, ghostwheel, ananjaser1211, khalvat, tripLr
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Beta
Current Stable Version: 11
Stable Release Date: 2021-06-04
Created 2021-06-04
Last Updated 2021-09-13
are u sure N9100 is a tblte and N915 is trlteduos ? not swapped ?
boy_venz21 said:
are u sure N9100 is a tblte and N915 is trlteduos ? not swapped ?
Click to expand...
Click to collapse
thanks for notice fixed now
Good job!
FlokoROM + BiTGApps
based on Android 11 (Lineage OS 18) (crDroid 7). Feels stable after 2 days' use. Does not crash.
SIM works.
fingerprint sensor (swipe) works.
Bank app works.
Have not tried installing Magisk. It is because the Bank app already works and I don't want to mess up.
crDroid 6.12 + opengapps
based on Android 10 (Lineage OS 17). Crash from time to time.
Sometimes the SIM card is not detected, and restart / reboot is needed.
fingerprint sensor does not work.
Bank app does not work. I have tried everything at Magisk.
Magisk can be installed (flash zip file).
Hope you like the above comparison. SM-N9100. TWRP 3.5.2. By the way, the 2nd SIM card slot not tested. GPS tested, but does not work. Google location service (Wifi) works
ROM RUNS VERY SMOOTH, I THINK THAT HAVE A BIT BETTER THAN CRDRID ROM 7.6, WELCOM TO DISCUSS TI IN HERE.
Best ROM I've ever used on this device. Bar none. Even better and more stable than the ROM it's based on (crDroid). So, hats off to you.
The problem I've had with it, however, is that there are a few apps that aren't allowed to function the way they are supposed to. These apps do function properly on crDroid 7.6, therefore it must be because of the adjustments made to that ROM.
The problems I've had are with apps that are supposed to have access to the system or root folders and are not afforded FULL access. I've noticed this with all the file managers I've used. But, my primary file managers are MiXplorer and X-plore.
I've been able to rename files in the system or root areas, but not copy anything to those areas. And, yes, I have given these programs all the permissions they have asked for (and then some). And I have uninstalled them, then reinstalled. Still, they don't function properly. MiXplorer doesn't even save it settings connsistantly (even though it did on crDroid 7.6). You make adjustments in settings and exit the program and immediately restart ... it may keep those settings changes on that restart, but after awhile, once you restart the program, sometime later it, reverts back to factory default settings. Strange. Never seen that before.
This also seems to be why a program like Elixr 2 does not function as intended (even though it does on crDroid 7.6). I can save a backup in the program, however, even though I can copy a backup of my older custom backup widgets, etc., to the programs backup location (something I've done for years - across multiple ROMS - and with crDroid 7.6), once you try to restore from backup it says "No permission to use this feature". Never see that before.
So, I appreciate all your work. I just hope this is a kink you can figure out and get adjusted.
Thanks, a lot!
This ROM looks great, thank you for making it. Been on crDroid 6.12 for quite a while and been very happy with it but need to update.
Does this ROM have signature spoofing built in? I want to run microG. Root with magisk no problem? Will wait for confirmation before I install.
BTW super cool to include OmniSwitch, by far my fave recents/switcher.
Apex Predator said:
This ROM looks great, thank you for making it. Been on crDroid 6.12 for quite a while and been very happy with it but need to update.
Does this ROM have signature spoofing built in? I want to run microG. Root with magisk no problem? Will wait for confirmation before I install.
BTW super cool to include OmniSwitch, by far my fave recents/switcher.
Click to expand...
Click to collapse
hello, In ternms of signature spoofing its the same as lineage 18.1. I personaly at testing had no problems with root espacialy magisk and micro G. Issues with read write in root I cant confirm.
It seems that trlteduos has a problem, how to fix this?
"assert failed: run_program("/tmp/install/bin/variant_blobs.sh")==0"
Do you have any other Android 11 ROMs for trlteduos?
VerdghXeljior said:
It seems that trlteduos has a problem, how to fix this?
"assert failed: run_program("/tmp/install/bin/variant_blobs.sh")==0"
Click to expand...
Click to collapse
seems to be an common issue with trlte duos roms. Idk why. Any help is welcome.
This is the first Snapdragon ROM on my N910V (Verizon model) that HAS NOT brought up the Maintenance Mode upon reboot. I've rebooted probably 50 times and haven't seen it even once!
This ROM seems to work very well on that device, but I have dropped Wifi a few times. No cellular card in this one, so can't verify that feature.
Since I mainly use these devices for watching TV and videos, I'd like to get Dolby working, or even viper, but no luck so far.
UPDATE: After 1 week, the wifi just stopped working. It just won't start, but everything else seems fine. I was able to install Dolby Atmos eventually and it works now, but without Wifi, it's useless to me. I reverted back to an Android 10 ROM and it's functioning just fine now, proving its not the device.
Tried this ROM. What i noticed is that the CPU speed never dips below 1958Mhz, and it never goes into deep sleep.
Other than that i've had no issues with this ROM. Used it in my spare phone without a SIM so it didn't get that thorough of a workout.
lowfatmilk said:
Tried this ROM. What i noticed is that the CPU speed never dips below 1958Mhz, and it never goes into deep sleep.
Other than that i've had no issues with this ROM. Used it in my spare phone without a SIM so it didn't get that thorough of a workout.
Click to expand...
Click to collapse
hi, this is intendet to get decent performence, to change that, use performence settings in the battery section.
Yeah, tried that. Doesn't seem to let me lower the base CPU speed below 1958Mhz tho.
I must be missing something.
-- Phone runs a little warm with the CPU set up like this, but it certainly is more fluid than it used to be.
any updates to floko or cr
hi everyone i have samsung note 4 910f and i flash many rom including this floko and cr, mostly of them work fine for few days, then i got random freeze from Ui, application start to not open, till some time the phone completely shutdown and i need the remove the battery.
i bought a brand new battery for see if the problem are the same, but nothing change, i roll back to the stock rom, and after few time the problem come back.
all my flashing are with the latest twrp except for the stock i use odin, in the twrp i use to wipe all of them (dalvik/ art cache, system , data, cache, internal storage). may i do something wrong? it is normal to have baseband and bootloader from the old stock samsung firmware (see attach file)
thanks in advance and sorry for my english
boss472 said:
hi everyone i have samsung note 4 910f and i flash many rom including this floko and cr, mostly of them work fine for few days, then i got random freeze from Ui, application start to not open, till some time the phone completely shutdown and i need the remove the battery.
i bought a brand new battery for see if the problem are the same, but nothing change, i roll back to the stock rom, and after few time the problem come back.
all my flashing are with the latest twrp except for the stock i use odin, in the twrp i use to wipe all of them (dalvik/ art cache, system , data, cache, internal storage). may i do something wrong? it is normal to have baseband and bootloader from the old stock samsung firmware (see attach file)
thanks in advance and sorry for my english
Click to expand...
Click to collapse
pls, try to log errors. you can is matlog for example, this my give you a hint whats wrong with your phone
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM/KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
* BOOM! goes the dynamite
*/
Hi XDA community, we are proud to present our vision of LineageOS with features that we think are useful. Hope you enjoy our builds as much as we do. The main goal of Nuclear Team is to provide a clean and fast ROM with nice, minimal and useful features.
• Based on LineageOS 14.1 by @Hashbang173
• Built for Stock Nougat Kernel and Modem
• Android version 7.1.2_r29
• Optimized for fast app opening and disabled lot of debugging
• Nuclear Settings
• Customizable status bar (Clock position, Date, Network Indicators, Battery style and such)
• Gestures Anywhere
• Switch To Hide SuperSU from Status Bar
• Ambient Display (Pick-up and Hand wave)
• Network traffic indicator
• Three finger swipe to screenshot
• Show CPU info
• DT2S everywhere on lockscreen
• Options to modify Dash board/Quick Settings (Number of columns)
• Option to disable warning color on Low Battery
• OmniSwitch
• Option to reset Battery history stats
• Enhanced dialer with smart call feature
• MicroG and signature spoofing support to use the ROM without GApps
• Enhanced system animation scale sliders in developer options
• Screen pinning selection in recents
• Show current and new version in package installer
• Option to disable screenshot sound
• More volume steps
• Substratum and Magisk tile in dashboard (if installed)
• QS tiles animations and row/columns configuration
• Alert slider modified with more options
• Wakeblock app support and baked into rom's zip ( more info Here ) all credits for @GioBozza
• Launcher3 with Google now gesture and icon support
• Exclusive NucleaRom wallpaper app
• AOSPA color engine (Accent color)
• All LineageOS goodies
Known Bugs:
Initial Release. But I couldn't find any.
-If you have a major bug to report that has not been reported already, and is not a known issue with CM,
please take the following steps to report it to us. It will save you time, as well as us.
- Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
- After downloading the Catlog app, go to the app settings, and change the log level to Debug.
- Clear all previous logs and take the exact steps to produce the error you are receiving.
- As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
- Copy and paste the entire log either to Hastebin or Pastebin
- Save the log, and copy and paste the link into the forum with a brief description of the error.
- You can also open trouble tickets on our website for bugs.
If you have flashed any third-party module and experiencing instability or whatever then please don't submit any bug report. You will be ignored.
First install (clean Flash) (If you come from another ROM or another Android version)
× Read the whole OP and make sure that you understand what is written here.
× Make a nandroid backup (optional but always recommended)
× Install Custom Unofficial TWRP
× Download Latest ROM
× Download 7.1 arm64 GApps
× Wipe System, Data, Cache, Dalvik-cache
× Flash Latest build for your device
× Flash ROM
× Flash GApps (optional)
× Flash your preferred Root method (optional)
× Reboot
Important note:
× Upon first boot, Disable the 'wakeblock' app. Device is safe to use after that.
× For safer side, you can permanently remove it by deleting /system/app/wakeblock folder.
Updating:
× For now, Uninstall Magisk (if installed)
× Flash Latest Build
× Wipe Cache, Dalvik-Cache
× Reboot
× Install Magisk (optional)
Goodluck, Have Fun and Enjoy!
LineageOS
@Hashbang173
@acuicultor
Lord Boeffla
Temasek
Ak
ResurrectionRemix
Aicp
Aospextended
XDA
Flar2
Grarak
Koenkk
nvertigo
GioBozza
Nuclear Team & testers
And a very special thanks to TugaPower
Anyone I might have forgotten (please let me know)
Main devs are @Moludo, @lozo2010, @Ordenkrieger and @acuicultor is the kernel Dev.
Telegram support chat:HERE
If you want to buy us a beer/coffee you can donate Here all donations will serve to improve the rom.
Thanks to all donors!!!!
@AlkaliV2
Please when do a donation tell your xda nickname in paypal message so i can give you proper credits here. Thanks.
XDA:DevDB Information
NucleaROM for Moto X Style/Pure (clark), ROM for the Moto X Style (Pure)
Contributors
antariksh, Hashbang173
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Stock Nougat 7.0
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: Initial Release
Beta Release Date: 2018-01-01
Created 2018-01-01
Last Updated 2018-03-03
Doing this because everyone does it.
Consider this as my excitement! xDD
A new year Gift. Thank you for keeping our device alive. Downloading now, gonna flash soon. Cheers!!
This looks awesome and I'm trying to install it but every time I try to wipe the old ROM, the phone just reboots. I'm on the Carbon by obsolete1, any ideas?
ccic2491 said:
This looks awesome and I'm trying to install it but every time I try to wipe the old ROM, the phone just reboots. I'm on the Carbon by obsolete1, any ideas?
Click to expand...
Click to collapse
Use this TWRP, it's built for Nougat Based ROMs
OP updated.
antariksh said:
Use this TWRP, it's built for Nougat Based ROMs
OP updated.
Click to expand...
Click to collapse
Sorry mate but can you provide me recovery img to flash through twrp?
Need a twrp for nougat
My pc is broken
andreskafe said:
Sorry mate but can you provide me recovery img to flash through twrp?
Need a twrp for nougat
My pc is broken
Click to expand...
Click to collapse
You can flash the recovery.img from TWRP itself. Go to the directory and tap 'Install Image' button. Select the recovery partition and flash.
ROM has been pretty stable for me, good amount of customization without overkill.
Performance is snappy, about equal to Hashbang's LOS that this is based on but with similar bugs, I'm guessing likely kernel & modem related:
• Wifi-Calling being on still causes silence when a call connects (Simple Mobile). Also makes me think that having it off is causing a lot of calls to go straight to voicemail instead of ringing.. could be coincidence
• Had the no notification/ringers/alarms bug initially but swapping my own sound files in, giving them the proper permissions, reboot with a dalvik & cache clear and it worked again (before on LOS and I think RR I had to replace audio xml files for it to work which i think caused new different audio related issues)
• Usual slow camera, flashlight bugs, no big deal
Really interested in the MicroG features and curios whether something has to be done in the ROM specifically to set it up. Would it improve battery life enough to go through the trouble?
acyd said:
• Had the no notification/ringers/alarms bug initially but swapping my own sound files in, giving them the proper permissions, reboot with a dalvik & cache clear and it worked again (before on LOS and I think RR I had to replace audio xml files for it to work which i think caused new different audio related issues)
Click to expand...
Click to collapse
I dont have this issue on NR. Funny enough. I did om rest.
I see no real hickups. All working here. Full pulldown on notifacation/ followed by edit, will freeze a sec, and go back to home screen, but just once each time - no biggie. Just a edit problem, once set up np.
But would like to see an option to see ram usage in recent, not just omni, no fan of omni Lol personal prefference. Absolut not a must, just so used to have it there.
Other than this GJ, new dayly driver. Ty. :highfive:
If my help can be used for some, just throw a holla OP :good:
acyd said:
ROM has been pretty stable for me, good amount of customization without overkill.
Performance is snappy, about equal to Hashbang's LOS that this is based on but with similar bugs, I'm guessing likely kernel & modem related:
• Wifi-Calling being on still causes silence when a call connects (Simple Mobile). Also makes me think that having it off is causing a lot of calls to go straight to voicemail instead of ringing.. could be coincidence
• Had the no notification/ringers/alarms bug initially but swapping my own sound files in, giving them the proper permissions, reboot with a dalvik & cache clear and it worked again (before on LOS and I think RR I had to replace audio xml files for it to work which i think caused new different audio related issues)
• Usual slow camera, flashlight bugs, no big deal
Really interested in the MicroG features and curios whether something has to be done in the ROM specifically to set it up. Would it improve battery life enough to go through the trouble?
Click to expand...
Click to collapse
Thank for the feedback.
Link me your audio files, I'll take a look and compare if anything is missing.
ROM boot and works without GApps. I have been installing test builds without GApps. You just have to manually install each apk and restore contacts.
Only thing that affects battery when using ROM with GApps is Location History, you can turn it off. Also you can disable Google Assistant so it won't run background processes to detect OK Google. It would get you almost similar battery life, as using without it.
As for WiFi-Calling, I don't think so we have that in India, so I can't test or even try to debug.
Dioser said:
I dont have this issue on NR. Funny enough. I did om rest.
I see no real hickups. All working here. Full pulldown on notifacation/ followed by edit, will freeze a sec, and go back to home screen, but just once each time - no biggie. Just a edit problem, once set up np.
But would like to see an option to see ram usage in recent, not just omni, no fan of omni Lol personal prefference. Absolut not a must, just so used to have it there.
Other than this GJ, new dayly driver. Ty. :highfive:
If my help can be used for some, just throw a holla OP :good:
Click to expand...
Click to collapse
Sure, Thanks. I just started getting into this stuff, so I'll try to get as much as help from the community itself.
Umm.. RAM usage in Recent? Have you seen any other ROM with that feature? It will be good for some reference, if am attempting to do that.
antariksh said:
Sure, Thanks. I just started getting into this stuff, so I'll try to get as much as help from the community itself.
Umm.. RAM usage in Recent? Have you seen any other ROM with that feature? It will be good for some reference, if am attempting to do that.
Click to expand...
Click to collapse
RR have this feature m8. Likewise CR. So my guess is most los. But cant seem to find it anywhere here. Went it all through step by step.
But its not a must in any kind.
Ill go look for the settings in RR also if you need med to?
I have no device with RR atm, but an s5 with CR nougat. I guess its maybe an aosp recents? Says so in CR recent screen settings, if any help. Have no SD card back before tomorow, and ill then reflash RR and screen the settings. Ill add two of CR settings. Its on Sgs5 though, but they look the same, and had the same on the xt1572 RR/CR
Im no developer my self.
But done some dif testing back in the days with insanity and slim. those days. So by me saying holla if need help, is could you test this for me, then OFC!
Dioser said:
RR have this feature m8. Likewise CR. So my guess is most los. But cant seem to find it anywhere here. Went it all through step by step.
But its not a must in any kind.
Ill go look for the settings in RR also if you need med to?
I have no device with RR atm, but an s5 with CR nougat. I guess its maybe an aosp recents? Says so in CR recent screen settings, if any help. Have no SD card back before tomorow, and ill then reflash RR and screen the settings. Ill add two of CR settings. Its on Sgs5 though, but they look the same, and had the same on the xt1572 RR/CR
Im no developer my self.
But done some dif testing back in the days with insanity and slim. those days. So by me saying holla if need help, is could you test this for me, then OFC!
Click to expand...
Click to collapse
I also have RR Unofficial build released in other thread. I'll check out. Thanks
Hi
Thanks alot for your great work on this smooth rom
The only issue that i have until now is the recent button that coudnt be changeable , its gray and i can't change that split screen to another function
antariksh said:
I also have RR Unofficial build released in other thread. I'll check out. Thanks
Click to expand...
Click to collapse
Yeah i saw u threw it up, but didnt try it bro
Low on anyones priority.. but has anyone tried this rom with Fly Delta app to access their Delta account ?
I have reports it will work on stock nougat rom for clark.. I have mm modem , have never installed stock N.. but no custom N rom I have tried for clark will it work on
Thanks
antariksh said:
Thank for the feedback.
Link me your audio files, I'll take a look and compare if anything is missing.
ROM boot and works without GApps. I have been installing test builds without GApps. You just have to manually install each apk and restore contacts.
Only thing that affects battery when using ROM with GApps is Location History, you can turn it off. Also you can disable Google Assistant so it won't run background processes to detect OK Google. It would get you almost similar battery life, as using without it.
As for WiFi-Calling, I don't think so we have that in India, so I can't test or even try to debug.
Click to expand...
Click to collapse
Thanks for your work on this and reply. What audio files are you referring to? I just have my own ogg & wav files which i put into the subdirectories in /system/meda/audio and delete the stock ones, change permissions and go from there.
Regarding the MicroG, my most recent knowledge is from here: https://lineage.microg.org/#instructions which mentions a MicroG settings app that masks itself sets up "google" services for the apps that require it. GCM etc. That's what I was looking for but didn't find here so was just wondering It's open-source as far as I know, would it be possible to include in some future version of the ROM?
Another bug I've had recently is phone calls not waking the screen.
I am absolutely happy with the ROM. Not finding anything wrong. Being a moderate user I feel Nuclea works perfectly. A small glitch while opening camera. It takes a bit more time than usual. Otherwise no issues.
chandruilkal said:
I am absolutely happy with the ROM. Not finding anything wrong. Being a moderate user I feel Nuclea works perfectly. A small glitch while opening camera. It takes a bit more time than usual. Otherwise no issues.
Click to expand...
Click to collapse
Try ditch the linage cam for moto cam.
https://androidfilehost.com/?fid=673791459329060250
I know I did :good: (flahsable zip)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Galaxy A3 2016 | a3xelte | SM-A310xx
OFFICIAL | Android 9.0
Download
Changelog:
Code:
[COLOR="Teal"]2019-07-07[/COLOR]
- More SELinux fixes (Stricted)
- Remove old implementation of Keydisabler and use Lineage Touch HAL instead (Stricted)
- dotOS 3.1 with many UI improvements and new features
- June 5 Security Patch
- Camera deadlocks are gone now (at least when using default Snap Camera) by fixes in the camera wrapper (danwood76)
- Updated stock vendor blobs (danwood76)
- Improve WiFi battery consumption by enabling the capability of the WiFi firmware to scan efficiently in the background in the framework-res overlays (danwood76)
- Add missing magnetometer config file in vendor/etc/yas_set.cfg (danwood76)
[COLOR="Teal"]2019-05-16[/COLOR]
- Update vendor security from 2018-07-30 to 2019-02-01
- Switching to NFC force download mode in libnfc-sec-hal.conf to improve reliability although turning on can take longer (danwood76)
- More SELinux fixes (danwood76)
- Fixed kernel issue from stock that the device was not charging sometimes (danwood76)
- May 05 2019 security patch (danwood76)
[COLOR="Teal"]2019-04-10[/COLOR]
- Fixed Tethering and Hotspot by enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel defconfig (danwood76)
- Much more kernel improvements (danwood76)
- Cleaned up ramdisk
- April 05 2019 security patch
[COLOR="Teal"]2019-03-29[/COLOR]
- More SELinux fixes (danwood76)
- Touchkeys are now also disabled when the display is turned off (danwood76)
[COLOR="Teal"]2019-03-26[/COLOR]
- Initial Release
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
Installation instructions:
1. Make sure you have TWRP installed on your device to be able to flash the rom.
2. Download the latest build from the link above and copy it to a place where you can find it later.
3. Optionally download GApps for using the Play Store and other Google related services from here: https://opengapps.org. Choose ARM as architecture and 9.0 as the OS version. The size of the GApps package is upon to you how much apps you want to have preinstalled. Copy this zip aswell to a place where you can find it easy later. If you download it with Chrome or with the Google Drive App it should be by default in the Download folder.
4. Turn your phone off and press Volume UP + Home Button + Power button at the same time until the splash screen appears. Then your device should boot into the recovery. There you wipe following partitions: Data, System, Cache, Dalvik if this is your first install. All of your installed applications get lost by this. Your photos, videos etc. won't get deleted if you haven't ticked the box for internal storage. As the kernel also supports F2FS i would change the filesystem for the cache partition from ext4 to f2fs for a better system performance. Now go to the main TWRP menu, click on install and go to the place where you have placed your zips and first select the rom and then click on the left button if you have downloaded the optional GApps package to add another zip to the queue. Now swipe the slider at the bottom to install and reboot the phone to the system. The first boot can take a while and after booting you could experience some lags because of the GApps initialization but they should disappear after some time.
4. Now you have successfully installed the rom and you're ready to use dotOS on your device. Congratulations!
Bugs:
- VoLTE (isn't working on samsung devices and won't work anytime in the future too)
- HWC isn't enabled yet (could lead to a bit performance decrease in apps with alot of layers)
XDA:DevDB Information
dotOS 3.1 for the Galaxy A3 2016, ROM for the Samsung Galaxy A Series
Contributors
dariotr
Credits
@danwood76
@Stricted
@alexax66
Source Code:
https://gitlab.com/dariotrombello
https://gitlab.com/Exynos7580
https://github.com/DotOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: dotOS
Version Information
Status: Stable
Stable Release Date: 2019-03-22
Created 2019-03-22
Last Updated 2019-07-11
Discord
I've created a new Exynos 7580 Discord because the old one from the Lineage 15.1 project got deleted. I regularly share testing builds here. Join if you want . If you have any questions or problems with the ROM, write them also there.
https://discord.gg/TEfC5hA
Building
You can find a guide for building dotOS for the Galaxy A3 2016 here: https://github.com/dariotrombello/local_manifests
Wow! Very great!
fix hwc
to enable hwc use this commit
https://github.com/SamsungGalaxyJ5-...mmit/8017ccdab7aa8d31c5de755a98717877551046e1
Jullian_Ms said:
to enable hwc use this commit
https://github.com/SamsungGalaxyJ5-...mmit/8017ccdab7aa8d31c5de755a98717877551046e1
Click to expand...
Click to collapse
Are you sure that this is working? I think it has to do with something else
The ROM is now out official with working OTA Updater. Changelog from the last unofficial build:
- Widevine L1 is working now for a better quality when streaming movies etc. via Amazon Prime or Netflix (thanks to danwood76)
- A few more SELinux fixes
Borduni said:
The ROM is now out official with working OTA Updater. Changelog from the last unofficial build:
- Widevine L1 is working now for a better quality when streaming movies etc. via Amazon Prime or Netflix (thanks to danwood76)
- A few more SELinux fixes
Click to expand...
Click to collapse
Although we now have Windevine L1 our phone is not supported on Netflix or Amazon Prime (it is not on stock either).
There are some hacked versions of Netflix floating about but I don't think you really need HD on our tiny screen .
danwood76 said:
Although we now have Windevine L1 our phone is not supported on Netflix or Amazon Prime (it is not on stock either).
There are some hacked versions of Netflix floating about but I don't think you really need HD on our tiny screen .
Click to expand...
Click to collapse
Widevine L1 is even supporting 4K, isn't it?
Borduni said:
Widevine L1 is even supporting 4K, isn't it?
Click to expand...
Click to collapse
L1 just enables a more protected version of DRM, it is carried out in a secure area of the CPU (mobicore). So yes it supports higher resolutions but neither Netflix nor Amazon support non certified phones, you may be able to get round it by changing the build fingerprint. I've not tested it because I have no need for HD video on a 4.7" screen .
Bug, or Problem?
Man, help me. I installed the Dot OS 3.0 (Pie) version, until I was able to use it for about 5 - 8 hours, but suddenly he started to stop the interface making me unable to use the phone, first I formatted it thinking it was just a bug , but it remained, I went back to version 2.5 of DotOS (Oreo) but still still giving the same problem ...: /
Kyukazai said:
Man, help me. I installed the Dot OS 3.0 (Pie) version, until I was able to use it for about 5 - 8 hours, but suddenly he started to stop the interface making me unable to use the phone, first I formatted it thinking it was just a bug , but it remained, I went back to version 2.5 of DotOS (Oreo) but still still giving the same problem ...: /
Click to expand...
Click to collapse
What exactly is the issue?
Did you wipe /data /system and erase the cache before installing?
Can you provide a logcat of the error?
danwood76 said:
What exactly is the issue?
Did you wipe /data /system and erase the cache before installing?
Can you provide a logcat of the error?
Click to expand...
Click to collapse
The issue is the same, the UI interface always stops running and the phone stuck for 45 seconds, after I stop the UI and restart it, the phone stay normal, after aproximately 1 - 2 minutes the problem return and permance in a loop
Yes, I did have a full wipe, data, system, cache, internal storage, etc...
Where I can get the logcat?
Kyukazai said:
The issue is the same, the UI interface always stops running and the phone stuck for 45 seconds, after I stop the UI and restart it, the phone stay normal, after aproximately 1 - 2 minutes the problem return and permance in a loop
Yes, I did have a full wipe, data, system, cache, internal storage, etc...
Where I can get the logcat?
Click to expand...
Click to collapse
You can produce a logcat using this guide: https://forum.xda-developers.com/showthread.php?t=1726238
Did you install gapps?
If so try a full clean flash but without installing gapps.
danwood76 said:
You can produce a logcat using this guide: https://forum.xda-developers.com/showthread.php?t=1726238
Did you install gapps?
If so try a full clean flash but without installing gapps.
Click to expand...
Click to collapse
Ok man, I'll try a full clean flash without Gapps and I will relate for you the situation, thanks for the response
Kyukazai said:
Ok man, I'll try a full clean flash without Gapps and I will relate for you the situation, thanks for the response
Click to expand...
Click to collapse
Yeah, I tried this and works! The phone back to work perfectly. So much thanks :victory:
But, it's possible to install the xposed with this ROM?
Kyukazai said:
Yeah, I tried this and works! The phone back to work perfectly. So much thanks :victory:
But, it's possible to install the xposed with this ROM?
Click to expand...
Click to collapse
You should be able to install the latest opengapps with DotOS without issue.
I don't think there is official Xposed for Pie, and I have heard that the unofficial is very unstable.
Why do you need xposed?
danwood76 said:
You should be able to install the latest opengapps with DotOS without issue.
I don't think there is official Xposed for Pie, and I have heard that the unofficial is very unstable.
Why do you need xposed?
Click to expand...
Click to collapse
Yeah, I see the unofficial, I will stay in Oreo, but thanks for the answer
I need the xposed for the modules: LTweaks, Gravity Box, Xposed Edge.
XD
Found a little bug
When you drop down the notification panel whilst in landscape and try to close it by tapping in the blank space below the "no notifications" text or around it, the menu bugs out, showing the tiles for a split second and then closing all together.
keep going..
Hello. I have been following dot OS for a long time. I've noticed that during both the trial of both stable and android pie .. The location is wifi hidden. I enter the user name and password manually, but does not recognize it. Although it appears to be a registered wifi network, the connection happens. everything is ok when wifi is removed from the modem interface. We wish to have a small share ..
Router bug
I noticed a bug when I try to connect the router along with the mobile data, it just does not turn on.
Good Job man, and thanks so much for this great ROM . You're the best.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.
Get ready to taste the unique features it brings with itself.
We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.
@Subinsmani
@rahul9999
@@ki
@Shreejoy Dash
@kvijaya
@AxelBlaz3
@Psycho-Mods
@amarbajpai
@gero
@melvingarcia
]
Support Us if you like our work
[SIZE=+1]Got an issue or suggestion? Reach us at[/SIZE]
Telegram: https://telegram.me/pixysos_chat
Coming soon
Pixys: PixysOS
Pixys Device Sources: PixysOSDevices
- Backup your personal data (Important)
- Download the ROM and GApps and transfer them to your device.
- Boot to recovery (TWRP recommended).
- Wipe the System, Cache, Data and ART/Dalvik cache.
- Flash the ROM + Gapps Zipfile.
- Flash the root solution of your choice (optional).
- Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
ROMs: DONWLOAD
You tell...
- Google for AOSP
- AOSCP
- Dirty Unicorns
- Pixel experience
- AOSP extended
- LineageOS
- Nitrogen Os
- Bootleggers Rom
- Superior OS
- AICP & POSP Team for thread template idea
- Also many pro devs who all help us to bring this rom to you..
- Please let us know if we forgot to mention your name in credits..
XDA:DevDB Information
PixysOS, ROM for the Moto G (5S) Plus
Contributors: @Pintoslp
Kernel source:
https://github.com/lit-kernel/android_kernel_motorola_msm8953
ROM OS Version: 10.x.x Ten
ROM Kernel: Linux 3.x.x
Based On: AOSP
Version Information
Status: Stable
Current Version: v3.03
Release Date: 02-13-2020
Coool
Update
PixysOS Update
New build available for Motorola G (5S) Plus (sanders)
by @pintos
Version: 3.1.0 (ten)
Build date: (2020/06/23)
Edition: NON-GAPPS
Download Now
#sanders #pixysos
After installing this OS my phone only charges to 70%. How do I fix this?
unl0ck said:
After installing this OS my phone only charges to 70%. How do I fix this?
Click to expand...
Click to collapse
I never faced this issue before. Can you try install again? Clean flash required.
Hugs!
Pintoslp said:
I never faced this issue before. Can you try install again? Clean flash required.
Hugs!
Click to expand...
Click to collapse
I have reinstalled it before and it didn't help. I guess I should mention that I installed the Mayhem Unravel 4 OC Treble kernel (https://forum.xda-developers.com/moto-g5s-plus/development/kernel-mayhem-kernel-t3942444). Could that be the problem or is there a fix from an xposed or magisk module? I need a kernel that can boost my phones performance and battery, and I would really appreciate some recommendations.
I also use Magisk 20.3 with Magisk Manager 7.5.1 and Riru EdXposed (Sandhook) 0.4.6.0.
unl0ck said:
I have reinstalled it before and it didn't help. I guess I should mention that I installed the Mayhem Unravel 4 OC Treble kernel (https://forum.xda-developers.com/moto-g5s-plus/development/kernel-mayhem-kernel-t3942444). Could that be the problem or is there a fix from an xposed or magisk module? I need a kernel that can boost my phones performance and battery, and I would really appreciate some recommendations.
I also use Magisk 20.3 with Magisk Manager 7.5.1 and Riru EdXposed (Sandhook) 0.4.6.0.
Click to expand...
Click to collapse
Mayhem kernel 4.0 is for Pie Roms !
All your problems must come from that.
Wipe everything and install the ROM again (Gapps already included !) .
Then you should be fine !
This ROM doesn't have many features, but is the only one with FM Radio and DTV working for this device so far.
I think we don't have any custom kernel for Android 10 yet.
Hope this could help you.
Good luck !
Damage1972 said:
Mayhem kernel 4.0 is for Pie Roms !
All your problems must come from that.
Wipe everything and install the ROM again (Gapps already included !) .
Then you should be fine !
This ROM doesn't have many features, but is the only one with FM Radio and DTV working for this device so far.
I think we don't have any custom kernel for Android 10 yet.
Hope this could help you.
Good luck !
Click to expand...
Click to collapse
I didn't even notice that. I will remove it and I hope this was the problem and that it will fix the alarm app. I have been late to school for a couple of days because of this.
unl0ck said:
I didn't even notice that. I will remove it and I hope this was the problem and that it will fix the alarm app. I have been late to school for a couple of days because of this.
Click to expand...
Click to collapse
I thimk it'll be ok, man.
I'm using Pixys OS as my daily driver, since it has DTV working.
Good luck !
Damage1972 said:
I thimk it'll be ok, man.
I'm using Pixys OS as my daily driver, since it has DTV working.
Good luck !
Click to expand...
Click to collapse
A quick update: I removed the kernel and killed the battery (used it until it shut down) to calibrate it, but when I turned it back on my battery was still limited to 70%. The alarm app is fixed though, so that's a relief.
I have already tried the following which people said is solutions:
Calibrating battery (draining it & charging while it's powered off).
Reinstalling PixysOS.
Removing the kernel (Mayhem Unravel 4).
Performing a factory reset.
Uninstalling all magisk modules (one by one (including Xposed)).
Uninstalling all Xposed modules (one by one).
Uninstalling magisk root completely.
Installing the "Battery Charge Limit" application & limiting it to 99%.
Wiping cache partitions (wiped cache & dalvik in recovery mode).
None of these worked and I have tried all of the at least 2 percent (except for the "uninstalling the kernel" since I didn't notice that it is for Pie). Is there a flashable zip or a magisk/xposed module (or application) that could be a potential fix, or can I fix it by modifying some system files?
Also, speaking of modifying system files, I went through the system files and navigated to "/sys/class/power_supply/battery" which redirected me to "/sys/devices/soc/qpnp-smbcharger-17/power_supply/battery". I went through and viewed the content of some files, and some of them could be a solution to my problem.
(I am just using logic here, and I don't know anything about this stuff. I was hoping you could help me, since you seem to know what you're talking about.)
I went into the following files:
capacity (file name)
58 (inside of the file)
(the value of the file changes every time my battery percentage changes)
charge_counter
1928327
charge_full
3013000
(this is what I meant with logic. The file is named "charge_full" as in the maximum charge the phone can have. Maybe if I change the numbers to something else it could reach 100%.)
charge_full_design
3013000
charge_rate
None/Normal/Fast
(depending if I am charging or not and if I am using the turbo charger which came with the phone)
constant_charge_current_max
2000000
current_now
452420
Then there's a lot of other files in the folder, for example:
flash_active
flash_current_max
input_current_max
input_current_settled
voltage_max
voltage_max_design
voltage_now
and then there's a file named "uevent" which contains the following:
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CAPACITY=54
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_CURRENT_NOW=374448
POWER_SUPPLY_CHARGE_COUNTER=1859488
POWER_SUPPLY_TEMP=357
POWER_SUPPLY_VOLTAGE_NOW=3800331
POWER_SUPPLY_CHARGE_RATE=None
There's one last thing which I think is strange.
The files "battery_charging_enabled" and "charge_enabled", and that doesn't sound strange, but when I looked inside of them while charging my phone I found that the "battery_charging_enabled" was set to '1' while "charge_enabled" was set to '0'. When I tried to change the 0 to a 1 (after backup of course) it saved, but when I plugged out my charger the "battery_charging_enabled" became a '0' but the "charge_enabled" was unchanged as if that file isn't needed.
I hope that's all information you (or anybody reading this and is willing to help me) need to be able to find a fix. Thank you for reading this extremely long comment/post. I will not waste any more of your time, but I really appreciate that you've spent your time helping me.
Thank you so much.
unl0ck said:
A quick update: I removed the kernel and killed the battery (used it until it shut down) to calibrate it, but when I turned it back on my battery was still limited to 70%. The alarm app is fixed though, so that's a relief.
I have already tried the following which people said is solutions:
Calibrating battery (draining it & charging while it's powered off).
Reinstalling PixysOS.
Removing the kernel (Mayhem Unravel 4).
Performing a factory reset.
Uninstalling all magisk modules (one by one (including Xposed)).
Uninstalling all Xposed modules (one by one).
Uninstalling magisk root completely.
Installing the "Battery Charge Limit" application & limiting it to 99%.
Wiping cache partitions (wiped cache & dalvik in recovery mode).
None of these worked and I have tried all of the at least 2 percent (except for the "uninstalling the kernel" since I didn't notice that it is for Pie). Is there a flashable zip or a magisk/xposed module (or application) that could be a potential fix, or can I fix it by modifying some system files?
Also, speaking of modifying system files, I went through the system files and navigated to "/sys/class/power_supply/battery" which redirected me to "/sys/devices/soc/qpnp-smbcharger-17/power_supply/battery". I went through and viewed the content of some files, and some of them could be a solution to my problem.
(I am just using logic here, and I don't know anything about this stuff. I was hoping you could help me, since you seem to know what you're talking about.)
I went into the following files:
capacity (file name)
58 (inside of the file)
(the value of the file changes every time my battery percentage changes)
charge_counter
1928327
charge_full
3013000
(this is what I meant with logic. The file is named "charge_full" as in the maximum charge the phone can have. Maybe if I change the numbers to something else it could reach 100%.)
charge_full_design
3013000
charge_rate
None/Normal/Fast
(depending if I am charging or not and if I am using the turbo charger which came with the phone)
constant_charge_current_max
2000000
current_now
452420
Then there's a lot of other files in the folder, for example:
flash_active
flash_current_max
input_current_max
input_current_settled
voltage_max
voltage_max_design
voltage_now
and then there's a file named "uevent" which contains the following:
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CAPACITY=54
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_CURRENT_NOW=374448
POWER_SUPPLY_CHARGE_COUNTER=1859488
POWER_SUPPLY_TEMP=357
POWER_SUPPLY_VOLTAGE_NOW=3800331
POWER_SUPPLY_CHARGE_RATE=None
There's one last thing which I think is strange.
The files "battery_charging_enabled" and "charge_enabled", and that doesn't sound strange, but when I looked inside of them while charging my phone I found that the "battery_charging_enabled" was set to '1' while "charge_enabled" was set to '0'. When I tried to change the 0 to a 1 (after backup of course) it saved, but when I plugged out my charger the "battery_charging_enabled" became a '0' but the "charge_enabled" was unchanged as if that file isn't needed.
I hope that's all information you (or anybody reading this and is willing to help me) need to be able to find a fix. Thank you for reading this extremely long comment/post. I will not waste any more of your time, but I really appreciate that you've spent your time helping me.
Thank you so much.
Click to expand...
Click to collapse
I have the solution: don't change the kernel.
Pintoslp said:
I have the solution: don't change the kernel.
Click to expand...
Click to collapse
Well I removed the kernel, but I found out that wasn't the issue. The issue was the Advanced Charging Controller (acc). I removed it, but my phone still wont charge above 70%.
unl0ck said:
Well I removed the kernel, but I found out that wasn't the issue. The issue was the Advanced Charging Controller (acc). I removed it, but my phone still wont charge above 70%.
Click to expand...
Click to collapse
Very strange
Pintoslp said:
Very strange
Click to expand...
Click to collapse
Do you have the original files in the '/sys/class/power_supply/battery' folder? Maybe I could restore them somehow. I will also try to reinstall the OS.
Hi there, I am using the latest build and for some reason the fingerprint sensor doesn't work. If I try to setup a new fingerprint, it read my fingerprint, but I can't use it to unlock my device.
Anyone having this issue?
ainstushar said:
Hi there, I am using the latest build and for some reason the fingerprint sensor doesn't work. If I try to setup a new fingerprint, it read my fingerprint, but I can't use it to unlock my device.
Anyone having this issue?
Click to expand...
Click to collapse
We will fix this issue on next update, that will released in a few days
Thanks!
Pintoslp said:
We will fix this issue on next update, that will released in a few days
Click to expand...
Click to collapse
Thank you so much!
Pintoslp said:
We will fix this issue on next update, that will released in a few days
Click to expand...
Click to collapse
Hi there,
Latest build (3/8/20) has not fixed this issue. And now I am running into "device personalization services keeps crashing" error.
Any advise?
Thanks!
ainstushar said:
Hi there,
Latest build (3/8/20) has not fixed this issue. And now I am running into "device personalization services keeps crashing" error.
Any advise?
Thanks!
Click to expand...
Click to collapse
Flash kernel permissive patcher for now. Device personalization is a matter with source, we need to wait.
first congratulations on your work, your rom is great and apparently without bugs, I managed to root it, but after rooting the twrp I use version 3.2.1r20 does not flash zip files showing the error "updater process ended with error 1" you know how to solve this? ah, i already tried the solution here on xda which is extracting the "boot" image from your rom and flash boot via twrp but it didn't solve it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
go to recovery
copy Rom,gapps and magisk to your internal memory or sd-card
wipe system,data and dalvik cache
flash Rom,gapps and magisk
reboot to system
Update installation:
go to recovery
copy Rom,gapps and magisk to your internal memory or sd-card
wipe system and dalvik cache
flash Rom,gapps and magisk
reboot to system
many thanks to @KShion619 for sending me a new board to continue making rom's for this great device
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM d850
ROM d851
ROM d852
ROM d855
ROM f400
ROM g3ds
ROM ls990
ROM vs985
Changelog: changelog_d850
Changelog: changelog_d851
Changelog: changelog_d852
Changelog: changelog_d855
Changelog: changelog_f400
Changelog: changelog_g3ds
Changelog: changelog_ls990
Changelog: changelog_vs985
Known issues:
this is based on Los sources with good old XTD kernel so expect the same issues.
we are working to try to solve all , sometimes we succeed, sometimes we don't
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
XDA:DevDB Information
crDroidAndroid, ROM for the LG G3
Contributors
firebird11, HardStyl3r
Source Code: https://github.com/crdroidandroid
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
Based On: LOS
Version Information
Status: Testing
Created 2020-03-20
Last Updated 2020-03-20
res
In my device
XTD can set
Boot loop in LG logo
great stuff!
fOxunO said:
In my device
XTD can set
Boot loop in LG logo
Click to expand...
Click to collapse
Which device and logs please
Sent from my ONEPLUS A6003 using Tapatalk
firebird11 said:
Which device and logs please
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Sorry , just back to AOSP Alpha
But seem like when trying LOS 20200315
Yours can get TWRP from VolDown+power , LOS can not
D855
Weird , flashing over LoS 20200320 not boot loop .
-
-
-
-
Seem more hot
TWRP also only vol + power
add
Maybe the problem is from kernel , without changing kernel adiutor , working better
works well d855...(stock kernel)
one bug..
screen flickers when opening a program,in the upper regions..
thank you...
Thanks a lot for this ROM @firebird11
Working exceptionally well for an initial build on my vs985.
- As for occasional flickering of the upper right hand side of screen, it's the homescreen intermittently showing beneath the current foreground activity.
- Transitions: sometimes, the back gesture arrow freezes along with its transition. Drawing down the notification shade sometimes freezes. Returning back to a previous app sometimes freezes the new one for a couple of seconds.The default music app sometimes stutters when drawing down the notification shade.
- Occasionally, Music (com.crdroid.music) shows the wrong album art for the playing song.
All in all, the issues I've observed are just minor bothers (almost all issues are SystemUI freezes). As is, this ROM can EASILY be a daily driver.
Thanks again for not throwing in the towel (I thought you did since crDroid 5.X) .
Sent from my LG-VS985 using XDA Labs
This loaded fine and felt smooth and quick on d850! I used it for 2 days so not too much time. battery drained quicker than normal tho. maybe it smooths out later on..
Anyway, I used the 3/20 Open Gapps Pico and Magisk 20.3 ...
My only only only major complaint is that the whole phone freezes and eventually reboots when plugged into my cars USB and Android Auto is selected from my car interface. probably an open gapps thing. maybe BitGapps does not have this issue. i will try that another time.
Also, minor, but old messages seem to keep showing up as new in the default messages app after a reboot.. this is after a message restore using sms backup & restore. no logs sorry i had to quickly revert back.
@firebird11
One Random reboot on vs985 when screen goes off. Last_kmsg log attached.
Sent from my LG-VS985 using XDA Labs
Tnx for 20200327
updated from v5.7 on d850 went mostly bad it seems
big issues:
it isn't recognizing my f2fs formatted SD card, which it was before.
seems the notification drawer gets a little twitchy if there's too many notifications. didn't notice that before upgrade either
android.process.media keeps stopping? dunno what's going on there, disabled force close dialogs in crDroid settings for the time being
GPS still not working
VoLTE doesn't seem to work either still, unless i'm missing something. real big deal for me, UMTS/HSPA in my area is very hit and miss and i can't reliably fall back to it
wifi wasn't working until i cleared out the WifiConfigStore.xml in /data/misc/wifi
might just try doing a clean install and see how that goes, but upgrade seems like a no go
Tried newest build on my D850 a few days ago with 4/3 OpenGapps Pico and Magisk 20.3 and I actually do not have any issues to report. Definitely try a clean install if you are having issues. I had notification drawer and quick settings twitchiness but it went away either after a few reboots or after setting up Nova launcher. My GPS has no issues either. Battery is somehow great on this build too - weird. I even got Android Auto working which means I will use this as a daily driver. Finally a good reason now to get off of Fulmics! As for Android Auto, I am not 100% sure this is the fix yet but it seems that I need to clear the Android Auto cache and also disable battery optimization for it to not crash the entire phone upon connecting to my car... Thanks!
clean install worked better
did a clean install. worked out a LOT better, although the notification drawer is still twitchy and no f2fs. didn't try calls oops. other than the notification bar weirdness, it's butter smooth
did have a weird issue while setting up where it didn't want to continue with account setup and wanted me to pick a wifi network, but after picking a wifi network it did nothing. ended up skipping the initial wizard and doing it again when i could kick wifi on with the QS tile while pressing use mobile network (which turns wifi off), which let the wizard work on wifi. kinda weird!
got a nandroid of it to roll back up to, but i went back to 5.7 for the time being. once f2fs support is fixed i'll probably go back and update it, but in the meantime i need my music!
Update: Android Auto still crashes. I was wrong. Attached is logcat.. look for date 4/9 around time 0750-0752 mark.. it shows me plugging in phone to car usb then crash occurring. Phone reboots and attempts to connect to car again and crashes again..
Thanks!!
Really nice build. I like how most of the bugs in Lineage OS has been fixed. But there is something wrong with mobile connection. When set to LTE, it becomes unavailable then after some time it's again available and then again unavailable. Changing to 3G or 2G makes connection available all the time.
YukiCRO said:
Really nice build. I like how most of the bugs in Lineage OS has been fixed. But there is something wrong with mobile connection. When set to LTE, it becomes unavailable then after some time it's again available and then again unavailable. Changing to 3G or 2G makes connection available all the time.
Click to expand...
Click to collapse
restart or set APN to internet
Animation issues
First off, I would like to thank the developer for the hard work he has done to keep this device alive even to this day. I personally enjoyed crDroid pie on my LG G3. I thought I should try this android 10 version. It went off to a good start but The android 10 has some animation issues. There's a lot of tearing in the animation transitions. I had to set the animations all to 0.0 to stop most of the tearing. You might want to consider looking into it.
Thanks
new builds up!
i didn't have time to look into any issues yet, maybe some are better now , test and let me know
Warning: bugs and outdated SP ahead...
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Stellar OS is an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
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.
Click to expand...
Click to collapse
We offer vanilla and gapps variants. If you install a vanilla variant, the only supported Gapps package is MindTheGapps (gapps builds are not available for a few devices due to space issues).
Download & instructions:
Build 23th September 2021
• 1.1 source update (September SP + new features)
• Fixed fast charging display
Vanilla | Gapps
Old releases:
Spoiler
Build 12th August 2021
Initial release
If you are coming from an older build (beta testers), clean flash is required
Vanilla | Gapps
IMPORTANT: If you are coming from another ROM, you need to format data (there where you type yes in twrp).
IMPORTANT: OTA updates require enabling recovery update in Setup Wizard (or, if you already set your device up developer options) - they do not support TWRP.
About:
Features:
All Mint 2.1 features
September security patch
SafetyNet passing WITHOUT Magisk Hide
Many optimizations
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Stellar Tweaks customization section
Navbar Tuner
Improved Trebuchet+
OmniJaws weather service
Many lockscreen clocks
Statusbar ticker
Signed official builds
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more (we accept suggestions)
The focus for the inital release was an neccessary set of tweaks and optimizing android.
What's working:
WiFi
Camera and Camcorder
Bluetooth
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE
USB tethering/audio
SELinux: Enforcing
Bugs:
You tell me
Sources are available at https://github.com/Stellar-OS and https://github.com/Stellar-Devices
Screenshots from ocean are attached
ROM OS Version: 1.0
ROM Kernel: Linux 3.18.140
ROM Firmware Required: Must be on latest Oreo Stock firmware
Based On: LineageOS 18.1
Version Information
Status: Stable
Current Stable Version: 1.0
SELinux Status: Enforced
Release Date: 15th August 2021
Thanks for letting us know- I'll have to try this! Will Mint 2.1 Seed vault backups be compatible with this new ROM?
doug888 said:
Thanks for letting us know- I'll have to try this! Will Mint 2.1 Seed vault backups be compatible with this new ROM?
Click to expand...
Click to collapse
I'm not sure, as this is a android version jump, but it's worth to try.
In instaled it, its working perfectly. No issues at all until now. Thank you so much for keeping my moto g5 alive
I have one minor issue. It seems TWRP has been replaced by lineageOS recovery. I would like to keep it that way in orer to receive updates. I would like to flash and install magisk though in order to hide root so I can work with MS Oulook and such. I do not see the option in lineageOS recovery. Can I boot into TWRP recovery from adb/fastboot, and then fash it? or are there other options?
listm said:
In instaled it, its working perfectly. No issues at all until now. Thank you so much for keeping my moto g5 alive
I have one minor issue. It seems TWRP has been replaced by lineageOS recovery. I would like to keep it that way in orer to receive updates. I would like to flash and install magisk though in order to hide root so I can work with MS Oulook and such. I do not see the option in lineageOS recovery. Can I boot into TWRP recovery from adb/fastboot, and then fash it? or are there other options?
Click to expand...
Click to collapse
It got replaced because you enabled the checkbox in setup wizard. Disable it in developer settings and install TWRP as normally.
nift4 said:
It got replaced because you enabled the checkbox in setup wizard. Disable it in developer settings and install TWRP as normally.
Click to expand...
Click to collapse
I missed that one. Thanks for the quick reply.
Issue solved. Sadly the microsoft company portal is aware of my device being rooted, this was also the case in android 10, but Ill work around it.
listm said:
I missed that one. Thanks for the quick reply.
Issue solved. Sadly the microsoft company portal is aware of my device being rooted, this was also the case in android 10, but Ill work around it.
Click to expand...
Click to collapse
Have you hidden magisk with a random package name in its settings?
Does your device pass ctsprofile?
If not install magisk hide props module and terminal emulator. Once installed type props in terminal emulator and change the fingerprint to a pixel 4 android 11
Also hide the app that detects root with magisk hide
TheFixItMan said:
Have you hidden magisk with a random package name in its settings?
Does your device pass ctsprofile?
If not install magisk hide props module and terminal emulator. Once installed type props in terminal emulator and change the fingerprint to a pixel 4 android 11
Also hide the app that detects root with magisk hide
Click to expand...
Click to collapse
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
listm said:
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
Click to expand...
Click to collapse
Unfortunately I don't use it else I would test it out and try get it to work
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
AndyFx12 said:
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
Click to expand...
Click to collapse
This is due to a slow driver, an issue that is known and present in all Android 11 builds for Moto G5, even official Lineage OS.
Idk if kernel 4.9 will get usuable any time soon, but that will hopefully resolve that issue.
listm said:
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
Click to expand...
Click to collapse
Hide props is not needed on this rom, for general information. I built it into the source.
AndyFx12 said:
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
Click to expand...
Click to collapse
Formatting system and data is an good idea actually. It prevents leftovers (on system, some things like Gapps packages store restore scripts). Formatting vendor is useless. No harm done, just time wasted.
Thanks for your replies and explanation!
It's amazing to see Android 11 on such an "old" device!
regards, Andy
@nift4 Are you still working on kernel 4.9?
xenondroid said:
@nift4 Are you still working on kernel 4.9?
Click to expand...
Click to collapse
Yes. Jarl & wiktorek140 made it work near to perfect on montana and I am trying my best to replicate that on cedric. Jarl said he will only bringup 4.9 ports to LineageOS 19...
Flashed this to replace Mint 2.1 no problems. Even the Seedvault backup worked. Battery seems to last longer too. One strange thing I'm experiencing since I flashed Stellar is that whenever I reboot my phone I get 5 text messages within a couple of minutes from O2 (my mobile network operator) saying my number doesn't support Visual Voicemail. I've never used Visual Voicemail it in the past, wonder why I'm getting these messages?
Thanks
doug888 said:
I've never used Visual Voicemail it in the past, wonder why I'm getting these messages?
Click to expand...
Click to collapse
Probably because it's enabled by default in Android 11. You can disable it in Dialer settings, I think.
Thanks! That worked
Hi,
Thank you for your work !
My questions may be slightly off-topic... and from a newbie but I am wondering why SafetyNet is OK on this ROM (checked with an application, without Magisk installed) BUT some applications still refuse to work or complain :
- WhatsApp just warns my device is not supported
- HID Approve (an MFA auth. app) refuses to run
- My banking app refuses to enable basic features at launch
What kind of checks have been implemented within these applications (are they well-known ?) and is there a way to workaround these issues ?
Otherwise, I could relock my bootloader and reinstall Oreo Stock but I tried many times a few months ago and never managed to do it without losing my IMEIs (I have not done EFS backups before installing MintOS...). Any suggestion to make this work without buying another phone ?
Thank you !