yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kufikugel:
guys are you kidding me?? is it so complicated to read 5 posts??

thats our statement

http://xdaforums.com/showpost.php?p=45619704&postcount=2300

if you want a permanent menu button it is now only possible to set menu visibility to always. But even that makes no sense see my post linked above...apps do not work any more like this since a longer time now.

We do not hold redundant or depreciated options!!!!!!
[Nexus 4 Original Android Development] razerblade17:
The main reason i like to set menu button on nav bar setting is due to the button arrangement, if in default setting, the menu button is not arrange properly,

Menu button if set in nav button setting

Menu button for default setting

BTW thanks for new update :good:
[Nexus 4 Original Android Development] m0cha5hake:
+1 for having a Menu button option. Read the reasons for not including it, but I bet if the Slim team polled having or not having it, most user would want it.
[Nexus 4 Original Android Development] JNewms:
I doubt that. I know I would never put it on my device. All of the apps have their own menu buttons within the app now. There's no point in it.
[Nexus 4 Original Android Development] elderap:
guys, is there any way to have the "slim camera" and the camera stock at the same time? Another thing would be in relation to the gallery, is to sync photos from g+ without losing the slim camera? Sorry for my English.

Slim 4.3 beta 5 Kernel faux123
[Nexus 4 Original Android Development] Craxx:
Please how can i check the voltage table? In trickster i don't see the voltages...

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] kufikugel:
the question is the use case at all for a menu button in the navbar like JNewms said. You guys are doing more interaction then neccessary. 90% if not more apps have holo style like google want to have. So you press on the bottom the menu button on the navbar.....then hunting to the top of the screen to press the menu selection. That is way more interaction then just to press the menu button in the action bar lol. If the menus would open on the navbar area this would be something other but that is for almost all apps not the case

and for the old apps (at least I do only know one....amazon) the button appears automatically
[Nexus 4 Original Android Development] Kurre:
Just this one. No tables. Current method is probably sufficient for majority of users.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Craxx:
But where can i see what voltages are set?

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] vikan:
guys, list view animations are awesome and all in all the ROM has become more superb. no doubt why i hv sticked to this rom on mako, exclusively. thanks !!!
[Nexus 4 Original Android Development] justthefacts:
Not true.
[Nexus 4 Original Android Development] kufikugel:
then you can write the app developer with greetings from google and SlimRoms that he/she should think about it to update the app to the common google guidelines which already exists since ICS lol
[Nexus 4 Original Android Development] eksasol:
nm
[Nexus 4 Original Android Development] rokK0:
I unfortunately still soft reboot if I uninstall paid apps (eg faux Control).

:(

Gesendet von meinem Nexus 7
[Nexus 4 Original Android Development] ghul21:
Just make it by yourself ;)

It's not that hard :p

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] raimopeku:
Is it possible to have flashlight when holding pwr button while screen is off?
[Nexus 4 Original Android Development] kufikugel:
lol this error is really following us since I think build.2 of 4.2.2

at least it is that the playstore tries to stop the app. But it cannot do it or it is not allowed to to be more precise.....so the system decides it for the playstore and soft reboots to kill it for real. You can avoid it when you kill the app before yourselfe...like going into recents and swipe the app away....or open the app and kill it with the kill button.
[Nexus 4 Original Android Development] NeBouse:
Does anyone have good settings for the screen color using trickster ?

I'd like to get Halfbreed color.

I've tried converting hex to decimal from that link :

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

And set the values in trickster.

But i don't get the same result as with halfbreed preset from another kernel.

Btw, Slimbean build 1 is running fast and good here ! many thanks to the team !
[Nexus 4 Original Android Development] Kurre:
Afaik, you can't. On the sysfs, there's only those same balls available. So no way to see specific voltage for each frequency. Try to find table of stock voltages some where and figure out those by yourself :) but why you should know exact numbers...? Btw, IIRC, hardcoded minimum is 700mV..

Sent from my Nexus 4
[Nexus 4 Original Android Development] ak:
Thanks a lot guys ... great work as always with new official slim ... 5 stars forever.! :D
[Nexus 4 Original Android Development] EternalAndroid:
I'm coming from PA 3.99 RC1 & I have a small issue when switching over. Okay so, I flashed the ROM with the G-apps along with the latest SuperSU.zip, installed all my apps and I seem to have this issue with Unicon, the app that allows you to theme an icon pack system wide. I install Nox, open Unicon grant it permissions, install Xposed Installer grant that permission, opened the modules tab selected Unicon and hit reboot. Opened Unicon one again selected Nox and hit apply, afterwards I select reboot & I end up in a bootloop. I wiped and reflashed the ROM to see if the issue could be reproduced & happened once more. -_- What seems to be my issue?
[Nexus 4 Original Android Development] Kurre:
Not grabbing a logcat and excessively modding the system ? ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] NeBouse:
Answering myself : [MENTION=3951205]el_liberator[/MENTION] pointed me to this, very useful :

https://docs.google.com/spreadsheet/lv?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E&pli=1#gid=0
[Nexus 4 Original Android Development] EternalAndroid:
What do you mean excessively modding the system? I've never had this problem on the beta 5 version, why all of a sudden on the stable release?
[Nexus 4 Original Android Development] kufikugel:
hmm we nearly changed nothing between beta.5 and the stable build

at least bt stuff which is not related

the menu button stuff which is not related

listanimations which is not related as well I think

and a security patch

so no idea why this is not working for you
[Nexus 4 Original Android Development] Devin Cuthbertson:
I've been using slim bean for awhile and not had kernel issues until build 5, I tried everything to get a jwr kernel to boot on build 5, no luck, now I'm having the same issue and would love advice on how to make a jwr kernel like neo or Franco based kernels boot on build 1
[Nexus 4 Original Android Development] el_liberator:
Someone ? :laugh::laugh:
[Nexus 4 Original Android Development] NeBouse:
Sorry, didn't know you were here also ^^

So let me do this again :

[MENTION=3951205]el_liberator[/MENTION] pointed me to the Google docs.:angel:
[Nexus 4 Original Android Development] gori11a:
Awesome ROM guys, very slick. Love the animations. Stock kernel great also.

Made with SlimBean JellyBeans
[Nexus 4 Original Android Development] manpildo:
Franco doesn't work on Slim. Try if semaphore or faux work.
[Nexus 4 Original Android Development] Devin Cuthbertson:
Well neo is based on matrix and hellscore won't work so what does?
[Nexus 4 Original Android Development] nadiros:
I am one of the users who use the navbar menu button. I have no positive feedback concerning the change over of something so important as a users choice of navigation being takin away. Maybe seems silly but I think its a big deal. It is no more redundant than many other features that add options in how we interact with our device. To make the transition more difficult, all buttons are squished together as if somthings missing now. What about the power widget verses tiles? Or wtf is Pie? They don't add redundancy? You guys have built a great ROM that's solid and high quaility. Obviously you have no one to answer too....We'll just get used to it or move on I guess :sly:
[Nexus 4 Original Android Development] justthefacts:
Hellcore works for me. make sure you're using jwr and not jss
[Nexus 4 Original Android Development] QUIETLYloud:
Hell's core 37 & semaphore 1.6 both working for me on build 1
[Nexus 4 Original Android Development] Devin Cuthbertson:
Wipe or no wipe and anything on neo?
[Nexus 4 Original Android Development] Goku80:
You can use neo
[Nexus 4 Original Android Development] QUIETLYloud:
Dirty flashed the rom... Neo has never worked for me, always had to reflash rom to get out of bootloop
[Nexus 4 Original Android Development] Devin Cuthbertson:
To install a kernel I've been wiping both caches, good thing to do?
[Nexus 4 Original Android Development] android88:
I never do if I flash a custom kernel (which I rarely do)
[Nexus 4 Original Android Development] jtwlbz:
Since franco won't work I use semaphore.
[Nexus 4 Original Android Development] Devin Cuthbertson:
I had lag with it on 1.5, how is it on 1.6?
[Nexus 4 Original Android Development] murraynt:
Is PA kernel jwr or jss? I used it on slim 4.2 because of the colour calibration.
[Nexus 4 Original Android Development] leiros:
Please.

You can either

- Search on the forum

- Google it

- Read in the respective thread

