yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] AuSSiELaMbChOpS:
You don't need to be concerned about anything but what I was saying is that the external sd card issues are related to problems our device has with the fuse daemon, part of the daemon is in the android system core and another part is contained in a kernel module.

So if you are having issues then try using the stock kernel and see if that helps, I did a full wipe this afternoon and re-flashed my build from last night, restored about 50+ apps through Titanium Backup and since then I have been listening to music playing from the external sd card for about 3 hours with everything going flawlessly.
[Galaxy S II Android Development] pdario:
I ended up using Xposed just to have notification area draggable down in lock screen: is it possible to add this?
[Galaxy S II Android Development] Twiq:
very good info, i'll let dorimanx and the devs to take a peek at your commits, if it's necessary to be merged so they could take actions from it.

thank you ?

auto responding to problems
[Galaxy S II Android Development] Georgel25:
Just asking if they can be of any use for our rom; i thought that smdk4412 is for our device...the kernel i believe.
[Galaxy S II Android Development] fusionjack:
oh yeah, that is important information that i forgot to mention in the release post. :eek:

btw, concerning slimbean features that you are ported, i can try to integrate them in this rom if you want to share. save me time and effort to port them from slimbean. :p

our device (4210) is using smdk4412 tree, but smdk4412 is for exynos 4412 and 4210 devices. :)
[Galaxy S II Android Development] fusionjack:
updated release post with important information.

edit: ok, here for the lazy one. :p
[Galaxy S II Android Development] AuSSiELaMbChOpS:
Just issued a pull request for both items in Frameworks & Settings didn't know if you wanted to do it that way but if not you can close the pull requests and cherry-pick the commits from my github :victory:

Saves me time too as I don't need to cherry-pick the commits against the SlimRoms source, check it all again and submit for review.

Also I pushed a review for system_core that made some slight changes based on the AOSP master sdcard.c fuse daemon, one thing I noticed on your source was the commit sdcard: Respect check_caller_access_to_name on readdir() calls which is not found in either AOSP or SlimRoms source. If you are interested in those changes too they can be found in my latest commit on github here
[Galaxy S II Android Development] Hopper8:
Arrrrghh. If only stock kernel had BLN!! Otherwise stock kernel would be brilliant!... But I can't do without BLN :(

I am liking having you around more and more literally by the minute :highfive: :D

Sent from a galaxy far, far away
[Galaxy S II Android Development] j1gga84:
I want to use Omniswitch for recents apps panel.

I can set it and it works but after a reboot it is standard again and I have to re-set it :confused:

What can I do?

EDIT: ok, I think I found the problem. I disabled autostart in System Tuner Pro ;)

Regards
[Galaxy S II Android Development] fusionjack:
thanks.

yeah, i cherry-picked that commit from cm. i'd probably revert it and make the sdcard.c synced with aosp.

i usually like to reset a commit rather than revert it if i won't use that commit again in future. so probably you'll also need to push system/core with --force to your github. :p
[Galaxy S II Android Development] hispanico957:
thank again great FusionJack... but Random music player stop. isn't solved... :crying:

Hispanico
[Galaxy S II Android Development] fusionjack:
are you using stock kernel?
[Galaxy S II Android Development] jpeg725:
Is the part that is in the android system core in the initial ramdisk or does it reside in /system?

If it is in the initial ramdisk, then as that is bundled with the kernel it will always be compatible with the kernel in use, if the kernel devs have done their job right.

Good to see a dev taking an interest in our old device.
[Galaxy S II Android Development] hispanico957:
Yes... and the problem appear 2 times after 3/4 minutes of playing

Hispanico
[Galaxy S II Android Development] Kai Disobey:
Here are some interesting stuff from xdadevelopersTV

Android Basics 101: Understanding ART, the Android Runtime

http://youtu.be/USgXkI-NRPo
[Galaxy S II Android Development] shekharpati:
bugs & requests

i have been using this ROM since December. Most of the isuues have been fixed ... thanks to our hyperactive dev.:good:

but one issue still persists. occasionally my phone does not wake up from lock screen. the hardware keys light up but not the screen. have to do a hard reboot.

Also how do i send a contact from people app using messaging / hangout? there is a share option but that is default one which comes with every app. it does have messaging / hangout as an option :confused:

PS i am on the 10th feb build
[Galaxy S II Android Development] johnny208:
Hi. I don't have that issue with screen. Everything is spot on. :D

You can install a third party app to send contact info by SMS (look on play store; there are a lot). I'm not sure if this was ever available. I didn't use this or any other ROM than Slim since ages. :p
[Galaxy S II Android Development] clone.x:
This happen because of using ART, try to restart after moved apps into internal storage... :good:
[Galaxy S II Android Development] fusionjack:
hmm...i can play music from external sdcard more than 1 hour without any issues. i was playing them with es music player. i'll try with another music player later.
[Galaxy S II Android Development] fusionjack:
Another release...:D

SlimSaber-i9100-4.4.2-20140213.zip

Changes:

Bring back the status bar activity indicators for mobile data and wifi.

Recents RAM bar. Thanks to [MENTION=4661001]AuSSiELaMbChOpS[/MENTION] for forward port from SlimBean. AuSSiELaMbChOpS: There are still some missing changes from latest SlimBean, but not much. I can send you the path if you want.

Add cell broadcast receiver. I didn't notice this until I test the build. Freeze mobile broadcast apk with TB.

See changelog for the rest of changes.
[Galaxy S II Android Development] Georgel25:
Thanks for the new release...but i would like not to have cell broadcast receiver within the rom; removing the apk from the zip file is the only thing needed for not having it installed ?
[Galaxy S II Android Development] fusionjack:
did you read my message on the release post? :confused:
[Galaxy S II Android Development] Georgel25:
Yeah...i don't want to disable it, i don't want the rom to install it at all :D
[Galaxy S II Android Development] AuSSiELaMbChOpS:
Sure mate send my the info and I will have a look at it tonight.
[Galaxy S II Android Development] Hopper8:
Hmm.... Something odd going on. I restored a nandroid of my initial setup of 0210, dorimanx 10.43v60. Media scanner was permanently on. I tried wiping cache, dalvik and clear data for media storage and reboot.... But nothing worked. The only thing that worked : flashing apolo kernel :confused: now media scanner is back to normal. It's weird because I never had that on dorimanx in approximately a year :o :confused: Downloading latest build to test now :D

Edit: [MENTION=1228651]fusionjack[/MENTION]... Does that 'little bit to port from slimbean' include allow all widgets on Lockscreen, or power widget? :D :D *hint hint* :p

Sent from a galaxy far, far away
[Galaxy S II Android Development] clone.x:
... for me the music bug is disapeared after release 0212 too, i can listen mp3 more than 4 hours without any problems. Big thanks :good::laugh:
[Galaxy S II Android Development] johnny208:
Hi [MENTION=1228651]fusionjack[/MENTION]

I'm on latest built with art stock kernel.

After updating (cleaned dalvik and cache) I can't access status bar. When I drag it down I receive attached error.

Am I missing something!?

Thanks!

EDIT: BUG REPORT: https://drive.google.com/file/d/0B80IqWz_5_wTSnlQNkhTSl9GVkE/edit?usp=sharing

EDIT2: Flashed back 20140212 version and everything works ok... So i guess it's because ram bar thing?!?
[Galaxy S II Android Development] AuSSiELaMbChOpS:
I just looked through your logcat on my phone as I can not access google drive from my work pc, the exception refers to statusbar shortcut methods. Did you make any changes to your shortcuts on the statusbar??

The ram bar code does not touch the status bar or quick settings panel the only modification it makes to the SystemUI is to the Recents view, associated xml layout files and adds a couple of strings.
[Galaxy S II Android Development] Wongkonka:
Ty in general. Ty clicked
[Galaxy S II Android Development] Hopper8:
0213 working fine here with stock kernel (only on stock kernel to test). But no problems whatsoever with the ram bar or status bar. Great work Aussie and fusionjack, latest build running sweet :) :good:

Sent from a galaxy far, far away
[Galaxy S II Android Development] johnny208:
Thank you.

I had 2 shortcuts on status bar. Deleted them... Problem gone. :D
[Galaxy S II Android Development] AuSSiELaMbChOpS:
Did you set them back up ok? Might have just gotten corrupted somehow because the shortcuts definitely work.
[Galaxy S II Android Development] cripubu:
I use an app called texdroider https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=de. Works really great, also on ART. I am on 216, have read quite a while ago than odd numbers should be avoided.

good luck
[Galaxy S II Android Development] Wongkonka:
My GPS isn't working, in on 0212. Anyone else similar problem?
[Galaxy S II Android Development] pippone121263:
For me it is working fine
[Galaxy S II Android Development] AuSSiELaMbChOpS:
Just tried too and locked to 8 sats in under 20 seconds, have you tried a reboot? If you still have issues attach a bug report. :thumbup:
[Galaxy S II Android Development] kepeto:
hi [MENTION=1228651]fusionjack[/MENTION], this build causing systemUI FC over and over, reverted back to 0212

Bugreport : https://dl.dropboxusercontent.com/u/48627310/bugreport.zip

ps: flashing 0213 > SystemUI FC > flashing 0212 > generate bug report, i don't know this bug report is still valid or not

for better battery life it's ok to select zzmoove + row or ???

last few weeks i had trouble with SwiftKey which is always replaced with default AOSP Keyboard in random circumstances,

the solution is you have to disable AOSP Keyboard through System > Apps > All > AOSP Keyboard > Disable

thanks
[Galaxy S II Android Development] pdario:
Why keep it enabled, anyway?
[Galaxy S II Android Development] fubo73:
Hi there,

I did some tests with my BT system. In reality if I try to do more than one call, the system is not able to recieve calls or initiate any call.
[Galaxy S II Android Development] pdario:
Bad news: TB stuck again at 66% even after updating to 0213!!

I found this to be a common problem on 4.4.2, see http://code.google.com/p/android/issues/detail?id=63010

I read there that if you call a number from phone (only 9999 works?), then the system start working for that pairing session, and I confirm that work.

Maybe nothing can be done by SlimSaber team.
[Galaxy S II Android Development] johnny208:
I already installed the old version (20140212) after I sent the bug report and then you told me about shortcuts. Then I went to shortcuts (in the old version) and push restore defaults button. Then I reinstalled 20140213 update and worked fine.

I added again the same shortcuts and works OK... Weird.

So basically I don't know if just deleting the shortcuts would of fix the problem without reflashing... :what:

The most I regret is that I didn't wait your reply and I spent 2 hours downgrading and upgrading (I'm on art with 140+ APS to optimise each time). Next time I know: wait for the wise ones. :)

My status bar and toggles are completely changed and I've been playing with customisations so much(thanks [MENTION=1228651]fusionjack[/MENTION]) that I'm sure I won't be able to do the same. :)) that's why I didn't made a clean install since early January. :D

Thank you very much for your support!
[Galaxy S II Android Development] Nos_20:
I have just flashed 02/13 build. Dirty flash (wipe cache/dalvik) over last build. No systemui force close and I just backed up all my apps using TB with no problems.

All working fine here using the stock kernel.

Thanks [MENTION=1228651]fusionjack[/MENTION] and [MENTION=4661001]AuSSiELaMbChOpS[/MENTION] good stuff!!

Sent From My Galaxy S2
[Galaxy S II Android Development] johnny208:
Do what I did:

- go to settings/interface/notification &qs / shortcuts/ then push the restore defaults button (upper right corner - the round thingy with an arrow and a dot in the middle)

- then install the 20140213 update and it will work OK.

Thanks to the "guy with long username that I can't remember" :) edit: [MENTION=4661001]AuSSiELaMbChOpS[/MENTION] :)
[Galaxy S II Android Development] pdario:
I don't understand battery logic.

Full 100% charged, AC connected, reboot -> 97%??

54% on battery, force reset for a freeze, reboot -> 6%???

Can this depend on kernel?
[Galaxy S II Android Development] Maniac9331:
I never dad any problem with restoreing apps since 4 4 2 but i do it with rom toolbox no issue
[Galaxy S II Android Development] j1gga84:
[MENTION=1228651]fusionjack[/MENTION]

many thanks for this awesome update :good:

RAM bar in recents is back (in my opinion much better than OMNI switch but that is a matter of taste like everything ;) ) and the data arrows :)

What I miss now are two more things:

- Theme chooser (like everybody else I guess :D )

- Functionality of hardware keys when screen is locked (set system volume - for now I still have to unlock screen to do this but I guess it is also not yet working in CM :confused: )

Hopefully this 2 points will come soon, then KK for my S2 would be just perfect. Only the battery consumption is a bit higher than in 4.3.1 (in usage, DS is perfect!)

EDIT: What also not works yet is when I long press on Location (GPS) toggle I does not come to location settings.

Regards
[Galaxy S II Android Development] pdario:
Isn't it possible to also add draggabel notification bar in lock screen as it is with Xposed?
[Galaxy S II Android Development] Rachid.Ala:
Long press on location toggle don't work. I've just tested. It's not a problem for me since I never deactivate gps... anyway
[Galaxy S II Android Development] Biftor:
Thats working here drag bar notification panel on lock screen

Are you sure?

Hey all Whats the problem of systemUI reported ???bring log cat

Goodluck

Armin.
[Galaxy S II Android Development] pdario:
You mean withouth xposed? No!

Is there any option to turn on??
[Galaxy S II Android Development] Mosquito79:
In last built taking screenshots aren't working

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Android Development] Biftor:
You mean this?

Goodluck

Armin.
[Galaxy S II Android Development] Kai Disobey:
+1 :highfive:
[Galaxy S II Android Development] fubo73:
Hi all,

farewell, I am going back to JB stock. It was a great adventure with you last two months, but I am experienced KK it's not good for my day-by-day usage. BT issues plus low volume (lost a lot of incoming call) plus unable to get used to pure android experience (never get used to dialer) plus some random crash (with no reboot, so phone off for hours) convince me that I am not ready for KK.

I'll keep following you master [MENTION=1228651]fusionjack[/MENTION].

Happy kitkat'ing!!!
[Galaxy S II Android Development] Georgel25:
I don't think it's kernel...i believe the battery stats readings are incorrect, and that's from the rom; maybe a dev could look into it
[Galaxy S II Android Development] sien1996:
you tried SlimSaber 4.3.1 yet? I'm not really ready for KitKat too but 4.3.1 is just too stable. :D:good:

Well whatever choice you make, hope you will still eventually come back to SlimKat/Saber by [MENTION=1228651]fusionjack[/MENTION]. :good::good:

Cheers
[Galaxy S II Android Development] AlexVat:
It's not a ROM problem. Please stop giving advices if you are not sure or you don't know what the problem is. You're not helping. This is a development thread and not the Q&A section. The battery gauge isn't synched. That's why the wrong readings. It happens after flashing ROM's or kernels. If he's using Dori's kernel he will find the reset battery gauge button in STweaks. It's a known problem and was also present on SGS1. So no problem with either the ROM or the kernel. Please follow the rules, use the search button and all questions will be answered. Cheers everyone and have a great weekend!
[Galaxy S II Android Development] fusionjack:
if you set your screen security to 'slide' you can drag it. otherwise you need first to unlock your phone.
[Galaxy S II Android Development] HardCorePawn:
Probably not... I've looked into this before... and WhatsApp is bypassing the Android notification system and playing it's "notification" sounds directly... You'd need to set the whole audio subsystem to silent to prevent this...

BT changed a HUGE amount... Google moved from BlueZ bluetooth stack, to Bluedroid...

This broke a metric **** ton of stuff... like the whole AVRCP stuff (artist/track titles being shown on BT devices etc)... some of it has been fixed... some of it is still broken... the carkit related stuff is a generic KitKat issue... it doesn't work well for some carkits... the common issue being that contacts aren't read/transferred correctly... I suspect this is related to extra contact fields not working well with some units, as some users have reported that some contacts transfer, but not others...

No... it is just the "Fuel Gauge" chip freaking out during a freeze/reboot... if you leave it for a while (unplugged)... you'd probably notice the battery increase from 6% back upwards! Magic recharge ;)... or it would just stay at 6% for hours and hours... it is a common and well known i9100 "defect"...

as for the decrease from 100% to 97% during reboot... the charger subsystem is actually managed by the kernel... it is not a separate embedded system... even in "offline" charging mode (ie. turn device off, plug it in) it actually starts up the kernel (and a version of recovery and ADB) to manage the screen, charging animation etc etc... there are portions of the reboot where the kernel is still loading etc, and the charger is not actually active, but the CPU is running... Additionally, during startup the CPU can be running at full speed, with the screen at full brightness/power etc... which might be enough to drain power, faster than the recharge can replace it... :silly:
[Galaxy S II Android Development] fusionjack:
you don't need to go to gps settings since by long press gps tile you can change the gps mode: wifi only, gps only, wifi+gps.

by normal pressing you enable or disable gps.
[Galaxy S II Android Development] Harsha Raj:
[MENTION=1228651]fusionjack[/MENTION] looking forward for long press home button on lock screen for turning on the torch :thumbup:
[Galaxy S II Android Development] fusionjack:
that is just an illusion. :D

