yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] ChodTheWacko:
One of the interesting features of kl7 firmware is something I've been suggesting for a while - a one handed keyboard.

Its the size of the 4.6 inch keyboard (i think) and you can align it to the left or right side depending on what hand you type with.

So I'm curious now - do you like it? I still prefer to two hand the note. I suck at typing tho.
[Galaxy Note GT-N7000 General] planoman:
I have not tried one handed. I like the size of the full sized keyboard and typing with two hands too much on the GNote to even try it!
[Galaxy Note GT-N7000 General] bnapalm:
I tried it, just to see what it looks like, but switched back to standard keyboard afterwards. Even though my hands are quite big, while holding the phone with my right hand, I was still only _just_ able to press the far-left column with my thumb, and the accuracy of tapping while holding the Note with the same hand is worse.

Besides, the phone is also quite big to hold comfortably using just one hand - after a while it gets uncomfortable. And the full-width keyboard is great and the button size suits me well.
[HD2 General] adolfo778:
So ya I know this topic has probably already been discussed but after several searching I couldnt find the anwser to my problem.

I was attempting to go from android to windows 7 just to test it out so what I did was I went back to windows 6.5 as is suggested I made sure my battery is over 50 percent but now the phone keeps rebooting and the only way it will turn on is if a usb is connected to it My guess is that it keeps rebooting because the battery has no charge in it :| any ideas?
[HD2 General] anseio:
I would think that if the battery pins aren't lined up that it wouldn't power on at all, except when plugged in.

I'm a little confused about where in the process you're having this problem. Have you installed WP7 yet? Or, are you still on WM6.5? Either way, to rule out battery as an issue, boot into magldr (press power button during startup to halt process) and let it charge from there.
[HD2 General] adolfo778:
ya turned out it was the battery pins :P weird would have never thought of that actually guess the battery was on wrong. Got it dual booting windows 7 and android thanks guys :D
[T-Mobile Samsung Galaxy S II SGH-T989] flipq88:
Dont know if this has been discussed alrrady, but I think i found a workaround fix for the blurry mms on 2.3.6. Download handcent and go to Settings> Application Settings> Default Messaging Application and set to MMS

After that my mms come in a lot better. This is with leaving it disabled

And this is after i change the Default Messaging Application to MMS

Hope this helps someone

Sent from Flip's SGS2
[T-Mobile Samsung Galaxy S II SGH-T989] Lantek23:
It worked for me man thanks!!

Sent from Samsung Galaxy S II running Ginger-Snap v1.1
[T-Mobile Samsung Galaxy S II SGH-T989] badazz_monkey:
Working for me as well, thank you so much.
[T-Mobile Samsung Galaxy S II SGH-T989] razormy:
Didn't work for me. Just shows Download button and image doesn't download.

Thanks anyway.
[T-Mobile Samsung Galaxy S II SGH-T989] flipq88:
Try a reboot, mine was doing that also at first l

Sent from Flip's SGS2
[T-Mobile Samsung Galaxy S II SGH-T989] MMakoto:
wait, so are you saying that since making these changes in handcent's settings, and now you're using the stock messaging app-it's not blurry anymore? or you're talking about using handcent only?
[T-Mobile Samsung Galaxy S II SGH-T989] Docmjldds:
DocMark's MMS Bible

Before I go into a long primer below, I still recommend E-Mail for sending a pix. We have smartphones and we have Gmail, so educate others into using this method for the best quality in a picture sending experience. But, for those that insist on MMS.....see below.

As far as I know and have been doing, you just use Handcent period. Handcent does not over compress the pix, so they are larger to begin with and therefore less blurry (or not blurry) to begin with. 99% of the ROMS based on 2.3.6 and using WiFi calling seem to NOT allow sending or receiving with WiFi calling enabled. (TMobile states at least in a tech support ticket to me they know this is an issue, BTW) So...turn off, WiFi calling, use Handcent and it will download/send etc. No reboot required. And you don't need to change anything in that application settings to turn off stock mms. If you go into Handcent send settings and use 1.2Mb mms sizes instead of 1.0Mb, the sizes will be as high as 600-850Kbs on average, depending on what you started with. But larger files take longer to send or receive, obviously. With 1.0 Mb mms settings enabled in Handcent send settings, I typically see 128kbs file sizes which is typically fine for mms messaging. This has always worked for me without doing the CM7 mms.apk shuffle btw also. I hope I covered everything. Oh, obviously if more than one messageing app is in residence, you need to turn off notifications for the ones that you are not using, unless you don't mind redundant notifications :)

Lastly, it's been hit or miss on whether 2.3.6 based wifi calling Roms will work leaving wifi calling enabled. The Zombie 2.x ROMs had been working for me with WiFi calling enabled, but even on that one, occasionally I get the message that the network is not available blah blah message and it won't send or receive. But turning off wifi calling is always the fix and use Handcent, for pix that are NOT over compressed.
[T-Mobile Samsung Galaxy S II SGH-T989] mikeyinid:
BS. No matter how big I set my mms in hancent they are never over 128kb. And this "fix" doesn't work for me. Mms is still blurry with handcent.
[T-Mobile Samsung Galaxy S II SGH-T989] darkamikaze:
Maybe I just don't MMS enough.. but this works fine for me:

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

I didn't flash the CWM.. but used Root explorer to replace MMS.apk with it.

For some reason when I flash using CWM it doesn't work. May work for you let me know.

let me know how it fairs for you all.
[T-Mobile Samsung Galaxy S II SGH-T989] Docmjldds:
I have no idea why it doesn't work for you. But to say BS is beneath your normal replies, IMHO. Here is a test shot screenie I'm posting using Handcent. Not sure which ROM. I believe at the time, I actually had to reboot to get my WiFi calling back to work since you can see the icon has that reddish color, meaning it was not working correctly. The few times this has happened to me, a reboot fixed this. I believe I was getting one of those erroneous sim card not correct messages. I do have a prper sim card. On a few slect times, it will get that message for some strange reason. And this has happened with more than one of the proper new sim cards since I already had TMobile replace mine the first time it happened. Again, a reboot fixes. If this is BS, then explain my message size properties? And it was not blurry either.
[T-Mobile Samsung Galaxy S II SGH-T989] mikeyinid:
Hmmm. I've tested every possible scenario and I can't get mms to be larger than 128. And no matter what, outside of the cm7 mms.apk its always blurry.
[T-Mobile Samsung Galaxy S II SGH-T989] Docmjldds:
I will try to bemore consistent in exact ROM, kernel, MMS apk used if not stock etc etc when posting a test shot etc. I honestly believe we see too many inconsistencies since T-Mobile says it's an issue, so the added variable of a Network issue just adds to the confusion and test results. Just my opinion.
[T-Mobile Samsung Galaxy S II SGH-T989] mikeyinid:
It is definitely clear. But when I send myself pics they are always clear. Soon as someone else sends me a pic it's blurry. Ill flash the stock rom I posted and do some research. Its the absolute closest to stock as it hasn't been doedexed or anything.

Edit: still blurry. Handcent or not. I really don't understand. people have reported in my thread that mms is clear on this rom but it never has been for me. Idk
[T-Mobile Samsung Galaxy S II SGH-T989] Docmjldds:
My only comment back would be my tests of clean installing that Skyrocket ROM and the jpgs I sent to myself were extremely blurry, which is at least for my own testing doesn't follow that sending to myself is always clear, as is for your own testing. IDK either....Confusing at best, but at least for me, I consistently have the same results wrt the Zombie ROM vs any other 2.3.6 based ROM.
[T-Mobile Samsung Galaxy S II SGH-T989] mastajest:
I think I may have found the issue. I changed the max size and user agent on the mms_config.xml.

I'll post the apks I tweaked myself for Jugs4.1 and the ICS themed Mms.apk for Jugs4.1 from the ICS Complete package theme.

I confirmed they worked on my phone by sending myself MMS's from other phones. Hope this works for you.

make backup of your current Mms.apk just in case you have issues you can revert

adb push into /system/app/Mms.apk (basically replace your Mms.apk with one of the ones attached)

reboot if necessary

I haven't tested with any other ROMs besides Jugs4.1 so I can only say it's working for Jugs4.1

Also, sending yourself a large MMS may still cause the compression, but at least now you should be able to receive MMS from other phones without them being compressed to ~19K.
[T-Mobile Samsung Galaxy S II SGH-T989] mettleh3d:
Will try and report back. Thanks a lot
[T-Mobile Samsung Galaxy S II SGH-T989] Docmjldds:
Nice. I'm using the Zombie 2.2 ROM. I also test just now using the ICS mms file you posted. I installed it using root explorer copying to system/app. Fixed permissions and renamed it Mms.apk just in case it needed to run with out changing the name. Rebooted. At first it looked like it was going to compress a pix down to 26kb when using the stock messaging app, so I first used Handcent, with wifi calling enabled and 1.0Mb mms settings. That worked fine. I then went and opened up the stock messaging app. Sent the same file to myself using the stock message app. Attached shows no blur as well as 591kb sized pix. And it was almost instantaneous with wifi calling enabled and the Zombie Rom.

EDIT: At least wrt sending to myself from my phone, Handcent still is the only app for me that leaves compression to a min. If I send a new pix using stock app, it still seems to compress down to 25kb approx. Guess I need to test with another phone sending to me to know for sure
[T-Mobile Samsung Galaxy S II SGH-T989] mastajest:
Glad it worked!

I may have named the files incorrectly since you tried the ICS one and it's not themed. Woops :o
[T-Mobile Samsung Galaxy S II SGH-T989] Docmjldds:
No problem. BTW didn't want to confuse 591 vs 605Kb. Different test with pix changed to slightly different compression, for whatever reason. So disregard the exact numbers. Will borrow one of my family members phones when I can to test this out from another account to me. Haven't used Juggs ROM in a while. Assuming it's 2.3.6 based and wifi calling, does having wifi calling enabled work for you when sending or receiving mms. For me, ONLY the Zombie ROM can work with WiFi calling enabled.
[T-Mobile Samsung Galaxy S II SGH-T989] mikeyinid:
Just wanted to share this with you. I gave my girl my gs2. She has the old sim card that doesn't support wifi calling. Her mms comes through perfectly clear from the same phone she use to send me blurry ones from. May be nothing, idk. Little odd to me that using the same phone/rom combo with switched sims and mms is fine.
[T-Mobile Samsung Galaxy S II SGH-T989] drzplaya1121:
When u guys send MMS pix using handcent, does handcent turn the picture sideways?
[T-Mobile Samsung Galaxy S II SGH-T989] Docmjldds:
No. Works perfect for me. No rotation.
[T-Mobile Samsung Galaxy S II SGH-T989] topdollar175:
People are unable to receive mms from me. It says too large and will be automatically deleted. Any idea why that happens or how to fix this problem. I am running beastmod 4.2 with the included kernel. Thanks for any info
[T-Mobile Samsung Galaxy S II SGH-T989] Invalid Username:
I understand what you're saying -- and I even agree with the sentiment -- but in my experience (for end-users at least) the argument "Method ABC is convenient" always ends up trumping any claims like "Method XYZ is the more appropriate way to do this, and unlike ABC it was intended for that purpose!"

It's not that you (we) are wrong, necessarily; but eventually the market will shift to accomodate how the end users are actually already using the service. Oddly enough, the "correct way" will sometimes even become the "old/no-longer-supported way" before too long.

Consider this: You're suggesting people send photos as email attachments, rather than trying to tack a giant file onto a tiny MMS message. (Very reasonable suggestion.)

But 10 years ago, I can remember trying to explain to people "No, don't attach multi-megabyte files to emails -- use FTP or save it to the department's server or ...etc." Why? Well, because it was the proper way to do it -- "file transfer protocol" it's right there in the name! And if you take a departmental mail server (which for YEARS had made due with just a few hundred gigabytes of storage space) and then suddenly everyone starts attaching, sending, and saving dozens of 50 megabyte files on the server.... well, you get the idea.

So I promise, I've *tried* to evangelize people to the "right way" of doing things -- and many listened (of course, restrictions on attachment size and mail quotas help a lot) -- but it didn't really matter. For most files, it was just more convienient to do it another way; so even amongst this very educated crowd, the "proper/appropriate way" flew out the window.

One final example and then I'll shut up. :) My Kindle has this wonderful feature: I can send documents/ebooks/pdfs/whatever to it from my laptop, wirelessly, without having to hook up the USB cable and all that. Yes, there are ways to transfer the files directly -- but what by far is the easiest method? Attach the file to an email, send it to "myusername@free.kindle.com" and have Amazon deliver the file for me. Is it proper? Is it appropriate, efficient, etc, etc? Nope, but it's convenient. Quick and easy.

So I guess long story short, we'd might as well quit running and just let the zombies bite us. They're gonna get us (they're gonna get everybody) anyway, so we'd might as well get it over with so we can hurry up and get a head start on all those delicious braaaaains.

Now, let me just attach my last Nandroid backup to this MMS I'm sending and I'll be on my way...hmm... :)
[T-Mobile Samsung Galaxy S II SGH-T989] MMakoto:
is it me or the handcent app doesn't show a "1" on the corner of the app icon if i have a new message? i do see it in the notifications bar, but sometimes i overlook that.
[Nexus S Q&A, Help & Troubleshooting] DubsideWICKED:
there is so meny roms going on. i started at the htc hero cdma an knew everything about that phone, i moved to the nexus s 4g an idk who runs the actual CM or AOSP roms. so whitch rom is stock ICS AOSP an CM
[Nexus S Q&A, Help & Troubleshooting] Braneless:
What? CM9 is posted in the NS4G development forum, if that's what you're looking for.
[LG Nitro HD] repherb:
So for the first time i am going to do something i have never done before... HEEEEELP!!!!

Sooooo I guess i will admit that i have fubared my Bell Optimus 4G LTE. I accidentally disabled my LG Stock Launcher and in my haste really fubared my phone. Without any way of regaining an su prompt or root access, i am essentially screwed.

I now have all 3 softkeys at the bottom flashing at once, and the only mode i can enter is adb shell, no SU access available because the phone reboots constantly now before the system partition finishes loading. I can get into download mode, but this serves me no purpose. the Bell unit has only 2GB of internal storage and no other P930 is similar to this one so the chances of recovery are none to none.

I have a feeling i may have to wait until the ICS update comes along as there is no .kdz file available for the Bell p930 yet.

If anyone knows more than me or can come across a .kdz for the Bell P930, please let me know. Bell does not accept returns and will shoot it directly to LG and once they crack it open, well the SuperUser.apk will pop out like a sore thumb and will screw me over for any replacement.

UPDATE!!******************************************************************

I followed Manilion's guide HERE with one very important difference: BELL OPTIMUS USERS MUST NOT FLASH THEIR BASEBAND mmcblk0p14 WHATSOEVER!!! use THIS stock Bell baseband image to preserve your Bell network access!!!!

These are the partitions and image names:

mmcblk0p1 -> firmware.img

mmcblk0p8 -> boot.img

mmcblk0p13 -> recovery.img

mmcblk0p14 -> baseband.img BELL USERS DO NOT FLASH THIS!!!

mmcblk0p27 -> system.img

You will also need to add the Bell APN Settings in Settings -> Wireless and networks -> Mobile Networks -> Access Point Names

Here's the Bell APN Settings if anyone needs them (these also allow LTE access) :

Name: Bell

APN: pda.bell.ca

Proxy: web.wireless.bell.ca

Port: 80

Username: <Not set>

Password: <Not set>

Server: <Not set>

MMSC: http://mms.bell.ca/mms/wapenc

MMSC proxy: web.wireless.bell.ca

MMS port: 80

MCC: 302

MNC: 610

APN type : <Not set>
[LG Nitro HD] schwin97:
If it isn't working then you have nothing to lose in sending it to LG to get fixed. The fix probably takes all of five minutes to reload the software. They may charge, but they may not? Never hurts to try...
[LG Nitro HD] repherb:
True, but then again.... oh, can anyone with a Bell Optimus LTE 4G please post their APN settings??
[LG Nitro HD] keenz:
Haha I guess I should not be a Lurker anymore.

repherb. Apn sent via pm. I cannot post outside links.. I'm not 8 post cool yet
[LG Nitro HD] repherb:
So, i have successfully flashed the SU640 .KDZ file to my unit and rooted it. I am up and running but the firmware is.... buggy... sluggish, and quite a bit of FC's.

I am trying to find the LG Nitro KDZ to flash, any help would be appreciated on this, maybe i could get a LG Nitro user to send me their IMEI via PM so i can download it from LG please???
[LG Nitro HD] LiViD:
That's not surprising, seeing that it's a ported Korean ROM. I'd wait for ICS to be released, which is going to be an eternity from the looks of it.
[LG Nitro HD] Malnilion:
@repherb,

Sweet! Sounds like you're about halfway through my recovery tutorial. What you need now is for a kind soul to post their partition images from the Optimus LTE 4G. I don't know if the default partition layout for the Optimus is the same as the SU640, though...

Maybe LiViD there can help you if he has the Optimus LTE 4G.

I'll do whatever I can to help guide you through the process should you need it.
[LG Nitro HD] LiViD:
I'm not programmer savvy, so whatever you require will require some direction from your behalf. I am familiar with the use of adb and that's it.
[LG Nitro HD] Malnilion:
Alright, I'll dig through the partition layout and get you a list of the mmcblk's that you need to copy with the dd command :)

This'll be outstanding if we can get a recovery tutorial that works for both the Optimus and the Nitro.

---------- Post added at 01:15 AM ---------- Previous post was at 01:03 AM ----------

@LiViD,

There should be a file somewhere in a folder called bootimg-ramdisk/etc/recovery_mmc.fstab according to this post by schwin97. I need the contents of that file to make sure your partition layout is the same as the Nitro's. If it is the same, this is going to be really easy :)
[LG Nitro HD] V@no:
If you can get into adb shell and stay there, then all you need to do is re-root.

In last 2 weeks I've done it at least hundred times while messing around with SystemUI.apk file.

If SuperOneClick doesn't work, then try manual root, if that fails, use the old version of zergRush binary which I posted under manual root topic. It might take several tries before it succeed (I once had to try non-stop for 2 hours, while it was boot animation looping, but zergRush finally succeeded)
[LG Nitro HD] Malnilion:
V@no,

repherb's already past the point of no return. He's on the SU640 rom already. I think we can get him back to stock though if LiViD helps us out.
[LG Nitro HD] repherb:
<starts grinding up the ROM Flashing program> all right boys and girls it's time to FLASH!!

@ V@no: yup i am past the point of no return

@LiViD: feels like a spinoff of that movie: "Dude! Where's my (car) partitions?!", and yes your (or anyone's help on Bell) help would be most appreciated.

@Malnilion: Yup i have discovered the partitions are identical across the P930 from Bell and SKT SU640.

So it looks like this might be an exercise in patience waiting for ICS or the partitions from a Optimus LTE 4G. An industry insider from GlenTel (tbooth, wireless wave) has informed me that LG has notified Bell of a February timeline for the ICS update. Whether this holds true or not is beyond me, but he has been right before.

To everyone, thank you for helping me out of this jam so far, and for your help in the future.
[LG Nitro HD] Malnilion:
repherb,

If you're positive the partitions are the same, I'll go ahead and give the steps for creating the images so that LiViD or anyone with a Optimus can help:

adb shell
su
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p13 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p1 of=/sdcard/firmware.img
dd if=/dev/block/mmcblk0p27 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p14 of=/sdcard/baseband.img

Then get them off your sdcard. I actually don't know how to do this using adb commands lol, but I think you just do an adb pull for each of the filenames?

So assuming the partition layout is exactly the same (I'm still kinda hoping to get the output of the file I requested before), anyone with an Optimus 4G LTE can help you out.

In the meantime, repherb, you could try flashing the AT&T images as an experiment. I have a hunch your phone would work pretty much exactly as a Nitro would :)
[LG Nitro HD] repherb:
Might want to edit that post to say "anyone with a Bell optimus lte 4g"

<GRINDGRINDGRINDGRINDGRINDGRINDGRINDGRINDGRINDGRINDGRINDGRIND> already flashing them now, will let you know in a bit what the outcome is. I hope they are the same base partition layout, because that would be pretty cool!!
[LG Nitro HD] Malnilion:
I can assure you they most definitely aren't the "same" (at least the system one). They could be close enough to actually function properly, though. I'm really intrigued to hear the results :)
[LG Nitro HD] aquariuz23:
Sorry, jumped in this thread really late. So I'm assuming an AT&T P930 will not work with Repherb's Bell Optimus LTE, or will it work? If it will work, I can try to help the best I can. Just let me know what to do.
[LG Nitro HD] repherb:
i am in the process of sending the Nitro HD system.img and firmware.img image files from gordec's post here to my Bell Optimus LTE 4G after trying <successfully!> to recover my P930 to the SU640 .kdz ROM image but having FC's and other issues... Anyone else get that sneaky feeling i am a Guinea Pig??? :D
[LG Nitro HD] Malnilion:
Just remember to do a factory data reset when you start your phone back up after flashing all 5 partition images.
[LG Nitro HD] repherb:
5??? i can only find 3!!! unless i am blind, senile and anal retentive... :D

@aquariuz23: Pray, just pray!

Oh, i can confirm that the SU640 ROM _does_ achieve LTE access to Bell's LTE Network
[LG Nitro HD] Malnilion:
Lol! I thought you were already following my unbricking guide.
[HTC Sensation] raja'i:
I have sensation XE which is locked to India CID: htc__38

and I wanna have an arabic rom, which i couldnt find any proper RUU for it

coz I like orginal roms

can anybody tell me if i s-off my device, install CWR, then change the CID to the arabic CID which is HTC__J15

does anything happen to my existing rom which is "htc__38"?

would the mobile boot after I reboot it?

and will i have the official arabic update if i checked for them through the settings??

"there is already an OTA for devices coming originally with this CID"

and what will happen to the S-off and CWR if any official rom where installed

thanks a lot in advance

any help is appreciated
[HTC Sensation] Psychoticus:
Is there a reason why you cant just root and go to super CID which is all 1's