[ROM][5.0.2][Grouper][Ext4 Only]Plain-Andy v15.1 - Nexus 7 Android Development

Fresh from the kitchen comes ....
Plain-Andy
for Nexus 7​
Downloads
Mirror
Need GAPPS? Download Here!
Rom Source.
Device Source
XDA:DevDB Information
Plain-Andy, ROM for the Nexus 7
Contributors
Snuzzo, REV3NT3CH,Special mention: @RenderBroken @BaNkS
Source Code: http://github.com/Plain-Andy-legacy
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Gapps, Multi-Rom Compatible
Version Information
Status: Stable
Created 2014-09-25
Last Updated 2015-01-14

Standalone kernel downloads:
http://snuzzo.android-edge.com/Kernels/Funky-Kernel/grouper/
v1.6.2 is baked into the rom.
v1.6.1 is similar but without any wake(DT2W/S2W/S2S) controls.
New feature as of 10/10/14
Plain-Tweak:
Ever wanted to control your kernel from a file on your internal storage? Now you can! There are currently 3 different ways
1.) Manually create a text file on the root of /sdcard named 'plaintweak' with the following values:
gov=(your choice of governor)
maxkhz=(max cpu clockrate for all cores)
minkhz= (min cpu clockrate for all cores)
scheduler=(choice of IO scheduler)
tcpcong=(choice of TCP Congestion control)
2.)Invoking the instruction 'plaintweak' with adb shell or Terminal Emulator.
3.)Separate aroma package for your device(not yet created) or through the rom installer.
When I run 'plaintweak' from aroma package adb shell or Terminal Emulator wouldn't it get overwritten?
No! Not at all. Your old settings are saved at /sdcard/plain-tweak listed by date.
Don't like the values? Want a different configuration? Rather use Performance Control or another app?
Simply rename your current plaintweak file or copy an older plaintweak file to /sdcard root located in /sdcard/plain-tweak.
Custom Density
Currently 3 different ways to set
This can be controlled via the aroma package installer, abd shell/terminal emulator, or through placeholder file
/sdcard/customdensity that contains "customdensity=<value>"
If value is less than 180 it will not set. If value has a difference of 180 from default it will not set. May take 2 reboots to also set properly if using placeholder file only.
With adb shell/terminal emulator:
'buildproptweaks density *180 and up in values of 20
For example;
buildproptweaks density 200
then reboot
Custom bootanimation
Must be 720x1080 and placed at /sdcard/bootani/bootanimation.zip
Bootanimation disabling
There is 3 different ways to disable it.
1. Through aroma installer package
2. With adb shell/terminal emulator:
2a. type in 'bootanimation' it will toggle
2b. type in 'buildproptweaks bootanim [en|dis]able'

Nice Name Will try it later
Gesendet von meinem Nexus 7 mit Tapatalk

Rom Download Link?
---------- Post added at 07:28 AM ---------- Previous post was at 07:25 AM ----------
chaostrodamis said:
Rom Download Link?
Click to expand...
Click to collapse
Sorry found it

Updated post #2 with link to the standalone kernel installer.

what feature does this rom include and will your kernel be updated. Your kernel with deadline/lionheart combo has me going 3 days no charge easy with more then 50 percent screen on time.

"Don't fix what's not broken" the kernel is working great.
The actual features have not been implemented yet.

Snuzzo said:
"Don't fix what's not broken" the kernel is working great.
The actual features have not been implemented yet.
Click to expand...
Click to collapse
Absolutely right. Kernel works great. Will wait patiently for rom update thanks for the reply and the Rom Dev.
Sorry to ask, but might not be the only one. would you mind setting screen wake controls to default as off in you next kernel update. lags system and screen wake up. users can turn on if wanted. Just request to a busy dev. thank you

chaostrodamis said:
Absolutely right. Kernel works great. Will wait patiently for rom update thanks for the reply and the Rom Dev.
Sorry to ask, but might not be the only one. would you mind setting screen wake controls to default as off in you next kernel update. lags system and screen wake up. users can turn on if wanted. Just request to a busy dev. thank you
Click to expand...
Click to collapse
Once I get more users to request that. I will.
OP updated to reflect proper hosting for downloads and special mention to @CPA Poke for his autodetection of EXT4 & F2FS.

@chaostrodamis
Oh I forgot to mention. 1.6.1 had DT2W disabled. All future updates will have my latest baked in, so for now use that version.

Gave a quick 10/1 build. Not much changed but did want to start rolling out weeklies.

