yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] robocop2000:
Hi have some problem with Gravity Box 5.1.3 on Zmod (06/017). Status bar and navbar customitazion dosen't work! Also desktop extended! It's incredible! Any one have same problems? Please can help me?
[Samsung Galaxy Nexus] siealex:
Try 5.1.0 or 5.1.2. Statusbar and navbar customizations work fine.
[Samsung Galaxy Nexus] ruben46_:
Thanks for your work,Ziyan this is a really good rom
[Samsung Galaxy Nexus] AgentSmith:
I've already mentioned that I'm experiencing serious lag with the latest build. I use minimal gapps. Today the phone froze and rebooted and got stuck at the Android boot logo. After pulling the battery it booted fine but went through the whole app optimization process again. When Android fully booted all data still appeared fine luckily.

With older builds Zmod was quite snappy but lately it has gotten a lot worse. A factory reset in TWRP didn't solve it unfortunately. Does anyone else experience the same issue here?

Multitasking is a pain in the a** as well. Even minimizing running apps to 1 or 2 doesn't have a noticeable positive effect on snappiness. Again this was a lot better with older builds and I'm tempted to revert to one of those, at least until a better build comes out. :)
[Samsung Galaxy Nexus] n76:
What file system are you using on /data and /cache?

I've been running ZMoD with /data formatted as f2fs for a while now and loaded the latest version when it was released and haven't noticed any lagging, freezing nor has it spontaneously rebooted on me at all.

OTOH, I'm not using gapps at all, just a couple of components from the microG project to give me access to Play Store and for network location. So there might be some issue with either the specific version of gapps you loaded or gapps in general and this version of ZMoD.
[Samsung Galaxy Nexus] siealex:
Are you using Xposed? It's a well known Xposed bug.
[Samsung Galaxy Nexus] AgentSmith:
EXT4. It served me well for years. I'm not fond of changing to a still relatively experimental file system. The gapps I use is also just Google play services stuff but I can always try a different version.

Nope.
[Samsung Galaxy Nexus] siealex:
Android 5.1 always performs dexopting after an unfinished boot. If you see yopur phone bootlooping or frozen at boot, reboot to recovery and delete data/dalvik-cache/arm/.booting. Then reboot again. If the dalvik cache is intact, the system will boot up without dexopting.
[Samsung Galaxy Nexus] wbedard:
Would you summarize the bug or post a link that provides more info? My GNex on ZMoD never freezes. It's a testing device and doesn't see as much use as my "daily driver" but still... it's not well known to me. Thanks in advance.

R/

wbedard
[Samsung Galaxy Nexus] siealex:
The known Xposed bug is random bootlooping or freezing on reboot with no obvious reasons. Search the Xposed for 5.1 thread and you'll see it...
[Samsung Galaxy Nexus] n76:
f2fs, the "still relatively experimental file system", is what came from the factory on the Moto E LTE we acquired a couple month or so ago. I guess Motorola missed the memo about it being experimental. :)

If you want to run ext4, verify that fstrim is being run on /data and /cache periodically (probably daily) and if not you should do that as preventative maintenance against one cause of lagging.
[Samsung Galaxy Nexus] wbedard:
Ok, perhaps I used the term "never" a bit too loosely.

My GNex (and only my GNex device...) also used to freeze during boot after updating XPosed or, more specifically, after wiping the dalvik cache (DC) . As you mentioned, XPosed dexopts all apks as needed and, after wiping the DC, that's a lot of work to do. After installing LiveBoot (I could have also used logcat via adb...), I noticed that the device was undergoing extreme thermal throttling during the initial phase of dexopt'ing, that is before the box appears saying "Optimizing app 1 of..." or very similar. At one point, I actually pulled the back off my device and blew on it during booting and noticed that this actually helped it past that point where it would normally freeze. In my experience, if I get the "Optimizing app... " box then I'm home free. I've since refined my process where I just set the device in front of my air-conditioner vent during boot... but again, only if I've had some reason to wipe the DC.

