yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Klewe:
Me too. Mostly happens on message sounds.

Another bug I faced is with the alarm clock. When I choose the alarm sound and select Ringtone --> Music and choose the song I want for ringing everything is fine and it also shows up as the song I selcted, but when the alarm starts ringing i only get the "beep beep" sound.
[ONE Android Development] icsakhil:
Totally agree with you. Linux is better.
[ONE Android Development] LiquidSolstice:
I exclusively use Linux at home and as much as I can at work, but how about we have a grown-up attitude about the fact that Windows kills the competition when it comes to enterprise-grade applications, mmkay? When Office, Visio, VMWare, vSphere, Photoshop, Premiere, and many others start running on Linux, I'll agree that there's not much of a point in Windows. The "open source alternatives" you're about tell me about don't even come close, so please don't bother. Trust me, every day I look forward to switching my company over to exclusively Linux platforms, but it's just not there yet.

We're not 13 years old here. Let's be mature about this.
[ONE Android Development] BarnOwl:
Anybody tried to change the user photo? Doesn't work for me. It happens in the last build and it happened in the build before, which was the unofficial CM 12.

Further it is a very smooth and efficient rom (Got an Antutu of 50666).
[ONE Android Development] katinatez:
log in to google + account and tick use contact
[ONE Android Development] kecinzer:
[MENTION=3814731]katinatez[/MENTION]

Can we look at proximity wake feature for bacon? It seeems that those "accidental wake" prevent phone to turn on when it's in dark. But not only from double tap to wake, but also from power button and from wake events from incoming call. Do you think you can look at it and fix it?

I realy like those feature on kitkat, but on that version power button normaly works even in dark as incoming calls wake.
[ONE Android Development] Khizar:
That's a CM12 issue. I have had it on all roms, including official CM12.

Sent From My Material Dark Tema'd A0001 With AK Awesomeness To All You Wonder Nobodies!
[ONE Android Development] kecinzer:
Yes, I know it's CM12 issue, but why [MENTION=3814731]katinatez[/MENTION] can't look at it? :)

Or can please tell me how to submit it into CM team?
[ONE Android Development] Khizar:
Yeah I was about to edit my post when you replied. This should fix that issue.

http://review.cyanogenmod.org/#/c/84385/

Sent From My Material Dark Tema'd A0001 With AK Awesomeness To All You Wonder Nobodies!
[ONE Android Development] kecinzer:
I looked at this patch, but it requires SE policy that is for LG phone - http://review.cyanogenmod.org/#/c/84389/

Did you tested it with bacon?

This patch definetely don't fix it. It's for issues with turning display on durring calls ;).
[ONE Android Development] aswinrulez:
So is there any fix for this yet?Does CM devs know it or should we raise a defect?
[ONE Android Development] TheWilkieWay:
Is anyone else still getting audio static? I've tried putting two cores minimum in synapse and that helps a fair bit but once I turn the screen off I get terrible static when listening to music.
[ONE Android Development] Khizar:
Well we have both phone not waking for incoming call and phone not waking while in-call. And I know that those commits only say it's for in-call but I believe those 2 issues to be linked so that's why I think IF those commits work for us those 2 issues should be fixed.

I don't know much about git, just try and understand to the best of my ability. Guess we'll see what [MENTION=3814731]katinatez[/MENTION] thinks and whether the issue gets fixed next build..

Edit - BTW just noticed that with proximity wake disabled when phone is asleep it sometimes doesn't wake with smart cover being opened.

Sent From My Material Dark Tema'd A0001 With AK Awesomeness To All You Wonder Nobodies!
[ONE Android Development] tobitege:
Hmm... incoming call wake-up and screen on/off while putting phone to/away from ear is working for me and probably others.

So why are there exceptions to this? With the past days' discussions about upgrading modem or not, imho, this is currently the only variable when we are using all the same rom build. If it works for me, why shouldn't it work for you... somehow. :) /rambling
[ONE Android Development] Khizar:
It doesn't have to do with modem, I never had those issues that users had with modem. This issue had been there since the first CM12 build, it's a known issue that many have reported. But it's a fact that the issue somewhat gets fixed in some builds and phone wakes up 9 times out of 10 and in some builds it's vice versa.

BTW do you have proximity wake enabled or disabled? This issue is caused by it being enabled.