Snuzzo said:
Gave a quick 10/1 build. Not much changed but did want to start rolling out weeklies.
Click to expand...
Click to collapse
any features or changes worth mentioning?

chaostrodamis said:
any features or changes worth mentioning?
Click to expand...
Click to collapse
Only thing notable that applies to this device, battery lock around lockring . Found in Settings -> Security. A couple frameworks opts. Removed Documents file manager in favor of Slim explorer.

Hello,
Sorry for asking a noob question, but what would the order of steps be to use this rom after converting a nexus 7 to f2fs?
Do I need to use LegoKernel or can I use the kernel given here? I was thinking I might have to use the instructions at this post, under "If you didn't switch to F2FS and want to do it now," but I'm not sure.
(to clarify: the nexus 7 is not currently f2fs, running an older omni nightly)

All you have to do is make sure your setup for All-F2FS. My kernel is setup to handle the rest, and the installer detects what partitions are f2fs. You can actually be using an ext4 setup to use the ROM too. So nothing really special needed. Just wipe your /data apps and /system then flash ROM and gapps.

one more stupid question, is flashing the boot.img and recovery.img required as part of flashing the rom?

Rimmir said:
one more stupid question, is flashing the boot.img and recovery.img required as part of flashing the rom?
Click to expand...
Click to collapse
Uploaded for my safekeeping only. If I need them later.

thank you for your fast replies

Rimmir said:
thank you for your fast replies
Click to expand...
Click to collapse
I have a decently sized update coming in the next build. See if you like the ROM in it's current state. The next build there is going to be some changes that could effect the user base of the ROM itself. If you don't like dt2w, flash kernel v1.6.1 as its disabled by defaulted.

Welcome new bootanimation credits to @scar45

Related

[KERNEL] Chacha kernel 2.6.35.14 by Tokafondo.

Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Edit:
You have to copy the files inside modules.zip to
Code:
/system/lib/modules
. Thanks to johan111 for pointing to this.
tokafondo said:
Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Click to expand...
Click to collapse
very very good mate ! , but how can i flash it? from fastboot or ? , and what about swap tested? on stock rom?
mohabmoka said:
very very good mate ! , but how can i flash it? from fastboot or ? , and what about swap tested? on stock rom?
Click to expand...
Click to collapse
Yes, you will have to flash it by using fastboot:
(remember to have a cwm backup just in case you want to reflash your original boot partition)
Code:
fastboot flash boot bootv6initd.img
Swap partition goes as second partition of SD card. Swapper2 will work to format it as 'swap' type.
hm, happy to see still chacha development is active....did anyone tested it?
eager
ajeevlal said:
hm, happy to see still chacha development is active....did anyone tested it?
Click to expand...
Click to collapse
I'm eager to try it but I just love your port man, I will get a new phone in march so I will have the time to test more things on my chacha
hm i tried to build kitkat but it didnt work and it needs more knowledge than what i have.... and if we can keep the kernal up to date, may be some issues in custom rom might get fixed (HOPE)
nice
ajeevlal said:
hm i tried to build kitkat but it didnt work and it needs more knowledge than what i have.... and if we can keep the kernal up to date, may be some issues in custom rom might get fixed (HOPE)
Click to expand...
Click to collapse
keep it up mate, kitkat cannot beat you! j/k Jelly Bean is already an amazing rom
swashie said:
keep it up mate, kitkat cannot beat you! j/k Jelly Bean is already an amazing rom
Click to expand...
Click to collapse
you could do it man !!
tokafondo, I haven't really taken a look at your kernel yet, but I recommend you take a look at the OWL project kernel, as well as Luzifer1984's forks. Might help you gain some insights into rom features and functionality for the future.
honestly, I'm really surprised nobody has forked OWL project's stuff and compiled all of it for the ChaCha yet. They even have an updated ClockworkMod, which if compiled correctly, should work with our device.
Seems their 10.1 roms are also stable, and most if not all features of the device work.
here's the link to their kernel: https://github.com/JDevs/OWL-Predator-KERNEL
and here's Luzifer's github page: https://github.com/Luzifer1984?tab=repositories
there's also Adlx's stuff, which has been very successful so far: https://github.com/adumont/htc-kernel-msm7227/
I'd really love to see a decent, fully stable, feature rich kernel with great battery life for the ChaCha.
As I said, I haven't tried yours out yet, but will definitely give it a look in the next few days!
kronflux said:
tokafondo, I haven't really taken a look at your kernel yet, but I recommend you take a look at the OWL project kernel, as well as Luzifer1984's forks. Might help you gain some insights into rom features and functionality for the future.
honestly, I'm really surprised nobody has forked OWL project's stuff and compiled all of it for the ChaCha yet. They even have an updated ClockworkMod, which if compiled correctly, should work with our device.
Seems their 10.1 roms are also stable, and most if not all features of the device work.
here's the link to their kernel: https://github.com/JDevs/OWL-Predator-KERNEL
and here's Luzifer's github page: https://github.com/Luzifer1984?tab=repositories
there's also Adlx's stuff, which has been very successful so far: https://github.com/adumont/htc-kernel-msm7227/
I'd really love to see a decent, fully stable, feature rich kernel with great battery life for the ChaCha.
As I said, I haven't tried yours out yet, but will definitely give it a look in the next few days!
Click to expand...
Click to collapse
Thanks. I'm not that into the trying to port or get things to be done in ChaCha for fun. I don't see the benefit of having the latest version of Android working just because I could be done. 2.3.5 and Sense does the trick and allows me to work with my phone.
I would like to have some external reports of success or failure with my kernel. I did it for myself but though others could also benefit from it -- if there is a benefit at all.
kernel tested - no WiFi
I have tested your kernel and found WiFi error. This prevents WiFi activation. I tried with this ROM http://forum.xda-developers.com/showthread.php?t=1644087 and with this one http://forum.xda-developers.com/showthread.php?t=1690088.
johan111 said:
I have tested your kernel and found WiFi error. This prevents WiFi activation. I tried with this ROM http://forum.xda-developers.com/showthread.php?t=1644087 and with this one http://forum.xda-developers.com/showthread.php?t=1690088.
Click to expand...
Click to collapse
My mistake!!! :silly:
You have to copy the modules included in the attached zip file to
Code:
/system/lib/modules
you should be able to connect to wifi after that.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
Click to expand...
Click to collapse
i cant file called sysinit in system/bin !! or i must create it and type the code inside it?
It's a text file you should create. Type in the code, set owner and permissions and you are done.
Custom Kernel Not Supporting on Chacha with Stock Rom (Rooted with Busybox)
tokafondo said:
Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Edit:
You have to copy the files inside modules.zip to
Code:
/system/lib/modules
. Thanks to johan111 for pointing to this.
Click to expand...
Click to collapse
The moment I install the provided zip, and reboots, the phone becomes un-stable and the screen flickers constantly with the icons.
Android :2.3.3
Stock Chacha Sense 2.1 based on India: 1.20.720.1
Kernel: 2.6.35.
Any help !!

