yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] spanish33:
Worked after I flashed new modem found in slimsaber thread http://xdaforums.com/oneplus-one/development/rom-slimsaber-bacon-t2858033/page293

Modem http://www.mediafire.com/download/90h319tcas40n8c/OPO_L5_alpha-modem-flashable.zip
[ONE Original Android Development] deltatux:
Has this modem been modified in any way? What's different about this and the modem from CyanogenMod 11S XNPH44S?

Also, for everyone: I got 2 OnePlus One invites up for grabs, PM me for them. They expire within a day.

Cheers,

deltatux
[ONE Original Android Development] spanish33:
No the modem doesn't look like it was modified in any way because the md5 checksum is the same as the modem from oneplus one lollipop alpha rom https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha-preview.223252/. I dont know what is the difference compared to the modem from CyanogenMod 11S XNPH44S but the new modem looks like it is for lollipop roms only.
[ONE Original Android Development] deltatux:
Sounds good, thanks for the info. Just didn't want to flash something that I don't know where it came from.

Also, is it me or the new radio's baseband version is broken? Can others confirm?

Cheers,

deltatux
[ONE Original Android Development] chikimonke:
Confirmed, flashing the alpha modem fixes the prox sensor [MENTION=4911350]RobbieL811[/MENTION] , I was previously on the 11-28 nightly modem.
[ONE Original Android Development] kevace1:
This rom has been my DD for about 13 days now and it ha been great, other then the known bugs of sometimes the wake up hesitates to where it just lights up the hardware keys, but stays black, this happens more if you try to wake the phone after you recently pressed the power button though.....

I just would like to know, how can we put in the audio fx app on to this app? if there is one thing I do miss of stock is the audio fx app as it reproduced music muuuuch better then DSP app. Music sounded much more detailed and bass came out cleaner...I use a set of Dr Dre beats headphones and I definitely tell the difference....can we just flash the audioFx app somehow or does it have to be baked into the ROM with some libs? Or is a CM11s exclusive or just a CM exclusive?
[ONE Original Android Development] Ankru:
It is inside!
[ONE Original Android Development] Ankru:
Here you are
[ONE Original Android Development] kevace1:
Where is it? Its not in my app list. I just see DSP
[ONE Original Android Development] SushiR:
But how can flashing a modem fix the proximity sensor? I'm confused... [emoji15]
[ONE Original Android Development] chikimonke:
When is the last time you flashed? AudioFX has been included for a few builds now. Look back a couple pages and grab the latest build from Robbie.

---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------

A very good question that I don't have an answer for...
[ONE Original Android Development] SushiR:
I can indeed report that proximity sensor is working again after flashing that modem. ?
[ONE Original Android Development] deltatux:
You both aren't on the same page lol. [MENTION=1657870]kevace1[/MENTION] is likely still on Android 4.4.4 SlimKat whereas AudioFX is only in the Android 5 builds.

deltatux
[ONE Original Android Development] vprasinos:
I flashed AK kernel to try it out on Stable 9 but then I wanted to revert back to the stock stable 9 slimkat. So what I did was to dirty flash stable 9 with Slim_mini_gapps.4.4.4.build.8.x-385 and could not connect to play store because Google Play Services was missing. I had to factory reset to get things working again (thank god for that Titanium backup).

So is there a flashable kernel anywhere for the stable 9 or what did i do wrong?
[ONE Original Android Development] indian84:
Just dirty flashing the ROM should have been enough. No need to flash GAPPS..
[ONE Original Android Development] Natakranta:
You used old gapps with outdated Play Store and Google Play Services.

Next time for KitKat ROM use least KitKat gapps made by Dan: here link

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] Natakranta:
I see the same baseband version number for the OPO alpha LP radio I've just flashed.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] vprasinos:
Is it safe to flash Dan's gapps over the old gapps right now? Should I clean cache/dalvic or anything else?
[ONE Original Android Development] kantjer:
Baseband version number listed is always the same regardless of the version flashed.

