yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 6.4 (& md5) >>

http://slimroms.net/

Features:

HeadsUp: Correctly add and remove the window

QuiteHours: Extra daily times

Major frameworks/base updates aosp caf

Major frameworks/av updates aosp caf

Major frameworks/native updates aosp caf

Update to recovery (TWRP)

display-caf-new updates

audio-caf updates

media-caf-new updates

libhardware updates caf

libhardware_legacy updates caf

frameworks_opt_telephony updates

hardware/ril updates using CM's caf for qcril "without msim"

Update Nova Launcher to version 3.0.2

More Translations

galaxys2-common updates

add netflix hack

media_codecs: Don't try to use absent VP8 decoder

Enable use of FFMPEG codecs for extended formats

fix front cam video recording

Exynos camera fixes

camera: add video snap param and set to "false"

Fix sdcard mounting

recovery.rc cleanup, fstab cleanup

Repo cleanup/fixes

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] badblood_antony:
Kinda irritating now...the in call picture zooms out...tried all the options...its started from the 4.4.3 version...its not the full screen feature for sure..nor is it the expanded desktop...
[AT&T Samsung Galaxy S II SGH-I777] david72262:
Wondering if anyone else is having problems with media scanner on this build acting up and draing battery. Restored previous build and all is fine again.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 6.6 (& md5) >>

Features:

add remote view tile

do not block home button if incoming call is a background call

enable hex color picker for quicksettings styles

Settings: Make sure time-range summaries match

frameworks/base updates aosp caf

frameworks/av updates aosp caf

frameworks/native updates aosp caf

display-caf-new updates

media-caf-new updates

frameworks_opt_telephony updates

packages_services_Telephony

Update to recovery (TWRP)

more translations

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] david72262:
Thanks this build is back to running perfect again media scanner issue fixed
[AT&T Samsung Galaxy S II SGH-I777] mr-cook:
Slim-i777-4.4.4.build.6.7-UNOFFICIAL-20140723-0614.zip - 141.05 MB

Built with the SaberMod 4.8 toolchain.

Sent from my SGH-S959G
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 6.8 (& md5) >>

Features:

Settings: Show heads up at the bottom of the screen

SystemUI: show statusbar icon if quiet hours is active

SlimActions: add new actions

frameworks/base updates aosp caf

frameworks/av updates aosp caf

frameworks/native updates aosp caf

display-caf-new updates

media-caf-new updates

audio-caf updates

packages_services_Telephony

vendor/slim updates

Update to recovery (TWRP)

more translations

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] snipe2nite:
Awesome job dude keeping the i777 alive!!! A couple questions, 1. I haven't flashed anything on the i777 for awhile, running slimbean 4.2.2 with AJ's kernel. Looking at the installation process I don't see anything special if coming from jellybean do I need to flash a KK kernel first then install or will just flashing the ROM with a JB kernel (recovery) work? 2. What kernel is included with the ROM? 3. Awesome job switching to TWRP, I'll guess going back to my nandroid if I ever wanted to or had issues I would need to flash the old CWM kernel to restore it any known issues with that? Thanks again for your work!

EDIT: I tried to thumbs up your post, XDA app said "Post Thanks Deny" NM I see it posted now

Sent from my Nexus 5 Pimpin AOSPA 4+
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
When coming from any pre-KK firmware, you will need to use a kernel with either CWM 6.0.4.4+, or TWRP 2.6.3.0+.

The suggested route is to flash a KK kernel, reboot to recovery, then flash the firmware.

Slim Team's own KK kernel uses TWRP 2.7.0.1 (included in the firmware), which can be found separately in the i777 slimkat download repository

Edit: added pre-4.4 installation info. to OP. 2014/07/31

Any issues swithing back to CWM? I don't think so, both CWM and TWRP seem to work well with i777-KK. Going back to JB is the same process; flash a JB kernel, reboot to recovery, then flash the JB firmware.
[AT&T Samsung Galaxy S II SGH-I777] snipe2nite:
Thanks for the info my dude!! Really appreciate your dedication and attention to detail!!!

Sent from my Nexus 7 Pimpin AOSPA 4+
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Stable build 7.0 (& md5) >>

Features:

**will update when formally published

http://slimroms.net/

