yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Crazy-Silver:
On 4.2 having proximity sensor issues. I use also AK 0.76
[ONE Android Development] :
didnt think it get any smoother, but the sm version tweaked and settled in half a day is as smooth. Could be placebo lol
[ONE Android Development] NikoZBK:
On the new modem, I broke data by switching from 3G to LTE and had to flash back the 44S modem. Just a heads up. (AT&T)
[ONE Android Development] slave2007:
Me too, twrp starts and stops a so on .Back to 4.0
[ONE Android Development] störte:
Which TWRP ? Official or unofficial ?

Had the problem and solve it to flash official TWRP 2.8.3
[ONE Android Development] raybit10:
I haven't seen anyone else writes about it but,

did anyone noticed "Root Access" in Developer Options is Disabled (I am after a clean flash of v4.2 sm + Boeffla alpha11 I474)?

just curious... it was always enabled after a clean flash, right?
[ONE Android Development] Striatum_bdr:
Yes it was OFF for me too, had to switch it.
[ONE Android Development] Spaulding89:
Yes but so far as I know CM changes this in CM12 and so it will be disabled here too . Or Katinatez or temasek must change this. But it is no big thing for me.

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Android Development] raybit10:
oh, didn't knew it was CM new setting... good to know, thanks!

Not a big thing for me too ;) as I always go over all settings after each update flash.

One last question...

what is the "Show unaccounted/overcounted stats" in Developer Options?
[ONE Android Development] TheQuarterMile:
Isn't this the new Alpha radio?
[ONE Android Development] neles86:
This is not a ROM issue. Its an issue with chrome beta.

---------- Post added at 12:03 PM ---------- Previous post was at 11:48 AM ----------

Hey any way to fix the fc when composing new email in gmail. Also, can't get chrome to work.

NVM..clean flashed and all is good! :)
[ONE Android Development] folken:
I don't know why but i have random reboot several times. I tried to install the ROM with twrp and philz same thing, slim gapps or pa gapps same.
[ONE Android Development] drdrewdown:
recovery shouldn't matter, gapps probably doesn't either. provide a log or last_kmsg if you want help/get it fixed.
[ONE Android Development] cerealguy:
Gradient locksreen in Misc folder on Androidfilehost, works on last build? :D

EDIT: flashed and it works like a charm! Great rom!
[ONE Android Development] katinatez:
Do a full wipe then flash ROM,gapps. I don't have any reboots.

Also when reporting bugs; catlog or it didn't happen.
[ONE Android Development] kpearly:
New gapps are great. How can I restore the default lockscreen and keep all the others?
[ONE Android Development] katinatez:
Open zip with 7-zip go here

/META-INF/com/google/android/updater-script/ and remove any of the aosp apps you want to keep; For aosp keyguard remove this line

delete("/system/priv-app/Keyguard.apk");

also remove this line

delete("/system/app/LatinIME.apk");

I found a bug on Google Keyboard v5 it FC when going into landscape, by editing this line you will keep aosp keyboard.

Also go to system/addon.d/82-full_gapps.sh/remove this line rm -f /system/pri-app/Keyguard.apk and rm -f /system/app/LatinIME.apk

These lines are removed because it will delete the apps when you flash another temasek update.
[ONE Android Development] katinatez:
Twitter

temasek [MENTION=2332422]temasek[/MENTION]71 · 48m 48 minutes ago

My hdd died on me. I will be out of action until further notice.

Will update tomorrow to fix panorama mode in CameraNext.apk and also have AdAway.apk this will be the last update until temasek is back up and running.
[ONE Android Development] OberstGrausam:
I'm also using adaway and it's really working great. [MENTION=2332422]temasek[/MENTION], do you plan to include paranoid androids dsb in your rom, since it's open source now? I'm not asking for an eta, I just want to know where it might be included in the future. Thanks.
[ONE Android Development] temasek:
It's up & running (for now).

V153 is ready for your building.
[ONE Android Development] Schrotty35:
What is new on gapps? I use pa gapps and i dont see new version.
[ONE Android Development] katinatez:
I made a new slim gapps found in the misc folder read a few post back.
[ONE Android Development] katinatez:
Change log: V153

Add support for single color notification LED

Implement Dynamic System Bars (switch OFF if you notice any lag whatsoever).

Add navbar search button into DSB & Add left and right navbar virtual buttons into DSB (thanks [MENTION=4478519]Cristiano Matos[/MENTION])

Camera2: fix camera has stopped" after long press camera key

Camera2: Fix crash on cameras with 6mp 16:9 resolution

Lots of system UI fixes (refer to Github https://github.com/temasek/android_frameworks_base/commits/cm-11.0 for more info)

Fix panorama mode in CameraNext

added AdAway 2.9.2

added AOSP Camera, & Gallery back

AK.068.GOLD.OPO.CM11
[ONE Android Development] Freddy1X:
ROM is super smooth.. If I ever want extra features that is only the ability to change icons system colors (like battery, bluetooth, WiFi, signal, etc..).
[ONE Android Development] OberstGrausam:
Thanks for all your hard work katinatez. Donation 7SF061580Y420703P
[ONE Android Development] fjsferreira:
For some reason, the new dynamic system bars, can't select navigation bar, only status... It selected fine at first, but then it's not working after a reboot.

Also, Calendar v5 doesn't show up as installed with the slim modified gapps.
[ONE Android Development] g_Four:
I got fc in quick setting. Anyone get the same problem? Or just me?
[ONE Android Development] anupsnair:
Caller screen

Hi Team,

For some reason the caller screen is sent to the background, everytime I get a call I see an Icon on the notification bar, and phone vibrates if I pull down the notification bar I can see the call, and clicking on it, will bring it to the foreground. The caller screen doesnt appear without clicking on it

I have tried a full wipe and clearing the data from the dialer.

Is there any fix for this ?
[ONE Android Development] CWick4141:
They work fine for me with a clean flash
[ONE Android Development] furrycurry:
Is there a way to use software keys only? After enabling them, software keys still vibrate and use.
[ONE Android Development] störte:
It is the new modem
[ONE Android Development] slave2007:
I think, it´s official from twrp site :http://teamw.in/project/twrp2/231
[ONE Android Development] tobitege:
I thought it was mentioned earlier, but I think all root access will go into Privacy Guard to be configured for each individual app and SuperSU (as default?) won't be accessible anymore. That's what I understood about it thus far.
[ONE Android Development] TheQuarterMile:
Then why is the proximity sensor messed up for me?
[ONE Android Development] bundysoat:
In v4.2 on Settings I can see Two clients off Root access.....What should I do?

EDIT: Ok, after update binaries, Superuser dissapeared.

I love it can to reorder and eliminate quick settings acces on notifications, but PLEASE, add more acces to include in this settings. I pray that this can be done real.
[ONE Android Development] disellusional:
same, lost all radio connection
[ONE Android Development] phierce:
Wow what a disaster this has turned into I'll stay on 4.0 till this mess gets sorted
[ONE Android Development] ghul21:
Hehe are some gerrits on slim to fix proximity speaker. I think they should be handy. New modem is a mess.... like whole lollipop alpha....

https://gerrit.slimroms.net/#/c/22230/

https://gerrit.slimroms.net/#/c/22231/

https://gerrit.slimroms.net/#/c/22232/

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] TheQuarterMile:
lol yah that would be a wise thing to do I wish I hadn't rushed to flash 4.2!
[ONE Android Development] zagzag99:
Try wiping system before flashing ROM and gapps.

I don't seem to have issues with proximity on 4.2 with new modem.
[ONE Android Development] TheQuarterMile:
I did a clean flash only..
[ONE Android Development] chindynasty:
Yes. Discussed couple pages back. Lost mine as well. Use toolbox and reflash twrp under fastmode. It should stick.
[ONE Android Development] ek69:
Your build shows you're on 4.0 still in the screenshot, flash the new 4.2 ROM it should be OK after that ;)

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] TheQuarterMile:
*facepalm* I must have selected the wrong zip in TWRP ?
[ONE Android Development] ak:
latest rom v4.2 + L5 modem + ak v.077 = no problem so far.

thanks a lot devs.

