n00b help! Tombstone problem [fixed] - Defy Q&A, Help & Troubleshooting

Yesterday I flashed maniac103's latest CM7 build. Before that I used a couple of Euroskank builds, after several months using Quarx/Eppy 7.1-11-11-11.
Today I have run into the Tombstone problem with no free space on the phone. I moved a couple of apps to SD, but the tombstone immediately fills out any empty space that I can create.
I've searched and the general advice is "delete the tombstone file". Great... except I can't find it? When I browse /data there is nothing there. Is this a permissions issue? Any advice on how to solve the problem and prevent it recurring?
I would be extremely grateful for some help, in simple english and with big pictures and chewable pages ideally...

Ok, I have managed to fix it myself. For any other challenged users, here it is
My problem was that the standard file manager could not see anything in /data
I tried using terminal, but equally that would not allow me to do an ls in /data (view a list of the files in /data).
This came down to a permissions issue.
Earlier on I had deleted Adobe Flash player, which seems to be regarded as the root cause of the tombstone problem. However, I still had no free space (at all - 0.00MB available). After removing Flash player, I uninstalled another app (google+ simply because I don't use it and it's big - 22MB). After uninstalling I had 14MB showing free, which allowed me to install Yaffs explorer. This allowed me to browse with superuser enabled - now I could see the contents of /data, and find the /data/tombstones folder, and find the 905MB file that was causing all of the problem. Deleting that file (tombstone_09 in my case) solved the issue.
Hopefully this will be of help to someone equally as clueless as I.

I just had this exact same issue. Inside the tombstone folder I had tombstone_00, tombstone_01, tombstone_02 and tombstone_03. The first 3 were about 60 Kb each, but the fourth one had 885 Mb. Deleted it and it's back to normal.
This is the first time having this issue, I was using CM 7.1 for almost a year and switched to CM 7.2 last month.

Thank you so much, had this issue, without your post I wouldn't know what to do
Sent from my MB525 using xda premium

Well, the problem has reoccurred, although I now have the tool to fix it.
So my next question...
What causes the problem? How do we stop it happening again?

maniac had been looking into it and told us, that he maybe screwed up on something when he compiled the build that was supposed to fix this issue.
The builds from yesterday on should limit the filesize of tombstones to 1MB correctly.
If it doesn't work, don't blame maniac for this, because it's Adobe's fault. maniac is simply not able to look into code from 3rd party apps.
I also had big tombstones especially when watching flash-videos in the browser. So far they're gone. But you could try to trigger a tombstone that way...
Greetz, Unr3aL67
Sent from my Defy via Tapatalk

I'm not blaming maniac103 - I am extremely appreciative of the work he has done along with that of Quarx, Epsylon and others.
Last night I updated to 16th may build from Maniac, so will keep an eye on things.

Related

VEGAn-TAB has reached BETA STATUS - We need your help!

