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.
Related
Can anyone tell me if this will wipe any updates etc that have been done to the phone by the phone company?
my phone forgot the lock code so i had to do a hard reset, since then the phone has been freezing quite often, mainly when sending/recieving texts if you change the orientation while typing.
at the moment its either wait 2 minutes for it to sort itself out or just restart sense which is now becoming annoying.
any help appreciated
it also wont play the h.264 recordings i have made on the phone, i just get a black screen that says loading :/
well i have figured out it is definately related to the orientaion of the phone, i cannot turn the phone on its side when sending texts or using the web browsers or it will just lock up or slow to a crawl.
p.s. somone just please reply so i know i aint getting ignored cos my posts seem to be lol
Hmmmm...
Is the issue only occuring since you performed the hard reset and not before?
Have you tried reinstalling any updates you had before the reset?
Do you have a lot of msg's in your inbox?
updates are usually stored in root of phone
have you installed any new cabs or roms ??
if you've not installed anything new another hard reset may be in order just to re-syncronize phone
only help I can give at mo
spookywillow said:
Can anyone tell me if this will wipe any updates etc that have been done to the phone by the phone company?
my phone forgot the lock code so i had to do a hard reset, since then the phone has been freezing quite often, mainly when sending/recieving texts if you change the orientation while typing.
at the moment its either wait 2 minutes for it to sort itself out or just restart sense which is now becoming annoying.
any help appreciated
Click to expand...
Click to collapse
Yeah it will. it is like doing a windows system restore using the restore discs that came with your pc. Personally i would look at updating to a newer rom if you haven't already got a 1.66 or 1.72 based stock rom. You could always look at a custom rom. I use energy 23569 and i haven't had any problems with it. Also the energy roms include a newer version of sense that is included with the new TMOUS roms and it appears to be less buggy
thanks for the replies guys,
it was fine before the reset but it did slow a little in landscape mode but nothing anywhere near what its like now, key presses had a slight delay and now they are like a 5 second delay....portrait mode is perfect.
i always delete messages so my inbox is empty, i never applied any updates prior to the reset, i assumed virgin did it all for me.
i have only installed a few tweaks but the main change is bsb tweaks, i'm now using the latest version where as i was using the prior version before the hard reset but this has only started happening about a week after i installed it.
rom version is 1.66.351.1 (76641) WWE
rom date 03/03/10
manilla version 2.5.19211619.0
OS version 5.2.21869
radio version 2.07.51.22_2
i want to use a custom rom or atleast update to newer one but how will i put it back to the stock rom? the phone has some locked items from virgin installed, they will know if those are not there.
No they won't. Just say you removed them by hand because they were of no purpose to you.
If you install a custom rom on your unbranded, unlocked (the phone virgin supplied you is exactly the same as what you would pay for standalone except for the software extras) Leo it will be easy to install a stock rom. just flash it and then remove HSPL3 in favour of the stock spl (1.42 i think).
Your manilla/sense version is actually very old. There are newer versions about (2015 and 2016) that have been developed for the TMOUS devices but as HTC neglect the UK we haven;t been given the officially yet but most of the new custom roms include them.
If you do stay stock try installing LeoCPUSpeed V4 and chainfire's 3D Driver Patch V2. They will improve the speed of the phone in general and you may find the typing lag goes away completely
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?
Hi all, I was wondering if you could help with an annoying issue I'm having.
I made a big mistake by updating to an ICS Rom, it worked fine apart from the accelerometer which stopped 100%. I did a backup, but system crashed and that's the end of that backup
1: I've since downgraded to Honey Comb Acer_A500_7.14.14_COM_GEN1, but Accelerometer still won't work, I don't know why, is there some fix or file to replace or anything like that.
2: Second question, because I updated to ICS the boot loader got updated also, is there a way to revert the boot loader back to the original so the end product would be a 100% original
This is a 16GB UK version of the A500, so any help would really be grateful. Even if I can get both the boot loader and OS to original I can then send it off to Acer for repair.
Kindest Regards to all
Garret
Man, I don't have an Acer iconia, but I have a Samsung galaxy player 5.0 and I just experienced the same issue after trying an ICS ROM.
When I searched for a way to solve my problem, I've seen many many users (increasingly, indeed) with the same kind of problem. It's hard to think that so many users are having accelerometer hardware fail. I believe it's not physical problem, mostly because this kind of issue happens after ppl try modding their phones/tabs or changing roms. I've seen some users talking about removing a sensorfile yamaha.cfg and trying to reboot the device. That didn't solve my problem, or executing:
"sensorcalibutil_yamaha"
It is under /system/bin/, you can see that with root explore.
Unfortunately, didn't work for me. Hope it works for you.
Best regards.
Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.
Hello, same issue for me, accelerometer doesn't work anymore! I had yesterday the official ICS fota. Is there a patch somewhere for this problem?
after official Acer ICS update - Accelerometer quit?
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.
bthorsberg said:
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.
Click to expand...
Click to collapse
This is the same issue I have on the leak version.
Sent from my PC36100 using XDA
gbyrne2011 said:
Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.
Click to expand...
Click to collapse
I need to do the exact same thing. Could you please let me know what you did to start all over and get all the OTAs?
Thanks!
One could conjecture that if the accelerometer is stuffed, so would the orientation detection be.
Cause and effect?
Z.
Sent from my A501 using Tapatalk 2
Same here but a reboot cured it.
anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.
What did you use to do the downgrade back to 3.0.2?
gr8buddha said:
anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.
Click to expand...
Click to collapse
The only solution I found so far is keepin rebooting, eventually at some point accelerometer starts to work.
Best regards.
Sent from my GT-I9000 using XDA
If any off you had a leak and altered boot loader prior to install, it may have caused that. You should have had a 2 step optimizing process in the update, when I tested it on a leaked/flashed back version the bootloader was wrogn and that issue resulted. The stock had no issue and went through the full hardware optimizing process.
Also you shoudl have applied the market place update first, it has a pre fix to prepare it for patching.
Hey guys, i also have the same issue with accelerometer. I downgraded the a500 to Honeycomb and it fixed now.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1516012
Rollback OS + Bootloader back to Rooted HC 3.2.1
Use this to Rollback OS + Bootloader back to Rooted HC 3.2.1
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS
http://forum.xda-developers.com/showthread.php?t=1516012
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS
the guides to rollback posted above can be used on an official pad , with no hack or root stuffs ?
No, it rolls you back to rooted 3.2.1. with stock bootloader. Once ur back, you can load your official 3.2 rom on an SD, use Pwr + Volume down to update to it. Then OTA to ICS.
Just saw a guy posted a system of methods to completely wipe all the system files (not just most) and clean install ICS which supposedly fixes the accelerometer problem.
Accelerometer / ICS
I sent my tab back to Acer for repair, they say they replaced the "motherboard" and it did work fine on stock ICS as returned for a while. Periodically it would stick in orientation and not auto-rotate, but a power cycle with a few minutes in between seemed to always bring it back ok. NOW - nothing I do brings it back - its working the very same way it was when it originally experienced this issue. I don't want to send this slab back to Acer every couple of months and deal with setting it back up when they ship it to me a week or so later. This is rediculous or am I just being picky?
Anyhow - How bout a reference or link for the info on downgrading, wiping ICS and re-installing from scratch as mentioned above? That would be helpful if I knew where to look.
UPDATE: This morning, based on another post about finding errors in the bootlog, I downloaded the bootlog capture app, ran it, and poof - the auto-rotate function came back to life - like magic. I'm sure it was NOT the app, but rather the fact that I had powered down the unit and let it sit all night long without touching it or powering it on/off, etc. so at least for now, I won't be sending it back to Acer for Warranty repair (AGAIN). BUT I might be listing it rather quickly on ebay and shopping for another tab that doesn't have this issue....
I have had this issue and normally a power cycle fixes it. I did have one time where it did not but I found an article that said to do a hard reset. You do this with a paper clip pushed into the very small hole. I did not lose any data.
Marc
Sent from my A500 using xda app-developers app
take a look at this. It work for me.
http://androidforums.com/acer-iconi...veral-a500-ics-related-symptoms-problems.html........
delete the last dots.
Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:
Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...
what?
i havent got this
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?
Read the freezing thread sticky .
Delete this non working fix as well .
JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?
Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.
Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.
So, it just popped up while my phone was idle, without anyone calling it in here first, YotaPhone finally decided to give us EU users the RU124 firmware! It looks from the changelog to be the exact EU equivalent to its RU counterpart, including YotaTravel, the return of the YotaStore and other stuff. It's been so long that I don't even remember, but I should be fine flashing this and then reflashing SuperSU and Xposed without losing anything, correct?
If you have stock recovery it will install fine. If not you should be able to grab the update zip from /cache and side load. Then reflash what you want.
Sent from my iPhone using Tapatalk
Yep I'm still on the stock recovery (I just boot TWRP every time I need it). Gotcha, then I'm just dumping my Titanium Backup folder onto my PC as a precaution, and then I'll update and report back on SU\Xposed.
Looks like whatever Yota pushed at 117MB was the wrong thing - a failed update attempt and a reboot later, it's now 0.94 GB. Seems like it's the correct size in ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/ so now it should work.
Update from RU1.1.112 to RU1.1.124 issue
https://r.tapatalk.com/shareLink?ur...share_tid=3436224&share_fid=3793&share_type=t
Sent from my iPhone using Tapatalk
Just as expected the 0.94 GB update file worked, I reflashed SuperSU and Xposed and the phone is working great on 1.124b.
What version were you coming from?
Sent from my iPhone using Tapatalk
EU1.87. I wanted to go to the RU version but never could get a KitKat RU firmware to boot on my device, so I just gave up and went back to the latest EU firmware.
Ah OK that makes sense. Glad you got it working.
Sent from my iPhone using Tapatalk
Go mine today (1.1.44HK)
Updated to EU 1.1.124b with official yotaflasher.
No Su nor any hack.
So far no bug, it's a great device.
Hi there!
I'm waiting for my yotaphone 2 from this new wave from chinese shops. I ordered the International version. Is it safe to flash the EU version firmware over the "international" version?
And please, can anyone provide an alternative downolad link for the yota flasher?
The one from offcial website:
https://yotaphone.com/us-en/ypflasher/
is a corrupted zip file.
Thanks!
Edit:
I could get it from here:
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Seems there's a bug.
Almost each time i try to unlock phone (with power button) from EDP the pin keyboard isn't showing up, i must tap all over the EDP screen, way it's relocking then i can have the keyboard again.
Solved by using gesture instead of pincode
satsuki_yatoshi said:
Solved by using gesture instead of pincode
Click to expand...
Click to collapse
Gutted they removed the Instagram Cover instead of fixing it!
Rarelyamson said:
Gutted they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
Instagram restricted access to its API, so none of 3rd party apps now work properly. Thats why Instagram Cover was removed.
Hello
I deployed this great update a few days ago, and it clearly brings numerous improvements and fixes.
One visibly new bug annoys me a lot anyway, and that's why I am posting :
When I type a SMS on the EPD, lots of freezes occur. And today, I found a simple pattern. I type a word, and then I back-delete one or a few letters of it. Then I add new letters, and that frequently freezes the EPD for a long moment.
It's not 100%, lots of times it freezes under these conditions, few other times it does not.
I setup 3 languages to choose from (thanks to the update !) and the auto correction is ON.
Does someone else experience the same issue ? Any workaround or fix ?
Thanks
Appens to me 2 times, each time i needed to look/unlook the edp screen to solve
My problem is that with the latest update I need to restart my phone until it starts charging. Otherwise it will not charge ... does this happen to anybody else? Probably I should try to reset ...
no charge bug here
No charge bug here neither. Quite the opposite in fact, I would even say that autonomy obviously improved since this update.
And I confirm I have the same bug with the PIN keyboard not showing up on the EPD when using the Powa button. It happens very often after using the other screen, but unlocking by tapping twice is an easy and efficient workaround.
Surprising obvious bugs anyway, I hope the Yotagods watch us and intend to fix them.