yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] Kinsman-UK:
Hi [MENTION=1228651]fusionjack[/MENTION],

Here are the results of my tests which I had a chance to do today, regarding the apps moved to SD disappearing on reboot. With both internal and external SD cards formatted to exFAT, here is what I did:

1) Powered off and removed external SD to keep it out of the equation.

2) Rebooted and performed a factory reset from the Settings menu.

3) Rebooted and installed two apps: BBC News and Wikipedia

4) Both apps installed and worked successfully.

5) Moved both apps to SD card, both continued to work 100%

6) Rebooted

7) Neither app now works after reboot - both give 'App isn't installed' message.

So next I did a full wipe, and reformatted internal SD to vFat, as you suggested, using PhilZ Kernel:

1) Did a full wipe and installed the 08/12 build of SlimSaber

2) Rebooted with external SD card inserted still formatted to exFAT

3) Installed BBC News and Wikipedia apps, and moved them to SD card

4) Rebooted and both apps work successfully while moved to SD!

So it seems that perhaps there is a problem with moving apps to the SD card when it is formatted to exFat. For now I will stick to vFat and see if any other problems arise, hopefully I won't need to use exFat on the internal SD after all.

It will be interesting to know if [MENTION=2244369]yokonunz[/MENTION] has the same problem, as this would confirm that it's not something else causing it on my device.

Thanks again for this fantastic ROM - I was getting very frustrated with my N7000 on Samsung stock 4.1.2 and was seriously considering purchasing a Note 4 when they come out next month. Using SlimSaber was my first attempt at installing a Custom ROM and it has given my device a new lease of life - it's a pleasure to use again. Hopefully I won't need to change my phone for quite some time yet!
[Galaxy Note GT-N7000 Android Development] Twiq:
They are valid, and implementable for those who want to try other settings than stock gov :)
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
Ive been playing about with zzmoove latelly and im really liking profile 10 for gaming. No issues whatsoever [emoji106]
[Galaxy Note GT-N7000 Android Development] AhmadOkda:
Mt4 (meta trader 4) issue,

Anyone else using mt4 on their note running this rom? I have an issue that the currency values appears as 0.0000,i contacted meta quotes and they informed me that mt4 is working fine on other 4.4.4 mobiles so it must be a rom issue

I am using version 4 of August
[Galaxy Note GT-N7000 Android Development] fusionjack:
thanks for your testing...

honestly, i really hate the nasty sdcard issue on our device. just in case you don't know, we still have sdcard fuse bug which appears random. this could be workaround-ed by using exfat.

till now i only tested exfat with external sdacard. based on your test, apparently there is a problem with moving-app to internal storage when it is exfat. this would be hard to trace where the problem lies...therefore for now don't expect a fix, sorry. :(

as long as there is no real need to format internal storage with exfat, then i'd leave it as vfat...
[Galaxy Note GT-N7000 Android Development] fusionjack:
oh btw, [MENTION=1190912]Kinsman-UK[/MENTION] thanks a lot for your support, really appreciate it. :) :good:
[Galaxy Note GT-N7000 Android Development] fusionjack:
what is the correct value? two digits?
[Galaxy Note GT-N7000 Android Development] Kinsman-UK:
You're welcome - just a small token of appreciation for your work! I had formatted to exFat to avoid sdcard fuse bug - but as I haven't actually encountered it yet, I will stick with vFat on internal for now :good:
[Galaxy Note GT-N7000 Android Development] AhmadOkda:
Attached are two images showing the correct values from another mobile and how do they appear on my Note

Thanks for your support

Edit:

It seems any value above one, the number on the left of the dot is changed to zero, either it is 1 or 2 or even 102

While any value less than one is changed to 0.0000

Edit2: I updated to version 12/8 and still the same issue, I have just started using kitkat from version 4/8, everything was fine on the jellybean versions
[Galaxy Note GT-N7000 Android Development] archraziel:
Flash led

Hey....my problem is the flash led, it's not working and when I let it turned on, my Camera app FC.

When i use the torch app to test it, if I keep on turning the led on, I can see it blinks really fast

It this a rom installation problem or it's more of a hardware problem?

Can someone help me, please?
[Galaxy Note GT-N7000 Android Development] Kinsman-UK:
Just tested on mine with latest build, using built in 'Torch' app and 'TeslaLED' from Play Store and it works fine here.

EDIT: Also tested Camera with Flash on and no FC.
[Galaxy Note GT-N7000 Android Development] fusionjack:
hmm, can't say anything. i don't have any idea what might be the reason...

