Related
This mod for CM11 on moto_msm8960 brings back the classic sdcard mount we know from devices like the Nexus One.
No more cluttering of /data with files which should go to sdcard.
Features:
- External sdcard mounted as /sdcard
- Internal memory fully available for /data
Installation:
- Have a nandroid backup of /boot and /system at hand if something goes wrong
- Simply flash the zip over your existing CM11 installation
- Wipe data is not necessary but will help if you have problems.
Deleting only the data of the concerned apps should be sufficient. (Only apps storing data on sdcard are effected)
- Files which were on the emulated sdcard can be found at /data/media/0. This is also the location where you have to put your zip files to be able to flash them with OpenRecovery.
Method:
Adjusting of following CM11 files to be in line with Nexus One example configuration according to:
http://source.android.com/devices/tech/storage/config-example.html
boot.img
- init.qcom.rc
- fstab.qcom
framework-res.apk
- storage_list.xml
See my github for details: https://github.com/S-I-M-O-N/android_device_motorola_moto_msm8960
Disclaimer:
This was developed and tested on a Photon Q but should work on all moto_msm8960 devices with CM11.
I cannot be held responsible if anything goes wrong while using this mod.
Thank you to everyone this work is based on: Cyanogenmod team for providing CM11, Google for providing Android and everybody else
Download
I will try to keep this thread updated and provide a flashable zip for the latest CM11 snapshot.
See attachment at the bottom.
Regards,
Simon
Downloads for:
cm-11-20140609-SNAPSHOT-M7-moto_msm8960.zip
cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip
cm-11-20140916-SNAPSHOT-M10-moto_msm8960_jbbl.zip cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip
cm-11-20141112-SNAPSHOT-M12-moto_msm8960_jbbl.zip
Cool, Thank you
Any updated version for CM11 M8 build?
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
S-I-M-O-N said:
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
Click to expand...
Click to collapse
Yeah..I've tried it over M8 and my phone stucked in bootloop. Thanks for your work. I've missed my sdcard as primary storage since JellyBean days. I'm glad I can use my 32gb sdcard usefully.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Download for M8 added.
S-I-M-O-N said:
Download for M8 added.
Click to expand...
Click to collapse
Thanks a lot..Downloading it now.
Hmm so I'm guessing the likelihood of this working on nightly builds isn't good?
You could give it a try.
Nandroid backup boot and system, then flash the mod.
If it screws up, just go back and restore boot and system.
Apart of that I think we should wait a few days to see if we get a moto_msm8960_jbbl M9 build. If yes I will, make the patch for it. If no, I will pick the latest nightly.
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Please...!
A new version.
The M10 CM is out now for the Photon Q!
S-I-M-O-N said:
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Click to expand...
Click to collapse
Download for M10 added. Have fun!
Download for M11 added. Enjoy!
Are there any issues with this mod when flashing a new ROM? Say you're going from a snapshot build to a newer snapshot build, or even from a snapshot build to to a stable build?
Flashing a new ROM will overwrite the mod. So you are using the emulated sdcard on internal memory. Apps which stored data on the sdcard will not find their data, just like when you install the mod the first time.
Nevertheless if you stick to CM11 snapshots for which the mod has been adapted and you flash another release, just flash the mod for this release while you are still in recovery and you will have no problems.
Made the mistake of installing a nightly restored my backup. But can't get the classic sdcard back. Have re flashed no joy. Is there a way to get it back, with out doing a clean install?
Did you create the backup including the mod?
Did you restore system and boot?
Did you try to just flash CM11 M11 + MOD for M11?
Do you have bootloops?
YDid you create the backup including the mod?
No
Did you restore system and boot?
Not sure about the boot, will check.
Restored backup m11 and flashed sddcard mod.zip.
Do you have bootloops?
No
Might be a mute point.
The restore is eating my battery!
Doing a clean m10 updating to m11 Now.
Will install sdcard mod and see how it goes.
Thanks.
I should know here in the next 15 min.
OK!
With out flashing sdcard mod after m11 installed I now have
4 gig.
My guess is my back up was not m11 or JB bootloader?
Thanks for the fast reply!
The PQ has no KK bootloader, so every (working) ROM for the PQ is based on the JB bootloader.
As long as you haven't modified your /system after updating to M11 and flashing gapps and sdcard_mod, you should be fine by just do the same again.
But it's always risky, from a nightly to a snapshot. Downgrades are also risky and might not work.
You might just wait until M12 comes out and use your backup to restore it.
M12 is here
Quick Camera Fix #1
Installation:
1. Download CM13 based ROM made by transi1
2. Open and replace files from temp_camera_fix_from_BEANSTALK_6.20.zip to the ROM of your choice respectively (flashing doesn't work)
3. Flash ROM, GApps etc.
4. After installation of ROM, install Open Camera or other 3rd party camera app
DOWNLOAD #1
temp_camera_fix_from_BEANSTALK_6.20.zip
Description:
This is basically a 3.0.72+ kernel from BeanStalk 6.20
IT WAS TESTED ON: RR 5.7.3, Bliss ROM
USING TWRP 3.0.2-1 WITHOUT TEMP_TOUCH_FIX
DOWNLOAD #2
temp_camera_fix_from_RR_5.6.5.zip
Description:
This is basically a 3.0.72+ kernel from RR 5.6.5
DOWNLOAD #3
temp_camera_fix_from_AICP_11.0.zip
Description:
This is basically a 3.0.72+ kernel from AICP 11.0
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
NOTE: Fix from BeanStalk 6.20 is updated (deep sleep issue fixed).
-------------------------------------------------------------------------------------------------------------------------------------------------
Quick Camera Fix #2
FLASHABLE ZIP
-------------------------------------------------------------------------------------------------------------------------------------------------
NOUGAT EMOJI FLASHABLE ZIP
-------------------------------------------------------------------------------------------------------------------------------------------------
OMNISWITCH FLASHABLE ZIP
-------------------------------------------------------------------------------------------------------------------------------------------------
THREAD CLOSED
Interesting workaround. If it works, it's even more evident that we're dealing with the 3.0.101+ kernel. I'm still planning on going through with that kernel backtracking to see which version or commit started this mess, and once I find it, report it so we can hopefully work through this. IIRC, those files were compiled against the 3.0.72+ kernel, so they might be a little old. Can someone try out the patch and see how it affects stability?
monster1612 said:
Interesting workaround. If it works, it's even more evident that we're dealing with the 3.0.101+ kernel. I'm still planning on going through with that kernel backtracking to see which version or commit started this mess, and once I find it, report it so we can hopefully work through this. IIRC, those files were compiled against the 3.0.72+ kernel, so they might be a little old. Can someone try out the patch and see how it affects stability?
Click to expand...
Click to collapse
2016/02/20 is the date of creation of last AICP. So, we need to find commits since that date and before.
alexander_32 said:
2016/02/20 is the date of creation of last AICP. So, we need to find commits since that date and before.
Click to expand...
Click to collapse
I already forked the repos prior to the post-3.0.72+ commits. I'll link in the manifest file I created if you're interested in building against them.
monster1612 said:
I already forked the repos prior to the post-3.0.72+ commits. I'll link in the manifest file I created if you're interested in building against them.
Click to expand...
Click to collapse
Yes, bring it, please.
alexander_32 said:
Yes, bring it, please.
Click to expand...
Click to collapse
Here's the manifest file for building against those repos. I'm going to backtrack through the commits by forking the original repos at different points in time. Obviously, the old repos I forked before the 3.0.101+ commits are going to stay as they are for the time being until the issue is pinpointed and fixed once and for all. After that, I plan on deleting the manifest file and repos. Make sure that you run repo sync --force-sync on your build tree after replacing the manifest file and make clean to revert the kernel, or you'll still have remnants of 3.0.101+ lurking in the builds.
monster1612 said:
Here's the manifest file for building against those repos. I'm going to backtrack through the commits by forking the original repos at different points in time. Obviously, the old repos I forked before the 3.0.101+ commits are going to stay as they are for the time being until the issue is pinpointed and fixed once and for all. After that, I plan on deleting the manifest file and repos. Make sure that you run repo sync --force-sync on your build tree after replacing the manifest file and make clean to revert the kernel, or you'll still have remnants of 3.0.101+ lurking in the builds.
Click to expand...
Click to collapse
Thanks.
Like I said to @alexander_32, I tried reverting the u-boot.bin commits that Transi made a couple months back for the aicp build. It booted, ran really slow, and OpenCamera still saw the camera module as being in use. Using the current boot binary things run nice and fast again. The build I ran off last night testing a couple more things also did not have any effect on camera...
electrikjesus said:
Like I said to @alexander_32, I tried reverting the u-boot.bin commits that Transi made a couple months back for the aicp build. It booted, ran really slow, and OpenCamera still saw the camera module as being in use. Using the current boot binary things run nice and fast again. The build I ran off last night testing a couple more things also did not have any effect on camera...
Click to expand...
Click to collapse
Probably it something else. Did you check my method by the way?
electrikjesus said:
Like I said to @alexander_32, I tried reverting the u-boot.bin commits that Transi made a couple months back for the aicp build. It booted, ran really slow, and OpenCamera still saw the camera module as being in use. Using the current boot binary things run nice and fast again. The build I ran off last night testing a couple more things also did not have any effect on camera...
Click to expand...
Click to collapse
What'd you happen to test with last night's build? Also, was it my u-boot commit that caused the problems or before that?
monster1612 said:
What'd you happen to test with last night's build? Also, was it my u-boot commit that caused the problems or before that?
Click to expand...
Click to collapse
I tested a couple of camera specific build tags in bowser common and tate. They didn't work. When I get a chance later on, I plan on diving into it again.
@alexander_32: Not sure why, but I can't boot using this with the rom you posted here. It stays on the boot logo indefinitely. After a clean install and making sure it boots fine once, I'm manually flashing the boot.img in the zip and copying the contents of the modules dir while fixing permissions afterwards. Is that all there is to it or am I missing something?
r3t3ch said:
@alexander_32: Not sure why, but I can't boot using this with the rom you posted here. It stays on the boot logo indefinitely. After a clean install and making sure it boots fine once, I'm manually flashing the boot.img in the zip and copying the contents of the modules dir while fixing permissions afterwards. Is that all there is to it or am I missing something?
Click to expand...
Click to collapse
You just extracting all files from camera fix, then update cm13.0 flashable zip with files from camera fix and flash flashable zip. It worked on Temasek's CM13. I'll do more researches and inform about results.
alexander_32 said:
You just extracting all files from camera fix, then update cm13.0 flashable zip with files from camera fix and flash flashable zip. It worked on Temasek's CM13. I'll do more researches and inform about results.
Click to expand...
Click to collapse
Ah, I read the OP wrong and wasn't merging into the rom zip but manually into existing installation. Though even now, I still can't boot after trying it with plain cm13, beanstalk, or temasek. I'm using twrp 2.8.7.0 with cache and data both f2fs if that makes any difference.
Has anyone else had success so far and if so with which roms?
r3t3ch said:
Ah, I read the OP wrong and wasn't merging into the rom zip but manually into existing installation. Though even now, I still can't boot after trying it with plain cm13, beanstalk, or temasek. I'm using twrp 2.8.7.0 with cache and data both f2fs if that makes any difference.
Has anyone else had success so far and if so with which roms?
Click to expand...
Click to collapse
I guess now I understand what happened. I flashed my fix first, then did factory reset and flashed changed zip. I'll test it and inform what happened
CONFIRMED: It's 3.0.72+ kernel.
http://i66.tinypic.com/33mwkyw.png
http://i64.tinypic.com/33u8qow.png
CONFIRMED: PAC ROM MM works!
http://i66.tinypic.com/2n8v5uf.png
CONFIRMED: Cyanogenmod works!
http://i64.tinypic.com/2eunbz9.png
CONFIRMED: BeanStalk works! (Solution was a kernel from RR 5.6.5 with blue logo)
http://i67.tinypic.com/107rwx2.png
alexander_32 said:
UNBELIEVABLE! It works on Temasek only! But I'm not done yet. Need some time to think.
Confirmed: It's 3.0.72+ kernel.
http://i66.tinypic.com/33mwkyw.png
http://i64.tinypic.com/33u8qow.png
I'll update this thread with more information.
Click to expand...
Click to collapse
I'm thinking it doesn't work on transi's RR or CM13 builds because he disabled the camera with some commits that he hasn't pushed to GitHub. Either way, those builds are built with 3.0.101+, and the patches you brought in are from 3.0.72+. It would make sense if they didn't boot after patching (especially if you flash the boot.img). What happens if you just replace the files in /system and leave the boot image intact?
monster1612 said:
I'm thinking it doesn't work on transi's RR or CM13 builds because he disabled the camera with some commits that he hasn't pushed to GitHub. Either way, those builds are built with 3.0.101+, and the patches you brought in are from 3.0.72+. It would make sense if they didn't boot after patching (especially if you flash the boot.img). What happens if you just replace the files in /system and leave the boot image intact?
Click to expand...
Click to collapse
My builds work with 3.0.101+ as well, but Temasek's works and BeanStalk doesn't (with 3.0.72+). Yes, I'll try it.
monster1612 said:
I'm thinking it doesn't work on transi's RR or CM13 builds because he disabled the camera with some commits that he hasn't pushed to GitHub. Either way, those builds are built with 3.0.101+, and the patches you brought in are from 3.0.72+. It would make sense if they didn't boot after patching (especially if you flash the boot.img). What happens if you just replace the files in /system and leave the boot image intact?
Click to expand...
Click to collapse
I tried that yesterday, and it results in never getting to the boot animation, so the kernel never loads.
5 from 7 for today. A new link https://www.androidfilehost.com/?fid=24591000424949408
[ROM][7.1][UNOFFICIAL] CM14.1 for Nexus 7 2012 (grouper)
*** Disclamer
By downloading and installing this ROM you agree that you do so at
your own risk, and that you understand that it probably voids your
warranty. (But does anyone still have an active warranty on this 2012
device?)
Introduction
@AndDiSa's AOSP 7 builds look pretty nice, but I needed something that seamlessly upgrades from CM13. @GtrCraft who provided our CM13 builds has moved on to other devices, so we need a new CM maintainer. I may not be the right person for that job... but I can at least share the build I made for myself. Perhaps someone will be motivated to join the fun or even take over.
[Images on screenshots tab.]
Installation instructions
Back up your data and previous ROM with TWRP 3.0.2.
Download from link below.
Wipe system, cache, dalvik.
Also wipe data unless you are coming from CM13.
Install the ROM.
Optionally add opengapps-pico.
With default settings it will give an error about insufficient space. To avoid that, first copy this gapps-config-grouper.txt file, perhaps edit it to your taste (instructions here), then copy to the device in the same directory as the opengapps zip. The opengapps updater-script will look for it there when you install opengapps.
Reboot.
WAIT for system to settle before you decide it is slow. Some of the app optimization which used to happen during initial boot now seems to happen in the background. When it's finished, responsiveness will improve.
Download
cm-14.1-20161226-UNOFFICIAL-grouper.zip (AndroidFileHost)
Credits / Thanks
Google / AOSP
CyanogenMod
@AndDiSa for AOSP 7.1 -- I use his kernel tree directly, and many of his device tree mods
@GtrCraft for the CM13 tree upon which mine is based
XDA:DevDB Information
Unofficial CM14.1 for Nexus 7, ROM for the Nexus 7
Contributors
aaopt, AndDiSa,GtrCraft
Source Code: https://github.com/aperomsik/cyanogenmod_android_device_asus_grouper/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-25
Last Updated 2016-12-31
Reserved
Changelog
Nearly all builds include CM sync -- only mentioned specifically when it was the main point of the build.
20161226 (AndroidFileHost)
LiveDisplay works (due to upstream work).
20161212 (AndroidFileHost)
NFC
20161208 (AndroidFileHost)
CM sync, including 7.1.1r4
20161130 (AndroidFileHost)
Stock camera works.
20161125 (DevHost)
Initial posting.
seems to be pretty stable so far but i cant get pico gapps to install even after installing the rom with the gapps-config.
There is a 3.4 kernel build for grouper which was helpful for cm13. Can you incorporate that into your build ?
why is this not even on development thread?
is this based on anddisa's device,vendor trees? cuz that build is super fast. i am downloading anyway.
turnert said:
seems to be pretty stable so far but i cant get pico gapps to install even after installing the rom with the gapps-config.
Click to expand...
Click to collapse
Sorry about that. I meant to say .gapps-config goes with the gapps zip, not with the ROM. Corrected, and also edited for clarity. If it still doesn't work for you, look at the log file it generates in the same folder as the zip, and make sure it says it read your config file.
abhifx said:
why is this not even on development thread?
Click to expand...
Click to collapse
I had originally put it in development, but it took me too long to fill in the devdb new project page... after it made me reload the page and reenter some things, apparently I wound up in general by mistake.
abhifx said:
is this based on anddisa's device,vendor trees? cuz that build is super fast. i am downloading anyway.
Click to expand...
Click to collapse
Yes, when I saw how fast @AndDiSa's AOSP 7 ROM was, I had to try a CM14 build. I'm using his kernel and vendor trees, and many of his recent device tree commits cherry-picked into a fork of @GtrCraft's CM13 device tree.
Requested mods to move this to development section.
Also can't install gapps with the given script. Anyone up for new gapps zip?
abhifx said:
Also can't install gapps with the given script. Anyone up for new gapps zip?
Click to expand...
Click to collapse
Please pastebin your resulting open_gapps_log.txt, and send me the link . You should find the log file on the device in the directory where you had put the gapps zip and config files. For comparison, mine is here.
aaopt said:
Please pastebin your resulting open_gapps_log.txt, and send me the link . You should find the log file on the device in the directory where you had put the gapps zip and config files. For comparison, mine is here.
Click to expand...
Click to collapse
will post it in the evening, i dont think gapps is picking up the config file, should the config file go inside the zip file? i am just pasting it outside the zip file.
Frankly the ROM is working fine, however i have yet to lock gps and test it which is my main usage.
After seeing CM booting, i would love to see other derived ROMs (AICp, RR etc)
Maybe you can post a guide others may build it too (i dont have the disk space or the bandwidth to do it anyway)
abhifx said:
will post it in the evening, i dont think gapps is picking up the config file, should the config file go inside the zip file? i am just pasting it outside the zip file.
Frankly the ROM is working fine, however i have yet to lock gps and test it.
Click to expand...
Click to collapse
Not in the zip file... Just alongside, in the same folder on the device (or usb stick if you install via OTG) where the Gapps zip is.
Sent from my MotoG3 using Tapatalk
The config files name needs to be "gapps-config.txt" or ".gapps-config". I just tried the first option an gapps installed just fine!
abhifx said:
will post it in the evening, i dont think gapps is picking up the config file, should the config file go inside the zip file? i am just pasting it outside the zip file.
Click to expand...
Click to collapse
I was having issues as well with the config file. I tried putting it in all kinds of places, but no dice.
I ended up using the Aroma Open Gapps package which worked great.
Haven't tried much on this ROM yet, but things feel snappy.
hawkshot said:
I was having issues as well with the config file. I tried putting it in all kinds of places, but no dice.
I ended up using the Aroma Open Gapps package which worked great.
Haven't tried much on this ROM yet, but things feel snappy.
Click to expand...
Click to collapse
ah yes.. Aroma Gapps, which keeps on cancelling this huge package. oh well will try renaming the text file
---------- Post added at 01:25 PM ---------- Previous post was at 12:49 PM ----------
ok this was even more weird, i copied the files in a separate directory (the config file was in txt format as suggested by @gothier) and this worked. earlier everything was in the root directory and nothing worked no matter was was the file extension, hidden or not.
Thanks OP.
I've successfully installed the ROM on my Grouper device.
Also, I've installed Opengapps via CF's Flashfire app and it worked very well.
Thank you for the rom.
I updated from CM13, install gapps with config , only rename it to ".gapps-config-grouper". I use all from USB drive via OTG for all my android devices.
All work fine.
Even in pico gapps package I had to exclude some apps so it could be installed. I've written in in gapps-config.txt this way:
GoogleTTS
calsync
A bug
When I pull down the notification/ quick settings, the device crashes and reverts to lock screen.
eNVy said:
When I pull down the notification/ quick settings, the device crashes and reverts to lock screen.
Click to expand...
Click to collapse
havent crashed on me yet.
@aaopt, it seems anddisa has a made some changes wherein camera is also working, maybe you can update the same for CM14.1?
It doesnot happen always. Sometimes only.
*** Disclamer
By downloading and installing this ROM you agree that you do so at your own risk, and that you understand that it probably voids your warranty. Installing this ROM may distroy your device, you may loose your data, your money, your friends, ...
If you are not sure what you are doing - leave it!
Introduction
I like Resurrection Remix but i could not find find it here, so i tried to make it on my own.
Here is the result - on my Nexus 7 it works, but i dont use it very much.
If you want to overclock your device (up to 1700MHz) you can change you kernel settings - use "Kernel Adiutor"
About me
I am not a developer! I just build it or fun and because i want to use it. Don't expect much support from me - my time is limited.
Installation instructions
Be sure you are on the latest TWRP https://dl.twrp.me/grouper/ or on the last CWM (Google for it)
Back up your data
Download ROM from link below
If you want to use Google Apps (openGAPPS):
Download GAPPS from http://opengapps.org/ Platform=ARM, Android=7.1, Variant=pico
Download gapps-config.txt (attached). Without removing something - configured in gapps-config.txt - you do not have space to install GAPPS in system partition
Put all files in the same directory
Wipe system, cache, dalvik, data (only for the first install)
If you like you can change the filesystem of the partitions "cache" and "data" to F2FS. Do not change "system" partition !!!
Install the ROM and optinal GAPPS.
Reboot into system - first boot may take 5 ... 10 Minutes!
Enjoy
Video by @Majid2000 uses CWM-Recovery.
If you want to root your device:
You have to add a root manager to root your device - there is no root by default.
Option 1: Look for Magisk on XDA and install it
Option 2: Install SuperSU or any Superuser
Only versions from July 2017 onwards come without "root".
If you want to add Googleapps:
With default settings it will give an error about insufficient space. To avoid that, take the smallest Gapps package you can get. I recommend opengapps.org (select Platform:ARM Android:7.1 Variant: pico).
The easy way:
Attached you will find my "gapps-config.txt" file. Feel free to change it to your needs. The name must be "gapps-config-grouper.txt" or "gapps-config.txt"
Copy this file to the same directory as you have your opengapps.zip file. The opengapps updater-script will look for it there when you install opengapps.
Pay attention: This script will remove some system apps from your device. If you still need them do this steps before installing gapps:
1) root your device or use twrp to execute following steps
2) copy all needed apps from /system/app or /system/priv-apps to any non /system directory (/data or external storage may be a good idea)
3) install gapps
4) install saved apps (you may need to change your settings to allow install of apps from an unsafe place)
You have to repeat it on every clean install or if you want to updete your apps with a fresh version.
Backgroundknowledge:
You have to deinstall some packages:
The easiest way is to follow these instructions:
https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
My file gapps-config.txt contains this:
Code:
DialerFramework
PackageInstallerGoogle
CMAccount
CMUpdater
CMSetupWizard
CMAudioFX
CMFileManager
CMMusic
CMScreenCast
CMWallpapers
CMWeatherProvider
BasicDreams
DashClock
Galaxy
Hexo
HoloSpiral
PhotoTable
CalculatorStock
FMRadio
Gallery
Gallery2
LiveWallpapers
MMS
PicoTTS
VisualizationWallpapers
GoogleTTS
(NexusLauncher)
(Eleven)
(Email)
(Contacts)
(Jelly)
(AudioFX)
(Calendar)
(ExactCalculator)
MusicFX
LockClock
Terminal
LRecorder
SoundRecorder
StorageManagerStock
LiveWallpapers
Studio
WhisperPush
ClockStock
Reboot.
WAIT for system to settle before you decide it is slow. Some of the app optimization which used to happen during initial boot now seems to happen in the background. When it's finished, responsiveness will improve.
Kernel settings
The kernelspeed is set to 1300Mhz by default. If you want more you have to change it. Use "Kernel Adiutor" or any tool of your choice.
Accordding to the architecture of the CPU the maximum speed is 1500Mhz if running in multikernel mode. If running in singlekernel mode it can go up to 1700Mhz. If you want maximum speed use 1700Mhz even this speed is mark as unused in monitoring tools. You are allways in multikernel mode if your display is on - use with care!
ZRAM is enabled by default.
CPU-Voltage is editable so u can undervolt if you like - use with care!
Download
Build 16.12.2917 (RR 5.8.5):
with December security patches.
androidfilehost
Build 20.11.2017 (RR 5.8.5):
With November security patches.
Google-Drive
androidfilehost
------------------------------------
Historical versions:
------------------------------------
RR 5.8.4:
Androidfilehost
------------------------------------
RR 5.8.3:
Androidfilehost
Note: From this version on there will be no root manager included.
------------------------------------
RR 5.8.2:
Androidfilehost
------------------------------------
RR 5.8.1:
Androidfilehost
---------------
RR 5.8.0:
Androidfilehost
--------------
Credits / Thanks
Google / AOSP
CyanogenMod / LineageOS
Resurrection Remix
@aaopt: I took the basics from his thread https://forum.xda-developers.com/nexus-7/development/rom-lineageos-14-1-nexus-7-2012-t3530261
@AndDiSa https://github.com/AndDiSa
https://github.com/aperomsik for his device tree
@daniel_hk for the DC-Kernel from his Github
@1lyharry for gapps-config.txt
and all the others who helped to keep our device alive and up to date
Known bugs
thumbnails in gallery show wrong colours - see attached screenshot -affects all ROM on my Nexus 7 started with Android 6
Problems with Bluetooth keyboard were reported
If you like to build it on your own, here is a brief instruction (for detail instructions use the web, there are plenty of them):
Make sure your system is set up to compile Android and your crosscompiler works and is in your env.
Setup Resurrection Remix: [url]https://github.com/ResurrectionRemix/platform_manifest[/URL]
Add a file ".repo/local_manifests/roomservice.xml" inside your RR directory with the content from [url]https://github.com/wilmsn/android_manifests/blob/cm-14.1/grouper.xml[/URL]
Add this to your ".bashrc"
Code:
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4g"
Then call
Code:
repo sync --force-sync
. build/envsetup.sh
make clobber
brunch grouper
Version 20170323:
March security patches
Merged kernel changes from @AndDiSa (thanks for your work)
Version 20170225:
RR System:
Upgrade to RR Version 5.8.2 with February security patches
Version 20170209:
Kernel:
Overclock and governors implemented (from former OC kernel). Kernel starts with 1300Mhz, if you want higher speed you have to change it.
ZRAM enabled by default.
Voltage table is editable now.
RR System:
Upgrade to RR Version 5.8.1
Nice! Testing right now
Edit: just installed. Smooth and with the 5th Jan security issue. Thanks!
Edit: after two days use, there are a couple of minor issues I've found. Just to say:
- The screen brightness seems to blink sometimes. Besides, if you adjust the screen brightness through the status bar swiping, the behavior is not perfect. Sometimes the screen get turned off Edit 2: I'm retarded and I had the auto brightness feature turned on
- Force close apps are sadly common when trying to start an app. However, restarting that app normally works. If the FC persists, switch the orientation of the tablet.
@wilmsn, did you have to do anything special to build the ROM? I'm building it by myself and I succeeded with your recipe, but it seems that
- My build is a bit slower than yours in terms of runtime performance. It's only an impression
- mp4 files won't play. VLC does not work at all, and internal video player only will play the audio tracks on these video files
Thanks!!
Edit: never mind, it seems that I configured something (I don't know what) in the improper way. Reinstalled my self-built ROM and mp4 files are being played properly .
@pacorrop
I use:
Code:
Pkg.Desc = Android NDK
Pkg.Revision = 13.1.3345770
and set this in my .bashrc:
Code:
CROSS_COMPILE=/home/norbert/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
Hope it helps!
Might I make a suggestion?
You may want to see if you can integrate DC-Kernel into this rom. I use this kernel all the time on my grouper and love Ressurection Remix. But the two don't play nice together currently. I would love to have the option to Oveclock and all that with this Rom.
If not, no worries. Rom is running rather well as it sits, would just like to have the added boost if needed.
Thanks for reading. Keep up the good work.
Thanks for reading
The~Skater~187 said:
Might I make a suggestion?
You may want to see if you can integrate DC-Kernel into this rom. I use this kernel all the time on my grouper and love Ressurection Remix. But the two don't play nice together currently. I would love to have the option to Oveclock and all that with this Rom.
If not, no worries. Rom is running rather well as it sits, would just like to have the added boost if needed.
Thanks for reading. Keep up the good work.
Thanks for reading
Click to expand...
Click to collapse
I will try to build it - so stay tuned ...
wilmsn said:
I will try to build it - so stay tuned ...
Click to expand...
Click to collapse
Thank you. I'm working on syncing sources myself because I was going to try to get it working. But I'm extremely New to kernel development
Resurrection-Remix5.7.4 Boeffla/Venom powered SM -G900P
DC Kernel added
I just added DC-Kernel to OP. You can overclock the device up to 1700MHz.
Use with care and on you own risk.
@The~Skater~187 hope you can use it - i did only a quick test.
Norbert
wilmsn said:
I just added DC-Kernel to OP. You can overclock the device up to 1700MHz.
Use with care and on you own risk.
@The~Skater~187 hope you can use it - i did only a quick test.
Norbert
Click to expand...
Click to collapse
Thank you. I will flash and report back.
Sent from my Nexus 7 using Tapatalk
wilmsn said:
I just added DC-Kernel to OP. You can overclock the device up to 1700MHz.
Use with care and on you own risk.
@The~Skater~187 hope you can use it - i did only a quick test.
Norbert
Click to expand...
Click to collapse
How did you go about flashing? I keep getting stuck at boot animation. Been there for about ten minutes now?
The~Skater~187 said:
How did you go about flashing? I keep getting stuck at boot animation. Been there for about ten minutes now?
Click to expand...
Click to collapse
Strange .... I just use rashr => flash kernel from storage and then reboot wait about 2 Min. or so in Google animation. After that RR animation
wilmsn said:
@pacorrop
I use:
Code:
Pkg.Desc = Android NDK
Pkg.Revision = 13.1.3345770
and set this in my .bashrc:
Code:
CROSS_COMPILE=/home/norbert/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
Hope it helps!
Click to expand...
Click to collapse
Thank you very much!
It's weird because, as far as I know, I don't have the NDK installed how am I able to compile? Geez :laugh:
wilmsn said:
Strange .... I just use rashr => flash kernel from storage and then reboot wait about 2 Min. or so in Google animation. After that RR animation
Click to expand...
Click to collapse
Got it working, thank you. Only thing I've noticed over the last day or two is that any kernel tweaks such as over clock or changing of governors don't seem to stick. Tried with many different apps and as soon as you close the app, it all goes back to default.
Sent from my SM-G900P using Tapatalk
The~Skater~187 said:
Got it working, thank you. Only thing I've noticed over the last day or two is that any kernel tweaks such as over clock or changing of governors don't seem to stick. Tried with many different apps and as soon as you close the app, it all goes back to default.
Click to expand...
Click to collapse
The only thing i use is overclocking. On my N7 OC works fine up to 1500MHz. If i go to 1600 or 1700 it is taken from the system but if i look at the statistics it runs only at 1500. I can change the governor and when i look it up it is still set to the right value.
The rest is DC kernel with no changes.
You are sure you gave root access to the tools you use?
BTW: I use kernel adiutor to change settings.
wilmsn said:
The only thing i use is overclocking. On my N7 OC works fine up to 1500MHz. If i go to 1600 or 1700 it is taken from the system but if i look at the statistics it runs only at 1500. I can change the governor and when i look it up it is still set to the right value.
The rest is DC kernel with no changes.
You are sure you gave root access to the tools you use?
BTW: I use kernel adiutor to change settings.
Click to expand...
Click to collapse
I tried kernel auditor myself, don't seem to stick. I'll give it a try again. I've recently been trying to use the performance control app DanielHK recommends for dc kernel. I did check to make sure all kernel as I've tried had root permission.
Sent from my SM-G900P using Tapatalk
Fantastic and I cannot say that enough!! I do have a remedial question as I have been out of the AOSP Roms for some time. I cannot get the Gapps to work. I used the pico and followed the steps. I am still have the same error and when. It boots back up they are not there. Can you help please?
hackwoof said:
Fantastic and I cannot say that enough!! I do have a remedial question as I have been out of the AOSP Roms for some time. I cannot get the Gapps to work. I used the pico and followed the steps. I am still have the same error and when. It boots back up they are not there. Can you help please?
Click to expand...
Click to collapse
Did you do a full wipe (system and data) bevor installing?
wilmsn said:
Did you do a full wipe (system and data) bevor installing?
Click to expand...
Click to collapse
Yes sir. I followed everything as closely as possible. I'm not sure where I made my error. Is there an easier how-to for the Gapps maybe there's something I'm missing? Again I'm coming back to AOSP after many years and definitely different.
During the last few months I have been testing several Nougat rom/kernel/modem/su combinations for the hlte N9005 international.
I created this thread to share my setup, hoping it will help others to save the many hours of research, trial, error and frustration I had before reaching the jackpot.
I have 3 hlte phones at my disposal, two myself and one my wife. All three are running trouble free.
By using my setup you will get:
Absolutely no freezes, reboots or FCs
Stable root and Safetynet checks ok
GPS fast and stable fix - average 5 seconds worst 20 seconds
Low battery drain (of course actual drain depends heavily on your apps and usage)
Everything works (AFAIK - you tell me what does not)
Keep in mind my main goal is to provide a stable setup. I will do my best to update this thread regularly, but it is very unlikely I will be using the very latest builds available, mainly because before I adopt a new build it must be thoroughly tested.
If you're interested head to the guide in Post #2
Why Resurrection Remix?
RR has, IMHO, the best combination of features and stability. The RR team has been around for a long time without the ups and downs of other roms. For the Note 3 we are in a very fortunate time, with an official build and many unofficial builds to choose from.
Since RR is based on LineageOS, it is available for most devices. It is very likely when we finally retire our Note 3 and move to another flagship, RR will be there for it.
Why Not Oreo?
Well, thread title says it all.
Credits and Thanks:
@vidwhal for the current RR build
@gj86 for Synergy kernel
@Jairus980 for Xenial kernel
@Hereiwas and @jcadduono for modems and bootloaders
@topjohnwu for Magisk
@stangri and @kantjer for Magisk unofficial daily beta builds
@Deic for the Safetynet fix Magisk module and @NovelliJack for finding the module
@MastahF and all other contributors that made the Open GApps project possible
Special thanks to @tarkzim for the RRN build used in initial setups.
and everyone else I forgot to mention.
>>>>>>> I know - screenshots below are from a previous setup. I will update then sometime in the future.
Rock Stable Setup
Using Resurrection Remix
Revision 11 - 11-Mar-2018
Phase 1 - Prepare for install
Here I am assuming you have a Windows PC. If not you will need to use google search to adapt my instructions to your available OS/hardware. The PC is only required for this phase.
1 - Samsung USB Driver:
Make sure you have the Samsung USB driver installed in your Windows PC.
If not download and install the latest driver:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.65.0.exe
2 - Odin:
If you do not have Odin, get it here, unpack to any folder and create a shortcut pointing to Odin3 v3.09.exe.
There are newer versions of Odin, but they may have issues with our Note 3. Odin v3.09 is the one to use.
3 - TWRP
New to TWRP? Read this guide: TWRP: the complete guide to using Recovery on Android.
If you do not already have it, install TWRP 3.2.1-0. Download it from https://dl.twrp.me/hlte. More info here.
If you no not have TWRP installed download the .tar file and flash with Odin.
If you have an older version download the .img file and use your current TWRP to flash the image into recovery partition.
4 - Update Bootloader and Modem:
You have to install latest Nordic Countries Bootloader and Modem. I have prepared a "tar.md5" with both.
And yes, modem is not country or region dependent. Rest assured Nordic will work no matter where you are.
Get it from here: N9005_Nordic_XXUGPQB1-Modem_XXSGBQD1-Bootloader.tar.md5
Updating bootloader and modem is a must!
If you don't you may get the "SIM Card not detected" error and GPS fix will be slow or not work at all.
There are many sure ways to flash modem and bootloader so that they "stick". What always works for me is:
- Restart into Recovery (TWRP)
- Select Reboot->Power off
- Turn on directly into download mode by holding Down Arrow+Home+Power at the same time
- Connect phone to PC
- Flash with Odin using the AP slot
Now you should check if update was successful. The best way is to install the app Phone INFO, run it and select the Firmware tab. The correct Bootloader and Baseband (modem) above should be displayed. There is a screenshot in first post.
If the update did not work repeat the steps carefully until it does. You may, as a last resort, after powering off remove the battery, wait for about 30 seconds, reinsert the battery and then turn on directly into download mode.
Thanks to @Hereiwas for the files I have used in previous setups. Check out in his thread Bootloader and Baseband for SM-N9005.
If you need more info on flashing modems and bootloaders also take a look at @jcadduono thread [Direct Download] Latest Bootloaders & Modems.
PHASE 2 - Download the necessary installation files
1 - Resurrection Remix Nougat rom - thanks @vidwhal:
Download from here: RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip.
Please note that I am not the rom builder or developer. All credits go to @vidwhal and the RR Team.
This is the rom thread: [ROM][HLTE][UNOFFICIAL][OMS]Resurrection Remix N.
Please note this build may not be the latest available. The goal here is to have a stable rom that you will be able to use as a daily driver with no issues for a long time. Only after a lot of testing a new build makes into my setup.
I modified the zip to remove Magisk. This will make it easier to use newer or beta Magisk builds if necessary in the future. Remember Safetynet is a cat and mouse game and changes happen fast.
Special thanks to @tarkzim, who produced the RR builds used in earlier setups. He did a fantastic job of producing a very stable build without a Note 3 device for tests. His builds led me to create this thread.
2 - Magisk v16.0 Official - thanks @topjohnwu):
Magisk Installer: Magisk-v16.0.zip
Magisk Manager: MagiskManager-v5.6.1.apk (optional - you might need it in the future)
Magisk Uninstaller: Magisk-uninstaller-20180222.zip (optional - you might need it in the future)
if you decide to use newer builds do it at your own risk. I strongly recommend to keep these.
3 - Gapps:
Open Gapps Pico: open_gapps-arm-7.1-pico-20180311.zip
Not much to say here. Open GApps FTW.
Again the above build is the one I tested. Use this for a failproof installation, but feel free to use a newer build. Usually it will not be a problem.
I prefer Pico Gapps so I have the bare minimum as system apps. And I live by the KISS Principle. All other gapps I need are installed as user apps so I am allowed to use Titanium Backup to backup/restore them with data.
If you would rather use another Gapps package just pick the one you want. All packages should work but the Aroma. Aroma does not work in TWRP 3.
4 - Xenial Kernel - thanks @Jairus980:
Xenial Kernel: [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
Kernel thread: [Kernel][Xenial][Hlte].
With Xenial you have some fixes like the correct charging current in lock screen and working Gravity, Linear acceleration and Orientation sensors. Of course there is a lot more under the hood. If you plan to do some kernel tweaking Xenial offers more options.
If you do flash Xenial kernel do not report any bugs in RR thread. To report a bug you must first go back to stock kernel by dirty flashing RR and Magisk. If you are still able to reproduce the bug then you may post it in RR thread.
Even if there is a newer kernel release, you should keep using the build I posted here to have my tested stable setup.
Special thanks to @gj86 for his Synergy Kernel, used in my previous setup. It is also a great option.
5 - GPS Fix:
In this setup there is no need for a GPS fix. GPS is fast and rock stable as it should always have been.
But you really must update your modem to my recommend Nordic QB1 or GPS will be slow or not work at all.
Do not worry about your current location. The modem will work not matter where you are.
Latest RR builds somehow made GPS fix slower. I checked the gps.conf file and it is exactly the same as in previous builds.
I have my own optimized gps.conf, prepared originally for Marshmallow CM13, with a few more adjustments for Nougat.
After installing my gps.conf in latest RR build, gps fix is back to normal, taking only a few seconds.
I prepared a flashable zip to install my gps.conf. It saves existing gps.conf and put mine in its place.
Download it from here: Fix-GPS-for-hlte-la14.1-based-roms-v1.zip.
PHASE 3 - Backup!!
Now it is time to make backups of your current setup.
Use TWRP to make a nandroid backup. You will need it if something goes wrong. If you are paranoid like me make two and save them on your PC hard drive.
If you use Titanium make also a Titanium full backup. Remember that you should never restore system apps or settings. Use Titanium only to restore user apps and xml backups of wifi passwords, call log and sms messages.
The steps to install the new ROM will not erase your internal storage, but why not make a backup of everything to your PC or an OTG USB Drive.
PHASE 4: Install
- Make sure you have updated TWRP and your bootloader and modem as instructed in phase 1
- Make sure you have all files downloaded from phase 2 in your phone - preferably in external sdcard
- Make sure you have backups!!
- Reboot into Recovery (TWRP)
- Use advanced wipe to wipe System, Data and Cache
- Flash RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip
- DO NOT WIPE ANYTHING
- Reboot System (be patient - it will take a while, around 3-4 minutes)
- Pick your preferred launcher
- Check Settings->Date & Time and make sure it is ok
- Reboot into Recovery (TWRP)
- Flash [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
- Flash Magisk-v16.0.zip
- Flash open_gapps-arm-7.1-pico-20180311.zip (or the one you prefer)
- DO NOT WIPE ANYTHING
- Reboot System (this time it will be faster)
- Go to Settings->Accounts and add your google account
- Customize your other settings
- Run Magisk Manager and check if SafetyNet passes
- If not disable/reenable "Magisk Hide" option in Magisk Manager Settings and try again
- Restore/install apps/data
- PROFIT!
[Reserved]
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
tarkzim said:
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
Click to expand...
Click to collapse
Sorry, you are absolutely right.
Thanks for being cool with it.
The main point in changing the rom zip is removing the magisk manager system app. It is a little tricky for noobs to remove the system app to be able to install the v5 beta Magisk Manager.
And thanks again for making your fantastic RR build available.
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
sperug said:
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
Click to expand...
Click to collapse
This does not happen in my phones.
In my work phone I have 600+ apps installed. It takes a while to open but no crashes.
If you post a logcat I may be able to help.
I reinstalled everything, and before made a full wipe, also of the internal storage. And the problem was no more present! Wow! And thank you again...
I checked AFH and have 30+ downloads of installation files.
Any more success or failure cases? Please let me know.
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
BobbyKa said:
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
Click to expand...
Click to collapse
AFAIK it should work for you no matter where you are.
I live in Rio de Janeiro, Brasil and use it.
If it does not work for you just flash another one.
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
BobbyKa said:
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
Click to expand...
Click to collapse
To use Sammy Spen apps/features you need a Touchwiz based stock rom.
There are some apps with similar features for AOSP roms.
Many users say the best is SPenCommand developed by @emandt. It is paid but users say that the app is well worth the price.
Check the SPenCommand Google+ Comunity.
Great post. I don't see google assistant working, any clue?
Sent from my Pixel using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:10 PM ----------
Please ignore, I installed nano gapps and it worked
Sent from my Pixel using Tapatalk
what about battery life ?
has anyone tried this on Sprint Note 3 sm-n900p ?
svbarbosa said:
Check the SPenCommand Google+ Comunity[/URL].
Click to expand...
Click to collapse
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
BobbyKa said:
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
Click to expand...
Click to collapse
I have never used SPenCommand myself. Just read good things about it many times in other threads. Try to search and get help from people who are using it.
You may also check these apps: Note Buddy (S Pen Helper) and CM S Pen Add-on(ROOT).
And this guide on them: The Ultimate S Pen Customization Tool for Your Galaxy Note 3.
But be advised that I have no experience using these apps. Just found them using google.
opexblue said:
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
svbarbosa said:
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
Click to expand...
Click to collapse
Thank you for fast response. I will try other kernel.