[WIP][KERNEL][KEXEC] JB ROMS For Droid 3 [03/06: BT/SPEAKERPHONE FIX]

Search This thread
By:
Advanced…
S

SeiferTV

Senior Member
Oct 6, 2010
189
73
rojocapo said:
Movistar Argentina is working ok on AOKP with the attached build.prop which was posted by mikeymike75 some pages ago.

I changed the default network type to 4 then rebooted.

Then go to Wireless and network setttings, and:

Enable alt OEM telephony code OFF
Enable alternate getIMSI code OFF
Enable World Phone settings. OFF
Set Enable GSM Signal Strength ON.

Reboot and set correct APN for working HSDPA :)
Click to expand...
Click to collapse

I use Claro Argentina, but, I'll sure as hell give it a shot.
Thanks a bunch.
 
J

javitogomezzzz

Senior Member
Jan 22, 2012
77
11
rojocapo said:
If it works, click on thanks to mikeymike75.

Oh, by the way, my phone is XT862, not 860.

Sure would love a working proximity sensor. I keep on accidentally hanging up calls.
Click to expand...
Click to collapse
tried this on a XT860 with Claro Argentina. Didn't work... probabbly worked for you because you got an XT862 no matter your carrier
If somebody with a XT860 managed to make data work it would be good to share how with us
 
R

rojocapo

Senior Member
Dec 11, 2011
223
56
Buenos Aires
javitogomezzzz said:
tried this on a XT860 with Claro Argentina. Didn't work... probabbly worked for you because you got an XT862 no matter your carrier
If somebody with a XT860 managed to make data work it would be good to share how with us
Click to expand...
Click to collapse

The difference is usually a change in build.prop. Maybe you could pastebin or attach your stock GB Build prop so we can compare it to a stock XT862 version.
 
Skreelink

Skreelink

Senior Member
Nov 28, 2010
299
182
For those with trouble entering recovery with SS 3.05

The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;

Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.

Phone will reboot showing the M logo, then proceed into SS Recovery. ;)
 
  • Like
Reactions: thorrules
S

SeiferTV

Senior Member
Oct 6, 2010
189
73
javitogomezzzz said:
already did that, but for some reason radio keeps turning on and off and SIM card is not recognized by the system
maybe the problem isn't just in the build.prop
Click to expand...
Click to collapse

Either you or rojo capo have this thing working on Argentina? ( Claro would be great, but, anything helps )
If so, mind sharing your build.prop setup?
I've tried a couple I've seen on the thread to no avail.
Thanks!
 
R

rojocapo

Senior Member
Dec 11, 2011
223
56
Buenos Aires
javitogomezzzz said:
i just did this, now i can make calls and send sms but can't receive them. Can't get 3g/edge (internet) working either, when i set and select the apn nothing happens...
Click to expand...
Click to collapse

Are you able to store the APN configuration?

Sent from my GT-I9300 using xda app-developers app

---------- Post added at 07:35 AM ---------- Previous post was at 06:41 AM ----------
SeiferTV said:
Either you or rojo capo have this thing working on Argentina? ( Claro would be great, but, anything helps )
If so, mind sharing your build.prop setup?
I've tried a couple I've seen on the thread to no avail.
Thanks!
Click to expand...
Click to collapse

As I wrote previously, my XT862 works fine on Movistar Argentina.
 
J

javitogomezzzz

Senior Member
Jan 22, 2012
77
11
rojocapo said:
Are you able to store the APN configuration?

Sent from my GT-I9300 using xda app-developers app

---------- Post added at 07:35 AM ---------- Previous post was at 06:41 AM ----------



As I wrote previously, my XT862 works fine on Movistar Argentina.
Click to expand...
Click to collapse

Yes, i can store the apn. As i said before, i can't receive calls or sms either, so there has to be something wrong

Enviado desde mi XT860 usando Tapatalk 2
 
slogar25

slogar25

Senior Member
May 19, 2012
411
163
Google Pixel 6 Pro
Google Pixel 6
I am still having the same issue. Radio turns on and off for me. I am on verizon and this issue is true for all the Kexec JB builds. Currently running CM9 non Kexec 8/20 build and this works perfect

Sent from my XT862
 
S

SeiferTV

Senior Member
Oct 6, 2010
189
73
rojocapo said:
Oh, sorry. I understood that you could not receive SMS, but incoming and outgoing voice calls were working.
Click to expand...
Click to collapse

Ok, so, I got SMS in and out., and voice calls working.
Just pulled the system/lib/libmoto_ril.so file from my AOKP ICS non-kexec rom, and changed ro.telephony.default_network to 3.
Now, mobile data is not working, altho' I CAN see my APN's properly configured and all.

rojocapo did you make any other changes to the build.prop file?

I'm so close now
 
Last edited:
J

javitogomezzzz

Senior Member
Jan 22, 2012
77
11
SeiferTV said:
Ok, so, I got SMS in and out., and voice calls working.
Just pulled the system/lib/libmoto_ril.so file from my AOKP ICS non-kexec rom, and changed ro.telephony.default_network to 3.
Now, mobile data is not working, altho' I CAN see my APN's properly configured and all.

