yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] nenol:
**Disclaimer: I realize that I am a *noob*. I flashed my original G1 to Cyanogen, upgraded my Vibrant to Team Whiskey, and my HD2 to Cyanogen 7. However, compared to many of you, this is insignificant. This is why I seek your help**

I installed Typhoon CM7 to my HD2 today using the directions given. The phone responded well at first, and I was able to install most of my apps back immediately. Due to commitments, I was unable to finish installing all apps I use regularly. Later tonight, I tried to install Google Maps - no dice. When I select it from the Market, I see a down arrow for a second, then nothing - it does not install. I have found that I am able to install other apps (ie Google Books) but not Maps. As an added note, it appears that I cannot install random apps - Angry Birds, for example - but some are fine - Gun Bros. There does not seem to be any logic to it.

I tried to use ROM Manager to boot to the Clockwork Recovery to reflash the ROM, but when I try, MAGLDR autoboots the OS (GO GO GO!). If I try to reboot holding volume down, I get to HSPL. I cannot seem to get to MAGLDR or Clockwork Recovery.

Because of this, I don't know how to proceed. I would be inclined to reflash the the ROM, but I can't seem to find a way to do so. I don't have a use for a ROM that randomly won't let me download (commonly used) apps, so I am open to switching to another ROM. However, as I can't find too much information on this problem, I suspect that it's a random glitch and not a ROM issue.

Does anyone have advice on booting to MAGLDR? Or on how to resolve the market issue? I have tried to use the 'Bad Behavior' reporting to report a 'WTF condition' but the button doesn't do anything. I really appreciate your help, and understand the urge to immediately direct me elsewhere, but I hope that somebody takes the time to provide details. As such, I am willing to help / provide as many details as possible to help solve this!
[Desire Q&A, Help & Troubleshooting] nenol:
Update: I did some reading, and found that holding the power button through the MAGLDR screen gives me options - Hurray! I am now trying to reflash the ROM and will soon update whether I am successful. I would say 'stay tuned', but hey, it's my problem, so hopefully I can close this soon without needing any expert advice.
[Desire Q&A, Help & Troubleshooting] nenol:
Screw it! I installed another ROM - this seems to have solved my problem. Hurray for fixed problems! Case: closed.
[Touch GSM General] thinman873:
I need the original HTC Elfin ROM. I'm based in India. can anyone please tell me where to download the original HTC Elfin ROM for India? also, I've installed a custom ROM on my elfin. Do I need to do anything before installing the original ROM?
[Touch GSM General] tito12:
look here, article 10 : http://xdaforums.com/showpost.php?p=2443038&postcount=3

Not if you haven't Hspl (hard spl will prevent original rom from installing)
[Vibrant Android Development] s0niqu3:
Hey everyone,

I guess this can be considered my "random act of kindness" for the year since I know that it will almost certainly be kanged over and over with out thanks/credit given.

Anyway I just figured out how to display the "H" icon in the status bar properly. And by that I mean, no renaming or duplicating drawable files in framework-res.apk, and the icon will show all data states now:

GSM, GPRS, Edge, 3G, HSDPA

I've only tested it for a few minutes myself, but thankfully the signal in my bedroom can be a bit flaky, so I've seen it bounce between 3G and H already, and I disabled 3g to make sure the "E" for edge still works fine too.

Anyway, decompile services.jar, and open /com/android/server/status/StatusBarPolicy.smali

Then search for ".method private final updateDataNetType(I)V" in and replace the entire method with this:

.method private final updateDataNetType(I)V
.registers 3
.parameter "net"

.prologue
.line 1381
packed-switch p1, :pswitch_data_30

.line 1409
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_g:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

.line 1412
:goto_7
return-void

.line 1383
:pswitch_8
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_e:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

goto :goto_7

.line 1386
:pswitch_d
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_3g:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

goto :goto_7

.line 1391
:pswitch_12
iget-boolean v0, p0, Lcom/android/server/status/StatusBarPolicy;->mHspaDataDistinguishable:Z

if-eqz v0, :cond_1b

.line 1392
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_h:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

goto :goto_7

.line 1394
:cond_1b
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_3g:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

goto :goto_7

.line 1399
:pswitch_20
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_1x:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

