Database Users

fast rom?

whats the fastest wildfire rom at the minute? sense or no sense doesnt really matter? like cyanogen or something, my phone is really slow at the minute which is really annoying me

wild puzzle, put an overclocked kernal on and use SetCPU to overclock, that might speed your phone up a bit.
Thats what i would do.

chrish2008 said:
wild puzzle, put an overclocked kernal on and use SetCPU to overclock, that might speed your phone up a bit.
Thats what i would do.
Click to expand...
Click to collapse
wth? cm7 by far...
Sent from my HTC Wildfire using XDA App

cm6 had bad graphics due to resolution on my WF is cm7 better res for WF?

Iv just tried cm7 and it lags, fcs and reboots like mad from a clean install

rosswaa said:
Iv just tried cm7 and it lags, fcs and reboots like mad from a clean install
Click to expand...
Click to collapse
It is probably a kernel issue. Try reusing HCDR.Kernel v4.1 from it's specific thread. Apart from that, you can try Openfire ROM as well, which is a completely vanilla AOSP build.

cold it be that rom manager didnt wipe properly? iv just manualy gone through and wiped everything and it hasnt crashed on me yet,
i thought the kernel would be flashed fresh from cm7?

rosswaa said:
cold it be that rom manager didnt wipe properly? iv just manualy gone through and wiped everything and it hasnt crashed on me yet,
i thought the kernel would be flashed fresh from cm7?
Click to expand...
Click to collapse
Yes, it is always recommended to wipe it manually through the Recovery Menu. You have to wipe data, cache, dalvik cache and /system for best results before installing a new ROM.
As for the kernel, yes, it is included by default in CM7, but it is v4.2. Using v4.2 has caused some stability issues for some members, and, in that case, it is recommended to revert back to kernel v4.1

yeh thanks for that info, was a kernel issue i hope, all been goin good so far

strange, cause the only difference between 4.1 and 4.2 is the wifi driver.
Sent from my HTC Wildfire using XDA App

Well since using the 4.1 keen every thing is working perfect, nice and fast no fcs or random reboots.
Well my mate said I have a desire hd and thank god I do, couldn't handle the wildfire lol

do not forget to enable jit
Sent from my HTC Wildfire using XDA App

Have done

Cm6 and Cm7 is a bit not very stable for me, have to reboot one or two times a day. Maybe I'll switch to other.

you are doing it wrong, cm7 is really stable. I m using nightly 19 for weeks without any problems.
Sent from my HTC Wildfire using XDA App

Don't think so, do a wipe data,system,darkvik cache, flash #53, boot in, first time ADW FC. reboot, flash 4.1 kernel, boot again, ADW FC again
I can reproduce it everytime, lol

I used CM the last two weeks..
Yesterday I went to the new CM7 Rc1 then i moved to Openfire..
it's very stable and fast, even without setCPU.. i've just backup all my apps and it is wonderful..
The last cyanogen seems to be quite slow sometimes..

Recommend a new rom for me!

All that matters to me is speed, stability and battery life.
I have been running Darkys 9.2 for a long time now, but the battery life is getting to be very poor, so looking to try out something new.
Appart from the battery life if has been rock solid to date.
Any advice is welcome
Sent from my GT-I9000 using XDA App

"All that matters to me is speed, stability and battery life."
...bit like saying "all that matters is health, wealth and happiness"
There are plenty out there and only one way to find out, happy flashing
Sent from my GT-I9000 using XDA App

In my opinion, there isn't a perfect rom in this world which matches your description. However, if I were to choose one, I would choose Cyanogenmod 7. It is currently on Nightly, but it is stable enough for daily usage. Battery life is not that good, but its speed complements it, combined with loads of customisations available.
I hope that helps, mate
Sent from my GT-I9000 using XDA App

djglenn1337 said:
All that matters to me is speed, stability and battery life.
Click to expand...
Click to collapse
So why not flash stock odexed JVQ without any modifactions?

