yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kufikugel:
after searching what causes this only for some user we found the problem lol I added a hint on slimroms.net

http://www.slimroms.net/index.php/news/370-gapps-update-for-4-3

do this and you will have it back,

hmm no we did not change anything RIL related....anyone who can confirm that it changed? Will take an eye on it as well
[Samsung Galaxy Nexus] davidep85:
Done, now I can see calendar. Before flashing this gapps update, I was on a beta 2 clean flash and I didn't touch/install anything. It is strange that it shows an update!

The problem is that my sync and calendars are enabled, but I can't see the events related..
[Samsung Galaxy Nexus] vojkan22:
Less frequent notification sound doesn't work, it plays one after another as usual

Also, disabling camera shutter sounds silences only screenshot, actual camera app still makes a sound when taking picture
[Samsung Galaxy Nexus] mangusZen:
And again a clean flash seems to have solved this issue. Everybody should know that a clean flash generally solves 98% of reported issues but this , signal related, is quite strange to me.

I made a nand backup and then a quick clean flash, and bam, signal was again there , low but present. I restored the backup and

the signal was gone again , sitting on the same chair lol.

I made a complete clean flash and for now so far so good.

How this can happen is quite obscure to me but maybe this can help someone else

cheers
[Samsung Galaxy Nexus] Wossner:
Baseband didnt change from latest 4.2.2

What baseband did you flash?
[Samsung Galaxy Nexus] flashbac76:
Just a tiny little bug : quick peek is not working with dots game.

Enviado desde mi Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] mangusZen:
The one that comes with google 4.3 stock image. I know it should be the same, but just to be sure...
[Samsung Galaxy Nexus] navyanup:
anyone has flashable zip file for new baseband of 4.3
[Samsung Galaxy Nexus] bartolinio:
again: baseband is the same as in 4.2.2!

XXLH1

XXLJ1
[Samsung Galaxy Nexus] AbhishekS:
It seems there is no option to play around with voltages under Settings->Performance.

I want to undervolt, but can't. Even by modifying using Trickster, the settings are lost after a reboot.

So can we get voltage tweaks under Performance?
[Samsung Galaxy Nexus] drmxmyt:
dots game hides the statusbar. how could it work?

tick "set on boot" on trickster. also you can use init.d scripts to set it.
[Samsung Galaxy Nexus] flashbac76:
That's what quick peek does. Let you take a peek at your status bar in full screen. ;)

Enviado desde mi Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] Kurre:
I haven't really used that feature, but could it be that it only works when you're using auto hide statusbar feature? So it's not available when app is hiding the statusbar by itself. Thus you can't force statusbar to appear if app wants to keep it hidden.

Sent from my Nexus 4
[Samsung Galaxy Nexus] Nebucatnetzer:
I really don't think that's something which should be added to the ROM.

We only would end up with tons of posts about people stuck in a boot loop.
[Samsung Galaxy Nexus] Nebucatnetzer:
Would make sense but I don't use it as well so I can't say it for sure.
[Samsung Galaxy Nexus] flashbac76:
This is what [MENTION=4790322]kufikugel[/MENTION] was saying here :

