yashsingh1/xdaforums huggingface dataset:
[Nexus S Q&A, Help & Troubleshooting] g.sembhi:
I think the air kernel is more stable.
[Nexus S Q&A, Help & Troubleshooting] chalan30:
wow thats the first time ive heard that lol. if its so stable then why does he have to issue so many "fixes" and "patches" or whatever to get stuff to work right? Matr1x works right the first time. matr1x is way, WAY more proven, and in the general consensus also more stable.
[Nexus S Q&A, Help & Troubleshooting] tthaz777:
CM9 kernel is good enough.:D
[Nexus S Q&A, Help & Troubleshooting] Skunk Ape1:
Matr1x....

_______________

Just Flash It !!!
[Nexus S Q&A, Help & Troubleshooting] b1337:
turn up your hearing aid or try new batteries wow...and an incorrect statement lol
[Nexus S Q&A, Help & Troubleshooting] bord1er:
Matr1x is the best I was just asking
[Nexus S Q&A, Help & Troubleshooting] b1337:
if you knew that(not so correct statement)then why did u ask?
[Nexus S Q&A, Help & Troubleshooting] chalan30:
youre an idiot
[Nexus S Q&A, Help & Troubleshooting] b1337:
and you're a nub, you and others are saying that an UV kernel is more stable than one that is not...who is the idiot again?
[Nexus S Q&A, Help & Troubleshooting] chalan30:
read the threads. and see which ones more stable. and you just made yourself look like even more of an idiot

http://xdaforums.com/search.php?searchid=23400828

---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------

you just have to type in the word "fix" in a search to see all the things that are jacked up with air
[Nexus S Q&A, Help & Troubleshooting] b1337:
each phone is different and handles voltages and OC different so for you or anyone to say one kernel for a rom is better than another is completely idiotic, the best kernel for cm9 is the cm9 kernel unless u need performance in a certain area, thats where custom kernels can be better, reading the threads would tell you this so look who is the idiot now nub...

air kernel gets updated more than matrix so you really have no argument there...
[Nexus S Q&A, Help & Troubleshooting] chalan30:
air kernel gets updated more bc of all of the "fixes" and the develper's work is mostly copied from the work of other more talented people. and the OP here asked a question and we answered. your right that each phone is different. but i didnt see you take issue with the person who said that air kernel is more stable, or that cm9 kernel is good enough. they both also stated their opinions without the caveat which we all should know already, that each phone is different and the kernel that is best for one person is not necessarily best for another and that it really depends on your usage and customization preferences we should all know that by now. the OP just asked which was better and I think Matr1x is better. so now what
[Nexus S Q&A, Help & Troubleshooting] b1337:
i think pete's is better what what in the butt
[Nexus S Q&A, Help & Troubleshooting] chalan30:
lol
[Nexus S Q&A, Help & Troubleshooting] b1337:
:p but really i am impressed with cm9 kernel, its pretty fast and battery friendly and with DI on its pretty friggin stable...matrix, air, thalomus, ink and trinity are all nice variety is the spice of life!
[Nexus S Q&A, Help & Troubleshooting] bord1er:
I was asking if it would be stable on that rom
[Nexus S Q&A, Help & Troubleshooting] chronophase1:
Im using stock. Or in other words, what came with the rom. Matr1x UV values don't like my phone and neither did Air. Lol. But ymmv.
[Nexus S Q&A, Help & Troubleshooting] b1337:
Nandroid, flash, observe....that's how you do it
[Nexus S Q&A, Help & Troubleshooting] g.sembhi:
air kernel has two builds; stable and weekly.
[Android Apps and Games] fongwe:
Android Bluetooth Control Device:)

Android Bluetooth Control Device Application is to allow you to control various electrical devices up to eight devices and independently controlled.

Use Android Bluetooth mobile device to remote control your device with Bluetooth Receiver hardware Device.

The program features.

- control up to 8 devices.

- Can be set Timer to ON / OFF the device and show the time.(the timer can be set to 1 minute, 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours).

- Use with Receiving device (Bluetooth Receiver Hardware more detail in website below).

Design for the Android version 4 and a screen resolution of 480 x 800 (WVGA).

Freeware with AD (free software)

More info about hardware :

http://microcontrollerkits.blogspot.com/2012/02/arduino-control-8-devices-via-android.html

More info about Apps : :)

http://androidcontrol.blogspot.com/2012/02/android-bluetooth-control-8-devices.html:)

Google Play Market:)

https://play.google.com/store/apps/details?id=com.app.control
[Android Apps and Games] D4rKn3sSyS:
I have developed something similar some time ago, however It was connected to computer. It's basic function was get temperature from a LM35 sensor through PWM inputs from Arduino, and then fetching them with android device, so any phone that sent a message with "STATE" code to my phone, would receive temperature measured by sensor.

