Jump to content


CyanogenMod for HTC Hero (GSM) v1.0 (now with online kitchen)

* * * * * 1 votes

420 replies to this topic

#41
Blackfish

Blackfish

    Regular

  • Members
  • PipPip
  • 55 posts
  • Location:Zug, Switzerland
  • Devices:HTC Hero, Magic, HD2
Bug report (maybe you accept it)

Goggles crashes after creating a picture of my PC Screen (Goggles is not created for that but it still should not crash)
- I have camera resolution on 3 MP

And i still say it is laggy against other ROMs...if you like it or not...i can not give you additional informations...

Edited by Blackfish, 04 February 2010 - 11:10 PM.

Windows Mobile
Current: HTC HD2
HTC Touch HD - HTC Touch Pro
HTC Touch Diamond - HTC Touch Dual
Android
Current: Samsung Galaxy S
HTC Legend
HTC Hero - HTC Magic


#42
jnwhiteh

jnwhiteh

    Diehard

  • Members
  • PipPipPipPip
  • 363 posts
  • Location:Oxford, United Kingdom
  • Devices:HTC Hero
  • Twitter:@jnwhiteh

View PostBlackfish, on Feb 4 2010, 23:09, said:

Bug report (maybe you accept it)

Goggles crashes after creating a picture of my PC Screen (Goggles is not created for that but it still should not crash)
- I have camera resolution on 3 MP

3MP resolution does not work on this or any other AOSP based Hero 2.X ROM.  This is listed in the first post.

Quote

And i still say it is laggy against other ROMs...if you like it or not...i can not give you additional informations...

Then feel free to use another ROM.  Thanks for your feedback.

AOSP-Eclair-jnwhiteh: http://tinyurl.com/aosp-eclair-hero
If you like my work, I like beer

#43
thecastlefordkid

thecastlefordkid

    Newbie

  • Members
  • Pip
  • 31 posts
  • Devices:HTC Hero
Nice ROM. Very impressed with it so far (only downloaded and flashed it a short while ago). Will post you some feedback once I've used it for a while

HTC Hero on Orange UK
ROM - MCR 3.2 Beta 5 Custom Custom ROM
Radio - 63.18.55.06JH_6.35.09.26

#44
Blackfish

Blackfish

    Regular

  • Members
  • PipPip
  • 55 posts
  • Location:Zug, Switzerland
  • Devices:HTC Hero, Magic, HD2

Quote

3MP resolution does not work on this or any other AOSP based Hero 2.X ROM. This is listed in the first post.
Also on 2 MP and with 1 MP...

Windows Mobile
Current: HTC HD2
HTC Touch HD - HTC Touch Pro
HTC Touch Diamond - HTC Touch Dual
Android
Current: Samsung Galaxy S
HTC Legend
HTC Hero - HTC Magic


#45
jnwhiteh

jnwhiteh

    Diehard

  • Members
  • PipPipPipPip
  • 363 posts
  • Location:Oxford, United Kingdom
  • Devices:HTC Hero
  • Twitter:@jnwhiteh

View PostBlackfish, on Feb 4 2010, 23:15, said:

Also on 2 MP and with 1 MP...

Once the application has 'broken' I dont think any of them will work. You should not experience that on a reboot.

AOSP-Eclair-jnwhiteh: http://tinyurl.com/aosp-eclair-hero
If you like my work, I like beer

#46
jnwhiteh

jnwhiteh

    Diehard

  • Members
  • PipPipPipPip
  • 363 posts
  • Location:Oxford, United Kingdom
  • Devices:HTC Hero
  • Twitter:@jnwhiteh
It appears that Goggles indeed does crash, but that seems to be independent of the picture-taking.  It's crashing with the following:

W/dalvikvm( 2867): No implementation found for native Lcom/google/android/apps/unveil/env/ImageUtils;.computeEdgeBitmap (II[B[B)V

I'll try to look into it.  It's likely the library that I left out of the google-bits because I had no idea what it did.  I'm not sure if I can just include it directly.

Edited by jnwhiteh, 04 February 2010 - 11:20 PM.

AOSP-Eclair-jnwhiteh: http://tinyurl.com/aosp-eclair-hero
If you like my work, I like beer

#47
JamesKing

JamesKing

    Regular

  • Members
  • PipPip
  • 75 posts
  • Devices:HTC Hero
Ignore this.  Either you've updated the first post since I read your post an hour ago, or I missed it the first time ;)

Edited by JamesKing, 04 February 2010 - 11:31 PM.


#48
jnwhiteh

jnwhiteh

    Diehard

  • Members
  • PipPipPipPip
  • 363 posts
  • Location:Oxford, United Kingdom
  • Devices:HTC Hero
  • Twitter:@jnwhiteh

View PostJamesKing, on Feb 4 2010, 23:30, said:

I haven't installed the ROM yet, but here's some feedback ;)

I've read the whole thread and seen your discussion with blackfish.

It is not clear from the first post that the "default" or "pre-installed" live wallpapers don't work.  Perhaps that should be mentioned :D

It's been rewritten, and I feel it's relatively clear at this point, in the known issues section.  Do you not agree?  Specifically considering that some of the default ones do work =).

Edited by jnwhiteh, 04 February 2010 - 11:31 PM.

AOSP-Eclair-jnwhiteh: http://tinyurl.com/aosp-eclair-hero
If you like my work, I like beer

#49
Blackfish

Blackfish

    Regular

  • Members
  • PipPip
  • 55 posts
  • Location:Zug, Switzerland
  • Devices:HTC Hero, Magic, HD2

Quote

It is not clear from the first post that the "default" or "pre-installed" live wallpapers don't work. Perhaps that should be mentioned

Quote

Some of the stock live wallpapers do not work properly, likely due to issues with video RAM and the renderscript library. I would suggest you use wallpapers from the market, simply search for 'live wallpapers'
He has added that information
Edit: To slow

Edited by Blackfish, 04 February 2010 - 11:31 PM.

Windows Mobile
Current: HTC HD2
HTC Touch HD - HTC Touch Pro
HTC Touch Diamond - HTC Touch Dual
Android
Current: Samsung Galaxy S
HTC Legend
HTC Hero - HTC Magic


#50
JamesKing

JamesKing

    Regular

  • Members
  • PipPip
  • 75 posts
  • Devices:HTC Hero

View Postjnwhiteh, on Feb 4 2010, 23:30, said:

It's been rewritten, and I feel it's relatively clear at this point, in the known issues section.  Do you not agree?  Specifically considering that some of the default ones do work =).
Yes.  Sorry.  What a remarkably quick answer!  I missed it and when I went back to double check I hadn't missed it I realised it's been re-written ;)


#51
jnwhiteh

jnwhiteh

    Diehard

  • Members
  • PipPipPipPip
  • 363 posts
  • Location:Oxford, United Kingdom
  • Devices:HTC Hero
  • Twitter:@jnwhiteh

View PostJamesKing, on Feb 4 2010, 23:32, said:

Yes.  Sorry.  What a remarkably quick answer!  I missed it and when I went back to double check I hadn't missed it I realised it's been re-written ;)

npnp =)  Going to bed now, see you all in the morning!

AOSP-Eclair-jnwhiteh: http://tinyurl.com/aosp-eclair-hero
If you like my work, I like beer

#52
commodoor

commodoor

    Enthusiast

  • Members
  • PipPipPip
  • 239 posts
  • Location:Venlo
  • Devices:Nexus One, HTC Desire
  • Twitter:@commodoor
Ok i just flashed it, and looks great. but the phone seems like a little slugish, i don't know maybe its only for me.

its slow with everything, scrolling down, pulling up the apps menu, etc etc. did i forget something?
i did a wipe, and wiped dalvik.


#53
DavidTJCXP

DavidTJCXP

    Newbie

  • Members
  • Pip
  • 10 posts

View Postjnwhiteh, on Feb 4 2010, 23:11, said:

Then feel free to use another ROM.  Thanks for your feedback.
Sorry, but I agree. This build, in fact any AOSP build, is laggy.

You can say otherwise, but it doesn't change the fact that they are slow. And yes, this is after giving several minutes to initialize, etc. I'm not a ''noob'' and have a few years of experience running Android on the Vogue and Hero now, this isn't a problem with anything I'm doing or with the phone.

Is it not true that AOSP releases lack certain drivers and OpenGL? I'm just throwing this out there, but perhaps that's the cause?

I've been told it's just me several times now, but I think a lot of you have to go and install a stock or vanilla Cupcake ROM again to truly experience the snappy and smooth Android experience, go back to an AOSP ROM and then tell me it's not laggy.

Again, I'm not trying to be an ass, and I truly appreciate the work you guys are putting into bringing Hero users the Eclair experience before HTC does, but people need to stop saying these ROMs are fast and lag free and that ''it's just you".


#54
winhhh

winhhh

    Newbie

  • Members
  • Pip
  • 7 posts
  • Devices:HTC Hero
When trying to run MetaMorph, I get this error;
It does not look like this phone has root access! the file: su could not be found

Any help ?


#55
stevenz

stevenz

    Diehard

  • MoDaCo Ad Free
  • PipPipPipPip
  • 455 posts
  • Gender:Male
  • Location:Wellington, New Zealand
  • Interests:Motorcycling
    Tinkering
  • Devices:Galaxy Tab, Galaxy S 2
  • Twitter:@KnightNZ
All you guys complaining about "lag" - do you just mean "not as snappy as MCR" or do you mean "slower than HTC Hero stock firmware"? Dunno if you remember, but that stock firmware is a complete dog.

Motorcycling watchmaker.

#56
keyra74

keyra74

    Regular

  • Members
  • PipPip
  • 88 posts
anyone can try reading a video with meridian for example and tell me if it stops after 2 seconds like on kagudroid


#57
arkhonic

arkhonic

    Newbie

  • Members
  • Pip
  • 10 posts
  • Devices:HTC Hero

View Poststevenz, on Feb 5 2010, 12:37, said:

All you guys complaining about "lag" - do you just mean "not as snappy as MCR" or do you mean "slower than HTC Hero stock firmware"? Dunno if you remember, but that stock firmware is a complete dog.

Agreed, this ROM is slower than Modaco but remember we don't have source code so no tweaks can be done. It is definitely useable and I have no issues as lag is really relative. Provided I don't get FC's I'm generally easily pleased.


#58
keyra74

keyra74

    Regular

  • Members
  • PipPip
  • 88 posts
videos close after 2 seconds like on every 2.1 aosp :/
same bug as with ckdroid 1.6 beta : market takes a while to refresh then shows a blank page, after being refreshed a few times it shows my download list

here's the error log

Quote

02-05 08:07:47.037: ERROR/vending(408): com.android.vending.InitializeMarketAction$MetadataAndDownloadsAction.abortOnServerError(): Server error in InitializeMarketAction:
02-05 08:07:47.037: ERROR/vending(408): java.net.SocketTimeoutException: The operation timed out
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.harmony.luni.platform.OSNetworkSystem.receiveStreamImpl(Native Method)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.harmony.luni.platform.OSNetworkSystem.receiveStream(OSNetworkSystem.j
va:478)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.harmony.luni.net.PlainSocketImpl.read(PlainSocketImpl.java:565)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.harmony.luni.net.SocketInputStream.read(SocketInputStream.java:87)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInp
tBuffer.java:103)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInput
uffer.java:191)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.
ava:82)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:1
4)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(Abstract
ttpClientConnection.java:179)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultC
ientConnection.java:235)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(Abstra
tClientConnAdapter.java:259)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecut
r.java:279)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:12
)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirecto
.java:410)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:5
5)
02-05 08:07:47.037: ERROR/vending(408):     at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:4
7)
02-05 08:07:47.037: ERROR/vending(408):     at android.net.http.AndroidHttpClient.execute(AndroidHttpClient.java:288)
02-05 08:07:47.037: ERROR/vending(408):     at com.google.android.net.GoogleHttpClient.executeWithoutRewriting(GoogleHttpClient
java:224)
02-05 08:07:47.037: ERROR/vending(408):     at com.google.android.net.GoogleHttpClient.execute(GoogleHttpClient.java:293)
02-05 08:07:47.037: ERROR/vending(408):     at com.android.vending.api.RequestDispatcher.performRequestsOverNetwork(RequestDisp
tcher.java:206)
02-05 08:07:47.037: ERROR/vending(408):     at com.android.vending.api.RequestDispatcher.performRequests(RequestDispatcher.java
174)
02-05 08:07:47.037: ERROR/vending(408):     at com.android.vending.api.RequestManager.doRequestsOverNetwork(RequestManager.java
244)
02-05 08:07:47.037: ERROR/vending(408):     at com.android.vending.api.RequestManager.doRequests(RequestManager.java:230)
02-05 08:07:47.037: ERROR/vending(408):     at com.android.vending.BaseActivity$BaseAction.run(BaseActivity.java:1601)
02-05 08:07:47.037: ERROR/vending(408):     at com.android.vending.BaseActivity$BaseAction$BackgroundThread$1.run(BaseActivity.java:1682)
02-05 08:07:47.037: ERROR/vending(408):     at java.lang.Thread.run(Thread.java:1096)

Edited by keyra74, 05 February 2010 - 07:13 AM.


#59
jnwhiteh

jnwhiteh

    Diehard

  • Members
  • PipPipPipPip
  • 363 posts
  • Location:Oxford, United Kingdom
  • Devices:HTC Hero
  • Twitter:@jnwhiteh

View Postcommodoor, on Feb 5 2010, 01:08, said:

Ok i just flashed it, and looks great. but the phone seems like a little slugish, i don't know maybe its only for me.

its slow with everything, scrolling down, pulling up the apps menu, etc etc. did i forget something?
i did a wipe, and wiped dalvik.

I appreciate that you consider it to be slow, but your experiences are not the majority.  Most people who try the ROM agree that it is very snappy and very responsive for most tasks.  Of course I will continue to try and improve the speed as best I can, but there it is.


View PostDavidTJCXP, on Feb 5 2010, 01:14, said:

Sorry, but I agree. This build, in fact any AOSP build, is laggy.

You can say otherwise, but it doesn't change the fact that they are slow. And yes, this is after giving several minutes to initialize, etc. I'm not a ''noob'' and have a few years of experience running Android on the Vogue and Hero now, this isn't a problem with anything I'm doing or with the phone.

Speed and lag is perception, not reality.  I don't think you're a noob.. but I'd be interested in what your adb logcat looks like when you're experiencing this lag.

Quote

Is it not true that AOSP releases lack certain drivers and OpenGL? I'm just throwing this out there, but perhaps that's the cause?

No, it's not true.  The phone gets 24 FPS on the OpenGL benchmarks and OpenGL ES works just fine.  Yes, we're using a leaked kernel and leaked drivers from an HTC build.. so of course we're at some disadvantage.  They may have compiled everything in debug mode, or who knows.  But that's not anything we can fix until they release a 2.1 ROM.. which given their speed may be after Duke Nukem Forever comes out.

Quote

I've been told it's just me several times now, but I think a lot of you have to go and install a stock or vanilla Cupcake ROM again to truly experience the snappy and smooth Android experience, go back to an AOSP ROM and then tell me it's not laggy.

Again, I'm not trying to be an ass, and I truly appreciate the work you guys are putting into bringing Hero users the Eclair experience before HTC does, but people need to stop saying these ROMs are fast and lag free and that ''it's just you".

I have installed cupcake ROMS.  I have installed donut ROMS.  I've been working on my HTC hero with stock HTC, AOSP and other custom builds for quite some time now.  The fact of the matter is speed and 'lag' is always perception.  It's a feeling and it is not a feeling shared by every single person.  I have two HTC heros sitting right here at my house, since my fiancé has the exact same phone and I can do side-by-side comparisons of 100% stock builds.

A clean build without google apps, and thus no synchronization overhead, and no other s*** floating around.. and this ROM is very competitive.  The only place I feel any lag whatsoever is when opening the application tray, and it's displaying more icons than the normal launcher with different graphics on the background.

I'm not saying people who consider the ROM slow 'stupid', 'noobs', or 'wrong'.  But the issues are perception issues, and must be considered relative to some other point.  They are also not universal, I have received constant feedback about the speed of this ROM and how happy people are with it.

I'm not being funny, or rude when I say that you're welcome to use whatever ROM you'd like.  I don't do any of this work for glory, massive amounts of users, or even donations.  I do it because it gives me a chance to control what is going on my phone, fixing any issues that come up along the way.  If the speed of the ROM is not up to snuff by your standard, I'm sorry and will continue to try improving it.

View Postwinhhh, on Feb 5 2010, 03:39, said:

When trying to run MetaMorph, I get this error;
It does not look like this phone has root access! the file: su could not be found

Any help ?

su is most certainly there, /system/xbin/su.  Downloading GScript Lite and running any of the 'root required' scripts works as expected, so no idea why Metamorph is not working properly.. Perhaps the path to su is hardcoded for some bizarre reason?

View Postkeyra74, on Feb 5 2010, 07:13, said:

videos close after 2 seconds like on every 2.1 aosp :/

I have to try a few more things, but will definitely try to tackle this one.  I had it working on one build at some point, for some people =).

Quote

same bug as with ckdroid 1.6 beta : market takes a while to refresh then shows a blank page, after being refreshed a few times it shows my download list

That's a server error, and I don't experience the same issue.  Its' a simple socket timeout, which means it is an issue with your connection.  This is the same market that is used on the Nexus, so it's not likely that there is such a terrible bug that causes a fake server error.  I'll see what I can find out, but there's not too much to look at when the issue is on the connection/server.

AOSP-Eclair-jnwhiteh: http://tinyurl.com/aosp-eclair-hero
If you like my work, I like beer

#60
Scottland

Scottland

    Regular

  • Members
  • PipPip
  • 98 posts
This ROM seems much quicker than Kagu 1.2.1 to me, and it's not crashed once yet - no force closes from any apps yet either. So far so good.

Thanks again ;)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users