Try s.u.f.a.ce rom .Its a base rom with addons I installed the base and manually extracted and installed what I wanted from the addons. Almost a build your own without being a developer. Fastest rom ive tried with best battery because its light
Sent from my GT-I9000 using XDA App

kb909 said:
Try s.u.f.a.ce rom .Its a base rom with addons I installed the base and manually extracted and installed what I wanted from the addons. Almost a build your own without being a developer. Fastest rom ive tried with best battery because its light
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This ^
Ive tried a bunch, I only flashed this ROM cuz Sam ported a theme I liked ended up liking the ROM since its a barebones ROM
Other then that ROM Id go with just a stock JVQ, Ive always fallen back to the stock ROMs after not liking something about the customs I installed

Thanks guys will give s.u.r.f.a.c.e a shot!
Just out of interest, does it have a lagfix like Darkys rom?
Cyanogen's battery issues are keeping me away from it for now.
I have it on my wife's wildfire and its a completely new animal since I flashed it.

djglenn1337 said:
Thanks guys will give s.u.r.f.a.c.e a shot!
Just out of interest, does it have a lagfix like Darkys rom?
Cyanogen's battery issues are keeping me away from it for now.
I have it on my wife's wildfire and its a completely new animal since I flashed it.
Click to expand...
Click to collapse
Yes it does

F1 Galaxy S2 V6
no battery drain and smooth with galaxianEE2.4 kernel

GingerReal 7.1.4 , Semaphore 1.3.3. kernel, works briliant-e.

Search: Android Development topic

Stock is the best...

In the past weeks i tested several roms and kernels.
Roms: GingerReal 7.1.4, Surface 2.1, Juwe 5.2, CM7, Darky 10.2
Kernel: Speedmod, Galaxian, Semaphore
For me the best pair is Darkys Rom with the semaphore kernel on EXT4.
I never had such a smooth, speedy and long battery usage on any rom/kernel.

Low voltage kernels

Just rooted. Im new to the droid world, so im curious, can i get a low voltage kernel? A friend has Savage Zen and brags about battery life, but would it be compatible with my default-rooted rom? Also can i backup the kernel? Thanks.
Btw i tried googling but every time i got a good lead the links were dead
Sent from my HTC Evo 4G [rooted] Sprint 2.3.3(stock, came preinstalled) hardware v.4 bought new in July.

If you are referring to a rooted, stock HTC Sense ROM, no, do not use SavagedZen. It is only for AOSP ROMs.
AOSP - Android Open Source Project (vanilla, like on the Nexus)
Sense - HTC's UI
You cannot use a Sense kernel on an AOSP ROM, or an AOSP kernel on a Sense ROM.
(All Gingerbread)
AOSP Kernels:
Tiamat
SavagedZen
Cyanogenmod (kernel)
Godmode
PoonKang
I know that Tiamat and SavagedZen have HAVS and can be undervolted using Vipermod. Cyanogenmod, Godmode and Poonkang may come undervolted, but they do not have HAVS so you cannot adjust it.
Sense Kernels:
Freedom by Lithid
Golden Monkey by Netarchy
ChopSuey by barnacles10
Stock HTC
None of these kernels have HAVS (Freedom used to, but it was causing issues so he took it out). Golden Monkey, ChopSuey, and Freedom can come undervolted by certain degrees, it depends on which version of the kernel you download.
I can't think of any way to back up a kernel except for nandroiding system, but I am probably wrong. Just go into recovery, wipe cache and dalvik and flash a new kernel if you have any issues.
There is a good study guide in I think Q&A stickied, telling all that you need to know about kernels. I advise you to read it. Link: http://forum.xda-developers.com/showthread.php?t=894880

tropicalbrit said:
I can't think of any way to back up a kernel except for nandroiding system, but I am probably wrong. Just go into recovery, wipe cache and dalvik and flash a new kernel if you have any issues.
Click to expand...
Click to collapse
You can usually recover a bad kernel by flashing to back to the stock kernel and wiping cache and dalvik. Its usually worked for me, but depends on how much the custom kernel changed things.
To OP, go check out Kernel Manager in the market. It takes a good amount of the guesswork out of kernel flashing.

