Hi Guys,
I will be in Delhi from the 13th till the 20th. I would like to take my FR
in for the buzzfix at Baig Electronics preferably on the 13th/14th or the
15th if possible.
Can you let me know what I need to do?
Thanks
--
View this message in context:
http://n2.nabble.com/Re-Fwd
rakshat hooja wrote:
Try this kernel
http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin
with your OM2009 installation if you dont want to experiment with your
rootfs right now.
Otherwise also try
PS: BTW, we got the buzz fix in roughly this
[http://3.bp.blogspot.com/_0EJ0z3prPXM/SqPZg8Zy1gI/Ars/0wRUtSvmFfg/s400/attachment-0001.jpeg]
way
you mean 1024 fix?
oopsyup, that pic is for 1024 fix :)
___
Openmoko community mailing list
On Thursday 17 September 2009 04:59:45 Vikas Saurabh wrote:
1024 fix: I am on SHR-U so avoiding deep sleep was just 1 line of
config. Anyways, after the fix I have removed that line and haven't
You should edit it, not remove it:
Change:
ti_calypso_deep_sleep = never
to
You should edit it, not remove it:
Change:
ti_calypso_deep_sleep = never
to
ti_calypso_deep_sleep = always
oh...the comment in the file said that adaptive was default...and i
kinda like the word 'adaptive' (sounds catchy :)...should I change it
to 'always' anyways
Vikas Saurabh wrote:
You should edit it, not remove it:
Change:
ti_calypso_deep_sleep = never
to
ti_calypso_deep_sleep = always
oh...the comment in the file said that adaptive was default...and i
kinda like the word 'adaptive' (sounds catchy :)...should I change it
to
Vibhav Sharma wrote:
Vikas Saurabh wrote:
You should edit it, not remove it:
Change:
ti_calypso_deep_sleep = never
to
ti_calypso_deep_sleep = always
I changed it to 'always', rebooted the phone. The follwing is now
happening.
Sometimes the phone will not
Update, adaptive also results in same behaviour, changed to 'never' and
seems ok now (for the past hour anyway).
Need to work out whether the fix not proper or something else causing the
behaviour.
For me I am not seeing any issues(issue with resume) with either
adaptive or never. So I have
On Thu, Sep 17, 2009 at 6:03 PM, Vikas Saurabh vikas.saur...@gmail.comwrote:
Update, adaptive also results in same behaviour, changed to 'never' and
seems ok now (for the past hour anyway).
Need to work out whether the fix not proper or something else causing the
behaviour.
For me I
- So it took you 3 days to get the phone back? I'm likely to be in
Delhi around the 15th or so for about a week. Hopefully I can get the phone
fixed in that time.
--
View this message in context:
http://n2.nabble.com/Re-Fwd-buzzfix-in-India-tp380p3662751.html
Sent from the Openmoko Community
- So it took you 3 days to get the phone back? I'm likely to be in
Delhi around the 15th or so for about a week. Hopefully I can get the phone
fixed in that time.
--
View this message in context:
http://n2.nabble.com/Re-Fwd-buzzfix-in-India-tp380p3662782.html
Sent from the Openmoko Community
rakshat hooja wrote:
bootloader, kernel, rootfs?
Try this kernel
http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin
with your OM2009 installation if you dont want to experiment with your
rootfs right now.
Otherwise also try
c_c wrote:
Hi,
Are you on the latest shr-U? T
Om2009t5 which has been opkg update/upgraded.
But the sep releases have so far been fine for me. Maybe you should
re-install on another partition, upgrade and confirm that the problem still
persists. There have been issues in upgrading
Vikas, how is your battery holding up without any charging?
47% since 9 am. If I click the illume-battery-gadget soon after
resume, it shows some 28 hours remaining (I think thats what coulomb
counter is reporting)
--Vikas
___
Openmoko community
On Thu, Sep 17, 2009 at 8:36 PM, Vikas Saurabh vikas.saur...@gmail.com wrote:
Vikas, how is your battery holding up without any charging?
47% since 9 am
I mean haven't put the phone on charging since 9 am...it was on 100%
when i disconnected..btw, strangely first 20% dropped pretty fast
On Thu, Sep 17, 2009 at 8:38 PM, Vikas Saurabh vikas.saur...@gmail.comwrote:
On Thu, Sep 17, 2009 at 8:36 PM, Vikas Saurabh vikas.saur...@gmail.com
wrote:
Vikas, how is your battery holding up without any charging?
47% since 9 am
I mean haven't put the phone on charging since 9 am...it
- So it took you 3 days to get the phone back? I'm likely to be in
Delhi around the 15th or so for about a week. Hopefully I can get the phone
fixed in that time.
--
View this message in context:
http://n2.nabble.com/Re-Fwd-buzzfix-in-India-tp380p3664045.html
Sent from the Openmoko Community
Hi,
Vibhav Sharma wrote:
Great. Let us Delhi wallas know if you have time. We could try arranging
a meetup when you are around.
Sure. I'll post here when the program is finalised. Thanks.
--
View this message in context:
http://n2.nabble.com/Re-Fwd-buzzfix-in-India-tp380p3664128
On Thu, Sep 17, 2009 at 9:28 PM, rakshat hooja raks...@gmail.com wrote:
On Thu, Sep 17, 2009 at 8:38 PM, Vikas Saurabh vikas.saur...@gmail.com
wrote:
On Thu, Sep 17, 2009 at 8:36 PM, Vikas Saurabh vikas.saur...@gmail.com
wrote:
Vikas, how is your battery holding up without any charging?
A lot of thanks to IDA Systems (Rakshat and Zoheb) as Vibhav and I
finally get the buzz fix done. And alongwith that our phones got
blessed with the 1024 fix as well :D.
Sorry for no pics of the naked moko being fixed.
Regarding the fixes:
Buzz fix: I (recepients of my calls) haven't been
On Thu, Sep 17, 2009 at 8:29 AM, Vikas Saurabh vikas.saur...@gmail.comwrote:
--Vikas
PS: BTW, we got the buzz fix in roughly this
[
http://3.bp.blogspot.com/_0EJ0z3prPXM/SqPZg8Zy1gI/Ars/0wRUtSvmFfg/s400/attachment-0001.jpeg
]
way
you mean 1024 fix?
Rakshat
Things are moving a little slow out here, so I think I should at least
start trying to look for components.
Hi All,
Zoheb from IDA systems is in Delhi these days and the Delhi FR owners
(basically just Vibhav and me :) are going to get our phones fixed on
Wednesday. We are going for buzz fix
I tried to look for component for 1024 but 22uF-0805-ceramic capacitor
was nowhere to be found.
You can order Ceramic Cap : 22uF-0805 in India from Farnell here:
http://in.farnell.com/kemet/c0805c226m9pac7800/capacitor-0805-22uf-x5r/dp/1108326
Here is the Delhi Sales office address:
*New
You can order Ceramic Cap : 22uF-0805 in India from Farnell here:
http://in.farnell.com/kemet/c0805c226m9pac7800/capacitor-0805-22uf-x5r/dp/1108326
I am already too tired of delaying the fix to delay it any further.
So, I would be going with 10uF (Vibhav might differ???). But useful
link for
Further reading:
1024::
Hi All,
Shamsul Hassan from Bangalore has posted
http://neofundas.blogspot.com/2009/09/1024-hardware-fixdeep-sleep.html
regarding the various options about the 1024 fix.
Shamsul is basically an elec and comm guy so I believe he would be
able to assess various fixes with
Hi,
I live in Bangalore and have an FR-A5. I am actually in the process of
getting buzz fix done through a local talent (acquaintance/colleague). I
need to find time to buy the components (0402: 2.2K and the tantalum cap)
and coach him on what needs to be done.
I am open to sending the
[cut]
I have updated
http://wiki.openmoko.org/wiki/Community_Updates/Draft_2009-09-02#Community.
Hope thats fine!
I just wanted to be sure about date, by ...on Apr 20th. you mean
2010-04-10 ??? Isn't it too early for announcing?
--
Kind Regards, Patryk LeadMan Benderz
On Tue, Sep 1, 2009 at 1:54 PM, Vikas Saurabh wrote:
Shashank Bharadwaj ()
FR - A6 (I think)
--
Regards
Shashank
As our circle of knowledge expands, so does the circumference of
darkness surrounding it - Albert Einstein
___
Openmoko community
I just wanted to be sure about date, by ...on Apr 20th. you mean
2010-04-10 ??? Isn't it too early for announcing?
Ah...sorry my mistake..
I actually wanted to mention 20Apr2009 when Rakshat first sent off a
mail on this list to announce that IDA Systems would be having a buzz
fix program in
Vikas Saurabh wrote:
Vibhav Sharma (FR - ??)
@Vikas,
was waiting for your update. I too have been busy but will have time
from next week. Let me know if you need any help.
I have a FR - A5, in for Buzz and Bug #1024 atleast. Let me see about
the Bass.
-- Vibhav Sharma (khoonirobo)
Dnia 2009-09-02, śro o godzinie 13:57 +0200, Patryk Benderz pisze:
[cut]
I actually wanted to mention 20Apr2009 when Rakshat first sent off a
But April was in the past. How can you tell people that this party will
be organized in the past? I don't get it, is it something wrong with me?
OK, i
[cut]
I actually wanted to mention 20Apr2009 when Rakshat first sent off a
But April was in the past. How can you tell people that this party will
be organized in the past? I don't get it, is it something wrong with me?
--
Kind Regards, Patryk LeadMan Benderz
Linux
If so, i would change text on CU from:
IDA Systems had announced buzz fix for Indian customers on Apr 20th
to:
On Apr 20th, IDA Systems had announced buzz fix for Indian customers.
Exact date of buzz fix is not known yet...
I copied your text and have updated the text :)
Let me know if you need any help.
I think right now we have to figure out how to get FRs here. As of
now, Chaitanya is in Payyannur(Kerala) and it might not be easy for
him to send in his FR. He said that he would be here (Delhi) around
Diwali, so that might be a good time to have the buzz fix
Hi guys,
First off, I am terribly sorry for the delay. I was too busy with work
of late. Anyways, I guess we need to plan on the dates and mode of
transport of phones to NCR.
Till now, I know of only following people (through this mail chain):
NCR:
Gora Mohanty (1973)
Vibhav Sharma (FR - ??)
/me
Dnia 2009-09-01, wto o godzinie 13:54 +0530, Vikas Saurabh pisze:
Hi guys,
First off, I am terribly sorry for the delay. I was too busy with work
of late. Anyways, I guess we need to plan on the dates and mode of
transport of phones to NCR.
Till now, I know of only following people
You might get some luck by announcing it on CU. Depends on how soon do
you plan to organize fix party. Is it better to announce tomorrow, or on
next CU?
[cut]
I have updated
http://wiki.openmoko.org/wiki/Community_Updates/Draft_2009-09-02#Community.
Hope thats fine!
--Vikas
the initiative to set this up.
--
View this message in context:
http://n2.nabble.com/Re-Fwd-buzzfix-in-India-tp380p3564569.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community mailing list
community
Vikas Saurabh wrote:
Alok G. Singh ()
FR - A7, afaict.
--
Alok
Your aim is high and to the right.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Mon, Aug 17, 2009 at 06:13:11PM +0530, Vikas Saurabh wrote:
Anyways, for bass fix there is a wiki page
(http://wiki.openmoko.org/wiki/GTA02_bass_fix) which suggests more
that one way of fixing the issue with pros and cons
There is also some discussion about the type of capacitor to use
@Rakshat: how many FRs do we have in India?
approx 150 freerunners in India through us and (my guess) about 20 ordered
directly form OM.
Rakshat
___
Openmoko community mailing list
community@lists.openmoko.org
[cut]
We are planning a buzz fix for FRs in India. As Rakshat has already
Do you pplan it on any particular date? IMHO it is worth to put it into
CU, but need date details also.
[cut]
--
Kind Regards, Patryk LeadMan Benderz
Linux Registered User #377521
() ascii
Do you pplan it on any particular date? IMHO it is worth to put it into
CU, but need date details also.
We haven't yet decided on the dates. In fact we were trying to figure
out if we can do #1024 and bass fix as well alongwith buzz fix. I have
been neck-deep in work this week and i think same
On Sat, Aug 22, 2009 at 12:51 AM, Vikas Saurabhvikas.saur...@gmail.com wrote:
Then we would call for the FR from outside Delhi (I know only 2 up
till now...chetan and alok...both, i guess, in bangalore) and then get
them for fix. I thought sending the FRs is a far bigger problem than
actually
On a related note, the fix for #1024 and the bass boost as well as the
shorting of the erroneous capacitor[1] (if present) would be a welcome
addition to the Buzz fix. It seems a reasonable amount of effort to send
the phone and it would make sense to do as much as possible on this one
trip.
Vikas Saurabh wrote:
On a related note, the fix for #1024 and the bass boost as well as the
shorting of the erroneous capacitor[1] (if present) would be a welcome
addition to the Buzz fix. It seems a reasonable amount of effort to send
the phone and it would make sense to do as much as
Hi All,
We are planning a buzz fix for FRs in India. As Rakshat has already
pointed out, the guy who would do the buzz fix is placed at Delhi. IDA
systems would be bearing the cost of buzz fix while we need to take
care of sending in the devices and take it back.
People in Delhi itself can of
Hi,
I would like to get my FR buzz fixed too. I was kind of hoping we could
get the #1024 (modem deep sleep) and the bass workaround for the earphones
done at the same time. Particularly #1024 since it really seems to seriously
improve battery life. Both require adding additional capacitors in
I would like to get my FR buzz fixed too. I was kind of hoping we could
get the #1024 (modem deep sleep) and the bass workaround for the earphones
done at the same time. Particularly #1024 since it really seems to seriously
improve battery life. Both require adding additional capacitors in
On Fri, Aug 14, 2009 at 7:56 PM, Vikas Saurabh vikas.saur...@gmail.comwrote:
I would like to get my FR buzz fixed too. I was kind of hoping we could
get the #1024 (modem deep sleep) and the bass workaround for the
earphones
done at the same time. Particularly #1024 since it really seems
Vikas Saurabh wrote:
While I don't know about postage options, I think the package can
still be sent to one of us (users) and we would take all the FRs to
the guy at the same time.
I have been trying to send my GTA02 to IDA Systems in Jaipur as per
Rakshat's email. It is not as simple as
rakshat hooja wrote:
Also I can mail the batteries to the repair shop or to one of you. Let me
know how that should be done.
Batteries need to shipped separately according to Blue Dart. It might be
better to just ship them individually.
--
Alok
52 matches
Mail list logo
