[ROM][CM12.1][Lollipop][Android 5.1.1] NightOwl 20180124

[ashes]

Yes I am having issues with multitasking. Along with that, even there is some problem with battery life.
Anyhow, banner has done a great job with beta1.


Sent from my iPad using Tapatalk

Hi, I'm also facing the multi tasking issue. Tried to switch kernels but it's the same behavior.

Very laggy when switching apps

 

[abufrejoval]

Raw v7 kernel helped me run NightOwl

Going forth and back between OmniROM KK and NightOwl LP to sort out the SDcard issues I had (I was still running with a 2GB primary /data and ~10GB internal sdcard or simply the original TW partitioning), lost me the ability to boot NightOwn LP at one point or another: Not even a full wipe would get me past a dark screen after loading--somehow initial setup wouldn't start and the screen stayed black and dead.

Switched to Remix Resurrected, which had also worked at one point, but had the same SDcard issues *and* that also stopped working at one point, running the boot animation endlessly (went shopping in the mean-time), but never entering initial setup, even with factory reset.

Reflashing OmniROM always got me a working device, so there seemed nothing fundamentally wrong.

I then did the repartitioning to get a ~12GB /data (which leaves a tiny 1GB internal SDcard) under Omni (fully working) and re-installed NightOwl.
Again a black screen after a long initial boot.

Inspection using bauner's ODIN flashable TWRM's file manager always yielded fine looking /system, /data and /cache partitions, clean and complete as far as I could tell: The flashing seemed to generally work just fine.

And since the Raw v7 kernel included for Remix Resurrected gives a slightly more recent TWRM than the ODIN flashable version, I tend to flash that before I go back to OmniROM.

At one point I wasn't fast enough going into recovery and had the RAW v7 kernel boot a NightOwl ROM----and *that* did the magic thing in my case:
Suddenly it booted Lollipop in all its glory!

My only explanation would be, that there seems to be some extra data in the kernel partition left over from those other ROMs, which prevents these LP kernels from initializing properly. And flashing the RAW v7 kernel with the (slightly bigger/longer?) TWRM recovery included, cause that extra data (an initial RAM disk?) to be properly initialized.

Unfortunately none of the recoveries seem to include the ability to wipe the kernel partition and in the case of these "kernel attached recoveries", where recovery doesn't seem to sit in its own separate partition, I guess that would be a little hard or dangerous to do in any case.

So just in case somebody else runs into a similar issue: RAW v7 kernel works with NighOwl and gives you TWRM recovery and RAW v7 features without the optical "improvments" of Remix Ressurected.

 

[I_android]

I am facing a weird problem on my phone... and I think it's not because of this ROM particularly since i faced it on KK ROMs as well...
Sometime when I connect / disconnect charger all sensors stop working... light sensor, proximity sensor, autorotation etc... and it gets fixed after some time automatically or if I restart. It doesn't happen every time I connect / disconnect the charger.
Only on LiquidSmooth KK ROM it did not happen or happened very very rarely.

Anyone else face this issue?

 

[xirusnet]

Going forth and back between OmniROM KK and NightOwl LP to sort out the SDcard issues I had (I was still running with a 2GB primary /data and ~10GB internal sdcard or simply the original TW partitioning), lost me the ability to boot NightOwn LP at one point or another: Not even a full wipe would get me past a dark screen after loading--somehow initial setup wouldn't start and the screen stayed black and dead.

Switched to Remix Resurrected, which had also worked at one point, but had the same SDcard issues *and* that also stopped working at one point, running the boot animation endlessly (went shopping in the mean-time), but never entering initial setup, even with factory reset.

Reflashing OmniROM always got me a working device, so there seemed nothing fundamentally wrong.

I then did the repartitioning to get a ~12GB /data (which leaves a tiny 1GB internal SDcard) under Omni (fully working) and re-installed NightOwl.
Again a black screen after a long initial boot.

Inspection using bauner's ODIN flashable TWRM's file manager always yielded fine looking /system, /data and /cache partitions, clean and complete as far as I could tell: The flashing seemed to generally work just fine.

And since the Raw v7 kernel included for Remix Resurrected gives a slightly more recent TWRM than the ODIN flashable version, I tend to flash that before I go back to OmniROM.

At one point I wasn't fast enough going into recovery and had the RAW v7 kernel boot a NightOwl ROM----and *that* did the magic thing in my case:
Suddenly it booted Lollipop in all its glory!

My only explanation would be, that there seems to be some extra data in the kernel partition left over from those other ROMs, which prevents these LP kernels from initializing properly. And flashing the RAW v7 kernel with the (slightly bigger/longer?) TWRM recovery included, cause that extra data (an initial RAM disk?) to be properly initialized.

Unfortunately none of the recoveries seem to include the ability to wipe the kernel partition and in the case of these "kernel attached recoveries", where recovery doesn't seem to sit in its own separate partition, I guess that would be a little hard or dangerous to do in any case.

So just in case somebody else runs into a similar issue: RAW v7 kernel works with NighOwl and gives you TWRM recovery and RAW v7 features without the optical "improvments" of Remix Ressurected.

I can confirm the same behaviour with my phone.

 

[ardicli2000]

I can confirm the same behaviour with my phone.

As you can realize, not all of the kernels have the same size. Some of them are 5MB ,some 8MB, etc.
There are some tweaks used In order to be able to rewrite kernel on to ehole partition, thus resulting in clean installation. Philz Kernels have it. So you can start all over agan with flashing Philz Kernel first. Also, there are some mods wandering in the net, caliming that they clean up old kernel files. I did not try them. I dont know. You are on your own. But what you say is possible and the concrete solution way could be flashing a Philz kernel, I believe.

 

[abufrejoval]

If LP keeps running hot (no deep sleep), the old trick helps...

I am currently running a mix of the raw v7 kernel and beuner's CM12 LP (just happens to work rather well!) and noticed the battery draining like crazy and device running hot...

CPU spy reports phone running at 500MHz almost constantly, no deep sleep no 200MHz.
Changed governor to "ondemand" and that got me 200MHz but still no deep sleep.
Searched for hints using BetterBatteryStats etc. but then I remembered that there was a magic recipe for curing "no deep sleep":
1. Switch phone into air plane mode
2. Shut down
3. Unplug external power if any
4. Remove battery
5. Stretch, take a leak, whatever
6. Insert battery, reboot
7. Put the phone in standby
8. Stretch, sip a drink, whatever
9. activate phone check deep sleep time using CPU spy (should be more or less equivalent to 8)
10. de-activate air plane mode (unless you happen to sit in one)
11. verify after some more standby, that deep sleep time keeps increasing

hope this helps!

P.S. If anyone knows, what's actually happening there and if some steps can be left out, I'd love to hear from you. I've just had the same issue with older ROMs way back and somebody suggested this method, also without explanation. I was desperate enough to try and it simply worked

 

[01000010]

Let start testing beta 2 ..

 

[abufrejoval]

Let start testing beta 2 ..

I'd love to.... got a link?

 

[fusionero]

BETA2

Well, after almost a facility like the one I mentioned in the first post:

format's & mount's: system, data, cache & SDCard0 (in default)
Nightowl Rom install BETA2
Slim Full GAPPS 5.x.439
And SuperSU 2.40
And restart the phone, selecting reboot system , and skip the fix for SuperSU message, select YES

And nothing, nothing comes out far more than the Recovery, but neither can be used only see a black screen with:

CWM-based Recovery v6.0.5.0
Swipe up / down to change selections.
Swipe to the right for enter.
Swipe to the left for back.

So to reinstall a kernel with ODIN pc, and reinstall the Rom, but the SDCard0 in vfat, if that's wrong because it has not said that can be done in another format, and certainly that's the mistake as I have not used a single zip, other than those discussed: nav3:

Well, I've done installing a kernel Philz by ODIN pc, and I installed the Forest v5, and since he, I followed these steps:

format's & mount's: system, data, cache & SDCard0 (in vfat)
Nightowl Rom install BETA2
Slim Full GAPPS 5.x.439
And SuperSU 2.40
And restart the phone, selecting reboot system , and skip the fix for SuperSU message, select NOT , even as it asked me, for that you save me, lol .

