I'm trying to get the kernel I've been working on for Captivate working on Vibrant. This poses a bit of a problem, because while I have access to a Vibrant kernel and initramfs, and a known-working config for Vibrant, I lack access to a phone.
I've forked a test branch based on what I have so far. I would appreciate pretty much any of the following:
a volunteer to build this kernel or test a binary
a volunteer to help with Vibrant development
any other Vibrant-specific details that don't apply to Captivate or to SGS in general
I have already built a binary, but it is mostly untested. I want to make it very clear that this is a testing kernel. It should work, it should not break anything... but it might not boot, it might wipe data, I haven't heard of it happening to anybody yet but it's certainly not impossible that it might damage hardware. These are unlikely, except for not working, but are all possible outcomes of trying this kernel. If you want to test this, read the OP in the thread for the Captivate version, have backups of your data ready, preferably duplicated to a hard drive or an SD card that is removed before testing. Have Odin3 and a stock Vibrant kernel on hand, and have ClockworkMod recovery installed.
If it hangs starting up, wait a bit, then pull the battery and start in recovery without trying to start up normally. Then, start clockworkmod, mount /system, and use adb to pull /system/user.log - this should contain a log of what happened when the user init scripts ran, and may provide clues as to what went wrong. You can make sure it doesn't include anything you don't want to reveal, and just PM it to me or join #sgs_dev on freenode and talk to me or some other developers there - perhaps a dev with a Vibrant will have a better idea where to start.
In the long term, I would not mind somebody forking the github repository to work on any Vibrant-specific issues. I can then try to pull changes from a fork and do builds for both phones, if somebody doesn't want to do the Vibrant builds themselves.
Good luck, and thank you.
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
ill be more than happy to test the binary
I too will be more than happy to give any sort of help possible. Should this be a start from a stock kernel and build deal, ie stock kernel stock rom just rooted with clockwork?
Sent from my Vibrant using tapatalk pro
If you're using a lagfix with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
EDIT: "lagfix", thx swype.
Unhelpful said:
If you're using a ladies with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm about to build from your source i just forked to see whats diff then mine. They look though to be about the same except for nilFS
I will probably fork and maintain a vibrant tree with ivan who also has a Vibrant. That way we can get the best of both worlds. And being that we are in the same IRC we pretty much have identical mods to our kernels.
So most likely any changes you make to your captivate Kernel will end up in the vibrant branch as well and I also have the device to test with
See ya in IRC
anomalous3 said:
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
haha if ur talking about the linux distro i know what u mean
Excellent news! I have some things in my tree I think you could use here, too, but it's much easier to have a developer with a Vibrant who can build them and test immediately.
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
rei165 said:
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The stock captivate kernel doesn't have any "advantages" and wouldn't really work. Unhelpful, however, has added nilfs support to the captivate kernel as well as some other tweaks, and has now made these changes available to the Vibrant community. As I understand it, NILFS mounts, reads, writes, and unmounts faster on our devices than any of the other filesystems he tested, so there's hope for a permanent lagfix.
I tried this kernel, it does boot but my existing lagfix scripts don't work with it, so I lose all my data. No big deal to fix from recovery, just revert to stock before messing with it if you want to test it. As mentioned, no real advantage either way, but it's nice to have options.
If there is interest, I'll fix my lagfix scripts to run on this kernel. Reverting back to JAC OVv4 works without hassle via clockwork.
Related
This was the tweet fromCvpcs!!! (We haz a booting "true" AOSP system with 0 blur! http://www.youtube.com/watch?v=PPqfIRZP7Mc Still very buggy but I'm working on it)
Sent from my DROIDX using XDA App
booyah! let get er done!
Sound like good news!
Still, could anybody explain what AOSP boot means? Will this enable us to boot a custom kernel on the x?
I have no idea what this means except 100% no blur sounds awesome!
AOSP essentially means it was built completely from source. Not built based on Moto's own build with their custom framework (blur) crap. It is a true complete Vanilla rom.
Android Open Source Project
http://source.android.com/
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
If they got an aosp to run they should be able to modify the kernel no? Thought that was the while point of the exploit nenolod is working on.
Sent from my DROIDX using Tapatalk
this is too awesome.
Joe92T said:
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
vonfeldt7 said:
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
Click to expand...
Click to collapse
This AOSP has actually been running for a while now. Its being developed by cvpcs, the same guy who's been developing the Sapphire roms for Droid. I don't know if he's using the recent exploit that has made the rumor-mill lately. He claims its a true AOSP boot, which implies a custom kernel compiled from source. However, for all we know he could still be using the Moto 2.2 kernel, but replaced everything else in user space with fresh, compiled code.
Either way, its interesting. Despite Motorola's best attempts, it looks like the Droid X (and Droid 2 by implication) will soon be free of its eFuse prison, allowing us users the choice of what to run on this device.
We won't be getting rid of eFuse, as it's hard coded into the silicon itself in NVRAM, as I understand it. Its just that folks are working on getting the keys to the prison .
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
sniffle said:
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
Click to expand...
Click to collapse
Thank you guys for your hard work, I am sure that most of the community is as excited as I am to see your work make it to the X. I love the boot ani from the video, and even though this is my first android phone the things Ive read about your teams previous releases has me EXCITED for this to hit.
appreciate your update and clarification, sniffle!
OMG, aosp 2.2 for my droidx would be awesome. Nice to set someone working on it, props and kudoes.
Sent from my PC36100 using XDA App
i hear this is almost 100% working!
LT1UltraZ said:
i hear this is almost 100% working!
Click to expand...
Click to collapse
Heard the same this morning. Very excited!
dogswind said:
Heard the same this morning. Very excited!
Click to expand...
Click to collapse
Would love a source on this info.
Almost 100% is a bit too strong of a descriptor, there are still some major bugs like rebooting on sleep(hitting the power button to turn the screen off) and a few others on top of that. With our next sapphire and Ruby release we will be making the latest build publicly available for other development to help figure out a fix for these problems.
Just out of curiosity, is it at all possible to flash a kernel from a different phone? I noticed that the Droid Incredible has 2.6.32.17 while we are still at 2.6.29.6.
What all is involved with porting it over? I'm sure the source code is needed.
No it's not possible (different hardware). However, both Darch and Deca are working to get the HeroC onto the .32 kernel.
Thanks for the reply. I don't know why the hardware issue didn't click in my mind. I guess I was thinking that since they are both CDMA networks that they would work.
The kernel has hardware specific info in it. The 2 devs working on it are basically taking the base kernel and adding and modifying it to work on our phone. Its very time consuming and a lot of trial and error.
Sent from my HERO200 using XDA App
What is this? It's an experimental ROM install setup that avoids the use of RFS entirely. The install basically pre-voodoo's your phone. If you know you want voodoo, this is faster than installing then doing voodoo, but it's a little more complicated. Not much, but be warned. It avoids the use of RFS durring install completely, so no RFS corruption to worry about.
The ROM itself is mostly untouched. The kernel is my Dragon Kernel, i9k based, so it will eat your battery (froyo only, eclair is better as we have source). I can get about 12 hours out of it. Buy a charger.
The new version is a 1-click install. It installs the kernel, reboots into it, then auto-installs the ROM. I tested it coming from JFD without issues.
These are based on voodoo5 beta code. Curio is releasing voodoo5 stable here soon, and I'll post an updated no-wipe kernel flash for that.
The ROMS are Team Whiskey Obsidian, Onyx, and Fusion. I changed the install procedure and the kernel out, the rest is as they made it. I take no credit for the ROM. Please post bugs here however, so I can make sure they are ROM bugs before letting TW know about them. I'm running the Onyx version as my daily driver. There has been some private beta testing, and they seem stable, but do have Odin handy just in case. I have installed over the top of various ROMs, but the safest way is probably to come from JFD just to be sure.
ALL THESE ROMS WIPE. NO, I WON'T CHANGE THAT.
Obsidian V5b: http://www.tabbal.net/files/Dragon-Obsidian-Installer-v1.0.zip
Onyx 4.2: http://www.tabbal.net/files/Dragon-Onyx-Installer-v1.0.zip
Fusion Final: http://www.tabbal.net/files/Dragon-Fusion-Installer-v1.0.zip
NOTE: THESE INSTALL VOODOO. ALL THE USUAL VOODOO PRECAUTIONS APPLY, IF FLASHING SOMETHING, DISABLE IT FIRST.
The latest voodoo stuff seems to play nicer and I have flashed things from clockwork without bricking, but just be warned.
Updates:
Kernel with the stable voodoo5 release. Should work with any froyo ROM, does not wipe.
http://www.tabbal.net/files/Dragon-Kernel-Voodoo-v2.0.zip
I can conform that these are indeed working. And they work beautifully. I'm evening thinking about going back to some voodoo love.
Love your work ttabbal.
"if you amplify everything, nothing is heard"
Hmmm...cool. Might have to try this with Axura 2.1.
geoffcorey said:
I can conform that these are indeed working. And they work beautifully. I'm evening thinking about going back to some voodoo love.
Love your work ttabbal.
"if you amplify everything, nothing is heard"
Click to expand...
Click to collapse
Curious! So what's the true (RFS free) Quadrant score for Vibrant?
Can we have just a kernel flash that will convert all the partitions? supercurio's i9000 flash doesn't wipe the data, it simply tars it and then untars it back once the conversion is done to each partition. Thanks for the hard work.
dasunsrule32 said:
Can we have just a kernel flash that will convert all the partitions? supercurio's i9000 flash doesn't wipe the data, it simply tars it and then untars it back once the conversion is done to each partition. Thanks for the hard work.
Click to expand...
Click to collapse
The post is about the ROMs, but yes, the kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
It's the custom kernel I reference in the OP. If you want more than about 12 hours off charger, don't install it. I'm going to look at Eugene's recently posted source to see if I can implement whatever he did to get the kernel sleeping better, but no promises. And reports are kind of mixed last time I looked at it anyway.
When Samsung gets around to releasing source, we can do better. Till then, give me a patch or don't complain about it.
ttabbal said:
The kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
Click to expand...
Click to collapse
Nice. I'll hold off trying this with Axura 2.1 until this posted, then. A battery life of 12 hours is fine in exchange for what Voodoo will provide in return.
ttabbal said:
The post is about the ROMs, but yes, the kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
It's the custom kernel I reference in the OP. If you want more than about 12 hours off charger, don't install it. I'm going to look at Eugene's recently posted source to see if I can implement whatever he did to get the kernel sleeping better, but no promises. And reports are kind of mixed last time I looked at it anyway.
When Samsung gets around to releasing source, we can do better. Till then, give me a patch or don't complain about it.
Click to expand...
Click to collapse
Sweet, thank you.
i flashed this on obsidian v5 beta w/ jk6 modem and it running like a champ. however, you were right about the battery life
thanks for posting it before hand. i appreciated.
Love the new kernel would u consider an overlook version? Eugene 1256 is so snappy but it corrupts data. That speed plus voodoo is crazy fast. Real 2000 + quadrant.
Sent from my GT-I9000 using XDA App
Froyo Kernel on Eclair?
ttabbal,
I did not know that a Froyo kernel could be backward compatible to Eclair. Is that the case, given that your Dragon 2.0 incorporating Voodoo 5 Stable will work with Bionix Fusion?
Please help me to understand this.
More to the point, I am on Bionix 1.9.1. Would Dragon 2.0 w/Voodoo 5 Stable work on my setup?
Thanks,
Bruce
Would love to use this, however i cant seem to get anything to install from the market no matter what i do. My TitaniumBackup restores just fine(apps only). Ive ODIN'd back to JFD twice but still nada. Ill try starting from JI6 and see if it helps.
dbacchus said:
Curious! So what's the true (RFS free) Quadrant score for Vibrant?
Click to expand...
Click to collapse
So I'm running ttabbal's latest kernel, 2.0, and just ran a quadrant. It gets 1564 as the score. Now, this isn't just from voodoo alone, he's done a few speed tweaked which will bump up the score. But it's snappy as hell.
"if you amplify everything, nothing is heard"
Just put this in my phone and its works fine I'm running axura 2.1 works fine but u will see a second boot up screen the benchmark test is not that high I got in the 2500 with the oclf inthe market download but can't do that one anymore it tells me I have one installed already but over all its smooth
Don't worry about benchmarks, they are easy to fool in a high level system like Android. Cyanogen managed to get something stupid like 10k out of Quadrant.
This setup isn't for being a benchmark queen. It's targeted at a couple things I deem important. Multitasking smoothness/performance, and a test of direct-to-ext4 install. The no-wipe voodoo kernel is really intended to be used as part of the whole, but like I said, it should work with any froyo. Note: NOT ECLAIR. If there is more demand for an eclair version, I'll consider updating my eclair ramdisk as well.
As for the market, couldn't say. It's NOT the rom/kernel though. The market is a finicky thing and sometimes just doesn't work. It's usually the server side or the app itself that has an issue though. There's also an update to Market for Froyo, it seems to be more stable. You should get it downloaded automatically after running for a while. To check, look at an app description, you should have a new tab "Related".
When I've had market problems, I fire up my Wife's G2 on a stock rom (not even root) and she does too, so it's not anything I, or anyone other than Google, can control.
Does anyone know whether the Dragon Kernel that works with any Froyo ROM available from the OP supports use of a BootAnimation.zip?
UPDATE: Thanks geoffcorey for the info!
Tried on Axura 2.1 with larger nand. Flashed, rebooted, converted with no issues and is running very well so far. Haven't been successful getting Voodoo to run before now.
Thanks to TW, ttabbal, Supercurio, et al.
epakrat75 said:
Does anyone know whether the Dragon Kernel that works with any Froyo ROM available from the OP supports use of a BootAnimation.zip?
Click to expand...
Click to collapse
yes, it supports bootanimation.zip
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Sent from my SGH-T959 using XDA App
joe.kerwin said:
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Click to expand...
Click to collapse
I did this very thing in my post #16 above yours. Go for it! Remove any other lag fixes you may have though. I had none installed so I didn't have to do that. PERFORM A NANDROID backup and optionally copy to a computer before flashing the kernel to be safe. Restoring the Nandroid backup won't restore the kernel though.
The dangers are minimal if you backup. Permanently bricking the phone is unlikely. You may soft brick but you probably won't. PLUG IN AND DON'T TURN OFF THE PHONE UNTIL THE "TW" LOGO DISAPPEARS! Around this time, you will hear a voice say voodoo has been activated.
I believe the conversion process may attempt to revert the changes it tried to make in the event of an unsuccessful conversion. If reversion is successful then you should again have access to CWM to flash back to any rom you have stored on your phone. Use nandroid to restore your data and your back to normal.
joe.kerwin said:
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Heimdall... Um if you cant get into download mode perhaps you shouldn't flash experimental things.
Sent from my SGH-T959 using XDA App
So we have root, custom kernel, and now CWM. It is about time we have a custom ROM to flash. Still no developers with the device, but we have gotten this far with the help of other developers without the device. I was thinking we could get a list of requests and then contact the right people and provide them the files they need to modify.
I guess ill start with the most obvious ones.
[*] Root / SU / Busybox
[*] Zipaligned
[*] Deodexed
[*] Ad Blocking
[*] Browser tweaks
[*] Bloatware removal
[*] OC kernel?
[*] CWM 5.5.0.4 w/ .hidenandroidprogress built in
[*] Updated stock apps
[*] Extended Power Menu
[*] Theming? (not necessary)
[*] Tethering
Thats all I can think of for now. Once we get a list of things we can begin to find someone with the skills to do it.
Pretty much what you mentioned. And of course the obvious one. ICS is the big want and I know it will take some time. Preferably right now a cleaned up stock rom and themes would be cool.
So i installed linux on my netbook along with dsixda's ROM kitchen. I dont know much but ill see what i can do.
so yea.
so far i can create a ROM which is bloatware free, zipaligned, deodexed, rooted, CWM w/ hidenandroidprogress, updated system apps, with or without OC kernel, and with tethering. sweet.
basically teaching myself though so it may be a while.
I'm not really active on these forums, but I'm also available for testing on my i957. (Wasn't allowed to post in the dev forum until I hit 10 posts)
Yep all the above. the main thing is to get rid of this UI lag.
On my 8.9 LTE i just used another launcher and it was gone...
I'm using another launcher and it's almost gone. I still get forces. I really want to do a full restore of the original rom before any roots and try to push the OC and libs again. The stock ROM I was given by Croak only helps recover from issues but not the ones I mentioned. It never had force closes or any weird issues before. But since the OC it's been running kinda crazy.
Thanks Orlando for the initiative!
In addition to what you have written, If possible, I would also would love to have:
1. Icons representing cellular speed (2G,3G,H,H+,4G) as on my SGS2.
2. JKAY mod. I don't know if this mod is SGS2 only mod or not. , but if it is possible to port it to our tab it would be great.
Thanks
I am not a dev by any means. I just dont have the time to teach myself all of the ins and outs that sammy devs and AOSP devs do. I give them so much credit. Coming from years of a windows base and no programming experience, its tough. I cant make up for what real devs can do, but for now I think I can get a ROM out which will be decent until we can get some real help.
I thnk as soon as we get a good stable, flashable, deodexed base it will open up a lot more easily implimented possibilities for theming and adding/subtracting little odds and ends that differentiate some of the different major ROMS.
My suggestion is to just work on good stable base ROM with fully functioning basics first and let the community work it from there.
I really need to fix the update-binary and the update script in order for this to work in CWM.
but basically I just did simple automated tasks. Kitchened from my nandroid.
Rooted
Superuser
Busybox
Deodexed
Zipaligned
Da_G Overclock Kernel
NoFrills OC App
Custom Libs for OC
Asus Water Wallpaper
Asus Weather Widget
Titanium Backup
Rom Manager (Dont Use It)
Custom Boot Animation Enabled
Bash Shell Support
CWM 5.5.0.4 w/ .nandroidprogress
If it turns out that the nandroid wont work well, then the stock will have to be modified, which means basically just deodex, root, zipalign. thats about all I can do. I wish i knew more about the whole android system but sadly i dont. i am trying to teach myself but it is going to be slow, so i pray we get a real dev soon.
Whatever you can do man is much appreciated. I wish I had a coders heart and talent. Because spend enough time on a PC to be able to contribute if I could this type of coding.
I thought I had everything set and tried to flash and just got bootloops. Then I just took the stock ROM and made a flashable zip from the stock firmware and that didn't even boot. Really discouraging and it took forever to get my tab back to working. Might be better just to wait for someone who knows what they are doing.
Sent from my SAMSUNG-SGH-I727 using xda premium
Google Maps 6.2 Ownhere Mod is a most... For any rom...
Sent from my SAMSUNG-SGH-I957 using xda premium
orlandoxpolice said:
I thought I had everything set and tried to flash and just got bootloops. Then I just took the stock ROM and made a flashable zip from the stock firmware and that didn't even boot. Really discouraging and it took forever to get my tab back to working. Might be better just to wait for someone who knows what they are doing.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Take it easy... Did you took the $7 AT&T insurance for the tab? Usually the AT&T sales rep. does not even know that there is an insurance option for this tab. I went online and saw there was insurance... And mentioned it to the AT&T rep. when buying the tab and he said there was no insurance option... And I told him, yes there is! And he double check and finally realized there was insurance. I took it, because I know the feeling of converting into a brick a brand new shiny device, lol... And look where I am... Already rooted, O/C, flashed recovery and waiting for CM9 or any rom available, lol... Just taking the sidewalk on brick ave. Lol...
Sent from my SAMSUNG-SGH-I957 using xda premium
Gsm calls please
Sent from my GT-P7300 using XDA App
I am going to look into insurance today. if i can get it then ill keep flashing away
couldn't get logcat working though to figure out why the flashes went bad...
Got the insurance!
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
Got the insurance!
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Great! so now... where can I download the orlandoxpolice ultimate kick ass rom? with all the features mentioned above with CM9 support, voice support for calls, that even unlocks tablet for any gsm sim card and all the latest versions of everything on the market? ahhh and everything in 4D of course... lol
Since nobody seems to check the Q&A forum [Q] Kernel compiled in Ubuntu 12.04 fails
So i havent worked on a kernel in a while and decided id start workin on one again. Well I recently updated to 12.04 lts and no changes to my old source I just did a test compile and it wont boot. Same toolchain, source, ramdisk, etc.
Is there some sort of issue with compiling on 12.04?
Even redownloaded the source from my github and tried the toolchain recommended by samsung, stock tool chain, and 3 others and i still get nuthin. Just trying to compile a 2.2 kernel for the vibrant. No source i download works am i missing something?
does ANYONE have any ideas? I dont care who you are just something! I been at this for a freakin week and cant figure it out, ......i've changed nuthing but the OS and i really dont want to have to redo my entire setup because it is such a huge pain
Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html
trailblazerz11 said:
Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html
Click to expand...
Click to collapse
100% sure it works, its the same source as my old nightly# 3 kernel which i can flash and works fine. Its a 2.2 kernel so thatd be the main diff there, and I've already done the setup of the build environment. I dont get past the vibrant logo so i have no idea what the problem is >.< its driving me nuts
i tried the linaro TC, 2 diff code sourcery, google toolchain even, and no luck
I even started a fresh kernel from scratch and added just the EXT4/voodoo stuff and my ramdisk and still nuthin
so i remade my voodoo ramdisk and that still doesnt work.
I'm out of ideas, I've quadruple checked to make sure all my tools and erthing are installed......idk what the issue is
Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high
helikido said:
Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high
Click to expand...
Click to collapse
Id rather not but it seems that might be the case -_- I gotta look into how well older versions of ubuntu suppport the BullDozer cores before i do i guess.....
also I only made GB kernels for the NS4g i think ? o .o Vibrant I had been workin on it but I like being able to have MSAA in my games and what felt like greater stability, so i scrapt the new projects in favor of specific features i use :3
Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.
hurtz777 said:
Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.
Click to expand...
Click to collapse
I've been gone working on a game project, so I really haven't been doing much android stuff in months. If I get some time I might but can't make promises. Don't take this the wrong way but I'm looking for some help if anyone has any ideas not requests or compliments on previous work (though both are appreciated)
Sent from my Galaxy Nexus using Tapatalk 2
Can you use windows xp to compile kernels?
helikido said:
Can you use windows xp to compile kernels?
Click to expand...
Click to collapse
no
10 char
No but ty for the try....looks like imma have to revert back to 11.10...so let it be known for best results on compiling android use Ubuntu 11. If u have Ubuntu 12 and it works fine then leave it and good for u
Sent from my Nexus S 4G using Tapatalk 2
Hey there! Try downgrading gcc and g++ to version 4.4. If that doesn't work you can always just set up a dev VM in xen or vmware instead of blowing away the whole box. Hope that helps.