Since adopting that process, my device never freezes... not during boot and not during normal operation. None of my other devices, which all run XPosed, have this issue. Hope this helps.

R/

wbedard
[Samsung Galaxy Nexus] Punkiderma:
I know is a little OT but since it came out in this thread I write about it here again:

The ones that had the issue with whatsapp (messages disappearing without reason) solved it in some way? Is getting really annoying for me...
[Samsung Galaxy Nexus] nickdc986:
Nope, the problem is still here.
[Samsung Galaxy Nexus] AgentSmith:
The fact that fsck still isnt able to fix f2fs partitions is reason enough for me to steer clear of the file system. That's what I meant with "relatively experimental". If f2fs would be the better file system wouldn't we see it on many more devices by now? Just one device with f2fs actually convinces me to _not_ use it. ;)

That's assuming I haven't done so yet. On the contrary, I fstrim'ed both cache and data manually quite often. Lately however it doesn't seem to have much effect so my guess is that most of the lag isn't file system related. And let me repeat myself: older builds were much more snappy.
[Samsung Galaxy Nexus] AgentSmith:
Today I tried open gapps (pico) with the latest Zmod build but AOSP keyboard constantly crashes. Can anyone give an alternative gapps or a specific open gapps build that does work?
[Samsung Galaxy Nexus] bamtan2:
these are the two most active/up-to-date google apps packages on xda that I've seen:

open gapps http://xdaforums.com/android/software/pa-gapps-continuation-t3098071

tk gapps http://xdaforums.com/android/software/tk-gapps-t3116347
[Samsung Galaxy Nexus] AgentSmith:
The first one is the one I tried. Their 20150707 build to be precise. Even with a completely clean flash AOSP keyboard constantly crashes here. I'm back on the old 0404 minimal gapps build which is fine except that gesture typing doesn't work.

Another issue I've come across is that AOSP calendar doesn't sync with my Google account. Could this be because googlecalendarsyncadapter.apk is missing? How can I fix this? I'm using AOSP calendar and browser now instead of google calendar and chrome to get rid of lag.
[Samsung Galaxy Nexus] dante197:
im using this gapps

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

i had no problem with aosp calendar, aosp keyboard and browser ;)
[Samsung Galaxy Nexus] hubik.j:
[MENTION=283276]AgentSmith[/MENTION]

Minimal gapps offer addon for calendar sync. Just flash it on top of the gapps. You can do it even now with wiping just cache.
[Samsung Galaxy Nexus] AgentSmith:
OK I just slapped myself in the face. [emoji14] I should've checked their OP. I knew about those addons it just didn't occur to me that calendar sync isn't part of the base pack. It's working now thanks! :)
[Samsung Galaxy Nexus] pavlo1c:
and where confidentiality?

why not work root?

why access denied to sd card for diff app?
[Samsung Galaxy Nexus] smhnkmr:
Major Issue with Phone Dialer - ZMod (06/17)

I am facing a major issue with phone dialer in ZMod 06/17 build.

