Database Develop

[Dev][Experimantal][Kernel][ION] nAa-ION Kernel

This is Strictly Development i u know something plz share if don't then be slient
What is ION .?
Noob way :- It makes things awsome -by lauppenstepperwolf
there is awsome explaination on LX git Wiki
LX said:
#### What is Shared Memory?
Memory is usually private; an app takes a chunk and nothing else can access it.
Sometimes, it makes sense to share memory between processes; for example, an app writes to the screen buffer, while the gfx driver reads that same buffer to put it on the screen. You need a special memory system for that.
####PMEM vs. ION
Back with Gingerbread, every ARM chip maker (Qualcomm, TI, nVidia, Samsung, more?) had their own way of doing shared memory. The Qualcomm way was a system called **PMEM**.
Problem: when a vendor sells a chip to Sony and Samsung, he needs to write two drivers, one for each shared memory system.
To reduce maintenance efforts, Google introduced **ION**, a unified shared memory system, that all vendors use since ICS
Problem: from ICS forward, Qualcomm only provides graphics drivers for ION. PMEM is obsolete.
For a while, stuff still worked, but it is getting worse for us - see the Google Maps app for example.
####Move to ION
An option is to rework the kernel, replace the PMEM system with ION, and replace the old PMEM drivers with newer ION drivers. A common problem on several old devices is, that the camera chip is non-standard, and Sony (Samsung, HTC) never wrote ION drivers for the old cameras. Moving to ION then means you lose the camera completely.
A new solution is to move the kernel to ION, but have a PMEM system on top of ION so that the old camera libs can connect to it. As far as I know, this was pioneered by the Dev_Connection team that maintains the Samsung S+ i9001 (great team, hats off to Christopher83 especially).
Another implementation of an ION/PMEM hybrid was made by galaxyfreak for the HTC Explorer (Pico).
The i9001 and the Pico have similar hardware to our 2011 Xperias (2011, MSM, 512MB RAM, similar specs).
Feedback for the ION builds is very positive. Performance is good and it solves some graphics problems like the Google Maps flickering, and it solves the slow browser.
####ION on LegacyXperia
It would be the next big step after the 3.x kernel, but, it's a lot of work.
On the i9001, 8 devs work on 1 device, while on our side, 1 dev works on 8 devices.
The i9001 approach was to migrate 10.1 to ION, then 10.2, then 11; instead of directly doing 11-ION.
Click to expand...
Click to collapse
ETA :- Nowhere to release
============================================================================
THIS IS A REWORK ON nAa-kernel to use ION but with no video recording support ... until mike does spread his awsome magic with his new scratch ported kernel...
Source :- http://www.github.com/rebel-x/msm7x30-3.4.x-nAa
Current Progress : Intial Pushes done "yay" lets hope it boots
NOTE :- We need your help , i m not able to do alone since i have very limited knowledge about kernels , Please forgive me if my coding somewhere wrong cause
ok so thank you i will post progress as we all get step further ,
thank you
Credits :
Mike : we all know why
nAa : Awsome dev
szezso : always helpful
XDA:DevDB Information
ION-Kernel, a Kernel for the Sony Ericsson Xperia Arc
Contributors
officiallysonyrebel, szezso, Mike
Kernel Special Features:
Version Information
Status: Testing
Created 2014-01-08
Last Updated 2014-01-07

Don't ever give up!

you also need To build rom with ion accelator

offical
its offical jb kernel ?

mahsun72 said:
its offical jb kernel ?
Click to expand...
Click to collapse
Can you read? It's not even official. It could be also for CM11 since he mentioned browser lag, which is an existing bug in CM11.
To OP, I should be able to check the coding and whatnot. Only problem is I'm currently in the army and unable to access my computer on weekdays.
僕のLT18iから送られてきた

@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk

I should also be able to check the code as I'm proficient in C++. Let me know where I can help out, it's a good initiative.

ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp

Boudin said:
ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
Click to expand...
Click to collapse
ion is different for every device i guess
Update :
finished initial kernel part (lets hope it boots know)

vishal_android freak said:
@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
im now focus on shool,also i give my arc to my sister i now have only idol mini

n1kolaa said:
im now focus on shool,also i give my arc to my sister i now have only idol mini
Click to expand...
Click to collapse
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak

vishal_android freak said:
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak
Click to expand...
Click to collapse
its idol mini form alcatel,how can i test new kernel with it explain it to me

n1kolaa said:
its idol mini form alcatel,how can i test new kernel with it explain it to me
Click to expand...
Click to collapse
Ohh.. My bad.. Sorry..
Sent from my Nexus 5 using Tapatalk

I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?

CedArctic said:
I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?
Click to expand...
Click to collapse
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work

rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
all the best bro.. Any improvements?

gpkumaran said:
all the best bro.. Any improvements?
Click to expand...
Click to collapse
yea its compiling know but no where Close to Boot ... i have changes locally purchased a XMP with screen destroyed only for kernel debugging purpose

rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
Thanks for your work! I love KK rom and im wait ion kernel :thumbup:
Regards

To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.

Dr.SAM88 said:
To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.
Click to expand...
Click to collapse
A better Kitkat .. lets summerize current kernel situation
1. nAa 3.4 full of hacks
2. using drivers and stuffs from 3.0.x
3. Stuck on Abandoned PMEM {with every increasing android version we are using patches more than before to maintain PMEM causing soo many graphic lags
4. msm_fb code /* lets not focus on it currently */
why this mess /* to bring 3.4 kernel faster */
i m trying on 3.0.x-nAa kernel cause it is Pure CAF and also mike is working on Pure CAF 3.4.x MHL enablin gis such a lot and lot of work we are not in fully stable stage to look at MHL and other workaround first..
our device is a 3 year old piece of hardware without camera and HDMI libs using outdated kernel and drivers what should be the main goal
1. To make kernel updated with current sources
2. then make things working
3. then wprkaround for all abandoned hardware(like HDMI)
hope u know why we are focus on kernels and roms know ... and to come at point of compeion in roms
there is no compeition we are not selling our products .. we are working cause we like it and more roms means more respect for developers who are working tirelessly on maintaining those roms @Marchinho6 please no these kinds of post ..!these will spam thread

DT2W MI4

is a year that I try on the web DT2W for my mi4 but could not find anything good ... tried all the kernels, the channel Mi4 and mi3, but none works well ...
I have the model with 2GB of ram and I think that has a different camera from the model to 3GB of RAM and all the kernel I tried does not work the camera ...
I would only DT2W ... someone can help me?
I currently have the 7.2.11.0 MM xiaomi.eu
thank you so much

....A 2GB variant of Mi4? AFAIK, there are no variant of Mi4 with only 2GB of RAM.
Maybe your device is either Mi4i or Mi4c, and those two are a completely different device than Mi3/Mi4 (Cancro).

rxl.noir said:
....A 2GB variant of Mi4? AFAIK, there are no variant of Mi4 with only 2GB of RAM.
Maybe your device is either Mi4i or Mi4c, and those two are a completely different device than Mi3/Mi4 (Cancro).
Click to expand...
Click to collapse
Apparently there is a 2gb ram version of mi4 of which even I was not aware...dont know if its real or fake...
https://www.youtube.com/watch?v=iFxBJ2Ufovw

sushd99 said:
Apparently there is a 2gb ram version of mi4 of which even I was not aware...dont know if its real or fake...
https://www.youtube.com/watch?v=iFxBJ2Ufovw
Click to expand...
Click to collapse
Hmm, I've searched around, and indeed there's a Mi4 with only 2GB RAM released by Xiaomi... Seems like there's no difference other than the RAM amount.
To OP, try ZeurionX. It's currently the latest kernel that supports DT2W (which is added back on request). Activate and set up the feature through Kernel Adiutor app.

I tried every version of the kernel ZeurionX but the camera or does not work or is upside down

barchitiello said:
I tried every version of the kernel ZeurionX but the camera or does not work or is upside down
Click to expand...
Click to collapse
I'm going to buy the same version you have. I think we should get in touch with the ZeurionX developer. It should be relatively easy to get this fixed. It's a known problem on several devices.
OT: do you confirm that Xiaomi.eu rom works good on 2GB Mi4? Also, could you please check the codename is Cancro? Thanks.

nor-ric said:
I'm going to buy the same version you have. I think we should get in touch with the ZeurionX developer. It should be relatively easy to get this fixed. It's a known problem on several devices.
OT: do you confirm that Xiaomi.eu rom works good on 2GB Mi4? Also, could you please check the codename is Cancro? Thanks.
Click to expand...
Click to collapse
the codename is always cancro, I always used the rom xiaomi.eu and work well ... I currently have the latest stable xiaomi.eu miui stable 7.3.1.0

I'd like to try this kernel, but how would I revert to stock kernel then?

nor-ric said:
I'd like to try this kernel, but how would I revert to stock kernel then?
Click to expand...
Click to collapse
Just dirty re-flash the current ROM you're using through the recovery without wiping anything, although if you use Xposed you also have to flash it too.

[Help] Android Oreo 32 or 64 bit?

I have a query, currently motorola works with 32 bits in android. When android 8 release will still be 32-bit or will they go 64-bit?
Thanks for your clarification :good:

benjaconb said:
I have a query, currently motorola works with 32 bits in android. When android 8 release will still be 32-bit or will they go 64-bit?
Thanks for your clarification :good:
Click to expand...
Click to collapse
No-one knows except moto - ask them.

Phazmos said:
No-one knows except moto - ask them.
Click to expand...
Click to collapse
Yes we know. Motorola won't update from 32 bits because it needs file wipes.. and people will get mad if their phone gets wiped for a update they won't notice (for the majority of users)

Still it's 64bit ready. Custom roms are based on 64bit architecture. And i think i read somewhere that official oreo wil lbe 64bit. M1810, how do you know that it won't?

It is 64
I have an old Samsung s4 Mini running resurrection remix Android 8.1. I formatted my SD card to NTFS with a 64bit cluster size. The phone reads it fine.

@Mikeyd125, an oopsie. I do believe you posted in the wrong thread.
Moto G5S Plus XT1806, GZOSP_PixelExperience, MultiROM, TBO Tapatalk 4.9.3

osemoka said:
Still it's 64bit ready. Custom roms are based on 64bit architecture. And i think i read somewhere that official oreo wil lbe 64bit. M1810, how do you know that it won't?
Click to expand...
Click to collapse
Switching architectures requires the device to be wiped so officially it wouldn't make much sense if Motorola doesn't want consumers to have issues

Yea Yea. Heard that already. Why wipe is so scarry to people? They can't make simple backup? ;D

osemoka said:
Yea Yea. Heard that already. Why wipe is so scarry to people? They can't make simple backup? ;D
Click to expand...
Click to collapse
Average Joe would be angry if his phone would be wiped from all data even if he backed up.
Most people doesnt care about OS version as long as it does what it has to do.

Well. At least they should give us a choice 32bit and no wipe oe 64bit and wipe.
Will there be real difference in our case (g5s+ users) in performance between these two versions? I will have a problem with choosing custom rom based on original 32b or 64b(which can't be based on future stock ?) in the future.

osemoka said:
Well. At least they should give us a choice 32bit and no wipe oe 64bit and wipe.
Will there be real difference in our case (g5s+ users) in performance between these two versions? I will have a problem with choosing custom rom based on original 32b or 64b(which can't be based on future stock ?) in the future.
Click to expand...
Click to collapse
gcam and few another apps
performace no changes

osemoka said:
Well. At least they should give us a choice 32bit and no wipe oe 64bit and wipe.
Will there be real difference in our case (g5s+ users) in performance between these two versions? I will have a problem with choosing custom rom based on original 32b or 64b(which can't be based on future stock ?) in the future.
Click to expand...
Click to collapse
And we would have to wait twice as long for developers to make both 32 and 64bit for few people to chose 64 bits. Genius.

Redmi 7A arm64 kernel

Most of us are aware that this device is running a 32-bit kernel on top of a 64-bit SoC.
After fiddling around with porting linux potentially to this phone (will come out once i manage to make something that ACTUALLY works), I found out that the Xiaomi 8A uses the EXACT same SoC (SDM439) and has a 64-bit kernel. Hmmm, maybe I can get 64-bit going on this phone I thought.
So what I did essentially was take a 8A kernel (that works) and add back the 7A defconfig changes.
I was sure it had no chance to work, but I tried it anyway.
It boots into Android without any issue... lmao
Since this board is pretty restrictive when it comes to attachments, I had no other choice but to upload to google drive.
Here's the link: [Outdated, look here instead -> https://forum.xda-developers.com/redmi-7a/development/64-bit-redmi-7a-t4145225]
Update: Everything works now, except some pretty minor bugs here and there.
Kernel source: https://github.com/nikp123/Xiaomi_Kernel_OpenSource/tree/pine64-p-oss

Wow... How interesting, I hope people can work something out of this, thanks

Turns out that the touch screen drivers are broken. Currently trying the opposite, building a 7A kernel using a "64-bit" defconfig, with the obvious changes so it compiles.

Wow !!! waiting for more update

Quick update: The stock kernel cannot compile with the ARM64 config. Will have to resort back to the 8A kernel for this.

Quick update 2: I've also broken audio and can't get it back.

yes ill be wating for this

This is really cool!! I'll definitely keep an eye on this thread

Update 3: Got touch screen to work
But I'm going to switch my kernel base to the Xiaomi stock kernel as it seems more stable.
Had to analyze a 14MB diff file to see what broke it 0_0
PS: Still haven't figured out how to get the audio back

Good luck!
Hope everything works soon

Update 4: Audio fixed
Only Wi-Fi left.

Update 5: The driver Wi-Fi seems to be missing from the kernel repo, that's why it doesn't work.
Merging it into the repository just like the audio driver might yield results.

nik1234567 said:
Update 5: The driver Wi-Fi seems to be missing from the kernel repo, that's why it doesn't work.
Merging it into the repository just like the audio driver might yield results.
Click to expand...
Click to collapse
Can't wait to try it

Update 6: Wi-Fi driver is giving me hell. Does anyone know a sane way to compile it, IT WOULD BE SO MUCH APPRECIATED.

nik1234567 said:
Update 6: Wi-Fi driver is giving me hell. Does anyone know a sane way to compile it, IT WOULD BE SO MUCH APPRECIATED.
Click to expand...
Click to collapse
can i know what base rom you test it?

daizu said:
can i know what base rom you test it?
Click to expand...
Click to collapse
Any 32bit ROM that works essentially

Update 7: Wi-Fi driver works when built as a kernel module. Kinda finicky, but that's that.
Now for vendor-space fixes.

Amazing! Thank you so much for sharing your advancements and development with us ?
May I ask: what will change on this device with a 64 bits kernel? I mean: what is gained? I'm pretty ignorant in the subject.

I want instruction for flashing boot.img ... Can i flash it on my current a64 custom rom? Or it needs to be on miui/stockrom?thanks

ModExplorer said:
I want instruction for flashing boot.img ... Can i flash it on my current a64 custom rom? Or it needs to be on miui/stockrom?thanks
Click to expand...
Click to collapse
Don't flash the kernel yet because it's not finished. Wait for the devs to release the final version unless you want bugs.

[Closed] BeastMode Kernel update UE5 RELEASED

hi all
for those impatient and dare to try, plus able to handle problems ON YOUR OWN as i cannot offer any help at this point:
anyone interested to test an updated version of BeastMode Kernel R154 by @freeza with the latest samsung firmware N960FXXU8FUD1?
please be noted that:
- this might be EXTREMELY DANGEROUS or could BRICK YOUR PHONE in a few seconds, and I am not responsible for bricked devices or any damages which may arise. so, you have been WARNED
- I have NOT TESTED on my n960f yet (just updated to TH4 from pie but not rooted yet for some reasons). SO THINK TWICE!!
- chances the phone may not boot up properly (boot loop or hang) due to the toolchains used to compile the kernel. I have encoutered this before with only one of the four or five gcc i had which booted up the phone successfully
ideal situation to minimize uncertainties:
- already on ud1
- data/cache partition is ext4 formatted (ideally NOT f2fs as supported by bm kernel)
- capable of diagnostic/identify the problems by examining the logcat/last_kmsg and the like would defintely a plus
to be continued...

Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested

JC1126 said:
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
Click to expand...
Click to collapse
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests

ykkfive said:
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
Click to expand...
Click to collapse
Alright Goodluck!

JC1126 said:
Alright Goodluck!
Click to expand...
Click to collapse
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated (N960F) without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- NOTE: other devices preiously supported are not recommeded yet, although you may try, i cant make any promise it will work since i didnt look at other devices sources
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz

ykkfive said:
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- f2fs supported as R154 (cache/data)
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
Click to expand...
Click to collapse
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom

JC1126 said:
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
Click to expand...
Click to collapse
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
sorry, but NO f2fs there in his kernel!!

ykkfive said:
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
Click to expand...
Click to collapse
that's cool, can't wait to try it out in lineage a11 lol

JC1126 said:
that's cool, can't wait to try it out in lineage a11 lol
Click to expand...
Click to collapse
i just checked the output, there's no f2fs unfortunately but i can add it later after test

ykkfive said:
i just checked the output, there's no f2fs unfortunately
Click to expand...
Click to collapse
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah

JC1126 said:
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
Click to expand...
Click to collapse
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first

ykkfive said:
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
Click to expand...
Click to collapse
Ohh alright then

update 20210618
the ue5 kernel works properly so far, tested on stock rom only due to unable to get a ue5 custom rom atm
will be released soon
thanks a lot

released, closed