yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] jgcaap:
If you enjoy my work please rate 5 stars the thread and leave thanks on the first OP as for me is a way of knowing you guys are happy with my builds.

Doing currently a new build, where i slowdown just a little animations, and improve speed of touch button and appear recent menus to test. Added back SU. And also synced with CM 27/04/2015 . I'll continue my work on friday.

If you guys like my work, please consider a donation (even if is small), as this takes for me lots of time, and will help with my electricity expenses (this is mainly my worry issue which if you can help will be perfect, as i can continue to improve stuff without any worries).

Big thanks again . And enjoy...
[ONE Android Development] iyousif:
Thank you so much, Should I flash the 1.42 after this one or it's included already?

I am on 2204 now :)

P.S.: Voted 5 stars, although you deserve 15 :D
[ONE Android Development] jgcaap:
Included :) download 27/4 or wait for new update. Is being built now.
[ONE Android Development] jgcaap:
Small note : If anyone gets Wi-Fi issues let me know. I'll fix on next build. I never had problems so I didn't bother to apply [MENTION=3814731]katinatez[/MENTION] fix. But I can do it easily if needed.
[ONE Android Development] gugas123:
huge breakthrough
[ONE Android Development] jgcaap:
New rom to try out with the goodies i spoke you guys about. If you dont like roll back (there are a very small diference on speed. ) http://www.drdevs.com/devs/jgcaap/oneplus/rom/
[ONE Android Development] jgcaap:
Guys I have something I discovered together with arter. Despite the fact of appearing on this print screen that gcc is 5.1, it was compiled with gcc 4.8... Sorry for this... :(

It seems all the work is being done by the kernel.

I got tricked by this.
[ONE Android Development] Jole7:
You are talking about the kernel and not the rom right??
[ONE Android Development] jgcaap:
I'll try explain better... I was so disappointed to discover this... So I preferred to announce it publicly my mistake. I was so excited that I thought it was a success. After speaking with [MENTION=4898097]arter97[/MENTION] which made me sad. But new kernel is really working good and making a great job.

But my promise will be this, I'll work together with [MENTION=2332422]temasek[/MENTION], [MENTION=4898097]arter97[/MENTION], and [MENTION=3814731]katinatez[/MENTION] to see a workaround.

Sorry about my mistake guys.

Kernel was compiled with gcc 5.1

Rom was compiled with gcc 4.8
[ONE Android Development] momsi:
The wifi issue is still there for me.... And still rebooting in airplane mode fixes this temporarily.

Despite of that, everything is fine ;)
[ONE Android Development] Jole7:
No problem my friend you 're doing a great work!!!
[ONE Android Development] jgcaap:
I'll fix that on next build.
[ONE Android Development] demon507:
Small difference on speed? Means?

Sent from my Oneplus One RenderedCapp
[ONE Android Development] jgcaap:
Yes but much more Smooth. Processing power is the same. :)
[ONE Android Development] jgcaap:
Beta version http://www.drdevs.com/devs/jgcaap/oneplus/rom/

Let me know if works.
[ONE Android Development] didicola:
when you have time plz make for us a rom f2fs compatible

we will flash manually the partitions via twrp to f2fs and we will just flash the rom ;)
[ONE Android Development] jgcaap:
Kernel is ready for that. But since I got issues so I rolled back. It'll be my next goal.

Good news... Managed to change gcc tool chain 4.9 compiled on rom level :)

With everything working.
[ONE Android Development] Amanpreet Wadhwa:
Downloading your beta version. What is the difference between normal and beta?
[ONE Android Development] jgcaap:
Rom is compiled with gcc 4.9 instead of 4.8.
[ONE Android Development] jgcaap:
Just arrived home. I thank you all for your patience, and regarding my mistake beeing so cheerfull and supportive. With this mistake i was able to discover a way of compiling ROM with GCC 4.9, until i come with a real working solution. That not only will provide us a better experience, as also will speed up.

Kernel has GCC 5.1 which is amazing to be able to compile with that. This business of trying to develop is hard stuff. At least, for me , with just basic knowledge of programing C language and also Java (or almost none) , has been a great victory and a real addiction to provide a better build by each time i try out .

I had advanced many times 10 steps to step back later 2-4 steps, then advanced again. I believe we are and i am on the right direction, as i have been learning and doing my best to improve each day even more.

