yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cloud_strife84:
I had official 4.3 with Franco kernel and it worked. I don't know with kitkat. I have sane issue with CyanogenMod 12.1

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
I seem to recall the method had to be updated with KK.. I think this was all of it? Check for this stuff in the OMAP4-AOSP ramdisk and add it with my AIK package if not, then see if it gets it working. ;)

https://github.com/franciscofranco/tuna/blob/ramdisk/ramdisk-4.4/fstab-ext4.tuna#L18

https://github.com/franciscofranco/tuna/blob/ramdisk/ramdisk-4.4/init.tuna.rc#L18

https://github.com/franciscofranco/tuna/blob/ramdisk/ramdisk-4.4/init.tuna.rc#L195

If it doesn't work, or it's all already there then I guess something needs a fixup for LP+.
[Samsung Galaxy Nexus] kerpert:
My otg works after install ES File Explorer and assigned it as default for USB (just connect the usb pendrive with otg cable and tick the message that appears).
[Samsung Galaxy Nexus] massima:
I use "USB OTG File Manager for Nexus" and it needn't root.
[Samsung Galaxy Nexus] osm0sis:
It's all in [MENTION=2633638]Ziyan[/MENTION]'s CM13 ramdisk, but looks like they're trying to do things differently here..

/fstab.tuna:

# USB storage device
*block/sda* auto auto defaults voldmanaged=usbdisk:auto

And there aren't any sdcard services in init.tuna.rc, let alone one for OTG. :eek:

I don't recall *'s ever working in an fstab, but I'm not going to add the things I suggested here because of the changes in init.tuna.rc. Now, the fact that it's in the CM13 boot.img sets us up for comparison though; does anyone know if OTG is working out-of-the-box on CM13?
[Samsung Galaxy Nexus] xc-racer99:
FYI sdcard services were deprecated in MM, and the * at the end of the entries is new as well. You can check out the docs at https://source.android.com/devices/storage/config.html.
[Samsung Galaxy Nexus] osm0sis:
Ah thanks! Wasn't aware. Guess that's kinda weird that it's still in CM13 then, eh?
[Samsung Galaxy Nexus] kerpert:
Enclosed the logcat with AOSP camera error, with all disactivated (wifi, gps, bt) and airplane mode ON.

The previous one was with Google Camera.
[Samsung Galaxy Nexus] Vankog:
I asked in Ziyan's CM 13 GNex thread about OTG a few weeks ago. They said it's not working.

(So Titanium won't work with OTG. :-/)
[Samsung Galaxy Nexus] kerpert:
Busybox update out today, they solved the installation issues, now trickster mod works.
[Samsung Galaxy Nexus] opticyclic:
I can't get mobile data (wifi is OK) with this ROM.

The phone is fine because all other ROMs I (clean) flash get mobile data fine.

Is anyone else seeing this issue?
[Samsung Galaxy Nexus] n76:
Data on T-Mobile US is working for me on my Maguro.

I had issues connecting to some servers which had advertised IPv6 addresses but weren't really able to deal with IPv6. (T-Mobile US sets up by default for IPv6 only in the APN settings and then does some sort of NAT to allow phone users to access IPv4 only sites).

Based on that experience, I'd first check the APN settings on your phone with this ROM against those from a ROM you know works.
[Samsung Galaxy Nexus] kerpert:
After the Busybox update of Monday, I haven't had more camera error.
[Samsung Galaxy Nexus] Max Frost:
Nope , data works fine on toroplus using sprint mvno ringplus . I think this rom uses the same unified tree the others do . It might help if you say what carrier your using . Are you using maguro , toro or toroplus ?
[Samsung Galaxy Nexus] Bron4444:
Great ROM!

No packet data for me at first on Wind Mobile, but all OK with Telus.

Got Wind data to work properly after changing default "APN protocol" setting from IPv4/IPv6 to only IPv4.
[Samsung Galaxy Nexus] n76:
I had some data and MMS issues on with T-Mobile US at first until I changed some APN settings too. Looking at the source code, this ROM picks those definitions up without modification from AOSP, so I suspect that I'd have had the same issue with any AOSP based ROM. For me the issues were:

Data: T-Mobile US is setup for IPv6 only and a couple of servers I access a lot advertise a IPv6 address but don't actually handle it properly. So those servers were not accessible. If the server/site is IPv4 only, then T-Mobile correctly deals with it. So my data issues weren't really the ROM or T-Mobile but incorrectly configured services. I could fix it by changing the APN though. :)

