I was wondering why does almost every rom seems to be so slow? Opening screen takes usually 10sec+, opening app lags the hell out of my phone. Seems that it lags more over time. (been rebooting this thing, doesn't help)
What i've done to this device when installed Slim Bean 6:
FULL wipe, /system etc gone
DID NOT RESTORE any backups
Changed DPI to 240
Apps that are running always:
Tasker, Hangout, Facebook messenger, Mail apps, Nova Launcher
I just don't know what to do with this.. Every rom i used has always lagged like hell after little of my usage.
Install nx kernel and tell me if it will smoothen. I also suggest using latest slim
Sent from my GT-N7000 using Tapatalk 2
If your using TW go to CM with nx kernel
Sent from my GT-I9200 using xda app-developers app
noteandfound said:
Install nx kernel and tell me if it will smoothen. I also suggest using latest slim
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Have been using NX kernel from when it first came out, and i don't think slim version do anything, cause this is also happening on every other rom I used (TW and AOSP) =/
Running out of ideas, i have tried everything i can to help this issue, been over year for now and nothing that is suggested helps =(
Racle90 said:
Have been using NX kernel from when it first came out, and i don't think slim version do anything, cause this is also happening on every other rom I used (TW and AOSP) =/
Running out of ideas, i have tried everything i can to help this issue, been over year for now and nothing that is suggested helps =(
Click to expand...
Click to collapse
Is your device emmc recovered?
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Is your device emmc recovered?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Got no idea what that means, so i'm going with no.
Racle90 said:
Got no idea what that means, so i'm going with no.
Click to expand...
Click to collapse
There is a new feature in android 4.3 called TRIM support, which has been around since windows 7. It's a feature for solid state drives that enhances the way the os reads deleted or old data. Without trim, drive performance lessens over time.
http://en.m.wikipedia.org/wiki/TRIM
So on our notes, every rom will get slower as the os continues to access data that's already been deleted because it doesn't realise it doesn't have to anymore.
So if a 4.3 rom gets released for the note, grab it!
Sent from my GT-N7000 using xda premium
SpyderTracks said:
There is a new feature in android 4.3 called TRIM support, which has been around since windows 7. It's a feature for solid state drives that enhances the way the os reads deleted or old data. Without trim, drive performance lessens over time.
http://en.m.wikipedia.org/wiki/TRIM
So on our notes, every rom will get slower as the os continues to access data that's already been deleted because it doesn't realise it doesn't have to anymore.
So if a 4.3 rom gets released for the note, grab it!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Current androbench result, I don't see that these are so bad tbh https://www.dropbox.com/s/d2k18210adf5de7/2013-08-06 08.55.31.png
And lagfix, which does TRIM also, has this warning:
AuxLV said:
here are some devices affected by BrickBug. Samsung Galaxy S2 and Samsung Galaxy Note are known to have it. There are also reports that some Acer A210/A211 and LG O2x are affected too. There is a Got Brickbug? app to test your device, but it is only intended for Samsung users. BrickBug means DEATH of your device if you try LagFix! There are some unlucky guys already. In case of brickbug - use warranty and exchange your device. This is a hardware fault and manufacturer is responsible.
Click to expand...
Click to collapse
Racle90 said:
Current androbench result, I don't see that these are so bad tbh https://www.dropbox.com/s/d2k18210adf5de7/2013-08-06 08.55.31.png
And lagfix, which does TRIM also, has this warning:
Click to expand...
Click to collapse
The brickbug is what I was asking about previously, it's a fault in a lot of samsung handsets with the emmc chip being corrupted.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
The brickbug is what I was asking about previously, it's a fault in a lot of samsung handsets with the emmc chip being corrupted.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
My chipset is *know* to have brickbug, but got no way to really comfirm that.
I also feel that I'm facing slowness and laggyness on my note.it is running cm10.1. If we can't use trim support on cm10.2 and if we also can't use lagfix application, then what can help us regain the emmc speed back to original? Some kind of firmware or flash file that will write 0 everywhere? (I know this is not a good idea for life of the emmc).
fastguy said:
I also feel that I'm facing slowness and laggyness on my note.it is running cm10.1. If we can't use trim support on cm10.2 and if we also can't use lagfix application, then what can help us regain the emmc speed back to original? Some kind of firmware or flash file that will write 0 everywhere? (I know this is not a good idea for life of the emmc).
Click to expand...
Click to collapse
You don't need trim or other tools to gain back the device performance. Trim and LAgfix and such are only usefull when you want to keep the partition data.
If you don't care about the data, a format of the partition is usually enough.
daedric said:
You don't need trim or other tools to gain back the device performance. Trim and LAgfix and such are only usefull when you want to keep the partition data.
If you don't care about the data, a format of the partition is usually enough.
Click to expand...
Click to collapse
Thanks Daedric, but doesn't format only reset & write the filesystem data structures but do not actually touch each cell in the eMMC. Therefore, the data on those eMMC cells remain as is and when it's time to write to them, don't the eMMC spend time to erase first & then re-write?
I mean, why does a secure erase or writing 0's everywhere speed up then? Is it placebo?
fastguy said:
Thanks Daedric, but doesn't format only reset & write the filesystem data structures but do not actually touch each cell in the eMMC. Therefore, the data on those eMMC cells remain as is and when it's time to write to them, don't the eMMC spend time to erase first & then re-write?
I mean, why does a secure erase or writing 0's everywhere speed up then? Is it placebo?
Click to expand...
Click to collapse
OK, regarding eMMC and SDD in general i'm not the most wise. When i refered format, i refered unconditional format, and not quick format. (read format.com /U vs format.com /Q)
Regarding the secure erase, it's not placebo. Benchmarks prove it, not just "i feel it faster".
Now, when it comes to the note, i believe only a few partitions are mounted ReadWrite, that will be /data and /cache, don't know about /preload. So, a recovery script that does dd if=/dev/zero of=/dev/mmcblk_where_data_is should clean the partitions.
Yet, i don't know if it will have any effect when running a secure kernel, where secure erase has been disabled.
daedric said:
OK, regarding eMMC and SDD in general i'm not the most wise. When i refered format, i refered unconditional format, and not quick format. (read format.com /U vs format.com /Q)
Regarding the secure erase, it's not placebo. Benchmarks prove it, not just "i feel it faster".
Now, when it comes to the note, i believe only a few partitions are mounted ReadWrite, that will be /data and /cache, don't know about /preload. So, a recovery script that does dd if=/dev/zero of=/dev/mmcblk_where_data_is should clean the partitions.
Yes, i don't know if it will have any effect when running a secure kernel, where secure erase has been disabled.
Click to expand...
Click to collapse
Hmm, I thought secure_erase works by applying a special command that sends some special voltage to the cells which wipe everything out there. But writing 0's everywhere may not actually be a secure_erase, but I do not know in detail unfortunately.
Related
I recently had to Run the repartition un-superbrick guide, Where I had to change the Start and end Point of the UMS partition.
After a long battle, I Managed to get a rom Running (Stock ics German open lpy).
The effects of the restoration Process were as follows:
Random Freezes, which require Force reboot. seems to be prone to them right After boot.
The Freeze occurs also when installing any App from play Store. However, I Was able to install SwiftKey 3 via apk.
The Internal sdcard is only 8gb on size, Where it used to be 11.
Any Ideas what to do?
Bump.. No one has any Ideas? :/
+1 same here would love to know as well. Only mine freezes after some multitasking not exactly like yours.
Sent from my GT-N7000 using xda premium
Same issue here. My UMS is 4 Gb. I think is problem of data partition but i restored it about 10 times. I'm running G&B ICS rom
Try to ODIN back to stock Gingerbread, root, and flash a safe CM9 rom.
Edit:
Or stay on Gingerbread. See if you still have freezes.
After restoring from brick, i installed GB stock from my operator and still freezing ramdomly, once was cuz i did multitasking, another one cuz i installed apps from market.... Cyanogen the same, i'm thinking that another partition is bad, but cache is good:
Here my modified values:
mkpartfs primary ext2 5000 6100
mkpartfs primary ext2 9000 11000
mkpartfs primary fat32 11500 15200
name 9 FACTORYFS
name 10 DATAFS
name 11 UMS
Hello
Did you find a solution I got the same problem but I don't know what I can do to solve it
I have the same problem. Anyone can solve it?
im experiencing the same situation, perhaps any solution/findings?]
Install cm based rom from gb, they use around 100mb space instead of 600mb. The issue here is that you're maxing out your reduced partitions so stock roms will struggle.
Sent from my GT-N7000 using xda premium
Changing rom is a good idea.
Another idea is to use tool under adb to check partitions. Use e2fsck with -c option to scan the partitions 7, 9, 10 to see if it find bad blocks and sometimes can fix them. If it reports no bad blocks find, that means those partitions are ok. Some time it find bad blocks and could fix or mark them, then we do not need to do re-partition again. (it will tell kernel to avoid those faulty blocks). If e2fsck freezes then there are serious fault it cannot fix and will requires more re-partition. It also no harm to check partition 11 as well, using dd/parted tool. Hope it may help. cheers.
I'm on latest CM9 with Semaphore 1.2.4, but this latest update used up a lot of space in /system partition which only left me 2MB spaces. I need extra spaces for system app and new bootanimation, how?
You cant change the system partition size however to get the space in it try moving your app to sdcard.
-----Sent using RemICS-i9000-----
Even I need help with it..
Sent from my GT-I9000 using Tapatalk 2
erpurohit said:
You cant change the system partition size however to get the space in it try moving your app to sdcard.
Click to expand...
Click to collapse
How sure are you on that? From what I understand PIT files in ODIN can change partition layout. If one can change partition layout, one should be able to increase /system as well.
That said, I find Android very confusing. Some examples:
Onboard flash is not a SD card. A SD card is something you can just pull out of the device. Yet android refers to the onboard flash - or well, more accurately a specific partition on the onboard flash - as SD card.
CWM backup is supposed to do a *FULL* backup. Yet it does not include my pictures. No matter what format/wipe options I choose in CWM, the pictures don't go away... I have a whole different concept off a full wipe / factory reset / format SD than that.
It seems several tools format the wrong thing.
App data directories seem to move all over the place. I usually make nandroid backups and I have issues restoring my app *data* every time I use another ROM.
All that said, I'm a big time linux user. I'm extremely familiar with system maintenance on computers. However Android is new to me. All the confusing on naming etc. however is a HUGE !#@%!!#% obstacle.
But why explain things clearly or use terms what they're for. Much easier to confuse people right? At least someone can make money of it then.
Get slimbean 2.1
It has 1.9 gb of /system!!
Sent from my Rolls-Royce.
jay_ingale said:
Get slimbean 2.1
It has 1.9 gb of /system!!
Sent from my Rolls-Royce.
Click to expand...
Click to collapse
All new version of jelly bean will be of this size only....
Delete /system/media/videos and convert cyanogenmod wallapapers to user apps. Saves ~15 mb
Sent from my GT-I9000 using xda premium
Sorry to bump such old thread.
I was offered a I9000 that I would like to use as second phone.
I flashed I9000XXJVU_I9000OXAJVU_OXA through odin, and then root (cf-root) and MackayRom 1.7 .
As it says in the rom thread, I have a space problem. Is there any chance better than this one?
Any possibility of repartitioning the internal storage?
Here is my partition scheme:
SUPERWIPE SCRIPT
Alright.. Here is a SUPERWIPE script for our Nexus 4
standard disclaimer here... i aint responsible if your phone catches fire, etc, etc
I'm not getting into the debate on their usefullness, whatever.. I like them and some others do so yeah :good:
Will not play nice with twrp it will not wipe your data partition at all or reboot back to recovery due to the way twrp handles their stuff I am currently working on a fix for this
Version 1
Wipes & Formats
- cache, system,
Wipes
- data (NOT SDCARD)
Wipes
- various system files found on sdcard
Checks
- system for errors
MD5 SUm : 7C95D25876C9D387139384639F77CB04 *LG Nexus 4 - SuperWipe v1.zip
How to Use
- Backup Original ROM
- Flash LG Nexus 4 Superwipe v?.zip
- FLASH OR RESTORE A ROM
- Continue as normal
TESTED working before a restore and new rom flash by myself multiple times
Original superwipe created by mike1986
cherry picked data wipe without wiping sdcard from Jst_In_Time
Used the partition information from mskip to ensure the correct locations were being wiped
I am not sure if this is the correct forum to be in and I read the thread sticky before posting
can anyone report their use? no problems thus far?
joshndroid said:
can anyone report their use? no problems thus far?
Click to expand...
Click to collapse
I would, but I haven't got anything new to flash yet
I will be sure to tell you when I do though, I always like having these scripts on hand, thankyou.
No no no no. Please don't use superwipe scripts. They are known to be problematic and don't do anything that your recovery doesn't do.
Thanks for the effort OP, but I strongly advise NOT to use it. I've troubleshooted Sensation and some other HTC phones for over a year with other guys, and we all agree that superwipe scripts are a no no.
undercover said:
No no no no. Please don't use superwipe scripts. They are known to be problematic and don't do anything that your recovery doesn't do.
Thanks for the effort OP, but I strongly advise NOT to use it. I've troubleshooted Sensation and some other HTC phones for over a year with other guys, and we all agree that superwipe scripts are a no no.
Click to expand...
Click to collapse
Used them every ROM flash with 3 sensations and a desire and my galaxy nexus when they were available.. Setup correctly with partition table information they yes will do what a recovery does and save time and remove unnecessary system files on sdcard before a ROM flash... Your problem lies when you try to use a super wipe on a device to which it isn't ported for as dev blocks change for partitions (so u end up wiping a radio partition instead of a system for example) and locations of sdcard etc change... I've used it probably 20-30 times already myself in testing (as i tested the mouting points etc before the last testing phase was the format of the partition.. And read each log until I was happy with the result)
Sent from my Nexus 4 using Tapatalk 2
Wipes
- data (NOT SDCARD)
Wipes
- various system files found on sdcard
Not sure what you mean, There is no sd card on the N4.
Internal sdcard
mounts as /sdcard/0/
By the recovery when you flash a file from the phone
Therefore is a "sdcard" for simplicity purposes
Sent from my Nexus 4 using Tapatalk 2
joshndroid said:
Used them every ROM flash with 3 sensations and a desire and my galaxy nexus when they were available.. Setup correctly with partition table information they yes will do what a recovery does and save time and remove unnecessary system files on sdcard before a ROM flash... Your problem lies when you try to use a super wipe on a device to which it isn't ported for as dev blocks change for partitions (so u end up wiping a radio partition instead of a system for example) and locations of sdcard etc change... I've used it probably 20-30 times already myself in testing (as i tested the mouting points etc before the last testing phase was the format of the partition.. And read each log until I was happy with the result)
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Oh, no doubt it works as intended. But I've seen too many people use wrong superwipe, and you know consequences of that. I think it's best to stick to recovery.
Sent from my Nexus 4 using Tapatalk 2
undercover said:
Oh, no doubt it works as intended. But I've seen too many people use wrong superwipe, and you know consequences of that. I think it's best to stick to recovery.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately that is therefore due to not reading how a script, etc works and is user error.. Not due to a dev/contributor... Not having a dig at you by the way... Script works a charm none the less
Sent from my Nexus 4 using Tapatalk 2
joshndroid said:
Unfortunately that is therefore due to not reading how a script, etc works and is user error.. Not due to a dev/contributor... Not having a dig at you by the way... Script works a charm none the less
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Indeed. User error. Users nowadays don't read, and it IS their fault if they brick their phone, but i prefer to have a little safeguard like for the kids on the stairs
I somehow ended up troubleshooting problems in Senny forums, along with ganeshp, malybru, kgs and many others, so my mentality has swerved a bit towards prevention of problems rather than fixing the problem after they done the deed.
I understand that you are not having a dig, i think we are having quite a constructive conversation here. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
I used a SuperWipe script and a Super Cache Wipe script made by the developer (thederekjay) when I had my T989 Samsung Galaxy S 2.
Back in those days the scripts were necessary because (for that particular device at least) the earlier versions of CWM did not wipe the partitions thoroughly/properly and people would have issues when flashing ROMs.
The scripts were fantastic and a go to for almost everyone in the forum. However, they were only necessary for the earlier versions of CWM, it was not necessary on TWRP or when CWM was updated.
I guess my question is, does it matter if we are using CWM or TWRP with your script? Can it be used on either recovery?
Either recovery is fine... Mostly this script will negate some time, provide an output of the results of the script, check for system filesystem errors and delete common files that are located on the internal sdcard from some system apps... Yes some things can be done via the recovery however some thing's cant and a lot of people don't wipe system.. Therefore this is an all over that will erase and format basically all relevant partitions and files relating to a ROM =]
Sent from my Nexus 4 using Tapatalk 2
joshndroid said:
Either recovery is fine... Mostly this script will negate some time, provide an output of the results of the script, check for system filesystem errors and delete common files that are located on the internal sdcard from some system apps... Yes some things can be done via the recovery however some thing's cant and a lot of people don't wipe system.. Therefore this is an all over that will erase and format basically all relevant partitions and files relating to a ROM =]
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Will be using this for sure, thank you very much for this, will save time and make sure my system is wiped clean as a whistle before flashing. Peace
Sent from my Nexus 4 using xda app-developers app
I've just added this script to the Nexus 4 Complete Index
Sent from my Nexus 7 using xda premium
As I mentioned already in other posts, I just got back into the Android scene so bear with me. I, too have been using super wipe scripts back in the Evo days (yes the OG Evo . I was actually looking for a script like this only because when I use the CWM data/factory reset, it wipes data and cache but I can still boot up into a fresh version of the ROM. Call me paranoid or OG when I want to wipe, I want to complete wipe everything so that unless I flash a rom, the phone won't boot up to anything other than fastboot and recovery. With that being said, would this script do just that?
Also, is it really necessary for me to wipe everything or does the CWM "wipe data/factory reset" good enough? I just worry that it doesn't wipe everything and leaves unnecessary files. Even though I have the 16gb N4, it's still very little space so I'd like to ensure I'm not being jacked out of space from all those unnecessary orphan files...
I'm really glad to see this. Scripts like this help a lot of people know they've wiped all the right things when they flash a new ROM. Thanks for putting this together.
KidCarter93 said:
I've just added this script to the Nexus 4 Complete Index
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks mate :good:
gqukyo said:
As I mentioned already in other posts, I just got back into the Android scene so bear with me. I, too have been using super wipe scripts back in the Evo days (yes the OG Evo . I was actually looking for a script like this only because when I use the CWM data/factory reset, it wipes data and cache but I can still boot up into a fresh version of the ROM. Call me paranoid or OG when I want to wipe, I want to complete wipe everything so that unless I flash a rom, the phone won't boot up to anything other than fastboot and recovery. With that being said, would this script do just that?
Also, is it really necessary for me to wipe everything or does the CWM "wipe data/factory reset" good enough? I just worry that it doesn't wipe everything and leaves unnecessary files. Even though I have the 16gb N4, it's still very little space so I'd like to ensure I'm not being jacked out of space from all those unnecessary orphan files...
Click to expand...
Click to collapse
1. Basically.. what will occur is that the script will "factory reset/wipe data" your device as a recovery would do.. AND it will not wipe your "internal sdcard" if it was set to just wipe the entire partition you may infact lose data, which is what I didn't want for obvious reasons.
2. Alot of people do not wipe their system partition at all, as you can see most people state to "factory reset/wipe data" which is an entirely different partition. Yes some people say that the entire system is wiped before a rom is flashed but looking through ROM updater scripts during the course of making the superwipe script for our device I noticed some had system parition format lines in there before the rom is flashed. This superwipe script will wipe/format the system partition regardless of what the rom zip may contain
3. This script also deletes some files located on the internal sdcard that can be left behind if conducting a "full wipe/factory reset" as previously stated as this script (as with recoveries) do not wipe this partition because that would be a pain in the butt to reload all your sdcard contents back on
so basically its up to you whether you wish to use a script to conduct more than most people usually do with just their recovery, if you feel that is what you would like to conduct in the course of flashing a rom
So I ran the script and then flashed a different ROM but when it booted up, I still had my apps....normal?? And like basically most features settings too..
.....I'm scared.... Hah
Sent from my Google Nexus 4
Simer03 said:
So I ran the script and then flashed a different ROM but when it booted up, I still had my apps....normal?? And like basically most features settings too..
.....I'm scared.... Hah
Sent from my Google Nexus 4
Click to expand...
Click to collapse
I'll take a look but hasn't occurred to me
actually send me a copy of your superwipe.log that is placed on your sdcard please
-------------------------------------------------------------------------------------------------------------------
EDIT:
1. flashed back to stock.. then ran the script...
2. flashed to AOKP downloaded a couple apps that are located in /data (like titanium backup and the like).. then ran the script
3. flashed to euroskank.. did the same as above
4. flashed back to my aokp rom
checked the superwipe logs and compared... all the same AND the apps that were downloaded into the data partition had been removed as I had no user apps each time
Sent from my Nexus 4 using Tapatalk 2
Simer03 said:
So I ran the script and then flashed a different ROM but when it booted up, I still had my apps....normal?? And like basically most features settings too..
.....I'm scared.... Hah
Sent from my Google Nexus 4
Click to expand...
Click to collapse
i was also using version one and it did not work. i dont think it wiped anything
i know it didnt wipe system and data because i had everything still installed.
on twrp latest
went from pa to cm all apps remained
had to manually wipe one by one
Hoping that someone might be able to give me some insight and/or direction.
I've been running CM 10.2 off EMMC for a while now. I started having some issues with slowness and I was interested in CM 11, so I put CM 11 on an SD card so I could dual boot. CM 11 ran well. CM continued to run worse and worse. Bluetooth would timeout, web browser was extremely slow...it was pretty unbearable.
CM 11 ran like a dream so I decided to put CM 11 on EMMC. After I did so, it ran just like 10.2 did. It took 10 - 20 minutes just to get through setup. Gmail would timeout (and reboot) when it tried to sign-in. Apps wouldn't load. I would click on buttons and it would take 1 -2 minutes for the the NOOK to respond.
When I put CM 11 on, I did a factory reset (a couple of times).
So, I decided to put stock back in...without CWM...pure stock. Well, it is still slow. Booting from SD card runs fine.
Any ideas what could be wrong? I'm running pure stock now, so I could take it to B&N, but I don't remember when I purchased it. I'm not sure they would do anything.
I appreciate any suggestions. Thanks!
Yes, you are suffering from LAG and need to run TRIM to fix it. But be careful as these devices with certain internal chips can be bricked running TRIM.
See this thread:
http://forum.xda-developers.com/showthread.php?t=2528009
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Yes, you are suffering from LAG and need to run TRIM to fix it. But be careful as these devices with certain internal chips can be bricked running TRIM.
See this thread:
http://forum.xda-developers.com/showthread.php?t=2528009
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
In the updated 01/18 CM 10.2, Verygreen re-enabled Trim. So can I install that update if my device has the faulty chip? Thank in advanced for your answer
leapinlar said:
Yes, you are suffering from LAG and need to run TRIM to fix it. But be careful as these devices with certain internal chips can be bricked running TRIM.
See this thread:
http://forum.xda-developers.com/showthread.php?t=2528009
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks. I was running CM 10.2 with the trim-enabled kernel. Also, I had completely wiped /data and all the caches.
I noticed in settings (which took forever to load) it said I had used about 10 gigs or so...which I thought shouldn't be the case if I had formated /data and did a factory reset from CWM. I did a hard reset with factory restore and now things are moving along well.
Do you still think it was the LAG issue? I thought that formatting /data and /cache would fix the LAG (also I thought running the trim-Kernel would fix it too. Perhaps TRIM didn't have a chance to run because I've been dual booting? Although the reason I went to the dual boot was because of the slow issue.
I don't know...perhaps I reflashed a 10.2 ROM and forgot to flash the Kernel, but I've been on the same 10.2 rom for a while.
Either way...things seem to be working now...but now I have to start from scratch to get CM 11 on EMMC.
Thanks for the response!
bebubanche said:
In the updated 01/18 CM 10.2, Verygreen re-enabled Trim. So can I install that update if my device has the faulty chip? Thank in advanced for your answer
Click to expand...
Click to collapse
There's a thread over in Android Development that discusses the TRIM related issues. It seems the only chip effective is rev. 5 (if I remember). I believe I have the rev. 6 and have been running the trim enabled kernel since last October or November. Sorry my memory is so faulty. If you need me to, I'll find my chip again (have to wade through the very long 10.2 thread to see what the command is since I've forgotten).
Some people say it is safe to do. I have tried it myself with no issues. You have to ask yourself if your device gets bricked can you afford to replace it? If no don't do it.
dmullens said:
I noticed in settings (which took forever to load) it said I had used about 10 gigs or so...which I thought shouldn't be the case if I had formated /data and did a factory reset from CWM. I did a hard reset with factory restore and now things are moving along well.
Click to expand...
Click to collapse
Your issue was you did not really FORMAT /data with those CWM commands. Because the HD/HD+ uses an emulated internal sdcard (/data/media), it only ERASES part of /data keeping the media files intact. So all of your earlier media files remained even after CWM /data format and factory reset commands. The only way to really format /data is to go to mounts and storage in CWM and format 'data and datamedia'. Then it really FORMATS all of /data (including your media files in /data/media) and gets rid of lag. Of course your hard reset and factory restore did that too.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Your issue was you did not really FORMAT /data with those CWM commands. Because the HD/HD+ uses an emulated internal sdcard (/data/media), it only ERASES part of /data keeping the media files intact. So all of your earlier media files remained even after CWM /data format and factory reset commands. The only way to really format /data is to go to mounts and storage in CWM and format 'data and datamedia'. Then it really FORMATS all of /data (including your media files in /data/media) and gets rid of lag. Of course your hard reset and factory restore did that too.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Okay. That makes sense, although I wasn't aware of that behavior. Guess running TRIM manually would have fixed my issue. It took a while, but I have CM 11 running now. Thanks for all your work on that. It seems much faster than 10.2.
Hi all,
I've been running a Cyanogenmod nightly version since december. version 10.2.20131222.
My HD+ has the bad memory issue. What would you guys reckon I should upgrade to. Its starting to run slow and a factory reset seems to be a temporary fix.
I havent replaced the boot rom.
Cheers
smurfster said:
I havent replaced the boot rom.
Click to expand...
Click to collapse
What does that last statement mean? Are you saying you still have stock on internal memory and you are running CM from SD?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
What does that last statement mean? Are you saying you still have stock on internal memory and you are running CM from SD?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I haven't installed a recovery e.g. cwm.
Cheers
So what you are saying is you are running an early version of CM10.2 that does not have TRIM activated and you have started to get lag. You have the bad memory chip and are worried to run something newer with TRIM activated. So now you want advice about what is safe to run. You also still have stock recovery installed. Is this a correct interpretation?
I don't know the best answer for that. The stable CM10.2.1 is supposed to be safe, but I have no proof of that. I know a lot of users have reported bricked devices with CM11, with no explainable reason why. I suspect TRIM with the bad chip.
It is a tough question. Maybe someone else has some comments.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
So what you are saying is you are running an early version of CM10.2 that does not have TRIM activated and you have started to get lag. You have the bad memory chip and are worried to run something newer with TRIM activated. So now you want advice about what is safe to run. You also still have stock recovery installed. Is this a correct interpretation?
I don't know the best answer for that. The stable CM10.2.1 is supposed to be safe, but I have no proof of that. I know a lot of users have reported bricked devices with CM11, with no explainable reason why. I suspect TRIM with the bad chip.
It is a tough question. Maybe someone else has some comments.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Exactly what I meant to say. Thanks for explaining it better leapinlar
I just had another thought. You say you do a factory reset and it helps temporarily. You might try going to mounts and storage in CWM and format 'data and datamedia'. That is a real format of /data. The factory reset and format /data does not really format /data. It erases the contents of /data except the /data/media folder where your emulated internal sdcard is. So it is an erase function rather than a format. Also some of your lag may be due to your media files. A clean real format of /data may help. Also format /cache, that is where your system dalvik cache files are stored and if you're are not factory reseting, you should do the cache separately.
Sent from my BN NookHD+ using XDA Premium HD app