yashsingh1/xdaforums huggingface dataset:
[Android General] northwindtrades:
Great work andreidi :). Strange though that the framework files aren't different .Maybe it's because 3.10.10.3 is based on 3.4.67 ,we do have to flash over the lower kernel for it boot else we'll be getting a boot loop.

As for vibration in capacitive buttons I'm not sure ,I'll do some asking around.

I've worked in 3.10.54 which is more performing kernel before and got the pink front camera. I believe it has a lot to do with the libs. A mtk contributor also said something about compiling special camera libs using Android one sources to fix it.but I've got into it for a fix and quit cuz there weren't any major Rom's to port.This and the storage bug(not finding anything) was the main problem with the kernel,asking it drains a bit faster but it's more gaming friendly.
[Android General] Villain16:
can u guys help me please??
[Android General] andreidi:
Please confirm it's working for you, too, when you can, of course. I should thank you and [MENTION=7523876]7awliet[/MENTION] for the tips and instructions on where and what to look for, as I couldn't have done it without you guys.

I also think setting sd card as default for all apps and no access to internal memory for personal files is stupid. I think it's much better to have internal memory as default and to choose which apps you want to have sd card as default memory, because there are ~3GB free on internal storage which we can use for small apps. So, I highly suggest to use XinternalSD for Xposed to set sd as default for games (to store huge obb and data files), camera app (to store captured images to sd), browser (to save downloads to sd) and whatsapp (to have all the images, videos etc. received from contacts on your sd for safety in case rom failure).

I've done some more research about the capacitive buttons. I've found out that:

1) single tap of menu button doesn't open the menu of app, it opens recents.

2) long tap of menu button doesn't work (nothing happens if you don't release it) and when you release it, it acts as the single tap opening the menu like above.

3) double tapping for the home button is working, because I can lock the screen if I double tap on it, after I activated the optin in RR Configuration menu from Settings. So I guess the issue is only with the menu button.

4) tried to fiddle with Kernel Adiutor and to add the following lines into the build.prop, but to no avail:

ro.init.haptic_feedback=true
ro.config.haptic_disable=false

5) tried to disable an re-enable etc. power saving function that might have to do with capacitive buttons not vibrating. Nothing worked.
[Android General] northwindtrades:
You're not alone in this.a lot of other guys also reported this,they eventually switched to other ROMs.didnt happen to me which is why I didn't reply.

I've noticed them too in all my 3.10.54 ROMs as well.

I'll try contacting guys like ferhung,hyperion70 etc... On this and report back on this.

[MENTION=5862131]andreidi[/MENTION] your best bet would be to replace audio related filles in lib and hw folder
[Android General] Ookami999:
I'm trying to flash TWRP via SP flash tool and I get the well known error 5054. I noticed that my scatter file which I extract with MTKtools has a different size, smaller in my case, recovery partition from what you provide and I think that's the issue. It's an A5000 ROW model. I'm on KitKat latest.
[Android General] kemo12533:
Sorry guys about the Cm13 but my friends still fixing it there are sime bugs still (bluetooth , some minor bugs ) so wait please untill the alpha and beta test finish to get a full work rom
[Android General] arjanh05:
sir??

sir?? request for a samsung note 5 rom for our device? thnx in advance..
[Android General] Dark-Coder:
Also Fix the VPN , Low Sound Issue and proximity Black Screen Bug ( Cm 12.1 , Phone Screen Not Wake itself when Remove Phone from Ear after some time like 4,5 min) Too if Possible.. :)
[Android General] 9jabasewap:
We are waiting Bro!!!!!
[Android General] leonidas13131313:
Thanks, I thought that was the case but couldn't be sure. Also, I want to flash some roms but the link to the baseband fix is not valid anymore... can anybody reupload it just in case I get the sim bug? Or provide a link
[Android General] Dark-Coder:
Re-Upload...

http://www.mediafire.com/download/ohxi3qhpabdoxc8/baseband_a5000-imey_fix.zip
[Android General] v265963:
Where and how can i get a Lollipop without the bloatware? Just plain vanilla. System currently has KitKat and uses almost 3Gb of internal storage. Internal memory only has 8Gb. Please help! Any suggestions for a plain vanilla KitKat or lollipop.
[Android General] v265963:
I have decided to just get a plain vanilla KitKat. Please post a link so i can install a KitKat without any bloatware included. Lenovo A5000 from Globe Philippines.
[Android General] babigabi:
can anyone tell me if there on CM12.1 are any settings, to scroll through menu from right to left, not from the top down how is it now? thanks!

I flashed CM-12.1_Final 2 from http://4pda.ru/. Is just another **** video camera doesn`t work. Bleah! 2 hours wasted....

CM-12.1 dev-rom also have a major bug I can`t play 3D games on it. So I will reinstall the stock kitkat rom until I will find something stable
[Android General] 9jabasewap:
Admin, This Miui 7 Hotspot automatic Switch off every 5-10 min....

pls any solution to this????????
[Android General] cosmosdna:
I can't use cm 12.1 stable

If i instal that rom is aborted.
[Android General] GrenadeSpamr:
Flashed Resurrection Remix by DRT,

having problems with YouTube: video quality is only up to 240p. Any fix?
[Android General] fucca:
Do cm12.1 bugless have 2tap to wake?
[Android General] babigabi:
nope...2tap to wake is only for dev-rom
[Android General] kemo12533:
For who waiting for cm 13 it is up now go check it out
[Android General] pedzz23:
There is a problem communicating with Google servers using CM13 please help
[Android General] Buntot:
Can i use latest versions of TOOLS here?
[Android General] Dark-Coder:
Bugs List .. ??:confused:
[Android General] kemo12533:
Bluetooth and some mirror bugs
[Android General] andreidi:
Should I do this in the boot.img? Where am I supposed to find these files? I really hope it's the boot.img because it's easier to find haha :D

BTW, I forgot to add:

1) 3.10.103 kernel boots way faster than others

2) boot animation is smaller than in luckas, but animation is smoother (more fps)

3) at boot, after powered by android logo, a white horizontal line appears on left-top corner and when RESSURECTION REMIX writing appears, screen flashes black for 1-2 seconds and animation stops and starts faster for 1 second. This flashing and line also happens when entering TWRP for 3.10.103. I don't really this (cosmetic reasons), but I guess this is how the kernel was made.

4) animations in the rom are much faster and smoother than in luckas kernel version and response time is much shorter.

Also, cannot wake by double tapping HOME capacitive button, even if this is enabled in RR Configurations menu. I understand that tapping the screen waking is disabled in the kernel, but HOME taping should work...
[Android General] northwindtrades:
No it's in lib and hw folder in extracted ROM gesture wake is exclusive for Luckas kernels only I think.

Also a file called keylayout(not exact name since I can't remember exactly) should be interesting since it has a lot to do with hardware keys.

Your observations are on point. It's just that the kernel is optimized for the Lenovo a536.

http://4pda.ru/forum/index.php?showtopic=608418 Google translate this and check the patches tab,could be helpful.

Also extracted ROM -> system->lib->hw

Keylayout is in a folder called usr. can't pinpoint sorry
[Android General] andreidi:
I know about the keylayout because I patched it to remap headset buttons functions. I will compare with luckas version, I thought about it too.

I would like to have a look on the pink camera bug as well, maybe I can find something about that too.

LE: I am now looking at vibro.zip from A536 on pda and it has to do with keylayouts. Comparing now with older a5000 and newer as well.
[Android General] northwindtrades:
https://cloud.mail.ru/public/6nMd/mCbczfhQH a536 front cam patch

Button vibration a536 cm12.1 http://4pda.ru/forum/dl/post/7695131/Vibro.zip

You can use these as reference

So sorry that you are left to do all the work
[Android General] andreidi:
Yes, I already got those. I only used those patches too see what files I should look upon, but I compared the files from 3.10.103 rom with those from older kernel.

Haha, [MENTION=7387201]northwindtrades[/MENTION], I solved the case again thanks to you. Got the capacitive buttons vibrating again. Solution is to edit "generic.kl" and replace:

1) at "key 139" --- "MENU" with "MENU VIRTUAL"

2) at "key 158" --- "BACK" with "BACK VIRTUAL"

3) at "key 172" --- "HOME" with "HOME VIRTUAL"

4) at "key 580" --- "APP_SWITCH" with "MENU VIRTUAL" --- this also restores open menu function when single pressed and open recents app when long-pressed, both functions with vibration ON.

I'm did a TWRP flashable zip, now that I also fixed the MENU button not working as a MENU button when single-pressed.

Cam patch is next. But I also want to recheck boot.img for any possibility to reimplement double-tap to wake....

LE: [MENTION=7387201]northwindtrades[/MENTION], do you still have RR 5.7.4 with luckas kernel? Can you please tell me if there is double vibration when long-pressing MENU and BACK capacitive buttons? Please temporary enable "Vibrate on touch" in "Settings-Sounds" to test. There is a vibration when you first touch it, but is there a second vibration when it remains pressed? On my current setup, only MENU vibrates the second time when long-pressed and I want to make sure this is the same setup as in luckas kernel.

LLE: [MENTION=7387201]northwindtrades[/MENTION], have you tried flashing camera fix for a536 which you linked previously onto a5000? I could try that first. It's harder to compare here, as there are unicodes...
[Android General] northwindtrades:
Thought about it because Most of the lib files are same for mt6582 devices which is why we got so much Roms from sites like mtkroms.but I'm on 3.4.67 and cant do anything :(
[Android General] andreidi:
Tried, got bootloop and I didn't backup my previous setup. All I had was 3.4.67 kernel backup so I have to flash from scratch again...
[Android General] northwindtrades:
Too bad you didn't make a backup.

Maybe you should take some rest and see if I get any reply from mtk mods
[Android General] andreidi:
I really have no idea what to seek in the camera fix... I will try to get RR 5.7.3 or CM13 for A536 and compare with that. Comparing between 3.4.67 and 3.10.103 is useless, because RR 5.7.4 for 3.10.103 has a newer camera app, therefore most libs are different.
[Android General] andydor:
Well, some of you said that kernel 3.10.103 is based on 3.4.67. Therefore, you should give a try and replace all those files in the lenovo a536 cam patch with those from stock S030. Maybe you'll have luck...
[Android General] Villain16:
Thanks for the feedback. I figured out a way by reading on 4pda. Those who have this problem(No sim card error) have to follow a procedure:

1. Update to lollipop firmware if u are on stock kitkat

2. Roll back to kitkat firmware

3. Flash TWRP with 3.10.103 kernel

4. Flash the rom of ur choice with kernel 3.10.103

This fixed things for me ;) hope it helps others.
[Android General] andreidi:
I'm gonna try some more.

So far, I tested individual files from A536 patch. Nothing happened/changed with most, but with these:

1) libcamdrv.so --> can't connect camera when starting app

2) libcamera_client.so --> bootloop

3) libcameracustom.so --> can't connect camera when starting app

Then, I tested individual fimes from A5000 RR 5.7.4 with kernel 3.4.67. Nothing happend with all, except only one file changed something: libcamdrv.so --> can't connect camera.

Then I figured out it has to be this single file libcamdrv.so responsible for the pink front camera, as others do nothing. So I tried this file from S030 and S123 and still - can't connect camera error.

Ideas?
[Android General] northwindtrades:
Didn't get any reply from devs yet

I'm thinking we'll need to compile special camera libs using Android one sources like I read in mtk hardcore thread to fix it.
[Android General] andreidi:
Yes, I think about that too. But one more question: how can we find out how the A536 patch was done? We could apply the same procedure to our files.
[Android General] 7awliet:
Kernel 3.10.103

[MENTION=5862131]andreidi[/MENTION] [MENTION=7387201]northwindtrades[/MENTION] I'm on page #178 and I'm catching up, but I love your work so far, real good job. I may have time on Tuesday to look at some stuff. As for comparing 3.10.103 with Luck@s' 3.4.67, I hope you're comparing to Danger-LuckAs-A5000-kernel-3.4.67-20160514-02-08-boot.zip

I know many people use the 11 February 2016 stable build (LuckAs-A5000-kernel-3.4.67-20160211-00-04-boot.zip) but if they're gonna do that, they might as well us the latest 25 February 2016 stable build which is LuckAs-A5000-kernel-3.4.67-20160225-17-07-boot.zip.

Even more people use the March 2016 UNstable build (Danger-LuckAs-A5000-kernel-3.4.67-20160322-14-20-boot.zip) which makes no sense because if they're gonna use an UNstable build then use the latest May 2016 build (Danger-LuckAs-A5000-kernel-3.4.67-20160514-02-08-boot.zip <--- THIS IS THE ONLY ONE I'VE USED).

ALSO, Luck@s has uploaded their kernel 3.10.103 ftp://185.86.77.191/LuckAs-kernels/A5000/ click the 3.10.x folder.

UPDATE: LUCK@S' 3.10.103 CUSTOM KERNEL AND DARKLORD4822'S 3.10.103 CUSTOM KERNEL ARE NOT FOR PUBLIC USE, REQUEST IT FROM THEM AT ON 4PDA (PLEASE DONATE FOR THEIR HARD WORK)

Finally, in the kernel, you may want to look at comparing files init.rc, init.cm.rc, and init.mt6582_common.rc for vibration, maybe DT2W, storage stuff, and definitely for camera. And maybe platform.xml too in \system\etc\permissions\ <---- I'm working with mtkroms.com's RR 5.7.3. Should be same in RR 5.7.4.

P.S.: I've written a bit about android.hardware.camera.xml and the other android.hardware.camera.______.xml files in this thread, use the search box and maybe also see my porting script posts as it mentions some discoveries I made about files to delete which should be there. But like northwindtrades said, take a break, a day or so, ;)

---------- Post added at 02:12 PM ---------- Previous post was at 02:06 PM ----------

Good observation by andydor. I can't remember who made that claim but I would say - just as a theory - that 3.10.103 is more like 3.10.54. No? They are both 3.10.x after all. Thus I would suggest replacing all libcam files from latest lollipop stock S124.

Just a theory for now, I'll compare this A536 patch whatever/wherever it is, with our libcam files maybe on Tuesday.
[Android General] andreidi:
So, should I try and unpack stock 3.10.103, replace kernel with renamed "zimage" from luckas's kernel, rebuild boot.img and flash it on top of the existing RR 5.7.4 with stock 3.10.103? What's the difference from the stock 3.10.103 kernel? Does it fix anything?

I tried placing all libs from S123, but to no avail. I don't think with S124 I should be more lucky, but I'll try. I don't have a S124 system.img on hand, as S124 can be downloaded only as an update, therefore I can't get the libs from that version.

Also, I found another annoying thing of the RR 5.7.4 with 3.10.103 kernel: Sound is very loud (ringtone, notification) and i have to keep the volume slider at 50%, because over this percent it gets nasty distortion. I tried "vol_fix.zip", but it didn't work. It worked on RR 5.7.4 with 3.4.67 kernel, but I can hear that sound on the newer version is not boosted if I reduce the volume level, therefore I think it may be elsewhere. What files should I look upon to edit volume levels? I heard about "mixerpath.xml", but I can't find it in system/etc...

Front camera patch for A536 is here: https://cloud.mail.ru/public/6nMd/mCbczfhQH
[Android General] 7awliet:
By "stock 3.10.103" do you mean the 4pda.ru one? then yes. My premise was that to get DT2W and camera working, Luck@s' kernels are pretty good and they have fixed such issues - again, not tested. Could compare the internals?

S124:

https://cloud.mail.ru/public/928y/m62Z4WSiM

OR

https://drive.google.com/drive/folders/0B1Ee0JPRAllUTFh5OEFOdFNkd2M (set it to list view, top-right) (OTA version is WC08)

Anyway, Luck@s' kernels may be worth checking out, at least at WinMerge and Notepad++ level.
[Android General] andreidi:
Haha, luckas kernel 3.10.103 RC3 DID THE JOOOOOOOB! PINK CAMERA FIXED. YAAAY! AND ALSO TAP2WAKE FULLY FUNCTIONAL! Luckas, you're the man!!!
[Android General] northwindtrades:
Nice work [MENTION=5862131]andreidi[/MENTION] .Never thought luck@s kernel could fix it :).
[MENTION=7523876]7awliet[/MENTION] people use the unstable build cause it was spoon-fed here to the thread in the first few pages.still ,didn't expect the kernel you found to fix front camera.nice thinking, owe it all to you just like GPS fixes.

Many thanks andreidi and 7awliet:o
[Android General] Satoshii:
Volume BUG!?!?!?

Anyone experienced the volume being too loud?!..... Cause i did.....and i didn't know the cause :eek:

BTW I'm new here :D
[Android General] northwindtrades:
That has been mentioned on the previous page:p

Flash vol_fix.zip if you're in 3.4.67 kernel if you're on 3.10.103 wait for a fix.

Btw welcome to our crazy group ;)
[Android General] Satoshii:
Thanks :D now it's back to normal,But what's the difference with the 3.10.103 kernel and 3.4.67 kernel?:eek:

BTW I'm using MI UI 8

I'm glad i joined :good::cool:
[Android General] northwindtrades:
3.4.67 is realativly old to 3.10.xx..3.10.103 and 3.10.54 can run higher Android versions like nougat, has more security patches and performance upgrade and fewer bugs. development on 3.4.67 will stop eventually
[Android General] andreidi:
Volume issues on 3.10.103 are odd:

1) ringtone (speaker on the back of the phone) is loud as hell, distorts when max --> after the fix was applied on 3.4.67, it still had some distortion, but rare, depending on ringtone raw volume.

2) headphone volume is same like stock S030/S124, lower than 3.4.67 CM13/RR --> in 3.4.67 was very good (enough loudness) even with or without the fix.

3) earpiece (calling speaker when not set on speaker on the back of the phone) seems even lower than stock S030/S124. --> in 3.4.67 was very good (enough loudness) even with or without the fix.

vol_fix.zip doesn't to anything to 3.10.103, not a single improovement. I also tried to remove AudioFX to see if it helps, but it doesn't. Where should I look in the rom or in the bootimg?

Also, another thing I'm concerned about is sim card signal strenght, it seems 3.10.103 has slightly lower signal, or maybe it's just a cosmetic bug of the signal icon in the notification bar.
[Android General] Satoshii:
Thanks for the info........ I hope the audio issue on the new kernel will be fixed....:)
[Android General] andreidi:
:good:
[Android General] evergreen49:
This new luckas 3.10.103 ROM should be flashed over stock kitkat or lollipop
[Android General] Villain16:
If u r on stock kitkat upgrade to stock lollipop and then roll back to stock kitkat and flash the rom with kernel 3.10.103 or else you will have no sim card error. :p
[Android General] romario_ne:
So? You are HERO now! We`ve paid money for this job and now you stole it. Well done!