It all comes down to a good memory and remember which modem you flashed last ;)
[ONE Original Android Development] Natakranta:
I'd do a semi dirty flash. Wipe these 3: cache, system, dalvik. Flash SlimKat 9. Flash Slim gapps Dec.29 from Dan's Basketbuild I linked. Reboot. Profit ;)

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] JaylanPHNX:
I flashed the new modem and ended up with no signal and com.android.phone has stopped messages. I reflashed the ROM, downloaded and flashed the modem again, neither helped. I had to flash back to the 44s radio. I hope this new one isn't required going forward, or I may be a screwed.
[ONE Original Android Development] Natakranta:
Maybe you had bad download? Does it match?:

MD5

f1fa99745035deb6d99bd856a196efba

SHA1

63d89ec5dd74c001756b72e2f77b9c676c32fffa

I flashed new OPO alpha LP modern successfully and it works fine. I've read today here and in SlimSaber thread few people flashing it and no problems.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] JaylanPHNX:
MD5 matches perfectly. Anyone have any idea why my phone wouldn't like the new modem?

It's baconnn!
[ONE Original Android Development] chikimonke:
Which build are you running? I believe the alpha modem is only compatible with roms that have the latest commit or 2 from CM. Basically, if your prox sensor is working, don't flash the alpha modem, if it's not working, do flash it. Also, this modem is ONLY for LP, not KK.
[ONE Original Android Development] Natakranta:
New OPO alpha LP modem works fine for me on latest SlimSaber LP.

I still need to flash Robbie's latest build.

Let's boot now my SlimKat 9 and see.

I'll report back.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] chikimonke:
If I understand correctly, the post from a few pages back that gave the initial suggestion, it was in the SlimSaber thread that this incompatibility/compatibility was first found.
[ONE Original Android Development] kevace1:
Yes you are right, I have been on stable 9 for a while. I have not researched the 5.0 slim since I hear many different builds have issues.....but if 5.0 has audiofx I will try then....... I m assuming a clean flash is necessary since its jumping android versions?
[ONE Original Android Development] chikimonke:
Certainly recommended [emoji2]
[ONE Original Android Development] Natakranta:
Correct.

Booted now SlimKat 9 (my primary on MultiROM, but hardly used nowadays). All works fine with the OPO alpha LP modern (I haven't test a call yet, but speed test is running ok) apart of when I switch off screen. Then SOD. Or I thought so. First time I rebooted. Second time I managed to switch screen back on with power button after some time. I'll test more.

I'm afraid it's the end of SlimKat for me on MultiROM. Otherwise I'd have to flash appropriate modem each time I boot from SlimLP to SlimKat or back.

Conclusions:

SlimKat and SlimLP up to Dec.29 build - use CM44S radio. SlimLP Jan.04 - use new OPO alpha LP radio.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] kantjer:
So the SOD's I was having on the latest LP with the old modem are also present on KK with the new modem.

I feel your pressure to keep offering dark ui builds then :D
[ONE Original Android Development] Nucleonic:
There have been a lot of discussions both in this thread and the CM12 daily thread regarding the radio. To be honest, I really haven't paid it much attention since I haven't been having any issues. I've been building straight from the github. Are the OPO alpha radios already included in the repo?

Here is a pic of my baseband version. Just built the ROM last night:
[ONE Original Android Development] Natakranta:
You are reading my mind :D

Otherwise I'd have to finally make friends with github and start doing it myself. Christmas=family period is over. Year end at work will be over soon, so I might find some time to learn it.

On a side note, these are not total SODs. I managed to turn screen on once, but I couldn't repeat it and had to long press power button to hard reboot. But the time screen was off notification came and led was blinking so the phone was on, just the screen didn't want to turn on.

SlimKat. Time to say good-by :(

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.

---------- Post added at 03:01 PM ---------- Previous post was at 02:50 PM ----------

I don't remember the number I had for CM44S radio, but that's what I see after flashing OPO alpha LP radio:

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] kantjer:
Bit OT, but thought you might find it interesting
[ONE Original Android Development] dharmabm:
This thread is a real cluster****. There really should be separate threads for KitKat and LP. Am I the only one who thinks this?
[ONE Original Android Development] JaylanPHNX:
I'm on Robbie's latest. The one with those commits. [emoji20]

It's baconnn!
[ONE Original Android Development] chikimonke:
That is odd then, don't know what to tell you?
[ONE Original Android Development] JaylanPHNX:
I tried once more to flash the new modem (wiped caches and system, flashed modem, ROM, Gapps, etc, and modem again) and still no signal. I get com.android.phone has stopped. My APN still appears to be correct. If I go to network operators it fails on search. Toggling in and out of airplane mode changes nothing (though strangely, the power menu says I'm in airplane mode even if I'm not). I downloaded an app to grab a logcat. I really hope there's something useful in it. I'm calling on [MENTION=4911350]RobbieL811[/MENTION], [MENTION=4790322]kufikugel[/MENTION], [MENTION=1277872]dankoman[/MENTION] anyone who might know anything. I know I'm on the build that requires the new modem, because my proximity sensor doesn't work. Any ideas/help would be appreciated.

PS The log was too large to upload as a .txt file so I added .zip on the end to fool the uploader. Just rename it and take off the .zip.
[ONE Original Android Development] rolear8:
Try a clean flash if you haven't tried .
[ONE Original Android Development] fusionjack:
i also hardly believe that a modem could solve proximity sensor issue.

as i saw in the logcat yesterday, the proximity sensor issue was coming from packages/services/Telecomm. this is a new component in LP. there no new commit in this project but yet the proximity sensor is broken. there must be something underlying changed. someone already mentioned this to Steve in a gerrit commit. let's wait for his response.

thanks for testing Nat!
[ONE Original Android Development] Nucleonic:
[MENTION=4911350]RobbieL811[/MENTION]

I was looking through Gerrit and saw that you added a new commit for NuPlayer - https://gerrit.slimroms.net/#/c/22587/ , which concerns not not assuming metadata .

I've been building successfully (able to watch Hulu) using this commit only - https://gerrit.slimroms.net/#/c/21974/ which concerns PCM offloading.

Are both commits necessary for resolving the Hulu problems I've posted about previously? Just asking to see if I should cherry pick the new commit on my next build.
[ONE Original Android Development] RobbieL811:
I just pushed that one this morning I think. Stupid Tapatalk won't let me go to the links. It's obviously not "necessary" as you answered your own question w/ your question. Lol. You said yourself that you had been successfully building with the other commit.

Sent from my 1+1
[ONE Original Android Development] spanish33:
[MENTION=4911350]RobbieL811[/MENTION] if I flash a kernel that supports dt2w on slimlp other than the default kernel it no longer works. Is it because of the temporary implementation of dt2w code you added to slimlp or because the rom don't have an option to turn dt2w on?
[ONE Original Android Development] kevace1:
Am I correct to assume that there is a known bug of the screen not coming back on a when it goes to sleep and you want to wake it back up? This happens to me every time I don't tap the screen before it automatically sleeps and then I try to wake it back up right away, the hardware keys light but the screen stays black and doesn't come back on till like 5-8seconds....in some occasions the screen is actually active as when I slide to unlock I get the sounds as if I unlocked but no screen image.....is this what everyone refers to as SOD? Is this also an issue on slimLP?
[ONE Original Android Development] chikimonke:
Which kernel are you flashing? I use AK myself, and then I have to use Synapse (with UKM flashed as well, otherwise Synapse throws nothing but errors at you) Then on the "Wake" tab in Synapse, uncheck everything, apply, check "Apply from init.d", apply, check DoubleTap2Wake, apply. Then DT2W should work no problem.
[ONE Original Android Development] Natakranta:
Let me guess, you are on SlimKat 9 and you flashed me OPO alpha LP radio? If that's the case flash back CM 44S radio.

just few posts back

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] RobbieL811:
Yeah. Definitely has to do w/ my Jacky way to add tap to wake. I still need someone that is good w/ java to fix the way our tap to wake is done. I have tried and tried man. I can't do it.

You are incorrect. This is not a bug and doesn't happen to me. Sounds like you need a clean flash. Something screwy is going on on your end.

Sent from my 1+1
[ONE Original Android Development] spanish33:
No I use boeffla kernel, [MENTION=3714874]matius44[/MENTION] reported that it works for him so I guess I will have to see why it doesn't work for me. Nothing to worry about I will use the swipe to wake functionality in the kernel by the time.

I know you work very hard on our device so it will fix sooner or later with your help and others.
[ONE Original Android Development] chikimonke:
Did you check the settings with Synapse? boeffla should work with it as well.
[ONE Original Android Development] kevace1:
This could not be further from the truth. This is the first ROM I flashed after I unlocked the boitloader. Its the whole reason why I unlocked it as the OP said, they were approached by OPO about the ROM, and after the sour taste I got from the Micromax/Cyanogen fiasco I decided to finally unlock my bootoader and flash something different. So I came from originally 44s to unlock bootloader to install TWRP recovery to factory reset anyway, to flashing this and slim gapps and wiping cache/dalvik afterwards.

So I'm not sure where to look for then....I haven't even rooted this ROM yet either, never had a reason too but it looks like I'm gonna have to as I'm gonna be forced to use titanium to back my data and reflash this......a little tedious really......
[ONE Original Android Development] Nucleonic:
I have the ak v77 kernel installed along with the latest alpha. I'm using Synapse and it shows an option to enable dt2wake. I selected the appropriate options to enable that feature via the app but dt2wake still doesn't work. I even went so far as to enable init. d. Am I missing a key commit to enable this?
[ONE Original Android Development] deltatux:
Hey guys,

Is it me or the latest build (January 5th, build 2343) seems to have crappier battery life than the previous builds? I'm running stock Slim kernel. Can anyone else confirm?

Cheers,

deltatux
[ONE Original Android Development] RobbieL811:
Ok. Well, glad to have you here as a newcomer. Did you flash one of my SlimLP alpha builds or did you flash SlimKat KK 4.4? Also, to everyone else, I will probably open another thread for SlimLP in the next few days. A few people have said something about it in here, and I agree, it does get kinda confusing. When I open up the new thread, I will post in here and let everyone know.
[ONE Original Android Development] deltatux:
That would be awesome because there's already confusion setting in when people assume everyone is on SlimLP or vice versa. Looking forward to it.

Cheers,

deltatux
[ONE Original Android Development] RobbieL811:
SlimLP thread - http://xdaforums.com/oneplus-one/orig-development/rom-slimlp-bacon-t2994643

From now on, this is where I will post alpha builds and anything related to SlimLP. Go ahead and subscribe it lol.
[ONE Original Android Development] kevace1:
Thanks for the welcome. I flashed the SlimKat stable 9, and slim gapps. Now I'm getting a weird reaction. When I go into my phone app and I press either a favorite contact that appears right away, or any contact from my list, I get a black screen and the famous loading circle....that's weird. Just started happening like a day ago....its happening a little more frequently now, but not always....just crazy. I know for sure now I'm gonna have to flash something again....let me see if I can tolerate any bugs if any of SlimLP...really want that audioFX back......
[ONE Original Android Development] Natakranta:
What exactly gapps did you flash with SlimKat 9?

You should use latest available Slim gapps for 4.4.4 - link.

If you used any other I recommend to reflash.

Best do to recovery, wipe these 3 only in advance wipe menu: cache, system, dalvik.

Flash SlimKat 9.

Flash mini or normal or full Slim gapps from my link above.

Reboot.

You will not lose your data, apps or settings. Everything will there be in place as you left it before going to recovery. But you will have updated gapps with updated Play Store and Google Play Services.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] vassy.uk:
Hi. Just flashed slimkat 4.4.4. Double tap to wake is working? :/
[ONE Original Android Development] kevace1:
I used the slim gapps from the official slim website. But I'm for sure gonna do what you suggested and see how things go. I downloaded the normal gapps from the link you provided and see. I will reported back by the end of the day to see if the little bugs dissapear.

Edit: BTW, I Ade sure I used the KK gapps and not the LP one.....in case that ran through your head.[emoji6]

