yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] shaker2k:
Hey Franco. Are you getting a wakelock problem related to google services/system update service? The phone won't go into deepsleep I'm running stock cm plus your kernel. I also had the problem on stock. Not much is installed besides a few rooted monitoring apps. Like better battery stats and wakelock detector. When I google it I get the response that it is a cm problem.

I did post this in Q&A but seeing how there is not many users for the device yet I decided to post it here as well in hopes that you can help me.

By the way... I GOT THE PHONE (obviously)!! Would not have if not for your review on it. I love it!

Really want to see what your kernel will do but can't get a good read with the waklock.
[ONE Original Android Development] erdal67:
Try

-Open a root filemanager

-load system as RW

-Go to system/etc

There is a file called hosts

-Open it with a code editor ( https://play.google.com/store/apps/details?id=com.henrythompson.quoda )

- Add a line called 0.0.0.0 mtalk.google.com

- reboot

- if you have luck it should work for you
[ONE Original Android Development] Mnt-XDA:
See my previous post with attachment...

---------- Post added at 10:17 AM ---------- Previous post was at 10:14 AM ----------

See my previous post. Flashable stock boot image for one plus one cm11 25R
[ONE Original Android Development] JustinOkay:
Thank you for Franco for all your hard work. :good::good::good: I've been following you on N4, N5, and now on OnePlus. :cool: I've purchased your paid updater and recommended it to many friends and family. :p

For anyone wondering I would like to confirm that r2 does not support CM11 bacon nightlys.

Any chance stock CM will get support? :laugh:
[ONE Original Android Development] fiz:ik:
Why does FKU not save my settings? I set governor to ondemand and IO scheduler to noop but it wont save that. After a reboot everything is stock (gov: interactive, io: deadline).
[ONE Original Android Development] david23c:
r11 boots with the 30O incremental also (along with the 30O OTA)
[ONE Original Android Development] Red5:
So having a custom recovery (twrp) will kill the OTA? Damn, now I gotta go back to stock recovery...
[ONE Original Android Development] Tzfardaya:
Just download the update from the ap link posted earlier today... Worked for me (custom ROM , edited system files) lost root, but kept twrp so it was an easy recovery.

---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------

[MENTION=4782328]Red5[/MENTION] here's the link
[ONE Original Android Development] goldenratio:
:good: just wanted to report this r11 kernel seems to be working well with XNPH30O. thanks!
[ONE Original Android Development] LiquidSolstice:
No no, TWRP works fine. CM Updater sends an OpenRecovery Script to Recovery, which TWRP will beautifully handle with no user interaction (just like a real stock OTA on any other device).

Just make sure you don't download the second incremental update before finishing the setup wizard; you'll want to go to Dev settings and uncheck "Update CM Recovery" before doing the OTA, otherwise the OTA will flash with TWRP, and then overwrite TWRP after it's done.

It's not really a big deal but it's a minor headache you can avoid.
[ONE Original Android Development] MICa.fighter:
Thanks for trying :)

I noticed that post but my phone is still locked & unrooted, so i couldn't try. :)

Tapatalk'd from my 1+1
[ONE Original Android Development] paychex:
Yup same one

---------- Post added at 02:44 AM ---------- Previous post was at 02:41 AM ----------

Why make it complicated? Use the damn fastboot and make it simple
[ONE Original Android Development] zephiK:
Maybe he's not at a computer? If you want to keep things simple, just use Flashify. No USB cable needed ;)

Plus the Flashify app is made by one of Franco's good friends
[ONE Original Android Development] mr pnut:
You can also use Rashr from the playstore its a really good app for flashing IMG.
[ONE Original Android Development] mr pnut:
Sweet......
[ONE Original Android Development] weppa83:
flashed franko's boot.img for XNPH30O with flashify, but my opo is gone in bootloop.

can someone upload the XNPH30O 'stock kernel?

thanks
[ONE Original Android Development] mr pnut:
Here you go stock kernel from XNPH30O https://www.dropbox.com/s/8by4ljbf5crht7j/boot.img
[ONE Original Android Development] paychex:
then wait
[ONE Original Android Development] SpOuK-3-:
And you are damn right ... And it's booting... So, is it something with the fku app? I also tried Flashify and it's also working...
[ONE Original Android Development] theglock:
:laugh:
[ONE Original Android Development] HaruSoul:
So I'm not sure if this is an ROM or kernel issues, but if I'm playing music from Pandora and lock my phone sound is at 100%. If I pause Pandora from my lock screen and just leave it there for like an hour or whatever and never close the app, and I want to start playing music again and just hit the play button from my lockscreen. The music plays at about 60% volume for the remainder of the song that I left it at, once it starts a new song it goes back to 100%.
[ONE Original Android Development] lordlambda:
Flashed 30O via twrp as zip and Franco kernel via flashify (boot.img) works perfect! :thumbup:

Gesendet von meinem A0001
[ONE Original Android Development] Red5:
Thanks guys. I did this and it went smoothly. I like the update. Not to try an actual phone call and see if it did in fact fix the in-call volume.
[ONE Original Android Development] XxKINGxX2580:
Thanks! I did the same thing. Got stuck on a boot loop, and I found the stock kernel here.
[ONE Original Android Development] Tzfardaya:
Is it fixed?
[ONE Original Android Development] zephiK:
Yeah it has. Fixed in nightlies too. Try it out by calling voicemail on your phone. Feels weird saying that because not many people make phone calls anymore but with voice mail you can try it out lol
[ONE Original Android Development] Tzfardaya:
I never had an issue with call volume to begin with...
[ONE Original Android Development] zephiK:
Some people found it to be too low, especially in places that are loud. Shrug, I don't do phone calls... well I do, but very rarely.

Edit: Can anyone confirm that the buttons are brighter with the new boot img ? I'm still on r10 on my custom rom.
[ONE Original Android Development] Tzfardaya:
Yeah, I usually have a bluetooth headphones/headset on when I'm making calls, internal amp so....
[ONE Original Android Development] Red5:
The buttons are not brighter with the update.

Also, calls are louder that before. Speakerphone is really loud now. Ear speaker could be louder still.
[ONE Original Android Development] Rhokk:
bootloop

So I'm running the new 4.4.4 update that I sideloaded via recovery. Got the message hours later that a kernal update was available via the Franco app. So I updated and rebooted to a bootloop. I went into TWRP and made a nandroid of this and restored to my backup that I had made 2 days ago that was still on 4.4.2.

My question is, any way I can restore this problematic nandroid and fix this bad kernal? Like do the restore and then flash or sideload something via TWRP? Or just boot to fastboot and flash...?

Any help please.
[ONE Original Android Development] jarjar124:
Flash the stock 30O kernel. That should fix it from what it looks like. Don't update through the app as far as I'm aware, the kernel update isn't available in app yet for 30O.
[ONE Original Android Development] Rhokk:
OK I will do this. Am I correct in that the kernel is the "boot.img"?

Also can I do this in TWRP? I only ask because I'm now at work without access to a PC for 10ish hours. So no fastboot for me.

1. Full restore my messed up 4.4.4 nandroid.

2. While in TWRP, Flash/restore 30O boot.img.

Or

1. While in 4.4.2, use flashify, flash 30O boot.img

2. Restore my messed up 4.4.4 nandroid, unselected restore boot option.
[ONE Original Android Development] zephiK:
The boot.img listed a couple pages back is only for XNPH30O which is Android 4.4.4.

If you want to flash that ensure that you're on 4.4.4 and on XNPH30O and use Flashify to flash the boot.img (find it on play store)

If you're on Android 4.4.2 (XNPH25R) then flash r10 from OP via flashable zip in TWRP.
[ONE Original Android Development] Rhokk:
all good...

OK I'm all sorted out now. Was able to get my nandroid restored with stock 4.4.4 boot.img! I will go back to Franco when everything settles down. I learned a few thing during this small heart attack. Thanks for the help fellas.
[ONE Original Android Development] paychex:
correct... don't upgrade from the app until you see r12
[ONE Original Android Development] auggie246:
Hi I am using mahdi ROM. And when I use r10 kernel instead of stock kernel The headphone volume is horribly low. I search this thread and there are others like me. I am just wondering if this will be fix in the future updates
[ONE Original Android Development] pekeltje:
Where did you get #11 ?

I only see #10 in paid FKU and this topic.

Is it a beta?
[ONE Original Android Development] MICa.fighter:
Tapatalk'd from my 1+1

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

Go to the quoted post of franco, you will see the boot.img attached.

Tapatalk'd from my 1+1
[ONE Original Android Development] omoithesane:
Reboots with r11

Had two reboots with r11 since flashing it yesterday. Flashed using Flashify. First time I wasn't doing anything on the phone, second time listening to music.