Roebeet, Rothnic, and Myself have been hard at work to bring you what we hope will be the killer ROM for our G-Tablets. Now that we have hit BETA status, we are interested in hearing your feedback including issues and feature requests.
The projects git home is here: https://github.com/gojimi/VEGAn-TAB
(here you will find all project code and mods. we are using a free account there and space is limited so ACTUAL RELEASES will happen in the Thread that Roebeet has already started)
Issues and feature requests can be followed and posted here: https://github.com/gojimi/VEGAn-TAB/issues
(please read before posting new issues or features request so we don't fill up with duplicates. you may also vote up the issues you feel are most important and we can concentrate on those areas based on your feedback.)
The wiki for VEGAn-TAB will be here: https://github.com/gojimi/VEGAn-TAB/wiki
(there is nothing there yet.... but as we approach a production stable ROM we may be adding some info here)
Thank you for all your support and patience as we iron out some of the more major issue. (ie. SSL! phew so glad we figured that one out..... such a simple mistake too!)
I am usually buried in CODE or REWORK of current framework that I don't come up for air to check XDA much.... But I do watch the GIT Repo and I will try to make a greater effort to keep an eye on this post.
For questions to issues that you are having but others aren't your answer may still be best answered in Roebeet's post.
--GoJimi
_____________________________
VEGAn-TAB Developer
The single issue I am having is random factory browser crash, and It is the reason that I have kept the tablet.
Can you guys include a tun/tap module to allow OpenVPN to work?
I can't get the Ad Hoc Tether to work from my rooted Hero phone. I had it working on the Zpad with this fix: http://www.chinadigitalcomm.com/android-a81/a81e-connect-to-ad-hoc-wifi-t1413.html
Any thoughts? Anyone else able to connect to an Ad Hoc Tether?
Edit (Fix) I was using the wrong fix. The fix it to apply the wpa6_adhoc-signed.zip
This was the fix I initially did on the Zpad rom, I just messed up and did the wrong fix...
I had a problem with the sound, sdcard, fc on websites, and changing the soft buttons. It was killer despite those issues. Also rotation of the home screen.
Sent from my PC36100 using XDA App
Do you guys still been able to copy the files from laptop to G Tablet running beta? I can't do that. Is there any trick to it or you guys using 2nd SD card?
2k3Mach said:
I can't get the Ad Hoc Tether to work from my rooted Hero phone. I had it working on the Zpad with this fix: http://www.chinadigitalcomm.com/android-a81/a81e-connect-to-ad-hoc-wifi-t1413.html
Any thoughts? Anyone else able to connect to an Ad Hoc Tether?
Click to expand...
Click to collapse
I had the same issues
I installed the WPA_adhoc-signed.zip and it solved my tethering issues. I tried to find the orginal post with the link to he downlaod but couldn't find it.
I know that there is talk of it in this thread
http://forum.xda-developers.com/showthread.php?t=842004&highlight=wpa_adhoc
and this one too
http://forum.xda-developers.com/showthread.php?t=854682&highlight=wpa_adhoc
The only issue I have so far is with Grooveshark FCing. Sign up and tutorial screens work fine but the actual interface never loads. Otherwise, great work on this. Its very responsive and other than the GS FCs I have no FCs.
Thank you guys for your hard work.
Wanted to answer a few of the questions. If I forget you I apologize.
OPENVPN support- we'll look into that feature for the future. (MAY not make it into betas)
wpa_supplicant issues.ie adhoc tether. This is an oversight. Should be in next beta
Most of the sound and stock browser FCS have been fixed(Ssl now works)
SD card issues. We are aware and they are all potentially related to a hack we implemented to get external sd support working. This issue includes the internal SD disappearance when connected to pc via usb. This is my PRIMARY focus right now.
Again thank you all for your patience and feedback.
Is there a way to change the launch applications along the bottom? Even if it's a file to modify.
2k3Mach said:
Is there a way to change the launch applications along the bottom? Even if it's a file to modify.
Click to expand...
Click to collapse
Tmk, it's not fixable. It seems to be hardcoded, silly as that may sound.
gojimi said:
Wanted to answer a few of the questions. If I forget you I apologize.
OPENVPN support- we'll look into that feature for the future. (MAY not make it into betas)
wpa_supplicant issues.ie adhoc tether. This is an oversight. Should be in next beta
Most of the sound and stock browser FCS have been fixed(Ssl now works)
SD card issues. We are aware and they are all potentially related to a hack we implemented to get external sd support working. This issue includes the internal SD disappearance when connected to pc via usb. This is my PRIMARY focus right now.
Again thank you all for your patience and feedback.
Click to expand...
Click to collapse
I plan on making a supplement or maybe a full image with the same supplicant binary in TnT Lite, plus that updated Gallery and a clean hosts file.
Working on TnT Lite 2.3.0 primarily at the moment, however. I guess I need two devices!
Another random question. .. I am on Tina lite 2.2 and find it to be super stable and flexible. I am concerned about what will happen when the battery gets to low : )
What happens with this rom when the charge runs out?
With b3 I find that I have to clear devoric cache after each shutdown or I lose the ability to run certain apps. Any suggestions?
ssmithri said:
Another random question. .. I am on Tina lite 2.2 and find it to be super stable and flexible. I am concerned about what will happen when the battery gets to low : )
What happens with this rom when the charge runs out?
Click to expand...
Click to collapse
I've only had battery die once, on TnT Lite. Didn't seem to cause any issues, just needed to recharge.
NMCBR600 said:
With b3 I find that I have to clear devoric cache after each shutdown or I lose the ability to run certain apps. Any suggestions?
Click to expand...
Click to collapse
I have not, but I have big issues with going back and forth between builds - I can't do it with this beta or else I have a big freezing problem, and apps go missing.
Can Not build VEGAn-TAB from source ???
I tried building the source from
VEGAn-TAB git hub
But it seem that there are missing. When I ran
repo init -u < the url submited in this thread for the git> ( it does not allow me to add urls)
I received the following error
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
Is it possible to build VEGAn-TAB from source? If it is can you please let me know how?
Thanks
what do i have with VEGAn Beta4??
the only issues i have with this rom is with sdcard2 or the microSD card, only when i put jpeg files in it and i open the gallery to load them and when i do a reboot all the pictures are gone from the microSD card, but just the pictures i can open the music player and play all songs and reboot and they still in there the issue is only for me with image files. After i update the kernel with the patch that has been post on the vegan beta4 topic i think this is almost perfect....i hope you can fix the files getting erased on the microSD card.....but after all you guys are doing and amazing job with all the ROMS you have made....i'm very gratefull for all the work you have done, you make love more this tablet....thanks a lot!
elrafa_paez said:
the only issues i have with this rom is with sdcard2 or the microSD card, only when i put jpeg files in it and i open the gallery to load them and when i do a reboot all the pictures are gone from the microSD card, but just the pictures i can open the music player and play all songs and reboot and they still in there the issue is only for me with image files. After i update the kernel with the patch that has been post on the vegan beta4 topic i think this is almost perfect....i hope you can fix the files getting erased on the microSD card.....but after all you guys are doing and amazing job with all the ROMS you have made....i'm very gratefull for all the work you have done, you make love more this tablet....thanks a lot!
Click to expand...
Click to collapse
Look and make sure there is NOT a .nomedia file in your picture folders, that will prevent them from showing.
Sent from my SGH-T959
the problem is not the files are not shown on the gallery, the problem is that the pictures are all deleted after i open the gallery and makes the pictures appear in it, so when i reboot the tablet all my pictures get deleted, even if a browse the microsd card with my computer and not in the tablet...all the files are gone!....
elrafa_paez said:
the problem is not the files are not shown on the gallery, the problem is that the pictures are all deleted after i open the gallery and makes the pictures appear in it, so when i reboot the tablet all my pictures get deleted, even if a browse the microsd card with my computer and not in the tablet...all the files are gone!....
Click to expand...
Click to collapse
I got the same thing tooo. also all my movies get deleted too
At this point the sd card2 is Clean

Help with increasing phone internal storage / Data.img size

I am currently running Superram 1.5 and am trying to increase the "internal" storage of the phone. I have skewered the forums and I understand this involves increasing the Data.img size beyond the initial 256mb compaction. Using TopoResize I have resized my data.img to 1.9 GB, however, i still had access to only 256 MB. I reinstalled Superram 1.5 and tried again with a fresh data image and also failed.
Can someone point me in the right direction, please?
Is there an XML i am to edit or something so the system recognizes the change?
App2SD just isn't cuttin it.
Much thanks to anyone who can help.
Well once the data img is used I don't think you can simply just enlarge it, it has never worked for me that way.. The only solution I can think of, is for you to get a new data image, a bigger one than the one you currently use, and restart your rom with that data img. You can find lots of Build threads with blank data images in them, eg. JDMS/MDJ. If you want to back up stuff, use titanium backup from the market.
data image resizing
Firstly, that should read "scoured" lol -not skewered. And "compaction" should read capacity. Sorry, was trying out swype with XDA App.
Now, more impotently. When you say "restart your rom," you mean to just substitute one image file for another in windows and restart superRAM, correct?
I will not have to reinstall SuperRAM 1.5?
Also, since superram runs off the RAM of the device, will using a image file from a different build cause a problem?
Finally, has anyone out there increased there Image file in size via TopoResize and had success? Was it before the initial launch of your android build or after?
Any help would be much appreciated. Thanks all
Kailkti said:
Well once the data img is used I don't think you can simply just enlarge it, it has never worked for me that way.. The only solution I can think of, is for you to get a new data image, a bigger one than the one you currently use, and restart your rom with that data img. You can find lots of Build threads with blank data images in them, eg. JDMS/MDJ. If you want to back up stuff, use titanium backup from the market.
Click to expand...
Click to collapse
I big to differ. It can be increased. I used to do that during my android SD days.
@OP, you haven't scoured "a lot" yet. Search for datai.img maker, it can resize and create data.img.
Sent from my HD2 Droid HD using XDA App
Issue resolved
Issue resolved.
In the interests of others who may encounter this problem, here is the solution.
Simply get titanium backup and back up all your apps and info, then find a 2GB image from another build and substituted the old image file (data.img) with the new image file (renaming in appropriately) and used titanium backup to restore mostly everything. Titanium backup does a very good job restoring, even Astrid tasks returned, yay.
I originally didn't what to attempt this because SuperRAM is a unique build in the way it runs but there seems to be no issue.
One thing did come up, however.
I attempted to use a 4GB image as a replacement at first and that did not work.
Something about it being too large.
I read someplace that android has a difficulty with image files larger then 2 GB, can someone confirm?
Resize
@Jose - I have tried using toporesize, It seems to increase the size of the data.img but only allow me to use the original 256MB. End result is ineffective.
thedarklion said:
@Jose - I have tried using toporesize, It seems to increase the size of the data.img but only allow me to use the original 256MB. End result is ineffective.
Click to expand...
Click to collapse
Sorry but I did not suggest toporesize but data.img maker.
Sent from my HD2 Droid HD using XDA App
jose makalolot said:
Sorry but I did not suggest toporesize but data.img maker.
Sent from my HD2 Droid HD using XDA App
Click to expand...
Click to collapse
Easy enough mistake to make, but toporesize is data.img maker. To OP (and for posterity's sake), I don't know if you tried it but if you tried making a new data.img using toporesize/data.img maker, you "should" have achieved about the same effect. Glad you got this solved though.
Hey Guys. How are you toady?
I come here with new problems! Probably this thread is solved but i got problem with Toporesize.
Anyway I solved why my Android crash all the time! Was the sd and now I installed few games but I will be glad to install Chainfire also but no way to go true because I do not have storage enough.
I try to use toposize to resize my data.img (inside i have many app and I did a backup) but I got this error, see pic.
If I make the fresh data.img no problem, but the Android do not turn on with "new" data.img, i looking just to resize mine without compromise it.
someone know how to do it?

"bugreports" folder on SD card

I've been having some SD card issues lately. Primarily, it is filling up constantly. I would delete photos, videos, and music, and a day or two later it would be nearly full again. Started digging through folders on the card and came across a folder named "bugreports." This folder seems to fill itself daily with 50 MB .txt files that contain a bunch of system dump information. I deleted 8 or 9 of them on Sunday and now have 6 more present. File title is: bugreport-2011-01-31-13-00-29.txt for example. Essentially they are bugreport-year-month-day-hour-minute-second.txt. They are generated throughout the day. A lot of mentions of Wifi in the text, as well as a few mentions of Root Explorer. Don't know what else really. A 50 MB text file contains a LOT of text. I would post one, but I'm concerned about personal information in the files... and it's 50 MB!
Only other reference I found to this problem was here: http://forum.androidcentral.com/htc-mytouch-4g/51568-bugreports-file.html
Not a lot of responses. Hopefully this gets a bit more discussion here.
Any ideas as to what could be generating these files and WHY?
File typically starts out with:
========================================================
== dumpstate: 2011-01-31 23:06:42
========================================================
Build: FRG83
Bootloader: 0.86.0000
Radio: 26.03.02.26_M
Network: T-Mobile
Kernel: Linux version 2.6.32.21-g899d047 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Oct 26 16:10:01 CST 2010
Command line: board_glacier.disable_uart2=0 board_glacier.usb_h2w_sw=0 board_glacier.disable_sdcard=0 diag.enabled=0 board_glacier.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.03.02.26_M androidboot.cid=T-MOB010 androidboot.batt_poweron=good_battery androidboot.carrier=TMUS androidboot.mid=PD1510000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=SH0CSRM07618 androidboot.bootloader=0.86.0000 no_console_suspend=1
------
This is followed by MEMORY INFO, a bunch of lines, CPU INFO, a bunch of lines, PROCRANK, VIRTUAL MEMORY STATS, a bunch of lines, VMALLOC INFO, a bunch of lines, ... etc.
Last section is:
-----------
<4>[ 522.264282] KinetoThread 1996 878562.464595 319220 120 878562.464595 4486.511104 355834.014873 /
<4>[ 522.264831] KinetoThread 1999 878562.434078 319078 120 878562.434078 4638.366746 360224.884030 /
<4>[ 522.265472] R dumpstate 2515 878562.037349 1247 100 878562.037349 3249.267594 26802.429198 /
<4>[ 522.266021]
[dmesg: 0.1s elapsed]
My guess is Wifi calling which is an absolute must for me out here in the sticks. Any suggestions?
EDIT: Forgot to mention. I'm occasionally temp rooted for Titanium Backup. As of this morning I have some Apps frozen, but this problem precedes the frozen apps.
Thanks,
Ryan
Ry-Guy615 said:
EDIT: Forgot to mention. I'm occasionally temp rooted for Titanium Backup. As of this morning I have some Apps frozen, but this problem precedes the frozen apps.
Click to expand...
Click to collapse
I think it might be because you're temp rooted. Try perma-rooting and see if that fixes your issues
This happened to me on my Nexus One all the time. When rooted, pressing the Volume up and trackball buttons at the same time caused it to make a log dump.
Did it almost every time I pulled it from my pocket, and it bogged down the phone too. Might be a similar issue for you.
Okay... That is a possibility. I've felt the phone randomly vibrate in my pocket yet there is no message or notification. This generally would happen when I would move in such a way that the phone had pressure on it. I've not checked to see whether or not new dump files were created along with the vibration. Will check next time it happens.
Did you ever come up with a fix?
Sent from my HTC Glacier using XDA App
Well today I had the phone go through a number of random vibration events and subsequently there were about 5 more bugreport files generated this morning. SD filled up to capacity and now only only mounts read only. Can't delete the files from my phone (need to plug sd in to a computer) and can't access the sd card at all if I try to go to /sdcard.
I also have a directory called /mnt. In this directory there are three folders: asec, sdcard, and secure. If I click secure, I end up in a folder with the same three folders. In fact, I could go to the directory /mnt/secure/secure/secure/secure/... On and on until the file system errors out which force closes the file explorer. The asec folder contains app data for two apps that have components installed on the sd. The sdcard folder contains the entire contents of my sdcard which I can't even view by looking at /sdcard. It is all visible if I look at/mnt/sdcard. I don't get it.
This is getting odd and rather annoying. Any help would be greatly appreciated.
Sent from my HTC Glacier using XDA App
Did you ever figure this out?
I am seeing these files on an HTC Inspire 4G.
Did u try formatting the sd card? Theres probly a currupt file somewhere & causin it to act up?? Ive never heard of this issue before?
Permrooted S=off-MyTouch 4g-White
Eng-0.85.2007
Clockwork Recovery-3.0.2.4
Rom-RoyalGinger v1.4.1(Gingerbread baked just right : } )
I haven't tried doing anything to fix this. The last "bugreport" file was 5 days ago. I'm going to see if I can figure out if it correlates with anything (debugging apps, force closes, etc.)
I just cleared the 'bug reports' folder in my sd card and I have noticed the random vibrating while pressing the volume. Is there any way to disable this?
Is any one figured out of these dumps?
Is anybody have update on these dumps?
I have HTC Inspire (Froyo 2.2.1) it has also generated random dumps. I also noticed couple of random vibrations but haven't checked that it generates dump or not.
Also i haven't noticed that any of the application crashed in past 1 month which can generate dump. Seems everything works fine but still i can see atleast 2-3 dumps generated daily on random time.
They are generated when the menu and back keys are pressed simultaneously.
Sent from my HTC Vision using XDA App
One quick reminder...
After you delete the 'bug reports' folder it is stored in your .trashes
Go into Astro and delete all files in .trashes but since so far there is no fix for disabling this just repeat this every few weaks.
Saved me 5gb
ESKIMOn00b said:
They are generated when the menu and back keys are pressed simultaneously.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Agree, although can't confirm which buttons. If you press those buttons, you will get your phone to vibrate and you'll see the bug report on sd
Happened to new several times. Case closed?
Sent from my HTC Glacier using XDA App
Noticed the same thing on my Glacier... Bugreport directory filled with dump files. Confirmed pushing the Back and Menu keys simultaniously generates the files. Couldn't generate the file with my wifes Glacier phone. Figured it wasn't an Andriod thing, it must be a particular app I have on my phone. Killed apps one at a time and kept trying the menu/back key. When I killed Oruxmaps, the menu/back key wouldn't generate the bugreport files. When I reloaded the Oruxmaps I could do the menu/back keys to generate the bugreport files. I've got an email into the developer for confirmation that it's coming from that app.
My earlier post pointing a finger at OruxMaps was wrong. Sorry Orux. Turns out the log is created by ADB. Take a look at:
ht-tp://wiki.cyanogenmod.com/wiki/Logcat (delete the dash between the ht-tp for the link to work, system wouldn't let me post a link. Don't worry, it's not spam.)
See 'magic key combinations'
Looks like a smoking gun to me...
Sam
Sent from my HTC Glacier using XDA App
Afters routing my Nexus S, I experienced the crashreports as well. I found out that activating 'USB debugging', as adviced by Titanium Backup, caused the problem. So (temp) switching off debug mode solved the problem for me.
BTW the 3 quick vibrates for android usually means that a app in the background has crashed and that is what usually generates a bug report.
hi
Hi! How can i disable this useless function? There is a script or a flashable zip? Please someone answer me
i also wish to disable this feature because my phone lags for a moment when it generates these files, plus there like 1.20Mb each! they bulild up.
xdarkmario said:
i also wish to disable this feature because my phone lags for a moment when it generates these files, plus there like 1.20Mb each! they bulild up.
Click to expand...
Click to collapse
Me too!!!!