try other camera app first. if it still the same, then try full wipe.

camera with flash is fine on my i9100...
[Galaxy Note GT-N7000 Android Development] proton_saopei:
I still encounter battery draining fast when my N7000 is in standby mode, either when I flash SlimSaber 4.4.2 or 4.4.4.

Else, everything of SlimSaber is so perfect.
[Galaxy Note GT-N7000 Android Development] der_Kief:
Same here, high battery drain when in Standby. Device is going to deep sleep, thats not the problem !

Everything else is working properly. But im back to Slimkat for now.....
[Galaxy Note GT-N7000 Android Development] pardus:
Thankfully I'm not the only one as there seem now to be others with the same problem, have clean flashed twice now to try stop the battery drain but it seems to come back.
[Galaxy Note GT-N7000 Android Development] AhmadOkda:
I tried the normal slimkat and it is working fine

So it seems it is really related to slimsaber

I am ready for any help needed from my side if you have the time to check the issue

It was a dirty flash by the way
[Galaxy Note GT-N7000 Android Development] Twiq:
Dont check the strobe.. Thats all i can think of
[Galaxy Note GT-N7000 Android Development] fusionjack:
since when this happens? how high is the drain?

see in settings - battery which app is at the top of the list. do bbs if necessary to find out...

the battery drain could come from the sdcard fuse bug. this could happen in random.
[Galaxy Note GT-N7000 Android Development] sergey1369:
Hello.

Does this fix help with sdcard fuse bug?

http://xdaforums.com/showpost.php?p=51657055&postcount=304
[Galaxy Note GT-N7000 Android Development] nursoda:
Cannot help you with the actual failure but would point you to TB support/forum (never checked where they are) and wanted to add that I never encountered this issue with no ROM, ever.
[Galaxy Note GT-N7000 Android Development] nursoda:
no drain here
[Galaxy Note GT-N7000 Android Development] Kinsman-UK:
Likewise. I've only been using 4.4.4 for about a week, but definitely find the battery life improved over 4.3.1 - no unexpected or unusual drain. With Wi-Fi always on and email, all the usual Google stuff (except G+), Twitter, eBay and Evernote syncing, I'm not losing any more than 1% per hour. Only battery saving measures I'm using are Greenify (root) and Screen Dimmer. Battery is an almost 18 month old Anker 2700mAh. I suspect more details would be needed for any diagnosis of battery drain others are having.
[Galaxy Note GT-N7000 Android Development] fusionjack:
i have already applied that months ago. :)

try force system busybox n sqlite. go in preferences - troubleshooting
[Galaxy Note GT-N7000 Android Development] archraziel:
The strobe is off

I tryed already with other camera app...and did full wipe

I have this problem for about 3 months...I post in here the first time it started, but did not get any answers :/
[Galaxy Note GT-N7000 Android Development] Kinsman-UK:
Hi [MENTION=4510534]archraziel[/MENTION] - have you tried flashing a different ROM or version, perhaps go back to stock, and see if the problem is still there? This would help show you whether it's a ROM problem or a hardware problem.
[Galaxy Note GT-N7000 Android Development] phedders:
Well that was better. I restored a bunch of apps and could still use play.

Then I restored a bunch more... and rebooted now I get the 110 error and a crash loop on

Unfortunately, the process com.android.systemui has stopped.

logcat is constantly spewing what looks like a repeating:

D/AndroidRuntime( 3394): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 3394): CheckJNI is OFF
D/dalvikvm( 3394): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 3394): Added shared lib libjavacore.so 0x0
D/dalvikvm( 3394): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 3394): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 3394): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
E/cutils-trace( 3394): Error opening trace file: No such file or directory (2)
D/dalvikvm( 3394): Note: class Landroid/app/ActivityManagerNative; has 181 unimplemented (abstract) methods
D/AndroidRuntime( 3405):
D/AndroidRuntime( 3405): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 3405): CheckJNI is OFF
D/dalvikvm( 3405): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 3405): Added shared lib libjavacore.so 0x0
D/dalvikvm( 3405): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 3405): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 3405): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
E/cutils-trace( 3405): Error opening trace file: No such file or directory (2)
D/dalvikvm( 3405): Note: class Landroid/app/ActivityManagerNative; has 181 unimplemented (abstract) methods
E/memtrack( 3394): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug( 3394): failed to load memtrack module: -2
D/AndroidRuntime( 3394): Calling main entry com.android.commands.am.Am
E/memtrack( 3405): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug( 3405): failed to load memtrack module: -2
D/AndroidRuntime( 3394): Shutting down VM
D/AndroidRuntime( 3405): Calling main entry com.android.commands.am.Am
D/AndroidRuntime( 3421):

