{
"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"
}
LineageOS 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.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Bugs/Issues :
Audio input volume is low
The video buffer will be cropped into weird dimensions when streaming (YouTube, etc)
Netflix is broken(?)
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : See below
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
### RELEASES ###
AOSP
01.09.2016 - SM-T815 / SM-T810
Paranoid Android
29.09.2016 - SM-T815 / SM-T810
CyanogenMod
26.10.2016 - SM-T815 / SM-T810
LineageOS
28.01.2017 - SM-T815 / SM-T810
XDA:DevDB Information
AOSP 7.0 Nougat, ROM for the Samsung Galaxy Tab S2
Contributors
RaymanFX
Source Code: https://github.com/CyanogenMod/android_kernel_samsung_gts2/tree/cm-14.1
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-09-01
Last Updated 2016-09-01
you are boss!
I have wifi tab s2, i will test afternoon
T810 version works.
Install image in TWRP
reboot to recovery
install opengapps (I used pico) and supersu.
Found issues:
My SD card is not supported (64 GB, extfat fs) and the device wants to format
Google Play services keeps stopping
Camera seems to be working correct. Initial login to google seems to be working, playstore is having issues.
I guess that's to be expected in the first 7.0 android and opengapps boot,
Chiefs, give me idea where are make mistake on t810. I installed successfully. Then installed pico gapps 7.0 for arm. Got error this gapps are for android 5.1.1, arm 22 if I remember. ROM booted but no google of course.
Give me all steps please
Thanks
Sent from my SM-T810 using XDA-Developers mobile app
I wanna jump on this ROM! But.......
I very want to jump on this ROM and get it tested for feedback and help it developed, but I a major issue..
Can I get this flashed to start with coming from a T-815C that is still running stock 5.01 Lollipop? Believe it or not Samsung is STILL not releasing stock 6.01 for my Hong Kong purchased Tab (version T-815C), only Lollipop updates. Ironically, Hong Kong was one of the very first locations where the Tab S2 line was first available for retail when it was launched and now, they dont even care to get it updated. Even the much older, original Tab S is already getting Marshmallow!!! But the S2 NOT! Subsequently I was told that I cant install Marshmallow CM or ASOP builds on my unit unless I'm already on a stock 6.01 firmware. But how about this 7.0 ROM? Same issue or somehow I can get it flashed directly from 5.01?
I have now reached a point of moral exhaustion with Samsung that is starting to take me to the idea of abandoning the brand forever. I have already had a streak of bad purchases and poor quality issues with several Samsung hardware in the past, and to say their repair centers are basically a waste of time, is an understatement. They do anything possible not to honor any warranties. But now, a current model hardware that doesn't get upgraded at all to a more than 1 year old OS, is starting to be too much for me to take. I bought this Tab under the assumption to immediately get rid of TouchWiz and get an CM or ASOP build in it, ONLY to find out, stupid me, that Samsung neglects completely the hardware they are selling as current models. Its unacceptable. My frustration and disgust at Samsung has reached overboard levels.
Id like to recap and confirm if it is INDEED true that I CAN'T jump into this CM 60.1 ROM unless I am already on Marshmallow? Or is there a workaround and way to do it? The weeks and months are passing by and I go anywhere like this.. just totally stuck.
Anyway, thanks for any advice or ideas on what I can try to do to get my Tab flashed and going with this 7.0 ROM so I can test drive it and give some feedback. There's gotta be away. Thanks again for the input and thumbs up to the developers for this ROM I cant wait to get my hand on
ivanox1972 said:
Chiefs, give me idea where are make mistake on t810. I installed successfully. Then installed pico gapps 7.0 for arm. Got error this gapps are for android 5.1.1, arm 22 if I remember. ROM booted but no google of course.
Give me all steps please
Thanks
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Install image, go back to TWRP main menu, restart to recovery and install gapps.
After that, boot, tap away 'google play services stopped' until you're don and in settings. There give the app 'google play services' every permission it wants and do a 'forced stop' of the application. Then you're ready to go.
I'll check tomorrow which permissions the app really needs, as it wants to much for my taste.
Sent from my T810 running cm-13.0
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
VeEuzUKY said:
I very want to jump on this ROM and get it tested for feedback and help it developed, but I a major issue..
Can I get this flashed to start with coming from a T-815C that is still running stock 5.01 Lollipop? Believe it or not Samsung is STILL not releasing stock 6.01 for my Hong Kong purchased Tab (version T-815C), only Lollipop updates. Ironically, Hong Kong was one of the very first locations where the Tab S2 line was first available for retail when it was launched and now, they dont even care to get it updated. Even the much older, original Tab S is already getting Marshmallow!!! But the S2 NOT! Subsequently I was told that I cant install Marshmallow CM or ASOP builds on my unit unless I'm already on a stock 6.01 firmware. But how about this 7.0 ROM? Same issue or somehow I can get it flashed directly from 5.01?
I have now reached a point of moral exhaustion with Samsung that is starting to take me to the idea of abandoning the brand forever. I have already had a streak of bad purchases and poor quality issues with several Samsung hardware in the past, and to say their repair centers are basically a waste of time, is an understatement. They do anything possible not to honor any warranties. But now, a current model hardware that doesn't get upgraded at all to a more than 1 year old OS, is starting to be too much for me to take. I bought this Tab under the assumption to immediately get rid of TouchWiz and get an CM or ASOP build in it, ONLY to find out, stupid me, that Samsung neglects completely the hardware they are selling as current models. Its unacceptable. My frustration and disgust at Samsung has reached overboard levels.
Id like to recap and confirm if it is INDEED true that I CAN'T jump into this CM 60.1 ROM unless I am already on Marshmallow? Or is there a workaround and way to do it? The weeks and months are passing by and I go anywhere like this.. just totally stuck.
Anyway, thanks for any advice or ideas on what I can try to do to get my Tab flashed and going with this 7.0 ROM so I can test drive it and give some feedback. There's gotta be away. Thanks again for the input and thumbs up to the developers for this ROM I cant wait to get my hand on
Click to expand...
Click to collapse
I expect you'll need to flash 'a' 6.0.x stock image. Any one will do, as long as it's for T815.
First make a backup with twrp of current image, then flash stock 6.0.x with odin, then flash this image with twrp, reboot to recovery and install opengapps.
Sent from my T810 running cm-13.0
T_I said:
Install image, go back to TWRP main menu, restart to recovery and install gapps.
After that, boot, tap away 'google play services stopped' until you're don and in settings. There give the app 'google play services' every permission it wants and do a 'forced stop' of the application. Then you're ready to go.
I'll check tomorrow which permissions the app really needs, as it wants to much for my taste.
Sent from my T810 running cm-13.0
Click to expand...
Click to collapse
Thanks, boss.
But, how to root? You said youmust root explicitly.
Thanks
Sent from my SM-N920C using XDA-Developers mobile app
Screenshots...
Main screen
About
SuperSU
Google play service with not enough permissions
Unsupported extfat (sdcard of 64GB, stock formatting), vfat works as I understand it.
Sent from my SM-T810 using Tapatalk
---------- Post added at 08:42 PM ---------- Previous post was at 08:36 PM ----------
ivanox1972 said:
Thanks, boss.
But, how to root? You said youmust root explicitly.
Thanks
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
I've installed BETA-SuperSU-v2.74-2-20160519174328.zip and when you connect with google play it gets updated.
I'm currently back at cm-13.0, as I have some things to do tonight. I will copy sdcard and reformat to vfat tomorrow to switch, get some extended testing done. Nice to play with it.
Sent from my SM-T810 using Tapatalk
T_I said:
I expect you'll need to flash 'a' 6.0.x stock image. Any one will do, as long as it's for T815.
First make a backup with twrp of current image, then flash stock 6.0.x with odin, then flash this image with twrp, reboot to recovery and install opengapps.
Click to expand...
Click to collapse
I cant! This is what I just explained! There is NO stock 6.0.x firmware update from Samsung from a Hong Kong T815-C, only Lollipop. Ive tried flash other stock 6.0.x with odin for T815 from other regions, and the flash gets aborted. Will not go it.
What can I do? This is too ridiculous that Samsung doesn't offer a 6.0.x update for a T815C..
The Play Services nag is irritating but I'll happily put up with it just to be able to try Android 7. Since I installed it, I've spent most of the time loading apps rather than having a chance to test many. I did try both Hulu and Netflix. Netflix works, Hulu doesn't. It get stuck buffering.
edit: I just flashed supersu and that seems to have fixed the Play Service closing problem.
VeEuzUKY said:
I cant! This is what I just explained! There is NO stock 6.0.x firmware update from Samsung from a Hong Kong T815-C, only Lollipop. Ive tried flash other stock 6.0.x with odin for T815 from other regions, and the flash gets aborted. Will not go it.
What can I do? This is too ridiculous that Samsung doesn't offer a 6.0.x update for a T815C..
Click to expand...
Click to collapse
Any stock 6.0.x image will do, as I tried to explain. You need an adjustment in one of the internal device blobs, forgot which one, but wuthout android 6 and higher won't boot. After that you can run cm-13.0 or this image.
I tested T815 cm-13 on my T810 and after a stock flash (EU tab, Canadian stock) it worked. I'm 'officially' stuck at 5 as well, that didn't stop me. [emoji1]
Make a TWRP backup after installing the latest official update and flash. Some experience with odin and twrp is nice, but not required, the manuals are good. When you know someone who did these things before and you're not sure uf you can do it, getting help is useful.
Sent from my SM-T810 using Tapatalk
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
lewmur said:
The Play Services nag is irritating but I'll happily put up with it just to be able to try Android 7. Since I installed it, I've spent most of the time loading apps rather than having a chance to test many. I did try both Hulu and Netflix. Netflix works, Hulu doesn't. It get stuck buffering.
edit: I just flashed supersu and that seems to have fixed the Play Service closing problem.
Click to expand...
Click to collapse
Which version supersu are you using and can you check if permissions for google play services are still all off or that all are turned on now.
Sent from my SM-T810 using Tapatalk
T_I said:
Which version supersu are you using and can you check if permissions for google play services are still all off or that all are turned on now.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
SuperSu version 2.76. Hulu said it needed all of the permissions turned on, so I turned them all on trying to get it to work. I just turned them all back off and I'm still not getting the nag.
Everything installed ok, but the internet Data did not work for me, it shows my internet provider name, full bars but nothing else, do not conect, neither shows 4g or LTE, I have the 815Y
Please for T715................:'(
@T_I
please, just tell me which gapps to install exactly?
ivanox1972 said:
@T_I
please, just tell me which gapps to install exactly?
Click to expand...
Click to collapse
I installed opengapps ARM 7.0 pico.
Has anyone tried this on the SM-T710 yet? I just achieved root last night, first time with android. I used to have apple and jailbreak. Just trying to get into this and see what it is about but can't with my phone as it is the Verizon note 5(920V). Thanks
Sent from my SM-T710 using Tapatalk
I can't find the setting in this ROM that allows me to display my owner info on the lock screen. There is a tiny blue icon at the top of the screen that says "owner", and I can put my info there. But the odds of some store clerk that finds my tablet, noticing that icon and thinking to touch it are little to none.
Dang, you guys are fast.
T_I said:
Install image, go back to TWRP main menu, restart to recovery and install gapps.
After that, boot, tap away 'google play services stopped' until you're don and in settings. There give the app 'google play services' every permission it wants and do a 'forced stop' of the application. Then you're ready to go.
I'll check tomorrow which permissions the app really needs, as it wants to much for my taste.
Sent from my T810 running cm-13.0
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
I expect you'll need to flash 'a' 6.0.x stock image. Any one will do, as long as it's for T815.
First make a backup with twrp of current image, then flash stock 6.0.x with odin, then flash this image with twrp, reboot to recovery and install opengapps.
Sent from my T810 running cm-13.0
Click to expand...
Click to collapse
Done like this, all ok. Android 7 looks great on 1. sight, of course this rom needs fixes and adding options. Specially manipulation with buttons, to switch them off. Generally GREAT job, thanks a Lot
Sent from my SM-N920C using XDA-Developers mobile app
Related
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 8.9"
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128175
CHECK KNOWN ISSUES BEFORE FLASHING. PROBABLY NOT GOOD ENOUGH FOR DAILY USE.
Official nightly builds can be found here:
http://download.cyanogenmod.org/?device=jem
Download Google Apps for Android 5.1:
https://www.androidfilehost.com/?w=files&flid=25361
(Choose newest *-5.1-* file)
NOTES:
Older versions of TWRP will show a "mount failed error". This is safe to ignore. TWRP 2.8.7.0 and on is recommended for cm-12.1 / android-5.1.
First boot after a clean wipe will take a LONG time. Be patient.
KNOWN ISSUES:
Use XDA Bug Reporter
SCREEN SHOTS:
Use XDA Screenshots
XDA:DevDB Information
CM12.1 KFire HD 8.9 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Beta Release Date: 2015-06-24
Created 2015-01-02
Last Updated 2015-06-24
Reserved
KERNEL UPDATES for Lollipop Android 5.0 / 5.1
Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP
Combined defconfig setup to better support all HD models
Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)
Picked IPV6 routing changes from Google's common 3.4 kernel
Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection
Reserved
Android 5.1 / CM-12.1 changes:
SElinux Enforcing as default enabled
Holy smokes! Was hoping this would be out soon after seeing it released for the 7 inch! Thank
You hashcode for all your hours and hard work that allows us to have a better experience with the kindle! This is awesome and can't wait to try!
Mike
update: did wipe, installed cm12 clean with no errors, installed gapps clean with no errors! this maybe normal but progress bar in TWRP did not move after "swipe to install" until file 3 of 3 gapps was installing and it was almost complete (had my heart beating a little faster than normal) : ) but then all was good! first boot took about 6 to 7 minutes i would say (meant to time it but forgot) have went through all settings and all seems good, wireless good, all gapps seem good, not a single bug/glitch/crash SO FAR! thanks a million Hashcode! continuing to test out everything right now but all seems good!
Mike
OK I noticed one major thing....I lost root. Why did that happen? I did not lose root after I flashed cm11. Is this because its alpha unofficial release? Thanks in advance for any input!
Mike
Pretty dang good for a first build. I think a new TWRP and f2fs is going to bring the life back to this device. Its been pretty laggy ever sense the Kit Kat builds. I don't remember Jelly Bean being this slow. Maybe I'm just used to faster devices now, but I've always adored my Amazon Jem. Only thing I've seen thus far is Chrome Browser crashes after a minute or two, a bit laggy overall, a battery whore, and Google Launcher flat out doesn't work. Could be the gapps package though. Awesome work so far my friend, real treat. Thanks Hash'
---------- Post added at 08:42 AM ---------- Previous post was at 08:39 AM ----------
11fan said:
OK I noticed one major thing....I lost root. Why did that happen? I did not lose root after I flashed cm11. Is this because its alpha unofficial release? Thanks in advance for any input!
Mike
Click to expand...
Click to collapse
Just flash a SuperSU zip and root is back. I think it's a CM issue because I lost root on other CM12 devices as well recently.
Thank you!!.Rom is fantastic..Gap link is a waste some kinda malware...
Here are a couple links while they last.
https://app.box.com/s/80q8qu7l9akgb04u828j
https://www.dropbox.com/s/lwbf3laae901mgo/gapps-lp-20141122-signed.zip?dl=0
There was two download tabs in the gapps link. Top one was junk as you described, I grabbed that one first also. But the bottom download tab was correct gapps for LP with matching md5.
Mike
---------- Post added at 08:04 AM ---------- Previous post was at 07:53 AM ----------
zavien3 said:
Pretty dang good for a first build. I think a new TWRP and f2fs is going to bring the life back to this device. Its been pretty laggy ever sense the Kit Kat builds. I don't remember Jelly Bean being this slow. Maybe I'm just used to faster devices now, but I've always adored my Amazon Jem. Only thing I've seen thus far is Chrome Browser crashes after a minute or two, a bit laggy overall, a battery whore, and Google Launcher flat out doesn't work. Could be the gapps package though. Awesome work so far my friend, real treat. Thanks Hash'
---------- Post added at 08:42 AM ---------- Previous post was at 08:39 AM ----------
Just flash a SuperSU zip and root is back. I think it's a CM issue because I lost root on other CM12 devices as well recently.
Click to expand...
Click to collapse
Flash a zip as in with adb install or just doing regular apk install will work? Thanks
Mike
I installed cm12 and gapps clean with no errors, no problems so far. No root when tried to install apps with root access...the solution was easy: in Configuration, Developer Options, Root Access tab.
Thanks Hashcode!
zavien3 said:
Pretty dang good for a first build. I think a new TWRP and f2fs is going to bring the life back to this device. Its been pretty laggy ever sense the Kit Kat builds. I don't remember Jelly Bean being this slow. Maybe I'm just used to faster devices now, but I've always adored my Amazon Jem. Only thing I've seen thus far is Chrome Browser crashes after a minute or two, a bit laggy overall, a battery whore, and Google Launcher flat out doesn't work. Could be the gapps package though. Awesome work so far my friend, real treat. Thanks Hash'
Try using PA GAPPS located at http://forum.xda-developers.com/showthread.php?p=56832776. Both Chrome Browser and Google Now Launcher work. I flashed the Full Modular package (clean flash with the ROM).
@Hashcode another great job - can't thank you enough.
Sent from my Amazon Jem using XDA Free mobile app
Click to expand...
Click to collapse
jaramosparra said:
I installed cm12 and gapps clean with no errors, no problems so far. No root when tried to install apps with root access...the solution was easy: in Configuration, Developer Options, Root Access tab.
Thanks Hashcode!
Click to expand...
Click to collapse
@jaramosparra thanks for the reminder! have been so excited about trying this out i did not even think about enabling those options.!
Mike
Root Works Fine
Root is now enabled through developer options.
Been running this since release and I have to say that it is functioning remarkably well. Almost a DD.
Does anyone know if Philz Touch 6.48 (the latest) has F2FS support?
think you for you working!
Didn't think that I would have Lollipop on my old KFHD before my HTC One M8!!
I have been running this for 3 or 4 days and all seems to be running great for me. I have found with the previous KitKat builds that it would only start to slow down if I installed too many apps. So far I just installed what I need (I just generally use it to browse the internet, read news and run any apps that cast to my chromecast) and it is certainly not any slower than Kitkat. One thing I did do a bit different was to install the "Micro Modular Package" from the PA Gapps Package in the link that BobJayJr posted (http://forum.xda-developers.com/showthread.php?p=56832776) to keep as much space available as I could.
Thanks very much for your time and effort Hashcode. Has kept my old Tablet going so much longer than I expected when I bought it
Been running for 2 days without issue. Is there any plans for an LTE version for working Bluetooth ?
Quick question: Has anybody done a backup from TWRP of the DATA partition and restored it after installing CM12 + Gapps?
I've done it, and it's been stuck on the CM boot logo for 5-10 minutes.
I've tried without restoring data and although it was a long boot but it did eventually boot. Any suggestions?
UPDATE: It booted so just ignore me
It was a little too slow with restoring the DATA partition so I just started from scratch - anyway so far so good. ROM is wicked. Thanks for the work
Hashcode said:
UNOFFICIAL CyanogenMod 12.0 for the Kindle Fire HD 8.9"
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
CHECK KNOWN ISSUES BEFORE FLASHING. PROBABLY NOT GOOD ENOUGH FOR DAILY USE.
Download Google Apps for Android 5.0:
http://d-h.st/users/dhacker29/?fld_id=27426#files
(Choose newest gapps-lp-* file and use the "Download Now" button)
NOTES:
You may see a "mount failed error" in TWRP when flashing the build. This is safe to ignore.
First boot after a clean wipe will take a LONG time. Be patient.
Unofficial builds can be found here:
Use XDA Downloads
CHANGES (always includes CM changes):
[01/02] 1st public release
KNOWN ISSUES:
Use XDA Bug Reporter
SCREEN SHOTS:
Use XDA Screenshots
XDA:DevDB Information
CM12.0 KFire HD 8.9 (LP 5.0.x), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Beta Release Date: 2015-01-02
Created 2015-01-02
Last Updated 2015-01-04
Click to expand...
Click to collapse
Would it be safe to perform a dirty flash from CM11, or would I need to do a clean wipe?
{
"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"
}
This is Candy5. Built straight from CyanogenMod source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM.We aim to add more features as this project progresses.
Check us out on the web @The-Candy-Shop
@matthew0776 @mar5hal @gimmeitorilltell @BMP7777 @CyberScopes @Cuzz1369 @rc420head @Flashalot @tr1gg3r84 @Venomtester @Darknites @Rapier @NexusPenguin @Alx31TLse @timmytim
Disclaimer: We here at The CandyShop are not responsible for any bricks you may obtain. Please follow the thread rules and steps and everything will be gravy. Remember, backing up before flashing is always recommended.
Features
*Candy Interface
*Navi Bar Height...Candy Interface
*Battery Percent ...Candy Interface / Status Bar
*Recents Panel Options ...Candy Interface/Recents Panel
*Clock and Date Options...Candy Interface/Clock and Date
*Wake Options ...Display
* Rotation 360 degrees...Display
*Custom Notification Lights...Sounds&Notifications
*Lockscreen Notifications Per App...Sounds&Notifications/App notifications
*IME options from 4.4+ ...Language and input/advanced options
*Disable Ime selector (thanks cm)
* Visual improvements
*ALL of Cm's Latest Feature Additions*
CHANGELOG
Steps:
Download Candy5.zip
Download Gapps (optional)
Place Candy5.zip on phones memory or SD card
Boot into recovery (USE MY TWRP (ONLY) in second post or CWM if it's been updated)
FULL wipe! (Dalvik Cache, Cache, System, Factory Data Reset)
Flash Candy5.zip
Boot into system
Flash Gapps
Reboot and Enjoi
Candy5-QUINCYTMO
* Gapps
Or use 5.0.0 Gapps of choice. !!!!NOTE!!!! Some are having issues with the playstore NOT installing so you might have to try some different gapps!!!!
Please give first boot a GOOD TEN minutes.
I DO NOT OWN THIS DEVICE!! I OWN THE QUINCYATT!! I AM JUST SHARING THIS BUILD BECAUSE I WAS FEELING GENEROUS!! PLEASE DO NOT ASK FOR NEW BUILDS!! I will update this rom "IF" I feel like it & "IF" I have the time. I am not trying to be rude here but many other devices I have that I own & support. Please be kind and appreciate this rom thread if you enjoy it. One last thing, let me know if it boots or not? This is just to give this device owner something new to flash. I believe you can somehow flash the quincyatt builds to this device, OR SO I'VE READ, I just don't know how to tell you to go about doing so.
Special thanks to CyanogenMod, SlimRoms,for making their source open. @NoSpamDan for helping with this device, hercules, & skyrocket. Be sure N thank him for getting Data working. Also I believe that @SultanXDA helped him with that a bit.
Sources:
CyanogenMod
SlimRoms
LiquidSmooth
XDA:DevDB Information
Candy5, ROM for the T-Mobile Samsung Galaxy Note
Contributors
gimmeitorilltell, gimmeitorilltell
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod, SlimRoms, BeanStalk, LiquidSmooth
Version Information
Status: Testing
Created 2015-03-03
Last Updated 2015-03-02
I can't believe that development is still so strong for this phone!!!! A very pleasant surprise. Thank you so much @ gimmeitorilltell
With this t-mo build do you know if the wifi calling app is included? I have flashed a t-mo build to this Att phone a couple years ago and it worked very well with the wifi calling working. I may just have to give it a try and see for myself!
sashusmom said:
I can't believe that development is still so strong for this phone!!!! A very pleasant surprise. Thank you so much @ gimmeitorilltell
With this t-mo build do you know if the wifi calling app is included? I have flashed a t-mo build to this Att phone a couple years ago and it worked very well with the wifi calling working. I may just have to give it a try and see for myself!
Click to expand...
Click to collapse
If you have the AT&T version then I have a few 5.0 roms over in the right section of development. Also have cm-12.0 in the original development section of AT&T devices. I am not sure about the wifi calling for T-mobile but I believe that all of my builds have wifi calling.
gimmeitorilltell said:
If you have the AT&T version then I have a few 5.0 roms over in the right section of development. Also have cm-12.0 in the original development section of AT&T devices. I am not sure about the wifi calling for T-mobile but I believe that all of my builds have wifi calling.
Click to expand...
Click to collapse
Yes, I have an att version- i717. I successfully flashed a tmobile rom with correct baseband changes when this phone was 6 months old-got it on launch day- and the official t-mobile wifi calling app was working.
I don't know of any other carrier that supports official wifi calling with your carrier number other than t-mo. Att is working on it, but it's still not out. Sometime in 2015 att will launch that official call over wifi with your att number. It comes in very handy when you are in a dead zone. Just turn on wifi calling and your phones works the same as over the 3g and lte connections, but on any wifi network with your native number.
I know voip over wifi works with 3rd party apps. Is that the kind of wifi calling you're referring to??
Either way, I will definitely check out your other 5.0 roms for the att Note. In the ATT side of development. My Note has been on the shelf for the past year or so!!!
Hi. I need help. I followed all the steps above but I can´t flash the rom. It always gets stuck at the goggle logo. I used CWM, because if I try WTRP I get a message error like " E:unknown volume for path. Any ideas? :crying:
Memocama said:
Hi. I need help. I followed all the steps above but I can´t flash the rom. It always gets stuck at the goggle logo. I used CWM, because if I try WTRP I get a message error like " E:unknown volume for path. Any ideas? :crying:
Click to expand...
Click to collapse
You NEED to wipe everything except the sdcard & internal sd. Try that to see what you get?
No luck. Did all the wipes and nothing. I'm considering do a dirty install.
I get this message: error executing updater binary in zip "/sdcard1/candy5
Memocama said:
No luck. Did all the wipes and nothing. I'm considering do a dirty install.
I get this message: error executing updater binary in zip "/sdcard1/candy5
Click to expand...
Click to collapse
Your recovery seems like it needs updated. I do not own this device so not sure which one will work. Do some research & see if you can flash my quincyatt roms to this device maybe? It has been done in the past & I keep those roms updated.
gimmeitorilltell said:
Your recovery seems like it needs updated. I do not own this device so not sure which one will work. Do some research & see if you can flash my quincyatt roms to this device maybe? It has been done in the past & I keep those roms updated.
Click to expand...
Click to collapse
Pollution used the patch for ROMs from att but he hasn't updated the patch to run 5.0 I have a busy day at work tomorrow but when u get home I'll give it a shot thanks gimme!!
Sent from my SAMSUNG-SGH-T879 using XDA Premium 4 mobile app
angelf82 said:
Pollution used the patch for ROMs from att but he hasn't updated the patch to run 5.0 I have a busy day at work tomorrow but when u get home I'll give it a shot thanks gimme!!
Sent from my SAMSUNG-SGH-T879 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im sure pollution is still around so maybe he would update things? If he isn't interest in this device any longer then maybe someone else could update his scripts, with permission from pollution of course.
i need help i get stuck at the goggle logo any idea ?? ?
i need help i get stuck at the goggle logo any idea ?? ? :crying::crying::crying::crying::crying:
What TWRP version do I use? I don't see one to download in post #2.
Boot into recovery (USE MY TWRP (ONLY) in second post or CWM if it's been updated)
gimmeitorilltell said:
Your recovery seems like it needs updated. I do not own this device so not sure which one will work. Do some research & see if you can flash my quincyatt roms to this device maybe? It has been done in the past & I keep those roms updated.
Click to expand...
Click to collapse
I used CWM 6.0.4.3 and your version of TWRP 2.8.3.0 whit no success. Until I find a solution, I´m using the Beanstalk ROM. But I wonder if there is conflict with the kernel.
---------- Post added at 12:19 AM ---------- Previous post was at 12:13 AM ----------
wgiddyup and nourmax64: I backed up my phone before flash the ROM. I wanna think you did so. If not, the only way to get your phone back is reflash the stock ROM with Odin. And then, if you want update your OS to KitKat, use the Beanstalk ROM, until we find a way to install this ROM.
wgiddyup said:
What TWRP version do I use? I don't see one to download in post #2.
Boot into recovery (USE MY TWRP (ONLY) in second post or CWM if it's been updated)
Click to expand...
Click to collapse
Memocama said:
I used CWM 6.0.4.3 and your version of TWRP 2.8.3.0 whit no success. Until I find a solution, I´m using the Beanstalk ROM. But I wonder if there is conflict with the kernel.
---------- Post added at 12:19 AM ---------- Previous post was at 12:13 AM ----------
wgiddyup and nourmax64: I backed up my phone before flash the ROM. I wanna think you did so. If not, the only way to get your phone back is reflash the stock ROM with Odin. And then, if you want update your OS to KitKat, use the Beanstalk ROM, until we find a way to install this ROM.
Click to expand...
Click to collapse
Sorry about the TWRP mishap. My OP is a C&P from my quincyatt thread which has the twrp for that device. This device would need someone to update recovery for it.
Hello.
Any news on how to install this rom without any problems. I tried and got stuck on flying dots.
I would like to try this rom.
Thanks.
gimmeitorilltell said:
Sorry about the TWRP mishap. My OP is a C&P from my quincyatt thread which has the twrp for that device. This device would need someone to update recovery for it.
Click to expand...
Click to collapse
Hey gimme any luck updating this Rom for us? I have beanstalk but it gives me at least 5 BSOD (blue screens of death) a day...thanks in advanve
angelf82 said:
Hey gimme any luck updating this Rom for us? I have beanstalk but it gives me at least 5 BSOD (blue screens of death) a day...thanks in advanve
Click to expand...
Click to collapse
Unfortunately work has me very tied up lately and I have not updated this rom. Maybe you and some others can see about flashing my quincyatt roms to this device? It has been done in the past & I really have no time to look into this currently. You may be able to kindly ask @pollution for some assistance or insight on what needs to be done. I believe he was the Dev that made this possible in the past?
gimmeitorilltell said:
Unfortunately work has me very tied up lately and I have not updated this rom. Maybe you and some others can see about flashing my quincyatt roms to this device? It has been done in the past & I really have no time to look into this currently. You may be able to kindly ask @pollution for some assistance or insight on what needs to be done. I believe he was the Dev that made this possible in the past?
Click to expand...
Click to collapse
Thank you I'll see if he would....
angelf82 said:
Thank you I'll see if he would....
Click to expand...
Click to collapse
Sounds good. If he is not able to help I would be willing to see what I can do when/if I get the time. Not sure when that would be but time is not on my side currently.
gimmeitorilltell said:
Sounds good. If he is not able to help I would be willing to see what I can do when/if I get the time. Not sure when that would be but time is not on my side currently.
Click to expand...
Click to collapse
No worries bro I have another question can I install a ROM through my internal sd card? My phone is not reading my micro sd card so I can not install anything and my USB port does not work so if I do a factory reset through custom recovery will it delete the rom I download it?
{
"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"
}
Disclaimer:
Code:
/*
* 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.
*
*/
DEVICE DISCLAIMER:
I DON'T OWN THE DEVICE. TESTING ON THE SPECIFIC DEVICE WILL BE LIMITED TO TESTERS
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested ON HAMMERHEAD, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
And lastly, this is first and foremost a ROM about Nexus 5 (hammerhead). This is my personal device, this is where I test the ROM. angler, bullhead, flo, MAKO, shamu builds are provided AS-IS. With that in mind, I have to say that the google+ community has been flashing mako builds for a looong time and hasn't come up with anything, so I thought I'd share it here, too.
That said, welcome aboard!
Google+ Community
Krexus kernel (thanks to @CallMeAldy)
PushBullet Channel
DOWNLOAD LINKS: AndroidFileHost
DOWNLOAD LINKS: BasketBuild
CHANGELOG
XDA:DevDB Information
Krexus, ROM for the Google Nexus 4
Contributors
KreAch3R
Source Code: https://github.com/krexus
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-02-03
Last Updated 2016-08-29
I'm linking to the Nexus 5 thread so I only have to manage one thread's updates.
Features List
Video review by @kassu99:
I'm linking to the Nexus 5 thread so I only have to manage one thread's updates.
F.A.Q.
This will be the post where I am going to write any new updates for my ROM. First of all, welcome!
For mako's forums, this is a new ROM. But for Google+, it isn't. I have been testing it and releasing some builds in this private community, so make sure to ask to join for the latest info! I created this thread to let more people try my ROM, only now that I feel that it is in an almost perfect condition.
As as I said, my idea is to create a better stock ROM, and this is my target goal.
Another one of my target goals is to make the release of a new build almost automated. Right now, the compilation of the 6 devices build list is finishing, and is uploaded to basketbuild, using clever smart scripts. This also updates the changelog in my site, so I don't have to write a new post every time a new build is released. Everything should just work!
Speaking of releases, the ROM comes with an updater, so you don't even have to check the community or this thread for new links. But follow the pushbullet channel if you want!
I've been copy/pasting information for the past half hour, so this new thread is bound to have mistakes and inconsistencies. Let me know and I'll fix it!
Some other important points:
You have to flash SuperSU and GApps.
If you have a question, you should check out google+, in case it's there.
For the Devs: check my vendor folder, I have been developing some automation scripts which, I think, you will like!
I am an one man team, sorry for any slow responses.
Yes, this ROM is released for 6 devices, not mako or hammerhead only. You can grab the zips from Basketbuild. I haven't created XDA threads for the others (yet) because I don't own them, but I thought I should give a go at mako, since I owned the device before.
I hope you like the ROM!!!
Thank you very much for Krexus @KreAch3R , really love the stability, smoothness and simplicity...Krexy indeed! ?
Sent from my Nexus 4 using Tapatalk
MtG92 said:
Thank you very much for Krexus @KreAch3R , really love the stability, smoothness and simplicity...Krexy indeed!
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hahah thanks! Enjoy! :good::highfive:
Did a clean flash, stuck on bootloop. It's been on bootloop since last night. I will wait until I hear other people's experience with this ROM.
mohsinkhan35 said:
Did a clean flash, stuck on bootloop. It's been on bootloop since last night. I will wait until I hear other people's experience with this ROM.
Click to expand...
Click to collapse
Hello! I'm sorry your first experience was bad. Please join the community so you can see other people's experience. Also, you can check the screenshots in DevDB to see that the ROM is booting.
Now, to troubleshoot. Did you try to flash only the ROM? If you did, check if your downloaded file matches this MD5: 8833b5804b786c6dbc4cc14f17b4486d And you don't need to let it one whole night bootlooping, stop it after 10min.
KreAch3R said:
Hello! I'm sorry your first experience was bad. Please join the community so you can see other people's experience. Also, you can check the screenshots in DevDB to see that the ROM is booting.
Now, to troubleshoot. Did you try to flash only the ROM? If you did, check if your downloaded file matches this MD5: 8833b5804b786c6dbc4cc14f17b4486d And you don't need to let it one whole night bootlooping, stop it after 10min.
Click to expand...
Click to collapse
Many Thanks @KreAch3R!! I am downloading it again as I type. In the past I used to flash ROM, boot the ROM and then flash gApps. I encountered many FCs that way. Now I flash ROM and gApps(only playstore), opengapps pico to be precise. For previous ROMs it has worked, would you suggest flashing them seperately?
I will update this post in bit after the install. Hopefully it goes smooth!
Update: Perfect! booted up nice! Time to play around with it, Thanks again for this beauty!
mohsinkhan35 said:
Many Thanks @KreAch3R!! I am downloading it again as I type. In the past I used to flash ROM, boot the ROM and then flash gApps. I encountered many FCs that way. Now I flash ROM and gApps(only playstore), opengapps pico to be precise. For previous ROMs it has worked, would you suggest flashing them seperately?
I will update this post in bit after the install. Hopefully it goes smooth!
Update: Perfect! booted up nice! Time to play around with it, Thanks again for this beauty!
Click to expand...
Click to collapse
Great! I hope you like it!
To answer your question: OpenGApps are definitely having SetupWizard FCing if you boot once before flashing them. I solve this by wiping data after the first boot.
I thought though that this happens with every GApps package on marshmallow (never tested it tbh). Isn't this the case? Which gapps have you flashed on Marshmallow roms that didn't do that?
KreAch3R said:
Great! I hope you like it!
To answer your question: OpenGApps are definitely having SetupWizard FCing if you boot once before flashing them. I solve this by wiping data after the first boot.
I thought though that this happens with every GApps package on marshmallow (never tested it tbh). Isn't this the case? Which gapps have you flashed on Marshmallow roms that didn't do that?
Click to expand...
Click to collapse
None, I think they all do that. So far I tested Open and bAnks. Both didn't work when installed after booting the ROM.
The first time I was stuck on bootloop was because TWRP asked me to run Super SU script and I went ahead with it, this time I didn't run the script after ROM and GAPPS install. So far, I am liking everything. I still haven't had a chance to charge full battery and judge the battery stats but the performance and fluidity is spot on!
mohsinkhan35 said:
None, I think they all do that. So far I tested Open and bAnks. Both didn't work when installed after booting the ROM.
The first time I was stuck on bootloop was because TWRP asked me to run Super SU script and I went ahead with it, this time I didn't run the script after ROM and GAPPS install. So far, I am liking everything. I still haven't had a chance to charge full battery and judge the battery stats but the performance and fluidity is spot on!
Click to expand...
Click to collapse
Ah, that's why. When you flash the latest SuperSU zips, they go systemless by default, so TWRP isn't detecting any SuperSU on system. TWRP is vey outdated on this front and Chainfire himself suggests never to press that button.
Regarding mako, krexus and a new battery
Great rom. Very smooth and bloat free.
2 things: i miss hide search from recents , the cm-style settings (redundant wifi / bt/ data switches at the top) are a jb/kk era throwback
Is the kernel based on Aldy's (minimal rom)? He has the best MM kernel for mako, in my testing.
Keep it up, all is well when the thread is quiet
Sent from my Nexus 4 using Tapatalk
Could someone tell me about this ROM? How is battery life?
Sent from my Nexus 4 using Tapatalk
[email protected] said:
Could someone tell me about this ROM? How is battery life?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
After going through chroma, minimal, resurrection, fake, orion, back to minimal, chroma, and lastly Krexus.
I think I have finally quenched my flashing thirst with Krexus+Quanta v10. It's only been a day, so far its fluid, and battery is holding up pretty good. Minimal OS is pretty good as well I will admit but I flashed Krexus because the future of Minimal OS looked in doubt. Now that CallmeAldy is back at supporting Minimal OS, it will be a tough choice between Krexus and Minimal. :silly:
danielcepa said:
Great rom. Very smooth and bloat free.
2 things: i miss hide search from recents , the cm-style settings (redundant wifi / bt/ data switches at the top) are a jb/kk era throwback
Is the kernel based on Aldy's (minimal rom)? He has the best MM kernel for mako, in my testing.
Keep it up, all is well when the thread is quiet
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hide searchbar is there, just in a different place. Look under apps--> default apps --> assistant & voice input --> show widget. That's where it is the perfect place for me. As for qs drawer, I don't want to move away from stock right now.
The default mako kernel is Aldy's marshmallow kernel, yes. Not AK, just the stock one he made so that a marshmallow ROM can boot.
I only include one in mako because it is needed. I go with stock Google kernels in all other devices.
& yeah, no news is good news in dev threads. It means no bugs
mohsinkhan35 said:
After going through chroma, minimal, resurrection, fake, orion, back to minimal, chroma, and lastly Krexus.
I think I have finally quenched my flashing thirst with Krexus+Quanta v10. It's only been a day, so far its fluid, and battery is holding up pretty good. Minimal OS is pretty good as well I will admit but I flashed Krexus because the future of Minimal OS looked in doubt. Now that CallmeAldy is back at supporting Minimal OS, it will be a tough choice between Krexus and Minimal. :silly:
Click to expand...
Click to collapse
That is what I get from all my mako users too, that they have seen a greater fluidity and battery usage. You know how it's all personal etc, but I have heard it from all of them, so that's worth mentioning. I had a mako (now my brother's) and he says the same too.
My personal choice is Quanta as well. Perfect for my/his needs.
As far as choice, Minimal and Krexus are brothers (a lot of common code between us, as Aldy finds the time to update it and merge stuff). In some time, I suppose MininalOS is going to have a lot of krexus stuff and then some more, while I keep going the "better stock" way. So it's just about the ROM philosophy.
I'm loving this ROM, testing the battery life and enjoying so far. Just one issue that I noticed is tab style on Chrome it's not dettached in recents, it's like pre-Lollipop days.
I'll try it right now, but I can't find your custom setup for the stock of "Open-GApps" which you mention in the FAQs. I already applied to the Google+ Community, but I've to wait.
Thanks
EDIT: I found it, probably i misunderstood that this gapps package was personalized by you, hence I wasn't able to find it.
EDIT2: I flashed latest supersu 2.67, quantaV10 and nano gapps; So I may have problems with Layers because of supersu, right? that's what I understand from FAQs.
Cristiano Lira said:
I'm loving this ROM, testing the battery life and enjoying so far. Just one issue that I noticed is tab style on Chrome it's not dettached in recents, it's like pre-Lollipop days.
Click to expand...
Click to collapse
That's not a ROM's fault. Go into Chrome Settings and change it.
TheArt. said:
I'll try it right now, but I can't find your custom setup for the stock of "Open-GApps" which you mention in the FAQs. I already applied to the Google+ Community, but I've to wait.
Thanks
EDIT: I found it, probably i misunderstood that this gapps package was personalized by you, hence I wasn't able to find it.
EDIT2: I flashed latest supersu 2.67, quantaV10 and nano gapps; So I may have problems with Layers because of supersu, right? that's what I understand from FAQs.
Click to expand...
Click to collapse
Which FAQs? I guess you mean both mine & Bitsyko's. This advice was given mainly to the newer nexuses (these are the ones over-reporting problems with systemless and layers). I have used systemless in the past and I had no problems. Right now, I have installed it on system (so it survives dirty flashes). You can do it in SuperSU settings.
I am using the ROM till morning and so far really great. I have only one wierd problem. Hangouts app is starting too long (compared to Chroma for example). I mean, on Chroma its like 2 sec, on Krexus its like 4 sec. Any ideas? I am using Quanta kernel.
######################################
This is NOT the Freedom OS that became known with the OP3/3T devices
recently. This is pure stock LG plus some alternative Google apps. It's
name comes from the fact that the installer will give you full access to
choose what you want to flash to your device !
######################################
{
"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"
}
DO NOT COPY MY WORK WITHOUT PERMISSION
IF YOU DO MODIFY IT, AND WOULD LIKE IT INCLUDED, CONTACT ME
YOU WILL BE REPORTED IF YOU ARE CAUGHT SHARING THIS AS YOUR OWN PROJECT
I'M NOT RESPONSIBLE FOR BRICKED DEVICES. THE ROM DOES NOT MODIFY CRUCIAL LG FILES
Freedom OS v1-4 is MM based
Freedom OS v5 + is N based
FEATURES:
Passing SafetyNet Check | Do NOT disable Logcat to pass SafetyNet Check [Installer Option]
H815|H811 29a-20v-30b Stock Base.
Legacy Support for Substratum and OMS with Magisk Module ( if the theme creator has included such modifications )
Rooted only if you choose it
Lower and different LED light upon touch to reduce useless battery drain
Improved Speakers volume
Auto-Trim all disks on every ROM or GAPPS package update
I/O Tweaks, CPU Tweaks, Kernel Tweaks, pre-installed
System mount filesystem performance tweaks
Wakelock blocker
Flash it to find out more....
SCREENSHOTS:
Screenshots folder
INSTALLATION GUIDE:
its absolutely crucial to have the latest TWRP BETA release or the latest beta from my Android File Host
Download the latest build
Reboot to TWRP (Keep your TWRP up-to-date cause i use the latest updated installer)
Install the Rom using adb sideload or If you downloaded it directly in your phone, just install it by tapping the Install in TWRP and navigate-select the rom.
Aroma installer will guide you through.
Reboot.
You will have to wait a few minutes. On 1st boot it will cache all the apps.
ISSUES:
No WiFi Calling
No Volte
Tethering currently not working
DOWNLOADS:
LG G4 H811
THANKS:
@Chainfire - SuperSU
@topjohnwu - Magisk
@renzetti.s - For the LG G6 Launcher
@TecknoFreak - Porting H815 Freedom ROM to work with H811
@kessaras - Thank him for taking the time to make FreedomOS and for anything else!
DONATIONS:
@seetru,@HorstiG - Much Appreciated !
XDA:DevDB Information
[H811][N]Freedom Rom v7.5, ROM for the T-Mobile LG G4
Contributors
TecknoFreak, Kessaras
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LG Stock
Version Information
Status: Testing
Current Stable Version: 3 +
Stable Release Date: 2017-11-11
Created 2017-11-12
Last Updated 2017-11-12
For future announcements
One more just in case
install went well, no bloat and fast - I remember you from g stylo days
VoLTE and Wifi calling work I presume?
thejaredhuang said:
VoLTE and Wifi calling work I presume?
Click to expand...
Click to collapse
VoLTE and wifi calling are not supported in any N Rom Stock based or not.
Basmatek said:
VoLTE and wifi calling are not supported in any N Rom Stock based or not.
Click to expand...
Click to collapse
It is supported on my G6 port but you need to do an entire modification from hidden menu. Not worth me trying to write a tutorial guide on how to do it as is been so long working on that Rom I gave up making a flashable zip to fix it but no success that way. On my back up still work though
Thank you for all the hard work on this ROM. Quick question.
Phone works great but it information section about the phone it says Baseband Unknown. Phone works but anyway to fix this to show correct baseband version ?
stewie-droid said:
Thank you for all the hard work on this ROM. Quick question.
Phone works great but it information section about the phone it says Baseband Unknown. Phone works but anyway to fix this to show correct baseband version ?
Click to expand...
Click to collapse
no unless LG releases N to the US. dont worry we all have unknown
Thank you. I think i found a bug unless i'm not aware of it.
This rom won't recognize sdcard. Its asking to format it which i don't want to do, have lots of data on it. It won't recognize it (it works fine on 6.0 rom) unless it's formated. Any suggestions?
Also question
I think i see the answer. Base is v30b so it's based on lg g4 libs, not G6. I got confused with all this porting lingo. I'm hoping it's not G6 libs. I would want pure G4 code.
https://www.androidsage.com/2017/07...-nougat-firmware-update-download-and-install/
stewie-droid said:
Thank you. I think i found a bug unless i'm not aware of it.
This rom won't recognize sdcard. Its asking to format it which i don't want to do, have lots of data on it. It won't recognize it (it works fine on 6.0 rom) unless it's formated. Any suggestions?
Click to expand...
Click to collapse
This has been happening off and on after upgrading Android for some time. It appears to be fairly common (universal?) when upgrading to Nougat. I don't think it's a characteristic of this ROM.
You need to copy the data from the sd card to a pc via a card reader, format the card in the phone, and copy the data back.
---------- Post added at 03:52 PM ---------- Previous post was at 03:50 PM ----------
Thank you for your work on this. I have decided to keep my (LG repaired) G4 H811 for a while longer because nothing "better" seems worth the investment at the moment.
I have a couple of minor suggestions:
1) Let people know in the op that they need to flash GAPPS.
2) Warn them that it is very possible their SD will not be readable on first boot.
3) On my install, after Aroma had finished with the ROM it asked me if I wanted to install Busybox. I said, "Yes," but the "extraction" phase got stuck at 30% for some time before I removed the battery. Then the phone started with the upgraded OS uneventfully.
channeledbymodem said:
This has been happening off and on after upgrading Android for some time. It appears to be fairly common (universal?) when upgrading to Nougat. I don't think it's a characteristic of this ROM.
You need to copy the data from the sd card to a pc via a card reader, format the card in the phone, and copy the data back.
---------- Post added at 03:52 PM ---------- Previous post was at 03:50 PM ----------
Thank you for your work on this. I have decided to keep my (LG repaired) G4 H811 for a while longer because nothing "better" seems worth the investment at the moment.
I have a couple of minor suggestions:
1) Let people know in the op that they need to flash GAPPS.
2) Warn them that it is very possible their SD will not be readable on first boot.
3) On my install, after Aroma had finished with the ROM it asked me if I wanted to install Busybox. I said, "Yes," but the "extraction" phase got stuck at 30% for some time before I removed the battery. Then the phone started with the upgraded OS uneventfully.
Click to expand...
Click to collapse
Ultimately I could not use this ROM on an unmodified T-Mobile H811, nor could I use any of the developer's variations on a H811 nougat port: the sd card problems persisted off and on and all of the ROMs had problems with 4G LTE data in New York City. Too bad.
Fortunately, for those who may be wondering it is possible to downgrade back to stock LG marshmallow. I would use the latest carrier version, which as of Nov 2017 is 20v. Flashable versions of it are available on XDA.
Ok i've been daily using this rom and besides things mentioned things are working ok.
Pros:
This stock rom is 2 times more smooth then 6.0. I'm assuming it's due to not having so much skin over android build which i love fluidity btw.
MM stock 6.0 was so sluggish. I love pure vanilla andoid experience but can't run those as need stock roms for most part and this one is stock and fluid like N roms.
Also available memory and it's management is way better as it has 700-400mb of more free ram then MM 6.0 stock. I run same apps.
Battery usage is also minimal while asleep, flat line, same as in LineageOS with interactive kernel. I use kernel-auditor-mod apk
Question regarding busy box. It seems it has custom busybox installed 1.26.2-osmOsis. Should this busy box be left alone as it helps in some custom features/settings or can it be updated if one has latest busybox. Don't wanna screw up fluidity of this rom so asking. Not sure if this custom busybox does something custom?
Issues:
No WiFi Calling - needs to be switched off in settings
No Volte - needs to be switched off in settings. It's on be default
Tethering currently not working - never use it as my plan is limited
Sd card recognition fails with sd card corrupted - didn't bother to fix it be format yet
Microphone Block app if anyone is using it it currently will block mic of phone conversations of this rom phone.apk so don't use it. Not a big deal but i thought i would mention it to help ppl out if some ppl are using it for privacy.
This wasn't an issue on MM nor on Nougat LineageOS so this is issue that either needs to be resolve by developer of that app or maybe within this rom excluding this app Microphone Block by BytePioneers from blocking phone.apk https://play.google.com/store/apps/details?id=com.bettertomorrowapps.microphoneblockfree&hl=en
Seems like there is no traction with this rom as very limited posts i see here. Hope it won't die out as this is best rom sine LP 5.1 release. MM 6.0 was a flop IMO, kinda like windows Vista between release lol
downloading this. will flash it later today and report back if there are any issues apart from one in OP.
Thanks OP for getting stockish ROM for H811 with TMobile dropping the ball on us.
so far so good. haven't run into any issues so far.
stewie-droid said:
Ok i've been daily using this rom and besides things mentioned things are working ok.
Pros:
This stock rom is 2 times more smooth then 6.0. I'm assuming it's due to not having so much skin over android build which i love fluidity btw.
MM stock 6.0 was so sluggish. I love pure vanilla andoid experience but can't run those as need stock roms for most part and this one is stock and fluid like N roms.
Also available memory and it's management is way better as it has 700-400mb of more free ram then MM 6.0 stock. I run same apps.
Battery usage is also minimal while asleep, flat line, same as in LineageOS with interactive kernel. I use kernel-auditor-mod apk
Question regarding busy box. It seems it has custom busybox installed 1.26.2-osmOsis. Should this busy box be left alone as it helps in some custom features/settings or can it be updated if one has latest busybox. Don't wanna screw up fluidity of this rom so asking. Not sure if this custom busybox does something custom?
Issues:
No WiFi Calling - needs to be switched off in settings
No Volte - needs to be switched off in settings. It's on be default
Tethering currently not working - never use it as my plan is limited
Sd card recognition fails with sd card corrupted - didn't bother to fix it be format yet
Microphone Block app if anyone is using it it currently will block mic of phone conversations of this rom phone.apk so don't use it. Not a big deal but i thought i would mention it to help ppl out if some ppl are using it for privacy.
This wasn't an issue on MM nor on Nougat LineageOS so this is issue that either needs to be resolve by developer of that app or maybe within this rom excluding this app Microphone Block by BytePioneers from blocking phone.apk https://play.google.com/store/apps/details?id=com.bettertomorrowapps.microphoneblockfree&hl=en
Seems like there is no traction with this rom as very limited posts i see here. Hope it won't die out as this is best rom sine LP 5.1 release. MM 6.0 was a flop IMO, kinda like windows Vista between release lol
Click to expand...
Click to collapse
The problem with all those issues is that this a modified Rom from other countries like Korea and or International variants where any of those features sadly dont work. Is a been a pain in the butt to port such features.
Has anyone tried the Titan kernel on this rom?
@TecknoFreak 20x came out for the H811, any plans to update v4 to it?
thejaredhuang said:
@TecknoFreak 20x came out for the H811, any plans to update v4 to it?
Click to expand...
Click to collapse
What is 20x? Can you provide link to it?
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:
If you find any bugs, bring a logcat. Logs are helpful....
If your problem cannot be reproduced without using Root modules or Xposed, don't report it! The same goes with custom kernels.
Not working:
Camera or Video recording
Encryption not working in TWRP
Data
Prerequisites:
The latest version of TWRP. This is an absolute requirement.
Your device (it better be a Galaxy Tab 3 7.0 (Sprint)).
How to flash this ROM:
So you really want to do this, huh? That must mean you accept the risks specified in the disclaimer, and that you read the warning.
From other custom ROMs (this assumes you already unlocked your bootloader a long time ago):
Download the zip file for your device (link is below).
Reboot into TWRP (Volume Up + Home + Power or Advanced Restart).
Make a backup (optional).
Perform a factory reset (Wipe > Swipe to Factory Reset).
Flash the ROM you just downloaded.
Flash OpenGApps for Android 8.1 if you want Google services (optional).
If you want root, flash Magisk or SuperSU
Reboot and proceed normally with installation.
Download links:
TWRP:https://drive.google.com/open?id=1SobBqwJ4blOBUwJRQhRbSngqli-GQOd4
Rom: https://drive.google.com/open?id=1-KmqmWPjX1CcS31llPttYkJkG61uY7zC
OpenGApps 8.1: https://drive.google.com/open?id=1te8P364JcVnlItY-r74a8CbkP4jAj85Q
Source code:
LineageOS on GitHub
Credits:
The LineageOS Team
TeamWIn
Special Thanks: @DarkFrenzy @captainthrowback @Dees_Troy @noahajac @LuK1337
Anyone i forgot to mention
Very Special Thanks: @arco as alot of my changes are based upon his Github upstream changes on serranoltexx, expecially on RIL. Without this project would not be possible.
Version Information:
ROM OS Version: Android 8.1 Oreo
Kernel Version: Linux 3.4.x
Sent from my SM-T217S using Tapatalk
IThinkALot said:
Android Oreo on a 5 year old device? You're awesome dude.
Sent from my Xiaomi Redmi Note 4 using XDA Labs
Click to expand...
Click to collapse
Thanks. Haha it wasn't a easy task. Took me about 2 months of tinkering and playing with it. I am personally using the device at the moment.
Sent from my SM-T217S using Tapatalk
slashez said:
That’s so impressive. I don’t want to sound unappreciative but can you please do it for the tab 3 8.0. [emoji1391]*[emoji1391]*[emoji1391]*[emoji1391]*
Click to expand...
Click to collapse
Thanks. Problem with that is I don't have the device on hand, so that's problematic in building and testing.
Sent from my SM-T217S using Tapatalk
sscsps said:
Wow dude! Awesome work!
---------- Post added at 08:40 AM ---------- Previous post was at 08:40 AM ----------
When will you be sharing your trees?
Click to expand...
Click to collapse
Thanks. Ya I was going to try to get the camera working before I dropped my self made trees.
majorkid said:
Thanks for the ROM ..
Click to expand...
Click to collapse
Welcome
The0919 said:
Can I flash this on my T210R Tab 3?
Click to expand...
Click to collapse
Different hardware
wtjra70 said:
You sir has restored my love in this little bugger the SM-217S. I found it a couple of months back hiding in a drawer. I figured I'd use it when I'm watching YouTube in bed. I've been on Resurrection Remix 7.1 and could believe it was so slow. Now this thing is has new life in it again.
Click to expand...
Click to collapse
Welcome.
Robsr said:
since i.m no technician or a computer whizkid i.ve to look up on these kind of threads for a good rom
so i dare asking you if you are willing to make a rom for a Samsung Tab 3 lite SM-T110. My wife uses this and its very, very slow on the stock rom.
thnx a lot
rob
out of the Hague Netherlands.
Click to expand...
Click to collapse
Problem is different hardware. And I don't have that tab on hand to debug issues.
Sent from my SM-T217S using Tapatalk
Thank you for cooking this ROM and interest in making the camera work. I know you use it as WiFi tablet only. I still can't get Sprint data working as was the case with earlier serranoltexx-based builds.
Looking forward to any updates you may provide. Best wishes...
Version Information:
ROM OS Version: Android 8.1 Oreo
Kernel Version: Linux 3.4.x
Click to expand...
Click to collapse
residentorca said:
Thank you for cooking this ROM and interest in making the camera work. I know you use it as WiFi tablet only. I still can't get Sprint data working as was the case with earlier serranoltexx-based builds.
Looking forward to any updates you may provide. Best wishes...
Click to expand...
Click to collapse
Can you take some logs when you insert your sim, and try to toggle data?
lazumo said:
I'm guessing a kernel for Lineage OS 15.1 wouldn't work with Lineage OS 14.1 ? I'm not ready to make the leap onto Oreo yet, but I'll be damned if I can find a good, non-stock kernel for LOS 14.1 on my SM-T217S. I've tried repeatedly to compile my own from all the sources that are readily available, but the OS just hangs saying that Lineage OS is starting... and that's just the stock source with the specific commits for this device. I can't figure out if it's the toolchain I'm using or what.
Thanks for the time and effort that you've put into this, though. Having begun to try to do this kind of thing myself has really given me a new appreciation for the work that you and other XDA members do. Hopefully one day I'll be compiling my own ROM builds for y'all too.
Click to expand...
Click to collapse
Kernel source compiles based upon device. The kernel from 14.1 or 15.1 should be interchangeable. If the ROM boots to the initial screen then its probably not a kernel issues but another issue why it won't boot. You have to take a adb log and look at the output to determine why its hanging.
residentorca said:
With SIM inserted I see a persistent notification atop the notification panel that says No SIM card - No service. When I remove and re-insert the SIM, the message remains. Because of this I am unable to toggle cellular data on and off using the status bar Mobile data switch or in Settings-Mobile Network. All items are greyed out under Settings-Mobile Network. When I access the "Testing" menu by dialing *#*#4636#*#* and then select Tablet Info I am unable to Enable Data Connection. I recall that after the first boot after flashing your ROM the Cellular setup wizard never started even after removing and reinserting the SIM card. I don't think this is relevant but I did not flash any GAPPS package. I did flash the file 2016.02.08 Freedompop_APNs_fix.zip which I obtained from a different thread and has worked on other ROMs. My SIM is for FreedomPop which uses the Sprint data network. I did collect logcat and Bug Report files to share with you if you think they may help. Let me know if I may provide any additional information. Thanks!
Click to expand...
Click to collapse
Thanks I will take a look at the logs. Ya I don't have a sim to insert maybe I can find a friend who has a old one lying around. Did the sim show inserted on my previous build?
residentorca said:
Thanks, the SIM did not show on the previous build either.
Click to expand...
Click to collapse
OK cool. I will work on getting that sorted. Wish I knew that before lol. Currently trying to get the camera to work. Thanks though.
I have this exact tablet version, but does this work for serranolte?
Nice job on the rom too bad i dont have the right device model to test but anyways its awesome to see development for samsung tablets especially oreo
TurnaboutSavage said:
I have this exact tablet version, but does this work for serranolte?
Click to expand...
Click to collapse
It might work if you flashed a custom kernel but the blobs are slightly different so idk the answer. It would be up to you, I can't provide support as I don't have that device.
JT1510365 said:
Nice job on the rom too bad i dont have the right device model to test but anyways its awesome to see development for samsung tablets especially oreo
Click to expand...
Click to collapse
Thanks, I figured I would give it a try, this is my first build for this device specific.
Can i flash this on T210??
Voyage Maker said:
Can i flash this on T210??
Click to expand...
Click to collapse
Different hardware.
Sent from my SM-T217S using Tapatalk
residentorca said:
Thanks, the SIM did not show on the previous build either.
Click to expand...
Click to collapse
So I been looking at the radio files I used. I am thinking they would work. But they were made for a different device but do work with serranotexx which I assumed would be work with this device. Obviously I believe this is the issue, I will try to do a rebuild semi soon to see if I can sort that out. The hardware is slightly different between the s4 and this.
Sent from my SM-T217S using Tapatalk
Does the Rom work on sm t110?
user325 said:
Does the Rom work on sm t110?
Click to expand...
Click to collapse
Different hardware.
Sent from my SM-T217S using Tapatalk
Not Working
It's not working for me, I'm on the Samsung galaxy tab SM-T217S (Sprint). When I try to flash it with TWRP, it says:
Installing zip file
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
Warning: No file contexts
E3004: This package is for device: lt02lte, lt02ltespr, lt02ltetmo; this device is .
Updator process ended with ERROR: 7
Error installing zip file
Updating partition details. . .
. . .done
Edit: FIXED, I edited the file and removed the version verification.
Justsnoopy30 said:
It's not working for me, I'm on the Samsung galaxy tab SM-T217S (Sprint). When I try to flash it with TWRP, it says:
Installing zip file
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
Warning: No file contexts
E3004: This package is for device: lt02lte, lt02ltespr, lt02ltetmo; this device is .
Updator process ended with ERROR: 7
Error installing zip file
Updating partition details. . .
. . .done
Am I doing something wrong?
Click to expand...
Click to collapse
Reread the first page. Latest version of twrp is an absolute requirement.
Woodbuger said:
Reread the first page. Latest version of twrp is an absolute requirement.
Click to expand...
Click to collapse
I was on the latest version of TWRP.