yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Hopper8:
Do you have the new hardware rebinding set to 'double tap' for anything? I mean, anything, even if you don't use it. IMHO the new rebinding is just a responsive, as long as you don't have any double tap features enabled. Otherwise the hardware keys are always waiting for the second tap before it does anything.
[Galaxy S II Android Development] paludi06:
Thanks for the tip :good: Now my S2 is flying ;)
[Galaxy S II Android Development] pdario:
For new Dialer and People apks should we wait for 4.4.3 or can they be ported to 4.4.2 earlier?
[Galaxy S II Android Development] fusionjack:
correct, i also notice the same if you set up 'double-tap' key binding. like [MENTION=4851213]Hopper8[/MENTION] mentioned, leave the 'double-tap' empty and the hardware key rebinding will responsive like usual.

not sure how big the changes...
[Galaxy S II Android Development] sien1996:
Nopes no double tap set here:p. Ok case scenario..... Open an app like whatsapp. Turn the screen off. Now wake the device.. Then press home button.... Well not all the time but sometimes it doesn't respond on first click but only on second... And if you set long press to a custom action for any key.... The normal tap won't work after screen on, only second tap will register it... :(. If I set this below. Turn screen off and on, press menu button, recents won't show on first click but only in second :p

Cheers :) I still liked 4.3.1 better though :D
[Galaxy S II Android Development] fusionjack:
yesterday, i have experimented with a new compiler flag that could optimize memory.

you won't probably notice the difference in rom performance, but the memory operations should be more efficient than before which could increase battery life. so far, i don't have any problems with this new flag...

another thing...i have changed slimsaber github account into an organization. this means if you followed slimsaber github before, you need to re-follow me (fusionjack github account) since an organization cannot be followed.
[Galaxy S II Android Development] Egyptiandroid:
Please anyone could help me asap!. My mobile cannot boot or get into recovery mode. it only get into download mode. When i try to switch on my mobile, it did not switch on, but when i plug the cable to computer, it shows empty battery sign only. So i cannot get it to boot or enter recovery mode to install new firmware. I tried many recovery via odin while my mobile is plugged into computer but i still cannot get it to work

I own samsung galaxy s2 with slimsaber on it. Anyone could help me please.
[Galaxy S II Android Development] clock51:
incall UI full screen

hello fusionjack, the build of 05/28 I liked the option incallUI full screen, you can have a zip to flash to get this, if you could you be so kind as to post. thanks for your time and for everything you do for us
[Galaxy S II Android Development] vrwmiaris1:
[MENTION=1228651]fusionjack[/MENTION] in call ui background it doesn't work with immersive mode, can you do something with this? Tnx

Στάλθηκε από το GT-I9100 μου χρησιμοποιώντας Tapatalk
[Galaxy S II Android Development] officiallyme:
[MENTION=1228651]fusionjack[/MENTION]: may i ask why you do not enable the BLN option in your stock kernel?
[Galaxy S II Android Development] Harsha Raj:
I tried this http://www.androidpolice.com/2014/0...-4-3-works-on-android-4-4-2-too-apk-download/

But it FC upon dialing or accessing the call history. It actually installed as separate phone app.
[Galaxy S II Android Development] waa2398:
So.... I installed the CWM given in the instructions and now im stuck at the Samsung logo. Any ideas? I was planing on upgrading from 4.1.2 official TW.
[Galaxy S II Android Development] la_malacoda:
you have to enter recovery, flash KK compatible recovery, reboot recovery (don't reboot phone, just hit reboot in recovery) and flash rom :good:
[Galaxy S II Android Development] m1trand1r:
Bwaaaahahaha-ha.....Read again bud.....2nd * ....

[emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji122][emoji122][emoji482][emoji482]

Oh.....you didn't need to help an ignorant bud above.....lol ...*SMH*

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] waa2398:
First of all, WTF is wrong with you "bud"? I didn't know the CWM was going to touch system. I wasn't prepare for installation just wanted to update CWM to be ready. Do not call people ignorant, you do not know the circumstances.
[Galaxy S II Android Development] fusionjack:
there is no bln, how should i enable it? :p

i need to check that later...eventually you could report this bug in slim forum.

@ all: btw, a new build is up with memory optimization flag
[Galaxy S II Android Development] la_malacoda:
Out of curiosity, I remember there was a rom with non intrusive incall ui. Does this rom have it? Thanks!

