Database Info

[APP/MOD][Nov 19th][1.0.3] DCIM compliant Camera

2012-08-25: Breaking news - DCIM Helper is here.
This means Camera DCIM is now obsolete and you're advised to migrate to DCIM Helper.
It is a free app for everyone.
There are a couple of extra features (currently just one...) which require a donation to be enabled. Wait, don't get mad!
If DCIM Helper detects you're running Camera DCIM, you will be recognized as a "Special donor" and you'll have everything unlocked. :victory:
For further information, you can read here.
Do you hate when iPhoto won't show the pictures you shot with your Android device, but it works fine with your friend's HTC Sense device? Why would that be?!?
That's simply because Google's camera does not comply with the DCIM standard, used by every other Digital Camera in the world (and HTC Sense does too!)
With this app, your Android device will be able to.
FEATURES:
- DCIM compliant digital camera
- Full Gingerbread Camera, as of latest source code (Android 2.3.5)
- Camera DCIM can be installed together with the official Android Camera, no overlapping issues!
- Camcorder app has been unhidden and can be choosen from the application launcher (check first screenshot)
- Support for Windows, Linux and Mac OS X hosts (don't worry about Thumbds.db, ._IMG0001.jpg files and so on!)
- "Automagically" converts existing picture files in Camera dir to the DCIM naming.
SOURCE CODE:
Google has been notified of this issue on June 2009 but has ignored it.
I've submitted a fix for the official Android Camera on July 9th, 2011 with no reply. If you are able to build your own ROM, I welcome you to download the fix and apply it to your source code! HTC has built a DCIM compliant camera, after all.
If you don't know how to build your ROM, or just want it hassle-free, then this is your app, less than $1 away from you.
In the spirit of Open Source, all the modified source code (in addition to the original fix) is available online to whoever wishes to check it out.
CHANGELOG
2011-11-01 - 1.0.2
- Attemped to work around a crash reported on the Market on devices without sdcard (Nexus S).
2011-09-07 - 1.0.1
- Added support for .mp4 and .m4v files in the "automagic" renaming
- Fixed FC opening Camcorder w/ Infuse 4G and other Samsung devices.
2011-09-02 - 1.0.0
- Initial Market release

How install this mod?
Pozdrawiam

Do you know if CyanogenMod has this patch included already? If it doesn't could you commit it?
Sent from my HTC Vision using Tapatalk

kred9k said:
How install this mod?
Click to expand...
Click to collapse
Download from Android Market.
EDIT: Or grab the source code from the github repository and compile in Eclipse.
g4rb4g3 said:
Do you know if CyanogenMod has this patch included already? If it doesn't could you commit it?
Click to expand...
Click to collapse
It doesn't. the patch is public and on github. I'll try sending the CM Team a twitter message...
EDIT: Twittered... let's see.

thanks for releasing this apps. finally something
Sent from my SAMSUNG-SGH-I997 using XDA App

2011-09-07 - 1.0.1
- Added support for .mp4 and .m4v files in the "automagic" renaming
- Fixed FC opening Camcorder w/ Infuse 4G and other Samsung devices.

Deleted.....

shadowch31 said:
Deleted.....
Click to expand...
Click to collapse

Any news of this being added to cyanogenmod or reply from google?

tetsuo55 said:
Any news of this being added to cyanogenmod or reply from google?
Click to expand...
Click to collapse
No reply from Google, but it was partially my mistake: in order to submit code to Google, the issue tracker is not the right place. However, until the source code comes back online I can't send a patch to the right place.
No reply from CyanogenMod, I even cloned the repository from github and pushed the patches, no activity at all.

hrk said:
No reply from Google, but it was partially my mistake: in order to submit code to Google, the issue tracker is not the right place. However, until the source code comes back online I can't send a patch to the right place.
No reply from CyanogenMod, I even cloned the repository from github and pushed the patches, no activity at all.
Click to expand...
Click to collapse
People just need to make them wake up. Lol, but i definitely like this idea. Don't give up
Sent from my PG06100 using Tapatalk

2011-11-01 - 1.0.2
- Attempted to work around a bug reported on the Market.
The bug was happening on a device without an SDCARD (Nexus S), I am not sure the fix will work, code should have worked from the beginning.

Fixing the AOSP camera app is nice. Do Google accept improvements into the official code?
I sure hope someone will add tap-to-focus to both the still and video camera. I'd also like to have tap-to-focus working while recording video because continuous AF can sometimes ruin some shots by introducing several seconds of blurry footage, or sometimes won't AF again while in an unfocused state.
iOS lets you tap to focus while recording video, making continous AF a non issue.

Interesting. How does this compare to MIUI camera on AOSP ROMs?

Cares said:
Interesting. How does this compare to MIUI camera on AOSP ROMs?
Click to expand...
Click to collapse
I'm not familiar w/ the MIUI Camera, but it's part of the MIUI ROM, not of AOSP ROMs. This is the very same source code of AOSP Camera w/ the DCIM patch and some minor bug-fixes.

People have extracted the MIUI camera and made flashable apks for AOSP ROMs.

2011-11-19 - 1.0.3
- Fixed "issue" with sdcard/_externalSD directory used in LG phones. Thanks to Danford for reporting the issue!

Off the market again?

I am really interested in getting this working with ICS 4.0.3 & 4.0.4. It really is a pain in the ass when you try to sync with iPhoto or other similar applications due to Android completely ignoring the DCIM specification... I mean, I guess they tried due to the fact that they use DCIM as the location to store the photos but completely ignore the format in which to use.
Would anyone be up for helping? I am sure this patch could still be applied to the ICS camera source code.

GeekyScott said:
I am really interested in getting this working with ICS 4.0.3 & 4.0.4. It really is a pain in the ass when you try to sync with iPhoto or other similar applications due to Android completely ignoring the DCIM specification... I mean, I guess they tried due to the fact that they use DCIM as the location to store the photos but completely ignore the format in which to use.
Would anyone be up for helping? I am sure this patch could still be applied to the ICS camera source code.
Click to expand...
Click to collapse
When ICS was released I tried updating the app to the new camera only to discover that Google changed lots of components (no biggie) and used private/unreleased code (wtf?) so I could not update the app.
I'll give it another go, however I'm moving to another app (which I have been developing since ages - well, I have been not developing since ages) which can work with every camera app on the Market.
PRO: you can use any camera you want, especially since Android base camera sucks big time. It's really crappy.
PRO: it works with stupid makers like LG or Samsung on devices which lack a real SD card.
CON: it's an external app, so if the device is under stress it could kill the app. Or if I release an update, you have to manually start it again by hand (or reboot the device).

[ROM][JB] Team EOS 3 *JELLYBEAN* Nightlies - TF101

Team EOS​JB 4.1.1 TF101​NIGHTLIES​
Continuing on from the success of the EOS ICS roms, we present to you EOS3, based on JELLYBEAN!
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. For the latest news on Team EOS releases make sure you follow @teameos on twitter and on IRC on Freenode in #teameos.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated every now and then, and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS Nightly builds: http://goo-inside.me/devs/teameos/roms/eos3/nightlies/tf101/
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:
Temporary Gapps package gapps
--
Features:
Because these are nightly builds the included features are constantly evolving, we do not provide a change log manually. Instead please see the changes on jenkins for your build.
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Kernel Note: This rom is currently using the stock kernel, so you can find the sources from aosp.
--
Installation Notes:
These builds are designed to be installed from your favorite recovery.
Perform a full wipe (read Factory Reset) prior to installing this over ANY ICS or JB based rom.
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
---
Enabling voice search in google now
Go into Settings
Go to "Language & input"
Scroll down to "Speech" and click on "Voice Search"
Click on "Download offline speech recognition"
Swipe Across to the "ALL" tab if needed
Download your speech pack for your language

Here is what I am aware of that has still to be fixed. I'll add to it once I've went through the bugtracker.
GPS
Face unlock
Audio is a bit too quiet.
HDMI Audio
Touchscreen sometimes stops accepting input. (temp workaround - go into standby and resume and it should come back to life).
Changelog:
Hopefully as of Build #58 the unscheduled reboot issue has been resolved. Freedback appreciated
Wifi regualatory domain changed added.
Full dock support including keyboard layout selector.
Google Search no longer crashes.
Screen now turns off when the lid is closed on the dock.
Smart covers now switch off the screen.
Location is reported correctly via wifi.
Screen no longer rotates when docked.
Credits:
The rest of Team EOS.
AndroidRoot esp. RaYmAn and Bumble-Bee for helping with the device tree in particular with sound. (Also for all the other great work AndroidRoot have done with this device).
aremcee (Ricardo Cerqueira) of Cyanogenmod for fixing the OMX issues. (Camera/YouTube)
Everyone else who provided feedback.

jb nighties!
any functions don't work in this build?
thanks

Jesus Christ they coming one by one. Gonna download and will report any bugs
Sent from my Transformer using xda premium

Running nicely so far. Camera doesn't work though. Not a big deal for me since i never use it lol
also google search does not work

Downloading Right Now, Going to test this an report back ASAP.
BTW FTW Team team EOS, Rayman33 and CM Team to Bring us Jellybean!

Thank you so much!
Eos was my first ICS rom, and it holds a special place in my heart.
Great work guys

Bugs audio is weird on this too.YouTube HD don't work
And netflix only shows a black screen
Sent from my Transformer TF101 using xda premium

Everything works great except FCs in google search bar. After downloading the language pack, google now worked but FCd immediately
Sent from my Desire HD using xda premium

metaldood said:
Everything works great except FCs in google search bar. After downloading the language pack, google now worked but FCd immediately
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Second that, force close on everything using google search

TheUndertaker21 said:
Bugs audio is weird on this too.YouTube HD don't work
And netflix only shows a black screen
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Netflix showing black means an issue with video decoding i believe

Checked camera and YouTube, the same errors me and rayman33 had. Yet in CM10 it works somehow. Need to investigate because I don't see any difference.

K900 said:
Checked camera and YouTube, the same errors me and rayman33 had. Yet in CM10 it works somehow. Need to investigate because I don't see any difference.
Click to expand...
Click to collapse
Yeah cm10, had its own bugs too. Crappy audio some frame rate problem and Google now annoying pop ups lol. But they have netflix and YouTube working.
Sent from my Transformer TF101 using xda premium

TheUndertaker21 said:
Yeah cm10, had its own bugs too. Crappy audio some frame rate problem and Google now annoying pop ups lol. But they have netflix and YouTube working.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Sound is common, and I think I have some ideas about it. Not sure about OMX yet though, don't see any reason why they have it and we don't.

Nice one to all devs :good:
btw i see Google Now works on Team EOS Xoom JB Nightly...so just wait and they will fix it,maybe :fingers-crossed:

asdfzz said:
Nice one to all devs :good:
btw i see Google Now works on Team EOS Xoom JB Nightly...so just wait and they will fix it,maybe :fingers-crossed:
Click to expand...
Click to collapse
I think it needs GPS for some weird reason. When we fix it properly, it should be working.

K900 said:
I think it needs GPS for some weird reason. When we fix it properly, it should be working.
Click to expand...
Click to collapse
yeah a lot of cards use gps

Yup, Camera and HW video decoding aren't working yet, neither is GPS.
Google Now sorta works but when you opt into Google Cards it breaksit. Probably be fixed as mentioned already when GPS is.

Ok i Tried the rom and Plan on sticking with it....its Useable
Google Voice Search Works with out any issues however google Now FCs
The sound can be worked around with Volume Plus Configs
Chrome Works but has some issues
Graphic Performance is increased [More Fps In Dead Trigger with Tegra 3 Fx] almost no lag
Software Decoding works so videos can still be watched till the next nightly fix
Overall UI Performance and consistancy is Phenomenal ! [Just Don't Change the launcher ]
USB Joysticks Work on Games
USB NTFS Drives are Unmountable [PLEASE FIX THIS!!!]
There can be a 100 things more to talk about but to sum it up, the rom is great, just wait for some fixes and updates and thiss rom will be on top of your list!

Roach2010 said:
Yup, Camera and HW video decoding aren't working yet, neither is GPS.
Google Now sorta works but when you opt into Google Cards it breaksit. Probably be fixed as mentioned already when GPS is.
Click to expand...
Click to collapse
I think camera is OMX related too. Any idea what that could be?
alizafar said:
Ok i Tried the rom and Plan on sticking with it....its Useable
Google Voice Search Works with out any issues however google Now FCs
The sound can be worked around with Volume Plus Configs
Chrome Works but has some issues
Graphic Performance is increased [More Fps In Dead Trigger with Tegra 3 Fx] almost no lag
Software Decoding works so videos can still be watched till the next nightly fix
Overall UI Performance and consistancy is Phenomenal ! [Just Don't Change the launcher ]
USB Joysticks Work on Games
USB NTFS Drives are Unmountable [PLEASE FIX THIS!!!]
There can be a 100 things more to talk about but to sum it up, the rom is great, just wait for some fixes and updates and thiss rom will be on top of your list!
Click to expand...
Click to collapse
+1 for NTFS. Your turn Roach

Desire S - Jelly Beans (4.1.1) CM10 Alpha/ Experimental ->Testing

Hello Desire S Enthusiasts,
{Please move this post to the appropriate thread I searched and could not find a thread with Desire S JB testing in the General section. Newbies can not post in the Development section}.
The Development of Android Jelly Bean(s) ROM has progressed a lot and so now we are able to test the great work of:
CyanogenMod Developer Team, nexx, nk111, superkid, and other "Chefs"
Please check this thread in the HTC Desire S > Android Development section
http://forum.xda-developers.com/forumdisplay.php?f=1033http://
I have tested the following ROMs by replacing each ROM after a full wipe:
ROM 1: cm-10-xxxxxxxx-EXPERIMENTAL
ROM 2: PARANOIDANDROID SAGA
ROM 3: BlindBean
ROM 4: Andromadus Test builds - Jelly Bean - CyanogenMod UPDATE 05 Oct 2012
see below, stable and working
Results as below.
ROM 1: cm-10-xxxxxxxx-EXPERIMENTAL
http://forum.xda-developers.com/showthread.php?t=1776256
Update Test
Test 25/07/2012
cm-10-20120724-EXPERIMENTAL-saga-NK111.zip
Microphone in call is working
Camera: App working, however black screen
Bluetooth not working - device not discovered/ device not found
Benchmark test:
Antutu score (no manipulation): 2440
Update Test
Test 24/07/2012
cm-10-20120723-EXPERIMENTAL-saga-NK111.zip
Messaging (SMS app) working
Working as below (previous releases):
Gallery working
Comment: Tasker app working
Microphone working for Google search
Attention: Microphone in call is not working
Bluetooth not working - device not discovered/ device not found
Camera not working - Error: Unfortunately Gallery has stopped
Update Test
Test 20/07/2012
cm-10-20120720-EXPERIMENTAL-saga-NK111.zip
Bluetooth works
Camera works (3rd party app)
Other conditions as below
Issue (solved) with google play does not download (open store, select app, start download, hangs) Any solution? fixed download JB gapps (flash full wipe) , removed google account, recreated google account
Benchmark test:
Antutu score (no manipulation): 2598
______
Here my brief test observation of the cm-10-20120718-EXPERIMENTAL-saga-NK111.zip :
Working:
Battery history
WiFi
GPS
Headset / Headphones
Mobile Data
Mobile Data usage logging
Sensors (Proximity, Light, Compass, Rotation)
Touchscreen
USB Mass Storage
Phone
Not working
Bluetooth (device not be found, could not find BT device)
Camera (not available)
SMS - fix with e.g. Android 4 SMS Messaging from google play store
Not tested
MMS
others
Other remarks:
Install:
Wiped dalvik cache
Recovery install off zip
Full reboot -> working
Benchmark test:
Antutu score (no manipulation): 2428
Apps restore with titanium backup require superuser confirmation at each programme step.
Looking forward to testing the next development release
ROM 2: PARANOIDANDROID SAGA
http://forum.xda-developers.com/showthread.php?t=1672537
Update
Test 28/07/2012
[ROM][27 JULY 2012][JB:CM10:HYBRID] PARANOIDANDROID SAGA v1.9.2a | *Theme engine* by Developer: blindndumb (credits CM10 development team)
Nice new start up animation
Working as below: test dd 20/07/2012
Not working
Camera not working (connection error, eventhough in original thread camera seems to work, this patch is not included in this build)
Bluetooth not working
Benchmark test:
Antutu score (no manipulation): 2411
Update
Test 21/07/2012
[ROM][20 July 12][JELLYBEAN][4.1.1] PARANOIDANDROID v1.8a by Developer: blindndumb (credits CM10 development team)
Most of features are working
Battery history
WiFi
GPS
Headset / Headphones
Mobile Data
Mobile Data usage logging
Sensors (Proximity, Light, Compass, Rotation)
Touchscreen
USB Mass Storage
Phone
...
Not working: camcorder, front cam
Not working bluethooth
Remark: Reboot under load, trying to use front cam leads app and/or desire s freezes, fix: forced reboot
Benchmark test:
Antutu score (no manipulation): 2549
Update Test
Test 25/07/2012
ROM 3: BlindBean
http://forum.xda-developers.com/showthread.php?t=1605896
BlindBean v1 - Preview Edition by blindndumb
Working: Google Voice Search
Comment Apps:
Titanium Backup Window looks pixelated, distroted letters
Titanium Backup requires constant superuser root access confirmation
Not working Microphone in call
Not working: Camera
Not working: Bluetooth (device not be found, could not find BT device)
Benchmark test:
Antutu score (no manipulation): 2663
Update test
30/07/2012
[ROM][29 JULY 2012][JB 4.1.1] BlindBEAN v1.3 - Preview Edition IV | *Camera Working* by Developer: blindndumb (credits CM10 nik111 et al, development team)
http://forum.xda-developers.com/showthread.php?t=1605896
Working:
Camera - rear (when using front - app not found, app crash, until reboot)
Battery history
WiFi
GPS
Headset / Headphones
Mobile Data
Mobile Data usage logging
Sensors (Proximity, Light, Compass, Rotation)
Touchscreen
USB Mass Storage
Phone
Home key back light working
Google Search works well
Not working: Bluetooth - device not discovered/ device not found
Comment: Nice new boot logo/ animation
Benchmark test:
Antutu score (no manipulation): 2667
ROM 4: Andromadus Test builds - Jelly Bean - CyanogenMod
http://forum.xda-developers.com/showthread.php?t=1805450http://
Update
05 Oct 2012
[ROM][04-09-12] Andromadus Test builds - Jelly Bean - CyanogenMod 10[3.x-1] however with flinneycm10_vision_109 (Thanks to flinney - developer
Working: Everything
Bluethooth
Battery history
WiFi
GPS
Headset / Headphones
Mobile Data
Mobile Data usage logging
Sensors (Proximity, Light, Compass, Rotation)
Touchscreen
USB Mass Storage
Phone
Camer (back)
WARNING: Do not try to switch from back to front camera, this will result in Gallery application not working and it can not be fix unless you clean install, i.e. FULL wipe and rebuild!!!
Not working:
Front Camera (green frozen screen -> gallery app stops)
HBOOT-6.98.1002
RADIO-3831.17.00.16_M
So for me it works on:
3.0.43-g609d353-dirty
[email protected] #1
Sound: yes including loudspeaker
BT: yes
GPS: yes
Except front camera
Antutu score (no manipulation): 2803
Update
30/07/2012
The CM10 rom tree has grown with a new branch from developer superkid
[ROM][30-07-12] Andromadus Test builds - Jelly Bean - CyanogenMod 10[3.x-1]
This ROM uses Kernel 3.0.16 with ref to virtousrom
Working:
Bluethooth
Battery history
WiFi
GPS
Headset / Headphones
Mobile Data
Mobile Data usage logging
Sensors (Proximity, Light, Compass, Rotation)
Touchscreen
USB Mass Storage
Phone
Google search: immediately
Not working: camera
Benchmark
Antutu score (no manipulation): 2550

Camera works,but not well enough.I installed lgcamera,went to the settings and changed something(like long press to focus&take photos),and then......It kept rebooting...
It seems that sometimes the ROM will lag at 1Ghz(interactive).I changed the setting to 1.2Ghz(ondemand),and things seems better.
Anyway,great ROM.jellybean tastes nice!

LBE donst work.
And I cant have Germany GSM network, only Dansk.
I did not find it was laggi.

Should I go for jellybean
For now I am on Ics sense 4
I want to try Rom should I go for it or there ate case of bootloop or smthing like that

help
hello!
I use my phone in CM9 nexx last version released since the first moment
Yesterday I tried the version 7.26 cm10.
Full wipe+new JB GAPPS + + is the new fixed camera.
disappeared from the gallery of my photos and videos.
If you restore the CM9-et I open the gallery and have their photos and videos, but about 10 seconds are automatically deleted.
it would be nice if someone would explain what it is and help.
thank you

acultr said:
hello!
I use my phone in CM9 nexx last version released since the first moment
Yesterday I tried the version 7.26 cm10.
Full wipe+new JB GAPPS + + is the new fixed camera.
disappeared from the gallery of my photos and videos.
If you restore the CM9-et I open the gallery and have their photos and videos, but about 10 seconds are automatically deleted.
it would be nice if someone would explain what it is and help.
thank you
Click to expand...
Click to collapse
Testing of experimental software is not intended for the average user. No offence.
Your pictures are not deleted, the media scanner service (that is responsible for showing the files on your SDcard in the Gallery application) has issues and is not finding them. Do not worry and wait a bit for more stable version or use a proven for daily use ROM

amidabuddha said:
Testing of experimental software is not intended for the average user. No offence.
Your pictures are not deleted, the media scanner service (that is responsible for showing the files on your SDcard in the Gallery application) has issues and is not finding them. Do not worry and wait a bit for more stable version or use a proven for daily use ROM
Click to expand...
Click to collapse
okay.
I do understand.
If you restore the CM9 will have their photos, but I open the gallery and will be deleted one by one.
I have 600 photo.
1 sec. később.599
and so on until 0

acultr said:
okay.
I do understand.
If you restore the CM9 will have their photos, but I open the gallery and will be deleted one by one.
I have 600 photo.
1 sec. később.599
and so on until 0
Click to expand...
Click to collapse
Check with ES File Explorer or another are your files still on the SDcard (the restored in Gallery are thumbnails). Look for a folder called DCIM and look inside. If there are no photos then some accident happened there...

amidabuddha said:
Check with ES File Explorer or another are your files still on the SDcard (the restored in Gallery are thumbnails). Look for a folder called DCIM and look inside. If there are no photos then some accident happened there...
Click to expand...
Click to collapse
This was the first step.
empty.
---------- Post added at 02:02 PM ---------- Previous post was at 01:31 PM ----------
acultr said:
This was the first step.
empty.
Click to expand...
Click to collapse
I can not recover with titanium

Been using it for three days now, and I really like it. It's fast and (surprisingly) the battery life is even better than under CM9. Not sure why other users have such a drain.

acultr said:
This was the first step.
empty.
Click to expand...
Click to collapse
Sorry then. IFAIK there are not much possibilities a file or folder to delete itself without the awareness of the user...
Anyway do not copy anything to the SDcard, remove it from the device, put it in your PC and start searching in Google for a Restore/Undelete software. This will be the only way to restore your files. /Or if by any not much possible case you have deleted the files from Linux, while in USB mount mode there should be a hidden .Trash-001 folder there...but I doubt it/

amidabuddha said:
Sorry then. IFAIK there are not much possibilities a file or folder to delete itself without the awareness of the user...
Anyway do not copy anything to the SDcard, remove it from the device, put it in your PC and start searching in Google for a Restore/Undelete software. This will be the only way to restore your files. /Or if by any not much possible case you have deleted the files from Linux, while in USB mount mode there should be a hidden .Trash-001 folder there...but I doubt it/
Click to expand...
Click to collapse
Thanks for your help.
it's all interesting.
this has never happened to me
I've used four different alpha.

Suggestion
Hi I'm following too the experimental ROM on JB...
Thanks for have a post where anyone (like me) can write..
I've just a suggestion; can you make the first post more readble. I mean you can use things like
Code:
ROM 1 - Release of 31-07
WORKING
-
-
-
NOT WORKING
-
-
and so on for the 3-4 ROM already present.
I repeat myself, it's just a suggestion
It will make more easy understand the differences and update status...
But as I said.. Thank you!!

[ROM][UNOFFICIAL] CyanogenMod 11 [Android 4.4.4]

CyanogenMod 11 (based on Android 4.4.4 "KitKat") for the HTC Liberty/Aria/Gratia/etc
NOTE: Just to make this clear, this is UNOFFICIAL, and NOT supported by CyanogenMod.
Hboot 1.02 or higher is required! (Revolutionary or HTCdev unlock)
Liberty is now an official device on the androidarmv6 project
This means updates will show up in Settings > About phone > CyanogenMod updates
However updating via the updater may not always work, due to very constrained system space.
Patches can be submitted to http://review.androidarmv6.org/
Huge thanks to everyone working on marvel/Wildfire S (Olivier, izi501, feroxx, Kevinjoa, thehacka1, benjamingwynn, JDevs, more I don't know?) & the androidarmv6 team
The kernel includes TONS of CPU governers, and a couple extra I/O schedulers.
I don't really care for kernels with this many CPU governers, but the rest of the changes to the kernel are useful, and it's more work taking them back out so I left them in
No idea what may or may not be better, but the default seems to work fine.
Screenshots: http://winsuk.net/screens/liberty/cm11/
Required recovery: http://forum.xda-developers.com/showthread.php?t=2474662
Known bugs/etc:
Slow - everywhere (I recommend CM9 or CM10)
Apps sometimes don't load on boot (appear to be completely gone) - even system apps
WiFi hotspot doesn't work
Screen brightness sometimes sticks at dim when turning on
Transparent GIFs in browser have a solid background
Large images in browser are usually broken
No adb screenrecord
No ART
Notes:
USB tethering: enable it, unplug & replug, then enable it again and it should work
For a transparent status bar, enable high-end graphics in Performance settings
USB debugging verify (the popup when you plug into a new PC) doesn't always work, so it has been disabled
Gesture typing, Photosphere, and voice recognition: all require closed-source libraries from Google built for ARMv6, which don't exist.
I can't make any of these work unless Google does.
Downloads!
Newest builds from the androidarmv6 buildbot can be found here:
http://download.androidarmv6.org/_builds/liberty/
Mirrors for stable build RC11:
cm-11.0.0-RC11-liberty.zip - d94c7e2163ce434241bfc0ee02c84eb1
androidarmv6: http://download.androidarmv6.org/_builds/liberty/stable/cm-11.0.0-RC11-liberty.zip
Google Drive: http://goo.gl/D635Gc
xda devdb: http://forum.xda-developers.com/devdb/project/dl/?id=9311
MediaFire: https://www.mediafire.com/?kf3it5ckd46mf3o
Google Apps: http://forum.xda-developers.com/showthread.php?t=2756379
Google Search cannot be installed from the Play Store, however if you can get an apk for it (like here maybe), it will work (sans voice) with one setting change:
1. install Google Search app (from apk)
2. open it, and hit Yes, I'm in
3. let it crash
4. open Google Settings from the app drawer
5. navigate to Search & Now > Voice > "Ok Google" hotword detection
6. slide hotword detection to off
7. done, it works
There is also an app to sort-of enable voice search in Google Search/Now: http://forum.xda-developers.com/showthread.php?t=2709285
Source:
Manifest with full ROM & kernel source
Kernel source only
Previous builds can be found here or here or here
Changelog of builds:
20140614 (June 14th, 2014):
First build from androidarmv6 jenkins
CM Updater added (should be getting weekly builds from jenkins through it soon)
Miscellaneous changes from CM and/or androidarmv6
20140607 (June 7th, 2014):
Android 4.4.3
Disabled fading edges on text for a small speedup - before, after
Switched to gps.conf with SUPL (assisted GPS) support - I can't tell a difference, but it may speed up GPS for some
Terminal Emulator updated
Upstream CM things (I don't keep track )
20140519 (May 19th, 2014):
Re-added missing fonts for various languages (they got removed during the KK bringup)
Removed what livewallpapers were left - this will not only free up some space on /system, but also /data because they had to be cached there
Removed CM Wallpapers to free up /system space (as with the live wallpapers, should free up a little on /data as well)
Removed 05mountsd script - most sd-ext solutions seem to have mounting built in now, and it conflicts with some
SELinux enabled in kernel - this may improve battery life as audit was constantly crashing without SELinux
Changes from CM (including new theme engine, oooh!)
20140507 (May 7th, 2014):
Got camera working (all of it including timelapse no glitches either)
Added some extra encoder/decoder files - not sure if they are doing anything right now
Latest changes from CM (whatever that may be)
20140503 (May 3rd, 2014):
Fixed hardware video decoder (& encoder)
Fixed GPS
20140501 (May 1st, 2014):
Baseline build
XDA:DevDB Information
Unofficial CyanogenMod 11, ROM for the HTC Aria
Contributors
WinSuk, Olivier, izi501, feroxx, Kevinjoa, thehacka1, benjamingwynn, JDevs, androidarmv6 team, more I don't know?
Source Code: https://github.com/androidarmv6/android/tree/cm-11.0
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 2.6.x
ROM Firmware Required: hboot 1.02 (Revolutionary or HTCdev unlock)
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20140614
Beta Release Date: 2014-06-14
Created 2014-05-01
Last Updated 2014-12-04

The camera has the opportunity to fix?

fmshe said:
The camera has the opportunity to fix?
Click to expand...
Click to collapse
Maybe... Our camera blob (from gingerbread) is extremely outdated, and something it relies on was removed in 4.4.

New build uploaded:
20140503 (May 3rd, 2014):
Fixed hardware video decoder (& encoder?)
Fixed GPS
http://goo.gl/c6Kekq
c298645ed377de26a6c3a833b7b70fc0
xda devdb mirror: http://forum.xda-developers.com/devdb/project/dl/?id=5948
MediaFire mirror: https://www.mediafire.com/?ld5pld43a3x2pr9
I've now tested Google Apps and everything seems to work fine, so I changed the OP to only have one link for them (what I would recommend using)
But the Play Store won't let you install Google Search (aka Google Now)

Awesome! Hoping you could get the camera working. This is quite exciting.
Sent from my Nexus 7 using Tapatalk 2

No way this is happening I gave this phone to my mom and she is not the biggest tech enthusiast but there are some things that just don't work with GB. You once again breath new life into this device. Thank you!
Sent from my Nexus 7 using Tapatalk

New build, snap snap
(sorry, hard to make "new build" original every time )
20140507 (May 7th, 2014):
Got camera working (all of it including timelapse no glitches either)
Added some extra encoder/decoder files - not sure if they are doing anything right now
Latest changes from CM (whatever that may be)
http://goo.gl/4YeJLa
e6c97b311bc3a32e1a17f0c199821f0b
xda devdb mirror: http://forum.xda-developers.com/devdb/project/dl/?id=6027
MediaFire mirror: https://www.mediafire.com/?f8tulxczubrzfcx
If you are updating from a previous build and the camera app doesn't appear, run this from terminal emulator or adb shell:
Code:
su
pm enable com.android.camera2/com.android.camera.CameraLauncher

Hey WinSuk, I know these are annoying questions, but Google Now is basically the only thing missing that's keeping me from installing this on my mom's phone. I understood your explanation about voice recognition and Google's libraries and am now wondering if that's the same reason Google Now isn't working. Do you think it will ever be possible to install Google Now? Thanks so much!
Sent from my Nexus 7 using Tapatalk

Cosmo123 said:
Hey WinSuk, I know these are annoying questions, but Google Now is basically the only thing missing that's keeping me from installing this on my mom's phone. I understood your explanation about voice recognition and Google's libraries and am now wondering if that's the same reason Google Now isn't working. Do you think it will ever be possible to install Google Now? Thanks so much!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I don't think it's possible because we don't have an arm v7 soc. The Aria is a v6, which is very old and most likely will never get updated. Though, Google now somewhat worked on the Aria when I was running CM9 (only contextual info). No voice features though.
You can try use the app Utter, which is similar to Google now in that it controls your phone via voice. I'm not sure if it works on our Arias.
Sent from my Nexus 7 using Tapatalk 2

kura808 said:
I don't think it's possible because we don't have an arm v7 soc. The Aria is a v6, which is very old and most likely will never get updated. Though, Google now somewhat worked on the Aria when I was running CM9 (only contextual info). No voice features though.
You can try use the app Utter, which is similar to Google now in that it controls your phone via voice. I'm not sure if it works on our Arias.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I didn't mean the voice functions of Google Now, just the app itself. So basically Google Search, Google Now cards and notifications.

Cosmo123 said:
Hey WinSuk, I know these are annoying questions, but Google Now is basically the only thing missing that's keeping me from installing this on my mom's phone. I understood your explanation about voice recognition and Google's libraries and am now wondering if that's the same reason Google Now isn't working. Do you think it will ever be possible to install Google Now? Thanks so much!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Just tried the newest Search app, and it works fine after you disable hotword detection : O
1. install Google Search app (I don't really want to distribute an apk myself, so here is a trustworthy source)
2. open it, and hit Yes, I'm in
3. let it crash
4. open Google Settings from the app drawer
5. navigate to Search & Now > Voice > "Ok Google" hotword detection
6. slide hotword detection to off
7. done, it works
I think ima add this to the OP...

Just installed your ROM and it runs great!! Such a difference coming from your cm9 build. Quite impressed.
I was wondering if s2ext will work with this ROM? I understand kitkat broke the SD card support but our rom storage is quite small. I was only able to install a few apps before hitting the limited memory alert Lol. Are there any work arounds? =)
Sent from my Nexus 7 using Tapatalk 2

kura808 said:
Just installed your ROM and it runs great!! Such a difference coming from your cm9 build. Quite impressed.
I was wondering if s2ext will work with this ROM? I understand kitkat broke the SD card support but our rom storage is quite small. I was only able to install a few apps before hitting the limited memory alert Lol. Are there any work arounds? =)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
What do you think about symlinking the whole data partition to the SD card? Just an idea.
Could you do me a favor and take a few screenshots of the used storage and ram? Would also be interesting to know how much of the system partition is used/free. Thanks again
Sent from my Nexus 5 using Tapatalk

Cosmo123 said:
What do you think about symlinking the whole data partition to the SD card? Just an idea.
Could you do me a favor and take a few screenshots of the used storage and ram? Would also be interesting to know how much of the system partition is used/free. Thanks again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry but I don't know how to symlink it lol. Is that like how when we used to use darktremors a2sd mod?
So after installing 7 apps, I only got about 18mb of rom left lol. The amount of free ram is quite good though.
Sent from my LT30p using Tapatalk 2

kura808 said:
Just installed your ROM and it runs great!! Such a difference coming from your cm9 build. Quite impressed.
I was wondering if s2ext will work with this ROM? I understand kitkat broke the SD card support but our rom storage is quite small. I was only able to install a few apps before hitting the limited memory alert Lol. Are there any work arounds? =)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
What app are you using?
I tried Link2SD, but it doesn't like the /sd-ext mount point... can be fixed by deleting /system/etc/init.d/05mountsd and rebooting.

Status bar loses transparency

fmshe said:
Status bar loses transparency
Click to expand...
Click to collapse
Read the first post?
WinSuk said:
Notes:
For a transparent status bar, enable high-end graphics in Performance settings
Click to expand...
Click to collapse

WinSuk said:
Read the first post?
Click to expand...
Click to collapse
thank you

The storage space is the most difficult part on this device right now...
Missing fonts for languages have been added, but even after stripping out the live wallpapers, it (and a few other changes) leaves just under 13MB free on /system... Google Apps takes up 26MB.
I'll be taking CMWallpapers out before the next release, but at 9.3MB - that isn't quite enough...
The newest recovery (6.0.4.8) also won't fit without stripping out everything that isn't needed (images, comments & linebreaks in files, etc).
We may have to start using custom partition sizes soon...
Another option is symlinking Google Apps to the /cache partition (40MB, mostly unused), like the gapps package I linked for 4.3

WinSuk said:
Another option is symlinking Google Apps to the /cache partition (40MB, mostly unused), like the gapps package I linked for 4.3
Click to expand...
Click to collapse
Are there any downsides to this? Isn't the cache partition just as fast etc?
Do you think your ROM is already usable as a daily driver? As I said I don't own the phone anymore and can only rely on the community before I install it for my mom.
Do you think ART will ever work? I think this phone would benefit from it greatly. Thanks
Sent from my Nexus 5 using Tapatalk

[8.1.x][OFFICIAL][RELEASE] CarbonROM | cr-6.1 [z3c]

{
"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