Related
Alright, here is the z4mod app at long last! This release needs a lot of testing for different devices still, so make sure you check the compatibility table below unless you know how to use Odin to flash back your original kernel. Thanks for helping to test this!
[size=+1]This is still in beta! If you know how to flash with Odin, please help test so all bugs can be found and fixed to allow for wider release![/size]
What is this?
Another lagfix. This one is a bit different from existing lagfixes though:
- Differences from OCLF: Uses native EXT/JFS instead of loopback mounts. Loopback mounts in linux can be a bit flakey at times, especially when they're on RFS. So this is generally better.
- Differences from lagfix kernels such as voodoo or sztupy's: These types of lagfixes are kernels compiled from GPL sources for specific devices. This can cause a number of issues, such as losing out on bug fixes in later Samsung kernels released after the GPL code, or differences in devices such as the I9000B, etc. z4mod also has (imo) a nicer design, in that it uses /etc/fstab for filesystem mounting, as well as keeping the convert scripts outside the kernel. It should also work across ALL (or many?) Samsung devices without changes!
How do I use this?
Install the app. Click the buttons. It should all just work. Let me know of any issues or complications! This is still in testing!
Device/firmware compatibility table
Samsung Galaxy S Devices
Stock Samsung
I9000 Stock Samsung 2.2 : WORKING
I9000 Stock Samsung 2.1 : NOT TESTED
I9000B Stock Samsung 2.2 : NOT TESTED
I9000B Stock Samsung 2.1 : NOT TESTED
I9000T Stock Samsung 2.2 : NOT TESTED
I9000T Stock Samsung 2.1 : NOT TESTED
I9000M Stock Samsung 2.2 : NOT TESTED
I9000M Stock Samsung 2.1 : NOT TESTED
Captivate Stock Samsung 2.2 : NOT TESTED
Captivate Stock Samsung 2.1 : NOT TESTED
Vibrant Stock Samsung 2.2 : NOT TESTED
Vibrant Stock Samsung 2.1 : NOT TESTED
Epic Stock Samsung 2.2 : NOT TESTED
Epic Stock Samsung 2.1 : NOT TESTED
Fascinate Stock Samsung 2.2 : NOT TESTED
Fascinate Stock Samsung 2.1 : NOT TESTED
Stock Japanese Docomo Galaxy S (SC-02B) : WORKING
Stock SHW-M110S (Korean SGS) : WORKING
Custom Firmwares
Any custom firmware that uses a stock kernel works as the stock kernel in the table above
Custom kernels that make use of changed filesystems or boot up scripts are unlikely to work at this time. Emphasis is on stock kernels currently.
Custom Kernels
BLN (backlight notification) custom kernel for GT-I9000 works
Voodoo kernels do not work
Kernels with heavily modified boot procedures such as rooted Vibrant kernels do not work
CFRoot kernel does not work.
DamianGto's kernels work
Other Samsung Devices
NOT TESTED
More info on z4mod
http://www.sgscompilebox.dreamhosters.com/about.html
Source Code
http://github.com/z4/z4mod
V0.9.2 Changelog
Fix for EXT2->RFS Conversion. Please update to this app version before using this conversion.
Other small bug fixes.
Conversion page now has scrolling text informing you of progress and any errors.
V0.9.3 Changelog
Critical: Upload kernel now passes binary MIME type to prevent corrupt kernels
Fixes for text in conversion screen.
Fix for 'mmcblk0p2' always being chosen for /data, even on devices that use 'mmcblk0p1'
Bug fixes for UI
Donations
Donate link is available at https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
quick question I need to disable vodoo before using this right ?
anyways im running vibrant rom ( axura ) on my rogers captivate ( i896 )
testing now
DAGr8 said:
quick question I need to disable vodoo before using this right ?
anyways im running vibrant rom ( axura ) on my rogers captivate ( i896 )
testing now
Click to expand...
Click to collapse
This probably won't work if you have a Voodoo kernel installed. The Voodoo kernel is unlikely to be patchable, since it's not native RFS, and does not use /etc/fstab.
RyanZA said:
- Differences from OCLF: Uses native EXT/JFS instead of loopback mounts. Loopback mounts in linux can be a bit flakey at times, especially when they're on RFS. So this is generally better.
Click to expand...
Click to collapse
I have a Vibrant and this is why I have avoided using the OCLF in the past. Many ROMs don't even need a lag fix. However, with that issue gone, I'll at least try it and report back on it.
RyanZA said:
This probably won't work if you have a Voodoo kernel installed. The Voodoo kernel is unlikely to be patchable, since it's not native RFS, and does not use /etc/fstab.
Click to expand...
Click to collapse
hey I forgot to mention I had flashed setiron's reoriented kernel on it , so yea result is could not patch kernel ..
I guess i have more test to do. But right now Im stuck with 0.12 problem.
I did test it
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.
Instead of restarting the phone.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
can i use this with speedmod kernel?
DamianGto said:
I guess i have more test to do. But right now Im stuck with 0.12 problem.
I did test it
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.
Instead of restarting the phone.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Click to expand...
Click to collapse
It checks for a /z4mod/z4version file to determine if it's been patched already. If you are using an earlier patched z4mod kernel that doesn't have that file, then it won't work right. If you start with a stock samsung kernel then it should work fine.
specialex said:
can i use this with speedmod kernel?
Click to expand...
Click to collapse
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels. At present, any custom kernel that does not change the initramfs (in particular, the /init binary and init.rc mount options) too heavily should work fine.
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Whitehawkx said:
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Click to expand...
Click to collapse
Thanks for testing!
Could you upload the z4mod.log file in your sdcard? /sdcard/z4mod.log
Okay. Then its just because the bug in the latest z4build then.
That's why it tried to apply the change.
Z4ziggy is working on that problem
Hope he will solve that soon. Right know Im on stock filsystem with my new kernel. Lol.
Kind of fun to compare them.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
RyanZA said:
Thanks for testing!
Could you upload the z4mod.log file in your sdcard? /sdcard/z4mod.log
Click to expand...
Click to collapse
I just looked and there isn't one there.
Whitehawkx said:
I just looked and there isn't one there.
Click to expand...
Click to collapse
Hah... Okay that's pretty strange. What method did you use to root btw? Perhaps it's a busybox conflict of some type.
RyanZA said:
Hah... Okay that's pretty strange. What method did you use to root btw? Perhaps it's a busybox conflict of some type.
Click to expand...
Click to collapse
Hmmm the rom/kernel I flashed came pre-rooted. Now that I think about it, I was using the stock JK2 kernel but it has a custom init script to allow the use custom boot animations. Could this be effecting the conversion process by chance? Anytime I manually root though I use OCLF from the market.
Hey RyanZA,
I see that there is a list of devices in the first post but I dont see a listing for the GT-i9000M specifically. I see the i9000, i9000B and i9000T but no "M". Is there a reason for this? Is the i9000M considered in the generic i9000 family? Also...
A bit off topic here but I am curious to know if I root using z4root and need to unroot for warranty purposes, will it remove ALL traces that it had been rooted including Busybox and Superuser app?
I know that Samsung has issued a memo stating that if a phone shows up rooted to a service center that the warranty will be voided and Id really like to try this rooting method.
Also, as you are probably aware, the i9000M here in Canada has issues with internal sd card failures and I am curious to know if just rooting with z4root will possibly kill my internal sd?
Thanks...
Flashed my Epic using the DK05 2.2 Rom, ran Z4mod, get error: zimage test failed when i try and patch the kernal.
RyanZA said:
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels.
Click to expand...
Click to collapse
should probably put this on OP , less hassle probably .
if nobody else test it on the cappy ill flash to stock just to test ..
@DamianGto:
The problem is with CWM recovery - it's busybox-tar is not working properly.
I think I found a way to overcome this and I updated the git, so now CWM option should be working again.
Whitehawkx said:
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Click to expand...
Click to collapse
If you could paste the contents of the following 2 files we might learn more:
/z4mod/log/init
/sdcard/z4mod.log
Just installed on my device (GT-I9000 with official JPA just released today in Thailand)
It worked fine. I got 1730 from quadrant.
Thanks for your excellent job. ^__^
Hello everybody,
I don't know if this has been done already, but I couln't find it so I thought why not make a version of my own.
Next to WhiteXP i'm also working on a version of CyanogenMOD 7.2, but with a different approach.
In my oppinion before even trying to release something it's important to have a permanent and working version of instead of the stock recovery.
The difference between this phone and many other phones is the fact that the recovery is included in the boot.img file.
My own phone for example, a Samsung Galaxy S Plus, has a seperate standalone recovery.img.
Because I don't own this phone myself I hope another developer can test if this is working properly.
I didn't change the kernel or important boot files other than the recovery itself, so booting into android shouldn't be a problem and remember it's build upon the stock kernel for now.
Here is the downloadable boot.img: http://depositfiles.com/files/90ye57wtm
The kernel should be flashable through the existing CWM which is already posted in the forums with this file:
http://depositfiles.com/files/e21qacxo9
Hopefully somebody is willing to give me some feedback.
Greetings PsychoGame
Hello
Here I am again with a little update.
This version doesn't seem to work okay, it gets into a bootloop.
I will try to fix these problems at a later time.
Greetings
Psycho Game
Thanks...for your work merge CWM into stock kernel...:thumbup:
Sent from my GT-S5360 using xda app-developers app
Here's a little update of the work i'm doing right now.
As I already said I'm also working on a version of CyanogenMod myself.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y at first, but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the make file of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary [status: complete]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: WIP]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. [Status: Planned]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Greetings
Psycho Game
As the title suggests, is there a kernel for the P605 which will allow SElinux permissive, and therefore allow full linux chroot installs to be completed with relative ease.
I am aware of a permissive kernel for P600, http://forum.xda-developers.com/showthread.php?t=2590311
but assume this will not function for the P605.
If not can the same steps used to make the P600 kernel permissive be applied to a P605 kernel?
Looking for the same kernel
I'm looking for the same SELinux-permissive kernel for P605.
You definitely can't use the P600 kernel as it is for the Exynos variant (P600/01) while ours (P605) is the Quallcom CPU.
Unfortunately the P600/01 was released around the world first with most devs getting the Exynos version. Little developement has been done for the P605 but there has been a little. Just not for an SE-Linux permissable kernel, at least not here on XDA...
Will try to build it myself
I've been thinking of modifying and building the kernel myself. The problem is that there are several kernel source codes on Samsung's website for SM-P605. (I can't post the link here) My device model is SM-P605 without any suffixes so I think it's the first kernel that I should choose.
I think modifying the kernel into SELinux permissive should be as easy as changing a default value in one of the source files and then I can build the kernel using the instructions that come with it. Fingures crossed!
One more thing: in the source code that Samsung provides there are two directories, one kernel and the other platform do I need to build the platform too?
Rhesus007 said:
I've been thinking of modifying and building the kernel myself. The problem is that there are several kernel source codes on Samsung's website for SM-P605. (I can't post the link here) My device model is SM-P605 without any suffixes so I think it's the first kernel that I should choose.
I think modifying the kernel into SELinux permissive should be as easy as changing a default value in one of the source files and then I can build the kernel using the instructions that come with it. Fingures crossed!
One more thing: in the source code that Samsung provides there are two directories, one kernel and the other platform do I need to build the platform too?
Click to expand...
Click to collapse
Hey Rhesus007, just wondering if you have made any progress?
Im really in need of a permissive kernel, however i have no knowledge of how to make it etc.
Thanks.
Just dropping back in the thread, still hoping this will happen, as linux on this tab would be really useful imo.
Someone with some dev experience might be able to use the methods used on the note3, which has the same snapdragon 800 soc to achieve this. The basic steps needed to modify the kernel are described in this thread
http://forum.xda-developers.com/showthread.php?t=2471416
if nobody with experience can do this, I might give it a try, but that might be a recipe for disaster....
patchseven said:
Just dropping back in the thread, still hoping this will happen, as linux on this tab would be really useful imo.
Someone with some dev experience might be able to use the methods used on the note3, which has the same snapdragon 800 soc to achieve this. The basic steps needed to modify the kernel are described in this thread
http://forum.xda-developers.com/showthread.php?t=2471416
if nobody with experience can do this, I might give it a try, but that might be a recipe for disaster....
Click to expand...
Click to collapse
I've got no experience with this, if you could attempt it, I'm sure a lot of people would be grateful!
For those still looking.
Maybe this might work, don't know if it will work on custom ROM's
http://forum.xda-developers.com/showthread.php?t=2765353&page=3
EP005 said:
Maybe this might work, don't know if it will work on custom ROM's
http://forum.xda-developers.com/showthread.php?t=2765353&page=3
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...rnel-stock-selinux-permissive-kernel-t3232814
For the 5.1.1 update!
looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: kind @xluco has built a kernel just for us:
http://forum.xda-developers.com/show....php?t=2756679
ionflux said:
looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: for p600. thanks!
Click to expand...
Click to collapse
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.
injola said:
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.
Click to expand...
Click to collapse
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful
ionflux said:
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful
Click to expand...
Click to collapse
I was trying to edit my last post because I saw that you have tried that kernel.
I have spent way more time compiling kernels over the past 20 years than I care to, which is one reason I haven't tried this task yet. I flashed the pre-kitkat selinux permissive kernel a while back and it simply wouldn't boot. I had saved the stock kernel with online nandroid backup. I reflashed stock kernel and there was no problem. I guess, the same would happen with an any unbootable kernel. I never have built an android kernel though.
Here you go guys, try this.. Stock KitKat kernel with SELinux in permissive mode and Knox removed: d-h.st/uCX
EDIT: slight update with NTFS support / HTCP and Multi-core scheduler support.. all completely stable as they're already in the kernel just not selected
EDIT 2: http://d-h.st/ziH - V3 [19/05/2014] (fixes a small derp in ramdisk)
http://forum.xda-developers.com/showthread.php?t=2756679
Any chance of a p605 kernel with SElinux enabled?
patchseven said:
Any chance of a p605 kernel with SElinux enabled?
Click to expand...
Click to collapse
samsungs opensource website is so slow, it would literally be about 5 hours of download time to get the source, I can do it but it'd be next week now
Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.
patchseven said:
Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.
Click to expand...
Click to collapse
Check the thread over in original development if you haven't already, p605 for jellybean just added
Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...
TrendingTech said:
Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...
Click to expand...
Click to collapse
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305
why?
Minto107 said:
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305
Click to expand...
Click to collapse
How come, I don't understand, there are serveral other ROM's for KITKAT, why would it be impossible to build a Lollipop ROM? I have NO idea how to build a rom, otherwise I would give it a try.
What makes it so difficult?
We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305
Minto107 said:
We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305
Click to expand...
Click to collapse
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?
TrendingTech said:
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?
Click to expand...
Click to collapse
None of TAB 3 family devices got 5.x so there's nothing to port. Tab 3 7,8,10 won't be updated to 5.x
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
Tab 3 8.0 has unofficial cm-12.1
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,
Grynot said:
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,
Click to expand...
Click to collapse
Omg but 8.0 uses Exynos 10.1 uses Intel and 7 uses ****ty Marvel CPU! You don't have source so no CM for you
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !
rheecollinskelley said:
So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !
Click to expand...
Click to collapse
You know that Tab 3 8.0 is only 4.2.2 supported, not even close to KitKat, although you can find yourselves SM-T21x Kit Kat roms. Lollipop will not be supported by any chance, even for custom roms man!
It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.
vorpalblade77 said:
It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.
Click to expand...
Click to collapse
Yeah but XDA is full of noobs that only asks when, why it takes so long time... Bringing Lollipop to TAB 3 7inch is very hard work... This tablet wasn't a beast, since release date it was low end tablet with such tragic performance. For such noobs who just want and doesn't want to help I've got an advice. Get Nexus 7 2013... 6.0 on board, noob friendly
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.
DroidTwe4kz said:
As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.
Click to expand...
Click to collapse
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.
vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
DroidTwe4kz said:
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.
Click to expand...
Click to collapse
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
gr8nole said:
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
You already did more than enough for our device and I'm thankful for that. Someone will continue to build CM based on your source.
gr8nole said:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO
vorpalblade77 said:
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO
Click to expand...
Click to collapse
I haven't looked at any of this in a long time, and have no real desire to at this point.
gr8nole said:
I haven't looked at any of this in a long time, and have no real desire to at this point.
Click to expand...
Click to collapse
Fair enough. I'll probably look into once I know I have my build environment set up correctly. E.g., I can build a recovery and have it work correctly.