[ROM][OFFICIAL][7.1] CyanogenMod 14.1 Nightlies for i9300 - Galaxy S III Original Android Development

[ROM][OFFICIAL][7.1] CyanogenMod 14.1 Nightlies for i9300 - Galaxy S III Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is not 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review.
Wiki
Official CyanogenMod Wiki: https://wiki.cyanogenmod.org/w/i9300_Info
Installation
(NOTE: if you experience robotic voice during calls: see the FAQ for a fix)
First time CyanogenMod 14.1 installation on your Galaxy S III:
Read the official Wiki page
Flash a custom recovery via Heimdall or Odin
Push GApps (arm) and the CM 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the CM 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of CyanogenMod (even from 13.0) :
Update your recovery - CM Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 to automatically install updates in CM14.1)
Push the new CM 14.1 zip to your SD card
Boot into Recovery
Flash the CM 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Lastest Nightly : http://get.cm/get/i9300-latest.zip
Lastest Recovery (Nightly) : http://get.cm/get/i9300-latest-recovery.img (or TWRP)
Lastest Snapshot : http://get.cm/get/i9300-snapshot.zip
Lastest Recovery (Snapshot) : http://get.cm/get/i9300-snapshot-recovery.img (or TWRP)
Unofficial Changelog
-----------------------------------------------------------------------------
Google Apps (arm): wiki.cyanogenmod.org/w/gapps
All the builds: http://download.cyanogenmod.org/?device=i9300
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* CM version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
(see next post)
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Official CyanogenMod 14.1 Nightlies, ROM for the Samsung Galaxy S III I9300
Contributors
forkbomb444, Nameless, Haxynox, JustArchi
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2015-12-17
Last Updated 2016-12-25

FAQ
Robotic voice during calls?
Make sure you're on the I9300XXUGMK6 modem. Instructions are here
Root?
CM ships with root, enable developer options and look in Settings -> Developer options -> root access
Google camera crashes?
Use Google Camera from the play store, not from gapps
There's a non-device related bug? - such as SystemUI crashes triggered by performing a certain action, stray settings entries, theme crashes, translation, etc.
I just work on the device support - not something I'll fix.
Something that worked in the last nightly doesn't work in the new nightly? - bootloops? Something new is broken? It can all go here.
Quick, to the bug tracker!
Some other issue?
You can't just say 'x is broken!' and expect me to magically find the bug and fix it.
Here's what I need:
Steps to reproduce - I don't care if "it's simple". I want to know exactly what you were doing at the time of the bug. How'd it happen? Does it only happen on Tuesdays when watching a specific YouTube video? Include it *all*
What happened - in what way is this *not* the expected behaviour? Don't just say "it didn't play/upload/whatever". Did the entire phone crash? Did it show an error? Did it just show an endless progress indicator? Again, I need specifics here.
Logcat/last_kmsg - Include the whole thing please, and if your phone's been running for a while, give me a rough region of time when the issue happened. Use last_kmsg if your device reboots unexpectedly, otherwise use a logcat. (See below for info on how to get them)
How to logcat?
See here (read up to the end of the "logcat" section).
Upload it to a pastebin, include the link in your bug report.
or if you're on your phone and can't get to a computer:
Sigi_cz said:
I'd like to provide logs for problems I'm reporting, but I can't sit by my computer all the time ...
Click to expand...
Click to collapse
If you install a terminal (this one works nicely) and type this:
Code:
su
then, accept the superuser prompt, and type
Code:
logcat -d > /sdcard/logcat.txt
it should save a logcat at /sdcard/logcat.txt. You can change the filename, and it will overwrite whatever exists already at /sdcard/logcat.txt
How to get last_kmsg?
Copy /proc/last_kmsg and upload the file contents to a pastebin, include the link to that in your bug report

You're awesome! Just wanted to be the first to let you know.

Congratulations simon
From nothing be all thing :thumbup:
Inyonge Ngepos Kang GT I9300, Maen Bet Kie..

