Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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... and at CarbonROM Gerrit.
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!
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 adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) 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.
4) Join our Discord server! 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.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
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 Sony Xperia Z3 Compact
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-04-01
Last Updated 2018-07-19
Wow thats good. Thank you very much.
Hi, Myself5! Thanks a lot that you still support our device though you have newer devices.
User experiences and issue list for 2019-03-11 Release
First of all, thanks to @Myself5, @rcstar6696 and all other members of the CarbonROM team for the release of CarbonROM 6.1 Oreo for our device! :good::victory:
User experiences with CarbonROM 6.1:
Installation was smooth. I flashed cr-6.1 and OpenGapps ARM 8.1 on top of my working cr-5.1 installation (dirty flash), so all of my apps and their settings were kept. MindTheGapps 8.1.0 arm, which are recommended by the Carbon devs, are also working fine. Keep in mind that there is no guarantee that a dirty flash works in all cases, so you might have to wipe your data partition. This generally is recommended when updating to a new Android version anyway.
Besides of some small issues (see below), everything runs stable and the system is snappy and smooth. Thermal management and charging speed is fine.
Magisk 16.0 works fine, as well as Xposed Framework (SDK 27) v90-beta3 or alternatively Systemless Xposed (SDK 27) v90.1-beta3 Magisk module. However, there are some force-closes of background apps every now and then, caused by the beta status of Xposed v90.
My Xperia Torch Boost Magisk module is still working well on cr-6.1.
Selinux is set to enforcing, just as it was in cr-5.1.
I found out that Android Messages SMS/MMS app has a high battery drain, which e.g. is also reported for Pixel devices on Android 8 Oreo, so a general bug by Google. Because of this, I switched to Textra SMS (of course you can also use one of the other SMS/MMS apps around), which fixes the battery drain.
Improvements in comparison to cr-5.1:
The camera button now acts exactly like in Sony Stock ROMs, so now focussing and taking pictures is possible with Stock Sony Camera. You can also invoke the Stock Sony Camera by long-pressing the camera button, just like in Stock ROMs, but this doesn't work when the device is off or locked. In this case you can use a double press on the power button, which can be enabled in Carbon Fibers settings.
Booting the device is noticably faster than on cr-5.1.
Lower battery drain than on cr-5.1.
Better, more uniform design.
The ROM is being updated to the latest Android Security Patches.
Apps can be "locked" in the Recent Apps, so when pressing the Clean All button, they keep running.
4K video recordings are possible.
Missing features in comparison to cr-5.1:
There is no option to turn on Network Traffic Indicators yet. (This has been added in 2018-04-05 Weekly.)
Default Camera-App does not allow to save photos to sd-card, puts photos in wrong orientation and is all around very limited. However, there are good alternatives like Open Camera and the Stock Sony Camera. (Since 2018-05-01 Weekly, Snap Camera is used again.)
Issues in Carbon ROM 6.1:
Video recording doesn't work yet with the built-in Camera app, as well as with several other apps like Open Camera and the Stock Sony Camera. Until this is fixed, you can use Footej Camera for video recording as a workaround. (This has been fixed in 2018-05-08 Weekly by @AdrianDC and Milos Ratkovic.)
DoubleTap2Wake isn't working yet. (This has been fixed in 2018-04-11 Weekly.)
The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. (See @Myself5's reply in post #14.)
The gyroscope doesn't work properly yet with certain apps, e.g. Vr Tester - Gyroscope Sensor App and Accelerometer Gyro Tester. (Obviously this is a bug of those apps or of Oreo in general, since @Myself5 could reproduce it on his Pixel 2 XL device, running on stock ROM. Many other apps that use the gyroscope are working fine on cr-6.1.)
Saving and accessing files on SD card doesn't work for certain apps and tools, which could be a Linux permission or SELinux denial issue. For further information and partial workarounds, see post #45, post #49 and post #51. (This has been fixed in 2018-06-05 Weekly.)
Screen Cast still isn't working for me with 2018-04-11 Weekly (I tested this with a Sony and an LG Smart TV which both connected fine to my Z3c on stock ROMs), even with the new boot image from post #103 which is working with @Myself5's Fire TV stick and Wireless Display Adapter. This has been fixed in 2018-04-17 Weekly.
WiFi isn't working on 5 GHz band in some countries, as has been reported in post #1634 on the Z2 cr-6.1 thread, including links to posts with possible workarounds and fixes. There's also an article in the xda wiki with further information. Since 2018-05-01 Weekly, Germany (DE) is used as Wifi country code, but there have been several reports by users from other countries that this doesn't work for them, so is not an universal fix. As a workaround, until this is fixed, you can use my Magisk module from post #195, which you have to change to your own country code by following the instructions that I gave there. Edit: @marcogiannetta posted an improved Magisk module in post #373 which changes the Wifi Country Code accordingly to the system language. A similar issue (wifi dosent connect in Iran) also has been reported on the bug tracker and is being looked after by the devs. Edit: According to post #2092 on the Z2 thread, this issue can also be fixed by installing WiFi regional problem solver Xposed module.
Music files can't be played from SD card with Vanilla Music, Sony Music and several other players. This issue was fixed in 2018-05-08 Nightly, but reappeared on 2018-05-15 Nightly. Until this is fixed again, you can use jetAudio HD Music Player as a workaround. (This has quickly been fixed again in the 20180515-2340 Weekly build.)
When making a screenshot via the Power menu, most of the time the Power menu itself is visible in the screenshot. There should be a slight delay (just 1/10th second might already be sufficient), so the Power menu is already hidden again before the screenshot is taken. This has been fixed in 2018-07-05 Weekly.
Apps like Netflix, MyCanal and MagineTV don't work because DRM WideVine is not supported yet, whereas in CarbonROM 5.1 it was supported. This has been fixed in 2018-08-15 Release.
Lock screen rotation has been removed since 2018-09-11 Release. It was a useful feature when using the phone in landscape orientation e.g. in a car holder and IMO should be added again. Edit1: As a workaround, I made LockscreenRotationEnabler Magisk module which adds this functionality by adding a setting to 'build.prop'. Edit2: Lock screen rotation can also be enabled with GravityBox [O] Xposed module.
NFC extended length isn't supported, which is needed e.g. for reading identity cards with apps like AusweisApp2. (This has been fixed in 2019-03-11 Release.)
NFC-HCE isn't supported, which is needed for Google Pay. (This has been fixed in 2019-03-11 Release.)
Wish list for some further improvement of Carbon ROM 6.1:
Long press camera button to wake and launch camera app when the screen is off or the phone is locked. Edit: I found a workaround which I described in this post.
A toggle to switch to dark UI theme for quick settings. Edit1: The dark UI theme can be forced with ForceDarkModeOreo Xposed module. Edit2: ForceDarkModeOreo unfortunately is one of the Xposed module which cause random app crashes, so it's not advisable to use it. Let's hope that the devs will add this feature eventually.
About time this one got its own thread, huh
Everything works great, no bugs so far and no problem with camera recording (using Footej Camera), though missing hardware key rebindings and i cant enable power notifications
Downloading right now. Lets see how it compares to Omni 8.1
EDIT (my comment from a few pages later):
After a few days with it, I can say it's already suitable for daily use. Using MindTheGapps (tho I will switch to OpenGapps pico, I don't want Google app ), Magisk 16.
It's smooth and very stable. No crashes or major issues for me so far.
Battery life is acceptable, worse than stock (doh), and perhaps even LOS 14.1. Thermal management and charging speed is fine.
No idea about the camera, mine is broken (HW) and I never use front one.
A few suggestions and comments:
Add some power balancing options like with LOS (better performance or battery life).
Also, I love how you can customize RGB values on LOS to make it more yellowish even during day, plus night light. Any idea what workaround I could use? My blueish screen is killing me and I can't use night light all day.
Good to hear night mode is being worked on.
How to make quick tiles menu like on 7.x? I preferred auto expanding options for mobile data and silent mode. Can't find it in fibers.
Hi, Great that development is ongoing - Thanks a lot!
One thing, got the same problem with the none carbon Oreo Version:
got problems with whatsapp. Video isn't running. The phone doesn't build up a connection. Chat works, but whatssap call or video not.
Skype ist working without problems ...
Any Ideas?
I installed it with a full wipe - system, cache, dalvik, data, internal storage. Used TWRP 3.2 for ROM (to mind error 7) and TWRP 3.1 for installation of MindTheGApps.
Thanks for help!
Thanks for the ROM, working great for me.
I have accidently deleted live wallpaper picker. Tried download a few different versions from the internet but nothing works. Where can I get the one this ROM is using?
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Nice post, okij
okij said:
[*]The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. Also, forcing dark theme via Dark Tricks Xposed module doesn't work.
Click to expand...
Click to collapse
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Kocane said:
Nice post, okij
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Click to expand...
Click to collapse
Doesn't substratum work?
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
Substratum works fine
Greets ted!
okij said:
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Click to expand...
Click to collapse
For things like Networks indicator: Some additional features will surely come with time, as you said.
Video recording: I think it was the Z3 thread where I explained it in detail: The commits to fix Video recording do work (kind of), but are WIP, so we're all working on getting them stable and polished, then they will be merged as fast as possible. When that happens is rough to estimate, I wouldnt expect it to take much longer than 2-3 Weeks though.
DT2W: As you said. Fixed and merged, will be included in the Next Weekly.
For the Dark Theme: Isn't that a Pixel only feature? For that to work you'd need assets for a "dark theme". On Pixel devices those are on the /vendor partition, so obviously not present on our Z3C. Correct me if I'm wrong please.
Thanks for the detailed report, will gladly keep on checking it with followup builds.
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
It does. Install the Substratum app and flip the switch in CarbonFibers -> Privacy to make it work.
The Switch is disabling the Security measures Google merged in the March ASBs. By default Subs completely removes them, but we decided to go for an opt-in for those that want to use it while keeping the "security" Google intended to have with merging it for those that don't want to.
First off all, thank u for this amazing work! Rom is awesome.
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
2 - Someone can tell me if led notification works? Not work here...
Sorry bad English...
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Any idea anyone?
Thanks!
marlontravagli said:
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
Click to expand...
Click to collapse
Yes, this is a great additional feature when using DT2W and one of the reasons that I use GravityBox. @Myself5: It would be great if you could implement this feature for those of us who don't use Xposed. In GravityBox it can be found under "Power tweaks -> Proximity wake up" and the additional option "Ignore for incoming call" which is also worth implementing.
2 - Someone can tell me if led notification works? Not work here...
Click to expand...
Click to collapse
I can confirm that LED notifications are working here, just tested this with missed call (using Google Dialer) and incoming email (using AquaMail).
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Laus_bub said:
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Click to expand...
Click to collapse
I don't use WhatsApp, but I guess that the not working video call has to do with the not fully working video recording (see #1 in the issues list I posted here).
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
ElLoloFR said:
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
Click to expand...
Click to collapse
Did you try removing all other modules? For me the very same thing is happening if I try to use the fbind (Folder Bind) module. You can try to remove all modules, if u use the Magisk Manager for Recovery Mode (mm).
I tried and :
"No magisk installation found."
So I installed Magisk v16, then installed this one.
I could install mm, this was the only module installed.
I uninstalled mm, rebooted without uninstalling Magisk V16, and the phone booted !
But I can't open Magisk Manager v5.6.4, stucked in the app logo...So Magisk seems to be installed, but I can't use it :/
EDIT : Well, after a recovery reboot, reinstall f magisk V16, phone boot correctly and Magisk is alive.
I don't know how this is working, but it's working.
No doubt, you helped me, many thanks
GLOBAL USERS, LATEST NEWS: WORKING GCAM3 with FRONT CAM and TIME LAPSE!
This thread was created to achieve, at first, two goals:
Organize useful information on the main topic about GCAM for GL/CN users and CONSTANTLY UPDATE IT;
Direct new users to a "solution" regarding GCAM on Global/China variants;
MY SPECS:
Phone: Redmi Note 5 Pro 64GB/4GB (CN and came with GLOBAL ROM installed)
ROM: Havoc Mod ROM (Android 9.0/Pie)
Understand the "problem" between the Indian vs Global/CN variants:
Indian variant uses Sony sensors on both front and rear cameras. So modders didn't had too much trouble porting GCAM for them;
GLOBAL/CN variants have the Samsung S5K2L7 sensor (same sensor used in RN6 Pro) on the rear, and on the front camera we have a Omnivision sensor (here lies the problem).
Know that: THERE'S NO WAY OF MAKING GCAM WORK ON ANDROID PIE WITHOUT A PATCH!
MAGISK METHOD NOTE:
UPDATE: There might be a light for your, warrior!
As gracefully explained by our fellow Desmanto, there are some steps you can take in order to make the Magisk modules work.
If it helps you on your lonely journey, please hit the Thanks button on his response. I'll only link his explanation.
I noticed that installing a PATCH through it isn't a guarantee of success.
Even when I installed AdAway on my phone, magisk took a while to finally grant root access to it... So it means it's a shot in the dark.
Once I was able to install the RN5 Camera Patch v1.035a(Pie 9.0).zip by nhappyman and make it properly work. But only once!
As pointed out by the user misiek735:
"If you install everything and you choose 4k with eis enabled in gcam 5.1 settings
and it does not work (camera error) then it means that patch is not working
at all and you make somewhere during the instalation proces a mistake."Since the process of installing the patch, rebooting, checking if the patch was installed successfully, removing it, rebooting, installing again...
isn't as pretty as I'd like, I advise you all to take the TWRP route.
TWRP ROUTE: THE LIGHT AT THE END OF THE ROAD:
Right, this is where the fun begins!
First of all, my rig consists of two GCAM:
Pixel 3 (For anything related to rear camera: Normal, Portrait, Nightsight and SlowMo) - MGC_6.1.021_BSG_Arnova-based_v.1.3d_TInNeun_2
Pixel 2 (Front Camera; Front Portrait Mode) - GoogleCamera-5.1.018.177624777-Urnyx05Mod
Patch used: RN5 Camera Patch TWRP v1.035a (Pie_9.0).zip (Reading through threads, I've came to the conclusion this one is guaranteed to work. New versions are out there to be tested. Please share your results)
With these guys I can do pretty everything* (passing the "misiek735 test" pointed out earlier):
SlowMo: [email protected] or [email protected]
Front/Rear Camera Portrait
Front/Rear Live Motion
Rear Camera video: [email protected], [email protected]
>>>*REMEMBER THAT ANY PIXEL 3 CAMERA FCs ON FRONT CAMERA!<<<
>>>*Not anymore. Check the end of this post!<<<
DOWNLOAD:
- Fantastic mods/patch, but... Where to find them?
At the moment, I'm going to point out the direction (since I'm not aware if I hold any rights to upload myself those files)
TWRP v1.035a patch:
Look for a Telegram Group called RN5 Camera Patch™ | Channel (@rn5cp - https://t.me/rn5cp)
Go to group details (tap on the group's title) -> Files -> Search in October 2018 for: RN5 Camera Patch TWRP v1.035a (Pie 9.0).zip
GCAMs:
Celso Azevedo's Page;
Telegram Group: Google Camera (Whyred) ( @gcamWhyred )
Telegram Group: Gcams Downloads (Whyred) ( @gcamdownloadswhyred )
And this very XDA page.
It's worth reading this message posted by Desmanto
Hope this thread can provide useful and reliable information for you guys.
Please share additional information, ask questions and correct any wrong information.
Cheers.
UPDATE: 2019/04/30
LATEST NEWS: WE HAVE A WORKING GCAM3!
Yesterday was release a brand new version for us GLOBAL users! It's a GCAM3 (Pixel 3 Camera App) with a working front camera!
Search for the APK on the Telegram Group gcamWhyred!
Look for:
Gcam 6.2.024 Advanced V2.1.beta._190429.1903.apk
In order to make the front camera work and use a lag-free app, you must use these settings presented on the attachments!
Or click here and check my shared Google Photos gallery.
Note:
I'm currently using the TWRP v1.035a patch
There's a new version called RN5 Camera Patch v2.034a that might fix the issues I'm going to talk about next, but I didn't test it yet (please, you can provide feedback here if you will), so bear with me.
Known Issues (So far):
If you zoom (use the digital zoom prior to the shot), it'll FC the app and a low resolution (probably the image in the buffer) will be saved in your gallery. (Zoomed shots on the front camera work!) Just set "Using Sabre" OFF and will be good to go! (From what I've understood this an algorithm to enhance zoomed pictures)
Occurred to me once, but you might get an black picture every now and never.
While recording something the "viewfinder" might show a worst image than the one which is actually being recorded.
Night Sight is laggy! It'll work as intended but you'll experience it's 1/3s shutter speed. Seems like it's already collecting data about the scenario prior to the shot.
UPDATE: 2019/05/14
Latest News: We have a working GCAM v6.2.030 (i.e. Time Lapse capable)
Today was shared on gcamWhyred telegram group a GCAM3 with the new time lapse.
Look for:
Gcam_6.2.030_Advanced_V2.1beta6.190512.1059.apk - Link for those who avoids Telegram (not posted by me)
In order to make the front camera work and use a lag-free app, you must:
Enable advanced mode.
Use these settings for the front camera and disable Sabre (also use RAW10 on RAW format, if I'm not wrong this will remove the lag on the rear camera).
The "Disabled Google Photo" actually sets it as default gallery (probably a bug)
In advanced settings, if you try to use the dark theme, it won't work. (Again, there's a reason why it still called "beta")
Created: 2019/03/06
Last Updated: 2019/05/14
Can you link here or dm me newest patch version for Pie ? @SpiderPack
I would like magisk version
EDIT: v2.025a patch for you
Both Miui and Pie 9.0 Custom
Only Magisk because there isn't TWRP edition of this version
https://mega.nz/#F!vDRVVC6b!M3RMVNkUK-RoEpt-IkwU_A
Gcam which I am using now:
https://www.celsoazevedo.com/files/...f/GCam-5.1.018-Pixel2Mod-Arnova8G2-V8.3b1.apk
Please recommend good gcam so i also stick it there
Has anyone tried this on the latest stable MIUI 10 build?
And I can see v2.025a Patch Module in the Telegram group. What's that for?
SpiderPack said:
GLOBAL/CN variants have the same Sony sensor on the rear, but on the front camera we have a Omnivision sensor (here lies the problem).
Click to expand...
Click to collapse
A small correction here. The Global/CN variant (RN5 AI) doesn't have Sony IMX486 sensor on the rear camera. Instead, it sports Samsung S5K2L7 sensor (same sensor used in RN6 Pro) with effective pixel size of 1.4 μm.
The4anoni said:
Can you link here or dm me newest patch version for Pie ? @SpiderPack
I would like magisk version
Click to expand...
Click to collapse
You can find them on RN5 Camera Patch™ | Channel telegram group.
SpiderPack said:
You can find them on RN5 Camera Patch™ | Channel telegram group.
Click to expand...
Click to collapse
I don't have telegram....
Thank you for the amazing thread, I'm sure it'll help a lot of people! But you're missing something: you should give the groups' @ instead of the groups' name. With the name only it's a lot harder to find.
TheForgotten said:
Thank you for the amazing thread, I'm sure it'll help a lot of people! But you're missing something: you should give the groups' @ instead of the groups' name. With the name only it's a lot harder to find.
Click to expand...
Click to collapse
Thanks for your input! I'll add the links.
great thread, thanks for sharing, I have one question though, how to undo a TWRP patch? is there a way like we have in Magisk? thanks in advance
Hello,
Is there any way to fix whatsapp video call lag when camera2api / patch is enabled? Everything in gcam 5.1 working fine with the patch, but the lags at whatsapp video call is a deal breaker for me, hope there is a way, been looking at how to fix this since day one..
Cheers!
*Im using PE 9.0
Hacksfallout said:
Hello,
Is there any way to fix whatsapp video call lag when camera2api / patch is enabled? Everything in gcam 5.1 working fine with the patch, but the lags at whatsapp video call is a deal breaker for me, hope there is a way, been looking at how to fix this since day one..
Cheers!
*Im using PE 9.0
Click to expand...
Click to collapse
Hm... That's odd, I've just tested with my boss and the WhatsApp Video Call was good enough. I don't know if it was supposed to have less delay (though, to me, was acceptable), but unfortunately I'm not aware of any fixes.
Dr.TheMaster said:
great thread, thanks for sharing, I have one question though, how to undo a TWRP patch? is there a way like we have in Magisk? thanks in advance
Click to expand...
Click to collapse
Yes! I'm pretty sure that dirty flashing the same ROM (and version) will bring everything back to what it was.
Best Gcam for v2.025a patch and 9.0 Resurrection Remix ?
Also uploading v2.025a Magisk (no TWRP Version) patch for MIUI 10 and Pie 9.0 Custom
Here
https://forum.xda-developers.com/showpost.php?p=79054168&postcount=2
i've tried every patch, every gcam version, none worked. crashes, only blue pictures, pictures not taken at all. As much as I love whyred, gcam ports are mehh
KissKK said:
i've tried every patch, every gcam version, none worked. crashes, only blue pictures, pictures not taken at all. As much as I love whyred, gcam ports are mehh
Click to expand...
Click to collapse
Really? Please share your specs* and maybe we can find something for you
*I meant the ROM you're using.
SpiderPack said:
Hm... That's odd, I've just tested with my boss and the WhatsApp Video Call was good enough. I don't know if it was supposed to have less delay (though, to me, was acceptable), but unfortunately I'm not aware of any fixes.
Yes! I'm pretty sure that dirty flashing the same ROM (and version) will bring everything back to what it was.
Click to expand...
Click to collapse
Hmm thats weird, are you in Pixel Experience rom? Because i only facing this issue in PE, at Havoc 2.2 and MIUI the bug does not happen
KissKK said:
i've tried every patch, every gcam version, none worked. crashes, only blue pictures, pictures not taken at all. As much as I love whyred, gcam ports are mehh
Click to expand...
Click to collapse
Try this bro
https://forum.xda-developers.com/showpost.php?p=79054168&postcount=2
Make sure to remove previous patches, etc. or best is reflash rom
Works like a charm on Resurrection Remix Pie
I am using 06.03.2019 build
Works on AOISP 9.0
Hacksfallout said:
Hmm thats weird, are you in Pixel Experience rom? Because i only facing this issue in PE, at Havoc 2.2 and MIUI the bug does not happen
Click to expand...
Click to collapse
No, I'm on Havoc OS Mod.
Is PE camera2api enabled by default? Check with the developer? Maybe?
Let me ask you something else: Why did you end up on PE? I went through the RN5 forum before buying my phone, and even though PE looked fancy and awesome, HavocOS seemed to provide more customization.
SpiderPack said:
No, I'm on Havoc OS Mod.
Is PE camera2api enabled by default? Check with the developer? Maybe?
Let me ask you something else: Why did you end up on PE? I went through the RN5 forum before buying my phone, and even though PE looked fancy and awesome, HavocOS seemed to provide more customization.
Click to expand...
Click to collapse
Oh i see now why at havoc the whatsapp bug does not occur, i looked at their changelog, one line caught my eye.. its the "Force HAL1 package in some app", i think that may be the case, the devs of Havoc is aware of this bug i think, so whatsapp must be one of the app that being forced to use HAL1. (HAL3 is camera2api right?)
Hmmm, its more like personal taste i think I kinda like a minimal rom with minimal costumization.. and PE is the one for me, it really gives me the taste of Pixel phone :laugh:
Have anyone tried a TWRP patch newer than version 1.035a?
If so, what's new? Any changelogs?
Hi @Urnyx05
First of all, thank you and to all the involved devs for sharing your vast knowledge and work on making ports of the Google Camera app.
On my particular device, I ran into an issue where the output file of image capture is strongly hued green. This occurs even after a phone restart, reinstallation, and an app data clear. Video capturing seems unaffected and the live preview is normal.
Sorry as it is my first time getting a Camera2 Test, but I don't have a clue which option to capture, so I captured the first dropdown item I saw. Also, all links are from Google Drive, sorry. Also, since I'm a new user, I can't put any links. Sorry for that.
- Camera2 Test (included description)"https://drive.google.com/file/d/1UPQP-kk0U-git5cdEhgw_we9hfxT1R2P/view?usp=sharing"
"https://drive.google.com/file/d/1IsZAuGZWwV1zQvXZ-LCMNLMEUKgJRZgX/view?usp=sharing"- Phone, ROM, any fixes installed
T-Mobile Samsung Galaxy S8+ Snapdragon
Stock ROM; Unrooted; Locked Bootloader
No fixes installed; Fresh
- Name of the apk you're using;
GCam_7.3.018_Urnyx05-v2.1.apk
- Screenshots or video recordings of the bug if you're able to;"https://drive.google.com/file/d/1pukskKl9xWRNfKxWloTXVSSokktcrLi_/view?usp=sharing"
"https://drive.google.com/file/d/1xskMLlDU4SqNFrXn10cScyioYQF4uM6d/view?usp=sharing"- A logcat if there's a crash (How to save a logcat: video guide, advanced guide);No crash- Steps to reproduce the bug/crash;Installing the app on the device and taking a photo immediately/opening the setting first does it.I hope you find the gracious time even amidst all of what's happening around. Keep safe and thank you.
Hi, have a good time.
since today, i have problem with the phone camera (both cameras) and flashlight.
when i try to open that, the pop-up message says: Camera has stopped unexpectedly.
and the flashlight icon had been disabled.
i tried clearing cache, hard reset, wrap all caches, factory reset, but i faced with this problem till now.
my phone and camera does not broke and everything was normal.
how i can fix this issue?
i will be very glad to see your help.
Andorid version: 9
Security patch level: August 1, 2020
Software number: 2.55.401.3
Does it work with a diffrent camera app?
.
DavidxxxD said:
Does it work with a diffrent camera app?
Click to expand...
Click to collapse
No, when i try other camera apps, the app get freezed and then after a while crashes.
my flashlight is also disabled and i can't run that.
anyone don't know how i can find the problem?
We are in the same boat.. Flashed several RUU's even downgraded OS from Pie to Oreo and still nothing.. Camera app works for a while (30seconds- 1 or 2 minutes) and crashes. BUT I found that Video record is working fine even though photo modes, both front and back are unavailable. Just hold Camera app's icon and choose Video. Then check if it works.. When I try to get into selfie mode - App crashes. So.. I think it's front camera's issue... maybe it's dead or nearly dead... Front and Back cameras and flashlight are linked, so if one has issue it affects the others.
P.S. Attached Log files..
Hello everyone!
I have HTC U12+. As you know this phone requires a buffer fix so Google Camera could work on it. I rooted my phone with Magisk and used packed in a module shell Mr. Wyroczen's Buffer Fix for HTC U12+. Everything worked fine for 2 month and then stock Camera and Flashlight apps started to crash. I flashed several RUU's, downgraded OS from Pie 2.55.401.1 to Oreo Exodus 1.68.2401.4 and it didn't help. Upgraded from Oreo Exodus 1.68.2401.4 to Pie Exodus 2.37.2401.3_R and that didn't help too.. Phone was never damaged physically or drowned in water so I don't know what's happening. I can't blame overheating because after downgrading to Oreo Camera app worked fine for 12 hours and I captured videos in 4k60fps and nearly 150 photos using both front and back cameras.
Now after upgrading to Pie Exodus 2.37.2401.3_R i figured out that Video capture on main(back) camera still works if I hold the Camera app's icon and choose Video. But changing to Selfie mod crashes Camera app and I can use neither Front nor Back cameras in Photo mode. But Video capture and Flashlight are working.
I don't think it's Buffer fix's issue. It worked for 2 month with no issues.
I attached Logs. Maybe someone could understand what the problem is and help me to fix it..
Before this incident I had Kirisakura 4.9.246_Imagine 1.2.0_Next+ kernel and Magisk(itself 20.4 and manager app 7.5.2) modules installed:
Buffer Fix (Camera)
EdgeSenseSlide
Busybox NDK 1.31.1
Greenify for Magisk 4.7.5
Riru Core 21.3
Riru EdXposed 0.5.0.0 (4548) (YAHFA)
Substratum 1020
Systemless Hosts 1.0
Edxposed ( 4.5.7 ):
Greenify
LuckyPatcher
I appreciate any help you can provide.
Hopefully yours,
urik7200.
@urik7200 Please be aware that you won't receive any support on XDA if your issue is due or somehow related to Lucky Patcher!
XDA Forum Rules (excerpt):
...
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
...
Click to expand...
Click to collapse
Oswald Boelcke said:
@urik7200 Please be aware that you won't receive any support on XDA if your issue is due or somehow related to Lucky Patcher!
XDA Forum Rules (excerpt):
Click to expand...
Click to collapse
I don't think this issue is related to Lucky Patcher. According to logs System can't get acces to camera due permission is not granted.. What permission and Why? I don't know..
signor.rayan said:
anyone don't know how i can find the problem?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Have you tried to load into Video mode by holding Camera icon?
Moving away from main thread to avoid spam
Original Question:
Hi,
first of all, thanks a lot for your effort bringing lineage to the pixel 4a.
I've got a problem with the main (front 12.2 MP) camera (please see attached logcat).
When opening the default camera app (as well as with my test with google camera) the screen stays black and I can't take pictures. I'm on build number lineage_sunfish-userdebug 11 RQ2A.210505.003 b609c3a431, but had this problem with the previous build as well (I was able to take pictures a few builds back, though).
Does anyone else have issues with the camera not working or is it just me?
Thanks a lot and let me know, if there's any further info I can provide that would be helpful for troubleshooting.
Thanks and regards,
C
second log from main thread
Original text:
Hey again
I clean installed the 20210527 build (and corresponding recovery) today and first thing I did was trying the camera... The org.lineage.snap is slow to non-responsive, the screen stays black and ultimately the camera app crashes...
The attached log shows multiple errors (as far as a noob like me can tell ).
If I'm the only person affected by this, is there anyone who could help me troubleshoot the issue... different hardware in Europe... or hardware failure... false stock firmware (though 100% sure it was on 11).
Thanks again and regards,
C
(If there's a better place for bug reports, kindly let me know )
reply to post
Hey @mangokm40
thanks for your feedback. I neither have magisk nor any custom kernel installed.
I basically came from stock android 11 and followed the installation instructions .
As per this lineage wiki I installed mindthegapps according to the instructions.
Do you or anybody have any other idea? As I seem to be the only one affected, I guess a bug report wouldn't be in order, would it
Thanks again, appreciate your support
Chris, stop using the stock/default app and use a Gcam port: https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Like PXMod (cstark's PXv4.5: PXv4.5_GoogleCamera_7.2.014.apk (cstark27, 2020-09-04, pixel)
I think you'll find the same and more features than the stock app, and it's a lot more stable. No issues taking front camera pics (you can also enable HDR+ for the front camera).
sk8223 said:
Chris, stop using the stock/default app and use a Gcam port: https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Like PXMod (cstark's PXv4.5: PXv4.5_GoogleCamera_7.2.014.apk (cstark27, 2020-09-04, pixel)
I think you'll find the same and more features than the stock app, and it's a lot more stable. No issues taking front camera pics (you can also enable HDR+ for the front camera).
Click to expand...
Click to collapse
thanks for the input, but i fear, that won't help in my case... I already tried the gcam mod of this post, which didn't work either
there might be darker forces at work with my pixel 4a...
nonetheless, I'll try your version asap and come back with the result.
thanks for your time and effort
I have the same issue. The rear cam stopped working. Upgrading to the latest 18.1 build did not help. I guess an update for "carrier services and device personalization apps" from play is causing this, as this are the only changes i noticed on my p4a.
hey guys,
sorry for the delay, but finally closing the loop on this one.
thanks to @razorloves , who looked a the logs and confirmed my suspicion, that an actual hardware issue might be the issue, I rolled back to stock and was able to confirm, that the camera issue had nothing to do with LOS 18.1 .
the same problem occured with stock, so I returned and exchanged the phone.
new phone with official LOS 18.1 has been working smoothly for two weeks now, including both cameras
so again, thanks @razorloves for your support and of course thanks @PeterCxy for a great rom.
cheers,
C