yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Khaon:
FOR TOUCHWIZZ USERS ONLY​

INTRODUCTION

Hello, I like doing not too heavy custom kernel, that's why I am sharing with you the kernel, hopefully at least someone like it! I have two version of this one. But some instabilities seems to be related with the hundred of patches I added from the stable linux kernel patches project and from the common Google android kernel repo.

This is an open devDB xda project. Feel free to fill in bugs reports, feature(s) requests and reviews.

My kernel is not intended to come along with tons of patches like many kernel you can see around..

However, I think it has some nice extras features I'ill try to increase in the coming weeks.​

Kernel's features :​

Latest Samsung's sources for MM

Compiled with GCC linaro64 6.2

Compilation options: O3 and architecture options enabled(A53 code generation optimized)

Double tap to wake: Removed for now because of non responsive screen.

cpufreq:touchboost duration and touchboost freq tweakables(only for interactive gov)

Second CPU clusters enabled: you will get 8 cores.

Overclocked max frequency for the first CPU clusters to 1.6Ghz ( 1.5 ghz remains the default)

Underclocked the second CPU cluster to 1.4 GHz not to have overheat problems

Voltage control for the first CPU

Tweaked cfq i/o scheduler to be more logical as we use NAND and not an HDD

​

installation instructions :​

You need TWRP recovery to start with: @ashyx custom recovery does every well ! I recommend this one

Once you get TWRP installed:

If your are scared to flashing something that will ruin your boot image; you can backup your current boot image from the BACKUP menu

copy to your phone the boot.img I provided.

Press INSTALL then press the right bottom button 'install Image' to switch to theflash image feature, then navigate to the path your copied the boot.img.

Select it and just flash !

Now you can reboot :).

What does work !

You can not set a max_freq for the second cluster: this is due because each time it goes on and let you the hability to change it, it will go offline and everything is to start again(if you dont crash until then). I think there is some easy for fix but I need to look over it.

What I would like to implement:

CPU voltage control

GPU governor down and threshold for each frequency step

GPU touch boost

DOWNLOADS LINK

​

XDA:DevDB Information

Khaon personal kernel for the A3 (2016) 13/10, Kernel for the Samsung Galaxy A Series

Contributors

Khaon, alexax66

Source Code: https://github.com/Khaon/android_kernel_samsung_a3xelte

Kernel Special Features: COmpiled by linaro 6.1, dt2w, blx, internal kernel space touchboost, SoC second cluster enabled(4 extra cores)

Version Information

Status: Stable

Stable Release Date: 2016-10-13

Created 2016-09-11

Last Updated 2016-12-31
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Jerome-X:
Sorry, only ServiceLogin.htm is able to download. Please correct link

---------- Post added at 01:51 PM ---------- Previous post was at 12:57 PM ----------

Download now works, thanks. Kernel works fantastic. Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Jerome-X:
if allowed, let me link a flashable odin file
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] IvoDi:
Can You compile one for A510F?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Khaon:
I am afraid I won't do this, as I don't own the device to test.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Khaon:
I think flashing with ODIN is a waste of time against the solution I provide.

Furthermore I am on linux. So no Odin.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] _euphonic_:
Can you tell us, how to do this?

Tapped by SM-A310F
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] joakim1988:
Some Geekbench scores here? I got Single: 626 and Multi: 2631
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] MarcoFal:
Ok thank you, i want to try your kernel. But if i want to restore the original? How can i do?

I suppose that if i make a backup of the boot.img, then in future i can restore this one. Is ok?

Thank you

---------- Post added at 02:23 PM ---------- Previous post was at 02:07 PM ----------

OK ... i've done the backup, installed the img of your boot and then ... the phone don't boot ...

I't show online the Samsung Galaxy Logo at the start, in the upper part of the monitor the red write abouth the kernel and then black ....

What can i do now?

... i'm not able to enter in TWRP ... i try all the button combo, what is the correct button combination?

Thank you ...

---------- Post added at 02:59 PM ---------- Previous post was at 02:23 PM ----------

I've found how to enter in recovery and restore boot image ... the phone now works ... Well

What was my error in flashing your boot image?

I've got an A310F, build version A310FXXU2APDC, Android 5.1.1.

I'had upload you image with TWRP 3.0.2, after have choosen to install an image, not a zip.

The procedure tell me that everything was ok ...

Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] papadawgg:
Does the CPU really has originally 8 cores? Is there any plausible reason why Samsung kept only 4 of them working by default?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mr.b4rt:
thx :good:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] JebusHerrl:
Hey there,

Can i use this kernel if i use the Nova Launcher instead of touchwiz?

I ask because in the First Post the Dev said "for touchwiz User only".

Thanks.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mr.b4rt:
yes
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] MarcoFal:
Someone was able to install this kernel and to use it?

I 've tried to install but the phone don't boot ... Any help?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mr.b4rt:
yes its working fine till now
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] MarcoFal:
What was my error in flashing the boot image?

I've got an A310F, build version A310FXXU2APDC, Android 5.1.1.

I'had upload the image file with TWRP 3.0.2, after have choosen to install an image, not a zip.

The log tell me that everything was ok ... but when i reboot the phone tell me that 'the kernel is not seanfored' and then doesn't boot and stay black.

I can only restore my backup boot image ...

Is there something that i have to check or do?

Inviato dal mio SM-A310F utilizzando Tapatalk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mr.b4rt:
kernel is for mm not lp
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] xpity34:
I have A510F MM and i install this kernel my device is bootloop. I bring back twrp recovery my files. But i need custom kernel for my devices. Anyone create kernel for A510F?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] likhon02:
installed and booted successfully .dt2w does not works properly and phone hangs when i change frequency and got 3-4 restart in half an hour..but it looks promising keep up the good work..
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Jerome-X:
8core rocks with MM

Yeah!

View attachment 3889785
[Huawei P9 Lite Questions & Answers] EnzoDC:
Lets ask the real question(s) here..

Does your P9 lite have a bottom hump beneath the logo area? Cause Ive tried various tempered glass and have spent quite a few thinking it was the tempered glasses fault till I realized the P9 Lite had a hump below thus causing an M-shaped bubble beneath the logo area.

Only me? No. Im an Admin in a P9 Lite Facebook group and most or all of my members have this issue.. furthermore that being said, does it have a fix or a solution so as to make the tempered glass fit and slick without bubble/ air space beneath the logo.

Thanks in advance!
[Huawei P9 Lite Questions & Answers] dc239:
Almost every tempered glass will create bubbles around the logo, because the screen of this phone isn't exacly "flat". The only solution is to use a screen protector or use a thinner tempered glass
[Huawei P9 Lite Questions & Answers] Jeik:
My bubble is on the left side of the logo and right above the top speaker.

It only reaches the H letter of the logo and goes to the bottom.

This is why I ordered tempered glass with a cut-out for the logo.

I specifically ordered the "Black" one from here,and I am currently using the "Full HD Clear" one:

https://www.aliexpress.com/item/P9-...2663990348.html?spm=2114.13010608.0.54.TPscxx

It will come to me either on Friday or on the next Monday,and just like I did with the clear one,I will post pictures of the package.
[Huawei P9 Lite Questions & Answers] EnzoDC:
Please update me with details once youve gottein it and take pics too pls :D
[Huawei P9 Lite Questions & Answers] EnzoDC:
Will they ever make a TG that fits the humps beneath perfectly?
[Huawei P9 Lite Questions & Answers] Jeik:
Maybe if they make tempered glass with stronger glue?
[Huawei P9 Lite Questions & Answers] EnzoDC:
Or a flexible glass that can curve the bottom hump. Did you get yours already? May I see? :D
[Huawei P9 Lite Questions & Answers] Jeik:
Sadly not yet. I am itching to remove my old one,the bubbles on bottom and top are driving me nuts...

It will arrive on Friday or Monday,since it was shipped by the seller on Saturday.
[Huawei P9 Lite Questions & Answers] EnzoDC:
Sounds great, please do post here when you've received it and put it. It also irritates me to see the bubble at the bottom lol
[Huawei P9 Lite Questions & Answers] SevenSlevin:
Try to buy on amazon the tempered glass selled by Spigen, it is quite good and doesn't leave the bubble on bottom.

the 2pack costs 10euro
[Huawei P9 Lite Questions & Answers] EnzoDC:
Any update on this?
[Note 7 Questions & Answers] GhostZini:
https://tapatalk.com/shareLink?url=...share_tid=3458590&share_fid=3793&share_type=t

Call Audio Quality? Something not right
[Note 7 Questions & Answers] nabbed:
Your link is broken.
[Note 7 Questions & Answers] GhostZini:
It worked for me. Strange
[Note 7 Questions & Answers] winol:
in fact, This phone has the best call quality I have heard, no complaints, on the contrary, high praises
[Note 7 Questions & Answers] GhostZini:
Do you have this phone?
[Note 7 Questions & Answers] winol:
I have a 930F, why?
[Note 7 Questions & Answers] GhostZini:
Because it sounded like you were quoting others experiences. I wasnt sure. I love the phone though. Sad to give up during recall.
[BLU R1 HD Guides, News, & Discussion] bibikalka:
Update, Dec 2, 2016 :

The procedure is updated to V7.4.2 and tested. Works!

Prerequisites :

1) You need to have stock V6.1 PRIME (unmodified /system & /boot partitions)

2) You need to have TWRP installed

If you have rooted your BLU R1, or removed ads from the Prime version, you need to restore your phone back to the stock condition first (unfortunately, the updates are incremental ...). Please follow this awesome post to downgrade your phone to stock Prime V6.1 version:

http://xdaforums.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499

After the downgrade, install TWRP via SPFT, and come back here.

Procedure to apply V7.4.2 update (please save all the files below to the device upfront, in order to do the steps in a single TWRP session):

0) If necessary, restore your /system & /boot to stock V6.1 (see the above section on how to restore back to stock V6.1 Prime)

1) Download the modified update zip file from here for the current version you have (6.1):

BLU_R0010UU_prime_V6.1_to_7.4.2_mod.zip

MD5 sum f806b3aabdf2e048ca0b32251d2c6a4f

link

2) Flash the above *zip in TWRP, and without leaving TWRP, go straight to 3)

3) Re-root by installing SuperSu.zip

http://xdaforums.com/r1-hd/how-to/twrp-how-to-root-t3425677

4) Remove ads again by applying the scripts :

http://xdaforums.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555

Here is how BLU_R0010UU_prime_V6.1_to_7.4.2_mod.zip was created. I took BLU_R0010UU_V6.1_GENERIC_6.0_20160617-1456-BLU_R0010UU_V7.4.2_GENERIC_6.0_20161109-13431478711915353.zip, edited updater-script to remove any references to the partition updates (meaning the old bootloaders will not be touched), and removed the new bootloader images just to be sure . The bootloader will still work as before with SPFT.

[MENTION=5355478]ColtonDRG[/MENTION], [MENTION=6782683]emc2cube[/MENTION], [MENTION=440235]kal250[/MENTION]
[BLU R1 HD Guides, News, & Discussion] emc2cube:
Great job [MENTION=6680544]bibikalka[/MENTION]

A 6.1 to 6.6 update package may be interesting as current phones are delivered with 6.1 and there is no easy way to update them to 6.5 via regular OTAs.

It will also be easy to upgrade after restoring 6.1 with [MENTION=5355478]ColtonDRG[/MENTION] SPFT files.
[BLU R1 HD Guides, News, & Discussion] jacewt:
Didn't work. 6.5-6.6

Fails:

Verifying current system ... /adupsfota.oded has unexpected contents
[BLU R1 HD Guides, News, & Discussion] bibikalka:
Are you sure you had 100% stock 6.5 system ? I have not really touched anything but the image files, so the script is working identically to what BLU programmed ...
[BLU R1 HD Guides, News, & Discussion] jacewt:
I didn't have the ads.
[BLU R1 HD Guides, News, & Discussion] bibikalka:
So your system was modified via those ad blocking scripts, and the update failed ... One option for you is to go back to stock V6.1, and then update it directly.
[BLU R1 HD Guides, News, & Discussion] jacewt:
I'll wait. Thanks!
[BLU R1 HD Guides, News, & Discussion] ColtonDRG:
Yes there is. You can upgrade to 6.4 and then to 6.5 using the OTA zips I have mirrored. Just drop them on the phone and choose them in FOTA (there is an option to choose an update from local storage)

---------- Post added at 09:14 PM ---------- Previous post was at 09:10 PM ----------

cna pl0x post version that doesn't require we download it from NSA headquarters?
[BLU R1 HD Guides, News, & Discussion] bibikalka:
OK, if you insist, I've added md5sum checksums to the original post. But remember, NSA can always fake those too !!!
[BLU R1 HD Guides, News, & Discussion] ColtonDRG:
No, no, no, I'm not worried about the integrity of the file, I'm worried about the server we're downloading it from. Everyone knows Dropbox is an Illuminati conspiracy.

---------- Post added at 11:43 PM ---------- Previous post was at 11:34 PM ----------

P.S. Added notes for those that used this to http://xdaforums.com/r1-hd/how-to/g...llback-ota-t3432499/post68036248#post68036248
[BLU R1 HD Guides, News, & Discussion] bibikalka:
;)

I did not have a better place to put the files. But I don't think that illuminati/NSA would care if ~100 people on the internet have unlocked their PRIME BLU R1 phones :D
[BLU R1 HD Guides, News, & Discussion] ColtonDRG:
That's exactly what they want you to think. You can upload it to https://mega.nz or something. Jus' sayin'.
[BLU R1 HD Guides, News, & Discussion] Flyinace2000:
So if we have modified to be "unPrime" (no ads) then no updates yet for us?
[BLU R1 HD Guides, News, & Discussion] bibikalka:
Your system is no longer stock, so the update will fail. Note that I've added a section in post #1 to explain how to go back to stock - you just re-install stock V6.1 Prime from [MENTION=5355478]ColtonDRG[/MENTION] , boot to TWRP, and upgrade to V6.6. Then re-apply scripts to remove ads.
[BLU R1 HD Guides, News, & Discussion] jacoghi:
What good is this update? Anybody noticed anything relevant?
[BLU R1 HD Guides, News, & Discussion] Flyinace2000:
and that is done on SPFT so there is no loss of data? Just revert back to PRIME 6.1, flash 6.6 via TWRP, then unprime again?
[BLU R1 HD Guides, News, & Discussion] thirdlobe:
This is what I am wondering as well..... Anyone?
[BLU R1 HD Guides, News, & Discussion] Sizzlechest:
An even better question: why bother upgrading their Prime phone to the latest firmware and then hack it to remove the ads when it can be converted to OEM? Yeah, there's the security fix in 6.6 that's missing in the latest OEM, but unless you like sideloading lots of questionable apps, who cares?
[BLU R1 HD Guides, News, & Discussion] emc2cube:
Just for the sake of accuracy, that's potentially (maybe OEM V12 do not contain the vulnerability patched, they are after all different versions) 3 security patches which are missing on the OEM: we got 6.1 patched to 6.4, 6.5 and 6.6.

Unfortunately as with many (all?) of their devices, BLU usually don't bother about updating the system. That's also why phones are cheap, there is no support provided and as often you get what you pay for.

I'm fine with that as for me it's a backup phone when traveling (dual sim!) or to mess up with.

I may be wrong on this one, and will be more than happy to admit so, but I do not think we will EVER get the band 12 update nor Nougat on the OEM, but as Amazon have a strong android division I would not be surprised that behind the scene they will be providing support and updates for the PRIME version. At least to be sure the ads are working and not bypassed too easily by the majority of the users, it's fair game after all.

You can also be sure that both amazon and BLU guys are reading this forum, I just wish some of them gave us a hand on how to improve the phone and were not just trying to revert all of our changes ;)
[BLU R1 HD Guides, News, & Discussion] bibikalka:
Yes, indeed. But just in case, do boot TWRP and do a backup beforehand.

That's my thinking too. Without ads the PRIME ROM may be the most up to date one. This calls for your scripts to be able to carefully rename all the stuff you want to disable, and then right before the ROM upgrade have another script which could rename all the files back and restore system to stock condition. You can actually have just 1 restore script to rename every possible file back that your original TWRP scrips could rename. This will be relatively straightforward, and clean.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
Yup, exactly my thinking too. Shameless self-advertising: http://xdaforums.com/showpost.php?p=68557388&postcount=19 that's what these guy do. Or at least are supposed to do.

I now avoid the first version of the scripts that removed the original files. Not only we have plenty of space left on /system so there is no real need to free up space, but it also allow a quick restore using a file explorer with root.

It worked on the few tests that I did on my phone (using custom OTA update scripts just using the check md5sum part). If you still plan to give a try on yours to upgrade to 6.6 and can give it a try before let me know how it go! (Script contents can easily be inspected and modified so feel free to edit them if you found something not working as intended or if you want to experiment furthermore)
[BLU R1 HD Guides, News, & Discussion] _bfritz:
Anyone applied the v6.1 to v6.6 update successfully?

I've tried installing the v6.1 --> v6.6 zip from TWRP twice now. Both times it failed with errors[1] and left the phone (Prime 16/2) unable to boot. No display at all, just red LED when plugged into USB. Fortunately, after much fiddling (and I think letting the battery fully discharge), I was able to connect with SPFT and reflash the preloader and other boot-related partitions.

Has anyone here successfully applied the modified update to v6.6 from v6.1 ?

[1] First time there were lots of errors when updater-script ran, including several about `/data`. I probably did something wrong. Second time I was more careful. No errors until it hit:

assert(package_extract_file("preloader_p6601.bin", "/tmp/preloader_p6601.bin"),
write_raw_image("/tmp/preloader_p6601.bin", "/dev/block/mmcblk0boot0"),
delete("/tmp/preloader_p6601.bin"));

where the `write_raw_image()` failed with exit code 7 (if I recall correctly).
[BLU R1 HD Guides, News, & Discussion] bibikalka:
OK, thanks ! Good catch ! Thanks for getting this far ! :D

It looks like TWRP cannot write to /dev/block/mmcblk0boot0 for some reason (probably need to report this to the TWRP developers).

I've removed the offending lines from the update scripts, and re-uploaded the zips, see post #1. It should work now.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
why do you want to change the preloader here anyway. Unless I am misunderstanding. Isnt the reason for this safe-update to avoid the ota from changing preloader?
[BLU R1 HD Guides, News, & Discussion] bibikalka:
I did not want to change it. I put the V6.1 copy into the zip in order not the change the updater-script at all. But since it does not seem to work under TWRP, I now took the preloader file and the flashing command out altogether.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Oh, I see. I have been thinking that maybe the way they used a u-boot image was odd. Since the phone doesn't have a u-boot. My idea was that a test with the u-boot and the updates lk.bin but original preloader.bin. I hope this combination allows the preloader to be written.
[BLU R1 HD Guides, News, & Discussion] _bfritz:
That did it. I'm now running v6.6 after an update from v6.1. SPFT still works and I was able to install TWRP via fastboot.

Thank you!
[BLU R1 HD Guides, News, & Discussion] bibikalka:
Thanks for reporting back !!! How does V6.6 feel, anything unusual ? Battery life ?

[MENTION=5355478]ColtonDRG[/MENTION] - care to mirror the update zips on your server ?
[BLU R1 HD Guides, News, & Discussion] kal250:
So I literally just went back to a fresh clean install of V12 OEM, and I can't just leave well enough alone, I am compelled to give 6.6 "safe" a shot!! So once the little one falls asleep(and shes wired tonight :silly: ) I think I'm gonna give it a go!! I'll chime in once I weigh in on it....
[BLU R1 HD Guides, News, & Discussion] _bfritz:
Didn't use it much before the update, so hard for me to compare it to v6.1. Everything feels pretty responsive. Definitely snappier than my Moto X (2013) on CM 12.1.
[BLU R1 HD Guides, News, & Discussion] bibikalka:
BLU does have UBOOT/LK images in the update file. What confusing is that they update the same partition twice, before & after the preloader update. I've looked at it, and decided that it was sloppy programming rather than any intent (& unrelated to the preloader itself):

http://xdaforums.com/showpost.php?p=68620455&postcount=98

http://xdaforums.com/showpost.php?p=68614012&postcount=77

http://xdaforums.com/showpost.php?p=68614088&postcount=79

But I still think that while the stock recovery can write to preloader, TWRP cannot for some reason. There is probably some bug in TWRP.