{
"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 a free, community built, aftermarket firmware distribution of Android 11, 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 LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/pioneer
Downloads :
https://download.lineageos.org/pioneer
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
0
Seppppx said:
@LuK1337
By WFD you mean Wi-Fi direct or Wi-Fi display?
Click to expand...
Click to collapse
Latter one.
Amazing!
Thank you very much and outstanding work OP! I got this device last week installed LOS17.1 right away, and there is v 18 already in the works! So cool.
drkshdwprophet said:
Thank you very much and outstanding work OP! I got this device last week installed LOS17.1 right away, and there is v 18 already in the works! So cool.
Click to expand...
Click to collapse
Did u install it ?
Can I say what's working and what not?
Arbaazhussain said:
Did u install it ?
Can I say what's working and what not?
Click to expand...
Click to collapse
Do it yourself.
LuK1337 said:
Do it yourself.
Click to expand...
Click to collapse
Ok and it was quick reply
---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------
Should I use nikgapps android 11?
Will it work?
Arbaazhussain said:
Ok and it was quick reply
---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------
Should I use nikgapps android 11?
Will it work?
Click to expand...
Click to collapse
God only knows.
LuK1337 said:
God only knows.
Click to expand...
Click to collapse
Ok I will try
Root which magisk version should be used?
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
Sir can u say me what are changes brought with everyday build?
Arbaazhussain said:
Ok I will try
Root which magisk version should be used?
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
Sir can u say me what are changes brought with everyday build?
Click to expand...
Click to collapse
Do I look like someone who'd use Magisk? Also no, I'm not going to put my time into writing changelogs.
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
emc02 said:
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
Click to expand...
Click to collapse
Yeah, it is quite possible that @Arbaazhussain and other people asking about official builds / future plans will annoy me so much that I'll just drop support entirely.
emc02 said:
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
Click to expand...
Click to collapse
The builds is always unofficial unless the lineage 18 is released as stable and then maintainers can make it official
So it is unofficial now
later official if luk sir does of course
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
LuK1337 said:
Yeah, it is quite possible that @Arbaazhussain and other people asking about official builds / future plans will annoy me so much that I'll just drop support entirely.
Click to expand...
Click to collapse
Sorry if I have annoyed you
I ask for forgiveness from the depth of my heart
Goddamn, didn't expect this one. Gonna try this one soon
i have installed this ROM. very good. no problems. also have installed nikgapps BASIC. everything is OK. thanks to the dev luK1337
Enviado do meu H4113 através de Tapatalk
Is there a way to activate VOLTE? I thought VOLTE and wifi calling were options on LOS 17. I had bricked this phone trying to update to the last LOS 17 and has been unused for a month or so, so I might be thinking of a rom I had on my XZP. Either way works good so far except I haven't been able to activate it on my new carrier, but that's another story.
Error installing
Hello,
I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.
The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Any help would be greatly appreciated,
Thanks.
DarkInvaderr said:
Hello,
I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.
The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Any help would be greatly appreciated,
Thanks.
Click to expand...
Click to collapse
Try to fastboot boot latest twrp instead.
LuK1337 said:
Try to fastboot boot latest twrp instead.
Click to expand...
Click to collapse
Tried doing that but i either get FAILED (Write to device failed in SendBuffer() (Too many links)) or FAILED (Write to device failed (no link)).
Flashed my firmware again just in case so i guess its not hard bricked?
Ill try to fastboot boot from a different PC to see if the issue is there.
Thanks for replying.
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"
}
Ahoy! Once again, PA's back (for our device, I mean)! This time, this ROM isn't based on CM rather AOSP (The nexus sources). I don't know if there will be legacy sources as such, but looking at how today's ROMs are basing themselves off of AOSP-CAF and AOSP, I don't think they will but hey enough with the reading already, go enjoy the ROM
Bugs:
Gapps may not install on first boot, you'll have to boot ROM first, then flash gapps, then wipe data and then boot.
Keypress light is back to the old always-on kinda style (Tried various things, wouldn't work :/)
NOTE: This ROM is based on AOSP so it has that weird chipset-specific boot issue. So flash the included zip (Thanks @orsonbear)
NOTE2: If you face error 7, you can scroll down to post#3 for installation instructions
Download:
AndroidFileHost
Bootloop fix (for users who can't boot their device)
Even then if the zip doesn't work, you can try @orsonbear's fix or @turbolukex5's fix
Credits:
Paranoid Android team
Slim team (AOSP-CAF)
mcgi5sr2
ivan_meler
Sources:
Kernel
i like skittles
XDA:DevDB Information
AOSPA for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
Gokulbalram
Source Code: https://github.com/AOSPA
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-07-05
Last Updated 2016-08-02
Reserved
FAQ:
Q. Why is there only 770~MB of RAM?
A. The kernel comes with CMA on which gives better performance and stability at the cost of memory
Q. Why won't my device boot?
A. This is a chipset related issue. But don't worry, instructions are in the OP
Q. What is the difference between AOSP and AOSP-CAF?
A. Slightly OT, but since many might be confused, AOSP ROMs are based on the Android source straight from Google, while AOSP-CAF (Code Aurora Forums) is optimized for Snapdragon devices in general and has slight enhancements for better Hardware-Software symbiosis (not the right word but I hope you get the point).
Installation Instructions
If the traditional wipe, flash, boot works for you, very well. But if you face error 7, you can follow the following procedure:
1) Once you face the error, wipe data, system and both the caches
2) Reboot Recovery (Do not let it root for you)
3) Flash ROM (and cfw zip if you have the chipset issue)
mobile data not working
luffy94 said:
mobile data not working
Click to expand...
Click to collapse
Just realized that, I will build a new package with RIL working.
Sorry for the delay guys
Yes! Finally PA for our device. waiting for the link.
Sent from my GT-I9300 using XDA-Developers mobile app
hopefully we see DU soon too,would love to try DU MM build,one of the most popular roms these days
but never the less ,thx for this awesome new rom,will definitely try it when you up new build
you are the king of AOSP roms for our s3 hehe
I'm downloading the rom right now. I don't care about not working RIL Will write back if there are ny other issues
---------- Post added at 13:38 ---------- Previous post was at 13:08 ----------
OK, so ROM is very fast. I mean, extremely fast Hope the RIL will get fixed soon, because restoring EFS from backup didint work for me.
---------- Post added at 13:39 ---------- Previous post was at 13:38 ----------
And, for me, the camera makes photos roated at 90 degrees angle
aciupapa said:
I'm downloading the rom right now. I don't care about not working RIL Will write back if there are ny other issues
---------- Post added at 13:38 ---------- Previous post was at 13:08 ----------
OK, so ROM is very fast. I mean, extremely fast Hope the RIL will get fixed soon, because restoring EFS from backup didint work for me.
---------- Post added at 13:39 ---------- Previous post was at 13:38 ----------
And, for me, the camera makes photos roated at 90 degrees angle
Click to expand...
Click to collapse
Okay. Mind telling me about the features the ROM has?
Sent from my GT-I9300 using XDA-Developers mobile app
Just watch this video https://www.youtube.com/watch?v=8c1zymMY-Z8
Alrighty! New build is up
Grab it here
Also, if any of the chaps who have the bootloop issue can check out the fix zip and let me know if it works, it'd be awesome
Thank You @Gokulbalram for this rom It works flawlessly, but video recording on snapchat is broken (wrong colors) and the rotaded images coming out of camera. Hope You can fix them somehow
aciupapa said:
Thank You @Gokulbalram for this rom It works flawlessly, but video recording on snapchat is broken (wrong colors) and the rotaded images coming out of camera. Hope You can fix them somehow
Click to expand...
Click to collapse
As for Snapchat, does the video go through?
Also for pictures, I'd suggest you use Google Camera as that one has 0 issues with orientation
After holding camera icon on snapchat i have to wait for 5 sec, then it starts recording in normal colors, after i leave the recording button, the video has messed up colors.
Is there any way to turn keypress light OFF ?
If i install boeffla kernel?
@up you can install xposed framework and gravitybox to control button light scenario or as You written above, flash boeffla ANY-kernel zip
---------- Post added at 15:30 ---------- Previous post was at 15:26 ----------
@Gokulbalram I'm experiencing random reboots on every AOSP 6.0 based rom (Haxynox, Slim, Tesla and PA) Am I doing something wrong when flashing, or it is a ROM issue?
---------- Post added at 15:44 ---------- Previous post was at 15:30 ----------
BTW, I've flashed agni PureCM any kernel and i can charge my phone (Before it wasnt charging on PA) and control the key lighting up scenario,
spizzicalino said:
Is there any way to turn keypress light OFF ?
If i install boeffla kernel?
Click to expand...
Click to collapse
aciupapa said:
@up you can install xposed framework and gravitybox to control button light scenario or as You written above, flash boeffla ANY-kernel zip
---------- Post added at 15:30 ---------- Previous post was at 15:26 ----------
@Gokulbalram I'm experiencing random reboots on every AOSP 6.0 based rom (Haxynox, Slim, Tesla and PA) Am I doing something wrong when flashing, or it is a ROM issue?
---------- Post added at 15:44 ---------- Previous post was at 15:30 ----------
BTW, I've flashed agni PureCM any kernel and i can charge my phone (Before it wasnt charging on PA) and control the key lighting up scenario,
Click to expand...
Click to collapse
Boeffla Any-Kernel does not work.
AGNi kernel works though.
When do you see these reboots?
@Gokulbalram sometimes when I put device to sleep it reboots, or when the device freezes (when not doing any heavy task), or i install app from playstore, the device sot reboots.
aciupapa said:
@Gokulbalram sometimes when I put device to sleep it reboots, or when the device freezes (when not doing any heavy task), or i install app from playstore, the device sot reboots.
Click to expand...
Click to collapse
That's very weird. Do you have any kernel settings set as such?
No, I have soft reboots on PA stock kernel provided with this rom as well as on AGNi kernel. I will test a little bit with AGNi and will let you know how it works. Also on every AOSP based rom there is an issue that i reported in Tesla's thread, when sometimes your Wi-Fi card mac adress changes to 02:00:00:00:00:00 where it should be 88:32:9b:58:3b:ba
{
"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:
/* *** Disclaimer
* I'm 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/KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
* BOOM! goes the dynamite
*/
[COLOR="181818"]About Project New World[/COLOR]
Hi XDA community, we are proud to present our vision of Android based on AOSP with features that we think are useful.
The main goal of Project New World is to provide a clean and fast ROM with nice and useful features.Thanks for your
attention and we hope you will enjoy our builds as much as we do.
[COLOR="181818"]Warning[/COLOR]
This build is based on B32 blobs so it requires an updated bootloader + modem. (They can be found in the download section)
Also is this a BETA build that means you may face high battery drain, force closing apps etc. Please be aware of this.
[COLOR="181818"]Features[/COLOR]
Coming soon
[COLOR="181818"]Bugs[/COLOR]
VoLTE
(Speaker bug) [While calling toggle loudspeaker to avoid]
(Dual Sim) [If you get no in call audio try to switch data sims etc.]
[COLOR="181818"]Installation instructions[/COLOR]
Attention! The bootloader needs to be unlocked
1. Update your version of TWRP (3.2.1-0 or > recommended) [Download]
2. Perform a backup of your current ROM (optionally)
3. Wipe system,data and cache (optionally) [Needed if coming from another rom!; always good to avoid bugs]
4. Install the Universal B32 bootloader and your model specific modem.
5. Install Project New World
6. Install GApps (optionally) [Recommended -> Unofficial Open GApps (arm64) (8.1)]
7. Reboot
[COLOR="181818"]Source[/COLOR]
Kernel
Device tree
Vendor to be continued..
[COLOR="181818"]Download[/COLOR]
Bootstack - B32 and modems
Project New World Beta Builds
[COLOR="181818"]Credits[/COLOR]
LineageOS
Unjustified Dev
DrakenFX
(If you think you should be on the list hit me up)
XDA:DevDB Information
Project New World - O_MR1, ROM for the ZTE Axon 7
Contributors
OrdenKrieger
Source Code: https://github.com/ProjectNewWorld
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Created 2017-12-31
Last Updated 2018-01-31
Frequently Asked Questions
Do I need to update my bootstack before flashing?
Yes, if you don't come from B32 stock it's necessary to update your boostack and modem. That files
can be found under the download section.
Does this rom support modifications?
No, because I don't know how every modification out there exact works which can cause
problems with debuging and overall stability.
Does this rom support custom kernels?
No, because this falls under the same section as modifications, but every kernel that is based
on the source of the stock kernel of this rom, should work fine.
Will you add feature or app XYZ?
No, our team decides democratically and we only want unique or necessary features
without overloading the rom. Also should the rom work the same no matter which device
it's used on.
Why isn't everything working flawlessly?
Remember, this is a Beta build for testing purposes. Also are this build based on old
N proprietary blobs and since ZTE didn't release any new for now it's impossible to fix
certain issues.
When will a new build drop?
When I think it's alright. I don't want to release untested work.
Downloading. Thank you very much for your work.
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Gases said:
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Click to expand...
Click to collapse
Flash universal bootloader
I installed it as soon as it hit AFH. Flashed bootloader and modem. No problems with install other than a corrupt sd notice. Working on that. Data/Wifi/Bluetooth operational. The camera doesn't fc but is very dark and takes dark images. Known issue, so let's move on. Substratum works. Mono looks sweet on 8.1. The big cluster doesn't seem to be downclocking on Interactive. Switching to Conservative solves that. Too early to tell much else. Gratz on a solid first release!
Edit: I backed up my SD card, formatted it and copied everything back. It's working fine. I've had this problem with a few other Oreo builds. Not sure why Oreo sees it as corrupted initially.
Gases said:
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Click to expand...
Click to collapse
you installed the B32 bootloader.
https://androidfilehost.com/?fid=962157660013068930
t started off well for me.
WesTD said:
Flash universal bootloader
Click to expand...
Click to collapse
I tried flashing the universal bootloader provided in the OP. It still shows the same error.
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
kenet said:
you installed the B32 bootloader.
https://androidfilehost.com/?fid=962157660013068930
t started off well for me.
Click to expand...
Click to collapse
Just tried that one as well, no difference.
I'm flashing that first, then the A2017U B32 modem provided in the OP, and then flashing the ROM. It shows error 7, and it says that my device name isn't correct.
Gases said:
I tried flashing the universal bootloader provided in the OP. It still shows the same error.
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
Just tried that one as well, no difference.
I'm flashing that first, then the A2017U B32 modem provided in the OP, and then flashing the ROM. It shows error 7, and it says that my device name isn't correct.
Click to expand...
Click to collapse
Surely you downloaded corrupted the zip.
Gases said:
I tried flashing the universal bootloader provided in the OP. It still shows the same error.
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
Just tried that one as well, no difference.
I'm flashing that first, then the A2017U B32 modem provided in the OP, and then flashing the ROM. It shows error 7, and it says that my device name isn't correct.
Click to expand...
Click to collapse
No mine sis the same to. Left my device name as blank lol. Had to manually remove the trust zone. Try redownloading it or go in and change it to blank like i did
kenet said:
Surely you downloaded corrupted the zip.
Click to expand...
Click to collapse
I honestly don't think so. I just re-downloaded everything, flashed everything and got the exact same error. What can I do?
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
reV17 said:
No mine sis the same to. Left my device name as blank lol. Had to manually remove the trust zone. Try redownloading it or go in and change it to blank like i did
Click to expand...
Click to collapse
How can I do that? I've tried doing it, but I get an error saying the ZIP file is in an incorrect format.
I'm sorry for asking so much, I'm a complete noob and I can't find information on this
Gases said:
I honestly don't think so. I just re-downloaded everything, flashed everything and got the exact same error. What can I do?
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
How can I do that? I've tried doing it, but I get an error saying the ZIP file is in an incorrect format.
I'm sorry for asking so much, I'm a complete noob and I can't find information on this
Click to expand...
Click to collapse
can you confirm, what version of TWRP are you using? Try using the latest. That fixed my problem. Still had the N1 version installed
reV17 said:
can you confirm, what version of TWRP are you using? Try using the latest. That fixed my problem. Still had the N1 version installed
Click to expand...
Click to collapse
I'm using version 3.1.1-0. I just tried removing the assert and got error 6 while trying to flash.
Gases said:
I'm using version 3.1.1-0. I just tried removing the assert and got error 6 while trying to flash.
Click to expand...
Click to collapse
Flash the latest TWRP 3.2.1-0 using TWRP and then flash the unmodified zips
Gases said:
I'm using version 3.1.1-0. I just tried removing the assert and got error 6 while trying to flash.
Click to expand...
Click to collapse
3.1.1-0 is janky. I had problems with Oreo and that version. 3.2.1-0 seems solid.
Would you look at that... Updating TWRP solved it! Thanks, guys! @Cablespider @reV17
Can I root this ROM? Or is Magisk incompatible with Oreo?
Magisk 15.1 is running fine.
Gases said:
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Click to expand...
Click to collapse
Update your TWRP. Forgot to mention that.
is footej camera working good ?
deleted
{
"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"
}
Android. Infused with magical unicorn bytes
The unicorn eats Pie and farts rainbows
INFO
Read about AOKP and Team Kang here
This is an unofficial build of AOKP Pie release with MicroG support and embedded SU.
DISCLAIMER
* By flashing this, you automatically void your warranty!
* You are installing this software at your own risk
* I am not responsible if your phone, SD card or anything else breaks or causes damage of any kind to anything as a result of flashing this ! Remember, you flashed this at your own free will!
A. Initial install
1. Copy ROM and Gapps (optional) to your external SD Card or internal memory
2. Boot into recovery (latest TWRP preferred)
3. Wipe Dalvik/ART Cache, Cache, System and Data
4. Install ROM and Gapps (optional)
5. Reboot
B. Updates
1. Copy ROM to your external SD Card or internal memory
2. Boot into recovery (latest TWRP preferred)
3. Wipe Dalvik/ART Cache and Cache
4. Install ROM
5. Reboot
Serranodsdd (GT-I9192)
Serrano3gxx (GT-I9190)
Serranoltexx (GT-I9195)
Gapps:
Open Gapps
NOT WORKING
Everything should be working, please report issues if found
Changelog in ROM Control
Gerrit:
AOKP Gerrit
LineageOS
CREDITS
This is not my work, all credit goes to the developers:
- Google
- Lineage Team
- Team Kang
- @arco68
- LineageOS
- AOKP
XDA:DevDB Information
AOKP Pie, ROM for the Samsung Galaxy S4 Mini
Contributors
csendre
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2019-03-05
Last Updated 2020-01-20
reserved
Thank you, to try.
It doesn't work Substratum. No changes when activating layers.
@soulreaver13mejia look at this: https://forum.xda-developers.com/showpost.php?p=76687502&postcount=8
You will need to enable root
seems there are still some issues with APN settings, the team is working on sorting it out.
Finally . Did you base this on LOS 16.0? The only problem I had with it was Screencast. I hope you'll find a solution.
csendre said:
@soulreaver13mejia look at this: https://forum.xda-developers.com/showpost.php?p=76687502&postcount=8
You will need to enable root
Click to expand...
Click to collapse
There was already root activator and it didn't work that way, but I went back to 8.1 and a question with trebuchet recent applications look like in Pie but if I put Nova Launcher they come back like before Oreo, because that happens?
faizankhalifa said:
Finally . Did you base this on LOS 16.0? The only problem I had with it was Screencast. I hope you'll find a solution.
Click to expand...
Click to collapse
Chromecast should be working. Miracast/wi-fi display support was removed in Pie and to my knowledge there is no workaround solution to make it work.
For some devices they started using Qualcomm's Wifi display implementation. Not sure if that is an option for us; I asked Arne
csendre said:
seems there are still some issues with APN settings, the team is working on sorting it out.
Click to expand...
Click to collapse
Right. In may case the APN screen was blank. I had to set up the APN manually and it worked fine.
Another issue is related to screen rotation. Turning the phone 90 degrees the screen keeps as it was, it not goes to horizontal.
And last, I was not able to root the phone whit magisk.
I will trying it.
The most important, thank so much for keeping upgraded our old devices
Ulises31 said:
Right. In may case the APN screen was blank. I had to set up the APN manually and it worked fine.
Another issue is related to screen rotation. Turning the phone 90 degrees the screen keeps as it was, it not goes to horizontal.
And last, I was not able to root the phone whit magisk.
I will trying it.
The most important, thank so much for keeping upgraded our old devices
Click to expand...
Click to collapse
Can't add any APN manually, it says "Settings for APN are not available for this user". Just have the option to "set to standard" but this does nothing.
onkelfeix said:
Can't add any APN manually, it says "Settings for APN are not available for this user". Just have the option to "set to standard" but this does nothing.
Click to expand...
Click to collapse
Do you see the plus sign (+) next to the search button? Don't forget to save your new apn via the menu...
nussbaum said:
Do you see the plus sign (+) next to the search button? Don't forget to save your new apn via the menu...
Click to expand...
Click to collapse
White on light grey, couldn't see it....
Now my temp-phone is working well , thanks alot.
Ulises31 said:
Right. In may case the APN screen was blank. I had to set up the APN manually and it worked fine.
Another issue is related to screen rotation. Turning the phone 90 degrees the screen keeps as it was, it not goes to horizontal.
And last, I was not able to root the phone whit magisk.
I will trying it.
The most important, thank so much for keeping upgraded our old devices
Click to expand...
Click to collapse
Hopefully APN will be fixed in next build.
Screen rotation works just fine now in latest build. Make sure that you enabled it. You can also try a clean flash if you dirty flashed from previous one.
You'll have to talk to Magisk developers; not a ROM issue. In the meantime enable embedded root in developer options.
Sim not working is there a solution The model is GT-I9192
---------- Post added at 08:51 PM ---------- Previous post was at 08:27 PM ----------
Sim not working is there a solution model GT-I9192
ahmed20001 said:
Sim not working is there a solution The model is GT-I9192
---------- Post added at 08:51 PM ---------- Previous post was at 08:27 PM ----------
Sim not working is there a solution model GT-I9192
Click to expand...
Click to collapse
If you have already done a clean flash try updating your modem. Some people were having this issue on older JB modems
New builds are up with March security patches.
APN should be working now, at least it does for me. Please report back.
csendre said:
New builds are up with March security patches.
Click to expand...
Click to collapse
Clean flash went fine on my serranoltexx. However root is not working. Default is set to "Apps and ADB" (in Developer Options -> Root access), but Kernel Adiutor tells me there is no root. Setting to "Disabled" and re-setting it to "Apps and ADB" does not work either.
ernsteiswuerfel said:
Clean flash went fine on my serranoltexx. However root is not working. Default is set to "Apps and ADB" (in Developer Options -> Root access), but Kernel Adiutor tells me there is no root. Setting to "Disabled" and re-setting it to "Apps and ADB" does not work either.
Click to expand...
Click to collapse
Tested it, you are right. The apps and ADB is the one that should be working, it means that root access can be granted to both apps and commands over ADB. Not sure what is going on though, this is coming from Lineage, AOKP doesn't use a custom SU in Pie. Will have to investigate further. Does anyone knows if this worked in previous version from March 05? I noticed there was a commit added by Lineage on March 6, maybe that broke it?
Update: also tried flashing SU from here: https://download.lineageos.org/extras but it didn't work either so definitely seems to be a Lineage SU issue
csendre said:
Does anyone knows if this worked in previous version from March 05? I noticed there was a commit added by Lineage on March 6, maybe that broke it?
Click to expand...
Click to collapse
Nope, didn't work either. I wanted to verify this on the current version just to be sure.
{
"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 a free, community built, aftermarket firmware distribution of Android 5, 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 LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.Instructions:
Reboot to recovery mode
Wipe data, system and cache
Flash the ROM and the GAPPs
Reboot and enjoy!
Downloads:
ROM: https://androidfilehost.com/?fid=4349826312261660645
GApps: Open Gapps (arm64/5.1/tvmini)
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Known issues:
HW decoding
Wi-Fi direct
Notes:
SELinux is in Permissive mode
The ROM only supports sloane
How do i...
Unlock and install TWRP?
Follow the instructions of the unlock thread
Go back to the original/stock ROM?
Download the stock update.bin and flash it using TWRP
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Changelog
2019-12-09
Initial release.
Reserved
Reserved
reserved
Does it Have the Rbox boot Menu installed so we don't lose access to TWRP
Toothless_NEO said:
Does it Have the Rbox boot Menu installed so we don't lose access to TWRP
Click to expand...
Click to collapse
Yes. The ROM will install it. Don't worry
Regards.
Great work dude. A tip tor everyone is simply backup system and data in TWRP of both fire os and then this rom and you can seemlessly but slowly switch between the two (if ever required)
Dualboot would be nice hahaha
CFKod said:
Great work dude. A tip tor everyone is simply backup system and data in TWRP of both fire os and then this rom and you can seemlessly but slowly switch between the two (if ever required)
Dualboot would be nice hahaha
Click to expand...
Click to collapse
Thanks
Yeah, agreed, dualboot would be nice but we need SafeStrap for that
Regards.
Hell yeah, it's up! Awesome work dude!
Side note: it would be cool if anyone could let us know if the WiFi direct remote fix is working for them?
The fix works for me, but when remote goes to sleep after being idle for too long I have to manually reconnect it, which is a bit of a hassle as involves a few adb commands to get to the correct settings menu.
In an ideal world, we would be using ozwpan (I think?) to store the remote's SSID & reconnect automatically upon a keypress (like Amazon does), but unfortunately I don't seem to be able to get ozwpan to write to to /sys/class/, so unless someone with more knowledge on the subject can weigh in on this matter (any Shield TV devs here? ), we will probably have to use the current method until someone figures out how to unlock the bootloader.
If reconnecting is an issue, I'm sure @Rortiz2 could probably include a script that reconnects automatically (like init.fosflags.sh does), but it'd probably have to be manually triggered from an adb shell command.
DanielF50 said:
If reconnecting is an issue, I'm sure @Rortiz2 could probably include a script that reconnects automatically (like init.fosflags.sh does), but it'd probably have to be manually triggered from an adb shell command.
Click to expand...
Click to collapse
Good shout dude. I'd say Tasker can do that... Ie. When awoken from sleep, run adb command
If I need to use a USB device will it work if I turn ADB off or is that dangerous/bricking?
Toothless_NEO said:
If I need to use a USB device will it work if I turn ADB off or is that dangerous/bricking?
Click to expand...
Click to collapse
You can turn off ADB. There's no problem.
Regards.
Enviado desde mi WAS-LX1A mediante Tapatalk
I have installed the rom fine but can not get remote to pair. I can see it in the searching for accessories screen then it goes to a settings screen. Then I can not do anything. I have tried 3 different remotes. Maybe I'm missing something but I think I'm following the instructions fine. I wait for the searching for accessories screen then hold the home key for 15-20 seconds, the remote shows up then after about 10 seconds it goes to settings screen and I can't do anything. How can I connect through ADB? Thank you for any help.
brick00444 said:
I have installed the rom fine but can not get remote to pair. I can see it in the searching for accessories screen then it goes to a settings screen. Then I can not do anything. I have tried 3 different remotes. Maybe I'm missing something but I think I'm following the instructions fine. I wait for the searching for accessories screen then hold the home key for 15-20 seconds, the remote shows up then after about 10 seconds it goes to settings screen and I can't do anything. How can I connect through ADB? Thank you for any help.
Click to expand...
Click to collapse
Hi. Are you using sloane's remote?
It shouldn't show up at the first screen... It should show up at that Settings Screen (Wi-Fi Direct screen).
Regards.
Rortiz2 said:
Hi. Are you using sloane's remote?
It shouldn't show up at the first screen... It should show up at that Settings Screen (Wi-Fi Direct screen).
Regards.
Click to expand...
Click to collapse
To be honest I'm not sure if it is the original remote. Is the original remote the little one? I'm using model-PE59CV
brick00444 said:
To be honest I'm not sure if it is the original remote. Is the original remote the little one? I'm using model-PE59CV
Click to expand...
Click to collapse
Sounds like you're using a BT remote
Are you using this remote?
Cheers.
Rortiz2 said:
Sounds like you're using a BT remote
Are you using this remote?
Cheers.
Click to expand...
Click to collapse
Yes I am. I just noticed I have another one that looks the same but different model number trying it now.
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
no luck
brick00444 said:
Yes I am. I just noticed I have another one that looks the same but different model number trying it now.
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
no luck
Click to expand...
Click to collapse
What model is the new one that you tried?
Regards.
Model- DR49WK B
{
"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 18.1 is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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.
The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features
Installing
Please follow the instructions at lineageos wiki
Clean flash if coming from UNOFFICIAL LineageOS or a different ROM
Downloads
Official builds
Unofficial builds: sourceforge
What a wonderful surprise ! Thank you !!!!
And thank you to @arco68 as well [emoji16]
@aleasto: Grazie mille, caro amico ...
And huge thanks - I think from all of us - to @arco68. You saved our phones ...
It's just driving me nuts. I can't install the setup wizard on BiTGApps-arm-10.0.0-R17_signed.zip, although setup-config.prop is in the root directory of the internal sd card as it should be. I reported the problem to the developer of BiTGApps about a year ago and it still continues unsolved. Maybe I'm making some mistake or else I'll just have to wait for OpenGApps for Android R ...
Very nice! Thanks!
I'll try to flash it today.
Any info on what's not working in this build?
I tried it earlier and the internet does not work with the mobile network.
Flashed the new R firmware today and it's magic! R for the G2 D802:laugh::good: I also installed BitGapps https://bitgapps.cf/arm/R/
My first experience (without a simcard in it). It feels snappy and that's great news. Wifi is working fine and streaming through bluetooth with TuneIn radio app is also working fine. Great start!
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
theelderstatesman said:
It's just driving me nuts. I can't install the setup wizard on BiTGApps-arm-10.0.0-R17_signed.zip, although setup-config.prop is in the root directory of the internal sd card as it should be. I reported the problem to the developer of BiTGApps about a year ago and it still continues unsolved. Maybe I'm making some mistake or else I'll just have to wait for OpenGApps for Android R ...
Click to expand...
Click to collapse
You are using the wrong version. Use BitGapps for Android 11 (see link in my other post). Working fine for me with this version.
BiG_FooT said:
Flashed the new R firmware today and it's magic! R for the G2 D802:laugh::good: I also installed BitGapps https://bitgapps.cf/arm/R/
My first experience (without a simcard in it). It feels snappy and that's great news. Wifi is working fine and streaming through bluetooth with TuneIn radio app is also working fine. Great start!
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
U are using the wrong version. Use BitGapps for Android 11 (see link in my other post). Working fine for me with this version.
Click to expand...
Click to collapse
I was tired. I think I copied the wrong file name. I think it was the right version. Did you use the setup wizard? Did it work for you?
---------- Post added at 06:10 PM ---------- Previous post was at 05:52 PM ----------
BiG_FooT said:
Flashed the new R firmware today and it's magic! R for the G2 D802:laugh::good: I also installed BitGapps https://bitgapps.cf/arm/R/
My first experience (without a simcard in it). It feels snappy and that's great news. Wifi is working fine and streaming through bluetooth with TuneIn radio app is also working fine. Great start!
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
U are using the wrong version. Use BitGapps for Android 11 (see link in my other post). Working fine for me with this version.
Click to expand...
Click to collapse
I just tried it again with BiTGApps-arm-11.0.0-R17_signed.zip. Same thing - setup wizard just doesn't work, but thanks anyway for trying to help me ...
theelderstatesman said:
I was tired. I think I copied the wrong file name. I think it was the right version. Did you use the setup wizard? Did it work for you?
---------- Post added at 06:10 PM ---------- Previous post was at 05:52 PM ----------
I just tried it again with BiTGApps-arm-11.0.0-R17_signed.zip. Same thing - setup wizard just doesn't work, but thanks anyway for trying to help me ...
Click to expand...
Click to collapse
Yes, no problem with setup wizard. My phone is D802
BiG_FooT said:
Yes, no problem with setup wizard. My phone is D802
Click to expand...
Click to collapse
Thanks so much. I wish I knew what I'm doing wrong here. Do you place setup-config.prop in the root directory of the internal sd card? Is it there along with BiTGApps-arm-11.0.0-R17_signed.zip and maybe other files or do you just place the two BiTGApps files there?
I'm sorry for all the questions, but I'm trying to find out what I'm doing wrong ...
BiG_FooT said:
Yes, no problem with setup wizard. My phone is D802
Click to expand...
Click to collapse
Just to be sure, I'm talking about the Google Setup (see picture) not the Lineage Setup Wizard ...
theelderstatesman said:
Just to be sure, I'm talking about the Google Setup (see picture) not the Lineage Setup Wizard ...
Click to expand...
Click to collapse
Ah, ok, i was misguided by your first post (as you stated to had installed BitGapps for 10.). I was convinced that this must have been the reason for your trouble with the setup wizard. And I'm talking about the Lineage setup wizard. You are right that Google setup wizard is not shown with BitGapps.
BiG_FooT said:
Ah, ok, i was misguided by your first post (as you stated to had installed BitGapps for 10.). I was convinced that this must have been the reason for your trouble with the setup wizard. And I'm talking about the Lineage setup wizard. You are right that Google setup wizard is not shown with BitGapps.
Click to expand...
Click to collapse
Thanks so much for your help ...
maybe a stupid question - magisk works with this rom?
60nine said:
maybe a stupid question - magisk works with this rom?
Click to expand...
Click to collapse
You must install Magisk Canary build to work with Android 11 (Google for instructions)
Hi! Do you think it's OK for daily use?
BiG_FooT said:
You must install Magisk Canary build to work with Android 11 (Google for instructions)
Click to expand...
Click to collapse
thanks... btw is magisk even needed for root in Lineage roms or does Lineage have it's own root of some kind already inplemented?
i'm kinda off with all the info since i'm not using G2 as a daily driver but i have it laying around for testing and it has RR 5.8.5 installed at the moment
I'm on LOS 18 now. I found a workaround for my problem with BiTGApps and installed Magisk Canary successfully. @aleasto: There's no advanced restart in the developer options. I found a solution for that, too - but it would be good to have, since it was there in LOS 17.1 ...
I can't find the power management slider on LOS 18. The battery Manager shows very high consumption. Where can I now manage power consumption as in LOS 17.1? Now I am using LOS 18, BitGapps, Magisk Canary.
60nine said:
thanks... btw is magisk even needed for root in Lineage roms or does Lineage have it's own root of some kind already inplemented?
i'm kinda off with all the info since i'm not using G2 as a daily driver but i have it laying around for testing and it has RR 5.8.5 installed at the moment
Click to expand...
Click to collapse
Lineage dropped its SU solution in 17.0