The last rom was compiled with Google Tool Chain 4.9 in combination with Linaro 5.1 . Now that we know it works, i'll try do a compilation with 4.9 GCC linaro again, which would be for us, the best solution.

Thank you all for your patience, and for following what i share with you guys. All this investment of time, has been rich, as i have made many friends, learned alot, and have been able to see the hard part of development and compare, when i was a mere user.

The reality is that Android the way it is programed, sucks for end user. Because there is always lags there and there. I hope google come up with a real solution so that we can in the future have a much better and improved operating system to use. That is way i have been so eager into finding solutions and combinations to "save" us from that, so that we can be happier with what we have and say, everything fast, smooth and great.

I know some of you are already happy as the rom is. I am achieving a bit of that level , but still is not enought . Well... I hope with time i can come up with a good combination where all of us will enjoy and say, amazing it's possible.

Thank you for all support and share for commitment to participate with the roms i have been building.

:)
[ONE Android Development] jgcaap:
More responsive on which way? Thanks for feedback
[ONE Android Development] :
More responsive in that I've been having a few performance issues since I flashed Marshmallow, every-so-often, my system freezes for a second. This happens mostly right after turning on the screen, and opening Chrome. I swipe down to see my tabs, and it freezes there for a second. I'm not sure whether it's Chrome that's crapping itself, but on Lightning with the profile applied, it recovers from the frozen state much quicker. Also, it sometimes freezes while unlocking the display; on Lightning, it doesn't.
[ONE Android Development] jgcaap:
That probably because of the thermal system. After boot, it lags a little because it reached a high temperature and thermal system is telling cpu that temp is to high. A problem with Qualcom chips heat to fast.

We use qualcom thermal system for now.

The one in the kernel you use is from Franco.

The difference is that qualcom thermal reacts earlier and decelerate the kernel frequency.

I still am trying to understand thermal code from qualcom in order to see a better solution. Already thought of implementing Franco thermal back.

That's why gets you a more snappier experience.

About the SOT. Well that's because of the hotplug with thermal combined.

I'm still studying solutions, and slowly writing my own hotplug, it is not even usable for now as I am very slowly understanding how this works. Let's see if I can build a better solution for us.
[ONE Android Development] lightman3dd:
Happens to me too with Chrome, never tried other kernel than the stock one of 0301 build..and i'm going crazy with GPS...it says fixed but the position is totally wrong :( i've tried the gps fix proposed some posts back but i was not lucky to solve. Also tried GPS stat app ...In need a correct GPS position for sport activiteis and i'm thinking to go back to cm12.1 :((((((
[ONE Android Development] aclup3:
am i the only one finding 31/12 version more snappy and overall smooth than 02/01 version?
[ONE Android Development] jgcaap:
Mistake I thought he had that thermal but doesn't. I'll review this again this week. :)

Using intellithermal

https://github.com/nikhil18/lightning-kernel-bacon/commit/9b02dc09534d1cbf3998b79d26b96dcb7ee9ea41

Again fixes the declaration thing.
[ONE Android Development] :
That makes a lot of sense - my phone generally lags quite a bit on boot. I always thought it was because of the apps autostarting and that must be contributing to the slow-down, but the thermal throttling explains it fully.

But what this doesn't explain is why, when my phone's been on for a while, the Chrome lag happens. I just turn on my screen, navigate to Chrome, swipe down on the tab-bar, and bam, freeze. Surely thermal throttling isn't coming into play then?

Thank you for your work, again. It's nice to see someone who's genuinely motivated to improve themselves and their work, other people would let their jealousy be a hindrance to them rather than a tool for improving. If you need any help with testing or whatever, let me know, I'll be more than happy to help.

In the meantime, however, is there any way for me to diagnose why Lightning isn't working? It's not even letting the system go to the bootanimation, it just shoots itself while in the 1+ bootloader logo and reboots.

Also, I'd mentioned a while back about implementing the Camera2 API. Looks like that isn't happening anytime soon, but I did stumble upon the modded/ported ColorOS app in the forum, and that has been brilliant. The reviews are not at all as overrated as I initially thought - this is the real deal. If you install the Camera HAL driver as well - which works flawlessly with this ROM - you even get manual focusing, all without the Camera2 API. If you haven't tried it yet, you should. The interface is simple, and it takes amazing pictures. Anyone who's used an iPhone should feel right at home.
[ONE Android Development] llevin:
For me GPS works fine (and has worked on all versions of this ROM).

Note that the gps.conf fix may help in getting a quicker fix, but does not affect the basic GPS function. It only selects closer time & AGPS servers.

Try the GPS Status app - Activate it in an open place and give it a long time to get a fix (may even be up to 20 minutes in worse case situations). Doing Menu/Manage A-GPS/Download should shorten the fix time significantly.
[ONE Android Development] jgcaap:
Did you ever trimmed your system? It makes alot of difference.

Personally I do not like to touch the thermal as is a very important piece to keep our phones from beeing fried.

Your thermal has a core reset limit at 90 C, our chips should not have problems to have it higher but I prefer to keep stock.

About why doesn't work... Well that only asking the dev. I already have to much at hand. But there were other users which used that kernel perhaps they can lend a hand here?
[ONE Android Development] jgcaap:
Today test build has art from Google instead of caf. The goal. Of this build is to evaluate performance and battery trade off.

Please some of you test. Thanks
[ONE Android Development] :
Trim my system? Meaning? I should probably try that.

I agree, but I don't think that those kernels overheat the system. As far as I know, reaching 90C is quite a big deal, it requires quite a deal of processing to get to that level. I'm sure it doesn't get to those levels under daily, normal usage, where I notice the snappiness.

If you haven't tried the kernel with Stylo's profiles, do give it a shot. You'll see what I'm talking about.
[ONE Android Development] jgcaap:
Is necessary to trim sometimes. Download android tuner and Do it with the app. You should have a faster system after that.
[ONE Android Development] fabio.pagliuca:
Today's test rom seems to be smoother and faster than yesterday's
[ONE Android Development] lightman3dd:
I've got the same "impression"..smoother and more responsive than the 0301 . About battery life it's to early to give a feedback...lets' see in the next hours
[ONE Android Development] jgcaap:
The one I just build?
[ONE Android Development] :
Holy hell. I trimmed my phone, 18GB in /data, but only 240MB in /system. I haven't had time to test, but let's see if it'll help. This is the app I used, for anyone interested.

You mentioned building the latest test nightly with Google's ART, not CAF. Correct me if I'm wrong, does this mean that this ROM is CAF-based? Because if it is, that would explain why Lightning isn't working. I've been trying to flash the CM-based one so far.
[ONE Android Development] lightman3dd:
Yes the cm-13.0-20160104-jgcaap-bacon.zip in the test dir.. Isn't?

.
[ONE Android Development] jgcaap:
All roms are caf based... :)

The kernel not working is for another reason. My bet is the boot img.
[ONE Android Development] fabio.pagliuca:
Yes!
[ONE Android Development] :
Okay, you lost me. As far as I knew, CM and CAF are two totally different frameworks, or am I mistaken? CAF, as far as I knew, was based off of Snapdragon's drivers, and they weren't that intercompatible or something.

So wait, so I shouldn't flash the CAF-based kernel right?
[ONE Android Development] jgcaap:
nope. There are many people which do not know the difference and are mislead with the description of CAF on the threads. I'll open up a small post clarifying that.

Added to the op

You problably wondering why i say is CAF+Google+CM. It's in fact very easy... and i have seen many threads which mislead the interpertation of what is included. Google provides AOSP+ kernel patches for the nexus devices which are identical to our chipset.

Qualcom provides CAF changes which is over linux kernel changes and google changes. (in other words kernel is linux based and frameworks/art/bionic are based on the google stuff which is also based on linux)

We still have CM changes.

So basically how it works? i'll simplify

We use Google as base which includes CAF changes and CM changes... and with this ROM... jgcaap changes :)

So why Add CAF on some roms at tittle?

Basically is linux kernel with CAF changes without google or CM changes on kernel (and kernel only)

But let me add you some knowledge here. What you call CAF is in fact Oxygen OS kernel. In other words, what Devs which have on title CAF which is related to 3.4.0 kernel is in fact linux+CAF+Oxygen OS.

Oxygen OS changes is only compatible with blobs which are from oxygen OS, and we do not use it. So because of that, the rom problably won't boot in case you flash a "CAF" kernel.

Why some Devs use the called CAF and some CM source?