[Q] Cache folder shows 100% usage

Hello all,
I actually have an Acer S120 but I figured I would give it a try anyway as it seems to be an Android issue rather than device specific. I recently tried to update my phone to 2.3.4 using Gingerounay 2.0 (made by Vache over at MoDaCo). Anyway it seems that after flashing, I am no longer able to download apps from the market, which is caused by my Cache folder "thinking" it is 100% full. I have tried to clear this folder through recovery, through fastboot, adb & through ES File explorer on the phone itself but i'm not getting any results. The only folder/file that is showing up is the lost+found folder but there are no files within this directory. I am able to successfully clear out the lost+found directory but still my cache reflects 100% usage.
I am really not sure what to do at this point and I'm hoping someone here has some ideas to help me out.
Thanks in advance.
Are you sure the access rights are correct?
The folder should be r/w and have rwxrwx--- (or 770) new files created there should have access: rw-rw-rw (or 666) or at least; that is the behavior on my Acer Liquid E (Android 2.2)
Thanks for the reply. I have already sent my phone back for service and they ended up replacing the entire board. I tried everything to clear it and apparently it was a H/W issue...hopefully no one else runs into the same problem.
Oddly enough; only problem I had due to the full/corrupted cache was that I couldn't download apps from the market. I was able to install from my SD card though.
FYI for this thread. If anyone else experiences this problem; its a hardware problem. My phone was sent back to Acer and they had to replace the board to fix the issue. Hopefully no one else encounters this!

