yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] cammi123:
Flashed last build clean, and like in other LP Rom's I have reboots, here logcat.log and maybe someone can help me why I have this reboots when screen off, thanks!

Logcat.log

--------- beginning of main

V/Term (17803): onCreate

D/OpenGLRenderer(17803): Use EGL_SWAP_BEHAVIOR_PRESERVED: false

D/Atlas (17803): Validating map...

D/Term (17803): TermService started

I/TermService(17803): Activity called onBind()

D/libEGL (17803): loaded /system/lib/egl/libEGL_mali.so

D/libEGL (17803): loaded /system/lib/egl/libGLESv1_CM_mali.so

D/libEGL (17803): loaded /system/lib/egl/libGLESv2_mali.so

E/ (17803): Device driver API match

E/ (17803): Device driver API version: 23

E/ (17803): User space API version: 23

E/ (17803): mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct 9 21:05:57 KST 2013

I/OpenGLRenderer(17803): Initialized EGL, version 1.4

D/OpenGLRenderer(17803): Enabling debug mode 0

I/Term (17803): Bound to TermService

I/TermService(17803): Activity binding to service

I/libjackpal-androidterm(17803): JNI_OnLoad

I/Term (17803): waiting for: 17830

I/Timeline(17803): Timeline: Activity_idle id: android.os.BinderProxy@1717c8b2 time:7330658

W/IInputConnectionWrapper(17803): showStatusIcon on inactive InputConnection
[Galaxy S II Android Development] danielbe:
I'm not sure, but the end line says it couldn't run the showStatusLine method as the screen is off and it crashed. That's my guess.
[Galaxy S II Android Development] stylemessiah:
Good news for anyone wanting to run Xposed and Greenify

The latest xposed sdk zip from here:

http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979

The non-64bit one - xposed-sdk22-arm-20150514.zip

Plus the latest Greenify 2.6.2 beta 5 from here:

https://plus.google.com/+apkmirror/posts/D56oFWxiJFP

Equals working Greenify.....

I couldnt even get the previous xposed sdk to flash without it ending in a bootloop and needing a nandroid restore, but the latest one works and perfect timing as the latest beta for greenify added 5.1 support

To avoid testing each xposed module like i did, do the saner thing and see what other xposed modules work (updated for the latest xposed release above) here:

http://xdaforums.com/xposed/modules/discussion-xposed-modules-5-1-lolipop-t3075257
[Galaxy S II Android Development] cammi123:
Maybe this logs if someone understand show us right why I have reboots, I think because off my Wi-Fi (my wifi don't work and from that time I have this reboots), but if yes why I have reboots even if I switch to airplane mode, ore if yes how can I turn off all wifi settings and if is possible to use just cellular data!

Sorry if I break the rules!

05-14 13:49:00.564 E/wifi (2359): error at line 318: android_net_wifi_getInterfaces null interface array

--------- beginning of crash

-05-14 13:49:00.586 E/AndroidRuntime(2359): *** FATAL EXCEPTION IN SYSTEM PROCESS: WifiStateMachine

05-14 13:49:00.586 E/AndroidRuntime(2359): java.lang.Exception: android_net_wifi_getInterfaces null interface array

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiNative.getInterfacesNa tive(Native Method)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiNative.getInterfaces(W ifiNative.java:1203)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiNative.startHal(WifiNa tive.java:1181)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiNative.getWifiLinkLaye rStats(WifiNative.java:1518)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiStateMachine.getWifiLi nkLayerStats(WifiStateMachine.java:1806)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiStateMachine.handleScr eenStateChanged(WifiStateMachine.java:3181)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiStateMachine.access$27 00(WifiStateMachine.java:141)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.server.wifi.WifiStateMachine$DefaultSt ate.processMessage(WifiStateMachine.java:4944)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.internal.util.StateMachine$SmHandler.p rocessMsg(StateMachine.java:967)

05-14 13:49:00.586 E/AndroidRuntime(2359): at com.android.internal.util.StateMachine$SmHandler.h andleMessage(StateMachine.java:790)

05-14 13:49:00.586 E/AndroidRuntime(2359): at android.os.Handler.dispatchMessage(Handler.java:10 2)

05-14 13:49:00.586 E/AndroidRuntime(2359): at android.os.Looper.loop(Looper.java:135)

05-14 13:49:00.586 E/AndroidRuntime(2359): at android.os.HandlerThread.run(HandlerThread.java:61 )

05-14 13:49:00.596 D/VoldCmdListener(1854): cryptfs getpw

05-14 13:49:00.618 D/VoldCmdListener(1854): cryptfs clearpw

05-14 13:49:00.630 I/Process (2359): Sending signal. PID: 2359 SIG: 9

05-14 13:49:00.665 W/Sensors (7962): sensorservice died [0x427d3940]

05-14 13:49:00.667 D/SurfaceFlinger(1855): Set power mode=2, type=0 flinger=0x40882000

05-14 13:49:00.667 E/SurfaceFlinger(1855): eventControl(0, 1) failed Bad address

Spoiler content hidden.
[Galaxy S II Android Development] :
@up lol dude, post your log here

Spoiler content hidden.
[Galaxy S II Android Development] maniknarang:
Finally, SIM PUK fix has been merged in the base package. No need to add it again and again!

Soon...

Regards.
[Galaxy S II Android Development] cammi123:
Thnx.
[Galaxy S II Android Development] maniknarang:
New Update

Hey!

SlimLP is making considerable progress! The team has added NavBar + Customizations, some Torch and Camera Rebinding, some more Tiles, the SIM PUK fix and a lot other fixes. I will build later today and upload soon!

Regards, and till then, KeepItSlim! :D
[Galaxy S II Android Development] keepasa:
Is anyone getting occasional google play services stopping notices?

I performed a cache & dalvic cache clear. Then data wipe and system format. Flashed beta 8 ROM then flashed Slim_ADD-ON-5.1-MULTI_DPI-20150516.zip from OP link. And finally super user zip.

The multi DPI was the only installable gapps since even the slim zero gapps said not enough system space.

Perhaps I missed something or something with gapps. Any help would be appreciated.
[Galaxy S II Android Development] wembleyy:
This is great news for me, because i'm SlimLP fan. The rom is very stable , which is most important for me... i dont excange stability over heavy customization. I have minor bugs (like front camera, can't search networks), nothing that i can't live with. I like android lollipop and stability, great work [MENTION=5419355]warrior1208[/MENTION]

[MENTION=5424021]keepasa[/MENTION] i have no FC and no problem with google play services...and i dont need to restart my phone from time to time. It never freezed or restarted on build#8
[Galaxy S II Android Development] painx:
Should I wipe all data when upgrade from 5.0.2 to 5.1.1?
[Galaxy S II Android Development] :
Probably yes. Too many changes.
[Galaxy S II Android Development] stylemessiah:
Another day, nothing to report

Has to be the most undramatic and stable ROM ive ever used for a Beta.....even stabler than my first foray into my previous and favourite - SlimSaber
[Galaxy S II Android Development] maniknarang:
Thanks. That's really nice to hear.
[Galaxy S II Android Development] sreinst1:
Do you use the same apps (with the same configuration) as you had in SlimSaber?
[Galaxy S II Android Development] stylemessiah:
Lol, i havent gotten round to putting them all back on, but yes, so far, i have about 90+ apps on there

Apart from BetterBatteryStats, where i had to make a folder under /system/priv-app/ and copy the apk into it (and thats not the ROM's fault, im led to believe its not uncommon to have to do this), no app has so far caused a moments drama

If anything was not going to work i would think it would be all the xposed modules i normally use, like greenify and amplify etc, and even those have given me 0 drama.
[Galaxy S II Android Development] sreinst1:
I'm not referring to apps that would not work; when you say it's more stable than SlimSaber, and has no problems, I'm interested to know if you're using it exactly the same way. E.g. you might discover, once you install everything that you used to have in SlimSaber, that the ROM will start crashing every now and then, or the battery will drain a lot more. (I hope not, but just like to put things in perspective, since I consider moving to SlimLP myself if it indeed has 0 problems with the same usage).
[Galaxy S II Android Development] stylemessiah:
I think i answered all those concerns you have with my first post today, on day 3 or 4 of using it:

I understand youre concerned, but i dont move ROM's for the fun of it, im not a ROM junkie or a tinkerer (dont have the time for it these days), im just an ordinary bloke who needs his phone to work and i wouldnt have a ROM on longer than a day if it wasnt stable. Cant afford the downtime or drama.

You can keep looking for issues, but i can only say i havent had any

Your experience may be different....but mine so far, no issues

Edit: Updated my sig to reflect that im now using this, i dont make changes/promote unless something works :) The SlimSaber KK part will come off, probably sooner than i thought :)
[Galaxy S II Android Development] mariox_92:
Does this ROM have freeze problems like in CM12.1?? [MENTION=5419355]warrior1208[/MENTION]

I think I am going to have a try on it. I will wait for next build as you said we are having it soon:)

Thanks for all your AMAZING work!
[Galaxy S II Android Development] Zile995:
Rom doesn't have freez problems. Overall it's better ROM, smoother and faster than CM.
[Galaxy S II Android Development] maniknarang:
As Zile995 very correctly said, the ROM doesn't freeze. As far as comparison with other ROMs is concerned, I'll leave that for all of you to decide! ;)
[Galaxy S II Android Development] mariox_92:
Great news, waiting for next build then! Thank you all for your quick replies:)
[Galaxy S II Android Development] sreinst1:
What do you mean by "come off"?

---------- Post added at 06:56 PM ---------- Previous post was at 06:51 PM ----------

Thanks for the info. I am interested to know, before trying it out, does the bluetooth work differently in this ROM vs. CM? In CM (and many other ROMs), there is a problem playing music in my car's audio system via bluetooth. The bluetooth works fine for phone calls through the audio system, but when I come to play music (or podcasts), I get a 1-second silence after each 1 second of music.

The ROMs I tried are: Mokee, CM, SOKP, BlissPop, and probably a few others I don't remember.

I haven't tried this with Omni or Slim LP. However, the bluetooth works fine with the car's audio system in all KK ROMs.
[Galaxy S II Android Development] stylemessiah:
Meaning i will probably remove the lines about SlimSaber from my signature soon, as the SlimLP becomes my main and only ROM
[Galaxy S II Android Development] otti17:
I'm on BlissPop and having no troubles playing music via BT in my car (JVC KD-X50BT).
[Galaxy S II Android Development] hispanico957:
Which GAPPS you advise to install ...this Slim_normal_gapps.BETA.5.1.build.0.x-20150516.zip ??

Thank

Hispa
[Galaxy S II Android Development] wembleyy:
I use Slim_zero_gapps.BETA.5.1.x.build.0.x-20150508.zip on this rom.

No problem with BT playing music
[Galaxy S II Android Development] tobemaster:
Regarding the SIM/PUK Issue... I disabled PIN Security on another Smartphone.

Hope this helps :)

Beta8 is very fast!! stable and smoth, came from 5.0.1x with full wipe.

Thanks warrior!
[Galaxy S II Android Development] sreinst1:
Well I guess it depends on the car stereo system. For me, BlissPop did not work. All KK ROMs work, so I am hoping that SlimLP will, because it started with the KK device tree.
[Galaxy S II Android Development] Nick_Knight:
[MENTION=5419355]warrior1208[/MENTION]

I use beta #5 with your kernel + Xposed-Framework and this combination is untoppable, performance battery stable. Do you think you make a new kernel for 5.1x than the old one is not working.

My opinion no new kernel no new build try.

Regards
[Galaxy S II Android Development] maniknarang:
Well, the BT in car should work fine. We have this commit included in the common tree.

https://github.com/warrior1208/devi...mmit/cd48678c5aa06df24b1f927e7a87ce1c67eef66c

There is no reason for it to not to work. Try again once on the new build.

Regards.
[Galaxy S II Android Development] maniknarang:
Beta#9

Beta#9 (18-05-2015)

Updated Slim Sources to 5.1.1 Revision 2

Fixed SIM PUK Bug

Fixed Lock Screen Notification Expansion

Added NavBar and Advanced Options

Added Car Dock Analog Audio Support

Added Notification indicating Flashlight is Active

Added Double Tap action to Lockscreen Shortcuts

Added CPU and RAM Info in About Phone

Added SlimLP Logo in About Phone

Added QS Four Tiles Per Row Option

Re-Added SimpleFileManager

Re-Added Advanced Doze Options

Re-Added Option to hide Network Activity Arrows

Re-Added Option for SuperSU Icon in Status Bar

Re-Added Hardware Buttons Options

Re-Added some more QS Tiles

Re-Added Recent Apps Clear All Icon

Materialized Some Apps

and Much More

More surprises to come soon! Till then, KeepItSlim!

Best Regards! :)
[Galaxy S II Android Development] sreinst1:
I've just tried SlimLP, the previous build (9/5) for a couple of hours. The problems I found:

1. Initially, after installing many apps at once from the Store (after a clean flash), I got notifications about the new apps installed, but these notifications were blank in the notifications panel. I could only see them in the lock screen. The notification panel had about 2 blank entries (where the panel is completely black) and below it, some more notifications. I wish I knew how to take a screenshot of that, I didn't find this option in the power menu and didn't find how to add it to the power menu or any option to do it using QS tiles. After a reboot, this problem was gone, and I now see all notifications in the notifications panel.

2. HUGE lag of the dialer app: I got an incoming call, and I could only reply after about 5 seconds! Call was almost over when I finally could press the reply button.

3. More of 2: Pressing a contact in the dialer takes 7-8 seconds until the call actually begins. During these 7-8 seconds, nothing changes in my phone screen.

I will try the new version now. Can I dirty flash this time?

Edit: The "four QS tiles per row" also existed in the 9/5 build. It's not new in the new version...

Another edit: I did not flash the Slim kernel separately, I am using the stock kernel that come with the ROM. Is it recommended to flash the Slim kernel if I have no intention of messing with scheduler/overclocking?
[Galaxy S II Android Development] Dr AM:
Thank you

Is hw overlays bug still there ?
[Galaxy S II Android Development] cascabel:
Good day. I apologize if this is not the proper place for this, but i have done multiple google searches on this topic and i got confused with the info i got. I'd really appreciate any help i can get.

This is the first sammy phone i've tried flashing custom roms on (all my devices are sony devices) so i am pretty much a noob here.

I've been trying to flash this rom (beta 8) and i keep getting the error "failed to mount/dev/block/mmcblk0p9 at /system: Device or resource busy" when using twrp. On philz/cwm there is no error. Unfortunately, the phone goes back to recovery when i try rebooting it. After every clean flash. I have yet to try going back to stock via odin (i can't right now since i'm away) but is there anything i can do? I'd love to have this rom up and running on my phone. GT-I9100... It's currently on omnirom 5.1.1.

Thanks in advance. If there is already a thread for this i apologize.
[Galaxy S II Android Development] :
[MENTION=5419355]warrior1208[/MENTION] your SlimLP Kernel works on newest builds? or makes bootloop?

Sent from Tapatalk Tokyo
[Galaxy S II Android Development] amwahab:
Download Error, download the Rom from other source and try again
[Galaxy S II Android Development] _followers_:
hey guys what kind of apps do you use for mms back up?.. I try to replace the MMS of this rom with other rom but all I got is FC...cuz this Rom use other MMS . :D
[Galaxy S II Android Development] sreinst1:
Flashed Beta#9, and slim zero gapps (also tried slim mini gapps) with a clean flash, and I can't set it up because it keeps showing dialogs with something like "System UI has crashed" (translating from Hebrew). If I click Ok to close this dialog, another one comes up 1 second later, and so on.
[Galaxy S II Android Development] wembleyy:
Flased beta9 with the lstest slim zero gapps. No problem so far
[Galaxy S II Android Development] sreinst1:
Went back to Beta#8 after the problem with #9. In #8, if I connect my earphones, I see an icon for it in the status bar. However, when I try to change the ringtone for notifications, whenever I click another ringtone, the ringtone is played through the phone's speaker and not through my earphones...

---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------

Did you dirty flash? When I clean flashed it, I couldn't use it at all. Didn't try dirty flash, but it means there's a problem with the rom or with the gapps.
[Galaxy S II Android Development] wembleyy:
I allways do CLEAN flash. Maby the custom recovery counts? I USE this every time Once i tryed the latest version and i had problems flashing gapps. Then i flash only with the cwm from the link.

Reboot to recovery, install cwm (form the link above), wipe data/factory reset, wipe cache partition, wipe dalvik cache, install rom, install gapps, restart (and i select NO, do not restore root). I use stock pit, i do not chose to restore (i have standard apps...whatsapp, fb, tapatalk, mega, some calc, dropbox, hangout, google maps, here etc). It works great so far! And, the most important, i do not lose my personal data (photos and other files).
[Galaxy S II Android Development] sreinst1:
So you flash another kernel just to have CWM? What is wrong with the stock one?

I did the following:

1. Coming from SlimSaber (KK), which has TWRP, I rebooted into recovery and did a "factory reset".

2. Still in the TWRP, I flashed the ROM zip file only, and then rebooted to recovery.

3. Now I'm in PhilZ recovery (the stock one, that comes with the ROM zip file). I do a factory reset once again.

4. Still in PhilZ, I install the ROM zip file.

5. I install the Slim zero gapps of 5.1.

6. I reboot the system.

The result is the continuous "ui stopped working" dialog.

In beta#9, did Slim finally add the option to configure all the volumes when you use one of the volume buttons? Or do you still configure only the current type of volume (e.g. ringtone OR media OR ...).
[Galaxy S II Android Development] cascabel:
[MENTION=5630829]sreinst1[/MENTION] still configures the current volume in use. But since xposed for 5.1.1 works with grav box now, it's easy enough to remedy that. Unless you'd rather not have xposed.
[Galaxy S II Android Development] sreinst1:
I don't mind using xposed if it doesn't affect (for the bad) stability, performance and battery. If it has a noticeable bad effect on either of these, I wouldn't want to use it. Though from what I've read in forums here, it sometimes improves battery life due to supporting something like Greenify (?).
[Galaxy S II Android Development] cascabel:
I mentioned you over at the Q&A thread for this rom. Unfortunately my mention failed. Lol.

I answered there so we won't clutter this thread and hopefully someone who knows can answer your question. [emoji1]
[Galaxy S II Android Development] wembleyy:
Flash the rom twice? that's ilogic for me. Why do i flash that specific CWM? Because i had trouble with othr recovery when flashing gapps. With that from the link works every time, you may give it a try (eaven if you have no faith). We have the same phone, if you do all the step i have done, then maybe it will work for you too. I use Slim_zero_gapps.BETA.5.1.build.0.x-20150516.zip (didnt flash supersu)

There is only one volume (media, alarm and ring volume are in the settings/sound &...). There is an option called Media control (Volume keys control media volume rather that notification, it is off by default). But we have battery percent and we can clear all recent app and more.
[Galaxy S II Android Development] sreinst1:
The first time, I flash the ROM only in order to get its kernel and recovery. After that, I reboot into the stock recovery. And then I flash it again, this time with the correct recovery.
[Galaxy S II Android Development] Gandalf19:
I come da SlimKat 4.4.4. No problem with clean flash.

Some questions:

- Where can I find SlimPie ?

- Where can I find switch for 2G/3G ?

- Where can I find setting for Media Storage ?

- Is there TRDS ?

- Is there governor settings ?

Thanks ^_^
[Galaxy S II Android Development] wihushae:
Upgraded with a clean flash Form beta 8 to 9 without and Problems :) [MENTION=5419355]warrior1208[/MENTION]: does the rom /device support HD voice, aka amr-wb?

THX for your great work!!
[Galaxy S II Android Development] silverio28:
the rom works with Mirroring chromecast?

or this app.

http://xdaforums.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193
[Galaxy S II Android Development] sreinst1:
Did you also go through a custom recovery for this? I tried twice, and both times I got into a loop of "user interface stopped" messages immediately after selecting my language (Hebrew). I'm beginning to think it might be language related... I will try English and see if it works.
[Galaxy S II Android Development] Android-Freak2012:
1.)

After the update from build#8 to build#9 (dirty flash) all works fine, but...

...has also struck you with the Beta#9 that in the "infos about the phone" except with the kernel (18.05.2015) with the other values with date (production datum, Slim version) stands still the datum of the Build#8 (09.05.2015)?

Strangely, or?

2.)

[MENTION=5419355]warrior1208[/MENTION]: your SlimLP Kernel works on newest build#9 or makes bootloop?

Thanks,

Android-Freak
[Galaxy S II Android Development] sreinst1:
Yes... Turns out my "user interface has stopped" problem happens when I select Hebrew as the phone language. No problem with English. Same happens if I change the language after the initial setup, using the settings.

I don't know if the problem is only with Hebrew out with all non English languages.
[Galaxy S II Android Development] wihushae:
[MENTION=298569]sreins[/MENTION]t: no, I didn't do a custom recovery (I think), at least not intentionally! :D how to do a custom recovery?

[MENTION=250713]Freak[/MENTION]: I think you are right, the about the phone section is the old one...
[Galaxy S II Android Development] JimboAccy:
Clean flashed from 8 to 9 - all phonecalls (incoming and outgoing) are now on speakerphone by default and I cannot toggle it off (worked fine on beta 8). Anyone else noticed this or should I just reflash :confused:

Jimbo

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

I use either the chromecast app itself or the mirror enabler v5 app (I found v6 and v7 don't work for my s2)

Jimbo
[Galaxy S II Android Development] Klaus20:
Upgraded with a clean flash Form beta 8 to 9 without any Problems - thanks for your work !!!

BT outgoing calls still have much noise and are difficult to understand

BT incoming calls are very clear and without any noise.

Regards Klaus