yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] priyank.gupta.1984:
I am on 1st Jan Build and not able to mount USB Pen drive, Using ES file Explorer, Is it only me or any one else is facing this issue, Any suggestion please

Thanks in Advance, Please someone reply
[ONE Original Android Development] jafferman:
White status bar, my bar is all white and I'm unable to see my notification text because the font is white too. Any suggestions?
[ONE Original Android Development] runderekrun:
My thumb drive works fine on same build.
[ONE Original Android Development] priyank.gupta.1984:
Thanks, May I know which file explorer you are using please
[ONE Original Android Development] Paoliz:
No SIM detected on latest build, dirty flashed... Solutions?

Inviato dal mio OnePlus One
[ONE Original Android Development] madsponge26:
Oneplus one cm13 new firmware/modem before update

No simcard?

No wifi?

Need latest modem?

Flash this Oneplus One update before flashing the sultanxda update

https://www.dropbox.com/s/llvifrxbm3jv17b/OnePlusFirmware.zip?dl=0

Flash update firmware

Flash sultanxda

Flash supersu

Flash xposed (optional)

Flash viperatmos mod (optional)

Wipe dalvik/cache

Reboot

Dont panic!

Benefit??

---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------

Flash update firmware.. Check above
[ONE Original Android Development] Paoliz:
I have already flashed the ROM, Have I only to flash the updated firmware or again dirty flash the ROM?

Inviato dal mio OnePlus One
[ONE Original Android Development] runderekrun:
ES. Doesn't really matter though I got a pop up from the system asking me what I wanted to do with the thumb drive the moment I plugged it in.
[ONE Original Android Development] JAKNAP1710:
[MENTION=4800121]Sultanxda[/MENTION], I am facing this intermittent issue with "Double Tap to Wake", and i am sure few others are also facing the same. Sometimes it doesn't work, we have to wake the device with Power button and then DT2W starts working again. Would you be kind enough to help me with this problem.
[ONE Original Android Development] nschopra:
[MENTION=4154916]madsponge26[/MENTION], I think flashing Supersu will result in bootloop. I once did it without reading the OP and faced the bootloop.
[ONE Original Android Development] Paoliz:
Flashed new firmware, flashed ROM, no simcard...

Inviato dal mio OnePlus One
[ONE Original Android Development] balleny:
i know it is not directly related to this rom but i recently did the switch from calkulins 4.4 and facing some problems:

i was able to limit most things and use Greenify to get even more out of my batterie (up to 3 days, was great) but now on the new rom i am facing the problem that i am not able to configure K-9 Mail, Whattsapp and Google Hangouts this way that they mostly sleep and maybe use the doze up to check for messages etc.

Either i am greenify'ing them (and some settings in privacy guard etc) and have to manually open them to update the messages (no pings / vibration on incoming messages) or i let them active and they drain heavy amounts (K-9 drained up to 25% of my overall usage :( )

Are there any tips or a small guide for the right configuration for a MM newbie? or even new app alternatives which work better with Doze / etc (pref opensource)

oh and i am a bit confused about the privacy settings / etc stuff because CM used to have one but MM implemented it too, which is recommended at all?
[ONE Original Android Development] madsponge26:
Dirty flashed the update firmware then the rom

Are you sure? Why im using super su...

---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------

Use naptime and greenify pro.
[ONE Original Android Development] bedman77:
Flashed supersu beta 2.66 with no problem.

Surce: http://xdaforums.com/showpost.php?p=64161125&postcount=3
[ONE Original Android Development] Paoliz:
Already done, no simcard

Inviato dal mio OnePlus One
[ONE Original Android Development] Nicuz95:
I can confirm what he said, no simcard for me too. I tried everything, really, I'm searching for a solution that not requires wipe.
[ONE Original Android Development] xxBrun0xx:
1/1 build runs great, but after dirty flashing 1/4, I get bootloops and no sim card. Went back to 1/1 and problems went away.
[ONE Original Android Development] bedman77:
No simcard is usually resolved with flashing a stock based rom . And after that flash the rom of your choice.
[ONE Original Android Development] Spaulding89:
Can't use any theme on 1/4. When I activate one everything will get unreadable.

Sent from my Bacon with Lightning Power
[ONE Original Android Development] nschopra:
Thanks a lot buddy. It worked in very first attempt. To all those who are facing "No SIM" and "Random Reboot" issues, kindly go through this post to solve the problem.
[ONE Original Android Development] madsponge26:
In that case you need to flash the cm13 nightly or sultanxda Jan1 build..

Flash update

Flash sultanxda jan1

Check if simcard detected (if not flash the update firmware)

Sultanxda Jan1 build with modem.
[ONE Original Android Development] abhibnl:
[MENTION=4800121]Sultanxda[/MENTION]

I'm facing a very weird but occuring a lot now kind of bug from the 1st Jan build. Sometimes when i double tap on screen to wake the device, it doesn't do anything. I then try tapping multiple times with no luck at all. Then, when i press the power button, the screen turns on but the moment i touch the screen, it gets off again, and DT2W works fine after that. This issue is completely random and happens alot now, 3-4 times a day. Could you please tell me if there are any logs that i can provide in order to help you debug this issue? This never happened on SlimSaber Lollipop or VM13 MM.
[ONE Original Android Development] Shreps:
My 2 cents :

I'm on Sultan's build since December 2015. Always dirty flashing every new build.

On December 30, I had to flash the CM 13 Nightly (firmware/trustzone version update), then the Sultan's build

Dirty flashed Build 1st January OK

Dirty flashed today build (2016-01-04)

> No SIM Card

> Random reboots

> Settings Force Close (probably because of my theme)

Dirty flashed back 20160101 build : all back to normal, SIM back, no data lost.
[ONE Original Android Development] Manholas:
Done. Thanks.
[ONE Original Android Development] hamma:
Strange, i´ve gone the exactly the same way. But i don´t have any problems.
[ONE Original Android Development] novren:
Are themes not working for anyone else?
[ONE Original Android Development] guywong:
I did an OTA update too, but my baseband reverted to the old H2OS 013 one. While that seems okay, I like the new modem a lot more as it gives me much better battery life. So I flashed the Dec 30 modem and reinstall the Jan 4 build.

​bacon_firmware_h2os_update_2015_12-30_.4.0.1.c1.11-00004.zip

https://www.androidfilehost.com/?fid=24352994023703384
[ONE Original Android Development] madsponge26:
I used swift dark theme.. So far i test euphoria cm13 and deep darkness.
[ONE Original Android Development] donk165:
Themes are broken for me, after I installed 1/4 build, my status bar was white and so was my quick toggles area, I changed back to stock theme and then when I go to select a different theme, the theme app crashes. I cannot select any themes :(
[ONE Original Android Development] Paoliz:
Exactly the same thing!
[ONE Original Android Development] Brian325:
I'm getting a much improved signal at home now with the new firmware. No issues with this ROM.
[ONE Original Android Development] world94:
Way to unclock it by a zip like in Sultan CM12? ( 2.4gHz )

Thanks :)
[ONE Original Android Development] Prodromodinverno:
Lord Boeffla?*@andip71

Exciting News... OnePlus obviously doing a developer program now and they just approached me on it. Sounds x-tremely interesting. #OnePlus

[MENTION=4800121]Sultanxda[/MENTION] you were contacted too?
[ONE Original Android Development] TareqA:
What!!!! Tell me more where did you find this info
[ONE Original Android Development] Sultanxda:
If your SIM card was detected and working fine in the Jan 1st build, but broke after flashing the Jan 4th build, then that means you did not install the updated firmware correctly. This has nothing to do with the ROM. TWRP versions newer than 2.8.6.0 do not properly install the modem, so you need to find a TWRP version that can install the modem (2.8.6.0, or some custom TWRP build), and use that to dirty flash the latest official CM13 nightly (or whichever firmware package you want).

If you want to use the Lollipop modem (0241 baseband), then you need to flash the full Lollipop firmware package.
[ONE Original Android Development] AksHay1994:
http://xdaforums.com/devdb/project/dl/?id=15052
[ONE Original Android Development] world94:
Thaaaanks!

Is there a way to update it when it's in secondary rom in MultiROM? ( without have gapps problems? )
[ONE Original Android Development] if-else-endif:
I have a problem with receiving messages from viber. I receive it only then unlocking the phone. Anybody have an idea how to fix it?
[ONE Original Android Development] S0und_:
OFFTOPIC

