Related
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help
I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix
Are you overclocking the processor? That might contribute to it shutting down.
I do overclock but why do i have to 'battery pull' to make it reboot?
Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.
Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone
Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.
hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone
Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..
This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd
i'm having the same problem
seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.
I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.
The hangs was the only reason I moved to virtududes rogers rom v3
I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.
atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.
Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue
So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?
I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1
I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?
Hello there,
I really am stumped, and would really like some help! I've searched the forums, can't really find what I'm after, so apologies if this as already been asked/answered.
Basically, my G1 hangs a lot when it goes to sleep. I'm running Cyanogen 4.0.4 with an 8Gb Class 6 card - everything was fine when I was using the stock 2Gb card that came with the phone, but after having loads of trouble trying to transfer my apps, I decided to just wipe and start again. The card is Ext2 parted with a 293Mb size partition. I did have it as Ext3, but thought this might be the problem (since I didn't have any problems with Ext2 on my old card), and wiped and repartitioned as Ext2 but that wasn't the case and problems persisted. Occasionally the phone will hang when it is on, but mostly the hanging happens when I leave it alone for a while; the screen stays dark and nothing happens, and I have to take the battery out and restart the whole phone.
One thing to note is that when I did reinstall everything, MybackupPro often didn't like the card, and gave me 'I/O problems with card' or 'Cannot install app' mesaages until I rebooted and started again each time the messages came up. I had to reinstall my apps in 10 - 20 app chunks in the end, rebooting when errors came up, but eventually I got everything reinstalled.
I'm running Swapper (I know Cyanogen does something similar natively, but wasn't sure how it worked...someone please correct me if I shouldn't be using it), and Overclock Widget. Like I said. I never had a single problem before with my old card and these apps, so this all leads me to think it may be the card, but any advice would be much appreciated!
markdjj said:
Hello there,
everything was fine when I was using the stock 2Gb card that came with the phone
MybackupPro often didn't like the card, and gave me 'I/O problems with card' or 'Cannot install app' mesaages until I rebooted and started again each time the messages came up.
I never had a single problem before with my old card and these apps, so this all leads me to think it may be the card, but any advice would be much appreciated!
Click to expand...
Click to collapse
Hmm... sounds like the card to me. And the fact that you are using swapper on a possible defective card may very well be causing your system to hang. The system is relying on the sdcard as part of it's memory. So if the cards fails at any point, so will your phone. It'll be like pulling the RAM module out of your computer while your using it. Include a logcat of the phone crashing if you can and post it. Also reformat and check the partition for errors.
Thanks for your advice, I thought it may be the card too. Partitions seems fine...I used Partition Manager and it didn't throw up any problems.
As for Logcat, I did try and do that, but got a bit stuck trying to fiddle with my computer, and I don't think it's going to happen. I'm a bit of a newbie I'm afraid.
I don't mind getting a new card, but the only thing I'm concerned about is moving my apps...on this post here http://forum.xda-developers.com/showthread.php?t=553469 it looked pretty easy, but could you tell me if these commands are to be executed in the terminal on the handset? Does it copy the apps, because I imagined that if you fiddled with stuff that's in use (like moving an app from the Ext2) would cause a lot of FCs and possibly even hangs.
odd hang
I myself am getting a bit of a hang when waking the phone up, i have to hit the menu button several times, kinda reminds me of the coma issue that we had back on the old kernal. i didn't have a problem till i clean out my phone by wiping and reformating my card, it is not that big off a deal but it is just strange. oh and to the op, you do not need to run openclocker since cyanogen's rom has cpu scaling that does it already and if you have your partions in order as fat,ext,swap than it will auto use compchace
gridlock32404 said:
I myself am getting a bit of a hang when waking the phone up, i have to hit the menu button several times, kinda reminds me of the coma issue that we had back on the old kernal. i didn't have a problem till i clean out my phone by wiping and reformating my card, it is not that big off a deal but it is just strange. oh and to the op, you do not need to run openclocker since cyanogen's rom has cpu scaling that does it already and if you have your partions in order as fat,ext,swap than it will auto use compchace
Click to expand...
Click to collapse
My phone did the exact same thing when I was using either Jac's Hero 1.3 or cyanogenmod 4.0.1. I tried everything and it wouldn't go away so I ended up switching to xrom.
Since cyan has been doing a lot of kernal tweaks lately do you think that it is possible that the coma issue has gotten reintroduce though, I mean both mine and the op is doing it, his is worse but if you remember that is what was happening to a lot before, mine never got to the point of pulling the battery but to the point of annoyance just like it used to
How is the xrom <that's jac's non hero build, right?> is it comparable to cyanogen's, I love cyan's performance but if this persits, I might find something else for awhile
I love it honestly. He just updated it to 1.4r3 and its is sweet, it has a custom theme and it looks really good. The performance is great and I don't even use a swap with it. I tried cyan again when 4.0.3 came out and only used it for 2 days before switching back to xrom. Personally I liked the icons and lockscreen of xrom 1.3r3 better then 1.4r3 but that is just my opinion, If you want to try 1.3r3 I can send it to you since it's not up anymore. Try 1.4r3 first though and see what you think because IMO it is the best rom out. Hero is nice but no matter what you get some lag and after a week or to it gets slower so I don't use it yet, I try the new builds but never stick with them.
Yeah I feel the same way but the hero builds too, nice to play with but nowhere near usable for me, I might just have to check out the xrom but I don't wanna give up loccy's browser, it is just friggin sweet and it works good for me because of the option of viewing just destop versions of sites since I get the men's health daily newsletter and whenever I would click on a link it would give me the moble version and not the article I would like to read, if loccy's brower works on the xrom, we might just have a winner
I haven't tried it yet so I'm not sure. Is it just a simple .apk to install or do I need to push it?
I just read the thread on the browser and it says it should work on xrom. It says to push it but I have just installed it like a normal apk before
Yea I am downloading it right now so I will let you know how it goes. Just so you know the browser on xrom doesn't have those zoom in/out buttons that pop up when you touch it, also it has multi touch just no double tap to zoom. I don't see any settings for turning off mobile pages though.
Well I am downloading the xrom right now so I will be flashing within the next half an hour or so, let me now if the browser works for you, by the way is compchache or swap automatic on it like cyan's or do I need to set it up myself, I perfer swapper, it just seems to work better for me
I think swapper is automatic but to be honest I never have used it for xrom because it is fast enough without it. The better browser works I just installed it normally, no pushing and I am using it right now with no problems, you have a pm.
If you like the notification bar icons in the first picture on the xrom thread they are from 1.3r3 because they changed in 1.4r3. If you want the older ones I can give you that rom amd it runs just as fast, only has a few differences from the newer one.
This xrom is nice, I am happy with the newest, oh and when I installed swapper and went in it was already set at 96mb and swappiness of 80 and I am on a fresh install and reformat so it must be automaticly set to then, explain why it is so smooth. Definitely comparable performance wise to cyanogen so I might have to stick with this for a while
I dont even have a linux-swap partition on my sd and I haven't had any problems with speed or lag.
Mine is silky smooth, better than I have had on any roms even the stock one
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Sound's like Kernel panic. Wipe everything and install soemthing stable like cyanogens 4.2.15.1 or dwangs rom. Didn't know there was anything worng with SuperD's kernel though.
jaekim708 said:
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Click to expand...
Click to collapse
Since the rom relies on apps to sd I would guess the ext is borked and maybe the fat32 as well. I would reformat the whole thing to fat 32 then reformat to ext2 or 3. Load Dwangs rom for testing (easier to get running just as a test).
So I wiped my SD (ext4, dalvik, fat32) and tried cyanogen. Then I tried Pays. Reboot problem's gone, but neither of them is reading my SD card.
I'm assuming its just a matter of backing up the SD and repartitioning? I'll try that next when I have time.
Thanks for the help guys! Lastly, any ideas on why this happened? It'd be hard to pinpoint the exact reason, but I'm assuming I'm not the only one who had this problem - how did other people get to the situation I'm in?
I wiped all of my SD, repartitioned, wiped the phone, flashed AOSP 1.6. w/ root and "expansion" pack.
Reboots are less frequent, but they still occur too often. They don't occur by themselves - its always when I'm using my phone.
It seems that it reboots more when its connected to my computer. The SD isn't mounted, but the simple fact that its connected seems to trigger reboots more frequently. Is this a coincidence or can a USB cord trigger reboots?
Help please
EDIT: The phone just made an audible cracking sound as it rebooted - like someone stepping on gravel. Hardware issue?
This phone is beginning to royally piss me off. I have never had any problems rooting or flashing ANY of my previous Android phones till I got this one, and this one is a freakin' nightmare.
I finally got SRE 1.4.1c working, after adjusting the clock speeds and voltage manually, applied the lagfix, and was enjoying the speed, but I decided to try flashing the latest version of Unhelpful Kernel to see if I could tweak a TAD bit more speed out of it... and now I'm stuck. I created a Nandroid using Clockwork, then did a factory reset and cache wipe (standard procedure on MOST Android phones,) then applied the new Kernel, attempted to boot... nothing. AT&T logo appears, then Galaxy S logo, stays on that for about 3-5 minutes, then black screens and won't respond to power button input until you pull the battery. So I fired up Clockwork, wiped again, cache wiped, then did a Nandroid restore... and ran into the same problem. Won't boot. WTF? Then I tried ANOTHER nandroid I had from before, one that I know worked because I had used it prior... and same issue. Device won't boot past the S logo, just blacks out on me. Any ideas?
I don't have access to Odin at the moment, nor will I for a while. Anyone have any ideas as to why Nandroid no longer does the job it was designed to do on every Android phone on the face of the earth? And anyone have any ideas how I can fix it?
OrionSX said:
This phone is beginning to royally piss me off. I have never had any problems rooting or flashing ANY of my previous Android phones till I got this one, and this one is a freakin' nightmare.
I finally got SRE 1.4.1c working, after adjusting the clock speeds and voltage manually, applied the lagfix, and was enjoying the speed, but I decided to try flashing the latest version of Unhelpful Kernel to see if I could tweak a TAD bit more speed out of it... and now I'm stuck. I created a Nandroid using Clockwork, then did a factory reset and cache wipe (standard procedure on MOST Android phones,) then applied the new Kernel, attempted to boot... nothing. AT&T logo appears, then Galaxy S logo, stays on that for about 3-5 minutes, then black screens and won't respond to power button input until you pull the battery. So I fired up Clockwork, wiped again, cache wiped, then did a Nandroid restore... and ran into the same problem. Won't boot. WTF? Then I tried ANOTHER nandroid I had from before, one that I know worked because I had used it prior... and same issue. Device won't boot past the S logo, just blacks out on me. Any ideas?
I don't have access to Odin at the moment, nor will I for a while. Anyone have any ideas as to why Nandroid no longer does the job it was designed to do on every Android phone on the face of the earth? And anyone have any ideas how I can fix it?
Click to expand...
Click to collapse
Let's just put it nicely and say Voodoo and Unhelpful's kernel don't play nice together. That's all there is to it. As far as my knowledge goes, Odin is your only choice. Borrow a friends computer if you have to.
I am not 100% sure but do you know if the version of are had voodoo 4 lagfix in it? If so nandroid and voodoo don't get along( something about nand not recognizing the ext 4 files from the lagfix. )You have to create a disable lagfix file in the voodoo folder(if you have one) and then reboot returning the files to rfs( undoes the lag fix, but doesn't delete it.) Nand should work then. As far as the no boot I am just a noob and will leave that one to the experts in here (anyone correct me if I'm wrong please) can you get net download mode with your phone?NM saw you dont have access to Odin. How proficient are you with adb?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes, that could be the problem buuuut I used the Ext2 lagfix, not the Ext4 one, so that shouldn't be the issue, I think... I managed to get it back to mostly stock, so I'm going to try manually applying my customized version of SRE 1.3.1c (higher voltage settings and slightly lower underclock) to see if I can get root/sideloading back, then I'll remove the Ext2 lagfix with SL4A and go from there. Wish me luck.
OrionSX said:
Yes, that could be the problem buuuut I used the Ext2 lagfix, not the Ext4 one, so that shouldn't be the issue, I think... I managed to get it back to mostly stock, so I'm going to try manually applying my customized version of SRE 1.3.1c (higher voltage settings and slightly lower underclock) to see if I can get root/sideloading back, then I'll remove the Ext2 lagfix with SL4A and go from there. Wish me luck.
Click to expand...
Click to collapse
Higer volt? Enjoy your brick... going over 1310mV will get your there really fast
designgears said:
Higer volt? Enjoy your brick... going over 1310mV will get your there really fast
Click to expand...
Click to collapse
+1 I don't understand why people are so obsessed with overclocking...the performance increase is nominal, if that.
DemonWav said:
+1 I don't understand why people are so obsessed with overclocking...the performance increase is nominal, if that.
Click to expand...
Click to collapse
That is not what the guy said, re-read the post. He said higher volt with underclock. That is backwards, it should be higher clock with less volts or same volts. And the overclock is not a huge issue keeping the stock voltage, seeing as how people have been OC chips for a really long time without any issues.
Actually, you all read it wrong. What I meant was I raised the voltages above what they were set to in Unhelpful's kernel, not above 1.3v though. The lowest voltage he had set was 100mhz/600mv, I raised it to 100mhz/850mv as my phone can't handle that low of a voltage without freezing. I then increased the other voltages in that pattern, with the top end being 1.1ghz/1250mv. I'm home now, and Odin3 just saved my tail (and my Captivate) so hurray for that. Thanks for all the help.
OrionSX said:
Yes, that could be the problem buuuut I used the Ext2 lagfix, not the Ext4 one, so that shouldn't be the issue, I think... I managed to get it back to mostly stock, so I'm going to try manually applying my customized version of SRE 1.3.1c (higher voltage settings and slightly lower underclock) to see if I can get root/sideloading back, then I'll remove the Ext2 lagfix with SL4A and go from there. Wish me luck.
Click to expand...
Click to collapse
OrionSX said:
Actually, you all read it wrong. What I meant was I raised the voltages above what they were set to in Unhelpful's kernel, not above 1.3v though. The lowest voltage he had set was 100mhz/600mv, I raised it to 100mhz/850mv as my phone can't handle that low of a voltage without freezing. I then increased the other voltages in that pattern, with the top end being 1.1ghz/1250mv. I'm home now, and Odin3 just saved my tail (and my Captivate) so hurray for that. Thanks for all the help.
Click to expand...
Click to collapse
How did we read what you posted wrong? You clearly said higher voltage with slightly underclocking did you not? Glad you got your phone working! Guess it is the lack of info which made DG and I think differently from what you intended to mean.
I assumed you would take into account the fact that SRE is already overclocked/undervolting, so by saying a higher voltage and slight underclocking I had hoped you would interpret that as lower than the existing overclock and higher then the existing underclock. Technically I was overvolting the processor above what Unhelpful's kernel was set, and I did reduce it from the 1.2 clock speed he set, so that technically underclocked it... Oh well, perhaps next time I'll have to be a bit more clear in my meaning. No harm no foul, though; phone is running great @ 1.1ghz/1250mV, 2500 Quadrant score really makes those other "superphones" look... well... not so super anymore. I had Cyanogenmod 6 on my Evo, and it only scored a 1500... anxious to see how this will perform with 2.2, and HOPEFULLY Samsung fixes the lag themselves so we don't have to keep lagfixing the onboard memory everytime... if we could get rid of that nuance, Nandroid and ClockworkRecovery would let us flash on the fly and ROM development would go crazy in here.
Hi all
Ever since upgrading to 2.3.3 I've been having random freezes that usually end up in needing a battery pull or pressing down on the power button until the phone reboots itself. This is with Darky's 10.1, although I don't think it's related to the "Darky parts" of the ROM itself, but something more to do with the OS.
Also, I've felt that the phone sometimes slows down. It doesn't feel like the original lag on 2.1, but rather feels like something's eating up CPU power. This will happen on ANY application, and even when moving through homescreens on TW Launcher or ADW Launcher.
Another thing of note is that it seems to be the UI or input process that hangs or dies or something. Because whatever's running keeps running I just can't make the phone respond to touch or any of the hard buttons. For example, today I was playing Age of Wind (sweet game, check it out) and after like 10 seconds of the game stuttering, the phone stopped responding, but my ship just kept going forward and the other ships were trying to keep up with me. Sounds and music kept going. And after 30 seconds of "inactivity", the screen went to sleep. As you can see everything's normal except there's no input.
So what I'd like is for ideas on how to fix or figure out what's wrong. I'm somewhat tech-savvy so I wouldn't be scared of using adb or some other debugging tool. So far I've not been able to figure out what's wrong because all the logs start over whenever I reboot the phone.
So, any ideas? Any additional information that would be useful?
Edit and update: I've changed the title because this has already happened on different custom ROM's, including Darky and Criskelo.
I have now tested for 5 days on Criskelo's ROM (based on 2.3.4) and it will happen also. So far what I've noticed both on Darky's and on Criskelo's ROMs:
- The phone will work perfectly for about 4-5 days
- On the 4th day it will start stuttering and lagging. That's when I know it's very close to locking up.
- On the 4th day it will maybe lock up once in a day
- After the 4th day it will start locking up up to three times a day
- The lock-up is at the UI level. Applications will keep running, it will ring if you call it, notification sounds are still alive, the screen will turn off normally after 30 seconds or whatever timeout you set up. But input is totally dead.
- When it locks up, both soft-buttons will light up and stay lit.
Possible causes:
- Something related to USB storage or SD card storage. Someone mentioned that it might be caused by the "fast media scanner". It's possible, because on one of my many tests, instead of reinstalling an OS, I formatted the minisd, the internal sd and phone storage and the phone was fine for 4-5 days and then it started doing screwy stuff again. This reinforces the theory that it's something to do with storage. My guess is the OS itself starts degrading the filesystem or handles or something. And my suspicion is that it's something in the /system/dbdata or /cache partitions, not the sdcard or external sd cards. Impossible to know because I have no idea how to debug using adb and nobody has given any ideas on this.
- I'm starting to suspect the BLN support in the kernel. I have BLN turned off, but I'm not so sure.
Hi,
Sorry don't have any answers, but am having the exact same problems on Darky's 10.1. Except I have a TouchWiz4 Port + Galaxy S II Icons.
Hopefully someone will know of this issue! Its starting to annoy me!!
Cheers,
Sunny
Tell me something, when you installed Darky, did you restore your apps via Titanium Backup? Did you select "Restore apps + data" or just apps?
I'm in the process of reinstalling Darky's from scratch, see if that works. If not I might go back to 9.5 or try Criskelo's ROM.
Thanks
Hi,
Nope I didn't backup or restore any apps. My data is all on my SD card and I just reinstall apps.. I came from DebusROM G1.
Thanks,
Sunny
Maybe a factory reset (do it in recovery) would help?
I actually did a factory reset before installing.
@sundazetoo: Do you have Voodoo lagfix enabled?
Last night, while in the process of reinstalling Darky's ROM, I disabled the lagfix (converting to RSF) and after almost an hour i decided to pull the battery. Then when I rebooted again, it went through the conversion process, finished in 2 minutes (wut!) and an error displayed (it couldn't mount some partition, one that I know is not critical).
So I'm suspecting a filesystem problem.
I already installed and DO NOT have Voodoo's lagfix enabled. I also did a complete wipe and restored my apps without data. So far it seems fine but it's only been a few hours.
@Lunchbox115: I did the factory reset when I installed too.
@ferparedes: Yep voodoo is enabled. I am now running on the stock launcher that came with Darky's 10.1 and it seems to be running a lot smoother. I was running a TW4 port so that may have been my problem!
I will monitor it and let you know how it goes.
Have you tried clearing the data / cache for the launchers you are using? That seems to fix alot of FC issues for apps for me.. I guess no harm in trying anyways?
2 days in after reinstalling.
Voodoo EXT4 lagfix NOT enabled. Phone is pretty snappy and I've haven't had any more freezes. I think it was either a bad EXT4 conversion or the lagfix itself was causing it. Anyways, since the phone is pretty fast I'm leaving it with RFS lagfix only.
One thing of note, though. I'm running stock GB launcher atm, because ADW was giving some problems.
Yesterday ADW Launcher *died* and although the phone was working and responsive, the launcher never came back. The result was that when I pressed the home button nothing happened but a blank screen. The power button worked, though, so I was able to do a clean reboot and switch to Launcher.
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Same again
I get these issues too. I seem to get them RFS and ext4 (I think - mostly its been ext4 though). Often get a delay on the keyboard. Its driving me a bit nuts but I am reluctant to go back to Froyo just for this (I hate having to restore all my user names and passwords).
Silly thing is I cannot recall if I got in when I tried Gingerreal (on Darky 10.1 now).
Would love to see thoughts and theories too..
G
UPDATE
After almost 2 days of totally flawless operation, I reinserted my 16 GB Micro SD card with all of my stuff in there. Among many things:
- Audible audiobooks, along with bookmark and "furthest listened" data
- Music, playlists. All created by TuneSync (which I use to wireless sync music and playlists from my PC's iTunes)
- Dropbox download folder
- Photos and videos taken with the phone
- Some other files not associated with any app
2 hours after doing this, blam, the phone locked up again requiring a reboot. So I removed the Micro SD and when I got home I backed up my photos and videos on the PC, reinserted it in the phone and formated the card. This was last night.
So far the phone's working fine.
My current theory:
The Micro SD card I originally bought for the phone was an 8gig. When I got the 16 gig one, I just copied everything from the 8gig onto a folder on the PC, then copied everything over to the 16 one. This might've broken something.
After going to Gingerbread, it's possible that the way some applications look for their data (for example, Audible) changed but when encountering the same data (that was copied over from a windows folder on the PC) it might've generated errors which in turn put the interface into a deadlock.
My strongest suspect is Audible. After installing Darky 10.1, the app just chugged away remembering all my farthest listened to data, all my audiobooks were visible, etc. After reinstalling (and removing the Micro SD) I had to redownload some, but it still remembered where I was and didn't have to reactivate the device. Now, after formatting the Micro SD, I've had to redownload everything, it didn't remember where I was on each audiobook and I also had to reactivate the device.
If the phone doesn't lock up during the next 4-5 days then I'll conclude that errors on accessing the Micro SD by some app was the cause.
sundazetoo said:
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Click to expand...
Click to collapse
Yeah I actually don't think ADW launcher is causing this particular problem. But in a different problem altogether, it did die and in this case required me to do a reboot, albeit a clean one. But if it gave me this one single problem than I'm inclined to stop using it. I don't want the phone disabled for the 3-5 minutes it takes to boot up if I need it in an emergency (it's a phone first and foremost, after all)
tw4 is an EVIL for SGSi9000 imho... because almost everyone have problems with it !!! so just use another Launchers... LauncherPro, Launcher EX (my favourite) but not TW4 )))
I tried to fix with a reinstall of stock jvp and then went to F1 v8 jvp rkm but I also formated ext_sd card as suggested here (and deleted audible application which I was not using.
So far so good but it's only been an hour...
Sent from my GT-I9000 using XDA Premium App
Definitely something related to sd card. Everything is screwy now but less so with the sd card out.
Anyone find any solutions?
I was getting double boot screens and freezes on the dialer. Realized it was the sd when my backup would not load.
Sent from my GT-I9000 using XDA Premium App
Had this happen to me today,
I had the phone boot up and it would get to the lockscreen, then media scan, then it would lock up, only a battery pull would turn it off.
Tried booting without the External SD and it didnt occur, hmmm
Put the microSD card in the card reader on the PC, and performed a scan for errors/fix bad sectors, it didnt find anything but i put it back in and it goes fine now, im sure its the external card.
related info
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
It did it again with the micro sd card out. So today I reformated the internal SD storage (usb storage) and will see how it goes. If this last attempt fails I will either go back to froyo or try another ROM.
But I do think it has something to do with one of the SD card storage.
gfacer said:
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
Click to expand...
Click to collapse
Should be fine
More things to try
Looked at my rom page (F1 JVP) and noticed that V8, which I have now, had the faster media scanner as does Darky's 10.1-which is not getting updates often now it seems. Well the faster media scanner only lasted 2 days until V9 of the F1 rom when the delevoper removed it. My guess it that it was causing issues.
Leads me to wonder if that might be causing the corruption in the first place or at least a contributing factor.
Also read some threads at google about similar issues across a whole wave of devices and one person there mentioned H2testw utility to test the sectors of your SD card. It sounds like cheap ebay sd card and larger SD cards my have more issues (mine is a 32gb). It is best to format and then test with h2testw but I decided to run just on the empty parts of the card and decide from there.
G