Well in 15 minutes and was torn, but I like not to hit install everything from 0, so if some surprise I will say ..... The SDCard0 is back, lol, the keyboard is turned on at first, without problems, the only thing is I do not demand data language or to put google account so touched me to do everything from 0, and restart the mobile touched me, because until then I took no updates/facilities applications google my account (and of course, I've purchased which are numerous, I do not care to be without them, lol).

Reported that applications without installing anything and you can play all the videos (I tested the mp4) as the first, doing nothing.

Edited:

There remains the problem with the change at 240 DPI (if anyone knows of any application that can change, and did not trouble, I would greatly appreciate if you leave a link to google play, to use it).

 

[rafi_android]

BETA2

Well, after almost a facility like the one I mentioned in the first post:

format's & mount's: system, data, cache & SDCard0 (in default)
Nightowl Rom install BETA2
Slim Full GAPPS 5.x.439
And SuperSU 2.40
And restart the phone, selecting reboot system , and skip the fix for SuperSU message, select YES

And nothing, nothing comes out far more than the Recovery, but neither can be used only see a black screen with:



So to reinstall a kernel with ODIN pc, and reinstall the Rom, but the SDCard0 in vfat, if that's wrong because it has not said that can be done in another format, and certainly that's the mistake as I have not used a single zip, other than those discussed: nav3:

Well, I've done installing a kernel Philz by ODIN pc, and I installed the Forest v5, and since he, I followed these steps:

format's & mount's: system, data, cache & SDCard0 (in vfat)
Nightowl Rom install BETA2
Slim Full GAPPS 5.x.439
And SuperSU 2.40
And restart the phone, selecting reboot system , and skip the fix for SuperSU message, select NOT , even as it asked me, for that you save me, lol .

Well in 15 minutes and was torn, but I like not to hit install everything from 0, so if some surprise I will say ..... The SDCard0 is back, lol, the keyboard is turned on at first, without problems, the only thing is I do not demand data language or to put google account so touched me to do everything from 0, and restart the mobile touched me, because until then I took no updates/facilities applications google my account (and of course, I've purchased which are numerous, I do not care to be without them, lol).

Reported that applications without installing anything and you can play all the videos (I tested the mp4) as the first, doing nothing.

Where do you got the link?

 

[G0711]

Where do you got the link?

You can open the download link by clicking the download link on the first page..
Then click bauner's name on the bottom right..
On the newest upload,you can find the link...

 

[abufrejoval]

Hi, I'm also facing the multi tasking issue. Tried to switch kernels but it's the same behavior.

Very laggy when switching apps

One of the big differences of Lollipop is that it attempts to take the concept of persistant applications a step further: At first it was just a re-position of the back button from the right (where your primary thumb is, unless you're a lefty) to the left (where I find it far less convenient) and then a redefinition of the 'menu' button into a 'recents' button.

Google really doesn't seem to want you to use anything but that newly re-purposed 'back' or 'recents' button, even on devices which like the Samsungs still have physical buttons, which I guess is supposed to mimik Apple only button (never used an i-thingy unless threatened with physical violence or disinheritance, so I'm not sure). You're no longer supposed to 'enter' and 'leave' applications by 'back'ing out of them. Instead you might be launching each just once and then just keep switching between them using 'recents'.

So it keeps all the applications you have used in the cache and ready for access via that 'recents' button not just until you restart the device (pre LP) but essentially 'forever', including its current state. It now survives even reboots and is meant to provide the illusion of applications which have permanent state. Of course the current high rate of updates largely invalidates that concept as cache gets cleared on updates so most applications you haven't used for a couple of days won't just continue from where you left them.

That behaviour is quite ok as long as there is only a few of these applications or your internal storage is super fast. If it is slow to begin with or in need of a TRIM, the re-loading of all that cached data especially after a re-boot or under low memory conditions can take quite a bit of time, most noticible after a re-installation and test of all your precious apps (you can see where this is going, right?)

Solution:
When you do wait for the recents applist and then stare at that list of a second or two, you'll notice a close marker appearing at the right hand top: Hitting that "x" will close the app and delete it from the cache until re-invoked which helps speeding things up already.

If you want a more thorough cleanup go to settings/storage and touch the cache area of your storage: You can see there, that the cache can accumulate quite a few dozens of megabytes if you've been busy and since these are complex structures traversing them can be slow, especially on slow or un-TRIMed storage.

If you touch the cache area you'll be prompted if you want to purge it. A yes will empty the recents list and indeed make it very fast.
But once you've only switched between the applications you actually use, you'll notice a significant gain of speed (well, that is unless you're just ZAPPING around).

P.S. I haven't really tested if applications with outstanding saves get reactivated on updates or cache clears to better support the notion of 'total persistance'.

---------- Post added at 04:27 AM ---------- Previous post was at 04:22 AM ----------

Let start testing beta 2 ..

Ok ok, took the hint and a) went back to the OP link b) replaced the "1" with a "2" in the Android Host search box and got the beta2 download link...

Just posting this here for the other slow guys

 

[fusionero]

As I say, I is working very well, and I have all my apps installed from play google it took a while to settle each separately (each facility has delayed discharge end, and installation), but smoothly, if you have problems with commpradas applications that asks you buy them again is to finish adjusting the Rom Settings, do a reboot in Recovery mode and do wipe cache partition and wipe dalvik cache, and after upgrading applications, the starting the mobile, and download your purchased software seamlessly requests repurchasing will work.

Edited:

I'm having trouble getting permission to SuperSU, I do not get root permissions, I tested with v2.40 and v2.42 (only zip), I tried installing from google play (normal mode and CWM/TWRP mode) from zip (selecting no and yes), and I still get root access for applications that need to be installed in the /system folder (BetterStatsBattery and GSAM), and the beta1 if I could make installation without problems.

If anyone is or may share obtaining such access would appreciate it, because they are the few applications use to check if consumption by improving search consumptions or failures of deep sleep.

Edited:

Fixed ... during startup, before you ask for the PIN code, if it goes fast, you can get access to get app's are installed in the /system folder.

 

[Jackwu696]

As you can realize, not all of the kernels have the same size. Some of them are 5MB ,some 8MB, etc.
There are some tweaks used In order to be able to rewrite kernel on to ehole partition, thus resulting in clean installation. Philz Kernels have it. So you can start all over agan with flashing Philz Kernel first. Also, there are some mods wandering in the net, caliming that they clean up old kernel files. I did not try them. I dont know. You are on your own. But what you say is possible and the concrete solution way could be flashing a Philz kernel, I believe.

Did you and 2 other person under your comment RE-FLASHED Raw7 after initial flash of rom before booting? Coz from what I have followed this thread, that is the best way to boot the rom

 

[rafi_android]

Hi there, how to flash beta 2? I mean dirty flash or full wipe?

 

[giokspy]

What happent in oldsdcard files after install beta 2? I transfer some basic files in sdcard0. In beta 2 working both, oldsdcard and sdcard0 ?

 

[imlop]

plz can anybody tell me, if i use 10gb pit file instead of 12 gb pit for repartion internal sd, does it solve laggy performance of my device by expanding dalvik-cahche partition.?

and how do i know my dalvik size changed or not after repartitioning.?

sorry 4 bad English. any one help me to solve laggy performance of my device after 1 week used with Bauners beta1.

I'm thinking about flash beta2 after 10gb pit file, like to it works or not.

plz give me any link for pit without google drive one.

thanks op @bauner for giving a lollipop for me.

 

[forest1971]

What happent in oldsdcard files after install beta 2? I transfer some basic files in sdcard0. In beta 2 working both, oldsdcard and sdcard0 ?

Your files will be there in a folder name "0" in the proper internal sdcard in B2.

---------- Post added at 03:08 PM ---------- Previous post was at 03:06 PM ----------

plz can anybody tell me, if i use 10gb pit file instead of 12 gb pit for repartion internal sd, does it solve laggy performance of my device by expanding dalvik-cahche partition.?

and how do i know my dalvik size changed or not after repartitioning.?

sorry 4 bad English. any one help me to solve laggy performance of my device after 1 week used with Bauners beta1.

thanks op @bauner for giving lollipop for me.

10-12 will be too much.
4 would be enough or u can tried 6.
it does not help with performance but give u more room to install apps.

---------- Post added at 03:08 PM ---------- Previous post was at 03:08 PM ----------

Hi there, how to flash beta 2? I mean dirty flash or full wipe?

Both will work.

 

[Suarezian]

I'm stuck on bootanimation since 15 mins. I was on beta one with raw r7 kernel. What i did was:
Enter recovery
wipe everything
install beta 2
install gapps
install raw r7
reboot

now stuck at bootanimation

 

[forest1971]

I'm stuck on bootanimation since 15 mins. I was on beta one with raw r7 kernel. What i did was:
Enter recovery
wipe everything
install beta 2
install gapps
install raw r7
reboot

now stuck at bootanimation

It seems B2 has some new update and Raw7 may not work. For now use stock kernel from B2 (reflash the rom without flash raw7) will work.