yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zzpianoman:
apns-conf.xml is located in /system/etc. Push from your computer to /sdcard/apns-conf.xml.

# mount -o remount,rw /system
# cp /system/etc/apns-conf.xml /system/etc/apns-conf.xml.bak
# cp /sdcard/apns-conf.xml /system/etc/apns-conf.xml
# rm /data/data/com.android.providers.telephony/databases/telephony.db
# reboot
[Samsung Galaxy Nexus] foosion:
A # just appeared on the top row of my home screen, next to the wifi icon. What does it mean?

I've never seen it before. Is it a CM thing (I'm on the latest build)?
[Samsung Galaxy Nexus] zzpianoman:
Root. It appears whenever an app (or system process, ugh) is requesting root access. This changed when superuser control was moved to AppOps.

EDIT: You can get rid of it by reverting this commit, but there should be an easier way. Hopefully they will bring this option to userspace so that the notification can be disabled because for people who use background apps that require root access (i.e. navigation bar replacements) the # symbol is present literally ALL the time and it can get quite annoying.
[Samsung Galaxy Nexus] musical_chairs:
Want calib files from a toro and a toroplus?
[Samsung Galaxy Nexus] foosion:
Is there a way to figure out what app or process is requesting root access?
[Samsung Galaxy Nexus] Ziyan:
Thanks guys, that's enough calibration files, I'll try to release a new build with this stuff tomorrow :)
[Samsung Galaxy Nexus] zzpianoman:
If you open AppOps under Privacy options, select "advanced" and swipe over to "Root Access" it will show you what app is currently requesting root.
[Samsung Galaxy Nexus] diogofd8:
guys.

20/01 CM12 + PA Pico Gapps + LP R6 Kernel (bsmitty) is freezing on bootanimation at the first boot. I'm using ext4 for System but f2fs for Data and Cache. Should it be alright or it is a known problem?

I've downloaded the zips 10 minutes ago so everything is with the latest release.
[Samsung Galaxy Nexus] zzpianoman:
If anyone wants to play around with multi-user mode, add these lines to build.prop:

fw.max_users=5
fw.show_multiuserui=1

Be warned though that it is verrrry sllllow and clunky - I'm guessing due to our device's low RAM among other limitations, but it works.
[Samsung Galaxy Nexus] BfstMtn:
CM doesn't support f2fs (yet?).
[Samsung Galaxy Nexus] NerdySpam:
Just remove Facebook app and Facebook messenger app, and no more freezing and lags.

Have some delay wen Receive a Call (Black Screen for few secs and cant anwser) same with alarm clock, anyone experienced that?
[Samsung Galaxy Nexus] chall32:
Yea, have that on KK / CM11 too, so not an L / CM12 specific issue. There was a build.prop fix discussed in either this or the CM11 thread.... Didn't try it myself but others that did reported delay went away

Sent from my Nexus
[Samsung Galaxy Nexus] PimpTwzt:
Beautiful, I was wondering about that too. Thank you for the 411. That thing is pretty hidden.
[Samsung Galaxy Nexus] smartAgent47:
after installing cm12 rom, and while installing pico gapps status 6 error. I tried nano status 7 error.

What to do ?
[Samsung Galaxy Nexus] Reptilez_DK:
Did you try a "factory reset" ? ;)
[Samsung Galaxy Nexus] smartAgent47:
Yeah actually i was first rooted then i came back to stock 4.1.2. Then i installed cwm via rom manager and flashing superuser .. then i took a nandroid backup and flashed the rom. The rom worked finebut gapps was cause status 6 and status 7 error. I tried FML and slim gapps but for sign in into google account is not there ...

