After too many work's and to many white night GB now working, off course there's no GSM waitin to Rebellos and Oleg work's on. Thank's for them to make this possible.
First Picture :
This ddms because S8530 no lcd then S8500 can use it with LCD view.
Update :
First pre-alpha SD
Work : Touch screen, Screen rotate...
Don't work : Wifi, Audio, all key...
I9000 factroyfs XJVO, initramfs XJVP full with modification!!!
Kernel GB some modif but not necessary, dont remember now
Just to clarify, all the work is mine except the kernel which is Rebellos and Oleg, I had no choice to use the kernel in order to work on porting Gb. But it will be confidentially.
Very very nice
Cant wait for LCD drivers to get ready.. badly want to play with android even if there are countless things left to fix
suggest not calling it "release" because it's certainly not rename thread?
maybe *MAYBE* pre-alpha release once it's shown on a phone with working display - S8530 has slightly different sdcard interface apparently... i've not been able to mount anything yet on my S8500, well done getting platform to start on S8530.
nbates66 said:
suggest not calling it "release" because it's certainly not rename thread?
maybe *MAYBE* pre-alpha release once it's shown on a phone with working display - S8530 has slightly different sdcard interface apparently... i've not been able to mount anything yet on my S8500, well done getting platform to start on S8530.
Click to expand...
Click to collapse
Its some corrupt with disk_policy i disabled it. there's maybe difference but im not sure. Send you later script you will see. For now some little issue with touch screen.
Very well done my friend ^^
Tigrouzen said:
After too many work's and to many white night GB now working, off course there's no GSM waitin to Rebellos and Oleg work's on. Thank's for them to make this possible.
Click to expand...
Click to collapse
Thumbs Up! I just finished my GB kernel compile, (but I replaced the init with the old one in the intramfs - I need my Bada, too ) but I can not test it until later this afternoon or evening... I'm on S8500 ...
Which version of OS did you used?
i've had disk policy disabled in all my builds as well, trying another variation now after redoing my filesystem though, Tigrouhzen are you able to mount moviNAND as well yet?
Gud start ..
this GB port can work on S8500 right ? the s-AMOLED drivers are already ready with the devs unlike the wave II i believe..
so this Gingerbread port will display on the wave S8500 Screen?
nbates66 said:
i've had disk policy disabled in all my builds as well, trying another variation now after redoing my filesystem though, Tigrouhzen are you able to mount moviNAND as well yet?
Click to expand...
Click to collapse
Yes verry wel mounted all partition.
anghelyi said:
Thumbs Up! I just finished my GB kernel compile, (but I replaced the init with the old one in the intramfs - I need my Bada, too ) but I can not test it until later this afternoon or evening... I'm on S8500 ...
Which version of OS did you used?
Click to expand...
Click to collapse
OK, it boots here, too, to some extent: I can see the boot logo, but I haven't provided a filesystem to it so it reboots after a while... But my Bada is intact so later I'll try to mount the filesystem, too!
anghelyi said:
OK, it boots here, too, to some extent: I can see the boot logo, but I haven't provided a filesystem to it so it reboots after a while... But my Bada is intact so later I'll try to mount the filesystem, too!
Click to expand...
Click to collapse
Because its on initramfs. If you want your bada intact dont forget disabled disk_policy. I use Gb init full from i9000. The big hardly its you need to change script and some script on system also, and make right symlink then ive got problem with symlink doesnt make any link then i make on my initramfs a link, like mount ext2 /dev/block/mmcblk1p2 /sd2 ln -s /sd2/system /system....etc...
I go to sleep some good night !!!
Edit: nbates66 ive got a real all scripts, booting in sd version froyo then adb pull /*.rc
i've been able to get gb kernel to execute for a while but no filesystems yet, anyways, for filesystems you make, ensure you configure the toolbox symlinks, this will help ensure all services work correctly later on:
http://dl.dropbox.com/u/55049485/gb_binsymlinks.sh
(the files are slightly different to in froyo apparently, but same thing is done)
hmmm current sources less functional for me compared to the ones a few days ago, with this kernel source set i cannot get adb to work(worked on gb build a few days ago), still no filesystem mounts working on S8500 as far as i can tell either (yes, symlink method doesn't work either)
Tigrouzen said:
Because its on initramfs. If you want your bada intact dont forget disabled disk_policy. I use Gb init full from i9000. The big hardly its you need to change script and some script on system also, and make right symlink then ive got problem with symlink doesnt make any link then i make on my initramfs a link, like mount ext2 /dev/block/mmcblk1p2 /sd2 ln -s /sd2/system /system....etc...
I go to sleep some good night !!!
Edit: nbates66 ive got a real all scripts, booting in sd version froyo then adb pull /*.rc
Click to expand...
Click to collapse
It's no news for me to change the scripts, played a lot with that in Froyo But as I see the apply_disk_policy is commented out in the latest init.rc...
nbates66: with disabled disk policy is it safe for Bada to use the original init ? (oh, man, I checked the script you provided... I remember doing the same by hand some months ago )
anghelyi said:
nbates66: with disabled disk policy is it safe for Bada to use the original init ?
Click to expand...
Click to collapse
which one? If you mean the init here: http://code.google.com/p/badadroid-kernel/source/list
then yes and haven't corrupted my bada for 2 weeks! Haven't tried using the froyo init on Gingerbread kernel since a while ago though(gingerbread requires ueventd).
nbates66 said:
which one? If you mean the init here: http://code.google.com/p/badadroid-kernel/source/list
then yes and haven't corrupted my bada for 2 weeks! Haven't tried using the froyo init on Gingerbread kernel since a while ago though(gingerbread requires ueventd).
Click to expand...
Click to collapse
Was it with the latest one? As Rebellos replaced the initramfs completly!
yes i just tried two kernels with that init executable from latest file push, my bada OS is intact just i can't do anything with the kernels without adb or device mounting capability
nbates66 said:
yes i just tried two kernels with that init executable from latest file push, my bada OS is intact just i can't do anything with the kernels without adb or device mounting capability
Click to expand...
Click to collapse
Thanks! I'll replace the old one then and later do some tests!
how about getting the old irc port channel up to discuss some results and ideas?
I saw that you wrote that screen rotation works. I was wondering, if you can charge the battery of the phone?
Awesome work, thank you a lot. I will donate next month.
Good work, awsome work indeed,
Just for asking, is this a Cyanogen Mod 7 version of GB for Galaxy S? If it is, then it's awsome work... If it isn't, why you don't pick it up? I have 0 knowledge in this so it can be a noob question, but I am interested in knowing that
Cheers
Related
If I undertsand well with the root applied we are sticky on the old kernel. To solve the problem we could is the old kernel to boot a new one as here:
embeddedarm.com/software/arm-linux-bootloader.php
What do you think?
Ciao Angelo
Ok at the end I thinked how to load alternative rom without modifying the bootloader (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
ardf69 said:
Ok at the end I thinked how to load alternative rom without modifying the (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
Click to expand...
Click to collapse
This sounds good. Isn't it similar to HaRET for Windows Mobile?
Theres a ton of potential on the X10 i dont get why so many people don't like it..
anyways I'm working on trying to get apps on the SDcard with CM mod (I'm close)
xxsashixx said:
Theres a ton of potential on the X10 i dont get why so many people don't like it..
anyways I'm working on trying to get apps on the SDcard with CM mod (I'm close)
Click to expand...
Click to collapse
It's only because of the lack of multi-touch.
We'll be able to use froyo anyway, if we can get this bootloader running - whatever SE do. Then nearly all of the features of the X10 can be used.
Just a question concerning Android
If i got it right,
1. Android is running as a virtual java machine on top of the linux kernel
2. SE uses a newer kernel than other donut (1.6) androids
3. Java VM boots AFTER linux kernel and system
4. we have root, so we can modify the init.d (boot) files
5. so wo could let files be launched at boot time
Woldnt it be possible to insert a shell script that after booting linux kernel and before starting the java vm replaces the java vm files so that on top of the SE 2.6.29 kernel Froyo is running?
That way we wouldnt need to modify the bootloader. Only problem (?) ist that we are bound to the linux kernel settings made by SE (as we cannot overwrite the running system).
just an idea to discuss ....
Bax
I'm very very interested in deving for X10, I have extensive knowledge of linux and kernels
but anyways, android is running a Java VM? really?
Baxxx said:
Just a question concerning Android
If i got it right,
1. Android is running as a virtual java machine on top of the linux kernel
2. SE uses a newer kernel than other donut (1.6) androids
3. Java VM boots AFTER linux kernel and system
4. we have root, so we can modify the init.d (boot) files
5. so wo could let files be launched at boot time
Woldnt it be possible to insert a shell script that after booting linux kernel and before starting the java vm replaces the java vm files so that on top of the SE 2.6.29 kernel Froyo is running?
That way we wouldnt need to modify the bootloader. Only problem (?) ist that we are bound to the linux kernel settings made by SE (as we cannot overwrite the running system).
just an idea to discuss ....
Bax
Click to expand...
Click to collapse
Yes it can be done in /init.rc. A better solution (instead of copying files) could be to chroot the envinroment, so you teorically could have more rom (one for each directory in /system). Remain however the problem you cannot run a modified kernel (you need a boot loader like 2nboot-ng as I said before).
Ciao Angelo
xxsashixx said:
I'm very very interested in deving for X10, I have extensive knowledge of linux and kernels
but anyways, android is running a Java VM? really?
Click to expand...
Click to collapse
Hi!
Android is running in a Dalvik VM, similar to Java VM ...
http://en.wikipedia.org/wiki/Dalvik_(software)
Greetings from Vienna,
Bax
ardf69 said:
Yes it can be done in /init.rc. A better solution (instead of copying files) could be to chroot the envinroment, so you teorically could have more rom (one for each directory in /system). Remain however the problem you cannot run a modified kernel (you need a boot loader like 2nboot-ng as I said before).
Ciao Angelo
Click to expand...
Click to collapse
Hi Angelo!
chroot sounds goot, but could be a space/speed problem. On SD there is enough space, but it is slower - so that could be testing ground. Internal Rom is faster, but if original is not overwritten space could be limited.
Concerning modified kernel: Is that modification really necessary for running Android 2.1? If i remember it right N1 uses a similar Kernel for 2.1 as SE for 1.6?
Greetings,
Bax
Lets keep this going and hopefully get a working 2.1 system
Baxxx said:
Hi Angelo!
chroot sounds goot, but could be a space/speed problem. On SD there is enough space, but it is slower - so that could be testing ground. Internal Rom is faster, but if original is not overwritten space could be limited.
Concerning modified kernel: Is that modification really necessary for running Android 2.1? If i remember it right N1 uses a similar Kernel for 2.1 as SE for 1.6?
Greetings,
Bax
Click to expand...
Click to collapse
There are interesting patches to the kernel as overclock for example. I think we can use the original kernel at the start and then we can create a new one kernel from the sources.
Ciao Angelo
That sounds great!
Another limitation i remember is the limited RAM use in 1.6 which is probably also a kernel/driver problem ...
(i think starting from 2.0 or 2.1 the full RAM area is usable)
Bax
We might be able to use the information already tried on the motorola milestone which also has a locked down bootloader.
http://and-developers.com/motorola_milestone
this has information on the kexec option
Also the mot_boot_mode hack looks promising. I don't have any idea of the boot up process of the X10 but hopefully this would work.
"mot_boot_mode hack
A.k.a. the Newton hack. The init.rc script resides in the signed boot CG, so we cannot alter it. But it happens to exec /system/bin/mot_boot_mode, which we CAN change once we run as root, since it's located inside the system CG. By moving mot_boot_mode to mot_boot_mode.bin and creating a shell script as our new mot_boot_mode, we can get the system to run commands of our choice such as mounting partitions, etc. This is the earliest we can tap into the boot process, and it is early enough to let us introduce hacks such as APPS2SD, making better use of /cache, and other useful stuff. We could even branch to load a new kernel using kexec like mechanism."
Yes I know it is not the X10 but hopefully we can learn from work already being done on the motorola milestone.
seems like an interesting idea, I hope some of the devs have time to work on this while dealing with the issues with root. They might be taking a well deserved break which is fine.
ardf69 said:
Ok at the end I thinked how to load alternative rom without modifying the bootloader (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
Click to expand...
Click to collapse
1 is done
2 working on 2
3.is for omap cpu wont work !!
4.manualy did it and device boots works
jerpelea said:
1 is done
2 working on 2
3.is for omap cpu wont work !!
4.manualy did it and device boots works
Click to expand...
Click to collapse
Great work, jerpelea!.
I'm not sure I understand this, but does this involve loading a another kernel after the flashed one, to boot into another rom?
HunteronX said:
Great work, jerpelea!.
I'm not sure I understand this, but does this involve loading a another kernel after the flashed one, to boot into another rom?
Click to expand...
Click to collapse
I'm curious about that too. Are we talking some kind of chainloading, kexec or even something UML-like?
Yes bu not using motorolas module
Motorola has different cpu
Sent from my X10i using XDA App
jerpelea said:
Yes bu not using motorolas module
Motorola has different cpu
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Ok, thanks.
Is there a module for the QSD8250 snapdragon chipset?
So I've finally kind of figured out several files in partition mmcblk0p1. Files named custom, init, and recovery are actually kernel and initramfs packed with 256 header. Information at offset 0x94 is length of kernel + header (256 bytes) and offset 0x98 is length of initramfs. Except of file init, contain additional size which I'm not actually understood.
By extracting init file, and modifying extracted initramfs, I can boot to android system with rooted state.
I've experimenting using unionfs got from somewhere in this forum and added files su and superuser.apk. I've added in init file inside initramfs.
Actually analyzing recovery files, we can get information regarding recovery program which mostly in bash script.
I've include my kernel and initramfs extracted from file init in mmcblk0p1. You can try for yourself only in Developer Edition, where you can flash your own kernel and initramfs.
Beware, I don't guarantee it will succeed... try for yourself
*Sorry, bad english...
Hi,
Is it not pointless to work on this squashfs, when we can use plain file/device partition on SDE (like Angstrom demo)? I guess (it's still theory - since I've just installed SDE) it's enough to create rootfs with copied everything from squashfs and /data - to make it fully writeable and rootable - and boot on it as /.
I'll give it a try later...
No methods are pointless. Stop saying that. It's a progress to what we can do with the device.
Anyway, were you able to make that root work on the main OS, dogma?
MoonPhantasm said:
No methods are pointless. Stop saying that. It's a progress to what we can do with the device.
Click to expand...
Click to collapse
Ehh ok - but it makes thinks complicated, while we should straight everything up - to make upgrading smooth and easy
MoonPhantasm said:
Anyway, were you able to make that root work on the main OS, dogma?
Click to expand...
Click to collapse
As far as I can see in files - it should work.
Here's a diff of those init files (what was added)
out# diff init init.old
53,54d52
< CP=/bin/cp
< CHMOD=/bin/chmod
122,130d119
<
< # Create tempfs on /rootfs/home and unionfs with /rootfs/system
< $MOUNT -t tmpfs tmpfs $rootfs_path/home
< $INSMOD /lib/modules/unionfs.ko
< $MOUNT -t unionfs -o dirs=$rootfs_path/home=rw:$rootfs_path/system=ro unionfs $rootfs_path/system
< $CP /home/su $rootfs_path/system/bin/
< $CP /home/superuser.apk $rootfs_path/system/app/
< $CHMOD 6755 $rootfs_path/system/bin/su
< $CHMOD 755 $rootfs_path/system/app/superuser.apk
Booting from normal ext3 device requires some more changes - but gives us no 300MB (or similar) limit, allows to change boot parameters after kernel boots up (now on squashfs partition) etc. etc.
Yeah.. I'm able to get root with kernel and initramfs I've attached...
I am very excited about the prospects with SDE. Hopefully with some more poking and prodding and with Archos Froyo source released we will see some nice custom ROMs coming down w/ full root and a re-mapped file system in the coming months. I for one am hopeful that the dev community embraces the Gen8's w/ SDE and bakes up a nice serving of Gingerbread!
I was thinking that in recovery there's tool to flash initramfs and kernel which formed in file custom in mmcblk0p1. If we can replace destination to init (not custom). I think we can force booting to our new change, without entering to recovery mode first.
But, I still don't want to break anything in partition mmcblk0p1 .
Also, if we can modifying squashfs file with new one, without script checking the file (I think is on cramfschecker program); we can have custom rootfs itself replacing androidmerged.squashfs.secure....
Just the thought...
Keep up the good work guys!
just copied the content of the squashfs in an ext3 image and modified the init and mountpoints.
will report later after some testing
Heh.. I've just did the same - but on ext3 partition of sd card. Not luck yet to full boot... yet...
me neither. don't have time for more testing today and tomorrow, but soon I have a lot of spare time
edit: currently running kernel and initramfs of dogmaphobia, works great so far
Let me know when you guys news beer on your break, its on me.
Keep up the good work.
its too bad i am too dumb to understand all of what you are saying.
Does this mean rhe archos can be booted with root?
is it then rooted on the normal android firmware i use at the moment or on something else?
If yes how exactly do i get this to work and will there be a easier version for people like me who dont know that much about that kind of things.
and sorry again if my questions are dumb,i just want to try to get it.
nimrodity said:
Does this mean rhe archos can be booted with root?
Click to expand...
Click to collapse
Yes - but with SDE installed (and voided warranty - unless Archos claims so)
nimrodity said:
is it then rooted on the normal android firmware i use at the moment or on something else?
Click to expand...
Click to collapse
We are trying to boot oryginal Archos-Android on writtable disk (then it will be fully rooted - on OS level at least). dogmaphobia prepared initrd (first stage boot - lets say) that mounts part of original dir tree as RW and installs SU (switch to root) tool.
nimrodity said:
If yes how exactly do i get this to work and will there be a easier version for people like me who dont know that much about that kind of things.
Click to expand...
Click to collapse
Probably yes, this one is not so hard either - but it's really just a first step, so I recommend to wait.
This is freaking awesome. Since 2.0.71 disabled temproot I haven't been using my 101 very much other than poking around in Angstrom.
I voided the warranty on every other Android device I own for root, and I sure don't mind doing it on my 101 either.
@$aur0n
thx for the explanation.
Since i am please ight now ho the archos works,i ca wait a while till something new comes up.
so no hurry,we all saw how achos handled that with an unfinished bugged fimware
this is great news, im so looking forward to the future with a fully rooted device. And all the benefits that comes with that,maybe some custom roms maybe even cyanogen mod, A2SD, custom kernels and Gingerbread. If this comes thru it blows this wide open. Keep up the good work
@dogmaphobia you've written kernel size was at 0x94 and initramfs size at 0x98 but I don't get it. 2byte value (db70) at 0x94 results in 56176 and (db700021) ist far too much for kernel size. same weird result for initramfs.
how did you extract initramfs and kernel from this mmcblk0p1/init file? may post a shell script?
I've checked my "custom" file - on pos. 94 i have unsigned 32bit (8 bits) value "2218864" - witch might be ok, since 2218864-256=2218608 - and that's exactly the size of kernel that dogmaphobia send (and it's bootable).
On pos. 98 I have value "833767" (8 bit stream like before) - that's look also quite ok.
ps. and you should be able to extract it with dd (dd if=custom of=whatever bs=1 skip=245 count=2218608) - it's slow with bs=1 but...
Heym I mounted the rootfs.img as loop, put the two files from dogmaphobia in /boot and copied the image back to internal memory, but wasn't able to boot from this image. Any tips?
I've been thinking: In order to use UrukDroid or Churli's quick-root method, we have to sacrifice using the other, as well as giving up on Angstrom (not a great loss...).
Thinking of the future, is there a way we can insert a bootmenu (something Grub-like) at the beginning of the SDE boot process that could allow us to have multiple OSs on the Archos. This way, for example, we could install Uruk on the SD while still having Angstrom available. We could then potentially install Ubuntu, Honeycomb betas, etc. in additional partitions we create.
I'm hoping to inspire someone...
strongergravity said:
I've been thinking: In order to use UrukDroid or Churli's quick-root method, we have to sacrifice using the other, as well as giving up on Angstrom (not a great loss...).
Thinking of the future, is there a way we can insert a bootmenu (something Grub-like) at the beginning of the SDE boot process that could allow us to have multiple OSs on the Archos. This way, for example, we could install Uruk on the SD while still having Angstrom available. We could then potentially install Ubuntu, Honeycomb betas, etc. in additional partitions we create.
I'm hoping to inspire someone...
Click to expand...
Click to collapse
Yes and no.
The no.
The problem is that the real boot loader (equivalent to grub on a linux box) is still not accessible. That boot loader is what does the choice between the custom, init and recovery images that are place in the /mnt/rawfs.
The Yes
It would be possible to create a zImage and an initramfs.cpio.gz with a special init script that asks what root filesystem to mount and then complete the boot.
The thing is that the kernel will be shared between all the custom boot solutions.
wdl1908 said:
It would be possible to create a zImage and an initramfs.cpio.gz with a special init script that asks what root filesystem to mount and then complete the boot.
Click to expand...
Click to collapse
That is what I was thinking about. I guess it was too early in the morning when I posted...
The thing is that the kernel will be shared between all the custom boot solutions.
Click to expand...
Click to collapse
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
strongergravity said:
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
Click to expand...
Click to collapse
I don't think so. Installing the SDE gives you the possibility to install a secondary kernel and to uninstall the default Android kernel.
So I can give you a No for your first question and a 'Yes, at the current state of development ans research' for your second question.
strongergravity said:
That is what I was thinking about. I guess it was too early in the morning when I posted...
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
Click to expand...
Click to collapse
There can be 3 different kernels.
custom
init
recovery
The custom is the only one that can be replaced when the SDE is flashed to the device, init is the stock android and recovery is just a kernel with some scripts that give you the ability to do stuff like reformat check disk etc.... Also the recovery is the part that is used to flash the custom kernel.
What about kexec, seems to be the perfect choice for this problem.
Unmensch said:
What about kexec, seems to be the perfect choice for this problem.
Click to expand...
Click to collapse
Sounds good to me, someone should definitly do some research and testing. Unfortunately it won't be me as I already have a bunch of project going on
Hi guy!
After some days without any answer, i have worked on Kitkat.
It seems that it boots on my tab.... :angel:
Wait the fist release on 2.6.29 kernel
And 2.6.37 for A70S2 (HC and FROYO)
:good::fingers-crossed::good:
Bizcuite
Amazing Biz... you are my hero :good:
airwolf1544 said:
Amazing Biz... you are my hero :good:
Click to expand...
Click to collapse
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
bizcuite said:
i will become all red stop stop please lol
well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only bt and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
ready to test sir!
Wow, just wow. Amazing!
Sharpen you swords (charge your batteries) and get ready for fiiiiiiight (and get ready for teeeeeeeeest)
bizcuite said:
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
I know its much work.. but you try it..
airwolf1544 said:
I know its much work.. but you try it..
Click to expand...
Click to collapse
Oooooh yes its lots of work. And patience to wait the compilation finish it...
I recompile all atm. I had forgotten to include all device.mk file maybe I will have trebuchet at first start (yes I compile cm11 ).
Gpu driver and libs seems to work... I have the boot logo (and a crash system. Bootloop)
First screenshot is near
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Ranomez said:
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Click to expand...
Click to collapse
You have the choice. you can choose in dev option dalvik or art.
Or chane an option in buid.prop, set libdvm to libart or inverse.
I have a boot failure at start, i try to fix it.
Bizcuite
Welcome Kitkat
Bizcuite
bizcuite said:
Welcome Kitkat
Bizcuite
Click to expand...
Click to collapse
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
mika67 said:
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
Click to expand...
Click to collapse
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
bizcuite said:
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Send me something to test - I am getting exited!
bizcuite said:
It will be possible with 2.6.29 kernel i think.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
mika67 said:
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
Click to expand...
Click to collapse
Partitions directmy wrote on the internal sdcard will be option at start.
Now. The main PB is the wifi hal. Because wpa supplicant v0.6 and wl1271 driver has been deleted from the code source of Android. I try to compile it for 2.6.35 (more easy because drivers are updated).
Let me see if there is a way to have wifi for 2.6.29 kernel.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
4qu4rius said:
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
Click to expand...
Click to collapse
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
bizcuite said:
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
Click to expand...
Click to collapse
Biz
Any progress on this?
Thanks
Mikerla said:
Biz
Any progress on this?
Thanks
Click to expand...
Click to collapse
Yes and no, i work on it when i have times.
I try to find any ways to have a working wifi. I use CM11 wifi drivers but i cannot use it correctly (myukernel or CM11 is not configured properly).
When i have a working wifi i will upload an alpha release.
For screen and navigation button, i think that there will have no pb with it. The managment about this is very different.
To fix:
-Wifi
-external/internal sdcard not seen
-OMX codecs
-Sound HAL
-BT
-ALL
Bizcuite
Ok guys, starting this theard also to find other devs that also are working on porting ubuntu touch to the same device and buildup a team, anyone interested?
So my 1st try was when CM wasn't final release and got stuck at boot, i could connect with adb, but i only got displayed ubuntu and kernel version, and only a few commands worked, this is my 2nd try, so let's hope it will work better this time, also i will put my work on github.
24.NOV.2013:
-Having issues with libstagefright: http://pastebin.com/C8cuCAYA
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
JustSueMe said:
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
Click to expand...
Click to collapse
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
Nice I have a dev build env for ubuntu touch but unsure how to pull repo for unknown device. But if u get a build that boots I'm more than eager to work on it
Sent from my GT-I9505 using xda app-developers app
I've tried a few times to get it going for the M919 but each time I can't get past the Samsung Splash screen. I wasn't even able to connect via adb. Granted, I don't exactly know what I'm doing, but I do have a build environment set up and do have a little experience building and debugging builds. I should have time to tinker with it again in a few weeks.
ubuntu build
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
i have a build enviroment made up and pulled repos ect.. i just need to work a few things out before im ready to test it and post on here, if you can point in right direction (if yours boots)
need to do the audio part but can boot without sound in the alpha
neeed to add in apparmor later, can be done later ubuntu should boot without it
brightness, i dont think it matters so much as booting up is priority but i dont seem to have file it wants me to change "device/[manufacturer]/[codename]/init.[codename].rc"
problem with the way fstab has to be setup
within my android source my fstab is "void.fstab" which has lines that look like :
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host/mmc2/ /devices/platform/msm_sdcc.2/mmc_host/mmc2/
ubuntu port guide for fstab asks to find a filename like "fstab.jfltexx" and have lines that look like:
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1
help with fstab will be much appreciated.
then ill make my build ready for testing/debugging + suppose ill upload files output files for others that are interested to use
Try this
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,journal_async_commit wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,journal_async_commit,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384
# recovery
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults recoveryonly
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults recoveryonly
# vold managed volumes
/devices/platform/msm_sdcc.2/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=sda:auto
Yes I used part of that, problem now is compile errors, I have fixed a lot of them which involved discarding some features for the time being.
Boot is the main priority though
Im stuck on a compile errors for shared library, ill attempt this one after I've slept.
Hope fully this is the last error, then ill have a .zip to upload .
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
coolnessQ said:
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
JustSueMe said:
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
Click to expand...
Click to collapse
are you unsing tw stock sources for the kernel? with 7.3mb it almost looks like that.
I have tried porting it before and here is my advise, you really have to look at the errors that it gives you during compiling rather then skipping it, or ignoring it, this is the only way you will get it decently working. the rom itself is only around 100mb if i remember correctly. the ubuntu package is like 400mb on top, but thats all proprietary files so universal.
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
JustSueMe said:
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
Click to expand...
Click to collapse
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
broodplank1337 said:
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
Click to expand...
Click to collapse
Ah I see this seems to of cleared it up abit for me, im busy today but may get look in at code, if not then tomorrow and clean it up abit and try recompile.
If it looks like a lost cause ill jump over to your git and pull that repo.
Fingers crossed
Sent from my GT-I9505 using xda app-developers app
commit to github so we can all take a look at it
.
..
You need to copy some header files for libstagefright to compile:
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMetaData.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-
core/inc/QOMX_AudioExtensions.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/OMX_QCOMExtns.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libmediaplayerservice
My cm compiled but it wont boot (after flashing .zip and ubuntu system)
hmm.. did you remove all unecessary APPS? that are only needed by android not ubuntu touch? at you it seems relating to mounting points, something in your source doesn't let the kernel mount the partitions, maybe find a different approach to mount and add it to the source tree.
http://e2fsprogs.sourceforge.net/
everyone with interest in using ubuntu
if your interested in ubuntu touch on jfltexx and want to help
your now in luck
go here http://forum.xda-developers.com/showthread.php?p=48344910#post48344910
there is the download links and a few fixes for connectivity
Here is the link to the AT&T/Tmobile rom download : http://www.androidfilehost.com/?fid=23252070760974893'
Here is the link to the how to site (now instead of the phablet download use the one above) : http://forum.xda-developers.com/showthread.php?t=2564187
Oh and you need to flash the lokidoki zip file if used for AT&T.
Had it working perfectly, it is in extreme alpha, I had the wifi working and sound only works when plugged into headphones.
This should be more than enough to get the rom started up and getting a nice UT running shortly where everything works :3
I am not responsible for whatever happens to you or your device before, during, or after this. :3