Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version of LineageOS 19.1 for our Samsung Galaxy S3 (I9305).
This is a beta build, also from the LineageOS side, there are typical functions still missing, so don't install it if you want a completely stable and completed ROM and don't report my already listet bugs!
Attention:
Sometimes it needs another reboot to find the sim card.
When you have BitGapps installed, you have to reflash them after every update!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
Random reboots
NFC
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
I9305 ROM
ROM Mega
Spoiler: Changelog
11.02.2022
14.02.2022
15.02.2022
08.03.2022
17.03.2022
25.03.2022
04.04.2022
19.04.2022
15.06.2022
27.09.2022
23.01.2023
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /vendor/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][I9305][BETA] LineageOS 19.1, ROM for the Samsung Galaxy S3 LTE
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2022-02-10
Last Updated 2023-01-23
*reserved
Update 11.02.2022:
Fixed GPS completely
Some RIL-Work, still buggy, I'm working hard to find a solution
Update 14.02.2022:
Fixed APN setting problem at boot.
Update 15.02.2022:
Fixed GPS completely, including 3D fix
Fixed low signal for 3G and 2G network
Update 08.03.2022:
Synched with latest LineageOS sources
html6405 said:
Update 08.03.2022:
Synched with latest LineageOS sources
Click to expand...
Click to collapse
Thank you for the great job. Having 12 on our old SIII is amazing ! Have now a very limited use of this device with Build 0215 - but works like charm. Although tech is old, transitions and speed are more than acceptable, ...
Have tried update OTA but ended in bootloop on LOS logo.
Tried a clean install with 0308 build same bootloop.
Tried Magisk - stuck on Samsung logo
Restored build 0215
Captain Kangaroo said:
Have tried update OTA but ended in bootloop on LOS logo.
Click to expand...
Click to collapse
Did you have older bitgapps installed?
(If yes, you would have to reflash them)
It's hard to say why you're facing a bootloop, it did really work fine on my testing device.
html6405 said:
Did you have older bitgapps installed?
(If yes, you would have to reflash them)
It's hard to say why you're facing a bootloop, it did really work fine on my testing device.
Click to expand...
Click to collapse
I use my SIII gappless, same with my S5. => I ota over 0215 gappless !
Then I did several attempt: after full format:
- restore build 0215 + flash Magisk + Bitgapp didn't work
- flash build 0308 + Magisk 24.2 or 21.4 didn't work
- flash build 0308 + Bitgapp for 12 didn't work
- flash build 0308 + MindTheGapp for 12 didn't work
So far, its fine with 0215 for my limited use (no tel, no text, no mail client, few use of internet browser, few specific Apps installed: SDMaid, AllToolinONE, Mixplorer, MusicSpeedChanger. Except Mixplorer where I noticed some laggy transitions, the other apps work fine.
Sorry I did'nt logcat fo you
Captain Kangaroo said:
Sorry I did'nt logcat fo you
Click to expand...
Click to collapse
This would have pointed me maybe to the problem,
my device still works fine, but I may will try a factory reset.
(I'm using it with gapps at the moment)
Update 17.03.2022:
Switched to Android 12L , attention, this could not work with your existing gapps! (mindthegapps will work)
A clean installation is recommended.
html6405 said:
Update 17.03.2022:
Switched to Android 12L , attention, this could not work with your existing gapps! (mindthegapps will work)
A clean installation is recommended.
Click to expand...
Click to collapse
Clean install 19.1-20220317-HTML6405-i9305.zip, no gapp went very well. So far so good
Update 25.03.2022:
Synced with latest LineageOS sources
Created possibility to disable the HW navigation keys (not really needed for full gesture navigation)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
html6405 said:
Update 25.03.2022:
Synced with latest LineageOS sources
Created possibility to disable the HW navigation keys (not really needed for full gesture navigation)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
Click to expand...
Click to collapse
Great job
OTA update done like a charm
HW keys disable is good as I use navigation bar
Will see for the 2 last item …
On previous version 0317, I succedded to flash magisk 24.3 but didn't work properly - device became very laggy or stuck, the permissions granted didn't stay, therefore I removed it
does volte works?
EeeK said:
does volte works?
Click to expand...
Click to collapse
No, never worked with any custom ROM,
Samsung didn't publish their proprietary implementation for VOLTE.
Maybe interesting!?
ComputerBase: Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones.
Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones
Samsung legt mit rückwirkend bis zu zehn Jahren Android-Updates für historische Smartphones wie das 2012 vorgestellte Galaxy S III nach.
www.computerbase.de
larswars said:
Maybe interesting!?
ComputerBase: Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones.
Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones
Samsung legt mit rückwirkend bis zu zehn Jahren Android-Updates für historische Smartphones wie das 2012 vorgestellte Galaxy S III nach.
www.computerbase.de
Click to expand...
Click to collapse
Good to know but April Fool's Day !!!!!!
@larswars @html6405 @rodman01
larswars said:
I encountered update 7 error when trying to flash the ROM in Tre, any idea?
Click to expand...
Click to collapse
Maybe wrong TWRP used.
Related
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.
Code:
/*
* Your warranty is now void. Knox 0x1.
*
* We are 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 us for messing up your device, we will laugh at you.
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
WARNING:
This is not a stable version of LineageOS. If you run into problems, give us a logcat as you report your problem or GTFO.
If your problem cannot be reproduced without using Magisk modules or Xposed, don't report it! The same goes with custom kernels.
Prerequisites:
The latest version of TWRP. This is an absolute requirement.
Your Samsung Galaxy Note 3.
The latest modem and your bootloader unlocked. Link on how to get that done is found below.
How to flash this ROM:
From other custom ROMs (RR-O, LineageOS 14.1, etc):
Download the zip file for your variant of the device. Use the table below to figure out which variant to use.
Make sure this zip file is saved to your device (just to get things done quickly).
If you want Google Play functionality, download OpenGApps (link below). (optional)
Reboot into TWRP (Volume Up + Home + Power or Advanced Restart).
Make a backup (optional).
Wipe System, Data, Cache, and Dalvik Cache partitions with Advanced Wipe. (required if upgrading from LOS 14.1 or RR-N)
Flash the ROM you just downloaded.
Flash OpenGApps for Android 8.1 if you want Google services (optional).
If you want root, flash Magisk.
Reboot and proceed normally with installation.
From LineageOS 15.1 (if you're updating):
Download the zip file for your variant of the device.
Reboot into TWRP.
Flash the zip file as normal. No wipes needed.
Reboot. You have updated your device.
Variants:
It is important that you get the right variant based on your model code! Otherwise, you might not be able to make phone calls, and run into other bugs!
hlte: SM-N9005 (unlocked, GSM) and SM-N900P (Sprint)
hltetmo: SM-N900T (T-Mobile), SM-N900W8 (Canada), SM-900R4 (USA Cellular), SM-N900V (Verizon)
hltechn: SM-N9008V and SM-N9006 (both are China)
hltekor: SM-N900S (SK Telecom), SM-N900L (LG Uplus), SM-N900K (KT Corp)
The Exynos variant (ha3g) is bound to gain support soon.
The SM-N900A (AT&T) might never get support due to its locked bootloader. That is unlikely to change.
Download links:
AndroidFileHost (haggertk): [url]http://androidfilehost.com/?w=files&flid=244014[/URL]
AndroidFileHost (mine): [url]https://androidfilehost.com/?w=files&flid=245260[/URL]
OpenGApps 8.1 (biggest is mini for Note 3): [url]http://opengapps.org[/URL]
Latest bootloader & modem (contains instructions): [url]https://forum.xda-developers.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504[/URL]
Magisk: [url]https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
Source code:
LineageOS on GitHub
Contact us on Telegram if you must! [url]https://t.me/galaxynotethree[/URL]
LineageOS 16.0 (unofficial) for HLTE currently exists now! Come check out the thread by clicking [url]here.[/URL]
Credits:
The LineageOS Team
haggertk
Trader418 (started the hype back in August 2017)
Version Information:
ROM OS Version: Android 8.1 Oreo
Kernel Version: Linux 3.4.x
Let's Help the developers to fix the remaining bugs on this ROM by posting the logs of bug you encountered to this thread. And u can say how to reproduce that bug... Here are the links that might help you on how to get a logs properly...
1. https://github.com/M66B/cm-xtended/wiki/How-to-get-logs
2. https://forum.xda-developers.com/showthread.php?t=1726238
lineage-15.1-20180128-UNOFFICIAL-hltechn.zip
for Samsung Galaxy Note 3. Suitable for device with two SIM card sm n9002?
This is the first rom.
Its not tested by many people I guess.
Maybe you should even try and report?
Known bugs in hlte version (20180128) (SM-N9005):
NFC doesn't work
Can't select lock screen password, pattern or pin (if you select one, phone crashes and you have to factory reset)
Can't rotate screen
For now, this is the bugs that I've detected, at least, on my phone.
I have to say that is a VERY STABLE rom, I've been trying for one day and I hadn't got much problems, only known bugs. Xposed installed, SIM detected, Magisk installed... very good ROM.
Fantastic ROM for such an early release. Battery life is amazing. few quirks with apps not holding root, and Bluetooth audio having a hiss on SM-N900W8 nonetheless magical start for such an early bake!
Thanks for your time and support for our old Notes.
SIM CARD DON'T WORKING ON HLTE!
Sent from my Galaxy Note 3 using XDA Labs
Nice and smooth
Been running this on a Verizon note 3 running on tmo and I haven't had any hiccups yet.
banikgames said:
SIM CARD DON'T WORKING ON HLTE!
Click to expand...
Click to collapse
Its working on mine.. u probably need the latest modem and bootloaders..
almost stable. but video recording on me crush, the volume is too low. but everything is good.. ?
Ok. Can u give me link to download latest modem/bl?
Sent from my Galaxy Note 3 using XDA Labs
banikgames said:
Ok. Can u give me link to download latest modem/bl?
Sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
look on my signature and search in general thread..
J_viix__ said:
Known bugs in hlte version (20180128) (SM-N9005):
NFC doesn't work
Can't select lock screen password, pattern or pin (if you select one, phone crashes and you have to factory reset)
Can't rotate screen
For now, this is the bugs that I've detected, at least, on my phone.
I have to say that is a VERY STABLE rom, I've been trying for one day and I hadn't got much problems, only known bugs. Xposed installed, SIM detected, Magisk installed... very good ROM.
Click to expand...
Click to collapse
No issue with lockscreen PIN code...work flawlessly
Im using n9005 hlte, i can set pattern or pin and it works perfectly. My only issue ive faced is the distortion in sound when i received a notification. Example when im playing music or videos from youtube then a notification came the notification sound was distorted for a couple of seconds then it will go back to normal.
help me
please help me
i wan't download rom
but ican't
this all in the download page
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
Downloads for : Samsung Galaxy Note 3
Developed By :
haggertk
Root
lineage-15.1
3 Folder(s) | 0 File(s)
Sort |
hlte [ 0 Folders | 1 Files ] Jan 28, 2018 | 06:14PM
hltechn [ 0 Folders | 1 Files ] Jan 28, 2018 | 06:20PM
hltetmo [ 0 Folders | 2 Files ] Jan 27, 2018 | 05:31AM
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
and i wan't to download gapps
but i wan't to know chose any one from links in post
this link in post
Quote:
Originally Posted by shivy23
Pico: open_gapps-arm64-8.1-pico-20171215-UNOFFICIAL.zip
Nano: open_gapps-arm64-8.1-nano-20171215-UNOFFICIAL.zip
Stock: open_gapps-arm64-8.1-stock-20171215-UNOFFICIAL.zip
Aroma: open_gapps-arm64-8.1-aroma-20171215-UNOFFICIAL.zip
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
Error message appears while flashing from twrp 3.1.1. Model N900W8
fad19 said:
Error message appears while flashing from twrp 3.1.1. Model N900W8
Click to expand...
Click to collapse
I guess u need to update to TWRP 3.2.1
How to flash without error on N900W8
Compatible for SM-N900S?
jonneldj said:
Compatible for SM-N900S?
Click to expand...
Click to collapse
If you have N900S i think you should try and report back. It's just strated
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (LP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
BEFORE INSTALLING THIS ROM, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE
IF YOU ASK ANY QUESTIONS LIKE "IS THIS FOR MODEL BLABLABLA" THEY WILL BE ALL IGNORGED
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
We'll not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our intructions word by word
are unfriendly
And most important: DON'T READ THE OP
What's working:
Wifi (connection, tethering, etc)
Bluetooth (need quick patches in download link)
Camera, video codecs
RIL (Calls, SMS, mobile data)
Storage (both internal and external)
MTP storage (both internal and external)
Offline charging
zRAM (compressed-RAM swap)
GAPPS
Tethering (USB, Wifi, Bluetooth)
GPS
Sound recording
Torch (flashlight)
BUGS/Not working:
Laggy recorded videos. In this case, use MX Player, choose SW codecs when you play these videos, they will become normal
Switching to other fonts will get bootloops after restart. In this case, if you use TWRP recovery, go to File Manager >> delete "themes" from /data/system would help you escape this without factory reset
First time installing CyanogenMod 12.1 to your Galaxy , or coming from another ROM:
Install TWRP Recovery
Reboot into Recovery using 3-button-combo (Vol-up+Home+Power)
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)*
Install the ROM from sdcard using TWRP Recovery
Optionally install the Google Apps ( get it here: https://opengapps.org ) (pico GAPPS recommended)
Quote:
DOWNLOADS:
ROM: Link
CHANGELOG
Code:
- 2016/06/25
+ Initial release, ported from Galaxy V's CM12.1
- 2016/06/27
+ Switched to built-from-source, no more portings
+ Fixed nearly all problem, except fonts
+ Underclocked to 1,2GHz for stable usage
+ Enable multi-threaded dex2oat >> Faster app installation
+ Fixed installation for some apps (FB, etc...)
Want some screenies? Get them from Screenshot tab
XDAevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy
Contributors
Erwin Abs
Source Code: https://github.com/jnkcode/android_kernel_samsung_j13g/tree/cm-12.1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 4.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 2
Stable Release Date: 2016-06-27
???
always says SETUP WIZARD HAS STOPPED
- works stable
- issues with WiFi and Bluetooth. WiFi cannot connect - you have to enter the same password multiple times when connecting for the first time. Then it keeps failing to connect from time to time
- more laggy than stock rom and resurrection remix
- installation is very straightforward
Thanks for sharing this rom. Lots of good work.
Lord87 said:
- works stable
- issues with WiFi and Bluetooth. WiFi cannot connect - you have to enter the same password multiple times when connecting for the first time. Then it keeps failing to connect from time to time
- more laggy than stock rom and resurrection remix
- installation is very straightforward
Thanks for sharing this rom. Lots of good work.
Click to expand...
Click to collapse
Try this https://androidfilehost.com/user/?w=settings-dev-files&flid=205876
CyanogenMod 12.1 for SM-J100H with dual SIMs
Thanks for posting this ROM, gave me a chance to test in on a SM-J100H with dual sims: flashed the ROM, the fix and then gapps. Was thinking not to have gapps but an app was requiring Google Play services.
Setup Wizard stopped several times after reboot, worked around it by restarting the phone. Mobile connection was unstable for both sims and kept dropping, overall performance was slow, especially when in Settings. Not sure if RAM on this phones can be upgraded, mentioning it since free memory was scarce.
As noted by another user WIFI setup had to be repeated for it to stick, good work for keeping it simple thu.
c0mpus3rvef said:
Thanks for posting this ROM, gave me a chance to test in on a SM-J100H with dual sims: flashed the ROM, the fix and then gapps. Was thinking not to have gapps but an app was requiring Google Play services.
Setup Wizard stopped several times after reboot, worked around it by restarting the phone. Mobile connection was unstable for both sims and kept dropping, overall performance was slow, especially when in Settings. Not sure if RAM on this phones can be upgraded, mentioning it since free memory was scarce.
As noted by another user WIFI setup had to be repeated for it to stick, good work for keeping it simple thu.
Click to expand...
Click to collapse
yeah i think ram 512 for now is not good especially with gapps that are constantly updating, i think you should buy a new handphone
Let's go join to Redmi 5A
Erwin Abs said:
yeah i think ram 512 for now is not good especially with gapps that are constantly updating, i think you should buy a new handphone
Let's go join to Redmi 5A
Click to expand...
Click to collapse
Totally agreed, it has limitations due to small RAM and older technology. am using my SM-J100H learning about behavior of various custom ROMs. Please bear with me, one observation when using Bluetooth, it said SM-G360H, perhaps not significant. was able to transfer files and use an app that required Bluetooth connection. Just curious if this could cause slow response time. Thanks again.
c0mpus3rvef said:
Totally agreed, it has limitations due to small RAM and older technology. am using my SM-J100H learning about behavior of various custom ROMs. Please bear with me, one observation when using Bluetooth, it said SM-G360H, perhaps not significant. was able to transfer files and use an app that required Bluetooth connection. Just curious if this could cause slow response time. Thanks again.
Click to expand...
Click to collapse
Will it work with the Sm-j100FN?
ugur30 said:
Will it work with the Sm-j100FN?
Click to expand...
Click to collapse
totally different hardware so NOPE
Donwload
Erwin Abs said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (LP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
BEFORE INSTALLING THIS ROM, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE
IF YOU ASK ANY QUESTIONS LIKE "IS THIS FOR MODEL BLABLABLA" THEY WILL BE ALL IGNORGED
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
We'll not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our intructions word by word
are unfriendly
And most important: DON'T READ THE OP
What's working:
Wifi (connection, tethering, etc)
Bluetooth (need quick patches in download link)
Camera, video codecs
RIL (Calls, SMS, mobile data)
Storage (both internal and external)
MTP storage (both internal and external)
Offline charging
zRAM (compressed-RAM swap)
GAPPS
Tethering (USB, Wifi, Bluetooth)
GPS
Sound recording
Torch (flashlight)
BUGS/Not working:
Laggy recorded videos. In this case, use MX Player, choose SW codecs when you play these videos, they will become normal
Switching to other fonts will get bootloops after restart. In this case, if you use TWRP recovery, go to File Manager >> delete "themes" from /data/system would help you escape this without factory reset
First time installing CyanogenMod 12.1 to your Galaxy , or coming from another ROM:
Install TWRP Recovery
Reboot into Recovery using 3-button-combo (Vol-up+Home+Power)
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)*
Install the ROM from sdcard using TWRP Recovery
Optionally install the Google Apps ( get it here: https://opengapps.org ) (pico GAPPS recommended)
Quote:
DOWNLOADS:
ROM: Link
CHANGELOG
Code:
- 2016/06/25
+ Initial release, ported from Galaxy V's CM12.1
- 2016/06/27
+ Switched to built-from-source, no more portings
+ Fixed nearly all problem, except fonts
+ Underclocked to 1,2GHz for stable usage
+ Enable multi-threaded dex2oat >> Faster app installation
+ Fixed installation for some apps (FB, etc...)
Want some screenies? Get them from Screenshot tab
XDAevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy
Contributors
Erwin Abs
Source Code: https://github.com/jnkcode/android_kernel_samsung_j13g/tree/cm-12.1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 4.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 2
Stable Release Date: 2016-06-27
Click to expand...
Click to collapse
A Bugs / Or My phone?
Device : J100H
Bugs (maybe) : Cant Connect To A Wifi (It Saying Cant Connect On This Network)
I Dont Know Its My Phone Or The ROM Sooo? Help
1.Thank You For The Information
2. I Already Know It,After Installing Lineage OS 14.1 (Nougat,Still Didn't Know IS THe ROM Ported Or Not But THe Wifi Works So I Used It (And Installing Family Link Bc That Phone I Will GIve It To My Lil Bro)
3.It Slow af
Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 15.1 for the ZTE Blade S6 aka P839f30.
This is the first beta release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable nano).
Please check this prop!
Click to expand...
Click to collapse
Changelog:
16.10.2019 - 2nd stable release:
los security patch level 05.10.
merge upstream kernel from oppo devices
kernel version 3.10.108
30.08.2019 - 1st stable release:
los security patch level 05.08.
use sdcard fs now
updated fs drivers
updated wifi driver
fix line-out, you can use it now
use deep-buffer for audio playback
23.12.2018 - 2nd beta release:
los security patch level 05.12.
cpu min freq. 200MHz, min cpu 0
correct modem and wcnss symlinks.
11.12.2018 - first beta release:
los security patch level 05.11.
standard features working.
Click to expand...
Click to collapse
Downloads
second stable release - 16.10.2019:
Google Drive or here.
first stable release - 30.08.2019:
Google Drive or here.
second beta release - 23.12.2018:
Google Drive or here.
first beta release - 11.12.2018:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: There is no weather provider available to download for los-15.1 - what to do now?
A: Search for it here on xda or see this post or use this download link.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
XDA:DevDB Information
Unofficial LineageOS 15.1 [OPM7.181205.001] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS 15.1
Version Information
Status: Stable
Current Stable Version: OPM7.181205.001
Stable Release Date: 2019-08-30
Current Beta Version: OPM7.181205.001
Beta Release Date: 2018-12-23
Created 2018-12-11
Last Updated 2019-10-16
The end of the year is coming and some will have a christmas feast before. So this is a small christmas gift for you - LineageOS 15.1 aka Oreo for our phone. Have fun with it.
In my opinion it is better than nougat.
Thanks!!!
Tested and no issues found
Great Rom:good:
Files error
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
Check if your build.prop has "ro.sys.sdcardfs=false" or check with terminal or adb shell:
Code:
getprop ro.sys.sdcardfs
it has to be false.
I have read about some problems with that and found it not to be working at the moment, so I disabled it.
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
It´s true, with other file manager different from the stock (Root explorer / ES Explorer) I cann't see the files in storage.
lightwars said:
Check if your build.prop has "ro.sys.sdcardfs=false"
Click to expand...
Click to collapse
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
d.alvick said:
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
Click to expand...
Click to collapse
Great that it could be resolved so fast. I will check, why the prop got not in or overwritten. For the second thing: I didn't know that, this is an android oreo thing?
lightwars said:
this is an android oreo thing?
Click to expand...
Click to collapse
Very similar error was in old LineageOS or miui builds for our device or in both of them, I don't quite remember. Tried it again just now, playback is fine... Maybe it depends on device's mood or smth with charging, but I can't repeat it
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
d.alvick said:
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
Click to expand...
Click to collapse
These are no bugs! There wont be an impact in performance. Go and look for a device tree which defines msm8939... The platforms msm8ôô916 and msm8939 aren't that different. Even qualcomm defines the values like this, have a look at the CAF. Some vendors habe a common device tree for both platforms, for example asus.
And the last thing the Hardware is 64bit, but the Software is 32bit,changing to armeabi-v8 will not make the Software be 64bit.
Works great so far. Thank you
PS: could unbrick my phone
Update in the OP. new beta release.
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
d.alvick said:
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
Click to expand...
Click to collapse
I try to answer your question, but I haven't any insight views or infos, should I could be barely wrong... Over time GApps have gotten more permissions ands task and also more GApps have been published. I think at first there was the syncing of contacts, calendar and sorts of thinks, than the geolocation services. Now we have backups or storage expansion through GApps and also tracking of your fitness, reading out sensor data of your phone. And maybe other sorts of thing, which should make your experience with a smartphone better, but also consums energy.
To emphasizes your feelings about GApps I attach a screenshot of my phone, you can see how often the google service triggers and alarm or wakeup in a span of some hours, roughly speaken every minute.
I stumbled across LKT, which should give you more screen on time. I have used it, but found mixed results. I also think that the battery optimization of 15.1 needs some time, but I could be also wrong.
At the moment I use the naptime app to get more usage, I'm afraid to say this will only help your device last longer, when not used in my opinion.
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
MouZ124 said:
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
Click to expand...
Click to collapse
Hi,
have you run the factory reset command from within the android settings menu?
So the device only boots the recovery, even if you select to start the system within TWRP, right?
In the TWRP terminal or from the adb shell with su permission you can try to reset all flags in the misc partition like so:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
You can also back the partition beforehand to be sure, nothing breaks.
Hello lightwars,
thank you for your answer
lightwars said:
have you run the factory reset command from within the android settings menu?
Click to expand...
Click to collapse
No, the Device starts automatically into TWRP after Lineage OS 15.1 has the Boot-Loop
lightwars said:
So the device only boots the recovery, even if you select to start the system within TWRP, right?
Click to expand...
Click to collapse
Yes, i can select Reboot - System, then i see the ZTE-Logo with vibration and then start the TWRP short after this Logo...
If i tipped this Command in the TWRP terminal it shows an Error:
Code:
dd: can't open '/sys/block/bootdevice/by-name/misc' : No such file or directory
I try to go back to the old Partition-Layout and try to flash CM12.1, stock-rom B15 (modifide for TWRP), LineageOS 15... nothing works
I try TWRP 3.0.2 and TWRP 3.2.3
I try to flash CM12.1 with other Kernels with is Modified for CM12.1 from the other thread but it fails too...
What else could I do?
Screen if i install a zip
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
MouZ124 said:
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
Click to expand...
Click to collapse
Sorry, my bad. It is not in sys, it is dev so this is the correct command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
6. Uncheck Update Lineage Recovery alongside the OS option during start wizard
Work
Almost all
Known Issues
video recording
Links
3. 20210509: may security patch: https://drive.google.com/file/d/1qYWhEj4L1XidBnasg0ug00fsquV0smjD/view?usp=sharing
2. 20210430: april security patch: https://drive.google.com/file/d/1N5IgMEqjezZIxkfntKY6EydGRbRV7a7Q/view?usp=sharing
1. 20201224: initial technical build: https://drive.google.com/file/d/1uKoPL8nBlYQumNKjxwyH795eotDeGC5j/view?usp=sharing
Gapps
opengapps: https://sourceforge.net/projects/opengapps/files/arm/test/20210130/
BiTGApps: https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/
P.s. for BiTGApps: Chrome workaround with gapps: Chrome should be a part of system app in Android R (11) but we install it as user app, which break sign-in and sync in chrome. To fix this, allow contacts permission for chrome. Restart chrome and you can add your google account.
Root
Install latest magisk (21.1+) from canary channel: https://github.com/topjohnwu/Magisk/releases/tag/v21.1
Recovery
this is my build, the error with the screen off is still present, but I added an option for twrp with unlimited screen timeout, as a result, the screen does not automatically turn off.
for recovery: https://drive.google.com/file/d/1UeC4LwVEA6d46y0UPpuuipHbcjAtAo0Q/view?usp=sharing
for odin: https://drive.google.com/file/d/1WmAzhWkq9l_3d4m3Ft1xmihZaYfccUym/view?usp=sharing
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_picassolte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_picassolte
Thank you for your hard work !
Unfortunately too laggy for daily use... I have to stay with 17.1 ver....
Salut
Pour ma part je l'ai testé et effectivement elle est lente. 10 fois meilleurs est la ColtOs 6.5 dans ces 2 tests
Mais peut être que je m'y suis mal pris avec cette rom
Hi
For my part, I tested it and indeed it is slow. 10 times better is the ColtOs 6.5 in these 2 tests
But maybe I did it wrong with this rom
I updated to the 20210430 version from 17.1 doing a full wipe (including internal storage). Everything seems to be working at least as well as with 17.1. TWRP-3.3.1 still bootloops but 3.2.2 got the job done.
I installed the latest core BitGapps but got "No space left on device" error when trying to install the addon package. Netflix and Disney+ sideloaded nicely and so far I haven't encountered any issues with my daily apps. Will keep you posted if something weird occurs. Note though, that I'm not using Phone, Mobile Data, BlueTooth or Camera.
Huge thanks to @Valera1978 for keeping our device alive!
Two minor issues I've found in 20210509:
If I try to access settings through the status bar by sweeping down twice and hitting the cogwheel, System UI restarts.
Reddit app doesn't respect screen orientation. If I set the screen to portrait so that the USB connector points to the right, the app starts upside-down. No setting makes it reverse that. In 17.1 I could use it in either portrait orientation.
works well for me for now, thank you for your work dev.
how to turn on the backlight of the touch buttons?
Since the SM-T525 is basically the SM-T520 with LTE, is it possible to just install this on the SM-T520?
Edit: nevermind, found the answer here.
L1feGuard said:
how to turn on the backlight of the touch buttons?
Click to expand...
Click to collapse
I don't think you can. They used to work in 17.1 but not in this one so the developer needs to make some (kernel config?) modifications to make it happen in future versions.
All works well, but the current build contains a very nasty bug that might corrupt your SD-Card during heavy write activity. The only fix (if you're lucky) is to connect it to a Windows machine via TWRP and repair it there. It's been fixed some time ago, so is there any chance we could get an up-to-date build?
Many regards,
Zy.
Just a fair warning for anyone using BitGapps. Any version beyond R29 will set your SELinux status to permissive.
Description for a fix can be found here.
Regards,
Zy.
Flashing the May Package with OpenGapps Nano, Magisk 21.1 with the linked twrp didn't work for me.
Even though i wiped cache before the install, i don't get past the lineage boot animation after 30m.
Hello. Wich TWRP Version is needed to flash LOS 18.1 to T525 ? My Problem, i found only an older TWRP 3.0.2.0 well working Version but this carnt flash newer LOS. I get Error 7. Newer TWRPs like 3.2.2.0 makes a restart, if i select an Feature. Can anyone make an easy unterstand way ?
The 3.2.2 version found in the LineageOS 16.0 for T525 thread worked for me. Anything newer caused a boot loop.
I used it to flash 16.0, 17.1 and 18.1.
Thanks, and wich Gapps Version i need ? Wheres ARM ARM64 x86 and x86_64 available.
Thank you. I sucessfully installed lineageos 16 and gapps arm 9.0 pico and first time it looks good running. my problem was the to old twrp version
Now i found 2 Prolems. First is that i see no more the ChargeIcon (Batterie Icon with green load state) if Tab is shutoff but it charge. And Second if i start booting i get a yellow Erro Message Set Warranty Bit Kernel. What could be reason and should i flash 18.1 better ?
@FrankLinke
The yellow message is normal, you have flashed a custumrom and a New Kernel.
The missing charging icon is a bug, it was also on other device with LOS 18.x
I think with the next Version it will be fixed.
Ok thanks, so i can wait till newer fixed lineageos comes, because 16 runs well.
Hi
Finally got it working. As an absolute noob in this matter it took me a while (2 days) but finally my brief log for those who may still have issues.
TWRP throught Odin - Odin version has no relevance - I could patch TWRP with any, most important is to rename TWRP .img from a specific name to recovery.img and tar with 7zip (for example).
TWRP 3.2.2 only - other versions failed for me, however even with 3.2.2 it was quite an effort.
I patched it with all three versions of LineageOS 18.1 , one after the other but keep touching the screen to avoid get it blank. After 1st time I got this , patching resulted in a bootloop.
Then google apps - I got the micro version - mini was too big.
Now it works , I think it is at least as fast as before or even better but keep in mind I had veeery old 4.2.2 and the apps from the stone age as well - so it could be the issue.
Currently the only issue I have is the netflix app, it says it is not compatiblewith the device - I cant view it also in the web browser. Before that the app was working well on 4.2.2 (installed from the apk for incompatible ones).
I'd like to thank Valera1978 for this effort - as well as the other people who are involved in this work. THANKS!
Code:
/* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is AOSP?
AOSP (Android Open Source Project) is Android just as Google publishes, without any other modifications or additions. More or less AOSP is the Pixel devices stock ROM without gapps and proprietary additions. Check out the screenshots to know more!
What's working?
Boots
RIL (Calls, SMS)
Mobile data
Bluetooth
WiFi/hotspot
Media (audio/video)
Camera
Camcorder
GPS
Fingerprint
NFC
Sensors
etc.
Bugs?
BT CALLS/voWiFi/voLTE
How to install?
Wipe system, data, dalvik's cache and cache Do not wipe vendor
TWRP:Install > select Image > select if they ask "system" select System and then the AOSP_A40......Image > install
Ofox: Tap on the Image > As system image
Reboot recovery
Flash Gapps
reboot system
Enjoy the goodness of Android 11.
Downloads
ROM: AOSP_VANILLA_STOCK_A40_R [Systemimage only]
Screenshots
Attachment
Sources
https://github.com/aosp-mirror
NOTE: For reporting any bugs, describe the issue properly and make sure to accompany it with a logcat. Without a logcat, bugs cannot and will not be fixed.
Don't forget to hit the thanks button to show love and support my work.
XDAevDB Information
AOSP 11.0, ROM for the Samsung Galaxy A40
Contributors
Kevios12
Source Code: Kernel Tree
ROM OS Version: 11.0.0
ROM Kernel: Linux 4.x
ROM Firmware Required: OneUI 2.0 or ALT+F4
Based On: AOSP
Version Information
Status: Stable
Created 2021-04-30
Last Updated xxxx-xx-xx
(Based On: AOSP) Roms unfortunately do not have the option to make sim2 passive while sim1 is active (or vice versa). Is there a solution to this?
I have installed the ROM with TWRP and my phone is now bricked, I cannot even get into TWRP anymore. Any idea what I could do now?
- Install order was: Unlocked bootloader, used Odin to install TWRP, flashed Multidisabler, reboot, then followed the instructions here
- Black screen followed the "reboot" button in TWRP
- I can reboot the phone by pressing all three buttons but this will only give me the Samsung warning I have to confirm and then black screen again
- this phone uses Exynos CPUs
- OneUI 3.1 was installed before. Is that the issue? I read "Firmware required" as "Minimum Firmware required"...
Edit: I can NOT reboot the phone while a USB cable is plugged in.
Yes OneUI 2.0 is required. OneUI3 FW is GAY! And you can go instand to twrp by pressing power + vol - then if restart hold power+vol+ if samsung logo come, release powerbutton and wait. Have u the A40 for sure? the rom is testet and works, nobody has a brick or whatever. Flash This image as system_image only no wipe vendor or everything btw. look in other treads for my custom vendor it will works.
kevios12 said:
Yes OneUI 2.0 is required. OneUI3 FW is GAY!
Click to expand...
Click to collapse
So I managed to flash OneUI 2.0 and then repeated the whole process and now your ROM boots. I can't connect to WIFI though (yes I made sure I used the correct password). It just says "connecting failed". Also, when I call someone, there is no call window. Is this ROM compatible with FlameGApps?
Also, yes, definitely the A40.
only u can Try gapps idk if flame works. did u use WPA2/3? combinied
My router uses WPA2/3 combined and Android does not give me an option.
I was now able to connect to another Wifi and tried to update my apps. It tells me I had not enough space. But I have over 50 GB free.
Edit: So, the Wifi problem depends on encryption. WPA+WPA2 works, WPA2+WPA3 does not work. I think that is a bug.
Also, I cannot get Play Store to install anything. It always complains about not enough space despite me having no apps installed and lots of free space on both internal and external memory. Cleaning cache did not help. This happens with both NikGapps and FlameGApps. FlameGApps works way better though.
Also explaine better, it should work maybe bug of gapps
I tried the rom , but it’s stuck on the android logo , any help?
Have u installed vendor? ... the custom one
kevios12 said:
Also explaine better, it should work maybe bug of gapps
Click to expand...
Click to collapse
Possible, but I do not know. Might also be partitioning. I did nothing but flash ROM and flash Gapps, then boot and run through the Gapps initial setup tool that automatically started (connect wifi etc). Then I tried to install any app from the Play Store. It always says I need to free up space before I can install an app. But I have lots of space, tens of GB.
hmm thats weird
It is weird indeed... also, are there known issues with phone calls with a Bluetooth headset? I couldn't use mine today, even though it was properly connected.
kevios12 said:
Have u installed vendor? ... the custom one
Click to expand...
Click to collapse
I did
CozmoGM said:
I did
Click to expand...
Click to collapse
Nevermind , i think i did something wrong , but i reflashed the rom and everything and now it works.
Konzertheld said:
It is weird indeed... also, are there known issues with phone calls with a Bluetooth headset? I couldn't use mine today, even though it was properly connected.
Click to expand...
Click to collapse
known bug, like voLTE/voWIFI/BT CALLS BUG/EXYNOS WONT WORK
kevios12 said:
known bug
Click to expand...
Click to collapse
So... please put that in your description above instead of stating "bugs: none". Other ROMs named the bug with Bluetooth etc and yours didn't, so I assumed it was not relevant. I would not have downloaded it if I knew.
Konzertheld said:
So... please put that in your description above instead of stating "bugs: none". Other ROMs named the bug with Bluetooth etc and yours didn't, so I assumed it was not relevant. I would not have downloaded it if I knew.
Click to expand...
Click to collapse
Well the problem is when you are developer & tester at the same time, because nobody feels like doing it, or you really do everything alone ... mistakes can happen!