Database Users

Kernel Sources released!!

Let us all petition Spice Mobile and Mediatek to release kernel sources!!
Visit THIS thread (remember to thank the OP)
We don't just want stock Android L now, do we??
EDIT: So, kernel sources HAVE been pushed...See this LINK

The Dork Knight Rises said:
Let us all petition Spice Mobile and Mediatek to release kernel sources!!
Visit THIS thread (remember to thank the OP)
We don't just want stock Android L now, do we??
EDIT: So, kernel sources HAVE been pushed...See this LINK
Click to expand...
Click to collapse
We Can't Live Without CM's and Custom Kernels! I'm With ya!

Neither can I CM ! is what we need !

Cannot Capture Screenshot, storage may be in use

Hi all
So i have been encountering this issue with which i can't seem to capture any screenshot.
It gives error "Cannot Capture screenshot. Storage may be in use".
Googling tells me i have to relock bootloader and unlock it again. Is that only way?
-Switch from L Preview (Rom i am currently using) to stock
-I unroot my phone
-Reroot it again
-Again install rom.
So those are only steps and workaround for this issue?
Weird thing is this issue happens on all roms except miui for some reason lol, but i like functioning of android L rom more so i want to stick to that.
Any help would be appreciated.

I'm sure this is something you already did, but try using a 3rd party app (like "Screenshot Ultimate", amazing functionality ) if the built - in screenshot feature isn't working. It could be possible that the issue with screenshotting is just a bug or glitch with your current ROM.
_________________________________________________
· US Samsung Galaxy Player 5.0 (YP-G70)
- Carbon ROM 4.4.4 KitKat
> By Meticulus Dev Team; visit their site at http://www.meticulus.co.vu/
- Entropy512's Daily Drivers Kernel

fangblade386 said:
I'm sure this is something you already did, but try using a 3rd party app (like "Screenshot Ultimate", amazing functionality ) if the built - in screenshot feature isn't working. It could be possible that the issue with screenshotting is just a bug or glitch with your current ROM.
_________________________________________________
· US Samsung Galaxy Player 5.0 (YP-G70)
- Carbon ROM 4.4.4 KitKat
> By Meticulus Dev Team; visit their site at http://www.meticulus.co.vu/
- Entropy512's Daily Drivers Kernel
Click to expand...
Click to collapse
Actually, i am quite aware of things i do and i am quite experienced with rom flashing and stuff (infact baked a few of my own), so its not likely something i did amd plus all i do with my N4 is wipe system+flash rom+xposed+some mods+kernel (though no xposed on L), no filesystem modding stuff, so I have no idea how this probcame into existence. Never happened on my S3 even though I am much more rough with it...
Yeah did try 3rd party apps, same result. And yeag, its happening on every other rom except miui. O_O
So my guess is its some internal bug or something:/

Wait, so what ROM are you using?
_________________________________________________
· US Samsung Galaxy Player 5.0 (YP-G70)
- Carbon ROM 4.4.4 KitKat
> By Meticulus Dev Team; visit their site at http://www.meticulus.co.vu/
- Entropy512's Daily Drivers Kernel

fangblade386 said:
Wait, so what ROM are you using?
_________________________________________________
· US Samsung Galaxy Player 5.0 (YP-G70)
- Carbon ROM 4.4.4 KitKat
> By Meticulus Dev Team; visit their site at http://www.meticulus.co.vu/
- Entropy512's Daily Drivers Kernel
Click to expand...
Click to collapse
I am currently using Android L Preview.
The problem comes on this ROM and all others I tested earlier except miui.

Do 3rd party apps not work on previous ROMs as well? Or is it just a problem you're encountering with Android L Preview?
_________________________________________________
· US Samsung Galaxy Player 5.0 (YP-G70)
- Carbon ROM 4.4.4 KitKat
> By Meticulus Dev Team; visit their site at http://www.meticulus.co.vu/
- Entropy512's Daily Drivers Kernel

Android L has not been officially released, so there is a few bugs with this

1) 3rd Party Apps dont work with other roms too.
2) Its not just android L, its happening on every rom except miui :/
If it was just on Android L then i would have posted in ROM's thread, but its happenjg on every rom.

Well, at this point, why not stick with miui?
________________________________________________
· US Samsung Galaxy Player 5.0 (YP-G70)
- Carbon ROM 4.4.4 KitKat
> By Meticulus Dev Team; visit their site at http://www.meticulus.co.vu/
- Entropy512's Daily Drivers Kernel

[WIP] [CM12] [DEVS ONLY] Cyanogenmod 12 for Moto G (2nd Gen)

Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:

N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.

nice work mate.... developers are needed urgently....

Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:

Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.

@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...

k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:

Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app

okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.

@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!

I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me

which model will this be for? (please say xt1064)

Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!

absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)

Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?

Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:

Waiting for it. Please keep updated though!

I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app

Hope to See this soon! Thanks guys!!

Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best

ROM Development Process and Cyanogem Rumor

Guys...
Our AmigoOS is Almost clean ROM to we can work... because he is a Custom ROM Based on AOSP (To how want check that just download HARDWARE INFO app and check Inside System(Android 4.4.2) -> Build ID, Fingerprint.... and Check Sensors Too(There have Generics AOSP Drivers Running) and on Codec's have some specific Generics Codecs Running too...
about my project i can Almost Clone Certificates from Sony Xperia C or Sony Xperia E4* because they use MediaTek SoC's and some Certificates Need be Compatible with Who Manufacture the SoC's... Some APPs and Framework Need that too... So i Will make my Rom Based on Xperia C (Most Close to our SoC) and Xperia Z3... :highfive:
---
Now talking About BLU and Cyanogem MOD Official ROM's
on internet this week we start see rumors about BLU Releases Official Phone Running Cyanogen MOD ROM to end of this year... -> http://www.xda-developers.com/building-the-machine-cyanogens-corporate-war/
what some forums started talking about is BLU Releases Lollipop Updates to their phones running Cyanogen ROM's... and THAT WILL BE AWESOME Because they will be forced to release their Sources to Official developers but Cyanogen don't have a Big team to do that amount of Modifications... so we will start see that on their Open Source Server ;D
that will bring to us a infinity ways to make things... Like Custom Kernels and Custom ROMs running CM 12.x ;D
BUT THAT IS ONLY A RUMOR ... nothing Concrete about that
We can just have faith about that become concrete and wait until June/July to get if that become true :highfive:

DvDwx. said:
Guys...
Our AmigoOS is Almost clean ROM to we can work... because he is a Custom ROM Based on AOSP (To how want check that just download HARDWARE INFO app and check Inside System(Android 4.4.2) -> Build ID, Fingerprint.... and Check Sensors Too(There have Generics AOSP Drivers Running) and on Codec's have some specific Generics Codecs Running too...
about my project i can Almost Clone Certificates from Sony Xperia C or Sony Xperia E4* because they use MediaTek SoC's and some Certificates Need be Compatible with Who Manufacture the SoC's... Some APPs and Framework Need that too... So i Will make my Rom Based on Xperia C (Most Close to our SoC) and Xperia Z3... :highfive:
---
Now talking About BLU and Cyanogem MOD Official ROM's
on internet this week we start see rumors about BLU Releases Official Phone Running Cyanogen MOD ROM to end of this year... -> http://www.xda-developers.com/building-the-machine-cyanogens-corporate-war/
what some forums started talking about is BLU Releases Lollipop Updates to their phones running Cyanogen ROM's... and THAT WILL BE AWESOME Because they will be forced to release their Sources to Official developers but Cyanogen don't have a Big team to do that amount of Modifications... so we will start see that on their Open Source Server ;D
that will bring to us a infinity ways to make things... Like Custom Kernels and Custom ROMs running CM 12.x ;D
BUT THAT IS ONLY A RUMOR ... nothing Concrete about that
We can just have faith about that become concrete and wait until June/July to get if that become true :highfive:
Click to expand...
Click to collapse
Привет!
Очень хочется надеяться на это!!!
Готов быть тестером всех наработок касаемо кастомных прошивок к нашему аппарату!!!)))
Maks-mix.

Maks-mix. said:
Привет!
Очень хочется надеяться на это!!!
Готов быть тестером всех наработок касаемо кастомных прошивок к нашему аппарату!!!)))
Maks-mix.
Click to expand...
Click to collapse
I too would be willing to test this out. right now I am running the MIUI port but I have always had success with Cyanogen.

[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1]

This thread will be about changes i have made to the device trees for the t700,t705,t800,t805 which should in the long run make maintaining the variants a lot easier the primary changes i have done are combine all 4 of the variants into 1 kernel source as well as make a common device tree so they can inherit everything that is the same across devices.
Kernel Changes:
The Base kernel from Cyanogenmod supports klimtwifi (T700) and klimtlte (T705) to add support for chagallwifi (T800) all that is needed is to add its defconfig which is this file
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
To add support for the Chagallte (T805) it was a little more complicated for to do but very simple for you guys for a little background T805 is exactly the same chipset as the other Galaxy Tab S's except for whatever reason Samsung decided to put a different gpu (Midgard_wk04) everyone else uses a mali_t6xx.
The stuff developers actually need to support Chagalllte are the following:
Defconfig:
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
The GPU addition commit:
https://github.com/LiquidSmooth-Dev...mmit/c8e96e86c902cbc2b13d34e7e7158623eacf5d84
Bam that was easy now any kernel can support all 4 main variants of the Tab S
Device tree and vendor repos
First part i want to place links to all of the stuff that's needed to make a rom for each device in one place.
(Disclaimer the trees will be LiquidSmooth but it is very easy to convert them to any rom)
Klimtwifi (T700):
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtwifi
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/klimtwifi
Klimtlte (T705)
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtlte
https://github.com/schwabe93/vendor_samsung_klimtlte
Chagallwifi (T800)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagallwifi
https://github.com/diego-cr/android_vendor_samsung_chagallwifi
Chagalllte (T805)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagalllte
https://github.com/Andrewt12/android_vendor_samsung_chagalllte
WIP Common Device Tree:
When bringing up support for LiquidSmooth for these devices i noticed that they are all pretty much copied each other (which makes sense) but because of it there was tons of duplicated code between the devices so i decided to make a common device tree so any future code changes could be placed in one place instead of over 4 device trees. This is still a WIP because i do not have all the devices so i can not test them all in my eyes they should all work fine. The common device tree will also hopefully will be rom independent so no changes would be needed on a per rom basis. I can for sure say klimtwifi and chagallwifi work with my common tree, Chagalllte and klimtlte need to be tested still.
Common Device tree repo:
https://github.com/LiquidSmooth-Devices/android_device_samsung_exynos5420-common
Common device tree migration commits
Klimtwifi:
https://github.com/LiquidSmooth-Dev...mmit/444b4fc08f82eeeabe8e0a533539fe0c2fadd723
https://github.com/LiquidSmooth-Dev...mmit/cdf5f06c8a29bb237b964d5ee602d151c6323677
Klimtlte:
https://github.com/LiquidSmooth-Dev...mmit/8570d466e2b5b88c316c7f1576bf8ea9051c5e2a
Chagallwifi:
https://github.com/LiquidSmooth-Dev...mmit/5be51eb30283355109c65513ea209dd1d6855ff2
Chagalllte:
https://github.com/LiquidSmooth-Dev...mmit/5ff21d73a9cad3f7f9cf7f79b29bdbab0d8b2b1e
One more improvement that myself and @diegocr made was finally made a pernament fix to Chagallwifi's (T800) wifi issue he made a custom release tool in the device tree to make it so you would not have to manually patch it every time. I then took that and fixed the root of the issue which was that the vendor repo was not putting the files in the right spot. (My orig commit also did egl but that was not needed) the commit that did it is this:
https://github.com/diego-cr/android...mmit/1fc5135eda985ddc159f8465ee114e67aa5dfcae
Now into the features of my Deathly kernel
XDA:DevDB Information
[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1], Kernel for the Samsung Galaxy Tab S
Contributors
deadman96385
Kernel Special Features:
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-21

