Related
Hi all,
it has been now nearly two weeks since the rom update leaked, and still so sign of an official update on htc website.
I'm wondering if this was really the final rom version, if so i don't know why htc would wait another two weeks after the leak.
I heard that somebody got that rom from an ftp server which is used by htc to upload data before it gets released. In this case two weeks seems also way too long for a deployment.
Are there any signs of the official release? I'm curious to see whether there are any last minute changes done.
well it could do with both orange and tmobile (in the uk) need to add there custom rubbish to there phones?
I read about major improvements in speed.
BUT - I also read about weather DB issues, WiFi issues, a.o problems.
So, I am definitely going to stay put, until an official release.
I am not going to waste time on reinstalling software etc, by flashing something "maybe-this-is-a-rom-very-close-to-the-final-one"!
yeah of course the carrier updates will take more time, but im talking about the htc update for unbranded devices.
since i made the ruu update i can confirm speed updates (but not huge difference), and i can confirm that more often the browser seems to have issues when going online via wlan. connection is there, signal is there, but the browser cant open pages.
and my device actually freezed two times, i couldnt make softreset and had to take the battery out. annoying.
but overall im satisfied with the performance optimization, still i will make another update as soon as the official rom is out..
and another minor thing: updating weather information manually will result in three updates. the app will update the weather data three times in a row, even though you only pressed update once,
I've had none of those problems, just checked the weather and it seems to update just once. I did have to pull the battery a couple of times BEFORE installing this new ROM when my phone totally locked though.
two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.
rom t-mobile
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol
rhedgehog said:
two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.
Click to expand...
Click to collapse
yeah two weeks was maybe too much. I was hoping this is not final since i have some new issues since i made the ruu update:
- peep widget updates only every 30th try. I'm trying to update the tweets and it doesn't work for about 20 times, and then somehow it works after many more tries. When i open peep app i get an error message that the service is not reachable.
- wifi has problems. many times it seems the connection is dead, when technically everything is ok.
- freezes (but i installed about 40 apps, maybe this was too much...)
- keyboard has sometimes lags. i never had ANY lags inputting text before the update.
- more force closes by 3rd party apps.
- touchflo force closes seem to occur more often also (but i had them before too so this might be the same).
- freezes when the device is in sleep mode. I was at a meeting, not doin anything with the device. Then i wanted to check the time and the display didn't power on. So the device freezed during some background process by android or any 3rd party app. I never had this problem before the update.
the good:
- yes its faster (homescreens)
- even the contacts list has LESS stutter, but stutter is still there. IPHONE 3gs is way ahead in this regard. i don't know why other lists on android are completely fluid while the contacts app list is not fluid.
- battery seems to last longer
overall the first impression was VERY good, but is somehow stained by the problems that surface after some usage time...i'm not 100% sure if the speed update was worth it...waiting for android 1.6 update, maybe this sorts some stuff out..
I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave
locutus-of-borg said:
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol
Click to expand...
Click to collapse
the RUU update won't work on a branded device. You need root to install the new rom in this case.
foxmeister said:
I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave
Click to expand...
Click to collapse
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...
Shahpur.Azizpour said:
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...
Click to expand...
Click to collapse
Well, Menu->Security->Factory Data Reset should do the job. To be honest though, I'd be more inclined to trust the "standard" Android way of updating your ROM than the HTC RUU process, because, as far as I'm aware, this'll be their first RUU for an Android device.
Regards,
Dave
Interestingly, the second poster here, http://forum.xda-developers.com/showthread.php?t=557628 , indicates that they had a problem with the factory data reset, but a recovery image wipe fixed it. I wonder if this related to your issues?
Even if you don't want to flash the modified recovery image permanently to your phone, you could boot it using fast boot and then wipe.
Regards,
Dave
how does it work? how can i restore a revocery image? isn't this an issue with the latest RUU update, that flashing recovery rom is not possible anymore or am i mixing things up here?
Steps 1 to 5 in this link, http://forum.xda-developers.com/showpost.php?p=4257045 , tell you what you need to do to boot the modified recovery image. Note that this doesn't flash anything to your phone - it just boots off the image you've supplied. You can permanently flash the recovery image later if you wish, but since you took the RUU root, I guess you don't want to put anything "unofficial" on your phone.
I've no idea if you having RUU'd already will prevent this, and I'm not going to RUU my phone to find out, but I doubt you would be stopped booting using fastboot.
Regards,
Dave
okay, thanks for the info!
Modaco wrote on a thread that doing the RUU update will make it nearly impossible to flash a modified recovery image.
I'm going to work with my current setup for some more days. If i see the mentioned problem reoccuring more often, i will proceed with the steps in your post.
or maybe we will see some changes (if not to the rom itself maybe at least the RUU will get an update) with the official rom update.
bye
shahpur
Just searched and you are right, you can't boot the recovery image if you have the new HBOOT from the RUU. However, the situation is not irreversible!
http://android.modaco.com/content/htc-hero-hero-modaco-com/292396/if-you-flashed-the-2-73-ruu-and-got-the-new-hboot/
Regards,
Dave
got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.
sorry, was busy working, but it seems you;ve got the answers...
i;ve not had any problems that you have had either with those apps. mine is so much better it's ridiculous. but then i wiped first and again afterwards just to make sure.
Lars8000 said:
got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.
Click to expand...
Click to collapse
Wow cant wait for tht, but 2bh I wud like T-mob to release their update as well at the same time as I am getting the G2 Touch on friday.
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
First post here but I have searched and read a lot since joining.
I bit the bullet and rooted my hero last night following this guide from regaw_leinadso I guess I can't post links...)
Everything went fine so I then wiped and loaded freshrom 2.1.2 followed by a damage710.zip overclocking file in that order. This also worked fine and I was enjoying the new setup.
The main reason I rooted was for wifi tethering so I tried it out and kept getting a "unable to start tethering, please try again" message. After more reading I found that there was a bug in 212 on superuser permissions. So, I loaded the 212 su fix file and went back to wifi tether. The su permission came up and I selected always allow, was able to connect and all was good. I then tried to stop, su permission came up again, always allow was selected...then the device froze on "stop tethering." The only way for me to get out of this was to pull the battery.
I tried it again, and again it freezes at stop tethering and I have to pull the battery. I tried updating wifi tether with the one that is currently on the market (202) and that version stops at "unable to start tethering" message.
My initial recovery image was 1.5.2. I then did the process again using 1.2.3 with the exact same results.
Am I missing something here?
Thanks
In the dev threads there is a kernel you need to flash to stop it from freezing. I couldn't tell you if it works with your rom though. just have to try it.
Thanks; any idea where or which one it is? I can't seem to find it.
Kcarpenter said:
In the dev threads there is a kernel you need to flash to stop it from freezing. I couldn't tell you if it works with your rom though. just have to try it.
Click to expand...
Click to collapse
Found it. Kernel is in the following thread:
"[KERNEL][OC]Darchstar's GoDmOdE-Darchshizz #15 for senseUI roms - UNDERVOLTED"
Hi,
I haven't found a similar problem, that's why i'm opening a thread here. I haven't done any unusual changes to the 2.1 that was already on device (no root, no sys file changes, nothing).
The phone reboots at least 2-3 times per day. Every time I check it (when it does that), it asks for PIN. So instead of working properly, all I see is ENTER PIN screen.
Anyone else having similar problems? How could I find out what is causing this?
thank you for replies.
I've got the same problem here.
I've read somewhere, that upgrading to the unofficial Froyo Rom solves that problem. But not confirmed so far...
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?