yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Infinimint:
Tvall, child you out the MD5 or SHA1 of the original?
[G1 Android Development] :
"Did you check out the md5 or SHA1 of the original?" :P
[G1 Android Development] Infinimint:
Lol my spell check was aweful hahaha
[G1 Android Development] :
I compiled CM9 from source with make -i & with linaro toolchain..

It wouldn't boot, however, as logcat would show an error related to sh/libc and I haven't looked into the issue yet.
[G1 Android Development] VeryCoolAlan:
My G1 broke almost two years ago xP

I was Running CM6 on it (first rom being Jesus Frekes RC 29?)

Anyways how does this ICS run?
[G1 Android Development] tvall:
The uploaded zip os bad. I'll get a new one out later. Still no internet. :/
[G1 Android Development] tvall:
I'm not sure of I trust linaro yet. I've heard plenty of good about it but I've also heard a similar amount of issues with it where it causes random crashes and freezes. Once I her internet back I'll do some testing with it. On the mytouch 1.2 all we need is hw acceleration for this to run smooth.
[G1 Android Development] Infinimint:
Linaro is a good group and is backed by some of the CM team. What is to dislike?

Edit: Not to mention the fact that Google is adding the Linaro performance patches into AOSP.
[G1 Android Development] satanic666:
Error 404

I am testing Alpha 2. I'll be back soon with error report and catlog :p

Please Update link of:

alpha1.1 - http://uniteddev.com/wordpress/file...0-RC0-dream_sapphire-UNOFFICIAL- alpha1.1.zip

alpha0 - http://uniteddev.com/wordpress/files/update-cm-9.0.0-RC0-dream_sapphire-UNOFFICIAL-signed.zip

http://uniteddev.com/wordpress/files/roms/cm9/mtdpartmap.txt

keep it up :good: Happy to see there is still some activity with legacy devices :)
[G1 Android Development] satanic666:
I got error in CWM recovery, there was not any error code number only error as follow: cm-9-20120609-UNOFFICIAL-dream_sapphire.zip (Bad)

Installation aborted...

so I decided to flash aokp it was installed properly, then I flashed provided kernel and then I was only able to see boot logo

I am currently on radio:2.22.28.25 and hboot: 1.33.0013 and my board is 32B, I doubt I am stuck in boot loop because of hboot so i will try danger spl tomorrow. :)
[G1 Android Development] Infinimint:
If anything, switch to 1.33.0013d.

Also, I'm pretty sure the .zips have been bad for a while and need to be reuploaded.

Also, try Superwiping your phone and reflashing. And if you're using United Recovery, try another recovery.
[G1 Android Development] pauldacheez:
How do people even use that hboot? No S-OFF, no useful Fastboot commands... I had to flash ENG 1.33.2005 because something screwed up my recovery and I couldn't do anything about it with that hboot.
[G1 Android Development] Infinimint:
What more do you need to do? You don't need to flash radio or hboot images, and so long as you have a booting system and kernel, you can flash recoveries easily if it gets screwed up by using the flashimage binary. Then with a working recovery you can flash onto the system, kernel, boot, and recovery partitions as well as the hboot and radio partitions if you know what you're doing. As for commands, make a package that will automatically do what you need it to by using AROMA Installer or Ezterry's yesno binary. If you are careful, you'll never need to flash an ENG hboot.

Of course, S-OFF is preferred, but not always needed if you can find workarounds.
[G1 Android Development] demkantor:
we still have fastboot wipe, the rest is only nice but not needed. this isn't true s-on
[G1 Android Development] pauldacheez:
In my case, I had flashed a bad recovery, and flash_image plain didn't work (?!). I forget the details, but I couldn't do a single thing with that hboot, and I couldn't find any solution other than to flash a different hboot.

I'm more familiar with doing stuff through Fastboot, so having an hboot that doesn't support all its features just hinders me on so many levels. Screw the safe route, I know what I'm doin'.
[G1 Android Development] tvall:
Cm9 zip is still bad (sorry)

Soon ill have internet back and ill get back to work on this. Cm9 will be an easy fix. Aokp doesn't have much work left. All I need to do now is fix hw acceleration, slim it down more, and mess with the camera.

Question for y'all, how many of you have an ext partition? Thinking of adding a script for apps and dalvik on ext
[G1 Android Development] Infinimint:
Haha that's great that you know what you're doing. Either way though, knowing or not, with the ENG hboot most new roms will be unbootable without a specific kernel. Also, you won't be able to take advantage of the features that the new radio offers.
[G1 Android Development] pauldacheez:
Meh, doesn't matter at all if it's my secondary phone and if the kernels are available.
[G1 Android Development] AndDiSa:
If you want to do everything with fastboot even in that case there is a solution:

flash the orange-xxx.nbh (using fastboot) which has a full eng spl included

then do what you want (flash recovery, ...) via fastboot

and at last you flash the 27.08/0013d combo again

No need to flash a single piece via recovery ...

(Btw. I prefer fastboot, too. ;))
[G1 Android Development] hrk:
I have. I doubt there are Dream owners without an ext partition..... and more than a handful of apps installed. :)
[G1 Android Development] kanttii:
I found a fix for the red borders that sometimes appear!

Go to settings -> developer options and disable "Strict mode enabled" under user interface settings.

Its useful if you are a dev and want to see which operations take a longer time on main thread and which not, but I doubt most of us need it...
[G1 Android Development] frankdrey:
I use an ext partition always. Include support and you may convert me to this rom.
[G1 Android Development] Infinimint:
I use a 512MB EXT4 partition.
[G1 Android Development] MMartins:
great work, waiting for a everyday usage version ;)
[G1 Android Development] DorianX:
A daily usage ICS rom on the G1? I don't think so, even Gingerbread it's laggy

Enviado desde mi Desire HD usando Tapatalk 2
[G1 Android Development] MMartins:
nop, for magic ;)
[G1 Android Development] DorianX:
If it's a 32a version good for you :D maybe someday you will have a decent ICS rom, but if it's a 32b I don't think so.

Enviado desde mi Desire HD usando Tapatalk 2
[G1 Android Development] MMartins:
yes it is a 32a :)
[G1 Android Development] Infinimint:
I think if we got hardware excelleration working, graphic libs, and compiled with linaro gcc and patches, it would be really good.
[G1 Android Development] prusokas:
That would be great.
[G1 Android Development] frankdrey:
Do it. :D
[G1 Android Development] tvall:
Hey infinimint, can you try getting a linaro build with my repo? I'd do it but... yeah. Some testing would be great.
[G1 Android Development] Infinimint:
Haha I would love to do this stuff but I'm in the process of moving :/

My house is empty and I don't have internet or a computer. It's very sad lol

I'll probably have most of it back by the 10th or later. Until then, all I can do is read and write posts.

It'll take that long because its all the way across the US so its a week long road trip, if not, longer. Also, we have to wait on the moving trucks with my computer, then setup a network in the house.
[G1 Android Development] Infinimint:
Also, it looks like ICS is kinda out of date :/

Jellybean FTW.

Jk, I think ICS is where we should probably stop because I think the demands of JB are a little too high. There's no way the Dream will ever reach 60fps lol. Although, the general speed improvements could help a lot if we had working drivers. I guess we'll just have to wait for the source to be released.
[G1 Android Development] frankdrey:
The dream shall dream on!!!! About jelly beans!!!!

And kandy kanes. And lemonade. M....I dunno.
[G1 Android Development] Ace42:
ICS ✓

Sound ✓

Calls ✓

Data ✓

Bt ✓

Camera x

HW Accel x

By the way...I'm wondering if you have considered using an OC to overcome some lag produced by HW accel's absence. Getting ICS GPU drivers is near impossible since this HW isn't even supported technically by AOSP, CM, etc. I think the highest this chip can peak at is 710MHz, not sure if that's what you'd call stable. But it's probably the best thing that can be conjured unless you can reverse engineer the Gingerbread or Froyo drivers for the G1. Now that I think about it, can the G1's 10MB GPU actually handle ICS? And if it can, would the GPU need to be OC'ed also?
[G1 Android Development] MMartins:
for what radio/SPL of magic is this for?

the old one?
[G1 Android Development] Infinimint:
Btw, did you ever try out those Hero EGL files that JianC (e334) linked to on page 2?

EDIT: @everyone We just left for Virginia today, and I'm completely bored. Hit me up on Twitter and/or Google+ and say hi or whatever. I'm gonna be posting crap every now and again and playing Xbox and stuff lol. I finally have time to play the MW3 and BF3 campaign. I wish I had SC2 in the car lmfao.
[G1 Android Development] frankdrey:
With the 2708+ kernel that GPU RAM is used for regular ram :O

