yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] mysteriousmonkey29:
When I hit usb, if the device is plugged in, its info shows up after the second (indented) 1 in a box. For the mouse, it doesn't have anything under it. But for the keyboard, it has: #0 3:01:01 HID boot (checkmark). No #1 3:00:00 though.

With the keyboard, I went back to the main USB mode screen, and mashed the keys/pressed every key on the keyboard. Nothing on the nook changed, including the scan and key codes. They remained blank. I did notice that the num lock key lighted up the keyboard num lock indicator though, so I guess it's at least getting adequate power. Although this is only after restarting a plugging in and out a bunch of times because the cable/connection is a bit janky.

I do have /system/usr/keylayout/qwerty.kl, other files in that folder include: AVRCP.kl, TWL5030_Keypad.kl,gpio-keys.kl, and omap_tw14030keypad.kl

dmesg (from this location, if that matters) outputs more than a hundred lines, so I would prefer not to copy them word by word. What are you looking for specifically? Notable lines include:

[random #.random #] zforce-ts 2-0050 invalid_frame: 255

[random #.random #]usb 1-1: new full speed USB device using musb_hdrc and address 5

[random #.random #]usb 1-1: device v1038 p1361 is not supported

[random #.random #]usb 1-1: rejected 1 configuration due insufficient bus power

[random #.random #]usb 1-1: new low speed USB device usir

[random #.random #] regulator regulator, 5: enabling charge: USB HID v1.10 keyboard...

[random #.random #] usb 1-1: device not accpeting addresss 15: error -110

[random #.random #] usb 1-1: device descriptor read/64, error -110

[random #.random #] hub 1-0: 1,0 unable to enumerate device on port 1

Looks like it fails for various different reasons, seemingly dependent on the power source, restarting, and how carefully I plug it in.

Thanks again for all your help!
[Nook Touch General] Renate:
-110 is timeout on the USB, it seems to be flailing.

Did you try using a powered hub?

A "SteelSeries ApS Ideazon Sensei" keyboard?

How about trying a crappy $3 keyboard?

I'd like to know what the configuration descriptor is quoting for bus power, I've not seen that "rejected 1 configuration due insufficient bus power" before.

If you use Windows (or Linux), try UsbView.exe on it from the good folks at FTDI: http://www.ftdichip.com/Support/Utilities.htm

Here's a typical device:

Configuration Descriptor:
wTotalLength: 0x0029
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x04
0x0409: "Default"
bmAttributes: 0x80 (Bus Powered )
MaxPower: 0x32 (100 Ma)
[Nook Touch General] mysteriousmonkey29:
I tried the standard dell keyboard with a powered hub. It didn't even appear to recognize it unless I used the adapter cable again with external power (which makes much less sense now, because the hub is definitely powered--the num lock key was lighting up before attaching the hub to the adapter). When I did plug it in with the powered adapter (so I had dell keyboard-->powered usb hub-->usb to microusb with a separate microusb power input from the wall-->nook), it was recognized, but performed essentially the same (showed up under viewusb, but didn't register any inputs). I'm attaching a picture of what the viewusb came up with.

Additionally, I tried a really crappy old apple keyboard, which again was recognized, but didn't register input. Looking at dmesg, this error came up (I think) every time:

usb 1-1: new low speed usb device using musb_hdrc and address 7

usb 1-1: device v413c p2005 is not supported

So possibly I just have to use yet another keyboard? I don't have a steelseries keyboard--the steel series thing was the mouse I was plugging in.

I am additionally attaching the outputs from usbview on the dell keyboard and the crappy apple keyboard.
[Nook Touch General] mysteriousmonkey29:
Oops , looks like the usbview.exe output files didn't get attached. Here they are!
[Nook Touch General] Renate:
Mmm, something goofy is going on

<7>[ 387.083526] usb 1-1: default language 0x0409
<3>[ 387.093414] usb 1-1: device v04d9 p1503 is not supported
<6>[ 387.098968] usb 1-1: New USB device found, idVendor=04d9, idProduct=1503

Even though I copied qwerty.kl over:

-rw-r--r-- root root 3123 2012-04-15 10:20 qwerty.kl
-rw-r--r-- root root 3123 2018-04-04 20:23 Vendor_04d9_Product_1503.kl

Maybe the NST didn't use that system, G2 & G3 did.

In any case, my NST still works fine without a specifically matching kl.

Android supposedly looks in eight places for a match: https://source.android.com/devices/input/key-layout-files

If it fails it should fall back to qwerty.kl
[Nook Touch General] mysteriousmonkey29:
One notable thing is that when following the initial install instructions, I accidentally installed usbmode.apk before changing the boot files like you're suppposed to. The nook started giving me an "install failed" lock screen when it idled for long enough. I then realized the problem, switched the boot files, then reinstalled usbmode. Do you think that could be causing the problem? I could try factory resetting and starting over, although I'm not sure if it would help.
[Nook Touch General] Renate:
There shouldn't be any problem when you installed UsbMode.apk, it's only an app.

The NST's Eclair doesn't use /system/usr/idc like the later Android.

I renamed /system/usr/keychars and system/usr/keylayout to garbage.

When a keyboard is attached and twiddled it all acts as a home key.

Does the cap locks cause the cap lock light on the keyboard to go on and off?
[Nook Touch General] mysteriousmonkey29:
When connected correctly (which is getting harder and harder over time), the caps lock and num lock lights are both toggled by the corresponding keys. But the keyboard still doesn't seem to register at all on the nook--no key codes, no home button functionality, etc.
[Nook Touch General] Renate:
Does the soft keyboard work correctly?

It's a little bit more difficult to debug when you have the choice of either ADB or keyboard.

If you had a hardware console, a rooted terminal app or ADB over WiFi it might be easier.

This will dump out info as long as the keyboard was inserted and working once:

# cat /proc/bus/input/devices
...
I: Bus=0003 Vendor=04d9 Product=1503 Version=0110
N: Name="USB Keyboard"
P: Phys=usb-musb_hdrc-1/input0
S: Sysfs=/devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/input/input23
U: Uniq=
H: Handlers=kbd event3
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=7
...

There could be two interfaces.
[Nook Touch General] mysteriousmonkey29:
Yes, the on screen touch keyboard on the nook works fine. I actually do have an ADB Konnect app, and I think it works. I start it on the nook, type in adb connect 192.whatever on my computer, and it says it's connected. Just not sure what to type then; if I enter commands just like into the terminal app on the nook it looks for files and folders on my computer, not on the nook. Getting this to work seems like a good idea though; it would certainly be a lot easier than retyping all the really tiny hard to read output from the nook terminal app.

In the terminal app, cat /proc/bus/... produces the following output:

I: Bus=0019 Vendor=0001 Product=0001 Version=0003

N: Name="TWL 4030 Keyboard"

P: Phys=twl4030_keyboard/input0

S: Sysfs=/devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-004a/tw14030_keypad/input/input0

U: Uniq=

H: Handlers=kbd event0

B: EV=3

B: KEY=similar long #s

then same paragraph except replace twl keyboard with gpio-keys, and the various numbers change slightly

then same paragraph except replace gpio-keys with zForce Touchscreen

Notably, there is no line after the "B KEY=number" line in the first two paragraphs, but for the third one (the touchscreen),

there is the line: ABS=600000 3. Not sure if that's important.
[Nook Touch General] Renate:
You're not seeing the USB keyboard at all.

The TWL4030 is the 4 side buttons on the Nook (which are scanned directly by hardware).

The gpio-keys is the power and home button (which are handled by software).

The B:KEY is a bitmap of allowed scancodes.

My button box has 4 scancodes, 1-4 and B:KEY = 1e = 11110

If you got that while the keyboard was connected (and you can get the LEDs to toggle) then there's the problem.

After adb connect 192.XX.XX.XX you should type "adb shell".
[Nook Touch General] mysteriousmonkey29:
The adb part worked great! I can now debug from the computer, so I should be able to copy the full output of long logs for you from now on.

I didn't realize that you wanted me to connect the keyboard while running that command (I thought you meant if it had been connected before it would be ok). I will try it again with the keyboard connected.
[Nook Touch General] mysteriousmonkey29:
Ok, here's the output of the cat line from wireless adb, after successfully connecting the keyboard with the powered adapter. I checked that num and caps lock keys were lighting up the indicators immediately before inputting the line.

I: Bus=0019 Vendor=0001 Product=0001 Version=0003
N: Name="TWL4030 Keypad"
P: Phys=twl4030_keypad/input0
S: Sysfs=/devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-004a/twl4030_keypad/in
put/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=10800000 0 0 0 0 0 0 0 40000800 0 0 0 1

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input1
U: Uniq=
H: Handlers=kbd event1 as3676
B: EV=3
B: KEY=100040 0 0 0

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="zForce Touchscreen"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=event2
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=600000 3

I: Bus=0003 Vendor=413c Product=2005 Version=0110
N: Name="DELL DELL USB Keyboard"
P: Phys=usb-musb_hdrc-1/input0
S: Sysfs=/devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3 as3676
B: EV=120013
B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
[Nook Touch General] mysteriousmonkey29:
also, attatched is the (almost) complete output from dmesg. the command prompt stopped letting me scroll up (might have gotten overloaded by the amount of text), so it's cut off at the top, I don't know how much.
[Nook Touch General] Renate:
Your dmesg is a train wreck!

You should not be having crashes.

Put the Dell keyboard aside. It's quoting 100 mA which may be the problem.

Use the Apple or another keyboard or even a mouse.

Use a powered hub until you get things working.

Your next experiment: If you find your keyboard in /proc/bus/input/devices, look for the event#.

Then:

cat /dev/input/event# [color=red]<- whichever number it is, event2 or something[/color]

Then twiddle keys, you should get a burst of garbage with each key.

Does your OTG adapter work on other things, your phone?
[Nook Touch General] mysteriousmonkey29:
OK, I attatched a newer keyboard (logitech K120), through a powered hub. I tried the cat line with the event number, and pressing keys produced garbage output, just like you said! However, the keyboard still doesn't seem to provide any input to the nook. Also I retested the non-externally-powered otg adapter (because it seems like it should have enough power now that I'm using the usb hub), but it still doesn't do anything.

I'm not sure what you mean about using the otg cable with other things. Like I wouldn't expect my phone to know what to do when I plug a keyboard into it through the adapter. I tried this (with the externally powered one), and the phone did start to charge. But it didn't do anything else.
[Nook Touch General] mrbryan:
Did you figure out the "install failed" when it sleeps issue? i have two NST that I cloned i thought way back, i can't remember even how I rooted them it's been so long. But one of them does this, and it's super annoying. It's about to sleep but instead it reboots then tries to install something and fails. Requires reboot.
[Nook Touch General] mysteriousmonkey29:
No, never fixed this. I bet I could fix it by wiping the nook, re-rooting, and re-installing usbmode, etc. (in the correct order this time), but that's a pain, so I would prefer not to unless necessary.

Although maybe we are headed in that direction.
[Nook Touch General] mysteriousmonkey29:
Any other ideas?
[Nook Touch General] Renate:
Actually, quite a few phones work with OTG.

I've used a Moto E4, Nexus 7, Nexus 9 and of course the NST.

It still sounds like you have some major problem with the input subsystem.

Try

# dumpsys input

That gives you a lot of info from Android's perspective (vs. the hardware/Linux side of things).
[Nook Touch General] mysteriousmonkey29:
Well, that's interesting. I plugged a keyboard and then a mouse into my phone through both adapters, and they worked perfectly! I didn't even have to use a hub, or external power, or anything. Very interesting.

I have to run right now but I'll let you know what dumpsys input does later. Thanks!
[Nook Touch General] mysteriousmonkey29:
Actually, I think I've decided to give up. This is turning out to be a lot more difficult than I expected, and I don't see an end coming soon. I appreciate everyone's help though, and sorry to bail!
[Nexus 6P Q&A, Help & Troubleshooting] Mamodsh:
Hello everyone,

Here same nexus 6P bootloop problem with locked bootloader and no enable oem to unlock it.

I remove emmc chip from board and detect it to pc by emmc tools.

Now how can use emmc to unlock bootloader or write dump from unlock another one or where can get oem file in emmc ?
[Nexus 6P Q&A, Help & Troubleshooting] Mamodsh:
Here image from inside emmc

https://image.ibb.co/ieAsVS/1.jpg

https://image.ibb.co/dkBzAS/2.jpg

https://image.ibb.co/iaO1Pn/3.jpg
[Nexus 6P Q&A, Help & Troubleshooting] Duumon:
I can give a full backup with the unlocked loader
[Nexus 6P Q&A, Help & Troubleshooting] Mamodsh:
This full backup tested or not ?

There any way to enable OEM or unlock without backup ?
[Nexus 6P Q&A, Help & Troubleshooting] Duumon:
yes, tested. After installing the eMMC your bootloader will be unlocked
[Nexus 6P Q&A, Help & Troubleshooting] Mamodsh:
How can get this backup?
[Nexus 6P Q&A, Help & Troubleshooting] Duumon:
in PM
[Nexus 6P Q&A, Help & Troubleshooting] moshu_fc:
Check out !!!!: https://www.xda-developers.com/googl...reo-brick-fix/
[Nexus 6P Q&A, Help & Troubleshooting] bedgja:
can you give me the link in pm??

i still in the same problem,locked bootloader and bootlooping :(:(:(

thank you very much
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
​

Resurrection Remix Oreo​

What is Resurrection Remix?

Resurrection Remix the ROM has been based on CM, slim, omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device

Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!

Special thanks to, the CM team, OMNI team, SLIMROMS, SaberMod and of course to all the supporters

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Downloads:

Resurrection Remix

Latest link for RR Wt88047

Gapps

TWRP (use Redwolf Recovery or Official Recovery or TWRP 64 bit by pirej)

TWRP version 3.1.0 or more is required to flash this ROM

To get everything working flash this boot image over here ( wipe dalvik and cache)

Headset and volte fix

Things Needs to be fixed

1) Audio FX needs to be turn off for a proper audio output (you can flash Viper4Android as a Magisk Module to fix this)

Instructions:

First time flashing Resurrection Remix on your device, or coming from another ROM (e.g. MIUI)?

WARNING: This procedure will factory reset your device! Accounts, applications, settings, etc will be lost!

Download the file Resurrection-Remix-O-vXXX-XXXX-wt88047.zip to your phone from the links below

Download the file open_gapps-arm-8.1-pico-xxxxxxxx.zip to your phone from the links above

Reboot your device into Recovery mode by holding PWR+VOL-UP

Format userdata, cache and dalvik cache

Install both the ROM and the GApps zip files

Reboot

Upgrading from earlier version of Resurrection Remix?

Download the file Resurrection-Remix-O-vXXX-XXXX-wt88047.zip to your phone from the links above

Reboot your device into Recovery mode by holding PWR+VOL-UP+VOL-DOWN

Install the ROM zip

Reboot

Special mentions:

- Special Thanks to Resurrection Remix team

- balika011 [Open Source Kernel]

- Kumajaya [ex?CM maintainer]

- nicknitewolf [Current CM/LineageOS Maintainer]

- Zwliew [Important Fixes]

- Premaca [Initial N Tree's and for adapting Xiaomi Kernel Source]

- Cyanogenmod

- AOSP​

Deviec Sources:

Device

kernel

vendor

My git:

https://github.com/karthikkm007

XDA:DevDB Information

[ROM][VOLTE][Redmi 2][OFFICIAL][8.1.0][10/12] Resurrection Remix 6.2, ROM for the Xiaomi Redmi 2

Contributors

karthik km

Source Code: https://github.com/ResurrectionRemix

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Lolipop and TWRP 3.2.x

Based On: LineageOS

Version Information

Status: Stable

Current Stable Version: 6.2.1

Stable Release Date: 2018-12-10

Created 2018-03-28

Last Updated 2019-06-01
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
New Build is Live ! 03-04-2018

1) OMX fixed (as I tested with Instagram)

2) this build is because of previous one is buggy

4) AudioFX is still buggy ( need to fix )

5) Live display not working ( no need to report this)

New Build is Live ! 10-04-2018

What's New

1) April Security Patch

2) Android tag_r20

3) More features ( check change log after flash)

Fixed things

1) Live Display

2) Home screen Widget

New Build is UP ! ( 08-05-2018)

1) Now you don't required ( any zips )

2) volte and headset is working fine

3) Signature Spoof added

4) More features and

New Build is UP ! ( 29-05-2018)

1) Source sided improvement
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
Check Screenshot Tab to see Screenshot

Fixed in latest build ( 8.5.18)

1) volte and headset

2) Permission manager FC ( on using Black theme)

New Official Builds Change logs

Can be found in device only

One New Kernel update

This kernel can be flashed on any oreo ROM

What's included

1) Zram Tweaks over excalibur kernel

Confirmed Zram working

Flashing Procedure

1) Reboot to recovery

2) Flash kernel

3) wipe Cache

4) Reboot

Download

SpaceX-Kernel

New SpaceX-kernel update with 512MB working Zram

Download

Space-X

Flashing Procedure

1) Reboot to recovery

2) Flash kernel

3) wipe Cache

4) Reboot
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] Superraju:
Omg! Tnx dev.

Now its confusing which one will be better?? rr oreo or aokp. Have to test both?
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] Guilhermerara:
Redmi 2 boot loop
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
Clean flash it again

I'm still using it

No boot loop or no reboots till now

At first boot just try

ROM +Gapps
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] muralirj:
Any bugs?
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
One in stated in op (not a big problem) (workaround available)

And 2nd obviously OMX
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] babu407:
my first question is can i use it as a daily driver...? if yes what is this omx bug.? and is there any earphone phone bug.? which one do u recommend aokp or rr..?
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] fallenguy98:
Maybe he got boot loop because of twrp 3.0.2? Right?
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
You could be right
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
There is no earphones bug ( if you turn off audio fx or flashed viper4android)

OMX is videos not playing on social apps like WhatsApp , Instagram etc

But videos are playing on such apps like MX player etc

So this bug exist on all Oreo redmi 2 build I think

And this will be fixed soon
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] fallenguy98:
Is YouTube videos working bro?
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] babu407:
which one do u recommend for daily driver aokp or rr.? and which recovery you used for flashing rr..? present iam on aokp..
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] fallenguy98:
I used for flashing twrp 3.2 for flashing RR as when I flashed with twrp 3.0.2 gapps didn't worked
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] Shivpremi:
Trying :D
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] tearex:
delete
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] ishuya:
For Gapps

Rom based on ARM or ARM64?
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
May be both will be stable soon

Wait for it
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] optimus_blade:
Yes...one jio and other airtel 4G..
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] redmi2prime:
I am having similar SIMs. Jio & Airtel 4G and LTE vanished once for all. I have submitted logs as asked by Karthik but that was different ROM but all ROMs have this issue except https://xdaforums.com/redmi-2/development/rom-nx-rom-r11-1-t3665705 this ROM.

With this LTE date and Volte calls also working, similar like MIUI, but this has another issue of Jio calls chopping and very low signals for Jio.

I hope Karthik able to find the issue.
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] optimus_blade:
Good to hear that someone here has the same issue..i thought only i hv this problem. I hv also submitted log here. ..lets see ...i m hoping Karthik wud figure it out.... Despite this i m using this rom....its best ..
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] Chefcrisp:
Delete
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
New Offcial Build is UP 12-06-2018

Changes:

1) Latest Android Tag r30

2) OTA support implemented (you will be notified whenever new build is up)

3) Some lags fix

4) Source sided improvement

5) June Security Patch

6) And more, Flash and check

** Check full Changelog in ROM **

Download Offcial Resurrection Remix

Remix
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] optimus_blade:
Installed. UI seems smooth. More feedback in some time.

karthik any workaround for LTE disappearance issue? That would be of a great help.
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
Flash latest firmware from LOS Thread

If it didn't help provide me modem logs
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] optimus_blade:
I searched the LOS thread here and couldn't find the firmware. Can anyone help me locate it. I will try that today and revert.
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] chaosp:
Any chance to install it on a wt86047 device?! I saw success reports here in the thread (e.g. in #139), but I get the following error message when I try to install it from TWRP 3.1.1-0 (linked also there):

"E3004: This package is for device: HM2014811, HM2014812, HM2014813, HM2014814, HM2014815, HM2014816, HM2014817, HM2014818, HM2014819, HM2014820, HM2014821, HM2014112, wt88047, wt86047; this device is ."

BTW:

Right now there is a LineageOS 14.1 on it.
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] fallenguy98:
change the twrp to 3.2 redwolf or any.other u like
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] bikramacdc:
Almost there!!!!

[MENTION=6429574]karthik km[/MENTION] Thank you so much for the official rom. It became almost perfect. It has improved a lot in terms of lagginess, but still there is lag which I cannot go away with it even if I use performance mode of cpu governor. There is little bit heating issue also. There is one major bug, that is Compass, it is totally messy and completely broken. No matter how I tried it couldn't be calibrated hence do not work at all. A fix will be highly appreciated. Otherwise it is good rom for use as daily driver.