yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] :
Hi Jesse,

I tried the new initrd, with the latest files up to 07-29 but I got some old problems... Calls could be answered but no audio, and I could not hang up... the call was dropped but Android did not know it, and could not turn it off, so I had to press the soft reset button.

I had to go back for the previous initrd and then everything as usuall (but the outgoing calls)

PIN was not tested, since I'm reseting so often my mobile, I don't use it.

I will post the SIM vs. USIM logs this weekend at latest.

Regards,

JM
[Touch Cruise Android Development] briggs81:
I also had no change with the new initrd unfortunately.
[Touch Cruise Android Development] bally3:
No luck at all with the hero builds lite or full, just black screen on boot and nothing else. I was getting to the logo last night with the looping but today I cant even get to that.

Rogers build works but I cannot for life of me get a data connection to work.
[Touch Cruise Android Development] briggs81:
Yeah still no go for me either. Getting tired of transfering files to sd card :P. could be a problem with sdhc cards.. not sure.

Rogers is working for me with data connection, but can't stand the oval shapes to things, so no more of that :P Will stick to trusty default setup.
[Touch Cruise Android Development] radem205:
When I use the rogers system (initrd.gz and roger2.0.img) it didn't pass the bootscreen (HTC logo stays on the screen).

The only files that I have changes is the initrd.gz and the system.img. Is it right that you have to rename the rogers2.0.img to system.img?
[Touch Cruise Android Development] briggs81:
yes, rename to system.img. You must have a 320 x 480 and lcd.density=160 for it to load up, apparently.
[Touch Cruise Android Development] vilord:
juan, was that with the 2009-07-30 initrd?

hmm.

I've gotten a version going that doesn't use default.txt stuff, it just uses what is in android's apk list (including username and password), although it does seem to have an issue with receiving sms, sending is fine, so i didn't post this morning...

It is very frustrating... gotta also figure out why audio got stuck for you and why it wouldn't hang up the call, that sounds like the RIL was locking up.

The PIN stuff I was just hoping that turning it on would help... apparently not...
[Touch Cruise Android Development] bally3:
That is correct.

I now have all the hero builds working. :)

Instructions:

Download zenulators hero-black build here

Connect to data in WinMo. (dont know if necessary but it might help with data issues).

Unpack to sd card and run.. no data image.. let it create one. it takes at least 10 mins to get to the lock screen.. dont touch anything even when the lock screen comes up .. clck wait on all the forced close boxes until it settles down. Add apn settings, connect modem and skip sign into google as this hasnt worked for me yet. Wait for it to become steady and the digital clock is on the screen then power off.

reboot and backup your newly created data image, you'll use this now for all these builds.

copy the hero image lite or full and run.. it should boot straight into Android.. enjoy the new touch flo.. realise its completely unusable but that you just had to see it anyway (even though you already knew that :rolleyes:) and then switch to the more usable lite version by copying the lite system image and renaiming it.

Good luck :)
[Touch Cruise Android Development] vilord:
how useable is hero lite? what works, what doesn't?
[Touch Cruise Android Development] bally3:
Sigh.. its usable I guess.. but even the lite one has lag.. and data still doesnt work. I'm downloading the 2.5 build thats meant to fix a few issues.. let you know how it goes.. but really I think hero is a novelty for the time being. As imfloflo pointed out it doesnt run fast on a 528mhz processor, its not going to run that fast on a 400Mhz one with less ram.

My take on this is its always worth a try, but if a system is slow on first boot, its hardly going to get better as you use it more and add more.

But..the novelty factor does keep you wanting to find out.. :rolleyes:
[Touch Cruise Android Development] briggs81:
Nice work! Gonna try now.
[Touch Cruise Android Development] briggs81:
Where is that one? I can't seem to find it. I just see a 29-07-09..
[Touch Cruise Android Development] vilord:
could you try the initrd here: http://vogue-android.googlecode.com/files/initrd-2009-07-31.gz

it bypasses the apn settings in default.txt and exclusively uses the stuff in android's apn list...

also on my phone calls in/out work fine, and text out works, but text in fails... looking for some perspective on that from others in our community
[Touch Cruise Android Development] briggs81:
Done. Will do it shortly.
[Touch Cruise Android Development] briggs81:
Same results for me with that initrd.. :( can't call out, can't even receive calls, unless i make a call first in winmo, even then it's not always like that.. sometimes i have to make a call, sometimes i dont. I do believe I can solve this issue though. Buy a Rogers Magic :P :D

Those Hero roms are pretty neat. Definitely not usable yet, but I can see the lite hero one eventually being used. some neat apps on there, i like "peep".
[Touch Cruise Android Development] freddycs:
Android Hero - Back-in-Black

zenulators have just released Android Hero build - Back-in-Black version HERE 4 hours ago. I have downloaded it and have a quick test, speed seems to be laggy a little bit, but now at least we can experience the sense UI in our Polaris.

Still not able to make outgoing call, have not try if able to receive call. SMS failed to send out, but able to receive though.... For internet connection, the 3G icon appear after APN is configure, but i can't find the modem application to make connection... though there is an option to keep internet on all the time in the setting page...

according to zenulators, the screen resolution must be 320X480 and 160. booting for the first time takes a while, just select wait if there is any force close of application...it will reboot by itself after first booting...

will try to explore it more later... :)
[Touch Cruise Android Development] bally3:
Lite version is working great at the moment with market and email working fine. The speed has improved significantly with the addition of a swap file.

Resolution cant be changed though and I experienced some call issues, but its starting to look promising.

Just wish we had working wifi, all this data download to get set up again is killing my data plan limit :rolleyes:
[Touch Cruise Android Development] briggs81:
I was on the lite version, but it's slower then the latest 1.5, and I don't see the point of it really, unless I am missing some things. I just see the the new "peep" app.
[Touch Cruise Android Development] briggs81:
Just wanted to throw this in here in case some of you didn't know about it.

Just a mortscript that asks if you if you want to launch android when you load up windows. you either press yes or no. if you press yes, it is suppose to start your data connection, then by default wait 5 seconds and automatically runs the haret app.

You need to install the mortscript cab and then put that mortscript file in your "startup" folder in your windows folder.

http://xdaforums.com/showpost.php?p=3713398&postcount=3442

would be cool if it could be modified to just run android automatiically and not ask about windows!

EDIT: haha. Actually that's a bad idea. I modified the script so it starts automatically, if i ever need windows I am screwed as it will just force me into android. But you can get out of that problem by just removing your sd card, then it can't load up android, then putting it back in after 30 seconds or so. perfect! if anyone wants it, i'll attach it, otherwise i suggest using the one above that asks you if you want to launch android or not.
[Touch Cruise Android Development] bally3:
Tried the new intird and cant get a data connection anymore. normally when you click connect in Modem, it connects and gives you ip address details. On this one it just says "done" but when you doesnt give any access.

How was it on yours Jesse?
[Touch Cruise Android Development] vilord:
wow... my phone is roasty toasty hot... this must be what y'all are talking about... i wonder why its doing this?

FYI new initrd is up on the google code page that should have complete data stuff and maybe fixes briggs' sms problem?

I'm going to want some new modem logs from someone with a phone with no outgoing calls bug.
[Touch Cruise Android Development] life02:
Data connection is working great for me here in the USA on ATT. Even reconnecting after it drops (been traveling a lot today throughout rural america... lol). Thanks Jessie!

It only gets hot for me with bg sync on. The only thing not working right for me is SMS in... I'll try to look at it with ya tonight.
[Touch Cruise Android Development] life02:
Strange... it's working fine on my NK hero themed built but is wrong on the mssmison theme build I tried.
[Touch Cruise Android Development] vilord:
life02, did you try the latest from 2pm your time today, or the one from early this morning? SMS in should hopefully be fixed...
[Touch Cruise Android Development] life02:
the one from this morning... just grabbed the new one... will let you know
[Touch Cruise Android Development] meknb:
Was the same for me to ??Then tried in windows same results off by miles about 15 miles off restarted gps in windows then all ok in android? seems ok now with mssmison build.??
[Touch Cruise Android Development] life02:
SMS IN is now working! You Rock Jessie!

Edit: Lost network connection and now it won't pick back up even after multiple disconnects and connects. Any Ideas?
[Touch Cruise Android Development] briggs81:
I will give it a try tomorrow and hopefully get some logs if it does not work.

edit: just gave it a shot. data connection does not automatically start and just hangs on "starting pppd". Text messages still don't go out :(
[Touch Cruise Android Development] briggs81:
I must be having all the bad luck! lol.. all of a sudden nothing works for me! I think I will go back to the initrd from a few days ago, 3rd one back or something.
[Touch Cruise Android Development] vilord:
yeah your sim card really screws with things... i'll need some new logs to find out what went wrong...
[Touch Cruise Android Development] bally3:
Ask not what your dev can do but what you can do for the good of all yer devices..

thought of the day:

You know what I really love about this Android development is that whilst with WinMo we were all divided with our devices and roms, With Android we have achieved the opposite, just looking at the Kaiser, Vogue and Polaris Android threads, where devs post on numerous occasions what they have fixed with the GSM stuff that will make things better on all devices or the latest initrd and how it affects all these devices. I love it, we're slowly getting to that point where other people care about other devices they dont own - and this all came from these wonderful devs who cared enough to help other device users enjoy Android.

I now find myself now posting solutions in Vogue and Kaiser threads and I no longer feel like an intruder on the thread, rather a collaberator - great isnt it? :)

I encourage you all to adopt the same attitude - I know many already do - and try and help out on other device threads when you can or other devices struggling with getting Android running, its the best way to honour our devs who continually amaze us not just with their knowledge, but their patience, tolerance and eagerness to teach and share that knowledge for the better of all our devices.

<yes ok, I can hear an anthem being played somewhere myself with that mushy speech, but as they say in the time honoured fashion of xdevs - MEH!)
[Touch Cruise Android Development] briggs81:
Ok I tested the latest initrd from google code

can't make calls, can't send sms.

Can receive sms, can use data.

Didnt test receiving calls but i probably can, if i make a call in winmo first.

The files are on issue 11, google code site
[Touch Cruise Android Development] :
They were the most updated listed in the repository... at that time may be they were from 29.... I just posted the logs with this version and also with initrd from 31.

BTW, it has been quite complicated to followup on the versions... it seems also some files are being removed from repository...

Please let me know if you would like some more tests..

JM
[Touch Cruise Android Development] radem205:
The new files from Zenulator are working pretty great. Sometimes it's a bit slow, but it's great to see Hero on the Polaris. The only issue I have is that I don't get a data connection (no modem.apk installed :s).
[Touch Cruise Android Development] Mormy:
I don't know if could be useful, but I try to boot up the hero pack from Zenulator. First the BeckInBlack (lite) and then the full.

I used all the file from his repository and a SD without data inside.

It take quite a long time to make first boot and it is really slow :(

I set my apn inside android, but I can't surf the web or look at the weather.

I could make and receive calls and this is the good news.

My default.txt is:

#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# ppp.nostart	- Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 1=Hitachi 2=Topoly 3=Samsung
# clock-7x00.mddi - MDDI clock (try 0xa51 or 0xe2c)
# clock-7x00.ahb_div - Advanced Host Bus divider, default is 4
# 2 is faster but uses more power
# clock-7x00.a11 - ARM11 clock speed in MHz, best to leave this alone
# lcd.density - Defaults to 160, 128 shows more on screen
# vogue-ts.XMIN - xmin value for the touchscreen calibration. Also YMIN, XMAX, YMAX, PMIN, PMAX.
#
# Probably the only one of these you will need to change is the panel type, NZ Vogues seem to all have type 1
# US Sprint vogues usually have type 2 or 3 I think.
# Make sure you add these between the quotes on the following line and that your editor hasn't split the line up.
set cmdline "mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=1 board-htcpolaris.panel_type=0 no_console_suspend board-htcpolaris-battery.battery_capacity=1350"
boot
[Touch Cruise Android Development] briggs81:
Browser would work but nothing else would, date wise, with zen's stuff. Oh well :P

edit: it is actually a lot faster, but data is still being weird. can use a browser, setup setup sync/calendar/gmail/etc, but sending email is out of the question, just stalls on "sending" and it won't sync when i tell it to, and actually it loses the connection quite often and can't do anything. It also does not want to remember that I am always roaming, and to always start the internet connection.

I changed initrds to an older one and it seems to be working better, but its still an initrd that does not let me send sms.. lol
[Touch Cruise Android Development] briggs81:
Vilord,

I believe initrd-2009-07-31.gz and 2009-07-31.gz worked for me, sms and auto connect data. (And for anyone trying hero, i tried 2009-07-31 initrd and it does not work with Zen's hero build, just gives a black screen, and the initrd supplied in the package seems to not giving me constant data connection. I switched to an earlier one, which one I don't remember now, because i have so many frigging intrd files around.)

I tried the 2009-08-01 and thats when sms stopped working for me. and pretty much anythign after that i think won't work either, sms at least.
[Touch Cruise Android Development] 188236:
SWAP on SD

I installed the two new files, which create a swap file on the SD-card. I guess there IS an advantage concerning speed, but could someone explain to me what EXACTLY the advantage is? I can't see one regarding acceleration...
[Touch Cruise Android Development] vilord:
It is primarily an advantage if there are background processes that use memory but aren't active all the time. It will swap their memory out to the SD and free up memory on the device for other things. I've found that the home screen is much snappier now when I have widgets and I go into something big, like copilot, then switch back.

The other MAJOR change with the two files is that it used to be that everything was in initrd, and all the files were constantly stored in RAM, wasting about 8 megs on a memory starved device... now initrd gets unloaded and we can use that extra RAM.

The problem is that I really killed off SMS... but I'm about 90% to getting it working... and I've added support for about 20 or 30 additional RIL functions, thanks to a team at TI that released code for the OMAP RIL... about 10 hours of merging and we'll be able to do a lot more, like I think SIM STK might soon be supported (if anyone knows what that is)

EDIT: Oh yeah, and I fixed signal strength reporting to use less power (it won't keep asking for the signal strength when the screen is off)... should get us an extra few minutes at least, maybe significantly more (haven't done a before/after test)... should have that change posted tonight in addition to the SMS fix, and maybe support to work with Zenulator's build
[Touch Cruise Android Development] imfloflo:
Very good job with this release @Vilord
[Touch Cruise Android Development] vilord:
isn't it nice you can now just remount,rw the rootfs and change whatever you like? I'm really happy that it works that way now... And I can change the init script to look for something in BackInBlack... what do you suggest? Maybe one of the files in /system/framework?
[Touch Cruise Android Development] Septavius:
Actually I changed the rootfs on my Linux box, but being able to modify the rootfs from the phone is a really nice bonus :).

I guess Zenulator could give you a more definite answer than me, but the file I am using is "/system/framework/com.htc.framework.jar".
[Touch Cruise Android Development] imfloflo:
@vilord i think you should take contact with some G1devs like justanotherdev,twisteumbrella,cyanogen or drizzy to get all their init optimisation and try to apply it to your init script
[Touch Cruise Android Development] vilord:
Agreed, just not sure the best way to do it... i wonder if they ever end up on IRC, as going through PM really isn't idea....

For ringtones and notifications etc, i think you just put it in /sdcard/ringtones and /sdcard/notifications etc... just move everything from the media folder to the root (although i haven't tried it yet, i'm still on nkhero)
[Touch Cruise Android Development] bally3:
Eeryones obsession appears to be sticking with the hero builds, I was initially intrigued too, just to see it working but frankly I just want to get back onto the kernel stuff again.

Testing hero builds can be fun for a while, especially when theres a lull in the development, but I hope this doesnt continue for too long. We have a long way to go yet and its looking like theres less and less people involved in the kernel these days.

Can we move the build conversations to the testing and reporting thread please? I know I'm just as guilty here, but we should try and keep it kernel related here.

Besides, both mssmisson and zenulator have dedicated threads for their builds.

Thanks.
[Touch Cruise Android Development] imfloflo:
@vilord try PM or their twitter they all have an account. I think they will help you.

They allready help each other to make better rom.
[Touch Cruise Android Development] bally3:
I now permanently seem to have this thread, vilords ION thread, dzo's thread and the kaiser thread open at all times. refreshing and checking new posts.

Whilst I admit I like reading the posts, its often confusing who is working on what and where they've got to. Recently someone mentioned that I should keep an eye on the android room on irc and also on linuxtogo (quite a good resource for this) then there's the vogue-android room... you can see where it starts to get a bit confusing!

I was wondering whether there exists somewhere, either in the wiki or threads, a breakdown of who is working on what kernel-wise?

I hear mention for example that enatefox and few devs are working on the wifi, this I get from the odd posts in the Kaiser thread, but it would be nice if that info was collated somewhere to keep up with progress.

An ideas anyone?
[Touch Cruise Android Development] bally3:
RE: my post about kernel related discussions here, all future non kernel development related posts may be moved by imfloflo to the bug testing and reporting thread. Just giving you a heads up if you find your post has disappeared.

No offense intended, just trying to keep everything organised and manageable. :)
[Touch Cruise Android Development] vilord:
Thank you for that...

So with the new initrd/rootfs what have people's experiences been? I hear there are SMS issues with some carriers (the same ones with outgoing calls issues)
[Touch Cruise Android Development] life02:
New high score in neocore... 23.0 FPS!!! Will post a new kernel shortly. Martin (dzo) helped me finish fixing the vsync stuff.

Please Donate to him for this accomplishment. I was just the monkey behind the wheel following his instructions. He said he would be interesting in helping with Polaris development if he received enough donations to purchase one.
[Touch Cruise Android Development] Leryan:
WOW, can't wait to try :)
[Touch Cruise Android Development] life02:
Here's the testing zImage.

Unzip and enjoy. (That's what she said!... sorry... it's late)
[Touch Cruise Android Development] vilord:
Okay, posted another rootfs, this one has a huge number of GSM commands added, and as usual my setup is somewhat limited, ie I have no SIM STK hardware at all, but I threw it in there and hopefully it'll work :)

Initialization functions changed significantly as well.

I've been having trouble with SMS messages out getting blocked *sometimes*, and haven't fully tracked it down, but I'll throw it out there anyways to see if anyone else has better or worse experiences with it. Who knows, maybe it fixes dial-out :)
[Touch Cruise Android Development] Michel82:
Whoohoo! An astounding 22.6 FPS in neocore. Feels much smoother... if we can also implement the swap stuff my pola will be flying.
[Touch Cruise Android Development] imfloflo:
I will move all posts related to Hero builds in http://xdaforums.com/showthread.php?t=473102 to keep this thread clean to the Kernel. ;)

ps: We already running android from our SD card, if we add a ext3 partition and a swap partition our SD card will die in 1 year with all this access but if this is the price to have a speed build.
[Touch Cruise Android Development] vilord:
we're staying away from ext3, as that will definitely kill the card fast (far less than a year). My understanding is that swap may slowly kill the card, but the writes *shouldn't* be as extreme.

And for those who tried the rootfs from 2 hours ago, instead of going to bed I fixed the SMS sending issue I was having... not sure if anyone else was experiencing it, but it would simply fail to send. Unrelated to the error message in hero... so another new rootfs, just updates to fix SMS.
[Touch Cruise Android Development] radem205:
Thank you for your work Vilord!! But unfortunatly sms isn't working now (I get a message that the sms wasn't sended and the receiver didn't received the sms). In and outgoing calls are working fine (has worked always fine).

Also data connection isn't working with the files of zenulators' builds. Do you guys have a working data connection with these builds?

I get the 3G icon in top of the screen but it wouldn't connect :(

Great job Dzo and Life02. It's working quite smooth now (zenulators' build)!