yashsingh1/xdaforums huggingface dataset:
[M.O.J.O. General] wastate2014:
This should be awesome if they do it right? I am kinda bummed its Quailcomm and not NVidia surprised coming from a gaming company they would choose a processor that isn't known for its gaming ability?

Also there is Snail Games OBox coming which is NVidia:D . Can be upgraded anytime by changing module!
[M.O.J.O. General] disorder78:
Forge TV

The Razor Forge TV is nothing special. It's just like the MOJO just running android TV. 16gb onboard storage is a joke, and the system will still not be able to run every game. I see no interest in the Razor Forge TV, and I have a hard time understanding why it won the best of CES. It's seriously nothing to be so happy about. I just think this box is a total failure, and has brought nothing special to the living room.
[M.O.J.O. General] Unjustified Dev:
It's because it's the first android TV box officially announced. The mojo in my opinion is better. Two USB ports micro sdcard and we also have Android TV port near fully functional. The setback for me is Google has yet to support external storage devices in android TV.
[M.O.J.O. General] kgersen:
The mojo was $250 with a controller (and a mandatory controller so if you already have BT controllers it was a waste).

ForgeTV will be $150 with a controller (optional controller so only $100 if you already have BT controllers).

The SN 805 beats the Tegra 4 everywhere: http://www.androidauthority.com/tegra-k1-exynos-5433-snap-805-541582

Same RAM and internal storage.

One the 2 USB ports of the Mojo is for the controller dongle. So practically 1 usb port each.

ForgeTV ethernet port is 1Gbps, Mojo port is 100Mbps.

16Go is enough because you can have as many as you want of external storage with an USB OTG storage (sd/stick,sdd, hd,etc).

According to the a XDA Nexus Player forum topic that external storage can also be used for apps (using some mounting apps).

I fail to see where the mojo is better. really. even more that Mad Catz practically abandoned it.

and so far "Android TV port near fully functional" is a one man job (you) and not guaranteed.;)
[M.O.J.O. General] Unjustified Dev:
We will just have to wait and see about that. Have a little surprise tomorrow.
[M.O.J.O. General] Aerofreak360:
You big tease lol
[M.O.J.O. General] Sir Jaxxy:
Having been at CES and having got hands on time on the Forge TV here is my take. I think that Razer should have added a second USB port and SD storage. In my opinion these 2 things will be a disadvantage. They did, however, bring some welcome improvements over the MOJO in the full Gigabit Ethernet and the entire UI. There is no doubt that the Forge TV is much more a consumer friendly product. However, from what I could tell from talking to folks at CES this is not going to be able to be easily rooted nor allow custom backup options. I could be wrong and just talked to the wrong folks (this was my first CES). The 2 areas that I thought the Forge really out did the MOJO was in it's ability to Stream almost any game from almost any PC (not just those running NVidea) to the forge. I tried a couple of high end games and they ran flawlessly. This will be huge because you will no longer need to really on 3rd party apps and subscription services such as OnLive to do this.

I was not impressed with the Serval. To me it was just another controller and at an $80 price point found it to be extremely over priced. I also have come to truly appreciate the media buttons on the CONTRLr and find the lack of them on the Serval to be disappointing. This is after all going to function as a remote as well as a controller.

The Turret was just the opposite. I was blown away by it. This is the first laptop keyboard I have used that feels good. It really feels and responds like a gaming keyboard. The mouse having a low level of magnetism so it stays where it is when you let go is fantastic. Only downside I had is that I have large hands and the mouse was on the small side. Along those same lines though, the key spacing was just enough that I did not feel cramped when typing.

In the end will I be buying any of these? I will most definitely be purchasing the Turret. Most likely a couple of them. I will also most likely be picking up a Forge TV down the road as well. As for the Serval, unless Razer rethinks the price point or I can get it at a Black Friday level discount I will be passing on this. It just does not bring anything to the table that any other Bluetooth controller doesn't and at half the price or less.
[M.O.J.O. General] Sir Jaxxy:
Did I miss the surprise?
[M.O.J.O. General] opiate81:
I'm keen to see what MINIX are about to release for their control pad. I'm getting pics in a few days as well as a test unit soon.

From what they've told me it is supposed to make touch games playable so I keep thinking of a PS4 controller type of thing :D
[M.O.J.O. General] gwaldo:
Follow the development forum.
[M.O.J.O. General] Sir Jaxxy:
Yeah I just got caught up over there.
[M.O.J.O. General] kgersen:
According to Razer web site (http://www.razerzone.com/cortex/stream), the streaming feature isn't specific to the Forge and will work on any Android 5.0 device.

The end game for Razer with the Forge is more to sell the accessories (Serval and Turret) than the console itself. That is where the high margins are. Peripherals are still their core business after all.
[Galaxy S II Q&A, Help & Troubleshooting] QA Bot:
Q&A for [ROM][AOSP][JB][4.1.2][JZO54K] SuperNexus - I9100G - BUILD 5 [17-10-12]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP][JB][4.1.2][JZO54K] SuperNexus - I9100G - BUILD 5 [17-10-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy S II Q&A, Help & Troubleshooting] topezz:
download link is dead, any backup?? TQ
[Galaxy S II Q&A, Help & Troubleshooting] vibez_well:
Any luck to a working link to build 5 ? :confused:
[Galaxy S II Q&A, Help & Troubleshooting] jamal2198:
Yeah link ia dead..now hot file cant be access..please op..link..
[ONE Q&A, Help & Troubleshooting] c00l3rf4rm3r:
Hey,

my proximity sensor is not working after:

-backing up my phone with twrp

-installing another rom

-restoring the backup with twrp

Now the proximity sensor is not working anymore. It's annoying, because my phone turns of while calling.

What can I do to fix this?

I downloaded an app to check the sensor values and it always showed "0" for the proximity sensor. I have no idea how to fix this. I rebooted my phone, installed the backup again, ...

Nothing helped :(
[ONE Q&A, Help & Troubleshooting] siddheshvartak:
same problem happened with me today...

i also need solution..

devs plz help..
[ONE Q&A, Help & Troubleshooting] Heisenberg:
It's your modern causing the problem most likely. What ROM were you on? What ROM did you change to? What ROM did you go back to?

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] jeronimo.ribeiro.pedome:
hi,

i ve the same problem! Help......

1º i was the ROM euphoria CM12!

2º i make the restore of stock rom 44s oneplus

3º the proximity sensor dont work!!!!
[ONE Q&A, Help & Troubleshooting] jeronimo.ribeiro.pedome:
hi,

Did you solved the problem? how?

thks.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Go to the modem thread by [MENTION=1978554]zephiK[/MENTION] in the General Section and flash the 44S radio.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] ek69:
Newer lollipop ROM are advising you to flash the new alpha modem. If you ever flashed cm12 official alpha, the new modem has been flashed to make proximity sensor on new cm12 code.

It'll break proximity sensor on older cm11s code. Answer is flash older modem like timmaaa said and problem fixed.

Sent From Lollipopified Bacon Goodness!
[ONE Q&A, Help & Troubleshooting] Rohitgomes:
Solved !! Thanks
[ONE Q&A, Help & Troubleshooting] abraxid:
YES!!

Dude! Thanks so much! I spent the whole day trying to find at least what had broken the proximity sensor and now it's fixed!!!!!
[ONE Q&A, Help & Troubleshooting] spintike:
It's working again in my case!!! Thanks a lot :):laugh:
[ONE Q&A, Help & Troubleshooting] b0r0d1nsky:
Didn't work for me.

1)Backup cm11s

2)Full wipe

3)Flashed from 11S to cm12 nightly

4)Flashed the 44S radio

inf:

opo 64Gb ver.

TWRP 2.8.5.1
[ONE Q&A, Help & Troubleshooting] Heisenberg:
That's because if you're on a Lollipop ROM you need to flash a Lollipop modem.

http://boeffla.df-kunde.de/bacon/modems

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] b0r0d1nsky:
I tried all modem at page you gave me - same problem.

I solved problem by flashing old cm12 nightly (cm-12-20150106-NIGHTLY-bacon) - it works, but if i'll try update it - it will cause problem again :(

P.S. I extracted NON-HLOS.bin (it's modem file, right?) from this old nightly , i flashed last cm12 nightly and after that i flashed extracted modem via fastboot - it didn't help me
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Why try all of them? Most of those modems are KitKat modems. Are you on the right firmware? And yes, NON-HLOS.bin is the modem, but it's only part of what's required. The Lollipop modems from Boeffla and the Lollipop firmware should fix your problem.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] b0r0d1nsky:
I tried all modems because the lolipop modems didnt work for me! I started from the new one in the list and finished with the oldest

As i said only cm-12-20150106-NIGHTLY-bacon work now, but if you'll turn on "adaptive backlight" - it will crash like other roms. It works because "adaptive backlight" is disabled by default.

