yashsingh1/xdaforums huggingface dataset:
[Nexus S Themes and Apps] revant:
My updater-script says

ui_print("Installing Launcher2");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
delete("/system/app/Launcher2.apk");
package_extract_dir("system", "/system");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Installation complete");

So it just removes any of previous Launcher2.apk
[Nexus S Themes and Apps] sugar 7:
what is the zip for flash with CM7 galaxy s for had it ?

thanks !
[Nexus S Themes and Apps] wingphil:
Hi there,

This looks like exactly what I want, but I don't have a nexus S, I have an htc desire. Running CM 7.1 final. Do you think this will work for me too?

Phil

---------- Post added at 12:32 PM ---------- Previous post was at 12:12 PM ----------

I tried it, it worked. Performance was slower than launcher pro though. Nexus S is faster on graphics obviously!
[Nexus S Themes and Apps] marco.ska:
thanks. Stock launcher still the best
[Nexus S Themes and Apps] .:Crack:.:
This doesn't work on CM7 i9000, any ideas why? (Because its not Nexus S? I thought CM7 was AOSP.)
[Nexus S Themes and Apps] Techno Droid:
can you add scrollable widgets support?
[Nexus S Themes and Apps] ilias4780:
no big differnces from the original. anyway thanks :)
[Nexus S Themes and Apps] jimmkind:
launcher2 2.3.7 without wallpapers and wallpaper chooser

Can someone please compile this.
[Nexus S Themes and Apps] jimmkind:
I simply want the original lanuncher2 2.3.7 compiled with only theese two commits:

wallpaper: remove com.android.launcher2.WallpaperChooser activity

and

Removed wallpapers
[Click General] Lazdaa:
When i try to restart my phone or just startup my phone in recorvery, it gets stuck on the "Tattoo" screen.

I've got the Clockwork mod 5.0.20 or something like that installed...

What do i do?
[Click General] Lazdaa:
-Bump-

Anyone?
[Click General] Njusskallo:
same problem, 5.0.2.0, now i'm stuck on tattoo, easyest way to fix this or restore default?

EDIT: + i wiped data/factory reset ... so i dunno if tattoo's now empty or with unbootable android. cant boot it, how to restore 1.6 (got backup with rom manager)

(sry for my bad english)
[Click General] gavincz:
Same issue here.

I was on CM7.0 stable. Today, I updated clockwork to actual latest version (same as the gentlemen above), flashed new recovery.

When I've tried to backup or reboot-to-recovery, infinite booting with TATTOO splash screen was all I've got. But after removing battery, I was able to boot with normal boot path.

Later today, I've tried to Fix Permissions through Clockwork and after reboot, I was stuck with TATTOO splash screen even after battery removal.

I've tried factory reset, it seemd to be successfull, but with no actual result - I'm still stuck with splash screen and cannot do anything.

Does somebody have any idea, what to try?
[Click General] gavincz:
I was not able to recover the CyanogenMod, however downgrading to stock rom via GoldCard was possible. (reference is here: http://xdaforums.com/showthread.php?t=1283429&highlight=stock+rom )
[Click General] mattia29:
Try flashing cyanogenmod stable 7.1.0.1 and then re-install the recovery via rom manager...Tell me if it resolves
[Click General] VuK$3:
Try to get into recovery from boot loader or flash it manually with adb... :)
[Click General] sunitknandi:
Flash ClockWorkMod a couple of times: See this:http://xdaforums.com/showthread.php?t=1293096&page=2 and http://xdaforums.com/showthread.php?t=1297141

Hope I helped you. Hit thanks if u liked it.
[XPERIA X8 General] arrakis3k:
Hi all,

After much reading on the forum, I have some question about sim unlocking my X8

It seems not possible without paying. And htccode seems to be ok, for what i've read.

Just a question; I'd like to use the bypass method (for the price), but there is not much informations. I'd like to be sure it will work so I dont waste money.

The website says "requires firmware 2.1", but my X8 is in 2.1-update1.

Is it still good?

Something else I should be aware of?

Thx
[Galaxy S II Accessories] socalphil:
After carefully looking at the FCC filing internal pictures and a certain website that tears down phones. It is clearly apparent that our European models are missing the NXP NFC chip.