goto :goto_7

.line 1402
:pswitch_25
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_1x:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

goto :goto_7

.line 1406
:pswitch_2a
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_3g:[I

iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I

goto :goto_7

.line 1381
nop

:pswitch_data_30
.packed-switch 0x2
:pswitch_8
:pswitch_d
:pswitch_20
:pswitch_2a
:pswitch_2a
:pswitch_25
:pswitch_12
:pswitch_12
:pswitch_12
.end packed-switch
.end method

And if you haven't noticed by now, I HATE this samsung bs and would kill for an AOSP or CM rom, lol.

Cheers, =)

P.S., next up (hopefully) a user selectable setting to hide the AM/PM flag from the status bar clock.
[Vibrant Android Development] Romanbb:
Wow nicely done. Thank you so much!
[Vibrant Android Development] ndwgs:
Great find, sonique!

And yes, I agree, need aosp or cm already!

Sent from my SGH-T959
[Vibrant Android Development] treyvaporizer:
I would LOVE you to find that am and pm removal! If this is any help, the 24 hour format doesn't use am/pm (obviously lol) but I wonder if there is any code on there to help you find out how to turn it off for the 12 hour format. No idea if thays right at all, just an idea:-) I would do it myself but I don't know how to

Sent from Bionix powered vibrant! If I helped, hit the thanks button!
[Vibrant Android Development] Whitehawkx:
It's unfortunate that's how it is S0niqu3, but definitely true.

Thanks for figuring this out and posting it here for everyone.
[Vibrant Android Development] dasunsrule32:
Is there a tutorial on how to decompile/recompile jar files? I want to learn how to do these edits.
[Vibrant Android Development] Romanbb:
for editing code like this, you need to download smali/baksmali jars. Then you'll need to pull out the classes.dex file out of said jar file (services.jar in this case, you can just open the apk with 7zip). I found this post to be a good reference for decompile/compile commands. Decompile. Do edits. Compile. Replace classes.dex in the jar file with the new one.

I can *try* and help you some more if you like... I'm no pro at this :)
[Vibrant Android Development] dasunsrule32:
I will take a look at this info. Appreciated. :) Worked perfectly! Thanks dudes!
[Vibrant Android Development] eugene373:
Awesome work Man... But not sure If I agree with the first part of the sentence.

My Stuff is Kanged all the Time & I don't mind to be honest.
[Vibrant Android Development] dasunsrule32:
I already have the services.jar edited and working on gingerclone r2, do you want it?
[Vibrant Android Development] eugene373:
You can release it if you want, I never felt the need for this...
[Vibrant Android Development] s0niqu3:
Hey Eugene,

Thanks for the compliment =)

And yeah, I was a little bitter the night I released this, lol.

But yeah, I don't honestly much care about people "kanging" unless its my theme work, re-drawing graphics from scratch sucks, a lot, so credit is very much appreciated in that area. =)

Thanks for all the hard work you do, any chance you can send me some tips on replacing the touchwiz dialer and contacts? I know you managed that on 2.1 with your Hybrid rom's, and I'd love to have them back on froyo, and I don't mind doing the work myself.

Cheers, =)
[Vibrant Android Development] dasunsrule32:
Ok, I will drop on the ginger thread. :)
[Vibrant Android Development] drhonk:
Awesome work as always s0niqu3 .. greatly appreciated. I've created a flashable of this MOD for KB1 ... I don't know if the same file work with other release or not. This will hopefully help somebody to get it installed easier. :)

- KB1 H-icon StatusBar MOD

- KB1 Original StatusBar
[Vibrant Android Development] dasunsrule32:
I put together two services.jar's, one includes the H hack and one includes the H hack + the AM/PM hack, for a genuinely Ginger feel. :) Enjoy!

Click Me
[Vibrant Android Development] eugene373:
LMAO! Oh trust me, I do understand aa bitter stand point..

But yeah I'll look into the Dailer / Contacts once I get my Dev machine back up and running & send ( DM ) you what I did in 2.1 but I've not tried 2.2 yet so Def. would like to help in anyway that I can..

P.S.

Regarding my Statement, I hope it wasn't taken out of context :D

as that's truly not how it was suppose to come across.

