Related
Morning guys - i'm a sort of noob (go easy.!) that needs help with my HTC desire. I took plunge and decided to try rooting & applying custom ROM, but now have problems with the screen freezing completely at any point, then on restart the phone boots into the home launcher but screen does not respond or will not wake.
So far:
Rooted with unrevoked
HBOOT flashed to Cm7r2
Latest version of clockworkmod recovery via app
Aurora 4.1 (all dalvik caches wiped at correct points).
V6 supercharger applied on setting 5 (balanced).
Tried with kernel built in ROM (0.7) & gingercakes 0.9cfs no2way havs.
SD card partitioned with GParted (fat32 primary, 2gb primary ext4).
I've had the ROM working fine, the only other thing i can place it to is swapping the SD card, which i've changed from 4gb class to, to a samsung 16gb class 6. Does anyone think that this error could be anyway caused by the fact the card readers i've used (tried 2 different readers) both have had trouble recognising the 16gb card?? (Gparted still recognised it however)
Is it possible to be a hardware issue? Please note recovery works perfectly - wiping caches, reinstalling zip files, backups etc.....only problem is now this freezing of home launcher and no response.
Any help be greatly appreciated, give me a nudge if i haven't given enough detail.
Regards, Nick.!
Additional:- Tried unsupercharging & rebooting - no difference.
Only other thing i can think that i've done prior to the fault is attempting to install busybox for V6 supercharger - which failed every time and affected my root access on the phone. I've found that the Aurora ROM has busybox installed already. However, is it possible me trying that install has somehow affected the rooting of the phone?
So many questions, sorry guys!
Bump.....would ADAO file manager (which isn't on google market I notice) affect anything on ext4 perhaps? That was one app that i downloaded from net.
Have you tried reverting your busybox to the default version? Also, are you overclocking and or overclocking? Going to high or to low with CPU speed can cause problems like that. It has also been said that partitioning an SD card can damage them, which may be an issue you have now. You could try formatting the SD card to its default state and run like that for a while. I ran a 16gb SD card in a Droid Eris for months and it never caused a problem like that. Of course, I didn't have a partition set up on it.
Sent from my ADR6350 using Tapatalk
I've literally left the settings for speed in daemon controller alone, although i'm still learning and not sure if they are default overclocked or not?
Possibility with the SD card, i'll give it a try for sure, that'd mean i'd have to revert to an alternate ROM would it, as Aurora specifies an ext4 partition?
Thanks again though, it's a start at least
Do you set profiles in SET CPU?
Accidentally sent from my Google Nexus S using XDA Premium
Excuse noobie brain here, where will i find those CPU settings?
If so, fully wipe and install again. And what rom are you using currently that causes freeze?
Accidentally sent from my Google Nexus S using XDA Premium
Aurora V4.1 ROM i'm using. Don't think it's the ROM itself as i have had it stable for week or so, before swapping SD card from 4gb to 16gb.
I'm thinking this may be the root cause as i've just tried a complete fresh partition with Gparted & fresh install of literally just the ROM itself and on first boot it froze again. Rebooted and now seems to be stable with nothing reloaded back on it but we'll wait and see. If it freezes again i'll try my 4gb card. Didn't want to revert back to that as its only class 2.
[Q] Noob help - Rooted desire keeps freezing.! Update...!
UPDATED - Still getting same problems - have now tried a different SD card & alternative ROM (Cool3d v5).
Is it possible it could be heat related fault? The more i use the phone the more readily it happens - from the occasional freeze (okay after reboot) to complete freeze and no response on every reboot.
Does the CPU therefore have a cut out or could be freezing based on the settings that are initially loaded through daemon controller? What are safe settings for the min/max values?
Only other thing i've noticed is once fault starts to occur - clearing dalvik cache in recovery is quite unresponsive - menu holds before allowing me to clear.
Got to get to the bottom of this - don't want to revert back to original, or throw my phone in the river!!
Save clock is 1ghz. No over clock is the safest.
Do your phone wear case? If yes, it may be the caused of heat.
I'm sure the rom caused you the freeze. You can try to change a more stabler rom, eg aosp
Accidentally sent from my Google Nexus S using XDA Premium
Bit more progress - as my phone literally would freeze on loading home launcher, i connected it to pc and mounted via recovery - and deleted everything i could see for V6 SUPERCHARGER - and hey presto, very slowly, but phone booted up and is now working again.
I see the devs of V6 say about removing hardtokill if any lags occur - i think it's this portion of the script affecting my bravo.
SO, i'm going to run it totally without V6, and may try to just run the memory portion, but the instructions to disable hardtokill are a little unclear to me, could you guys tell me in simple terms how to acheive??
Thanks again for all your responses, a great help
V6 now off and all fresh re-installed with cpu max turned down also, and set to ondemand gov, will see how we go
[Q] Noob help - Rooted desire keeps freezing.! PT3.!
Still no joy with this issue guys - pulling my hair out now - after a few hours use (usually overnight) phone just freezes, then freezes on reboot, before getting worse and now will not pass alpharev's boot screen.
Installing fresh gets me into home launcher, but becomes unresponsive and freezes again.
I've tried different ROM's, different SD's, basic clean install, all without any luck. I'm thinking now it is more a hardware issue with the phone?
nikh667 said:
basic clean install
Click to expand...
Click to collapse
Did you wipe data/cache partitions/dalvik cache before flashing the rom? Did you wipe dalvik cache and cache partitions after flashing the rom?
Yep all wiped before and after.
nikh667 said:
Yep all wiped before and after.
Click to expand...
Click to collapse
Have you tried flashing a new kernel?
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
nikh667 said:
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
Click to expand...
Click to collapse
Has your device went through any physical damage (around the time the problem started)?
No physical damage apart from the battery cover being pulled off more than once(!) and a lot of obscenities being flung it's way, lol! But no, not dropped or damaged at all.
I've used the phone now all afternoon, longer than normally, with the same details on same hboot, but left some of the sense widgets off the home launcher, and it hasn't locked up once.
This is a more detailed edited version of how to install the Resurrection ROM by westcrip...
as have seen too many users that seem to be skipping parts or confused of the installation.
This is also for users like myself, who just started on this site and can't post on Development side to find their answers.
BACKUP your apps of course...but DO NOT backup system data.Repeat!! DO NOT BACKUP SYSTEM DATA. Restoring system data can give you some problems because if you don't know what you're doing, can accidentally replace something from the fixes that screws things up!
-----------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------------
PART-1
Rom Installation (you MUST follow these steps! )
**Go to recovery mode( Vol UP + Power+ Home and hold until the Samsung Galaxy screen comes on)
1- Wipe data / Factory reset then (can Wipe cache partition or go straight to)
Install ResurrectionV1.1_official_remix_ics_4.0.3_XXLPE_FULL-WiPE.zip
*if you did not Wipe cache, can go straight to install from cache...
but if you Wiped cache then you go to install from external SD card and install 1.0_CWM.zip (this will be touch version)...
then choose - install zip from sdcard. - choose zip from sdcard. Scroll down to Download folder and select ResurrectionV1.1_official_remix_ics_4.0.3_XXLPE_FULL-WiPE.zip.
Please wait a moment.
2-Install gapps_for_remix_v1.1.zip
3-Install gapps_fixer.zip then go back and go to Advanced.
4-Wipe dalvik cache (required)
and Fix permissions and go back to
5-Reboot system
(at this stage it may take a while for first bootup, because we have wiped cache. It needs to rebuild it, so don`t panic.
It may take a while *average around 3-5min before getting to Installing applications screen)
At this stage, boot to system and configure the phone (change language settings, etc).
When finished, again reboot into recovery and follow PART-2
PART-2 (required)
This part it's mandatory here are contained the language, theme, AOSP apps and the T9 dialer if you want it...
or use default. ONLY install one of these:
*note: you're in regular CWM using up and down volue + power button to enter.
If you want the touch - reinstall it like before.
1.- Install the SMSfixupdate-afterboot+T9 Dialler.zip
or
SMSfixupdate-afterboot+default remix dialler.zip
go back
2.- Reboot into system
After finishing the boot it's highly probably that you receive a force close from android phone.
It's normal and it's the only FC that you should get.
Enjoy!
**There is a RAM Manager Fix (When you open the Task Manager app, there's a section called RAM and a button to Clear Memory.
The fix enables that button again... for those not working).
Here is a mirror link for this and other files: RAM Manager Fix and others
PART-3 (optional)
*This can apply to many other files you want to flash.
If you want to install Siyah kernel:
Place Siyah-v3.0rc4-CWM.zip (or whichever version you're using) in the root of internal SDcard memory ("download" folder) and go to recovery mode (Vol Up + Power + Home).
Go to Install zip from SDCard... and select it.
Yes and install... Fix permissions... Reboot.
**battery issues with Siyah?
go to recovery
wipe dalvik
go to "kernel specific options" to reset them or other performance tweaks.
reset kernal
fix permission
reboot
**No more video player?
Get the VideoPlayer.apk file (*have to do a search for it now until I find another working link to it)
and copy it to system/app using something like Root Explorer
Reboot
Hope this helps. I'll edit this when I have time (usually busy with other projects).
*Version 1.2 is out now Check it here.
Good job
Tho make sure you spend a bit of time regularly checking the thread (depending on how much action the thread gets, obviously). Once you make threads like these people invariably ask questions & it's best if the person who detailed the method answers most of them.
Thank you sir.
I will give as much time as I can on this, when questions come up... and I'll be sure to keep up with bugs going on on original thread... though they will be updating this ROM soon to 4.0.4.
When that happens, guess will have to update this lol.
(oh no, what have I gotten myself into )
Language problem
Hello!
Thanks for the thread, really useful for noobs needing help to fix some problems.
I am a noob... and I have a problem.
Everything is working fine, battery is ok, no fc... but language seems to be messed up, I get my language (spanish) in almost all settings and menus, but dialer is invariably in english. Some contacts dialogs show this behaviour too.
Thank you very much in advance!
Thanx a lot, really useful...cant wait for 1.2
SMSafter-reboot is the only fix i needed to fix my dialer fcs issue, after a dalvik cache clean and permission fixing. That was the only way, if some1 has same issue.
Sent from my GT-I9100 using XDA
Hi Miguel. The ROM is mostly for English and some language settings are off here and there. Mine too shows Chinese characters in some parts. I think this has to do with where the phone is originally from.
Version 1.2 will be out soon (based on 4.0.4) and should have more bugs fixed. I will see if there's anything can be done to help you with Spanish settings.
*glad it's helpful for you guys.
Thanks for a good simple guide.... it is getting pretty difficult to find answers with so many posts in the main thread.
Will you be making a similar step by step guide for ver 1.2 that should be out soon?
If it is needed I will. Will have to wait for it to come out and see if instructions changed. The process will be easier (after what westcrip said), not needing to add gapps fix, etc now I think.
Anyways, if I think needs more detail for newer users, I'll add a new thread for it and post a link here to it too.
Which dialler
I'm a true noob and I'm rooted with CWM installed and I'm giving serious consideration to this rom. My only question at this point is what are the differences btw the 2 diallers and do most folks prefer one over the other?
Hi tlmacson. It's a very good fast and smooth rom with good support. 1 dialer gives you T9 abilities... which means when you start dialing some number, it shows you contact(s) that much those numbers.
But there are some bugs in it not working for some, so recommended to install the default one and add some other app that does the same, or install T9 on after the default.
PS
If you want to give this ROM a try... the new 1.2 version will be out any moment which should have easier installation with hopefully less bugs ^^
I have been using it for a few weeks now. It has run really smooth, the only bugs are very small and do not effect the use of it daily.
I had a few problems with the dialler, so I installed exDialler. I actually prefer it, it has t9 searching and can be skinned to look like ics dialler.
I will definatly give ver 1.2 of the rom a try too.
Yes, that's the 3rd party app people like for T9 use: exDialer
It also allows you to give it black theme.
HELP!
Cyber i'm wondering if you did test the 1.2 PRO resurrection I want to upgrade to it but i don't know if it is a FULL WIPE or not because westscript didn't mention it also there are no GAPPS and FIXER within the thread can you please confirm for me this?
I think that I may just do that since I'm not having any real issues with the leaked "stock" XXLPQ. I appreciate your advice and dialer explanation.
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Test
Thank you cyberboob.
I will try 1.2 and see how it goes, anyway I will install exDialer to fix my languages "problems" (it is not a dealbreaker but is disturbing seeing some dalogues in other language).
According to 1.2 changelog this version is promising.
cyberboob said:
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Click to expand...
Click to collapse
thank you. i'll try without the wipes
Sorry.. a full wipe is needed again (or more bugs will be present).
Follow these steps:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*Also westcrip will post a new fix update for some new bugs reported by some users.
cyberboob said:
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Click to expand...
Click to collapse
I know I'm showing my "noobness" but I thought that the kernel was part of the ROM; so how do I install the kernel after the ROM?
Same way you installed the main ROM.. go into recovery mode and select the folder you placed it in (usually internal sd card "download" folder) and flash it "yes". Fix permissions if want and reboot. Same with anything else you need to flash/CWM after/before.
Hello Guys,
First of all, this is my first post here and also this is my first time flashing a custom ROM in my phone.
I would like to ask for advice regarding my current situation.
I came from stock ICS 4.0.4 and flashed android revolution hd 17.1 through CWM recovery. Everything went smooth in the beginning but later on, I noticed that there is lag during home screen panning.
Here is how to create the said lag.
1. In the home screen, you should have an app inside a folder. Open the folder, open an application. preferably not a very lightweight application.
2. After launching the application, exit using the back key.
3. Immediately, pan the home screen left or right.
4. You should notice a slight lag which is not present when panning the home screens that does not come from exiting an application.
So i thought this could probably a problem with some cpu and memory management.
Anyone have the same experience with me. I use the default touchwiz launcher btw.
And also I tried re-flashing the rom and selecting the perseus kernel included but the problem still exists.
If you have any suggestions how I can remove the said lag, please do so. I like the speed of the ROM and the smooth animations but the consistent lag that I am experiencing is just more noticeable because everything else is smooth.
Thanks in advance.
I don't experience this... :3 Same ROM.
xPlayGunZ said:
I don't experience this... :3 Same ROM.
Click to expand...
Click to collapse
No lag for me. Did you do a full wipe before flashing ARHD?
xSpeced said:
No lag for me. Did you do a full wipe before flashing ARHD?
Click to expand...
Click to collapse
I am not really sure if I did a full wipe.
But I wipe cache, wipe dalvik cache, used the wipe that is provided with the AROMA installer.
The internal sd card remained intact.
Try wiping in CWM data and caches en then reinstall the ROM.
I get the same thing using Perseus kernel. I like the options it gives but the lag really bothers me. Using cleanrom 4.5.
http://forum.xda-developers.com/showthread.php?t=1873670
Having a minor problem similar to the above thread - icons disappear from home screen after reboot for apps on sdcard.
I changed launchers from trebuchet and this seems to have remedied the problem for the time being for any other launcher so far.
The thread above suggests launcher change is only a temp remedy and unchecking fast boot android setting may help too.
But that setting is missing in cm11-0712 - anyone know if this setting still exists or where one may find it?
Thread above also suggests real issue requires an added flash of Convert2ext4 which is prob too complicated for me to understand at this point and so I wouldn't try it without more study - not even sure if this particular flash would play right with my current ROM.
Anyone else with this same problem?
Model: YP-G70
Android: 4.4.4 = CM11-20140712-UNOFFICIAL-venturi
Kernel: default = 3.0.101-G70UEK18 [email protected] #1
Full wipe and flash again that's all I can tell you
Sent from my YP-G70 using XDA Free mobile app
troy5890 said:
Full wipe and flash again that's all I can tell you
Sent from my YP-G70 using XDA Free mobile app
Click to expand...
Click to collapse
Just out of curiosity - if I full wipe (i think full wipe means in cwm to do factory/data wipe & cache wipe & format system & dalvik cache wipe) and then attempt to reflash the same rom cm11_0712 - would I have to restart from scratch meaning cm9 to cm10 to cm11_0712 or can I just push cm11_0712 directly? I am asking because I think cm11 already contains a kernel embedded so this might work directly?
Then of course I would have to restore my apps from TB which I'm still working on learning how to do. But am interested in poss increasing performance by turning on ART so I'd want to turn on ART first thing and then one by one restore my apps+data. Would this also work? Or is it not advisable to restore from backups with data from before ART was enabled?
Could I poss also restore some system data like launcher & live wallpaper data settings at this point without being too destructive?
I don't think you have to start over from CM 9, unless you're coming from q stock ROM, which you aren't. But yeah, just do a full wipe and reflash CM 11. As for ART, I wouldn't recommend using it until there is CM for Android L. Oh yeah, and restore your apps BEFORE you convert to ART if you haven't ever messed around with it before. Your device will automatically do the conversion from Dalvik to ART once you enable ART in Developer Options, then you will be able to mess around with it. Hope this helps
__________________________________________
Samsung Galaxy Player 5.0 (Model YP-G70)
• Carbon ROM 4.4.4 by Meticulus Dev Team
• Daily Drivers Kernel
Yes, thanks. Perhaps ART is alittle too much to bite off for now and will wait. Since my other thread talks about FC's, I was thinking ART might help too but better instead to just direct re-flash cm11 fresh vs update flash (what I had been doing and redoing). Everyone's tips very helpful too.
Just a quick update - for other reasons, I reflashed cm11 fresh (full wipe) and restored apps from TB backups. The trebuchet home screen icons still disappeared for sdcard installed apps but also poor battery life returned too. Tried to mess with settings again to save more battery life but not so good battery & this compelled me to switch to carbon ROM fresh install as a new try out.
This now has launcher3 & home icons disappear too & the few battery saving settings get the battery life to pretty good. So going to stick around with carbon for a while for now - many more settings in carbon too if that appeals. As for the icons disappearing root cause still not sure exactly but at least carbon seems to support std fix also used with cm11 to change launchers to something else. Am using smart launcher instead and home icons don't disappear with it.
Sent from my YP-G70 carbon 444
I have read pretty much forums and other websites to find a solution for my problem, but did not find any so far.
I am happy with my Galaxy S2 for more than three years now.
The last 1,5 or 2 years I have installed and tried a lot of custom roms, Ice Creams Sandwiches, KitKats and now also Lollipop (Omni and CM).
The last half year I have the next problem.
After installing a new rom and installing the apps I would like to use, the phone is nice smooth and fast, with a nice fluid UI.
But after some time ( after 1 or 2 weeks), the phone realy becomes suddenly very, very slow....opening apps takes a lot of time, often 5 seconds or even much more
Clearing cache, restart, clearing dalvik, nothing helps....the only thing that works is a complete fresh install.
There is enough diskspace and free space. I could even install quit some extra apps if I would like to.
This is the way I install a new rom:
- factory reset
- clear dalvik, system, data
- sometimes I reformat the internal storage (which is best: fat32, EXfat?)
- flash kernel wipe
- install rom, gapps and mostly superuser
- reboot the phone, do the settings
- install all wished apps
- sometimes I do a dalvik wipe and reboot again.
The phone is now nice smooth and fast.
The strange thing is, after these steps, I do not install anymore apps or widgets anymore. But still, after about a week, the smoothness is over and all that left is a lot of lag......
Does anybody know what causes this and how this can be solved?
Is it possible, that the flasdrive has become corrupted or bad, after this three years and if yes, can this be tested?
Any ideas would be great!
Best Regards,
Branko