So what should i do ??
[Samsung Galaxy Nexus] JackClarke:
I can't install any GApps either. I've tried PA-GApps Stock, PA-Gapps Nano and FML GApps. All of them tell me there's not enough space in system/.
[Samsung Galaxy Nexus] Airlibik:
use pico gapps the gapps you used are too mutch big for the system.
[Samsung Galaxy Nexus] foosion:
Settings - Privacy - PrivacyGuard - : - Advanced - Superuser shows ES File Explorer / Superuser (used once) / Running, even though it's not running and not on the list of running apps in Settings - Apps - Running.

Is this expected behavior?
[Samsung Galaxy Nexus] Reptilez_DK:
I use these gapps, and they work very well. http://xdaforums.com/showthread.php?t=2943330
[Samsung Galaxy Nexus] CYoung234:
I installed the 1/20 ROM as a dirty flash, and had a lot of trouble with lag, so I did a fresh install of it (Factory Reset), and saw the same thing. So, I reverted back to the 1/11 ROM, and it performs much better on my phone. I also found I had to use the Pico GAPPS. As usual, your mileage may vary!
[Samsung Galaxy Nexus] Felixander:
Root

Is possible make the root to this Rom?
[Samsung Galaxy Nexus] Sumsar94:
Flash SuperSU in recovery

Check here: http://xdaforums.com/showthread.php?t=1538053
[Samsung Galaxy Nexus] Jacek80:
gapps you entered did not want to install (Status 6, instalation aborted). It was not until I was able to with this

everything works just fine .... sometimes the phone freezes for a few seconds.

and another error ... If I plug the charger (the phone is turned off), then after a while the phone starts in recovery mode .... why?
[Samsung Galaxy Nexus] 505243267:
Status 6 means you're using CWM v6.0.4.7 Recovery.(See the first question in http://xdaforums.com/showpost.php?p=56832798&postcount=3 ) You can using another recovery to install it.
[Samsung Galaxy Nexus] pobetiger:
Hey Ziyann,

when we build the omap kernel, do we use the cm-12 branch or the domx branch? Can you explain what's the difference?

I can see the the domx branch looks like you are rebuilding the ducati camera interface? (Still learning obviously, so any instructions will be appreciated).

Thanks,

Ben
[Samsung Galaxy Nexus] IceVip:
Does this rom have pie control?
[Samsung Galaxy Nexus] Noeljunior:
Our nexus might not like high altitudes as I was flighting on a cessna and after a few minutes of recording and monitoring some values, it rebooted and bootlooped after that. I was using one app for recording the track (Google My Tracks), one for monitoring GPS values (GPS Status & Toolbox) and an altimiter app. At some point I decided to take some pictures. The phone warm up even more and rebooted. The only thing I think that might be causing these reboot loops (sometimes it askes me the PIN and then reboot) is corrupted file system... Is there a way to check file system?
[Samsung Galaxy Nexus] Nautilus74:
[MENTION=4923603]Rayaxe[/MENTION] , [MENTION=6328692]BfstMtn[/MENTION] :

R1 , R6

f2fs works! ;) (CACHE & DATA)
[Samsung Galaxy Nexus] Noeljunior:
Looks like my data partition got some files corrupted. It in f2fs but with fsync enabled. Anyway, I could backup and restore after format the data partition.
[Samsung Galaxy Nexus] Rindmann:
Guys, what exactly is f2fs?
[Samsung Galaxy Nexus] Noeljunior:
Quoting Wikipedia,
[Samsung Galaxy Nexus] sergialess:
Flashed along with SmittyL R6, PA Gapps Pico, and data & cache in F2FS. No luck for me (freezed at CM's boot animation).

Wiped Dalvik, Cache, System and Data.
[Samsung Galaxy Nexus] vaby234:
Phone wont wake up if kept idle for long time

I have been testing the new rom dated 20/01/2015 its running smooth stock camera working fine. charging sign still displaying on the locked screen. I have faced few glitches.. My Nexus if kept idle for long time does not wake up when I press power key or volume keys. It responds if I plug in a charger or if a call is received. A restart fix the problem temporarily. One more bug I have detected is that some times the network bar goes missing.
[Samsung Galaxy Nexus] Nautilus74:
versions that I linked are different! ;)
[Samsung Galaxy Nexus] Noeljunior:
Are you using custom kernel and/or set the min frequency to lesse then 350MHz and/or did you undervoltage? I'm running a lot of tests about governors, min/max frequencies and voltages and I found the 200 and 250MHz freqs are tricky. Also, undervoltage sometimes looks good, even stressing the cpu, but after a long deep sleep it won't turn on.
[Samsung Galaxy Nexus] Grzembo1:
Hey,

