[10][OFFICIAL] CarbonROM | cr-8.0 [hotdog] - OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.

[10][OFFICIAL] CarbonROM | cr-8.0 [hotdog] - OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
Other than previously provided ROMs, this is using the "normal" method of providing a flashable zip.
You should start off with the latest OxygenOS on both slots and then proceed to flash Carbon.
You must at least use TWRP 3.4.0-1 by @mauronofrio to flash this.
Download the ROM and optionally GApps, reboot to TWRP.
Flash the ROM
Reboot recovery (to switch between slots)
Flash GApps (optional)
Format /data*
Done
*As TWRP is currently unable to format /data you can use fastboot to format
Code:
fastboot -w
It appears that fastboot on Windows has issues with the wipe command. In that case use both of the following commands
Code:
fastboot erase userdata
fastboot erase metadata
After the first flash you'll be able to use the builtin updater to profit from seamless updates when updating Carbon.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the OnePlus 7T Pro
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2020-09-09
Last Updated 2020-10-13

How would you flash the ROM if TWRP cannot decrypt data? Sideload, OTG?

Bugs and screenshots ?

Lossyx said:
How would you flash the ROM if TWRP cannot decrypt data? Sideload, OTG?
Click to expand...
Click to collapse
Both option work, if you want you can also push the file to /cache via adb and flash as regular. I totally forgot that TWRP still has encryption issues with OOS cause it's fine with AOSP based ROMs like Carbon.
Phreaker8 said:
Bugs and screenshots ?
Click to expand...
Click to collapse
If there were bugs they would be listed in the OP and the builds wouldn't be tagged official. Screenshots can be found in the gallery section of carbonrom.org.

How do you push the file to /cache via adb and flash as regular?

TheLittlemodder said:
How do you push the file to /cache via adb and flash as regular?
Click to expand...
Click to collapse
Put your file in the same folder of your ADB then open ADB and use this command:
adb push FILENAME /cache/

Mrdream94 said:
Put your file in the same folder of your ADB then open ADB and use this command:
adb push FILENAME /cache/
Click to expand...
Click to collapse
Then what is the flash command after i've pushed it to cache

TheLittlemodder said:
Then what is the flash command after i've pushed it to cache
Click to expand...
Click to collapse

Great rom! I flashed it manually by using payload dumper and fastbootd commands (on stock recovery). But then I realized that this rom does not have Gapps built in like most other roms
So now I need to flash TWRP to install Gapps....
Please includes Gapps in the next release. I would greatly appreciate it.
Also, device specific features such as DC Dimming and Refresh rate switcher is very useful. Hopefully the dev read this message.

thanks for this great rom.
Verstuurd vanaf mijn HD1913 met Tapatalk

Zealith said:
Great rom! I flashed it manually by using payload dumper and fastbootd commands (on stock recovery). But then I realized that this rom does not have Gapps built in like most other roms
So now I need to flash TWRP to install Gapps....
Please includes Gapps in the next release. I would greatly appreciate it.
Also, device specific features such as DC Dimming and Refresh rate switcher is very useful. Hopefully the dev read this message.
Click to expand...
Click to collapse
The instructions on how to install as well as the warning that GApps are NOT included is in the OP. We will NOT include GApps in this or any further builds. I genuinely don't see a reason on why you wouldn't want to install TWRP anyways and, as also stated in the OP, you only need to install this once as the builtin updater has backuptools support meaning GApps and things like Magisk will automatically reinstall on the updated version.
The screen is configured to run in QHD+ 90Hz by default. We don't plan to introduce a refresh rate switch because there's zero need for it. DC dimming may come at some point though.

TheLittlemodder said:
Then what is the flash command after i've pushed it to cache
Click to expand...
Click to collapse
The cache partition is readable by TWRP so you just can flash the file from TWRP searching for it in cache partition

Can we not flash this via fastboot? I really don't want to be messing with different partitions as it messes with my banking apps and safety net.
Sent from my [device_name] using XDA-Developers Legacy app

speedyjay said:
Can we not flash this via fastboot? I really don't want to be messing with different partitions as it messes with my banking apps and safety net.
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t-pro/development/10-carbonrom-cr-8-0-t4160681/post83477287
Read two comments up.
And I'm not sure were you're getting at? This 'messes' with same partitions as it would with fastboot no?

