yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Q&A, Help & Troubleshooting] deskweed:
Sorry about the wrong section. I admit to being a noob. And I seen the big red text. I know what that mod does that is why I wanted to do it
[Hero CDMA Q&A, Help & Troubleshooting] deskweed:
Now that you have all bashed me for the wrong place and accidentally posting twice can somebody tell what I can do to fix this.
[Hero CDMA Q&A, Help & Troubleshooting] thoughtlesskyle:
use rom manager from inside CM6 to install clockwork recovery, then reinstall cm6 and the gapps, that should atleast get you back to a usable state
[Hero CDMA Q&A, Help & Troubleshooting] deskweed:
That did the trick! Thank you very much and I will try to be more careful with the posts. I would still like to free up the memory like what is done with firerat's mod. Can somebody give me a little help as to how to do this for my Sprint Hero.
[General Questions and Answers] vanjapanco:
Hi,

Can somebody help for offline maps instalation on ZTE Racer. I have install maps for RMAPS acording instructions on net but I haven't get map on the screen, please help if you can!!!

Regards,

Vanja
[Desire Q&A, Help & Troubleshooting] rahul.pillai:
+1, getting this issue on Oxygen and CM ROM but not with Ultimate Droid.
[Desire Q&A, Help & Troubleshooting] horst0815:
getting the same since i changed to supervillain hd rom. before that, everything was ok.
[Desire Q&A, Help & Troubleshooting] d0msen:
Alright so I tried some other ROMs this afternoon and can confirm that Ultimate Droid does not have these wifi glitches.

Apart from that, MIUI has the problem, but somehow manages to stay connected longer than Oxygen or CM and it never occurred to me, that MIUI would drop the connection, while the screen is on.

Tested both ROMs with Wifi policy set to sleep on screen off and dynamic ip. Hope this helps :)

EDIT: Ultimate Droid just dropped the connection as well, looks like it's pretty similar to MIUI network-wise.
[Desire Q&A, Help & Troubleshooting] DashingGentleman:
I have had this happen constantly since the earliest CM6 builds on my university (eduroam; wpa2 enterprise) network. If data's not being used constantly, wifi will die in 2-20 minutes and then needs to be toggled off and on before it reconnects again. Massive pain in the bum. My home wifi is fine.

The stock 2.1 ROM did not seem to have this problem. I've seen these issues brought up several times in here and on IRC - they appear to occur on non-standard network setups. I vaguely recall someone saying it had to do with Android trying to re-establish an idling connection after the security token had expired but, rather than re-authenticating properly, the system just keeps making requests with the invalid token. Someone also suggested it's something to do with migrating between access points on a multi-AP network. Not sure if this is at all accurate, but it would be nice to see this issue fixed.
[Desire Q&A, Help & Troubleshooting] d0msen:
Kinda not diggin my thread being moved without even giving a reason for that.
[Desire Q&A, Help & Troubleshooting] bamboo12:
because maybe it doesn't belong in android development.. you're not developing anything?
[Desire Q&A, Help & Troubleshooting] bemymonkey:
Anyone else feel like this started some time around 2.2.1?

I'm having a similar glitch on Eduroam (PEAP + MSCHAPv2) networks...
[Desire Q&A, Help & Troubleshooting] mad-murdock:
since only few people have this problem, i suggest checking if its connected to your wlan access points. if you got a linux box with wlan card (or boot from a live cd), enter

iwlist [wlan device] scanning

to get a list of wlan devices, type

iwconfig

here is the output for my wlan, which does NOT drop (policy wifi never off - the battery killer)

Cell 03 - Address: ***DELETED***
Channel:10
Frequency:2.457 GHz (Channel 10)
Quality=67/70 Signal level=-43 dBm
Encryption key:on
ESSID:"wtf"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000000061f3181
Extra: Last beacon: 348ms ago
IE: Unknown: 0003777466
IE: Unknown: 010882848B0C12961824
IE: Unknown: 03010A
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: DD180050F20201010A0002A3400027A4000042435E0062322F00
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD0900037F01010024FF7F