Sent From My Material Dark Tema'd A0001 With AK Awesomeness To All You Wonder Nobodies!
[ONE Android Development] tobitege:
I have "Ambient display" and "Prevent accidental wake-up" always disabled.
[ONE Android Development] expiredd:
I'm in 4.6 special with CM alpha modem and AK80. I'm experiencing heavier Android OS battery drain than previously. It's true that now we can't block kernel wake locks straight from ROM (I used to block alarm wakelock)
[ONE Android Development] smint86:
And second is, why it works. It's not about ambient display, which just works fine since [MENTION=3685904]ak[/MENTION] fixed it in I think v0.77 or so.

You can easily reproduce it:

- enable prevent accidental wake-up

- cover proximity sensor with your finger or anything else

- give yourself a call

- screen won't turn on

I think the prevent accidental wake-up setting just is given “more priority“ and the screen on for call is just regarded as power button press or double tap, why phone prevents screen from waking up.

If you disable the option (or uncover the sensor with option activated) it works as it's supposed to.
[ONE Android Development] Khizar:
Yeah that's why you haven't noticed this issue.

Using the same setup as you and no issues. May wanna try clean flashing.

No. That's the problem. It doesn't work even when sensor is uncovered.

If it was working right that's how it would be working. The point of that feature is to keep screen off when proximity sensor is covered, no matter what BUT once proximity sensor is uncovered screen should turn on. Which it doesn't.

Sent From My Material Dark Tema'd A0001 With AK Awesomeness To All You Wonder Nobodies!
[ONE Android Development] ak:
I'm checking kernel wakelocks every day, and with 4.7 standard i have 0 problems.

---------- Post added at 12:42 PM ---------- Previous post was at 12:39 PM ----------

I have made a few tests and the rom work like a champ:

- enabled prevent accidental wake-up

- cover proximity sensor

- made a call to my phone

- screen remains off

- i can wakeup with power button

- disabled prevent accidental wake-up

- cover proximity sensor

- made a call to my phone

- screen goes on without problem

I have verify proximity functionality (ok for me) with cpu-z app.
[ONE Android Development] kecinzer:
@ak

Did you tested it with Prevent accidental wake-up enabled and cover up proximity sensor?

If you have you phone in light room, it works.

But when you have it in your pocket and someone calls you, display don't turn on.

EDIT: Ah, I red again your post.

- enabled prevent accidental wake-up

- cover proximity sensor

- made a call to my phone

- screen ramins off

- i can wakeup with power button

Thats exactly wrong behaviour. When someone calls display have to turn on on every case!

BTW. I just tested it and when I enabled "prevent accidental wake-up" and cover proximity sensor, I can't wake up with power button!
[ONE Android Development] ak:
yes, it seems to work from my point of view.
[ONE Android Development] smint86:
I think you didn't get be right or I explained not good enough. What I meant with “works when sensor uncovered“ is, that if the phone lays for example on the table, the screen will light up when a call comes in, no matter if option is enabled or not. With the rest I agree with you.

Problem is: You have the phone in your pocket, call comes in, with option enabled screen should stay off (to protect from maybe accidentally answering the call), but when you take the phone out and uncover the sensor, screen should light up so that you can see who calls you.
[ONE Android Development] kecinzer:
Yes, exactly that way it suppose to work for me! Thanks for this explanation :).
[ONE Android Development] tobitege:
[MENTION=4519152]Khizar[/MENTION] [MENTION=4164878]smint86[/MENTION] [MENTION=525305]kecinzer[/MENTION] [MENTION=3685904]ak[/MENTION]

Thanks, guys, learned something new from the discussion about that tricky option(s)!
[ONE Android Development] martinmax1:
I'm also experiencing heavier Android OS battery drain than previously. Yesterday i've upgraded from 4.5 to 4.6 SE and Google Services and Facebook Messenger are draining too heavy ( 20% battery in one night ) which wasn't the case on the previous version ( 3% battery in one night ) . Im using Boeffla kernel.
[ONE Android Development] kipue:
I can still, as AK said, wake the screen with power button, although it silences the sound.

For people with accidental wake up turned off, do you find your phone turns on in your pocket, like the leg "doubles tap" it or something?
[ONE Android Development] Life Engineer:
Hey guys!

Excuse my ignorance but if I wanna flash the latest build with the most features and original light/white material (not black/dark) which should I use?

cm-12.0 sabermod temasek OR cm-12.0 stock temasek?!

And what's the difference?
[ONE Android Development] LookedPath:
I'm one of the few that are having some heavy draining since the last few versions and I presume that at least for me it's caused by all this Play Services alarms.