Changelog: (same as I9100)[/QUOTE]
[AT&T Samsung Galaxy S II SGH-I777] mr-cook:
New build. Built with SaberMod toolchain. Added color and transparency settings for Slim Recent.

http://www.androidfilehost.com/?fid=23610159112651987

Sent from my SGH-S959G
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
This ROM is working great the battery life is amazing. Thanks for bring us new toys. :thumbup:
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
...The 7.2 build crashed last night. It has already been reported and addressed. I'll re-sync and build again tonight.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 7.2.1 (& md5) >>

Features:

InCallUI: fix blue call button background on some devices

SlimIRC update

Slimrecents: background color && transparency

frameworks/base updates aosp caf

frameworks/av updates aosp caf

display-caf-new updates

display-caf-new updates

external_chromium_org_third_party_openssl updates

more translations

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 7.4 (& md5) >>

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Thanks Cyril it is my daily driver ROM because it is very fast and stable I set the DPI in 240 with textdroider and it looks great. I have a question which is the different between slimsaber slimkat and this rom?
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I'm glad you're enjoying it. Stability, speed, and the less-is-more approach, are what I find most appealing about the firmware. My Wife runs Slim as the DD on her i777, I DD SlimSaber.

FusionJack has made a few changes, and added a few picks to the firmware, but these are the main sabermod differences (as listed in the slimsaber OP):
[AT&T Samsung Galaxy S II SGH-I777] badblood_antony:
Is the caller screen picture zoom issue fixed in the latest release...
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Can you provide screenshots of the desired behavior? as well as the name of the firmware that they are generated from?
[AT&T Samsung Galaxy S II SGH-I777] badblood_antony:
Sure...first screen shot is what i set as contact pic...

Second is what happens when i make a call...

Running ur latest 7.4 release
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I did see that example in your prior post about the issue. So in other firmwares the photo does not zoom in during a call? It is exactly the same as the contact photo?
[AT&T Samsung Galaxy S II SGH-I777] desteele:
My contact pics have always done that, regardless of the ROM I was running.
[AT&T Samsung Galaxy S II SGH-I777] badblood_antony:
It all started with slim kat 4.4.2 and above. and as i checked it on other forums too all roms developed from slim kat sources have this issue.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
What I need to know is what firmwares DON'T have this issue.
[AT&T Samsung Galaxy S II SGH-I777] badblood_antony:
Not sure about it...cant even try other roms now...using this device at work...but it was working till 4.4.2 slim kat..

Sent from my SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 7.6 (& md5) >>

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] rirozizo:
does this build include slimIRC app?

Sent from my Nexus 4
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Slim IRC was pulled from unofficial builds, although the option still appears in the menu

settings > slimcenter > slimIRC

Installing the "Android IRC for SlimRoms" apk (from a backup, or extracted from other firmware) is an option, and makes the menu link fully functional. Support is NOT guaranteed, since this device is not officially supported, and even the i9100 DM is MIA.
[AT&T Samsung Galaxy S II SGH-I777] rirozizo:
thanks for the info.. I'm hunting down those unofficial ones that still have the app, because... well... you know we don't support unofficial builds, and as IRC support it's my job to hunt these things :D

Sent from my Nexus 4
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 7.8 (& md5) >>

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] david72262:
Thank you. This has been my DD for some time now runs smooth without issue.
[AT&T Samsung Galaxy S II SGH-I777] david72262:
Is there a way to decrypt your phone once you in crypt it? I thought I would try it out a few days ago and it sure created problems when I went to do the last update. I do not really want to have to wipe my data

Well I search for hours in hours and nothing worked so I will end up just wiping data. I guess it was time for a totally clean install anyway
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
https://www.youtube.com/watch?v=0qbhTmVs5tA

snipped from: https://plus.google.com/106433967005195000488/posts/jDrFwpTWqNs
[AT&T Samsung Galaxy S II SGH-I777] razen_kain:
what EVER! I had no idea you could do all that. And what's this chamber of secrets? How have i missed this one???

Sent from my SGH-S959G
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Chamber of Secrets

-- Chamber of Secrets [video] --
[AT&T Samsung Galaxy S II SGH-I777] david72262:
Only took an hour to find it lol
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 7.9 (& md5) >>

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] david72262:
Congrats [MENTION=5294352]cyril279[/MENTION] on your new recognized contributor status
[AT&T Samsung Galaxy S II SGH-I777] 4-2ndtwin:
^