When Lucas decided to make rollback kernel for us he even didn`t ask any money for his job. But we gave some $ to him - because he spend his time for our trouble.

And now when we asked Lucas to make TOTALY NEW KERNEL for us without any bugs (NOT FOR FREE!!!) and he made REALLY COOL FULLWORKING KERNEL, get money as he asked...

And now you are HERO! Great job, man, great job! Excellent theft!
[Android General] Satoshii:
But he said thanks to "Lucas" though....:angel::good:
[Android General] romario_ne:
Realy?!	Tell me on which $ exchange rate???
[Android General] andreidi:
All credits go to LuckAs for the kernel, [MENTION=7387201]northwindtrades[/MENTION] & [MENTION=7523876]7awliet[/MENTION] for precious advice, suggestions and assistance. [MENTION=7523876]7awliet[/MENTION] shared the ftp link for the kernel with all of us. I believe that if LuckAs wanted to share this for an ammount of money, he wouldn't have uploaded this on his ftp for free, on a link which has been quoted numerous times on this topic and which is easily accessible since his 3.4.67 and 3.10.54 kernels are shared in that same location. I DIDN'T AND I WILL NEVER REQUEST MONEY FOR THIS, I put together all these patches ABSOLUTELY for free (I wanted to correct the issues for my personal use, but I also wanted to share to other, thinking I could be helpful), using stuff provided for free (LuckAs kernel, 4pda kernel, rr 5.7.4 ports, freeware apps for working with etc.). I'm also very sure that confirming the fix will certainly make a lot of people thank LuckAs and make donations for it directly to LuckAs. I WON'T EVER ACCEPT ANY DONATIONS BECAUSE NEITHER I DID THIS FOR MONEY, NOR I WANT TO BE A HERO. LuckAs kernels were available for free since the beggining and the people who wanted to donate they could do it, but they weren't forced to. Besides, all I did was to built the bootimg using LuckAs kernel zImage with Android Kitchen tools. I didn't steal anything, because everything was already shared for free.

Please correct me if I'm wrong and I'm also truly available for being reported and banned from this forum or for deleting all my posts and shared files. PERIOD.

---------- Post added at 05:17 PM ---------- Previous post was at 05:01 PM ----------

This new luckas ROM should be flashed over stock kitkat, as usually, but I didn't test it and cannot guarantee it will work, I just updated the old 5.7.4 with the patches. I use the old 5.7.4 with patches applied separately from within TWRP, because I didn't need yet to reflash from scratch and I don't want to redo all the installation process just to test if it really works. But I will report working or not when I will need to reflash from scratch. It might not work, in which case you have to flash the patches separately after installing and first boot of original 5.7.4 with 3.10.103.

I didn't experience the "no sim card error" when flashing 5.7.4 without upgrading to stock lollipop (I never upgraded to stock lollipop before flashing other roms). I had a "no sim card error" once, but was related to a backup with TWRP over another existing ROM, but it was gone after flashing kitkat from scratch and flashing the rom again with TWRP.
[Android General] evergreen49:
Andreidi ,the full ROM reboot to recovery and doesn't boot.

Romario ne sir why are you talking like he named the luckas kernel to andreidi kernel.
[Android General] andreidi:
So, did you:

1) Flashed stock S030, luckas 3.4.67 and TWRP 3.0 recovery with 3.10.103

2) Boot S030 fully

3) Reboot in TWRP, wipe data/cache/dalvik, flash the RR 5.7.4, wipe cache/dalvik and reboot

and when you boot the 5.7.4 it gets bootloop (with RR animation) or doesn't boot at all (powered by Android logo over and over again)?
[Android General] evergreen49:
I didn't use the recovery you're referring to,that must be it:good: thanks I'll try with that recovery.

It shows powered by android and turn off reboots to recovery might be because recovery and rom were incompatible with each other. Thanks
[Android General] andreidi:
Yes, but this was happening even with unpatched 5.7.4 3.10.103, this is why they said to use TWRP 3.0 with 3.10.103. But if this still happens when you use the correct recovery, I guess I couldn't embed the patches successfully in the unpatched rom zip, therefore I can only say to flash that first, then boot normally, then flash the zip patches over it.