Related
Hi! When running ROMs that are "newer" such as 2.2 ROMs they crash/freeze for no apparent reason. With or without an SD card in, everything wiped, newly updated recovery etc etc.
However! When i run a ROM like Kimera 1.8 Cupcake ROM it all floats on perfectly.
I cant see any rhyme nor reason behind the problems im experiencing. Any thoughts? It's really killing me :/
Could you define "crash/freeze" a bit more specific please? Does the phone boot up as normal?
If it just hangs on randomly when using the phone normally, it might be a ROM specific problem (not neccesary 2.2), maybe some app who can't handle 2.2 just yet, or you configured it badly (overclocking?).
As riemervdzee says, more information required.
What ROM are you trying? What radio? What CPU settings if available?
I tried SenseHero (2.1), Froyos and currently running Fusion!ROM 2.2 and they all run perfectly on my G2 Touch (Hero)
It boots up perfectly but then either reboots after random use or just freezes in the sense that i use some app or scroll through the app list or try to make a call and it simply freezes up and is unusable until i remove the battery and reboot.
I am running FROYO_2.2.1_Special_Edition_RC1_update1 and as far as i can think of i haven't configured it anything specific. Is there perhaps a way to reset every setting such as CPU setting etc that might be wonky?
Im running 63.18.55.06PU_6.35.15.14 Radio!
lol i love you're definition of "newer roms" when you've only used 1 rom.
first i'd recommend trying some others. i'm not saying the one you tried is bad at all but it may just not agree with your phone for some reason.
Having said that - if I were you i'd check exactly what you're wiping - it sounds to be that you haven't cleared the dalvik cache or something (i.e. you've not done a full wipe before flashing a new rom).
My new bie guide has the process for flashing a new rom (part 2 i think).
I've run a myriad of roms, im just stating that this is the one im currently running and experiencing problems with.
kloggeboll said:
I've run a myriad of roms, im just stating that this is the one im currently running and experiencing problems with.
Click to expand...
Click to collapse
What exactly is the problem of running an other 2.2 ROM? It could be a ROM specific problem, which frankly occurs at your phone (egh, sometimes happens ).
If you are sure you wiped data, dalvik, cache and ext2 (if any) I really suggest you move to another ROM and see if that one works OK.
I experience exactly the same problem with every 2.1 and 2.2 ROM so i doubt its ROM specific. I've wiped everything. Im quite clueless in this case what the problem might be!
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 am writing on this thread as i still cannot add to the development thread yet
I am using Elelinux-7.0.0-Hero-v2.0. Thanks Ele for a great rom.
So far the only problem i have had is once the unlock screen went invisible on me.
I had to use the patch which worked fine. no black screen. everything else works great so far.
Just trying to contribute to the developers what i can to help.
Any one else has any issue yet.
Elelinux-7.0.0-Hero-v2.0
RADIO VERSION:63.18.55.06SU_6.35.17.03
Kernel: Herokernel-12a
I've had the same issue with the lockscreen but like yourself it was a once off.
Generally the ROM is great (however, this is the first ROM that I've flashed to my hero)
The only other issue im getting is with linking facebook with my contacts; for some reason FB keeps crashing. But keep in mind that I'm a retard in comparison to what you lads know about custom roms etc..... but slowly learning!
Sent from my Hero using XDA App
same problems
I have had the same problems as you. lock screen went invisible a couple of times. and my facebook does not work quite right.
Apart from that has been very stable. no problems or reboots. works great.
Running gingerbread with honeycomb theme on my hero. running at 691mhz is well good.
I have got widgets running on every screen to.
Elelinux RC4 version 7.0 V2.0
kernel 12a
691mhz
clockworkmod.
Thanks Ele for a great rom
After installed 2.0 patch, I still get blank screen (wall paper ok, no any widgets).
The only way to solve is restart
Any thing wrong with my installation? (same spec as above post)
The Bug seems to affect some phones and not others. Might be due to different hardware but not sure.
I am a network engineer. Not a developer.
There is a patch that fixes the black screen bug which might help. You might have to delete dalvik cache first though. But as said not a developer.
I just wanted to try some different roms and loaded cronos rom yesterday and is very good. So running that at the moment.
It is really fast and stable. The fastest i have used so far. But i have not tested everything yet like GPS. But admit i am becoming a cronos fan.
Cheers.
P.s i always backup my phone first and do a complete wipe before trying a new rom. Otherwise could get problems.
I use clockwork mod.
Unfortunately the bug your getting with black screens, invisible menus etc.. is an aosp bug that affects some devices which Google are unable to fix, if you had read through the thread you would have seen this. Ele is working hard on a fix for this but as CM no longer support the hero, its unlikely many cm7 roms will see many updates.
Sent from my HTC Hero using XDA App
Everyone is hoping that Google will fix the memleak and invisible manus problem. To fix it, one needs to undersatand the big picture on how these things are managed. I think it can be done only by experienced coder.
It's a real shame. i love gingerbread and did not want to go back to 2.1 or 2.2.
But might have to if they do not fix it.
I know Ele is working hard on a fix. using his rom at the moment. Was using cronos. But suddenly started getting random reboots and battery started only lasting a few hours and could not find out why.
Thanks to all devs and help.
Elelinux 7.0 v2.1 GPS reboot issue
Hi all,
I found Elelinux 7.0 v2.1 to be almost perfect.
The only major issue so far for me is that when running applications such as sportstracker that use GPS and are running in the background, that as soon as the GPS connection is lost (for whatever reason) the phone always seems to crash.
I wonder whether anyone else has seen this issue and whether there's a way to investigate it.
E.g. is it possible ot redirect logcat to the sdcard and then analyze the log file?
Regards,
MJ
Her0 V2.1 - USB problem
This is a weird one...
I flashed to Elelinux 's fab 2.1 the usual way....
I booted into the ClockworkMod Recovery V2.5.0.7
-- wipe cache partition
-- Advanced - Wipe Dalvik Cache
-- reboot
Then again within Clockwork Recovery I choose 'Install zip from sdcard'
I select the Hero rom and it flashes perfectly...
Now the problem ----> I cant get the usb port working to enable transfer of files?
When the phone boots up it shows 'preparing sd card'
Then when i connect usb lead to pc it shows 'usb connected'
When i then pull the screen down, i see 'usb connected - select to copy files to/from your computer'
When i select that tab, it just crashes back to the home page?
I see the icon at the top of the screen but when i pull down the screen and select as above, it crashes back to home screen again?
In settings, i have both USB debugging and USB debugging notify - all enabled.
Can anyone provide a solution to this issue for me..
thank you
The only way around this problem i think is to mount usb storage from recovery.
Sent from my HTC Hero using XDA App
Hi!
I put my MAGLDR on my HD2 and tried tytungs ICS ROM, was not happy with the performance, went back to Boxmax GB Sense build, but after restoring data+apps the phone will start rebooting every few minutes.
I boot andorid from the SD card, so I tried a few versions of the ROM, v8.5 and v7 ([BoxmaX.S3.5.v8.5][Runny HTC Sensation XL][Kmarc2.1 + KTytung r14]).
Same result, sooner or later it'll start rebooting.
The weird thing is that I got another HD2 which is set up identically (magldr+BoxmaX.S3.5.v7) and is working perfectly for months.
I'd appreciate if someone could give me a few ideas on how to debug this?
kosmarnik said:
Hi!
I put my MAGLDR on my HD2 and tried tytungs ICS ROM, was not happy with the performance, went back to Boxmax GB Sense build, but after restoring data+apps the phone will start rebooting every few minutes.
I boot andorid from the SD card, so I tried a few versions of the ROM, v8.5 and v7 ([BoxmaX.S3.5.v8.5][Runny HTC Sensation XL][Kmarc2.1 + KTytung r14]).
Same result, sooner or later it'll start rebooting.
The weird thing is that I got another HD2 which is set up identically (magldr+BoxmaX.S3.5.v7) and is working perfectly for months.
I'd appreciate if someone could give me a few ideas on how to debug this?
Click to expand...
Click to collapse
When it reboots, is it when you're heavily using the phone? Do you feel the back of the phone getting warm before it reboots? Do other SD ROMs work perfectly? Logically since another HD2 with the exact same setup works fine, I would assume that it's something to do with hardware but I don't really know why something like this would happen so suddenly (assuming it worked fine before you changed the ROM)
Nigeldg said:
When it reboots, is it when you're heavily using the phone? Do you feel the back of the phone getting warm before it reboots? Do other SD ROMs work perfectly? Logically since another HD2 with the exact same setup works fine, I would assume that it's something to do with hardware but I don't really know why something like this would happen so suddenly (assuming it worked fine before you changed the ROM)
Click to expand...
Click to collapse
Ah, some more info: Phone was working perfectly with wm6.5+haret, and with magldr+ICS (albeit with ICS bugs) but no reboots ever though it was always overclocked.
As to reboots, they happen for no reason, even when on stock frequency. I don't even have to use the phone, it'll be sitting there sleeping and I just hear the boot up sound.
And here we go: swapped the sd and sim cards, and it is rebooting even in the other HD2, so it's a software OR SD card problem.
I'll move my data to another SD card to exclude it from the equation, but I doubt it's the card.
Ok, so my procedure to setting up a rom is:
after the 1st boot, either log in in to google or not
install TB, restore apps+data
use MyBackup to get SMSes back
Only after or in the middle of that does the rebooting start happening, once it starts it's game over as I only get a minute or two before reboot.
My idea is that something I'm restoring is causing it, but have no clue what it could be.
My last backup was in ICS, but I have no clue how could that be a problem, apps are apps :|
I'm only backing up/restoring regularapps+data not any system stuff.
How could get to the logs from the data.img? Maybe they'll give me a clue about this?
kosmarnik said:
My idea is that something I'm restoring is causing it, but have no clue what it could be.
My last backup was in ICS, but I have no clue how could that be a problem, apps are apps :|
I'm only backing up apps+data not any system stuff.
Click to expand...
Click to collapse
Hmm, so if it reboots after you restore then perhaps you're right, it may be a problem with something you're restoring. Apps may be apps, but some apps are different for ICS and GB (e.g. YouTube, Launchers, Google Chrome etc.) so it's quite possible it may be causing a problem. Try doing the following:
Fresh install the SD build
Restore apps which you KNOW are the same on ICS and GB. This includes all games and many other apps.
For apps which you aren't sure about, download them for the play store.
Manually restore specific app data for the apps you downloaded
Hopefully, if the problem's to do with an app being restored, this will sort it out.
Nigeldg said:
Hmm, so if it reboots after you restore then perhaps you're right, it may be a problem with something you're restoring. Apps may be apps, but some apps are different for ICS and GB (e.g. YouTube, Launchers, Google Chrome etc.) so it's quite possible it may be causing a problem. Try doing the following:
Click to expand...
Click to collapse
Could be, but I only had ICS running for 10 day and did not install any new apps. I don't have any games
Fresh install the SD build
Click to expand...
Click to collapse
Done that ~10 times.
With different approaches. (Restoring more/less)
Tried both newest v8.5 and v7 (gf's [email protected] is running the v7).
Restore apps which you KNOW are the same on ICS and GB. This includes all games and many other apps.
For apps which you aren't sure about, download them for the play store.
Manually restore specific app data for the apps you downloaded
Hopefully, if the problem's to do with an app being restored, this will sort it out.
Click to expand...
Click to collapse
Yeah, I'll have to do that. I'll see if have the backups before ICS and just put the latest data.
What a chore
Tried another SD card, same happens, so at least I know it's 100% software fault.
How could I check the logs?
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
rocksolidsr said:
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
Click to expand...
Click to collapse
could be a ROM/Kernel pairing. have you tried wiping system/data/internal storage - reboot recovery, then flashing a new ROM?
the static screen is common on custom 4.2.2 ROMs, but it's usually a quick flash. I don't get any random reboots though.
I've tried many different rom's along with the Vanquishkitties kernal but still random reboots
I noticed my phone acting weird, specifically it would not play any audio, I noticed this because when I was in the dialer it was going really slow. Then I tried to play some notifications and none worked. I rebooted my phone and all seemed ok, I've attached two logs the first one being while audio would not work and the second after the reboot. I'm not really sure what to look for in the logs but thought someone here might.
This might be something...
E/AudioStreamOutALSA( 300): pcm_write returned error -5, trying to recover
Or this, just a warning though...
W/AudioTrack( 692): obtainBuffer timed out (is the CPU pegged?) 0x63d72108 name=0x6user=00001000, server=00000000
Sent from my Nexus 7 using Tapatalk HD
Just noticed that when in the dialer and the phone starts working very slow, if I turn the sound all the way off, the phone becomes responsive
two more logcats for anyone interested in helping this time one is when trying to use google voice actions, I actually get an error message that says can't open microphone and the other is when someone called me and I did not have any ringtone but I answered and I could not hear them and they could not hear me, shortly after my phone rebooted, I did not catch the reboot in the logcat.
Also when it reboots it doesn't reboot all the way it boots to the boot logo screen and then hangs and I have to hold all three buttons until it reboots again, is there a way to get it to just reboot on its own?
After the reboot everything seems to be fine until I experience the same issues again
Which ROM are you on right now? That sounds like a kernel level issue
Sent from my XT907 using Tapatalk 4 Beta
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
rocksolidsr said:
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
Click to expand...
Click to collapse
Has your issue been resolved? I am almost facing the same issues of random rebooting with my phone and was searching for a solution....
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
5318008 said:
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
Click to expand...
Click to collapse
Im having this issue and Im on kitkat.