Why would the TT/TBP supplied busybox/sqlite be a problem? Weird. Anyway seems to be more of a problem than just that.
[Galaxy Note GT-N7000 Android Development] archraziel:
hey man,

Did not try other rom, I will try go back to stock and see if work, and I will come back with news about it.
[Galaxy Note GT-N7000 Android Development] fusionjack:
i though your TB is hanging while restoring apps. that's why i suggest you to use system busybox n sqlite.

did you restore system apps? you shouldn't restore any system apps, only data apps from the same android version. restoring 4.3.1 data apps to 4.4.4 is a bad idea...
[Galaxy Note GT-N7000 Android Development] phedders:
No the phone starts giving errors trying to install from play store TBP or adb.

The backups I'm restoring are all recent - 4.4.3 at least - and the only system restore I tried was for SMS and call log. That seemed to go ok (was in the first batch).
[Galaxy Note GT-N7000 Android Development] LukaszBobrek:
[MENTION=1228651]fusionjack[/MENTION] would you consider cherry-picking Lockscreen Notification from slim gerrit? - https://gerrit.slimroms.net/#/c/6933/

I am asking because I am not advanced enough to build my own build and this is the feature that I (and a lot of other users) would be really glad to see in your awesome rom ;)
[Galaxy Note GT-N7000 Android Development] fusionjack:
errmm now adb? what is tbp? i think i'm lost here...lol.

anyway, fc on system ui usually indicate that old system data is restored.

yeah i was planning to give a shot...
[Galaxy Note GT-N7000 Android Development] proton_saopei:
The battery drainage situation happens quite frequently, about one or two times a day. When I put the N7000 in my pocket with about 90% battery level, after an hour I took out the N7000 from my pocket, I felt the the phone is really hot and I noticed that the battery level dropped to about 50%.
[Galaxy Note GT-N7000 Android Development] phedders:
Sorry to confuse :)

TBP = Titanium Backup Pro

Once the phone is broken ie I get the -110 errors, I cannot install from play app or play website, nor can I "adb install foo.apk"
[Galaxy Note GT-N7000 Android Development] Twiq:
Check the battery stats, i bet it's media services.

If necessary, continue monitoring with BBS..

You could minimize media scanner stucking issue by cleaning .thumbnails folder inside /dcim/

Also try checking your sdcards for corruption, you could read how tos here http://xdaforums.com/showpost.php?p=50264173&postcount=9137
[Galaxy Note GT-N7000 Android Development] fusionjack:
i want to say many thanks to [MENTION=5203387]deremarry[/MENTION] for the support. :):good:
[Galaxy Note GT-N7000 Android Development] fusionjack:
i see...how about if you just restore the app without its data?

i also using TB to restore some apps. it is indeed sometimes hanged, but i didn't have that error and i can still install other app as usual.
[Galaxy Note GT-N7000 Android Development] Zzgfont:
I use "All in One Toolbox" to clean thumbnails and logs from the phone.

Then I usually face 2 situations:

1) the drain is due to the media scanner (usually after a reboot). It drains the battery very quickly (like 60% after 3 hours). Moreover there are other weird behaviour (all the ringtones are missing, and so are the list of the mp3 available on the player). You can reboot the device, but sometime it's better to leave it plugged to the AC and wait until it stops and reboot at the end.

2) the drain is not due to the media scanner (the battery stats show the max usage comes from android or from the screen). Drains not so quickly (I'm not able to reach the end of the day with a 100% battery). Usually I clean the cache/dalvik cache. This stops the drain, as the reboot seems not to solve the problem.
[Galaxy Note GT-N7000 Android Development] fusionjack:
that is caused by the sdcard fuse bug. it is also possible that some media files are corrupted or mediaserver has problem to index them.

the missing ringtone is an indicator that mediaserver stuck (which drains battery) before it can index the ringtones.

for media files, see in faq for possible solutions. if your media files are on ext sdcard, you can also try to format it to exfat. this could workaround sdcard fuse bug. don't forget to backup your media files first on pc or somewhere else...
[Galaxy Note GT-N7000 Android Development] phedders:
I'll try that. I had tried just data restores (ie restore app from play then restore the data - and that seemed to have some success.

And yes I've had the TBP restores hang many times in the past. Annoying that one! But this is a different problem.

Thanks again for your thoughts on it :cool:
[Galaxy Note GT-N7000 Android Development] fusionjack:
a new build is up for testers
[Galaxy Note GT-N7000 Android Development] LukaszBobrek:
Build boots fine ;) Thank [MENTION=1228651]fusionjack[/MENTION]

I will test new features and report soon.
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
Flashed ROM+ gapps+ new kernel , wiped cache & dalvik.

Everything ok for last few minutes. [emoji106]

Thanks fusionjack

BTW I couldn't see anything in changelog regarding kernel..only changes in performance control apk AFAIK. Any info?
[Galaxy Note GT-N7000 Android Development] nursoda:
Testers: Since some users experienced FCs when accessing Security Setings on current SlimSaber i9100, could you please double-check?

Samsung Note N7000, Galaxy S I9000, Galaxy Ace S5830
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
All good here. I went through all security settings without problems...
[Galaxy Note GT-N7000 Android Development] fusionjack:
the security settings fc only when you are using face unlock and gesture. slide, pattern, pin or password are fine.
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
We don't have face unlock here so where safe ;)

And gesture fcs but it works fine after that...
[Galaxy Note GT-N7000 Android Development] LukaszBobrek:
We do have face unlock! It depend on gapps you have installed, in both normal and full slim gapps there is face unlock. All tested, and no FCs ;)

Wysłane z mojego GT-N7000 przy użyciu Tapatalka
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
Never use anything apart from slim-gapps as recommended due to small system partition. Why would I want to bloat an un-bloated ROM with google shait [emoji3]

Good to know though thanks. If I remember correctly you can manually flash face unlock mod from slimroms site too.
[Galaxy Note GT-N7000 Android Development] fusionjack:
btw, i'll postpone yesterday build and i'll fix the security setting tonight and release it...

i uploaded the kernel first. it is just a latest kernel that we have till now. there is no new changes.

SlimKernel-n7000-4.4.4-20140819.zip

edit: for testers, sorry i didn't explain it earlier regarding the kernel :angel:
[Galaxy Note GT-N7000 Android Development] m1trand1r:
yes....gesture works fine after Settings fc's once....but....can you change it back to slide?...I can't even access settings anymore ....lol...I have to wipe settings data now....:)
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
Yes. Same here. I tried several workarounds without luck. Only solution is what FJ said...

Revert back to earlier build,change security back to slider and then flash new build again (and obviously dont touch lockscreen security settings untill new build with a fix by Master [MENTION=1228651]fusionjack[/MENTION])
[Galaxy Note GT-N7000 Android Development] fusionjack:
i'll post a new build tonight with a fc fix...

fc happens because it cannot find the lockscreen notification options and the code doesn't guard for this situation. the lockscreen notification options are only available on slider, pattern, pin and password. as long as you use those mentioned lock mechanism, there won't be fc and you safe to open security settings as usual.
[Galaxy Note GT-N7000 Android Development] fusionjack:
SlimSaber-n7000-4.4.4-20140820.zip

SlimKernel-n7000-4.4.4-20140819.zip (No changes, it is just latest kernel)

Changes:

Synced with weekly 7.4

Compiled with latest SaberMod 4.8.4 and 4.9.2 20130814

Lockscreen notifications

Settings - Security

Show/hide network speed arrow icons

Settings - Interface - Statusbar

Extended configurable overflow menu button

Settings - Navigation - Hardware buttons

PerformanceControl: Rework time in stats

libcore: Fix parsing of fractional seconds

See changelog for the rest of changes
[Galaxy Note GT-N7000 Android Development] fusionjack:
for testers, if you use 08/19 build and don't use gesture or face unlock lockscreen mechanism, you don't need to update to 08/20 build. it is just bug-fixing build.
[Galaxy Note GT-N7000 Android Development] der_Kief:
Hi,

i have a question about updating to a newer version of Slimsaber ?

On first post you describe the following:

- Wipe cache and dalvik cache.
- Flash the unofficial build.
- No need to re-flash gapps. Gapps will be restored back automatically by backup
tool during flashing.

On the official Slimkat site they desribe the following:

- Download latest SlimRoms and latest gapps and put them on your sd card
- Boot to recovery
- In CWM, wipe cache, dalvik and format system in mounts and storage section
- In TWRP choose advanced in wipe section and wipe cache, dalvik and system
- Flash ROM
- Flash Gapps
- Reboot

Which way to go ?
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
They're both OK.

I normally wipe cache ,dalvik cache and flash ROM and gapps because I'm in the habit of doing it that way.

I could avoid flashing gapps because autobackup script should take care of it but there's no harm done and if I do full wipe and i forget to flash gapps I don't have to reboot back into recovery to flash gapps.

-If I want to do a semi clean flash I also wipe system(apart from cache and dalvik).

-If I want to do a full wipe.... I tick cache, dalvik, system and data from recovery/advanced wipe options.

Hope it helps
[Galaxy Note GT-N7000 Android Development] fusionjack:
additionally to [MENTION=4181659]pSyCh¤_O_O[/MENTION]:

basically, they are both doing format system. the difference: the (1) flashing method does backup and then restoring it whereas the (2) one doesn't do backup. now, for example, if you use different dpi than stock one and choose (2) flashing method, you need to setup again your dpi by each flash. with (1) you don't need to setup it again.

it's your choice which method you want to use...i'm using the (1) one.
[Galaxy Note GT-N7000 Android Development] der_Kief:
[MENTION=4181659]pSyCh¤_O_O[/MENTION]
[MENTION=1228651]fusionjack[/MENTION]

Thank you both for your detailed information. Now i understand the difference :o
[Galaxy Note GT-N7000 Android Development] Hank87:
Hi [MENTION=1228651]fusionjack[/MENTION], what do you think about this?

http://xdaforums.com/showthread.php?p=54690465

The note/s2 are the only galaxy devices that doesn't support line call recording on kitkat and only works on stock samsung rom or old aosp roms. Can you take a look on this thread, if it's possible to add rom support?

Thank you! ?
[Galaxy Note GT-N7000 Android Development] bladecgn:
My settings FC on klicking on "Notifications and QS Drawer" with latest build.

At fist (after a clean install) it worked but after changing some tiles it ist FCing everytime I am trying to access it.

Anyone else experiencing this problem?
[Galaxy Note GT-N7000 Android Development] canguroribelle:
please, I have a problem:

I flashed slimsaber 4.4.4 using the first kernel SlimKernel-n7000-4.4.4-20140623.zip

and all was ok. Than i installed many apps and all was ok too.

I decided to update kernel with new SlimKernel-n7000-4.4.4-20140705.zip but after reboot my bluetooth wan't installed.

I try to reinstall it by original app ( /system/app/bluetooth.apk) but it doesn't install nothing.

In titanium backup, com.android.bluetooth is cut as if I had uninstalled it (without backup). But I never did it!

I tried to flash the old kernel but it's the same, bluetooth doesn't work yet.

I restored nandroid backup that was ok (bluetooth worked) but it's the same, after restored bluetooth isn't installed.

So, I tried to flash Slimkat 4.4.2 and bluetooth is ok. But I prefer Slimsaber.

Someone could help me please?

Thanks so much.

Guly
[Galaxy Note GT-N7000 Android Development] fusionjack:
call recording could cause serious legal issue in some countries :)

grab a logcat...settings - slimcenter - bugreport - attach the zip file here

there was a bluetooth issue in old build but it has nothing to do with kernel.

btw, why are you using old kernel? the rom contains already latest kernel, you don't need to flash kernel again.

i'd suggest you to full wipe and flash latest build without flashing kernel.
[Galaxy Note GT-N7000 Android Development] canguroribelle:
Ok, I didn't know that the rom contains kernel. I'll flash again without flashing kernel.

Thanks
[Galaxy Note GT-N7000 Android Development] Hank87:
It's a bulls**t! ?, call recording works on kitkat in all samsung galaxy, don't work only on sgs2 and note 1!

And in Europe and most countries in the world is legal in fact,often, this function is implemented natively even in official rom.
[Galaxy Note GT-N7000 Android Development] m1trand1r:
It works yes....but...dev could get into serious troubles if he implements Call Recording feature in kernel....that's one of the reasons why dorimanx kernel don't have it....

If you want call recording feature head back ti stock sammys rom which has it.....as Samsung is Inc. ....no one can touch them....

But do behave in future.....respect what dev has to say.....or else....build your own kernel....and add call recording patch....flash it and enjoy..;)
[Galaxy Note GT-N7000 Android Development] der_Kief:
one short question about setting up touchscreen sensitivity in advanced options.

Is a higher value more sensitive than a lower value ?

I dont know but i dont see/feel any difference between those values ! Does it work for others ?