yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Themes] Showtime7:
Lol... I told NRGZ specifically... DON'T COOK IT. Guess he didn't read my post.

But I will try to fix this now because I upgraded to 6.5.5 so I am back to arkswitch. Tried applying my theme and it crashed immediately. I am going to try using all solid GIFs with simpler profiles and hopefully that helps.

Also the background is not solid color. Look at the hi res screenshot it is clearly textured. I must keep it to be consistent with the HTC look.
[Windows Mobile Themes] xILukasIx:
I get the same error, but it worked fine until I read that yours constantly crashes lol...

It works fine when there's no program open, but when I open a program and start ArkSwitch, it crashes.

Again, this didn't happen until NOW.

I can't even open the Start Menu after the crash and the phone gets really slow.

I'm on Energy ROM (GTX) for HTC HD2 btw.

Is the theme cooked in this ROM?
[Windows Mobile Themes] toadlife:
I tried it out on my ROM. No crashes in the short time I've used it.

I have a feeling it's not your theme that is causing the crashes for certain people. In the processes off making my ROM, I experienced frequent Arkswitch crashes, but the theme never changed. The crashes corresponded with certain Windows mobile builds.

Right now, my ROM is using 21887 and I haven't seen Arkswitch crash in ages. With other builds (21892) Arkswitch was VERY unstable.

BTW, your "selected" and "deselected" buttons are a bit jagged on the edges. Here are the ones from mine.
[Windows Mobile Themes] Showtime7:
Thanks. I was just being lazy (as usual) and just wanted to make my theme quick and easy, lol... I'll update my package with your x buttons.

And it does appear to be the theme because I've been using ArkSwitch since yesterday with no theme applied and have had no crashes. As soon as I apply the theme, almost immediately it will crash. And will continue crashing until I kill Arkswitch or uninstall it. Majorly sucks, wish the app was a little more stable. :-/
[Windows Mobile Themes] toadlife:
Well maybe it just doesn't like large themes. Mine is pretty light. It only consists of the buttons and the top bar. The background is just a solid color.
[Windows Mobile Themes] Showtime7:
I wonder if the background can be set to repeat...
[Windows Mobile Themes] p0izn:
On HTC TD2 @ 6.5 looks great! Thanks a lot. Good job
[Windows Mobile Themes] powinmo:
I did see your original background image theme was textured, and your image is pretty darn good match to the HTC theme. But the values I picked for a background color vs using image seemed close enough for my needs without having arkswitch constantly painting a 64k png to the device.

Yeah I saw that NRGZ put in his own custom arkswitch theme with his latest July 10, 2010 ROMs. Like toadlife mentioned, I doubt the themes are the primary cause of arkswitch terminating prematurely so much. Some ROM builds seem to cause AS more grief than others regardless of the theme used and my experience mirrors his.

Looking forward to seeing your modified theme. Otherwise, I'm just using your original theme with some tweaks of my own for now.
[Windows Mobile Themes] Showtime7:
I am working on it now... I need someone to test it because my current rom has a task manager built in. Any takers?
[Windows Mobile Themes] powinmo:
If no one else has offered since your post, shoot me a PM (assuming I can receive them since I have a low number of posts). I'll try it out.
[Windows Mobile Themes] toadlife:
I'll be happy to test it for you.
[Windows Mobile Themes] Showtime7:
I will send it to you both. Oddly switching to indexed profile and saving as a GIF made the file much larger. Regardless, it's worth a shot. Will be sending the PMs shortly.
[Windows Mobile Themes] Showtime7:
Success! Using the GIF background it seems the problem is fixed. I will need others to test it as well to be completely sure but for me it did the trick. First post being updated now... Once we get some feedback, chefs feel free to cook this in your roms! :)
[Windows Mobile Themes] Stephane Dufault:
constant crash

I love your theme, but also I get constant crash (same as on the post#4). When I remove the background and replace by a color I still get the crash but much less.

To be noted that I get the same problem with other theme, any idea?
[Windows Mobile Themes] Showtime7:
Not sure, I haven't been able to reproduce the crash since the updated version with GIF background format. It may be helpful to post your rom information so that others may be able to test and see if they get the same thing.
[Windows Mobile Themes] Stephane Dufault:
My info is in my signature
[Windows Mobile Themes] Showtime7:
Oh... yes of course xD

Well have you tried upgrading to v1.2? This fixed some lingering bugs for me.

Sorry I can't help more, but I really think my theme is not causing the problem at this point because I've tried several ROMs on my HD2 and it works on all of them.
[XPERIA X1 Q&A, Help & Troubleshooting] klick_drauf:
Hello

I'm new here and I need a Windows Mobile 6.5 Rom in German but not from rapidshare

I have the italian version but i cant read it or can someone say how to make it in german ??
[XPERIA X1 Q&A, Help & Troubleshooting] Draken Korin:
hey

welcome to xda :)

