I have an International version of GNote and it does not have an Insane chip i.e. it does not have Brick Bug according to 2 apps (screenshot attached).
So my question is that can I use TRIM to cope up with storage fragmentation or not, as my device has started hanging alot lately and whenever I am over using it, lockscreen gets crashed and I have to reboot the device. It mostly happens playing Real Racing 3 or Dead Trigger 2.
If not, is there any alternative, for defragmentation or to correct this issue.
I am using CM11 KitKat stock Kernel no mod.
Sent from my GT-N7000 using XDA Premium 4 mobile app
You should be able to get past it if you change your build.prop so that you have say... a nexus 4
http://forum.xda-developers.com/showthread.php?t=1948558
EDIT: Also our kernel has this thing disabled by default so you will have to compile your own kernel and change a flag.
EDIT2: Here's the flag you have to disable/enable: MMC_CAP_ERASE
Note: I DO NOT TAKE RESPONSIBILITY FOR ANY DAMAGE THAT MAY HAPPEN.
XxPixX said:
You should be able to get past it if you change your build.prop so that you have say... a nexus 4
http://forum.xda-developers.com/showthread.php?t=1948558
EDIT: Also our kernel has this thing disabled by default so you will have to compile your own kernel and change a flag.
EDIT2: Here's the flag you have to disable/enable: MMC_CAP_ERASE
Note: I DO NOT TAKE RESPONSIBILITY FOR ANY DAMAGE THAT MAY HAPPEN.
Click to expand...
Click to collapse
Yah thanks, but I am more concerned about the issues related to LagFix with incompatible devices, as I have read somewhere that if the wrong formatting/fragmentation/whatever it is, is used then it can make the memory permanently unreadable/corrupt.
There's no issue in running the app on my device, I just wanna know that is my device compatible with TRIM or not, and also the potential issues related to it.
Sent from my GT-N7000 using XDA Premium 4 mobile app
yes, you can trim the n7000...
http://forum.xda-developers.com/gal...kernel-trim-speed-cyanogenmod-galaxy-t2875730
Related
I upgraded from stock froyo to oc 2.0.0 gold.
Then I noticed some lags.
the worst were in the gallery app which had about one fps while thumbnails were loading and in maps when zooming in to a level where buildings are displayed and then I then scrolled. This totaly stalled the device for more than 10 seconds sometimes.
Then I disabled lagfix in recovery and now it feels like in froyo again, both maps and gallery (i have about 800 photos on the device so itcan be easyly reproduced.
I wanted to post it in the oc thread in dev section, but I do not have permissions to do so.
Any ideas?
Sent from my GT-P1000 using XDA App
any ideas of what if you already found the solution ? ... they have to work on it little bit more give them time , they will release an update so wait
For me my problems are solved, but isnt this the purpose of this forum to tell others?
I know that there were reports of lags but I dont remember someone pointing at lagfix to cause the lag.
Sorry if this was already known.
Sent from my GT-P1000 using XDA App
Your gallery will lag after a new rom, as it needs to build a cache first.
If you followed the instructions perfectly when flashing overcome you shouldnt have any lag
I followed the instructions 100%. Really pedantic.
After killing and restarting the gallary app the lag was back evrry time, rebooting didnt help either. It didnt seem to be a cache issue.
After disabling lagfix galary was fast right from the start.
also all other lags I noticed vanished.
I can turn lagfix back on and see what happens, my guess is that lags will come back.
Sent from my GT-P1000 using XDA App
areshinakya said:
I followed the instructions 100%. Really pedantic.
After killing and restarting the gallary app the lag was back evrry time, rebooting didnt help either. It didnt seem to be a cache issue.
After disabling lagfix galary was fast right from the start.
also all other lags I noticed vanished.
I can turn lagfix back on and see what happens, my guess is that lags will come back.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
The lagfix could be borking with the included tweaks, but you dont need the lagfix anyway
Yep, lagfix is a stupid name for a filesystem conversion anyway.
I admit I did not know what lagfix was until I tried to disable it, heard the robot voice and then checking via adb shell for mounted filesystems.
I have no problem with rfs and will stick to it for now.
Sent from my GT-P1000 using XDA App
areshinakya said:
Yep, lagfix is a stupid name for a filesystem conversion anyway.
I admit I did not know what lagfix was until I tried to disable it, heard the robot voice and then checking via adb shell for mounted filesystems.
I have no problem with rfs and will stick to it for now.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
if you want ext4 see here
http://forum.xda-developers.com/showthread.php?t=943669
Use that kernel, and see the instructions in converting, i'm currently using the kernel, so far so good.
natious said:
if you want ext4 see here
http://forum.xda-developers.com/showthread.php?t=943669
Use that kernel, and see the instructions in converting, i'm currently using the kernel, so far so good.
Click to expand...
Click to collapse
are you using this kernel with overcome gold ? i really need to know the benefit cuz overcome also got the same kernel or am wrong ? thanks in advance
ok I converted back to ext4, tested and converted to rfs once more.
with ext4 gallery lags like hell, with rfs it is okay.
Strange..
Sent from my GT-P1000 using XDA App
With overcome 2.0.1 the problem I described in this thread is gone
Sent from my GT-P1000 using XDA App
Once i tried a new ics firmware. And because of that my note got bricked(i guess you all know that issue)
I revived Note with emmc. Pit file for bricked phones but after that day my note had some really serious issues like freezing on screen,not booting up some times.
I guess i have bad blocks(stops while scaning on partition scanner).
I dont know how to fix this.
I am sick of restarting Note again and again
Any help???
Sent from my GT-N7000 using XDA Premium HD app
waheed wattoo said:
Once i tried a new ics firmware. And because of that my note got bricked(i guess you all know that issue)
I revived Note with emmc. Pit file for bricked phones but after that day my note had some really serious issues like freezing on screen,not booting up some times.
I guess i have bad blocks(stops while scaning on partition scanner).
I dont know how to fix this.
I am sick of restarting Note again and again
Any help???
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Try flashing stock GB firmware for your region and then full wipe including internal and external SD card (after backup though), if that too doesn't help and if you are covered under warranty then send it to service center.
I said stock firmware for your region as that can help you in claiming warranty.
No warrenty
Any other way worth considring???
Sent from my GT-N7000 using XDA Premium HD app
waheed wattoo said:
No warrenty
Any other way worth considring???
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
above method still applicable and worth a try
Ok i will give it a short......thankyou
Sent from my GT-N7000 using XDA Premium HD app
waheed wattoo said:
No warrenty
Any other way worth considring???
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
I don't know if jtag fix the kind of brick you have, but maybe worth to check out: http://www.youtube.com/watch?v=d0SX3iDuIZc&feature=youtube_gdata_player
Sent from my GT-N7000 using xda premium
waheed wattoo said:
Once i tried a new ics firmware. And because of that my note got bricked(i guess you all know that issue)
I revived Note with emmc. Pit file for bricked phones but after that day my note had some really serious issues like freezing on screen,not booting up some times.
I guess i have bad blocks(stops while scaning on partition scanner).
I dont know how to fix this.
I am sick of restarting Note again and again
Any help???
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Hi, I had the exact situation like you. You able to work it out ?
If you've repartition the emmc chip there will be damaged sections. Often this means that stock roms will not function very well any more as they utilise a lot of the damaged partitions. One way around is to flash a deodexed or cm based ROM as they take up a hell of a lot less space on the damaged partitions.
If you aren't able to claim warranty, then this is a workaround and effective, if you do have warranty, flash stock gb and claim it.
Sent from my GT-N7000 using xda premium
I want to send it to service center, should I make it at the bricked stage and say I just wipe on stock ICS without knowing anything ? or send it at stock gb ??
ZatanRoy said:
I want to send it to service center, should I make it at the bricked stage and say I just wipe on stock ICS without knowing anything ? or send it at stock gb ??
Click to expand...
Click to collapse
If you had previously bricked your phone and got it revived now,and thinking of sending it to SSC,then its better to be on ics and make sure you clear your flash counter
So, there's another update releasing soon which has S Cloud, Touchwiz 5 and offer Note 2/S3 features on our original Notes. But, is is brick-bug free?
No it isn't. And its always advisable not to wipe data on the stock ICS kernels.
Sent from my GT-N7000 using xda premium
ral7 said:
No it isn't. And its always advisable not to wipe data on the stock ICS kernels.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
What are the actual risks? Is it really high because I have updated ICS like two or three times now with no problems?
Brad387 said:
What are the actual risks? Is it really high because I have updated ICS like two or three times now with no problems?
Click to expand...
Click to collapse
Actual risk varies from user to user but here is something [might have already seen ]
Damage is not guaranteed - it may only affect a small percentage of users, but even a 5% chance is far more dangerous than the effectively 0% chance of hardbricking due to kernel bugs in safe kernels.
Not all users hardbrick - some wind up with /system, /data, or another partition becoming unwriteable, which leads to an effectively useless phone even though they are able to flash kernels in Odin.
Click to expand...
Click to collapse
It's pure Russian roulette. You have to meet four or so criteria for the bug to be triggered but there's no way to limit or know which criteria are being activated with each wipe, so you just never know. You could have 100 lucky wipes and then trigger or you could trigger immediately.
Safest option, stick to safe kernels or don't do any wipes at all under stock ics kernels.
Sent from my GT-N7000 using xda app-developers app
emmc brick bug
The brick bug depends on emmc chip and kernel. U can test with 'eMMC check' app on play store
dont risk it..
and the brick bug will never be fixed. Samsung said they will simply not trigger it, someday... dirty workaround issue...
their recall is worse thenvToyota
Sent from my GT-N7000 using Tapatalk 2
Since I'm using firekernel I have weird problems with touchscreen. It happens randomly by itself - the bottom left area of the touchscreen is being tapped as I tap different areas. I don't OC. I wouldn't like to change my current rom (nitrogen rom) because it's really awesome, but it's annoying like hell to erase mistyped letters almost every time. It happened in different roms too, with the same kernel.
If it's necessary I can change the kernel but it would be good if it has kernel memory mod path by psn available.
Are you guys facing the same problem? Are there any patches to fix it? Or maybe you can prefer other kernel which would work with nitrogen/the ultimate rom and psn patch?
Sent from my GT-S5830 using xda premium
Taracair said:
Since I'm using firekernel I have weird problems with touchscreen. It happens randomly by itself - the bottom left area of the touchscreen is being tapped as I tap different areas. I don't OC. I wouldn't like to change my current rom (nitrogen rom) because it's really awesome, but it's annoying like hell to erase mistyped letters almost every time. It happened in different roms too, with the same kernel.
If it's necessary I can change the kernel but it would be good if it has kernel memory mod path by psn available.
Are you guys facing the same problem? Are there any patches to fix it? Or maybe you can prefer other kernel which would work with nitrogen/the ultimate rom and psn patch?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
brother it may be the problem of your touch i think it have got weak or faulty go to customer care and have it checked
aditya rathee said:
brother it may be the problem of your touch i think it have got weak or faulty go to customer care and have it checked
Click to expand...
Click to collapse
Thank you for your message. As I said before - everything is fine when I don't use firekernel so it's not hardware fault.
Sent from my GT-S5830 using xda premium
It is either your digitizer fault or because of an unclean android system. Flash stock via odin & reflash the ROM. If problem persists, replace your digitizer.
Sent from my GT-S5830 using xda app-developers app
Venomous Viper 119 said:
It is either your digitizer fault or because of an unclean android system. Flash stock via odin & reflash the ROM. If problem persists, replace your digitizer.
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
That's obvious! I don't want to change my ROM to stock. And it's not hardware fault.
I just want to install other kernel which is somehow simillar to firekernel.
Taracair said:
That's obvious! I don't want to change my ROM to stock. And it's not hardware fault.
I just want to install other kernel which is somehow simillar to firekernel.
Click to expand...
Click to collapse
yeah you can try space kernel it is also good
Well like the title says I was wondering if we might be able to use kexec to boot cm on our devices. If I'm not mistaken that's what is used for the droid 3 to boot cm
Sent from my SAMSUNG-SM-N900A using Tapatalk
This has been discussed many times here and in multiple other device forums. At this point, it has not been implemented into SafeStrap. I am not sure if it is possible or not, nor do I know if hash is working on putting it in. He is aware of it though.
Sent from my SM-N900A using XDA Premium 4 mobile app
kexec uses a hijacked kernel module to direct to a different kernel placed on the SDcard. Sort of like how SS works, but a bit differently. All SS does is direct the kernel to a different image. Kexec needs a hijacked module to load an insecure kernel. While this sounds easy to implement, trust me it will most likely never happen with the note 3. The problem is that the note 3 doesn't have any modules. And don't ask about inserting them, because the kernel will not run them. They are completely disabled in this kernel. That property is set when the kernel is compiled, so with it being disabled, we cannot enable it, and we cannot hijack the modules, because they are completely disabled.
Thanks for your informative reply. Just thought id ask
Sent from my XT862 using Tapatalk