Sent from somewhere around the world
[Galaxy S II Android Development] vrwmiaris1:
I did m8, and since I'm using your build I thought is good to let you know that , Tnx dude

Στάλθηκε από το GT-I9100 μου χρησιμοποιώντας Tapatalk
[Galaxy S II Android Development] Hopper8:
Click the Odin link in my signature. In there you'll find step-by-step troubleshooting for your situation. Long story short, you need to flash a stock rom from download mode. If I were you, I'd be flashing the 3 part stock firmware which is linked in my thread. It will wipe your phone as it flashes, so gives the best chance of getting it back :)

Every single thing possible to recover it using Odin is covered in that guide, so make sure you try every thing, multiple times over if necessary. Good luck :)

Sent from a galaxy far, far away
[Galaxy S II Android Development] Plinky89:
To be honest I don't know what you truly did or where you messed up (no offence m8). Here a step by step guide to flash this rom from an empty phone. Just start at the point that you consider right (If you are confused start at point 1 and everything will be fine).

1 - Flash any Samsung stock 4.1.2 rom with Odin.

2 - Put this http://d-h.st/mEg in you external sd and flash it from stock recovery (when phone is shutted down, press vol up + power and select "apply update from external sd card". You have to navigate with volume bottons and select options with power botton). After that you will have Philz custom recovery without the annoying yellow triangle.

3 - Reboot phone and put the KitKat compatible recovery http://mirror21.downloadandroidrom.com/file/GalaxyS2/recovery/CWM-KitKatCompatible-i9100.zip in external sd card. Put the latest Slimsaber release + gapps on ext sd too http://d-h.st/users/fusionjack/?fld_id=26999#files ------ http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4

4 - Reboot in recovery and select "Wipe/Factory reset" ---> "Clean to install a new rom" --> Yes

4.a (optional) - Mounts and Storage ---> format "emmc" to have the internal sd card 100% clean (do not do this if you placed all the zips in the internal sd because you don't have an external sd card in your phone!)

5 - Do not leave the recovery, flash zip from sd card, and select the CWM KitKat compatible recovery.

6 - When the installation is finished... Power Option ---> Reboot Recovery.

7 - Now you'll be in the KitKat compatible recovery ready to flash the rom.... so... (navigate with volume and select with power) install first the zip of the ROM and after the GApps (I use slim_minimal gapps).

8 - reboot and enjoy Slimsaber with a 100% correct install and bugless process. :fingers-crossed:

PS: before you ask, after you are done with the flashings, use this app to change the UI size https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi. 240 DPI is samsung's stock, but you can play with it until you find your sweet spot.
[Galaxy S II Android Development] bodzik155:
Files are still 0 bytes on newest ROM ;/.
[Galaxy S II Android Development] dinos3:
I have this problem, now im on Samsung base ROM...
[Galaxy S II Android Development] m1trand1r:
You didn't know because you don't wanna read "bud".....if you would read....I wouldn't have to reply to your crying post lol.....oh...what's wrong with me?.....Ask yourself and maybe you'll figure out[emoji23][emoji23][emoji23][emoji23]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] officiallyme:
???

there is a kernel patch that enables BLN. all the custom kernels use it. without issues.
[Galaxy S II Android Development] vizdak:
no move to sdcard option

after full wipe and flash 0603 with minimal gapps 5.6 the move to sdcard option is gone. i'm on dori v112.
[Galaxy S II Android Development] fusionjack:
stock kernel is not a custom kernel.

grrr...this because of the new feature 'move to ext sdcard'. this feature is still disabled for our device and it looks like it ends up completely disables the whole 'move apps'

sorry for that...i didn't notice this and i'll try to enable it.
[Galaxy S II Android Development] Vibsi:
I'm sorry, but I can find tons of posts in this very thread about issues with custom kernels. So how come you are claiming "without issues", who's to say the problems are not related to this BLN kernel patch?

Sometimes one has to just accept a "no". Fusionjack doesn't want to temper with the stock kernel and I'm glad about that.
[Galaxy S II Android Development] nutij3:
Someone can PM me setting for V10.43 v112 for battery saving, with screen too if possibile (not extreme) I'm in slimsaber kat last update if can help, ty for all that reply me!

For report about Kernel, no problem so far, have only 2 soft reboot One when the phon is plugged and One when unplugged (screen off), ty for all the work that make this Kernel the best!

P.s. sorry for my bad english :)

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Android Development] Hopper8:
I agree with the point of your post, in that stock kernel is stock, custom is custom. Don't mix the two. However, I will just say that I've been using bln for approximately a year and a half on S2 with no issues. I can say that Bln itself doesn't cause kernel issues :)

