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

[Soytudios]

this only works, on the main screen
does not works, on the lock screen

work with you google maps

Go to Settings > Security > Ring shorcuts (i think this is the translation, i have it in spanish) and the last option is to activate the torch when you double tap and hold the unlock ring in lockscreen.

Hope it hepls.

 

[gruniu78]

Go to Settings > Security > Ring shorcuts (i think this is the translation, i have it in spanish) and the last option is to activate the torch when you double tap and hold the unlock ring in lockscreen.

Hope it hepls.

no

one more time:
1) screen lock, i hold and i let button turn on torch
2) torch shine
3) i hold and i let button turn off torch
4) torch goes out

not works me:
screen cast and google maps

 

[SurajH]

This ROM is with 240 DPI OR 320 DPI
Want to try Now
I think its 240 Dpi want to try with 320 Dpi so can i change it to 320 ? It will cause any issues?
And also want to know having CM Theme manager ?

 

[fusionjack]

no

one more time:
1) screen lock, i hold and i let button turn on torch
2) torch shine
3) i hold and i let button turn off torch
4) torch goes out

not works me:
screen cast and google maps

ok, again...you cannot use torch with hardware button on lockscreen, but you need to use lockring or slider instead. it works the same but with double tap. it is much better like this since the hardware buttons could be pressed accidentally in your jeans.

This ROM is with 240 DPI OR 320 DPI
Want to try Now
I think its 240 Dpi want to try with 320 Dpi so can i change it to 320 ? It will cause any issues?
And also want to know having CM Theme manager ?

the default dpi is 245. you can use any app to change it.
no theme support (yet)

 

[fusionjack]

a new build is up for testers...

 

[riaan0010]

Test Build 13-07-2014

New Test Build Booted Fine ( Like Always ). Testing now

Thank you Fusionjack

 

[fusionjack]

SlimSaber-n7000-4.4.4-20140713.zip

Changes:

• Fix Bluetooth FC
• Change ro.build.version.codename from UNOFFICIAL to REL
• Lower the minimum brightness as suggested by some users from XDA
• TWRP: Track omnirom repo
• HeadsUp: Some fixes
• See changelog for the rest of changes

 

[boris03]

Just in the right time

Sent from my C6833 using XDA Free mobile app

 

[korkunov]

@fusionjack n German people
Congrat-n!

 

[SurajH]

I Flashed Latest Test build so far all GOOD but want to try with default 320DPI can i change it and Test
Is it cause any issues
And Please suggest safe app to change DPI count.
Thanks Dev for Fantastic Rom:good:

 

[fusionjack]

I Flashed Latest Test build so far all GOOD but want to try with default 320DPI can i change it and Test
Is it cause any issues
And Please suggest safe app to change DPI count.
Thanks Dev for Fantastic Rom:good:

i usually use build prop editor app to change the dpi. there is also dpi changer app. it should be safe. in worst case, you get bootloop. reflashing the rom with formatting system should bring back to the previous state.

 

[j1gga84]

@fusionjack

I think startpost and thread title is wrong
It is 07/13, not 07/11

Regards

 

[fusionjack]

@fusionjack

I think startpost and thread title is wrong
It is 07/13, not 07/11

Regards

i must hate the number 13 ;p

 

[gruniu78]

does not work screen cast

 

[fusionjack]

a new build is up for testers...
see this release summary for some info: http://forum.xda-developers.com/showpost.php?p=54197307&postcount=13598

 

[Theo Chamalis]

When I booted up from the new build I got the following FC: Unfortunately, the process android.process.acore has stopped. It did not affect anything till now and everything that I've used works fine. I wonder what that FC was about... Thanks again for the build FJ ! I will report if anything comes up

 

[pSyCh¤_O_O]

does not work screen cast

Have you tried with Allcast from playstore?
Never tried this feature but give that app a try anyway. Screencast might not even be supported by our device. No idea.

When I
booted up from the new build I got the following FC: Unfortunately, the process android.process.acore has stopped. It did not affect anything till now and everything that I've used works fine. I wonder what that FC was about... Thanks again for the build FJ ! I will report if anything comes up

Did you reboot? Does it happen after reboot?

Downloading...

 

[Theo Chamalis]

It happened only on the initial setup just before choosing language and haven't seen it since.

 

[pSyCh¤_O_O]

It happened only on the initial setup just before choosing language and haven't seen it since.

It happens sometimes. Reboot solves it. Not an issue AFAIK.

Edit. Booted fine. I didnt have FC.

SlimSaber is on Fireeeeee!!!![emoji91][emoji91][emoji91][emoji91][emoji91]

[emoji6][emoji6][emoji7]

 

[fusionjack]

When I booted up from the new build I got the following FC: Unfortunately, the process android.process.acore has stopped. It did not affect anything till now and everything that I've used works fine. I wonder what that FC was about... Thanks again for the build FJ ! I will report if anything comes up

It happens sometimes. Reboot solves it. Not an issue AFAIK.

yeah, i also got that but very rarely. that issue might have something to do with creating dalvik cache and i have feeling since the 'multi-threaded dalvik cache creation at boot' feature, somehow there is a race condition which leads to that fc later in the home screen. this is my assumption so i could be wrong.
usually if i get that kind of fc, i wipe the dalvik cache again.
...and thanks for testing. :good: