{
"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
RevengeOS is a custom ROM based on CAF which aims to increase you phone smoothness, offer a better user experience and make your battery last longer
All the source code for Revenge OS is available in the Revenge OS Github repo.
* I am not responsible for bricked devices, dead SD cards
Whats working?
WiFi
RIL
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
IR
Lights
All Sensors
Sound / vibration
Mobile data
Known issues
You tell me
You can find all my builds here
https://www.androidfilehost.com/?w=files&flid=286017
DON'T FLASH GAPPS, ALREADY INCLUDED -Download the ROM
-Backup each and every partition from TWRP Recovery(optional)
-Make a full wipe (system, data, cache, dalvik)
-Flash RevengeOS Package
- Gapps are included in this ROM
-Wipe cache! -And at last Reboot!
[First boot will take few minutes! Have patience]
Clean Flash is always recommended!
small tip :
check out
settings > system > gestures > swipe up on home button >
system runs smoother
Thanks to:
All MSM8916 Developers
XDA:DevDB Information
RevengeOS, ROM for the Samsung Galaxy S4 mini VE(GT-I9195I)
Contributors
mernurisha
Source Code: https://github.com/RevengeOS
Kernel: https://github.com/Galaxy-MSM8916
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: CAF
Version Information
Status: Stable
Stable Release Date: 2019-07-24
Created 2019-07-06
Last Updated 2019-07-24
new build
changes:
- Mobile data fixed
- Added KCAL to the kernel for Advanced color control support (Thanks to Kariboo92 for the hint)
- Kernel compiled toolchain version gcc_linux-x86_arm_arm-eabi-8.3
mernurisha said:
changes:
- Mobile data fixed
- Added KCAL to the kernel for Advanced color control support (Thanks to Kariboo92 for the hint)
- Kernel compiled toolchain version gcc_linux-x86_arm_arm-eabi-8.3
Click to expand...
Click to collapse
Gracias por esta nueva ROM, en mi caso el idioma español no se aplica a todas las funciones, jejejejeje obviamente no afecta a la funcionalidad....nuevamente gracias
Nice Work!
I am trying to compile for my "serranodsdd" variant but I am having this error, can you help me?
[email protected]:~/WORKSPACE$ make -j4 serranodsdd
Restriction Checker not present, skipping..
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.0.0-20-generic-x86_64-Ubuntu-19.04
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PKQ1.190616.001
OUT_DIR=/home/bezouro/WORKSPACE/out
============================================
ninja: no work to do.
[34/53] test android/soong/cc/config
[51/53] test android/soong/cc
[53/53] /home/bezouro/WORKSPACE/out/soong/.bootstrap/bin/soong_build /home/bezouro/WORKSPACE/out/soong/build.ninja
FAILED: /home/bezouro/WORKSPACE/out/soong/build.ninja
/home/bezouro/WORKSPACE/out/soong/.bootstrap/bin/soong_build -t -l /home/bezouro/WORKSPACE/out/.module_paths/Android.bp.list -b /home/bezouro/WORKSPACE/out/soong -n /home/bezouro/WORKSPACE/out -d /home/bezouro/WORKSPACE/out/soong/build.ninja.d -o /home/bezouro/WORKSPACE/out/soong/build.ninja Android.bp
(0x8fb0e0,0xc42013c6f0)internal error: panic in GenerateBuildActions for singleton glob
error parsing variable "glob": invalid character after '$' at byte offset 1
goroutine 1 [running]:
github.com/google/blueprint.newPanicErrorf(0x805f80, 0xc48019ca50, 0xc4393bf380, 0x27, 0x0, 0x0, 0x0, 0x20, 0x42633e)
/home/bezouro/WORKSPACE/build/blueprint/context.go:3462 +0x82
github.com/google/blueprint.(*Context).generateSingletonBuildActions.func1.1(0xc423773b98, 0xc4780e1540)
/home/bezouro/WORKSPACE/build/blueprint/context.go:2320 +0x396
panic(0x805f80, 0xc48019ca50)
prebuilts/go/linux-x86/src/runtime/panic.go:505 +0x229
github.com/google/blueprint.(*singletonContext).Build(0xc4780e1540, 0x902f00, 0xc420092320, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/bezouro/WORKSPACE/build/blueprint/singleton_ctx.go:169 +0x16f
github.com/google/blueprint/bootstrap.GlobFile(0x7f8d857f70e8, 0xc4780e1540, 0xc42c17e800, 0x20, 0x0, 0x0, 0x0, 0xc4801aa550, 0x4d, 0xc4801aa5a0, ...)
/home/bezouro/WORKSPACE/build/blueprint/bootstrap/glob.go:72 +0x245
github.com/google/blueprint/bootstrap.(*globSingleton).GenerateBuildActions(0xc4200900f8, 0x9075e0, 0xc4780e1540)
/home/bezouro/WORKSPACE/build/blueprint/bootstrap/glob.go:133 +0x3d6
github.com/google/blueprint.(*Context).generateSingletonBuildActions.func1(0xc423773b98, 0xc4780e1540)
/home/bezouro/WORKSPACE/build/blueprint/context.go:2324 +0x81
github.com/google/blueprint.(*Context).generateSingletonBuildActions(0xc4200a9a20, 0x88be20, 0xc42018e000, 0xc4200b2780, 0xb, 0x10, 0xc4274299e0, 0x0, 0x0, 0x0, ...)
/home/bezouro/WORKSPACE/build/blueprint/context.go:2325 +0x2a8
github.com/google/blueprint.(*Context).PrepareBuildActions(0xc4200a9a20, 0x88be20, 0xc42018e000, 0x7f8d865f6740, 0xc42018e000, 0x1, 0x0, 0x0, 0x0)
/home/bezouro/WORKSPACE/build/blueprint/context.go:1878 +0x12c
github.com/google/blueprint/bootstrap.Main(0xc4200a9a20, 0x88be20, 0xc42018e000, 0xc420623f58, 0x3, 0x4)
/home/bezouro/WORKSPACE/build/blueprint/bootstrap/command.go:164 +0x7d3
main.main()
/home/bezouro/WORKSPACE/build/soong/cmd/soong_build/main.go:75 +0x26d
ninja: build stopped: subcommand failed.
02:19:08 soong bootstrap failed with: exit status 1
#### failed to build some targets (53 seconds) ####
#### hidl-gen compilation failed, check above errors ####
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.0.0-20-generic-x86_64-Ubuntu-19.04
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PKQ1.190616.001
OUT_DIR=/home/bezouro/WORKSPACE/out
============================================
ninja: no work to do.
[0/1] /home/bezouro/WORKSPACE/out/soong/.bootstrap/bin/soong_build /home/bezouro/WORKSPACE/out/soong/build.ninja
Click to expand...
Click to collapse
bbezouro said:
Nice Work!
I am trying to compile for my "serranodsdd" variant but I am having this error, can you help me?
Click to expand...
Click to collapse
Do not know your computer configuration (ram, cpu). I can not say much about your log.
You build on an Ubuntu 19. You have to instal all dependencies to build pie rom. There are enough instructions on the web.
https://raw.githubusercontent.com/nathanchance/Android-Tools/master/Guides/Building_AOSP.txt
I do not know if that goes on ubuntu 19 (due to dependencies). Try with lineageos first. Is much easier if you have the right device tree.
good luck
mernurisha said:
Do not know your computer configuration (ram, cpu). I can not say much about your log.
You build on an Ubuntu 19. You have to instal all dependencies to build pie rom. There are enough instructions on the web.
https://raw.githubusercontent.com/nathanchance/Android-Tools/master/Guides/Building_AOSP.txt
I do not know if that goes on ubuntu 19 (due to dependencies). Try with lineageos first. Is much easier if you have the right device tree.
good luck
Click to expand...
Click to collapse
ohh, thanks!
I'm using the lineage device tree, but I probably missed something while setting up the build environment,
I followed this step by step "https://github.com/RevengeOS/android_manifest"
well, my computer specs are pretty simple, i think i will set up the development environment on google cloud
Core2quad 2.33ghz Q8200
4gb ddr3
240gb ssd
---------- Post added at 02:53 PM ---------- Previous post was at 01:54 PM ----------
well i'm sorry i saw that i was actually compiling for a "generic" device and again i used the "build / envsetup.sh" and "lunch" commands and it started working
mernurisha said:
changes:
- Mobile data fixed
- Added KCAL to the kernel for Advanced color control support (Thanks to Kariboo92 for the hint)
Click to expand...
Click to collapse
Thank you, KCAL works great !
We can control KCAL thougth /sys
I'm able to reduce saturation from 275 (default) to 240 to obtain more natural colors using command line:
Code:
echo 240 >/sys/devices/platform/kcal_ctrl.0/kcal_sat
Set 128 for grayscale, and between 224 to 383 to control color saturation (default 275).
Here is the list of controls that are available:
/sys/devices/platform/kcal_ctrl.0/kcal - (0-256 0-256 0-256) - Controls R/G/B Multipliers
/sys/devices/platform/kcal_ctrl.0/kcal_min - (0-256) - Controls minimum RGB Multiplier value
/sys/devices/platform/kcal_ctrl.0/kcal_enable - (0-1) - Enables/Disables RGB Multiplier Control
/sys/devices/platform/kcal_ctrl.0/kcal_invert - (0-1) - Enables/Disables Display Inversion Mode
/sys/devices/platform/kcal_ctrl.0/kcal_sat - (224-383 or 128) - Controls saturation intensity - use 128 for grayscale mode
/sys/devices/platform/kcal_ctrl.0/kcal_hue - (0-1536) - Controls display hue - may have issues with msm8x26 in the higher values
/sys/devices/platform/kcal_ctrl.0/kcal_val - (128-383) - Controls display value
/sys/devices/platform/kcal_ctrl.0/kcal_cont - (128-383) - Controls display contrast
Click to expand...
Click to collapse
For more information on KCAL : https://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
The Kcal app (re.codefi.savoca.kcal-v1.2.apk) control is crashing unless Magisk Hide is disabled for this app.
Good job !
Is it possible to build a CAF rom for GTI9195 (not VE version) using the phone's device tree?
faizankhalifa said:
Is it possible to build a CAF rom for GTI9195 (not VE version) using the phone's device tree?
Click to expand...
Click to collapse
Usually yes.
Thank you for developing our device very much, mernurisha
In my case:
1. first boot lasted a few seconds and it stopped responding
2. after 15 minutes I turned my device off
3. when turned on again RevengeOS started after 2 minutes
4. system works well but SD-card was not detected
5. first system reset made it boot looping
ffox.pl said:
Thank you for developing our device very much, mernurisha
In my case:
1. first boot lasted a few seconds and it stopped responding
2. after 15 minutes I turned my device off
3. when turned on again RevengeOS started after 2 minutes
4. system works well but SD-card was not detected
5. first system reset made it boot looping
Click to expand...
Click to collapse
I bought the same memory card (Kingston microSDXC 64GB Class 10). Is recognized without problems in all roms.
Below is a screenshot made in RevengeOS. Unfortunately, I can not explain your problem with SD card.
I will update the RevengeOS for the last time very soon with many changes.
new update
The new and last update has been uploaded.
RevengeOS-2.5-Pasta-UNOFFICIAL-serranovelte-20190730-1524
<Mod Edit>
Thread closed by OP request.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I present to you, LineageOS 14.1, brought to you by me and @surdu_petru, @spirtix, @papsi177, @Speedo.thc, @haky86 and @nexolight & @ad2072
Code:
/*
I am not responsible for fried or bricked devices.
This ROM is in testing stages. If you point the finger of blame at me for messing up your device, I will laugh at you. (Maybe I will try to help)
*/
What works:
RIL (sms, calls, lte)
Wifi
Screen recording
Ok performace (governor ondemand)
Bluetooth
SD card
Heating is controlled
Sensors
NFC
DT2W (well, it really is a 4-tap to wake when device is sleeping) code from @meticulus (github)
Power profiles (adjustable cpu speeds via settings->battery)
GPS
What does not work:
Camera
FM radio
Battery drain by telephony (?)
Unstable SD
#########################
Downloads:
https://mega.nz/#F!RDhHgIgL!AAecbdpaipXsR01d2pT6gA
v1.6.2-beta-8-7-2018 https://mega.nz/#F!RDhHgIgL!AAecbdpaipXsR01d2pT6gA
Upstreamed kernel
Better sdcardfs
Fixed Wifi hotspot
v1.6.1-beta-5-7-2018 https://mega.nz/#F!dfg2xIII!pPIrs7V1fLOSrjouAe5AxQ
Fix rest of powerHAL
Fixed GPS (will only work after reboot)
v1.6-beta-25-6-2018 https://mega.nz/#F!4T5jUKhY!582ayRsiwjWakXacPH9PPA
Update power profiles
Adjustable in settings (battery->battery saving and performance)
Changed to interactive
Scheduler row -> cfq
NFC works (give it a little time to load after booting)
Minor updates regarding GPS, Wifi hotspot and HD playback
v1.5.2-beta-20-6-2018 https://mega.nz/#F!cOQF3CKL!jy7nOLaxaCYEXvfMfX3GbQ
A zip file!
Cleaned up ramdisk
Improved kernel
* DT2W (or 4T2W when device is dozing)
v1.5-beta-31-5-2018 https://mega.nz/#F!RCIzGJ4L!fpbZA0lFY9HA85RN0aevyA
Kernel updated to 3.10.108
Cleaned up ramdisk
Slight performance update (assinged seperate core for other tasks)
Enabled FlipFlap (smart covers (only magnetic))
Improved kernel
* Added more governors
* Removed pointless huawei stuff
v1.3-beta-3-5-2018 https://mega.nz/#F!dGAWWKYa!z5HgFbfr35MaS2UDsQs94Q
Kernel updated from 3.10.86->3.10.105
ZRAM and KSM disabled -> better performance
Sensors
###################
Also thanks for everyone who helped (erayrafet, rejaue0)
XDA:DevDB Information
LineageOS 14.1 gra_l09, ROM for the Huawei P8
Contributors
T1mb3, surdu_petru, spirtix, papsi177, speedo.thc, haky86
Source Code: [url]https://github.com/T1mpp4/android_device_huawei_hwgra[/URL]
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2018-04-18
Last Updated 2018-04-22
Logcat on quick settings tiles crash: https://drive.google.com/file/d/1wtmxJI-6DLTuwDhpvNUDHM0SaWjTJD5t/view?usp=drivesdk
Old builds
Code:
Version 1: [url]https://mega.nz/fm/lPQmGaaD[/url]
[LIST]
[*]I have not actually tried this
[*]There is some update on trying to fix ril, so report if it works (is SIM detected)
[/LIST]
Version 2:
[LIST]
[*]RIL fixed (thanks speedo.thc)
[*]Some camera work
[/LIST]
Version 3: [url]https://mega.nz/#F!pf5TTJYI!vISWqwBm3BfBW9uRD-K87A[/url]
Version 4: [url]https://mega.nz/#F!oeRFnJDA!c3IIWNPnipiauUHh7_87gg[/url]
[LIST]
[*]Performace update
[*]Some GPS work
[/LIST]
Version 5: [url]https://mega.nz/#F!wPwGFITZ!D9nngDohPQuE-NtRdsAjFg[/url]
[LIST]
[*]Bluetooth fix (by Packmaan7144 [user=4166799]@github[/user])
[*]Thermal-daemon enabled
[*]Freed up some space in boot partition
[/LIST]
Version 6: [url]https://mega.nz/#F!5OZnUApY!RmPRBvM8lFRnciinA023wg[/url]
[LIST]
[*]SD card fixed (thanks [user=5300098]@Speedo.thc[/user] (as my builder wont work for some reason))
[*]Compression -> Magisk should work
[/LIST]
T1mb3 said:
I present to you, LineageOS 14.1, brought to you by me and @surdu_petru, @spirtix, @papsi177, @speedo.thc, @haky86 and @nexolight & @AD2072
Note:
Code:
/*
I am not responsible for fried or bricked devices.
This ROM is in testing stages. If you point the finger of blame at me for messing up your device, I will laugh at you. (Maybe I will try to help)
*/
What works:
It boots
Screen recording
Ok performace
What does not work:
RIL
Camera
Many other things
Today I will upload images to test this. Not in stage to be a daily driver. No ETA.
I will first try to fix RIL. Soon I hope I have more time
Downloads:
Version 1: https://mega.nz/fm/lPQmGaaD (uploaded in max. 1h)
I have not actually tried this
There is some update on trying to fix ril, so report if it works (is SIM detected)
XDA:DevDB Information
LineageOS 14.1 gra_l09, ROM for the Huawei P8
Contributors
T1mb3, surdu_petru, spirtix, papsi177, speedo.thc, haky86
Source Code: https://github.com/T1mpp4/android_device_huawei_hwgra
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Testing
Created 2018-04-18
Last Updated 2018-04-18
Click to expand...
Click to collapse
there is no files in mega
...
Click to expand...
Click to collapse
I hope you read the posts I write
Edit:
Now it's done uploading
T1mb3 said:
Some RIL log:...
No other errors but this:
Code:
04-07 05:29:53.714 3061 3061 I RILD : rild_main: i: ClientId=1, argv rilLibPath=(null)
Click to expand...
Click to collapse
From what I can see from the log is that the path libpath is read from the file system..prop AFTER the line where rilLibPath=(null).
rild_main: o: read prop rild.libpath1, result=30, value=/system/lib64/libbalong-ril.so
AND
rild_main: o: read prop rild.libpath2, result=32, value=/system/lib64/libbalong-ril-1.so
So that should be fine.
Small note.
system.prop at Line 123: rild.libargs=-mmodem0
But is then redefined at line 259. rild.libargs=-m modem0
Did you try to give permissions to files, such as the modem, rild?
T1mb3 said:
I present to you, LineageOS 14.1, brought to you by me and @surdu_petru, @spirtix, @papsi177, @Speedo.thc, @haky86 and @nexolight & @ad2072
Note:
What works:
It boots
Screen recording
Ok performace
Much more
What does not work:
RIL
Camera
Many other things
Today I will upload images to test this. Not in stage to be a daily driver. No ETA.
I will first try to fix RIL. Soon I hope I have more time
Downloads:
Version 1: https://mega.nz/#F!FCoAiYSK!VhITf9I5K46e1MnrQ74lZQ (uploaded in max. 1h)
I have not actually tried this
There is some update on trying to fix ril, so report if it works (is SIM detected)
XDA:DevDB Information
LineageOS 14.1 gra_l09, ROM for the Huawei P8
Contributors
T1mb3, surdu_petru, spirtix, papsi177, speedo.thc, haky86
Source Code:https://github.com/T1mpp4/android_device_huawei_hwgra
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Testing
Created 2018-04-18
Last Updated 2018-04-18
Click to expand...
Click to collapse
Thanks thats you wrome me in "thanks"
Sent from my HWPLK using XDA Labs
T1mb3 said:
I present to you, LineageOS 14.1, brought to you by me and @surdu_petru, @spirtix, @papsi177, @Speedo.thc, @haky86 and @nexolight & @ad2072
Note:
Code:
/*
I am not responsible for fried or bricked devices.
This ROM is in testing stages. If you point the finger of blame at me for messing up your device, I will laugh at you. (Maybe I will try to help)
*/
What works:
It boots
Screen recording
Ok performace
Much more
What does not work:
RIL
Camera
Many other things
Today I will upload images to test this. Not in stage to be a daily driver. No ETA.
I will first try to fix RIL. Soon I hope I have more time
Downloads:
Version 1: https://mega.nz/#F!FCoAiYSK!VhITf9I5K46e1MnrQ74lZQ (uploaded in max. 1h)
I have not actually tried this
There is some update on trying to fix ril, so report if it works (is SIM detected)
XDA:DevDB Information
LineageOS 14.1 gra_l09, ROM for the Huawei P8
Contributors
T1mb3, surdu_petru, spirtix, papsi177, speedo.thc, haky86
Source Code: [url]https://github.com/T1mpp4/android_device_huawei_hwgra[/URL]
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Testing
Created 2018-04-18
Last Updated 2018-04-18
Click to expand...
Click to collapse
nice work thank you very much
waiting for fixing camera issue and wifi ...
@papsi177
Hey! Do you mind sharing how you have fixed the video playback issue on CM/LOS 13 for Honor 7?
erayrafet said:
@papsi177
Hey! Do you mind sharing how you have fixed the video playback issue on CM/LOS 13 for Honor 7?
Click to expand...
Click to collapse
I think that this is the fix https://github.com/papsi177/Honor_7_framework_av/commit/255091c935a1505351d5186d3747adf1918efbf2
We use LOS stock codecs instead of Huawei proprietary codecs, I will try to implement them to the source, but firstly we need to fix camera, sensors, GPS etc...
spirtix said:
I think that this is the fix https://github.com/papsi177/Honor_7_framework_av/commit/255091c935a1505351d5186d3747adf1918efbf2
We use LOS stock codecs instead of Huawei proprietary codecs, I will try to implement them to the source, but firstly we need to fix camera, sensors, GPS etc...
Click to expand...
Click to collapse
There isn't a Huawei phone with Hisilicon chipset on AOSP based ROMs that can play [email protected] videos, because they use software decoders from Google. Only @papsi177 seems to have been able to fix hardware decoding.
zeadope said:
From what I can see from the log is that the path libpath is read from the file system..prop AFTER the line where rilLibPath=(null).
rild_main: o: read prop rild.libpath1, result=30, value=/system/lib64/libbalong-ril.so
AND
rild_main: o: read prop rild.libpath2, result=32, value=/system/lib64/libbalong-ril-1.so
So that should be fine.
Small note.
system.prop at Line 123: rild.libargs=-mmodem0
But is then redefined at line 259. rild.libargs=-m modem0
Did you try to give permissions to files, such as the modem, rild?
Click to expand...
Click to collapse
I removed the doubles.
This is from the environment:
https://android.googlesource.com/platform/hardware/ril/+/master/rild/rild.c#97
But in nougat that does not exist: https://android.googlesource.com/platform/hardware/ril/+/nougat-mr2.3-release/rild/rild.c
Anyways, the prop is set in system.prop https://github.com/T1mpp4/android_device_huawei_hwgra/blob/lineage-14.1/system.prop#L249
I have a feeling that the service ril-daemon is still not started. I will now try to start it somehow and see
T1mb3 said:
I removed the doubles.
This is from the environment:
https://android.googlesource.com/platform/hardware/ril/+/master/rild/rild.c#97
But in nougat that does not exist: https://android.googlesource.com/platform/hardware/ril/+/nougat-mr2.3-release/rild/rild.c
Anyways, the prop is set in system.prop https://github.com/T1mpp4/android_device_huawei_hwgra/blob/lineage-14.1/system.prop#L249
I have a feeling that the service ril-daemon is still not started. I will now try to start it somehow and see
Click to expand...
Click to collapse
Do you start everything correctly as I do here https://github.com/Spirtix/android_...ob/master/rootdir/etc/vendor.init.platform.rc and here https://github.com/Spirtix/android_device_huawei_HWPLK/blob/master/rootdir/etc/vendor.init.hisi.rc ?
Do you have right proprietary files?
spirtix said:
Do you start everything correctly as I do here https://github.com/Spirtix/android_...ob/master/rootdir/etc/vendor.init.platform.rc and here https://github.com/Spirtix/android_device_huawei_HWPLK/blob/master/rootdir/etc/vendor.init.hisi.rc ?
Do you have right proprietary files?
Click to expand...
Click to collapse
For the proprietary files I think I have them all: https://github.com/T1mpp4/android_vendor_huawei_hwgra/blob/master/hwgra-vendor.mk
I will now try with your hisi.rc and platform.rc ! I also rebuild vendor files if there is some problems
erayrafet said:
@papsi177
Hey! Do you mind sharing how you have fixed the video playback issue on CM/LOS 13 for Honor 7?
Click to expand...
Click to collapse
Well..Here is no secret. If want play HD video, you have to use hardware codecs. It must to be implemented to vendor and properly configured. All is shared long time befor. You have just take what you need Btw i dont undestand why other devs, who working on Huawei devices with huawei SoC, dont use this as well(i mean harcored codecs)
I hope this week end i finally boot my LOS14 and many questions will clear for me..
---------- Post added at 06:46 PM ---------- Previous post was at 06:32 PM ----------
T1mb3 said:
I removed the doubles.
This is from the environment:
https://android.googlesource.com/platform/hardware/ril/+/master/rild/rild.c#97
But in nougat that does not exist: https://android.googlesource.com/platform/hardware/ril/+/nougat-mr2.3-release/rild/rild.c
Anyways, the prop is set in system.prop https://github.com/T1mpp4/android_device_huawei_hwgra/blob/lineage-14.1/system.prop#L249
I have a feeling that the service ril-daemon is still not started. I will now try to start it somehow and see
Click to expand...
Click to collapse
Why?
This is the same..
https://android.googlesource.com/platform/hardware/ril/+/nougat-mr2.3-release/rild/rild.c#L146
Anyway we have to use prop files..
papsi177 said:
Well..Here is no secret. If want play HD video, you have to use hardware codecs. It must to be implemented to vendor and properly configured. All is shared long time befor. You have just take what you need Btw i dont undestand why other devs, who working on Huawei devices with huawei SoC, dont use this as well(i mean harcored codecs)
I hope this week end i finally boot my LOS14 and many questions will clear for me..
---------- Post added at 06:46 PM ---------- Previous post was at 06:32 PM ----------
Why?
This is the same..
https://android.googlesource.com/platform/hardware/ril/+/nougat-mr2.3-release/rild/rild.c#L146
Anyway we have to use prop files..
Click to expand...
Click to collapse
I will definitely implement that fix later!
Today 4 hours of working but no progress.. Maybe better luck next time
Some lines from this log: https://drive.google.com/open?id=14071ObxSfueZqljtzsb6vtYXaVoIdg3G
Code:
Action: android.intent.action.SIM_STATE_CHANGED
SubscriptionInfoUpdater: slotId: 0
SubscriptionInfoUpdater: simStatus: NOT_READY
SubscriptionInfoUpdater: Ignoring simStatus: NOT_READY
mBroadcastReceiver: action android.telephony.action.CARRIER_CONFIG_CHANGED
com.android.stk.StkAppService: onCreate()+
com.android.stk.StkAppService: simCount: 1
com.android.stk.StkAppService: slotId: 0
com.android.stk.StkAppService: onStart sim id: 0, op: 5, *****
com.android.stk.StkAppService: mStkService is: -1
Couldn't find 'rild' socket; retrying after timeout
The sim is there and the logger knows it. But then it does not find rild socket. The blob is there in it's place. I'll try with another rild (system/bin/rild) from device alice later.
T1mb3 said:
Some lines from this log: https://drive.google.com/open?id=14071ObxSfueZqljtzsb6vtYXaVoIdg3G
Code:
Action: android.intent.action.SIM_STATE_CHANGED
SubscriptionInfoUpdater: slotId: 0
SubscriptionInfoUpdater: simStatus: NOT_READY
SubscriptionInfoUpdater: Ignoring simStatus: NOT_READY
mBroadcastReceiver: action android.telephony.action.CARRIER_CONFIG_CHANGED
com.android.stk.StkAppService: onCreate()+
com.android.stk.StkAppService: simCount: 1
com.android.stk.StkAppService: slotId: 0
com.android.stk.StkAppService: onStart sim id: 0, op: 5, *****
com.android.stk.StkAppService: mStkService is: -1
Couldn't find 'rild' socket; retrying after timeout
The sim is there and the logger knows it. But then it does not find rild socket. The blob is there in it's place. I'll try with another rild (system/bin/rild) from device alice later.
Click to expand...
Click to collapse
Hi , i've send you a PM with my files for rild.
it works fine for simcard but no sound at all (tested on H7)
Speedo.thc said:
The sim is there and the logger knows it. But then it does not find rild socket. The blob is there in it's place. I'll try with another rild (system/bin/rild) from device alice later.
Hi , i've send you a PM with my files for rild.
it works fine for simcard but no sound at all (tested on H7)
Click to expand...
Click to collapse
Again, thanks!:highfive:
I will test on sunday
So it turns out that the issue was in kernel. It is now fixed! All credits for @Speedo.thc !!
This same fix also fixed wifi (and did not disable sound)
Now looking at camera issue:
I see that nexolight had earlier the same kind of issue here: https://github.com/CM-Huawei-P8-Development/device_gra_l09/issues/2
I looked at her fix and added some blobs and get this in log:
CANNOT LINK EXECUTABLE "/system/bin/mediaserver": cannot locate symbol "_ZNK7android14ICameraService22getInterfaceDescriptorEv" referenced by "/system/lib/libcameraservice.so"...
If someone knows a fix, tell. I'm done for today but tomorrow I will look at it more. Maybe just something simple like this shim: https://github.com/Spirtix/android_device_huawei_HWPLK/blob/lineage-14.1/shim_libs/camera.cpp
Looking at sensors also quickly:
SensorService: couldn't load sensors module (No such file or directory)
I will now upload latest to mega: https://mega.nz/#F!pf5TTJYI!vISWqwBm3BfBW9uRD-K87A
Full log: https://drive.google.com/open?id=1AwRQ7cJIOQQZcN-oN7Pzup8fFtI0eyfs
{
"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"
}
PixelExperience for Xiaomi Redmi 4A[rolex]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Lights
Sound / vibration
Facelock
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from my Google Drive
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 9.0.0
Security patch level: December 2019
Build author/Device Maintainer: dandyfarid
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
Pixel Experience, ROM for the Xiaomi Redmi 4A
Contributors
dandyfarid,sunnyraj84348,muralivijay
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x. Pie
ROM Kernel: Linux 3.18.
ROM Firmware Required: V10.2.3.0.NCCMIXM
TWRP Required: here
Based On: AOSP
Version Information
Status: Stable
Created: 10/04/2019
Last Updated: 12/12/2019
Changelog: 10/04/2019
- Enable bootanimation Half res
- Add Custom Hotplug folder
- Add Alucard Hotplug
- Add Thunderplug Hotplug
- Correct blobs entry
- Set Zram 1 GB
- arm64: Cortex-A53/ARMv8 optimizations for msm8917/20/37/40/52/53/sdm450
- prima: Merge tag 'LA.UM.7.6.r1-04300-89xx.0
- Merge tag 'LA.UM.7.6.r1-04300-89xx.0
- rolex_defconfig: update config
- rolex_defconfig: disable VGA_ARB
- staging: prima: Correct the ini value to enable default sap interface
- msm: kgsl: Remove POPP
- Enable Simple GPU Algorithm
- Enable State Notifier
- Enable Adreno Idler
- Enable KCAL color control
- Merge Tag v3.18.138 [EOL] from kernel.org
- Enable Wireguard
- Enable PowerSuspend driver
- Add Nightmare Governor
- Add DanceDance Governor
- Add Intelliactive Governor
Coba dulu
bokirganteng said:
Coba dulu
Click to expand...
Click to collapse
ok
Does adoptable storage work on this ROM? (It works!) Also why does it say This edition will no longer receive updates. on the Pixel Exp site?
MaxisMan said:
Does adoptable storage work on this ROM? (It works!) Also why does it say This edition will no longer receive updates. on the Pixel Exp site?
Click to expand...
Click to collapse
"This edition will no longer receive updates". ignore it this i m already updated CAF version
I can't get any Notification, it shuts down my apps after a while.
Seems that this ROM working pretty good.
foomanchoo said:
I can't get any Notification, it shuts down my apps after a while.
Click to expand...
Click to collapse
what apps ?
Changelog 13-04-2019
- Rebased new tree ( Thanks to sunnyraj84348 )
- power: Kill "Failed to acquire lock" log
- Selinux Still permisive
- Use Stock Kernel ( No features in kernel now )
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in kernel
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in Media HAL
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in Display HAL
Clean Flash Highly recomended !!!
dandyfarid said:
Changelog 13-04-2019
- Rebased new tree ( Thanks to sunnyraj84348 )
- power: Kill "Failed to acquire lock" log
- Selinux Still permisive
- Use Stock Kernel ( No features in kernel now )
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in kernel
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in Media HAL
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in Display HAL
Clean Flash Highly recomended !!!
Click to expand...
Click to collapse
Clean flash? ?
allboyz said:
Clean flash? ?
Click to expand...
Click to collapse
yup wipe data,cache,dalvik,system,vendor
dandyfarid said:
Changelog 13-04-2019
- Rebased new tree ( Thanks to sunnyraj84348 )
- power: Kill "Failed to acquire lock" log
- Selinux Still permisive
- Use Stock Kernel ( No features in kernel now )
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in kernel
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in Media HAL
- Merge tag 'LA.UM.7.5.r1-04500-8x96.0' in Display HAL
Clean Flash Highly recomended !!!
Click to expand...
Click to collapse
Data loss?
allboyz said:
Data loss?
Click to expand...
Click to collapse
yeah
dandyfarid said:
what apps ?
Click to expand...
Click to collapse
WhatsApp, Facebook, and almost all.
allboyz said:
Data loss?
Click to expand...
Click to collapse
You don't loss user data, just don't wipe Internal storage.
semivanya said:
You don't loss user data, just don't wipe Internal storage.
Click to expand...
Click to collapse
yup you right
Is it true that there will be no more updates?
ihor2284 said:
Is it true that there will be no more updates?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79323345&postcount=6
maintainer wrote that we should ignore this.
ihor2284 said:
Is it true that there will be no more updates?
Click to expand...
Click to collapse
ignore it
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android,which is designed to increase performance and reliability over stock Android for your device.All the source code for LineageOS is available in the LineageOS GitHub repo.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 17.1 (Unlocked Bootloader) :Xperia SP (Huashan) - Development : https://mega.nz/folder/r11xAbSL#Lwt5FOvHpV1POu_3OHU6UwGoogle Applications (optional) :OpenGApps : https://opengapps.org (Use packages for ARM, Android 10.0, pico)Information : Flash the GApps before the first boot. If not, a clean flash is recommended.Recommended Recovery (optional) :TWRP 3.5.x : http://forum.xda-developers.com/xperia-sp/orig-development/-t3309938Disable the default Low-RAM features (optional) :Low-RAM Property Patcher : http://forum.xda-developers.com/-/-t3737373Tools required for bootimage patches such as root :Boot Bridge for Sony ELF : https://forum.xda-developers.com/-/-/-t3506883Informations and references :About LineageOS updates : ChangeLog available on https://download.lineageos.org/huashan/changes/About LineageOS device side : See my GitHub trees linked below
Flashing and updating
LineageOS clean install :- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool- (Optional) Install TWRP Recovery to the FOTA partition (Read the TWRP thread)- (Optional) Wipe the data & cache (Backup to make sure not to lose data)- Flash the LineageOS ROM zip from recovery- (Optional) Flash a GApps package to have the Google Applications- (Optional) Every additional zip you want to flash- RebootLineageOS update / upgrade :- (Warning) Do not update / upgrade between OFFICIAL and UNOFFICIAL builds- (Information) Do not wipe anything unless you want to- Flash the latest LineageOS ROM zip from recovery- (Optional) Flash a GApps package on first install / upgrade. Not required later, but do update sometimes- (Optional) Every additional zip you want to flash- Reboot
About the builds
Device tree : https://github.com/LineageOS/android_device_sony_huashanKernel sources : https://github.com/LineageOS/android_kernel_sony_msm8960tDevice tree (Development) : https://github.com/AdrianDC/android_device_sony_huashanKernel sources (Development) : https://github.com/AdrianDC/android_kernel_sony_msm8960tVendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony
Issues and reports
- Report issues only if you use the ROM original kernel- If an additional mod is installed, make sure it is unrelated, and mention it- Make sure the issue was not discussed earlier in the thread- Acquire ADB logcat logs to a file : how-to-take-logs-in-android- If the device crashed and rebooted, retrieve this file from the device : /proc/last_kmsg- Use Permissive Kernel Patcher and share logcat logs if it solves issues
Legal
About LineageOS Legal : http://lineageos.org/legal/The LineageOS team would like to thank everyone involvedin helping with testing, coding, debugging & documenting! Enjoy!
LineageOS available for Xperia SP also thanks to :
- Google AOSP- The LineageOS Team- Arne (arco68)- Everyone involved in working and testing
XDA:DevDB Information
LineageOS 17.1, ROM for the Sony Xperia SP
Contributors
AdrianDC
Version Information
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
Status: Stable
ALSO WORKING ON SONY HUASHAN
Music Lights Effects implementation fully working
Presentation of the features : https://forum.xda-developers.com/showpost.php?p=73049970&postcount=399
YouTube Presentation :
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open LineageOS Recovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
FEATURES AND ISSUES
Code:
Boot : Ok
GApps : Ok (OpenGApps Pico recommended)
Partitions (Data, Cache) : Ok
Bluetooth : Ok
WiFi : Ok
WiFi Hotspot : Ok
RIL - Phone - Data : Ok
GPS : Ok
Camera : Ok
Camcorder : Ok
Lights : Ok
MicroSD : Ok
Accelerometer : Ok
Compass : Ok
Gyroscope : Ok
AOSP sensors : Ok
Touchscreen : Ok
FM Radio : Ok
Vibrator : Ok
Microphone : Ok
Audio & music : Ok
Bluetooth audio : Ok
Video playback : Ok
NFC : Ok
Kernel : Ok
Graphics : Ok
3D Rendering : Ok
Clock : Ok
DRM : Ok
Offline Charging : Ok
USB : Ok
USB OTG : Ok
Encryption : Ok
SEPolicies : Ok (Enforced)
Kernel CVE : Partially outdated (ToDo)
Root : Ok (with ADB, supported with Magisk + BootBridge)
TWRP : Ok (TWRP 3.5.0 recommended, system restore may need a ROM reflash due to a TWRP internal issue)
CHANGELOG
Code:
Future release:
- Kernel CVEs updates to check
28/12/2020:
- Update release on Security level 2020-12-05
25/10/2020:
- Update release on Security level 2020-10-05
20/09/2020:
- Upgrade release on Security level 2020-09-05 (android-10.0.0_r46 August)
- Back gesture navigation with keyboard swipe conflicts resolved (topic:ten-back-gesture-go)
30/08/2020:
- Multiple kernel optimizations and debugging features cleanups (thanks Tomoms)
- Previously patched SEPolicies included and now considered stable
27/08/2020:
- Patch regarding SEPolicies for FM Radio support (extends the 26/08/2020 patch)
26/08/2020:
- Patch regarding SEPolicies for FM Radio support and sensors detection
23/08/2020:
- Migration to userspace Low Memory Killer daemon (LMKD) instead of the old kernel LMK
- Massive kernel updates against upstream, especially LZ4 and ZRAM (257 commits)
- Additional SEPolicies updates
20/08/2020:
- Updates to enforced SEPolicies
- Actionbar previous button in DeviceSettings fixed
- High Touch Sensitivity (Glove mode) reimplemented in display settings
19/08/2020:
- Enforced SEPolicies security with all rules refactored and cleaned up,
if anything looks "blocked", please report with ADB logs
16/08/2020:
- GPS legacy support fixed
15/08/2020:
- Video playback fixed
- ZRAM 768MB reenabled
- Bootimage support for Magisk
- RIL updates
- Minor lights selection fix
13/08/2020:
- Initial public release on Android 10.0.0_r41 June
11/08/2020:
- Initial beta testers release on Android 10.0.0_r41 June
2019 - 2020:
- Initial AOSP 10 / LineageOS 17.0 / 17.1 ports
- Internal bringup
The next release will resolve these :
Video playback : Due to Android 10 newer codecs, recorded videos now play properly
Boot : The bootimage will support Magisk as the current one does not
Notifications : Minor fix on lights selection (https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/283994)
Great work as usual @AdrianDC . Got featured on XDA portal. Even though I've not had this device for a couple of years now, I'm still subscribed to this device forum just because of the work you put into it when I had it. :good:
Totally wasn't expecting this to happen !
Definitely need to check it out.
I'm still using my XSP as a daily phone
Woow this great!!
OMG ...
Thank you AdrianDC for keeping this device alive in 2020
This phone is still my daily driver
I remember asking you if you'd ever stop, to which you replied "never".
Long live the king.
A new release 19/08/2020 is available :
Enforced SEPolicies security with all rules refactored and cleaned up (if anything looks "blocked", please report with ADB logs)
Huashan should be fine, everything looks to be working fine right now with the enforced security.
Please PM me ADB logs if you see anything not working / behaving as it should and explain what you did.
Hi AdrianDC,
first of all a BIG THANK YOU for putting so much effort in bringing LOS 17.1 to our good old huashan. I'm still running several devices and really appreciate to have LOS 17.1 on them. now..
Overall, it looks / runs really really good - so: :good: THUMBS UP :good:
One little thing I noticed: The upper left "back arrow" of the "Lights effects" settings menu does not work (which did on LOS 16.0) ... only standard android back button functionality does. I'll try to grab some logs, but maybe you can reproduce it yourself..
But again: Thank you for all the work you put into LOS 17.1 for huashan
NyQuilXT
NyQuilXT said:
One little thing I noticed: The upper left "back arrow" of the "Lights effects" settings menu does not work (which did on LOS 16.0) ... only standard android back button functionality does. I'll try to grab some logs, but maybe you can reproduce it yourself..
Click to expand...
Click to collapse
You're correct, it broke due to the refactoring of our DeviceSettings against Android 10 changes.
The back feature was not handled by the new activity.
Please try this patch on top of the latest release and let me know if it's fine for you too.
AdrianDC said:
You're correct, it broke due to the refactoring of our DeviceSettings against Android 10 changes.
The back feature was not handled by the new activity.
Please try this patch on top of the latest release and let me know if it's fine for you too.
Click to expand...
Click to collapse
Yep, it's working now! Thanks a lot!
NyQuilXT said:
Yep, it's working now! Thanks a lot!
Click to expand...
Click to collapse
Good news.
This also made me notice Huashan was missing it's LineageOS High Touch Sensitivity option in displays,
(my DeviceSettings specific Glove setting activity was meant only for AOSP support, the service is common though),
this is now reimplemented for LineageOS and will be there in the next release.
A new release 23/08/2020 is available, on my side, the performance and normal usage have improved a lot :
Migration to userspace Low Memory Killer daemon (LMKD) instead of the old kernel LMK
Massive kernel updates against upstream, especially LZ4 and ZRAM (257 commits)
Additional SEPolicies updates
After some testing, i must say: this release really kicks ass! I'm really amazed, how fast my devices now performs...Even the one, which suffers the "write amplification effect", is running much better now. Adrian, you are sooo awesome! I'm deeply impressed by the effort, you put into the development for this device! I cannot say that often enough!!!
Wow, I did not expect to find a 17.1 build for a device that old.
Good job!
As I'm using my Xperia SP basically 99% just as a backup for my 2FAs and stock-ROM does not support Google Authenticator 5.10 which introduced the "Transfer codes"-function, I'm very much looking forward to update.
But as I run into troubles with the camera-support of 17.1 on my Samsung Galaxy Tab 4 (bad resolution, couldn't read the big QR-Code) I want to shoot up a question before doing so:
Is the camera-support good enough to read complex/big QR-Codes?
Thanks in advance for any report on one's experiences!
Aequita
After running the 20.08 and 23.08 builds for a bit i must say that they feel realy nice in daily usage
I've stumbled on a few minor things comparing to lineageOS 15,1 from which i updated:
- FM radio doesn't work, it displays a toast saying "currently unavailable" (log fragment from pressing play button below)
Code:
08-25 18:25:40.922 4384 4409 I android_hardware_fm: TurnOn, [freq=100]
08-25 18:25:40.922 4384 4409 I android_hardware_fm: Pwr_Up,[freq=100000]
08-25 18:25:40.922 4384 4409 D android_hardware_fm: BT soc is ''
08-25 18:25:40.922 4384 4409 D android_hardware_fm: open_dev, [fd=59]
08-25 18:25:40.922 4384 4409 D android_hardware_fm: Pwr_Up: cur_fm_state = 0
08-25 18:25:40.922 4384 4409 I android_hardware_fm: start_fm_patch_dl: start_fm_patch_dl = 59
08-25 18:25:40.922 4384 4409 D android_hardware_fm: start_fm_patch_dl: executed cmd
08-25 18:25:40.925 4384 4409 D android_hardware_fm: set versionStr done
08-25 18:25:40.927 4384 4409 D android_hardware_fm: set FM_MODE_PROP done
08-25 18:25:40.933 4384 4409 D android_hardware_fm: set FM_INIT_PROP done
08-25 18:25:41.042 4465 4465 I qcom-fm : /system/etc/init.qcom.fm.sh: In FM shell Script
08-25 18:25:41.092 4466 4466 I qcom-fm : /system/etc/init.qcom.fm.sh: mode: normal
08-25 18:25:41.120 4467 4467 I qcom-fm : /system/etc/init.qcom.fm.sh: Version : 199217
08-25 18:25:41.168 4468 4468 I qcom-fm : /system/etc/init.qcom.fm.sh: inserting the radio transport module
08-25 18:25:41.194 4469 4469 E libc : Access denied finding property "ro.qualcomm.bt.hci_transport"
08-25 18:25:41.175 4469 4469 W fm_qsoc_patches: type=1400 audit(0.0:18): avc: denied { read } for name="u:object_r:bluetooth_prop:s0" dev="tmpfs" ino=6774 scontext=u:r:fm_dl:s0 tcontext=u:object_r:bluetooth_prop:s0 tclass=file permissive=0
08-25 18:25:41.223 4470 4470 E qcom-fm : /system/etc/init.qcom.fm.sh: FM QSoC firmware download and/or calibration failed: exit code 255
08-25 18:25:49.071 884 884 D ServiceStateProvider: subId=1
08-25 18:25:49.078 506 791 D AlarmManagerService: Kernel timezone updated to -120 minutes west of GMT
08-25 18:25:49.082 2248 2248 D CellBroadcastReceiver: onReceive Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 cmp=com.android.cellbroadcastreceiver/.CellBroadcastReceiver (has extras) }
08-25 18:25:49.990 4384 4409 E android_hardware_fm: FM patch downloader failed: -1
08-25 18:25:49.990 4384 4409 D android_hardware_fm: close_dev, [fd=-1] [ret=0]
08-25 18:25:49.990 4384 4409 D android_hardware_fm: TurnOn, [ret=-1]
08-25 18:25:49.993 4384 4384 D FmMainActivity: mHandler.handleMessage, what = 9,hashcode:150427765
08-25 18:25:49.993 4384 4384 D FmMainActivity: refreshStationUI, set station value null when it is first time
08-25 18:25:50.088 4384 4404 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
08-25 18:25:52.032 506 791 W NotificationService: Toast already killed. pkg=com.android.fmradio [email protected]
- it seems that the screen on/off animation is missing. There was a post in earlier lineageOS thread with details how to enable it, but i cant fing it
A major thing may be connected to phone deep sleep - i've had a situation after enabling the alarm, that it would ring only after lighting the screen up with power button. I will investigate this further as it does not happen every time.
Thanks again for the updates !
Aequita said:
Wow, I did not expect to find a 17.1 build for a device that old.
Good job!
As I'm using my Xperia SP basically 99% just as a backup for my 2FAs and stock-ROM does not support Google Authenticator 5.10 which introduced the "Transfer codes"-function, I'm very much looking forward to update.
But as I run into troubles with the camera-support of 17.1 on my Samsung Galaxy Tab 4 (bad resolution, couldn't read the big QR-Code) I want to shoot up a question before doing so:
Is the camera-support good enough to read complex/big QR-Codes?
Thanks in advance for any report on one's experiences!
Aequita
Click to expand...
Click to collapse
I can scan simple or comple QR-Code properly here, can't tell much more though.
Jadimo said:
After running the 20.08 and 23.08 builds for a bit i must say that they feel realy nice in daily usage
I've stumbled on a few minor things comparing to lineageOS 15,1 from which i updated:
- FM radio doesn't work, it displays a toast saying "currently unavailable" (log fragment from pressing play button below)
- it seems that the screen on/off animation is missing. There was a post in earlier lineageOS thread with details how to enable it, but i cant fing it
A major thing may be connected to phone deep sleep - i've had a situation after enabling the alarm, that it would ring only after lighting the screen up with power button. I will investigate this further as it does not happen every time.
Thanks again for the updates !
Click to expand...
Click to collapse
Thanks for the report, FM Radio is now resolved with an incremental patch release for the 23/08/2020 release.
Patch regarding SEPolicies for FM Radio support and sensors detection
Regarding the screen on / off animations, this is due to the Android Go (Low RAM) configurations,
if you want to restore the related features with a bit of performance losses, look at my "Low-RAM Property Patcher" linked in the OP.
AdrianDC said:
I can scan simple or comple QR-Code properly here, can't tell much more though.
Thanks for the report, FM Radio is now resolved with an incremental patch release for the 23/08/2020 release.
Patch regarding SEPolicies for FM Radio support and sensors detection
Regarding the screen on / off animations, this is due to the Android Go (Low RAM) configurations,
if you want to restore the related features with a bit of performance losses, look at my "Low-RAM Property Patcher" linked in the OP.
Click to expand...
Click to collapse
Well, today I am surprised with this version that I never imagined that it would come out, I am using the 16 I will try to see how it goes with this on my old xperia sp
{
"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"
}
" #DroidOnTime "
ROM Version: 5.1.3
Device: polaris
Build Status: UNOFFICIAL
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration.."
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
CLEAN FLASH/First Time Installation :
Clean flash required if coming from from android 10!
- Install the latest custom recovery (either twrp or orangefox)
- Format data
- After formatting data, you may have to reboot again to recovery
- Wipe system & data & cache & dalvik cache
- Install ROM and GAPPS
- Reboot
DotOS Vanilla https://mega.nz/file/5A1XzYQD#AKwaj0kWV8fB6hrBd-uOEUIvoPjl4e_RgUc-At8VLyk
DotOS GAPPS https://mega.nz/file/wV12ARCQ#Kh3I8tQ_tAiVFK3Fp83rEv4NduIHjzNHiRQF0ylOwDk
Complete Changelogs: https://changelogs.droidontime.com/
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
And all other open-source Devs/Teams.
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Sipun Kumar - Developer/Maintainer
Special thanks:
Manish Bajpai - Web Developer
Important Links
If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM
Contributors: * Mohan C M *
Source Code: https://github.com/DotOS
Kernel Source: - https://github.com/PixelExperience-Devices/kernel_xiaomi_polaris
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.1.3
Stable Release Date: 22-08-2021
Changelogs
2021-08-22 DotOS 5.1.3
August - dotOS v5.1.3 Release
dotOS 5.1.3 August release - August Security patches, fixes, Stability and much more
blog.droidontime.com
2021-07-21 DotOS 5.1.2
https://blog.droidontime.com/blog/july-release-2021
2021-06-14 DotOS 5.1.1
Rom changelog:
June - dotOS v5.1.1 hotfix Release
dotOS 5.1.1 hotfix release - June Security patches, fixes, Stability and much more
blog.droidontime.com
Device changelog (man thanks to Scherzo for his trees and kernel)
- Etude kernel: Op.11 No.5
* Linux 4.9.272
* CAF tag LA.UM.9.3.r1-02100-sdm845.0
* ported UFS health sysfs node from crosshatch
* enabled DualSense controller driver which includes support for the latest PlayStation 5 controller
* security hardening backport: Clang's zero initialization of stack variables
* set cortex a-75 as target for architecture-specific optimizations
* enabled RELR relocation and reduced kernel binary size slightly
* enabled Clang's -Wtautological-compare and fixed lots of incorrect checks in qcom's code
* used proper null pointer checks across the kernel tree
* synaptics and ft5x46 touchscreen: switched to qcom drm notifier
* ft5x46 touchscreen: use pm_qos_request to reduce input latency in irq handler
* moved kgsl_3d_init to async probe
* validate dsi command size before sending command
* silenced a harmless error log in qpnp-smb2
* wireguard: 1.0.20210606
* some upstream improvements of lz4
* DO NOT use a third party kernel without proper support for Pixel thermal hal
- Fixed the initialization of zram backing device and cleaned up the init script
- Added a property for libperfmgr's powerhint file name
- Reduced the default GPU idle timer to 70ms in powerhint
* this aligns with the kernel default value after ms-to-jiffies conversion
- Dropped some duplicated or non-existent init code
2021-05-31 DotOS 5.1
Initial build
May - dotOS v5.1 Mega Release
dotOS 5.1 release - May Security patches, New UI, FaceUnlock, Applock and much more
blog.droidontime.com
Seems good!! I will try!! Thanks
Will there be a plan for the official version in the future?
acc274 said:
Will there be a plan for the official version in the future?
Click to expand...
Click to collapse
Probably not anytime soon. I don't really see any advantage from making it official.
DotOS 5.1.1 14.06.2021 Unofficial
Rom changelog:
June - dotOS v5.1.1 hotfix Release
dotOS 5.1.1 hotfix release - June Security patches, fixes, Stability and much more
blog.droidontime.com
Device changelog (man thanks to Scherzo for his trees and kernel)
- Etude kernel: Op.11 No.5
* Linux 4.9.272
* CAF tag LA.UM.9.3.r1-02100-sdm845.0
* ported UFS health sysfs node from crosshatch
* enabled DualSense controller driver which includes support for the latest PlayStation 5 controller
* security hardening backport: Clang's zero initialization of stack variables
* set cortex a-75 as target for architecture-specific optimizations
* enabled RELR relocation and reduced kernel binary size slightly
* enabled Clang's -Wtautological-compare and fixed lots of incorrect checks in qcom's code
* used proper null pointer checks across the kernel tree
* synaptics and ft5x46 touchscreen: switched to qcom drm notifier
* ft5x46 touchscreen: use pm_qos_request to reduce input latency in irq handler
* moved kgsl_3d_init to async probe
* validate dsi command size before sending command
* silenced a harmless error log in qpnp-smb2
* wireguard: 1.0.20210606
* some upstream improvements of lz4
* DO NOT use a third party kernel without proper support for Pixel thermal hal
- Fixed the initialization of zram backing device and cleaned up the init script
- Added a property for libperfmgr's powerhint file name
- Reduced the default GPU idle timer to 70ms in powerhint
* this aligns with the kernel default value after ms-to-jiffies conversion
- Dropped some duplicated or non-existent init code
* DO NOT use a third party kernel without proper support for Pixel thermal hal
Dirty flash from previous build is fine if using the vanilla build, if you want to switch to the gapps build then a clean flash is required
Clean flash guide:
- Install the latest custom recovery
- Format data
- After formatting data, you may have to reboot again to recovery
- Wipe system & data & cache & dalvik cache
- Install ROM
- Reboot
Vendor+FW included
DotOS Vanilla https://mega.nz/file/5IlkCK6R#ibocRVfBb0vmjbITbw-umO2tfrgmHhdtJeovkR7-hB4
DotOS GAPPS https://mega.nz/file/oc9yRK5A#3xDdXkNkVnuJ8FQ6lwYKQ9aCvT96qipczGkxzRzrVC8
Thanks to scherzo, dahake and Wooby for helping me
awesome!
can this dotos rom quickly switch data sim card in Status bar?
just like EVOx os
jack1995hjj said:
awesome!
can this dotos rom quickly switch data sim card in Status bar?
just like EVOx os
Click to expand...
Click to collapse
Hi. I don't have 2 Sim cards, but it looks like it has it.
cvamoose said:
Hi. I don't have 2 Sim cards, but it looks like it has it.
Click to expand...
Click to collapse
thx! I had using this rom, feeling so good!
Amazing Rom, work very fast and well.
For now the only thing I found is : is you phone is power off and you charge it you don't see any animation about the battery levels... Only black screen.
The levels of bright is not working well.
To slow in automatic change.
For gaming I tray CALLOFDUTY and work very well.
I love this ROM.
Thank you
Is this rom good as a daily driver?
BaamAlex said:
Is this rom good as a daily driver?
Click to expand...
Click to collapse
Yes, work very well .
Just the automatic brightness.
..
...
caoscorp said:
Amazing Rom, work very fast and well.
For now the only thing I found is : is you phone is power off and you charge it you don't see any animation about the battery levels... Only black screen.
The levels of bright is not working well.
To slow in automatic change.
For gaming I tray CALLOFDUTY and work very well.
I love this ROM.
Thank you
Click to expand...
Click to collapse
Thanks for the feedback, I'll look into the problem with automatic brightness and the offline charger.
Carl
I found an issue in my daily use...
after switching the dual sim cards data using, the newly using sim's data become very very slow, about 50kB/s
so I have to switch the card's APN setting to reset data's speed
In my evoX rom and officail MIUI using , I never experienced it.
I found some wrong with the app Pinterest.
All ways ask for user name and password.
Then every time that I click to see some image apen the WEB browser.
I tray to download Pinterest from differents sites and is the same issue.
. .......
Other issue is when you write to fast or move your home screen to much.
I'm getting screen LAG and some times just won't work well.
.....
I'm testing games with this Rom
CALL OF DUTY : working perfectly with high settings and MAX fps, I get my phone warm but perfect. Better than MIUI EU BETA....
PUBG : is not working well, to slow with any settings. Is impossible to play like that.
Real Racing 3 : work well, no issues.
Gear.Club : no issue
Sky : work well to.
Genshin Impact : Perfect with MEDIUM Settings.
I'm gonna continue testing.
I use more than 100 apps
Thank you, for this fast ROM.
Will be any Updates in the Future ?
Thanks ª!~
I found issue with FULL screen gestures.
Some times the gesture BACK won't work.
With any app or game.
So any update? Or something?
Thanks
I found issue
When I pull down the status bar, FPS is very low.
This problem has been bothering me all the time
dot official had been released 5.1.2,will this rom upgrade?
jack1995hjj said:
dot official had been released 5.1.2,will this rom upgrade?
Click to expand...
Click to collapse
Wait for it.
{
"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"
}
XPerience is a free, community built distribution of Android 13.0.0 which greatly extends the capabilities of your phone.
This project are based on CAF (CLO)
The XPerience Project since 2011
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NOTE: READ this PLS
Please don't ask for etas
Please don't report same bugs all time
Report with logcat and dmesg
Screenshots representative only
Don't ask to add ANX it will never be included.
Click to expand...
Click to collapse
Features:
Custom tiles
Power menu customizations (reboot to recovery one touch in advanced reboot, for bootloader do a long touch)
Bionic optimizations
3 fingers swipe take screenshot
Long press on power to enable torch
Immersive nav
Gaming optimizations
Adaptive playback
Double tap to sleep
GameSpace
DC-Dimming
Screen ON/OFF animations (CRT as default)
Full screen apps support
High touch polling rate
Icon pack
Status bar icons
system fonts
Custom battery icons
Thermal profiles
per-app volumen control
Mi sound enhacer (aka dirac, hi-fi)
Clear speaker
WORKING:
Boot
Rild
LTE
bluetooth
Camera
camcorder
MTP
Sensors
Led
Wi-Fi
MUSIC
sounds
Videos
DT2W
NFC
Bugs
[*] You tell me
Install steps:
Install orangefox 11.1
download the rom flash the rom
Format data and recreate it as F2FS for better perf also do a fix partition in ofox
Reboot and enjoy gapps included
CAF BRANCH:
LA.QSSI.13.0.r1-07400-qssi.0
AOSP branch:
android-13.0.0_r11
Source forge | Pling
Telegram Chat:
https://t.me/xperiencechat
GAPPS:
Not needed. included
The XPerience Project
Contributors
TeamMex
Source Code (device tree and kernel in the git):
https://github.com/TheXPerienceProject
ROM OS Version: Android 13
ROM Kernel: Linux 4.19
ROM Firmware Required: Unlocked Bootloader
Based On: CAF (CLO)
Version Information
Status: NIGHTLY
Changes in second post
Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
XPerience version:
Download url:
Did you--
wipe:
restore with titanium backup or swift backup (Say which):
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel(only yuki kernel is supported):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Also add a LOGCAT DMESG if required
logcat in formated version
adb shell logcat > log.txt for example
If you like my work, you can buy me a coffee , coke or any drink all donations are appreciated.
Ór
https://www.paypal.me/TheXPerienceProject
Changelog
2023/05/18
System: Fixed Auto-Brightness issues
System: Merge tag 'LA.UM.9.14.r1-21600-LAHAINA.QSSI14.0'
System: Merge tag 'LA.QSSI.13.0.r1-10000-qssi.0'
System: SF: Scheduler: vote max for NOTIFICATION_SHADE
System: Bluetooth fixes
System: Animate auto brightness toggle
System: enable UMO_SURFACE_RIPPLE
System: Avoid cast exceptions
System: SystemUI: Add support for black theme
System: Introduce bypassEnabledBiometric on faceunlock
2023/05/09
System: Merge LA.QSSI.13.0.r1-09900-qssi.0
System: lavender: use LZ4 ramdisk
System: lavender: remove dynamic attributes from APS config
System: enforcing! safetynet pass by default
System: lavender: Enable AUX cameras on aperture
System: lavendererf: Disable multiple kswapd threads
System: update yuki kernel
System: SF: Scheduler: vote max for NOTIFICATION_SHADE
System: SystemUI: Add support for black theme
System: Introduce bypassEnabledBiometric on faceunlock
2023/05/02
System: Merge LA.QSSI.13.0.r1-09800-qssi.0
System: Merge Android QPR2
System: dropped edge light
System: dropped firewall status bar indicator
System: Revert to jemalloc
System: dropped hotspot toggle in QS internet dialog
System: Transparent QS customization
System: Blur the power menu
System: Updated google apps to april
System: Forward-port notification counters
System: removed option to disable volte
System: Update translations
2023/04/15
Initial public release
4.19 Kernel rom (dont change the kernel cuz can cause issues)
reserved
I am considering this rom? How good is it compared to other android 13 roms?
What does it mean in the install guide? "also do a fix partition"
drdagi said:
What does it mean in the install guide? "also do a fix partition"
Click to expand...
Click to collapse
Ofox can break F2FS partitions in weird stages and rom cant boot thats why at 1st installation is needed then every update not need to do that
i'll test this rom, i will report any issue if found
Bluetooth is not working...
Minnakin said:
Bluetooth is not working...
Click to expand...
Click to collapse
It Works fine
Code:
* Xperience Version: URL=https://sourceforge.net/projects/xperience-aosp/files/lavender/17/nightly/xperience-17.1.0-20230502-NIGHTLY-lavender.zip/download
* Wipe: yes as told in the installation steps
* Clean intall with magisk 26.1 root with safetynet fix modules.
* Other modifications: root booster pro ultra performance mode
logcat: https://www.mediafire.com/file/26t3spsrko0r7t9/logcat.txt/file
Bluetooth is not working for me too, more info above, it just won't turn on
will try a clean install with no root to see if i will fix that
Citrixbun said:
Bluetooth is not working for me too, it just won't turn on
Click to expand...
Click to collapse
my problem is the same bluetooth is not opening
Citrixbun said:
will try a clean install with no root to see if i will fix that
Click to expand...
Click to collapse
yeah, tried with a super clean install no root no anything and still the same issue for me, it´s a shame because this is the best performing room for quad touch and delta touch
Tried this ROM out and I really like it. Description says that SELinux is set to permissive but that seems to have been fixed. I find it really impressive that this ROM actually uses kernel version 4.19 (most ROMs use 4.4 for this device). That must have took a lot of work to make possible. Would highly recommend!
can you tell me how to do "recreate it as F2FS" sorry im new thx
oyabun324 said:
can you tell me how to do "recreate it as F2FS" sorry im new thx
Click to expand...
Click to collapse
in Ofox go to menu->]Manage partitions -> data tap in the orange button and repair FS
Sadly that i can't use my sdcard as internal storage hopefully you can add it in future.