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

Search This thread
By:
Advanced…
dhacker29

dhacker29

Inactive Recognized Developer
May 27, 2011
1,802
3,819
Millsboro, DE
You have to flash the Chinese radio and edit the build.prop to use gsm

Sent from my XT912 using Tapatalk 2

---------- Post added at 01:20 AM ---------- Previous post was at 01:20 AM ----------

Bugtracker androidhosting.org:8050

Sent from my XT912 using Tapatalk 2
 
5318008

5318008

Senior Member
Aug 16, 2009
493
103
Portland, OR
dhacker29 said:
You have to flash the Chinese radio and edit the build.prop to use gsm

Sent from my XT912 using Tapatalk 2

---------- Post added at 01:20 AM ---------- Previous post was at 01:20 AM ----------

Bugtracker androidhosting.org:8050

Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse

I could be wrong here but I believe the radio flash and build.prop changes are to enable GSM specifically in the US. If you're using GSM internationally, just the unlock code should suffice.

--posted from my phone
 
H

harryspar

Senior Member
Nov 28, 2011
293
55
@glennj99:

I have an XT862 with the edited build.prop and GSM unlock for US, on ATT.

Calling and data work on older ROMs such as Steel Droid, but with CM10 I get voice and SMS but no data.

So before you go to Italy you might want to check if GSM data is working for you.
 
G

glennj99

Senior Member
Jul 7, 2012
78
16
No way to do that here in the USA, without first flashing the Chinese Radio. If I do that, CDMA will no longer work in the USA.

I'll just take my Nexus4 and unlocked Droid3 and maybe a VGNexus which I can tether to the Nexus4 (and maybe the Droid3 too) for Ingress in Italy.

I'll buy a WIND sim for the Nexus4 and try it in the Droid3 as well...no wrong size...no matter. I don't intend to place much voice calls.
 
FrankieDedo

FrankieDedo

Senior Member
Dec 26, 2010
86
35
33
Lucca
glennj99 said:
No way to do that here in the USA, without first flashing the Chinese Radio. If I do that, CDMA will no longer work in the USA.

I'll just take my Nexus4 and unlocked Droid3 and maybe a VGNexus which I can tether to the Nexus4 (and maybe the Droid3 too) for Ingress in Italy.

I'll buy a WIND sim for the Nexus4 and try it in the Droid3 as well...no wrong size...no matter. I don't intend to place much voice calls.
Click to expand...
Click to collapse
Buy a micro-sim adapter too, Nexus 4 has micro-sim and Droid 3 has normal sim ;)
 
H

harryspar

Senior Member
Nov 28, 2011
293
55
Update - after flashing hash code's April 9 build and applying the build.prop mods, I can get high speed GSM data on ATT.
 
K

krasoski

Member
Jun 9, 2009
32
3
Does Anybody had issues with contact info retrieving at sms?, After sending an SMS, on the messaging screen I can se whom I send the sms, but when I receive one, it only apperas the number. Could you please give me a hint on this?. It didn't happened to me with stcok GB ROM.
As a clarification, I save contacts with the country and area code so I if travel to another country I don't have to edit anything.
 
G

glennj99

Senior Member
Jul 7, 2012
78
16
glennj99 said:
No way to do that here in the USA, without first flashing the Chinese Radio. If I do that, CDMA will no longer work in the USA.

I'll just take my Nexus4 and unlocked Droid3 and maybe a VGNexus which I can tether to the Nexus4 (and maybe the Droid3 too) for Ingress in Italy.

I'll buy a WIND sim for the Nexus4 and try it in the Droid3 as well...no wrong size...no matter. I don't intend to place much voice calls.
Click to expand...
Click to collapse

WIND was too expensive so I bought a TIM micro-sim chip for like 10 E plus 10 more E for 1 gig of data, rechargable.
They gave me an adapter for the micro-simm so it would fit and it works on both Stock and Hashcode's latest Cyanogenmod 10.1 builds fine for data - have not tried voice. Gets HSPA or Edge or doddlesquat, depending on where I am. Often doddlesquat, unfortunately.

Plugged it into my Nexus4 as well, and it works exactly the same as in the Droid3.
 
H

harryspar