I say go with chopsuey 9.1 ill say its really good left my phone off charger for 8 hours while i slept was at 41% before and when i woke up it was still at 41% i mean does it get anybetter than that

Thanks for the help. Really in depth and helpful advice . Using freedom aggressive kernel now. Still testing to see if it helped. Great forums.
Sent from my HTC Evo 4G [rooted] Sprint 2.3.3(stock, came preinstalled) hardware v.4 bought new in July.

nscollab/cyanogenmod - the need of a stable kernel

Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael

it was the same for me. nscollab was unusable since it was always freezing in two minutes after boot. changing the kernel did not help. so I decided to change the rom to Nexus MV 10.05. it works very stable (not a single reboot or freeze) and faster than nscollab.

mikkkg said:
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
Click to expand...
Click to collapse
Well, I found that custom kernels can work with stock ROM's. I'm using stock Google 2.3.6 on my 9023 + pete's kernel with Voodoo sound and BLN. Stable as ****, practically no issues, I'm happy with my NS as never before just because of the lack of constant flashing the **** around to "optimize". It just works flawlessly.
Here's the link to the kernel : http://www.peteralfonso.com/2011/08/download-nexus-s-263514-kernel.html

Had the no wake issue with cm7 216 and nscol 1.4.5. On nscol 1.4.6 and no problems yet. If it happens again it would seem to be a cm7 issue. While annoying devs are constantly hunting down and correcting problems, just the way it is and doesn't bother me.
Sent from my Nexus S using xda premium

Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App

The hole point for me is not using any other kernel but the stock one.. compile yourself a nexus s kernel (google it for how to) and be happy without any reboot, crash..
baterry? normally 1.5 days @ 1.0ghz..

You could do that as well
Sent from my HTC Sensation 4G using XDA App

mathkid95 said:
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
.45 with stock voltages caused the "pin asking" issue even with stock voltages(even with 5.5 cfs - maybe a cyanogen problem?), so that's why i am stuck at .42 with 5.5 cfs and did not even try .46.

Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App

mathkid95 said:
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
If you see, in the thread of nscollab, there are also problems with the phone dying etc, even with the new stable cyanogenmod + matr1x kernel.
I only do tests in my mobile during the weekend, because i use it all week for my job. So stuck with matr1x 5.5 until i see a really stable matr1x kernel coming after 8.

madd0g said:
Here's the link to the kernel :
Click to expand...
Click to collapse
Thank you very much for posting this link. I did not know that kernel. I just found some time to flash nscollab .50 with this kernel and i only changed interactive governor with ondemand to be even closer to stock kernel.
I hope that it is as stable as it is for you.

After some hours with this new kernel, i am not sure about stability(although it seems stable) but nexus is running smoothier than ever.

I've used ondemand from the beginning I started using this kernel, then I tried interactive (default) just to try it out. Not really a difference, same stability/speed and I could get rid of NoFrillsCPU app setting the default governor at startup. So to wrap up, kernel runs beautiful from the start, no extra fiddling necessary.

I do not believe the issues described in the OP are kernel related. They persist in all custom kernels. I think it is from Dalvik VM crash but I have no proof.
Sent from my Nexus S using XDA App

http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.

After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.

Id say if you want stability, stay on stock, extra features like BLN and Voodoo sound are added via kernel anyway.
Sent from my Nexus S using Tapatalk

mikkkg said:
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Click to expand...
Click to collapse
Kalimocho found a kernel error and a missing vendor file in the CM kernel. It will be fixed in the next nightly. The hope is that this was the cause of the freezes/reboots/bootloops/dimscreen bootloops that people were seeing.

mikkkg said:
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
Click to expand...
Click to collapse
I use this, if it helps you.
Thread here.

mikkkg said:
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
Click to expand...
Click to collapse
lol i keep looking but i dont find anything
ahhhh

smooth and fast in nexus 6p

Wich ROM, mod, kernel or combination of two of them give me the best experience in android?? I m looking for an Android system fast, smooth and best battery life. Thanks to all

