yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] UseYourIllusion:
Emoji doesn't work when sent to my girlfriend's Verizon iPhone 4. It works for like 2 messages if i restart my phone and then just shows up as question marks after that. It didn't work on my original One X on Clean ROM 4.0 and now with my new one on 4.5. It worked with GOSMS on stock ROM but doesn't work with GOSMS now either. Anyone know how I can fix this, it upsets her lol.
[AT&T, Rogers HTC One X, Telstra One XL] UseYourIllusion:
Notifcation hardly ever sticks in the status bar with this app. I had the same problem on my old One X with Clean ROM 4.0 as well as this new one with 4.5 If I don't see the text come in I don't even know half the time because there is no icon in the status bar. Really like this but emoji never works when sending to non AT&T people and notification system is faulty. Is there anyway to fix this??
[AT&T, Rogers HTC One X, Telstra One XL] reidman:
+1.....The compression rate is terrible. I know there was another asop message app that ignored the size limit but it didn't support emoji...would be nice to combine the two somehow...
[AT&T, Rogers HTC One X, Telstra One XL] mrbillishere:
Would anyone else care to report on the specific ROMs that this works 100% with?

I'd love to get this working but on my ROM (CleanRom 4.5 DE beta) I had the MMS issue with stripped photos.

I also found that the stock messaging app was a different name than the OP's, fwiw. So in my case I renamed the apk named, 'Message+MR_1.apk' and the odex file then dropped the attached in its place using the same name as the file I renamed. Basic SMS worked, but in MMS the pictured were stripped. Bummer cause I liked the emoticons, and the AOSP interface is nicer too, imo.
[AT&T, Rogers HTC One X, Telstra One XL] Saenzscene:
Strange. When I was on cleanrom De it worked fine. After I renamed the odex.apk and the messaging.apk I cleared cache and delvik. Then I also went into apps and cleared data on messaging. Reboot and it worked fine.

Sent from my Nexus 7
[AT&T, Rogers HTC One X, Telstra One XL] atombone:
any chance of getting the 4.2 messaging app working? (popup capabilities)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seanci:
Hey guys just wanted to see what other people are getting on seanz amazing rom skyIcs.

I'll start by posting a screenshot of battery stats.

Please feel free to state your base and update as well as a screenshot to see how you stand.

****If you are not using sky ics please do not post screenshots or bash his rom***

Sent from my SGH-i727 using Sky-ICS build 4.2e-17
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seanci:
Reserved

Sent from my SGH-i727 using Sky-ICS build 4.2e-17
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ckck543:
Just wondering what you might need that reserved post for?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seanci:
Lol just in case I switch to a new rom just to compare the two.

Sent from my SGH-i727 using Sky-ICS build 4.2e-17
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ckck543:
I see :P
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ian1:
Pretty decent
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] chinthekng:
How do you get such good battery life I'm on update 17 and mine barely lasts 12 hours of light use
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seanci:
Not quite sure, I don't use bt, data( I'm always in wifi range), brightness constantly low and I use the user space or on demand governers they seem to work quite well. My battery lasts all day from when I wake up at 6am until around 10pm.

Sent from my SGH-i727 using Sky-ICS build 4.2e-17
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nrm5110:
Cm9 start hating
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seanci:
Always biggest troll, the open says no other roms besides sky ics....other than that are you running nightlies or team chopsticks cm9? I want to switch over when all the bugs have been worked out so I can use as a daily rom, do you know if anyone fixed the HDMI out for cm I heard it doesn't work properly.

Sent from my SGH-i727 using Sky-ICS build 4.2e-17
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Bruno2123:
I started having problems with battery life issues after update 17 but turning off back up my data in back up and reset has helped a ton. There also might be something wrong with google services constantly downloading something I stopped it with droidwall for awhile but after turning back up off it seems to have stopped hope this helps.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Ends:
Your screen has been on for over 7 hours? Not bad.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wendellp601:
Here is mine.

4.2e-17 with xloud ON
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nrm5110:
Screen on time post or it doesn't count lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Dirtburgler:
Turning off the backup does help a lot. Here is also the option to tell wifi to stay on only while charging when sleeping. Its set to be on at all times by default, but will help quite a bit while asleep. Hit Wifi, then hit menu, then advanced settings.

To android vets this a well known, but it may help some android noobs get that stellar battery life their searching for.

i727-ucle2-SkY IcS
[Motorola Droid RAZR] xgshortbus25:
I keep seeing posts about not being able to come back from ICS to GB I want to know why? I'm not dumb and I have looked but don't really understand why you couldn't come back from a leak? There are methods of completely wiping the operating system from the phone I've done it could you not do this after installing a leak?

Oops I don't know how to delete a post just logged in with my PC and seen the new Q&A section didn't see that on my phone mods can delete if needed or move it if possible!!!
[Motorola Droid RAZR] daniel644:
Because 4.0.4 leaks update the bootloader and since the bootloader is locked you can't revert it back to an older one. If I understand it right.
[Motorola Droid RAZR] BytecodeMe:
Yes, this is correct. And fastbooting doesn't / can't flash bootloaders. So that's why were stuck.
[Motorola Droid RAZR] xgshortbus25:
OK

So a bootloader is like the bios of a motherboard? But locked or not if you erase everything I don't know did the bootloader not change with the first leaks?:confused:
[Motorola Droid RAZR] sonicfishcake:
Not quite.

The bootloader can be upgraded (this happens usually with a OTA) but cannot be downgraded.
[Motorola Droid RAZR] xgshortbus25:
OK see what I'm saying if the bootloader gets upgraded with a OTA it can not be wiped? So not all the leaks have the bootloader upgrade within them then? This is why I'm having these questions when I upgraded flashed to the first leak I had a few problems with it and didn't fully know how to get it back off and back to stock I installed bootstrap and played with it all of about 2minutes before I had completely erased everything on my phone and could not go anywhere and had to fastboot with fastboot file. What I'm saying is if the upgrades come with a updated bootloader sometimes then formatting the internal memory can delete everything and you can apfastboot back to another stock rom right? I would belive this could work you just need a way to get to a custom recovery mode to be able to format the internal memory? I may be confusing more people than I want but wanted to understand this better!
[Motorola Droid RAZR] Giblet535:
I assume it is because the phones BIOS will allow upgrades to the bootstrap code, but not downgrades. It's probably tied to the revision string value.

The .79 leak is (I'm pretty sure) the latest leak that doesn't upgrade the bootstrap code (aka bootloader), so reverting to GB is possible from .79 or earlier leaks. I re-flashed GB from .79 last week, so I can confirm that it does actually work. I'm on .181, waiting for an OTA release of .912190282762628 from Motonverizola.

Motorola may know a trick to force a bootstrap downgrade, but I do not.
[Motorola Droid RAZR] dtrail1:
The bootloader is not the only problem, it can be downgraded without a problem (e.g. from 0A.74 to 0A.6C). The reason that we cannot downgrade from ICS to GB is the signature on each partition. The partitions are getting signed. For example the boot (kernel) partition gets a higher secure number when updated. Now, when we want to flash another boot.img, its secure number has to match with that one from the boot partition, otherwise there will come up an signature verification error. And the same thing applies to the another partitions (except /system which is unsigned). The bootloader is responsible for the signature checks. If it were unlocked the signatur checks could be turned off and we were able to flash anything to the device.

But there are some tricks possible to perform a downgrade. But this would be a lot of work (patching fastboot files to the ICS-matching secure versions or signatures. Decrypting of Motos signature is nearly impossible, so we would have to patch already signed files - too much work and not really needed)

And official ICS will come now and with it we will get a lot of nice things. We will be able to bypass the bootloader for booting custom kernels, we will get full working custom roms and we will be able to use the full power of our Razr.
[Motorola Droid RAZR] xXxTehxXx:
I hate to be that guy but seriously:
[Motorola Droid RAZR] xgshortbus25:
OK got it now!
[Motorola Droid RAZR] cheekrox:
I think we should start something like a community project to guess n hack the bootloader encryption. Heck, I could leave my lappy on 24x7 n use brute force.
[Motorola Droid RAZR] BakaPhoenix:
We could use a cloud based array to crack it XD

BUT i don't think setting up this system is worth the work. Some dev are hinting that after the ics ota we will don't need the unlocked bootloader. So just wait and hope for the best :D
[Motorola Droid RAZR] sonicfishcake:
It's likely the encryption key is nigh on unbreakable even with a cloud based array it would take years, by which time we will no longer have our Razrs so it would be a waste of time.

Guide to AES encryption:

http://www.moserware.com/2009/09/stick-figure-guide-to-advanced.html
[Galaxy S II Q&A, Help & Troubleshooting] shermanx:
Hi all

I have been wondering how I can tell if the custom or claimed-to-be-official S2 ICS rom supports OTA upgrade?

I know it's perhaps impossible for those custom ones, but the ones I downloaded and flashed that claim 'official', how can I be sure if they supports OTA or not? I am a bit tired of keeping flashing the new versions after all.

Thank you!
[Galaxy S II Q&A, Help & Troubleshooting] gaeilge:
it is strictly connected to your product code and region the ROM was released for - these two things have to match.

You will have OTA update if you're using ROM officially released for the region you have set in your phone. and you will get OTA updates only to other ROMs released for this region. few examples:

1. you have XEO product code and you use ROM officially released for XEO - you will get OTA updates but only to other ROMs released for XEO;

2. you have TWO product code but you have installed ROM released for XEO - you won't have OTA update at all (unless you change your PC according to you ROM release region - to XEO - and then, again, updates will be only to XEO ROMs)

3. you HAD XEO and ROM released for XEO, but for some reason you changed your PC to TWO - you won't have OTA update at all (unless you match your PC with region your ROM was released for again).

so, check your product code and the region your ROM was released for, match them however you want - change ROM or PC - and you will be having OTA updates. remember that changing PC is wiping all your data so do backup.

other thing is that you won't have OTA update if you use custom ROM, custom kernel or in some cases root (depending on the root method. rooting phone without making changes to kernel doesn't stop your device from getting OTA update until you make changes in your system).
[Galaxy S II Q&A, Help & Troubleshooting] shermanx:
Thanks for the detailed response. So I guess I need to get a stock rom for Australia then as I bought the phone and am using it in Australia.

Where I can find it? What's the code for Australia market? XEO is just for Euro, rite?

Thanks!!
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Get the PC version of Checkfus (search for it on here/Google) & download I9100XWLP8/I9100XSALP4/I9100XXLPS/I9100XWLP8 which is an unbranded Australian ICS stock rom. Flash it following the instructions in this thread. You can also download carrier branded ICS stock roms with Checkfus if that's your preference.
[Galaxy S II Q&A, Help & Troubleshooting] shermanx:
Thanks!

a few more questions:

1. How can I tell a ROM definitely supports OTA before I install it?

2. How can change my s2 region code to match the ROM's in order to get OTA working again?

3. what's the real difference between carrier branded rom and unbranded ones? e.g. is it better to use say telstra branded rom?
[Galaxy S II Q&A, Help & Troubleshooting] gaeilge:
1. Be sure that ROM was released for the region/carrier which fits product code set in your phone - it's always written in ROM info on any download page I know. you may also adapt product code in your phone later, to fit the ROM you wish to use (in case you insist on FOTA/Kies updates).

2. *#272*IMEI# changes your product code. Remember that it wipes all your data.

3. Branded FW may include additional apps but also lot of operator's useless trash. Personally I never use branded ROMs and always suggest debranding. Check thread about chosen ROM for more info.
[Galaxy S II Q&A, Help & Troubleshooting] shermanx:
Thanks, Re #2, it seems strange that although I never used that command to change my code, only flashed a stock rom issued for another region a while ago, now the checkfus says my handset's the regional code that fits this new rom, other than the supposed-to-be australian one.

Is this normal? So the flashing process can actually alter the phone prod. region code without warning me?
[Galaxy S II Q&A, Help & Troubleshooting] gaeilge:
Theoretically it shouldn't but s... happens. If you were flashing ROMs in which your product code wasn't available then it could adjust itself. Mostly I've seen situations when after such an ROM update, PC just wasn't available for change but it stayed the same as it was. On the second hand I've also heard about few cases like yours. Anyway, are you sure about your original PC if you never used this code option? Maybe originally it was different than you think it ought to be?
[Galaxy S II Q&A, Help & Troubleshooting] kilometers4:
You can also try www.sammobile.com for stock firmware. Just make sure that you input your device and region correctly

Edit : and you'll have to flash through odin :)
[Galaxy S II Q&A, Help & Troubleshooting] shermanx:
Strange!

1. I use *#1234# command and found my rom info is I9100ZSLPG, which is for the region Hongkong - TGY

2. then I use *#272*imei#* (Product code) to check my phone's current CSC, which is shown already 'TGY'.

Now my question is, why my phone still can't get any OTA update?

Any other bit not matched? How to check if any?

Thanks.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
Since I flashed sky ics I haven't been able to fix permissions like I was on a stock rooted rogers phone. Gives me an error everytime. Any ideas?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Busy box. Install it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
Every time I try it fails

Edit

I have 37.0mb free in system/bin could that be why?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Ends:
Nope. Update Busybox. IDK
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
Hmm is there a flash or rom for busybox since the program isn't doing it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skrambled:
By "program" do you mean the app? If not, download the app from the market (Play Store).

Or, just fix permissions in ROM Manager. Works every time for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
That's the issue I'm having is that rom manager/cwm isn't fixing permissions
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Ends:
It is impossible to fix permissions unless busybox is installed properly.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skrambled:
Yup, needs busybox. Download the app and install it.

PS--When people say cwm on this site they mean cwm recovery, not rom manager. Not everyone uses the term correctly of course, but just thought I'd let ya know.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Ends:
Easy to mistake, beings ClockWorkMod makes ROM manager
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skrambled:
True, I understand that. Not trying to be a jerk by pointing that out, it's just very confusing to those of us trying to help when people get this mixed up.

I've been using rom manager for a long time but I'm pretty sure this confused me at first too. :beer:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
That's why i always just say "recovery". That and a lot of people use other recoveries.

--

SGH-I727 using XDA premium, running cm9.

Questions? look here: http://xdaforums.com/search.php
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Ends:
Oh no, no jerk. I was totally agreeing with you. :beer: is good
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skrambled:
Good call, makes it crystal clear.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skrambled:
Ha! Right on. Kind of ironic that I misunderstood you. lmao
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] garydv2002:
I had the same problem. If you are on cwm touch I don't know why but you must have busybox 1.21. If not rom manager is gonna hang up every time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
well ill take note of those differences aha thanks for the heads up, and im gonna try installing the 17b update and see if that fixes my issues

just a quick edit:

when i do go into busybox its the free version and it says "BusyBox null is installed" then "Busybox is installed to sh:<stdin>[1]:not found"

then gives me the option to install 1.20.1

so do i need to spend the money to upgrade to busy box pro?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] garydv2002:
I didnt. I just went to the market and typed busybox downloaded the app and installed it that way... the app just says busybox not busybox installer. I think stericson is the app dev on the one I'm talking about....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] confyzone:
holy sweet bleep it worked, i dont know how but it finally installed lol.

I went to update to 17 on sky ics, it was taking forever in recovery so i rebooted the phone, tried busybox again and it said it was SUCESSFUL!!

Edit

Lol so I noticed I had to do a delvik cache clear to get busy box to install but even after install and permission rewrite it still won't install 17 for me :confused:

aha well thanks for your help everyone.
[Galaxy S II Q&A, Help & Troubleshooting] Yoruichigo:
New Samsung Galaxy S2, works perfectly as a media player...somewhat lacking in the mobile phone area... Unable to make calls, texts or use internet, somewhat nullifying the purpose of a phone =/ It displays the "not registered to network" message when I try to make calls or send texts... Ever so slightly annoying =/ any suggestions please?
[Galaxy S II Q&A, Help & Troubleshooting] g00ndu:
Did you try your sim card on other phones?

Did you try another sim card in your GS2?
[Galaxy S II Q&A, Help & Troubleshooting] poppienutshell:
Probably try resetting your APNs. If you are getting this error while underground/in the office/in the loo/travelling/hiding from the rain/paragliding/standing next to a relay station, it's either environmental circumstance or your telco's fault. Hardly anything to do with hardware. I assume your phone's not rooted? New stock phones should just work right out of the box. You could bring it back to the shop and get someone to test/verify the condition of your phone.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] skramz:
Is there any mod for the MiniCMSandwich Lite AOSP that would have the power menu options to reboot in clockworld and take a screen shot? Plus the additional skip track via long press volume... (up=next, down=prev)

Because I tried flashing Lasan's work on kamarush's MiniCMSandwich Lite Final v4 and there seems to be an issue.

http://xdaforums.com/showpost.php?p=27256913&postcount=1

The rom would load and then all of the sudden would just freeze up, and then restart the phone.. Tried wiping data but that didn't help..

:(:mad::confused:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] anivesh93:
http://xdaforums.com/showthread.php?t=1704226

this worked for me..If this is what you need
[Android General] shekki:
Under the GPL requirements companies are to release the source code within 90-120 days. HTC also made a promise to release kernel source code for their devices. So far HTC has been the clear and has usually released source code for devices within weeks of releasing an update for that said device. However with one particular device HTC has been slacking and that device is the HTC Amaze 4G.

The ICS update for this device was released about a month ago around May 16-21 for T-Mobile. As I stated earlier HTC usually releases the source code within weeks and have done so for other devices that came out AFTER this device. Examples of this are the HTC One series phones. Within a week HTC released the source code for these devices. This is somewhat understandable as these are HTC's current flagship devices and they would want to support it fully. However what I don't understand is how the Sensation XL received it's source code release within a week of it's ICS update and yet the device itself was released after the HTC Amaze 4G. It's as if HTC has decided to put this device on the backburner and ignore the Amaze customers. HTC has decided to instead support the HTC Sensation series devices and release the source code for those instead of the Amaze. This as a customer is frustrating and makes me believe that HTC does not care.

To ask HTC to release the full kernel source code and not partial source code like they did in the past with this device is not that far fetched. Other companies such as Samsung listening to their customers to release the source code and whatever else they need to develop on their devices. Sony Ericsson even went as far as to work with Team Douche to make sure CyanogenMod would run on their devices.

It is up to us on xda-developers and other android developing communities to get HTC to live up to their promise and release the full kernel source code for this device! We must let our voices be heard! I've already contacted them about this and you can too! Just contact HTC on htcdev.com and raise this situation to them. You can also tweet them @htc and @htcdev to get their attention. Please be professional when talking to them or they won't take us seriously. If enough of us voice our opinion on this matter then HTC will have to listen to their customers. I may include my conversations with HTC in another post.
[Android General] mcord11758:
HTC is struggling to stay relevant

Flyer
[Android General] Biohazard0289:
This issue requires support from everyone, we can't just let it go. I've generally liked HTC devices, however I do not like this "pick and choose" support mantra.

I don't understand the issue, release it and quit frustrating users. Done.
[Android General] shekki:
I'm an avid HTC fan as all my Android devices have been HTC; however this "pick and choose" thing is making my liking towards HTC to fade.
[Android General] Biohazard0289:
In order to stay relevant as posted above, this kind of thing just shouldn't be an issue.
[Android General] fredryk:
I had a Sensation and it was a piece of crap. The source code bs, random rebooting all the time, volume rocker fell off, the list goes on and on.

HTC is a bunch of scammers, too. Read this, you will see that they had a faulty design in the Sensation where the volume rocker fell off on a lot of devices, and because so many people claimed warranty on it and they were losing money, they stopped honoring warranties for that issue.

Ditch that HTC crap and go the Nexus route, man. The Galaxy Nexus is the best Android phone you can buy.