yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] smit.sanghavi:
1) Don't know.

2) The remove all apps button was there previously but was removed by the developers for some reason. I doubt if it will come back.
[Nexus S Android Development] coolek33:
And here is why there is no clear all button.

http://youtu.be/Mx_uDZObqvY
[Nexus S Android Development] linuxxp:
There is another way that I prefer. Install app like "System app remover". Whit this app I remove every unused for me app like live wallpaper, gmail and other.
[Nexus S Android Development] MarkRain:
Thank you!

The new feature seems to be good, but i don't see (from the video) neither in this version the feature i'm searching for.

Let's wait for it and see. :good:
[Nexus S Android Development] coolek33:
It's the new slim recents window under construction.
[Nexus S Android Development] Setting.Out:
You can take omni-switch out of Omni ROM and get kill all using it, and it works in ART... I'm using it now... ;)
[Nexus S Android Development] MarkRain:
I just looked for this Omni-Switch and it seems to be good :good:

Unfortunately i'm not good at coding, it's impossible for me to cut/paste things from a rom...

Do you know if there's already some standalone package for this?

Thank you for the advice!!
[Nexus S Android Development] Setting.Out:
It's just an app... Just extract it from the priv-app folder and put it in what ever (KitKat) ROM you like.. (Placing it back into the priv-app folder and fixing permissions)...
[Nexus S Android Development] MarkRain:
That easy? :eek:

Ok, i'll try it later, i'll report back here if my NS is still working :D
[Nexus S Android Development] Setting.Out:
If I wasn't on the way to work I'd make a flashable zip...
[Nexus S Android Development] MarkRain:
Don't worry, i'll try to copy it in my rom.

Can you tell me exactly how have i to set the permissions? i use Root Browser, it should be ok i think
[Nexus S Android Development] Setting.Out:
When in doubt, look at the permissions on the files in the folder you're working in and just match them... ;)
[Nexus S Android Development] MarkRain:
Just tried...i copied the file, set the permission and than rebooted, but nothing changed.

idk if it's the right procedure, as i told you i never did something like that.

I also tried to install it but it give me an error.

EDIT: i got it, now it's working!!

Thank you for helping :D
[Nexus S Android Development] outlogic:
The phone is not booting after removing Nova launcher :(
[Nexus S Android Development] ottoemezzo:
Did you have your other, preferred launcher installed? The system cannot run without a launcher I guess.

You can dirty flash your rom and it'll boot again.
[Nexus S Android Development] Setting.Out:
Ha ha ha.. lol.. I did this once, took me a bit to figure it out.. :) You just need to reflash the rom or flash a launcher.. :)
[Nexus S Android Development] coolek33:
If you want to remove nova make sure U flashed aio gapps. There is Google launcher there also.
[Nexus S Android Development] outlogic:
I had the Start launcher. I though that animating wallpaper (or something like that) caused the problem. Then deleted the Nova Launcher from the reflashed ROM and it appeared to be the case.

Didn't have time for experiments with AIO gapps, plus the largest font is smaller than in the AOSP ROM (I needed it to be very big, because the phone is for an older person), so flashed the AOSP instead.
[Nexus S Android Development] smit.sanghavi:
So I finally installed the build 3.0 and now I feel why I didn't do it earlier. :D

Some things I noticed:

1) Fast and smooth as hell. Like the small small changes by KK and SlimROM team.

2) Feels like a new phone.

3) Smart status bar is no more an option. Enabled by default. Like it.

4) Google Now Launcher is interesting.

5) Boot animation is cool and of much better quality.

6) Default brightness seems higher than usual. (Anybody else feels the same?)

Missing few things like:

1) alternate "default app picker" (Already integrated in KK by Google)

2) memory management like zRAM, purge assets etc (don't know if they are actually useful)

3) Expanded lockscreen widgets. Pattern lockscreen cuts off some dashclock extensions. (It's back in Build 5!)

4) Lockscreen hardware keys rebinding (Don't know if it's coming back)

5) Still waiting for holo black in screens mentioned here. (I have OCD about it) :laugh: (Some screens fixed. Yay!)

6) In Quick Settings, when sync toggled, the corresponding status is not reflected in the power widget. (Still not fixed in Build 5)

7) Notification panel loses transparency setting and becomes opaque after reboot and after TRDS toggle. (Fixed in Build 5)

8) While adding widget for Slim Actions (using Apex Launcher), you see a massive icon on the screen.

I'll update the post when I find new things. Till then,enjoying SlimKat.
[Nexus S Android Development] coolek33:
About the dashclock. It has an option now for extensions to be collapsed or not.
[Nexus S Android Development] smit.sanghavi:
I have enabled that. What I'm saying is that in 4.3.1 (Build 2.2), there was an option to expand the extensions on screen wake and an unlock button below that. Now, that is gone and we have the pattern screen which cuts the extensions.
[Nexus S Android Development] K96:
If you are talking about this

Get Xposed Installer install the module reboot then download a module called Maximize lockscreen widgets.

I'm sure slimroms will add this feature back in but for now there are loads of modules that will do everything the old 4.2 rom did.
[Nexus S Android Development] joaor10:
If you want that option you need to change in build.prop the line lowmemory to false.

Enviado do meu Nexus S através de Tapatalk
[Nexus S Android Development] smit.sanghavi:
Thanks. I think there is an Xposed module for EVERYTHING now. :D

I'll test out SlimKat the way it is though.

Thanks for your suggestions.

I know I can do it if I change build.prop but I'd rather keep the low memory tweaks. That will also enable the transparent status bar but I'll just keep it the way it is.

On a side note, do any of you feel the minimum brightness is still wayyy to bright than usual?

And do you'll also have the power widget sync icon bug as I mentioned in #6?
[Nexus S Android Development] khimois:
Is it okay to dirty flash from STABLE to WEEKLY build? Thanks!
[Nexus S Android Development] coolek33:
wipe cache, dalvick and system, flash rom and gapps and you're good to go. All your settings and apps will stay.
[Nexus S Android Development] khimois:
Thank you!!!
[Nexus S Android Development] Zahih:
Hi [MENTION=4404392]tchaari[/MENTION], thanks for the updates..

The new Recent Apps SlimKat in build 3.4 is great... :thumbup::thumbup:
[Nexus S Android Development] smit.sanghavi:
Anybody???

I have also tried screen recording.Fails with this error:

"Request for encoder buffer failed"

Will attach a logcat if anybody wants.
[Nexus S Android Development] Setting.Out:
I'm having issues with the browser.. All the other apps connect to the internet well, but the stock browser can't seem to? Other browsers work fine..
[Nexus S Android Development] coolek33:
Unfortunately I can't confirm that. Works like it should here on wifi and mobile data.
[Nexus S Android Development] Setting.Out:
Wifi is fine, it's just mobile data that lagggggggs on the stock browser.. Strange.. (Clean install ect.. )

also the new recents lags a bit and doesn't always open on home button double tap for me, long press is fine..
[Nexus S Android Development] Zahih:
Mobile Data & Wifi works fine on stock browser here.

And yes, new recent apps little bit lag too (long press home button).
[Nexus S Android Development] khimois:
Anyone having a problem with front cam? I'm getting FC and I have to clear data of Camera to make back cam work again. :(

And yeah, the recent app is a bit laggy at times but it's cool and stock browser is working fine with mobile data and WiFi but it also FC at times. :(

Came from Build 3, Dirty Flash to 3.4 with coolek33's instruction.
[Nexus S Android Development] coolek33:
Well 3.4 is a bit laggy for me, my wife doesn't feel the difference so if she's happy then it's not so bad. About FCs, I got some on Hammerhead with recents window but flashed test build and they're gone. So maybe next build will be better for Crespo as well.
[Nexus S Android Development] Sumanji:
Hey guys,

First foray into custom ROMs for my Nexus S :D

Toying between Slimkat and CM11... main priority is a light install to make the device quicker. Guessing Slim is the way to go?

If Slim, should I do the official build (16th Feb), or the latest weekly?

Thanks,

Su
[Nexus S Android Development] smit.sanghavi:
Thumb Rule:

Weekly - Little unstable but early access to features. Builds every week.

Stable - Well, you know, it's stable. Builds around a month. :D
[Nexus S Android Development] Sumanji:
Wow... that did not take very long at all to install!

Not as scary as it's made out to be :p :D

---------- Post added at 07:46 PM ---------- Previous post was at 06:53 PM ----------

Quick Q, is it cool to relock the bootloader after flashing?
[Nexus S Android Development] coolek33:
Leave it unlocked. U can end up in bootloop.
[Nexus S Android Development] khimois:
Ooops, wrong post. xD
[Nexus S Android Development] linuxxp:
Hi! From few days ago I have this error: insufficient storage available when I try to update Poweramp. Other apps hasn't this problem. Today Shazam got the same error. I tried to uninstall and then install again but no result.
[Nexus S Android Development] Po0yAn:
Well you seem to use the poweramp with lucky patcher or other hacking programs. You should delete the patch for the Poweramp from the root folder!
[Nexus S Android Development] smit.sanghavi:
Actually this had happened to me also. I had not installed lucky patcher or any other hacking app but still got the error.

I rebooted once and the problem went away.

Or uninstall any random app and try updating the problematic app from the play store.

This is just a workaround solution and may not work.
[Nexus S Android Development] linuxxp:
Hi! I haven't lucky patcher. Software in my phone is legal.
[Nexus S Android Development] DjoeN:
ok, FAQ sure, i did oversee it the first time i looked at it :D
[Nexus S Android Development] smit.sanghavi:
Same here. But I don't know why it happens. I just live with it.
[Nexus S Android Development] DjoeN:
I have the issue that only my back button works, home and search button do not work :/

did a clean install 3 times, the home button works on CM11 and TWPR 2.7.0.0
[Nexus S Android Development] tchaari:
The storage limit is due to /system and /data partitions limit which are becoming too small. For now there is no other solutions than removing apps until we look into changing crespo partition table...
[Nexus S Android Development] homerograco:
Have you guys heard about F2FS file system? It seems to be much faster than ext4. Is there any hope for this to come to our NS?
[Nexus S Android Development] linuxxp:
I don't understand why because I have 365mb free in internal storage.
[Nexus S Android Development] tchaari:
This is strange. I don't have this issue at all. Are you sure you are doing a clean wipe? (wipe data factory reset + format /system)
[Nexus S Android Development] smit.sanghavi:
I had a full done a full wipe (dalvik, cache, system) before installing Build 3 of SlimKat. Got the same error of insufficient storage space today for WhatsApp. I had more than 100MB of free space. I'm attaching a logcat if it helps. Also, no modding/patching software (e.g. Lucky Patcher) is installed in my OS. Let me know if you need anything more.
[Nexus S Android Development] adm1jtg:
Are you running ART or a gapps package other then minimal?
[Nexus S Android Development] briatide:
check /data/app for odex files left over from the apps you uninstalled, that could possibly be the root of the problem
[Nexus S Android Development] smit.sanghavi:
I'm on DVM and using Slim AIO Gapps.

My /data/app has only APKs and no .odex files.
[Nexus S Android Development] beppegg:
I had the memory limit problem too. In my case, it turned out to be native e-mail app, who stored more than 100mb of data. I deleted and re-entered my accounts and all is good... Currently :D

Inviato dal mio Nexus S utilizzando Tapatalk
[Nexus S Android Development] DjoeN:
Problem solved with installing the Stable version :)

Everything working great now, thanks!
[Nexus S Android Development] smit.sanghavi:
Good for you. Still looking for a trick to avoid the dubious error. :(
[Nexus S Android Development] khimois:
I love SlimKat, but where can I find the Reverse Volume button in landscape? And also, the weather in Dash Clock widget, can't it be retain even if you turned on your mobile data and you don't have internet? It is annoying for me since it is always updated through WIFI but will display no data whenever I turned off my mobile data...

BTW, the transparency of Notification & QS drawer background style always become solid color background even it is set to 30% whenever I reboot.

And last, won't you guys include an option to make the status bar transparent without editing build.prop?

That's all. xD
[Nexus S Android Development] smit.sanghavi:
I have the Navigation Drawer & QS transparency issue. Mentioned it before in this post along with other errors. Waiting for a fix.
[Nexus S Android Development] MarkRain:
Has anyone ever tried this 4.4 build 3 with a different kernel?? any feedback??
[Nexus S Android Development] Setting.Out:
I prefer Devil kernel still, but it has to do more with customization over performance or battery life.. The stock kernel is virtually the same in those regards to Devil..
[Nexus S Android Development] MarkRain:
Thank you for the feedback!!

I asked cause i'm looking for a kernel that:

-allow me to use BLD

-won't get worse performance

Do you think that Devil Kernel can meet my needs?? :good:

Can you link me the version you're using?? :D
[Nexus S Android Development] Setting.Out:
Give me a few hours and I'll upload the latest one from ThinkingBridge rom..
[Nexus S Android Development] MarkRain:
Thank you very much!!

I'm not in a hurry so ... do it when you want . :good:
[Nexus S Android Development] rakeshbro:
Is there any option available to make status bar transparent?

Or editing build.prop will do that..:confused:
[Nexus S Android Development] adm1jtg:
I believe the transparent status bar is not available if the build prop identifies as a low memory device aka = true

You can change to false and the transparent should be back but we ARE a low memory device so this is not recommended
[Nexus S Android Development] kriout:
on last two weekly i have the same problem: often, but not always, when someone is calling me the screen doesn't turn on even after i press the power button. Both are clean install with all wipes ...
[Nexus S Android Development] Setting.Out:
I made a mistake, it seems the ThinkingBridge rom didn't boot correctly using the previous kernel I had installed which is this one

http://xdaforums.com/attachment.php?attachmentid=2350048&d=1382729831

Which is the latest Devil kernel, but not from ThinkingBridge.. From looking at the boot.img size, I'd say it was supposed to boot with a normal CM kernel... but either way, here's the kernel you requested.. :)
[Nexus S Android Development] adm1jtg:
Can you capture and post a bug report for me
[Nexus S Android Development] kriout:
you asked me that ? if so i don't know how to do that ...
[Nexus S Android Development] MarkRain:
Thank you, i'm using it right now and it seems to be good for me. I also use ART without a problem,

:good:
[Nexus S Android Development] paul279:
I saw there is touchwake support from kernel and software.

But I am not able to find the settings for touchwake. Where can i find them or do I need an third party app from store to activate them?

Thanks
[Nexus S Android Development] Setting.Out:
Official

http://xdaforums.com/attachment.php?attachmentid=2453825&d=1387010535

Non-official

https://play.google.com/store/apps/details?id=com.metalignus.devilappsgs
[Nexus S Android Development] Jhyrachy:
i have to do a full wipe, what version do you suggest me: weekly or Build 3?
[Nexus S Android Development] AzN MusiQ:
First I want to say that this rom is rocking Android Kitkat. By far faster than JellyBean and all important features are implented!

[MENTION=4370703]Jhyrachy[/MENTION]

My Nexus S is running build 3 and I haven't got any problems yet!
[Nexus S Android Development] tchaari:
We are aware about the delay to show the icoming call user interface and we are working on fixing it. Stable build doesn't have this issue ;)
[Nexus S Android Development] kriout:
thanks for the reply. On last build i have force close on keyboard while using gesture.
[Nexus S Android Development] coolek33:
Redownload and reflash gapps. They're updated.
[Nexus S Android Development] kriout:
i'm going to do that ... should i wipe system again ? anyway i noticed less lagginess :)
[Nexus S Android Development] coolek33:
No. Just flash them or wipe cache and dalvick if U want to.
[Nexus S Android Development] gnaurittiello:
I flashed Build 3 and latest slim GApps AIO today. It run very smooth.

But I'm really disappointed, because even if the device connected fine to my WiFi network during setup, then it unexpectedly dropped WiFi and used 3G connection instead, before I can disable it, since I have no data plan on my current SIM card. Result? I lost 4€ for a bunch of kilobyte (yeah, my carrier is kinda a thief). I flashed so many roms on this phone over the years, and this is the very first time I see a bad behavior like this. I'm not blaming dev, of course, but maybe it's a bug. Have someone else experienced this?
[Nexus S Android Development] adm1jtg:
Have I been testing slim a very long time and not seen issues like you mentioned. Did you do a clean install or at least wipe system and both caches? Are you sure your wifi network isn't the culprit?

You could probably test further in airplane mode using just wifi and see if you can reproduce this error. If you can reproduce it right after it occurs go into settings and slimcenter and tap bugreport. This will make a zipfile of all the logs, you can then post those here for us to look it
[Nexus S Android Development] Setting.Out:
When I tested build 3 I had the opposite result.. I didn't have WiFi and Google didn't sign in and auto restore.. My 3g was fine but it tried to save my data usage... I have yet to encounter this WiFi issue.. But to be on the safe side flash the ROM, boot, then flash gapps so Google won't automatically use any data..
[Nexus S Android Development] gnaurittiello:
I did a full wipe before install, including sdcard (it's not necessary, I know, but it needed a cleanup).

My WiFi went down right after the device finished the initial setup? Possible, but very unlikely. My home network was (is) running up and fine with many clients connected without any problems.

The phone wasn't in airplane mode. The data was actually activated (I wasn't able to turn off it in time), alongside the WiFi. The issue is that phone disconnected from WiFi and used 3G instead. I don't know how to reproduce this, apart from doing a fresh install.

So my suspect that something might be wrong is not so absurd.

Thanks for the tip. Even better, taking out the SIM will avoid this kind of issue at all.

---------- Post added at 01:57 AM ---------- Previous post was at 01:55 AM ----------

Sorry for double posting, but this is unrelated to previous question.

I think I found another issue in Build 3.

If ART is used, a LOT of apps get FC if moved to SD (e.g Quickoffice, Drive, eBay, and many others). Some apps work fine with ART if installed on SD (e.g. QuickPic, Amazon).

I reverted using Dalvik, and all apps work like a charm if moved to SD.

Another thing I noticed: using ART, occupied space in /data is much higher than using Dalivk.

I don't know if this a known bug or not.

EDIT: Just found that ART consumes indeed more space than Dalvik by design. My fault.
[Nexus S Android Development] MarkRain:
Hi

if i look into settings->app i can see that i have more than 800mb used and less than 200mb free.

If i try to tot up all the single app's sizes i can reach 600mb or so, so i was wondering what's using all that space?? :confused:

ADD: is it possible that the "problem" is ART? I just switched to dalvik and now i have 580used... :S
[Nexus S Android Development] adm1jtg:
Yes ART users a lot more space as both you abs previous poster have discovered. I can confirm this is the case and just the way ART is. On our devices I also have found no benefit at all to using it. They're are still some compatability issues and worst is all in my setup it ran much slower with a lot more lag. I was very disappointed. But all these issues are ART itself not slim
[Nexus S Android Development] MarkRain:
Thank you for the clarification.

At first when i enabled ART i felt there was a performance improvement, but i'm starting to think it was just a placebo effect.

That's because when i re-enabled Dalvik i had the same impression :D

I'll stick with Dalvik than, thank you again!
[Nexus S Android Development] mclisme:
Hi guys, after a long time in 4.2.2 I changed to this ROM and couldn't believe how smooth and fast it is (for a 4 y.o. phone!). I have only one question: How do we make icons and the whole GUI smaller? Is there some hidden ppi setting which I've missed? Menus looks a bit tiny on that 4" display. Thanks!

( I am running v3 - stable)
[Nexus S Android Development] coolek33:
So U want to change the dpi setting. For that U need to change density value in build.prop. U can do it via some file Explorer or build.prop editor from playstore for example. Grand root permissions to it, change and save it. Reboot and U good to go. Don't remember what is stock dpi for NS. 240 maybe.
[Nexus S Android Development] mclisme:
Oups! Yes I meant dpi not ppi! That you can't change it via software unfortunately! :p

I have root access already, so is it just one value (Density) that I need to change then? Yes 240 is the stock NS value.

PS. I just came across this: http://www.slimroms.net/index.php/faq/slimbean/71-how-too-change-dpi

but seems it was removed from SlimKat?
[Nexus S Android Development] MarkRain:
i had this problem too and i solved it using an app you can find in the Play Store, it's called "Texdroider DPI". ;)

Stock DPI for Nexus S is 240, but i find it way too big, while the SlimKat setting was too small. i setted my DPI to 210 and i'm quite satisfied with the result!
[Nexus S Android Development] coolek33:
Dpi changer is build in rom yet. Maybe it will come at some point.
[Nexus S Android Development] mclisme:
Thanks! I had to use the app you suggested to achieve the dpi change. Thought I could do it by directly editing build.prop but for some reason, even though it looks as I grant Superuser permission to File explorer, I couldn't save build.prop after I had changed the value. And the Superuser of this ROM seems to be integrated in its settings (not a separate SU app) so I couldn't update it in case that was the problem. Strange...
[Nexus S Android Development] joaor10:
I use ES Explorer to edit build.prop and it works well.
[Nexus S Android Development] mclisme:
That's what I used as well but everytime I selected "Save" there was an error that the file couldn't be saved.
[Nexus S Android Development] lyvidium:
[MENTION=3599246]mclisme[/MENTION] Try enablin root explorer in ES. Settings/Tools/Root Ex. ON
[Nexus S Android Development] mclisme:
Nop, that didn't do it either. As I said I managed to do what I wanted using "Texdroider DPI" but it's strange not being able to edit build.prop generally. Don't think I will need to edit it for any other reason though, I am not the owner of the phone any more :p
[Nexus S Android Development] smit.sanghavi:
You weren't able to save the file using ES File Manager because /system was mounted as read-only... ;)
[Nexus S Android Development] joaor10:
And I guess you have activated root in ES explorer, right?

Edit: ups, didn't saw the other replies xD

Enviado do meu Nexus S através de Tapatalk
[Nexus S Android Development] khimois:
New build is up... :good:

Thanks, will try...