If i decide to go back to 44S (yes, to kitkat), can i face any predictable problem during the process? I would do the jump from sultan's rom.
[ONE Original Android Development] honor_77:
What about the cortana integration in cm? Is it included in cm13 too?!
[ONE Original Android Development] dorian1326:
My modem has been properly updated and it worked on LTE when I was over at my parents house yesterday. I now moved back to my college town (where T-Mobile only offers 3G on the bands supported by our OPO) and I don't get any 3G signal, nor even Edge. I get only the base signal with no data whatsoever. I tried flashing the latest CM13 nightly and it said "modem already up to date" in the log. Not sure what to do now other than going back to the older firmware or switching to Cricket (I tested a friends' cricket sim and it got LTE on it). Where can I find the Lolipop firmware package or what would I need to do to go back to the older firmware?
[ONE Original Android Development] Wicked4u:
Did that. All's well. I'll stick to 2860 and that's that :)

So, to recap,

EASIEST method:

1. Go to playstore: search for FLASHIFY

https://play.google.com/store/apps/details?id=com.cgollner.flashify

2. Install that

3. Flash twrp 2860

4. Reboot to recovery

5. Flash latest CM13 4 bacon:

https://download.cyanogenmod.org/?device=bacon

6. Flash Sultan's ROM

7. Enjoy! :)

8. I HOPE I don't see any more posts u don't get the latest build working properly :)
[ONE Original Android Development] world94:
I've flashed latest nightly but I can't open Playstore anymore, fc every time :(
[ONE Original Android Development] Wicked4u:
It's working here. I got open gapps, micro, I guess...

Didn't update those in a while..
[ONE Original Android Development] world94:
Open Gapps too
[ONE Original Android Development] Wicked4u:
Ur not gonna like it but if I were u, I'd wipe it all and then do a clean install.

Make sure u back up your media first and u might wanna move ur tb backup to ur pc or smth !!!!

Follow the steps I gave u above PLUS the open gapps to flash lastly and then u should be good 2 go!! :)
[ONE Original Android Development] stalkachu:
Soft reboot to CM logo when trying to to make regular calls on newest build. Is it just me?
[ONE Original Android Development] world94:
I can flash the gapps but when i flash the update on secondary in MultiROM I have an error ( E:Error executing updater binary in zip '/tmp/mr_update.zip' ) and when I reboot on this ROM ( still installed even with the error ) I can't open PlayStore
[ONE Original Android Development] Wicked4u:
MultiROM is outta my league, pal. It's like dating several women. U'll get none :) /joke
[ONE Original Android Development] drnizeguy:
Rom is really great and the new radio is much better for me.

One thing tough, I'm on 400 DPI and in some apps the settings menu is messed up, see the pic attached.

On normal dpi there is no problem. Dont know if this is rom or app related, but on 5.1.1 I didnt have the 'problem' .
[ONE Original Android Development] raul.lopez1958:
Modem?

January 4, 2016:

ROM:

*Latest upstream CyanogenMod changes

*Modem firmware is no longer built into the ROM (you can use the Lollipop modem if you had issues with the new modem)

¿What modem are in this build?

Thx
[ONE Original Android Development] raul.lopez1958:
Good contribution boy ... so you still get far :good::good::good::good:

This build change my last modem.:eek:
[ONE Original Android Development] runeazn:
Flashing the 4 jan 16 build bricked my phone, so flashers beware!

coming from 1 jan build.

what did I do?

It said no SIM card detected so i tried to call my home number, phone crashed rebooted and froze on lock screen, charging stopped.

Hardshutdown by volumebuttons + lock button, doesn't boot or charge anymore.

Flashing comes with a risk I learnt :P
[ONE Original Android Development] thijsoost:
6 January? Are you a time traveler?

Latest build is working fine on my device (dirty flash), calling is also working fine.

*Edit*

Ah, I see you edited your post.
[ONE Original Android Development] raul.lopez1958:
No problem with me... but new bulid change my old modem... :confused::confused::confused::confused:
[ONE Original Android Development] Varakh:
Hi!

After upgrading to Jan 4 build (via Settings/Update Menu) my SIM isn't recognized anymore (no PIN-screen) and force reboots within 1 minute. Rebooting won't help. I tried to resolve this by manually flashing it with the following steps:

wipe sys/cache/dalvik in TWRP

flash nightly of CM

dirty flash Jan 4 build

This didn't work either. Do I have to reflash a modem now? The previous build worked fine.
[ONE Original Android Development] madsponge26:
1 in a million cases?

Read the OP..

Follow instructions..

Benefit?

---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------

Modem include in jan1..

January 4 not included because other users flash 5.1.1 modem.
[ONE Original Android Development] Varakh:
I am having the same thing. Is this mentioned in the OP? :eek: Cannot see it. See #6447. I am having the same issue + reboots. Provider is T-Mobile.
[ONE Original Android Development] raul.lopez1958:
January 4 has changed my modem that has January 1 ... How is it possible?
[ONE Original Android Development] Lupin The Third:
Can you upload a screenshot of your modem?
[ONE Original Android Development] madsponge26:
Clean install..:)
[ONE Original Android Development] alroger:
Modem and SIM Problems

I have an idea... let's copy/paste the OP and Sultan's last comment on every page:

http://xdaforums.com/showpost.php?p=63694406&postcount=1

http://xdaforums.com/showpost.php?p=64640204&postcount=6425

All residual side effects from other tests, ROMs, firmwares, modems...

Restock and start over.. and feel fresh again.

If you are going to use other modems, deal with it. If not following the OP, deal with it. This is Sultan's thread, not CM's, not TWRP's, not xposed's, not modems...

BTW there is a OnePlus One all in one thread with links to almost everything you need... all modem versions from Stock, for example.

Don't expect your modem to be the same, if you have residual stuff from other tests... TWRP will get a backup or something from the other ROM/firmware you flashed and do strange things.
[ONE Original Android Development] Lupin The Third:
[/COLOR]

So what's the problem here? you are on latest modem...
[ONE Original Android Development] -iHackerz-:
Well I thought that the new modem + wifi firmware would fix my issues but it apparently didn't. I seem to have a really slow WiFi connection ever since I flashed the first build of this rom and can't seem to notice why. When I use speedtest on the phone, it turns out around 30mbps which is fine and it's my speed. But loading pages, browsing the play store and connecting in general, takes forever! The connection was perfectly fine on Lollipop. Sorry if this was mentioned before but I didn't any solutions yet.

I'm running the 1st Jan build, stock kernel, new modem.
[ONE Original Android Development] ttsprnkls:
Cant access recovery after flashing 2.8.6.0. How do I downgrade? (used fastboot to flash)
[ONE Original Android Development] Varakh:
Working now. Didn't see/pay attention to the twrp version requirement and had 2.8.6.1, my fault, sorry. :angel:
[ONE Original Android Development] jukyO:
Same happened to me. I simply could not load 2.8.6.0 by any means. Use modified 2.8.7.0.5, and flash via fastboot. It will load firmware properly.

Here:

http://xdaforums.com/showthread.php?t=2981495
[ONE Original Android Development] runeazn:
If someone can help me unbrick it be my guest, im kinda sure it's not in the OP. Else you could point it out as I'm not finding IT?

edit: the post tells me to flash recovery,

but how do you flash recovery on a bricked device? with fastboot or something? I did this years ago, but i forgot now...

Phone doesn't turn on ...

its a hard brick as my OPO is detected as QHSUSB_BULK USB
[ONE Original Android Development] madsponge26:
I have no problem mate. Someone ask to take screenshot.
[ONE Original Android Development] Lupin The Third:
I'm your guest, so to speak.

This helped me unbrick my opo some time ago

http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
[ONE Original Android Development] alroger:
http://lmgtfy.com/?q=how+to+flash+twrp+oneplus+one

Then backup what you need, via TWRP... and restock.
[ONE Original Android Development] runeazn:
Same guide i'm using atm found it few min ago however I cant find my usb device in the list...

I'm sure you can vouch the usual flashing procedure works for hardbricked devices [MENTION=4101982]alroger[/MENTION]?
[ONE Original Android Development] Lupin The Third:
But I asked someone who had a problem, quoting HIM. Follow the discussion please before creating a mess replying without thinking (no offence, and thanks for trying to be helpful)
[ONE Original Android Development] runeazn:
my oneplus doesnt show up anymore in device manager.

Well I leave it fortnight in the charger and hope it will just magically turn on, battery before dieing was 50% tho.
[ONE Original Android Development] stalkachu:
Worked out what it was. For me, switching from the Play Store Dialer back to the GApps Dialer solved the reboot on call making. May help anyone else who is having the same problem. Everything else working great.
[ONE Original Android Development] runeazn:
nonethless i found that thread already, props to u [MENTION=3859635]varben[/MENTION] it worked my phone is back into recovery mode :D
[ONE Original Android Development] Sultanxda:
The January 4th build did not brick your phone; you did. The reason why I don't provide firmware packages in the OP and instead tell people to flash the official CM nightly is because I don't want to take responsibility for distributing firmware packages. Playing with firmware can be risky if you don't do it correctly.

