Related
Alright guys, getting a little bored with the stock ROM! What is the best ROM floating out there? Are all the ROM's just easily done with a update.zip file, or do you usually have to use Odin?
Depends on what you're looking for... official Captivate firmwares other than JF6 are all internal test builds ATM. As far as ROMs go there's a decent variety of options to choose from, but they all depend on your personal preference.
However you've come in at sort of a transitional period, we've got lag fix kernels, we've got OC kernels, and we've got kernels that make I9000 ROMS work properly on the Captivate, but all of those things aren't yet merged.
I recommend you keep on reading, check out the different threads, figure out what suits you, and if you don't find what you're looking for- wait a week, I'm sure someone will come up with it
Zilch25 said:
Depends on what you're looking for... official Captivate firmwares other than JF6 are all internal test builds ATM. As far as ROMs go there's a decent variety of options to choose from, but they all depend on your personal preference.
However you've come in at sort of a transitional period, we've got lag fix kernels, we've got OC kernels, and we've got kernels that make I9000 ROMS work properly on the Captivate, but all of those things aren't yet merged.
I recommend you keep on reading, check out the different threads, figure out what suits you, and if you don't find what you're looking for- wait a week, I'm sure someone will come up with it
Click to expand...
Click to collapse
/agree 100%!!
Really appreciate the replies guys!! I'll keep an eye out! What exactly is so special about the I9000 rom's?
Sent From My Captivate
jbcap43 said:
Really appreciate the replies guys!! I'll keep an eye out! What exactly is so special about the I9000 rom's?
Sent From My Captivate
Click to expand...
Click to collapse
the i9000 ROMs are generally cleaner (less bloat, a little more streamlined). they're also more recent for the most part. they have other features that really comes down to user preference though. I enjoyed the i9000 ROM I ran much more than the stock captivate one.
I suggest trying it and comparing it to how you used JF6 and go with whichever feels better to you. Each ROM has it's own bugs. Last time I ran an i9000 ROM was JM5 and it refused to clear message/e-mail alerts unless you manually backed all the way out, can't say if it's fixed yet with later releases.
jbcap43 said:
Really appreciate the replies guys!! I'll keep an eye out! What exactly is so special about the I9000 rom's?
Sent From My Captivate
Click to expand...
Click to collapse
They're a bit more mature development-wise. The I9000 has been on the market longer is and is ATM Samsungs "baby" so they're getting all the newest updates. In addition their firmwares don't include any of the bloat that the Captivate has since international carriers don't care about stupid crap like "AT&T Navigator"- they also don't care if people can sideload.
Don't get me wrong, cross pollinating I9000 ROMS can have their own little annoyances, like flaky haptic feedback and scuh, but the reorient kernel takes care of the really big issues.
One thing you should REALLY look into before you start flashing ANYTHING is whether or not your phone is capable of using button combinations to get into recovery and download mode. Some of the newer handsets arent. A good starting point would be to turn off your phone... let it shut down completely, then hold both volume buttons and power on. If you get into the recovery menu, GREAT.
Next step (Assuming you passed the first), power off your phone, hold both volume buttons, and plug in USB, if you get the android guy with the shovel that means you're good to go, you'll have to yank battery to reset from this point, but this verifies you can achieve download mode, which means game on for careless flashing!
Zilch25 said:
One thing you should REALLY look into before you start flashing ANYTHING is whether or not your phone is capable of using button combinations to get into recovery and download mode. Some of the newer handsets arent. A good starting point would be to turn off your phone... let it shut down completely, then hold both volume buttons and power on. If you get into the recovery menu, GREAT.
Click to expand...
Click to collapse
I've seen mention of people being unable to achieve that. I presumed they were just getting the timing wrong.
So if you fail that, does it mean you are unable to change ROM?
no,it just means that you will have to be more careful, and that you may not be able to fix your phone if anything goes wrong.
my 2 cents
Well for what it is worth. this is my daily driver as of now.
I went into odin and flashed back to stock.
Flashed the i9000 JM8 rom( the Phone CODE file from JM8 and the CSC from JM5)
Then flashed the stock captivate kernal and the .512 pit file
once that is done i flashed Unhelpfuls kernal over to OC
Then i flashed the Tatumia(sp) rom over it.
Ran the OCLF app from the market and changed my scheduler to deadline.
It is by far the best for real world performance and my quadrants are in the 2200-2300 range(like it matters).
Enjoy
P.s. i have flashed i am sure every other combination of roms and kernals and stuff. Voodoo kernal is freaking awesome but i cant get Clockwork to work with it and that is just not okay with me!
I just found the long thread about this topic here. Haven't read through it all yet. Won't bother unless I find I end up with a phone with that problem.
okay, so what's so special about this ROM the cyanogen mod? When will this be available...?
Sent from my SAMSUNG-SGH-I897 using XDA App
jbcap43 said:
okay, so what's so special about this ROM the cyanogen mod? When will this be available...?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nobody knows when it will be available since it is only getting Vibrant support to start. Cyanogen mod is probably the most popular ROM for Android, I don't know much about it though. They have a wiki page and a website for information.
jbcap43 said:
okay, so what's so special about this ROM the cyanogen mod? When will this be available...?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
cyanogenmod is a HUGELY supported ROM based on AOSP (android open source project) with various tweaks to improve usability. as for release, well the only rule about cyanogenmod is that you don't ask for release dates
officially, the Captivate isn't even supported, only the Vibrant is. But as shown, moving things over from Vibrant to Captivate isn't terribly difficult, but still takes time and we'll need someone to maintain it (cyanogen does not release/support devices it doesn't expect to work properly on). support for the vibrant is slated for 6.1 (which will probably be November, it's hard to say)
let me pop in and say there is no "Best Rom" just best for you. We all look for different things in the roms we use so it really is a trial and error. Just make sure to read, read and read some more to make sure you have everything set up right and dont end up with a big brick.
I am closing this.
good luck with your rom search
Hi all Thanks to all.... Newbie here with flashing and all so i just want to get started on the right track... being doing alot of reading just wanted to know what is the safest rom right now for the captivate....
also ive downloaded bay_wolfs AIO captivate tool ...if i use this tool i dont have to go through the the whole process of installing rom manager..zip files etc..do i if i read correctly..well thanks all in advance for the responses.....
It depends on What you want. For a really bare bones rom, use precision. For a close to stock rom, use cognition. For a well themed and polished rom, use serendipity or ultimate. Cognition is the only captivate based one though.
Sent from my GT-I9000 using Tapatalk
yeesh - sorry but most of these get locked in 10 posts or less as these become "My ROM is better than Your ROM" epeen arguments.
With that being said.. if a ROM is posted in the Dev forum and as long as it doesn't say Cyanogen Beta or Gingerbread alpha AOSP in it? It is pretty much safe to flash.
Most of these ROM's use either a Rogers, Captivate, or i9000 Source and don't deviate other than tweaks to apps/kernels/modems/lagfixes/themes.
If you want to be safe - I would go with Cognition as a first ROM flash then go from there. It is basically "stock".
Thanks guys for the quick posts....Just a little worried about doing it for the first time i have read, watched videos, this is why im asking before taking the plunge...
i really like Bay_wolfs tool seems great for newbies has anyone used it...i think i may go with cognition is there a better version than the 3.4 what i mean is the newest version seem best or and older one...
I also flashed my first ROM the other week after lots of reading and studying. I went with Andromeda 1.0 at and have since gone to 1.1. I didn't use the tool that you're wondering about, but have downloaded it for future use. So if you do use it, let me know how it goes for you. I went with the installation instrustions on Andromeda's website, and that worked flawlessly. Once you do decide on a ROM, I'm sure that you'll be extremely happy as the performance is way better than stock. Happy flashing and good luck!
Like the other posters said, it's all about what you want and then personal preference. Once you have flashed a few you will start realizing what you do and don't like about the ROMs and what you really want in them. (My first ROM I had no idea, I was like, lets just flash because it's cool and custom and I feel like it. Then I started noticing the differences between my first ROM and stock, realizing what they can actually do with it and what they cannot. From there I figured out what I was really looking for by going custom, and starting browsing the released ROMs to find it)
In short, your first ROM is just that, the first. It wont stay there long so it doesn't really matter which one you choose. Cognition, like stated above, is a good start because it's pretty close to stock. If you want to just straight into a very custom one and screw the baby steps, try something a little more feature rich. Eventually you will get into trying different ROMs with different kernels and test out over-clocking, etc...
I would recommend for your first that you don't go with an OC ROM though, save that for when you feel more comfortable with your ability to flash and tweak things.
I have never used the tool you are talking about because I feel more comfortable doing all the .zip stuff and seeing what is actually being done to my phone, not trusting something else to do it. The tools I do use are Odin3 and One Click Root/Unroot. If you want to try flashing without that tool but aren't sure of the exact steps or why they are necessary you can PM me and I'll help you out.
Welcome to the addiction of ROM flashing! (It's harder to shake then cigarettes once you start)
You guys are great here thanks for all the tips...tonight i will be flashing my first Rom hope all goes well if i have any questions i will ask...once again thanks...
joeygutz said:
You guys are great here thanks for all the tips...tonight i will be flashing my first Rom hope all goes well if i have any questions i will ask...once again thanks...
Click to expand...
Click to collapse
Was bored, sent you a PM
Jeordy thanks for all info on the Pm ... that was fantastic i sent you a pm let me know what you think.....
I've tried several. So far, out of all of them, I like Andromeda 1.2 with the Speedmod kernel. It seems to be the most functional.
best rom in March
Hi everyone,
I flashed the Cognition ROM on captivate in Jan. I do not know at this moment which one is the best since gingerbread is also here now. Can someone please help.
ask_j said:
Hi everyone,
I flashed the Cognition ROM on captivate in Jan. I do not know at this moment which one is the best since gingerbread is also here now. Can someone please help.
Click to expand...
Click to collapse
Do not flash any of the Gingerbread ROMs unless you really know what you are doing. They are still unstable and you risk bricking your phone. As for stable ROMs, there's a wide variety of them, and they're all based on Android 2.2, which is really fast. There is no best ROM, and it all depends on your personal preferences. Try visiting a few of the ROM threads to check them out, and hopefully that will help you decide which one to flash.
psai said:
Do not flash any of the Gingerbread ROMs unless you really know what you are doing. They are still unstable and you risk bricking your phone. As for stable ROMs, there's a wide variety of them, and they're all based on Android 2.2, which is really fast. There is no best ROM, and it all depends on your personal preferences. Try visiting a few of the ROM threads to check them out, and hopefully that will help you decide which one to flash.
Click to expand...
Click to collapse
A bit of an overstatement, but I concur on there is no best, find what works best for you
CM7
Ok well not 10 or less this time but close.
There is no best rom just best for you. I could say Rom X is the best and does everything I need it to and when you run it, you dont like it or doesnt work well with your set up.
Thread Closed
Can any1 make a cm7 img to boot from sd.....my wife has a nook so I really root just yet but I love the fact that I can boot nookie. And honeycomb from sd so can any1 plz make a cm7 img
kitila said:
Can any1 make a cm7 img to boot from sd.....my wife has a nook so I really root just yet but I love the fact that I can boot nookie. And honeycomb from sd so can any1 plz make a cm7 img
Click to expand...
Click to collapse
I'll second that. I also really like the fact I can boot into HC or NF without flashing my stock Nook.
On a side note I would think once CM7 gets to a more stable version that someone would probably do this.
or is there a way to make a bootablr img form a rom
I'm with Snyperx on his sidenote.
I'm betting someone will when the flurry of development has slowed down a bit.
I did read where one of the devs (can't remember who or where...I read too many threads here daily!!) said that if you had the correct partitions on the sd card and you pointed to them correctly you could make a bootable SD card just like we have seen from cicada before.
Give it some time and I'm sure it will pop up.
I'm looking forward to it also.
Ill add one more vote for a bootable card.. it would be great, especially since we just have nightly stuff right now...
Divine_Madcat said:
Ill add one more vote for a bootable card.. it would be great, especially since we just have nightly stuff right now...
Click to expand...
Click to collapse
Yeah, it would be a great treat, and also a step to multiply this army of CM7-For-NC of beta testers (or lab rats, as some prefer to call them... sure, who exactly listens to a lab rat when that rat whines about every next nightly is wonkier than the previous one?).
Whoever would be assembling an image for CM7 SD boot, I would also suggest to add latest Gapps/Market and possibly full Flash 10.1 (10.2 when available for Xoom), YouTubeTablet.apk, and dozen other apks from Xoom Honeycomb dump.
However, even if everyone was warned that no bugreports for nightlies are accepted, or desirable, I still wish to see a 2.6.32....37-based branches of CM7 nightlies to play with. Even silently, with no bug reports and such, like a lab rat, lol. It's not just me: I probably missed that notion of TI engineers being lazy idiots switching to 2.26.32 kernels even for their shot on FroYo. OMAP4 repos see 2.26.37 kernel these days for AOSP 2.3.2.
Apart from kernel maturity issues, I would love to see progress in engaging all sorts of NC hardwares: SGX full UI acceleration/font rendering/zooming, SGX/DSP HW decoding AND HW rendering (HW overlay) for video, full BT 1.2 functionality, FM radio, USB "hub" hack (to add (Web) cam, keyboard, hacked Kinect, whatnot)
CM Group may stay clean from commercial products, but I would love to see some less picky coders borrowing stuff from AOSP 3.0, Xoom, Nexus S, and whatnot and backporting it to NC CM7. By "stuff" I mean stuffy stuff, and not some fancy wallpapers.
While this thread is probably in the wrong forum, I have been asking for this same thing in other related threads. Squeaky wheel gets the grease?
Theres instructions in the dev thread (direct link here http://forum.xda-developers.com/showpost.php?p=11472094&postcount=3 )
They're untested instructions. The author assumes they'll work but admits not knowing for sure. Regardless, I might have to figure out how to follow those instructions then. Might be the only way to get what I want. Everyone can do the same too.
epakrat75 said:
They're untested instructions. The author assumes they'll work but admits not knowing for sure. Regardless, I might have to figure out how to follow those instructions then. Might be the only way to get what I want. Everyone can do the same too.
Click to expand...
Click to collapse
lol. let the devs work on the important stuff. now you have a chance to contribute to the community
lafester said:
now you have a chance to contribute to the community
Click to expand...
Click to collapse
Another chance. Indeed.
the main issue is currently they are at the nigtlies stage, so someone would need to manually create the img files every day, which is a bit of a pain for the small changes that are being made.
I can try to create one early next week when a few more commits have been written but I wont be able to make a new one every day.
I would like this as well but it seems that most people are content with flashing the Nook.
I might break down finally and just flash my nook but I need instructions on how to back up/recover my nook just in case something goes wrong or I want to return my nook to the store if I'm dissatisfied.
Can anyone point me in the right direction.
ill give a shot at making a bootable sd for the newest nightly tonight
Sentack said:
I would like this as well but it seems that most people are content with flashing the Nook.
I might break down finally and just flash my nook but I need instructions on how to back up/recover my nook just in case something goes wrong or I want to return my nook to the store if I'm dissatisfied.
Can anyone point me in the right direction.
Click to expand...
Click to collapse
restore to stock thread:
http://forum.xda-developers.com/showthread.php?t=914690
I bet you can take the froyo sd card image, replace the uramdisk with this one, replace the system contents with the CM version and maybe be good to go. At the very least, this ramdisk is built from the dev instructions relating to making a CM7 bootable sd.
You will probably need to convert the partition where system lives to ext4.
http://dl.dropbox.com/u/20399857/uRamdisk.7z
mckooter said:
ill give a shot at making a bootable sd for the newest nightly tonight
restore to stock thread:
http://forum.xda-developers.com/showthread.php?t=914690
Click to expand...
Click to collapse
Any success on that bootable SD image?
Hi guys!
Since two days I'm trying to create a ROM based on HTC Sense, porting from HTC Desire to our Nexus One using, as a base, the RCADSmixHD ROM.
I've been able to complete the entire package .zip and installing succesfully, BUT at reboot I'm stuck at the Nexus logo...
Do you think it's a kernel-related issue?
I really don't have any other ideas...
EDIT: I'd also like to know how to develop/modify a kernel for our Nexus One, but based on HTC roms... Someone has guides/links?
Try to Flash this Kernel: 2.6.35.6-eViL--10-7--1-wmcfg by eViL D:
You can find dl link here : http://forum.xda-developers.com/showpost.php?p=16995049&postcount=2
I had problems with the kernel include in RCADS on my N1
Thanks but no changes here... BTW the kernel included in RCADS rom works with my Nexus.. But here in this new ROM that I'm trying to develop I don't know what's wrong...
My guess there's something wrong with the ROM itself you probably have a few lines of code somewhere that are not working right. Were you able to compile the code on your computer?
Well, actually I'm trying to port a Sense ROM from HTC Desire with 250mb fit into /system/... I think that's the problem because my Nexus One could have bad blocks and/or less space into /system/, so this ROM wouldn't fit. I think so.
Regarding the code, I haven't written any kind of code, apart from looking at updater-script to be ok... Other suggestions? Thanks anyway, much appreciated
Now I'm trying to port a different ROM, the Desire S Gingerbread 2.3.5 with Sense 3.0!
But after replacing many folders and files from a Sense Rom of the Nexus One and the target Sense Rom that I'm developing, I have replaced boot.img and edited the updater-script properly (I think).
After installation, it's stuck at the Nexus logo... always!
What's wrong????????
Look at your logcat.
And at your /proc/kmsg.
If you don't know what these 2 mean - read up on those, use some googling.
If you can't - I believe you won't be able to develop anything worthy, or anything at all.
Moreover, Nexus has 145MB on /system partition. You need to utilize SD-EXT partition and symlink parts of the ROM to make it fit.
If I'm speaking Chinese and you can't figure it out - read the previous paragraph
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
rugmankc said:
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
Click to expand...
Click to collapse
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Iperzampem0 said:
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Click to expand...
Click to collapse
What did you add to the updater-script? And which folders specifically did you replace and change? And did you use a rooted ROM or the OTA one for the desire?
@Ace42:
Hi, I had used a rooted ROM from the Desire thread and I have followed this pretty useful guide which illustrates how to port Sense Roms:
http://forum.xda-developers.com/showthread.php?t=1222746
I have also had a look at almost all the files into each folders to see if there was differences in the code between the 2 roms..!
BTW the problem is in the updater-script...
For example I'm not able to mount "sd-ext", which is one of the most important steps to do for the Rom to being able to run into the device.
Look at that link properly, porting sense to OTHER SENSE DEVICES.
N1 isn't a sense device.
First, porting is more than replacing your boot.img and changing your update-script.
Like the other user said, you need to symlink files to your SD card cause N1 just isn't big enough.
Second, you're taking roms from other devices, most probably you'd have to re-write or mod the drivers.
Third, Porting just isn't that easy.
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Iperzampem0 said:
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Click to expand...
Click to collapse
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
illuminarias said:
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Iperzampem0 said:
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Click to expand...
Click to collapse
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
@Deep-Knight:
Yep, I was working yesterday evening with the official Desire gingerbread update from HTC, but, as always, I'm stuck at the Nexus logo, after the installation is done... :/
I think I'm doing something wrong with system partition.. I know that our N1 can handle only 150mb for /system...
But I must admit that I'm using almost the same updater-script and boot.img as the N1Sensation v0.5 rom or RCADSmixHD rom..
Deep-Knight said:
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
Click to expand...
Click to collapse
Just make a thread and upload your beta version, theres a plenty of people here able to test and help.
Thank you Menelkir for your interest!
But first I'll have to create something useful.. Maybe later on I'll create a new thread..
Till now I'm using some HTC Desire's ROM from the dedicated section here at XDA.
Stay tuned guys
As always graphical glithces will not be solved, until HTC releases Desire's Source Code..
The code is released already.
Unfortunately, the real trouble with porting ROMs is fixing the things that don't work - which will include trackball, hotspot etc - and this is the part where most of ROMs fail, because very few developers are skilled enough for that.
Based heavily on TeamICS' work on HeroC, here is some very early initial work on ICS for the HTC Kovsky, AKA Sony Xperia X1. Built from AOSP source, with source available.
This is NOT for the faint of heart, and as far as I know nearly everything is broken right now. Instructions for building are coming soon - meanwhile, source is available at https://github.com/Zorlin with bits from https://github.com/CyanogenMod and https://github.com/TeamICS
Credits:
- TeamICS for all their ridiculously awesome work on Hero/HeroC
- CyanogenMod team, on which some TeamICS work is based.
- IceDroidV2 for the installer and current (slightly modded) kernel/boot.img - see IceDroidV2 thread for appropriate credits and source.
Currently working:
- Boots!
Currently not working:
- Everything else
- ADB
Notes:
boot.img is made from applying the ICS porting guide to IceDroidV2's boot.img
Currently there's a "hack" to attempt to get adb working - I threw in a copy of busybox as /system/bin/sh. Need to work out a better way, since it really didn't work...
I've got a bunch of ideas, but it's late, so... here:
DOWNLOAD:
testbuild0 - "The Magic ZIP File"
I can't believe it. OMG !!
BUT
Is it really ICS or just some skin for android 2.3 ?
X1 long live
Garena said:
I can't believe it. OMG !!
BUT
Is it really ICS or just some skin for android 2.3 ?
Click to expand...
Click to collapse
It's really ICS, which is why so little works. Gingerbread kernel for now, though.
woooaaaahhhh.....i love u full to all developers x1 the brilliant smart man ....kovsky never die !!!!
Do you really think you have enough background knowledge to get this off the ground? Or is it more of a "lets see what I can do" thing?
wallaceff said:
Do you really think you have enough background knowledge to get this off the ground? Or is it more of a "lets see what I can do" thing?
Click to expand...
Click to collapse
Yes and no. I think I can bring it to the same state as HeroC, maybe sans camera, and port hardware acceleration if/when they get it working. Kernel isn't my forte, though. At the moment adb is a major and confusing stumbling block... I'm missing something stupidly simple.
can we install it or it's not ready yet
I installed it that we install IceDroid v2 but nothing happened
It was stuck in android boot
mahmoodifar said:
can we install it or it's not ready yet
I installed it that we install IceDroid v2 but nothing happened
It was stuck in android boot
Click to expand...
Click to collapse
You install IceDroid V2 first and then overwrite it... but no, at the moment this is just for developers and tinkerers.
oh damn how nice would that be!!!!
go ahead zorlin an thx a lot for your work
Hi Zorlin how is going ur work ?
Slow... lots of real-life stuff going on. I'll probably publish build instructions on the weekend so others can start contributing.
Haven't forgotten you guys though.
Hello. Any progress or updates of Your work?
Oh my god..
I hope this really happen....
I will do wait your work!
revol5 said:
I hope this really happen....
I will do wait your work!
Click to expand...
Click to collapse
I will try to make something based on @Zorlin sources from #1 post. At all, probably He have own things to do so that is why He not respond.
fergy said:
I will try to make something based on @Zorlin sources from #1 post. At all, probably He have own things to do so that is why He not respond.
Click to expand...
Click to collapse
Your signature shows that you have a own kernel for NAND for X1?
What is working etc? maybe you could share it, when it has benefits to the current published ones
EDIT: maybe you could join zargloub and midnight for kernel dev?
neoofoox said:
Your signature shows that you have a own kernel for NAND for X1?
What is working etc? maybe you could share it, when it has benefits to the current published ones
EDIT: maybe you could join zargloub and midnight for kernel dev?
Click to expand...
Click to collapse
Hello @neoofoox.
Working everything except camera, fm radio and bluetooth (atm working on kernel to see where is problem).
Charging/discharging (at last I think it is ok as phone discharge within 20 hours->3.5 yrs old battery<- using push, wifi, bluetooth and location with 10-15 minutes of talking)
Also, phone wake asap You press power, ok or lock button (also with double security using pattern after normal unlocking)
I also don't think that this is right thread for something other than ICS work conversation.
When I got all things working proper, be sure that will make an new thread with image and patches to kernel.
BR,
Ramon
EDIT: Yeah, I will be happy to talk with @zargloub and @midnight regarding kernel.
EDIT2: Regarding sharing, I use only main system of Cyanogen but My own kernel, so as I say, until kernel completely work, I will not share it because of lot's of questions what users cannot fix until I fix holes inside kernel.
@fergy Last question ot jooc Does your phone reboots if you miss a call?
Sorry guys, I might be retiring my Kovsky... I'll publish build instructions and sources etc either way. If you don't hear back from me, assume I retired it
I'm getting fairly hopeful that you'll get decent ICS on the Kovsky soon though.
EDIT: Yup, it's official. I turned in my Xperia X1 in exchange for a free, off-contract Samsung Focus S (which I'm reselling) through the recent Microsoft promotion. I'll still have it for a week - I'm going to try and get ICS on it before then, but I don't really know what chances are like.
After that, I'll turn this over to someone else who can hopefully carry it through.
fergy said:
Hello @neoofoox.
Working everything except camera, fm radio and bluetooth (atm working on kernel to see where is problem).
Charging/discharging (at last I think it is ok as phone discharge within 20 hours->3.5 yrs old battery<- using push, wifi, bluetooth and location with 10-15 minutes of talking)
Also, phone wake asap You press power, ok or lock button (also with double security using pattern after normal unlocking)
I also don't think that this is right thread for something other than ICS work conversation.
When I got all things working proper, be sure that will make an new thread with image and patches to kernel.
BR,
Ramon
EDIT: Yeah, I will be happy to talk with @zargloub and @midnight regarding kernel.
EDIT2: Regarding sharing, I use only main system of Cyanogen but My own kernel, so as I say, until kernel completely work, I will not share it because of lot's of questions what users cannot fix until I fix holes inside kernel.
Click to expand...
Click to collapse
With these things working it is working perfectly, who need wifi if you can use mobile Data to access Internet and who needs bluetooth if you can send files via Email or connect your Phone via headphone port to your soundsystem etc..
I would test that if it becaume available and will report every bug etc. You could choose some people for testing which know something about that / for reporting bugs. So you can fix them and make the kernel 'perfect'.
Zargloub stopped developing and he has his files on gitorious so you could merge the kernels, here is working bluetooth and wifi (but it shows bad signal strenge)
Are you on github or gitorious so other devs can see what you are doing and maybe can help or people see what you are working on now.
I would love to test it, because for me it is allready perfect I hope we read something from you soon. You are our last hope
EDIT: sp3dev was also working on kernel you can get the sources here and here
EDIT2: I asked sp3dev if he would help, but he cannot for 2 reasons, first he has currently no time, the second reason is that he don't want to work on project which are close-source. Maybe you should think about releasing that before it is completely finished or make it open-source. Your device is old and that slow down the process a lot.