Related
Gentlemens,
Goo.im site is in the process of improvement.
Technical support goo.im site works on the physical replacement of all servers to increase the download speed and stability. Besides replacing servers is also working on network gears.
So, be patient and do not ask questions about GOO.IM site on the developers Threads will not be announced until the completion of upgrade.
I know you want to download gapps ROMs like CM10, CM10.1, CM10.2, PAC or Paranoid Android, but you must have a little patience. I understand that during this week the process will be completed.
Source: https://twitter.com/GooInsideme
UPDATE 07.11.2013
Status Update!
- All servers are online and running normally. We're seeing much faster downloads for users across the board with room to spare, compared to our old setup!
- Missing files are being restored from a backup. We had done a preliminary sync before installing the new servers, however it seems that during the migration there were some file system issues, and we're restoring from the old system. Developers, if you have backups, please feel free to rsync them to your folder to speed things along!
- The file indexer is now working normally after some hiccups. There's a bug regarding deleted files not being dropped, but +Alex Blair is working on it.
- Sponsor sign-ups are once again working. There was an issue with the site's code that made a few assumptions and stopped sign-ups from being processed.
- We are processing all of the sponsor-related emails we have received. +Denham Crafton will be responding to the emails tonight and tomorrow. If you do not hear from him by Thursday afternoon (PST), then please send an email to contact at snipanet dot com and include your PayPal confirmation/transaction number so we can get your account straightened out!
- EDIT: GooManager sign-in issues have been resolved. The issue was caused by GooManager using our old domain, Goo-Inside.me, to access our API. We fixed the DNS records for that domain, and as soon as your DNS resolver updates (within 24 hours) GooManager should work fine once more.
Click to expand...
Click to collapse
ROMs like CM10.1, CM10.1, PAC or Paranoid Android
Click to expand...
Click to collapse
CM10.1 twice
Thanks for info.
Update OP.
I guess soon we will have all ROM's back.
Update OP.
I guess soon we will have all ROM's back.
So can anyone please upload 4.2 gapps on dev host please? I need it right now
Edit. Found.
http://forum.xda-developers.com/showpost.php?p=47244660&postcount=627
What's new in the update?
[email protected] said:
What's new in the update?
Click to expand...
Click to collapse
Goo.im is file host site. They are changing server.
Sent from my GT-I9070 using Tapatalk
Almost done with upgrading.
Few steps to finish all jobs and restore all backups.
I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.
Click to expand...
Click to collapse
READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:
doesn't work as a result of flashing this;
initiates a nuclear meltdown, or;
doesn't permit your alarm clock to function normally.
By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.
Click to expand...
Click to collapse
Downloads:
click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)
Features:
[*]Compiled with UBERTC 4.9
UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
based on CM13
more to come!
Known issues in post #2
Changelog in post #3
Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.
Credit where credit is due
@Hashcode, because we wouldn't have CM on our kindles at all without him.
@BuQQzz for some mentoring & advice
@transi1 for porting CM13 and providing some useful fixes for build errors
XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD
Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-29
Last Updated 2016-08-07
Known issues
Bugs affecting all CM13-based ROMs on the kindle
Screen artifacts when playing video from Snapchat, Vine, etc.
Audio chops in and out often
Other bugs currently afflicting the other CM13 ROMs for this device
Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
Play Store & Setup Wizard FCs
CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)
Changelog
08/07/2016
experimental backtracking to kernel 3.0.84+
July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
07/01/2016
doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
reverting from UBERTC toolchains to native CM/AOSP one
05/20/2016
defecting to BlissRoms-Devices GH for newest device config files
05/2016 security patches from AOSP, et al.
04/27/2016
refreshing CM sources & obtaining latest sources from transi1
04/09/2016
revert the 4/4 kernel reversion; back to 3.0.101(+)
carry in latest edits from transi1 to try to fix the camera
04/04/2016
revert to kernel 3.0.72+
first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
03/29/2016
initial build!
Roadmap
The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.
Layers/RRO theming support
Custom boot animation (or at least one scaled to the kindle's screen size)
Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
Publication of a custom .gapps-config file for use with opengapps packages
I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.
So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.
Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.
Some updates...
I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.
More updates...
It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:
I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.
Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.
Finally, some planned changes:
I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
Obvious name change in the ROM, mentioned earlier.
Replacing CM's theme engine with RRO(?)
CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.
Good version,thanks. But it often wifi reconnect , can it fix?
wizard_mini said:
Good version,thanks. But it often wifi reconnect , can it fix?
Click to expand...
Click to collapse
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
monster1612 said:
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
Click to expand...
Click to collapse
It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time
Android system cost battery drain more than screen, is it normal?
wizard_mini said:
Android system cost battery drain more than screen, is it normal?
Click to expand...
Click to collapse
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
wizard_mini said:
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
Click to expand...
Click to collapse
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
sirp0p0 said:
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
Click to expand...
Click to collapse
It's a good solution,, I fix it, thanks
monster1612 said:
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
Click to expand...
Click to collapse
I use 4hours screen on and 7hours screen off cost 92% battery.
wizard_mini said:
I use 4hours screen on and 7hours screen off cost 92% battery.
Click to expand...
Click to collapse
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
monster1612 said:
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
Click to expand...
Click to collapse
Thanks. I am expecting it!
Hi everyone,
I got my mako in apr 2013. Apparently, on cm12/13 it seems to be affeected by this bug. So, to clear any doubt about it, I wondered if downgrading to kitkat might help in general.
Even if the battery gain was to be dramatically high, security is my first corcern. The last
Android security bulletins (ASB) contain a lot of critical bugs; anyway from them I discovered that kitkat still get security updates from google and from CMxLog that someone still add to about page that cm11 is updated to respect the "MM YYYY ASB". I trust cyanogenmod in that.
So since I never tried to compile aosp and as this rom wasn't updated in a while, I synced cyanogenmod repos and I compiled it with the instructions on cyanogen wiki.
The rom is good and stable.
As you can see from the screenshot below, without gapps, with major instant messengers (whatsapp, telegram-foss with smart push disabled) and email push notifications (k9 mail), battery drain on idle is basically non-existent:
I wanted to share this build with you because I think this is an amazing community.
I plan to update this rom every time an ASB comes out (once in a month, as long as google keeps supporting kitkat).
Zio Guiduccio
NB: If you can't open Messages, flash first june rom, then august one.
26/08/2016
I made available a second build (FOSS) with some little differences. Here they are:
- Replaced Browser with getChromium app, because zero-day exploits in kitkat webviews (use only updated chromium!);
- Replaced Email with K9-mail, because kitkat webview and zero-day exploits;
- Removed Exchange2 because zero-day exploits (don't know alternatives othen than normal gmail);
- Added F-Droid;
- Added Offline Calendar, otherwise standard calendar is useless;
- Added Adaway;
- Added Document Viewer (many formats reader);
- Added Kolab Notes;
- Added Yaab (Minimum brightness on-demand).
Download
CM-11-20160820-GUIDUCCIO-FOSS-mako.zip
CM-11-20160820-GUIDUCCIO-mako.zip
CM-11-20160611-GUIDUCCIO-mako.zip
Just as you mentioned battery drain has lowered.
Thanks for ROM!
zio guiduccio said:
Hi everyone,
I got my phone in apr 2013. Apparently, on cm12/13 it seems to be affected by this bug. So, to clear any doubt, I wonder if downgrading to kitkat might help in general.
Even if the battery gain was to be dramatically high, security is my first corcern. The last
Android security bulletins (ASB) contain a lot of critical bugs; anyway from them I discovered that kitkat still get security updates from google and from CMxLog that someone still add to about page that cm11 is updated to respect the "MM YYYY ASB". I trust cyanogenmod in that.
So since I never tried to compile aosp and as this rom wasn't updated in a while, I synced cyanogenmod repos and I compiled it with the instructions on cyanogen wiki.
The rom is good and stable.
The only change I had to do was to replace these files
/system/framework/webview
/system/framework/webviewchromium.jar
/system/lib/libchromium_net.so
/system/lib/libwebviewchromium.so
/system/lib/libwebviewchromium_plat_support.so
with ones from cm-m12-official because logcat tells me that the webview i compiled goes segfault when I try to open messages in mms.apk, k9 mail and settings in rar and amaze. In general, the code is untouched.
As you can see from the screenshot below, without gapps, with major instant messengers (whatsapp, telegram foss with smart push disabled) and email push notifications (k9 mail), battery drain on idle is basically non-existent:
I wanted to share this build with you because I think this is an amazing community.
I plan to update this rom every time an ASB comes out (once in a month, as long as google keep supporting kitkat, which I hope is long).
Obviously, the ROM is updated to the latest android security bulletin of 1st june 2016.
Zio Guiduccio
Download
MD5SUM: 4B129774050768E8D21114D7816A8D56
CM-11-20160611-GUIDUCCIO-mako.zip
Click to expand...
Click to collapse
Hi,
Is there any chance you've updated this for the July ASB? Might give it a shot if you haven't
(And thank you, this is freaking awesome!)
Just a quick question, but can you download Pokemon GO from Play Store when using this ROM?
thegodsmustbecrazy said:
Hi,
Is there any chance you've updated this for the July ASB? Might give it a shot if you haven't
(And thank you, this is freaking awesome!)
Click to expand...
Click to collapse
Sorry. The day cyanogenmod mantainer approved the patches (31th july) I went away from home (and the building machine.) I will come back next week at minimum. I'll publish next build for 15th August at maximum.
EDIT: Still no july patches merged to cm11 branch.
espionage724 said:
Just a quick question, but can you download Pokemon GO from Play Store when using this ROM?
Click to expand...
Click to collapse
Can't see why non.
The rom has been updated to August 2016 ASB.
zio guiduccio said:
The rom has been updated to August 2016 ASB.
Click to expand...
Click to collapse
Thank you!
I'm running this with my n4 underclocked at 700mhz (might bump it up to 1ghz, but I haven't really noticed any crazy lag to speak of) and the battery life must be at least double! Freaking awesome if you ask me :good:
zio guiduccio said:
The rom has been updated to August 2016 ASB.
Click to expand...
Click to collapse
In your OP, you mention running this ROM "without gapps." Is the ROM designed to be run only in a state that is without any gapps package, or is it OK to use a gapps package if we want? I would use Open GApps for KK 4.4.
Of course you flash KK gapps.
{
"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 12.1 is a free, community built, aftermarket firmware distribution of Android 5.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
The following CyanogenMod 12.1 builds are based entirely on CyanogenMod code. Please refer to the official XDA thread for CM-12.1 on the LG G2 for basic information on installation and usage. It has the same requirements. It has many of the same limitations, except for those expressly listed updates listed in the Changes list below.
Why are you doing this, why do I want these builds?:
The last release of an OS from LG for the G2 was Lollipop. Since we need to use the proprietary binaries from LG to make our devices functional, and since CM-12.1 is based on Lollipop, the 12.1 release of CyanogenMod is regarded as the most stable for our device simply because they function natively at similar API levels.
Sadly, the LG G2 was one of the very first devices transitioned to the Marshmallow release of CM (CM-13.0) and it's never been quite the same since. The last official 12.1 nightly for most G2 devices is from November of 2015, and since then there have been many stabilizations to the CM-12.1 code base, as well as many security patches from Google. Therefore I thought it would be important to offer people the ability to run a more recent CM-12.1 nightly, rather than force them to transition to CM-13.0 in order to be up to date. And since CM-12.1 is not really changing, except for Google security level patches, I can make this offering once every few months without leaving people to far behind.
These builds are based entirely on CM source code. They are, for all intents and purposes, official CM-12.1 nightlies for the G2. I did make a few very small, but important changes that I thought most people would benefit from. Namely I backported the Snap camera from CM-13.0, as well as fixes to the IR Blaster permissions (so it'll work without having to switch to permissive mode) and changes to the volume that most people were constantly asking for. These builds are what CM-12.1 would have looked like had we waited a few months for CM-13.0 to become mature.
You should know that I built this originally for my mom and a friend of mine. I do not run this on a daily basis. You should consider support relatively non-existent, except for the help you get from the other people on the forums.
Changes since Official 2015-11-17 CM-12.1 Snapshot, About these builds:
Official CM-12.1 sources
Current as of 20161114
October 1, 2016 Android security patch level
CVE-2016-5195 (Dirty COW) kernel vulnerability fix (change 170897)
Integrated CM-13.0 Snap Camera w/ working HDR mode
IR Blaster fixes (build 2016-06-14 or newer, change 149554)
Audio volume adjustments from cm-13.0 (build 2016-06-14 or newer, change 149563)
I DO NOT give any guarantees on this working. PLEASE make a full backup before installing this zip. This rom comes with ABSOLUTELY NO SUPPORT (that's right, I don't really care if it works or not). That being said, I hope it works for you and you enjoy it
Downloads:
All features, unless otherwise noted, are cumulative. It is safe to assume that if a feature is added to a release, all subsequent releases likely have that feature.
Final Build 2016-11-14: October 1, 2016 Security Patch Level
These builds incorporate the latest security patches for Lollipop (CyanogenMod 12.1) as of October 14, 2016. They additionally incorporate a fix for the Dirty COW vulnerability. And since it seems the CM builds are over for CM-12.1, I ran a build for the ls980 as well. These are my final builds for this ROM. I will not be releasing any more after this.
d800: 1e2b77f689f1812e05cbc6cce5f0e0a6
d801: 9845a9bbef8a1721b8dd90e962ecfda9
d802: 16edad3b455bcb39f2ae5f20a3b04842
d803: f2f5602c080973417f065048d9f6d2ef
ls980: efc40e09538a483af2af1373b66b3ea2
vs980: 4f1379e03b62875f42b0599b8490f6e7
Please reference the above md5sums when verifying downloads from other sites.
Download 2016-11-14 for d800, d801, d802, d803, ls980 and vs980.
Build 2016-08-19: August 1, 2016 Security Patch Level
These builds incorporate the latest security patches for Lollipop (CyanogenMod 12.1) as of August 19, 2016.
d800: c6161c397b4333010e1aa0bb799ebd11
d801: 94fc86c21677380cd68a2b8809133189
d802: 1633e4feb08ac3a003219153b70d1a63
d803: de0abb09091eff724f09db92bc3e782c
vs980: afce5b1e4e67ec7aafb5f16fb883d0d6
Please reference the above md5sums when verifying downloads from other sites.
Download 2016-08-19 for d800, d801, d802, d803 and vs980.
Build 2016-06-14: June 1, 2016 Security Patch Level
These builds add proper IR Blaster sepolicy changes for properly working IR. They also add audio volume changes to increase the device volume output.
Note: Some builds list the build date as 2016-06-15. The builds are all identical, they take a little over an hour to run each one, and the date changed between builds. I did not update my sources between builds, they are NOT DIFFERENT AT ALL.
IMPORTANT NOTE: This build contains a modified and BOOSTED mixer_paths.xml file. Please be careful when upgrading to adjust volumes. I am not responsible if you blow your speaker. These changes were made to CM-13.0 (change: 138749) and have been backported. They are assumed safe.
Download 2016-06-14 for d800, d801, d802, d803, ls980 and vs980.
Build 2016-03-28: March 1, 2016 Security Patch Level
The builds include the version of Snap included with CM-13.0. They also include a fix so HDR works with it (I don't believe my old Snap builds worked w/ HDR before).
Download 2016-03-28 for d800, d801, d802, d803 and vs980. No build was done for ls980 as it was still receiving CM-12.1 nightlies.
Build Usage Notes:
I DO NOT give any guarantees on this working. PLEASE make a full backup before installing this zip. This rom comes with ABSOLUTELY NO SUPPORT (that's right, I don't really care if it works or not). That being said, I hope it works for you and you enjoy it
I'm so confused! The last official nightly was from Nov-2015, how in the world could this be current?!?:
The CyanogenMod devs didn't stop developing on version 12.1 when we were transitioned to 13.0. There was a period of months where a group of developers started transitioning existing features and developing new features on CM-13.0, while another group worked to continue to stabilize and maintain the existing CM-12.1 codebase. Sadly, we were one of the very first devices transitioned to 13.0 at the very beginning of the 13.0 development. Therefore we never received a particularly solid 12.1 build.
These builds represent a nightly build from the continually developed 12.1 code base. It has a large number of fixes that have occurred (and, at a very slow pace now, continue to occur) from November of 2015 to the present. Additionally this build has all the monthly security patches from google. These are incorporated by CM, not me. With the exception of the Sprint(US) model of the G2 (the LS980), these builds represent the most up-to-date official builds of CM-12.1 for the G2 you will find.
What are the requirements and/or procedure for installing this ROM?:
These CM-12.1 builds are essentially the same as the official and nightly CM-12.1 builds. Therefore the requirements are the same. Please visit the Official CM-12.1 XDA Thread for information on the requirements and procedure on installing this ROM.
NOTE: This is my own personal recommendation. I HIGHLY recommend following the advice from the CM-13.0 builds: if you can, if you have the chance, backup your device and copy that backup and your phone data to your computer, then completely wipe your device. Do a full stock update (KDZ, TOT, forced OTA's, whatever) to bring your device up to stock LG Lollipop. From there, root the device, do the auto-rec, update TWRP to the latest from blastagator, and then install this ROM and a compatible Gapps package. I personally believe putting your device on stock lollipop firmwares will give you the best possible experience on a Lollipop ROM. And whatever you do, DO NOT USE BOOTSTACKS!!!
Flashing over official CM-12.1:
As stated above, these builds are essentially the same as the official and nightly CM-12.1 builds. They aren't substantially different enough to cause compatibility problems. They are simply updated builds with a number of fixes, and the only real added package is the Snap from CM-13.0. You *should* be about to simply flash this over an existing official CM-12.1 build (which I recently did over a 7-8 month old build with no ill effect).
That being said, if in doubt, do the appropriate backups and start fresh from scratch, restoring app data as necessary. Often times a fresh install can solve a number of odd problems and lead to a smoother experience.
I have a newer nightly, I just want the Snap camera:
If you are currently on the Sprint LG G2 (The LS980) you are already on the official CM-12.1 track, and any future official nightlies will incorporate the IR and Volume patches from my 20160614 builds. Otherwise if you like the nightly you're on and you really just want the snap camera, you can download them here:
Download: Snap camera for CM-12.1 G2 Builds
These zip files should be installed via the recovery. They are also persistent, you won't need to flash them every time you update the ROM. You will only need to re-install whenever you do a clean reset of the device. I will try to upload a new build of Snap whenever I build new snapshots.
Note about Snap builds: Because the Snap settings aren't integrated into the ROM itself, I don't believe these Snap builds will have working HDR. I'm not sure, but if it doesn't work there's nothing really I can do about it.
Can I safely use the CM Updater?:
In a word: No. The only exception to that is if you are on the LS980 device. The recommended way to update these builds is by manually downloading them and flashing them from TWRP (or your chosen recovery).
The CM Updater downloads updates from CM's official build system. For most G2 devices CM Updater will offer you CM-13.0 builds to update to. If you try to update to a CM-13.0 release through the CM Updater from CM-12.1, your device will cease to work. Your best bet (and my recommendation) is to go into the updater (Settings -> About Phone -> System Updates) and setting the update type to "Manual". That will keep the device from checking for updates. Another option would be to re-install your gapps and set it to remove the CM Updater all together.
If you are on an LS980 device, the CM build system is providing you relatively up to date builds. You should be able to use CM Updater to safely update from one of my releases to a newer official CM nightly without any trouble. The only thing you will lose is the Snap camera. In this case I would recommend staying with the official nightly and simply installing the Snap camera separately as mentioned above.
My device seems to be heating up:
User @mwedo on the official thread had a similar problem (click here to see). He tracked it down to the "OK Google" Hotword detection. After disabling it his device things returned to normal. I don't know why this happens, and I doubt it'll get fixed in my lifetime since 12.1 is no longer on the support track for us. However, I am mentioning it here for those of you experiencing a similar problem. I have also updated the gapps-config attachment that I posted below to disable the default Hotword enrollment. Hopefully that'll save people some headache. The gapps-config keyword is "Hotword".
IMPORTANT: Gapps / OpenGapps and Snap Camera:
If you use a modern-ish Gapps package, it may recognize Snap as the default CM camera and remove it. You should modify your Gapps config so that it does NOT do that. If you need to modify Gapp's behavior, you can wipe the system partition (do NOT factory reset), and then fresh install your ROM and Gapps (with any gapps-config modifications you need). I am attaching the gapps-config.txt file I use in conjunction with OpenGapps "Stock" release. Keep in mind it removes the built in Gallery to be replaced by Google Photos.
Thank you so much bro ???
Sent from my LG-D802 using XDA-Developers mobile app
Fuq yeah! Great news!
D801 version working great.
Mother of god @dr4stic, what have you done regarding the kernel?? This is the most supreme caching I've ever seen! Wow! This build is blistering fast on my D802 and it's multitasking like a boss!
I've yet to see a single bit of lag or jerky transitions but... WOW! I'm totally speechless, sick.
Stunning build! Thank you, thank you, THANK YOU!!
Coming from stock rooted 4.4 will I just need to flash bootstack? If going from CM12.1 back to stock 4.4 what is the process then? Really want to test this ROM
Sent from my LG-D802
zizuka said:
Coming from stock rooted 4.4 will I just need to flash bootstack? If going from CM12.1 back to stock 4.4 what is the process then? Really want to test this ROM
Sent from my LG-D802
Click to expand...
Click to collapse
If you're willing to, I'd HIGHLY (and I've been meaning to list this in the second post... which btw you should read), I HIGHLY recommend taking your device up to stock Lollipop from LG. Do the TOT's, KDZ's, force OTA's, whatever you need to do to arrive at stock LG lollipop. Then root and autorec from there. And then update to the latest blastagator TWRP and install this rom and a suitable Gapps. That should give you the best experience. This is a Lollipop ROM and even though it will theoretically work with a KK firmwares, it'll likely be more solid on LP firmwares.
Also, bootstacks are the devil. They are a crutch, the devs that make them don't even like them. We had so much trouble with it on CM-13.0, the troubles only went away when people did full stock restores and then rooted instead of using bootstacks. I know you won't, but you should read the FAQ for CM-13.0.
dr4stic said:
If you're willing to, I'd HIGHLY (and I've been meaning to list this in the second post... which btw you should read), I HIGHLY recommend taking your device up to stock Lollipop from LG. Do the TOT's, KDZ's, force OTA's, whatever you need to do to arrive at stock LG lollipop. Then root and autorec from there. And then update to the latest blastagator TWRP and install this rom and a suitable Gapps.
Click to expand...
Click to collapse
That's exactly what I did on the second run. By second run I mean that at first try I just flashed this build over the CM13 to see, or to be precise - to hear, improvements in sound. Sound is great tho! It's loud and clear and it's a joy to blast some nice beats through my Sennheiser headphones. Then flashed it "for real".
However, back to the point... For the first time ever I decided to bother with all that boring stuff; KDZ flashed latest version for my IMEI, rooted, TWRPed (lol word) to the latest version (3.0.2.1 IIRC), wiped everything including the internal storage (just b/c I prefer OTG), rebooted back to TWRP, flashed this marvelous 12.1 build, flashed stock (open)Gapps with some heavy tweaks in config file (removed a ton of that, something like you did @dr4stic but with a couple apps more or should I say less), wiped everything (except the system) once again, rebooted and... it's running like a champ! It's literally the snappiest and smoothest experience I've ever seen on the G2 and even my ex G Flex 2 can't beat this fluidity. Plus there's that insane RAM management without bothering to flash different kernels. It's so good that multitasking is a breeze. Dat multitasking ?
I seriously can't recall if there is any ROM that wasn't giving me some serious frustrations because I'm a professional nitpicker. Your latest build is the first one to achieve that and just when I thought it couldn't get better - this stellar beauty popped here ?
mwedo said:
I seriously can't recall if there is any ROM that wasn't giving me some serious frustrations because I'm a professional nitpicker. Your latest build is the first one to achieve that and just when I thought it couldn't get better - this stellar beauty popped here
Click to expand...
Click to collapse
I'm certainly happy you guys are enjoying this build as much as you are. Rashed hates when I get into a discussion with him about how unstable cm-13 is on the device, and that if I really thought it was stable I'd put my mom's phone on it, which I haven't done yet. CM-13.0 is stable, but it's stable in the sense that the phone won't catch fire and it consistently has the same bugs it's always had. But CM-12.1 for our device is simply rock solid. And that has to do with the fact that the last release from LG was for LP and that's where our proprietery binaries are from.
Rashed once told me something interesting... in theory the G2 and G3 could likely use the same RIL's. That's a pretty big deal because the RIL is the thing I find buggiest about the CM-13 release for the G2, and LG finally released native marshmallow to the G3. Also, PsychoGame and I were able to get LG's kernel for the G3 to build and boot quite easily for the G2. The only reason we never really released it was because there were a couple showstoppers with bluetooth and the vibrator driver. Other than that, everything worked beautifully. I'm gonna talk to some other devs and see if I can get a crash course on porting a RIL. I'm not quite ready to abandon this device yet... I'm close, but not just yet.
I remember Rashed talking about how we were moving to marshmallow really early, and I was all excited (I missed being on early releases when I had my Nexus). I later regretted that we didn't stay on Lollipop a little longer.
As for these builds, I otherwise did nothing to the build. It's just pure unadulterated CM-12.1 with Snap built in. I guess they did a good job after all. I hope you guys enjoy!
Is the old random vibration bug exist ?
Ok, i think i will flash this rom during the week end. The only thing that prevented me to flash an AOSP build is the fact that the camera doesn't have the photosphere option. Does this snap camera has the photosphere option? However thank you very much for this build!
KpKi said:
Is the old random vibration bug exist ?
Click to expand...
Click to collapse
No more, bro
Sent from my LG-D802 using XDA-Developers mobile app
[email protected] said:
Ok, i think i will flash this rom during the week end. The only thing that prevented me to flash an AOSP build is the fact that the camera doesn't have the photosphere option. Does this snap camera has the photosphere option? However thank you very much for this build!
Click to expand...
Click to collapse
If you want photosphere, install the Google camera from the play store. It isn't difficult, and it seems a bit much to avoid AOSP just for that feature. Otherwise no, snap doesn't have photosphere natively, neither does the native AOSP camera. But Google's camera from the play store does.
I have paired this build with Lambda kernel Domino (stable) and everything is working as it should. Give it a try.
Thanks a lot @dr4stic for the build.
dr4stic said:
If you want photosphere, install the Google camera from the play store. It isn't difficult, and it seems a bit much to avoid AOSP just for that feature. Otherwise no, snap doesn't have photosphere natively, neither does the native AOSP camera. But Google's camera from the play store does.
Click to expand...
Click to collapse
Yes, i've tried to download the google camera but i can't find it anywhere in the playstore.... However thank you for your response and for the rom!
Best ROM so far but one bug it over heats
Sent from my LG-D800 using Tapatalk
lox2013 said:
Best ROM so far but one bug it over heats
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Yes this is my observation too .
lox2013 said:
Best ROM so far but one bug it over heats
Click to expand...
Click to collapse
KpKi said:
Yes this is my observation too .
Click to expand...
Click to collapse
Try disabling everything having to do with "OK Google" voice detection. On the official thread, someone discovered that the cause of his overheating was because of the "OK Google" detection. You can try turning that all off and seeing if it makes a difference.
Google (the App) -> Press Hamburger Menu -> Settings -> Voice -> "OK Google" detection
On that screen, make sure all switches are turned off. Then, for good measure, reboot.
Then the play store stops I don't know why
Sent from my LG-D800 using Tapatalk
I made this ROM to test my build environment and I thought I would share it with the community in case someone finds it useful.
Find out more about AOKP here: https://aokp.co/
Sources:
Base ROM: https://github.com/aokp
Device trees and kernel: https://github.com/Exynos5433
My thanks to ripee and the exynos5433 team for supporting this tablet. Check out his thread for LineageOS which contains installation instructions and useful utilities which are also applicable to AOKP. https://forum.xda-developers.com/tab-s2/development/rom-lineageos-15-1-t3879302
Here is what you've been waiting for https://androidfilehost.com/?w=files&flid=296203
AOKP has Lineage SU baked in. If you prefer another root solution or don't want root then flash this immediately after flashing the ROM. https://mirrorbits.lineageos.org/su/addonsu-remove-15.1-arm-signed.zip
Heres a new build: latest upstream changes and security update
https://www.androidfilehost.com/?fid=6006931924117894736
thanks.
good to see t815 getting some love
Bug Wifi
With this last rom the wifi connection doesn't turn on, do you have the same problem? What should i do guys?
New builds being uploaded, now also available for the other tab s2 variants.
https://androidfilehost.com/?w=files&flid=296203
Flashed (clean) the latest for 715. I don't see any errors and all is working well... I use WiFi only so I can't confirm cellular data.
Google photos keeps crashing on T815
Google photos keeps crashing +1
T715Y
others work good by now.
Thanks a lot!
Select Google apps package without photos app and install it from play store. Works here! On 715.
Google Photos crashing seems to be an issue with opengapps. If you install the update to Photos from the Play Store, it starts working again.
How different is the T815 variant to the T815Y variant? I have a T815Y, am I able to use this ROM?
I have been using this as a daily driver for my 815 since your first build. thanks @Inkypen !
i took the liberty of forking your roomserice, i wanted to try to make an all in one build. not working so far, the remove frameworks av, didnt work.
ill keep digging. cheers
Tried flashing for the T810 and get error "E3004: This package is for device: gts210wifi,gts210wifixx; this device is ." and it fails.
Edit: Probably has to do with the old TWRP I use. Doesn't support newer versions, so I just edited the updater-script and it worked fine.
BeardKing said:
Tried flashing for the T810 and get error "E3004: This package is for device: gts210wifi,gts210wifixx; this device is ." and it fails.
Edit: Probably has to do with the old TWRP I use. Doesn't support newer versions, so I just edited the updater-script and it worked fine.
Click to expand...
Click to collapse
New twrp has been out for a while.
What mod did you make in the updater script and how.? Just curious to see your work around
New 710 and 815 up
Building 715 check in a little bit if it's uploaded.
Will do 810 after work
tripLr said:
New 710 and 815 up
Building 715 check in a little bit if it's uploaded.
Will do 810 after work
Click to expand...
Click to collapse
Android file host? Can't find new builds?
My build URL
ArtoD2 said:
Android file host? Can't find new builds?
Click to expand...
Click to collapse
Hi all , as i just started building these for myself from @Inkypen 's sources, I thought i would share the google drive link with everyone
tiny.cc/triplr
I will be updating my signiture
Note, I also build for the note 4 and there is some legacy tabs2 stuff im storing
download from the AOKP_oreo folder
thanks !
anyone else having constant (like, every 5 to 10min) drops? wifi stays on, it just disconnects everywhere and I have to manually select a network all the time, or wait a couple of minutes for it to automatically reconn
Dunno
Hi all.
Due to life issues( work )
And aokp not being used too much
I will be discontinuing builds.
Sources are still at
GitHub.com/exynos5433
Best wishes.