yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Killer.shubham:
Pictures comes out to be dark, that was not the case in previous builds, I did flashed underclocking removing zip this time. Sep 10 build
[ONE Original Android Development] Zalbu:
My phone's still chugging along for now, but speaking of audio, I get a loud buzzing noise about a second after starting a song on Spotify, any idea what that could be? It's not happening in any other apps so could it be a problem with Spotify?
[ONE Original Android Development] Killer.shubham:
Yea actually it works well, I had some cheap earphones without mic as soon as I connected volume was going down on its own. Now everything is fine.
[ONE Original Android Development] AbhishekS:
Downloading this ROM now. By the looks of it, it seems to be an 'awesomer' version of the already awesome Cyanogen. :D
[ONE Original Android Development] techrack:
When I am on a phone call, suddenly the device will just switch off. I have to hold the power button for 20 seconds and the device powers on again. I am on the latest stable version which I updated to this morning over the previous stable version. I have root and xposed, can you help me?
[ONE Original Android Development] Xenocide23:
This has happened to me as well on the older 9/6 builds in addition to having the network drop for hours at a time according to the battery stats. I'm hoping the new 9/10 build with a different modem cleans up these issues for me.
[ONE Original Android Development] mikecantreed:
Would someone mind directing me towards the modem used in the Sept 6 build? I want to flash 9/10 but a little nervous about 44S signal drops.

Thanks!
[ONE Original Android Development] Suarezian:
Is there any way I can increase the intensity/brightness of the notification LED?
[ONE Original Android Development] sneakerspark:
Why would there be any signal drop?
[ONE Original Android Development] mikecantreed:
I saw Sultan saying he had some initial issues with it plus 2 or 3 other people were experiencing suboptimal signal. If you could just let me know what modem was included prior to 44S I can find it.
[ONE Original Android Development] bashar.abu.diak:
[MENTION=4800121]Sultanxda[/MENTION]

I also have problem with charging its too long time to charge even when the phone is closed, I don't face this problem with the previous version, I made a clean flash using twrp 2.8.6.1, and I use original charger and cable
[ONE Original Android Development] CNDow:
The newer versions do not flash the firmware on our device. You can downgrade with flashify from the play store to 2.8.6.0

---------- Post added at 10:21 AM ---------- Previous post was at 10:18 AM ----------

You cannot flash a different modem it is baked in. Give it a try & if you have issues flash the previous ROM
[ONE Original Android Development] zBear:
I have no problems with 2.8.7.0.3 from ketut.kumajaya

http://xdaforums.com/oneplus-one/development/unofficial-twrp-2-8-3-0-t2981495
[ONE Original Android Development] 1ceb0x:
Yes you can flash a different modem AFTER you installed this rom (provided you have a different modem zip that you can try).
[ONE Original Android Development] Galactus:
Yep would be a brilliant idea. It is fine in the August 28th build. September builds all have the problem

Because you are using MaxxAudio. Going to have to remove it for now.

Format /system, reflash ROM, Gapps and any other mods apart from MaxxAudio.
[ONE Original Android Development] techrack:
Yeah the exact same thing is happening to me and I'm on the 9/10 build. I hope it's fixed soon because I'll have to go back to COS12.1 if it isn't and I really like SultanROM?
[ONE Original Android Development] AbhishekS:
Even I am experiencing the same bug where the phone just shuts off during a call. Coincidentally all thrice occurrences have been during incoming calls.
[ONE Original Android Development] techrack:
Happens on both incoming and outgoing calls for me
[ONE Original Android Development] Phoenix Wright:
He can't do that because MaxxAudio is closed source, they just licensed it to Cyanogenmod for COS... I tried copying only the needed files (AudioFX apk, the few extra libraries in /system/vendor/lib and the audio effect configuration files) from latest COS and the buzzing is there. The weird part is that it only happens with Spotify. CM Eleven and Play Music are fine. I'd guess we'll have to wait for the next COS update to have updated libraries.
[ONE Original Android Development] mikecantreed:
What build are you guys on?
[ONE Original Android Development] techrack:
I'm on the latest, 9/10.
[ONE Original Android Development] mikecantreed:
Is the issue that the phone reboots or that it drops the call?
[ONE Original Android Development] Zalbu:
Yeah, assumed that was the problem. Uninstalling it helped, but can I flash a non-MaxxAudio version of AudioFX?
[ONE Original Android Development] CNDow:
I think a modem zip is a conventional means
[ONE Original Android Development] Galactus:
Of course :), reflash the ROM
[ONE Original Android Development] techrack:
Well the phone reboots and naturally that drops the call
[ONE Original Android Development] Zalbu:
Dirty flashing doesn't restore it, I have to find a flashable Zip.
[ONE Original Android Development] Galactus:
Going to have to format /system, can't be a dirty flash
[ONE Original Android Development] Mayex:
I have random reboots every 10min-3hours. It happens after update to sep06 and sep10. How can I provide you logs? Probably my fault, too ristrict Amplify.
[ONE Original Android Development] CounterC:
Invalid link
[ONE Original Android Development] Galactus:
Invalid link since there is a new version now (v73 to v74)

