ANXCamera - Miui Camera Port
Port for AOSP-Based Pie ROMs on Xiaomi's Devices
Instructions for Use:
Download the Zip from MOD EDIT: dl link removed
Supported Devices
oosberyllium is Poco F1 with OOS
singularity is all below devices, One for all, Plus Ultra, AOSP+MIUI
beryllium is poco
dipper is mi8
polaris is mix2s
perseus is mix3
cepheus is mi9
lavender is rn7
violet is rn7p
whyred is rn5/p
equuleus is mi8p
raphael is k20p
platina is mi8l
tulip is rn6p
gemini is mi5
grus is mi9se
sirius is mi8se
davinci is mi9t/k20
pyxis is cc9
laurus is cc9e
cactus cereus laurel_sprout lotus nitrogen onc riva rosy tiare ursa chiron jason mido sagit sakura vince wayne <-- Needs devs and testers
Install the Zip via Magisk if you have it, Install via TWRP only if you don't have Magisk
Install the Appropriate Addon (Required for most phones)
Keep a note of the release you will be using, for issue discussion etc.
Start Using
Uninstall via Magisk, or flash same again in TWRP to uninstall
IMPORTANT NOTE
There are currently two DEVs making build me and Luffitys.
AEonAX - Owns a POCO, Makes builds with Lots of features and Bugs
Luffitys - Owns a MI8, Makes Debloated Version, with Lots of features removed and Less bugs due to feature removal. He is not on XDA
Choose a version as per your liking, try both.
ChangeLogs
v160: AOSP
Highly Experimental Version, Has Bugs, Re-Ported from Tucana, Added VLOG, SuperEIS, SuperNight, GoogleLens + More
If you can't tolerate or don't know the bypass, Use V158
v158: AOSP
Add Andromeda, Enable Focus Peaking for Violet, ANXBattle-ized
v156: AOSP
Updated Device Features XML
INTL Watermarks for Davinci and Raphael thanks to @nckmml
Fix Violet Thanks to @Dyneteve
Added Ginkgo, Begonia, Begoniain
Added Daisy_Sprout and Jasmine_Sprout
v152 :AOSP
Fixed Manifest for Q, Added Back Bootlooping Permissions
v151: AOSP
Add Q Support (Use DocumentMode)
Revert V29Utils,
Add support for YSL,
Kill ParallelProcess Support
No PocoLibs By Default
v148: AOSP
Remove Studio Lighting for Lavender
Add 240fps to Violet, Lavender and Whyred
v146: AOSP
Removed TikTok infection from ShortVideo, Fix WideSelfie.
DIsabled ParallelProcessing, Fixed Watermark Implementation
v145: AOSP
Add tissot, fix panorama crash
v141: AOSP
Rebase on MiuiCamera from MIUI Q on Raphael 9.9.3
Raw Support
Mimoji now separate Addon @FIX_mimoji
Portrait Fixed for Cepheus, Raphael, DaVinci, Violet and Maybe Lavender. use #fix_custlibs
Featureset for Beryllium:
960fps Works
240fps Works, use Gphotos
Photo Works
Square Works
Panorama Works
Manual Mode Works
Portrait Mode
4k30 eis
Dynamic Shots
Studio Lighting
Mimoji
AntiFeatureset:
Portrait Mode (works for some)
120fps
Night Mode (works for some)
AI Mode (works for me)
960FPS doesn't record in left Landscape, try right landscape
POCO Q, Wait for Official Miui Q, Or use PA Q, ANX works on it.
Donate @ https://www.paypal.me/XEonAX
Special Thanks to @CodeElixir for his work with lib modding and fixes shutter button bug
LogCat are required to help, Solutions will also be very much appreciated.
All those who followed/starred/forked https://github.com/XEonAX/ANXMiuiCamera10 or https://github.com/XEonAX/ANXCamera10 make sure to change to https://github.com/XEonAX/ANXCamera
This is a leaner repository
MOD EDIT: Telegram link removed, please read the STICKY!
People asking about EIS:
It is only available at 30fps, please don't ask about 1k60fps or 4k60fps, currently it won't be possible.
People asking about the Bug Fixes:
If you have the fix please tell me, as I don't
Currently known issues and their workarounds, if any are available here
https://github.com/XEonAX/ANXCamera10/issues
Please do check there before reporting anything.
There is an abandoned alpha release for Oreo at https://github.com/XEonAX/ANXMiuiCamera9/tree/master/out
If anyone interested to bring it to working condition please contact me.
To Learn How to Port MiuiCamera join this MOD EDIT: LINK REMOVED
and watch this porting videos recorded livestream at https://mega.nz/#F!sGx0US5B!hXy30KunCOjmVmZ7kUMW3g
or https://www.youtube.com/playlist?list=PLKwynvsh3Ed3zMZHwJCiaP8n-gHzhXUCA
XDA:DevDB Information
ANXCamera, Device Specific App for the Xiaomi Poco F1
Contributors
AEonAX, CodeElixir, amog787, abhishek987, mustang_ssc, psygarden
Source Code: https://github.com/XEonAX/ANXCamera
Version Information
Status: Stable
Beta Release Date: 2018-12-23
Created 2018-12-15
Last Updated 2020-02-16
Edit :
Join Telegram for better support and updates.!
Bro I have the same problem
psygarden said:
Great initiative.
Are you on Telegram? Will be easy to interact there.
Also the cam version for Pie ie MIUI10 gives error. Says its developed for an older version of android. I'm on Pie as of now.
Thanks.
Click to expand...
Click to collapse
I am also getting the same error but it continues once you dismiss that. Please note this version does not work. It is in pre-alpha condition
I will create a new group on telegram, give me you username
AEonAX said:
I am also getting the same error but it continues once you dismiss that. Please note this version does not work. It is in pre-alpha condition
I will create a new group on telegram, give me you username
Click to expand...
Click to collapse
Same as xda. @psygarden
AEonAX said:
MOD EDIT: quote removed
Click to expand...
Click to collapse
Congrats for getting working mod on oreo & good to see you still trying to keep this project alive. I know it's not easy keep it up !
I've downloaded the apk file but I'm unable to download the etc folder... Can you plz upload the folder here on xda?
Sent from my Poco F1 using XDA Labs
Glad to know that porting development is going on. Btw getting this on opening the app.
Sent from my Poco F1 using XDA Labs
Ooo, this is awesome, thank you for working on this! I'm on LOS 16 so I cant really do any testing yet. Still though, keep up the good work
Atleast found someone who is trying to make this port. Thanks a lot man.
I hope you port it successfully, keep up the great work! The MIUI Camera was pretty decent.
I have a lot of hope for this great work man I'll test it on Pie when I have time.
donk165 said:
Ooo, this is awesome, thank you for working on this! I'm on LOS 16 so I cant really do any testing yet. Still though, keep up the good work
Click to expand...
Click to collapse
+1
thank-you for porting. now i can flash my favourite custom rom and use mi ui camera ?
Sharfuddin Ahmed said:
I've downloaded the apk file but I'm unable to download the etc folder... Can you plz upload the folder here on xda?
Sent from my Poco F1 using XDA Labs
Click to expand...
Click to collapse
Beryllium.xml attached to first reserved post of this thread. Create the path manually.
Anybody knows how to solve?
Code:
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: ShaderNativeUtil load CameraEffectJNI.so failed.
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: java.lang.UnsatisfiedLinkError: dlopen failed: library "[email protected]" not found
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at java.lang.Runtime.loadLibrary0(Runtime.java:1016)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at java.lang.System.loadLibrary(System.java:1669)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at com.android.camera.effect.ShaderNativeUtil.<clinit>(ShaderNativeUtil.java:14)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at com.android.camera.effect.ShaderNativeUtil.initTexture(ShaderNativeUtil.java:25)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at com.android.camera.effect.renders.SnapshotEffectRender$EGLHandler.applyEffect(SnapshotEffectRender.java:542)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at com.android.camera.effect.renders.SnapshotEffectRender$EGLHandler.drawMainJpeg(SnapshotEffectRender.java:692)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at com.android.camera.effect.renders.SnapshotEffectRender$EGLHandler.handleMessage(SnapshotEffectRender.java:401)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at android.os.Handler.dispatchMessage(Handler.java:106)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at android.os.Looper.loop(Looper.java:193)
12-17 22:43:03.784 29901 30015 E CAM_ShaderNativeUtil: at android.os.HandlerThread.run(HandlerThread.java:65)
12-17 22:43:03.785 29901 30015 E .android.camer: No implementation found for int[] com.android.camera.effect.ShaderNativeUtil.initJpegTexture(byte[], int, int) (tried Java_com_android_camera_effect_ShaderNativeUtil_initJpegTexture and Java_com_android_camera_effect_ShaderNativeUtil_initJpegTexture___3BII)
I have added [email protected] to lib\arm64-v8a of apk
Can anyone provide steps to install miui camera?
hi @AEonAX
I'm a dipper user and really want to have MIUI Camera on AOSP. I tried install your apk however it said this application is intended for older android version.
I attach the logcat
rizahakam said:
hi @AEonAX
I'm a dipper user and really want to have MIUI Camera on AOSP. I tried install your apk however it said this application is intended for older android version.
I attach the logcat
Click to expand...
Click to collapse
You need to give "Usage Access" permission. Read the first post for instructions.
Also you will have to procure your device's specific dipper.xml. Maybe you will have to rename it to beryllium.xml. I don't know, I didn't plan to support other devices.
AEonAX said:
You need to give "Usage Access" permission. Read the first post for instructions.
Also you will have to procure your device's specific dipper.xml. Maybe you will have to rename it to beryllium.xml. I don't know, I didn't plan to support other devices.
Click to expand...
Click to collapse
ok I give Usage Access and now the camera is open.
how to get dipper.xml? can I get it from MIUI rom?
Related
So FIXED on CM based Nougat roms: only change the media.msm8956hw=1 to 0 in the build prop.
Tested with Lineage, Xenon, NitrogenOS. I think when it's enabled the VR playing quality wrong.
This method wont working on MIUI, because 0 is the default value.
How to fix on MIUI 9.5: post
Hi members! Redmi Note 3 Pro QA
So a simple question and remark. I'm using Var's VR Video Player. This is one of the best optimized player at the moment for all VR formats. Tested a lot of players, the quality as the same with others, so the next problem is not an app problem.
VR video quality is very good in the older MIUI v7.1.x.x and 7.2.x.x roms (not tested all MIUI roms) and Krexus (build 3) rom.
Tried on other roms (I think in all roms), and the quality is not as good, not as sharp the picture. Blurred the edges and the lines not as sharp. All other roms, new MIUI's, all CM base and AOSP roms this happening. Tried to change some encoding options in the build.prop, like in Krexus rom, but not helped.
In Krexus the quality looks like when we disabling hardware encoding in the player app in the newest CM roms. Very good picture, looks like in PC. (but on this rom the hw encoding working).
Yesterday tried the lastest MIUI 8 MM rom, the quality as in other CM-s, but the seeking (stepping?) is very fast, at the moment playing. Not buffering 3-4 sec and not stopped the playing like in other CM and AOSP based roms.
I contact with the Var's player devs and finally we came to the conclusion, it's a rom bug.
Anyone experienced this? Or if playing VR anyone could to check Krexus rom? I don't think it's a simple value problem in some files in the rom, maybe a codecs problem?
So the 2 problem what need to eliminating:
- Hardware decoding quality improve, like in the Krexus rom
- Seeking improvement, like in the lastest MIUI 8 MM dev rom.
If I don't know about this quality problem I would not even notice, but always when trying in new roms I'm goes back to Krexus.
I'm not a dev, so only the testing, and this is in above, what I could to do. If you have an idea and it's not comlicated I'm trying, testing the metode in newer CM rom if this will help a bit.
UPDATE:
Made a screenshot on the systems (check the hills and the licence plate on the car):
Left: CM13 / Right: Krexus old
[url=https://postimg.org/image/o0byvant9/]
[/URL]
Logcat
Yesterday I checked 9+ roms.
Working this Krexus (the oldest build 3, in the new similar the problem). TheStrix CM14 build and a really old MIUI rom.
Not working: All CM13 and AOSP builds and similar modded roms, like Resurrection, Slim, Nexus Exp, Qualcomm AOSP, Exodus, Santhosh CM, Orion, DU, Temasek, iZi etc. On iZi the gyro not working in the app.
Any solution devs? Thanks.
Rom's which working good for VR, sharp image etc.
[ROM][CAF][23/10] halogenOS 7 for Redmi Note 3 [0.5-beta] - used the 0.5 beta release
[30/10/2016]CyanogenMod 14.0/14.1 for Xiaomi Redmi Note 3 - used the 30/10/2016 release
[ROM][LAYERS][KENZO] Krexus-CAF 6.0.1 (MMB29M) used the build3 (20160626) release
[CAF][1/16] [UNOFFICIAL] [halogenOS 7.0] [Kenzo] [VOLTE] by @rocknegi (first release - 2017/01/15)
On Androiddevs @Santhosh M ALL RR Nougat release (latest: 2017/01/17) !!
I didn't notice any difference from MIUI 7.x.x.x to 8.x.x.x to CM13 to CM14.
I think it's your brain making you to think that it's blurred, I had this exact problem with my brain when I first tried VR on my Redmi Note 3. I currently have ANT VR (which comes bundled with Lenovo K4 Note but I bought it seperately) and have no problems with it.
superboy123 said:
I didn't notice any difference from MIUI 7.x.x.x to 8.x.x.x to CM13 to CM14.
I think it's your brain making you to think that it's blurred, I had this exact problem with my brain when I first tried VR on my Redmi Note 3. I currently have ANT VR (which comes bundled with Lenovo K4 Note but I bought it seperately) and have no problems with it.
Click to expand...
Click to collapse
Only some older MIUI builds working good with this higher quality. That's why I tested the roms. On the picture is visible the difference (two system, cropped and merged the two screenshot) and from now it's not a brain trick. I'm using VR more than one year, making and editing videos, so have a difference with that.
If check the original channel VR official videos, on SBS 180 and SOS 180 videos have this issue with HEVC, but also see the differences on H264 . If only check youtube and simple 360 video the quality is very similar. So it's a codec problem I think. Btw thanks if you could help with the logs, which cause this affects thanks again
I will compare old MIUI and latest CM13 by flashing them and will tell you the results as soon as possible!
Looking more into this, keep this update cause i just bough xiami VR, and i'm interested to know wich rom is better etc, Using umang unofficial cm13
superboy123 said:
I will compare old MIUI and latest CM13 by flashing them and will tell you the results as soon as possible!
Click to expand...
Click to collapse
I suggest compare with Krexus build 3, as the same, older base.
Yes, I feel huge difference between krexus build 3 and CM13. looks like gpu does not render vr graphic well.
Hey @Steve1207, this is some great debugging, and much more that I'd be able to do to help you, kudos. I have no idea, right now, what could be the culprit. I noticed though that you found the some problem in a newer Krexus-CAF build VS an older one? If this is the case, we could go through the changes in my repos and find out what broke it.
So, the logcats of the working vs the non-working krexus-caf might be helpful, and the changelogs (/system/etc/changelog.txt) of the two ROMs.
KreAch3R said:
Hey @Steve1207, this is some great debugging, and much more that I'd be able to do to help you, kudos. I have no idea, right now, what could be the culprit. I noticed though that you found the some problem in a newer Krexus-CAF build VS an older one? If this is the case, we could go through the changes in my repos and find out what broke it.
So, the logcats of the working vs the non-working krexus-caf might be helpful, and the changelogs (/system/etc/changelog.txt) of the two ROMs.
Click to expand...
Click to collapse
Hello @KreAch3R, I upload the changelogs and the logcat about the last builded krexus (renamed the files for the easier recognition). Hope you found what couse this problem. Thank your help!
Steve1207 said:
Hello @KreAch3R, I upload the changelogs and the logcat about the last builded krexus (renamed the files for the easier recognition). Hope you found what couse this problem. Thank your help!
Click to expand...
Click to collapse
I took a look at the logcats. What I found was, that both cm13 and krexus-wrong build (the ones that don't work) use this driver:
10-09 15:57:32.843 I/Adreno (1223): QUALCOMM build : 2d489f5, I74772a33ad
10-09 15:57:32.843 I/Adreno (1223): Build Date : 08/04/16
10-09 15:57:32.843 I/Adreno (1223): OpenGL ES Shader Compiler Version: XE031.07.00.00
10-09 15:57:32.843 I/Adreno (1223): Local Branch : mybranch21158950
10-09 15:57:32.843 I/Adreno (1223): Remote Branch : quic/LA.BR.1.3.4_rb1.17
10-09 15:57:32.843 I/Adreno (1223): Remote Branch : NONE
10-09 15:57:32.843 I/Adreno (1223): Reconstruct Branch : NOTHING
Click to expand...
Click to collapse
While the only working krexus build uses this driver:
10-09 15:48:34.033 I/Adreno (9424): QUALCOMM build : 4ad80b1, Ibc10b8cc61
10-09 15:48:34.033 I/Adreno (9424): Build Date : 04/14/16
10-09 15:48:34.033 I/Adreno (9424): OpenGL ES Shader Compiler Version: XE031.06.00.02
10-09 15:48:34.033 I/Adreno (9424): Local Branch : mybranch19231206
10-09 15:48:34.033 I/Adreno (9424): Remote Branch : quic/LA.BR.1.3.3_rb2.15
10-09 15:48:34.033 I/Adreno (9424): Remote Branch : NONE
10-09 15:48:34.033 I/Adreno (9424): Reconstruct Branch : NOTHING
Click to expand...
Click to collapse
The changelog seems to agree with me, as you the dates make me assume that this commit is included in the broken build.
So maybe, what you can do is, try to grab all adreno libs from the working krexus, put them into another ROM and see if they work
I gave up for today. Made a flashable pack with the old libs, but dosn't work or when booting with other rom don't change the quality. But I'm trying again tomorrow, now search and read about this libs. Thanks your help @KreAch3R, I think helped a lot for the Kenzo developers with this, maybe someone fix this!
I just stopped using VR!
After trying MIUI and Krexus, CM's VR quality is so bad that I refuse to use VR glass.
UP
Hey all! Any news on this? I'm on miui 8 and was thinking about moving to cm based but now you guys are changing my mind.. I dont wanna lose vr for this, even though I dislike miui. Well, lets hope someone fix it. What about asking in their specific rom thread?
What about that krexus version that has good quality? Does it has any bug? Its safe for daily use?
Vr is not that popular so almost no one cares about development. Lets hope draydream changes that!
Steve1207 said:
UP
Click to expand...
Click to collapse
Hey bro does it fixed by that old adreno blobs? im in Miui 8 MM global beta does Miui 8 MM have also quality issues???
Not any news guys. I'll test the CM14 builds today, now looks like it's pretty stable as I read the threads.
Nice! Please report back to us any news. I moved to RR cm13 rom yesterday and did a little testing with my vr box 2, I actualy saw some improvement, in Miui 8 there was a lot of distortion, it's gone now, the quality still not good, haven't tested with old miui to tell the difference. What I noted is that performance is not that good in games anymore, there was some problems with fps, do you guys know what caused that ? I'm on raidon 3.9 kernel, default settings.
In case the problem for you guys is related to what looks like the two screens being misaligned, I might have a fix. I had the same, and read somewhere to try setting up the phone using qr codes for different viewers through the google cardboard app. It worked for me with a setup by someone called José Francisco. I will try to find the same page again, but for now, just try different setups.
EDIT: It seems that youtube and browser do not work for me. The google web asks me to fill in PPI because it can't detect it. could it be some apps are not able to detect the PPI?
V-incent said:
In case the problem for you guys is related to what looks like the two screens being misaligned, I might have a fix. I had the same, and read somewhere to try setting up the phone using qr codes for different viewers through the google cardboard app. It worked for me with a setup by someone called José Francisco. I will try to find the same page again, but for now, just try different setups.
EDIT: It seems that youtube and browser do not work for me. The google web asks me to fill in PPI because it can't detect it. could it be some apps are not able to detect the PPI?
Click to expand...
Click to collapse
Yep, I was having a bad experience in miui and a terrible one in cm, but I just figured some way to improve, those chinese vrs are a pain, there is no documentation, the solution is to create your own QR Code. It's actualy pretty simple, here is the link https://vr.google.com/cardboard/viewerprofilegenerator/
Send the link through a qr viewer or copy the address into the phone, now your pc and phone are connected, put ur phone in vr and test those configurations. That fixed most problems for me today.
PS: google web ou mention is the qr generator ? It always ask for ppi. There was one qr that I tried one time that bugged my youtube too in VR. Best option isto create your own.
[9.0.0_r50/v121] download : https://androidfilehost.com/?a=show&w=files&flid=286761"Regular" #phhusson AOSP 9.0 vanilla build with microG patches, #ale5000 implementation and multiple foss apps:
(/system partition requires: [arm64:>1.6Gb] [arm32:>1Gb] minimum)
microG: GmsCore19.9.99.mapbox*² GoogleServicesFramework* DroidGuard*
addons: NominatimGeocoderBackend DejaVuBackend IchnaeaNlpBackend LocalWifiNlpBackend openbmapRadiocellsOrg LocalGsmNlpBackend
hot-built: emailExchange2 snapMusic Terminal screenRecorder testDevCamera browserQuarks
prebuilt: Fdroid F-DroidPrivilegedExtension ZxingClient kDI
system/bin* : aapt32 curl32 grep64(pcre2grep version 10.22 2016-07-29)
Also included are these non-foss 3 Google : Playstore, Calendar/Contact_Sync; they can be fully disabled, if not needed, via Settings/Apps, and re-activated back (with or without previous valid Google account registration) . To match Magisk ctsProfile:true (Playstore certified) check https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 to restore vendor original build.fingerprintwip
Click to expand...
Click to collapse
not included: Latest compatible Google Maps 9.84.2 optional https://androidfilehost.com/?fid=11410963190603886579
Nota : android Webview v76 (spoofing an Oreo 74/SamsungS9) is signed & upgradable from Bromite, Terminal is activated via Settings/System/Advanced/DeveloperOptions and Playstore has to be ForceStop-ed once after registration/wizard, and relaunch. F-Droid V.102.3 auto-update needs FDroid/Settings/ExpertMode/Privileged disabled.
After first rom flash and MicroG prim-initialization, for immediate working location, toggle /Settings /Security&Location /Location off&on. Switching between vtm & mapbox can need wipe for apk cache & account re-creation.
*) home-built with targetSDK 28 and manifest/multiArch
*²) GmsCore is anticipated to v19.9.99(PlayServices variants): can be upgraded with all attached gmscore__.apk
All other included prebuilts are fdroid signed editions.
donations: Consider prim-origin @phhusson @MaR-V-iN @csagan5(Bromite)
others : @ale5000 @Setialpha #ThibG(DroidGuard)
+info for microG implementation https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
If you need more, please let me know about it, but for more "Google": just switch to phhusson "gapps" flavour...
Bugs reporting
ufOfficial rom includes static & passive app kDI (KalturaDeviceInfo) to list all your device specs (treble, widevine...) in a json, and can help you with GSFid or others info(s). This app doesn't connect to internet, and the json (~Android/data/com.oF2pks.kalturadeviceinfo/files/) should not include any private data or ids; it's up to you to share or not.
If you encounter major AOSP "hardware (not software)" related bugs, please switch to #phhusson vanilla v___ edition and help him with proper focused hardware logs. For Camera2 missing features, take time to check OpenCamera first, aosp DevCamera "sample stub" is included for testing purpose : autofocus... ; full cam specs are also in KalturaDeviceInfo (per each "physical" cam).
Click to expand...
Click to collapse
(Specific Sony yoshino overlay & props are added: only available for Sony xz1/G8341-2 & xz1c/G8441 devices)
For Treble when rooted, you can do some tests modifying specifically : /system/bin/rw-system.sh to change some features on post-fs https://github.com/phhusson/device_phh_treble/blob/android-9.0/vndk.rc#L1
hot-built links :
Code:
[SIZE="1"]https://source.codeaurora.org/external/gigabyte/platform/packages/apps/Exchange -b LA.UM.7.6.r1-03700-89xx.0
https://source.codeaurora.org/quic/la/platform/packages/apps/SnapdragonMusic -b android_ui.lnx.3.0.r11-rel
https://github.com/LineageOS/android_packages_apps_Recorder -b lineage-16.0
https://gitlab.com/oF2pks/jelly -b jQuarksMore
https://github.com/LineageOS/android_external_chromium-webview/tree/lineage-15.1
https://github.com/LineageOS/android_packages_apps_Terminal
[/SIZE]
- Bromite latest webView v76 with ad-blocking, upgradable via F-Droid repo https://fdroid.bromite.org/fdroid/repo (Bromite 76 returns a 74/SamsungS9 webclient https://github.com/bromite/bromite/issues/156#issuecomment-445449741: Mozilla/5.0 [Linux; Android 8.0.0; SM-G960F] AppleWebKit/537.36 [KHTML, like Gecko] Chrome/74.0.3729.157 Mobile Safari/537.36); if v76 seems too selective, upgrade to latest Bromite without ad-blocking (v78)
- Optimized browser Quarks ( offline reading mht , print/pdf , share/clipboard target ...) https://gitlab.com/oF2pks/jelly/commits/jQuarksMore package is renamed org.lineageos.jelly for better LineageOS upstream.
Can it boot by mokee kernel for a snapdragon 835?
umidigi a1 pro camera crash.... (open camera, footej, beacon camera)
A very well written OP.
Great job
Tested and functional on S9
Most thing fully functional. Cant get MTP to connect tho.
NisseGurra said:
Tested and functional on S9
Most thing fully functional. Cant get MTP to connect tho.
Click to expand...
Click to collapse
Can you please check GCam is working or not?
oF2pks said:
[9.0.0_r21/v108] download : https://androidfilehost.com/?a=show&w=files&flid=286761
"Regular" #phhusson AOSP 9.0 vanilla build with microG patches, #ale5000 implementation and multiple foss apps: .
microG: GmsCore15.9.99** GoogleServicesFramework
addons: DroidGuard* DejaVuBackend NominatimGeocoderBackend IchnaeaNlpBackend
hot-built: emailExchange2 snapMusic Terminal screenRecorder testDevCamera browserQuarks
prebuilt: Fdroid ZxingClient NightshadelabsAnotherbrowser** kalturadeviceinfos**
system/bin** : aapt32 curl32 grep64(pcre2grep version 10.22 2016-07-29)
Any chance you would be interested in building arm64 a/b ?
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
swiftbones74 said:
Any chance you would be interested in building arm64 a/b ?
Click to expand...
Click to collapse
See the link, already there...
Thanks for doing that, I know that's something that's been missing for some time.
Do you think you'll maintain it "long"-term? (you're using it for yourself?)
Are you releasing by hand, or do you have scripts to automate releases?
It would be nice to also have arm a-only variant, since usually those are cheaper devices, with a lot less RAM, which would be much more happier without Google apps.
Missing complementary old MapsAPIv1 will be added in next release (framework/com.google.android.maps.jar) + specific attached wallpaper
phhusson said:
"long"-term? (you're using it for yourself?)
Are you releasing by hand, or do you have scripts to automate releases?
Click to expand...
Click to collapse
Yes, I will try to follow your releases versioning so user's reports will be synced (build: I've added an inherit ufo.mk -> vendor/ufo, to your generated treble_arm64_*vN.mk)
For arm32 low cost device release, are you referring to treble_arm_avN(vndk-binder32) or treble_a64_avN(vndk32) ?
EDIT2: @phhusson , both arm32_aonly uploaded here :
https://androidfilehost.com/?w=files&flid=287186
com.google.android.maps.jar & LosTerminal are now included
btw, I choose to deodex embedded webwiew (Los v69), but was not able to build a stable complete deodexed aosp (#WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY := true), any hint ?
For info, I use your embedded prebuilt Phonesky(gapps-go) to initiate Playstore account; already paid apps are ok, but with microG/Magisk 17.3 (sony xz1), I fail on CTSprofile match.
EDIT Playstore NOT certified (PlayProtect...) despite GSFid registration
Since some don't have twrp, I'm also looking for a simple "bridge" to patch etc/hosts from within Settings/.../DevOptions, do you believe it could break Treble securities & bootloop : https://github.com/AICP/packages_ap...ndroid/settings/aicp/hfm/HfmHelpers.java#L108 ?
1000Thx again for your heavy works.
Any Screenshot?
Newest version works great !!! Play store works (once enable all the MicroG settings). Waze works for GPS (Google Maps would not work for my Moto G6 XT1925-6).
I tested latest version...a good work but it would much better if there are no apps preinstalled, like here:
https://lineage.microg.org/
Just installed latest arm32_binder64 version on j6 (j600fn to be more exactly) booted fine but without RIL, stock camera crashed at launch.
Shobit Joura said:
This is for a only , I am having a device with a/b partition...
Click to expand...
Click to collapse
you should find it in arm64_abSEAMLESS
Lecterr said:
... it would much better if there are no apps preinstalled, like here:https://lineage.microg.org/
Click to expand...
Click to collapse
Can you elaborate ? Not all users have twrp on their device, so they need all @ale5000 prebuilts in/system + Playstore + Contact/Calendar_GoogleSync;
-classic "old" fdroid 0.102.3 in /system helps users decide to upgrade to any "modern" version with option to downgrade back,
-NightshadelabsAnotherbrowser is tiniest existing apk : browser switcher.
-(hotbuilts are not preinstalled...)
-most of all users forgot barcode/QRcode and miss it when they need it, also it useful to test camera (same as devCamera... and ZxingClient best you can find).
Finally KalturaDeviceInfo (I'm also the dev) is embedded because, conversely to Lineage, aosp don't include any dynamic reporting, and should helps users ( @conanedogawa1011 , @SkyWorldWide ) to overview their device & report: my next release will include fdroid signed edition.
(will also probably use MicroG gmscore semi-official @Setialpha ' release & repo)
All these "preinstalled" floss can be disabled via settings: your next ota will keep them disabled automatically.
lzimbrea said:
Just installed latest arm32_binder64 version on j6 (j600fn to be more exactly) booted fine but without RIL, stock camera crashed at launch.
Click to expand...
Click to collapse
DevCamera & KalturaDeviceInfo can help you understanding the behavior: check latest(rc6) for "#CAMERA2API="in json for more details, and find appropriate focused log (clean all recent apps+ launch adb shell logcat + launch camera...)for Phhusson (hardware bug)
I been on this rom for few weeks now, very stable.
0,4% / h idle drain with 2 sims. Getting 6-7 h screen on
No bugs at all. Good work!
Device: S9
maybe on update more optimization for more battery life
hello, thank you!
is there a separate patched microG package which can be installed in TWRP over vanilla-nosu AOSP?
@eremitein
https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
Welcome to Quantic a Kernel built specially for Redmi k30 PRO/ POCO F2 Pro codename: lmi
One of the most used kernel on Custom ROMS on Cepheus chosen by developers and one of the most battery friendly on Redmi k20 Pro community
/* I'm not responsable for any damage on your device, for X or Y reason, also I'm not responsable if you loose your alarm and got fired and also the thermonuclear war, anything like that, installing this kernel you renounce to make me responsable of any unwanted behavior of your device */
/*Compatible ONLY with Android 10*/
Hi everyone, I want to introduce you my new kernel named Quantic-Kernel, this is my personal build kernel with my prefered features. Hope everyone enjoy it and I'll be maintaining it so people can used it with their preferred AOSP ROM(See details below)
FEATURES
Upstreamed CAF to: LA.UM.8.12.r1-10600-sm8250.0
Fixed Camera not working on AOSP ROMs
Reduced logging events
Performance Improvements on scheduler
Enabled ZRAM up to 2GB with lz4 compressor
Upstreamed lz4 compressor
readahead optimizations
Android Binder tweaks
Optimized memory allocations
Reduced kernel weight
Deactivated CAF CPU Boost following MIUI stock kernel parameters
FIX CPU Capacity issues
INSTALLATION PROCEDURE
Make a TWRP backup of BOOT and DTBO partitions
Flash Quantic-Kernel_rX.zip
Reboot to system
Enjoy it
BUGS:
Hostpot may be broken
Works only on ROMS with firmware 12.0.4.0 (check details on Github release)
DOWNLOAD HERE
https://github.com/KONA-DEVS/kernel_xiaomi_sm8250/releases/tag/r2
TELEGRAM CONTACT
https://t.me/Ayrton990 <-- Personal TG
https://t.me/aicplmi <-- Discussion group for support
Thanks List
To kdrag0n
To Kerneltoast
To alk3pInjection
ATTENTION: This KERNEL is NOT based on HiiraKernel, is in construction since early October when I bought the device
SCREENSHOTS ATTACHED BELOW
XDA:DevDB Information
Quantic Kernel, Kernel for the Redmi K30 Pro
Contributors
Ayrton990
Source Code: Github KONA-DEVS
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: r2
Beta Release Date: 2020-11-29
Created 2020-11-22
Last Updated 2020-11-29
Reserved
Another reserved
Hostpot may be broken => I'm waiting when it finish !!!
svzodiac said:
Hostpot may be broken => I'm waiting when it finish !!!
Click to expand...
Click to collapse
what do you mean with that?
Ayrton990 said:
what do you mean with that?
Click to expand...
Click to collapse
BUGS:
Hostpot may be broken => I'm waiting for the stable version
PE Plus - stuck on POCO Logo. Still better this than crashing after boot ;D
Edit: Also if some apps stopped working (showing content) for ya just clear data of Android System WebView
Deleted
@Ayrton990: Awesome! Could you add Wireguard support, please?
Finally a kernel for this device, thanks for this man. I hope we get more kernels and MIUI/Android 11 support.
svzodiac said:
BUGS:
Hostpot may be broken => I'm waiting for the stable version
Click to expand...
Click to collapse
Yeah but the way you wrote it seems to be little rude
grt67DFqyu said:
@Ayrton990: Awesome! Could you add Wireguard support, please?
Click to expand...
Click to collapse
Yes it will be added next update
Thank you for your work！！！Will you consider supporting lineageos？
will you add kcal support & fsync toggle?
Camera does not work in c.droid after kernel
Derepinar said:
Camera does not work in c.droid after kernel
Click to expand...
Click to collapse
Crdroid use 12.03......this kernel work on 12.04 base.
This should work for Paranoid Quartz right?
nvm: aospa is based on 12.03
Awesome work! Thanks!
Thank you very much ? i am waiting miui12 and android 11 weakly support. And i am waiting mostly screen oc. Congratulations for fix xiaomi sources ?
how do I know on which version of ROM am I ? I forgot what was my stock ROM was when I was flashing first Xiaomi.eu rom then oneOS rom..
{
"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"
}
Introduction
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is a combined thread for the A series Exynos7580 based devices.
What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Installation
Install the latest TWRP for your device
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Data, System)
If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
Flash the latest LineageOS 18.1
Opengapps
(Magisk if required)
Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
Make a full backup
Flash in this order:
LineageOS-18.1
OpenGapps 11
(Magisk if required)
And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE
Thanks
@Stricted
@dariotr
@Androbots
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present
If you like my work consider buying me a coffee:
Source Code: https://github.com/LineageOS
Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_a7xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common
Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580
ROM OS Version: Android 11
Based On: LineageOS
Version Information
Status: Stable
Created 2020-08-20
Last Updated 2022-06-15
Changelog:
Changes 09-04-2023:
Synced to latest LineageOS source (including March security patch)
Changes 18-01-2023:
Synced to latest LineageOS source (including January security patch)
Included patches missed in last build
Changes 19-08-2022:
Synced to latest LineageOS source (including August security patch)
Changes 15-06-2022:
Synced to latest LineageOS source (including June security patch)
ZRAM now mounted with discard option (thanks @JPCastillo2000 for the link)
Changes 26-04-2022:
Synced to latest LineageOS source (including April security patch)
Changes 15-03-2022:
Synced to latest LineageOS source (including march security patch)
Spoiler: Older changelog
Changes 20-01-2022 (all devices):
Synced to latest source (January security patch)
Enable WiFi display
Switch to GNSS HIDL service (improves GPS stability, thanks @retiredtab @impasta)
Fixed power profile switching (restores correct CPU speed when going back to balanced mode)
Changes 20-01-2022 (A510F/A710F):
Enable fastcharge hal (allows disabling fastcharge)
Changes 19-10-2021:
Synced to latest Lineageos (October security patch)
Changes 25-09-2021:
Fixed SDFat bug that caused reboots when accessing sd card (thanks to Ícaro Albuquerque for testing)
Changes 21-09-2021:
Resysnced source (includes updated webview)
Fixed Wi-Fi hotspot (broken in last build)
Added slow/fast charging detection (indicates on lock screen)
Changes 16-09-2021:
Synced LineageOS sources (includes September security patch and AOSP WFD)
Fixed WiFi direct
Added further ZRAM improvements (thanks @alexax66)
Changes 28-08-2021:
Updated ZRAM implementation from Linux 4.1.52
Switched to LZ4 ZRAM compression (should be faster and better)
Changes 24-08-2021:
Synced latest LineageOS sources (includes new lineageos charger animation)
Cleaned up device overlays
Fixed tethering overlays
Disabled BPF offload for tethering (as we dont support it)
Added a7xelte to thread
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
vrobo said:
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
Click to expand...
Click to collapse
Hi,
A search on XDA reveals this write up:
LineageOS 18.1 based on Android 11 is here for nearly 60 devices
LineageOS 18.1 builds based on Android 11 are now available for dozens of smartphones. Here's the changelog and supported devices list!
www.xda-developers.com
On top of this we have a lot of fixes for our devices from security to ram management. The list is too long, if you are interested take a look at the device trees and kernel source on GitHub.
With regards to app compatibility, Android 11 has been out for nearly a year now. If an app you use isn't compatible then to be honest it isn't worth using.
Kind regards,
Danny
vrobo said:
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
Click to expand...
Click to collapse
Mail app is missing. Make sure you have your mail account details to setup a different client. I recommend FairEmail
kurtn said:
Mail app is missing. Make sure you have your mail account details to setup a different client. I recommend FairEmail
Click to expand...
Click to collapse
probably because the Email app is broken?
I've been using FairEmail since I've spotted this problem: https://forum.xda-developers.com/t/...7-1-for-a5-2016.4036151/page-35#post-85302601
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.
How are the plans for going official? That determines how to handle forks with signature spoofing.
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.
So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.
Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.
No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.
Edit:
the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
danwood76 said:
Introduction
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is a combined thread for the A series Exynos7580 based devices.
What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Installation
Install the latest TWRP for your device
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Data, System)
If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
Flash the latest LineageOS 18.1
Opengapps
(Magisk if required)
Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
Make a full backup
Flash in this order:
LineageOS-18.1
OpenGapps 11
(Magisk if required)
And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE
Thanks
@Stricted
@dariotr
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present
If you like my work consider buying me a coffee:
Source Code: https://github.com/LineageOS
Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common
Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580
ROM OS Version: Android 11
Based On: LineageOS
Version Information
Status: Stable
Created 2020-08-20
Last Updated 2020-08-20
Click to expand...
Click to collapse
Hi
Why was it not Build for (a7xelte) A710 2016?
setecastronomy said:
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.
So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.
Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.
No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.
Edit:
the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
Click to expand...
Click to collapse
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.
mihancad said:
Hi
Why was it not Build for (a7xelte) A710 2016?
Click to expand...
Click to collapse
I will add the a7 on Tuesday, although I am not the maintainer of that device.
kurtn said:
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.
How are the plans for going official? That determines how to handle forks with signature spoofing.
Click to expand...
Click to collapse
The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.
Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).
Kind regards,
Danny
Thank you, my brother, I look forward to it
Thanks a lot for developing new OS for our A310f, Dan. Great work, I runs fine, flowing perfect!!
danwood76 said:
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card.
Click to expand...
Click to collapse
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).
And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.
danwood76 said:
You are much better off switching to exfat.
Click to expand...
Click to collapse
And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2
08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096
08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space
08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67)
--------- beginning of kernel
(and the boot sequence, apparently)
After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.
So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
setecastronomy said:
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).
And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.
And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2
08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096
08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space
08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67)
--------- beginning of kernel
(and the boot sequence, apparently)
After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.
So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
Click to expand...
Click to collapse
Try formatting the card from the phone. I have had issues formatting using Linux and Windows before, even for my stock S9.
Kind regards,
Danny
danwood76 said:
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.
I will add the a7 on Tuesday, although I am not the maintainer of that device.
The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.
Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).
Kind regards,
Danny
Click to expand...
Click to collapse
Will it be ready for download for A7 (a7xelte) today?
mihancad said:
Will it be ready for download for A7 (a7xelte) today?
Click to expand...
Click to collapse
Asking for ETAs is rude. I have already said that I will make a build for the A7 today. But it will be much later on.
setecastronomy said:
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
Click to expand...
Click to collapse
I have just done this on my test A5 and everything worked perfectly, I downloaded 300MB of maps of my region and it all works well. There was a permissions pop up when I first opened the app which i accepted.
The card is my old Samsung 64GB, I wiped the card in my desktop and then allowed the phone to format it, I think Windows/Linux sets some exFAT options that android doesn't like so it is best to let the phone do it.
Kind regards,
Danny
I have just uploaded a small update and added the a7xelte build.
Changes 24-08-2021:
Synced latest LineageOS sources (includes new lineageos charger animation)
Cleaned up device overlays
Fixed tethering overlays
Disabled BPF offload for tethering (as we dont support it)
Added a7xelte to thread
Kind regards,
Danny
danwood76 said:
Asking for ETAs is rude. I have already said that I will make a build for the A7 today. But it will be much later on.
Click to expand...
Click to collapse
I'm sorry, I'm using Google Translate, I just informed you as a reminder.
Thank you very much for your kindness, dear Danny
Just wanted to say that the A510F works very well, except that sometimes the camera doesn't connect.
Thank you for your effort @danwood76 (and maybe others )!
Hello everyone ! i started today my third guide , i hope i was helpful and if you want help me complete the index you can ! and don't forget hello we are human not animal
CUSTOM ROM :
[ROM][OFFICIAL][A12.1] Descendant [06/22] by Ayrton990
LineageOS 19.1 | UNOFFICIAL posted by rayman95 but created by @NeoArian updated today jump to page 2 for OS update
LineageOS 19.1 | OFFICIAL by ???
LineageOS 18.1 | UNOFFICIAL | posted by rayman95 but created by @NeoArian
CorvusOS 4.0-L v12.1 - UNOFFICIAL | Android 12L. Vanilla/GApps | posted by rayman95 but created by @mejsi
Pixel Experience 12 Renoir | OFFICIAL | DISCONTINUED
DotOS by Iacob Ionut Need to be Tested
CHERISH OS 12.1 by RobertGarciaa Need to be Tested
TEQUILA OS by ejbtrd
[ROM][OFFICIAL][A12.1] Descendant [06/22] by Ayrton990RECOVERY :
TWRP OFFICIAL by Nebrassy
FIRMWARE :
[Firmware] Mi 11 Lite 5G [renoir] [Auto updated!] by yshalsager
KERNEL:
[KERNEL][AOSP] Quantic Kernel [5.4.203][07/04/22] by Ayrton990
Thanks to member post and shared ROM and developer , please answer this post if you want add more modification for this phone
- Fabien976
After lineage os 19.1 isn't working for me i searched for another custom rom and found dotos:
dotOS | Loading...
A beautiful custom ROM based on AOSP, which endeavors the essence of Simple, Unique, Secure.
www.droidontime.com
Hope it's working for me =(
jokergermany said:
After lineage os 19.1 isn't working for me i searched for another custom rom and found dotos:
dotOS | Loading...
A beautiful custom ROM based on AOSP, which endeavors the essence of Simple, Unique, Secure.
www.droidontime.com
Hope it's working for me =(
Click to expand...
Click to collapse
Hello ! When have you tested do me feedback !
fabien976 said:
Hello ! When have you tested do me feedback !
Click to expand...
Click to collapse
At the moment nothing is working for me. I am stuck in fastboot everytime and have to recover miui 13...
jokergermany said:
At the moment nothing is working for me. I am stuck in fastboot everytime and have to recover miui 13...
Click to expand...
Click to collapse
Hello, format all data and flash a new recovery and miui rom ? In fastboot rom ?? Developer Can help ?
fabien976 said:
Hello ! When have you tested do me feedback !
Click to expand...
Click to collapse
Los is better than dotos, more stable and smooth
rayman95 said:
Los is better than dotos, more stable and smooth
Click to expand...
Click to collapse
is that the one from Arians?
danko843 said:
is that the one from Arians?
Click to expand...
Click to collapse
yes, the one I share here..
jokergermany said:
After lineage os 19.1 isn't working for me i searched for another custom rom and found dotos:
dotOS | Loading...
A beautiful custom ROM based on AOSP, which endeavors the essence of Simple, Unique, Secure.
www.droidontime.com
Hope it's working for me =(
Click to expand...
Click to collapse
I will add dot OS in the list this afternoon
fabien976 said:
I will add dot OS in the list this afternoon
Click to expand...
Click to collapse
salut tu pourras ajouter un cherish aussi
Release cherish os 12.1 · RobertGarciaa/renoir-custom-rom
LOS tree, kernel : https://github.com/renoir-development cherish os dialer
github.com
Thank you very much for this resumee.
I am very, very sad, that there are only that few roms for our lite pfone - most of them even unofficial builts.
I get, that the release-circles of new phone models and the trend to chunky, heavy and even faster flagships are hindering factors, but I had my hopes up, that after the 4G-model there would be an official cr-droid maintainer for the stronger 5G-model as well - but there is not! 4G is getting update after update, but 5G is not getting any attention.
If I only knew, how to install cr-droid on our phone and update it weekly, I would be totally satisfied.
I am now on Xiaomi.EU 13, A12. I will try unofficial LOS of course, but I miss features of cr-droid.
Best regards and keep up the good work!
Thanks for your jod, brother
tequilaOS | renoir
tequilaos.pl
New build of tequilaOS tobacco for Xiaomi Mi 11 Lite 5G (renoir) is available!
by: ejbtrd
jokergermany said:
After lineage os 19.1 isn't working for me i searched for another custom rom and found dotos:
dotOS | Loading...
A beautiful custom ROM based on AOSP, which endeavors the essence of Simple, Unique, Secure.
www.droidontime.com
Hope it's working for me =(
Click to expand...
Click to collapse
rayman95 said:
salut tu pourras ajouter un cherish aussi
Release cherish os 12.1 · RobertGarciaa/renoir-custom-rom
LOS tree, kernel : https://github.com/renoir-development cherish os dialer
github.com
Click to expand...
Click to collapse
Hello ! Added!
fabien976 said:
Привіт ! Додано!
Click to expand...
Click to collapse
м Do you not add the Android 13 assembly that I indicated above?
danko843 said:
м Do you not add the Android 13 assembly that I indicated above?
Click to expand...
Click to collapse
Sorry i didn't see your post, it's added !
Index updated , if anyone want i add new mods in index write here
fabien976 said:
Index updated , if anyone want i add new mods in index write here
Click to expand...
Click to collapse
salut
new GMS LOS today and miui camera mod too
Index updated i've added a official link about LOS
fabien976 said:
Index updated i've added a official link about LOS
Click to expand...
Click to collapse
it's @NeoArian who made it official..thank's to him..