Wrong thread mate. You're in the ROM thread, not the kernel thread. Hint : find the dorimanx profiles thread by eskriminal for what you're after.

Sent from a galaxy far, far away
[Galaxy S II Android Development] nutij3:
Oh **** sorry for the wrong post, ****ing blindness xD ty for the answer mate :)

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Android Development] m1trand1r:
Lol.....mind your words please....this is xda not some pub...;)

Thanks ;)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] sien1996:
First set of **** could stand for "really".:p( need an extra star though) ;)
[Galaxy S II Android Development] j1gga84:
[MENTION=1228651]fusionjack[/MENTION]

next build of CM (Markox89) will (maybe) be built on 4.4.3, do you already see anything concerning 4.4.3 in Slim Github? :fingers-crossed:

Regards
[Galaxy S II Android Development] cyril279:
Thanks again, you had all the relevant device changes covered within an hour of forking the repository!

Speaking of pull-requests, I have submitted one for the slim_i777_defconfig.

the changes are tested -compiles and boots:
[Galaxy S II Android Development] fusionjack:
there is still no 4.4.3 merging-conflict commits on cm gerrit...

slim gerrit has already some commits to solve the merging-conflict...but i think it is not all of them.

updating android version is not easy as it sounds...it is not just change the tag version, but it needs also solving the merging-conflict.

in term of slimroms, there are basically two type of projects...projects that are directly used from aosp and projects that are based on aosp and modified. for the projects that are heavily modified, there will be too much conflicts while merging with the aosp one.

solving conflict needs an extra caution since we want to keep the existing features with additional changes from the new android version. hence the name merging...

i tried last night to merge two heavily modified projects (frameworks/base and frameworks/av) and there were a lot of conflicts. i'd rather wait slim team to merge them because slimsaber also has some modifications apart from slim official which will potentially cause conflict again.

so...there is a lot work to merge new android version. :D
[Galaxy S II Android Development] m1trand1r:
Mate....sometimes slower developement brings even more joy.....don't you feel the same?;)

Very well put [MENTION=1228651]fusionjack[/MENTION] .....take it easy....and again....Kudos to you man....[emoji482][emoji481][emoji106]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] j1gga84:
Of course I feel the same, it was a simple question, just for information, nothing more, nothing less ;)

[MENTION=1228651]fusionjack[/MENTION]

Are this important information for "us":

http://www.xda-developers.com/android/browse-every-new-aosp-code-commit-in-android-4-4-3/

? ;)

regards
[Galaxy S II Android Development] fusionjack:
SlimSaber-i9100-4.4.2-20140603.zip

Changes:

Using memory optimization flag. Credit to AOSPAL

SlimRecents: Option to show topmost task

Options can be found in settings accessibility

Launcher3: Hotword: More ding-dong fixes

App2SD: Moving applications to an external volume

Due this feature is still disabled on our device, moving app is now completely impossible. Don't use this build if you really need to move apps.

See changelog for the rest of changes
[Galaxy S II Android Development] pdario:
What happens if you have apps already moved?
[Galaxy S II Android Development] fusionjack:
yeah, i saw that last night...i won't cherry-pick them one by one especially the chromium changes...:D

good question...i think i don't have any apps that are moved to sdcard. so i'd say, just try it...:angel:
[Galaxy S II Android Development] mkl1959:
They disappear, but you can get them back installing previous version of the ROM.

Enviado desde mi GT-I9100 mediante Tapatalk
[Galaxy S II Android Development] LukaszBobrek:
I can tell you exactly what will happen - those apps will be gone ;) You can restore them via TiBu, but only on internal menory.

BTW. I really need apps on SD... And i don't want to lose all incredible feature that will come in future, so is it possible that moving apps to SD will be availible back one day?

Wysłane z mojego GT-N7000 przy użyciu Tapatalka
[Galaxy S II Android Development] pdario:
+1 of course
[Galaxy S II Android Development] clock51:
or restore them with Titanium Backup
[Galaxy S II Android Development] officiallyme:
i know :)

but the kernel patch enabling BLN is applicable to the stock kernel. unfortunately i cannot find the source, but I remember someone posting a patch.

