yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] Compusmurf:
Other than different theme colors, what's the difference between this and the current 3.6.84.xxxxx beta released?

Oh, nvm. Found the info on their site.

--------

How is Nexus S 4G on Sprint Swype BETA different from the generic Swype beta?

There are 3 major differences:

Customized Sprint keyboard theme - Swype and Sprint worked together to develop a custom Swype keyboard design that matches the high-power experience of the Nexus S 4G on Sprint. This theme is ONLY available to Nexus S 4G on Sprint owners who participate in this Swype beta.

Secondary/symbol key layout - The Nexus S 4G on Sprint Swype Beta uses a slightly different keyboard layout design than most (but not all) of the generic Beta packages. It includes a Globe key, for quickly switching languages, and has several of the secondary symbol characters (the ones you get by long-pressing a key) in different places.

Languages - The generic Swype beta features support for languages that may still be in development for international users. For the Nexus S 4G on Sprint Swype Beta, we want to make sure you have a rock-solid, reliable experience, and so have limited this version to US English and Spanish only.

Are there any new features in this version of Swype?

Yes! The Nexus S 4G on Sprint Swype Beta is using version 3.25.91 of Swype, which is just now being released to the public for the first time.

Orig link:

http://sprint.swype.com/android/faq/
[HTC EVO 3D] CheesyNutz:
i would love for a dev to take a shot at porting that theme its sexy
[HTC EVO 3D] incarceration:
I love swype!

Currently I'm using Swype Beta on my 3VO, do you know if there are any other versions (newer) available?
[HTC EVO 3D] EricSS619:
I am really disliking the new swype beta.
[HTC EVO 3D] wrxlvr:
I wish they'd get rid of the globe (for switching languages). It's a dumb place to have it. Not enough people switch languages often enough for it to be a key on the keyboard. Put it in the menu.
[HTC EVO 3D] ch1naski:
No kidding. It's a really bad location for it. They would be better off just making the sym button bigger, since it gets used pretty often.

Nandroids are for sissies.

Bang.
[HTC EVO 3D] nhutpham:
Anyone try it out yet?

http://www.androidpolice.com/2011/0...-4g-now-available-for-rooted-android-devices/

I'm about to give installation a shot...
[HTC EVO 3D] nhutpham:
Sigh, it works and all, just there's bars on the side due to the screen resolution. You can still swype, it's just a smaller area to use.
[HTC EVO 3D] SayWhat10:
this thing been in beta for like 2 years
[HTC EVO 3D] jgalan14:
+1 Lmao for real they should just put it in the market and update it eventually instead of going thru the hassle
[HTC EVO 3D] Tachi91:
just got the new pre-release beta from an email... same old looking theme.. The one in the video looks so much nicer
[HTC EVO 3D] housry23:
Yeah the 3.25 beta has all the features of the NS4G build except for the skin. I'm hoping that someone will port that skin over for all devices.
[HTC EVO 3D] norm12:
Just downloaded the 3.25 version and it is nice. pretry fast and more accurate

Sent by Logo the turtle
[Galaxy S II Q&A, Help & Troubleshooting] Schindler33:
I changed the contacts.apk to a themed one. After rebooting my IMEI was completely gone. I could restore it somehow but it is no the generic IMEI 004999010640000

I could not find a solution for the S2. Has anybody an idea how how to restore my original IMEI.
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
Have you backed up your EFS folder?

If not you need to flash back to stock and send it back to samsung for reflashing, because as far as I know the IMEI is in there and cant be restored without a backup.
[Galaxy S II Q&A, Help & Troubleshooting] Schindler33:
No I did not back up the efs folder. Will there be any issues if I continue to use they phone with the generic

IMEI? Or should I send it back?
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
One it may give network problems as IMEI is part of the handshake process with the network .

Two you may find it impossible to prove ownership of the phone

Three you may not be able to block it if stolen .

Four Some countries its illegal to alter the IMEI code .

jje
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
Does the phone work, and make calls and send texts? If so it should be ok

But its technically illegal to change your IMEI in most country's.

I am surprised the generic IEMI isn't blocked on your carriers network

Also if your phone gets stolen or lost you wont be able to get it traced via IEMI or blocked.
[Galaxy S II Q&A, Help & Troubleshooting] thegza83:
how did you get generic imei to go on your sgs2 i hyave same problem flashed rom now having problems making calls ect ??

:mad:
[Galaxy S II Q&A, Help & Troubleshooting] hgroove:
Try this....

http://xdaforums.com/showthread.php?t=1264021&highlight=recovery+IMEI

This save my day

Hgroove4
[Samsung Galaxy S (4G Model)] ryan8440:
I installed the update.zip file and the recovery file. I rebooted into recovery and selected reinstall packages. CWM then loaded. Yay.

When I went to go back into CWM and found that it booted into Samsung Recovery again. I selected reinstall packages and got into CWM again.

Is this the expected behavior? Meaning, does it boot to samsung recovery each time?

I'm running a completely stock GS4G other than rooting. Running T959VUVKD1.

Sorry for the n00b question and thanks to all the developers, there's some really great stuff out there.

Thanks,

Ryan
[Samsung Galaxy S (4G Model)] FBis251:
Try to Odin this:

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

You'll get a permanent CWM recovery.
[Samsung Galaxy S (4G Model)] jager555:
Yea, flash bali 3.3uv with odin out cwm and that won't happen anymore
[Samsung Galaxy S (4G Model)] ryan8440:
The "uv" stands for undervolted. Is there a manual I can read so I know what I'm getting myself into?

Thanks again,

Ryan
[Samsung Galaxy S (4G Model)] FBis251:
Not quite a manual, but this is the original thread for Bali

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

Gives you features and such. If you don't want to undervolt your processor (understandable) there's a non-UV version available.
[Samsung Galaxy S (4G Model)] jager555:
yea. if you want to overclock, i would recommend the uv. if not, then go with the normal. uv saves you a bit of battery. there is no correct choice. all up to personal preference
[Verizon Droid Incredible 2] shoman24v:
Get it here - Credit to XsMagical

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

I'm on RMK's debloated ROM and it seems to work ok.

Be sure you backup your device in the event this doesn't work.
[Fascinate Q&A, Help & Troubleshooting] Kidd_Funkadelic:
I just changed from an earlier debloated version of the stock verizon ROM to power washed w/ the stock updated ED05 kernel. Since then I noticed that attempts to disable the keyguard (puzzle lock screen) are ignored. I had both a tasker task to turn on the screen and unlock automatically when plugged in, as well as a switchpro widget that turns off the keyguard, and neither of them are functional anymore.

Any help?

Thanks.

Kidd_Funkadelic

Update: Also, the quick reply functionality of chomp no longer works. It seems nothing can unlock my screen now?
[Captivate Q&A, Help & Troubleshooting] b-eock:
Is there a way to mod the 3e recovery like there was for 2.2?

Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
[Captivate Q&A, Help & Troubleshooting] studacris:
Flash a kernel with cwm cooked in like the cognition beta 2 kernel if you are refering to kf1...
[Captivate Q&A, Help & Troubleshooting] b-eock:
Cog kerel just makes it bootloop

Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
[HTC Sensation] cromozone:
Apologies if this has been answered already elsewhere, but I've searched all the Sensation forums and can't find anything like this, so here goes...

I got a Vodafone UK Sensation at the beginning of July. The only 'bug' I noticed was that even if MMS Delivery Reports were ticked in the message settings, I didn't receive any delivery report (SMS delivery reports worked fine). I thought this was odd as MMS reports used to work fine on the Desire.

After this I rooted the phone and flashed to the most up to date (at that time) standard European HTC ROM using RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed and I found that MMS delivery reports were working perfectly.

Now since the 2.3.4 update came out, I decided to move over to InsertCoin 2.2.2 which is based on the 2.3.4 update. Everything is perfect, apart from that MMS delivery reports are no longer working regardless of the settings.

Has anyone else had any problems with delivery reports for MMS, and if so is there a way to fix it?

Thanks in advance!
[Eee Pad Transformer Android Development] rothnic:
Context: [DEV] Touchwiz for Transformer - xda-developers This was moved because there were no files to test.

What is this? This is based on Prime 1.6. All the samsung galaxy tab 10.1 specific files that run UX have been merged in. Then I decompiled the framework for both the TF and GT10.1, and merged in functionality into the TF framework. It has come a long way, and the launcher is usable. However, the statusbar does not come up because systemui.apk FC's.

PrimeUX: Download THIS IS NOT USABLE YET, PEOPLE WHO EDIT SMALI ONLY

You will get FC's from systemui, media, and myfiles. Media and myfiles could be avoided by leaving out more of the samsung files that fguy did not include in his. I assume it is because of the FC's.

This is meant for others to work on the systemui issue, not for any real use.

Porting Process:

Here was what I was using to decompile the framework. Drop all the files into the framework directory, then run decompile.bat and it'll all go into respective folders under an out folder. Then you can do this to the samsung framework, then diff them with winmerge or something like that.

When you find an error in logcat, search for a term related to it within Notepad++'s search in files feature. Generally, this will point you into the direction of a missing class. Then you can copy the class over into the associated TF framework file by right clicking on the highlighted missing class within Winmerge. However, sometimes it isn't so easy because Samsung and Asus have heavily modified the HC framework. Asus to add the dock functionality, samsung for the touchwiz stuff.

Tools: Decompile Framework
[Eee Pad Transformer Android Development] Gtj94:
Good to see this happening! :D quick question, there isn't any resizing needing to done yea? Just smali edits?
[Eee Pad Transformer Android Development] rothnic:
I guess I'm unsure what you mean by resizing.

Currently it is at a point where more merging needs to happen(i think) to get the mini apps working. The systemui.apk has a major dependency on the mini apps working, so it crashes without them working.

The main problem I have is there is a FC by systemui, pointing to the mini apps as the problem. However, there is no way to find out why the mini apps aren't running. So, I don't know if more framework porting needs to happen, or what.
[Eee Pad Transformer Android Development] Roach2010:
Hey rothnic. Great work so far. I don't envy you task of trying to merge the frameworks but you have my full support. I'm no smali expert by any means but I'll help out if I can.

I suggest keeping a healthy supply of beer at hand as smali editing drives me to drink :p
[Eee Pad Transformer Android Development] stitoo:
Ported going to interface with applications such keyboard? I do not like asus keyboard:mad:
[Eee Pad Transformer Android Development] rothnic:
Yeah, not the most fun stuff in the world. Was going to get around to touching base with you if I ever get it working. I'll package it up as a delta so it's not a full on release to manage. If there is a way to get it working, I hope to document the changes I made so it could be applied to TF updates as they come out.

If it works, I'll probably alter Prime 1.6 as little as possible. Have you tried Thumb Keyboard from the market? Worth the cost.
[Eee Pad Transformer Android Development] dwillMUFC:
Just comparing smali files and in "smali\com\android\systemui\statusbar\tablet" the TableyStatusBar$H file in the Prime UX, when compared to the A500 UX rom exact file. There are many differences between the two. Now Myself have only done minimal smali editing. However I was just wondering if this has already been looked at and/or whether they theoretically should be the same?

Thanks

Dan
[Eee Pad Transformer Android Development] rothnic:
I started using the A500 UX version of systemui.apk. I had the errors that we still have now. But, I thought maybe the version that Fguy used for the Acer might not work well with this specific implementation of honeycomb. So I tried a newer version of the samsung UX files, but it had no impact.

So that is why you would find differences between the one in PrimeUX versus Fguy's ROM. I tried talking to him about it, but I think the language barrier is too great to really communicate well enough.

I'm not sure if he added anything to the SystemUI.apk or not, but my intuition was that the changes were mainly to the framework files. That is a consideration to make, though.
[Eee Pad Transformer Android Development] nicknowsky:
this is great, I was wondering if and when we were gonna see this ported. Its great to see the DEV'n really starting to take off!!
[Eee Pad Transformer Android Development] br13an:
Why are you guys concetrating on the keyboard so much for this port, it just gives extra unneeded problems with it, maybe it's a better thing to leave the keyboard as it is for now, i guess that can take alot of headaches away,
[Eee Pad Transformer Android Development] rothnic:
We, as in the people trying to get this to work, aren't messing with the keyboard at all. One person had a hard to understand comment about the keyboard, and I was just being a nice person about an off topic comment.

The keyboard is definitely the last of my worries.
[Eee Pad Transformer Android Development] nex7er:
Okay, so I thought I'd take a look at what is causing the systemui to crash, but upon decompiling in apkmanager I am getting an error. I've done the menuitem 9 and 10 (with both frameworkres and twframeworkres).

I DO get Smali files to edit, but the errors make me not want to try to recompile and put them in there, lol.
[Eee Pad Transformer Android Development] jcarrz1:
Take some courage, try it :P

I've had luck despite errors (although unlikely).
[Eee Pad Transformer Android Development] nex7er:
Well, I'm at another stop. I was going to use files from a real Galaxy Tab rom to see what differences there are. Perhaps the OP missed something (obv). I can't seem to decompile them. Not even giving me any smali folder. Hmm.

This would be a lot easier if OP listed all the files he has edited to add functions from normal prime 1.6 smali files. If not, I might as well have to start all over just so I'll know what files to edit and which not to. When Winmerge lists a different item, how am I supposed to know it's really just an identical file with some added Asus bonus without checking every single file? :p
[Eee Pad Transformer Android Development] nex7er:
Is anyone able to decode what this exception is? Doing some merges and running logcat while booting, this one comes up (untouched PRIMEUX.zip, just flashed back to the stock zip in OP).
[Eee Pad Transformer Android Development] rothnic:
What are you using to decompile? Also, I havn't had much luck compiling apk's, so if anyone knows for sure how, let me know. I can decompile/compile framework files just fine with the files I posted.

Not sure what you mean by from a real Galaxy Tab rom. I used the files from Fguy's Iconia port at first, then a stock deodexed samsung ROM. I had the same problem I still have, but PrimeUX that I uploaded has untouched samsung applications (everything that goes in /app). I have merged classes from samsung to asus framework files: android.policy.jar, framework.jar, and framework-res.apk. All those errors were related to missing classes, so I merged them.

So what I'm saying is, it doesn't really matter what has already been merged, because those classes now exist. I have approached it by decompiling frameworks from samsung or fguy's rom and prime 1.6. Then i diff them, and then all you can do is use winmerge to let you know if they are different or not. If a file looks like it could have something to do with the status bar etc, then you can double click on that file and winmerge shows a side by side view where you can see the differences and merge lines or not.

This works isn't a clean, let me see which files are different so i can copy them around. It requires digging into each and every class file in the framework to see if something needs to be merged. Also, when you use different ROMs for the touchwiz files, many of the files will differ, so be careful there when mixing stuff.

I'm not sure on that one, but my guess is something went wrong when they deodexed the file. I tried replacing these files from different ROMs, including Fguy's and it always showed that error. I'm thinking maybe it's not a critical error and it still functions since those others work fine.
[Eee Pad Transformer Android Development] rothnic:
I'm pretty sure those line references won't be an issue. It is more to do with things like Environment.smali from android.policy.jar. It has overlapping capability that looks very hard to merge.

Also, about not knowing what are errors. You will see a lot of red stuff coming from samsung related files. A lot of it is just samsung printing out debug information, but for some reason they print them like exceptions. They did this a lot when I was porting the original galaxy tab's email app to the Gtablet. The main issue is the one you pasted. That is all that is given, and it doesn't really tell you much.

I'll try to post later today which samsung ROM I was using. I think it might have been the deodexed one from here: http://xdaforums.com/showthread.php?t=1198921 . I'll find out for sure.
[Eee Pad Transformer Android Development] nex7er:
Good stuff. Yeah I've been using that one as well. Right now I am going over services.jar and comparing with omftab and the primeux service.jar is missing a bit. Including one that has to do with TW, apparently.

Differences like this " const v1, 0x10402d3" are all over. I have no idea what they are, but I'm going to guess I'm not to touch these even if they differ?

EDIT ADD: Without having looked much further (just started again), I came upon errors pertaining to GsmSignalBar, referenced from systemui. Could this be what causes the SystemUI.apk to not launch itself?

08-23 01:14:07.570: WARN/dalvikvm(1113): VFY: unable to resolve virtual method 441: Landroid/telephony/SignalStrength;.getGsmSignalBar ()I

Hmm, now to decide to take time to check this out or try something else. Really hard when you're alone and not working as a team on several parts. :p

EDIT ADD 2: Hmm, at some point, it IS launching the statusbar without crashing. It's not until later when that errormsg I pasted a few posts up, that it disappears. The remaining errors between it loading and the crashing are all related to phone stuff. Here's a full paste from when it loads till it crashes and starts doing other stuff: http://pastebin.com/4AnEX6kq

