I finally finished compiling an aosp build. But when i boot it sticks on the htc incredible screen and the logcat shows http://pastebin.com/YNvdwqA2. Anyone have any idea how i can fix this problem?
i wouldnt know how to fix it, but i can say that the dalvik cache is shot.
Sent from my Incredible using XDA App
i think it has something major to do with D/dalvikvm( 204): Unable to process classpath element '/system/framework/servic es.jar'
i think it was services.core....which is the main part or dalvik
Sent from my Incredible using XDA App
please anyone, im still having these problems when using my build
did it build successfully.?
Sent from my Incredible using XDA App
yes, and it installs completely fine
Related
Ok so I have done a few full wipes with cm7 and miui and everytime car mode turns on randomly and I can't get rid of it, its been happening since I tried the sense 3.5 rom
Maybe something to do with that, I can't find any settings for it or processes but it in notification bar running and I cant stop it from going into car mode
Someone please help
Sent from my Desire HD using xda premium
Now I can't access emails, the market or anything Google
Browser works and xda and settings are working right
Sent from my Desire HD using xda premium
Do a full wipe again, if you get access to the market anytime soon download lookout and let it scan your phone. But best bet start from scratch
Sent from my CM7 Nightly HTC Desire HD
Turns out it wasn't a virus, its the USB port thinking its docking lol
Sent from my Desire HD using xda premium
Im trying to port a android 4.0.4 rom called Qiss Me using cm9 nightly as base but i get non stop bootloops logcat says something like media.audio flinger died media.camera died audio policy died
using htc desire rom with cm9 base thanks i cant upload the logcat as im not near my pc
Sent from my PC36100 using xda app-developers app
Why do most roms OP state to "fix permissions" directly after flashing the rom, when that does nothing... it fixes them in .3 seconds? lol.... pretty sure it's best to do it after setting the phone up the way you want. Where it takes a couple minutes and actually gives you a log of what is fixed. Just curious if I'm wrong in thinking all this jazz.
Sent from my SGH-T999 using xda premium
I had no idea either. But this cleared it up for me.
http://wiki.cyanogenmod.org/wiki/Fix_permissions
Sent from my Galaxy Nexus using xda premium
Probably just because it can't hurt to do one, that and if an issue arises they can be certain that it was done.
Sent from my SGH-T999 using xda premium
Ive wondered it myself. Never do it though. To me its there for when you run into problems with FCs and such. I assume its the devs trying to be proactive for those who dirty flash.
Ive seen it screw things up to btw.
Sent from my SGH-T999 using xda app-developers app
I know what Fixing Permissions does, just why they tell their users to fix them before anything can be broken, is where my curiosity begins, if I remember right even after a dirty flash they don't wont be fixed til after a reboot...
my way of doing things
wipe data/system/cache
flash rom
boot up>let sit for 5 minutes>install through TB or recover data
boot into recovery and fix permissions, which takes a couple minutes, if I have errors.
Congratulations, no one cares.
psykhotic said:
Congratulations, no one cares.
Click to expand...
Click to collapse
True story, I'm a terrible person.
Sent from my SGH-T999 using xda premium
only fix permissions if you have issues of force closes or log cats are showing files as unreadable... basically if you are having issues of some sort.
also, good idea to fix permissions from terminal while booted into android if you are using a recovery that has not been updated in a long time
cobraboy85 said:
only fix permissions if you have issues of force closes or log cats are showing files as unreadable... basically if you are having issues of some sort.
also, good idea to fix permissions from terminal while booted into android if you are using a recovery that has not been updated in a long time
Click to expand...
Click to collapse
Oh, I know how to run and use fix permissions. I'm just curious as to why some rom cooks give instructions that are useless.
Sent from my SGH-T999 using xda premium
That's a valid question.
I think it's an instruction for crack flashers.
It levels everything out.
Especially, if you are trying to keep your data
Sent from my SGH-T999 using xda premium
********UPDATE*********
Thanks to hardcore,I found a fix in another thread
forum.xda-developers.com/showthread.php?t=1843837&page=4
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Ever since Jellybean instead of apps force closing as they normally would my phone becomes unresponsive and reboots after 2-3 minutes.It gets quite annoying and I wanted to know has anyone else has been getting this issue. I have wiped dalvic/cache also factory data reset,I am unable to do anything in anycut,the phone automatically goes through freeze process,any ideas on how to fix issue?
got the issue too. Only on tw based roms tho. why i only **** wit cm10/aokp. And anycut doesnt work completely with jb yet. You have to use the anycut widget instead
Thanks for the response I guess the only way to stop the problem is not to have a tw Rom,I guess I might just have to bit the bullet on that one,im not really into flashing roms I'm only rooted for hotspot and system settings to change certain things
Sent from my SPH-L710 using xda premium
Could always setup the dualboot to have stock and an aosp rom
Okay I might have to look into that, thanks for the quick responses I thought I was the only one, my friends have s3 to add well and was not experiencing issue,I can see now that's for top them not having stock Rom
Sent from my SPH-L710 using xda premium
You could also find out what process is causing the bad behavior, what's not playing nice, and remove or freeze that app. You could also try to do a fresh install of your rom.
I was getting the same issues, but I found out that Maps social pin-point (Latitude) was causing my issues and unchecked all of the options related to check-ins and location sharing. No problems since.
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Sent from my SPH-L710 using xda premium
brianhot1 said:
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Click to expand...
Click to collapse
For that specific problem, it was trial and error, but a logcat would help. At the time, I couldn't figure it out. I believe there's an app to help read logcats.
Okay thanks
Sent from my SPH-L710 using xda premium
I found one app that was freezing for me I cleared data and uninstall updates for play store, the issue still happens sometimes though
Sent from my SPH-L710 using xda premium
Download Fast Force Close it really helped with the extremely frustrating freezes.
https://play.google.com/store/apps/details?id=com.issess.fastforceclose
Sent from my SGS3!
Cool so how exactly would the app help me if you don't mind me asking I see that it produces the fc would that help in fixing the freezing issue? And if so then how
Sent from my SPH-L710 using xda premium
Any update? It still happens?
Sent from my SPH-L710 using xda premium
Did you use the app? It seems that the app triggers a force clse popup if (im guessing here) a certain amount of time has gone by (like the OS itself does, but maybe shorter) or whenever an app goes unresponsive (it comes up instantly)
So either way, its supposed to fix the force close dialog not showing up for you.
I have our installed but I guess im still working on how to use it, I'm going to try to run it in the background
Sent from my SPH-L710 using xda premium
Update!!!!! Thanks to http://forum.xda-developers.com/member.php?u=336619
Thanks for the tips guys. This was also irritating me to no end on several Samsung roms. I think it happens on the Note and S3 too. Maybe even the S2.
My solution was:
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Sent from my SPH-L710 using xda premium
Great tip. Had never heard of this before.
Sent from my SPH-L710 using xda app-developers app
Just wondering if anyone can tell me whether its necessary to revert to dalvik before dirty flashing nightlies. I got stuck at boot when leaving ART enabled, so I've been switched to dalvik before flashing. Is this standard procedure? Its kind of a pain, didn't know if anyone was having luck leaving ART enabled. I'm running vanir btw. Thanks in advance.
Sent from my Galaxy Nexus using xda app-developers app
D1BB said:
Just wondering if anyone can tell me whether its necessary to revert to dalvik before dirty flashing nightlies. I got stuck at boot when leaving ART enabled, so I've been switched to dalvik before flashing. Is this standard procedure? Its kind of a pain, didn't know if anyone was having luck leaving ART enabled. I'm running vanir btw. Thanks in advance.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm running vanir too. With ART enabled. The boot does take longer with ART. And after boot it will optimize apps which takes ages with ART. I'm flashing nightlys with ART enabled and no problems here. Just some patience friend
Sent from my Galaxy Nexus using XDA Premium HD app
No problem here. It takes a bit longer than dalvik, but it's normal due to the difference between them.
Sent from my Galaxy Nexus using xda app-developers app
Thanks a lot, that'll save me some time. I waited about 4 minutes which is how long it usually takes to originally enable ART and nothing was happening so I figured it was stuck. This was also many builds back. Thanks again guys.
Sent from my Galaxy Nexus using xda app-developers app
D1BB said:
Thanks a lot, that'll save me some time. I waited about 4 minutes which is how long it usually takes to originally enable ART and nothing was happening so I figured it was stuck. This was also many builds back. Thanks again guys.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Try a clean flash. I had that same issue. Then did a clean flash, switched to ART and everything was fine. Maybe let it boot for 15 minutes or so before doing this..
Sent from my Galaxy Nexus using XDA Premium HD app
Flashed 1/31 nightly only wiping dalvik /cache with ART enabled and it started optimizing apps in 4 or 5 minutes. Just noticed 2/1 is up, hopefully I get the same results.
Sent from my Galaxy Nexus using xda app-developers app
CyanogenMod
Hi, have anyone experience with cyanogen?