yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] hillbeast:
Progress update:

I haven't done anything in a while on Serenity as it is limited by the kernel now and I also haven't done much on the kernel as I haven't had much motivation to do so. However, in light of Jellybean going open source as we speak, and CM team are downloading the source also as we speak, I am currently waiting for their merge to finish before I will download the JB source and I will then begin (attempting to) port JB to the G3. I have no idea how much luck I will have, but I feel I should let you know.
[Galaxy 3 Android Development] ak700:
Is there any hope that Project Butter will make the device smoother?

All the best! :good:
[Galaxy 3 Android Development] hillbeast:
It's possible but I can't guarantee it.
[Galaxy 3 Android Development] hillbeast:
Change of plans (well no more of a set back), I need to rebuild my server before I can work with JB. It turns out JB comes with GCC 4.6 (great news as GCC 4.4.3 was outdated when ICS came out), but it's a 64-bit version of it.. and stupid Hill Beast installed a 32-bit variant of Ubuntu on his server when he set it up...

No idea why I did that but that means now I need to reinstall Ubuntu to get 64-bit (at least I'm damned sure I do), but even if I don't need to actually reinstall it to get to 64-bit, I really should because there are a few things I need to redo on the server, namely the hostname as it's no longer a Power Mac G5, it's now a server, and a few things need to be set up better with the drives and such and also VNC is acting really peculiar. It's all just easier to start from scratch.
[Galaxy 3 Android Development] nishant_713:
Can't wait to get my hands on JB, Even if nothing gets fixed. :P :D

But what i am able to understand, that ICS to JB should be an easier update for our G3 than GB to ICS, cause very little has changed. Correct me if I am wrong.

---------- Post added at 12:58 PM ---------- Previous post was at 12:06 PM ----------

That zip had some issues. Try this one... http://d-h.st/4Vs
[Galaxy 3 Android Development] hillbeast:
It would appear so. The only big change seems to be to the audio subsystem.

In other news, my new server is nearly up and running. In case anyone is wondering what I'm using, I will run you through it.

Note that my server is not powerful by any means, it was built from spare parts and will receive a massive upgrade at the end of the year when I finish upgrading my main computer.

The system is custom built, but it uses an HP server case as they are nice and it has a nice hotswap cage for the SCSI drives on the front.

CPU: Intel Pentium Dual Core @ 3.0GHz

RAM: 4GB DDR2 < needs more

OS: Ubuntu Linux 12.04 LTS AMD64

Remote Access: VNC4server, OpenSSH, VSFTPd, Unity 2D

HDDs: (where it gets interesting)

1 20GB slow drive for storing operating system and programs (/ ext4)

2 80GB Seagate Barracudas in RAID0 (fast drives) for source codes and projects and general /home storage (/home ext4)

2 74GB Seagate Cheetah SCSI 15K RPM drives in RAID0 for output from make (android/out) using symlinks for every project I use (/mnt/out ext4)

If people are wondering what is with the crappy 20GB drive for the OS, I wanted to save power and the programs are hardly accessed. It only needs to boot the system. When compiling Android, the system uses mostly the Cheetahs and the Barracudas. As for the using RAID0, I don't need any redundancy at all. All the data on this computer is backed up on Github or source.android.com.

Hope this may be of interest to some people. The server will be upgraded to a Core i7 930 with at least 8GB of RAM, probably more like 12 or 24GB by the end of the year. At the current rate I am saving, I will have my Ivy Bridge-E computer by then and my current parts will go into the server.
[Galaxy 3 Android Development] simbawimba:
wouldn't you run into a lot of similar issues porting JB as you did with ICS because of the kernel?
[Galaxy 3 Android Development] hillbeast:
Yes I will but if I'm going to work with something that isn't 100% working, I might as well work with the newest. I can't see there will be any less working in JB than in ICS.

A lot of the changes for JB seem to be for the better. Even during the compiling JB has left good impressions upon me for the following reasons:

Google added Smali to the repository

They updated GCC to 4.6

They added arm, mips and x86 targets natively (most likely to target those cheapo China tablets with MIPS chips and the new x86 Atom phones we expect to see popping up

Prebuilts are moved about a little to make it a little more sensible

There's more stuff around here and there, but I can't remember them off the top. JB looks good to me.
[Galaxy 3 Android Development] ahsanaimad:
So in a way we may get Jellybean as well? You Devs Rock.. I wish JB has Camera without Preview... :D Anyways All the Best...
[Galaxy 3 Android Development] strugalovic88:
Hi Hillbeast, why are u going to port JB before fixing ICS major errors? We even don't have full GB working, and i think that it would be better if u devs going in to project by project together and solve issues.. For example, if u solve all gb issues, u will find correct way of fixing main problems from FROYO to GB, and it would be much easier to go on ICS with full GB, ICS to JB with ICS for daily usage... I am not complaining, just told what i'm thinking about that..

Cheers!
[Galaxy 3 Android Development] hillbeast:
You guys will have to wait a bit before I can get it on the G3. JB also doesn't have support for ARMv6 so I will either have to add it myself again or wait until CM10 has that, but not sure how long that will take.

I'll start cloning their repo now that it's up.

EDIT: Oh wait no it's not. They haven't added it to the manifests.xml just yet.
[Galaxy 3 Android Development] achkap:
i have installed cm9 rc1 and now my phone shows a black screen and it won t boot. i cant even go to recovery mode with vol up+ down+home+ power.. and the worst thing is that i don t have a pc to flash something through odin. so i don t have a phone. anyone can help...? remember.. i don t have a phone
[Galaxy 3 Android Development] DoR2:
I think even PC will not help you.It looks like a hard brick...
[Galaxy 3 Android Development] achkap:
the backlights are on... besides i can enter into download mode by pressing the buttons. but how to enter to recovery mode..pressing the buttons doesn t work
[Galaxy 3 Android Development] hillbeast:
Because what's the point of trying to get something that is outdated working? Might as well see how much has changed in the new system and if not much has changed then just use the newer system. If ICS takes a while more to fix then we will be fussing around with something that's outdated and JB won't ever touch this phone. I can't see the effort to get JB going being more complex than getting ICS working. It's only a small change unlike GB > ICS was.

Does the Samsung logo show up?
[Galaxy 3 Android Development] DoR2:
If you can enter download mode I think you'll be able to come to recovery too(volume - volume + home off)
[Galaxy 3 Android Development] allspark2020:
I too got into problems like these

You need to flash via odin (no other alternative :()

@DoR2 I could not get into recovery in such a situation

hillbeast made foolproof odin for the users having same problem
[Galaxy 3 Android Development] achkap:
yes it does.. but i don t have a pc. is there any way just to get to recovery or erase everything? i know what to do next.

the former build of serenity worked very good.
[Galaxy 3 Android Development] PlumSauc3:
@Hillbeast is JB going to be a continuation of Serenity or will it be a completely seperate ROM?
[Galaxy 3 Android Development] achkap:
I think i am heading towards odin. Nothing i can do.. the funny thing is that i can enter both to download and upload mode but not recovery..weird...
[Galaxy 3 Android Development] strugalovic88:
Hm.. That really have sense... But, u know what i tought..
[Galaxy 3 Android Development] nishant_713:
Exactly my opinion. Whats the point of putting the effort to get something outdated, when the same effort can get something new. Jelly bean shall also bring performance improvements. So if not very much effort is required to get jb (though effort is required) then its always betrer to get the new one than trying to fix old one.
[Galaxy 3 Android Development] strugalovic88:
Hm.. I don't agree with that... We would have all the ports from gb, ics, jb but neither fully working. What is the point of that? Many people need their phone functions rather than good looking os with no functions.. I would like to see all that ports on g3 and probably will use it, but that's only because g3 is not my primary mobile. Think about people who have just g3..
[Galaxy 3 Android Development] ahsanaimad:
Stop imposing up your opinions and let the Developers Work the way they like, they ain't working for you.. Respect their decision. They are Devs coz they know something more..

Cheers!
[Galaxy 3 Android Development] hillbeast:
Depends on how much work is required for JB. If it's stuff all effort to get it to the level of ICS then yes. If not then no.

Your kernel is corrupted somehow. If the kernel doesn't work, then you have no recovery. It's a flaw in Samsung method of storing recovery in the kernel partition rather than the standard Google imposed of a kernel partition and a recovery partition separate from each other.

For those people we have Froyo. I get where you're coming from, but as I said, GB > ICS was a huge leap. GB was still able to run on old kernels whereas ICS can't. JB and ICS are supposed to be very similar (still haven't dived much into it), so therefore the amount of work to adapt JB for our device should be pretty minimal. It should only be a matter of getting the simple changes (adding ARMv6 support) and adding the device information. If I'm wrong about this then I will continue my efforts on ICS until it I feel JB would be better.

People gave marcellusbe this grief as well when he said he wanted to port CM6.2 on the device and people were all like 'Q.Q WAH WAH YOU ARE GIVING UP ON GINGERBREAD' when actually it will likely help me fix ICS as well.
[Galaxy 3 Android Development] sarthak.killedar:
True! CM 6.2 will be good one, actually it will clear many hardware problems! As our device hardware is made for that OS only!
[Galaxy 3 Android Development] strugalovic88:
Relax dude... ;) of course i respect our devs, especially great four marcellusbe, hillbeast, tom3q,dharam_mainar and all others..

I am not going to insult someone so just stay cool if i want to hear hillbeasts opinion.. ;)
[Galaxy 3 Android Development] ahsanaimad:
I am already relaxed ;) If you thught that I was rude or angry unfortunately you were wrong.. I am Cool...

:D
[Galaxy 3 Android Development] hillbeast:
Okay enough off topic. Nobody is angry on the XDA. We're a happy place :)
[Galaxy 3 Android Development] PlumSauc3:
Hillbeast, If I may ask, when do you suppose your first build of JB will be out?
[Galaxy 3 Android Development] hillbeast:
No clue. At this stage I'm discussing with SGS2 developers as it may seem that JB won't work on the Galaxy S2 without some major modifications to the audio subsystems because of the stupid Yamaha soundchip...

It's times like this that I miss the glorious WM8994 in the Galaxy 3...
[Galaxy 3 Android Development] achkap:
You right as always.. I just flashed a cm7 kernel and I was able to get into recovery and the rest was easy. Except that enough times my phone booted in airplane mode from which I couldn t get out. But now all is runing well.

And one question. Data2sd is not on. What can I do to activate it. Because I have link2sd which is very slow..

Sent from my apollo
[Galaxy 3 Android Development] hillbeast:
If Link2SD is already slow the Data2SD will be slower. I don't recommend it, but you can use KMapp.
[Galaxy 3 Android Development] DiGaTTo:
Found one interesting thing with calling issue (all call issues, call waiting, when you could not hear your opponent, ect.) If I calling to a person which has the same mobile operater as I everything perfect, but if I call to a person with different mobile operater I could not hear him until I push speaker. Maybe I'll be captain but I think it's something wrong with a driver, there is mistake in it from very begging which continues from ver to ver. It's main future of the phone - calls, so I think we need to look into it more deeper. I'm ready to help, but my knowledge right now is only enogh for linux comands ect. Im ready to learn to help so much as I can. So please pm me from what should I start
[Galaxy 3 Android Development] hillbeast:
The problem is that the kernel for this phone was never designed to handle ICS and as a result things will behave bizarrely.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] pmanian:
@hillbeast

Will this be useful in any ways...

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0375a/index.html

Edit: Attached one PDF File.

If not, sorry. :laugh:
[Galaxy 3 Android Development] nishant_713:
Hey Hillbeast, looks like some devs managed to get JB working for ARMv6 http://maclaw.pl/?p=205

Can it help in port of JB for G3 ??
[Galaxy 3 Android Development] ahsanaimad:
McClaw is an awesome Dev working for Galaxy Devices as Fit, Mini.. He has fixed full ICS (almost) on those devices with Old Outdated Kernel.. I think we must talk to him..

He works with Tom3q in Project GALAXYICS :D
[Galaxy 3 Android Development] hillbeast:
Nah it's too generic to help out, but thanks anyway.

I'm just waiting for CM10 to get a bit more finished (well rather more started) as it will have ARMv6 support as well. I don't even have CM10 for my GS2 yet, that's how early it is.

If anyone wishes to contact him then feel free to.
[Galaxy 3 Android Development] nishant_713:
We must, after all g3 is also a galaxy device, it deserves to be a part of galaxyics or galaxyjb project. Why not ask Tomq3 about this first, as they've worked together.
[Galaxy 3 Android Development] sad96:
@hillbeast

Maybe it's better to start porting clear JB as the matter not to waste time? And then make CM10 based on this port?
[Galaxy 3 Android Development] hillbeast:
Because then I need to make all the ARMv6 code myself.
[Galaxy 3 Android Development] cdesai:
Nope, check r.cyanogenmod.com

Sent from my GT-P1000
[Galaxy 3 Android Development] srgudhka:
Optimus one already booted jb. http://xdaforums.com/showthread.php?t=1751957

just few bugs left. @Hillbeast and rest, you guys are doing a great job. Its because of you guys i am able to atleast use my g3. =D
[Galaxy 3 Android Development] kylandomos:
"Please read!

This ROM is only themed and modded, until Google releases their source codes. Then I will try to build it."

I don't think so...
[Galaxy 3 Android Development] m1trand1r:
:what:?:what:?:confused:

Sent from my SGS-II powered by CM9
[Galaxy 3 Android Development] PlumSauc3:
I think he means that the Optimus One ROM is only prepared with themes and mods and hasn't actually been created yet.
[Galaxy 3 Android Development] PlumSauc3:
Hey Hillbeast, I heard that Marcell is working on a JB project too. I think that you should team up with him, Ruben and RaymanFX. After all 4 devs is a lot better than 1.
[Galaxy 3 Android Development] hillbeast:
Marcellusbe is a far better Android developer than I could ever hope to be, that's more his specialty. I'd be getting in the way if I tried to help him. Best if I stick to what I do best, which is kernels and just get kernel 3.4 done. We've got the ball rolling now so it's mostly just porting drivers and such now and lots of debugging.

I want to stick to one project per device I develop on, kernel 3.0 on the SL, 3.4 on the G3 and 3.3.8 on my Linksys WAG160N. If I do too much then I won't get anything done. It'll be like back when I was doing G3MOD, Kyorakernel, Kyorarom and Debian and all that stuff at the same time: nothing got done and the quality of my work was terrible. I want to maintain a high standard these days.

I'll follow their work though and I wish them luck. JB on our device won't be too hard (well to get it to ICS levels). It's certainly going to be easier than it is on the GS2.
[Galaxy 3 Android Development] nishant_713:
G3 is rocking these days... kernel 3.4 and cmx ... just amazing... also it looks like cm9 has become less popular cause cmx is hot topic now. :P
[Galaxy 3 Android Development] pmanian:
While building CM9 with your device and kernel (inline kernel) source.... I get the following error...

I was trying to build like this....

. build/envsetup.sh

lunch

make -j2 otapackage

Please help.

In file included from /home/prasanna/android/cm9/kernel/samsung/apollo/include/linux/mempolicy.h:62:0,

from /home/prasanna/android/cm9/kernel/samsung/apollo/init/main.c:52:

/home/prasanna/android/cm9/kernel/samsung/apollo/include/linux/pagemap.h: In function 'fault_in_pages_readable':

/home/prasanna/android/cm9/kernel/samsung/apollo/include/linux/pagemap.h:415:16: warning: variable 'c' set but not used [-Wunused-but-set-variable]

GEN usr/initramfs_data.cpio.lzma

CC init/do_mounts.o

File ../../ramdisk.cpio could not be located

line 45

File ../../ramdisk-recovery.cpio could not be located

line 46

make[3]: *** [usr/initramfs_data.cpio.lzma] Error 255

make[2]: *** [usr] Error 2

make[2]: *** Waiting for unfinished jobs....

Thanks.
[Galaxy 3 Android Development] hillbeast:
Yeah that's a problem I face too. It starts compiling the kernel before generating the ramdisks. Just make temporary ones:

cd out/target/product/apollo/
touch ramdisk.cpio
touch ramdisk-recovery.cpio

Then compile it, and then compile it again to make the proper ramdisks get inserted into the kernel. It's an issue with us having to use zImages rather than boot.imgs where the kernel and the ramdisk are in a package rather than being compiled together.
[Galaxy 3 Android Development] nishant_713:
Hey hillbeast, if I am not asking for too much, then can you please make a new build with those latest ICS fixes like bluetooth, GPS, USB mass storage fix.... Tried MPICS rom with those fixes but seems way too laggy and sluggish...
[Galaxy 3 Android Development] hillbeast:
I shall give it a go at some point, but not for at least a week. I am busy at work as I alluded to in the kernel 3.4 thread and I don't want to spend much time developing. I want to relax on my one day off.
[Galaxy 3 Android Development] pmanian:
Could you please tell me where does the rooting happens in your kernel.

I am looking for something like this....

https://github.com/dharamg3/g3_tuts/blob/master/initramfs/default.prop
[Galaxy 3 Android Development] hillbeast:
I don't believe I rooted my kernel in Serenity. I never bothered to do that, but what you could do is add the rooted default.prop to the repository, and add:

PRODUCT_COPY_FILES := \
device/samsung/apollo/init.apollo.usb.rc:root/init.apollo.usb.rc \
device/samsung/apollo/init.rc:root/init.rc \
...
device/samsung/apollo/recovery.fstab:recovery/root/etc/recovery.fstab \
device/samsung/apollo/default.prop:root/default.prop
[Galaxy 3 Android Development] pmanian:
Thanks.. Will try it out.
[Galaxy 3 Android Development] cdesai:
Fixed it :)

http://review.cyanogenmod.com/21035

That's ugly, you should override persist.sys.root_access if you want it enabled for adb too (by default it's apps only)

PRODUCT_PROPERTY_OVERRIDES := \
persist.sys.root_access=3

3 is apps + adb, 2 adb only, 1 apps only, 0 disabled

Also, you don't root the kernel, nor the default.prop

You just enabled root access ;)
[Galaxy 3 Android Development] pmanian:
Thanks cdesai. Similar to that I have one more problem... If I use CodeSourcery toolchain for building the kernel it works fine but not with default one. So is there a way to change toolchain used for building the kernel without modifying the source.
[Galaxy 3 Android Development] cdesai:
Yep, place it under prebuilt/linux-x86/toolchain/somename

Then, add TARGET_KERNEL_CUSTOM_TOOLCHAIN := somename to device.mk

And make sure prebuilt/linux-x86/toolchain/somename/bin/arm-eabi-* exists

P.S. Won't work with ics, we added this in jellybean.
[Galaxy 3 Android Development] pmanian:
@hillbeast / @cdesai

Please tell me, how do these partition size are calculated

BOARD_BOOTIMAGE_PARTITION_SIZE := 8388608

BOARD_SYSTEMIMAGE_PARTITION_SIZE := 222822400

BOARD_USERDATAIMAGE_PARTITION_SIZE := 204996608
[Galaxy 3 Android Development] hillbeast:
Well they don't matter anyway as they are for generating OTA images rather than OTA update.zips. The only one that matters is the BOOTIMAGE size which is actually wrong but when I enter the correct size it doesn't boot.

However I haven't checked it since I got UART so I could perhaps fix it.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] hillbeast:
To answer the question, they are the size of the partitions in /proc/partitions

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] sumit yadav:
I did as you said, it successfully compiled the zImage, then i compiled it again.

After i got the zimage 2nd time, i checked the ramdisk.cpio and ramdisk-recovery.cpio and they are empty, their size is 0 bytes,

I'm compiling cm11 kernel for samsung galaxy S2 GT-i9100.

Thank you.
[Galaxy 3 Android Development] hillbeast:
You shouldn't need to do this compiling for a Galaxy S2. They fixed this issue for the S2 a long time ago.
[Galaxy 3 Android Development] sumit yadav:
I am compiling only the kernel source is this the problem?, i don't have the full cm11 source.

And is it possible to only compile the cm11 kernel?, or i need to compile the full rom?

Thank you, sir.
[Galaxy 3 Android Development] hillbeast:
OH well that's where the problem lies. My instructions are relating to A a different phone completely, B compiling the kernel as part of the full CM compile, and C it uses the full source.

If you're trying to compile a kernel for CM11, you are really best served by compiling all of CM, as you need to get the RAM disk binaries from somewhere. You could extract the zImage but that's messy and I don't recommend doing it when you can just compile it yourself. I'm not going to give any details on how to do it anyway as there are plenty of guides out there on doing this.
[Galaxy 3 Android Development] sumit yadav:
Thank you for your great help, one last please give me link to GUIDE "how to open zImage", i'm asking you this because you are much more experienced than me, and you'll provide me with the best solution, as you did in your last posts.

Again, Thank you very much!
[Galaxy 3 Android Development] hillbeast:
I have no idea if this one will work or not.

http://xdaforums.com/galaxy-s2/themes-apps/how-to-unpack-repack-initramfs-zimage-t1294436
[Galaxy 3 Android Development] sumit yadav:
Sir, can you tell me what's this...

[Feeling confused]

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=i9100

Is it the full source code needed to develop future android builds or it the one sammy used to build JB fir i9100?

Thank you!
[Galaxy 3 Android Development] hillbeast:
If it's provided by Samsung, it's only going to be for Samsung JB firmware. No company provides source code for something they don't officially support.
[Galaxy 3 Android Development] sumit yadav:
Can we use them to upgrade kernel to Linux 3.4.x, as these sources for 3.0.x?
[Galaxy 3 Android Development] hillbeast:
There's no point in upgrading the kernel version on the Galaxy S2. It's already on a long term support kernel version, and the issues on the S2 are related to GPU libraries for Android, not a kernel level limitation.

Now can we please not continue this off topic discussion on a dead thread for a completely different device?
[Galaxy 3 Android Development] sumit yadav:
Okay, thank you

You served me best!