Related
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
Is anyone else having this problem?
I've got a Rogers HTC Magic, and whenever I've tried a ROM with Android 1.6 or greater (I've tried 3 or 4) the accessing the camera will cause the phone to reboot itself.
It doesn't happen the first time I use the camera, but it does the second time and consistantly.
Does anyone else have this problem?
1.5 ROMs are fine. I'm currently using cursorsense and it's not an issue but at some point I will want to use a newer version of Android.
I have the same problem :x
Relash the rom. If you are using any of the legal roms (cyanogen/superd) flash the base before the rom. remember to wipe before starting.
I've tried cyanogen 2.1 test2 and Smoki both causes reboot when using camera apps (barcode scanner, google goggles, fxcamera, ...).
It doesn't reboot always tho like 1/3 times i use one of these apps i get a black screen and then a reboot.
Im using CursorSense now and all the camera apps work just fine :s.
Always did a wipe before flashing the roms.
Known issue. Been dealing wirh this for a long time on my Rogers Magic. I think the trouble is the devs dont have this model, and no one has submitted useful logs. http://code.google.com/p/cyanogenmod/issues/detail?id=792
The new Android Market (vending.apk) had lot's of alignment issues on MIUI ROMs. Here's a fixed vending.apk that Absolute on MIUI-Dev put together. Just flash it and enjoy!
DO A BACKUP BEFORE INSTALLING! It works for some but for some it causes FC's. There's currently no information what's causing this.
http://www.mediafire.com/?z55qwqw5wmwtxx5
Original thread: http://miui-dev.com/forums/showthread.php?1196-New-Android-Market&p=13875&viewfull=1#post13875
Still not working. Force closes every time
No issues for me, simply flashed and all is good. Fixed the alignment issues aswell.
Have you tried removing the old market app and then try installing this one?
cobz91 said:
Still not working. Force closes every time
Click to expand...
Click to collapse
There are some random issues with new market and MIUI. When I first installed the market I pushed it via ADB and that caused the market not to work. The next time I flashed a zip and it worked. I've seen people reporting that sometimes it takes many attempts to get it to work.
Fc on my Desire too...removed old market first ... What now?
Send by me! d[°_°]b
Toisan said:
Fc on my Desire too...removed old market first ... What now?
Send by me! d[°_°]b
Click to expand...
Click to collapse
You made a backup right? You should be able to find the old market somewhere by googlint it. What MIUI version are you using btw? I consider it weird that it works so randomly.
Managed to install 1 app, then force closed the whole time. Erasing user data didn't helped.
Hey, running 12.11, at the beginning it works and i downloaded some apps, than it crashed, tried to delete, wipe cache and reflash the zip, but now it crash every time im startet it twice... Btw, old market is ok, backuped it!
Send by me! d[°_°]b
Well that's definately weird Have any of you tried installing it a few times again? Like I said earlier I had crashes at first install but after recovering and installing again it started working correctly.
Jiia said:
Well that's definately weird Have any of you tried installing it a few times again? Like I said earlier I had crashes at first install but after recovering and installing again it started working correctly.
Click to expand...
Click to collapse
Wiped rom, reflashed 2 times, didn't helped.
EleCtrOx666 said:
Wiped rom, reflashed 2 times, didn't helped.
Click to expand...
Click to collapse
On my the same, wiped, new flash, nothing woukd help, have to wait for later reales of the market, or change the rom xD but nope, i can w8, now i have to put the market back on my Desire, its not an Android Phone without an Market app
see u!
anybody know if this works on the dinc?
it works for me..try this method
i dunno if thisll help anyone but ive been trying for the past week relentlessly to get this to work and i think ive found a solution..at least for me..
i did a clean wipe [data and dalvich] twice to be safe even with amon_ra's..i know its amon's but im just picky
installed miui 12.3_final.zip and booted into it WITHOUT installing the new market yet, and then i opened up the old market to make sure even that was working and to get everything in the cache's memory
reboot..
install barnacles-update-vending-v2.2.6.zip [he claims this fixes the fc issues]
reboot..
let everything load and try the market it should work..it did for me
reboot..and installed the 12.3.1.update.zip over that and it still worked..
the alignment issues are still off so far and i havent tested the fixed alignment .zip yet and ill update after i have..
if anyone is successful in this, or unsuccussful let me know
i have a stock miui kernal also so that might be it...i dunno yet
im flashing the trickle battery kernal now, update in a bit
credit goes to barnacles for his work
Found the solution!
It was by matlacki, basically just reflash stock ruu 1.32, re-root and restore your nanadroid and it's all good.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
==================================================
Btw i am using build 30
For those who having this proximity sensor issue like myself , I done a test.
Go to setting > CyanogenMod setting >display > automatic backlight > > tick use custom > edit other levels.
For me I can see my sensor functioning will. 7 for total darkness and 59 for din light and 190+ for lamp.
Now try to make a call and watch the screen go off. You can't on it back but there's still ringing tone.
I used my nexus one flash to shine on the sensor and my screen turned back on.
Now go back to the edit other lvl notice that the light sensor doesn't response to the different brightness.
A reboot will fix the problem but if there's s phone call,this bug starts again. Try it!!!
And share your results. If there's ppl with the same as mine, it might be a cm7 bug and not s proximity sensor failure
Its not a CM7 bug. I have never had the proximity sensor problem on any ROM, be it stock or otherwise.
I'm also using build 30 and no proximity sensor problem to report.
i want to believe its not a CM7 bug.
For the past 2 weeks when I was using various CM7 builds, I do not have any proximity issues as described by other users till yesterday, it just popped up.
Nandroid to my old backup (which has no such the problem), and problem still persist.
flashed back to RUU 1.32 rom and the sensor is working in sense rom.
So now i cant even send back for a replacement.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
This problem started yesterday evening for me. 5days of CM7 without issues and now this dealbreaker. Need to pull battery after end of a call.
Sent from my Desire HD using XDA App
try flashing 1.32 RUU and redo the whole rooting again > and back to CM7.
seems unreal but it really did solve my problem..
Okay...
I'm having the same problem, i just checked it with the program "Sensorlist" which gives me info about the proximity sensor....
With CM7 it doesn't work, but with stock rooted ROM it works fine...
So it must be a problem with the CM7 software....
Has anyone solved the problem, so it doesn't come back?
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
My findings (with input from Apache14):
- The proximity issue only affects those with a non-Sharp LCD.
- The kernel source code released by HTC does not contain the correct code to handle this device. I am still looking for solutions.
- On the 1.32 kernel, when proximity is required, some polling mechanism is activated. I assume this is needed as there is no Interrupt hooked up on a hardware level on this LCD/chip (same sensor uC however).
- There is no source code for this. Not in HTC released kernel source or CM or AOSP.
Currently I am looking at either:
- Getting the latest source code for the DHD kernel which HTC has failed to release. The source code corresponds to some RUU older than 1.32.
or
- Hacking the kernel to do the same polling as present in the 1.32 kernel binaries.
McKebapp said:
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
Click to expand...
Click to collapse
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Numsefis said:
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Didn't remove them from the ROM.
I simply unticked them while/before restoring my FullBackup with TitaniumBackup.
For those that cant get proximity sensor to work on custom kernel/ROMS, try the following (no root required):
Code:
echo '0x50530b0c 0x140b0b0c' > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
This will adjust the calibration values. The 0b part is the 'low tide' aka FAR start and 0c is the 'high tide' aka NEAR start.
IOW, values below FAR start is FAR, and values above NEAR start is NEAR.
Tested this on latest Buzz (Apache14) kernel.
Need to somehow make this persistent, and make sure it does not get reset during normal operation.
Stay tuned
Update: Still thinking of how to apply this at boot, maybe 'init.d' ? Also havent been reset during normal operation.
Thanks for the info
ok but how do you appli that ?
Text editor ? etc.
Flashing default (stock ruu) kernel
did it for me. Prox sensor working as intended.
Sent from my Revolutionized Desire HD using XDA App
I wrote an app to fix this.
See http://forum.xda-developers.com/showthread.php?p=11312762#post11312762.
Great work Leppie!
I had this problem, wile on CM6, started after I installed ADW EX. Used to use launcher pro, but realy liked the transisions in ex, so started using that, and got this problem. Updated to CM7, stil had the problem, no matter rom version. Went back to launcher pro, and now it works like normal. Thinking ther might be something with the launcher, and mabye a hardwere thing in some phones.
I am now on nihtly CM7 34, I think, and no problem.
So for those having this prob, try to switch to another launcher, and reboot a couple of times.
Hope this helps
how did you downgrade?
with Recovery?! or with Gold card?!
i have done both ways but didn't solve my problem :-(
please give me a link of Stock rom ruu!
i used to love miui for my I9500
but lately its causing me hell
i dont which update started it but my BT isnt working at all, once i switch it on and try to connect to any device its crashing
my cell signal goes kaput for a minute and then comes back, and it cycles all over again
same thing happens when i try to use wifi hotspot
i get crashes when watching youtube videos sometimes
i tried starting all over again, flashed a stock rom and then miui after wiping everything of course
and still after a fresh install it happens again
what am i doing wrong ?
maybe its my kernel ?
the only thing thats conssistent is after i flash a stock rom, i flash cwm recovery, does it comes with a kernel that could be not compatible with miui ?
is there a recommended kernel that should work better ?
AzurA86 said:
i used to love miui for my I9500
but lately its causing me hell
i dont which update started it but my BT isnt working at all, once i switch it on and try to connect to any device its crashing
my cell signal goes kaput for a minute and then comes back, and it cycles all over again
same thing happens when i try to use wifi hotspot
i get crashes when watching youtube videos sometimes
i tried starting all over again, flashed a stock rom and then miui after wiping everything of course
and still after a fresh install it happens again
what am i doing wrong ?
maybe its my kernel ?
the only thing thats conssistent is after i flash a stock rom, i flash cwm recovery, does it comes with a kernel that could be not compatible with miui ?
is there a recommended kernel that should work better ?
Click to expand...
Click to collapse
Yes, Somehow it is not stable yet maybe. My I9500 with the latest MIUI 5 4.12.5 suffer a few problem, but BT is ok, hotspot ok too. when turning on hotspot it will force close, but the hotspot is turn on e few seconds later.
the main problem is when I flash Gapps. the phone get freeze and restarted.
I tryed another release but the same problem still happen with Gapps. without GApps the phone works properly.
h6x said:
Yes, Somehow it is not stable yet maybe. My I9500 with the latest MIUI 5 4.12.5 suffer a few problem, but BT is ok, hotspot ok too. when turning on hotspot it will force close, but the hotspot is turn on e few seconds later.
the main problem is when I flash Gapps. the phone get freeze and restarted.
I tryed another release but the same problem still happen with Gapps. without GApps the phone works properly.
Click to expand...
Click to collapse
well about gapps
what i do is go into the bulit in Market app
type google play at the top
and download google installer
from there install what you need
AzurA86 said:
well about gapps
what i do is go into the bulit in Market app
type google play at the top
and download google installer
from there install what you need
Click to expand...
Click to collapse
I've tried it. but google play service doesnt work properly... so my phone live with no gapps... T_T