Related
Trying very hard to keep the Internal Storage on my Eris @ 50% . Wonder how low I can really go before I run into issues ???? Too bad I'm not rooted otherwise I would move/install some of my apps to my 16GB MSD card.
gemro311 said:
Trying very hard to keep the Internal Storage on my Eris @ 50% . Wonder how low I can really go before I run into issues ???? Too bad I'm not rooted otherwise I would move/install some of my apps to my 16GB MSD card.
Click to expand...
Click to collapse
Just try to make sure you're only hanging on to apps you actually use versus something that was cool for like 10 minutes and then forgotten. I would also reccomend wiping dalvik cache every now and then. Also there's a cool little app called app monster that allows you to store apps on your sd card. you can't run them but if its something you dont want to get rid of then you can have a back up.
why does it matter if your internal storage is at 50%?
Maybe a bit of obsessive complusive (not saying this to be derogatory) mixed with hoping to keep his phone as fast as possible?
Don't know about the compulsive part, but yeah I am looking to keep my phone "mean and lean". I gather I can load up my phone with tons of Apps and not be concerned about how little storage space I wind up with. By the way I am a Windows person , and learned the hard way . Tis not the case with Android?
Yea, the system paths are set up a little different in that respect. What's holding you back from rooting? If you're leaked, I understand, and sympathize. If it's warranty issues, then you can always recover and go back to stock. If you aren't sure how to do it, well there are plenty of how-to's and helpful people here. Apps 2 SD is pretty nice, and that's just the beginning...muahaha.
I was leaked the day it came out in March ..just my luck . Just wondered about space. Saw/heard on another forum where someone ran out of space and ran into issues. To me this is the best forum to get positive answers
I would like to keep this short and sweet so...
Basically heres the low down: I got a G1 almost a year ago, got into Rooting/flashing 7 months ago. I noticed in the beginning almost every rom was giving me a problem, Freezing up, hanging for long periods of time, etc. I eventually found a very nice, stable rom thats been lasting me for about 6 months but as of late was being horrible. Force Closing everytime I got a text message, REALLY Hanging for long periods of time, freezing up. Etc.
So I finally got FED UP, and decide it was time for a change, so I grabbed MLIGN 3.3v having seen so many good reviews and what not, thinking it would be the remedy to my poison. I cried. So in short, here is whats going on:
1. It seems to only wanna cooperate when Plugged into the USB, which, isn't too practical.
2. When not plugged in, it is NOT sluggish, but when loading into apps I've noticed it will hang for quiet awhile or completely lock up to the point only popping out the battery will work.
3. I haven't noticed it yet, but on the old ROM it would randomly shut off during phone calls; which leads me too....
4. When ever I shut the screen off (by pushing endcall) it seems to freeze and lock up and eventually either SHUTOFF or REBOOT into a SHUTOFF of the phone and refuse to turn back on until it has been plugged into the USB, or enough time has passed for it to 'forgive me' and by that, I mean randomly work again.
5: Various other things I cant think of right now.
So, basically thats almost everything. Whenever its plugged into USB though, it works like a charm (for the most part).
Would a problem with my Battery be the case? Which, would be awkward but a possibility.
Or did I just do something wrong?
I made sure to factory wipe the phone twice, even 3 times on the last go, I updated the ENG.SPL and Radio every time I tried to reflash just to make sure.
I partitioned my SD Card for 32MB Swap; 512EXT2 (and 7xxEXT2 I forget what it was) and I also upgraded it to EXT3, which showed some improvement... I believe.
So, I just would like to have my phone working, in a peaceful, obedient manner xD.
Forgive me for the block of text, and all help will be appreciated. Thank you guys... I await sound advice
Try different ROM? See which one works best.
Like me, I found that SuperAosp is best suit for me (see my sig for DEV Site and Download, if you want to try it). It had been running fast and I had no issue, what so ever. Occasionally when I loaded apps that hogged the power usage it gets lags, but still good. FCs are at minimal to none (that's just because of the way I handle the apps). Once in a while I noticed that it reboot, when I tried to use the apps that hogged the memory (maybe that was the apps issue).
Only other thing I recommed is to download a different launcher, because the build-in ADW Launcher does not work too well in my opinion.
Another thing, if you wish to keep the ROM you had. I would suggest to change the partition size. (IE: Catch [128MB]/Ext 2 or EXT 3 [1024MB]/ FAT32[the rest]) Now I know other people might say that it's overkill, but to me my G1 performance it great.
I've tried multiple roms as of late, and the one I like the most does happen to be MLIGNs... everything seems to be working correctly for the most part with the exception of what I listed above... Now on the like, 23rd reboot most of the sluggishness that was there before is gone, and everything is pretty much being cooperative, with the exception of like the weather, which isn't updating properly but I can live with that. What I cant live with is the fact that this ROM when not plugged in, will freeze up when in the lock screen, a few minutes after it has darkened and gone black and wont respond at all. Or I'll unplug it and just do a test, swipe left, right for a good minute or two, go into apps and It'll just SHUT OFF. Maybe it really is the battery? I'm unsure. When I look at the battery it does look quiet bloated... I am unsure...
I'm gonna try to set it to what you recommended, and see if that works...
I don't think it's the battery.
Have you tried reformat/partion your SD card (be sure to backup your data first). See my last comment on sizes recommendation for each partition.
Also check on the swappiness setting.
Mhm... so I went back and followed everything you told me to do, including repartitioning to the exact file sizes you told me. (Also I'm guessing Cache meant Swap) So I set everything up and its really blazing fast and stable.... until I remove the USB cord. Then it shuts off, freezes at lock screen when the screen is dimmed to black, and will just randomly shut off while doing things (especially when trying to get into messages)
Also if it helps, I have a Class 2 8Gig SD card, and my Recovery is Ra 1.5.x(I forget.) I'm completely confused... I dunno what to do... I would really like this to just work and stop being a hassle D:
Hmmm, Try reading this thread, http://forum.xda-developers.com/showthread.php?t=1010932
See if it helps.
Nothing :/ Its okay... I'm gonna go play around with other roms, completely re do my phone, make sure everything is updated etc. Then go from there.
Thank you anyways, you were a big help, reguardless of my phones triumphing retardism
Hi guys.
I was wondering if changing roms and wipe often can be dangerous for our phone. I had an Htc Diamond 2 and i used to flash it often. I thought that, with the time, the system was more slow for this reason. What do you think? is it like the damage on hard disk when we formatting a pc?
it's like pc.
i thought pentium 1 was fast too.
ROM is designed to read and write, so i dont think flashing often would shorten the life compare to normal usage.
U might change phone before your internal storage dies on u. That's how solid it is.
Yeah it's like buying a memory stick and being scared to use it incase it breaks LOL
(I'll just keep it in the box and store it away)
You get something like 100,000 write cycles on NAND, no need to worry.
Hello everyone, thanks for taking the time to read my thread. i'm really having a hard time here. I'm trying to take pictures, but it has become so unstable, and I can't reply. and it keeps saying i don't have any space in my SD. I've NEVER had this problem with my other ROM/Default.
There are 2 SDs, one is the one i bought and put it, so i can put all my music and i thought the other i would be able to have it for pics and other stuff. But I can't see it. i've taken out so much music to try and make space (like 10 folders/albums). But it's still saying it doesn't have enough space.
I'm right now rooted. used ClockworkMod then installed CM10 I believe. or CM11 and right now i'm running android (I went from a 2.3.6) to 4.1.2. on an SGH-T679 and the ROM is CyanogenMod version, Build date Apr 2, 16H EDT 2019, CyanogenMod version 10-20130402-UNOFFICIAL-Ancora_tmo. I hope that's enough info.
So I'm guessing if anyone from these forums. Has anyone been through this? Or has heard of someone else having problems. Because my #1 thing is just walking around NYC, taking pics. But when I can only walk around and like take 3 or 4 pics. i'm like :crying: all day. And i don't have the $ to just buy a camera like that.
P.S. and since yesterday, It takes longer to load the battery while charging unlike before. I thought that it was weird. But then to waste/discharge the battery.
Thank you
This may or may not solve your problem, sometimes there are hidden files that stay on your internal storage and eat up all your room. In your file manager enable hidden files, then look for things you can remove. One of hem right off the bat would be .thumbnails, I'm sure there are more but honestly you have to look around your storage, there may be old downloads or cache files that are still there. Hope this helps.
I think i flashed my ROM, data, cache, dalvik-cache and I think data was the last one. and since i've done that. I can't start my phone. It says samsung. then the samsung cyanogenmod start up screen, and it just hangs there. can anyone help me with this pls? I pressed
start button + down volume button. Then it says that it's going to download the OS for me. But i think that just hangs too cause it takes a while. and then it goes back to the start up screens that won't go anywhere.
Thanks D'vari, but unfortunately i think i'm passed that. Now i need to know just how to start my phone and get it past the phone.
You probably have conflicting data somewhere. Try power + volume up. That should get you into recovery. Then wipe everything except system and you should be able to boot up.
It took so long, because i read somewhere else to press vol down + power button. so i was trying. And It got me into Odin, and that said an OS is important, do you want to dl an OS now? so i said, well, i don't think i even have one left, so i chose yes. then it would say it was downloading for hours. but then it would boot up into the boot up screen loop. which was kind of good, but i didn't think so at the moment. Then i read how to get into cwm in my phone. so then i did it, and i had to do an advanced restore before regular restore was coming back MD5 mismatch. So It's like i flashed my old system, restored it to factory cyanogenmod factory. Tomorrow i'll flash cm10 and google apps and something else that had swipe working on this phone. maybe it was just upgrading to CM10, because now it's in version 9 and swipe is not working.
Thanks for your help
cyanogenmod issues as well
I had the same issue last week when updating to 10.1. but it did say that it may take a while to boot up. I didn't stress it. I just plugged it in by my bed and went to bed. when I woke up the next morning, I had it!
I did the volume up/power-wipe clean-reboot and then I slept. give that a try. maybe you are just like me and worrying that it is taking too long and you have F-ed up your phone!
On a different note, this 10.1 is awesome. But I can't get it to recognize my sd card. it does show that one is mounted but wont save anything and wont let me access the files. I have wiped the sd card clean and formatted to fat32. but that is doing nothing for me. any other suggestions here? I need my music and the space! this is taking so much time, it almost isn't worth the effort. but I love the cyanogenmod 10.1. but can't keep if it wont work right. ???
Deefex said:
It took so long, because i read somewhere else to press vol down + power button. so i was trying. And It got me into Odin, and that said an OS is important, do you want to dl an OS now? so i said, well, i don't think i even have one left, so i chose yes. then it would say it was downloading for hours. but then it would boot up into the boot up screen loop. which was kind of good, but i didn't think so at the moment. Then i read how to get into cwm in my phone. so then i did it, and i had to do an advanced restore before regular restore was coming back MD5 mismatch. So It's like i flashed my old system, restored it to factory cyanogenmod factory. Tomorrow i'll flash cm10 and google apps and something else that had swipe working on this phone. maybe it was just upgrading to CM10, because now it's in version 9 and swipe is not working.
Thanks for your help
Click to expand...
Click to collapse
I'm using pac 4.2 and I can switch were I want my pics stored from the camera settings maybe that ROM would help your situtation.
Thank you for all your help. But i decided to switch over to JellyBean. But i've been having some minor problems with it. I just flashed this ROM after doing something stupid in CWM (as you all know) while using cyanogen. I actually really like this ROM. I though CM10 futuristic looking. this beats that by a lot of points. I just have a problem now. The icons in the apps menu/section, are spaced too far apart. IDK what I did to cause this. Cause i was messing with those options of icons rows and colums for the desktop, but i set it back to default and that still didn't do anything to the apps section.
The other problem I'm having is with the camera. I try to open it, but it just says camera can't go on, 'wait-report-close'. That type of message. IDK what it is because the main reason for switching was to be able to take lots of pics. I love taking pics with my phone. And i found out what had my internal memory soooo clogged up. I had a .txt music cache file that was 848MB. Once I erased that, I know have 50% free space.
It looks really retarded . I know i'll fix it somehow, someday. I think there's even an upgrade now for slimbean, maybe I should try that. But right now i'm in google play store. in the 'my apps' list. and going through what i used to have, and installing my old apps, one by one. a grueling task, but I really want to use this ROM as my main rom.
I recently switched over from CM10.1 to LN14.1 and have been getting misreported battery (it worked fine previously) Specifically, it will drop 15-20% every 10 minutes or so, and stay at 1% for several hours (I've recorded up to ten hours).
What I've tried to fix the issue:
Draining to 0% and recharging to 100% (i.e. manual calibration listed on XDA) on LN14 builds
Battery Calibration Apps recommended on XDA
Flashing down to stock ROM, factory resetting, and re-flashing 14.1 (I read this could restore a battery file that has been affected by repeated flashing of ROMs.)
Flashing back down to CM10.1 and CM10.2 (also tried CM11 and CM12 builds) that I used previously
Wiping DALVIK/Cache between each install
Battery Monitoring Apps (Rooted)
Battery saving/hibernation apps
Adjusting nearly every power consumption option (screen brightness, WiFi, etc.)
The behavior has been the same switching between any ROM of CM, LN, Stock/Factory Reset from the point that I first upgraded from CM10 to LN14.
I don't think it's a lack a capacity and it has to do with misreporting.
I haven't tried recalibrating/draining on CM10 or stock, but I don't know if that would be pointless since I've attempted it three times on LN14 with no success. Also, I don't know if the process causes battery issues long-term. Right now, I'm looking to see if TWRP reports the same battery level as LN14. Last night, I was at 1% for 10 hours or so, including ~3 hours of video trying to discharge.
Anyone have any tips on where to look next? Is this just an issue with LN on HD+ in general? Thanks in advance for any help.
Probably one of your sources of information is this post: https://forum.xda-developers.com/nook-hd/help/nook-hd-battery-issue-custom-rom-fixes-t3389721
We suffered through this issue with an HD for quite awhile and tried all the stuff you mention. It may be that the return to stock/factory reset actually worked but it may also be that we discovered that somehow the SD card we were using for flashing (and which we had remade at some point) had not been properly configured as 0x0c and was instead 0x0b. This eventually led to a tablet that would only boot when plugged in and allowed to sit for a minute before being unplugged. We never got to the battery misbehaving issue at that point because of the panic that ensued over what the %#W% was going on!
Anyway.....once the card was made properly, we started from stock/factory reset (including actually re-registering the tablet with B&N, etc.) and then flashed the CM ROMs. Everything is now fine.
Whew.
nmyshkin said:
Probably one of your sources of information is this post: https://forum.xda-developers.com/nook-hd/help/nook-hd-battery-issue-custom-rom-fixes-t3389721
We suffered through this issue with an HD for quite awhile and tried all the stuff you mention. It may be that the return to stock/factory reset actually worked but it may also be that we discovered that somehow the SD card we were using for flashing (and which we had remade at some point) had not been properly configured as 0x0c and was instead 0x0b. This eventually led to a tablet that would only boot when plugged in and allowed to sit for a minute before being unplugged. We never got to the battery misbehaving issue at that point because of the panic that ensued over what the %#W% was going on!
Anyway.....once the card was made properly, we started from stock/factory reset (including actually re-registering the tablet with B&N, etc.) and then flashed the CM ROMs. Everything is now fine.
Whew.
Click to expand...
Click to collapse
I checked my SD card and the Partition ID is 0x0b. However, my tablet doesn't have the behavior you described regarding the need to be plugged in to boot.
Are you indicating that it would be worth flashing back down to 2.1.0 Stock ROM/Factory Reset with a 0x0c card, and Registering to attempt to resolve the issue? Would I be required to remain on stock for a period of time or can I re-flash to LN immediately? Thanks in advance for you help, the Partition ID type is news to me.
theleagueofstream said:
I checked my SD card and the Partition ID is 0x0b. However, my tablet doesn't have the behavior you described regarding the need to be plugged in to boot.
Are you indicating that it would be worth flashing back down to 2.1.0 Stock ROM/Factory Reset with a 0x0c card, and Registering to attempt to resolve the issue? Would I be required to remain on stock for a period of time or can I re-flash to LN immediately? Thanks in advance for you help, the Partition ID type is news to me.
Click to expand...
Click to collapse
I'm no expert so my information is anecdotal. I'd never seen the weird behavior like on the HD tablet in all my work with an old Nook Tablet. And I can't pinpoint the battery reporting issue vs. the improper remake of the card. All I know is that at some point I thought there must be something wrong somewhere and decided to make a completely new card. Then the "fun" really began.
The actual correct Partition ID type is 0x0C FAT32 LBA (as shown by Minitool Partition Wizard). This is documented in all (most?) of the instructions for preparing SD cards. I just got sloppy, I guess. It's still difficult to believe that this change made the difference but it did for me, at least in terms of boot. I do think the return to stock is a good idea. It may not be necessary to register (we already had an account from the old days of running stock), but I would do the factory reset and let it sit awhile as the OP suggested (maybe 15 min?). As he said, what's a few minutes if it will save you endless headaches? What do you have to lose?
When I (carefully) prepared my new SD card I used the files provided by @belfastraven, substituting the old version of CWM needed to reflash stock for the one he had. This gave me SD-based TWRP (two different versions) as well as the old CWM. For the life of me I can't relocate that post, but I expect other card recipes will work.
Edit: here we go: https://forum.xda-developers.com/showpost.php?p=66086179&postcount=10
nmyshkin said:
I'm no expert so my information is anecdotal. I'd never seen the weird behavior like on the HD tablet in all my work with an old Nook Tablet. And I can't pinpoint the battery reporting issue vs. the improper remake of the card. All I know is that at some point I thought there must be something wrong somewhere and decided to make a completely new card. Then the "fun" really began.
The actual correct Partition ID type is 0x0C FAT32 LBA (as shown by Minitool Partition Wizard). This is documented in all (most?) of the instructions for preparing SD cards. I just got sloppy, I guess. It's still difficult to believe that this change made the difference but it did for me, at least in terms of boot. I do think the return to stock is a good idea. It may not be necessary to register (we already had an account from the old days of running stock), but I would do the factory reset and let it sit awhile as the OP suggested (maybe 15 min?). As he said, what's a few minutes if it will save you endless headaches? What do you have to lose?
When I (carefully) prepared my new SD card I used the files provided by @belfastraven, substituting the old version of CWM needed to reflash stock for the one he had. This gave me SD-based TWRP (two different versions) as well as the old CWM. For the life of me I can't relocate that post, but I expect other card recipes will work.
Edit: here we go: https://forum.xda-developers.com/showpost.php?p=66086179&postcount=10
Click to expand...
Click to collapse
I just flashed down to stock, factory reset and reinstalled 14.1 I set the SD to 0x0C FAT32 LBA. I didn't wait 15 minutes after installing the stock though, just a few minutes (I missed this step and hopefully it doesn't make all the difference.) I'll report the results on usage.
I flashed down to stock with NookHDplus-bootable-CWM-6028-for-stock-BOOTFILES-r4-(05.15.13) posted in a CM10 thread though.
The early indication is that the issue is still the same. I think I'm fighting a losing battle and I'll have to look into replacing the battery or making a regular habit of keeping the tablet plugged in.
theleagueofstream said:
to open the device and/or replace the battery, but it doesn't seem like the device is made for it.
Click to expand...
Click to collapse
Like most Android devices, not it's not made to be opened up.
But it's doable with care. If you search you can find instructions and videos.
But, 1, I'm non convinced it's a bad battery. You get too much runtime at 1%
And 2, not sure of any good options for replacement batteries. That's why my wife's HD+ doesn't gave a new battery.
ST Dog said:
Like most Android devices, not it's not made to be opened up.
But it's doable with care. If you search you can find instructions and videos.
But, 1, I'm non convinced it's a bad battery. You get too much runtime at 1%
And 2, not sure of any good options for replacement batteries. That's why my wife's HD+ doesn't gave a new battery.
Click to expand...
Click to collapse
I'm considering opening it just for the sake of seeing if there's a bad connection, but I've seen people damaging the case, etc. I agree with your sentiment that the capacity doesn't indicate it's a bad battery. Regardless, I'm grateful for everyone's help here so far.
theleagueofstream said:
but I've seen people damaging the case, etc.
Click to expand...
Click to collapse
Some people just shouldn't work on finiky stuff. I;ve seen people screw up lots of things because they rushed.
Phones and tablets just require time and patience.
ST Dog said:
Some people just shouldn't work on finiky stuff. I;ve seen people screw up lots of things because they rushed.
Phones and tablets just require time and patience.
Click to expand...
Click to collapse
I'm assuming you've opened a few, so do you recommend a special set of tools? Or is a guitar pick and appropriate screwdriver enough?
theleagueofstream said:
I'm assuming you've opened a few, so do you recommend a special set of tools? Or is a guitar pick and appropriate screwdriver enough?
Click to expand...
Click to collapse
Not sure on these.
I've got a few plastic spludgers that have been handy with other devices.
This one makes it look easy, but the tape on the bezel is missing.
https://youtu.be/1muVOrhORq8
Also they don't even tape the replacement battery to the back so it might shift around in the case.
This is more like what you'll encounter.
https://youtu.be/HpVrds3g-M8
Note all the double sided tape. You'll want to preserve it replace it.
ST Dog said:
Not sure on these.
I've got a few plastic spludgers that have been handy with other devices.
This one makes it look easy, but the tape on the bezel is missing.
https://youtu.be/1muVOrhORq8
Also they don't even tape the replacement battery to the back so it might shift around in the case.
This is more like what you'll encounter.
https://youtu.be/HpVrds3g-M8
Note all the double sided tape. You'll want to preserve it replace it.
Click to expand...
Click to collapse
Do you have any suggestions for a replacement brand?
I found:
https://www.amazon.com/TLP-040-Li-P...d=1510605819&sr=1-4&keywords=nook+hd++battery
but I thought someone with better experience could make a suggestion.
theleagueofstream said:
Do you have any suggestions for a replacement brand?
Click to expand...
Click to collapse
As I said earlier, no. I'm not confident any of them are any good.
Someone posted a link to the one they got in the other thread.