yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
k, understood... the fact that a commit would show up in 9100 changelog, but not in 777's on bbqdroid made me suspicious that we aren't getting all the good stuff ;)
[AT&T Samsung Galaxy S II SGH-I777] brendonlee:
Depends on your location. For me (Charlotte, NC) KJ4 works best.
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
The automatic brightness levels are borked... Or more likely, they just havent been touched yet =(

And in response to the apn.. Its as location dependant as the modem. So you wont find one single apn that works the best. Try them all out, there is an app on the "play store" to manage apns.

Nightly 30 running significantly cooler than 29, i hope to see improved battery life from this.

in regards the the modem question. The modem thread has a map of which users are using which modems where.

Also is anyone else having problems with the xda app. I cant post anything...
[AT&T Samsung Galaxy S II SGH-I777] dandrumheller:
I haven't been on CM9 yet - but in CM7 there were settings to customize autobrightness levels to your liking...might want to look around... I apologize if these settings don't exist in CM9...
[AT&T Samsung Galaxy S II SGH-I777] CyberpunkDad:
All I did was go back into GPS Test app and clear and re-download the AGPS state/info.
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
Yea i modified them to my liking already but i think i have to redo them each flash, though i could be wrong. Either way its just another thing on a long list

Edit: i can post now through the xda app... If you get here from the dev thread link, it wont work. If you go through general section then it works =)
[AT&T Samsung Galaxy S II SGH-I777] wookiefoot:
Significant Change in battery life

FYI -

Updated from update-cm-9-20120329-NIGHTLY-i777 to update-cm-9-20120330-NIGHTLY-i777 this morning.

I'm getting a 10% drop in battery on standby each hour.

I ran update-cm-9-20120326-NIGHTLY-i777 for 33 hours with light use on one charge.

Could be just me but I wanted to share.

-- wookiefoot
[AT&T Samsung Galaxy S II SGH-I777] NJGSII:
ok.

You got any data to back up what you're saying? It's hard to see where you're battery drain is coming from without any info.
[AT&T Samsung Galaxy S II SGH-I777] leadman1415:
anyone know what modem works best in California?...specifically central California?
[AT&T Samsung Galaxy S II SGH-I777] breeves002:
Can you get CPU spy and see if your CPU is going into deep sleep? Also get better battery stats and check on wake locks/what app may be keeping your CPU on. Upload photos after running them for a few hours.
[AT&T Samsung Galaxy S II SGH-I777] wookiefoot:
Thanks for the suggestions on tools to help diagnose. I'll grab them and do some diagnostics.
[AT&T Samsung Galaxy S II SGH-I777] kennonk:
Im in cencal and tend to get the best results with KK6.
[AT&T Samsung Galaxy S II SGH-I777] naturefreak85:
So I just had the Wi-Fi issue and actually can't turn it off or back on, so I pulled the logfile through log collector, not sure if it has the actual reason for the WiFi not working

http://pastebin.com/atEL2mjM
[AT&T Samsung Galaxy S II SGH-I777] breeves002:
I was just messing with the brightness and the settings seem to work fine.

I do have two problems with it though:

1) the sample rate is too long. I notice that I pull my phone out of my pocket after I walk out into the sun it takes at least 5 seconds before the brightness goes up. Of course I can wait, but its just slightly annoying.

2) the buttons light settings don't work right. I'm not even sure if the buttons are supposed to dim, but they don't. They will only turn on and off if brightness ie changed before phone screen is turned on. I set buttons to turn off in bright light. If I'm using the phone in a dim area and then go to a bright area, the screen will brighten, but the buttons will stay on. Also the other way around. Its really not something that matters or is a big problem, its just something I noticed.
[AT&T Samsung Galaxy S II SGH-I777] yahoowizard:
Quick question: How do I know which bootloader I'm running? I'm trying to learn this stuff, and can't find the information on this. I posted this about 10 pages back, but I think it just got buried x.x
[AT&T Samsung Galaxy S II SGH-I777] Pseud0logik:
Unless you flashed different ones using ODIN then you're probably on stock GB BLs.
[AT&T Samsung Galaxy S II SGH-I777] kennonk:
Maybe my experience is an anomaly, but I flashed from Phonebricker v2 to CM9-mar26 then later no-wipe upgraded to CM9-mar29th nightly without any issues. Aside from known cm9 bugs I didnt have any problems pre or post install. Then this morning I nandroid backuped and full-wipe flashed to Shostock v2 RC5 and it is running fine too. If there is some kind of weird load order or bootloader issue I haven't experienced it yet flashing back and forth almost daily for the past week. Just lucky?

Do you guys format /system /data /cache and dalavik from CWM between new roms?
[AT&T Samsung Galaxy S II SGH-I777] breeves002:
Anytime. CPU spy is free in market, but better battery stats can be found free somewhere in xda. Search on Google, I don't have a link though.

Depending how much you use your phone, deep sleep state will change, but should usually be above 50%. Some peoples are as high as 90%.

If you go to other in better battery stats it will show you awake vs screen on. If the time awake is high, go to partial wake locks and the item at the top will be the process thats keeping the phone from going into deep sleep.

---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------

Between different roms, yes. I have used a different bootloader as well and had no problems. Between nightlies I only wipe dalvik and cache. I hear some people can come from akop to cm9 without wiping data.
[AT&T Samsung Galaxy S II SGH-I777] corruptsoul:
This has probably been addressed already, but is anyone else having an issue with the YouTube app not loading?
[AT&T Samsung Galaxy S II SGH-I777] AndAllThingsWillEnd:
It's working for me...
[AT&T Samsung Galaxy S II SGH-I777] Ashhong:
I don't think the sensors for the buttons are working right now. Nor do I believe they dim with the backlight even on official ROMs. The backlight is however currently dimmed when compared to Gingerbread.
[AT&T Samsung Galaxy S II SGH-I777] thracemerin:
Except for the very limited number of files that aren't common between the 2 devices, most things that are merged to android_device_samsung_galaxys2 should also be built into the I777.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Yup. Some things must be manually applied to both trees - mainly, those that are actually I777-specific.

Look at the I777 device tree and you'll notice that it is EXTREMELY sparse compared to the galaxys2 tree.

Changes to the core .mk files (especially BoardConfig) must me made individually.

In the case of the commit linked above, it was solely against a library that exists only in the galaxys2 tree (we use it, but we use it from that tree directly).

If you look through the commit history - 75% of the commits to the i777 tree just touch BoardConfig, 20% or so just touch extract-files related stuff, and the remaining 5% are changes to other makefiles.

As to bbqdroid... There simply is no clean way to have an accurate device-specific changelog. As it is we have a TON of non-device-specific commits show up in the logs because they're in "core" repos.
[AT&T Samsung Galaxy S II SGH-I777] murlyn444:
I'm getting this issue as well. Has anyone found a fix? I'm currently on RC2.
[AT&T Samsung Galaxy S II SGH-I777] REOGrand:
I found the easiest way for me to do it is. Download everything you need on your micro sd card. Then reload it back on your phone from that. You should still have CWM. After you get it loaded on your micro card put the batt back in and it should show the samsung s II logo again. Hold the buttons to get into CMW. Flash from the micro card and your set. Works for me every time. I hate a bunch of crap left on my phone from other roms. The only problem with this is you have to also flash a i777 rom first or you will get system error. I use unnamed.
[AT&T Samsung Galaxy S II SGH-I777] forzaazzurri:
Thanks for the information. Just to clarify a little bit more information. Which specific buttons do you hold down to get into CMW? And when I get back into CMW you said I have to flash a i777 rom first. Can I just flash the i777 version of CM9 RC2?
[AT&T Samsung Galaxy S II SGH-I777] Fierceguitar:
I'm getting something weird, hopefully someone can help me out.

After my last flash, I'm getting a strange thing where Rom Manager only shows CM7 nightlies and features. I've done a full factory reset and am still having this issue.

Any ideas?
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
None of you should be using Rom Manager in the first place as its proven it will soft brick your phone left and right.
[AT&T Samsung Galaxy S II SGH-I777] Fierceguitar:
I've merely been using it to download the file, not to flash it.

Any ideas?
[AT&T Samsung Galaxy S II SGH-I777] ricktherick:
Meh...there are better ways imo to download the nightlies. I just use my browser to go directly to get.cm/?device=i777 or I get them on my computer (it d/l faster for me). Since GB/CM7 I've been disappointed with the downloads on Rom Manager, so I don't use it for downloads. In fact I don't really use Rom Manager much at all.

....and yeah, +1 on softbrick w/ Rom Manager. Ever since that happened to me a few months back, I just reboot recovery to flash anything. I know Rom Manager fixed those bugs, there's just no reason for me to use it to flash.
[AT&T Samsung Galaxy S II SGH-I777] mikeflash:
I'm on 7/22, i went to sleep with 95% battery and woke up 7 hours later with 93%. And Wi-Fi on. This is great.
[AT&T Samsung Galaxy S II SGH-I777] cchiapusio:
vol-up and vol-down if i'm not mistaken.

