yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] __GOLD_:
Or in this one I should install the original Kernel first? If yes where can I find it? In the factory images for nexus?

Install only the boot.img. Sorry for so many questions.

---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------

I have read the first page and say's 5.1 an later..

I will wait for some one confirm that could be used in L or not.
[Nexus 4 Android Development] dragos281993:
Why aren't you using Marshmallow. There's Chroma or Pure Nexus, etc. With Quanta on top, things are super smooth and overall great. M is as stable as the stock ROM plus that you get many more additional features that will come in handy. Stock doesn't compare to custom, as long as they're both as stable as it can get.
[Nexus 4 Android Development] arjundas86:
This is normal. It's the major change that [MENTION=4217103]zaclimon[/MENTION] implemented as of V11 - switching from mako_hotplug driver to cpu_boost implementation. It now keeps all cores online, at min frequency rather than hotplug (i.e., turn cores on and off). This implementation came from Qualcomm (via CAF) and has been taken up by many kernel developers. It is supposed to improve the UX (smoothness in daily use) on the phone, because it can respond to changing processor needs much quicker when the cores are already on. Also, in theory, having cores come online and offline frequently consumes more power than staying online at low power. This will reduce battery consumption for users who interact with their phones often during the day (i.e., most people). But if you only check the phone a few times during the day and it spends most of its time sleeping on your desk, this implementation might be worse for battery life.

For more information, go back to Post #1286 on Page 129 and read to the bottom of the page.
[Nexus 4 Android Development] __GOLD_:
Only because I will lost all my data. And I already try before make backup's but always without lucky. I don't like to lost all my sms and call logs / all e-mail's configurations and so on and so on..

But for the most users the best experience for now is Chroma or Pure Nexus?
[Nexus 4 Android Development] dragos281993:
You can backup the data of the apps you want, with Titanium Backup. After you're done backing up, you can copy the Titanium Backup folder from the internal storage to a computer then make the jump to Marshmallow and after that you can restore the data and you're done.
[Nexus 4 Android Development] TheArt.:
[MENTION=4217103]zaclimon[/MENTION] is it safe to use Doze Settings Editor with PureNexus with QuantaV13? Maybe some doze settings may interfere with your kernel energy saving settings?

BTW I've QuantaV13 since it came out, no reboots or SODs so far. Great :)
[Nexus 4 Android Development] shadeMe:
Hmm, I just did and the CIFS manager returns the following error: Mount. No such device. According to the app developer, it indicates that the kernel doesn't support CIFS. I manually tried using the mount command using a shell script and I keep getting an invalid argument error.

The script I used:

#!/system/bin/sh

# Mount script (by DualJoe@XDA)
# v1.1 - moved credentials to top of the script

folder=Vault	# will be /mnt/cifs/MyShare
host=smb://readyshare/vault	# Source Host
username=user	# Username
password=pass	# Password
mountoptions=ro,iocharset=utf8	# Mount options (read-only, UTF8 for Windows)

folder="/mnt/cifs/$folder"

if [ ! -d "$folder" ]; then
mount -o remount,rw /
mkdir -p $folder
chmod 755 /mnt/cifs
mount -o remount,r /
fi
su --mount-master -c mount | grep "$folder" > /dev/null
if [ $? -eq 0 ]; then
su --mount-master -c umount $folder
if [ $? -eq 0 ]; then
gscript-input toast "Umount successful :)"
else
gscript-input toast "Umount error $? :("
fi
else
su --mount-master -c mount -t cifs -o username=$username,password=$password,$mountoptions $host $folder
if [ $? -ne 0 ]; then
gscript-input toast "Mount error $? :("
else
gscript-input toast "Mount successful :)"
fi
fi