So....maybe we should ditch the kernel....
[G1 Android Development] :
2708 kernels doesn't have decreased GPU ram compared to the "other" kernels..
[G1 Android Development] frankdrey:
I thought it took GPU RAM and assigned it as regular RAM...
[G1 Android Development] Infinimint:
Last I checked, that isn't the case.

A lot of roms have broken hw3dc which allows for more ram in exchange for broken 3D graphics.

The new radio and kernel combo gets the extra ram from the newer firmware, not from breaking the GPU. If it broke 3D graphics, T-Mobile would not have made it an official OTA.

Also, if you break the camera, you can get even more ram :)
[G1 Android Development] Ace42:
Maybe we should break camera then and get its 4-5MB RAM; the camera is far from stellar so I''m sure many won't miss it.
[G1 Android Development] Infinimint:
Lol we should make a version with everything broken and no phone capabilities so that it could act as a simple media/app player.
[G1 Android Development] pauldacheez:
That's actually a pretty decent idea – most of us have newer phones anyway, and if we actually use our Dream/Sapphire as our daily driver, A) we're crazy/broke, and B) we could just use a working Donut/Froyo ROM.

Or, even better, we could temporarily break everything that doesn't work yet for the RAM and give up that extra RAM if we get something working.

</stupid_suggestion>
[G1 Android Development] Ace42:
Sounds like a plan, disabling the radios should raise performance exponentially with so much extra ram. :highfive:

10MB GPU + 4MB Cam + Radio RAM = faster G1
[G1 Android Development] demkantor:
not a bad thought, and i believe it is possible to remove the radio but i have a feeling we would need a custom spl then as bootloader probably would load with any of the spl currently for the g1

but hey this would be a kick ass little mp3/internet device if all were said and done - but in that case would ics even be the platform.... maybe this discussion should be moved to a new thread :P
[G1 Android Development] Infinimint:
Hahaha we wouldn't actually remove it. Just break it by using improper permissions or removing files entirely. Things that could be fixed easily.

Not hard to do, just make a .zip and inside the updater-script just change the permissions or remove the files necessary maybe with AROMA and then move the apps to sdext if it exists, data, or delete them entirely.
[G1 Android Development] demkantor:
huh, I was under the impression you could dissable the radio after boot but your boot loader won't allow the phone to load without a functioning radio, at least the bootloaders we have. I guess I've never tried or looked into it much, if its this easy we just scored ram for our little tablet w/ hardware keyboard!

so long as wifi still is functional people would be digging their ol g1s out of the sock drawer for this!
[G1 Android Development] frankdrey:
:D

Awesome ideas.

Also, wait, so 2708 radio does NOT get ram from gpu???

And it was an OTA?

Please explain...:P
[G1 Android Development] Infinimint:
Yes, the 2708/2825 radios and the 1.33.0013 HBOOT were OTA updates for the 32B HTC MyTouch 3G by T-Mobile.

However, 1.33.0013d is a modified version of that HBOOT by ezterry to also work with the HTC Dream and T-Mobile G1.

No it does not get the extra ram from the GPU, the updated radio firmware allows the device to access more ram. From where, I am unsure but it was probably either from the radio or was just dedicated to something unnecessary or it was unused entirely.
[G1 Android Development] tvall:
Ill get to work on a kernel that steals ram from the cam and gpu.

I still think I can do some with hw acceleration. AndDiSa got it kinda working in his port. haven't had time to figure put what he did yet..
[G1 Android Development] SlashSpeed:
Boy if you can get HW acceleration working, I'll worship you as my god. :victory:
[G1 Android Development] frankdrey:
Understandable.

And the 2708+ ROMS that claim 3d graphics suck just have it broken? Okay. Gotcha.

Well that fixed a misconception I've always had.

Leave the gpu ram if you want some hardware accelaration for the ics ui.
[G1 Android Development] almostthere:
I'd doubt if ARMv5 even suppports the h/w acceleration that ICS mandates
[G1 Android Development] Infinimint:
Didn't the HTC Hero get ICS HW Acceleration working?
[G1 Android Development] tvall:
Yes, but i havent got it to work..

The dream is ARMv6j

I'm running ics on an ARMv6-vfp device with hw acceleration. I was thinking it was just a gpu issue, but the hero has it working.... idk
[G1 Android Development] blaster44:
Magic has it working too, but on new radio(Sandwich Deluxe).
[G1 Android Development] tvall:
Yeah. But they are binary porting an older version of ics. And I've helped the devs there with several bugs. They haven't told me how to fix hw accel. I'm assuming it was fixed in the base rom.
[G1 Android Development] hrk:
I don't know if this may come useful at all, but here's a post related to using the old (and working!) libcamera from Gingerbread on ICS through a wrapper (although on a Samsung device): http://xdaforums.com/showpost.php?p=28438502&postcount=961
[G1 Android Development] PowerPlop:
A possible solution to fix the cameraproblem:

- Download my rom or the base rom

- Replace all libcamera....so files + lib/hw/camera.....so files

It could be that this solves the problem.

How do I know that HW is working?
[G1 Android Development] :
It's not as simple as that.. camera works differently than GB in ICS..

You will know HW is working when you don't see any choppiness/lag when scrolling :good:
[G1 Android Development] Infinimint:
His rom is ICS. It's in the Magic/Sapphire Forum.
[G1 Android Development] Sefy:
Maybe it's just me... but wouldn't it be better to focus on ONE project which will work from start to finish.. then to have 3 of them, where none is finished? :confused:
[G1 Android Development] :
I'm a victim of that.. sadly.. :'(
[G1 Android Development] Infinimint:
+1 Me too unfortunately.
[G1 Android Development] xillius200:
Bleh aint been here in a while.... ICS hw acceleration should work with any device with a gpu just with worse gpu it will work worse. For the ram it may have been taken from the camera as the camera from froyo and up began to use less ram but then other places it was probably taken also get your ass over to a diff forum infin xD jelly bean aosp is out.

PS: I know i just pop up randomely after a long time but thats just me..

PS2: sefy you can blame that on me.
[G1 Android Development] Sefy:
I don't wanna blame anything on anyone, if anything, i appreciate you guys working on it in the first place. I just honestly don't understand the logic of spreading yourself across a lot of pretty much identical projects instead of finishing one all the way thru.

There's amazing developers here, i personally don't understand why not working together to first create a single basic fully working OS and THEN to the tweaks and twists. I see it happening in a lot of devices, that have missing bits and pieces...
[G1 Android Development] frankdrey:
1. Because not everyone agrees on what should be in an OS.

2. The more people you get, the more time wasted explaining each others code and tripping over each other.

3. Its fun to work on a ROM. Especially alone.
[G1 Android Development] xillius200:
1. True working together has its down falls yet it helps in establishing better roms and fixing problems. Some businesses and companies work in teams to create software as there are many many advabtages. For instance oracle ans microsoft work in this way. Oracle work across the internet on many occasions share code and meet at a place like once a year in some cases. <<that was what I was told by someone who works at oracle designing software>>

2. As for what's in a from completely agree everyone has different ideas of what they would like for instance some like sense while others don't some people want certain apps while others don't some want speed while others stability so many different types of roms must be made in order to satisfy everyone......think of skittles. Some like some colours and flavour other people like different ones xD
[G1 Android Development] whoshotjr2006:
Hw acceleration working on the hero and hero cdma is a myth. Sorry if I crush anyone's dreams lol. What we have is actually just a hacked up gles 1.1 binary that works better than what's built with the rom from source. Dunno where it came from but if someone would like to they can dl eligorom from the heroc forums and replace the entire egl folder in /lib with the downloaded one and see if it speeds anything up. Its almost a guarantee we wont get hardware acceleration for g1 hero and heroc because qualcomm just decided to throw us under the bus all because we don't have a real gpu

Worth a shot to try the hacked gles libs though. If needed I can rip it out and upload it here. Just let me know.

Great work btw

sent from my heroc running cm7.2
[G1 Android Development] xillius200:
See now from android 2.1 hardware-accelerated graphics have been used just we have not had a hardware accelerated UI as far as I know, so we have had hardware acceleration just not for the UI. as for the ICS drivers for armv6 there is the adreno 2xx GPU binaries for armv6 devices from Qualcomm themselves http://www.xda-developers.com/andro...no-2xx-gpu-binaries-for-on-ics-armv6-devices/ However im not sure if they enabled us to use the full hardware acceleration capabilities. A petition was created to get these drivers for armv6 so we could use more hardware acceleration in ICS xD
[G1 Android Development] tvall:
I tend to focus on multiple (different) projects at once because most of the time I work alone. When I get stuck and frustrated with one, I switch to another and fix it instead of getting to the point where I'm mad enough to throw my keyboard at the cat (only happened once). Then once I've relaxed, I go back and rethink what was causing the issue.

Btw, my current projects:

- United ics (cm9 and aokp)

- Iho magpie (cm7 + magpie for the lg optimus v)

- custom kernel for my desktops.

I don't think I'm spread too thin.
[G1 Android Development] xillius200:
You need to add jellybean now that ICS is working mwuahahah :D
[G1 Android Development] tvall:
Once cm starts on it, ill have something as soon as possible.
[G1 Android Development] whoshotjr2006:
The drivers that qualcomm made for arm6 devices are only for ones that have the adreno 200 gpu. We do not. We have adreno 120 or 150, one of the 2. The 200 drivers will not work for us at all. Qualcomm did in fact unfortunately throw many older devices like ours and many more under the bus. Unless someone is a crazy dev with all sorts of skills to write us somewhat of a software emulated hardware acceleration driver, no dice here.

Lol sorry if I sound like the doom bringer, but I guess someone has to.

sent from my heroc running cm7.2
[G1 Android Development] xillius200:
lol I never said it was for this device just that they were drivers for ICS for armv6 that would enable hardware acceleration for us and they will lol they are still written with armv6 in mind just needs modding for our GPU which can be done.

Also don't be so negative xD things which have said would never be possible for the HTC Dream have been done many times so with that in mind even this is possible ^^
[G1 Android Development] Infinimint:
Lol completely off-topic (I'm attention whoring :D):

I just broke my keyboard (It's a Microsoft Arc, also not by throwing it at the cat xD) and am looking to buy a new one.

Here's the criteria:

- Around $85, must be under $100.

- Preferably Backlit keys.

- Must be mechanical with Cherry MX reds.

It'll mostly be used for programming and Starcraft II. I'm currently looking at the SteelSeries 6gv2 and the CoolerMaster CM Quickfire.

Thanks homies :)

EDIT: After doing some research, here's what I've come up with:

SteelSeries 6gv2 - Cherry MX Red - $84.99 - Link - Sucks with Mac (I have a hackintosh :\), Also, the right spacebar is too small and the key placement makes no sense.

Cooler Master CM Storm Quickfire Rapid - Cherry MX Red - $89.99 - Link - Ridiculous amounts of CM logos that it's*pretty annoying.

Corsair Vengeance K60 - Cherry MX Red - $89.98 - Link - Not fully mechanical, only the main keys are.
[G1 Android Development] whoshotjr2006:
Hey, not being negative just being a realist. If you know how or know anyone who does know how to mod incompatible drivers to work for us please do tell. If someone is good with source coding and such then they could look through the binaries involved for Hw acceleration and possibly tweak things. But I hold my doubts until I see it working.

those drivers werent only designed for armv6, they were designed for armv6 with the adreno 200 gpu. gpu being the key word. we dont have a real one. our graphics rendering is all handled by the cpu. from what i gather the only thing that changes the code from armv6 from armv7 is the compiler, as im pretty sure some armv7 devices have adreno200's too.

as far as my knowledge of all this stuff, im not god. im not infallable. if you or someone else proves me wrong, i will gladly say i was wrong and rejoice in the basking glow of hardware acceleration and gpu acceleration goodness.

from what i understand, hardware acceleration in adreno 200 ics roms (such as legend, wildfire, etc) alludes to gpu accelated video. whether it be ui, youtube, or standard video playback. with no gpu to accelerate, how do we for lack of better terms, accelerate gpu rendering?

when adreno 200 got hw acceleration, the only real thing it did for them was accelerate the ui (handled by gpu), accelerate youtube video playing so it could be watched (again handled by gpu), and accelerate video playing from sd card (and again, handled by gpu.)

wiki about imageon/adreno "gpus" http://en.wikipedia.org/wiki/Imageon

we fall into the adreno 130 category

we would also need working opengles 2 on our devices, another feat that hasnt been accomplished because our "gpus" (or lack of them anyway) dont support it at all

so please dont think im being a jerk, thats not my intention. my only intention is to report findings to the public so that the public does not get their hopes up for something that is likely not to happen. xillius200, if i offended you in any way that wasnt the goal. if qualcomm could have facilitated us having hw/gpu acceleration, im sure they would have accomidated us like they did the adreno 200 crowd.

by the way, here are those libs i promised. should be drag and drop replacement. opengles 1.1 if i remember correctly, but its what some think is hw accleration on hero/heroc

edit build.prop to say

ro.opengles.version=131072

instead of

ro.opengles.version=6**** (whatever it is i forgot)
[G1 Android Development] frankdrey:
Holy crap, my keyboard costs around $5 and looks like its from the 90s.