Related
XDAndroid 2.2.2 Build FRX07
Kernel: Duckly's turbo kernel with keypad drivers not as modules (25-03-2010)
How to:
1. First, get "FRX07.1_Full_Bundle_20110901.zip" from XDAndroid website.
2. Add and replace the next files to the root XDAndroid bundle: "modules-2.6.27.46.tar.gz", "zImage", "haret.exe", "STARTUP.TXT" and "ts-calibration".
3. Install the new bundle following the instructions.
Instructions:
* Format the SD card in FAT32 with a 32kb cluster size.
* Unzip the .zip file using WinRAR or 7zip.
* Then you will get a bunch of files.
* Copy all the files in the root of the memory card.
* Don't copy them in a folder just in the root otherwise android will not work.
* Run "haret.exe" from the File Explorer. Be patient, wait till xdandroid rom is fully installed.
* Turn off and run "haret.exe" again so it will be fast & stable. (If you have the dual boot installed "haret.exe" runs automatically. See lines below).
Working:
* WiFi. You can turn off and turn on without problems
* Overclocked to 652MHz
* Graphics [24.5 FPS]
* GPS
* Market
* 3G Network
* Phone Speaker (If you get problems turn speaker on and off)
* 3D Acceleration
* Bluetooth
* Awesome Battery Life
* Battery Indicator (Very Accurate)
* Smooth Animations
* Browser
* Gmail
* Backlight Control
DualBoot from Windows Mobile:
1. First find "Gen.Y DualBOOT v1.0.6.0-CAB.zip" from: http://forum.xda-developers.com/showthread.php?t=623792
2. After extract "Gen.Y DualBOOT WVGA v1.0.6.0-Storage Card.cab" into your SD card, you have to install it to \Storage Card, not \Windows.
3. After install it from windows mobile, you have to edit your registry using "Total Commander". The registry location is at [\\\Plugin\Registry\HKCU\Software\Gen.Y\DualBOOT]
4. Find a registry named "AndroidBootFolder", click it and check whether the content is blank. I've left a list describing what the keys are for:
* "AndroidBootFolder"="string" ("": boot from root of storage (e.g. \Storage Card\haret.exe)| "andboot": boot from \Storage Card\Andboot\haret.exe, string can be edited in registry)
* "AutoBootAndroid"=dword:1 (1: boot Android | 0: boot Windows)
* "AutoBootEnabled"=dword:1 (1: enable autoboot | 0: disable autoboot)
* "FastBootEnabled"=dword:0 (1: enable fastboot | 0: disable fastboot)
* "StorageBootMode"=dword:0 (1: boot from Storage Card (SDMemory) | 0: boot from Internal Storage (moviNAND))
Wifi-Tether 3.1 Beta 6:
1. Install "wifi_tether_v3_1-beta6.apk".
2. Launch the app.
3. Go to "settings".
4. Then go to "Change Device-Profile" and choose HTC Desire (GSM) and start tethering.
5. Without stop tethering go again to "settings>Change Device-Profile>" and choose HTC Dream.
6. Now stop tethering and start again.
Note:
I'm not either developer or programmer. All merit goes to XDA folks.
Screenshots:
Great Job. Thankssss
h_pro9x said:
Great Job. Thankssss
Click to expand...
Click to collapse
Not at all. I've just joined what other did before. All merit goes to the real developers, in especial to XDAndroid.
Best.
any screenshots ?
I've left two screenshots.
Best.
kuskro said:
I've left two screenshots.
Best.
Click to expand...
Click to collapse
thank you =)
Hows the battery performance?
legalmantra said:
Hows the battery performance?
Click to expand...
Click to collapse
Awesome if you use Duckly's Kernel. If you use XDAndroid kernel very bad.
If you are going to use this rom for tethering, do it always charging the battery.
Best.
kuskro said:
Awesome if you use Duckly's Kernel. If you use XDAndroid kernel very bad.
If you are going to use this rom for tethering, do it always charging the battery.
Best.
Click to expand...
Click to collapse
what duckly's monster kernel should i use?
KERNELS WITH KEYPAD DRIVERS NOT AS MODULES
Duckly's Kernel [Monster Kernel] [26-3-2011]
or
KERNELS WITH KEYPAD DRIVERS AS MODULES
Duckly's Kernel [Monster Kernel] [27-3-2011]
ueharaf said:
what duckly's monster kernel should i use?
KERNELS WITH KEYPAD DRIVERS NOT AS MODULES
Duckly's Kernel [Monster Kernel] [26-3-2011]
or
KERNELS WITH KEYPAD DRIVERS AS MODULES
Duckly's Kernel [Monster Kernel] [27-3-2011]
Click to expand...
Click to collapse
I'm using the Keypad drivers NOT as modules one and everything is working fine so far
ueharaf said:
what duckly's monster kernel should i use?
KERNELS WITH KEYPAD DRIVERS NOT AS MODULES
Duckly's Kernel [Monster Kernel] [26-3-2011]
or
KERNELS WITH KEYPAD DRIVERS AS MODULES
Duckly's Kernel [Monster Kernel] [27-3-2011]
Click to expand...
Click to collapse
Well, you can use Turbo or Monster kernels with keypad drivers not as modules. The one I'm using is the turbo (25-03-2011).
but i have Sleep Of Death problem. Do you have the same problem?
ryo2456 said:
but i have Sleep Of Death problem. Do you have the same problem?
Click to expand...
Click to collapse
SOD is because of the kernel, it is supposed the turbo kernel avoid SOD, but sometimes don't. Try with the monster kernel. I prefer the turbo one but monster solve the problem. Try to set the overclock around 600mhz.
As well, if you don't use either wifi or BT you can try with the XDAndroid kernel included in the bundle.
however, I only use wifi .
I'll try the monster kernel if i get SOD again.
thanks for your help.
Speed is awesome, battery life is already better than the previous builds I've used, but still cannot last longer than 4hrs with Wifi / 3G on.
[email protected] said:
Speed is awesome, battery life is already better than the previous builds I've used, but still cannot last longer than 4hrs with Wifi / 3G on.
Click to expand...
Click to collapse
Try SenseDroid v7, is a great rom as well. Please compare the battery life between both rom and post again with the result.
I cant get it working in dynamics 2.4 rom...
it gets stuck in the loading screen with the latest word: busy
i formatted it in fat 32 but not 32kb max is only 16 kb
and I followed all instuctions...
what can I do?
[email protected] said:
Speed is awesome, battery life is already better than the previous builds I've used, but still cannot last longer than 4hrs with Wifi / 3G on.
Click to expand...
Click to collapse
Wi-fi sucks a lot of battery(my battery lasts 2h with wi-fi,but on my diamond lasted 12-14h without it) ,if you want to do a battery life test,don't use wi-fi at all
helicopter88 said:
Wi-fi sucks a lot of battery(my battery lasts 2h with wi-fi,but on my diamond lasted 12-14h without it) ,if you want to do a battery life test,don't use wi-fi at all
Click to expand...
Click to collapse
I've not compared this FAT32 rom with others because I use my xperia as a wifi-tether router and I always use the charging cable. And with the Faryaab FAT32 rom is not possible use wifi-tether. So I can compare.
From your point of view, which is the best rom and kernel for using wifi?
samsamx said:
I cant get it working in dynamics 2.4 rom...
it gets stuck in the loading screen with the latest word: busy
i formatted it in fat 32 but not 32kb max is only 16 kb
and I followed all instuctions...
what can I do?
Click to expand...
Click to collapse
disable overclock
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
Support for Governors---
Interactive
Performance
PowerSave
Userspace
Optimizations and Tweaks---
Disabled CRC-Check for upto 30% faster I/O.
Support for Dynamic-FSync (adjusts FSync according to usage resulting in a significant boost in the I/O performance).
Reduced RQ Lock-Contention for upto 0.7% increase in Performance.
Install
Copy the zip to your external or internal memory
Boot to twrp
Select the zip.
Reboot to system
Download-- Note 3 Neo (3g/4g)
XDA:DevDB Information
FireKernel for LP (5.1.x) ROMs (3g/4g), Kernel for the Samsung Galaxy Note 3 Neo
Contributors
FireLord, franciscofranco,Shoaib05
Source Code: https://github.com/FireLord1/android_kernel_samsung_smdk5260/commits/FireKernel-lp
Kernel Special Features: battery life
Version Information
Status: Beta
Created 2016-10-08
Last Updated 2016-10-08
ChangeLog
v1
Code:
FireLord1 - script: use google gcc 4.8
franciscofranco - Reduced RQ Lock-Contention for upto 0.7% increase in Performance
Shoaib0597 - Optimized task_sched_runtime for upto 20% increase in Performance
Shoaib0597 - Added support for CRC Toggle
Shoaib0597 - Reduced OverHead
Shoaib0597 - Enabled ARCH-Power feature
Joonsoo Kim - slub: fix a possible memory leak
franciscofranco - Remove '+' symbol from kernel version string
franciscofranco - drivers: mmc: according to the comment left by the original author disabling a cyclic redundancy check on data blocks by yield a a performance improvement hovering ~30%
Francisco Franco - backport https://lists.linuxfoundation.org/pipermail/ltsi-dev/2013-December/002683.html from Kernel 3.10 workqueue: use a higher bit to give more space to actual non-internal flags
franciscofranco - ksm: check and skip page, if it is already scanned
franciscofranco - sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire. From http://ripke.com/loadavg/moire
franciscofranco - Added fsync on/off support.
Greg Kroah-Hartman - Linux 3.4.40
FireLord1 - Linux: FK: r1
FireLord1 - script: zip: add building script and all
FireLord1 - defconfig: renamed to match script
Reserved
* This is my Kernel from osprey (moto g3). this may not have much features as compared to my first kernel release bcz that is for qcom and in exynos i cant do much BUT ill try to maintain main thing which is common. i.e battery life
* osprey: http://forum.xda-developers.com/2015-moto-g/orig-development/firekernel-v1-0-mm-6-0-x-roms-t3401538
* This is for single sim exynos galaxy note 3 neo.
* Compatible with all the custom roms.
* Can work for stock rom too but one thing will not work that is USB PC connection bcz i have edited the files for cm so..
* Its still using google GCC, will test uber GCC if that seems stable ill cook and give here.
* Well not much features but but.. ill upstream till 3.4.112 one Day!
* As always i dont own note 3 neo but i like to make stuff for it. Thanks to my testers 3g and 4g both.
It's very nice to see this Kernel coming from our osprey. It's the nice kernel for Osprey. Hope it's smooth & stable like osprey for exynos too
Huge kudos for you to work on 'Exynos' like SoC. Best of luck.
Thank you for your dedicated work brother. Appreciate it, and keep it up ?✌?
Thanks, waiting for N7502 custom ROM
Good job @FireLord
It doesn't save wifi when I reboot...I am on stock Why? :/ please help me cause I really need a costume kernel and I really appreciate your work! @FireLord
JimmygreecePanathinaikos said:
It doesn't save wifi when I reboot...I am on stock Why? :/ please help me cause I really need a costume kernel and I really appreciate your work! @FireLord
Click to expand...
Click to collapse
Wooah. Sorry to hear that.. Can you tell your device? I'm not sure if I can fix..
Sent from my MotoG3 using Tapatalk
FireLord said:
Wooah. Sorry to hear that.. Can you tell your device? I'm not sure if I can fix..
Click to expand...
Click to collapse
Samsung galaxy note 3 neo 4g version stock Android 5.1.1 Thanks for the fast reply I hope you will find something to fix this.. You always do!!
JimmygreecePanathinaikos said:
Samsung galaxy note 3 neo 4g version stock Android 5.1.1 Thanks for the fast reply I hope you will find something to fix this.. You always do!!
Click to expand...
Click to collapse
umm dunno how stock works.. try deleting /system/lib/module (whole module folder) it is not required cuz kernel has it inbuilt now.. please make backup before doing anything
FireKernel for SM-N7507 (hlltezt)
This is FireKernel with fixed Deadlock bug
Download: AFH
FireLord said:
umm dunno how stock works.. try deleting /system/lib/module (whole module folder) it is not required cuz kernel has it inbuilt now.. please make backup before doing anything
Click to expand...
Click to collapse
I always have backups... You don't say on the steps if we have to do a simple wipe/cache after installing the rom.. Could this be my problem for no savings wifi passwords after reboot??
JimmygreecePanathinaikos said:
I always have backups... You don't say on the steps if we have to do a simple wipe/cache after installing the rom.. Could this be my problem for no savings wifi passwords after reboot??
Click to expand...
Click to collapse
Yea try wiping after flashing kernel.. But hey? Why you keep on rebooting ?
Sent from my MotoG3 using Tapatalk
FireLord said:
Yea try wiping after flashing kernel.. But hey? Why you keep on rebooting ?
Click to expand...
Click to collapse
I installed a xposed module after your kernel so I had to soft reboot
JimmygreecePanathinaikos said:
I installed a xposed module after your kernel so I had to soft reboot
Click to expand...
Click to collapse
Oh.. Then try wiping cache
Sent from my MotoG3 using Tapatalk
Thx for your work. Will try the new kernel with stock rom in a few days.
Sent from my SM-N7505 using XDA-Developers mobile app
does this kernel fix camera issue or calling audio in cm-based roms ?
SAMSUNG Galaxy Note 3 neo
moss20 said:
does this kernel fix camera issue or calling audio in cm-based roms ?
SAMSUNG Galaxy Note 3 neo
Click to expand...
Click to collapse
Its just custom kernel.. Not bug fixing kernel please test it may fix
Sent from my MotoG3 using Tapatalk
biggoof75 said:
Thx for your work. Will try the new kernel with stock rom in a few days.
Click to expand...
Click to collapse
When you try please tell us if your wifi passwords are deleted after every reboot
These boot images should work on any LOS-based or CAF-source based ROMs (in theory).
Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
Kernel Information
ROM Target Device: Samsung Galaxy Grand Prime SM-S920L | SM-G530MU | SM-G530M | SM-G530H | SM-G530FZ | SM-G530P | SM-G530T | SM-G530T1 | SM-G530W
Kernel Status: Beta
Project GitHub Repositories: https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
Project GitHub Branch: cm-14.1-experimental
Project Gerrit Review site: https://review.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Bug reports: https://bugs.msm8916.com/
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530M[/B] - [COLOR="DarkSlateBlue"][B]fortunalteub[/B][/COLOR]
[B]SM-G530H (XX)[/B] - [COLOR="DarkSlateBlue"][B]fortuna3g[/B][/COLOR]
[B]SM-G530H (XC)[/B] - [COLOR="DarkSlateBlue"][B]fortunave3g[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
[B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]
Click to expand...
Click to collapse
Features
Code:
[B]
[COLOR="Red"]
* Latest CAF kernel source merged into kernel.
* CPU overclock to 1612 MHz
* GPU overclock to 650 MHz
[/COLOR]
* If you have any (reasonable) suggestions
for anything, tell me.
[/B]
DownloadAll Jenkins builds are testing builds, and as such, are likely to be extremely unstable or unusable.
This goes doubly for these kernels: You know the risks associated with overclocking, and, though stable,
there may be hiccups in the kernel.
Kernel Builds: https://jenkins.msm8916.com/job/Boot_Images/job/Overclocked_Images/job/Samsung_Galaxy_GRAND_Prime/
RSS: https://jenkins.msm8916.com/job/Boot_Images/job/Overclocked_Images/rssLatest
Click to expand...
Click to collapse
Instructions
If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).
You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.
Click to expand...
Click to collapse
Installation via recovery (TWRP)
* Download a recent .tar file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Plug in your phone into your computer, extract the tar file and place the .img to a location on your Internal or External Storage on a device.
* Click Install on TWRP on your phone and locate the img file in the phone.
* Enjoy your kernel.
Click to expand...
Click to collapse
Installation via odin
* Download a recent .tar file from the links above for your device.
* Reboot into ODIN mode [Press Power+Volume Down+Home].
* Plug in your phone into your computer, and open the Odin application, and place the .tar file in the AP slot and flash it.
* Enjoy your kernel
Click to expand...
Click to collapse
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
PLEASE, don't PM @vince2678, as he's busy right now, and your questions can be not answered. PM @kentone instead, write here on the post, or on the telegram group, your questions will be responded as soon as we can Understand that we have family, studies and jobs aside of this project. Thanks for your understanding
XDA:DevDB Information
[KERNEL] Overclocked Kernel for Galaxy Grand Prime [SM-S920L|SM-G530M/MU/H/P/T/T1/W], Kernel for the Samsung Galaxy Grand Prime
Contributors
vince2678
Source Code: https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
Kernel Special Features:
Version Information
Status: Beta
Created 2017-04-16
Last Updated 2017-08-29
Reserved
Changelog
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added support for SM-G530M (fortunalteub)[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the
latest build. This was due to the failure to set a
critical kernel variable at boot because the kernel init
system was not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
mounting and formatting should be working fully.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
Code:
[B][U]14/04/2017[/U][/B]
* [B] [ [COLOR="Red"]ALL[/COLOR] ][/B] [B] Created DevDB project [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built into the kernel. Should
(slightly) improve speed of enabling/disabling wifi. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.14[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]fortuna3g[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Brightness adjustment is broken[/B]
Thanks!
Reserved.
Great work Vince! Gonna try it soon nd will let you know.
Maybe stupid question
But if CPU overclocked to 1612
It won't be damaged or something
I mean why Samsung didn't make GP stock CPU like this ??
Sorry if its stupid question
But if it won't damage the phone CPU
The performance will increased as hell
abooooood said:
Maybe stupid question
But if CPU overclocked to 1612
It won't be damaged or something
I mean why Samsung didn't make GP stock CPU like this ??
Sorry if its stupid question
But if it won't damage the phone CPU
The performance will increased as hell
Click to expand...
Click to collapse
All processors are put limits, snapdragon 410 goes up to 2.1ghz, but it's like asking the mobile phone does not last a month, Do you use xxu or xcu?
Play4NoobWin said:
No boot in xcu
Got stuck in the samsung logo
Tested in aex 4.0
Click to expand...
Click to collapse
Sorry, my fault. Meant to write 'XXU' instead of 'XCU'.
Will make a build for that soon, keep wacthing the thread.
abooooood said:
Maybe stupid question
But if CPU overclocked to 1612
It won't be damaged or something
I mean why Samsung didn't make GP stock CPU like this ??
Sorry if its stupid question
But if it won't damage the phone CPU
The performance will increased as hell
Click to expand...
Click to collapse
I've been using it myself for about a month with no adverse effects.
I chose 1612Mhz because it's fast enough without risking instability. At higher frequencies the memory might not be able to keep up with the cpu/gpu clock, so I have not gone higher than that (though they may work).
vince2678 said:
I've been using it myself for about a month with no adverse effects.
I chose 1612Mhz because it's fast enough without risking instability. At higher frequencies the memory might not be able to keep up with the cpu/gpu clock, so I have not gone higher than that (though they may work).
Click to expand...
Click to collapse
OK thanks for reply
I will keep watching thread for xcu ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:44 PM ----------
Play4NoobWin said:
No boot in xcu
Got stuck in the samsung logo
Tested in aex 4.0
Click to expand...
Click to collapse
What are the bugs of that ROM bro ?
No boot un xxu LOS 14.1
You only see SAMSUNG GALAXY GRAND PRIME.
I USE TRANSLATOR
I Test 13.0
when will you make XCU build ?
@[email protected]
vince2678 said:
I've been using it myself for about a month with no adverse effects.
I chose 1612Mhz because it's fast enough without risking instability. At higher frequencies the memory might not be able to keep up with the cpu/gpu clock, so I have not gone higher than that (though they may work).
Click to expand...
Click to collapse
+1
On 2GB devices it could've been useful but battery consuming as well. Whats the minimum frequency you've set? I suggest you to set to 200Mhz, that will greatly save the battery.
abooooood said:
OK thanks for reply
I will keep watching thread for xcu ?
Click to expand...
Click to collapse
AhMaD eLMoMaNi said:
when will you make XCU build ?
@[email protected]
Click to expand...
Click to collapse
You should wait but please ETA is not allowed.
He'll soon make a build for xcu as well but till then Keep Calm nd Enjoy!
Has.007 said:
+1
On 2GB devices it could've been useful but battery consuming as well. Whats the minimum frequency you've set? I suggest you to set to 200Mhz, that will greatly save the battery.
Click to expand...
Click to collapse
The minimum was already at 200MHz, but thanks for the insight anyways .
he already mentioned for LOS so it may not work for aex
G530T on LOS 13. All seems fine here and over clock is functional. Thanks Vince.
At first thanks alot for this great work ,this OC is very safe and SUPERFAST .but Unfortunately Wifi isn't working on 530H (XCU) LOS 14.1 .This is the Logcat that I've got
I've a few skills on Linux system I can help you to test things if you want.
Code:
04-19 00:20:18.061 1612 2587 D WifiService: setWifiEnabled: true pid=8244, uid=1000
04-19 00:20:18.063 1612 2407 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
04-19 00:20:18.072 1612 2407 D WifiHW : finit_module for "/system/lib/modules/wlan.ko" failed: Exec format error
04-19 00:20:18.072 1612 2407 E WifiStateMachine: Failed to load driver
04-19 00:20:18.075 1612 1612 E WifiController: WifiControllerWifi turn on failed
----I've not found fast charge on Kernel Adiutor , i think you've upload a kernel for another device or something like this ,cuz wlan.ko seems to now be loaded
SM-G530H (XXU) wifi not working
Wifi also isn't working for me on the G530T with the 4/7 build of cm13, but when i use the nightly for 4/16 it works, but then I get no outgoing call audio, but then again I was still getting no outgoing call audio without using the kernel on that build
AhMaD eLMoMaNi said:
At first thanks alot for this great work ,this OC is very safe and SUPERFAST .but Unfortunately Wifi isn't working on 530H (XCU) LOS 14.1 .This is the Logcat that I've got
I've a few skills on Linux system I can help you to test things if you want.
----I've not found fast charge on Kernel Adiutor , i think you've upload a kernel for another device or something like this ,cuz wlan.ko seems to now be loaded
Click to expand...
Click to collapse
The fast charging is not something that has an exposed sysfs interface so it's not configurable.
Clvers said:
SM-G530H (XXU) wifi not working
Click to expand...
Click to collapse
As for the wifi, it has to do with the fact that your devices use a wifi module instead of one built into the kernel. I'll work on a flashable fix for this later this week.
DanteDFG said:
Wifi also isn't working for me on the G530T with the 4/7 build of cm13, but when i use the nightly for 4/16 it works, but then I get no outgoing call audio, but then again I was still getting no outgoing call audio without using the kernel on that build
Click to expand...
Click to collapse
Yes, we switched to using a built in wifi module on the roms i make, so an upgrade is necessary to use the kernel.
vince2678 said:
Yes, we switched to using a built in wifi module on the roms i make, so an upgrade is necessary to use the kernel.
Click to expand...
Click to collapse
So since we'd have to upgrade to use it, and that 4/16 one was a test build and not nightly is it safe to assume the next LO13 nightly will have the in-call audio fixed? I can't hear anything not even if it's ringing the phone unless i switch speaker phone on and off. Or the gprimelte not recieving any more LOS13 builds? I see only LOS14 avail now for it but it has no themes and doesn't update/refresh the screen when watching videos on the browser unless i start dragging my finger across the screen while it loads...
Code:
Warning, this is a custom Kernel which is not developed by Samsung. I'm not responsible of eventual bugs that can append, bricks and any problem. So please, do a backup in TWRP before installing this. By installing this Kernel, you agree with this disclaimer.
Velocity Kernel v14.1 [latest build] for all Nougat ROMs full flashing procedure.(It is advised to store the kernel zip file in your internal storage as storing in external storage may cause some issues.)The Kernel is compatible with all YU Devices having Nougat OS and all other devices having Nougat 7.1.1 support like Resurrection Remix,Lineage OS,AOKP, AOSP etc.
it dont support Resurrection Remix 7.1.2 And Lineage OS 7.1.2
Test Version
Unknown
Bugs
PM Me if It Doesn't Boot in that Model
For which models my man?
Fild5x said:
For which models my man?
Click to expand...
Click to collapse
What Model U have? A 2015 , A 2016 , A 2017 ?
a500h 20 15
Fild5x said:
a500h 20 15
Click to expand...
Click to collapse
I didn't tested that model yet but it may work?
Ok but please maybe stupid question, on which roms stock or custom do think I can use this? If stock, then which one would you suggest I download and install?
Fild5x said:
Ok but please maybe stupid question, on which roms stock or custom do think I can use this? If stock, then which one would you suggest I download and install?
Click to expand...
Click to collapse
Works Stock ROM/ doesn't work in custom ROM because it may not be Compatible
Thanks for the response. So I need to download a noogat 7.1.1 stock rom? I am thinking, there is no stock nougat rom for a500h. Therefore can I use stock marshmallow? Please forgive ny nubeness.
Fild5x said:
Thanks for the response. So I need to download a noogat 7.1.1 stock rom? I am thinking, there is no stock nougat rom for a500h. Therefore can I use stock marshmallow? Please forgive ny nubeness.
Click to expand...
Click to collapse
Try if it works if it dozen boot PM Me
Ok. I will
Hi , on which model this kernel turn
ÉNITSED said:
Hi , on which model this kernel turn
Click to expand...
Click to collapse
Any A Model But only in Nougat stock rom
@AnotherOneTest, I think you don't know anything about kernel or ROM. Why do you keep bringing stuffs from other devices? (even not samsung!)
https://forum.xda-developers.com/yu...elocity-kernel-64-bit-lollipop-5-1-1-t3253776
But.. one kernel for all devices?! What?
Markxdx said:
But.. one kernel for all devices?! What?
Click to expand...
Click to collapse
Yes.. Feradroid engine can support all device too
Sent from my Samsung SM-A500F using XDA Labs
jjjhitel said:
@AnotherOneTest, I think you don't know anything about kernel or ROM. Why do you keep bringing stuffs from other devices? (even not samsung!)
https://forum.xda-developers.com/yu...elocity-kernel-64-bit-lollipop-5-1-1-t3253776
Click to expand...
Click to collapse
Trying hard to get thanks, I bet. Please close thread.
XenRon said:
Trying hard to get thanks, I bet. Please close thread.
Click to expand...
Click to collapse
Well Its Not Taken From Closed Thread its just a modified
Kernel. Well The Name is the same from Closed Thread idk
There to find that thread i guess its just the are same.
AnotherOneTest said:
Well Its Not Taken From Closed Thread its just a modified
Kernel. Well The Name is the same from Closed Thread idk
There to find that thread i guess its just the are same.
Click to expand...
Click to collapse
Dude our device is not a yu device even your op states so. You didn't even credit anybody or open source it.
AnotherOneTest said:
Well Its Not Taken From Closed Thread its just a modified
Kernel. Well The Name is the same from Closed Thread idk
There to find that thread i guess its just the are same.
Click to expand...
Click to collapse
Just close this thread yourself.
updater-script
Code:
package_extract_dir("tools", "/tmp");
ui_print("---------------------------------------");
ui_print("Flashing [B]Velocity Kernel[/B] (64-BIT) v14.1");
ui_print("---------------------------------------");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
set_perm(0, 0, 0777, "/tmp/flash_kernel.sh");
ui_print("The Most");
run_program("/tmp/flash_kernel.sh");
ui_print("Efficient Kernel");
delete("/tmp/boot.img");
delete("/tmp/mkbootimg");
delete("/tmp/unpackbootimg");
delete("/tmp/flash_kernel.sh");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
delete("/system/bin/ims_rtp_daemon");
delete("/system/lib/modules/wlan.ko");
delete("/system/etc/init.d/Velocity-Core_Settings");
package_extract_dir("system", "/system");
set_perm(0, 0, 0755, "/system/etc/init.d/Velocity-Core_Settings");
unmount("/system");
ui_print("for [B]Yu-Devices[/B]");
ui_print("----------------------------");
ui_print("Developed by [B]Shoaib Anwar[/B] :)");
ui_print("----------------------------");
Thread closed.
Clearly, this is not developed by the OP, and doesn't appear to be for this device. Not only that there are no credits or kernel source.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version of LineageOS 19.1 for our Samsung Galaxy Note 10.1 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a BETA build, also on the LineageOS side, so don't install it if you want a complete and stable rom and don't report my already listed bugs!
When you have BitGapps installed, you have to reflash them after every update!
Here you can see how far everything is working for now.
Spoiler: Whats working
N8000, N8010, N8013, N8020:
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
GPS
Wifi
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus with gestures and hovering icon
RIL
sec_keyboard docking station
much more...
Spoiler: Whats not working
Random reboots
Long screenshot
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N8000 / N8005 Rom
N8010 / N8013 Rom
N8020 Rom
ROM Mega
Magisk zip file
Spoiler: Changelog
23.11.2021
29.11.2021
01.12.2021
26.12.2021
28.12.2021
04.03.2022
15.03.2022
26.03.2022
03.04.2022
04.04.2022
20.04.2022
27.04.2022
06.05.2022
25.06.2022
23.09.2022
20.01.2023
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
https://androidfilehost.com/?fid=7161016148664799666
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
In some cases the sim card becomes unusable while typing in the code.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs?
Now you can use my app to access all boeffla sound configurations.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][N8000/N801x/N8020][BETA] LineageOS 19.1, ROM for the Samsung Galaxy Note 10.1
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2021-11-18
Last Updated 2023-01-20
Wow, looking forward to a new beginning
Kindly add the original bootsplash script to restore to original bootsplash ...
This rom changed my bootsplash. Pls add the zip to revert it if anyone want to switch back ....
The rom is running super smooth without gapps
Bugs -:
•) The Quick Settings in Portrait mode is not adjusting to the device size ...
The notifications also get squeezed
•) Lock Icon on lockscreen is upside-down
•) Taskbar Modification from settings not working
I'll add more if I found
Thx
@html6405
Also, does this rom support OTA ?
And is there any Device Group on telegram or anywhere else ?
Ayushskull said:
Kindly add the original bootsplash script to restore to original bootsplash ...
This rom changed my bootsplash. Pls add the zip to revert it if anyone want to switch back ....
Click to expand...
Click to collapse
Check out this post:
LineageOS 18.1 Android 11 for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 Beta EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
Ayushskull said:
Bugs -:
•) The Quick Settings in Portrait mode is not adjusting to the device size ...
The notifications also get squeezed
•) Lock Icon on lockscreen is upside-down
•) Taskbar Modification from settings not working
Click to expand...
Click to collapse
You're right, there are many more bugs, many settings are still missing / incomplete.
It's in a real early stage.
Ayushskull said:
Also, does this rom support OTA ?
And is there any Device Group on telegram or anywhere else ?
Click to expand...
Click to collapse
Yep, OTA does work and no, there is no group.
Which branch did you use to build the ROM? Is the repo manifest available somewhere?
SD card used for extra tablet storage failed too........
chgans said:
Which branch did you use to build the ROM? Is the repo manifest available somewhere?
Click to expand...
Click to collapse
lineage-19.0, but they aren't up to date, I will push them soon.
aliveday said:
SD card used for extra tablet storage failed too........
Click to expand...
Click to collapse
Thx, i thought that it will be the same case, it's the same Kernel .
If the sdcard is formatted as a portable storage, it should work.
But this bug is listed above.
html6405 said:
lineage-19.0, but they aren't up to date, I will push them soon.
Thx, i thought that it will be the same case, it's the same Kernel .
If the sdcard is formatted as a portable storage, it should work.
But this bug is listed above.
Click to expand...
Click to collapse
I will keep hope this can be fixed！In the process of trying this, i found that the TWRP of another phone can format the SDcard, Is it possible to add this feature to our TWRP, but the recovery partition of our device is a bit too small.
aliveday said:
I will keep hope this can be fixed！
Click to expand...
Click to collapse
Me too ,
aliveday said:
i found that the TWRP of another phone can format the SDcard, Is it possible to add this feature to our TWRP, but the recovery partition of our device is a bit too small.
Click to expand...
Click to collapse
I had to remove some file systems from TWRP because of the limited space,
but TWRP should be able to format your sd card to exfat.
html6405 said:
Me too ,
I had to remove some file systems from TWRP because of the limited space,
but TWRP should be able to format your sd card to exfat.
Click to expand...
Click to collapse
If there is a trade-off, i suggest the language file can be deleted. just keep English，the TWRP operation is very simple.
aliveday said:
If there is a trade-off, i suggest the language file can be deleted. just keep English，the TWRP operation is very simple.
Click to expand...
Click to collapse
This would only work for not official versions,
in the official TWRP, we are already using the small language pack.
But I will have to find some space anyway for the next release.
Update 23.11.2021:
Fixed Bluetooth
Brought Livedisplay entry in settings back
Fixed partly Tethering
html6405 said:
Update 23.11.2021:
Fixed Bluetooth
Brought Livedisplay entry in settings back
Fixed partly Tethering
Click to expand...
Click to collapse
Thank you for all your hard work! I'm running this ROM currently and so impressed by the smoothness and speed throughout. Thanks again!
Hey, are you interested in making OC profile for them?, I wanna help
I can beta test / private test them and adjust voltages, I would have done that myself by decompiling the kernel to change the CPU0 seems kinda hardish right now since I don't have a lot of experience with that
I remember people were running the CPU around 1700-1750Mhz ish mark same on the 8" and Note 2
also, I noticed the GPU in this kernel isn't appearing in apps for some reason
after digging in I found it runs at 533mhz, the mali400MP can run at 600mhz
you can still make the kernel "Overclockable" by leaving it at stock speeds but adding 4-6 more tiers to scaling ava freq after 1600MHz as:
1650
1700
1725
1750
1775
1800
Edit/Forgot to say: I did some tests with it Running at performance governer at 1600mhz, it was a way smoother and far better experience, the interactive one either isn't fast enough or bad, I got around 300-400extra points in PC mark (from 2600 to 2950 average) that's around 14% increase in performance!
LightingX said:
Hey, are you interested in making OC profile for them?, I wanna help
Click to expand...
Click to collapse
Hi,
the kernel is already to the highest usable level overclocked.
I've enabled all the frequencies up to 1800 earlier (LOS16), but everything over 1600 MHz was too unstable,
so I've removed them.
LightingX said:
by leaving it at stock speeds
Click to expand...
Click to collapse
stock speed is 1400 MHz .
LightingX said:
Edit/Forgot to say: I did some tests with it Running at performance governer at 1600mhz, it was a way smoother and far better experience,
Click to expand...
Click to collapse
That's true, but it's less energy efficient, I recommend everybody to use Kernel aduiator to switch to performance after every boot (if they want to use it).
The problem is if I reenable the higher frequencies, people will try to overclock and land in a bootloop,
then they claim me for doing this...
html6405 said:
Hi,
the kernel is already to the highest usable level overclocked.
I've enabled all the frequencies up to 1800 earlier (LOS16), but everything over 1600 MHz was too unstable,
so I've removed them.
stock speed is 1400 MHz .
That's true, but it's less energy efficient, I recommend everybody to use Kernel aduiator to switch to performance after every boot (if they want to use it).
The problem is if I reenable the higher frequencies, people will try to overclock and land in a bootloop,
then they claim me for doing this...
Click to expand...
Click to collapse
can you at least provide the modified kernel boot.img with a warning?
I used to run this thing on a 1704Kernel if I remember correctly
the stock speed is in fact 1.4ghz, maybe I remember stuff from the note 2
I use FKM it works pretty well with me
LightingX said:
can you at least provide the modified kernel boot.img with a warning?
Click to expand...
Click to collapse
That would be possible.
LightingX said:
the stock speed is in fact 1.4ghz, maybe I remember stuff from the note 2
Click to expand...
Click to collapse
Its the same on note 2 , 1400 MHz on stock.
html6405 said:
Update 23.11.2021:
Fixed Bluetooth
Brought Livedisplay entry in settings back
Fixed partly Tethering
Click to expand...
Click to collapse
I still can't believe it, I already want to see it with my own eyes, brother, your work is incredible, thank you very much.
Hello,
Guys, I don't know if there will be a solution. But I read that Google intends to end the support of applications that use 32bis processors and it is already mandatory for developers to provide the 64bit version. And already have apps only in the 64bit version on the Play Store. The question is: Will we have a way around this and install 64bit apps on our tablet? Our old man still has a lot of wood to burn with the help of our friend Html6405 who is bringing Android 12 to us.