[OFFICIAL] Xposed for Lollipop

http://xdaforums.com/attachment.php?attachmentid=3469283&d=1441910102
[ONE Original Android Development] joefso:
[MENTION=4800121]Sultanxda[/MENTION] - I am experiencing no signal with the latest release ( OTA update ). If you need any testers I am available ...
[ONE Original Android Development] jkmangang:
I felt hotter in the surroundings of camera while playing videos. I never felt like this in the previous versions.
[MENTION=4800121]Sultanxda[/MENTION]
[ONE Original Android Development] CounterC:
Have you tested this?
[ONE Original Android Development] Cesaragus:
It just doesn't work. I don't know if I'm doing it right. I flash the zip in TWRP and then install the Xposed Installer. It says it is active. Then I install anything that requires xposed to work and none of it works. Do I have to flash something else? Do I have to flash makepermissive.zip or something? The thing is it doesn't ask for root permissions.

I don't know.
[ONE Original Android Development] Galactus:
Yep, for some reason, with all of these newer Xposed builds I have to format /system otherwise the phone stays on the boot logo for ever. But yeah, it works.
[ONE Original Android Development] hawkwind:
This is a great build thanks, I'm not having any of the problems that others are reporting everything has been perfect all day.

Just charged the phone as well and it's so much faster than cos 12.1 was for me, I couldn't be any happier thanks
[ONE Original Android Development] Galactus:
Might have to start from scratch.

format /system,

reflash ROM, GAPPS and Xposed zip in one go.

Install the apk

install modules, make sure they are ticked in the xposed app

reboot.