it was not necessary to open a new thread on that

let's sum up:

if you want to change the language of winmo you have to flash a rom with the language cooked in, it's not possible to do so later

to find roms in German search titles for GER, then check the source through the dl links, avoid rapidshare hosted ones that way

best :)

Mod. edit: not dev related, moved to general
[XPERIA X1 Q&A, Help & Troubleshooting] klick_drauf:
:rolleyes:

i have installed it

but i now i have an other problem !!

So i download the touchflo 3d software and install it

but now i cant start it !!!

how can i start it ??
[XPERIA X1 Q&A, Help & Troubleshooting] klick_drauf:
Another problem .jar games dosn't start and java isn't here

can i download the original java version for the xperia ??
[EVO 4G Android Development] wsantiagow:
Thank you. Will see if this fixes my broken 4G.
[EVO 4G Android Development] whitslack:
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.
[EVO 4G Android Development] blehzz:
please add back in Qik and TV... let users delete that after? many people use those programs.

either way, nice work :)
[EVO 4G Android Development] wphend00:
Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?
[EVO 4G Android Development] whitslack:
Get the rootsafe-Sprint.zip instead. The only differences between it and the stock update are that it doesn't include the recovery image and it preserves setuid+setgid root for /system/xbin/su.
[EVO 4G Android Development] ViViDboarder:
I'm assuming broken as in you ran the unrevoked update?

Any luck?

Also, OP:

Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.
[EVO 4G Android Development] whitslack:
It's exactly the update package furnished from Sprint over-the-air (the 30.2 MiB one), but with one line added to the updater script so that the update doesn't kill the setuid permissions on /system/xbin/su.

That means it changes everything Sprint changed in the latest update, including kernel, radio, WiMAX, and anything else.
[EVO 4G Android Development] bjrmd:
So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?
[EVO 4G Android Development] whitslack:
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.

FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.

I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.
[EVO 4G Android Development] rugedraw:
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?

Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?

Thanks, btw!
[EVO 4G Android Development] ViViDboarder:
Right... Well, here it scans and then turns off wimax and then turns it back on and keeps doing that. Working with joshua_ last night I got it to keep scanning... It never did get an IP though but the interface was definitely present. I could see it with netcfg from the adb shell.

I pointed joshua_ to this thread to see what he things of these patches. I had been trying to help him use my phone to debug this issue so I don't want to mess things up too much for him.
[EVO 4G Android Development] Badious:
I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.

BTW I am now using a Fresh and not DC on my phone. And I am fully rooted(NAND unlocked) and have been able to run several other updates.zip without issue, currently using Clockwork MOD for recovery and not RA
[EVO 4G Android Development] whitslack:
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)
[EVO 4G Android Development] whitslack:
What recovery are you using? Amon RA 1.7.0.1 wouldn't work for me. It kept complaining about no signatures, even though I had signed the update. I used toast's recovery successfully.

If that's not the problem, then it can only be that some file on your phone is not identical to the version from the stock 1.32.651.6. Did you replace the /system/build.prop file with the stock one linked in the OP? In particular, this update will not apply against Flipz's stock rooted ROM unless you replace that file with the really stock one.
[EVO 4G Android Development] Badious:
Yep downloaded the buildprop in the OP and copied that over via ADB successfully(checked softwar version and it shows stock buildprop info)

Let me try it one more time and see exactly what it is bawking about.

Ok. Error Reads as Such:

Verifying Current System....assert failed: apply_patch_check ("system/app/AccountandSyncSettings.apk" . TWO LONG SETS OF HEX NUMBERS[if you need them I can provide them])

E: Error in /sdcard/OTA..(name of full file)

(status 7)

Installation Aborted.
[EVO 4G Android Development] TheMike1:
ERROR:

Verifying current system...

assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]

E:unknown command [56479c22c")]

E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip

(Status 7)

Installation aborted.

Can someone assist please, would like to get this new Radio OTA flashed....

Edit: Running DC 3.2.1 with Aloyisus Theme
[EVO 4G Android Development] rugedraw:
Thanks for the quick response! I am running a rooted version of 1.32.651.6 and I've been waiting for something like this. So I should be OK using clockwork recovery to run this?
[EVO 4G Android Development] whitslack:
You can put it on your SD card by any means available to you. The only requirement is that your recovery program does not care that it's signed by someone other than HTC.

That can only mean that you're not using the stock ROM (w/ root added). This is an incremental update straight from the official sources with one slight tweak to preserve root access, so you must be using a stock system in order for it to apply.

Users of custom ROMs should be flashing new versions of those custom ROMs. The incremental upgrade path here will not work on custom ROMs.
[EVO 4G Android Development] nunyabiziz:
BY THE OP first page
[EVO 4G Android Development] frankenstein\:
4G FIXED!

OK, I had the problem many people are having with 4G following the update. My 4G would Scan without finding or attempting to connect to the network.

After applying this update, which ran again without a problem once I restored the apk files I had previously removed and substituted the build.prop posted by the op for the one flipz modified in his .6 rooted stock rom, I did a little digging as I was again stuck in the scanning for 4G network phase.

I ran through the checks outlined in this post: http://xdaforums.com/showpost.php?p=7020516&postcount=3826 primarily looking to make sure my mac address was correct and the wimax_properties file had the correct entries as outlined there in.

I then found some information in the DC rom thread that suggested a number of steps, many of which wern't aplicable because I don't run DC but the ones I did use are as follows.

1. I ran an update of the prl just to make sure it was current.

2. I ran the profile update in the same location.

3. I then did this:

adb shell

ls /data/misc/wimax/

look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)

mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old

4. Start 4G (It didn't connect for me here.)

5. Power off the phone and power it back on. (When it powered back on it connected for me.)

4G has been working since then. In fact, I'm posting this via wireless tether over that 4G connection.

I used the original patch. The one that does not include the recovery image. the recovery image was not needed as part of the update package to correct this.

---Edit---

For those that use the fix I posted here and find that their 4G connects but drops the connection fairly quickly and then reconnects over and over, this is a function of the timeout period for the 4G connection which is reset by this process. This can be adjusted by doing the following:

##DATA#

Select Edit Mode and input your MSL. (Call sprint and request it or use CDMA Workshop to get it.)

Select WIMAX and look for the WIMAX_Idle_Sleep value.

The value will be 10 which is 10 seconds. This is why it keeps droping the connection over and over. Change that to 300. Then hit the menu button and select Commit Modifications.

Once done, your wimax shouldn't drop every 10 seconds any longer.
[EVO 4G Android Development] telugite:
The PRL Version shows as 60662 (i think the current one is 60667)

and PRL update does not find any update

Is there another way to update.
[EVO 4G Android Development] onyx00:
I get a basic error it seems: when I try to apply update zip it says "Can't open /sdcard/update.zip (no such file or directory)"

What am I doing wrong?
[EVO 4G Android Development] whitslack:
To solve all of the problems with people having modified versions of stuff, and to get us back to a really stock everything, I've posted a new method for updating that starts over with the original firmwares of everything and takes you right up through the latest OTA update without even needing adb. Truly a dummies' method. It should work for any EVO in any condition, even unrooted phones, assuming they haven't already done the official OTA.

How to start over: From original stock to rooted latest OTA, no adb needed!
[EVO 4G Android Development] Lord-Audie:
I did the incremental update, but now i can't wireless tether nor use root explorer.... any way to solve this?

did i lose my nand unlock?
[EVO 4G Android Development] whitslack:
It's impossible for you to have lost the NAND unlock, as this update didn't include an HBOOT image.

Most likely, you need to install the new Superuser update, su-2.1-e-unsecure-signed.zip.
[EVO 4G Android Development] whitslack:
Sounds like you have the stock recovery. You might want to try the new method I posted here, which will set everything (including the radio and WiMAX) back to the original stock versions and then take you through the two OTA updates while still retaining root.
[EVO 4G Android Development] nunyabiziz:
The same thing happened to me, I do have SU 2.1-e-unsecure-signed.zip installed.

I have Clockworkmod on mine but there are issues with access to some files but not all. Strange:confused:. I just redid the NAND unlock again to gain access to all files but have to redo my ROM.
[EVO 4G Android Development] wsantiagow:
The other day I got past all these steps successfully except for the 4G would just keep scanning:confused:. I now see your post that you renamed the tree.xml and this actually caused the new 4G radio to properly install.

As of today, are you still connecting to wimax and just to confirm, you are running the latest 4G radio "EVO_WiMAX_25641_R01" and the latest software 1.47.651.1?

Thanks for your quick reply:)!
[EVO 4G Android Development] mikeyxda:
OK, so I'm a new Evo owner and unrevoked root user. That makes me a root tard but I figure if I'm smart enough to realize I'm a tard, maybe I'm not a tard after all! :D Anyway, we're all root virgins at some point and I'm ready to dig into "real root". Since I'm currently on 1.32.651.6 and basically have a stock/unrooted phone, is there currently a path to go to 1.47.651.1 and root my phone? Obviously I haven't yet accepted the latest OTA but it's not clear to me if the process in this thread will work for a totally stock unrooted 1.32.651.6 phone or do you have to start with stock PLUS root? In any case, which steps would I use in the instructions?

Thanks,

