Related
Hi folks,
First I wanna take a moment to thank the community for all the great work.
with out your hard work and excellent tutorials I would not have been able to do this on my own.
I Originally had JF1.42RC33, and had used MarcusMaximus's AppstoSD application found here. http://forum.xda-developers.com/showthread.php?p=3627492#post3627492
When JF put out his 1.5ADP recently I went ahead and flashed that without wiping. I also updated the Radio immedietly after flashing JF's ROM. Everything was working fine at this point.
Then when johnowa636 posted his Aero port based on the JF build.
Found here:http://forum.xda-developers.com/showthread.php?t=511183
I decided to flash that, because I really like Aero. Everything at this point was good, with the occasional forceclose error coming from com.vending.something (sorry i just don't remember the excact error)
So recently when Ultra Spikey posted his Aero theme for JF1.5
Found here: http://forum.xda-developers.com/showthread.php?t=482799
I decided to Flash once again the Original JF1.5 I had downloaded from JF's blog. and then I flashed the theme created by Ultra Spikey.
Everything seems fine, but it's not. All the apps installed work and function as they should and the Market sees all my installed apps and purchased apps. it sees them as installed and some have updates available.
The problem Im having is when I clik on update, I get a starting download, but it just sits there and never downloads. I've tryed on both 3G and wi-fi and still it is not working. I also tryed to just download an app i didn't have. and also it would not download.
If anyone can help guide me in the right direction so I can learn what is wrong and how to fix it, I would really appreciate it.
I have the SDK installed in windows XP 64bit and also have a drive I installed Debian 5.0 on. I installed Debian so I could partition the SD, but Im a totall newbie to it.
I hope I've provided enough info. If there is anything else I can add please let me know, And thanks for taking the time to read this.
Something similar happened to me today after I (finally) got A2SD working on JF1.5. Apps were downloading fine initially, but then stalled. Got stuck on the same "Starting download..." step just like yours did. I left it there, remembering people having a similar issue a month ago or so, and eventually they downloaded and installed fine.
Is it just the market throttling people who download too many apps within a short time frame?
Off-topic question. Does the Aero v1.3 theme work with Open Home, or is it purely for the stock launcher?
Thanks for the reply ^^
I'll try just waiting and see if the download issue resolves itself.
I do have open home installed. it seems to work just fine with Ultra spikey's theme. i've a atached 2 screenshots.
Problem is fixed.
waiting did not solve the problem I had downloading apps.
Having no other input for ideas on how to go about fixing this I simply wiped, Reformated the ext2 partition ( just to be sure I started with a clean slate ), and reflashed JF1.5.
I then Applied the Aero theme and Finally used the A2SD method found here:
http://forum.xda-developers.com/showthread.php?t=512743
All is working well
I would close this thread, but I do not know how.
My girlfriend has the Rogers HTC Dream, while I have the T-Mobile G1.
I was able to properly root both phones (although I had mine longer) and I have tried several different roms on both. When we were both running TheOfficial Rogers 1.8.4 and I think 1.9.1, everything was ok. TheOfficial AOSP 1.6 came out, so I took the plunge and tested it on my phone. It was fine.
She kept complaining that her phone was slow and non responsive at times, and indeed it was. I tried flashing the same TheOfficial AOSP 1.6 on her phone and did a wipe. I believe her phone was still non responsive at times, although I can't seem to remember exactly what it was this time.
I then proceeded to install the latest Cyanogen because I was curious and hoping that it could resolve the problems. -My amnesia kicking in again.. wtf?-
I decided to go back to TheOfficial AOSP 1.6. I do the wipe, flash the base rom, then the expansion, then reboot. On first boot, it connects to the GPRS fine. Connecting to the internet will cause the phone to hang. Only way to use the phone is keep it from connecting to 3G/Edge. If I reboot the phone, sometimes it gets stuck on the Rogers screen. When it does boot, it won't connect to GPRS. The only way to use her phone is to wipe and do a fresh flash. Then I won't be able to reboot or else I have to flash again. I have reflashed and rewiped this rom several times already and it's the same.
Anyone know the reason why? I have the correct radio and spl flashed. I have no idea why this is happening. I have flashed my T-Mobile G1 many, many times and, well.. she's using it now. I'm going to try Dwang's rom to see if the same thing happens.
So far it worked. I'm not getting any force closes. I can't figure out why I can't install TheOfficial Donut AOSP on this phone. Dwang's rom doesn't come with terminal or maps. I'm not sure if it's supposed to be like that. I tried the Google Navigation update mod and for some reason that just restored the normal Google Maps on her phone. I'll try it on my own phone later. I'll just leave it at that and won't update anymore unless someone can figure out for me how to install TheOfficial Donut AOSP.
Bye.
Hate to ask you something you might have answered, but are you sure that you have used the EBI1 radio image on the Rogers Dream?
Its me again, my thread got deleted by a mod. He couldve just moved it..but anyways i have tried to get to a solution but havent succeded.
What i have tried is
-Reflashing latest radio
-Tried flashing MCR 3.2
-Tried flashing Sensehero 1.6 (the ROM i used as standard)
Of course i did a full wipe.
Nothing works.
The thing is, i can connect to the internet but browser, facebook, weather or anything cant update or load pages..
Same problem for every access point, and this happened suddenly. Its like, 1 day working and next day it dosnt work.
RADIO: 63.18.55.06JU_6.35.09.26
Currently running MCR 3.2
Latest news
It loaded up google.com, but it took like 45seconds. And loading another page does not work..
same problem ovr here
my hero wont even detect any wifi hotspots
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?
I just recently got this tablet from someone else. (This person had no problems and is trustworthy in reporting all that was done and care taken with it, even offering on advice on things you can do with it.)
My first step was to connect to Wifi. This happened without problems.
When returning home from work where I also connected, my wireless connection(s) said "Disabled" after trying to obtain the IP where they worked fine before. The first time this happened I had to do a factory reset to solve it (hardware reset didn't do it).
Today, it is happening again. I woke it from "standby" to start using again at home and received this message. In fact, any attempted WiFi connections comes up saying "disabled" after attempting to connect and obtain an IP. Again, these are saved connections that previously worked. I know for a fact that it's not the routers.
Please help if you can. I've tried:
1) power off/up 2x in a row to no avail
2) removing and adding back the connection with the appropriate passwords
3) a factory reset but I really don't want to do that again because I'm afraid flashing it back will bring back the same problem.
3) I haven't put any new apps on it since it last worked earlier today so I can't figure that as an issue. The first time it happened a week ago was when I'd just gotten it. It has worked for almost a week without problem. I did nothing special but travel home.
SPECS:
A500 Wifi
Rooted (was unrooted when it first happened); rooted now using IconiaRoot v1.3
(previously rooted and unrooted with Gingerbreak which would no longer root)
ROM: Honeycomb 3.1 with Virtuous Picasso v.1.1.0
Kernel: 2.6.36.4-UNITY-V5-ge7dee2a-dirty
Thanks in advance.
it's a known problem with this tablet when moving from one access poin to another, introduced with the update to 3.1. you have to reset using the pin hole near the micro USB port. i use a staple.
it may take a few tries. if it never works, there's a specific file you can delete if you're rooted. if you cant do that, you will have to do a device wipe.
There is a known issue of connecting to PEAP/EAP networks, which most work networks are. After connecting successfully, often many times, it will suddenly fail to connect. It also shows the signal from the access point to be very low or non-existent. After this happens, it can also cause problems with other PEAP/EAP access points as well.
If this is what happened to you, here's the fix. Try to connect to the access point giving you problems. While it is stuck on trying to connected, click the access point name and tell the tablet to Forget it. Then enter the same access point information manually and try to reconnect. This fixed my problem, and the fix sticks for a few weeks or so until it comes back.
Interesting, I had this same problem a few weeks ago when I visited my parents house. After a couple reboots it just started magically working again and didn't think anything of it. Their router is whatever the Verizon FiOS people install when you get their service.
Thanks, GeekGuy and Falkner, but.....
I've tried both before, but I went ahead and tried both of your recommendations again (pin reset and connection attempt/forget/add). Neither fixed it.
I would like to try to delete the file that Falkner mentioned, but you didn't specify a name and/or location of it. Can you share that?
I could never find what file to delete, so I've just installed a new ROM (thanks to XDA for info on all the how to stuff).
We'll see if it repeats.
Gone from V.Picasso v.1.1.10 with HC 3.1 to Taboonay 2.1 with HC 3.2.
Thanks for the attempted help!
Just guessing but I would say your problem is solved since no reply from yesterday?
Per my last post, I've switched ROMS. As it happened randomly before, I can only wait to see if it happens again. I will post back if it does.
And....as of tonight it happened again.
Note: Different ROM working since the last post 9-26-11.
ROM Taboonay 2.1
The only thing I can wonder about is if it happens when it tries to connect to a network that is actually down such that it cannot obtain an IP that actually gets internet access. However, it was "disabled" when I brought it up before ever trying to specifically reconnect to a network to realize the ISP wasn't doing their part.
Still....no reboots, or hardware resets have worked. I'm working on an image restore of only the system from the 9.25 install of the ROM rather than a factory data reset. Not sure if that would have been better. Trying to save some of what I've done recently. Gonna have to get used to a weekly backup if this is to continue.
Grrrrr..........restoring a backup turned out to be the last ROM. After reinstalling Taboonay 2.1, I still had all my apps and found the same problem. I'm doing a factory data reset as it's the only thing that fixed it before :-(
The only "oddity" I've experienced has been since last Thursday. The Android Market doesn't even recognize now that I have another device. Have communicated with them; they are investigating and saying they have received reports of this on free downloads giving an "unable to process purchase" message. It updates installed apps, but I cannot download any new ones through market, appbrain -even the appbrain app only and not to the market app. I can download through Amazon, so it's the Market issue. Still, that shouldn't affect this issue.
If you have any constructive feedback, I'd appreciate it!
This was happening to me. I had problems with every rom I tried until the following combo: Taboonay 2.2 with Richard's Villain ROM 3.7 kernel. Every other combo would lead to erratic wifi...now it hasn't happened in 2 days. I don't know why this is happening as many of the roms I tried claim to have the wifi fix integrated. I hope this helps. Just flash the latest Taboonay and then the kernel zip file on too of it. By the way, latest rabbinate is 2.2....NOT THE ONE YOU HAVE NOW.
Sent from my A500 using xda premium