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/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
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
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
Wohhhhaaaa thank you !!!!!
downloading ......
i will see how its work in Europe
Dude awesome. Thanks so much! Does the camera work?
Sent from my xt862 using xda app-developers app
duncan254 said:
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
Click to expand...
Click to collapse
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 ----------
MrObvious said:
Dude awesome. Thanks so much! Does the camera work?
Sent from my xt862 using xda app-developers app
Click to expand...
Click to collapse
Nope. Or should I say not yet...
Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?
Sent from my DROID3 using Tapatalk 2
duncan254 said:
Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
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
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
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
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!
Amazing! :good:
THANK YOU CM9 TEAM!
and hash and jonpry
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
rojocapo reports it as working on GSM in argentina, so I wonder what the difference might be.
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
rojocapo said:
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!
Click to expand...
Click to collapse
By GSM you are referring to voice calls, or to voice calls plus data connection? And if data connection is alive in this build, did you need to configure the APNs?
Enviado desde mi XT860 usando Tapatalk 2
thingonaspring said:
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
...
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
Click to expand...
Click to collapse
Is doing the '#info' stuff the same as going to the Network Settings and clicking on the right radio button? For me, the default is CDMA/WCDMA and selecting GSM Auto does the trick, but not without a reboot.
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
rojocapo said:
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
Click to expand...
Click to collapse
I have problems with usb charging on all roms. Only works in usb mass storage mode.
Sent from my XT860 using xda premium
the_linkin3000 said:
By GSM you are referring to voice calls, or to voice calls plus data connection? And if data connection is alive in this build, did you need to configure the APNs?
Enviado desde mi XT860 usando Tapatalk 2
Click to expand...
Click to collapse
thingonaspring said:
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
rojocapo reports it as working on GSM in argentina, so I wonder what the difference might be.
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
Click to expand...
Click to collapse
By GSM I am referring to voice plus data connection. I always use an app called HiAPN to automatically detect my APN settings by reading the network id from the SIM card. The app was complaining about "no SIM card inserted", so did INFO and set the network to GSM auto. After a reboot HiAPN set the APN correctly and data was working.
I was also getting the "number unavailable" message before setting the network to GSM auto and rebooting.
rojocapo said:
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
Click to expand...
Click to collapse
LOL! Yeah, and the battery indicator is broken.
Bobbar said:
LOL! Yeah, and the battery indicator is broken.
Click to expand...
Click to collapse
Yup, it's broken.
BTW, I tried the Razr Beats patch and I still have no sound.
Related
A test/stock anykernel for CM6 inc is up on rom manager under the Koush section. Please test it out and let me know how it compares. I am working on tracking down some instability issues.
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Used it for a day...
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
sucker4pa1n said:
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
Click to expand...
Click to collapse
2.15.00.09 radio literally KILLED my battery. I went back to 2.15.00.07 and battery life is great again. FYI.
Everything is good for me with this kernel. No issues. Flashed it last night.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
At the moment, I'm using Miui but wanted to note that this is the only kernel which allows Pre-9 Wifi tether to work on Miui (in my hands, King's #1 and #2 AOSP kernels gave me errors with Wifi Tether). Thanks for providing this kernel, Koush. Will give it a try with CM and see how that goes.
I had a soft reboot last night with this new kernel while I was on facebook. 0 wifi used.
Radio 2.15.00.07
Not sure if it's the kernel or just the latest nightly, but I'm loosing my data connection quite often. Otherwise, its running great.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
My built in wifi tethering isn't working either....sad day. I was loving how fast my phone charged
New version, number. 11 is online, testing now.
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
mikeacela said:
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
Click to expand...
Click to collapse
Funny, I'm running the test2 on Ruby as well. Been rock stable for 4hours. Practically a record for my phone on Ruby. Hope it makes it through the night.
Using the "test2" kernel.
Built in tethering works for me.
I'm running the 9/27 nightly.
No other issues so far.
P.S. I would love if internal memory was mounted properly in Windows.
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Another question would be, does anyone know if test kernel #1 or #2 is the test kernel in rom manager?
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
showing up as a 245-998mhz one with compcache optional... Not that I put much credence in quadrant scores, but I'm pulling over a 1300 on that. So plenty quick.
Also does anyone know if its undervolted?
Sent from my INCREDIBLE using Tapatalk
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
#2 is running at default clock.
So far looking good on test#2 for me (9.26 nightly). I just had a meeting in a location where the phone has frozen up nearly every time I was running CM 6.02 or any previous build and it worked fine. If I make it out to lunch, then back home later today without a freeze I think we may have a winner. Or at least I'll have a winner...
I grabbed the test kernel on friday night via the ROM manager, am I running the latest test, or is there a new one with the same name? In other words do I have to redo it to get the test #2 I am seeing comments about?
I am running test2 and my only issue is with wifi cutting out and erroring out when running things like streaming media in the background, but no reboots. Tt just cuts out the wifi, and resumes relatively well upon turning the screen back on. For some reason the screen being off sets off a timer that cuts out the wifi after a while. I've tested this with both Pandora and Slacker. No cut outs when running over 1x CDMA (3G doesn't work in my office) except when my signal becomes nonexistant.
Just seen this tweet from Dhacker29!!!!!
First Off Working Cam!!!!!! YEAH!!
I knew they would get there!!!
This is basically the same rom from Dhacker29's last release but with the cam working!!!
You need to be on the .902 update to install this. If your not follow instructions Here or Here.
What works:
CAMERA!!
Graphics working smooth now (Hashcode)
Adb is working so we can track the rest (Hashcode)
Touchscreen (Hashcode)
Capacitive buttons (Hashcode)
Charging indicator (Hashcode)
BlueTooth
Both SDCards mounting on phone
Builtin Screenshot (CM)
Reboot menu (CM)
Phone and SMS works
GPS fully functional
Audio fully working (Hashcode audio wrapper based on tpruvot’s Defy work)
USB Mount working for sdcard-ext (Hashcode)
Gallery recognizes both cards (Hashcode)
1x/3g/lte data working
NOTE: you may have to dial *#*#4636#*#* (or use Phone Info from the market) and toggle data mode between modes. For me toggling to GSM only till the screen flashes and then back to GSM/CDMA auto (prl) works perfect. It will show data for a sec then flash off and about 30 seconds it will pop up to full data.
Not Working:
Front Facing Cam(really messed up you look at it)
Face Unlock
Cam Video
SafeStrap for Bionic
http://db.tt/D624eHLF
Rom
http://t.co/MLRC1IhL
ICS G-Apps
http://t.co/oKqQs4g3
.902 update
http://db.tt/g0gm69Hq
Get A Twitter Account!!
PS: Really Cool BootAnimation
Sent from my PC using XDA
"@dhacker29: OK technical deficulties on Bionic wrong upload.. cam will be out at some point tonight lol if I can upload. site is taking beating"
This is his latest tweet. Don't flash just yet
Sent from my DROID BIONIC using Tapatalk
Does hotspot hack work on this build. What isnt working?
Sent from my Samsung Galaxy S II Epic 4g Touch using XDA App
booting this up right now. ive been at boot anin for a couple mins now. hoping for the best
dm1027 said:
"@dhacker29: OK technical deficulties on Bionic wrong upload.. cam will be out at some point tonight lol if I can upload. site is taking beating"
This is his latest tweet. Don't flash just yet
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
DH just posted another link that should work this time from his twitter.
"Bionic AOKP Build 15 with cam fix for real http://bit.ly/AOKP25Bionic Gapps: "
not sure how to post links, just check him out on twitter...
Anyone have a link to just the camera fix as I don't use twitter.
You dont need a twitter account to view his tweets https://twitter.com/#!/dhacker29
I've Finsihed editing the OP. Sorry guys, Bricked my phone last night trying to get this right. All the links are correct and are safe for download.
How's it coming people? I haven't seen any bugs or problems other than the Cam Video.
Hotspot hack?
Sent from my SPH-D710 using XDA App
fabs109 said:
Hotspot hack?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
There is already a WiFi Tether app installed.
Sent from my XT875 using Tapatalk
Hello all. It looks like the DATA is not working. It was good when I installed it, but after that it kept going in & out & now there is no DATA connection. It shows 3G/4G but there is no connection. I have full bars but they are Gray not Blue And yes I did that *#*# thingy.
Chrome does not seem to work
Tried installing chrome beta browser, but it says that my version of android is not supported, needs 4.0 or higher. Anyone able to get chrome to work?
lawtalking said:
Tried installing chrome beta browser, but it says that my version of android is not supported, needs 4.0 or higher. Anyone able to get chrome to work?
Click to expand...
Click to collapse
I don't think chrome is working on any of the ics roms yet. I haven't tried any of the ics roms in a few days but it's always one of the first things I check (even though its not going to have flash). I'll be playing around with ics over the weekend so I will be able to see if that particular problem was fixed but its only alpha so its no big deal if it isn't.
Sent from my DROID BIONIC using XDA App
iNsAnEmOd said:
How's it coming people? I haven't seen any bugs or problems other than the Cam Video.
Click to expand...
Click to collapse
youtube videos are the only problems i'm having now, they stutter and don't play correctly, i've seen this is a common problem with ics roms and no video acceleration at this point though
smokedkill said:
I don't think chrome is working on any of the ics roms yet. I haven't tried any of the ics roms in a few days but it's always one of the first things I check (even though its not going to have flash). I'll be playing around with ics over the weekend so I will be able to see if that particular problem was fixed but its only alpha so its no big deal if it isn't.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Beta
Sent from my XT875 using Tapatalk
herach said:
Hello all. It looks like the DATA is not working. It was good when I installed it, but after that it kept going in & out & now there is no DATA connection. It shows 3G/4G but there is no connection. I have full bars but they are Gray not Blue And yes I did that *#*# thingy.
Click to expand...
Click to collapse
That may just be for you, I have been running it all day with no problems, besides the front camera, video, and everything else that is known. Try going to settings, then under Wireless & networks > network mode > click GSM only, wait for screen to flash, then hit LTE/CDMA again and after about 30 seconds you should have data.
Skidoo03 said:
That may just be for you, I have been running it all day with no problems, besides the front camera, video, and everything else that is known. Try going to settings, then under Wireless & networks > network mode > click GSM only, wait for screen to flash, then hit LTE/CDMA again and after about 30 seconds you should have data.
Click to expand...
Click to collapse
I give thanks for everyone that doesn't
Sent from my XT875 using Tapatalk
Skidoo03 said:
That may just be for you, I have been running it all day with no problems, besides the front camera, video, and everything else that is known. Try going to settings, then under Wireless & networks > network mode > click GSM only, wait for screen to flash, then hit LTE/CDMA again and after about 30 seconds you should have data.
Click to expand...
Click to collapse
Ya. I have done that too. No luck. Well, I'll just go back to GB till a stable working ROM is out, and thanks to everyone and all the Devs that are working hard for us. I just wish that I had the knowledge of doing this but unfortunately I don't. So, all the DEVS out there, THANK YOU.
Now on 2-24 ICS and 2-17 Gapps this morning, here are my initial thoughts after coming from 2-10:
- Camera will take photos but does force close for me after each photo taken
- I had to toggle GSM Only --> GSM/CDMA auto (PRL) a few times today to get data back
- Twitter app has FC'd a few times for me, never did with 2-10
- ICS Music app won't start, FC's as soon as I try to load it. The old Google Music app does work
- Having battery icon at top display increments is great (even if it is only by 10%)
- Google+ FC's like whoa
That is all for now. I did not wipe data when I flashed the new version so take this for what its worth. I just didn't have time to, still might if others don't notice these issues.
Greetings,
Just a few days ago I installed the most recent CM 10.1 nightly, first 20130319 and now updated to 20130323. For the most part, my phone is working well, but I do not have any 3g data service nor have I had it since installing CM 10.1.
I have a Droid 3 XT862 being used in the US on Verizon's CDMA network and placing and receiving calls works. I *can* send and receive SMS as well, although in a test I did toay I sent very short 25 character text from my Droid 3 on the Verizon network to another Android device on the Sprint network and it arrived a mere 2h15m later.
I have read many messages on this forum and others, but either the problem addressed is too far removed or the ideas/changes suggested are offered with little explantion as to why, so I am unsure if making any of these changes would be a good idea. I did read through the build.prop on my device and it certainly appears that it is more or less configured and ready for CDMA usage. I have performed a *228 PRL update, but it did not appear to help. CM 10.1 makes available, unlike the stock ROM, a menu/page full of mobile network settings. I have tried to work with some of these settings, toggles, preferred network types, and so on, but again none of these changes seems to have had an effect on my 3g data connection.
Am I doing something wrong? Does anybody know how to fix this? Or perhaps it is a new/temporary bug in CM 10.1?
As for the operation of everything else under CM 10.1, I like it very much. It is a very big step up from before, when I was first using stock Android 2.3.4 followed by the Maverick ROM, which, while better, sure liked to crash/reboot when under memory pressure. I do have a few issues that I hope others might be able to help with:
* The hardware keyboard's ALT key does not appear to work anymore which rules out half the symbols on the keyboard, making it far less useful. I also cannot use it any longer with VX ConnectBot as some of the mappings do not seem to work. For example, the "OK" key used to work as a CTRL key. Maybe these are related? Any idea how to fix this?
* The backlight on the hard buttons and on the keyboard was, previously, triggered by a light sensor (I think). Now the backlight comes on when there is any tapping, swiping, or button/key activity. That's fine, except that the timeout for the light is extremely short, on the order of about two seconds. In a dark environment, this can be annoying.
* It's slow... my god is it slow! I think this is due almost entirely to a severe lack of free RAM on the device, but I don't know what to do about it. Some programs, like GMail, take forever to start, while many others are just very slow to use/respond. I see the "Not Responding" popup appear *much* more than ever before, but, as I know these apps are just slow and not dead, I always just tap on "wait" and go on with what I was doing.
I really don't think I have that much running in the background or foreground to use all of this RAM. I have replaced Trebuchet with NemusLauncher in hopes of freeing some memory. I have three widgets only: a clock/weather widget, the standard calendar widget, and the Google Voice inbox widget. In the background, besides whatever Android and CM run, I have Google Voice and imo (the instant messanger) running. I believe that is it. Is there *anything* I can do to improve the speed issue? I understand how Android handles memory, so it is clearly not about just increasing the "free RAM" value. That said, however, it seems that if there were fewer apps trying to use the limited memory then this would naturally be higher to begin with.
I have a decent collection of apps, but the number is much smaller than in the past and most all of them should remain dormant unless I actually run them... or so I believe.
Okay, so those are the issues. I could add battery life and the camera to that list, but I have read on the forum that, no thanks to Motorola, the camera is unlikely to be available anytime soon, and I have also read that the battery issues should be resolved soon.
So, um... please help! And great many thanks to all of the hard working devs who bring us better software and especially to those who help those of us with devices that are practically *new* and yet abandoned by the carriers. Extra kudos to those finding ways to work around locked bootloaders and proprietary binary blobs.
--John Gruenenfelder
Can you force it to EVDO only? And what happens in a stock ROM?
In the mobile network settings page, as mentioned above, I can, and have, tried many of the options. Among them is the preferred network type.
It defaults to 'global' which actually sets it to LTE/CDMA, though this is not an LTE device. I have tried all of the options that make sense (i.e. nothing GSM related). I have tried Evdo-only and currently have it set to 'CDMA/Evdo auto'.
None of these settings has changed anything. To test, I disable WiFi and see if I have a Net connection.
With the stock ROM, as well as the Maverick ROM, when I have 3g, the letters '3g' appear in the status bar next to the mobile signal strength icon and there are two small arrows to indicate I/O. This is what I expected to happen with CM.
-Sent from my XT862 using xda app-developers app
I have a 3g update, but no solution yet.
In the mobile net settings page I have the network set to 'CDMA/EvDo auto'. Then I turn on airplane mode to force the radio off, then turn airplane mode back off.
The radio comes back and as it does I can see the network strength icon briefly add an R, presumably meaning reconnecting, followed by a 1x, and finally by a 3g. Then the 3g disappears. This entire sequence takes only about 3 to 5 seconds. If I do this while viewing Settings->About->Phone, I can see the current radio/network states change. Of course, I do all of this with my local wifi connection off.
Also, I did try a network type of 'EvDo only' and the above sequence still occurred but without the 1x step. However, this sequence didn't seem to occur as reliably as when the network is set to 'CDMA/EvDo auto'. For reference, the phone info page under settings indicates that this phone or network is 'CDMA - EvDo rev. A:6'.
So, it would seem 3g is at least possible, if fleeting. What should I do now? I really don't want to stop using CM 10.1.
--John Gruenenfelder
Same issue here. No 3g. In the system status, it will briefly show the mobile network status as "connecting" then drop back to disconnected.
If you reboot into stock it works right?
MrObvious said:
If you reboot into stock it works right?
Click to expand...
Click to collapse
Me or rocksolid99?
In my case, I, well, did not follow the correct Safestrap update procedure when I went from 1.x to 3.05. As such, I *think* my stock ROM may be slightly hosed. I *do* have a complete backup of the original stock that I created with Safestrap 1.x, but 3.05 does not "see" it when I tap on the "Restore" button in recovery. So, I have it, I'm just not sure what I should do if I really need to restore that backup.
However, I have installed the Minimoto 1.7 ROM into slot 2 in Safestrap 3.05 and if I use that ROM (which is a super stripped down Droid 3 stock) then 3g works just fine. I did not have any network/connection issues and did not need to take any extra steps to get 3g to work.
--John Gruenenfelder
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium
Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Click to expand...
Click to collapse
Really? Good to know. Thanks for the info.
If I might reiterate on my other CM 10.1 problem, they keyboard? Right now, the ALT key does not work which means that I cannot access most of the punctuation keys. Strangely, in many apps when I press ALT I will see the cursor change with the upside down triangle at the top of the cursor bar indicating that ALT has been pressed. Good, but if I press any other key it is not recognized. It is as though I had not pressed anything. The ALT indicator doesn't even change or go away. The only thing I can do is continue to press the ALT key to cycle through its states (off, one-key, locked). Could this also be a bug in CM 10.1?
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Thanks again!
--John Gruenenfelder
JetpackJohn said:
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Click to expand...
Click to collapse
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Click to expand...
Click to collapse
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.
doogald said:
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.
Click to expand...
Click to collapse
+1 anything above gingerbread is not stable. Some people manage to use them for daily drivers but they have to deal with the bugs. Myself, I need a camera and I need my phone to work all day, I use it for my job. As such, I run minimoto, as it is quite stable, and any bugs that do arise can be dealt with as it's based on gingerbread, which is stable on our devices. Liberty is also a good rom to use, it's based on an older system version but it's quite stable and has lots of features, as opposed to Minimotos minimalist goal.
Sent from my XT860 using xda premium
has anyone tried making a swap partition for cm10.1 ?
I made it and it seems to be much much faster or the latest nightly (04/07/2013) is quicker.
anyhow I have it up only for about an hour it remains to be seen during the day how it's reacting
regards
Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Have you (or has anyone) successfully booted CM10.1 on the XT860? I just get bootloops after install. MiniMoto has been working great for me though.
Hello.
I recently dusted off my Australian Velocity after the Nexus 5 went for a swim at the beach. I have S-off, rooted and installed the albinoman ROM.
There are a couple of issues I have noticed so far.
The 4g connection is patchy at best. Not very stable at all but I can live with that.
The battery indicator is acting strangely it stays in 100% for ages but then it starts going down very quickly until it gets to 14% where it stays for a long time but once it gets past that it just goes to full discharge very fast.
I am having the same issue that many other guys and my MMS capabilities are not working. The phone just stays sending or retrying but messages never leave.
Any suggestions about what to do? I have wiped and reinstalled the ROM a few times and it makes no difference.
On the other hand I love the overclocking capabilities makes the phone feel a bit more responsive.
Thanks and keep up the good work
munecito said:
Hello.
I recently dusted off my Australian Velocity after the Nexus 5 went for a swim at the beach. I have S-off, rooted and installed the albinoman ROM.
There are a couple of issues I have noticed so far.
The 4g connection is patchy at best. Not very stable at all but I can live with that.
The battery indicator is acting strangely it stays in 100% for ages but then it starts going down very quickly until it gets to 14% where it stays for a long time but once it gets past that it just goes to full discharge very fast.
I am having the same issue that many other guys and my MMS capabilities are not working. The phone just stays sending or retrying but messages never leave.
Any suggestions about what to do? I have wiped and reinstalled the ROM a few times and it makes no difference.
On the other hand I love the overclocking capabilities makes the phone feel a bit more responsive.
Thanks and keep up the good work
Click to expand...
Click to collapse
As for the 4G connection, once you've accumulated 10 posts you should mention this in the CM 11 ROM thread and ask if the APN needs to be any different than normal (or if the mod changes the APN). The battery issue should get fixed if you let it fully charge and fully discharge about 3 times. The MMS capabilities is a known issue; try the specific nightlies that albinoman recommended to fix the MMS issue. New nightlies might break previous fixes and stuff.
Same Issue
I'm having the same issue here for AT&T HTC Vivid, none of my MMS were sent, nor have I received any. It's really essential for me cuz of my group, clubs have MMS and inorder for me to get those notifications I need MMS.
Calls are okay, but there are times where there's no sound on the other caller, so to fix that I end call and call again, which fixes it.
One final issue I've been having since Jellybean and Kitkat is the proximity for when calls, it does not respond. So i have to turn on Settings>Accessibility>Power button to end a call, because the phone's screen stays black during call, and 10-30 seconds after call. Camera is okay too, but doesn;t function well in video recording in apps like Snapchat and Instagram.
Overall, it's a great ROM by albinoman, I wish the Sweep2Wake is soon embedded, that's really great and wayyy better than the power button.
projectisaac said:
As for the 4G connection, once you've accumulated 10 posts you should mention this in the CM 11 ROM thread and ask if the APN needs to be any different than normal (or if the mod changes the APN). The battery issue should get fixed if you let it fully charge and fully discharge about 3 times. The MMS capabilities is a known issue; try the specific nightlies that albinoman recommended to fix the MMS issue. New nightlies might break previous fixes and stuff.
Click to expand...
Click to collapse
Thank you very much.
I tried Albinoman suggested rom and I still have issues with MMS.
The battery indicator is normalising as you said it would.
I know about the 10 posts count but it is hard for me to just write a post for the sake of getting the count up.
Yeah, I hear ya, I've been there before too. The posts will generally come easily and quickly posting to q&a and general, so you're on the right track
Sent from my Vivid 4G using xda app-developers app
Similar question
I'm also in Aus.
Been running CM versions now for over a year.
The new CM11 has been trouble free, with one quirky problem. I manually set my network preference to 2G at one desperate battery extending moment.
Now i can't find how to select "4G"??? When i use the preferred network type i only have 2 or 3G as options.
When i search for available networks i get an "error"
Cheers
Mike
Mikeyr1000 said:
I'm also in Aus.
Been running CM versions now for over a year.
The new CM11 has been trouble free, with one quirky problem. I manually set my network preference to 2G at one desperate battery extending moment.
Now i can't find how to select "4G"??? When i use the preferred network type i only have 2 or 3G as options.
When i search for available networks i get an "error"
Cheers
Mike
Click to expand...
Click to collapse
Well, I just did what you did, and rebooting does not fix it, nor does clearing the data of various apps installed. I'll post this to the CM11 thread and see if any answers or ideas are brought to light.
ngelTV should
projectisaac said:
Well, I just did what you did, and rebooting does not fix it, nor does clearing the data of various apps installed. I'll post this to the CM11 thread and see if any answers or ideas are brought to light.
Click to expand...
Click to collapse
Many thanks, i saw the post!
Yeah I tried clearing everything. Did a manual reinstall of the APNs using a number of different configs.
Did the wipes ....... did a little dance .... pulled the battery and sim ...... sacrificed a small packet of tofu (no goats, i like goats) The gods of mobility have still not smiled my way.
Wont find networks when i do a search yet am nicely connected, can make calls etc etc.
thanks for trying. If i get no joy will reflash a nightlie and see if it resets?!
Yeah, although wiping the caches didn't do the trick, reflashing a nightly (along with wiping data, cache, and dalvik-cache) should take care of the problem. If you are really attached to your app settings, look into titanium backup for backing up your apps along with their data; it's also the way I save my WiFi passwords.
Sent from my Vivid 4G using xda app-developers app
OK...
If you don't like my dialer solution... I have found 2 xposed mods that do what you want...
Intelli3G... And GravityBox...
They both hook the dialer to force network changes...
Sent from my Vivid 4G using Tapatalk
rignfool said:
OK...
If you don't like my dialer solution... I have found 2 xposed mods that do what you want...
Intelli3G... And GravityBox...
They both hook the dialer to force network changes...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
Hi, tried the dialer solution and no joy.
Installed INtelli3G but it needs the xposed framework which simply won't install. Have tweaked instal options appropriately so it should???
Mike
EDIT My bad, didn't like installing from bluetooth transfer, downloaded on phone worked .... will test I3G
Fixed
Many thanks rignfool
I installed xposed and Intelli3g and with a bit of mucking around now have 4g back!
Seems to work, have 4g 4 bars!
My initial attempts to force lte caused me to have no coverage (I was at work in North SYd so good LTE normally).
Using the "use all" option in Intelli3g, a reboot and swapping around towers was the trick for me.
Thanks again
Mike
Awesome! Do you want to make a step by step instruction set on how to fix that? I would like to know, and I'm sure a newbie who runs into the save problem would really appreciate it.
Sent from my Vivid 4G using xda app-developers app
Im on the newest nightly build of CM11, On ATT. MMS not working and I have no clue on how to get it to work. Anyone wanna help?
VividTheMan said:
Im on the newest nightly build of CM11, On ATT. MMS not working and I have no clue on how to get it to work. Anyone wanna help?
Click to expand...
Click to collapse
Known issue, you just have to be patient until it gets fixed (no one has gotten it to work)
UNOFFICIAL AICP for the Sprint HTC One
Since @superfes is no longer using this phone, I figured I would post some unofficial builds of AICP (Android Ice Cold Project). The previous thread is intended for closure, so we can use this one. To be clear, I'm only compiling this ROM and will not be troubleshooting specific issues. I will do my best to troubleshoot, but no guarantees. Any help on this front is appreciated - I'm new to this and am interested in continuing to learn.
I'm planning on putting together a build once every week or two for personal use and will share that with you guys.
Obligatory disclaimer: I am not responsible for any trouble you may run into with flashing or otherwise using this ROM. Just because it is working well for me does not guarantee that you will have the same experience.
For those of you wondering what AICP is: http://aicp-rom.com
Download link
10/3/2015: Google drive: https://drive.google.com/open?id=0B0lza8kzVL9RSVNnUzdoT0J5QWs
Build notes
10/3/2015
- Fresh build from 10/3
- Tested service / data when moving and no issues
- Remember that I am not troubleshooting specific issues. I'm not a developer. If you wish to post a logcat or anything like that though, feel free and I will take a look but not necessarily be able to provide a solution
- Yes, the digital roaming display is still there. In fact, when you see digital roaming, this is a sign that you are in service. 'Sprint' shows up when you are roaming so it is backwards.
9/27/2015:
- Didn't make clobber so build that hasn't been updated since 9/19 does not show an update (i.e. build will say 9/19 in many places since that was my last full repo sync). For future builds I will do this but didn't feel like waiting that many hours today
- Cherry-picked tdhite's commit from PAC ROM: http://review.pac-rom.com/#/c/13403/
------This has fixed the com.android.phone crashing problem + service being dropped
------ Usable as a daily driver again!
- From a full day on this ROM it's running smoothly and without errors
- 'Digital Roaming' display-only issue persists (been there for a long time now - no surprises here), and it is not indicative of actually roaming. Go into settings / about / sim status to definitively determine what your service status is.
Reserved
Reserved for now
Appreciate any feedback you guys have too
I'll give it a try and let you know.
Sent from my One using Tapatalk
wmatheney said:
I'll give it a try and let you know.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I couldn't get a solid connection. It was roaming and when I toggled the network type to global, I lost connectivity. I toggled back to CDMA/LTE but still no connection. I toggled Airplane mode. Still no go. I then changed it to Global and got a connection finally, but it was still roaming.
I hope this helps.
Sent from my One using Tapatalk
Same issue I've noticed everywhere, no proximity sensor feedback when in dialer!
I'm not pushing the power button every time I get called or I make a call. Only reason I'm still glued to 4.4.4.
Tjis is my 3rd m7 on kk and lp Ota, all 3 on both revisions, same issue.
Sent from my One using Tapatalk
wmatheney said:
I couldn't get a solid connection. It was roaming and when I toggled the network type to global, I lost connectivity. I toggled back to CDMA/LTE but still no connection. I toggled Airplane mode. Still no go. I then changed it to Global and got a connection finally, but it was still roaming.
I hope this helps.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
The digital roaming issue is cosmetic - that one's to be expected (see build notes; you are probably not roaming). As for the connectivity drop, I haven't run into that. If that's happening infrequently and you can deal with the display issue, this ROM should be otherwise fine for service-related actions (calls/texts) in my experience over the last couple of days.
swerff said:
Same issue I've noticed everywhere, no proximity sensor feedback when in dialer!
I'm not pushing the power button every time I get called or I make a call. Only reason I'm still glued to 4.4.4.
Tjis is my 3rd m7 on kk and lp Ota, all 3 on both revisions, same issue.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Yes, that one is pretty annoying. I have also noticed it on AOSP LP ROMs including this one and just deal with it. Sorry to hear that's holding you back. If there's a fix out there and I come across it, I'll be sure post about it and add to the ROM if applicable.
You can port camera stock m7?
http://www.apkmirror.com/apk/htc-co.../htc-camera-7-30-581119-android-apk-download/
Vember31 said:
Yes, that one is pretty annoying. I have also noticed it on AOSP LP ROMs including this one and just deal with it. Sorry to hear that's holding you back. If there's a fix out there and I come across it, I'll be sure post about it and add to the ROM if applicable.
Click to expand...
Click to collapse
Do you need a log cat when doing anything? Sensor programs show the proximity responding as expected.
Sent from my One using Tapatalk
First of all, great ROM! Have used AICP on my Nexus 4 and my TF300T in the past and it's always been a nice, stable ROM. Just got one question about non-market apps. I've been unable to install any, though I do have the option enabled in the Security menu. From what I've been able to tell, I can start the install of non-market apks with no problem but then the install screen closes by itself and once or twice, I've seen a pop-up that says something about Anti-piracy software activated. Is there any way around this?
So I need Gapps with this ROM?
How about MM?
Any aicp work?
Sent from my One using Tapatalk
Just wanted to stop in and say thank you for uploading this to the site. I have had a hard time finding a good daily driver and this is perfect for my needs.
If you are still building weekly for your own personal use i would greatly appreciate you uploading here as well.
Also I like the inclusion of more cpu governors such as smartmax_eps, has been great for pokemon go