yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] krasoski:
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.
[Motorola Droid 3] glennj99:
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.
[Motorola Droid 3] harryspar:
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.
[Motorola Droid 3] fxwrangler:
cm9 rom slot

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.
[Motorola Droid 3] harryspar:
Thanks, fxwrangler!

Was 0120820 a Kexec build?
[Motorola Droid 3] fxwrangler:
I don't believe it was Kexec in this particular build. Someone correct me if I'm wrong.
[Motorola Droid 3] Munckster:
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!
[Motorola Droid 3] krasoski:
" 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?
[Motorola Droid 3] harryspar:
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.
[Motorola Droid 3] Endoroid:
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
[Motorola Droid 3] rblanca:
And I think that there isn't HW Codecs
[Motorola Droid 3] fxwrangler:
Camera works and youtube video is fine. It does have some bugs.. I've never tried video camera. Here's a link. Try it and see if u like.. http://xannode.com/cm-9-20120820-UNOFFICIAL-solana.zip
[Motorola Droid 3] Munckster:
So let's try and see.

Thanks mate!
[Motorola Droid 3] MrObvious:
Ducati never did work on that ROM, so no hwcodecs so no video camera.
[Motorola Droid 3] Higgs_Boson:
Does anybody know if Hash made any mention of the reworked D3 kernel he was working on?
[Motorola Droid 3] dhacker29:
He has everything about ready to switch to the new kernel. Should be soon.
[Motorola Droid 3] deviousmrtaco:
Thanks for the update Dhacker I tried the 4/20 (insert joke about drugs here) nightly for solana and I can confirm speakerphone is working 100% in call thanks for the fix.
[Motorola Droid 3] dhacker29:
Sweet I'm glad it worked. I'm flying blind without device but it is very similar to targa so I figured that would fix it. ;)
[Motorola Droid 3] harryspar:
Thanks for the link, fxwrangler.

Question: did you get audio bugs on this build, like call or media audio occasionally gong silent till you reboot or toggle Bluetooth?

That seemed to be the main trouble for me on Steel Droid's ICS builds.
[Motorola Droid 3] Endoroid:
Yes it was a known bug
[Motorola Droid 3] harryspar:
Does anyone happen to have a link to a kexec cm9 build other than Hashcode's from the OP?

That one isn't working for me for some reason - phone doesn't wake up once it goes to sleep.
[Motorola Droid 3] attack11:
Does anyone have problems with wifi in that build? What safestrape should i use?
[Motorola Droid 3] ricky12:
EDIT: Good questions.

As for the Wi-Fi, I'm in the same boat. Wi-Fi's been touchy on these builds with random drops. I'm hoping that won't be the case here with this one.
[Motorola Droid 3] Bobbar:
Just tried the 422 nightly.

No audio / media server crashing.

Besides that it was running very well. Also noticed that system panel showed core 1 sleeping!
[Motorola Droid 3] harryspar:
[MENTION=3316648]Bobbar[/MENTION] What's the most recent nightly you've tried that worked well without media or other bugs?
[Motorola Droid 3] Bobbar:
I came from 413, which isn't available anymore (they only keep the last 5).

I've been following the kernel commits here: https://github.com/STS-Dev-Team/kernel_mapphone_kexec/commits/jb-mr1

It looks like Hash did a bit of merging on 4/21 which may have broke some stuff, although I'm not sure that is the exact repository the nightlies are building the kernel from.

But I would try one from before 4/21, it might be OK.
[Motorola Droid 3] Higgs_Boson:
How stable is 4/22? Is the phone snappy while Core 1 is asleep? Or, is the core being asleep a glitch, I wonder...

I can't wait for the new kernel, as I am hoping it improves responsiveness, and cuts battery drain.
[Motorola Droid 3] Bobbar:
What I meant was that the second core was sleeping while in idle, what I would think is more normal behavior not a glitch.

However after looking more closely it looks like this behavior is related to I/O Sheduler / CPU Governor, which they changed the default settings for recently; NOOP and HOTPLUG respectively. I can replicate the behavior in 4\13 by setting IO Shed to NOOP and governer to HOTPLUG.

From what Hash is saying, the new kernel is working great on similar devices like the Bionic. I too am anxiously waiting.
[Motorola Droid 3] prg318:
I had absolutely no audio (media or call audio) on 4/22 so I've reverted back to 4/20.
[Motorola Droid 3] Higgs_Boson:
That makes sense now with the governor as hotplug. Although, I'm wracking my brain trying to figure out if I like deadline or cfq better. Technically, cfq should be better for power savings and dual core, low memory devices.
[Motorola Droid 3] harryspar:
Anyone have any thoughts or comments about the responsiveness of your device with the new ROMs?

One thing I miss about the old non-kexec ICS builds is that they were pretty zippy.

Now, not so much.

When I hit the search softkey, for example, it's a good few seconds before Google Search app loads and the keyboard comes up.

Any setting / tweaks I ought to change?
[Motorola Droid 3] Bobbar:
Very slow. Slowest ROM I've every used on it. As to be expected; it isn't supposed to be a daily driver.

If you watch the CPU usage, you can see that it's spending a lot of time lost in I/O and kernel.

The one thing that is faster than the non-kexec ICS is the time it takes to bring up previous apps. Long press home, and bam, it comes right up -- more or less. The ICS with gingerbread kernel would hang for several seconds. *shrug*
[Motorola Droid 3] Higgs_Boson:
EDIT:

My tweaks are as follows.

+ I keep the CPU ranges at 1200 MHz MAX and 300 MHz MIN; with the Hotplug governor and the CFQ i/o scheduler.

I tweak the governor at:

SAMPLE RATE: 30000

UP THRESHOLD: 65

DOWN DIFFERENTIAL: 3

DOWN THRESHOLD: 50

HOTPLUG IN SAMPLING PERIODS: 5

HOTPLUG OUT SAMPLING PERIODS: 20

IGNORE NICE LOAD: 0

I/O IS BUSY: 0

+ I also use a couple of programs that I FEEL absolutely make the device faster.

+ I use an app called RAM MANAGER PRO on the "MORE FREE MEMORY" setting with

Launcher locked in the memory

Set to start on boot

+ I also use the app called SEEDER with:

Aggressive settings

Service always running (even with screen off)

Extend I/O Queue

Starts automatically on boot

Again, these are my settings based on my opinion and trial and error. I am not guaranteeing these will work for you, but they seem to make a huge difference for me.

I'm on the 4/20 build and find it to be quite responsive. It needs to be mentioned, however, that I have spent many an hour tweaking i/o and governor settings. I am able to multitask with relative ease. The battery life is no better or worse with my customizations, either; as opposed to previous observations. I'm still at work and will try to share my tweaks when I get a chance.

Sent from my XT862
[Motorola Droid 3] harryspar:
Thank you, Higgs_Boson! I made all the tweaks you mentioned and all I can say is WOW! There is a measurable boost in responsiveness, no question about it, and the battery life is roughly the same.

Thanks again!
[Motorola Droid 3] Higgs_Boson:
Thanks for your feedback. At least I know my experimentation paid off.
[Motorola Droid 3] ricky12:
I just got ics running again but I may give this a go. Thank you for the settings. :beer:
[Motorola Droid 3] harryspar:
ricky12 what build are you using and how is it?
[Motorola Droid 3] ricky12:
I'm using the non kexec CM9 build found here: http://xdaforums.com/showthread.php?p=40486241#post40486241

So far, beyond the notorious random wi-fi disconnects, it's pretty stable. I have had one instance of the phone not turning on again after being left alone for a while, pulling the battery got me back up and running though. Camera works well, although no video but I don't do the latter at all so no big deal.

I will say that it can feel a bit slow especially when it comes to app launches, and input lag can occur. Chrome isn't really a good experience on it..best to run the native ICS browser, it's plenty speedy.

Still, I feel like those are small tradeoffs to make to get off of Gingerbread...which was just beginning to annoy me.

I forgot for a second that there's no camera in the kexec JB builds...I don't take photos terribly often but it's nice to not have to restart the phone to get to a camera when you need it: By the time you get it set up and stuff the moment's likely lost.

If JB's as buttery smooth with Higgs Boson's settings as people say though...i may be installing another OS tonight.
[Motorola Droid 3] Higgs_Boson:
Try JB with my settings. You might be surprised. (I'd also like the feedback.) But, I would advise you to make a backup of your CM9 setup, so you won't have to hassle with reverting back in case you decide to do so.

Sent from my XT862
[Motorola Droid 3] ricky12:
Will do later today.
[Motorola Droid 3] Bobbar:
Any chance you could upload 4/20 somewhere? I thought I had DL'd it last week, now it's gone from the nightly list.
[Motorola Droid 3] Higgs_Boson:
There you go:

http://www.filedropper.com/cm-101-20130420-nightly-solana

Enjoy. :good:
[Motorola Droid 3] Bobbar:
Awesome, thank you!

Yes, this is much better than 4/13.
[Motorola Droid 3] harryspar:
Is there a specific issue or bug that is fixed in 4/20 as compared to 4/13, or is it just smoother in general?
[Motorola Droid 3] Skreelink:
Just incase there are any users on US-GSM for AT&T/T-Mobile, I've modified the 4/20 build.prop for the XT883 radio. :)

Click here for info and build.prop attached to the post. I've NOT tested data yet, will tomorrow as I am in a roaming area with talk/text only and no signal (I see a bar occassionally on a local GSM network, no Verizon, AT&T, Sprint, or T-Mobile!). Hard to test stuff at home without service. ;)

The build.prop should work on other nightly versions, but the system will read as info from the 4/20 build. After pushing the build.prop, setting rw-r--r-- permissions, reboot, then go to mobile networks and set GSM/WCDMA (after boot phone process might crash once until you set this).

EDIT: Data works beautifully. :) Now I just need to work on fixing the signal, I know there was something somewhere, I just can't research it right now. For now I am using the app signal notification found here: https://play.google.com/store/apps/details?id=info.narazaki.android.signalnotification
[Motorola Droid 3] Higgs_Boson:
Not necessarily. The only thing I can think of is that DHacker got the speakerphone working again. I just uploaded some settings I tweaked to make the experience a little smoother.

Sent from my XT862
[Motorola Droid 3] Bobbar:
I tried Higgs tweaks on 4/13 but it actually appeared to make things worse.

If you look at the repositories listed here there haven't really been any major commits since February so I have no idea where to find what changes would have been made to fix/break thing on these nighties.

Perhaps someone could explain.
[Motorola Droid 3] ricky12:
Finally got JB installed yesterday and installed using your settings, save for the ram usage app you chose: went with ROM Toolbox's "strict" task manager setting, white listing apps i needed of course.

Feedback: I noticed a immediate difference changing the memfree settings from the system default...phone literally slowed to a crawl when i tried setting it back to default...not doing that again!

Overall the phone is snappy for the most part, may ditch Trebuchet for a alternate launcher that lets you lock it in memory (and yes Trebuchet is one of the white listed apps...), but no big deal.

I don't know how you managed to clock yours up to 1.4 ghz...my max according to both SetCPU and ROM Toolbox is 1.0 Ghz. Custom Kernel?

Downsides: Phone gets a little warm, and while I'm still trying to get a feel for battery life...it dropped from fully charged to 30% in about 3 hours of light to moderate use (podcast listening through dogcatcher, reading a email or two, and charging at least over USB is slow going.

I'm hoping the battery issues will get better as builds become more stable. Anywho, thanks again for the settings! :good: :)
[Motorola Droid 3] Higgs_Boson:
A couple of things:

I have the standard kernel from Hash, but I am able to overclock to 1.2 GHz. If all else fails, you could always overclock in the performance settings directly in the ROM, and tweak the kernel specifics in SetCPU.

I used Titanium to make a backup of Trebuchet, and then uninstalled for Nova Launcher free.

The phone running warm is normal and your described battery life sounds about right under the conditions you used it. Battery life is abysmal.

Hash is working on a wholly reworked kernel for our device. According to dhacker, preparations are almost compete and Hash seems to indicate that we have much to look forward to.

Sent from my XT862
[Motorola Droid 3] ricky12:
Thanks for the reply! :good:

I need it to last more than it does (or at least charge ok under USB) since I'm a college student so back to ICS I go until Hash is ready with the kernel.

Think your settings changes will be useful under ICS?
[Motorola Droid 3] Higgs_Boson:
It should have the same effect to my knowledge. It's not like they're radical changes or adjustments; just a few kernel tweaks on when to increase and decrease the CPU frequencies.

The nice thing about the Hotplug governor is that you can save a lot of battery life when the screen is off and the CPU is under less pressure, as Hotplug has the ability to put CPU cores to sleep when unused.

The other settings are just RAM adjustments and Seeder works by elongating input and output requests and demanding more "entropy" for random data. Although, Seeder is a person-by-person decision really, some say it's placebo, I've heard others say it's dangerous. I've never researched any of those claims, but I am almost convinced it works.
[Motorola Droid 3] gadgetrants:
Oh mighty thread, please come back to life, and tell me the D3 has hope for a new, magical kernel that will make my phone worth loving again. :o

-Matt
[Motorola Droid 3] glennj99:
Back to life, yes, but you will need to wait patiently a bit longer for news from HashCode of improvements. The new kernel he is working on will be a major improvement.

With this current kernel, I have been running the CM nightlies and they have allowed me to play Ingress and make calls and SMS and so forth just fine in Italy on both a Wind and a TIM sim chip (phone unlocked for international use by Verizon). I was surprised how well it worked, actually. It IS a World Phone - who would have guessed !

The latest CM nightly though, the one from 3 May I think, is not working with Ingress beta v1.25.2 (latest Ingress beta). It crashes while starting up, during the location search animation, all the way back to the CyanogenMod start-up animation (the circle stuff). I have no idea who is to blame (I suspect Ingress), but until I upgraded both Ingress and Cyanogenmod (together, duh...), all was well. Its not the radio code, because in the USA the phone has no access to a non-wifi network. Used to work tethered here though.
[Motorola Droid 3] gadgetrants:
Thanks Glenn -- hope you had a good time in Italy. We were in Rome last May with our two D3s (stock ROM, though) and like you I was pleased at how easily they worked. I was even a bit more surprised that the TIM guy immediately knew how to program the phone once I'd bought the SIM card. The nicest surprise of all was going home and seeing that not once did I accidentally turn on data with the Verizon card in either phone, and unknowingly sync it. Disaster averted!

Our contracts end in October. Kind of a moot point anyway, because there's no way to stay on contract and get an upgrade without losing unlimited data (thanks Verizon). So I'm particularly hopeful that whatever is around the corner kernel-wise is a major improvement. I'm fine going without camera, but the phone is running best on Gingerbread right now which isn't saying much.

-Matt
[Motorola Droid 3] ricky12:
Mine ends in November. I'm literally counting down the months. :p

Anyway, I too have noticed the Gingerbread thing. It makes sense I guess until the new kernel is ready which i'm psyched for! In the meantime I'm tempted to wipe away my rom-slots and return to the stock ROM for now.
[Motorola Droid 3] gadgetrants:
I'm sorry to hear that -- it probably means you're part of the HOLY-CRAP-DID-THEY-JUST-ANNOUNCE-THE-DROID4?!?!?!?! club like me. I'm still in therapy over the fact that the D3 was released in July and barely 6 months later the D4 came out. Actually, I was cool with the whole thing, figuring we were going to get ICS.

Anyway, we all know how that story went. Which is ALL the more reason why I deeply appreciate hashcode and the other devs who've continued to work on the D3. It's a personally meaningful gesture in a technologically cruel world. :crying:

-Matt
[Motorola Droid 3] ricky12:
Exactly. My Droid 1 was dying a painful death with power button, keyboard, and headphone jack woes. I first upgraded to the Stratosphere instead of the D3 due to the 4G and the Galaxy S' historical open to tinkering nature, but after having 2 handsets with random reboots (plus a dearth of custom ROMs) I threw in the towel and went with the D3. "So what if the bootloader was encrypted, it'll get ICS and has a removable battery unlike the D4..." i thought.

I felt even better when I found out that the Stratosphere wouldn't get upgraded, "dodged a bullet there!" was my sentiments.

And yeah..we all know how it went down. What kills me the most is how short a lot of people's memories are. I listened to a certain podcast the other day and people recommended the Motorola handset over the LG because "Motorola's doing really good at updates....they're updating all their recent older handsets...."

So yeah, I definitely appreciate all the hard work Hashcode and others are doing to improve this handset. Seriously, kudos to all of you working on it. :)
[Motorola Droid 3] Eclipse00:
Dock Detection

Wondering if anyone has had any luck getting either the car or bedside dock to work? I looked back through this forum and didn't see much success. Like a few others, this is holding me back from using this as my primary boot.

Cheers and Much thanks for Hash for all the work and support.
[Motorola Droid 3] Munckster:
I'm a big fan of the guys that doing this amount of effort to make our phones better.

I'm hopeful that Hash and Dhacker could eventually find a solution, or maybe another solution to give us an afterlife with our phones. Here in Brazil, I don't have much of a choice of a good phone with a keyboard.

The worst of all is the lack of support from Motorola, that doesn't help us with anything.

Because I really need the camera working, Maybe I'll wait a little more. Besides, I never managed to connect to 3G, so to use it as a daily driver, sadly still doesn't work for me.

I hope that someday we could have a working JB.

Keep up the excellent job, devs!
[Motorola Droid 3] harryspar:
RAM questions.

Does anyone have any input on optimizing RAM on these ROMs?

The OS hogs almost all the RAM, leaving very little for running apps, which seems to be at least part of the reason this ROM is sluggish.

Does anyone have suggestions for tweaks for this?

Are there UI or OS elements that can be disabled or deleted?

What about zRAM settings?

All guesses / suggestions / tips are appreciated.

(PS Tip of the hat to higgs_boson for his tweaks [Bottom of page 204]. Anyone just arriving should check that out)
[Motorola Droid 3] Higgs_Boson:
You could always try a minfree memory manager. In addition to my tweaks, I use jrummy's memory manager with the minfree settings. (It also has some great presets.)

https://play.google.com/store/apps/...sImNvbS5qcnVtbXkuYXBwcy5tZW1vcnkubWFuYWdlciJd

I always enable zRam settings with the default settings and enable the purging of assets option.

You could also try the app Greenify, which allows you to hibernate apps until you activate them, or a sync is required. Unfortunately, this app cannot hibernate system apps. But, since Facebook is often pinged as a rogue app, it might be beneficial to hibernate that.

https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5vYXNpc2ZlbmcuZ3JlZW5pZnkiXQ.

You could also try a low-resource launcher. Nova, Apex, Trebuchet all require a significant amount of memory.

If I can think of any other tweaks, I'll make a note of it.
[Motorola Droid 3] glennj99:
I should add that I have gone back to some April versions of the Solana CM nightlies, and none of them will work with Ingress 1.25.2, so I staart to think the Ingress beta is no longer compatible with Cyanogenmod on the droid3. This is a real shame. Works still on Stock.

:crying:
[Motorola Droid 3] MrObvious:
I think people forget that the Droid 3 was actually made by Motorola proper before it was bought by Google and Google is now saying how to make and update the phones so it's gotten better in terms of updates.
[Motorola Droid 3] ricky12:
The Bionic was released before the Google purchase. Yes, to be fair, they got a bit of a bad hand with the software + launch timing of the RAZR. I get that.

But it's not like even the D3's latest MR is perfect (i'm on it again...its ok but there's still some flaky/laggy stuff going on in motorola's Droid line GB launcher...) + we too got burned by Motorola's crap launch timing when the D4 came out mere months later.

It also isn't like the RAZR and Droid 4 weren't already released before Google arrived.

The least they could have done IMO is threw us a belated ICS bone like they did with JB for the Bionic, IMO. After all...Motorola's brief resurgence into the smartphone spotlight all started with the Droid line of qwerty sliders.
[Motorola Droid 3] harryspar:
Sleep Of Death?

Anyone finding the D3 hard to wake after it's been sleeping?

I get SOD when trying the Kexec CM9 and CM10 builds but not on CM10.1, and @__tobby__ on Twitter reports having SOD on CM10.1 too.

Anyone else having this (or better yet, a fix)?