I've got stupid question.... should I copy code which you wrote at SDK?

Before # i should write adb ?

Sorry, for that, but i'm rookie in that case.

When I typed "adb shell" there were # so phone is rooted, yes ?
[Samsung Galaxy Nexus] sergialess:
Finally working! thank you very much!.
[Samsung Galaxy Nexus] zzpianoman:
in adb if you see $ you must type su to get a # prompt.
[Samsung Galaxy Nexus] Grzembo1:
i have # in adb
[Samsung Galaxy Nexus] zzpianoman:
Then you should be able to just copy and paste the commands after the #.
[Samsung Galaxy Nexus] Grzembo1:
i did it, but i wrote adb before your codes.

If it is OK, then MMS still not works.

I copied apns-conf.xml from AOSP, where MMS works. But IMO AOSP works slower on my phone.
[Samsung Galaxy Nexus] Ziyan:
New build up. Disabled non-pie support and added in my fRom replacement, so report back if there's any problem. The current camera hal crashes without the calibration data, so a problem can be easily noticed, lol. The replacement also logs into logcat (logs successful extractions as well), just grep logcat for 'dcc' to see it (hopefully) logging successful saves :) minus one blocker before going official, only offmode charging should be remaining now.

EDIT: for those with camera problems after updating, flash this hotfix kernel.

