yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] ek69:
[MENTION=2332422]temasek[/MENTION] [MENTION=3814731]katinatez[/MENTION] I think I found a bug?

Enable the option "prevent accidental wake up" then Engage the proximity sensor by turning the phone screen side down on a surface (like a table), then give yourself a test call. After it starts ringing/vibrating disengage the proximity sensor by turning it over like you would pick it up to answer the phone. The phone screen never turns on like it's supposed to until you hit a button.

Or is that how it's supposed to work?? Lol :)

I thought it's just supposed to keep the screen off when a notification or email etc comes through, or something else accidentally triggers the screen to turn on, but this shouldn't happen with a phone call you would think?

Temasek 3.0

AK kernel 061

I don't remember pulling my phone out of my pocket on previous temasek versions and having to press a button to see who's calling, but I am not 100% sure on this...

If you disable the option "prevent accidental wake up" under display settings, this problem goes away. Looks like phone calls are not exempt from this option, but maybe they should be? Should I report this to CM or you guys lol I dunno

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] katinatez:
Keep all your f2fs questions in the correct thread, and be nice to your kernel dev and post last kmsg
[ONE Android Development] Synnexo:
Dark Screen / Skype (Other party unable to hear)

Hi [MENTION=3814731]katinatez[/MENTION]

I have encountered 2 things:

1. Screen does not turn on when phone ring

2. While using Skype, after a few minutes, the other party is unable to hear my voice but I can hear her loud & clear. (connection with both WiFi & mobile data have the same problem) - experience the same with previous versions.

The link will lead to my logcat http://goo.gl/KXYVsx - hope it can be of some good information to you.

I was using Mokee 44.4 with AK Kernel, things are working fine. So likely, AK kernel is working fine.

I always format data before I flash to new ROM or even updates.

For AK kernel, I'm running stock .
[ONE Android Development] R0iZ:
Yes, the same things. Clean install with wipes don't help :(
[ONE Android Development] tobitege:
That issue with the "prevent accidental wake up" has been reported multiple times already and until fully "fixed", just disable that option.
[ONE Android Development] katinatez:
Your going to love this new boot animation.

Enjoy :D

Change log: cm-12.0 V3.1

Dec. 21 2014

sync time 7:45 pm utc-7

F2FS support

Multirom support

Stock Toolchain

Stock Kernel

Updated CM source

https://github.com/temasek/android_frameworks_base/commits/cm-12.0

https://github.com/temasek/android_packages_apps_Settings/commits/cm-12.0

https://github.com/temasek/android_system_core/commits/cm-12.0

https://github.com/temasek/android_packages_apps_Bluetooth/commits/cm-12.0

https://github.com/temasek/android_vendor_cm/commits/cm-12.0
[ONE Android Development] Zorachus:
Can we dirty flash over 3.0 ?
[ONE Android Development] berdey:
always dirty flash it, and working well.
[ONE Android Development] gd6noob:
Is it normal to have mounting and unmounting issues with installing with F2FS?
[ONE Android Development] Zorachus:
Noob question. What's the best procedure for dirty flashing again please ? Been awhile, I typically clean flash always.
[ONE Android Development] Deadpool253:
It's Your rom that I'm using. it's the one that [MENTION=874961]zaph[/MENTION]obeeb has with Temasek and AK built into it. That's why I was asking if anyone had reboots with your direct builds vs his recompiled builds of your rom. I was wondering if it had anything to do with his builds of your rom or if it was a Temasek issue in a nightly. If it isn't I would've just formatted back to Ext 4 and stuck with your builds. I didn't mean any disrespect.
[ONE Android Development] stu5797:
Cool boot animation! Thanks for the nightly!
[ONE Android Development] berdey:
format cache and clean dalvik cache in advance.

then flash new rom.

Thx.
[ONE Android Development] Bronyr:
Screenbeam mini2 (from Actiontec) no longer works on lollipop. It used to be fine on kk. Any workaround?
[ONE Android Development] tobitege:
Yes, indeed, awesome!

Btw, if you'd need somebody for TWRP beta testing, especially USB-OTG and F2FS, please pm me anytime.

Currently having a lot of reboots with the MultiRom-enabled version as soon as MTP is enabled (@kantjer?), so looking forward to any enhancements in TWRP. Cheers!
[ONE Android Development] berdey:
Agree, very cool one.
[ONE Android Development] Zorachus:
Do I need to flash GAPPS again too
[ONE Android Development] katinatez:
Which version of multirom? Compiled by who?Link
[ONE Android Development] tobitege:
The ones hosted by [MENTION=3306843]kantjer[/MENTION]:

https://s.basketbuild.com/devs/kantjer/bacon/TWRP repack/TWRP MultiRom
[ONE Android Development] ek69:
No if you have the files in post #2 they will be OK

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] katinatez:
Thank you for the logs, many people mention but never provide any logs.

Non taken, if your still on f2fs try flasing stock kernel f2fs from same thread, most reboots are from kernels. But mentioning reboots dont help anybody, you have to provide logs.

Thanks, I will try to replicate your steps to see if mine reboots
[ONE Android Development] tobitege:
[MENTION=3814731]katinatez[/MENTION]: Thanks! Just wondering if it would make sense to split any TWRP development of yours into a separate thread? It would deserve the attention and distract less from your rom, imho.
[ONE Android Development] katinatez:
TWRP 2.8.3.0

https://github.com/omnirom/android_bootable_recovery/commit/f5c904b2fffa0dcb2e4fb9285ba0b097c6603ebb
[ONE Android Development] M3gAtR0N:
Man your awesome !!!! Great work with super quick updates for the rom !!
[ONE Android Development] katinatez:
Your welcome, compiling twrp 2.8.3.0 right now
[ONE Android Development] Synnexo:
I hope the logs are good for u.

I think most folks may not know how to pull the log out.

As for me, I used adb for extraction.

If u require more log extraction, just tickle me, I'm more than willing to help.
[ONE Android Development] nirmik379kale:
Does MTP work?

Does mtp work? i m not able to get it to work ( ubuntu ) ptp works though...

and wont there be ota updates? m sorry but im new to this rom...just flashed it yesterday night...

ThankYou!
[ONE Android Development] ek69:
Is this a custom version of twrp?

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] katinatez:
Yes, once I introduce features I keep them going. How many would like me to open new twrp thread?
[ONE Android Development] NikoZBK:
I think a new thread would be good :good:
[ONE Android Development] M3gAtR0N:
+1 for new TWRP thread !
[ONE Android Development] Striatum_bdr:
F2FS thread please.
[ONE Android Development] jamiescott23:
Thanks mate. I've come across some other bugs bothered me, so went back to mahdi for a while. On mahdi it's the same, %5 to %100 at 1h 45 minutes.
[ONE Android Development] ek69:
I think a new thread for your custom version of twrp would be good. I have to use the multirom modified one (even though I haven't booted my cm11s ROM in weeks thx to this ROM lol) but it would make sense if there's gonna be differences between the official regular version and your version of twrp

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] jcespi2005:
Is not recompiled, just repackaged with an adapted installation script ;)

I had a couples of reboots on 3.0 with AK 0.61. Now i'm on 3.0 with Ty55 kernel, and no problem for now... seems a good combination.
[ONE Android Development] Criton30:
+1 for new thread! [emoji106]

Sent from OnePlus One via Tapatalk
[ONE Android Development] katinatez:
Ok twrp 2.8.3.0 done all the same features that I introduced as the Unofficial TWRP just going to send this to beta testers before uploading to the masses. MTP is working USB-OTG, F2FS, EFS/Persist, Theme

And has not rebooted on me yet, but need beta testers to confirm also.
[ONE Android Development] jcespi2005:
Im on F2FS and use MTP and OTG for flashing also, if you need one more tester ;)
[ONE Android Development] fabiienb:
Hi hello, first I would like to say is is the best lolipop rom i tested at the moment but how I can have navigation ring?

Any chance to dark ui?

ONEPLUS ONE SLIMSABERKAT BOEFFLA-KERNEL LATEST
[ONE Android Development] kecinzer:
Hmm, it's not completly fixed. Sometimes buttons staying on.
[ONE Android Development] solar666:
Not for me. Never again
[ONE Android Development] gulp79:
It will have MultiRom commits? ;)
[ONE Android Development] jcespi2005:
Should be good to have all the things in on TWRP version ;) The EFS backup part is missing on multiROM branch ...
[ONE Android Development] nicksmizzle:
do you currently have testers or are you looking? if so, i am glad to help.
[ONE Android Development] Eef:
My alarm wakelocks are finally gone but now after some sleep with nothing running I have this wakelock, does someone knows how it comes? Something with mediaserver and audio offload. Many thanks
[ONE Android Development] Almayce:
That's when you listen to something on your phone. Songs, movies etc fall in this category to name a few :) that's not really a wakelock. At least in my experience.
[ONE Android Development] Eef:
Yes I understand but the thing is that I unplugged my phone couple of minutes before going to bed and never listened to anything and also greenefied everything.
[ONE Android Development] CounterC:
Go to settings - storage and disable media scanner behaviour on boot, then reboot.
[ONE Android Development] jcespi2005:
Prefer the previous one ;) But looks good...

THANKS
[ONE Android Development] Fabioo123:
+1 :)
[ONE Android Development] davibs:
Mistake.

My Microphone is not working on call.

Can anyone help?
[ONE Android Development] gnan10:
Does this rom supports f2fs file system?
[ONE Android Development] foomanjackel:
there is a seperate thread for that:

http://xdaforums.com/oneplus-one/development/rom-5-temasek-unofficial-ak-f2fs-t2963619
[ONE Android Development] Deadpool253:
I didn't flash any kernels. Just his repackage of your rom. He bundles in AK versus the stock kernel you do. I poked around and updated to AK 65 Skull and that seems to have fixed the issue. Again I wasn't implying there was anything wrong with your rom, I just wanted to know how this one without AK was running. It's my fault for not communicating better. Sorry about that.
[ONE Android Development] lordneopt:
Remove all your media from the phone.

Android has a bug with corrupted previews since ever. I'm surprised they didn't take the time to fix that.

99% of the mediaserver high battery consumption when idle is due to that.
[ONE Android Development] Synnexo:
Hi [MENTION=3814731]katinatez[/MENTION],

The dark screen issue seem to have been "activated" when I select long press Home button to turn off screen.

It was fine when set at default, but after the change, the bug is alive & stay on.

Hope the logcat is of good use to u: http://goo.gl/4uZC2J
[ONE Android Development] mak725:
Still does not work recording video in 4K?
[ONE Android Development] wajahebat:
Turn Off mediascanner at boot, you can change that in Settings if Temasek made it available.
[ONE Android Development] wishmaker738:
seems like all the download servers are down
[ONE Android Development] Eef:
Thank you will also try that. Do I need to wipe the whole internal storage or only the audio and images? And if ive done that do I still need to disable media scanning on boot?
[ONE Android Development] lordneopt:
Doesn't solve the problem because the corrupted preview is still there.

You can even kill the service that it keeps draining battery.

No, you do not need to stop the media scan.

Just delete everything media related. If images and audio doesn't solve it wipe everything. However with me just images and audio are enough.
[ONE Android Development] wajahebat:
What do you mean by corrupted preview
[ONE Android Development] lordneopt:
Android generates a preview for every media file it can find. It's a preview. I don't know what else to say.

If that file is corrupted the Android goes berserk and instead of skip it does the opposite.

It's a bug Android had since ever, I remember building 2.x ROMs and it was already a pain on the micta for those who had lots of media on the SD.
[ONE Android Development] jcespi2005:
What about this

http://www.addictivetips.com/mobile...ectory-from-being-scanned-by-android-gallery/

Could help?
[ONE Android Development] lordneopt:
Don't know about that to stop the first scan.

But if you have the draining problem stopping the rescan won't do much. Will keep draining more battery than it should.
[ONE Android Development] wajahebat:
If it works like what you say and i believe the fundamentals in what youre saying. But in my opinion its not due to the corrupted preview, instead it was due to the corrupted media itself.

This happens on mine during my S4 time, where i have a corrupted wallpaper JPG in my collection due to disturbed copy process, and the same happen to my OnePlus where my MP3 files is corrupted, and the mediascanner is not stopping after half an hour reboot. After replace all the media carefully, the mediascanner problem is gone.

What im saying is, its not the android bugs, but the media. Its good to double checked your media files.
[ONE Android Development] lordneopt:
You can have all files working nice (images, audio, video) and still have the media scanner bug due to the internal corruption.

Its not "file" corruption, its android berserking.
[ONE Android Development] wajahebat:
And why i dont have that mediascanner running right now? And others too
[ONE Android Development] azsl1326:
I am running F2FS file system. Can I flash this directly or do I need to make some sort of change to the ROM.

Thanks!
[ONE Android Development] M3gAtR0N:
Refer this :-

http://xdaforums.com/oneplus-one/development/rom-5-temasek-unofficial-ak-f2fs-t2963619
[ONE Android Development] kecinzer:
[MENTION=3814731]katinatez[/MENTION] [MENTION=2332422]temasek[/MENTION]

I did little test with incoming calls and found those 2 bugs:

1) When I have phone with display turned off on the table and someone calls me, display normaly turned on, but I can't see contact's photo.

2) When I have turned on proximity check on wake and somene calls me when I have phone on pocket, phone ringing but don't turn on - I have to turn it on maunaly.

Ad 1 - I think this have something to do with temasek mods - in pure CM12 it works fine.

As 2 - This is CM bug I think, It happend for me also on pure CM12.

Anyways, can you guys check those things, if you can find how to fix it?

EDIT: I mentioned, if I have enebaled proximity check, I can't turn on 1+1 by classic power button - that was possible definetely possible in CM11. I think it's related.

In actual version with proximity check enabled simplay anything can turn on device if it's in pocket :).
[ONE Android Development] katinatez:
Which commits are you talking about?
[ONE Android Development] Spaulding89:
I'm very happy when next build arrives. I see dark ui commits on Temaseks GitHub [emoji2] [emoji106]

Sent from my Bacon with loaded AK Kernel
[ONE Android Development] ghul21:
Please no dark ui :( why we always make our roms inversely to what we have in the stock? Since ICS we have a dark ui, now when we have bright, beautiful interface we want back to black :( can't understand that....

Dark ui should be an option like trds or separate theme....

Why cyanogenmod have a white ui ? Because they want to be close to stock (but with steroids;) )

Wysłane z mojego HTC One_M8 przy użyciu Tapatalka
[ONE Android Development] gulp79:
ops sorry, Multirom support....
[ONE Android Development] HaTrED_:
Where can i see that proximity check settings? :confused:
[ONE Android Development] LeroViten:
[MENTION=3630491]ghul21[/MENTION] Ah, that's quite a dummy topic. Personally, I prefer dark holo minimalistic style and many colors are making me sick. But that doesn't mean devs should care about that. The best option is really trds thing that allows different people with various tastes have their own choice in a ROM. ;)
[ONE Android Development] fjsferreira:
Huh, where are those? I don't see anything...
[ONE Android Development] temasek:
I'll check (1)
[ONE Android Development] NOSTALGIA:
you shud also sleep
[ONE Android Development] fjsferreira:
I can confirm the same bug, been happening since 3 or 4 versions ago.
[ONE Android Development] Spaulding89:
Here my friend

https://github.com/temasek/android_frameworks_base/commit/48dad1afdd5614b30d60fad0991779a4271861c3

Sent from my Bacon with loaded AK Kernel
[ONE Android Development] LeroViten:
What about THIS ONE .? ;)
[ONE Android Development] temasek:
Can u remember which version build was the last one working?
[ONE Android Development] LeroViten:
Those two annoyances happen to me on LS ROM either. So this can be sources related stuff. ;)
[ONE Android Development] hunter0389:
I agree. It happens with other CM12 rom. Contact pic has been a hit n miss for me. Sometimes, it has pic and other times not. Annoying but I can live with it. At least the contact name and number still display correctly. So, I know who is calling.
[ONE Android Development] foomanjackel:
I myself would LOVE to see dark ui on this ROM :good:

Certainly not a deal breaker by any means, I'll stick with it regardless....but I do prefer the darkness. :)

Thanks to temasek, katinetez and ak for all your great efforts. You guys are the best. :D
[ONE Android Development] almaximo:
me too, same issue on (1)
[ONE Android Development] gianton:
Strange cause I don't have these bugs.
[ONE Android Development] almaximo:
Hi [MENTION=3814731]katinatez[/MENTION]

I've seen you were talking about TWRP 2.8.3.0 unofficial, probably modified and compiled by you, I supppose

I'm using 2.8.2.0 always from you without any issues

which new features have you implemented in new version ?
[ONE Android Development] ghul21:
Yes bit Dummy..... I've try some dark theme roms. They look nice but...... But look at the colors... In stock we have a really nice contrast. Everything is clear. On dark theme when we change tha background and leave the icons stock green contrast is near to zero.

When the sun shines only thing we can see is a gray stain..

But that is my personal opinion ;)

Sent from my A0001
[ONE Android Development] temasek:
I don't have it too.
[ONE Android Development] rutgerhoorn:
V150 running great! Thanks! Only thing i don't get is that my statusbar on my lockscreen is solid black.
[ONE Android Development] chris264:
Good evening, which recommends her recovery? TWRP or Philz_touch? Nice greetings

Gesendet von meinem Oneplus One
[ONE Android Development] fahadali2315:
:) Its a user preference . both are great recoveries. Twrp is used often on this device as i have seen.
[ONE Android Development] katinatez:
Personally I roll with Philz recovery because I use most of the features. And most people probably don't know but you could backup and restore in both twrp and cwm formats, so if you go back to twrp you already have backups to restore.
[ONE Android Development] Freddy1X:
The latest version doesn't work with Spotify + Viper4Android. If I used other music players such as Google Play Music, the Driver Status will show Processing: Yes. But when I use Spotify, it will show No. Because I am a heavy user of Spotify unfortunately I have to revert to 146. :(
[ONE Android Development] EasyGoingXD:
Also there is a problem with the LED as a guy said before, did a clean install but sometimes the notifications light stays on and i found a second problem..sometimes the notifications in the status bar stays if i already viewed it in the app, might be an CM problem
[ONE Android Development] habnzrot:
Thanks for this great ROM! It's been a day since I install v150 (stock cm11 Temasek) and everything is so far running solid... Spotify and led light working...a happy camper here:)
[ONE Android Development] katinatez:
Here is another update V150.2 The last build 150 I changed to temasek toolchain 4.8 which uses Justarchi's Archidroid optimizations; you could read about v150 here.