I usually use this function, and it works just fine with other apps. But, like I was saying , it`s just a little bug and it's not so important.
[Samsung Galaxy Nexus] standa75:
Trickster is working without problems for me. Undervolted values sticks after reboot..maybe you forgot to select aply settings after boot.also when installing new kernel, do not forgot to clear trickster cache/data before installing kernel.
[Samsung Galaxy Nexus] coolek33:
Great rom. 1 thing bothers me. Cant see miniature of a photo in recents window any more. I was using this alot. Can U please do something obout it?
[Samsung Galaxy Nexus] Punkiderma:
I noticed that even if I set the root access to "Apps & ADB", android commander on my pc still says "You need root access!" when I try to copy something from my pc to the system folder.

Someone other also have this problem?
[Samsung Galaxy Nexus] kufikugel:
hehe true.....first time that I hear that an app can disable this.

But in general it works with all apps...try YouTube or templerun or whatever full screen apps you can swipe it down.

---------- Post added at 11:57 PM ---------- Previous post was at 11:53 PM ----------

hmm weird...works here...will test it deeper

does android commander send su command? I mean adb su etc etc. This needs to be done on 4.3
[Samsung Galaxy Nexus] Punkiderma:
Honestly, I don't know XD

But it's a while since the last update(and sure was before 4.3), so I think you got the problem.

Do you know a similar software that works on 4.3? (root file management, apk installing and things like that, with a simple and light GUI?)

Thanks!
[Samsung Galaxy Nexus] coolek33:
Try it with photosphere installed. Thats what i have it.
[Samsung Galaxy Nexus] ChazzMatt:
Neither baseband nor RIL changed from 4.2.2 to 4.3. And the RIL in your ROM is the one you should use, forget RIL (if you are flashing a new ROM). Go see the baseband Galaxy Nexus thread, they same the same thing. :)

http://xdaforums.com/showpost.php?p=43558010&postcount=2271
[Samsung Galaxy Nexus] kufikugel:
thanks and fixed

https://github.com/SlimRoms/frameworks_base/commit/abc572625d31d9cad3ddc0d0dfd84e471b0abf78

https://github.com/SlimRoms/frameworks_av/commit/36be5192def963315e4538b05244bc4b2e74f1ef

as well I think interesting for some due that was a long time issue on 4.2.2 already latest changes allows now to fix it easy

https://github.com/SlimRoms/frameworks_base/commit/99e68396b8a84ea229242a41b7c20080a9421050

for ppl without gnow there was another issue as well fixed

https://github.com/SlimRoms/frameworks_base/commit/bafbfc20f0b5d9ea2213f3fed1bbcc53fde5c4bb

and the sometimes not updating widgets

https://github.com/SlimRoms/frameworks_base/commit/663f759a9dbc18f981f28e7d0fdf490f444bdb93

+ some google derps we fixed as well last days

just to show a bit that we are still working to make it perfect before we start again to develop new features lol
[Samsung Galaxy Nexus] vojkan22:
great. but I found one much bigger problem: memory leak. here are some screenshots

no1 i no2 are showing the problem (check uptime and free ram)

no3 shows how big is memory print of Android System and SystemUI (this one is taken after second screenshot, so ~5.5hours uptime)

fourth shows how big are they right after reboot.
[Samsung Galaxy Nexus] castaway1:
same memory leak issue here
[Samsung Galaxy Nexus] sago62:
I can not restore the apk with tb ... I have to flash supersu?thanks
[Samsung Galaxy Nexus] Tim4828:
I have the same issue. Hope next release will resolve it.
[Samsung Galaxy Nexus] coolek33:
Enable root access to apps and adb. In TB set backup folder to legacy not 0.
[Samsung Galaxy Nexus] kaiyoto123:
+1:good:
[Samsung Galaxy Nexus] kufikugel:
So.....do not get me wrong...but that shows nothing. It it absolutly normal on linux that apps (as well android system and systemUI) takes there mem when services are started or needed....when not they will stay and will only be freed after another app maybe needs the space. Thats the magic of linux/android ram managment. To show that it grows shows nothing.....I can give you 2 days uptime.....with between systemUI 70Mb and some hours after 39 :rolleyes: Easy thing you can try.....check with a ram diagnostic tool (OS Monitor eg) open PIE you will see suddenly it jumps up....close it....it goes a bit down. Close all recents apps...systemUI goes dramatically down. It just depends on how much systemUI needs (notification wallpaper is as well systemUI) it will fetch what it needs...and give free if any other system or app needs the space.

Anroid system as a side not is not only dependent on the rom. Lot apps can start services or actions which can cause that-

You can read up on our homepage FAQ how it worky. A better and more realistic ram calculation you can see as well on recents rambar (activate cache + other) due that this reads real values from proc/meminfo out and not the weird ones like AOSP is doing.

When you say that you have now suddenly all apps closing (normal usage) then I would say yes it is a problem. All other the number 1 sentence counts on linux: free ram = wasted ram

change as said in devloper options to app & adb and till tibu is not updated you need to change the backup/restore folder in tibu settings to "legacy" then it works. No need to flash superSU which breaks more then it is helpfull IMO
[Samsung Galaxy Nexus] castaway1:
i dont want start any kind of flame war here so dont get me wrong no complain to ROM, im just want to say this.

I know this is ROM problem not kernel or android system. It was same on 4.2.2. I tried use complete stock google (with root) for 7 days. And RAM was never drop below 180MB even with game in background. I was able switch to game, then home, music player, google play then go back to game and it was still running in background so it just switch to it.If you are right then why stock google ROM is ok with this?

Other side is customROM like Slim. Maybe you are right but my research is based on what i feel whish is start lag when RAM bar is bellow 100MB. This number is getting closer to zero.

I know free RAM is wasted ram i agree with this. But free RAM bar in android is used as cached proceses. So if "free RAM" is 30MB then you have zero multitasking and for some bug it cant free RAM it is still increasing till you are forced to reboot.

peace :)
[Samsung Galaxy Nexus] vojkan22:
1) I agree that "free ram = wasted ram" BUT that sentence refers to literally free ram (empty if you wish, useless). The problem is, in android's built-in "task manager" (shown in first two screenshots), "free" ram is empty ram + cached apps. Maybe better term for that would be "available" RAM. So when it goes down to 25MB, there are no cached apps! Or one small at best. Everything keeps reloading. Webpages, whatsapp service, apex... Multitasking is literally non-existing.

2) On stock ROM, or custom ROMs based on stock, this problem doesn't exist. With my setup (and it is always the same), free (or available if you wish) RAM never goes in double digits, most of the time it hovers around 150MB. Lots of apps cached then.

I dont know if this is JWR vs JSS issue, but I do know that this is same story as on 4.2.2. Every AOSP ROM had this problem, CM fixed it to some extent, and stock or stock based were the only ones that didn't have it (among those that I've tried)
[Samsung Galaxy Nexus] jackbane:
Great work again, much thanks to the Slim team! Loving Beta 2, very stable on my phone. I have one small glitch to report. If I run the camera app (photosphere not installed) and turn the phone so the orientation flips before the the app comes up, the lens does not turn on, the screen stays black with just the camera nav buttons appearing. Turning the phone to flip the orientation only moves the buttons around, the lens remains off and the screen black. I have to back out or kill the app and then run it again, without flipping the orientation of the phone and then the lens turns on.

Im on a clean install of the latest beta. Thanks again to the devs!
[Samsung Galaxy Nexus] kufikugel:
uh wait that are two partys

to compare a stock rom with a custom rom does not work. Ppl need to realize that full integrated mods they want to have are using ram. Simple thing....custom QS tiles...every tile you add needs its space. Every color or image thing you can customize takes its space. There is no way around it. Stock rom does not do this at all and of course can be lower in the memory foot print and this will never change. Even cm which does not offer that much customization have a bigger memory foot print then every Stock firmware which is available. Combined with the growing apps (see all the new google app and services which got last 2 month enormous memory consumption) this is especially for low end devices from year to year a bigger problem (I still wonder that sgs devices can handle it).....see mako...they do not care at all due that it grows till a certain point and stops they have a lot mem included so no problem

So at least what I want to say

1. maybe there are new memory leaks in 4.3...but I doubt it due that they did not change in this case much (especially SystemUI)

2. features like this without memory use = not possible

3. to help to track that down if it exists it needs to be messured without any 3rd party apps installed for first. Other then that the result is useless due that 3rd party apps can effect that much. Especially in the early stage of 4.3 and a lot apps did not update at all. Then it needs to be messured over severall days if it is all the time growing.....or if it does stop on a certain point. If it is growing without stop we need to know the exact setup. As I said we have even on the low low end device not this problem currently. Me myself on maguro (low end device) absolutly not. As well tracing the memory handling via trace developer tools does not show anything unusual.

4. just a side not the memory leak problems on 4.2.2 was a cooperation from cm, aokp and slim....cannot stand to read every time cm solved it. They were the last one at this party.

5. of course let us discuss it here....we are on a developer thread and I am happy to discuss everything about this. But we need a same base on results and messures to get deeper into it. The screenshots does not show much at least

6. and last one.....apps get not laggy when they have low memory....the only thing what happens that an app can get laggy then if in the background other apps are killed and the system tries to get memory free which can be seen very easy

:)

EDIT: about jw vs JSS this is only a discussion about mako (and was for flo now solved) due of problems in qcom display and kernel patches. Does not effect maguro at all
[Samsung Galaxy Nexus] openlatedotorg:
Does the AOSP calendar show text of events when in month view? Mine doesn't after update and I really enjoyed seeing what my events were, rather than just a coloured bar.

Thanks again everyone! Rom is rocking!
[Samsung Galaxy Nexus] vojkan22:
yes, I have a friend that has N4 and he doesn't have a slightest idea what am I talking about... To him, 600 or 800 MB used are totally the same... :D

but, about other things you said... i really don't use that much of customization options. for example, QS tiles that you mentioned are disabled :) I only use power widget. On the other hand, on Cataclysm ROM (custom stock based, that I mentioned earlier) I use power toggles, so that's more or less the same thing... Little resizing of navbar, assigning actions to long press on navbar buttons and thats about it. and all of this I also use on google based ROM.

I understand your doubts... but trust me, I know what I am talking about :) I'm always using the same apps, I even do not have many of them, about 40 user apps... Kernel is also always the same, only variable are ROMs, so it's easy for me to spot something like this. apps that I use (running as service in background, counting in "used" ram):

- facebook (this one gets killed often on every ROM)

- whatsapp+

- lux auto brightness

- swiftkey instead of stock keyboard

- nova or apex (last few weeks apex, but they are essentially the same)

- dropsync

yes, not apps, maybe [MENTION=2195826]castaway1[/MENTION] didn't use the right word, but phone itself gets slow and sluggish... I'm viewing a web page, receive IM on whatsapp, switch to it to answer, then go back to browser and it's loading the page again :/ Because it does not have ~50MB of free RAM for caching it... You press home button and launcher redraws itself... every operation that should take 5ms then takes say 2-5 sec... and it's noticably slower ofcourse

now I know that you for some reason don't like screenshots :D but as they say, picture is worth a thousand words... custom stock based ROM, same kernel (fancy r39) same apps (I wrote them above), uptime and free ram are obvious... and that's with apex at 60+ MB, it usually sits around 40... huge difference in phone's behaviour when it has 30-40-50MB of free RAM an when it has 130 - 140 - 150 MB free...
[Samsung Galaxy Nexus] buckowski:
I've found minor issue with slim gapps calendar. With original Google calendar everything works fine but with real black calendar from slim gapps I'm not able to change color of my calendars and events.
[Samsung Galaxy Nexus] hardstyle86:
Hangouts crashes when I try to videocall a person...
[Samsung Galaxy Nexus] Doublewise:
Hope this discussion about memory issues will broaden our knowledge to improve our beloved Rom -)
[Samsung Galaxy Nexus] dancingtortoise:
Does anyone have the stock lockscreen logo? I can't seem to locate it on the slim website.

Edit...never mind, not where I remembered it being.
[Samsung Galaxy Nexus] Nebucatnetzer:
http://slimroms.net/index.php/bugs
[Samsung Galaxy Nexus] hardstyle86:
OK, tried this, even i'm not very expert.

This is the interesting (I believe) part of the LogCat:

[ 08-22 09:34:31.260 4324: 4324 E/AndroidRuntime ]

FATAL EXCEPTION: main

java.lang.UnsatisfiedLinkError: Couldn't load videochat_jni from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/com.google.android.media.effects.jar", zip file "/system/app/Hangouts.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]]: findLibrary returned null

at java.lang.Runtime.loadLibrary(Runtime.java:355)

at java.lang.System.loadLibrary(System.java:525)

at com.google.android.videochat.Libjingle.<clinit>(SourceFile:47)

at com.google.android.videochat.RendererManager.<clinit>(SourceFile:27)

at com.google.android.apps.babel.hangout.renderer.GLView.a(SourceFile:150)

at com.google.android.apps.babel.hangout.HangoutFragment.onCreateView(SourceFile:321)

at android.support.v4.app.Fragment.performCreateView(SourceFile:1470)

at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:898)

at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1080)

at android.support.v4.app.FragmentManagerImpl.addFragment(SourceFile:1182)

at android.support.v4.app.FragmentActivity.onCreateView(SourceFile:280)

at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)

at android.view.LayoutInflater.inflate(LayoutInflater.java:469)

at android.view.LayoutInflater.inflate(LayoutInflater.java:397)

at android.view.LayoutInflater.inflate(LayoutInflater.java:353)

at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:318)

at com.actionbarsherlock.internal.ActionBarSherlockNative.setContentView(SourceFile:119)

at com.actionbarsherlock.app.SherlockFragmentActivity.setContentView(SourceFile:251)

at com.google.android.apps.babel.hangout.HangoutActivity.onCreate(SourceFile:53)

at android.app.Activity.performCreate(Activity.java:5201)

at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2293)

at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2389)

at android.app.ActivityThread.access$600(ActivityThread.java:153)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1269)

at android.os.Handler.dispatchMessage(Handler.java:99)

at android.os.Looper.loop(Looper.java:137)

at android.app.ActivityThread.main(ActivityThread.java:5287)

at java.lang.reflect.Method.invokeNative(Native Method)

at java.lang.reflect.Method.invoke(Method.java:525)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:554)

at dalvik.system.NativeStart.main(Native Method)

[ 08-22 09:34:33.292 511: 570 E/InputDispatcher ]

Received spurious receive callback for unknown input channel. fd=194, events=0x9
[Samsung Galaxy Nexus] Punkiderma:
I also have this problem.

I was able to solve it after some passages(like delete calnderprovider and things like that, I don't remember well now), but wasn't that simple(at a certain point my calendar stopped syncing and I had to reflash again) and, after updating the rom, the problem was back, so I gave up.

For me is like that: when I change calendar color, after some seconds they turn back to the color before
[Samsung Galaxy Nexus] ChazzMatt:
Exactly. Yes, free RAM = wasted RAM, but only up to a certain point. Our Android systems need also need a buffer of FREE RAM to function effectively.

There was another custom ROM -- Xylon a few months ago -- that sucked the free RAM to very low amounts, causing lag. There were severe memory leaks and the developers were loathe to admit it, citing the "free RAM = wasted RAM" phrase incessantly -- which becomes quite irritating. :rolleyes: It becomes a denial there is a problem, when in fact there obviously is a problem. When I switched to Slim ROM, 4.2 a few months ago that low RAM problem disappeared -- which proved it was Xylon at fault. (May have been fixed since then, I don't care. I can still use that problem at that point in time as an example of bad performance and developer blindness.)

Normally, on my Galaxy Nexus I have 80MB - 100MB free RAM at any given time. If it falls below that, I start having severe lag. It means Android OS is not releasing RAM or stopping unnecessary apps in the background, or SOMETHING.

I am not making any comments on the 4.3 beta. I've flashed it a couple of times but keep going back to my CWM 4.2.2 SlimRoM Build 8. I haven't run 4.3 beta long enough to notice low RAM. I'm just pointing out that if RAM is dropping below 80MB - 100MB on Galaxy Nexus, the "free RAM = wasted RAM" gets thrown out the window. Don't even say it. :rolleyes: At that point, investigation is needed to see WHY RAM is dropping that low. Find the cause. May be the ROM, may be something else. But it's WRONG.
[Samsung Galaxy Nexus] mangusZen:
I agree 100%. Thats true for linux systems also. When coding some mem leaks can happens , it's really up to devs skills, experience and attention.

In my linux systems, with 8 gb of ram, the usage is quite stable around 1gb for normal operations, obviously ram is not fullfilled. If thats happens something is going very wrong.
[Samsung Galaxy Nexus] jmcdonald58:
I run usally 150mb+ of free Ram after install - after I have a day or 2 of uptime then it reduces I was reading this conversation and decided to check mine Now remind you I haven't rebooted since installing this build I was at 25mb of free Ram and was experiencing some lag so I wiped the caches and I am know around 165mb,maybe I have misunderstood but I am going keep an eye on it the next few days and see what happens I used the phone daily at work
[Samsung Galaxy Nexus] stevensoaj:
Now, this is with zRAM enabled, but I'm at about ~34 hours uptime. I guess I'm not having the problems you guys are. I'm on Fancy r39-ext. Great performance no matter the uptime.

Perhaps it's because I use greenify? Who knows...
[Samsung Galaxy Nexus] vojkan22:
so we are using same kernel and rom and get different behaviour, interesting. It isn't about greenify because I dont use it ever and again dont have this problem on other roms.

One thing that comes to my mind that is different between your and my phone is TRDS. You're not using it and I do. Could that be a reason [MENTION=4790322]kufikugel[/MENTION] ?
[Samsung Galaxy Nexus] jmcdonald58:
I am really not having any issues - I think after 3-4 days of uptime a simple wipe should clears out whatever is chewing up the ram for me it seems to be more of an app issue rather than Build anyway its gotten much better since the Donut days :laugh: