yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nnay:
Hello, good job for the stable ?

I have a question : is there a way to increase the charge current on USB without installing an another kernel?
[Samsung Galaxy Nexus] gwindlord:
I've heard in Russian segment that at least one user experiences reboots/freezes too, and logs he'd sent, point to Chrome too (or maybe to another app, based on Chrome). But that happened on previous builds, not on latest one (maybe yet).
[Samsung Galaxy Nexus] LibertyMonger:
Well actually, on previous weekly's I was getting SOD's while in browser or Chrome, now I am getting them outside of browsing.
[Samsung Galaxy Nexus] Nebucatnetzer:
Logs, Logs, logs

Btw this is a very nice app for collecting the last_kmsg file.

https://play.google.com/store/apps/details?id=se.mumu21.bootlog

---------- Post added at 07:04 PM ---------- Previous post was at 07:02 PM ----------

IIRC the built in kernel supports fast charging.

However I forgot how to activate it :o

You could probably check it with something like Trickster Mod.
[Samsung Galaxy Nexus] Natakranta:
Stable 4 running fine on my wife's Maguro. No complains from her side means nothing happened which is good :good:

2 working days so far used half battery (2000 mAh) with 50 minutes SOT, WiFi always on, auto brightness.
[Samsung Galaxy Nexus] josera06:
With stock kernel?

Enviado desde mi Android 4.4.2 GNexus
[Samsung Galaxy Nexus] 2LoT:
Have you enabled ART?
[Samsung Galaxy Nexus] Natakranta:
100% Slim with default settings on clean flash. Remember that's Samsung extended 2000 mAh battery.

---------- Post added at 11:32 PM ---------- Previous post was at 11:30 PM ----------

SlimKat 4 running on dalvik. Previously (build 3 to 3.10) it was on ART.

I don't see a difference. Might be because it's not me using the phone but my wife, and for her it just needs to work ;)
[Samsung Galaxy Nexus] agritux:
Hi,

Can we change lockscreen walpaper?

Can we set statusbar notification count? Because with 320 dpi, notifications crushinh to centered clock.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Nebucatnetzer:
Both not included. But for lockscreen wallpaper exists xposed module AFAIK.
[Samsung Galaxy Nexus] Ashtrix:
Unfortunately those don't work with any SlimKAT Rom. I had stated previously in this thread only with the new 3.10 update both Xblast tools and Xposed lockscreen wallpaper modules that change lockscreen wallpaper don't work...

P.S : AFAIK from that thread of Xposed lockscreen module the dev points out that there's some change in the code that's interfering with the params....
[Samsung Galaxy Nexus] xxSAKISxx:
guys anyone use xlouder mod with last stable build? Does it work or not?
[Samsung Galaxy Nexus] amzad90:
I'm on Build 3 and would like to be on the latest build (4). How would I do this? Would i have to just flash it like a normal rom? Or are there shortcuts as its just an udate
[Samsung Galaxy Nexus] atljatl:
Wiping everything (system and data) is always recommended for a good and clean install.. BUT.. I came from build 3 and dirty flashed (wiped cache and dalvik only) and have had zero problems with build 4
[Samsung Galaxy Nexus] ashclepdia:
I think that was their initial internal name for it.

Which reminds me, anyone who has connected to adb, what is the symbol that shows? I remember seeing a screen shot not long ago that showed the pie slice, I was just curious if they left it that way or what symbol they decided to use?

:D

(I haven't had a chance to load up yet lol)
[Samsung Galaxy Nexus] Sesme:
...

I wanted to know if it will be able to run MHL

Is Gnex run's kitkat

http://www.youtube.com/watch?v=Gld4RcF0MKc
[Samsung Galaxy Nexus] ashclepdia:
I believe they trying to say that USB MHL does indeed work.

(Some people call it HDMI but it isn't, although it's similar. It's a micro USB connection that you plug into device, then other end has HDMI output along with a cord to plug a charger into to power it. Mirrors device to larger screen)

---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------

Edit::

(I can't edit via tapatalk for some stupid unknown reason)

That pic/reply was hilarious

---------- Post added at 08:18 PM ---------- Previous post was at 08:17 PM ----------

Edit again, apparently I was wrong, I thought they meant it DOES work.

I'll try if I'm able to load up tonight and let ya know the answer.
[Samsung Galaxy Nexus] dudeman1996:
I just tested MHL, it works fine.

such definition wow very mirror

much big so mhl wow

so usb wow such run's
[Samsung Galaxy Nexus] ant49:
I can not install the Slimkat, when I try to install the zip file gives me error:
[Samsung Galaxy Nexus] misterk267:
Wrong recovery. Must utilize the CWM for proper install.
[Samsung Galaxy Nexus] ant49:
Thanks! Now Work!
[Samsung Galaxy Nexus] fairct:
It's 3 little bars, which I'm guessing is a kitkat bar haha
[Samsung Galaxy Nexus] ant49:
It's possible change the DPI and take them to the original value?
[Samsung Galaxy Nexus] cardboardhome:
For some reason, after flashing this rom, I get no mobile service. I still get wifi but it always shows 0 bars and says emergency calls only. I tried flashing other roms and reflashing this one and there's no change. I even flashed stock 4.3, but no change. Any ideas why?
[Samsung Galaxy Nexus] galapagos:
ItHalf of the "issues" or questions can be resolved by reading the OP's post on the first page. The other half of the "issues" or questions can be resolved by reading on responses in this thread. But many of these questions are so fundamental in nature (i.e., how do I install this ROM?), it seems as though only noobs are installing this ROM.
[Samsung Galaxy Nexus] dirtygoldfish:
This has been brought up quite a few times already. Do some reading or do some Googling.
[Samsung Galaxy Nexus] chding:
Using GE launcher or aosp launcher?
[Samsung Galaxy Nexus] -Jesco-:
Great deep sleep happening here :) slept with 50% woke up 8 hours later with 49% , great job slimkat
[Samsung Galaxy Nexus] akash3656:
Turn dynamic fsync off as this ROM tends to have random reboots but hey its an alpha. Having dynamic fsync on increases the chance of having corruption on the /data partition when the phone crashes or needs a battery pull.
[Samsung Galaxy Nexus] kufikugel:
guys,

just a small heads up....after working now 10h non stop on the rom, on other device bringups, between features and request and fighting with our maguro surfacflinger problem which both roms currently have I need to sleep.

So build will come when I am awake lol. Want to add the new reboot menu we have done and maybe another try to fix surfaceflinger without breaking anything other lmao

maybe I am just to tired.

I am so nerved that I added notification light patches and battery light patches and our PrivacyGuard implementation we did for CM just to see something other then the device trees lmao

So a lot will come tomorrow.....hopefully as well approvements to surfaceflinger and gpu drivers which are on both roms the reason for the graphical glitches and the reboots from time to time

if any other dev has anything to suggest I am open for everything :D

cheers and good night
[Samsung Galaxy Nexus] baldwinguy77:
Great work on your ROM so far! It looks great and you were super fast at putting it together! I just posted my toro ROM over on RootzWiki (I'm sorry, I'm sorry! No hate towards XDA though) a little bit ago. Having the same webview graphical glitches that it seems like you guys are experiencing, and just wanted to see if you want to try to work something out together. I know you're done for the night now, but feel free to PM me later if you're interested!
[Samsung Galaxy Nexus] msip:
you truly deserved it.

good night!
[Samsung Galaxy Nexus] cardboardhome:
seriously, does anyone know how to fix the lack of signal? I can't get any mobile network signal on any rom and its really frustrating.
[Samsung Galaxy Nexus] migueldbr:
you probably messed up your imei...i heard that if it gets messed up it cant be registered to the network. check your imei and see if it is the same
[Samsung Galaxy Nexus] dharmabm:
Changelog recommends manually wiping system when dirty flashing this upgrade, which I did, with no problems and no data loss
[Samsung Galaxy Nexus] aliesz:
The latest stable build 4.0 with fancy r45 kernel works without any problem and it is very smoth and fast here..:)
[Samsung Galaxy Nexus] Doublewise:
Hi, day dream is not work if I screen off manually, only work when auto off. Is it suppose to be like that?
[Samsung Galaxy Nexus] molimo:
Hi Friends,

I've flashed second stable slimKat Rom but there are some question:

1- How can active "All recent Activity Clear" ?

2- Is there any special setting to improve speed even though the rom is fast enough?

3- What is "smart Pulldown" I couldn't find out?
[Samsung Galaxy Nexus] Nebucatnetzer:
1. Pinch

2. Disabling the animations in the dev options makes quite a difference

3. It allows you to open the quicksettings when there aren't any notifications.
[Samsung Galaxy Nexus] Doublewise:
[MENTION=4790322]kufikugel[/MENTION] [MENTION=3609932]Nebucatnetzer[/MENTION]

Pinch to clear all recent means for two handed operation. Other alternative such as swipe right (swipe left to clear specific app), double tap or use a button to clear all are more ergonomic also for single hand operation IMHO.

About progress bar, could you check this xdaforums.com/showthread.php?t=2618262

This way smoother & customizable and I believe it still match with slimkat philosophy.

And could you bring back power toggle in notification drawer like slimbean. So we can use quick toggle and check notification at once. More efficient.

Thanks for your hard work.
[Samsung Galaxy Nexus] zbeky:
I don't know how about you, but I can easily pinch with one hand too. Thumb at the bottom, other finger at top and just move them towards each other
[Samsung Galaxy Nexus] redj12:
Spent many times on this kind of features is useless in my opinion because your are not supposed to kill your app manually.

If you want to be efficient, you should enable SmartPulldown in the options.

If you want all these features I recommend you the CarbonROM.

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] prbassplayer:
Kill all is something that shouldn't be done at all. We however added the feature because it does help finding memory leaks and such, but we made it so its not easy on purpose.

And why in all that is holy would we bring back something that was designed for eclair? Android moved on, so did we. We however made it so QS is faster and easier to access either using quick pulldown or smart pulldown.
[Samsung Galaxy Nexus] Doublewise:
I just suggest other easier way to kill all that already exist in the rom.

Smartpulldown is different, it can't open clearable notification and quick setting at once.

Btw, this only suggestions and depend on the dev whether to implement or not.
[Samsung Galaxy Nexus] friedCELLS:
This ROM with fancy kernel is the fastest that my phone has ever been. Thank you SlimKat! Running ART very stable here. Changed DPI to 300 with texdroider app and changed softkeys with softkeyz root app.
[Samsung Galaxy Nexus] buckowski:
Aftet update to last stable version my gps stoped working.

Odesláno z mého Galaxy Nexus pomocí Tapatalk
[Samsung Galaxy Nexus] Nebucatnetzer:
Could you post a bugreport?

Settings/Slimcenter
[Samsung Galaxy Nexus] 2LoT:
Can you please give some technical background as kill all is not recommended? Thanks in advance.
[Samsung Galaxy Nexus] Nebucatnetzer:
http://slimroms.net/index.php/faq/slimbean/238-why-do-i-have-less-memory-free-on-my-device
[Samsung Galaxy Nexus] kufikugel:
As addition to nebus link.

When you do a MAT analyzing of the heap dump to see what is going on memory wise you have two situations

Normal situation: system keeps apps in memory. System detects oh I need more...it kills the app and frees the resource references the app uses so that the garbage collectors can remove it from the memory.

Kill all: user kills all apps on purpose. What happens: the system kills all the apps and frees the resource references (which is an extremely expensive task for the system). So but it is not doing what the user think. The memory is still in use....just does not have a reference to it. Means next time the system decides that it needs more memory it finally garbage collects it.

So you see the situation is exactly the same. Only difference is the time when the references getting free. The memory handling for both is the same. But kill all compared to let the system handle it brings the system into a situation were it needs to do a lot work without a need to. That simply why Google never and never will include a kill all.
[Samsung Galaxy Nexus] xxSAKISxx:
Now that is a very good explanation about what kill all means and what happens when we press the button. Thank you [MENTION=4790322]kufikugel[/MENTION]
[Samsung Galaxy Nexus] buckowski:
Here it is

https://www.dropbox.com/s/khlq3qlkhfpiir0/bugreport.zip

I've tried to reboot device and turn gps on and off but it is still not working.

Odesláno z mého Galaxy Nexus pomocí Tapatalk
[Samsung Galaxy Nexus] hardstyle86:
Little bug on Google Apps.

When selecting a row, a blue line appears also within the action bar.

I'm on latest stable (clean flash) with 280 DPI.

Examples of Gmail, Quick Office and Gallery in the attachments.
[Samsung Galaxy Nexus] buckowski:
Phone is really slow too. I used dirty flash with formatting system. I'll try clean flash.

Odesláno z mého Galaxy Nexus pomocí Tapatalk
[Samsung Galaxy Nexus] bluesock:
Background Info: I just got a Galaxy Nexus and directly went from stock 4.3 to Slimkat build3 by fastboot oem unlock etc. and installing cwm.

I previously made a backup of my previous phone (Motorola Defy) with "adb backup -apk -noshared -all -nosystem" and then used "adb restore" to put it on build3, but manually used "adb push" for some of the sdcard contents (instead of -shared option) from my defy to the galaxy nexus internal sd. The Defy was running a more or less experimental CM11 (Android 4.4).

From build3 after 2-3 days there was build4 and I "dirty" upgraded to it by wiping /system /cache + dalvik (just kept the /data from before)

Now there are more or less minor issues which I either just didn't see in build3 because of only 2-3 days of low use, or they came with build4, and maybe they are even to be expected:

1. Sometimes I had an app crash immediately when starting it for the first time(after that running fine), it might be only from the apps that I previously have from my adb backup (and also not all of them), but I am still investigating. I should have written it down maybe... Maybe an adb backup sideeffect though.

More or less feature issues / localization:

2. On the lockscreen the temperature seems to be shown in Fahrenheit (it's also not very nice to only show the degree symbol but no 'F' or 'C'), can this be set to Celsius or deactivated/replaced entirely? 24h Format works, but no idea where to set Celsius instead of Fahrenheit. I think (but I am not sure) that build3 had celsius temperatures there..

3. Can the Recent Apps Display be changed back again to the original one? I couldn't find an option for that. Two problems with the new one:

3.1. With the larger app-preview I was sometimes still be able to read something from one app that I needed in another, which I can't do now with the smaller app previews.

3.2. In Apps running in full-screen, I was previously be able to press the recents-button and was then able to see the the whole status bar and could pull the notifications down if required. The new recents does only scroll in from one side but the notifications cant be accessed or seen like that. I have to go back to home and with recents go back to my previously used app, which also require time to find. These are unnecessary multiple steps involved now. While 3.1. isn't that bad, this here is really a usability killer for me....

Thanks for any ideas/solutions to my issues!
[Samsung Galaxy Nexus] kufikugel:
1. Well we did not have any report of app crashes across all devices. If you cannot resolve it we need logcats.

2. Yes in the dashclock settings you can change it when you clock in the settings on the menu button for weather.

3. No

3.1 well you can increase the overall DPI. The thumbnail size is not much different from stock

3.2 I do not really get the problem lol. Since KitKat you can always just swipe down the statusbar from the top if an app is in fullscreen or immersive mode.
[Samsung Galaxy Nexus] Nebucatnetzer:
1. Sounds like you should try a clean install.

2. Next to the clock you should see a gear. When you tap on it, it will open the options for the dashclock app.

3. Nope this version will stay.

3.1 You can change the size in Settings/Accessibility

3.2 You still can open the notifications drawer.

Edit: Lol ninjad by Kufikugel
[Samsung Galaxy Nexus] bluesock:
1. Ok, for now I am guessing adb backup side-effects. I will see if it happens for new apps too.

2. Somehow I can't find this, where is this supposed to be? If I am clicking on the temperature / weather from the lockscreen, the browser opens with a google search, searching for "weather" instead of opening some app or anything. Maybe this is wrong and should normally open these settings?

Okay thanks I didn't know this :laugh: - the only problem is now with some apps that still take the sliding as an in-app action at the same time. But that is acceptable.
[Samsung Galaxy Nexus] kufikugel:
2. Expand on then lockscreen with a swipe down on the widget the widget. Then you will see the settings gear on the top right.

3. Well yeah still some apps did not implement it correctly so that it indeed a touch can go trough to the app. Basically an app problem. Though I think about to cover this on the firmware side....Google missed IMO a bit this case lol especially on older apps which do not update anymore but have full screen support.
[Samsung Galaxy Nexus] bluesock:
Size can only be decreased there and not increased (100%, 85%, 70% are the options). But thanks, maybe increasing DPI again and then setting smaller fontsize etc. could help. If just the icons wouldn't be that big then... a 125% option would of course be the best ;)

2. Cool thank you very much, this works, and wow, there are bunch of much more hidden settings. :)

3. For now it's okay, a workaround is to open recent apps and drag down the statusbar where the recent apps are shown, one step too much for these specific apps but otherwise less annoying.
[Samsung Galaxy Nexus] erghetto:
fantastic result on quadrant o.O
[Samsung Galaxy Nexus] amzad90:
Okay ill a dirty flash and if I do experience problems the I'll do a clean one.

After I perform a dirty flash I just flash the gapps as normal don't I?
[Samsung Galaxy Nexus] Nebucatnetzer:
Depends if you wiped /system.

If you don't wipe that partition you don't have to flash the gapps.
[Samsung Galaxy Nexus] kufikugel:
Maybe you should learn to flash correct + working on your attitude.

On top you do not think that we would have already tons of reports here?

Unbelievable really.
[Samsung Galaxy Nexus] qu4nd:
Working stable, fast and without an issue here! Great job! Some people just don't get it...
[Samsung Galaxy Nexus] friedCELLS:
Yeah, I've tried many Roms, but for me this is wonderfully stable and the fastest that my phone has ever been. I have had 0 issues and use my phone a lot. I have none of what you say. Stable is a good name for me....
[Samsung Galaxy Nexus] JG:
New Weekly

http://www.slimroms.net/index.php/d...10139-slim-maguro-4-4-2-build-4-2-weekly-3744
[Samsung Galaxy Nexus] Natakranta:
can't reconnect to Google services on WiFi

4.0 clean flash, slim karnel running Dalvik. No moods, no change. Default slim setup apart of DPI to 300 and aosp keyboard replaced with Shafta Google keyboard.

I don't tink it's SlimKat as this Maguro has this problem since I bought it in May last year on stock 4.2.2, aokp, stock 4.3, SlimBean 4.2.2, 4.3 and SlimKat now since I've been flashing it.

When it lose WiFi connection, it reconnects afterwards only to show orange WiFi bars. Dolphin can't open web page and advises there's no internet connection. Restarting Dolphin change nothing. I have to toggle WiFi off with QS tile, wait few seconds and toggle WiFi back on. Then it quickly reconnects and shows white bars. Internet access is back. Bug report attached, look at the end of file because phone is running 2nd cycle of charge, for last 4 days and still on 32% battery as I'm writing it now :) of course I want to finish this cycle to see how long this smartphone can be a phone. 1:40h SOT so far running for 4 days! :cool: (Airplane mode over night, WiFi always on - just a convenience to my wife, taker is switching off mobile data when home WiFi is connected, location on battery saver. BT off, GPS off, location history and reporting off, G-Now off)

I'd appreciate if somebody could throw some light on it, point me in a right direction, advise if it is repairable, or my Maguro is a lemon :(

Edit:

So I've just juiced out the battery (rapid slide down at the end) playing with the phone and downloading today's weekly 4.2 which I'm about to dirty flash now.

Before doing so some screen shots from battery life (Samsung extended 2000 mAh). I'm very happy with it. So is my wife. Since she stopped playing Candy Crush Saga she can charge her phone every four days instead of every evening after she drains it :D
[Samsung Galaxy Nexus] LibertyMonger:
Thought I would give the latest stable another shot since hardly no one is reporting any issues. The first time I installed it I was running Franco kernel and this time I used Fancy kernel. I had freezes and reboots again today while running maps navigation and trying to open phone. I don't have any issues like this with the 3.4 weekly, it is the build after the first stable release. I have been flashing each and every build and getting these same type freezes and reboots on every build except 3.4 weekly. Here is my bug report, I had to wait a few minutes after bootup cause I had to finish getting my directions from maps so hopefully it shows the bug report. SlimKat 3.4 is the only stable ROM out in my opinion and experience in case anyone has the same issues as me and want to try it. Thanks for the great support I love SlimKat and will hang tight on 3.4 while testing the weekly's. :good:
[Samsung Galaxy Nexus] Nebucatnetzer:
Does happen on the stock kernel as well?
[Samsung Galaxy Nexus] vivekbalan:
I don't know what is the reason for your issues but in my case all Weeklies (including the recent one) and Stable versions run smoothly without any freezes or reboots. In my opinion, SlimKAT achieved Daily driver status from the first beta build itself. Thanks Slim team for your wonderful work.

[Edit] in case if you are using Fancy Kernel versions r46, r47 or r48, users are reporting these kind of issues (reboot, kill all apps and freeze) in these kernel versions (refer Fancy thread). So try to reproduce these issues with Fancy r45 and report. Try clean flash also.
[Samsung Galaxy Nexus] Charmacas:
boype ported the lmk from hammerhead. But the minfree values are not right anymore. You have to set them way lower then before. r48 with the right values is running well with SlimKat.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] LibertyMonger:
I will run stock kernel today and see. All I know is build 3.4 runs flawlessly with Franco, I been running it since it's release. I am quite sure with the nature of my freezes compared to 3.4 that it is not kernel related. But I thought having a bug report would determine that but I don't know anything.

---------- Post added at 07:08 AM ---------- Previous post was at 06:57 AM ----------

Yeah well I used to think my freezes were kernel related as well until I ran the stable kernels with SlimKat build 3.4. There is a possibility it is the ROM and these reports on kernels are mistaken.
[Samsung Galaxy Nexus] Nebucatnetzer:
The thing is that I can't read the reports.

I just filter the feedback for kufi.

And if it's caused by a custom kernel then it's no our problem.