Deathly Kernel
I have had a deathly kernel on most devices i own the goal of it is to get as many options and features into a kernel but still be stable. For the Tab S i took the aosp cm base and have updated it against kernel.org from 3.4.105 too 3.4.108 along with pull in a bunch of features from other exynos 5420 devices
As you read above i have made a common tree which changes the ramdisk so i have to provide two zips one with the new format one with old format currently the only rom that i personally have built with the new version is the latest klimtwifi and chagawifi all other roms will boot loop with it so use the old version
Currently i only have flashable for Klimtwifi (T700) i will generate the others once i get back from my trip.
New Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/New_format/
Old Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/Old_format/
Features of the Deathly kernel:
Will support all 4 main tab s devices (will add support for the US carrier variants if aosp is brought up)
CPU Voltage Control
CPU OverClock/UnderClock
GPU Voltage Control
GPU OverClock/UnderClock
MIF/INT Voltage Control (I will not show how to configure this if you know how too then you can)
Wolfson Sound Control Thanks to oloendithas for fixing it for stereo out
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot (WIP)
Android Logger disabled by default can be enabled over sysfs
Exynos thermal exposed to sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128

Details how to configure all of the features i will add the rest once i come back
GPU Configuration:
To configure the max or min gpu frequency you would go to either of the following files in a root enabled file browser and change the value inside
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_gpu
The allowed values for the files are as followed:
667, 600, 533, 480, 420, 350, 266, 177, 100
T800 owners the default min gpu freq is 100 on all roms if that causes issues raise the min freq to 266 you will probably not notice a battery decreases if that still does not work let me know i'll take a look at the code.

Reserved

Reserved

Thanks, working great on CM12.

Thank you man.. Im glad someone finely separated the device tree... And specially Happy about a new kernel that I can use in my Project Roms.
With all Credits going to you of course.. thanks again.

Hey mate, thanks for this!
I'm a little unsure about the new and old ramdisk thingy.
Running aicp on my klmitwifi, new ramdisk is cool?
Will try anyway, but let me know please!
Edit :
just checked, didn't stupidly before, Looks like the kernel is baked in your AICP rom.
Thanks again for your hard work!
Edit edit:
tried the v02 on the rom mentioned, had to revert cause I was having many ui fc.
Used new ramdisk version, could be that or I should have done a clean flash maybe?

Thanks for this, hopefully if fixes the lag issue for me on CM12 with the T800.

Thanks for all the hard work, grid .1 and .2 both worked perfect on bliss rom

Thanks, I will use your kernel on my chagallwifi SlimLP builds

Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks

SkOrPn said:
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
Click to expand...
Click to collapse
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though

deadman96385 said:
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
Click to expand...
Click to collapse
OK, thanks. Hope your enjoying your time off... :good:
I'm going to backup your kernel and try ashyx's new build released today. Its closer to stock but has F2FS support also. Then I will test yours once its updated. Loving this new tab of mine, almost forgot how much fun it was trying to find the sweet spot on a device, lol. My Nexus 7 found its sweet spot a long time ago and now its just a plain ole boring tablet. hehe

diegocr said:
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Click to expand...
Click to collapse
...Slim LP, for t800 maybe, where to find it?
m.

meduza2 said:
...Slim LP, for t800 maybe, where to find it?
m.
Click to expand...
Click to collapse
In SlimRoms Builders Collective

diegocr said:
In SlimRoms Builders Collective
Click to expand...
Click to collapse
...nice Do you intend to make an own SLIM LP thread?
m.

meduza2 said:
...nice Do you intend to make an own SLIM LP thread?
m.
Click to expand...
Click to collapse
Great idea, but now I have no time to keep updated

diegocr said:
Great idea, but now I have no time to keep you updated
Click to expand...
Click to collapse
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.

meduza2 said:
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/development/rom-ezio84-slimlp-t3146025