yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] revvone:
okay so im going to add it to the end of 90userinit like so

#!/system/bin/sh
# call userinit.sh if present in /data/local

if [ -e /data/local/userinit.sh ];
then
log -p i -t userinit "Executing /data/local/userinit.sh";
/system/bin/sh /data/local/userinit.sh;
setprop cm.userinit.active 1;
fi;
echo "1" > /sys/module/msm_otg/parameters/otg_hack_enable;

hopefully that enables it during start up.
[Nexus 4 Android Development] fefecilly:
I didn't know that tapping with 4+ fingers solve the problem,

Till now my personal solution was to tap alternatively and quickly once in the first third of the screen (over the clock) and once in the third third (over the unlock icon).
[Nexus 4 Android Development] __GOLD_:
I didn't know the 4 fingers.

But my solution is press quickly in any area of the sreen and it works after 3 or 4 times.

Next time I will try 4 fingers.
[Nexus 4 Android Development] hozjacz:
It looks crazy. Everybody has own system to unlock. I think, that best way would be abide Google standard - one finger up.... it's impossible?

Odesláno z telefonu N4 pomocí aplikace TT
[Nexus 4 Android Development] jolas:
[MENTION=4217103]zaclimon[/MENTION],

Are there any news regarding self reboot problem?

Thanks in advance
[Nexus 4 Android Development] mohdschizo:
Back to v10 ✌
[Nexus 4 Android Development] rachit995:
I'm new to Quanta. Have been reading few posts of v12 giving random reboots. Can anyone help me with, which version is stable for use as a daily driver?
[Nexus 4 Android Development] zaclimon:
I didn't look into the problem yet. It's possible that I'll look at it in the weekend but don't expect a fix for the moment.

So far, it looks like it is V10.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] tom0769:
V10 is just perfect. Using it with PN. Great performance an very good on battery.

Almost no difference to my son's N5 in terms of speed and on time.
[Nexus 4 Android Development] manpildo:
It's a strange solution, but the author of currently implemented DT2W solution (stratosk, developer of the mighty semaphore kernel) said that a multi-finger touch resets the touchscreen driver... or something like that. I don't know if he implemented this on purpose to bypass the glitch, if I recall correctly I think he did.. Guy is a genius after all. Btw it might work with 2-3 fingers too.

And no, there is no way that I know of to prevent it. Nexus 4's hardware doesn't natively support dt2w, so we are lucky that this is the only minor inconvenience. Without stratosk we would have never got anything as stable as that.

Regarding your question about v11, then it has the same problem as v12. For now, v10 is the latest stable version. I downgraded to v10 myself too and it's been smooth sailing so far.
[Nexus 4 Android Development] dimaka1256:
v10 is stable, but it fails on pptp connection to my office with VPNroot, while v12 can do it
[Nexus 4 Android Development] aldus12:
My feedback is that v12, unlike v11, is very stable. With v11 I had several reboots every day while v12 is rock solid, at least the last uploaded version, not the first. Flashed as soon as it was available, till now I haven't had any reboot!! Smoother than v10 with similar battery drain. Thank you [MENTION=4217103]zaclimon[/MENTION]!
[Nexus 4 Android Development] kryzeK:
Ok, now I've some reboots with V12 while my device is sleeping :(
[Nexus 4 Android Development] jolinnard:
Could be this commit?
[Nexus 4 Android Development] zaclimon:
I've done tests with it removed and still had issues. For the moment, I've removed all commits related to the timer and see if I can get a panic/watchdog.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] mohdschizo:
Thank you dev. For now i just stay with v10 until v13 come out.
[Nexus 4 Android Development] :
Solution to the problem is to go back to TWRP 2.8.7.0 and upload the system again.

I did so and I no longer restarts the phone , Quanta v12 works well .
[Nexus 4 Android Development] dimaka1256:
what's the difference in recovery versions? it's not loaded while android is running

I use omnirom nightlies and have my /system formatted every update
[Nexus 4 Android Development] jolinnard:
Ok. I was trying to build the source with UBER 5.3 to make some tests (toolchain was freshly built with included scripts) and it gives me an error in qdsp6v2, same with UBER 4.9... Do you build your toolchain too? or you are using some prebuilt....
[Nexus 4 Android Development] zaclimon:
Woah I do build my own toolchain and I never got an error for this. I'm wondering if there is something related to an update. How are you building it?

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] jolinnard:
:eek: freshly updated my Archlinux machine, restart, sync and build again and now qdsp6v2 works (code is not modified since 3 years ago), but I had to disable ondemand if I revert "rcu: Add RCU_FAST_NO_HZ tracing for idle exit". So build done at least for now.
[Nexus 4 Android Development] dragos281993:
So, any chance of seeing "Jolie kernel v4.0.0" ? :D
[Nexus 4 Android Development] jolinnard:
I don't think so ;)

