yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] Blezz:
robin can you say any time when the rom will be ready? cause my androbin is really f***d up, only get 0,08 mflops (linpack) .. something i did wrong :D

will the new rom be there in the next time so i should wait for it or better install the "actual" rom?
[Hero, G2 Touch Android Development] fredphoesh:
GROAN!!!

again, a new, hyped up ra ra rom , and no f***bluetooth headset.

Dang.

AFAIK Villain makes the ONLY vanilla rom with bluetooth headset working.
[Hero, G2 Touch Android Development] robin04:
moderate terms. remember, I am not obliged to waste my time on the Rom, so, no complaints but only advice.

otherwise pay me.

you're not forced to use my ROM, if that something is not working.
[Hero, G2 Touch Android Development] Blezz:
i love your rom robin, and i said nothing against you

"something i did wrong :D" i said that it was my fault, i just wanted to ask if it is better to wait for the new version or just wipe / install it again
[Hero, G2 Touch Android Development] masterpfa:
That's a bit harsh. Remember these DEVS do all this to help us all out for no financial reward, if you want an all working ROM, revert back to Cupcake 1.5 your phone was supplied with. You'll find everything works there!

We all want 2.1 and we all want it now, but unless you are contributing to the efforts......:mad:
[Hero, G2 Touch Android Development] robin04:
@ Dipje :)

you have compiled kernel with kendong patch?

have also tested bfs and compcache?

Thanks in advance
[Hero, G2 Touch Android Development] attn1:
Robin,

What is different between GSM Hero and Magic with 032A board? Would this ROM run okay on a Magic?

Thanks
[Hero, G2 Touch Android Development] robin04:
essentially the kernel, because the hardware is similar (so you can easily port). I can do the porting of my rom for the magic, but I can't test it because I don't have a magic :D
[Hero, G2 Touch Android Development] dipje:
What's kendong patch? :).

I've got mine working on Androbin. Removed a lot of debugging crap, turned on some optimizing paramters in the build.

Behnaam 22 / 23, with BFS + Compcache.

Size of compcache is still not adjustable, so it's "enable or not" :). If it's enabled, it takes 25% of RAM to use for compcache, which means around 48mb in our case.

My clocks are now set as following: _ONLY_ freqs allowed are: 245mhz, 352mhz, 576mhz and 691mhz.

'on demand minimum' is 352, and 'on demand maximum' is 691mhz. So out of the box, without any overclocking tools, the kernel will pick 352, 576 or 691mhz depending on how much is asked of it.

The thing is: Robin's ROM sets the freq-policy to 'performance' in his boot, so it's always running at 691mhz now. I like it that way (battery get's throug the day so I'm fine) but if not you gotta use OC-Widget to set the clocks lower when the screen is off. When I tried to set the kernel back to 'ondemand' my 3d / opengl started working ok (real slow and with glitches). After a reboot it was fine again.

I have no 710mhz support on my hero, but I could enable it for the people who can.

Sooo, my question to robin and / or the users is:

What kernel to give you guys by default?

Let it boot a default 518mhz, and let users choose any mode of overclocking they want for themselves by using setcpu or OC-Widget

Let it boot a default '352mhz - 691mhz'-ondemand mode, so no overclocking tools required. These freq's should work on all heroes out there

Let it boot a default '691mhz' all the time, and let users use setcpu or OC-Widget to clock it down when the screen is off.

Build the default HTC-behaviour back in, but with different clocks. So let the phone itself set it to 352mhz with screen off, and 691mhz with screen on (no overclocking tools required).

Choose! I can't guess your demands, so let's hear it.

@Robin: Did you manage to do something about GPS? I used the same kernel on different ROMs and there it worked, so it seems to be something with your ROM and not my kernel.

Compcache on / off can be made into two command-line scripts. With GScript-Lite you can make shortcuts for them in the homescreen so users can choose themselves. I can supply the scripts, but that's it :).
[Hero, G2 Touch Android Development] dipje:
I know they are very much alike, things like the start-memory-address for the kernel are the same. So it will start and get you a long way.

I think (correct me if wrong) that some drivers are different for things like the Wifi, or g-sensors / compass, and / or camera. Even 'simple' stuff like that volume-keys or detection of a headset being plugged in can be different.

Sapphire 32a and Hero have the same 'mainboard' and same memory-addresses. There can be still a lot of other different hardware attached to it :)
[Hero, G2 Touch Android Development] robin04:
-This is the patch, I think he cleaned the tables and added scaling_freq

you have tried with CFS?

-Regarding compcache maybe you can add a script in init, so that it can adjust.

-I changed the freq-policy performance, then and now scaling_governor on ondemand and opengl works fine for me.

-My hero is running at 710 MHz and have a good answer.

- I am inclined to the second choice, but I didn't understand what you mean with last (default HTC-behaviur)

- I worked on config and libgps, I hope it works well now.

Thanks for your time mate ;)
[Hero, G2 Touch Android Development] robin04:
yes, base address is the same.

as you said, you need to work a little on hardware (wifi, light, sensor, bluetooth, etc.).
[Hero, G2 Touch Android Development] attn1:
I can test it. cyanogen 2.1 is for 32B, so you have to update cyanogen with a kernel update anyway. I could flash that and try it.

Gotta love nandroid backups.

I am wondering what the issue is with bluetooth on this ROM. Everything else looks so good. Is it something in the kernel that isn't quite right?
[Hero, G2 Touch Android Development] ZeppeMan:
Just wanted to test this ROM against VanillaEclair 3.2. I must say, in speed there's not much difference, maybe a little bit snappier, anyway very smooth and fast! Linpack I get same scores (4.7MFLOPS, 690Mhz, JIT).

If battery is better I stick to this one.

Nice work!

EDIT1:

JIT seems very stable too, no force closes, no freezes,..

Battery doesn't run hot like on other ROMs.

EDIT2:

Neocore doesn't work, same problem on VanillaEclair, maybe wiping ext partition will help?

EDIT3:

Neocore is working, was still on version 1.8 :x
[Hero, G2 Touch Android Development] gatsu_1981:
Hello, a couple of questions:

1) Is autobrightness working?

2) Touchscreen bug (high cpu utilization while touching the screen)?

3) Facebook sync with contacts?

If everything is working (don't care about A2DP at moment) I will stick here :D
[Hero, G2 Touch Android Development] jokuf:
Awesome

This is the best rom that i`ve used by now....very good job!!!!
[Hero, G2 Touch Android Development] ZeppeMan:
This morning fully charged, and battery still running on 100% :D I answered on 1 sms today, that was all I did with the phone today.

Very stable and fast ROM!
[Hero, G2 Touch Android Development] danwar:
Hello, my opinion is

[*]Let it boot a default 518mhz, and let users choose any mode of overclocking they want for themselves by using setcpu or OC-Widget

- every users are "lawful man" and make his settings.

or

[*]Let it boot a default '352mhz - 691mhz'-ondemand mode, so no overclocking tools required. These freq's should work on all heroes out there

- developer of ROM make some tweaks for speed, stability and battery live

- BUT stil exist choice for user with OC-W or SetCPU.

My experience, my settings

Screen off - 245MHz - better battery life and stil quick wake-up
[Hero, G2 Touch Android Development] robin04:
dipje and I are doing some tests on the new kernel.

He has set the default freq min_352 and max_691

unfortunately there was a strange battery drain. :(
[Hero, G2 Touch Android Development] Drevak:
Hi,

Just one question, does the Androbin_R_ come OC'd by default? or it's optional?

Should I use R5 instead if i dont want any OC?
[Hero, G2 Touch Android Development] robin04:
Androbin_R_, has the kernel OC

Androbin_r5 no

For OC Androbin_R_ you use widgets overclocking because there are not set freq by default.
[Hero, G2 Touch Android Development] dipje:
To be honest, I don't know anymore. Been a lot of kernel changes in the time in between :).

I _think_ that it defaults to 518mhz, with the possibility to OC it if you wish so.
[Hero, G2 Touch Android Development] dipje:
Like robin said, we are still testing a bit.

I had the kernel now to default OC. So the kernel switches itself between 352mhz and 691mhz, according to how much the phone is doing at the moment.

The thing is, it still runs too much on 691mhz. So the battery drains like crazy. Just as if you had it set to 691mhz all the freaking time :).

The thing about OC is: It doesn't cost that much power, if you only OC it when the screen is on. How much time is your screen actually on? For me, no more than 2 hours between charges :). The rest it's idle waiting for mails / calls / texts / etc...

So, if you OC only when the screen is on, battery life is OK. I had hoped that the 'ondemand' mode in the kernel would do the same thing, but it looks like no.

If I run OC-Widget for example, and set it to 352mhz when the screen is off, the battery drain is gone :). So I think we have to let go off the hope that we can make an 'automatic OC'-kernel, and just let it run at default 518mhz when it's booted, and let the user overclock it when / if they want.
[Hero, G2 Touch Android Development] gatsu_1981:
I agree 120%.

Since, my Hero can't manage running at 691 stable.
[Hero, G2 Touch Android Development] robin04:
we are working more carefully to avoid mistakes such as RaduG.

Competition leads to hurry and make mistakes.

we need to change this mentality, not a race and nobody forces us to deliver the work :rolleyes:
[Hero, G2 Touch Android Development] gatsu_1981:
Yep, I was a VanillaEclair user, but now I'm using your rom.

Less reboot (JIT-related) and everything works as it should.

BTW, are you sure that autobrightness is working? For me it stays @ maximum.
[Hero, G2 Touch Android Development] robin04:
I never said that it worked autobrightness :p
[Hero, G2 Touch Android Development] ZeppeMan:
Same here. Haven't had one FC, freeze, reboot,... with JIT enabled. Very stable and fast ROM.

Very nice work robin04 :)

You could expect a little donate from me soon ;)
[Hero, G2 Touch Android Development] robin04:
thanks for the support :)
[Hero, G2 Touch Android Development] meLIanTQ:
Work only whith titanium backup installed -_-' :(
[Hero, G2 Touch Android Development] gatsu_1981:
I can donate a resin cover for your hero :D
[Hero, G2 Touch Android Development] snaven:
I'm very interested in trying your ROM, but please tidy up the first page. It is far too confusing!! Does the latest version (Androbin_R_) have JIT? What is in the "extra apps" zip? Why all the links to so many different old versions?!

Phew!
[Hero, G2 Touch Android Development] robin04:
-I don't find it confusing, however ....

-have the jit (it is written in the title :rolleyes:)

-Common app (facebook, jbed, astro, autokiller, etc...will update the first post with the included app)

-I decided to leave the old versions, there is no particular reason
[Hero, G2 Touch Android Development] robin04:
is an appreciable contribution :D
[Hero, G2 Touch Android Development] mobydeek:
before i flash this...

1. Is "extra apps r5" essential to the operation of the ROM ? Or isit really "extra" apps such as Java box

EDIT: forget it... just dled and took a peek in the zip :D
[Hero, G2 Touch Android Development] robin04:
no, not necessary.....
[Hero, G2 Touch Android Development] dipje:
Things like that only work on real CyanogenMod ROMs most of the time, because he added things in his ramdisk to support those widgets / programs. See it as the CyanogenMod version of Spare Parts, it has settings for Compcache in it, but those don't automaticly work on every ROM.. the ROM actually has to make changes to support it (mostly).

I never heard of 'rom manager' or 'cyanogen boot manager', so who knows what a ROM must do to make them work 100%? :)
[Hero, G2 Touch Android Development] meLIanTQ:
@dipje:

Try this tools:

http://www.megaupload.com/?d=S6XNCX1A

the reboot in recovery work when i dowload busybox with titanium backup and after 'reboot system now' the rom launch and i retry but don't work ... its a joke -_-'
[Hero, G2 Touch Android Development] danwar:
reboot problem

I read user reference about reboot.

I have same or similar problem.

With Androbin_R_ I can not reboot to recovery, only reboot back to Androbin.

If I want go to recovery, I must shut down and next turn on to go to recovery.

I thought that is my problem with wrong pushing Home button, but I read, that this is ROM problem.
[Hero, G2 Touch Android Development] robin04:
this problem may be due to changes in the library hardware, especially "gralloc" that this version has

in the next version there should be no problem
[Hero, G2 Touch Android Development] meLIanTQ:
Ok thx Robin ;)

I push this 2 files in /system/lib/hw and now no problem ^^

http://www.megaupload.com/?d=I1DKYIRX
[Hero, G2 Touch Android Development] robin04:
I noticed yesterday while testing the rom :)
[Hero, G2 Touch Android Development] nomnompie:
Curious.. The keyboard lag on this rom seems not so good. I know that they say to turn off vibration feedback when typing but on Nathan's (nprussel's) SlideVillain 1.0.1 there was very little lag even with vibration feedback so I assume there is some way to fix the lag. I was just wondering if you have looked at this to figure out why there is so much lag. I was wondering if it has anything to do with the bug on Hero that makes the phone lag when you touch the screen in certain games and such.

If the keyboard lag could be fixed that would be awesome, as this is a really great ROM. :D
[Hero, G2 Touch Android Development] gatsu_1981:
Man, do you know what's the problem causing the touchscreen lag?

Usually while playing a game, touching the screen results in lag, and it's a consistent issue above 2.1 roms with new/older kernel.

Only a couple of roms doesn't have that issue (I think that vanilla eclair in the 3.0 didn't have that, but it does have a lot more of issues :D ... And I think it was smoother playing Abduction too).
[Hero, G2 Touch Android Development] robin04:
the kernel .29 has been ported from eris. there have been interventions in the kernel in order to operate the touchscreen in aosp, so it can be normal to find a bit of lag in some Rom. considered, I have compiled the current version from old sources cyanogen, where this problem is probably only partially resolved.
[Hero, G2 Touch Android Development] dipje:
no offense, but I have less lag on Androbin_R than I had on stock 1.5 rom or even Modaco 3.x .

The age-old problem where all the game-devs are whining "that android should fix the cpu usage while touching the screen" has nothing to do with Android, but the synaptics touchscreen driver being used. Newer devices like the HTC Incredible have no touchscreen-cpu usage problem, and they still run 2.1.

Keyboard lag (specially landscape) is a bit present. Landscape without lag I never noticed on _any_ Android device. Being it a Nexus One, Desire or Hero Modaco. But I only type in portrait it any flies through my words without problems.

Too much background processes running or a browser that might still be loading a page is most of the times the cause for this.
[Hero, G2 Touch Android Development] gatsu_1981:
So that's a synaptic driver's problem...

Is there only a binary driver for that?
[Hero, G2 Touch Android Development] dipje:
Better yet, we have source in the kernel. There is a newer version of it, but that one only works on Sense ROMs (hence AOSP versions need to use an older version).

But even the Sense ROMs have cpu usage problems when touching.. it's just the nature of the touch-device. That driver requires to time and poll quite often, resulting in higher cpu usage.

The keyboard lag has nothing to do with it though (or almost anyway). Searching through the dictionary, and drawing the keys takes up quite some power on our aging hardware. That's why landscape lags soooo much more than portrait: It requires more drawing :), that's the only reason I could come up with.

It can also be that some hardware-acceleration in the graphics is not working when the phone is flipped to landscape, but I can't believe that. Lot's of games run fine in landscape.
[Hero, G2 Touch Android Development] ZeppeMan:
New RADIO is working like a charm with Androbin_R @ 691Mhz + JIT.

New record with Linpack, 4.774 MFLOPS :eek:

I don't know if this is because of the new RADIO. But before I had high 4.6 MFLOPS. After RADIO flash I don't go under 4.7 MFLOPS :D
[Hero, G2 Touch Android Development] dipje:
New radio? Did I miss something? Does it fix the current GPS issues? Because then I can go back to AOSP (installed Villain because I needed something working real quick yesterday, and I'm missing Androbin already :)).

Anyway, @robin: Any news on the new release? I gave you a working kernel two days ago.. soo... new release? :)
[Hero, G2 Touch Android Development] mardurhack:
dipje maybe you missed the official 2.1 release! :P HTC gave us the upgrade!
[Hero, G2 Touch Android Development] robin04:
hey mate :)

I played around with values such as sampling_rate, up_threshold, etc. .. to observe performance / battery and then I'm trying to do work autobrightness and LWP.

However by today or tomorrow I should upload new release.
[Hero, G2 Touch Android Development] dipje:
Really?!? Damn I missed that :).. Buying a house is taking too much of my time :)
[Hero, G2 Touch Android Development] ZeppeMan:
Will the next version be based on the official release?
[Hero, G2 Touch Android Development] dipje:
Is that possible with an AOSP rom? :) :).

Maybe he can take some binary files from it (radio + ril, maybe legacy_hardware), but that's it. The complete build is from source.

What you probably want is something like SuperHero, a stripped down Sense rom to look like an AOSP rom.
[Hero, G2 Touch Android Development] robin04:
sorry guys, but interrupting the work

go out to eat ice cream :D

Tomorrow I should be able to upload new version

LWP work
[Hero, G2 Touch Android Development] clin81:
Great Robin!!! (Abbiamo fiducia in te) ;)
[Hero, G2 Touch Android Development] gatsu_1981:
I've tested your rom with latest radio today.

Everything seems smooth, it rebooted a couple of times just after installing the radio (just after putting the PIN for my SIM card), maybe before the update the cache was emptied so it needed to be rebuilt.

So far so good, my signal with Tre seems a bit smoother (it's really strange, since I can have 0/4 lines of signal and HSDPA and conversation works really good... With Vodafone below 2 lines speaking quality becomes unbearable).
[Hero, G2 Touch Android Development] ZeppeMan:
That's what I meant :)

btw, using this ROM for a couple of days now. Still no lag, no FC's, freeze,...

Very nice ROM!! :)
[Hero, G2 Touch Android Development] robin04:
release....release...release :D
[Hero, G2 Touch Android Development] gatsu_1981:
What's the changelog?

PM me with your home address, you need a new resin cover for protecting your hero... If you drop it you will have to stop develop for us! :D
[Hero, G2 Touch Android Development] robin04:
Changelog CR1:
-update buggy gallery3D
-ultimate ADWlauncher (thanks Anderweb)
-add HtcMusic
-add CorCal & CorGal
-fix facebook sync (melianTQ)
-solved huge battery drain
-fix gps signal lost
-fix su
-fix graphical bug in default_wallpaper (joshman99)
-BFS and compache
-set by default -- freq_min = 245760 MHz -- freq_max = 518400
-live Wallpapers all work well (high frequency of CPU work more smoothly, thanks firerat)
-other things that I don't remember

is this a joke? :p
[Hero, G2 Touch Android Development] robin04:
maybe I can integrate autobrightness

for A2DP, I need a bluetooth headset, so you can make tests :D
[Hero, G2 Touch Android Development] emilio666:
sorry, can't find the htcmusic and OC widget gets FC's :( (but the set cpu app works)
[Hero, G2 Touch Android Development] robin04:
I both work perfectly. wipe test Dalvik & Date
[Hero, G2 Touch Android Development] emilio666:
I always do that before flashing... anyway, I'll do it once more time
[Hero, G2 Touch Android Development] gatsu_1981:
Not kidding, just take it as a small donation :D

I've bought some from eBay, for choosing between different colors :D

P.s. I'm Italian too ;)
[Hero, G2 Touch Android Development] emilio666:
finally, the widget is working and so the htcmusic is (strange... have to do it twice...)
[Hero, G2 Touch Android Development] gatsu_1981:
I didn't wiped data, only Dalvik Cache, and now I don't have HTC Music!

But... I don't want HTC Music! :D

So that's ok with me :D

But all my settings are still here, and Market works.
[Hero, G2 Touch Android Development] ZeppeMan:
Going to test your new ROM now :)
[Hero, G2 Touch Android Development] ZeppeMan:
Just finished with testing a bit. But I don't find any differences in speed. In my opinion it's as fast and stable as Androbin_R.

So, this is a very stable and fast ROM :)

EDIT:

1 issue:

Neocore performs very bad. Took about 3 minutes to finish, 4 frames, colors not good. Also other games I have very little frames.

Everything else is working fine.

Any ideas on this problem?
[Hero, G2 Touch Android Development] xtkme:
HTC Music... that sounds interesting.

But, anyway, don't HTC stuffs require Sense frameworks in order to get them working? Thus, is it possible to have HTC Camera on AOSP as well? :D

-------------------------------------

Sent via the XDA Tapatalk App
[Hero, G2 Touch Android Development] intronauta:
LWP <------- ------->3D
[Hero, G2 Touch Android Development] ZeppeMan:
Stupid question maybe, but what means LWP:confused:

EDIT:

In the topic "3D/OpenGL performance" kad3t has the same issue with 3D performance.
[Hero, G2 Touch Android Development] kad3t:
Indeed I do. At first I though - sh*t my CPU is frying but then when I grabbed my mobile and it was all cool and all I realized that there's an OpenGL issue of some sorts. Any known way around it yet? Anyone? ^__^
[Hero, G2 Touch Android Development] robin04:
Guys, the problem is due to patches for live wallpaper.

I try to fix the problem, however removing GPU_permission in init.d quite normal return
[Hero, G2 Touch Android Development] kad3t:
WOW! Thanks for the prompt answer and big THANKS for this awesome ROM!

But what is that you're telling us that we should do to have Neocore and games running at normal pace?
[Hero, G2 Touch Android Development] dipje:
Hmm, I had the same problem with neocore performing badly while I was toying with the kernel and frequencies. I was solved though, so are you guys sure it has nothing to do with Live Wall Papers being active or something?

And what Launcher are you guys using? It might have something to do with it.

Anyway, Robin is saying you can remove a file in the startup-scripts to return 3D to normal operation, but he will make a fix for it if you don't know how to do it yourself :)
[Hero, G2 Touch Android Development] kad3t:
I do performance tests on regular wallpapers and not live ones. So, it was a regular one. And also did not touch the kernel. I tried it both with ADW Launcher and Launcher Pro - same results.

I would love to have 3D at normal operation but does it mean no Live Wallpapers?

Anyway, I'll be waiting for the script.

Thanks! To you and Robin! ^__^
[Hero, G2 Touch Android Development] ZeppeMan:
I'm using Launcher Pro.

This is one of the fastest vanilla ROM out there, If the 3D issue is gone then this ROM is near to perfect :)