yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] locutusx:
i thought that the google play store is "locked" to the country of the firmware?

so if you put a Singapore firmware on, you get .sg's play store, which may be missing apps that are in the USA play store, etc.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] tangcla:
I believe - and I could be wrong - the Play Store region is based on your Google account.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] milkk:
What does the Open Line mean on the new Philippines (Open Line) firmware?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] tangcla:
I think it's a telco in Philippines.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] notalent-assclowns:
Except for the LTE model (SM-T325) of course.

Edit: Sorry, I'm an idiot and didn't realize the link only had the firmware for the wifi version.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] milkk:
Ah ok. As I was searching I also found this article (link below) and tons of Philippines openline (open line) videos/posts etc so it seems a lot of mobile stuff in Philippines are locked. Not sure why a wifi tab would be locked in the first place that it would need to be open lined.

http://www.ehow.com/how_6076987_open-line-cell-phone.html
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] locutusx:
So you used NG2 from sammobile right?

Which one - Singapore or Phillipines?

Also, I noticed there's an NF2 (unknown region) and NF3 (UK region) - has anyone tried those?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] tangcla:
NG2 Singapore for me, from SamMobile. I didn't notice a UK NG, I would have preferred to use that one if it was available.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] nkolsen:
I'm coming from a NF3 UK, and didn't really see any difference. Going to try the NG2.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] milkk:
I'm on NG2 Singapore from the NF3 UK everything works still except i had one extra app some Line Phone/voice app hehe. Which I deleted so I re-rooted after install.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] milkk:
Singapore because I got Line voice calling app on my device when I installed the Singapore NG2 firmware.
[G3 General] arnonrgo:
SDKs for QCircle case, QSlide, QRemote etc.:

http://www.androidcentral.com/lg-opens-quickcircle-sdk-developers
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] tcatut:
I just had to replace my S4 because I broke the screen on my old one. Unfortunately, the new one was shipped to me with NAE firmware and boot loader already installed. This means I'm already on KNOX from the first second of turning it on.

I have seen plenty of guides on how to update to NAE, and get root, etc. by not allowing KNOX to installed. However, I haven't really seen anything about what can be done if it's already installed. There's things scattered all over the net that suggest there might be ways around this, but nothing on the forums here that I have been able to find yet.

I'm not looking to flash any crazy roms or anything right now, I really just want root, but it seems like even that might be impossible now. Could I use something like "DrKetan Multitool" to "DeKNOX" my device and then root it? Does this tool even work on the S4, he claims it does but I've not seen it mentioned on the actual S4 forums. Any advice would be greatly appreciated. Note, I am looking for a method that doesn't trip the flash counter; or at least allows a reset afterwards. I'd rather not void the warranty on a brand new device if possible.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] btoddweber:
http://xdaforums.com/showthread.php?p=53166571

Try this...it is a custom ROM but really close to stock
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] tcatut:
I was already planning on installing UnknownForce Stock Rooted NAE Rom, if it's possible. However, you didn't really answer my question. Is there a method to bypass/kill the KNOX boot loader at this point or not? If not, then I might as well just stop now. I'm not prepared to void the warranty at this point.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] frostedunit:
No. Once you have Knox, you have it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] bruteoutlawz:
Anyone tried the new 104mb update that just come out, says it adds ui improvements and stability. Also adds kid mode.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] simacca:
Installed it earlier. Haven't really played with it that much yet. Still can't get rid of the magazine ui though. Seems OK to me so far.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] locutusx:
but you guys know you can really minimize the impact of MagazineUX by removing all but one of the "magazine home pages", and then putting only ONE widget on the last remaining page (something low on resources; like Calendar!).

When I did that (removed all magazine pages except for 1, and only had 1 widget (calendar) on the last page) I no longer noticed any UI lag. I was pretty happy with it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] simacca:
That's what I did, but would like the option to disable it like I can on my s5.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] bruteoutlawz:
I like the MagazineUX, i haven't had any lag, maybe a few stutters but that's disappeared since the last 2 updates
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] simacca:
I don't get any lag with it anymore. It just feels dis-jointed compared to the rest of the experience. Would also of liked a screen mode option so I can turn down the saturation.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] macioh:
could someone post a build number after flashing the update?

Wysłane z mojego SM-T320 przy użyciu Tapatalka
[Galaxy S III Q&A, Help & Troubleshooting] jegze:
After replacing broken lcd screen my phone wont recognize the sim card anymore. Sd card works fine and as far as i know sd and sim card slots are connected with same ribben cable to the mainboard, so I think this is'nt hardware problem? Anyone know anything i could try to make it work again? Thanks
[Galaxy S III Q&A, Help & Troubleshooting] eskorpiao112:
Did you replace the lcd screen for yourself? If you sended the phone to a repair shop, you should send it again.

