Kinda weird ... using CM10.1 nightly (4.2.2) + franco r82 kernel and getting very low score on antutu than when I was on CM10.1 (4.2.1) + franco r72. Maybe its not yet optimized?

Crap...with 4.2.2 I am still getting only 2hrs on screen time with 3G.

Do I got a faulty battery???

Getting worried. Any advice fella comrades?

Appreciate some advice based on my BBS below..

Need help to decipher the readings as I am pure noob...

cowithgun

bro, do you have 4.2.1 bootloader version zip file?

nope. i dont use zip created by others.

you can flash the boot loader directly:

1. download the stock image: https://developers.google.com/android/nexus...ages#occamjdq39
2. open with 7zip, extract the bootloader

3. flash it

fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz10o.img

ic sorry. mis-understood u. i tot u said zip. that is image file.

fastboot flash update ota.zip --(i renamed the zipfile)
sending 'update' (52274kb)...
okay [3.270s]
writing 'update'...
FAILED (remote: partition table doesn't exist)
finished. total time: 3.272s

download the stock kernel provided in this xda thread http://forum.xda-developers.com/showthread.php?t=2145848
flash it then clear cache and dalvik cache
reboot and try update again

which ota.zip u using? if the one directly from google should use:

http://android.clients.google.com/packages...0D.de8b8d10.zip

"'adb sideload update.zip"

careful with those command... mess up bootloader partition, u ll get hardbrick

ps: i notice your filename has space "update ota.zip"... dont use space.

yup, that was the stock kernel.

if u use that zip, correct command should be:

1. adb reboot recovery
2. adb sideload ota.zip

http://forum.xda-developers.com/showthread.php?t=2145848

if ur adb cannot see your device in recovery, you need the universal driver, or manually edit the android_winusb.inf to include the hardware id.

adb sideload first intro after jellybean, u may wanna update your adb.

glad u got it sort out

b38 is out, some fix for gamma interface in b37.

motley has reverted back to b32 colours though since they were a few that didnt like it. time to put that colour script in data/local/userinit.d 

which colour setting are using now?

haha are you sure? it is very noticeable from b35 to the newer one. quite washed out la now. haha i revert back to b35's colour here just look for the file inside the zip, it should be under system

jazzboys ones are here

i know sophan is using the visceral's one.   hehe i haven't had time to try it yet. I just use scriptmanager to test between motley's b35 colour and the halfbreed, then put the file in /data/local/userinit.d with permission rwxr-xr-x that should make it stick in between flashes if you are using a nightly rom etc. remember the permission though
lol, that site was just trying to push for traffic. thread is closed anyway
nama pun hotspot! 

Yeap, copy the files inside the zip file, 91rgbgammaPA to that folder. Then set the proper permission via your file manager. Most file manager supports this.

flashable but it won't survive a nightly flash since it is in /system

Yeap, create the folder, i had to create mine as well. You can check whether the userinit.d is supported by going to /system/etc/init.d there should be a file called 90userinit this tells the phone to execute the scripts in /data/local/userinit.d on boot.

Since it is in /data, you won't lose it when you are updating your ROM.

refer my previous posts t for the correct permission of the script in userinit.d.

user - read write execute
group - read write execute
other - read write execute

refer first page

Tick all, then untick write column for 'group' and 'other'. That should give you the correct setting. Check the values afterwards.