• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[UNOFFICIAL][ROM] LineageOS/Go 15.1 for Grand Prime [S920L/G530H/FZ/M/MU/P/T/T1/W]

Search This thread

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903
2okPze5.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.


Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
   phone or causes thermonuclear war  and ends the
    world as we know it. You have been warned.


ROM Information


Device Names

Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
[B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]
[B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530M[/B] - [COLOR="DarkSlateBlue"][B]fortunalteub[/B][/COLOR]
[B]SM-G530H (XX)[/B] - [COLOR="DarkSlateBlue"][B]fortuna3g[/B][/COLOR]
[B]SM-G530H (XC)[/B] - [COLOR="DarkSlateBlue"][B]fortunave3g[/B][/COLOR]


Download


Instructions


If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.





If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.

Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.

* Reboot into recovery mode [Press Power+Volume Up+Home].

* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.


* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:

* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:

adb sideload name_of_zip.zip

to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.

* Download and flash GApps in the same way.


How to provide logcats

Under Windows:


Code:
[B]* Install samsung device drivers and then
 the adb utils from here:[/B]

[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]

[b]* Then enable developer mode, connect your phone to usb,
 and from [B]cmd[/B] paste this command:[/b]

[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]

[b]then try to reproduce the bug.[/b]

[b]* The logcat file will be on your desktop.[/b]



Under Linux:


Code:
[b]* Install the adb utils from your distribution's
 package manager and execute the command:[/b]

[I]adb logcat > ~/logcat.txt[/I]

[b]then try to reproduce the bug.[/b]

[b]* The logcat file will be on your home directory.[/b]

* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.

* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:

Code:
adb connect [ip address here]

And then the adb logcat command for windows.



FAQ

Q: Are you taking device requests?
A: No.

Q: Are you accepting feature requests?
A: No.

Q: Can you make XXX ROM as well as LOS?
A: No.

Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.

XDA:DevDB Information
[UNOFFICIAL][ROM] LineageOS/Go 15.1 for Grand Prime [S920L/G530H/FZ/M/MU/P/T/T1/W], ROM for the Samsung Galaxy Grand Prime

Contributors
vince2678, minz1, vlw, Danil_e71
Source Code: https://github.com/Galaxy-MSM8916

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: >= 4.4 (KitKat)
Based On: LineageOS

Version Information
Status: Beta

Created 2017-11-12
Last Updated 2018-09-03
 

Attachments

  • Screenshot_20180207-011657.jpg
    Screenshot_20180207-011657.jpg
    30.2 KB · Views: 24,406
  • Screenshot_20180207-011741.png
    Screenshot_20180207-011741.png
    197.6 KB · Views: 25,127
  • Screenshot_20180207-011747.png
    Screenshot_20180207-011747.png
    53.8 KB · Views: 25,314
  • Screenshot_20180207-011755.png
    Screenshot_20180207-011755.png
    45.5 KB · Views: 24,975
  • Screenshot_20180207-012109.jpg
    Screenshot_20180207-012109.jpg
    32.3 KB · Views: 25,192
  • Screenshot_20180207-012124.png
    Screenshot_20180207-012124.png
    48.6 KB · Views: 24,773
  • Screenshot_20180207-012129.png
    Screenshot_20180207-012129.png
    63 KB · Views: 23,607
  • Screenshot_20180207-013151.png
    Screenshot_20180207-013151.png
    33.7 KB · Views: 22,337
  • Screenshot_20180207-013155.png
    Screenshot_20180207-013155.png
    43.4 KB · Views: 21,604
  • Screenshot_20180207-013220.png
    Screenshot_20180207-013220.png
    40.5 KB · Views: 20,784
  • Screenshot_20180207-013241.png
    Screenshot_20180207-013241.png
    48.6 KB · Views: 20,486
  • Screenshot_20180207-013258.png
    Screenshot_20180207-013258.png
    51 KB · Views: 19,713
  • Screenshot_20180207-013409.png
    Screenshot_20180207-013409.png
    39.9 KB · Views: 19,260
  • Screenshot_20180207-022736.png
    Screenshot_20180207-022736.png
    57 KB · Views: 18,644
  • Screenshot_20180207-022804.jpg
    Screenshot_20180207-022804.jpg
    31.9 KB · Views: 18,542
  • Screenshot_20180207-022837.jpg
    Screenshot_20180207-022837.jpg
    13.9 KB · Views: 18,256
Last edited:

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903
Important

If this is your first time flashing O, you will need to install the latest unofficial TWRP image for your device from the links above before flashing a zip image, otherwise installation of a zip will invariably fail.

For SM-G530P users, use the gprimelte unofficial twrp instead of the gprimeltespr one.
For SM-S920L users, use the gprimeltetfnvzw official twrp instead of the unofficial gprimeltetfnvzw one.
 
Last edited:

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903
What works

Code:
[B]
* RIL (in-call audio, messaging, [I]data possibly[/I])
* Bluetooth (including audio)
* WiFi
* Audio (music, etc)
* Camera (including video recording)
* Flash
* Sensors
* GPS
[/B]

Known Issues

Code:
[COLOR="RoyalBlue"][B]SM-G530P | SM-S920L [/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] In-call audio is buggy (there's a persistent ring tone during calls).[/B]

Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] NFC does not work. This is indefinitely broken[/B]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Encryption does not work. This is indefinitely broken[/B]

Changelog

Code:
[COLOR="Red"][B]09/02/2018[/B][/COLOR]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Core control has been disabled permanently, in-kernel. [/B]

* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] NFC may (or may not) be working this build on capable devices.
   This is Untested. [/B]

* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Rebased lineage-15.1 branches in repos. This is mostly
   for our benefit; just to tidy up the repos and make commit history more descriptive,
   accurate and give proper credits to commit authors. [/B]
   
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Camera recording should be working again.
   This was broken due to upstream android security change. [/B]

* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Reworked zram support in ROM. There are now two zram properties:
	[I]ro.config.zram.enabled[/I] and [I]ro.config.zram.size[/I]
	Set [I]ro.config.zram.enabled[/I] [I]true[/I] to enable zram;
	and [I]ro.config.zram.size[/I] to set the size of the zram disk.

  If you set this too large the system will slow down. You can also just use a zram
  zip from the download server to do this automatically.[/B]

Code:
[COLOR="Red"][B]08/12/2018[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Camera recording is broken.
   This is due to upstream android security change. [/B]

* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Reworked zram support in ROM. There are now two zram properties:
	[I]ro.config.zram.enabled[/I] and [I]ro.config.zram.size[/I]
	Set [I]ro.config.zram.enabled[/I] [I]true[/I] to enable zram;
	and [I]ro.config.zram.size[/I] to set the size of the zram disk.

  If you set this too large the system will slow down. You can also just use a zram
  zip from the download server to do this automatically.[/B]

* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Enabled zram by default for low-ram (1GiB) devices [/B]


Code:
[COLOR="Red"][B]07/26/2018[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Camera recording should be working normally again [/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] sdcard (vfat/fat32) should work fine in recovery [/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Some stutter and lag issues have been fixed 
     (tweaked core_control, among others) [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] exFAT support has been restored [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Re-enabled QS transparency [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Removed go-gapps from lineage-go [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Reduced kernel logcat buffer size from 512KB to 256KB (slight RAM saving)[/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] zram has been disabled by default. If you want this, you can set the 
    property [I]ro.config.zram[/I] to true[/B]

Code:
[COLOR="Red"][B]06/03/2018[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Frequency scaling issues should be fixed (stutter after suspend/resume should be gone). [/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] In-call audio should be fixed on multi sim devices. [/B]

Code:
[COLOR="Red"][B]06/01/2018[/B][/COLOR]
* [B][[COLOR="Blue"]MISC[/COLOR]][/B] [B] Go GApps are now embedded in LineageOS Go builds. [/B]

Code:
[COLOR="Black"][B]05/28/2018[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Frequency scaling should be fixed (improved power savings) [/B]

Code:
[COLOR="Black"][B]05/21/2018[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Thermal engine is now working proper (for better temperature control) [/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Hidden Wi-Fi networks should now be connectable/reachable [/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Power hal is now working proper (resulting in improved battery usage)[/B]
* [B][[COLOR="Blue"]MISC[/COLOR]][/B] [B] RIL includes updated [/B]
* [B][[COLOR="Blue"]MISC[/COLOR]][/B] [B] Misc. kernel updates (sdcardfs, binder) [/B]

Code:
[COLOR="Black"][B]04/27/2018[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Brightness adjustment should be fixed for the fortuna3g/SM-G530H[/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] In-call audio should be working for the second sim on dual-sim devices[/B]

Code:
[COLOR="Black"][B]04/24/2018[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Sim detection should be fixed for fortuna* devices.[/B]

Code:
[COLOR="Black"][B]04/23/2018[/B][/COLOR]
* [B][[COLOR="Green"]MISC[/COLOR]][/B] [B] Added fortuna* devices.[/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Video recording now works[/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Bluetooth audio is fully working[/B]

Code:
[COLOR="Black"][B]13/03/2018[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] In-call audio should be working in the latest build[/B] 

* [B][[COLOR="Orange"]PARTIAL FIX[/COLOR]][/B] [B] Camera flash and previews should be working, however, saving pictures or videos will not work. [/B]

Code:
[COLOR="Black"][B]06/02/2018[/B][/COLOR]
* [B][[COLOR="Red"]REGRESSION[/COLOR]][/B] [B] In-call audio is broken [/B]

Code:
[COLOR="Black"][B]20/11/2017[/B][/COLOR]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] WiFi is working[/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] RIL functions (Calling, texting, data) should be working, including in-call audio [/B]
* [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Music and video playback should be working [/B]

Code:
[COLOR="Black"][B]12/11/2017[/B][/COLOR]
* [B][[COLOR="Green"]NOTE[/COLOR]][/B] [B] First working image built. [/B]

 
Last edited:

Zippy Dufus

Senior Member
Feb 12, 2011
475
178
Important:

If this is your first time flashing O, you will need to install the latest unofficial TWRP image for your device from the links above before flashing a zip image, otherwise installation of a zip will invariably fail.

If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.

Is it possible to flash your latest TWRP 3.1.1 builds without Odin?

I see the recovery.img in the tar file. What I am really asking is if it is safe to flash this over itself? (i.e. by replacing the image in an older TWRP flashable zip file)

I don't have ready access to a Windows machine.

BTW, great work! The folks in the other thread are still struggling just to get a bootable build. :good:

== EDIT ==

FWIW, I found a simpler way:
  1. Downloaded TWRP-3.1.1-lineage-14.1_j20_20171110_gprimelte.tar from the TWRP link in the OP.
  2. Extracted the recovery.img (renaming to TWRP-3.1.1-lineage-14.1_j20_20171110_gprimelte.img for recognition).
  3. Flashed this using TWRP. Choose the Install Image button from the Install screen.
 
Last edited:
M

manueltimz

Guest
Is it possible to flash your latest TWRP 3.1.1 builds without Odin?

I see the recovery.img in the tar file. What I am really asking is if it is safe to flash this over itself? (i.e. by replacing the image in an older TWRP flashable zip file)

I don't have ready access to a Windows machine.

BTW, great work! The folks in the other thread are still struggling just to get a bootable build. :good:
EXCUSE US
G530H has an oreo ROM(check telegram) just that the dev doesnt want to release a ROM without RIL. calls,text and data are the sense behind having a phne
 

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903
Is it possible to flash your latest TWRP 3.1.1 builds without Odin?

I see the recovery.img in the tar file. What I am really asking is if it is safe to flash this over itself? (i.e. by replacing the image in an older TWRP flashable zip file)

I don't have ready access to a Windows machine.

BTW, great work! The folks in the other thread are still struggling just to get a bootable build. :good:

Yes.
 
  • Like
Reactions: Zep0th

Zippy Dufus

Senior Member
Feb 12, 2011
475
178
EXCUSE US
G530H has an oreo ROM(check telegram) just that the dev doesnt want to release a ROM without RIL. calls,text and data are the sense behind having a phne

My bad, sorry for misspeaking.

I'm just glad that folks are making progress with oreo on this device!

And I just want to be ready to flash when the ROM is ready. :silly:
 

Zippy Dufus

Senior Member
Feb 12, 2011
475
178
Good progress

Well, just for fun, I managed to build a (11/19) bootable ROM.

However, once booted the screen was black except for the bluetooth, network strength, and battery icons in the top right corner.

Futzing with the buttons and touching the screen, I got a panel "Setup Wizard isn't responding" and choosing either "Close app" or "Wait" continued with the black screen.

Interestingly, a little "LTE" text item is displaying over the network strength icon. My build includes the commit which uses the A3 RIL libraries. I'm not sure if this is relevant to progress in that direction.

Also, it should be noted that I probably haven't done everything needed to build this ROM properly. I did discover the repopicks.sh script which was needed to make the build complete but I suspect that I am missing some other patching.

Regardless, a great start!!

Thanks @vince2678 and all the other MSM8916 contributors.
 

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903
Well, just for fun, I managed to build a (11/19) bootable ROM.

However, once booted the screen was black except for the bluetooth, network strength, and battery icons in the top right corner.

Futzing with the buttons and touching the screen, I got a panel "Setup Wizard isn't responding" and choosing either "Close app" or "Wait" continued with the black screen.

Interestingly, a little "LTE" text item is displaying over the network strength icon. My build includes the commit which uses the A3 RIL libraries. I'm not sure if this is relevant to progress in that direction.

Also, it should be noted that I probably haven't done everything needed to build this ROM properly. I did discover the repopicks.sh script which was needed to make the build complete but I suspect that I am missing some other patching.

Regardless, a great start!!

Thanks @vince2678 and all the other MSM8916 contributors.

You installed GApps, that's why setup wizard is crashing.
 
  • Like
Reactions: Zep0th

Zippy Dufus

Senior Member
Feb 12, 2011
475
178
A first look

Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] WiFi does not work[/B]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Camera and camera-related functions (flash) do not work[/B]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] RIL functions (Calling, texting, data) do not currently work [/B]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Music playback may not be working [/B]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] NFC does not work [/B]

I built and flashed a 11/20 ROM, this time without flashing GApps, because I was excited to see that the FM radio was enabled again.

Alas, there was only static on my G530W. I still would like to know if the hardware has been definitely crippled on this variant or perhaps mixing/matching the proprietary firmware from other variants might enable FM.

Otherwise:
  1. WIFI is working for me.
  2. I don't even see a camera app in apps panel. It is listed in Settings->Apps.
  3. The phone can make and receive phone calls but has no audio. This is the RIL issue?
  4. Music payback with the default Music app is working for me.
  5. NFC (Near Field Communication - is this bluetooth?) - sending a file using bluetooth didn't work from my computer although it could see the phone. "Connection refused" was the error message.
Other observations:
  1. The $WITH_SU flag doesn't work with Lineage so I didn't have root baked-in. This is a disappointment.
  2. ADB thru a cable doesn't work but it does for my NookHD+ so it isn't my desktop. Error below.
  3. ADB over the network does work.
  4. Mobile network is stuck in "Connecting" but this is glitchy on 14.1 because it is stuck too after a recent flash. Wait!? A reboot fixed this! Working now.
  5. Nice and smooth responsiveness.
So progress is being made!

adb W 11-20 18:06:28 27156 27159 usb_libusb.cpp:287] failed to open usb device at usb:1:14: LIBUSB_ERROR_ACCESS
 
  • Like
Reactions: Has.007

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903
I built and flashed a 11/20 ROM, this time without flashing GApps, because I was excited to see that the FM radio was enabled again.

Alas, there was only static on my G530W. I still would like to know if the hardware has been definitely crippled on this variant or perhaps mixing/matching the proprietary firmware from other variants might enable FM.

Otherwise:
  1. WIFI is working for me.
  2. I don't even see a camera app in apps panel. It is listed in Settings->Apps.
  3. The phone can make and receive phone calls but has no audio. This is the RIL issue?
  4. Music payback with the default Music app is working for me.
  5. NFC (Near Field Communication - is this bluetooth?) - sending a file using bluetooth didn't work from my computer although it could see the phone. "Connection refused" was the error message.
Other observations:
  1. The $WITH_SU flag doesn't work with Lineage so I didn't have root baked-in. This is a disappointment.
  2. ADB thru a cable doesn't work but it does for my NookHD+ so it isn't my desktop. Error below.
  3. ADB over the network does work.
  4. Mobile network is stuck in "Connecting" but this is glitchy on 14.1 because it is stuck too after a recent flash. Wait!? A reboot fixed this! Working now.
  5. Nice and smooth responsiveness.
So progress is being made!

adb W 11-20 18:06:28 27156 27159 usb_libusb.cpp:287] failed to open usb device at usb:1:14: LIBUSB_ERROR_ACCESS

In-call audio and adb should be working. If not, you're probably missing a few repopicks. See http://msm8916.com/~vincent/repopicks.sh

As for FM radio, it may or may not be working. I haven't really done any extensive tests on that.
 

keon1

Senior Member
Jul 31, 2017
200
81
Toronto
Good to see this progress :) I have forgotten what it is called, but the red lines around the screen, does that happen to be gone? or Still existing in builds?
 

Zippy Dufus

Senior Member
Feb 12, 2011
475
178
In-call audio and adb should be working. If not, you're probably missing a few repopicks. See http://msm8916.com/~vincent/repopicks.sh

I can confirm that making/receiving calls works in a 11/21 build. My older copy of your repopicks.sh was indeed missing a couple cherry picks. That won't happen again (see snippet from my build script below).

Also, Lineage 15 has removed support for then WITH_SU flag so I did an inline ad-hoc patch to add su on to the end of the products list. The su binary was definitely build and included in the zip file but never actually got installed anywhere. I also put the L15 binary in the L14.1 su addon zip and flashed that. This didn't work either. Bummer! Still investigating.

I also trying to do an end-run around the gapps issue by installing after the initial install and boot and including a gapp-config.txt file to disable the installation of the setup wizard. No luck with that either. The adding of a new google account hung and I was getting closing of the google services as well.


echo '61c61,62
< MmsService
---
> MmsService \
> su' | patch -b $HOME/build/make/target/product/core.mk

. build/envsetup.sh

rm -f $HOME/repopicks.sh
wget -O$HOME/repopicks.sh 'https://msm8916.com/~vincent/repopicks.sh'
chmod 755 $HOME/repopicks.sh
$HOME/repopicks.sh
 
  • Like
Reactions: Has.007

Zippy Dufus

Senior Member
Feb 12, 2011
475
178
Gapps/Playstore

Is Gapps/PlayStore working on this yet?

Hacking at this, I've managed to either side-load or restore my must-have apps using Titanium backup (which I side-loaded). Interestingly, some apps could not be restored by Titanium - it froze on the progress panel.

I also installed open_gapps_arm-8.0-pico-20171119 after the initial boot up and it wouldn't get through the setup dialogue. This is the same problem after flashing Gapps after the initial ROM flash. So I used Titanium to restore the Google services data and got to the very last step of not being able to connect the the Google server and "Try again later". But it certainly did recognise my account.

If this and the camera get fixed, this ROM would be awesome!

Any ideas?

== EDIT :eek: ==

I downloaded and installed the latest version of gapps (2017/12/02 versus 2017/11/19) and all is fine now!

I don't know if it was the newer version of gapps which resolved the problem(s) or if it was my hacking described above whereby I installed without wiping the dalvik cache and re-installation let me complete the Google registration process.

Regardless, I'm ecstatic now. This is my new daily driver!
 
Last edited:
  • Like
Reactions: Has.007
Apr 8, 2016
30
1
Samsung Galaxy A51
Well, just for fun, I managed to build a (11/19) bootable ROM.

However, once booted the screen was black except for the bluetooth, network strength, and battery icons in the top right corner.

Futzing with the buttons and touching the screen, I got a panel "Setup Wizard isn't responding" and choosing either "Close app" or "Wait" continued with the black screen.

Interestingly, a little "LTE" text item is displaying over the network strength icon. My build includes the commit which uses the A3 RIL libraries. I'm not sure if this is relevant to progress in that direction.

Also, it should be noted that I probably haven't done everything needed to build this ROM properly. I did discover the repopicks.sh script which was needed to make the build complete but I suspect that I am missing some other patching.

Regardless, a great start!!

Thanks @vince2678 and all the other MSM8916 contributors.

Yes, I installed gapps and didn't think to not to do this for initial testing. Duh!

I'll try building/installing again in a week.

Thanks, and keep up the excellent work. My current build of your 14.1 ROM is simply awesome!!

Were you able to set up your Google Account? If so, how? I too installed Gapps and am now stuck with a frozen "checking info" screen...
 

Zippy Dufus

Senior Member
Feb 12, 2011
475
178
A dodgy procedure for installing Gapps

You're fine without cameras working?! :eek:

No, not fine, just patient. :silly:

Were you able to set up your Google Account? If so, how? I too installed Gapps and am now stuck with a frozen "checking info" screen...

I did A LOT of futzing around to get it installed and working. However, I am not exactly sure what I did to actually accomplish this. But, it is working great now!

I suggest this:
  1. Use the latest Open Gapps (I used pico 12/03) This might be what did the trick for me, not sure.
  2. Install Gapps after the initial flash and first bootup of the ROM. Attempt to add your Google account from Settings->Users & Accounts If this works then you are done!
  3. Add the following text file in the same directory on your phone as the Gapps zip and reflash both the ROM and Gapps. gapps-config.txt See contents below.
  4. See if you can add your google account again from Settings->Users & Accounts. If so, then done!
  5. Side load Titanium Backup APK from ADB and go to Restore all apps and system data and choose Run then Prefer snapshot. Then choose DESELECT ALL
  6. Choose to restore Google Play Services, Google Services Framework, Google Play Store but restore the Data only
  7. Go to Settings->Users & Accounts and see if you can set up your account.
  8. Steps 5 thru 7 are sketchy!. Hope you have success!
gapps-config.txt
Code:
Exclude
SetupWizard
 
Last edited:

Scholeggo

Senior Member
Sep 27, 2017
303
30
Is the team planning to release an Android Go version of Lineage OS Oreo? And to continue supporting G530P (gprimeltespr)?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 41
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.


    Code:
    ** Disclaimer
    I am not responsible if flashing this ROM bricks your
       phone or causes thermonuclear war  and ends the
        world as we know it. You have been warned.


    ROM Information


    Device Names

    Verify your device codename before downloading any firmwares or recovery images!
    Code:
    [B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
    [B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]
    [B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
    [B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
    [B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
    [B]SM-G530M[/B] - [COLOR="DarkSlateBlue"][B]fortunalteub[/B][/COLOR]
    [B]SM-G530H (XX)[/B] - [COLOR="DarkSlateBlue"][B]fortuna3g[/B][/COLOR]
    [B]SM-G530H (XC)[/B] - [COLOR="DarkSlateBlue"][B]fortunave3g[/B][/COLOR]


    Download


    Instructions


    If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

    You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.





    If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

    You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.

    Installation via recovery (TWRP/LineageOS Recovery)
    * Download a recent .zip file from the links above for your device.

    * Reboot into recovery mode [Press Power+Volume Up+Home].

    * Wipe your data and cache partition (equivalent to doing a Factory Reset)
    if you are coming from a stock ROM.


    * Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:

    * Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
    Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:

    adb sideload name_of_zip.zip

    to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.

    * Download and flash GApps in the same way.


    How to provide logcats

    Under Windows:


    Code:
    [B]* Install samsung device drivers and then
     the adb utils from here:[/B]
    
    [url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
    
    [b]* Then enable developer mode, connect your phone to usb,
     and from [B]cmd[/B] paste this command:[/b]
    
    [I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
    
    [b]then try to reproduce the bug.[/b]
    
    [b]* The logcat file will be on your desktop.[/b]



    Under Linux:


    Code:
    [b]* Install the adb utils from your distribution's
     package manager and execute the command:[/b]
    
    [I]adb logcat > ~/logcat.txt[/I]
    
    [b]then try to reproduce the bug.[/b]
    
    [b]* The logcat file will be on your home directory.[/b]

    * Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.

    * If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:

    Code:
    adb connect [ip address here]

    And then the adb logcat command for windows.



    FAQ

    Q: Are you taking device requests?
    A: No.

    Q: Are you accepting feature requests?
    A: No.

    Q: Can you make XXX ROM as well as LOS?
    A: No.

    Q: Can I throw money at you?
    A: Most certainly. Donations are always welcome.

    XDA:DevDB Information
    [UNOFFICIAL][ROM] LineageOS/Go 15.1 for Grand Prime [S920L/G530H/FZ/M/MU/P/T/T1/W], ROM for the Samsung Galaxy Grand Prime

    Contributors
    vince2678, minz1, vlw, Danil_e71
    Source Code: https://github.com/Galaxy-MSM8916

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: >= 4.4 (KitKat)
    Based On: LineageOS

    Version Information
    Status: Beta

    Created 2017-11-12
    Last Updated 2018-09-03
    11
    Important

    If this is your first time flashing O, you will need to install the latest unofficial TWRP image for your device from the links above before flashing a zip image, otherwise installation of a zip will invariably fail.

    For SM-G530P users, use the gprimelte unofficial twrp instead of the gprimeltespr one.
    For SM-S920L users, use the gprimeltetfnvzw official twrp instead of the unofficial gprimeltetfnvzw one.
    10
    What works

    Code:
    [B]
    * RIL (in-call audio, messaging, [I]data possibly[/I])
    * Bluetooth (including audio)
    * WiFi
    * Audio (music, etc)
    * Camera (including video recording)
    * Flash
    * Sensors
    * GPS
    [/B]

    Known Issues

    Code:
    [COLOR="RoyalBlue"][B]SM-G530P | SM-S920L [/B][/COLOR]
    * [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] In-call audio is buggy (there's a persistent ring tone during calls).[/B]

    Code:
    [COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
    * [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] NFC does not work. This is indefinitely broken[/B]
    * [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Encryption does not work. This is indefinitely broken[/B]

    Changelog

    Code:
    [COLOR="Red"][B]09/02/2018[/B][/COLOR]
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Core control has been disabled permanently, in-kernel. [/B]
    
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] NFC may (or may not) be working this build on capable devices.
       This is Untested. [/B]
    
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Rebased lineage-15.1 branches in repos. This is mostly
       for our benefit; just to tidy up the repos and make commit history more descriptive,
       accurate and give proper credits to commit authors. [/B]
       
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Camera recording should be working again.
       This was broken due to upstream android security change. [/B]
    
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Reworked zram support in ROM. There are now two zram properties:
    	[I]ro.config.zram.enabled[/I] and [I]ro.config.zram.size[/I]
    	Set [I]ro.config.zram.enabled[/I] [I]true[/I] to enable zram;
    	and [I]ro.config.zram.size[/I] to set the size of the zram disk.
    
      If you set this too large the system will slow down. You can also just use a zram
      zip from the download server to do this automatically.[/B]

    Code:
    [COLOR="Red"][B]08/12/2018[/B][/COLOR]
    * [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Camera recording is broken.
       This is due to upstream android security change. [/B]
    
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Reworked zram support in ROM. There are now two zram properties:
    	[I]ro.config.zram.enabled[/I] and [I]ro.config.zram.size[/I]
    	Set [I]ro.config.zram.enabled[/I] [I]true[/I] to enable zram;
    	and [I]ro.config.zram.size[/I] to set the size of the zram disk.
    
      If you set this too large the system will slow down. You can also just use a zram
      zip from the download server to do this automatically.[/B]
    
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Enabled zram by default for low-ram (1GiB) devices [/B]


    Code:
    [COLOR="Red"][B]07/26/2018[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Camera recording should be working normally again [/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] sdcard (vfat/fat32) should work fine in recovery [/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Some stutter and lag issues have been fixed 
         (tweaked core_control, among others) [/B]
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] exFAT support has been restored [/B]
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Re-enabled QS transparency [/B]
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Removed go-gapps from lineage-go [/B]
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] Reduced kernel logcat buffer size from 512KB to 256KB (slight RAM saving)[/B]
    * [B][[COLOR="Blue"]NOTE[/COLOR]][/B] [B] zram has been disabled by default. If you want this, you can set the 
        property [I]ro.config.zram[/I] to true[/B]

    Code:
    [COLOR="Red"][B]06/03/2018[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Frequency scaling issues should be fixed (stutter after suspend/resume should be gone). [/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] In-call audio should be fixed on multi sim devices. [/B]

    Code:
    [COLOR="Red"][B]06/01/2018[/B][/COLOR]
    * [B][[COLOR="Blue"]MISC[/COLOR]][/B] [B] Go GApps are now embedded in LineageOS Go builds. [/B]

    Code:
    [COLOR="Black"][B]05/28/2018[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Frequency scaling should be fixed (improved power savings) [/B]

    Code:
    [COLOR="Black"][B]05/21/2018[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Thermal engine is now working proper (for better temperature control) [/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Hidden Wi-Fi networks should now be connectable/reachable [/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Power hal is now working proper (resulting in improved battery usage)[/B]
    * [B][[COLOR="Blue"]MISC[/COLOR]][/B] [B] RIL includes updated [/B]
    * [B][[COLOR="Blue"]MISC[/COLOR]][/B] [B] Misc. kernel updates (sdcardfs, binder) [/B]

    Code:
    [COLOR="Black"][B]04/27/2018[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Brightness adjustment should be fixed for the fortuna3g/SM-G530H[/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] In-call audio should be working for the second sim on dual-sim devices[/B]

    Code:
    [COLOR="Black"][B]04/24/2018[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Sim detection should be fixed for fortuna* devices.[/B]

    Code:
    [COLOR="Black"][B]04/23/2018[/B][/COLOR]
    * [B][[COLOR="Green"]MISC[/COLOR]][/B] [B] Added fortuna* devices.[/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Video recording now works[/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Bluetooth audio is fully working[/B]

    Code:
    [COLOR="Black"][B]13/03/2018[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] In-call audio should be working in the latest build[/B] 
    
    * [B][[COLOR="Orange"]PARTIAL FIX[/COLOR]][/B] [B] Camera flash and previews should be working, however, saving pictures or videos will not work. [/B]

    Code:
    [COLOR="Black"][B]06/02/2018[/B][/COLOR]
    * [B][[COLOR="Red"]REGRESSION[/COLOR]][/B] [B] In-call audio is broken [/B]

    Code:
    [COLOR="Black"][B]20/11/2017[/B][/COLOR]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] WiFi is working[/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] RIL functions (Calling, texting, data) should be working, including in-call audio [/B]
    * [B][[COLOR="Green"]FIX[/COLOR]][/B] [B] Music and video playback should be working [/B]

    Code:
    [COLOR="Black"][B]12/11/2017[/B][/COLOR]
    * [B][[COLOR="Green"]NOTE[/COLOR]][/B] [B] First working image built. [/B]

    8
    I've regenerated all twrp images - the sdcard (fat32/vfat) issue should be fixed.

    These are dated '20180725' and are available on the download server (link in OP).
    6
    Yeah.. That would be silly, as the error says.

    === Edited ===

    I'll elaborate. I don't mean to sound rude in my previous post.

    The kernel and all critical system services need some memory, both static (for the kernel code, application code, etc) as well as space for accounting or anything variable (page tables and other data structures).

    The system will absolutely let you set a ridiculous size for zram, no doubt. But since zram is swap (with the highest possible swapping priority set), the kernel will swap out any pages it can if it has the chance. Since there'll be so much space in zram, the kernel will eventually try to swap out more than is tenable (zram is in *RAM*, so past a certain point swapping a page from RAM to RAM will have no saving, even with compression) and thrashing will result, making the system grind to a halt.

    ZRAM also does not automatically clean up freed up space. So, for example, if I make a 1GB zram, format it with a file system, say ext4, and fill it up with a zeroed file, then remove the file, all that space will still be marked as allocated in RAM in the kernel, even if the file system says it's free, since the kernel doesn't know how zram works, nor zram how any underlying data structure placed on it works. You will need to deactivate the zram disk (and thus deallocate the memory) to free up that space.

    So, when you get that warning, don't ignore it and go set the size manually anyways using kernel adiutor or something else. It's a cause for trouble.

    And when I change something in the ROM, say disable zram for all devices, it's for reasons like this. Me, Sean and Emery were very much against this and other decisions by Dyneteve, like core control, because forcing optimizations like this on users is very bad. Trust me on this. So the compromise I reached was to leave them there, but disabled.

    I have a degree in these things; I'm a computer scientist, favouring low level system design and programming, so trust me when I make a decision like this.

    === Edited ===