yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] randallstevens:
MultiROM needs the kexec-hardboot patch applied to the kernel which isn't included in Sultan's kernel since keeping it clean is his priority, which is a good thing. Also, I believe this was added previously and later reverted since the kexec patch broke encryption support.

About the volume keys for skipping tracks, have you enabled the option in the buttons menu?
[ONE Original Android Development] tigobrata:
Just want to let everyone know, including [MENTION=4800121]Sultanxda[/MENTION] that using gravity box's proximity sensor accidental wake up prevention works, so for everyone who misses it, there it is, and sultan, you could take a look at the code, I guess :silly:
[ONE Original Android Development] shiniiigami:
Yes I have Tried disabling and enabling them again. Didn't work
[ONE Original Android Development] gronostaj:
Sometimes I have a weird problem: when I press the power button or double tap, the screen turns on, but touch doesn't work. I can't unlock the phone, pull down notification bar, etc. I have to turn screen off and then turn it on again and everything goes back to normal. It happens about twice a week, so it's not a major issue, but it's quite irritating. Stock ROM doesn't have this problem, but all Sultan's builds I have tried (Oct 27 - Nov 16) are affected. Is it a known issue? Do we have any fix?
[ONE Original Android Development] deepaklunked:
I too had it, but not only on Sultan's roms. I had it in many roms. It was very random, could not predict the cause.

Sent from my OmniBacon
[ONE Original Android Development] GForceXIII:
Yep, it also happens on my phone occasionally.

But I thought it was probably because of powernap?

Haven't tested with powernap off.
[ONE Original Android Development] mhulsegge:
I only have this issue with the top bar. I can't pull it down a lot of times, mostly after a reboot. After entering my pin and unlocking the phone, I need to wait for sometimes a few minutes before I enable the screen again and it works again. At those moments the entire top of the screen is completely unresponsive, which after that I don't have at all. Strange
[ONE Original Android Development] jim_bocho:
I have encountered the following bug:

When having played Spotify (Playback stopped) and start to make a call, Spotify starts playing again, but without showing up in the notification bar.

Similar things happen when I start a call over my in car bluetooth - when I start the call, Spotify stops, however it restarts when the it starts to ring.
[ONE Original Android Development] viralbug:
That's good stuff!

Can you please tell me which theme that is?
[ONE Original Android Development] tigobrata:
+1

---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------

Gravity box's proximity sensor setting works fine, use it instead
[ONE Original Android Development] Thracks:
Hi, [MENTION=4800121]Sultanxda[/MENTION]. I just wanted to say thank you.

For months I have struggled with outrageously high battery consumption on my OPO, in the range of 2-3% per hour idle and a paltry 2-3 hours of SOT. This was especially frustrating for me in light of the fact that CM12.1 nightlies from mid-2015 had given more like 5-6 hours of SOT and .2-.5% idle drain per hour.

I felt as though I'd tried everything with my recent battery woes: aggressive use of Amplify, Privacy Guard, disabling Google Location history, switching to location Battery Saving mode, underclocking, undervolting, cutting off cores. It was a gigantic hassle and I was beginning to get super pissed off at Android. I tried CM12.1 nightlies, Jgcaap's nightlies, Temasek's nightlies, multiple kernels and more. No matter what I tried, Android System kept gobbling up crazy amounts of battery regardless of whether or not I was on a fresh ROM or had loaded any apps. It wasn't wakelocks, either, as wakelock detector and Gsam were always clear. So was amplify. Nothing was obviously gobbling up battery.

But what I had never tried was a CAF ROM like yours. Your ROM + AK CAF kernel + the 11/7/2015 H2OS firmware/modem has changed everything. I'm back to <1% drain overnight, with 6-8 hours of SOT. I could not be happier.

Thank you.
[ONE Original Android Development] bucketheadmjs:
I am also experiencing a dead top quarter of the screen. It happens to me on reboot sometimes and I have to reboot to fix it. This reminds me of before CM released a fix for ghost touches and such.
[ONE Original Android Development] muleyman:
Running 11/16 build I'm seeing GPS issues for the first time. GPS has me jumping all over the map for some reason.
[ONE Original Android Development] idonttakedrugs:
How do you flash the modem?? I've tried searching but it made 0 sense to me ??
[ONE Original Android Development] prstorero:
Either with fastboot or just like flashing a ROM if you find it in a flashable zip format.
[ONE Original Android Development] Yvan12:
I'm on the 1101 build. I would want upgrade to 1116 build. I want keep all my data. I need to flash just the ZIP?
[ONE Original Android Development] kyrgeo1978:
Yes. Just the zip.
[ONE Original Android Development] Dr.Now:
....edit.
[ONE Original Android Development] 3ddfknmontana:
You repeated the same things like 100 times, double tap to wake up you like it eh?

---------- Post added at 10:30 PM ---------- Previous post was at 10:24 PM ----------

Whats the difference between the modem i have now and the h20s?
[ONE Original Android Development] sitong1991:
Thanks Got it!! Since I turn off the "Ambient display" then "the accidental wake up" is gone, at least better than before:o

---------- Post added at 01:31 AM ---------- Previous post was at 01:19 AM ----------

yes, double tap to wake up is very convenient and I also set double tap Home button to turn off the screen. What's more because I am not good at English so I will repeated the same things many times to express my idea. I am sorry if the repeats disturb you.
[ONE Original Android Development] Sultanxda:
What's your baseband version?
[ONE Original Android Development] hidequick:
Hey! using your rom and my calls just wont go through says dialing number then just hangs up I am on lte with full bars sometimes a call will go through after 4-6 attempts
[ONE Original Android Development] muleyman:
241

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

241

Should I be on something different?

On the other hand, my cellular reception has never been better.
[ONE Original Android Development] Tharun Gowd:
Mee too had same issue but I thought its network issue may be bcz of signal strength but now confirmed its ROM bug :(

---------- Post added at 03:07 AM ---------- Previous post was at 03:06 AM ----------

Mee too had same issue but I thought its network issue may be bcz of signal strength but now confirmed its ROM bug :(
[ONE Original Android Development] hidequick:
i had the problem before i flashed too the rom i have the kernel correct and everything
[ONE Original Android Development] megamonkey:
I just flashed the ROM and I can't find my photos...anyone can tell me where my camera pictures are? i don't see a "Gallery" button

Thanks

Nevermind, I have to use Google Photo...is there any other Gallery app anyone would suggest?
[ONE Original Android Development] Sultanxda:
241 is the correct version.

I guess we just can't have nice things :/
[ONE Original Android Development] easy_mac:
Quickpic is great

http://xdaforums.com/android/apps-games/app-quickpic-v4-5-2-classic-version-t3204543

Use the second apk (signaligned)
[ONE Original Android Development] teccrom:
Just posting to say Thank You so much for releasing and taking the effort for making this. I was ready to throw my OPO away and buy a new phone since it wasn't working well at all on the official roms, but this made me keep it still. The camera quality is as good now as it was with the original ColorOS rom.
[ONE Original Android Development] neisor:
Hi [MENTION=4800121]Sultanxda[/MENTION] ,

I am really having an annoyance here. I don't know why it is but when I flash your ROM I will get then a whiter and brighter strip around the display at around 0,5cm of distance from the edges of the display. I am not having this issue with any other ROM.

May it be because of the kernel and your rewritten touchscreen driver? It is not the yellow band/strip that the OnePlus Ones have, but it is really like the display itself is brighter around those edges. I tried to make a screenshot but it is not visible, since it is not how the content should be displayed, but it's something that it manipulating the screen itself, I suppose the kernel.

Is there a way to go over it or something?

Again I say, this problem I am experiencing only with your CAF builds (be it the 5.1.1 or even with the 6.0).

Thank you.

EDIT: Everything else works great. Even the touchscreen itself is very responsive. It's just that bright band around the edges.

EDIT 2: It looks like the bright light is coming from the edges? May it be like that? Still don't understand how come it is only with you CAF ROMs. I have been using RR, CM nightlies and stable releases, CyanogenOS, BlissPop and even OxygenOS; there wasn't such a problem on any of these ROMs. I tried to flash back another ROM to see if it really is not a HW issue. And it comes up that there is not any problem on them even if reflashing back one of them directly from yours (clean flash always). So it ain't a HW issue. It's something code-written.

Reverted back to CM12.1 until clarified :)
[ONE Original Android Development] m@++:
For what it's worth, the GPS changes in the latest build have made a HUGE improvement for me. I had a first fix time of 10 seconds last night! I've never seen my GPS get a lock on a cold start that quickly before. And the other cold start locks since installing the 11/16 build have all been under a minute, instead of the usual 130-400 seconds I usually experience. And my running path in Runkeeper looks no less accurate with the newest build, either. This is the best the GPS on my OPO has ever performed. Fo' realz.
[ONE Original Android Development] dadamanu:
[MENTION=237269]sultan[/MENTION] and guys

Hello , congratulations for the great job I have only one small problem ...

Some themes do not install .. are themes for cm12 but many do not go ... but first worked with COS 12 .. what can ' be ?

for esemple don't work : deep darkness, material glass, dark material, vault...
[ONE Original Android Development] Sultanxda:
Argh, do I favor those who get 400-second GPS locks or those get GPS data scattered all over the place?

MSB is something we're supposed to support by default (and enabling it is recommended by Qualcomm). I wonder where it's going wrong :confused:

Who manufactured your LCD?

If you don't know, reboot your phone twice, open a terminal emulator app, and run this command:

su -c "cat /proc/last_kmsg | grep Panel"

Note that capitalizing "panel" is important.
[ONE Original Android Development] NoSpamDan:
No problem here...
[ONE Original Android Development] paras33:
+1 to this... i face exact same thing... not a big issue but yes if i lv phone on autolock aftr 30sec it gets light dim screen n unresposive and had to wake with power..happens randomly...
[ONE Original Android Development] dadamanu:
What can I do to try to fix ? wipe cahe and davilk ? still install the rom ?
[ONE Original Android Development] neisor:
I ran this code in Local Terminal and it showed this:

mdss_dsi_panel_init: Panel Name = LG 1080p cmd mode dsi panel
[ONE Original Android Development] muleyman:
I re-flashed the rom and GPS works great.
[ONE Original Android Development] NoSpamDan:
That's a good start, yes. I wipe cache and dalvik on every dirty flash.
[ONE Original Android Development] 3ddfknmontana:
Piktures app is awesome
[ONE Original Android Development] mlord:
Just adding a data point here, mine works fine, and is:

mdss+dsi_panel_init: Panel Name = jdi 1080p cmd mode dsi panel
[ONE Original Android Development] neisor:
Okay, now I am getting a little bit confused... Why is mine made apparently by LG and yours by JDI, as it should be?

P.S.: My OnePlus One came out from fabric circa at the end of September 2015.

I did not hear about such a difference anywhere, this is really strange and weird.

[MENTION=4800121]Sultanxda[/MENTION] , is there a workaround for this problem? Thank you very much.
[ONE Original Android Development] shiniiigami:
Can u post the links to the files and the order u flashed them????
[ONE Original Android Development] GoldenBadger:
[MENTION=6794528]shiniiigami[/MENTION]

Here ist a list of modems, where to get new ones and how to flash them.

http://xdaforums.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
[ONE Original Android Development] mlord:
All I see at that link are out-of-date firmwares, though there may be newer ones hidden in the followup posts there.

Meanwhile, in

this

very thread, there are many posts which include links to the latest OPO firmwares. Eg. http://xdaforums.com/showpost.php?p=63078371&postcount=5531

I am currently using the latest 00013 HydrogenOS modem + firmware with Sultan's latest 12.1 ROM. Thus far, the best yet for me here!
[ONE Original Android Development] Tharun Gowd:
Hi Sultan

I am having about 5-10% of battery drain by the WhatsApp in the latest build and my mobile radio is active all time.

Previously i used to have only 1-2% of drain by WhatsApp.

Any workaround for this ?
[ONE Original Android Development] mhulsegge:
It's a known fact that various brands etc of displays have been used in the OPO.

So it's not as strange as you think.

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] neisor:
Ouch, that wasn't expected by me.

So, is there a solution for a different display? (Made by LG)
[ONE Original Android Development] somanshmittal:
OK Google Detection

I know I might get some bashing because of this, but still I'll ask this question.

So going by the instruction in the OP, I wiped my device clean (system, cache, data), installed the latest CM Nightly, wiped system, flashed the ROM and finally the GApps (TK GApps Micro Package) and SU to get root. ROM installed perfectly.

I want to use the OK Google functionality but it is not working even after training it! Is it disabled in this ROM? If not, is there a way I can get that functionality to work? I use my phone quite a bit while driving and need to use the feature quite often. Any help would be highly appreciated!
[ONE Original Android Development] BigBenlolz:
So I have a pretty complicated problem: when my alarm rings in the morning the phone totally locks up,black screen and white led blinking (probably not related).It goes on for about a minute then it soft reboots,but the led is still blinking without any notification so I have to reboot it again.Did something similar happen to someone else? I'm on the latest build,never had this before.It's pretty weird.
[ONE Original Android Development] satfly:
For me, GPS has gotten a lot worse on the Nov 16 ROM. It has been great for many releases in a row but after flashing the Nov 16 build, my phone is losing GPS-fix in Google Maps every couple of minutes during a long drive.

Edit: Reading Sultanxda's post from Nov 18, this might be caused by MSB being enabled since the Nov 16 build. Can I disable MSB myself? Is the setting in gps.conf?
[ONE Original Android Development] sdmark:
I had problems with my n5 - I think it's a lollipop bug that randomly affects random phones. There is a bug report page on Google but you know how that goes. For me I changed location to device only vs high accuracy and I stopped getting disconnects (on my opo too). Not sure if it's related or not but might be worth a try
[ONE Original Android Development] mongoosesRawesome:
Just wanted to add that GPS has been horrible for me too after Nov 16 build. Was considering doing a full wipe and clean install, or returning to Nov 1, but would appreciate other solutions. Going to try the "device only" location option mentioned by sdmark and report back, but would ideally like to be able to choose among the different modes.
[ONE Original Android Development] 3ddfknmontana:
The only problem i have with gps is that it takes about 30 seconds to locate me
[ONE Original Android Development] mongoosesRawesome:
Just a quick update - setting location to device only did not completely fix the problem. I still had my location jumping around for the entirety of my commute.
[ONE Original Android Development] Sultanxda:
I guess we really can't have nice things. I'll revert the GPS change in the next update.