Update: this idea did not work for me at all. The phone app is acting even more funky.....I receive a call as I was doing something on the phone, and the phone won't let me pick it up......didn't even change screens to the phone app.....it just played the ring tone.....but the phone didn't freeze, I kept doing what I was doing (typing a text, and looking at eBay). And the phone wake up from auto time out is still happening, but this time is much more frequent then not. So, I'll be clean flashing over to SlimLP now.....
[ONE Original Android Development] evanovici:
Just asking here as I found no answer anywhere else, how to or is it possible to move the volume panel position? It's hard to reach all the way to the top of the screen one-handed...
[ONE Original Android Development] RobbieL811:
Would have to be done across ALL Slim builds. Not prepared to do that. It's fine the way it is. Besides, there are the buttons too. And really, how often do you change the volume?
[ONE Original Android Development] badutahboy:
Hey all, I just bought, unlocked, and rooted my OPO and installed Slimkat (the late december stable release)... Today I was trying to use carbon backup to restore some of my saves, and I can't get root to work. I enabled it in Developer options, and no popup comes when I launch Carbon (or rootchecker).. both tell me my device isn't rooted, presumably because the SU popup isn't coming.

Also flashed superSU through TWRP, but I don't have an icon, although it shows up under Apps if I search in google now, but I can't launch it there either.

Is there some obvious step I'm missing here?
[ONE Original Android Development] Natakranta:
Strange. I never had any problems with SlimKat built in Superuser. Root is working fine. I restored most of my user apps from Titanium.

Did you do a clean flash? Are you sure your downloads (ROM and gapps) are not corrupted?

Which gapps did you flash? You should use 4.4.4 build 9 gapps. Download them and do clean flash. In TWRP go to wipe menu and chose advanced. There in advance tick these 4: cache, system, data, dalvik and swipe to wipe. Flash SlimKat 9 and Skin gapps 9. Reboot.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] badutahboy:
I installed the 4.4.4 build 8 x-385 gapps...

Relatively sure my downloads weren't corrupted. I didn't have any hiccups while downloading or moving them to the phone... I did a complete wipe.. In fact, I wiped everything and had to ADB push the ROM to the phone since I wiped out my OS. I wiped before installing GAPPS just in case, etc....

If possible, I'd like to avoid wiping again. Downloading my apps takes FOREVER.. Tons of apps, 2 different google play accts, and Amazon to boot, lol.
[ONE Original Android Development] Natakranta:
385 gapps you used are outdated, use the one I linked in my previous post.

Try semi dirty flash first. In TWRP wipe advanced tick these 3 only: cache, system, dalvik. Flash ROM. Flash gapps. Reboot.

This will not delete your apps or settings.

Go to developer options. Disable root (if enabled) and enable it back for apps and adb.

Go back to seeing main list and open Slim Centre. It should now ask you for root. Grant it.

If it doesn't work, I don't know.

Then try clean flash as I described in previous post.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] badutahboy:
Worked like a charm. Gracias!
[ONE Original Android Development] Natakranta:
De nada amigo ;)

Yet another happy user!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] evanovici:
Oh, didn't even think of that, couldn't dare to ask. I would love to do it myself, that is if you will point me in the right direction... Thanks!
[ONE Original Android Development] ripeart:
Sorry wrong thread.
[ONE Original Android Development] iamelton:
forgive me if this is asked in this thread.. i did searched with "reboot recovery" but couldnt find any related posts..

my problem was that from the power menu, when i chose "Reboot > Recovery" or "Reboot > Bootloader", it booted breifly to the TWRP logo screen and then booted up to the system (for the former) or just booted up to the system (for the latter).. in either case the reboot option did not worked..

im running latest SlimKat build 9.0 with full gapps flashed, latest TWRP 2.8.3.0.. all stock apps with no user app installed yet..
[ONE Original Android Development] indian84:
That's a bit strange.

Can you try below,

1. Power off your phone.

2. Hold Vol Down and Power button together.

3. Release them when you see 1+ logo.

This should boot you into recovery.

If it doesn't you probably have corrupted recovery.

Install flashify from play store and reflash recovery of your choice.