The strange thing is that I've just updated the rom as usual and in the past I never had problems.

It seems that all theese alarms are triggered by the location service but I always left it in low drain mode since I don't need the GPS always on but I need that the phone knows its position through wifi.

If someone could give me any advice it would be great.

I'm on 4.6 sabermod, the first version without all the graphite optimization.

Thanks
[ONE Android Development] Criton30:
If somebody call me then the Display wont turn on only if I press the power button. This is a future or bug? Can I resolve this issue?

Temasek SM 4.7 full clean install, all is stock.
[ONE Android Development] cd69:
You can flash either. The dark version attained with a flash file so you don't need to worry as you want white. In terms of the difference between the two a link is mentioned in op about tool chain.

Oneplus Nexus 5
[ONE Android Development] Mrj0to:
Disable "prevent accidental wakeup" that should do the trick.

I had the same issue. But having read the previous 3 pages I knew what to do :)

---------- Post added at 02:14 PM ---------- Previous post was at 02:09 PM ----------

Since when is the incoming call pictures fixed? I thought this was a lollipop issue that it would work only if animation were set at 1.

I found the animations too slow at one so I put them back at 0.75 and I just had a call with a contact picture :D

Was this fixed by the 5.0.1 to 5.0.2 update?
[ONE Android Development] fjsferreira:
The contact picture bug is random, sometimes they appear, sometimes they don't.
[ONE Android Development] Mrj0to:
Unfair! [emoji22]
[ONE Android Development] IAmNiceify:
My drain was pretty heavy too. From 70% to 2% in just few hours and even not using my phone.
[ONE Android Development] P4ll1n01:
amazing performance thanks

thanks for your amazing works

is stable and very very fasssst

all work without lag

and....

I'm sorry for my previous post
[ONE Android Development] gianton:
No issues with extreme battery drain on v4.7 here, using either ak v0.80 or stock kernel.
[ONE Android Development] miragez:
Hi all,

Temasek and katinatez coming back for this build again cheers and thanks for everything you have done for OnePlus one with CM12.
[ONE Android Development] Gamm86:
Same. No issues.
[ONE Android Development] Criton30:
can somebody confirm this?
[ONE Android Development] smint86:
I have it enabled as well (I think it's the stock setting) and am not facing any reboot problems at all.
[ONE Android Development] Criton30:
with stock kernel is no issue in Antutu, but if I flash AK kernel 80 and run AntTutu and settings/performance/enable per-app profile is enabled then after 27% in Antutu the phone rebooted. If per-app is disabled then there is no issue with Antutu and with AK kernel.... I can not understand some issue (reboot), the phone has the same hardware, sometimes the same OS/Software configuration, and one user has no issue and the other has....

everybody has dirty flashed 4.7 sm over official cm12 nighlty?
[ONE Android Development] expiredd:
I just flashed 4.7 and leaving stock kernel. Charging up. I'll test it this week.
[ONE Android Development] bundysoat:
Hey guys.

I report an error that have found.

The volume key, not work to wake the device and the same error to past the tracks on music players.

And in profiles settings, when you try to create a profile with the sound mode at "silent", the option will be a FC, and not works. The profile it's possible to create it, but not work in this mode.

P.D: when I find the modem of cm12 nightly?

Enviado desde mi OnePlus One.
[ONE Android Development] tobitege:
in [MENTION=3814731]katinatez[/MENTION] Misc folder (link is also in first post!)
[ONE Android Development] Srikar_NBK:
Strange issues

I'm facing 2 strange issues:

1) When connected to my home Wifi, I'm unable to receive any calls. When folks call me, it directly goes to my Voicemail. When disconnected from Wifi, calls start coming in normally.

2) Double tap to wake doesn't work most of the time. Sometimes, have to tap the screen harder to make it work.

Anyone else facing similar issues?

Edit: After some more testing, looks like the issue is not with LTE or Wifi. My radio seems to be broken, inspite of being on the CM 12 nightly one
[ONE Android Development] spazen:
Hi,

Using cm-12-20150108-UNOFFICIAL-sm-temasek-bacon-v4.7

there are bug issue :

- Charge only can't be selected and goes back to MTP

- When you turn off MTP connection, then can't turn it back on no matter what. All options are then greyed out and can't be selected anymore. Moreover after MTP is un checked, I cannot go back into usb connection option and stuck in storage option. quite annoying because all transfert are now impossible.

