Related
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.
http://forum.xda-developers.com/showthread.php?t=772795
Apparently it is possible to run the PSFreedom Jailbreak App on all MSM72x CPU, and considering the Tattoo has one, then theoretically it should be able to run it right?
But in it's current state, will it work on our Tattoo's and how in the freaking hell does it work anyway? xD
Anyways, just wanted to drop this here.
It would be wonderful *______*
I was thing of that.. lol
Well we just have to give it a try...
KezraPlanes said:
http://forum.xda-developers.com/showthread.php?t=772795
Apparently it is possible to run the PSFreedom Jailbreak App on all MSM72x CPU, and considering the Tattoo has one, then theoretically it should be able to run it right?
But in it's current state, will it work on our Tattoo's and how in the freaking hell does it work anyway? xD
Anyways, just wanted to drop this here.
Click to expand...
Click to collapse
Is confirmed the porting on android and psp. But we don't know what will need to run. A new kernel, sure. Maybe the terminal emulator (or a gui) to start/stop the deamon.
francians said:
Is confirmed the porting on android and psp. But we don't know what will need to run. A new kernel, sure. Maybe the terminal emulator (or a gui) to start/stop the deamon.
Click to expand...
Click to collapse
As far as I've heard, you need to not have USB at all (only charging works) to be able to run this.
So either as someone said on the original thread, someone makes a recovery image that we can flash for that same purpose OR dual-boot from SD.
To be honest I don't see the second one happening on the Tattoo
To run this hack you'll need a non-senseUI 2.2 rom.
https://spreadsheets.google.com/lv?key=tarAC83Wjsq2QZvP4iR5mlw&toomany=true
At least on kernel 2.6.29 (spqrom 0.4), the tattoo uses the msm_hsusb driver instead of the MSM72K, so i don't think it will work without porting it. But the hero and dream use msm_hsusb on 2.6.2x kernel and MSM72K on 2.6.3x. Maybe a kernel update could fix this for us (hear that, rom cookers? update the kernel of your froyo roms!)
blackkn1ght said:
To run this hack you'll need a non-senseUI 2.2 rom.
https://spreadsheets.google.com/lv?key=tarAC83Wjsq2QZvP4iR5mlw&toomany=true
At least on kernel 2.6.29 (spqrom 0.4), the tattoo uses the msm_hsusb driver instead of the MSM72K, so i don't think it will work without porting it. But the hero and dream use msm_hsusb on 2.6.2x kernel and MSM72K on 2.6.3x. Maybe a kernel update could fix this for us (hear that, rom cookers? update the kernel of your froyo roms!)
Click to expand...
Click to collapse
Hi,
In eclair kernel for tattoo there are the drivers for MSM72K! Later i ll try to
compile a kernel with MSM72K support for tattoo and publish it here to test
it.
Seg.
Nice already some progress
Well were we go... for Desire and G1...
h**p://forum.xda-developers.com/showpost.php?p=8025826&postcount=52
h**p://www.ps3-hacks.com/2010/09/06/hack-your-ps3-with-your-androiddesire/
it works?
Im going to try this now :0
already try, does not work((( at spqrom 0.4
I tried flashing the zip and it said error in /sdcard/PS3-signed.zip (Status 0)
That's because they weren't made for the Tattoo
Tattoo appeared in the list http://psfreedom.com/wiki/index.php?title=Device_compatibility_list. waiting ...
It works on HTC Wildfire : http://www.ps3underground.net/esclusiva-port-del-psfreedom-su-htc-wildfire/
tibob33 said:
It works on HTC Wildfire : http://www.ps3underground.net/esclusiva-port-del-psfreedom-su-htc-wildfire/
Click to expand...
Click to collapse
The wildfire uses the same msm_hsusb as shown in the graph, so maybe the ball is now rolling?
Edit:
I flashed the wildfire zip and it returned no errors like the other zip, but failed to go past the tattoo logo on SPQRom 0.4.1?
Incorrect boot.img I guess
Wildfire kernel 2.6.32
Tattoo kernel 2.6.29
so probably if you use segway's experimental .32 kernel it is going to work . try it.I don't have a ps3.
rwmanos said:
so probably if you use segway's experimental .32 kernel it is going to work . try it.I don't have a ps3.
Click to expand...
Click to collapse
Im pretty noobish at android stuff, seen the thread and gone to the link and there is loads of files... please guide
So I've just recently flashed my vogue with myns donut for a couple days and It was pretty good. The camera worked but no video and neither did the gps. I understand that for verizon you have to follow a specific procudure to get that to work so that makes sense. I'm just curious to what android roms they are using for their vougue. I'm looking for one that has the most working features. Let me know what it is and how you had it set up.
For my Fresh Froyo although remember android no is 100% stable but Fresh Froyo is very good.
If you know what you want my barebones build is known to be one of the fastest and most stable builds. With that though you need to get the apk's to what you want and add them in. It is meant to be as cut down to the minimum to be light and lithe on our devices.
Another way to get apps is to use the market, I have the most recent version of the market in my build. CM 6.1 is Froyo based so you have video and all the other froyo features.
aceoyame said:
If you know what you want my barebones build is known to be one of the fastest and most stable builds. With that though you need to get the apk's to what you want and add them in. It is meant to be as cut down to the minimum to be light and lithe on our devices.
Another way to get apps is to use the market, I have the most recent version of the market in my build. CM 6.1 is Froyo based so you have video and all the other froyo features.
Click to expand...
Click to collapse
I tested more than 10 ROM including the yours and I am sorry to tell you than ever before me to worked well even the last released CM 6.1, does not work properly with the kernel that is in my signature and is the one that works best with the USB sync and just by this already this ruled out your ROM, so I'm still saying Fresh Froyo for me is the more stable and clean ROM of froyo that I tested.
Josue_181 said:
I tested more than 10 ROM including the yours and I am sorry to tell you than ever before me to worked well even the last released CM 6.1, does not work properly with the kernel that is in my signature and is the one that works best with the USB sync and just by this already this ruled out your ROM, so I'm still saying Fresh Froyo for me is the more stable and clean ROM of froyo that I tested.
Click to expand...
Click to collapse
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Josue_181 ......Any chance you could post where you got the exact images/files etc. if it's not too much trouble. Thanks! I hope to run from haret if possible.
I have searched but it has been a while since I looked in this section. Is it DZO's Fresh Froyo you use and I cannot find Kernel: 2.6.25 10-31-10??? Hope you can help, thanks.
aceoyame said:
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Click to expand...
Click to collapse
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
aceoyame said:
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Click to expand...
Click to collapse
Would have to prove with that kernel I know how to adapt the kernel Clemsyn's to our Vogue if it works I comment as I was to see if I change my mind about your ROM
krwilson said:
Josue_181 ......Any chance you could post where you got the exact images/files etc. if it's not too much trouble. Thanks! I hope to run from haret if possible.
Click to expand...
Click to collapse
The thread Fresh froyo this here, as well as guides for the installation of haret/nad, only is question search and read...
Prowess said:
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
Click to expand...
Click to collapse
our vogue would not benefit from the battery enhancements since our kernels were designed for our battery
Okay so you say fresh froyo is one of the best? I looked it up but I am confused about what to download. Any advice would be great. I know how to install it I just dont know what file is the latest/best
loffyg said:
Okay so you say fresh froyo is one of the best? I looked it up but I am confused about what to download. Any advice would be great. I know how to install it I just dont know what file is the latest/best
Click to expand...
Click to collapse
This is my situation too....as I posted above. I know how to install, but am unsure of exactly what you are recommending as to the Fresh Froyo files. Thanks again.
Well try to be brief to that understand... (my English is very bad).
They must go to the thread of Fresh Froyo and go to this page, there download the ROM latest although I recommend the penultimate that is in my signature the most recent gave me problems.
The ROM download whith the name system-froyo-us-unodex-XX-XX-XX (X are date) have to rename it to androidinstall.tgz and copy in the ANDBOOT folder then locate the kernel of their choice here, the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
For the rest follow the installation guide in NAND is here and everything should go well.
Not be as it is done for HARET but here also the Guide to install in haret. I believe with what I said is more than enough so installed android in their device.
Best regards.
Josue_181 said:
Well try to be brief to that understand... (my English is very bad).
They must go to the thread of Fresh Froyo and go to this page, there download the ROM latest although I recommend the penultimate that is in my signature the most recent gave me problems.
ROM: Fresh Froyo 2010-12-03
Kernel: 2.6.25 10-31-10
The ROM download whith the name system-froyo-us-unodex-XX-XX-XX (X are date) have to rename it to androidinstall.tgz and copy in the ANDBOOT folder then locate the kernel of their choice here, the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
For the rest follow the installation guide in NAND is here and everything should go well.
Not be as it is done for HARET but here also the Guide to install in haret. I believe with what I said is more than enough so installed android in their device.
Best regards.
Click to expand...
Click to collapse
Okay I am pretty sure I understood what you said. I have the files you suggested thanks for the help I will try it tonight.
Josue_181 said:
the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
Click to expand...
Click to collapse
It works in Ubuntu Linux. It does not work for Windows 7, at least that I could configure successfully.
I'm using SuperFroyo and the 2.6.32.9 Kernel and a few things I noticed to make it more stable: don't use a Task Killer and be sparing in your use of a cache cleaner. Seriously, a week of doing that has really helped things. Trust the Linux Kernel, it's not Windows. I also used Autostarts to prevent a few of the more eager apps from starting automatically post-boot, but that's optional.
Prowess said:
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
Click to expand...
Click to collapse
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
So it loses a lot of those tweaks but I can say 1 thing about cm6.1 and 7 so far, they are getting rather large themselves, I can look into cm7 for hero and find atleast 10 apks that just take up space or are only good once
aceoyame said:
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
Yeah that is true, it's why I made a barebones.
goducks3620 said:
It works in Ubuntu Linux. It does not work for Windows 7, at least that I could configure successfully.
I'm using SuperFroyo and the 2.6.32.9 Kernel and a few things I noticed to make it more stable: don't use a Task Killer and be sparing in your use of a cache cleaner. Seriously, a week of doing that has really helped things. Trust the Linux Kernel, it's not Windows. I also used Autostarts to prevent a few of the more eager apps from starting automatically post-boot, but that's optional.
Click to expand...
Click to collapse
Does seem contradictory as to not use a task killer, the task killer close applications that are open and if you don't use are accumulating and this put slow the phone, the APP autostarts manager if I heard but none that worked well in my Vogue, which do you use?
aceoyame said:
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
Click to expand...
Click to collapse
Using this kernel modified with atool I may obtained the benefits mentioned in the battery life?
aceoyame said:
Yeah that is true, it's why I made a barebones.
Click to expand...
Click to collapse
even with barebones, the cm settings along with the now statistic reporting and updater (which cause FC's if removed) are still pretty huge. i have grown to like cm7 on my hero but with having so much stuff commited to the project as much as i hate to say it, there is starting to be alot of ::gulp:: bloatware
Josue_181 said:
Does seem contradictory as to not use a task killer, the task killer close applications that are open and if you don't use are accumulating and this put slow the phone, the APP autostarts manager if I heard but none that worked well in my Vogue, which do you use?
Click to expand...
Click to collapse
You don't need a task killer. The newer versions of Android will shut down apps that aren't being used if the resources are needed elsewhere. If you run a Advanced Task Killer or something similar, it will use system resources shutting down apps that then re-open themselves, which the task killer will again kill. It drains the battery and makes the OS unstable. Uninstall your task killer for a few days and see if it helps.
I use Autostarts because it fixed a problem--the music player started randomly. I also use it to prevent some apps from starting up but it is probably not necessary.
Please!!!
any answer?????'
Use the search button before you make a thread!
i haven't found anything about the x8
lucasiumej said:
i haven't found anything about the x8
Click to expand...
Click to collapse
And chances are that you won't find a tutorial about how to cook a ROM for the X8.
In theory you have all the information you're possibly looking for around in the General Android Forums section as well as in the Chef section.
To build from scratch you need the Android SDK/NDK, the Android source code (you're most likely looking for the CM7 git sources), a kitchen, maybe Eclipse (the Integrated Development Environment) and a whole lot of coding experience to tackle the task. EDIT: You also need: A computer featuring a CPU supporting 64-Bit, a 64-Bit Linux distro (i.e. Ubuntu or Linux Mint in their x86_64 edition) and AT LEAST 8GB RAM to successfully compile Gingerbread/ICS.
The easier task might be to mod a existing ROM (of course ONLY with the express permission of the author of the ROM as well as of all other developers whose modules you are using), but even this requires a solid knowledge about what you're doing.
Oh, and you also need a phone where you can test out your ROM creation (just because it works in the SDK Emulator does not mean it works on the real device), and you need to be able pull your phone back out of "bad flash" in case your ROM or Kernel creation bricked your phone.
In short, the answer to your question is nothing more than reading up on lots of stuff and adapting things to the specifics of the X8 and porting a whole lot of stuff to make it work with the X8 (you know, the vanilla AOSP sources don't come with X8 drivers to support camera and so on).
As B.Jay said You need a looooooooooooooooooot of patience because every time something will go wrong. Also you must know how to analyze logs from terminal. It's really complicated stuff.
eagleeyetom said:
You need a looooooooooooooooooot of patience because every time something will go wrong.
Click to expand...
Click to collapse
LOL...
Yeah, welcome to the fabulous world of open source software where there are always surprises upon invoking "make"
you have to become einstien of android if you want to make a rom!! lol
freshy wanna cook a rom..??
yeah U have learn from modify rom first
and when u aready know what the stuff very well
that is u r ready...
Or you could use ROMMODGEN.com
Sent from my X8 using xda premium
Why do you need 8 Gb of ram?
I was able to compile CM7 with 1,5 GB of RAM on virtual machine. It was compiling for about 4 hours + time to fix errors 8GB of RAM is needed to compile ICS, because it's a beast There's one rule - more RAM, quicker result for magic "make" command
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.