Here is a component manifest for the V, for purposes of building ICS
(THIS ISNT AN ICS DEV THREAD, IT'S JUST INFO: DO NOT ASK IF I AM MAKING ICS AS I AM NOT)
CPU: Qualcomm Snapdragon QSD8250: In Qualcomm driver source
GPU: Qualcomm Adreno 200: Qualcomm released driver source
Cellular: ?
Power management: Texas Instruments tps65023: In Qualcomm driver source
Camera: Omnivision OV8810: Driver from different device?
Capacative Sensors: Synaptics capsensor?: Possibly in kernal source
Wireless: Broadcom BCM4329: Source in CM9 linux kernal
Accelerometer: Bosch BMA150: Driver source available
eCompass: AKM akm8973: Source in android linux kernal
Touch: Atmel mxT224: Likely requires port? (if the V is like the S7, the driver is badly mangled by dell) [Part of porting kernel]
Basically, once we get a reasonably working kernel, it might be possible to get a fully working ICS port (possibly including camera too) without having to port any drivers ourselves.
The V looks like a potentially very easy device to update to ICS, it's unfortunate Dell didnt bother updating it nor do we have many devs.
The mxT224 also supports more then the 2 touch points we currently have, but dell badly botched up the drivers for the S7 (which uses the same controller), and likely did the same for the V
Hi, I wanted to try something for the Galaxy Player 4.0. I know that the hummingbird processor inside of it had a lot of potential and I want to extract all the power it has to offer . To do so I had to use any tools that could help me achieve that objective . Now enough with the talk and more with the actual content of this kernel. Note that this kernel works for both versions (US and Intl, Korea can work but it hasn't been tested).
Disclaimer: This is a MTD kernel, it will only work with CM based ROMS (CM10.1 and up). Flashing it in a GB ROM could result in a brick, Also I'm not responsible to any bricks caused by this kernel.
Features:
Linux 3.0.101
Compiled it using Christopher83 custom Linaro 4.7.4 toolchain optimised for Cortex-A8 chipsets (4.9.1 For Android 4.4 and up)
Cranked it up with -O3 optimisations and -Ofast optimsations for GPU
LZ4 Compression for kernel and crypto
OC available up to 1.2 GHz (through 100 MHz steps)
Available governors (8): Lulzactive, SmartassV2 Intellidemand, Conservative, Ondemand, Interactive, Userspace and Powersave.
Available I/O schedulers (5): Noop, Deadline, Fiops, Row, Cfq, Sioplus, Bfq (Row is enabled by default)
Updated GPU drivers ([email protected] )
Tweaked and optimised I/O schedulers
Sound improvements (ALSA, PCM)
ARM RWSEM optimisations
Optimised SLUB memory allocator
Timer slack controller support
Backported CPUidle from 3.5 kernel
Support for swap
CIFS
TUN
Zram
Ext4 optimisations
Fast Charge
Fast wifi while in standby
Support for OTG connectivity
NTFS and FAT read and write support
Undervolted the LCD panel by 20%
LMK backported from kernel 3.4
Minimum brightness lowered (Needs confirmation)
Always up-to-date with Bbelos and Cyanogenmod Aries sources
720p Video recording support
Download:
4.4:
r7.1: r7.1 CWM Download
r7: r7 CWM Download
r6: r6 CWM Download
r5: r5 Download
4.3:
r4.6: r4.6 Download
r4.5: r4.5 Download
r4: r4 Download
r3: r3 Download
4.2:
r2.1: r2.1 Download
r2: r2 Download
r1: r1 Download
Installation:
Flash the zip with CWM. (Yes it's that simple )
Note: with the newer version of CWM, you'll need to flash the zip from the internal sdcard ONLY. If you want to use the external sdcard to flash the zip, please mount the internal one first as it will cause your device to be stuck in the samsung logo.
Sources:
Here you can find my sources if you want to do something.
https://github.com/zaclimon/impulse_ypg1
Thanks:
Bbelos
Mevordel
DerTeufel
Kasper_h
Alberto96
DerRomtester
Christopher83
Android1234567
Koala888
Changelog:
4.4.x
r7.1 (26/06/14)
Compiled with 4.9.1 GCC from Christopher83 (2014.06)
Patched futex exploit (Towelroot)
r7 (27/05/14)
Synced with the dev repo
Smaller kernel size
Compiled with the 4.9.1 Optimized GCC from Christopher83. (2014.05)
r6 (18/04/14)
Synced with the *regular* aries repo
Compiled with the newer 2014-01 Christopher83's toolchain
Removed 1.3 and 1.4 GHZ OC for stability purposes, however I added 1.1 GHZ if you needed it.
Added the BFQ I/O Scheduler
Added support for the 720p video recording as well as some fixes for preview
Misc optimisations.
r5 (17/01/14)
Android 4.4 support (KitKat)
Stuff synced from the dev repo as well (Front cam fix, lvm etc...)
Changed some optimisation flags
Optimised with newer 2013-12 Christopher83 toolchain
Fixed some other stuff
4.3.x
r4.6 (17/02/14)
Fixed the rotation (for the camera)
Misc fixes
r4.5 (12/12/13)
Updated to Linux 3.0.101
Increased the voltage on 1.3 Ghz OC (should fix the SOD's)
Included the fix for newer CM and Pac-Man Roms
Updated to the 11/13 toolchain from Christopher89
r4 (14/10/13):
Upstream changes from bbelos and aries tree (resized the /system and /cache partition)
Added 1.1 and 1.3 GHZ OC steps
Backported Cpuidle from 3.5 (not deep idle as it's been reported that it causes stability issues)
Updated the GPU drivers to [email protected]
Added a new I/O scheduler: sioplus (based from sio but better)
Enabled LZ4 compression and decompression for kernel and crypto
Added a fix for PACman users who was stuck
Misc improvements and fixes, check github for details
r3 (15/09/13):
Linux 3.0.95
Fully compatible with android 4.3 roms (cm10.2, PAC)
Used the newer 09/13 linaro toolchain from christopher89
ALSA PCM patches from newer kernel versions
Ext4 Optimisations
Timer slack controller support
Optimised SLUB Allocator
Optimised ARM RWSEM
Fixed right speaker
Updated the intellidemand governor (should be more efficient and shouldn't cause SOD's if it was the case before)
Misc optimisations (check github for more details)
4.2.x
r2.1(31/07/13):
Increase voltage to 1.4 Ghz OC in order to fix the freezing issue.
r2 (27/07/13):
Updated to linux 3.0.86
Revamped the I/O schedulers core drivers (Noop and Row tweaked as well, thanks to Derteufel)
Added FIOPS I/O scheduler
Enabled zram
LiveOC support (it may be half baked, would need the implementation of custom voltage to reveal it's full potential)
Replaced Wheatley with SmartassV2 as per user requests
Fast charge support (Download NS tools or a fast charge app to enable)
Updated BCMDHD drivers to 5.90.195.114
Enabled PM_FAST config for wifi (wifi speeds while sleeping should be as fast as when turned on)
Lowered the brightness down to the hardware's maximum
Added USB OTG host support (I would need confirmation as it's support) Enabled full FAT and NTFS read and write support into the kernel
Tweaked the VM values (Dalvik stuff)
Some under the hood refinements
r1 (08/07/13):
Initial release
Things planned to be implemented:
You propose
Digital FM radio works, which does sound better than the salsa method.
Bottom speaker still sounds quieter.
How fast is fast charge?
Sent from my YP-G1 using Tapatalk 2
dorfd1 said:
Digital FM radio works, which does sound better than the salsa method.
Bottom speaker still sounds quieter.
How fast is fast charge?
Sent from my YP-G1 using Tapatalk 2
Click to expand...
Click to collapse
I don't know how much time it takes for fast charge. Actually fast charge is only something that makes your device think that you're using AC when you charge with your computer. And I still yet implemented it.
Wow, I am happy that you decided to make kernel
props
About lowering screen brightness.
Sometimes kernel modification works, but framework lets us only set it to stock lowest minimum brightness. Try rootdim and see if it allows you to set your brightness lower
I will have a closer look at your repo when I will be on PC
Wysłane z mojego Nexus S za pomocą Tapatalk 4
as a future feature could you force enable adb? otherwise porting roms is impossible because I can't get a bootloop logcat
Awesome work! I will flash it this weekend
I'm still in 4.1 though can i just flash it or do i need to do it from the start?
And what are features like CIFS and TUN?
crancpiti said:
Awesome work! I will flash it this weekend
I'm still in 4.1 though can i just flash it or do i need to do it from the start?
And what are features like CIFS and TUN?
Click to expand...
Click to collapse
I believe you need 4.2.2
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
theraf said:
as a future feature could you force enable adb? otherwise porting roms is impossible because I can't get a bootloop logcat
Click to expand...
Click to collapse
I don't know well as far as the 4.2.2 kernel related, adb needs to be enabled from the dev section (because of security reasons) except for the first boot where it is doing an initial logcat than lock itself. I can try to do something though.
crancpiti said:
Awesome work! I will flash it this weekend
I'm still in 4.1 though can i just flash it or do i need to do it from the start?
And what are features like CIFS and TUN?
Click to expand...
Click to collapse
It can work but I'm not giving support for it. Also cifs is known for mostly remote file access and tun for vps servers.
Envoyé depuis mon Nexus 7 avec Tapatalk
Great work on this! I have one suggestion though. Can the amount of available ram be increased? I know the kernels on the 5.0 have done it, so I don't see why it would not be possible on the 4.0 (and everyone loves more ram!).
WHib96 said:
Great work on this! I have one suggestion though. Can the amount of available ram be increased? I know the kernels on the 5.0 have done it, so I don't see why it would not be possible on the 4.0 (and everyone loves more ram!).
Click to expand...
Click to collapse
I would need to find the right amount of ram that the camera needs (which could take some time).
Base on others sources
Wysłane z mojego Nexus S za pomocą Tapatalk 4
KOala888 said:
Base on others sources
Wysłane z mojego Nexus S za pomocą Tapatalk 4
Click to expand...
Click to collapse
I can't use the same amount of ram as the 5.0 because it will crash the camera, I will try to put 10000 instead of 14000.
I've been using this for a day and a half or so. Looking good so far.
At 1GHz, UI performance compared to the "regular" 3.0 kernel feels the same. Sunspider completes about 300ms faster, and Nenamark2 is consistently 1fps higher, but no difference with any other benchmark I tried. Modern Combat 4 now also runs with no stutters- I figure since Linaro has no performance benefits this must be due to the -O3/-Ofast optimizations (which by the way: what is O3 and Ofast? Can't find any info searching).
Battery life seems good so far.
Haven't experienced any odd crashes or lags.
Great job so far, I'll continue playing around with this- might use it in a future ROM.
zaclimon said:
I can't use the same amount of ram as the 5.0 because it will crash the camera, I will try to put 10000 instead of 14000.
Click to expand...
Click to collapse
I ment sources of kernels for different devices using same soc as yours
Wysłane z mojego Nexus S za pomocą Tapatalk 4
KOala888 said:
I ment sources of kernels for different devices using same soc as yours
Wysłane z mojego Nexus S za pomocą Tapatalk 4
Click to expand...
Click to collapse
Hmm well I checked venturi and derteufel sources, no good. I'll check p1 and Crespo later.
Hey guys I'm considering this, would you like to get TWRP instead of CWM as far as the recovery solution goes?
Envoyé depuis mon Nexus 7 avec Tapatalk
zaclimon said:
Hmm well I checked venturi and derteufel sources, no good. I'll check p1 and Crespo later.
Hey guys I'm considering this, would you like to get TWRP instead of CWM as far as the recovery solution goes?
Envoyé depuis mon Nexus 7 avec Tapatalk
Click to expand...
Click to collapse
make a poll on the thread
but yes, definitely
zaclimon said:
Hey guys I'm considering this, would you like to get TWRP instead of CWM as far as the recovery solution goes?
Click to expand...
Click to collapse
I have TWRP on my Galaxy S4 and comparing it to CWM on my Player (and even the original CWM on my ancient s3c6410 devices), they all do what they need to do about the same. So it really doesn't matter to me.
TWRP would be nice but it does not matter to me. I would like to see aroma file manager working.
Sent from my YP-G1 using Tapatalk 2
Ok I put up the pool in OP, as for aroma FM, I don't want to mess with including touchscreen drivers (I feel sometime too lazy I know )
Ok, so the problem is: everytime I do something that demands more of the GPU, the Androidx86 OS crashes (turns screen black) and restarts in the bootanimation, I looked on the internet a lot for any fix, with no luck. And when I use the onboard intel graphics this doesnt happen. So I turned to my trusting XDA Developers. Anyways, I want to run Ax86 on my PC to test the capabilities of an nvidia gpu in android games. I once used BlueStacks for this purpose, but when I stumbled upon the Ax86 project I wanted it to work. Because my PC isnt the most powerful machine, thus having windows running on the same time as BS dragged the performance a bit. I would like to test the newest titles on android games library such as PUBGM which is a very demanding game (I run it at balanced in a Xiaomi Redmi Note 5 with an Adreno 509 and smooth at a Redmi Note 4 with an 506 all of which are global versions). I saw a notice at the Ax86 site about Nvidia and AMD not providing the necessary tools to integrate their drivers in the OS or something of the sort, thus I looked at my hardware in the Device Control app it says my GPU is a noveau and my renderer is a Gallium 4.0 on NV106 (I looked up thia gallium 4.0 and discovered it is a legacy driver for AMD and Nvidia graphics). I was wondering if there could be anyway to use the Nvidia Tegra driver (I remember once having BlueStacks identifying my GPU as a Tegra). If im not mistaken the Ax86 site had instructions to modify the kernel, and someone in some forum said that this could be fixed in the kernel or something, but I am not such an advanced tech guy and I am a bit scared to mess about in kernels and such. I was wondering if anyone knows a way to have the OS ID my GPU as a Tegra or anything that will change this.
Here are my Ax86 OS specs:
Android version
7.1.2
LineageOS version
14.1.0-android_x86
Android security patch
5 april 2018
Kernel version
4.9.95-android-x86-gd25a822 (gcc version 4.9.20150123 (prerelease) (GCC) )
[email protected] #1
Thu May 3 07:48:31 CST 2018
LineageOS API Level
Guava(7)
OpenGL driver version
GL vendor: nouveau
GL renderer: Gallium 4.0 on NV106
GL version: OpenGL ES 3.1 Mesa 17.1.10 (git-946651c)
OS Version
cm_android_x86-userdebug 7.1.2 NJH47F b3f47217aa test-keys
SELinux status
Permissive
Here are my PC specs:
CPU: Intel Xeon L5430 4 cores 2,66GHZ @ 2,72GHz
GPU: Nvidia GeForce GT710 2Gb VRAM @ 954MHz coreclock
RAM: 4Gb 1333MHz DDR3