Can someone confirm this ?

cheers
[ONE Android Development] martinmax1:
Im on 4.6 and i'm able to reproduce this bug.
[ONE Android Development] UltraBoykj:
This ROM with Dark Material is extremely beautiful. I appreciate all your efforts. Currently Running 4.6 ( not SE ) ATM with standard kernel and alpha modem. Would there be any concerns with flashing SE or 4.7 over my current setup? ( been reading about TWRP disappearing and proximity sensor not working etc )

It's all working so well at the moment, Im worried about flashing a new kernel on it. Last time I did, my USB connection stopped working properly ( it would charge, but never mount and when I pressed the button it did nothing at all ).

That said, once my paypal funds come through ( added 2 days ago ) Ill donate to the devs. Thank you again for making my 1+ run so smooth.
[ONE Android Development] ek69:
To all the ppl above [MENTION=4877142]tobitege[/MENTION] [MENTION=3281463]aosimon[/MENTION] [MENTION=4415183]icsakhil[/MENTION] use the app called zarchiver. You can explore the zip right on your phone, browse to that location, delete the file, add the right updater-script file by clicking the plus sign in bottom right of app then select it, then flash. No need for a PC at all :) [MENTION=3814731]katinatez[/MENTION] can you add this info into op or 2nd post so we can direct all users to this info instead of typing it out everytime ? :)

Stock settings of AK 080 seems to be over clocked. Not every phone has the same grade of CPU you can check this in synapse. Install UKM then synapse then put clock frequencies to stock and then I suspect you won't have any reboot problems. I suspect your specific CPU is lower grade that can't run at the over clocked speeds

See my screenshot below. Look at the SOC binning numbers. If they are lower than mine, the CPU can't run stable at over clocked settings. Mine was also over clock by default I dunno if [MENTION=3685904]ak[/MENTION] did this by default or synapse settings is messed up.

The synapse explanation is quite clear as well on the matter :)

Sent From Lollipopified Bacon Goodness!

---------- Post added at 04:32 PM ---------- Previous post was at 04:27 PM ----------

I had no problem dirty flashing sabermod build over regular build, many others have done the same without issues.

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] ak:
Overclocked situations are related to mpd. You cant fully control min/max freqs.

Sent from my A0001
[ONE Android Development] Criton30:
I have speed 3 and pvs 9.
[ONE Android Development] Pipodi93:
Guys, do I need to convert the ROM to F2FS or I just flash it on a F2FS partition?
[ONE Android Development] :
+1 Also a extreme battery compsumition since 4.5
[ONE Android Development] 1ceb0x:
No issues here on latest SE + boeffla kernel SM. 20% dropped for 2 hours of SOT!

Pretty decent i must say!

Congratulations for everyone involved.
[ONE Android Development] ek69:
The per app mode was made by CM I read somewhere it is made to put phone in performance mode with some apps such as bench marks. Your PVS is higher than mine it should be able to take the higher speeds. Did you under volt by chance? Try making it stock speeds both idle speed and highest speed and then try again with stock voltages.

There is f2fs thread around here, go to that thread for info on f2fs things

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] ak:
These are normal stats for opo.

I have:

0.3 % hour with standard 4.7

0.5 % hour with sm 4.6

Sent from my A0001
[ONE Android Development] ek69:
What does this mean? Sorry i don't understand.

Upon initial startup after synapse clear data and dirty flash of ROM and kernel it was on default Qualcomm mpdecision and over clocked CPU frequency. Then I had to change it manually to msm mpdecision and set to normal frequency.

You mean since default setting is stock Qualcomm mpdecision then that is why the CPU frequency is over clocked by default?

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] ak:
Mpd don't respect min max freqs setted into scaling sysfs path

Sent from my A0001
[ONE Android Development] ek69:
Got it now thanks :)

I love this ROM and your kernel combo.

Most stable alpha/beta/whatever it is lol :)

I only wish I could have this ROM for my wife's nexus 5 lol. Maybe if I get an invite I'll just sell her nexus 5 hammerhead and get her a one plus one just cuz of this ROM and kernel combo :D

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] Negotiator50:
Same problem with the SM version 4.7 of this ROM as follows:

When I am on a phonecall and get another call, the current call goes silent and the other party cannot hear me. If I reject the second incoming call and hit the speaker button, everything goes back to normal. I have had this issue on every single CM12 ROM I have tried over the past month or so. However, its intermittent and happens about 60% of the time. I do not experience the issue on stock CM11s at all.

