[ROM][4.4.4][10/21] SlimSaber - n7000

[Super Prince]

Thanks.. But i think this is completely uncorrelate.
It happens exactely as I reported in Asylum thread some weeks ago: http://forum.xda-developers.com/showpost.php?p=49704669&postcount=11942

Take a look.

As i see in your asylum post, this black screen is caused by the sdcard fuse bug and even if you killed the app the heating and drain will continue and the app usually will not start again because of the fuse bug until you do exactly this in terminal emulator

su
pkill sdcard

After that the phone will be normal again (without rebooting) I am not a developer or a technical guy but this is what i have been doing all the time using KK and its working for me.

Sent from my GT-N7000 using Tapatalk

 

[PharrellVP]

See, guys. My phone heats too much and drains more than ever. I stopped Google+ and disable it and here it is the result...

Sent from my GT-N7000 using XDA Free mobile app

 

[Super Prince]

See, guys. My phone heats too much and drains more than ever. I stopped Google+ and disable it and here it is the result...

Sent from my GT-N7000 using XDA Free mobile app

If google+ disabled correctly it will disappear from the battery state but it is there in screenshot. Freeze it with titanium backup or uninstall it better.

 

[fusionjack]

can you add this double tap to wake feature in slimsaber
http://forum.xda-developers.com/showthread.php?p=52966673
Sent from my GT-N7000 using XDA Free mobile app

no, it needs touch wake support from kernel side. the touch wake was recently reverted on 4412 devices since it causes some issues.
so don't expect this on our device.

Is there double tap to sleep option present in this rom? Tnx

nope, it is enabled by default.

I'm getting the same on fresh installs.. Seemes some drivers or kernel bug that cause app to be unresponsive and hug 100% of cpus
Inviato dal mio GT-N7000 utilizzando Tapatalk

Every now and then my note gets really hot and if I don't notice it shuts down, sometimes it reports that gpsd is using a large percentage of the battery, other times it's the screen. Sometimes the responsiveness goes way down and I have to reboot. Once it took 4 reboots to stop the overheating.
I've only been doing dirty flashes, could this be the cause or is anyone else getting the same with a clean flash?

i have the same opinion with @Twiq, your issues are mostly related to the sdcard fuse bug.
not all users suffer from this bug. this bug is also pretty random. there is a thread that discusses this issue in the faq, you can try their suggestions. if you still suffer from this problem, then i'm afraid you need to downgrade to jelly bean.

 

[yokonunz]

no, it needs touch wake support from kernel side. the touch wake was recently reverted on 4412 devices since it causes some issues.
so don't expect this on our device.


nope, it is enabled by default.



i have the same opinion with @Twiq, your issues are mostly related to the sdcard fuse bug.
not all users suffer from this bug. this bug is also pretty random. there is a thread that discusses this issue in the faq, you can try their suggestions. if you still suffer from this problem, then i'm afraid you need to downgrade to jelly bean.

What the bug is related to? Is there a way to make a script that check what "can break" and automagically kill that process?

EDIT: What about this http://forum.slimroms.net/topic/1778-sd-card-fuse-bug-fixed/ ?

 

[Super Prince]

I have the same opinion with @Twiq, your issues are mostly related to the sdcard fuse bug.
not all users suffer from this bug. this bug is also pretty random. there is a thread that discusses this issue in the faq, you can try their suggestions. if you still suffer from this problem, then i'm afraid you need to downgrade to jelly bean.

I agree with you , I have downgraded to slimbean 4.3.1 very stable rom compared to the current KK roms.

and exFat is really a good workaround to avoid this nasty bug in KK for the timebeing

 

[yokonunz]

I agree with you , I have downgraded to slimbean 4.3.1 very stable rom compared to the current KK roms.

and exFat is really a good workaround to avoid this nasty bug in KK for the timebeing

exFat on both internal ed external sdcard?

 

[Super Prince]

exFat on both internal ed external sdcard?

yes, check this thread to know more.

 

[PharrellVP]

If google+ disabled correctly it will disappear from the battery state but it is there in screenshot. Freeze it with titanium backup or uninstall it better.

I just uninstalled the Google+. I hope the battery drain would stop right away I got battery drain since yesterday/when I installed the rom/ though... What else could it be if it turns out Google+ not the only one drainer...

 

[yokonunz]

yes, check this thread to know more.

Seems like not everyone find the right solution. Somesays ext4/exfat and someone else says that the bug still occur.

 

[PharrellVP]

Just for sure. How is my CPU doing now after uninstallin Google+? It seems not that hot my phone, but still..

Sent from my GT-N7000 using XDA Free mobile app

 

[Super Prince]

I just uninstalled the Google+. I hope the battery drain would stop right away I got battery drain since yesterday/when I installed the rom/ though... What else could it be if it turns out Google+ not the only one drainer...

Google+ is the only app causing unusual heat and drain in KK . Any other unusual heat and drain may be to the fuse bug but this is not happening for everyone.

Seems like not everyone find the right solution. Somesays ext4/exfat and someone else says that the bug still occur.

with Exfat it does not happen I can copy whatever i want back and forth between internal and external. without exfat I can not even copy 100 mb file and a lot of heating and draining.

And do not go with ext4 if you are using windows desktop to copy files to the phone since it is not supported by windows.

