[New Rom][U/B] February 9: Jaguar Aries LP 5.1.1 Official Hardened - Xperia Z3 Compact Original Android Development

[New Rom][U/B] February 9: Jaguar Aries LP 5.1.1 Official Hardened - Xperia Z3 Compact Original Android Development

This is the Official Jaguar rom for Aries, which is based on AOSP with some flavors from Slim and Dirtyunicorn. The rom was originally made for Xperia Z1 Honami in August 2015, then extended to Z1c Amami and now it is time for Z3c Aries. There have been thousands of downloads and great success with both Z1s. You can check respective original development threads. I hope the trend will continue with Jaguar for Aries.
Why LP, as opposed to MM and Nougat? Several reasons. The main one is Sony's unfriendliness to development community. Camera sucks, because Sony wouldn't provide proper blobs. Also, MM brings very few features, as opposed to LP. MM is still in alpha, but is already being abandoned by developers in favor of Nougat. Nougat will never work for Z1/Z2/Z3, because Sony wants you to buy a newer device. And finally, all LP roms, except Jaguar, have been abandoned by their developers since November 2015. CM still publishes nightly LP, but they have abandoned CM 12.1 kernel, meaning, they haven't incorporated about 800 security patches from Google and Code Aurora in LP kernel. Enough reasons for you?
The main difference from other roms is the emphasis on security and multiple features. With that in mind , let's see what Jaguar has to offer:
1. Hardened Kernel, modified M5; hardened rom built with HYPERTOOL 5.4
2. All ciphers enabled in kernel instead of just a few
3. Hardened/Fortified Bionic and Libs
4. Fstack protection strong to resist buffer overflows
5. Many System apps and processes are made read-only, to reduce elevation of privilege
6. Selinux replaced with Tomoyo Security, Yam security
7. Disc encryption, keymaster to 256 bit AES instead of 128
8. Latest TWRP with working brightness and ability to decrypt Data (Coming Soon)
9. Random number generation mixed hardware/software, as recommended by Linus Torwalds
10. Options to randomize host on every boot
11. Option to have a separate password for lock screen and boot
12. Qualcomm's Time Services disabled due to leaking on early boot (set time to automatic to get it from your carrier)
13. WIFI Background Scanning disabled to prevent leaking
14. Internet disabled for both WIFI and Data until Afwall is set and activiated (Afwall included in download, install as regular app)
15. The phone is VOLTE ready and you have all network options available in Cell menu (not just LTE/WCDMA/GSM)
16. GRsecurity features, such as Sidechannel implemented
17. Some Pax Security Features
18. Option to deny USB connection: denied always; denied when locked; and allowed always
19. Hardened webview with Google and other "interesting" IPs removed
20. Prevention of bruteforcing screen pin: the phone will reboot upon 3 unsuccessful attempts
21. Perfect_Event_Paranoid ported from Grsecurity: now third party apps can't use other apps including system to elevate privileges
22. Camera hardware button works to focus, take pictures and start video recording
23. Option to disable writing to Tombstones (a lot of private info is dumped there if there is a crash)
24. Option to disable continuing writing of logcat
25. Option to disable device cameras: back; front, both or none
26. Option to disable third party apps to access clipboard
27. Always latest Google Security Patches
28. Always latest Code Aurora Security Patches
29. Changes ported directly from Google Android Gerrit, so most of those in MM and even N are in this rom
30. About 80% of kernel changes are ported into Jaguar kernel from 3.10 and 3.18 (not Sony AOSP 3.10 that has Down Syndrome, but Linux/Google/Code Aurora one)
31. Rom is odexed to significantly increase boot speed (under 30 seconds) and application start
32. Many more security features ported from Linux and Copperhead OS
33. Dns Crypt: a feature allowing to choose among many Dns providers (all encrypted)
34. Seccomp: secure computing enabled in kernel
Other features include: Layers Theme Engine; Native Call Recording with interface integrated in Dialer with no restrictions; Privacy Guard; Native Wakelock Blocker; Native Black List; Global Menu; Slim Recents; Traffic Indicators; Advanced Reboot; Slim Pie; CPU Info on Screen; Ram Bar in Recents; Open source Superuser (not Supersu) included and integrated in Settings; True Offline Charging with Screen Off; Kernel Adiutor included (unzip and install as a normal app) and integrated in Settings plus more
Things users need to know to have smooth experience:. These are not bugs, but rather an explanation of some features
1. If you want to do data encryption, keep in mind that unlike Android, Jaguar uses 256 bit encryption. If you were encrypted on other roms, you won't be able to decrypt. So, wipe encryption and then re-encrypt on Jaguar. Also, keep in mind that if you ever did factory reset on official TWRP 3+ for honami, your data partition is screwed and have to be resized to enable encryption. This has nothing to do with the rom, but rather with the official TWRP itself. Fastboot my unofficial TWRP 3.0.2, (it is coming for Xperia Z3c, which, by the way has working brightness, as well as ability to decrypt and mount data
2. Jaguar contains a script running on early boot, which cuts the internet access to both WIFI and Data until Afwall is running. This is done to prevent leaking, as well as having all your internet traffic routed through some interesting number of servers, including this IP: 26.147.196.22. So, install Afwall and activate it, otherwise, no Internet for you
3. If your system language is different from English and you want to make changes in Phone/Cell Network settings, switch to English first, make the changes and then return to your language. The changes you made will hold. If you try to make the changes in your language, you will have com.android.phone crash. Localization takes time and is virtually impossible to implement in Jaguar, which is a one-person-rom
4. Sony TimeKeep, which is ported from MM/N, now sets the correct time on reboot without the Internet or GSM signal. All you need to do is set it once and TimeKeep will save/recalculate/restore the same on each reboot
5. GAPPS: if you use them, you need to flash them right after the rom (or each update) and before reboot. Flashing after reboot will result in multiple f/c
6. Due to Volte implementation, you might be required to flash LP or MM stock baseband (only if you have no 2g/3g signal)
Download: All updates and change logs are in Post #3
Instructions:
1. Be on LP at least, have TWRP, unlocked bootloader and root
2. In TWRP, wipe data/factory reset, then wipe System/Data/Cache/Dalvik
3. Flash the rom
4. If you use xposed, flash the latest installer
5. Reboot, install Afwall and Kernel Adiutor as normal apps; activate Afwall to have Internet
6. Enjoy the rom, say thank you, donate or do both
Warning: If your device and/or anyone in the immediate vicinity dies, don't blame me: it is all China and Russia's fault.
Credit: CM, AOSP, Slimroms, DU, Copperhead OS, Myself5 (kernel)
UPDATED KERNEL SOURCE: https://forum.xda-developers.com/devdb/project/dl/?id=23107 . Don't flash. This is not kernel, but rather sources to compile kernel
Kernel Source: https://github.com/AOSP-Jaguar/kernel_sony_msm8974
XDA:DevDB Information
JAGUAR ARISE LP 5.1.1 OFFICIA, ROM for the Sony Xperia Z3 Compact
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, CM, Slim,DU
Version Information
Status: Stable
Stable Release Date: 2016-10-16
Created 2016-10-17
Last Updated 2017-02-09