breakdown: WPA2 with CCMP, max 54MBit on channel 10
[Desire Q&A, Help & Troubleshooting] :
reported a similir bug by me to cyanogen at october 29

http://code.google.com/p/cyanogenmod/issues/detail?id=2431

but no solution yet :(
[Desire Q&A, Help & Troubleshooting] Blissful Choreography:
I no longer have this issue with CM-216 but I did have it with about CM-200 and earlier (didn't use in between).

My iwlist output is:

Cell 01 - Address: ---------
Protocol:802.11b/g/n
ESSID:"Epa"
Mode:Managed
Channel:8
Quality:86/100 Signal level:-56 dBm Noise level:-81 dBm
Encryption key:on
Bit Rates:18 Mb/s
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PS

My radio is 32.49.00.32U_5.11.05.27
[Desire Q&A, Help & Troubleshooting] d0msen:
After two days of testing I can confirm that Wifi works flawlessly with the CM nightly 216! Something must have been changed in between 215 and 216 =)
[Desire HD Themes and Apps] he_stheone64:
Guys - this is driving me nuts. After exploring stock Android inside out with the Milestone, there is a new and great learning curve with Sense, which is fine. In any case after investigating it is pretty clear what to do, if I want to change htcdialer to a black background and in this case certainly white (or another bright) font colour for the dialer buttons. After decompiling and checking the layout folders everything directly aims to style.xml - so I edited the corresponding values:

<style name="text_style_dialer_button_number">

<item name="android:textSize">27.0sp</item>

<item name="android:textColor">#ffffffff</item>

<item name="android:layout_gravity">center_horizontal</item>

<item name="android:layout_width">wrap_content</item>

<item name="android:layout_height">wrap_content</item>

<item name="android:shadowColor">@color/color_255_255_255</item>

<item name="android:shadowDx">2.0</item>

<item name="android:shadowDy">2.0</item>

<item name="android:shadowRadius">1.0</item>

</style>

<style name="text_style_dialer_button_alphabet">

<item name="android:textSize">14.0sp</item>

<item name="android:textColor">#ff777777</item>

<item name="android:layout_gravity">center_horizontal</item>

<item name="android:layout_width">wrap_content</item>

<item name="android:layout_height">wrap_content</item>

<item name="android:layout_marginTop">42.0px</item>

</style>

<style name="text_style_dialer_button_zero_number">

<item name="android:textSize">27.0sp</item>

<item name="android:textColor">#ffffffff</item>

<item name="android:layout_gravity">center</item>

<item name="android:layout_width">wrap_content</item>

<item name="android:layout_height">wrap_content</item>

<item name="android:shadowColor">@color/color_255_255_255</item>

<item name="android:shadowDx">2.0</item>

<item name="android:shadowDy">2.0</item>

<item name="android:shadowRadius">1.0</item>

Unforunately no success - I also tried several layout xml despite knowing it will not work, just to double check. I also looked into EVO threads (since there was nothing here) and found out, that this style.xml and my values are right (certainly knowing that HTC changed something for DHD).

I also checked htcframework - besides a few pngs which I certainly found and edited no corresponding xml. So the answer seems to be in the smali code.

Anyone else tried this and succeeded? Any help would be greatly appreciated - Thx :cool::p
[Desire HD Themes and Apps] he_stheone64:
solved it myself - see Revolution theme thread :p
[Desire HD Themes and Apps] MrYuiM:
Would you mind sharing how you did it? I spent over an hour editing each PNG one by one to find out it doesnt work! Now that got me a bit pissed grrrrr
[Desire HD Themes and Apps] he_stheone64:
That is certainly not png related, you need to decompile the apk first and then need to edity styles.xml in values-hdpi folder.I was so used to AOSP (had a Milestone before, never had values-hdpi), that I started editing everything in values folder and with all the language value folders was not looking at the obvious...
[Desire HD Themes and Apps] MrYuiM:
Thanks. Last question, how would I go about making the buttons plain black, instead of having a sort of gradient around it/button around it? I'm trying to match my keyboard.
[Desire HD Themes and Apps] he_stheone64:
1. Use my themed htcdialer from Revolution Theme (which is already compiled for inverted use - credit is always nice, if you release it)

2. Make htc_pin_asset_rest.png in htcdialer 100% transparent

3. You should at least have a little glow or whatever effect for htc_pin_asset_pressed.png in order to have feedback for input

4. Make phone_keypad_background.png in com.htcresources.apk as dark as you like it
[Desire HD Themes and Apps] kurniawan77:
whaaa!!! almost a week looking at those files.... and indeed never looked between those language folders....H
[Desire HD Themes and Apps] MrYuiM:
Much appreciated and I will make sure to credit you if I release :D
[Desire HD Themes and Apps] Aamir.Badat:
can you install the dialer as an apk file? if you could please pass it over it would would go well with my screen setup at the moment ;)
[Desire HD Themes and Apps] he_stheone64:
You only need to download the Revolution Theme and flash only the htcdialer (delete anything in the update.zip, which you don`t need -certainly not the Meta-INF...)
[Desire HD Themes and Apps] he_stheone64:
I`m having a very strange Problem - all system/apps and framework-res compile fine (why shouldn`t they...) - only with com.htc.resources.apk I have the same issue after trying it 20 times with different approaches - directly in apktool, apkmanager 4.9, transfering compiled resources to original htc framework, compiling with apkmanager 4.9, transfering Manifest and Meta-Inf to the compiled htc resources, basically all the bells and whistles...

The system boots and works fine, but after compiling I loose access to settings. Even if I decompile in a test run and CHANGE NOTHING and compile, same result.

Following warning comes from apktool, but build finishes and boots as mentioned:

aapt: warning: string 'htc_day' has no default translation in C:\apktool\com.htc

.resources-decoded\res; found: zh_HK

aapt: warning: string 'htc_hour' has no default translation in C:\apktool\com.ht

c.resources-decoded\res; found: zh_HK

aapt: warning: string 'htc_minute' has no default translation in C:\apktool\com.

htc.resources-decoded\res; found: zh_HK

aapt: warning: string 'htc_month' has no default translation in C:\apktool\com.h

tc.resources-decoded\res; found: zh_HK

aapt: warning: string 'htc_year' has no default translation in C:\apktool\com.ht

c.resources-decoded\res; found: zh_HK

I: Building apk file...

Usually if something`s wrong you get errors (no warnings) or system does not boot, but this here is really unique. It is clear that apktool is loosing some entries somewhere, which are necessary for settings to load, subsequently settings init fails due to these missing entries.

I even added the missing translations to strings.xml and it compiled again fine, same result. I don`t expect a solution here, since I reported that issue to brut, but I only need to know whether that`s an isolated problem on my PC or whether you guys are experiencing the same problem with the latest 2.2.1 com.htc.resources.apk
[Desire HD Themes and Apps] MrYuiM:
I'll try and compile the file tomorrow and see what I get, at the moment I've just decompiled the whole theme to take a look at its guts :)

Sent using my two thumbs.
[Desire HD Themes and Apps] he_stheone64:
It`s really a pity, since I added some cool new look to com.htc.resources and it looks great on the DHD, but not really nice with this settings bug...
[Desire HD Themes and Apps] kurniawan77:
Hmmm, still can't get the menu text to white or green...

changed it to

<style name="TextAppearance.Widget.IconMenu.Item" parent="@style/TextAppearance.Small">
<item name="textColor">?textColorPrimary</item>

and even to

<style name="TextAppearance.Widget.IconMenu.Item" parent="@style/TextAppearance.Small">
<item name="textColor">#ffffffff</item>

and to

<style name="TextAppearance.Widget.IconMenu.Item" parent="@style/TextAppearance.Small">
<item name="textColor">#ff777777</item>

Still no luck, and yes i have even modded it in values and values-hdpi

How's your progress on this he_stheone64???
[Desire HD Themes and Apps] kurniawan77:
which version of apktool r u using? 1.3.1 or 1.3.2?
[Desire HD Themes and Apps] he_stheone64:
Both - 1.31 AND 1.32.
[Desire HD Themes and Apps] he_stheone64:
No problem - I managed to invert menu AND all popups plus color in notification bar. I used the popups and menu from Gingerbread for the tests and even black menu for bright and medium popup`s. That gives a little DarkEdge feeling... The problem here is, that it looks great but due to described issues I`m loosing access to settings, a behaviour I never experienced and I compiled thousands of apk`s...

Coming from AOSP or CM6 ROM`s like me, you initially are editing the wrong framework... these changes for menu, popup and even the simple statusbar have all to be done in values folder of com.htc.resources - BUT due to compilation issues I can`t release the outcome. There might still be other approaches, but com.htc.resources OVERWRITES all style edits in framework-res you`ve tried before. It is like some png`s like popup, where the changes have to be done in com.htc.resources and not in framework-res.

So my question still remains the same - if you decompile and compile com.htc.resources and push it back and boot - do you also have the same issues, that settings don`t start anymore (no FC`s - they just don`t init)? Just try this without changing ANYTHING, only decompile, compile and push back. This helps me to understand, whether I have an isolated problem or whether this is a general apktool issue with the latest htc resources on DHD (maybe also on Z).I tried it with apktool 1.31 and 1.32, both directly and with apkmanager 4.9.
[Desire HD Themes and Apps] kurniawan77:
I'll give it a try to de- and compile com.htc.resources... sometimes it helps to run as administrator... don't know if it helps u.
[Desire HD Themes and Apps] kurniawan77:
nope getting same warnings

I: Building resources...
aapt: warning: string 'htc_day' has no default translation in C:\Users\HP DV7-4030ed\Desktop\Irwan\apk_manager_4.9\other\..\projects\com.htc.resources.apk\res; found: zh_HK
aapt: warning: string 'htc_hour' has no default translation in C:\Users\HP DV7-4030ed\Desktop\Irwan\apk_manager_4.9\other\..\projects\com.htc.resources.apk\res; found: zh_HK
aapt: warning: string 'htc_minute' has no default translation in C:\Users\HP DV7-4030ed\Desktop\Irwan\apk_manager_4.9\other\..\projects\com.htc.resources.apk\res; found: zh_HK
aapt: warning: string 'htc_month' has no default translation in C:\Users\HP DV7-4030ed\Desktop\Irwan\apk_manager_4.9\other\..\projects\com.htc.resources.apk\res; found: zh_HK
aapt: warning: string 'htc_year' has no default translation in C:\Users\HP DV7-4030ed\Desktop\Irwan\apk_manager_4.9\other\..\projects\com.htc.resources.apk\res; found: zh_HK
I: Building apk file...

i'll try renaming it to comhtcresources.apk.... don't know if it helps but we'll see tonight... i'm off to work now...
[HD2 Android Q&A, Help & Troubleshooting and Genera] dogntbone:
Hi everyone,

Sorry if this has been answered before, but would someone please point me in the right direction to get MMS working on MDJ Froyo HD v4.3 for me?

I am currently on M1 (Singapore) and would really like to get the MMS feature working on my HD2 now.. Thank you!
[HD2 Android Q&A, Help & Troubleshooting and Genera] .hide:
which rom are u using bro? i try Mj and shubcraft rom. all mms setting is by default 1.

u can try this setting i get from my Rom

Name: M1 Mms

Apn:miworld

username:65

password:user123

mmsc:http://mmsgw:8002

mms proxy:172.16.14.10

Mms port:8080

Mcc:525

Mnc:03

Apn Type:mms

hope it helps.
[Captivate General] KM00:
Hi,

I don´t know if everyone got this issue but I was recoding a concert on my Captivate the other day and the sound its just distorted like the mic sensitivity is way to high or the recording volume is to high, is there a menu to change the recording mic volume?
[Captivate General] KM00:
I'm the only one with the sentive mic?, no body else has this issue or find this to be and issue?
[Wildfire General] rolks:
is it possible to make wildfire to work with MicroUSB to HDMI or similar
[Wildfire General] nunosilva10:
Hdmi I think not, but a friend told me that is possible to connect our phone to Projectors and our computers lcd televisions etc..

You just need a specific cable
[Wildfire General] rolks:
any idea wich cables?
[Wildfire General] AlexKR91:
You are funny =) USB is USB, HDMI is HDMI. You need hardware USB->HDMI, not cable
[Wildfire General] rolks:
what hardware do you mean? there is a microusb2hdmi cable for 50$, but this for galaxyS.
[Wildfire General] 1000moths:
Thats because the Gal S has the hardware needed to do this.
[Wildfire General] MySelf_v1:
take your wildfire, put it on a table, put the hdmi cable over the wildfire then take a hammer and... put the cable into the phone. That's the right way ...
[Wildfire General] rolks:
do you mean WF not able send video audio over microusb or eclair cant?
[Wildfire General] litening:
Bingo! :cool:
[Wildfire General] atkinchris:
I'm going to add to this in the case it wasn't clear to the OP.

The Wildfire is not built to transmit AV signals via the micro USB port, unlike some models such as the Galaxy S. Therefore, regardless of the cable you stick in the side, or the software you run on the device, the Wildfire will never have the hardware in between for it to work.

Stop looking, and don't splash out on any expensive cables; they won't work.
[Wildfire General] rolks:
thaks for answering, thread can be closed
[Wildfire General] Manc:
such a shame it cant do this
[Droid Eris Q&A, Help & Troubleshooting] semmtexx:
I know I have seen a thread on how to fix this issue with Launcherpro not syncing facebook contact photos but I have been googling all morning and cannot find it. Could someone either post me the link to that fix or post the Gscript file that fixes it? Thanks!!
[Droid Eris Q&A, Help & Troubleshooting] lotus22:
http://xdaforums.com/showpost.php?p=9175184&postcount=5
[Galaxy S I9000 Q&A, Help & Troubleshooting] makuchaku:
Hi,

I recently bought a GT 9000 device and first thing to do was installing voodoo lagfix.

Yesterday, I tried updating to Froyo via Kies - and now the phone gets stuck up at a blank screen. I do get the colorful "S" logo - but thereafter, nothing on the screen. Both the soft buttons keep glowing.

To make the matters worst, none of the 3-button combos work on my device.

I'm a little lost now.

How should I proceed?

Thanks!

[Update]

Fixed - http://xdaforums.com/showpost.php?p=9739803&postcount=7
[Galaxy S I9000 Q&A, Help & Troubleshooting] pwhooftman:
you should have disabled lagfix first.....

Are you absolutely sure none of the 3-button methods work ? For download mode, i have to follow exactly this procedure:

- turn off phone (and wait for the final vibrate which indicates its really off. Pull the battery if not sure)

- turn on pressing and holding volume-up, home and power in that order

- wait till the Samsung GT9000 logo appears for the second time

- release power, home, volume up in that particular order

Once in download mode, you can flash Voodoo again via Odin and it will work again.

If you cant get into download mode, you'll have to solder a special usb plug to get into download mode, or bring your phone in for repair. This is why there are warnings everywhere to only proceed lagfixing & stuff if the 3-button combo works...
[Galaxy S I9000 Q&A, Help & Troubleshooting] makuchaku:
Hi pwhooftman,

I really wish that I would have read the docs completely. Anyways, its too late now - only thing to do is to learn from this mistake.

None of the three button combos work on my phone, have tried them several times.

I've spoken to the Sammy reps, will be taking in my phone for a repair.

The special USB plug sounds very interesting but I'm not too interested in hacking hardware on just a week old phone :)

Your reply is much appreciated :)

Thanks!
[Galaxy S I9000 Q&A, Help & Troubleshooting] pwhooftman:
Hi,

You wont have to hack the phone itself for the special USB ' JIG' as its called. The jig can be a micro usb plug or cable which you open up and connect 2 pins with the right kind of resistor. That will make the i9000 go into download or recovery mode. The repair center will probably use the same thing. You can make the jig yourself if your good in electronics and have resistors lying around, otherwise it's a trip to the repair center like you plan to do.
[Galaxy S I9000 Q&A, Help & Troubleshooting] makuchaku:
Onto researching about the JIG then! :))
[Galaxy S I9000 Q&A, Help & Troubleshooting] makuchaku:
Here it is...

http://xdaforums.com/showthread.php?t=819551
[Galaxy S I9000 Q&A, Help & Troubleshooting] makuchaku:
Good news! My story has a happy ending!

1) Took my phone to a local mobile repair shop, and he managed to REALLY brick my phone! (Only the phone-!-pc icon came on screen)

2) Asked him to put the phone into download mode

3) Brought the phone back home while it was still in download mode

4) Fired up Odin and followed the process from http://www.pathikshah.com/blog/install-android-2-2-froyo-galaxy-s/

5) Now I have a perfectly fine Froyo build on my device :)

6) Data saved on my internal SD card is still there :))

Next things...

1) Make a homemade JIG

2) Make sure to get the 3 button combo working on my phone!
[Galaxy S I9000 Q&A, Help & Troubleshooting] iMohak:
I found this post while looking for samsung usb jig new delhi :)

Did your local guy have a jig? I am in GK and with a samsung captivate in a semi-bricked situation ;)

Cheers
[Galaxy S I9000 Q&A, Help & Troubleshooting] keylocked:
my samsung galaxy is stuck in recovery mode (clockworkmod recovery) and will not connect to the computer via usb. I have reinstalled the usb drivers but they constantly fail to install, tried on different computers and manually installing them seems not to work, what would be recommended?

regards

edit: manged to fix with odin yay
[Legend Android Development] ali ba:
CyanogenMod 6.1

Download

Use ROM-Manager or the teamdouche mirror.

Description

The official release of CyanogenMod for the Legend.

You know the rules. But let me repeat them for your reading pleasure:

Read before you post. Read the

whole

thread.

Requests for builds, features, fixes or apps to include will be ignored.

Do not ask questions. This is the development board.

Add-Ons

For those who want 2.6.32.17 here's an experimental and unsupported update package:

cm-6.1.0-Legend-kernel-2.6.32.17.zip

Be warned as 2.6.32 is still unstable resulting in the device not suspending correctly when bluetooth is on.

Beer / Coffee / Prescription Drugs:
[Legend Android Development] gyroing:
Thanks Great Developers. ;)
[Legend Android Development] canttona:
Woow, that's great!
[Legend Android Development] Sckank:
Wow thanx :-)
[Legend Android Development] maximus1965:
Thank you very much aliba :)

Which radio do you recommend for the stable release ?
[Legend Android Development] deimdos:
here we go! :D

EDIT: I guess "latest" gapps still are 20101020, is that right?

EDIT2: damn it! teamdouche web is down and I couldn't download the ROM... if anyone has any mirror would be great :)
[Legend Android Development] Chaotick:
Cannot download out of this link....The download starts but after a couple of moments it cancelled and the file is incomplete.
[Legend Android Development] mrkekson:
Cool, keep up the great work ali ba!:D
[Legend Android Development] versifier:
*Scratch that*

Found it :)
[Legend Android Development] JonasDroid:
Thx I'll try the 2.32 kernel asap

If only I would have visa ,... :(