If something was the best, nothing else would be used as there's no point in using something that's inferior when you can get something better.
There is no best, I suggest you read each thread and pick one that suits your needs. Saying X ROM and kernel is the best is like saying a specific vehicle is the best...One may say a Ferrari and another may say an F-350. But who's right?
Some people like roms and kernels bloated with 1000 customization options filled with placebo "optimization and enhancements". Others prefer a clean, minimal ROM without all the useless bling that they'll never use.
P.S. there's probably 10 threads like these, and possibly 11 by next week that you could've read through. I'll just copy and paste this same post on the next one.
Sent from my Nexus 6P using Tapatalk

Currently using PureNexus nougat with ElementalX kernel. The experience is pretty good.
Using the phone for SMS/MMS, YouTube and web browsing. I can get ~ 5/6h sot with a full charge on WiFi and ~ 3h30 sot on 3g/LTE which is enough for me.
Also using custom CPU governor profile in EXKernel Manager helped me with battery life without affecting performance (at least not that I noticed). You can find more infos here:
https://forum.xda-developers.com/nexus-6p/general/guide-advanced-interactive-governor-t3290605
Hope that helps

I am using the stock ROM with the ElementalX Kernel. Very happy with the performance of the phone. I arrive at the end of the day with 40% battery on average

yamilmanzur said:
I am using the stock ROM with the ElementalX Kernel. Very happy with the performance of the phone. I arrive at the end of the day with 40% battery on average
Click to expand...
Click to collapse
Wich version of stock are using?? I was use that option but I had some issue with stock.

5.1 said:
Currently using PureNexus nougat with ElementalX kernel. The experience is pretty good.
Using the phone for SMS/MMS, YouTube and web browsing. I can get ~ 5/6h sot with a full charge on WiFi and ~ 3h30 sot on 3g/LTE which is enough for me.
Also using custom CPU governor profile in EXKernel Manager helped me with battery life without affecting performance (at least not that I noticed). You can find more infos here:
https://forum.xda-developers.com/nexus-6p/general/guide-advanced-interactive-governor-t3290605
Hope that helps
Click to expand...
Click to collapse
Thanks for your answer. I had a boot loop when I install pure Nexus, Gapps, ElementalX and super su. But I like this option. Wich Gapps recommend?

hpagliettini said:
Wich version of stock are using?? I was use that option but I had some issue with stock.
Click to expand...
Click to collapse
7.1.1 ROM stock

hpagliettini said:
Thanks for your answer. I had a boot loop when I install pure Nexus, Gapps, ElementalX and super su. But I like this option. Wich Gapps recommend?
Click to expand...
Click to collapse
Hi. Gapps included in the OP of thePureNexus thread. OenGapps will work too.

Another "best rom" thread? Seriously ?
Pure

F2FS + Dark ROM + FLASH kernel ! That's the best combination and I am a serial flasher

These people that are saying there isn't a best ROM, I don't really understand the reasoning behind this. There most certainly is a best ROM kernel combination. Otherwise all these ROMs and kernels would be exactly the same right? Sorry to say, some are better than others. This is just a fact.
If you want speed, smoothness, glass, breakneck speeds, great battery life, there really is one only choice.
Uber rom by Chad and faster kernel by Chad.
Why?
On f2fs, (trust me, you want f2fs) I have yet to find kernel or ROM combination that beats this.
Its the only rom that's built with GCC 6.3.1, and the only rom built with clang 3.9.1. Coupled with f2fs, this rom FLIES.
I have flashed every single ROM on this forum and then some, and I'm telling you this is the best combination you can possibly hope for:
https://temp.bbqdroid.org

NOTilyass said:
F2FS + Dark ROM + FLASH kernel ! That's the best combination and I am a serial flasher
Click to expand...
Click to collapse
How much sot do you have with this combination?
You flash f2fs + dark ROM + Gapps + flash kernel in one time?