08-23 01:14:07.440: DEBUG/SystemUIService(1113): loading: class com.android.systemui.statusbar.tablet.TabletStatusBar
08-23 01:14:07.490: DEBUG/SystemUIService(1113): running: com.android.systemui.statusbar.tablet.TabletStatusBar@4049d9b0
[Eee Pad Transformer Android Development] rothnic:
Not sure what the deal is with the getGsmSignalBar, because that didn't even have to be merged. It was already within framework.jar.

Try this services.jar, I did find something in there critical to the status bar and fixed it:

http://www.multiupload.com/3Q2WD076XI

I'm not setup atm to test. The wife has been needing the tablet and I've been working on the car. However, I should be free to work on this, this afternoon.
[Eee Pad Transformer Android Development] nex7er:
Just woke up and the first thing I see is having to nandroid again and try something new out. I just got done spending six hours on it and having a break consisting of making a new lock screen and some sleep. :)

Give me a few minutes and I'll report back. Nandroid takes its time.

Oh, and another thing, what is the main difference between Prime 16r2 and PrimeUX? I mean, did you just copy and paste all the apks the other files that the Samsung had that EEE didn't, then merge classes from framework.jar, framework-res.jar, services.jar and android.policy.jar? Or is there more?

It's been bugging me out how the launcher works "fine" (lack of sensor) in the A500 roms when installed on the TF101. I wonder how they managed that. While looking at that Systemui error that points to a ****load of smali files, I can't help but scratch my head. The systemui is 100% like the XKFC build (why not use a newer rom with more fixes, new home button and new browser?) so I wonder how the hell it's not working. I've tried using frameworkfiles from omftab 1.0.5 but nada.

I might not have touched smali files but I'll be damned if it it's not intriguing to see how things work by being called upon. :p
[Eee Pad Transformer Android Development] rothnic:
Yeah, so PrimeUX will be an overlay on top of Prime 1.6. It was a collection of apk's, framework files that don't exist in Prime(samsung specific), and libs(samsung specific). Then I did merging on the .jar files I mentioned, and included those.

What do you mean by works fine on the TF? I thought it stated that the Iconia port doesn't have Launcher rotation with the sensor? Or is that what you are saying? The rotation problem is in the framework files, not the launcher2.apk. I've tried to avoid those framework classes so far so we don't have the rotation issue. The reason the Acer port works on the TF is because it includes the Acer framework files that have samsung classes merged in. I tried comparing the original Acer build to his merged build to see if I could pinpoint the changes he made, and thought I got them all. Obviously I didn't, so I'll take another try at that.

Are you saying why don't I use a newer build, or that why doesn't the guy who ported to the Acer? I'm not too worried about which build I use because most likely the framework merges will not change significantly between them. I started with Fguy's build(which is based of an older build than I used), thinking he might have modified some of the samsung files. I do plan to get the latest stuff working if we ever do get it up and running.

BTW, I only ever use Asus core android framework files. The only framework files I took from samsung were the obviously missing ones.
[Eee Pad Transformer Android Development] nex7er:
Alright, was just wondering what you did to complete this.

I meant that it works fine sans sensors. What I think would be a better idea is use the exact same samsung rom he used while merging, and then merge them just like they are in his/their rom. Yes, even the rotational issue. This way, if it's now just the iconia rom but built by you so you can use your own name for it, try to fix the sensorissue from there? Much easier to get it working, even if with a few issues, and fix the issues later on. Seeing as how rotation works here, that shouldn't take too long. I think. :p

I was asking why we don't use a newer build? I've gone looking over the classes with the latest TouchWIZ rom and there are too many differences for me to not go bananas.

That services.jar didn't help. Btw, the tools delete the META-INF with certificates, so when you're done compiling the .JAR/APK files, open both the unmodded and modded .jar/.apk file and drag the META-INF from the unmodded over to the modded. That way you don't have to go through certification-errors, if they matter.

EDIT ADD: Also, I'm pretty sure the android.process.media crash relates to the files wanting to mount an sd-card somewhere it shouldn't be (the samsung mounts them differently). I think if we fix that, we can stop that crash and get at least the apps working.