Depends on preference. I prefer CM because i believe is the best not only on performance but also never had issues with it. But there might be different experiences regarding the phone you have since we all have different batches. There are devs which believe that compability issues might be related to some CM commits. As also, there are devs which think the other way around.
[ONE Android Development] MurdererFight:
Can i install caf kernel like lightning kernel?
[ONE Android Development] jgcaap:
replyed up :P
[ONE Android Development] MurdererFight:
Ok
[ONE Android Development] dkv2222:
Installed the latest build.

Screen flickering seems gone. No glitches.

Battery will test.

Smoothness, very smooth.
[ONE Android Development] xdavidc:
Hey guys can you check what it says on your side? Maybe I clicked the wrong file? Supposed to be latest test build :/
[ONE Android Development] fabio.pagliuca:
Same here, don't worry, it's the latest
[ONE Android Development] jgcaap:
ignore it. :) is latest.
[ONE Android Development] xdavidc:
Ok thanks.
[ONE Android Development] Bradl79:
i didn't quite understand, so did u did u not flash the CAF Kernel? thank u

---------- Post added at 08:12 PM ---------- Previous post was at 07:51 PM ----------

flashed the latest fw 12/10/15 and 01/03/16 and no sim
[ONE Android Development] xdavidc:
Ok so, so far it's snappier then 01/03 and I think 01/03 was the worst build on these terms since 31/12 builds. For battery need one more day to see xD
[ONE Android Development] jgcaap:
Read the OP. Try see differences compared to your post :P i'm sure you'll find what gone wrong
[ONE Android Development] xdavidc:
From OP latest is 12/30/15.
[ONE Android Development] MrTapa:
So raw camera still works with the latest build?
[ONE Android Development] Purerawenergy:
Which build are you on now?

Tom-alpha
[ONE Android Development] Bradl79:
i am sorry, that is what i meant, yes that is the one i flashed, it kept rebooting and showed no sim, i ended flashing an old fw and is working fine now
[ONE Android Development] xdavidc:
01/04 test folder.

---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------

Which recovery did you use?
[ONE Android Development] Purerawenergy:
So how do you grade it compared to what I'm currently on, 12.31.15?

Tom-alpha
[ONE Android Development] xdavidc:
Equal or better.
[ONE Android Development] aclup3:
But the smoothness was "removed" by cm ou jgcapp?
[ONE Android Development] :
This is the sort of battery life I'm getting. As you can see, I'm not going to cross 4 hours. This is, quite frankly, abysmal, considering this phone was touted as having the best battery life of 2014. My phone isn't that old yet, even, hardly a year, so the battery can not have degraded that much.

Also, I'm not sure how others' sleep/awake cycles look, but this does not look that bad, so I can draw the conclusion that sleeping isn't an issue for the phone. I'm using Greenify, Amplify, Power Nap, Naptime, and Servicely, which is, admittedly, overkill, and is pathetic when you compare it to an iPhone - which sleeps like a baby and doesn't need these apps to keep everything barely under control. Based on the slopes of the graphs when the device is supposed to be sleeping, battery drain during that time is still much higher than it ought to be, considering how many fail-safes I've tried to use to keep it contained.

But the main problem I'm having is with the battery life when my phone is on. That's where I believe most of my battery life is being devoured, and as testament to that, I've noticed my phone gets quite hot towards the top under normal usage - which should not be happening. With regards to trimming my system - no dice: the stutters are still aplenty.

Again, not to be knocking on OP, but I believe his kernel/optimizations still need work. How does the test 01/04 build compare, for anyone who's tried it?
[ONE Android Development] :
I know you tried your best to explain, but I can't for the life of me understand the difference. I'll have to carry out further research to grasp at these concepts, but I'm sure you've helped other people understand.

That's the thing. I have Xposed installed, but I have no modules that affect Chrome. None that affect GCal either, nor Relay Pro, yet those are the apps that constantly stutter horribly. I haven't gotten round to installing any CM themes this time around either. So that should not be the problem with my setup.

Do you have no lag with Chrome at all? It occurs most commonly when you unlock the screen - and works better if Chrome is in the foreground - and then when you swipe down the tab bar to show your tabs. Or when scrolling a picture-heavy webpage. Also, check GCal, all the pictures make the scrolling stutter like a toddler.

I might be inclined to believe the stutter may be caused by Greenify hibernation waking the app up for usage. So that then conflicts with the minimal battery savings I'm garnering from the said app.
[ONE Android Development] jgcaap:
Try stock kernel... See if improves... I tested on both situations. Battery life is bad compared to kitkat , the battery drain bug is still present since lolipop , which is a google bug .

