Develop Bugs

[SNEAK-PEAK] Vid of Froyo on Hero

Here is a little sneak peak of froyo on Hero:
http://www.youtube.com/watch?v=5_Bir6OldNM

behnaam said:
Here is a little sneak peak of froyo on Hero:
http://www.youtube.com/watch?v=5_Bir6OldNM
Click to expand...
Click to collapse
1 word : wooooooooooooooooooooooooooooooowwwwwwwwwwwwwwwwww

Man that's AWESOME!

amazing benhaam

whats the Linpack score with JIT on?

will it be released ?
Edit : I read your twitter

No it wont be released as, why? Because its based on the SDK images that was not meant to run on devices
Wait until android git gets refreshed

behnaam said:
No it wont be released as, why? Because its based on the SDK images that was not meant to run on devices
Wait until android git gets refreshed
Click to expand...
Click to collapse
AAH
Anyway , good job

Was wondering where you got kernel source 2.6.29 from

xaueious said:
Was wondering where you got kernel source 2.6.29 from
Click to expand...
Click to collapse
don't ask too many questions
Behnaam has his sources

It's the same kernel from all the htc leaks ports available now...

behnaam said:
Here is a little sneak peak of froyo on Hero:
http://www.youtube.com/watch?v=5_Bir6OldNM
Click to expand...
Click to collapse
What's is the Linpack for Android MFLOPS score?

If it's anything like 2.1, we will not have any fully functioning 2.2 ROMs until the manufacturers release device-specific drivers.

RaduG said:
It's the same kernel from all the htc leaks ports available now...
Click to expand...
Click to collapse
Is it? I wouldn't be so sure Behnaam can have things he isn't allowed to release due to protecting leakers at HTC. I know someone with almost-final RUU for GSM Hero. But he can't release it cos it's all watermarked

I thought he did something cool to the toastcfh CDMA Hero kernel:
http://github.com/toastcfh/CdMa-HeRoC-2.6.29
That was just refreshed his github within the last 24 hours.

behnaam said:
No it wont be released as, why? Because its based on the SDK images that was not meant to run on devices
Wait until android git gets refreshed
Click to expand...
Click to collapse
anyone care to explain what behnaam meant?

anon2122 said:
Is it? I wouldn't be so sure Behnaam can have things he isn't allowed to release due to protecting leakers at HTC. I know someone with almost-final RUU for GSM Hero. But he can't release it cos it's all watermarked
Click to expand...
Click to collapse
hm..
hey , let me ask you as off-topic .
when will villain 6 be released ?
thanks

anon2122 said:
Is it? I wouldn't be so sure Behnaam can have things he isn't allowed to release due to protecting leakers at HTC. I know someone with almost-final RUU for GSM Hero. But he can't release it cos it's all watermarked
Click to expand...
Click to collapse
RaduG said:
It's the same kernel from all the htc leaks ports available now...
Click to expand...
Click to collapse
Well here is some proof which the other dev (wont mention names) couldnt get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Im holding it back because I have some issues that needs to be resolved
EDIT: Happy now?

behnaam said:
Well here is some proof which the other dev (wont mention names) couldnt get:
Im holding it back because I have some issues that needs to be resolved
Click to expand...
Click to collapse
nice
what about the BeHero 1.3 rom ?

looks a bit slow & buggy to be fair. and not sure i like the wallpaper of that dude holding a camera, is that stock?

Official support by Cyanogen

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now come on, let's do it!
Commiters, send me your Github usernames so I can add you as collaborators!
http://github.com/maxisma/Hero-CM-vendor
Click to expand...
Click to collapse
Click to expand...
Click to collapse
___________________________________________________________________________________________________________________________________________________________________________________
EDIT:
Just got a PM from Elemag:
Dude, count me in, I have fully working vendor tree for Hero, I only need to get some time to fix the scripts Will do my best to upload it to github as far as the end of next week (probably sooner).
Click to expand...
Click to collapse

maxisma said:
Now come on, let's do it!
Click to expand...
Click to collapse
I am in with both hands and a leg

I'm in with both hands and legs.

What is meant by a hero vendor ?
i really would like a official support but i didn´t understand :S

What is meant by a "Hero vendor"?

was my intention to propose a community eclairs.
if I can help somehow

I can agree with this. Throw up a poll!

Cyanogen just announced on Twitter "HeroC" support for CM6 !!
C'MON !! GSM Hero is more popular !!
we gotta act FAST !!

See first post.

Cyanogen getting bigger and bigger Super Nice...
I'm not a dev but I really like this idea. Official support.

Cyanogen is a legend! Wo made me go from WinMO to Android,just wanted to try his work as there was a lot of hype!

I am in! Send us Official support!

Commiters, send me your Github usernames so I can add you as collaborators!
http://github.com/maxisma/Hero-CM-vendor

Well, problem isn't compile cyanogen sources with working hero vendor. Problem is that last working vendor I know was LoxK with some fixes from mr.Whitehead.
I would like to support your effort, but I have to say that I always ended with compiled update.zip which simply never booted.

why don't u guys fork my heroC vendor tree. it isn't hard at all from there to make the subtle changes for GSM.

vorcigernix said:
Well, problem isn't compile cyanogen sources with working hero vendor. Problem is that last working vendor I know was LoxK with some fixes from mr.Whitehead.
I would like to support your effort, but I have to say that I always ended with compiled update.zip which simply never booted.
Click to expand...
Click to collapse
Don't worry about that, I have a strange mix of Lox' repo alongside some ported Cyanogen stuff from other devices and a few files of mine. And it works as it should I'll start uploading tomorrow and with a good community effort I hope that we can have a working tree, compatible with CM by weekend.

darchstar said:
why don't u guys fork my heroC vendor tree. it isn't hard at all from there to make the subtle changes for GSM.
Click to expand...
Click to collapse
I guess we will do that.. thanks for the suggestion

maxisma said:
I guess we will do that.. thanks for the suggestion
Click to expand...
Click to collapse
haha, u pulled the wrong vendor tree. the one u pulled is for froyo. i have another one for cyanogenmod
this is the one u want
http://github.com/darchstar/android_vendor_htc_heroc

MaXo64 said:
I'm in with both hands and legs.
Click to expand...
Click to collapse
I'm in with both hands and legs and certain parts of my anatomy that it isnt appropriate to talk about on the net.

darchstar said:
why don't u guys fork my heroC vendor tree. it isn't hard at all from there to make the subtle changes for GSM.
Click to expand...
Click to collapse
Actually, I tried your vendor, there was some problem with kernel alignment I guess. So I thought: this is for cdma, it should not work at all
It was stupid that I didn't asked you first
ah..and there were some differences in drivers, two of them you pulling from device wasn't on any ROM I tried.

1st Android 4.04 AOSP for the Gnex....

Birdman did the ROM I am Posting a link only~~
It is for Gnex Toro CDMA here is the Link
http://rootzwiki.com/topic/21626-aosp-404-stock/
~~~ENJOY~~~

Saw this as well. Gonna wait for CM9 or GummyNex though.

it should be noted that the kernel source isn't getting its 4.0.4 push till later this week. still - this is 4.0.4 (and 4.0.3 kernels should work on it anyways)
Click to expand...
Click to collapse
What does this mean? It's not using an official kernel? Or it's using the 4.0.3 kernel?

weirddan455 said:
What does this mean? It's not using an official kernel? Or it's using the 4.0.3 kernel?
Click to expand...
Click to collapse
I think he means that the 4.0.4 kernel source isn't getting updated on Google's repositories yet (the kernel source is maintained separate from the "Android" source code). Thus, all custom kernels will still be based on the 4.0.3 kernel, but should still work with 4.0.4. The kernel that flashes with the 4.0.4 update is the new, 4.0.4, stock kernel.

Sooooooo, what's the difference between this 4.0.4 and the leaked Verizon 4.0.4 from a few weeks ago?

stevessvt said:
Sooooooo, what's the difference between this 4.0.4 and the leaked Verizon 4.0.4 from a few weeks ago?
Click to expand...
Click to collapse
Doesn't include and verizon stuff and the code is probably updated.

i thought they only released the 4.0.4 was for GSM models.

Here was JBQ's post about it
https://groups.google.com/forum/m/?fromgroups#!topic/android-building/YoBlTfntDvo
Sent from my Galaxy Nexus using XDA App

Just flashed it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A couple interesting things about it. You can see the model number is different than on stock which I believe was "Galaxy Nexus" (fixed with newest build.prop, changed screenshot to reflect). Also, it comes with multiple keyboards. Whenever the virtual keyboard comes up there's a notification up top that lets me pick between them.
That's showing the "Japanese IME" which is not the default. The "Android English" one is which is what we're all used to.
It also has a carrier name "T-CDMA 64" instead of "Verizon Wireless"
And it comes with the Music app that CM9 has
EDIT: Also, comes with new ringtones and notifications as well as new defaults.
EDIT 2: Also, CM9 style louder clicks whenever you click on an app or navigate around the settings.
EDIT 3: He updated the build.prop so now it shows the model number as "Galaxy Nexus" correctly instead of "Full AOSP on Toro-VZW". Updating the screenshot with the fixed version. Either download the ROM again (the md5 will be different) or just download the build.prop from the link in the OP and copy it manually. The carrier still shows as "T-CDMA 64" instead of "Verizon Wireless" however, that hasn't been fixed.

Edit: why was this thread moved? This is for the CDMA version, doesn't belong in general.
Sent from my Galaxy Nexus using XDA App

Misleading thread title. First "publicly" released AOSP 4.0.4 maybe. I built it for myself yesterday. No T-CDMA issues either.

stevessvt said:
Sooooooo, what's the difference between this 4.0.4 and the leaked Verizon 4.0.4 from a few weeks ago?
Click to expand...
Click to collapse
Leaked build is IMM30B, this is IMM76D, which basically means it's a month newer. IMM30 means ICS Main Tree, where as M30B means it's the second build of January 30th. IMM76D is the fourth ICS main build of March 16.

ATnTdude said:
Leaked build is IMM30B, this is IMM76D, which basically means it's a month newer. IMM30 means ICS Main Tree, where as M30B means it's the second build of January 30th. IMM76D is the fourth ICS main build of March 16.
Click to expand...
Click to collapse
Thanks, although I kind of figured it was a newer build. More specifically Im trying to find out what the differences are between the builds. Is its worth redoing my phone from its current stock IMM30B.

How to build CyangenMod kernel?

Hi All,
I have successfully built CM7.2 ROM from source. It appears that the build uses a "prebuilt" kernel. I want to rebuild the kernel from source too. It appears to me that the kernel is a KANG kernel.
Q: Does CM7 indeed use the KANG kernel?
Q: Where can I get the source code for it?
Thanks
-John

hyperdyne said:
Hi All,
I have successfully built CM7.2 ROM from source. It appears that the build uses a "prebuilt" kernel. I want to rebuild the kernel from source too. It appears to me that the kernel is a KANG kernel.
Q: Does CM7 indeed use the KANG kernel?
Q: Where can I get the source code for it?
Thanks
-John
Click to expand...
Click to collapse
1.wrong section
2.kang = built from sources by people other than the official maintainers or buildbot.
3. https://github.com/CyanogenMod/android_device_samsung_aries-common/commits/gb-release-7.2
https://github.com/CyanogenMod/android_kernel_samsung_aries/commits/android-samsung-2.6.35

DanielSanchez said:
1.wrong section
2.kang = built from sources by people other than the official maintainers or buildbot.
3. https://github.com/CyanogenMod/android_device_samsung_aries-common/commits/gb-release-7.2
https://github.com/CyanogenMod/android_kernel_samsung_aries/commits/android-samsung-2.6.35
Click to expand...
Click to collapse
Thanks for your reply.
1. Sorry if this was posted in wrong section. I lack privilege to post in the Android Development section. But in any case, could you please offer a more appropriate section?
2. I guess I was imprecise. By "KANG" I meant specifically the Android Open Kang Project (AOKP). So, rephrasing my question: "Does CM7 indeed use the AOKP kernel?"
3. Thank you.

hyperdyne said:
Thanks for your reply.
1. Sorry if this was posted in wrong section. I lack privilege to post in the Android Development section. But in any case, could you please offer a more appropriate section?
2. I guess I was imprecise. By "KANG" I meant specifically the Android Open Kang Project (AOKP). So, rephrasing my question: "Does CM7 indeed use the AOKP kernel?"
3. Thank you.
Click to expand...
Click to collapse
1. appropriate section would be q&a or General. this is the android development section only for android roms.
2. No. kang is different from aokp. kang is a term and aokp is a project. like i described earlier, kang means built from sources by other people than the build bot or official cm maintainers. from wikipedia : Kang - A term used for stealing others intellectual property and claiming it as your own. (ie. When a developer uses another developer's work, and then publishes the end product as their own.)
if you plan to post your kang somewhere around here, make sure to give credits.
3.you are welcome.

DanielSanchez said:
1.wrong section
Click to expand...
Click to collapse
Since when that polite?

LOL i thought its tutorial
BUT : @OP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

dark_knight35 said:
Since when that polite?
Click to expand...
Click to collapse
Since i got warning from telling someone to read the op.
Sent from my GT-I9000 using xda premium

DanielSanchez said:
Since i got warning from telling someone to read the op.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I'm sure it ways the way you told and not the fact that you did that led to the warning .

4.1.2 jb

Anyone tries it out stock and noticed any differences?
Sent from my Galaxy Nexus using xda premium

4.1.2 has just been pushed to AOSP for the Nexus 7. As far as we know right now the only changes are for the N7.

http://www.funkyandroid.com/aosp-JRO03R-JZO54K.html
good day.

martonikaj said:
As far as we know right now the only changes are for the N7.
Click to expand...
Click to collapse
Changelog does list our devices.
** Project : device/samsung/maguro
8194bb9 Strip board-info.txt for AOSP
708ac51 Update board-info.txt
** Project : device/samsung/toro
e6eb055 SMS isn't converted to MMS even after 7 segments of messages
1cc0286 Strip board-info.txt for AOSP
bd30a89 Update board-info.txt
** Project : device/samsung/tuna
d59ae3b tuna: Kernel prebuilt
5fa370b tuna: prebuilt kernel (USB audio use after free) -- DO NOT MERGE
6b6fdeb tuna: prebuilt kernel (HSMMC1 suspend fix)
b69d5d1 tuna: kernel prebuilt DO NOT MERGE
32c13ca tuna: kernel prebuilt
Click to expand...
Click to collapse

building with JRO03R binaries atm.

Not to be negative Nancy or anything but from what I've read around the web. This new android os isn't a new build but more less a update to Jelly bean.

MMuzzy has a toro build up.

minor update

http://m.youtube.com/#/watch?v=a6dzMzklEd4&desktop_uri=/watch?v=a6dzMzklEd4&gl=GB
http://code.google.com/p/android/issues/detail?id=34212 - solved in 4.1.2
changelog is huge in some projects, primarily bugfixes
sent from my i9250

I just updated my nex 7 and its nothing major. The only thing I've noticed is you can expand notifications with 1 finger but I'm sure there's other little things 2
Sent from my Galaxy Nexus using Xparent SkyBlue Tapatalk 2

mainly "behind the hood" changes. like n3rd420 mentioned, thats the only new feature i find present.

i dont remember seeing Settings > Dev Options > Take bug report before.
sent from my i9250

ironside2011 said:
Not to be negative Nancy or anything but from what I've read around the web. This new android os isn't a new build but more less a update to Jelly bean.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Flashing??
bk201doesntexist said:
i dont remember seeing Settings > Dev Options > Take bug report before.
sent from my i9250
Click to expand...
Click to collapse
Hi there maybe this isnt the place but i thnik its a really tiny question im in stock jb 4.1.1 should i update the aosp for 4.1.2? or should i wait something else? if so how should i do it? should i install CWM recovery and install zip from sd card? or should i just use the stock recovery and do full wipes or whats the procedure to flash it thanks so much maybe this Q inst supposed to be here but in the Dev post i couldnt ask anything kindda noob here

F17Z63R4LD said:
Hi there maybe this isnt the place but i thnik its a really tiny question im in stock jb 4.1.1 should i update the aosp for 4.1.2? or should i wait something else? if so how should i do it? should i install CWM recovery and install zip from sd card? or should i just use the stock recovery and do full wipes or whats the procedure to flash it thanks so much maybe this Q inst supposed to be here but in the Dev post i couldnt ask anything kindda noob here
Click to expand...
Click to collapse
xda rule: search before you post.
and general questions go in q&a.
read this http://forum.xda-developers.com/showthread.php?t=1419170
sent from my i9250

I hope this is a good sign of things to come.
http://www.droid-life.com/2013/01/1...r-sprint-galaxy-nexus-flashable-through-odin/