Development update and some screenshots
I broke my Z1 screen again and I am not in the mood for after market screens. And I am sick and tired of Sony crappy treatment of development community.
I am now looking at Lenovo Zuk Z2 or Z2 pro. Both excellent phones with the latest CPU and made out of metal and glass by Motorola which they bought from Google a couple of years ago. Zuk is friendly to developers and their blobs don't dumb down camera and they don't seek to "unify" bugs for all their devices. I no longer wish to support a fat bastard corporation that can't make a good phone, but thinks that just by putting their logo on the phone would make it worth $700.
RE Jaguar. I will continue to maintain Jaguar mainly with security patches... for a while, but my main work will be concentrated on Zuk. There is a lot of work to be done cleaning Android N and implementing security and other features from Jaguar...
Screenshots are here http://forum.xda-developers.com/showpost.php?p=62560391&postcount=2

This is where you have downloads
February 9: New release including
1. February Security patches
2. DNS_Crypt (in settings/security)
3. Seccomp (secure computing implemented in kernel)
4. Open Source Superuser integrated
5. Silent SMS notification enabled
6. 1440p profile in camcorder added
7. Sony TimeKeep: now time is set locally without the Internet or GSM signal (you need to set it right the first time only)
If you enable Dnscrypt and you use Afwall, allow internet for apps running as root...
If you prefer closed source Supersu, just flash the zip...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=23074
____________________________________________________
January 21. TWRP 3.x with the ability to decrypt and mount data on Jaguar
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22772
Flash in fastboot: fastboot flash recovery recoveryz3c.img
or use an app able to flash from SD card...
__________________________________________________________________________________
January 6: New release with January Google and Code Aurora patches. Also, Qcom time service is back...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22459
You can flash on top of another Jaguar release. Otherwise, fresh install (read the OP)
___________________________________________________________________
December 10. Rom updated to include
1. December security patches
2. Signature Spoofing (as in Omnirom), switch in Developer settings
3. USSD fixed (maybe)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22023
________________________________________________________________________________
November 10. Rom updated to include November Security Patches. I have also removed Supersu, since the rom has a built-in root manager and quite a few people no longer like Chinese owned Supersu.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21434
_________________________________________________________________________________
October 17. Latest version:
1. October security patches from Google and Code Aurora
2. Over 80 commits from Google Master Gerrit which included changes to bionic, art, frameworks and system
3. Updated Afwall
Rom Download: http://forum.xda-developers.com/devdb/project/dl/?id=20947
Afwall/KernelAdiutor Download: http://forum.xda-developers.com/devdb/project/dl/?id=20946
Afwall and Kernel Adiutor: unzip the file and install as normal apps

Thank you for making this really solid rom.
I only have one concern, is the reversed fisheye bug present?

stefx98 said:
Thank you for making this really solid rom.
I only have one concern, is the reversed fisheye bug present?
Click to expand...
Click to collapse
I really don't know what it is, as I don't have Z3. Someone else tested it and verified everything worked...

optimumpro said:
I really don't know what it is, as I don't have Z3. Someone else tested it and verified everything worked...
Click to expand...
Click to collapse
I was referring to the camera bug where the photos that you take look bent a little in a circular fashion, but what i could see from the screenshots, it looks like it's not present.
I will give this rom a try as soon as i get home and the effort that was put into it is really extraordinary

stefx98 said:
I was referring to the camera bug where the photos that you take look bent a little in a circular fashion, but what i could see from the screenshots, it looks like it's not present.
I will give this rom a try as soon as i get home and the effort that was put into it is really extraordinary
Click to expand...
Click to collapse
Screenshots are from Z1/z1c, which were not affected with that bug, so they are probably present. But please, try it out and post your feedback, I'm interested, but not able to do it on my device at the moment
Salutes for the OP for supporting Z3c

OMG! This is awesome.I'll flash it as soon as someone confirms no bug in camera.Thanks for your hard work!

ysfernblc said:
OMG! This is awesome.I'll flash it as soon as someone confirms no bug in camera.Thanks for your hard work!
Click to expand...
Click to collapse
Just be "someone"!

fluffi444 said:
Just be "someone"!
Click to expand...
Click to collapse
Of course I want,but I Can't.I'm a student and I use camera so often and I'm so experienced in aosp camera quality.If someone confirms camera quality,I am ready to be a tester user

ysfernblc said:
Of course I want,but I Can't.I'm a student and I use camera so often and I'm so experienced in aosp camera quality.If someone confirms camera quality,I am ready to be a tester user
Click to expand...
Click to collapse
My family member has a Z3c. There is Open Camera there and no fish eye problem whatsoever. I am going to post a few pictures taken by both cameras later...

optimumpro said:
My family member has a Z3c. There is Open Camera there and no fish eye problem whatsoever. I am going to post a few pictures taken by both cameras later...
Click to expand...
Click to collapse
Here is a photo on a dark and gloomy day...

optimumpro said:
Here is a photo on a dark and gloomy day...
Click to expand...
Click to collapse
Reverse fish eye bug is present if u have unlocked the bootloader....take a pic of something straight...

optimumpro said:
My family member has a Z3c. There is Open Camera there and no fish eye problem whatsoever. I am going to post a few pictures taken by both cameras later...
Click to expand...
Click to collapse
Is your family member using this rom, or anything based on this rom? If so, please take a picture of computer monitor/tv screen/door, something with clear straight lines.

Cirra92 said:
Is your family member using this rom, or anything based on this rom? If so, please take a picture of computer monitor/tv screen/door, something with clear straight lines.
Click to expand...
Click to collapse
Why would I post something taken on another rom? Here is a picture of a computer monitor. Yes, you can see some distortion. Too bad for Z3 and you are not getting a better camera.

optimumpro said:
Why would I post something taken on another rom? Here is a picture of a computer monitor. Yes, you can see some distortion. Too bad for Z3 and you are not getting a better camera.
Click to expand...
Click to collapse
Just asking Yeah just as I expected, that is an issue present for 2 years already, with no clear effort from Sony to release a proper calibration for Z3/Z3C.