When making a call, I can't hear anything, nor the receiver can hear me. The only solution is to reboot the phone. This is really a serious bug - the phone lost it's core feature of making/receiving a phone calls. Right now i am using my old Nokia Phone to make calls :(

Does someone else experience this and found a workaround?

[MENTION=2633638]Ziyan[/MENTION] - it would be much helpful if we get it fixed soon/

Thanks in advance
[Samsung Galaxy Nexus] scassascassa:
I confirm the bug, I reboot the phone and go on.
[Samsung Galaxy Nexus] cartman333:
Same thing here.
[Samsung Galaxy Nexus] Merio90:
Yup same here. I flashed the 6/17 build the day it was released, I received a phone call, answered it and couldn't hear a thing (nothing but static, muffled sound). I thought it was my reception so I hanged up and just texted. Later that day I received another phone call and the same problem took place again. I didn't want to look further into the issue and try to find a solution so I went ahead and immediately flashed back to 5/18 and been using that build since with no issues. I was beginning to think that this was an "isolated" bug and it was effecting my phone only due to hardware failure, but thank you so much for pointing out that bug. Huge sigh of relief. I am glad it is a bug in the 6/17 build and not just my phone acting crazy. Thanks. Hopefully Ziyan can replicate the bug and fix it soon. Kind of odd how very few people have pointed this issue out. I guess people don't talk on their cell phones anymore, just text lol.
[Samsung Galaxy Nexus] AgentSmith:
I mostly talk using VoIP services including SIP. But even the few 'real' calls I made went just fine. I'm surprised this wasn't mentioned before until now.
[Samsung Galaxy Nexus] Ziyan:
That's odd, as I make/receive 2-3 calls daily, and didn't notice this bug yet :rolleyes: any chance you guys could post a logcat immediately after this happens next time?
[Samsung Galaxy Nexus] brandonabandon:
I don't have this bug using 6/17. I am however running a personal build of FA kernel w/sabermod. If someone would like to test, you can pm.
[Samsung Galaxy Nexus] JackSlaterIV:
Using build 6/17 and no in-call bugs here.
[Samsung Galaxy Nexus] filenox:
Is there someone who can shoot video Snapchats?
[Samsung Galaxy Nexus] n76:
This seems odd to me: In the last day or so my phone with 17-June ZMoD started to get laggy. Poking around and found /cache was formatted as ext4 even though I thought I had formatted it as f2fs. Ran fstrim on /cache and the lagging seems to have gone away.

But I do not want to have to periodically run fstrim so I booted into recovery (twrp 2.8.6.0 from the download link on this thread) and wiped /cache and reformatted it to f2fs. And then verified in recovery that /cache was f2fs. Rebooted to normal operation and rechecked: /cache is back to ext4. What the heck? Why/where is /cache being reformatted to ext4?

FWIW, /data is f2fs and there seems to be no problem with that.
[Samsung Galaxy Nexus] clyder:
Here also no such bugs. I am using 6/17 build since it came out. No custom kernels, xposed or anything other then just dirty 6/17 flash over the previous version.
[Samsung Galaxy Nexus] alagga:
Look at page 105, i wrote a tutorial. Usw TWRP Version 2.8.5.0 as 2.8.6.0 is buggy for some users

Gesendet von meinem Galaxy Nexus mit Hilfe von XDA Forums
[Samsung Galaxy Nexus] JackSlaterIV:
Same here, I have been using a stock Zmod rom.
[Samsung Galaxy Nexus] Merio90:
Not sure what must have gone wrong, maybe it was a bad flash perhaps. I was running 6/17 with LuckyKernel & F2FS when I noticed the sound issue when receiving a phone call. I don't want to take any chances and flash back to 6/17 (I'm on 5/18) to try and look further into the problem w/o custom kernel. I might have to flash it again during the midnight hours when I don't receive any calls. That's really strange, everything is working perfectly fine on this 5/18 build no phone call issues whatsoever. Second thought, I just might wait till Ziyan releases another build as the current build I'm using is working flawlessly.
[Samsung Galaxy Nexus] n76:
Your post at http://xdaforums.com/showpost.php?p=61587885&postcount=1050 gives a link to twrp 2.8.5.0 but the link is broken. I tried the 2.8.5.0 and 2.8.7.0 over at https://dl.twrp.me/maguro/ and neither supports f2fs.

Do you have another link for a Maguro 2.8.5.0 that supports f2fs?

