yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Twohothardware:
It just loads a set of diagnostic tests you can run on your device, mostly to test the screen, stylus, and speaker. Like the person above said it is good to test for dead/stuck pixels.
[Galaxy Note GT-N7000 General] knowsnophones:
Just tested it. Worked fine. Does this work on non-samsung devices?
[Eee Pad Transformer General] JoeJags:
http://www.androidauthority.com/ice-cream-sandwich-unofficial-port-lands-on-asus-transformer-34386/

Figured the link to this story would have been linked by now.....if it has, sorry.....didn't see it......
[Eee Pad Transformer General] dictionary:
The thread right beneath yours....
[Eee Pad Transformer General] JoeJags:
Sorry.....thought that was just a screenshot......this one had a working video......

sorry if it is a duplicate......
[Vibrant General] xriderx66:
I'm guessing that since the CM team has dropped support for us that Miui would also have dropped it for us since miui is using the base of CM?

Or is Miui still going to support us?
[Vibrant General] mohamobo:
Maybe yes maybe not. Lets see who out 1st. CM ICS or MIUI ICS.
[Vibrant General] xriderx66:
Its 100% going to be cm.

Miui has always from past used their base to start off with. I'll be surprised if miui is first though. I really would like a stable version of ics on this phone. It can handle it for sure, I tried the latest ics Rom we have
[Vibrant General] VeryCoolAlan:
I don't think MIUI is using CM as a base. AOSP built by them.

Anyways Atinm said that they'll see if they'll drop the Vibrant its not official yet.
[Vibrant General] mohamobo:
Then you should get ready to be suprised.. :D
[Vibrant General] xriderx66:
I can't say anything for something thats not released yet, but the miui we have now is using a base of cm.

How do I know? The exact same problems that cm7 faced during the beginning the same miui did and the further cm7 got the same happened to miui.
[Vibrant General] VeryCoolAlan:
Hmm ... they lied!

I think...eh
[Vibrant General] b1337:
Aosp based cm parts merged in, that's how it is
[Vibrant General] funeralthirst:
cm9 is not currently supported and may never officially be, but i feel very confident it will get ported to the vibrant. i imagine it will follow similarly to cm7 on the vibrant. while atinm said he's sick of the vibrant he did mention the possibility of a port.
[Vibrant General] Shortbus-Driver:
What you seem to be missing here...is the big picture.....its the vibrant that is dying.
[Vibrant General] mohamobo:
Dying for you but not for me :D
[Vibrant General] funeralthirst:
[No message]
[Vibrant General] xriderx66:
never seen that meme before... I wonder what it means
[Vibrant General] mohamobo:
huh :confused:

Move forward..
[Vibrant General] bfranklin1986:
I think this place has officially hit rock bottom
[Vibrant General] x-out:
i'm willing to bet we will see cm9 in a port of some kind
[Vibrant General] defconoi:
Doesn't make sense that they wont support the vibrant since GPS and camera work.with it
[Vibrant General] x-out:
my thoughts exactly
[Vibrant General] dardani89:
this is a developers forum of a one and half year old phone with no manufacturer support. we should be thankful for what we've gotten. we could have been left after gingerbread came out but we've gone this far already. I remember about a year ago we were waiting for froyo and were officially still on eclair. now we're trying to see if we'll get ICS, thats a 3 generation jump not counting honeycomb in about a years time. I think that just says a lot about our platforms upgrades.
[Vibrant General] KWKSLVR:
+1 10chars
[Vibrant General] Phrack:
They grow old so fast

Sounds about right, 1.5 years, 2 tops for any dev support of a smartphone. Doesn't matter which phone you get, this has been my experience. Devs move onto newer phones because of better hardware and newer features. Sorry you thought your Vibrant would be supported forever.

Even if you buy the newest, hottest phone you can expect dev support to start tapering off 18 - 24 months after you bought it. Don't blame the devs, blame the phone manufacturers for coming out with shiny new phones every few months.
[Vibrant General] JettyLife:
Hey guys, IMHO, the vibrant made out pretty well. I left the vibrant for the dual core G2x and ill soon be switching back. Even the vibrant roms that aren't unsupported are awesome and make the phone a powerhouse.

plus you cant get unlocked Vibrants relatively cheap online, considering how nice of a phone it is.
[Vibrant General] z0phi3l:
I know that at least one person will be trying to get a MIUI ICS port for the Vibrant, whether or not it pans out is a completely different question.