I'm really interested in your unofficial TWRP, my phone is encrypted and the official TWRP can't decrypt it.

jacobs0n said:
I'm really interested in your unofficial TWRP, my phone is encrypted and the official TWRP can't decrypt it.
Click to expand...
Click to collapse
It is coming...

@optimumpro
Your work seems very appealing and thank you very much for supporting our beloved z3c!
I have a few questions,
1-Did you specifically choose the word "arise" ?
If Yes, then forget question one
If No, then it would be nice to change name to "Aries" because z3c codename is Aries.
2-Is this rom battery and resource friendly?
If the answers are somehow satisfying i'm thinking of unlocking my bootloader and use your rom.
Thanks in advance and best regards.

Tosgaba said:
@optimumpro
1-Did you specifically choose the word "arise" ?
If Yes, then forget question one
If No, then it would be nice to change name to "Aries" because z3c codename is Aries.
Click to expand...
Click to collapse
It's probably a typo, since the Z1 version is called Jaguar Honami.
From the Z1 thread:
This rom is now about 40% Nougat. One of the side effects: Xposed framework no longer works, but getting rid of it and instead using Privacy Guard is almost as good. Don't forget, Xposed is an exploit, which provides hooks for good and bad things.
Click to expand...
Click to collapse
These security features sound nice.
Does Xposed work on this one? Also, could I flash this and not enable encryption?
Normally, I'd flash it and get the answers myself, but I don't want to unlock my BL if I don't have to.
Sent from my Z3C using Tapatalk

Related

[ROM]Unofficial OmniRom 5.1 for the Galaxy S 4G (SGH-T959V and T959P)