There has to be a solution, but seeing as how I don't have an LG/Truly display, fixing it is very difficult for me (I could fix this within the hour if I had the device).

I can try shooting in the dark though. I never got far with working on it in the past because all of the users with an LG/Truly display so far had been very slow to respond (1 week or more per response), so I gave up.

Flash this kernel and see if the issue persists: View attachment Sultan-kernel-TRULY1_2015-11-20.zip
[ONE Original Android Development] m@++:
Oh, darn. :(

[MENTION=4238096]mongoosesRawesome[/MENTION] and [MENTION=764691]satfly[/MENTION] Would either of you be willing to try a re-flash/clean flash? [MENTION=3004837]muleyman[/MENTION] was the first and only other user to report GPS issues in this thread with the 11/16 build, and he stated that a re-flash of 11/16 fixed his GPS.
[ONE Original Android Development] Ejvyas:
Can you clear data on your maps app and uninstall reinstall your maps app and try again?

That fixed my gps from jumping around

I have compiled some other things that worked for others

http://ejvyas.blogspot.com/2015/10/one-plus-one-bacon-gps-fix.html?m=1

PS. I'm on temasek
[ONE Original Android Development] rob77:
GPS works fine for me also on the latest build. The only thing I have found is that sometimes using Maps navigation it takes a couple of minutes to get a lock. After that though it works fine. I have recently come back to this build from sultan's marshmallow as I was finding GPS on that would loose lock frequently.
[ONE Original Android Development] :
I ran into couple of issues after applying theme. Theme was Euphoria dark by blaze (Theme was working fine with other roms tho)

1. Navigation Bar changes to stock after rebooting. (I tried with another Rom it works fine)

2. Navigation bar glitch where i cannot use the navigation buttons at all in Landscape Mode. (This issue happened 2-3 builds back too)
[ONE Original Android Development] neisor:
I understand. I am here almost always since I have mobile data snd can respond at any time. I am willing to help you with fixing the LG panel issue. You have my support with it and am willing even to be a tester of the fixes.

I am now going to try this kernel. Will report in edit of this post.

EDIT: Okay, so far it looks good, no problem. Fresh installed your CM12.1 + this kernel.

Does it work even with the CM13?

+ Can you post in the OP the direct download link for this fix + write a changelog comparing to the classic kernel that comes with the ROM directly? (Just to ease a things up a bit for future)

Thank you.

EDIT 2: Now after a few minutes it's there again. So

not fixed

:(

EDIT 3: It's interesting... It seems like it is switching from a bad to good view experience by itself. Hmm. So it is good for a moment, then again bad for a moment.. and it repeats.
[ONE Original Android Development] Sultanxda:
Round 2: View attachment Sultan-kernel-TRULY22_2015-11-21.zip
[ONE Original Android Development] neisor:
Dirty flashed this one right now. It's still there, but those edges are less bright than before (at least for now). But it's there.

So, still not fixed. :(

Thank you.
[ONE Original Android Development] Sultanxda:
Round 3: View attachment Sultan-kernel-TRULY333_2015-11-21.zip
[ONE Original Android Development] neisor:
Ouch. When locking and then unlocking display it will only show a blank black screen. The kernel from round 2 didn't have such a bug with that blank black screen.

not fixed + bug
[ONE Original Android Development] Sultanxda:
Round 4: View attachment Sultan-kernel-TRULY444_2015-11-21.zip

Round 5: View attachment Sultan-kernel-TRULY555_2015-11-21.zip
[ONE Original Android Development] Stamatis.X:
Im having the same problem and round 4 and 5 didnt work for me. The problem still persists
[ONE Original Android Development] neisor:
In the round 4 version I experienced the blank black screen issue (occassionaly).

Now I am using round 5 and after the intial boot up it looks good. Will report if I'll find something, but maybe yes, since the user above me is experiencing issues even with the round 5 kernel.

EDIT: No improvement.. Not fixed :(

Round 5 kernel build did not fix that either. But the blank black screen is gone..
[ONE Original Android Development] rob77:
I am now getting a gps fix within a few seconds on the latest build. I installed an app off of the play store called GPS status test and fix. I fired it up and waited until I had fix. Pressed reset the GPS and then pressed get xtra data. I believe this is the same as agps which other apps call it.
[ONE Original Android Development] mongoosesRawesome:
I'll give these things a try. I should mention that my GPS has always been a bit finicky, unlike my wife's OPO GPS, but on this ROM it's been pretty good after setting a close NTP server and updating AGPS
[ONE Original Android Development] Ejvyas:
I listed that on my link :)

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

Can you please point me to the GPS fix commit?
[ONE Original Android Development] scedeov:
I just logged in to say that I'm having the best battery performance on this last build (16/11). My GPS locks quite quickly. The ROM is great. Luckily I haven't experienced any of the issues here. WiFi works like a charm, phone goes smoothly and the audio on calls is great. I'm thinking on not updating my phone in a while. I will just stay on 16/11.
[ONE Original Android Development] AL2000EX:
On the latest couple of builds 3g is very inconsistent. It shows good signal but it looses network a LOT. 2g works fine tho. I'm using hydrogen os modem
[ONE Original Android Development] superbrowndude:
No GPS or wifi problems. LTE and 5ghz work flawlessly, battery life is awesome. Absolutely no issues what so ever!

Boosted 1+1
[ONE Original Android Development] somanshmittal:
Help Needed!

Can anyone please help me on this? Also, my phone now switches off at 15% battery! I get the lo battery notification and the phone switches off! Anyone else facing this?
[ONE Original Android Development] atulclassic:
not able to restore apps through TB

deleted
[ONE Original Android Development] lokesh.3440:
Music gestures doesn't seems to be working for me. I clean flashed recently and I m on stock kernel. Although it's a minor issue as battery life and performance has been awesome. Can anybody confirm whether it's working ?
[ONE Original Android Development] rahulbhasme:
ew
[ONE Original Android Development] lammpat:
Battery charging is too slow, switched off phone and put on charging when 53% ,after 90 minute it charged upto 89%. Never faced such issue on Cyanogen Stock. Anybody else? I am on latest build.
[ONE Original Android Development] uriii13:
Me too...
[ONE Original Android Development] 3ddfknmontana:
Get Ak kernel CAF, you can boost your charging mA, are you using all original wiring and wall plug.?
[ONE Original Android Development] lammpat:
Forgot to mention that I am already on ak caf..checked current of home,all ok around 220 volt..yes all original wiring and wall plug...dont want to play with the kernel voltage settings.

Edit.. checked with synapse,current level is 1200ma and usb fast charge is disabled... can't understand that sometimes it charges like rocket with the same settings, sometimes become too slow.
[ONE Original Android Development] AdrianM:
Well, if you are using a custom kernel, don't come here and complain.

For me, with stock kernel, while the screen is on, the phone draws 1,2A, and with the screen off it draws 2,1A, the maximum that my samsung charger can give. So charging is not slow.