yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] TheDarkDefender:
I'm running a test kernel by zac and its working great, just for me though Zac is unable to access his sdcard. He's working on fixing it, he's got his finals coming so you can expect one next weekend probably.

Cheers,

D
[Nexus 4 Android Development] zaclimon:
As [MENTION=4778194]TheDarkDefender[/MENTION] mentionned, I have my finals coming this week,. I'll try to do something soon about it. I think that Flo might be here before (Today if I have the time) Mako. (I have a feeling that this bug might take some time to pinpoint)
[Nexus 4 Android Development] MtG92:
No worries, take your time, I was just curious as to where things were at ;) Good luck for your finals! Mine are in January, this week is my last before the holidays...
[Nexus 4 Android Development] emanuele1986:
i'm waiting your kernel! :)
[Nexus 4 Android Development] zaclimon:
Android Lollipop, r215, Launching!! (Those who know Gundams will understand)

Hey, the moment that everybody has waited since Lollipop arrived on our devices is here! :) I decided that with Lollipop I want to be closer to the actual vanilla sources. I want to make a franco.kernel that only has been compiled with SM. (With some tweaks here and there)

r215:

- Completely rebased off Franco's sources (With Android 5.0.1 sources)

- Compiled with the latest 4.9.3 SM toolchain (With all the flags from the previous versions)

- Everything you liked from the other versions :p

It is now available on basketbuild. CM kernel isn't here yet, it'll come later.

Enjoy. :)
[Nexus 4 Android Development] aviz1911:
Sooo, you fixed those sdcard issues that stopped you from releasing R214 :p or is it your master plan from the start to release this with all 5.0.1 updates ;)
[Nexus 4 Android Development] vampire36:
Works perfect...super smooth...

DT2W and Faux Sound make it even better :)

Super work...SM seems even better :)

Keep it updated ;)
[Nexus 4 Android Development] zaclimon:
Yea the issues were fixed though I tend to believe it got fixed with those mounting flags I've modified. (/data) 5.0.1 came as a bonus. :p
[Nexus 4 Android Development] loukvlav:
Has anyone used this kernel with EuphoriaOS? Does it play well? Also is FKU the recommended app to tweak this kernel?

Thanks!
[Nexus 4 Android Development] zaclimon:
Can't say for Euphoria as I'm using stock. FKU is recommended to have the most enjoyable exprience, though you can use apps like trickster that will do the job just fine. :)
[Nexus 4 Android Development] zaclimon:
CM r215 is now available on Basketbuild! :)
[Nexus 4 Android Development] gharrrrrr:
X-Mas came earlier! Thanks for your continued work on this kernel [MENTION=4217103]zaclimon[/MENTION]
[Nexus 4 Android Development] emanuele1986:
Thanks!!!

So, i'm with franco kernel 215 and to install your kernel is Be enough wipe cache and dalvick?
[Nexus 4 Android Development] zaclimon:
You're not even obligated to wipe wipe cache or dalvik. Only flash and forget.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] fanquela:
nope, 2.0
[Nexus 4 Android Development] tvisforme:
As I understand it, v7 is the last version for CM12.1, correct?
[Nexus 4 Android Development] zaclimon:
Can you send a dmesg when you're connecting your usb device to know at least if it is recognized?

That's correct.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] fanquela:
Thank you for your help!

Yes, It works in dmesg, but when I try to mount it with StickMount it prints "The mount service is busy - try again in a few seconds

[ 4719.283716] usb 2-1: new high-speed USB device number 6 using msm_hsusb_host

[ 4719.433724] wlan: [1204:E :HDD] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable

split scan

[ 4719.446359] usb 2-1: New USB device found, idVendor=1221, idProduct=3234

[ 4719.446756] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 4719.446970] usb 2-1: Product: Flash Disk

[ 4719.447336] usb 2-1: Manufacturer: USB2.0

[ 4719.447550] usb 2-1: SerialNumber: 2008090816360671