Am I doing something wrong or are there other prerequisites for mounting Windows shares on Marshmallow (I'm on the Chroma ROM)?
[Nexus 4 Android Development] zaclimon:
Well not really much as the settings I've put is really during the device is being used. I'm using Naptime myself and have no problem in Quanta with it.

Well personally I'm using Root Explorer/Solid and I don't have any problems mounting shares. I was able to mounting manually my home SMB share using this guide, you should perhaps adapt the script to these instructions:

http://www.netzgewitter.com/2013/10/troubleshoot-cifs-on-android/

It should work normally with these changes. Though, I would keep the stuff pretty much simpler by using a file manager that can mount it natively.
[Nexus 4 Android Development] zeeBomb:
How is this kernel compared to Taurus? What are the governors/io schedulers? And if I was to f2fs which ones would I change? Data and...
[Nexus 4 Android Development] dragos281993:
They're both great kernels but Taurus is not gonna be updates any more. The dev sold his N4 so no more Taurus. At the moment is not really outdated but soon it will be and if you happened to have a bug, you'd get help only from the users, if you're lucky. Quanta kernel is the only one still maintained by it's dev, it's got the latest stuff inside based on Franco's work on Flo (N7 2013) so that's pretty descriptive. And Zaclimon is here to help us when we need it, when we find a bug, etc. Taurus had a bit bigger amount of options but people still ended up using the most common "setups" so those additional features were pretty much left untouched. F2FS is basically the same with both kernels. For me F2FS is placebo effect. Some users may have gotten slightly better results in some benchmarks, but in real life scenarious, I haven't noticed a single difference. No better performance, nor more snappiness, etc. It was the same thing. And after converting to f2fs you have to be careful at what you want to flash cause there are things not compatible with this system format and you could end up with a bootloop. But if you decide to change to f2fs, make sure you copy all the important files to a computer cause everything is erased during the transition. For f2fs, only "data" and "cache" must be converted. After that you'll always need a custom kernel with f2fs support otherwise the phone won't boot up.
[Nexus 4 Android Development] zeeBomb:
Very informative post...thank you.
[Nexus 4 Android Development] avlis88:
I Need help. I flashed quanta kernel, installed quanta tweaks. Active Option otg hack. Reboot my nexus. Plug pendrive with usb y cable. I use es Explorer, but dont see pendrive. I using pure nexus.

Enviado de meu Nexus 4 usando Tapatalk
[Nexus 4 Android Development] jacomail95:
I dare say there's another custom kernel shipped with features and updated, included in Beanstalk ROM, so it can be pulled out from the zip and used, but only on CM or CM based ROMs, not AOSP. Sorry for OT, but i discovered that a few days ago

http://xdaforums.com/showthread.php?t=3279427

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] shawnbrennan55:
You also need Chainfire's Stickmount app from the Play store.
[Nexus 4 Android Development] TheArt.:
Would you mind sharing your Naptime's setting? I applied some values but I don't know if they can break some core functionalities.
[Nexus 4 Android Development] arjundas86:
[MENTION=7179560]zeeBomb[/MENTION],

I just want to add to the detailed post above, that to convert to and use F2FS, you need an F2FS compatible recovery as well. The standard versions of TWRP from the official site will not work.

One great option is Tassadar's modified TWRP for MultiRom:

Here is the latest from Tassadar: https://s.basketbuild.com/filedl/de...multirom/mako/TWRP_multirom_mako_20160210.img

Another option is the unofficial TWRP 3.0.0 EXT4/F2FS

http://xdaforums.com/nexus-4/development/unofficial-twrp-mako-3-0-0-ext4-f2fs-t3309705
[Nexus 4 Android Development] AlexBelikov:
Less battery life after upgrade from V10 to V13

Hi guys,

Looks like for the way I use my phone V10 was better for battery life. Usually I had 40-50% of battery at the evening and I could have total 1.5 hour of SOT per day and 15-20% left of battery. Now it's only 4pm and I have only 26% left with only 32 min of SOT. All the apps are the same, nothing else updated these days. I'm running Chroma february version. I'm not using my phone during the day a lot. Just dismissing notifications over Pushbullet from laptop... Tweaks is all by default. I even did "drop app data and reboot" after I installed v13. Also noticed that phone is warmer while charging.

Is there anything I can try to improve bettery life? I'm thinging to go back to v10.
[Nexus 4 Android Development] dragos281993:
The reason people install custom kernels is for the ability to tweak them the way they want, something not entirely possible with stock kernels. The presets on a custom kernel are meant for a good balance between battery life and performance.

So, in order to achieve the results you desire, you're gonna have to do some digging up on what every single option of a custom kernel does. There are tutorials here on xda that explain thoroughly what you have to do to perfectly set up a kernel according to your needs.

If you (generally speaking) don't feel like spending some time understanding what all those options do and simply use the kernel as is, I believe you'd be better off with the stock kernel.

So I suggest you start doing some research and you'll see that in the end it's gonna really pay off.
[Nexus 4 Android Development] AlexBelikov:
Yes, I agree. Know everything on a deep level is a very good way. Just thought there is something I can try quickly which will make difference.

Actually v10 worked so good for me out of the box. It's smoother than stock Chroma kernel, phone is colder, battery life better. Looks like the best for me is to return to v10 until I have time for experiments. Thank you for reply.

---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------

Also just read your reply in Chroma Nexus 4 thread about 2-3 cycles of full charge/discharge. Maybe trying that is a good idea after upgrading kernel? Or it's good only when I switch ROM?
[Nexus 4 Android Development] dragos281993:
Yup. Good idea. You need a bit of spare time exclusively dedicated for researching. V10 is still great, of course.
[Nexus 4 Android Development] __GOLD_:
I'm thinking about the same. V10 is great I only test it on L.

Can I revert V13 to V10 directly?

V10 for me is great V13 is smooth but Hight comsumption of baterry.
[Nexus 4 Android Development] dragos281993:
I never tried to downgrade. Considering that it's a downgrade process, I suggest you dirty flash the ROM first, then the v10.
[Nexus 4 Android Development] __GOLD_:
Thanks.

That was my concern.

I will make a dirty flash and after install the V10.

Because V10 on L is really good smooth VS battery.

V13 at night without touch ldrain 10% of battery I think is just because of keep all cores online.
[Nexus 4 Android Development] _HaZaRD_:
Is normal that with DT2W activated (set on boot) the first time I turn on the phone the touchscreen die, and I have to reboot/soft reboot the phone to make it work without problems?
[Nexus 4 Android Development] __GOLD_:
Never happens to me.

Strange behavor. What Rom did you use? Did you gcome from each kernel before this one.
[Nexus 4 Android Development] _HaZaRD_:
Atm I'm using chroma. I don't know the name of the kernel but was the one included with the rom.
[Nexus 4 Android Development] AlexBelikov:
I dirty flashed v10 on top of v13 and also cleared cache and dalvic cache. Phone stuck on Google logo. I rebooted to recovery and flashed v10 again. Phone started, did "optimizing apps" and now it's all OK. I think I shouldn't clear cache and dalvic cache after kernel installation.
[Nexus 4 Android Development] arjundas86:
Clearing dalvik and cache should never cause boot problems. Flashing a kernel over another kernel is known to cause problems and is never recommended by kernel devs. Between Quanta V10 and V13, there has been enough of an upgrade, that it might as well be an entirely different kernel. When it's suggested to not do so by kernel devs and senior forum members, why would you do it anyway?

Just a few posts before yours, [MENTION=5796730]dragos281993[/MENTION] said it would be better to dirty flash the ROM (to go back to stock kernel) before flashing Quanta V10 - as is the general rule for flashing kernels.
[Nexus 4 Android Development] kaiser_tytnii:
Alternative, extract the boot.IMG from the ROM and flash it in recovery. Save you time in not having to clear caches
[Nexus 4 Android Development] AlexBelikov:
I'm not saying what's correct and what is not. I'm just sharing what happened to me as guys in a few posts before were curious how to do it. But once we're already talking about it.... If you'll open zips of v10 and v13 you'll see that kernel is a binary file zImage + there are a few shell scripts. So "installing" it it's just overwriting of those files. So I don't see how "flashing ROM kernel then flasing v10" different to "flashing v10".
[Nexus 4 Android Development] zaclimon:
Well it's nothing big, it is a bit agressive but you're up to changing those if you don't like them:

Inactive timeout: 600s

Sensing timeout: 0s

Locating timeout: 0s

Location accuracy: 20.0

Motion inactive timeout: 0s

Idle after...: 0s

Idle pending timeout: 120s

Max idle pending timeout: 120s

idle pending factor: 2.0

Idle timeout: 1800s

Max idle timeout: 21600s

Idle factor: 2.0

Min time to alarm: 600s

Max temp app: 120s

Mms temp app: 60s

Sms temp app: 20s

Anykernel does overwrite the zImage found in the kernel's original boot.img but the scripts aren't installed into the device. They have a purpose of modifying the ramdisk found in the said kernel. I've added checks to see if the kernel isn't Quanta based. If so, the ramdisk changes will be applied. This is why it is recommended flashing the original rom's kernel before flashing the kernel because the values in V10 and V13 vary too much just to flash over version.

