1415 replies to this topic

[maddoc600]

erikcas, on 28 September 2011 - 02:23 AM, said:

Already tried it..

Edit: I think I have Beta2 native working with spica's modem.bin. But I have this imei problem. I am registered to the network but no phone, no data.

I didn't the proper libsec-ril.so packed with it.
Now use another one.

Please test and report back. If it works we have the real Beta 2 on B7610

You are GREAT!

You are the only reason that stops me throwing my b7610 into the garbage bin!

Edited by maddoc600, 28 September 2011 - 04:00 AM.

[erikcas]

maddoc600, on 28 September 2011 - 04:00 AM, said:

You are GREAT!

You are the only reason that stops me throwing my b7610 into the garbage bin!

But does it work on your providers network?
I need only one confirmation of someone calling, twittering or whatever. Then I will repack with a newer modem.bin

If not, we have to do more research.

But for now, I will stop for today. I will become father in a few hours, my wife is having contractions since 2 hours,
You're welcome, my pleasure!

Edited by erikcas, 28 September 2011 - 05:11 AM.

[erikcas]

By the way, all credits are for Sandor, Voyteckst and Almar. They are the real developers I only try to adapt their excellent work to B7610.

Thumbs up for them!

[VMZ]

I'm knee deep in pink. Meh

For some reason none whatsoever kernels or anything get me past the pink screen. Funny  thing is, the Beta 2 worked in the 1st install (oh well, "worked" in a way... like no keyboard or connectivity).

I've tried to format the card in linux and the automatic install goes fine to the end and startup.txt is pointing to the correct partition (mmcblk0p2). Now with "no-pink" zImage it goes to the stage where it says "A N D R O I D" (no graphics) , nothing else happens.


@erikcas: best wishes to you and your family

[erikcas]

VMZ, on 28 September 2011 - 09:39 AM, said:

I'm knee deep in pink. Meh

For some reason none whatsoever kernels or anything get me past the pink screen. Funny  thing is, the Beta 2 worked in the 1st install (oh well, "worked" in a way... like no keyboard or connectivity).

I've tried to format the card in linux and the automatic install goes fine to the end and startup.txt is pointing to the correct partition (mmcblk0p2). Now with "no-pink" zImage it goes to the stage where it says "A N D R O I D" (no graphics) , nothing else happens.


@erikcas: best wishes to you and your family

Thanx!

Did you use autoinstaller? If yes, please re-partition your sd as one fat (no fat32) partition and reinstall by running the installer. Apply update at first boot.

If you install manually, create first fat partition, second partitin as ext4 and make in a primary partition.

[erikcas]

VMZ, on 28 September 2011 - 09:39 AM, said:

I'm knee deep in pink. Meh

For some reason none whatsoever kernels or anything get me past the pink screen. Funny  thing is, the Beta 2 worked in the 1st install (oh well, "worked" in a way... like no keyboard or connectivity).

I've tried to format the card in linux and the automatic install goes fine to the end and startup.txt is pointing to the correct partition (mmcblk0p2). Now with "no-pink" zImage it goes to the stage where it says "A N D R O I D" (no graphics) , nothing else happens.


@erikcas: best wishes to you and your family

Will provide a new test upload within half an hour.
If you have startup problems, please check your init.rc for the part below.
Check if it is according to your install (SD or My Storage)
set to mmcblk0 for SD, to mmcblk1 for my storage

write /sys/devices/platform/s3c6410-usbgadget/gadget/lun0/file /dev/block/mmcblk0

You can also try to remove "/tweak.sh" and the "exit" some 2 or 3 lines under tweak.sh

[LightningBullet]

Quote

Will provide a new test upload within half an hour.

I can't seem to find the update yet, looking forward to it.
Anyway, with the patch that you (erikcas) gave me, I have the same problem, it recognizes my provider but no phone/data connection.

Edited by LightningBullet, 28 September 2011 - 01:05 PM.

[LightningBullet]

Some small addition:
Even with the new version I still don't have any phone/data connection. It does recognize my provider though (KPN)...

[Gurbanyo]

HI all.first thx very much for ur work.about new update and kernel-qwerty and hardware buttons is work!( but button for lock is just go to black screen.there is no slider for unlock.and when i push again android is wake up.without slider.and of course no network.no data.(i tried many times to put to sd and storage no result.everything is work.only phone no work.

[VMZ]

erikcas, on 28 September 2011 - 11:08 AM, said:

Did you use autoinstaller? If yes, please re-partition your sd as one fat (no fat32) partition and reinstall by running the installer. Apply update at first boot.

Wow, that really does a difference, I've tried numerous combinations and different builds after my 1st (and up to this moment the only) successful boot of Android and I kept thinking that autoinstaller formats my Android partition every time. How wrong I was...

So for clarification and note to everybody: Always repartition and format your SD card to one FAT16 partition before using autoinstaller!


Now I'm currently testing the latest (REV64) version, so far everything works great but no outbound connectivity

[erikcas]

VMZ, on 29 September 2011 - 11:08 AM, said:

Wow, that really does a difference, I've tried numerous combinations and different builds after my 1st (and up to this moment the only) successful boot of Android and I kept thinking that autoinstaller formats my Android partition every time. How wrong I was...

So for clarification and note to everybody: Always repartition and format your SD card to one FAT16 partition before using autoinstaller!


Now I'm currently testing the latest (REV64) version, so far everything works great but no outbound connectivity

Yup, maybe the driver (dpram?) has to be revised. Currentley enjoying my new born daughter (born 16 hours ago) will look into this when mother and daughter are doing their beauty-sleeps this afternoon

[VMZ]

erikcas, on 29 September 2011 - 11:19 AM, said:

Yup, maybe the driver (dpram?) has to be revised. Currentley enjoying my new born daughter (born 16 hours ago) will look into this when mother and daughter are doing their beauty-sleeps this afternoon

That's such a nice time... Congratulations 8) 8) 8)


I'll continue testing


/VM

[Gurbanyo]

nobody gonna answer my post?about network.

Edited by Gurbanyo, 29 September 2011 - 05:17 PM.

[VMZ]

Gurbanyo, on 29 September 2011 - 04:27 PM, said:

nobody gonna answer my post?about network.

Networking needs more investigation, but I think erikcas is on the right track


/VM

[Gurbanyo]

VMZ, on 29 September 2011 - 05:42 PM, said:

Networking needs more investigation, but I think erikcas is on the right track


/VM

i hope we will have working network .beta 2 is very fast and smooth.

Edited by Gurbanyo, 30 September 2011 - 08:26 PM.

[inf3rn0]

Hi all,

first off, a big up to all omnia2-devs for opening up all these possibilities for our beloved devices.

Also a big up for erikcas & elbee (i see their names popup here & at the googlecode pages) for adapting the kernel for our 'beloved' (or hated ) b7610's.


My situation is as follows;

I've used the manual install method from the phj.ru page, and first booted with the included kernel. This booted fine and was working, albeit without keyboard support and with incorrect hardkey mapping, etc.

By my understanding Erik was able to get the keyboard working and correct the hardkey mapping, atm without outbound connections.

So i checked out revision 64 from googlecode svn (the latest to date), and compiled the kernel - all as is...

This gave me a non booting kernel, with a cursor blinking a couple of times in the top left-hand corner, and a screen blackout a couple of seconds later.

I checked out the compilation of the kernel again, and it seemed the kernel was a build of googlecode/svn/kern_oII - and from what I can understand I need the build of kern_2.6.32.

To achieve this, I edited the make_kernel script, commenting out the line that defines kern_oII as the kernel source directory.

Now the kernel also compiles, giving me a larger zImage than before (about 2k bigger) - so to me it seems like its compiling the .32 kernel.

Loading this kernel, the screen turns to the pink screen, -as the original i8000 kernel did at first boot- and stays on this screen for over 10 minutes. I waited so long because I have no idea if the 'dalvik-cache' needs to be recreated or whatever with this new kernel - it is only noted on phj.ru as the reason why the first boot takes so long

So I'm missing something, probably big

The command I execute to compile the kernel:       # PHONEMODEL=b7610 make_kernel -kc

The script exits without error, copying the zImage to the out folder and all.

I replaced the 'working' i8000 kernel with this zImage and,... nothing.

Please enlighten me



Greetings,
   Inf3rn0

[erikcas]

inf3rn0, on 02 October 2011 - 09:15 PM, said:

Hi all,

first off, a big up to all omnia2-devs for opening up all these possibilities for our beloved devices.

Also a big up for erikcas & elbee (i see their names popup here & at the googlecode pages) for adapting the kernel for our 'beloved' (or hated ) b7610's.


My situation is as follows;

I've used the manual install method from the phj.ru page, and first booted with the included kernel. This booted fine and was working, albeit without keyboard support and with incorrect hardkey mapping, etc.

By my understanding Erik was able to get the keyboard working and correct the hardkey mapping, atm without outbound connections.

So i checked out revision 64 from googlecode svn (the latest to date), and compiled the kernel - all as is...

This gave me a non booting kernel, with a cursor blinking a couple of times in the top left-hand corner, and a screen blackout a couple of seconds later.

I checked out the compilation of the kernel again, and it seemed the kernel was a build of googlecode/svn/kern_oII - and from what I can understand I need the build of kern_2.6.32.

To achieve this, I edited the make_kernel script, commenting out the line that defines kern_oII as the kernel source directory.

Now the kernel also compiles, giving me a larger zImage than before (about 2k bigger) - so to me it seems like its compiling the .32 kernel.

Loading this kernel, the screen turns to the pink screen, -as the original i8000 kernel did at first boot- and stays on this screen for over 10 minutes. I waited so long because I have no idea if the 'dalvik-cache' needs to be recreated or whatever with this new kernel - it is only noted on phj.ru as the reason why the first boot takes so long

So I'm missing something, probably big

The command I execute to compile the kernel:       # PHONEMODEL=b7610 make_kernel -kc

The script exits without error, copying the zImage to the out folder and all.

I replaced the 'working' i8000 kernel with this zImage and,... nothing.

Please enlighten me



Greetings,
   Inf3rn0

do:
./make_update B7610 what-you-want

(B7610 will be set as phonemodel)

edit make_update and apt_kernel to the correct out path, kernel path (kern_2.6.32) and modules path (modules32)

good luck!

[Gurbanyo]

any news about phone,

[erikcas]

Gurbanyo, on 03 October 2011 - 06:37 AM, said:

any news about phone,

no yet from my side...

[Banbu]

really expect for that. i opened this site: http://code.google.c...id/updates/list ten times a day. much thanks to you