I did a clean install on stock kernal with updated modem. I have tried turning off reverse phone lookup to no avail.

I can't imagine that I am the only one with this issue as it happens on every cm12 ROM I have tried.

Please help.
[ONE Android Development] TheQuarterMile:
I think the Saber Mod version is consuming more battery than the normal version...

I'm also facing the problem where an incoming call makes the current call go silent. Have to put on the speaker to gain back audio.
[ONE Android Development] silvagroup:
Flashed 4.7sm and thought I was jsut lucky and some how evereted all the modem and prox sensor problems --- ha tha was just wishful thinking.

After flashing ROM also had to go back flash nightly modem from link in OP that seems to have partially worked, screen goes off when put phone to face but deosn't come back on when moved away ....???? Eventually, ferw seconds, of course seems like forever, screen comes back on, but thats really annoying.
[ONE Android Development] trax69:
Best audio settings? Lollyviper+ extremebeats :rolleyes:
[ONE Android Development] mervinj:
Wakelock Blocker

Sorry if this has been answered before but has the wakelock blocker been removed from the SE 4.6 version of the build ? I searched the settings but could not find it ?
[ONE Android Development] linezero:
so what's better in terms of battery life? the regular version of the sabermod version?
[ONE Android Development] azsl1326:
Yes. Recommended to use Privacy Guard in place of it.
[ONE Android Development] afrob:
Where can i find cm12 official?
[ONE Android Development] mervinj:
Thanks,I do use the privacy guard but how does that help in reducing wakelocks?
[ONE Android Development] Criton30:
I have nothing changed. stock ak kernel.....
[ONE Android Development] mervinj:
Incredible, are you using any specific settings in Boeffla's kernel and for the ROM as well
[ONE Android Development] smint86:
Remove “keep awake“ permission.
[ONE Android Development] prometheus1010:
http://lmgtfy.com/?q=cyanogenmod+oneplus+one+download
[ONE Android Development] Alin CG:
You can't do this with every wake lock

For example ..how do I stop this wakelocks ?
[ONE Android Development] smint86:
Believe me, you don't want to stop all wakelocks. The phone is intended to work like that, apps you use are using wakelocks. If you'd like to stop all, you won't be successful or it will cause misbehavior. You could not use gapps, then you'll have much less I believe. No google services and so on. But usability would suffer much. In the end it's your decision, but you just should not care that much about it. Wakelocks are normal.
[ONE Android Development] Alin CG:
know that and you are right ...but some of them must be stoped :D now i lose like 3-4% per hour with screen off ..... before i lost 1% every 5 hours ..... my opinion wakelock locker shoud be included and shoud be used by who needs it... like many other options in this rom .... i don't think you use every option of this rom ......but are included ....thx
[ONE Android Development] afrob:
what was the install guide?

Full wipe

cm12nightly

Temasek sm 4.7

gapps

modem

? Right?
[ONE Android Development] :
well tradiotionally wakelocks keep phone awake and yes some are functional, but most are annoying and definitely can be disabled without adverse effect, just google if it does.

I see it as bad programming if wakelocks are used. I dont want for a lot of apps/settings wakelocks. When one dissables it, and a program behavious badly, again bad programming. Google should make it a standard that wakelocks can be dissabled. Amazed it was slimroms and cm to first enable users without root to stop them
[ONE Android Development] Alin CG:
Thank you :D
[ONE Android Development] 1ceb0x:
zzzmoove governor, optimal profile.

268 mhz - 2.4 ghz cpu

deadline scheduler

read ahead 2MB

hotplug defauly profile

-50uV

force GPU rendering in developer options

my android tools app to disable some services, receivers and providers for Google play services and other pesky apps :).
[ONE Android Development] Alin CG:
then my battery must be broken ..because i get only 30 minuts ost per 10% with zzmove battery yank and 1.7 ghz cpu :D
[ONE Android Development] smint86:
Yeah, but [MENTION=2332422]temasek[/MENTION] decided to remove the option, for a good reason imho. It's causing problems, what several providers of his ROM realised, too. If you want it so bad, you'll have to build on your own or use an older version of this ROM (which I wouldn't recommend).

---------- Post added at 10:28 PM ---------- Previous post was at 10:27 PM ----------

You don't need the modem in the end if you flash the nightly, that's why you flash it ;).