~Eugene
[Vibrant Android Development] krackers:
Will it work on KA6
[Vibrant Android Development] tjsynkral:
I posted a fix for this as a patch on top of the Fascinate lockscreen mod last month here: http://xdaforums.com/showpost.php?p=10951625&postcount=44

For those who don't feel like doing all the legwork.
[Vibrant Android Development] s0niqu3:
Hi,

Do you mean you added this to the lockscreen mod, or you found something wrong with the code?

If you simply added it to the mod, would you mind at least linking back to this thread for credit in your post?

And if you found a bug, would you please share the fix so I can update the OP here.

Cheers, =)
[Vibrant Android Development] MikeyMike01:
Absolutely.

I don't give a **** when people use the Home Haptic feedback that I figured out for Captivate, but when people start stealing my theme it pisses me off.
[Vibrant Android Development] tjsynkral:
It's flashable on top of the lockscreen mods since the services.jar is already modified in those mods - flashing a clean services.jar would undo it.

I posted that 15 days before you started this thread so I don't think I owe you any credit. :)
[Vibrant Android Development] s0niqu3:
Sorry about that, I didn't even look at the dates when you linked, just briefly saw the thread title and then closed the page.

Absolute honesty, I never saw your post, and figured this out on my own while first starting to work on porting some mods from CM to the vibrant.

So I guess grats on figuring this out before I did.

Cheers, :-)
[Vibrant Android Development] BruceElliott:
Jocelyn,

Forgive my ignorance, but does "H" in your indicators (ref: OP) mean HSDPA+? (Because HSDPA is 3G.)

HSDPA: Connection utilizes up to 16-QAM modulation to provide speeds from 900 kbps to 14.4 mbps. (T-Mobile calls this "3G.")

HSDPA+/HSPA+: Connection utilizes 64-QAM modulation to provide speeds of 17.6 mpbs and above. (T-Mobile calls this "4G.")

(Note that "3G" and "4G" are not defined in standards; they are merely marketing terms.)

I would really like to know the answer to this question; because it would be very handy to know, at any particular time, whether I am on an HSDPA connection (which stock Vibrant shows as "3G") or on an HSDPA+ (aka HSPA+) link operating in legacy (HSDPA) mode with the Vibrant (since the Vibrant is not capable of HSDPA+ operation due to its HSDPA-only decoder chipset).

Thanks,

Bruce
[Vibrant Android Development] s0niqu3:
Hi,

I'm honestly not sure how android is differentiating between displaying the 3G and H icons.

In the case of this mod, I didn't do anything new that android doesn't natively do, so you'd need to pull the android source code to see how its deciding when to show 3G v H icons.

What this mod does, is remove a ton of (ridiculously unnecessary) checks against the phone's internal model numbers (t759, t959, t959v, etc.) to allow it to display the "H" icon the way normal, AOSP android does.

Ironically, there's a setting, by default, built into android to turn off the H icon (its compiled into framework-res.apk "config_hspa_data_distinguishable" boolean, true or false.) I'll never understand why t-mobile/samsung decided to modify code to hide the icon, instead of setting a preference.

So anyway, my best guess? I'm guessing that t-mobile is only broadcasting that their HSPA+ capable towers qualify for the "H" to be displayed for the case of android's data icons. This is purely conjecture though, based on my geographic location (southern california, los angeles metro area) where HSPA+ is largely available, but just passing through some suburbs, etc., my phone will display 3G instead of the H icon.

Anyway, sorry I don't have an official answer for you, you might have fun pulling the source code and seeing if you find anything.

Hope that helps though.

Cheers, =)
[Vibrant Android Development] BruceElliott:
Yes, that does help; thanks. I am a non-programming engineer; so the source code would represent a learning curve that I do not have time for. But I believe that your "best guess" is correct. What else could cause the icon state to change?

As to why Samsung/T-Mobile would hide that state...to avoid confusion on the part of a non-technical subscriber who sees the "H" and then complains that his phone recognizes (and therefor should be capable of) HSPA+ operation but does not attain speeds exceeding 7.2 mbps. (The subscriber not realizing that his phone can operate on an HSPA+ network in a downgraded "legacy" mode.)

Anyway, thanks; differentiating between networks will be useful to me!