Use the cm-12.0 branch for everything, the other branches contain experimental code that will at one point get merged into cm-12.0 (actually, this build contains the domx branch's changes).
[Samsung Galaxy Nexus] pobetiger:
I saw that push to remove the proprietary fRom for open source ones. Sounds good.

So does this mean you figured out how to work the Ducati OMX interface to get camera working? What about the non-pie support? Is that needed for the open source version of fRom?

From what I read on gerrit, that patch doesn't look like it will be merged without some more tweaks (the whole discussion on security, hardcoded names, etc.) Thoughts?

Thanks for your time.

Ben
[Samsung Galaxy Nexus] freshgiammi:
Users, we need your help.

The ones that are on the old builds (aka the ones with still fRom) could you please post the output of "adb shell ls -Z /data/misc/camera/R5_MVEN003_LD2_ND0_IR0_SH0_FL1_SVEN003_DCCID1044" ?

Seems like i'm having permission issues, but i need to know if different devices set them in different ways.
[Samsung Galaxy Nexus] Ziyan:
Non-pie support isn't needed for the replacement. It was only required for fRom :)
[Samsung Galaxy Nexus] pobetiger:
Ah! Now I understand why you said that makes us one down from official (charging issue).

Sweet! Thanks for all the great work. How did you know what to do with the dumpdcc app? All those headers, did you kind some documentation online?

Thanks,

Ben
[Samsung Galaxy Nexus] poo706:
When you mention a conflict with O3, are you talking about the ROM, kernel, or both?

[poo]

Edit: Now that I look at Liquid's optimizations closer, it is stated that strict aliasing is not included, thus I should have no issues with O3, right? https://github.com/LiquidSmooth/android_build/commit/151bdb50158cf0485c4fa1e3b6429a8f2848f8ff
[Samsung Galaxy Nexus] Ziyan:
I sniffed the i2c communication it transacts, by adding some logging to the i2c subsystem of the kernel. Then with the help of some C code, I replicated that - as it turns out, those commands indeed enable/disable the small flash storage located on the camera module, so it could be dumped. It was easy enough to hardcode the always-the-same DCC header and then append the first 0x225 bytes dumped from that flash device to it, and finally save it to it's location :D
[Samsung Galaxy Nexus] zzpianoman:
Well from what I understand, when you compile with O3 you should really follow strict-aliasing rules to avoid introducing hard to trace bugs that could crash the system later on down the road. The idea is that strict aliasing violations will trigger errors in the compiler rather than cause random reboots once the ROM is actually up and running. I don't really know much about Liquid Smooth and what compiler flags are used for that particular ROM but I think the running philosophy is that you should fix the code as much as possible and strict-aliasing rules kind of forces one to do that and ofcourse with O3 you get even further optimizations that should lead to some substantial performance improvements. For CyanogenMod, I'm sticking with the middle ground for now until everything is fully functional. As it is many of the daily updates are introducing plenty of bugs on their own without adding compiler headaches to the whole thing.
[Samsung Galaxy Nexus] musical_chairs:
Are you referring to the same problem I'm seeing on toro and toroplus, where the calibration data is written correctly but the camera can't read it and fails to initialize? It's odd because the calib file is set to 0700 media media on my toro (I still have fRom on that), and it works fine. But I have to change permissions on a clean install or the camera won't work.
[Samsung Galaxy Nexus] freshgiammi:
Exactly. There's some weird thing for sure. The fact is that Ziyan can use his calib.bin with 0700 media media, while i can't, and you too it seems. The trick is to chmod 0704 it, so the "other" category will get read permissions. I actually added a S_IROTH to the dumpdcc file, and it works just fine.

The strange thing is about Ziyan, but i suppose that maybe different devices might have different permissions? Even tho that's unlikely imho.

That's why I asked users to post a ls -Z of that, so we can gather more info.
[Samsung Galaxy Nexus] ALBIEL:
Last build camera don't work and torch tile missing
[Samsung Galaxy Nexus] musical_chairs:
Is that a clean install or a dirty flash? (Just trying to get info here, if my suspicions are right a clean flash won't help this time.)

[MENTION=4986658]freshgiammi[/MENTION] what baffles me is that with fRom it works with 0700, without fRom but with a valid calib.bin file it works with 0700, but with the new implementation it needs 0704 to open the camera.
[Samsung Galaxy Nexus] foosion:
Both work for me in extremely limited testing.

Dirty flash.
[Samsung Galaxy Nexus] freshgiammi:
Sure is something that we're missing in dumpdcc. Oh well, we also have around 4 or 5 new SELinux policies with this opensource tool, and we don't know how fRom truly works. Even tho Ziyan got it working with 0700, i believe we need to -rwx---r-- it.

However, I don't see how a read permission would cause trouble. I think we can leave it there and keep on living.

Last word belongs to the dev, of course.
[Samsung Galaxy Nexus] frickinjerms:
Go to about phone and tap the build number 7 times to get to developer options then in there turn root access to either apps, adb, or both.
[Samsung Galaxy Nexus] Ziyan:
Looks like I goofed the ramdisk when I replaced fRom with dumpdcc, causing it to run as root, instead of media... that may explain the issues some people had with it.

This kernel fixes it - it also has a special sauce that may improve things - report back if you find anything different when using it, compared to the previous build. :)
[Samsung Galaxy Nexus] Syakir Imran:
Testing it will report what happened

---------- Post added at 09:25 AM ---------- Previous post was at 09:20 AM ----------

LOL sorry I didnt notices a new update ... Downloading the new update first
[Samsung Galaxy Nexus] opticyclic:
Excuse my ignorance but what is fRom?

Searches just look for "from" :)

If people are having RAM issues Naked Browser is tiny.
[Samsung Galaxy Nexus] frickinjerms:
I dirty flashed successfully from the 1/20 and holy bologna its running 1000x better, I was using full auto r6 before but am running the test kernel a few posts up now and no lag or sitting there hoping my phone catches up with me. ???

The secret sauce is quite delicious on my lollipops!
[Samsung Galaxy Nexus] musical_chairs:
Well it definitely fixes my camera / dumpdcc issues. And what'd ya do to it??? This thing feels faaast...
[Samsung Galaxy Nexus] zzpianoman:
fRom is a proprietary binary executable which was responsible for extracting calibration data for our cameras from a NV flash chip. This calibration file is unique to every device and is necessary to properly interface with the camera sensor so pictures come out with the correct color composition. The "dilemma" was that this executable was compiled without PIE code, and starting with Lollipop, all executables are required to be compiled with PIE or else the system will refuse to run them. The only workaround, until now, was to disable PIE enforcement, copy our unique calibration data from a KitKat install, or just live with grainy, miscolored photos.
[Samsung Galaxy Nexus] smartAgent47:
in latest build charging text is stuck or it is fixed ??
[Samsung Galaxy Nexus] Syakir Imran:
The boot animation not full screen or Im only???

---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------

Still stuck

---------- Post added at 11:43 AM ---------- Previous post was at 11:34 AM ----------

Hmmm Im lagging really hard .. Im dirty flash
[Samsung Galaxy Nexus] pobetiger:
I pulled today's commits and did a rebuild. My camera and torch is working! w00t!!

Thank you [MENTION=2633638]Ziyan[/MENTION]. Awesome. I'll continue to play with it and report back.

Although I also made the mistake of pulling the rest of the CM-12 stuff also - and the new boot animation looks terrible (cm on the partial white background with things radiating outward). Well, that's why we have CM though, we can change it.

btw, wondering if anybody has issues where when you change ccache location and size, the build takes a very very long time (over a day)?

With my current ccache setup, it takes about 35m to rebuild and 135m to do a make clobber then brunch build. Just curious.
[Samsung Galaxy Nexus] AgentSmith:
Here's my calib.bin from 4.3 stock. These are the permissions according to file manager:
[Samsung Galaxy Nexus] what9000:
Is there anyone on a US T-mobile network that is having success with any LP roms? I have been trying for weeks to get any of them to play nice with any cellular connection. Right now I have used CM12, FML, and AOSP with smitty V5, V6, V7 kernels (CM/FML) and experience constant failure to register/connect to the T-mobile network. If I disable data, it will give me the "!" over the cellular network, if I enable data, it comes up for roughly a second, then completely loses the connection and cycles between a connected/disconnected tug of war.
[Samsung Galaxy Nexus] pobetiger:
Hello what9000,

I am not on T-mo so situation might be a little bit different. But I'm on ATT but my account started out as Cingular, all those years ago. And my data plan uses a really old APN that is not the default. When I first got onto "L", I had to go under wireless -> more -> mobile network -> Access Point Names -> find the one that your plan is on.

I happened to know my APN. If not, you should be able to call up T-mo (on a different phone) and ask them for the correct APN for your plan.

Don't know if this will help.

Regards,

Ben

p.s. I suspect it's the APN because at first I was having the ! over the mobile data icon all the time. On ATT they just disconnect you if you go to the wrong APN from the look of it. So after some thinking and looking, I guessed it was the APN and sure enough it was going to some other place instead of the Cingular APN that I was expecting.
[Samsung Galaxy Nexus] lazydognet:
I have a T-Mobile pre-paid plan with a gnex phone. I flashed FML (with both R6 and R7 kernals) and I've had no issues with data or phone calls so far. I didn't have to make any adjustments or enter in any APN information. I remember that the exclamation mark was on for about a minute after initially flashing the ROM, but it finally connected. After any reboots now, I see a exclamation mark for maybe 5 seconds, but works just fine after that.

On FML, my APN is set to T-Mobile GPRS (fast.T-Mobile.com).

LDN
[Samsung Galaxy Nexus] what9000:
I just did a fresh reinstall of LP and only installed the ROM and Apps, skipped everything but the initial network registration as well. It connects, climbs from edge to H, drops to 3G, and then immediately loses all connection after the 3g signal is shown. If I have WIFI on, it appears to connect to the network and hold it (after a reboot) but loses it again one I close wifi and it has to start coming up on a data connection.

I have used epc.tmobile.com and fast.tmobile.com. I can only select them when on wifi (for stable connection), otherwise it shows no available APNs and simply states "Access point name settings are not available for this user" in the APN selection menu.

While doing some tests on WiFi (to keep a signal) I couldn't successfully make any phone calls, either. They just hung and resulted in a dropped call, or there was no actual sound between us.

...

I just kept this post window open during another reinstall, this time back to 4.4.4 CM-Remix with SmittyV SR kernel and pico gapps. It booted up, immediately acquired the network and went to full signal with H+. Occasionally it swaps between H+ and 3G, but never drops signal. The stock APN selected was fast.tmobile.com.

It is really frustrating, I wish I could figure out what I'm doing wrong. :(
[Samsung Galaxy Nexus] smartAgent47:
One major bug in video recording

I recorded a video through Google Camera, while recording its good no issues but after recording and while playing the video, the video in between is very laggy.

Although that green band appears, the video is very laggy while playing.

I played in stock gallery app and also in mx player . It is laggy in both the apps.

So what should i do ??

I am on 24-01-2015 build and has flashed cmkernel which ziyan had posted.

Thank You !! I hope i didn't post something stupid

Hope this is fixed ...
[Samsung Galaxy Nexus] Syakir Imran:
Yea that is the known bug right now ....
[Samsung Galaxy Nexus] chall32:
root@maguro:/ # ls -Z /data/misc/camera//R5_MVEN003_LD2_ND0_IR0_SH0_FL1_SVEN003_DCCID1044/

-rwx------ media media u:object_r:camera_data_file:s0 calib.bin

root@maguro:/ #

From CM11 M12 build
[Samsung Galaxy Nexus] smartAgent47:
okay thanx for replying
[Samsung Galaxy Nexus] revanmj:
It finally disappeared few minutes ago. I wonder what's causing this.
[Samsung Galaxy Nexus] Reptilez_DK:
If you, like me, prefer cwm recovery, the latest nightly from http://xdaforums.com/showthread.php?t=1757146 works fine, when flashing minimal gapps. :)
[Samsung Galaxy Nexus] madhavs:
Same thing happened to me

I downloaded Super su 2.37 ZIP and flashed in recovery

And its working Give it a try
[Samsung Galaxy Nexus] aliesz:
is it possible to update cm12 updates with cyandelta?!
[Samsung Galaxy Nexus] revanmj:
Nope, because CyanDelta works only with official nightlies which are not yet available.

It works but only for restoring just data (apps have to be installed manually). It generally has issues with any operation on apps files (installing, uninstalling, freezing, etc.). Restoring only data works fine.
[Samsung Galaxy Nexus] w0uter:
I'm flashing right now...... and everything is working just fine now.

Thank you!
[Samsung Galaxy Nexus] Airlibik:
I've settled it creating an update.zip with all apps I needed and I've restored them by flashing them from recovery.
[Samsung Galaxy Nexus] Ashutos1997:
So same way on installing CM12 as FML AOSP 5.0 :

1. Install TWRP 2.8.1.0

2. Make sure You have all partition on ext4

3. Wipe system/data/cache

4. Install ROM

5. Go to mount options and uncheck system

6. Flash GAPPS

7. Reboot

?
[Samsung Galaxy Nexus] foosion:
The location icon is still there for me. In other versions (KK and LP), it only appears when an app is using location services. I'm on a reboot with no apps running and location services off (although who knows what google might be doing in the background).

I wonder if it's just an icon showing or if location is actually running.
[Samsung Galaxy Nexus] revanmj:
Well, I checked in AppOps and it said that Google Play services and Android System were both using location.