Database Develop

Cyanogen Mod Offically Supports the IS! - No Download yet, still in beta

UPDATE: 2 Cyanogen developers have picked up the Incredible S and it is being officially supported!! The ROM is in Beta and will be released when ready.
Remeber, the first rule of cyanogen: Don't ask for deadlines!!​
Click to expand...
Click to collapse
Previous version of this post, kept for historical reasons:
Code:
I am sure everyone here wants to see CM7 hit this device. I am also sure that in our collective efforts, we can do it. At the moment, it is just me (or no one else is saying they are trying ;)) I basically want to try and get a team of people to crack the porting problem, because so far I am unable to do it on my own.
Finding information is proving difficult, and I just keep hitting dead ends. Is anyone willing to help? Has anyone ported a ROM from one device to another before? Can anyone point me towards information on how to start / debug?
As a community, this will get done a lot quicker, so if anyone can help please post here. If you idea of helping is posting "[I]I can help, what can I do / tell me what to do /give me something to do[/I]" then thanks, but no thanks.
[SIZE=3][B]Please keep this thread clear of chatter so it can be used for discussing the problem at hand.[/B][/SIZE]

I have ported from the HTC Dream to the HTC Diamond ...
If you wish to get started the way i do it ... Take a cm build from the closest device ... Say the DHD ... And chuck the system.img into an official update zip or any other zip with a working boot.img etc ... Then try booting directly ... If it bootloops ... The first thing you should try is to replace /lib from a stock rom ...
This will get you to boot surely ... But if you manage to boot directly then keep the libs ... After that we need the appropriate libs extra things like the secondary cam that u can take from the stock rom ...
A more detailed way to do it would be to get the ported libs working by using logcat to see whats wrong and replace only the related libs from a stock rom ... Keeping stock libs will make performace related things such as battery in the same state as stock ... So it is best to keep the ported libs ...
I would have done this myself by now but i have a s-on devoce :-/
Anyway can you tell me whats wrong with your attempts? Where do you get stuck? Which device are u trying to port from?
EDIT: idon see why you hit dead ends if u port from a similar device it should be no problem to boot ... Heck ports from the dream to the bloody winmo diamond worked out of the box ... The dream libs worked fine ... Would be nice if u could chuck us a logcat ... Even if i cant figure it out ill ask neopeek ...hes a pro but idon think this will go that far
Sent from my HTC Incredible S using XDA App

I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25
I will try what you said, it's a good starting point, thanks!
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...

Hehe ... Good point ... U cant get a bootloop if u dont even start boot ... I admit ... U sure have a funky way of trying things out ...
EDIT: that logcat ... Did u get it with what i said or what u tried?
Sent from my HTC Incredible S using XDA App

Both gave me that result. Can't really find out what it means other than it couldn't mount the system partition, no idea why
Sent from my HTC Incredible S using Tapatalk

I think the problem comes earlier ... Look at what you have said ... That failed to format part ... I think it screwed up halfway and now its empty ... Have you compared the update script with the one from the dhd? You are porting from the dhd right? Its the best option ...
Sent from my HTC Incredible S using XDA App

I use the same script I use for lpremix so I know the script is fine. Which is why I am stuck.
Sent from my HTC Incredible S using Tapatalk

Hmmm ... We need to narrow this down ... Try copiying in only /app /framework /media ... And also try using the older setup with the stock build.prop ... If u can boot this then the problem is in the rest ...
EDIT: did u also try different update scripts? Try using the dhd one as it is ... I think the problem is there might be a difference in the way the IS is partitioned compared to the dhd ... Cuz idon think we really have a mmc's upto 25
Sent from my HTC Incredible S using XDA App

Have you tried converting the Ace updater script to update script then changing the mount partitions to say from:
Code:
format("ext3", "EMMC", "/dev/block/mmcblk0p25");
format("ext3", "EMMC", "/dev/block/mmcblk0p27");
format("ext3", "EMMC", "/dev/block/mmcblk0p22");
to
Code:
format SYSTEM:
format CACHE:
format BOOT:
Then convert back?

K bro i think ive got some thing ... In /system/etc there is a file called vold.fstab ... Please do a comparison ... There might be a difference there ... Check the cm one with stock ... Also compare the cm7 update script from ace and the update script from a lp remix ... Maybe you just need to change the partition name ... Also try removing those lines completely from the script you are using ... Chuck all the lines related to format...
EDIT: its getting a little late ... Its around 330 am now ... I think ill go to sleep ... Ill see if i can think up of anything else for u bro ... Gnite every1 -_-
Sent from my HTC Incredible S using XDA App

looks like u have the same prob as me bro

l0st.prophet said:
I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25...
Click to expand...
Click to collapse
As far as i know Desire HD is ext3 and IS/DS are ext4.
Try to change the partition information.
See my previous post.
l0st.prophet said:
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...
Click to expand...
Click to collapse
Also here in your script you have a reference to /system/bin/sh which is probably missing from your rom.

hmm didnt even read that, but yes it shud be 4 o.0 or is that why my script is fkin me up?
imma test 3 anyway...

Im back from bed ... Maybe marylandcookie is right ... But where can that problem be? He is using the lpremix update script that usually works not the dhd script ... So why is it trying to chuck up ext3? Are u sure we are ext4?
@marylandcookie: do you have a nickname ... Ur name is real handfull to type out -_-
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Sent from my HTC Incredible S using XDA App

Ext3 works fine, but I will try ext4 anyway. It's us more likely to be a problem in the system files so I will check void.fstab file
The sh file is there, the system partition just isn't mounts properly
Sent from my HTC Incredible S using Tapatalk

it's too diffcult for me...but i believe we can

knightrocker said:
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Click to expand...
Click to collapse
I'm not sure what you mean, I suggest you look at the partition table. It's differant from mtd blocks cause its nand, system is definately mmcblk025
Sent from my HTC Incredible S using Tapatalk

Really? Still not used to this whole nand partition thing
Much better with android itself have made any progress?
Sent from my HTC Incredible S using XDA App

I won't today or until Tuesday as I am on holiday and away from a pc, but I will get back to it next week
Sent from my HTC Incredible S using Tapatalk

Ok then ... Ill see if i can think of something by then ...
Sent from my HTC Incredible S using XDA App

Kernel compilation for Samsung Galaxy S I9000

Hi all,
we are trying to build our own kernel for a Samsung Galaxy S (I9000XWJVB).
What we did so far:
- Download the correct sources from "opensource.samsung.com"
- Studied the README
- Installed cross-compiler toolchain
- Created ".config" as described in README
- Kernel compiled
Compilation worked fine -> zImage was available (but with only 2mb very)
OK, looks like initramfs is missing.
The first question is now, where to get / how to create a correct initramfs?
We copied the initramfs from Leshak and we extracted an ".cpio" from a working zImage.
Then we tried to use them in the ".config" (CONFIG_INITRAMFS_SOURCE) for kernel compilation.
Resultant zImage was larger (around 6mb) so it looks like something changed.
But once we installed the tared zImage on the phone (using Odin), the phone freezes during reboot.
Any advice how to progress here?
Is it possible to use Leshaks initramfs for all Galaxy S phones? Or is this only for a specific version? The CONFIG_INITRAMFS_SOURCE should point to the "initrd.arm.initramfs_list", correct? And not to the initramfs-folder?
And: Is there a way to get any type of kernel boot debugging message from the booting phone back to the PC (or the phone screen)?
Many thanks in advance!

I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Sent from my GT-I9000 using XDA Premium App

Just saw 2nd question. I think that it should point to intiramfs folder. You can zip all kernel files and upload it so i can take a look at them
Sent from my GT-I9000 using XDA Premium App

Hi,
themate1987 said:
I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Click to expand...
Click to collapse
we tried four different initramfs now, but ended up always with a freezing phone.
I would like to ask the kernel experts directly, but I'm new to this forum and not allowed to post in the developers forums. I hope that one of the gurus will reply to this thread.
themate1987 said:
Just saw 2nd question. I think that it should point to intiramfs folder.
Click to expand...
Click to collapse
My understanding is that the .list file will describe the structure of the initramfs folder and if this file is present, it should by used in the .config. Otherwise the .config should point to the folder.
Please correct me if I'm wrong.
But anyway, we tried both versions, none worked.
Regards!

PM some kernel developers
Sent from my GT-I9000 using XDA Premium App

Use speedmod kernel patches with the readme file he has given..
or else you can go through supercurio threads also ...
they explained the kernel compilation methods....
thanks

Did you get this to work finally? I too am trying to compile and flash a custom kernel ( For SGS4G) I point my INIIRAMFS_SOURCE to an extracted initram dir, but the resulting boot zImage does not proceed past the initial boot screen(s) Please let me know if you succeeded, and if yes, how.
Thanks!

What I got the problem was about initramfs.cpio.
At that moment , the most important point you know is you should make the file in Linux..
When my friend made me a file is initramfs.cpio , it worked well.
But what I made in window made always troubles for compile.
So if you made a initramfs.cpio with hexeditor in window, try it in Linux again..
Thx!

Help for custom boot loader for Cyanogenmod 7.1

I have installed Cyanogenmod 7.1 and modified my bootanimation. I would like to also modify my bootloader screen, the first screen that appears just after the phone boots. Please help on t this topic! Thanx in advance!

Well that's not as easy as changing the bootanimation.... Cause i think you need to build your own kernel.

Thanx! Could you please make or modify a kernel for the cyanogenmod 7.1 that I'm using. I'm pretty new to this android development, all I know is how to root, change bootanimation, and other basic things. Thanx in advance!

Ya kernel...read it can be changed in the param.lfs without having to build a kernel. Not sure how true this is in the case of mini.

What do I have to read and edit? And where can I find this param.lfs? Thanx in advance dude!

I replies on your other thread in Galaxy Mini General. Try modifying TASS.rle in root folder. I don't know if you need to unpack-then-repack your boot.img though.
Edit :
Since this "TASS.rle" doesn't exist in CM7 update zip file, then it means you do have to unpack your boot.img, open the ramdisk folder then edit the extracted TASS.rle" using image editor or something. I never modified TASS.rle so I don't know exactly how to do it.
If you're using Windows, you can use dsixda kitchen+custom cygwin package+Java Dev Kit to do the unpack+repack. It's somewhere in xda.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

Thanx a lot dude! But are you sure it'll work? I'll try it out, but is there any simpler method than this. Some way that I can modify it using my phone itself? By the way are you using cyanogenmod 7.2 RC 3 by squadzone? How is it? Please give the link too... thanx in advance!

Like I said, I never modified TASS.rle so I have no clue if it will work or not. I did unpacked and repacked boot.img several times using dsixda kitchen and they worked.
I don't know if easier method exist, so I only suggest what I know from browsing.
It looks like in order to do what you want, several steps are needed :
1. Unpacking your boot.img into zImage file (kernel) and ramdisk folder.
Anything inside ramdisk.folder will be flashed into your system partition each time you boot your device. Examples are init.rc, default.prop and TASS.rle. You can do whatever you want with these files, say modifiying their contents, but the changes only persist as long as you do not boot your phone, which will restore them back to initial state as I explained above.
2. Converting TASS.rle found inside ramdisk folder into editable format such as PNG
3. Modifying the converted PNG in point 2 (using Photoshop or other app)
4. Re-converting the modified PNG from point 3 back into RLE format
5. Re-packing (compiling) zImage file and ramdisk folder (having modified TASS.rle from point 4) back into boot.img
6. Flashing boot.img from point 5 into your phone.
To make it short, you need to learn how to :
1. Unpack and repack boot.img, which you can do using dsixda kitchen from here : http://forum.xda-developers.com/showthread.php?t=633246
2. Converting RLE to PNG and vice versa. More info here : http://forum.xda-developers.com/showthread.php?p=20128066
3. Flashing boot.img into phone. You can compress your boot.img into TAR (type this in cygwin shell window "tar -cf boot.img.tar boot.img" and flash it using ODIN with one package option or you can create a flashable zip file.
CM 7.2 RC3 works great for me, better than RC2; but that's my personal judgement and there's a chance you will not agree with me after you try it.
Head over to CM 7.2-RC3 by squazone for download link.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.

roofrider said:
@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.
Click to expand...
Click to collapse
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

distan7 said:
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Thanks.
I have Ubuntu on a vm

And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

distan7 said:
And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Ya...but I didn't try cpio to extract ramdisk..simply clicking it mounted the ramdisk and it's contents were visible...I wonder if I make any change and unmount it will be saved or not?! Then no need to gzip and cpio

Thanx guys! roofrider and distan7 for all your help and support! If I had a bank account, I would have donated by now, but since I don't all I can do is click the thanks button! Thanx a lot dudes!

You're welcome mate
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

I've attached the tass.rle converted to tass.png thanks to ketut.
but this is only one of the 2 images that appear while booting.
I have to dump the stl6 to find the other i think...but dumping stl5 bricks the phone (stepph) so a little nervous...but i might give it a try.
edit: no harm done.
but stl6 had nothing....anyone got any ideas?
the .jpg or whatever is hidden somewhere, at least that is how it is for galaxy s variants.

[DEV] - Porting HTC Sense 4.0 - [HTC Primo ROM]

oooh, Finally I can post here
Since the HTC Primo has similar hardware I thought that is not impossible to port its ROM to our lovely SE Xperia Arc.
So, I got the Leaked RUU (thanks for Football) and started working.
Actually, I couldn't touch the Sense but I realized that is possible.
I'm telling you what I did.
First, The BOOT.IMG:
I modified it to be compatible with our Arc. I had some problems with it one of them was the size, after I finished editing i found its size was only 3.7Mb and that is less than the correct size which needed by the bootloader but after adding filler file (thanks for DooMLorD) that wasn't a problem no more.
I also added a fully working CWM Recovery .
And end with 5.7Mb Boot.img.
Second, The ROM.ZIP:
After I replaced some files which allow the hardware and keys to work I had the same problem with the size, the system folder is about 500Mb and our device's ROM is only 350Mb !!! I believed that I can remove some files but once i got another idea i realized that wasn't the best solution so i moved the app folder from system to data folder I didn't give it a try before but i guess it will work.
Finally I wrote updater-script and that was difficult but always there is Google.
OK, now I'm facing problems with the file-system .
I've tried YAFFS2 after editing init files and finished with bootloop.
So I think this ROM needs EXT4 /system, /data and /cache .I'm about to format them with EXT4 but I'm a little afraid
So what you think guys ...?

---[Reserved]---

I'm no help here but I hope other more experienced people on this forum give the help you need, and best of luck on this project
Sent from my Arc to your eyes.

amazing! I wish i could help but instead of trying ics first i guess it is better to try older sense 2.1/3.0
http://forum.xda-developers.com/showthread.php?t=1465628 an example universal mtd/yaffs rom

Its ICS Time !
and for the link i'll try but not now.

did you format the /system /data and /cache partition???

nickholtus said:
did you format the /system /data and /cache partition???
Click to expand...
Click to collapse
no, i didn't
and i'll not till i make sure that we can use emmc ROM on Arc

ok
10 chars

There is a thread in Play Development. You might check with Blagus
http://forum.xda-developers.com/showthread.php?t=1174309

i am working on porting sense to the xperia play.
i already asked blagus, he can't help because his play is stolen

have any one tried to format /system to EXT4 ...?

It wont work because of the way SE devices work
Our partitions aren't the same ass DHD/Devices similar. They've method is completely different to ours, was an effort on x10 but died down due to the fact the devices/bootloader are different
Regards
Sent from my LT15i using xda premium

It is defiantly possible since Jason stein ported Dhd Roms to the arc
Sent from my LT15i using XDA

zainthesnipe said:
It is defiantly possible since Jason stein ported Dhd Roms to the arc
Sent from my LT15i using XDA
Click to expand...
Click to collapse
Wait... What? Where can I find it?

Jason Stein ported MIUI roms based on AOSP not HTC sense roms
Sent from my LT18i using Tapatalk

dinesh690 said:
Jason Stein ported MIUI roms based on AOSP not HTC sense roms
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
Just as I thought, too good to be true.

we need to modify the nand partition tables
i'm not interested in this and it's seems impossible for me
another solution is dual-boot i don't now if someone working on this or not.
any help ...

what about porting the launcher and apps over the stock rom or AOSP..... this will make it much stable ...

^
^
^
that will not work

Sad-Clown said:
^
^
^
that will not work
Click to expand...
Click to collapse
Here is an idea:
Using SD card space might help..you can create partitions in sdcard and make a script that boots the os from SD card...is that possible??

CM10 partition layout

Hi all!
Is there any ways of changing back the /system and /data partition to it's old place?
400Mb it kinda small.

No your stuck I'm afraid. Have a look at the Helly Bean rom which will use a different partition layout. That will have more space for apps.

Just move apps to sd card in settings.

beatimgame said:
Hi all!
Is there any ways of changing back the /system and /data partition to it's old place?
400Mb it kinda small.
Click to expand...
Click to collapse
you can mover few apps to system partition, this will give you more space.

^And lag.
Sent from my GT-I9000 using xda premium

Can't add all my apps to SD, because the OS would die of the lag.
It would be good to create a data forder in /system and link it to /data (it may be stupid).

beatimgame said:
Can't add all my apps to SD, because the OS would die of the lag.
It would be good to create a data forder in /system and link it to /data (it may be stupid).
Click to expand...
Click to collapse
App data is stored on /data when you move to sd natively. The rest of the game has to be read, so no lag at all. data stays on fast chip.

AlwaysDroid said:
App data is stored on /data when you move to sd natively. The rest of the game has to be read, so no lag at all. data stays on fast chip.
Click to expand...
Click to collapse
But the data that stored on my lil bit slow class6 sdcard makes the system slow.
By the way I can't see that speed up after the partition change. I hope pawitp will change it back.

beatimgame said:
Hi all!
Is there any ways of changing back the /system and /data partition to it's old place?
400Mb it kinda small.
Click to expand...
Click to collapse
You can do it yourself quite easily by compiling CM10 from source. All you need to do is revert the kernel and os changes that were made by Pawitp. After that you can build your own nightlies. Take a look at the guide to compiling CM10 from source thread. Also, here are the commits you'll need to revert:
https://github.com/CyanogenMod/android_kernel_samsung_aries/commit/0c3f5d384b092e6d9874faed0c1122c95e6ca32b
https://github.com/CyanogenMod/android_device_samsung_aries-common/commit/8778488c4920d2245164a8c99f89e85f664e6a50
As you can see from my signature, I've already done this myself.

fishears said:
You can do it yourself quite easily by compiling CM10 from source. All you need to do is revert the kernel and os changes that were made by Pawitp. After that you can build your own nightlies. Take a look at the guide to compiling CM10 from source thread. Also, here are the commits you'll need to revert:
https://github.com/CyanogenMod/android_kernel_samsung_aries/commit/0c3f5d384b092e6d9874faed0c1122c95e6ca32b
https://github.com/CyanogenMod/android_device_samsung_aries-common/commit/8778488c4920d2245164a8c99f89e85f664e6a50
As you can see from my signature, I've already done this myself.
Click to expand...
Click to collapse
But if I would build my own nightly I couldn't use Devil kernel.

beatimgame said:
But if I would build my own nightly I couldn't use Devil kernel.
Click to expand...
Click to collapse
You can if DerTeufel is open source Semaphore can be used. Stratosk is open also Kasper (Mackay kernel)
You have many options. The choice is yours.
Sent from my GT-I9000 using Tapatalk 2

As we stand right now, with all the kernels/ROMs flying around... what would be a choice that would give us more space for apps? I only got 366 MB now on CM10 and in the last year the app sizes has grown (generally speaking). After installing all Gapps, some mandatory day-to-day apps and a GPS app I am kinda out of space for any other apps. That's sad... 4 years ago when I bought the phone I had ~100 apps installed (of course, the phone worked like c**p but the space was there).