Mike
[EVO 4G Android Development] frankenstein\:
4G continues to work for me today as it did yesterday. I appear to be in good shape.

and

Yes, software ver is 1.47.651.1 Raido is 2.05.00.06.10 and wimax_mtd reports wimax is 24651.
[EVO 4G Android Development] frankenstein\:
You don't need to go to the .1 release to root. Toast's 2 part full root method will work with the 1.32.651.6 ota release. Look in the wiki that is stickied at the top of the dev forum for links to both parts of Toast's root method or use one of the other methods based on Toasts process posted in the dev forum. I think there is a three click process and a couple of others as well.

DO NOT apply the latest OTA HTC released or you will loose your ability to root. The devs here are working on finding a way to overcome the changes made by the latest ota but have not found one yet.
[EVO 4G Android Development] wsantiagow:
4G Fixed II!

First of all thanks to Frankenstein for posting these instructions!

I used Calkulin's EVO_1.47.651.1_Rooted.zip, then I updated the Wimax radio with version EVO_WiMAX_25641_R01

Here are Frankenstein's Instructions: This worked for me......

"adb shell

ls /data/misc/wimax/

look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)

mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old

4. Start 4G (It didn't connect for me here.)

5. Power off the phone and power it back on. (When it powered back on it connected for me.)"
[EVO 4G Android Development] Nitro2985:
After doing this my 4G is stuck on "Turning on" It's grayed out and I can't select the option in settings. Alogcat confirms that WiMAX is working in the background trying to connect.

I'm getting really frustrated with this 4g connection issue.
[EVO 4G Android Development] Jackdup:
Didn't work for me (unrevoked victim).

This frankenstein process did not work for me. 4g still scanning endlessly after OTA.

I used the Unrevoked v2 patch update (supposedly did not include wimax update, and did not cause wimax to stop working). WRONG. Caused my wimax to stop working. But it's possible I ran the adb code wrong and didn't know it. I'm on a MAC and run it in terminal. It showed me my mac address with tree.xml file, then when I ran the mv command, it seemed to work, just gave me a new prompt line with "$" so I figured it accepted my mv command. Is that right?

Any advice for fools like me on the Unrevoked train with no wimax connection after OTA2 v2 patch update?

UPDATE: I fixed my 4g the "Whitslack - how to start over" way. STart with Toast part 2, then do Whitslack intructions. Skipped nandroid backup. Everything is back in order now. Thanks everyone for the posts.
[EVO 4G Android Development] l1nk3d:
All I did from the instructions was to move the file he mentions last, power off the phone and power it back on. Activate 4G, and I was good to go. I think that is the part of his instructions that really matters. I have had this issue with Bugless Beast for weeks now. No more, 4G is staying active the way it did when I first bought the phone.
[EVO 4G Android Development] frankenstein\:
The fix I posted likely won't work for unrevoked users. From what I've read their problem goes somewhat deeper in that the unrevoked update changed the wimax mac address of the phone to something that is invalid.

The link in my post will take you to instructions on how to check and see if your mac address has been changed. There are a couple of threads in the dev section for dealing with this problem, depending on how extensive the change is.

This fix is for those with their 4G stuck in scanning, but not connecting or attempting to connect, with an unchanged mac address.

There is also a permissions fix posted in the dev section someplace that might address the problem being experienced by the person who's 4G isn't turning on completely. I can't say for sure.

I wish I could take credit for these fixes but they come from a variety of places around the board and I just pulled them together and posted what worked for me. Much of it came from the Damage Controll rom thread. I believe you can find a link to the permissions fix there.

The wimax mac address proof of concept fix is posted in a seperate thread on the board here in the dev section.

For those that use the fix I posted and find that their 4G connects but drops the connection fairly quickly and then reconnects over and over, this is a function of the timeout period for the 4G connection which is reset by this process. This can be adjusted by doing the following:

##DATA#

Select Edit Mode and input your MSL. (Call sprint and request it or use CDMA Workshop to get it.)

Select WIMAX and look for the WIMAX_Idle_Sleep value.

The value will be 10 which is 10 seconds. This is why it keeps droping the connection over and over. Change that to 300. Then hit the menu button and select Commit Modifications.

Once done, your wimax shouldn't drop every 10 seconds any longer.

Good luck!
[EVO 4G Android Development] mrkmrk:
Is there any alternate way to go about this? I'm running Baked Snack, and we can't type ##DATA# to get to the proper menu :(. I have the exact problem you describe, though, I'm pretty sure. It connected once, then disconnected, and now it alternates between scanning, turning off, and turning on. The first part of your suggestions (deleting the xml file) was excellent, though! :)
[EVO 4G Android Development] mac_evo:
Thanks so much for this fix - worked perfectly! Fully rooted now with operational 4G. :)