Just for kicks, i tried turning my phone off, taking out the SD card, and turning it back on. holy frig! It loaded the apps (in settings, to clear caches and stuff, force stop if needed), turned off, SO much faster!! Like, warp speed. Compared to the well over a minute with my current class 4 sd card installed... im truly amazed!!
I need one of these like, tomorrow!! lol
The one thing i didnt understand, is that since moving app data to the external SD card isnt actually possible (despite the deceptive "move to SD card" in the app settings)... alot of the apps didnt show their correct icons or names in the app settings menu with my card out. But - even to just take the card out and look at it on the computer, all thats on there is camera photos, wallpapers..... a couple of things in directory bind, but only for 2 apps. well over 2 apps showed the incorrect icon and name. But... why??
ok, so ive since invested in a class 10 sd card...... and i notice no difference with having the phone calculate storage, powering off (the 2 main time wasters) since when i had my class 4 card.....
the only extreme difference is with no card in it.
For all of you who used class 10 SD cards, did it take the storage roughly 3 minutes to calculate (when you keep your caches cleaned out regularly), and the phone over a minute to power down, when you power down or at least restart once a day??
im just wondering if the extreme difference in speed is to be expected. even with the best type of sd card.
Hi
what ROM and Kernel?
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
Hi
what ROM and Kernel?
Click to expand...
Click to collapse
The rom is this one here actually: http://forum.xda-developers.com/showthread.php?t=1994902
Since i was new to the android world and rooting and such (still kind of am), i went with the pure stock version. I had actually decided to use the legit update, but it turned out my "brand new" phone had already been rooted, realized after a couple hours of trying to get it to update the legit way... maybe they had to to carrier unlock it, not sure. I knew for sure once i got into recovery for the first time, that it was already non factory. But, i didnt complain, the phone worked well and had no physical scratches or anything.
The kernel says (im not sure what much of this means):
"3.1.10-I927UCLJ3-CL970642
[email protected] #3
smp preempt thu oct 11 14:00:57 KST 2012"
Im guessing that last line isnt important but i didnt want to leave anything out.
Im not too sure what kernel means, unless referring to corn. Is that an important factor in the speed? Would changing it if needed ruin my whole current rom setup?
Ok so it is more or less stock and rom and kernel are UCLJ3. Thats fine just wanted to be sure. Btw: the whole kernel line is important as one can see the build, builder and build time which all is important to identify.
You can try another kernel without any impact to your ROM as long as it is ICS compatible. You may take a look into sediROM its installer has all available Kernels where you can choose from (v2.0 beta has absolutely all added). You can start sediROM installer and choose to not install the ROM but only modify the kernel. That way you can be sure that all requirements for flashing a new kernel are met (e.g. removing dalvik cache) without loosing data. But be warned i never tested that on pure stock!!
A better way may be to install sediROM and then choose the modify mode instead but I absolutely do not want to force you to choose sediROM !!
Nevertheless flashing sediROM or simply flashing a new kernel only:
As always keep in mind that doing a nandroid backup is essential!!
But back to topic: to be honest I'm not sure about your problem itself. You told that you have slow speed when opening your app drawer in the launcher? The other thing mentioned was calculating storage (I believe you meant those in settings?) and powering down.
Well i have a class 10 card with atm 1 GB free storage and need 10sec for all calculatings (settings). A power off need about 10-30sec and opening my app drawer with 114 apps installed take less than 1 sec.
I use sediROM v2.0 beta.
So you may try flashing a litekernel version. Maybe removing the dalvik cache may help a little, too - at least it will not harm (remove dalvik cache from within recovery).
My recommendation would be - if I were you:
0) backup! /efs and nandroid!
1) remove dalvik cache and /cache
2) if that doesnt help: flash a litekernel
3) if that doesnt help: flash another ROM
-----
Sent from my SGH-I927 using XDA Android mobile app
I do go into recovery regular and clean the regular cache, but never the dalvik cache. Ive read everywhere that people recommend doing that just before formatting and installing a new rom, so ive always thought that the dalvik cache held something important (like user data).
is that something i should be regularly cleaning out too? If so, and i havent for over a year, could that be any part of the issue??
The main 2 spots i notice it very slow is when opening the storage (within settings), and when powering down. the app drawer does open right away, but it does take a while for everything to load up and all app sizes are accurate, probably the same 3ish minutes as when starting from storage.
but other than that its been running great so its weird that only those 2 spots are slower.
Pawprints1986 said:
I do go into recovery regular and clean the regular cache, but never the dalvik cache. Ive read everywhere that people recommend doing that just before formatting and installing a new rom, so ive always thought that the dalvik cache held something important (like user data).
is that something i should be regularly cleaning out too? If so, and i havent for over a year, could that be any part of the issue??
The main 2 spots i notice it very slow is when opening the storage (within settings), and when powering down. the app drawer does open right away, but it does take a while for everything to load up and all app sizes are accurate, probably the same 3ish minutes as when starting from storage.
but other than that its been running great so its weird that only those 2 spots are slower.
Click to expand...
Click to collapse
Cleaning the cache on a regular base will not harm but IMO not doing anything useful.
The dalvik cache does not contain anything important like user data. It is filled when you boot your ROM with let me say "uncompressed" version of all your applications. That means because they are "uncompressed" they will open faster. Removing that cache will only let the ROM re-create that cache and this can solve some problems too. But it is an important thing you ever should do after flashing a kernel. Normally each ROM out there will do that for you, too because there it is needed too of course.
So no you do not need to do that on a regular base Android will update the cache for you (normally). Only when you encounter problems, flashing or upgrading ROM or Kernel.
Related
Just like the title says im looking for the best clean option. My phone gets really sluggish at times and I would like to increase the internal storage for memory and cache.
Have you tried Cachemate?
Try changing the vm heap size to 32-48. This will not give you more internal memory, but will give your larger apps (launchers & such) more room to breathe, so to speak. If your default isn't already 32, I'd try that first. Move your way up if needed and see what works best for you. Lower numbers can cause force closes and larger numbers can cause memory management issues. 40 always works well for me, 44 when I was using LauncherPro.
Almost forgot, you can do this with the app VM Heap Tool. It's free on the market.
Thanks plainjane, im trying it as we speak.
knowledge561 said:
Thanks plainjane, im trying it as we speak.
Click to expand...
Click to collapse
No problem, hope it helps :] I've also found that rebooting every day keeps the phone from getting bogged down. Using the "hot reboot" option from Widgetsoid works for me and takes less than a minute to reboot & reload the os.
Let me know how changing the dalvik vm works for you. It should help. It might not solve all of your problems, but it definitely made a noticeable difference for me.
My phone for some reason boots up faster now that I changed the VM to 44 And it everything is much snappier. Rebooting is understandable. I've just rebooted for the first time in 3 days.
Glad it helped!
It's a neat little trick that I haven't seen mentioned very much.
I don't think that availability of internal storage itself has a huge impact on performance. Increasing the VM heap size certainly could though.
knowledge561 said:
Just like the title says im looking for the best clean option. My phone gets really sluggish at times and I would like to increase the internal storage for memory and cache.
Click to expand...
Click to collapse
Here. I've done it, make sure you follow the instructions:
http://forum.xda-developers.com/showthread.php?t=855424
Install
1. Copy FR_Boot_CustomMTD_v1.5.7b_for_EVO, FR_Recovery_CustomMTD_v1.5.7b_for_EVO, FORMAT_ALL zips(& custom mtdpartmap.txt if you want to change the default sizes) to your SD card
2. Reboot into recovery
3. Make a Nandroid backup if you didn't already
4. Format cache, data & system partitions using my FORMAT_ALL.zip for ease
6. Flash FR_Recovery_CustomMTD_v1.5.7b_for_EVO.zip(this patches the recovery to use the custom partition sizes)
7. Reboot into recovery again
8. Restore Nandroid backup or flash new ROM but don't reboot
9. Flash FR_Boot_CustomMTD_v1.5.7b_for_EVO.zip(this patches the kernel to load the custom partition sizes)
10. Reboot
Click to expand...
Click to collapse
On step 7, I've rebooted in my recovery (amon) by pressing selecting reboot, pressing volume down and then getting back into recovery, as while in recovery, I found that you can't adb to get back into recovery.
I have used CM7 on my Incredible for a while now and have had to constantly wipe and reinstall every week or so. When i install, the ROM runs perfectly, with all my apps working and everything. After a few days though, most of my apps force close whenever I open them. Namely, messaging, Gmail, and browser force close, along with my market installed apps.
This has happened to me many times now and I can't figure out how to fix this issue. I have changed different options when installing the ROM and tried Fix Permissions in Rom Manager and nothing fixes it .
My friend's phone as well as my dad's have had this same issue on CM7 as well. Any help would be greatly aprreciated!
bravesfan171 said:
I have used CM7 on my Incredible for a while now and have had to constantly wipe and reinstall every week or so. When i install, the ROM runs perfectly, with all my apps working and everything. After a few days though, most of my apps force close whenever I open them. Namely, messaging, Gmail, and browser force close, along with my market installed apps.
This has happened to me many times now and I can't figure out how to fix this issue. I have changed different options when installing the ROM and tried Fix Permissions in Rom Manager and nothing fixes it .
My friend's phone as well as my dad's have had this same issue on CM7 as well. Any help would be greatly aprreciated!
Click to expand...
Click to collapse
Any ideas?
Check and make sure your data/data partition isn't full. If it is, grab a cache cleaner from the market to free up some space.
This actually happened to me earlier tonight.
Had to reinstall to get through the night til I got back home, but I may need to go back to another ROM if this keeps up. Glad to know I'm not the only one though.
Smabbage said:
Check and make sure your data/data partition isn't full. If it is, grab a cache cleaner from the market to free up some space.
Click to expand...
Click to collapse
That's true, didn't think about that. Will I have to keep doing that more and more if i install more apps though?
This happens to me and all my friends phones with the cm7 final. They keep telling me its user error. We all have to clean wipe about once a week because of force closes. I finally switched it redemption rom
DROID Incredible
By the way i never had a single problem with the nightlies
DROID Incredible
06stang said:
By the way i never had a single problem with the nightlies
DROID Incredible
Click to expand...
Click to collapse
If what Smabbage said is true then hopefully that'd make sense. That way when you consistently install the nightlies, there is no way for the data partition to fill up all the way. Good to know. thanks!
I've been fighting this exact same problem. The only way I can keep it from happening is to do a full wipe and let the Android Market reinstall most of the apps. Then I can use titanium to bring back the missing apps and system settings.
Here's the things I've tried, with no success:
Wipe Cache / Wipe Dalvik Cache
Fix Permissions
Nandroid Backup then Restore (ok so I didn't expect that to do much)
Uninstalling apps, moving apps to SD (using the Android method, not Apps2SD)
Another interesting thing is that I run Watchdog, but instead of force closing, it pops up a message saying "Disk IO Error in Watchdog". That makes me wonder if some partition (Cache, data, I dunno) is out of space or worse, there are physical problems with the internal memory of my Incredible.
I have one question for everyone - How do I see how much space is available on each partition? I mean, I can go to the Android settings and see App Data storage left or SD card space left, but is there an app or tool I can see that will show me each partition with space left?
jjdoyle20 said:
Another interesting thing is that I run Watchdog, but instead of force closing, it pops up a message saying "Disk IO Error in Watchdog". That makes me wonder if some partition (Cache, data, I dunno) is out of space or worse, there are physical problems with the internal memory of my Incredible.
I have one question for everyone - How do I see how much space is available on each partition? I mean, I can go to the Android settings and see App Data storage left or SD card space left, but is there an app or tool I can see that will show me each partition with space left?
Click to expand...
Click to collapse
Had exactly same issue (even same Watchdog error) and Smabbage's answer was spot-on.
To check, open terminal emulator (gives you shell prompt) and do "df -k" - this will list all filesystems and, among other info, how full they are. My "/data/data" partition was full. Cleaned up some cache's and my phone is back in action.
Seems like a lot of games (and Netflix) fill the /data/data partition. Wonder if it is possible to make it larger at the expense of built in memory?
In any case, may be a good add-on to CM to monitor space in /data/data and give a reasonable warning when you close to running out.
I have been using CM7 for a while now and the apps that force close, are usually tied to the SD card. Try moving them to internal and see if it helps.
same here..
I use galnet miui (cm base)
after a few weeks, it shows 'disk io eror in watchdog'
and many programs fc.
never had this problem before.
someone can help me?
how can I fix this..
I know this is an old thread, but ive been searching around to see if other people have this problem.
i have found a temporary solution. open Root Explorer and go to /cache/dalvik-cache....use multi-select to select all items and then delete. reboot (IT WILL TAKE A WHILE TO REBOOT, IT IS REBUILDING, IT CAN TAKE UP TO 15MIN DONT PANIC) yes, this is in fact "wiping dalvik-cache" but ive gotten much better results doing it manually than through CWM.
this will calm your phone down at least for a few days with no force closes/service interruption, but you will have to do it again..........and again, and again. its better than having to do a full wipe though, obviously. hope this helps anyone who is still having this problem.
Hello everyone,
I've compiled a kernel which separates the NAND memory into 3 partitions (well more then that but anyway). These partitions are system, data and cache like a native Android phone (which also has recovery but we don't need that). Previously cache was linked to a directory on the data partition which was constantly becoming corrupt causing errors on start-up. Often clearing dalvik-cache would allow Android to boot but data was lost. There's nothing to say that this will solve the problem but i'm giving it a go so thought I would post it up for you to try also.
The cache partition is 20mb which means the data partition is only 90mb or so. If you like a million apps on your phone either put some on your SD card or don't use it
I haven't completely incorporated this partition into the initrd which means that currently it will only mount if data is also on NAND but this can be changed easily enough, but for testing purposes I want everything on the NAND chip anyway.
Downloads from market on all versions of Android, unless the init.rc directory is changed in Gingerbread, all go to the cache partition and are deleted on restart. What this means is that you can't download and install an app larger then 20mb (which isn't recommended anyway with the small amount of data space available). This is a drawback but for those that use data on SD it should be possible in the future to utilise more of the NAND memory for cache so you can install whatever you want. I don't know of many apps larger then 20mb anyway though.
I have included a modified version of ATools in the zip. The standard version will overwrite the partition values and the kernel won't work properly so if you need to modify the kernel use the version included. It is also important that you DO NOT change the system or data partition sizes in ATools as this hasn't been modified to account for the cache partition so will mess it all up.
I have also included an androidupdate.tar modules update for the kernel in case your wifi doesn't work after flashing the kernel.
I think that's it for now, let me know how it goes!
EDIT::
One last thing, you will need to wipe your DATA partition to use this kernel because some of your data may be positioned where the cache partition is now, so if you load this kernel and android is heavily corrupt you know what you have to do!
To check the kernel is working correctly you can type "df -h" into a terminal and it should show all of the current partitions including one called cache on mtdblock4.
Should now work with polaris, kaiser and vogue. There is a VOGUEIMG.NBH included for those who have trouble with ATools. It is completely untested on Vogue so sorry if it doesn't work.
EDIT
I have re-uploaded a modified kernel because there was some issues with data with the last one. If you have already applied the last one flash the new one and apply the module update again
testing will leave feedback
Ok, using your Scoot CyanogenMod 6.1.2 (RLS6) [16.03.2011], overclock via atools+roguetools to 529, gpu oc, battery units tweaked to suit my battery.
No SIM card yet, don't have one to put there, sync with google to get contacts.
Installed GoLauncher. Enabled JIT and Keep Launcher in memory.
Once in a while, Android is killing all apps, launcher included... strange...
Nevermind that, it was Cyanogen and the LongPress BackKey. LongPress on our Kaisers during lag can become short press
First couple of days of heavy use I've had in ages with no corruption. First day of my new job today so it's been on Google Navigation for 3 hours and used extensively during the day. Had to do a hard reset at one point and everything was fine. had a few soft reset's too. Don't get me wrong, i'd be surprised if this is a fix, but it's been a while since I've used my Kaiser this much and not had to wipe my data partition!
Update: CM is a bit slow, trying:
VaniljEclair RLS11 - A fast & stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-08-19]
And everyting seems good. I've pushed it a little, several normal reboots.
Had to reflash system (didn't reflash data). No errors, FC's, whatevar. Everything works, yet didn't try to make/receive calls. Its 1am here...
Now this particular version, has a god damn bug that is get the best of me. The Power Button and the red button won't make the phone go to standby. If i long press, i get the normal reboot/power off/airplane etc menu, on both keys. But single press is ignore... Any idea ?
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Using this kernel with Valentine 1.02. GPU overclocked and CPU @ 520mhz. Super fast and for the first time... no data corruption! Verry happy so far!
daedric said:
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Click to expand...
Click to collapse
Well in theory not too hard, there is a feature built into the linux kernel called cpufreq which is currently disabled in our kernel because our cpu and chipset code doesn't support it but krazy-killa has been working on getting it working in his kernels with a little success as far as i'm aware but i'm not that sure. I haven't personally looked into it but if I get some spare time I definitely will. I've started a new job now which i'm sure will keep me quite busy but I still intend to so some work on the Kaiser when I get time
Best of luck on your new job! I wish i had enough knowledge to continue the kernel development, but i'm quite a ignorant
Still, thank you, till now it's one of the best kernels i've used.
Hi Scoot!
I love your kernel. No data corruption so far (two days). did a few stylus resets and stuff.. Magical =D. Now IMO we only need better sleeping and autofocus to call kaiser a fully android device! Please Keep up the awesome job, scoot! thanx, danke, sposeeba, bedankt, aciu, dzenkuja!
Nice job scooter, I've been using Scoot CyanogenMod 7.0.2 RLS2 [28/04/11] @ 500MHz, and it seems fine so far.
I tried Fat Free Froyo before CyanogenMod, which also worked great for the few hours it was running. I'm not sure which one to stick with though.
Keep up the good work. I wish I could help with the development, but I have yet to learn programming (been ten years now ).
This kernel looks pretty stable, but just a few quick questions:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Thanx for your great work, finally it seems to be fully usable for me and if you and Krazy-Killa would be able to work together to manage the power consumption, then it would be amazing, because I am going to get new phone (running some new extensive business and I can not afford to be not reachable when something happends on Kaiser) and give this lovely piece of HW to my son... And I really do not want him to have a WM machine But Android needs to be stable for him to use Well... he will get it for his 10th birthday at 6.9. so we still have some time to tweak it a bit more
if this works then it would be magical, your CM builds were so fast and awesome and if there's no data loss then... <3
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
PoXFreak said:
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
Click to expand...
Click to collapse
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
a.s.j said:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Click to expand...
Click to collapse
1) The cache partition is still using Yaffs2 because it is the easiest filesystem to configure at the minute, but the idea of making it a separate partition like on a native android device is that it can be changed to another filesystem in the initrd relatively easily. If it gets corrupted it will do what it used to I guess, but I haven't had any corruption as of yet so it's difficult to say. Hopefully if the cache partition get's corrupted it shouldn't affect data so you should just be able to wipe and format dalvik-cache in the install menu.
2) I made it 20mb because most android devices have 30mb or bigger and this is mainly because market app downloaded get downloaded here before being installed, so if you installed google maps for instance it would use up 6mb, plus the standard 1-2mb normally being used, but if you only had a 10mb cache for instance, you would only be able to install apps less then 8mb which is a little limiting really. I don't really care much about installing lots of apps in data or on the phone at all for that matter so having 95mb for data is more then enough for me.
3) You can put apps in the system partition in /system/app. The system partition is read only so all data for the app still goes to the data partition. You can still save a little data partition space though if you need it. Most installs of android are 80-95mb which should leave you 5mb or so to play with. Some all language builds pretty much use up all of the partition though so you need to look and see what space you have to play with before putting apps on the system partition. If you overload it you will probably end up corrupting it and having to reinstall. But to answer your last question, the system partition works in the same way as the data partition apart fro the fact that it is read-only and data is read/write.
I've modified my Kernel to use the NAND mtdblock3 (/data for everyone else) as the cache partition, since my NAND is pretty much shot to begin with, and have system and data on SD Card. So far it's made downloading Market Apps twice as fast, loading webpages pretty fast, and basically anything else that the cache is used for.
scooter1556 said:
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
Click to expand...
Click to collapse
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
PoXFreak said:
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
Click to expand...
Click to collapse
Can you not do all of this using the ATools i provided in the attachment in the first post? You should be able to load the nbh into ATools and then set the CPU speed, change the keyboard type and remap the buttons and then save it before flashing. Just don't change the partition sizes as this will mess up the cache partition I added until I make it more permanent.
For a few weeks i have been getting these total random shut downs of my DHD running the latest Virtuous Unity 2.35.
I saw that happening live 2 times on specific occasions/functionality calls:
1)After switching the DHD on and inserting the PIN to unlock the sim card...few secs and BAM....everything goes down. This happens from time to time.
2)Few secs after running the camera app...some loading goes on and BAM...here we go again...cell goes off
What the hell is happening, should i worry about the phone hardware or is it some wipe/format i didn't do properly prior to flashing the rom.
The problem is i noticed it also with other custom roms...but with those it never happened while i was using it, instead it happened getting the phone out of my small shoulder bag.
I am really afraid my cell has something wrong with the hardware...i was angry as hell and i tried to do some "heavy shakin" to see if the battery was not retained to its place as it should have but nothing happened...cell always on...
What should i do?
PS: i must say i tried almost 15 roms last 2 weeks but always used the related full wipe files/used a decent format/wipe procedure.
plz help me
---------------------------------------
Some tech stuff maybe you need to know
Device: Desire HD
Rom: (current) Virtuous Unity 2.35 (those days i flashed more than 10 roms, MIUI included)
Status: S-OFF HBOOT-0.85.2007 (CID-11111111)
Radio: 26.09.04.11_M2
RIL: 2.2.0131HM
Kernel: Stock that comes with VU
So that you know that's what i always did prior to flashing any ROM (currently using 4EXTRecovery 2.1.3 RC2) :
1)format system
2)format cache
3)format data
4)wipe data/factory reset
5)FLASH ROM
--------------------------------------
EDIT1: I noticed, just to keep you posted, that on the recovery menu the SD appear to be "not well partitioned", i don't know if it may be the cause.
Do you have app2ext working?
I'm guessing here. Try backing up your SDcard on a pc (preferably via cardreader) and giving it a thorough format with one partition only. You may need to delete the partitions first. I can't tell you how unless I know your operating system. If you continue having the shutdown issue afterwards you would be able to cross out SDcard problems at least.
Hi ROBINGAZI, thanks for your fast reply.
ehm, what is exactly app2ext?
I don't have a card reader right now, does it really change if I mount the SD via the phone? Anyways, i got a machine running WIN 7 x64.
hope this step will clear out the problem
Plug your phone to the computer as disk drive.
copy everything you have on the sdcard to a directory in your computer.
then click start>control panel>administrative tools> computer management.
a window will appear and you should see "storage"
in storage you will find "disk management".
you should be able to see your phone's SDcard there. right click and then delete the partition into unallocated space. Then right click and create a partition (fat32). format the partition.
if needed remount the sdcard to your computer (not the phone)
copy only one zip file (the rom you want to flash) to the SDcard (preferably something reliable like stock or something very close to stock).
unplug the phone and reboot into recovery. Do a full wipe...format everything apart from the sdcard if you think it is proper.
flash the rom and see what happens.
this way you can at least rule out the SDcard for causing your problems.
PS: Dont restore via nandroid...you could be putting the problem back into your phone.
BTW: Does your phone shut down properly or the screen goes blank like it would if you unplug a computer. Anyway make sure you dont just have a loose battery cover or battery before you try this out.
Thanks again.
Yeah my phone screen just goes blank like it would if you remove the battery from it while on.
I restored the SD card and it works properly. installed Revolution HD 5.2.6
As i stated earlier i also tried to shake the phone to see if the battery had some kind of faulty retention system but the phone stays on.
So i really can't understand what is the problem.
PS: I was curious, is there an application that tells you the entire life of a battery? meaning since when it started to operate?
NEW UPDATE ABOUT THE MATTER:
It's DEFINITELY the battery...i don't know why, i don't know with what criteria but it's the battery.
Yesterday i switched it with my brother's phone, obviously another DHD. Since then i have had absolutely no problem of any sort. He, instead, is experiencing random shut downs...
i think that the "problem is sloved" so to speak
the question about the battery app remains...or maybe there is a way to see the battery entire life cycle with a system file.
So...
I've had this problem for a while now, getting worse from day to day. I've asked about this before, but it wasnt solved.
Basically my phone is taking up data in the background. Probably updating, downloading something. Its so bad, that if i dont turn off data on the go, my 1.5GB are used in a day. Sync is turned off at all times
And another side effect of that is, that all that data probably has to be stored somewhere. So Im getting the storage space running out error. Kinda annoying cause I cant use gmail, Cant install any apps(insufficient storage available) etc.
I really have no idea where all that data is(after searching through all the folders for a while now)..
I'm on the latest AOKP Milestone(4.2)
Thanks!
There are a couple things I recommend doing in your position. First thing I would do would be to get an app that allows for more informative breakdown of what is using the storage. Something like diskusage should do the trick. This will allow you to see exactly where data is going, opposed to "misc" Perhaps this will show exactly what is taking up the storage, since you are rooted perhaps backups are the problem.
If that doesn't tell you what you want to know, or if you think an app may be using data behind the scenes then the next step I would do is to use some sort of data usage monitor. The built in one may suffice, settings > data usage. If not there may be better apps out there, although to be honest I have zero experience with those.
cupfulloflol said:
There are a couple things I recommend doing in your position. First thing I would do would be to get an app that allows for more informative breakdown of what is using the storage. Something like diskusage should do the trick. This will allow you to see exactly where data is going, opposed to "misc" Perhaps this will show exactly what is taking up the storage, since you are rooted perhaps backups are the problem.
If that doesn't tell you what you want to know, or if you think an app may be using data behind the scenes then the next step I would do is to use some sort of data usage monitor. The built in one may suffice, settings > data usage. If not there may be better apps out there, although to be honest I have zero experience with those.
Click to expand...
Click to collapse
Uploaded a pic what diskusage says. When i hit media it only opens the file manager and directs me to sd storage
BTW this what Onavo says has been consuming data this month:
Market Downloader - 800MB mobile, 2.4Gb Wifi, all in background - and no, i didnt download anything from the play store on the go and hardly anything on wifi - havent updated my apps in weeks b/c of missing storage
Android OS + Others - 530MB mobile and a whooping 12GB on Wifi! All in Background too.
Timoooo said:
Uploaded a pic what diskusage says. When i hit media it only opens the file manager and directs me to sd storage
Click to expand...
Click to collapse
It looks like you have some nested 0 folders in that pic. Perhaps cleaning that up will clear up some space. Side note, if you haven't updated your custom recovery in a long time it may not be a bad time to look into that.
BTW this what Onavo says has been consuming data this month:
Market Downloader - 800MB mobile, 2.4Gb Wifi, all in background - and no, i didnt download anything from the play store on the go and hardly anything on wifi - havent updated my apps in weeks b/c of missing storage
Android OS + Others - 530MB mobile and a whooping 12GB on Wifi! All in Background too.
Click to expand...
Click to collapse
If I were in your situation, I would probably just get a clean start. This also would get rid of the nesting problem I mentioned above.
- I would make a backup of my current setup, probably just using Titanium Backup.
- Backup everything I want to keep from my phone to my PC, going through the 0 folders.
- Use fastboot to flash factory images, allowing it to wipe everything in the process. The .bat file should do this automatically.
- Use fastboot to install a recent custom recovery.
- Push the sdcard backup from my PC to my phone.
From here you have a couple options, root and reinstall Titanium backup and restore some of your apps (no system data) or go back into custom ROMs. You could flash AOKP again, or pick a different ROM.
A bit heavy handed, but I think that would be the least time consuming option considering the problem(s).
cupfulloflol said:
It looks like you have some nested 0 folders in that pic. Perhaps cleaning that up will clear up some space. Side note, if you haven't updated your custom recovery in a long time it may not be a bad time to look into that.
Click to expand...
Click to collapse
Yeah I noticed that like half a year ago, had no idea why that happened. At one point I felt like everytime I flashed a new rom a new 0 folder appeared.. How does that happen?
cupfulloflol said:
If I were in your situation, I would probably just get a clean start. This also would get rid of the nesting problem I mentioned above.
- I would make a backup of my current setup, probably just using Titanium Backup.
- Backup everything I want to keep from my phone to my PC, going through the 0 folders.
- Use fastboot to flash factory images, allowing it to wipe everything in the process. The .bat file should do this automatically.
- Use fastboot to install a recent custom recovery.
- Push the sdcard backup from my PC to my phone.
From here you have a couple options, root and reinstall Titanium backup and restore some of your apps (no system data) or go back into custom ROMs. You could flash AOKP again, or pick a different ROM.
A bit heavy handed, but I think that would be the least time consuming option considering the problem(s).
Click to expand...
Click to collapse
I was actually thinking about a clean start, googleing how to wipe everything and I read that thats kinda not possbile. But thanks for those steps, I'll do that when I have time!
Thanks
Timoooo said:
Yeah I noticed that like half a year ago, had no idea why that happened. At one point I felt like everytime I flashed a new rom a new 0 folder appeared.. How does that happen?
Click to expand...
Click to collapse
Basically when 4.2 came out, it brought along multi-user functionality. Custom recoveries at the time, when wiping and installing ended up creating the nesting problem. Recoveries then were updated, which doesn't create a bunch of /0 folders (one existing is correct). This was a super common problem about a year ago when 4.2 came to be. There were hundreds of threads about this problem, with more detailed info about what happens, why, and how to fix it. Wiping everything is one of the solutions, and since this isn't your only problem, this would probably be the recommended solution.
I was actually thinking about a clean start, googleing how to wipe everything and I read that thats kinda not possbile. But thanks for those steps, I'll do that when I have time!
Thanks
Click to expand...
Click to collapse
I am not sure where you read that a wiping everything isn't possible, but whoever said that is all sorts of wrong. There are multiple ways to wipe things.
Just did what you said and it looks like everything worked! Everything is deleted, I have almost 13 gigs of free space, rooted my phone again and I'll probably install aokp or paranoid in a couple days.
No 0 Folders anymore and I'm sure as hell hoping that my data consumption will be fine now. I'll keep you updated on that in a few weeks again, but thanks for the help!
looks good thanks bud