Code:
Code:
/*
* Your probably long expired 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
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card before flashing!!!! This can be created with minitool partition wizard on Windows or gparted on Linux.
If on a BML rom (stock-based GB)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want root or Gapps, flash them now
If on an MTD rom (CM7 and all ICS+)(I tested CM9, CM10.1 and CM11)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Wipe data, and cache paritions (just in case). If updating to a newer build, you can probably skip this step
3. Install zip
4. If you want root or Gapps, install them now
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess and also provide T959P builds.
The USB connection is MTP and not mass storage as Omni has removed mass storage. In recovery there is still an option to mount as mass storage device.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps reportedly slow down the device significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
Video Recording
Automatic Brightness
Moving Apps to the SD Card
GPS
Encryption
Compass
SElinux in enforcing mode
What probably doesn't
Microphone mute option doesn't work during calls
What doesn't
720p recording is very laggy
What's been removed
TV-Out - It was removed upstream plus I think binary blobs are broken in Lollipop...
Live wallpapers - this is a low-ram device
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Galaxy S 4G (T959V) and Galaxy S Fascinate 4G (T959P), ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99, humberos
Source Code: http://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: All
Based On: OmniRom
Version Information
Status: No Longer Updated
Created 2015-06-30
Last Updated 2016-05-12

Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Download folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch galaxys4gmtd"
Changelog
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
Notifications are sometimes wonky. To fix, in Settings, go to Performance, then Advanced. Select Force high-end graphics and reboot your phone.
Changelog for 2015/07/20 Build
The data partition is now the second partition of the SD Card as opposed to internal storage
Gapps now work. If you get error 461 when installing from Play Store, a full data wipe should fix it. You can try experimenting with clearing data for the Play Store and/or Play Services or removing and re-adding your Google account if you don't want to do a full data wipe.
HSPA vs UMTS settings in DeviceSettings has been fixed
High-End graphics are forced by default to fix notification issue
ART parameters have been tweaked
Miscellaneous other tweaks, see my Github for details
Changelog for 2015/07/24 Build
Stabilized bluetooth connection
Fixed typo in GPS initialization. Does it work?
Added ability to use f2fs file system on /data. Supposed to give better performance
Added force fast charge and touch wake to kernel. Touchwake is accessible through its sysfs path, fast charge through Performance Settings, BatterySelinux currently denies these requests...
Changelog for the 2015/07/29 Build
This is a maintenance build. Very little has changed
Some more RAM freed (disabled some debugging stuff, TV-Out driver, IR driver)
Sepolicy updated for fast charge and touch wake
GPS initialization tweaked - unsure if works. If it doesn't, a dmesg would be appreciated
Changelog for 2015/08/02 Build
SElinux changed to permissive - this build only
GPS sepolicy changed - unsure if all necessary things are implemented
Changelog for 2015/08/13 Build
Selinux back to enforcing. Thanks to @anoymonos for the dmesg and @DerPugNa for offering to send me one as well
Fixed encryption
Changelog for 2015/08/31 Build
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
Restoring /system in TWRP should now work
When installing from BML, a chance is given to install gapps and/or SuperSu before rebooting
zRam is now actually used...
Changelog for 15/10/2015 Build
Fixed typo in updater.sh (thanks @FBis251!)
Update Omni source code - plenty of little tweaks since last build

Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-5.1-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Please let me know if the link doesn't work! There are also builds there for the T959P, in case there are any users of it left.
Gapps
Gapps do not work on builds prior to 2015/07/20. On more recent builds, they can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/

Thanks thanks ....

Awesome work @xc-racer99!

Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.

GFX.myst. said:
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
Click to expand...
Click to collapse
I hope I can keep this great little device going a little longer, however it will probably get tough. I did a repo sync earlier today and things are starting to break. The last few builds haven't even booted. With humberos no longer maintaining the i9000 and aries-common, I've had to fork the aries-common repository to try to keep going. The only upside of this is that I now have a little bit more freedom and can add things in if I want to.
Thanks for the offer of the graphics. If I can get a new build working, then I'll probably take you up on your offer. I think I've traced the problem but I'll have to wait and see...
For anyone that is trying/has tried this out, I'd be very curious on the status of the GPS on the T959V. I'm interested in creating the sepolicies for it so we can put selinux into enforcing mode but I don't want to go to the effort if it doesn't even work right now.

I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.

New Build Uploaded!
Download is still at the same link as before, just use the 2015-07-03 build
I managed to find out why my new builds hadn't been booting - it was because the syntax for using a custom kernel toolchain had changed.
Anyway...
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
On another note, I've had a look at re-implementing TV-Out support. It doesn't look promising as several of the functions in the android frameworks that it used have been tweaked.... Still working on it but don't hold your breath.
Also, if somebody could test dock audio that would be appreciated. I don't have any way of testing it. If it doesn't work, I do have an idea on how to fix it (for those interested, another almost-aries device, the Infuse 4G, had to modify things slightly to get it to work. I would try to emulate their solution).

Omg download nowwww....thanks my friend

Alright, I'm having some issues on the latest build with notifications and the lockscreen. I'm still working on tracing down the reason for the problem...

DickyG said:
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
Click to expand...
Click to collapse
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.

billowusu47 said:
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
Click to expand...
Click to collapse
Good to hear that that's its (mostly) been working for you. I was hoping that the gapps problem was just me
Out of curiosity, which of the alternate gapps did you try?
A brief google of the error brings up a couple of possibilities...
Try an older gapps version. The ones from devloz on the i9000 thread devloz and the oldest revision for 5.1.1 are probably your best bet. Please be aware that Google Play store will automatically update!!! In order to prevent this, you will need to create a folder called "com.android.vending-1.apk" in /data/app (use a root explorer such as ES File Explorer or adb if you know how). If a file with that name already exists, delete it first.
Another thing to try would be to unmount your sdcard first before trying to install an app. I know, its a terrible work-around but it should work. This is because the error is that Google Play is trying to save some data on your sdcard but then for some reason it fails (I'm not sure why).
I'll hopefully get around to seeing if its a permissions problem after I find out what's been causing the issue with the notifications on the latest build.
P.S. Does the GPS work?

Early update...
...ROM flashed fine...a little slow to boot...about 3 minutes...but it booted.
...Gapps flashed fine...used 20150513_5.1.x package
...Installed Super SU (although I don't think that's necessary) and TB.
...So far only gave a quick test to camera and web browser...no problems.
...Am now in the process of re-installing user apps and data from TB...this will take a while.
When I'm done with that, I use Link2SD to link most of my user files to the SD card. After that is all set up, I'll test stuff like GPS, root access, etc. I'll post back later...maybe tomorrow.
But so far so good.

OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.

DickyG said:
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
Click to expand...
Click to collapse
Alright, thanks very much for the update. I'll do some more testing here and see if I can solve anything. For me, bluetooth file transfers to the phone work but not from the phone.
I've been looking at the notification "error" where the lockscreen notifications do not appear correctly. It appears to have been introduced upstream with a merge. I'm having difficulty finding out exactly what changed and since no errors are being thrown in the logcat, it could be a while...
For testing the GPS, there's an app from the Play Store called GPS Test which does a nice job of showing satellites and whether or not you have a lock on them.

you're the man!
nice one! its nice that this device are still alive.! and now were on 5.1

DerPuGNa said:
nice one! its nice that this device are still alive.! and now were on 5.1
Click to expand...
Click to collapse
No, it should be Humberos is the man! I basically re-hashed his code for the i9000 and used bits and pieces from people like Bhundven, noiphonehere, maxfierke, Dao, and FB to get things to work properly.
For a status update, I figured out the lockscreen notification problem. I have a new build being made that I hopefully will be able to upload in the next couple of days (internet dependent). TV-Out looks totally broken as the proprietary blobs no longer function. I don't have the know-how to make ugly hacks to get them to work. The new build will have SElinux in enforcing mode and have the different GPS initialization (like the last build) until someone tells me that it doesn't work
Uh-oh, looks like I jumped the gun.... Having problems once again

Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.

AgainstTheFlow said:
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
Click to expand...
Click to collapse
Darn, so its still not working. Not surprising. I've been struggling on the notification issue and am at my wit's end as to what the problem is. I don't think its only our phone as several i9000 users have been reporting it as well. Whether it is only the first-gen Galaxy S series that is having the problem or not is anyone's guess. My programming skills are insufficient to fix the issue!
I'll have another look at gapps over the next couple of days and see if I can figure out a combination that works 100% of the time.
I'm assuming the error message is still 963 or does it silently fail now? Its probably related to the fact that we have only an external sd card and no internal sd card like most devices...
All the problems with the notifications that I've found are:
Only one notification will show up at a time
Large notifications such as the music player do not render properly. They are cut off at the normal notification size and occasionally it seems as if there are two layers there (one for the small version, one for the bigger version) (see attached picture, taken with VLC as the media player, but also appears with Apollo)
Notifications don't always show up. A little icon appears in the top left corner of the status bar but no notification is present. Seems hit or miss
The words No notifications appears in the lockscreen just above the clock when there are no notifications. Otherwise, a notification (and only one) which can't be clicked covers part of the clock

[ROM] iPioneer Slim 10c v0.1 for LGV521 - Rooted, busybox, init.d, debloated, etc...

ROM Ipioneer Slim 10c v0.1
A light, clean & faster rom!!!
Disclaimer:
/***
* Your warranty is now void (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
iPioneer Slim 10c v0.1 is a light, clean and fast custom rom designed for the Lg G Pad X 8.0 (T-Mobile variant only) and it's aim is to become a replacement for the default system of this device.
iPioneer Slim 10c v0.1 it is light because it only takes 519.8Mb of disk space which is a big difference when you compare the 1.2Gb of a stock rom, it is clean because it only contains the essential apps to make it work properly and it is faster because the whole system have been 100% optimized.
iPioneer it have been designed with the User Freedom in mind, it only provides you with the basic OS so you can do what you need to do on top of that.
Features:
Based on stock (10c)
Rooted
Busyboxed
Init.d Support
Extremely debloated (very serious)
Deodexed
Zipaligned
Nova as default launcher
Installation instructions:
Download the rom to your desire location (link to download to the end of this post).
Boot into Twrp recovery and do a standard wipe (factory reset).
Install the downloaded rom .zip.
Reboot the device.
Be patient, is going to take more time than a regular stock rom to boot into the system, at first is going to be stuck at T-Mobile logo but after few seconds is going to enter into App Optimization mode and after that you will be able to setup your system.
Enjoy it.
First things to do after you install this rom:
Add your google account (if you didn't complete that step at the first setup).
Download your favorite app manager (Rom Toolbox, Titanium, etc.).
Freeze the application called App Updates in order to stop the system update beacon for OTA. I removed 3 core apps in order to stop OTAs but it seems to be very integrated with the system, there is no way I can remove it from the rom without breaking the system. This is the most practical way to my knowledge right now.
Optionals things to do after you install this rom:
You can uninstall Nova Launcher if you want as is not part of the system apps, but before you need to install your favorite launcher. If you don't install another launcher and remove Nova you will have a broken system and most likely you'll have to re-flash the rom.
On purpose bugs and missing options:
On purpose bugs are bugs that comes when you remove a functionality from the system but it can not be removed from a third party component, example: LG VPN app it has been removed but the options remains in the Settings of the device and when you tap that option you will provoke a crash event, the way to resolve this is to decode the third party component (very difficult) or reinstall the missing part (in this case the LG VPN app).
iPioneer Slim 0.1 it comes without some apps that can not be removed from the system setting options, this is like that because I believe that these apps are not necessary for all people, if someone need them they can be downloaded/replaced from the Play Store or I will provide a flashable file with these apps so you can install them.
On Purpose bugs (located at settings):
From the Share & Connect menu:
File Sharing that contains BLE and Android Beam doesn't work, package SmartShare it has been removed.
Media Server (DLNA) doesn't work, package SmartShare that also contains SmartShare.MediaServer it has been removed.
Lg Airdrive doesn't work, package LGAirDrive & LGAirDriveSettings were removed.
From More>VPN menu:
LG VPN doesn't work, package VpnClient_LG it has been removed. Basic VPN it works.
From Display menu:
Home screen doesn't work, packages LGHome, HomeSelector, LGHome_Theme_Optimus, com.lge.launcher3, com.lge.launcher2.theme.optimus were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.
Missing options (located at settings):
Smart Cleaning not present, package LGSpringCleaning it has been removed.
Cloud (cloud integration in settings) not present, package CloudHub (maybe dependant on SmartShare package) it has been removed, please also note that this cloud integration it was integrated on the stock File Manager, so... if you want a full integration of the Cloud service on settings maybe you will have to install the stock File Manager provided by LGFileManager package.
From Backup & reset menu:
LG Backup is not present, packages LGBackupLauncher and LGBackup were removed.
From About tablet menu:
Update Center and its content (App updates & System updates) is not present, packages com.lge.appbox.client (app updates), com.lge.updatecenter & LGUpdateCenter (main menu for updates) were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.Flashable zip with system apps:
Coming soon when I have a free time.
What to do if you get the OTA notification:
Freeze the app called App Updates with your favorite app manager.
With your favorite file manager go to /cache and delete the update.zip (the downloaded ota).
Tap on Restart & Install button on OTA pop-up, the pop-up it will start counting to 0 in order to restart but your device won't restart because there are 3 core apps removed from this rom plus 1 app that you just disabled (all these 4 app controls the OTA), the notification is just gonna disappear, push recent button and clear the ota pop-up window.
Bugs Report:
If you find a bug in this rom just notify me about that in this thread, please, just use the title as "Bug Report" so I can pay close attention to that, my time is very limited. Thank you.
Feature Request:
If you want a feature to be added into future revisions of this rom just notify me about that in this thread, please, just use the title as "Feature Request" so I can pay close attention to that, my time is very limited. Thank you.
More info:
-------------------------------------
Device: Lg G Pad X 8.0
Model: LGV521
Code Name: b3
Carrier: T-Mobile
Android version: 6.0.1
Security patch level: 2016-07-01
Software version: V52110c
Link: https://www.androidfilehost.com/?fid=385035244224403624

Screenshots:
Default View: (sorry guys, I was not able fix Nova in order to show an organized and clean layout by default).
Default App Drawer: remember this is an extremely debloated rom, only the most basic core apps remains.
Settings view, yes some options are not present, read above about this.
Software info.

Reserved 2...

For some reason this post doesn't show up on ET page: lg-g-padx
Too bad, a lot of people won't be able to see this rom, but I can do nothing.
If someone knows an admin who can fix this issue please make mention of this post to him. I would do it but I don't have the time to.
Thank you.

Some screenshots added on post #2...

How fast does it run compared to the stock rom?

Munns86 said:
How fast does it run compared to the stock rom?
Click to expand...
Click to collapse
How fast it can go is a subjective matter:
It will depend on hardware lifetime span (how you use it and how other people use this tablet).
It will depend how much apps and content you put in it (the more things you download the more slow android is gonna be, this is kind a Swap area).
I did not do a benchmark, when I declared that is faster than a stock rom is because that speed response enhacement it comes based on the Deodex and Zipalign process. It can be or maybe not noticeable to your eyes but based on deodex and zipalign process is for sure that is faster than an odex and not-zipaligned rom.
The best answer is that you need to try it on your own and see the difference.
Sent from my LG-H918 using Tapatalk

Poll added at the beginning (not visible in tapatalk or xda app).
Please only select the apps that you really need or you really think that should comes with the next revision of iPioneer Slim rom.
This will help me to build a better version with features that users needs.

C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!

xtremelora said:
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
Click to expand...
Click to collapse
The reason is that the xda app can't see the vote going on.
Personally, I will be excited to see a cm/aosp custom build, which will sure draw much more attention.

googlephone said:
The reason is that the xda app can't see the vote going on.
Click to expand...
Click to collapse
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...

xtremelora said:
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
Click to expand...
Click to collapse
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.

googlephone said:
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
Click to expand...
Click to collapse
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.

xtremelora said:
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
Click to expand...
Click to collapse
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.

Munns86 said:
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Click to expand...
Click to collapse
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.

xtremelora said:
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
Click to expand...
Click to collapse
There is already a TWRP recovery for v521. Why you need to compile cm recovery?

googlephone said:
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
Click to expand...
Click to collapse
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk

xtremelora said:
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.

shabbypenguin said:
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
Click to expand...
Click to collapse
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.

xtremelora said:
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
Click to expand...
Click to collapse
i built it from scratch, id be careful looking too much at the v500, it's a snapdragon 600 SOC which is very old and is a quad core. the 615 in the g pad x is octacore and much newer. even the ramdisk is going to have big differences in how its handled.

SRGX2 Rom for the Life One X2 Mini

SRGX2 for Life One X2 MiniThis Rom Is a Stripped down modified version of the Life One X2 Mini stock Rom.
NOTE: After installation give Launcer 3 notification permission and update Google Play Services (click on the notification).
(Please remember I do this in my free time and with my own money. If you like it please hit the thanks button)
Mods:
Malware removed
Build.prop Tweaks
Oreo Launcher
Camera app replaced by OpenCamera
File manager replaced by MiXplorer
To do list:
Build wifi drivers into the Kernel
Strip down rc scripts
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Camera
Flash
Fingerprint
Not Working Yet:
(You tell me)
Downloads:
Current Build: https://www.androidfilehost.com/?fid=673956719939824825
Builds: https://www.androidfilehost.com/?w=files&flid=239712
Patches: https://www.androidfilehost.com/?w=files&flid=254440
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel: https://github.com/vampirefo/android_kernel_blu_kernel_x2 (Special thanks to @vampirefo for the kernel source)

Screenshots: comming soon

Changelog
Version: Testing
Build: 01072018211020
Initial release
Version: rc1
Build: 01142018205847
switched to stock theme
Version: 1.1.0
Build: 02182018215948
rebuild off of the 01/04/2018 update
Version: 1.1.1
Build: 02242018165134
fixed mobile data bug
Version: 1.1.2
Build: 03032018224915
changed DPI to 441
added stock calendar app
added stock calculator app
add stock clock app

Troubleshooting

reserved

Does quick charge work?

Been running for a couple of days now without issue.

cyrusharding said:
Does quick charge work?
Click to expand...
Click to collapse
Yes it works, I've beeen using 2 QC3 chargers with no problems at all.

Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!

cyrusharding said:
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
Click to expand...
Click to collapse
Interesting, didn't know that exists. I currently just download off of http://download.spotify.com/android/SpotifyAndroid.apk

enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy

srgrusso said:
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
Click to expand...
Click to collapse
This is awesome thanks so much!! I use Windows on a daily basis but I do have a pretty good knowledge about Linux and have set up a build environment in for Android. These links should help me understand what I am missing. I am also happy to continue testing and give you feedback on this ROM as it is currently my daily driver.

New Rom out. It has the stock theme, other than that it is the same.. I haven't decided if I'm going to build two Roms or have the theme be a patch. Maintaining all the different variants of the Rom are getting to be very time and space consuming.
https://www.androidfilehost.com/?fid=889964283620778170

Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?

Requia77 said:
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Click to expand...
Click to collapse
Is this without root? I don't know if my rom will fix that, I never used the Paypal app. Your welcome to try and let me know. Also there is LineageOS 13 for the mini which has been built from source.
https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814

New rom rebuilt from the 01/04/2018 update.
v 1.1.0

There is a problem with the latest version of SRGX2. Mobile data doesn't work. I work on it this weekend and keep everyone updated.

Here is the fixed rom.
https://www.androidfilehost.com/?fid=818070582850494825

Good news I was able to get Android File Host to make the Life One X2 an official device. I have made a request for the Mini too. For now all the files will be under the Life One X2 device.
Updated rom: https://www.androidfilehost.com/?fid=673956719939824825
It includes the stock Calendar, Clock and Calculator apps. I changed the DPI to 441. Let me know if anyone has any problems with the Playstore. I know that there has been some requests for the stock Camera and file Manager apps. It's hard to please everybody so I added a patch section which may please some.

[ROM] [Unofficial LineageOS 15.1] [8.1] [Build 2018-09-14] [Oppo R7f]

EDIT 2018-1-10
Changed ROM download link from single file to folder structure.
The folder will include new builds for OPPO R7f
Latest build currently 09-14
First off this wouldn't be possible without mikeNG, TheMuppets, LineageOS team
I'm just the cook
Devices supported: R7f, ONLY
Do not flash this rom on any other R7 variants. It will brick the device
Device specific changes/fixes compared to previous release:
BUILD: 07-15
* Tape 2 Wake should be completely functional now!
* Updated Oreo source (OPM2.171026.006.H1)
* Various minor kernel & device specific changes (Check Github)
BUILD: 09-14
* Android security patch level updated (September)
* Updated Oreo source (OPM6.171019.030.K1)
* Various minor device specific updates (check git)
* Various minor LineageOS updates (check git)
* Not verified, battery lifetime seems a bit longer
How to install and all that kind of jazz please refer to my previous 15.1 thread
Updating from previous 15.1 release. Regular wipe in recovery is enough also wipe Dalvik & Cache
Downloads :
[ROM] Unofficial R7f LineageOS 15.1
Archive must be unpacked! Contains flash-able zip & md5 checksum
[Gapps -> ARM -> 8.1]
*Don't select the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.2-0)

thank you. I am downloading and want to try it now.

Thanks again. It looks like it's time for me to try it as well.
P.s. please don't create a new thread for each release

Forage81 said:
Thanks again. It looks like it's time for me to try it as well.
P.s. please don't create a new thread for each release
Click to expand...
Click to collapse
I'll keep this as a rolling thread
PS. I wasn't unable to successfully build with Ubuntu
ParrotOS worked much easier and seems more stable as build environment

Wow this is great! thanks!

oh and would u be updating the build with the new lineageos features like true dark mode etc.?

ph03nae said:
oh and would u be updating the build with the new lineageos features like true dark mode etc.?
Click to expand...
Click to collapse
With the next (major) device specific changes and/or android changes I'll make another build which will include the newer LineageOS features
Guess within the next 1 ~ 2 Months you could expect another build from me.
In the meantime I'm taking a crash course on Android kernel development.
Would be nice to squeeze some extra juice out of this device.

JJRT said:
With the next (major) device specific changes and/or android changes I'll make another build which will include the newer LineageOS features
Guess within the next 1 ~ 2 Months you could expect another build from me.
In the meantime I'm taking a crash course on Android kernel development.
Would be nice to squeeze some extra juice out of this device.
Click to expand...
Click to collapse
Alright! Will be looking forward to the next release! (oh and btw is it possible to shift the power menu from the right to the left since the power button is on the left?)

ph03nae said:
Alright! Will be looking forward to the next release! (oh and btw is it possible to shift the power menu from the right to the left since the power button is on the left?)
Click to expand...
Click to collapse
You'll have to do that yourself
I want to keep this ROM a pure LineageOS source no modified frameworks
Try Xposed with NeoPowerMenu module, think it's able to do the trick

@JJRT,
Thank you very much for 'cooking' this ROM! On vacation I discovered that GPS did not work on that old 7.1.2 version. Now again works perfectly fine with this ROM!
I have one small problem though. Android indicates that my SD card is corrupted and want to fix it by 'configuring' it.
1) Does anyone know if it is actually going to try to fix it or will it just reformat it?
Obviously I do not want the latter. I would rather remove it from the phone and repair it in my PC.
2) Can I 'hot swap' the SIM/SD tray or do I really need to turn off the phone? The latter will most likely cause the phone to go into boot loop.
Thanks in advance for any help or info.

eximiusnl said:
@JJRT,
Thank you very much for 'cooking' this ROM! On vacation I discovered that GPS did not work on that old 7.1.2 version. Now again works perfectly fine with this ROM!
I have one small problem though. Android indicates that my SD card is corrupted and want to fix it by 'configuring' it.
1) Does anyone know if it is actually going to try to fix it or will it just reformat it?
Obviously I do not want the latter. I would rather remove it from the phone and repair it in my PC.
2) Can I 'hot swap' the SIM/SD tray or do I really need to turn off the phone? The latter will most likely cause the phone to go into boot loop.
Thanks in advance for any help or info.
Click to expand...
Click to collapse
Likely partition filesystem issues/corruption.
Preferable to do this with a SDcard-reader
Under Linux I'd suggest using Gparted to check/change filesystem and/or format
Under Windows Paragon Partition Manager™ Would do the job splendidly. Even ext4 / exfat layouts
And yes you could hotswap with phone still on, but I wouldn't recommend doing so out of precaution

I notice the following issues with this ROM:
1) Battery life noticeably less than the 'old' 7.1.2 (of 23-8-17).
2) Notifications arrive 20 to 30 minutes late.
3) In the about it says "Playform: msm8916", which is a 4 core Snapdragon 410. However, the R7f contains MSM8939, which is an 8 core Snapdragon 615. Does this mean only 4 cores are used?

eximiusnl said:
I notice the following issues with this ROM:
1) Battery life noticeably less than the 'old' 7.1.2 (of 23-8-17).
2) Notifications arrive 20 to 30 minutes late.
3) In the about it says "Playform: msm8916", which is a 4 core Snapdragon 410. However, the R7f contains MSM8939, which is an 8 core Snapdragon 615. Does this mean only 4 cores are used?
Click to expand...
Click to collapse
1: I do notice a bit, not dramatically
Concerning battery , did you do a clean install? (format data / cache / system) coming from 14.1 it's advisable to do so
2: Not having those issues (WiFi and 3G) Whatsapp/gmail/youtube notifications are near instant. Have more info?
3: Yeah not sure what the deal is with that. While building the rom it does use the msm8939 sources from LineageOS/TheMuppets
But indeed the info screen of 'Model & Hardware' Does report msm8916. Shall look into that (Guess it's just a left over from a initial script source they've used)
Other diagnostic software does identify it correctly and the performance is on par with 8939

JJRT said:
1: Concerning battery , did you do a clean install?
Click to expand...
Click to collapse
Yes, I did a complete wipe.
JJRT said:
2: Not having those issues (WiFi and 3G) Whatsapp/gmail/youtube notifications are near instant. Have more info?
Click to expand...
Click to collapse
Notifications usually get in when I click the button on the left side to unlock the phone or after a certain time (20-30 minutes). So it seems it does not work instant when the phone is locked.
I also notice that I only get notifications from email, sms and whatsapp. I checked the settings and notifications are enabled for all apps, but I do not get any notifcations from any other apps.

eximiusnl said:
Yes, I did a complete wipe.
Click to expand...
Click to collapse
Try getting some stats about what is eating your battery in the battery usage section of the settings or an app like BetterBatteryStats.
With the 14.1 lineageOS release I sometimes have/had that sensor use went nuts for a long period of time, draining battery as a result.
eximiusnl said:
Notifications usually get in when I click the button on the left side to unlock the phone or after a certain time (20-30 minutes). So it seems it does not work instant when the phone is locked.
I also notice that I only get notifications from email, sms and whatsapp. I checked the settings and notifications are enabled for all apps, but I do not get any notifcations from any other apps.
Click to expand...
Click to collapse
Can it be that this only happens when you are connected to WiFi? If yes, verify the WiFi settings to make sure remains connected or if it's not doing something else undesirable.

is it possible to activate camera2api and install google camera? Los 15.1

Ravhinzy said:
is it possible to activate camera2api and install google camera? Los 15.1
Click to expand...
Click to collapse
Currently no, camera firmware restriction
Might become possible if someone manages to update the sources, but I wouldn't count on it

JJRT said:
Currently no, camera firmware restriction
Might become possible if someone manages to update the sources, but I wouldn't count on it
Click to expand...
Click to collapse
Just curious, who would be able to update the sources/what needs to done to update the sources?

I solved the problem with the notifications of Whatsapp. The trick is to disable battery optimization for Whatsapp. Of course this is even worse for the battery life. I find it interesting that Android 8 has measures to save battery, but ends up using much more battery than 7.1.2.
This does not help for the apps that do not give any notifications at all. Maybe there is something changed in the way Android 8 handles notifications? I did read some comments from one app maker that they had updated their app to make notifications work on Android 8.1.

ph03nae said:
Just curious, who would be able to update the sources/what needs to done to update the sources?
Click to expand...
Click to collapse
Someone with low-level hardware/firmware/kernel knowledge
What exactly needs to be changed in order to make it compliant, I don't have a clue. It's over my head

[ROM][UNOFFICIAL][SUNFISH][A11] LineageOS 18.1

I'm not a fan of Android 12's Material You, i.e. dull color schemes, ginormous headers and copious amounts of whitespace. Screens got bigger over time, but information density is getting lower and lower. It's crazy. Anyway, I'll spare you the rant.
As the LineageOS project stopped publishing builds for LineageOS 18.1, but they continue to patch their 18.1-branch with Android's monthly security updates, I decided to start building it myself following the instructions here.
You can download the builds here:
LineageOS 18.1 for Pixel 4a (sunfish) - Browse Files at SourceForge.net
Unofficial builds for those who wish to stay on 18.1 a bit longer.
sourceforge.net
I usually publish an update every month.
Additional tweaks
Default maximum lockscreen password length of 64 characters (instead of 16) [more info]
FirmwareIt's probably best to run the latest Android 11 firmware, since this is Android 11. You can download the last official Android 11 factory image from Google and flash it from fastboot mode (your data will be erased).
Clean install
Download the latest lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img and lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip from aforementioned link
Boot to bootloader a.k.a. fastboot
Flash the boot image with this command (replace filename with actual filename):
fastboot flash boot lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img
Boot to recovery
Factory reset > Format data/factory reset > confirm (your data will be erased)
Apply update > Apply from ADB
Sideload the ROM with this command (replace filename with actual filename):
adb sideload lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip
(If it asks "Signature verification failed. Install anyway?" answer Yes)
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
Reboot system now
UpdatingUpdates are delivered through the built-in updater (Settings > System > Updater).
If you use Magisk, deny the Updater's request to reboot at the end of the update process, open Magisk, tap Install and then "Install to Inactive Slot (After OTA)". Tap reboot after the process completes.
Migrating from last official LineageOS 18.1 buildSo it turns out builds are signed with a secret cryptographic key and when you install an update it has to have the same cryptographic signature or bad things will happen. This means you can't directly update from the last official build (signed by the LineageOS team) to my build (signed by me).
The solution: build and install (as an update a.k.a. dirty flash) a so called "migration build", which "resets the keys on all packages at every boot." I guess after booting into this build once, you can just update to the regular build using the updater (the LineageOS wiki is very concise on this topic and doesn't explain much).
You can download the migration build and boot image from the aforementioned link, they are marked MIGRATION instead of UNOFFICIAL. Don't run this build any longer than necessary, it's a security risk by its very nature.
When I tried this migration, my system wouldn't boot (stuck on boot logo). ADB worked and I could see in dmesg or logcat that, among other errors, SystemUI failed to start. Was it because I didn't reflash Gapps? But I never reflashed Gapps when using LineageOS' builtin updater...
Later I did some testing. I did a clean install of the latest official build, then my migration build, then my normal build, all was fine. Then I did a clean install of the latest official build WITH Gapps, then flashed the migration build WITHOUT Gapps, and the system booted up just fine. Huh? Then I flashed my normal build DIRECTLY over the latest official build, without migration build in between, and all was STILL FINE! So uhm... what's happening, how does this signing work and when does it become a problem? I have no clue.
If you decide to try the migration route, make sure to backup any data you don't want to lose and let us know how it went!
AcknowledgementsThanks to the original maintainers PeterCxy, cdesai and mikeioannina for bringing LineageOS 18.1 to the Pixel 4a!
Source code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com

GcamYou can just install it from the Play Store. There are a few bugs:
In photo mode, slide up to record video doesn't work
Motion Photos doesn't work
It doesn't scan QR codes without Google Lens
App versions without Material YouIf, like me, you try to avoid Material You like the plague, here's a list of the last versions of Google apps that I use(d) that don't have Material You. Note that LineageOS includes its own versions of some of them and all of them are optional anyway. You can find them on e.g. APKMirror.
Calculator 7.8
Calendar 2021.35.3
Camera 8.2.400
Clock 6.4.1
Contacts 3.49.2
Gboard 10.8.05
Maps 10.80.1
Phone 68.0.3
Photos 5.58.0
Translate 6.24.0.02
Is it wise to run older software? You decide. In an ideal world security updates and bug fixes would be separate from UI and "we decided you don't need this functionality so we removed it" updates. I've long ago stopped regularly updating my apps (i.e. turned off automatic updates) because I like to be able to trust my device will look & work the same tomorrow as it did today.

P.S. After you've installed the regular 20220815 build, the updater will keep showing an August 16 update which is actually the build you're already running. This is because I had to move the timestamp one day forward in order to enable updating from the MIGRATION build, which was also build on 20220815 and wouldn't see the regular 20220815 build as an update otherwise. This will be remedied with the next update I publish.

The September update is now live.

Does banking app works?

My bank's app has always worked fine on LineageOS. Your bank's hasn't?

icantlogin said:
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
Click to expand...
Click to collapse
I had never tried this rom want to try if bank apps works out of box

icantlogin said:
The September update is now live.
Click to expand...
Click to collapse
Been using this for several days now without a hiccup , fast ,,smooth, and google proofed, Thanks!!

Thanks for keeping LOS 18.1 alive with these security updates. I recently upgraded to 19.1 to try it out for a few months but I just couldn't get used to or appreciate the new UI. With every app update they also make it more like A12 and it just wasn't working for me.
Just installed your September update and all is well so far.

The October update is live!
A little background: I'm building this ROM on a Google Cloud Compute Engine instance, which is a virtual computer (also called virtual machine or VM) running in a Google data center. To keep the VM around is very costly, as it uses 300 GB of SSD storage which doesn't come cheap. So I create a new VM every month and dismantle it afterwards. This means I have to set up the build environment from scratch every time, which consists of a lot of steps. So from the beginning, I've put most of those steps in a Bash shell script (the VM runs Ubuntu 20.04) to speed things up drastically.
Last week I added some code that generates the updater.json file (that's read by your phone when it checks for updates) which I had been creating by hand before. I also added code to automatically upload the build to SourceForge. So yesterday all I had to do was create the VM, upload the script and run it. Six hours later, your phone was able to download the update without any further intervention on my part.
What can I say, the geek in me is very happy

Hi, I thank you for your work. Would you know if I can install microg without magisk, maybe via nanodroid or similar while maintaining OTA updates?

I have no experience with that. I assume you would have to apply the signature spoofing patch and install microG before booting from the updated system partition. So after installing the OTA update boot into recovery and do this?

Hello ! How to you push the google apps on this one ?
I'd like to get a pico gapp installed to get some game running

It's in the instructions in the first post, after flashing the ROM:
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
I'm using NikGapps Core myself.
This only works if you do it before first boot by the way, as far as I know you can't put Gapps on an installation you're already using.

Hi! Do you know if this will retain microg if I dirty-flash it on top of a lineage.microg.org build (the last official release) using your MIGRATION build? If you're not sure I'll back up my stuff and give it a shot and report back Thanks a lot for your your work!

Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!

icantlogin said:
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
Click to expand...
Click to collapse
Here is what I found, in case it helps someone: flashing the migrate ROM and then the latest proper ROM works perfectly, however I did lose microg, system f-droid, etc, and anything which is in the lineage.microg.org build but not in this one.
Now since you are building monthly ROMs, would you consider applying the signature spoofing patch to your builds? This would make it easy for those who want to run microg instead of google play framework/gapps. As far as I understand it you just need to apply this patch with `cd android_frameworks_base; patch -p1 -i /path/to/android_frameworks_base-R.patch`. Thanks again for your efforts

I'm open to consider this, but as I somewhat but not fully grasp the security implications of enabling signature spoofing, and not everyone might want to have this enabled by default, it would have to be a toggle in Developer Options and disabled by default, or I would produce a separate build with the patch applied.
If you could find a patch for me that implements the toggle in Developer Options, that would be great. As I researched it a bit I read that some ROMs have this.
Interesting that the migration worked, by the way!

Some more thoughts on this: it seems with signature spoofing enabled on the ROM, an app still has to ask for the permission to spoof its signature, so for advanced users like us who know what we're doing, I guess that's good enough. I'll have to read up on this a bit more though. I know the LineageOS devs are against implementing it but most everyone else says it's actually not that big of a security risk.

I just reply to show you my gratitude for maintain LoS 18. I updated to 19 two weeks ago and I was literally suffering with the system theme. IDK what they were thinking but it was terrible. Also for me, on 4a, was having lag: An example is when I shuffle songs on Musicolet, they take a good while to update the information (song name, basically) while with 18 it updates as soon as I press next.
BTW, can you recommend me a good KERNEL? Thanks!

Database Info

welcome