[ 4719.457896] usb-storage: USB Mass Storage device detected

[ 4719.458537] usb-storage: -- associate_dev

[ 4719.458568] usb-storage: Vendor: 0x1221, Product: 0x3234, Revision: 0x0000

[ 4719.458598] usb-storage: Interface Subclass: 0x06, Protocol: 0x50

[ 4719.458629] usb-storage: Transport: Bulk

[ 4719.458659] usb-storage: Protocol: Transparent SCSI

[ 4719.458964] usb-storage: *** thread sleeping.

[ 4719.458995] scsi4 : usb-storage 2-1:1.0

[ 4719.460979] usb-storage 2-1:1.0: waiting for device to settle before scanning
[Nexus 4 Android Development] zaclimon:
Hmm what's the filesystem on your stick?so far only FAT32 is supported kernel side.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] zaclimon:
[MENTION=7283374]fanquela[/MENTION] are you able to mount the stick now? If not, what happens if you reboot your device with the USB stick plugged in?

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] fanquela:
I'm not able to mount the stick. Neither with the Stick on restart

StickMount seems to work, because it shows # blinking on the top bar, but it doesn't works. If I try twice "Mount" it prints "The mount service is busy - try in a few seconds" and no more.

I've to say, StickMount prints at start: "Its highly recommended to use SuperSU v1.93 or newer with StickMount. You are currently running either an older version or a different superuser management tool, wich may be a cause for issues".

I use the built-on root from Cyanogenmod 13. If I try to use SuperSU, I have a bootloop

When it works, where does StickMount usually mount the UsbStick? in /sdcard/storage? I have the empty directory.

Thank you very much for your help!
[Nexus 4 Android Development] zaclimon:
Cm doesn't mount otg devices at boot which is why it won't mount automatically. What is the version of SuperSU you're currently trying to install?

We can either try stickmount or manually mounting the stick from the device.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] fanquela:
I tried to install SuperSU v2.46.

How can I try to mount manually the stick?

Thank You very much for your support!
[Nexus 4 Android Development] zaclimon:
If I'm correct 2.46 is the latest stable which won't work for marshmallow . Try to install the 2.67 here:

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

For the devices, I don't know the name for the OTG device. Could you tell me the files or folders of /dev?

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] fanquela:
The list of files and folders in /dev

__properties__ media1 random tty11 tty54

alarm media2 rfkill tty12 tty55

android_adb memcg rmnet_mux_ctrl tty13 tty56

android_mbim msm_aac rtc0 tty14 tty57

android_rndis_qc msm_aac_in smd1 tty15 tty58

apr_apps2 msm_acdb smd11 tty16 tty59

ashmem msm_amrnb smd2 tty17 tty6

bcm2079x-i2c msm_amrnb_in smd21 tty18 tty60

binder msm_amrwb smd22 tty19 tty61

block msm_amrwb_in smd27 tty2 tty62

bus msm_amrwbplus smd3 tty20 tty63

ccid_bulk msm_camera smd36 tty21 tty7

ccid_ctrl msm_dsps smd4 tty22 tty8

console msm_evrc smd5 tty23 tty9

cpu_dma_latency msm_evrc_in smd6 tty24 ttyHSL0

cpuctl msm_mp3 smd7 tty25 tun

cpuset msm_multi_aac smd_cxm_qmi tty26 uhid

device-mapper msm_qcelp smd_pkt_loopback tty27 uinput

dsp_debug msm_qcelp_in smd_sns_adsp tty28 urandom

efs_hsic_bridge msm_rotator smd_sns_dsps tty29 usb

fscklogs msm_rtac smdcnt_rev0 tty3 usb_accessory

full msm_sps smdcnt_rev1 tty30 usf1

fuse msm_vidc_dec smdcnt_rev2 tty31 v4l-subdev0

gammacontrol msm_vidc_dec_sec smdcnt_rev3 tty32 v4l-subdev1

gemini0 msm_vidc_enc smdcnt_rev4 tty33 v4l-subdev10