Edit: As to why to use the "model number" code rather than the Android preference...the former method is more global in the sense that they avoid having to worry about which state the switch should be in every time they compile a code module that may be applicable to various models.
[Vibrant Android Development] tjsynkral:
When I was going through the services.jar code I remember seeing that the original code was set up for UMTS and HSPA connections to show as "3G" on the Vibrant and "4G" (not "H") on the GS4G, without regard to whether HSDPA>7.2 is actually connected. It was based on the phone's model number string.

In other words, they might as well have just replaced the 3G icon with a 4G icon, because it will show even when you only have 3G speeds available. (But they may have corrected this on the final GS4G rom, I'm just going off what I saw for GS4G model numbers in the Vibrant services.jar...)
[Vibrant Android Development] s0niqu3:
Yeah, I saw all that in the Vibrant code too.

The SGS4G code is almost completely different, no model-checking at all, but instead, checking for roaming state every step of the way.

Regardless, I thought using either code was a bit absurd, so I used the AOSP code for the method in this post to remove their excess checking.

Cheers, =)
[Vibrant Android Development] BruceElliott:
+1

Bruce
[Vibrant Android Development] Binary100100:
I edited it for TeamWhiskey's Bionix 1.3.1.

By itself it's useless since the rom has "H" even for the 3G connections but it might be useful for the themers out there.

Please make a backup prior to flashing by CWM because I haven't received my phone back from Samsung Warranty to test it for myself.

If you use this in a theme and this works please credit me.

Thanks!

EDIT:

Verified that it works for 1.3.1
[Droid Eris Q&A, Help & Troubleshooting] labnjab:
I have been talking this over with Condemned Soul but wanted to see if anyone else has ran into this problem since he & I are both confused.

My fiances phone has been force closing a lot lately aka com.android phone not responding. I saw the first force close when I tried flashing Tazzs cm7 on his phone so thats when I first put on gsb 1.2

I switched his over to Sheds GSB on the 8th and it was great everything was fine but then I decided to try to improve on a few settings and when I restarted the phone it decided to start force closing.

I reflashed the rom and the gapps and everything seemed fine but then I wanted to put cs skull theme on his phpne since we had it on Kaos v9 but then when I restarted the phone after flashing the theme it force closed again.

So then I reflashed the rom and gapps again and got all his apps and settings all back how he had it and decided to do a Nandbackup so that we wouldnt have to keep reflashing the rom again and once I restarted the phone after the nandbackup it force closed again.

Long story short I reflashed the rom and gapps and now am in the process of getting his apps and settings back how he had it once again.

Am I doing something wrong to make it keep force closing? I would like to make a nandbackup at least for him so that we wont have to keep setting up his phone.

Thank you for any help
[Droid Eris Q&A, Help & Troubleshooting] Pokelover980:
When you say you flash the ROMs, do you also do a wipe beforehand? If not, try doing a wipe and then install and see if that changes anything.
[Droid Eris Q&A, Help & Troubleshooting] labnjab:
Yes I wiped both the factory and dalvk sorry I thought I mentioned that. lol.
[Droid Eris Q&A, Help & Troubleshooting] zerocool79346:
Its a problem that happens on certain ROMs with certain themes. Not sure there's a fix for it, I just got around it by not applying the phone.apk theme.
[Droid Eris Q&A, Help & Troubleshooting] CondemnedSoul:
phone.apk wasn't changed in the theme. Strange part is it's only on the one phone and haven't heard of it on any of the others.
[Droid Eris Q&A, Help & Troubleshooting] zerocool79346:
That is odd.
[Droid Eris Q&A, Help & Troubleshooting] labnjab:
Update:

This is still causing issues. Going to try and format the sd like tazz suggested, but moving my phone.apk to his didnt work, and yesterday he had to restart his phone and it did it again and needlessto say hes not very happy with his phone. Says its not reliable at all. If anyone else has anything else I can try it would be a big help. I have tried searching on google but dont find a whole lot of information. I just wish I could figure this out its got to be something I did or something stupid that I am missing.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
There are a couple of next steps you can take.

If the problem is a software configuration issue, then it is possible that you will see the reason for the FC in the logcat.

