{
"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"
}
How-to:
* download firmware zip
* download opengapps
* push it into your phone
* reboot to recovery, make a full wipe
* install RR, install gapps
* reboot
* enjoy
GENERAL INFO:
First, for all who had a problem with camera (green pics) this is because you are NOT update your firmware. I used blobs from latest version of firmwares. To solve this "issue" please flash new version of firmware via newflasher, but exclude:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Update your blobs ONLY if you have green pics. Update it every time not needed.
Second, in my ROM i disabled force encryptions (because i don't like it) and many users had bootloops. To solve this "issue" after flashing ROM zip in recovery turn off your phone and flash boot (see link below). Flash it ONLY if you NOT disabled force encryptions.
Download ROM & encrypted boot.img:
HERE
Flash IT by
Code:
fastboot flash boot name_of_boot.img
Thanks:
@modpunk
Github:
Sources
Эта прошивка поддерживает TTL?
Проверка в терминале:
Code:
su
iptables -t mangle -A POSTROUTING -o -j TTL --ttl-set 64
Если не будет ошибок, то ок.
translation
Does this the ROM support TTL?
Check in terminal
Code:
su
iptables -t mangle -A POSTROUTING -o -j TTL --ttl-set 64
If there are no errors, then ОК
Thanks a million! Goes for an immediate test as LOS seems so buggy for my needs at the time.
Thank you so much for making this ROM! So far so good. The only bug I've found is that trying to change the accent color of the theme doesn't work. Other than that everything I've tried so far is perfect!
EDIT: So I tried to flash this ROM on another Compact, but it gets stuck on boot. Anyway to fix this?
Never mind. Fixed by formating data in TWRP
Have to say that so far waaaaay best ROM for XZ1C, I've propably tried all available. One thing I've noticed that after -4 hrs of me sleeping phone was very hard to wake up. Other things notices are some minor desriptions or translations which circled on screenshots. This ROM does not leave much more to hope for. Magisk does not pass safetynet due cts.profile mismatch.
First, in build data wrote right, because I'm from Russia and when building rom host used my home language, for other it's not matter so much
Magisk works perfect, but only stable version 16 and safetynetfix last beta
Sent from my Sony Xperia XZ1 Compact using XDA Labs
russel5 said:
First, in build data wrote right, because I'm from Russia and when building rom host used my home language, for other it's not matter so much
Magisk works perfect, but only stable version 16 and safetynetfix last beta
Sent from my Sony Xperia XZ1 Compact using XDA Labs
Click to expand...
Click to collapse
Yes, no offense, few things would just make it perfectly clean ROM + cleaning he audio files witch seems to be there for 3-4-5 times each. But those I can clean myself.
Thanks for making this ROM, finally my phone is usable... since mid December.
To clarify: the audio files sees to be there once per file, no duplicates, the picker just lists them multiple times for some reason.
Anyone getting random reboots with this ROM, like people have reported with Lineage? Is this GPS working? Is the fingerprint sensor working?
Thanks for all the work.
Thread updated, enjoy
ChangeLog_11.04.18:
* WiFi fixed
* 'Ok Google' fixed
* GPS fixed
Thanks to:
@modpunk @derf elot @djdarkrider
russel5 said:
First, in build data wrote right, because I'm from Russia and when building rom host used my home language, for other it's not matter so much
Magisk works perfect, but only stable version 16 and safetynetfix last beta
Sent from my Sony Xperia XZ1 Compact using XDA Labs
Click to expand...
Click to collapse
Thks for the latest update. Could you give me some pointer on how to get Magisk to pass safetynet as I cannot seem to find my way out of it?
Install magisk 16.0 via twrp, turn on your phone
Install universal safety net fix beta via twrp
That's all
Sent from my Sony Xperia XZ1 Compact using XDA Labs
russel5 said:
Install magisk 16.0 via twrp, turn on your phone
Install universal safety net fix beta via twrp
That's all
Sent from my Sony Xperia XZ1 Compact using XDA Labs
Click to expand...
Click to collapse
Still no luck. Maybe I don't have right safetynetfix file. BTW, do you experience issues copying files from internal memory to sd-card and the files get corrupted, like mp3 is 0 bit?
Reboot and all files will be normal
Sent from my Sony Xperia XZ1 Compact using XDA Labs
russel5 said:
Reboot and all files will be normal
Sent from my Sony Xperia XZ1 Compact using XDA Labs
Click to expand...
Click to collapse
It's me being stupid now, just can't figure it out and suspect that my safetynetfix file is screwed up or incorrect.
Any chance you could link or post it here or ia PM?
Thks!
It seems like Calling doesn't work on this ROM. Whenever I call someone and they answer we can't hear each others voice. I tried a phone call without VoLTE enabled and it still didn't work.
Dinowaffles said:
It seems like Calling doesn't work on this ROM. Whenever I call someone and they answer we can't hear each others voice. I tried a phone call without VoLTE enabled and it still didn't work.
Click to expand...
Click to collapse
I'd say this ROM has less non-working-features as any other. Calling works just as it's supposed here.
akonet.android said:
I'd say this ROM has less non-working-features as any other. Calling works just as it's supposed here.
Click to expand...
Click to collapse
+1
No problem with calling.
Sent from my Sony Xperia XZ1 Compact using XDA Labs
akonet.android said:
I'd say this ROM has less non-working-features as any other. Calling works just as it's supposed here.
Click to expand...
Click to collapse
Does it really? Yeah I could make calls, but the person that calls me can't hear me, and I can't hear the person who called me. I thought the problem might be the microphone, but using the recorder app showed me that it was working fine.
Dinowaffles said:
Does it really? Yeah I could make calls, but the person that calls me can't hear me, and I can't hear the person who called me. I thought the problem might be the microphone, but using the recorder app showed me that it was working fine.
Click to expand...
Click to collapse
Sorry to hear, I'm not that much of an expert but just a regular flash-junkie. Wiped, dalvik, cache, system, data. That's it. You may want to take Titanium back up of current set up to your external SD. Redownload the ROM and wipe like I did... and yes, start all over again. But Titatium helps the set up just as long as you don't restore any faulty calling related backups.
---------- Post added at 06:48 PM ---------- Previous post was at 06:45 PM ----------
...I'm doing TBU's of user apps to a different folder in these cases. Let the ROM build up it's own files of data etc and then you just restore the user apps from the specific folder.
Dinowaffles said:
Does it really? Yeah I could make calls, but the person that calls me can't hear me, and I can't hear the person who called me. I thought the problem might be the microphone, but using the recorder app showed me that it was working fine.
Click to expand...
Click to collapse
I think you are used aosp? If yes please flash via newflasher the latest firmware, exclude system, vendor, kernel, fotakernel, userdata and all *.ta
If not, do the same
Sent from my Sony Xperia XZ1 Compact using XDA Labs
Related
JB AOSP 4.3 alpha 1 by LeTama
{
"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"
}
*** DISCLAIMER ***
I'm not responsible if it breaks your device! Don't install it if you want something stable.
*** /DISCLAIMER ***
Be careful, this is a very preliminary build. Backup your stuff and expect problems.
DON'T TRY TO FORMAT any unformated external USB drive/key with OTG cable, it could format internal storage instead !!!
Introduction
Here is my port of JB AOSP 4.3 for our Xperia S. This is a work in progress, it's currently missing few of the patches I used in 4.2.X and few things are completely untested.
Installation and downloads
You need unlocked bootloader and a working recovery.
Download installation zip from here, mirror thanks to @androidlover007 (I know, uploaded.net is not the fastest of the earth, multipload mirrors coming soon. I'm not against posting any other mirror).
Copy it to internal storage
Wipe Data/Cache
Install gapps for 4.3. Currently, we don't have "official" gapps from CM team, I used PA ones with good success.
Reboot and let the rom settle down a bit
Important: Current release has a recovery with broken offline charging, you should flash a fixed one after installing the rom to avoid any trouble. Check this post.
Kernel source code is here (branch jb-4.2-experimental).
Note: this rom flashes its own kernel that comes with TWRP recovery and last version of Boot Manager. Just use volume up/down to navigate boot manager menu and power to select if you want to go to TWRP. Don't play with Boot Manager options if you don't know what you're doing.
Status
Working:
Display / 3D (with some stuttering, under investigation)
Audio (without LPA, won't add it)
Calls / SMS / MMS / Data
Camera (Pictures / Videos)
Bluetooth
Wifi
Wifi Tethering
Sensors
GPS
Hardware video encoding/decoding
Offline charging
NFC
SELinux
WIFI EAP. (untested, can anyone confirm ?)
Not working:
FM radio: I won't implement it in aosp with current proprietaries as they will conflict with 4.2+ bluetooth.
HDMI.
Auto brightness (disabled now)
And probably more, let me know
Missing
TRIM Support
Known issues
1080p video stuttering (waiting for new Sony firmware)
voip audio disabled, voip is going through normal channels (waiting for new Sony firmware)
Wifi direct disabled (waiting for new Sony firmware)
subway surfers game is not working
SuperSU not working. You can flash a working one here.
Changelog
2013/08/07 - Alpha 1
- SELinux added
- Media server crash on audio notification fixed
- Move to SD fixed
- Ril crash on some mvno fixed.
- SuperSU updated to 1.51
- 12 and 9M camera size
- Panorama fix
- Google backup selected as default
- EAP finished
2013/08/03 - Alpha 0
FAQ
Can I flash any kernel with it ?
No. This rom is using Nexus 4 proprietaries and requires matching video drivers. You must use embedded kernel.
Something is not working, crashed, whatever, how can I help ?
Please provide logs! Description is not enough, I need at least logcat and ideally dmesg. If phone reboots, go to recovery, get the /proc/last_kmsg file and provide it to me.
Dev options are missing ?
No, they're just hidden, it's now the default behavior in 4.2.x. To enable it, go to settings / about and tap multiple times on build number, menu will be enabled and stick after reboot.
* reserved, now you can go on *
Great And Fast Work.
Omg you are fast man
Sent from my LT26i using xda premium
Is there need to report bugs or it is too early for such thing?
Anyhow, I'm downloading right now, will report back with observations.
Log:
- Booting seems fine, some glitches but nothing to worry about...
- Font is kinda different, I like it, very much. It is even more close to Helvetica and for me it is very nice typeface porn
- Touch vibration is kinda shorter, more direct but weaker.
- Developer tools are updated with very nice features, everything mentioned at Google I/O 2013.
- Animations are smoother. It's not that "new ROM" smoothness, transitions between screens appear like constant 60fps, without that lag that sometimes occurs regardless on hardware.
- There are some differences in first time configuration, nothing radical but still...
- Google Play Store wont open, close it and relaunch and then it will show TOS. It lags a bit.
- Is it me or DPI is kinda different? Everything seems to be bigger. Icons in drawer, Google play apps... SystemUI feels kinda same. EDIT: 320dpi.
- AOSP keyboard icon is different. RAM usage is same, no lower usage or anything special. Available RAM - 622 MB.
- Touch responsivness seems a bit better.
- Texdroider DPI (DPI changer) doesn't work. On 4.2.2 it would work with OpenSEMC, but it's not the case on 4.3.
SuperSU does not work (no su binaries), this ROM is unrooted. To root it again do the following:
Download SuperSU 1.51 from here
Move it to your root folder on your phone
Turn your phone off, boot it into recovery
flash that zip you copied to your root folder "SuperSU 1.51"
Reboot to system.
Voila!
damn your way ahead of me
letama
Click to expand...
Click to collapse
Damn your way ahead of me,aw whell , ill try in 4.4 xD
PS did you use the google 4.3 source code or did you use Sonys Aosp source code... or did you port this from XZ??
still learning....
i love that warning about formatting otg drives d:
great
mirhl said:
i love that warning about formatting otg drives d:
Click to expand...
Click to collapse
i am so happy,now a android 4.3 developing for our xperia s.hope it is soon capable of daily use.THANK YOU to all developers :laugh: i love yall very much
switzerland92 said:
Is there need to report bugs or it is too early for such thing?
Click to expand...
Click to collapse
Yes, please do. I didn't run it for a long time, I really need feedback.
Envious_Data said:
Damn your way ahead of me,aw whell , ill try in 4.4 xD
PS did you use the google 4.3 source code or did you use Sonys Aosp source code... or did you port this from XZ??
still learning....
Click to expand...
Click to collapse
This is google 4.3 code, with my 4.2.x device tree and proprietaries. I'll take a shot at merging 4.3 kernel drivers soon.
mirhl said:
i love that warning about formatting otg drives d:
Click to expand...
Click to collapse
Burnt once! I didn't include 4.2 patch. Code changed, so it could work properly, but I have to test it first with a good backup
Ty bro
letama
Click to expand...
Click to collapse
hopefuly soon i will know as much as you
lets see if sony make a 4.3 or a 4.4 (sony themed)
i will definatly try to port that to an older device
Hey awesome letama! Are you going to release the ROM for loop? Tried your script but it didn't work. Thanks
letama said:
Yes, please do. I didn't run it for a long time, I really need feedback.
Click to expand...
Click to collapse
To keep it on one place and as organized as possible I'll edit my post with new info for you and others that are afraid to flash it right away
EDIT: Well, I don't have root. SuperSU says I must manually re-root and I must, quote, "consult the relevant forums for your device" which in this case is your thread
Someone please mirror i can never use uploaded.net
Sent from my 4.2.2 PAC powered Xperia S via Tapatalk
Noob question: Can adreno 220 ever support OpenGL ES 3.0 ?
skifyr123 said:
Hey awesome letama! Are you going to release the ROM for loop? Tried your script but it didn't work. Thanks
Click to expand...
Click to collapse
Yes, script can't work. I will upload it tomorrow, it's prepared but untested.
switzerland92 said:
EDIT: Well, I don't have root. SuperSU says I must manually re-root and I must, quote, "consult the relevant forums for your device" which in this case is your thread
Click to expand...
Click to collapse
Check first posts, known issues sections, SuperSu is not up to date in the rom. There is a link to one that can be flashed and works...
I'm going to download as soon as I get home. About performance, similar to 4.2.2?
Enviado desde mi Xperia S usando Tapatalk 4 Beta
Ben36 said:
Someone please mirror i can never use uploaded.net
Click to expand...
Click to collapse
Electricity problem here, I lost my multiupload I'll restart tomorrow.
Flash this ROM at your own risk. I am not responsible for anything that happens to your device when flashing.
The goal of this ROM is to rid of any unneeded apps along with replacing Huawei's apps with better alternatives such as AOSP apps. In the future this ROM will feature an AROMA installer but for now I am looking to squash bugs and make sure its as smooth as possible.
Features:
AOSP Keyboard (long press symbols)
AOSP Email
AOSP Music
Android N Emojis
Google Messenger
Rooted
ViPER4Android
Call Recording
DT2W
AdAway
KangVIP Tools
Xposed Ready
Deodexed
Debloated
More to come/etc.
Noted Bugs:
-VPN getting "Unsuccessful" error when connecting over L2TP only
-Google Voice Routing not working when set as default
-AOSP Keyboard seems to be using data
-Permissions Manager does not open
-Can't swipe the NavBar to make the screen smaller
-K-settings: Lockscreen & Desktop Modifications not functioning properly
-Can't edit in gallery
Downloads:
ROM is in the download section above.
TWRP:
https://www.androidfilehost.com/?fid=24421527759883292
Removed Apps:
https://basketbuild.com/devs/Ephemera/Mate%208
How to install:
Note: TWRP must be installed, see above for download link.
1. Head on over to the downloads section and grab the latest version.
2. If you'd like to clean install (recommended) wipe data.
3. Flash ROM file
4. You may need to install SuperSU from the Play Store.
Note: ROM will restart on initial boot, this is due to SuperSU patching the boot.img to prevent the filesystem from being encrypted. If it doesn't boot after the first restart hold power to restart it a second time, should boot without any issues.
Please report any critical bugs you can find. If you have a feature request or would like to a certain AOSP app don't be afraid to ask
If you like my work and would like to keep me going consider buying me a cup coffee by clicking here. It'll help a lot more than you think thanks to a recent loss of hundreds of dollars. If you're interested here's a read for you: http://forum.xda-developers.com/mate-8/general/gizok-t3376018
Thanks to:
@ajsmsg78 and @pappschlumpf for their help and time.
@ajsmsg78 for his TWRP
XDA:DevDB Information
Ephemeral Mate 8, ROM for the Huawei Mate 8
Contributors
Ephemera
ROM OS Version: 6.0.x Marshmallow
Based On: Stock International
Version Information
Status: Stable
Stable Release Date: 2016-04-18
Beta Release Date: 2016-04-04
Created 2016-03-22
Last Updated 2016-07-03
Notes:
ajsmsg78 said:
On International custom roms where Permission Manager keeps closing, after you flash the rom open up Phone Manager FIRST and hit the settings icon then disable Smart tune-up. Then open up Permission Manager. I made a test rom for B180 and can confirm this is what I did to resolve the issue.
Click to expand...
Click to collapse
Workarounds:
To get ViPER4Android working change SELinux to permissive using this app:
http://forum.xda-developers.com/showthread.php?t=2524485
If AOSP Keyboard is using mobile data please report and restrict access in traffic management.
Changelog:
Code:
7/03/16:
-Switched to chinese firmware
-Updated verison with Kang to B352
-Android N Emojis
4/18/16:
-Switched both versions to a deodexed base.
-Removed FMRadio
-SELinux to permissive by default
-Removed Themes to reduce filesize
-Changed the way SuperSU is installed for a potential fix for freezing apps
-Default DPI set to 360 (version without tools)
4/08/16:
-Updated to B180 (without kang tools)
-Remove ViPER4Android drivers to resolve an issue with hangouts calls
-Reverted to stock music player
4/04/16:
-Small kernel changes
-SELinux to permissive
-Reverted a change in build.prop to potentially solve any issues with Kang Tools
-Fixed issue with swiping on NavBar
-ViPER4Android drivers are now installed by default
4/01/16:
-Reverted to stock Gallery
-Revived original odexed version with bug fixes
-Switched from SolidExplorer to Cabinet BETA
Download link is a recovery image. FYI.
jdubya45 said:
Download link is a recovery image. FYI.
Click to expand...
Click to collapse
It is in the download section at the top. Changed heading to prevent confusion.
Is it necessary to flash the twrp or twrp 3.0.0.1 is fine?
huh, did we get an update to 3.0.0.1 for the mate 8? as far as i can see, rayglobe's version is still at 3.0...
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
jbmc83 said:
huh, did we get an update to 3.0.0.1 for the mate 8? as far as i can see, rayglobe's version is still at 3.0...
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
Click to expand...
Click to collapse
My mistake, you are right. My Twrp is shown as 3.0.0.r1
tonyeltriton said:
Is it necessary to flash the twrp or twrp 3.0.0.1 is fine?
Click to expand...
Click to collapse
Any version of twrp should work fine.
{
"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"
}
send from my HUAWEI NXT-L29 with Tapatalk
Hen Ry said:
View attachment 3692273View attachment 3692274
send from my HUAWEI NXT-L29 with Tapatalk
Click to expand...
Click to collapse
give viper4qndroid permission in settings →apps
send from my HUAWEI NXT-L29 with Tapatalk
Hen Ry said:
View attachment 3692312
send from my HUAWEI NXT-L29 with Tapatalk
Click to expand...
Click to collapse
Did you download SuperSU from the play store and give access? Also use the app in the download section to SELinux to permissive for now.
1.Will xposed be installed in the rom in the future?
2.the reboot option is soft reboot?
Ps: it seems that this rom works fine on nxt l09,but others don't.
( stuck on the hwstartguide )
Ah, now.
send from my HUAWEI NXT-L29 with Tapatalk
catchfree said:
1.Will xposed be installed in the rom in the future?
2.the reboot option is soft reboot?
Ps: it seems that this rom works fine on nxt l09,but others don't.
( stuck on the hwstartguide )
Click to expand...
Click to collapse
Yes it is a soft reboot. Xposed support is a WIP you can try flashing it to see if it works. How is it stuck on the hwstartguide? I have had someone report it works fine on the AL10 and I imagine it should work fine on L29
Ephemera said:
Yes it is a soft reboot. Xposed support is a WIP you can try flashing it to see if it works. How is it stuck on the hwstartguide? I have had someone report it works fine on the AL10 and I imagine it should work fine on L29
Click to expand...
Click to collapse
Ah i have a typo initially
It's l09 not l29.
I'll try xposed at night and give you a feedback
on my phone,the hwstartguide of is a loop(unable to sign in the hw account because of region, not sure if it will cause problem )
Additionally,the erecovery always shows that it can't receive the data of the package(guess that hw didn't upload the rom for my device)
catchfree said:
Ah i have a typo initially
It's l09 not l29.
I'll try xposed at night and give you a feedback
on my phone,the hwstartguide of is a loop(unable to sign in the hw account because of region, not sure if it will cause problem )
Additionally,the erecovery always shows that it can't receive the data of the package(guess that hw didn't upload the rom for my device)
Click to expand...
Click to collapse
eRecovery should be working just fine that's something I haven't touched, it ignores build number and always grabs the latest for your model number. I can't test whether it loops o not because I don't have a Huawei account. But report it as a bug in the top so I can keep track of it and look into it later.
Call Recording
DT2W
Where do I enable it?
catchfree said:
Ah i have a typo initially
It's l09 not l29.
I'll try xposed at night and give you a feedback
on my phone,the hwstartguide of is a loop(unable to sign in the hw account because of region, not sure if it will cause problem )
Additionally,the erecovery always shows that it can't receive the data of the package(guess that hw didn't upload the rom for my device)
Click to expand...
Click to collapse
nice, proof that one can crossflash firmwares onto the single sim model as well
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
Hen Ry said:
Call Recording
DT2W
Where do I enable it?
Click to expand...
Click to collapse
Settings > Smart assistance > Motion control > Double touch
Call Recording is built into the dialer, so you'd make a call and then see the option to record it.
AICP 11_ANDROID ICE COOL PROJECT For Honor 3c (h30-u10)Kernel Source: Stock Honor 3c
{
"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"
}
Intro: Like RR Remix, AICP 11 is an awesome rom based on CM13_6.0.1 and packed with lots of customization options and super performance. AICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!
Rom Features :
#All CM13 Features + A boat load of features
***Awesome AICP 11 Boot Animation
What's Working:
#Camera
#Video recording in stock/google camera is working with 1080p.
#Ril, Dual SIM, USSD, SMS, Audio in calls, no more fc in dialer.
#Wi-FI, Bluetooth, Mobile Data, Hotspot.
#Audio, Mic
#All sensors ( proximity, accelerometer, rotation)
#Notification LED.
#Storages (SD and internal) [Mounting in both Phone and PC]
# Gapps, Youtube 720P_with patch
Known Bugs:
#GPS partially works... [The GPS detects your location when you're at one place (not moving) very accurately but when you move it doesn't work properly]
#VPN isn't working.. [May work with some third party apps]
#Changing mobile data mode from 3g to 2g doesn't work.
My contributions to this rom:
#Porting this rom.
#Fixing Sensors.
#Fixing LED bug.
#Increased Overall sound...
***More modifications coming soon with future builds...
Credits:
Ferhung, Fire855, Hyperion70, Diparth Shah, Ajit Guraya, Minh Quoc and Karim Gahgah, Aniruddha Adhikary, Team Roger That, nofearnohappy, Varun Chitre, Ariafan, Vald.masti, Alex
Thank you guys for compiling this rom...
ROM LINKSLatest AICP_11 Rom:https://drive.google.com/open?id=0B3jAP5B2Fcq1R2Fvdl9VMFlqT1U
Gapps: https://drive.google.com/open?id=0B3jAP5B2Fcq1cmZVbDNrNG9pdnM
Youtube Patch: https://drive.google.com/open?id=0B3jAP5B2Fcq1MVlHTXROeDNvZ2M
***If you apply youtube patch only higher reolution of a youtube video will play smoothly.You won't be able to switch to lower resolution.
If you are satisfied with 360p, don't flash youtube patch.
Links to my other ported ROM: #CM13 : http://forum.xda-developers.com/android/development/rom-6-0-1-cyanogenmod-1320-04-2016-t3363980/post66492336#post66492336
# RR Remix 5.6.8 : http://forum.xda-developers.com/android/development/rom-ota-resurrection-remixv5-6-8stable-t3374493/post66747505#post66747505
PLZ DON'T MIRROR THIS POST OR THE ROM WITHOUT GIVING PROPER CREDITS
Installation Instructions*Take a nandroid backup if you want to restore your previous rom, incase anything goes wrong.
1. Wipe cache, Dalvik cache, System, Data
2. Flash rom
3. Flash gapps right after flashing rom (important)
4. turn device off..
5. Extract boot.img from this rom.zip and flash it using SPFT. (important)
6. Start your device.
7. If the touch is unresponsive and no sim is detected then goto recovery and flash codelover's kernel swapper and modemfix.
[ I think modem fix doesn't work in cm13...if it works, you are lucky but if it doesn't work then copy "catcher_filter_1_wg_n.bin" and "modem_1_wg_n.img" file from your stock rom's system/etc/firmware folder and paste and replace these two files in cm13's system/etc/firmware folder] (if you change these files in the cm13 rom zip file then you don't need to change permissions. but if you are doing it with root explorer then don't forget to change their permission to rw-r-r)
9. Reboot the phone and wait for the cm13 to bootup. The rom should boot within 10 mins.
Enjoy
Screenshots Attached Below:
Pavel GPS partially working means the GPS detects your location when you're at one place (not moving) very accurately but when you move it doesn't work properly.
Sent from my Honor 3C using XDA-Developers mobile app
boss.tekkers said:
Pavel GPS partially working means the GPS detects your location when you're at one place (not moving) very accurately but when you move it doesn't work properly.
Click to expand...
Click to collapse
I have this similar hunch... but I wasn't quite sure. Do you have something/somekind of evidence/proof to back your statement, perhaps a simple steps by using somekind of diagnostic app? I felt it too when using any kinds of apps that utilize GPS, but I couldn't be quite sure where it did come from.
boss.tekkers said:
Pavel GPS partially working means the GPS detects your location when you're at one place (not moving) very accurately but when you move it doesn't work properly.
Sent from my Honor 3C using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for your feedback bro..i'll add it in the rom description.
Sent from my Honor 3c using Tapatalk
First of all a huge thanks for you..
you are rocking by porting the new and fixing the bugs ur hardwork will never fail. I going to flash the rom sry to ask how about the battery life bro
Sent from my mt6582 using Tapatalk
popz1 said:
First of all a huge thanks for you..
you are rocking by porting the new and fixing the bugs ur hardwork will never fail. I going to flash the rom sry to ask how about the battery life bro
Sent from my mt6582 using Tapatalk
Click to expand...
Click to collapse
Welcome bro
I didn't have the time to install all of my apps in this rom. I had to go to versity, so i restored back to my previous rom.
I think this rom is faster and smoother than rr remix.
Plz leave your feedback about battery life after using this rom.
Sent from my Honor 3c using Tapatalk
sure bro
Sent from my mt6582 using Tapatalk
Vibration and then restart
Im Flashed this rom but Vibration and then restart does not boot uphelp mi??
South_Azarbijan said:
Im Flashed this rom but Vibration and then restart does not boot uphelp mi??
Click to expand...
Click to collapse
Did you flash boot.img using SPFT tool?
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
Nice work Pavel. Much appreciated. I am currently testing your other Android 6 ported ROM.
x3r0.13urn said:
I have this similar hunch... but I wasn't quite sure. Do you have something/somekind of evidence/proof to back your statement, perhaps a simple steps by using somekind of diagnostic app? I felt it too when using any kinds of apps that utilize GPS, but I couldn't be quite sure where it did come from.
Click to expand...
Click to collapse
There must be some app to test this. I'll see and let you guys know of any test results.
hakneo said:
Did you flash boot.img using SPFT tool?
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
Nice work Pavel. Much appreciated. I am currently testing your other Android 6 ported ROM.
Click to expand...
Click to collapse
I carefully did all the installation steps but Vibration and then restart does not boot up
South_Azarbijan said:
I carefully did all the installation steps but Vibration and then restart does not boot up
Click to expand...
Click to collapse
If you have TWRP 2.8.6.0 you can easily flash boot.img. Did you try that method?
Sent from my H30-U10 using XDA-Developers mobile app
So how do we multi window in this rom?
Sent from my H30-U10 using XDA-Developers mobile app
goku1234567890 said:
If you have TWRP 2.8.6.0 you can easily flash boot.img. Did you try that method?
Sent from my H30-U10 using XDA-Developers mobile app
Click to expand...
Click to collapse
I every way carfully doing gave's but again Vibration and then restart does not boot up
South_Azarbijan said:
I every way carfully doing gave's but again Vibration and then restart does not boot up
Click to expand...
Click to collapse
Open rom zip file and extract boot.img to your memory card. Go to recovery and make sure your current rom is backed up. Then go to wipe and do factory reset. Then go to install and flash this rom. Then flash the gapps provided in the first page. Then go to the install option in recovery and click "images" option then find the boot.img file you extracted earlier in your card and then flash boot.img only. And then your rom should boot up and start working in 10 min or so.
Sent from my H30-U10 using XDA-Developers mobile app
thanks you very much
Pavel Sajjad Khan said:
Welcome bro
I didn't have the time to install all of my apps in this rom. I had to go to versity, so i restored back to my previous rom.
I think this rom is faster and smoother than rr remix.
Plz leave your feedback about battery life after using this rom.
Sent from my Honor 3c using Tapatalk
Click to expand...
Click to collapse
thanks you very much, I want to know which rom are you using now, I want to flash a more stable rom you have ported, thanks
Hey just a quick update about this. Really loving this rom i usually dont like ported roms to our phone due to all the bugs and by far i haven't seen any. Really really smooth, camera and video works well too haven't given mobile data a test don't use it but to my extend you can use it. And battery life is nice too comparable to miui v7. All in all really a nice rom. Can be used as a daily driver.
Sent from my H30-U10 using XDA-Developers mobile app
goku1234567890 said:
Hey just a quick update about this. Really loving this rom i usually dont like ported roms to our phone due to all the bugs and by far i haven't seen any. Really really smooth, camera and video works well too haven't given mobile data a test don't use it but to my extend you can use it. And battery life is nice too comparable to miui v7. All in all really a nice rom. Can be used as a daily driver.
Sent from my H30-U10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for your reply,I have flashed your rom Cyanogenmod 13 link in http://forum.xda-developers.com/and...20-04-2016-t3363980/post66492336#post66492336
but when i reboot my cell phone, the boot animation stay in screen until the battery was completely consumed. Now, I am waiting for your reply, I need an stable rom based on cyanogenmod, please recommend one to me, thank you very much
Hi Pavel,
The data connection is not valid.
Goes offline than turn it on again, but nope. The data connection still cannot turned on. Restarting the phone for several times also still persist.
goku1234567890 said:
Open rom zip file and extract boot.img to your memory card. Go to recovery and make sure your current rom is backed up. Then go to wipe and do factory reset. Then go to install and flash this rom. Then flash the gapps provided in the first page. Then go to the install option in recovery and click "images" option then find the boot.img file you extracted earlier in your card and then flash boot.img only. And then your rom should boot up and start working in 10 min or so.
Sent from my H30-U10 using XDA-Developers mobile app
Click to expand...
Click to collapse
thanks you very much Finally Solved:good::good:
{
"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'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
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 Suicide Squirrel and LineageOS Github repos.
If you would like to contribute to do not hesitate to submit patches
**** These builds are for UsU'd devices only ****
UsU? http://bit.do/unlockg4
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM 20p or higher! (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable N modem (recommended)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Flash GApps (8.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Download
Get your builds from my leech server
http://leech.binbash.it:8008/lineage/oreo/h815-UsU/
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Known issues:
Check the current issues at the github tracker (feel free to help, provide logs etc!)
Credits
LineageOS
ThePiGuy
kessaras
steadfasterX
and more..
Sources
LineageOS
Kernel
device tree
build manifest
XDA:DevDB Information
lineage-usu-h815, ROM for the LG G4
Contributors
steadfasterX, ThePiGuy, kessaras
Source Code: https://github.com/Suicide-Squirrel/local_manifests/tree/los-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 20p or higher firmware
Based On: pure LineageOS
Version Information
Status: Beta
Created 2018-06-20
Last Updated 2019-07-10
Reserved
Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX
emrtnl said:
Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX
Click to expand...
Click to collapse
Thanks for offering your help but unfortunately you can't do anything at the moment. I'm working on it at highest priority because I need it by myself but this issue is absolutely a nightmare and not easy to fix
Sent from my LG-H815 using XDA Labs
Thank You!
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow
igorgpsouza said:
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow
Click to expand...
Click to collapse
BT music is ok but calls has that bad noise.
Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.
Rich Rich said:
Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.
Click to expand...
Click to collapse
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
adb shell
su
logcat -b all -c
logcat -b all
(now immediately reproduce the crash)
ctrl+c to cancel
Click to expand...
Click to collapse
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)
steadfasterX said:
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)
Click to expand...
Click to collapse
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
no. all good.
Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen
steadfasterX said:
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen
Click to expand...
Click to collapse
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee
Rich Rich said:
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee
Click to expand...
Click to collapse
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.
steadfasterX said:
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.
Click to expand...
Click to collapse
Just tried that. Still the same.
Tried it twice, once as you said then again by picking all the wipe options. If I try set a password or code it will crash then ask me to re-enter the password which always fails.
Think I'll just use it without a lockscreen.
New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.
Rich Rich said:
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.
Click to expand...
Click to collapse
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output
steadfasterX said:
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output
Click to expand...
Click to collapse
I've attached a screenshot of my SALT window. Hope this shows the info needed.
Rich Rich said:
I've attached a screenshot of my SALT window. Hope this shows the info needed.
Click to expand...
Click to collapse
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.
steadfasterX said:
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.
Click to expand...
Click to collapse
Don't know where the backup files are stored. I just have SALT installed in a standalone VMWare Linux machine, I'm not Linux literate so not sure where to start looking for the files. What's the default backup location?
LineageOS 20.0 for Sony Xperia XZ1 Compact
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1 Compact, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
DOWNLOAD
ROM: https://sourceforge.net/projects/yoshino/files/lilac/lineage-20.0/
TWRP: https://sourceforge.net/projects/yoshino/files/lilac/twrp/
Suggested Gapps (MTG): http://downloads.codefi.re/jdcteam/javelinanddart/gapps (choose 13.0.0/arm64)
Check the ChangeLog below for firmware requirements!
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Or if you are coming from Lineage 19.x, dirty flash to 20.0 is possible too: flash the new TWRP, ROM, and GApps, su addons (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread.
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, sohrab1985
Source Code
https://github.com/whatawurst/android_device_sony_lilac
https://github.com/whatawurst/android_kernel_sony_msm8998
https://github.com/whatawurst/android_device_sony_yoshino-common
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-10
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
REQUIRED FIRMWARE:
CHANGELOG
Suggested Gapps (MindTheGapps) - choose 13.0.0/arm64:
https://androidfilehost.com/?w=files&flid=322935 or http://downloads.codefi.re/jdcteam/javelinanddart/gapps
v1.2 (2023-05-10):
Updated to T QPR2 release (LineageOS upstream)
Updated to May 2023 Security updates (both ROM and kernel)
Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
Fully enabled IMS on Congstar Germany via overlay on lilac
Possibly some battery/performance optimizations here and there
Fixed Android Auto support
Added new LineageOS "Charging control hal" for battery charging care (3)
Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream is LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
2023-01-08 | 1.1 | 47.2.A.11.228
- Updated to T QPR1 release (LineageOS upstream)- New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)- Any other updates by LineageOS upstream- Kernel security updates (also thanks to Flamefire)- Dropped keyprovd service - it is useless on unlocked BL anyway- Show 4G instead of LTE icon - saves some space too- Enable IMS by default - this still only works if carrier is supported- Fix some selinux denials (also thanks to Flamefire)- Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
2022-10-03 | 1.0 | 47.2.A.11.228
Initial release
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
Sneexy said:
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
Click to expand...
Click to collapse
did you format data
reboot to recovery
wipe all internal portions
reboot to recovery
then flash rom
just curious because i was gona try it
victor126 said:
did you format data
reboot to recovery
wipe all internal portions
reboot to recovery
then flash rom
just curious because i was gona try it
Click to expand...
Click to collapse
Yes, multiple times.
Dirty flash from 19.1 and all work! Thanks
I have done clean flash and I don't get any notifications or call screen on phone calls causing missed calls. No problems on wifi and mobile
susetoyix said:
I have done clean flash and I don't get any notifications or call screen on phone calls causing missed calls. No problems on wifi and mobile
Click to expand...
Click to collapse
Weird, first time hearing this. Everything works just fine for me.
sohrab1985 said:
Weird, first time hearing this. Everything works just fine for me.
Click to expand...
Click to collapse
Kinda not recurring anymore after a few more reboots. I'll keep a lookout on this.
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
azndan2 said:
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
Click to expand...
Click to collapse
t mobile and its nvmo's are the only place this phone is not white listed
rez78 said:
Dirty flash from 19.1 and all work! Thanks
Click to expand...
Click to collapse
does split screen work on 20. it didnt work for me on 19.1
victor126 said:
t mobile and its nvmo's are the only place this phone is not white listed
Click to expand...
Click to collapse
Could you be more specific? I believe it's blacklisted on AT&T. It doesn't work at all on Verizon, because it has the wrong bands.
I've seen plenty of reports of it working on T-Mobile.
How does it work compared to 19.1? Any bugs?
azndan2 said:
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
Click to expand...
Click to collapse
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
norabitox said:
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
Click to expand...
Click to collapse
What do I replace the contents with?
tonsofquestions said:
Could you be more specific? I believe it's blacklisted on AT&T. It doesn't work at all on Verizon, because it has the wrong bands.
I've seen plenty of reports of it working on T-Mobile.
Click to expand...
Click to collapse
correct. t mobile and mint, and others that use t mobile work.
azndan2 said:
What do I replace the contents with?
Click to expand...
Click to collapse
carrierconfig.xml for the LOS version that LTE was working on your phone
victor126 said:
correct. t mobile and mint, and others that use t mobile work.
Click to expand...
Click to collapse
Sorry, what? Can you please be more specific?
First you said it was _not_ whitelisted on T-Mobile (so presumably doesn't work) and now you say it _does_ work on T-Mobile.