genlock msm_vidc_enc_sec smdcnt_rev5 tty34 v4l-subdev2

graphics msm_vidc_reg smdcnt_rev6 tty35 v4l-subdev3

gss msm_wma smdcnt_rev7 tty36 v4l-subdev4

hidg0 msm_wmapro smdcnt_rev8 tty37 v4l-subdev5

hidg1 mtp_usb smdcntl0 tty38 v4l-subdev6

hsicctl0 network_latency smdcntl1 tty39 v4l-subdev7

hsicctl1 network_throughput smdcntl2 tty4 v4l-subdev8

hsicctl2 nmea smdcntl3 tty40 v4l-subdev9

hsicctl3 null smdcntl4 tty41 vcs

hw_random ppp smdcntl5 tty42 vcs1

i2c-0 ptmx smdcntl6 tty43 vcs63

i2c-3 pts smdcntl7 tty44 vcsa

i2c-4 qmi0 smdcntl8 tty45 vcsa1

input qmi1 smem_log tty46 vcsa63

ion qmi2 snd tty47 video0

keychord qseecom socket tty48 video1

kgsl-3d0 ramdump_dsps tgt tty49 video100

kmsg ramdump_gss touchwake tty5 video2

loop-control ramdump_lpass tty tty50 video3

mako_hotplug_control ramdump_riva tty0 tty51 wcnss_wlan

mdm ramdump_smem-dsps tty1 tty52 xt_qtaguid

media0 ramdump_smem-gss tty10 tty53 zero
[Nexus 4 Android Development] fanquela:
[MENTION=4217103]zaclimon[/MENTION]

No way to mount the USB Stick with last nightly version of CM13 (Marshmallow).

How can we go on? Should I wait for a next Quanta Kernel update for 6.0?

Thank you!
[Nexus 4 Android Development] zaclimon:
Hmm, do you have a /sys/devices/platform/msm_hsusb/usb file? If so, we can begin from this.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] fanquela:
:-/ no, that's what I have. Seems no change with or without USB stick

Thank you very much for your help :)
[Nexus 4 Android Development] DingoDingo:
[MENTION=4217103]zaclimon[/MENTION] is there any chance to add ondemand governor (maybe something like Semaphore ondemand) in one of next builds? I have to use perfomance governor while using Viper4A to avoid pops and cliks.

Thank you anyway for almost perfect kernel, fast, stable, otg, dt2w, color profiles....

I am using your kernel for few months now and never looked back. ☺️
[Nexus 4 Android Development] dragos281993:
I had the same problem while listening to music in Spotify. There's no need for ondemand any more. Go to the "Viper|Atmos" thread and download "ViperAtmos 4.6 Sony Beats edition". It works perfectly fine. If you don't want to flash that right now, if you have Dolby Atmos installed, which I assume you do, open it and disable "Surround visualizer", until you decide to flash the older build, which even the v4a dev agrees it's the best despite the fact that it's older. To flash that older build of v4a, you need to dirty flash the ROM that you're using first in order to get rid of all the files related to v4a, then flash the custom kernel and Viper Atmos 4.6. And then, you're good to go, no static noise, but nice and clean sound with all the effects that you want turned on.
[Nexus 4 Android Development] DingoDingo:
Thanks for advice but I already flashed 4.6 (downgraded from 5.2.1) and having pops and clicks on every governor except performance . Using V4A for years.

Just realised that performance governor is not so bad for battery as I thought, I have to charge my old N4 at least once during the day no matter what governor I use. Will keep using performance governor for now, battery life is not on my priority list.

Thanks again for advice ?
[Nexus 4 Android Development] zaclimon:
Hmm I don't know what to say honestly. I would need to check what is the exact path first. Have you retried to install SuperSU to see if stickmount can work.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] jer_ying_fd:
Congrats on the breakthrough
[Nexus 4 Android Development] zaclimon:
V11/QT 4.1.2

