im concentrating more on bugs for the moment trying to iron out as much as possible and pass anything i find to the main developer (ie the chmod 04755 /system/bin/su thing). Prettiness can come later. What i would love is a kernel

ZTE Blade/San Francisco Unofficial Froyo Build
Started by
Stephen Hyde
, Oct 22 2010 10:54 PM
#501
Posted 27 October 2010 - 03:43 PM
#502
Posted 27 October 2010 - 04:50 PM
Sure, no pb... I am using the Alpha in the meantime (mostly fo the automatic SIM unlock, btw isn't this great ?!?)
#503
Posted 27 October 2010 - 05:01 PM
Just trying this out. Looking great from my first tests. Not got any problems with the calendar that I've noticed... Apart from now it manages to sync with exchange, I get duplicates because I sync'd my exchange calendar with my google calendar. So, I'm getting both versions of an event... lol. Fortunately, also, I haven't had any probs with the calendar force closing. Does this only happen when trying to do certain things?!
#504
Posted 27 October 2010 - 05:11 PM
I haven't seen any mention of voice dialing. Is it present in this build? If so has anyone tried it?
#505
Posted 27 October 2010 - 05:25 PM
I had a bit of an discovery on the 'Dialer' bug today (shown using most of the battery). So, I decided to try to freeze all three 'Dialer' entries with Titanium Backup and then to use a third-party dialer (Dialer One) to see if I could get the battery usage (reporting) to drop. The interesting thing I learned was when 'Dialer Storage 2.2' was frozen, I completely lost the phone/radio function. I also got frequent FC messages on com.android.phone. So, this all leads me to believe the native 'Dialer' is, in fact, integrated with the phone/radio and perhaps it is frequently (too frequently?) polling the mobile towers which is taking a hit on our batteries and causing the reporting of such high numbers under battery usage. Not a fix/workaround, but maybe that will help someone develop a fix/around? Perhaps there is a way to hack the /system/app/Phone.apk and change some setting where it's not so active?
I still have not figured out why some mp3s I have play (music I've ripped) and other don't (low-fi lectures with no DRM or anything - they play fine in 2.1).
I still have not figured out why some mp3s I have play (music I've ripped) and other don't (low-fi lectures with no DRM or anything - they play fine in 2.1).
#506
Posted 27 October 2010 - 05:51 PM
abdn-android, on Oct 27 2010, 18:25, said:
I had a bit of an discovery on the 'Dialer' bug today (shown using most of the battery). So, I decided to try to freeze all three 'Dialer' entries with Titanium Backup and then to use a third-party dialer (Dialer One) to see if I could get the battery usage (reporting) to drop. The interesting thing I learned was when 'Dialer Storage 2.2' was frozen, I completely lost the phone/radio function. I also got frequent FC messages on com.android.phone. So, this all leads me to believe the native 'Dialer' is, in fact, integrated with the phone/radio and perhaps it is frequently (too frequently?) polling the mobile towers which is taking a hit on our batteries and causing the reporting of such high numbers under battery usage. Not a fix/workaround, but maybe that will help someone develop a fix/around? Perhaps there is a way to hack the /system/app/Phone.apk and change some setting where it's not so active?
I still have not figured out why some mp3s I have play (music I've ripped) and other don't (low-fi lectures with no DRM or anything - they play fine in 2.1).
I still have not figured out why some mp3s I have play (music I've ripped) and other don't (low-fi lectures with no DRM or anything - they play fine in 2.1).
re mp3's
I found it was just the wma's that didnt work........codec?
walk wild walk free! and die living!
#507
Posted 27 October 2010 - 05:57 PM
abdn-android, on Oct 27 2010, 18:25, said:
I had a bit of an discovery on the 'Dialer' bug today (shown using most of the battery). So, I decided to try to freeze all three 'Dialer' entries with Titanium Backup and then to use a third-party dialer (Dialer One) to see if I could get the battery usage (reporting) to drop. The interesting thing I learned was when 'Dialer Storage 2.2' was frozen, I completely lost the phone/radio function. I also got frequent FC messages on com.android.phone. So, this all leads me to believe the native 'Dialer' is, in fact, integrated with the phone/radio and perhaps it is frequently (too frequently?) polling the mobile towers which is taking a hit on our batteries and causing the reporting of such high numbers under battery usage. Not a fix/workaround, but maybe that will help someone develop a fix/around? Perhaps there is a way to hack the /system/app/Phone.apk and change some setting where it's not so active?
I still have not figured out why some mp3s I have play (music I've ripped) and other don't (low-fi lectures with no DRM or anything - they play fine in 2.1).
I still have not figured out why some mp3s I have play (music I've ripped) and other don't (low-fi lectures with no DRM or anything - they play fine in 2.1).
#508
Posted 27 October 2010 - 11:02 PM
ive got my froyo build to work fine, im having no problems AT ALL with the marketplace?, the only isssues I have are that the music player won't play some songs for whatever reason?, and the GPS won't find my location.. but apart from that the phone is loads faster than what it was on 2.1. Thanks for the release looking forward to future builds. Keep up the good work! 
#509
Posted 28 October 2010 - 12:09 AM
abdn-android, on Oct 27 2010, 18:25, said:
The interesting thing I learned was when 'Dialer Storage 2.2' was frozen, I completely lost the phone/radio function. I also got frequent FC messages on com.android.phone.
If I understand correctly the dialler storage 2.2 process makes copies of (or possibly archives?), SMS/MMS data and possibly other phone related info to one or more sqlite databases under /data/data/com.android.providers.telephony/databases
If that process is busy can you see an increase in the size of the mmssms.db file in that location?
(I don't have this ROM loaded so can't check myself).
#510
Posted 28 October 2010 - 12:48 AM
Right I have done both a full clockwork backup and a full titanium backup before installing 2.2
Obviously by following the installation instructions I am going to be wiping all data etc from the phone before applying the 2.2 update
So I was wondering if getting the phone back to how I have it now with all the data apps etc as it is will just be as simple as running a clockwork restore/titanium backup restore, if not can someone give me an idiots guide
Failing that if I want to go back to 2.1 (how i have it now, Pauls r4) will i just need to run that update.zip through clockwork and then perform clockwork restore to return phone to the current state
Obviously by following the installation instructions I am going to be wiping all data etc from the phone before applying the 2.2 update
So I was wondering if getting the phone back to how I have it now with all the data apps etc as it is will just be as simple as running a clockwork restore/titanium backup restore, if not can someone give me an idiots guide
Failing that if I want to go back to 2.1 (how i have it now, Pauls r4) will i just need to run that update.zip through clockwork and then perform clockwork restore to return phone to the current state
Edited by johntrfc, 28 October 2010 - 12:50 AM.
#511
Posted 28 October 2010 - 01:58 AM
big thanks to everyone working on this and all the helpfull comments im a noob and for some reason i cant get anything google to sync wont let me in market but the thing is ive flashed my psp ive had my phone on every rom going lol all worked compliments to everyone ive been reading every thread and everyone seems to be running market flawlessly now and ive tried it all clearing cache partition and privacy even formatted sd card setting tried to sign on 3g 1st i hope this is in the right thread could anyone else comment if having this problem please p.s sorry about the english 
#512
Posted 28 October 2010 - 07:02 AM
Does anyone know why bluetooth HID doesn't work in this 2.2 rom? It works in pretty much every other Froyo rom out there...
#513
Posted 28 October 2010 - 08:19 AM
JolyonS, on Oct 28 2010, 01:09, said:
If I understand correctly the dialler storage 2.2 process makes copies of (or possibly archives?), SMS/MMS data and possibly other phone related info to one or more sqlite databases under /data/data/com.android.providers.telephony/databases
If that process is busy can you see an increase in the size of the mmssms.db file in that location?
(I don't have this ROM loaded so can't check myself).
If that process is busy can you see an increase in the size of the mmssms.db file in that location?
(I don't have this ROM loaded so can't check myself).
I also belive this to be true, with my hero the biggest issue with battery was google backup. When you add your accounts and s*** it asks you if you want google to back stuff up. Say no otherwise your battery will be googles personal hooker every 20 seconds (xD).
Battery life issues? Turn off google backup sync!
#514
Posted 28 October 2010 - 12:39 PM
Open Issues:
MP3 - notifications.
I looked at the MP3 playing problems and it seems to be that the complete integration of MP3 decoding is not finished in the Chinese ROM, on which the alpha is based on.
I checked, with various MP3`s and some play some not. This depends on the structure of the MP§ ( if lenght is correctly displayed and so on). If you have badly encoded MP3, with wrong metadata, usally they do not play.
So i can´t imagine there will be a fix until the source comes up
a-GPS:
As written also in the other thread, in my gps.conf intermediate mode was activated, which sends "intermediate" GPS coordinates to GPS enabled apps before it gets the final fix.
You can just turn this off if you change the INTERMEDIATE = 1 switch to INTERMEDIATE = 0 ..
FM-Radio:
Seems to be a bug somewhere in the audio-hardware driver (looks to me like a typo in a function call) and without source it is the same situation as the MP3-problem. (BTW: Switching the FM-app from stock does not work
)
Bluetooth:
There is a problem in the setup of the Bluetooth profiles on startup, but you can fix it very easy
type following commands
adb shell
cd /system/etc/bluetooth
chmod 644 *
reboot
Audio Routing:
On Boot there are some parameters set. The require the files AudioFilter.csv /system/etc
You can extract this file from the stock rom and place it into /system/etc
I don`t have a clue what it does, but at least the error message is gone.
That`s all folks.
MP3 - notifications.
I looked at the MP3 playing problems and it seems to be that the complete integration of MP3 decoding is not finished in the Chinese ROM, on which the alpha is based on.
I checked, with various MP3`s and some play some not. This depends on the structure of the MP§ ( if lenght is correctly displayed and so on). If you have badly encoded MP3, with wrong metadata, usally they do not play.
So i can´t imagine there will be a fix until the source comes up
a-GPS:
As written also in the other thread, in my gps.conf intermediate mode was activated, which sends "intermediate" GPS coordinates to GPS enabled apps before it gets the final fix.
You can just turn this off if you change the INTERMEDIATE = 1 switch to INTERMEDIATE = 0 ..
FM-Radio:
Seems to be a bug somewhere in the audio-hardware driver (looks to me like a typo in a function call) and without source it is the same situation as the MP3-problem. (BTW: Switching the FM-app from stock does not work
Bluetooth:
There is a problem in the setup of the Bluetooth profiles on startup, but you can fix it very easy
type following commands
adb shell
cd /system/etc/bluetooth
chmod 644 *
reboot
Audio Routing:
On Boot there are some parameters set. The require the files AudioFilter.csv /system/etc
You can extract this file from the stock rom and place it into /system/etc
I don`t have a clue what it does, but at least the error message is gone.
That`s all folks.
#515
Posted 28 October 2010 - 01:05 PM
tocixxx, on Oct 28 2010, 14:39, said:
Bluetooth:
There is a problem in the setup of the Bluetooth profiles on startup, but you can fix it very easy
type following commands
adb shell
cd /system/etc/bluetooth
chmod 644 *
reboot
There is a problem in the setup of the Bluetooth profiles on startup, but you can fix it very easy
type following commands
adb shell
cd /system/etc/bluetooth
chmod 644 *
reboot
Will this enable bluetooth HID mode?
EDIT: It didn't
Edited by nilezon, 28 October 2010 - 02:14 PM.
#516
Posted 28 October 2010 - 02:57 PM
See forum
http://android.modac...te-blade-alpha/
Which is based on this rom with some tweaks and fixes (most mentioned in this thread)
http://android.modac...te-blade-alpha/
Which is based on this rom with some tweaks and fixes (most mentioned in this thread)
#517
Posted 28 October 2010 - 08:44 PM
noticed how intallation of this allowed more icons and exceptional web browsing.. was wondering is there something like this avail for the HTC Wildfire as this would be ideal....
#518
Posted 02 November 2010 - 08:46 AM
hi dnt no y but i keep getting "google talk authentication failed" error message and there for i think it is stopping me from downloading from the app store anyway of fixing this? thnx
#519
Posted 02 November 2010 - 10:42 AM
lilzad, on Nov 2 2010, 08:46, said:
hi dnt no y but i keep getting "google talk authentication failed" error message and there for i think it is stopping me from downloading from the app store anyway of fixing this? thnx
see 4th post in
http://android.modac...te-blade-alpha/
#520
Posted 02 November 2010 - 11:03 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users







Sign In
Create Account

Back to top