No need Flash CM12 first?

Android-Banjarmasin said:
No need Flash CM12 first?
Click to expand...
Click to collapse
no clean flash is ok

Android-Banjarmasin said:
No need Flash CM12 first?
Click to expand...
Click to collapse
Direct clean flash is recommended... Screen flicker can be fix by turning off ambient display... All good to go

You are awesome

DrmohamedShawky said:
no clean flash is ok
Click to expand...
Click to collapse
haha I mean. this no need dirty flash from CM12?

Just flashed 1st nightly build.
I think there are something wrong with graphic,
Sometimes screen blinking happen here and there.
But,,,overall.
nice !!!
Finally first official nightly build released.
Thanks @forkbomb444

bandari solomon said:
Direct clean flash is recommended... Screen flicker can be fix by turning off ambient display... All good to go
Click to expand...
Click to collapse
The question is this need dirty flash from CM12 or not, can it boot without flashing CM12 first?

Thank you for bringing marshmallow sweetness on out beloved s3.

Nice move
Man. You are great.

Dirty flashed via CM Updater in Settings with no Problem! Thank you so much for the hard work on our aged S3?? Keep up the great work.

Android-Banjarmasin said:
The question is this need dirty flash from CM12 or not, can it boot without flashing CM12 first?
Click to expand...
Click to collapse
No need to dirty flash... It boots up without CM12.... I'm on CM13 nightly now

bandari solomon said:
Direct clean flash is recommended... Screen flicker can be fix by turning off ambient display... All good to go
Click to expand...
Click to collapse
Thanks for info,
I will turn off ambient display, and lets see whats happen

Android-Banjarmasin said:
haha I mean. this no need dirty flash from CM12?
Click to expand...
Click to collapse
i figured out that i should say yes, no need after posting

Great ROM!
Smooth and stable.

tokict said:
Just flashed 1st nightly build.
I think there are something wrong with graphic,
Sometimes screen blinking happen here and there.
But,,,overall.
nice !!!
Finally first official nightly build released.
Thanks @forkbomb444
Click to expand...
Click to collapse
Turning off ambient display should fix it (might have to reboot).

Screen Flickering is still here after disabling ambient display

Related

[ROM] [6.0.1] [MARSHMALLOW] CyanogenMod 13 for Nexus 9 LTE

About encryption
As you should've already guessed, CyanogenMod 13 will always (re)encrypt your /data partition on first boot unless you flash another kernel with encryption disabled.

Bug reports
Bug reports while using custom kernels, mods (like Xposed) and whatsoever will be ignored.
When reporting a bug don't forget to mention the version you're using (eg.: cm-13.0-20151218-NIGHTLY-flounder_lte), what steps do you need to do to reproduce the problem, what's happening and what it should be happening instead.
Attaching a logcat won't hurt you.

Just one bug I found...using 12-20 nightly and flashed systemless root, arm64 stock gapps. Selecting the "sounds" menu in settings causes an immediate crash of settings. Happens every time. Happened immediately from a fresh, clean flash, and after a reboot, and after a factory reset and reflash. Also happened with elementalx kernel. Tried getting a logcat but I can't get any logcat app to run properly for some reason (might be another bug but could just be me lol).
Everything else seems to work fine for me. Much better than stock so far in my opinion.
Sent from my Nexus 6 using Tapatalk

ss12108 said:
Just one bug I found...using 12-20 nightly and flashed systemless root, arm64 stock gapps. Selecting the "sounds" menu in settings causes an immediate crash of settings. Happens every time. Happened immediately from a fresh, clean flash, and after a reboot, and after a factory reset and reflash. Also happened with elementalx kernel. Tried getting a logcat but I can't get any logcat app to run properly for some reason (might be another bug but could just be me lol).
Everything else seems to work fine for me. Much better than stock so far in my opinion.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Heys!
I don't want to be rude... but:
lcrponte said:
Bug reports
Bug reports while using custom kernels, mods (like Xposed) and whatsoever will be ignored.
When reporting a bug don't forget to mention the version you're using (eg.: cm-13.0-20151218-NIGHTLY-flounder_lte), what steps do you need to do to reproduce the problem, what's happening and what it should be happening instead.
Attaching a logcat won't hurt you.
Click to expand...
Click to collapse
But even that (systemless root), shouldn't justify the issue. logcat would be appreciated.
@lcrponte is using the builtin root access and doesn't have that issue, can you confirm that, if you don't flash chainfire's systemless root, it crashs the same?

