Related
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.
Hello to all you Lenovo A7600-F owners! I've Got yet another Android Nougat ROM ported to the Lenovo A7600-F Tablet! This one is very stable, smooth, and has the least bugs of any ROM i've ported to the A7600-F.
Android Version: AIM OS v2.5 (Android 7.1.2)
Security Patch Version: November 6, 2017
Kernel Version: 3.4.67 (kk)
First of all special thanks to:
-The AIM OS ROM team
-S M Nahid Emon (From romclaims.com for the portable MT6582 ROM)
Working:
-Wifi, Bluetooth, Root, Storage, etc...
-Camera (Pictures, Video)
-Youtube (Up to 720p30)
-Substratum Themes (Latest OMS Themes work great! Still smooth!)
-FM Radio
-GPS!
Not Working (kind-of):
-Camera video recording is laggy on default settings.
-FM Radio in loudspeaker mode (It only works in headphone mode)
-Let me know if you find something else.
Installation:
-Step 1: Don't download this ROM, I recommend you try this ROM instead. It is also ported by me but has far fewer bugs and has newer patches. Over a year later, I still see people installing this ROM ): Do yourself a favor and try out the newer one.
-Download Rom
-Download Gapps
-Backup your current ROM
-Flash ROM using TWRP 3.x.x.x
-Flash Gapps
-Reboot
Notes:
-To get brightness to change, turn off Adaptive brightness.
-Substratum seems to work best with root enabled (in Developer Settings) and after a reboot.
Downloads:
-TWRP Download
-ROM Download
-GAPPS Download (Choose ARM - 7.1 - pico or nano)
Emulated Storage Fix:
-For those of you who have wiped/formatted "Internal Storage" with my TWRP recovery, you will likely not have proper access to internal storage in this ROM. If you have internal storage issues try to flash this boot image to /boot with TWRP's builtin .img flash utility. Download storage fix image here.
Kernel Source: here
Changes:
-Revision 2:
Fix Storage issue (For people with physical internal storage).
Update Launcher to new Pixel Launcher 8.1 4429924
Removed unnecessary service startups related to SIM/Modem
SaberShip said:
Hello to all you Lenovo A7600-F owners! I've Got yet another Android Nougat ROM ported to the Lenovo A7600-F Tablet! This one is very stable, smooth, and has the least bugs of any ROM i've ported to the A7600-F.
Android Version: AIM OS v2.5 (Android 7.1.2)
Security Patch Version: November 6, 2017
Kernel Version: 3.4.67 (kk.......
Click to expand...
Click to collapse
Thank you so much.. Give your link so that we will donate you.. I will definitely try it. .. But could you try any other roms like resurrection remix or rom with android 8.0.. Anyway thanks a lot again
Really good work. Thank you very much. This ROM is a new Life for this device. I have flashed a while ago and I'll test It this afternoon.
Hello. @SaberShip, I'd like to build RR on this tablet. Where can I find the device and the kernel source code for this device? Is it tough to build?
Thanks
Srisri7 said:
Thank you so much.. Give your link so that we will donate you.. I will definitely try it. .. But could you try any other roms like resurrection remix or rom with android 8.0.. Anyway thanks a lot again
Click to expand...
Click to collapse
In regards to the Resurrection Remix: I'll look into it. Iv'e got a Resurrection Remix rom running but its got some issues that need fixed.
pacorrop said:
Hello. @SaberShip, I'd like to build RR on this tablet. Where can I find the device and the kernel source code for this device? Is it tough to build?
Thanks
Click to expand...
Click to collapse
Lenovo has the source on their developer pages I believe. I have not even messed with the source though, I've also heard that it might not be complete.
SaberShip said:
In regards to the Resurrection Remix: I'll look into it. Iv'e got a Resurrection Remix rom running but its got some issues that need fixed.
Lenovo has the source on their developer pages I believe. I have not even messed with the source though, I've also heard that it might not be complete.
Click to expand...
Click to collapse
Ok cool! Thanks for that. I'll give it a try.
Anyway, given that you're trying to build RR as well... may I ask you where to find this needed stuff? I mean, I'll download the sources from Lenovo (which are for KitKat, according to their website); but you're not using these sources for RR and Nougat, right? Where can I find the sources you are using? Ahh or you may be using compiled kernel and device blobs, right?
Sorry for the off-topic; if further conversation is needed, I'll write you a PM instead.
Thanks again
pacorrop said:
Ok cool! Thanks for that. I'll give it a try.
Anyway, given that you're trying to build RR as well... may I ask you where to find this needed stuff? I mean, I'll download the sources from Lenovo (which are for KitKat, according to their website); but you're not using these sources for RR and Nougat, right? Where can I find the sources you are using? Ahh or you may be using compiled kernel and device blobs, right?
Sorry for the off-topic; if further conversation is needed, I'll write you a PM instead.
Thanks again
Click to expand...
Click to collapse
Nope! Im just porting Roms right now. Which is to say, i'm taking Roms already built for other devices with the same SOC (MT6582 in this case) and doing whats needed to convert them to run well on the A7600-F.
No bugs so far, aside from weird background noise - every time I click something, like a playing audio file but with no sound for 3 seconds, speaker goes on and off..
/sdcard is not well mounted
First, thanks for your greeeaaat job !!! I've beginning to install 6.01 and now i try this version 7.1.2?
I've an error with quasi all apps i've installated (ex : EZ Pdf reader, SyncDrive). The error is /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message)
And, indeed, with ES File Explorer, when i click on /sdcard, it show an error...
Yes, I have this error too. If I try to download a file with chrome, it can´t because there is no sdcard
freddie2000 said:
Yes, I have this error too. If I try to download a file with chrome, it can´t because there is no sdcard
Click to expand...
Click to collapse
It happened to me.. Try another browser
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
Almironi said:
No bugs so far, aside from weird background noise - every time I click something, like a playing audio file but with no sound for 3 seconds, speaker goes on and off..
Click to expand...
Click to collapse
Yeah.. This is happening to me also.. I have tried various mods but couldn't solve it.. And also there is too much distortion when volume is high..
Can some one port this rom to A7600-F..rr rom 7.1.2 (bugless)
http://www.techonarena.com/resurrection-remix-5-8-5-n-rom-for-mt6582/?i=1
5.1.1 bugless rr.. I wanted to try lollipop on this device.
http://mtk65roms.blogspot.in/2016/02/bugless-resurrection-remix-for-mt6582.html?m=1
coucout said:
First, thanks for your greeeaaat job !!! I've beginning to install 6.01 and now i try this version 7.1.2?
I've an error with quasi all apps i've installated (ex : EZ Pdf reader, SyncDrive). The error is /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message)
And, indeed, with ES File Explorer, when i click on /sdcard, it show an error...
Click to expand...
Click to collapse
Seems like the usual storage bug, I've run into this as well, I'll work on a fix and release an update soon hopefully.
Two new [mt6582] roms on romclaims:
Viper-OS v3.1.1
Colt-OS v1.3
Almironi said:
Two new [mt6582] roms on romclaims:
Viper-OS v3.1.1
Colt-OS v1.3
Click to expand...
Click to collapse
Thanks, saw these earlier too. But, what ones do we want more, Resurrection Remix or one of those? Let me know.
Port Revision 2
Updated the ROM to hopefully fix the storage issues. Check the OP for full changelog/download link
Please test and let me know if it helps!
SaberShip said:
Thanks, saw these earlier too. But, what ones do we want more, Resurrection Remix or one of those? Let me know.
Click to expand...
Click to collapse
AIM OS rom suits me best for now, till the new lightweight oreo go edition arrives
Internal storage error
SaberShip said:
Updated the ROM to hopefully fix the storage issues. Check the OP for full changelog/download link
Please test and let me know if it helps!
Click to expand...
Click to collapse
THX for the fast error fixes, but the internal storage error is still exist (in chrome /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message), when connect the tablet to the computer, no internal storage space). In TWRP when connect, the internal storage exist, you can copy files.
szelezola said:
THX for the fast error fixes, but the internal storage error is still exist (in chrome /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message), when connect the tablet to the computer, no internal storage space). In TWRP when connect, the internal storage exist, you can copy files.
Click to expand...
Click to collapse
Thanks for the info. Strange, mine seems to work just fine. Iv'e tried from Chrome, built in storage manager, other storage managers, and over USB. They all seem to work fine for me.
Have you ever wiped data AND internal storage with TWRP? Perhaps the TWRP I ported isn't properly formatting the internal storage, this is one thing I haven't done since having stock on my tablet. I'll try it soon.
SaberShip said:
Thanks for the info. Strange, mine seems to work just fine. Iv'e tried from Chrome, built in storage manager, other storage managers, and over USB. They all seem to work fine for me.
Have you ever wiped data AND internal storage with TWRP? Perhaps the TWRP I ported isn't properly formatting the internal storage, this is one thing I haven't done since having stock on my tablet. I'll try it soon.
Click to expand...
Click to collapse
Yes I do, format-wipe everything (internal storage to). I use the TWRP in your OP message.
SRGX2 for Life One X2 MiniThis Rom Is a Stripped down modified version of the Life One X2 Mini stock Rom.
NOTE: After installation give Launcer 3 notification permission and update Google Play Services (click on the notification).
(Please remember I do this in my free time and with my own money. If you like it please hit the thanks button)
Mods:
Malware removed
Build.prop Tweaks
Oreo Launcher
Camera app replaced by OpenCamera
File manager replaced by MiXplorer
To do list:
Build wifi drivers into the Kernel
Strip down rc scripts
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Camera
Flash
Fingerprint
Not Working Yet:
(You tell me)
Downloads:
Current Build: https://www.androidfilehost.com/?fid=673956719939824825
Builds: https://www.androidfilehost.com/?w=files&flid=239712
Patches: https://www.androidfilehost.com/?w=files&flid=254440
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel: https://github.com/vampirefo/android_kernel_blu_kernel_x2 (Special thanks to @vampirefo for the kernel source)
Screenshots: comming soon
Changelog
Version: Testing
Build: 01072018211020
Initial release
Version: rc1
Build: 01142018205847
switched to stock theme
Version: 1.1.0
Build: 02182018215948
rebuild off of the 01/04/2018 update
Version: 1.1.1
Build: 02242018165134
fixed mobile data bug
Version: 1.1.2
Build: 03032018224915
changed DPI to 441
added stock calendar app
added stock calculator app
add stock clock app
Troubleshooting
reserved
Does quick charge work?
Been running for a couple of days now without issue.
cyrusharding said:
Does quick charge work?
Click to expand...
Click to collapse
Yes it works, I've beeen using 2 QC3 chargers with no problems at all.
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
cyrusharding said:
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
Click to expand...
Click to collapse
Interesting, didn't know that exists. I currently just download off of http://download.spotify.com/android/SpotifyAndroid.apk
enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
srgrusso said:
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
Click to expand...
Click to collapse
This is awesome thanks so much!! I use Windows on a daily basis but I do have a pretty good knowledge about Linux and have set up a build environment in for Android. These links should help me understand what I am missing. I am also happy to continue testing and give you feedback on this ROM as it is currently my daily driver.
New Rom out. It has the stock theme, other than that it is the same.. I haven't decided if I'm going to build two Roms or have the theme be a patch. Maintaining all the different variants of the Rom are getting to be very time and space consuming.
https://www.androidfilehost.com/?fid=889964283620778170
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Requia77 said:
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Click to expand...
Click to collapse
Is this without root? I don't know if my rom will fix that, I never used the Paypal app. Your welcome to try and let me know. Also there is LineageOS 13 for the mini which has been built from source.
https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814
New rom rebuilt from the 01/04/2018 update.
v 1.1.0
There is a problem with the latest version of SRGX2. Mobile data doesn't work. I work on it this weekend and keep everyone updated.
Here is the fixed rom.
https://www.androidfilehost.com/?fid=818070582850494825
Good news I was able to get Android File Host to make the Life One X2 an official device. I have made a request for the Mini too. For now all the files will be under the Life One X2 device.
Updated rom: https://www.androidfilehost.com/?fid=673956719939824825
It includes the stock Calendar, Clock and Calculator apps. I changed the DPI to 441. Let me know if anyone has any problems with the Playstore. I know that there has been some requests for the stock Camera and file Manager apps. It's hard to please everybody so I added a patch section which may please some.