Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA
Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?
There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA
Related
Now CM7 Nightlys Android 2.3.2 Gingerbread available:
http://mirror.teamdouche.net/?device=hero
Gapps:
gapps-gb-20110120-signed.zip from here http://goo-inside.me/google-apps/
All changes to the source code, from which the nightlies are built from, are listed there.
It is not suited for end users but hey, it´s something where you can track the current progress.
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_device_htc_hero,n,z
HTC Hero @Github
is this the same as beta3?
CM7 Nightly ROM zip is a little bit smaller,maybe some little fixes
and updates there,but don`t know,not tested at the moment.
Nightly ROM has also the the other kernel "2.6.29.6-flykernel-12pre2"
Beta 3 has "2.6.29.6-flykernel-12a" kernel!
But Flykernel-12a is newer than Flykernel-12pre2, isn't it? Also, could anybody tell me how nightlies work? Is it like you get updates pushed to your device through the CyanogenMod menu, like OTA? Please explain lol
12a should be newer,but don`t know why now 12pre2!
Maybe more optimized for CM based ROMs.
You can ask erasmux:
http://forum.xda-developers.com/showthread.php?t=730471
wow,there is something that is good for expecting
12a will be used soon if I read the commits at github:
https://github.com/loxK/android_device_htc_hero/commit/53b03bf186cd4a4d47b3604cd6290e8dc8cfdb1b
I believe it was something about CM asking for IPv6 to be build as module, while in 12a this is included statically (straight into the kernel).
Krizp0 said:
Also, could anybody tell me how nightlies work? Is it like you get updates pushed to your device through the CyanogenMod menu, like OTA? Please explain lol
Click to expand...
Click to collapse
I second this question. I've never used nightlies before. Could someone please explain how they work?
Download and flash them. No OTA update (but its a great idea).
Wipes in between are not necessary but sometimes you need them.
Not every new nightly is better then the last one (performance).
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
1immortal said:
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
Click to expand...
Click to collapse
Yeah. You need the lastest recovery 'cause of some drivers.
RA-hero-v1.7.0.1
Link: http://forum.xda-developers.com/showthread.php?t=561124
thats the one i'm running, and also tried the other one, from clockworkmod, same thing:
1. wipe EVERYTHING.
2. WIPE again.
3. flash the rom.
and .... nada, nothing.
even replaced the sd card, still same crap.
this Hero ran cronos twice, and since then... not a single 2.3 rom.
2.1, 2.2 , no probs, reflashed the radio, tried everything.
wtf ???
1immortal said:
thats the one i'm running, and also tried the other one, from clockworkmod, same thing:
1. wipe EVERYTHING.
2. WIPE again.
3. flash the rom.
and .... nada, nothing.
even replaced the sd card, still same crap.
this Hero ran cronos twice, and since then... not a single 2.3 rom.
2.1, 2.2 , no probs, reflashed the radio, tried everything.
wtf ???
Click to expand...
Click to collapse
Hmmmm maybe some are boot oc but i dont think so.
How long have you waited till you think its bootlooping? Do you only see the "HERO"-screen or do you see the bootanimation? keyboard lights are off all the time?
can't even see the bootanimation. only seeing the spl logo, and it reboots there.
1immortal said:
can't even see the bootanimation. only seeing the spl logo, and it reboots there.
Click to expand...
Click to collapse
huuuuuuu crazy Okay sorry i dont know. You can create a logcat (dont ask me) and post it over the CM forum. Also you can tweet Lox and show him your log. Maybe he know anything.
or ... i could recreate the "will it blend ?!" with this phone ...
1immortal said:
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
Click to expand...
Click to collapse
yes, woudl be recovery and your wiping within the recovery OR it could be a previous rom or something you did while using a previous rom that has somehow messed up one or more files on the phone. there are parts of the phone's memory that can sort of seem to get stuck. I can't explain more as I have no further details other than first hand experience with this phenomenon.
wiping several times in a rom, or wiping fully (all types of wipes in recovery menu) then flashing a totally different rom (like a 2.1 sense rom) then wiping fully and flashing the rom you want to use could maybe fix it - if in fact this is the cause of your problem.
try wiping ONLY dalvik cache AFTER flashing the rom. i use recovery 1.6 and everything works.
Found this,seems there is another bug at Android 2.3.2 too.
Not only the SMS bug!
Android 2.3 Shows Security Bug, Can Gain Access To Content On microSD Cards
http://www.talkandroid.com/28696-and...microsd-cards/
Have you tried wiping with fastboot? Then flash the ROM.
posted from the other side of town with a 2nd class stamp
I've got MIUI ROM 1.6.10 installed on my HTC Desire and I really like it, but I've got a big issue with the camera: it's in a constant state of being frozen.
So to clarify, I open the camera app, and it's straight away frozen. I try to press buttons but all I get is the Force Close / Wait dialogue. If I wait, nothing happens. If I force close and open it again, it's frozen still/again.
It used to happen to me in MIUI 1.2 as well and when I upgraded to MIUI 1.4 after a wipe, surprisingly it was exactly the same, but then I tried pressing the Clear Data button for the Camera application and it started working again.
A little bit after it started getting frozen again. Clear data didn't work anymore, neither did a wipe, SD card format and upgrading to 1.6.10, as mentioned above.
The only thing I can think about the might cause the problem is this: before miui I used to have cyanogen ROM. When I look at phone information it says I've got the cyanogen kernel. is that something that could cause problems to the miui ROM? Should install a different kernel?
Can anyone please help? I really like this ROM and I don't want to have to start getting used to something else!
Thanks for reading!
I'm not sure if this is useful/helpful at all but i gather that since it says that you've got cm kernel you didn't perform a full wipe when you installed miui... try doing a full wipe and reinstalling it...
Save important user data and apps, perform a full wipe and flash again.
Does a full wipe erase the previous kernel?
What kernel will I have then?
Can anyone actually explain what kernel is exactly?
Also, how do I do a FULL wipe?
Because I've already done:
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache
What am I missing?
Cheers
After a full wipe you won't be able to start any rom.
You will get the kernel which is delivered with the rom you flash.
An explanation for the kernel:
http://en.wikipedia.org/wiki/Linux_kernel
Nothing is missing for a full wipe.
Search the miui thread for your problem.
MatDrOiD said:
After a full wipe you won't be able to start any rom.
You will get the kernel which is delivered with the rom you flash.
An explanation for the kernel:
http://en.wikipedia.org/wiki/Linux_kernel
Nothing is missing for a full wipe.
Search the miui thread for your problem.
Click to expand...
Click to collapse
If nothing is missing and I've actually done a full wipe, then why is my kernel still cyanogen?
liranh said:
If nothing is missing and I've actually done a full wipe, then why is my kernel still cyanogen?
Click to expand...
Click to collapse
Because cyanogen is the kernel which is delivered with miui rom.
MatDrOiD said:
Because cyanogen is the kernel which is delivered with miui rom.
Click to expand...
Click to collapse
Wicked thank you. So the kernel is not the problem.
Could I still have missed something from a full wipe? I remember reading in the guide that u need to format /data,or something. But I assumed the wipes I've detailed above were sufficient. Can anyone confirm that for me?
Or can anyone tell me otherwise why I'm having this problem?
Thanks.
Try to update radio on newest version (post #6):
http://androidforums.com/desire-all...sers-anyone-elses-camera-stopped-working.html
MatDrOiD said:
Try to update radio on newest version (post #6):
http://androidforums.com/desire-all...sers-anyone-elses-camera-stopped-working.html
Click to expand...
Click to collapse
Thank you. You reckon the radio might affect the camera?
Edit: Just had a quick look at the thread you gave me. Seems like that might fix the problem. I'll give it a go when I finish work. Thank you very much!
liranh said:
Thank you. You reckon the radio might affect the camera?
Edit: Just had a quick look at the thread you gave me. Seems like that might fix the problem. I'll give it a go when I finish work. Thank you very much!
Click to expand...
Click to collapse
DIDN'T WORK!
It's a shame. I really thought that was the solution, but it didn't work.
I've just downloaded and installed the recommended radio (5.17.5.23), even tried to clear the camera's data again, but it's still frozen.
ANYONE ...? :\
Did you try some other kernels like ManU or Tiamat?
guersam said:
Did you try some other kernels like ManU or Tiamat?
Click to expand...
Click to collapse
No. Do you reckon that might help? Which one would u recommend?
Okay I've tried a different radio, different kernels (Tiamat 3.3.8 and 4.0.5). Nothing helps!
Does anyone have a clue how to fix this annoying problem?
Another lead I had in mind: Could the fact that I have S-ON affect anything?
Update: I've tried pressing "Fix Permissions" in ROM Manager which didn't help either.
................?
The MIUI camera seems to be a bit buggy, I had to update the radio which helped me get rid of the worst crashes (suprise reboots) but it's still FC'ing and crashing the camera totally so that a reboot is necessary.
Try installing Camera360 from Market. It works for me, and at least you will know if it's just the MIUI Camera app that's broken or if you have bigger problems. In case Camera360 can't connect to the camera, reboot and try again.
enemix said:
The MIUI camera seems to be a bit buggy, I had to update the radio which helped me get rid of the worst crashes (suprise reboots) but it's still FC'ing and crashing the camera totally so that a reboot is necessary.
Try installing Camera360 from Market. It works for me, and at least you will know if it's just the MIUI Camera app that's broken or if you have bigger problems. In case Camera360 can't connect to the camera, reboot and try again.
Click to expand...
Click to collapse
I've already tried a different camera from the market and it does work with no problems at all.
It is the miui camera app that's malfunctioning.
If no one has a solution, all that's left for me is to hope the miui devs will fix this critical issue for their next build.
liranh said:
I've already tried a different camera from the market and it does work with no problems at all.
It is the miui camera app that's malfunctioning.
If no one has a solution, all that's left for me is to hope the miui devs will fix this critical issue for their next build.
Click to expand...
Click to collapse
Ah, then it's most probably the same problem that I have, only I get to shoot a few pics before it goes bye bye and then no camera app at all works until I reboot.
It's a shame because I really like the MIUI Camera, but I guess we'll just have to wait for a fix. If you have error logs, try posting them in the official forum for your MIUI build and maybe they can get someone in China working on a solution?
same problem for me but i am on 1.9.16 ported to X10 lol...
I seen somewhere that it was the auto focus that caused problems/ lags for ppl so if i could just get it to work once and maybe turn that off?
So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?
kevinzone said:
So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?
Click to expand...
Click to collapse
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.
efrant said:
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.
Click to expand...
Click to collapse
will this make my files be deleted? I would rather not have that happen please
kevinzone said:
will this make my files be deleted? I would rather not have that happen please
Click to expand...
Click to collapse
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...
efrant said:
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...
Click to expand...
Click to collapse
Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused.
If this is the ONLY way , then can you please tell me how to do this, i'm confused.
If there is another way on to get out of this boot logo aokp thingy, without losing data , please tell me.
Note: i dont know if i'm doing anything, but i backed up via the recovery CWM
then after i deleted cache and dalvik, then flashed aokp,franco and then g apps. And nothing happened
Bump please. i really don't want to wipe my phone
Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.
Prod1702 said:
Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.
Click to expand...
Click to collapse
Uhh i reflashed aokp, kernel and gapps. Nothing really. Two questions.
1. Anything else?
2. for the reflashing, i want to flash another rom, how do i put the files on the phone? Gnex doesn't have an sd card slot and i dont know how to access it on the computer if it is in recovery mode. So confused
EDIT: not entirely sure what flashing means, so what i meant by flashing in my case, was that i just re ran the zips. then reboot. Nothing . waited 5-10 minutes ish. Never had long bootups on my first try.
Bump please!
kevinzone said:
Bump please!
Click to expand...
Click to collapse
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)
efrant said:
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)
Click to expand...
Click to collapse
But there is a problem. I cant access the phone. Since it won't boot up i can't access it from the computer.. Or can i? There's no sdcard slot either
Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work
I searched for something like this, but couldnt find anything. Ive been flashing between different Roms since I got my phone, and wanted tosee if there was something that I could flash to wipe away all the gremlins from previous Roms. I still do a clean flash and wipe dalvik, cache, and factory reset. But ive been noticing little issues here and there.
itsLYNDZ said:
I searched for something like this, but couldnt find anything. Ive been flashing between different Roms since I got my phone, and wanted tosee if there was something that I could flash to wipe away all the gremlins from previous Roms. I still do a clean flash and wipe dalvik, cache, and factory reset. But ive been noticing little issues here and there.
Click to expand...
Click to collapse
Well There isn't one as such. Typically what I do is.
1. Factory Reset
2. Wipe Dalvik, Cache and sometimes /Data
3. Flash the Rom & Gapps.
4. Reboot Setup everything
5. Reboot Again to Recovery and then wipe Dalvik+Cache and then flash custom Kernel if I wanted.
I may skip Step 5 if I want to stick with Rom's own kernel. I know you went through this, I just wanted to specify the sequence. If you still have issues then post them on the new rom's thread.
Perseus71 said:
Well There isn't one as such. Typically what I do is.
1. Factory Reset
2. Wipe Dalvik, Cache and sometimes /Data
3. Flash the Rom & Gapps.
4. Reboot Setup everything
5. Reboot Again to Recovery and then wipe Dalvik+Cache and then flash custom Kernel if I wanted.
I may skip Step 5 if I want to stick with Rom's own kernel. I know you went through this, I just wanted to specify the sequence. If you still have issues then post them on the new rom's thread.
Click to expand...
Click to collapse
Thanks. I know on the SGS Blaze 4G someone developed a gremlin cleaner that you could flash along with wiping everything manually. Just wondered if there was one for the S3. Im using Goosh rom, but it looks like the developer dropped support.
itsLYNDZ said:
Thanks. I know on the SGS Blaze 4G someone developed a gremlin cleaner that you could flash along with wiping everything manually. Just wondered if there was one for the S3. Im using Goosh rom, but it looks like the developer dropped support.
Click to expand...
Click to collapse
Take a look at this thread. Hope it helps.
itsLYNDZ said:
I searched for something like this, but couldnt find anything. Ive been flashing between different Roms since I got my phone, and wanted tosee if there was something that I could flash to wipe away all the gremlins from previous Roms. I still do a clean flash and wipe dalvik, cache, and factory reset. But ive been noticing little issues here and there.
Click to expand...
Click to collapse
What little issues and on which ROMs? It matters.
Factory reset wipes data and cache. Dalvik cache is on the data partition, isn't it?
So factory reset, wipe system. Should be all you need to do.
Aerowinder said:
What little issues and on which ROMs? It matters.
Factory reset wipes data and cache. Dalvik cache is on the data partition, isn't it?
So factory reset, wipe system. Should be all you need to do.
Click to expand...
Click to collapse
Ive been reflashing Goosh rom, but after 2-3 months or so I have to reflash it because it slows down and starts to have issues. Havent installed or updated any apps. I dont have many and I know they can affect it. So thats when ive been doing. I really like the rom and get great battery life, but the dev has dropped support for it. Even to tell me to "use a different ROM" because he doesnt care. But each time I reflash it after a couple months, it doesnt seem to work as well as the very first flash from when I first got the phone. I feel like things are building up/not getting completely wiped.
itsLYNDZ said:
Ive been reflashing Goosh rom, but after 2-3 months or so I have to reflash it because it slows down and starts to have issues. Havent installed or updated any apps. I dont have many and I know they can affect it. So thats when ive been doing. I really like the rom and get great battery life, but the dev has dropped support for it. Even to tell me to "use a different ROM" because he doesnt care
Click to expand...
Click to collapse
Please try Auto Memory Manager on most aggressive setting. Check and see how things go. If you see FCs then dial back to medium.
On a side note, Better Battery life ? See these Screenshots for Battery life of other roms to compare/
itsLYNDZ said:
Ive been reflashing Goosh rom, but after 2-3 months or so I have to reflash it because it slows down and starts to have issues. Havent installed or updated any apps. I dont have many and I know they can affect it. So thats when ive been doing. I really like the rom and get great battery life, but the dev has dropped support for it. Even to tell me to "use a different ROM" because he doesnt care. But each time I reflash it after a couple months, it doesnt seem to work as well as the very first flash from when I first got the phone. I feel like things are building up/not getting completely wiped.
Click to expand...
Click to collapse
Unless you're completely wiping everything, including internal sd, then there will of course be lingering data. But consider doing a true factory reset, which formats /data. From a custom recovery, it doesn't format because it's preserving your internal sd data. You'll have to specifically choose Format Data from within the recovery.
Something else you can try is in Settings, Developer Options, at the bottom choose Limit Background processes and I would select 3 to start. If it doesn't help much go to 2 and test.
Sent from my SGH-T999 using Tapatalk
Perseus71 said:
Please try Auto Memory Manager on most aggressive setting. Check and see how things go. If you see FCs then dial back to medium.
On a side note, Better Battery life ? See these Screenshots for Battery life of other roms to compare/
Click to expand...
Click to collapse
I cant find the screen shots on that page :/ I would like to see a comparison of battery life between roms.
itsLYNDZ said:
I cant find the screen shots on that page :/ I would like to see a comparison of battery life between roms.
Click to expand...
Click to collapse
I had linked another post of mine here on XDA. Are you sure in the entire post you didn't see linked screenshots ?
There's one set near the top and bellow that there is "Hide Button" which hides my own set.
Here is a Direct Link and the other shot.
Perseus71 said:
I had linked another post of mine here on XDA. Are you sure in the entire post you didn't see linked screenshots ?
There's one set near the top and bellow that there is "Hide Button" which hides my own set.
Here is a Direct Link and the other shot.
Click to expand...
Click to collapse
No, but I did read how to use Greenify to control Google Service Framework from that thread... Didnt see any screenshots..
itsLYNDZ said:
No, but I did read how to use Greenify to control Google Service Framework from that thread... Didnt see any screenshots..
Click to expand...
Click to collapse
You probably clicked on a link in the post that took you to the GSF related Thread.
Also in my last post I linked 2 screenshots. Were they not accessible ?
Please visit This thread. You are interested in Post # 11.
Perseus71 said:
I had linked another post of mine here on XDA. Are you sure in the entire post you didn't see linked screenshots ?
There's one set near the top and bellow that there is "Hide Button" which hides my own set.
Here is a Direct Link and the other shot.
Click to expand...
Click to collapse
Can you tell me what Rom was being used in this screenshot that you linked to? I would like to stay with a TW rom.... Also, does it matter if I flash via TWRP or CWM? Im so used to CWM....