sheffzor said:
Heys!
I don't want to be rude... but:
But even that (systemless root), shouldn't justify the issue. logcat would be appreciated.
@lcrponte is using the builtin root access and doesn't have that issue, can you confirm that, if you don't flash chainfire's systemless root, it crashs the same?
Click to expand...
Click to collapse
You aren't being rude. I read the OP...I should have mentioned I did get the bug without systemless root installed. I actually couldn't get root access on anything until I went back into recovery and flashed supersu. As a matter of fact, no logcat apps could gain root to generate a log for the bug, which is why I flashed it in the first place.
If I were able to get a log I would, but without supersu the log apps couldn't get root, and with supersu the log apps just weren't logging anything...at all, not just errors.
Not a big deal to me anyway just figured I'd try to contribute...when I get to work I'll see if I can grab a log from the computer.
Sent from my Nexus 6 using Tapatalk

Let me know if this log helps - https://www.dropbox.com/s/6tkzx629re5uklz/LogCat_Filtered_Error_12-21-2015_13-06.txt?dl=0
I can't revert back from elementalx at the moment because I don't want my data to encrypt...if you need me to I will make a backup and do so later tonight.
Sent from my Nexus 6 using Tapatalk

ss12108 said:
Just one bug I found...using 12-20 nightly and flashed systemless root, arm64 stock gapps. Selecting the "sounds" menu in settings causes an immediate crash of settings. Happens every time. Happened immediately from a fresh, clean flash, and after a reboot, and after a factory reset and reflash. Also happened with elementalx kernel. Tried getting a logcat but I can't get any logcat app to run properly for some reason (might be another bug but could just be me lol).
Everything else seems to work fine for me. Much better than stock so far in my opinion.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This started with 12-19 nightly for me. The 18th build is fine.

briand.mooreg said:
This started with 12-19 nightly for me. The 18th build is fine.
Click to expand...
Click to collapse
Ok good I'm not alone haha.
Sent from my Nexus 6 using Tapatalk

briand.mooreg said:
This started with 12-19 nightly for me. The 18th build is fine.
Click to expand...
Click to collapse
so should we revert to the 18th build? i just installed today as well (latest build) and i'm experiencing the same exact issue.

clamder said:
so should we revert to the 18th build? i just installed today as well (latest build) and i'm experiencing the same exact issue.
Click to expand...
Click to collapse
If sound setup is important to your N9, then I would, I did. Other than the FC though, everything else ran fine.

It's not related to any kind of "root" access. It's a CM-wide bug meaning that you could revert to your last backup or wait for it get fixed.

Flashed 12/24 nightly and the sound settings crash is fixed for me.
Sent from my Nexus 9 using Tapatalk

LTE does not work with CyanogenMod 13 on my device

This is probably a dumb question, but what gapps should I use? The OpenGapps project, which is recommended by Cyanogenmod, does not have 6.0.1 gapps, so I'm kind of lost.

Weird. I tried to use the nano package of that 6.0.X version, but for some reason, I got an error, hence my question.
I'll give it another try, maybe I made some kind of mistake.

thechicgeak said:
LTE does not work with CyanogenMod 13 on my device
Click to expand...
Click to collapse
User problem, not a ROM problem. Flash latest img and repeat the steps on the installation instructions.

imcass said:
Weird. I tried to use the nano package of that 6.0.X version, but for some reason, I got an error, hence my question.
I'll give it another try, maybe I made some kind of mistake.
Click to expand...
Click to collapse
I use the nano, without problems. Make sure you download the 64 bit gapps.