MMS: This ROM has a separate APN for MMS and the value in AOSP is wrong for it. I changed that to the one listed on the T-Mobile site to be the same as for data and MMS started working.
[Samsung Galaxy Nexus] MentalBreach:
Hi guys!

To developers: great work! I'm following your projects (CyanogenMod, ZMoD, Fork My Life) and I can only say thanks! You're awesome!

To everyone: How many of you use this ROM ad daily driver?

How is the browser experience? After some months of various ROMs testing I rolled back to stock firmware (Android 4.3 Jelly Bean); but also with 4.3 internet browsing is a bit problematic due to low RAM amount.

Right now I'm using TWRP 2.8.7: must I update to 3.X in order to install this ROM?
[Samsung Galaxy Nexus] n76:
I have been using this as my "daily driver" on my Maguro for some time now.

Can't say about the stock browser experience as I don't use it much. I was using Firefox and am now using the Ghostery browser which seems to work reasonably well.

I am using TWRP 2.8.7. Only issue I have is that it won't handle encrypted F2FS partitions, so instead of downloading an update to my phone and flashing it from /data, I use the adb sideload capability to flash ROM updates.
[Samsung Galaxy Nexus] MentalBreach:
Thanks for your feedback :)

I'm using Opera and Opera Beta on stock firmware (JB 4.3) and often the pages crash (specially on "heavy" websites). I hope the optimizations of this ROM could help.