so there is no "just enabling" BLN but i assume you patch the kernel anyway, do you not?
[Galaxy S II Android Development] vrwmiaris1:
Latest build is a true dynamite, i don't mind about sd issue!

Στάλθηκε από το GT-I9100 μου χρησιμοποιώντας Tapatalk
[Galaxy S II Android Development] Spaulding89:
[MENTION=3763274]rkoby13[/MENTION] so far as i know it's only for ext SDCards. So only apps from internal storage will run.

---------- Post added at 09:24 PM ---------- Previous post was at 09:22 PM ----------

Btw.newest build is really awesome great,fast,stable. No hot reboot or so. Thanks [MENTION=1228651]fusionjack[/MENTION] for your really hard work to build the perfect Rom.
[Galaxy S II Android Development] mentzik:
Hi FusionJack,

I see a new build 04-06-2014 in the downloads. Should we update to this one or 03-06-2014?
[Galaxy S II Android Development] fusionjack:
better use todays build since moving app is working again.

upps...did i mention a new build? [emoji14]
[Galaxy S II Android Development] fusionjack:
[MENTION=3763274]rkoby13[/MENTION] with yesterday build it is not possible to move apps. use today's build...:)
[Galaxy S II Android Development] clock51:
Great ... I fusionjack credit card blocked, when I can give to you
[Galaxy S II Android Development] Nico_60:
Sorry for the OT... :rolleyes:

fusionjack, could you have a look at my PM...

Thank you ;)
[Galaxy S II Android Development] fubo73:
Some apps disappeared as they were on sd (don't ask me why, if I move them to internal partition they do not work anymore). With 0604 all seems ok! Great!
[Galaxy S II Android Development] m1trand1r:
Thanks a zillion mate, I can't really thank you enough for all that you're doing for US here.....so....i'll d/l 04/06 tomorrow morning at work....do some changes ....flash ahoy....[emoji106][emoji106][emoji106][emoji106]

Keep it up and take care;)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] clock51:
flashing build 06/04 back "move to sd" all ok. thanks fusionjack
[Galaxy S II Android Development] mentzik:
OK flashed latest! Seems very fast! I had to reflash latest GAPPS thought cause I have Text to Speech service stopping.

After re flashing GAPPS everything is OK.

Thank again Fusionjack. You are the best!
[Galaxy S II Android Development] Flegias:
I dirty flashed the 06/04 over the 06/03 but after reboot I had the phone stuck on the bootanunation.

Then I repeated the flash but with same result! Luckily I have stored the previous version and I flashed it. The phone booted even if with many pop-up of Android media crash.

What do to suggest to do? And why I had that issue ? Regards

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Android Development] LukaszBobrek:
That might be a "cliche", but it is probably time for clean install ;) if you dont want to lose your data simply use Titanium Backup.

Wysłane z mojego GT-N7000 przy użyciu Tapatalka
[Galaxy S II Android Development] Gamer015:
what should be the first thing to do if in some weird instances, all apps FCs suddenly? any help would be useful. thanks! ?

Sent from my GT-I9100
[Galaxy S II Android Development] Twiq:
Reboot and observe? If it happens again fetch a logcat and post it here

Running 0522 Sabered SlimKat | DorimanX 10.43v111
[Galaxy S II Android Development] Gamer015:
will take note of that. thanks!

the last time it happened, I rebooted for about four to six times but keeps happening until I decided to full wipe. the worst part is I didn't updated my TBackups before that unfortunate disaster, so *bam!*, that's the worse thing happened. so as much as possible, if there's other way round aside from full wipe, that would be great. ??

Sent from my GT-I9100
[Galaxy S II Android Development] ratvim:
Always do dalvik and cache wipe after dirty flashing new rom..it will keep ur setting and other app as it is.
[Galaxy S II Android Development] sien1996:
Haha happened here before... So nowadays I'm all super cautious when flashing ROMs and like have a checklist of things to do before flashing :p.

You should maybe start a checklist too ;)

Try clearing cache and dalvik cache and see if it persists :)
[Galaxy S II Android Development] Gamer015:
I always do it the other way around(clearing cache and dalvik before flashing). is it the same really?

yeah, maybe I should start making the same too. haha! ?