Is it possible to edit cm12 nightly zip file to disable adaptive backlight (maybe some kind of config file) and flash after that?
[ONE Q&A, Help & Troubleshooting] Heisenberg:
There's no point in flashing the KitKat modems, they'll only

cause

the problem, not fix it. If the Lollipop modems didn't work for you, you're doing something wrong. Like maybe you're on the wrong firmware, you never answered my question asking which firmware you're on.

And no, you can't just edit the zip to remove the adaptive backlight feature, you'd need to fork the CM12 repo and remove that commit, and then build the ROM from source.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] b0r0d1nsky:
i am on CM12 nightly (cm-12-20150106-NIGHTLY-bacon) now and i wanted to install the last nightly.

I found the solution - my friend with same OPOphone will disable "adaptive backlight" and he'll made TWRP backup, i'll flash it today.

thank you very much for help. :good:

UPD. Forgot to say - modem isn't the main reason, the adaptive backlite and my proximity sensor - are the problem... maybe sensor is broken
[ONE Q&A, Help & Troubleshooting] Heisenberg:
The modem is the problem, the proximity sensor is governed by the modem. The way the proximity sensor is handled changed when they released Lollipop. Adaptive backlight has absolutely nothing to do with it, you're mistaking a symptom of the problem for the cause. Of course adaptive backlight is going to cause problems, it relies on your proximity sensor, which in turn relies on the modem. The cause of the problem is the modem, without doubt. Hundreds of people have had the exact same problem.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] b0r0d1nsky:
but all that people solved this problem by flashing lollipop modem... why it doesn't helped me?

ok, lets start again

1) I had cm 11S

2) installed TWRP

3) flashed cm12 nightly from official site

4) i tried to flash other lollipop roms from xda

5) after all faults i returned to cm 11S

6) I posted my problem here

7) now I am on cm-12-20150106-NIGHTLY-bacon - it works... but if i'll go to settings -> screen and will enable the adaptive backlight - it will cause same problem! :(
[ONE Q&A, Help & Troubleshooting] Heisenberg:
That isn't what you said in your initial post. This is what you said:

In your first you went from CM11S to CM12 nightly and flashed an incompatible modem. Now you're telling me you went from CM11S to CM12 nightly to other ROMs and back to CM11S. Completely different scenarios. So which is it? It turns out you haven't been very accurate or specific with your information. I'm still waiting for you to answer my question about which firmware you're on (this is the third time I'm asking). If you can't even provide accurate and specific information about what you've done, then you can't expect anyone to be able to help you effectively.

So maybe it's better to ask this way; exactly which ROM do you want to be on? You tell me that and I'll give you links to the correct firmware and modem(s).

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] b0r0d1nsky:
OK i'll try again

1) I had cm 11S

2) installed TWRP

3) flashed cm12 nightly from official site

4) i tried to flash other lollipop roms from xda

5) after all faults i returned to cm 11S

6) I found this thread

7) Backuped cm11s

8) Full wipe

9) Flashed to cm12 nightly

10) Flashed the 44S radio (as you said Go to the modem thread by [MENTION=1978554]zephiK[/MENTION] in the General Section and flash the 44S radio.)

i didn't give you differnet information i gave you info about i had and what i got

I just want the last for today cm12 nightly rom (cm-12-20150316-NIGHTLY-bacon.zip ) from official site http://download.cyanogenmod.org/?device=bacon

sorry, it's hard to understand me because my english isn't so good as yours

Как же хуево когда ты так хуево знаешь английский :crying:
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Flash the latest nightly + gapps and nothing else. Check proximity sensor, report back.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] b0r0d1nsky:
didn't help me :(
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Ok, now flash this:

http://www.vanir-exodus.net/exodus/bacon/bacon_firmware_update_2015_02_26.zip

And this:

https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api

Over the top of the ROM, test bug, report back.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] Naughtie:
Hi,

I have gone through the thread and I too am suffering from the proximity sensor problem after flashing the latest nightly through Cyanogen Delta.

I am currently on the latest Nightly build of CM12 and I had originally flashed from CM11S 5Q to CM12 nightly about 15 days ago )mostly the 4th march build) and proximity sensor was working properly but since last 2 days or so its broken. I have not tried flashing any modem as of now.

Had visited the CM12 nightly thread on OnePlus forums and noticed couple of other users reporting the same problem. Need a fix as this is my primary device and going back to 11s is a PITA.