On the other hand, if you use trickster mod you calibrate colors.
[Nexus 4 Original Android Development] DomOctober:
Absolutely phenomenal work. I stand behind the fact that you guys out do yourselves every time. Runs like a top, and the extras including the list animations are top notch. Another donation sent! I'd put you guys on a payroll if I could.
[Nexus 4 Original Android Development] Mercado_Negro:
Please, give the stock kernel a few days before flashing anything else. If you're after stability, performance and great battery life the stock kernel does a good job.
[Nexus 4 Original Android Development] murraynt:
I'm trying to find out. No need to be a **** about it. It would of actually taken less time to Give a straight answer than to be a smart ass.

Good advice. I'll flash tonight and see how see how things go. Things should settle soon anyways.
[Nexus 4 Original Android Development] fkloznica:
Slim 4.3 bild 1 > android kit kat 4.4 ! Fck google.. I wish they hire you to devolop in google :) best regards slim team
[Nexus 4 Original Android Development] Devin Cuthbertson:
Stock slim kernel lags right now, u truly think it will settle smoothly?
[Nexus 4 Original Android Development] Mercado_Negro:
Most of us think stock kernels aren't good enough but truth is things got better in 4.3, kernel-wise. With all the improvements and enhancements done by the Slim team it's even better. I just wish they'd give us a custom hotplug driver to define cores behavior at will.

---------- Post added at 06:34 PM ---------- Previous post was at 06:30 PM ----------

It's been smooth since I flashed it. I didn't have to wait for it to settle. Could you please be more specific? Maybe I haven't tried it in some areas where you're experiencing such lags.

Did you reboot after setting your device up? Maybe it just needs a reboot.
[Nexus 4 Original Android Development] Devin Cuthbertson:
Multi tasking lags, like when switching apps or some pie button functions lag like going to the app drawer using a pie button or last app button

---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------

Or just scrolling seems to hesitate or be awkward
[Nexus 4 Original Android Development] elderap:
Guys, anyone else experienced random reboots? I had with beta 5 is to build today. sorry did not log file these reboots, but I wonder if this only happens to me. Note kernel slim

Enviado de meu XT915 usando Tapatalk 4
[Nexus 4 Original Android Development] ciprianruse88:
Get syslog app from playstore and use it to grab logs :thumbup:
[Nexus 4 Original Android Development] elderap:
In this case, when it happens, I just click and take log will already be registered right?
[Nexus 4 Original Android Development] Mercado_Negro:
No need for that anymore on build 1. The option in Slim Center is working now.
[Nexus 4 Original Android Development] ciprianruse88:
Yep.After you press the "take log" button take those 3 logs from internal memory/syslog folder and post them here :)
[Nexus 4 Original Android Development] ciprianruse88:
Wow ! Great!Eighter way both ways work fine(slimcenter/bugreport or syslog app) :thumbup:
[Nexus 4 Original Android Development] Mercado_Negro:
Yeah, sure! Syslog is also very good :thumbup:
[Nexus 4 Original Android Development] jdmcivic:
dirty flashed over the previous build and now my settings keep on FC. anyone else having this prob?
[Nexus 4 Original Android Development] Mercado_Negro:
From Slimroms site:

Having said that, I did a clean flash and that's what I would suggest.
[Nexus 4 Original Android Development] nickslg:
I've dirty flashed build1 official over beta 5 and flashed a different kernel all is working perfectly
[Nexus 4 Original Android Development] jdmcivic:
alright nvm. i reflashed again and all is good. loving the animations. woo
[Nexus 4 Original Android Development] playya:
We all know dirty flashing is a crap shoot. If you dirty flash and come across issues the standard method at that point would be clean flash and try again. Its hard to help troubleshoot dirty flashes
[Nexus 4 Original Android Development] prbassplayer:
Whoever said it's laggy are you sure cpu and gpu clock speeds ate properly set?

Random reboot reports where you messing with voltage control? Get me last kmsg (slim bug report should suffice) from soon after it happens
[Nexus 4 Original Android Development] Devin Cuthbertson:
Yes, cpu set at 1512 max and 486 min, mp desicion off, 400 mhz gpu
[Nexus 4 Original Android Development] prbassplayer:
Why did you turn off mpdecision? Pretty much killed your hotplug and you are probably only running 2 cores on all time.
[Nexus 4 Original Android Development] Devin Cuthbertson:
Mp decision keeps ramping my min up to 1000 mhz, kills battery
[Nexus 4 Original Android Development] prbassplayer:
Bull crap mate. It does not. Your cpu cycles just fine through all the steps.
[Nexus 4 Original Android Development] Devin Cuthbertson:
Each time I check my min max it goes from 486 and 1512 to 1000 and 1512