Chip
[AT&T Samsung Galaxy S II SGH-I777] kleinschmizzy:
Impressive... Are you using the stock kernel or something else?
[AT&T Samsung Galaxy S II SGH-I777] willmayah:
Is anyone getting stuck at the Samsung screen after flashing 7/23? I did the usual wipe cache/dalvik and installed the newest nightly in CWM. I do not use Rom Manager. I can't even get into CWM using the buttons at power up. Does anyone have any suggestions for how I can get back to an earlier backup? Thanks!

---------- Post added at 03:21 PM ---------- Previous post was at 03:12 PM ----------

Update: I was able to boot into CWM. As for 7/23 is anyone else having issues?
[AT&T Samsung Galaxy S II SGH-I777] sir_dwtc:
I flashed 7/23 this morning. It booted normally and seems to be fine.
[AT&T Samsung Galaxy S II SGH-I777] kleinschmizzy:
Doesn't look like there were any changes merged in 7/23. I flashed 7/22 earlier today and it booted right up and hasn't presented any issues thus far.
[AT&T Samsung Galaxy S II SGH-I777] cchiapusio:
no problems with 7/23 today.

Chip
[AT&T Samsung Galaxy S II SGH-I777] ou812bkewl:
CM10 preview is out for I9100 with working audio. It's only a matter of time now. :D

http://xdaforums.com/showthread.php?p=29280423
[AT&T Samsung Galaxy S II SGH-I777] billyjed:
Only a matter of time for us! C'mon Entropy!
[AT&T Samsung Galaxy S II SGH-I777] djmurphix:
+1
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
OMG I cant wait!! Hopefully we get ours tomorrow :)
[AT&T Samsung Galaxy S II SGH-I777] billyjed:
On G+ Entropy said he has a busy week. It may be a couple of days. Thanks in advance!
[AT&T Samsung Galaxy S II SGH-I777] ThierryXN:
Entropy's G+ post: https://plus.google.com/101093310520661581786/posts/3fmeQRE9rK1