Just for sure. How is my CPU doing now after uninstallin Google+? It seems not that hot my phone, but still..

Sent from my GT-N7000 using XDA Free mobile app

Normal CPU behaviour

 

[fusionjack]

a new build is up for testers...

 

[LukaszBobrek]

There is rather big problem with new release... I cannot move my apps to sd using titanium backup - tried both on dirty and clean install.

Anyone has the same problem?

---------- Post added 4th June 2014 at 12:36 AM ---------- Previous post was 3rd June 2014 at 11:55 PM ----------

I just did some more testing - on 2014/05/31 build moving apps to sd works, and after upgrading to 03/06/2014 it fails.

 

[PharrellVP]

Can someone recommend me weather widget such as Accuweather suitable for our ROM? Also a keyboard with numbers row on the top of the letters?

Sent from my GT-N7000

 

[fusionjack]

There is rather big problem with new release... I cannot move my apps to sd using titanium backup - tried both on dirty and clean install.

Anyone has the same problem?

---------- Post added 4th June 2014 at 12:36 AM ---------- Previous post was 3rd June 2014 at 11:55 PM ----------

I just did some more testing - on 2014/05/31 build moving apps to sd works, and after upgrading to 03/06/2014 it fails.

grrr...this is because of the new feature 'move to ext sdcard'. this feature is still disabled for our device and it looks like it ends up completely disables the whole 'moving apps'
sorry for that...i didn't notice this and i'll try to enable it.

Sent from my GT-I9100 using Tapatalk

 

[Twiq]

I'm getting the same on fresh installs.. Seemes some drivers or kernel bug that cause app to be unresponsive and hug 100% of cpus

Every now and then my note gets really hot and if I don't notice it shuts down, sometimes it reports that gpsd is using a large percentage of the battery, other times it's the screen. Sometimes the responsiveness goes way down and I have to reboot. Once it took 4 reboots to stop the overheating.
I've only been doing dirty flashes, could this be the cause or is anyone else getting the same with a clean flash?

as promised..
sorry, forgot to post yesterday

if you have media scanner or sdcard fuse daemon bug issues try these steps to minimalize it from happening:

1. REBOOT, yes this is necessary to make sure no block/sectors are locked by any (corrupt?) processes
2. run this in your favourite terminal emulator :

mount | grep sdcard <press enter>

3. read the output next to /vold/
if you have sdcard installed, you should have 2 similar entries (change the red colored code below)
WARNING! these are example for i9100:

su <press enter>
fsck_msdos -p -y /dev/block/vold/[COLOR="Red"]179:9[/COLOR] <press enter>
fsck_msdos -p -y /dev/block/vold/[COLOR="Red"]259:3[/COLOR] <press enter>

you may run it a couple of times until there are no "YES" word in the output.

ADDITIONAL STEPS :

4. Open System Settings > Apps > go to "ALL" Tab > Media Storage
Force stop the process, then clear its data and cache

5. Reboot, after it boots up let media scanner to run (wait +5 mins should suffice)

6. Use phone as usual

IF MEDIA SCANNER STILL STUCKS

find .thumbnails folder under DCIM folder then delete it, after that reboot.

 

[j1gga84]

grrr...this is because of the new feature 'move to ext sdcard'. this feature is still disabled for our device and it looks like it ends up completely disables the whole 'moving apps'
sorry for that...i didn't notice this and i'll try to enable it.

Sent from my GT-I9100 using Tapatalk

I think the problem is also present in I9100 build because a german user told me about that in german android forum, just for your information


Regards

 

[yokonunz]

as promised..
sorry, forgot to post yesterday

if you have media scanner or sdcard fuse daemon bug issues try these steps to minimalize it from happening:

1. REBOOT, yes this is necessary to make sure no block/sectors are locked by any (corrupt?) processes
2. run this in your favourite terminal emulator :

mount | grep sdcard <press enter>

3. read the output next to /vold/
if you have sdcard installed, you should have 2 similar entries (change the red colored code below)
WARNING! these are example for i9100:

su <press enter>
fsck_msdos -p -y /dev/block/vold/[COLOR="Red"]179:9[/COLOR] <press enter>
fsck_msdos -p -y /dev/block/vold/[COLOR="Red"]259:3[/COLOR] <press enter>

you may run it a couple of times until there are no "YES" word in the output.

ADDITIONAL STEPS :

4. Open System Settings > Apps > go to "ALL" Tab > Media Storage
Force stop the process, then clear its data and cache

5. Reboot, after it boots up let media scanner to run (wait +5 mins should suffice)

6. Use phone as usual

IF MEDIA SCANNER STILL STUCKS

find .thumbnails folder under DCIM folder then delete it, after that reboot.

After I followed all steps when i reboot mediascanner doesn't start and I get a blank gallery. (Files are still there)
How to fix?

 

[Twiq]

After I followed all steps when i reboot mediascanner doesn't start and I get a blank gallery. (Files are still there)
How to fix?

Have you waited at least 5 minutes after booting?
Did you disable media scanning behavior?

Thumbnails are automatically generated, just go to gallery then press menu and refresh.

Or trigger media scanner by opening "dev tools" app > media provider > scan sd card

Running 0522 Sabered SlimKat | DorimanX 10.43v111