Do you miss something in Quanta or Taurus?

---------- Post added at 02:58 PM ---------- Previous post was at 02:45 PM ----------

OMFG.... mistery solved, I don't know why, but I was generating the config with mako_defconfig and not with quanta_defconfig :eek::eek::eek::eek: Sorry for the noise.
[Nexus 4 Android Development] dragos281993:
Definitely not. I was just asking. I like to see that our Nexus 4 hasn't been forgotten.
[Nexus 4 Android Development] arvindgr:
Absoluelt love this kernel!! Yet with recent v12 on mako, I often have random reboots on latest Chroma ROM. See last_kmsg http://pastebin.com/nAdN1JpJ Is this really kernel bug?
[Nexus 4 Android Development] manpildo:
Yes
[Nexus 4 Android Development] emraz786:
[MENTION=4217103]zaclimon[/MENTION] maybe surprise us with a v13 with that fixed bug ?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] xWolf13:
There have been already a bunch of bug reports about V12. No need to keep posting about it. Before you post a bug, search around the thread if it has been reported. Spamming it just clutters the thread with useless posts. It's been reported

already

. You can follow any commits made by [MENTION=4217103]zaclimon[/MENTION] on GitHub to have a "sneak peek" on what's coming next via his GitHub.
[Nexus 4 Android Development] arvindgr:
Sorry, if the Bug I reported was already noticed. Plus, I just wanted to share the bug, i came through without intention of spamming! Maybe in Downloads post, Dev can mark v12 with known bugs and write, Fix's are in way, when most people dont read up entire posts to follow the thread,,,
[Nexus 4 Android Development] TheWizardofOdd:
No other managers are installed
[Nexus 4 Android Development] bfoos:
I haven't tried v12 as all of the complaints about it made it not seem to be worth it. However, unlike most who have gone back to v10, I myself have been using v11 and not had a single reboot or sleep of death.
[Nexus 4 Android Development] AlexBelikov:
installation and upgrade

sorry for nub question, looked for some faq but didn't find any

I'm going to install v10 on top of latest Chroma. What are the right steps after new Chroma build will be released? Dirty flash of Chroma and then dirty flash kernel again. Is it a right way?

Big thanks to developers!
[Nexus 4 Android Development] dragos281993:
Yes, to upgrade, dirty flashing works fine. A cache + dalvik cache wipe is recommended before and after flashing the ROM + custom kernel.
[Nexus 4 Android Development] emraz786:
I lasted three days using v10, v12 now I installed the above and have 24 hours without Restart. chroma rom.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] stefat77:
I updated from v10 to v12. (Flashed ROM , flashed kernel , wipe cache/delvik).

I have a huge battery drain and 1 reboot every hour. :(

ROM : chroma ROM
[Nexus 4 Android Development] dragos281993:
Don't get me wrong but taking a look at the latest comments is recommended before leaving one yourself. The random rebooting problem it's been discussed over and over again in the last few pages.
[Nexus 4 Android Development] zaclimon:
Hope this one is good

Hey guys, I've been pretty much silent since last week. I hope this build will fix all the issues related to the panics/watchdog that you've been having. Here it is:

V13(09/03/16)

- Reverted a commit related to timers that were the cause of the panics (Looks like [MENTION=2002216]jolinnard[/MENTION] was right)

- Reintroduced Nvidia Power savings

- Updated F2FS

Both builds are available on BasketBuild.

Enjoy!! :)
[Nexus 4 Android Development] emraz786:
¿You not need wipes?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] Italico:
Thank you very much, gonna try it into the weekend!
[Nexus 4 Android Development] zaclimon:
Nope you don't need to. :p
[Nexus 4 Android Development] arjundas86:
Sweet!! I love how both things I was waiting to update came out on the same day... Quanta and PureNexus!

Thanks Zac!