Senior Member
Nov 28, 2011
293
55
Does anyone know if ALL D3 kexec builds have to go in romslot1, or only JB? I'm wondering if cm9 can go in slot 2.
 
fxwrangler

fxwrangler

Member
Mar 12, 2009
33
15
cm9 rom slot

B
harryspar said:
Does anyone know if ALL D3 kexec builds have to go in romslot1, or only JB? I'm wondering if cm9 can go in slot 2.
Click to expand...
Click to collapse

Not sure about slot 1 for CM9 builds. I just recently went back to a Cm9 build from 20120820 and it works very well in my opinion. I wasn't sure about which slot so I went with Slot 1.. After a day of use, it seems pretty stable with a camera and video that works. I know this build is quite different than what is currently on the table, but I may stick with it. Its the one of the best roms I've put on my D3 other than minimoto( a gingerbread based from). I didn't find the OP to see if it tells in there, as it may be. Might tweet Hash (@Hashcode0f) and ask him.
 
H

harryspar

Senior Member
Nov 28, 2011
293
55
fxwrangler said:
B

Not sure about slot 1 for CM9 builds. I just recently went back to a Cm9 build from 20120820 and it works very well in my opinion. I wasn't sure about which slot so I went with Slot 1.. After a day of use, it seems pretty stable with a camera and video that works. I know this build is quite different than what is currently on the table, but I may stick with it. Its the one of the best roms I've put on my D3 other than minimoto( a gingerbread based from). I didn't find the OP to see if it tells in there, as it may be. Might tweet Hash (@Hashcode0f) and ask him.
Click to expand...
Click to collapse

Thanks, fxwrangler!

Was 0120820 a Kexec build?
 
Munckster

Munckster

Senior Member
Feb 6, 2011
223
26
Katowice
Is it available for download somewhere? Because I really want to use ICS, but at least with partial camera working.

In fact, I rather prefer to have a fully Non Kexec ROM working, instead of a Kexec ROM without the camera.

Thanks!
 
K

krasoski

Member
Jun 9, 2009
32
3
harryspar said:
Thanks, fxwrangler!

Was 0120820 a Kexec build?
Click to expand...
Click to collapse

fxwrangler said:
B

Not sure about slot 1 for CM9 builds. I just recently went back to a Cm9 build from 20120820 and it works very well in my opinion. I wasn't sure about which slot so I went with Slot 1.. After a day of use, it seems pretty stable with a camera and video that works. I know this build is quite different than what is currently on the table, but I may stick with it. Its the one of the best roms I've put on my D3 other than minimoto( a gingerbread based from). I didn't find the OP to see if it tells in there, as it may be. Might tweet Hash (@Hashcode0f) and ask him.
Click to expand...
Click to collapse

" it seems pretty stable with a camera and video that works. " I thought that any other version than GB makes camera works for Droid 3. Which one newer did you use to have them operationaly?
 
H

harryspar

Senior Member
Nov 28, 2011
293
55
No kexec roms have a working camera on the droid 3.
I've been quit satisfied with Steel Droid's non kexec ICS ROMs.

The camera works, but there are other bugs. The call audio and media audio sometimes go bad for reason, I find that turning Bluetooth on and off seems to help.
 
  • Like
Reactions: krasoski
Endoroid

Endoroid

Senior Member
Aug 28, 2011
1,463
311
Surrey
krasoski said:
" it seems pretty stable with a camera and video that works. " I thought that any other version than GB makes camera works for Droid 3. Which one newer did you use to have them operationaly?
Click to expand...
Click to collapse

The non kexec cm9 camera works, however it's a hack. It's slow, secondary functions like qr code scanning don't work and neither does video recording. Plus the rom has just as many bugs a kexec, just different bugs

Sent from my XT860 using xda premium
 
  • Like
Reactions: krasoski
R

rblanca

Senior Member
Dec 12, 2011
258
33
Endoroid said:
The non kexec cm9 camera works, however it's a hack. It's slow, secondary functions like qr code scanning don't work and neither does video recording. Plus the rom has just as many bugs a kexec, just different bugs

Sent from my XT860 using xda premium
Click to expand...
Click to collapse

And I think that there isn't HW Codecs
 
fxwrangler

fxwrangler

Member
Mar 12, 2009
33
15
  • Like
Reactions: harryspar, ricky12 and Munckster
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