I don't think it is the recovery program however. . . If I format /cache to f2fs using twrp 2.8.6.0 and then reboot into the bootloader (to make sure I'm starting fresh) and then reboot back into recovery it still shows /cache to be f2fs. It only changes to ext4 when I boot into system. That makes me think something in the system start up is not happy with f2fs and is formatting it to ext4.
[Samsung Galaxy Nexus] Punkiderma:
I have the same bug, and I wrote here about ths some time ago; If I rememember well, is a rom-related issue
[Samsung Galaxy Nexus] osm0sis:
fstrim /data and /cache seemed to resolve a fair amount of the lag for me as well. Still definite memory management issues compared to KitKat, but it's not being exacerbated by the storage bottleneck anymore. :good:
[Samsung Galaxy Nexus] slayerz:
Same issue with Instagram - which I believe happens with most custom roms.
[Samsung Galaxy Nexus] siealex:
Somebody on this forum said that Android 5 can dexopt apps in background. Does this feature exist and how to enable it?
[Samsung Galaxy Nexus] WoolTomb:
Hey [MENTION=2633638]Ziyan[/MENTION], when will u release a new fantastic build? :D

---------- Post added at 04:59 PM ---------- Previous post was at 04:59 PM ----------

Hey [MENTION=2633638]Ziyan[/MENTION], when will u release a new fantastic build? :D
[Samsung Galaxy Nexus] n76:
dexopt is Dalvik executable optimisation. Basically the Dalvik environment uses "just in time" (JIT) compilation to run the Java code that is the bulk of most Android apps. dexopt was a way to optimize this.

Android 5 replaces Dalvik with the new "Android Run Time" (ART). ART was introduced as an experimental option in 4.4 and on KitKat you had to enable it. ART compiles each app to native code at installation time. So installs on apps can take longer, most noticeable on large apps. But once installed they are native code and don't need to be further optimized at run time.

Because apps are no longer compiled just in time at runtime, the old optimizations needed to make that faster, like dexopt, are not needed.
[Samsung Galaxy Nexus] alagga:
It's recovery related. I got this issue with 2.8.6.0 even on /data. Will look later to find a downloadlink to the 2.8.5.0 TWRP

Gesendet von meinem Galaxy Nexus mit Hilfe von XDA Forums
[Samsung Galaxy Nexus] hardstyle86:
OT:

Any news? I still have the problem.

I'm not on Zmod, but this is the only place where I have found people with the same problem.

May this be related to F2FS? I'll try to switch back to EXT4 as a last resort. :(

Thanks.
[Samsung Galaxy Nexus] siealex:
Does this rom use FS caching? This problem can be related to caching, you exit the program before it actually writes its data to flash memory. But much more likely the problem is on their servers.
[Samsung Galaxy Nexus] NerdySpam:
Anyone try to use MHL-HDMI Adaptor with zMod? I try but dosent work, i read something about you have to use original ROM or custom ROM based on orignal to get it work, is true?

Any way to make it work in zMod?
[Samsung Galaxy Nexus] obscurer:
With included kernel I got it working after few attemts to reconnect, but video is freezing.
[Samsung Galaxy Nexus] hardstyle86:
For those who have the problem of WhatsApp disappearing messages, I can confirm that switching back to EXT4 solves the problem.

Performances are a bit worse, but the problem was so annoying.
[Samsung Galaxy Nexus] kerpert:
Can you confirm that isn't possible to personalize the quick setting icons?

I didn't find nothing.
[Samsung Galaxy Nexus] Jagoflax:
You can do it using Xpossed + GravityBox

Enviado desde mi Nexus 7 mediante Tapatalk
[Samsung Galaxy Nexus] NerdySpam:
zMod+LuckyK [5.x] kernel and i have MHL-HDMI Workink perfect, not lag at all.
[Samsung Galaxy Nexus] nickdc986:
My brother with f2fs and same ROM doesn't have the problem.
[Samsung Galaxy Nexus] Punkiderma:
But I used whatsapp with f2fs for a long time without any issue, so sad I have to switch to ext4 again :(

I think we with the problem should try to write down everything we have on our phones (xposed modules, busybox version etc) in order to find the common points, maybe we can trace down the issue. What do you think?
[Samsung Galaxy Nexus] hardstyle86:
Good idea!

Since the problem is not Zmod related, I think it's better to move to the thread I opened a few weeks ago: http://xdaforums.com/galaxy-nexus/help/whatsapp-deleting-messages-t3140876
[Samsung Galaxy Nexus] nickdc986:
So is it definitely a f2fs related issue?
[Samsung Galaxy Nexus] Nautilus74:
I've same issue in Uozzapp...... (and f2fs) ...... and I've a different rom.......

I do not know if the problem has always existed, because I've installed Uozzapp again (discovering the problem) after a long time..... and before I was in ext4....
[Samsung Galaxy Nexus] aosp:
I got a used maguro off of eBay thanks to the six users who donated to [MENTION=2633638]Ziyan[/MENTION] paypal he helped me receive it quickly thanks alot ladies and gents GNeX4Eva ;)
[Samsung Galaxy Nexus] Mrmoves:
weird wifi

I'm running 16/5 version here.

Got some major wifi problems, it connects/disconnects/won't connect/ has a connection for 5sec./working ok?

weird stuff :cyclops:

anyone else has these problems?
[Samsung Galaxy Nexus] n76:
This won't help much: My wifi has been rock solid both on my home network and when using access points at various businesses. Running the 17June version now but I don't recall that issue when I was running the 16May version either.
[Samsung Galaxy Nexus] siealex:
Sometimes (several times per month) I can't turn on WiFi and need a hard reboot.
[Samsung Galaxy Nexus] ammarabbasi:
I'm using the latest build (06/17) and experiencing some unexpected battery drains due to cell radio, anybody have any idea what might be causing it? Do I need to flash an appropriate baseband img file?

Thanks.
[Samsung Galaxy Nexus] siealex:
It's a common 5.x problem and it will most probably never be fixed.
[Samsung Galaxy Nexus] siealex:
My phone often starts lagging and freezing (sometimes even soft-reboots) exactly at 3.00 AM (12.00 AM GMT). What's this and how to fix?
[Samsung Galaxy Nexus] kerpert:
Xposed unofficial for 5.1 won't be installed on my Nexus via f2fs TWRP.

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] n76:
Any odd things in logcat when it happens? Any indication of anything using excessive power?
[Samsung Galaxy Nexus] siealex:
No excessive power at all (the CPU remains almost cold). I'll try to catch it on logcat next time.
[Samsung Galaxy Nexus] E66666666:
I'm using the most recent build (06-17), but Vsync seems to be turned off? I get tearing, in the right half of the screen.

Uh, apparently it was CF Lumen and unrelated to the ROM.
[Samsung Galaxy Nexus] n76:
I'd like to make a request for the next build: To allow the microG's project's gms replacement to run apparently a patch is needed: https://github.com/microg/android_p..._frameworks_base+FAKE_PACKAGE_SIGNATURE.patch

It would be nice for those of us who are not loading a gapps package.
[Samsung Galaxy Nexus] chemtrails:
The best ROM till today for GNEX, to me. Thank you so much Zyan!

Is there a way to remove the Google Search Bar? (I don't know if already asked, sorry!)

Thanks to everyone!
[Samsung Galaxy Nexus] obscurer:
Google for "Google apps minimal edition" for 5.1.x

there is also add-on "Bloatware removal script"
[Samsung Galaxy Nexus] filenox:
Can someone tell me if this is fixed by now? :)
[Samsung Galaxy Nexus] osm0sis:
TK GApps lets you remove any system apk now, as well. :good:
[Samsung Galaxy Nexus] siealex:
Does ZMOD with its STOCK kernel support init.d? I can't make it work with stock kernel, but not with LuckyK.
[Samsung Galaxy Nexus] Punkiderma:
I tried: latest carbon, and your version of Franco's kernel. It's sad but true, my phone is again blazing fast. Maybe Lollipop is really too much for this phone?

The only thing I was asking myself is: is possibile that Kitkat drains more battery than lollipop?
[Samsung Galaxy Nexus] sergialess:
Yeah, it's the price to pay for running latest version of Android on a 3 yrs old device. Sad... and worth to give KK a second chance.

I'd love to have LP, but right now I'm running latest Dirty Unicorns (KK).

About the battery drain, maybe is true what you say. I'm not able to find what is constantly eating power, even using BetterBatteryStats and WakeLock Detector. I look at statistics and I see a little drainage all time. Perhaps it is normal...
[Samsung Galaxy Nexus] MaLiXs:
I got pretty bad battery life with my gnex, even on stock jelly bean... Perhaps our battery is unable to hold charge normally

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] sergialess:
Remember the Google Play Services, always being updated. They are source of constant FCs and Wakelocks. A nightmare...

So, not all the problem is the rom or SO version...
[Samsung Galaxy Nexus] MaLiXs:
If you read carefully my message I didn't blame the ROM or any other things except our old battery's...

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] sergialess:
It's uncertain, because some power cycles last more and other last less. Some cycles are awesome, and some are horrible. Some are better with a certain rom, some are worse with other roms. So... at the end, I'm not clear it's a battery problem but software.
[Samsung Galaxy Nexus] siealex:
It can be your 3G module, it constantly drains 2..3 % per hour.
[Samsung Galaxy Nexus] n76:
Interesting thought.

I haven't had any issues with excessive battery drain due to unknown causes. I usually have mobile data disabled and mostly use WiFi. And I am running software from the microG project so the wake lock issues some people have with recent versions of gapps does not affect me. Sounds like my normal usage patterns have avoided the issues others are seeing.

For me the screen is the big power hog. But I can minimize that by setting the brightness to as low as possible for any given lighting conditions.
[Samsung Galaxy Nexus] siealex:
On 4.4 it's true, but on 5.1 the CPU consumes much more...
[Samsung Galaxy Nexus] n76:
I haven't noticed a significant change in CPU coming from CM11 to ZMoD. OTOH, it seems that I don't use a number of the apps and frameworks that others have noticed triggering system power use.
[Samsung Galaxy Nexus] xuaozinho:
Doubts

Hi people, i need some help!

To use this ROM do i need to change the kernel or the system files to f2fs, or can i just flash it and keep everything else (ext4)?

Thanks
[Samsung Galaxy Nexus] MeHR@N:
Do a clean flash for first time installation of ZMoD, and no need to change file system to f2fs.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2633638]Ziyan[/MENTION] clean installs of TK GApps after 0726 fail once booted during the SetupWizard. I've verified this is because ZMoD doesn't have the patch to allow it to use Google Android WebView instead of AOSP's when installed. Can you add this patch for the next build?

I'd love to be able to set a custom bootanimation again too if possible. Thanks!
[Samsung Galaxy Nexus] bamtan2:
Is this anything to do with Google getting rid of the old "Browser" browser that can run Flash? I always liked having that browser as a backup to Chrome, et al!
[Samsung Galaxy Nexus] osm0sis:
Nah, it's just that most ROMs support switching to Google's WebView if it's detected so TK removes the AOSP one when it installs Google's; since ZMoD doesn't yet, it gets left with no working WebView and this causes many problems. :p

Easy workaround until Ziyan can add the patch is to exclude Google WebView from the GApps install using a .gapps-config file. :good:
[Samsung Galaxy Nexus] ardeus_ua:
It'll better have switching to google's webview
[Samsung Galaxy Nexus] Ziyan:
Sure, I'll add the secondary webview package name to the next build :)
[Samsung Galaxy Nexus] Reptilez_DK:
Using search doesn't kill you. ;)
[Samsung Galaxy Nexus] moovID:
This rom is very stable for me. Recomended for daily use.

Offline charge not broken on my own. Amazing work!!

Thanks ziyan.
[Samsung Galaxy Nexus] werty100:
With this ROM my gnex is not charging well when it gets to 98% it stops charging with other roms happen the same but with others no i think is kernel related in dreams rom it works well so is not phone is kernel
[Samsung Galaxy Nexus] ramosroger:
could someone please help this guy. it looks like he really wants to know but no one answered him.