Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOURCE​
**Snapdragon™ is a registered trademark owned by Qualcomm Technologies Inc.
**Synapse™ is a registered trademark owned by @Andreilux
**(v1)Xcelerate Logo™ is created by @fareed_extreme
**(v2)Xcelerate Logo™ is created by @Sharan Narayan
XDA:DevDB Information
Xcelerate™ Custom Kernel, Kernel for the YU Yureka
Contributors
kairi_zeroblade, DooMLoRD, RohanAJoshi
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Production build 4
Stable Release Date: 2015-04-11
Created 2015-02-16
Last Updated 2015-04-11
Reserved
Short Credit list:
DooMLoRD for assisting in the compilation
Rohan Joshi, Prithvi Raju and Raj Gopi for testing
Cyanogen
ARM
Short Feature list:
Basic Governors(I won't add Ripoffs)
Built using my own GCC 4.9.x Toolchain(with fixes specifically Aimed at Cortex A53 erratas) built across the standards of Google's own Toolchain..
Simple and no fancy stuff..(more does not guarantee it's better)
Uses a simple free and user friendly application called Synapse by @AndreiLux for configuration purposes(slightly adding more functionality)
A few Notes:
Be advised that this kernel is best used "As is" i do want to prohibit the use of scripts that they say "enhances performance and battery" just use the kernel as it is..everything is managed automatically by the kernel and rest assured continuous innovations are en-route.
**Camera might be broke on OLDER CM11 and UNOFFICIAL BUILDS since this is built using the latest source from Cyanogen use this FIX
Compatibility list:
According to testers/users feedback the Kernel works on the FOLLOWING ROMS(tested)
CyanogenMod 11(Stable)
The list will grow as soon as Testers/Users can provide means and ways to make this compatible with everything..
Downloads
Grab latest Production builds here
Nice work mate :good:
BTW could have been much better if u could just left cm commits on git
so would have been easier for other devs to track earlier parent commit changes Rather than using : initial dump of Yureka source from CM snapshot 2-13-2015
Anyways no problems .....
Proud to be tester of this kernel..
working amazingly..
charging speed is double than before now..
also smoothness is awesome, thanks bro..
in call battery drain is dramatically reduced from 12% / hr to 6% / h..
will seek for further features..
does it shutdown cores when low usage ???
Not a fan of Custom Kernels, but...
but, yeah, but for the first time 'll be trying this (don't know why but I have this voice inside of me that's compelling me to try this out), hope everything goes well, will edit to share my experiences once I've used it for a couple of days, till then, thanks for this and appreciations for your efforts.
more governors please?
Thanks a lot! I had been waiting for this kind of a custom kernel!
hey, could you add smartassv2 governor to the kernel?
*downloading the kernel as i type*
Cheers!
:good: :good:
camera not working!!!!!!!!!!!!!!!!
sauravdante said:
camera not working!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Flash the updated kernel I have posted, it includes the libs, then flash xcelerate kernel, camera should work.
Op can add those libs.
No UCI support detected !
Damn ! OP enlighten me on this error when I try to open Synapse.
I'm rooted, I have the stock room that came with the cell, the ago had superuser permissions, but still I'm not able to get that app to work. Did a normal flash, booted into recovery, selected the zip that I downloaded and record again.
Googled for the error, found a post in which a guy having Xiaomi had the exact same problem, there you our someone suggested to flash normally, so that's kinda what I did, what m I missing ??
hkm93 said:
Damn ! OP enlighten me on this error when I try to open Synapse.
I'm rooted, I have the stock room that came with the cell, the ago had superuser permissions, but still I'm not able to get that app to work. Did a normal flash, booted into recovery, selected the zip that I downloaded and record again.
Googled for the error, found a post in which a guy having Xiaomi had the exact same problem, there you our someone suggested to flash normally, so that's kinda what I did, what m I missing ??
Click to expand...
Click to collapse
I am getting this. [emoji20]
hkm93 said:
Damn ! OP enlighten me on this error when I try to open Synapse.
I'm rooted, I have the stock room that came with the cell, the ago had superuser permissions, but still I'm not able to get that app to work. Did a normal flash, booted into recovery, selected the zip that I downloaded and record again.
Googled for the error, found a post in which a guy having Xiaomi had the exact same problem, there you our someone suggested to flash normally, so that's kinda what I did, what m I missing ??
Click to expand...
Click to collapse
Sudeep Duhoon said:
I am getting this. [emoji20]
Click to expand...
Click to collapse
Support for synapse is probably coming in the next builds..as I'm not familiar with the sysfs for the YU yet..I'm building this blind and with @RohanAJoshi only doing the tests for me.. rest assured its stable, fast and battery friendly..
EDIT:
I'm still looking for testers if someone is interested in hitting up to the task well you can find me on Hangouts via [email protected]
I am in pac man rom can i use this kernal?
proximity issue
Facing proximity issue after flashing this kernel.... Hope so this ll get fixed in upcoming builds nice work indeed
---------- Post added at 04:59 AM ---------- Previous post was at 04:55 AM ----------
Camera not working after flashing latest build
Been using for more than half a day. So far so good. thanks @kairi_zeroblade :good:
Testing your kernel on dumtara CM11 build.
Any possibilities of some custom governors that implement core hot plugging functionality ??
Error
satitrip said:
Click to expand...
Click to collapse
Dude, its already posted in the thread, Read first. Correct your image size, it covers my screen, seriously.
cm11 dumtara
I'm on cm 11 by dumtara. can I flash this kernel?
kairi_zeroblade said:
I'm still looking for testers if someone is interested in hitting up to the task well you can find me on Hangouts via [email protected]
Click to expand...
Click to collapse
I saw ur post regarding that, but I may not have mentioned this but I'm not so good in technical side of android. Being a java developer I never bothered about them but for the past few days I'm actually inclined towards learning android development too, say just as an additional hobby, and to my surprise it's Java too.
Now that I have already flashed the kernel, I can be of some use for sure, but conditions apply. I am not available all ( I can update you on a daily basis in between 10-11 pm IST, and on weekends if that's ok with you) the time and someone will have to guide me or provide info on what I'm supposed to do, coz I have no idea what needs to be done while testing a kernel.
Sudeep Duhoon said:
Flash the updated kernel I have posted, it includes the libs, then flash xcelerate kernel, camera should work.
Op can add those libs.
Click to expand...
Click to collapse
Thanks.. But which kernel should should I flash first and which one next.. Can you give download links pls.
</> Developpers Only </>
As you may know it, GALAXY Grand Prime is powered by a 64Bit Entry-Level Quad Core CPU, that makes developpment on this device VERY HARD It's like Intel Atom Processors
Anyway, I tried to make a repo for building TWRP GALAXY Grand Prime by refering to Huawei G620S' Repo by GitHub member "EloYGomeZ" BIG thanks to him.
If you're interested in building TWRP, you can use this repo. Feel free to use it, but please remember to give credits when done.
The Repo isn't yet done, it may contains many bugs and errors; plus I can't test it or test a TWRP build since I don't have my hand on that device (should have one in 2 weeks).
Update as of 18/6/2015: TWRP has been compiled for Grand Prime
TWRP ==> http://forum.xda-developers.com/grand-prime/development/share-twrp-2-8-4-0-galaxy-prime-t3064506
Philz Touch :
Download ==> https://mega.co.nz/#!SQ8XkIiI!Kj_9rhfVY8bz0nRjZGDGra4Bs3Nen-87O4vhWGHlVzc
Thread ==> http://forum.xda-developers.com/gra...share-galaxy-grand-prime-sm-g530h-f0-t3057571
Source ==> http://www.phonandroid.com/forum/ph...d-galaxy-grand-prime-sm-g530f-fz-t116883.html
Current CM12 ETA:​- Compiled successfully
- Bootable
- CanNOT get to home launcher!
GitHub an sources:
@K_TECH 's device tree and all sources needed to compile cm12 ==> https://github.com/fortunave3gxx
fortuna3g TWRP Repo ==> https://github.com/Nonta72/fortuna3g-twrp (mine)
Huawei G620S TWRP Repo (used as a reference): https://github.com/Nonta72/android_device_huawei_g620s-twrp (EloYGomeZ)
Device Tree (WIP): https://github.com/Nonta72/fortuna3g-tree (mine)
Source Code for KK: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G530​
Wow great,
IMO, its not about 64bit chipset, as we know, lenovo a6000/k30 have the same chipset 64bit.
But have development, we have CWM, Phillz recovery, cm11, MIUI rom
The main problem to devevelop grand prime is qualcomm secure bootloader that protect the device. We need to disable the secure bootloader first. CMIIW
Shinkumara said:
Wow great,
IMO, its not about 64bit chipset, as we know, lenovo a6000/k30 have the same chipset 64bit.
But have development, we have CWM, Phillz recovery, cm11, MIUI rom
The main problem to devevelop grand prime is qualcomm secure bootloader that protect the device. We need to disable the secure bootloader first. CMIIW
Click to expand...
Click to collapse
I didn't see Lenovo a6000 CWM/TWRP and Custom ROMs yet.
About Bootloader on Grand Prime, I never heard about this
Maybe we should start unlocking this 1st
I can't do anything as of now, since I don't have the decice yet.
i hope i can learn somewhere how to build twrp. Anyway i will support u guys.
Samir96 said:
i hope i can learn somewhere how to build twrp. Anyway i will support u guys.
Click to expand...
Click to collapse
If you think you can be tester and don't care about flashing your phone at least twice a day, then you can help!
can you please fix it. recently i don't have the device. building cm 11
nilimahona said:
can you please fix it. recently i don't have the device. building cm 11
Click to expand...
Click to collapse
What's the problem with the BoardConfig ?
PS: I also don't own the device yet.
The board config should be in KK Kernel source.
I'll test extensively I have 8 sm-g530az (cricket USA)
All rooted with cwm philz recovery
Nonta72 said:
If you think you can be tester and don't care about flashing your phone at least twice a day, then you can help!
Click to expand...
Click to collapse
krazy_smokezalot said:
I'll test extensively I have 8 sm-g530az (cricket USA)
All rooted with cwm philz recovery
Click to expand...
Click to collapse
The device already have CWM.
All you need now is CyanogenMod.
Nonta72 said:
The device already have CWM.
All you need now is CyanogenMod.
Click to expand...
Click to collapse
Would you know if anyone has started on that project?
krazy_smokezalot said:
Would you know if anyone has started on that project?
Click to expand...
Click to collapse
I already started, currently getting the device tree ready.
Lets start ^_^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm getting stuck in this error :3
source: http://github.com/fortunave3gxx
Try "apt-cache search audio_defs.h" to find the dev package that is missing. Sometimes it work
Sent from my SM-G530FZ using XDA Free mobile app
kentone said:
Try "apt-cache search audio_defs.h" to find the dev package that is missing. Sometimes it work
Sent from my SM-G530FZ using XDA Free mobile app
Click to expand...
Click to collapse
Nevermind, i solved that errors in an hour ago ^_^
The build progress has been done, but i get an error when i try to flash it"binnary error". And it's come from recovery
If it ready, i'll upload my device configuration, Stay tuned
my own source: http://github.com/fortunave3gxx
K_TECH said:
The build progress has been done, but i get an error when i try to flash it"binnary error". And it's come from recovery
If it ready, i'll upload my device configuration, Stay tuned
my own source: http://github.com/fortunave3gxx
Click to expand...
Click to collapse
try to replace the update-binary in META-INF folder
The you can building kernel from source code boeffla working with grand prime ... kernel boeffla is 1 of the famous kernel. if you are building is too good. I very much hope into you. Thx you
Nonta72 said:
try to replace the update-binary in META-INF folder
Click to expand...
Click to collapse
Can you share your update-binary?
recoman said:
The you can building kernel from source code boeffla working with grand prime ... kernel boeffla is 1 of the famous kernel. if you are building is too good. I very much hope into you. Thx you
Click to expand...
Click to collapse
I don't think Lord Boeffla does support the Grand Prime.
K_TECH said:
Can you share your update-binary?
Click to expand...
Click to collapse
I'd love to, but I don't have the device yet. That's why I even stopped the project.
Suggestion: try to find a similar device (same chipset) that have CM or a CWM ROM, download that ROM and replace your binary with the one in that ROM. I heard the Huawei G620S (with MSM8916) have a working CyanogenMod, you may want to check that out.
Suggestion 2: make sure your updater-script is well formed, I can help you with that if needed, just upload that file.
Deleted project.
I was not making progress and others had. This was intended as a kick-starter, i suppose, and that seemed to have worked. Now Much better advanced work is done elsewhere.
Reserved
Issues have been noted, where built kernel did not boot on "ford" custom rom but did boot on "austin" custom rom.
So after comparing the the build defconfigs, I merged the differing commands that where not screen or camera related, and now I rebuilt the stock level -54 and it did load on "ford" with custom rom.
Changeing the file in download tab now
Reserved
Wow! Nice, let's hope we get an upstream!
Good job!
mrmazak said:
Stock kernel can now be updated, because of the recent bootloader unlock.
cherry-pick merged to linux-stable branch
project just beginning.
made first build and flash of stock version 3.10.54
I am takeing just baby steps here. Booting into just one update step at a time,
In the linux stable tree updates are currently at 3.10.108
Current version on Fire device is 3.10.54
I have made success on the first step to 3.10.55
Flash with twrp using the anykernel2.zip attached.
Tested anykernel method on revampted-os with magisk patched boot.img.
Worked fine.
But on rom without magisk, flashing kernel keeps device on boot-animation screen.
must give credits to
@osmosis for anykernel
--creator of__ android-linux-stable.sh on github
XDA:DevDB Information
Amazon Ford upstream Kernel, Kernel for the Amazon Fire
Contributors
mrmazak
Source Code:https://github.com/mrmazakblu/Fire_Ford-upstream_kernel
Kernel Special Features:
Version Information
Status: Testing
Created 2019-04-06
Last Updated 2019-04-06
Click to expand...
Click to collapse
I don't see a zip, am I mistaken?
t3chwizard said:
I don't see a zip, am I mistaken?
Click to expand...
Click to collapse
on the downloads tab.
I believe that is visible to everyone signed in.
here is link to it if not.
https://forum.xda-developers.com/devdb/project/?id=32276#downloads
mrmazak said:
on the downloads tab.
I believe that is visible to everyone signed in.
here is link to it if not.
https://forum.xda-developers.com/devdb/project/?id=32276#downloads
Click to expand...
Click to collapse
If you could compile it for the 7th gen I would appreciate it very much.
I can be a tester if you want.
Thanks!
mrmazak said:
on the downloads tab.
I believe that is visible to everyone signed in.
here is link to it if not.
https://forum.xda-developers.com/devdb/project/?id=32276#downloads
Click to expand...
Click to collapse
It didn't show on XDA labs that's why I couldn't see it I think
mrmazak said:
Stock kernel can now be updated, because of the recent bootloader unlock.
cherry-pick merged to linux-stable branch
project just beginning.
made first build and flash of stock version 3.10.54
I am taking just baby steps here. Booting into just one update step at a time,
In the linux stable tree updates are currently at 3.10.108
Current version on Fire device is 3.10.54
I have made success on the first step to 3.10.55
Flash with twrp using the anykernel2.zip attached. On the downloads tab.
Direct link to download page:
#downloads
Tested anykernel method on revampted-os with magisk patched boot.img.
Worked fine.
But on rom without magisk, flashing kernel keeps device on boot-animation screen.
must give credits to
@osmosis for anykernel
--creator of__ android-linux-stable.sh on github
XDA:DevDB Information
Amazon Ford upstream Kernel, Kernel for the Amazon Fire
Contributors
mrmazak
Source Code: https://github.com/mrmazakblu/Fire_Ford-upstream_kernel
Kernel Special Features:
Version Information
Status: Testing
Created 2019-04-06
Last Updated 2019-04-08
Click to expand...
Click to collapse
Lineage 12 just boots up to a black screen, then goes back to the boot logo.
Pix12 said:
Lineage 12 just boots up to a black screen, then goes back to the boot logo.
Click to expand...
Click to collapse
Like I mentioned, I tested it on "revampted" and with majisk.
Afaik lineage has SuperSU. I do not know if you can flash majisk or not.
And as of now, I do not understand why that it is only booting with magisk.
Needs testing
mrmazak said:
Like I mentioned, I tested it on "revampted" and with majisk.
Afaik lineage has SuperSU. I do not know if you can flash majisk or not.
And as of now, I do not understand why that it is only booting with magisk.
Needs testing
Click to expand...
Click to collapse
It had magisk.
Pix12 said:
It had magisk.
Click to expand...
Click to collapse
Ok, the revamped is still fireos, so this might be related.
The kernel is forcing the addition of "trapz" on the build. Best as I can tell it is some type of logging system. I will try and skip that and see if it might then boot on lineagos.
Rortiz2 said:
If you could compile it for the 7th gen I would appreciate it very much.
I can be a tester if you want.
Thanks!
Click to expand...
Click to collapse
i made you the stock level subversion 54,
adding it to the upstream folder i am working on.
Got stuck right now though.
After first few merge conflicts i am getting build errors. I must have allowed bad commit or merge.
Uploading file for you to try.
mrmazak said:
i made you the stock level subversion 54,
adding it to the upstream folder i am working on.
Got stuck right now though.
After first few merge conflicts i am getting build errors. I must have allowed bad commit or merge.
Uploading file for you to try.
Click to expand...
Click to collapse
Working perfectly!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Was the 55 broken?
Pix12 said:
Was the 55 broken?
Click to expand...
Click to collapse
I have flashed both the Ford test kernels on my two devices. The one with revamped is and magisk , they both worked. But on the other fire 7 5th gen that I have lineagos on neither one worked.
This one that just worked on the 7th gen worked on lineagos. I don't know what was different.
Now the lineagos for the 7th gen was modified from the one for the 5th gen. Maybe that had some other change that allowed it.
Need to check that out.
Rortiz2 said:
Working perfectly!
Click to expand...
Click to collapse
Did you need to have magisk?
And what build version boot.img do you have installed.
I see in the ported Austin version of the lineage you are not flashing any new boot.img.
mrmazak said:
Did you need to have magisk?
And what build version boot.img do you have installed.
I see in the ported Austin version of the lineage you are not flashing any new boot.img.
Click to expand...
Click to collapse
1- No. I use SuperSu
2- 5.6.3.4
Enviado desde mi Mi A2 mediante Tapatalk
Rortiz2 said:
1- No. I use SuperSu
2- 5.6.3.4
Enviado desde mi Mi A2 mediante Tapatalk
Click to expand...
Click to collapse
Thanks, the superSU that is preinstalled. Or flashed zip in TWRP.
Either way, I guess I need to try again on my 5th gen. Lineage install. Cause it should have worked, then.
mrmazak said:
Thanks, the superSU that is preinstalled. Or flashed zip in TWRP.
Either way, I guess I need to try again on my 5th gen. Lineage install. Cause it should have worked, then.
Click to expand...
Click to collapse
SuperSu by ChainFire
Enviado desde mi Mi A2 mediante Tapatalk
Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ
mzakharocsc said:
Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ
Click to expand...
Click to collapse
I'm sure you know this already, but there's a magisk module that does that already.
If I was to build a kernel I would try and definitely build something that has smoother performance or slightly better battery life.
Keep up the efforts. It is a shame there are no custom kernels for the phone...
Burt Squirtz said:
I'm sure you know this already, but there's a magisk module that does that already.
Click to expand...
Click to collapse
If you are talking about this: https://github.com/evdenis/selinux_permissive , then having tried it it did not work. On their own XDA thread, they state 'The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels'. Unless I am missing something here?
Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.
mzakharocsc said:
Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.
Click to expand...
Click to collapse
commenting that line will brake your image, we need llvm to make bootable kernel.
afaneh92 said:
commenting that line will brake your image, we need llvm to make bootable kernel.
Click to expand...
Click to collapse
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.
mzakharocsc said:
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.
Click to expand...
Click to collapse
By reading Makefile you can find it there.
afaneh92 said:
By reading Makefile you can find it there.
Click to expand...
Click to collapse
Yeah, I read the makefile. LLVM flag is supported there, but unset/unused by default, resulting in corrupt images. and you have to somehow know that you need to set it externally.
If someone build a good custom kernel wich improves battery and performance i will donate 100 usd
I want custom kernels too.
Would it be possible to make a bounty?
I'm interested in battery, hackability, booting time, stability and performance.
songoku1 said:
If someone build a good custom kernel wich improves battery and performance i will donate 100 usd
Click to expand...
Click to collapse
Are there some official XDA bounty program for this stuff?
timofonic said:
Are there some official XDA bounty program for this stuff?
Click to expand...
Click to collapse
Sadly no on my oneplus i use arter kernel and i absolutely lovibg it. Sadly for my s21u there isnt one :/
What's more important now is to stress samsung's opensource service to release the AUG4 kernel source
DaReDeViL said:
What's more important now is to stress samsung's opensource service to release the AUG4 kernel source
Click to expand...
Click to collapse
Already requested it.
interested in a custom kernel also, it's already a very good device but battery life needs to be better
afaneh92 said:
Already requested it.
Click to expand...
Click to collapse
Got it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
I will rebase my kernel soon
Ok
DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
Hope we will see a custom kernel soon
Any news?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project Official
For SM-T210(R)/SM-T211 (lt02)
USE AT YOUR OWN RISK!
Please make sure to this thread if you like the port! ​
ISSUES
Temperature is not available because the kernel does not support it.
Google apps install does not work (Fixed in latest nightly release!)
DOWNLOADS
All nightly releases are on our build repository. DOWNLOAD
All standard releases are on the TWRP website. DOWNLOAD
LINKS
Source Code
Discord Server
CREDITS
@Jespert
@TriDiscord
@gr8nole
@ketut.kumajaya
@paziusss
@ruben15prd
Reserved -
Thanks for maintaining TWRP for this almost 9 year old tablet! It's about time it gets official support. Works perfectly on my SM-T2105.
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
We'll probably never get a custom ROM except for modified stock ones anyways lol.
throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
CM11 exist, there are plans to fix bugs.
throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
uhh, cyanogenmod 11 recieved its last update for this tablet 7 years ago, so it's been around for a damn long time
gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0
TriDiscord said:
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0
Click to expand...
Click to collapse
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.
throwaway019299292 said:
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.
Click to expand...
Click to collapse
This is the line as the final result:
TARGET_OTA_ASSERT_DEVICE := lt02wifi,lt02wifijpn,lt02wifizc,lt02wifizs,lt02wifiue,lt02kidswifi,lt02kidswifiub,lt02kidswifiue,lt02kidswifiww,lt02kidswifixw,lt02kidswifizc,lt02kidswifizh
Will merge when other changes are completed. Thanks!
This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!
CaptainBenSisko said:
This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!
Click to expand...
Click to collapse
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Hehe, I understand. It takes so much time.
CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Any GitHub sources? We can maybe try to help?
TriDiscord said:
Any GitHub sources? We can maybe try to help?
Click to expand...
Click to collapse
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.
CaptainBenSisko said:
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.
Click to expand...
Click to collapse
Those are very buggy sources for CyanogenMod 11. I doubt that 14.1 will work on this.
@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.
retiredtab said:
@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.
Click to expand...
Click to collapse
I'm just curious, has anyone tried MM yet?
I think I found a guy who got lollipop to work on the t210r but it was canceled
HackerMan195 said:
I think I found a guy who got lollipop to work on the t210r but it was canceled
Click to expand...
Click to collapse
Ooh! Could you share a link?