It won't ask for root.
[ONE Original Android Development] sneakerspark:
Give it a try. He added it for a reason. I am having no such issues
[ONE Original Android Development] TwoXfour:
New version with changed modem presents some odd behaviour, in areas of weak signal (that normally don't present any problem) signal indicator goes from 30% to no signal to 30% repeatedly quite fast and fails any data connections.

In good signal areas, I occasionally get the ! until I reboot.

I've also seen 2G come up as a connection indicator which is very unusual, as my carrier (Three UK) doesn't run any 2G towers.

Restored backup to prev build for usability. Will try and test again this weekend to provide logs.
[ONE Original Android Development] Tymp:
Thanks, I will try with this app and see what it says.

---------- Post added at 11:32 PM ---------- Previous post was at 11:22 PM ----------

Thanks for the reply! It used to take 1h and a half with cm12.1 nightlies to get a full charge, (original cable and charger) . Now it takes more than 2 hours. I also noticed that if I use a 1amp charger, the lightning symbol on the battery icon appears intermittently, and the charging time takes forever. Maybe something went wrong when I flashed the rom, even if I did a factory reset...
[ONE Original Android Development] NOSTALGIA:
lightning appears intermittently?? possible defective cable
[ONE Original Android Development] legolas93:
Me too. No reboots, freezes, black screens etc..

Clean flashed without Xposed or any other mod/theme/tweak/stupidthing.

Phone runs great without problems and doesn't heat up.

Even the new (or it's better to say old..) modem seems good.

Network switch seems faster and reception is ok and solid. :)
[ONE Original Android Development] Tymp:
Nope, the cable is fine. Used it without problems with other roms. The lighting symbol is intermittent, while the cirlce keeps rotating. This means that charging does not stop, but at it goes on at lower amperage. It isnlike when you connect the phone to a laptop usb port of 0.5amp: no lighting symbol, but still the circle keeps moving...
[ONE Original Android Development] Cesaragus:
It is not working. I did that a hundred times, but it doesn't do anything at all. It is like it is not installed, but Xposed Installer shows that is installed and active, and it lets me install modules and all that. The thing is any module that I install is not working. It just doesn't work. Should I install SuperSu or something? I have no idea o what's going on.
[ONE Original Android Development] shail139:
Hi, I m new to Bacon and flashed this latest stable last night and my device is not going to deep sleep and it was wakeup while time during idle .

Any suggestion or known issue
[ONE Original Android Development] Knox316:
Sultan CM CAF + AK Caf + Xposed
[ONE Original Android Development] novren:
Anyone?
[ONE Original Android Development] Amanpreet Wadhwa:
Kernel settings? Have you applied any synapse profiles? Amplify, greenify?
[ONE Original Android Development] Sultanxda:
44S modem seems to be a bust for most people, and I forgot to add 2 modem-related firmware images (mba) from the 44S modem partition (this is what caused some random reboots), but those aren't related to some of the other issues people are experiencing (i.e. no signal at all). I've been happy with having signal for the first time in the chem wing at school (using the 44S modem), but that isn't as important as stability (though it has been working fine for me). I won't do the RIL dance and try to make the 44S RIL work with Lollipop. I'll abuse the 230 Lollipop modem for maybe 10 minutes and may or may not put that into the next build (which will probably come today since I finished all my homework in the library, and since the 44S modem is exploding).
[ONE Original Android Development] CNDow:
I’ll be driving home through rural Central Valley CA & check the 44s modem. There is always spot where I lose signal & coincidently where I usually get a phone call.
[ONE Original Android Development] sneakerspark:
How do you turn off the WiFi completely? Whenever i turn it off, battery stats still show that it's on.
[ONE Original Android Development] renaltosonylevi:
I have actually noticed that with the 44s modem I am not getting constant voice mail notifications like I normally do in marginal signal area's which is sweet relief because I never use that service.

Also have had no reboots so far or any other issues that people complain of.

I don't know if there is a link but I am not using xposed or themes or any add or wakelock blockers etc at the moment.
[ONE Original Android Development] auerbach:
This is really my favourite ROM

Great battery life and performance with 6/9 build

I think I'll keep with it

Idle drain is pretty good
[ONE Original Android Development] SubNoizey:
[MENTION=4800121]Sultanxda[/MENTION] in your honest opinion which version should we be using? Your nightlies or stable? It seems like since you're running stable that would be the way to go as it will likely get the most attention?
[ONE Original Android Development] auerbach:
Woww

Same question and what apps do u have
[ONE Original Android Development] dcoulombe:
Good job, [MENTION=4800121]Sultanxda[/MENTION], tonight I didn't get any soft reboot. It was probably related to those commits from CM that was mentioned earlier.

:good:
[ONE Original Android Development] deepaklunked:
He won't be working on Nightlies anymore. So, its the stable version you should be running.
[ONE Original Android Development] Dukejester:
I will try again tonight. Thank you very much.
[ONE Original Android Development] Sultanxda:
New build uploaded with the Lollipop modem back, as well as a couple of other random fixes.
[ONE Original Android Development] mikecantreed:
I don't really know what the difference is between the lollipop modem and 44S but if I'm not having any signal issues or having any reboots would you say I'm better off on the 9/10 build?
[ONE Original Android Development] renaltosonylevi:
Now on the 9/11 build. Ever since the 9/9 build have not been getting voice mail notifications. What ever you have done.... don't fix it!!!!:thumbup:

Never used that @$$%* service. %#@%¥¢ waste of time. But hey work pays the phone bills.:D

All it ever told me was that the signal was fading in and out.:mad:
[ONE Original Android Development] Sultanxda:
I don't think you are. There are definitely random reboots with 9/10 because some of the 44S modem firmware is missing (I forgot to update the mba images from the 44S package).
[ONE Original Android Development] CounterC:
What version of xposed?
[ONE Original Android Development] Aniket.t20:
Could you make a flashable zip with only the 44S modem ? So that we can take advantage of all the changes you made to the wifi config too.
[ONE Original Android Development] redline2097:
Messaging crashes when trying to open. When using alternate sms app, i can send sms's but don't receive. Whats going on?
[ONE Original Android Development] satfly:
Thanks, my 3G data transfer speeds are about 4x faster on the Lollipop modem than on the 44S so I'm happy.

On another note, after flashing this latest build, my GPS behaved perfectly on my entire 45 minute drive this morning. No loss of fix at all.
[ONE Original Android Development] Quasar:
Yaaay CAF kernel! I agree with [MENTION=5284595]Qrze[/MENTION]. You deserve a cookie!
[ONE Original Android Development] nazfalas:
Yeah that's ok, it's another known issue. I would prefer that to the two finger x-axis problem and delayed input (yeah that happens simultaneously) any day.
[ONE Original Android Development] vindows18:
can i get a link to download kernel only?
[ONE Original Android Development] Quasar:
I don't know if the kernel would work on any other ROM...
[ONE Original Android Development] malavan:
You hade me on myfluxi thanks for this rom
[ONE Original Android Development] feed3:
Exactly what I'm looking for.. Thanks!

Dirty flashing on top of cm nightly 28/05 with no issue but now I'm on clean flash just to start fresh.

Just one request if i may; underclocked CPU max freq to be optional instead of by default.

Once again, many many thanks.

P/S: I've pressed the thanks button too. :D
[ONE Original Android Development] malavan:
Do we need gapps with this rom if yes wich one do you recommend
[ONE Original Android Development] nazfalas:
For a mini gapps package I can recommend Slim gapps:

http://www.slimdevs.com/Gapps/Lollipop/5.1/

For a modular package use Delta gapps:

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Edit:

Btw, no touch issues yet. These would have manifested themselves several times already on a warm day like today on the old firmware. Fast typing and even swiping was unbearably inaccurate and suffered from ghost touches - working fine. Seems pretty good to me.
[ONE Original Android Development] Sultanxda:
The kernel won't work on any other ROM, which is why I didn't upload a separate package for the kernel.

I'm not opposed to adding back the higher frequencies, but if I never forced it then nobody would even consider underclocking, even though it has many benefits. I'll add back the higher frequencies but I'll keep the default max freq at 1958MHz.
[ONE Original Android Development] black.ic3:
Gonna try it out. But why you cant keep 2457 available and boot by default on 1958? It's a perfect compromise
[ONE Original Android Development] Babyhustle:
Wow, thanks SultanXda

Had been using your ROMs since sensation :)

