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

Root Froyo Development

Sorry to beat a dead horse Drellisdee, but if there's no working camera I'll never use it no matter how badly I want to. I take too many random pictures of my kids to not have a camera; so yes it is a deal breaker for me.

I imagine there will be a Velocity or Raptor or whatever ROM cooked from a stock Froyo at some point so I could go to that or else go back to stock and do the official update if needed.
 
This is the best! Thank You so much drellis! I'd like to report that my headphone jack works perfectly. I haven't changed anything, modded anything, etc,. I was wondering about the baseband you used though, where did it come from?
 
Valkerie said:
Sorry to beat a dead horse Drellisdee, but if there's no working camera I'll never use it no matter how badly I want to. I take too many random pictures of my kids to not have a camera; so yes it is a deal breaker for me.

I imagine there will be a Velocity or Raptor or whatever ROM cooked from a stock Froyo at some point so I could go to that or else go back to stock and do the official update if needed.
Click to expand...

Camera is a important feature none-the-less, but you need to understand this is in Alpha stage(idk why people keep saying beta, it is no where close).
 
Quick question, if I try AOSP15 and then want to switch back, will I be able to get rom manager working on the phone again or at least be able to hook up to my PC and do the reset to stock method by pushing the old firmware and then reupdating again and going back to Velocity?
 
getitnowmarketing said:
Yes I'm personally on build 17 and have gps working. I only upload when I have a chance and have an improvement. Camera may not ever be working on an aosp build as Lg made extensive changes to the libcamera.so (extra camera modes etc.) that a large portion of android build process is linked against. Even with a froyo camera for ally stripped from an official 2.2 it still will error the whole android open source build process. A solution may be found and I have a untested idea but for the forseeable future its a feature that will NOT be working. I'd appreciate it if people stop talking about it (camera) and help with other things that can be made working.
Click to expand...

So the gps is only working 100% only in build 17?
 
Well hopefully build 17 will be released soon, can't wait to test this out but I need my gps working as I use it for finding clients for work.
 
CTroxtell said:
Well hopefully build 17 will be released soon, can't wait to test this out but I need my gps working as I use it for finding clients for work.
Click to expand...

I'm gonna go out on a limb here, but if you rely on your phone to help in earning a living, flashing and experimenting with it may not be the best idea. I don't mean to be brash, but alot of people here are spouting off "I need this because I need my phone for this, etc". These builds are experimental, and the real purpose here was to aid drellisdee in getting the build debugged before releasing it the general public, you know, the people that rely on their phones on a daily basis.
 
username.unknown said:
I'd like to report that my headphone jack works perfectly.
Click to expand...

Can you post a logcat when you plug in the headphones? Also the type of headphones used? (double ring or triple ring, etc.)

That would be cool if you can confirm the headphone jack works 100% of the time.
 
AlexMason said:
Camera is a important feature none-the-less, but you need to understand this is in Alpha stage(idk why people keep saying beta, it is no where close).
Click to expand...

This I understand and I have complete faith in the devs here to get things working as they should work.

Like I said, there's always a flash back to stock and OTA update if needed...worst case scenario.
 
Originally Posted by flick159
Believe it has been reported as haptic feedback not working. However the on screen keyboard's haptic works fine.
im saying when a call comes in it will not vibrate
Click to expand...

It seems odd to because there both obviously based on the same hardware.
 
flick159 said:
Can you post a logcat when you plug in the headphones? Also the type of headphones used? (double ring or triple ring, etc.)

That would be cool if you can confirm the headphone jack works 100% of the time.
Click to expand...

I'm using double ring headphones. Here's my logcat.
Code: 
V/HeadsetObserver( 1358): Headset UEVENT: {SUBSYSTEM=switch,
SWITCH_STATE=2, DEV
PATH=/devices/virtual/switch/h2w, SEQNUM=1285, ACTION=change, SWITCH_NAME=h2w}
W/Vold    ( 1175): Ignoring unknown switch 'h2w'
W/UsbController( 1177): Ignoring unknown switch 'h2w'
V/HeadsetObserver( 1358): Intent.ACTION_HEADSET_PLUG: state: 1 name: h2w mic: 0
D/PhoneApp( 1464): handleQueryTTYModeResponse: TTY enable state successfully que
ried.
D/PhoneApp( 1464): handleQueryTTYModeResponse:ttymode=0






E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
E/dun_service( 1191): process rmnet event
E/dun_service( 1191): Post event 3
V/HeadsetObserver( 1358): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=0, DEV
PATH=/devices/virtual/switch/h2w, SEQNUM=1286, ACTION=change, SWITCH_NAME=No Dev
ice}
W/Vold    ( 1175): Ignoring unknown switch 'No Device'
W/UsbController( 1177): Ignoring unknown switch 'No Device'
V/HeadsetObserver( 1358): Intent.ACTION_HEADSET_PLUG: state: 0 name: No Device m
ic: 0
D/PhoneApp( 1464): handleQueryTTYModeResponse: TTY enable state successfully que
ried.
D/PhoneApp( 1464): handleQueryTTYModeResponse:ttymode=0

The first block is me plugging in the headphones and the second part (minus the stuff about dun) is me unplugging the headphones.
 
Aosp21:

Fixed:
Headset audio (required rewriting libaudio.so for a non-htc phone)
Youtube (plays both SD and HD but not as fast as I'd like)
MMS (needs tester)
GPS (both aGps & sGps)
Keyboard backlight
Changed from javascript to V8 browser engine.

I'd also like to say : Keep Out of Browsing my FTP. I had some personal stuff in there and if it happens again there will be no more public releases from me for ANYTHING!!!

I'd like to say thanks to the openetna project that had the audio headset fix and keyboard slideout fix for LG Eve that I used.

Aosp21

same password as last time.
 
Outstanding. Will be donating tomorrow(payday). You are truly amazing drell. Will post a logcat if any bugs are found. Thanks again.
 
getitnowmarketing said:
Aosp21:

Fixed:
Headset audio (required rewriting libaudio.so for a non-htc phone)
Youtube (plays both SD and HD but not as fast as I'd like)
MMS (needs tester)
GPS (both aGps & sGps)
Keyboard backlight
Changed from javascript to V8 browser engine.

I'd also like to say : Keep Out of Browsing my FTP. I had some personal stuff in there and if it happens again there will be no more public releases from me for ANYTHING!!!

I'd like to say thanks to the openetna project that had the audio headset fix and keyboard slideout fix for LG Eve that I used.

Aosp21

same password as last time.
Click to expand...

Thanks Dre, BTW i was the one who donated you 6$ the other day when you released aosp15, Vapcdoc@gmail.com here, thanks for all your work man
 
getitnowmarketing said:
Aosp21:

Fixed:
Headset audio (required rewriting libaudio.so for a non-htc phone)
Youtube (plays both SD and HD but not as fast as I'd like)
MMS (needs tester)
GPS (both aGps & sGps)
Keyboard backlight
Changed from javascript to V8 browser engine.

I'd also like to say : Keep Out of Browsing my FTP. I had some personal stuff in there and if it happens again there will be no more public releases from me for ANYTHING!!!

I'd like to say thanks to the openetna project that had the audio headset fix and keyboard slideout fix for LG Eve that I used.

Aosp21

same password as last time.
Click to expand...

thanks for fixing the GPS, I'm getting ready to do some winter travelling and happy to have this back. MMS works fine for me as near as I can tell. Didn't the original MMS have 2 themes a light and dark? The MMS app in this Froyo doesn't seem to be able to be changed off of light.

I will be sure to let you know if I have any issues. SO far it's running great, a little heavy on battery when using online apps, but otherwise I can't complain.

I am assuming the wireless tether is still broken? it launches the app, but then errors out with a message about not being able to tether.

Great job, again. I'm not making promises, but I do INTEND on donating, just need a little bit more Christmas money. HA haha.
 
k.c.cole said:
thanks for fixing the GPS, I'm getting ready to do some winter travelling and happy to have this back. MMS works fine for me as near as I can tell. Didn't the original MMS have 2 themes a light and dark? The MMS app in this Froyo doesn't seem to be able to be changed off of light.

I will be sure to let you know if I have any issues. SO far it's running great, a little heavy on battery when using online apps, but otherwise I can't complain.

I am assuming the wireless tether is still broken? it launches the app, but then errors out with a message about not being able to tether.

Great job, again. I'm not making promises, but I do INTEND on donating, just need a little bit more Christmas money. HA haha.
Click to expand...

Go into Manage Applications and clear data for the Wireless Tether. Then reinstall using method of your choice.
 
I just noticed I don't have keyboard back light with aosd21. Did I do something wrong with the install? I am not familiar with the logcat, so if you want one you'll have to ppint me in the right direction.

Does our browser have the google dns? It seems alittle slower than the velocity browser.
Also is there any possibility of getting some of tridents script like ad block?

When I installed aosp21 I wiped the caches then flashed then flashed gapps and restarted. I did not wide data. All of the apps were there and the theme by GRZLA was now. I am fairly sure I have the new build but i didn't pay enough attention to the "About" section to know what should be there now. I did verify the GPS so I'm pretty sure that it took.
 
k.c.cole said:
I just noticed I don't have keyboard back light with aosd21. Did I do something wrong with the install? I am not familiar with the logcat, so if you want one you'll have to ppint me in the right direction.

Does our browser have the google dns? It seems alittle slower than the velocity browser.
Also is there any possibility of getting some of tridents script like ad block?

When I installed aosp21 I wiped the caches then flashed then flashed gapps and restarted. I did not wide data. All of the apps were there and the theme by GRZLA was now. I am fairly sure I have the new build but i didn't pay enough attention to the "About" section to know what should be there now. I did verify the GPS so I'm pretty sure that it took.
Click to expand...

The keyboard backlight works for me. I would wipe data, clear cache and dalvik cache, flash AOSP21, reboot. Then go back into recovery, wipe cache and dalvik cache and then flash gapps. See if that works. There is an app on the market, can't recall the name at the moment, that blocks ads quite well.
 
You must log in or register to reply here.
Back
Top Bottom