I had hoped to just change the battery to the ATT one, but I think we are screwed on NFC for now, until a new fangled microo SD might add it.
[Galaxy S II Accessories] DJSYNTHVIRUS:
I picked up a Samsung Attain today(GS II) and looked all over for the NFC settings i couldnt find them. When i opened the back of the phone the battery read NFC like you had said. So this is hardware related ? We cant get an AT&T battery pop it in and have NFC work( after some tomfoolery of course)?
[Galaxy S II Accessories] compuguy1088:
Honestly that is exactly what I was thinking....
[Galaxy S II Accessories] nikzDHD:
If you take a look at the NFC models one thing you notice they are slightly thicker, why? Maybe there's some internal for NFC? Too early to say whether the NFC battery actually contains the NFC chip but most likely it does. It's still disabled on the AT&T version, until someone figures out how to enable it etc and whether actually it can be ported over. Or if there even is a NFC module inside the phone as well.

Need to see tear aparts of the Korean models.
[Galaxy S II Accessories] jdsemler:
Don't you need 2.3.6 to support NFC?
[Galaxy S II Accessories] nikzDHD:
Nope, it's down to Samsung to implement this on their firmware. Korean models come loaded with a carriers app to make use of their services but plenty of other NFC related apps on market, 2.3.6 will make some improvements to NFC.
[Galaxy S II Accessories] socalphil:
Do me a favor and go to phonescoop.com and look for the galaxy s2 att. Then click on the FCC filing number in the review. Click details at the FCC page and you will see internal photos. You will see the NXP NFC chip in the radio section. If you go to Ifixit.com and look at the tear down of the European model you will see a space where it goes. Not populated.
[Galaxy S II Accessories] nikzDHD:
Thanks, that's cleared up everything.
[Galaxy S II Accessories] socalphil:
AT&T lost band 8 to make space for the NXP circuit. Our model is quad band 3G AT&T is tri-band 3G.
[Galaxy S II Accessories] KayDat:
Which page on the FCC report? Trying to find the NXP chip, not sure where to look.

Edit: Wait, dw I found it. Page 4, just to the left of the volume buttons. Interesting though, the unpopulated pins in the I9100 don't line up exactly with the I777. Actually, the whole radio section is completely different.
[Galaxy S II Accessories] AllGamer:
you know you can buy the NFC enabled batteries for SGS2, right?

for example the new sprint version and T-mobiles version have NFC, but they are not part of the phone, rather they are integrated into the battery pack.

so, if i'm not mistaken, all you need to do is swap in a battery with NFC build in to make it work
[Galaxy S II Accessories] KayDat:
It's more than just the battery. I suspect "NFC" batteries are simply giant NFC antennas. I have an NFC battery with my I9100, and I've tried flashing AT&T and Korean M250S/K ROMs and kernels to try and get NFC working, to no avail. Many SGS2 phones are definitely missing NFC hardware.

---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------

As a side note, I'm hoping this comes out soon.
[Galaxy S II Accessories] Mr.Raviteja:
Android 4.0 AKA Ice Cream Sandwich comes with NFC = You can make sure if NFC is available on your Device or not ...I think many know this
[EVO 4G Q&A, Help & Troubleshooting] jlgreen531:
For the past week or so engadget.com hasn't been working on my phone. I am running CM7 nightly from may. My gf has a stock Epic 4G, and it isn't working on hers either. downforeveryoneorjustme says that the site is up. Is anyone else on sprint having issues?
[HTC Sensation] moshe22:
Can someone who has not updated your Sensation or someone that knows what software version the TMO USA Sensation comes with post it here?

I checked the thread that has all the official ROM's and there is two for TMO USA and wanted to know which one it is the one that actually comes with it and lets you install to 1.45.

Thanks in advanced
[HTC Sensation] Behold_this:
1.29......
[HTC Sensation] moshe22:
Thanks
[HTC EVO 3D] Eaglesfreak:
It would be really cool if a Dev could port this app from the lg thrill.

Is anyone else interested.
[HTC EVO 3D] JohnM:
Link to app thread?
[HTC EVO 3D] KB112:
3D Space?

If its the app from the LG phone, I think it just puts a bunch of 3D stuff in an easy to find directory. Unless I am thinking of something totally different?

http://att.deviceanywhere.com/LGThrill4G/tutorials/13893

3D Space and 3D Widgets

NEXTPREV EMAIL IT PRINT IT

Press the 3D key on the right side of the phone to access 3D Space. It will show you 3D content, such as:

3D Games & Apps: Any 3D Games and Applications you have downloaded from Gameloft™ 3D Store will be listed. Four applications, Asphalt 6, Let's Golf 2, Nova, and Gulliver's Travels, are provided as default settings.

3D Guide: Provides advice on how to create 3D pictures, connect to 3D TV via HDMI, view or share 3D content, and more.