I'm keeping this till T-Mobile has the Galaxy Nexus, or I switch providers
[Vibrant General] msnuser111:
While we're not officially supported by teamhacksung/cyanogenmod at this point, we do have support from another source for ICS.

come join us in ##icssgs on freenode irc.

http://xdaforums.com/showthread.php?t=1365884
[Vibrant General] playonline53tms:
Those who say vibrant is dead don't only see what's in front of them not what's behind them :) ics will and is coming to vibrant,

sent via Vibrant
[Vibrant General] 9xnine:
Passionv4

Try Passionv4 if you want to try out ICS. It's quite stable for me so far give or take a few bugs.

http://xdaforums.com/showthread.php?t=1362961
[Vibrant General] hkfan:
From cyanogenmod

"Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One."
[Vibrant General] shreddintyres:
Thats their goal, ive had the Vibrant since last september, and the development and growth for this phone has been astounding, while i would love to see CM9 on our phones i am quite content with Fully functional CM7. As others have pointed out new phones garner more attention from developers, if you wanted a phone that was gonna be supported forever you shoulda bought a nexus device. I for one will stick with the vibrant until i can come up with enough extra scratch to buy Galaxy Nexus out right (the UK version supports tmo 4g bands). just my 2 cents

- cheers
[Vibrant General] hkfan:
I can buy a new phone ..no issue with that....But I feel that vibrant with FFC mod has everything which new phones can offer...

Unless I see some real change I will keep my vibrant.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] draztikrhymez:
I don't have my phone yet, amazon!, but I know we can't turn LTE off. Can we just turn all data off and run off of wifi?

I don't mean airplane mode as in calls and texts would still come in
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] silver03wrx:
Yes you can ....click menu settings wireless and networks then mobile networks and uncheck use packet data
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] draztikrhymez:
Perfect thanks, I can't wait for this phone. Coming from a iPhone and ICS looks so much like my old favorite webOS.
[HTC Rezound] zerocool79346:
So since the Rezound has gained it's S-OFF, there is really only one thing holding me back from getting the phone. Will it's AOSP ROMs suffer from the same woes as the Tbolt's do because of the SVDO RIL issue?
[HTC Rezound] Marcismo55:
The TB and the Rezound use the same LTE radio so the code shouldn't be too far off. r2DoesInc had confirmed this before the Rezound was even released IIRC.
[HTC Rezound] triton302:
Forgive me... but what problem was it having on the Tbolt?
[HTC Rezound] zerocool79346:
From what I understand, even with the written RIL code, the AOSP ROMs still suffer because the code isn't perfect. So basically the Rezound would likely be looking at the same problem?
[HTC Rezound] Marcismo55:
Without this coding for the RIL in the TB the data (can't remember if it was all data or just 4G) would not work. I'm pretty sure it was r2doesInc that got the code correct and managed to get data working properly for CM & MIUI.

Someone feel free to correct me if I am wrong...
[HTC Rezound] zerocool79346:
You're correct, but I believe it was only the 4G. However, it also threw a few monkey wrenches into the ROMs themselves, and I'm not sure that the written code ironed them all out.

FWIW, my friend that has the TBolt told me to steer clear because of how badly it botches the AOSP ROMs on his Tbolt.
[HTC Rezound] bolt_of_thunder:
I can't say I'm having any problems with aosp roms on my tbolt. Actually the one I'm on now is the smoothest and fastest rom by far I've ever used (I switch weekly, sometimes daily) , sense or aosp. I'm not trolling, just checking on how you guys and gals are liking your new rezounds :-)

Sent from my SHIFTAO5P
[HTC Rezound] Marcismo55:
Good to hear! Hopefully the AOSP for the Rezound will be smooth because of the experience the devs have gained with the TB.

Waiting pateintly for mine to get here still!
[HTC Rezound] jasonpantuliano:
Wow who said we have s off. I don't see any instructions
[HTC Rezound] jbh00jh:
You won't for a while.

Sent from my Galaxy Tab 10.1
[Defy General] woundedtiger:
Hello,

I read most of the threads on this very topic and I can't seem to find the answer so please don't yell at me for starting a new one. Most of the people had their problems solved in those threads with one of SBF files but I can't seem to find any that can boot my defy.

I have tried to flash my defy with 8 different SBF files but still am stuck on M logo, which is sometimes white and sometimes Red with different SBF files. My original defy was froyo based and it had white M logo (hoping this info may help somehow).

I cannot get my defy to boot with any SBF that i tried. I am in Pakistan and I couldn't see any defy files for Pakistan. my bootloader is 09.10 and RSD recognize my phone as S Flash OMAP 3630.

Can anyone please tell me if there is a SBF file that can boot my defy or atleast allow me to access my recovery mode so I can restore my original froyo version? I tried many times but I can only access bootloader and not the recovery mode.

I am also doing all of the flashing with my SIM card inside the phone, is that correct way or am I making a mistake doing it this way?

Is there a universal basic SBF file that can flash every defy no matter which region it belongs? I would love if such a SBF exists.

I would really really appreciate any help, :(
[Defy General] Adityaak:
I think the sea 15 sbf should work here is the link xdaforums.com/showthread.php?t=1093352

Just follow simple instruction..

If you instal any ROM from gb kernel than it will be hard for you to get back to 2.2.2 if you hadn't flashed a proper fixed sbf i have bad English
[Defy General] woundedtiger:
Thanks, I will give this one a shot and let you know if it worked or not.

PS my Defy has a T-Mobile logo (US company) on it at the back, does all Defy models even sold in like India has those? and what does that mean for my Defy?
[Defy General] hackergnome:
What sbf have you flashed so far....

For ur region sea 15 I'd recommended...

After flashing sbf I'd u get boot loop goto stock recovery and wipe the data...

Make sure u don't flash ginger bread sbf...
[Defy General] Adityaak:
Where did you got your defy? Is it having blur or is it the de blur version? In India I think all defy are with motorola logo at back with sea 15 sbf version
[Defy General] woundedtiger:
I purchased mine from a local company that sells all sort of cell phones. But, I am not sure where they purchase their phones. My Defy indeed had Motorola Blur and T-mobile logo at the back. Thats why i flashed my Defy with US and UK variants of SBF files listed here:

and-developers.com/sbf:defy

I also tried chinese and Nordic versions with no luck at boot. Even if I somehow can access my recovery mode I can atleast go back to my original defy by doing factory reset and resorting it to the way it came in.
[Defy General] woundedtiger:
Ok I tried the sea 15 sbf along with the Chinese Eclair sbf that people put after putting in gingerbread for going back. Yet i am still stuck in logo M. I cannot get into boot recovery mode at all, I tried everything but I can only access the BootLoader and not Boot Recovery.

Please tell me How can i access boot recovery so I can wipe everything and do factory reset and get my defy back to life.
[Defy General] Chamelleon:
I had the same problem and it was really funny. I had Defy Retail CEE with Android 2.1 and next Official Froyo 2.2 CEE too. I was selling it few weeks ago and needed to wipe phone, I wiped data and cache and after this phone stuck on Moto logo. I was trying every sbf. for Europe starting from early versions of Eclair ending on official Froyo and nothing. After this I just removed memory card and wipe data/cache and phone turns on on stock Froyo. Memory card wasn't damaged cause i was using it with this phone and was ok but it just can't boot first time with this card inside. Next boot was ok with card inside.
[Samsung Galaxy S (4G Model)] Light-라이트:
App1.

Unrestricted camera/camcorder -

meaning no battery restriction, fast capture (stock camera takes too long to take a picture), power button to take picture.

App2.

Unrestricted video player -

No battery restriction.

App3.

voice recorder -

no battery restriction

!better voice recognition (stock voice recorder distorts your voice meaning it does not sound like you. Iphones have a very good voice system)

Thats pretty much it for now....

Im not demanding anything, just asking if you can work on these during your free time 8D.

P.s. I already tried sgstools. Doesnt work for me. Dont think that app likes me. ;p.

Thanks in advance!
[Galaxy Tab 10.1 Android Development] Technecium:
As I make progress towards making us an overclocked kernel I will keep m380w users informed in this thread. Wish me luck!

June 16, 2012 Had to post an updated torrent file.

May 01, 2012 New Firmware Released (NOT ICS)

Attached is a torrent file for FD19

Dec. 08, 2011 Development Halted :(

Here's the latest. The source code that Samsung makes available seems to have issues. I have tried and tried again to reproduce a stock kernel that will boot with the initramfs. However, the defconfig provided does not match the .config extracted from config.gz. There are some big differences between the two. The defconfig supplied with the source code defines the board as p4 yet the .config from the kernel defines it as p4wifi. So naturally I have tried both and I have tried many, many other things. All for not.

I contacted FOSS and the response was to the tune of, "We sent your message to the dev. team. If they respond, we'll respond. Until then, just wait."

With that said, I see no reason to muck about with trying to make an overclocked kernel, when there is no indication that I have valid source code.

Nov. 24, 2011

Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.

SHW-M380W.EK10.7z

Rooting directions and files I have tested and do work with this release can be found here on XDA

Nov. 26, 2011

I made some progress and have extracted the initramfs from the EK10 kernel using koush's AnyKernel. See attachments. One step closer to an overclocked kernel.

Pershoot has graciously offered his time and resources and built a recovery cwm_5.0.2.7_kor for the m380w. Which now displays correctly on this device.

He included the following notes:
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
Can you give a few more details?

Is it HoneyComb 3.2?

Is it for WiFi or 3G tablets?
[Galaxy Tab 10.1 Android Development] Technecium:
It is Honeycomb 3.2. The shw-m380w is a wifi model.
[Galaxy Tab 10.1 Android Development] vincentru:
One of the most noticeable difference is the integrated digital dmb tv and radio receiver and antenna. With no change in the look and dimensions. It comes wifi with or without 3g.
[Galaxy Tab 10.1 Android Development] pershoot:
refreshed:

http://droidbasement.com/db-blog/?p=2439
[Galaxy Tab 10.1 Android Development] Technecium:
Excellent! Just completed a backup and all worked as expected.

Thanks
[Galaxy Tab 10.1 Android Development] phuonglev:
Thank you so much pershoot and Koe1974. Now, CWM can operate normally with my device. Actually, my device model is shw-m380s with 3g and I would like to ask you is it able to upgrade by CWM with the custom roms of P7500 (as overcome rom) and the overclock kernel?
[Galaxy Tab 10.1 Android Development] phuonglev:
Hi pershoot. I've just made a backup for my kor tab (model shw-m380s). Please help me to check the boot.img attached and let me know my device is able to apply your kernel or not. Thank you in advance.
[Galaxy Tab 10.1 Android Development] pershoot:
Your device is not compatible with my kernel.
[Galaxy Tab 10.1 Android Development] phuonglev:
Thank for your reply Pershoot. Yesterday, I tried to patch your kernel and my tab couldn't boot, so I had to back to its stock kernel. I also upgraded my tab to Overcome Rom with stock kernel and it works fine exclude one issue is the brightness level couldn't adjust anymore. Because I am not good at hex and linux coding, so I appreciate if you or other developers could help me (and people own this device) to fix my stock kernel to make it is suitable with CWM roms and able to be overclocked. Thanks alot in advance.
[Galaxy Tab 10.1 Android Development] phenix11:
Just to share some of my experience, I have an M380W model, I installed pershoot's CWM-based recovery, backed up everything, and installed Galaxy Task 6.2 ROM for a try (and 6.3 update). The screen keeps scrolling, but this is solved by restoring boot.img within the recovery.

I then have the same symptom as phuonglev, the screen brightness level can't be adjusted (set to medium and looks so), and I sometimes have orientation problems.

Could all this be resolved with your specific kernel koe1974 ?
[Galaxy Tab 10.1 Android Development] Technecium:
I don't imagine it will. All I am planning at this point is to enable overclocking. It will essentially be a stock kernel. It sounds as if it is something in the rom causing the problem. As much as we would like to think the korean models are the same, from past experience with a galaxy s 'shw-m110s vs gt-i9000', the roms are just not interchangable. It always seems that there is 'something' that does not work as it should.
[Galaxy Tab 10.1 Android Development] phuonglev:
How is your progress Koe? I'm waiting for the good new from you.
[Galaxy Tab 10.1 Android Development] aigoya:
Awesome, can't wait to see some progress.

I thought I was the only one with problems trying to use tasks rom.

Just FYI for any other M380W owners out there, you can supercharge your tab. Made a big difference for me.

*Edit

Btw Koe,

There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
[Galaxy Tab 10.1 Android Development] Technecium:
If you are on EK10 then it is probably the update for Polaris Office. However, if you are not running the stock rom, your device may be reporting that is an p7500 or p7510 which I think comes with QuickOffice. So it might be confused.
[Galaxy Tab 10.1 Android Development] samoelito:
could you upload the rom to other source please?
[Galaxy Tab 10.1 Android Development] Technecium:
This is the best I can do ( http://www.wupload.com/file/2662167342/SHW-M380W.EK10.7z ). If you prefer bit torrent, let me know.
[Galaxy Tab 10.1 Android Development] M@31:
So, just to confirm.

If I want to root my device (I just picked it up yesterday) I need to download the

Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.

So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it :)

Then, who do you flash a ROM with this one?

I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before :) Thanks for that.

I have taken over the old thread and have been trying to fill your shoes! hahhaa
[Galaxy Tab 10.1 Android Development] Technecium:
To root just follow the instructions and you will be fine.

ek10.7z is just the stock rom for if you choose to revert from back. currently, there doesn't seem to be much development going on for the m380w so I uploaded it for those brave enought to try roms built for other 10.1 models. I always delete tons of stock apps so it's helpful to have a stock rom to get back it i need to.
[Galaxy Tab 10.1 Android Development] M@31:
is flashing ROMS still the same?

Just using Odin and put the file into the PDA slot?
[EVO 4G Q&A, Help & Troubleshooting] dpwhitty11:
I rooted/rommed a friend's phone with the latest CM7 nightly. She's on Cricket, so I'm not sure what do about mms settings. Google wasn't much help. Can anyone point me in the right direction? Thanks.
[EVO 4G Q&A, Help & Troubleshooting] slydovhans:
Mms settings: dial ##data* in dial pad msl code: 000000

And you should be able to setup everything from there or dial

##276* code is 333333 and

username=(phone#)@mycricket.com and password=cricket. mms settings are: server url= mms.mycricket.com/mms/servlets

Mmc=310

Mnc=00

Any more questions let me know i have a list of codes for cricket network setup
[EVO 4G Q&A, Help & Troubleshooting] dpwhitty11:
All this stuff in apn-conf.xml?
[EVO 4G Q&A, Help & Troubleshooting] dpwhitty11:
Bump.

Still wondering.
[EVO 4G Q&A, Help & Troubleshooting] slydovhans:
Yes. Cricket was having a lot of network problems recently, it should be pretty easy to figure out now
[EVO 4G Q&A, Help & Troubleshooting] iAMsalm:
One thing I did that worked for me was use GOSMS Pro from the Android Market. My preferred SMS app anyway, and went into the settings and found the APN option in there:

Menu > Settings > Advanced (tab) > MMS Settings > APN configuration. Checked Fill APN configuration manually, then set the following:

MMSC: http://mms.mycricket.com/mycricket/mms.php or http://mms.mycricket.com/servlets/mms

MMS Proxy: wap.mycricket.com

MMS Port: 8080

Worked fine for me.

Note: This was when I had my Evo on cricket around 2 months ago, now I have one on Sprint. Just thought I'd give my 2 cents. :]
[Desire Q&A, Help & Troubleshooting] ididnt:
i am having trouble with my video cam not working so did a full wipe and restore. flashed rom gapps kernel ok. radio cant write no space left on device?:(
[Desire Q&A, Help & Troubleshooting] eric_son:
By chance, are you using a custom HBOOT with a reduced CACHE partition?
[Desire Q&A, Help & Troubleshooting] ididnt:
thanks- yes i just changed hboot to oxygen r2 alpharev. i suspected this might have something too do with it. so, what is happening?
[Desire Q&A, Help & Troubleshooting] ididnt:
ok so i went to flash it through android flasher but it is already on there so thats good. but still im getting still camera working and video force closing as soon as i switch to it.

It says "Sorry. the application Camera(process com.andoid.camera) has stopped unexpectedly"
[Desire Q&A, Help & Troubleshooting] Leesire:
maybe try another rom, some have Problems with camera. Has it worked and just stopped without you changing things?
[Desire Q&A, Help & Troubleshooting] WRson:
Are you sure your Rom fits at this Hboot ?
[Atrix 4G Q&A, Help & Troubleshooting] alainalemany:
Hi guys, I have my Atrix 4G with AT&T stock 2.3.4 ROM and I really need to connect to ad-hoc connections. I can see it, but it says "Obtaining IP address" and then disconnects.

I need a working-with-ad-hoc-connections wpa_supplicant or any other solution.

Regards.
[Atrix 4G Q&A, Help & Troubleshooting] Bruce Lee:
Are you using the mobile hotspot app that came with the stock ROM? What's the device you are trying to connect to?

Sent from my Atrix XDA Premium App
[Atrix 4G Q&A, Help & Troubleshooting] anupash:
Connecting to adhoc works with Cyanogenmod 7. However, for the stock rom u might need to patch the wpa_supplicant to work with adhoc connection. Primarily such restriction by factory OEM rom because adhoc connection drain a lot of battery.
[Atrix 4G Q&A, Help & Troubleshooting] pitastrudl:
so cm7 has adhoc support so there is no need for replacing the wpa suplicant?
[Atrix 4G Q&A, Help & Troubleshooting] anupash:
Yep that's correct .. I am connected to a adhoc hotspot right now ..