Hi guys,
I've just installed ICS CM9 4.0.3 for HTC Desire and decided to use Darktremor A2SD+ to move the dalvik cache to my SD card. After doing this the volume of the ringer and notification sound is very low.
In the ICS CM9 ROM thread there are others that reported this issue but they said it can be fixed by wiping cache and dalvik-cache, but it did NOT work for me.
I did 3 times a clean install and it did not work. I also had this issue when I switched to GingerVillain first and never got to fix it until a full wipe and install of
Oxygen ROM.
Is this a known problem ? Is there a fix for it ?
Maybe at least someone can point me in the right direction to search for the problem (I just started working with Android ROMs, so I'm not very skilled at this, but I can give it a try)
Thanks.
Related
I can not install a HD rom on my partners Desire without it either locking up / freezing in use, power button to unlock the phone will light the buttons but doesn't power the screen or phone just restarts. Stock rom has run perfect for near a year never any issue and I have been running Starburst ROM with DATA2SD for 24 hours without any problems.
It seems that HD roms just won't work!??! It feels like CPU/GPU hang ups perhaps from the different voltage/clockspeed they use? In any case here's what I did maybe I'm missed something.
This is a launch desire locked to T-Mobile with all the latest updates. I have rooted the Desire using the latest unrEVOked and there has been no problems with this. I partitioned and formatted the 4GB SD card to 2.2gb FAT32/1GB EXT4/300mb EXT4/125mb Swap using gParted and full wiped all (data,cache & Dalvik) of phone using clockwork recovery 2.5.0.7 and installed SupeROM v2.0 D2EXT. This wouldn't run for very long at all without locking up or restating.
So I wiped all and installed SupeROM v1.5 D2EXT and this was the same.
So I tried another SD Card and problems were still there.
Reformatted SD Card to 2.2gb Fat32/1.5gb EXT4 using gParted
Wiped all and installed SupeROM v2.0 D2WE this ran for longer but would still restart or lock-up.
Full wipe again and installed RCMIXHD v3.0 D2WE This would last the longest but would still lock up or restart phone.
Deleted all partitions on SD card and formatted it all to FAT32 restored data and Nandroid backup so phone was back to a rooted stock. Phone ran fine for hours.
Installed Starburst ROM with DATA2SD and this has been running perfect for near 24 hours uptime.
Any suggestions?
Just to add I've rooted my Desire and Installed SupeROM v2.0 D2EXT without a problem and that runs perfect.
1.5GB ext4 partition is generally too big. Maybe the SD isn't class 6 and can't run Data2SD right. Maybe an explanation of why it isn't running right.
I used a two SD cards with various partition formats and sizes the lock-ups are still there.
Something else I've noticed is that each time the phone restarts the date/clock resets to 00:00 6/01/1980.
Maybe just a bad flash of the rom. Reflash it without a wipe and see if it helps. Try another rom to see if it's hardware issue.
Tried a few roms and the only ones that don't lock up the phone are the non HD roms. I think it could be hardware fault, but it really does run fine with stock rom and starburst rom so I at a loss as to what hardware is at fault, since surely the hardware would cause problems with non HD roms.
I'm going to keep trying different roms and see which works best. Could be all irrelevant soon once an official GingerSense rom is released.
I have the same problem (black screen with lighted buttons) and I have seen it with official 2.2, starburst 1.3.3.1 and 1.3.3.3 (data2sd 0.7 and x1). Could be a hardware fault. Can I be so unlucky? I have already had it for service for overheating-bootloop
Cool HD v9 DATA2SD works with no problems. It's a HD Rom and it's very stable and very fast so it does the missus.
Balor said:
Cool HD v9 DATA2SD works with no problems. It's a HD Rom and it's very stable and very fast so it does the missus.
Click to expand...
Click to collapse
Are you experiencing any lag? Especially with Sense frequently reloading itself?
I'm not, no. It's really quite stable and a very smooth rom.
Sometimes custom skins crash and revert back to standard sense skin but the phone is still usable.
try to flash a RUU. Then root your phone again etc
It had solved many problems i had before.
Hope it helps you.
Hi all,
I posted yesterday about an A2SD problem, I fixed the previous problem, but now another one has shown itself, I just finished installing all my apps to my Desire with MIUI ROM and the low memory issue was gone, however, when I rebooted the phone to flash Superuser 3 beta4, all my apps either disappeared or moved back to the internal memory, I am aware of how A2SD actually works and I have searched the website looking for assistance,can anyone here help me or link me to anyone with the same problem?
Thanks in advance
+1 i had this same issue on nexus one. Forced me too change back to cyanogen. Second time it happened to me, caused just by rebooting.
Hi, hope this is ok to post in this support thread...
Basically i have RCMIX3D RUNNYMEDE rom on my dhd. everything has been running fine for around 3 or 4 weeks.
Now all of a sudden my wifi does not work (says Error when trying to turn on).. and neither do my volume buttons.. its so frustrating... i have thought maybe i can do a complete wipe and re install the custom rom but i cannot use the volume buttons in clockworkmod recovery to move down and select to install from zip.. neither can i do this from within rom manager as it says it cannot open the file.
Is this a hardware failure or can it be resolved by re installing this or another rom? has anyone else had this problem?
Hope somebody can help me!
Cheers
Gaz
Could be a hardware problem, but I would try wiping and reflashing a ROM first. If your volume keys don't work in recovery you can use the softkeys to navigate (home=up, menu=down, back=back, search=select).
If it still doesn't work after reflashing, maybe try some other ROMs, if they still have the same problems then it's likely that the issue is with the phone hardware.
The fact that your volume keys don't work even in recovery (when there's no ROM loaded) sounds like that bit might definitely be a hardware problem.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
I have some issues with my Defy, it worked great for about 5 weeks with Quarx's CM7 the i started to get random lags, all apps crashing and freezes. I wiped the cache and dalvik cache, still not working.
After that i installed MIUI, worked pretty good for 2 days then got the same problem. Wiping the cache didn't worked here either so i decided to re-install CM7 (7.1.0-jordan) but still got the same problem.
I tried lowering the CPU settings to the default but it had no effect.
What else can i do?
I'm kinda new to this so please, have mercy.
Thanks in advance!
Could it be the RAM (not enough available)? Use an app like this or similar and see if there's any difference.
Also, if you like CM7, go for CM7.2 - it already has a RC version, and it's stable and fast (bug fixes included, tweaks, interface optimizations, etc). Regarding the CPU: it's not necessary to underclock to the stock 800mhz value, just be careful about the voltages (don't go too low suddenly, or you'll get freezes or random soft restarts - try to undervolt progressively).
Plus, it's a good habit to wipe Cache and Dalvik cache before and after flashing a ROM/nightly.
it's not the ram, i used netqin from the beginning which has a widget that shows available memory and a task manager and the lowest memory i ever had was 100MB. currently on cm7.1 i have 213mb available.
is there a way to completely revert all changes, like a factory reset?
Actually, task managers on Android don't fix any problems, they even cause problems - I would get rid of that if I were you.
Like a factory reset? Wiping data from custom recovery (but you'll lose all data, settings, apps, etc on the phone), but you keep your current ROM.
Give CM7.2 a shot, it might be better.
Edit: Did you have these problems before installing that task manager?
i really don't care about the current ROM, i would go for the stock android just to have a working defy. do i need to flash a sbf before installing 7.2?
could it be a hardware problem?
Don't flash a SBF!
If you are already on CM7 just flash a CM7.2 version like a nightly (wipe Cache and Dalvik cache, before and after flashing). When I used CM7.2, I was happy with a version by maniac103, from 27 February. Stable, fast, good battery life.
If you really don't care about all of your settings and apps and data and so on, you could try to wipe Data in custom recovery before installing CM7.2, it might solve that issue (but I'm not sure, and it's not really worth it to try it now, only as a last solution). But if you do that, remember to flash gapps too, after the ROM.
But first try CM7.2 and use your phone for a while without that task manager.
No, I don't think that it's a hardware problem, especially if it worked fine after you flashed MIUI.
just installed cm7.2, will update if problem still occurs.
Thanks!
You're welcome.
Great, I hope you'll get rid of those issues. Did you also remove that task manager?
Yes, kept just the basic stuff for now. i have a problem with the proximity sensor, after a call the screen stays off and i have to remove the battery. I tried loosing the back screw and several ways of disabling the sensor but none worked.
Any ideas?
I noticed that in every single ROM thread it says to wipe data and factory reset before flashing..
but one time i forgot to do it and just wiped cache then flashed a new ROM, and so on, and so on..
After i booted my phone i noticed that all my data and settings was exactly how it was before i flashed the new ROM..
i have done it this way with Juggernaut 5.0 and SlickMod 3.6 RC1 and never experienced a bug or anything unusual by doing it this way.. (although every time i tried an ICS ROM I followed the instructions perfectly)
it sure saved me a lot of time setting up my phone again
my question is ... has anyone seen bad results by doing it this way?
Theres more to it than that. The problems arise when you flash system data on top of another rom's system data. The ROM maker may have put tweaks in that mixed with another ROM's tweaks could cause unwanted effects. For example, TDJ builds his roms and kernal specifically for his roms, and states if you use another kernal his tweaks wont work.