YouTube 3D: Select a video you want to watch or view your own uploads. The video will be shown in side-by-side format in portrait mode.

3D Gallery: View or edit your 3D photos and videos. You can also share your 3D content by touching Menu, then touching Share to select an application.

3D Camera: Switch to 3D Camera mode to capture 3D photo and video.

Note: You can also access the same 3D applications by flicking the Home screen RIGHT to view the 3D widgets.
[HTC EVO 3D] mancuk29:
There is the apk knocking around on the lg optimus. 3d forum alas it doesn't work on non lg handsets ill see if I can try to find the link
[HTC EVO 3D] mancuk29:
http://xdaforums.com/showthread.php?t=1195237
[HTC EVO 3D] mancuk29:
Sorry guys unless someone can re program the apk were stuffed
[Nexus S Q&A, Help & Troubleshooting] Oldiesmann:
I've been using Ultra Keyboard for a long time (used it on my Hero and have been using it on my Nexus S 4G since I bought it back in July), but starting with CM7 build 115 or 116, it started crashing. From the stacktrace, it appears to be related to the user dictionary, but I don't know much about Java, so I'm not sure.

I have tried asking on the CM forum, but haven't had any luck there, so I'm hoping maybe someone here can help me.

Here's the stack trace:

java.lang.UnsatisfieidLinkError: openNative
at com.android.inputmethod.latin.UserDictionary.OpenNative(Native Method)
at com.android.inputmethod.latin.NativeDictionary.open(NativeDictionary.java:50)
at com.android.inputmethod.latin.UserDictionary.<init>(UserDictionary.java:99)
at com.android.inputmethod.latin.latinIME.onCreate(LatinIME.java:369)
at com.binarybulge.android.apps.keyboard.KeyboardInputMethodService.onCreate(KeyboardInputMethodService.java:157)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2066)
at android.app.ActivityThread.access$2500(ActivityThread.java:123)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:993)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.activityThread.main(ActivityThread.java:3835)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
at dalvik.system.NativeStart.main(Native Method)

I've switched to using Swype for the time being, but I prefer Ultra Keyboard for several reasons and would like to go back to using it if possible. Any suggestions?
[Nexus S Q&A, Help & Troubleshooting] Oldiesmann:
No suggestions? Guess I'll move on to the developer and hope they can help.
[Omnia 7 General] egyfox85:
I have samsung omnia 7 16GB unbranded i bought it from expansys

and till now i didn't get Mango update

any one could help

Regards
[Omnia 7 General] Spookidoodles:
Lies and a different battery cover?

I dunno the whole system seems buggered - I have an 8GB "3" branded Omnia 7, and I received the updates the day it came out
[Omnia 7 General] JSSR:
Its getting rolled slowly, it can take up to 24 days to reach everyone. Google force update trick to get it to install faster
[Omnia 7 General] Sherwet:
Try the Unofficial Way

You probably won't get the update until a few weeks because it's still in the distribution phase which could, or could not, take forever.

There is a trick that everyone's been doing though:

1. Connect your phone to your PC and launch Zune.

2. Go to your phone's settings from there, and click the 'Update' tab.

3. Then click on any other tab, and once again click on the Update tab.

4. This is the tricky part...right after you click the 'Update' tab for the second time, wait exactly from 2 to 3 seconds and then disconnect your PC from internet. You must do that before you get the 'No Updates Found' screen.

If you suceed, you should wait for about 20 seconds and then you will find an available update.

5. Reconnect to the internet, start your update, and voila.
[Omnia 7 General] egyfox85:
thx for help

i try this unofficial way and it work with me and install the first update 7.0.4

but while installing 7.10 it give me error and the phone restart and stuck with samsung omnia 7 logo

i made hard reset for the phone it restore again to old software

but form this time every time i restart the phone it stuck with omnia 7 logo and i have to remove the battery and insert it again to load the os

any idea about this
[Omnia 7 General] liamhere:
strange, i have the same as you and are on three....no update for me???
[Omnia 7 General] 17-apg:
I have 16GB unlocked and unbranded version as well and i have no mango yet either. I read elsewhere here that if you do the "trick" download using Zune you don't get the proper update for the Omnai because there is a Samsung firmware update as well that is missing. I will wait for a few weeks max to see if I can get via Zune. Will let you know when I get it.
[Omnia 7 General] sallto:
@egyfox85:

Try to flash your device with a RTM ROM (or Nodo rom, but you cant use then the Chevron Jailbreak), because your Omnia 7 firmware is damaged.

Then try update to Mango..

Greetings.
[Omnia 7 General] Kash511:
I'm in a similar position as you where I have a 16gb Omnia 7. I actually forced my device but restored it back to NoDo soon after realising my firmware version was incorrect. I just hope me forcing it doesn't hinder my chance of getting Mango - does anyone know whether this could be an issue or not?
[Omnia 7 General] Starsyde:
I have an unbranded omnia 7 16gb from tmobile germany (no carrier branding shown when turned on the phone). I forced update to mango but received an error 80180048 and now I want to reflash it back to its original rom to re-do updates to nodo and just wait for offical release. Does anyone know what the original rom is?
[Omnia 7 General] batman222:
I was in the same situation. I made dozens of attempts to update, but only succeeded by reverting to a pre nodo rom, and allowing updates as far as Zune would go. After this, the phone updated all the way through to Mango using the network pull trick without issue. So if you are willing to wipe the phone completely, this might be the way.

I started at Samsung Omnia 7 Firmware XXJL3 Retail UK.
[Omnia 7 General] DMAND:
I've been using Mango since the day it first rolled out on my 16GB Omnia 7 from expansys UK.

Used the forced update, got the lastet OEM updated firmware with it too :)
[Omnia 7 General] egyfox85:
now my phone stuck at start up Omnia 7 logo and i reflash it with firmware	I8700XXKC1 after i finish it updated to 7.392 but also no mango

this should be UK rom

any idea about this too
[Omnia 7 General] 17-apg:
I put mine back to Nodo a few days ago and just got the official Mango via Zune today. Now, my details are:

OS 7.10.7720.68

FW 2424.11.3.1

HW 3.15.0.4

Radio SW 2424.11.7.2

Radio HW 0.0.0.800

Bootloader 5.8.1.0