Thanks in Advance
[ONE Q&A, Help & Troubleshooting] Heisenberg:
There are more ROMs than just CM11S and CM12 available, dozens more.
[ONE Q&A, Help & Troubleshooting] Naughtie:
I think I knew that ! :rolleyes:

And that does not help me :confused:
[ONE Q&A, Help & Troubleshooting] waterdaan:
Solution(s) can be found in the cm12 thread http://xdaforums.com/oneplus-one/general/rom-cyanogenmod-12-oneplus-one-t2994967
[ONE Q&A, Help & Troubleshooting] avid4b11t:
I found that going into the display settings and turning off the Prevent Accidental Wakeup fixes the problem of not being able to turn on the phone and phone call problem.
[ONE Q&A, Help & Troubleshooting] benthomp85:
I just got my 2nd OPO last week (lost first). It came with CM11S, I flashed OxygenOS. Wiped and flashed CM12.1 nightly.

Noticed today proximity sensor does not work (in call or prevent accidental wake) so flashed CM12S after wiping to see if it still didn't work, it does not.

I know it is not hardware as I got an app that tests the proximity sensor.

Help?
[ONE Q&A, Help & Troubleshooting] Heisenberg:
You need to flash a Lollipop modem.

http://boeffla.df-kunde.de/bacon/modems

XDA Moderator

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] sambaeallegria:
CM12.1 flashes modem by itself so he already has a lollipop modem. There's the possibility that something is broken because I have the same issue too.
[ONE Q&A, Help & Troubleshooting] sshanky:
I'm in the same predicament. I had Vanir Exodus running fine, and stupidly decided to back up and see what miui was like. It didn't work and I restored my backup. No more proximity sensor.

My understanding is that Oxygen and/or Color are both similar to miui, in any case, I'm stuck here. I've tried flashing lollipop modems, even tried caulkulin's restore ROM. Nothing makes my proximity sensor work.

Are there any other things I can do? I wonder if I should just load the new ROM and see if that rectifies the issue...

Thanks for your help...
[ONE Q&A, Help & Troubleshooting] Gede:
And the same here. After receiving the phone, installed twrp, and 12s, that's all. No proximity :(
[ONE Q&A, Help & Troubleshooting] Heisenberg:
What method did you use to install 12S? Were you coming from Kitkat?
[ONE Q&A, Help & Troubleshooting] Gede:
Yes, from kitkat, as it came with the phone. Installed twrp 2.8.6.1 and YNG1TAS17L, SU v2.46.

Tried a sensor thingie from the appstore, shows the brand, type, but no changes...
[ONE Q&A, Help & Troubleshooting] Heisenberg:
So the YNG1TAS17L zip that you flashed was the official update zip from OnePlus?

XDA Moderator

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] Gede:
Yes, official.

---------- Post added at 10:31 AM ---------- Previous post was at 10:24 AM ----------

Ow, method of flashing, installed os via twrp.
[ONE Q&A, Help & Troubleshooting] benthomp85:
I fixed my issue.

I did a full wipe of everything and used wugfresh bacon toolkit to unroot and restore total stock.

I reverted to cm11s checked sensor, then updated to cmos12 checked sensor, then oxygen checked sensor, then cm12.1 checked sensor.

All working fine now.
[ONE Q&A, Help & Troubleshooting] Gede:
Good it can be fixed like that. But I surely hope there is a simpler way of fixing this.... Flashing 4 roms to get a sensor working ?
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Flash this:

http://boeffla.df-kunde.de/bacon/modems/Full-YNG1TAS0YL-modem-flashable.zip

XDA Moderator

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] Gede:
This seems to work!, thanks! ?

Thanks, got any crystals with that?
[ONE Q&A, Help & Troubleshooting] benthomp85:
I didn't have to flash 4 roms. I did that for testing.

As suggested the issue was surely with the modem/radio, but flashing the oxygen modem did not fix it for me.

Starting again from scratch was the best way for me.
[ONE Q&A, Help & Troubleshooting] Gede:
Ok...

Maybe this modem I flashed only solves the problem partially.

The sensor apps I used, detect now "near" or 0 cm, but don't change status anymore after that. I guess they should?
[ONE Q&A, Help & Troubleshooting] Heisenberg:
I wouldn't worry too much, as long as the sensor is picking you up it doesn't matter. Anyway I'm pretty sure this sensor doesn't have the capability to measure the exact distance, it either sees you or it doesn't.
[ONE Q&A, Help & Troubleshooting] sambaeallegria:
Ok i definitely found a solution. As suggested by [MENTION=6596304]benthomp85[/MENTION] I flashed back the 44s from fastboot. I let the phone update to COS12 and then installed CM12.1. Now my proximity sensor is fully working. Flashing modem only can possibly doesn't work because I think files related to proximity are not in modem but in some other file included in firmware, that's why flashing different cm12.1's didn't solve the situation, it only flashes and updates modem.

