yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] stevensoaj:
I'm still having audio issues. I am on a clean flash. I play a song at full volume, then turn down the volume while the song is playing and hear nothing (good behavior). Then, while the volume is turned all the way down, I pause the song. When I press play again, the song plays at full volume, despite media volume being turned all the way down (bad behavior). Even other apps (Audioglow) that recognize current volume level show the volume as turned down, but the speaker is playing at full volume. I have to adjust the volume after unpausing the song for it to adjust to the correct volume. This is with Google Play Music from the play store.

I'm on beta 3. Here's the logcat.

http://db.tt/OZPC8AQA
[Samsung Galaxy Nexus] kufikugel:
hmm weird....just tried it and indeed heavy memory allocation problems with 3rd party apps. I will investigate it. A lot changed in screenshot handling....not sure what is exactly the cause

at least for me it is fixed on the latest internal unofficial build. Should be fine with next weekly
[Samsung Galaxy Nexus] ChazzMatt:
YES, I know how to do that. I submitted a bug report yesterday on the Voice Dialer, because I KNEW it was a bug. And YOU thanked me.

I'm asking if anyone else has any information on this issue before I report an alleged bug in SlimROM that instead turns out to be an issue with Android 4.3 borking screenshot apps.

Are YOU admitting it's a bug? :rolleyes: Then, I'll get a catlog and submit a bug report.

---------- Post added at 05:51 PM ---------- Previous post was at 05:47 PM ----------

OK, so admitted it's a bug. Thanks for clearing that up. Do I still need to submit a logcat or do you personally have enough info from your experiment?

By the way there's several free screenshot apps as well as trial versions of paid apps that I tried. If you need a list to try, I'll be glad to supply.

This is the one I used for a long time, even before I got my Nexus.

___________

Screenshot ER DEMO

https://play.google.com/store/apps/details?id=fahrbot.apps.screen.demo&hl=en

(says demo version, but except for upper right logo stamp it works perfectly, perpetually.)

____________

I left a bad review on Google Play that it now doesn't work with 4.3, which I now need to retract. :( I've paid for the developer's other apps, like Root Call Blocker.

After that failed, I installed others and found they also didn't work. So, I started wondering if it was 4.3 in general or SlimROM 4.3 beta 3....

Thanks for investigating.
[Samsung Galaxy Nexus] kufikugel:
thanks I do not need for this issue a logcat. The logcat does not show anything only that it was successfull lol....just black result on 3rd party screenshot apps. Will check first on stock if it is a 4.3 problem and then diving more into it. Tbh never used a 3rd party screenshot app due that the system provides so many screenshot possibilities (navbar, pie, navring, hw key, power menu etc) lol
[Samsung Galaxy Nexus] diSke:
Finally had the time to test a 4.3 weekly! Fully erased my phone, flashed 4.3 bootloader via fastboot, flashed stock system, data... and flashed the new beta 3.

I don't know whether it's mentioned already since I didn't follow the thread as close as before but sometimes it seems like my back button is unresponsive.

For example I'm in the settings menu and want to go back, I press the back button several times (10-15 times) nothing happens and I have to use the home button to

take me back to my homescreen.

Also not sure if it was a rom feature but I used to disable the widget group in nova launcher's appdrawer.

Can't seem to locate it. Perhaps I'm overlooking something direclty in nova launcher?

First afternoon testing but works like a well oiled machine!

Awaiting the first stable build to test some kernels ;)

Good job so far guys!
[Samsung Galaxy Nexus] ChazzMatt:
With SlimRom 4.2 I had to use the app's "alternate" method of taking a screenshot. With SlimROM 4.2, it showed black using the default method (which had always worked before), but I thought it was something that changed with 4.2. But most of the screenshot apps have an "alternate" or "slow" method, which work when default does not. However, now with SlimROM 4.3, neither works.

So, when testing, be sure to also try the "alternate method"?

______________

Screeshot ER Demo

https://play.google.com/store/apps/details?id=fahrbot.apps.screen.demo&hl=en

_____________

Screenshot It

https://play.google.com/store/apps/details?id=com.edwardkim.android.screenshotitfree&hl=en

_____________

I used screenshot app for my LG Optimus M and my LG Esteem, before I got my Galaxy Nexus which has "native" ability. But I like the screenshot app options, instead of holding down the volume/power button at the same time.

You are right, SlimROM does give other screenshot options I had never paid attention to (since I liked using the app with either countdown or "shake" activation). I've now added screenshot option to the power menu. I had taken everything off except for Power Off and Reboot, as I don't like a cluttered Power Menu. But I need screenshot capability. :)

If you can get the screenshot app capability working, thanks. Who knows, might also affect other aspects of the ROM? If you find it also does not work on stock 4.3, then sorry for the bother. That's why I was asking if anyone else had encountered the issue.

Thank you again.
[Samsung Galaxy Nexus] coolek33:
Someone mentioned about back button not working but works fine here. Try it in Slimpie maybe. And the widget group can be removed/add here...
[Samsung Galaxy Nexus] Nebucatnetzer:
The thing is that those question are IMO redundant.

This guide exists exactly for investigating in bugs. There's no need to post such questions if you would follow that guide.

If you can reproduce the bug on a clean install then you should post here the detailed steps to reproduce it and which apps needed.

If it doesn't happen on a clean install then there's nothing to post.

That guide isn't only there to help getting us logcats it's the as well the only correct way to track a bug.

This is btw not only meant for you but for everyone.
[Samsung Galaxy Nexus] bunnycool:
no problems here mate !!! works like a charm !!

---------- Post added at 07:10 AM ---------- Previous post was at 07:05 AM ----------

its not a bug..its working fine with me !!!
[Samsung Galaxy Nexus] samumar82:
Hey guys I've been on 4.3 beta 3 for 10 days now and it seems fine to me.

I flashed Franco Kernerl #391 and I have less battery drain now.

Also I installed Nova prime and made some customizations like changing the animated boot image and other small things.

My question is: when the stable release will be out, can I use the slim center and the ota update without loosing all my modification such as kernel, nova prime instead of the free version and so on?

Thanks a lot and keep up the good work!

(also using slim on my gf's old i9000, working like a charme!)
[Samsung Galaxy Nexus] LibertyMonger:
Sounds like the apps have issues, maybe they are not ready for 4.3!
[Samsung Galaxy Nexus] dirtygoldfish:
You could try dirty-flashing the stable when it's released (ie: don't wipe anything but cache and dalvik cache) and all of that would be untouched, although you might run into some bugs. If you wipe /system and /data however, all apps will have to be re-downloaded, the boot animation will have to be changed again, etc. It's more of a hassle, but personally I always prefer to do a clean install.
[Samsung Galaxy Nexus] Nebucatnetzer:
The kernel will get overwritten.

Nova Prime is only an unlocker so those settings will stay.
[Samsung Galaxy Nexus] samumar82:
Thanks a lot for your quick replies!

Inviato dal mio Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] diSke:
Thanks! Been searching in Nova Launcher and the exact same spot as you say but couldn't find it. Now I did though!

About the back button, probably my fault. Will do some more testing on this.

Thanks for the reply's
[Samsung Galaxy Nexus] hardstyle86:
Hi!

I love this ROM! :laugh:

But... is there any possibility to see the AOKP Ribbons introduced in the Slim Bean?
[Samsung Galaxy Nexus] Nebucatnetzer:
We decided against it. There are more than enough options in Slim to achieve a similar function.
[Samsung Galaxy Nexus] diSke:
[MENTION=3609932]Nebucatnetzer[/MENTION]: Any ideas what new features you'll be implementing with 4.3? Or does it depends whether someone is in the mood to implement something from the features list? Just excited and curious about whats coming!
[Samsung Galaxy Nexus] Nebucatnetzer:
No plans yet AFAIK. You have to keep in mind that not every device was as fast up as the Nexus devices.

Maybe in one or two weeks we have some ideas.
[Samsung Galaxy Nexus] bartolinio:
for me personally, the only features missing: these are keys left/right appearing together with the keyboard
[Samsung Galaxy Nexus] hardstyle86:
For example? :D

Anyway, the ROM is very good.

Thanks for the quick answer.
[Samsung Galaxy Nexus] Nebucatnetzer:
IIRC ribbon is a way to have shortcuts at hand right? So for that you could use, notification shortcuts, pie or navbar shortcuts.
[Samsung Galaxy Nexus] Natakranta:
I agree with Nebucatnetzer. I set one ribbon when I was still on AOKP Milestone 2 and guess what, I've never used it. I kept forgetting it is there. Nova and Slim gives me more then enough customisation options. Though three is one thing from AOKP I am missing. That's Navbar on/off switch in power menu. It was a safe mode for me when LMT pie stopped working. I know there's pie in Slim ready to be used and faster and smoother than LMT, but LMT has some options I'm used to.

And btw LMT is freezing and switching off a lot since I'm on beta 3. I see messages saying LMT granted root access randomly every hour. Sometimes it comes back, sometimes I need to restart the app.
[Samsung Galaxy Nexus] stevensoaj:
Couldn't you use expanded desktop to toggle navbar? That's what I do. I have mine set to not hide the status bar, so its basically a navbar/pie toggle.
[Samsung Galaxy Nexus] Natakranta:
Man learns every day :)

