Related
Roebeet and I have confirmed that the 1.2 bootloader is not locked, it just has changes that other devices have gained before the Gtablet.
The 1.2 bootloader is compatible with pershoot's Zpad kernel and Adam kernels. The newer bootloader causes older kernels to fail because it requires extra voltage levels from the bootloader.
Check out Pershoot's Zpad option here: https://github.com/pershoot/gtab-2632/commit/6665ebaa6cd071d4669578983e82ea36d58fc68a
The Gtab can run Pershoot's Zpad kernel on the 1.2 bootloader. This means that the Zpad and Adam's bootloaders were from a newer branch of Malata's internal smba1002 kernel repo. If any future Gtablet or Adam kernels come out past 2.6.32, they will most likely be incompatible with the 1.1 Gtab bootloader, so it is best if people start moving ROMs on to 1.2 to prepare. We know that Notion Ink has Malata working on a post 2.6.32 kernel.
I know Roebeet is updating his mods to run this new setup, so watch out for them.
Bottom Line:
- If you run a 1.1 ROM now, you can continue to do so.
- If you want to prepare for future development, just transition your next version to using Pershoot's kernel for 1.2 and the 1.2 bootloader
Hmm, seems some apologies are in order.
Good stuff guys. Glad to see that the G-Tab will be able to move on to the new stuff.
We really think this is an opportunity for the Adam and Gtablet efforts to unite under one effort. The system images have always been easily ported to each other, now the kernels are also.
rothnic said:
We really think this is an opportunity for the Adam and Gtablet efforts to unite under one effort. The system images have always been easily ported to each other, now the kernels are also.
Click to expand...
Click to collapse
I also think this is the way to go. It's rumored NI is going to release a GB update soon ( It should have hardware acceleration since it is from NI). Also there is a tremendous dev effort going on porting HC to Adam, in addition to NI's promise for HC.
ive updated the compatibility listing.
Fantastic news. Thanks for sharing.
Sent from my ADR6300 using Tapatalk
rothnic said:
Roebeet and I have confirmed that the 1.2 bootloader is not locked, it just has changes that other devices have gained before the Gtablet.
The 1.2 bootloader is compatible with pershoot's Zpad kernel and Adam kernels. The newer bootloader causes older kernels to fail because it requires extra voltage levels from the bootloader.
The Gtab can run Pershoot's Zpad kernel on the 1.2 bootloader. This means that the Zpad and Adam's bootloaders were from a newer branch of Malata's internal smba1002 kernel repo. If any future Gtablet or Adam kernels come out past 2.6.32, they will most likely be incompatible with the 1.1 Gtab bootloader, so it is best if people start moving ROMs on to 1.2 to prepare. We know that Notion Ink has Malata working on a post 2.6.32 kernel.
Click to expand...
Click to collapse
pershoot said:
ive updated the compatibility listing.
Click to expand...
Click to collapse
rothnic/pershoot- this is good news for the zPad and Adam - but not concerned about those devices, even if they're related. This is about the gTablet and if this bootloader requires certain things that come direct from the manufacturer - and discourage the custom creation and modification of kernels - how is that not locked?
If we have to use the zPad kernel on the gTablet because voltages have to be higher (odd) then don't we lose the advancements pershoot has made in the overclocking of the gTablet? And how does staying with a manufacturers regulated bootloader help with people who have decided not to use the crud coming from the manufacturers and instead want to make their gTablet more than it can be? Why are we still thinking we have to follow the manufacturer like sheep and not break away and become more?
Looking for answers, not trying to be antagonistic. Looking out for the community at large as well.
Good work on figuring that out for those on TnT and stock-based MODs. If it were going to be anybody it'd be you guys!
jerdog said:
rothnic/pershoot- this is good news for the zPad and Adam - but not concerned about those devices, even if they're related. This is about the gTablet and if this bootloader requires certain things that come direct from the manufacturer - and discourage the custom creation and modification of kernels - how is that not locked?
If we have to use the zPad kernel on the gTablet because voltages have to be higher (odd) then don't we lose the advancements pershoot has made in the overclocking of the gTablet? And how does staying with a manufacturers regulated bootloader help with people who have decided not to use the crud coming from the manufacturers and instead want to make their gTablet more than it can be? Why are we still thinking we have to follow the manufacturer like sheep and not break away and become more?
Good work on figuring that out for those on TnT and stock-based MODs. If it were going to be anybody it'd be you guys!
Click to expand...
Click to collapse
the voltages are not higher.
old/new bootloader kernel is the same (save for the attenuation of the extra voltage step). this is to update to the current standard of the device, as layed out by Nvidia.
Thats awesome news, and thanks Rothnic for posting it. I'm running one of Roebeets 1.2 ROMs now, so I look forward to being able to get pershoots custom kernel on it.
karlkarloff said:
Thats awesome news, and thanks Rothnic for posting it. I'm running one of Roebeets 1.2 ROMs now, so I look forward to being able to get pershoots custom kernel on it.
Click to expand...
Click to collapse
just flash the 0430 .zip from droidbasement labelled 'newbl', and you'll be set. that rom is froyo, so choose froyo.
if it doesnt flash properly with the stock recovery, then create a boot.img for yourself, stick that in the rom .zip, and flash.
pershoot said:
the voltages are not higher.
old/new bootloader kernel is the same (save for the attenuation of the extra voltage step). this is to update to the current standard of the device, as layed out by Nvidia.
Click to expand...
Click to collapse
Hmm - haven't seen any new standards from nVidia. Do you have a link?
So those wishing to use your kernel need to use the "new Malata bootloader" ones if they are on the 1.2 bootloader? Are you still going to be separating the kernels for those who want to stay away from what a manufacturer pushes and wish to stay with CM and other custom builds?
pershoot said:
just flash the 0430 .zip from droidbasement labelled 'newbl', and you'll be set. that rom is froyo, so choose froyo.
if it doesnt flash properly with the stock recovery, then create a boot.img for yourself, stick that in the rom .zip, and flash.
Click to expand...
Click to collapse
You're definitely going to need to provide a procedure for the above and then support it because there is a LIMITED few who even understand what you just told this user to do.
jerdog said:
Hmm - haven't seen any new standards from nVidia. Do you have a link?
So those wishing to use your kernel need to use the "new Malata bootloader" ones if they are on the 1.2 bootloader? Are you still going to be separating the kernels for those who want to stay away from what a manufacturer pushes and wish to stay with CM and other custom builds?
Click to expand...
Click to collapse
yes, just look at my github.
the kernels are seperate. this is outlined in the downloads and in source.
jerdog said:
You're definitely going to need to provide a procedure for the above and then support it because there is a LIMITED few who even understand what you just told this user to do.
Click to expand...
Click to collapse
just flash the .zip in recovery as you would any rom.
that's all.
if it hangs (it shouldn't, as someone else just did this without issue: http://forum.xda-developers.com/showpost.php?p=13588874&postcount=5), then you wait for someone to produce a boot.img in a 1.2 rom.
pershoot said:
just flash the .zip in recovery as you would any rom.
that's all.
if it hangs (it shouldn't, as someone else just did this without issue: http://forum.xda-developers.com/showpost.php?p=13588874&postcount=5), then you wait for someone to produce a boot.img in a 1.2 rom.
Click to expand...
Click to collapse
yeah - but you told the user to create a new boot.img, put it in the rom.zip and flash.... not wait for someone else. And what's the fall-back?
pershoot said:
yes, just look at my github.
the kernels are seperate. this is outlined in the downloads and in source.
Click to expand...
Click to collapse
Probably blind, but where in your github does it answer the question about nVidia and provide a link? and by your downloads are you referring to your blog site and the different blob of kernels? A suggestion would be to provide more of a writeup on which to choose - based on if you're going the manufacturer route or the custom ROM route.
Good work figuring out the locked bootloader and getting around it's restrictions.
pershoot said:
then you wait for someone to produce a boot.img in a 1.2 rom.
Click to expand...
Click to collapse
Only one person doing that as of now and I'm using the BC version. The updated version with the kernel will be released today
jerdog said:
yeah - but you told the user to create a new boot.img, put it in the rom.zip and flash.... not wait for someone else. And what's the fall-back?
Probably blind, but where in your github does it answer the question about nVidia and provide a link? and by your downloads are you referring to your blog site and the different blob of kernels? A suggestion would be to provide more of a writeup on which to choose - based on if you're going the manufacturer route or the custom ROM route.
Good work figuring out the locked bootloader and getting around it's restrictions.
Click to expand...
Click to collapse
the fallback is you reflash the rom. this is nothing new to the procedure.
this has been this way for weeks in my tree and blog postings. i need not add anything further to the postings. i just renamed the labelling to reflect the current gtab testing confirmation.
And how does staying with a manufacturers regulated bootloader help with people who have decided not to use the crud coming from the manufacturers and instead want to make their gTablet more than it can be? Why are we still thinking we have to follow the manufacturer like sheep and not break away and become more?
Click to expand...
Click to collapse
Let's be honest here, not every owner of a Gtablet is a developer that wants to unlock the pandora's box of great things that this thing is capable of. Some of us just (to be honest once more) wanted the cheapest alternative to the iPad that we could find. I use iPad, because it IS the industry standard...we wouldn't need terms like "iPad killer" if it wasn't what people strive to be or surpass, right?
in my opinion, the 1.1 based roms available right now do what you say we want, make it more than it can be. It takes the crud from the manufacturer and improves on it. Heck, some people actually like the crud from the manufacturer, but just utilize the market fix, to have access to more apps. I would say that most of the people that own a Gtablet flashed 1 rom, and still use it to this day, without messing with their Gtablet, for fear of breaking something (yea, that would be me) I'm perfectly happy with Vegan 5.1.1, and have no intentions of changing until there is an OFFICIAL Nvidea hardware supported rom, that allows for hardware acceleration. Kernel tweaks etc. are fine, and I'm running Clemsyns right now, but NVidea has stated that it will not support Harmony unless requested by a manufacturer. If we need their crud to get the drivers, then so be it...but we do need their crud, first. If NI is actually doing what VS can't, or doesn't want to do, then so be it, I'll take it. But, regardless, if the bootloaders are changing, and all new updates are going to be using that new format, then why not change with the times?
I can understand that the people sorking on 1.1 roms are feeling a bit jaded, since they are still working very hard on all of their 1.1 roms. I do sympathize with them, since it does appear that 1.1 is becoming a thing of the past.
I believe that Robeet's initial point was that there would be new Gtablets that will possibly be shipped with the 1.2 bootloader. Had those people come here and flashed a 1.1 Rom, not knowing the difference, they might be a bit upset with the results. 1.2 Roms needed to be made, just for the people that have the new bootloader. Me, personally, as I've said, I'll be sticking with my 1.1 Rom just the way it is right now until there is a huge significant change that will make me update to 1.2, and flash a new rom...but it must be stable, everything working, hardware accelerated, with kernels that work...might be a while before I switch from Vegan 5.1.1.
Regards,
Todd
pershoot said:
the fallback is you reflash the rom. this is nothing new to the procedure.
this has been this way for weeks in my tree and blog postings. i need not add anything further to the postings. i just renamed the labelling to reflect the current gtab testing confirmation.
Click to expand...
Click to collapse
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-2632/commit/b957d369741cf432146405a956cbc578fd201c80
http://nv-tegra.nvidia.com/gitweb/?...ff;h=7c97a1a4ebdff710907f9361cc05c1459cdeb510
pershoot said:
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-2632/commit/b957d369741cf432146405a956cbc578fd201c80
http://nv-tegra.nvidia.com/gitweb/?...ff;h=7c97a1a4ebdff710907f9361cc05c1459cdeb510
Click to expand...
Click to collapse
excellent - thanks pershoot.
NOTE: THIS ROM IS NOT CURRENTLY USABLE! DO NOT FLASH IF YOU DO NOT KNOW WHAT YOU ARE DOING
Ladies and gentlemen of XDA, I present to you ICS on the TF101! This ROM is currently very much still in development, and is not usable in it's current state, but it boots! This is more or less a proof of concept at the moment.
What's not working:
Display has a green overlay most of the time
Touchscreen
Wifi
Camera
HW Acceleration
Pretty much everything else
What does work:
adb
Boots to launcher
Touchpad on the dock (currently only method of input)
To install:
Download the system blob from http://mirror.mostoftheinternet.com/android/ROM/tf101/system-AOSP-20111230.blob.bz2
Boot into recovery
Do factory reset
Mount /sdcard using the menu
Use adb to transfer the blob to the device
Code:
adb push system-AOSP-20111230.blob.bz2 /sdcard/blob.bz2
Enter device shell
Code:
adb shell
Decompress blob and apply
Code:
bzcat /sdcard/blob.bz2 | dd of=/dev/block/mmcblk0p4
Reboot and wait for it to install
Done!
If you are able to contribute at all, please let me know. The Git repo for this is at https://github.com/Deathisfatal/android_device_asus_tf101/tree/cm9.
Dev notes:
Most of the random crashes (and the green colour) seem to be caused by an issue with the graphics
Eventually, I plan to move to CM9 once they move closer to release
Screenshot! (yay, green...)
http://mirror.mostoftheinternet.com/images/ics.png
this
is
sex
Congrats
Sent from my MyTouch_4G_Slide using xda premium
Are you going to setup a repository for this? I was actually planning on starting a port of my own but I would love the opportunity to jump in and work with you.
Already have, forgot to add it to the post
Thanks for the support, guys.
Nice to finally see even an early build as this, well done i`ll be keeping an eye on this thread
Deathisfatal said:
Eventually, I plan to move to CM9 once they move closer to release
Click to expand...
Click to collapse
This would make my day! If we manage to get CM9 to start working, I would love to help try or try to be the main man behind porting MIUI (English Site). I've helped a decent bit with porting it to my phone (Samsung Epic 4G). From everything i've seen so far the kernels of CM7 and MIUI are pretty much interchangeable, so it should be a fairly easy transition if CM9 functions. I don't know squat about kernels, so i wouldn't be of any help there though.
UH i had this like 3 weeks ago, but didn't post cuz it sucked so much.
Here's mine, no green stuff either.
I also didn't post it because it's a straight up kang of the Iconia guys' but whatever.
LOL
Thanks to OP for your hard work...
www.scienceprousa.com/jcarrz1/icstest.zip just flash in clockwork but don't expect much...........
Mind sharing your vendor files, jcarrz1?
Deathisfatal said:
Mind sharing your vendor files, jcarrz1?
Click to expand...
Click to collapse
Nope cause it's a straight-up kang of the iconia guys'. And they took their source down because n00bs b crazy.
I really admire that you actually have a device tree and stuff, I'm too inexperienced to do that.
Nice!
jcarrz1
Maybe this may help? https://github.com/CyanogenMod/android_device_asus_tf101
Was going to start an ICS port today as well so I'll be forking your branch and hopefully helping out. Glad we are going to get some progress on this!
arayray said:
Maybe this may help? https://github.com/CyanogenMod/android_device_asus_tf101
Click to expand...
Click to collapse
My original code is a fork of that. Their repo is pretty incomplete.
Was going to start an ICS port today as well so I'll be forking your branch and hopefully helping out. Glad we are going to get some progress on this!
Click to expand...
Click to collapse
Excellent!
Deathisfatal said:
My original code is a fork of that. Their repo is pretty incomplete.
Click to expand...
Click to collapse
Yeah its pretty outdated... Lets get a community effort here..
Good to see a start on this, a bit later than expected!
Sent from my Transformer TF101 using xda premium
For the graphics drivers, as the tf101 uses the same SOC as the xoom, it might be possible to pull the tegra2 drivers from google's wingray aosp sources (found here)
First of all for your work
You know what i dont get is this
http://phandroid.com/2011/11/27/asus-transformer-not-prime-gets-early-ics-port/
where is bumbledroids work?(this was november still)
i am a total retard when it comest od developing but if you ever need any beta tester i have loads of experience on rooting/romming devices an am in possesion of a SBK1 asus transformer with keyboard.
looking forward to giving it a go
Sent from my Lumia 800 using XDA Windows Phone 7 App
Are you compiling against AOSP or CM9?
telsk said:
First of all for your work
You know what i dont get is this
http://phandroid.com/2011/11/27/asus-transformer-not-prime-gets-early-ics-port/
where is bumbledroids work?(this was november still)
i am a total retard when it comest od developing but if you ever need any beta tester i have loads of experience on rooting/romming devices an am in possesion of a SBK1 asus transformer with keyboard.
Click to expand...
Click to collapse
Right, and if the cyanogenMod device tree for tf101 is by bumbledroid then why doesn't touch work yet?
jcarrz1
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/system.img.gz md5sum: 29a6c707d25520c28528b502bb190c7e
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
jimbridgman said:
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
https://dl.dropbox.com/u/45576654/system.img
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
Click to expand...
Click to collapse
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
EDIT: i assume the gs3 is GSM correct?
lkrasner said:
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
Click to expand...
Click to collapse
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is in the system.img file I posted.... just mount it as an iso and you can pull out /system/app and grab the Svoice.apk from there.
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
jimbridgman said:
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Click to expand...
Click to collapse
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
lkrasner said:
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
Click to expand...
Click to collapse
Yeah I think that is a good start. Take a look at this link, the guys from team epic that do cyanogenmod ports have come up with a way to use kexec to test booting thier kernel and roms. You might PM one of them, I have not gotten to that point yet, plus these guys are working on the Sprint version, of the SGS3, but I am sure they can explain how they are doing this with kexec. These guys are on XDA, I have chatted with them on a couple issues I was having.
http://www.epiccm.org/
Oh, P.S.
Here is how to compile the "stock MB/ME865" kernel:
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.3
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) CROSS_COMPILE= $(android platform directory you download)/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
$ export ARCH=arm
$ make m2_att_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
Just make sure the toolkit is pointed to the install of the codesourcery toolkit I linked in the above post.
P.P.S
Your defconfig might be another pointer name, that you will have to find out for sure. You know the one above called m2_att_defconfig.
For the beginners don't try the rom,you might kill your phone!
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Glad to see you back around here, but lets not even give anything towards JB until we get ICS. if you are interested in helping with that, send me a PM, I have made some progress with cm9 (as in it boots fine, and i have some ideas for the radio).
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Yay! Cogeary's back! Good to see you around again...
Sent from my phone's mind
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
ICS to JB is going to be a much smaller kernel jump, but there will be a HUGE performance increase due to project butter which is now officially part of Jelly Bean.
The key to running something like this is to get a kernel compiled and running with kexec, even though it is just 1 proc, it is a good way to get started. Ports will be much easier if you do some merging of the changed code in newer kernels and do merged kernel. There are instructions for doing a kernel that is merged from 2 sources to get a complete kernel.
Now this will just work for testing and porting, and the actual ICS or JB install from at least a leak will be needed to actually run the port, but you can get ahead of the game by doing what I have mentioned.
Well going to give this a go in a few days doing some maintenance on my computer but will get back with something (hope not a bricked phone) .....
(off topic ranting)
Hate to say it at this rate what getting close to a year since Ics release Jb might just be a pipe dream..... Think I am growing grey hairs waiting for something to give here..... Without bootloader unlock I feel so useless (Yea I could make a recovery image with all the bells and whistles but I got bigger plans).....
Downloaded so I could tinker with some files. Thanks for sharing.
Sent from my SAMSUNG-SGH-I997 using xda premium
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
sure, no problem, give me a bit, my internet is slower than hell where I am right now.
EDIT: of course I didn't add it to dropbox originally, so now it is uploading to google drive. It just hit 1%
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
I uploaded it to my Drive right away after downloading - try this for SGSIII ICS: https://docs.google.com/open?id=0B-CZ8hXV8qOiVGtjOHZ3ZEg5eFU
P.S. - I also have a JB dump there, if anyone's interested: https://docs.google.com/open?id=0B-CZ8hXV8qOiSkc3QkE1Y0ZsRkU
EDIT: make that 2 jelly beans: https://docs.google.com/open?id=0B-CZ8hXV8qOiS2QtcG41QUh4R1k
...I was pretty active during the I/O hype last week...
jimbridgman said:
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
Click to expand...
Click to collapse
Why not try Filedropper or Mediafire?
MagicXB said:
Why not try Filedropper or Mediafire?
Click to expand...
Click to collapse
I am actually trying to get my recognized developer cert on here and get free premium access to xdafilehost, that all the recognized devs get access to.
We will see if I get it or not. If not I have other options, but things like filedropper will not do, I already looked into it
How can I compile the tf201 jb asus kernel for tf101?
Im trying to port the official jb rom from the tf201.
cpu999 said:
How can I compile the tf201 jb asus kernel for tf101?
Im trying to port the official jb rom from the tf201.
Click to expand...
Click to collapse
I'd start by making a diff with the original kernel to see how bad the damage is first. Then you can probably manually port the Makefile to fit the old kernel and such, but it doesn't mean it'll compile, not by a long shot. You'll need to port the modules and possibly libraries too. I don't know enough about Android itself to provide instructions, but I know enough about Linux and the kernel to know this is going to be a painful task. Hope you can achieve this!
Lethe6 said:
I'd start by making a diff with the original kernel to see how bad the damage is first. Then you can probably manually port the Makefile to fit the old kernel and such, but it doesn't mean it'll compile, not by a long shot. You'll need to port the modules and possibly libraries too. I don't know enough about Android itself to provide instructions, but I know enough about Linux and the kernel to know this is going to be a painful task. Hope you can achieve this!
Click to expand...
Click to collapse
ok
im gonna try using rayman's divemaster first cuz ppl say it works on lots of things.
if that doesnt work, ill try that
this is just a demo of a kernel based on quarx 3.0.8 kernel sources,maybe later i'll try to merge several fixes or something but till then lets say i've reached a small milestone like finishing to compile this kernel,booting it up,take some screenshots from it.
known bugs,just like initial quarxs or blenchose commits.
Warning:flash at your own responsability,works only with cm 10.1 under boot options by ticking 2ndboot and ticking adb disable
link to kernel:http://www.mediafire.com/?vdjoj438tlvz2lw
NOTE:kernel sources are based on quarx repo on github:https://github.com/Quarx2k/jordan-kernel
What's this? A fix for CM10.1 23/01?
I think it's a 3.0 kernel... so not a fix.
i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency
Shubhamqweasd said:
i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency
Click to expand...
Click to collapse
you're right,because i could not boot this kernel on 4.1.2 so tried with 4.2.1 without adb manual boot,the difference is that i added forced module unloading and allow old eabi binaries to run with this kernel trying to get some backwards compatibility thus my conclusion is that either this kernel needs scratch bins in the os for propper functioning
rodrigoswz said:
What's this? A fix for CM10.1 23/01?
Click to expand...
Click to collapse
nope,my bad to mention that is an kernel build on quarx repo
You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^
Kayant said:
You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^
Click to expand...
Click to collapse
The thread is already reported
Sent from my MB526 using xda premium
nogoodusername said:
The thread is already reported
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig
drunk_ryder24 said:
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig
Click to expand...
Click to collapse
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium
nogoodusername said:
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance
drunk_ryder24 said:
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance
Click to expand...
Click to collapse
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
thats the whole point,everithing gets trouc the cross compiler even battery and every hw aspect for defy,but cant seem to get sgx drivers on it it boots but only backlight flickers,also the importance of this is that one day we might bump in a problem like this(maybe future android versions will use kernel 3.7.5 as default)and my opinion is that we should have some widen experience about it in any way possible
Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either
I understand your point and even I know nothing is impossible.
BUT, there has to be a logic in things that you are doing, isn't it? Believe me, Nobody is discouraging him. Anyways, its a matter of understanding and not a debate.
FYI and to my knowledge, very few devices like xperia T/V has kernel 3.4
abhifx said:
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either
Click to expand...
Click to collapse
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.
Kayant said:
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.
Click to expand...
Click to collapse
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method
drunk_ryder24 said:
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method
Click to expand...
Click to collapse
That sounds good am I bit surprised it worked so well with not that much errors but thats's good Yh I know Quarx is unstoppable and good luck with the project ..... If you need any more advice or help just shoot me up with a pm and I will see what I can do
kayant said:
that sounds good am i bit surprised it worked so well with not that much errors but thats's good yh i know quarx is unstoppable and good luck with the project :d..... If you need any more advice or help just shoot me up with a pm and i will see what i can do
Click to expand...
Click to collapse
thanks for your support,its wellcomed