Myself5 said:
The instructions on how to install as well as the warning that GApps are NOT included is in the OP. We will NOT include GApps in this or any further builds. I genuinely don't see a reason on why you wouldn't want to install TWRP anyways and, as also stated in the OP, you only need to install this once as the builtin updater has backuptools support meaning GApps and things like Magisk will automatically reinstall on the updated version.
The screen is configured to run in QHD+ 90Hz by default. We don't plan to introduce a refresh rate switch because there's zero need for it. DC dimming may come at some point though.
Click to expand...
Click to collapse
That's a very understandable explanation. The reason I don't prefer flashing by TWRP is because some roms (like PA) does not have the vendor.img or odm.img file in their payload, so I needed to extract the oxygenOS vendor.img and odm.img file and flash it all together by fastbootd on the stock recovery. I don't prefer flashing oxygenOS first and then flash other roms so that's just me I guess. Turning the refresh rate down to 60hz can be a great option to save battery. Maybe you can make it a optional toggle in the power saving option. Glad to hear that it is locked at 90hz because my experience on Paranoid Android rom which have automatic refresh rate switcher really buggers me out as it is causing a lot of flickering issues. Can't wait for DC-Dimming and new features!

Zealith said:
But then I realized that this rom does not have Gapps built in like most other roms
So now I need to flash TWRP to install Gapps....
Please includes Gapps in the next release. I would greatly appreciate it.
Click to expand...
Click to collapse
Are you a member of the Open Handset Alliance?
I'll answer that for you: NO.
Are any of the 3rd-party ROM developers a member of the Open Handset Alliance?
I'll answer that one for you too: NO.
Ergo, 3rd-party ROM developers have no legal right to distribute G-apps.
https://arstechnica.com/gadgets/201...rolling-open-source-by-any-means-necessary/3/

Lossyx said:
https://forum.xda-developers.com/7t-pro/development/10-carbonrom-cr-8-0-t4160681/post83477287
Read two comments up.
And I'm not sure were you're getting at? This 'messes' with same partitions as it would with fastboot no?
Click to expand...
Click to collapse
No, it really doesn't. If theirs only a dtbo, vbmeta, system etc to flash via fastboot, the stock recovery is left in tact as well as the vendor etc. If you go messing with the recovery and flashing **** through that, you'd have to do it on both slots (A/B) correct?
Sent from my [device_name] using XDA-Developers Legacy app

speedyjay said:
No, it really doesn't. If theirs only a dtbo, vbmeta, system etc to flash via fastboot, the stock recovery is left in tact as well as the vendor etc. If you go messing with the recovery and flashing **** through that, you'd have to do it on both slots (A/B) correct?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
There's an install instruction in the OP... You should make sure to have the latest stock installed on both slots first to have a "clean start", but you're only required to Flash the ROM once.
Judging by your signature, you're in the wrong forum though, anyways. The OnePlus 7T Pro 5G (McLaren), which we also support, is NOT the same device as the OnePlus 7T Pro.
You're looking for this thread: https://forum.xda-developers.com/7t-pro-mclaren/development/10-carbonrom-cr-8-0-t4160715

Exabyter said:
Are you a member of the Open Handset Alliance?
I'll answer that for you: NO.
Are any of the 3rd-party ROM developers a member of the Open Handset Alliance?
I'll answer that one for you too: NO.
Ergo, 3rd-party ROM developers have no legal right to distribute G-apps.
https://arstechnica.com/gadgets/201...rolling-open-source-by-any-means-necessary/3/
Click to expand...
Click to collapse
Ahh yes. Totally forgot "that" existed. Well go ahead and take down every ROM that includes Gapps because they have no "legal right" to distribute Gapps. Right?
Pretty sure no one here have the legal right anyway. We're not manufacturer or OEM or a company. We're just developers modding our devices to make the best out of it. It's not like some FBI agents going to show up on our doorstep only because we installed a ROM that have Gapps included.
But I get it, and I fully understand why Gapps is not included and will never be included in this ROM as stated by the dev and how the "Open Handset Alliance" works. It's no big deal but I thought that it would be more convenience hence why I question about it in the first place.