It's good to see another great developer to start development on the bacon :D
[ONE Original Android Development] tombassi:
great rom, my suggestion is to leave the default kernel forced to 1958MHZ which is very cool and post separate kernel with all values available or even overclocked
[ONE Original Android Development] RenderBroken:
[MENTION=4800121]Sultanxda[/MENTION]

Great job! Really interested in the specifics of how you got this to work. That's the part of kernel development that I am wanting to learn. Being able to take CAF and make it work for CM or any rom for that matter. How do you know what blobs you need and such. Those are things I am interested in finding out. Thanks for your hard work, it is appreciated.
[ONE Original Android Development] Aka91:
i did a dirty flash finally.hope it works.fingers crossed. :)
[ONE Original Android Development] PhillyFlyer:
I am sorry if you're repeating yourself. I just can't seem to grasp the installation process - from what I read the process is to be on the latest CM12.1 nightly (5-28) and flash "over" it with your build. Does that imply it should be a simple/dirty flash of your ROM? Or a full wipe/flash over the CM 12.1 nightly?

Sorry/thanks! Excited to try.:confused:
[ONE Original Android Development] 69gm:
You can either clean flash OR dirty flash over CM 12.1 nightly. This is especially important if coming from CM 12. The latest CM 12.1 nightlies have an updated firmware which is required.
[ONE Original Android Development] PhillyFlyer:
Welp! Thanks! I am on the 5/28 CM12.1 Nightly, so looks like I will make a backup then dirty flash this gem over top of the Nightly.

Thanks!
[ONE Original Android Development] BitEE:
Alright I'm definitely flashing this, let's see if my issue with silver bullet microphone when screen is on is fixed with these clean caf **** https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/BACON-3699
[ONE Original Android Development] 69gm:
Good choice! Yes, I always make a nandroid as a safety net. After that you can dirty flash. And don't forget to wipe cache and dalvik!