Great app!. I like that you dont need a computer :D

ps. Thanks for the schematics and arduino code. Really useful for future implementations!
[Android Apps and Games] fongwe:
For Hardware and Aduino code :)

Pls.link to

http://microcontrollerkits.blogspot.com/2012/02/arduino-control-8-devices-via-android.html
[Android Apps and Games] fongwe:
This Program has wakelock function so your Android device wake up all the time. :)
[Android Apps and Games] fongwe:
Now upgrade.
[Kindle Fire General] nogloww:
It's been about 4 or 5 months since I flashed CM7 on my Kindle Fire and I am having some problems with it rebooting spontaneously (at least I haven't noticed any patterns) and some slight lag in my launcher loading apps in files and sometimes even uninstalling apps (GOex Launcher). I am wondering if anyone else has had this problem, mainly with rebooting randomly on CM7, or if I did something wrong when flashing it?

Also, if there's been a newer release of CM for the Kindle that I overlooked or missed, that could also explain the problem as well, I think...

Any thoughts, comments, or experiences would be helpful. Thanks.
[Kindle Fire General] nogloww:
Also, I've noticed a bit more posts than a few months ago about CM9 for KF. Has anyone had the experience of comparing the two? Is one more stable now than the other? I was told (at the time I flashed) that CM7 was more stable but am wondering if that's still the case. If you've used both or particularly had a great experience with one over the other, I'd like to hear what you think.
[Kindle Fire General] tipzilla:
I am currently running AOKP Build 35 by OxD34D, and it is probably the best ROM I have every run on any of my Android devices. Everything is super solid, virtually no bugs. I say this, however, my experience with CM7 is limited on this device. I would say from the forums it would seem that CM7 and CM9 are very similar as far as stability goes. A lot of the thanks goes to the kernel devs who have made great strides in getting this device to where it is now. So make sure to give them some thanks for their works as well.
[Kindle Fire General] HaiKaiDo:
PS: This is great development you have here. *points you to the general section*
[Kindle Fire General] abundantmussel:
I would recommend updating your FireFireFire bootloader and recovery and then trying Hashcodes CM9 ROM.

FireFireFire 1.4a:

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

ClockworkMod Recovery 5.5.0.4:

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

Hashcodes CM9 ROM:

http://xdaforums.com/showthread.php?t=1591850
[Kindle Fire General] ChicagoGOBLUE:
I'm running gedeROM (I think that's how its spelled) CM9 and its friggin amazing. Blows CM7 out of the water, IMO.
[Kindle Fire General] brizey:
I think the general consensus is that the CM9 based ROMs are better than the CM7 ROMs at this point. They are not perfect, but neither was CM7, which don't forget, is really a phone OS, not a tablet OS. The launchers are better and I think the app support is better as well.
[Kindle Fire General] JustROLLIN:
But still no hi-def video correct? I have been out of the loop lately, so please correct me if I am wrong. I know its petty, but I use my KF for a lot of video viewing and it was important to me at the time I loaded CM7.
[Kindle Fire General] sthomas38:
Yes it has HWA ;).
[Kindle Fire General] Aesrys:
HWA works for any ICS based ROM (CM9 or AOKP) as long as it has the 3.x kernel, which I think pretty much all of them do now. While there are still some random issues (looks like more app-centric (HBO Go and Hulu+ especially)), it tends to work well for most folks with Netflix and YouTube HD. It does seem to help if you do a full clean on your device (factory reset, both caches, system) before switching ROMs.
[Kindle Fire General] nogloww:
I'm not sure if you were being sarcastic or what exactly your reply meant (inflection is hard to hear within text) so sorry if you think I posted this question in the wrong forum but I thought the development from CM7 to CM9 would be best discussed by developers. It looks like I'm not the only one, but if you feel that strongly about it, I'll keep it mind next time. Thanks for your opinion.
[Kindle Fire General] veeman:
Try gedeROM. It's ice cream sandwich.
[Kindle Fire General] HaiKaiDo:
Yep the development section is for actual development and releases of roms, kernels etc. Wasnt trying to be a ****, just tired of people posting discussion threads in the development forums. The Developers also read the general section. Its not my opinion, its a forum rule.
[Kindle Fire General] BananaFusion:
Actually you can get Hulu+ to work with the latest kernel. Search the forums for Hulu, and someone made a modified version that bypasses the device not supported screen. I even have swype working on it too. At this point there's no reason not to use ICS.
[Kindle Fire General] BluesHawk:
HBO Go was recently updated to support android 4.0 so it's working great for me on my KF :)
[Kindle Fire General] Aesrys:
Figured someone would get them working.
[Kindle Fire General] thea mohamed-toorn:
smirkit zip

