• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [DEV] Continuing Triumph ICS Development

Hello. You may have seen me earlier in this thread, but it seems us at the optimus forums are at the beginning process of this. I did the whole booting without wiping from cm7 and got incoming text messages.

I'm going to need to talk to somebody to find out what exactly they did to get each of these features working, preferably mantera, konspiracy, progmamos, or yumbrand. If you could, PLEASE pm me with a subject that relates to this, as us at the optimus forums would REALLY need your guys' help. :)
 
gannon5197 said:
Hello. You may have seen me earlier in this thread, but it seems us at the optimus forums are at the beginning process of this. I did the whole booting without wiping from cm7 and got incoming text messages.

I'm going to need to talk to somebody to find out what exactly they did to get each of these features working, preferably mantera, konspiracy, progmamos, or yumbrand. If you could, PLEASE pm me with a subject that relates to this, as us at the optimus forums would REALLY need your guys' help. :)
Click to expand...

The problem is that everything is entirely different from this phone and the optimus V.

I think that BOBZhome said something along the effect of yall were stuck with the radio problems untill the new sprint ICS 4.0.4 (I believe?) comes out and hopefully some cdma stuff will be intergrated into telephony.

Yumbrad and Tickerguy hand coded most of our radio stuff.

Try sticking this in your build prop

ro.telephony.ril_class=QualcommNoSimReadyRIL
And tell me what happens.
 
konspiracy said:
The problem is that everything is entirely different from this phone and the optimus V.

I think that BOBZhome said something along the effect of yall were stuck with the radio problems untill the new sprint ICS 4.0.4 (I believe?) comes out and hopefully some cdma stuff will be intergrated into telephony.

Yumbrad and Tickerguy hand coded most of our radio stuff.

Try sticking this in your build prop

ro.telephony.ril_class=QualcommNoSimReadyRIL
And tell me what happens.
Click to expand...

that code is already in my build prop. I'm using the thunder prop from jolly Rodger.
 
konspiracy said:
The problem is that everything is entirely different from this phone and the optimus V.

I think that BOBZhome said something along the effect of yall were stuck with the radio problems untill the new sprint ICS 4.0.4 (I believe?) comes out and hopefully some cdma stuff will be intergrated into telephony.

Yumbrad and Tickerguy hand coded most of our radio stuff.

Try sticking this in your build prop

ro.telephony.ril_class=QualcommNoSimReadyRIL
And tell me what happens.
Click to expand...

At first, it wouldn't boot. Then, it booted but no effect. Still no phone calls or SMS or data...
 
I just pushed all of my changes up. The repo should be up-to-date with 0.6.4 now. Repo sync and you should be gtg.
 
wsimon said:
I have the voice search/input/mic working now :)

Credit goes to edowar for finding the fix. I applied his fix, built, tested and it is working.
https://github.com/edowar/android_system_core/commit/ed6934779ec56849f0825b1e3f125be5758b02ce

Mantera, I am still a github noob so I'm not sure how to do a pull request and everything. You should just have to remove those ifdefs from the audio.h file in /system/core/include/system and it'll work.
Click to expand...

I can cofirm Skype is working great! :D
 
wsimon said:
I have the voice search/input/mic working now :)

Credit goes to edowar for finding the fix. I applied his fix, built, tested and it is working.
https://github.com/edowar/android_system_core/commit/ed6934779ec56849f0825b1e3f125be5758b02ce

Mantera, I am still a github noob so I'm not sure how to do a pull request and everything. You should just have to remove those ifdefs from the audio.h file in /system/core/include/system and it'll work.
Click to expand...


Thanks. I was hoping not to have to do this. Since this would mean having to keep track of yet another repo locally. I was trying out the overlay first to see if that would work as you can see from this commit:

https://github.com/mantera/android_...mmit/b2759a4ad6743f022ede3ac5da992a6e69908e2e

However, apparently, after reading some more about it, overlays aren't meant to be used for source code and only meant for resources. doh!
http://androidforums.com/listen to this
http://www.sadtrombone.com/
 
mantera said:
Thanks. I was hoping not to have to do this. Since this would mean having to keep track of yet another repo locally. I was trying out the overlay first to see if that would work as you can see from this commit:

https://github.com/mantera/android_...mmit/b2759a4ad6743f022ede3ac5da992a6e69908e2e

However, apparently, after reading some more about it, overlays aren't meant to be used for source code and only meant for resources. doh!

Sad Trombone
Click to expand...


lol I love the trombone :)

Yeah I saw your commit afterwards and was wondering about it...
That would be nice if there were some way to overlay the source code so you wouldn't have to add the extra repos.
 
