So I've tried everything I could think of. Reflashing ROM, using a different ROM, different browser, everything minus a different modem, which I'm not sure would really do anything. But where I'm at is that anytime I go to status on facebook it closes the browser back to the home. I'm on Frozen ROM at the moment, I've tried on stock, same issue. Tried on the ASOP ROM, same issue, tried on those ROM's with Dolphin, Miren, Firefox, Stock Browser, all the same issues.
So will a modem actually make a difference is how the phone handles? Or is it more related to data speeds? I don't know what else to do, this is driving me absoluetely nuts. Thanks Guys.
Try this go into settings / manage application / all application & wipe data from browser & wipe data from Google search then reboot if that doesn't work I don't know
Sent from my Nexus S 4G using xda premium
Figured I would move it to the proper area. Haha. I really appreciate all the help Bro. Tried the other route you said, nothing doing. So I don't know either. It's annoying though. I think I got the phone into a bootloop now tried to install a different ROM see if that would work, and doesn't seem to be working. Piece of crap. Just my luck. Ha.`
What kernals were/are you running?
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
odin back to stock
and clear out the sd card. redownload everything and rebackup.
Did you uninstall the Facebook app and redownload it? Wipe data in it before uninstalling. Did you try a different browser like Miren or Dolphin?
xTMFxOffshore said:
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
Click to expand...
Click to collapse
Well, you aren't running without a kernel - the kernel is the core of the Android operating system.
Maybe you're having a hardware issue, such as a touch screen that's acting up (you said it wasn't force closing or anything, right?) - it could be registering false touches in the wrong location... I'm just taking a shot in the dark on this one, since it sounds like you've tried restoring just about everything...
I would suggest reformatting your sd card (copy the contents to your computer first, the card WILL be erased).
Then, Odin a full stock tar (try DI18, you'll get an OTA to EC05 after you boot).
Then use the one click root and recovery - be sure to have the rom on your sd card, especially if you use an ext4 recovery like 3.1.0.1, because of the file system conversion (stock kernel won't boot ext4, so you'll need to flash the rom and an ext4 kernel before rebooting from recovery - Genocide or ACS's twilight zone or vision kernel... I would stick to Genocide for now, under worked the best for me)
You might want to skip the rooting step momentarily, so you can see if the same problem occurs on a completely stock setup.
Finally, I would suggest carefully cleaning your touch screen with something mild - I use eyeglass cleaner (safe for glasses with all the expensive protective coatings), other users here might have other suggestions.
This should cover all of your bases, and if you still have problems, it might be a hardware issue.
I do want to point out that (unless I'm missing something about what you're trying to do) the facebook that you access from the browser is loaded from their servers every time you connect - it isn't software on your phone. It cannot be the older version, not like an app, which has to be updated on your phone. The pandora issue sounds like a different issue, but I still need to test that (had to get to sleep last night, I was passing out mid-sentence, lol)
EDIT: re read the first post... Pandora issue was mentioned in the SRF thread... But it seems you did try stock and other roms...
When you say it closes back to home, I think I misunderstood - I had an issue once or twice where facebook would act up, going back to my facebook home page, but did you mean that the browser simply closes and dumps you back to your phone's home screen?
Because that could be as basic as your capacitive home button registering a false touch (the opposite of the unresponsive button issue we're all used to, lol)... But cleaning the touch surface could still help... Turn the phone off first, and apply whatever cleaner you use VERY lightly... Don't use household cleaners, if you don't have eyeglass cleaner then I would research whether rubbing alcohol is safe for gorilla glass...
Side note - swype suggested "guerilla" glass... made me chuckle...
Sent from my SPH-D700 using XDA App
What he said. ^... Also I would let it
Repartition and reset time when you Odin back to stock. I know most people say not to when flashing some things, but this would be an exception. Also when you flash to stock use the victory.pit file as well as the ROM tar.
Sent from my SPH-D700 using XDA App
All righty. I'm gonna try all that. As really nothing else has worked. I do think it's something with the screen though.....I just can't figure out why it only happens on the NEW facebook. I got her using the APP now she was only using the browser before, but I would punch say four letters it would bump a couple more then close. So you may be onto something with that touch screen registering incorrect keys so would that have anything to do with the contents of the SD card itself? Or is that an actual hardware conflict with the facebook (newer version) of the software? Cause it works fine on the APP. So I guess I'm basically at a loss for how this really makes any sense ,but really appreciate all the help from you guys.
Related
Hi All,
I have a problem where my phone crashes and reboots when I launch an app that uses the camera in any way, for example layar, barcode scanner, camera etc. This only happens in Android 2.1, I've tried various ROMs and always the same issue. I've tested Android 1.5 and there are no problems with that at all.
I've noticed the crashes only occur when I'm on battery power, it never happens when the phone is plugged in so I cannot get logs to see what is going on, unless someone knows a way to get the logs from a crash.
I was wondering if anyone else has seen this problem and if so, if they've found a resolution to it.
Since updating with the OTA 2.1 update I have been experiencing this problem too. Phone reboots when it uses the camera, Layar, Yelp, AugSatNav all seem to cause the problem.
I get this problem too, with the camera, and also sometimes when I put the volume down it freezes and reboots
Sent from my HTC Hero using XDA App
I've got the same problem. Restarting when launching apps using the camera.. Im glad that's not a HW problem but "only" SW bug.. I hope
It could (and probably is) a radio issue....Happens on the N1 and Desire if you try to use the camera too and seeing as the GPS,Camera both are dependant on the radio id say that is it! Find the radio reccomended with the rom you use and flash it( Beware of orange users being locked down though,you need a specific radio)
Just to add that I'm getting the same problem too running FroydVillain 1.2.2 and baseband 6.35.15.14, should point out that been having the problem for quite a while on a multitude of ROMs :-(
I'm not - did you full wipe?
Multiple wipes...
try 1.3 i guess
I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App
Tried multiple ROMs and multiple Radios with no change :-(
Unless theres a second secret wipe button hidden in recovery I don't know what else I can do :-/
try to disable "automatic brightness"...
Gynjanynja said:
I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Hi,
I have had this problem since i went to 2.1 also, i have also flashed several rom's since villainrom 12 and have even used rcmix 1.0b which is a great 2.1 imo.
Have flashed 2.2 roms, and i am still having the same problem.
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Some things to consider.
The phone will never reboot if it is plugged in to a usb / electric plug Charger and is actually charging.
The phone will remain on and will carry on taking pictures IF you don't close out of the camera the first time around.
No task killer was installed on my phone at the time of this test, although i have had task killers before with the same results.
Lighting effects and brightness can sometimes have an effect on the ratio and probablility of a reboot, with brightness on full in a dark room being the most probable.
I am using the newest froyd rom 1.4.3 although i have tried pretty much every rom out there, I NEVER have this error when i installed a 1.5 rom which does not have apps2sd (weird that) which tells me that it is NOT a hardware fault.
I am using villains no logo kernel 19mhz - 691mhz
63.18.55.06PH_6.35.15.14 Radio
HTC Hero on Orage UK.
IF anybody can shed any light on this rather annoying matter resulting in this problem being erradicated will earn my eternal respect and a big clock. : )
dladz said:
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Click to expand...
Click to collapse
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I originally posted this issue and the descriptions from everyone else with the problem match mine pretty much perfectly.
I've taken all info off the sd card and performed a complete wipe of data, ext and davlik before formatting the sd card. I've put the blank SD card (apart from the ROM I'm about to flash) back into the phone and flashed. After config and before any new apps are installed on the phone I launch the camera and within 4 attempts at start the camera the phone will crash. This has happened across every 2.1 ROM I've tried, but doesn't happen on 1.5 ROMs.
Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?
btdag said:
Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?
Click to expand...
Click to collapse
Yep, it crashes using the stock app.
I've tried a rooted version of the offical but not the actual OTA update. I've not tried vanilla as I don't really want to run vanilla on it.
I've managed to take some logcat logs of the problem happening but there's nothing really specifc happening over a few crashes that would point to anything. .
I'm going to try to unroot my hero and downgrade to stock to start again. Just have to find a way to downgrade my bootloader first so I can put on the original RRU. I tried to downgrade before but got an invalid bootloader error.
The camera crash doesn't really affect me day to day as I don't really use the camera, where it is annoying is it stops you using apps that use the camera like goggles and layar.
Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.
btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I have formatted and re partitioned my sd card to a T and it still occurs and thats with everytime i install a new rom, i don't use titanium i go the long way around every time and re set up all my programs, I know i can replicate this error like i said and like i also said this does not occur in 1.5 roms.
I have also have this problem with vanilla, modaco's new one, villain rom, rcmix, froyd, it appears that ever since the phone was updated to 2.1 there is a problem when using the camera app.
I have tried to install a rom and replicate the issue without installing any apps at all and it still persists, the only thing i can say is that it doesn't happen when i'm either on 1.5 OR the phone is charging?
It sounds like the the phone is requesting access for use of the camera and then not putting back what it requested in the first place, like a cache or something, and it simply make the phone reboot when it is called upon again.
I don't believe it is a hardware fault, i know this sounds like wishful thinking but the phone does not have this error in 1.5 roms. Thus, it cannot be hardware. Simple!
Also a logcat does not show anything, i was only able to replicate the error once whilst my phone was plugged in, it just won't do it again, and when i posted my findings on villainroms bug report section, a few of the lads still didn't know what it was so i don't know what else to say.
I'm due for an upgrade in October so for me at least it's not that much of a deal but i'm planning on giving this phone to my daughter so it would be good to get it working for her.
Would save me a lot of earache.
If u need to know anything else then please let me know, oh and i am using a class 2 sd card, which i have been unable to change, however just today my girlfriend has just had a class six delivered and her old one will be up for grabs so i will test with that too. Has anyone else tried with multiple cards??? Also how do i find out what boot loader i am using (recover) as maybe the problem resides there.
btdag said:
Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.
Click to expand...
Click to collapse
Thats right, its any app which accesses the camera.
What could be the correlation between connecting the charger and not connecting the charger, could that be a power issue and the battery is delivering too low a power output on it's own to run the camera? Hence it works with the charger plugged in ?? Either way i think that is the only real clue there is to be honest, unless your phones still restart when the phone is plugged in, in which case it's not much use.
I've been having lockscreen reboot issues with the last few Fission roms, and a couple of Matt's. Has anyone else had this problem and resolved it?
I followed the installation instructions and even formatted my SD card. I'm going to try to SBF before I install the next Fission, is there anything else I can do to completely clean out my phone? Such as wiping some system files in recovery or something.
The only data I have left over from other ROMs is backups I made of a few games like Angry Birds.
Any suggestions are appreciated, I've been trying to fix this issue for awhile!
Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?
mikeyinid said:
Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?
Click to expand...
Click to collapse
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?
kdog349 said:
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?
Click to expand...
Click to collapse
I never sign into google until after the hard reset. But I dont know if that matters. Next time you flash a rom, try wiping data and cache in recovery, after flashing, but before you reboot. And, are you overclocking or undervolting?
I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.
kdog349 said:
I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.
Click to expand...
Click to collapse
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!
mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!
Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.
mjones1052 said:
Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.
Click to expand...
Click to collapse
Personally I had a Droid 1 for 6 months and don't remember having any lockscreen reboots, at least not at the frequency of 2-3 a day that I'm having now. Could run the phone for a week without rebooting.
There were a couple of D2 roms that didn't have the reboot issue for me, but most do so maybe it is an issue with the phone like you say. I Don't understand their persistance with motoblur either At least take out eFuse if you're going to throw on motoblur
I've been trying lockbot free to solve my reboot issues. You can basically set it to be exactly the same the normal lockscreen, and so far it seems to be working for me.
I had this problem. Random, intermitten soft reboots during slide to unlock. Ran multiple roms, always had the problem. But I was always removing the same things after sbf. I had found one Dev to seem to find this to follow the music.apk file. So this time I left it on. On my last sbf, I left that in there. Havent had a problem since. Before that I had tried what I thought to be everything, multiple sbfs, multiple roms, completely formatted sd card, and re-sbf'd again. But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!
But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!
Click to expand...
Click to collapse
Which music.apk is this? Is it the D2's original application or the google music app? Because I've never taken the music app that's been on the phone or came with any ROM and I've had a few not a big number but a few.
Sent from my DROID2 using XDA App
Not sure what the google music one is, but the file is named music.apk
Please clarify this lol. Mine was working great until I installed that damn black theme for fission rom.
I've had a droid1 and I have never had reboot issues with roms before. I think it may just be a d2/x problem
Sent from my DROID2 using XDA App
Yeah the same thing happens to me. I'm pretty sure the dev's for Fission know about it, so hopefully 2.2.1 from them fixes it.
Sent from my DROID2 using XDA App
I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.
Im just curious, are you guys only experiencing these reboots with the non-blur roms, or have you experienced them with other roms also? I have only had one reboot, and that was running fission 2.2.1.
tonorice said:
I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.
Click to expand...
Click to collapse
Was it the "Android_Music.zip" or "D2_Music.zip"?
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.
Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk
I am so glad I didn't update to 1.0.7!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...
The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..
I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.
coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App
I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App
I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?
rjhall said:
I have this weird problem, and I can't figure out the cause.
And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.
rjhall said:
I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?
il Duce said:
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?
Click to expand...
Click to collapse
1. Yeah I know that. I hadn't had this problem until the last couple months. Until then, it was more or less okay. The problem is, it really is a completely fresh rom.
2. The Hero is kind of a low memory phone to begin with, so that's certainly a possibility. 2.2 and 2.3 aren't exactly kind on old hardware.
3. I don't have those settings in 6.1.0. I was using SetCPU for awhile with it at 480-7XX (Can't remember, I think 791, as that was max) and OnDemand. I had some screen off, temperature, and battery profiles too.
4. Any specific threads I should read you can suggest? I was lurking on the forums for awhile before I did anything to my phone (didn't want to brick it).
5. I'm currently using Amon RA 1.6.2. I considered clockwork, but some people said it has more problems. I've heard complaints that Amon RA requires signed packages, but frankly it hasn't been a problem thus far. It actually saved me from bricking my phone when I was new to this whole thing. As for what I wiped, I simply went through Amon RA and wiped data, dalvik, battery stats and rotation. Don't know what battery stats/rotation are, but I am familiar with the Dalvik cache.
6. As for saying I could have messed something up, when I was flashing my phone, it was something I'd never done before. It's certainly possible I mistyped something or screwed something up.
I was hoping someone could help me to completely wipe it and start fresh, since I'm sure it's had its share of problems.
I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?
also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.
Bierce22 said:
also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.
Click to expand...
Click to collapse
Are you aware that the performance governor runs at the MAX CPU speed all the time? Seriously. Your battery life must suck.
sent from a series of tubes.
yea but otherwise my performance sucks lol.
most of the time on aosp and cm7 i cant even stream music without it freezing unless i set it to performance.
Houndog101 said:
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.
Click to expand...
Click to collapse
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
oohaylima said:
I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?
Click to expand...
Click to collapse
I tried using RomManager to flash Clockwork, and it still booted to Amon RA recovery. I'm going to try to use ADB to do it, but I don't know that I'll be able to.
EDIT: Manually pushed ClockworkMod Recovery v2.5.0.7 onto my Hero.
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?
hmm thats very weird thats just about the only thing rom manager is good for now adays is installing cmr
rjhall said:
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?
Click to expand...
Click to collapse
You will not brick, that is how you wipe. You should also wipe dalvik cache. Go to this site for really good instructions :
www.romrepo.info/wiki
But please note when u wipe u "wipe" lol you will loose all your market apps and anything else installed just make sure you dont wipe sd card then youll loose all your photos and music backups exc...
rjhall said:
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
Click to expand...
Click to collapse
So I downloaded the 2.1 update from the HTC website, ran it, and it completed with no problems. Phone booted up, and now I'm trying to go through the tutorial, lagging all the while. It's almost impossible to type.
Does this mean it's hardware related?
sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.
Bierce22 said:
sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.
Click to expand...
Click to collapse
I had to start from scratch several times and my phone was pretty snappy when I first started it up after RUU. Also you stated your phone was fine and then just started running slow for no reason, was this after it took a bump?
are you talking to me or rjhall lol
Bierce22 said:
are you talking to me or rjhall lol
Click to expand...
Click to collapse
sorry, RJhall..
I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?
rjhall said:
I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?
Click to expand...
Click to collapse
Never had mine apart, maybe someone has and can help..
Okay so things have gotten increasingly weird. It used to be that squeezing the sides of the phone allowed the touch screen to work. Yesterday that stopped working altogether. Today, the screen stopped turning on at all. The LCD simply doesn't turn on. Pressing the red button turns on the phone (it vibrates when turning it on) and when the phone is on, pressing the red button lights up the keys (so I know it's waking the phone up). I took the phone apart (much simpler than I thought it would be) but I was unable to find anything that seemed out of place or broken. Does anyone have any ideas?
Hello my name is Xan Steel. I've been trying out roms on this forum for my Epic 4G. However I've run across a lot of bugs in this rom "ACS ICS V6". I would love to be able to post them in the development thread pertaining to the rom, but since I'm under the 10 post limit to post in a dev thread. I would like to ask how I go about doing this the correct way without breaking forum rules.
Thanks in advanced
Xan Steel
Tell us what your problems are here.
1st you have to have 10 post. Go to other threads and comment on stuff like the off topic forum. Then you should be able to post on dev threads. Or you can pm them and let them know.
Sent from my SPH-D700 using xda premium
Well as Neckberg has said to post my issues here (Thanks) I shall.
[ROM] ACS ICS V6.
Where to began.
I came from ACS SyndicateFrozen 1.1.1 I could never get 1.2 to run. And this ROM was based on GB. Really wanted to see what GB was like. SO after installing the ROM. Everything started out normal (no issues at that point). It was sluggish which made me wonder if Carrier I.Q. was still in the ROM. It wasn't listed that it was removed.
SO I started trying things out. Everything was going good until I turned on the Wireless WiFi Tether. It crashed outright. Tried again, and crashed. It would open to a black screen and then crash. So I did some digging, and apparently this is a known issue. So I got a different one from the market that worked (Open Garden WiFi Tether).
I installed Opera. I like Opera for it's desktop mode that actually works over Dolphins. I would type in a address, and hit go, and it would act like its going, and then stop and remove what I had typed. Tried again, and it would load a blank page. Tried a third time, and got the HTML header to load the page in a text format. Uninstalled and reinstalled same thing happen. So I left it alone, and about 3 hours later it had uninstalled itself/completely missing on the phone and market stated it wasn't installed. Rebooted phone, still gone. Not idea where it went. After reinstalling it again. it would do the same thing.
So I flashed and wiped X3. And reloaded the ROM. Thinking I have a bad load.
reinstalled all my apps and even though Opera is still doing it's thing I mentioned earlier, it hasn't uninstalled itself... yet.
Now after the reload of the ROM. Last night I lost cell service (couldn't make calls) but I had data. Which was odd to me. Rebooted the phone, and same thing. Had data but not cell service. After about and hour or so, I have cell and data back together. Maybe it was someone working on the tower in the area at 11pm, or maybe the ROM decided it would be funny.
Another thing I noticed. If you hit the menu button to pull menus in apps and on the home screens. They are white on black. White text and image, on a black background. Now if you go into any sub-menu from the main menu, its black on black. You can't read anything unless your lucky to have a bright white page behind it, so that it can try to bleed through some of the transparency.
The battery icon when charging in portrait goes from normal to skinny (blinking), while in landscape mode it goes from normal to fat (blinking).
Also two music apps is not really needed. One is fine. Trimming down on unneeded apps would help save on space. Also remove Carrier I.Q. if it hasn't been yet.
Adding that super brightness, is actually bad. Not thinking about it, it's actually crashed the video HW of the phone. On a plain white screen at max brightness, it starts to artifact, and if what ever your trying to do doesn't complete. The video HW crashes, and you get a pretty rainbow on the screen until you pull the battery. Basically acts like a dying or dead video card in a PC. Also it can (and has happened to me) cause screen burn in. If you want a image of it let me know and I'll post one.
Also Rom Manager does not recognize any ClockWorkMod Recovery, if you manually install the recovery yourself.
If I find anything else buggy I'll post and update here.
Thanks
Xan Steel
Phone: Epic 4G
ROM: ACS ICS V6
Recovery CWM 3.1.0.1 purple
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder. Rom chefs correct attitude about roms is that they build for themselves first. I personally have 3 music players installed.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Your lack of service issue it probably a carrier issue and not a rom issue.
shane6374 said:
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Click to expand...
Click to collapse
Ah makes sense. It's relatively new, and most likely not been worked on yet.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder.
Click to expand...
Click to collapse
Ah, then I should be able to remove them myself fairly easily.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Click to expand...
Click to collapse
Do you know if that is something being worked on?
Your lack of service issue it probably a carrier issue and not a rom issue.
Click to expand...
Click to collapse
It's a good possibility since it only happened the one time, but since it is a beta, and I'm using it for the first time. I felt it needed to be brought up just in case it wasn't. Heh beta tested a lot of new software, and got into the habit of reporting everything, even if it looks like something else is the issue and not the software.
Many Thanks
Xan Steel