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

[ROM][G930F/FD/W8/S/K/L][7.1.1] OFFICIAL LineageOS 14.1 for Galaxy S7

Search This thread

djfw

Member
Apr 24, 2018
5
0
MMS only apn's have no radio button to switch to that apn

Hi,
I am trying to get MMS to work on 14.1-20180301-NIGHTLY-herolte. I am using the Australian Optus network. If I reset the apn's all MMS only APNs have no radio button to activate them. If I change an existing APN to MMS only it is moved down the list to the top of the MMS only APNs and it's radio button is removed.
I have tried merging internet and MMS parameters, but MMS does not work on that APN.
Previously MMS apn's worked.
Cheers,
David
 

thomaso

Member
Oct 3, 2008
48
2
Worse pictures taken by camera at night

Did anyone else got the same problem?
At night the camera shots really worse pictures.
Actually I am using the latest nightly 14.1 LOS version on my Samsung S7 with Exynos8890 chipset.
The camera chipset is not shown in any hardware ident tool.
So far I a asume it is not the Sony camera.
 

Pat750

Senior Member
Sep 12, 2016
595
260
Did anyone else got the same problem?
At night the camera shots really worse pictures.
Actually I am using the latest nightly 14.1 LOS version on my Samsung S7 with Exynos8890 chipset.
The camera chipset is not shown in any hardware ident tool.
So far I a asume it is not the Sony camera.
You can check your camera with Aida64 app, but I remember it only shows what camera you have (Sony or "normal") on stock ROM, so you have to restore your stock ROM to check it.
 

thomaso

Member
Oct 3, 2008
48
2
You can check your camera with Aida64 app, but I remember it only shows what camera you have (Sony or "normal") on stock ROM, so you have to restore your stock ROM to check it.

The AIDA64 APP did not say anything about the camera. Just nothing. Seems to be not available.
Has there anyone the same topic with the night pictures?
 
Last edited:

Attachments

  • IMG_20180424_212430.jpg
    IMG_20180424_212430.jpg
    248.3 KB · Views: 802
  • IMG_20180424_220732.jpg
    IMG_20180424_220732.jpg
    259.2 KB · Views: 781

thomaso

Member
Oct 3, 2008
48
2
It seems that the flash is not synchronised with camera and so the pictures habe always sparkles everywhere.
Will attache a picture for better explanation.
Sometimes the pictures have a little more light but the spreads are almost there.
 

Attachments

  • IMG_20180427_235553.jpg
    IMG_20180427_235553.jpg
    235.8 KB · Views: 416
Last edited:
  • Like
Reactions: Allmightyusfame

zSyntex

Senior Member
Sep 24, 2017
181
155
Bari, Apulia
Samsung Galaxy S21+
Right. I tried several camera apps. Same result everwhere.
At all grained pictures without the right flashlight.
No workaround available?
Will it make sense to switch to other ROM like Batman?

Like now, I'd suggest to use LineageOS 15.1 or Stock Based ROM (like UltimateNougat, Batman is no longer updated->ported to SuperMan ROM).
On Stock Based, the Camera is better than the Official Stock ROM (Nougat), so If you'd like Audio & Photo Quality, go for stock based way.
If you want to try newer Android Version, more or less stable, try LOS 15.1
Hope I've helped you :)
 

thomaso

Member
Oct 3, 2008
48
2
Like now, I'd suggest to use LineageOS 15.1 or Stock Based ROM (like UltimateNougat, Batman is no longer updated->ported to SuperMan ROM).
On Stock Based, the Camera is better than the Official Stock ROM (Nougat), so If you'd like Audio & Photo Quality, go for stock based way.
If you want to try newer Android Version, more or less stable, try LOS 15.1
Hope I've helped you :)

Thanks a lot.
I do not why I had written Batman. In mind I got Superman.
As far as I can see at 15.1 there are topics with GPS.
So the only solution for me will be the stock rom based Superman ROM? Right? Valid Version 2.9.

I may be wrong, but the problems occur because of the topics with provided drivers from Samsung. Is may assumption correct?
I was using a HTC M8. This runs smooth and softly but ony the batteriedrain was to hard right now.
The phone was in use since the release date. Perfect.
Now I see the troubles with S7. Again a Samsung?
Not at all. May be a OnePlus or again HTC. Never used the original ROM. The CM and LOS where perfect for my demand.
 
Last edited:

mayhemrules

Senior Member
Feb 3, 2012
66
22
Thanks a lot.
I do not why I had written Batman. In mind I got Superman.
As far I as I can see at 15.1 there are topics with GPS.
So the only solution for me will be the stock rom base Superman ROM? Right?

I may be wrong, but the problems occur because of the topics with provided drivers from Samsung. Is may assumption correct?
I was using a HTC M8. This runs smooth and softly but ony the batteriedrain was to hard right now.
The phone was in use since the release date. Perfect.
Now I see the troubles with S7. Again a Samsung?

I came from Superman and although decent the snapiness and speed on LOS is just too great. Ill try another nightly and report.
 

zSyntex