Hi guys, it was long and with my other internship, I didn't have really a lot of time to get it earlier but it's here now :D. I've tested it and it seems buttery enough for me so I hope it will be for you XD.

Let's breakthrough the first release of the year!

V11:

- Rebased from my Flo release V7 release

- Changed from mako_hotplug to cpu_boost (it's actually not bad at all)

- Replaced Conservative by Interactive (Though this one is optimized and should be better)

- Misc additions (KSM, optimized LMK from Motorola, etc... Check my Github for details)

- Updated F2FS

- Compiled with the lastest UberTC.

Because I've changed values in the ramdisk, you MUST flash your original rom's kernel before flashing V11. I've put the settings to be quite a bit conservative whilst still giving some good performance. You can still tweak your settings if you're not happy XD.

Both builds are available on BasketBuild.

As far as QT is concerned, here is the changelog for V4.1.2:

- Added CPU temperature limit

- Added an option to erase the app's data

- Fixed Analog Headphone Gain

- Fixed input on governor tweaks

- Misc fixes/improvements (like Franco_My_Profile)

It should be available in the next hours in the Play Store.

Thanks also to [MENTION=5796730]dragos281993[/MENTION] for the testing he did during that time!

Enjoy!! :)
[Nexus 4 Android Development] kryzeK:
Oh yesss!! Thank you for your awesome work :victory:

I love this kernel, I hope it never ceases to exist

I have a doubt: I must wipe cache and dalvik cache to install/update/change the kernel?
[Nexus 4 Android Development] zaclimon:
Nope. Cache wiping isn't necessary at all I must say lool. XD

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] str3tch72:
Great work, this kernel/app with every relase are going to be the most powerfull thing on Mako. :D

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] dragos281993:
Yup. You got that damn right. Plus in combination with QT that's exclusively been built to work with it... The best experience.
[Nexus 4 Android Development] DingoDingo:
I am on Fake Nexus Rom with Cataclysm Mod and couldn't flash boot.img from rom (ended with bootloop) prior to update Quanta to V11. I have only Nandroid with Quanta V10 kernel (yes, my fault) and on the end I updated directly V10 to V11. It seems that everything working OK, should I except problems because of changed values in the ramdisk as [MENTION=4217103]zaclimon[/MENTION] informed us that we MUST flash original rom's kernel prior update?

Fake Nexus Rom doesn't have flashable kernel, I tried to flash boot.img through TWRP as well with the Flashify but ended with bootloop.

Thanks in advance for advice
[Nexus 4 Android Development] .stendeck:
Hmm… cannot confirm this phenomenon on Fake Nexus ROM. But I've flashed boot.img via fastboot:

fastboot flash boot boot.img

[MENTION=4217103]zaclimon[/MENTION]

Interesting new version. Quanta Tweaks now shows CPU max frequency of 1242 MHz by default. And CPU min frequency seems to adjust depending on workload?! That's a correct behavior, right? ;) But QT seems to crash frequently.
[Nexus 4 Android Development] zaclimon:
Well you won't have problems, only that you won't have the optimized values I've put in.

Yeah I've changed the max cpu frequency because there wasn't much of a difference and it can help in the battery life department.

As for the min frequency, that's a normal behavior and that's how cpu-boost works.

Last, about QT, I know why it crashes and I thought I've fixed that bug but it doesn't look like it... -.-

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] yaymalaga:
Great release! I will take a deep look to the cpu_boost. Btw the gpu freq is also set by default at 200mhz and maybe for general smoothness is better 320mhz as stock.

I will take several tests to see performance and battery with other gpu and cpu freqs, but the kernel looks really awesome, congratulations;)
[Nexus 4 Android Development] zaclimon:
I haven't found any difference in performance between using 200mhz and 320mhz. Sure enough my usage habits are different from the others but as I said, they're still free to modify it if they aren't happy. XD

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] yaymalaga:
Yeah, you're right, also every phone is unique
[Nexus 4 Android Development] zaclimon:
True, that said, I can't lessen everything just because I can't touch every device out there.

If really everybody has an issue with 200 mhz, then I'll change it. Otherwise, I'll leave as is.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] dragos281993:
Everyone can change it themselves, most probably. If not, they won't noticed the difference and won't complain, of course.

Dude, I've got to say, this final build is so good... Damn ! Maybe it's just me, but it's at least two times better than "test build 5", which was the best of all the other test builds. I saw all those tweaks you did, frequencies, etc, so you absolutely nailed it. I can't even dare touch anything. Is better than ever.

People should be very satisfied with v11 and grateful to you cause you're one of the few developers left to keep our Nexus 4 alive. Thanks !
[Nexus 4 Android Development] arjundas86:
Can't wait! Echo the thanks to Zaclimon!

Sounds like there's a new Chroma build coming soon, as Zephik is fixing some bug with FCs in Sound & notifications. Once that's out, gonna update Chroma and Quanta.
[Nexus 4 Android Development] dragos281993:
Why don't you use Pure Nexus ? It's as stable as it can get and you've got a few additional features that you'll never get on Chroma. And you also have 2 versions to choose from, both AOSP, one with Layers support and the other CMTE, so it pretty much gives you the ultimate experience on the Nexus 4. And it also has some additional tweaks that improve the scrolling experience. Pure Nexus + Quanta v11 + Viper|Atmos Sony Beats 4.6 = the best combination. I literally couldn't find anything better cause I'm pretty sure there isn't at the moment. But maybe this is just me, so it's just a suggestion.
[Nexus 4 Android Development] arjundas86:
Thanks... I'll check out PureNexus as well. Chroma has been pretty good for me for the last few months. I don't really use any theming/layers, so that's not a big deal. I just want a stable rom with reasonable performance for daily driver tasks (no UI lag), and good battery life.

Btw, does the "update your vendor image" apply to Nexus 4 or can we just skip it? I figure it's only for devices on which Google is still supporting Marshmallow.
[Nexus 4 Android Development] TheArt.:
Have you tried Krexus with Quanta?
[Nexus 4 Android Development] dragos281993:
No, I haven't. I went from Pure Nexus to Chroma and then came back to PN because it has a larger variety of features that happen to be exactly all I need, nothing more, nothing less, so I'm gonna stick with it. As for "Krexus", I'm sure it's a good ROM, and combined with Quanta v11, it would probably be even better. KreAch3R is a great dev, so without a doubt his ROM is good.
[Nexus 4 Android Development] jer_ying_fd:
Really enjoy this latest build, which is perfect for me after some minor tweaking for extra performance (cuz I'm a performance freak). Agree with above, users should tweak it to fit their own needs, because the stock settings are quite good on its own and I was really surprised how smooth GPU 200 mhz was like.

Also, I seem to have discovered that the app will crash whenever I change io scheduler from deadline to cfq. It doesn't seem to happen when I switch from noop to cfq though.

Edit 3: Somehow, I did not encounter any reboots when undervolting -50mv for all frequencies, but when I decrease 12mv for 1350 to 1512mhz, reboots start to come in. Never encountered this using V10 and other kernels before.

Edit 4: Reboot again so I guess both undervolt+cfq might have an issue for now, although not undervolting as much seems to have helped decrease the frequency of rebooting
[Nexus 4 Android Development] scissorscrush:
What did you do for scrolling?
[Nexus 4 Android Development] jolas:
[MENTION=4217103]zaclimon[/MENTION],

Thank you for last version of your excellent kernel.

Even if it is running really smooth with the setting it comes with (e.g. lowered frequency at 1242000), I want to have all the features that Nexus 4 came with , so I changed settings (it is attached as 'mychanges.rar').

But, I had a kernel panic reboot (never faced this problem with Quanta v10).

I don't know if this happened due to my settings changes, so could you please take a look at 'last_kmsg' and 'logcat'?

Thank you in advance
[Nexus 4 Android Development] dragos281993:
The ROM has "scrolling cache improvements" included. You can fiddle with it.
[Nexus 4 Android Development] Fenvarien:
Thanks [MENTION=4217103]zaclimon[/MENTION] for the great new version and your hard work! 200 MHz GPU frequency is working fine here and your Quanta Tweaks make it very comfortable to to apply custom settings, if needed. :good: :)
[Nexus 4 Android Development] jer_ying_fd:
Forget the earlier posts, here's my logcat

Settings changed:

Max frequency 1512 mhz

input boost duration 680ms

input boost freq 1134mhz

gpu max frequency 400 mhz

voltage -50 mv

digital headphone gain -1

speaker gain -1

Will see what happens if I use stock settings
[Nexus 4 Android Development] dragos281993:
Undervolting, man. That's the main culprit to pretty much everyone's problems. If I remember correctly, one dev once said that whoever undervolts the CPU, should be light on complains, or something like that. Undervolting creates instability and, from my experience, doesn't offer any real world benefits.
[Nexus 4 Android Development] jer_ying_fd:
It makes the phone run cooler, and I have been running the same setup since Lollipop times, I didn't even undervolt 1350 or above frequencies extra 12 mv. And it was fine in V10.
[Nexus 4 Android Development] dragos281993:
For me it feels like placebo effect. Just like f2fs.
[Nexus 4 Android Development] jer_ying_fd:
Still, it shouldn't have rebooted like that
[Nexus 4 Android Development] jolas:
An other self-reboot logs.

The only changes I done is setting max_freq 1512000 and input_boost_freq 1026000 :confused:
[Nexus 4 Android Development] dragos281993:
How did you flash the kernel. Write here the entire procedure.
[Nexus 4 Android Development] jolas:
Each time I update ROM or Kernel, I follow the exact same (flashing) order:

First clean cache, dalvik, data, system...

Then flash:

1. boot.img and system.img (Fake Nexus ROM)

2. Cataclysm mod

3. kernel

4. SuperSU (2.67)

5. Xposed framework

6. restore data

Between each flash, clean cache & Dalvik and reboot in recovery.

Never faced any kind of problems with above order, while on Quanta v10.
[Nexus 4 Android Development] dragos281993:
I don't use Xposed and restore apps and data only with Titanium Backup. I didn't get any problems. So, if for me everything is working perfectly fine, it should work for you too. What kernel manager are you using ? Cause if you backed up data and you had "apply on boot" checked, after restoring it, it's gonna try to apply the settings you had with the previous kernel.
[Nexus 4 Android Development] jolas:
I follow exact the same order a long time now, without facing not a single problem.

So, the problem is either with the settings I changed or with Quanta v11.

As for kernel manager, I use Kernel Adiutor and I have no setting applied with this application

The kernel changes I did by changing init.performance_profiles.rc and modrd.sh :)
[Nexus 4 Android Development] zaclimon:
Yep the issue is with quanta V11. (As far as the panics are concerned) I'll do some quick patches and possibly release a V12 today.

[MENTION=5579519]jer_ying_fd[/MENTION] do you have a logcat of when you're changing I/O schedulers? So far for me, it is working normaly.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] scissorscrush:
Something that I can do?
[Nexus 4 Android Development] dragos281993:
Sorry, I said "you can fiddle" but I misstyped. You can't modify it.
[Nexus 4 Android Development] jolas:
Sorry, in my previous post #1431 I forgot to attach the new logs...
[Nexus 4 Android Development] jer_ying_fd:
I think I did a report when the app crashed, so I wonder if you can check it from Google Play? It was titled constant crash I think. If not then I will do a logcat as soon as possible since I'm studying atm :P But shouldn't take too long as I only have one page of exercise left to do for the day.
[Nexus 4 Android Development] zaclimon:
Yep I see the crash. (Forgot that functionality existed for a sec XD) As far as I see, the crash is the exactly the one I'm trying to squash right now.
[Nexus 4 Android Development] jer_ying_fd:
Glad to have helped!