The reason why your SIM was working in the January 1st build, but not the January 4th build, is because you did not update your firmware correctly. TWRP versions newer than 2.8.6.0 do not properly install the modem, but you never noticed that the modem wasn't installed correctly because the January 1st build came with the correct modem built into it. The January 4th build no longer has its own modem, so instead it uses the modem available on your device... but you did not have the correct modem installed (due to TWRP not installing it correctly). The Lollipop modem (0241 baseband) is not compatible with the other new pieces of firmware, which is why your phone didn't work.

As a note to everyone else: firmware should only be flashed in full packages. Mixing and matching modems with firmware that they didn't come with can cause instability (ex. people using the 44S modem with Lollipop firmware experience random reboots, and using the 0241 modem with the new firmware breaks mobile network completely).

Good luck with un-bricking your device :/

It's possible because the January 1st build came with its own modem. In the January 4th build, I removed the built-in modem from the ROM, so now the ROM is using the modem that you have installed on your device.
[ONE Original Android Development] gkillerx:
I am really confused now. What recovery can we use? 2.8.6.0 or can we also use the 2.8.7.0.5 material recovery? (which I like way more)
[ONE Original Android Development] thewoZa:
Either
[ONE Original Android Development] buciuta.andrei:
They both work very well
[ONE Original Android Development] fourpointsix:
That's good information, and likely explains why I had issues with the latest CM13 nightly. So, coming from the 12/24/2015 release of CM13 and likely running a newer version of twrp, what's the procedure for switching to your ROM?
[ONE Original Android Development] ygoralmeida:
... Well, i'm loving this build, but i noticed ( maybe i did something wrong ) where is the trebuchet launcher ? since i use gaaps for 6.0 stock does it removed or it never comes with it ?? how can i install trebuchet launcher 3 ??
[ONE Original Android Development] buciuta.andrei:
Some gapps remove the trebuchet launcher and replace it with the google one, ot should be written in their description if they do that.
[ONE Original Android Development] Sultanxda:
1. Install TWRP 2.8.6.0.

2. Flash the official CM13 nightly without wiping anything.

3. Flash my ROM without wiping anything.

4. Reboot. You're done.
[ONE Original Android Development] ygoralmeida:
Huum, but how to get the launcher 3 back !? i'm missing it
[ONE Original Android Development] buciuta.andrei:
Here it is, inside the zip, no need to flash, just install.
[ONE Original Android Development] ygoralmeida:
Thanks brother !!! :D
[ONE Original Android Development] FirstBurst:
Newest update soft bricked my phone, no sim card, and constant reboots. This occurred by dirty flashing and clean install. I went back to 01-01-2016.
[ONE Original Android Development] buciuta.andrei:
Try to dirty flash the CM13 nightly first and after that Sultan's rom
[ONE Original Android Development] Lupin The Third:
Maybe ONE page back is the answer to your problem.
[ONE Original Android Development] move_some:
Read post #6468 and you know why....?
[ONE Original Android Development] runeazn:
Well I was on 2.8.6.0 not sure, can't check it now anymore.

I remember flashing the frimware someone posted in this thread and afterwards I flashed the 1 Jan build.

Well no matter what, I just flashed the recent nightly and then flash ur rom, it's booting again :)
[ONE Original Android Development] FirstBurst:
Thanks friends! I completely missed that post.
[ONE Original Android Development] runeazn:
Hmm I couldn't login into my cyanogen account as the homescreen just pops up, does this happen for everyone?
[ONE Original Android Development] highdiver_2000:
Install and configure Google plus
[ONE Original Android Development] Ghost-of-the-Sun:
I was able to configure my profile and choose a picture without having G+ installed.
[ONE Original Android Development] CalamitySir:
Having come from your CM12 ROM to this right now feels awesome. Performance has been very good, same goes with the battery. But just one thing I want to clarify if any of you guys are having this problem as well. My phone's battery stats are never reported correctly. I am using the latest update right now, I charged it to max 100% and I have been using it while traveling back and fro from home to work. My battery stats are constantly at 100% until about 2 hours in. Then just this morning it suddenly shuts down at around 50%. I am guessing the battery stats are falsely reported, any of you guys have this similar issue?
[ONE Original Android Development] Evermind10:
Those with trouble flashing their rom shld try philz touch. Never had any problems using it.

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

Use your phone till it shuts down, go into recovery and charge your phone back to 100%. After that, reboot back into the rom.
[ONE Original Android Development] tigobrata:
when will this rom leave alpha phase?(what does it take) #curious