Senior Member
Sep 24, 2017
181
155
Bari, Apulia
Samsung Galaxy S21+
Thanks a lot.
I do not why I had written Batman. In mind I got Superman.
As far as I can see at 15.1 there are topics with GPS.
So the only solution for me will be the stock rom based Superman ROM? Right? Valid Version 2.9.

I may be wrong, but the problems occur because of the topics with provided drivers from Samsung. Is may assumption correct?
I was using a HTC M8. This runs smooth and softly but ony the batteriedrain was to hard right now.
The phone was in use since the release date. Perfect.
Now I see the troubles with S7. Again a Samsung?
Not at all. May be a OnePlus or again HTC. Never used the original ROM. The CM and LOS where perfect for my demand.
That's why I don't suggest a Galaxy S7 to anyother user who like to mod its device.
LineageOS 15.1 has the GPS FIX since a months, and works better than the stock one.
SuoerMan and UltimateNougat are also very good, trust me :)

But I like the AOSP, so I've gone to LOS. CM is dead (now is LOS) but I flashed it since CM 6.1 and 7.1 for Galaxy S2 hehe
 

LGaljo

Senior Member
Like this, ever new 15.1 official? should focus on developing 15.1 or 16

Just wait. We have Oreo sources for less than a week and you expect a 100% working build in a matter of couple of days? Nobody pays developers to rush with developing ROMs. They do that in a free time.

On other note, @Ivan_Meler will help to complete LOS 15.1. He said we should expect his unoffisial builds in a few days/week (source). These builds are almost 100% working. He got everything except GPS working (dont count in VoLTE and Camera quality) without Oreo sources.
He added that he joined LOS team, which will merge his work from unofficial to official LOS sources (source).

You don't need to ask for ETAs... Learn to look after dev's sources on github and review.lineageos.org. Here are some links:
https://github.com/ivanmeler?tab=repositories
https://review.lineageos.org/#/q/owner:davikovs%40gmail.com
https://review.lineageos.org/#/q/owner:i_ivan%40windowslive.com
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_samsung_universal8890
https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_herolte
https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_hero2lte
https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_hero-common
https://review.lineageos.org/#/q/project:LineageOS/android_hardware_samsung_slsi-cm_exynos8890
https://review.lineageos.org/#/q/project:LineageOS/android_hardware_samsung

I hope that you appreciate that post. Press thanks if you learned sth new :)
 
Last edited:

Cường Hồ

Senior Member
Dec 3, 2014
404
43
Just wait. We have Oreo sources for less than a week and you expect a 100% working build in a matter of couple of days? Nobody pays developers to rush with developing ROMs. They do that in a free time.

On other note, @Ivan_Meler will help to complete LOS 15.1. He said we should expect his unoffisial builds in a few days/week (source). These builds are almost 100% working. He got everything except GPS working (dont count in VoLTE and Camera quality) without Oreo sources.
He added that he joined LOS team, which will merge his work from unofficial to official LOS sources (source).

You don't need to ask for ETAs... Learn to look after dev's sources on github and review.lineageos.org. Here are some links:
https://github.com/ivanmeler?tab=repositories
https://review.lineageos.org/#/q/owner:davikovs%40gmail.com
https://review.lineageos.org/#/q/owner:i_ivan%40windowslive.com
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_samsung_universal8890
https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_herolte
https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_hero2lte
https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_hero-common
https://review.lineageos.org/#/q/project:LineageOS/android_hardware_samsung_slsi-cm_exynos8890
https://review.lineageos.org/#/q/project:LineageOS/android_hardware_samsung

I hope that you appreciate that post. Press thanks if you learned sth new :)
A lot of roms are looking to the rom lineage, they have moved to another device, they probably have the official 8.0,,???

---------- Post added at 12:09 PM ---------- Previous post was at 11:56 AM ----------

I have m9 and s7, I feel sad, for example crdroid for example, other devices have 8.1.0,4.2, lineage m9 seems to stop growing but luckily the claymore continues to grow, and s7 ... ? ??
 

hazzl

New member
May 11, 2018
2
0
Having trouble installing official LineageOS 14.1 on Galaxy S7

Hi there,

I've recently bought a Galaxy S7 (SM-G930F) to replace my broken Galaxy S4-mini (serranoltexx). I've been running LineageOS on my S4-mini for a long time and was hoping to do the same on my new device. However, I haven't been able to get LineageOS to run on my new phone :crying:

I've followed the official installation instructions, installing TWRP 3.1.1 instead of 3.2.0 because I've read here that the latter does not work with Nougat-based ROMs. I have also unlocked OEM-lock in the developer options.

However, my device gets stuck in the first boot process. The boot animation just never stops with no sign of what went wrong.

Is there anything I can do to further debug the issue? I'm currently running UltimateNougat (based on stock). But I would really prefer using LineageOS because of its better configurability.

Thanks in advance for any advice!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 151

    QCgMClH.png


    Code:
    [COLOR="red"]Your warranty is now void.[/COLOR]
    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. 
    A lot.

    /* What’s working */
    Audio
    Bootanimation
    Brightness Level
    Bluetooth
    Camera *needs to be improved
    Microphone
    Fingerprint reader
    MTP
    NFC
    Wi-Fi
    LED
    RIL (calls, sms, microphone, data)
    Torch
    All sensors except fingerprint reader
    SD Card
    Capacitive buttons
    Torch
    Wi-Fi Hotspot

    /* What’s not working */
    You tell me

    Install Instructions
    1. Download ROM from the link below.
    2. Wipe dalvik/cache/data/factory reset.
    3. Flash the rom in recovery.
    4. Reboot device.
    5. Now you can help me to find bugs :)

    Quick Look


    Thanks @KiaTheKing

    Downloads

    Latest Build​



    ExyGen² staff:
    Fevax, fedegin, jah2110, briann_cs

    If you are happy with my work, please:





    Thank You! :victory:

    XDA:DevDB Information
    OFFICIAL LineageOS 14.1 for Galaxy S7, ROM for the Samsung Galaxy S7

    Contributors
    Fevax, jesec
    Source Code: https://github.com/Fevax

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: N Bootloader and Modem
    Based On: LineageOS

    Version Information
    Status: Nightly

    Created 2017-01-04
    Last Updated 2017-06-10
    30
    Changelog:

    20170115 -> 20170205
    - Fingerprint deletion bug is now fixed by preventing users to enroll more fingerprints than what HW allow.
    - Some network-related problems are now fixed.
    - Battery life should be improved now.
    - HW encoders and decoders are enabled again.
    - Size of package is reduced. (from approx. 570M to 460M)
    - Wi-FI hotspot is fixed.

    01/15
    hero-common: disable Exynos HW encoders
    * This change fixed video recording(in camera app and other apps like Snapchat).

    audio: redo mixer_paths
    * This change fixed headset mic and other audio-related problems.

    01/14
    Off-mode charging is fixed.

    01/13
    Fingerprint reader is now fixed.

    01/11
    kernel: bcmdhd4359: update to 1.363.59.181
    * This change updates Wi-Fi driver to a much newer version. Should improve Wi-Fi stability and signal strength.

    01/09
    hero-common: add back Snap camera
    - Image quality of built-in camera should be better now.

    PD: Some users are reporting battery drain on this build.

    01/08
    universal8890: Use custom rssi buckets, ignoring rssnr
    - This change should make LTE signal looks stronger.

    hero: add power profile
    - This change fixed battery stats.

    vendor: wifi: set country code to ALL
    - This change should fix Wi-Fi problems in some countries.

    vendor: wifi: add some hacks to make Wi-Fi signal strength stronger
    - I am not sure if it works lol.

    01/07
    - Vibrator is now fixed.
    - Rendering issues is now solved (but not on stock android browser, you are recommended to use Chrome or other browsers).
    - Enabled multiwindow support.
    - Some performance improvements.
    - Add gains to input/output volume(should fixed low volume problem in some situations). Also maybe mic problem of Viber and some IM apps is fixed.

    01/06
    - Snap Camera was removed and has been replaced by Google Camera, now the camera should work a lot better than previous build.
    - GPS now has been completly fixed, it was working but with some errors that cause performance issues.
    - Microphone was not working on some applications, now should work fine. Still have some problems while using headphones, we're working on that.
    - General performance has been improved.
    - DualSIM support, now should work on FD variant, please report.
    - Now the random freeze problem should be gone.
    - Video playback will work after a second reboot due to SELinux, please report.

    01/02
    - Camera has been fixed, it won't work anymore when you closed it due to some HAL problems, we're working on that. It will work again after a few minutes.
    - Now flashlight it's working, but it will work when camera works.
    - GPS has been fixed.
    - Low volume audio via headphone jack has been fixed.

    12/30
    - Initial Release.
    21
    Yeah I am totally aware of the Exynos nightmare, I was just wondering how they dealt with previous CM versions. Were there an official support for CM13,14,... for S6 and S7 (both missing from lineage offficial) or was it always based on unofficial built?
    Official builds will come the next week ;)
    20
    Weekly builds have been re-enabled and I have joined official herolte/hero2lte LineageOS maintainers.

    The following device-specific things are fixed in today's build:
    • BUGBASH-1270 OTA updater (thanks @fabwu for doing most of the work). Ota updates will start to work AFTER manually installing this build and TWRP version 3.2.1-1 (or newer). CC: @Blato @pluto123 @gnarf49
    • BUGBASH-840 Low microfone recording volume
    • BUGBASH-1169 Inability to play videos and phone overheating + draining battery, after playing some/many videos (this is fixed by workaround, proper fix will be included in one of further builds)
    18
    Samsung releases kernel source with almost all major update, so we have sources, and (on Google git) it's available the exynos5 userspace source (deprecated, but modified to work with new devices by cm staff)

    So, it's true, we doesn't have "proper and specific" source for every device like qcom has, but we have a great group of people working every day to make this happen, backtracing, decompiling apps and lib, researching how the weird Sammy works...