The system logcat is designed as a "circular buffer" (in a way that it has a maximum size) - once you fill it to capacity, each new record which is added to the end causes information at the beginning to be lost. But, this also means that if a FC occurs, so long as you "dump the logcat" within a reasonable period of time after the FC happens, you will capture the moment in time that the FC occurred,

Generally, the "logcat" buffers get filled to capacity quite quickly at boot time (because there is lots and lots of "android" app activity), and quite a bit slower after the phone has been completely booted. If you are trying to capture a logcat event during the first boot, you need to continuously capture output to a file on your PC (it will be quite large) - but once the phone has completed booting, so long as you "run a logcat" within 5 or 10 minutes after a FC occurs, the relevant event(s) will be in the logcat.

If you want to capture it during the first boot cycle of a freshly flashed ROM, probably you ought to have a PC attached and dump the prodigious output to a file on the PC, as in

C:\MyWindozePC> adb shell logcat -v time > LogcatFileOnMyPC.txt

So long as the ROM you have flashed has "USB debugging" turned on by default, you can run the above command about 10-15 seconds after you see the 3 skating droids, and it will continuously place output into the local file on your PC. You need to interrupt the above command (Control-C) to get it to stop; you would usually do that a few seconds after you saw the FC, and then you would know that the log entries you are looking for at the end of the file.

(Note that logcat dumps are usually huge - don't bother trying to look at them with a text file viewer on the phone - they suck at handling large files... well, at least the ones that I have tried).

You could also instrument this on the BF's phone in a way where he can capture the info to the SD card anytime he is using the phone during the day with a couple taps of the screen, and then you could look at the logcat(s) later at your leisure - for instance by using Gscript Lite, and a simple script like this:

#! /system/bin/sh
_LOGDIR='/sdcard/logcats'

if [ ! -d ${_LOGDIR} ]; then
mkdir ${_LOGDIR}
fi

_tstamp=`date +%Y%m%d-%H%M`
logcat -v time -d > ${_LOGDIR}/logcat_${_tstamp}.txt

With this method, you just need to train him like a monkey to press the right keys after a FC occurs. If he's a clever monkey, you could even train him to send the logcat files to you via e-mail. :)

If the problem is due to an intermittent hardware issue with the phone, that will be tougher to identify. About the best you can do to make that determination is to return the phone software to stock and use the phone without installing any apps for a reasonable period of time and see if the problem continues to occur.

cheers

bftb0
[Droid Eris Q&A, Help & Troubleshooting] labnjab:
Thank you for the detailed reply bfbt0 I was about to msg you when you responded.

I will have to give what you mentioned a try.

Is the gscript lite what I use for the adb shells or do I need another app as well. I have never done anything with adb or if I have it was something simple.

To clarify I would have to get his phone to fc again which is easy to do and then run a logcat. It sounds easy through the pc I just want to make sure I do it right. I would make a folder dedicated to where the logcats would be stored and then run it in the gscript lite? Meaning run the first code you posted.

Update ~ Never mind I found you had to have android sdk on your pc Im downloading that now. I still may need help tho.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
GScript Lite is a free app on the market. It was put together by XDA member "rogro", and he has a paid version as well if you want to throw a couple bucks his way.

Using the script above with Gscript (Lite or Pro), you don't need to be tethered to a computer nor set up the SDK and drivers. (Only when you want to capture a full first ROM boot do you need to use a PC (because the logfile grows so big in that specific case).

If you can force the FC to occur, then using the Gscript Lite script I showed above will capture the information you want.

bftb0

PS There is a brief outline of how you load a script into Gscript Lite in that "Universal Root for Dummies" thread over on AF.

cheers
[Droid Eris Q&A, Help & Troubleshooting] labnjab:
Thank you I will try that tonight and hopefully can figure out what the issue is :)
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
That code I posted checks to see if a folder exists, and if not creates it - /sdcard/logcats

No need for you to do it manually; the first time the script runs it creates that folder

But, yeah - wait for the FC to happen and then run that script within the next couple of minutes (no real hurry). It is also useful to make note of the time the phone displays when the FC occurs - it will be easier to find things in the logcat file by timestamp if you do that.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] labnjab:
Thank you I will do that as well. Thanks also for taking the time to help me.