ak
[ONE Android Development] hunter0389:
Did anyone else notice Ambient display lights up without notification? On the lockscreen, double tap to sleep, and the ambient display will light up for a couple of second. Also, it will light up randomly without notification. Not sure if this is a "feature" or a "bug".
[ONE Android Development] keen36:
i had a random reboot a few hours ago. i used sabermod compiled temasek 4.2, ak kernel 76, ukm 3.6.1.1, the new radio from this thread and supersu beta 2.43 on a clean flash as secondary rom (i am running multirom). this could very well be a multirom-related problem, i just wanted to mention it in case i am not the only one.
[ONE Android Development] ak:
Ambient display on? if yes please update the kernel to v.077.
[ONE Android Development] dy2592:
Sorry but this new 4.2 update has got me so confused. I usually just update through twrp but now I have to install a new modem separately?
[ONE Android Development] stu5797:
And there are now 2 different versions which I have no idea what truly differentiates the 2 versions
[ONE Android Development] Striatum_bdr:
They are the same, just compiled using different tools, sabermod is supposed to optimize the code to make is faster to execute. But same Rom exactly.
[ONE Android Development] StimpyMGS:
I had random reboots after flashing ak kernel. When I returned to stock kernel by flashing 4.2 zip again all problems were gone!
[ONE Android Development] raycaster3:
Edited to remove jerky comment:

Reporting random reboots for those not using the stock kernel (in this thread) will not get answers. It's the kernel (or kernel settings) that is causing your problem, not ROM related.

Report in ak kernel thread for support.

Once again my apologies to [MENTION=3685904]ak[/MENTION] for unnecessary comment.
[ONE Android Development] ak:
I think you guys should stop talking about kernel here, and try to bring back the real problems in the right places.

I also believe it would be better to refrain in making judgments free.

wasted energy without giving any contribution.
[ONE Android Development] raycaster3:
You are right. I meant no disrespect. Please accept my apologies.
[ONE Android Development] jl2222:
Recommended vs stock?
[ONE Android Development] stu5797:
Anyone find that it's double tap to wake is harder to turn on than it used to be
[ONE Android Development] ak:
you have to do a fast 2 tap on the screen, its related to the new tp firmware.
[ONE Android Development] hunter0389:
Not really. Feels about the same.
[ONE Android Development] stu5797:
Thanks ak! It definitely needs that faster double tap and then it turns on perfectly
[ONE Android Development] keen36:
will do! the reboot occured after a day of usage and while i was in the subway (which only has 2g network), i have no idea how to reproduce it at will, so i will have to wait and see.

yeah, as i said, it could also be a multirom problem. concerning ak kernel: i thought that temasek's rom and ak kernel were supposed to be highly compatible? i remember reading "a match made in heaven" somewhere.

why is ak kernel unstable? i do not change voltage or overclock/underlock and i do not use the added 267mhz step.

edit:

i just read the recent posts, i will refrain from posting about the kernel here. i just was not sure whether it is a kernel problem, a rom problem or whatever problem when i made the post!
[ONE Android Development] silvagroup:
FYI - Using 4.0 in multirom as secondary ROM for me see no problems very smooth great battery no problems, using stock as primary. Hardly ever in primary should probably swap them. But why mess with success.
[ONE Android Development] TJ_bab:
Is v4.2 out?

Why no post from op?
[ONE Android Development] fjsferreira:
It's in katinatez androidfilehost folder.
[ONE Android Development] solar666:
Post #4068?
[ONE Android Development] raybit10:
+1 lol (before you edited ;) )

For all of you interested in knowing a bit about Sabermod -

Originally posted in ZaneZam thread here

(make your own conclusions about which toolchain is "better")
[ONE Android Development] fischwrap:
I'm getting system ui crashes when trying to pull down the notification bar. This is what I did:

Dirty flash 4.2sm over 3.9

Flash new alpha modem

Got sys ui crashes... So...

Clean flash (wipe data sys cache n dalvik) 4.2sm

Flash boeffla kernel

Flash gapps

Still getting the crashes with notification pulldown. Could it be kernel?
[ONE Android Development] raybit10:
I did the same except flashing gapps before kernel and everything is great here.
[ONE Android Development] katinatez:
Thanks will post this on post 2!
[ONE Android Development] katinatez:
I am going to run a test build with these commits
[ONE Android Development] fischwrap:
Weird. I'll just stick with stock builds for now I guess
[ONE Android Development] temasek:
It's already ported over before your post.

Will be in next build.
[ONE Android Development] katinatez:
Already merged with cm? If it is I will build again to end the whole modem fiasco.
[ONE Android Development] Deadpool253:
Anyone have a link to the old modem? I'm having issues with the new one.

---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------

Can I just flash the camera in the misc folder and Viper audio zip or should I uninstall DSP and the camera from the rom first?
[ONE Android Development] raybit10:
Did I just got a :good: Thanks! From Katinatez?!?

yeahhhhhh ;)