TrainNanpaMaster said:
These people that are saying there isn't a best ROM, I don't really understand the reasoning behind this. There most certainly is a best ROM kernel combination. Otherwise all these ROMs and kernels would be exactly the same right? Sorry to say, some are better than others. This is just a fact.
If you want speed, smoothness, glass, breakneck speeds, great battery life, there really is one only choice.
Uber rom by Chad and faster kernel by Chad.
Why?
On f2fs, (trust me, you want f2fs) I have yet to find kernel or ROM combination that beats this.
Its the only rom that's built with GCC 6.3.1, and the only rom built with clang 3.9.1. Coupled with f2fs, this rom FLIES.
I have flashed every single ROM on this forum and then some, and I'm telling you this is the best combination you can possibly hope for:
https://temp.bbqdroid.org
Click to expand...
Click to collapse
Uber rom by Chad I definitely agree is the best. I tried using his faster angler but it caused problems with mods like viper4arise so I am sticking with flash kernel. Uber by Chad is definitely the best rom though and I have tried so many roms like pure nexus, resurrection remix, dirty unicorns, sixRom, lineage, cyanogenmod, nitrogen, Cortex and so many more.

Is the stock camera working on either Uber or Dark ROM with f2fs file system?
Thanks

There's no such thing as a best rom fact, but only best rom opinions, which isn't a good idea to ever discuss here. [emoji14]
As for battery, that all depends on you as a user to manager your battery life your way. I get 4+ SOT easily and I listen to a lot of music and text a lot.
As for what I'm using, I'm running ABC Rom with franco.kernel, root, and V4A. ?
Sent from my Nexus 6P using Tapatalk

TrainNanpaMaster said:
These people that are saying there isn't a best ROM, I don't really understand the reasoning behind this. There most certainly is a best ROM kernel combination. Otherwise all these ROMs and kernels would be exactly the same right? Sorry to say, some are better than others. This is just a fact.
If you want speed, smoothness, glass, breakneck speeds, great battery life, there really is one only choice.
Uber rom by Chad and faster kernel by Chad.
Why?
On f2fs, (trust me, you want f2fs) I have yet to find kernel or ROM combination that beats this.
Its the only rom that's built with GCC 6.3.1, and the only rom built with clang 3.9.1. Coupled with f2fs, this rom FLIES.
I have flashed every single ROM on this forum and then some, and I'm telling you this is the best combination you can possibly hope for:
https://temp.bbqdroid.org
Click to expand...
Click to collapse
In this link I download the Uber ROM, right?
And other thing, you say me I have to flash to f2fs first before install this ROM and kernel?? Or I don't have to flash previous?

DEVILOPS 007 said:
Uber rom by Chad I definitely agree is the best. I tried using his faster angler but it caused problems with mods like viper4arise so I am sticking with flash kernel. Uber by Chad is definitely the best rom though and I have tried so many roms like pure nexus, resurrection remix, dirty unicorns, sixRom, lineage, cyanogenmod, nitrogen, Cortex and so many more.
Click to expand...
Click to collapse
I'm using faster kernel (r63) with Viper for arise with no problems at all bro. What's your steps for flashing?
I'm using 2.4 alpha B.

TrainNanpaMaster said:
I'm using faster kernel (r63) with Viper for arise with no problems at all bro. What's your steps for flashing?
I'm using 2.4 alpha B.
Click to expand...
Click to collapse
I basically just wiped cache and dalvik/art cache and flashed the rom and kernel and all my mods. I also made sure to do stuff like rename audio effects and everything I did to make it work with flash. I use stable 2.4 deutronomy aroma installer. I was talking to someone else on this rom and kernel and he said he had the same problem too so it might be hit and miss or maybe you flashed it different than us. Please tell.me what you did to get it to work. Thanks

What partitions do you guys convert to f2s besides cache? Data as well? Everything else remains ext4?

Running stock has been great for me lately. Downgraded to 6.0.1 running Xposed for pixel mods. Amplify and greenify. With exkernel has been a great experience so far. Near 7h SOT yesterday. Will be going back to 7.1.1 soon, as the February update is out.. I heard lineage OS has good battery life. Will be trying that out soon in a few days.
Read the threads on XDA and good luck!!:good: