Jump to content


Photo

About Android beta

* * * * * 2 votes

  • Please log in to reply
131 replies to this topic

#41
almar

almar

    Newbie

  • Members
  • Pip
  • 14 posts
Although I appreciate the effort, I have a pretty clear idea what is happening. I think I could easily give you a kernel which would work. This is not in my or your interest, I want to make the full device work. For this what we need are the logs. If nobody is able to produce them, I will create a script which does the above, so you guys would only have to run it in haret like it was a kernel.

  • 0

#42
fire3element

fire3element

    Newbie

  • Members
  • Pip
  • 46 posts
  • Location:Houston, TX
  • Devices:Samsung i920, Motorola Droid X
Ok, let me ask a few questions then. I was under the impression that the beta installed android on the SD card, and ran from that location. Is this right?
What I was hoping to accomplish was, by replacing the beta zImage with the alpha Image... I was trying to get the base foundation for android to install on the SD card. After that, I wanted to switch back to the zImage and hope that it would get past the "Checking kernel crc..." to let the beta finish installing.
It was just a lark, but I thought it couldn't hurt to try.
I also ran Haret from the root of my storage, changing values in the default.txt to see if it would spark anything interesting.
OH, BY THE WAY. DO NOT CHANGE "Set ramaddr 0x50000000" to 0x20000000. It will hang the Haret process and will keep your phone stuck in the "Omnia II" boot logo. I did it several times to confirm. NO, A HARD RESET WILL RESULT IN NOTHING
I also tried changing the Set CMDLINE "root=/dev/mmcblk1p2 init=/init" to... mmcblk1p1, mmcblk1p2, mmcblk1p3, mmcblk1p4, mmcblk1p5, mmcblk0p1,
mmcblk0p2, mmcblk0p3, mmcblk0p4, mmcblk0p5.
I get different errors of output with different mmcblk combos.


Now I would like to add something I found last night.
During the boot log that I posted in my last post, I received a very strange error.

mmc0: new MMC card at address 0001
mmcblk0: mmc0:0001 M8G4DD 7.65 GiB
mmcblk0: p1 < p5 >
Creating block devices...
Creating other devices...

-----between the lines "mmcblk0: p1 <p5>" and "Creating block devices..." I see 3 more lines at random.
mmcblk0: p1 <p5>
mmc2: host doesn't support card's voltages
mmc2: Got command interrupt 0x00010001 even though no command operation was in progress.
mmc2: error -22 whilst initialising SDIO card
Creating block devices...

I seem to get this error at shear random. I come from a clean boot everytime, and immediately launch Haret from the 02beta folder. There is no set pattern to the error above. I get it about 1 out of 5 times, but not 1 every 5 times. Sometimes it does it multiple times, back to back and then maybe nothing the next 10 times.
Nothing on the phone or SD card (completely clean) has changed, nor is the SD card the problem. I verified by trying a few different SD cards, resulting in the same error (4gb class4, 128mb class2, 2gb class2).
I have tried formatting the SD card under Windows with NTFS, FAT, FAT32, and exFAT. Also formatted from the phone,but nothing seems to make a difference. I have tried to turn off any power saver settings on the phone, set CPU to HIGH, and tried while plugged into the wall outlet. Nada...
And I would like to mention that it is not the SD card socket loose or anything like that. I have never used this phone (nice paperweight), so it is still like new.


@elbee72: Just as many others have posted, if you use the zImage from the beta release, Haret will hang at the "Jumping to kernel..." message.
I am not skilled enough to do the things you have suggested. I have no knowledge of linux or programming. I am just the dummy in the test car so to speak. I let you know if I feel something. LoL
The reason that I tried the Image file from the alpha, is that I read from many different threads that many i920 users could not get the alpha to load. That is when someone smart (not me) figured out that it would work with the uncompressed zImage, hence the Image file. That is why I requested that Alamr give us the uncompressed image of the new zImage. Maybe I will not work, but it might give more detail in a log as to why it wont boot.
I have searched and tried to figure out how to uncompress the zImage file, but everywhere I search said that it was near impossible without the source code.

I can try a few more thing you suggested, but remember you are playing dodge-ball with a blind guy (I'm the blind guy).




@Alamar: If you have a spare second, could you supply us with the non-compressed zImage file. I am not sure if It will do any good, but it might get the i920 users a little further than the "Jumping to kernel..." message. Then we could provide the heret logs for both zImage and Image outputs.
Thanks
Edit: LoL you posted while I was typing. I did not get a chance to read your comment before I posted mine. Apologies :P

Edited by fire3element, 08 February 2011 - 03:51 PM.

  • 0

#43
almar

almar

    Newbie

  • Members
  • Pip
  • 14 posts

Edit: LoL you posted while I was typing. I did not get a chance to read your comment before I posted mine. Apologies :P

Doesn't matter. But it really doesn't matter what kind of output you get. You could have corrupted your NANDflash with your 0x2000000 command and brick your phone. You are running the Image from alpha which I already knew would run. But I want a safe option, not a trial and error one. With all the knowledge we got from the whole process we don't have to do the trial and error if I get my logs which are android/(z)image indenpendant. So i created a slimmed down script. If you guys would please run this and send me the created i920 log file. Attached File  default.txt.txt   557bytes   59 downloads

From this we can analyse what changes we have to make, to make it work. This script is not as complete as my instructions but it is better than nothing. Once you have the output, please compress it in a nice zip and send it to me. What would be even better if you opened up the log file with a text editor. You would see all the addresses with all the corresponding hex values (0x). If you would take the xps file match the register address with the corresponding value and give me a nice little excel sheet with all the registers and all the corresponding outputs (except ofcourse for the mmu dump). If you don't know what im talking about, never mind. Explaining it in more detail would cost me more effort than doing it myself.

Good luck,

Marc

  • 0

#44
elbee72

elbee72

    Regular

  • Members
  • PipPip
  • 130 posts
  • Devices:Samsung i8000, HTC Desire

Doesn't matter. But it really doesn't matter what kind of output you get. You could have corrupted your NANDflash with your 0x2000000 command and brick your phone. You are running the Image from alpha which I already knew would run. But I want a safe option, not a trial and error one. With all the knowledge we got from the whole process we don't have to do the trial and error if I get my logs which are android/(z)image indenpendant. So i created a slimmed down script. If you guys would please run this and send me the created i920 log file. Attached File  default.txt.txt   557bytes   59 downloads

From this we can analyse what changes we have to make, to make it work. This script is not as complete as my instructions but it is better than nothing. Once you have the output, please compress it in a nice zip and send it to me. What would be even better if you opened up the log file with a text editor. You would see all the addresses with all the corresponding hex values (0x). If you would take the xps file match the register address with the corresponding value and give me a nice little excel sheet with all the registers and all the corresponding outputs (except ofcourse for the mmu dump). If you don't know what im talking about, never mind. Explaining it in more detail would cost me more effort than doing it myself.

Good luck,

Marc

I am used to haret and can help a windows user or a linux user with a i920 through all the steps to get almar the logs he needs.
I myself dont own a i920

pse mail me at elbee1972 at gmail dot com if you want to put in some effort in making this nice Android port work on i920

EDIT: got some help now, i'll update this post when we get the logs for almar

Edited by elbee72, 08 February 2011 - 08:38 PM.

  • 0
For info about Android port to I8000 Omnia 2 (like) winmo phones you can visit http://code.google.com/p/omnia2droid/

#45
urphonesux

urphonesux

    Diehard

  • Members
  • PipPipPipPip
  • 370 posts
  • Devices:AMDZERO'D out i920!!!!!!!!
I can be remote controlled if anyone is interested.
I have a i920 and would like to run android on it BUT i have no knowledge of the ins and outs of android.
hopefully elbee will respond to my email for assistance but other than that im at a loss
if you will just tell me what to do in a simplified manner i got you

also would it help to just let you rdp into one of my pc's setup just for this?

Edited by urphonesux, 08 February 2011 - 07:32 PM.

  • 0

#46
almar

almar

    Newbie

  • Members
  • Pip
  • 14 posts

Doesn't matter. But it really doesn't matter what kind of output you get. You could have corrupted your NANDflash with your 0x2000000 command and brick your phone. You are running the Image from alpha which I already knew would run. But I want a safe option, not a trial and error one. With all the knowledge we got from the whole process we don't have to do the trial and error if I get my logs which are android/(z)image indenpendant. So i created a slimmed down script. If you guys would please run this and send me the created i920 log file. Attached File  default.txt.txt   557bytes   59 downloads

From this we can analyse what changes we have to make, to make it work. This script is not as complete as my instructions but it is better than nothing. Once you have the output, please compress it in a nice zip and send it to me. What would be even better if you opened up the log file with a text editor. You would see all the addresses with all the corresponding hex values (0x). If you would take the xps file match the register address with the corresponding value and give me a nice little excel sheet with all the registers and all the corresponding outputs (except ofcourse for the mmu dump). If you don't know what im talking about, never mind. Explaining it in more detail would cost me more effort than doing it myself.

Good luck,

Marc

The script can be loaded by Haret, in the same way the regular default.txt(which you have to replace). Make sure you rename it to default.txt, as is see here it is two times .txt.

  • 0

#47
elbee72

elbee72

    Regular

  • Members
  • PipPip
  • 130 posts
  • Devices:Samsung i8000, HTC Desire

The script can be loaded by Haret, in the same way the regular default.txt(which you have to replace). Make sure you rename it to default.txt, as is see here it is two times .txt.

Memdump has been made (for b7610, i920, i8000) and send, waiting for analyses.
Thanks for dumping !!

  • 0
For info about Android port to I8000 Omnia 2 (like) winmo phones you can visit http://code.google.com/p/omnia2droid/

#48
nickmo20

nickmo20

    Regular

  • Members
  • PipPip
  • 105 posts
  • Location:Chicago IL
  • Devices:Omnia i910 & i920
Can anyone confirm that the dumps have been sent? @Almar, do you have what you need?

  • 0

#49
nahyah

nahyah

    Newbie

  • Members
  • Pip
  • 33 posts

Can anyone confirm that the dumps have been sent? @Almar, do you have what you need?


I'm almost done getting the dumps. I just couldnt get to it this weekend. My church made me a small group leader and had to do that all weekend. Hopefully i can have it finished by the weekend.

@Almar, I looked into the GPIO project. Would that help speed up the porting process?

  • 0

#50
nickmo20

nickmo20

    Regular

  • Members
  • PipPip
  • 105 posts
  • Location:Chicago IL
  • Devices:Omnia i910 & i920

@nickmo20: would you mind sharing the details of how you got it to work?

Here is what I did:
Downloaded Beta
Downloaded Alpha
Unpacked Beta to default location (root of My Storage)
Unzipped Alpha on desktop, then copy Image to both root of My Storage and 02beta folder.
Opened default.txt (root MyStorage and in 02beta folder) and changed "Set kernel" from zImage to Image. (note, I did not actually remove the zImage from either location)
Ran Haret.exe from 02beta folder
Process begins, but eventually ends up in a kernel panic (comes up with error "fdisk: cant't open '/dev/block/mmcblk1' ")

let me post the exact transcript of what comes up on my screen:

Welcome to Android Install on Samsung Omnia II

mmc0: new MMC card at address 0001
mmcblk0: mmc0:0001 M8G4DD 7.65 GiB
mmcblk0: p1 < p5 >
Creating block devices...
Creating other devices...
Mounting internal SD memory as mmcblk0p5...
Internal FLASH mounted.
Preparing SD card ...
Empty SD card ...
fdisk: can't open '/dev/block/mmcblk1'
mkfs.vfat: can't open '/dev/block/mmcblk1' : No such device or address
Not enough space on SD card...
Kernel Panic - not syncing: Attemted to kill init!
Backtrace:
yada yada yada yada yada yada yada yada yada yada yada
blankidy blank blank
oasiudfh a osidfh aos iguh io awu er htoq ywbh gasigp ahfashdb oic uhvl awegf uwi bvf
and so on...

Rebooting in 30 seconds...
Then I get right back into WinSlo.
Funny thing is, my SD card is a Kingston Micro SD HC, 4GB, Class 4. The text above reads that the phone is reporting my SD Card as 7.65 GiB. (and yes the card is empty, have formatted in Windows 2 times)
I have tried running Haret.exe from MyStorage right after this, but it hangs on r4 r5 under "kernel_init_0x0 something, something"
I tried going back and running Haret from both locations again, but no dice.

Does this have anything to do with the very first message you get after you hit RUN in Haret?
It shows:

HARET boot
Shutting down hardware
Turning of MMU
In preloader
PSR 60000df
Kernel relocated
Initrd Relocated
Is this normal? Sometimes the lines "Turning of MMU" through "PSR 600000df" are all jumbled up together on one line and you can't read it. Next time its ok, then bad the next. ??? LoL
@nickmo20, what ROM are you on? Also, what SD card do you have? (brand name, size, speed class)
Hope some of this info is helpful.



Um, most likely I got this by shear accident, and I don't want anyone to mess up there phones by something I did... I just did some tinkering late at night, and I was tired, and not quite sure how I got it.

Also, this past weekend was a bit busier than expected, but I am now doing the steps to getting those dumps. Sorry to almar that I'm a noob when it comes to this detailed stuff... I'll get you whatever I can. I hate to be the illiterate guy here. If I had the time to commit like I did my last phone, I'd be of more help. Sorry I can't be of much help now.

  • 0

#51
nickmo20

nickmo20

    Regular

  • Members
  • PipPip
  • 105 posts
  • Location:Chicago IL
  • Devices:Omnia i910 & i920

Doesn't matter. But it really doesn't matter what kind of output you get. You could have corrupted your NANDflash with your 0x2000000 command and brick your phone. You are running the Image from alpha which I already knew would run. But I want a safe option, not a trial and error one. With all the knowledge we got from the whole process we don't have to do the trial and error if I get my logs which are android/(z)image indenpendant. So i created a slimmed down script. If you guys would please run this and send me the created i920 log file. Attached File  default.txt.txt   557bytes   59 downloads

From this we can analyse what changes we have to make, to make it work. This script is not as complete as my instructions but it is better than nothing. Once you have the output, please compress it in a nice zip and send it to me. What would be even better if you opened up the log file with a text editor. You would see all the addresses with all the corresponding hex values (0x). If you would take the xps file match the register address with the corresponding value and give me a nice little excel sheet with all the registers and all the corresponding outputs (except ofcourse for the mmu dump). If you don't know what im talking about, never mind. Explaining it in more detail would cost me more effort than doing it myself.

Good luck,

Marc


OK, sorry to keep posting but I do have a file for you. I'm not sure what I'm doing, and kind of like you said yourself, it might be easier for you to plug it in, than explain to us... (whenever you have time of course!)
http://www.megaupload.com/?d=SBS6SWZA

  • 0

#52
elbee72

elbee72

    Regular

  • Members
  • PipPip
  • 130 posts
  • Devices:Samsung i8000, HTC Desire

Memdump has been made (for b7610, i920, i8000) and send, waiting for analyses.
Thanks for dumping !!

used nickmo20's dump (thanks) for extra reference.
send raw dumps and new excel comparison to almar.

info: from 93 register values (dwords) 6 differ semi-random and 15 differ consequent between models (i8000 b7610 i920)

  • 0
For info about Android port to I8000 Omnia 2 (like) winmo phones you can visit http://code.google.com/p/omnia2droid/

#53
almar

almar

    Newbie

  • Members
  • Pip
  • 14 posts
Hi Guys,

Great work! I forgot to add these to the script:

PWRCON0 0x7C200029 R/W Present State Register (Channel 0) 0x0
PWRCON1 0x7C300029 R/W Present State Register (Channel 1) 0x0
PWRCON2 0x7C400029 R/W Present State Register (Channel 2) 0x0

Can anyone add this to the script on the bottom:

pdump 0x7C200029 4
pdump 0x7C300029 4
pdump 0x7C400029 4
pdump 0x7C200028 4
pdump 0x7C300028 4
pdump 0x7C400028 4
pdump 0x7C20002c 4
pdump 0x7C30002c 4
pdump 0x7C40002c 4

And send me the new output?

Thanks!

  • 0

#54
nickmo20

nickmo20

    Regular

  • Members
  • PipPip
  • 105 posts
  • Location:Chicago IL
  • Devices:Omnia i910 & i920
here's the thing. I'm doing everything via opera mobile while my monitor is bring fixed (also samsung) so it makes everything take longer than normal. so putting everything into excel mobile would almost kill me haha! it should only be about 10 more days unless it doesn't get fixed or they need to acquire a whole new unit. granted swype is a life saver while writing on the forums I just simply don't have the time right now to fit it to your needs (almar) . sorry. I'll do my best to get another dump loaded!

  • 0

#55
cergaster

cergaster

    Newbie

  • Members
  • Pip
  • 15 posts
  • Devices:i920
@elbee Any news on the 920

  • 0

#56
elbee72

elbee72

    Regular

  • Members
  • PipPip
  • 130 posts
  • Devices:Samsung i8000, HTC Desire

@elbee Any news on the 920

Almar got all the HaRET info he requested.
Depending on the analysis, some parts of the kernel have to be excluded or changed for i920 to boot safely.
Almar is also working on other area's (cam/sensors/..) so don't know when analysis/adaptation is scheduled ....

  • 0
For info about Android port to I8000 Omnia 2 (like) winmo phones you can visit http://code.google.com/p/omnia2droid/

#57
cergaster

cergaster

    Newbie

  • Members
  • Pip
  • 15 posts
  • Devices:i920

Almar got all the HaRET info he requested.
Depending on the analysis, some parts of the kernel have to be excluded or changed for i920 to boot safely.
Almar is also working on other area's (cam/sensors/..) so don't know when analysis/adaptation is scheduled ....



Thanks for the reply i've been watching this project from day one. I wish i knew something about how to do some of this stuff to help out but i have zero knowledge of these things. When the project is ready for the 920 i'll probably be that guy asking all the dumb questions about how to install (LOL)

  • 0

#58
Snow02

Snow02

    Addict

  • Members
  • PipPipPipPipPip
  • 515 posts
  • Devices:Omnia SCH-i920
I have an i920 I'm not using. Do you still need those dumps almar? If there's anything else you need done just let me know.

Edit: nvm, just saw the post a few up from this. Offer still stands if you need any testing done.

Edited by Snow02, 18 February 2011 - 04:11 AM.

  • 0

#59
elbee72

elbee72

    Regular

  • Members
  • PipPip
  • 130 posts
  • Devices:Samsung i8000, HTC Desire

@elbee Any news on the 920

  • Haret logs reveil: hint about diffs in UART, Almar will investigate
  • modded kernel tests reveils: alpha touch driver is working on i920, but modded new i8000 touch driver isn't yet.
  • modded kernel tests reveils: key mapping is messed up, but easely fixed
Thanks to testers/loggers !!

If you want to play with Android on your phone alpha version is still your best bet (touch and screen working, but slow, glitchy).
i920 modifications on i8000 beta will be ready for closed beta testing when ready.

We could use people who like to test versions and have adb working on alpha.
Adb can work on Windows platform, but easier to make it work on linux.
If you want to play a bit you can download alpha from xda-developers.
Make sure you use Image in stead of zImage in default.txt.
for adb on windows check here and here
for adb on linux check here and here
usb in alpha is glitchy, so play with different times to plug in usb cable (from start, from somewhere in booting proces, afterwards).
interesting adb commands are: "adb logcat" (logs on android level) and "adb shell dmesg" (logs on linux/kernel level)

  • 0
For info about Android port to I8000 Omnia 2 (like) winmo phones you can visit http://code.google.com/p/omnia2droid/

#60
nickmo20

nickmo20

    Regular

  • Members
  • PipPip
  • 105 posts
  • Location:Chicago IL
  • Devices:Omnia i910 & i920
why is it that i can't get android out of landscape mode? anyone else with i920 having this issue?

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users