(Originally spotted in the task/ktoonsez AOKP thread: http://xdaforums.com/showpost.php?p=29283510&postcount=19792)
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Quoted from another thread:

"There is a tree already for i777. Codeworkx pushed it.

https://github.com/teamhacksung/andr...tree/jellybean

Now it's just a matter of compiling it and testing."
[AT&T Samsung Galaxy S II SGH-I777] mikeflash:
Stock cm kernel and cle5 modem. I haven't charged my phone yet and there's 61% left after 24 hours with Wi-Fi on (and in range 24/7), here are the screenies. But tbh, today I gave my phone very light usage, though what I'm most impressed about is that there aren't any apps or processes killing my battery.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
codeworkx's tree is untested - it keeps derping. Looks like I'll have to temporarily rip out NFC.

It's 1:35 AM, I'm about to go to bed regardless of whether it builds or not.
[AT&T Samsung Galaxy S II SGH-I777] kleinschmizzy:
Prior to flashing 7/22 I would see considerable battery drain over night which could definitely be attributed to wake locks. I have since cleaned up some apps and froze some others. Between that and this latest nightly I'm seeing about a 3-4% drop over an 8 hour period when not using the phone which is exponentially better than going to bed and waking up at 60% or less after a full charge.
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Entropy512,

I am not sure if there is any "JB" (source drop from Samsung yet) kernel that is required for "JB" ROM, and guess I9100 "JB" preview has been released on latest 3.0.36 but may be with many changes, but I strongly believe you would carry forward wifi changes to new tree, especially "wifi unicast" change that saves tremendous amount of battery IMHO, thanks as always.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
We're using the same source tree for kernel we've been using for months with very minor changes. The changes can be seen in the teamhacksung smdkc4210 kernel repo.

For most devices, JB requires very little kernel work - it's frameworks and HALs that are a pain, esp. the graphics subsystem.

BTW, hwcomposer is kinda flaky, as a result, there won't be any "butter" for a while.
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
Screw butter, I can deal with cream for the time being!! Overtime that cream will get spun into butter. I'm itching to install JELLYBEAN! Thanks for all your hard work!
[AT&T Samsung Galaxy S II SGH-I777] switters1:
I've noticed that immediately after turning on the screen I cannot unlock for a few seconds because the screen is unresponsive. Anybody else have this issue?

Running 7/22 nightly.
[AT&T Samsung Galaxy S II SGH-I777] mgd76:
I hope this is fun for you, Entropy, it sure is for us. As fun as a SGS3? Almost!!! Hopefully you at least get a "jolt" when you "crack a code?"

+1, except the itchy part... no rush, it's all good...
[AT&T Samsung Galaxy S II SGH-I777] jthatch12:
Haha no rush, I just miss flashing stuff
[AT&T Samsung Galaxy S II SGH-I777] mgd76:
Two words... cm9 nightlies
[AT&T Samsung Galaxy S II SGH-I777] slayaman22232:
Hey guys, I'm having trouble installing the latest nightly. I've downloaded it twice already so I don't think its a download errror. But idk. I've attached a pic of the error.
[AT&T Samsung Galaxy S II SGH-I777] billyjed:
Did you mean to download the i777 rom? Your sig says i9100. If you have an i777 edit your build.prop to change all the i9100's to i777.
[AT&T Samsung Galaxy S II SGH-I777] KevinChaos:
Assert error. You need to remove it from the updater script, or flash an I777 rom before you flash cm9. Are you currently on cm9 nightlies? If so, that'd a weird error to get.

Edit: didn't notice the signature. That might be the problem.
[AT&T Samsung Galaxy S II SGH-I777] slayaman22232:
Ya I thought that might be the problem and yes I do have the i777 I'll tell you if it worked.

Edit: it worked thnx alot
[AT&T Samsung Galaxy S II SGH-I777] killman2659:
What do you mean by removing from updater script? I'm coming from AOKP, was getting these errors, tried flashing a different rom (shostock) and it worked fine. With CM9 it is doing this for me also. All my build are i777. Any ideas?
[AT&T Samsung Galaxy S II SGH-I777] killman2659:
Never mind.
[AT&T Samsung Galaxy S II SGH-I777] scidon37:
Not much joy in flashing those either right now... no changes.

Edit: Spoke too soon. There is one change today, and some translations.
[AT&T Samsung Galaxy S II SGH-I777] djmurphix:
I have a question(yes I have searched myself on google, but would be more likely to get feedback from users in here better.) Now my question is, is it a bug or Rom related issue when you plug in your head phones and instead of muting the external speaker I still get sound coming out from speaker. I only ask cuz I bought some decent earphones and at work I wanna be "sneaky" texting n listening to music... thanks!
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
im going to flame you for flame sake... why dont you google it n00b.

k now that thats over. it cropped up recently and has alarmed ... or rather perked our attention. it happened after the open source HAL and "work around" was introduced. it has been mentioned but not addressed, im sure it wont receive a ton of attention as minds are startnig to shift to JB. if you roll back to RC1 maybe... look at the change logs for an open source hal. bbqlog and review.cyanogenmod.com are your two tools.

if you want to know more about the HAL google, or search this or the JB thread sticked in general.... there are a few explanations by me.
[AT&T Samsung Galaxy S II SGH-I777] djmurphix:
A$$ O
[AT&T Samsung Galaxy S II SGH-I777] jcomana:
I felt this way several times. In the forum someone suggest me to previously install a Rom which help to install stock bootloader for I777. It's suggest Cruelees Rom and later install CM9. Was the only way to solved this problem. It's works for me.

Sure, you have to working with all the standard procedure. Wipes and flash every time.
[AT&T Samsung Galaxy S II SGH-I777] forzaazzurri:
Okay, still trying to recover from my big mistake. So far this is what I've done.

I ran the below which is [Heimdall][Odin][Stock][Root]UCKH7/KK6 Return/Unbrick to Stock (or Root) and it succeeded.

http://xdaforums.com/showthread.php?t=1286432

I tried to install the CWM from the dev forum but it still links to megaupload which is now gone. I did a search and found the wiki article on CyanogenMod for the i777 and followed those instructions. Ended up at some point with a i9100 boot screen and yellow triangle. So I reran the above. Installed the Entropy GB DD Kernel. Booted to CWM with a UCKH7 i777 modem on my sd card and the clean kernel script. Ran the clean kernel and installed the modem and rebooted and I still have the darn i9100 boot screen. Tried to install the latest nightly and am getting the prop build error in the post above.

How do I get rid of the i9100 boot screen? Which specific kernel/modem/steps do I need to take? And looking above I guess I now need to install a different ROM after I fix that to install CM9.

One day I'll get this phone back up and running. Thanks in advance for all help, I truly appreciate it.
[AT&T Samsung Galaxy S II SGH-I777] AetaCapella:
I can not solve your big problem, but i can tell you this. The i1900 boot screen is a "feature" of the Samsung phones. Until you can reset the flash counter (using a jig or the triangle away app) it will persist. It doesn't in any way interfere with the operation of the phone (or inoperation, as it may be) it's just Samsung's way of telling if your phone has been tampered with for warranty purposes.
[AT&T Samsung Galaxy S II SGH-I777] Biporch:
@Forzaa, use the triangle away app.

And guys, it's so easy to get rid of the 7 error.

The most time consuming one is downloading a ROM like ucle5, uckh7, etc.

You could simply edit the updater script located in the meta inf/Google/android and remove the first lines that mention our phone model.
[AT&T Samsung Galaxy S II SGH-I777] mcala:
The most easiest way to get rid of the build prop error 7 message is to wipe data, cache, dalvik & here we go: Mounts>>>Format System>>>>BINGO>>>> no more error because you just wiped the build prop!! Now hopefully the flasher is flashing the correct ROM for the correct phone!;) Flashing stock roms/Odin not necessary :)
[AT&T Samsung Galaxy S II SGH-I777] Biporch:
Nope.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
That boot screen has nothing to do with the flash counter at all and resetting it will not magically change it back to the i777 one.

