Closed
Bug 859260
Opened 12 years ago
Closed 12 years ago
[Leo] Cellular and Data is not working on leo devices
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(blocking-b2g:leo+)
RESOLVED
WORKSFORME
blocking-b2g | leo+ |
People
(Reporter: atsai, Unassigned)
References
Details
(Keywords: regression, smoketest, Whiteboard: leo)
Attachments
(6 files)
Reproduce step:
./config.sh leo
./build.sh
./flash.sh
after manually changing the status of system/b2g/b2g and system/b2g/plugin-container.
The device is able to boot but at Settings>>Cellular&Data will show "Unknown SIM card state" and the device is not able to make call or sending SMS.
Comment 1•12 years ago
|
||
I tried to clone the leo environment today but I can't reproduce this issue. The message I saw is "SIM card is not ready" and it belongs to another bug 857462. I need to verify the way to reproduce it.
Keywords: qawanted
Updated•12 years ago
|
Assignee: nobody → vliu
In yesterday's build I was able to get a mobile data connection on Leo. (.60)
In Today's build is not connecting to the mobile data. (.62)
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/950db80b82cb
Gaia 54ab4ce3f9107d1624c18bed2a09ace6bbc6601f
BuildID 20130412070204
Version 18.0
Leo
RIL : ril01.01.00.019.062
blocking-b2g: --- → leo?
![]() |
||
Updated•12 years ago
|
Severity: normal → blocker
Going to settings -> Cellular & Data -> Network operator and changing from automatic selection shows no network operators in the area. It is continually on Searching. Unagi shows otherwise.
mvines, could you ask someone to take a look into the ril if this is not a known issue please? it was working for me in .60
Oh it looks like the manifest is looking at the wrong place from the log:
04-12 17:38:31.039: E/GeckoConsole(501): Could not read chrome manifest 'file:///system/b2g/distribution/bundles/libqc_b2g_ril.version/chrome.manifest'.
Shouldn't it be file:///system/b2g/distribution/bundles/libqc_b2g_ril/chrome.manifest ?
Comment 5•12 years ago
|
||
Is that error fatal? That's a text file that gets added to indicate which version of the RIL is present. Looks like we need to move it out of the way at the very least.
I'm not sure if the manifest is a red herring or not; it's something I caught in the log file.
mvines? May we get some assistance please?
Flags: needinfo?(mvines)
Comment 7•12 years ago
|
||
That's something releng is adding to the device.
Comment 8•12 years ago
|
||
This issue happens in qcril and need help from mvines. I will set the assignee to him.
Assignee: vliu → mvines
![]() |
Reporter | |
Updated•12 years ago
|
QA Contact: atsai
Comment 9•12 years ago
|
||
Data WFM on the tip v1-train Gecko/RIL on Leo
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(mvines)
Resolution: --- → WORKSFORME
I think we need the latest RIL. This is still not working:
leo-mozilla-b2g18-20130415070205-ril01.01.00.019.065
Comment 11•12 years ago
|
||
I reopen this bug for further investigation because we are still seeing this issue on Leo Commercial RIL (.65)
agree with comment 2, it also works for me when I flash to .60 build
- "SIM card not ready" is a current message under Cellular & Data in Settings
- device is not able to make call or sending/receiving SMS
(after flashing it shows "Unknown SIM card state", then after adding RIL it changes to "SIM card not ready")
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/e2d297ddf01d
Gaia baec473de45d4971b86a470b7580cd1444585a26
Build 2013-04-15-070205
Comment 12•12 years ago
|
||
Please share a device w/ with so I can take a look
Updated•12 years ago
|
blocking-b2g: leo? → leo+
Whiteboard: [POVB][leo]
![]() |
Reporter | |
Comment 13•12 years ago
|
||
Accidently, I found that also happens on my buri devices.
buri - v1.1.0
gaia: 502653c27d86acbb82e170ccf4d226999458ca84
gecko: d95b195ae1b120c7e6d5031667e5dd15432a4cf7
![]() |
Reporter | |
Comment 14•12 years ago
|
||
Remove POVB and LEO tags because it's not just on specific devices.
Whiteboard: [POVB][leo]
Updated•12 years ago
|
Assignee: mvines → nobody
Whiteboard: [POVB][leo]
Updated•12 years ago
|
Whiteboard: [POVB][leo]
Last known working ril :
leo-20130411070205-ril01.01.00.019.061
mvines, we could use your expertise in figuring out what might be the problem. I understand it works for you in the tip Gecko/RIL.
Is there anything you can help lead us to in order to look for what the problem might be so we can get this fixed asap please?
Flags: needinfo?(mvines)
Comment 16•12 years ago
|
||
Let's start from the beginning. The latest vendor build is based on v1.1 AU 48, could you please load that build unmodified (the vendor flashing tool is required) and check if the bug still manifests?
My Leo build is literally just the vendor binary build with gecko/Gaia/ril replaced with ones I built that are closer to the tip of v1.1.
The Moz Leo builds attempt to build much more stuff from source, but I am worried that there's a mismatch between the vendor source and the source that Moz is using to rebuild binaries.
Flags: needinfo?(mvines)
I will try to do so. I'll need to get the vendor software and build and investigate further.
Looking at the builds for another vendor and another issue, I think there are some differences that might need to get addressed. Thanks for the input.
I rebuilt my own Gaia on top of the leo; I had to do an adb root in order to get the gaia version on and it shows the SIM stable, though no carrier.
I do believe it's a build/permission issue now more so. Going to play around with adb root before flashing.
Comment 19•12 years ago
|
||
Adding Vincent per tchung - this is still affecting our ability to test the Leo device on both the Commercial RIL and the Mozilla RIL as well.
Flags: needinfo?(vchang)
Comment 20•12 years ago
|
||
FWIW. AT&T is working fine for me on Leo device still
I did some further testing:
After flashing with Leo flashing tool: everything worked, firmware was updated
After that I flashed the commercial ril, mobile data, dialer was busted. wifi worked
I removed the bundle to get the mozril, mobile data, dialer was busted. I did get the can't make a call dialog. wifi worked.
After that I reflashed using a special boot image w/ the commercial ril, mobile data, dialer was busted. wifi worked.
I removed the bundle to get the mozril, mobile data dialer was busted.
I'm trying to build leo currently on my machine but am running into an error message which I'm unsure how to resolve:
make: *** No rule to make target `out/target/common/obj/PACKAGING/public_api.txt', needed by `out/target/common/obj/PACKAGING/checkapi-last-timestamp'. Stop.
Comment 23•12 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #22)
> I did some further testing:
> After flashing with Leo flashing tool: everything worked, firmware was
> updated
>
> After that I flashed the commercial ril, mobile data, dialer was busted.
> wifi worked
> I removed the bundle to get the mozril, mobile data, dialer was busted. I
> did get the can't make a call dialog. wifi worked.
>
> After that I reflashed using a special boot image w/ the commercial ril,
> mobile data, dialer was busted. wifi worked.
> I removed the bundle to get the mozril, mobile data dialer was busted.
>
> I'm trying to build leo currently on my machine but am running into an error
> message which I'm unsure how to resolve:
> make: *** No rule to make target
> `out/target/common/obj/PACKAGING/public_api.txt', needed by
> `out/target/common/obj/PACKAGING/checkapi-last-timestamp'. Stop.
The latest partner build from Leo, dated 4/25/2013, i flashed seems to have working dialer, sms, sim data, and wifi.
Environment:
Gecko
Gaia f9d8af05fdd3e1ee4b4d9b715849690333a2dd1c
BuildID 20130425170448
Version 18.0
I have no idea what AU version or gecko version, but the filename from Leo is D300(leo) TLF ES V07e.
So we need to keep investigating those differences between moz builds and the leo one.
Comment 24•12 years ago
|
||
Version info for this partner build is:
- AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.071
- Mozilla build ID: 20130421070203
- Gecko : 950b402b6188bb2f3ce3176e620ed5249719d720
- Gaia : 5cbb19e4bb78a7ad879fbe4b9a841e1c35714f5c
Comment 25•12 years ago
|
||
On Mozilla RIL, I could see the RIL message below when "Unknown SIM card state" was shown in Settings.
I/Gecko ( 143): RIL Worker: Handling parcel as REQUEST_GET_SIM_STATUS
I/Gecko ( 143): RIL Worker: iccStatus: {"cardState":2,"universalPINState":0,"gsmUmtsSubscriptionAppIndex":-1,"cdmaSubscriptionAppIndex":-
Please also see the specification of cardState.
typedef enum {
/* A file on SIM has been updated. data[1] contains the EFID. */
SIM_FILE_UPDATE = 0,
/* SIM initialized. All files should be re-read. data[1] contains AID that caused REFRESH */
SIM_INIT = 1,
/* SIM reset. SIM power required, SIM may be locked and all files should be re-read. */
SIM_RESET = 2
} RIL_SimRefreshResult;
This error report came from modem and we need help from partner side.
Flags: needinfo?(vliu)
(In reply to Vincent Liu[:vliu] from comment #25)
> On Mozilla RIL, I could see the RIL message below when "Unknown SIM card
> state" was shown in Settings.
>
> I/Gecko ( 143): RIL Worker: Handling parcel as REQUEST_GET_SIM_STATUS
> I/Gecko ( 143): RIL Worker: iccStatus:
> {"cardState":2,"universalPINState":0,"gsmUmtsSubscriptionAppIndex":-1,
> "cdmaSubscriptionAppIndex":-
>
> Please also see the specification of cardState.
>
> typedef enum {
> /* A file on SIM has been updated. data[1] contains the EFID. */
> SIM_FILE_UPDATE = 0,
> /* SIM initialized. All files should be re-read. data[1] contains AID
> that caused REFRESH */
> SIM_INIT = 1,
> /* SIM reset. SIM power required, SIM may be locked and all files
> should be re-read. */
> SIM_RESET = 2
> } RIL_SimRefreshResult;
>
I think vliu copied/pasted wrong enum in last comment, should be
typedef enum {
RIL_CARDSTATE_ABSENT = 0,
RIL_CARDSTATE_PRESENT = 1,
RIL_CARDSTATE_ERROR = 2
} RIL_CardState;
Also remove ni? for vchang.
Flags: needinfo?(vchang)
Comment 27•12 years ago
|
||
This is also happening on French SIM cards from different carriers (all of them).
Comment 28•12 years ago
|
||
Leo Gecko team, can you please help us with this bug? We are all blocked on using cellular and data sim cards here. Thanks!
Flags: needinfo?(leo.bugzilla.gecko)
Comment 29•12 years ago
|
||
Does data/cellular on the stock vendor builds work for your devices? Latest (at the time of this comment) is based on AU 71.
Comment 30•12 years ago
|
||
Michael, the last known good vendor build i got from leo, does work; yes. I can make phone calls, surf the internet on data... But my comment 23 doesnt tell me which AU they are using.
FWIW, i tried on our builds today, using AU 75, and still no cellular and data worky.
Gaia detects the SIM network name "T-mobile", but nothing else in the SIM card state is detected that can be used to do radio.
I'll attach a logcat capture, but i dont know if anything here is helpful. Also show a screenshot of the status.
Comment 31•12 years ago
|
||
no sim card found
Comment 32•12 years ago
|
||
marking regression, because i believe this worked on previous binaries and our builds dating back to Apr 11th.
also, this is only for Leo. we dont see this issue with other devices.
Keywords: regression
Whiteboard: leo
Comment 33•12 years ago
|
||
(In reply to Tony Chung [:tchung] from comment #30)
> Michael, the last known good vendor build i got from leo, does work; yes. I
> can make phone calls, surf the internet on data... But my comment 23 doesnt
> tell me which AU they are using.
Cool. That build was based on AU 71. How different are the Mozilla builds from the stock Leo builds? Beyond Gecko/Gaia (/system/b2g/*), what else is being removed/replaced? Ideally nothing.
Comment 34•12 years ago
|
||
User unable to dial outbound calls, but may receive incoming calls.
Leo v1.1.0 Mozilla and Commercial RILs:
Build ID: 20130501070205
Gecko: 765d296cff66
Gaia: e420d71c9528786621f176fb4ce67d291e0a530e
Comment 35•12 years ago
|
||
(In reply to Michael Vines [:m1] [:evilmachines] from comment #33)
> (In reply to Tony Chung [:tchung] from comment #30)
>
> > Michael, the last known good vendor build i got from leo, does work; yes. I
> > can make phone calls, surf the internet on data... But my comment 23 doesnt
> > tell me which AU they are using.
>
> Cool. That build was based on AU 71. How different are the Mozilla builds
> from the stock Leo builds? Beyond Gecko/Gaia (/system/b2g/*), what else is
> being removed/replaced? Ideally nothing.
ideally nothing, but realistically a lot. im currently testing a different gaia / gecko commit set than what Leo has in their build. I also have no idea what their binaries are, since they send they control when they send those to mozilla or not. I can only provide you the builds that mozilla builds (gecko/gaia/gonk), and tell you what we see when we flash on top of the vendor binaries.
I hope leo can provide the information on what's changed, and why mozilla builds see this non-working radio.
Comment 36•12 years ago
|
||
Why is Moz changing stuff outside of /system/b2g/ at all? That is likely the root cause of this bug. We don't do that here and voice/data is working fine it seems.
Every time new blobs come, update of course. But then only replace /system/b2g/* with the tip v1.0.1 gecko/gaia/ril.
Comment 37•12 years ago
|
||
(In reply to Michael Vines [:m1] [:evilmachines] from comment #36)
> Why is Moz changing stuff outside of /system/b2g/ at all? That is likely
> the root cause of this bug. We don't do that here and voice/data is working
> fine it seems.
I can't confirm if that's happening, so dont quote me. But i'll cc someone that might now. fabrice, ya know if thats true?
>
> Every time new blobs come, update of course. But then only replace
> /system/b2g/* with the tip v1.0.1 gecko/gaia/ril.
Flags: needinfo?(fabrice)
Comment 38•12 years ago
|
||
(In reply to Tony Chung [:tchung] from comment #37)
> (In reply to Michael Vines [:m1] [:evilmachines] from comment #36)
> > Why is Moz changing stuff outside of /system/b2g/ at all? That is likely
> > the root cause of this bug. We don't do that here and voice/data is working
> > fine it seems.
>
> I can't confirm if that's happening, so dont quote me. But i'll cc someone
> that might now. fabrice, ya know if thats true?
>
I don't think we change anything. I have a leo device flashed with the 20130425170448 build and it's working fine (I use an AT&T sim).
Flags: needinfo?(fabrice)
Comment 39•12 years ago
|
||
So i just tried flashing gecko on top of the base image from Leo. This test rules out our nightly builds replace vendor Gonk.
gecko only binaries are at: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-b2g18-leo/latest/b2g-18.0.en-US.android-arm.tar.gz
Results before the flash:
- Leo base image detects my ATT SIm card just fine, and i can make phone calls
Results after flashing gecko:
- Unknown SIM card state (see comment 31 screenshot). can't make any phone calls or SMS due to this.
Any help?
Comment 40•12 years ago
|
||
Hi Tony. have you removed Commercial RIL in your device after you flashed gecko?
I tested on my leo device which I updated it using AUS( http://update.boot2gecko.org/nightly/b2g_update_20130502230205.mar?build_id=20130502230205&version=18.0 )
Before AUS Update : Call & Data works fine
After AUS Update : Call & Data busted
After AUS Update + remove Commercial RIL : Call & Data works fine
I changed the file name to chrome.manifest_ from chrome.manifest in /system/b2g/distribution/bundles/libqc_b2g_ril/ to avoid loading the Commercial RIL extension component.
After this, everything just works fine.
I'm not sure it works on your device too.
BTW, I couldn't get the binaries you shared on comment #39 because i don't have the right to access the server.
Comment 41•12 years ago
|
||
I can reproduce the problem following the below steps.
1. Flashed leo image.
Note: After flashing the image and reboot, the status in Cellular & Data was normal.
2. Flash gecko binaries in Comment 39.
Note : After flashing the binaries and reboot, the status in Cellular & Data showed "Unknown SIM card state"
But if I took a detailed look, I found I couldn't see rilproxy risen by checking the ps command. It means we still not using Mozilla RIL even updating the gecko binaries.
Discussed with :atsai, I believe the device run qcril even flashing gecko binaries. Please see the attached logcat file and you can see lots of qcril in log file.
Comment 42•12 years ago
|
||
From the attached logcat file in Comment 41, I found an error log about SimIO
E/ICCFILEHANDLER_QC_B2G( 150): HandleSimIO received error 2 for EF 0x6f13
I think the |error 2| could be the reason why we got "Unknow SIM card state". It should take look into qc_ril.
Comment 43•12 years ago
|
||
(In reply to JinhoHwang from comment #40)
> Hi Tony. have you removed Commercial RIL in your device after you flashed
> gecko?
> I tested on my leo device which I updated it using AUS(
> http://update.boot2gecko.org/nightly/b2g_update_20130502230205.
> mar?build_id=20130502230205&version=18.0 )
>
> Before AUS Update : Call & Data works fine
> After AUS Update : Call & Data busted
>
> After AUS Update + remove Commercial RIL : Call & Data works fine
>
> I changed the file name to chrome.manifest_ from chrome.manifest in
> /system/b2g/distribution/bundles/libqc_b2g_ril/ to avoid loading the
> Commercial RIL extension component.
>
> After this, everything just works fine.
> I'm not sure it works on your device too.
>
> BTW, I couldn't get the binaries you shared on comment #39 because i don't
> have the right to access the server.
Hi JinHoHwang, no luck, i tried your steps of disabling the commercial RIL, and restarting, but still see the Unknown SIm state. Let me find out if i can share the gecko build with you. Can you let me know where i can email it to?
I see vincent has reproduced this in comment 41 as well with our gecko binaries. So surely, there is something incompatible with my v1.1 gecko bits and the Device binaries.
Comment 44•12 years ago
|
||
Jin Ho, i've emailed you the gecko build via email.
I found the same results as tchung, except:
I use both T-mobile and AT&T for testing and I found that AT&T is detected in only in the lockscreen as T-Mobile is not detected anywhere.
( I have also flashed to the latest v1-train from my own gaia repo: commit d5f7b2d3f7acc04c35abda8b001262d8912f9dfe Date: Fri May 3 16:10:34 2013 -0700 )
I think AT&T uses 2G, T-mobile uses 3G?
Comment 46•12 years ago
|
||
Tony, Thanks for sharing the binary with me.
I've flashed gecko with your binary.
Here is the result.
Leo Vendor build version : 4/25/2013 (the version you mentioned on comment 23)
Before Tony Binary : Call & Data works fine
After Tony Binary applied : Call & Data busted (Unknown Sim State)
After Tony Binary + Removed commercial RIL : Call & Data just works fine.
I don't understand why we have different testing result on it.
I will check some other Sim cards too.
Comment 48•12 years ago
|
||
(In reply to JinhoHwang from comment #46)
> Tony, Thanks for sharing the binary with me.
>
> I've flashed gecko with your binary.
> Here is the result.
>
> Leo Vendor build version : 4/25/2013 (the version you mentioned on comment
> 23)
>
> Before Tony Binary : Call & Data works fine
> After Tony Binary applied : Call & Data busted (Unknown Sim State)
>
> After Tony Binary + Removed commercial RIL : Call & Data just works fine.
>
> I don't understand why we have different testing result on it.
> I will check some other Sim cards too.
Thanks for testing and the feedback. I'll give this test again without the commercial RIL and report back here.
Updated•12 years ago
|
QA Contact: atsai → tchung
Comment 49•12 years ago
|
||
leo b2g-18
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/499c3627e89a
Gaia 495c46489eb256be598a19ea54d7837ce4fc385b
BuildID 20130502070205
Version 18.0
Detects SIM on Lockscreen
AT&T Yes
T-Mobile no all
Automatic Data Configuration under Settings => Cellular & Data => Data Settings
AT&T Yes
T-Mobile no
Incoming calls
AT&T yes
T-Mobile yes
Outgoing Calls
AT&T no
T-Mobile no
leo b2g-18 : base build + base ril + gecko + gaia
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/00c554abfc17
Gaia 9377636cee5ac55b9f1d68f598afc7aadfbb2b00
BuildID 2013-05-06-07-02-04
Version 18.0
Detects SIM on Lockscreen
AT&T Yes
T-Mobile yes
Detects SIM on notification
AT&T yes
T-Mobile yes
Automatic Data Configuration under Settings => Cellular & Data => Data
Settings
AT&T Yes
T-Mobile no
Incoming calls
AT&T yes
T-Mobile yes
Outgoing Calls
AT&T no
T-Mobile no
leo b2g-18 : base build + mozril + gecko + gaia
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/00c554abfc17
Gaia 9377636cee5ac55b9f1d68f598afc7aadfbb2b00
BuildID 2013-05-06-07-02-04
Version 18.0
Detects SIM on Lockscreen
AT&T Yes
T-Mobile yes
Detects SIM on notification
AT&T yes
T-Mobile yes
Automatic Data Configuration under Settings => Cellular & Data => Data
Settings
AT&T Yes
T-Mobile yes
Incoming calls
AT&T yes
T-Mobile yes
Outgoing Calls
AT&T yes
T-Mobile yes
SMS incoming:
AT&T yes
T-mobile yes
SMS outgoing:
AT&T yes
T-mobile yes
leo b2g-18 : base build + commercial ril + gecko + gaia
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/00c554abfc17
Gaia 9377636cee5ac55b9f1d68f598afc7aadfbb2b00
BuildID 2013-05-06-07-02-04
Version 18.0
Detects SIM on Lockscreen
AT&T Yes
T-Mobile yes
Detects SIM on notification
AT&T yes
T-Mobile yes
Automatic Data Configuration under Settings => Cellular & Data => Data
Settings
AT&T Yes
T-Mobile yes
Incoming calls
AT&T yes
T-Mobile yes
Outgoing Calls
AT&T yes
T-Mobile yes
SMS crashes when sending or receiving on commercial ril:
https://crash-stats.mozilla.com/report/index/cc31623b-3ffb-4bd1-aec0-e53482130506
https://crash-stats.mozilla.com/report/index/3d02b236-12ca-42f5-a6aa-970c32130506
Comment 51•12 years ago
|
||
thanks naoki for the test.
i had a flaky Leo phone, so i found another one and did the same test.
* Gaia + Gecko flashed over base Leo image + Mozilla RIL -- sms and dialer works
* Gaia + Gecko flashed over base leo image + *Commercial RIL* -- SMS, dialer broken, "Unknown SiM state"
Mvines, over into your court. how do we investigate further here? what info do you need from us?
Flags: needinfo?(mvines)
Comment 52•12 years ago
|
||
Tag, I'm it :)
Could you please share with me all the bits that you used for the broken dialer case? Also the version info for each. The raw dump files from the crashes in comment 50 as well.
Flags: needinfo?(mvines)
Comment 53•12 years ago
|
||
(In reply to Michael Vines [:m1] [:evilmachines] from comment #52)
> Tag, I'm it :)
>
> Could you please share with me all the bits that you used for the broken
> dialer case? Also the version info for each. The raw dump files from the
> crashes in comment 50 as well.
Sure. here's the gecko and gaia binaries from build 2013-05-07 that i used to test in comment 51.
https://www.dropbox.com/home/Public/20130507_leo_gecko_gaia
Naoki, can you provide the raw dump files for your reported crashes?
Hi Michael,
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=869196 to track the crasher.
Side note : mwu had taught me how to build with the latest RIL as well. I will be building that way from now on.
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/00c554abfc17
Gaia: 9377636cee5ac55b9f1d68f598afc7aadfbb2b00
RIL : 01.01.00.019.086
Oops. Sorry. the last 2 comments were for the crashing in the SMS.
The broken dialer issue is that we were using the base build's commercial ril so my guess is that the ril is outdated and it might not be worth pursuing. I am unsure how to get the id from the basebuild's ril.
Comment 57•12 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #56)
> Oops. Sorry. the last 2 comments were for the crashing in the SMS.
>
> The broken dialer issue is that we were using the base build's commercial
> ril so my guess is that the ril is outdated and it might not be worth
> pursuing. I am unsure how to get the id from the basebuild's ril.
Oh, ok. The basebuild's ril will be of the same AU vintage as the basebuild. Leo should have provided that information to you.
Mixing the basebuild's ril with the tip gecko will certainly fail due to recent RIL interface changes. But using the tip ril + tip gecko is working as expected?
Comment 58•12 years ago
|
||
(In reply to Michael Vines [:m1] [:evilmachines] from comment #57)
> Oh, ok. The basebuild's ril will be of the same AU vintage as the
> basebuild. Leo should have provided that information to you.
>
Hi, there.
Leo build info has been already proivided when vendor binaray was released.
However, you can find Leo build indentifier at Setting app ->Device info--> more info-->Firmware revision.
If the firemware revision is v07e, version info is the same as comment #24
Flags: needinfo?(leo.bugzilla.gecko)
I haven't successfully got Gecko to compile for Leo on my machine. I might have to try on a windows machine. The error I get is:
make: *** No rule to make target `out/target/common/obj/PACKAGING/public_api.txt', needed by `out/target/common/obj/PACKAGING/checkapi-last-timestamp'. Stop.
I can only use close-but-not-tip gecko as per described in an earlier comment until I get this resolved.
mvines, I'm going to try using the try server to build a leo build. Would it be possible to get the manifest of a working build from you please?
Tip is a little vague in terms of which pull to pick from as it could change from the time you commented. :)
Comment 61•12 years ago
|
||
Sure, please pick out the Gecko/Gaia SHA1s any recent AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.xyz manifest from https://www.codeaurora.org/gitweb/quic/b2g/?p=b2g/manifest.git;a=log;h=refs/heads/release and match it with the corresponding RIL.
Comment 62•12 years ago
|
||
Latest base images + gecko + ril makes this work.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•