(No problem mate)
[ONE Android Development] scott62185:
This
[ONE Android Development] phierce:
So does mean I can still use original modem as always if so you rock dont like messing with modems especially when I have no issues with current stock modem. Love this ROM !
[ONE Android Development] katinatez:
Yes, just sat down on computer checking to see if those commits have been merged, if so going to compile as soon as [MENTION=2332422]temasek[/MENTION] stops adding commits.
[ONE Android Development] kipue:
Hey, this is it

http://xdaforums.com/showpost.php?p=57125376&postcount=389

(this thread for info : http://xdaforums.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734)

Thanks to the people putting it up there in the first place :)

This seems to be a modem with good comments, haven't tried it yet, but will when the new rom build will appear.
[ONE Android Development] ek69:
http://xdaforums.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734

There is all the modems from cm11s flashable zips in that thread :)

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] temasek:
???

Ported over from Slimrom to my sources. If u sync from mine it's in.

---------- Post added at 08:54 AM ---------- Previous post was at 08:53 AM ----------

Lol

Ok I stop. U go compile.
[ONE Android Development] katinatez:
Thanks will compile v4.3 with another clobber, will be about 1 1/2 hour
[ONE Android Development] hunter0389:
I am limited to 8 thanks a day. Grr.... haha...

Anyways, just want to thank you for the post. It will be very handy if we need to go back to an older modem.
[ONE Android Development] mak725:
V4.2 very very fast and soft!! [MENTION=3814731]katinatez[/MENTION] and [MENTION=2332422]temasek[/MENTION] great work!!

Antutu Score:
[ONE Android Development] kipue:
You're welcome :)

Alpha modem is not much of a problem in practicality for me, but I don't like such an important part of my phone to be tagged "alpha" so I was prepared too :D
[ONE Android Development] ArmorD:
Edit. wrong thread
[ONE Android Development] katinatez:
Well Thank's [MENTION=2332422]temasek[/MENTION] we are out of the whole alpha modem fiasco, These commits posted below let us keep the current modem no alpha modem flashing is necessary. If you already done that just flash back cm11s modem that are already posted in thread. I have personally flashed both stock & Sabermod and both running good. Customization Quick Settings is a very nice feature to have.

I also removed v4.2 from downloads, and added files into Misc folder LolliViper.zip is android4viper but for lollipop, added SuperSU_2.43

Already in Android File Host, come and get it!

https://gerrit.slimroms.net/#/c/22230/

https://gerrit.slimroms.net/#/c/22231/

https://gerrit.slimroms.net/#/c/22232/

Change log: cm-12.0 V4.3

Jan. 4 2015

sync time 6:30 pm utc-7

Stock Toolcahin &

SaberMod Graphite 4.8 & 4.9

F2FS support

Multirom support

Stock Kernel

Updated CM source

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

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

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

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

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

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

https://github.com/temasek/android_packages_apps_Settings/commits/cm-12.0
[ONE Android Development] temasek:
I didn't change any part of rom to use other toolchain. I'm still on stock cm12 toolchain. :p
[ONE Android Development] katinatez:
Did you remove this commit?

https://github.com/temasek/manifests/commit/2a78339a136017aeb0c07ba7424de069346b94ea
[ONE Android Development] temasek:
In my local yes removed.

You don't need to use my manifest repo. Ignore it.

I actually intend to use linaro 4.9 in future but the libart is a headache. It breaks.
[ONE Android Development] katinatez:
OK made a mistake, I will edit the changelog.
[ONE Android Development] jukiewalsh:
So does that mean ours aren't on linaro?
[ONE Android Development] hunter0389:
Flashed V4.3 Sabermod over V4.2. Looks like the new alpha modem works with V4.3. I didn't have to flash the "old" modem. Proximity sensor works.
[ONE Android Development] eunique:
I tried out that alpha modem and my OPO would not wake. I would have to reboot to see the screen. Reverted back to old modem.

Just downloaded v4.3 will report back.

Thanks [MENTION=3814731]katinatez[/MENTION] and [MENTION=2332422]temasek[/MENTION] for all your hard work
[ONE Android Development] StimpyMGS:
I'm sorry but looking back at my comment I see a perfectly objective observation about a ROM+kernel related problem which people who are experiencing the same problem could make use of. No need to take it personal ;)