I never changed file system partitions (so I think it's still EXT4), do you think I should convert to F2FS?

I'm sorry for so much questions :p
[Samsung Galaxy Nexus] n76:
Might help, there is a lot more RAM available with this ROM that previously.

Ext4 is not really designed for flash memory storage systems and can become laggy if a fstrim command is not run periodically. In theory that should be automatic with any 5.0 or later (maybe even 4.4) ROM. But in practice the ROMs I was running did not seem to do that. So about once a week or so I'd end up manually doing it using adb shell.

F2FS (Flash Friendly File System) was specifically designed for use with flash memory based storage and does not need the periodic fstrim operation (I don't even think it supports it). Initially I was reluctant to try it, thinking it was experimental. But I noticed the factory ROM on my spouse's Moto E (2015 LTE) used F2FS and figured if it was good enough for Motorola to ship to customers it was probably good enough for me to use.

That said, there appears to be an issue in transferring large files off of this ROM with F2FS (or maybe only encrypted F2FS) formatted partitions based on what I've been following in the bug reports. And I see some check-ins in GitHub that seem from the comments that they address F2FS issues. Not sure those changes are actually integrated into the ROM as the components the changes are in don't seem to be in the build manifest. So this ROM is definitely a work in progress.

OTOH, it has been running great for me even if it is not perfect (yet).
[Samsung Galaxy Nexus] bamtan2:
F2fs is good, but there have been incompatibilities with WhatsApp and others. Ziyan has yet to really endorse using it yet, so I'd say skip it unless you want to test.

CM12/CM13/OMAP4ASOP are all good enough to use, and should be good upgrades from 4.3!

I don't know if a newer TWRP is needed. TWRP has always been pretty sketchy for me, so if someone doesn't work, I'd flash ziyan's latest TWRP 3 wherever that is.
[Samsung Galaxy Nexus] MentalBreach:
Thanks you both! As soon I have enough free time, I think I'll try this ROM.
[Samsung Galaxy Nexus] opticyclic:
I am using an UNOFFICIAL Dirty Unicorns based on this ROM.

That was it thanks.

I wonder why this defaults differently to CyanogenMod though. :confused:

I'm on Wind too!
[Samsung Galaxy Nexus] musical_chairs:
This ROM uses the stock APNs from aosp, CyanogenMod uses its own very heavily modified APNs, in addition to a very heavily modified telephony stack. No surprise at all that they behave differently.
[Samsung Galaxy Nexus] Ziyan:
Since I'm done with my finals, I'm going to release a new build as soon as the July security patches are up (probably in a few days) :)
[Samsung Galaxy Nexus] gecko16300:
Hello, thank you for your awesome work !

I am wondering if you will add support for more devices (such as Toshiba AT200 ?) ?
[Samsung Galaxy Nexus] uji_sine:
Glad to hear news from Ziyan, I hope to see CM13 update also.
[Samsung Galaxy Nexus] Ziyan:
It's highly unlikely; I already support *all* devices I own :rolleyes: and even if I had an AT200, I have so many projects and not enough time already....

Of course, it's just that I have to take care of so many Android projects that they stacked up a little now :)
[Samsung Galaxy Nexus] n76:
[MENTION=2633638]Ziyan[/MENTION] Question regarding the repository. . . I see android_kernel_omap4_common in the repository with a number of recent check-ins that sound interesting. But when I look at the project manifest I don't see that being included at all. How does that component fit in to the project?
[Samsung Galaxy Nexus] opticyclic:
Is This Really What AOSP Looks Like?

First off: I appreciate this project and the benefits it creates for a base for new custom ROMs.

However, this looks very Jelly Bean.

Is it just that I have been spoiled by themes and fully configured ROMs or is this what AOSP looks like in Marshmallow?

Or is it that the last official AOSP for GNex was Jelly Bean and if I got AOSP on an up to date Nexus device it would look nicer?
[Samsung Galaxy Nexus] n76:
FWIW, my spouse's Moto E LTE (2015) with stock 5.1 Lollipop has the same look and feel to me as both this Marshmallow build and the 5.1 ZMOD I was running before this. That Moto ROM is reputed to follow stock AOSP very closely in its look and feel. So my take is this it is what AOSP looks like.

Over on the CM13 thread for GNex, it seems that Ziyan is just about ready to turn on nightlies, so if you want themes and such that might be a good ROM for you.
[Samsung Galaxy Nexus] AgusL:
This is how AOSP looks. Google hasn't been upgrading in terms of visual design very much really. They have their branded apps so they push that ones instead of taking care of AOSP.

Please someone correct me if I'm wrong.
[Samsung Galaxy Nexus] osm0sis:
Yes, you're right, CM are the ones who try to keep the included apps matching their Google counterparts better, but of course installing a good GApps package with Dialer, Chrome, etc. will alleviate pretty much all of that on an AOSP ROM as well.
[Samsung Galaxy Nexus] phaleg:
Waiting for your big update after your exams ^^
[Samsung Galaxy Nexus] THEfog101:
Hey Ziyan. Glad to hear you will be updating this build again, sure you blasted through your finals.

Quick question, at what point will freq above 1.2Ghz be available? Thanks.
[Samsung Galaxy Nexus] iorme:
I've been using this rom for about one week and it is working quite stable. When using CM 12.1 after a few days sometimes the power button is not working and the device must be restarted to be working again, but its not happen on this rom.
[Samsung Galaxy Nexus] massoudsh:
I use a build of this rom with kernel modified by [MENTION=6140342]Fenix46[/MENTION] for test about a week, it is very smooth and liquid and my old Gnex run very well now, I didn't see any major problem, Since the kitkat is so far the best rom, if [MENTION=1952004]fenix86[/MENTION] let me share a link to download it here???
[Samsung Galaxy Nexus] r.albu:
Hi, do you have USB OTG?

Did anyone find a "solution" to USB OTG with this ROM?
[Samsung Galaxy Nexus] massoudsh:
I didn't test it but install solid explorer otg plugin and now have this option[emoji6]

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] siealex:
Forget it forever, it will never be supported. It's clean AOSP and OTG is OEM crapware.
[Samsung Galaxy Nexus] r.albu:
So you don't use it nor have a solution.
[Samsung Galaxy Nexus] Markoz88:
So even the app "usb otg file manager for Nexus" doesn't work?
[Samsung Galaxy Nexus] massoudsh:
Use "solid explorer otg plugin", work fine for me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thepasto:
Well, it's a bit weird, if i can rember, OTG was working with aosp-6.0-smc, so it doesn't seem to be a rom related issue.
[Samsung Galaxy Nexus] MentalBreach:
I installed this ROM and it's wonderful! In the past three days everything worked flawlessy, even battery life. Just two things:

1 - No SIM with Airplane Mode on: if you shutdown your device with Airplane Mode on, at next boot SIM won't be recognized. Just disable Airplane Mode and everything will be ok (no reboot needed).

2 - Bluetooth notification entries are not translated: even if I'm using the italian language, the successful/unsuccessful counter of bluetooth notification is not translated (notification title is in italian language).*

* If you need help with translation don't hesitate to contact me! :)
[Samsung Galaxy Nexus] massoudsh:
Well friends, @ Fenix46 finally allowed me to share his rom:highfive:, Install and Enjoy one of the best MM ROMs...:good:

download here
[Samsung Galaxy Nexus] PythonNut:
This seems very nice, but I have a strange issue where I can't pull down the quicksettings panel. I'll give it a try on a clean flash this weekend, if I can.
[Samsung Galaxy Nexus] massoudsh:
You must do a clean flash and resolve your problem.[emoji6] [emoji6] [emoji6]
[Samsung Galaxy Nexus] n76:
You might want to try the either of the two things listed in these links:

http://infomash.net/home-button-not-working-after-updating-to-android-marshmallow/

https://www.virag.si/2015/08/home-button-not-working-after-flashing-to-android-marshmallow/

http://retiredtechie.fitchfamily.or...orking-after-flashing-to-android-marshmallow/

The one in the last link is what worked for me.
[Samsung Galaxy Nexus] PythonNut:
Thanks, actually the first item of the first link worked for me. The ROM does seem quite nice.
[Samsung Galaxy Nexus] Ziyan:
New build up:

- updated to MOB30R (July security patches)

- kernel fixes related to USB OTG (report back if it works now)

- some minor, mostly unnoticeable device tree cleanups (like disabled camera hal debugging, which can result in very slightly faster camera operating speed, and slightly tweaked read-ahead value)

Enjoy!
[Samsung Galaxy Nexus] phaleg:
Since there is this tricky thing of gapps,

what is the correct procedure to dirty flash from your previous april build?

Help [MENTION=2633638]Ziyan[/MENTION]
[Samsung Galaxy Nexus] Master94ga:
Thanks for the build, can be flashed over the previous build?
[Samsung Galaxy Nexus] Ziyan:
Let's take a look at the second post:

So, simply flash the ROM zip, then flash the gapps zip. That's all in case of an upgrade :) but like I always say: always backup!
[Samsung Galaxy Nexus] phaleg:
You're the best buddy!!! :highfive:
[Samsung Galaxy Nexus] Master94ga:
I have a big problem, somehow I lost the recovery I can't enable usb debugging, also I can't start android... How can I reinstall a custom recovery? Fastboot doesn't find the devices... :(
[Samsung Galaxy Nexus] phaleg:
Should I flash superSU again?
[Samsung Galaxy Nexus] siealex:
After dirty-flashing this build I've lost ALL notification icons (even persistent ones) in the status bar, also Quick Settings and Recents. WTF???

PS, Now on Tap does not work too, it worked fine in the previous build.
[Samsung Galaxy Nexus] phaleg:
Did you follow Ziyan procedure?
[Samsung Galaxy Nexus] siealex:
Usual dirty flash. ROM, latest GAPPS (Nano), SuperSU 2.76, Xposed v86, everything in one batch, then wipe cache and reboot.

Ps, also NO LOCKSCREEN!

---------- Post added at 12:07 PM ---------- Previous post was at 11:43 AM ----------

Also I can't access Developer settings. "Developer settings are inaccessible for this user". WTF?
[Samsung Galaxy Nexus] Ziyan:
In this case, you need to follow http://xdaforums.com/showpost.php?p=67856851&postcount=492.
[Samsung Galaxy Nexus] siealex:
I downgraded to the previous build, this problem persists. Trying these steps now...

---------- Post added at 01:27 PM ---------- Previous post was at 01:20 PM ----------

http://infomash.net/home-button-not-working-after-updating-to-android-marshmallow/

This one works on the previous build, now updating again...
[Samsung Galaxy Nexus] siealex:
These methods DO NOT work on the new build, the settings wizard loops with a message saying "you must enter the Google account you used before restoring settings". But I can't find where to enter it...

PS, it finally worked after entering

settings --user 0 put secure user_setup_complete 1

in ADB shell and rebooting.
[Samsung Galaxy Nexus] r.albu:
Thanks @Ziyan! That's really great!

The notification and his functionality is really good.

With me, USB OTG works now but I'm having some problems (I'm using a 32GB pen drive):

- I'm able to read the usb drive, delete and copy with the "internal" file manager (only from usb to internal memory).

- but, with Solid Explorer, I was not able to copy from/to internal memory to/from USB drive one of my nandroid backups (as it used to do).

Don't know if it's a problem on the Solid Explorer side. I had to search for the usb drive location (couldn't get it in "Storage", but only under "mnt/media_rw/1C38-BC23"...). I'll try with another file explorer and report back.

Anyone got a problem like this? Is there anything I can do to help?

UPDATE [MENTION=7168283]2016[/MENTION]0804:

It's working fine, after installing Solid Explorer (not the Classic one I had before).

I've done that too, got the same and had to make a clean install: everything's back to normal.
[Samsung Galaxy Nexus] :
Thank you very much for uploading this.

The kernel seems to be working fine with the newest release of the ROM (I extracted and applied the boot.img manually).

I do not need a lot of kernel "features" but the one I must have is colour settings (I prefer warmer colour temperature) which is not available in the stock kernel. It would be nice though to have more CPU and GPU tweaks available as even in this kernel the maximum is only 1200 MHz (CPU) and 384 MHz (GPU).
[Samsung Galaxy Nexus] osm0sis:
And I like mine cooler, so hopefully [MENTION=6140342]Fenix46[/MENTION] will release a new version, since I imagine this older one undoes the OTG fixes, etc. from the latest ROM release.

Edit: Theoretically the latest CM13 or Omni kernels could also work.

Edit 2: Nope.. Omni also doesn't have the colorcontrol commits, and CM's boot.img seems incompatible up front, but just the zImage may still work, I'll try it later today after I catch up on some sleep.

Edit 3: [MENTION=2633638]Ziyan[/MENTION], still no Google WebView support patch included? :(
[Samsung Galaxy Nexus] fromfree:
[MENTION=2633638]Ziyan[/MENTION] I noticed that the Omni build has SELinux set to enforcing, is it possible to have it set to enforcing on this ROM too? Is it something that we can do by ourselves without having to re-build the ROM?

[MENTION=4544860]osm0sis[/MENTION] for what concerns WebView, is it not enough to install it from the PlayStore?
[Samsung Galaxy Nexus] KShion619:
Installing higher level gapps (micro or above) require this fix to create google accounts without xposed framework installed
[Samsung Galaxy Nexus] bamtan2:
I've tested every kernel feature there is in [MENTION=4608636]bsmitty83[/MENTION]'s kernels, and the one I keep coming back to, flash after flash, is color control. Because our OLED displays are so old, they do not have the right colors anymore. I must adjust every ROM to look right, which is the only reason I can think of why I must use CM not AOSP. ;(
[Samsung Galaxy Nexus] osm0sis:
Doesn't do anything unless the ROM supports it and uses it over the AOSP one. Flashing GApps replaces AOSP's with Google's and then the SetupWizard fails. It's a long standing thing that's pretty well documented. CM and Omni both have the patch, OMAP-AOSP still needs it added to make GApps work like on a Nexus ROM.

Same. I've always really liked Omni too, but it's also missing colorcontrol.
[Samsung Galaxy Nexus] fromfree:
Maybe it doesn't matter, but I noticed that if I install WebView from the playstore the userAgent of a webView browser changes from Chrome 44.* to Chrome 51.* , so it looks like the system uses the Google webView instead of the AOSP one, or am I wrong?

I'm using the pico Open GApps package :o
[Samsung Galaxy Nexus] osm0sis:
You have both WebViews installed though, a larger GApps package removes AOSP's to make it like it should be on a Nexus device. Pretty much every custom ROM has the patch to make it work, except for OMAP-AOSP.

Edit: Follow-up on my experiment: applying CM's zImage to the Omni ramdisk didn't boot, and likely wouldn't work with OMAP-AOSP either, so I guess we're out of luck until [MENTION=2633638]Ziyan[/MENTION] adds colorcontrol or another custom kernel dev ([MENTION=6140342]Fenix46[/MENTION]? [MENTION=4608636]bsmitty83[/MENTION]? [MENTION=6779822]voidz777[/MENTION]?) steps up with an AnyKernel2 zip to make it work over most ROMs.
[Samsung Galaxy Nexus] Fenix46:
Don't boot because it need the PVR driver build with it.. also if the kernel it is the same for CM, Omni, and OMAP4-AOSP. the driver are part of hardware... and when build the rom, it call the kernel for header's and omaplfb.. but if this kernel (without PVR) is flash, in another rom, it stuck, because fails to load libraries...
[Samsung Galaxy Nexus] osm0sis:
Ah well, maybe the drivers could be packaged with the AK2 zip to make it work universally.
[Samsung Galaxy Nexus] KShion619:
I'm pretty sure this is more of a project to make a great base level ROM for the Galaxy Nexus, for that, we don't necessarily need nor want to have to make a modified system outside of the omap4 tuna trees, another ROM can be created for purposes of this, similar to how ZMod, Shiny and FML were, slightly altered AOSP ROMs for daily driver use and completeness. Of course correct me if im wrong [MENTION=2633638]Ziyan[/MENTION] but that's how I'm reading this project as from afar.
[Samsung Galaxy Nexus] osm0sis:
WebView isn't an arguably pointless feature, it's a basic ROM functioning thing, so hopefully that's good to go in. Colorcontrol, yeah, I can agree maybe not necessary in the base, but then we'll need a custom kernel in a bad way for anything non-CM based..
[Samsung Galaxy Nexus] :
I have experienced a lot of issues with the camera while using this ROM for the last few days. It does not seem to be able to reclaim the required RAM when there are many other apps open and the amount of RAM free is low. In such a situation it always fails to start on first try, and only works after closing and re-opening the camera app after the crash happens.

I thought that the camera related issues had been mostly fixed, especially since these kind of problems are not mentioned in the OP. At the moment I find it very unreliable and kind of annoying, e.g. when trying to open the camera directly with a double-tap on the power button just to take a quick picture only to see the camera app fail to start.

I have been using the default camera app and have not tried any 3rd party yet. Has anyone else experienced these kind of problems recently?

I am going to check the CM 13 now, and had been using the zzpianoman's ROM before but that one had serious issues with phone calls (which are much more important to me than the camera).
[Samsung Galaxy Nexus] Ygor Cortes:
It can't seem to work for me. Do I have to do it on a computer or can I do it on Terminal Emulator on the phone?

Edit: nvm, it worked by running the setup wizard.
[Samsung Galaxy Nexus] kerpert:
Hello,

adb root

adb shell

settings --user 0 put secure user_setup_complete 1

Doesn't work also for me, please how to force setup wizard for creating a new user?

PS: I can't also enter into developer options because aren't available for the current (admin) user.