I have the gedeROM from 13-05-2012 installed and

did the update FireFireFire 1.4a and TWRP 2.1.1 with the smirkit zip

that's easy and you don't need de computer you can do it on your kindle.

---------- Post added at 10:15 PM ---------- Previous post was at 10:06 PM ----------

I think the gedeROM is the best at the moment.

but don't forget shut down in recovery or push the power button for 10 sec. before the battery is dead.

with all the rom's with kernel 3.0
[Motorola Photon 4G] perrotype3:
I was rooted but restore back to stock with rsd lite now both my laptop or desktop wont read the phone

Any ideas?
[Motorola Photon 4G] rsjc741:
did you download the motorola x64 or 32-bit drivers?

you need the sunfire drivers for your phone (in fast boot, etc) to work right with rsdlite
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/

Maybe someone who is a little more savvy in this field could take a look?

Here is a very good article and discussion about the issue:

http://xdaforums.com/showthread.php?t=1644364
[T-Mobile Samsung Galaxy S II SGH-T989] shankar10:
this is kinda scary but so far I never had any problem
[T-Mobile Samsung Galaxy S II SGH-T989] _ice_:
We don't even have any kernel source. There is a leaked kernel but that didn't cause any brick in our devices. Also note that the article does not mention sgh t989 or sgh 727 and all its sub variants. If this was the case for us you would see many more "[Q] plz halp I haz brick " threads
[T-Mobile Samsung Galaxy S II SGH-T989] kahm:
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:

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

For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.

Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.

There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.

Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.

The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone :)

TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
Finally someone with a brain! Thanks for the post :)
[T-Mobile Samsung Galaxy S II SGH-T989] Spartan 363:
Scary stuff indeed, has anyone confirmed that our devices (T989) is affected by this bug?
[T-Mobile Samsung Galaxy S II SGH-T989] Xhyperion:
Back on the original Epic we used Odin to get the next version. I think it was 2.1 to 2.2 roms. I've always wondered how safe it was to revert to GB by flashing after installing ICS
[T-Mobile Samsung Galaxy S II SGH-T989] mharmon:
[Q] plz halp I haz brick

Disregard. Funny how you figure out your issue just seconds after you post and open yourself up to ridicule.

DOH!
[T-Mobile Samsung Galaxy S II SGH-T989] Micronads:
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
[T-Mobile Samsung Galaxy S II SGH-T989] mharmon:
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
[T-Mobile Samsung Galaxy S II SGH-T989] Micronads:
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
[T-Mobile Samsung Galaxy S II SGH-T989] xcrazydx:
Yeah sounds dead to me. Send in for warranty. Oh well, stuff happens. Good luck to you!
[T-Mobile Samsung Galaxy S II SGH-T989] Karakoram2:
Id rather risk bricking than rock without 4.04
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
Nobody has said it is necessary applicable to this device.
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
You're right, it doesn't say it's applicable to our device. But it also doesn't say our device is one of the safe GS2 variants. As you can see in my signature, I'm also using 4.0.4. And if you read my post history, I recommend it to everyone. I'm just saying that it hasn't been proven safe yet, but there's also no proof its dangerous either.
[T-Mobile Samsung Galaxy S II SGH-T989] markusf21:
ICS has been flashed to these phones probably a half million times by now. If it was causing bricks we would have heard about it.

Sent from the iPhone graveyard.
[T-Mobile Samsung Galaxy S II SGH-T989] kahm:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
[T-Mobile Samsung Galaxy S II SGH-T989] jose makalolot:
Also, people should know that the listed phones in the OP are Exynos based and T989, i727/r and i717 are Qualcomm based. This has been discussed in the skyrocket forums and some devs have explained that.

Just my 2 cents.
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
The brick in this thread was due to flashing an i777 rom to a t989. Flashing an i777 rom to t989 regardless of OS will brick your phone.
[T-Mobile Samsung Galaxy S II SGH-T989] xcrazydx:
It seems to be all exynos based, but thanks for the heads up, man.
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
Yeah that seems to be the case. I'm curious as to what it was that was causing it that's different from ours..
[T-Mobile Samsung Galaxy S II SGH-T989] xcrazydx:
From the brief reading I did, It seems like the Note had a problem with an ICS kernel and using the wipe functions of a custom recovery.
[T-Mobile Samsung Galaxy S II SGH-T989] kahm:
Not at all what I was talking about:

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

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

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

http://xdaforums.com/showthread.php?t=1358401&page=2

Every single one of these threads has someone in it that has memory related issues (corruption, file disappearing, or straight up bricking), and none of them flashed the wrong rom. This is just the past months' worth, I don't feel like going back any further. As someone who came from a device that was absolutely RIDDEN with bricking issues (the Sprint Epic Touch 4g), I've done the research and can tell you this seems JUST like the stuff people see when dealing with this same issue.

I don't get it, why are people getting so damn defensive about this? Brick your devices, I guess I don't really care, we're just trying to help. It's something worth thinking about.
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
Those are all related to either known issues or GB roms?

Non Touch recovery has been known to cause bootloops but bootloops are not bricks.
[T-Mobile Samsung Galaxy S II SGH-T989] kahm:
okay, point taken, but again, theres literally no harm in knowing things, and it's a pretty safe thing for this issue to be looked into instead of written off.
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
TDJ seemed to have looked into why the touch recovery was causing bootloops so it hasnt been written off but it hasnt panned out as bricking devices. These possible brick issues where the reason why some devs where careful at first but now all devs seem to be working with ICS bases so the looking into has happened. However currently it seems the amount of bricks is equivalent for ICS as GB (The amount of GB bricks on your posts make it seem like GB might even have an edge).
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
Had to thank you for the post, glad to see people agreeing on stuff. That's kind of why I made this thread, so everyone can be on the same page as to where our device stands in the ICS brick "scare".
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
I also sent a PM to the guy who found this issue to ask him about the t989/i727. This is what he said:

So far, it seems not. You might want to try an experiment:

Find out the manufacturer ID of your eMMC chip:

cat /sys/class/block/mmcblk0/device/name

If it's MAG4FA, VYL00M, or KYL00M, then follow the instructions in the thread below for identifying your fwrev:

http://xdaforums.com/showthread.php?t=1644364&page=1
[T-Mobile Samsung Galaxy S II SGH-T989] kahm:
So, my phone has the firmware revision "0x25". If you follow the instructions there, you can see that this firmware has a KERNEL level fix going on, but thats only for ICS kernels:

So, I'm not sure what devices and what firmwares everyone is running, but if what I'm reading is correct, there are scenarios in both firmwares that could potentially cause a brick. Regardless of firmware, there are EMMC firmware bugs in these chips across multiple firmwares. This is why I feel the need to have some extra caution, and perhaps this is why there seems to be more GB related bricks rather than ICS related bricks for our devices; the 'fix' that samsung issued for the 0x25 firmwares was recently checked in, meaning its in the ICS kernels.

Based on this info, I think I'm going to wait until the next ICS leak specific to our device before I erase anything in any recovery. Obviously, that's just me though.
[T-Mobile Samsung Galaxy S II SGH-T989] AJ26T:
Mine says KYLOOM so should I be worried and I checked out that thread but still not understanding what I need to do if anything
[Motorola Atrix 2] Apex:
Okay gang,

I recently fried my Atrix 2's system partition somehow, and it wouldn't load passed the "M" Motorola boot logo. But, after some patience and step-by-stepping through how to use AP Fastboot to install a 2.3.5. script, its now working again.

The question is this: In my haste felt from being without a phone for a few days, and in thinking that the phone was just completely jacked, I filed a claim with AT&T to get a "new" replacement phone.

The phone came today, but along with that came the solution to fic the original back to stock. Now, I have (2) Atrix 2's and the original SIM card from the first is still active, and with the 2nd Atrix 2 came a new SIM card -not activated.

So, can I (or should I) keep both phones and use the first as my rooted "test" phone, whilst keeping the second as an unadulterated "back-up" phone?

I don't want to cheat the system here, but was thinking it mightb be worth the deductible from my AT&T insurance to keep both so as to get more fluent with ROMS, flashing, etc all while having a completely stock 'back up'.

I was thinking of activating the 2nd (fresh) SIM card that came with the new phone and swapping between the two handsets as necessary.

Any thoughts/suggestions/warnings/insight?

As always, thanks in advance for your responses...
[Motorola Atrix 2] deBricker:
Yes., because you can switch phones and keep your SIM... I do it all the time when I switch between my Captivate and my Galaxy Nexus when I was with AT&T.
[Motorola Atrix 2] Apex:
So, in my paranoid mind, there's no issue between the handset and the SIM card communicating with the service provider letting them know that I have two handsets running off one SIM card at any given time?

I don't want to run the risk of (firstly, and most importantly) insurance fraud, and second having any issues with warranty/service agreement mumbo-jumbo!

I figured this would work, since the Atrix 2 doesn't have Carrier IQ to divulge any of mine or my phone's information, just wanted to be absolutely sure!
[Motorola Atrix 2] matt99017d:
With your claim simply say that the phone was lost. And after you got your new phone someone returned it too you....can't be insurance fruad if someone returned a lost phone....can it?