https://github.com/temasek/android_build/commit/eb2aab3e0fb99542a6cf67aa5622e933807d86df

V150.2 is all SaberMod 4.8.4 Rom & Kernel you could read here.

https://github.com/UBERUTILS/arm-linux-androideabi-4.8

Enjoy :D
[ONE Android Development] nikzDHD:
Giving this rom a spin and I like it. Has all the features I use frequently and it's smooth on v150. New version sounds even good ?
[ONE Android Development] rutgerhoorn:
I noticed this has something to do with the c11 to c11s.zip. When i flashed it after i updated to 150.2, wich is running great again btw, my statusbar became solid black again. Could you take a look at this [MENTION=3814731]katinatez[/MENTION] ? Thanks!
[ONE Android Development] nikzDHD:
v150.2 is flying...
[ONE Android Development] habnzrot:
Indeed, this is a turbocharged v150! Everything is running smooth and rock solid.
[ONE Android Development] tmcpnet:
I have the same issue....
[ONE Android Development] katinatez:
OK I have been running a black theme so I changed my wallpaper to see what you are saying but the screenshot helped. This is not a Rom bug it has to do with the CMKeyguard.apk from Oneplus One 38r! Solution dont flash the CMKeyguard.apk zip

I have to spend time on this one, have to decompile apk and change values or add values when I get free time, or if anyone wants to help and do that I am OK with that too.

On another note V150.2 was a test build! I have V151 coming in a couple of hours.

Quote Temasek;

Build V151

- Built with self-compiled SaberMod 4.8.4 toolchain dated 20141016 for ROM & Kernel

- Hover master switch is in. Thanks to Cristiano Matos

- Updated cm sources
[ONE Android Development] tmcpnet:
Thanks, just finished setting up my phone with 150.2, Can i dirty flash 151?
[ONE Android Development] m-law:
I've been running build 150 for the last couple of days and it's been fantastic, no bugs (that I could find), super smooth and has all the features I need! Up till now I was jumping from rom to rom but I think I'm going to stay on temasek:)

btw [MENTION=3814731]katinatez[/MENTION], is there a way to open omni switch by long pressing the home button? I could do that on heisenberg rom but I can't find a way of doing this here.
[ONE Android Development] katinatez:
Yes just dirty flash

I dont believe so, but you could use pie settings.

V151 is up :D

Seems you could use the cm11 to cm11s based off 25r will fix the black status bar!
[ONE Android Development] Setting.Out:
Is justarchi on both, or is this to test the validity of the optimisations?
[ONE Android Development] Freddy1X:
Viper4Android still not working with Spotify..
[ONE Android Development] rutgerhoorn:
Great!
[ONE Android Development] Spaulding89:
But at night the white background burns in eyes. I hope the dark theme will be toggled so we can choose. For daytime bright for nighttime dark. That is my personal wish.

Sent from my Bacon with loaded AK Kernel
[ONE Android Development] temasek:
Best is to wait for TRDS or any similar feature with toggleable switch. So both black and white wins.
[ONE Android Development] Spaulding89:
Exactly what I mean :)

Sent from my Bacon with loaded AK Kernel
[ONE Android Development] temasek:
Lol

I quoted the wrong post.

LMAO :)
[ONE Android Development] ghul21:
That's what I wrote in first place :)

Sent from my A0001
[ONE Android Development] Beaster:
Was about to report the same bug..

The 1st doesnt always happen. For example if i receive 2 calls in a close time frame,the first wont show a picture and the 2nd one will...

I didnt have this bug on pure cm 12 built on 15 / 12 if this helps..

Thx in advance!
[ONE Android Development] davibs:
It's my urbeats or ma headphone not working?
[ONE Android Development] kecinzer:
That's strange. This bug has also my friend with Sony Xperia Z (yuga) - I'm also compiling for this device.

I can confirm that it's don't happend all the time. Sometimes it worked sometimes not.
[ONE Android Development] temasek:
I'll do more tests tomorrow.