rojocapo did you make any other changes to the build.pro file?

I'm so close now
Click to expand...
Click to collapse
can you upload that libmoto_ril.so?
apparently the one i got from GB stock has some kind of issue with JB
 
You must log in or register to reply here.

Similar threads

Hashcode
[SELFKANG ICS AOSP ROM] CM9/ICS for Droid 3 -- [BETA 2012-03-11]
Replies
2K
Views
378K
Endoroid
Endoroid
F
  • Sticky
[GUIDE]TBH inspired Free wireless tethering hack instructions for Droid 3
Replies
246
Views
171K
yanger
yanger
Deodexed
  • Locked
Can this Root Droid 3?
Replies
808
Views
140K
NeoS
NeoS
bippi79
[ROM][JB] [4.2.2] Avatar ROM for Motorola Droid 3 (solana) - Updated [Nov 30,2013]
Replies
153
Views
92K
psouza4
psouza4
chevycam94
[ROM] Steel Droid: 5.0 Gingerbread - 5.7.894 - DEODEXED - 1-11-2013
Replies
423
Views
140K
T
tim-ranger

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 115
    Hashcode
    Hashcode
    Jellybean 4.2.2 for the Droid 3

    [ CURRENTLY THIS ROM REQUIRES A ROM-SLOT1 INSTALL IN SAFESTRAP ]

    [ ALL Jellybean 4.2.x ROMs should be using 20130301 GApps: http://goo.im/gapps ]

    OFFICIAL CyanogenMod 10.1 (Android 4.2.2): [NIGHTLIES]
    http://www.get.cm/?device=solana&type=nightly
    [03/06] - BT/Speakerphone Fix in next nightly(thanks DHacker)
    [02/26] - HWcomposer API 1.0 (JB-MR1 compliant)
    [02/26] - HD codec fixes
    [02/26] - Kernel updates / bugfixes for clock management, battery drain and stability
    [02/26] - Android 4.2.2 merged into CM10.1
    [01/23] - MMS fix (sending from native Messaging app)
    [01/20] - Keyboard Backlight fixes (tied to the front button backlight for now)
    [01/18] - Fixed incoming call bug
    [01/16] - Fixed bluetooth for device starting. Audio is still bad.

    OLDER CyanogenMod 10.1:
    http://goo.im/devs/Hashcode/solana/cm10.1/


    AOKP (Android 4.2.2): [B5]
    http://aokp.co/supported-devices/?id=58&device=solana

    Official release: [GETTING REBUILT FOR BOOT ISSUE]
    [03/06] - BT/Speakerphone Fix -- need to get a new build up(thanks DHacker)
    [03/05] - Official Release Build #5
    [02/26] - Official Release Build #4
    [02/26] - HWcomposer API 1.0 (JB-MR1 compliant)
    [02/26] - HD codec fixes
    [02/26] - Kernel updates / bugfixes for clock management, battery drain and stability

    OLDER AOKP:
    http://goo.im/devs/hashcode/solana/aokp/


    CyanogenMod 10:
    http://goo.im/devs/hashcode/solana/cm10/


    USING WITH GSM INFORMATION FOUND HERE (by Skreelink):
    http://xdaforums.com/showpost.php?p=34057016&postcount=1


    ICS BUILDS:

    CyanogenMod 9:
    http://goo.im/devs/hashcode/solana/cm9/
    ** NOTE: I Kept the HD Codecs alive in this build. I realize they are laggy and need work to reduce the memory impact.


    KERNEL NOTES:

    This is the same kexec kernel used in the CM9 builds, so expect all of the same issues (see below):
    - No Camera
    View
    32
    Hashcode
    Hashcode
    Re: [WIP][KERNEL][KEXEC] JB ROMS For Droid 3 [01/23: MMS/Kbd Backlight FIX]

    Hi guys,
    A quick update on what I'm doing atm.

    I've been taking the kexec kernel and walking back through every problem that it is currently having.

    This includes the high battery drain, and other "oddness" only present after kexec.

    Right now I'm working on the current kernel code, but I may go back and do a completely new build up of the kernel starting back from the 3.0.8 RAZR kernel again and work my way forward applying all of the fixes I have in the current branch.

    This would create a much nicer git history helping to maintain the kernel in the future.

    TL;DR: All of the current bugs in the kexec kernel have been identified and Im working on fixes. There is still no fix for the camera due to proprietary files which dont exist for the 3.0 kernel.

    Sent from my DROID RAZR HD using Tapatalk 2
    View
    28
    Hashcode
    Hashcode
    Just a side note today: I've fixed the download links in the OP. No new builds out (yet).

    Also, I've been working with DHacker to restructure our hosting / downloads site: rombot.org (formerly rombot.droidhive.com)

    The goal was for stability and added features.
    - Downloads at: http://files.rombot.org/
    - Bugtracker (in progress) at: http://bugzilla.rombot.org/
    - (Needs fixing) Gitweb tracker for the Android source projects we work on
    - Basic support forums for the devices that I work on
    - And eventually I'll be migrating my blog postings over to rombot.org as well.

    FYI: I will also continue to maintain the threads here at XDA and other active Droid 3 websites.

    Hope everyone is having a great day.
    View
    27
    Hashcode
    Hashcode
    UPDATED: 2013-02-26

    CURRENT DROID 3 DEVELOPMENT:

    CAMERA NOTES:
    ** I would never expect the camera to be fully functioning. I am working several avenues to get a functional camera on the Droid 3, but they're all sketchy at best. Just know that if you choose to flash custom ROMs w/ newer OS versions: You won't have a camera.
    ** Did I say don't expect the camera to be fixed? If it was to be fixed, trust me, you'll see me all over the boards, twitter and the social universe telling people about it.
    ** There are other devs now working on the kexec kernel and it's possible that they can get some basic camera functionality through kernel drivers. It's quite complicated and there are no public data sheets which describe the sensor functions in great detail for our devices.
    ** Don't expect the camera to be fixed.


    CHANGES OVER THE LAST MONTH:

    BATTERY LIFE / KERNEL BUGFIXES:
    https://github.com/STS-Dev-Team/kernel_mapphone_kexec/commits/3.0.31
    - Several internal clocks which were left active are now turned off as they should be. (since they're un-used)
    - IPI/LOCAL timers were re-enabled in the kernel. These are interrupt driven timers which help trigger various drivers for updates.
    - Bugfixes to allow other lower level functions to run in the kernel as well like gpmc
    - I've fixed the kernel bootlog recovery driver (/proc/last_kmsg) so that this now works in our kexec kernel. This is a copy of the last kernel bootlog from a prior boot. So if you crash, please reboot and pull /proc/last_kmsg with adb and send me a log via email: hashcode0f at gmail.com
    - Removed a hack to initiate the sound driver, causing it to stay active all of the time in the background. It now starts normally and suspends normally. (Thanks to kfazz for the fix).

    JB-MR1 DEVICE UPDATES WITH OMAPZOOM:
    https://github.com/STS-Dev-Team/android_device_motorola_solana/commits/jb-mr1
    - hwcomposer now updated to API1.0
    - domx (HD codec) code updated to the latest sources



    CHANGES OVER THE NEXT MONTH:
    - I'm taking the kexec kernel back to the beginning and re-merging Motorola's changes with the Texas Instrument changes that are needed to run the kernel on the Droid 3: memory allocations, HD codec binary changes, etc.
    - This process is already 3-4 weeks in the running, and will be another 2-3 weeks before it's done.
    - Once that kernel source is ready for prime-time, I'm going to swap the Droid 3 over to the new kernel source.

    WHY DO THIS?
    - By taking the time to create a full kernel history (from omapzoom) and integrate the Motorola changes into it, I can then migrate the kernel sources forward in a nice orderly manner cherry-picking new kernel commits directly from Omapzoom.
    - This should make for a much cleaner / more stable kexec kernel in the future. And allows other devs to see where I'm going w/ kernel development so that they can add to it. Each file shows how it was edited and by who so it's more transparent where Motorola made their changes to the original TI kernel.

    BATTERY DRAIN AND WHEN WILL IT BE "FIXED":
    - The current kernel cannot put the UART ports to sleep like a normally booted kernel can. There is an issue that happens during kexec where the clocks associated w/ the UART ports become stuck in a full enabled mode. Any attempts to place them in suspend or disable hangs the kernel. It's being looked at. Right now the device never really 100% suspends. Hence higher than normal battery usage.


    "OFFICIAL" ____ (AOKP/CM) MEANS WORKING CAMERA/BLUETOOTH AUDIO RIGHT?
    - No. Actually "official" just means you can repo init the source straight from either AOKP/CM and build the device w/o worrying too much about extra sources or patches, etc.
    - "Official" also means automated builds for the device (in some fashion). Currently for AOKP it's every 2-3 weeks and for CM it's nightly. These have the benefit of including any changes to the ROM automatically.
    - The device doesn't get any more devs
    - The device isn't magically fixed or more stable


    Just thought I'd toss that in :)
    View
    22
    Hashcode
    Hashcode
    Hi Guys,

    I know there hasn't been a whole lot of progress on the D3 front. It really centers around 3 main issues with the kexec kernel that I'm working on:
    - Deep sleep issues
    - Sensor issues
    - Stability / lock ups

    So, over the last few days, I took the stock RAZR kernel and cleaned it up quite a bit, trying to see if these issues would show up when booting the stock Moto ROM but with a 3.0.8 kexec kernel. Hoping to forward fort any fixes.

    You can see some of this work here:
    https://github.com/STS-Dev-Team/kernel_mapphone_kexec/commits/3.0.8

    Right now, I can see some sensor fixes, and possible stability improvements, but still seeing deep sleep issues.

    So, I'll keep hacking away on it.

    Sent from my XT894 using Tapatalk 2
    View

New posts