---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------

I kinda got tired of adjusting it back down soooo yea, not bull crap but thanks for your wonderful input.
[Nexus 4 Original Android Development] kufikugel:
you know the thing is that this question was answered 10000 times and can be googled very easy.....mp decision does not push the min freq permanently to 1000 and it does not effect your battery life. It is completly dynamic. But that you can google.

just an addition imagine your cpu would be permanently on 1000 your battery would be empty in 2 hours for sure lol
[Nexus 4 Original Android Development] prbassplayer:
It doesn't matter what the app says it uses all cpu steps even if app says min is 1026,thats just the boost pulse that automatically bumps freq to 1026 on cpu0 and cpu1 when screen is touched. This is week know and simply found.
[Nexus 4 Original Android Development] yethz:
Yes really sad for me too. Its gone.

It is remove from choices, now its on the side.

Austhetics speaking this is horrible for me.

________________________

Device: Google Nexus 4 (LG-E960)

ROM: SlimBean 4.3 Beta Build 5

Kernel: Slim-4.3-JWR_RC-1.0+

Recovery: PhilZ Touch (CWM) Recovery v5.11.2
[Nexus 4 Original Android Development] hooliganx:
CONGRATULATIONS TEAM SLIM!

Nothing, absolutely nothing to complain or to comment yet about the Build-1 Official Stable.

Always clean install (full wipes), everything works perfectly!

Good performance, good speed, no lag, slow, reboot, freeze. Nothing!

Zero bug! :laugh:

I am one of the users who like (a lot) the menu button on the navbar. But okay, the new option doesn't have. Everything works normally!

As for aesthetics, good for everything we can get by, see photo attached. Beautiful and even more useful because I can use the menu anywhere now. :D.

This is not a request (directly), but it would be nice if we had:

* Slide for brightness in navbar (as an option, and if possible);

* Longpress option in menu buttons.

* Faux Sound in kernel.

And just it! :)

Perfect Rom!

Thanks again!

edit: forget pic heheheheh... sorry...
[Nexus 4 Original Android Development] Mercado_Negro:
Should the back key go to recents sometimes? There are times where I press it to go to the previous app and it takes me to recents. Is that normal?
[Nexus 4 Original Android Development] happiboi:
FWIW, I'm currently on build 1, using stock slim kernel. Had preveiously been constantly on semaphore 1.6.0 for gamma and touch control compatibility.

But this time round giving stock slim a good run in to see how it fairs. On semaphore, things were smooth and I liked havving touch control but battery was not as ideal as I'd like. Hopefully with stock slim it'll be good :D
[Nexus 4 Original Android Development] hooliganx:
not here man.

maybe you put longpress with last app, don't you?

or, maybe is to close now and accidentally you press recents? :D

N4*Slim.b1.Stable.JSS.4.3*UHC.JWR.b3*TWRP.2.6*Radio.0.84

---------- Post added at 12:20 AM ---------- Previous post was at 12:16 AM ----------

I prefer more battery life/SOT than s2w :p

with SlimKernel I have 6h30 SOT. With my use and conditions... very good! :D

N4*Slim.b1.Stable.JSS.4.3*UHC.JWR.b3*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] Mercado_Negro:
No, I didn't set any longpress actions and the back key is on the other side. My NavBar is just the default one, 3 buttons only. I've been doing a lot of multitasking and maybe something just got stuck. Anyways, thanks for replying, appreciated :thumbup:
[Nexus 4 Original Android Development] Devin Cuthbertson:
Had no idea about specifics to mp decision nor was I asking how it worked or I would have Googled it but good to know how it works anyways, I only turned off mp because I liked having my settings on at all times but I may give it another shot with mp if it's supposed to give good battery life
[Nexus 4 Original Android Development] chadalu:
Why you guys removed the option to add menu buttonsbutton as a main button on navbar...it was so pratical...i dont like the 3 dots... And now when you chose to never show the menu button ,navbar no longer expand the distance between the buttons...

Just why? y.y
[Nexus 4 Original Android Development] MaliceOmega:
cool. ive been holding off on updating bcuz i wanted my feature. mainly the dark toggle, navbar settings and qs customization. figured slim would add them pretty quick.
[Nexus 4 Original Android Development] android88:
if i understand your post correctly, then that's just mpdecision doing its thing.. disable mpdecision and you'll be able to change it as much as you want even though i dont recommend disabling it..

yes, but we never "added" the features back - we just merged 4.3 into our current 4.2.2 ROM ;)
[Nexus 4 Original Android Development] MaliceOmega:
ah ok cool. i figured the 4.3 update was a drastic change due to the fact that the few 4.3 roms i flashed had stripped their features. thought the framework had a major switch up or something. good to know things merged smoothly though
[Nexus 4 Original Android Development] odeccacccp:
1. Slim kernel does not have the fast charge option yet on 4.3

2. Other available kernels have build in colour settings to choose from, more convenient for me.

3. Would be nice to make ROM comparable with other kernels, don't u think...

4. This alpha build people are testing pointing things out , no one complaining, what's with the yelling man?
[Nexus 4 Original Android Development] shayne77:
But you come in this thread when THAT kernel doesn't work with this ROM? Go to the kernel's developer and complain. Stock ROM and Stock Kernel of Slim works just fine and would serve 99% of people who just use their Phone, as that, as a Phone with great battery life. Not the other 1% who are flashoholics and need to flash something every day so they can beat their chest and say to their friends, "Ive got the latest greatest... look at me, weeeeeeee!"

Point is, you seriously think these guys should fix your problem with a random kernel you're having?
[Nexus 4 Original Android Development] odeccacccp:
No I didn't. I said this what I've done and is this how it should be or did I do it wrong.

Battery life? What?

Good point on calculations.

Useless conversation.
[Nexus 4 Original Android Development] kufikugel:
that just point how good and organized the code base of slim was on 4.2.2 + that we programmed 80% of our features ourselves which just give another feeling for how the code is working which a lot kanger do not get of course....this said the easier is it to merge new versions. And yes frameworks base had major updates....over 2 million code changes only in that package....overall they were 5 million. Some packages we started from scratch some we could merge and resolve conflicts etc etc. At least one and a half week two guys of our team worked night and day to get that in

About the features: frameworks features are all in

Camera: due to the new camera not all features are back...they are present but we did not made an UI for it till now lol

Phone: the pickup the phone and call feature is missing

thats it

I can say for next version which is rolling out that the last issues are sorted out and are pimped up a bit

@ kernel....slim kernel is nearly google stock kernel with first tweaks. To say that we need to make the rom compatible....do not get me wrong....it is kernel devs work to have a working kernel on an aosp rom. Due that a stock kernel is working without issues I cannot see the problems on our side

as well the root issue with other kernels is not really an issue. Ppl need to realize that google introduced big security changes. In this case selinux. So all kernel which do not fit google selinux permissions or maybe use other (the one from cm eg they use since some weeks a sligthly different selinux implementation then google but are merging them together currently) will lose root. Thats a security feature and not an error. That a thing were user need to life with it. Of course I am sure that more and more kernel devs will find a way to be compatible to all that stuff. But as well they need time for it.

About the kernel discussion itself....of course we like to see that you guys stay on our (nearly google) stock kernel....just for only one reason...to get propper logs and proper feedback about our current state. Epecially now due that a lot kernels are not stable on that early stage it is nearly impossible to say what the cause is when we get a report.

cheers
[Nexus 4 Original Android Development] Larrondo:
I totally get why you would want to get everything sorted out on the stock kernel. I'm curious why, in the long run, Slim keeps it's kernel (as you describe it) close to stock. I'm not criticizing at all and really don't have an opinion-- I'm just curious. Do you think it's better to keep it close to stock? I don't personally care very much about color and sound tweaks but it seems like other kernels boast improved battery life and/or performance.

I've actually had very good battery life on Slim build 8, so I have no complaints. Could you get it even better with more aggressive kernel settings?
[Nexus 4 Original Android Development] 1ceb0x:
That's why it would be good to ignore people who have other kernel than stock slimbean. I have unofficial Franco kernel and if I have a major issue I am experienced enough to find myself the answer but you should put the stock slim kernel on the op as a separate download in case someone flashes another kernel and complain about issues. Force your fan base to test their issue on stock kernel and maybe stock settings (no apps installed, etc). Cheers for a great working ROM!