[SOLVED] Market FC - com.android.vending not responding.

Hello everyone I flashed the new CM7 update recently and after that no matter what I do I get this error. I don't usually write for help, usually I find my answer from google and try everything, but I guess I already did that I'm really desperate, please help me I've tried everything...
- Reflashing Gapps
- Clearing the Market (and associated apps) Cache
- Fixing Permissions
- Wipe Data, Deleting Dalvik Cache
- Installing the latest Market (installs, but the error still remains)
- Replacing market related apk files with root explorer manually
- Formatting everything, re-flashing rom, re-flashing google apps (and all of the above after that) and still no go
I'm using the latest nightly PLEASE HELP! I've never screwed that bad before
P.S.: Info about my phone in the signature!
KoolSavas95 said:
Maybe its a bug of the new nightly?
Click to expand...
Click to collapse
Thank you so much for your reply! Maybe it is.
- Unfortunately noone else reported it in the time being, thus meaning it's not.
- Fortunately I haven't tried flashing a stable release in a long time... probably never so It's a must to give it a try! Maybe even an older Stable release (still cm7 though). I'll wipe everything, flash it and if it's good I'll backup and upgrade to the latest again, if the problem comes up again - you were right, I'll restore the backup and wait for the next release, if not... even better, thanks again! Didn't thought of that.
In the mean time other suggestions are accepted as well, I'll report later what happened!
I dont think this is related to rom. I cleared the data and cache of google play a couple of days ago. It started force closing after that. Tried reflashing, uninstalling the update and even advanced restore of system (as I replaced vending.apk with another one) but it didnt solve it. At the end I did a full restore of my nandroid which solved the problem..
saadislam said:
I dont think this is related to rom. I cleared the data and cache of google play a couple of days ago. It started force closing after that. Tried reflashing, uninstalling the update and even advanced restore of system (as I replaced vending.apk with another one) but it didnt solve it. At the end I did a full restore of my nandroid which solved the problem..
Click to expand...
Click to collapse
Hm nice to know, unfortunately I've lost my nandroid backup... (it was on my flash drive, the next moment it's gone...) Could you possibly back up your market with TB and share the backup file from your SD card? Or at least send it via PM :?
**Double post intended to bump **
Banging my head against the wall here, but I feel I'm getting close! It turns out it's some kind of permissions problem (tried fixing permissions about 100 times) still no go.
Here's a log cat from the market on a clean brand new installed CM7 nightly (latest again):
Code:
06-04 01:27:33.952 W/PackageManager(229): Unknown permission com.android.vending.permission.UPDATE_MARKET_FAILURE in package com.android.vending.updater
Anyone knows how to fix this? The device is currently formated from head to toes. Gonna install a different ROM on it tomorrow and swap Cyanogen after that =/ Hope this helps, cuz I'm running out of options here.
EDIT: OMG Just tried the splash mod after wiping everything... SAME PROBLEM :O I guess the problem is in gapps? or my sdcard maybe... or CWM I have no idea...
HipHopBlond said:
**Double post intended to bump **
Banging my head against the wall here, but I feel I'm getting close! It turns out it's some kind of permissions problem (tried fixing permissions about 100 times) still no go.
Here's a log cat from the market on a clean brand new installed CM7 nightly (latest again):
Code:
06-04 01:27:33.952 W/PackageManager(229): Unknown permission com.android.vending.permission.UPDATE_MARKET_FAILURE in package com.android.vending.updater
Anyone knows how to fix this? The device is currently formated from head to toes. Gonna install a different ROM on it tomorrow and swap Cyanogen after that =/ Hope this helps, cuz I'm running out of options here.
EDIT: OMG Just tried the splash mod after wiping everything... SAME PROBLEM :O I guess the problem is in gapps? or my sdcard maybe... or CWM I have no idea...
Click to expand...
Click to collapse
I run the latest Nightly Build after I really needed to use my video camera as that does not work on Erwin's ICS for now. No issue with my Market but one thing that could cause this is your MTD partition. I use 180 20 on the latest build (Nothing added, nothing removed in the ROM). Hope it helps.
olu.danNY said:
I run the latest Nightly Build after I really needed to use my video camera as that does not work on Erwin's ICS for now. No issue with my Market but one thing that could cause this is your MTD partition. I use 180 20 on the latest build (Nothing added, nothing removed in the ROM). Hope it helps.
Click to expand...
Click to collapse
MY F***ING HERO!!! After 4 days... 4 miserable days...!!!
Moral of the story - You shouldn't set 150MB for the ROM and 10 for the Cache partition
Just to make sure I set 250 for the rom and 40 for the cache (like the original partitions of the wildfire) - voala... Now I'm gonna lower them, but it's good to finally see where the problem was. One beer from me dude! /Changing the topic name now
Final Decision: Rom:160 Cache:20 works like a charm.
Glad to hear you solved the problem. My internet went down yesterday so I couldnt reply you.
Sent from my HTC Wildfire using XDA
HipHopBlond said:
MY F***ING HERO!!! After 4 days... 4 miserable days...!!!
Moral of the story - You shouldn't set 150MB for the ROM and 10 for the Cache partition
Just to make sure I set 250 for the rom and 40 for the cache (like the original partitions of the wildfire) - voala... Now I'm gonna lower them, but it's good to finally see where the problem was. One beer from me dude! /Changing the topic name now
Final Decision: Rom:160 Cache:20 works like a charm.
Click to expand...
Click to collapse
I am still thirsty buddy... I'm glad that helps... Enjoy!... LOL
-EDIT-
There is a new CM7 Nightly Build... I am flashing later.
sorry if this sounds like a silly question, but I've searched around and was not able to find any clue... I do think I'm experiencing the same problem (even if it worked flawlessly for weeks...)-- HOW can I set the cache?
thank you in advance!
f
HipHopBlond said:
MY F***ING HERO!!! After 4 days... 4 miserable days...!!!
Moral of the story - You shouldn't set 150MB for the ROM and 10 for the Cache partition
Just to make sure I set 250 for the rom and 40 for the cache (like the original partitions of the wildfire) - voala... Now I'm gonna lower them, but it's good to finally see where the problem was. One beer from me dude! /Changing the topic name now
Final Decision: Rom:160 Cache:20 works like a charm.
Click to expand...
Click to collapse
MTD - How to?
HipHopBlond said:
MY F***ING HERO!!! After 4 days... 4 miserable days...!!!
Moral of the story - You shouldn't set 150MB for the ROM and 10 for the Cache partition
Just to make sure I set 250 for the rom and 40 for the cache (like the original partitions of the wildfire) - voala... Now I'm gonna lower them, but it's good to finally see where the problem was. One beer from me dude! /Changing the topic name now
Final Decision: Rom:160 Cache:20 works like a charm.
Click to expand...
Click to collapse
Guys - you make it sound like breeze to change the MTD partition?!? I have now used several days searching the net to try to figure out how to do this - but with no luck. All I've benne able to figure out, is that my Galaxy Gear has MMCBLK type partition and not MTD. But can you please explain to me how to change it?
Rgds
Viking

Categories

Resources