He has that because he flashed the wrong ROM plain and simple.
[AT&T Samsung Galaxy S II SGH-I777] forzaazzurri:
Appreciate the responses so far. So, to get my phone back to a normal state and fix the i9100 issue which ROM, etc. do I need to run. The frustrating part is I got into this state by following instructions on the CyanogenMod wiki for the i777. As I mentioned I've tried the kernel clean, reflashing with the the [Heimdall][Odin][Stock][Root]UCKH7/KK6 Return/Unbrick to Stock (or Root) which fixes the boot screen but as soon as I flash Entropy's DD it goes back to the i9100.

Do I need to flash a different ROM like Biporch said first and then CM9 daily to get around the build prop issue? And then run the triangle away apk? Or are there additional/different steps I need to take to fix this?
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
You should really keep your facts straight before saying stuff like that
[AT&T Samsung Galaxy S II SGH-I777] JmPTaz09:
i9100 and yellow triangle on boot screen is not an issue, I've had that since the day I rooted my i777 8 months ago and have flashed 50 roms since. Not sure why you are worried about that. For the build prop issue, just flash one of tasks aokp rooms and that will set it back to i777 in build prop and u can then flash cm9, etc. I do this all the time as I go back and forth between cm9 and Hellraised i9100 aosp roms. You will still have the i9100 boot screen but it's not a problem. Additionally, when flashing tasks rom to change build prop, u don't even have to set up or wipe data, etc. (If coming from an aosp rom). I just flash and the hit reboot from within recovery, but once the boot screen comes up and before it boots, hold the recovery combo to boot back into recovery and you'll be good to go; cm9 will install.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Enlighten me then. I'm curious how resetting the flash counter will replace the i9100 boot screen with the ATT one..
[AT&T Samsung Galaxy S II SGH-I777] thracemerin:
It won't, the splash image is part of the initial ramdisk that loads from the bootloader.
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Because it isn't an i9100 boot screen (well it is but it was built into the phone by samsung). It shows that you flashed something like a kernel using odin.
[AT&T Samsung Galaxy S II SGH-I777] thracemerin:
Resetting the flash counter will get rid of the triangle, not change the splash screen.
[AT&T Samsung Galaxy S II SGH-I777] KevinChaos:
False. Let's just settle this guys. I've done it before. Resetting the flash counter will get rid of the triangle AND change the screen. It will say "Galaxy S II" instead of "Galaxy S II GT-i9100" it will never say i777, but it will change it.
[AT&T Samsung Galaxy S II SGH-I777] Ostate24:
It does change it I've done it a million times!
[AT&T Samsung Galaxy S II SGH-I777] vs8:
I never had an issue with the triangle. I've flashed tons of ROMs and it works. I choose to ignore the triangle.
[AT&T Samsung Galaxy S II SGH-I777] elherr:
I really like triangles. Particularly isosceles.

Welcome to the triangle forum. Needs more cowbell.
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Oh don't be obtuse
[AT&T Samsung Galaxy S II SGH-I777] TheDude:
Kevin speaks the truth.