yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] wintel_mac:
What would be your method to get used to this technology? Try & Error seems to be a start. What I miss about Android is a good documentation since every device is different. It's quite hard to learn things only by reading forums or even code snippets. And not having a good sub forum for non dev related stuff makes it not easier. A thread created here yesterday evening was moved to Q&A and now resides on page 3. Not very likely that users will click trough 3 pages with most things being for a different device. Sorry for being off thread again but the situation here makes me both angry and helpless. :(:(:(
[Galaxy S Plus I9001 Android Development] rayiskon:
that's exactly what i meant. my post was mainly referring to ur statement that u will try to combine ur kernel (which works just fine with stock roms) with CM. i find it hard to believe that there can be a single kernel that would work on both stock and AOSP roms at the same time because of the hundreds of modifications from the manufacturer just as u mentioned. ur current kernel could be a starting point, but by the end the AOSP kernel will be totally different from ur stock one, and won't work on stock roms. also some drivers will have to be modified for the corresponding hardware to work etc... at least that was the case with the htc desire.
[Galaxy S Plus I9001 Android Development] skywalker01:
That's not what I meant. Although it is not proven that it won't work. Just replace "combine" with "adjust" or "port" or something like this ;)
[Galaxy S Plus I9001 Android Development] haydar100:
Is there anything i could do to help you with the kernel?
[Galaxy S Plus I9001 Android Development] skywalker01:
Well, you could test a complete beta release when I decide to publish it. But there is still so much broken and to test so I think it is still too early. And you won't see much differences to YardE's latest release anyway.

Well, I have just proven that you are wrong at least for the SGS+. The current beta of CM7 actually IS now booting with my latest kernel release (V1.3 02-02-12). And I didn't change a single bit of the kernel core itself (the zImage for those who have some basic linux kernel knowledge). The crucial point is obviously the startup script. Actually these are several scripts with hundreds of settings. But the kernel startup procedure is located outside of the kernel core. Namely in the startup scripts (rc files) of the ramdisk. So just combining the CM ramdisk with my prebuilt kernel core was my first (and obvious) attempt and it already worked.

So now begins the fiddling part, there are hundreds of settings in all these scripts and many of them look totally different. This is also true for the Galaxy W modifications, there are so many differences it would take me weeks to list and explain them all here so I won't. And it will take at least 1 or 2 weeks to analyse them all and get the kernel startup procedure as close to the stock ROMs as possible while still being able to boot CM.

For more details you can just have a look into the sources (links were already given here) and run a diff on them, you will get some thousand hits i.e. differences ;)
[Galaxy S Plus I9001 Android Development] wietwiet:
Improper bootanimations (like this one) will just be skipped (blank screen), and cant give a bootloop. I can only look into the thumbnails on my phone, but they look pretty nice.

The bootanimation.zip needs some refinement though: folder layout and scripting of the desc.txt files are wrong. To make it work on any stock rom (and probably yarde's cm build eventually as well), you'll need to rename the folders to part0 / part1, and the images into "00001", 00002"

Download another bootanimation, and see how layout and desc.txt should be.

Btw, this is getting horribly off-topic
[Galaxy S Plus I9001 Android Development] dhiru1602:
@YardE

https://www.codeaurora.org/xwiki/bin/QAEP/ics_chocolate

Check this and see if you find something useful.
[Galaxy S Plus I9001 Android Development] wintel_mac:
Not so helpful. I already posted the link to that project earlier.

And we need either 7230 or 8255T, but they are not in the list.
[Galaxy S Plus I9001 Android Development] kubson1999:
When can we expect the final version? Months, maybe more? By. I preferred a port ics

Wysłane z mojego GT-I9001
[Galaxy S Plus I9001 Android Development] nail16:
Have patience man, our dev section ain't so popular as the i9000 one so we gotta wait, yarde is doing his best to port cm7 for us now. ics port won't happen so soon, if only we had more devs around here :(
[Galaxy S Plus I9001 Android Development] kubson1999:
Hi, I can not find a link to the latest version. I ask for? Thanks

Wysłane z mojego GT-I9001
[Galaxy S Plus I9001 Android Development] Blumdum:
take a closer look on the first post

http://xdaforums.com/showpost.php?p=22394052&postcount=284
[Galaxy S Plus I9001 Android Development] abbradar:
Just a post to say "I'm still there, guys"

I've studied Galaxy W's configuration for half a week and it really helped me to understand A LOT about our device, those guys have done a lot of work. I've basically rebased my configuration on it, and it looks sooo much cleaner and prettier now. I've tried to compile ICS with my new conf, but ran into many compile errors, I'll continue with Gingerbread but with new configuration for now to achieve first usable build faster. Though, I think it is much closer now to completion. My studies are harder now, so I have much less time and I'm not reading forum much, I'll look over this thread really good later.

I have some ideas considering audio, I'll try to implement them later. I'm studying CodeAurora and Samsung's kernel sources now. See you later, stay tuned!
[Galaxy S Plus I9001 Android Development] immortal3k:
Yo,

i sory for this question but i don't understand whay You don't use this porting....

galaxy w have almost the same hardware...?!

I so sory for my english;]

http://translate.google.pl/translat...genmod-9-ics-dla-samsunga-galaxy-w/#more-2498

http://samsunggsm.pl/nowe-romy/cyanogenmod-9-ics-dla-samsunga-galaxy-w/#more-2498
[Galaxy S Plus I9001 Android Development] Keinbockwurst:
Umm.. Dude, he actually said that he looked at the Galaxy W's port ;) It seems that it helped him a lot, and im very happy that he sticks to Gingerbread, I dont like the look and feel of ICS, I would prefer a CM7-Port! :)
[Galaxy S Plus I9001 Android Development] skywalker01:
@YardE: well done, I have performed similar steps and even finished a complete compilation of CM7 for the Galaxy W (based on arco68's ICS work) some days ago. While I also managed to make it even boot on our phone (with my SGS+ kernel image) I come to a quite contrary conclusion. There still seem to be many differences to our phone (even the board is different) that it isn't so much help from my point of view as your post implies. Maybe I missed something crucial but the fact that there is much more broken/not working on our phone with the Galaxy W CM than in your latest I9001 build seems to prove my impression. The fact that the Galaxy W build of CM does boot on our device (with an appropriate SGS+ kernel) of course also proves that there are a lot of similarities. But sadly none that I wasn't aware of before looking into the Galaxy W.

But on the other hand it is absolutely true that you can actually learn a lot about basic methods and features of the android sources itself while analysing sources from other phones. But this is not very device specific and therefore true for ANY other (android) phone. So I didn't concentrate on the I8150 so much but looked at everything I stumbled upon in the last two weeks. The interaction of the many android libraries is still very challenging so I concentrated on a clean base first which means my kernel core and the startup ramdisk.

The result so far is that my kernel (primarily the startup scripts in ramdisk, no relevant changes to the core necessary) is now ready for use with CM and shouldn't need much more modification. Today I studied the vold sources quite a lot and I already know why the original vold.fstab from the stock ROMs does not work with CM7. Unfortunately with my modifications so far only the internal sd card is completely mounted by vold. Actually vold already recognizes the external sd but just holds it in idle unmounted state for unknown reasons. Seems to be an ums/lun problem, still working on that matter.

BTW: vibration and haptic feedback seem to be controlled by AudioHardwareManager so fixing audio should also solve these two issues (perhaps). I am also working on this but this is very complex and challenging as you already noticed ;)
[Galaxy S Plus I9001 Android Development] annqx:
Just want to give a quote of Acro about porting parts of his work to SGS+:

"[...]However, all my work for the Galaxy W are on my github, and it should be pretty easy for someone having your device, and having a little bit of experience working with AOSP source, to adapt it to work for you. Most important though is to get your kernel to be more compatible with ICS, but there you can also look at the things I've done to the Galaxy W kernel"
[Galaxy S Plus I9001 Android Development] skywalker01:
Well, actually none of this is new, so I hope it's just for the records.

Because that's exactly what arco already said some weeks before and what I and also YardE have already done in the last week: getting his github sources, analysing them and then porting it all to the I9001. But still with gingerbread sources, YardE already said why not ICS and I had the very same problems. And my results are described above and at least from my point of view more a drawback than a progress.

For the working state of CM(7) for the I9001 that is. But of course I learned a lot new features of AOSP just like YardE so it really was helpful for us but not for the mod itself if you understand what I mean. But again - the hardware is NOT similar enough to make it just work like many non-coders here think.

Maybe it is asked too much and you will NEVER understand if you are not a coder yourself, but looking at other phones with less similar hardware can sometimes even help more. That's at least true for me and I have already studied a lot of other phone sources as well. I got a lot of ideas from all that but testing them all needs even more time.

So there is absolutely no need for such posts like above so please be patient and keep the thread tidy.
[Galaxy S Plus I9001 Android Development] annqx:
@skywalker01 Don't take it so serious. It wasn't meant to offend you or Yarde nor your work.

Just wanted to post it, so you don't miss anything.

"Most important though is to get your kernel to be more compatible with ICS".

Pretty sure you know that already but who knows... can't hurt to quote it or? ;)

And maybe the focus of someone who ported CM9 is different to someone who is in the development.

If it doesn't help pls just ignore it.
[Galaxy S Plus I9001 Android Development] pinowthebird:
I'm curious, what differences in hardware are you talking about?

Ofcourse there's the CPU and the displaytype. But what are the less obvious ones?

Keep up the good work, skywalker01 and YardE :)

By the way, I would love to see a custom ROM from you guys.

Never thought about it before?
[Galaxy S Plus I9001 Android Development] rayiskon:
People get a life and stop refreshing the thread waiting for an update.it will be here when it's finished.

Whenever u feel the need open a thread in General and discuss whatever is on ur chest. Thanks for giving me the chance to contribute to OT.
[Galaxy S Plus I9001 Android Development] Damunix:
don't know if this can help, but I flash the ROM, but some things I see:

- USB seems to be always see as "connected", I always have the notification

- for the Cyanogen Settings, it seems that the application is not in the ROM:

E/AndroidRuntime( 582): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.cyanogenmod.cmparts/com.cyanogenmod.cmparts.activities.MainActivity}; have you declared this activity in your AndroidManifest.xml?
E/AndroidRuntime( 582): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1405)
E/AndroidRuntime( 582): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1379)
E/AndroidRuntime( 582): at android.app.Activity.startActivityForResult(Activity.java:2827)
E/AndroidRuntime( 582): at android.app.Activity.startActivity(Activity.java:2933)
E/AndroidRuntime( 582): at android.preference.Preference.performClick(Preference.java:828)
E/AndroidRuntime( 582): at android.preference.PreferenceScreen.onItemClick(PreferenceScreen.java:195)
E/AndroidRuntime( 582): at android.widget.AdapterView.performItemClick(AdapterView.java:284)
E/AndroidRuntime( 582): at android.widget.ListView.performItemClick(ListView.java:3513)
E/AndroidRuntime( 582): at android.widget.AbsListView$PerformClick.run(AbsListView.java:1849)
E/AndroidRuntime( 582): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 582): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 582): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 582): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime( 582): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 582): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 582): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:864)
E/AndroidRuntime( 582): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:622)
E/AndroidRuntime( 582): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 152): Force finishing activity com.android.settings/.Settings
[Galaxy S Plus I9001 Android Development] Rhonin86:
Hi Skywalker, first of all a real BIG THX for your engagemant :D.

I wonder if it is possible to get your new kernel ? I use your SkyHigh 1.2 meanwhile for more than a month without problems. And i get new battery duration records :D I searched for it but can't find a download link.

Thx in advance

Rhonin :D
[Galaxy S Plus I9001 Android Development] dr.wtf:
sorry for off topic. is there skyhigh for non cymod-roms?
[Galaxy S Plus I9001 Android Development] skywalker01:
I didn't release any version of V1.3 so far but V1.2 is here:

http://xdaforums.com/showpost.php?p=21664707&postcount=23

OK, added standard V1.3 for use with ANY stock ROM here but it's just the boot.img. So unzip and copy to internal sdcard and then flash via adb as usual:

adb shell su -c "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8"

Someone of the more experienced guys here may also build a CWM flashable zip from that and upload it here if requested by somebody while I continue with CM building and debugging :D
[Galaxy S Plus I9001 Android Development] dt-floppy:
Would you release a testbuild?
[Galaxy S Plus I9001 Android Development] skywalker01:
Did you read the third from last line ???
[Galaxy S Plus I9001 Android Development] rayiskon:
keep it up :)
[Galaxy S Plus I9001 Android Development] Damunix:
I send you a PM with diff for a "better"(?) cyanogen ROM compilation. I succeded in compile a cyanogen ROM with a "lunch cyanogen_galaxysplus-eng", but I have no time to try it on my phone.
[Galaxy S Plus I9001 Android Development] genericmann:
I tried flashing this kernel on top of UCM Gingerbread (XXKQ1). When in CWM it sais:

...deleting boot

...copying to boot

...REBOOTING

...phone reboots, but under system info i see the same old FeaCore kernel.

(i wiped cache partition and Dalvik prior to flashing it)
[Galaxy S Plus I9001 Android Development] crybert:
Take this One!
[Galaxy S Plus I9001 Android Development] skywalker01:
OMFG, please stop spamming this rubbish. :mad:

You just changed some labels in the Galaxy S (I9000) make files and even there only about half of the obvious device label settings, still lots of I9000 instead of I9001 references there. :(

And even with all of this done correctly this would only be about 1% of the REAL necessary changes to the CM sources. No device specific hardware settings are touched so only the display would work. That is if it would boot at all what is impossible, see below why.

But most important: you didn't even care to change the kernel flash settings which means this so called "better"(?) cyanogen ROM would flash the Galaxy S kernel to a Galaxy S Plus.

This will for sure soft brick any Galaxy S Plus because it's completely different hardware apart from the display. And perhaps even hard brick it because the kernel base and the partition tables are quite different and therefore it could most probably damage the bootloader beyond repair which is equivalent to a hard brick (exactly this happened to YardE when he was fiddling with vold and the partition tables). :eek:

One last remark: you ask in your PM if I "already" make a cyanogen package. Did you read any of my posts ??? :confused:

Well, if you really have you obviously didn't understand anything of it. :eek: :mad:
[Galaxy S Plus I9001 Android Development] broodplank1337:
boot.img and recovery.img are not related to dalvik so that won't help. It might be so that the name is not yet changed (I don't know)
[Galaxy S Plus I9001 Android Development] Damunix:
Yes of course this was based on galaxy S, I was just trying to help.

Sorry for the inconvenience.
[Galaxy S Plus I9001 Android Development] neluba:
@YardE Wow, well done!!1!!

Ohh, I can't post the "me gusta" meme :(
[Galaxy S Plus I9001 Android Development] Alex93917:
I installed it, it's lack of optimization, but this is only the beginning of development.

Good job!

Good luck for the future!
[Galaxy S Plus I9001 Android Development] naturist:
You can verify the device status here :

http://stats.cyanogenmod.com/
[Galaxy S Plus I9001 Android Development] abbradar:
Interesting link, thanks ^_^. Also, if there is our device, it means someone could establish Internet connection from it. How, I wonder...
[Galaxy S Plus I9001 Android Development] manveru0:
Hi there, good job. I think we should implement the extract-files and setup-makefile bash scripts, since they get all the needed proprietary drivers from our phone. We can of course just copy them from an existing image. Right now I'm working on adapting the extract-files.sh from other already "ported" devices
[Galaxy S Plus I9001 Android Development] abbradar:
Oh, that's really good, I've just thought about that. ^_^ Meanwhile, I've built tun.ko (was asked by one forum member), also fixed DPI and tried to load some of original modules into device. Looks like files in device/samsung/aries_common can be pretty useful to us.

Started build from scratch, looks like DPI-related resources are not updated otherwise. I'll check some of my updates and push them to repo then.

Also, made small kernel patch to allow us to use "ueventd.galaxysplus.rc" and "init.{...}.rc". (just changed name of board a bit, according to Android's init sources, this should work)
[Galaxy S Plus I9001 Android Development] manveru0:
sounds good then, ehm small detail: I've seen you have the entry BOARD_HAS_NO_SELECT_BUTTON := true (or something similar, I've already deleted it) in the BoardConfig. I don't think thats needed since our device do have a select button. I've removed the entry from the board for FeaMod 1.2. Otherwise you always have the *********Go back****** button on screen which is useless in my opinion.
[Galaxy S Plus I9001 Android Development] abbradar:
Oh, thanks. I'm merging with your repository from time to time, so just push the change.
[Galaxy S Plus I9001 Android Development] manveru0:
hehe that's what I'm doing with your repos as well :D I'm pushing it in the next view minutes. By the way, how can I merge on the console? I'm a pretty noob considering github.
[Galaxy S Plus I9001 Android Development] abbradar:
In fact, I have no idea as well. (if you are talking about github's pull requests) I'm working like in this manual: http://help.github.com/fork-a-repo/
[Galaxy S Plus I9001 Android Development] manveru0:
ye yeah :-D so we are on the same boat. Thx for the link
[Galaxy S Plus I9001 Android Development] abbradar:
Pushed changes to repositories just now. Also, don't forget to do "make mrproper" before commit or you'll end with lot of temporary files in it.

I'll call it a day for now, waiting for your extracting scripts a lot. ^_^ We should pull at least properietary modules from /lib/modules, firmware, maybe modem firmware as in aries_common, GPS and so on...

Oh, one last thing - I think we have incorrect /system and /data partition sizes. For /system I've took size of system.img.ext4 from original firmware. Also, we have a lot of strange partitions, useless at the first sight - we should check if we can take their space into /data or something else later.
[Galaxy S Plus I9001 Android Development] manveru0:
Have a good evening then :-) I'm working on them and hopefully load em up this evening. Yup, I agree with you, I think I'm gonna even pull to many files, but we can care about those later I guess. I'm gonna have a lookt at those partitions and their sizes. Maybe I find something out.

Ah yeah, I need to do the make mrproper, thx and read from ya soon

EDIT: wow, this was my 100th post :-D

EDIT2: uploaded the scripts and some files into modules. I've also included the bcm4329... files. We should think where to put them to. The ariesve-vendor-blobs.mk produces an error in line 42 (multiple target patterns) But I can't see it for now. ..
[Galaxy S Plus I9001 Android Development] abbradar:
Here is my dev log for today:

I've completed extracting scripts and made them work (though, we should think which files we need/don't need, I was too lazy to write copying for all proprietary libs today ^_^). Finally learnt true "platform name" for our phone and renamed .rc files accordingly, and reverted renaming commit in kernel. Lots of config changes. Results - system asked me for PIN code on start... and hanged up immediately after input. It hangs up after loading shell if no SIM is inserted. So far, I'll call it a day for today. Also, I learnt a pretty fast way to flash new build to device - via packing it to .tar archive and extracting it in recovery via "adb shell" (for small changes if you know them, just pushing them to /system via adb is even faster). We definitely need to get some info on what proprietary lib and bin does what and if they are needed at all. Also, dpi seems to be invalid even after rebuild with "hdpi"... or it is cyanogen's native settings? (all icons and interface at all is small comparable to stock build)
[Galaxy S Plus I9001 Android Development] abbradar:
It would be cool to have help from someone who once tried porting cyanogen - he would probably have a lot of experience in configuring builds. ^_^
[Galaxy S Plus I9001 Android Development] sakindia123:
y dont u contact codeworxx?
[Galaxy S Plus I9001 Android Development] skywalker01:
And ask shadowb0ss, he already wants to port ROMs for 9001 since September but couldn't begin as there was no working CWM for our device.

See his original post on that matter here:

http://xdaforums.com/showpost.php?p=17834406&postcount=20

With FeaMod v1.2 which is working great by the way - many thanks to manveru0 and you for that master piece - he no longer has any excuses ;)
[Galaxy S Plus I9001 Android Development] _strauch_:
Its nice to see, that something happend, i hope i could help in testing and donation :-).
[Galaxy S Plus I9001 Android Development] h94sharma:
ummm...

I did he isn't interested. And he needs a device for any development. Sooo....
[Galaxy S Plus I9001 Android Development] abbradar:
Missed a thread, sorry ~_^. Also, the radio module is working now!. Other problems are still exist, will continue work later.
[Galaxy S Plus I9001 Android Development] dr.wtf:
my phone won't boot now...
[Galaxy S Plus I9001 Android Development] wintel_mac:
Some phones seem to have problems with OC/UV kernels. Try to flash stock kernel from your ROM or the one with init.d support (there is a topic in this board with a link)
[Galaxy S Plus I9001 Android Development] dr.wtf:
its ok, just reflashed the rom... wanted to install cranium kernel but the site is offline... back to topic