---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------

Yes please report back your experience! Sultanxda is always hoping to improve his builds so constructive feedback is always welcome. And please include logcat so he see what went wrong if something does.

---------- Post added at 09:24 AM ---------- Previous post was at 09:19 AM ----------

May I also suggest the TK Gapps. It is the new PA Gapps for those familiar with it.
[ONE Original Android Development] nazfalas:
Hey thanks for that link! Didn't get the news that PA gapps was being continued/revived. In that case there's no doubt which package to choose. PA gapps successor all the way.
[ONE Original Android Development] renaltosonylevi:
Sometimes it's hard to let go of old habits.:confused:

In the old days of my lg g2 with poor thermal design and less than average CPU binning undervolting was that phones saviour. I wasn't worried power consumption. Heat throttling was the big issue and the improvement was noticeable.

But with my one plus one and slightly lucky CPU binning I feel little urge to spend much time fafing around with that.

And I suppose as developer the last thing you want is people undervolting their phones unstable and complaining of reboots while you are trying to work out real bugs.:mad:
[ONE Original Android Development] gondsman:
I have to disagree on this. It is totally true that getting undervolting wrong (i.e. too much) leads to reboots/crashes and I can understand you don't want to deal with people getting unstable systems because of their own faults. However, undervolting does have a noticeable effect on the CPU power consumption.

On a (very) rough approximation, the power consumption of a chip is proportional to the clock frequency times the voltage squared. At very low cpu frequencies the cpu runs at very low voltages, so any undervolt you can manage to do has a fairly important impact on the power consumption. To give an idea, if you can go from 0.75 to 0.7 (a -50mV undervolt, which is totally stable on my phone) at the lowest speed, you will have a reduction of dynamic power consumption of ~13% while the phone is idle, which is definitely noticeable. Static power is more complicated to calculate, but it usually has the same squared voltage term in it.

Now, there are clock gating techniques and other fancy things in a moder cpu, so the gain might be a bit lower, but the principle is still the same.

If you still don't want to implement it, it's ok, of course we can live without it and the ROM is still awesome. I just wanted to do some fact checking as I design microchips for a living. :)
[ONE Original Android Development] Lugke:
Lets say we have a power consumtion of 10 mA while being in idle mode and 8 mA while in idle and airplane mode.

So we have approximately a consumtion of 8 mA in idle caused by cpu, board, sensors and so on... lets even pretend its all consumed by the cpu...

If you reduce now the consumtion at about 13 %, you get 6-7 mA.

additionally YOU get it stable at an undervolted state. but you cannot tell this for all, the possible problems for other users can be numerous.

Chances are good that this could be true for many even most, but noone can be sure, so its really better to stay with the preset currents.

One reboot because of an error caused by undervolting destroys the whole calculation and in the end, we have less runtime.
[ONE Original Android Development] Sultanxda:
In actual practice though, the AP will spend most of its time power collapsed, and then there are other fancy features you mentioned such as clock gating and other idle modes that reduce power consumption even more. It might've been a while ago, but at some point I read a post by someone on detailed battery consumption undervolted vs. not undervolted. The poster found that, in the end, there was no significant difference in his day-to-day battery consumption while undervolted, so the undervolt didn't benefit him in that regard. I don't think you would get much more screen-on time out of this.

That and I don't want to deal with the false bug reports :p
[ONE Original Android Development] gondsman:
Well, that boils down to CPUs being so power efficient that other parts of the system use more power (radios/display, mainly). I was just trying to say that, for the CPU itself, undervolting will save a good amount of power. On the grand scale of the whole phone, I can understand if the difference is minimal (I don't really have data on this).
[ONE Original Android Development] ImmortAlex:
Actually, CPU binning can be treated as "factory undervolting", and I don't think that what is left for users can have meaningful effect.

It's like AMD chips at the Pentium I/II era - they were cheeper at same speed, but can't be overclocked at all, just because they were "factory overclocked".

I played enough with undervolting when owned Xperia Ray with Snapdragon S2, but AFAIR there was no binning on that chip, so we have lot of room to play.

I strongly advice Sultanxda not to put any hack abilities to his ROM and kernel. We have enough of such kernels already, where you never know who is failed again: you, commiter, compiler or Jesus Christ...