Sent from my GT-I9100
[Galaxy S II Android Development] Hopper8:
[MENTION=5456260]Gamer015[/MENTION], reboot recovery and fix permissions. That has a chance of working. I'm not sure it will though. I can't remember if stock kernel/recovery has this option? If not, you may need to reboot recovery, mount USB storage, sideload a new kernel (e.g. dorimanx). Reboot recovery from inside recovery (recovery-ception? :p) and then fix permissions from Dori recovery. ONLY do that if your current recovery doesn't have the option to fix permissions.

Speaking of checklists, that seems like a very good idea. For a full wipe, here is mine:

1. Back up all user apps in Titanium Backup. Don't backup system apps. If using Titanium backup pro, it's possible to create an 'update.zip' of all user apps to flash. To make the update.zip of all user apps: Menu>batch actions>create update.zip. If you don't select batch action, it will only create a flashable zip of Titanium Backup app.

2. Backup systems settings in MyBackup Root. New Backup>Data>Local>System Settings. This will back up your ROM settings (quick tiles, framework animations, everything). Thanks to [MENTION=3763274]rkoby13[/MENTION] for this tip, a long long time ago ;)

3a. Reboot Recovery

3b. Nandroid backup

4. Wipe data, format system, wipe cache, wipe dalvik.

5. Flash ROM, Gapps, any addons (I use ad-blocker)

6. Reboot to ROM

7. Sign in to Google account

8. Reboot Recovery, flash update.zip of Titanium apps, OR don't reboot to recovery and restore while in the app

9. Restore data from MyBackup Root of system settings.

Done! Full wipe flash done in less than 15 minutes :D

Or, for dirty flash:

1. Backup user apps with Titanium backup (just in case)

2a. Reboot recovery

2b. Nandroid backup

3. Wipe cache & dalvik cache

4. Flash ROM

5. Flash addons (for me, ad-blocking)

6. Reboot to system

Done! Less than 5 minutes :)

For me, I always use my full wipe procedure. The extra 10 minutes is worth it, I find that a build installed with a full wipe always out-performs a build which has been dirty flashed.

I hope this helps a few of you, I've seen a few questions on what to wipe/"can I do this" etc (even though general instructions are in OP ;) )
[Galaxy S II Android Development] Gamer015:
that MyBackup Root is new to me, so I'll take note of that. and I'm always on Dori kernel so that's helpful. ?

and I use ad blocking app too(I don't know if it's safe to say here), and I notice that's it's not usually affected when I clear dalvik and cache, so that's good I guess. thanks for the useful tips, I really appreciate it. ?

Sent from my GT-I9100
[Galaxy S II Android Development] sien1996:
Haha cool checklist. Remember to turn WIFI off to stop the incoming messages during backups haha :p.

And I heard someone or can't remember if it was Dori himself that said fixing permissions is bad on KitKat.... Correct me if I'm wrong though :)
[Galaxy S II Android Development] Hopper8:
Turning wifi off?? Never heard of that one, but sure :) and then that is news to me about fixing permissions.... Maybe worth checking it out though. Thanks for the tip :)
[Galaxy S II Android Development] sien1996:
Haha naah man just to prevent further important whatsapp messages before flashing :p. I could be wrong though ;)

Cheers :D
[Galaxy S II Android Development] Harsha Raj:
[MENTION=4851213]Hopper8[/MENTION] is it necessary to reboot to ROM and then sign in to Google account and then reboot to recovery to flash the update.zip?

Also my only problem with full wipe was that I had to setup my system settings again. Gonna try Mybackup Root.
[Galaxy S II Android Development] Hopper8:
Yes unfortunately it is, if you don't sign into your google account the update.zip doesn't flash properly. I'm not sure why, but that's the way it has to be done :silly: And yep, that's a lifesaver for me. I hate having to redo the settings. I went from a full wipe taking me about 40 minutes to sub-15 minute full wipe flashes :D
[Galaxy S II Android Development] j1gga84:
[MENTION=4851213]Hopper8[/MENTION]

Thanks for your explanation concerning backup and full wipe. I think this is important for those who have problems after dirty flashing.

What I want to know: when I create this update.zip can I choose weather I want to backup user data or only the apps?

Because everybody tells me that it is better not to restore (system) settings.

Edit: I think it is time for a full flash for me. I had a soft reboot after exiting tapatalk, yesterday after quitting whatsapp. Is that a known problem or what could be the problem?

Regards

Sent from my GT-I9100 using german Tapatalk 4