5,600,919 Members 42,395 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
Hashcode
Old
(Last edited by Hashcode; 10th April 2013 at 06:23 PM.)
#1  
Hashcode's Avatar
Recognized Developer - OP
Thanks Meter 19693
Posts: 2,932
Join Date: Sep 2011

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

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://forum.xda-developers.com/show...16&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
The Following 117 Users Say Thank You to Hashcode For This Useful Post: [ Click to Expand ]
 
Hashcode
Old
(Last edited by Hashcode; 26th February 2013 at 05:55 PM.)
#2  
Hashcode's Avatar
Recognized Developer - OP
Thanks Meter 19693
Posts: 2,932
Join Date: Sep 2011

 
DONATE TO ME
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/kern...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/andr...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
The Following 27 Users Say Thank You to Hashcode For This Useful Post: [ Click to Expand ]
 
duncan254
Old
#3  
Senior Member
Thanks Meter 5
Posts: 108
Join Date: Nov 2010
How do I get from safstrap 1.0.8 using mavrom 4.5 to test this baby. Fairly detailed please. I have eta 906 btw.

Sent from my DROID3 using Tapatalk 2
The Following User Says Thank You to duncan254 For This Useful Post: [ Click to Expand ]
 
niko99
Old
#4  
niko99's Avatar
Senior Member
Thanks Meter 124
Posts: 277
Join Date: May 2008
Wohhhhaaaa thank you !!!!!

downloading ......

i will see how its work in Europe
Using a own Droid 3 rom called DROM
http://forum.android.com.pl/showthread.php?t=158868
The Following User Says Thank You to niko99 For This Useful Post: [ Click to Expand ]
 
MrObvious
Old
#5  
MrObvious's Avatar
Senior Member
Thanks Meter 250
Posts: 1,807
Join Date: Mar 2008
Location: Wichita KS
Dude awesome. Thanks so much! Does the camera work?

Sent from my xt862 using xda app-developers app
The Following User Says Thank You to MrObvious For This Useful Post: [ Click to Expand ]
 
kernelguy
Old
#6  
kernelguy's Avatar
Senior Member
Thanks Meter 11
Posts: 106
Join Date: Jul 2007
Location: Bangalore
Quote:
Originally Posted by duncan254 View Post
How do I get from safstrap 1.0.8 using mavrom 4.5 to test this baby. Fairly detailed please. I have eta 906 btw.

Sent from my DROID3 using Tapatalk 2
From the experience of various users, all one needs is an update of safestrap to 2.0 and the flash of the kexec ROM. I did this over stock, CM7 and CM9. Many other users have gone from other ROMs - including some version of mavrom.

---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------

Quote:
Originally Posted by MrObvious View Post
Dude awesome. Thanks so much! Does the camera work?

Sent from my xt862 using xda app-developers app
Nope. Or should I say not yet...
Droid 3 | DoCoMo GSM | CM 9.x
Droid2 Global (stolen)
AT&T Tilt (Kaiser) CM6.x (broken screen)
The Following User Says Thank You to kernelguy For This Useful Post: [ Click to Expand ]
 
duncan254
Old
#7  
Senior Member
Thanks Meter 5
Posts: 108
Join Date: Nov 2010
Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?

Sent from my DROID3 using Tapatalk 2
The Following User Says Thank You to duncan254 For This Useful Post: [ Click to Expand ]
 
the_linkin3000
Old
#8  
Junior Member
Thanks Meter 9
Posts: 29
Join Date: Jan 2008
Location: Resistencia
Quote:
Originally Posted by duncan254 View Post
Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?

Sent from my DROID3 using Tapatalk 2
I think that the steps to follow would be something like
1) Go back to non-safe/stock
2) Uninstall safestrap 1.08 from there
3) Install the new one
4) Go to safe mode and finally
5) Flash the build and admire that precious CM9 bootanimation :P

That's what I would do anyway, I didn't have to since the first safestrap I've ever installed was the 2.0/kexec version

Enviado desde mi GT-I5510 usando Tapatalk 2
The Following User Says Thank You to the_linkin3000 For This Useful Post: [ Click to Expand ]
 
duncan254
Old
#9  
Senior Member
Thanks Meter 5
Posts: 108
Join Date: Nov 2010
I just deleted old safestrap and installed new one on safe system. Everything appears fine. However, the dl is not working.

Sent from my DROID3 using Tapatalk 2
The Following User Says Thank You to duncan254 For This Useful Post: [ Click to Expand ]
 
rojocapo
Old
(Last edited by rojocapo; 30th July 2012 at 01:38 PM.)
#10  
Senior Member
Thanks Meter 29
Posts: 122
Join Date: Dec 2011
Location: Buenos Aires
GSM on Movistar Argentina network is working fine (850 mhz/1900mhz UMTS). SMS is ok too.

The GSM level indicator is stuck in the middle. *#*#INFO#*#* Phone information says Signal Strength 0dBm 97 asu. Seen this before in previous ICS builds. Signal indicator works fine in non-safe 906.

Wifi seems solid. Netflix and mp4 video is working

Guess we "just" need audio and camera now.

Thanks Hash and kexec team

EDIT: Oh, and I forgot to say F*CK YOU MOTO!

The Following 5 Users Say Thank You to rojocapo For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes