[HERO ROM] Sneak Peek Working Donut on CDMA Hero

[Jerry Hildenbrand]

@phil
@travo112
@nclobo

Check your PM's. Thanks for not letting this die guys.

 

[pbrennan42]

Ok I have the batton and I am awaiting Travo112 and nclobo to get in touch.

I have already sent a round robin pm to the coders who have already been writing stuff.

Lets bang our heads together and see where this goes.

And have fun doing it.

Phil.

 

[nclobo]

Hey Phil. Could you pm me with some contact info? I tried clicking on your sig. links but all I got out of that was you like bein a bad bad boy...

 

[pbrennan42]

*snickers*

PM sent.

Phil.

 

[travo112]

Hey, sorry I was really busy yesterday.. I am downloading everything now, and Ill be taking a look at everything asap.

 

[WhiteWidow]

Couple issues after wiping twice. No texts go out. Is this just me? But I think I can fix that. GPS cant get a stable lock. Tried on the 2.1 rom on XDA with no success. Ill keep poking

 

[nclobo]

I cant get SMS to go out either. I don't know why because gbhil stated it was fully functioning on this build. But the same thing is happening on quiet's build on XDA. It works for some people and doesn't for others. ???

 

[Jerry Hildenbrand]

Couple issues after wiping twice. No texts go out. Is this just me? But I think I can fix that. GPS cant get a stable lock. Tried on the 2.1 rom on XDA with no success. Ill keep poking

I cant get SMS to go out either. I don't know why because gbhil stated it was fully functioning on this build. But the same thing is happening on quiet's build on XDA. It works for some people and doesn't for others. ???

Question - are both of you using Handcent?
If so, do you get a notification that gives an error and allows you to open the message to try to send again?
If so again, try ignoring that error, closing handcent AND killing it's process (use top + kill commands in term or a task killer app). Then use stock messaging app and deleting all messages from the database. Try sending a SMS through the stock app and report any error.

Another idea - make sure delivery confirmation is off and see if the same error occurs.

FWIW I use the stock messaging app with no delivery confirmation, on both "with google rev A displayed" and "non-with google Rev 0 display" Heros and have no problem sending SMS or MMS with this build. I also receive MMS messages with a link for download of the media. The download fails, and it appears it's because of extra data Sprint uses for it's picmail system that I never figured out how to handle.

Hope some of this was helpful.

 

[nclobo]

I only use the stock messaging app. I haven't used Handcent since the MR so that's not the problem. I have wiped, reflashed and didn't change anything. I tried it before and after applying the googlebits and it didn't work. I also redownloaded the files for fear they had somehow been corrupted the first time and reflashed those and it still nothing. So I'm stuck right now because I cant work on anything else until I get that going. However, I haven't had any problems with the GPS like WW described. So at least that's somethin.

 

[nclobo]

No go. The MMS sends fine but SMS doesn't. The logcat says they're doing the same thing(with the exception of the media). Is anyone still working on this besides me?

 

[Jerry Hildenbrand]

You will need to compare a logcat, ddms dump and maybe even strace and tcpdump from a working 1.6 user, a stock 1.5 build, and a non-working 1.6 user.

Also compare the /system/etc/apns-conf.xml file from all three.

I'm also thinking the PRI, Baseband radio, Software version, and Hardware version from all three might need looked at as well. These should all match, but I never checked or even thought to check.

Here's a stock 1.5's info:
PRI - 1.70_003
Baseband - 1.04.01.09.21
Software Version - 1.56.651.2
Hardware version - 0002

Stock 1.5 apns-conf.xml contents-

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project

     Licensed under the Apache License, Version 2.0 (the "License");
     you may not use this file except in compliance with the License.
     You may obtain a copy of the License at
  
          http://www.apache.org/licenses/LICENSE-2.0
  
     Unless required by applicable law or agreed to in writing, software
     distributed under the License is distributed on an "AS IS" BASIS,
     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     See the License for the specific language governing permissions and
     limitations under the License.
-->

<!-- This file contains fake APNs that are necessary for the emulator
     to talk to the network.  It should only be installed for SDK builds.

     This file is not installed by the local Android.mk, it's installed using
     a PRODUCT_COPY_FILES line in the sdk section of the toplevel Makefile.
-->

<!-- use empty string to specify no proxy or port -->
<!-- This version must agree with that in apps/common/res/apns.xml -->
<apns version="6">
    <apn carrier="Android"
        mcc="310"
        mnc="995"
        apn="internet"
        user="*"
        server="*"
        password="*"
        mmsc="null"
    />
    <apn carrier="TelKila"
        mcc="310"
        mnc="260"
        apn="internet"
        user="*"
        server="*"
        password="*"
        mmsc="null"
    />
</apns>

This is what builds the telephony database. This one will be different from the 1.6 one, as changes were made. Try pushing in this one, or making a frankenmorph version with this info added into what's in 1.6.

You'll need to delete the data/data/com.android.providers.telephony/databases/telephony.db database while in recovery and let it get recreated, of course pull a copy as a backup first.

I can post up the ddms dumps, tcpdump and logcat from a stock rom tomorrow evening. I can't actively run/test/build the 1.6 ROM, but I can be an extra set of eyes and a helper monkey!

 

[ro_bro]

Sorry to ask this again, but one of you with 1.6, can you try calling your phone? how many rings does it take until you hear it on the Hero?

 

[Ali Fazel]

I'm not a dev, and this may be a bit off topic so feel free to ignore it if you like. Android 1.6 has support for CDMA radios built in. Why is there such a problem building AOSP on any phone from 1.6 on up?

 

[nclobo]

Hey Gb, do you think that the PRI is what could be causing this? I went through as much data as I could find and or generate. And the only thing I can figure is that my PRI is 1.68 and not 1.70. Any ideas?

 

[Jerry Hildenbrand]

Sorry to ask this again, but one of you with 1.6, can you try calling your phone? how many rings does it take until you hear it on the Hero?

2, same as my other Sprint phones. That being said, I never had the issue others have had with the 'missing' rings. I realize I forgot to update that before when I tried it. Sorry.

I'm not a dev, and this may be a bit off topic so feel free to ignore it if you like. Android 1.6 has support for CDMA radios built in. Why is there such a problem building AOSP on any phone from 1.6 on up?

Because the phone is also full of non open source software that is used to make it work on the carriers network. All hardware functions will work with this build from the kernel side. It's a matter of reverse engineering the closed programming, and setting up the OS to correctly use the hardware. HTC/Sprint doesn't have to tell us that, and never will.

The big issue is that there's only a handful of people interested in the Sprint version of the Hero, so development is slow. And since we have a bit different hardware, we have to plug at it ourselves.

Hey Gb, do you think that the PRI is what could be causing this? I went through as much data as I could find and or generate. And the only thing I can figure is that my PRI is 1.68 and not 1.70. Any ideas?

Yes I do. Sort of lol. I don't think it's the PRI itself, but whatever decides what PRI you can update to.

I have a feeling there are some hardware changes from revision one (non-Google, has rev-a speed but displays rev-0 in settings) Sprint Heros and revision two (With Google, rev-a displayed) phones. That leads me to believe there may also be other small hardware changes in other areas. Some phones can update to a higher PRI than others, and it has to be hardware reporting which PRI it needs. Who knows what else these hardware changes could be doing?

What those changes might be, or if I'm even right is something I've been unable to find answers to.

 

[theoottesen]

I would also like to test this rom out and give some feedback.

 

[Brian]

i would also like the opportunity to test this rom out and give feedback on what is found.

 

[darchstar]

I too would like to test out this ROM and give feedback please

 

[bcnice20]

anybody trying to send me a update.zip of this please

 

[theoottesen]

does anyone have a link to this rom? i dont think gbhil is following this thread very closely at the moment. Thanks for any help.