I have been using Pixel AOSP 9.0.0_r2 for testing purposes. It's a "standard" build (no modifications) of AOSP with the correct Vendor and driver files for the 9.0.0_r2 branch for the pixel.
Using that build setup the resultant ROM is not seeing the Phone Sim. I've tried building several times. No dice. The sim works when I flash the Factory version of 9.0.0_r2 but the AOSP versions I'm building never work.
I'm operating under the assumption that this is purely a ROM/build problem but since this is an unmodified build of 9.0.0_r2, I'm not clear where I should start looking for the problem. Does anyone have any suggestions?
I have discovered that whatever this is, it's purely a 9.0 issue. When I cross checked against and old AOSP 8.1 branch I built, the sim works. Since I'm currently on branch r2 I think the first step is to update to the latest branch and try again.
Well whatever this is, it's still in branch r10. I'm stumped. I'm not doing anything different with my builds than I did with Android 8 and yet the sim is detected in 8 but is not detected in 9.
I'm having the same issue: Android 8 AOSP worked fine, but 9 cannot find the SIM.
I did a logcat of the radio buffer, and it's complaining about a missing file: /system/lib64/[email protected]
Seeing as this is a vendor file, I'm not sure why it's not provided in the vendor file downloads.
was this ever solved? I'd like to build AOSP 9 for my pixel, but if running into these issues, I'm a little worried i won't be able to fix them.
See this thread:
https://groups.google.com/forum/m/#!topic/android-building/UWZN5Ez4M6Y
ztotherad said:
was this ever solved? I'd like to build AOSP 9 for my pixel, but if running into these issues, I'm a little worried i won't be able to fix them.
Click to expand...
Click to collapse
Sent from my AOSP on msm8996 using Tapatalk
nicedream06 said:
See this thread:
https://groups.google.com/forum/m/#!topic/android-building/UWZN5Ez4M6Y
Click to expand...
Click to collapse
awesome thanks! now to just build it and hope it works awesomely!
Related
EDIT: Oops, I meant to put this in General section. Sorry!!!
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
The first one is that there is of course no Google Apps. I understand why, but is there a good source for them? Or do the ones for CM7 work?
Second, I get the regular Android boot animation, not the cool Nexus S one. Is that normal?
Third, my Android version always says something like 3.1.x.x.x.x.x or something crazy. Is that normal? I was kind of expecting it to say GRJ22 2.3.4 or something like that.
I am trying to build full_crespo-user, FYI.
I use the normal gapps whenever I compile an aosp. Try the modded one specific for the nexus s. You would find it in the last pages of the nightlies thread.
Yes. The android marine blue animation is the default one for aosp.
The version number you are getting 3.1.xxzzxxxxxxxxxz is quite normal. This is the actual version of aosp. You can change it in your build.prop if you want to.
Good luck/
Sent from my Nexus S using Tapatalk
matt2053 said:
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
Click to expand...
Click to collapse
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
no need to pull them. anyway official binaries are available for the nexus s
http://code.google.com/android/nexus/drivers.html
Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
Yes, pull from the gingerbread branch! Master is almost always full of bugs and not the best to build. You know you have master when the build number is pi (the 3.1.4... one mentioned earlier).
To use repo to pull down the gingerbread branch, use the repo init command as usual but add "-b gingerbread" at the end (no quotes).
Sent from my Nexus S
I would love to know more about this master vs gingerbread branch difference. I've been building from master it seems. What purposes do the different branches serve? Can someone shed some light on the Android development process?
Sent from my Nexus S using XDA App
So master basically contains everything, all versions. Master is basically all of android xD
Now, you can do a -b gingerbread to just clone the gingerbread branch, which will give u the 2.3 code for everything on android.
** Note -b can also be used for froyo, eclair, etc. **
I hope this helps!
Not development. Moved to Q&A.
I have another question so I am bumping this up:
I have successfully build Android 2.3.5 for my Nexus S. Is there anyone who might help me adding Google Nexus boot animation and Google Apps, and putting it all into a flashable zip?
I figured out the zip thanks to this awesome thread: http://forum.xda-developers.com/showthread.php?t=732957
Now my problem is the keyboard. The "suggested" words are only names from my contacts, I don't get any regular English language suggestions. Any ideas?
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
pplayz18 said:
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
Click to expand...
Click to collapse
Which CM10 build are you using? It's my understanding that on the current build of the official CM10 NFC is not yet supported. This could be the case on the unofficial ones as well but I'm not sure.
Relentless D said:
Which CM10 build are you using? It's my understanding that on the current build of the official CM10 NFC is not yet supported. This could be the case on the unofficial ones as well but I'm not sure.
Click to expand...
Click to collapse
A nightly unofficial one released last night. 3.0.39
The only thing that is different about getting GW working on CM10 is you don't need to flash anything (except Google Wallet if you are using the .zip provided by ogdobber) and editing the build prop. NFC is currently broken on the newer CM (and all others based off of CM code) for the time being but I would imagine it would be fixed after the main bugs are all squared away.
The last unofficial build I that had NFC working was InvisibleK's 8/13 but that was before the recent MMS or RIL fixes.
Marcismo55 said:
The only thing that is different about getting GW working on CM10 is you don't need to flash anything (except Google Wallet if you are using the .zip provided by ogdobber) and editing the build prop. NFC is currently broken on the newer CM (and all others based off of CM code) for the time being but I would imagine it would be fixed after the main bugs are all squared away.
The last unofficial build I that had NFC working was InvisibleK's 8/13 but that was before the recent MMS or RIL fixes.
Click to expand...
Click to collapse
I figured it out. I was trying to use the same verizon zip file when I needed to use one specifically for aosp roms.
pplayz18 said:
I figured it out. I was trying to use the same verizon zip file when I needed to use one specifically for aosp roms.
Click to expand...
Click to collapse
Do you have a link to get it working?
pplayz18 said:
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
Click to expand...
Click to collapse
if you took the time to read the notes on the release, you would see that it is not supported yet.
Since you did not, now you will likely have a ton of people telling you to read next time.
NFC DOESNT WORK. THEREFORE NOTHING THAT RELIES ON IT WORKS.
Its a piece of hardware, that does not FUNCTION yet.
did you also figure out that NFC doesn't work on any CM10 build yet so it doesn't matter what you flash?
Not to thread jack... but...
It's been quite a few days without any action on this thread and NFC is one thing I'd really like to try out. With that said I love CM10, currently running the 8-27 nightly without any other issues and love it... NFC isn't that important that I'd go back to a TW/Stock Rom for it.
Any word from the CM guys on when/if the rils and NFC functionality will be fixed up? Patiently waiting and love everyone working on CM10 D2VZW! :good:
Flashed the 8-31 nightly and NFC just greys out after ticking the box still. Wake me up when September comes
Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies
I was reading in the official CM10 thread that someone had developed a fix and that it would soon be implemented into the Nightlies
Edit:
http://forum.xda-developers.com/showpost.php?p=30952627&postcount=1317
This a work in progress. Any help will be appreciated.
The problem:
When I try to Start Camera, I get an error "Can't connect to the camera."
I get the same error from HD Camera Ultra and Focal
Unsuccessful fixes tried and notes of caution:
After installing CMFix for Camera from play store, the app does not seem to do anything at all.
Flashing,
Using TWRP to flash camfix.zip causes phone not to boot up. Had to reflash ROM.
This post is a work in progress, and will be updated as I keep trying until it is an explanation.
The ROM installed these two files in \system\lib\hw
camera.msm8960.so
camera.vendor.msm8960.so
I tried renaming these to:
old.camera.msm8960.so
camera.msm8960.so
I then tried renaming them to:
vendor-camera.msm8960.so
camera.vendor.msm8960.so
none of these worked.
Since the specs of the RAZR M and and the XT897 are very similar, I plan to try these Motorola camera apk's. The RAZR M's front facing camera is lower resolutin; so, I would imagine mine might not work.
If you are running a xt897 build on a RAZR M, that might explain the camera issues...
Are you using the old unified builds? Is there any reason you're not on CM13? PAC hasn't gotten any new builds, unified or otherwise, for a long time (for this device).
arrrghhh said:
If you are running a xt897 build on a RAZR M, that might explain the camera issues... Are you using the old unified builds? ...
Click to expand...
Click to collapse
My phone is an XT897, not a RAZR M. My Photon had already been updated to Jelly Bean by Sprint when I bought it. I am currently running: [ROM][OFFICIAL][KitKat 4.4.4][moto_msm8960_jbbl] PAC-ROM 4.4.4.RC-2. This is a unified build for phones with msm8960 cpu and is based on CM11.
arrrghhh said:
... Is there any reason you're not on CM13? PAC hasn't gotten any new builds, unified or otherwise, for a long time (for this device).
Click to expand...
Click to collapse
I have a CDMA XT897 -- no SIM Card. CM10 is the last release for my device. There are some CM11 Nightly builds available.
Since the XT897 only has 1GB of RAM, I thought KitKat would be a good place to be. This PAC-ROM was the only KitKat 4.4.4 ROM I could find for my phone that still has a live download link.
Everything is infinitely more responsive on all things. The most noticeable is the keyboard. On JB stock ROM, I have to hold keys about 1/4 of a second before the letters show up on the screen ... and just to make it more annoying , if I don't release it precisely when it is registered, I end up with multiple characters, grr. With this PAC-ROM, they are instantly registered.
Also, I can't begin to tell you how many "features" of Android I disable regardless of version:
My wallpaper is a plain black png.
The annoying google search box on my desktop -- GONE!
Screen rotation -- disabled.
The cutsie battery and wireless icons are now numbers.
All animations are disabled.
The list goes on... LOL
That being said, I do wish I had a way to patch my ROM for known security holes in KitKat 4.4.4 now and in the future without having to replace the OS and re-tweak it back with all the changes I want. I use Firefox 40.0.3 for much the same reason .
RandyB201 said:
My phone is an XT897, not a RAZR M. My Photon had already been updated to Jelly Bean by Sprint when I bought it. I am currently running: [ROM][OFFICIAL][KitKat 4.4.4][moto_msm8960_jbbl] PAC-ROM 4.4.4.RC-2. This is a unified build for phones with msm8960 cpu and is based on CM11.
I have a CDMA XT897 -- no SIM Card. CM10 is the last release for my device. There are some CM11 Nightly builds available.
Since the XT897 only has 1GB of RAM, I thought KitKat would be a good place to be. This PAC-ROM was the only KitKat 4.4.4 ROM I could find for my phone that still has a live download link.
Everything is infinitely more responsive on all things. The most noticeable is the keyboard. On JB stock ROM, I have to hold keys about 1/4 of a second before the letters show up on the screen ... and just to make it more annoying , if I don't release it precisely when it is registered, I end up with multiple characters, grr. With this PAC-ROM, they are instantly registered.
Also, I can't begin to tell you how many "features" of Android I disable regardless of version:
My wallpaper is a plain black png.
The annoying google search box on my desktop -- GONE!
Screen rotation -- disabled.
The cutsie battery and wireless icons are now numbers.
All animations are disabled.
The list goes on... LOL
That being said, I do wish I had a way to patch my ROM for known security holes in KitKat 4.4.4 now and in the future without having to replace the OS and re-tweak it back with all the changes I want. I use Firefox 40.0.3 for much the same reason .
Click to expand...
Click to collapse
You're mistaken. The division to separate xt897 cdma (xt897c) and sim modified xt897 gsm (xt897) builds at the time of cm10 was artificial, caused by broken world phone support in cm10 at the time.
The separate cdma and gsm builds were later unified again under a single xt897 cm11 build meant for both cdma and gsm networks as soon as the world phone support was fixed.
xt897 cm-11.0, cm-12.0, cm-12.1 and cm-13.0 builds are supposed to work on cdma networks just fine.
That being said, it's still true that I'm able to test only the gsm stuff myself and the dealing with possible cdma issues solely depends on detailed reports and logs from cdma users.
cm-11 builds for xt897 are here: https://download.cyanogenmod.org/?device=moto_msm8960_jbbl
cm-12.1 and newer builds for xt897 are here: https://download.cyanogenmod.org/?device=xt897
kabaldan said:
You're mistaken. The division to separate xt897 cdma (xt897c) and sim modified xt897 gsm (xt897) builds at the time of cm10 was artificial, caused by broken world phone support in cm10 at the time. The separate cdma and gsm builds were later unified again under a single xt897 cm11 build meant for both cdma and gsm ...
Click to expand...
Click to collapse
In this case, I am happy to be mistaken! :cyclops: Unless someone knows something I do not, the XT897 is the only qwerty phone that works on Sprint's 4G LTE CDMA network.
I have 2 functional XT897's here. Both are rooted. One has stock JB. The other is currently running PAC-ROM. I use TWRP for recovery and backup, etc.
kabaldan said:
cm-11 builds for xt897 are here: https://download.cyanogenmod.org/?device=moto_msm8960_jbbl
cm-12.1 and newer builds for xt897 are here: https://download.cyanogenmod.org/?device=xt897
Click to expand...
Click to collapse
Since you provided both links, you have me wondering, do I need to install 11 before installing 12.1 or later?
RandyB201 said:
Since you provided both links, you have me wondering, do I need to install 11 before installing 12.1 or later?
Click to expand...
Click to collapse
You can go straight to CM13 if you desire. Just need to be unlocked with a custom recovery (IE TWRP).
arrrghhh said:
You can go straight to CM13 if you desire. Just need to be unlocked with a custom recovery (IE TWRP).
Click to expand...
Click to collapse
Thank you. I flashed cm-12.1-20151007-SNAPSHOT-YOG4PAO339-xt897.zip
Unless, I am mistaken "Snapshot" suggests a more stable / proven / debugged version, is that not correct? That is the highest version with Snapshot on the page you sent me to.
I have been playing around with it this morning. I have 2 xt897's here. Right now, one is running stock JB rooted and majorly tweaked, lol. It is the one I have active with my phone service. So, I can't test SMS or phone calls on the new ROM yet.
Wifi is working. Bluetooth turns on and works with my speaker. Both of the Cameras work, and the software lets me save pics to my exfat formatted sd card with no extra app -- NICE!
I found one problem, but I am not sure how to deal with it. The space key on the hardware keyboard is not working. Can you help me debug that? Or tell me where I should post / ask the question, even?
Thank you again!
RandyB201 said:
I found one problem, but I am not sure how to deal with it. The space key on the hardware keyboard is not working. Can you help me debug that? Or tell me where I should post / ask the question, even?
Click to expand...
Click to collapse
Post in the thread relevant to that ROM, or make a Q&A thread about that topic... but that sounds like a hardware issue.
arrrghhh said:
Post in the thread relevant to that ROM, or make a Q&A thread about that topic... but that sounds like a hardware issue.
Click to expand...
Click to collapse
sadly, you were correct. That key is now dead in all ROMs. :crying:
Just wondering what people's thoughts are on the Dev preview, IE current stability and features
Sent from my Pixel 3a using Tapatalk
upinsmoke7610 said:
Just wondering what people's thoughts are on the Dev preview, IE current stability and features
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I ran it up until this last weekend. Sometimes using the phone dialer it would randomly reboot. Also the files app had a glitch where I could not delete files and folders on /sdcard. I reported both. Other than that I had no other issues. Not many user facing changes right now so not really worth it in my opinion.
DP1: Surprisingly Stable
ptn107 said:
I ran it up until this last weekend. Sometimes using the phone dialer it would randomly reboot. Also the files app had a glitch where I could not delete files and folders on /sdcard. I reported both. Other than that I had no other issues. Not many user facing changes right now so not really worth it in my opinion.
Click to expand...
Click to collapse
I found DP1 surprisingly stable on my Pixel 3a; in fact, nothing failed to work. The only reason I'm not running it now is because I am running Lineage 17.1 now (same phone) while waiting for DP2; in fact, I had more issues installing Lineage than installing DP1 OR any version of Android 10.
I'm actually thinking that Android going forward is more about stability than anything else - especially given the pushback merely concerning changes from 8->9 and 9->10. Fewer and fewer folks want a host of change in their mobile OS; what they want instead is stability.
PGHammer said:
I found DP1 surprisingly stable on my Pixel 3a; in fact, nothing failed to work. The only reason I'm not running it now is because I am running Lineage 17.1 now (same phone) while waiting for DP2; in fact, I had more issues installing Lineage than installing DP1 OR any version of Android 10.
I'm actually thinking that Android going forward is more about stability than anything else - especially given the pushback merely concerning changes from 8->9 and 9->10. Fewer and fewer folks want a host of change in their mobile OS; what they want instead is stability.
Click to expand...
Click to collapse
hey can ya share the lineage rom you on?
BuT_TeR said:
hey can ya share the lineage rom you on?
Click to expand...
Click to collapse
It's elsewhere in the Pixel 3a thread: invisiblek's Pixel 3a weeklies.
Boot the included recovery, then adb sideload the ROM itself.
I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
rodri_rebag5 said:
I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Click to expand...
Click to collapse
maybe you flashing over incompatible firmware
mattie_49 said:
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
Click to expand...
Click to collapse
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Eric_Lev said:
In progress ... Be patient !
https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8350/+/349350
Workaround : https://forum.xda-developers.com/t/rom-official-lemonade-13-lineageos-20.4536697/post-88176351
Edit about workaround : 4 days of uptime without the binder issue.
Click to expand...
Click to collapse
Try the workaround until the fix is included.
downhere said:
Try the workaround until the fix is included.
Click to expand...
Click to collapse
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
rodri_rebag5 said:
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
Click to expand...
Click to collapse
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
downhere said:
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
Click to expand...
Click to collapse
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
rodri_rebag5 said:
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Click to expand...
Click to collapse
It's binder issues
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
After you've installed build.
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
You can use Developer Options of the custom ROM.
Thanks for all the answers, I will flash a ROM probably later tonight and try the cached_apps_freezer fix.