I have attached last_kmsg for both reboots. Hope that helps
[ONE Original Android Development] paychex:
it's posted in this thread
[ONE Original Android Development] Тhe Dark Knight:
Also had 2 reboots for today. R11
[ONE Original Android Development] Tzfardaya:
Logs?
[ONE Original Android Development] david23c:
So it seems that r11 broke the new vibration strength setting from the 30O update. I couldn't change the strength (the setting was stuck at 100% but the actual vibration was weaker) until I reflashed stock kernel. Maybe a fix coming?
[ONE Original Android Development] bradm23:
Just reporting that I had four reboots today on latest OTA with Franco r11. I was not able to get a log but all the reboots happened during a phone call
[ONE Original Android Development] franciscofranco:
Pushed r11. It's different from the one I posted 2 days ago. It's only for the new OTA, it won't work on older CM11S versions. Also if you're on CM11 nightlies or derivates r11 was also deployed and it's available from my server.
[ONE Original Android Development] nicholaschum:
Great, is there a more complex changelog to see the individual commits?

As I see "ONLY FOR THE NEW OTA 30O", I'm just wanting to see what the changelog looks like for the AOSP build :)
[ONE Original Android Development] zephiK:
https://github.com/franciscofranco/one_plus_one/commits/cm-11.0
[ONE Original Android Development] nicholaschum:
Great, thanks zephi.

So r11 disabled/reverted the new synaptics workaround...I wonder what CM would do.
[ONE Original Android Development] Spider_Pig27:
Thanks for r11 aosp
[ONE Original Android Development] zephiK:
Is anybody able to reproduce by inserting a headphone (doesn't matter what headphone/headset it is) audio is playing and no sound is being output? Not exclusive to a music player but sound as a whole. When unplugged it goes to speakers. Volume during headphones is set to high and I swapped to all different levels of volume.

As a workaround, I was able to reboot the phone with the headphones already plugged into the jack and then it worked but if the phone booted up without headphones already in the jack. It will fail to work. It seems to vary between different kernels being used, I was trying out another kernel and it was perfectly fine but on another ROM's "stock" kernel it would encounter this problem only for headphones with microphones.

Edit: Yep, I just removed Viper/DSP Manager and it all came to the same route but when I used the same settings and went to use ak kernel then this problem didn't occur. On r10, I noticed this happen as well, was hoping that cm audio commits would have fixed it. This is also on the "aosp" version of the kernel.
[ONE Original Android Development] auggie246:
Zephik I set fku headphone boost to 1 for audio. But my problem of Lowe headphone volume still exist, with franco kernel. If I set boost to 0 and reboot i get no volume at all

Edut: Temporarily switch to ak just to listen to music at suitable human volume
[ONE Original Android Development] shure2:
Thanks for r11 AOSP. Unfortunately during use the touch screen started to have issues and not respond. I therefore have gone back to r10 which seems to be more stable with the touchscreen driver
[ONE Original Android Development] trojanz:
Are you on the new OTA?
[ONE Original Android Development] bud77:
CM has reverted a commit about the touch screen issue, which also caused reboots : https://github.com/CyanogenMod/andr...mmit/7be7330da001462d1146c4a1c412a1b88666ad9f
[ONE Original Android Development] musashiken:
Hi franco, the latest CM11S OTA is causing the proximity sensor to be on the whole time.

I know that the proximity sensor is used to prevent double tap to wake in pockets but does the sensor have to be on the whole time?

Can your kernel turn it off or use it only when touches are detected on the screen?

If you take another handphone camera and look at the OPO though the camera app, you can see the IR light that's constantly blasting from the sensor.
[ONE Original Android Development] jdec529:
This is a problem with the new ota not Franco's kernel.
[ONE Original Android Development] musashiken:
I know. But I was asking if Franco can do something with his kernel for a temporary solution or otherwise we will have to wait til CM does something.

The developers for HTC One M7 could write code into their custom kernels to achieve something similar for the proximity sensor so maybe franco can do something about it.
[ONE Original Android Development] jdec529:
Lol. Sorry. Don't know how I missed the first line of u saying it was from ota. Anyways CM is aware and working on an expediting a fix. As far as I'm aware Franco can do anything from his level to fix it.. Would be nice if he could. It's killing my battery.

Edit : it's not killing my battery but has effected it.
[ONE Original Android Development] musashiken:
Yeah, actually I'm more worried about an invisible light beaming and frying my cells constantly :silly:

Can you imagine an IR beam pointing at your head every time you look at the screen or making a phone call?

I don't know if IR beams are safe or not, but for the time being I turned off double tap to wake and all the gestures as a temporary solution.
[ONE Original Android Development] jdec529:
I turned them off also, but I don't think it will hurt u. Some phones like the Moto x always have it on with their active display or whatever it's called. I think my note 3 would always be on with certain settings so I could wave my hand over it to get notifications. You might get a little tan spot in the forehead though. Lol.
[ONE Original Android Development] shure2:
No I'm using PA that's why I said AOSP in my message. I'm using the AOSP version
[ONE Original Android Development] clock51:
This is the kexec patch in r11 v
[ONE Original Android Development] paychex:
Proximity sensor uses so little battery the extra drain is almost imperceptible

---------- Post added at 08:08 AM ---------- Previous post was at 08:05 AM ----------

No it isn't. On my N5 I use the proximity sensor to wake my phone, so it's always on. I had it sitting for 10 hours on LTE with everything syncing, location on, Google now and had .4% drain an hour
[ONE Original Android Development] omoithesane:
Screen flickering on lockscreen

Hello,

I am not sure if my issue is related to franco kernel, but I haven't observed it on stock kernel. Maybe I just didn't realize, so a question to all franco kernel users.

When I use the OPO default lockscreen with lockscreen background and desktop background beeing the same, there is a very noticable screen flickering when unlocking. I'd say it is about half a second, screen shows lockscreen background -> black -> shows desktop.

When backgrounds are not identical, there is no flicker.

When i use the CM/AOSP lockscreen, there is always a flicker, not matter what the backgrounds.

As I said, I only noticed it since using franco kernel r11 for CM11s latest OTA. Haven't noticed it with default kernel, but I am not saying it isn't there.

Another reason I am asking here is that I remember a similar issue on my Xperia SP using DoomKernel with dynamic F-Sync on. I think he was somehow able to fix it, but it might be a totally unrelated thing to this isse.

Any of you noticed the same?
[ONE Original Android Development] jdec529:
That's why my idle drain goes from 1.3% hour to .8 % per hour by turning gestures off and rebooting. And everyone on the one plus one battery thread in the general section that is getting similar results is wrong. And I go from averaging 30-50 mA at idle to 17-25 by turning it off. My bad. [emoji1]

Edit: I may have been wrong for saying killing my battery but it is effecting it in a negative way.
[ONE Original Android Development] paychex:
When you turn the gestures off, you turn off the digitizer, which will cause significantly more drain than the proximity sensor sensor

---------- Post added at 08:39 AM ---------- Previous post was at 08:38 AM ----------

Not seeing it
[ONE Original Android Development] jdec529:
I agree that the digitizer has more drain but it is still double it was before last update with gestures on where proximity sensor wasn't all the time. And CM acknowledge its was a problem and had said that they were going to expedite a fix per Steve kondik. Let's just agree to disagree [emoji1]
[ONE Original Android Development] Spl4tt:
Turning gestures off should turn digitizer and the sensors off, right?

In my opinion it should suck less battery then? OO
[ONE Original Android Development] paychex:
No one is arguing that. My point is the drain from the proximity sensor is not very high at all.

Using Phone Tester Pro https://play.google.com/store/apps/details?id=com.mtorres.phonetesterpro

I found the draw from the proximity sensor to be .37mA

So (.37*24)/(3100*100)=.29%

So in a 24 hour period the proximity sensor accounts for just over a quarter of a percent of your battery drain
[ONE Original Android Development] franciscofranco:
They are waiting for a newer touch firmware from synaptics. The cause for this weird touch issue is much deeper than simple firmware problem though and it's agravated by the ambient temperature. The hotter it is the more odds of derping. I know the real cause of this, but I'm probably not allowed to share, so hang in there.

Steve pushed a patch to prevent the controller to mess with the panel voltage during screen idle cases (after they reverted the workaround) and so far Im not having any more issues (included on r11).

I cannot reproduce, but they have been messing with the audio drivers, specially Steve. One already not present patch once caused my Apple earbuds to stop working altogether. Its possible there are bugs because I'm always pulling from them sometimed even less production-ready patches. Hang in there. If you manage to get logs or something send them to me and I'll forward them to rcee or Steve.
[ONE Original Android Development] franciscofranco:
I can see to it. If there were changes to the sensor behaviour it was all in userspace, I haven't seen any Kernel patch. But the drivers for it are in the Kernel. You understand that turning off the sensor will increase the chance of having mis-clicks while the phone is on your pocket don't you (with double tap to wake enabled of course).

The Kernel has absolutely no corelation with the lockscreen. It doesn't even know what a lockscreen is.
[ONE Original Android Development] aeppacher:
Are your apple earbuds working now? For me they output sound but when ever I try to use them in a call the receivers just receive a loud tone that doesn't end til I unplug them. Its frustrating because I like using them as a mic
[ONE Original Android Development] zephiK:
My setup: I use Poweramp so whenever it detects a headphone being plugged in, it will automatically start playing the song.

Disabled any equalizer apps (viper/dsp/etc).

Scenario 1: Using AK Kernel (not encountering this problem on this kernel)

Rebooted the phone. Waited for the widgets to all load up while keeping the phone screen on.

Headphone (without microphone) works.

Headset (with microphone in 1 headphone jack) works.

Scenario 2: Using Franco Kernel r11 (occurs on previous as well)

Same as previous scenario. Waited for the widgets to load up keeping screen on.

Headphone: works

Headset: the jack gets inserted in the same way as I insert the headphones, poweramp does not auto play when i press play on poweramp the phone for some reason outputs the audio via speakers instead of the headset.

Workaround: Slowly plug the jack half way in.... hear the music start outputting via headset but and then a few seconds later I insert the jack fully in and then it works.

Unplug... replugged but this time in a way that it isnt being plugged in slowly (same as how I plugged in the headphones), outputs to speakers.

Used a audio splitter (splits 3.5mm jack into two audio jacks.. 1 for sound and 1 for microphone) plugged it in the same way as I plugged in headphones (without half way then it will play as if it was a ordinary headphone without any problems)

Logs are attached in attachments (included kmsg,last_kmsg,logcat)

ROM: Mahdi

Kernel: Scenario 1 for AK and Scenario 2 for Franco Kernel r11.

Hope this helps... Oh yeah and the headset works completely fine on the Nexus 5 running r59. No problems there, inserted normally as I would. And when I mean insert I just plug it into the 3.5mm jack nothing special. The workaround I found out from somebody else that was having this problem as well.
[ONE Original Android Development] franciscofranco:
They don't work for calls on this device. I don't remember the cause, but I doubt its ever fixable.
[ONE Original Android Development] franciscofranco:
Have you tried the latest r11 on aosp folder with the latest CM11 nightly? Nevertheless I will forward this report to the CM guys!
[ONE Original Android Development] Tzfardaya:
Iirc, it's because apple reverses the contacts, and most non-apple devices try to auto sense which pattern is used... Most, not all...

Apple with their nonstandard connectors and all... :(
[ONE Original Android Development] Red5:
Enhance.

Enhance.

Enhance.

After some sleuthing, I found the culprit.
[ONE Original Android Development] Tzfardaya:
Bingo...
[ONE Original Android Development] zephiK:
Just flashed CM11 nightly with r11 AOSP and the same thing case scenario in scenario 2 occurred. Used Apollo (CM Music Player) this time as I didn't want to restore all of my apps etc.

Headphones worked fine by just directly plugging it in.

Headset plugged in directly, pressed play, output sound via speakers. Put in headset half way, heard a static sound, pressed play.. played via headset.

Tried CM11 stock kernel as well, same scenario happened. It doesn't happen in AK kernel though, hmmm.

Whats weird is that if you say OPO out loud, it sounds a lot like "Apple." :p
[ONE Original Android Development] Tzfardaya:
Meh, I always hear psy's gangnam style song in my head when i see opo....
[ONE Original Android Development] shaker2k:
Lol [emoji1]
[ONE Original Android Development] prstorero:
[MENTION=3292224]franciscofranco[/MENTION] or anyone else, does anyone know where the color calibration settings are stored on a device? I was hoping to find out from one of Vomers tweaks for the N5 that had some color changes in an init.d script, but I can't find any working downloads. Does anyone happen to know?
[ONE Original Android Development] franciscofranco:
I just pushed r12 which contains the fix from CM for the higher battery drain since 30O OTA - go grab it!
[ONE Original Android Development] chachin:
so this means I cant use your kernel if I'm on pa4.5b2?
[ONE Original Android Development] franciscofranco:
Who said that? Just use the image from the aosp directory...