Sure enough, one could simply flash over and not use stock values and would still be good. That said, certain features (like KSM) isn't present in V10 so the values won't apply.
[Nexus 4 Android Development] AlexBelikov:
Thank you [MENTION=4217103]zaclimon[/MENTION], this is a good explanation.

Not sure why but after my strange way of dirty flashing of v10 over v13 I have extremely good battery life. I wanted to drain the battery asap so I turned on youtube video for 4 hours. So far I have 2:39 of SOT and 48% of battery! This is something really cool! Not sure if it's only about dirty downgrading of kernel or it's because of I used an other charger at work or both.
[Nexus 4 Android Development] zaclimon:
Hmm in that case, it can be that the optimized values that I've put are not battery friendly enough. Is cpu_boost activated?
[Nexus 4 Android Development] AlexBelikov:
Not sure. I'm new to custom ROMs and Kernels.

I'm using Chroma. Installed v10 with no tweaks (except of OTG hack). Then flashed v13 and battery life became much worse... Now I'm back to v10 and I dirty flashed it. After that my device suddenly sets the longest SOT ever :)
[Nexus 4 Android Development] __GOLD_:
I have made a dirt flash off Croma and instal the V10 again.

Now I'm testing but it's clear he drain isn't so big like with V13.

After 2 days of use I will let you know my opinion.
[Nexus 4 Android Development] arjundas86:
[MENTION=4217103]zaclimon[/MENTION]

I too am having slightly worse battery life with V13 compared to V10, but not critically so.

InputBoost is activated. Changed a few settings from default because I found that the UX to slightly lag sometimes (scrolling, etc.).

- Interactive governor

- increased max cpu freq by 1 step (1242 to 1350)

- increased max gpu freq by 1 step (200 to 320)

- increased boost duration (not input boost duration) from 20 ms to 50 ms

The above changes improved the UX significantly.

I also have DT2W enabled in V13, which I never did back in V10. I suspect that would have a noticeable effect on battery life as well.
[Nexus 4 Android Development] Cristiano Lira:
Can you update a backup of your boot partition for zaclimon can analize it and for us can test if we can get the same result? But I don't know if the boot partition is enough or if you'll have to upload a backup from you system and/or your caches partitions also. What are needed [MENTION=4217103]zaclimon[/MENTION]?
[Nexus 4 Android Development] zaclimon:
There is nothing to take note of. Probably Interactive coupled with cpu_boost consumes more battery life due to it's nature. I would like to see what could be the difference of battery life if cpu_boost is deactivated leaving only Interactive running.
[Nexus 4 Android Development] Cristiano Lira:
But In his case he is getting greater battery life when he flashed V10 then v13 then V10 again than just flashing V10 over stock kernel. I think it could be due leftovers values in ramdisk. And thus you could analyze it and know what are the cause from that better battery life. That way you could release a "tweaked" V10 with even better battery life, if you want to, idk.
[Nexus 4 Android Development] arjundas86:
Turning off cpu_boost - i.e., the "Input Boost" setting, will not restore hotplug, will it? Won't it keep all cores online anyway?
[Nexus 4 Android Development] jolas:
After several days of use, I can say that Quanta v13, gives me a slight better battery life that v10.

I also made same changes to fit better to my liking: max_freq 1512000, max gpu clock 400000000, input boost 150ms, input boost freq 1134000... :o
[Nexus 4 Android Development] zaclimon:
In this case, there won't be any V13 leftover values because they haven't even be added in the first place, he still have the values from V10.

No, the governor will be the one to handle everything. Even though all the cores are still online, it could help considering there won't be the burst every time there's a new input.

Maybe hotplugging shouldn't even be considered if the system is mainly using 2 cores instead of 4.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] mjehan:
Which editor to use to modify the kernel settings ?
[Nexus 4 Android Development] dragos281993:
"Quanta tweaks", "Kernel Adiutor", "Synapse", "Trickster Mod", etc.

The choice is yours.
[Nexus 4 Android Development] arjundas86:
The kernel dev has also developed his own app call Quanta Tweaks for editing kernel settings. See post #3 as well.
[Nexus 4 Android Development] AlexBelikov:
I will share whatever will be needed. But now I think several more things could make the difference. I'll check them and let all of you guys know.

