got english translation?

you help lah

but wait for him to post first

what firmware you at?
if below .423 = power button can (long press till the menu comes out)
if .423 onwards = power button + volume down

then should be power + volume down.. try that already?

got such thing?

try taking off the case and see if it'll work

must press both together.. no worries tho, sometimes i also missed it and end up adjusting volume instead

5 hours not enough?

its more than enough, considering with data + wifi in the graph..

average is 3 hours ++, 5 hours is quite awesome liao..

flash the .244 ftf using flashtool, but im not sure which version has root in it.. i think

------------------------------------
safest way: (is yours c6603 or c6602?)
http://forum.xda-developers.com/showthread.php?t=2387191

flash that 1 first (via flashtool.. read instructions), as once you are on .244 and with root + recovery (so basically you're safe)


after that just flash monx's zip files in recovery. (wipe data/cache/d.cache/factory reset)

------------------------------------
- after that dual recovery or recovery might be missing, so just follow this instruction:
http://forum.xda-developers.com/showthread.php?t=2335940

download: http://www.fun-industries.nl/xda/download....UFTRS53aW5kb3dz (sorry, download this one. if you've download the earlier one. pls download this)

(only try this if your recovery is missing, test it by rebooting then volume up when you see a green light)
sorry i cant guarantee if it'll bring back recovery as im not on stock rom anymore.

as long as you follow instructions, you'll ALWAYS be fine..

This post has been edited by mafioso: Aug 5 2013, 02:07 PM

if you want the safest way.. flash the stock one first

as once you are on .244 based, you no need to worry using whichever method you want to flash the zip
it'll always be:

1. enter recovery
2. wipe all necessary things (make sure you backup even before flashing the stock .244 tho, as everything will be wiped).. but wipe again when you wanna flash monx's zip.. (data/cache/d.cache/factory reset aka wiping system, not just wipe data)

3. flash the zip
4. reboot
5. done

----
and yes, according to the stock rom instructions, flash the zip first, then dont reboot, but power off, after that flash the .ftf (they should have instructions in the flashtool thread)

i think its:

- power off
- plug in the usb port from your phone first (but dont plug into the pc)
- prepare your finger with pressing + hold volume down
- then only plugin to the pc (ofcuz thats when you're running already flashtool with the screen telling you to power off/etc lah)

you got use flashtool before? if you haven, PLEASE install the drivers.. if you're on windows 8, they'll also got instructions on how to do it..

This post has been edited by mafioso: Aug 5 2013, 02:36 PM

i guess it would be the same

like i said, safest way = stock first, then custom rom (because you are jumping from .423 to .244, totally different base)

safest = stock first, custom second.

get the one from [nut] as they have recovery + root..

This post has been edited by mafioso: Aug 5 2013, 04:35 PM

you have to wipe it anyway
because you're jumping from a different base, flashing the .ftf = will wipe no matter what

im just providing the safest route to flash the rom.. its up to you which way you want to use

just double check to see if recovery still exists in monx rom after you wipe all..
if not try the dual recovery thing i posted up there.

thats great

btw got test to see if it has recovery?

thats great

always use the standard DPI provided by google if you duwan your playstore to be broken.

as for other apps -> 90% of the time it will scale accordingly, 10% of the apps might be broken (thats when you can adjust with the xposed app)

always use:

160 = LDPI
240 = MDPI or HDPI
360 = XHPDI (im using this)
480 = XXHDPI

however, you can also use 320 (no problem, just configure google play to 360 DPI (possibly you gotta configure "google service framework" as well to 360 DPI..see if that'll work) might need a restart to see the effects tho, clear cache/data for both of them too.. )

if it doesnt, set the main DPI as 360, then configure other apps smaller.

This post has been edited by mafioso: Aug 6 2013, 01:59 PM

yea, adjust it..
try 320,330 and 360 with 320x480 resolution.. i think one of them will fix it..

note: your call screen will be cut off too, so just search for Phone.apk or "Phone" and adjust it to 480 with 320x480..

but i tried adjusting before tho, then i gave up.. (for the dialer, not sure why it doesnt work for me)
so i just download "exdialer" from the playstore

but now i no longer have this problem as im on AOSP. everything just scales perfectly

why would u wanna hide? o.0

navbar is our main navigation.. without it phone is useless..

unless u have PIE, but PIE is on AOSP only, or u installed LMT launcher?

read about fast dormancy before. what does it do actually?

and if its like this means we wont be able to really use our alarms anymore?

so does it affects your data speed so far?
i might try it though, but not sure if its on AOSP rom

:: urgh sadly its not in AOSP based rom.. nvm lah

This post has been edited by mafioso: Aug 6 2013, 04:44 PM

it depends

if non of your port's white small paper turned blue = then most likely covered as its not your fault
if one of them turned blue = its your fault for not closing it properly

This post has been edited by mafioso: Aug 7 2013, 03:45 AM

Oh right.. pink!

https://play.google.com/store/apps/details?....autolock&hl=en

you can try this, im currently using it.. its pretty good, and wont randomly lock/unlock when you're using it on the bed

the sensor gotta be near an object for it to lock/unlock.. like very near

you can also set if you MANUALLY lock it, it WONT unlock (like sometimes when you really need it to be locked on the outside, it wont auto unlock )