View the sourcecode on google Code!
Don't let the app die, develop for it/include its features in another app.
Latest version (4.1.9) can be found on page #37
Hi,
I have written an app, which contains useful functions specially for the Galaxy S imho.
It can do the following things:
-Secret codes list (contains at the moment 31 codes)
(Don't worry clicking around, there will appear a popup if you have selected factory/hard reset )
-System clean up: this means you can delete all system apps you don't like with 1 click. It will remove the .apk, the .odex and the data directory.
It won't let you delete apps that will "brick" your phone, so very useful for android beginners.
-MarketFix: This sets the Fingerprint in the build.prop to JF3 (2.1) and cleares the market cache. After a day you should see 120 hits when searching for "documents".
Useful if you are using a test Firmware and don't see copy protected apps in market.
-Homescreen Settings: In this Menu you can set the default screen (press the home button when you are already on the home screen) and the screen count.
Only works with some Firmwares! Works for example with JM5, JM7.
-Move SGS Tools to System: This will save the app on the device if you do a factory/hard reset. You can also undo this.
-Run a script.
This menu can run scripts, which are written as .txt files.
Simply write every command in a new line and put the script.txt to /sdcard/sgstools.
It checks the inputstream of the process, for example if you want to notify the user about progress with "echo /sdcard/test removed", this will appear in the progressdialog. It also checks the errorstream and will display, if for example a command could not be found.
- Enable/Disable boot/shutdown sound or place custom sounds
-Last but not least, you can add shortcuts to homescreen, which let you run commands. Useful for example as shutdown, reboot recovery, reboot, etc.
There's a bug in 2.2 Firmwares, which won't let you pick custom icons for shortcuts! (I tested it on 2.2 Emulator and also anycut won't set an icon on 2.2 Firmwares..)
That's it. Hope you like it.
(Sorry, it's not on the market - I don't have a market account yet )
PS: Press Menu Button to access further menus.
PPS: It uses a custom menu
PPPS: Rotate the device, and you will see in some menus a rotation animation!
PPPPS: German users can also look in this http://www.android-hilfe.de/samsung-galaxy-s/33978-sgs-tools-app-zum-schnellen-bearbeiten.html.
Ver 3.0: - now translated into english
Ver 3.0.1 - Bugfix: added permission to install shortcuts
Ver 3.1
- Activity handling improved
-new tool for setting boot sound / shutdown sound
Ver 3.1.1:
-MarketFix improved: now show better warnings, for example if busybox is not installed.
-Now a .nomedia file is created in the sgstools folder.
Ver 3.2
-Bugfixes
Ver 3.2.1
-Bugfixes: -Warning when removing system apps now in english
-Standard icons fixed for creating shortcut. (sry, but the broken icons will be only fixed if you deinstall the old version before)
Ver 3.3
-When removing system apps, the .apk and the .odex will be backuped in /sdcard/sgstools
Ver 3.4:
changes
edit: I forgot, please deinstall the old version, so you can read the disclaimer
Ver 3.5.1:
.prop editor bugfix
added 2 small scripts: mount /system ro/rw
command shortcuts now with basic commands (shutdown, reboot, mount..)
Ver 3.6
- script modul update, can now execute .txt scripts wrapped in a .zip
Ver 3.6.1
- script modul can now handle .zips with several scripts in it
Problems with busybox should be fixed now!
Ver 3.8.3
-some useful scripts
-backup & restore your homescreen
Newest version is 4.1.0
-added some tw launcher mods
-modded contacts.apk
-modded browser
-hacked camera.apk
-reverse scripts
If you want to donate something for this free app (Paypal) you can use the following link:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XEMXTUYAZVUGY
I guess it requires root access? Haven't tried yet but the description looks great.
Very nice app.. Good Work..
ssj4Gogeta1 said:
I guess it requires root access? Haven't tried yet but the description looks great.
Click to expand...
Click to collapse
Yeah requieres root, but not for the secret codes.
Nice one!
You could also add a option to change system sounds, bootscreens etc. (very SGS specific)
Fr4gg0r said:
Yeah requieres root, but not for the secret codes.
Click to expand...
Click to collapse
Very nice app I have just one remark about secret codes, it seems that the secret codes executes directly which is very handy but in a case of "HARD RESET", Factory data reset" I think the user should been warned about danger this commands can do before one pinch those links
Can you implement that in your app ?
Wow! Looks amazing. Is the rotation animation just in that application or across the whole device?
lajson said:
Very nice app I have just one remark about secret codes, it seems that the secret codes executes directly which is very handy but in a case of "HARD RESET", Factory data reset" I think the user should been warned about danger this commands can do before one pinch those links
Can you implement that in your app ?
Click to expand...
Click to collapse
When users execute the Factory data reset code they come in a window in which they explicitely have to agree by clicking a button (same window btw when you trigger factory data reset from the settings->security menu... which also don't present a warning btw)
Hard reset is tricky on the other hand. You never wanna trigger that one
lajson said:
Very nice app I have just one remark about secret codes, it seems that the secret codes executes directly which is very handy but in a case of "HARD RESET", Factory data reset" I think the user should been warned about danger this commands can do before one pinch those links
Can you implement that in your app ?
Click to expand...
Click to collapse
Already implemented, look at attached picture. Or did u meant a second warning?
@Hard Reset:
I needed that 2 days ago, in order to use the lagfix. I had not enough space on data and only a hard reset (or manually removing much files) could solve that.
LevitateJay said:
Wow! Looks amazing. Is the rotation animation just in that application or across the whole device?
Click to expand...
Click to collapse
Rotation is only in that application, sry. For whole device you would have to modify the Framework, which isn't possible because it's not open source.
You would have to build a rom from aosp to implement that.
appelflap said:
Nice one!
You could also add a option to change system sounds, bootscreens etc. (very SGS specific)
Click to expand...
Click to collapse
Bootscreens is a very nice idea.
I will look if I can implement that feature.
Fr4gg0r said:
Already implemented, look at attached picture. Or did u meant a second warning?
@Hard Reset:
I needed that 2 days ago, in order to use the lagfix. I had not enough space on data and only a hard reset (or manually removing much files) could solve that.
Click to expand...
Click to collapse
OK, I was just testing some secret codes in your app and saw that they were executed directly and then I hadn't guts to pinch the hard reset and factory reset links and hence was my question to you.
But now I know better and can bee shore that they can't do some major damage if I stupidly do a mistake and pinch those links
BTW a very nice touch the sliding menu
As a suggestion you could maybe implement APN backup as well
5 stars Fr4gg0r, so useful. Many thanks!
Custom Bootanimation seems not to be possible at the moment..
But I will add enable/disable Bootsound later this day.
Fr4gg0r said:
Rotation is only in that application, sry. For whole device you would have to modify the Framework, which isn't possible because it's not open source.
You would have to build a rom from aosp to implement that.
Click to expand...
Click to collapse
So because Samsung's version of Android is closed source we can't implement it but say in Cyanogen Mod it would be possible? This is one of the major features I want to see in Android, adds a nice visual touch.
I think it should be possible in a Cynogen Mod.
But it's not said, that the system is powerful enough to handle that with heavy views..
okay, for the noobs here (meaning me), can someone do a quick "how to" install instuction
tks - and i am rooted
'Homescreen Settings' doesn't work for me
I set 'default: 2' and 'amount of screens: 5'. After press apply and reboot, no results. If I press home key, always show me the first one (0)
rafalense said:
'Homescreen Settings' doesn't work for me
I set 'default: 2' and 'amount of screens: 5'. After press apply and reboot, no results. If I press home key, always show me the first one (0)
Click to expand...
Click to collapse
I have already heard this by other people.. the problem is, for me it always worked.
Are you really using JM5 or JM7?
To exclude misunderstanding:
If you press the home button from anywhere, you will always taken to first screen. This cannot be changed.
But if you already are on homescreen and then press the home button, it should take you to the screen you have set in my app.
@larryccf
Simply copy the apk to sdcard.
Then launch the stock myfiles app, or whatever file explorer, and click on the .apk.
The file explorer should initiate the installing then.
Update to Version 3.1:
-now you can de or activate the boot / shutdown sound and also replace them with custom sounds.
-I rewrote the Activity handling, which had been very bad! Now you won't have the press several times the back key.
The new .apk can be found in the first post.
I'll attach 2 example bootsounds..
Thanks very useful app.
{
"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 any damage you cause to your device.
I hope you like reading.
You have been warned.
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features:General:See our current feature list at our GitHub!
Device-specific:
OnePlus Camera & Gallery fully working (using APKs directly from OOS 11.1.2.2 or apkmirror.com with verifiable signatures; currently shipping OnePlus Camera v3.14.40 and OnePlus Gallery v4.0.297); including 60fps video recording in 1080p & 4K, watermark, depth effect, smart content detection, actually-working HDR, et al.
DeviceExtras for OnePlus-feature-specific customizations including alert slider modes, DC dimming, High Brightness Mode including customizable Auto-HBM threshold, customizable rendered FPS overlay, digital earpiece/mic gain controls, built-in UI jitter test, and 3-category vibration strength control (thanks to AnierinBliss for all his work on this implementation).
OnePlus-style color modes available through LiveDisplay (6 & 6T have slightly different implementations and you may not notice a difference, but think of "Natural" and "Wide Gamut" like uncalibrated versions of "sRGB" and "DCI-P3").
Ongoing kernel tuning (trying to get the best of both worlds tuning existing QTI perfd & scheduler & lmk, rather than cutting over to Google libperfmgr/powerhints/userspace lmk, definite improvements over vanilla LOS, mostly importing/adapting work by EdwinMoq and mcdachpappe).
Upstreamed updates from 4.9-q branch of Android common kernel for 4.9 LTS (merges courtesy of BananaFunction).
Everything you never wanted to know about slots & A/B devices (but have been forced to find out):
Spoiler: Show/Hide
"Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip by formatting data.
"Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
"Wipe data": This used to be synonymous with "factory reset" in TWRP, without formatting the data partition and losing the contents of internal storage. Now, with TWRP being deprecated and using built-in LineageOS-based recovery, "wipe data" and "factory reset" mean the same thing as "format data" (which means, everything in internal storage gets erased).
"Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
"User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
"OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system. Is always installed to the currently "inactive slot", and will trigger a slot switch upon the next reboot.
Some partitions are duplicated (system, vendor, boot, and a couple others, but not data) and have a "slot A" & "slot B" copy.
"Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" and "inactive" upon next reboot; causing it to attempt to boot from the formerly-inactive slot's boot partition.
The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, vbmeta, and now vendor as of Android 12. If you are planning on going back to an Android 11 ROM that does not build the vendor partition from source (so everything except SyberiaOS, essentially), you'll need to flash the OOS stock vendor partition to both slots from fastboot before installing the OTA zip.
"Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). We finally got a source-built vendor bringup for OnePlus SDM845 (enchilada & fajita) as part of the Android 12 (lineage-19.1) bringup, so some things work better, and some things work worse, but at least it's possible to fix things and keep moving forward to newer Android versions. However, since we're still dependent upon at least SOME binary blobs copied over from OxygenOS 11.1.2.2, the vendor patch level will remain at the release date for the last release of OOS 11, because we can't know for sure that some component isn't vulnerable, no matter how new all of the source-built components are.
"Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system & vendor partitions in custom ROMs for our device are generally built against a particular version of OxygenOS; in this case OOS 11.1.2.2 was the final release by OnePlus before they announced the end of support & updates for the OnePlus 6 series. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than 11, that doesn't matter when you're talking about installing this custom ROM over it. So please; update to OOS 11.1.2.2 firmware (see instructions below).
Notes on stock recovery & TWRP:
Spoiler: Show/Hide
TWRP is deprecated & unsupported, for purposes of bug reporting & getting help with crDroid. I liked it personally, and I agree with all the reasons for wanting to try and keep using it; but the source has been described as a hot mess, the official releases for enchilada & fajita have not had good compatibility with Android 12 or newer (trouble with decrypting file-based encryption for userdata), and there are too many variations & unofficial TWRP-based recoveries for me to keep track of.
Meanwhile, the stock crDroid recovery (based on LineageOS) intentionally cannot decrypt userdata, and doesn't correctly process addon.d OTA survival scripts on A/B devices; so after using it to flash any OTA zips, you'll need to reboot to recovery and manually flash things like Magisk or GApps installers. But for all those shortcomings, it has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot") that lets you flash one image to both slots at once with a single command, and unlocks critical partitions... while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "proper" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"), and 3) gets the updater to call backuptool correctly & process addon.d OTA survival scripts on A/B devices. But they're not going to, and since crDroid is LineageOS-based; it's what we've got, and fastbootd is the best way to update firmware.
The takeaway: If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that; it's an unsupported configuration.
For purposes of doing updates, plan on doing your initial installation from bootloader & recovery then applying subsequent system OTA updates using the built-in Updater tool (Settings > System > Updater), both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk canary for several versions, and MindTheGapps & NikGapps on my tester fajita and MinMicroG "system" install package on my daily driver enchilada.
The built-in recovery DOES support use of a USB thumb drive and will mount it in OTG mode, so any place in the instructions you see "adb sideload", you can instead copy all your things to a FAT32-formatted USB stick and then apply the update from there instead.
Flashing Instructions:Pre-installation prerequisites:
Spoiler: Show/Hide
Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, USB drivers, and a known-good USB cable (see links in post #2).
Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
If you don't KNOW you already have OOS 11.1.2.2 flashed to BOTH slots, follow the "Updating Firmware" instructions below. You may also want a utility like 7-zip in order to extract .tgz files under Windows.
Updating Firmware:
Spoiler: Show/Hide
Reboot phone to bootloader (no USB cable connected until you've entered OEM bootloader).
If you're not already using the stock crDroid recovery, you'll need to 'fastboot flash boot path/to/boot.img' on the computer, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites listed above.
Reboot to bootloader again (actually loads new bootloader contents that you just flashed).
Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery.
Tap "Advanced", then tap "Enter fastboot" (the already-selected first option).
Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/enchilada/fw_update or https://wiki.lineageos.org/devices/fajita/fw_update, except for the very last command ('fastboot reboot').
If you're only updating firmware and were already on crDroid, you can just 'fastboot reboot' which will go back to booting the system normally. If this is part of coming to crDroid 9.x from another ROM, continue with the first-time installation instructions below.
First-time installation:(when coming from any other ROM or stock OOS or crDroid 8.x or earlier)
Spoiler: Show/Hide
*Back up anything you want to keep from the phone's internal storage to your computer/cloud storage, because we're going to format the userdata partition in this process.*
Download boot.img & rom zip to computer.
Reboot phone to bootloader.
Flash boot image to both slots ('fastboot flash boot_a boot.img' then 'fastboot flash boot_b boot.img').
Reboot phone to bootloader.
Use vol +/- keys to select recovery mode & press power button to enter recovery.
On phone, choose "Apply update" > "ADB sideload" & then from computer, 'adb sideload path/to/rom.zip' (substituting the actual path to the actual filename) to sideload the installation zip; the orange recovery header graphic will disappear until the process has completed ("error" messages like "no error", or finishing at 47% on the computer are normal).
On phone, choose "Factory reset / Wipe data", and confirm (note: this will erase everything from the phone's internal storage; make sure that you have backed up anything you want to keep first!). If you want to try out f2fs as a filesystem for userdata, give it a shot. It should be stable. If you don't know, just pick ext4; that's what we've been using forever.
On phone, choose "Advanced" > "Reboot recovery" to reboot into recovery on the newly-flashed slot.
Use adb sideload to flash GApps or microG installer zips (MinMicroG installer requires you to choose "Advanced" > "Mount/unmount system" first, others might as well).
Reboot into system.
If you want to root with Magisk, complete the initial first boot setup, then reboot the phone back into recovery, choose "Apply update" > "ADB sideload", and then from the computer, 'adb sideload path/to/latest_magisk.apk' to flash Magisk, and reboot back to System afterwards.
???
Profit!
Update installation:
Spoiler: Show/Hide
Use the built-in Updater ("Settings > System > Updater") to apply OTA updates as they become available, or to manually flash a ROM zip by going to the three-dot menu in the upper right and choosing "Local update". Seriously, that's it; it processes addon.d survival scripts correctly, including Magisk, MindTheGapps, NikGapps, MinMicroG, and presumably others.
If you must update from recovery, then be aware that the stock crDroid recovery does NOT process addon.d OTA survival scripts correctly on our non-dynamic, non-virtual A/B system-as-root device, so you'll need to do the following:
Reboot phone to recovery.
Choose "Apply update > Apply from ADB" on the phone, and 'adb sideload path/to/installation.zip' from a terminal on the computer (or use a USB drive with appropraite files copied to it and choose OTG as the update source instead).
After installation has completed and the menus have reappeared on the phone, go back, then choose "Advanced > Reboot to recovery" on the phone.
Choose "Apply update > Apply from ADB" on the phone, and 'adb sideload path/to/installation.zip' for each addon like Magisk or GApps installation zip you need in order to match what was initially installed on the phone.
Reboot system.
Please see post #2 for current boot.img files, information about Google apps & microG, release notes, installation notes, known issues, and lots of helpful links.
Please see post #3 for information about bug reporting & troubleshooting.
Sources:ROM:https://github.com/crdroidandroid
Device trees:https://github.com/crdroidandroid/android_device_oneplus_enchilada
https://github.com/crdroidandroid/android_device_oneplus_fajita
https://github.com/crdroidandroid/android_device_oneplus_sdm845-common
https://github.com/crdroidandroid/android_hardware_oneplus/tree/13.0-op6
Kernel:https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
Vendor-specific:https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_enchilada
https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_fajita
https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_sdm845-common
https://gitlab.com/crdroidandroid/android_vendor_oneplus_apps
https://github.com/Terminator-J/vendor_ih8sn
Download:ROM:https://crdroid.net/enchilada/9
https://crdroid.net/fajita/9
Changelog:https://crdroid.net/enchilada/9#changelog
https://crdroid.net/fajita/9#changelog
Links:Visit the official website at crDroid.net
crDroid OnePlus 6/6T Telegram Group
crDroid Community Telegram Group
crDroid Updates Telegram Channel
Donate to help our team pay server costs (PayPal or Patreon)
Donate to support me in maintaining this device (PayPal or Patreon)
crDroid 9.5-r2 - May 2023 ASB release notes/changelog: Changelog since v9.5 (03 June release:
Device trees/hardware/kernel/vendor changes pulled from LineageOS.
Still May 2023 ASB, since the June security bulletin requires merging QPR3, which the ROM team is currently working hard at finishing.
crDroid:
I managed to re-add independent Battery Styles for QS shade compared to statusbar (and battery estimate if you have "turbo", Google's DeviceHealthServices) installed. Enjoy it while it lasts; everything will be ruined again with the QPR3 merge here in a bit.
At least a couple things I'd imagine, I dunno. Haven't been paying attention because I'm always a month behind.
Device-specific:
Updated kernel commits from bananafunction's lineage-20-test branch & upstream LineageOS lineage-20 branch.
Dropped ZRAM writeback (meh, less thrashing on the flash storage pls).
Dropped a few more of the overly-ambitious changes from 9.5 that didn't seem to actually do much, except make it a little more battery-hungry. I think battery life is back where we want it to be.
Re-added the "squash revert" commit in kernel to help with some of the camera usage causing drops to Qualcomm Crashdump mode. But honestly, it's going to keep being a thing with newer Google Camera ports. If you need stability for lots of photos, stick with a GCam port (like DMGC or Urnyx05) based on v7.3 or v7.4 for best results.
"Misc tweaks and bugfixes".
If it feels like it's still slightly too battery hungry, turn on the "GPU Throttling" toggle in DeviceExtras to save a little bit more (may cause a little more jank in gaming).
Other release-specific notes:
People keep complaining about boot loops or losing their GApps or massive battery drains. I get it, sometimes the "Settings > System > Updater" has issues. But frequently the issue is a reading comprehension failure, and the answer keeps being the same: do a dirty flash from the included LineageOS-based crDroid recovery according to the instructions below, and DON'T FORGET TO REBOOT RECOVERY AFTER FLASHING THE ROM ZIP BEFORE FLASHING GOOGLE APPS. If you read NOTHING else from the first post about slots and stuff, at least FOLLOW THE INSTRUCTIONS.
I now have "elite builds" of my custom NikGapps config available for our device, and 16 June and newer releases of "crDroid-op6" now include a few extra packages in there that should help with some app compability going forward (added DeviceSetup, GooglePartnerSetup, DeviceHealthServices, and CarrierServices). See the "Google Apps" section below.
And if you come to the TG channel, I've got a little something something for you kernel-wise that isn't going into the official release build.
Known issues:
Spoiler: Show/Hide
Upstream crDroid/LineageOS things:
Custom fonts in crDroid Settings don't get reapplied to everything on reboot; need to select a different font & then back to preferred font after restarting.
There might occasionally be icons that don't work when "Themed Icons" is enabled in crDroid Home settings. If home screen keeps going black and then reloading, open Settings, then go to Apps > Default Apps, and click the gear next to "crDroid Home" to open our built-in launcher settings, and toggle off "Themed Icons" for now. Send me the crash report URL (paste.crdroid.net) or MatLog zip and it'll tell me which icon needs to get fixed.
Google Apps: If you have MindTheGapps or older NikGapps and you have SetupWizard installed as part of your Google Apps package, then enable Multiple Users and create a new Guest User, the "Setup Wizard" activity will fail to run at the end of the new profile creation, which will leave a couple props unset that normally tell Android that you've finished initial setup; and you won't be able to interact with the notifications/QS shade & will only have the "back" button in the navbar. You can either wait 10 minutes and it automagically fixes itself, or exit the "Guest session" without deleting data, and the next time you enter it, you'll have full control over navigation & statusbar/shades. This seems to be a limitation on multiple custom ROMs currently.
I don't know if this is an upstream issue or device-specific or certain Google Apps packages, but Google Assistant Hotword Detection/Voice Match causes media playback stutter sometimes. So you can either disable it, or doing an adb sideload installation rather than update seems to help some people (permissions issue in Android 13? who knows).
If you get problems with Google Play Store or Android Setup complaining that you need to connect to wi-fi in order to download updates, go into Settings > Apps > "See all __ apps" > [overflow menu] "Show system", then for Android Setup, Google Play Services, and Google Play Store, get app info and make sure to toggle on Network Access for all of them (or turn it off & back on), clear app cache, and then reboot as quickly as possible after. That should get them to realize they CAN connect to the internet after all.
People don't read documentation.
You tell me, with logs!
Installation notes:
Spoiler: Show/Hide
In case of bootloop (boot animation stuck for longer than about 2 minutes and never gets to lock screen), reboot to recovery and manually flash the ROM zip via ADB sideload from computer, then reboot to recovery again, and re-flash your same Google Apps/microG/Magisk/whatever install zips (again via ADB sideload), and reboot system. This *should* take care of any lingering errors with old things getting stuck in your /system/addon.d/ directory that might be trying to preserve old privileged system apps without privileged permissions (which is what causes those boot loops in the first place).
The built-in OTA updater in Settings > System > Updater goes a lot faster if you go into Updater preferences and toggle on "prioritize updater process", and make sure the screen stays on by using the Caffeine QS tile, or "never sleep while charging" toggle in Developer Options, or changing your Display timeout to 30 minutes.
If you're installing MinMicroG instead of Google Apps, then before ADB sideloading the zip, from built-in recovery on the phone, you might need to go to Advanced > and choose "Mount/Unmount System" first. Then go back to "Apply update" and proceed with ADB sideloading as normal to install. I've heard this has been fixed in more recent builds this year, but haven't had a chance to confirm.
General Notes:
Spoiler: Show/Hide
Yes this ROM supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
Tested against latest Magisk canary, works well.
No there won't be official builds with inline GApps; please don't ask. The dev team's policy is vanilla-only whenever possible (and it's very possible with our devices).
Google Apps:
Spoiler: Show/Hide
Maintainer doesn't often use Google Apps personally as daily driver, but here are some notes gathered from peoples' testing:
TL;DR: If you're doing a fresh install, use this Nik GApps custom version (updated 16 June 2023):
https://sourceforge.net/projects/nikgapps/files/Elite-Releases/crDroid-op6/NikGapps-T/
Otherwise, use Nik Gapps Core + Setup Wizard addon (if you're going to restore from a Google Drive cloud backup during setup; *not* the Pixel one, it breaks our launcher) + GoogleSearch addon (for assistant & hotword integration) + GoogleTTS (more voice integration) + Markup (optional, good screenshot editor that you cannot add from Play Store later as a user app) + DeviceSetup, CarrierServices, GooglePartnerSetup, and DeviceHealthServices for now.
https://nikgapps.com/downloads#downloads
If you're already on MindTheGapps, and it's working fine, then ignore this. If you're on official MindTheGapps and facing weird battery drain issues, try updating to newer official version and doing dirty flash of ROM & MTG zip from recovery. If *that* doesn't work, try my modified build. It seems to vary by person and I don't know why.
Due to intermittent issues with excessive battery drain & missing location or network access permissions after Android 13.0 QPR1 that seemed to correlate with MindTheGapps 13.0 arm64 current official release, but not with NikGapps, I went ahead and made a modified build of MindTheGapps that includes additional allowances copied into permissions, default-permissions, and sysconfig XMLs from NikGapps, and the issues seem to be resolved. If you have battery drain issues with MindTheGapps official, then I recommend this package for everyone until such time as I can get the fixes narrowed down and commits submitted for inclusion upstream to the official MindTheGapps project. I have never been able to recreate the drain issue myself, although I have experienced the permissions problems with failure to pre-grant permissions for network access or location to Play Store and Setup Wizard/Android Setup.
However, some folks have had issues with my build that they didn't have with official, so... I don't even know any more. Use what works best if you're already on MindTheGapps.
https://github.com/TJ-Releases/mtg/releases/tag/tau-20230224
Until we can get a fix submitted, I am NOT recommending the use of official MindTheGapps 13.0, as it has begun exhibiting battery drain & permissions retention problems after Android 13 QPR1 was merged in December 2022. If you still need official MindTheGapps, you can get it here:
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
To switch from official MindTheGapps to my modified build (and back):
- Reboot phone to recovery
- ADB sideload the latest ROM zip
- Choose Advanced > Reboot recovery to reboot phone directly to crDroid recovery again
- ADB sideload desired MindTheGapps zip (use my modified build, unless you're specifically trying to help me trace down permissions/battery issues)
- ADB sideload Magisk (if you're rooting)
- Reboot system
Otherwise, in general, try to go with the lightest weight package you can and don't replace the stock dialer/messaging apps (just download them from Play Store and set defaults).
BitGApps ... exist. No idea how that's going. I hear it works though, so give a shot. Don't know the link, sorry.
Flame Gapps I have no idea about in Android 13.0.
https://flamegapps.github.io/download.html
Since we are LineageOS-based, here are the Lineage team's recommendations & reasoning:
https://wiki.lineageos.org/gapps.html
OpenGApps are not recommended, for reasons outlined in the LineageOS wiki link above.
Please report what worked for you, whether or not it survives updates when using the System Updater, whether or not it survives manual "dirty" update flashing via built-in recovery, and whether it passed SafetyNet, so I can keep this list updated.
Magisk and Google Play Integrity API (SafetyNet):
Spoiler: Show/Hide
Without root:
We pass SafetyNet/Play Integrity out of the box, avoiding hardware-backed attestation & falling back to basic integrity (using PixelProps in framework).
I also build & ship ih8sn inline, which should cover all sensitive props to keep most apps from being able to detect root or bootloader unlock.
I don't know how to set up everything correctly to sign builds & verify everything needed to safely enable bootloader re-locking. I'm not even sure it's possible. So just don't try it; you're asking for a trip to MSMTool-land.
With root (Magisk):
If you root with Magisk and configure the Zygisk denylist correctly (see below), you should still pass. For fastest "certified" status, wait after initial installation & signing in to Google to update Play Store & Play Services before rebooting to recovery & ADB sideloading Magisk to root.
Be sure you're on an official topjohnwu release; I recommend beta or canary. "Magisk Delta" is unneeded; we already spoof the props you're worrying about.
Do not install kdrag0n's "Universal SafetyNet Fix"; it's not only unnecessary with this ROM but actively causes problems & interferes with other things (like preferences resetting every reboot).
Look, I don't like the idea of "Shamiko" or anything else that employs LSposed techniquies or similar to do framework injection, and I'm not going to troubleshoot bug reports from people using it. It's a Magisk module that's not open source, so there's no way to verify what it's doing with the root access you have given it. But if that's what makes your ****ty bank app work, then do what you gotta do. I would change to a credit union that doesn't try to hold you hostage with crappy apps.
How to configure Magisk & the Zygisk denylist:
1. Hide the Magisk app:
Go to Magisk > Settings, and choose "Hide Magisk app", granting "install from untrusted source" permission along the way if needed, re-open the hidden "Settings" app
2. Enable Zygisk process hiding:
Go to Magisk > Settings
Enable Zygisk, Enable Enforce Denylist
3. Set up Zygisk denylist:
From Magisk Settings, go to Configure Denylist
Tap overflow (three-dot) menu in upper-right, and select "Show system apps"
4. Find "Google Play Services" and select the following:
com.google.android.gms
com.google.android.gms.persistent [needed for Google Pay/Wallet]
com.google.android.gms.unstable
com.google.android.gms.snet
5. Find "Google Play Store" and select the following:
com.android.vending
6. [Optional, for contactless payment] Find "Google Wallet" or "Google Pay" if installed and select the following:
everything, who cares; it's like 2 processes
7. Back out of "Configure Denylist"
8. Get app info for Google Play Store, force stop, and clear app cache
9. Get app info for Google Play Services, and clear app cache
10. Reboot
Use something like YASNAC to verify that you're now passing Play Integrity API attestation with basic integrity.
Other helpful links:
Download current boot.img files: enchilada / fajita (also attached below)
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA: enchilada / fajita
Firmware update instructions (LineageOS Wiki): enchilada / fajita
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade): enchilada / fajita
MinMicroG (recommend the "Standard" package from "abuse-cl" releases; needs you to "Mount System" in crDroid recovery Advanced options before installing)
Magisk (recommend latest stable/beta v26.1 release; bootloop-to-recovery-after-OTA-update issue appears to have been fixed).
LOGS OR IT DIDN'T HAPPENHow to make bug reports (and how not to):TL;DR: if you've got adb set up on the computer and authorized on the phone, plug into a USB cable, run adb bugreport from a terminal, and send me the zip file it generates, ALONG WITH A DESCRIPTION OF YOUR PHONE SETUP AND WHAT THE PROBLEM ACTUALLY IS.
Spoiler: Show/Hide
i appreciate bug reports, but I also need details. If an app is crashing ("FCing", meaning "force closing") then at a bare minimum, copy the crash log URL and share that with your report.
That probably won't be enough, though, which is why there are two main logs that I'm after, logcat and dmseg.
1. logcatYou can either use the built-in MatLog tool to acquire this, or get it via USB debugging and adb on the computer (which was in the prerequisites section of the XDA first post, so you installed platform-tools and have adb & fastboot on your PATH, riiiight? )
Using MatLog
MatLog is shipped built-in, and it works great. It's built for an older API though, so you'll need to manually grant it permission to access all files (it doesn't know enough to ask since it's a system app and assumes itself to be privileged). If you don't, then you can only use the "Sharing" interface to save logs, rather than saving them to internal storage.
To use, open the MatLog app, and go into settings and tick the box for "omit sensitive info" so that you don't end up sharing your IMEI or email addresses with the world. Probably still best if you PM me the logs instead of share to the group.
Ideally if it's a reproducible problem, reboot, open MatLog, do the thing that causes the buggy behavior, switch back to MatLog, tap on the menu and choose "Save Zip", then send me the resulting file (they're saved to /sdcard/matlog/saved_logs/). Otherwise, try to open it as soon after the issue as possible and Save Zip.
Using ADB (Android debug bridge)
Since we're currently building as "userdebug", you can always grab a logcat even without being rooted. I'm assuming you've got adb and fastboot installed & can run them from a terminal.
Enable Developer Options if you haven't already by going to "Settings" > "About Phone" > scroll down to the bottom and tap on the "Build number" field 7 times to enable, then back up to System and choose the new "Developer options" menu, and toggle on "Enable USB debugging".
Connect the phone to computer via USB, then on the computer open a terminal type adb devices to start the server & verify you can see the phone. At this point you might get a prompt on the phone asking if you want to trust the computer with some ID for debugging; tell it yes (probably always yes, in case you need to do troubleshooting later due to a boot loop). You should see your phone's serial number listed under the output of adb devices in the terminal window. If not, you probably need to install OnePlus USB drivers.
Run adb logcat from the terminal and get ready for a wall of text. Ctrl-C to stop the firehose after about 10 seconds. Save the output to a file. Note: this is the stupid way assuming you just opened a command window or built-in PowerHhell in Windows. Any linux shell or current version of PowerShell should instead be able to just run adb logcat > logcat.txt to dump the output directly to a text file in the current working directory without the wall of text; just give it about 10-15 seconds and Ctrl-C to stop the capture.
That's it! PM me the file, with any other details about what's happening and your setup (device, how you flashed, GApps, and so on).
2. dmesgRequires root, probably USB debugging, platform-tools added to your PATH, and knowledge of what the below instructions mean
Open a root shell on the phone (via local terminal or adb shell via USB).
Run dmesg and save the output to a text file.
PM me the dmesg.txt file, along with a logcat capture as well, and a detailed description of what the problem is, what the behavior is you noticed, how to reproduce, details of your setup (which device, what GApps, what Magisk modules, any custom kernels, how you installed, and so on).
Protip: If you're not rooted, since this is a "userdebug" build, you can go into Settings > System > Developer options, turn on the toggle for "Rooted debugging", and then on your computer, do adb root to restart the adb server process. The next adb shell you run from the computer will get superuser privilege instead and you can run dmesg or do other things without having to root with Magisk.
If you are rooted, I highly recommend installing & using SysLog (by Tortel), available on the Play Store and on F-Droid; it's a GUI app that lets you easily capture both logcat & dmesg & can generate zip archives to send to your favorite maintainer, while allowing for scrubbing potentially sensitive data, and has some other advanced filtering options.
3. A detailed description of the actual problem & how to reproduceMaintainer is not a mind-reader
Describe what the actual problematic behavior is, compared to what the expected behavior is. Don't just throw a logcat at me and expect me to figure out what you think was actually wrong. Explain how to reproduce the bug, and what you were doing at the time. Give me details about your configuration: are you actually on the most current version, did you clean install, did you use the recommended MindTheGapps package, are you rooted & if so what add ons/modules/root-required utilities are you using regularly, etc.
A picture is worth a thousand words. Moving pictures even moreso. If you can use screenshots, or better yet a screen recording, to show me how something is failing, that helps a TON.
Realize that a number of things are beyond my control. I'm not a software developer, I'm not on the ROM dev team, and some things might never get resolved. It's *still* better than OnePlus though, hey?
Feature requests are not bug reports. If you don't have a stack of tested commits that you can submit as a pull request for the dev team to merge, it's not likely to happen. But you can always ask politely!
Other Notes:"Supported" status - PLEASE do not do these things if you want help:
Spoiler: Show/Hide
It's your device to use the way you want of course, but don't expect support for your bug reports if you...
didn't update firmware in both slots.
didn't do a clean flash when first switching to this ROM at this major Android version (13.0).
installed with TWRP/any other custom recovery (or, worse yet, installed that custom recovery after).
aren't using the built-in kernel.
are using extensive root-required modifications & Magisk modules like Project Themer, Lsposed/Xposed/Riru/Shamiko, Dolby Atmos, Viper4A, modified Adreno GPU drivers, etc.
immediately start flashing stuff like "finalize.zip" or migrate restore zips instead of following the actual instructions.
are running decrypted (ugh, just don't).
re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
followed some other installation method different than the steps in the first post.
tried to dirty flash from an earlier crDroid/Android major version (like 8.x) without a factory reset.
Connectivity issues:
Spoiler: Show/Hide
If you are having problems with wifi or mobile data under Android 13, try some of the following (and please let us know if one/all actually fixed things for you):
Get info for the Google Play Store app, go to "Mobile data & WiFI", and toggle network access off (if on), then on (again). Force close the app, then re-open it; see if it finds the Internet now.
Same as above, except for Google Play Services (you'll have to find it in "Settings > Apps > See all __ apps > overflow menu > Show system" then it should be in the list).
Go into Settings > Network & internet, scroll down to "Private DNS" and choose a different private DNS provider or simply turn the feature off.
Go into Settings > Network & internet, scroll down to "Connectivity check" and turn it off (in case connections to Google are being filtered at the network level).
Go into Settings > Network & internet > Internet, tap the gear icon next to the wifi network you're trying to connect to, and change Privacy to "Use device MAC" (some networks actively reject spoofed MAC addresses).
Go into Settings > Network & internet > Calls & SMS, and make sure your primary SIM is actually selected for calls, messages, and mobile data, then back up one menu level, go into SIMs, select your SIM if needed, and make sure "Mobile data" is toggled on.
Go into Settings > Network & internet > SIMs, select your SIM, and change the radio mode to one of the ones that *doesn't* start with "NR", like "LTE/TDSCDMA/CDMA/EvDO/GSM/WCDMA" (or the one without the CDMA/EvDO stuff if you know you're not on a CDMA carrier).
Go into Settings > Network & internet > SIMS, select your SIM, go into Access Point Names, and make sure you've got the correct APN selected.
Go into Phone (whatever you have for the default dialer), keypad, type in *#*#4636#*#* to open the "Testing" activity, choose "Phone information", then in the three-dot menu in the upper-right, choose "Select Radio Band" and choose the correct region instead of leaving it on "Automatic".
OnePlus Camera & Gallery:
Spoiler: Show/Hide
It works. It all works, and it's also the only way to get 60fps video recording on this hardware right now, unless there's a GCam mod with configs I'm not aware of.
This version of OnePlus Gallery requires a Google account to actually exist before it will successfully download the expansion pack. If you're running vanilla or haven't signed into a Google account yet, it won't be able to download the thing it wants.
Oops, I dropped something.
Reserved. If I were you, I'd have reservations about this as well.
One huge ass bug report coming right up
Aaaand we're official!
Just in time to merge Android 13.0_r16 qpr1, which is an enormous rebase of android/frameworks/base/ with over 10K commits different, so Neobuddy89 and the rest of the team have been busy trying to redo all our customization/features on top of THAT for a week now. So everything that was finally working is probably broken again, sweeeeeet!
Thanks again for your work.
I know dirty flash isn't the recommended way, but this worked for me:
OTA 8.10 -> 8.11 -> fastboot flash boot.img to both slots (just in case something's changed since I flashed it the last time) -> reboot to recovery -> dirty flash 9.0 -> flash NikGApps Basic (not the recommended GApps, I know, but I found out too late to switch) - > flash Magisk -> reboot to system.
Last time when I tried to dirty flash 7 to 8, I got a bootloop since I was one version behind unlike this guy, so I figured waiting for the latest 8 release might be the right thing.
So far, so good. System feels much more responsive now and all the minor issues I encountered in crDroid 8 are gone (not sure about RAM management yet, I'll see).
I had a few issues initially, but everything's resolved now:
I had a "Settings Services not responding" pop-up after the first boot, which I fixed by clearing the app's storage
My 6T randomly became completely unresponsive after locking a screen (with a double-tap on the default launcher, I think). I've encountered a similar issue on crDroid 8 several times before, but I think that had something to do with the pocket mode. When it happened on 8, I'd have to force reboot with hardware buttons. This time however long pressing the power button showed me the power menu (although it looked like a standard Android one, with a white background and only 3 options, unlike the crDroid one). This has only happened once and hopefully never will again
My only pet peeves (probably upstream issues and not out device-specific) are:
Weather service doesn't seem to be working (neither OpenWeatherMap nor MET Norway, neither on lockscreen nor the OmniJaws widget). Do I need a custom OWM key?
Mobile icon used to hide when data was off. Now there's a permanent data disabled indicator, which is kinda annoying but I guess I'll get used to it
Terminator.J said:
Aaaand we're official!
Just in time to merge Android 13.0_r16 qpr1, which is an enormous rebase of android/frameworks/base/ with over 10K commits different, so Neobuddy89 and the rest of the team have been busy trying to redo all our customization/features on top of THAT for a week now. So everything that was finally working is probably broken again, sweeeeeet!
Click to expand...
Click to collapse
Bluetooth keeps crashing.Any One Experiencing the same?
For some reason, the GPS doesn't work (in google maps for example). Gave all of the apps location access and made sure to turn on the "use location" toggle. All location services are turned on as well (e.g. google location accuracy). However, location data does work in the metadata of pictures taken by the camera app.
Adnan Hussaini said:
Bluetooth keeps crashing.Any One Experiencing the same?
Click to expand...
Click to collapse
Can't say I've had that issue, with my fitness tracker, or multiple headphones/headsets, or mouse/keyboard...
See post #3 for how to take logs if you'd like to send me a bug report!
Awner said:
For some reason, the GPS doesn't work (in google maps for example). Gave all of the apps location access and made sure to turn on the "use location" toggle. All location services are turned on as well (e.g. google location accuracy). However, location data does work in the metadata of pictures taken by the camera app.
Click to expand...
Click to collapse
Depending on how you installed, or Google apps package, or if you did something like clearing storage for Play Store or Play Services, you might need to go into Settings > Apps > "Show all ___ apps" > 3-dot menu > "Show system", find Google Play Services and Google Play Store and re-grant them permissions again (like location).
Never had a problem with GPS working while driving in Waze regularly, or recording locatoin in photos in in OP Camera, Lineage Aperture (the other "camera" app with darker grey icon).
Please see post #3 for details on how to send me a bug report & what kind of logs/information I'll need.
runtosafety said:
Thanks again for your work.
I know dirty flash isn't the recommended way, but this worked for me:
OTA 8.10 -> 8.11 -> fastboot flash boot.img to both slots (just in case something's changed since I flashed it the last time) -> reboot to recovery -> dirty flash 9.0 -> flash NikGApps Basic (not the recommended GApps, I know, but I found out too late to switch) - > flash Magisk -> reboot to system.
Last time when I tried to dirty flash 7 to 8, I got a bootloop since I was one version behind unlike this guy, so I figured waiting for the latest 8 release might be the right thing.
So far, so good. System feels much more responsive now and all the minor issues I encountered in crDroid 8 are gone (not sure about RAM management yet, I'll see).
I had a few issues initially, but everything's resolved now:
I had a "Settings Services not responding" pop-up after the first boot, which I fixed by clearing the app's storage
My 6T randomly became completely unresponsive after locking a screen (with a double-tap on the default launcher, I think). I've encountered a similar issue on crDroid 8 several times before, but I think that had something to do with the pocket mode. When it happened on 8, I'd have to force reboot with hardware buttons. This time however long pressing the power button showed me the power menu (although it looked like a standard Android one, with a white background and only 3 options, unlike the crDroid one). This has only happened once and hopefully never will again
My only pet peeves (probably upstream issues and not out device-specific) are:
Weather service doesn't seem to be working (neither OpenWeatherMap nor MET Norway, neither on lockscreen nor the OmniJaws widget). Do I need a custom OWM key?
Mobile icon used to hide when data was off. Now there's a permanent data disabled indicator, which is kinda annoying but I guess I'll get used to it
Click to expand...
Click to collapse
There's probably permissions issues going on there. You really should plan on backing up your stuff & doing a factory reset (which will wipe internal storage, sorry) or it's just going to have little lingering issues like this that I can't help with.
Pet peeves:
1. The weather service works flawlessly both with MET Norway & OWM even without a custom API key; came right up for me. Likely needs a clean flash/factory reset to work correctly.
2. Not sure what combination of settings caused that bug to happen, but mobile signal strength should be visible even when data is disabled, since calls & SMS still exist. But yeah; lots of UI-related stuff is likely different. Every major release the ROM dev team has to figure out what will actually keep working or not, and tried to bring features back in or drop them because it's buggy now or causes problems elesewhere or so forth. Honestly the statusbar icon customization options were kind of a mess in Android 12 and it does seem like it's more reliable & consistent now than it was before.
But I understand you miss your favorite setup; I get it. Sorry friend.
Meanwhile, having synced Android 13.0_r16 (QPR1/December ASB), the dev team had to redo all our stack of modifications & customizations on top of it again (for the git-savvy, it's because it's a rebase of all the AOSP repos; more than 10K commits difference, can't just merge in monthly changes).
They essentially had to do Android 13 all over again, and now all of us maintainers are checking to see what broke.
It seems not entirely broken though, so I'll probably start putting up December ASB testing builds in the TG group soon!
Terminator.J said:
Depending on how you installed, or Google apps package, or if you did something like clearing storage for Play Store or Play Services, you might need to go into Settings > Apps > "Show all ___ apps" > 3-dot menu > "Show system", find Google Play Services and Google Play Store and re-grant them permissions again (like location).
Never had a problem with GPS working while driving in Waze regularly, or recording locatoin in photos in in OP Camera, Lineage Aperture (the other "camera" app with darker grey icon).
Please see post #3 for details on how to send me a bug report & what kind of logs/information I'll need.
Click to expand...
Click to collapse
Hi first of all thanks for making this amazing rom! I fixed the issue by formatting my data again. I think everything works now. Really love the device-specific additions that are otherwise missing in other roms. Thank you
I just moved from Rice to this ROM and I feel this ROM is better and more polished.
Thanks @Terminator.J
marcioafoliveira said:
I just moved from Rice to this ROM and I feel this ROM is better and more polished.
Thanks @Terminator.J
Click to expand...
Click to collapse
Yes, in my humble opinion it is better and J always cool, he answer every question on telegram.
Hey there's a weird bug that's been going on and it has been happening with all the android 13 ROMs I have been using. The NFC just quits randomly and blanks out the menu in settings until reboot.
marcioafoliveira said:
I just moved from Rice to this ROM and I feel this ROM is better and more polished.
Thanks @Terminator.J
Click to expand...
Click to collapse
any review compared to LOS20 unoficial? I love LOS but really miss the abilty to customize the rom
Nice work,It suit me well,But i can't get OTA updates,I gess it might be a network issue,so I wonder the OTA adress to find out what's wrong,can some one help?
imokpd said:
Nice work,It suit me well,But i can't get OTA updates,I gess it might be a network issue,so I wonder the OTA adress to find out what's wrong,can some one help?
Click to expand...
Click to collapse
Well, so far there aren't any. That might be why. I've only ever made one official 9.0 (Android 13) release.