I don't think is related to kernel. But is a matter of helping up studying.

Battery is something i'm investigating solutions. In case someone finds possible or suitable solutions, share.
[ONE Android Development] :
This is the stock kernel. Not Lightning.

This setup is completely stock: your 01/02 nightly, stock kernel, Slim GApps Mini 12/25.

The first day I used Marshmallow (on another ROM) I got 6 and a half hours SOT. No Greenify, no Amplify, no nothing. After that, the battery life practically died.

Google get your **** together.
[ONE Android Development] jgcaap:
i'll build kernel 3.51 to see if improves battery life, basically i've disabled cotex-a15 code back to stock. Please test and report.
[ONE Android Development] jgcaap:
there was also a report that the update 6.0.1 caused drains. But lets find ;)
[ONE Android Development] xdavidc:
I had 2h30+ of sot when I flashed from 01/03 to 01/04 test build with 30min of bt audio streaming. After flash and restore all my apps trough titanium I still got this:

PS: I don't use fb anymore, I use browser for it and no 'control' apps (greenify nap etc)
[ONE Android Development] :
Okay. Link to kernel?

---------- Post added at 04:49 AM ---------- Previous post was at 04:47 AM ----------

That's a very good time. What is your setup? Do you use apps like Amplify, Greenify, etc? Tasker? Fb? Chrome?
[ONE Android Development] xdavidc:
I've edited previous post, but I don't use anything and no Facebook.
[ONE Android Development] :
I use Facebook but it's Greenified, and I didn't even use it today. Something is seriously wrong with my setup, I just can't figure out what that is.
[ONE Android Development] jgcaap:
When i said stock was CM kernel. I have it published on the server also . :)

if possible try first 3.51 and after the one which says stock. Would be very helpfull.

Thanks
[ONE Android Development] Zombie Dude:
Thank you. I'll try the first link but how do I install the .img file?
[ONE Android Development] :
Okay, I'll try out 3.51 and test it out tomorrow from 100%. I'll keep you posted.
[ONE Android Development] xdavidc:
Basically browsing, bt streaming with viper on, xda.. from 9am to now, 23:30pm.. Do you greenfiy fb messenger? It's a battery eater too.

When I first started with cm13 wakelock detector didn't work very well so I tried with no greenify or other apps and gave up on facebook app.

Edit: 9am
[ONE Android Development] :
That's brilliant. All I did on my phone during the duration of that test was browsing on Chrome, and Reddit. All on 3G, not even LTE.

And let's put it this way - I've greenified (and PowerNapped, for that matter) everything except for the system apps which would make the phone drop dead if hibernated. I've even got a Tasker profile to force-trigger hibernation of all apps 5 minutes after the screen switches off.

I've got a serious problem here guys.

Edit: Okay, so I did a quick BBS test. Deep sleep for 97% of the time. The problem, therefore, is when the screen is on.
[ONE Android Development] jgcaap:
3G is a battery drainer from what i know. Also will depend on the capacy of getting signal on your area.

Alright lets focus on finding a solution.

I don't use xposed, but i noticed a drain on battery life for 30min to 1 hour SOT. my bet would be on the cortex code, which increase speed.

Lets see :)
[ONE Android Development] xdavidc:
Just try to use it as it was built. I mean give it a try with no greenify or any other apps, just what you use normally but don't install fb or fb messenger. Clean flash and go for it for a day.

Edit: you have radio mobile active eating also on chrome, I'm always WiFi so its a big difference there too I think.
[ONE Android Development] devilsshadow:
Yes that is dreadful and precisely the reason I was forced to go back to kitkat. Google has been notified but I doubt they will give it much attention. What's funny is that even people with nexus 5x are reporting the bug.

Here's the link to the bug in case more people want to star it/comment so it gets more visibility https://code.google.com/p/android/issues/detail?id=190396
[ONE Android Development] jgcaap:
The fix is complex. I am sure they are doing their best
[ONE Android Development] jgcaap:
Another thing. Try also without xposed. Only stock clean rom.

We'll find solutions.

The optimizations done for our device are mainly hardware use and code. Should not affect performance on battery.

The only code which I can think that might kill battery is cortex a15 code, which I've disabled on 2.51 beta.

We had also an experience of battery drain in the past while using cortex 15 optimized bionic but it killed battery faster.. Was fun to play a bit. :) hehe