Enviado do meu GT-I9300 através de Tapatalk
[Galaxy S III Q&A, Help & Troubleshooting] jegze:
Replaced by myself
[Galaxy S III Q&A, Help & Troubleshooting] tallman43:
Simple way to test is flash a stock rom with odin if problem still there it is hardware fault ;)
[Galaxy S III Q&A, Help & Troubleshooting] jegze:
Phone imei has disappeared, could that mean its only software problem?
[Galaxy S III Q&A, Help & Troubleshooting] tallman43:
Yes could be a efs issue take a look here >> http://xdaforums.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289 <<
[Galaxy S III Q&A, Help & Troubleshooting] haydonraffles:
Most likely. What did you do before replace the sim? You may try to restart the phone and see whether it works.
[Micromax A116] neomanu:
*** Disclaimer

I/XDA is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!

Featues :

Bugs :

Versions :

There are 3 versions available, with everything similar but different GPU clocks :

1. GPU @ 286 MHz (for those who face problems with OC version)

2. GPU @ 312 MHz (slight OC)(for those who want little more performance than stock)

3. GPU @ 403 MHz (OC version)

Download :

NeoKernel_v1.5_GPU-286MHz.zip

NeoKernel_v1.5_GPU-312MHz.zip

NeoKernel_v1.5_GPU-403MHz.zip

Installation :

Source :

Original : https://github.com/kashifmin/KashKernel_MT6589

Modified : https://github.com/neomanu/NeoKernel-MT6589-A116

FAQ :

Credits :

[MENTION=4917631]kashifmin[/MENTION]

[MENTION=4176821]bindassdost[/MENTION] (for porting s2w and dt2w to mtk)

[MENTION=3332811]faux123[/MENTION] (for Powersuspend, Dyn Fsync & Intelli_plug)

XDA:DevDB Information

NeoKernel, Kernel for the Micromax A116

Contributors

neomanu, kashifmin

Source Code: https://github.com/neomanu/NeoKernel-MT6589-A116

Kernel Special Features:

Version Information

Status: Stable

Current Stable Version: v1.5

Stable Release Date: 2014-12-26

Created 2014-06-10

Last Updated 2014-12-26
[Micromax A116] neomanu:
Reserved

Changelog :

v1.0

Initial Release

v1.1

1. Updated to kernel 3.4.93
2. Made 2 versions :
2.1. GPU standard clock version (GPU @ 286 MHz)
2.2. GPU OC version (GPU @ 403 MHz)
3. Screenshots updated
And the numbers are looking pretty good

v1.2

1. Updated to kernel 3.4.94
2. GPU : Replaced 286 MHz version with 312 MHz
3. Enabled F2FS (was disabled before)
4. Added exclusive Sweep2Sleep (see post #3)
5. Fixed DoubleTap2Wake
6. Enabled DEBUGFS and Tracing (see post #3)

v1.3

1. Updated to kernel 3.4.96
2. GPU : Added back 286 MHz version
3. Added Intelli_plug driver (see post #3)
It was exclusive to Qualcomm devices earlier,
but is now available to all ARM devices
4. Added, updated and enabled SIO & BFQ I/O schedulers
5. Enabled CONFIG_SCHED_AUTOGROUP
6. Numerous fixes (see Gitbub commits)

v1.4

1. Updated to kernel 3.4.103
2. Bluetooth components now built-in, not external modules
3. Makefile : Use -mcpu=cortex-a7 instead of -march=armv7-a
4. UKSM : Disable by default
5. Updated UKSM
6. Hotplug : Use Intelli_plug by default instead of MTK mechanism
7. Updated Intelli_plug
8. Tuned CPU governors : Intelliactive, PegasusQ, Nightmare, SmartassV2
9. Enable Quad-core stats
10. Set SmartassV2 and SIO as default schedulers
11. Added init.d support
12. Numerous fixes (see Gitbub commits)

v1.5

1. Updated to kernel 3.4.105
2. Bluetooth components compiled as external modules again, solves bluetooth errors
3. Set Hotplug as default CPU scheduler again
4. Added Multi-core scheduler support
5. Numerous fixes (see Gitbub commits)
[Micromax A116] neomanu:
Reserved

Kernel Controllers :

For Sweep2Wake, DoubleTap2Wake, LED Control, Dynamic Fsync & Intelli_plug :

Trickster MOD Kernel Settings

(Recommended)

For Powersuspend(w/ Mode selection), Dynamic Fsync & Intelli_plug :

Faux123 Kernel Enhancement Pro (FauxClock) by [MENTION=3332811]faux123[/MENTION]

Manual Control :

UKSM :

Disable :

echo 0 > /sys/kernel/mm/uksm/run

Enable :

echo 1 > /sys/kernel/mm/uksm/run

Intelli_plug :

Disable :

echo 0 > /sys/module/intelli_plug/parameters/intelli_plug_active

Enable :

echo 1 > /sys/module/intelli_plug/parameters/intelli_plug_active

Touch Boost Disable :

echo 0 > /sys/module/intelli_plug/parameters/touch_boost_active

Touch Boost Enable :

echo 1 > /sys/module/intelli_plug/parameters/touch_boost_active

S2W/S2S :

Disable :

echo 0 > /sys/android_touch/sweep2wake

Sweep2Wake only :

echo 1 > /sys/android_touch/sweep2wake

Sweep2Wake + Sweep2Sleep :

echo 2 > /sys/android_touch/sweep2wake

Sweep2Sleep only :

echo 3 > /sys/android_touch/sweep2wake

DT2W :

Disable :

echo 0 > /sys/android_touch/doubletap2wake

Enable :

echo 1 > /sys/android_touch/doubletap2wake

Note :

Sweep2Wake & DoubleTap2Wake increase battery use.

Sweep2Sleep has no effect on battery use.

DEBUGFS :

mount -t debugfs none /sys/kernel/debug

ROM Makers :

Feel free to include this kernel in your ROM if you wish to,

but don't forget to mention me.
[Micromax A116] malick186:
First reply

Finally a new kernel! :victory: I am running CM11 v0.7. Can i flash it directly??? And wait a minute! where is the download link??? :confused

Edit: Found the downloading link its in the download Tab. :D Kindly add it on the main thread :angel:
[Micromax A116] darshan dazzGeEk:
Does it work on cm11?
[Micromax A116] malick186:
Just flashed it over cm11 v0.7 it stucks at cm logo! Tried to revert back to KashKernel v2.7 but still stucks at the logo! restoring my nandroid backup now! :D
[Micromax A116] darshan dazzGeEk:
Change ram-disk n try
[Micromax A116] malick186:
Can you do it for us plz plz! :angel: I dnt know how to do this! but waiting eagerly to try this kernel on cm11 bcoz its Linaro GCC 4.9.1 :D
[Micromax A116] Sk.D:
[MENTION=3911074]neomanu[/MENTION] : Good work, Appreciate it!!!!!:good::good::good:

and [MENTION=5070303]malick186[/MENTION] I can do it but I need both the boot.img files, Could you or [MENTION=4991113]darshan dazzGeEk[/MENTION] upload it
[Micromax A116] gregferns:
You need this from the flashable zip file or will itdo from the installed rom ??

Also will there be 2 boot.img files ???

Edit : sorry about that.. i realised my noob question... boot.img will always be flashable right...

Edit 2 : I found only 1 file in the cm zip flashable.
[Micromax A116] GroovyG:
Great job! None of the bugs of previous kernels are present, runs very smoothly. Definately keepers for now :thumbup:
[Micromax A116] gregferns:
which rom are you running it on please ??
[Micromax A116] GroovyG:
My own pretty much :D

I used a european 4.2.1 stock ROM and removed everything I didn't need. This kernel runs flawlessly with it.
[Micromax A116] pradeepjoshua:
Brings down nenamark score to 27....on sldv2
[Micromax A116] Sk.D:
Please any one try this on cm11 rom. I have changed ramdisk with cm11. Flash it. Remember to take backup first

Download Link :

Neo-kernelv1.0Cm1Ramdisk
[Micromax A116] malick186:
Its working i tried on cm11 v0.7 . thanks alot for replacing the ramdisk! :thumbup:
[Micromax A116] smustafasms:
after flashing this kernel my camera is not working. dark greenish
[Micromax A116] gregferns:
Let me know if you changed governors etc and are getting good battery life...

thanks
[Micromax A116] smustafasms:
sk.d sir, i m using this kernel but my camera is dark greenish. as i know it is ramdisk issue. plz help me if possible. i have windows pc. dont have linux
[Micromax A116] malick186:
After using couple of hours on cm11 finally realized that camera is not working giving me error "cant connect the camera" and i think gpu is oc by default! Since my device is based on old hardware so its decreasing the performance i hope op will release the default gpu modules soon for this kernel.

Overall it gives me a smooth experience but reverting back due to above problems. :thumbup:

Thanks again bro for building kernel for our device! :D
[Micromax A116] vismaiy:
Starting ADB...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connect phone...
ADB shell...
shell@android:/ $ su
su
root@android:/ # grep -i "cam" /proc/kmsg | tee /sdcard/camera.log
grep -i "cam" /proc/kmsg | tee /sdcard/camera.log
sh: tee: not found

This is what i get.
[Micromax A116] seb3773:
initd support ?

Great work, but no initd support ?
[Micromax A116] neomanu:
I suppose it does have. But I haven't gotten around to testing it. Maybe you could do the same and let me know?
[Micromax A116] seb3773:
No, It doesn't have initd support, I have made the test. Not a real problem, it's possible to use Uni-init v1.0.apk (universal initd support) and it works.

But I'm facing the same greenish problem with the camera (stock app), and another problem with all the apps who are using camera (qr droid, camera zoom...): although it's possible to take pictures, there is no image displayed in the app (but the picture taken is okay, can see it in the galery). And it's not possible to switch to frontal camera in these apps. I tried to delete datas, reinstall, but no luck.

Too bad, because the performances are very very good... Don't hesitate to ask me logs or everything else if I can help. With correct camera support it will be a killer kernel ^^

ps: sorry for my bad english...

ps 2: forget to say, my device is a "wiko cink five", french version of the a116
[Micromax A116] pradeepjoshua:
Apps like TOI and groupon keep force closing...anything to do with kernel ?? On sldv3
[Micromax A116] neomanu:
Could be the ROM or Xposed. Try seeing the logs for more information.
[Micromax A116] GroovyG:
[MENTION=244186]seb[/MENTION], that's not a kernel issue, it's the ramdisk. I had the same issue plus some others, so i used the kernel with a stock T5 ramdisk and that solved all the issues. So use a stock cinq five ramdisk and see if that does it for you as well.
[Micromax A116] neomanu:
Added support in ramdisk.

Will be available in next release.
[Micromax A116] seb3773:
Well, I'm using a stock rom on my cink five, so I thought the ramdisk is "stock" ?

And the camera IS working (I can take pictures with it), but the problem is I can't monitor the image on screen (black area instead of the camera picture, in every apps using it, except stock camera, but this one with a greenish image)
[Micromax A116] GroovyG:
Nope, the ramdisk is part of boot.img

There is a link to a tutorial on how to change it in one of the first posts though.
[Micromax A116] seb3773:
Ok, I tested with my stock ramdisk (unpacked the two boot.img files and replaced the ramdisk in the new boot.img with the stock one). I added initd in the same time, works well :)

So, it solved the stock camera "greenish effect", (but the frontal camera is always unavailable) but not the problem I mentionned with all the other apps using the camera function :(

In fact the image of the camera in these apps appears just at the opening, during less than one second, then a black screen... And there's another flash when I switch from one app to another. But they can use the camera function, take pictures, scan a barcode... without diplaying anything.

Feel free to ask me any ather informations if needed. It's not so far from perfect, only this annoying bug :)
[Micromax A116] GroovyG:
That's interesting and strange at the same time.

Just to clarify again, everything works fine in the default camera app, but not in any third party apps using it?

Have you installed anything that might tamper with the basic camera app, like the 4.3 camera i've seen floating around here? Just asking because our camera hardware is different from A116, and you may inadvertently have messed up some libs by installing A116 cam software.
[Micromax A116] seb3773:
I find it strange too :p

To clarify:

-- everything works fine in the default camera app <--- Except frontal camera (doesn't appear, no selection possible to switch to it)

-- in any third party apps using camera: No image displayed (well, image displayed at a fraction of second at the start of the app, then black screen) but I can take pictures, etc... In blind mode :p

(This is with my stock ramdisk, without it, the stock camera has the greenish effect).

Didn't see other problems, performance is very good. But had to revert to my nand backup because I need the camera, and not only with the stock app :-/ )

- Everything is stock, no 4.3 camera app.

- Android version: 4.1.2 (cink five stock rom, kernel 3.4.5, build ALPS.JB.SP.V1)...
[Micromax A116] GroovyG:
Ok, really weird then, I have no explanation for that :confused:

But your stock rom is a 4.1, not 4.2, don't wiko offer one? You could try the T5 stock rom, I think we have absolutely identical hardware. I use that with the P18 baseband and this kernel, totally flawless package :cool:
[Micromax A116] vismaiy:
For me, the front camera works perfectly but the back camera doesn't! Using stock 4.2.1. Other than that the kernel is perfect!! :)
[Micromax A116] neomanu:
That's not a "bug". Can't be fixed. That's just the way things work. I'm surprised you noticed that only for Powersuspend.

Since, governor, i/o scheduler, s2w, dt2w, fsync all work in the same way. All these values revert to default at boot.
[Micromax A116] deepesh.tickoo:
Use 'set on boot' option for kernel related settings, features and all that stuff!

Kernel settings are supposed to revert back after a reboot, but the 'set on reboot' option re-change the kernel settings just after the reboot.
[Micromax A116] Viggen66:
Lg is using one new feature similar to DoubleTap2Wake, Knock Code, it´s almost a copy of this feature
[Micromax A116] eagledipesh:
HEY neomanu :), please check this post http://xdaforums.com/showthread.php?t=2698984 by [MENTION=5238428]superdragonpt[/MENTION]

Lots of optimization done.

Please check if its usefull for out device kernel
[Micromax A116] superdragonpt:
Well you have mention my name and now im here...

@ The OP :

You should remove that missleading thread title...

This is NOT 3.4. 96 kernel version ( not even close )

Not sure what you want to acomplish with this, but OK.

--> The best features in "your kernel" are ported from another kernel ( your using kash kernel as base )

--> Also you've added useless junk ... that only increases The kernel footprint.

Not an rank, just an heads up...

Why not starting from your device clone kernel source ( WIKO ) and starting building your own kernel from scratch ?

Regards
[Micromax A116] neomanu:
Firstly, love your work!

Secondly, it's not like I stole anything. I mentioned in the very first line that the KashKernel was the base.

About 3.4.96, I applied every single patch manually, so there can be no doubt about it. Can't think of a reason why you would say that.

Next, all the 'useless junk' is optional, disabled by default. Users are free to turn them on, if they want.

But also, your advice is good. Really thinking of starting over.
[Micromax A116] eagledipesh:
I dont know anything about kernel version, we all know you are doing an awesome work with kernels, so keep it up, but what will really help a116 community is by providing a kernel with minimal footprint and better battery life, i know under clocking is not an option for MTK devices as of now but there some battery tweaks incorporated by him, please check that out. 99% to 0% in 7.5 hours that the how this phone consumes battery with no usage, only WIFI and network on.

If you have patch 3.4.96 manually, then its really an awesome job. :good::highfive:
[Micromax A116] superdragonpt:
Hi

I didnt want to made an wall of text.

I know you merge 3.4.9x commits (cherry-pick) and i know you gave credits to Kash ( thats fine and its The way to do it).

Question here is Kash kernel is based at 3.4.0 - 3.4.5 , MtK stock kernels " 3.4.5" are fake!( nothing more than 3.4.0 with an few commits from 3.4.5)

You'll need to remove The few commits MTK added to kernel common and start your way over. ( upstream and bump kernel releases)

Kash did upstream an bit, but its still on 3.4.0 - 3.4.5 area.

--> then you pick The kernel with this base, and bump to 3.4.90 ish...on your commit...

Your missing The upstream from 3.4.5 - > 3.4.90.

Hope i was clear enough ;)

There are a lot of important commits missing, also some of faux features need those commits, and an continuous upstream.

( keep an eye on schd / arm / timekeep, etc commits)

You should try an compilation with -O2 flags (with some custom aditional mod flags), usually the end result is an smaller kernel and in some cases w/ better performance)

-O3 on MTK doesnt bring great performance ( MTK is NOT Qualcomm lol )

Toolchain: From your thread title your on Linaro ( good) , you should try out Linaro-Cross Toolchains by Christopher ( search xda) they are very very optimized for Cortex .

Hope i was clear, and like i said it was just an heads up. NOT an rank.

Regards ;)
[Micromax A116] neomanu:
I know about the 3.4.5 being fake. Read [MENTION=5439876]Dr-Shadow[/MENTION]'s notes on that.

I carefully applied 3.4.1 to 3.4.5 checking for the same. Then applied smoothly uptil 3.4.90.

Nothing is missing. It was just that sharing on XDA wasn't planned, was building for my personal use. Wasn't a git project while I did the above.

Hope you understood what I was trying to tell you in the previous post.

I'll take your advice about O2 and test the difference.

About the toolchain, I compiled it myself using Christopher's tool. Did all the searching already.

But they were for A15, A9 and general A's. I compiled specially for A7 using the latest kernel headers.

Shared on Github too, for others with A7.

It's nice to get advice from a senior dev. Thank you.