Thanks a million for this tip! Somehow I missed it in the settings.

Slim settings structure is still mystery to me.

Slim ROM is great and this thread support is fantastic, both developers and users.

The force is strong with this community :)
[Samsung Galaxy Nexus] Tribes11:
Is is possible to add on this ROM an option to change glow color on navbar and option to have AOKP battery icon along with circle battery?

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] Seraz007:
u can change glow color

Navigation>Nav Bar>Buttons>Button Style> Glow Color :)
[Samsung Galaxy Nexus] Tribes11:
Thank you sir, that worked, I just missed this option cause it's a little different from other ROMs I've tried lol, so I missed this option.

About the AOKP Battery Mod, do you think it's possible to have it added to the Battery Icons menu?
[Samsung Galaxy Nexus] Seraz007:
Don't know which battery icon you are wanting but here is a thread with an enormous amount of battery mods :D

http://xdaforums.com/showthread.php?t=2397545

Just be sure read this thread http://xdaforums.com/showthread.php?t=1574401

for installing the framework first and then the mods :)
[Samsung Galaxy Nexus] ChazzMatt:
That has not been confirmed. It may work perfectly fine on stock 4.3.

I don't know, I never flashed stock 4.3 and have no desire to. I was asking if anyone else has encountered the situation before I reported a SlimROM bug that might actually be a stock 4.3 issue.

---------- Post added at 12:26 PM ---------- Previous post was at 12:22 PM ----------

We are going to have to just disagree about this.

I am loathe to falsely report a bug on SlimROM when possibly it's an issue with 4.3 in general. If I did a clean install of SlimROM and a 3rd party app does not work, that does NOT prove anything if it also does NOT work on stock 4.3. That is NOT a SlimROM bug, no matter how many times you can reproduce it on a clean install of Slim ROM.

With the Voice Dialer, I KNEW it worked on stock 4.3 as that is a Google Android app. I could also prove it did NOT work on SlimROM. Thus, I reported it as a SlimROM bug and included a logcat.

I do not have that same knowledge with these 3rd party screenshot apps. Do you understand?

So, I asked others in this thread, who are using the same device I am and using SlimROM 4.3 betas if they have any additional information. Some of these people have installed stock 4.3, or may have some information I do not know.
[Samsung Galaxy Nexus] bunnycool:
i have heard about this problem in many roms !! but luckily never faced it..:cowboy:
[Samsung Galaxy Nexus] Nebucatnetzer:
Maybe this helps a bit.

http://slimroms.net/images/galleries/SlimBean feature overview/p1824s2qse1nlfb0mvdb1h9v1u2h4.png

We won't add any more battery mods to the ROM.
[Samsung Galaxy Nexus] ivanlaszik:
Is there any way to change the value at which the low battery alarm/event goes off ? I would like it at 5%. Also would it be possible to set two alarms ? One, lets say at 15%, another one at 5%, and different sounds for the alarms ?

I found some information about this, that its in an integers.xml file in the framework-res.apk defined, but that was in a thread on some forum back in 2011, and I cannot find such a file. Probably this has changed since ICS or JB ?
[Samsung Galaxy Nexus] shreddintyres:
The way i understand it is how busybox calls SU, Kusch and Chainfire use different methods of calling dameonsu the exact reason i forget but in any case i have found that using /sdcard instead of emulated or legacy works just fine, all apps are humming along nicely, ill probably do a full wipe for alpha build 4 when it comes out and make sure everything is on /sdcard instead n see if there are any differences.

My understanding was that the reason for the emulated and legacy folders were because of the partition changes from ICS to JB and this was just the easy symlink way of getting around it
[Samsung Galaxy Nexus] stevensoaj:
I also fixed a lot of issues in root file browsers by using /sdcard instead of /storage/emulated/0, as I posted above.

Also, since I can't get Bug Reporting in Slim Center working, I created a script to fetch a logcat(with timestamp) and last_dmsg and put them in the /sdcard/Slim/Bugreport directory. Here it is if anyone wants it. ---> https://www.dropbox.com/s/b3s6yctgss1359u/Slim Bugreport.sh

I originally got the script from an AK Kernel build, but I made lots of changes to only get the logcat and last_dmsg. It only gets the last 500 lines of the logcat to make it easier to read, so it will only help if the bug/issue happened relatively recently before pulling the logcat. It's a temporary solution until Bug Reporting is working in SlimCenter and it can be used without downloading additional apps (if you have a way of running scripts of course), which is why I made it.

Also, I don't know how it worked before because I never tried it before these alpha builds, but it would be nice to have some sort of notification of when the bug report has been completed when using the SlimCenter bugreport feature.
[Samsung Galaxy Nexus] zy2zyy:
thanks for replying. it seems like that's impossible..

welcome to china sometime. :p
[Samsung Galaxy Nexus] castaway1:
for me build in kernel is very good i had 1d 4h with 2.5h screen on. (i dont remember when i had results like this before, if any.)

only problem i have is low free memory like 20-60MB so i have to reboot every day or two. alpha 3
[Samsung Galaxy Nexus] Nebucatnetzer:
Free RAM is wasted RAM

http://slimroms.net/index.php/faq/slimbean/238-why-do-i-have-less-memory-free-on-my-device
[Samsung Galaxy Nexus] castaway1:
as far as i know "free" RAM in android App - > Running is used for cached background processes so if there is for example 30MB then only few apps can be cached..but if there is 200MB ..its different. I can feel that its low by just using phone as it start to have delayed reactions.

no complaints i love this ROM :good: it was same on 4.2.2
[Samsung Galaxy Nexus] gamerman123x:
I'm on build 3.1 alpha and I wanted to change my DPI to 320 but every time when I change it and press rebbot it always goes back to the original dpi settings that came with the ROM just wondering if other people have this problem Thanks:confused:
[Samsung Galaxy Nexus] vivekbalan:
You need to set Root Access to "Apps and ADB" in Settings > Developer Options to get root access to change dpi.
[Samsung Galaxy Nexus] gamerman123x:
Thanks it worked :)
[Samsung Galaxy Nexus] sago62:
installed everything, but android.process.media always crashes ... and can not access the internal memory via mac ... resolutions?
[Samsung Galaxy Nexus] Nebucatnetzer:
How did you install it?
[Samsung Galaxy Nexus] sago62:
did wipe all + data ... then I upgraded supersu, but does not go ... even with windows reads the memory, always gives the same error ...
[Samsung Galaxy Nexus] zulu90:
do you installed another kernel?
[Samsung Galaxy Nexus] Zanera:
Finally had the chance to test alpha 3.1 and I have to say the built in kernel with this rom are a perfect combination. I do have more wifi drops as usual but I have to test my ethernet controller first before I blame the rom. Beside that I'm having a 4% drop in about 8 hours idle which is very nice.

Check out the battery life ! (Used wifi for a few hours but mostly 2G network and was connected to usb for 1 minute.)

Still cant find any major bugs. Great job !:good:
[Samsung Galaxy Nexus] stevensoaj:
[MENTION=3609932]Nebucatnetzer[/MENTION] would it be logical/beneficial to have the default root access setting changed to "Apps and ADB" so that users won't post root related issues as bugs, or would that not fix the issue?
[Samsung Galaxy Nexus] geckocavemen:
The new Android Device Manager (locates a lost phone with ring and wipe feature) doesn't work on Alpha 3.1. The ADM website interface didn't even recognize that I had a Galaxy Nexus. I then restored a stock 4.3 backup and ADM worked and the web interface found my phone. After that I restored my slim Alpha 3.1 backup and it stopped working (wouldn't locate my device and the ring phone feature didn't work).
[Samsung Galaxy Nexus] standa75:
As I can see there are not big issues related to alpha 3.1, so I would like to request possible feature for next release...is it possible to use default dpi for 3rd party keyboard as well as use custom dpi for the rest?I know this work for stock keyboard, but I would like to use 3rd parties keyboard too, which is almost not possible for custom dpi now, or am I missing something?

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] drafgnjom:
Happy to see 4.3 slim bean :) Will update when v4a is compatible with 4.3 roms. Thanks for the ROM again :)
[Samsung Galaxy Nexus] Nebucatnetzer:
It's not that easy unfortunately.

However we're discussing this already internally.

For the beginning it would already help if the people would read the OP and the thread.

Works fine here.
[Samsung Galaxy Nexus] Nebucatnetzer:
No feature requests until we're out of the experimental phase.

We won't include per app DPI due to the fact that it doesn't fit into our concept.
[Samsung Galaxy Nexus] samumar82:
Hangout videocall keep crashing on slim 4.3 beta 3 witho franco kernel 391

Inviato dal mio Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] 1haumann1:
Known issue.....read on slimroms.net

swyped from my maguro
[Samsung Galaxy Nexus] Kurre:
I just tested those screenshot apps with stock 4.3 (JWR66Y) with and without root.

Without root, none of the tested apps were able to make a screenshot.

This includes many which "promise" non-root screenshots (actually those seem to rely on windows/mac connection etc.).

With root (SuperSu) I were able to make a screenshot.

In Screenshot Ultimate app, I used automated detection of working capturing methods and only one resulted a non-black picture (capture method root 10).

So it's actually possible to grab screenshots with Android 4.3, but it seems that working methods are quite limited.

So most likely problems lies in apps, if they doesn't support this working method.

I'll do more testing tomorrow (it's movie evening now.. :p ) with stock 4.3 and other apps and with slimbean 4.3 beta 3.

After that I'll push some data to SlimTeam's bug tracker if needed. I'll keep you posted.
[Samsung Galaxy Nexus] agnostic900rr:
Anyone else noticed that email notification is not working?
[Samsung Galaxy Nexus] mrdevil_25:
I didn't find anything on slim Rom website regarding hangout video call crashing. Is there a work around?
[Samsung Galaxy Nexus] 1haumann1:
Was always asked and answered ;)

swyped from my maguro
[Samsung Galaxy Nexus] kufikugel:
you can download the just published beta.4 gapps which fixes that issue

we will start jenkins for the device builds soon....just pushed last changes and closed the code for weekly

btw as well 2 memory leak fixes ;)
[Samsung Galaxy Nexus] Nebucatnetzer:
The new weekly build is up.
[Samsung Galaxy Nexus] ChazzMatt:
Thank you. When you do the testing, try ScreenShot ER demo in particular. (It does need root). That app does offer an "alternate" method in Settings/Debugging if you need to. Thank you again.

https://play.google.com/store/apps/details?id=fahrbot.apps.screen.demo&hl=en
[Samsung Galaxy Nexus] Kurre:
Yes, I shall do that. Actually I already have that one installed, but haven't tested it with root yet. It's now The Venetian Night celebration weekend in here, so I'm at the cottage now..so I'll have to postpone testing to tomorrow :)

Sent from my Nexus 4
[Samsung Galaxy Nexus] stevensoaj:
Beta 4:

1) Thanks for fixing the audio bug I reported.

2) I love how status bar transparency works now. Much smoother when pulling down notification drawer.

3)You added .75 animation speed to dev options! Yay!

4) Torch can now be toggled with navring! Yay again!

Keep up the great work guys.
[Samsung Galaxy Nexus] Natakranta:
I've just downloaded beta 4 and beta 4 AIO gapps. Finishing titanium beckup now and I'll be flashing in a moment. So excited :)
[Samsung Galaxy Nexus] Blackcrx:
Anyone else notice that data usage is missing from settings?
[Samsung Galaxy Nexus] pagratios:
I have it with no problem
[Samsung Galaxy Nexus] buckowski:
I had no such problem with build 3 and

I have no such problem after dirty flash of build 4

Odesláno z mého Galaxy Nexus pomocí Tapatalk 4

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

Voice dialing still doesn't work

Odesláno z mého Galaxy Nexus pomocí Tapatalk 4
[Samsung Galaxy Nexus] docck:
Don't confirm. Try fresh install
[Samsung Galaxy Nexus] Blackcrx:
Sorry. False alarm. Data usage was missing in settings due to max ram kernel
[Samsung Galaxy Nexus] sago62:
it seems to me not very sensitive the touch to build 4 ... am I wrong?
[Samsung Galaxy Nexus] docck:
As for me I don't see any difference in touch's work between beta 3 and beta 4
[Samsung Galaxy Nexus] Kurre:
Screenshot ER doesn't work with stock rooted 4.3 since it seem to rely on module which it can't load (since module support is disabled in 4.3).

CANNOT LOAD EXECUTABLE: could not load library "libsurfacelinger_client.so" needed by "/data/data/fahrbot.apps.screen.demo/lib/libscreenshot-client.so"; caused by library "libsurfacelinger_client.so" not found

Also Screenshot Ultimate is giving me massive lags and logcat is full of:

W/SurfaceFlinger( 125): Timed out waiting for hw vsync; faking it

Which could mean that current screenshot apps just aren't fully compatible with 4.3 version.

Now I'll grab SlimBean beta 4 and do same tests with it..but I wouldn't expect any better results..since it seems that problems lie in system/changes in 4.3 and apps that can't work with it (yet?). Maybe [MENTION=4790322]kufikugel[/MENTION] can give he's opinion about those lags (which he mentioned also meantioned earlier?)

edit: On SlimBean 4.3 beta 4, at least Screenshot ER seems to work just fine with alternative method. Screenshot Ultimate is giving same issues like with stock 4.3.