it is the battery gauge acting weird if shutdown is not normal. if you wait until the system is cooling down, you'll experience another illusion that your battery is charging by itself. so all just illusions....:D

just charge your phone again. :)
[Galaxy S II Android Development] Georgel25:
I understand...sorry for that :( so this means that every time after a rom/kernel flash we must reset the fuel gauge, or only in case it starts to go crazy ? :p
[Galaxy S II Android Development] Harsha Raj:
Also I think to stop this illusion, following steps:

1. Plug the phone to the charger

2. Restart the phone. That way the fuel gauge won't act weired :p

Whenever I'm travelling I try my level best not to restart lol.
[Galaxy S II Android Development] fusionjack:
remember me to take a look into the logcat. i'm away from my pc right now.
[Galaxy S II Android Development] pdario:
It seems. How do you enable that?

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

Ok, I have "path" security option (well, it's "sequenza" in Italian, not sure about English for it), so my only option is to use xposed? Can't that be added to the ROM?
[Galaxy S II Android Development] AlexVat:
You don't have to do it after each flash. Only when it's misbehaving. After you reset it, leave it alone for a couple of hours, without plugging the charger. It will charge up until it reaches its true value ;)
[Galaxy S II Android Development] pdario:
Is there anything I can do to "reset" it when I need?

Can this harm the battery? I mean, if it think the battery is @ 6%, it will charge it at full current, but this may be harmful if the battery is in facts near 100%... Or not?
[Galaxy S II Android Development] fusionjack:
if you are using security beside 'slide', it is intended that you cannot drag the notification drawer because it is security breach since you can access many important information like sms and start any apps from there without supplying password, pin or gesture that you are already set.

so if you want to drag notif drawer in lockscreen, you need to use 'slide'.
[Galaxy S II Android Development] pdario:
I'm not sure what you mean here...

When I receive an SMS and the screen is locked, I can see it in the notification area, drag down the area, read ad slide it away without unlocking.

I if tap "reply", I have to unlock the phone.

That's fine with me and not particularly different from having SMS readable on a lock-screen widget, no?
[Galaxy S II Android Development] essi:
Hi, found this

http://forum.cyanogenmod.com/topic/...ll-prior-cm-versions/page__st__20#entry436998

In this thread they had exactly the same problems like me with my BMW. May be someone can have a look at it
[Galaxy S II Android Development] Harsha Raj:
1. "Screen is locked" you mean with a pin or pattern or password?

2. If answer to the above question is yes, then you cannot drag the notification bar in lock screen. It's an Android security feature. If the notification bar was draggable then there is no point in setting the security for the lock screen. This feature was put by Google in Android JB and forward.

3. If at all you can drag the notification bar down, then people can indeed read the SMS, or IM's because it's content is visible in notification bar too. So having notification bar draggable when the lock screen is secure is pointless.

4. If you want this feature, I don't know if xposed does this. This feature will no way be made available in SlimSaber or any ROMs for that matter, because of security reasons. You can enquire in xposed thread if any xposed module exists to make this feature available for you.
[Galaxy S II Android Development] pdario:
As I wrote, I'm using an xposed module to let me drag the notification bar when I have my screen pattern-locked.

It is ok for me if someone reads an SMS, the important thing to me is he cannot use the phone, I don't see this as making security pointless...

Anyway, I understood it is pointless asking here! ;)

I'll keep on with the xposed module.
[Galaxy S II Android Development] Rachid.Ala:
For all who want to reboot their devices without the battery gauge issue

If you want to reboot your device, reboot first to recovery then reboot to system :D
[Galaxy S II Android Development] AlexVat:
It doesn't always work. Sometimes when you reboot to recovery you can see the battery percent is already changed. But let's stop this OT and get back On Topic. They already got enough help :)
[Galaxy S II Android Development] pdario:
I don't understand why sometime the mobile and wifi network tiles turn orange/brown in the notification area, even with mobile data off. What's the logic?
[Galaxy S II Android Development] pSyCh¤_O_O:
Grabbed from first Google search from androidpolice:

"Now that the status bar icons are white, it could be confusing to figure out whether you're connected to Google services or not. In Jelly Bean this distinction was easy: gray icons mean no connection, holo blue and you're set. In KitKat, your icons are always white, but if you're not hooked up to Google services, the icon will be orange in the quick settings panel."

So orange basically means not connected