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 have Modded DSPManager to use the libs & Audio files from BEATS to work with AOKP & CM9 ONLY!!!
Flashing this will not mess up your other Equalizers!!
V.1
Had a bunch of FC for alot of devices
v.2
Fixed the FC issue
v.3
Added MUSICFX so settings work for CM9
Added Awesome Control Panel
Re-built Awesome BEATS
Download: AwesomeBEATS™ v.3
Just FLASH and enjoy!!
Make sure to change in SETTINGS/SOUND/MUSIC EFFECTS to AWESOME BEATS.
Thanks to:
spc_hicks09 (with Permission to use his modded DSP manager)
Sckyboy78 (For the find )
nik3r (For all the help getting it to work on other devices)
mwalt2 (Helping fix the MOD to work on CM9 based Roms)
Confirmed Devices working:
MyTouch 4G
Desire HD
Desire S
Inspire 4G
Desire
GalaxyTab Plus
Sensation
Amaze 4G
Galaxy S2
Nexus
SSII
SI
Sensation XL
Donations Received:
*Dgardner425
*La_Blu_Eyez
*Tornado234
*WhiteMambaB
*Fabio Battisti
*Chris Miller
*Mike Cruz
*Liz AguilarMAKE SURE YOU GUYS HIT THAT THANK BUTTON IF THIS MOD WORKED FOR YOU!!!
Awesome I have been looking for something like this for a long time
(Need nandroid first I'm in a middle of testing something)
nik3r said:
Awesome I have been looking for something like this for a long time
Click to expand...
Click to collapse
Test and report plz and repost what rom your on thanks.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
Can it work with aokp b39?
Sent from my Desire Z using XDA
Steven How said:
Can it work with aokp b39?
Sent from my Desire Z using XDA
Click to expand...
Click to collapse
Test it! Worked fine on my end and report back thanks.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
Testing...
Flash ... OK
Boot ... OK
Settings - Sound - Effects entry ... OK
Switched engine ... OK
Control app ... FAILED
Rebooting for second try ...
...
...
Engine persisted ... OK
Control app ... FAILED
It FC's on me and I don't hear a difference, sorry
nik3r said:
Testing...
Flash ... OK
Boot ... OK
Settings - Sound - Effects entry ... OK
Switched engine ... OK
Control app ... FAILED
Rebooting for second try ...
...
...
Engine persisted ... OK
Control app ... FAILED
It FC's on me and I don't hear a difference, sorry
Click to expand...
Click to collapse
What rom so I can flash it and test thanks.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
EliteMod (= basically AOKPb39 + EliteKernel)
confirmed that on nik3r's elitemod rom the control app does not work. It force closes everytime. exactly as described above.
LogCat
Code:
I/ActivityManager( 1421): START {act=android.intent.action.MAIN cat=[android.int
ent.category.LAUNCHER] flg=0x10200000 cmp=com.bel.android.dspmanager/.activity.D
SPManager} from pid 1950
I/ActivityManager( 1421): Start proc com.bel.android.dspmanager for activity com
.bel.android.dspmanager/.activity.DSPManager: pid=4034 uid=10043 gids={3002}
D/OpenGLRenderer( 1950): Flushing caches (mode 1)
W/AssetRedirectionManager( 1421): Unable to attach target package assets for com
.bel.android.awesome
E/dalvikvm( 4034): Dex cache directory isn't writable: /data/dalvik-cache
I/dalvikvm( 4034): Unable to open or create cache for /system/app/Awesome BEATS.
apk (/data/dalvik-cache/[email protected]@Awesome [EMAIL="[email protected]"][email protected][/EMAIL])
D/AndroidRuntime( 4034): Shutting down VM
W/dalvikvm( 4034): threadid=1: thread exiting with uncaught exception (group=0x4
0a591f8)
E/AndroidRuntime( 4034): FATAL EXCEPTION: main
E/AndroidRuntime( 4034): java.lang.RuntimeException: Unable to instantiate activ
ity ComponentInfo{com.bel.android.dspmanager/com.bel.android.dspmanager.activity
.DSPManager}: java.lang.ClassNotFoundException: com.bel.android.dspmanager.activ
ity.DSPManager
E/AndroidRuntime( 4034): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:1993)
E/AndroidRuntime( 4034): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2104)
E/AndroidRuntime( 4034): at android.app.ActivityThread.access$600(Activit
yThread.java:132)
E/AndroidRuntime( 4034): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1157)
E/AndroidRuntime( 4034): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 4034): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 4034): at android.app.ActivityThread.main(ActivityThrea
d.java:4575)
E/AndroidRuntime( 4034): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 4034): at java.lang.reflect.Method.invoke(Method.java:5
11)
E/AndroidRuntime( 4034): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 4034): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:553)
E/AndroidRuntime( 4034): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4034): Caused by: java.lang.ClassNotFoundException: com.bel.an
droid.dspmanager.activity.DSPManager
E/AndroidRuntime( 4034): at dalvik.system.BaseDexClassLoader.findClass(Ba
seDexClassLoader.java:61)
E/AndroidRuntime( 4034): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:501)
E/AndroidRuntime( 4034): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:461)
E/AndroidRuntime( 4034): at android.app.Instrumentation.newActivity(Instr
umentation.java:1023)
E/AndroidRuntime( 4034): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:1984)
E/AndroidRuntime( 4034): ... 11 more
W/ActivityManager( 1421): Force finishing activity com.bel.android.dspmanager/
.activity.DSPManager
D/OpenGLRenderer( 1950): Flushing caches (mode 0)
Should be easy to figure out.
I'll try to wipe dalvik cache for one..
EDIT: No such luck, DSP manager from CM9 was working fine.
EDIT2: Doesn't work from /data/app either
Ok i figured it out hopefully it works now please reply if you dont get the FC anymore
Instructions please make sure u deleted the AwesomeBEATS.apk first from system/apps before flashing.
Thanks guys for testing again for me.
This is what your suppose to get.
Is it just me or is there a space in that filename... linux hates that you know..
EDIT: Doesn't work either, I think this bit is the problem:
I/dalvikvm( 3312): Unable to open or create cache for /system/app/Awesome BEATS.apk (/data/dalvik-cache/[email protected]@Awesome [email protected])
There's a space in that dex class filename, I don't think that's allowed
Renamed the apk file and trying to regenerate dalvik cache.
---------- Post added at 03:07 AM ---------- Previous post was at 02:46 AM ----------
Yup got it working by renaming the apk file, but I hear no changes in sound when I move the EQ, the engine is selected and I even rebooted.
nik3r said:
Is it just me or is there a space in that filename... linux hates that you know..
EDIT: Doesn't work either, I think this bit is the problem:
I/dalvikvm( 3312): Unable to open or create cache for /system/app/Awesome BEATS.apk (/data/dalvik-cache/[email protected]@Awesome [email protected])
There's a space in that dex class filename, I don't think that's allowed
Renamed the apk file and trying to regenerate dalvik cache.
---------- Post added at 03:07 AM ---------- Previous post was at 02:46 AM ----------
Yup got it working by renaming the apk file, but I hear no changes in sound when I move the EQ, the engine is selected and I even rebooted.
Click to expand...
Click to collapse
Can you pm me the one you got working so I can look at it thanks.
Edit: What app were u using to listen to music? Apollo? Theirs a big difference with Apollo.
Edit: All you did was rename the App from Awesome Beats.apk to AwesomeBeats.apk?
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
Yup just rename it without space, the dex class is named after the apk file. Notice how nobody uses spaces in their filenames for that very reason, the convention is xx.domain.appname.apk for a reason, there's no space in URL either
I use poweramp and I disabled all internal postprocessing to hear it better.
Oh it works fine with google music. I'll see if I can get it to work with poweramp too
Yup if I disable direct volume control it works well, just takes a while to take effect, poweramp has nice large buffers
Nice work, just change the filename and here's your certificate for my ROM:
Code:
[** NIKER APPROVED **]
nik3r said:
Yup just rename it without space, the dex class is named after the apk file. Notice how nobody uses spaces in their filenames for that very reason, the convention is xx.domain.appname.apk for a reason, there's no space in URL either
I use poweramp and I disabled all internal postprocessing to hear it better.
Oh it works fine with google music. I'll see if I can get it to work with poweramp too
Yup if I disable direct volume control it works well, just takes a while to take effect, poweramp has nice large buffers
Nice work, just change the filename and here's your certificate for my ROM:
Code:
[** NIKER APPROVED **]
Click to expand...
Click to collapse
Thanks man I appreciate it! Gave u thanks in the OP!.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
So doesn't work with apollo?
XxhTcG2uSERxX said:
So doesn't work with apollo?
Click to expand...
Click to collapse
I does work with Apollo hit settings and equalizer and it will bring up the Awesome Control by default it used Apollo for your audio files.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
The preset are all 0.0+,running mimicry
XxhTcG2uSERxX said:
The preset are all 0.0+,running mimicry
Click to expand...
Click to collapse
In equalizer? I set the equalizer at 0.0 but even without the equalizer u can see a huge improvement and if u wanna add anything else thru the equalizer or use a different app like Power Amp it will now use the beats audio files.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
Oh,because in ur screenshot it has them high
poo706 presents... LIQUIDSMOOTH LOLLIPOP - UNOFFICIAL
Things to note
Same kernel as Ziyan's CM12 (EXT4 only)
F2FS supported on /data and /cache only, /system must be EXT4
For F2FS use one of the following Full_Auto kernels: R1, R4.5, R5, R6, R7, R8, R10, R10, R11
Linaro toolchains for both ROM and kernel
Liquid Optimizations
CM12 Theme Engine
Deodexed: First boot will take a long time!
Clear all recents on a regular basis to reduce lag, they survive a reboot!
Su binary is not included, install SuperSu from recovery: http://download.chainfire.eu/supersu
Use as small gapps as possible, I've had luck with the minimal edition from here: http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
2/21: http://www.mediafire.com/download/xjpv7cdiqrea6fe/LS-LP-v4.0-2015-02-21-liquid_toro.zip
Old versions:
2/14: http://www.mediafire.com/download/anrm2e7utbpi743/LS-LP-v4.0-2015-02-14-liquid_toro.zip
2/11: http://www.mediafire.com/download/spspbpcg2r9h41t/LS-LP-v4.0-2015-02-11-liquid_toro.zip
1/28: http://www.mediafire.com/download/nu9tppot8xzl9yf/LS-LP-v4.0-2015-01-28-liquid_toro.zip
1/25: http://www.mediafire.com/download/az5s82692b7pqb3/LS-LP-v4.0-2015-01-25-liquid_toro.zip
1/19: http://www.mediafire.com/download/4olpmgsifq5qygc/LS-LP-v4.0-2015-01-19-liquid_toro.zip
Google Drive mirror: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhX0s4WGpFMm1BWEk&usp=sharing
Click to expand...
Click to collapse
Changelogs:
2/21: Boot animation memory leak fix
2/14: Switched from Layers to CM12 Theme Engine (clean flash this build)
2/11: Resynced source
1/28: Reverted minor F2FS change, Linaro 4.8.4 for ROM, Linaro 4.9.1 for kernel, deodexed
1/25: Minor change regarding F2FS, HW decoding working again, YouTube working, navbar customizations
1/19: ROM (but not kernel) supports F2FS on /data and /cache, torch tile fixed, new APNs
Credits and thanks:
LiquidSmooth team: https://github.com/LiquidSmooth
@Ziyan: https://github.com/Ziyann
@MWisBest: https://github.com/MWisBest
@zzpianoman: https://github.com/zzpianoman
@musical_chairs
@bsmitty83 for the Full_Auto kernel: http://forum.xda-developers.com/gal.../lollipop-kernel-fullauto-r1-aosp-cm-t2994371
@Nautilus74 for repacking Full_Auto with ramdisks
My other projects:
LiquidSmooth-UNOFFICIAL LP: maguro, toroplus
LiquidSmooth-OFFICIAL KK: maguro, toro, toroplus
LiquidSmooth-UNOFFICIAL KK: maguro, toro, toroplus, grouper
F2FS Converter tools: Galaxy Nexus, grouper
APNs: Ting (LTE), Verizon (MMS)
Click to expand...
Click to collapse
[poo]
Thanks @poo706! Looking forward to this.
A few things I collected on the first build:
Logcat error and fatal events ("adb logcat *:E *:F") for camera crash when saving a picture:
Code:
E/AudioTrack(17751): AudioTrack::set : Exit
F/libc (17751): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xf3e0 in tid 18007 (NotificationThr)
E/DEBUG ( 133): AM write failure (32 / Broken pipe)
E/SharedPreferencesImpl( 537): Couldn't create directory for SharedPreferences file shared_prefs/log_files.xml
E/Camera (17842): Error 100
E/CAM_CamErrCallback(17842): Got camera error callback. error=100
E/AndroidRuntime(17842): FATAL EXCEPTION: main
E/AndroidRuntime(17842): Process: com.android.camera2, PID: 17842
E/AndroidRuntime(17842): java.lang.RuntimeException: Media server died.
E/AndroidRuntime(17842): at com.android.camera.CameraErrorCallback.onError(CameraErrorCallback.java:33)
E/AndroidRuntime(17842): at com.android.ex.camera2.portability.AndroidCameraAgentImpl$ErrorCallbackForward$1.run(AndroidCameraAgentImpl.java:1099)
E/AndroidRuntime(17842): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(17842): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(17842): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(17842): at android.app.ActivityThread.main(ActivityThread.java:5221)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AudioService( 537): Media server died.
E/MediaPlayerFactory(18162): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(18162): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/MonoPipe(18162): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/SoundTriggerHwService(18162): couldn't load sound trigger module sound_trigger.primary (No such file or directory)
E/AudioService( 537): Media server started.
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
Strace output of launching the rild daemon on liquid LP (non-working radio) ("rild -l /vendor/lib/libsec-ril_lte.so -- -d /dev/ttys0"): http://pastebin.com/pHGNC7k3
Strace output of launching the rild daemon with FML's working radio: http://pastebin.com/LL50FQux
Keep seeing this "Failed to get socket port [7777]" after "Opening tty device /dev/ttys0\n\0", by filtering the previous 2 outputs through sort, uniq, and diff. I think MWisBest fixed something similar by patching the kernel.
My 2 cents. Keep up the great work man!
7175 said:
Thanks @poo706! Looking forward to this.
A few things I collected on the first build:
Logcat error and fatal events ("adb logcat *:E *:F") for camera crash when saving a picture:
Code:
E/AudioTrack(17751): AudioTrack::set : Exit
F/libc (17751): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xf3e0 in tid 18007 (NotificationThr)
E/DEBUG ( 133): AM write failure (32 / Broken pipe)
E/SharedPreferencesImpl( 537): Couldn't create directory for SharedPreferences file shared_prefs/log_files.xml
E/Camera (17842): Error 100
E/CAM_CamErrCallback(17842): Got camera error callback. error=100
E/AndroidRuntime(17842): FATAL EXCEPTION: main
E/AndroidRuntime(17842): Process: com.android.camera2, PID: 17842
E/AndroidRuntime(17842): java.lang.RuntimeException: Media server died.
E/AndroidRuntime(17842): at com.android.camera.CameraErrorCallback.onError(CameraErrorCallback.java:33)
E/AndroidRuntime(17842): at com.android.ex.camera2.portability.AndroidCameraAgentImpl$ErrorCallbackForward$1.run(AndroidCameraAgentImpl.java:1099)
E/AndroidRuntime(17842): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(17842): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(17842): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(17842): at android.app.ActivityThread.main(ActivityThread.java:5221)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AudioService( 537): Media server died.
E/MediaPlayerFactory(18162): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(18162): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/MonoPipe(18162): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/SoundTriggerHwService(18162): couldn't load sound trigger module sound_trigger.primary (No such file or directory)
E/AudioService( 537): Media server started.
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
Strace output of launching the rild daemon on liquid LP (non-working radio) ("rild -l /vendor/lib/libsec-ril_lte.so -- -d /dev/ttys0"): http://pastebin.com/pHGNC7k3
Strace output of launching the rild daemon with FML's working radio: http://pastebin.com/LL50FQux
Keep seeing this "Failed to get socket port [7777]" after "Opening tty device /dev/ttys0\n\0", by filtering the previous 2 outputs through sort, uniq, and diff. I think MWisBest fixed something similar by patching the kernel.
My 2 cents. Keep up the great work man!
Click to expand...
Click to collapse
Damn dude, your debugging abilities are far greater than mine! The device repos for maguro, toro, and toroplus were all set up in the same fashion : starting with googles latest source (jellybean) and applying a handful of commits authored by ziyan. All three boot. Everything works on maguro, no data on toro, and no voice or data on toroplus.
I gathered these commits from mw's github and figured I might need some or all to fix the radio issues on toro and toroplus. I would greatly appreciate your opinion.
https://github.com/MWisBest/android_bionic/commit/af1fc2a3051992897939980b38ef9da6455f2a73
https://github.com/MWisBest/android...mmit/8994231ced53c29b33200bc04275cafacf48025e
https://github.com/MWisBest/android...mmit/6d5cc7a2044335ee8c3cd042d173a5f4a66e520f
https://github.com/MWisBest/android_hardware_ril/commit/880e828a9424b469d27ec07b800efdb65cddc1af
https://github.com/MWisBest/android...mmit/7611a40b233517384d56d1f93caa7fd836c376af
https://github.com/MWisBest/android...mmit/f04c281e50ece48fc93dae62e4d5a5e4f982a567
https://github.com/MWisBest/android...mmit/b700091b6b5fc13b0b17e7fbc8ecb8083234dcea
https://github.com/MWisBest/proprie...mmit/9fc72185943049645c82dccd9f8f8791568d1444
https://github.com/MWisBest/proprie...mmit/5d70b4a8d019d60102432ca29f738e6e7c39a978
[poo]
poo706 said:
Damn dude, your debugging abilities are far greater than mine! The device repos for maguro, toro, and toroplus were all set up in the same fashion : starting with googles latest source (jellybean) and applying a handful of commits authored by ziyan. All three boot. Everything works on maguro, no data on toro, and no voice or data on toroplus.
I gathered these commits from mw's github and figured I might need some or all to fix the radio issues on toro and toroplus. I would greatly appreciate your opinion.
https://github.com/MWisBest/android_bionic/commit/af1fc2a3051992897939980b38ef9da6455f2a73
https://github.com/MWisBest/android...mmit/8994231ced53c29b33200bc04275cafacf48025e
https://github.com/MWisBest/android...mmit/6d5cc7a2044335ee8c3cd042d173a5f4a66e520f
https://github.com/MWisBest/android_hardware_ril/commit/880e828a9424b469d27ec07b800efdb65cddc1af
https://github.com/MWisBest/android...mmit/7611a40b233517384d56d1f93caa7fd836c376af
https://github.com/MWisBest/android...mmit/f04c281e50ece48fc93dae62e4d5a5e4f982a567
https://github.com/MWisBest/android...mmit/b700091b6b5fc13b0b17e7fbc8ecb8083234dcea
https://github.com/MWisBest/proprie...mmit/9fc72185943049645c82dccd9f8f8791568d1444
https://github.com/MWisBest/proprie...mmit/5d70b4a8d019d60102432ca29f738e6e7c39a978
[poo]
Click to expand...
Click to collapse
Thanks man, tryin to sharpen up my debug toolbox.
That's great you gathered up all the commits. I think you found exactly what we need.
I didn't see it in the commits, but there's also some toro-radio specific additions to build.prop I noticed in FML's build.prop, some of which may be needed.
Code:
# Set PREFERRED_NETWORK_MODE to GLOBAL in Database for this device
ro.telephony.default_network=7
# Set CDMA SUBSCRIPTION SOURCE to RUIM in Database for this device
ro.telephony.default_cdma_sub=0
# Enable code specific to toro's RIL
ro.telephony.toroRIL=1
# Default CDMA/LTE values from 4.2.2 OTA
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.cdma.otaspnumschema=SELC,1,80,99
7175 said:
Thanks man, tryin to sharpen up my debug toolbox.
That's great you gathered up all the commits. I think you found exactly what we need.
I didn't see it in the commits, but there's also some toro-radio specific additions to build.prop I noticed in FML's build.prop, some of which may be needed.
Code:
# Set PREFERRED_NETWORK_MODE to GLOBAL in Database for this device
ro.telephony.default_network=7
# Set CDMA SUBSCRIPTION SOURCE to RUIM in Database for this device
ro.telephony.default_cdma_sub=0
# Enable code specific to toro's RIL
ro.telephony.toroRIL=1
# Default CDMA/LTE values from 4.2.2 OTA
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.cdma.otaspnumschema=SELC,1,80,99
Click to expand...
Click to collapse
Thanks for the heads up about build.prop. I have a lot of stuff to try, I just need to find the time. Hopefully this weekend.
[poo]
Awesome news
Sent from my Galaxy Nexus using Tapatalk
There's no lag and I like the darker theme too.
I forgot to test the camera when I had it running though.
Did anyone get data to work? I think it just needs the proper apns.
See the unnificial thread. Poo posted a possible fix
nicotheandroidguy said:
Did anyone get data to work? I think it just needs the proper apns.
Click to expand...
Click to collapse
prbadboy69 said:
See the unnificial thread. Poo posted a possible fix
Click to expand...
Click to collapse
It's not an APNs issue, and I didn't post a fix. I think I know what needs to be fixed, but I'll have to put out another build.
[poo]
I saw a new build posted in maguro, excited to see if a new toro build is in the pipeline *waits patiently*
Either way backing up and converting my GNex back to ext4 for now, because I can't wait to try this. Really appreciate your work!
wkr.mky said:
I saw a new build posted in maguro, excited to see if a new toro build is in the pipeline *waits patiently*
Either way backing up and converting my GNex back to ext4 for now, because I can't wait to try this. Really appreciate your work!
Click to expand...
Click to collapse
My plan is to implement a couple of commits that will hopefully fix data and then put out a new toro build tonight or tomorrow.
[poo]
12/27 added to the OP. I expect data to be fixed in this build, if someone could please confirm that.
[poo]
poo706 said:
12/27 added to the OP. I expect data to be fixed in this build, if someone could please confirm that.
[poo]
Click to expand...
Click to collapse
Nice job man, data is working great with 3g! I'm in a weak area, so I haven't been able to test 4g yet.
{
"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"
}
Could someone let me know which gapps has a working camera?
7175 said:
Nice job man, data is working great with 3g! I'm in a weak area, so I haven't been able to test 4g yet.
Could someone let me know which gapps has a working camera?
Click to expand...
Click to collapse
Score! Please keep me posted on the 4G situation. I thought our camera problems were because of the new GPU drivers, not anything to do with gapps.
[poo]
poo706 said:
Score! Please keep me posted on the 4G situation. I thought our camera problems were because of the new GPU drivers, not anything to do with gapps.
[poo]
Click to expand...
Click to collapse
Ok, I must have misread something about the gapps camera working. For anyone that needs a working camera on lollipop, I've been using "Camera ZOOM FX".
Also, Smitty's lollipop beta 3 kernel is working great with this new liquid. Details here at this post.
7175 said:
Ok, I must have misread something about the gapps camera working. For anyone that needs a working camera on lollipop, I've been using "Camera ZOOM FX".
Also, Smitty's lollipop beta 3 kernel is working great with this new liquid. Details here at this post.
Click to expand...
Click to collapse
New Smitty is working with LS? I know that it wasn't compatible with CM before and LS is largely CM. Interesting... Is it f2fs compatible? I take it you manually removed the gpu module?
[poo]
poo706 said:
12/27 added to the OP. I expect data to be fixed in this build, if someone could please confirm that.
[poo]
Click to expand...
Click to collapse
"no sim card" error on boot... i dunno....
might just be my phone...screenshots are the same as last build..CMDA-1xRTT...voice:in service/Data: out
arigr said:
"no sim card" error on boot... i dunno....
might just be my phone...screenshots are the same as last build..CMDA-1xRTT...voice:in service/Data: out
Click to expand...
Click to collapse
Hmm, so that makes two bad reports and one good report. Not sure what to make of that.
[poo]
This looks interesting. I'm charging up my toro now, gonna give this a flash and see if I can help with any info on data and signal.
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the rebrand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or LAOS team, if it concerns their code base. This rom isn't LAOS supported, so no need to report errors or bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
maxwen
DU team
SlimRoms team
Resurrection Remix team
OmniRom team
SuperLamic, Sony-Lineage-3.4 team, Hazou, Sonyxperiadev
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 12.1
Download link: http://dwnld.aicp-rom.com/?device=amami
No more official Nougat support since focus shifted to Oreo! You can still get my unofficial Nougat builds here:
https://basketbuild.com/devs/SpiritCroc/amami/AICP-n7.1
Full Changelog link: http://dwnld.aicp-rom.com/?device=amami
Google Apps:
Beans gapps
Or
Open GApps (ARM or ARM64 7.1 pico or nano, depending on your phone's architecture)
If you experience a black screen in some apps (e.g. in Youtube or in camera app), please go to Developer options and enable "Disable HW overlays". Alternatively, you can also add a quick setting for this setting after having enabled developer settings. This setting is not persistent, so you will have to set it after each boot!
Reboot to recovery not working
You tell...
The ROM should contain everything you need to enjoy Android Nougat. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
Make sure you have real recovery!
Download the ROM and GApps and transfer them to your device
Boot to recovery (TWRP recommended)
Wipe system, Cache, data and ART/Dalvik cache
Flash ROM Zipfile
Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
Flash/Install the root solution of choice (optional)
Reboot to system
The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!
Supported root solutions:
Magisk v13.x
SuperSU - stable and beta available (Site by CCMT that took over the the marketing from chainfire)
SuperSU - direct download link for the latest SuperSU directly from the dev (chainfire)
Lineage SU-addon (check your needed version: 14.1 arm or arm64) -> the removal zip is available here too.
PREREQUISITE FOR OTA:
To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
IceColdJelly AICP G+ community
Kernel source: https://github.com/AICP/kernel_sony_msm8974/tree/n7.1
ROM & Additional links:
Gerrit Code Review
Github
You want to see a normal night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 12.1 Amami, ROM for the Sony Xperia Z1 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader, real recovery
Based On: AOKP, CyanogenMod, LineageOS, Omni-ROM, DirtyUnicorns
Version Information
Status: No Longer Updated
Created 2016-07-29
Last Updated 2018-03-02
another new rom How is it going with the camera?
NeoAqr said:
another new rom How is it going with the camera?
Click to expand...
Click to collapse
I heard that it's similar to du
Someone have some Screenshots from this ROM ?
FotoMichi said:
Someone have some Screenshots from this ROM ?
Click to expand...
Click to collapse
It looks like normal marshmallow, but wait, I'll install it and give you some
Here are screenshots!
@SpiritCroc why SIM card don't working? o
CmDaRkShAdOw said:
@SpiritCroc why SIM card don't working? o
Click to expand...
Click to collapse
It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?
SpiritCroc said:
It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?
Click to expand...
Click to collapse
I was waiting a few minutes. Tried reboot, clean flash(wipe system, data,cache, art) on DU was fine, not modified
CmDaRkShAdOw said:
Here are screenshots!
@SpiritCroc why SIM card don't working? o
Click to expand...
Click to collapse
whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now
NeoAqr said:
whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now
Click to expand...
Click to collapse
Yes. It's more stable than du,and photos are better.
SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?
Overall looks like a good MM ROM! Thank you!
EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.
SpiritCroc said:
AICP
Click to expand...
Click to collapse
Sudden battery drain a couple of times on 7/24 build, but love it overall, (i usually assume stuff like that has simething to do with Xposed, etc. anyway). Using newest build now. What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...
[GER]Roxxor said:
SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?
Overall looks like a good MM ROM! Thank you!
EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.
Click to expand...
Click to collapse
We all should use real recovery by now - can't be overwritten.
levone1 said:
We all should use real recovery by now - can't be overwritten.
Click to expand...
Click to collapse
Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.
And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".
Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.
EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.
EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.
levone1 said:
What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...
Click to expand...
Click to collapse
Well, I don't have any experiences with modifying kernel (I've always used the kernel that comes with the ROM in the past).
I can build the kernel together with the ROM, anything else I'd have to learn first...
[GER]Roxxor said:
Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.
And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".
Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.
EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.
EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.
Click to expand...
Click to collapse
Real recovery isn't touched by AICP, it still can be accessed the usual way (first press volume button before pressing power & hold until sony logo appears). It's the same way as in DU. In DU, you cannot reboot to recovery or boot to recovery when the sony logo appears after a normal power on. AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.
First press & hold volume button, power on -> device boots recovery partition
Power on while not pressing volume buttons -> device boots into ROM
Power on while not pressing volume buttons, then press volume when notification LED lights up -> tell the ROM you want to access recovery, which has no access to real recovery, but uses inbuilt recovery instead
SpiritCroc said:
AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.
Click to expand...
Click to collapse
Thank you very much for clarifying!
About the AudioFX issue(somehow I cant attach files):
Code:
11:22:04.332 819 2920 I MediaFocusControl: AudioFocus requestAudioFocus() from [email protected][email protected] req=1flags=0x0
07-30 11:22:04.335 336 6146 D NuPlayerDriver: reset(0xb3a38120)
07-30 11:22:04.335 336 6146 D NuPlayerDriver: notifyListener_l(0xb3a38120), (8, 0, 0)
07-30 11:22:04.335 336 6198 W AMessage: failed to post message as target looper for handler 0 is gone.
07-30 11:22:04.335 336 6198 D NuPlayerDriver: notifyResetComplete(0xb3a38120)
07-30 11:22:04.337 5999 6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.337 5999 6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.338 6181 6181 I HeadsetService: Starting service.
07-30 11:22:04.347 336 3033 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.347 6181 6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.347 6181 6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.348 6181 6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.348 6181 6181 E HeadsetService: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348 6181 6181 E HeadsetService: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService.saveDefaults(HeadsetService.java:521)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService.onCreate(HeadsetService.java:389)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2923)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.-wrap4(ActivityThread.java)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1446)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.348 6181 6181 E HeadsetService: at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.348 6181 6181 E HeadsetService: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.348 6181 6181 E HeadsetService: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.350 336 336 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.350 6181 6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.350 6181 6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.350 6181 6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.351 6181 6181 D AndroidRuntime: Shutting down VM
07-30 11:22:04.352 6181 6181 E AndroidRuntime: FATAL EXCEPTION: main
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Process: org.cyanogenmod.audiofx, PID: 6181
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Theme: themes:{default=, iconPack:org.twelf.cmtheme}
07-30 11:22:04.352 6181 6181 E AndroidRuntime: java.lang.RuntimeException: Unable to start service [email protected] with Intent { act=android.media.action.OPEN_AUDIO_EFFECT_CONTROL_SESSION cmp=org.cyanogenmod.audiofx/.HeadsetService (has extras) }: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3073)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.-wrap17(ActivityThread.java)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1461)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Caused by: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService.addSession(HeadsetService.java:208)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService.onStartCommand(HeadsetService.java:431)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3056)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: ... 8 more
07-30 11:22:04.354 819 835 W ActivityManager: Process org.cyanogenmod.audiofx has crashed too many times: killing!
EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?
[GER]Roxxor said:
EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?
Click to expand...
Click to collapse
I'm a bit lazy and they have inline kernel building while sonyxperiadev use a prebuilt kernel.
Additionally, they have some more modifications like TWRP configs which can become handy when building some custom ROMs, and they even have some commits cherry-picked from CM device tree (e.g. in order to enable reboot to recovery), while sonyxperiadev is clearly aimed at pure AOSP.
It worked fine when I was experimenting with different device trees for DU, and for now I just stick with it.
I think I'm going to directly fork sonyxperiadev when Nougat arrives, though
Now this thead has explained a lot of my confusion regarding recovery i have tried ACIP but because there was only 2-3 Cpu gouvernors and device was always hot (something is causing increased temps and batt drain)anyway there are 2 recoverys one that we call real recovery and that one after power on which flashes alongside ROM.
And if you lower the freq of cpu you will get random reboots
Sent from my D5503 using XDA-Developers mobile app
Verry nice Rom. Camera is a bit more stable than the du one.
For me Autorotation don't work.
I'm sorry. SIM Card works fine. Last time I had issue while flashing and I ignored it. Today SIM card didn't work on DU. Don't know why.
New build is up.
- Fix sensors not working (e.g. no working auto-rotation)
I was surprised by how few people noticed/complained about that...
{
"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:
/*
* 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.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Images
Here are some Screenshots of this ROM.
Ask me
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3
Latest firmware .291
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Format data to get rid of encryption.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Download TWRP
** optional
Update:
Get the latest build
Boot into TWRP
Flash the downloaded build
Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.
Downloads
Download ROM
MD5: 78a54bc2c55ce935a97b4c16cebe3c69
Addons
OpenGapps
BiTGApps
microGISG (Alternative GApps microG based)
Magisk
SU-Addon
Thanks
Whole LineageOS Team for this amazing ROM
@rcstar6696
@Myself5
@drakonizer
@tomascus
@koron393
@nailyk
@SpiritCroc
I hope I haven't forgot anyone
Bugs
WHAT'S BROKEN
Tell me
XDA:DevDB Information
LineageOS 17.1 z3, ROM for the Sony Xperia Z3
Contributors
NeoArian & Mr.Tom_Tom
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
ROM OS Version: 10.x
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2020-08-18
Stable Release Date: 2020-05-01
Current Beta Version: 2020-02-23
Beta Release Date: 2020-02-08
Created 2019-10-17
Last Updated 2020-08-18
Working LOS17 build achieved
Yep, here it is: LineageOS 17 with Android 10 for our good old Z3. Shinano's not dead (yet)!
Thanks to @NeoArian for sharing repos, manifests and some hints. Behavior seems to be similar to the Z3c build.
The following links are provided for testing purposes only and may be deleted in a few days, please refer to the "official" download links of the thread owner (thanks @ronidianpatisa).
Warning: the links below are now outdated, use the download links in post #1 please
Download: LOS 17 ROM for Z3, compiled as userdebug for TESTING ONLY (alternate hoster here)
Download: Related MD5 checksum file
Download: TWRP for Z3, compatible with Android 10 ROMs for TESTING ONLY
Download: GAPPS BETA
What I have tested so far: checklist working/not working (again, thanks to @NeoArian for this idea and the initial list)
What about Z3 Dual support ? Can D6633 users test the rom safely ?
Thanks @ MrTom_Tom for the sharing of the early LOS 17 build. Very nice from you.
One question: For what stands tbd in the linked checklist?
Nevetheless i will wait for the builds from NeoArian with working encryption.
I have tested your Android 10 rom for z3! Here it is some issues that I have found!
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
.
.
.
dhacke said:
[...] i will wait for the builds from NeoArian with working encryption.
Click to expand...
Click to collapse
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
dhacke said:
For what stands tbd in the linked checklist?
Click to expand...
Click to collapse
tbd = to be determined = not yet tested
elmxx said:
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
Click to expand...
Click to collapse
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Thanks you for your concern and your hard work along with your dedication.
Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
----------------------------------------------------------------------
Yes, I wiped cache, dalvik cache, data but I did wipe system either. May be wipe the SYSTEM wasn't such a good idea!
ignore " 4. some google sound cant be saved."
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
You are right , when you swipe down, a percentage value is shown next to the icon but without swipe down you wont able to see percentage value even if you enable it.
I think this rom will be better then pie rom.... Thanks for your time.
Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
On Android pie, digital wellbeing is not working unless gapps is installed. After installing gapps, digital wellbeing works like a charm. At least on android pie, I can confirm that.
Deleted
Today I took a look at the issue with Digital Wellbeing as reported by @elmxx.
I can confirm the issue - when trying to access Digital Wellbeing through Settings, the app force closes.
Log Cat excerpt:
Code:
10-19 21:47:20.091 19366 19366 D AndroidRuntime: Shutting down VM
10-19 21:47:20.092 19366 19366 E AndroidRuntime: FATAL EXCEPTION: main
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Process: com.google.android.apps.wellbeing, PID: 19366
10-19 21:47:20.092 19366 19366 E AndroidRuntime: java.lang.RuntimeException: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jex.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2071)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2039)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1987)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub$Proxy.getUnsuspendablePackagesForUser(IPackageManager.java:7072)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ApplicationPackageManager.getUnsuspendablePackages(ApplicationPackageManager.java:2368)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzd.get(PG:1)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at doj.get(PG:10)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzb.a(PG:2)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kik.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxx.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxy.run(PG:27)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at laq.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jgl.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jen.run(PG:4)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforce(ContextImpl.java:1896)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1924)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.getUnsuspendablePackagesForUser(PackageManagerService.java:13936)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:3326)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4028)
10-19 21:47:20.092 19366 19366 E AndroidRuntime:
I think the key info here is:
Code:
Neither user 10100 nor current process has android.permission.SUSPEND_APPS
I will look into that in more detail later, but it might be not that simple that there are some GAPPS missing.
Update:
I guess I found a solution, test was successful and submitted a patch already. Problem should be fixed in future builds.
elmxx said:
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
Click to expand...
Click to collapse
As you @elmxx have been the first to provide a detailed feedback I took some time to look after your FM Radio request, see updated post #2. It isn't working perfect as explained here by @NeoArian.
AbdullahSayed said:
What about Z3 Dual support ? Can D6633 users test the rom safely ?
Click to expand...
Click to collapse
Sorry, I have zero experience with the Dual Sim variant, I do not hink it will currently work.
FM Radio
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.
Thanks for the great work guys! It's awesome to see our shinano getting a 10 build. Will flash ASAP. Keep it up!
elmxx said:
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Click to expand...
Click to collapse
Yes, ignore the LOS email and calender app for the moment, they are buggy but the LOS team is working hard to fix them soon.
Flashing LineageOS rom without Gapps!
I just did flash lineageos rom without flashing Gapps! Here is what I found.......
Every lineageos apps work fine except message app. not getting Text Message Notifications. ------> " google message app works fine".
By the way, May be Gapps beta caused E-mail "keep closed" issue! I am not sure.
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????
Technoolli said:
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????
Click to expand...
Click to collapse
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
elmxx said:
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.
Click to expand...
Click to collapse
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?
nikapos said:
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?
Click to expand...
Click to collapse
I do not get into recovery like that, fastboot flashing does not work anymore ...
Technoolli said:
I do not get into recovery like that, fastboot flashing does not work anymore ...
Click to expand...
Click to collapse
ok then, start over.
1. flash original .291 rom with flashtool
2. make sure your bootloader is unlocked
3. enter fastboot to flash 3.3.1 twrp recovery to FOTAPartition
4. press power button holding down volume button until you feel one short vibration.
hope this does the trick. however this is not the proper thread to discuss unbricking or installing recoveries.
Thank you, but with the Flashtool I can not select the firmware ... Can I flash it somehow different? I just can not do more in the gas pedal, also I do not come in the recovery or Android system ... help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
/*
* 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.
*/
HOW TO INSTALL LINEAGEOS:
- Official instructions
- In short: sideload in Lineage recovery (suggested) / flash in TWRP
HOW TO UPDATE LINEAGEOS:
- Download update from Updater app
- Install update
DOWNLOADS:
LineageOS 18.1: Official Oneplus 5, Official Oneplus 5T
Google Apps: MindTheGapps
Recovery: Suggested: Lineage recovery for Oneplus 5, Oneplus 5T | Alternative: TWRP
DEVELOPER RESOURCES
LineageOS source code:
- https://github.com/LineageOS
Device tree:
- android_device_oneplus_cheeseburger
- android_device_oneplus_dumpling
- android_device_oneplus_msm8998-common
Kernel:
- android_kernel_oneplus_msm8998
Android version: Android 11
Kernel version: Linux 4.4.y
Required firmware: OxygenOS 10.0.1 (shipped with ROM, no need to install manually)
Telegram group: https://t.me/los_op5
Issues:
- Safetynet does not pass. Magisk hide & MagiskHide Props Config help here.
- Wireless display does not work
Notes:
- Relocking bootloader https://forum.xda-developers.com/t/...s-18-1-for-oneplus-5-5t.4173997/post-84770085 (thanks for @Eric_Lev ) (not suggested though)
Really appreciate your efforts dude
Will try this out
Would you consider removing the lineage recovery from future builds?
Any idea about oneplus 5t
Added to the OnePlus 5 Index Thread here.
T1mb3 said:
ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
There actually is no option higher than Android 10 yet
JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.
T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
Having said this...
Oswald Boelcke said:
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.
Click to expand...
Click to collapse
...you can always edit the first post using the edit button at the end of the post (instead of using the edit project option for DevDB threads) and manually change it to Android 11.
Is it rooted?
Does this pass SafetyNet?
sergio_sant said:
Is it rooted?
Does this pass SafetyNet?
Click to expand...
Click to collapse
This is not rooted by default. Latest Magisk works for that purpose.
This does not pass safetynet. I will have to look for a solution. Other ROMs use kernel-side patches for safetynet and those are not allowed in LineageOS.
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？
kpzhao said:
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？
Click to expand...
Click to collapse
I did it this way: https://github.com/LineageOS-cheese...mmit/65b18d38368955a5a9cac58d09bf5c867624fb53
Great work, thanks for this rom. I LOVE IT
this is the 1st custom rom i install and the instructions were smooth. I did upgrade because oneplus stopped supporting OP5 and just sent a message in the community app giving fake excuses for the delays.
I noticed this bug
some apps that has the option to login with fingerprint doesn't work properly ( i.e. TD Canada Trust, Manulife)
as soon as the phone tries to communicate with the fingerprint reader, it freezes. 1st login in Manulife app, it asks if you want to allow or deny access to fingerprint reader, if you deny, it will let you login with the password if you remember it. if you accept, it hangs.
In TD Canada Trust app, first time you login with your password, it gives you a popup asking you if you want to enable fingerprint login, and you cant press anything other than closing the app.
T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Can't call through VoLte, Volte cannot call!
Cannot tap to wake(settings-Display-Advanced-Tap to wake)
Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?
kpzhao said:
Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?
Click to expand...
Click to collapse
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b
T1mb3 said:
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b
Click to expand...
Click to collapse
You are a good man, sir. I am very appreciated for your help.