+1

Congrats [MENTION=5294352]cyril279[/MENTION] !

Well earned and deserved !
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
The update improved the sensitivity of the screen, improved the performance of the battery, and all the applications run without any problem, with 240 dpi looks great. No issues found in this ROM. Thanks for this great project.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Input requested

I'm thinking about providing stock slim, but built with a different toolchain (the same or similar to what mr.cook was providing).

What is the benefit? unedited slim firmware, that will run better on our devices.

If I choose this route, the current slim builds will be replaced with the non-stock toolchain builds.

I'd like some feedback on whether folks are:

Interested

Indifferent

opposed | bad idea because...

-OR- if mr.cook's builds magically re-appear, then we get the best of both worlds :D
[AT&T Samsung Galaxy S II SGH-I777] razen_kain:
Interested.

But i thought that's slimkat was already...?

Sent from my SGH-S959G
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I don't think so, but I still have a rather loose grasp of the toolchain scenario, so if you know better then please straighten me out!

I know that stock slim is built on a 4.8 13.06 linaro toolchain from one year ago, and I'm fairly certain that fusionjack and [MENTION=5554845]rogersb11[/MENTION] have setups that are more current & more specific to the i777.
[AT&T Samsung Galaxy S II SGH-I777] mr-cook:
I know I've been super busy here lately. I will try to get a fresh sync here soon to run a new build. I have a few different toolchains, if you need anything.

Razen the slim kernel is already built with linaro. So I haven't changed that. I built the ROM with SaberMod, and left the kernel with linaro.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
It's a good time to sync, the builds were notched to 8.0 yesterday evening. Officials are having Jenkins issues, but ours builds fine.
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
I'd just go for it man, these are your builds, make them your own and however you want them. They'll be awesome and if you need any help with anything just let me know. I uploaded the linaro I use in the kernel. Custom build, patches already done and specific to cortex-a9 for this device. Believe my SM is optimized for the device as well even tho it's slightly older it's still 4.8. Been experimenting with 4.10
[AT&T Samsung Galaxy S II SGH-I777] TheGeekyNimrod:
I agree with [MENTION=5554845]rogersb11[/MENTION] .... These are builds that YOU make. Do them how you want to. Build plainly like I do or tweak the hell out of it like master rogers over there.

People will appreciate whatever it is you do.

:thumbup:

Sent from my SAMSUNG-SGH-I747
[AT&T Samsung Galaxy S II SGH-I777] david72262:
You just keep doing what you want this has been the best ROM for this phone since Mr cooks
[AT&T Samsung Galaxy S II SGH-I777] mr-cook:
My new build resulted in the sdcards not mounting. This also happened on a previous build a couple weeks ago. So I cleared it all out including ccache , and am starting clean. New build is going to take a while.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
[MENTION=5315289]TheGeekyNimrod[/MENTION], [MENTION=5554845]rogersb11[/MENTION],

Regarding my intitial question of what calls the toolchain variable that is sometimes defined in the boardconfig.mk, I finally found what I was looking for.

Using Carbon's github as an example;

https://github.com/CarbonDev/android_build/blob/kk/envsetup.sh#L155

envsetup.sh (of the android_build project) shows us that the build process for an arm device (our beloved S2) will use whatever toolchain files are located at

"arm/arm-linux-androideabi-$targetgccversion/bin"

https://github.com/CarbonDev/android_build/blob/kk/envsetup.sh#L146

a few lines earlier, "$targetgccversion" is instructed to use build variable

"TARGET_GCC_VERSION" from a linux-arm.mk file (also located in the build project).

https://github.com/CarbonDev/androi...454fc47a6a/core/combo/TARGET_linux-arm.mk#L37

The linux-arm.mk defines "TARGET_GCC_VERSION" as 4.7 unless "TARGET_GCC_VERSION_EXP" is defined in the device config.mk (where this all started)

^^So If I ammend the device config.mk to include

TARGET_GCC_VERSION_EXP := Q4CW

then the build sequence will look for the toolchain files at

"arm/arm-linux-androideabi-Q4CW/bin"

So when adding the toolchain project to the manifest, the path should match.

:feeling accomplished:
[AT&T Samsung Galaxy S II SGH-I777] TheGeekyNimrod:
Very well done sir! This now makes it pretty simple to use different toolchains if desired. I knew there had to be a few scripts that pointed around at each other, but I wasn't sure where it would be at.

Nice work!
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Awesome work. This is EXACTLY what i meant to show you. That's my bad for sure. Call log had me flustered and I've been so focused on that I completely for. I'm sorry but on the bright side I'm sure you learned more than just the toolchain path and call m=by digging around. Awesome job [MENTION=5294352]cyril279[/MENTION]
[AT&T Samsung Galaxy S II SGH-I777] TheGeekyNimrod:
At some point, I'll get the time to get around to thoroughly going through things and learning exactly what they do and why. Something I started out wanting to do, but have found myself without a lot of time to do so. That was definitely one of those things.
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
You ever had this error before? all of the sudden adding threads give me this crap

brett@brett-ET1331G:~/android/custom$ brunch i777 -j12

including vendor/cm/vendorsetup.sh

Invalid lunch combo: cm_i777--j12

and yes there is a space there
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I don't use brunch anymore, I've definitely never asked it to brunch threads... Doesn't brunch use "mka bacon?"

The variable that follows brunch defines the device, so it's trying to find an i777-j12 in the lunch list, which will definitely return "invalid lunch combo"
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
[MENTION=5554845]rogersb11[/MENTION],

lunch, as described in CM's envsetup.sh:

[ - lunch: lunch <product_name>-<build_variant> ]

so whether [ breakfast i777 -j12 | brunch i777 -j12 | lunch i777 -j12 ] the script is treating the "-j12" as a build variant of the i777.

I typically spec the number of threads after lunching, during make

[ make -j12 bacon ]

or they could be combined as

[ lunch cm_i777-userdbeug && make -j12 bacon ]

Unless building for AOSPAL or SlimSaber, who both use scripts, so the sync/lunch/make commands are combined, and look completely different.
[AT&T Samsung Galaxy S II SGH-I777] TheGeekyNimrod:
I had that with a ROM I am working with right now. LS is great for putting it within a bunch of scripts where I choose options and it does the rest. This new ROM I have to run envsetup.sh then "lunch full_i777-userdebug" or whatever build version. Then "make i777-userdebug j#" ... Completely different from what I'm used to at this point.

Sent from my SAMSUNG-SGH-I747
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
OK, I'll use the make bacon command BUT this is how ice l I've always done it. Just strange it always worked until few days ago. Thanks for the response. Build is entirely too slow if I don't add threads lol
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 8.2 (& md5) >>

Features:

Heads up color and transparency

Moved heads up to settings to Interface

New Bluetooth stack for caf branch

frameworks/base updates aosp caf

packages/apps/Settings updates aosp caf

libhardware updates

build updates

packages/apps/Camera2 updates

hardware_qcom_fm updates

frameworks/av updates aosp caf

frameworks/native updates

hardware_qcom_audio-caf updates

hardware_libhardware_legacy updates

system_core updates

hardware_qcom_display-caf-new updates

hardware_qcom_media-caf-new updates

hardware_samsung updates

apn updates

more translations

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 8.4 (& md5) >>

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 8.6.1 (& md5) >>

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
This ROM works like a charm, without any fuss
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
<< Weekly build 8.8 (& md5) >>

http://slimroms.net/

Changelog: (same as I9100)
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Throwing a toolchain into the manifest is one thing, but the flags matter, no?

how about these?:

TARGET_USE_O3 := true
STRICT_ALIASING := true
SUPPRES_UNUSED_WARNING := true
OPT_MEMORY := true

Do you have/use other specific flags? or are these default settings in your toolchain?
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Yea they matter. Watch for a pm and I'll just give you a copy of my make file. The flags are used by what you've shown here but which flags to actually use are defined in another location
[AT&T Samsung Galaxy S II SGH-I777] TheGeekyNimrod:
Is your make file and the SM you use in your github repo? I'll be hitting you up on G+ soon to discuss tweaking. Just gotta get through a few days first.

Sent from my SAMSUNG-SGH-I747
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Well yes and no. I have 3 actually at the current time. The one on shift github repo will do tho. It's completely stable
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
...they are defined in another location within the same makefile? or in a different file?
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Well see this is where it gets tricky man. Start with the same makefile. You actually can define flags in pretty much every single makefile but it's hard to determine what could be making your build wonky that way. Mine that I keep pushed are stable, I don't even push experimental stuff until I know it's going to work. Sorry, I've been packing and started moving today and have been swamped. I'm about done got the day and my net got hooked up already woot woot lol. I'll pull my makefile and highlight where the flags you want are and then you can basically just copy and paste it

Edit: This is actually good timing as I just messed with some flag type stuff the other day. Look closely at these 2 commits but mainly pay attention the the make file of course. You don't need to do the optimize alot stuff unless you want to as it can cause some build failures if the source isn't clean enought in certain places

https://github.com/rogersb11/Shift/commit/0c7af5dd0556fd49953244269913bdad2f8c07e9

https://github.com/rogersb11/Shift/commit/859cec419c4f78e9f9e9ce0eefcf6a56032000e4

also look here for defining a specific toolchain https://github.com/rogersb11/Shift/blob/master/Makefile#L196

and here for the flags themselves, follow it down a couple lines. You'll be able to tell

https://github.com/rogersb11/Shift/blob/master/Makefile#L372
[Android Q&A, Help & Troubleshooting] akshay tyagi:
guys its my first post here and am not a dev or any android tweeker i bought a micromax a27 rooted it but idk what came in my mind i installed dreamboltxv2 and after successfully installing it through cwm it just stucks at the BOLT logo....[Actually i forgot to wipe cache and reset ]

there another problem too ...as i have researched over past few days i found out vol up+power key gets my device into recovery but itsnot (at the time of successfully flashing CWM + when my device was fully working ) but i tell u it wont' it just goes onto screen like recovery but asking PCB check,sensor check and all that useless stuff [I think an INDIAN guy with a micromax a27 can only understand my problem ]

U guys wud be imagining me as a idiot ...like how do i know CWM is installed well i installed Rom Manager and used it to boot to CWM :{

Any help will be appreciated.....THANKS :D
[Android Q&A, Help & Troubleshooting] Hovatek:
just flash stock backup via SP flash tool
[Lenovo K900] sev7en:
Dear All,

finally, it's arrived in my working-place, Qatar. I have it and... it's a very great smartphone, just to start with a bright display and a great grip.

Full Technical Specs: http://www.gsmarena.com/lenovo_k900-5241.php

​

First of all some screens without and with a Sony Ultra Z (picture grabbed with my Z30):

​

The firmware onboard is the VIBEROM_V1.0_1403_7, Android 4.2.2 with hardware version H-3.01.

​

As starting point for the development of the v7KX9, I evaluated the performance of the K900 with the following tools:

​

Results are the average of a 3 times execution... I will pack a stand-alone archive with all the benchmark as well the utility for your toolkit:

Vellamo...

​

GFX Bench...

​

Antutu Benchmark...

​

CPU Prime Benchmark & MemBenchmark...

​

3DBenchmark...

​

GPS Benchmark...

​

BenchMarks Package with Lenovo Camera (23.05.2014) - 121.23Mb: https://drive.google.com/file/d/0B282FXce0kggel9pbFE2TkZjcmc/edit?usp=sharing

​

And pictures... the challenger is a BlackBerry Z30 with the official firmware 10.2.1:

Lenovo K900... VS BlackBerry Z30

​

Pictures in Native-Resolution are available over at here: http://www.sev7en.eu/Retrogaming/imgs/

:)
[Lenovo K900] dabdob:
Cool thread! What's the ROM or launcher on your phone? I'm talking about 3ed pic.
[Lenovo K900] sev7en:
Thank you, it is a screen-lock with the built-in ROM.
[Lenovo K900] alveox:
how weird you got k900 builtin on vibe rom out of the box...

CMIIW, but when you buys new k900 phone from store, it should have the original lenovo rom, not a vibe rom..
[Lenovo K900] sev7en:
I haven't get it from the official store, for that it has the Vibe ROM already. I specified built-in as I have no added new application to the flashed ROM, just that.
[Lenovo K900] alveox:
ow i see...

good luck on your Dev on this device..

btw do you have a link to JB 4.2.2 stock phone.apk, contact.apk and mms.apk that i can use on this k900?

i really hate using the lenovo contact manager.. until now i freeze it using titanium, im only defrost it if im gonna add new contact to my phone.

for daily use im using textra and exdialer, i cant find the stock one that work on this device.. :(