Not sure if you already have this mantera, but I would suggest making a simple script that goes through all your local repos and pulls from cyanogenmod, then pushes them out (cd, git pull, push), that way it's consistent and nothing is missed. I just synched a couple of hours and got an error when trying to build ICS.

BTW, I just want to say thanks & you're doing a great job, I can really see the MT dev community shaping up nicely.
 
Whyzor said:
Not sure if you already have this mantera, but I would suggest making a simple script that goes through all your local repos and pulls from cyanogenmod, then pushes them out (cd, git pull, push), that way it's consistent and nothing is missed. I just synched a couple of hours and got an error when trying to build ICS.

BTW, I just want to say thanks & you're doing a great job, I can really see the MT dev community shaping up nicely.
Click to expand...

Yes I do use a script. What error did you get?
 
mantera said:
Yes I do use a script. What error did you get?
Click to expand...

This is the error I when trying to build after a repo sync today, it worked my last attempt about a week ago.

Code: 
No private recovery resources for TARGET_DEVICE triumph
make: *** No rule to make target `hardware/qcom/gps/loc_api/libloc_api-rpc/inc-50001/loc_api_cb.h', needed by `out/target/product/triumph/obj/include/libloc_api-rpc/inc/loc_api_cb.h'.  Stop.
I've been getting this error for a while too, but it built fine before:

Code: 
Fetching projects: 100% (236/236), done.
Syncing work tree:   5% (12/235)  error: revision refs/heads/ics in CyanogenMod/android_device_motorola_triumph not found
Any particular reason why you're using https for repo syncs? I believe git:// protocol has more advanced features for compression & reliability. There were some issues with github a month ago but I think that's resolved now.
 
I got those errors also, what I did was delete everything in
Code: 
/home/username/android/out/target/product/triumph
repo sync and . build/envsetup.sh && brunch triumph and it built without errors
 
piper_ said:
I got those errors also, what I did was delete everything in
Code: 
/home/username/android/out/target/product/triumph
repo sync and . build/envsetup.sh && brunch triumph and it built without errors
Click to expand...

Removed out/target/product/triumph and still got that error. It may have something to do with the new qcom_gps repo being tracked is out of sync with the rest of CM9's repos.
 
Whyzor said:
Removed out/target/product/triumph and still got that error. It may have something to do with the new qcom_gps repo being tracked is out of sync with the rest of CM9's repos.
Click to expand...

A couple of weeks ago, I accidentally pushed up a hybrid cm7/cm9 manifest and python script which is causing the issues that you're experiencing now.

I didn't notice it until I was experiencing the same problems. I ended up having to scrap my cm9 repo and do a complete resync. However, after looking at what happened some more I think you can try the following and see if it solves it for you:

1. In your CM9 repo or branch, Look in your .repo folder in the root of your android working directory. See if there's a default.xml.new file in the ./repo/manifests directory. If there is, delete it. Also, if there's a tagfix.py script in that same directory, delete that as well. Try a repo sync after that and see if that fixes your issue.

2. If the above doesn't help, try deleting the gps folder and doing a git clone on just that repo to get the current.

3. If all else fails, you can dump the .repo folder and try doing a complete repo init again and resync everything again. I know that sucks and I apologize for messing up the push that day.

Regarding your question about the use of https, I switched it all to https when git was having trouble and just never got around to switching back to git. I suppose I could do that now.
 
mantera said:
A couple of weeks ago, I accidentally pushed up a hybrid cm7/cm9 manifest and python script which is causing the issues that you're experiencing now.

I didn't notice it until I was experiencing the same problems. I ended up having to scrap my cm9 repo and do a complete resync. However, after looking at what happened some more I think you can try the following and see if it solves it for you:

1. In your CM9 repo or branch, Look in your .repo folder in the root of your android working directory. See if there's a default.xml.new file in the ./repo/manifests directory. If there is, delete it. Also, if there's a tagfix.py script in that same directory, delete that as well. Try a repo sync after that and see if that fixes your issue.

2. If the above doesn't help, try deleting the gps folder and doing a git clone on just that repo to get the current.

3. If all else fails, you can dump the .repo folder and try doing a complete repo init again and resync everything again. I know that sucks and I apologize for messing up the push that day.

Regarding your question about the use of https, I switched it all to https when git was having trouble and just never got around to switching back to git. I suppose I could do that now.
Click to expand...

I think people are just getting caught up in bad syncs, because I build about once or twice a day after a fresh sync and have had zero problems.

I think git must be getting overloaded with all the DDOS attacks thats been happening.
 
You must log in or register to reply here.
Back
Top Bottom