Zealith said:
Ahh yes. Totally forgot "that" existed. Well go ahead and take down every ROM that includes Gapps because they have no "legal right" to distribute Gapps. Right?
Pretty sure no one here have the legal right anyway. We're not manufacturer or OEM or a company. We're just developers modding our devices to make the best out of it. It's not like some FBI agents going to show up on our doorstep only because we installed a ROM that have Gapps included.
But I get it, and I fully understand why Gapps is not included and will never be included in this ROM as stated by the dev and how the "Open Handset Alliance" works. It's no big deal but I thought that it would be more convenience hence why I question about it in the first place.
Click to expand...
Click to collapse
It's not our jurisdiction to take down others, but Google can if it pleases them and they did so in the past. On top of that, many users use custom ROMs to get rid of Google services, so it's "better" not to include them given it's only 5 clicks away from being installed via TWRP anyways.

Related

[ABANDONED][ROM][Pixel 2][UNOFFICIAL] LineageOS 15.1 / 16.0 [walleye]

{
"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"
}
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM and reboot of flash to TWRP
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing

Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.

Is link not posted yet?

I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!

JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?

JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...

Any chance for an MD5

jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f

TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.

Thanks very much for sharing this. I've got it installed and it's running fantastic.

Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!

razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.

Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?

Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support

@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.

redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo

I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?

Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.

banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview

Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list

[9][OFFICIAL][WEEKLY] CarbonROM | cr-7.0 [taimen]

Fyi your post isn't loading on the XDA app.

gforceriders said:
Fyi your post isn't loading on the XDA app.
Click to expand...
Click to collapse
Shows up fine on the XDA labs app :good:

Badger50 said:
Shows up fine on the XDA labs app :good:
Click to expand...
Click to collapse
After you posted now it's working lol. Strange man strange. Carry on with flashing peeps.

Rock on brother! Be flashing this next week when back from my cruise!!

What gapps do you recommend for this ROM. It has been a while since I ran carbon.