And just to confirm... V13 still uses cpu_boost (rather than revert to hotplug), correct?
[Nexus 4 Android Development] zaclimon:
That's correct, cpu_boost is going nowhere at the moment.
[Nexus 4 Android Development] kaiser_tytnii:
Love it! Thanks dev!
[Nexus 4 Android Development] xenyz:
Did you happen to test with Kodi? :)
[Nexus 4 Android Development] zaclimon:
That's something that you'll have to check by yourself as I don't have any reason to install kodi on a 4.7" phone. XD

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] kryzeK:
No more reboots with V13. Thank you Dev!

But my N4 burns within minutes of normal use, and of course, the life of my battery is horrible.

I'm using PureNexus 03/09 build (Layers).
[Nexus 4 Android Development] emraz786:
quiet, as the kernel stabilized in a second cycle. my nexus got very hot but it is stable again.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] jer_ying_fd:
Hi, wonder if someone can provide the stock interactive settings for Franco kernel? I want to mess with the governors but I'm not familiar with interactive settings since I was used to ondemand so would like to have a base to work with, since I'm a performance freak and I would like to have somewhere to start. Thx!
[Nexus 4 Android Development] CatsAreGods:
Quanta v13 seems to have broken my wifi!

After flashing and rebooting, couldn't connect to my home wifi...or even turn it off! Couldn't access my settings pull-down either. Reflashed Chroma, using stock kernel, and still can't get settings pull-down. Very odd.
[Nexus 4 Android Development] shawnbrennan55:
Been running V13 for about 24 hours without issue. Thanks for continuing to work on Quanta for all of us Mako users!
[Nexus 4 Android Development] marcoDima:
Using it for one day.

Everithing works fine: no random reboots or strange behavior.

Thanks for your work.
[Nexus 4 Android Development] str3tch72:
I never thought that Nexus 4 can fly. With this kernel I know one - "nothing is impossible!" Great work, no random reboots. Smoothest experience ever!

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] zaclimon:
Plans for 2016

Glad to see that everything is pretty much stable these days. Looks like there won't be a new release until a bit. I'll use that time to learn more about C, the Linux Kernel and Android development. (Times are hard as I don't know how to code in C...)

Concerning QT, I was thinking of adding this future functionnality of Android N:

https://developer.android.com/preview/api-overview.html#tile_api

Could be neat huh? :P
[Nexus 4 Android Development] arjundas86:
Thanks bro!

You mean adding a QS Tile for certain QT kernel settings that we might want to frequently toggle?

Are you talking about for when N comes out, and people start using QT to tweak custom kernel settings on N?
[Nexus 4 Android Development] zaclimon:
Yeah exactly. I could serve the same purpose as widgets without actually taking space screen. I don't know if I'll still use my N4 when N will be released, (Given that Google must release a better N5 than the N5X...) but it was just a little idea that could be interesting.
[Nexus 4 Android Development] Applesan:
Can you add GPU voltage control into kernel?
[Nexus 4 Android Development] zaclimon:
Self-explanatory.
[Nexus 4 Android Development] Facebooook:
But add touchwake control option in quanta tweak app because its included in kernel. I need to set it via manually after every reboot.
[Nexus 4 Android Development] zaclimon:
I'll add touchwake in the future when I'll get started with QT. It can take a long time before it arrives on the app though.
[Nexus 4 Android Development] granazis:
[MENTION=4217103]zaclimon[/MENTION],can you please explain why when tried to use your kernel also using your app to control on my N4 runing Broken rom (every build) in all the apps icons colours changed? Last try was today on this latest build: Broken-v4.3-mako-6.0.1-OFFICIAL-20160304 with the same result.The kernel worked excellent except on refered issue.As i am very interesting about OTG also ,can you do or suggest something?

Thanks in advance
[Nexus 4 Android Development] dragos281993:
The "funny-inverted" colors appear when you flash an AOSP kernel over a CM based ROM or a CM kernel over an AOSP based ROM. make sure you flash the correct version. Don't know what Broken-OS is based on but whatever version of Quanta v13 you downloaded, you have to get the other one. If you have the AOSP version then get the CM one, or if you have the CM version, then get the AOSP one.
[Nexus 4 Android Development] granazis:
No,friend i know exactly what i am doing,FYI Broken its no cm based rom and the kernel flashed is for AOSP.

Regards

EDIT:@dragosThe same happen when Taurus r41 for AOSP flashed,orAK-M2, May be rhe rrom is disfunctional? as its out of any logic to flash the opposite version.Are U agree that something goes wrong w/rom as never happen on pure nexus or chroma?
[Nexus 4 Android Development] dragos281993:
If you read carefully, you'll notice that I didn't say that the ROM was based on CM. I covered both sides.

"its out of any logic to flash the opposite version". No, it's not out of any logic. "VR-Toxin" is AOSP based and it requires a CM kernel, otherwise you get messed up colors, so it's completely logical. I even got in an argument with the VR Toxin ROM's dev on this matter.
[Nexus 4 Android Development] TNSMANI:
v.13 working flawlessly for the last 24 hours.

I don't know whether it is related, but I had issues with AD of Greenify (not blocking motion sensing) with the built in Chroma kernel and v.10 and v.11 of Quanta. But with v.13, AD of Greenify has started working as intended.

Thank you Dev!
[Nexus 4 Android Development] kol1124:
What is your settings for kernel?
[Nexus 4 Android Development] TNSMANI:
So far, except undervolting by 25 and CPU max at 1242, all other settings are stock.

I am a noob as far as kernel settings are concerned, so progressing slowly.
[Nexus 4 Android Development] TA123:
Sorry, I'm new to Quanta. It is not possible to set the lowest CPU frequency below 384, is it?
[Nexus 4 Android Development] dragos281993:
Nope. FYI, there was never a benefit for going below 384MHz. No battery life improvement and occasional SOD for the kernels that had lower frequency steps. So no frequency below 384.
[Nexus 4 Android Development] quentin2260:
Hello ! I have flashed Quanta yesterday and this morning I have got SOD. Why ?

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] dragos281993:
1. What version did you flash ?