For those having problem with proximity I suggest spending a couple of hours to set the phone from scratch.

Those are the detailed step I followed:

1) Nandoid backup of my actual cm12.1 setup

2) backup of all my files on my pc

3) flash 44s from fastboot

4) Check proximity sensor

5) update towards COS12

6) Check proximity sensor

7) Install TWRP

8) Wipe everything, internal storage included

9) Restore all files from my pc trough mtp in recovery

10) clean flashed latest cm12.1, gapps, kernel

11) from recovery reboot to recovery again

12) from my nandroid I restored data only

13) reboot to system.

It took a couple of hours but I didn't have to set again my apps and data and I have a 100% functioning proximity sensor now.
[ONE Q&A, Help & Troubleshooting] clown_from_hell:
this worked for me, kudos.

I got me OPO 2 days ago, unlocked it and flashed CM12.1 06.06 nightly, shortly after that I noticed the proximity sensor issue during calls, confirmed it with 'Sensors' app. I tried multiple fixes suggested throughout xda and oneplus forums; flashing CM11S radios always eventually resulted in a bootloop. however, flashing the file linked above sovled it, hopefully for good.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Whoever was suggesting to flash a KitKat modem with a Lollipop ROM was only perpetuating the problem, where was that?
[ONE Q&A, Help & Troubleshooting] Gede:
Eventually it did not for me. I also flashed the latest oxygen modem, same result.

The proximity sensor detects "close", but then fails to detects "not close" afterwards, so calling screens stay black, like the sensor is stuck.

I have my previous phone ready to take over the "daily driver" function, while the opo goes experimental.

Sad that there is no simple solution for this :(

It's a nice phone otherwise...
[ONE Q&A, Help & Troubleshooting] Gede:
Ok, found definite solution for the proximity sensor problem.

I extracted the modem from the cm-12.0-YNG1TAS17L-bacon-signed.zip (file named NON-HLOS.bin) , this is the rom I use, and flashed it with fastboot from pc. fastboot flash modem NON-HLOS.BIN

Proximity sensor works now! ?
[ONE Q&A, Help & Troubleshooting] sshanky:
Yes, this worked! Thanks Gede. I am surprised how easy this was once you figured it out. There should be a sticky for this.
[ONE Q&A, Help & Troubleshooting] freaky deaky:
UR awesome.. ;) worked really well so thank you
[ONE Q&A, Help & Troubleshooting] 2anyone:
This is the way to kill this issue finally.
[ONE Q&A, Help & Troubleshooting] Gede:
Hmm, just flashing the modem only with fastboot solves the issue too. And it's a lot faster.
[ONE Q&A, Help & Troubleshooting] minego:
I got a OnePlus One a few days ago. Immediately after getting the phone I installed Oxygen OS on it, and used that for the first few days. Before long I realized that the proximity sensor was not functioning. I noticed this by sending email with my ear.

So, I found this thread, and tried each of the different lollipop radios available. None of them made a difference. I even tried the 44S radio (which made my wifi stop connecting and didn't help anything) and then switched back, which again, didn't help.

Finally I wiped the phone and installed the latest CM12.1 nightly. Still no luck. I've just finished taking a backup and plan now to install CM11S to see if the sensor works there, but I'm not optimistic.

Is there anything else I am missing? Anything else I can try? I installed a app called "Sensor Test" from the play store, and it shows the proximity sensor's value as 0 even when I have my hand directly over the top half of the phone. If I hold it there for a few seconds the value will jump to something between 8,000 and 10,000 but once it jumps up it never goes back down to 0 (or down at all even).

Is it possible that my hardware is actually defective, or should I keep trying to get this working?

---------- Post added at 10:03 PM ---------- Previous post was at 09:39 PM ----------

I just finished installing CM11S and my proximity sensor works! So, I'm now convinced it is NOT a hardware issue. I'm now going to restore my backup of CM12.1 and apply the correct radio and cross my fingers.
[ONE Q&A, Help & Troubleshooting] sshanky:
Minego, try the solution above (in post #50). It was what did the trick for me.