gforceriders said:
Fyi your post isn't loading on the XDA app.
Click to expand...
Click to collapse
gforceriders said:
After you posted now it's working lol. Strange man strange. Carry on with flashing peeps.
Click to expand...
Click to collapse
Haha, weird things.
encephalon9986 said:
What gapps do you recommend for this ROM. It has been a while since I ran carbon.
Click to expand...
Click to collapse
I recommend OpenGapps.
Flashing procedure is
Flash Carbon
Flash TWRP
Reboot to recovery (this switches slots, it's important)
Flash GApps
Done

is anyone else having trouble with Gboard themes on this ROM? If I pick a gradient theme it just hangs and crashes.
I flashed this with Mini gapps first and had a hard time getting through setup, tried again with pico with more success.

Edmontonchef said:
is anyone else having trouble with Gboard themes on this ROM? If I pick a gradient theme it just hangs and crashes.
I flashed this with Mini gapps first and had a hard time getting through setup, tried again with pico with more success.
Click to expand...
Click to collapse
I flashed the micro package and can't even get past checking for updates. The data transfer tool keeps just keeps crashing.
Edit: Tried flashing the pico package instead and now device health services keeps crashing.

Has anyone tried razorloves' MindTheGapps package?
https://androidfilehost.com/?fid=1395089523397912604

Myself5 said:
Haha, weird things.
I recommend OpenGapps.
Flashing procedure is
Flash Carbon
Flash TWRP
Reboot to recovery (this switches slots, it's important)
Flash GApps
Done
Click to expand...
Click to collapse
How to flash if I only want twrp temporary? Same way?

omair2005 said:
How to flash if I only want twrp temporary? Same way?
Click to expand...
Click to collapse
Leave out the "Flash TWRP" part and replace "reboot to recovery" with "reboot to bootloader and boot the twrp image"

Not judging but simply confused...
I see people not wanting to install twrp and it just makes no sense to me why I would want to limit my options and functionality.
It's been like almost a year since twrp had been totally stable for me with no decryption or touch issues.
Again, what is it folks are afraid of??

I'm digging how clean and fast this ROM is. Hopefully you get your server issues resolved soon.

Trying this out again! Carbon was the first ROM I've ever used on my Pixel 2 XL and absolutely loved the experience.

Edmontonchef said:
I'm digging how clean and fast this ROM is. Hopefully you get your server issues resolved soon.
Click to expand...
Click to collapse
So do I... We already have a new host because we're fed up with the old one. Currently waiting for the old one to finally answer our support ticket and bring the server back on so we can move our data to the new server and can call it a day with the old host.

Has anyone tried installing NanoDroid with this?
I went from factory image -> flash rom -> flash twrp -> reboot recovery -> flash magisk -> flash full nanodroid.zip
This leads to a bootloop until it boots back into recovery

When I try to set up any password, it does not let me proceed after the second test. Confirm gets grayed out

Bilge656 said:
Has anyone tried installing NanoDroid with this?
I went from factory image -> flash rom -> flash twrp -> reboot recovery -> flash magisk -> flash full nanodroid.zip
This leads to a bootloop until it boots back into recovery
Click to expand...
Click to collapse
The issue here would be magisk. You usually need to boot to the system at least once before you can sucessfully flash Magisk. Don't know the reasons but it's seems to be an ongoing theme on A/B devices. Same happens on my OP6 and 6T

Myself5 said:
The issue here would be magisk. You usually need to boot to the system at least once before you can sucessfully flash Magisk. Don't know the reasons but it's seems to be an ongoing theme on A/B devices. Same happens on my OP6 and 6T
Click to expand...
Click to collapse
So theoretically I need flash the rom in 'A,' flash magisk on 'B', boot into the system once, reboot recovery into 'B,' and then install nanodroid?
Edit: Well I ignored Magisk and rebooted to recovery to install nanodroid after rom installation and it booted back into recovery unfortunately.

[UNOFFICIAL]Paranoid Android Quartz Alpha [OnePlus 7T Pro]

{
"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"
}
Hi, it was my personal idea , i took the initiative to create an XDA thread so that you all get a taste of what's coming soon. I didn't want to keep this any more to myself. So this thread is sure to be updated soon. You must have thought that your device doesn't have any support right ? Wrong !
We’re really excited to announce the release of Paranoid Android Quartz Alpha, based on Android 10.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. For those who are unfamiliar, Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhances the overall user experience. This time around he have his wallpaper app Abstruct, were you will be able to find all of the Paranoid Android wallpapers alongside a huge amount of amazing wallpapers.
The alpha builds include adjustments and improvements on top of the stock Android CAF base. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features.
Device-specific issues
SafetyNet fails
Note: Custom kernels are explicitly unsupported and will cause issues unless they state that they are AOSPA compatible or AOSPA based!
Note: If you used your root access to mess with your device do not ask for help in this thread or send any kind of log to ask for anything. Instead, create a thread in Help section of OnePlus 7T Pro
Download
Official Release: Link will be added as soon as we release
@33bca UnOfficial Personal Builds: Link will be added as soon as I upload my builds
@kessaras UnOfficial Personal Builds: https://mega.nz/#F!U45BgIhK!gmdNFXiPLH7a1_th2_FwDw
Paranoid Android [Quartz] official release: Soon !
Instructions & requirements
This device runs under OxygenOS 10 (Android 10 / Q) vendor, make sure you are coming from OxygenOS 10 (Android 10 / Q) or flash it from Fastboot just before flashing AOSPA package.
**Flash OxygenOS 10 (I recommend using at leastOxygenOS 10.0.4)
**Format Data
Install AOSPA (for now from fastboot)
Here the commands to install PA from fastboot.
Code:
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
** Only required for the first flashing.
Important / Useful links
OpenGapps
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Our kernel source
Help us improve PA by submitting good bug reports possibly with a log attached. Learn how to take logs here.
Our device maintainers for OnePlus 7T Pro are @33bca and @kessaras. Mention (@) them if you need some assistance and/or when reporting bugs.
Cheers and #StayParanoid!
XDA:DevDB Information
[UNOFFICIAL]Paranoid Android Quartz Alpha [OnePlus 7T Pro], ROM for the OnePlus 7T Pro
Contributors
kessaras, 33bca, herna
Source Code: https://github.com/AOSPA
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: At least 10.0.5.HD01 or newer
Based On: CAF
Version Information
Status: Beta
Created 2020-01-16
Last Updated 2020-04-27

Reserved

Here you will find a very nice guide on how to make a useful logFULL GUIDE "How to provide a good bug report"https://forum.xda-developers.com/g4/help/guide-providing-logcat-t3814517
Please post only for debugging purpose. This thread was NOT meant to be used for chat or any type of discussions.
Caution:
I built gapps afterwards and i haven't formatted my device. So if you get any kind of crash, even if it's unimportant, upon your initial set up during your 1st log in , let me know about it to fix it asap.

Thanks for this a lot

Thanks a lot for this! Pleasant surprise in the morning, you made my day Keep up the good work! I hope other roms will follow this way of flashing and releasing roms. Will flash it today THANK YOU!

Yay, we're on the track :highfive:

Does this have support for the T-Mobile McLaren 5G version? Super excited for PA, thanks for this!

DanDroidOS said:
Does this have support for the T-Mobile McLaren 5G version? Super excited for PA, thanks for this!
Click to expand...
Click to collapse
it should.
personally i don't know because i don't own that McLaren model.
Guys the initial setup wizard from google may cause issues.
Code:
pm disable com.google.android.setupwizard
if it crashes and i will solve this as soon as i find the best gapps package for us.
For now thats the best i found.

Nice! Made my day!
GAPPS included?
Without TWRP it's hard to flash it
---------- Post added at 12:02 PM ---------- Previous post was at 12:02 PM ----------
Nice! Made my day!
GAPPS included?
Without TWRP it's hard to flash it

Attention. I'm uploading now a build with working GAPPS.
And from now on i will upload only OTAs but you will have to flash them manually.
I will upload a full firmware when there is an update there, otherwise there is no reason to flash all the partitions.
Hold on few minutes and the build will be there.
Enjoy.
EDIT:
It's up but i'm unsure if this time again the initial setup wizard is fine as i didn't format my phone, i need it.
Do not forget to fastboot -w to format it before you flash anything when coming from another rom.

kessaras said:
Attention. I'm uploading now a build with working GAPPS.
And from now on i will upload only OTAs but you will have to flash them manually.
I will upload a full firmware when there is an update there, otherwise there is no reason to flash all the partitions.
Hold on few minutes and the build will be there.
Enjoy.
EDIT:
It's up but i'm unsure if this time again the initial setup wizard is fine as i didn't format my phone, i need it.
Do not forget to fastboot -w to format it before you flash anything when coming from another rom.
Click to expand...
Click to collapse
thanks a lot mate! will flash it clean and report btw the build says jan-15, it`s the new build or?

darkoj2007 said:
thanks a lot mate! will flash it clean and report
Click to expand...
Click to collapse
Ok. And everyone keep in mind that it's not easy for me to format everyday. If this setup wizard by Google has any issue now or in the future , be patient with it. We still don't have GAPPS so I'm doing what I can with these.

kessaras said:
Ok. And everyone keep in mind that it's not easy for me to format everyday. If this setup wizard by Google has any issue now or in the future , be patient with it. We still don't have GAPPS so I'm doing what I can with these.
Click to expand...
Click to collapse
the last build says jan-15 10:06, this the last build or the one from today isn`t showing up?

darkoj2007 said:
the last build says jan-15 10:06, this the last build or the one from today isn`t showing up?
Click to expand...
Click to collapse
It is the same build. I only changed the Google setup wizard apk inside.
Rom is close to stock oxygen stable. Only this apk gives me trouble since I can't format to test it, I need the phone at work.
If it still crashes I will keep changing it until we get one which works. Or you can do it urself too. I build with root access to adb , until we officially release. Extract a working SetupWizard and adb push it in place to replace the one in product/priv-app

kessaras said:
It is the same build. I only changed the Google setup wizard apk inside.
Rom is close to stock oxygen stable. Only this apk gives me trouble since I can't format to test it, I need the phone at work.
If it still crashes I will keep changing it until we get one which works. Or you can do it urself too. I build with root access to adb , until we officially release. Extract a working SetupWizard and adb push it in place to replace the one in product/priv-app
Click to expand...
Click to collapse
I did a clean flash. "Android setup keeps stopping" after I insert pin. can`t move from there. Can I do something to get past this?

darkoj2007 said:
I did a clean flash. "Android setup keeps stopping" after I insert pin. can`t move from there. Can I do something to get past this?
Click to expand...
Click to collapse
Either wait till tomorrow , either adb shell, pm disable com.google.setupwizard.
If pc doesn't have access now because it hasn't done first boot, just wait until tomorrow.
Without TWRP we can't do anything more.
If current TWRP can mount system and product partitions you can rm -rf /product/priv-app/<path to setup wizard>
Really sorry. Can't test that stupid setup wizard currently at my phone. Tomorrow last day of week at work , then I can test.

kessaras said:
Either wait till tomorrow , either adb shell, pm disable com.google.setupwizard.
If pc doesn't have access now because it hasn't done first boot, just wait until tomorrow.
Without TWRP we can't do anything more.
If current TWRP can mount system and product partitions you can rm -rf /product/priv-app/<path to setup wizard>
Really sorry. Can't test that stupid setup wizard currently at my phone. Tomorrow last day of week at work , then I can test.
Click to expand...
Click to collapse
Sadly can`t be done. Can`t see the phone with adb. no worries mate, I hope we will get through this and we can enjoy the rom. I assume you use it so probably there are not any bugs that keep us from using it as daily driver. Have a nice day

Thanks a lot for this! Started worrying about support for the 7t Pro!

kessaras said:
Either wait till tomorrow , either adb shell, pm disable com.google.setupwizard.
If pc doesn't have access now because it hasn't done first boot, just wait until tomorrow.
Without TWRP we can't do anything more.
If current TWRP can mount system and product partitions you can rm -rf /product/priv-app/<path to setup wizard>
Really sorry. Can't test that stupid setup wizard currently at my phone. Tomorrow last day of week at work , then I can test.
Click to expand...
Click to collapse
You can also do it from the ADB enabled stock recovery.
Do you thing the Safetynet will be fixed later? Would be nice to use Gpay.

tibcsi0407 said:
You can also do it from the ADB enabled stock recovery.
Do you thing the Safetynet will be fixed later? Would be nice to use Gpay.
Click to expand...
Click to collapse
Sorry for slight offtopic, but how do you use Gpay in Hungary?

[ROM][UNOFFICIAL][Android 11] LineageOS 18.1 [joyeuse/miatol][22/01/21]

{
"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"
}
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
We have progressed to LineageOS 18.1
Flash instructions :
Use latest pbr recovery for miatol, supports decryption - beta available here, https://pitchblackrecovery.com/joyeuse/.
DO NOT - Wipe data!, ONLY FORMAT, otherwise you may hose the phone.
There is a way to fix this without the fastboot factory clean, flash and lock with the official Xiaomi tool, which was forcing you to clean and lock... now available here: https://github.com/Szaki/XiaomiADBFastbootTools
If you hose the phone, use this tool - you need to install JRE though, as the tool is Java base. Put your phone is fastboot, use the tool to download the latest global rom (or whichever). Then go to where its downloaded, extract the .xy/tar file, then go back into the tool and under "image" select the folder INSIDE the folder you just extracted, then select "clean install" and install it. This will flash the majority of imgs but will error out at the end and be unable to create the "user data" partition.
That's okay, because all of the partitions will be setup again, and you can flash any rom you want again. So when its done, and still in fastboot, fastboot flash recovery recovery.img (recovery.img being the latest joyeuse pbr recovery, you renamed to recovery.img and were in that folder in the command prompt, so it will flash that recovery) or use the tool to select that recovery and it will flash it for you and reboot into for you if you like.
(Do this step last, after Magisk, if you want to unencrypt, no worries if you don't unencrypt - PBR recovery will decrypt your data ON THE SECOND TRY OF ENTERING YOUR SCREENLOCK PIN NUMBER...), the new PBR Miatol Beta 10/14/20, fixes this issue, it is now decrypted on the first entry of the phone's lockscreen PIN. Then flash disable_dm-verity_forceencrypt.zip available here for those who want decrypted data partition: https://zackptg5.com/android.php#disverfe and other places as well.
If you are encrypted and decide to unencrypt later, you will need to flash the disable_dm-verity_forceencrypt.zip in miatol recovery, then format data. Store roms, gapps, recoveries (just in case), disable_dm-verity, magisk install and uninstall and all that stuff on the SD card, so you can use them in PBR after you format DATA (the first step after installing PBR miatol recovery), just FYI. Then do the following:
Flash ROM
Flash OpenGAPPS for android 11 nano
Boot into android, make sure its working and install Magisk Manager 8.0.7, then reboot into recovery and install Magisk 21.4 (in recovery, I did not need to extract the boot.img and patch in Magisk Manager, and reboot into recovery to flash the patched boot.img, but your results may be different): https://github.com/topjohnwu/Magisk/releases. If you want to unencrypt (no guarantees its permanent though) you need to format data, THEN FLASH MAGISK, then flash disable_dm-verity (always the last step)- I usually wipe dalvik and cache too.
USE LATEST MIATOL PBR RECOVERY, PLEASE.
SD card issues resolved with the implementation of the EXFat android driver.
Source Code: https://github.com/LineageOS
Kernel Source: https://github.com/Redmi-SM6250 or Stock kernel from Miui
Apologies for the lack of updates, was diagnosed with stage 4 metastatic cancer and this project was not on my priority list anymore...
Update 28/1/21:
Release notes:
LineageOS
Device: Unified (Miatoll)
Developers: ScaryMen1325 & Loptr4
ROM Version: 18.1
Android Version: Android 11
Build date: 22/01/2021
Status: UNOFFICIAL
Changelog:
• Fixed power related issues
• Added useful apps (thanks to Dev: Emulond for that)
• Other fixes and performance improvements
Notes:
• It's 2nd test version, if you found bugs, give log.
• Using loki kernel by default, haven't tested custom kernel.
Download here:
https://drive.google.com/file/d/1M5-cRBfrRdBdNYGzy5G9bOa1Ncf5JkE4/view?usp=sharing
Please note this is a unified release, you should do a clean install unless you're coming from a unified ROM alreadyl.
Will keep you more regularly updated now that I'm out of the hospital....

Perfect will try tonight

Belpek said:
Perfect will try tonight
Click to expand...
Click to collapse
Have you tried it?
How is it? Good for daily?

There are so many Joyeuse LineageOS ROMs I don't even know where to start.

i don't see you mentioned mobile network in bugs section; does it work? i'll try this rom in a couple hours

Tell me please. If phone will be locked with black screen and i say "ok google". Will it work? Or it will work only if screen is unlocked?

sorry if its not much, since i can't do much on this rom. flashed nikogapps, google sign-in succeded but it seems that i cant install anything from play store.
(dumb me forgot to screenshot, it only says "something went wrong" when i try to install an app from play store)
about ok google from lockscreen/screen off, i tried it, also not working. can't confirm about volte since volte still relatively new here and hasn't developed that much.

Why nikgapps? Open gapps nano is recommended.
Sent from my Redmi Note 9 Pro using Tapatalk

Flash it and using it by now, so far so good, sometimes it gets a little freeze but nothing serious, miracast reboots phone so dunno if this is a bug or not, proximity sensor is another one cuz while I was in speaking with my pal screen was on all the time and my ear activated bluetooth and DND
Have nothing to talk about VoLTE cuz in my country is not available.
ANX modules left my phone in bootloop so instead I went for GCam. Flash unofficial opengapps nano and make sure to use Wi-Fi to complete the first run.
Magisk canary works so it can be rooted.
Keep the hard work!
*Sorry if I made some writing mistakes, english is not my native language. Cheers!!

Tried flashing the latest build (02.10.20) using the latest TWRP from the thread you linked but I get the "can't install package over new build" error. Is it required to come from stock miui?

gigahurts said:
...
Newer Build:
https://mega.nz/file/PlkgiSzS#C_tIspgbtGDrweztQ83lADHyEQf4dTkIUiSAqgjVAFk
NOTE: You should be on 11.0.7.0 QJZMIXM (EU) Global firmware for this build. Also, I have a newer build, but its not ready for primetime and has issues with SMS and Call Log enabling permissions.
Oh, and BTW, if you hose your ROM/Phone, just flash vbmeta.img in fastboot to avoid using the factory fastboot img flash, otherwise you many need to wait another 7 days to unlock the bootloader.
...
The dev for this build is: @wight554, all thanks and credit go to him, he is awesome, and I, for one, seriously appreciate this ROM as it works very well for me. It is so snappy and smooth, with a super fast boot time, no reboots and generally pretty frickin AWESOME!
...
Click to expand...
Click to collapse
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.

Swiftor said:
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.
Click to expand...
Click to collapse
hey Swiftor,
We will continue to work on this rom. LineageOS has been around a long time, development has spread across so many devices, however, the hardware of many devices is very similar, so support will continue. The last Redmi Note 8 pro, had a mediatek SOC, and made development difficult until MIUI decided to release its source. The snapdragon platform is very mature and is more easily and readily available to develop roms for. Redmi Note 10 pro has been released in India, and has a slightly better processor 765g vs 730g, but the kernel and hardware are very similar, so I development for this phone and the Note 10 pro should parallel and continue. We are working on submitting an official 18.0 release, but have to have all hardware (and software) fully functional and as close to zero bugs as possible. I predict development to continue as long as Xiaomi continues to release new MIUI roms for this device (and they continue to release roms for phones much, much older than this).
I have updated the first post with a newer release. Let me know if you have any issues and I will try to help.
Thanks for the props too

does magisk 21 work on the latest build? really excited for android 11

So this will not be compatible with curtana devices?

Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.??

everything is working perfectly and its showing charging rapidly , it was on 88% and showing 10 minutes until full
everything is completely smooth gonna keep it for my daily use

Bantryred said:
Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.
Click to expand...
Click to collapse
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse

there're few thing that you need to fix @gigahurts
1) you putting wrong kernel source. its should be this link
2) why would you mirror it when you can get it in his sourceforge

Why is today's build 590MB while all others are 1.1GB?

pwnaz said:
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse
Click to expand...
Click to collapse
Sorry for the delay, Im on Curtana so dont know if it makes a difference, but I used no. 16 - mi 10 Global(11)
I also had to hide Magisk Manager

CherishOS V4.8 [13] [Gapps/Vanilla] [NB1] [Unofficial]

Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,

Kasi1906 said:
Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,
Click to expand...
Click to collapse
hey, thank you i am glad you are happy with it, always nice to see things like this, appreciated.

4.2 build is up, happy flashing, changelog in git page

marceldossantos91 said:
4.2 build is up, happy flashing, changelog in git page
Click to expand...
Click to collapse
Thank you for the timely security update! My gratitude is still very high. The ROM works perfectly. So far I have not had any problems.

I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear

satanvade said:
I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear
Click to expand...
Click to collapse
Hi, you can follow the guide in the Q & A section linked above or in our telegram support group, but the basic idea is:
Unlock bootloader + critical
Flash Tvirus 2.0, which includes twrp 3.6 already (there is however a 3.7 update available, which supports decryption in A12/13, but 3.6 can flash fine)
Flash the rom
Wipe data
Reboot to system
If you need further support, we are more responsive in our support group

It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock

guorium said:
It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock
Click to expand...
Click to collapse
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added

marceldossantos91 said:
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added
Click to expand...
Click to collapse
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!

guorium said:
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!
Click to expand...
Click to collapse
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me

marceldossantos91 said:
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me
Click to expand...
Click to collapse
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.

guorium said:
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.
Click to expand...
Click to collapse
thanks

marceldossantos91 said:
thanks
Click to expand...
Click to collapse
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.

guorium said:
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.
Click to expand...
Click to collapse
thank you for the log i will look into it and see if i can resolve it in updated builds

marceldossantos91 said:
thank you for the log i will look into it and see if i can resolve it in updated builds
Click to expand...
Click to collapse
No problema. PE A12 has the same problema. Must be easy to miss.

4.4 build is up, happy flashing

marceldossantos91 said:
4.4 build is up, happy flashing
Click to expand...
Click to collapse
Thank you!
Enjoy

Kasi1906 said:
Thank you!
Enjoy
Click to expand...
Click to collapse
tysm appreciate it

4.6 build is up, happy flashing!

Develop Bugs

welcome