The main thing to check is an other charger. I used apple 2.1A for iPads. I noticed that phone charging goes slower. But on the same evening I got 4.5 hours SOT. Today I used my regular charger and 1 hour of SOT left only 20% of battery. Trying apple charger again.
[Nexus 4 Android Development] Cristiano Lira:
There is still this problem with QT that I'm having since v11. After I have rebooted my phone input boost duration and boost duration settings changed to 0 by itsef and the phone became really laggy.
[Nexus 4 Android Development] Giovaneveterano:
I'm on V13: Quanta Tweaks don't apply settings at boot even if I checked that setting.

Chroma ROM

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Android Development] zaclimon:
What is your QT version?

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] Cristiano Lira:
Latest, downloaded from Play Store.
[Nexus 4 Android Development] veketash:
Some time ago i posted here my results with V10 regarding the battery life, when I was getting 5h+ of SoT. Please, tell me how I can get close to that on V13? On V10 I used Conservative governor, but now, without it, I don't know how to set the current ones, and the Powersave still doesn't help.
[Nexus 4 Android Development] zaclimon:
Alright guys, I see that having 4 cpu cores online might not help really much with battery life as our batteries pretty much suck and that all our cores are the same (compared to Franco where he tried it on big little devices.)

I'll probably keep cpu_boost but I'll most likely keep 2 cores on and leave the choice to the user to enable the 2 other ones.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] dragos281993:
Yes, I believe that having the option there would be nice. That way people can decide which option they prefer.
[Nexus 4 Android Development] zaclimon:
Were you updating from 4.1.1 before or it is the first time you're using QT? If it's the first case, try to wipe your app's data and see if it works again. Otherwise, could you send me a logcat to see what is the issue?

I don't know when I'll have time to attack this as I have some projects going on right now but I'll see if I can push something this week before easter vacation.
[Nexus 4 Android Development] sis71:
Hello,

i use chroma OS (6.X) built date 2016 Mar. 13. an i wold like test your kernel.

with fastboot boot <kernel.img>

how can i find the *.img file to make the test ?

Thanks ...
[Nexus 4 Android Development] arjundas86:
Why don't you just flash the zip file in recovery?
[Nexus 4 Android Development] sis71:
I just want to do a test . Without anything in the long run on the system to change . Should something not so function as I want it , I do a reboot and everything is the same before.
[Nexus 4 Android Development] arjundas86:
Changing a kernel is a change in the system partition - no way around it. Kernel is an integral part of the OS, not one or two settings to change. You can always revert back to your original kernel (the one that came with the ROM) by dirty flashing the ROM. But you can't undo a kernel by rebooting. Flashing it via fastboot doesn't make a difference.
[Nexus 4 Android Development] sis71:
according to this

http://www.android-user.de/franco-kernel-auf-dem-nexus-4-testen/

and

http://www.android-hilfe.de/thema/kernel-nur-zum-testen-installieren.729011/

is is possible an i have done it some times if i had stock android 5.x.

And it works perfekt. all wat you need is an kernel.img file, and fastboot.

The question is why there are no img files ?
[Nexus 4 Android Development] arjundas86:
Oh ok... boot with a temporary kernel, without flashing the kernel. Haven't heard of that before. Cool.

Nobody here has had a need for that or requested it before. You can see if zaclimon is willing to create img files for you. He's the kernel developer.
[Nexus 4 Android Development] zaclimon:
Because of the differences between the roms, I can't create a universal boot.img and call it a day. What you could do though it's backup your boot partition using TWRP or something like flashify. Then flash Quanta and try it.

If you want to go back, you just have to restore your backup.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] sis71:
OK thanks for the informations ...
[Nexus 4 Android Development] __GOLD_:
After several day's using V10 instead of V13. On Chroma the both versions.

I can esure that V10 is a beast in terms of battery. Isn't comparable with V13.

In terms of smooth perhaps V13 is better than V10.

But for me V10 for sure.

Only giving feedback to help new users and to the developer knows the feedback of the users.

In any case great Job to Keep mako alive with so great work.
[Nexus 4 Android Development] zaclimon:
After some testing on my N7, Disabling the 2 cores made a great difference. I wasn't able to make 4 hours with the 4 cores activated. Now I can do about 6:30 without any problems. I expect something simillar to happen on my N4 as well.

Probably the reason why Franco could do this is because of the nature of the processor he had. He is probably always keeping the low-power cores on so they don't take a lot of battery whilst giving some good performance overall. Which isn't the case with us. I'll be out during the weekend so I'll try to get a little update before going to Easter vacations.