Running the last version of temaseks cm7 kang along with a cutom kernel Neok UltimateS Kernel v3.9Ti. lately ive been trying to maximize the ROM space and reduce the size of the system partition to have more room for apps and avoid using A2SD (which creates more performance problems than I need now). as a result i think this has started causing me to get random applications to force close and random reboots when idle or trying to do to many things at once.
I picked up an N1 for my daughter to use and have experienced random reboots since the get go starting with the stock setup (1 month ago). Since then I've flashed a few different Roms, read through various posts related to the random reboot issue which seems to plague this phone and nothing tried seems to make a difference as yet. Everything from flashing a different kernel to radio has been suggested and I may venture there next. One thing I can say, despite the teen being disappointed and dad (me) having to constantly mess with it, it's a hard phone to brick (ha).
Yeah I've had my phone since launch so I think my issue might be related to wear of. Instantly flashing and repartitioning the nand
If you can grab a logcat of the reboot then you have a much better change diagnosing the problem, without this there will just be guesses
Sent from my Nexus 7 using xda premium
Alright will try that when I get home on tuesday
EDIT: here is the Logcat of where the reboot happened
Any ideas?
(deleted)
Custom blackrose
Sent from my Nexus 7 using xda app-developers app
(deleted)
It is the latest version. the only thing ive done different from before was make the cache 8mb is that too small?
(deleted)
solidmac said:
It is the latest version. the only thing ive done different from before was make the cache 8mb is that too small?
Click to expand...
Click to collapse
ShellChip said:
Does seem small. Use 10MB, it's what's recommended for CyanogenMod ROMs.
Click to expand...
Click to collapse
I think that's not the case. We can have Cache as small as 5MB and still not have problems. I have 10 MB cache and even I've experienced reboots from time to time.
Yeah i can confirm that now after doing that i still get random reboots.
Sent from my Nexus 7
(deleted)
Quikpic is that app
Sent from my Nexus 7
(deleted)
Well I uninstalled it to see if it is the issue
Sent from my Nexus 7
ShellChip said:
Have you noticed anything weird when using it?
Click to expand...
Click to collapse
Yeah this isn't the problem just rebooted a few hours ago.
Sent from my Nexus 7
Related
Ever since i've been using CM 7, my Hero's been acting up badly. Gradually over the past weeks, its gotten slower, unresponsive, and just plain dumb. I've Bootloops about 90% of the time, takes like maybe 10 minutes for it to realize its awake. I'm frankly tired of it and ready to bury it. I'm getting either the Evo 3D or SG II in January, so thankfully I won't have to put up with this for too long. I don't know if resetting it to stock would help, but i'm ready to try it. If there's any other suggestions that could rejuvenate my Hero, please do tell.
Do you use autokiller? Try that if you don't. Try wiping your cache in recovery. What cm7 are you running? Try jaybobs. Do you overclock? You could be running your speed too high. 691 is the fastest safe speed any hero can run.
Lastly, try doing a clean wipe and reflashing. Back up your sd card and format that too. Those have been known to cause problems every now and then.
Sent from my HERO200 using XDA App
Mobiono said:
Ever since i've been using CM 7, my Hero's been acting up badly. Gradually over the past weeks, its gotten slower, unresponsive, and just plain dumb. I've Bootloops about 90% of the time, takes like maybe 10 minutes for it to realize its awake. I'm frankly tired of it and ready to bury it. I'm getting either the Evo 3D or SG II in January, so thankfully I won't have to put up with this for too long. I don't know if resetting it to stock would help, but i'm ready to try it. If there's any other suggestions that could rejuvenate my Hero, please do tell.
Click to expand...
Click to collapse
Try these apps...
1.) Autokiller
2.) SetCpu
3.) CacheMate
4.) SpeedBooster
5.) SpareParts
6.) MemoryUp Pro
7.) Advanced Task Killer
MrDowntown12 said:
Do you use autokiller? Try that if you don't. Try wiping your cache in recovery. What cm7 are you running? Try jaybobs. Do you overclock? You could be running your speed too high. 691 is the fastest safe speed any hero can run.
Lastly, try doing a clean wipe and reflashing. Back up your sd card and format that too. Those have been known to cause problems every now and then.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I'm running the latest nightly. I don't overclock. I thought jaybob only had cm 6 Roms. Could you link me to his cm 7 roms? And i'll try just wiping everything.
I'm itching to install it but I'd like to hear from some people who have used it first.
I'd advise against it.
No need, since no weak memory allocation and management like the DX2.
I did it worked had to get correct busybox version couldn't tell if anything really happened but why the avoid krazy?
Sent from my Droid using XDA App
Have you rebooted your device? If not give that a go, and tell me how it works out for you.
I didn’t' even execute any options with the script and it cause me to bootloop once I rebooted, and someone else experienced the same.
I did bootlooped factory rest got my stuff back re-supercharged and works fine I even did a reboot after 30mins and still worked
Sent from my Droid using XDA App
rushless said:
No need, since no weak memory allocation and management like the DX2.
Click to expand...
Click to collapse
I figured as much, but I am getting a pretty decent amount of lag, even after fully removing bloatware (about 32 apps total). I don't see how people are claiming 200mb free. Even after bloatware removal, I still only have 80-130 free at any given time, and I personally hate using an app-killer.
Don't get me wrong, I do know that Android will try and use up any memory that is free and that having a low number of RAM available isn't a bad thing. But, as I stated earlier, I am experiencing a good amount of lag from time to time (mainly due to my widgets I would assume).
I did a factory reset and a battery pull 2 days ago, and the boot-up process is twice as fast now...just as it was when I first bought the phone. But the lag is still present, and the REDRAWING is driving me absolutely insane.
krazykrivda said:
Have you rebooted your device? If not give that a go, and tell me how it works out for you.
I didn’t' even execute any options with the script and it cause me to bootloop once I rebooted, and someone else experienced the same.
Click to expand...
Click to collapse
Yeah. That was me. I did run the script though. It didn't even get past the Droid part of the boot animation. A factory reset will fix it, and you'll still have root after.
Silly rabbits V6 is for Froyo!
Sent from my DROID X2 using XDA App
BDAZZG1 said:
Silly rabbits V6 is for Froyo!
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
not true; v6 is for all android OS released so far. It was specifically developed for Gingerbread, but works well on Froyo also.
BUT: There are still conflicting reports that changes it makes in the /system folder may cause problems with the D3, so until an .sbf is available, i'd proceed with great caution doing ANYTHING to the D3 that is not entirely in userspace.
I removed most of the bloat I was comfortable pulling off... but I must say the biggest jump in responsiveness has been from tweaking the build.prop to increase the events per second (I'm at 120) and VM memory (64m).
Please, err on the side of caution right now as we have no sbf, no clockwork recovery. I had to sbf my D2 enough times playing with things I didn't think had a chance of breaking it, that did, that I'm very careful what I poke at on my daily driver, and urge you to as well
This morning when I woke up I checked the calendar on my Captivate and everything looked fine. I had an IM app (Go) running but stopped it. I went back about 15 minutes later to look at something else on my phone and it would not wake up. Nothing I did would make the screen come on. I eventually just pulled the battery and it started working fine. This is the 3rd or 4th time that's happened and usually at night while charging.
Any ideas?
Thanks for any help
Its called sleep death. What ROM, kernel,oc/UV values are you using?
I've never heard of that, but I would definitely say that describes it perfectly.
I'm actually running stock Froyo. All of this pain lately makes me want to load up a custom ROM this weekend (assuming it would help). I just don't want to end up bricked.
Thanks
That's not sleep death, at least what I experienced, I have seen that on my own captivate. Usually mine will lock up and become non-responsive, eventually the phone will restart. I don't know if it is a common issue but one I have had often.
Ya I've had that happen. Either I gotta pull the battery or my phone poops on itself and reboots. Oh well
Sent from my SGH-I897 using XDA App
I have been having the screen go black and the phone is unresponsive at times so i called att and they are sending me another phone under warranty but i asked them if my replacement is going to have the same issues because most cappy owners have this problem she said it would but i think all the phones have this issue
Sent from my SAMSUNG-SGH-I897 using XDA App
I wish they would send refurbs with updated GB but i was told im getting the same
Sent from my SAMSUNG-SGH-I897 using XDA App
Does anyone know if a custom ROM would fix the issue or is this hardware related?
I've given custom ROMs much thought. Not sure which one I'd choose, etc. Seems like there is so much to read and a lot of the information builds on itself. My luck I'd try AIO or something and get down to page 80 of all the postings and realize it doesn't work for me after I already flash it.
Thanks
I started having the same problem a couple days ago. I've my captivate for almost one year already. I had stock eclair, froyo, several roms. Now I'm using stock GB 2.3.5 KI2. The only thing that I can think it changed is the fact that I added an external 16gb sd. I'll do a factory reset and remove sd to see if it happens again.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have had the least issues on cognition 4.5.3, the gingerbread leaks for whatever reason never worked well for me. I have a S II now with no issues, but still use the captivate like an iPod touch. Working very well on cognition as I type.
xfedex said:
I started having the same problem a couple days ago. I've my captivate for almost one year already. I had stock eclair, froyo, several roms. Now I'm using stock GB 2.3.5 KI2. The only thing that I can think it changed is the fact that I added an external 16gb sd. I'll do a factory reset and remove sd to see if it happens again.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I found the source of my battery leak/black screen. It was "Smooth Calendar Widget" app.
I've had a couple of random reboots since updating to leaked 213 version of ICS, has anyone else here had this issue?
zPacKRat said:
I've had a couple of random reboots since updating to leaked 213 version of ICS, has anyone else here had this issue?
Click to expand...
Click to collapse
Can't say I have. What apps are you usually running? (or in the background)? Are you on 4G? Strong cell strength? GPS? Bluetooth? Etc can you give us more details as to when you see them?
danifunker said:
Can't say I have. What apps are you usually running? (or in the background)? Are you on 4G? Strong cell strength? GPS? Bluetooth? Etc can you give us more details as to when you see them?
Click to expand...
Click to collapse
Normal stuff, email, facebook, xda app, nothing special. this happened when using different apps, once was firefox, the other was the built in email client. first time lte was turned off, the second time it was not.
may be you have to clean caches simply.
Have you tried a Factory Reset? I know a lot of people don't like/enjoy doing that....but you just "updated" an OS from 2.3.6 to 4.0.4.
I personally always factory reset whenever going from one OS version to the next.
2.x to 4.x....YES a Factory Reset can cure many many issues.
2.x to 2.y....No, just update and run with it...
tcrews said:
Have you tried a Factory Reset? I know a lot of people don't like/enjoy doing that....but you just "updated" an OS from 2.3.6 to 4.0.4.
I personally always factory reset whenever going from one OS version to the next.
2.x to 4.x....YES a Factory Reset can cure many many issues.
2.x to 2.y....No, just update and run with it...
Click to expand...
Click to collapse
Yeh, thought about doing a reset. Just installed safe strap and plan on a full backup and then a factory reset.
Sent from my HTC_Amaze_4G using xda premium
I've been running .213 for almost 5 days and its been super smooth. I notice its a bit more heavy on the battery drain though.
splant said:
I've been running .213 for almost 5 days and its been super smooth. I notice its a bit more heavy on the battery drain though.
Click to expand...
Click to collapse
No idea on battery use as I flashed 213 within 6 hours of getting the device. I did clear both the cache & dalvik cache and so far so good.
Sent from my HTC_Amaze_4G using xda premium
I'm still on 211 is there anything fixed or buggy in 213?
meek2100 said:
I'm still on 211 is there anything fixed or buggy in 213?
Click to expand...
Click to collapse
I don't know about any list of fixes between the 2 releases. Most likely not going to be published either. That said, I've no issues with 213 yet, except for 2 random reboots that seem to have been cleared up by clearing both caches.
One thing i noticed moving between.211-.213 is my gps seems to be much more active, almost like it had a hard time getting a fix. Same thing happens outside, and i have all my locations on. It's not terrible just an observation
I just rooted my tablet using instructions from several sources here, and have a bit of a problem. I rooted it because of a slightly annoying problem with the touch screen. It worked great 90% of the time, but occasionally I would have to tap an icon a few times for the screen to respond. I have not installed any Rom on it as I decided to keep it stock for the time being. That could change real quick though!! After I rooted it, the problem has increased. I did install several tweaking apps on it (Enterprise ram and digitizer booster, Optimus Root Memory Optimizer, and Entrophy Fixer) and a few games that I had on it before. Removing the digitizer app did no good. The odd thing about it is, I do not notice the touch screen issue if I am playing a game, only when I touch the application icons or links. There does not appear to be any app available to calibrate the screen. Has anybody else had this issue with the 701? Thanks for any help you can provide!!
mikekoz said:
I just rooted my tablet using instructions from several sources here, and have a bit of a problem. I rooted it because of a slightly annoying problem with the touch screen. It worked great 90% of the time, but occasionally I would have to tap an icon a few times for the screen to respond. I have not installed any Rom on it as I decided to keep it stock for the time being. That could change real quick though!! After I rooted it, the problem has increased. I did install several tweaking apps on it (Enterprise ram and digitizer booster, Optimus Root Memory Optimizer, and Entrophy Fixer) and a few games that I had on it before. Removing the digitizer app did no good. The odd thing about it is, I do not notice the touch screen issue if I am playing a game, only when I touch the application icons or links. There does not appear to be any app available to calibrate the screen. Has anybody else had this issue with the 701? Thanks for any help you can provide!!
Click to expand...
Click to collapse
I had the same issue with mine, installing a custom Rom improved things no end
Sent from my K00C using XDA Premium HD app
boldnuts said:
I had the same issue with mine, installing a custom Rom improved things no end
Sent from my K00C using XDA Premium HD app
Click to expand...
Click to collapse
Thank you. That is what I am leaning towards. I am looking at CROMi-X 7.0.3. Which one did you flash?
boldnuts said:
I had the same issue with mine, installing a custom Rom improved things no end
Sent from my K00C using XDA Premium HD app
Click to expand...
Click to collapse
mikekoz said:
Thank you. That is what I am leaning towards. I am looking at CROMi-X 7.0.3. Which one did you flash?
Click to expand...
Click to collapse
Installed the latest version of CROMi, and no luck. The problem remains. Plus I apparently lost root. I will mess with it more tomorrow!
mikekoz said:
Installed the latest version of CROMi, and no luck. The problem remains. Plus I apparently lost root. I will mess with it more tomorrow!
Click to expand...
Click to collapse
i have tried just about all the available Roms for the tf701, currently using the new CM12 which runs very well, make sure you do a full wipe/format before hand though, try this app, also worked for me, the one on the OP page
http://forum.xda-developers.com/showthread.php?t=1261237
Sent from my K00C using XDA Premium HD app
I may end up trying CM12. I am also getting an error at boot up , "the process com.google.process.gapps has stopped" . It does not seem to be causing any problems, but it is annoying nevertheless. Also, this rom is nice, but I see no performance difference between it and stock. I tried that calibration app you linked to, but it does not seem to have done anything. Thanks!
boldnuts said:
i have tried just about all the available Roms for the tf701, currently using the new CM12 which runs very well, make sure you do a full wipe/format before hand though, try this app, also worked for me, the one on the OP page
http://forum.xda-developers.com/showthread.php?t=1261237
Sent from my K00C using XDA Premium HD app
Click to expand...
Click to collapse
Where did you find CM12? I have been searching the web and all I can find is CM11!
mikekoz said:
Where did you find CM12? I have been searching the web and all I can find is CM11!
Click to expand...
Click to collapse
http://forum.xda-developers.com/tra.../cyanogenmod-12-lollipop-pre-nightly-t3003092
Sleeepy2 said:
http://forum.xda-developers.com/tra.../cyanogenmod-12-lollipop-pre-nightly-t3003092
Click to expand...
Click to collapse
I may actually wait on this after reading the blog. Is there anything that is not working on this at this time? I do not have the dock, so the one limitation listed would not affect me. Would the performance of this rom be better than the Cromix I have on it now?
mikekoz said:
I may actually wait on this after reading the blog. Is there anything that is not working on this at this time? I do not have the dock, so the one limitation listed would not affect me. Would the performance of this rom be better than the Cromix I have on it now?
Click to expand...
Click to collapse
I doubt it, but doesn't hurt to try. CM12 is in beta though. CROMi-X 7.1 was just released. The "xxx process has stopped" is a bug that will be ironed out soon. You did clean install the rom, did you?
But if you have the same problem on different roms it's unlikely that your touch problem is software related.
To rule out a software problem you should format data and reflash the rom. Format, not just wipe. Which will delete all data on your tablet.
Also try with the microSD out. Bad cards can cause all kinds of weird problems.
berndblb said:
I doubt it, but doesn't hurt to try. CM12 is in beta though. CROMi-X 7.1 was just released. The "xxx process has stopped" is a bug that will be ironed out soon. You did clean install the rom, did you?
But if you have the same problem on different roms it's unlikely that your touch problem is software related.
To rule out a software problem you should format data and reflash the rom. Format, not just wipe. Which will delete all data on your tablet.
Also try with the microSD out. Bad cards can cause all kinds of weird problems.
Click to expand...
Click to collapse
Thank you for your response. I was able to fix the process error, but I still ended up putting CM12 on it anyhow! It took me all of 10 minutes and I have had no problems so far. It is very smooth and fast. I did a wipe/format, and a dalvik wipe before I put CM12 on it using CM 6.0.5.1 (I think that is the correct version). Not sure I did that correctly though, since my download folder on the tablet was still intact afterwards. My LCD problem is more than likely hardware, but it is more of an annoyance than anything. It only affects opening up apps. The screen works great in games and just typing.