[KERNEL][9305] HboKernel v0.3 - 02.02.2015 (NamelessRom 5.0)

Hi all​
Introduction
I cannot call myself a developer or a kernel master at all. I'm just good at discovering and learning new things and in fact that's the way my journey with kernels started. At this point I want to start a new thread for something different from my earlier work, porting Boeffla kernel.
Features included:
Compiled with 4.9 Linaro toolchain
CPU OC up to 1600Mhz
ZZmoove as default governor (with moderate profile) - best for smoothness/battery life
Zen and Row I/O schedulers
Undervolting interface introduced
Configurable Touchboost
Configurable Touchwake
Charging interface
Boeffla Sound 1.6.6
Dynamic Fsync
Switchable Sharpness Tweak
Led configurable (fading, strength)
Configurable Android logger
Configurable printk logging
Readable: asv level, CPU temperature
Disabled some debug
Few minor tweaks (check github if interested)
If I forgot something - Github is up !
What kernel features may we expect?
F2FS support
Dualbooting support (if I can handle it properly)
What you say?
Compatibility
Flash only on proper roms!
As for now we have only Lollipop version, compatible with NamelessRom (you may try with others LP).
Download
You can download the most recent kernel here -> Click
Source
Github link - Click
Credits
These men never refused to give me a helping hand, advised me what to do and, more important, without their work this kernel wouldn't even exist (opensource doesn't mean no respect!).
@JustArchi
@Lord Boeffla
@Yank555
@ZaneZam
@arter97
Samsung :good:
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can't and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash anything.
Camera bug info: (hidden, only applies to Samsung ROMs)
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solutions:
Option 1 is good for people that rarely change their ROMs (and it fixes EVERYTHING), whether option 2 is better for people changing their ROMs more frequently (however, it's always good to have backup of your SlimISP on sdcard).
Option 1. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my HboKernel
Option 2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Option 3. Read this thread and follow steps --> click
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
I say, may good luck be with you accomplishing these features in the kernel :good:
Best of luck with this project Hbohd
Thanks to you, there is some life potential remaining for i9305!
Long life to i9305 and may the (dev) force be with you HboHd!
Thanks for your work!
+1 Nice one.
Hbohd said:
What you say?
Click to expand...
Click to collapse
I say: it's freaking interesting!!!!
Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3
aaz03 said:
Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3
Click to expand...
Click to collapse
Hmm.. Isn't 'Screen mode' under Display settings enough? It gives a little bit of difference without need of additional kernel's code modification.
New alpha 0.1
Okay, to keep this project alive, to show off some progress step by step and to satisfy flashoholics - I've decided to release my small achievements in form of alpha kernels
Firstly, let's restart naming convention of the kernel. It will be simple x.x now, starting from available below 0.1 version :cyclops:
Small changelog:
removed debugging in many places
compiled with linaro 4.9
few tweaking commits
Let's say that due to my 'stupidity' or magic ability to forget something, I've spent on it many hours today :silly:
Is Insecure ADB fixed?
Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin
This is for old bootloader only?
SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..
@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!
ShonkUK said:
SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..
Click to expand...
Click to collapse
sham79 said:
This is for old bootloader only?
Click to expand...
Click to collapse
I haven't stated anything different from what is true I mean, if I write that you can you use it with new bootloader or SE is disabled - then it would be true
I think that in next release I will disable it (simply forgotten due to my compiling problems mentioned earlier).
Oh, and I don't need another changelog when everything is written in the git I haven't just suceeded in uploading it to the github yet :/
machotecba said:
@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!
Click to expand...
Click to collapse
Yeah, someone mentioned it already. I will try to fix it for next version, thanks!
djb77 said:
Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin
Click to expand...
Click to collapse
Will be in for the next so-called 'alpha'
Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?
fpriot said:
Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?
Click to expand...
Click to collapse
Yep, you are right
If I may suggest @Hbohd... Could you please start with the power features implementation? Charging rates, ignore unstable power and margin...
Because these are the ones I really miss... My chargers and/or cables are not good and I need these mods to charge properly...
Thanks!
Firsty thanks for all your hard work.
The phone no longer charges from the car dock. This was the same for the stock kernels in 4.1.2 & 4.3 - still withold bootloader. 4.1.2's was fixed with Pegasus kernel and 4.3 was fixed by your Beoffia 5 kernel.

ViPER4Android Universal Fix CM13 Android 6.0/+

So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.
Can i flash it on android one device running on 6.0.1
Yes. If you have any issues, please let me know!
rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:
It works great. thanks.
my bad for not following the instructions.

[ROM][SM-G313H/HZ/ML]CyanogenMod 13 for Samsung Galaxy V

The original development thread is here. Since @doesntexits does not develop for this phone any more, I asked him to make this clone and he accepted.
CyanogenMod is a free, community built, after-market firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
BEFORE INSTALLING THIS ROM, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE
IF YOU ASK ANY QUESTIONS LIKE "IS THIS FOR MODEL BLABLABLA" THEY WILL BE ALL IGNORGED
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
We'll not support users and answer questions from users which:
Are running a custom kernel
Have flashed mods
Modified system files
Didn't follow our instructions word by word
Are unfriendly
And most important: DON'T READ THE OP
What's working:
RIL (Calls, SMS, Mobile data)
Wifi (connection, tethering)
Bluetooth
Camera, video codecs
Storage (internal, external and adoptable storage)
Offline charging
zRAM (compressed-RAM swap)
GAPPS
Tethering (USB, Wifi, Bluetooth)
GPS (except Device Only mode)
Torch (flashlight)
WiFi-Direct
SELinux enforcing
LZ4 compressor/de-compressor for zRAM
BUGS/Not working:
FM radio app FC (due to missing libraries)
Distorting sound when using Bluetooth headset in call or in recording
First time installing CyanogenMod 13 to your Galaxy V, or coming from another ROM:
Install TWRP Recovery
Reboot into Recovery using 3-button-combo (Vol-up+Home+Power)
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)*
Install the ROM from sdcard using TWRP Recovery
Optionally install the Google Apps ( get it here: https://opengapps.org ) (pico GAPPS recommended) (*)
(*) NOTE: If you're about going to install GAPPS with ROM, install it right after you've installed the ROM, else you have to do a factory reset if you've booted the ROM first
Mirrors:
Stable-1: MF
XDA:DevDB Information
CyanogenMod 13, ROM for the Samsung Galaxy Ace 4
Contributors
ngoquang2708, doesntexits
Source Code: https://github.com/ngoquang2708/android_device_samsung_vivalto3gvn/tree/cm-13.0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 4.4.2
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2016-09-12
Created 2016-08-28
Last Updated 2016-09-12
Reserved
CHANGELOG
ALPHA-1
Initial release
BETA-1
Fixed RIL, switched to beta builds
Switched to AOSP charging module
Fixed screen flickering
Fixed audio
BETA-2
Fixed screen flickering.
Fixed audio, now you can maximize your volume!
BETA-3
Fixed AudioFX
Fixed WiFi auto-disconnect
Working WiFi-Direct
No more "lock" at Setup Wizard
SELinux is now in Enforcing mode
BETA-4:
Fixed battery drain
Added lz4 compressor/de-compressor for zram
STABLE-1:
Fixed GPS (except Devide Only mode)
Fixed mobile data switching
Reserved
F.A.Q
Q: ROM startup too slow?
A: This device is just a single-core phone, so the first startup is super-duper slow, and some lags are expected during usage
Q: ETAs?
A: See here: Link
Q: Anymore models supported?
A: SM-G313ML, SM-G313H
Q: Is init.d supported on this ROM?
A: Every CyanogenMod ROMs support init.d, so be free at scriptings
Q: Can you include ABCXYZ feature / Samsung Apps here?
A: NO!
Q: Can i use your ROM as a base for portings?
A: Yes, you could, but give proper credits
Q: Status 7 when installing the ROM?
A: Use TWRP recovery to install the ROM, as CWM is not supported yet
Q: Server error in Google Play Store?
A: Install latest Google Play Services manually first (might take long time, due to Lollipop's nature), then you can install apps from GG Play as usual
Q: How to use adoptable storage feature? I see it's new in Marshmallow
A: Go to Settings >> Storage & USB >> Tap on the SD card label (not the eject icon) >> 3 dots menu on the top right >> Settings >> Format as internal and done!
Q: Where's the MTP option in Marshmallow? I don't see it in Storage settings
A: This feature has been moved to Developer settings, and will reset to default (Charging) after every reboots. Enable developer options first by tapping 7 times on Build number in About phone section >> Go to Developer settings >> Select USB configuration. The fastest way to do this is plug in your USB with your PC, scroll down notification bar and tap on "USB for Charging"
Q: Where's the "running" section in Apps settings?
A: It has been cut off separately to Memory setting and "Running services" in Developer settings. You can see the memory used by apps for a period of time and closing apps too, but they won't disappear in the menu, and in "Running services", still same as old-fashioned running apps section
@ngoquang2708 said in the CLOSED THREAD: I do not think screen lock when you are pulling the notification drawer is a bug. You have to unlock your screen to do things, right?
About "wakelock", didn't I fix it, or you misstyped it?
Man, you did fix that wakelock thing in the Beta 3, but it's happening someting similar with me (that why I thought it has a wakelock thing), when I click on the bottom of the screen happens that damn thing showed in the screenshot (only when i click in the bottom).
I wonder if I'm the only one with this problem, this has happened with you @ngoquang2708?
Hey bro, hopefully soon solve the problem of GPS, lock screen and the annoying message from the SIM Card
Thank you so much for your work
Not work for my the module aosp offline charging
Hi. I tried installing SuperSu but it keeps on failing, the Su binary can't be installed for some reason. I tried rebooting as it says but still gives the same error. I already enable the root access in developer options and gave permission but it just doesn't work, is there any fix?
Also can I install OC Kernel? I would love to overclock a bit if i can?
Any help would be greatly appreciated!
Thanks in advance guys!
JominatorX said:
Hi. I tried installing SuperSu but it keeps on failing, the Su binary can't be installed for some reason. I tried rebooting as it says but still gives the same error. I already enable the root access in developer options and gave permission but it just doesn't work, is there any fix?
Also can I install OC Kernel? I would love to overclock a bit if i can?
Any help would be greatly appreciated!
Thanks in advance guys!
Click to expand...
Click to collapse
Why do you want SuperSu on CM? It isn't supported
For now you can't install OC kernel, as the ramdisks are outdated. I'll make a ZIP for all ROMs now
doesntexits said:
Why do you want SuperSu on CM? It isn't supported
For now you can't install OC kernel, as the ramdisks are outdated. I'll make a ZIP for all ROMs now
Click to expand...
Click to collapse
Oh I see, I just feel like SuperSu is better than the privacy guard. I'll look forward on the updated OC Kernel, Thanks a lot Dev!
JominatorX said:
Oh I see, I just feel like SuperSu is better than the privacy guard. I'll look forward on the updated OC Kernel, Thanks a lot Dev!
Click to expand...
Click to collapse
I have updated OC kernel link. Can you check it out?
This time the kernel doesn't need ramdisk, so it can be easily replaced between all ROMs
doesntexits said:
I have updated OC kernel link. Can you check it out?
This time the kernel doesn't need ramdisk, so it can be easily replaced between all ROMs
Click to expand...
Click to collapse
I downloaded it but still waiting for my phone to boot up, I flashed xposed and its optimizing apps now. Usually take around 30mins or so on other roms. Probably the same with cm13.
doesntexits said:
I have updated OC kernel link. Can you check it out?
This time the kernel doesn't need ramdisk, so it can be easily replaced between all ROMs
Click to expand...
Click to collapse
I have just flash OC kernel and it booted up just fine. I still dont have apps/games installed so I cant tell if the soft reboot still happens.
Which i/o scheduler and governor is the best for gaming btw?
JominatorX said:
I have just flash OC kernel and it booted up just fine. I still dont have apps/games installed so I cant tell if the soft reboot still happens.
Which i/o scheduler and governor is the best for gaming btw?
Click to expand...
Click to collapse
What app did you use in those screenshoots?
ngoquang2708 said:
What app did you use in those screenshoots?
Click to expand...
Click to collapse
Kernel Auditor. It's free and light.
JominatorX said:
Hi. I tried installing SuperSu but it keeps on failing, the Su binary can't be installed for some reason. I tried rebooting as it says but still gives the same error. I already enable the root access in developer options and gave permission but it just doesn't work, is there any fix?
Also can I install OC Kernel? I would love to overclock a bit if i can?
Any help would be greatly appreciated!
Thanks in advance guys!
Click to expand...
Click to collapse
Try to activate and deactivate the Root Permission again in Apps and ADB or Apps Only, and then give Root Permission when it asks (it worked for me when I was with this problem).
---------- Post added at 09:43 PM ---------- Previous post was at 09:08 PM ----------
JominatorX said:
I have just flash OC kernel and it booted up just fine. I still dont have apps/games installed so I cant tell if the soft reboot still happens.
Which i/o scheduler and governor is the best for gaming btw?
Click to expand...
Click to collapse
I recommend you see this guide thread about the CPU and I/O Scheduler: http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
About the best CPU, I/O Scheduler, i'm not sure but, let me give you a example: When i play in Drastic DS Emulator and switch the CPU and I/O to another one than the default, the screen freezes in the middle of the game and defrost later (about 30secs and 1min), but when I play in the default (Intelliacive/BFQ) it goes smoother with no screen freezes.
I had read about the new Systemless Root by Chainfire, it can root (and install Chainfire Supersu of course) without modifying system, it done with flashing mod boot.img ... Anybody try in this ROM ? Or it is not supported ? Or it is pointless ?
Sent from my SM-G313HZ using Tapatalk
any way to change the path of the external sd, change the path in format numeric for this "storage/extSdCard"
well is that it is not possible restore backup user apps from titanuim the option to extract a backup nandroid. Thanks in advance
Idayrad said:
I had read about the new Systemless Root by Chainfire, it can root (and install Chainfire Supersu of course) without modifying system, it done with flashing mod boot.img ... Anybody try in this ROM ? Or it is not supported ? Or it is pointless ?
Click to expand...
Click to collapse
No need to do that, you just need to download and install supersu from the play store. After installation disable and re enable root access make sure its apps and adb. Worked for me.
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
DavidGR15 said:
any way to change the path of the external sd, change the path in format numeric for this "storage/extSdCard"
well is that it is not possible restore backup user apps from titanuim the option to extract a backup nandroid. Thanks in advance
Click to expand...
Click to collapse
You should format it as portable.
jesusadolfog said:
Hey bro, hopefully soon solve the problem of GPS, lock screen and the annoying message from the SIM Card
Thank you so much for your work
Click to expand...
Click to collapse
What kind of annoying message? A screenshot would help.
I can port?
Hi my friends! I would port for my device (SM-G318ML) I Can port and modify?

[ROM][7.1.2_r36][grouper][OC 1700MHz/F2FS]Resurrection Remix 5.8.5 for Nexus 7 2012

*** 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.

Categories

Resources