Chip SOC 0.36.2.0
[Omnia 7 General] Kash511:
Nice one mate and congratulations (I'm jealous lol) - I'm checking mine everyday but have had no luck so far, guess I'll just have to be patient. Just for info, is your phone a German model, (mine is but its still unlocked/unbranded). I ordered mine from eBay assuming it was a UK model but it wasn't - it updated to NoDo fine a while back...
[Omnia 7 General] 17-apg:
yip, mine is a German model with 16GB (that's why I bought from there). But hey, horror stories.... I couldn't update NOW so I deleted it thinking that the old version was stopping the new version from downloading. Then I couldnt get it at all so I tried to go back to NODO and couldnt restore. Phone hung on the update connection . Reinstalled KC1 using WP7 installer and got back to NODO and did a force install (trick) to get back to Mango. And still I cannot update NOW; must be a Sammy problem. You should try the "force Zune trick" to get the Mango update pal..
[Omnia 7 General] drado:
Running 16 GB unbranded Omnia 7 purchased from ebay.de on Swisscom in CH and tried Zune update for 1/2 hour ago .... & got the regular update to Mango (not forced). Will post later if everything went well.... Regz from CH
[Omnia 7 General] Kash511:
Aaah,nah I already forced it and wasn't happy as the firmware was completely wrong, the reason I reverted back to NoDo was because of that issue. On a positive note, I sent a tweet to windowsphonehelp (or whatever they're called) and they responded back saying if you've forced it and go back to NoDo it shouldn't cause an issue - so, when Mango does officially come out for these handsets, I should get it with no issues. Here's hoping that happens sometime soon as I'm getting quite fed up - all my mates and even my brother are fully mango'd

---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------

Congratulations to you Drado, I'm extremely jealous. Here's hoping your update is the start of many updates to these handsets, especially mine lol
[Omnia 7 General] Freypal:
I'm on Mango final... no tricks at all just prompeted by my carrier.

OS 7.10.7720.68

FW 0222.11.8.5

HW 3.15.0.4

Radio SW 2424.11.7.2

Radio HW 0.0.0.800

Bootloader 5.8.1.9

Chip SOC 0.36.2.0

I've been having loads of issues with it. I had no problems whatsoever on NoDo.

Slooooow boot ups. (sometimes fast sometimes takes a couple of mins)

Sometimes if i switch it off and on it locks up and just displays the battery indicator. No home screen. (need to pull the battery)

Problems with the data connection dying requiring a soft reset of the phone to re-enable. (this is a MAJOR issue)

Started having bluetooth issues - it wont discover anything sometimes. (seems to work if i switch on WiFi as well. wtf?)

Info slow to appear on lock screen.

Keyboard closes itself randomly (known issue i see)

Really un-impressed with Mango. I've just hard reset my device so will see if that helps at all.
[Omnia 7 General] 17-apg:
For your info after the Zune tric install here are my stats!!

FW 2424.11.8.5

HW3.15.0.4

Radio SW 2424.11.7.2

Radio HW 0.0.0.800

Bootloader 5.8.1.9

So my specs are close to most others on here so I dont think I will force back to NODO to wait for official Mango. My phone is working 100% on every level right now so i will leave well enough alone for now!!

Let me know when you get the official release and your stats when installed.
[Omnia 7 General] manganoid:
Well, I forced Zune to get mango on my Omnia 7 about a week ago (unlocked, unbranded, was on chevron unlocked NoDo) and now my stats are:

OS: 7.10.7720.68

FW: 2424.11.8.7

HW: 3.15.0.4

Radio SW: 2424.11.7.2

Radio HW: 0.0.0.800

Bootloader: 5.8.2.5

Chip SOC: 0.36.2.0

Now, the issues I'm having are slower booting/powering on, deploying apps is waaaaay slower, issues with the Wifi router at work - I connect to the router O.K. my phone's MAC appears on the list, but I have no internet connection whatsoever (I used to connect no problem, and go to internet on NoDo).

Are my stats O.K? I'm asking because i see people here saying something about wrong firmwares etc.
[Omnia 7 General] Kash511:
Just got the official Mango update and it looks pretty different...

Guys,

Just got the official Mango update and it looks pretty different to what you all have, details are as follows:

OS Version: 7.10.7720.68

Firmware Revision Number: 2424.10.11.1

Hardware Revision Number: 3.15.0.4

Radio Software Version: 2424.11.2.2

Radio Hardware Version: 0.0.0.800

Bootloader Version: 5.2.1.4

Chip SOC Version: 0.36.2.0

I've only just had it for 5 mins so if I have any issues I'll let you all know.

Cheers,

Kash
[Omnia 7 General] nestavaro:
I have 16GB T-mobile Omnia.7, in Vietnam, and I did NOT get Mango update. It's Oct-25 now. OMG. Zune still says my phone (7392) was up2date. OMFG
[Omnia 7 General] chicagolive:
I have a 16gb T-Mobile Branded Omnia 7 my friend has a 16 unbranded. Tried all the tricks to no avail damn phone would not update. So we decided to flash are phones with the omnia 7 all providers firmware update(says nodo but it is really pre-nodo 7390 build took 5 minutes)I used the 02 csc plugged into zune and 45 minutes later I was at Mango, my friend had the same result and we also did it with 8 others much easier and quicker than all the other hassle and constant errors. One person had a problem but it was hardware related he never new it since his phone was already bought at nodo. Hope this help the folks who have been waiting.
[Omnia 7 General] Gerwa77:
Download the Patch from Samsung.com for Omnia7 and install it.

Reboot the Phone and then you can update to Mango.:)
[Omnia 7 General] mrrtt:
Could you please explain the process in more details? New with WP so I've no idea what's what, all I know is I forced Mango on my Omnia 7 and now it's stuck at 7403 with the infamous 80180048 error and it's driving me out of my skin.
[Omnia 7 General] unow:
I have not yet managed to do the update to 7392 because of the error cycle InFit to restart the phone ...

Is it possible to update from version 7390 to mango?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] MaliciousGod:
Hi all,

Looking for a little advice -- I've got a completely wiped (ie no data on the internal SD card) Galaxy Tab 10.1v that's stuck in a boot loop -- just continually cycles the first 'Galaxy Tab' logo again and again.

I'd ideally like to reset it to the stock Samsung 3.0.1 rom, but I can't get Odin to see the device.

I can happily get onto the Fastboot/Download mode screen, and Fastboot mode works fine (skitzandroid's recovery image from his rooting guide will let me get into basic recovery mode). However, switching to Download mode and checking with ADB for connected devices just yields a blank list -- ADB seemingly cannot find it, although it shows up in Windows Device Manager just fine.

I've confirmed ADB is working by plugging in my SGSII phone -- it's seen instantly.

I'm presuming that as ADB can't see the 10.1v, Odin can't either.

Does anyone have any advice on getting ADB to work?

Thanks!

------------------------------------------------------------------------------------

Scratch the above -- installed Kies and tried a bunch of different USB ports and that eventually fixed Odin's ability to detect the tablet. (It's worth noting that ADB still couldn't see it, however.)

Hope this helps anyone unfortunate enough to come across the same issue; I'm going to go clean the inside of my pants now.