anyhow, I'll stop talking about anything in this topic when I have your kernel installed to prevent cases of butthurt, and will only talk when I have stock kernel installed. Like now for instance. Uptime=14hrs and no random reboots :) will try 077 later today
[ONE Android Development] Striatum_bdr:
So far so good no problem with old modem and 4.3. I cleaned SuperSu from within the app before flashing the Rom to be sure no survival script would interfere.
[ONE Android Development] j1po:
I just flashed manually all bin and mbn files in CM11S v44 including NON-HLOS.bin

then I flashed Temasek sm 4.3

my proximity always detect near (0 cm)

I tried CM11s 44 flashable zip radio few pages back, still detect near only

then I tried flash alpha modem, works fine

what am I missing here ? thanks
[ONE Android Development] Genericxx:
Flashed v4.2 yesterday with Alpha Modem. So far no problems. Proximity seems to work fine. Abseloutely clean flashed this one.
[ONE Android Development] nirmik379kale:
No Permissions on adb??

I installed 4.0 ( didnt go for 4.2 coz of all the modem thig ) ... and i cannot get adb to work when the phone is in mtp mode... it only works in ptp mode.

using Ubuntu.

also added the udev rules... still no luck.

tried with sudo also... why so? any idea?

wiped 3.3.1 ( system, data, cache, dalvik cache )

flashed 4.0

flashed superSU
[ONE Android Development] fedecape:
I'm on 3.9 and everything is working fine. I also have stock 11S modem.

I understand that all the issues are fixed with 4.3, and I can simply dirty flash it on top of what I have. Is this correct? Also, what are the new things/advantages of this "SM" release? Thanks!
[ONE Android Development] truth77:
I would love to see this rom built with linaro!
[ONE Android Development] katinatez:
Adb working here but I am running Arch Linux

v4.3 modem flashing not necessary all fixed, read post 2 about Sabermod Graphite.
[ONE Android Development] Zekene:
Im on 4.0 right know. Can i flash 4.3 sabermod over it? Whit cache and dalvik wipe
[ONE Android Development] acuicultor:
Proximity sensor still borked with 44s modem on 4.3
[ONE Android Development] raybit10:
Thank you temasek for the new "clear all recents" button (I was waiting for it to go to bottom right).

I flashed the cm11

nightly

"old" modem and everything working great.

Was I supposed to flash the cm11s modem instead? Is there any difference between them?

Edit: By the way...what is your method of checking functionality of proximity sensor?
[ONE Android Development] Striatum_bdr:
Yes if you flashed the alpha modem it also flashed static_nvbk.bin file.

You have to revert this file to xnph44s version, with fastboot. Grab the file from a fastboot flashable xnph44s archive and in fastboot mode flash it with

fastboot flash oppostanvbk static_nvbk.bin

At least it worked for me, just flashing old modem didn't do the trick alone for proximity sensor.
[ONE Android Development] Deadpool253:
The camera you have in your misc folder gets cannot connect to camera error when I flash it. Is it not compatible with these builds or am I don't something wrong? I've deleted stock camera with TB and even tried installing it over the stock one... Halp
[ONE Android Development] solar666:
Can you post your static_nvbk.bin you flashed?

In that case I can provide a flashable zip for others.

Thanks
[ONE Android Development] Striatum_bdr:
Faster for you to grab it from a 44s fastboot archive as I'm away from my computer for the day now. I grabbed it here on xda.
[ONE Android Development] j1po:
still not work with sm-4.3. i tried with wipe system data cache dalvik

i extracted from cm-11.0-XNPH44S-bacon-signed-fastboot.zip

I dirty flashed temasek v4.0, proximity working fine
[ONE Android Development] feed3:
Proximity broke for me too...

Tried 44S modem and static_nvbk.bin,

tried the cm11 nightlies modem and static_nvbk too on top of 4.3,

tried the stock and SM version,

tried clean flash and dirty flash,

all to broken proximity.

Will try few things more and report back here..
[ONE Android Development] kipue:
Same result as you.

Flashed alpha modem yesterday, then reverted to 11s modem and 4.0

Fastboot flashed that little extra file too but screen will turn off when in call and won't turn back on on 4.3.

Some things worked though. For example, on 11s modem+4.2 I would not get double tap to wake/sleep, now it works on 4.3 with same modem.

So something changed in that respect, but maybe not all fixed :)
[ONE Android Development] gianton:
New alpha modem works a lot better for my area and provider with v4.2. I get faster LTE speeds, more stable signal and have no static noise on my BT device.

I'll stick to this modem for now.
[ONE Android Development] shrayv:
Flashed 4.3 saber build, proximity sensor still broken. Reverted back to CM 11S.

Cheers