Get rid of corrupted device warning?
Has anyone figured out a way to run this ROM (or any custom ROM) without the nasty "Your device is corrupt ...." (and Santa Claus won't bring you any presents) warning on every boot?
(I feel like this must be an FAQ, but I can't find it in this thread or the CM 12.1 thread, so ...)

ipilcher said:
Has anyone figured out a way to run this ROM (or any custom ROM) without the nasty "Your device is corrupt ...." (and Santa Claus won't bring you any presents) warning on every boot?
(I feel like this must be an FAQ, but I can't find it in this thread or the CM 12.1 thread, so ...)
Click to expand...
Click to collapse
I don't get that message, but I don't know what I did that is different. Elementalx kernel maybe?
Sent from my Nexus 6 using Tapatalk

[OFFICIAL] LineageOS 14.1 - Nexus 7 2013 nightlies for flo

On my 32GB Flo the System partition is 840MB, clean flashing the latest CM14.1 Nightly + Nano Gapps uses about 800MB, so all we have left on the System partition is about 40MB! Now I'm wondering if we will have enough space for CM as it grows over time...
Partial log from Open Gapps Stock:
Total System Size (KB) | 847,656
Used System Space (KB) | 805,700
Current Free Space (KB) | 41,956
Additional Space Required (KB) | 426,668

18.11 nightly does not boot for me. Twrp says that flash is successful. I am coming from 17.11 nightly (I have 90 mb free on my system partition). Some users are experiencing the same issue over at the bacon forums, however my one plus one is fine on the 18.11.
The 15mb increase might be the issue?

Pezmet said:
18.11 nightly does not boot for me. Twrp says that flash is successful. I am coming from 17.11 nightly (I have 90 mb free on my system partition). Some users are experiencing the same issue over at the bacon forums, however my one plus one is fine on the 18.11.
The 15mb increase might be the issue?
Click to expand...
Click to collapse
It does seem to be somewhat buggier than the previous build, it did boot for me, and tried it without any gapps, Gello Browser would crash, tried Pico and Delta Gapps Base, both would not connect to a Google Account, Play Store would crash (those gapps worked fine on other builds). I'm back to factory stock for now. But yes, stick to Nov 17 for now.

Setting long press of the home button to launch search assistant does not work. Trying to get assistant working using the build.prop tweaks. Assistant shows in the google app, I just can't launch it. Also very flaky OK google voice detection.

What if any custom kernels are available for 14.1 and the Nexus 7 Flo? I have a pretty healthy overclock on mine, and would to keep it.

Pezmet said:
18.11 nightly does not boot for me. Twrp says that flash is successful. I am coming from 17.11 nightly
Click to expand...
Click to collapse
+1

Very nice! Using 11-17 currently.
Reposting my bugs from the old unofficial discussion thread:
osm0sis said:
Running decently!
Still the usual Nougat bug of Developer Options crash though. I also noticed the Live display interface doesn't do anything, and neither does the battery status icon choices for anything but portrait or text.
Click to expand...
Click to collapse
osm0sis said:
Maybe Developer Options only crashes when installed as MultiROM?
To avoid the log[] errors when installing, or install a Nougat ROM in MultiROM you just need a newer recovery.
Latest is here:
https://basketbuild.com/devs/Captain_Throwback/Nexus 7 2013/MultiROM
Click to expand...
Click to collapse
osm0sis said:
Noticed it didn't want to restore my Google device backup during the setup process (Google Play services kept crashing from a NPE ), so I did it manually:
Code:
bmgr list sets;
bmgr restore 1234567890abcdef
(substitute 1234567890abcdef with the code for the backup you want)
I also noticed "ringer" is showing in the volume panel, which it shouldn't, but despite editing the build.prop with the values:
ro.carrier=wifi-only
ro.telephony.default_network=9
-it still shows. Oh well. Minor bug. I'm sure they'll get to it.
Click to expand...
Click to collapse
Should be easily reproducible. I'll happily produce some logs if needed.

Nov. 19 Nightly Build:
Clean flashed with TWRP 3.0.2-0, CM and Open Gapps Nano, no problems during flashing. Booted just fine, Google Setup went normal, signed in to Google Account, Gello Browser and Play Store are not crashing. Only had a few minutes with it so far, but seems good to go!
Stay safe, use Pico!
Apps from the Play Store will be installed to the Data Partition.
Still getting CM Bug Report Stopped...

Gus Ghanem said:
Nov. 19 Nightly Build:
Clean flashed with TWRP 3.0.2-0, CM and Open Gapps Nano, no problems during flashing. Booted just fine, Google Setup went normal, signed in to Google Account, Gello Browser and Play Store are not crashing. Only had a few minutes with it so far, but seems good to go!
Stay safe, use Pico!
Apps from the Play Store will be installed to the Data Partition.
Still getting CM Bug Report Stopped...
Click to expand...
Click to collapse
Can you please confirm if night mode is available and working? It's a deal breaker for me! Thanks

utfluc said:
Can you please confirm if night mode is available and working? It's a deal breaker for me! Thanks
Click to expand...
Click to collapse
I've never used it, but if you mean under:
Settings > Display > LiveDisplay > Display mode > Night
Then no, it doesn't look like any color related settings are working. I tried all settings, a dark room, nothing, only Adaptive Brightness and Invert colors work.

I'm getting rotation stuck in portrait, a reboot didn't even resolve it. That's a deal breaker for me.
Nothing shows up in the logcat when attempting to rotate.
Edit: Disregard, happens on stock now too..

osm0sis said:
I'm getting rotation stuck in portrait, a reboot didn't even resolve it.
Click to expand...
Click to collapse
I just tried Home Screen rotation a few times, no problem. Trebuchet Allow Rotation enabled, Quick Settings on AutoRotation. Try clearing launcher data.

Does 11/19 nightly solve bootloop issue from 11/18 nightly?

MWFD said:
Does 11/19 nightly solve bootloop issue from 11/18 nightly?
Click to expand...
Click to collapse
Yes, but you should clean flash, and Nano maximum, Pico probably safer.

Gus Ghanem said:
Yes, but you should clean flash, and Nano maximum, Pico probably safer.
Click to expand...
Click to collapse
Clean flash from 11/15 nightly? Trying not to lose data everytime I flash a nightly.

MWFD said:
Clean flash from 11/15 nightly? Trying not to lose data everytime I flash a nightly.
Click to expand...
Click to collapse
If you're on Nov. 15 then try a dirty flash first.

Gus Ghanem said:
I just tried Home Screen rotation a few times, no problem. Trebuchet Allow Rotation enabled, Quick Settings on AutoRotation. Try clearing launcher data.
Click to expand...
Click to collapse
Disregard that bug report. I booted back to Marshmallow and it still doesn't work. Guess there's something up with my accelerometer. First sign my N7 has shown of aging..
Edit: and now it's working again! No rhyme or reason.

osm0sis said:
Disregard that bug report. I booted back to Marshmallow and it still doesn't work. Guess there's something up with my accelerometer. First sign my N7 has shown of aging..
Edit: and now it's working again! No rhyme or reason.
Click to expand...
Click to collapse
Mine does that to, the touchscreen stops working too. Everything comes back with a reboot
I'm going to try the hardware mod :good:
I'm using stock with a custom kernel, it's happened on everything. Bricked kernel's touchscreen fixes aren't for these issues btw, if anyone's wondering
http://forum.xda-developers.com/nexus-7-2013/general/fix-nexus-7-2013-grounding-issue-t3011140

Gus Ghanem said:
I've never used it, but if you mean under:
Settings > Display > LiveDisplay > Display mode > Night
Then no, it doesn't look like any color related settings are working. I tried all settings, a dark room, nothing, only Adaptive Brightness and Invert colors work.
Click to expand...
Click to collapse
Thanks Gus, much appreciated your report
---------- Post added at 06:40 AM ---------- Previous post was at 06:37 AM ----------
poondog said:
Mine does that to, the touchscreen stops working too. Everything comes back with a reboot
I'm going to try the hardware mod :good:
I'm using stock with a custom kernel, it's happened on everything. Bricked kernel's touchscreen fixes aren't for these issues btw, if anyone's wondering
http://forum.xda-developers.com/nexus-7-2013/general/fix-nexus-7-2013-grounding-issue-t3011140
Click to expand...
Click to collapse
My touchscreen recovered after applying that mod, there's almost no risk in trying it, I used a bit of foam tape

[OFFICIAL][WEEKLY][7.1.2] LineageOS 14.1 for i9300

Reserved
Builds are up!

Reserved

Good job @forkbomb444

Extreme anxiety for the builds. Until then i will flash the new recovery

GREAT JOB!!!!!!!!!
P.S.: Why is root being shipped separately now?

I9300 Official build is now available
Lineage Os 14.1 i9300 official build is now available to download.
https://download.lineageos.org/i9300

Finally official build here.. Good job!

Do i have to flash both zips (experimental and nightlies) or i have to choose one of them? I'm in Archidroid. Sorry but i read the wiki and i'm still stuck.

bloodlithium said:
Do i have to flash both zips (experimental and nightlies) or i have to choose one of them? I'm in Archidroid. Sorry but i read the wiki and i'm still stuck.
Click to expand...
Click to collapse
Only flash experimental if coming from unofficial Lineage or CM14.
Otherwise clean install the nightly.
The ROM does not include Root.
Lineage will release it's own Root in a few days.
Chainfire's very latest revision to his 2.79 Super Su may work. I have not tried it yet on the Official Lineage ROM.
Sent from my GT-I9300 using XDA-Developers Legacy app

baltics said:
Only flash experimental if coming from unofficial Lineage or CM14.
Otherwise clean install the nightly.
The ROM does not include Root.
Lineage will release it's own Root in a few days.
Chainfire's very latest revision to his 2.79 Super Su may work. I have not tried it yet on the Official Lineage ROM.
Sent from my GT-I9300 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Successfully flash! Thanks. I think i will wait the Lineage Root. Thanks again! Greetings.

andrescm said:
GREAT JOB!!!!!!!!!
P.S.: Why is root being shipped separately now?
Click to expand...
Click to collapse
Those who want to use online secure payment Apps need unroofed devices. Whether this is the reason is just speculation.
Sent from my GT-I9300 using XDA-Developers Legacy app

Wow,it was exactly 1 moth since last official CM build.
Long live LineageOS!!!

Just to confirm..
Built-in file manager works fine and I can easily accesses external sdcard, and another thing is that last SuperSU beta (SuperSu v2.79 SR3) works for root

kiva1 said:
Just to confirm..
Built-in file manager works fine and I can easily accesses external sdcard, and another thing is that last SuperSU beta (SuperSu v2.79 SR3) works for root
Click to expand...
Click to collapse
But will we be able to switch to LOS root afterwards? Will it interfere with su?(i don't ask you directly kiva1 ,maybe someone will answer)

Great job @forkbomb444

LuciferIII said:
But will we be able to switch to LOS root afterwards?
Click to expand...
Click to collapse
Don't know for now. For this we have to wait until they release LOS root.
Sent from my Samsung GT-I9300 using XDA Labs

kiva1 said:
Don't know for now. For this we have to wait until they release LOS root.
Click to expand...
Click to collapse
I will wait till root.zip is out,then i install the latest official build. Just to be sure,i dont want to brake stuff and restore.
And how come no one talks about some of the settings reseting after Nandroid restore?

Thanks very much @forkbomb444 for sticking with us i9300'ers!

Awesome
Tonight I went from stock, to CM14 to Lineage-experimental to Lineage-nightly as smooth as butter, it's amazing. :highfive:

[ROM][Oreo][SM-T550][UNOFFICIAL] AICP for the Samsung Galaxy Tab 9.7 Wifi

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link: https://www.androidfilehost.com/?w=files&flid=274850
Official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
select ARM + Android Oreo 8.1 here: https://opengapps.org/
- SELinux is permissive
- The current builds are "incompatible" with some apps in the Play Store > You can download the last build without this issue here
You tell
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash, and then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Sources:
Kernel source
Device tree
Vendor tree
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
@deadman96385
@Galaxy-MSM8916 team
@elginsk8r
ROM OS Version: 8.1.0 Oreo
Kernel: Linux 3.10.x
Version Information:
Status: NIGHTLY
Release Date: 25-6-2018
You want to see a "normal" night at the "DEV office", click here!!

Can it be installed on t555?

Mihai14 said:
Can it be installed on t555?
Click to expand...
Click to collapse
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.

virsys said:
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.
Click to expand...
Click to collapse
I don't really care about ril but it just doesn't boot. Like the other roms and i just can't find the problem. Lineage os 14.1 should boot on t555 too but without ril and it ij stuck in the boot logo refusing to boot into /system.

Mihai14 said:
it just doesn't boot.
Click to expand...
Click to collapse
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?

virsys said:
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?
Click to expand...
Click to collapse
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data

Mihai14 said:
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data
Click to expand...
Click to collapse
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.

virsys said:
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.
Click to expand...
Click to collapse
Of course i would want to help. I can PM you my telegram.

Hi all,
I tested the ROM on SM-T550 and it boots quiet well.
Initial google (nano opengapps) setup was broken for me, but the setup
via "Google app" and my phone worked.
Another thing is that when installing a browser it
crashes right after starting it.
Opera says that I have no space free
Chrome says something like an unexpected error.
Buildin browser just appears short and closes immediately.
The game little wars and Netflix app shows the same behaviour.
So right now I can't use the ROM but I am very Happy that this device is not abandoned!
Thank you for your work and if I can help testing, just drop me a line.

I have SM-T550
Its great ROM, but.. Problem, has error browser, for example: I can't open Google chrome, opera, ... Pls fix? You are the best! ??

Ok so apparently it boots but the screen is always black. I just found a screenshot i've taken accidentally after i flashed the rom and it seems to boot.

ramaxcalmax said:
Another thing is that when installing a browser it
crashes right after starting it.
Click to expand...
Click to collapse
Thanks for your report. The latest build should work.

My Model: SM-T550
I have one problem... The ROM is great working with all browser (Google Chrome, Opera, ...) Very Good.
But... Please you read.
- It's very laggy the security (for example: PIN, password and Sequence). I'm ready PIN, it's fine.
When my tablet is lock PIN (Off). I'm watching TV or other. My tablet lets off 1 hour. After, I go my tablet open "On" it's very laggy and PIN too, all..
I hope you understanding? I'm a deaf, sorry!

I'm fighting against selinux right now. I'll update the build soon, thanks for your hint.

I think I found why the screen is not working on t555: might be because of a problem in the kernel. More precise the dt. You can use the kernel from the stock firmware as base to fix this. Also for the ril take look at samsung galaxy j5 2015/2016 sources. They have the same chip as t555/t550. Especially the 2016 version as it have almost the same base firmware (7.1.1).

Mihai14 said:
You can use the kernel from the stock firmware as base to fix this.
Click to expand...
Click to collapse
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.

virsys said:
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.
Click to expand...
Click to collapse
I would but my laptop is quite s**t. I have tried to build roms before but ot was a fail.

Thanks for keeping this device relevant. Working great!

Could this be ported to the 8" variant SM- T350 ? We have no Oreo development

vin_001 said:
We have no Oreo development
Click to expand...
Click to collapse
That's not true.
There's oreo development.

[ROM][Redmi 7A][PINE][10.0] LineageOS 17.1 [Unofficial]

Good performance
Very good battery life
Ambient display not working (23.2. image)
Great work, looking forward to a final release.

This custom ROM looks like it could be worth a try. The first post says that MIUI v10.2.5.0 firmware is required but what if the Redmi 7A is on MIUI 11? Is that okay?

You have to downgrade. Otherwise lineage will not boot.

Just wanted to use this i love lineage,running on my zuk z2...but volte is what is have to use ?

partner if I want to root in the ROM just flashes magisk? or do you need to flash another plugin? Why are there some ROMs of other computers that have magisk root to flash and another complement so that something like a permission is not brickee, in this ROM for redmi 7a it is only the magisk and it starts the system?

Been using the rom a few hours. Performing amazing! The only real issue is with the in call audio as written, everything else works amazing. Maybe the signal is a bit lower than with miui, but that's fine. Hope the call audio issue gets fixed asap! Thank you! ?
Update: bluetooth audio is also not working. Completely frozen video playback when bluetooth audio device is connected.

friend did you root? and you just flashed the magisk file or some other file other than the magisk to boot the system ??

Depressing what xda have turned into.. before more people ask, yes, root is easy, just flash magisk, no need to do anything. This is not gsi or miui rom.

GabbyWC said:
This custom ROM looks like it could be worth a try. The first post says that MIUI v10.2.5.0 firmware is required but what if the Redmi 7A is on MIUI 11? Is that okay?
Click to expand...
Click to collapse
You base firmware must be MIUI v10.2.5.0 . Otherwise, it will not boot.

DebrupGhosh said:
Just wanted to use this i love lineage,running on my zuk z2...but volte is what is have to use
Click to expand...
Click to collapse
I am working on it to fix VoLTE. Please keep patience

jason2781 said:
partner if I want to root in the ROM just flashes magisk? or do you need to flash another plugin? Why are there some ROMs of other computers that have magisk root to flash and another complement so that something like a permission is not brickee, in this ROM for redmi 7a it is only the magisk and it starts the system?
Click to expand...
Click to collapse
You can just flash Magisk to root the ROM. No need of another plugins to root it..

gingerboy92 said:
Been using the rom a few hours. Performing amazing! The only real issue is with the in call audio as written, everything else works amazing. Maybe the signal is a bit lower than with miui, but that's fine. Hope the call audio issue gets fixed asap! Thank you!
Update: bluetooth audio is also not working. Completely frozen video playback when bluetooth audio device is connected.
Click to expand...
Click to collapse
Thanks for the feedback. Will fix them soon..

jason2781 said:
friend did you root? and you just flashed the magisk file or some other file other than the magisk to boot the system ??
Click to expand...
Click to collapse
It will boot without rooting. If you want to root it , you can directly flash Magisk . Not any other files required to root it other than Magisk.

Deleted

priyabrat MI said:
I am working on it to fix VoLTE. Please keep patience
Click to expand...
Click to collapse
Thank you
Are you intending to make it official once it becomes stable?

thank you for your hard work. i was about to regret paying 30usd for this phone because of the lack of software update and 3rd party development, the good battery life is the only reason i still haven't threw it out of the window ?

gingerboy92 said:
thank you for your hard work. i was about to regret paying 30usd for this phone because of the lack of software update and 3rd party development, the good battery life is the only reason i still haven't threw it out of the window ?
Click to expand...
Click to collapse
Me2 ...miui in this device is so buggy especially indian version, that i think custom rom is much better as a daily driver than this garbage
Also who wants a spyware in their mobile!?!!

After flashing the .img file I always get a black screen even after waiting for half an hour. (Same with every rom)
Help is really really really appreciated
Thank you
Redmi 7a
Arm
Android 9
Now on mokee 9 (nightly) (only this one works for me not even aosp)

DebrupGhosh said:
Thank you
Are you intending to make it official once it becomes stable?
Click to expand...
Click to collapse
Ofc

Better Mobile App

welcome