yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
That could be the problem right there. Try a more updated ROM. 6.1 or 6.5.
[Tilt, TyTN II, MDA Vario III Android Development] chinomoreno:
i never flashed a rom bahh well i have to learn i dont want to mess with warranty but if this is needed let's do it ;P i ll search for a how to, if anyone knows a good one and tips about what rom to use etc.. pm me thx o/
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
Hey Natalic, I just booted the build you posted and all seems good accept, I cannot get a data connection. Tells me the sim isn't provisioned for data services. On the first Hero build posted I could get data np. Is there something I need to do? :confused:

Another thing I noticed is when I go to settings and turn data on it says it is on but I never get the 3G symbol at the top. Also, every time I try to add a clock and a city it crashes the clock app.
[Tilt, TyTN II, MDA Vario III Android Development] momo254:
be patient, it takes a while. Once it took almost 5 minutes for my phone to boot hero the first time
[Tilt, TyTN II, MDA Vario III Android Development] natalic:
Make sure you setup the APN and connect the modem.
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
Well, modem says it's connected, I'll look into the APN, thanks. ;)

Could lack of data access be why the clock crashes? Need data to find your city I assume.

That did it bro, thanks a bunch. :D

Still won't let me add a clock with a selected city, it just crashes, I tried adding a clock with the default "selected city" and briefly saw an error about Touchflo being unhappy and now my SenseUI is gone. :(
[Tilt, TyTN II, MDA Vario III Android Development] chinomoreno:
yeah i know i already tried more then 30m but once it goes to stand by and the screen goes black is over i think... the HTC bright effect stops just before stand by.. if i press power button the screen turn on but HTC isn't with that initial bright so i guess is really weird, i have tried all the "fixes" for the problems on this post and other posts.... o/
[Tilt, TyTN II, MDA Vario III Android Development] momo254:
I tried this build and sms is not working :(
[Tilt, TyTN II, MDA Vario III Android Development] xxbabiboi228xx:
Hero Build Dialer

Does anybody have any idea in these hero build why the persons picture nor name showing up when making or recieving calls? Can it be fixed ?
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
SMS works for me but I get the notification bug.

From what I can tell, there is no way to set an alarm in this build. :( and the digital clock with built in weather doesn't seem to function either.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Bear in mind you are using a closed-source proprietary system on the open source version of Android. I'm looking into an interface that should let them talk to each other. The reasons you think Hero is better than your family and pets is also the reason that it is seperate from the normal Android system. Just in case you were thinking these were bugs with the build. Give us some time but meanwhile, Hero is running very nice for me.
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
I'm not *****ing by any means. Just pointing out things I notice on the different builds. I am amazed by the progress so far. It seems each build has it own quirks. The one natalic posted seems pretty close to being a full package. If it had alarm functionality I would use it as my primary OS. Whomever is putting all the work into this it's greatly appreciated. Can't wait to see what you guys do next. ;) My biggest problem with the Hero builds so far is, 90% of my calls go to voicemail. :(
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
I'm just saying that's where we're at with porting. The issues that most people are reporting are related to the fact that Hero has its own notifications, alarms, contacts, etc. Everything that makes it as nice as it is. They don't inherently work with the open source version we are primarily using. I just don't want people surprised when that stuff doesn't work. My calls are going through. Some report they have to call out first. Not for me though. Could be a radio issue and should be reported correctly. You can always do a log dump of your radio and it will help us all out.
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
I tried a few different radios with similar results. I just had my wife call me 3x. Out of those, only one went through, the others went to VM. I did not have to call her first but, have experienced that. Tell me how to log dump the radio and where to send it and I'll help any way I can. I would like to see this work as much as you guys. It's the coolest thing I've had on my phone by far.

I think I am using radio 1.71.09.01 ATM.

Am I correct on the alarms being taken out of the latest build? So, I can stop looking for them. ;)

The first build I tried ran sweet but, I had the call bug (no incoming unless I called first). Everything else worked fine out the box. Data, alarms, notifications and texts (without the message not sent bug). The more resent ones seem to have introduced new issues but, Wifi works. Looking at this from a user and not a developer standpoint, I'd have to say you guys are really close to a fully functional build. As far as any Android build I've tried.

Just thought of something, the last time I tried powering off the Hero build it froze up on me. First time that ever happened and all that was connected was the phone, everything else was off (Data/Wifi).
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
logcat -b radio -f /sdcard/radiolog.txt

then disconnect twice in modem, then wait 'till the network comes up and try to make or receive a call. You'll have the output in your SD card's radiolog.txt file. You might want to double check that there's no personal info in it.
[Tilt, TyTN II, MDA Vario III Android Development] 2girls1cup:
i came across a touchflo disabler somewhere in the forums and was wondering if anyone had seen it because im looking for it. touchflo error keeps popping up and I think I need that disabler.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Zenulator uploaded it if you can't find it elsewhere. Sauce: http://vogue-hero.googlecode.com/files/ymst.android.homeswitcher.apk
[Tilt, TyTN II, MDA Vario III Android Development] 2girls1cup:
thanks enatefox you are such a big help bro. are you getting payed or something for this cuz wow you have good feedback.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
I'm waiting for answers on my own issues. That means my F5 key is worn out completely... while I wait, I got all these threads open in tabs.. it's no problem really. Just on xda and 4chan mostly
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
I assume that is done in terminal. I will do that now and get back to you.

I just did some more testing and had the 'ole lady call, it went through but, I could not hang up. She ended the call but mine kept going AND we had no audio at all. I am so bummed ATM, I want this to work so, let me know what I can do and I will. When I booted to Hero again it showed the call that it showed as being connected to as a missed call.
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
double post, sry...
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
I used to be like you. Lately, things have worked perfectly. I had issues where it would take 2-3 rings to be able to answer but I'm averaging 80Mb of free memory and those days are over. I have 8-15 Hero system.img with wifi and 8-15 everything else. Compcache and 60Mb swap. Calls come through. Tell me what's up with the logcat function (yes, that's a terminal command)
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
unable to open log device "/dev/log/radio": Permission denied

It created the file but it has nothing in it. :(
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Yup, you have Zen's original system.img. My repack for wifi included su access. You can easily bypass this by doing:

/bin/su
logcat -b radio -f /sdcard/radiolog.txt
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
OK, Thanks.:p I'm booting the Super Hero build ATM with the calibration/default files from the newer build just to see what happens. I will boot the other build in a few and get you that log file. ;)
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
8-15 has worked very well for me. SuperHero lagged enough that I tried Pure Black and that made me go back to 8-15 again. Since, not a single issue with calls. I will say though, my radio is old enough that GPS doesn't work with it. I really couldn't care less about that but it should indicate that the radio might be a factor with receiving calls (that is what the logcat script checks anyways). You might want to consider updating to the newest radio and see if that makes a difference for you. Personally, Android is like it was preinstalled for my phone.
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
Seems I have the latest Kaiser radio. Super Hero build was far to slow on my phone and Wifi didn't work. I am going to go back to what I sort of had working a minute ago. I was making and receiving calls after toggling the modem on/off a couple of times. I will get you that log file in a second. Thanks for your input. :)

Any way you could zip your current set up and post it?
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
rootfs that I manually engage swap with. You could just use this to get the same effect: rootfs with 8-8-9 files and 8-15's system.img from Zenulator that I modded to have wifi for Kaiser.

I recommend Pure Black:

this rootfs.img

this system.img

and the rest from here
[Tilt, TyTN II, MDA Vario III Android Development] Biglittlewhateva:
Thanks allot, Ima try it now :D

Looking at the files I'm downloading I realized something, I have a fully functional Android (same release) with data/wifi, works fine. What do I add to give it the Hero interface?

When I put those files all together it loops between the hero/htc splash screens and that's all it does. :P
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
system.img. need a new data.img if you swap system.img though. I use one that's 256Mb and I think it's faster than 128Mb
[Tilt, TyTN II, MDA Vario III Android Development] natalic:
You have a better system.img for PureBlack? Or is the one in my package good? I don't want people using old stuff (that was the only one I could find). I am more into ION.

Also, whats the difference between Hero and Ion?

Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
The one I posted just had wifi added for Kaiser, SuperUser was fixed and I disabled the startup sound. When I said 256Mb I was referring to the size of my data.img. I have a lot of apps, 128 doesn't cut it.

ION is a Cupcake style closed-source version of Android. Hero is HTC's version, proprietary so beyond closed source, with a gussied up interface and a plethora of new features 2 years in the making so far.
[Tilt, TyTN II, MDA Vario III Android Development] LordPhong:
for some reason, I can't get any of the HTC clock to work with this build. i get:

The applications Clock widget (process com.htc.widget.clckwidget) has stopped unexpectedly. Please try again.
[Tilt, TyTN II, MDA Vario III Android Development] ljinsane:
Downloading now....which hero build is this based off of?
[Tilt, TyTN II, MDA Vario III Android Development] natalic:
PureBlack by Zen.
[Tilt, TyTN II, MDA Vario III Android Development] ljinsane:
OK, cool that's the build I am currently running.
[Tilt, TyTN II, MDA Vario III Android Development] mcfarlan:
I also had the same problem. Even though I had the correct APN settings entered, it was not establishing a network connection.
[Tilt, TyTN II, MDA Vario III Android Development] xxbabiboi228xx:
Thats the same prob i had with the clocks on pure black i would run that version but for that reason im not so im running the super hero build
[Tilt, TyTN II, MDA Vario III Android Development] LordPhong:
I'm with tmo and the data is working fine for me. I made sure that the user/pswd is completely empty.
[Tilt, TyTN II, MDA Vario III Android Development] mantorp:
Wired headset

In lieu of bluetooth I could get by with the wired headset working. Does anyone know how to do that? I got a dongle thing that came with my Tilt from AT&T that accepts normal headphones.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
mantorp, that should be working. It was patched back in May I believe but I hadn't tested it recently. If not, it shouldn't be too hard to put back.
[Tilt, TyTN II, MDA Vario III Android Development] mantorp:
Wired headset

Thanks for the quick reply, once you confirmed it should be working I just unplugged it and plugged it in again a few times and it worked eventually. FYI I'm using everything from the RAR file natalic posted.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
There was at one point an issue where a running app would not refresh the output so you'd have to close and reopen it with either it plugged in or not to switch back and forth.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
@enatefox can you give specifics on your phone Model, Rom, Radio etc... the only build I can get working is the one you released last week or so, I am trying to get pure black to boot but it is stuck in a loop I am using the newest zImage, rootfs with compcache and swapfile, initrd from your build

here is mine

ROM HD IOLITE

RADIO 1.65.24.36

Kaiser110/ATT Tilt

I am getting somewhat frustrated I have the default.txt set correctly I think same one I been using for several builds now
[Tilt, TyTN II, MDA Vario III Android Development] pmos69:
Check you deleted data.img and that you have the correct resolution (320x480) in default.txt.

Those are the 2 most common causes for the loop.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
agreed. I've never had an issue with booting a build unless I screwed up. I have my default.txt with 320x480 and delete data.img any time I change system.img.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
As I am very religious at doing this as well I have tried a couple different roms I am In the process of trying a TPC 6.5 winmo ROM right now but usuall can only get hyperdragon IOLITE to boot any android well Maybe its just my phone then

Well in the middle of typing all this it booted with TPC Rom
[Tilt, TyTN II, MDA Vario III Android Development] FloatingFatMan:
What radio and WM OS version are you using?
[Tilt, TyTN II, MDA Vario III Android Development] lpri:
can any one tell me y i cant get voice on my calls sim is in the slot but it says no sim
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
Well after going through the normal routine of changing settings to my likings pure black is a no go for me. The biggest killer is no alarm clock the one I belive that was removed. I tried a couple from the market but they did not fit my needs. I still believe that the hybrid enate did is the best android build going. The one thing I have noticed from all the recent builds is when I want to use delete on the keyboard it doesn't work backspace does though.
[Tilt, TyTN II, MDA Vario III Android Development] madshiva:
Dear all,

The problem of the logo that reboot over, was solved by flashing the rom.

I had the version Windows Mobile 6.0 with radio 1.26 ~.

Now I have version Windows Mobile 6.1 with radio 1.65 ~.

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] svenn0508:
I have tried so many Hero builds on my Kaiser already and was no able to find one working great for me. Each one has something missing.

Things I need to work flawlessly are listed below, the rest is not important.

Normal battery life

Calls - send/receive

SMS/MMS - send/receive

GPS

WiFi - other data connection not needed

Music player

Alarm clock

Camera - only back, front I don't use

Sync with PC via USB would be great, but can live without

If anyone knows a built that has all things listed working without a problem, pls advise.

Rom D3 By Josh

Radio 1.65.24.36

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] FloatingFatMan:
Of all those, it's only really the Camera and PC Sync which isn't working. Though I'm not sure on MMS as haven't tried it.

You can improve battery life by turning location services and background data transfer OFF, especially the automatic syncing.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
svenn0508, when did 2-8 hours battery life seem like less than WM6? This was the best phone I could upgrade to with ATT (inb4 "lolz iphone rulz") and it said the battery life was 2 hours of talk time.

calls work for me (6.1 AthineOS ROM, old 1.65 radio), GPS would work if I updated my radio and cared, wifi is a-workin', SMS seems to work if you don't mind the false error for now, music player... they have those-- get Ambient, alarm clock-- if Hero doesn't then deal with ION's for now, camera works on Vogue so wait a little for Kaiser and syncing works with ADB. And bluetooth is coming too

FloatingFatMan, do you have a Kaiser? You've asked about other phones a couple of times. Just wondering if these are running right on other models
[Tilt, TyTN II, MDA Vario III Android Development] FloatingFatMan:
I have several phones (see my sig).. It runs reasonably well on the Kaiser, but won't run at all on any of the others. HARET just crashes out on me with the error:

"Terminating haret due to unhandled exception (pc=00fd5640)"

Mind you, they're mostly based on Samsung processors (except the one that's giving that particular error, that's an MSM7225 processor - The others have varying different errors), so its likely to be a start from scratch job to get it working on those.

Oh, for a generic image that runs on all things, even if some features don't work like the camera, wifi and BT... ;) A generic image that just lets you use the phone that'll run on any ARM would be nice... :p
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
I would love to find a way to sandbox Android in a Linux environment, basically extending the minimal one Haret loads. The joy of Android on hardware is its compatibility like how there's not just an x86 version but a live CD of it as well. Oh to dream.. without owning a Dream of course
[Tilt, TyTN II, MDA Vario III Android Development] svenn0508:
Ok, I have finally managed to make a working combination for my Kaiser and am running quite good Hero with everything except camera and Bluetooth working - and sms failure report - but will live with it for now.

But just found out one strange problem which is a bit annoying - my TouchFlo home screen reloads each time I leave some app and want to go back home.

It takes 30sec to 1min and in that time my phone is non-responsive.

Also in this period my call go to VM and not able to receive text...

Can anyone help? I like the TouchFlo, but this is starting to bug me real good...

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] FloatingFatMan:
Yeah. I've been getting that too, it's really annoying but I think I know what's going on.

Android us unloading the SenseUI elements when using other programs as it's running low on RAM. Once that program is closed, Android reloads the SenseUI. There's probably not a lot we can do about it as the Kaiser's just don't have a lot of RAM...
[Tilt, TyTN II, MDA Vario III Android Development] xxbabiboi228xx:
which Hero build are you guys running cause it was happening to me to but i switched kernel and system image kernel addisu which is the Zimage and zenulators System Kaiser wifi2 now it actually lets me answer the call instead of going straight to voicemail with one quick ring.Was running the

8-19-09 Zimage and SuperHero Build wifi
[Tilt, TyTN II, MDA Vario III Android Development] FloatingFatMan:
I'm running the version from pmos69's post on the 17th.
[Tilt, TyTN II, MDA Vario III Android Development] mustafa885:
Calls Disconnect Immediately

When ever I try to make a phone call it disconnects immediately after connection. Any help? Thanks

Regards
[Tilt, TyTN II, MDA Vario III Android Development] pmos69:
You can use this: http://vogue-hero.googlecode.com/files/rootfs-compcache-swap-2009-08-16.zip to automatically give you an swap file and try to avoid android doing too much "housecleaning" (unloading programs like sense-ui when memory gets too low).

Zenulator will put up a new rootfs with backing store support in a day or so, and that should give even better results. (it does in my case)

also change zImage to http://vogue-android.googlecode.com/files/zImage-18-08-09

(well, it's the one I'm using atm, and it's working ok)
[Tilt, TyTN II, MDA Vario III Android Development] FloatingFatMan:
That runs MUCH smoother, thanks pmos69! :)
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Just to keep things consistent for those that aren't thread hopping and having issues with lag and Touchflo reloading:

As of last night, when someone was complaining about swap issues, I ran "free" in the terminal and got:

Mem: [98816] [97068] [1748]

Swap: [86128] [42904] [43224]

Total: [184944] [139972] [44972]

Over 42Mb of data swapped and a little more than that available just from swap (60Mb total) and compache making up the difference. Needless to say, Rosie doesn't "reload" it just appears and then the clock slides around in it's glorious manner. Whether it was just sleeping or I hit back a bunch of times in a full screen app.

You might want to try to force a swap. There's an "effective memory" which is less than available memory. It's the point at which Android decides it needs to swap to make room for the next activity. Once you've built up swap a bit, it will run fast. Don't expect 2Mb of used swap to make a fast system.
[Tilt, TyTN II, MDA Vario III Android Development] pmos69:
Enatefox,

There are some flaws in your explanation:

You need to see the whole picture.

Here's the current stats from my phone: (no lag or TF reloading also)

$free
total used free shared buffers
Mem: 98816 97392 1424 0 80
Swap: 104824 43504 61320
Total: 203640 140896 62744

As you can see, about the same memory usage as you.

In my case, I'm using a backing store for compcache:

$ cat /proc/swaps
FilenameType Size Used Priority
/dev/block/ramzswap0 partition 104824 43420 -1

But now you need to see the compache stats to get the complete picture:

$ cat /proc/ramzswap
DiskSize: 104832 kB
MemLimit: 14820 kB
NumReads: 34546
NumWrites: 16107
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 712
GoodCompress: 100 %
NoCompress: 0 %
PagesStored: 10789
PagesUsed: 2824
OrigDataSize: 43156 kB
ComprDataSize: 11101 kB
MemUsedTotal: 11296 kB
BDevNumReads: 7335
BDevNumWrites: 3354

What this means is that compcache is handling 43156 kB of memory, which it has compressed into just 11101 kB.

Since compcache has 14820 kB of physical memory reserved for itself,

ALL

of the data you see in swap when you look at the output of free is still in memory, not in the swapfile/partition.

What the swapfile can be helping with, is delaying android in killing processes by telling android there's still more free memory available(it's total memory available that counts, not just physical memory available) so no need to start killing rosie, for example. If you didn't have the swapfile, that might happen.

When you load your system and are using less memory and things lag, that probably means not everything is loaded into memory, and has to be fetched from the flash. And that is very slow. Once everything is in memory (even if it is compressed memory) it all flows nicelly.

If you "overload" the system, loading more programs/whatever, you'll get to the point where things are in fact swapped to the swapfile partition, and you'll start noticing lag/freezes, etc.