2. Did you have a custom kernel installed, before you flashed Quanta ? (Describe the "setup" you had before trying Quanta)

Please answer on point.
[Nexus 4 Android Development] shadeMe:
Hello, I tried search the thread for any mention of it but couldn't find it, so apologies if this has been requested before. Could CIFS support be added for mounting network/samba shares using the CIFSManager? Thanks in advance.
[Nexus 4 Android Development] granazis:
[MENTION=434573]dragos[/MENTION], Hi friend the problem solved following your suggestion, i will never try on such a way knowing that Broken its an AOSP rom and so an AOSP kernel version was needed to work ok i all fields as the devs never give such infos even on wich fs their rom made,i met this many times and on many devs.May be they have their own reasons.The caps used (FYI) did as was thinking that was uknown to you(about broken) and also thinking that i did the right trying to flash an aosp version kernel ,so it was matter-of-course to wonder about this meeting it for first time.At the end i ought to tank U once more for this so important post at least for me.

All the best,Christos

EDIT: Its time to start a refresher course to rom devs(its just for joke)
[Nexus 4 Android Development] zaclimon:
CIFS has always been enabled by default in Quanta. So you can go ahead and try it out if it was your only concern.

Before going into "That's meant for a different ROM", we need to stop believing the misconception surronding the Qcom display. As you know, most kernels for the N4 and the N7 2013 are separated in 2 values which are AOSP and CM. Though, the reason why they're separated as such is because of commits related to the kernel and to the display driver which are defined here:

Kernel:

https://github.com/CyanogenMod/android_kernel_google_msm/commit/c53fb6d134fab3e3d7a022ba857d9cad4fcfa59a

https://github.com/CyanogenMod/android_kernel_google_msm/commit/c53fb6d134fab3e3d7a022ba857d9cad4fcfa59a

Display (I might be missing one):

https://github.com/CyanogenMod/android_hardware_qcom_display/commit/b52399cfa01141ed611c98bf58ec9f87b3cf1931

The fact that YUV color format has been added is the reason why there are funky colors. (I don't know where is the commit that set it the default way of doing things) Though, that part, is only one component of the ROM and can still be associated with a pure AOSP ROM. The distinction was only made between CM and AOSP because CM were the first to implement that change.

All recent devices doesn't even deal with this issue so it can be possible that the rom developpers doesn't know about it. Though, if the ROM is really based off AOSP instead of CM, then I'll decide to believe them.

Last thing, why has it been adopted? Well as people may know, CAF is always working on optimizing Qcom stuff and this may break the stuff in AOSP that is older than their CAF counterpart. Some may find it for the best, others for the worst. This is why there is mostly fragmentation between CM sources and AOSP.
[Nexus 4 Android Development] dragos281993:
Don't bother with this. It's ROM related. I tested it with Taurus a while back ago and it was the same. So don't trouble yourself cause it's not such a big deal.
[Nexus 4 Android Development] zaclimon:
I know this is only ROM related but trying to remind to a ROM dev that their ROM is CM based while it is AOSP is kind of ridiculus. I just wanted to clarify why there are AOSP and CM based kernels for mako and flo/deb specifically.
[Nexus 4 Android Development] dragos281993:
There are currently only 2 ROMs with this "issue": VR Toxin and Broken OS. The VR toxin dev got pissed off when I pointed out the issue and the Broken OS devs, from the description they added to their G+ ROM thread, I might get a "gtfo" if I said anything. Lol

When I told the VR toxin ROM that his ROM is CM based, he claimed it was AOSP, then I explained that flashing an AOSP kernel (no matter which one) gives you funky colors. I was told to get out basically for pointing out that the description is misleading.

But that's it, I stopped using VR toxin.

So don't trouble yourself cause it's not a big deal.

Soon, a new Game of Thrones season will be out so there's no need to waste our time with little stuff like this. ?
[Nexus 4 Android Development] jolinnard:
Hi, I have a SOD too. It's the first with Quanta I believe... I have attached the last_kmsg (I'm using Krexus FYI) if someone wants to check. It has some weird things and characters... I think that never happened before. I don't think it was a ROM issue or even the kernel issue... Will report if it happens again.

ZIP password: quanta

PD: I don't know why xda was rejecting the file :confused:
[Nexus 4 Android Development] shawnbrennan55:
Broken uses AOSP ROM sources and CAF kernel sources, so you need to use the Quanta CM version.
[Nexus 4 Android Development] dragos281993:
Yup, I know. I learned about that after the ROM dev said it. The problem was he didn't say anything about it in the description so people flashed the kernel according to the ROM base and got funky colors. That was pretty such it.
[Nexus 4 Android Development] quentin2260:
1. Lastest v13.

2. Taurus kernel before on Chroma ROM.

I have flashed Chroma ROM in order to have stock kernel then make cache + dalvik wipe then flash Quanta with default settings.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] dragos281993:
Uninstall the kernel manager that you used, reboot the phone, then install it again. If the kernel manager you used, had "apply on reboot" chexked in some sections, then the app would try to apply settings that are no longer the same cause you're using a different kernel now. It happened to me.
[Nexus 4 Android Development] truevision:
v13 has not conservative governor ?
[Nexus 4 Android Development] dragos281993:
No. But Interactive does the job very well. You can tweak to suit your needs, for either battery preserving or performance.
[Nexus 4 Android Development] dragos281993:
Check the reply I sent to Quentin. It might be of help, hopefully. It's at the bottom of the previous page.
[Nexus 4 Android Development] quentin2260:
Chroma ROM = AOSP Quanta ?

I have uninstalled kernel Adiutor. So I waiting tomorrow morning to see if SOD have been fixed. Thanks for help !

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] dragos281993:
Yup.
[Nexus 4 Android Development] granazis:
[MENTION=4217103]zaclimon[/MENTION],Hi friend i just read your posts refered on problem for first time i met using your project on Broken rom and soved by help of [MENTION=434573]dragos[/MENTION](already thanked about), i ought to say a big TNX to U for your in depth given explanation about all these you reffered which was uknown to me untill now and well understood what is happening about.

As always follow your work plus one thanks for your new project wich works excellent on Broken i am runing now w/no SOD atall, on 10 hours -> 98% deep sleep(BBS), The same on pure Nexus.These are my beloved roms for my N4.

Just informing and thanking

All the best ,Christos (Christos Thimis on G+)
[Nexus 4 Android Development] quentin2260:
No SOD this morning !

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] underskyzx:
Why default settings max cpu is 1242Mhz?
[Nexus 4 Android Development] zaclimon:
Because the interactive settings have been forced anyways to use it's max at 1242. I could have left it at 1512 but I've done it the double verification way.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] __GOLD_:
I come from V10 to V13.

I see that the cpu are almost the 4 working at same time. And I can't get deep sleep the 384 is always working on the 4 cpu's.

This is normal? I'm using Original ROM 5.1.1 (LMY48T).

Or have I made something wrong?

Thanks for your help.
[Nexus 4 Android Development] dragos281993:
Maybe I'm wrong, but I'm pretty sure the last versions of Quanta have specifically been built for M, not L.

But you might want to try finding what's causing the wakelock cause it seems it might be a wakelock that's bugging you. "Betterbatterystats" is the best app for this kind of stuff. Get it and start monitoring your devices activity.